vpk:Vprepub-4.2 FHIR eOverdracht - Bewerkingsoverzicht

Mik de Jong: EOVDR-269: Added explanation on administeringSystem extension

2026-09-24T14:29:39Z

EOVDR-269: Added explanation on administeringSystem extension

Mik de Jong: EOVDR-933: Edited recieving to receiving

2026-09-24T12:46:46Z

EOVDR-933: Edited recieving to receiving

Mik de Jong: EOVDR-949: Removed lifeStance from HCIM profiles

2026-08-10T11:11:39Z

EOVDR-949: Removed lifeStance from HCIM profiles

Mik de Jong: EOVDR-954: In paragraaf 3.2.3 ‘Notifications’ is een toelichting toegevoegd over error handling.

2026-08-10T11:06:21Z

EOVDR-954: In paragraaf 3.2.3 ‘Notifications’ is een toelichting toegevoegd over error handling.

Mik de Jong: EOVDR-939: In het Technisch Ontwerp is toelichting gegeven in de banner van hoofdstuk 4 “FHIR Profiles“ over de versionering van packages.

2026-08-10T11:04:33Z

EOVDR-939: In het Technisch Ontwerp is toelichting gegeven in de banner van hoofdstuk 4 “FHIR Profiles“ over de versionering van packages.

Mik de Jong: EOVDR-937: In het Technisch Ontwerp, hoofdstuk “Introduction“ is een toelichting gegeven op de commit strategie van Nictiz over het gebruik van ticketnummers

2026-08-10T11:01:18Z

EOVDR-937: In het Technisch Ontwerp, hoofdstuk “Introduction“ is een toelichting gegeven op de commit strategie van Nictiz over het gebruik van ticketnummers

Mik de Jong: EOVDR-935: Het overbodige vraagteken is verwijderd bij het hoofdstuk 'Actors Involved'

2026-08-10T10:58:48Z

EOVDR-935: Het overbodige vraagteken is verwijderd bij het hoofdstuk 'Actors Involved'

Mik de Jong: EOVDR-934: In paragraaf 3.2.1 van het Technisch ontwerp is toelichting gegeven op wat verschil is tussen een 'new' en 'update' Task.

2026-08-10T10:55:59Z

EOVDR-934: In paragraaf 3.2.1 van het Technisch ontwerp is toelichting gegeven op wat verschil is tussen een 'new' en 'update' Task.

Mik de Jong: EOVDR-763: Added extra sentence on explanation on HCIM profiles paragraph

2026-04-23T06:58:11Z

EOVDR-763: Added extra sentence on explanation on HCIM profiles paragraph

Mik de Jong: EOVDR-763: Added extra sentence on explanation on HCIM profiles paragraph

2026-04-21T11:46:12Z

EOVDR-763: Added extra sentence on explanation on HCIM profiles paragraph

@@ Regel 264: / Regel 264: @@
 | rowspan="2" | Infuus
 | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Infusion|nictiz.fhir.nl.stu3.zib2017|pkgVersion={{VersieInfo|nictiz.fhir.nl.stu3.zib2017|release=V4.2}}}}
-| rowspan="2" |
+| rowspan="2" | the extension LumenOrLine.AdministeringSystem is not supported; see [[vpk:V4.2_Ontwerp_eOverdracht#Known_issues|the Known Issues on the Functional Design page]] for more information
 |-
 | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Infusion-Product|nictiz.fhir.nl.stu3.zib2017|pkgVersion={{VersieInfo|nictiz.fhir.nl.stu3.zib2017|release=V4.2}}}}

@@ Regel 122: / Regel 122: @@
 | colspan=2 | Send confirmation of nursing handoff
+|
-* Recieving XIS updates Task:
+* Receiving XIS updates Task:
 ** {{fhir|Task.status}} = {{term|completed}}
 |}

@@ Regel 273: / Regel 273: @@
 |-
 | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LegalSituation-Representation|nictiz.fhir.nl.stu3.zib2020-preadopt|pkgVersion={{VersieInfo|nictiz.fhir.nl.stu3.zib2020-preadopt|release=V4.2}}}} (Not finalized)
 |-
 | Lichaamsgewicht

@@ Regel 73: / Regel 73: @@
    POST [base]/[Task.id]
-The notified party is expected to respond with HTTP status code ''202 Accepted'' to inform the notifying party that the notification was successfully received. Please note that the unhappy flow (such as timeouts, error handling) are not in scope within the minor release 4.2.
+The notified party is expected to respond with HTTP status code ''202 Accepted'' to inform the notifying party that the notification was successfully received. Please note that the unhappy flow (such as timeouts, error handling) are not in scope within the minor release 4.2, except for [[FHIR:V1.0_FHIR_IG_STU3#Handling_errors|error handling]] in FHIR.
 ==Use of the Composition resource==

@@ Regel 143: / Regel 143: @@
 * [https://simplifier.net/packages/nictiz.fhir.nl.stu3.zib2017 nictiz.fhir.nl.stu3.zib2017, version 2.1.0 or compatible]
-'''Note''': packages use [https://semver.org/ Semantic Versioning]. Other versions can be used at will as long as they have the same ''major.minor'' number or a ''minor'' number higher than the stated version.}}
+'''Note''': packages use [https://semver.org/ Semantic Versioning]. Other versions can be used at will as long as they have the same ''major.minor'' number or a ''minor'' number higher than the stated version. The package version may differ from the versioning of the information standard. Changes to the information standard will not always result in a version increment for the package. As a result, the package version may differ from the version of the information standard.}}
 ==Example resources==
 Examples for the profiles above can be found in the FHIR packages [[#FHIR profiles|defined above]]. Additionally, instances for the [[vpk:Vprepub-4.2_Testen|test scenarios]] can be found on [https://github.com/Nictiz/Nictiz-testscripts/tree/main/src/eOverdracht-4-2/Test/_reference/resources Github].

← Oudere versie		Versie van 10 aug 2026 om 11:01
Regel 7:		Regel 7:

	Apart from this document, the guidelines as specified in [[FHIR:V1.0 FHIR IG STU3\|general FHIR Implementation Guide]] apply. In particular, the reader should take note of the [[FHIR:V1.0_FHIR_IG_STU3#Use_case_overarching_principles\|Use case overarching principles]] and the use of [[FHIR:V1.0_FHIR_IG_STU3#FHIR_Packages\|FHIR packages]].		Apart from this document, the guidelines as specified in [[FHIR:V1.0 FHIR IG STU3\|general FHIR Implementation Guide]] apply. In particular, the reader should take note of the [[FHIR:V1.0_FHIR_IG_STU3#Use_case_overarching_principles\|Use case overarching principles]] and the use of [[FHIR:V1.0_FHIR_IG_STU3#FHIR_Packages\|FHIR packages]].
		+
		+	Please note that all FHIR fixtures regarding testscripts are always in the 'main' branch. It is possible to look up the changes in the [[vpk:Vprepub-4.2_Ontwerp eOverdracht\|release notes]]. These correspond with tickets that have been implmented in the 'main' branch on github.

	=Actors involved=		=Actors involved=

@@ Regel 22: / Regel 22: @@
 |-
 | Sending organization
-| The organization or health care professional(?) at the organization that wants to transfer the care of a patient
+| The organization or health care professional at the organization that wants to transfer the care of a patient
 | Sending XIS
 | Healthcare information system of the sending organization
@@ Regel 29: / Regel 29: @@
 |-
 | Receiving organization
-| The organization or health care professional(?) at the organization that the sending organization wants to transfer the care of a patient to
+| The organization or health care professional at the organization that the sending organization wants to transfer the care of a patient to
 | Receiving XIS
 | Healthcare information system of the receiving organization

@@ Regel 1: / Regel 1: @@
 {{DISPLAYTITLE:eOverdracht {{VersieInfo|eOverdracht|release=V4.2}} FHIR Implementation Guide}}
 __NUMBEREDHEADINGS__
 =Introduction=
-This is the implementation guide for the information standard eOverdracht. This standard is described in [[vpk:V4.2_Ontwerp eOverdracht|this functional specification]] and implemented here using [https://www.hl7.org/fhir/stu3/ FHIR(STU3) HL7 FHIR, STU3]. This implementation guide assumes that the reader is familiar with this FHIR version.
+This is the implementation guide for the information standard eOverdracht. This standard is described in [[vpk:Vprepub-4.2_Ontwerp eOverdracht|this functional specification]] and implemented here using [https://www.hl7.org/fhir/stu3/ FHIR(STU3) HL7 FHIR, STU3]. This implementation guide assumes that the reader is familiar with this FHIR version.
 Apart from this document, the guidelines as specified in [[FHIR:V1.0 FHIR IG STU3|general FHIR Implementation Guide]] apply. In particular, the reader should take note of the [[FHIR:V1.0_FHIR_IG_STU3#Use_case_overarching_principles|Use case overarching principles]] and the use of [[FHIR:V1.0_FHIR_IG_STU3#FHIR_Packages|FHIR packages]].
@@ Regel 43: / Regel 44: @@
 ===Task requirements===
 The requirements for the Task resource in the eOverdracht context are specified using the {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-Task|nictiz.fhir.nl.stu3.eOverdracht|eOverdracht-Task|pkgVersion={{VersieInfo|nictiz.fhir.nl.stu3.eoverdracht|release=V4.2}}}} profile. This profile SHALL be used for the eOverdracht workflow.
 The Task instance SHALL be hosted on the server of the sending XIS. Both the sending and the receiving XIS need to be able to update the Task. The sending XIS MAY use business rules to reject an update, for example if invalid status change is used.
@@ Regel 85: / Regel 88: @@
 The information standard requires that all information described is exchanged in a structured way, according to the FHIR profiles described on this page. However, some systems are not able to support the full extent of the standard yet and may need to send part of the data as formatted text. The following implementation advice provides guidance on how systems with such a need may accomplish this exchange.
-* All unstructured (textual data) is collected in one single PDF/A document. In every data exchange, these will be included, as described in [[vpk:V4.2_Ontwerp_eOverdracht#Gegevensuitwisseling_in_ongestructureerde_vorm|FO paragraph 2.2.4.4.]]
+* All unstructured (textual data) is collected in one single PDF/A document. In every data exchange, these will be included, as described in [[vpk:Vprepub-4.2_Ontwerp_eOverdracht#Gegevensuitwisseling_in_ongestructureerde_vorm|FO paragraph 2.2.4.4.]]
 * This document is added to the Composition resource representing the nursing handoff, in the following way:
 ** An additional {{fhir|Composition.section}} is created, with {{fhir|.section.code}} set to SNOMED CT/{{term|703852005}} (Narrative comment section).
@@ Regel 140: / Regel 143: @@
 '''Note''': packages use [https://semver.org/ Semantic Versioning]. Other versions can be used at will as long as they have the same ''major.minor'' number or a ''minor'' number higher than the stated version.}}
 ==Example resources==
-Examples for the profiles above can be found in the FHIR packages [[#FHIR profiles|defined above]]. Additionally, instances for the [[vpk:V4.2_Testen|test scenarios]] can be found on [https://github.com/Nictiz/Nictiz-testscripts/tree/main/src/eOverdracht-4-2/Test/_reference/resources Github].
+Examples for the profiles above can be found in the FHIR packages [[#FHIR profiles|defined above]]. Additionally, instances for the [[vpk:Vprepub-4.2_Testen|test scenarios]] can be found on [https://github.com/Nictiz/Nictiz-testscripts/tree/main/src/eOverdracht-4-2/Test/_reference/resources Github].
 ==Infrastructure profiles==

@@ Regel 156: / Regel 156: @@
 ==HCIM profiles==
-The following table lists the FHIR profiles that implement the HCIMs used within eOverdracht. More information about which HCIMs and rules have been implemented can be found here in [[vpk:Vprepub-4.2_Ontwerp_eOverdracht#Transacties_&_Transactiegroepen | the transactiondataset of the functional design]].
+The following table lists the FHIR profiles that implement the HCIMs used within eOverdracht.
 {| class="wikitable"
 !style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;  background-color: #E3E3E3 width:400px" | HCIM Name