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

Evelyn Lai op 18 feb 2026 om 12:25

2026-02-18T12:25:40Z

Wijzigingen bekijken

Evelyn Lai op 18 feb 2026 om 12:22

2026-02-18T12:22:59Z

Wijzigingen bekijken

Evelyn Lai op 16 feb 2026 om 17:31

2026-02-16T17:31:15Z

Evelyn Lai: {{VersieInfo|mp9|V3.0.0-rc.1}} vervangen met {{VersieInfo|mp9|release=V3.0.0-rc.1}}

2026-02-16T17:22:29Z

{{VersieInfo|mp9|V3.0.0-rc.1}} vervangen met {{VersieInfo|mp9|release=V3.0.0-rc.1}}

Evelyn Lai: https://www.hl7.nl/wiki/index.php?title=DatatypesR1:II vervangen met https://hl7.nl/component/zoo/item/publicatie-van-de-hl7v3-cda-implementatiehandleiding-basiscomponenten-versie-2-3.html?highlight=WyJkYXRhdHlwZSIsImlpIl0=

2026-02-11T17:35:37Z

https://www.hl7.nl/wiki/index.php?title=DatatypesR1:II vervangen met https://hl7.nl/component/zoo/item/publicatie-van-de-hl7v3-cda-implementatiehandleiding-basiscomponenten-versie-2-3.html?highlight=WyJkYXRhdHlwZSIsImlpIl0=

Evelyn Lai: mp:V3.0.0-beta_Ontwerp_medicatieproces_9_ENG vervangen met mp:V3.0.0-rc.1_Ontwerp_medicatieproces_9_ENG

2026-02-11T17:26:24Z

mp:V3.0.0-beta_Ontwerp_medicatieproces_9_ENG vervangen met mp:V3.0.0-rc.1_Ontwerp_medicatieproces_9_ENG

Evelyn Lai: mp:V3.0.0-rc.1_MedicationProcess9_FHIR# vervangen met # en https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-rc.1_MedicationProcess9_FHIR# vervangen met #

2026-02-11T17:07:15Z

mp:V3.0.0-rc.1_MedicationProcess9_FHIR# vervangen met # en https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-rc.1_MedicationProcess9_FHIR# vervangen met #

Evelyn Lai: https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0_Ontwerp_medicatieproces_9_ENG vervangen met https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-rc.1_Ontwerp_medicatieproces_9_ENG

2026-02-11T16:41:46Z

https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0_Ontwerp_medicatieproces_9_ENG vervangen met https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-rc.1_Ontwerp_medicatieproces_9_ENG

Evelyn Lai: https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-beta_Ontwerp_medicatieproces_9_ENG vervangen met https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0_Ontwerp_medicatieproces_9_ENG

2026-02-11T16:35:40Z

https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-beta_Ontwerp_medicatieproces_9_ENG vervangen met https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0_Ontwerp_medicatieproces_9_ENG

Evelyn Lai: mp:V3.0.0_MedicationProcess9_FHIR vervangen met mp:V3.0.0-rc.1_MedicationProcess9_FHIR

2026-02-11T15:25:21Z

mp:V3.0.0_MedicationProcess9_FHIR vervangen met mp:V3.0.0-rc.1_MedicationProcess9_FHIR

@@ Regel 8: / Regel 8: @@
 = Introduction =
-This is the implementation guide (IG) for the information standard Medication Process 9 (MP9) version  {{VersieInfo|mp9|release=V3.0.0-rc.1}} using the HL7® FHIR® standard. The MP9 standard is described in [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-rc.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.
+This is the implementation guide (IG) for the information standard Medication Process 9 (MP9) version {{VersieInfo|mp9|release=V3.0.0-rc.1}} using the HL7® FHIR® standard. The MP9 standard is described in [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-rc.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 17: / Regel 17: @@
 == Building blocks and profiles ==
-The exchange of data within the MP9 standard version  {{VersieInfo|mp9|release=V3.0.0-rc.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.
+The exchange of data within the MP9 standard version {{VersieInfo|mp9|release=V3.0.0-rc.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 1.577: / Regel 1.577: @@
 =Release notes=
-Release notes can be found [[mp:V {{VersieInfo|mp9|release=V3.0.0-rc.1}}_releasenotes|here]].
+Release notes can be found [[mp:V{{VersieInfo|mp9|release=V3.0.0-rc.1}}_releasenotes|here]].
 =Footnotes=
 <references/>

@@ Regel 3: / Regel 3: @@
 __NOINDEX__
 __NUMBEREDHEADINGS__
-{{DISPLAYTITLE:FHIR Implementation Guide Medication Process 9 version {{VersieInfo|mp9|V3.0.0-rc.1}} }}
+{{DISPLAYTITLE:FHIR Implementation Guide Medication Process 9 version {{VersieInfo|mp9|release=V3.0.0-rc.1}} }}
 __TOC__
 = Introduction =
-This is the implementation guide (IG) for the information standard Medication Process 9 (MP9) version {{VersieInfo|mp9|V3.0.0-rc.1}} using the HL7® FHIR® standard. The MP9 standard is described in [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-rc.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.
+This is the implementation guide (IG) for the information standard Medication Process 9 (MP9) version  {{VersieInfo|mp9|release=V3.0.0-rc.1}} using the HL7® FHIR® standard. The MP9 standard is described in [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-rc.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 17: / Regel 17: @@
 == Building blocks and profiles ==
-The exchange of data within the MP9 standard version {{VersieInfo|mp9|V3.0.0-rc.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.
+The exchange of data within the MP9 standard version  {{VersieInfo|mp9|release=V3.0.0-rc.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 27: / Regel 27: @@
 Note that the package versioning does not follow the versioning of the information standard, as MP9 version 2.0.0 was the first release of the MP9 information standard based on FHIR R4 (and largely based on zib publication 2020). This means that:
 * MP9 version 2.0.0 makes use of version 1.0.0 of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package;
-* MP9 version {{VersieInfo|mp9|V3.0.0-rc.1}} makes use of version {{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|V3.0.0-rc.1}} of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package.
+* MP9 version  {{VersieInfo|mp9|release=V3.0.0-rc.1}} makes use of version {{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|V3.0.0-rc.1}} of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package.
 === Medication building blocks ===
@@ Regel 1.577: / Regel 1.577: @@
 =Release notes=
-Release notes can be found [[mp:V{{VersieInfo|mp9|V3.0.0-rc.1}}_releasenotes|here]].
+Release notes can be found [[mp:V {{VersieInfo|mp9|release=V3.0.0-rc.1}}_releasenotes|here]].
 =Footnotes=
 <references/>

@@ Regel 249: / Regel 249: @@
 All profiles used within the MP9 information standard contain {{fhir|.identifier}} elements with a cardinality of 0..* because of open world modelling. However, all ART-DECOR transactions referenced within this IG assign a 1..1 R cardinality, meaning a stable identifier SHOULD be provided, or [[FHIR:V1.0_FHIR_IG_R4#Missing_information|the DataAbsentReason extension if a value is missing]]. Identifiers SHALL contain both a {{fhir|.system}} and a {{fhir|.value}}.
-Because in HL7v3 (CDA) an identifier can only be composed using OIDs, the {{fhir|.system}} SHALL be an OID to accommodate compatibility in transformations to and from FHIR. The [https://www.hl7.nl/wiki/index.php?title=DatatypesR1:II Netherlands HL7v3 datatype II] also defines additional restrictions on the maximum length of both <code>@root</code> and <code>@extension</code> (equivalent to respectively {{fhir|.system}} and {{fhir|.value}} in FHIR). For the same compatibility reasons, {{fhir|.system}} SHALL have a maximum of 128 characters and {{fhir|.value}} SHALL have a maximum of 64 characters.
+Because in HL7v3 (CDA) an identifier can only be composed using OIDs, the {{fhir|.system}} SHALL be an OID to accommodate compatibility in transformations to and from FHIR. The [https://hl7.nl/component/zoo/item/publicatie-van-de-hl7v3-cda-implementatiehandleiding-basiscomponenten-versie-2-3.html?highlight=WyJkYXRhdHlwZSIsImlpIl0=  Netherlands HL7v3 datatype II] also defines additional restrictions on the maximum length of both <code>@root</code> and <code>@extension</code> (equivalent to respectively {{fhir|.system}} and {{fhir|.value}} in FHIR). For the same compatibility reasons, {{fhir|.system}} SHALL have a maximum of 128 characters and {{fhir|.value}} SHALL have a maximum of 64 characters.
 Systems that encounter or resolve references, either logical or literal, in resources they receive, SHALL NOT rewrite these references to a copy of these resources (with {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/ext-CopyIndicator|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|V3.0.0-rc.1}}}} present) they may store. This means that [https://hl7.org/fhir/r4/references.html relative literal references] may need to be rewritten to absolute ones. This also goes for [[FHIR:V1.0_FHIR_IG_R4#Including_.22secondary.22_resources_when_sending_information|included secondary resources in transactions]].

@@ Regel 226: / Regel 226: @@
 == 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. As mentioned in [[#Resource_identification|‘Resource identification’]] the system of the identifer SHALL be an OID to accommodate compatibility in transformations to and from FHIR. 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-rc.1_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. As mentioned in [[#Resource_identification|‘Resource identification’]] the system of the identifer SHALL be an OID to accommodate compatibility in transformations to and from FHIR. 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 347: / Regel 347: @@
 = Transactions =
-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’.
+This section describes the FHIR implementation of all transactions listed in [[mp:V3.0.0-rc.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 ‘Query’ and ‘Making available’, this IG uses the terms ‘Retrieving’ and ‘Serving’.
 <section begin=medmij1 />
 == Medication data (Retrieve/Serve) ==

@@ Regel 190: / Regel 190: @@
 ====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-rc.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.
+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 [[#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. The different ways to reference building blocks in MP9 can be found in the last paragraph of [[#Mappings_between_profiles_and_data_set|section 2.2]].
@@ Regel 633: / Regel 633: @@
 ==== Serving resources with a stoptype ====
-Additional custom behavior is expected of servers when serving a MedicationAgreement, a VariableDosingRegimen or a AdministrationAgreement building block. It is required to include the latest stopped MedicationRequest or MedicationDispense resource for each pharmaceutical treatment (regardless of [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-rc.1_MedicationProcess9_FHIR#Retrieve_.28request_message.29 the date given in the period-of-use search parameter] and the value of the period of use in the extensions ext-TimeInterval.Period and ext-TimeInterval.Duration). This requirement is described in sections [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-rc.1_Ontwerp_medicatieproces_9_ENG#Process_step:_Making_a_medication_agreement 2.2.5.3 Discontinuing medication], [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-rc.1_Ontwerp_medicatieproces_9_ENG#Process_step:_Making_a_variable_dosing_regimen 2.2.6.3 Stopping a variable dosing regimen] and [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-rc.1_Ontwerp_medicatieproces_9_ENG#Process_step:_Creating_an_administration_agreement 2.3.6.3 Discontinuing an administration agreement] in the functional design.
+Additional custom behavior is expected of servers when serving a MedicationAgreement, a VariableDosingRegimen or a AdministrationAgreement building block. It is required to include the latest stopped MedicationRequest or MedicationDispense resource for each pharmaceutical treatment (regardless of [#Retrieve_.28request_message.29 the date given in the period-of-use search parameter] and the value of the period of use in the extensions ext-TimeInterval.Period and ext-TimeInterval.Duration). This requirement is described in sections [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-rc.1_Ontwerp_medicatieproces_9_ENG#Process_step:_Making_a_medication_agreement 2.2.5.3 Discontinuing medication], [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-rc.1_Ontwerp_medicatieproces_9_ENG#Process_step:_Making_a_variable_dosing_regimen 2.2.6.3 Stopping a variable dosing regimen] and [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-rc.1_Ontwerp_medicatieproces_9_ENG#Process_step:_Creating_an_administration_agreement 2.3.6.3 Discontinuing an administration agreement] in the functional design.
 For each pharmaceutical treatment, only the latest MedicationAgreement, VariableDosingRegimen or AdministrationAgreement building block wherein the ext-StopType extension is present should be included in the Bundle. The latest one is based on the value of the ext-RegistrationDateTime extension in each resource.

@@ Regel 633: / Regel 633: @@
 ==== Serving resources with a stoptype ====
-Additional custom behavior is expected of servers when serving a MedicationAgreement, a VariableDosingRegimen or a AdministrationAgreement building block. It is required to include the latest stopped MedicationRequest or MedicationDispense resource for each pharmaceutical treatment (regardless of [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-rc.1_MedicationProcess9_FHIR#Retrieve_.28request_message.29 the date given in the period-of-use search parameter] and the value of the period of use in the extensions ext-TimeInterval.Period and ext-TimeInterval.Duration). This requirement is described in sections [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0_Ontwerp_medicatieproces_9_ENG#Process_step:_Making_a_medication_agreement 2.2.5.3 Discontinuing medication], [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0_Ontwerp_medicatieproces_9_ENG#Process_step:_Making_a_variable_dosing_regimen 2.2.6.3 Stopping a variable dosing regimen] and [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0_Ontwerp_medicatieproces_9_ENG#Process_step:_Creating_an_administration_agreement 2.3.6.3 Discontinuing an administration agreement] in the functional design.
+Additional custom behavior is expected of servers when serving a MedicationAgreement, a VariableDosingRegimen or a AdministrationAgreement building block. It is required to include the latest stopped MedicationRequest or MedicationDispense resource for each pharmaceutical treatment (regardless of [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-rc.1_MedicationProcess9_FHIR#Retrieve_.28request_message.29 the date given in the period-of-use search parameter] and the value of the period of use in the extensions ext-TimeInterval.Period and ext-TimeInterval.Duration). This requirement is described in sections [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-rc.1_Ontwerp_medicatieproces_9_ENG#Process_step:_Making_a_medication_agreement 2.2.5.3 Discontinuing medication], [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-rc.1_Ontwerp_medicatieproces_9_ENG#Process_step:_Making_a_variable_dosing_regimen 2.2.6.3 Stopping a variable dosing regimen] and [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-rc.1_Ontwerp_medicatieproces_9_ENG#Process_step:_Creating_an_administration_agreement 2.3.6.3 Discontinuing an administration agreement] in the functional design.
 For each pharmaceutical treatment, only the latest MedicationAgreement, VariableDosingRegimen or AdministrationAgreement building block wherein the ext-StopType extension is present should be included in the Bundle. The latest one is based on the value of the ext-RegistrationDateTime extension in each resource.
@@ Regel 858: / Regel 858: @@
 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 functional specification].
+The clinical content of the medication overview is defined in the [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-rc.1_Ontwerp_medicatieproces_9_ENG#Medication_overview_and_inference_rules functional specification].
 === List of profiles ===
@@ Regel 964: / Regel 964: @@
 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 functional specification].
+The clinical content of the medication overview is defined in the [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-rc.1_Ontwerp_medicatieproces_9_ENG#Medication_overview_and_inference_rules functional specification].
 === Receive (response message) ===