Brontekst bekijken van MedMij:Vprepub-2019.01 FHIR BGLZ

{{#customtitle:MedMij FHIR Implementation Guide: BgLZ 1.0.1}}
{{MedMij:V2019.01_Issuebox_FHIR_IG}}

[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]
[[Bestand:BgLZ-icon.png |link=|links|90px|Use case BgZ 2017|Patient Summary (BgZ)]] 
<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:V2019.01_OntwerpLangdurigeZorg|Functioneel]]                
circle 1787 230 212 [[MedMij:V2019.01_FHIR_IG|Technisch]]                
desc none                    
</imagemap>

__TOC__

=Introduction=
[[Bestand:Functioneel-02.png|link=MedMij:V2019.01_Ontwerpen |100px|rechts|Functional design|Go to functional design]]

This page provides the technical specification of the exchange of long-term healthcare information (Dutch: Basisgegevens Langdurige Zorg or BgLZ) based on a selection of Dutch Health Care Information Models. The specification is based on this [[MedMij:V2019.01_OntwerpLangdurigeZorg|functional design]]. 

=Actors involved=
{| class="wikitable"
! colspan="2" style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;" | Actors
! colspan="2" style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;" | Systems
! colspan="2" style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;" | FHIR Capability Statements
|-
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Name
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Description
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Name
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Description
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Name
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Description
|-
| Patient
| The user of a personal healthcare enviorment.
| PHR
| Personal health record
|[[Bestand: Verwijzing.png| 20px]] [https://simplifier.net/resolve?target=simplifier&canonical=http://nictiz.nl/fhir/CapabilityStatement/bglz-clientcapabilities CapabilityStatement: Client]
| FHIR Client requirements 
|-
| Healthcare professional
| The user of a XIS
| XIS
| Healthcare information system
|[[Bestand: Verwijzing.png| 20px]] [https://simplifier.net/resolve?target=simplifier&canonical=http://nictiz.nl/fhir/CapabilityStatement/bglz-servercapabilities CapabilityStatement: Server]
| FHIR Server requirements 
|}

=Boundaries and Relationships=
The BgLZ has similarities with the [[MedMij:V2019.01_FHIR_BGZ_2017|Basisgegevensset Zorg (BgZ)]] and [[MedMij:V2019.01_FHIR_GGZ|Basisgegevens GGZ (GGZ)]] but is definitely different. These information standards use much of the same HCIM based FHIR profiles for exchanging information. Wherever possible every attempt is made to re-use profiles. The BgLZ use case also has unique profiles compared to the aforementioned use cases, such as OutcomeOfCare. In addition, it uses a CareTeam profile without an underlying HCIM.
A second thing to note is that also the selection of requested information per HCIM may differentiate. For example, only a subset of LaboratoryResults or AllergyIntolerance is expected to be returned by a XIS. [[MedMij:V2019.01_InhoudLangdurigeZorg|This page]], which belongs to the BgLZ functional design, and related [https://decor.nictiz.nl/decor/services/RetrieveTransaction?id=2.16.840.1.113883.2.4.3.11.60.58.4.3&effectiveDate=2019-04-09T16:33:35&language=nl-NL&ui=nl-NL&format=html&hidecolumns=34567 transactions] provide details on the information that is expected to be exchanged. 

Medication information is part of a good overview of patients in long-term healthcare. Retrieving medication information by a PHR is however out of scope for this information standard. A separate information standard, [[MedMij:V2019.01_FHIR_MedicationProcess|MedicationProcess]], is intended to serve this purpose.

=Use case: Retrieve BgLZ information=
{{FHIR-IG-Afsprakenstelsel-Note}}

[[Bestand:Afsprakenstelsel-01.png|link=https://www.medmij.nl/afsprakenstelsel/|rechts |100px|Go to Afsprakenstelsel]]

==Introduction==
The retrieve BgLZ transaction is used by the PHR to retrieve long-term healthcare information from a XIS.

==Actors==
{| class="wikitable" "cellpadding="10"
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Transaction group'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Transaction'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Actor'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Role'''
|-
|style="background-color: white;" rowspan="3"|Retrieve BgLZ (PULL)
|style="background-color: white;vertical-align:top;"|Retrieve BgLZ request
|style="background-color: white;vertical-align:top;"|Patient (using a PHR)
|style="background-color: white;vertical-align:top;"|Request long-term healthcare information from a XIS
|-
|style="background-color: white;vertical-align:top;"|Retrieve BgLZ response
|style="background-color: white;vertical-align:top;"|Healthcare professional (using a XIS)
|style="background-color: white;vertical-align:top;"|Serves long-term healthcare information to a PHR
|}

==Invocations==

===PHR: request message===
The PHR system requests the BgLZ using individual search interactions. The BgLZ consists of multiple FHIR resources with certain constraints. To obtain the patient's BgLZ, the client can use multiple individual search operations based on specified search queries. The interactions are performed by an HTTP GET as shown:

<code>GET [base]/[type]/{?[parameters]{&_format=[mime-type]}}</code>

The table below shows in the first four columns the BgLZ sections, the HCIMs that constitute those sections and the specific content of the BgLZ. The last column shows the FHIR search queries to obtain the BgLZ information. These queries and expected responses are based on StructureDefinitions listed in [[#List_of_StructureDefinitions| this section]].

{| class="wikitable collapsible" width="100%" style="horizontal-align: right"  
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;  background-color: #E3E3E3 width:10px" | #
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;  background-color: #E3E3E3 width:10px" | BgLZ Section
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;  background-color: #E3E3E3 width:10px" | HCIM EN
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;  background-color: #E3E3E3 width:10px" | Content
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;  background-color: #E3E3E3  width:10px" | Search URL
|-
| 1
| Patient information
| Patient
| Identification, birthdate, gender, deceasedindicator, contact details, marital status, and general practitioner (practitioner or organization)
| <pre>GET [base]/Patient?_include=Patient:general-practitioner</pre>
|-
| rowspan="2" | 2
| rowspan="2" | Treatment Directives
| TreatmentDirective
| Known treatment directives
| <pre>GET [base]/Consent?category=http://snomed.info/sct|11291000146105</pre>
|-
| AdvanceDirective
| Known advance directives
| <pre>GET [base]/Consent?category=http://snomed.info/sct|11341000146107</pre>
|-
| 3
| Contactperson
| ContactPerson
| First relation/contact
| <pre style="font-style: italic;">see Patient in Patient.contact</pre>
|-
| 4
| Problems
| Problem
| All known problems including diagnoses; no verification status
| <pre>GET [base]/Condition</pre>
|-
| 5
| Allergies
| AllergyIntolerance
| A selection of information from all known allergies and intolerances. The [https://decor.nictiz.nl/decor/services/RetrieveTransaction?id=2.16.840.1.113883.2.4.3.11.60.58.4.3&effectiveDate=2019-04-09T16:33:35&language=nl-NL&ui=nl-NL&format=html&hidecolumns=34567 ART-DECOR transaction] specification describes the selection.
| <pre>GET [base]/AllergyIntolerance</pre>
|-
| 6
| Results
| LaboratoryTestResult
| A selection of infromation from the last known clinical laboratory results per type. The [https://decor.nictiz.nl/decor/services/RetrieveTransaction?id=2.16.840.1.113883.2.4.3.11.60.58.4.3&effectiveDate=2019-04-09T16:33:35&language=nl-NL&ui=nl-NL&format=html&hidecolumns=34567 ART-DECOR transaction] specification describes the selection.
| <pre>GET [base]/Observation/$lastn?category=http://snomed.info/sct|275711006&_include=Observation:related-target&_include=Observation:specimen</pre>
|-
| 7
| Procedures
| Procedure
| All procedures
| <pre>GET [base]/Procedure</pre>
|-
| rowspan="4" | 8
| rowspan="4" | Goals and interventions 
''* see the NoteBox above''
| NursingIntervention
| NursingInterventions beloning to active problems
| rowspan="4" | <pre>GET [base]/CarePlan?_include=CarePlan:activity-goal:Goal
&_include=CarePlan:activity-outcomereference:Observation
&_include=CarePlan:activity-medicaldevice:DeviceUseStatement
&_include:recurse=DeviceUseStatement:device:Device</pre>
|-
| TreatmentObjective
| All treatment objectives beloning to NursingInterventions
|-
| MedicalDevice
| All MedicalDevices belonging to NursingInterventions; only product type and anatomical location
|-
| OutcomeOfCare
| Known treatment outcomes
|-
| rowspan="2" | 9
| rowspan="2" | Caresetting / CareTeam
| HealthProfessional
| rowspan="2" | 
* General practitioner of the patient ''(see Patient.general-pracitioner)''
* Primary practitioner - information of the primary care giver, no ID, adress/contact information
* Other practitioners - information of all practitioners given care to the patient, no ID, adress/contact information
* Healthcare provider - organization where care is given
| rowspan="2" | <pre>GET [base]/CareTeam?_include=CareTeam:participant</pre>
|-
| HealthcareProvider
|}

===XIS: response message===
Important sections of the FHIR specification for a server in this use case are the [http://hl7.org/fhir/STU3/http.html#2.21.0 RESTful API section] the [http://hl7.org/fhir/STU3/search.html search section] and [http://hl7.org/fhir/STU3/operations.html operation section] (for the nlast operation).

====Response to resource requests====
If the search succeeds, the server SHALL return a 200 OK HTTP status code and the returned content SHALL be a Bundle with type = searchset containing the results of the search as a collection of zero or more resources in a defined order. The returned resources SHALL conform to the StructureDefinition applicable for the specific HCIM request. The list of StructureDefinitions relevant for this use case is shown in the following paragraph: [[#List_of_StructureDefinitions | List of StructureDefinitions]]. All resources SHALL include their related StructureDefinition canonical URL in the meta.profile element in order to show compliance.

The result collection can be long, so servers may use paging. If they do, they SHALL use the method described below (adapted from RFC 5005 (Feed Paging and Archiving ) for breaking the collection into pages if appropriate. The server MAY also return an [http://hl7.org/fhir/stu3/operationoutcome.html OperationOutcome resource] within the searchset Bundle entries that contains additional information about the search; if one is sent it SHALL NOT include any issues with a fatal or error severity, and it SHALL be marked with a Bundle.entry.search.mode of outcome.

In order to allow the client to be confident about what search parameters were used as criteria by the server, the server SHALL return the parameters that were actually used to process the search. Applications processing search results SHALL check these returned values where necessary. For example, if the server did not support some of the filters specified in the search, a client might manually apply those filters to the retrieved result set, display a warning message to the user or take some other action. Link to the relevant FHIR specification: http://hl7.org/fhir/STU3/http.html#search

====Handling errors====
If the search fails '''(cannot be executed, not that there are no matches)''', the return value is a status code 4xx or 5xx with an OperationOutcome. An HTTP status code of 403 signifies that the server refused to perform the search, while other 4xx and 5xx codes signify that some sort of error has occurred. The HTTP status code 404 is returned if a XIS did not implement an endpoint used in a request by a PHR. When the search fails, a server SHOULD return an OperationOutcome detailing the cause of the failure. For example, in case of a not implemented FHIR endpoint, the OperationOutcome would state that the resource type is not supported. Note: an empty search result is not a failure.

Common HTTP Status codes returned on FHIR-related errors (in addition to normal HTTP errors related to security, header and content type negotiation issues):

* 400 Bad Request - search could not be processed or failed basic FHIR validation rules
* 401 Not Authorized - authorization is required for the interaction that was attempted
* 404 Not Found - resource type not supported, or not a FHIR end-point

In some cases, parameters may cause an error. For instance:

* A parameter may refer to an unknown code e.g. <code>GET [base]/Observation?code=1234-1</code>, where the code "1234-1" is not known to the server
* A parameter may refer to a time that is out of scope e.g. <code>GET [base]/Condition?onset=le1995</code>, where the system only has data going back to 2001
* A parameter may use an illegal or unacceptable modifier e.g. <code>GET [base]/Condition?onset:text=1995</code>, where the modifier cannot be processed by the server
* A date/time parameter may have incorrect format e.g. <code>GET [base]/Condition?onset=23%20May%202009</code>
* A parameter may be unknown or unsupported 

Where the content of the parameter is syntactically incorrect, servers SHOULD return an error. However, where the issue is a logical condition (e.g. unknown subject or code), the server SHOULD process the search, including processing the parameter - with the result of returning an empty search set, since the parameter cannot be satisfied. In such cases, the search process MAY include an OperationOutcome in the search set that contains additional hints and warnings about the search process. This is included in the search results as an entry with search mode = outcome. Clients can use this information to improve future searches.

Link to relevant FHIR specification: http://hl7.org/fhir/STU3/search.html#errors

==Interactions, operations, search parameters==

===Interactions===

The following logical interactions are needed for the BgLZ use case:
* [http://hl7.org/fhir/STU3/http.html#search Search]

===Operations===
The following [http://hl7.org/fhir/STU3/operations.html operation] is needed for this use case.
* [http://hl7.org/fhir/STU3/observation-operations.html#lastn Last N Observations Query]

The lastn query meets the common need for searching for the most recent or last n=number of observations for a subject. For example, retrieving the last 5 temperatures for a patient to view trends or fetching the most recent laboratory results or vital signs. The link will provide more detailed information and examples regarding this operation.

===Search parameters===
The following search parameter types and search result parameters need to be supported for this use case.

Search parameter types:
* [http://hl7.org/fhir/STU3/search.html#token token]
* [http://hl7.org/fhir/STU3/search.html#reference reference]

Search result parameters:
* [http://hl7.org/fhir/STU3/search.html#include _include]
** Including modifier 'recurse'

The following custom search parameters are defined for this use case:

* [https://simplifier.net/resolve?target=simplifier&canonical=http://nictiz.nl/fhir/SearchParameter/careplan-activity-goal http://nictiz.nl/fhir/SearchParameter/careplan-activity-goal]
* [https://simplifier.net/resolve?target=simplifier&canonical=http://nictiz.nl/fhir/SearchParameter/careplan-activity-outcomereference http://nictiz.nl/fhir/SearchParameter/careplan-activity-outcomereference]
* [https://simplifier.net/resolve?target=simplifier&canonical=http://nictiz.nl/fhir/SearchParameter/careplan-medicaldevice http://nictiz.nl/fhir/SearchParameter/careplan-medicaldevice]

==List of StructureDefinitions==
The profiles represent their entire respective HCIM, to make them applicable in a broader context than the exchange of BgLZ or a MedMij context. 

{{NoteBoxPackage|https://simplifier.net/NictizSTU3-Zib2017/~packages|1.2.x|MedMij:V2019.01_FHIR_IG}}

{| class="wikitable" "cellpadding="10" 
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|ZIB NL
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|HCIM EN
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|FHIR Resource
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|FHIR Profile
|-
| style="background-color: white;"| [https://zibs.nl/wiki/Patient-v3.1(2017NL) Patiënt]
| style="background-color: white;"| [https://zibs.nl/wiki/Patient-v3.1(2017EN) Patient]
| style="background-color: white;"| Patient
| style="background-color: white;"| [https://simplifier.net/resolve?target=simplifier&canonical=http://fhir.nl/fhir/StructureDefinition/nl-core-patient http://fhir.nl/fhir/StructureDefinition/nl-core-patient]
|-
| style="background-color: white;"| [https://zibs.nl/wiki/BehandelAanwijzing-v3.1(2017NL) BehandelAanwijzing]
| style="background-color: white;"| [https://zibs.nl/wiki/TreatmentDirective-v3.1(2017EN) TreatmentDirective]
| style="background-color: white;"| Consent
| style="background-color: white;"| [https://simplifier.net/resolve?target=simplifier&canonical=http://nictiz.nl/fhir/StructureDefinition/zib-TreatmentDirective http://nictiz.nl/fhir/StructureDefinition/zib-TreatmentDirective] 
|-
| style="background-color: white;"| [https://zibs.nl/wiki/Wilsverklaring-v3.1(2017NL) Wilsverklaring]
| style="background-color: white;"| [https://zibs.nl/wiki/AdvanceDirective-v3.1(2017EN) AdvanceDirective]
| style="background-color: white;"| Consent
| style="background-color: white;"| [https://simplifier.net/resolve?target=simplifier&canonical=http://nictiz.nl/fhir/StructureDefinition/zib-AdvanceDirective http://nictiz.nl/fhir/StructureDefinition/zib-AdvanceDirective]
|-
| style="background-color: white;"| [https://zibs.nl/wiki/Probleem-v4.1(2017NL) Probleem]
| style="background-color: white;"| [https://zibs.nl/wiki/Problem-v4.1(2017EN) Problem]
| style="background-color: white;"| Condition
| style="background-color: white;"| [https://simplifier.net/resolve?target=simplifier&canonical=http://nictiz.nl/fhir/StructureDefinition/zib-Problem http://nictiz.nl/fhir/StructureDefinition/zib-Problem] 
|-
| style="background-color: white;"| [https://zibs.nl/wiki/AllergieIntolerantie-v3.2(2017NL) AllergieIntolerantie]
| style="background-color: white;"| [https://zibs.nl/wiki/AllergyIntolerance-v3.2(2017EN) AllergyIntolerance]
| style="background-color: white;"| AllergyIntolerance
| style="background-color: white;"| [https://simplifier.net/resolve?target=simplifier&canonical=http://nictiz.nl/fhir/StructureDefinition/zib-AllergyIntolerance http://nictiz.nl/fhir/StructureDefinition/zib-AllergyIntolerance]
|-
| style="background-color: white;"| [https://zibs.nl/wiki/LaboratoriumUitslag-v4.1(2017NL) LaboratoriumUitslag]
| style="background-color: white;"| [https://zibs.nl/wiki/LaboratoryTestResult-v4.1(2017EN) LaboratoryTestResult]
| style="background-color: white;"| Observation
| style="background-color: white;"| [https://simplifier.net/resolve?target=simplifier&canonical=http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation]
|-
| style="background-color: white;"| [https://zibs.nl/wiki/Verrichting-v4.1(2017NL) Verrichting]
| style="background-color: white;"| [https://zibs.nl/wiki/Procedure-v4.1(2017EN) Procedure]
| style="background-color: white;"| Procedure
| style="background-color: white;"| [https://simplifier.net/resolve?target=simplifier&canonical=http://nictiz.nl/fhir/StructureDefinition/zib-Procedure http://nictiz.nl/fhir/StructureDefinition/zib-Procedure]
|-
| style="background-color: white;"| [https://zibs.nl/wiki/VerpleegkundigeInterventie-v3.2(2018NL) VerpleegkundigeInterventie *]
| style="background-color: white;"| [https://zibs.nl/wiki/NursingIntervention-v3.2(2018EN) NursingIntervention *]
| rowspan="4" style="background-color: white;"| CarePlan
| rowspan="4" style="background-color: white;"| [https://simplifier.net/resolve?target=simplifier&canonical=http://fhir.nl/fhir/StructureDefinition/nl-core-careplan http://fhir.nl/fhir/StructureDefinition/nl-core-careplan]
|-
| style="background-color: white;"| [https://zibs.nl/wiki/Behandeldoel-v3.1(2017NL) Behandeldoel]
| style="background-color: white;"| [https://zibs.nl/wiki/TreatmentObjective-v3.1(2017EN) TreatmentObjective]
|-
| style="background-color: white;"| [https://zibs.nl/wiki/MedischHulpmiddel-v3.1(2017NL) MedischHulpmiddel]
| style="background-color: white;"| [https://zibs.nl/wiki/MedicalDevice-v3.1(2017EN) MedicalDevice]
|-
| style="background-color: white;"| [https://zibs.nl/wiki/UitkomstVanZorg-v3.1(2017NL) UitkomstVanZorg]
| style="background-color: white;"| [https://zibs.nl/wiki/OutcomeOfCare-v3.1(2017EN) OutcomeOfCare]
|-
| rowspan="2" style="background-color: white;" | [https://zibs.nl/wiki/Zorgverlener-v3.2(2017NL) Zorgverlener]
| rowspan="2" style="background-color: white;" | [https://zibs.nl/wiki/HealthProfessional-v3.2(2017EN) HealthProfessional]
| style="background-color: white;"| Practitioner
| style="background-color: white;"| [https://simplifier.net/resolve?target=simplifier&canonical=http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner]
|-
| style="background-color: white;"| PractitionerRole
| style="background-color: white;"| [https://simplifier.net/resolve?target=simplifier&canonical=http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole]
|-
| style="background-color: white;"| [https://zibs.nl/wiki/Zorgaanbieder-v3.1.1(2017NL) Zorgaanbieder]
| style="background-color: white;"| [https://zibs.nl/wiki/HealthcareProvider-v3.1.1(2017EN) HealthcareProvider]
| style="background-color: white;"| Organization
| style="background-color: white;"| [https://simplifier.net/resolve?target=simplifier&canonical=http://fhir.nl/fhir/StructureDefinition/nl-core-organization http://fhir.nl/fhir/StructureDefinition/nl-core-organization]
|-
| style="background-color: white;"| -
| style="background-color: white;"| -
| style="background-color: white;"| CareTeam
| style="background-color: white;"| [https://simplifier.net/resolve?target=simplifier&canonical=http://fhir.nl/fhir/StructureDefinition/nl-core-careteam http://fhir.nl/fhir/StructureDefinition/nl-core-careteam]
|}

<blockquote>* The 2018 release of the HCIM NursingIntervention is used because the 2017 release is not suitable. The functional design page provides more information. In addition, the CarePlan resource is used to transfer the HCIM NursingIntervention. The BgLZ does not use the Procedure resource for HCIM NursingIntervention.</blockquote>

==Terminology, NamingSystems, Mappings==

===Terminology===
Relevant value sets can be found [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=ValueSet using the ValueSet category].

===NamingSystems===
Relevant NamingSystems can be found [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=NamingSystem using the NamingSystem category].

===Mappings===
Relevant HCIM to FHIR value set mappings can be found [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=ConceptMap using the ConceptMap category].
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.

<pre>
<StructureDefinition>
    <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>

=Annex: Document history=
==Release notes==
Release notes can be found on the [[MedMij:V2019.01_OntwerpLangdurigeZorg#Release_notes|functional design page]].

==History==
{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Release
!style="text-align:left;"|Date
!style="text-align:left;"|Description
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 05-09-2019
| style="background-color: white;"| 
* Version from v0.1.0 (public consultation) to v1.0.0 (initial final version).
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 20-05-2019
| style="background-color: white;"| 
* Added intitial version for public consultation.
|-
|}
[[categorie:MedMij FHIR Use Cases]]