Luud Slagter: Updated links to FO and added banner

2023-11-02T07:21:09Z

Updated links to FO and added banner

Tim Schuller: Nieuwe pagina aangemaakt met 'NUMBEREDHEADINGS {{DISPLAYTITLE:FHIR Implementation Guide Medication Process 9 version {{VersieInfo|mp9|release=V3.0.0}} }} TOC = Introduction = This is t...'

2023-11-01T15:08:36Z

Nieuwe pagina aangemaakt met '__NUMBEREDHEADINGS__ {{DISPLAYTITLE:FHIR Implementation Guide Medication Process 9 version {{VersieInfo|mp9|release=V3.0.0}} }} __TOC__ = Introduction = This is t...'

Wijzigingen bekijken

@@ Regel 1: / Regel 1: @@
 __NUMBEREDHEADINGS__
-{{DISPLAYTITLE:FHIR Implementation Guide Medication Process 9 version {{VersieInfo|mp9|release=V3.0.0}} }}
+{{DISPLAYTITLE:FHIR Implementation Guide Medication Process 9 version {{VersieInfo|mp9|release=V3.0.0-beta.1}} }}
 __TOC__
 = Introduction =
-This is the implementation guide (IG) for the information standard Medication Process 9 (MP9) version {{VersieInfo|mp9|release=V3.0.0}} using the HL7® FHIR® standard. The MP9 standard is described in [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0_Ontwerp_medicatieproces_9_ENG this functional specification] and further specified here using [https://www.hl7.org/fhir/R4/ FHIR version R4]. This implementation guide assumes that the reader is familiar with both the functional specification and this version of FHIR.
+This is the implementation guide (IG) for the information standard Medication Process 9 (MP9) version {{VersieInfo|mp9|release=V3.0.0-beta.1}} using the HL7® FHIR® standard. The MP9 standard is described in [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-beta.1_Ontwerp_medicatieproces_9_ENG this functional specification] and further specified here using [https://www.hl7.org/fhir/R4/ FHIR version R4]. This implementation guide assumes that the reader is familiar with both the functional specification and this version of FHIR.
 Apart from this document, the guidelines as specified in the [[FHIR:V1.0_FHIR_IG_R4|general FHIR Implementation Guide]] apply. In particular, the reader should take note of the [[FHIR:V1.0_FHIR_IG_R4#Overarching_principles|Overarching principles]] and the use of [[FHIR:V1.0_FHIR_IG_R4#FHIR_Packages|FHIR packages]]. Where the general IG uses the term ‘use case’, this IG follows the functional specification in using the term ‘transaction’ for the various processes that are described. The functional specification uses the term ‘use case’ for more practical examples.
@@ Regel 14: / Regel 18: @@
 == Building blocks and profiles ==
-The exchange of data within the MP9 standard version {{VersieInfo|mp9|release=V3.0.0}} is largely based on the 2020 publication of the Dutch Health and Care Information Models (Dutch: ‘zorginformatiebouwstenen’ or ‘zibs’). The objects that are present in the functional data set of the MP9 standard (and which are actually exchanged) are referred to as ‘building blocks’, and can thus be seen as ‘extended zibs’ suitable for implementation.
+The exchange of data within the MP9 standard version {{VersieInfo|mp9|release=V3.0.0-beta.1}} is largely based on the 2020 publication of the Dutch Health and Care Information Models (Dutch: ‘zorginformatiebouwstenen’ or ‘zibs’). The objects that are present in the functional data set of the MP9 standard (and which are actually exchanged) are referred to as ‘building blocks’, and can thus be seen as ‘extended zibs’ suitable for implementation.
 However, due to new insights, the medication related building blocks in the functional data set have deviated from the corresponding zibs they were originally based on, making them incompatible in varying degrees from a technical point of view. Therefore it was not possible to implement the FHIR profiles for these main building blocks by building on and extending [[FHIR:V1.0_FHIR_IG_R4#Functional_definitions|the nl-core profiles]] based on zib-publication 2020. Hence the profiles for these building blocks have been created ‘independently’ from these profiles, meaning that the MP9 profiles have no dependency on the zib2020-package.
@@ Regel 183: / Regel 187: @@
 ====Bundle profiles====
-The profiles on Bundle serve as guidance both on what is needed to differentiate between transactions (for example setting {{fhir|.meta.tag}} or a specific value of {{fhir|.intent}}, see also [[mp:V3.0.0_MedicationProcess9_FHIR#Differentiating_between_transactions|Differentiating between transactions]]) and on which building blocks can be expected to be included in a Bundle within a transaction.
+The profiles on Bundle serve as guidance both on what is needed to differentiate between transactions (for example setting {{fhir|.meta.tag}} or a specific value of {{fhir|.intent}}, see also [[mp:V3.0.0-beta.1_MedicationProcess9_FHIR#Differentiating_between_transactions|Differentiating between transactions]]) and on which building blocks can be expected to be included in a Bundle within a transaction.
 All building blocks defined in the functional specification of a transaction have been added as slices on {{fhir|.entry}}. This is not a limited list, a sending system has the option to include more referenced resources if needed. Note that where the functional specification of a transaction specifies a minimum cardinality of 1 for a building block, the minimum cardinality in a Bundle profile has been set to 0. Because there are different ways in FHIR to reference to building blocks, senders are not required to include it in the Bundle.
-Where the functional specification of a transaction expects a HealthProfessional building block, both [[mp:V3.0.0_MedicationProcess9_FHIR#Supporting_building_blocks|the profiles on resource types PractitionerRole and Practitioner]] have been included in the Bundle profile. The same goes for the HealthcareProvider building block with its profiles on Location and Organization.
+Where the functional specification of a transaction expects a HealthProfessional building block, both [[mp:V3.0.0-beta.1_MedicationProcess9_FHIR#Supporting_building_blocks|the profiles on resource types PractitionerRole and Practitioner]] have been included in the Bundle profile. The same goes for the HealthcareProvider building block with its profiles on Location and Organization.
 == Mappings between profiles and data set ==
@@ Regel 207: / Regel 211: @@
 == Pharmaceutical treatment ==
-The MP9 transaction data sets reference a container ‘Pharmaceutical treatment’ (Dutch: ‘Medicamenteuze behandeling’), which contains all medication building blocks relevant to the transaction. For the specification of the Pharmaceutical treatment, see [[mp:V3.0.0_Ontwerp_medicatieproces_9_ENG#.27Medicamenteuze_behandeling.27|the functional specification]]. In FHIR, the Pharmaceutical treatment does not have an explicit resource representation. Instead, each medication building block contains the PharmaceuticalTreatmentIdentifier extension which contains the ‘Pharmaceutical Treatment Identifier’. This Identifier shall be the same across different related medication resources that constitute one Pharmaceutical treatment. The custom search parameter {{fhir|pharmaceutical-treatment-identifier}}, see [[#Search_parameters|‘Search parameters’]], is used within the ‘Medication data’ transaction to query a server for all building blocks within a specific Pharmaceutical treatment.
+The MP9 transaction data sets reference a container ‘Pharmaceutical treatment’ (Dutch: ‘Medicamenteuze behandeling’), which contains all medication building blocks relevant to the transaction. For the specification of the Pharmaceutical treatment, see [[mp:V3.0.0-beta.1_Ontwerp_medicatieproces_9_ENG#.27Medicamenteuze_behandeling.27|the functional specification]]. In FHIR, the Pharmaceutical treatment does not have an explicit resource representation. Instead, each medication building block contains the PharmaceuticalTreatmentIdentifier extension which contains the ‘Pharmaceutical Treatment Identifier’. This Identifier shall be the same across different related medication resources that constitute one Pharmaceutical treatment. The custom search parameter {{fhir|pharmaceutical-treatment-identifier}}, see [[#Search_parameters|‘Search parameters’]], is used within the ‘Medication data’ transaction to query a server for all building blocks within a specific Pharmaceutical treatment.
 == Patient identification ==
@@ Regel 328: / Regel 332: @@
 = Transactions =
-This section describes the FHIR implementation of all transactions listed in [[mp:V3.0.0_Ontwerp_medicatieproces_9_ENG#Information_systems_and_transactions|section 7 of the functional specification]]. Transactions are paired per transaction group. Each subsection below hyperlinks the names of the transaction groups and transactions to the functional definition in an ART-DECOR publication. The ART-DECOR publication details which data elements are expected to be supported ([[Handleiding_Kardinaliteiten_en_conformance|cardinality and conformance]]) for each transaction. Where the functional specification uses the terms ‘Consulting’ and ‘Making available’, this IG uses the terms ‘Retrieving’ and ‘Serving’.
+This section describes the FHIR implementation of all transactions listed in [[mp:V3.0.0-beta.1_Ontwerp_medicatieproces_9_ENG#Information_systems_and_transactions|section 7 of the functional specification]]. Transactions are paired per transaction group. Each subsection below hyperlinks the names of the transaction groups and transactions to the functional definition in an ART-DECOR publication. The ART-DECOR publication details which data elements are expected to be supported ([[Handleiding_Kardinaliteiten_en_conformance|cardinality and conformance]]) for each transaction. Where the functional specification uses the terms ‘Consulting’ and ‘Making available’, this IG uses the terms ‘Retrieving’ and ‘Serving’.
 <section begin=medmij />
 == Medication data (Retrieve/Serve) ==
@@ Regel 701: / Regel 705: @@
 The server returns a HTTP Status code appropriate to the processing of the operation. The successful outcome of the {{Simplifier|http://nictiz.nl/fhir/OperationDefinition/Medication-Overview|nictiz.fhir.nl.r4.medicationprocess9|title={{fhir|$medication-overview}} operation}} is the body of the medication overview response message. Successful processing of this operation should result in a Bundle resource with {{fhir|Bundle.type}} = {{term|searchset}} that conforms to the mp-MedicationOverview-Bundle profile, which contains at least one List resource (that represents the medication overview and conforms to the mp-MedicationOverview profile) and optionally one Patient resource, along with all the resources that represent the current medication overview. These latter resources SHALL be referenced from the List resource. All resources included in the Bundle SHALL conform to their respective profiles listed in [[#Building_blocks_and_profiles|section 2.1]]. The {{fhir|Bundle.total}} value contains the number of matching building blocks (i.e. MedicationAgreement, AdministrationAgreement and MedicationUse2). Other included resources, such as Medication resources, are not included in the total.
-The clinical content of the medication overview is defined in the [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0_Ontwerp_medicatieproces_9_ENG#Medication_overview_and_inference_rules Medication Process specification].
+The clinical content of the medication overview is defined in the [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-beta.1_Ontwerp_medicatieproces_9_ENG#Medication_overview_and_inference_rules Medication Process specification].
 === List of profiles ===
@@ Regel 807: / Regel 811: @@
 The Bundle SHALL conform to the mp-MedicationOverview-Bundle profile, which contains at least one List profile (that represents the medication overview and conforms to the mp-MedicationOverview profile) and optionally one Patient resource, along with all the resources that represent the current medication overview. These latter resources SHALL be referenced from the List resource. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.
-The clinical content of the medication overview is defined in the [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0_Ontwerp_medicatieproces_9_ENG#Medication_overview_and_inference_rules Medication Process specification].
+The clinical content of the medication overview is defined in the [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-beta.1_Ontwerp_medicatieproces_9_ENG#Medication_overview_and_inference_rules Medication Process specification].
 === Receive (response message) ===
@@ Regel 1.420: / Regel 1.424: @@
 =Release notes=
-Release notes can be found [[mp:V2.0.0_releasenotes|here]].
+Release notes can be found [[mp:V3.0.0-beta.1_releasenotes|here]].
 =Footnotes=
 <references/>

mp:V3.0.0-beta.1 MedicationProcess9 FHIR - Bewerkingsoverzicht

Luud Slagter: Updated links to FO and added banner

Tim Schuller: Nieuwe pagina aangemaakt met '__NUMBEREDHEADINGS__ {{DISPLAYTITLE:FHIR Implementation Guide Medication Process 9 version {{VersieInfo|mp9|release=V3.0.0}} }} __TOC__ = Introduction = This is t...'

Tim Schuller: Nieuwe pagina aangemaakt met 'NUMBEREDHEADINGS {{DISPLAYTITLE:FHIR Implementation Guide Medication Process 9 version {{VersieInfo|mp9|release=V3.0.0}} }} TOC = Introduction = This is t...'