MedMij:V6/FHIR Vaccination-Immunization: verschil tussen versies

Uit informatiestandaarden
Naar navigatie springen Naar zoeken springen
 
(83 tussenliggende versies door 5 gebruikers niet weergegeven)
Regel 1: Regel 1:
__NOINDEX__
 
{{DISPLAYTITLE:FHIR Implementation Guide: Immunization 0.1.0}}
 
{{NoteBox|Draft version of the FHIR IG for Immunization. Currently in development and therefore not yet suitable for implementation. The draft version of the functional design can be found [https://informatiestandaarden.nictiz.nl/wiki/MedMij:Vdraft/OntwerpImmunisatie here].}}
 
 
UNDER CONSTRUCTION --- NOT SUITED FOR TESTING OR IMPLEMENTATION
 
 
 
__NUMBEREDHEADINGS__
 
__NUMBEREDHEADINGS__
{{VersieInfo|Immisatieresultaten}}
+
{{DISPLAYTITLE:FHIR Implementation Guide: use case Retreive vaccinations by the patient 1.0.8}}
{{MedMij:V2020.01/Issuebox_FHIR_IG}}
+
{{MedMij:V6/Issuebox_FHIR_IG}}
  
 
[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]
 
[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]
[[Bestand:Immunisatie.png |link=|links |87px|Immunisatie]]
+
[[Bestand:Icoon_Nictiz_Cirkel_Informatiestandaard_Vaccinatie.svg|link=|87px|Vaccinatie-Immunisatie]]  
<imagemap>Bestand:Leeswijzer-technisch-banner 03 white.png|center|400px|alt=Afspraken-Functioneel-Technisch 
 
circle 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]               
 
circle 1013 224 212 [[MedMij:V2020.01/OntwerpLabresult|Functioneel]]               
 
circle 1787 230 212 [[MedMij:V2020.01/FHIR_IG|Technisch]]               
 
desc none                   
 
</imagemap>
 
  
 
=Introduction=
 
=Introduction=
[[Bestand:Functioneel-02.png|link=MedMij:V2020.01/Ontwerpen |100px|rechts|Functional design|Go to functional design]]
+
This page describes patient's use case for the retrieval of vaccination results, in a personal health environment (PHR) context. Functional specifications of this use case are described at the [[MedMij:V6/Ontwerp_Vaccinatie-Immunisatie| functional design wiki page]]. This use case consists of enabling a patient to view his own administered vaccinations in a PHR. The technical specification is described here. HL7 FHIR R4 is used for this purpose. Vaccinations are represented by the Immunization resources in FHIR. A transaction will retrieve all administered vaccinations from the XIS.
 
 
This page describes patient's use case for the retrieval of immunization results, in a personal health environment (PHR) context. Functional specifications are described at the [[MedMij:V2020.01/Ontwerpen| functional design wiki page]]. The technical specification is described here. HL7 FHIR R4 is used for this purpose.
 
 
 
'''Note''': This implementation guide builds on the general guidelines described in the [[MedMij:V2020.01/FHIR_IG#Use case overarching principles|use case overarching principles]].
 
 
 
-----> DIT LIJKT ME HIER NIET VAN TOEPASSING TOCH? EN ANDERS AANGEVEN WELKE WEL RELEVANT ZIJN HIERVOOR
 
Many immunization result observations have important relationships to other observations and need to be grouped together. [http://hl7.org/fhir/observation.html#10.1.4.1 The FHIR specification] defines three structures to do this: DiagnosticReport and DiagnosticReport.result, Observation and Observation.component, and Observation and Observation.related. For the transactions of laboratory results retrieval, the following two grouping structures are relevant.
 
 
 
====Observation====
 
Individual laboratory results are represented by Observation resources, such as one blood glucose value. The Observation resource can also be used as a structure for a panel or battery observation. Observation.related is used for any supporting result that can be interpreted and used on its own and has one or more different values for method, observation, performer, device, time, and/or error conditions. The top-level observation specifies the grouping code in Observation.code, but typically does not have its own Observation.value, and the set of member observations are listed in the Observation.related element.
 
 
 
====DiagnosticReport====
 
In contrast to the Observation resource, the DiagnosticReport resource typically includes additional clinical context and some mix of atomic results, images, imaging reports, textual and coded interpretation, and formatted representations. Report conclusions can be expressed as a simple text blob, structured coded data or as an attached fully formatted report such as a PDF. The DiagnosticReport.code names the panel and serves as the grouping element, which is traditionally referred to as a "panel" or "battery" by laboratories. The DiagnosticReport.result element references the individual observations.
 
  
Both structures may exist in a XIS. Therefore, two transactions are defined to retrieve a patient's laboratory results. The transaction content either consists of a single and related laboratory results structure or a complete diagnostic report that adds more clinical meaning to the single and related laboratory results. The transactions:
+
==Dependencies==
 
+
* [[MedMij:V6/Ontwerp_Vaccinatie-Immunisatie|The functional design of this usecase]], and by extension
* [[MedMij:V2020.01/FHIR_LaboratoryResults#Use_case:_retrieve_laboratory_results| Retrieve laboratory results]]
+
** [[imm:V1/Ontwerp_Vaccinatie-Immunisatie|The information standard Vaccinatie-Immunisatie 1]]
* [[MedMij:V2020.01/FHIR_LaboratoryResults#Use_case:_retrieve_laboratory_results_DiagnosticReport| Retrieve laboratory results DiagnosticReport]]
+
** [[MedMij:FO:V1/FunctioneelOntwerp|The functioneel design for MedMij 6]]
 +
* Zib publication 2020
 +
* [[MedMij:IG:V1/FHIR_IG#Overarching principles|The general implementation guide for FHIR R4 in MedMij context]], and by extension:
 +
** HL7 FHIR, version R4
 +
* The zib2020 package for FHIR R4
  
 
=Actors involved=
 
=Actors involved=
 
{| class="wikitable"
 
{| class="wikitable"
! colspan="2" style="text-align:left;" | Persons
+
! colspan="2" style="text-align:left; background-color: #4AB8A7; color: white; font-weight: bold;" | Actors
! colspan="2" style="text-align:left;" | Systems
+
! colspan="2" style="text-align:left; background-color: #4AB8A7; color: white; font-weight: bold;" | Systems
! colspan="2" style="text-align:left;" | FHIR Capability Statements
+
! colspan="2" style="text-align:left; background-color: #4AB8A7; color: white; font-weight: bold;" | FHIR CapabilityStatements
 
|-
 
|-
 
! style="text-align:left;" |Name
 
! style="text-align:left;" |Name
Regel 56: Regel 35:
 
| PHR
 
| PHR
 
| Personal health record
 
| Personal health record
|[[Bestand: Verwijzing.png| 20px]] {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/labresults-clientcapabilities|nictiz.fhir.nl.stu3.zib2017|title=CapabilityStatement: Client}}
+
| rowspan="2" | {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/imm-RetrieveServe|nictiz.fhir.nl.r4.vaccinationimmunization|pkgVersion=1.0.0-rc.1|title=CapabilityStatement: Retrieve Serve}}
| LaboratoryResults process client requirements  
+
| rowspan="2" | FHIR client/server requirements  
 
|-
 
|-
| Healthcare professional
+
| (Healthcare) provider
 
| The user of a XIS
 
| The user of a XIS
 
| XIS
 
| XIS
| Healthcare information system
+
| (Healthcare) information system
|[[Bestand: Verwijzing.png| 20px]] {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/labresults-servercapabilities|nictiz.fhir.nl.stu3.zib2017|title=CapabilityStatement: Server}}
 
| LaboratoryResults server requirements
 
 
|}
 
|}
  
=Use case: retrieve laboratory results=
+
=Use case details =
 
[[Bestand:Afsprakenstelsel-01.png|link=https://www.medmij.nl/afsprakenstelsel/|rechts |100px|Go to Afsprakenstelsel]]
 
[[Bestand:Afsprakenstelsel-01.png|link=https://www.medmij.nl/afsprakenstelsel/|rechts |100px|Go to Afsprakenstelsel]]
 +
==Introduction==
 +
The retrieve vaccinations transaction is used by the PHR to retrieve vaccinations from a XIS.
 +
==Assumptions==
 
{{FHIR-IG-Afsprakenstelsel-Note}}
 
{{FHIR-IG-Afsprakenstelsel-Note}}
 
==Introduction==
 
The retrieve laboratory results transaction is used by the PHR to retrieve laboratory results from a XIS.
 
 
 
==Actors==
 
==Actors==
 
{| class="wikitable" "cellpadding="10"
 
{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transaction group'''
+
! style="text-align:left; background-color: #4AB8A7; color: white; font-weight: bold;"| '''Transaction group'''
! style="text-align:left;"| '''Transaction'''
+
! style="text-align:left; background-color: #4AB8A7; color: white; font-weight: bold;"| '''Transaction'''
! style="text-align:left;"| '''Actor'''
+
! style="text-align:left; background-color: #4AB8A7; color: white; font-weight: bold;"| '''Actor'''
! style="text-align:left;"| '''Role'''
+
! style="text-align:left; background-color: #4AB8A7; color: white; font-weight: bold;"| '''Role'''
 
|-
 
|-
|style="background-color: white;vertical-align:top;" rowspan="2"|Retrieve Laboratory Results(PULL)
+
|style="background-color: white;vertical-align:top;" rowspan="2"|Retrieve vaccinations(PULL)
|style="background-color: white;vertical-align:top;"|Retrieve laboratory results request
+
|style="background-color: white;vertical-align:top;"|Retrieve vaccinations request
 
|style="background-color: white;vertical-align:top;"|Patient (using a PHR)
 
|style="background-color: white;vertical-align:top;"|Patient (using a PHR)
|style="background-color: white;vertical-align:top;"|Request laboratory results from the XIS
+
|style="background-color: white;vertical-align:top;"|Request vaccinations from the XIS
 
|-
 
|-
|style="background-color: white;vertical-align:top;"|Retrieve laboratory results response
+
|style="background-color: white;vertical-align:top;"|Retrieve vaccinations response
|style="background-color: white;vertical-align:top;"|Healthcare professional (using a XIS)
+
|style="background-color: white;vertical-align:top;"|(Healthcare) provider (using a XIS)
|style="background-color: white;vertical-align:top;"|Serves laboratory results to the PHR
+
|style="background-color: white;vertical-align:top;"|Serves vaccinations to the PHR
 
|}
 
|}
  
Regel 95: Regel 71:
 
The request message represents an HTTP GET parameterized query from the PHR to the XIS.
 
The request message represents an HTTP GET parameterized query from the PHR to the XIS.
  
====Trigger Events====
+
====Trigger events====
When the patient(PHR) wants to obtain laboratory results, it issues a retrieve laboratory results request message.
+
When the patient (PHR) wants to obtain vaccinations, it issues a retrieve vaccinations request message.
  
====Message Semantics====
+
====Message semantics====
 
The PHR executes an HTTP GET conform to the FHIR [http://hl7.org/fhir/http.html RESTful] and [http://hl7.org/fhir/search.html search] specification against the XIS's Observation endpoint. This search query URL is configurable by the PHR and has the following format:
 
The PHR executes an HTTP GET conform to the FHIR [http://hl7.org/fhir/http.html RESTful] and [http://hl7.org/fhir/search.html search] specification against the XIS's Observation endpoint. This search query URL is configurable by the PHR and has the following format:
 
<pre>GET [base]/Observation?category=http://snomed.info/sct|49581000146104{&[parameters]}</pre>
 
  
The PHR may use, and the XIS shall be capable of processing, the following parameters to configure the search query:
+
<pre>GET [base]/Immunization{?_include=Immunization:patient&_include:iterate=Immunization:performer}</pre>
{| class="wikitable"
+
 
! Name
+
At this point in time, there are no use cases for filter parameters on the query. The stated query will return a Bundle with all known administered immunizations. Each immunization is conveyed in an Immunization resource. The Immunization resource will contain references to actors such as the Patient and the Health Professional/Organization. If those references are not in the Bundle, a client SHALL be able to resolve them at the source. The client may wish to have these references resolved in the Bundle by specifying the [http://hl7.org/fhir/R4/search.html#include {{fhir|_include}}] parameter on the query. The server SHALL support this {{fhir|_include}} parameter. It MAY include referenced resources even if the client doesn't ask for them if it doesn't support read operations for these resources.
! Description
 
! Examples
 
|-
 
| [https://www.hl7.org/fhir/stu3/observation.html#search date]
 
| Obtained date/time for the result. If the result was obtained over a period, this parameter should be interpreted as a date that falls in this period.
 
| Retrieve all zib LaboratoryTestResults Observation resources that have an effective date greater than 01-01-2010:
 
<pre>GET [base]/Observation?category=http://snomed.info/sct|49581000146104&date=ge2010-01-01</pre>
 
Retrieve all zib LaboratoryTestResults Observation resources that have an effective date within a 2 year period:
 
<pre>GET [base]/Observation?_include=Observation:specimen&category=http://snomed.info/sct|49581000146104date=ge2010-01-01&date=le2011-12-31</pre>
 
|-
 
| [https://www.hl7.org/fhir/stu3/observation.html#search category]
 
| The classification of the type of observation.
 
| Retrieve all zib LaboratoryTestResults Observation resources:
 
<pre>GET [base]/Observation?category=http://snomed.info/sct|49581000146104</pre>
 
|-
 
| [http://hl7.org/fhir/STU3/search.html#include _include]
 
| The PHR may request that the XIS returns resources related to the search results, in order to reduce the overall network delay of repeated retrievals of related resources.
 
| Retrieve all zib LaboratoryTestResults Observation resources and include Specimen information in the search results:
 
<pre>GET [base]/Observation?_include=Observation:specimen&category=http://snomed.info/sct|49581000146104</pre>
 
|}
 
  
=====Expected Actions=====
+
=====Expected actions=====
The XIS shall process the query to discover Observation resources that match the search parameters given.
+
The XIS SHALL process the query to retrieve patient's Immunization resources and the included referenced resources.
  
 
===XIS: response message===
 
===XIS: response message===
The XIS returns an HTTP Status code appropriate to the processing as well as a FHIR Bundle including the matching observation information.
+
The XIS returns an HTTP Status code appropriate to the processing as well as a FHIR Bundle including the matching information.
 +
 
 +
====Trigger events====
 +
The XIS completed processing of the retrieve vaccinations request message.
  
====Trigger Events====
+
====Message semantics====
The XIS completed processing of the retrieve laboratory results request message.
+
The returned data to the PHR should conform to the profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the {{fhir|.meta.profile}} element in order to show compliance.  
  
====Message Semantics====
+
{{MedMij:V2020.01/NoteBoxPackage|p1=nictiz.fhir.nl.r4.vaccinationimmunization|p2=nictiz.fhir.nl.r4.zib2020|v2=0.7.0-beta.1}}
The returned data to the PHR should conform to the HCIMs and their associated profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.  
 
  
{{MedMij:V2020.01/NoteBoxPackage|p1=nictiz.fhir.nl.stu3.zib2017}}
 
  
{| class="wikitable" width="1400px"
+
{| class="wikitable"
|-style="background-color: #1F497D; color: white; font-weight: bold; "
+
! style="text-align:left; background-color: #4AB8A7; color: white; font-weight: bold;" | Profile name
|Zib name NL||Zib name EN||FHIR Resource||URL profile|
+
! style="text-align:left; background-color: #4AB8A7; color: white; font-weight: bold;" | FHIR Resource
|-style="vertical-align:top; background-color: #E3E3E3;  
+
! style="text-align:left; background-color: #4AB8A7; color: white; font-weight: bold;" | HCIM EN
 +
! style="text-align:left; background-color: #4AB8A7; color: white; font-weight: bold;" | Canonical URL
 +
|-
 +
| nl core Vaccination event
 +
| Immunization
 +
| [https://zibs.nl/wiki/Vaccinatie-v4.0(2020NL) Vaccination]
 +
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Vaccination-event|nictiz.fhir.nl.r4.zib2020|pkgVersion=0.7.0-beta.1}}
 
|-
 
|-
 +
| nl core Patient
 
| Patient
 
| Patient
| #Zib Patient|Patient
+
| [https://zibs.nl/wiki/Patient-v3.2(2020EN) Patient]
| Patient
+
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.zib2020|pkgVersion=0.7.0-beta.1}}
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|nictiz.fhir.nl.stu3.zib2017}}
 
 
|-
 
|-
| Zorgverlener
+
| nl core HealthProfessional
| HealthProfessional
 
 
| Practitioner
 
| Practitioner
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017}}
+
| rowspan="2" | [https://zibs.nl/wiki/HealthProfessional-v3.5(2020EN) HealthProfessional]
|-
+
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.zib2020|pkgVersion=0.7.0-beta.1}}
| Zorgaanbieder
 
| HealthcareProvider
 
| Organization
 
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017}}
 
|-
 
| LaboratoriumUitslag
 
| LaboratoryTestResult
 
| Observation
 
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017}}
 
|}
 
 
 
====Expected Actions====
 
The PHR shall process the results according to application-defined rules. The PHR should be robust as the response may contain observation and specimen resources that match the query parameters.
 
 
 
=Use case: retrieve laboratory results DiagnosticReport=
 
[[Bestand:Afsprakenstelsel-01.png|link=https://www.medmij.nl/afsprakenstelsel/|rechts |100px|Go to Afsprakenstelsel]]
 
{{FHIR-IG-Afsprakenstelsel-Note}}
 
 
 
==Introduction==
 
The retrieve laboratory diagnostic report transaction is used by the PHR to retrieve laboratory results from a XIS.
 
 
 
==Actors==
 
{| 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"|Retrieve Laboratory Results(PULL)
+
| nl core HealthProfessional PractitionerRole
|style="background-color: white;vertical-align:top;"|Retrieve laboratory diagnostic report request
+
| PractionerRole
|style="background-color: white;vertical-align:top;"|Patient (using a PHR)
+
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.zib2020|pkgVersion=0.7.0-beta.1}}
|style="background-color: white;vertical-align:top;"|Request laboratory diagnostic report from the XIS
 
 
|-
 
|-
|style="background-color: white;vertical-align:top;"|Retrieve laboratory diagnostic report response
+
| nl core HealthcareProvider Organization
|style="background-color: white;vertical-align:top;"|Healthcare professional (using a XIS)
+
| Organization
|style="background-color: white;vertical-align:top;"|Serves laboratory diagnostic report to the PHR
+
| rowspan="2" | [https://zibs.nl/wiki/HealthcareProvider-v3.4(2020EN) HealthcareProvider]
|}
+
|{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.zib2020|pkgVersion=0.7.0-beta.1}}
 
 
==Invocations==
 
===PHR: request message===
 
The request message represents an HTTP GET parameterized query from the PHR to the XIS.
 
 
 
====Trigger Events====
 
When the patient(PHR) wants to obtain laboratory diagnostic report, it issues a retrieve laboratory diagnostic report request message.
 
 
 
====Message Semantics====
 
The PHR executes an HTTP GET conform to the FHIR [http://hl7.org/fhir/http.html RESTfull] and [http://hl7.org/fhir/search.html search] specification against the XIS's DiagnosticReport endpoint. This search query URL is configurable by the PHR and has the following format.
 
 
<pre>GET [base]/DiagnosticReport?category=http://snomed.info/sct|4241000179101{&[parameters]}</pre>
 
 
 
The PHR may use, and the XIS shall be capable of processing, the following parameters to configure the search query:
 
 
 
{| class="wikitable"
 
! Name
 
! Description
 
! Example(s)
 
 
|-
 
|-
| [https://www.hl7.org/fhir/stu3/diagnosticreport.html#search date]
+
| nl core HealthcareProvider
| The clinically relevant time of the report.
+
| Location
| Retrieve all zib LaboratoryTestResult DiagnosticReport resources that have an effective date greater than 01-01-2010.
+
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.zib2020|pkgVersion=0.7.0-beta.1}}
<pre>GET [base]/DiagnosticReport?category=http://snomed.info/sct|4241000179101&date=ge2010-01-01</pre>
 
Retrieve all zib LaboratoryTestResult DiagnosticReport resources that have an effective date within a 2 year period.
 
<pre>GET [base]/DiagnosticReport?category=http://snomed.info/sct|4241000179101&date=ge2010-01-01&date=le2011-12-31</pre>
 
 
|-
 
|-
| [https://www.hl7.org/fhir/stu3/diagnosticreport.html#search category]
+
| nl core PharmaceuticalProduct
| Which diagnostic discipline/department created the report.
+
| Medication
 +
| [https://zibs.nl/wiki/PharmaceuticalProduct-v2.1.2(2020EN) PharmaceuticalProduct]
 +
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-PharmaceuticalProduct|nictiz.fhir.nl.r4.zib2020|pkgVersion=0.7.0-beta.1}}
 
|-
 
|-
| [http://hl7.org/fhir/STU3/search.html#include _include]
 
| The PHR may request that the XIS returns resources related to the search results, in order to reduce the overall net
 
| Retrieves all zib LaboratoryTestResult DiagnosticReport resources and include the referenced Observation resources in the search results.
 
<pre>GET [base]/DiagnosticReport?category=http://snomed.info/sct|4241000179101&include=DiagnosticReport:result&date=ge2010-01-01&date=le2011-12-31</pre>
 
 
|}
 
|}
  
=====Expected Actions=====
+
====Expected actions====
The XIS shall process the query to discover DiagnosticReport resources that match the search parameters given.
+
The PHR SHALL process the results. The PHR SHOULD contain all the resources that match the query and all the reference resources that are included in the Bundle.
  
===XIS: response message===
+
=Release notes=
The XIS returns an HTTP Status code appropriate to the processing as well as a FHIR Bundle including the matching laboratory diagnostic report information.
+
Release notes can be found on the [[MedMij:V6/Ontwerp_Vaccinatie-Immunisatie#Release_notes| functional design page]].
 
 
====Trigger Events====
 
The XIS completed processing of the retrieve laboratory diagnostic report request message.
 
 
 
====Message Semantics====
 
The returned data to the PHR should conform to the HCIMS and their associate profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.
 
 
 
{{MedMij:V2020.01/NoteBoxPackage|p1=nictiz.fhir.nl.stu3.zib2017|v1Min=2.0.0}}
 
  
{| class="wikitable" width="1400px"
+
=Support=
|-style="background-color: #1F497D; color: white; font-weight: bold; "
+
For questions and change requests regarding this IG, please create a ticket in [https://bits.nictiz.nl/projects/MM BITS].
|Zib name NL||Zib name EN||FHIR Resource||URL profile|
 
|-style="vertical-align:top; background-color: #E3E3E3;
 
|-
 
| Patient
 
| #Zib Patient|Patient
 
| Patient
 
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|nictiz.fhir.nl.stu3.zib2017}}
 
|-
 
| Zorgverlener
 
| HealthProfessional
 
| Practitioner
 
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017}}
 
|-
 
| Zorgaanbieder
 
| HealthcareProvider
 
| Organization
 
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017}}
 
|-
 
| rowspan="2" | LaboratoriumUitslag
 
| rowspan="2" | LaboratoryTestResult
 
| DiagnosticReport
 
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-DiagnosticReport|nictiz.fhir.nl.stu3.zib2017}}
 
|-
 
| Observation
 
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017}}
 
|}
 
 
 
====Expected Actions====
 
The PHR shall process the results according to application-defined rules. The PHR should be robust as the response may contain DiagnosticReport, Observation and Specimen resources that match the query parameters.
 
 
 
=Release notes=
 
Release notes can be found on the [[MedMij:V2020.01/OntwerpLabresult#Release_notes| functional design page]].
 

Huidige versie van 15 dec 2023 om 13:18



Naar medmij.nl

Vaccinatie-Immunisatie

1 Introduction

This page describes patient's use case for the retrieval of vaccination results, in a personal health environment (PHR) context. Functional specifications of this use case are described at the functional design wiki page. This use case consists of enabling a patient to view his own administered vaccinations in a PHR. The technical specification is described here. HL7 FHIR R4 is used for this purpose. Vaccinations are represented by the Immunization resources in FHIR. A transaction will retrieve all administered vaccinations from the XIS.

1.1 Dependencies

2 Actors involved

Actors Systems FHIR CapabilityStatements
Name Description Name Description Name Description
Patient The user of a personal healthcare environment. PHR Personal health record CapabilityStatement: Retrieve Serve FHIR client/server requirements
(Healthcare) provider The user of a XIS XIS (Healthcare) information system

3 Use case details

Go to Afsprakenstelsel

3.1 Introduction

The retrieve vaccinations transaction is used by the PHR to retrieve vaccinations from a XIS.

3.2 Assumptions

This FHIR implementation guide assumes that the PHR system is able to make a connection to the right XIS that contains the patient's information. It does not provide information on finding the right XIS nor does it provide information about security. Moreover, each transaction is performed in the context of a specific authenticated patient, for whose context (token) has been established using the authentication mechanisms described in the 'Afsprakenstelsel'. Each XIS Gateway is required to perform filtering based on the patient associated with the context for the request, so only the records associated with the authenticated patient are returned. For this reason, search parameters should not be included for patient identification.

3.3 Actors

Transaction group Transaction Actor Role
Retrieve vaccinations(PULL) Retrieve vaccinations request Patient (using a PHR) Request vaccinations from the XIS
Retrieve vaccinations response (Healthcare) provider (using a XIS) Serves vaccinations to the PHR

3.4 Invocations

3.4.1 PHR: request message

The request message represents an HTTP GET parameterized query from the PHR to the XIS.

3.4.1.1 Trigger events

When the patient (PHR) wants to obtain vaccinations, it issues a retrieve vaccinations request message.

3.4.1.2 Message semantics

The PHR executes an HTTP GET conform to the FHIR RESTful and search specification against the XIS's Observation endpoint. This search query URL is configurable by the PHR and has the following format:

GET [base]/Immunization{?_include=Immunization:patient&_include:iterate=Immunization:performer}

At this point in time, there are no use cases for filter parameters on the query. The stated query will return a Bundle with all known administered immunizations. Each immunization is conveyed in an Immunization resource. The Immunization resource will contain references to actors such as the Patient and the Health Professional/Organization. If those references are not in the Bundle, a client SHALL be able to resolve them at the source. The client may wish to have these references resolved in the Bundle by specifying the _include parameter on the query. The server SHALL support this _include parameter. It MAY include referenced resources even if the client doesn't ask for them if it doesn't support read operations for these resources.

3.4.1.2.1 Expected actions

The XIS SHALL process the query to retrieve patient's Immunization resources and the included referenced resources.

3.4.2 XIS: response message

The XIS returns an HTTP Status code appropriate to the processing as well as a FHIR Bundle including the matching information.

3.4.2.1 Trigger events

The XIS completed processing of the retrieve vaccinations request message.

3.4.2.2 Message semantics

The returned data to the PHR should conform to the profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the .meta.profile element in order to show compliance.


Profile name FHIR Resource HCIM EN Canonical URL
nl core Vaccination event Immunization Vaccination http://nictiz.nl/fhir/StructureDefinition/nl-core-Vaccination-event
nl core Patient Patient Patient http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient
nl core HealthProfessional Practitioner HealthProfessional http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner
nl core HealthProfessional PractitionerRole PractionerRole http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole
nl core HealthcareProvider Organization Organization HealthcareProvider http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization
nl core HealthcareProvider Location http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider
nl core PharmaceuticalProduct Medication PharmaceuticalProduct http://nictiz.nl/fhir/StructureDefinition/nl-core-PharmaceuticalProduct

3.4.2.3 Expected actions

The PHR SHALL process the results. The PHR SHOULD contain all the resources that match the query and all the reference resources that are included in the Bundle.

4 Release notes

Release notes can be found on the functional design page.

5 Support

For questions and change requests regarding this IG, please create a ticket in BITS.