Gebz:V1.0 FHIR IG: verschil tussen versies
Geen bewerkingssamenvatting |
Geen bewerkingssamenvatting |
||
| Regel 2: | Regel 2: | ||
{{#customtitle:FHIR Implementation Guide Geboortezorg v2.3 | FHIR Implementation Guide Geboortezorg v2.3}} | {{#customtitle:FHIR Implementation Guide Geboortezorg v2.3 | FHIR Implementation Guide Geboortezorg v2.3}} | ||
<imagemap>Bestand:Afsprakenstelsel-functioneel-technisch-banner_00_alle.png|center|500px|alt=Afspraken-Functioneel-Technisch | <imagemap>Bestand:Afsprakenstelsel-functioneel-technisch-banner_00_alle.png|center|500px|alt=Afspraken-Functioneel-Technisch | ||
circle 241 216 211 [ | circle 241 216 211 [[Gebz:V2.3_Babyconnect | Afsprakenstelsel]] | ||
circle 1013 224 212 [[Gebz:V2.3_Ontwerpen | Functioneel]] | circle 1013 224 212 [[Gebz:V2.3_Ontwerpen | Functioneel]] | ||
circle 1787 230 212 [[Gebz:V2.3_FHIR_IG | Technisch]] | circle 1787 230 212 [[Gebz:V2.3_FHIR_IG | Technisch]] | ||
Versie van 17 jan 2020 15:11
|
|
Dit materiaal is in ontwikkeling en nog niet geschikt voor gebruik! |
{{#customtitle:FHIR Implementation Guide Geboortezorg v2.3 | FHIR Implementation Guide Geboortezorg v2.3}}
Introduction
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.
Read more:
Examples
Expected Actions
List of StructureDefinitions
The profiles listed in the table below represent their entire respective HCIM and are applicable in a broader context than the exchange of eOverdracht information.
| Zib naam | Zib versie | FHIR Resource | FHIR Profile |
|---|---|---|---|
| - | - | Composition | TODO |
| Patient | v3.1(2017NL) | Patient | http://fhir.nl/fhir/StructureDefinition/nl-core-patient |
| - | - | Patient | http://nictiz.nl/fhir/StructureDefinition/bc-Woman |
| Zwangerschap | Observation | http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy | |
| Observation | http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-Gravidity | ||
| Observation | http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-Parity | ||
| A term datum | Observation | http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-TermDate | |
| - | - | DiagnosticReport | TODO ObstetricReport |
| LaboratoriumUitslag | Observation | http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation | |
| DiagnosticReport | http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-DiagnosticReport |
Terminology, NamingSystems, Mappings
Terminology
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'.