vpk:Vprepub-4.0 FHIR eOverdracht - Bewerkingsoverzicht

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

2026-04-21T11:47:59Z

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

Micha Drielinger: EOVDR-867: kleine wijziging

2026-04-21T09:53:09Z

EOVDR-867: kleine wijziging

Mik de Jong: EOVDR-758: all 4.0 mentions have been changed to "minor release 4.0"

2026-04-20T11:00:14Z

EOVDR-758: all 4.0 mentions have been changed to "minor release 4.0"

Mik de Jong: EOVDR-754: Text has been added that the 4.0 does not use the negotiation workflow.

2026-04-20T10:58:51Z

EOVDR-754: Text has been added that the 4.0 does not use the negotiation workflow.

Mik de Jong: EOVDR-775: The Notifications paragraph has been provided with explanation about the error handlig and happy flow.

2026-04-20T10:57:37Z

EOVDR-775: The Notifications paragraph has been provided with explanation about the error handlig and happy flow.

Mik de Jong: EOVDR-765: Added a note in the overview of workflow and structure about the scope with the happy flow.

2026-04-20T10:56:06Z

EOVDR-765: Added a note in the overview of workflow and structure about the scope with the happy flow.

Mik de Jong: EOVDR-721: Small adjustments in hyperlink

2025-06-02T11:56:27Z

EOVDR-721: Small adjustments in hyperlink

Mik de Jong: Create prepub environment from vpk:V4.0

2025-03-12T12:29:28Z

Create prepub environment from vpk:V4.0

Mik de Jong: Gekopieerd van vpk:V4.0 FHIR eOverdracht, versie 222794

2025-03-12T12:29:22Z

Gekopieerd van vpk:V4.0 FHIR eOverdracht, versie 222794

Niek van Galen: Beveiligde "vpk:V4.0 FHIR eOverdracht": Protect production page from accidental edits ([Bewerken=Alleen beheerders toestaan] (vervalt niet) [Hernoemen=Alleen beheerders toestaan] (vervalt niet))

2024-07-23T09:16:58Z

Beveiligde "vpk:V4.0 FHIR eOverdracht": Protect production page from accidental edits ([Bewerken=Alleen beheerders toestaan] (vervalt niet) [Hernoemen=Alleen beheerders toestaan] (vervalt niet))

@@ Regel 157: / Regel 157: @@
 ==HCIM profiles==
-The following table lists the FHIR profiles that implement the HCIMs used within eOverdracht.
+The following table lists the FHIR profiles that implement the HCIMs used within eOverdracht. 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:V4.0_Ontwerp_eOverdracht#Transacties_&_Transactiegroepen | the transactiondataset of the functional design]].
 {| class="wikitable"
 !style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;  background-color: #E3E3E3 width:400px" | HCIM Name

@@ Regel 76: / Regel 76: @@
 ===Composition invocations===
-The receiving XIS MAY use either of the following mechanism for retrieving the individual FHIR resources referenced in the Compostion resource.
+The receiving XIS MAY use either of the following mechanism for retrieving the individual FHIR resources referenced in the Composition resource.
 ; As a Document: The receiving XIS uses the {{fhir|$document}} operation to retrieve both the Composition ''and'' all referenced resources as a single document Bundle.<br/><pre>GET [base]/Composition/[Composition.id]/$document</pre>''Note:'' the Compositions list just the resources that act as the entry point for the various concepts in the eOverdracht transactions, but each of these referenced resources may further refer other resources not listed there. The sending system SHALL produce a complete Bundle containing not only the resources listed directly in the Composition, but all the indirectly referenced resources as well.
-; Individual requests: The receiving XIS first retrieves the Composition resource<br/><pre>GET [base]/Compositon/[Composition.id]</pre>Then the necessary other resources referenced can be fetched using a <code>GET</code> interaction.
+; Individual requests: The receiving XIS first retrieves the Composition resource<br/><pre>GET [base]/Composition/[Composition.id]</pre>Then the necessary other resources referenced can be fetched using a <code>GET</code> interaction.
 The sending XIS SHALL support both mechanisms.
@@ Regel 118: / Regel 118: @@
 | colspan=2 | Send confirmation of nursing handoff
+|
-* Recieving XIS updates Task:
+* Receiving XIS updates Task:
 ** {{fhir|Task.status}} = {{term|completed}}
 |}
@@ Regel 127: / Regel 127: @@
 | [[Bestand:2024-04-12-eOverdracht-TransferPhase.svg|none|top]]
 |}
-The initial eOverdracht minor release 4.0 has to be carried out without the negotiation phase, the sending XIS will create the Task instance with {{fhir|Task.status}} already set to {{term|in-progress}} and {{fhir|Task.input:nursingHandoff}} populated. The full eOverdracht Task workflow will be supported but is out of scope for the minor release 4.0.
+The initial eOverdracht minor release 4.0. has to be carried out without the negotiation phase, the sending XIS will create the Task instance with {{fhir|Task.status}} already set to {{term|in-progress}} and {{fhir|Task.input:nursingHandoff}} populated. The full eOverdracht Task workflow will be supported but is out of scope for the minor release 4.0.
 ===Brokers===

@@ Regel 4: / Regel 4: @@
 =Introduction=
-This is the implementation guide for the information standard eOverdracht, version 4.0. This standard is described in [[vpk:Vprepub-4.0_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, minor release 4.0. This standard is described in [[vpk:Vprepub-4.0_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 127: / Regel 127: @@
 | [[Bestand:2024-04-12-eOverdracht-TransferPhase.svg|none|top]]
 |}
-The initial eOverdracht 4.0 version has to be carried out without the negotiation phase, the sending XIS will create the Task instance with {{fhir|Task.status}} already set to {{term|in-progress}} and {{fhir|Task.input:nursingHandoff}} populated. The full eOverdracht Task workflow will be supported but is out of scope for the 4.0 version.
+The initial eOverdracht minor release 4.0 has to be carried out without the negotiation phase, the sending XIS will create the Task instance with {{fhir|Task.status}} already set to {{term|in-progress}} and {{fhir|Task.input:nursingHandoff}} populated. The full eOverdracht Task workflow will be supported but is out of scope for the minor release 4.0.
 ===Brokers===

@@ Regel 95: / Regel 95: @@
 ==Using Task to manage the workflow==
-The Task is the main entry point for the eOverdracht transactions. The eOverdracht workflow starts with the retrieval of a new Task instance by the receiving XIS, and all subsequent steps in the workflow are mediated by updates to this Task instance.
+The Task is the main entry point for the eOverdracht transactions. The eOverdracht workflow starts with the retrieval of a new Task instance by the receiving XIS, and all subsequent steps in the workflow are mediated by updates to this Task instance. Please note that the minor release 4.0 does not make use of the negotiation workflow. The negotiation workflow is part of the [[vpk:VOntwerpversie_FHIR_eOverdracht#Using_Task_to_manage_the_workflow|development version of the extended eOverdracht]].
 The eOverdracht transactions are mapped to FHIR in the following way:

@@ Regel 69: / Regel 69: @@
    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.
+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.0.
 ==Use of the Composition resource==

@@ Regel 39: / Regel 39: @@
 ==Overview==
-Although the eOverdracht is currently limited to the transfer of the nursing handoff, the ultimate vision is to have a workflow which may include the negotiation of the transfer of the patient. For this reason, a Task resource is used as the entry point for all data exchanges (see [[#Use of the Composition resource]]).
+Although the eOverdracht is currently limited to the transfer of the nursing handoff, the ultimate vision is to have a workflow which may include the negotiation of the transfer of the patient. For this reason, a Task resource is used as the entry point for all data exchanges (see [[#Use of the Composition resource]]). Please note that this minor release 4.0 is limited to the happy flow only. Unhappy flow and error handling is not part of the information standard, except for [[FHIR:V1.0_FHIR_IG_STU3#Handling_errors|error handling]] in FHIR.
 ==Task==

@@ Regel 43: / Regel 43: @@
 ==Task==
 ===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}} profile. This profile SHALL be used for the eOverdracht workflow.
+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|pkgVersion={{VersieInfo|nictiz.fhir.nl.stu3.eoverdracht|release=V4.0}}|title=eOverdracht-Task}} 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 1: / Regel 1: @@
 {{DISPLAYTITLE:eOverdracht {{VersieInfo|eOverdracht|release=V4.0}} FHIR Implementation Guide}}
 __NUMBEREDHEADINGS__
 =Introduction=
-This is the implementation guide for the information standard eOverdracht, version 4.0. This standard is described in [[vpk:V4.0_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, version 4.0. This standard is described in [[vpk:Vprepub-4.0_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 141: / Regel 142: @@
 '''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.0_Testen|test scenarios]] can be found on [https://github.com/Nictiz/Nictiz-testscripts/tree/main/src/eOverdracht-4-0/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.0_Testen|test scenarios]] can be found on [https://github.com/Nictiz/Nictiz-testscripts/tree/main/src/eOverdracht-4-0/Test/_reference/resources Github].
 ==Infrastructure profiles==
 The following table lists the FHIR profiles that should be used for the infrastructural parts of the eOverdracht information standard. The mapping to the functional data elements is given using the mapping within these profiles.

← Oudere versie	Versie van 12 mrt 2025 om 12:29
(geen verschil)

← Oudere versie	Versie van 23 jul 2024 om 09:16
(geen verschil)