The profiles listed in the table below represent their entire respective HCIM and are applicable in a broader context than the exchange of Prio1 information.
This page details the HL7 FHIR requirements for exchanging the Geboortezorg v2.3 data described in Functioneel.
Use case: Register Prio1 data
Introduction
The Register Prio1 transaction is used by the sending XIS to send the relevant data to the registry.
Actors
Transaction group
Transaction
Actor
Role
Register Prio1(PUSH)
Register Prio1
Healthcare professional (using a XIS)
Sends Prio1 data to registry
Retrieve Prio1(PULL)
Querying XIS
Healthcare professional (using a XIS)
Retrieves Prio1 data from registry
Invocations
Sending XIS: request message
Trigger Events
Message Semantics
Because the data needed will most likely consist of multiple FHIR resources, a document Bundle is used.
The interaction is performed by an HTTP POST command as shown:
POST [base] {?_format=[mime-type]}
The body of the post submission is a Bundle with Bundle.type = document. The first entry contains a Composition resource, and each subsequent entry contains a resource that is referenced from the Composition resource. By sending it to the target's base, the document Bundle will be processed as a transaction and each Bundle.entry will be treated as a create interaction for the entry.resource.
Relevant value sets can be found here. All resources can be downloaded in a .zip in XML or JSON format. In the .zip, the value sets are stored in the directory 'value sets'.
