MedMij:IG:Vissue-MM-3407/FHIR IG - Bewerkingsoverzicht

Pieter Edelman op 30 aug 2022 om 12:11

2022-08-30T12:11:59Z

← Oudere versie		Versie van 30 aug 2022 12:11
Regel 2:		Regel 2:
	__NOINDEX__		__NOINDEX__
	__NUMBEREDHEADINGS__		__NUMBEREDHEADINGS__
	{{DISPLAYTITLE:MedMij FHIR R4 Implementation Guide {{VersieInfo\|MedMij_FHIR_IG_R4\|release=V6}}}}		{{DISPLAYTITLE:MedMij FHIR R4 Implementation Guide {{VersieInfo\|MedMij_FHIR_IG_R4\|release=V1}}}}
	{{MedMij:IG:Vprepub-1/Issuebox_FHIR_IG}}		{{MedMij:IG:Vprepub-1/Issuebox_FHIR_IG}}

Pieter Edelman: Fix links

2022-08-30T11:42:37Z

Fix links

← Oudere versie		Versie van 30 aug 2022 11:42
Regel 3:		Regel 3:
	__NUMBEREDHEADINGS__		__NUMBEREDHEADINGS__
	{{DISPLAYTITLE:MedMij FHIR R4 Implementation Guide {{VersieInfo\|MedMij_FHIR_IG_R4\|release=V6}}}}		{{DISPLAYTITLE:MedMij FHIR R4 Implementation Guide {{VersieInfo\|MedMij_FHIR_IG_R4\|release=V6}}}}
	{{MedMij:Vprepub-~~2020.01~~/Issuebox_FHIR_IG}}		{{MedMij:IG:Vprepub-1/Issuebox_FHIR_IG}}

	[[Bestand:MedMij2.png \|link=https://www.medmij.nl/\|rechts\|Naar medmij.nl]]		[[Bestand:MedMij2.png \|link=https://www.medmij.nl/\|rechts\|Naar medmij.nl]]
Regel 15:		Regel 15:

	==Scope==		==Scope==
	The scope of this guide includes requirements to enable PHR and XIS vendors in the Dutch realm to use standardized structured data in a defined inter-organizational transaction. Health is a vast domain. Therefore, MedMij has made scoping choices for its roadmap. MedMij starts with a limited number of medical subdomains but has the vision to elaborate on more domains later. In scope domains are first described in the [[MedMij:~~Vissue-MM-3408~~/Ontwerpen\|functional design]] that underlies this technical design.		The scope of this guide includes requirements to enable PHR and XIS vendors in the Dutch realm to use standardized structured data in a defined inter-organizational transaction. Health is a vast domain. Therefore, MedMij has made scoping choices for its roadmap. MedMij starts with a limited number of medical subdomains but has the vision to elaborate on more domains later. In scope domains are first described in the [[MedMij:FO:V1/Ontwerpen\|functional design]] that underlies this technical design.

	==Background==		==Background==

Pieter Edelman: Pieter Edelman heeft de pagina MedMij:Vissue-MM-3407/FHIR IG hernoemd naar MedMij:IG:Vissue-MM-3407/FHIR IG zonder een doorverwijzing achter te laten

2022-08-30T11:35:34Z

Pieter Edelman heeft de pagina MedMij:Vissue-MM-3407/FHIR IG hernoemd naar MedMij:IG:Vissue-MM-3407/FHIR IG zonder een doorverwijzing achter te laten

← Oudere versie	Versie van 30 aug 2022 11:35
(geen verschil)

Niek van Galen: HOTFIX: VersieInfo aangepast

2022-08-18T13:55:11Z

HOTFIX: VersieInfo aangepast

← Oudere versie		Versie van 18 aug 2022 13:55
Regel 2:		Regel 2:
	__NOINDEX__		__NOINDEX__
	__NUMBEREDHEADINGS__		__NUMBEREDHEADINGS__
	{{DISPLAYTITLE:MedMij FHIR R4 Implementation Guide {{VersieInfo\|~~FHIR_IG~~\|release=V6}}}}		{{DISPLAYTITLE:MedMij FHIR R4 Implementation Guide {{VersieInfo\|MedMij_FHIR_IG_R4\|release=V6}}}}
	{{MedMij:Vprepub-2020.01/Issuebox_FHIR_IG}}		{{MedMij:Vprepub-2020.01/Issuebox_FHIR_IG}}

Niek van Galen: HOTFIX: release=V6 aan VersieInfo toegevoegd

2022-08-18T13:50:14Z

HOTFIX: release=V6 aan VersieInfo toegevoegd

← Oudere versie		Versie van 18 aug 2022 13:50
Regel 2:		Regel 2:
	__NOINDEX__		__NOINDEX__
	__NUMBEREDHEADINGS__		__NUMBEREDHEADINGS__
	{{DISPLAYTITLE:MedMij FHIR R4 Implementation Guide {{VersieInfo\|FHIR_IG}}}}		{{DISPLAYTITLE:MedMij FHIR R4 Implementation Guide {{VersieInfo\|FHIR_IG\|release=V6}}}}
	{{MedMij:Vprepub-2020.01/Issuebox_FHIR_IG}}		{{MedMij:Vprepub-2020.01/Issuebox_FHIR_IG}}

Luud Slagter op 18 aug 2022 om 10:25

2022-08-18T10:25:55Z

← Oudere versie		Versie van 18 aug 2022 10:25
Regel 12:		Regel 12:

	==Purpose==		==Purpose==
	An implementation guide for making use of FHIR in the Dutch context. This guide is developed specifically for the use of HL7® FHIR® between personal health records (PHR) and healthcare provider systems (XIS). PHR and XIS vendors that participate in MedMij conform to a framework of agreements, in Dutch this is called the 'Afsprakenstelsel'. HL7 FHIR, or just FHIR, plays an important role among those agreements and is used as a standard to exchange health information between the involved parties. The purpose of this guide is to describe use cases and provide technical guidance on how to implement FHIR in these situations. This guide outlines the FHIR building blocks, or profiles, involved in these use cases. Moreover, this guide provides a textual explanation of these building blocks and describes their relationships and boundaries.		An implementation guide for making use of FHIR in the Dutch context. This guide is developed specifically for the use of HL7® FHIR® between personal health records (PHR) and healthcare provider systems (XIS). PHR and XIS vendors that participate in MedMij conform to a framework of agreements, in Dutch this is called the [https://www.medmij.nl/afsprakenstelsel/ 'Afsprakenstelsel']. HL7 FHIR, or just FHIR, plays an important role among those agreements and is used as a standard to exchange health information between the involved parties. The purpose of this guide is to describe use cases and provide technical guidance on how to implement FHIR in these situations. This guide outlines the FHIR building blocks, or profiles, involved in these use cases. Moreover, this guide provides a textual explanation of these building blocks and describes their relationships and boundaries.

	==Scope==		==Scope==
Regel 25:		Regel 25:

	==Audience==		==Audience==
	The main target audience of this implementation guide is software vendors and developers that ~~will implement~~ FHIR as part of electronic information exchange under MedMij. This IG is intended for developers of both PHR and XIS vendors.		The main target audience of this implementation guide are software vendors and developers that are implementing FHIR as part of electronic information exchange under MedMij. This IG is intended for developers of both PHR and XIS vendors.
	Users of this guide are expected to be familiar with the [https://hl7.org/fhir/R4 FHIR specification] and resource processing. This guide provides links to relevant sections of the FHIR specification. This implementation guide is not intended to be a tutorial on that subject.		Users of this guide are expected to be familiar with the [https://hl7.org/fhir/R4 FHIR specification] and resource processing. This guide provides links to relevant sections of the FHIR specification. This implementation guide is not intended to be a tutorial on that subject.

Regel 35:		Regel 35:
	The 'Afsprakenstelsel' references the MedMij information standards. In addition, the MedMij information standards are specified in the context of the 'Afsprakenstelsel'. This applies to the implementation guidance of the use cases described in this implementation guide.		The 'Afsprakenstelsel' references the MedMij information standards. In addition, the MedMij information standards are specified in the context of the 'Afsprakenstelsel'. This applies to the implementation guidance of the use cases described in this implementation guide.

	For example, all use cases performed in the context of a specific authenticated patient, for which an OAuth2 token has been retrieved using the Authentication mechanisms described in the ~~[https://www.medmij.nl/afsprakenstelsel/~~ 'Afsprakenstelsel']. This token must be passed in each call in the HTTP header named <code>Authorization</code>. Each XIS Gateway is required to perform filtering based on the patient associated with the OAuth2 token received for the request so that only the records associated with the authenticated patient are returned.		For example, all use cases performed in the context of a specific authenticated patient, for which an OAuth2 token has been retrieved using the Authentication mechanisms described in the 'Afsprakenstelsel'. This token must be passed in each call in the HTTP header named <code>Authorization</code>. Each XIS Gateway is required to perform filtering based on the patient associated with the OAuth2 token received for the request so that only the records associated with the authenticated patient are returned.
	{{#lst:FHIR:V1.0_FHIR_IG_R4\|OverarchingPrinciples}}		{{#lst:FHIR:V1.0_FHIR_IG_R4\|OverarchingPrinciples}}

Luud Slagter op 18 aug 2022 om 10:16

2022-08-18T10:16:44Z

← Oudere versie		Versie van 18 aug 2022 10:16
Regel 12:		Regel 12:

	==Purpose==		==Purpose==
	An implementation guide for making use of FHIR in the Dutch context. This guide is developed specifically for the use of HL7® FHIR® between personal health records(PHR) and healthcare provider systems (XIS). PHR and XIS vendors that participate in MedMij conform to a framework of agreements, in Dutch this is called the '~~afsprakenstelsel~~.' HL7 FHIR, or just 'FHIR', plays an important role among those agreements and is used as a standard to exchange health information between the involved parties. The purpose of this guide is to describe use cases and provide technical guidance on how to implement FHIR in these situations. This guide outlines the FHIR building blocks, or profiles, involved in these use cases. Moreover, this guide provides a textual explanation of these building blocks and describes their ~~relationship~~ and boundaries.		An implementation guide for making use of FHIR in the Dutch context. This guide is developed specifically for the use of HL7® FHIR® between personal health records (PHR) and healthcare provider systems (XIS). PHR and XIS vendors that participate in MedMij conform to a framework of agreements, in Dutch this is called the 'Afsprakenstelsel'. HL7 FHIR, or just FHIR, plays an important role among those agreements and is used as a standard to exchange health information between the involved parties. The purpose of this guide is to describe use cases and provide technical guidance on how to implement FHIR in these situations. This guide outlines the FHIR building blocks, or profiles, involved in these use cases. Moreover, this guide provides a textual explanation of these building blocks and describes their relationships and boundaries.

	==Scope==		==Scope==
	The scope of this guide includes requirements to enable PHR and XIS in the Dutch realm to use standardized structured data in a defined inter-organizational transaction. Health is a vast domain. Therefore, MedMij has made scoping choices for its roadmap. MedMij starts with a limited number of medical subdomains but has the vision to elaborate on more domains later. In scope domains are first described in the [[MedMij:Vissue-MM-3408/Ontwerpen\|functional design]] that underlies this technical design.		The scope of this guide includes requirements to enable PHR and XIS vendors in the Dutch realm to use standardized structured data in a defined inter-organizational transaction. Health is a vast domain. Therefore, MedMij has made scoping choices for its roadmap. MedMij starts with a limited number of medical subdomains but has the vision to elaborate on more domains later. In scope domains are first described in the [[MedMij:Vissue-MM-3408/Ontwerpen\|functional design]] that underlies this technical design.

	==Background==		==Background==
	MedMij aims to stimulate electronic information exchange between patients and caregivers. Caregivers generally have access to software applications to help them support their work in treating patients. Software applications for patients are evolving as we speak, but patients typically are not yet enabled to be regarded as a true partner in the care process. MedMij delivers an agreements scheme to enable patients to become that true partner. The section [[#Afsprakenstelsel]] describes the relation to this implementation guide.		MedMij aims to stimulate electronic information exchange between patients and caregivers. Caregivers generally have access to software applications to help them support their work in treating patients. Software applications for patients are evolving as we speak, but patients typically are not yet enabled to be regarded as a true partner in the care process. MedMij delivers an agreements scheme to enable patients to become that true partner. The section [[#Afsprakenstelsel]] describes the relation to this implementation guide.

	Information standards have a functional and technical component. The functional part contains definitions of relevant concepts (~~dataset~~) and ~~scenario’s~~ that define when to exchange which of those concepts. The technical part translates the functional ~~scenario’s~~ in an exchange format (such as HL7v3 or FHIR). The stakeholders in MedMij have chosen to introduce FHIR as a modern standard to exchange information in MedMij. A Dutch ~~factsheet~~ that explains why FHIR is chosen is available on the [https://medmij.nl/wp-content/uploads/2021/12/Factsheet-FHIR-november-2021.pdf MedMij website]. MedMij delivers a FHIR representation ([https://hl7.org/fhir/R4/profiling.html profiles]) for each domain in scope.		Information standards have a functional and technical component. The functional part contains definitions of relevant concepts (data set) and scenarios that define when to exchange which of those concepts. The technical part translates the functional scenarios in an exchange format (such as HL7v3 or FHIR). The stakeholders in MedMij have chosen to introduce FHIR as a modern standard to exchange information in MedMij. A Dutch fact sheet that explains why FHIR is chosen is available on the [https://medmij.nl/wp-content/uploads/2021/12/Factsheet-FHIR-november-2021.pdf MedMij website]. MedMij delivers a FHIR representation ([https://hl7.org/fhir/R4/profiling.html profiles]) for each domain in scope.

	The program ‘Registratie aan de bron’ (Data capture at the point of Care) has defined [https://zibs.nl/wiki/HCIM_Mainpage Health and Care Information models] (zorginformatiebouwstenen or zibs) for The Netherlands. Zibs contain definitions of healthcare concepts. MedMij information standards contain mappings to these zibs. MedMij creates FHIR profiles based on zibs which include mappings to the relevant zib concepts. As a result, the created profiles enable context-free implementation. Therefore, these profiles are applicable in a broader context than the described use cases or the MedMij context. Reuse of these profiles enables interoperability for health information.		The program ‘Registratie aan de bron’ (Data capture at the point of Care) has defined [https://zibs.nl/wiki/HCIM_Mainpage Health and Care Information models] (zorginformatiebouwstenen or zibs) for The Netherlands. Zibs contain definitions of healthcare concepts. MedMij information standards contain mappings to these zibs. MedMij creates FHIR profiles based on zibs which include mappings to the relevant zib concepts. As a result, the created profiles enable context-free implementation. Therefore, these profiles are applicable in a broader context than the described use cases or the MedMij context. Reuse of these profiles enables interoperability for health information.

	==Audience==		==Audience==
	The main target audience of this implementation guide is software vendors and developers that will implement FHIR as part of electronic information exchange under MedMij. This IG is intended for developers of PHR ~~as well as~~ XIS vendors.		The main target audience of this implementation guide is software vendors and developers that will implement FHIR as part of electronic information exchange under MedMij. This IG is intended for developers of both PHR and XIS vendors.
	Users of this guide are expected to be familiar with the [https://hl7.org/fhir/R4 FHIR specification] and resource processing. This guide provides links to relevant sections of the FHIR specification. This implementation guide is not intended to be a tutorial on that subject.		Users of this guide are expected to be familiar with the [https://hl7.org/fhir/R4 FHIR specification] and resource processing. This guide provides links to relevant sections of the FHIR specification. This implementation guide is not intended to be a tutorial on that subject.

Regel 35:		Regel 35:
	The 'Afsprakenstelsel' references the MedMij information standards. In addition, the MedMij information standards are specified in the context of the 'Afsprakenstelsel'. This applies to the implementation guidance of the use cases described in this implementation guide.		The 'Afsprakenstelsel' references the MedMij information standards. In addition, the MedMij information standards are specified in the context of the 'Afsprakenstelsel'. This applies to the implementation guidance of the use cases described in this implementation guide.

	For example, all use cases performed in the context of a specific authenticated patient, for which an OAuth2 token has been retrieved using the Authentication mechanisms described in the [https://www.medmij.nl/afsprakenstelsel/ '~~afsprakenstelsel~~']. This token must be passed in each call in the HTTP header named <code>Authorization</code>. Each XIS Gateway is required to perform filtering based on the patient associated with the OAuth2 token received for the request so that only the records associated with the authenticated patient are returned.		For example, all use cases performed in the context of a specific authenticated patient, for which an OAuth2 token has been retrieved using the Authentication mechanisms described in the [https://www.medmij.nl/afsprakenstelsel/ 'Afsprakenstelsel']. This token must be passed in each call in the HTTP header named <code>Authorization</code>. Each XIS Gateway is required to perform filtering based on the patient associated with the OAuth2 token received for the request so that only the records associated with the authenticated patient are returned.
	{{#lst:FHIR:V1.0_FHIR_IG_R4\|OverarchingPrinciples}}		{{#lst:FHIR:V1.0_FHIR_IG_R4\|OverarchingPrinciples}}

Niek van Galen: Link van transclude aangepast naar livepagina.

2022-08-17T12:47:24Z

Link van transclude aangepast naar livepagina.

← Oudere versie		Versie van 17 aug 2022 12:47
Regel 36:		Regel 36:

	For example, all use cases performed in the context of a specific authenticated patient, for which an OAuth2 token has been retrieved using the Authentication mechanisms described in the [https://www.medmij.nl/afsprakenstelsel/ 'afsprakenstelsel']. This token must be passed in each call in the HTTP header named <code>Authorization</code>. Each XIS Gateway is required to perform filtering based on the patient associated with the OAuth2 token received for the request so that only the records associated with the authenticated patient are returned.		For example, all use cases performed in the context of a specific authenticated patient, for which an OAuth2 token has been retrieved using the Authentication mechanisms described in the [https://www.medmij.nl/afsprakenstelsel/ 'afsprakenstelsel']. This token must be passed in each call in the HTTP header named <code>Authorization</code>. Each XIS Gateway is required to perform filtering based on the patient associated with the OAuth2 token received for the request so that only the records associated with the authenticated patient are returned.
	{{#lst:FHIR:~~Vissue-MM-3497_FHIR_IG_R4~~\|OverarchingPrinciples}}		{{#lst:FHIR:V1.0_FHIR_IG_R4\|OverarchingPrinciples}}

	=Release notes=		=Release notes=

Niek van Galen: VersieInfo toegevoegd

2022-08-16T11:24:08Z

VersieInfo toegevoegd

← Oudere versie		Versie van 16 aug 2022 11:24
Regel 2:		Regel 2:
	__NOINDEX__		__NOINDEX__
	__NUMBEREDHEADINGS__		__NUMBEREDHEADINGS__
	{{DISPLAYTITLE:MedMij FHIR R4 Implementation Guide}}		{{DISPLAYTITLE:MedMij FHIR R4 Implementation Guide {{VersieInfo\|FHIR_IG}}}}
	{{MedMij:Vprepub-2020.01/Issuebox_FHIR_IG}}		{{MedMij:Vprepub-2020.01/Issuebox_FHIR_IG}}

Niek van Galen: /* Release notes */

2022-08-11T09:22:46Z

Release notes

← Oudere versie		Versie van 11 aug 2022 09:22
Regel 42:		Regel 42:
	!style="text-align:left;"\|Release		!style="text-align:left;"\|Release
	!style="text-align:left;"\|Version		!style="text-align:left;"\|Version
	!style="text-align:left;"\|BITS ~~issue~~		!style="text-align:left;"\|BITS ticket
	!style="width:850px; text-align:left;"\|Description		!style="width:850px; text-align:left;"\|Description
	\|-		\|-

← Oudere versie		Versie van 11 aug 2022 09:22
Regel 42:		Regel 42:
	!style="text-align:left;"\|Release		!style="text-align:left;"\|Release
	!style="text-align:left;"\|Version		!style="text-align:left;"\|Version
	!style="text-align:left;"\|BITS ~~issue~~		!style="text-align:left;"\|BITS ticket
	!style="width:850px; text-align:left;"\|Description		!style="width:850px; text-align:left;"\|Description
	\|-		\|-