Zandbak/MM-440 - Bewerkingsoverzicht

Maarten Ligtvoet: Tekst vervangen - "{{#customtitle:" door "{{DISPLAYTITLE:"

2020-07-20T00:59:25Z

Tekst vervangen - "{{#customtitle:" door "{{DISPLAYTITLE:"

← Oudere versie		Versie van 20 jul 2020 00:59
Regel 1:		Regel 1:
	__NUMBEREDHEADINGS__		__NUMBEREDHEADINGS__
	{{~~#customtitle~~:MedMij FHIR Implementation Guide: BgZ 2.1.3}}		{{DISPLAYTITLE:MedMij FHIR Implementation Guide: BgZ 2.1.3}}
	{{MedMij:Vdraft_Issuebox}}		{{MedMij:Vdraft_Issuebox}}

Niek van Galen: /* Page history */ Categorie-vermelding weggehaald ivm Vdraft pagina

2020-05-28T09:10:26Z

Page history: Categorie-vermelding weggehaald ivm Vdraft pagina

← Oudere versie		Versie van 28 mei 2020 09:10
Regel 567:		Regel 567:
	* Added version in title, and document history		* Added version in title, and document history
	\|}		\|}
	~~[[categorie:MedMij FHIR Use Cases]]~~

Pieter Edelman: Versie 22126 van Pieter Edelman (overleg) ongedaan gemaakt

2019-10-14T09:08:28Z

Versie 22126 van Pieter Edelman (overleg) ongedaan gemaakt

← Oudere versie		Versie van 14 okt 2019 09:08
Regel 22:		Regel 22:

	The patient journey of [https://www.nictiz.nl/ehealth/MedMij Thomas van Beek], provides a patients context for exchanging a patient summary from a healthcare provider's system (XIS) to a personal health record (PHR). MedMij created a [https://informatiestandaarden.nictiz.nl/wiki/MedMij:V2019.01_Ontwerpen functional design] of the BgZ use case. This use case consists of enabling a patient to view his own BgZ in a PHR. This page will elaborate further on the HL7 FHIR details needed to exchange the BgZ information using FHIR.		The patient journey of [https://www.nictiz.nl/ehealth/MedMij Thomas van Beek], provides a patients context for exchanging a patient summary from a healthcare provider's system (XIS) to a personal health record (PHR). MedMij created a [https://informatiestandaarden.nictiz.nl/wiki/MedMij:V2019.01_Ontwerpen functional design] of the BgZ use case. This use case consists of enabling a patient to view his own BgZ in a PHR. This page will elaborate further on the HL7 FHIR details needed to exchange the BgZ information using FHIR.

	~~test~~

	==Actors involved==		==Actors involved==

Pieter Edelman: MM-440

2019-10-14T09:05:59Z

MM-440

← Oudere versie		Versie van 14 okt 2019 09:05
Regel 22:		Regel 22:

	The patient journey of [https://www.nictiz.nl/ehealth/MedMij Thomas van Beek], provides a patients context for exchanging a patient summary from a healthcare provider's system (XIS) to a personal health record (PHR). MedMij created a [https://informatiestandaarden.nictiz.nl/wiki/MedMij:V2019.01_Ontwerpen functional design] of the BgZ use case. This use case consists of enabling a patient to view his own BgZ in a PHR. This page will elaborate further on the HL7 FHIR details needed to exchange the BgZ information using FHIR.		The patient journey of [https://www.nictiz.nl/ehealth/MedMij Thomas van Beek], provides a patients context for exchanging a patient summary from a healthcare provider's system (XIS) to a personal health record (PHR). MedMij created a [https://informatiestandaarden.nictiz.nl/wiki/MedMij:V2019.01_Ontwerpen functional design] of the BgZ use case. This use case consists of enabling a patient to view his own BgZ in a PHR. This page will elaborate further on the HL7 FHIR details needed to exchange the BgZ information using FHIR.

			test

	==Actors involved==		==Actors involved==

Niek van Galen op 21 aug 2019 om 14:16

2019-08-21T14:16:05Z

← Oudere versie		Versie van 21 aug 2019 14:16
Regel 1:		Regel 1:
			__NUMBEREDHEADINGS__
	{{#customtitle:MedMij FHIR Implementation Guide: BgZ 2.1.3}}		{{#customtitle:MedMij FHIR Implementation Guide: BgZ 2.1.3}}
	{{MedMij:Vdraft_Issuebox}}		{{MedMij:Vdraft_Issuebox}}

Niek van Galen: /* History */

2019-08-21T14:14:41Z

History

← Oudere versie		Versie van 21 aug 2019 14:14
Regel 540:		Regel 540:
	Release notes can be found on the [[MedMij:V2019.01_OntwerpBGZ_2017#Release_notes\|functional design page]].		Release notes can be found on the [[MedMij:V2019.01_OntwerpBGZ_2017#Release_notes\|functional design page]].

	==~~History~~==		==Page history==
	{\| class="wikitable" "cellpadding="10"		{\| class="wikitable" "cellpadding="10"
	!style="text-align:left;"\|Release		!style="text-align:left;"\|Release

Niek van Galen op 21 aug 2019 om 14:13

2019-08-21T14:13:51Z

← Oudere versie		Versie van 21 aug 2019 14:13
Regel 1:		Regel 1:
	{{#customtitle:MedMij FHIR Implementation Guide: BgZ 2.1.3}}		{{#customtitle:MedMij FHIR Implementation Guide: BgZ 2.1.3}}
	{{MedMij:~~V2019.01_Issuebox_FHIR_IG~~}}		{{MedMij:Vdraft_Issuebox}}

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

Niek van Galen: /* Mappings */

2019-08-21T14:09:58Z

Mappings

← Oudere versie		Versie van 21 aug 2019 14:09
Regel 506:		Regel 506:
	Relevant HCIM to FHIR ValueSet mappings can be found [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=ConceptMap using the ConceptMap category].		Relevant HCIM to FHIR ValueSet mappings can be found [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=ConceptMap using the ConceptMap category].
	All profiles include HCIM mappings. HCIM concepts are mapped to the corresponding FHIR elements using the HCIMs concept id. The top of the StructureDefinition contains meta information regarding the HCIM mapping, such as the name and uri of the HCIM. In the StructureDefinition elements, the corresponding HCIM ID is given including the mapping meta information id.		All profiles include HCIM mappings. HCIM concepts are mapped to the corresponding FHIR elements using the HCIMs concept id. The top of the StructureDefinition contains meta information regarding the HCIM mapping, such as the name and uri of the HCIM. In the StructureDefinition elements, the corresponding HCIM ID is given including the mapping meta information id.

	This is illustrated in the following example:		This is illustrated in the following example:

Niek van Galen: /* Terminology, NamingSystems, Mappings */

2019-08-21T14:09:47Z

Terminology, NamingSystems, Mappings

← Oudere versie		Versie van 21 aug 2019 14:09
Regel 498:		Regel 498:

	===Terminology===		===Terminology===
	Relevant value sets can be found [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=ValueSet using the ValueSet category]. All resources can be downloaded in a .zip in XML or JSON format. In the .zip, the ~~value sets~~ are stored in the directory '~~value sets~~'.		Relevant value sets can be found [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=ValueSet using the ValueSet category]. All resources can be downloaded in a .zip file in XML or JSON format. In the .zip file, the ValueSets are stored in the directory 'Valuesets'.

	===NamingSystems===		===NamingSystems===
Regel 504:		Regel 504:

	===Mappings===		===Mappings===
	Relevant HCIM to FHIR ~~value set~~ mappings can be found [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=ConceptMap using the ConceptMap category].		Relevant HCIM to FHIR ValueSet mappings can be found [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=ConceptMap using the ConceptMap category].
	All profiles include HCIM mappings. HCIM concepts are mapped to the corresponding FHIR elements using the HCIMs concept id. The top of the StructureDefinition contains meta information regarding the HCIM mapping, such as the name and uri of the HCIM. In the StructureDefinition elements, the corresponding HCIM ID is given including the mapping meta information id. This is illustrated in the following example:		All profiles include HCIM mappings. HCIM concepts are mapped to the corresponding FHIR elements using the HCIMs concept id. The top of the StructureDefinition contains meta information regarding the HCIM mapping, such as the name and uri of the HCIM. In the StructureDefinition elements, the corresponding HCIM ID is given including the mapping meta information id.
			This is illustrated in the following example:

	<pre>		<pre>

Niek van Galen: /* List of StructureDefinitions */

2019-08-21T13:20:46Z

List of StructureDefinitions

← Oudere versie		Versie van 21 aug 2019 13:20
Regel 305:		Regel 305:
	!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:100px" \| ZIB NL		!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:100px" \| ZIB NL
	!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:100px" \| HCIM EN		!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:100px" \| HCIM EN
	!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:100px" \| FHIR ~~Resource~~		!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:100px" \| FHIR resource
	!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" \| FHIR ~~Profile~~		!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" \| FHIR profile
	\|-		\|-
	\| 1		\| 1