MedMij:Vprepub-6/FHIR Vaccination-Immunization: verschil tussen versies

Uit informatiestandaarden
Naar navigatie springen Naar zoeken springen
(Aanmaken FHIR IG voor Immunization)
 
Regel 2: Regel 2:
 
{{DISPLAYTITLE:FHIR Implementation Guide: Immunization 0.1.0}}
 
{{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].}}
 
{{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__
 +
{{DISPLAYTITLE:MedMij FHIR Implementation Guide ImmunizationResults {{VersieInfo|Immisatieresultaten}}}}
 +
{{MedMij:V2020.01/Issuebox_FHIR_IG}}
 +
 +
[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]
 +
[[Bestand:LabResults@2x.png|87px|links|Use case Medication|Medication process]]
 +
<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=
 +
[[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 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:
 +
 +
* [[MedMij:V2020.01/FHIR_LaboratoryResults#Use_case:_retrieve_laboratory_results| Retrieve laboratory results]]
 +
* [[MedMij:V2020.01/FHIR_LaboratoryResults#Use_case:_retrieve_laboratory_results_DiagnosticReport| Retrieve laboratory results DiagnosticReport]]
 +
 +
=Actors involved=
 +
{| class="wikitable"
 +
! colspan="2" style="text-align:left;" | Persons
 +
! colspan="2" style="text-align:left;" | Systems
 +
! colspan="2" style="text-align:left;" | FHIR Capability Statements
 +
|-
 +
! style="text-align:left;" |Name
 +
! style="text-align:left;" |Description
 +
! style="text-align:left;" |Name
 +
! style="text-align:left;" |Description
 +
! style="text-align:left;" |Name
 +
! style="text-align:left;" |Description
 +
|-
 +
| Patient
 +
| The user of a personal healthcare environment.
 +
| PHR
 +
| Personal health record
 +
|[[Bestand: Verwijzing.png| 20px]] {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/labresults-clientcapabilities|nictiz.fhir.nl.stu3.zib2017|title=CapabilityStatement: Client}}
 +
| LaboratoryResults process client requirements
 +
|-
 +
| Healthcare professional
 +
| The user of a XIS
 +
| XIS
 +
| 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=
 +
[[Bestand:Afsprakenstelsel-01.png|link=https://www.medmij.nl/afsprakenstelsel/|rechts |100px|Go to Afsprakenstelsel]]
 +
{{FHIR-IG-Afsprakenstelsel-Note}}
 +
 +
==Introduction==
 +
The retrieve laboratory results 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)
 +
|style="background-color: white;vertical-align:top;"|Retrieve laboratory results request
 +
|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;"|Retrieve laboratory results response
 +
|style="background-color: white;vertical-align:top;"|Healthcare professional (using a XIS)
 +
|style="background-color: white;vertical-align:top;"|Serves laboratory results to the PHR
 +
|}
 +
 +
==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 results, it issues a retrieve laboratory results request message.
 +
 +
====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:
 +
 +
<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:
 +
{| class="wikitable"
 +
! Name
 +
! 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=====
 +
The XIS shall process the query to discover Observation resources that match the search parameters given.
 +
 +
===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.
 +
 +
====Trigger Events====
 +
The XIS completed processing of the retrieve laboratory results request message.
 +
 +
====Message Semantics====
 +
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"
 +
|-style="background-color: #1F497D; color: white; font-weight: bold; "
 +
|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}}
 +
|-
 +
| 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)
 +
|style="background-color: white;vertical-align:top;"|Retrieve laboratory diagnostic report request
 +
|style="background-color: white;vertical-align:top;"|Patient (using a PHR)
 +
|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
 +
|style="background-color: white;vertical-align:top;"|Healthcare professional (using a XIS)
 +
|style="background-color: white;vertical-align:top;"|Serves laboratory diagnostic report to the PHR
 +
|}
 +
 +
==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]
 +
| The clinically relevant time of the report.
 +
| Retrieve all zib LaboratoryTestResult DiagnosticReport resources that have an effective date greater than 01-01-2010.
 +
<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]
 +
| Which diagnostic discipline/department created the report.
 +
|-
 +
| [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=====
 +
The XIS shall process the query to discover DiagnosticReport resources that match the search parameters given.
 +
 +
===XIS: response message===
 +
The XIS returns an HTTP Status code appropriate to the processing as well as a FHIR Bundle including the matching laboratory diagnostic report information.
 +
 +
====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"
 +
|-style="background-color: #1F497D; color: white; font-weight: bold; "
 +
|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]].

Versie van 4 mrt 2022 11:49


Em.png

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 here.

UNDER CONSTRUCTION --- NOT SUITED FOR TESTING OR IMPLEMENTATION


Waarschuwing:Titelweergave "MedMij FHIR Implementation Guide ImmunizationResults" overschrijft eerdere titelweergave "FHIR Implementation Guide: Immunization 0.1.0".


Naar medmij.nl
Medication process
AfsprakenstelselFunctioneelTechnischAfspraken-Functioneel-Technisch

1 Introduction

Go to functional design

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 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 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. 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.

1.1 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.

1.2 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:

2 Actors involved

Persons Systems FHIR Capability Statements
Name Description Name Description Name Description
Patient The user of a personal healthcare environment. PHR Personal health record Verwijzing.png CapabilityStatement: Client LaboratoryResults process client requirements
Healthcare professional The user of a XIS XIS Healthcare information system Verwijzing.png CapabilityStatement: Server LaboratoryResults server requirements

3 Use case: retrieve laboratory results

Go to Afsprakenstelsel

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.1 Introduction

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

3.2 Actors

Transaction group Transaction Actor Role
Retrieve Laboratory Results(PULL) Retrieve laboratory results request Patient (using a PHR) Request laboratory results from the XIS
Retrieve laboratory results response Healthcare professional (using a XIS) Serves laboratory results to the PHR

3.3 Invocations

3.3.1 PHR: request message

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

3.3.1.1 Trigger Events

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

3.3.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]/Observation?category=http://snomed.info/sct|49581000146104{&[parameters]}

The PHR may use, and the XIS shall be capable of processing, the following parameters to configure the search query:

Name Description Examples
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: 
GET [base]/Observation?category=http://snomed.info/sct|49581000146104&date=ge2010-01-01

Retrieve all zib LaboratoryTestResults Observation resources that have an effective date within a 2 year period: 

GET [base]/Observation?_include=Observation:specimen&category=http://snomed.info/sct|49581000146104date=ge2010-01-01&date=le2011-12-31
category The classification of the type of observation. Retrieve all zib LaboratoryTestResults Observation resources: 
GET [base]/Observation?category=http://snomed.info/sct|49581000146104
_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: 
GET [base]/Observation?_include=Observation:specimen&category=http://snomed.info/sct|49581000146104
3.3.1.2.1 Expected Actions

The XIS shall process the query to discover Observation resources that match the search parameters given.

3.3.2 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.

3.3.2.1 Trigger Events

The XIS completed processing of the retrieve laboratory results request message.

3.3.2.2 Message Semantics

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.

Em.png

MedMij 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.

Zib name NL Zib name EN FHIR Resource
Patient Patient Patient http://fhir.nl/fhir/StructureDefinition/nl-core-patient
Zorgverlener HealthProfessional Practitioner http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner
Zorgaanbieder HealthcareProvider Organization http://fhir.nl/fhir/StructureDefinition/nl-core-organization
LaboratoriumUitslag LaboratoryTestResult Observation http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation

3.3.2.3 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.

4 Use case: retrieve laboratory results DiagnosticReport

Go to Afsprakenstelsel

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.

4.1 Introduction

The retrieve laboratory diagnostic report transaction is used by the PHR to retrieve laboratory results from a XIS.

4.2 Actors

Transaction group Transaction Actor Role
Retrieve Laboratory Results(PULL) Retrieve laboratory diagnostic report request Patient (using a PHR) Request laboratory diagnostic report from the XIS
Retrieve laboratory diagnostic report response Healthcare professional (using a XIS) Serves laboratory diagnostic report to the PHR

4.3 Invocations

4.3.1 PHR: request message

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

4.3.1.1 Trigger Events

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

4.3.1.2 Message Semantics

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

GET [base]/DiagnosticReport?category=http://snomed.info/sct|4241000179101{&[parameters]}

The PHR may use, and the XIS shall be capable of processing, the following parameters to configure the search query:

Name Description Example(s)
date The clinically relevant time of the report. Retrieve all zib LaboratoryTestResult DiagnosticReport resources that have an effective date greater than 01-01-2010. 
GET [base]/DiagnosticReport?category=http://snomed.info/sct|4241000179101&date=ge2010-01-01

Retrieve all zib LaboratoryTestResult DiagnosticReport resources that have an effective date within a 2 year period. 

GET [base]/DiagnosticReport?category=http://snomed.info/sct|4241000179101&date=ge2010-01-01&date=le2011-12-31
category Which diagnostic discipline/department created the report.
_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. 
GET [base]/DiagnosticReport?category=http://snomed.info/sct|4241000179101&include=DiagnosticReport:result&date=ge2010-01-01&date=le2011-12-31
4.3.1.2.1 Expected Actions

The XIS shall process the query to discover DiagnosticReport resources that match the search parameters given.

4.3.2 XIS: response message

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

4.3.2.1 Trigger Events

The XIS completed processing of the retrieve laboratory diagnostic report request message.

4.3.2.2 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.

Em.png

MedMij 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.

Zib name NL Zib name EN FHIR Resource
Patient Patient Patient http://fhir.nl/fhir/StructureDefinition/nl-core-patient
Zorgverlener HealthProfessional Practitioner http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner
Zorgaanbieder HealthcareProvider Organization http://fhir.nl/fhir/StructureDefinition/nl-core-organization
LaboratoriumUitslag LaboratoryTestResult DiagnosticReport http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-DiagnosticReport
Observation http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation

4.3.2.3 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.

5 Release notes

Release notes can be found on the functional design page.

Overgenomen van "https://informatiestandaarden.test-nictiz.nl/index.php?title=MedMij:Vprepub-6/FHIR_Vaccination-Immunization&oldid=102093"