bgz:V2.0 Beta BgZ 2017 Technical IG - Bewerkingsoverzicht

imported>Iwo Serlie: /* FHIR Query Specification */

2024-11-06T20:48:51Z

‎FHIR Query Specification

imported>Iwo Serlie: /* FHIR Query Specification */

2024-11-06T20:20:36Z

‎FHIR Query Specification

imported>Iwo Serlie: /* FHIR Query Specification */

2024-11-06T20:12:31Z

‎FHIR Query Specification

imported>Iwo Serlie: /* FHIR Query Specification */

2024-11-06T20:08:26Z

‎FHIR Query Specification

imported>Mik de Jong: /* FHIR Profiles */ - Added versioning package from bgz for task queries

2024-11-06T13:41:23Z

‎FHIR Profiles: - Added versioning package from bgz for task queries

imported>Mik de Jong: Corrected spelling meta data to metadata, also added the new BgZ package link

2024-11-06T13:34:57Z

Corrected spelling meta data to metadata, also added the new BgZ package link

imported>Gabriel Hopmans: /* Background */

2024-11-05T15:04:01Z

‎Background

imported>Gabriel Hopmans: note / to do helemaal in begin verwijderd

2024-11-05T15:03:11Z

note / to do helemaal in begin verwijderd

imported>Gabriel Hopmans: note in begin weggehaald bij FHIR profiles

2024-11-05T15:01:35Z

note in begin weggehaald bij FHIR profiles

imported>Gabriel Hopmans: /* Release Notes */

2024-11-05T14:59:34Z

‎Release Notes

@@ Regel 253: / Regel 253: @@
 All AdvanceDirectives available in the source system are exchanged as FHIR consent instances, which conform to the zib-AdvanceDirective profile.
 * The consent.category is fixed to ‘levenstestament en wilsverklaring in dossier’ (code = '11341000146107' in codeSystem 'SNOMED CT').
 |-
 ! scope="row" colspan="2" style="text-align: left;" | 4 Contact persons

@@ Regel 305: / Regel 305: @@
 All drug use available in the source system is exchanged as a FHIR Observation instances that conform to the zib-DrugUse profile.
 * The Observation.category is fixed to ‘Finding relating to drug misuse behavior’ (code = '228366006' in codeSystem 'SNOMED CT').
-* The target system may be configured to optimize the use of this information. For example, filtering the last known data for a specific DrugOrMedicationType.
+* The target system may be configured to optimize the use of this information. For example, grouping data according to a specific DrugOrMedicationType.
 |-
 !  colspan="2" style="text-align: left;" | 7.3 Alcohol Use
@@ Regel 312: / Regel 312: @@
 code=http://snomed.info/sct|228273003</pre>
+|
-All known alcohol use, available in the source system, is exchanged as FHIR Observations, which conform to the zib-AlcoholUse profile.
+All known alcohol use, available in the source system, is exchanged as FHIR Observations that conform to the zib-AlcoholUse profile.
 * The Observation.category is fixed to ‘Finding relating to alcohol drinking behavior’ (code = '228273003' in codeSystem 'SNOMED CT').
 |-
@@ Regel 320: / Regel 320: @@
 code=http://snomed.info/sct|365980008</pre>
+|
-All known Tobacco Use, available in the source system, is exchanged as a FHIR Observation instances, which conform to the zib-TobaccoUse profile.
+All known Tobacco Use, available in the source system, is exchanged as FHIR Observation instances that conform to the zib-TobaccoUse profile.
 * The Observation.category is fixed to ‘Finding of tobacco use and exposure’ (code = ' 365980008' in codeSystem 'SNOMED CT').
 |-
@@ Regel 328: / Regel 328: @@
+|
 All Nutrition Advice available in the source system is exchanged as a FHIR NutritionOrder instances that conform to the zib-NutritionAdvice profile.
-* The target system may be configured to optimize the use of this information. For example, filtering the last known data for a specific NutritionOrder.oralDiet.type.
+* The target system may be configured to optimize the use of this information. For example, grouping data according to a specific NutritionOrder.oralDiet.type.
 |-
 ! scope="row" colspan="2" style="text-align: left;" | 8 Alerts
@@ Regel 336: / Regel 336: @@
 | <pre>GET [base]/Flag</pre>
+|
-All alerts available in the source system is exchanged as a FHIR Flag instances that conform to the zib-Alert profile.
+All alerts available in the source system are exchanged as a FHIR Flag instances that conform to the zib-Alert profile.
 |-
 ! scope="row" colspan="2" style="text-align: left;" | 9 Allergies
@@ Regel 344: / Regel 344: @@
 | <pre>GET [base]/AllergyIntolerance</pre>
+|
-All allergies and intolerances available in the source system is exchanged as a FHIR AllergyIntolerance instances that conform to the zib-AllergyIntolerance profile.
+All allergies and intolerances available in the source system are exchanged as a FHIR AllergyIntolerance instances that conform to the zib-AllergyIntolerance profile.
-* According to the BgZ-msz transactions, the AllergyIntolerance.Reaction.Symptom must be exchanged if available. In exceptional cases where for legacy data there is no Symptom recorded, then the Reaction.manifestation field MUST be populated with the ‘unknown’ data-absent-reason.
+* According to the BgZ-MSZ transactions, the AllergyIntolerance.Reaction.Symptom must be exchanged if available. In cases where for legacy data there is no Symptom recorded, then the Reaction.manifestation field MUST be populated with the ‘unknown’ data-absent-reason.
 <pre>
 "manifestation":{
@@ Regel 363: / Regel 363: @@
 _include=MedicationRequest:medicationReference</pre>
+|
 All medication agreements available in the source system are exchanged FHIR MedicationRequest instances that conform to the zib-MedicationAgreement profile.
 * The MedicationRequest.category is fixed to ‘Prescription’ (code = '16076005' in codeSystem 'SNOMED CT')
 * The PharmaceuticalProduct agreed upon to be used is returned in full as FHIR Medication instance according to the zib-Product profile.
@@ Regel 373: / Regel 373: @@
 _include=MedicationDispense:medicationReference</pre>
+|
 All administration agreements available in the source system are exchanged FHIR MedicationDispense instances that conform to the zib-AdministrationAgreement profile.
 * The MedicationDispense.category is fixed to ‘Provider medication administration instructions’ (code = '422037009' in codeSystem 'SNOMED CT')
 * The PharmaceuticalProduct in the agreement is returned in full as FHIR Medication instance according to the zib-Product profile.
@@ Regel 384: / Regel 384: @@
 _include=MedicationStatement:medicationReference</pre>
+|
 All medication use available in the source system are exchanged FHIR MedicationStatement instances that conform to the zib-MedicationUse profile.
 * The MedicationStatement.category is fixed to ‘Medicatiegebruik’ (code = '6' in codeSystem ' 2.16.840.1.113883.2.4.3.11.60.20.77.5.3')
 * The PharmaceuticalProduct that is used is returned in full as FHIR Medication instance according to the zib-Product profile.
@@ Regel 406: / Regel 406: @@
+|
 All administered vaccinations available in the source system are exchanged as FHIR Immunization instances conforming to the zib-Vaccination profile.
-* Only vaccinations that have been administered are exchanged. Effectively, the Immunization.status is always fixed at ‘completed’.
+* Only vaccinations that have been administered are exchanged. Effectively, the Immunization.status is always fixed to ‘completed’.
 |-
 ! scope="row" colspan="2" style="text-align: left;" | 13 vital signs and measurements
@@ Regel 415: / Regel 415: @@
 code=http://loinc.org|85354-9</pre>
+|
-The last known Blood pressure available in the source system is exchanged as a FHIR Observation instance that conforms to the zib-BloodPressure  profile.
+The last known Blood pressure available in the source system is exchanged as a FHIR Observation instance that conforms to the zib-BloodPressure profile.
 * The Observation.category is fixed to ‘Blood pressure panel with all children optional’ (code = '85354-9' in codeSystem 'LOINC').
 * The Observation.effectiveDateTime is used to determine the last known Observation.
@@ Regel 448: / Regel 448: @@
 &_include=Observation:related-target</pre>
+|
-All last known Laboratory results, where for each PanelOrBattery the last known results, are exchanged as FHIR observations conforming the zib-LaboratoryTestResult-Observation profile.
+All last known Laboratory results, with the most recent test result for each PanelOrBattery, are exchanged as FHIR observations conforming to the zib-LaboratoryTestResult-Observation profile.
-* The optional result Type of the Laboratory Result is not used for filtering.
+* Per PanelOrBattery, all known laboratory tests are exchanged, regardless of their TestDateTime. They are exchanged as related observations with the PanelOrBattery-observation.
-* All known Laboratory test results are shared per PanelOrBattery.
+* The optional ResultType is not used when selecting Laboratory results for exchange.
 |-
 ! scope="row" colspan="2" style="text-align: left;" | 15 Procedures
@@ Regel 463: / Regel 464: @@
 * Surgical procedure are exchanged via an instance with the Procedure.category fixed to ‘Surgical procedure’ (code = ‘387713003’ in CodeSystem ‘SNOMED CT’).
 * Image guided procedures are exchanged via an instance where the Procedure category is fixed to ‘Imaging guidance’ (code = ‘258174001’ in CodeSystem ‘SNOMED CT’).
-* When instances are used in a FHIR store or test purposes and none of the above types apply, the Procedure.category is fixed to ‘procedure’ (code = ‘71388002’ in CodeSystem ‘SNOMED CT’).
+Procedure instances with any other category that the two specified above are not exchanged. The default category for the BgZ MSZ is ‘procedure’ (code = ‘71388002’ in CodeSystem ‘SNOMED CT’).
 |-
 ! scope="row" colspan="2" style="text-align: left;" | 16 Encounters
@@ Regel 483: / Regel 483: @@
 </pre>
+|
-All planned procedures available in the source system are exchanged FHIR ProcedureRequest instances according to the zib-ProcedureRequest profile.
+All planned procedures available in the source system are exchanged as FHIR ProcedureRequest instances according to the zib-ProcedureRequest profile.
 |-
 ! scope="row" colspan="2" style="text-align: left;" | 18 Care Setting
@@ Regel 506: / Regel 505: @@
 </pre>
+|
-Providers, are exchanged as part of the BgZ information elements. There is no specific query to retrieve Health Providers.
+Providers, are exchanged as part of the BgZ information elements according to the nl-core-organization profile. There is no specific query to retrieve Health Providers.
 |-
 ! colspan="2" style="text-align: left;" | 19  Meta data
@@ Regel 515: / Regel 513: @@
 | <pre>GET [base]/Provenance</pre>
+|
-All provenance data available in the source system is exchanged as FHIR provenance instances according to the bgz-metadata profile.
+All provenance data available in the source system for a specific BgZ summary is exchanged as FHIR provenance instances according to the BgZ-metadata profile.
 |-
 |}

@@ Regel 232: / Regel 232: @@
 _include=Coverage:payor
 </pre>
 | The payer data available in the source system is exchanged as a FHIR coverage instance that conforms to the zib-Payer profile.
 * The specified referenced payor resource instances, that may be of type nl-core-organization, nl-core-patient, or nl-core-relatedperson, are returned in full.
 |-
@@ Regel 244: / Regel 245: @@
 All treatmentDirectives available in the source system are exchanged as FHIR consent instances, which conform to the zib-TreatmentDirective profile.
 * The consent.category is fixed to ‘treatment instructions’ (code = '11291000146105' in codeSystem 'SNOMED CT').
 |-
 !  colspan="2" style="text-align: left;" | 3.2 Advance directive
@@ Regel 253: / Regel 253: @@
 All AdvanceDirectives available in the source system are exchanged as FHIR consent instances, which conform to the zib-AdvanceDirective profile.
 * The consent.category is fixed to ‘levenstestament en wilsverklaring in dossier’ (code = '11341000146107' in codeSystem 'SNOMED CT').
 |-
 ! scope="row" colspan="2" style="text-align: left;" | 4 Contact persons
@@ Regel 260: / Regel 259: @@
 |-
 | <pre>Patient.contact</pre>
 | Primary partner/contact data are exchanged via the patient resource (see 1.1).
 |-
 ! scope="row" colspan="2" style="text-align: left;" | 5 Functional/mental status
@@ Regel 273: / Regel 273: @@
 * Functional status data are exchanged with the observation.category fixed to ‘Functional finding’ (code = '118228005' in codeSystem 'SNOMED CT').
 * Mental status data are exchanged with the observation.category fixed to ‘Mental state, behavior and/or psychosocial function finding’ (code = '384821006 ' in codeSystem 'SNOMED CT').
-* The target system may be configured to optimize the use of this information, so that it facilitates in filtering the last known status regarding mental, hearing, vision, mobility and language skills.
+* please note that as defined in the BgZ dataset, the category may be both a functional and a mental status.
 |-
 ! scope="row" colspan="2" style="text-align: left;" | 6 Complaints and diagnoses
@@ Regel 281: / Regel 282: @@
 | <pre>GET [base]/Condition</pre>
+|
 All problems available in the source system are returned as zib-Problem instances.
-* The condition.clinicalStatus must be populated according to the zib-Problem profile. In exceptional cases where for legacy data there is no Problem.ProblemStatus recorded in the source system then the Condition.clinicalStatus field MUST be populated with the ‘unknown’ data-absent-reason.
+* The condition.ProblemStatus must be populated when exchanging data. In cases where for legacy data there is no Problem.ProblemStatus recorded in the source system then the Condition.clinicalStatus field must be populated with an assumed state such as “active” if there is no problemEndDate defined. It is a known problem that the data-absent-reason cannot be used. This aspect is under investigation.
-<pre>
+* Note that no Condition.category (e.g. diagnosis or symptom) may be assumed while exchanging data if the condition.category is not known.
-"clinicalStatus":{
+* Note that the condition.code can exchange multiple encodings for the same problem. In the transaction it is defined that a problem may contain an additional more specific problemName that is exchanged using a second condition.code.coding.
 |-
 ! scope="row" colspan="2" style="text-align: left;" | 7 Social history
@@ Regel 300: / Regel 294: @@
 code=http://snomed.info/sct|365508006</pre>
+|
-The last known living situation available in the source system is exchanged as a FHIR Observation instance that conforms to the zib-LivingSituation profile.
+All living situations available in the source system are exchanged as FHIR Observation instances that conform to the zib-LivingSituation profile.
 * The Observation.category is fixed to ‘Residence and accommodation circumstances - finding’ (code = ' 365508006' in codeSystem 'SNOMED CT').
 |-
 !  colspan="2" style="text-align: left;" | 7.2 Drug Use

@@ Regel 212: / Regel 212: @@
 The patient information available in the source system is exchanged as a FHIR patient instance that conforms to the nl-core-patient profile.
 * The last known marital status available in the source system is exchanged using the patient.maritalStatus field.
-* The general practitioner (GP) available in the source system is exchanged (a) as a FHIR Practitioner instance conforming to the nl-core-practitioner profile, where the Practitioner.identifier indicates a GP, or (b) as a FHIR Organization instance conforming to the nl-core-organization profile. The specified referenced resources are returned in full.
+* If available in the source system, the general practitioner (GP) is exchanged (a) as a FHIR Practitioner instance conforming to the nl-core-practitioner profile, where the Practitioner.identifier indicates a GP, or (b) as a FHIR Organization instance conforming to the nl-core-organization profile. The specified referenced resources are returned in full.
 * Information regarding the primary partner/contact available in the source system is exchanged using elements of the patient instance. It is not exchanged using the RelatedPerson resource.
 |-

@@ Regel 163: / Regel 163: @@
 |-
 | (Notification) Task
-| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/bgz-msz-notification-task-location-to-be-added}}
+| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/BgZ-NotificationTask|nictiz.fhir.nl.stu3.bgz|pkgVersion={{VersieInfo|nictiz.fhir.nl.stu3.bgz|release=V2.0|namespace=BgZ}}}}
 |}
@@ Regel 176: / Regel 176: @@
 |-
 | (Workflow) Task
-| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/bgz-msz-workflow-task-location-to-be-added}}
+| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/BgZ-WorkflowTask|nictiz.fhir.nl.stu3.bgz|pkgVersion={{VersieInfo|nictiz.fhir.nl.stu3.bgz|release=V2.0|namespace=BgZ}}}}
 |}

@@ Regel 868: / Regel 868: @@
 |-
 | 16
-| Meta data
+| Metadata
 | Provenance
 | Provenance
-| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bgz-metadata|nictiz.fhir.nl.stu3.zib2017|pkgVersion={{VersieInfo|nictiz.fhir.nl.stu3.zib2017|release=V2.0|namespace=BgZ}}}}
+| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bgz-metadata|nictiz.fhir.nl.stu3.bgz|pkgVersion={{VersieInfo|nictiz.fhir.nl.stu3.bgz|release=V2.0|namespace=BgZ}}}}
 |}
 <small>''Table 5.2 Referenced BgZ FHIR Resources''</small>

@@ Regel 18: / Regel 18: @@
 This data collection can be exchanged between care institutions. The information standard focuses on the exchange between healthcare providers of specialist medical care.
-This BgZ MSZ implementation guide defines the BgZ information exchanges, in terms of use cases, based on the Zib2017 and [https://www.hl7.org/fhir/stu3/ FHIR(STU3) HL7 FHIR, STU3]. HL7 CDA is no longer supported for BgZ MSZ exchange. This implementation guide assumes that the reader is familiar with this FHIR version.
+This BgZ MSZ implementation guide defines the BgZ information exchanges, in terms of use cases, based on the Zib2017 and [https://www.hl7.org/fhir/stu3/ FHIR(STU3) HL7 FHIR, STU3].
 Apart from this document, the guidelines as specified in [[FHIR:V1.0 FHIR IG STU3|general FHIR Implementation Guide]] apply. The guide defines methods on how to proceed with implementing FHIR STU3 and what rules apply (e.g. how to handle empty reponses etc.). In particular, the reader should take note of the [[FHIR:V1.0_FHIR_IG_STU3#Use_case_overarching_principles|Use case overarching principles]] and the use of [[FHIR:V1.0_FHIR_IG_STU3#FHIR_Packages|FHIR packages]].

@@ Regel 11: / Regel 11: @@
 {{DISPLAYTITLE:BgZ msz FHIR Implementation Guide v2.0 - Beta, under construction}}
 __TOC__
 =Introduction=

← Oudere versie		Versie van 5 nov 2024 om 15:01
Regel 154:		Regel 154:

	=FHIR Profiles=		=FHIR Profiles=
−	~~Note: These FHIR Profiles are under review and will be finalized by the beta version of the TO.~~

	==FHIR Notification Task==		==FHIR Notification Task==

@@ Regel 910: / Regel 910: @@
 ! style="font-weight: bold;text-align:left;" | BITS ticket
 ! style="font-weight: bold;text-align:left;" | Short description
 |-
 | [https://bits.nictiz.nl/browse/MSZ-139 MSZ-139]