MedMij:Vprepub-2019.01 FHIR AllergyIntolerance: verschil tussen versies

Uit informatiestandaarden
Naar navigatie springen Naar zoeken springen
(Copy of Vdraft)
 
(Replace the deprecation issuebox)
 
(39 tussenliggende versies door 12 gebruikers niet weergegeven)
Regel 1: Regel 1:
−
{{#customtitle:MedMij FHIR Implementation Guide AllergyIntolerance 1.1.0}}
+
{{MedMij:Vprepub-2019.01_AllergieIntolerantie2_Uitgefaseerd}}
−
{{MedMij:V2019.01_Issuebox_FHIR_IG}}
+
__NOINDEX__
 +
{{DISPLAYTITLE:MedMij FHIR Implementation Guide AllergyIntolerance {{VersieInfo|AllergieIntolerantie|release=V2019.01}}}}
 +
{{MedMij:Vprepub-2019.01_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]]
Regel 6: Regel 8:
 
<imagemap>Bestand:Leeswijzer-technisch-banner 03 white.png|center|400px|alt=Afspraken-Functioneel-Technisch   
 
<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 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]                 
−
circle 1013 224 212 [[MedMij:V2019.01_OntwerpAllergieIntolerantie|Functioneel]]                 
+
circle 1013 224 212 [[MedMij:Vprepub-2019.01_OntwerpAllergieIntolerantie|Functioneel]]                 
−
circle 1787 230 212 [[MedMij:V2019.01_FHIR_IG|Technisch]]                 
+
circle 1787 230 212 [[MedMij:Vprepub-2019.01_FHIR_IG|Technisch]]                 
 
desc none                     
 
desc none                     
 
</imagemap>
 
</imagemap>
Regel 15: Regel 17:
  
 
=Introduction=
 
=Introduction=
−
[[Bestand:Functioneel-02.png|link=MedMij:V2019.01_Ontwerpen |100px|rechts|Functional design|Go to functional design]]
+
[[Bestand:Functioneel-02.png|link=MedMij:Vprepub-2019.01_Ontwerpen |100px|rechts|Functional design|Go to functional design]]
  
−
This page describes a patient's use case, in a personal health record (PHR) context, for exchanging allergy and intolerance data. Functional specification of this use case is described in the [[MedMij:V2019.01_Ontwerpen| functional design wiki pages]]. The technical specification is described here. HL7 FHIR STU3 is used for this purpose.
+
This page describes a patient's use case, in a personal health record (PHR) context, for exchanging allergy and intolerance data. Functional specification of this use case is described in the [[MedMij:Vprepub-2019.01_Ontwerpen| functional design wiki pages]]. The technical specification is described here. HL7 FHIR STU3 is used for this purpose.
  
 
=Actors involved=
 
=Actors involved=
Regel 36: Regel 38:
 
| PHR
 
| PHR
 
| Personal health record
 
| Personal health record
−
|[[Bestand: Verwijzing.png| 20px]] [https://simplifier.net/resolve?target=simplifier&canonical=http://nictiz.nl/fhir/CapabilityStatement/allergyintolerance-clientcapabilities CapabilityStatement: Client]
+
|[[Bestand: Verwijzing.png| 20px]] {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/allergyintolerance-clientcapabilities|nictiz.fhir.nl.stu3.zib2017|pkgVersion=1.3.12|title=CapabilityStatement: Client}}
 
| AllergyIntolerance client requirements  
 
| AllergyIntolerance client requirements  
 
|-
 
|-
Regel 43: Regel 45:
 
| XIS
 
| XIS
 
| Healthcare information system
 
| Healthcare information system
−
|[[Bestand: Verwijzing.png| 20px]] [https://simplifier.net/resolve?target=simplifier&canonical=http://nictiz.nl/fhir/CapabilityStatement/allergyintolerance-servercapabilities CapabilityStatement: Server]
+
|[[Bestand: Verwijzing.png| 20px]] {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/allergyintolerance-servercapabilities|nictiz.fhir.nl.stu3.zib2017|pkgVersion=1.3.12|title=CapabilityStatement: Server}}
 
| AllergyIntolerance server requirements  
 
| AllergyIntolerance server requirements  
 
|}
 
|}
Regel 91: Regel 93:
  
 
===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 allergy and intolerance medication information.
+
The XIS returns an HTTP Status code appropriate to the processing as well as a FHIR Bundle including the allergy and intolerance information.
  
 
====Trigger Events====
 
====Trigger Events====
Regel 106: Regel 108:
  
 
=====Message resource content=====
 
=====Message resource content=====
−
The returned data to the PHR should conform to the ZIB AllergyIntolerance profile. The table below shows the relevant ZIBs and their profiles. 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.  
+
The returned data to the PHR should conform to the zib AllergyIntolerance profile. The table below shows the relevant zibs and their profiles. 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.  
  
−
{{NoteBoxPackage|https://simplifier.net/packages/nictiz.fhir.nl.stu3.zib2017/1.1.0|1.1.0|MedMij:V2019.01_FHIR_IG}}
+
{{NoteBoxPackage|https://simplifier.net/NictizSTU3-Zib2017/~packages|1.3.x|MedMij:V2019.01_FHIR_IG}}
  
 
{| class="wikitable"  
 
{| class="wikitable"  
−
|-style="background-color: #1F497D; color: white; font-weight: bold; "
+
|-style="background-color: #1F497D; color: white; font-weight: bold; text-align:left;  background-color: #E3E3E3 width:100px"
−
|ZIB name NL||ZIB name EN||FHIR Resource||URL profile
+
|Zib name NL||Zib name EN||FHIR Resource||URL profile
 
|-style="vertical-align:top; background-color: #E3E3E3;  
 
|-style="vertical-align:top; background-color: #E3E3E3;  
 
|-
 
|-
 
| Patient
 
| Patient
−
| #ZIB Patient|Patient
+
| #Zib Patient|Patient
 
| Patient
 
| Patient
−
| [https://simplifier.net/resolve?target=simplifier&canonical=http://fhir.nl/fhir/StructureDefinition/nl-core-patient http://fhir.nl/fhir/StructureDefinition/nl-core-patient]
+
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|nictiz.fhir.nl.stu3.zib2017|pkgVersion=1.3.12}}
−
|-
 
−
| Zorgverlener
 
−
| HealthProfessional
 
−
| Practitioner
 
−
| [https://simplifier.net/resolve?target=simplifier&canonical=http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner]
 
 
|-
 
|-
 
| AllergieIntolerantie
 
| AllergieIntolerantie
 
| AllergyIntolerance
 
| AllergyIntolerance
 
| AllergyIntolerance
 
| AllergyIntolerance
−
| [https://simplifier.net/resolve?target=simplifier&canonical=https://simplifier.net/resolve?target=simplifier&canonical=https://simplifier.net/resolve?target=simplifier&canonical=http://nictiz.nl/fhir/StructureDefinition/zib-AllergyIntolerance http://nictiz.nl/fhir/StructureDefinition/zib-AllergyIntolerance]
+
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AllergyIntolerance|nictiz.fhir.nl.stu3.zib2017|pkgVersion=1.3.12}}
 +
|-
 +
| rowspan="2" | Zorgverlener
 +
| rowspan="2" | HealthProfessional
 +
| Practitioner
 +
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=1.3.12}}
 +
|-
 +
| PractitionerRole
 +
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nictiz.fhir.nl.stu3.zib2017|pkgVersion=1.3.12}}
 +
|-
 +
| Zorgaanbieder
 +
| HealthcareProvider
 +
| Organization
 +
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=1.3.12}}
 +
|-
 +
| Contactpersoon
 +
| ContactPerson
 +
| Patient.contact
 +
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=1.3.12}}
 
|}
 
|}
 +
{{Sjabloon:Voorbeelden}}
  
 
====Expected Actions====
 
====Expected Actions====
Regel 136: Regel 152:
 
==Interactions, operations, search parameters==  
 
==Interactions, operations, search parameters==  
 
===Interactions===
 
===Interactions===
−
The following logical interactions are needed for the retrieve medication information transaction:
+
The following logical interactions are needed for the retrieve AllergyIntolerance information transaction:
 
* [http://hl7.org/fhir/STU3/http.html#search Search]
 
* [http://hl7.org/fhir/STU3/http.html#search Search]
  
Regel 145: Regel 161:
 
No search parameters are defined or needed for this transaction.
 
No search parameters are defined or needed for this transaction.
  
−
=Terminology, NamingSystems, Mappings=
+
=Use case: Retrieve AllergyIntolerance612ToFHIRConversion =
 +
{{FHIR-IG-Afsprakenstelsel-Note}}
 +
 
 +
==Introduction==
 +
A PHR uses the retrieve AllergyIntolerance612ToFHIRConversion transaction to retrieve "6.12-based" allergy and intolerance information from a XIS. This information is based on a conversion from the [https://www.nictiz.nl/standaardisatie/informatiestandaarden/medicatieveiligheid/ 6.12 information standard]. The XIS converts the requested information by a PHR to FHIR-resources.
 +
 
 +
The 6.12 AllergyIntolerance information is originally exchanged in HL7v3-messaging format. For interested readers the HL7v3-specifications can be found in the [http://decor.nictiz.nl/medicatieproces/mp-html-20181220T121121/tmp-2.16.840.1.113883.2.4.3.11.60.20.77.10.12-2013-08-19T000000.html 6.12 template for 'potential contraindications'].
  
−
===Terminology===
+
However, please note that it is not necessary for a PHR to have knowledge of the HL7v3-format to implement this use case.
−
Relevant ValueSets can be found through the ValueSet bindings in the listed StructureDefinitions. All ValueSets can be found here [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=ValueSet here] and can be downloaded as a .zip in XML or JSON format.
 
  
−
===NamingSystems===
+
==Actors==
−
Relevant NamingSystems can be found [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=NamingSystem here].
+
{| 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="3"|Retrieve AllergyIntolerance612ToFHIRConversion (PULL)
 +
|style="background-color: white;vertical-align:top;"|Retrieve AllergyIntolerance612ToFHIRConversion request
 +
|style="background-color: white;vertical-align:top;"|Patient (using a PHR)
 +
|style="background-color: white;vertical-align:top;"|Request allergy and intolerance information from the XIS
 +
|-
 +
|style="background-color: white;vertical-align:top;"|Retrieve AllergyIntolerance612ToFHIRConversion response
 +
|style="background-color: white;vertical-align:top;"|Healthcare professional (using a XIS)
 +
|style="background-color: white;vertical-align:top;"|Serves allergy and intolerance information to the PHR
 +
|}
  
−
===Mappings===
+
==Invocations==
−
A FHIR ConceptMap resource is provided when a FHIR value set is used instead of a HCIM value set. A ConceptMap maps the values between the two value sets. These ConceptMaps can be found [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=ConceptMap here].
+
===PHR: request message===
 +
The request message represents an HTTP GET query from the PHR to the XIS.
  
−
All profiles include HCIM mappings. HCIM concepts are mapped to the corresponding FHIR elements using the HCIMs concept id. The top of the StructureDefinition contains meta information regarding the HCIM mapping, such as the name and uri of the HCIM. In the StructureDefinition elements, the corresponding HCIM ID is given including the mapping meta information id. This is illustrated in the following example.
+
====Trigger Events====
 +
When the patient(PHR) wants to obtain allergy and intolerance information, it issues a retrieve AllergyIntolerance612ToFHIRConversion 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 AllergyIntolerance612ToFHIRConversion endpoint. This search query has the following format.
 +
 
<pre>
 
<pre>
−
<StructureDefinition>
+
GET [base]/AllergyIntolerance
−
    <id value="nl-core-patient" />
 
−
    .....
 
−
    <mapping>
 
−
        <identity value="hcim-patient-v3.1-2017EN"/>
 
−
        <uri value="https://zibs.nl/wiki/Patient-v3.1(2017EN)"/>
 
−
        <name value="HCIM Patient-v3.1(2017EN)"/>
 
−
    </mapping>
 
−
    .....
 
−
        <element id="Patient.name">
 
−
            <path value="Patient.name" />
 
−
            <short value="NameInformation" />
 
−
            <alias value="Naamgegevens" />
 
−
            <type>
 
−
                <code value="HumanName" />
 
−
                <profile value="http://fhir.nl/fhir/StructureDefinition/nl-core-humanname" />
 
−
            </type>
 
−
            <mapping>
 
−
                <identity value="hcim-patient-v3.1-2017EN"/>
 
−
                <map value="NL-CM:0.1.6"/>
 
−
            </mapping>
 
−
        </element>
 
−
    .....
 
−
</StructureDefinition>
 
 
</pre>
 
</pre>
  
−
=Annex: Document history=
+
=====Search Parameters=====
−
==Release notes==
+
No query parameters are defined for this use case. The PHR searches on all AllergyIntolerance resources available for the patient using a HTTP GET on the AllergyIntolerance endpoint without parameters.
−
Release notes can be found on the [[MedMij:V2019.01_OntwerpAllergieIntolerantie#Release_notes|functional design page]].
+
 
 +
=====Expected Actions=====
 +
The XIS shall process the query to discover AllergyIntolerance resources that are part of the 6.12 information standard and match the patient in the context.
 +
 
 +
===XIS: response message===
 +
The XIS returns an HTTP Status code appropriate to the processing as well as a FHIR Bundle including the appropriate allergy and intolerance information.
 +
 
 +
====Trigger Events====
 +
The XIS completed processing of the Retrieve AllergyIntolerance request message.
 +
 
 +
====Message Semantics====
 +
Based on the query results, the XIS will either return an error or success. When the XIS needs to report an error, it SHALL use HTTP error response codes and SHOULD include a FHIR OperationOutcome resource with more details on the failure. If the request message is processed successfully, whether or not any AllergyIntolerance resources are found, the HTTP status code SHALL be 200.
 +
 
 +
The response message shall be a Bundle resource of type "searchset" containing zero or more FHIR resources as entries. If the XIS is sending warnings, the Bundle resource SHALL also contain a FHIR OperationOutcome resource that contains those warnings. The FHIR specification describes the relevant sections:
 +
*[http://hl7.org/fhir/STU3/http.html RESTful API framework]
 +
*[http://hl7.org/fhir/STU3/search.html#errors Search errors]
 +
*[http://hl7.org/fhir/STU3/bundle.html Bundle resource]
 +
*[http://hl7.org/fhir/operationoutcome.html OperationOutcome resource]
 +
 
 +
=====Message resource content=====
 +
The returned data to the PHR should conform to the zib AllergyIntolerance profile. The table below shows the relevant zibs and their profiles. 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.  
  
−
==History==
+
{{NoteBoxPackage|https://simplifier.net/NictizSTU3-Zib2017/~packages|1.3.x|MedMij:V2019.01_FHIR_IG}}
−
{| class="wikitable" "cellpadding="10"
+
 
−
!style="text-align:left;"|Release
+
{| class="wikitable"  
−
!style="text-align:left;"|Date
+
|-style="background-color: #1F497D; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:100px"
−
!style="text-align:left;"|Description
+
|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|pkgVersion=1.3.12}}
 +
|-
 +
| AllergieIntolerantie
 +
| AllergyIntolerance
 +
| AllergyIntolerance
 +
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp612-AllergyIntoleranceToFHIRConversion|nictiz.fhir.nl.stu3.zib2017|pkgVersion=1.3.12}}
 +
|-
 +
| rowspan="2" | Zorgverlener
 +
| rowspan="2" | HealthProfessional
 +
| Practitioner
 +
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=1.3.12}}
 
|-
 
|-
−
| style="background-color: white;"| 2019.01
+
| PractitionerRole
−
| style="background-color: white;"| 24-01-2019
+
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nictiz.fhir.nl.stu3.zib2017|pkgVersion=1.3.12}}
−
| style="background-color: white;"| Moved release notes to the functional design page.<br/>[https://bits.nictiz.nl/browse/MM-70 MM-70] Updated links for profiles so they have less maintenance
 
 
|-
 
|-
−
| style="background-color: white;"| 2018.06
+
| Zorgaanbieder
−
| style="background-color: white;"| 12-11-2018
+
| HealthcareProvider
−
| style="background-color: white;"| Added section about Terminology, NamingSystems, Mappings
+
| Organization
 +
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=1.3.12}}
 
|-
 
|-
−
| style="background-color: white;"| 2018.06
+
| Contactpersoon
−
| style="background-color: white;"| 15-10-2018
+
| ContactPerson
−
| style="background-color: white;"| Added version in title, and document history
+
| Patient.contact
 +
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=1.3.12}}
 
|}
 
|}
 +
{{Sjabloon:Voorbeelden}}
 +
 +
====Expected Actions====
 +
The PHR processes the results according to application-defined rules. The PHR should be robust as the response may contain AllergyIntolerance information resources as mentioned in the former section.
 +
 +
==Interactions, operations, search parameters==
 +
===Interactions===
 +
The following logical interactions are needed for the retrieve AllergyIntolerance612ToFHIRConversion transaction:
 +
* [http://hl7.org/fhir/STU3/http.html#search Search]
 +
 +
===Operations===
 +
No operations are defined or needed for this transaction.
 +
 +
===Search parameters===
 +
No search parameters are defined or needed for this transaction.
 +
 +
=Terminology, NamingSystems, Mappings=
 +
{{MedMij:Vprepub-2019.01_Template_Terminologies_NamingSystems_Mappings|id1=Message_resource_content|t1=Retrieve AllergyIntolerance response message content|id2=Message_resource_content_2|t2=Retrieve AllergyIntolerance612ToFHIRConversion response message content}}
  
−
[[categorie:MedMij FHIR Use Cases]]
+
=Release notes=
 +
Release notes can be found on the [[MedMij:Vprepub-2019.01_OntwerpAllergieIntolerantie#Release_notes|functional design page]].
 +
{{EindUitgefaseerd}}

Huidige versie van 13 sep 2022 om 13:14

Icoon Nictiz Cirkel Informatie Grafiet.svg

Deze versie van de informatiestandaard is per 1-7-2022 uitgefaseerd. Zie de MedMij-overzichtspagina voor de actuele versies van de MedMij-informatiestandaarden.

This version of this information standard has been deprecated as of 1-7-2022. Consult the MedMij overview page for the current versions of MedMij information standards.



Naar medmij.nl
AllergyIntolerance
AfsprakenstelselFunctioneelTechnischAfspraken-Functioneel-Technisch


Introduction

Go to functional design

This page describes a patient's use case, in a personal health record (PHR) context, for exchanging allergy and intolerance data. Functional specification of this use case is described in the functional design wiki pages. The technical specification is described here. HL7 FHIR STU3 is used for this purpose.

Actors involved

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

Use case: Retrieve AllergyIntolerance information

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.

Introduction

The retrieve AllergyIntolerance transaction is used by the PHR to retrieve allergy and intolerance information from the XIS.

Actors

Transaction group Transaction Actor Role
Retrieve AllergyIntolerance(PULL) Retrieve AllergyIntolerance request Patient (using a PHR) Request allergy and intolerance information from the XIS
Retrieve AllergyIntolerance response Healthcare professional (using a XIS) Serves allergy and intolerance information to the PHR

Invocations

PHR: request message

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

Trigger Events

When the patient(PHR) wants to obtain allergy and intolerance information, it issues a retrieve AllergyIntolerance request message.

Message Semantics

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

GET [base]/AllergyIntolerance
Search Parameters

No query parameters are defined for this use case. The PHR searches on all AllergyIntolerance resources available for the patient using a HTTP GET on the AllergyIntolerance endpoint without parameters.

Expected Actions

The XIS shall process the query to discover AllergyIntolerance resources that match the patient in the context.

XIS: response message

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

Trigger Events

The XIS completed processing of the Retrieve AllergyIntolerance request message.

Message Semantics

Based on the query results, the XIS will either return an error or success. When the XIS needs to report an error, it SHALL use HTTP error response codes and SHOULD include a FHIR OperationOutcome resource with more details on the failure. If the request message is processed successfully, whether or not any AllergyIntolerance resources are found, the HTTP status code SHALL be 200.

The response message shall be a Bundle resource of type "searchset" containing zero or more FHIR resources as entries. If the XIS is sending warnings, the Bundle resource SHALL also contain a FHIR OperationOutcome resource that contains those warnings. The FHIR specification describes the relevant sections:

Message resource content

The returned data to the PHR should conform to the zib AllergyIntolerance profile. The table below shows the relevant zibs and their profiles. 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 examples, profiles and other conformance resources you need into a single download. For more background information see the the FHIR implementation guide. This version of the information standard depends on Nictiz package 1.3.x. 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.
Zib name NL Zib name EN FHIR Resource URL profile
Patient Patient Patient http://fhir.nl/fhir/StructureDefinition/nl-core-patient
AllergieIntolerantie AllergyIntolerance AllergyIntolerance http://nictiz.nl/fhir/StructureDefinition/zib-AllergyIntolerance
Zorgverlener HealthProfessional Practitioner http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner
PractitionerRole http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole
Zorgaanbieder HealthcareProvider Organization http://fhir.nl/fhir/StructureDefinition/nl-core-organization
Contactpersoon ContactPerson Patient.contact http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson

Example instances of FHIR resources can be found on Simplifier. Please note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of any information standard.

Expected Actions

The PHR processes the results according to application-defined rules. The PHR should be robust as the response may contain AllergyIntolerance information resources as mentioned in the former section.

Interactions, operations, search parameters

Interactions

The following logical interactions are needed for the retrieve AllergyIntolerance information transaction:

Operations

No operations are defined or needed for this transaction.

Search parameters

No search parameters are defined or needed for this transaction.

Use case: Retrieve AllergyIntolerance612ToFHIRConversion

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.

Introduction

A PHR uses the retrieve AllergyIntolerance612ToFHIRConversion transaction to retrieve "6.12-based" allergy and intolerance information from a XIS. This information is based on a conversion from the 6.12 information standard. The XIS converts the requested information by a PHR to FHIR-resources.

The 6.12 AllergyIntolerance information is originally exchanged in HL7v3-messaging format. For interested readers the HL7v3-specifications can be found in the 6.12 template for 'potential contraindications'.

However, please note that it is not necessary for a PHR to have knowledge of the HL7v3-format to implement this use case.

Actors

Transaction group Transaction Actor Role
Retrieve AllergyIntolerance612ToFHIRConversion (PULL) Retrieve AllergyIntolerance612ToFHIRConversion request Patient (using a PHR) Request allergy and intolerance information from the XIS
Retrieve AllergyIntolerance612ToFHIRConversion response Healthcare professional (using a XIS) Serves allergy and intolerance information to the PHR

Invocations

PHR: request message

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

Trigger Events

When the patient(PHR) wants to obtain allergy and intolerance information, it issues a retrieve AllergyIntolerance612ToFHIRConversion request message.

Message Semantics

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

GET [base]/AllergyIntolerance
Search Parameters

No query parameters are defined for this use case. The PHR searches on all AllergyIntolerance resources available for the patient using a HTTP GET on the AllergyIntolerance endpoint without parameters.

Expected Actions

The XIS shall process the query to discover AllergyIntolerance resources that are part of the 6.12 information standard and match the patient in the context.

XIS: response message

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

Trigger Events

The XIS completed processing of the Retrieve AllergyIntolerance request message.

Message Semantics

Based on the query results, the XIS will either return an error or success. When the XIS needs to report an error, it SHALL use HTTP error response codes and SHOULD include a FHIR OperationOutcome resource with more details on the failure. If the request message is processed successfully, whether or not any AllergyIntolerance resources are found, the HTTP status code SHALL be 200.

The response message shall be a Bundle resource of type "searchset" containing zero or more FHIR resources as entries. If the XIS is sending warnings, the Bundle resource SHALL also contain a FHIR OperationOutcome resource that contains those warnings. The FHIR specification describes the relevant sections:

Message resource content

The returned data to the PHR should conform to the zib AllergyIntolerance profile. The table below shows the relevant zibs and their profiles. 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 examples, profiles and other conformance resources you need into a single download. For more background information see the the FHIR implementation guide. This version of the information standard depends on Nictiz package 1.3.x. 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.
Zib name NL Zib name EN FHIR Resource URL profile
Patient Patient Patient http://fhir.nl/fhir/StructureDefinition/nl-core-patient
AllergieIntolerantie AllergyIntolerance AllergyIntolerance http://nictiz.nl/fhir/StructureDefinition/mp612-AllergyIntoleranceToFHIRConversion
Zorgverlener HealthProfessional Practitioner http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner
PractitionerRole http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole
Zorgaanbieder HealthcareProvider Organization http://fhir.nl/fhir/StructureDefinition/nl-core-organization
Contactpersoon ContactPerson Patient.contact http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson

Example instances of FHIR resources can be found on Simplifier. Please note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of any information standard.

Expected Actions

The PHR processes the results according to application-defined rules. The PHR should be robust as the response may contain AllergyIntolerance information resources as mentioned in the former section.

Interactions, operations, search parameters

Interactions

The following logical interactions are needed for the retrieve AllergyIntolerance612ToFHIRConversion transaction:

Operations

No operations are defined or needed for this transaction.

Search parameters

No search parameters are defined or needed for this transaction.

Terminology, NamingSystems, Mappings

Relevant ValueSets, NamingSystems and ConceptMaps can be found in the packages referenced in the Retrieve AllergyIntolerance response message content and Retrieve AllergyIntolerance612ToFHIRConversion response message content sections.

The HCIM ValueSets used in the profiles are included in the package (or one of its dependencies). When a FHIR core ValueSet must be used instead of an HCIM ValueSet, a FHIR ConceptMap resource is provided to map the values between the two sets. An explanation about mappings can be found at in the overarching principles.

Release notes

Release notes can be found on the functional design page.

Overgenomen van "https://informatiestandaarden.test-nictiz.nl/index.php?title=MedMij:Vprepub-2019.01_FHIR_AllergyIntolerance&oldid=131274"