vpk:Vdraft FHIR eOverdracht Proeftuin: verschil tussen versies

Uit informatiestandaarden
Naar navigatie springen Naar zoeken springen
Regel 15: Regel 15:
 
{{NoteBox|Basic [https://www.hl7.org/fhir/stu3/ FHIR(STU3)] knowledge is required.}}
 
{{NoteBox|Basic [https://www.hl7.org/fhir/stu3/ FHIR(STU3)] knowledge is required.}}
  
−
==Actors==
+
=Use case 1A: Send Overdrachtsbericht volwassenen (PUSH) =
−
{| class="wikitable" "cellpadding="10"
 
−
! style="text-align:left;"| '''Transaction group'''
 
−
! style="text-align:left;"| '''Transaction'''
 
−
! style="text-align:left;"| '''Actor'''
 
−
! style="text-align:left;"| '''Role'''
 
−
|-
 
−
|style="background-color: white;vertical-align:top;" rowspan="2"|Send eOverdracht Aanmeldbericht(PUSH)
 
−
|style="background-color: white;vertical-align:top;"|Send aanmeldbericht request
 
−
|style="background-color: white;vertical-align:top;"|Healthcare professional (using a XIS)
 
−
|style="background-color: white;vertical-align:top;"|Sends aanmeldbericht to the receiving XIS
 
−
|-
 
−
|style="background-color: white;vertical-align:top;"|Send aanmeldbericht response
 
−
|style="background-color: white;vertical-align:top;"|Receiving XIS
 
−
|style="background-color: white;vertical-align:top;"|Sends acknowledgement message to sending XIS
 
−
|-
 
−
|style="background-color: white;vertical-align:top;"rowspan="2"|Send eOverdracht Overdrachtbericht(PUSH)
 
−
|style="background-color: white;vertical-align:top;"|Send overdrachtbericht
 
−
|style="background-color: white;vertical-align:top;"|Healthcare professional (using a XIS)
 
−
|style="background-color: white;vertical-align:top;"|Sends overdrachtbericht to the receiving XIS
 
−
|}
 
−
 
 
−
=Invocations=
 
−
==Send Aanmeldbericht==
 
−
===Trigger events===
 
−
This transaction is invoked when the patiënt is ready for transfer, and the sending XIS wants to confirm a recieving XIS.
 
−
 
 
−
===Message Semantics===
 
−
Both the Aanmeldbericht as the eOverdrachtbericht are sent as a [https://www.hl7.org/fhir/STU3/documents.html FHIR Document]. To create this document, a FHIR Composition resource should be created according to the relevant [https://simplifier.net/NictizSTU3-Zib2017/~resources?text=eoverdracht&category=Profile&corebasetype=Composition Composition] profiles.
 
−
 
 
−
The Composition resources reference each of the relevant resources included in the eOverdrachtbericht. The Composition resource and the relevant resources are subsequently assembled into a FHIR [http://hl7.org/fhir/STU3/bundle.html Bundle] resource which ''Bundle.type'' set to ''document''. The Composition resource should be the first entry in the Bundle.
 
−
 
 
−
For the Bundle, the following rules apply:
 
−
* The Bundle resource SHALL include all the resources listed as described in the different use cases, each in a ''separate Bundle.entry''.
 
−
* The resources in the message SHALL be a valid instances of these profiles listed in the use cases.
 
−
* All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.
 
−
* The Bundle SHOULD include the resources that are linked from the included resources
 
−
 
 
−
{{NoteBox|A FHIR Document is an immutable statement which can't be updated once it's created, it can only be superseded by a new Document. Updating falls outside the scope of the current design.}}
 
−
 
 
−
The Send eOverdrachtbericht transaction is an HTTP POST method on the target XIS's base:
 
−
POST [base] {?_format=[mime-type]}
 
−
where the body of the POST request is the assembled Bundle.
 
−
 
 
−
====Expected actions====
 
−
The document Bundle should be processed as a [http://hl7.org/fhir/STU3/http.html#transaction transaction] by the receiving XIS and each ''Bundle.entry'' should be treated as a ''create'' interaction for the ''Bundle.entry.resource''.
 
−
 
 
−
When the resource syntax or data is incorrect or invalid and cannot be used to create a new resource, or when the server rejects the content of the resource because of business rules, it should perform a rollback of the creation of any previous entries and send the appropriate response (see below).
 
−
 
 
−
==eOverdrachtbericht response==
 
−
====Trigger events====
 
−
The target XIS completed processing of the Send eOverdrachtbericht transaction.
 
−
 
 
−
====Message semantics====
 
−
The target XIS responds to the Send eOverdrachtbericht transaction with an HTTP Response, where:
 
−
* The status code SHALL be set appropriate to the processing outcome. When the resource syntax or data is incorrect or invalid, and cannot be used to create a new resource, the server returns a 400 Bad Request HTTP status code. When the server rejects the content of the resource because of business rules, the server returns a 422 Unprocessable Entity error HTTP status code. Additional HTTP status code may be used if more appropriate.
 
−
* On success, The server returns a 201 Created HTTP status code, and SHALL also return a Location header which contains the new Logical Id and Version Id of the created resource version.
 
−
* On failure, the response body SHOULD be set to a FHIR [http://hl7.org/fhir/STU3/operationoutcome.html OperationOutcome] resource with detailed error messages describing the reason for the error, and perform a rollback of the creation of any previous entries.
 
−
 
 
−
A client may use the returned Bundle to track the outcomes of processing the entry, and the identities assigned to the resources by the server. Each entry element SHALL contain a response element which details the outcome of processing the entry - the HTTP status code, and the location and ETag header values, which are used for identifying and versioning the resources. In addition, a resource may be included in the entry, as specified by the Prefer header.
 
−
 
 
−
=Use case 1A:Send Overdrachtsbericht volwassenen (PUSH) =
 
 
==Introduction==
 
==Introduction==
 
The Send Overdrachtsbericht scenario is used by the sending XIS to send the relevant data for the patient care to the receiving XIS. The structure of the eventual scenario is described in the functional design and additionally in [[vpk:V3.1_Opbouw_eOverdracht_volwassenen|Opbouw eOverdracht Overdrachtsbericht]]. For the pilot a limited subset is implemented.
 
The Send Overdrachtsbericht scenario is used by the sending XIS to send the relevant data for the patient care to the receiving XIS. The structure of the eventual scenario is described in the functional design and additionally in [[vpk:V3.1_Opbouw_eOverdracht_volwassenen|Opbouw eOverdracht Overdrachtsbericht]]. For the pilot a limited subset is implemented.
Regel 280: Regel 219:
 
| Should be used to send unstructured PDF data.
 
| Should be used to send unstructured PDF data.
 
|}
 
|}
−
 
−
==Proeftuin eOverdracht phase 2==
 
−
===Introduction===
 
−
In phase 2 of the proeftuin, participants will expand on the implementations made in phase 1. This phase will encompass the complete aanmeldbericht (as shown in the table below) and an extension on the overdrachtbericht.
 
−
 
−
===Structure of the Aanmeldbericht phase 2 (complete)===
 
−
 
−
The Aanmeldbericht consists of multiple FHIR resources, which are assembled into a FHIR [http://hl7.org/fhir/STU3/bundle.html Bundle]. The table below lists the FHIR StructureDefinitions that are applicable for the pilot implementation of the 'Aanmeldbericht' transactions. The Phase Two aanmeldbericht implements the complete aanmeldbericht as described in the functional design.
 
−
 
−
{| class="wikitable" style="horizontal-align: right"
 
−
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;  background-color: #E3E3E3 width:400px" | Section
 
−
!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:50px" | FHIR resource
 
−
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;  background-color: #E3E3E3 width:50px" | HCIM name
 
−
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;  background-color: #E3E3E3 width:50px" | HCIM version
 
−
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;  background-color: #E3E3E3 width:50px" | Remarks
 
−
|-
 
−
| -
 
−
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-aanmeldbericht|eOverdracht aanmeldbericht}}
 
−
| Composition
 
−
| -
 
−
| -
 
−
| Declaration of the Send Aanmeldbericht transaction.
 
−
|-
 
−
| Datum overplaatsing
 
−
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-TransferDate|eOverdracht-TransferDate}}
 
−
| -
 
−
| -
 
−
| -
 
−
| DateTime extension used in eOverdracht composition profiles
 
−
|-
 
−
| rowspan="3"|Persoonsgegevens
 
−
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|nl-core-patient}}
 
−
| Patient
 
−
| Patient
 
−
| v3.1(2017NL)
 
−
| -
 
−
|-
 
−
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Payer|zib-Payer}}
 
−
| Coverage
 
−
| Betaler
 
−
| v3.1(2017NL)
 
−
| -
 
−
|-
 
−
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nl-core-relatedperson}}
 
−
| RelatedPerson
 
−
| Contactpersoon
 
−
| v3.1(2017NL)
 
−
| -
 
−
|-
 
−
| Sturende organisatie
 
−
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
 
−
| rowspan="2"| Organization
 
−
| rowspan="2"| Zorgaanbieder
 
−
| rowspan="2"| v3.1.1(2017NL)
 
−
| rowspan="2"| -
 
−
|-
 
−
| Ontvangende organisatie
 
−
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
 
−
|-
 
−
| Medische diagnose
 
−
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
 
−
| Condition
 
−
| Probleem
 
−
| v4.1(2017NL
 
−
| -
 
−
|-
 
−
|-
 
−
| Voorgeschiedenis
 
−
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
 
−
| Condition
 
−
| Probleem
 
−
| v4.1(2017NL
 
−
| -
 
−
|-
 
−
| Let op
 
−
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Alert|zib-Alert}}
 
−
| Flag
 
−
| Alert
 
−
| v3.2(2017NL)
 
−
| -
 
−
|-
 
−
| Vrijheidsbeperking
 
−
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FreedomRestrictingMeasures|zib-FreedomRestrictingMeasures}}
 
−
| Procedure
 
−
| VrijheidsBeperkendeMaatregelen
 
−
| v3.1(2017NL)
 
−
| -
 
−
|-
 
−
| Actuele patiëntenproblemen
 
−
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
 
−
| Condition
 
−
| Probleem
 
−
| v4.1(2017NL)
 
−
| -
 
−
|-
 
−
| Afspraken patiënt
 
−
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ProcedureRequest|zib-ProcedureRequest}}
 
−
| ProcedureRequest
 
−
| OverdrachtGeplandeZorgActiviteit
 
−
| v3.1(2017NL)
 
−
| -
 
−
|-
 
−
| Wensen en behoeften patiënt en/of naasten
 
−
| -
 
−
| -
 
−
| -
 
−
| -
 
−
| Declared as a text section. See {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-aanmeldbericht|eOverdracht aanmeldbericht profile}}.
 
−
|-
 
−
| rowspan="2"| Voeding/vocht
 
−
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem|zib-FeedingTubeSystem}}
 
−
| DeviceUseStatement
 
−
| SondeSysteem
 
−
| v3.2(2017NL)
 
−
| -
 
−
|-
 
−
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Infusion|zib-Infusion}}
 
−
| DeviceUseStatement
 
−
| Infuus
 
−
| v3.2(2017NL)
 
−
| -
 
−
|-
 
−
| Uitscheiding
 
−
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Stoma|zib-Stoma}}
 
−
| Observation
 
−
| Stoma
 
−
| v3.2(2017NL)
 
−
| -
 
−
|}
 
−
 
−
==Examples==
 
−
Example instances can be found on Simplifier:
 
−
* [https://simplifier.net/nictiz-stu3-eoverdracht/~resources?category=Example&exampletype=Composition Composition examples]
 
−
* [https://simplifier.net/nictiz-stu3-eoverdracht/~resources?category=Example&exampletype=Bundle Bundle examples]
 
−
 
−
=Use case: Overdrachtsbericht Volwassenen=
 
−
==Introduction==
 
−
During the pilot, the transfer information is based on a subset of the [[vpk:V3.1_Ontwerp_eOverdracht#Use_Case_1A_-_Verpleegkundige_overdracht:_Overdrachtsbericht_-_volwassenen_.28PUSH.29|Overdrachtsbericht Volwassenen]] (transfer message for adults). Phase one consists of the implementation of four HCIMs. The remaining information from eOverdracht may be sent unstructured in a PDF file.
 
−
 
−
==Actors and transactions==
 
−
 
−
{| class="wikitable" style="horizontal-align: right"
 
−
! Actor
 
−
! Role
 
−
! Transaction
 
−
|-
 
−
| Sending XIS
 
−
| Sends transfer message to the receiving XIS
 
−
| Send Overdrachtsbericht
 
−
|-
 
−
| Receiving XIS
 
−
| Acknowledges transfer message to sending XIS
 
−
| Overdrachtsbericht response
 
−
|-
 
−
|}
 
−
 
−
==Structure of the Overdrachtsbericht phase 2: 11 HCIMs + PDF==
 
−
 
−
The Overdrachtsbericht consists of multiple FHIR resources, which are assembled into a FHIR [http://hl7.org/fhir/STU3/bundle.html Bundle]. The table below lists the FHIR StructureDefinitions that are applicable for the pilot implementation of the 'Overdrachtsbericht' transactions. During phase 2, the Overdrachtsbericht is based on the same 11 HCIMs as the aanmeldbericht. The remaining information is made available via an unstructured PDF.
 
−
 
−
{| class="wikitable" style="horizontal-align: right"
 
−
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;  background-color: #E3E3E3 width:400px" | Section
 
−
!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:50px" | FHIR resource
 
−
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;  background-color: #E3E3E3 width:50px" | HCIM name
 
−
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;  background-color: #E3E3E3 width:50px" | HCIM version
 
−
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;  background-color: #E3E3E3 width:50px" | Remarks
 
−
|-
 
−
|
 
−
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-overdrachtsbericht-volwassenen-phase-two|eOverdracht Overdrachtsbericht volwassenen phase two}}
 
−
| Composition
 
−
| -
 
−
| -
 
−
| Declaration of the Send Overdrachtsbericht volwassenen phase two transaction.
 
−
|-
 
−
|-
 
−
| Datum overplaatsing
 
−
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-TransferDate|eOverdracht-TransferDate}}
 
−
| -
 
−
| -
 
−
| -
 
−
| DateTime extension used in eOverdracht composition profiles
 
−
|-
 
−
| rowspan="3"|Persoonsgegevens
 
−
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|nl-core-patient}}
 
−
| Patient
 
−
| Patient
 
−
| v3.1(2017NL)
 
−
| -
 
−
|-
 
−
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Payer|zib-Payer}}
 
−
| Coverage
 
−
| Betaler
 
−
| v3.1(2017NL)
 
−
| -
 
−
|-
 
−
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nl-core-relatedperson}}
 
−
| RelatedPerson
 
−
| Contactpersoon
 
−
| v3.1(2017NL)
 
−
| -
 
−
|-
 
−
| rowspan="3"|Sturende organisatie
 
−
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
 
−
| Organization
 
−
| Zorgaanbieder
 
−
| v3.1.1(2017NL)
 
−
| -
 
−
|-
 
−
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nl-core-practitioner}}
 
−
| Practitioner
 
−
| rowspan="2" |Zorgverlener
 
−
| rowspan="2" |v3.2(2017NL)
 
−
| rowspan="2" | -
 
−
|-
 
−
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nl-core-practitionerrole}}
 
−
| PractitionerRole
 
−
|-
 
−
| rowspan="3"|Ontvangende organisatie
 
−
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
 
−
| Organization
 
−
| Zorgaanbieder
 
−
| v3.1.1(2017NL)
 
−
| -
 
−
|-
 
−
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nl-core-practitioner}}
 
−
| Practitioner
 
−
| rowspan="2" |Zorgverlener
 
−
| rowspan="2" |v3.2(2017NL)
 
−
| rowspan="2" | -
 
−
|-
 
−
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nl-core-practitionerrole}}
 
−
| PractitionerRole
 
−
|-
 
−
| Medische diagnose
 
−
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
 
−
| Condition
 
−
| Probleem
 
−
| v4.1(2017NL
 
−
| -
 
−
|-
 
−
|-
 
−
| Voorgeschiedenis
 
−
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
 
−
| Condition
 
−
| Probleem
 
−
| v4.1(2017NL
 
−
| -
 
−
|-
 
−
| Let op
 
−
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Alert|zib-Alert}}
 
−
| Flag
 
−
| Alert
 
−
| v3.2(2017NL)
 
−
| -
 
−
|-
 
−
| Vrijheidsbeperking
 
−
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FreedomRestrictingMeasures|zib-FreedomRestrictingMeasures}}
 
−
| Procedure
 
−
| VrijheidsBeperkendeMaatregelen
 
−
| v3.1(2017NL)
 
−
| -
 
−
|-
 
−
| Actuele patiëntenproblemen
 
−
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
 
−
| Condition
 
−
| Probleem
 
−
| v4.1(2017NL)
 
−
| -
 
−
|-
 
−
| Afspraken patiënt
 
−
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ProcedureRequest|zib-ProcedureRequest}}
 
−
| ProcedureRequest
 
−
| OverdrachtGeplandeZorgActiviteit
 
−
| v3.1(2017NL)
 
−
| -
 
−
|-
 
−
| Wensen en behoeften patiënt en/of naasten
 
−
| -
 
−
| -
 
−
| -
 
−
| -
 
−
| Declared as a text section. See {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-overdrachtsbericht-volwassenen-phase-two|Overdrachtsbericht Volwassenen phase two composition profile}}.
 
−
|-
 
−
| rowspan="2"| Voeding/vocht
 
−
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem|zib-FeedingTubeSystem}}
 
−
| DeviceUseStatement
 
−
| SondeSysteem
 
−
| v3.2(2017NL)
 
−
| -
 
−
|-
 
−
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Infusion|zib-Infusion}}
 
−
| DeviceUseStatement
 
−
| Infuus
 
−
| v3.2(2017NL)
 
−
| -
 
−
|-
 
−
| Uitscheiding
 
−
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Stoma|zib-Stoma}}
 
−
| Observation
 
−
| Stoma
 
−
| v3.2(2017NL)
 
−
| -
 
−
|-
 
−
| PDF
 
−
| [https://www.hl7.org/fhir/binary.html Binary]
 
−
| Binary
 
−
| -
 
−
| -
 
−
| Should be used to send unstructured PDF data.
 
−
|}
 
−
 
−
==Examples==
 
−
Example instances can be found on Simplifier:
 
−
* [https://simplifier.net/nictiz-stu3-eoverdracht/~resources?category=Example&exampletype=Composition Composition examples]
 
−
* [https://simplifier.net/nictiz-stu3-eoverdracht/~resources?category=Example&exampletype=Bundle Bundle examples]
 
  
 
=FHIR CapabilityStatements=
 
=FHIR CapabilityStatements=
Regel 602: Regel 224:
 
* {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/eOverdracht-servercapabilities-phase-one|CapabilityStatement server}}
 
* {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/eOverdracht-servercapabilities-phase-one|CapabilityStatement server}}
 
* {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/eOverdracht-clientcapabilities-phase-one|CapabilityStatement server}}
 
* {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/eOverdracht-clientcapabilities-phase-one|CapabilityStatement server}}
−
 
+
=FHIR Examples=
−
===Phase two===
+
Example instances can be found on Simplifier:
−
* {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/eOverdracht-servercapabilities-phase-two|CapabilityStatement server}}
+
* [https://simplifier.net/nictiz-stu3-eoverdracht/~resources?category=Example&exampletype=Composition Composition examples]
−
* {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/eOverdracht-clientcapabilities-phase-two|CapabilityStatement client}}
+
* [https://simplifier.net/nictiz-stu3-eoverdracht/~resources?category=Example&exampletype=Bundle Bundle examples]

Versie van 8 apr 2020 08:44

Introduction

This page details the HL7 FHIR requirements for exchanging the data in the Verpleegkundige eOverdracht Proeftuin pilot described in this functional design. 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 excist out 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. This FHIR implementation guide assumes the sending XIS is able to make a connection with the recieving XIS. It does not provide information on finding the right XIS nor does it provide information about security.

Packages

eOverdracht uses the FHIR Packaging mechanism. This conveniently bundles all examples, profiles and other conformance resources you need into a single download. This version of the information standard depends on Nictiz Zib2017 package . Please note that the direct links to the various conformance resources below will take you to the latest version, which might not match the package version. At time of writing, there is no way to render the conformance resource as found in the package. This is on the roadmap for Simplifier.

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.

Em.png

Basic FHIR(STU3) knowledge is required.

Use case 1A: Send Overdrachtsbericht volwassenen (PUSH)

Introduction

The Send Overdrachtsbericht scenario is used by the sending XIS to send the relevant data for the patient care to the receiving XIS. The structure of the eventual scenario is described in the functional design and additionally in Opbouw eOverdracht Overdrachtsbericht. For the pilot a limited subset is implemented.

Actors

Transaction group Transaction Actor Role
Send eOverdracht Overdrachtbericht(PUSH) Send overdrachtbericht Healthcare professional (using a XIS) Sends overdrachtbericht to the receiving XIS

Invocation

The Send Overdrachtbericht transaction is an HTTP POST method on the target XIS's base: 

POST [base] {?_format=[mime-type]}

where the body of the POST request is the assembled Bundle.

Trigger events

This transaction is invoked when the XIS needs to send the eOverdrachtbericht to the receiving XIS.

Expected response

The document Bundle should be processed as a transaction by the receiving XIS and each Bundle.entry should be treated as a create interaction for the Bundle.entry.resource.

When the resource syntax or data is incorrect or invalid and cannot be used to create a new resource, or when the server rejects the content of the resource because of business rules, it should perform a rollback of the creation of any previous entries and send the appropriate response.

On success, the target XIS SHALL respond:

  • With the HTTP status code 201 Created.
  • With the Location header containing the new Logical Id and Version Id of the created resource version.
  • With a response body set to a Bundle of type "transaction-response", containing one entry for each entry in the request, in the same order, with the outcome of processing the entry.

On failure, the target XIS SHALL respond:

  • With an HTTP status code set appropriate to the processing outcome:
    • When the resource syntax or data is incorrect or invalid, and cannot be used to create a new resource, the server returns a 400 Bad Request HTTP status code.
    • When the server rejects the content of the resource because of business rules, the server returns a 422 Unprocessable Entity error HTTP status code. Additional HTTP status code may be used if more appropriate.
  • With a response body set to a FHIR OperationOutcome resource with detailed error messages describing the reason for the error.

Structure of the Overdrachtbericht phase 1 (4HCIMs + PDF)

Both the Aanmeldbericht as the eOverdrachtbericht are sent as a FHIR Document. To create this document, a FHIR Composition resource should be created according to the relevant Composition profiles.

A client may use the returned Bundle to track the outcomes of processing the entry, and the identities assigned to the resources by the server. Each entry element SHALL contain a response element which details the outcome of processing the entry - the HTTP status code, and the location and ETag header values, which are used for identifying and versioning the resources. In addition, a resource may be included in the entry, as specified by the Prefer header.

The Overdrachtsbericht consists of multiple FHIR resources, which are assembled into a FHIR Bundle. The table below lists the FHIR StructureDefinitions that are applicable for the pilot implementation of the 'Overdrachtsbericht' transactions. During phase 1, the Overdrachtsbericht is based on the same 4 HCIMs as the aanmeldbericht (Patient, Betaler, Contactpersoon en Zorgaanbieder).

Section FHIR profile FHIR resource HCIM name HCIM version Remarks
Overdrachtsbericht volwassenen phase one@ http://nictiz.nl/fhir/StructureDefinition/eOverdracht-Overdrachtsbericht-volwassenen-phase-one Composition - - Declaration of the Send Overdrachtsbericht volwassenen phase one transaction.
Datum overplaatsing http://nictiz.nl/fhir/StructureDefinition/eOverdracht-TransferDate - - - DateTime extension used in eOverdracht composition profiles
Persoonsgegevens http://fhir.nl/fhir/StructureDefinition/nl-core-patient Patient Patient v3.1(2017NL) -
http://nictiz.nl/fhir/StructureDefinition/zib-Payer Coverage Betaler v3.1(2017NL) -
Sturende organisatie http://fhir.nl/fhir/StructureDefinition/nl-core-organization Organization Zorgaanbieder v3.1.1(2017NL) -
http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner Practitioner Zorgverlener v3.2(2017NL) -
http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole PractitionerRole
Ontvangende organisatie http://fhir.nl/fhir/StructureDefinition/nl-core-organization Organization Zorgaanbieder v3.1.1(2017NL) -
http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner Practitioner Zorgverlener v3.2(2017NL) -
http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole PractitionerRole
PDF Binary Binary - - Should be used to send unstructured PDF data.

Use case 3A: Send Aanmeldbericht (PUSH)

Introduction

The Send Aanmeldbericht scenario is used by the sending XIS to send the relevant data for the patient intake to the receiving XIS, and constitutes a subset of the Overdrachtsbericht. The structure of the eventual scenario is described in the functional design and additionally in Opbouw eOverdracht aanmelding. For the pilot a limited subset is implemented.

Actors

Transaction group Transaction Actor Role
Send eOverdracht Aanmeldbericht(PUSH) Send aanmeldbericht request Healthcare professional (using a XIS) Sends aanmeldbericht to the receiving XIS
Send aanmeldbericht response Receiving XIS Sends acknowledgement message to sending XIS

Invocations

The Send Aanmeldbericht transaction is an HTTP POST method on the target XIS's base: 

POST [base] {?_format=[mime-type]}

where the body of the POST request is the assembled Bundle.

Trigger events

This transaction is invoked when the patiënt is ready for transfer, and the sending XIS wants to confirm a recieving XIS.

Server response

Structure of the Aanmeldbericht phase 1

Both the Aanmeldbericht as the eOverdrachtbericht are sent as a FHIR Document. To create this document, a FHIR Composition resource should be created according to the relevant Composition profiles.

The Aanmeldbericht consists of multiple FHIR resources, which are assembled into a FHIR Bundle. The table below lists the FHIR StructureDefinitions that are applicable for the pilot implementation of the 'Aanmeldbericht' transactions.

Section FHIR profile FHIR resource HCIM name HCIM version Remarks
- aanmeldbericht phase one@ http://nictiz.nl/fhir/StructureDefinition/eOverdracht-aanmeldbericht-phase-one Composition - - Declaration of the Send Aanmeldbericht transaction.
Datum overplaatsing http://nictiz.nl/fhir/StructureDefinition/eOverdracht-TransferDate - - - DateTime extension used in eOverdracht composition profiles
Persoonsgegevens http://fhir.nl/fhir/StructureDefinition/nl-core-patient Patient Patient v3.1(2017NL) -
http://nictiz.nl/fhir/StructureDefinition/zib-Payer Coverage Betaler v3.1(2017NL) -
Sturende organisatie http://fhir.nl/fhir/StructureDefinition/nl-core-organization Organization Zorgaanbieder v3.1.1(2017NL) -
Ontvangende organisatie http://fhir.nl/fhir/StructureDefinition/nl-core-organization
PDF Binary Binary - - Should be used to send unstructured PDF data.

FHIR CapabilityStatements

Phase one

FHIR Examples

Example instances can be found on Simplifier:

Overgenomen van "https://informatiestandaarden.test-nictiz.nl/index.php?title=vpk:Vdraft_FHIR_eOverdracht_Proeftuin&oldid=25746"