vpk:Vdraft FHIR eOverdracht Proeftuin phase 2 - Bewerkingsoverzicht

Pieter Edelman: Tekst vervangen - "{{VersieInfo\|([^\|]+)\|release=MedMij:" door "{{VersieInfo|$1|release="

2020-07-30T20:15:07Z

Tekst vervangen - "{{VersieInfo\|([^\|]+)\|release=MedMij:" door "{{VersieInfo|$1|release="

← Oudere versie		Versie van 30 jul 2020 20:15
Regel 25:		Regel 25:

	==Package and dependencies==		==Package and dependencies==
	eOverdracht uses the FHIR Packaging mechanism to conveniently bundle all examples, profiles and other conformance resources you need into a single download. The eOverdracht package has a dependency on the [https://simplifier.net/NictizSTU3-Zib2017/~packages Nictiz Zib2017 package {{VersieInfo\|package\|release=~~MedMij:~~V2019.01}}].		eOverdracht uses the FHIR Packaging mechanism to conveniently bundle all examples, profiles and other conformance resources you need into a single download. The eOverdracht package has a dependency on the [https://simplifier.net/NictizSTU3-Zib2017/~packages Nictiz Zib2017 package {{VersieInfo\|package\|release=V2019.01}}].
	==Example instances==		==Example instances==
	Example instances of the FHIR messages can be found on [https://simplifier.net/nictiz-stu3-eoverdracht Simplifier]:		Example instances of the FHIR messages can be found on [https://simplifier.net/nictiz-stu3-eoverdracht Simplifier]:

Pieter Edelman: Tekst vervangen - "{{MedMij:VersieInfo\|([^\|]+)\|([^}]+)}}" door "{{VersieInfo|$2|release=MedMij:$1}}"

2020-07-29T20:15:14Z

Tekst vervangen - "{{MedMij:VersieInfo\|([^\|]+)\|([^}]+)}}" door "{{VersieInfo|$2|release=MedMij:$1}}"

← Oudere versie		Versie van 29 jul 2020 20:15
Regel 25:		Regel 25:

	==Package and dependencies==		==Package and dependencies==
	eOverdracht uses the FHIR Packaging mechanism to conveniently bundle all examples, profiles and other conformance resources you need into a single download. The eOverdracht package has a dependency on the [https://simplifier.net/NictizSTU3-Zib2017/~packages Nictiz Zib2017 package {{MedMij:~~VersieInfo\|~~V2019.01~~\|package~~}}].		eOverdracht uses the FHIR Packaging mechanism to conveniently bundle all examples, profiles and other conformance resources you need into a single download. The eOverdracht package has a dependency on the [https://simplifier.net/NictizSTU3-Zib2017/~packages Nictiz Zib2017 package {{VersieInfo\|package\|release=MedMij:V2019.01}}].
	==Example instances==		==Example instances==
	Example instances of the FHIR messages can be found on [https://simplifier.net/nictiz-stu3-eoverdracht Simplifier]:		Example instances of the FHIR messages can be found on [https://simplifier.net/nictiz-stu3-eoverdracht Simplifier]:

Pieter Edelman: Tekst vervangen - "{{VersieInfo|" door "{{MedMij:VersieInfo|"

2020-07-29T20:00:36Z

Tekst vervangen - "{{VersieInfo|" door "{{MedMij:VersieInfo|"

← Oudere versie		Versie van 29 jul 2020 20:00
Regel 25:		Regel 25:

	==Package and dependencies==		==Package and dependencies==
	eOverdracht uses the FHIR Packaging mechanism to conveniently bundle all examples, profiles and other conformance resources you need into a single download. The eOverdracht package has a dependency on the [https://simplifier.net/NictizSTU3-Zib2017/~packages Nictiz Zib2017 package {{VersieInfo\|V2019.01\|package}}].		eOverdracht uses the FHIR Packaging mechanism to conveniently bundle all examples, profiles and other conformance resources you need into a single download. The eOverdracht package has a dependency on the [https://simplifier.net/NictizSTU3-Zib2017/~packages Nictiz Zib2017 package {{MedMij:VersieInfo\|V2019.01\|package}}].
	==Example instances==		==Example instances==
	Example instances of the FHIR messages can be found on [https://simplifier.net/nictiz-stu3-eoverdracht Simplifier]:		Example instances of the FHIR messages can be found on [https://simplifier.net/nictiz-stu3-eoverdracht Simplifier]:

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

2020-07-20T01:17:20Z

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

← Oudere versie		Versie van 20 jul 2020 01:17
Regel 1:		Regel 1:
	{{~~#customtitle~~:eOverdracht Proeftuin phase 2 FHIR Implementation Guide}}		{{DISPLAYTITLE:eOverdracht Proeftuin phase 2 FHIR Implementation Guide}}
	{{IssueBox\|Work in progress - See [[vpk:V3.1_FHIR_eOverdracht_Proeftuin\|official publication]] here.}}		{{IssueBox\|Work in progress - See [[vpk:V3.1_FHIR_eOverdracht_Proeftuin\|official publication]] here.}}
	=Introduction=		=Introduction=

Stephan Opdenberg: /* Introduction */

2020-04-29T11:04:26Z

Introduction

← Oudere versie		Versie van 29 apr 2020 11:04
Regel 3:		Regel 3:
	=Introduction=		=Introduction=

	This page will detail the HL7 requirments for exhcanging the data in the eOverdracht Proeftuin phase 2 as described in [[vpk:V3.1 eOverdracht Proeftuin\|the functional design]].Imnplementation of the eOverdracht Proeftuin is spread over 3 different phases. Phase 1 and 3 can be ~~foudn~~ by navigated the following links in the table listed below.		This page will detail the HL7 requirments for exhcanging the data in the eOverdracht Proeftuin phase 2 as described in [[vpk:V3.1 eOverdracht Proeftuin\|the functional design]].Imnplementation of the eOverdracht Proeftuin is spread over 3 different phases. Phase 1 and 3 can be found by navigated the following links in the table listed below.

	{\| class="wikitable"		{\| class="wikitable"

Stephan Opdenberg: /* Introduction */

2020-04-29T11:03:18Z

Introduction

← Oudere versie		Versie van 29 apr 2020 11:03
Regel 3:		Regel 3:
	=Introduction=		=Introduction=

	This page ~~details~~ the HL7 ~~FHIR requirements~~ for ~~exchanging~~ the data in the eOverdracht Proeftuin ~~pilot~~ described in [[vpk:V3.1 eOverdracht Proeftuin\|the functional design]].		This page will detail the HL7 requirments for exhcanging the data in the eOverdracht Proeftuin phase 2 as described in [[vpk:V3.1 eOverdracht Proeftuin\|the functional design]].Imnplementation of the eOverdracht Proeftuin is spread over 3 different phases. Phase 1 and 3 can be foudn by navigated the following links in the table listed below.

	~~TODO~~		{\| class="wikitable"
			! colspan="2" \| Phase 1 and Phase 3 of the eOverdracht Proeftuin
	~~Imnplementation~~ of the eOverdracht Proeftuin ~~is spread over~~ 3 ~~different phases. This page will detail the HL7 requirments for exhcanging the data in the eOverdracht Proeftuin phase 2 as described in~~ [[vpk:~~V3.~~1 ~~eOverdracht Proeftuin\|the functional design~~]].		\|-
	* For the implementation of Phase 1 to the [[vpk:~~Vdraft_FHIR_eOverdracht_Proeftuin~~\|~~Proeftuin Phase 1 page~~]] ~~should be visited.~~		\| style="text-align: center;" \| Phase 1
			\| style="text-align: center;" \| Phase 3
			\|-
			\| [[vpk:Vdraft_FHIR_eOverdracht_Proeftuin\|Proeftuin Phase 1 page]]
			\| [[vpk:Draft_FHIR_eOverdracht\|eOverdracht FHIR implementation guide]]
			\|-
			\|}
	* For the implementation of Phase 3, which is the complete message we recommend visitting [[vpk:Draft_FHIR_eOverdracht\|eOverdracht FHIR implementation guide]]		* For the implementation of Phase 3, which is the complete message we recommend visitting [[vpk:Draft_FHIR_eOverdracht\|eOverdracht FHIR implementation guide]]
	Phase two consists of the complete Aanmeldbericht as well as an incomplete Overdrachtsbericht. The Overdrachtsbericht is a subset of 11 HCIM's (complete set used in Aanmeldbericht) and an unstructured PDF containing the remaining data which are not part of the HCIM's.		Phase two consists of the complete Aanmeldbericht as well as an incomplete Overdrachtsbericht. The Overdrachtsbericht is a subset of 11 HCIM's (complete set used in Aanmeldbericht) and an unstructured PDF containing the remaining data which are not part of the HCIM's.


	~~/TODO~~

	This implementation guide assumes that the reader is familiar with [https://www.hl7.org/fhir/stu3/ FHIR(STU3)].		This implementation guide assumes that the reader is familiar with [https://www.hl7.org/fhir/stu3/ FHIR(STU3)].

Stephan Opdenberg: /* Introduction */

2020-04-16T14:28:26Z

Introduction

← Oudere versie		Versie van 16 apr 2020 14:28
Regel 8:		Regel 8:

	Imnplementation of the eOverdracht Proeftuin is spread over 3 different phases. This page will detail the HL7 requirments for exhcanging the data in the eOverdracht Proeftuin phase 2 as described in [[vpk:V3.1 eOverdracht Proeftuin\|the functional design]].		Imnplementation of the eOverdracht Proeftuin is spread over 3 different phases. This page will detail the HL7 requirments for exhcanging the data in the eOverdracht Proeftuin phase 2 as described in [[vpk:V3.1 eOverdracht Proeftuin\|the functional design]].
	For the implementation of Phase 1 to the [[vpk:Vdraft_FHIR_eOverdracht_Proeftuin\|Proeftuin Phase 1 page]] should be visited.		* For the implementation of Phase 1 to the [[vpk:Vdraft_FHIR_eOverdracht_Proeftuin\|Proeftuin Phase 1 page]] should be visited.
	For the implementation of Phase 3, which is the complete message we recommend visitting [[vpk:Draft_FHIR_eOverdracht\|eOverdracht FHIR implementation guide]]		* For the implementation of Phase 3, which is the complete message we recommend visitting [[vpk:Draft_FHIR_eOverdracht\|eOverdracht FHIR implementation guide]]
	Phase two consists of the complete Aanmeldbericht as well as an incomplete Overdrachtsbericht. The Overdrachtsbericht is a subset of 11 HCIM's (complete set used in Aanmeldbericht) and an unstructured PDF containing the remaining data which are not part of the HCIM's.		Phase two consists of the complete Aanmeldbericht as well as an incomplete Overdrachtsbericht. The Overdrachtsbericht is a subset of 11 HCIM's (complete set used in Aanmeldbericht) and an unstructured PDF containing the remaining data which are not part of the HCIM's.

Stephan Opdenberg op 16 apr 2020 om 14:27

2020-04-16T14:27:56Z

← Oudere versie		Versie van 16 apr 2020 14:27
Regel 7:		Regel 7:
	TODO		TODO

	~~Implementation~~ of ~~these transactions~~ is spread over ~~multiple~~ phases. In the ~~first~~ phase ~~of the~~ Proeftuin ~~a simplified version of both~~ the ~~Aanmeldbericht en Overdrachtsbericht are being used~~. ~~Both messages exist~~ of ~~four HCIMs listed in~~ the ~~table below~~. ~~The Aanmeldbericht is send to~~ the ~~recieving organisation~~, which ~~after confirmation of recieving~~ the ~~aanmeldberricht, gets send the Overdrachtbericht.~~		Imnplementation of the eOverdracht Proeftuin is spread over 3 different phases. This page will detail the HL7 requirments for exhcanging the data in the eOverdracht Proeftuin phase 2 as described in [[vpk:V3.1 eOverdracht Proeftuin\|the functional design]].
			For the implementation of Phase 1 to the [[vpk:Vdraft_FHIR_eOverdracht_Proeftuin\|Proeftuin Phase 1 page]] should be visited.
			For the implementation of Phase 3, which is the complete message we recommend visitting [[vpk:Draft_FHIR_eOverdracht\|eOverdracht FHIR implementation guide]]
	Phase two consists of the complete Aanmeldbericht as well as an incomplete Overdrachtsbericht. The Overdrachtsbericht is a subset of 11 HCIM's (complete set used in Aanmeldbericht) and an unstructured PDF containing the remaining data which are not part of the HCIM's.		Phase two consists of the complete Aanmeldbericht as well as an incomplete Overdrachtsbericht. The Overdrachtsbericht is a subset of 11 HCIM's (complete set used in Aanmeldbericht) and an unstructured PDF containing the remaining data which are not part of the HCIM's.
	~~Phase three is the complete dataset of the Aanmeldbericht, Overdrachtsbericht Volwassenen, Overdrachtsbericht Kinderen 0-1 jaar, Overdrachtsbericht Kinderen 1-18 jaar as PUSH messages.~~

	/TODO		/TODO

Stephan Opdenberg: /* Structure of the Aanmeldbericht (complete) */

2020-04-09T07:56:58Z

Structure of the Aanmeldbericht (complete)

← Oudere versie		Versie van 9 apr 2020 07:56
Regel 231:		Regel 231:
	===Expected response===		===Expected response===
	The document Bundle should be processed as a [http://hl7.org/fhir/STU3/http.html#transaction transaction] by the receiving XIS. See [[#Processing documents]] for more information.		The document Bundle should be processed as a [http://hl7.org/fhir/STU3/http.html#transaction transaction] by the receiving XIS. See [[#Processing documents]] for more information.
	==Structure of the Aanmeldbericht (complete)==		==Structure of the Aanmeldbericht phase 2 (complete)==
	The Aanmeldbericht consists of multiple FHIR resources, which are assembled into a FHIR document. See [[#Creating documents]] for information on how to assemble this document.		The Aanmeldbericht consists of multiple FHIR resources, which are assembled into a FHIR document. See [[#Creating documents]] for information on how to assemble this document.

Regel 357:		Regel 357:
	\| -		\| -
	\|}		\|}

	=FHIR Documents=		=FHIR Documents=
	Both the Aanmeldbericht and the Overdrachtsbericht are sent as a [https://www.hl7.org/fhir/STU3/documents.html FHIR Document]. A document is a FHIR Bundle that assembles all relevant resources that need to be exchanged, together with a [https://www.hl7.org/fhir/STU3/composition.html Composition resource] that summarizes and references all these resources.		Both the Aanmeldbericht and the Overdrachtsbericht are sent as a [https://www.hl7.org/fhir/STU3/documents.html FHIR Document]. A document is a FHIR Bundle that assembles all relevant resources that need to be exchanged, together with a [https://www.hl7.org/fhir/STU3/composition.html Composition resource] that summarizes and references all these resources.

Stephan Opdenberg op 9 apr 2020 om 07:56

2020-04-09T07:56:13Z

← Oudere versie		Versie van 9 apr 2020 07:56
Regel 1:		Regel 1:
	{{#customtitle:eOverdracht Proeftuin FHIR Implementation Guide}}		{{#customtitle:eOverdracht Proeftuin phase 2 FHIR Implementation Guide}}
	{{IssueBox\|Work in progress - See [[vpk:V3.1_FHIR_eOverdracht_Proeftuin\|official publication]] here.}}		{{IssueBox\|Work in progress - See [[vpk:V3.1_FHIR_eOverdracht_Proeftuin\|official publication]] here.}}
	=Introduction=		=Introduction=