eOverdracht 4.0-rc.20 FHIR Implementation Guide
- 1 Introduction
- 2 Actors involved
- 3 Workflow and message structure
- 4 FHIR profiles
This is the implementation guide for the information standard eOverdracht, version 4.0. This standard is described in this functional specification and implemented here using 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 general FHIR Implementation Guide apply. In particular, the reader should take note of the Use case overarching principles and the use of FHIR packages.
2 Actors involved
|Actors||Systems||FHIR Capability Statements|
|Sending organization||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||CapabilityStatement: Sending XIS||FHIR requirements for sending XIS|
|Receiving organization||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||CapabilityStatement: Receiving XIS||FHIR requirements for receiving XIS|
3 Workflow and message structure
The use cases within eOverdracht are not isolated, but form a workflow that may include the negotiation of the transfer of the patient, and ends with the transfer of the medical record. In FHIR, this is handled by using a Task resource. This resource tracks the worflow (see #Workflow) and acts as the entry point for all data exchanges (see #Use of the Composition resource) for the transfer of care for a patient.
3.2.1 Task requirements
The requirements for the Task resource in the eOverdracht context are specified using the http://nictiz.nl/fhir/StructureDefinition/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.
Both the sending and the receiving XIS SHALL monitor the Task resource for changes. It is expected that the sending XIS will use a notification mechanism to inform the receiving XIS of creation or updates of the Task (see #Notifications), but the receiving XIS could use a polling mechanism as well.
For each combination of sending and receiving XIS, a dedicated instance of the Task resource SHALL be used for each transfer situation. This is true even when the sending XIS wants to send the same request to multiple parties. The reason for this is that the Task status is used to negotiate the transfer of care, so it cannot be used simultaneously for multiple recipients.
3.2.2 Task invocations
The receiving XIS can query the Task at the sending XIS by using the Task.id which is communicated in the notification:
Note: It is up to the receiving XIS to determine if this is a new Task or an update to an existing Task, and if it is an update, what the change entails.
The receiving XIS can update a Task hosted by the sending XIS using a PUT operation:
The body should be the original Task with the needed modifications. The sending XIS SHOULD check the update for errors and inconsistencies. If the update is rejected, the sending XIS SHALL response with a HTTP 422 status code and an OperationOutcome detailing the problem.
It is expected that the sending XIS will notify the receiving XIS when a new Task is created or when an existing Task is updated. Although the notification mechanism is out of scope for the eOverdracht information standard, the notification SHALL communicate the
Task.id to the receiving XIS.
A straightforward implementation for this notification mechanism is for the notifying party to make an empty POST request combined with an authorization header on a pre-determined endpoint at the party that should be notified, with the
Task.id appended as path component:
The notified party is expected to respond with HTTP status code 202 Accepted to inform the notifying party that the notification was successfully received.
3.3 Use of the Composition resource
The advance notice (Aanmeldbericht) and the (three variants of) the nursing handoff (Overdrachtsbericht) are mainly built up of individual FHIR resources, selected by the sending organization to form a coherent set of information relevant to the receiving organization. The bulk of these resources are not referenced directly from the Task. Instead, the Task references a Composition resource which in turn assembles the references to all individual FHIR resources. For this purpose, the Composition profiles described in #FHIR profiles SHALL be used.
3.3.1 Composition invocations
The receiving XIS MAY use either of the following mechanism for retrieving the individual FHIR resources referenced in the Compostion resource.
- As a Document
- The receiving XIS uses the
$documentoperation to retrieve both the Composition and all referenced resources as a single document Bundle.
GET [base]/Composition/[Composition.id]/$documentNote: 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
GET [base]/Compositon/[Composition.id]Then the necessary other resources referenced can be fetched using a
The sending XIS SHALL support both mechanisms.
3.3.2 Exchanging data as unstructured text
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.
- This document is added to the Composition resource representing the advance notice or the nursing handoff, in the following way:
- An additional
Composition.sectionis created, with
.section.codeset to SNOMED CT/703852005 (Narrative comment section).
- In this section, there is a single
.section.entry, and it refers to a DocumentReference resource.
- This DocumentReference resource references the PDF/A document containing the unstructured text.
- An additional
The use of the DocumentReference resource allows the sender to specify additional metadata about the document, if needed. It also prevents that the PDF/A is directly included when the Composition is requested using the
$document operation, which could lead to unexpected large data volumes.
3.4 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 worflow are mediated by updates to this Task instance.
The eOverdracht transactions are mapped to FHIR in the following way:
|Send advance notice||
|Send response to advance notice|
|Propose alternate date||
|Respond to alternate proposed date|
|Accept alternate proposed date:
(process starts over again)
|Reject alternate proposed date:||
|Send nursing handoff||
|Send confirmation of nursing handoff||
The following sequence diagrams illustrate the relevant exchanges and state transitions:
|Normal flow||Negotiate alternative date|
3.4.1 Partial workflow
When the transfer has to be carried out without the negotiation phase, the sending XIS will create the Task instance with
Task.status already set to in-progress and
The use of a broker to find an available healthcare provider for the patient transfer fall outside the scope of the eOverdracht information standard. However, it is possible to start the workflow without knowing the receiving organization, which allows for the use of a broker. In this situation, for the sending XIS the broker acts as a receiving XIS, and for the receiving XIS the broker acts as a sending XIS.
Task.input:nursingHandoff is populated with the nursing handoff Composition,
Task.owner MUST be populated with the receiving organization.
4 FHIR profiles
eOverdracht uses the FHIR Packaging mechanism. This conveniently bundles all profiles, terminology, example material and other conformance resources you need into a single archive, which can be downloaded or installed using the appropriate FHIR tooling. This version of the information standard uses the following packages:
Note: packages use 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.
4.1 Example resources
4.2 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.
|HCIM Name||FHIR profile|
|Composition for advance notice (Aanmeldbericht)||http://nictiz.nl/fhir/StructureDefinition/eOverdracht-AdvanceNotice|
|Composition for nursing handoff adults (Overdrachtsbericht volwassenen)||http://nictiz.nl/fhir/StructureDefinition/eOverdracht-NursingHandoff-Adults|
|Composition for nursing handoff childcare 0-1 yo (Overdrachtsbericht kinderen 0-1 jaar)||http://nictiz.nl/fhir/StructureDefinition/eOverdracht-NursingHandoff-Childcare-0-1yo|
|Composition for nursing handoff childcare 1-18 yo (Overdrachtsbericht kinderen 1-18 jaar)||http://nictiz.nl/fhir/StructureDefinition/eOverdracht-NursingHandoff-Childcare-1-18yo|
4.3 HCIM profiles
The following table lists the FHIR profiles that implement the HCIMs used within eOverdracht.