mp:Vissue-MP-1078 MedicationProcess9 FHIR - Bewerkingsoverzicht

Luud Slagter: Updated hyperlinks

2023-10-31T18:03:37Z

Updated hyperlinks

Luud Slagter: /* Pharmaceutical treatment */

2023-10-31T17:55:29Z

‎Pharmaceutical treatment

Luud Slagter: /* Pharmaceutical treatment */

2023-10-31T17:54:48Z

‎Pharmaceutical treatment

Luud Slagter: Updated versions to VersieInfo reference

2023-10-31T17:53:54Z

Updated versions to VersieInfo reference

Wijzigingen bekijken

Luud Slagter: MP-594: Added additional requirement for PeriodOfUse search parameter

2023-10-25T17:44:33Z

MP-594: Added additional requirement for PeriodOfUse search parameter

Luud Slagter: /* Mappings between profiles and data set */

2023-10-24T14:47:29Z

‎Mappings between profiles and data set

Luud Slagter: /* Mappings between profiles and data set */

2023-10-24T14:44:56Z

‎Mappings between profiles and data set

Luud Slagter: Generalized mappings between profiles and data set

2023-10-24T14:29:01Z

Generalized mappings between profiles and data set

Luud Slagter op 23 okt 2023 om 11:47

2023-10-23T11:47:46Z

Lauri Rondolo: AD publicatie verwijzingen aangepast naar nieuwe timestamp https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005

2023-10-18T14:23:34Z

AD publicatie verwijzingen aangepast naar nieuwe timestamp https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005

Wijzigingen bekijken

@@ Regel 7: / Regel 7: @@
 = 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}} using the HL7® FHIR® standard. The MP9 standard is described in [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-beta_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 216: / Regel 216: @@
 Each transaction contains a Patient building block with cardinality 1..1 M. This patient is the subject of all other building blocks in the transaction, although no explicit relation exists in the data set. Therefore, a reference to a Patient resource conforming to the nl-core-Patient profile is expected in {{fhir|.subject}} of each FHIR instance of each building block.
-Relations between different building blocks exist in transactions by means of concepts with a name starting with ‘Relation…’ (Dutch: ‘Relatie…’) and an underlying concept 'Identification' of data type Identification, for example RelationAdministrationAgreement (mp-dataelement9x-1328) in building block MedicationAgreement. These relations are mapped to the FHIR data type ‘Reference’. Implementers SHOULD use literal references (using {{fhir|.reference}}) instead of logical references (using {{fhir|.identifier}}) where possible, see the [[FHIR:V1.0_FHIR_IG_R4#Use_of_the_reference_datatype|general FHIR IG on the Reference data type]].
+Relations between different building blocks exist in transactions by means of concepts with a name starting with ‘Relation…’ (Dutch: ‘Relatie…’) and an underlying concept 'Identification' of data type Identification, for example RelationAdministrationAgreement (mp-dataelement9x-1328) in building block MedicationAgreement. These relations are mapped to the FHIR data type ‘Reference’. Implementers SHOULD use literal references (using {{fhir|.reference}}) instead of logical references (using {{fhir|.identifier}}) where possible, see the [[FHIR:V1.0_FHIR_IG_R4#Use_of_the_reference_data_type|general FHIR IG on the Reference data type]].
 == Pharmaceutical treatment ==
@@ Regel 340: / Regel 340: @@
 = Transactions =
-This section describes the FHIR implementation of all transactions listed in [[mp:Vprepub-3.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 ‘Query’ 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_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 ‘Query’ and ‘Making available’, this IG uses the terms ‘Retrieving’ and ‘Serving’.
 <section begin=medmij1 />
 == Medication data (Retrieve/Serve) ==
@@ Regel 718: / Regel 718: @@
 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_Ontwerp_medicatieproces_9_ENG#Medication_overview_and_inference_rules functional specification].
 === List of profiles ===
@@ Regel 824: / Regel 824: @@
 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_Ontwerp_medicatieproces_9_ENG#Medication_overview_and_inference_rules functional specification].
 === Receive (response message) ===

@@ Regel 219: / Regel 219: @@
 == 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_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_Ontwerp_medicatieproces_9_ENG#.27Medicamenteuze_behandeling_.2F_Pharmaceutical_treatment.27_.28MBH.29|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 219: / Regel 219: @@
 == 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:Vprepub-3.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_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 444: / Regel 444: @@
 | PeriodOfUse
 | Search on the MedicationAgreement, VariableDosingRegimen, AdministrationAgreement and MedicationUse2 building blocks that are related to medication that was used, is used or will be used during the indicated period.
 | {{fhir|period-of-use}}<ref name="custom-searchparameter"/>
 | MedicationRequest, MedicationDispense, MedicationStatement<ref>For the MedicationRequest and MedicationDispense resource types, the {{fhir|period-of-use}} parameter searches on the ext-TimeInterval.Period extension which may include the ext-TimeInterval.Duration extension. For the MedicationStatement resource type, the parameter modifies the core search parameter on {{fhir|.effective}} to include the ext-TimeInterval.Duration extension that may be present.</ref>

@@ Regel 210: / Regel 210: @@
 Following the procedure outlined above thus results in the following:
 * All relevant zib mappings stay visible, and moreover all elements in the corresponding ART-DECOR data set that aren't compatible anymore with their zib counterparts are marked.
-* All incompatible changes made with respect to the previous version are marked.
+* All incompatible changes made in the latest version with respect to the previous version are marked.
 Because of [[FHIR:V1.0_FHIR_Profiling_Guidelines_R4#Open_vs._closed_world_modeling|open world modelling]], the cardinality of elements in the FHIR profiles can be less strict than the cardinalities in the ART-DECOR transactions. However, the latter cardinality is leading when it comes to exchanging building blocks in the context of a specific transaction. For example: in the mp-MedicationAgreement profile, {{fhir|.requester}} has a cardinality of 0..1, while in the ‘Serve Medication data’ ART-DECOR transaction, the Prescriber element has a cardinality of 1..1 R. Therefore, {{fhir|.requester}} is expected to be filled with either a Reference to an nl-core-HealthProfessional-PractitionerRole resource or a [http://hl7.org/fhir/R4/extension-data-absent-reason.html DataAbsentReason extension], see the [[FHIR:V1.0_FHIR_IG_R4#Missing_information|general FHIR IG on ‘Missing information’]].

@@ Regel 198: / Regel 198: @@
 Each transaction starts with links to the functional definition in an ART-DECOR publication and references one or several FHIR profiles. Where the functional definition contains all specific data elements for the transaction (prefixed with ‘mp-dataelement9x’), the FHIR profiles only contain a mapping to these data elements that do not have a dependency on a zib counterpart. For example: ‘mp-dataelement9x-83’ (MedicationAgreementDateTime) has a relation with the zib element with id ‘NL-CM-9.6.19757’, therefore no mapping with ‘mp-dataelement9x-83’ can be found in the profiles. On the other hand, ‘mp-dataelement9x-42’ (Identification) has no relation with a zib element, therefore a mapping can be found in the relevant FHIR profile.
-From version 3.0.0-beta.1 of the MP9 standard onwards, changes in the functional definition have lead to mappings being deprecated. The following situations can be identified:
+From version 2.0.0 of the MP9 standard onwards, changes in the functional definition have lead to mappings being deprecated. The following situations can be identified:
 * If an element in the functional definition was modified in a non-compatible way (for example, a concept has been removed from or added to the value set on that element, the data type of the element has changed, or the cardinality of the element (in all relevant transactions) has changed)
-** and the element had a zib mapping applied, the zib mapping gets a suffix {{term|[DEPRECATED]}}, and a mapping to the new version of MP9 is added following the rules stated before.
+** and the element had a zib mapping applied, the zib mapping gets a suffix {{term|[DEPRECATED]}}, and a mapping to the latest version of MP9 is added following the rules stated before.
-** and the element had a mapping applied to the previous version of MP9, that mapping gets a suffix {{term|[DEPRECATED]}}, and a mapping to the new version of MP9 is added following the rules stated before.
+** and the element had a mapping applied to the previous version of MP9, that mapping gets a suffix {{term|[DEPRECATED]}}, and a mapping to the latest version of MP9 is added following the rules stated before.
 * If an element in the functional definition is removed
 ** and the element had a zib mapping applied, the zib mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.

@@ Regel 1: / Regel 1: @@
-{{IssuePaginaWaarschuwing|MM-1078|mp:V3.0.0_MedicationProcess9_FHIR}}
+{{IssuePaginaWaarschuwing|MP-1078|mp:V3.0.0_MedicationProcess9_FHIR}}
 __NOINDEX__
 __NUMBEREDHEADINGS__