https://informatiestandaarden.nictiz.nl/api.php?action=feedcontributions&feedformat=atom&user=Luud+Slagter 2026-07-18T23:28:28Z Gebruikersbijdragen MediaWiki 1.31.16 https://informatiestandaarden.nictiz.nl/index.php?title=uz:V1.0.0-alpha.1_FHIR_OBC&diff=223714 2024-08-05T08:33:03Z

<p>Luud Slagter: /* Scores and calculation rules */</p> <hr /> <div>{{Vdraft/InformationBox|This FHIR IG is currently under development and can not be considered stable and ready for use. For questions and change requests regarding this IG, please create a ticket in [{{VersieInfo|BITS|release=V1.0.0|namespace=uz}} BITS].}}<br /> <br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide OBC version {{VersieInfo|OBC|release=V1.0.0|namespace=uz}}}}<br /> <br /> = Introduction =<br /> <br /> This implementation guide (IG) functions as the initial draft for the pilot phase of a new information standard, Outcome-Based Care (OBC, Dutch: Uitkomstgerichte zorg), version {{VersieInfo|OBC|release=V1.0.0}}. This IG is developed using [https://www.hl7.org/fhir/R4/ HL7 FHIR R4]. It assumes that the reader is familiar with both this version of FHIR and the functional specification [TO-ADD link]. This information standard is inspired by the international [http://hl7.org/fhir/us/sdc/index.html Structured Data Capture (SDC)] implementation guide and tries to follow it where possible.<br /> <br /> 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 Overarching principles and the use of FHIR packages. <br /> <br /> This IG first describes the boundaries and relationships in place, after which the implementation of PROMs in FHIR is described.<br /> <br /> = Boundaries and relationships =<br /> <br /> == Boundaries ==<br /> As mentioned in the introduction, this IG serves as a precursor for the pilot phase of the new information standard OBC. This version of the IG focuses solely on the manifestation of PROM questionnaires and their corresponding answers in FHIR. It does not include clinical data or use cases for data exchange, as the primary goal of the pilot is to evaluate the feasibility of implementing FHIR in this context. It is the intention to expand the scope in future versions of the IG to include clinical data and data exchange use cases, ultimately aiming to develop OBC into a comprehensive information standard.<br /> <br /> == FHIR resources and building blocks ==<br /> The PROM questionnaires and response data building blocks within OBC version {{VersieInfo|OBC|release=V1.0.0}} are not based on any publication of the Dutch Health and Care Information Models (Dutch: ‘zorginformatiebouwstenen’ or ‘zibs’), as there are no zibs that represent these building blocks. Therefore, there is no dependency on corresponding nl-core profiles, and mappings to zib concepts are not defined. Currently, there are no plans to create more general nl-core profiles, as no corresponding zibs exist. <br /> <br /> === Questionnaire ===<br /> <br /> Each PROM questionnaire is represented through a dedicated FHIR Questionnaire instance. A FHIR Questionnaire is a definitional artifact, which means it defines the questions to be asked, how these should be structured and rendered, and what answers are allowed. More information on structure and rendering of the FHIR Questionnaire instances can be found in [[#Rendering|section 2.4]]. The answer options to each question are represented through terminology resources using ValueSets and CodeSystems.<br /> <br /> The primary purpose of representing PROMs as Questionnaire instances is to establish a canonical identifier for each PROM in the form of a URI. This URI serves as a linkage point connecting every QuestionnaireResponse to their corresponding Questionnaire.<br /> <br /> The Questionnaire resource isn't strictly necessary to create a QuestionnaireResponse. However, using FHIR Questionnaire instances for PROMs provides significant benefits through standardized and structured formatting. Each question is included in the Questionnaire as a separate {{fhir|.item}} and has a unique identifier in the corresponding {{fhir|.item.linkId}} element. Additionally, the terminology used in PROMs is represented in FHIR ValueSet and CodeSystem resources and is correctly linked to the questions in the Questionnaire, ensuring all definitions are easily accessible for implementers.<br /> <br /> === QuestionnaireResponse ===<br /> <br /> The collection of outcomes and scores of a PROM is represented in a FHIR QuestionnaireResponse profile. For every completed PROM, an instance conforming to the [https://simplifier.net/nictiz-r4-outcomebasedcare/obcquestionnaireresponse obc-QuestionnaireResponse] profile is created. This profile features a structured set of answers with linked ids to the answered questions. The QuestionnaireResponse also includes the completion date and the language of the completed form.<br /> <br /> The QuestionnaireResponse contains enough information about the questions asked that it can be interpreted somewhat independently from the Questionnaire it is based on. In other words, no access to the Questionnaire is necessary in order to extract basic information from a QuestionnaireResponse.<br /> <br /> === Main building blocks ===<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ResponseData<br /> | Antwoordgegevens<br /> | QuestionnaireResponse<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse|nictiz.fhir.nl.r4.obc|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.obc|release=V1.0.0-beta.1|namespace=obc}}}}<br /> |}<br /> <br /> Note that each PROM questionnaire building block in the functional data set is represented by a separate Questionnaire instance. However, these are not listed here, but are instead added as [https://simplifier.net/nictiz-r4-outcomebasedcare//~resources?category=Example&amp;exampletype=Questionnaire MISSING instances] to the FHIR package.<br /> <br /> == Mappings between profiles and data set ==<br /> === Questionnaire instances ===<br /> <br /> Each instance of a FHIR Questionnaire contains the following elements:<br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Type<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Concept<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Mapping<br /> |-<br /> | uri<br /> | Questionnaire Coding system<br /> | Questionnaire.Coding.system<br /> |-<br /> | code<br /> | Questionnaire code<br /> | Questionnaire.Coding.code<br /> |-<br /> | string<br /> | Questionnaire code display<br /> | Questionnaire.Coding.display<br /> |-<br /> | string<br /> | Title of Questionnaire<br /> | Questionnaire.title<br /> |-<br /> | string<br /> | Publisher information<br /> | Questionnaire.publisher<br /> |-<br /> | string<br /> | Version of Questionnaire<br /> | Questionnaire.version<br /> |-<br /> | code<br /> | Language of Questionnaire<br /> | Questionnaire.meta.language<br /> |-<br /> | coding<br /> | Domain code of Questionnaire<br /> | Questionnaire.usageContext.code<br /> |-<br /> | any<br /> | Domain of Questionnaire<br /> | Questionnaire.usageContext.value<br /> |-<br /> | markdown (string)<br /> | License/Author information<br /> | Questionnaire.copyright<br /> |-<br /> | string<br /> | Instructions for a question or group of questions<br /> | Questionnaire.item.text<br /> |-<br /> | boolean<br /> | Read-only instructions for a question or group of questions<br /> | Questionnaire.item.readOnly<br /> |-<br /> | ??coding<br /> | Instruction format<br /> | Questionnaire.item.extension:renderingStyle??<br /> |-<br /> | string<br /> | Question<br /> | Questionnaire.item.text<br /> |-<br /> | code<br /> | Value type of question<br /> | Questionnaire.item.type<br /> |-<br /> | coding<br /> | Flag for sensitive questions<br /> | Questionnaire.item.linkId.extension:sensitivityFlag<br /> |-<br /> | ??coding<br /> | Question format<br /> | Questionnaire.item.extension:renderingStyle??<br /> |-<br /> | string<br /> | ??Score rating for questionnaire??<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Read-only score rating <br /> | Questionnaire.item.readOnly<br /> |-<br /> | boolean<br /> | Hidden score rating <br /> | Questionnaire.item.extension:hidden<br /> |-<br /> | string<br /> | Total score for questionnaire<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Hidden total score<br /> | Questionnaire.item.extension:hidden<br /> |-<br /> | string<br /> | Score calculation rules for questionnaire<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Read-only score calculation rules<br /> | Questionnaire.item.readOnly<br /> |-<br /> | boolean<br /> | Hidden score calculation rules<br /> | Questionnaire.item.extension:hidden<br /> |-<br /> | string<br /> | Interpretation score calculation rules for questionnaire<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Read-only interpretation score calculation rules<br /> | Questionnaire.item.readOnly<br /> |-<br /> | boolean<br /> | Hidden interpretation score calculation rules<br /> | Questionnaire.item.extension:hidden<br /> |}<br /> <br /> === QuestionnaireResponse profile ===<br /> The QuestionnaireResponse profile is connected to the functional definitions in ART-DECOR. It includes mappings to all data elements within the functional data set (prefixed with ‘obc-dataelement-10-').<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Type<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Id<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Concept<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Cardinality<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Profile<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Mapping<br /> |-<br /> | <br /> | 1405<br /> | Antwoordgegevens<br /> | 0 .. *<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse<br /> |-<br /> | Any??<br /> | 14??<br /> | Vraag<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.item??<br /> |-<br /> | Any<br /> | 1404<br /> | Antwoord<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.answer.value[x]<br /> |-<br /> | dateTime<br /> | 1406<br /> | InvulDatumTijd<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.authored<br /> |-<br /> | reference<br /> | 1407<br /> | Onderwerp<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.subject<br /> |-<br /> | reference<br /> | 1440<br /> | IngevuldeVragenlijst<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.questionnaire<br /> |-<br /> |}<br /> <br /> == Rendering ==<br /> A PROM questionnaire may take the form of a straightforward flat list of questions, but may also be hierarchically organized in groups and subgroups including patient instructions. Likewise, it can contain a wide range of question types, varying from simple fill-out fields to multiple-choice questions, scales and questions with dependencies to previous answers. As a result, different styles can be rendered for particular items.<br /> <br /> The FHIR base Questionnaire resource offers limited rendering capabilities, with item labels and text elements displayed sequentially, and choice options provided through renderer-determined controls. For more control, the core specification defines additional elements and extensions, including the [https://build.fhir.org/ig/HL7/sdc/rendering.html rendering-style] extension. This extension allows the full capabilities of the HTML style attribute to be applied to items in a questionnaire, such as changing font or color, and adjusting font styles like bold, italics, or small caps. Conformant systems may ignore this extension unless the rendering-styleSensitive flag is set to true.<br /> <br /> The JSON snippet below is an example of a Questionnaire instance that contains the rendering-style extension to make the item partially bold.<br /> <br /> [INSERT SNIPPET]<br /> <br /> == Questionnaire versioning ==<br /> PROMs are subject to change over time, with alterations or additions made to their questions and answer options, as well as to the underlying algorithm used to calculate the scores. Any changes made to these PROMs are recorded and disseminated through ?Amigo?. To accurately analyse PSOM (PROMs Standard Operating Model) data, it is crucial to determine which version of the PROM was filled out by the subject. This can be done by matching the PROM version with the Amigo reference number.<br /> <br /> In FHIR, the version of a PROM can be registered in the {{fhir|Questionnaire.version}} element. A Questionnaire is referenced from other resources by its [https://www.hl7.org/fhir/r4/references.html#canonical canonical URL]. To reference a particular version of a Questionnaire, users must combine the canonical URL and version using a pipe character in the format: [canonicalURL]|[version]. When users refer to a Questionnaire with just the {{fhir|.url}}, they automatically refer to the latest version.<br /> <br /> However, the definition of 'latest version' may vary for Amigo compared to what the PROMs provider may consider latest. Therefore, to ensure clarity about which version of the PROM is requested and collected, any references in the {{fhir|QuestionnaireResponse.questionnaire}} SHALL always include a specific version.<br /> <br /> To note:<br /> *The assumption is that all PROMs will be registered with a version number.<br /> *Amigo will be responsible for assigning version numbers to ensure these reflect a consistent standard approach for the organization.<br /> <br /> == Sensitive questions ==<br /> <br /> Every PROM may include sensitive questions, indicating that the answers might contain sensitive information. As a result, a specific level of authorization is required to read these answers.<br /> <br /> The Data Segmentation for Privacy project defined the Inline Security Label extension. This extension enables flagging elements with a security label, for example indicating their sensitivity, and SHALL be added to all relevant {{fhir|.item}} elements as {{fhir|.item.linkId.extension:sensitivityFlag}} in both the Questionnaire and QuestionnaireResponse instances. The {{fhir|.valueCoding}} SHALL be populated with the code PDS from the InformationSensitivityPolicy ValueSet to indicate this data item contains sensitive information reported by the patient.<br /> <br /> == Scores and calculation rules ==<br /> The Questionnaire definition includes information on how to calculate the total score, the weight for each question, and how to interpret the total score. Currently, this information is provided in {{fhir|.item}} elements, where the calculation rules are read-only instructions and hidden from users completing the forms through an extension.<br /> <br /> In the next version of the Questionnaire definition, it is the intention to incorporate dynamic calculation rules using structured data capture, making the Questionnaire more structured and flexible.</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=uz:V1.0.0-alpha.1_FHIR_OBC&diff=223710 2024-08-05T08:17:30Z

<p>Luud Slagter: /* Questionnaire versioning */</p> <hr /> <div>{{Vdraft/InformationBox|This FHIR IG is currently under development and can not be considered stable and ready for use. For questions and change requests regarding this IG, please create a ticket in [{{VersieInfo|BITS|release=V1.0.0|namespace=uz}} BITS].}}<br /> <br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide OBC version {{VersieInfo|OBC|release=V1.0.0|namespace=uz}}}}<br /> <br /> = Introduction =<br /> <br /> This implementation guide (IG) functions as the initial draft for the pilot phase of a new information standard, Outcome-Based Care (OBC, Dutch: Uitkomstgerichte zorg), version {{VersieInfo|OBC|release=V1.0.0}}. This IG is developed using [https://www.hl7.org/fhir/R4/ HL7 FHIR R4]. It assumes that the reader is familiar with both this version of FHIR and the functional specification [TO-ADD link]. This information standard is inspired by the international [http://hl7.org/fhir/us/sdc/index.html Structured Data Capture (SDC)] implementation guide and tries to follow it where possible.<br /> <br /> 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 Overarching principles and the use of FHIR packages. <br /> <br /> This IG first describes the boundaries and relationships in place, after which the implementation of PROMs in FHIR is described.<br /> <br /> = Boundaries and relationships =<br /> <br /> == Boundaries ==<br /> As mentioned in the introduction, this IG serves as a precursor for the pilot phase of the new information standard OBC. This version of the IG focuses solely on the manifestation of PROM questionnaires and their corresponding answers in FHIR. It does not include clinical data or use cases for data exchange, as the primary goal of the pilot is to evaluate the feasibility of implementing FHIR in this context. It is the intention to expand the scope in future versions of the IG to include clinical data and data exchange use cases, ultimately aiming to develop OBC into a comprehensive information standard.<br /> <br /> == FHIR resources and building blocks ==<br /> The PROM questionnaires and response data building blocks within OBC version {{VersieInfo|OBC|release=V1.0.0}} are not based on any publication of the Dutch Health and Care Information Models (Dutch: ‘zorginformatiebouwstenen’ or ‘zibs’), as there are no zibs that represent these building blocks. Therefore, there is no dependency on corresponding nl-core profiles, and mappings to zib concepts are not defined. Currently, there are no plans to create more general nl-core profiles, as no corresponding zibs exist. <br /> <br /> === Questionnaire ===<br /> <br /> Each PROM questionnaire is represented through a dedicated FHIR Questionnaire instance. A FHIR Questionnaire is a definitional artifact, which means it defines the questions to be asked, how these should be structured and rendered, and what answers are allowed. More information on structure and rendering of the FHIR Questionnaire instances can be found in [[#Rendering|section 2.4]]. The answer options to each question are represented through terminology resources using ValueSets and CodeSystems.<br /> <br /> The primary purpose of representing PROMs as Questionnaire instances is to establish a canonical identifier for each PROM in the form of a URI. This URI serves as a linkage point connecting every QuestionnaireResponse to their corresponding Questionnaire.<br /> <br /> The Questionnaire resource isn't strictly necessary to create a QuestionnaireResponse. However, using FHIR Questionnaire instances for PROMs provides significant benefits through standardized and structured formatting. Each question is included in the Questionnaire as a separate {{fhir|.item}} and has a unique identifier in the corresponding {{fhir|.item.linkId}} element. Additionally, the terminology used in PROMs is represented in FHIR ValueSet and CodeSystem resources and is correctly linked to the questions in the Questionnaire, ensuring all definitions are easily accessible for implementers.<br /> <br /> === QuestionnaireResponse ===<br /> <br /> The collection of outcomes and scores of a PROM is represented in a FHIR QuestionnaireResponse profile. For every completed PROM, an instance conforming to the [https://simplifier.net/nictiz-r4-outcomebasedcare/obcquestionnaireresponse obc-QuestionnaireResponse] profile is created. This profile features a structured set of answers with linked ids to the answered questions. The QuestionnaireResponse also includes the completion date and the language of the completed form.<br /> <br /> The QuestionnaireResponse contains enough information about the questions asked that it can be interpreted somewhat independently from the Questionnaire it is based on. In other words, no access to the Questionnaire is necessary in order to extract basic information from a QuestionnaireResponse.<br /> <br /> === Main building blocks ===<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ResponseData<br /> | Antwoordgegevens<br /> | QuestionnaireResponse<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse|nictiz.fhir.nl.r4.obc|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.obc|release=V1.0.0-beta.1|namespace=obc}}}}<br /> |}<br /> <br /> Note that each PROM questionnaire building block in the functional data set is represented by a separate Questionnaire instance. However, these are not listed here, but are instead added as [https://simplifier.net/nictiz-r4-outcomebasedcare//~resources?category=Example&amp;exampletype=Questionnaire MISSING instances] to the FHIR package.<br /> <br /> == Mappings between profiles and data set ==<br /> === Questionnaire instances ===<br /> <br /> Each instance of a FHIR Questionnaire contains the following elements:<br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Type<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Concept<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Mapping<br /> |-<br /> | uri<br /> | Questionnaire Coding system<br /> | Questionnaire.Coding.system<br /> |-<br /> | code<br /> | Questionnaire code<br /> | Questionnaire.Coding.code<br /> |-<br /> | string<br /> | Questionnaire code display<br /> | Questionnaire.Coding.display<br /> |-<br /> | string<br /> | Title of Questionnaire<br /> | Questionnaire.title<br /> |-<br /> | string<br /> | Publisher information<br /> | Questionnaire.publisher<br /> |-<br /> | string<br /> | Version of Questionnaire<br /> | Questionnaire.version<br /> |-<br /> | code<br /> | Language of Questionnaire<br /> | Questionnaire.meta.language<br /> |-<br /> | coding<br /> | Domain code of Questionnaire<br /> | Questionnaire.usageContext.code<br /> |-<br /> | any<br /> | Domain of Questionnaire<br /> | Questionnaire.usageContext.value<br /> |-<br /> | markdown (string)<br /> | License/Author information<br /> | Questionnaire.copyright<br /> |-<br /> | string<br /> | Instructions for a question or group of questions<br /> | Questionnaire.item.text<br /> |-<br /> | boolean<br /> | Read-only instructions for a question or group of questions<br /> | Questionnaire.item.readOnly<br /> |-<br /> | ??coding<br /> | Instruction format<br /> | Questionnaire.item.extension:renderingStyle??<br /> |-<br /> | string<br /> | Question<br /> | Questionnaire.item.text<br /> |-<br /> | code<br /> | Value type of question<br /> | Questionnaire.item.type<br /> |-<br /> | coding<br /> | Flag for sensitive questions<br /> | Questionnaire.item.linkId.extension:sensitivityFlag<br /> |-<br /> | ??coding<br /> | Question format<br /> | Questionnaire.item.extension:renderingStyle??<br /> |-<br /> | string<br /> | ??Score rating for questionnaire??<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Read-only score rating <br /> | Questionnaire.item.readOnly<br /> |-<br /> | boolean<br /> | Hidden score rating <br /> | Questionnaire.item.extension:hidden<br /> |-<br /> | string<br /> | Total score for questionnaire<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Hidden total score<br /> | Questionnaire.item.extension:hidden<br /> |-<br /> | string<br /> | Score calculation rules for questionnaire<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Read-only score calculation rules<br /> | Questionnaire.item.readOnly<br /> |-<br /> | boolean<br /> | Hidden score calculation rules<br /> | Questionnaire.item.extension:hidden<br /> |-<br /> | string<br /> | Interpretation score calculation rules for questionnaire<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Read-only interpretation score calculation rules<br /> | Questionnaire.item.readOnly<br /> |-<br /> | boolean<br /> | Hidden interpretation score calculation rules<br /> | Questionnaire.item.extension:hidden<br /> |}<br /> <br /> === QuestionnaireResponse profile ===<br /> The QuestionnaireResponse profile is connected to the functional definitions in ART-DECOR. It includes mappings to all data elements within the functional data set (prefixed with ‘obc-dataelement-10-').<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Type<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Id<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Concept<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Cardinality<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Profile<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Mapping<br /> |-<br /> | <br /> | 1405<br /> | Antwoordgegevens<br /> | 0 .. *<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse<br /> |-<br /> | Any??<br /> | 14??<br /> | Vraag<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.item??<br /> |-<br /> | Any<br /> | 1404<br /> | Antwoord<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.answer.value[x]<br /> |-<br /> | dateTime<br /> | 1406<br /> | InvulDatumTijd<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.authored<br /> |-<br /> | reference<br /> | 1407<br /> | Onderwerp<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.subject<br /> |-<br /> | reference<br /> | 1440<br /> | IngevuldeVragenlijst<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.questionnaire<br /> |-<br /> |}<br /> <br /> == Rendering ==<br /> A PROM questionnaire may take the form of a straightforward flat list of questions, but may also be hierarchically organized in groups and subgroups including patient instructions. Likewise, it can contain a wide range of question types, varying from simple fill-out fields to multiple-choice questions, scales and questions with dependencies to previous answers. As a result, different styles can be rendered for particular items.<br /> <br /> The FHIR base Questionnaire resource offers limited rendering capabilities, with item labels and text elements displayed sequentially, and choice options provided through renderer-determined controls. For more control, the core specification defines additional elements and extensions, including the [https://build.fhir.org/ig/HL7/sdc/rendering.html rendering-style] extension. This extension allows the full capabilities of the HTML style attribute to be applied to items in a questionnaire, such as changing font or color, and adjusting font styles like bold, italics, or small caps. Conformant systems may ignore this extension unless the rendering-styleSensitive flag is set to true.<br /> <br /> The JSON snippet below is an example of a Questionnaire instance that contains the rendering-style extension to make the item partially bold.<br /> <br /> [INSERT SNIPPET]<br /> <br /> == Questionnaire versioning ==<br /> PROMs are subject to change over time, with alterations or additions made to their questions and answer options, as well as to the underlying algorithm used to calculate the scores. Any changes made to these PROMs are recorded and disseminated through ?Amigo?. To accurately analyse PSOM (PROMs Standard Operating Model) data, it is crucial to determine which version of the PROM was filled out by the subject. This can be done by matching the PROM version with the Amigo reference number.<br /> <br /> In FHIR, the version of a PROM can be registered in the {{fhir|Questionnaire.version}} element. A Questionnaire is referenced from other resources by its [https://www.hl7.org/fhir/r4/references.html#canonical canonical URL]. To reference a particular version of a Questionnaire, users must combine the canonical URL and version using a pipe character in the format: [canonicalURL]|[version]. When users refer to a Questionnaire with just the {{fhir|.url}}, they automatically refer to the latest version.<br /> <br /> However, the definition of 'latest version' may vary for Amigo compared to what the PROMs provider may consider latest. Therefore, to ensure clarity about which version of the PROM is requested and collected, any references in the {{fhir|QuestionnaireResponse.questionnaire}} SHALL always include a specific version.<br /> <br /> To note:<br /> *The assumption is that all PROMs will be registered with a version number.<br /> *Amigo will be responsible for assigning version numbers to ensure these reflect a consistent standard approach for the organization.<br /> <br /> == Sensitive questions ==<br /> <br /> Every PROM may include sensitive questions, indicating that the answers might contain sensitive information. As a result, a specific level of authorization is required to read these answers.<br /> <br /> The Data Segmentation for Privacy project defined the Inline Security Label extension. This extension enables flagging elements with a security label, for example indicating their sensitivity, and SHALL be added to all relevant {{fhir|.item}} elements as {{fhir|.item.linkId.extension:sensitivityFlag}} in both the Questionnaire and QuestionnaireResponse instances. The {{fhir|.valueCoding}} SHALL be populated with the code PDS from the InformationSensitivityPolicy ValueSet to indicate this data item contains sensitive information reported by the patient.<br /> <br /> == Scores and calculation rules ==<br /> The Questionnaire definition includes information on how to calculate the total score, the weight for each question, and how to interpret the total score. Currently, this information is provided in {{fhir|.item}} elements, where the calculation rules are read-only instructions and hidden from users completing the forms through an extension.<br /> <br /> In the next version of the Questionnaire definition, the plan is to incorporate dynamic calculation rules using structured data capture, making the Questionnaire more structured and flexible.</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=uz:V1.0.0-alpha.1_FHIR_OBC&diff=223707 2024-08-05T08:08:46Z

<p>Luud Slagter: /* Rendering */</p> <hr /> <div>{{Vdraft/InformationBox|This FHIR IG is currently under development and can not be considered stable and ready for use. For questions and change requests regarding this IG, please create a ticket in [{{VersieInfo|BITS|release=V1.0.0|namespace=uz}} BITS].}}<br /> <br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide OBC version {{VersieInfo|OBC|release=V1.0.0|namespace=uz}}}}<br /> <br /> = Introduction =<br /> <br /> This implementation guide (IG) functions as the initial draft for the pilot phase of a new information standard, Outcome-Based Care (OBC, Dutch: Uitkomstgerichte zorg), version {{VersieInfo|OBC|release=V1.0.0}}. This IG is developed using [https://www.hl7.org/fhir/R4/ HL7 FHIR R4]. It assumes that the reader is familiar with both this version of FHIR and the functional specification [TO-ADD link]. This information standard is inspired by the international [http://hl7.org/fhir/us/sdc/index.html Structured Data Capture (SDC)] implementation guide and tries to follow it where possible.<br /> <br /> 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 Overarching principles and the use of FHIR packages. <br /> <br /> This IG first describes the boundaries and relationships in place, after which the implementation of PROMs in FHIR is described.<br /> <br /> = Boundaries and relationships =<br /> <br /> == Boundaries ==<br /> As mentioned in the introduction, this IG serves as a precursor for the pilot phase of the new information standard OBC. This version of the IG focuses solely on the manifestation of PROM questionnaires and their corresponding answers in FHIR. It does not include clinical data or use cases for data exchange, as the primary goal of the pilot is to evaluate the feasibility of implementing FHIR in this context. It is the intention to expand the scope in future versions of the IG to include clinical data and data exchange use cases, ultimately aiming to develop OBC into a comprehensive information standard.<br /> <br /> == FHIR resources and building blocks ==<br /> The PROM questionnaires and response data building blocks within OBC version {{VersieInfo|OBC|release=V1.0.0}} are not based on any publication of the Dutch Health and Care Information Models (Dutch: ‘zorginformatiebouwstenen’ or ‘zibs’), as there are no zibs that represent these building blocks. Therefore, there is no dependency on corresponding nl-core profiles, and mappings to zib concepts are not defined. Currently, there are no plans to create more general nl-core profiles, as no corresponding zibs exist. <br /> <br /> === Questionnaire ===<br /> <br /> Each PROM questionnaire is represented through a dedicated FHIR Questionnaire instance. A FHIR Questionnaire is a definitional artifact, which means it defines the questions to be asked, how these should be structured and rendered, and what answers are allowed. More information on structure and rendering of the FHIR Questionnaire instances can be found in [[#Rendering|section 2.4]]. The answer options to each question are represented through terminology resources using ValueSets and CodeSystems.<br /> <br /> The primary purpose of representing PROMs as Questionnaire instances is to establish a canonical identifier for each PROM in the form of a URI. This URI serves as a linkage point connecting every QuestionnaireResponse to their corresponding Questionnaire.<br /> <br /> The Questionnaire resource isn't strictly necessary to create a QuestionnaireResponse. However, using FHIR Questionnaire instances for PROMs provides significant benefits through standardized and structured formatting. Each question is included in the Questionnaire as a separate {{fhir|.item}} and has a unique identifier in the corresponding {{fhir|.item.linkId}} element. Additionally, the terminology used in PROMs is represented in FHIR ValueSet and CodeSystem resources and is correctly linked to the questions in the Questionnaire, ensuring all definitions are easily accessible for implementers.<br /> <br /> === QuestionnaireResponse ===<br /> <br /> The collection of outcomes and scores of a PROM is represented in a FHIR QuestionnaireResponse profile. For every completed PROM, an instance conforming to the [https://simplifier.net/nictiz-r4-outcomebasedcare/obcquestionnaireresponse obc-QuestionnaireResponse] profile is created. This profile features a structured set of answers with linked ids to the answered questions. The QuestionnaireResponse also includes the completion date and the language of the completed form.<br /> <br /> The QuestionnaireResponse contains enough information about the questions asked that it can be interpreted somewhat independently from the Questionnaire it is based on. In other words, no access to the Questionnaire is necessary in order to extract basic information from a QuestionnaireResponse.<br /> <br /> === Main building blocks ===<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ResponseData<br /> | Antwoordgegevens<br /> | QuestionnaireResponse<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse|nictiz.fhir.nl.r4.obc|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.obc|release=V1.0.0-beta.1|namespace=obc}}}}<br /> |}<br /> <br /> Note that each PROM questionnaire building block in the functional data set is represented by a separate Questionnaire instance. However, these are not listed here, but are instead added as [https://simplifier.net/nictiz-r4-outcomebasedcare//~resources?category=Example&amp;exampletype=Questionnaire MISSING instances] to the FHIR package.<br /> <br /> == Mappings between profiles and data set ==<br /> === Questionnaire instances ===<br /> <br /> Each instance of a FHIR Questionnaire contains the following elements:<br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Type<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Concept<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Mapping<br /> |-<br /> | uri<br /> | Questionnaire Coding system<br /> | Questionnaire.Coding.system<br /> |-<br /> | code<br /> | Questionnaire code<br /> | Questionnaire.Coding.code<br /> |-<br /> | string<br /> | Questionnaire code display<br /> | Questionnaire.Coding.display<br /> |-<br /> | string<br /> | Title of Questionnaire<br /> | Questionnaire.title<br /> |-<br /> | string<br /> | Publisher information<br /> | Questionnaire.publisher<br /> |-<br /> | string<br /> | Version of Questionnaire<br /> | Questionnaire.version<br /> |-<br /> | code<br /> | Language of Questionnaire<br /> | Questionnaire.meta.language<br /> |-<br /> | coding<br /> | Domain code of Questionnaire<br /> | Questionnaire.usageContext.code<br /> |-<br /> | any<br /> | Domain of Questionnaire<br /> | Questionnaire.usageContext.value<br /> |-<br /> | markdown (string)<br /> | License/Author information<br /> | Questionnaire.copyright<br /> |-<br /> | string<br /> | Instructions for a question or group of questions<br /> | Questionnaire.item.text<br /> |-<br /> | boolean<br /> | Read-only instructions for a question or group of questions<br /> | Questionnaire.item.readOnly<br /> |-<br /> | ??coding<br /> | Instruction format<br /> | Questionnaire.item.extension:renderingStyle??<br /> |-<br /> | string<br /> | Question<br /> | Questionnaire.item.text<br /> |-<br /> | code<br /> | Value type of question<br /> | Questionnaire.item.type<br /> |-<br /> | coding<br /> | Flag for sensitive questions<br /> | Questionnaire.item.linkId.extension:sensitivityFlag<br /> |-<br /> | ??coding<br /> | Question format<br /> | Questionnaire.item.extension:renderingStyle??<br /> |-<br /> | string<br /> | ??Score rating for questionnaire??<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Read-only score rating <br /> | Questionnaire.item.readOnly<br /> |-<br /> | boolean<br /> | Hidden score rating <br /> | Questionnaire.item.extension:hidden<br /> |-<br /> | string<br /> | Total score for questionnaire<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Hidden total score<br /> | Questionnaire.item.extension:hidden<br /> |-<br /> | string<br /> | Score calculation rules for questionnaire<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Read-only score calculation rules<br /> | Questionnaire.item.readOnly<br /> |-<br /> | boolean<br /> | Hidden score calculation rules<br /> | Questionnaire.item.extension:hidden<br /> |-<br /> | string<br /> | Interpretation score calculation rules for questionnaire<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Read-only interpretation score calculation rules<br /> | Questionnaire.item.readOnly<br /> |-<br /> | boolean<br /> | Hidden interpretation score calculation rules<br /> | Questionnaire.item.extension:hidden<br /> |}<br /> <br /> === QuestionnaireResponse profile ===<br /> The QuestionnaireResponse profile is connected to the functional definitions in ART-DECOR. It includes mappings to all data elements within the functional data set (prefixed with ‘obc-dataelement-10-').<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Type<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Id<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Concept<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Cardinality<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Profile<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Mapping<br /> |-<br /> | <br /> | 1405<br /> | Antwoordgegevens<br /> | 0 .. *<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse<br /> |-<br /> | Any??<br /> | 14??<br /> | Vraag<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.item??<br /> |-<br /> | Any<br /> | 1404<br /> | Antwoord<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.answer.value[x]<br /> |-<br /> | dateTime<br /> | 1406<br /> | InvulDatumTijd<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.authored<br /> |-<br /> | reference<br /> | 1407<br /> | Onderwerp<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.subject<br /> |-<br /> | reference<br /> | 1440<br /> | IngevuldeVragenlijst<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.questionnaire<br /> |-<br /> |}<br /> <br /> == Rendering ==<br /> A PROM questionnaire may take the form of a straightforward flat list of questions, but may also be hierarchically organized in groups and subgroups including patient instructions. Likewise, it can contain a wide range of question types, varying from simple fill-out fields to multiple-choice questions, scales and questions with dependencies to previous answers. As a result, different styles can be rendered for particular items.<br /> <br /> The FHIR base Questionnaire resource offers limited rendering capabilities, with item labels and text elements displayed sequentially, and choice options provided through renderer-determined controls. For more control, the core specification defines additional elements and extensions, including the [https://build.fhir.org/ig/HL7/sdc/rendering.html rendering-style] extension. This extension allows the full capabilities of the HTML style attribute to be applied to items in a questionnaire, such as changing font or color, and adjusting font styles like bold, italics, or small caps. Conformant systems may ignore this extension unless the rendering-styleSensitive flag is set to true.<br /> <br /> The JSON snippet below is an example of a Questionnaire instance that contains the rendering-style extension to make the item partially bold.<br /> <br /> [INSERT SNIPPET]<br /> <br /> == Questionnaire versioning ==<br /> PROMs are subject to change over time, with alterations or additions made to their questions and answer options, as well as to the underlying algorithm used to calculate the scores. Any changes made to these PROMs are recorded and disseminated through ?Amigo?. To accurately analyse PSOM (PROMs Standard Operating Model) data, it is crucial to determine which version of the PROM was filled out by the subject. This can be done by matching the PROM version with the Amigo reference number.<br /> <br /> In FHIR, the version of a PROMs can be registered in the {{fhir|Questionnaire.version element}}. A Questionnaire is referenced from other resources by its [https://www.hl7.org/fhir/r4/references.html#canonical canonical URL]. To reference a particular version of a Questionnaire, users must combine the canonical URL and version using a pipe character in the format: [canonicalURL]|[version]. When users refer to a Questionnaire with just the {{fhir|.url}}, they automatically refer to the latest version.<br /> <br /> However, the definition of 'latest version' may vary for Amigo compared to what the PROMs provider may consider latest. Therefore, to ensure clarity about which version of the PROMs is requested and collected, any references in the {{fhir|QuestionnaireResponse.questionnaire}} SHALL always include a specific version.<br /> <br /> To note:<br /> *The assumption is that all PROMs will be registered with a version number.<br /> *Amigo will be responsible for assigning version numbers to ensure these reflect a consistent standard approach for the organisation.<br /> <br /> == Sensitive questions ==<br /> <br /> Every PROM may include sensitive questions, indicating that the answers might contain sensitive information. As a result, a specific level of authorization is required to read these answers.<br /> <br /> The Data Segmentation for Privacy project defined the Inline Security Label extension. This extension enables flagging elements with a security label, for example indicating their sensitivity, and SHALL be added to all relevant {{fhir|.item}} elements as {{fhir|.item.linkId.extension:sensitivityFlag}} in both the Questionnaire and QuestionnaireResponse instances. The {{fhir|.valueCoding}} SHALL be populated with the code PDS from the InformationSensitivityPolicy ValueSet to indicate this data item contains sensitive information reported by the patient.<br /> <br /> == Scores and calculation rules ==<br /> The Questionnaire definition includes information on how to calculate the total score, the weight for each question, and how to interpret the total score. Currently, this information is provided in {{fhir|.item}} elements, where the calculation rules are read-only instructions and hidden from users completing the forms through an extension.<br /> <br /> In the next version of the Questionnaire definition, the plan is to incorporate dynamic calculation rules using structured data capture, making the Questionnaire more structured and flexible.</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=uz:V1.0.0-alpha.1_FHIR_OBC&diff=223685 2024-08-05T06:10:11Z

<p>Luud Slagter: /* Main building blocks */</p> <hr /> <div>{{Vdraft/InformationBox|This FHIR IG is currently under development and can not be considered stable and ready for use. For questions and change requests regarding this IG, please create a ticket in [{{VersieInfo|BITS|release=V1.0.0|namespace=uz}} BITS].}}<br /> <br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide OBC version {{VersieInfo|OBC|release=V1.0.0|namespace=uz}}}}<br /> <br /> = Introduction =<br /> <br /> This implementation guide (IG) functions as the initial draft for the pilot phase of a new information standard, Outcome-Based Care (OBC, Dutch: Uitkomstgerichte zorg), version {{VersieInfo|OBC|release=V1.0.0}}. This IG is developed using [https://www.hl7.org/fhir/R4/ HL7 FHIR R4]. It assumes that the reader is familiar with both this version of FHIR and the functional specification [TO-ADD link]. This information standard is inspired by the international [http://hl7.org/fhir/us/sdc/index.html Structured Data Capture (SDC)] implementation guide and tries to follow it where possible.<br /> <br /> 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 Overarching principles and the use of FHIR packages. <br /> <br /> This IG first describes the boundaries and relationships in place, after which the implementation of PROMs in FHIR is described.<br /> <br /> = Boundaries and relationships =<br /> <br /> == Boundaries ==<br /> As mentioned in the introduction, this IG serves as a precursor for the pilot phase of the new information standard OBC. This version of the IG focuses solely on the manifestation of PROM questionnaires and their corresponding answers in FHIR. It does not include clinical data or use cases for data exchange, as the primary goal of the pilot is to evaluate the feasibility of implementing FHIR in this context. It is the intention to expand the scope in future versions of the IG to include clinical data and data exchange use cases, ultimately aiming to develop OBC into a comprehensive information standard.<br /> <br /> == FHIR resources and building blocks ==<br /> The PROM questionnaires and response data building blocks within OBC version {{VersieInfo|OBC|release=V1.0.0}} are not based on any publication of the Dutch Health and Care Information Models (Dutch: ‘zorginformatiebouwstenen’ or ‘zibs’), as there are no zibs that represent these building blocks. Therefore, there is no dependency on corresponding nl-core profiles, and mappings to zib concepts are not defined. Currently, there are no plans to create more general nl-core profiles, as no corresponding zibs exist. <br /> <br /> === Questionnaire ===<br /> <br /> Each PROM questionnaire is represented through a dedicated FHIR Questionnaire instance. A FHIR Questionnaire is a definitional artifact, which means it defines the questions to be asked, how these should be structured and rendered, and what answers are allowed. More information on structure and rendering of the FHIR Questionnaire instances can be found in [[#Rendering|section 2.4]]. The answer options to each question are represented through terminology resources using ValueSets and CodeSystems.<br /> <br /> The primary purpose of representing PROMs as Questionnaire instances is to establish a canonical identifier for each PROM in the form of a URI. This URI serves as a linkage point connecting every QuestionnaireResponse to their corresponding Questionnaire.<br /> <br /> The Questionnaire resource isn't strictly necessary to create a QuestionnaireResponse. However, using FHIR Questionnaire instances for PROMs provides significant benefits through standardized and structured formatting. Each question is included in the Questionnaire as a separate {{fhir|.item}} and has a unique identifier in the corresponding {{fhir|.item.linkId}} element. Additionally, the terminology used in PROMs is represented in FHIR ValueSet and CodeSystem resources and is correctly linked to the questions in the Questionnaire, ensuring all definitions are easily accessible for implementers.<br /> <br /> === QuestionnaireResponse ===<br /> <br /> The collection of outcomes and scores of a PROM is represented in a FHIR QuestionnaireResponse profile. For every completed PROM, an instance conforming to the [https://simplifier.net/nictiz-r4-outcomebasedcare/obcquestionnaireresponse obc-QuestionnaireResponse] profile is created. This profile features a structured set of answers with linked ids to the answered questions. The QuestionnaireResponse also includes the completion date and the language of the completed form.<br /> <br /> The QuestionnaireResponse contains enough information about the questions asked that it can be interpreted somewhat independently from the Questionnaire it is based on. In other words, no access to the Questionnaire is necessary in order to extract basic information from a QuestionnaireResponse.<br /> <br /> === Main building blocks ===<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ResponseData<br /> | Antwoordgegevens<br /> | QuestionnaireResponse<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse|nictiz.fhir.nl.r4.obc|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.obc|release=V1.0.0-beta.1|namespace=obc}}}}<br /> |}<br /> <br /> Note that each PROM questionnaire building block in the functional data set is represented by a separate Questionnaire instance. However, these are not listed here, but are instead added as [https://simplifier.net/nictiz-r4-outcomebasedcare//~resources?category=Example&amp;exampletype=Questionnaire MISSING instances] to the FHIR package.<br /> <br /> == Mappings between profiles and data set ==<br /> === Questionnaire instances ===<br /> <br /> Each instance of a FHIR Questionnaire contains the following elements:<br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Type<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Concept<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Mapping<br /> |-<br /> | uri<br /> | Questionnaire Coding system<br /> | Questionnaire.Coding.system<br /> |-<br /> | code<br /> | Questionnaire code<br /> | Questionnaire.Coding.code<br /> |-<br /> | string<br /> | Questionnaire code display<br /> | Questionnaire.Coding.display<br /> |-<br /> | string<br /> | Title of Questionnaire<br /> | Questionnaire.title<br /> |-<br /> | string<br /> | Publisher information<br /> | Questionnaire.publisher<br /> |-<br /> | string<br /> | Version of Questionnaire<br /> | Questionnaire.version<br /> |-<br /> | code<br /> | Language of Questionnaire<br /> | Questionnaire.meta.language<br /> |-<br /> | coding<br /> | Domain code of Questionnaire<br /> | Questionnaire.usageContext.code<br /> |-<br /> | any<br /> | Domain of Questionnaire<br /> | Questionnaire.usageContext.value<br /> |-<br /> | markdown (string)<br /> | License/Author information<br /> | Questionnaire.copyright<br /> |-<br /> | string<br /> | Instructions for a question or group of questions<br /> | Questionnaire.item.text<br /> |-<br /> | boolean<br /> | Read-only instructions for a question or group of questions<br /> | Questionnaire.item.readOnly<br /> |-<br /> | ??coding<br /> | Instruction format<br /> | Questionnaire.item.extension:renderingStyle??<br /> |-<br /> | string<br /> | Question<br /> | Questionnaire.item.text<br /> |-<br /> | code<br /> | Value type of question<br /> | Questionnaire.item.type<br /> |-<br /> | coding<br /> | Flag for sensitive questions<br /> | Questionnaire.item.linkId.extension:sensitivityFlag<br /> |-<br /> | ??coding<br /> | Question format<br /> | Questionnaire.item.extension:renderingStyle??<br /> |-<br /> | string<br /> | ??Score rating for questionnaire??<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Read-only score rating <br /> | Questionnaire.item.readOnly<br /> |-<br /> | boolean<br /> | Hidden score rating <br /> | Questionnaire.item.extension:hidden<br /> |-<br /> | string<br /> | Total score for questionnaire<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Hidden total score<br /> | Questionnaire.item.extension:hidden<br /> |-<br /> | string<br /> | Score calculation rules for questionnaire<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Read-only score calculation rules<br /> | Questionnaire.item.readOnly<br /> |-<br /> | boolean<br /> | Hidden score calculation rules<br /> | Questionnaire.item.extension:hidden<br /> |-<br /> | string<br /> | Interpretation score calculation rules for questionnaire<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Read-only interpretation score calculation rules<br /> | Questionnaire.item.readOnly<br /> |-<br /> | boolean<br /> | Hidden interpretation score calculation rules<br /> | Questionnaire.item.extension:hidden<br /> |}<br /> <br /> === QuestionnaireResponse profile ===<br /> The QuestionnaireResponse profile is connected to the functional definitions in ART-DECOR. It includes mappings to all data elements within the functional data set (prefixed with ‘obc-dataelement-10-').<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Type<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Id<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Concept<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Cardinality<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Profile<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Mapping<br /> |-<br /> | <br /> | 1405<br /> | Antwoordgegevens<br /> | 0 .. *<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse<br /> |-<br /> | Any??<br /> | 14??<br /> | Vraag<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.item??<br /> |-<br /> | Any<br /> | 1404<br /> | Antwoord<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.answer.value[x]<br /> |-<br /> | dateTime<br /> | 1406<br /> | InvulDatumTijd<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.authored<br /> |-<br /> | reference<br /> | 1407<br /> | Onderwerp<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.subject<br /> |-<br /> | reference<br /> | 1440<br /> | IngevuldeVragenlijst<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.questionnaire<br /> |-<br /> |}<br /> <br /> == Rendering ==<br /> A PROM questionnaire may take the form of a straightforward flat list of questions, but may also be hierarchically organized in groups and sub-groups including patient instructions. Likewise, it can contain a wide range of question types, varying from simple fill-out fields to multiple-choice questions, scales and questions with dependency's to previous answers. As a result, different styles can be rendered for particular items.<br /> <br /> The FHIR base Questionnaire resource offers limited rendering capabilities, with item labels and text elements displayed sequentially, and choice options provided through renderer-determined controls. For more control, the core specification defines additional elements and extensions, including the [https://build.fhir.org/ig/HL7/sdc/rendering.html rendering-style] extension. This extension allows the full capabilities of the HTML style attribute to be applied to items in a questionnaire, such as changing font or color, and adjusting font styles like bold, italics, or small caps. Conformant systems may ignore this extension unless the rendering-styleSensitive flag is set to true.<br /> <br /> The JSON snippet below is an example of a Questionnaire instance that contains the rendering-style extension to make the item partially bold.<br /> <br /> [INSERT SNIPPET]<br /> <br /> == Questionnaire versioning ==<br /> PROMs are subject to change over time, with alterations or additions made to their questions and answer options, as well as to the underlying algorithm used to calculate the scores. Any changes made to these PROMs are recorded and disseminated through ?Amigo?. To accurately analyse PSOM (PROMs Standard Operating Model) data, it is crucial to determine which version of the PROM was filled out by the subject. This can be done by matching the PROM version with the Amigo reference number.<br /> <br /> In FHIR, the version of a PROMs can be registered in the {{fhir|Questionnaire.version element}}. A Questionnaire is referenced from other resources by its [https://www.hl7.org/fhir/r4/references.html#canonical canonical URL]. To reference a particular version of a Questionnaire, users must combine the canonical URL and version using a pipe character in the format: [canonicalURL]|[version]. When users refer to a Questionnaire with just the {{fhir|.url}}, they automatically refer to the latest version.<br /> <br /> However, the definition of 'latest version' may vary for Amigo compared to what the PROMs provider may consider latest. Therefore, to ensure clarity about which version of the PROMs is requested and collected, any references in the {{fhir|QuestionnaireResponse.questionnaire}} SHALL always include a specific version.<br /> <br /> To note:<br /> *The assumption is that all PROMs will be registered with a version number.<br /> *Amigo will be responsible for assigning version numbers to ensure these reflect a consistent standard approach for the organisation.<br /> <br /> == Sensitive questions ==<br /> <br /> Every PROM may include sensitive questions, indicating that the answers might contain sensitive information. As a result, a specific level of authorization is required to read these answers.<br /> <br /> The Data Segmentation for Privacy project defined the Inline Security Label extension. This extension enables flagging elements with a security label, for example indicating their sensitivity, and SHALL be added to all relevant {{fhir|.item}} elements as {{fhir|.item.linkId.extension:sensitivityFlag}} in both the Questionnaire and QuestionnaireResponse instances. The {{fhir|.valueCoding}} SHALL be populated with the code PDS from the InformationSensitivityPolicy ValueSet to indicate this data item contains sensitive information reported by the patient.<br /> <br /> == Scores and calculation rules ==<br /> The Questionnaire definition includes information on how to calculate the total score, the weight for each question, and how to interpret the total score. Currently, this information is provided in {{fhir|.item}} elements, where the calculation rules are read-only instructions and hidden from users completing the forms through an extension.<br /> <br /> In the next version of the Questionnaire definition, the plan is to incorporate dynamic calculation rules using structured data capture, making the Questionnaire more structured and flexible.</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=uz:V1.0.0-alpha.1_FHIR_OBC&diff=223684 2024-08-05T06:09:29Z

<p>Luud Slagter: /* Questionnaire instance */</p> <hr /> <div>{{Vdraft/InformationBox|This FHIR IG is currently under development and can not be considered stable and ready for use. For questions and change requests regarding this IG, please create a ticket in [{{VersieInfo|BITS|release=V1.0.0|namespace=uz}} BITS].}}<br /> <br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide OBC version {{VersieInfo|OBC|release=V1.0.0|namespace=uz}}}}<br /> <br /> = Introduction =<br /> <br /> This implementation guide (IG) functions as the initial draft for the pilot phase of a new information standard, Outcome-Based Care (OBC, Dutch: Uitkomstgerichte zorg), version {{VersieInfo|OBC|release=V1.0.0}}. This IG is developed using [https://www.hl7.org/fhir/R4/ HL7 FHIR R4]. It assumes that the reader is familiar with both this version of FHIR and the functional specification [TO-ADD link]. This information standard is inspired by the international [http://hl7.org/fhir/us/sdc/index.html Structured Data Capture (SDC)] implementation guide and tries to follow it where possible.<br /> <br /> 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 Overarching principles and the use of FHIR packages. <br /> <br /> This IG first describes the boundaries and relationships in place, after which the implementation of PROMs in FHIR is described.<br /> <br /> = Boundaries and relationships =<br /> <br /> == Boundaries ==<br /> As mentioned in the introduction, this IG serves as a precursor for the pilot phase of the new information standard OBC. This version of the IG focuses solely on the manifestation of PROM questionnaires and their corresponding answers in FHIR. It does not include clinical data or use cases for data exchange, as the primary goal of the pilot is to evaluate the feasibility of implementing FHIR in this context. It is the intention to expand the scope in future versions of the IG to include clinical data and data exchange use cases, ultimately aiming to develop OBC into a comprehensive information standard.<br /> <br /> == FHIR resources and building blocks ==<br /> The PROM questionnaires and response data building blocks within OBC version {{VersieInfo|OBC|release=V1.0.0}} are not based on any publication of the Dutch Health and Care Information Models (Dutch: ‘zorginformatiebouwstenen’ or ‘zibs’), as there are no zibs that represent these building blocks. Therefore, there is no dependency on corresponding nl-core profiles, and mappings to zib concepts are not defined. Currently, there are no plans to create more general nl-core profiles, as no corresponding zibs exist. <br /> <br /> === Questionnaire ===<br /> <br /> Each PROM questionnaire is represented through a dedicated FHIR Questionnaire instance. A FHIR Questionnaire is a definitional artifact, which means it defines the questions to be asked, how these should be structured and rendered, and what answers are allowed. More information on structure and rendering of the FHIR Questionnaire instances can be found in [[#Rendering|section 2.4]]. The answer options to each question are represented through terminology resources using ValueSets and CodeSystems.<br /> <br /> The primary purpose of representing PROMs as Questionnaire instances is to establish a canonical identifier for each PROM in the form of a URI. This URI serves as a linkage point connecting every QuestionnaireResponse to their corresponding Questionnaire.<br /> <br /> The Questionnaire resource isn't strictly necessary to create a QuestionnaireResponse. However, using FHIR Questionnaire instances for PROMs provides significant benefits through standardized and structured formatting. Each question is included in the Questionnaire as a separate {{fhir|.item}} and has a unique identifier in the corresponding {{fhir|.item.linkId}} element. Additionally, the terminology used in PROMs is represented in FHIR ValueSet and CodeSystem resources and is correctly linked to the questions in the Questionnaire, ensuring all definitions are easily accessible for implementers.<br /> <br /> === QuestionnaireResponse ===<br /> <br /> The collection of outcomes and scores of a PROM is represented in a FHIR QuestionnaireResponse profile. For every completed PROM, an instance conforming to the [https://simplifier.net/nictiz-r4-outcomebasedcare/obcquestionnaireresponse obc-QuestionnaireResponse] profile is created. This profile features a structured set of answers with linked ids to the answered questions. The QuestionnaireResponse also includes the completion date and the language of the completed form.<br /> <br /> The QuestionnaireResponse contains enough information about the questions asked that it can be interpreted somewhat independently from the Questionnaire it is based on. In other words, no access to the Questionnaire is necessary in order to extract basic information from a QuestionnaireResponse.<br /> <br /> === Main building blocks ===<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ResponseData<br /> | Antwoordgegevens<br /> | QuestionnaireResponse<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse|nictiz.fhir.nl.r4.obc|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.obc|release=V1.0.0-beta.1|namespace=obc}}}}<br /> |}<br /> <br /> Note the following:<br /> * Each PROM questionnaire building block in the functional data set is represented by a separate Questionnaire instance. However, these are not listed here, but are instead added as [https://simplifier.net/nictiz-r4-outcomebasedcare//~resources?category=Example&amp;exampletype=Questionnaire MISSING instances] to the FHIR package.<br /> <br /> == Mappings between profiles and data set ==<br /> === Questionnaire instances ===<br /> <br /> Each instance of a FHIR Questionnaire contains the following elements:<br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Type<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Concept<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Mapping<br /> |-<br /> | uri<br /> | Questionnaire Coding system<br /> | Questionnaire.Coding.system<br /> |-<br /> | code<br /> | Questionnaire code<br /> | Questionnaire.Coding.code<br /> |-<br /> | string<br /> | Questionnaire code display<br /> | Questionnaire.Coding.display<br /> |-<br /> | string<br /> | Title of Questionnaire<br /> | Questionnaire.title<br /> |-<br /> | string<br /> | Publisher information<br /> | Questionnaire.publisher<br /> |-<br /> | string<br /> | Version of Questionnaire<br /> | Questionnaire.version<br /> |-<br /> | code<br /> | Language of Questionnaire<br /> | Questionnaire.meta.language<br /> |-<br /> | coding<br /> | Domain code of Questionnaire<br /> | Questionnaire.usageContext.code<br /> |-<br /> | any<br /> | Domain of Questionnaire<br /> | Questionnaire.usageContext.value<br /> |-<br /> | markdown (string)<br /> | License/Author information<br /> | Questionnaire.copyright<br /> |-<br /> | string<br /> | Instructions for a question or group of questions<br /> | Questionnaire.item.text<br /> |-<br /> | boolean<br /> | Read-only instructions for a question or group of questions<br /> | Questionnaire.item.readOnly<br /> |-<br /> | ??coding<br /> | Instruction format<br /> | Questionnaire.item.extension:renderingStyle??<br /> |-<br /> | string<br /> | Question<br /> | Questionnaire.item.text<br /> |-<br /> | code<br /> | Value type of question<br /> | Questionnaire.item.type<br /> |-<br /> | coding<br /> | Flag for sensitive questions<br /> | Questionnaire.item.linkId.extension:sensitivityFlag<br /> |-<br /> | ??coding<br /> | Question format<br /> | Questionnaire.item.extension:renderingStyle??<br /> |-<br /> | string<br /> | ??Score rating for questionnaire??<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Read-only score rating <br /> | Questionnaire.item.readOnly<br /> |-<br /> | boolean<br /> | Hidden score rating <br /> | Questionnaire.item.extension:hidden<br /> |-<br /> | string<br /> | Total score for questionnaire<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Hidden total score<br /> | Questionnaire.item.extension:hidden<br /> |-<br /> | string<br /> | Score calculation rules for questionnaire<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Read-only score calculation rules<br /> | Questionnaire.item.readOnly<br /> |-<br /> | boolean<br /> | Hidden score calculation rules<br /> | Questionnaire.item.extension:hidden<br /> |-<br /> | string<br /> | Interpretation score calculation rules for questionnaire<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Read-only interpretation score calculation rules<br /> | Questionnaire.item.readOnly<br /> |-<br /> | boolean<br /> | Hidden interpretation score calculation rules<br /> | Questionnaire.item.extension:hidden<br /> |}<br /> <br /> === QuestionnaireResponse profile ===<br /> The QuestionnaireResponse profile is connected to the functional definitions in ART-DECOR. It includes mappings to all data elements within the functional data set (prefixed with ‘obc-dataelement-10-').<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Type<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Id<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Concept<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Cardinality<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Profile<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Mapping<br /> |-<br /> | <br /> | 1405<br /> | Antwoordgegevens<br /> | 0 .. *<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse<br /> |-<br /> | Any??<br /> | 14??<br /> | Vraag<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.item??<br /> |-<br /> | Any<br /> | 1404<br /> | Antwoord<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.answer.value[x]<br /> |-<br /> | dateTime<br /> | 1406<br /> | InvulDatumTijd<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.authored<br /> |-<br /> | reference<br /> | 1407<br /> | Onderwerp<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.subject<br /> |-<br /> | reference<br /> | 1440<br /> | IngevuldeVragenlijst<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.questionnaire<br /> |-<br /> |}<br /> <br /> == Rendering ==<br /> A PROM questionnaire may take the form of a straightforward flat list of questions, but may also be hierarchically organized in groups and sub-groups including patient instructions. Likewise, it can contain a wide range of question types, varying from simple fill-out fields to multiple-choice questions, scales and questions with dependency's to previous answers. As a result, different styles can be rendered for particular items.<br /> <br /> The FHIR base Questionnaire resource offers limited rendering capabilities, with item labels and text elements displayed sequentially, and choice options provided through renderer-determined controls. For more control, the core specification defines additional elements and extensions, including the [https://build.fhir.org/ig/HL7/sdc/rendering.html rendering-style] extension. This extension allows the full capabilities of the HTML style attribute to be applied to items in a questionnaire, such as changing font or color, and adjusting font styles like bold, italics, or small caps. Conformant systems may ignore this extension unless the rendering-styleSensitive flag is set to true.<br /> <br /> The JSON snippet below is an example of a Questionnaire instance that contains the rendering-style extension to make the item partially bold.<br /> <br /> [INSERT SNIPPET]<br /> <br /> == Questionnaire versioning ==<br /> PROMs are subject to change over time, with alterations or additions made to their questions and answer options, as well as to the underlying algorithm used to calculate the scores. Any changes made to these PROMs are recorded and disseminated through ?Amigo?. To accurately analyse PSOM (PROMs Standard Operating Model) data, it is crucial to determine which version of the PROM was filled out by the subject. This can be done by matching the PROM version with the Amigo reference number.<br /> <br /> In FHIR, the version of a PROMs can be registered in the {{fhir|Questionnaire.version element}}. A Questionnaire is referenced from other resources by its [https://www.hl7.org/fhir/r4/references.html#canonical canonical URL]. To reference a particular version of a Questionnaire, users must combine the canonical URL and version using a pipe character in the format: [canonicalURL]|[version]. When users refer to a Questionnaire with just the {{fhir|.url}}, they automatically refer to the latest version.<br /> <br /> However, the definition of 'latest version' may vary for Amigo compared to what the PROMs provider may consider latest. Therefore, to ensure clarity about which version of the PROMs is requested and collected, any references in the {{fhir|QuestionnaireResponse.questionnaire}} SHALL always include a specific version.<br /> <br /> To note:<br /> *The assumption is that all PROMs will be registered with a version number.<br /> *Amigo will be responsible for assigning version numbers to ensure these reflect a consistent standard approach for the organisation.<br /> <br /> == Sensitive questions ==<br /> <br /> Every PROM may include sensitive questions, indicating that the answers might contain sensitive information. As a result, a specific level of authorization is required to read these answers.<br /> <br /> The Data Segmentation for Privacy project defined the Inline Security Label extension. This extension enables flagging elements with a security label, for example indicating their sensitivity, and SHALL be added to all relevant {{fhir|.item}} elements as {{fhir|.item.linkId.extension:sensitivityFlag}} in both the Questionnaire and QuestionnaireResponse instances. The {{fhir|.valueCoding}} SHALL be populated with the code PDS from the InformationSensitivityPolicy ValueSet to indicate this data item contains sensitive information reported by the patient.<br /> <br /> == Scores and calculation rules ==<br /> The Questionnaire definition includes information on how to calculate the total score, the weight for each question, and how to interpret the total score. Currently, this information is provided in {{fhir|.item}} elements, where the calculation rules are read-only instructions and hidden from users completing the forms through an extension.<br /> <br /> In the next version of the Questionnaire definition, the plan is to incorporate dynamic calculation rules using structured data capture, making the Questionnaire more structured and flexible.</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=uz:V1.0.0-alpha.1_FHIR_OBC&diff=223683 2024-08-05T06:08:12Z

<p>Luud Slagter: /* FHIR resources and building blocks */</p> <hr /> <div>{{Vdraft/InformationBox|This FHIR IG is currently under development and can not be considered stable and ready for use. For questions and change requests regarding this IG, please create a ticket in [{{VersieInfo|BITS|release=V1.0.0|namespace=uz}} BITS].}}<br /> <br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide OBC version {{VersieInfo|OBC|release=V1.0.0|namespace=uz}}}}<br /> <br /> = Introduction =<br /> <br /> This implementation guide (IG) functions as the initial draft for the pilot phase of a new information standard, Outcome-Based Care (OBC, Dutch: Uitkomstgerichte zorg), version {{VersieInfo|OBC|release=V1.0.0}}. This IG is developed using [https://www.hl7.org/fhir/R4/ HL7 FHIR R4]. It assumes that the reader is familiar with both this version of FHIR and the functional specification [TO-ADD link]. This information standard is inspired by the international [http://hl7.org/fhir/us/sdc/index.html Structured Data Capture (SDC)] implementation guide and tries to follow it where possible.<br /> <br /> 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 Overarching principles and the use of FHIR packages. <br /> <br /> This IG first describes the boundaries and relationships in place, after which the implementation of PROMs in FHIR is described.<br /> <br /> = Boundaries and relationships =<br /> <br /> == Boundaries ==<br /> As mentioned in the introduction, this IG serves as a precursor for the pilot phase of the new information standard OBC. This version of the IG focuses solely on the manifestation of PROM questionnaires and their corresponding answers in FHIR. It does not include clinical data or use cases for data exchange, as the primary goal of the pilot is to evaluate the feasibility of implementing FHIR in this context. It is the intention to expand the scope in future versions of the IG to include clinical data and data exchange use cases, ultimately aiming to develop OBC into a comprehensive information standard.<br /> <br /> == FHIR resources and building blocks ==<br /> The PROM questionnaires and response data building blocks within OBC version {{VersieInfo|OBC|release=V1.0.0}} are not based on any publication of the Dutch Health and Care Information Models (Dutch: ‘zorginformatiebouwstenen’ or ‘zibs’), as there are no zibs that represent these building blocks. Therefore, there is no dependency on corresponding nl-core profiles, and mappings to zib concepts are not defined. Currently, there are no plans to create more general nl-core profiles, as no corresponding zibs exist. <br /> <br /> === Questionnaire ===<br /> <br /> Each PROM questionnaire is represented through a dedicated FHIR Questionnaire instance. A FHIR Questionnaire is a definitional artifact, which means it defines the questions to be asked, how these should be structured and rendered, and what answers are allowed. More information on structure and rendering of the FHIR Questionnaire instances can be found in [[#Rendering|section 2.4]]. The answer options to each question are represented through terminology resources using ValueSets and CodeSystems.<br /> <br /> The primary purpose of representing PROMs as Questionnaire instances is to establish a canonical identifier for each PROM in the form of a URI. This URI serves as a linkage point connecting every QuestionnaireResponse to their corresponding Questionnaire.<br /> <br /> The Questionnaire resource isn't strictly necessary to create a QuestionnaireResponse. However, using FHIR Questionnaire instances for PROMs provides significant benefits through standardized and structured formatting. Each question is included in the Questionnaire as a separate {{fhir|.item}} and has a unique identifier in the corresponding {{fhir|.item.linkId}} element. Additionally, the terminology used in PROMs is represented in FHIR ValueSet and CodeSystem resources and is correctly linked to the questions in the Questionnaire, ensuring all definitions are easily accessible for implementers.<br /> <br /> === QuestionnaireResponse ===<br /> <br /> The collection of outcomes and scores of a PROM is represented in a FHIR QuestionnaireResponse profile. For every completed PROM, an instance conforming to the [https://simplifier.net/nictiz-r4-outcomebasedcare/obcquestionnaireresponse obc-QuestionnaireResponse] profile is created. This profile features a structured set of answers with linked ids to the answered questions. The QuestionnaireResponse also includes the completion date and the language of the completed form.<br /> <br /> The QuestionnaireResponse contains enough information about the questions asked that it can be interpreted somewhat independently from the Questionnaire it is based on. In other words, no access to the Questionnaire is necessary in order to extract basic information from a QuestionnaireResponse.<br /> <br /> === Main building blocks ===<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ResponseData<br /> | Antwoordgegevens<br /> | QuestionnaireResponse<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse|nictiz.fhir.nl.r4.obc|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.obc|release=V1.0.0-beta.1|namespace=obc}}}}<br /> |}<br /> <br /> Note the following:<br /> * Each PROM questionnaire building block in the functional data set is represented by a separate Questionnaire instance. However, these are not listed here, but are instead added as [https://simplifier.net/nictiz-r4-outcomebasedcare//~resources?category=Example&amp;exampletype=Questionnaire MISSING instances] to the FHIR package.<br /> <br /> == Mappings between profiles and data set ==<br /> === Questionnaire instance ===<br /> <br /> Each instance of a FHIR Questionnaire contains the following elements:<br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Type<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Concept<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Mapping<br /> |-<br /> | uri<br /> | Questionnaire Coding system<br /> | Questionnaire.Coding.system<br /> |-<br /> | code<br /> | Questionnaire code<br /> | Questionnaire.Coding.code<br /> |-<br /> | string<br /> | Questionnaire code display<br /> | Questionnaire.Coding.display<br /> |-<br /> | string<br /> | Title of Questionnaire<br /> | Questionnaire.title<br /> |-<br /> | string<br /> | Publisher information<br /> | Questionnaire.publisher<br /> |-<br /> | string<br /> | Version of Questionnaire<br /> | Questionnaire.version<br /> |-<br /> | code<br /> | Language of Questionnaire<br /> | Questionnaire.meta.language<br /> |-<br /> | coding<br /> | Domain code of Questionnaire<br /> | Questionnaire.usageContext.code<br /> |-<br /> | any<br /> | Domain of Questionnaire<br /> | Questionnaire.usageContext.value<br /> |-<br /> | markdown (string)<br /> | License/Author information<br /> | Questionnaire.copyright<br /> |-<br /> | string<br /> | Instructions for a question or group of questions<br /> | Questionnaire.item.text<br /> |-<br /> | boolean<br /> | Read-only instructions for a question or group of questions<br /> | Questionnaire.item.readOnly<br /> |-<br /> | ??coding<br /> | Instruction format<br /> | Questionnaire.item.extension:renderingStyle??<br /> |-<br /> | string<br /> | Question<br /> | Questionnaire.item.text<br /> |-<br /> | code<br /> | Value type of question<br /> | Questionnaire.item.type<br /> |-<br /> | coding<br /> | Flag for sensitive questions<br /> | Questionnaire.item.linkId.extension:sensitivityFlag<br /> |-<br /> | ??coding<br /> | Question format<br /> | Questionnaire.item.extension:renderingStyle??<br /> |-<br /> | string<br /> | ??Score rating for questionnaire??<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Read-only score rating <br /> | Questionnaire.item.readOnly<br /> |-<br /> | boolean<br /> | Hidden score rating <br /> | Questionnaire.item.extension:hidden<br /> |-<br /> | string<br /> | Total score for questionnaire<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Hidden total score<br /> | Questionnaire.item.extension:hidden<br /> |-<br /> | string<br /> | Score calculation rules for questionnaire<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Read-only score calculation rules<br /> | Questionnaire.item.readOnly<br /> |-<br /> | boolean<br /> | Hidden score calculation rules<br /> | Questionnaire.item.extension:hidden<br /> |-<br /> | string<br /> | Interpretation score calculation rules for questionnaire<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Read-only interpretation score calculation rules<br /> | Questionnaire.item.readOnly<br /> |-<br /> | boolean<br /> | Hidden interpretation score calculation rules<br /> | Questionnaire.item.extension:hidden<br /> |}<br /> <br /> === QuestionnaireResponse profile ===<br /> The QuestionnaireResponse profile is connected to the functional definitions in ART-DECOR. It includes mappings to all data elements within the functional data set (prefixed with ‘obc-dataelement-10-').<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Type<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Id<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Concept<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Cardinality<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Profile<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Mapping<br /> |-<br /> | <br /> | 1405<br /> | Antwoordgegevens<br /> | 0 .. *<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse<br /> |-<br /> | Any??<br /> | 14??<br /> | Vraag<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.item??<br /> |-<br /> | Any<br /> | 1404<br /> | Antwoord<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.answer.value[x]<br /> |-<br /> | dateTime<br /> | 1406<br /> | InvulDatumTijd<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.authored<br /> |-<br /> | reference<br /> | 1407<br /> | Onderwerp<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.subject<br /> |-<br /> | reference<br /> | 1440<br /> | IngevuldeVragenlijst<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.questionnaire<br /> |-<br /> |}<br /> <br /> == Rendering ==<br /> A PROM questionnaire may take the form of a straightforward flat list of questions, but may also be hierarchically organized in groups and sub-groups including patient instructions. Likewise, it can contain a wide range of question types, varying from simple fill-out fields to multiple-choice questions, scales and questions with dependency's to previous answers. As a result, different styles can be rendered for particular items.<br /> <br /> The FHIR base Questionnaire resource offers limited rendering capabilities, with item labels and text elements displayed sequentially, and choice options provided through renderer-determined controls. For more control, the core specification defines additional elements and extensions, including the [https://build.fhir.org/ig/HL7/sdc/rendering.html rendering-style] extension. This extension allows the full capabilities of the HTML style attribute to be applied to items in a questionnaire, such as changing font or color, and adjusting font styles like bold, italics, or small caps. Conformant systems may ignore this extension unless the rendering-styleSensitive flag is set to true.<br /> <br /> The JSON snippet below is an example of a Questionnaire instance that contains the rendering-style extension to make the item partially bold.<br /> <br /> [INSERT SNIPPET]<br /> <br /> == Questionnaire versioning ==<br /> PROMs are subject to change over time, with alterations or additions made to their questions and answer options, as well as to the underlying algorithm used to calculate the scores. Any changes made to these PROMs are recorded and disseminated through ?Amigo?. To accurately analyse PSOM (PROMs Standard Operating Model) data, it is crucial to determine which version of the PROM was filled out by the subject. This can be done by matching the PROM version with the Amigo reference number.<br /> <br /> In FHIR, the version of a PROMs can be registered in the {{fhir|Questionnaire.version element}}. A Questionnaire is referenced from other resources by its [https://www.hl7.org/fhir/r4/references.html#canonical canonical URL]. To reference a particular version of a Questionnaire, users must combine the canonical URL and version using a pipe character in the format: [canonicalURL]|[version]. When users refer to a Questionnaire with just the {{fhir|.url}}, they automatically refer to the latest version.<br /> <br /> However, the definition of 'latest version' may vary for Amigo compared to what the PROMs provider may consider latest. Therefore, to ensure clarity about which version of the PROMs is requested and collected, any references in the {{fhir|QuestionnaireResponse.questionnaire}} SHALL always include a specific version.<br /> <br /> To note:<br /> *The assumption is that all PROMs will be registered with a version number.<br /> *Amigo will be responsible for assigning version numbers to ensure these reflect a consistent standard approach for the organisation.<br /> <br /> == Sensitive questions ==<br /> <br /> Every PROM may include sensitive questions, indicating that the answers might contain sensitive information. As a result, a specific level of authorization is required to read these answers.<br /> <br /> The Data Segmentation for Privacy project defined the Inline Security Label extension. This extension enables flagging elements with a security label, for example indicating their sensitivity, and SHALL be added to all relevant {{fhir|.item}} elements as {{fhir|.item.linkId.extension:sensitivityFlag}} in both the Questionnaire and QuestionnaireResponse instances. The {{fhir|.valueCoding}} SHALL be populated with the code PDS from the InformationSensitivityPolicy ValueSet to indicate this data item contains sensitive information reported by the patient.<br /> <br /> == Scores and calculation rules ==<br /> The Questionnaire definition includes information on how to calculate the total score, the weight for each question, and how to interpret the total score. Currently, this information is provided in {{fhir|.item}} elements, where the calculation rules are read-only instructions and hidden from users completing the forms through an extension.<br /> <br /> In the next version of the Questionnaire definition, the plan is to incorporate dynamic calculation rules using structured data capture, making the Questionnaire more structured and flexible.</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=uz:V1.0.0-alpha.1_FHIR_OBC&diff=223682 2024-08-05T05:42:35Z

<p>Luud Slagter: /* Boundaries */</p> <hr /> <div>{{Vdraft/InformationBox|This FHIR IG is currently under development and can not be considered stable and ready for use. For questions and change requests regarding this IG, please create a ticket in [{{VersieInfo|BITS|release=V1.0.0|namespace=uz}} BITS].}}<br /> <br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide OBC version {{VersieInfo|OBC|release=V1.0.0|namespace=uz}}}}<br /> <br /> = Introduction =<br /> <br /> This implementation guide (IG) functions as the initial draft for the pilot phase of a new information standard, Outcome-Based Care (OBC, Dutch: Uitkomstgerichte zorg), version {{VersieInfo|OBC|release=V1.0.0}}. This IG is developed using [https://www.hl7.org/fhir/R4/ HL7 FHIR R4]. It assumes that the reader is familiar with both this version of FHIR and the functional specification [TO-ADD link]. This information standard is inspired by the international [http://hl7.org/fhir/us/sdc/index.html Structured Data Capture (SDC)] implementation guide and tries to follow it where possible.<br /> <br /> 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 Overarching principles and the use of FHIR packages. <br /> <br /> This IG first describes the boundaries and relationships in place, after which the implementation of PROMs in FHIR is described.<br /> <br /> = Boundaries and relationships =<br /> <br /> == Boundaries ==<br /> As mentioned in the introduction, this IG serves as a precursor for the pilot phase of the new information standard OBC. This version of the IG focuses solely on the manifestation of PROM questionnaires and their corresponding answers in FHIR. It does not include clinical data or use cases for data exchange, as the primary goal of the pilot is to evaluate the feasibility of implementing FHIR in this context. It is the intention to expand the scope in future versions of the IG to include clinical data and data exchange use cases, ultimately aiming to develop OBC into a comprehensive information standard.<br /> <br /> == FHIR resources and building blocks ==<br /> The PROM questionnaires and response data building block within the OBC pilot version {{VersieInfo|OBC|release=V1.0.0}} is not based on any publication of the Dutch Health and Care Information Models (Dutch: ‘zorginformatiebouwstenen’ or ‘zibs’), as there are no zibs that represent the building blocks included in the pilot. Therefore, there is no dependency on corresponding nl-core profiles, and mappings to zib concepts are not defined. Currently, there are no plans to create more general nl-core profiles, as no corresponding zibs exist. <br /> <br /> === Questionnaire ===<br /> <br /> Within the scope of the OBC pilot, each PROM questionnaire is represented through a dedicated FHIR Questionnaire instance. A FHIR Questionnaire is a definitional artifact, meaning it defines the questions to be asked, how these should be structured and rendered and what answers are allowed. More information on structure and rendering of the FHIR Questionnaire instances can be found in [[#Rendering|section 2.4]]. The answer options to each question are represented through terminology resources using ValueSets and CodeSystems.<br /> <br /> The primary purpose of representing PROMSs as Questionnaire instances is to establish a canonical identifier for each PROM in the form of a URI. This URI serves as a linkage point connecting QuestionnaireResponses to their corresponding Questionnaires.<br /> <br /> The Questionnaire resource isn't strictly necessary to create a QuestionnaireResponse. However, using FHIR Questionnaire instances for PROMs provides significant benefits through standardized and structured formatting. Each question is included in the Questionnaire and uniquely identified in the {{fhir|.item.linkId}} elements. Additionally, the terminology used in PROMs is represented in FHIR ValueSet and CodeSystem resources and is correctly linked to the questions in the Questionnaire, ensuring all definitions are easily accessible for programmers.<br /> <br /> === QuestionnaireResponse ===<br /> <br /> The collection of outcomes and scores of PROMs is represented in a FHIR QuestionnaireResponse profile. For every completed PROM, an instance conforming to the [https://simplifier.net/nictiz-r4-outcomebasedcare/obcquestionnaireresponse obc-QuestionnaireResponse] profile is created. This profile features a structured set of answers with linked ids to the answered questions. The QuestionnaireResponse also includes the completion date and the language of the completed form.<br /> <br /> The QuestionnaireResponse contains enough information about the questions asked that it can be interpreted somewhat independently from the Questionnaire it is based on. In other words, you don't need access to the Questionnaire to extract basic information from a QuestionnaireResponse.<br /> <br /> === Main building blocks ===<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | Responsedata<br /> | Antwoordgegevens<br /> | QuestionnaireResponse<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse|nictiz.fhir.nl.r4.obc|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.obc|release=V1.0.0-beta.1|namespace=obc}}}}<br /> |}<br /> <br /> Note the following:<br /> * Each Questionnaire profile is represented by a unique questionnaire and is not included as a building block or subsequent resource. Instead, the FHIR Questionnaire instances included in the pilot are added as [https://simplifier.net/nictiz-r4-outcomebasedcare//~resources?category=Example&amp;exampletype=Questionnaire MISSING instances] to the FHIR package.<br /> <br /> == Mappings between profiles and data set ==<br /> === Questionnaire instance ===<br /> <br /> Each instance of a FHIR Questionnaire contains the following elements:<br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Type<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Concept<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Mapping<br /> |-<br /> | uri<br /> | Questionnaire Coding system<br /> | Questionnaire.Coding.system<br /> |-<br /> | code<br /> | Questionnaire code<br /> | Questionnaire.Coding.code<br /> |-<br /> | string<br /> | Questionnaire code display<br /> | Questionnaire.Coding.display<br /> |-<br /> | string<br /> | Title of Questionnaire<br /> | Questionnaire.title<br /> |-<br /> | string<br /> | Publisher information<br /> | Questionnaire.publisher<br /> |-<br /> | string<br /> | Version of Questionnaire<br /> | Questionnaire.version<br /> |-<br /> | code<br /> | Language of Questionnaire<br /> | Questionnaire.meta.language<br /> |-<br /> | coding<br /> | Domain code of Questionnaire<br /> | Questionnaire.usageContext.code<br /> |-<br /> | any<br /> | Domain of Questionnaire<br /> | Questionnaire.usageContext.value<br /> |-<br /> | markdown (string)<br /> | License/Author information<br /> | Questionnaire.copyright<br /> |-<br /> | string<br /> | Instructions for a question or group of questions<br /> | Questionnaire.item.text<br /> |-<br /> | boolean<br /> | Read-only instructions for a question or group of questions<br /> | Questionnaire.item.readOnly<br /> |-<br /> | ??coding<br /> | Instruction format<br /> | Questionnaire.item.extension:renderingStyle??<br /> |-<br /> | string<br /> | Question<br /> | Questionnaire.item.text<br /> |-<br /> | code<br /> | Value type of question<br /> | Questionnaire.item.type<br /> |-<br /> | coding<br /> | Flag for sensitive questions<br /> | Questionnaire.item.linkId.extension:sensitivityFlag<br /> |-<br /> | ??coding<br /> | Question format<br /> | Questionnaire.item.extension:renderingStyle??<br /> |-<br /> | string<br /> | ??Score rating for questionnaire??<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Read-only score rating <br /> | Questionnaire.item.readOnly<br /> |-<br /> | boolean<br /> | Hidden score rating <br /> | Questionnaire.item.extension:hidden<br /> |-<br /> | string<br /> | Total score for questionnaire<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Hidden total score<br /> | Questionnaire.item.extension:hidden<br /> |-<br /> | string<br /> | Score calculation rules for questionnaire<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Read-only score calculation rules<br /> | Questionnaire.item.readOnly<br /> |-<br /> | boolean<br /> | Hidden score calculation rules<br /> | Questionnaire.item.extension:hidden<br /> |-<br /> | string<br /> | Interpretation score calculation rules for questionnaire<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Read-only interpretation score calculation rules<br /> | Questionnaire.item.readOnly<br /> |-<br /> | boolean<br /> | Hidden interpretation score calculation rules<br /> | Questionnaire.item.extension:hidden<br /> |}<br /> <br /> === QuestionnaireResponse profile ===<br /> The QuestionnaireResponse profile is connected to the functional definitions in ART-DECOR. It includes mappings to all data elements within the functional data set (prefixed with ‘obc-dataelement-10-').<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Type<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Id<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Concept<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Cardinality<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Profile<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Mapping<br /> |-<br /> | <br /> | 1405<br /> | Antwoordgegevens<br /> | 0 .. *<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse<br /> |-<br /> | Any??<br /> | 14??<br /> | Vraag<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.item??<br /> |-<br /> | Any<br /> | 1404<br /> | Antwoord<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.answer.value[x]<br /> |-<br /> | dateTime<br /> | 1406<br /> | InvulDatumTijd<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.authored<br /> |-<br /> | reference<br /> | 1407<br /> | Onderwerp<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.subject<br /> |-<br /> | reference<br /> | 1440<br /> | IngevuldeVragenlijst<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.questionnaire<br /> |-<br /> |}<br /> <br /> == Rendering ==<br /> A PROM questionnaire may take the form of a straightforward flat list of questions, but may also be hierarchically organized in groups and sub-groups including patient instructions. Likewise, it can contain a wide range of question types, varying from simple fill-out fields to multiple-choice questions, scales and questions with dependency's to previous answers. As a result, different styles can be rendered for particular items.<br /> <br /> The FHIR base Questionnaire resource offers limited rendering capabilities, with item labels and text elements displayed sequentially, and choice options provided through renderer-determined controls. For more control, the core specification defines additional elements and extensions, including the [https://build.fhir.org/ig/HL7/sdc/rendering.html rendering-style] extension. This extension allows the full capabilities of the HTML style attribute to be applied to items in a questionnaire, such as changing font or color, and adjusting font styles like bold, italics, or small caps. Conformant systems may ignore this extension unless the rendering-styleSensitive flag is set to true.<br /> <br /> The JSON snippet below is an example of a Questionnaire instance that contains the rendering-style extension to make the item partially bold.<br /> <br /> [INSERT SNIPPET]<br /> <br /> == Questionnaire versioning ==<br /> PROMs are subject to change over time, with alterations or additions made to their questions and answer options, as well as to the underlying algorithm used to calculate the scores. Any changes made to these PROMs are recorded and disseminated through ?Amigo?. To accurately analyse PSOM (PROMs Standard Operating Model) data, it is crucial to determine which version of the PROM was filled out by the subject. This can be done by matching the PROM version with the Amigo reference number.<br /> <br /> In FHIR, the version of a PROMs can be registered in the {{fhir|Questionnaire.version element}}. A Questionnaire is referenced from other resources by its [https://www.hl7.org/fhir/r4/references.html#canonical canonical URL]. To reference a particular version of a Questionnaire, users must combine the canonical URL and version using a pipe character in the format: [canonicalURL]|[version]. When users refer to a Questionnaire with just the {{fhir|.url}}, they automatically refer to the latest version.<br /> <br /> However, the definition of 'latest version' may vary for Amigo compared to what the PROMs provider may consider latest. Therefore, to ensure clarity about which version of the PROMs is requested and collected, any references in the {{fhir|QuestionnaireResponse.questionnaire}} SHALL always include a specific version.<br /> <br /> To note:<br /> *The assumption is that all PROMs will be registered with a version number.<br /> *Amigo will be responsible for assigning version numbers to ensure these reflect a consistent standard approach for the organisation.<br /> <br /> == Sensitive questions ==<br /> <br /> Every PROM may include sensitive questions, indicating that the answers might contain sensitive information. As a result, a specific level of authorization is required to read these answers.<br /> <br /> The Data Segmentation for Privacy project defined the Inline Security Label extension. This extension enables flagging elements with a security label, for example indicating their sensitivity, and SHALL be added to all relevant {{fhir|.item}} elements as {{fhir|.item.linkId.extension:sensitivityFlag}} in both the Questionnaire and QuestionnaireResponse instances. The {{fhir|.valueCoding}} SHALL be populated with the code PDS from the InformationSensitivityPolicy ValueSet to indicate this data item contains sensitive information reported by the patient.<br /> <br /> == Scores and calculation rules ==<br /> The Questionnaire definition includes information on how to calculate the total score, the weight for each question, and how to interpret the total score. Currently, this information is provided in {{fhir|.item}} elements, where the calculation rules are read-only instructions and hidden from users completing the forms through an extension.<br /> <br /> In the next version of the Questionnaire definition, the plan is to incorporate dynamic calculation rules using structured data capture, making the Questionnaire more structured and flexible.</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=uz:V1.0.0-alpha.1_FHIR_OBC&diff=223681 2024-08-05T05:40:33Z

<p>Luud Slagter: /* Introduction */</p> <hr /> <div>{{Vdraft/InformationBox|This FHIR IG is currently under development and can not be considered stable and ready for use. For questions and change requests regarding this IG, please create a ticket in [{{VersieInfo|BITS|release=V1.0.0|namespace=uz}} BITS].}}<br /> <br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide OBC version {{VersieInfo|OBC|release=V1.0.0|namespace=uz}}}}<br /> <br /> = Introduction =<br /> <br /> This implementation guide (IG) functions as the initial draft for the pilot phase of a new information standard, Outcome-Based Care (OBC, Dutch: Uitkomstgerichte zorg), version {{VersieInfo|OBC|release=V1.0.0}}. This IG is developed using [https://www.hl7.org/fhir/R4/ HL7 FHIR R4]. It assumes that the reader is familiar with both this version of FHIR and the functional specification [TO-ADD link]. This information standard is inspired by the international [http://hl7.org/fhir/us/sdc/index.html Structured Data Capture (SDC)] implementation guide and tries to follow it where possible.<br /> <br /> 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 Overarching principles and the use of FHIR packages. <br /> <br /> This IG first describes the boundaries and relationships in place, after which the implementation of PROMs in FHIR is described.<br /> <br /> = Boundaries and relationships =<br /> <br /> == Boundaries ==<br /> As mentioned in the introduction, this IG serves as a precursor for the pilot phase of the new information standard OBC. This version of the IG focuses solely on the manifestation of PROM questionnaires and their corresponding answers in FHIR. It does not include clinical data or use cases for data exchange, as the primary goal of the pilot is to evaluate the feasibility of implementing FHIR in this context. The plan is to expand the scope in future versions of the IG to include clinical data and data exchange use cases, ultimately aiming to develop OBC into a comprehensive information standard.<br /> <br /> == FHIR resources and building blocks ==<br /> The PROM questionnaires and response data building block within the OBC pilot version {{VersieInfo|OBC|release=V1.0.0}} is not based on any publication of the Dutch Health and Care Information Models (Dutch: ‘zorginformatiebouwstenen’ or ‘zibs’), as there are no zibs that represent the building blocks included in the pilot. Therefore, there is no dependency on corresponding nl-core profiles, and mappings to zib concepts are not defined. Currently, there are no plans to create more general nl-core profiles, as no corresponding zibs exist. <br /> <br /> === Questionnaire ===<br /> <br /> Within the scope of the OBC pilot, each PROM questionnaire is represented through a dedicated FHIR Questionnaire instance. A FHIR Questionnaire is a definitional artifact, meaning it defines the questions to be asked, how these should be structured and rendered and what answers are allowed. More information on structure and rendering of the FHIR Questionnaire instances can be found in [[#Rendering|section 2.4]]. The answer options to each question are represented through terminology resources using ValueSets and CodeSystems.<br /> <br /> The primary purpose of representing PROMSs as Questionnaire instances is to establish a canonical identifier for each PROM in the form of a URI. This URI serves as a linkage point connecting QuestionnaireResponses to their corresponding Questionnaires.<br /> <br /> The Questionnaire resource isn't strictly necessary to create a QuestionnaireResponse. However, using FHIR Questionnaire instances for PROMs provides significant benefits through standardized and structured formatting. Each question is included in the Questionnaire and uniquely identified in the {{fhir|.item.linkId}} elements. Additionally, the terminology used in PROMs is represented in FHIR ValueSet and CodeSystem resources and is correctly linked to the questions in the Questionnaire, ensuring all definitions are easily accessible for programmers.<br /> <br /> === QuestionnaireResponse ===<br /> <br /> The collection of outcomes and scores of PROMs is represented in a FHIR QuestionnaireResponse profile. For every completed PROM, an instance conforming to the [https://simplifier.net/nictiz-r4-outcomebasedcare/obcquestionnaireresponse obc-QuestionnaireResponse] profile is created. This profile features a structured set of answers with linked ids to the answered questions. The QuestionnaireResponse also includes the completion date and the language of the completed form.<br /> <br /> The QuestionnaireResponse contains enough information about the questions asked that it can be interpreted somewhat independently from the Questionnaire it is based on. In other words, you don't need access to the Questionnaire to extract basic information from a QuestionnaireResponse.<br /> <br /> === Main building blocks ===<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | Responsedata<br /> | Antwoordgegevens<br /> | QuestionnaireResponse<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse|nictiz.fhir.nl.r4.obc|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.obc|release=V1.0.0-beta.1|namespace=obc}}}}<br /> |}<br /> <br /> Note the following:<br /> * Each Questionnaire profile is represented by a unique questionnaire and is not included as a building block or subsequent resource. Instead, the FHIR Questionnaire instances included in the pilot are added as [https://simplifier.net/nictiz-r4-outcomebasedcare//~resources?category=Example&amp;exampletype=Questionnaire MISSING instances] to the FHIR package.<br /> <br /> == Mappings between profiles and data set ==<br /> === Questionnaire instance ===<br /> <br /> Each instance of a FHIR Questionnaire contains the following elements:<br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Type<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Concept<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Mapping<br /> |-<br /> | uri<br /> | Questionnaire Coding system<br /> | Questionnaire.Coding.system<br /> |-<br /> | code<br /> | Questionnaire code<br /> | Questionnaire.Coding.code<br /> |-<br /> | string<br /> | Questionnaire code display<br /> | Questionnaire.Coding.display<br /> |-<br /> | string<br /> | Title of Questionnaire<br /> | Questionnaire.title<br /> |-<br /> | string<br /> | Publisher information<br /> | Questionnaire.publisher<br /> |-<br /> | string<br /> | Version of Questionnaire<br /> | Questionnaire.version<br /> |-<br /> | code<br /> | Language of Questionnaire<br /> | Questionnaire.meta.language<br /> |-<br /> | coding<br /> | Domain code of Questionnaire<br /> | Questionnaire.usageContext.code<br /> |-<br /> | any<br /> | Domain of Questionnaire<br /> | Questionnaire.usageContext.value<br /> |-<br /> | markdown (string)<br /> | License/Author information<br /> | Questionnaire.copyright<br /> |-<br /> | string<br /> | Instructions for a question or group of questions<br /> | Questionnaire.item.text<br /> |-<br /> | boolean<br /> | Read-only instructions for a question or group of questions<br /> | Questionnaire.item.readOnly<br /> |-<br /> | ??coding<br /> | Instruction format<br /> | Questionnaire.item.extension:renderingStyle??<br /> |-<br /> | string<br /> | Question<br /> | Questionnaire.item.text<br /> |-<br /> | code<br /> | Value type of question<br /> | Questionnaire.item.type<br /> |-<br /> | coding<br /> | Flag for sensitive questions<br /> | Questionnaire.item.linkId.extension:sensitivityFlag<br /> |-<br /> | ??coding<br /> | Question format<br /> | Questionnaire.item.extension:renderingStyle??<br /> |-<br /> | string<br /> | ??Score rating for questionnaire??<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Read-only score rating <br /> | Questionnaire.item.readOnly<br /> |-<br /> | boolean<br /> | Hidden score rating <br /> | Questionnaire.item.extension:hidden<br /> |-<br /> | string<br /> | Total score for questionnaire<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Hidden total score<br /> | Questionnaire.item.extension:hidden<br /> |-<br /> | string<br /> | Score calculation rules for questionnaire<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Read-only score calculation rules<br /> | Questionnaire.item.readOnly<br /> |-<br /> | boolean<br /> | Hidden score calculation rules<br /> | Questionnaire.item.extension:hidden<br /> |-<br /> | string<br /> | Interpretation score calculation rules for questionnaire<br /> | Questionnaire.item<br /> |-<br /> | boolean<br /> | Read-only interpretation score calculation rules<br /> | Questionnaire.item.readOnly<br /> |-<br /> | boolean<br /> | Hidden interpretation score calculation rules<br /> | Questionnaire.item.extension:hidden<br /> |}<br /> <br /> === QuestionnaireResponse profile ===<br /> The QuestionnaireResponse profile is connected to the functional definitions in ART-DECOR. It includes mappings to all data elements within the functional data set (prefixed with ‘obc-dataelement-10-').<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Type<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Id<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Concept<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Cardinality<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Profile<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Mapping<br /> |-<br /> | <br /> | 1405<br /> | Antwoordgegevens<br /> | 0 .. *<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse<br /> |-<br /> | Any??<br /> | 14??<br /> | Vraag<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.item??<br /> |-<br /> | Any<br /> | 1404<br /> | Antwoord<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.answer.value[x]<br /> |-<br /> | dateTime<br /> | 1406<br /> | InvulDatumTijd<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.authored<br /> |-<br /> | reference<br /> | 1407<br /> | Onderwerp<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.subject<br /> |-<br /> | reference<br /> | 1440<br /> | IngevuldeVragenlijst<br /> | 0 .. 1<br /> | [http://nictiz.nl/fhir/StructureDefinition/obc-QuestionnaireResponse obc-QuestionnaireResponse]<br /> | QuestionnaireResponse.questionnaire<br /> |-<br /> |}<br /> <br /> == Rendering ==<br /> A PROM questionnaire may take the form of a straightforward flat list of questions, but may also be hierarchically organized in groups and sub-groups including patient instructions. Likewise, it can contain a wide range of question types, varying from simple fill-out fields to multiple-choice questions, scales and questions with dependency's to previous answers. As a result, different styles can be rendered for particular items.<br /> <br /> The FHIR base Questionnaire resource offers limited rendering capabilities, with item labels and text elements displayed sequentially, and choice options provided through renderer-determined controls. For more control, the core specification defines additional elements and extensions, including the [https://build.fhir.org/ig/HL7/sdc/rendering.html rendering-style] extension. This extension allows the full capabilities of the HTML style attribute to be applied to items in a questionnaire, such as changing font or color, and adjusting font styles like bold, italics, or small caps. Conformant systems may ignore this extension unless the rendering-styleSensitive flag is set to true.<br /> <br /> The JSON snippet below is an example of a Questionnaire instance that contains the rendering-style extension to make the item partially bold.<br /> <br /> [INSERT SNIPPET]<br /> <br /> == Questionnaire versioning ==<br /> PROMs are subject to change over time, with alterations or additions made to their questions and answer options, as well as to the underlying algorithm used to calculate the scores. Any changes made to these PROMs are recorded and disseminated through ?Amigo?. To accurately analyse PSOM (PROMs Standard Operating Model) data, it is crucial to determine which version of the PROM was filled out by the subject. This can be done by matching the PROM version with the Amigo reference number.<br /> <br /> In FHIR, the version of a PROMs can be registered in the {{fhir|Questionnaire.version element}}. A Questionnaire is referenced from other resources by its [https://www.hl7.org/fhir/r4/references.html#canonical canonical URL]. To reference a particular version of a Questionnaire, users must combine the canonical URL and version using a pipe character in the format: [canonicalURL]|[version]. When users refer to a Questionnaire with just the {{fhir|.url}}, they automatically refer to the latest version.<br /> <br /> However, the definition of 'latest version' may vary for Amigo compared to what the PROMs provider may consider latest. Therefore, to ensure clarity about which version of the PROMs is requested and collected, any references in the {{fhir|QuestionnaireResponse.questionnaire}} SHALL always include a specific version.<br /> <br /> To note:<br /> *The assumption is that all PROMs will be registered with a version number.<br /> *Amigo will be responsible for assigning version numbers to ensure these reflect a consistent standard approach for the organisation.<br /> <br /> == Sensitive questions ==<br /> <br /> Every PROM may include sensitive questions, indicating that the answers might contain sensitive information. As a result, a specific level of authorization is required to read these answers.<br /> <br /> The Data Segmentation for Privacy project defined the Inline Security Label extension. This extension enables flagging elements with a security label, for example indicating their sensitivity, and SHALL be added to all relevant {{fhir|.item}} elements as {{fhir|.item.linkId.extension:sensitivityFlag}} in both the Questionnaire and QuestionnaireResponse instances. The {{fhir|.valueCoding}} SHALL be populated with the code PDS from the InformationSensitivityPolicy ValueSet to indicate this data item contains sensitive information reported by the patient.<br /> <br /> == Scores and calculation rules ==<br /> The Questionnaire definition includes information on how to calculate the total score, the weight for each question, and how to interpret the total score. Currently, this information is provided in {{fhir|.item}} elements, where the calculation rules are read-only instructions and hidden from users completing the forms through an extension.<br /> <br /> In the next version of the Questionnaire definition, the plan is to incorporate dynamic calculation rules using structured data capture, making the Questionnaire more structured and flexible.</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=uz:Landingspagina_Uitkomstgerichte_Zorg&diff=223680 2024-08-05T05:36:35Z

<p>Luud Slagter: </p> <hr /> <div>{{DISPLAYTITLE: Landingspagina Contra-indicaties en Overgevoeligheden}}<br /> <br /> Het Programma &quot;Uitkomstgerichte Zorg&quot; is een landelijk initiatief om de kwaliteit en efficiëntie van de gezondheidszorg in Nederland te verbeteren. Het programma heeft twee doelen:<br /> <br /> * Het bevorderen van gezamenlijke besluitvorming op basis van uitkomstinformatie. Dit kan bijdragen aan het verbeteren van de kwaliteit van leven voor de patiënt.<br /> * Het leveren van kwaliteitszorg en het verhogen van de werktevredenheid voor de zorgprofessional.<br /> <br /> Het programma betrekt verschillende belanghebbenden, zoals patiënten, zorgverleners, verzekeraars en onderzoekers, die samenwerken om uitkomstmaten, dataverzamelingsmethoden en best practices te ontwikkelen en te implementeren. Daarnaast bestrijkt het programma verschillende domeinen van de gezondheidszorg, zoals chronische ziekten, oncologie, verloskunde en geestelijke gezondheid. Door zich te richten op de uitkomsten die het belangrijkst zijn voor patiënten en professionals, streeft het programma naar een meer patiëntgerichte, waardegedreven en duurzame gezondheidszorg in Nederland. Voor elke zorgdomein zijn de belangrijkste uitkomstmaten gedefinieerd. Daarnaast zijn er methodes en instrumenten ontwikkeld voor het meten en rapporteren van de uitkomstmaten. [Rol van Nictiz]<br /> <br /> <br /> ==Ondersteunende informatie en handleidingen==<br /> <br /> ===Actueel===<br /> <br /> ==Ontwerpen==<br /> <br /> ===Actueel===<br /> *[[uz:V1.0.0_FHIR_OBC|FHIR Implementation Guide Outcome-Based Care 1.0.0 (ENG)]]<br /> <br /> ===Vorige versies===<br /> <br /> ==Release notes==</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=cio:V2.0.0-beta.3_FHIR_CiO&diff=223280 2024-07-24T09:07:55Z

<p>Luud Slagter: Initial version of technical design for beta.3</p> <hr /> <div>{{Vdraft/InformationBox|This FHIR IG is currently under development and can not be considered stable and ready for use. For questions and change requests regarding this IG, please create a ticket in [{{VersieInfo|BITS|release=V2.0.0-beta.3|namespace=cio}} BITS].}}<br /> <br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide CiO version {{VersieInfo|CiO|release=V2.0.0-beta.3|namespace=cio}}}}<br /> <br /> [[Bestand:Icoon Nictiz Cirkel Informatiestandaard Contra-indicaties en Overgevoeligheden (2).svg|link=|100px|CiO|rechts]] <br /> <br /> &lt;div class=&quot;toclimit-3&quot;&gt;__TOC__&lt;/div&gt;<br /> <br /> = Introduction =<br /> <br /> This is the implementation guide (IG) for the information standard CiO (Dutch: Contra-indicaties en overgevoeligheden, English: Contraindications and hypersensitivities), version {{VersieInfo|CiO|release=V2.0.0-beta.3}}. The functional specification can be found [[cio:V2.0.0-beta.2_Ontwerp_CiO|here]] and is implemented using [https://www.hl7.org/fhir/R4/ HL7 FHIR R4]. This implementation guide assumes that the reader is familiar with both the functional specification and this version of FHIR.<br /> <br /> 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 Overarching principles and the use of FHIR packages. Where the general IG uses the term ‘use case’, this IG uses the term ‘transaction’ for the various processes that are described.<br /> <br /> This IG first describes the boundaries and relationships in place, after which the implementation is described per transaction.<br /> <br /> = Boundaries and relationships =<br /> <br /> == Boundaries ==<br /> <br /> Note that this version of the CiO information standard is only focused on medication contraindications and hypersensitivities due to medication (see [[cio:V2.0.0-beta.2_Ontwerp_CiO#Algemeen|section 1.1 of the functional specification]]). Technically this scope is reflected in for instance the terminology used within the FHIR profiles or the naming of the cio-MedicationContraIndication profile. In this IG however, we will not further elaborate on this narrower scope and instead describe the technical implementation of this standard as general as possible, in order to make it easier to incorporate a broadening of the scope in subsequent versions of this IG.<br /> <br /> == Building blocks and profiles ==<br /> <br /> The exchange of data within the CiO standard version {{VersieInfo|CiO|release=V2.0.0-beta.3}} is partly based on the 2020 publication of the Dutch Health and Care Information Models (Dutch: ‘zorginformatiebouwstenen’ or ‘zibs’), and subsequent changes made that will be present in the 2024 prepublication. In particular, the prepublication of 2021 saw the introduction of the Hypersensitivity and Reaction zibs which are based on and still have quite some overlap with the zib AllergyIntolerance that already existed. In the prepublication of 2024 the zibs Hypersensitivity and Reaction have been overhauled in such a way that they only contain ‘diagnostic’ elements. The concepts within these zibs that were related to surveillance with respect to substances have been removed, resulting in a new zib SurveillanceDecision. Moreover, the zib Alert has changed in this prepublication such that the zib MedicationContraIndication has become superfluous, by adding a new AlertType reserved for medication contraindications. The functional data set of CiO has further built upon these four zibs, and the resulting objects (which are actually exchanged) are referred to as ‘building blocks’ in the data set, and can thus be seen as ‘extended zibs’ suitable for implementation.<br /> <br /> Due to new insights, the building blocks Hypersensitivity and Reaction in the functional data set have deviated quite a lot from the zib AllergyIntolerance present in the 2020 publication, making them incompatible in varying degrees from a technical point of view. Therefore it was not possible to implement the FHIR profiles for these 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 the nl-core profiles, meaning that they are not derived from nl-core-AllergyIntolerance. Similarly, for the building block MedicationContraIndication it was not possible to derive its profile from the nl-core-Alert profile corresponding to zib publication 2020, due to incompatible changes introduced in the zib Alert in the prepublication of 2024. Lastly, the zib SurveillanceDecision is newly introduced, so obviously no derivation from nl-core profiles is possible.<br /> <br /> In a subsequent version of the information standard, it is the intention to base the profiles for all building blocks on their respective nl-core profiles based on zib publication 2024. There are however some considerations to be taken into account, since it is only possible to use these nl-core profiles provided:<br /> * the underlying zibs are still part of the 2024 publication;<br /> * no incompatible changes will be added on the relevant zibs between the prepublication and publication of 2024;<br /> * they are defined in FHIR R4 (otherwise the cio profiles would also need to be converted to another FHIR version).<br /> <br /> It is important to note that there is still extensive discussion about the exact scope and content of the CiO building blocks, meaning that the current profiles definitely cannot be considered to be stable and ready for use. A list of discussion topics with regards to the technical implementation can be found in [[#Discussion|section 2.5]].<br /> <br /> {{NoteBoxNictizR4Package|p1=nictiz.fhir.nl.r4.cio|v1={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.3|namespace=cio}}|p2=nictiz.fhir.nl.r4.nl-core|v2={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> <br /> Note that the package versioning does not follow the versioning of the information standard, as CiO version 2.0.0 was the first release of the CiO information standard based on FHIR R4. This means that CiO version 2.0.0-beta.x makes use of version 1.0.0-beta.x of the nictiz.fhir.nl.r4.cio FHIR package.<br /> <br /> === Main building blocks ===<br /> <br /> As described above, the main building blocks have no dependency on any zib counterparts of the 2020 publication, resulting in so-called ‘cio’ profiles.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationContraIndication<br /> | MedicatieContraIndicatie<br /> | Flag<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-MedicationContraIndication|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | SurveillanceDecision<br /> | BewakingBesluit<br /> | Flag<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-SurveillanceDecision|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | Hypersensitivity<br /> | Overgevoeligheid<br /> | AllergyIntolerance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Hypersensitivity|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | Reaction<br /> | Reactie<br /> | AllergyIntolerance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Reaction|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | Condition<br /> | Aandoening<br /> | Condition<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Condition|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | RegistrationData<br /> | RegistratieGegevens<br /> | Provenance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-RegistrationData|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |}<br /> <br /> The last two building blocks in the above table have a special status:<br /> * Condition is not a separate building block within the CiO data set, and the cio-Condition profile actually contains mappings to concepts within the Hypersensitivity and Reaction building blocks that relate to the underlying condition and diagnosis. Thus, in order to convey the complete Hypersensitivity or Reaction building block, it is necessary to use an instance conforming to the cio-Hypersensitivity or cio-Reaction profile, together with an instance conforming to the cio-Condition profile.<br /> * The RegistrationData building block is part of every other main building block in the data set, containing data that relates to the registering process instead of the medical concept itself. Such data is often not (completely) mappable within the profiles corresponding to the medical concept. Hence, whenever another main building block is exchanged, it is represented by its own profile in conjunction with an instance of the cio-RegistrationData profile. In the future, if more information standards will make use of the Provenance resource to represent the administrative concepts present in RegistrationData, it is intended to create an nl-core-RegistrationData profile that replaces the cio-RegistrationData profile.<br /> <br /> === Secondary building blocks ===<br /> <br /> Additionally, the standard uses several secondary building blocks referenced from the main building blocks. All secondary building blocks are part of the [[FHIR:V1.0_FHIR_IG_R4#Functional_definitions|‘nl-core’]] package.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | ContactPerson<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |}<br /> <br /> Note the following:<br /> * Each occurrence of the zib HealthProfessional is normally represented by '''two''' FHIR resources: an instance of nl-core-HealthProfessional-PractitionerRole and an instance of nl-core-HealthProfessional-Practitioner. Sending systems should only fill the reference to the PractitionerRole instance where relevant. Receiving systems can resolve the reference to the Practitioner resource from that PractitionerRole instance.<br /> * The zib HealthcareProvider is mapped to both a Location and Organization profile. In general the Location profile acts as the focal resource, because most references to this zib are concerned about the recording of the physical location where the care to patient takes place rather than the organizational information. However, within the CiO information standard, the HealthcareProvider is only referenced indirectly via the PractitionerRole resource, hence a reference to the Organization profile is sufficient in those cases. The Location profile is mentioned in the table above for completeness purposes.<br /> <br /> === Relations between building blocks ===<br /> <br /> [[Bestand:Resources diagram CiO (beta.2).drawio.png|1000px]]<br /> <br /> == Mappings between profiles and data set ==<br /> <br /> Each transaction starts with links to the functional definition in an ART-DECOR publication and references one or several FHIR profiles. The FHIR profiles contain mappings to all data elements that are present in the functional data set (prefixed with ‘cio-dataelement-20-’).<br /> <br /> 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}} or {{fhir|.patient}} of each FHIR instance of each main building block (with the exception of RegistrationData).<br /> <br /> 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 Identifier, for example RelationHypersensitivity (cio-dataelement-20-734) in building block Hypersensitivity. 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]].<br /> <br /> == Patient identification ==<br /> <br /> This implementation guide assumes that the client system is able to make a connection to the right server that contains the patient's information. It does not provide information on finding the right server nor does it provide information about security. Moreover, each transaction is performed in the context of a specific patient, whose context might have been established using the authentication mechanisms described in external specifications such as the MedMij ‘Afsprakenstelsel’ or through the usage of search parameters for patient identification. <br /> <br /> Each server is required to perform filtering based on the patient associated with the context for the request or based on the patient identification search parameters, which is a [https://www.hl7.org/fhir/r4/search.html#chaining chained search parameter] for all resource types except Patient, so only the records associated with the authenticated patient are returned.<br /> <br /> When patient identification requires the use of search parameters, the following search parameters SHALL be supported:<br /> * Patient: {{fhir|identifier}}<br /> * Flag: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> <br /> An example of a request that retrieves all Flag resources of a patient with a fake BSN of 111222333:<br /> <br /> &lt;pre&gt;GET [base]/Flag?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> <br /> Most request examples in this IG do not include patient identification mechanisms. Requesters are assumed to include these if necessary.<br /> <br /> == Discussion ==<br /> <br /> As stated before, the current profiles cannot be considered to be stable and ready for use. This is partly due to the ongoing discussion about the exact scope and content of the functional building blocks in CiO. However, there are also some topics regarding the technical implementation that need to be addressed before considering the resulting FHIR profiles to be ready for use:<br /> <br /> * The functional data set defines several relations between different building blocks (concepts with a name starting with ‘Relation…’), which have been implemented in FHIR as custom extensions of data type ‘Reference’. Some of these refer to instances of the same building block and are meant to track updates done between different instances of the same building block. In that sense the approach of the Medication Process information standard is followed here, where such relations are used for building blocks that are changed or stopped. In FHIR however it is possible to just update existing resources resulting in a new version of the same instance, and therefore it is up for debate whether this approach is deemed necessary and desirable for the CiO use cases. In particular one might wonder whether this approach is justified for Flag resources, since this resource has a different nature than for instance medication-related resources. The conclusion on this topic also depends on the way object identification and mutations will be handled on a functional level within the CiO information standard. This has not been fully thought out yet and will be taken into consideration for the 2.0.0-beta.3 release.<br /> * This is the first release of an information standard making use of the Provenance resource to represent the concepts present within the zib RegistrationData (instead of defining additional extensions for concepts like RegistrationDateTime and InformationSource). The exact use of this resource on a broader level needs to be further analyzed (and generalized).<br /> * Several concepts within the Hypersensitivity and Reaction building blocks that are related to the underlying condition and diagnosis have been mapped to elements within a separate Condition profile, instead of adding them as extensions within the AllergyIntolerance profiles. It needs to be discussed whether this approach is feasible (also taking into account international standards) and whether this Condition resource has a ‘right’ to exist. Moreover, the Hypersensitivity and Reaction building blocks are modeled by different AllergyIntolerance profiles, as they are both representing diagnostic insight of a health professional regarding (the predisposition to develop) a reaction, while in core FHIR the relation between a hypersensitivity and reactions due to that hypersensitivity are modeled within one AllergyIntolerance. This discrepancy might result in difficulties when exchanging information on hypersensitivities and reactions on a broader/international scale. Both modeling approaches mentioned here need to be taken into account while deciding on the definitive modeling of the aforementioned building blocks.<br /> * The exact requirements regarding the search parameters used within CiO aren't fully fledged yet, especially the {{fhir|_revinclude}} defined on {{fhir|Provenance.target}}, and the possible requirement of an {{fhir|_include}} on the contents of the {{fhir|flag-detail}} extension (the latter being out of scope for this release). Note that in general, references are required to be either resolvable or readily available in the search request results; since the reference between the Provenance resource and other resources is reversed with respect to the focal resource of the search requests, supporting the {{fhir|_revinclude}} on {{fhir|Provenance.target}} is required. Further discussion with software suppliers is necessary to finalize these requirements.<br /> <br /> = Transactions =<br /> <br /> This section describes the FHIR implementation of all transactions listed in [[cio:V2.0.0-beta.2_Ontwerp_CiO#Usecases|section 2 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’.<br /> <br /> == Medication Contraindication (Retrieve/Serve) ==<br /> <br /> The retrieve medication contraindications transaction is used by the client to retrieve medication contraindications from a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Transaction group<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Transaction<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Actor<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| System role<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| FHIR CapabilityStatement<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/sc-2.16.840.1.113883.2.4.3.11.60.26.3.2-2019-08-28T133341.html#_2.16.840.1.113883.2.4.3.11.60.26.4.16_20200622101830 MedicationContraIndication (PULL)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/tr-2.16.840.1.113883.2.4.3.11.60.26.4.17-2020-06-22T101830.html Retrieving medication contraindications]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|CIO-MCIR<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/cio-MedicationContraindications.RetrieveServe|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.3|namespace=cio}}|title=CapabilityStatement Retrieve/serve medication contraindications}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/tr-2.16.840.1.113883.2.4.3.11.60.26.4.18-2020-06-22T101830.html Serving medication contraindications]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|CIO-MCIB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> <br /> When a health professional or healthcare provider wants to obtain all medication contraindications or specific ones matching various parameters, they issue a retrieve medication contraindications request message. This message uses the HTTP GET method parameterized query against the server's FHIR Flag endpoint.<br /> <br /> The search interaction is performed by an HTTP GET conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query.<br /> <br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|350241000146102&amp;_revinclude=Provenance:target{&amp;[additional parameter(s)]}&lt;/pre&gt;<br /> <br /> ==== Search parameters ====<br /> <br /> All search parameters listed in the table below SHALL be supported for processing by servers and MAY be supported by clients, with the exception of the {{fhir|category}} parameter, as well as the {{fhir|&lt;nowiki&gt;_revinclude=Provenance:target&lt;/nowiki&gt;}} search result parameter, which SHALL be supported by clients as well (as these are always part of the search query in this transaction).<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | CiO search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Description<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Example<br /> |-<br /> | -<br /> | Search on MedicationContraIndication building blocks (not taking into account the RegistrationData building block). <br /> | {{fhir|category}} &lt;ref name=&quot;custom-searchparameter&quot;&gt;The search parameter consists of a custom FHIR search parameter not represented in the FHIR specification.&lt;/ref&gt;<br /> | Flag<br /> | Retrieves all Flag resources representing a MedicationContraIndication.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|350241000146102&lt;/pre&gt;<br /> |-<br /> | -<br /> | Include the RegistrationData building block referenced from the MedicationContraIndication.<br /> | {{fhir|&lt;nowiki&gt;_revinclude=Provenance:target&lt;/nowiki&gt;}}<br /> | Flag<br /> | Retrieves all Flag and corresponding Provenance resources representing a MedicationContraIndication.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|350241000146102&amp;_revinclude=Provenance:target&lt;/pre&gt;<br /> |-<br /> | PatientIdentificationNumber<br /> | Search on patient.<br /> | {{fhir|patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;&gt;This search parameter only needs to be supported when patient identification requires the use of search parameters, see [[#Patient_identification|section 2.4]].&lt;/ref&gt;<br /> | Flag<br /> | Retrieves all MedicationContraIndication building blocks of a patient with a fake BSN of 111222333.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|350241000146102&amp;patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&amp;_revinclude=Provenance:target&lt;/pre&gt;<br /> |-<br /> | ReferenceDate<br /> | Search on the MedicationContraIndication building blocks that were active on or after a certain date.<br /> | {{fhir|date}}<br /> | Flag<br /> | Retrieves all MedicationContraIndication building blocks that were active from 01-05-2023.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|350241000146102&amp;date=ge2023-05-01&amp;_revinclude=Provenance:target&lt;/pre&gt;<br /> |-<br /> | -<br /> | The client may request that the server returns resources related to the search results, in order to reduce the overall network delay of repeated retrievals of related resources.<br /> Supporting the include of the Patient resource referenced by building blocks is required. Others (PractitionerRole, Practitioner, RelatedPerson, Organization) are optional. However: all resources referenced per literal reference SHALL be resolvable [[FHIR:V1.0_FHIR_IG_R4#Including_referenced_resources|per the Nictiz IG]].<br /> | {{fhir|&lt;nowiki&gt;_include=Flag:patient&lt;/nowiki&gt;}}<br /> | Flag<br /> | Retrieves all MedicationContraIndication building blocks of a patient with a fake BSN of 111222333 and includes the Patient resource in the search results.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|350241000146102&amp;patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&amp;_revinclude=Provenance:target&amp;_include=Flag:patient&lt;/pre&gt;<br /> |}<br /> <br /> The following custom search parameter is defined for this transaction:<br /> <br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/Flag-category|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> <br /> === Serve (response message) ===<br /> <br /> The server returns an HTTP Status code appropriate to the processing outcome and returns a Bundle, with {{fhir|Bundle.type}} = {{term|searchset}}, including the resources matching the search query. The resources included in the Bundle SHALL conform to the profiles listed in the ‘List of profiles’ below.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationContraIndication<br /> | MedicatieContraIndicatie<br /> | Flag<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-MedicationContraIndication|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | RegistrationData<br /> | RegistratieGegevens<br /> | Provenance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-RegistrationData|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | HealthcareProvider<br /> | Zorgaanbieder<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | ContactPerson<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |}<br /> <br /> == Medication Contraindication (Send/Receive) ==<br /> <br /> The send medication contraindications transaction is used by the client to send medication contraindications to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Transaction group<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Transaction<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Actor<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| System role<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| FHIR CapabilityStatement<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/sc-2.16.840.1.113883.2.4.3.11.60.26.3.2-2019-08-28T133341.html#_2.16.840.1.113883.2.4.3.11.60.26.4.10_20200622101711 MedicationContraIndication (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/tr-2.16.840.1.113883.2.4.3.11.60.26.4.11-2020-06-22T101711.html Sending medication contraindications]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|CIO-MCIS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/cio-MedicationContraIndications.SendReceive|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.3|namespace=cio}}|title=CapabilityStatement Send/receive medication contraindications}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication contraindications<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|CIO-MCIO<br /> |}<br /> <br /> === Send (request message) ===<br /> <br /> Because the data sent in this transaction potentially consists of several building blocks along with secondary resources, a [https://www.hl7.org/fhir/r4/http.html#transaction {{term|transaction}} interaction] is used. This allows for sending a Bundle with a set of resources in a single interaction and makes it possible to [[FHIR:V1.0_FHIR_IG_R4#Including_.22secondary.22_resources_when_sending_information|include referenced secondary resources]] if needed. The interaction is performed by an HTTP POST command as shown:<br /> <br /> &lt;pre&gt;POST [base]&lt;/pre&gt;<br /> <br /> The body of the POST submission is a Bundle with {{fhir|Bundle.type}} = {{term|transaction}}. Each entry SHALL carry request details ({{fhir|Bundle.entry.request}}) that provide the HTTP method of the action to be executed. Usually, this will be POST, even for informative secondary resources.<br /> <br /> The resources included in the Bundle SHALL conform to the profiles listed in the ‘List of profiles’ below.<br /> <br /> === Receive (response message) ===<br /> <br /> The server returns an HTTP Status code appropriate to the processing outcome. If the transaction is successful, the server returns a Bundle with {{fhir|Bundle.type}} = {{term|transaction-response}}, that contains one entry for each entry in the request, in the same order, with the outcome of processing the entry. Included secondary resources are handled [[FHIR:V1.0_FHIR_IG_R4#Including_.22secondary.22_resources_when_sending_information|following the Nictiz IG]].<br /> <br /> If the transaction fails, the server returns an OperationOutcome with one or multiple {{fhir|.issue}} elements filled with information, as detailed as possible, that describes why the transaction failed and which resource and/or request caused this.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationContraIndication<br /> | MedicatieContraIndicatie<br /> | Flag<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-MedicationContraIndication|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | RegistrationData<br /> | RegistratieGegevens<br /> | Provenance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-RegistrationData|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | HealthcareProvider<br /> | Zorgaanbieder<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | ContactPerson<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |}<br /> <br /> == Medication Hypersensitivity (Retrieve/Serve) ==<br /> <br /> The retrieve medication hypersensitivities transaction is used by the client to retrieve medication hypersensitivities from a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Transaction group<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Transaction<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Actor<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| System role<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| FHIR CapabilityStatement<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/sc-2.16.840.1.113883.2.4.3.11.60.26.3.2-2019-08-28T133341.html#_2.16.840.1.113883.2.4.3.11.60.26.4.34_20201021150632 MedicationHypersensitivity (PULL)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/tr-2.16.840.1.113883.2.4.3.11.60.26.4.35-2020-10-21T150632.html Retrieving medication hypersensitivities]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|CIO-GOR<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/cio-MedicationHypersensitivities.RetrieveServe|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.3|namespace=cio}}|title=CapabilityStatement Retrieve/serve medication hypersensitivities}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/tr-2.16.840.1.113883.2.4.3.11.60.26.4.36-2020-10-21T150632.html Serving medication hypersensitivities]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|CIO-GOB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> <br /> When a health professional or healthcare provider wants to obtain all medication hypersensitivities or specific ones matching various parameters, they issue a retrieve medication hypersensitivities request message. This message uses the HTTP GET method parameterized query against the server's FHIR Flag endpoint.<br /> <br /> The search interaction is performed by an HTTP GET conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query.<br /> <br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|225419007&amp;_revinclude=Provenance:target{&amp;[additional parameter(s)]}&lt;/pre&gt;<br /> <br /> References within the {{fhir|flag-detail}} extension (in the Flag resources present in the search result) to instances conforming to the cio-Hypersensitivity or cio-Reaction profiles can be resolved afterwards by individual read operations. The same holds true for instances conforming to the cio-Condition profile referenced from {{fhir|Provenance.target}}.<br /> <br /> ==== Search parameters ====<br /> <br /> All search parameters listed in the table below SHALL be supported for processing by servers and MAY be supported by clients, with the exception of the {{fhir|category}} parameter, as well as the {{fhir|&lt;nowiki&gt;_revinclude=Provenance:target&lt;/nowiki&gt;}} search result parameter, which SHALL be supported by clients as well (as these are always part of the search query in this transaction).<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | CiO search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Description<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Example<br /> |-<br /> | -<br /> | Search on SurveillanceDecision building blocks (not taking into account the RegistrationData building block). <br /> | {{fhir|category}} &lt;ref name=&quot;custom-searchparameter&quot;&gt;The search parameter consists of a custom FHIR search parameter not represented in the FHIR specification.&lt;/ref&gt;<br /> | Flag<br /> | Retrieves all Flag resources representing a SurveillanceDecision.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|225419007&lt;/pre&gt;<br /> |-<br /> | -<br /> | Include the RegistrationData building block referenced from the SurveillanceDecision.<br /> | {{fhir|&lt;nowiki&gt;_revinclude=Provenance:target&lt;/nowiki&gt;}}<br /> | Flag<br /> | Retrieves all Flag and corresponding Provenance resources representing a SurveillanceDecision.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|225419007&amp;_revinclude=Provenance:target&lt;/pre&gt;<br /> |-<br /> | PatientIdentificationNumber<br /> | Search on patient.<br /> | {{fhir|patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;&gt;This search parameter only needs to be supported when patient identification requires the use of search parameters, see [[#Patient_identification|section 2.4]].&lt;/ref&gt;<br /> | Flag<br /> | Retrieves all SurveillanceDecision building blocks of a patient with a fake BSN of 111222333.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|225419007&amp;patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&amp;_revinclude=Provenance:target&lt;/pre&gt;<br /> |-<br /> | ReferenceDate<br /> | Search on the SurveillanceDecision building blocks that were active on or after a certain date.<br /> | {{fhir|date}}<br /> | Flag<br /> | Retrieves all SurveillanceDecision building blocks that were active from 01-05-2023.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|225419007&amp;date=ge2023-05-01&amp;_revinclude=Provenance:target&lt;/pre&gt;<br /> |-<br /> | -<br /> | The client may request that the server returns resources related to the search results, in order to reduce the overall network delay of repeated retrievals of related resources.<br /> References to AllergyIntolerance and Condition resources are resolved by individual read operations, as mentioned above. Supporting the include of the Patient resource referenced by building blocks is required. Others (PractitionerRole, Practitioner, RelatedPerson, Organization) are optional. However: all resources referenced per literal reference SHALL be resolvable [[FHIR:V1.0_FHIR_IG_R4#Including_referenced_resources|per the Nictiz IG]].<br /> | {{fhir|&lt;nowiki&gt;_include=Flag:patient&lt;/nowiki&gt;}}<br /> | Flag<br /> | Retrieves all SurveillanceDecision building blocks of a patient with a fake BSN of 111222333 and includes the Patient resource in the search results.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|225419007&amp;patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&amp;_revinclude=Provenance:target&amp;_include=Flag:patient&lt;/pre&gt;<br /> |}<br /> <br /> The following custom search parameter is defined for this transaction:<br /> <br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/Flag-category|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> <br /> === Serve (response message) ===<br /> <br /> The server returns an HTTP Status code appropriate to the processing outcome and returns a Bundle, with {{fhir|Bundle.type}} = {{term|searchset}}, including the resources matching the search query. The resources included in the Bundle SHALL conform to the profiles listed in the ‘List of profiles’ below.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | SurveillanceDecision<br /> | BewakingBesluit<br /> | Flag<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-SurveillanceDecision|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | Hypersensitivity<br /> | Overgevoeligheid<br /> | AllergyIntolerance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Hypersensitivity|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | Reaction<br /> | Reactie<br /> | AllergyIntolerance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Reaction|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | Condition<br /> | Aandoening<br /> | Condition<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Condition|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | RegistrationData<br /> | RegistratieGegevens<br /> | Provenance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-RegistrationData|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | HealthcareProvider<br /> | Zorgaanbieder<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | ContactPerson<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |}<br /> <br /> == Medication Hypersensitivity (Send/Receive) ==<br /> <br /> The send medication hypersensitivities transaction is used by the client to send medication hypersensitivities to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Transaction group<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Transaction<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Actor<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| System role<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| FHIR CapabilityStatement<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/sc-2.16.840.1.113883.2.4.3.11.60.26.3.2-2019-08-28T133341.html#_2.16.840.1.113883.2.4.3.11.60.26.4.31_20201021150608 MedicationHypersensitivity (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/tr-2.16.840.1.113883.2.4.3.11.60.26.4.32-2020-10-21T150608.html Sending medication hypersensitivities ]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|CIO-GOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/cio-MedicationHypersensitivities.SendReceive|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.3|namespace=cio}}|title=CapabilityStatement Send/receive medication hypersensitivities }}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication hypersensitivities <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|CIO-GOO<br /> |}<br /> <br /> === Send (request message) ===<br /> <br /> Because the data sent in this transaction potentially consists of several building blocks along with secondary resources, a [https://www.hl7.org/fhir/r4/http.html#transaction {{term|transaction}} interaction] is used. This allows for sending a Bundle with a set of resources in a single interaction and makes it possible to [[FHIR:V1.0_FHIR_IG_R4#Including_.22secondary.22_resources_when_sending_information|include referenced secondary resources]] if needed. The interaction is performed by an HTTP POST command as shown:<br /> <br /> &lt;pre&gt;POST [base]&lt;/pre&gt;<br /> <br /> The body of the POST submission is a Bundle with {{fhir|Bundle.type}} = {{term|transaction}}. Each entry SHALL carry request details ({{fhir|Bundle.entry.request}}) that provide the HTTP method of the action to be executed. Usually, this will be POST, even for informative secondary resources.<br /> <br /> The resources included in the Bundle SHALL conform to the profiles listed in the ‘List of profiles’ below.<br /> <br /> === Receive (response message) ===<br /> <br /> The server returns an HTTP Status code appropriate to the processing outcome. If the transaction is successful, the server returns a Bundle with {{fhir|Bundle.type}} = {{term|transaction-response}}, that contains one entry for each entry in the request, in the same order, with the outcome of processing the entry. Included secondary resources are handled [[FHIR:V1.0_FHIR_IG_R4#Including_.22secondary.22_resources_when_sending_information|following the Nictiz IG]].<br /> <br /> If the transaction fails, the server returns an OperationOutcome with one or multiple {{fhir|.issue}} elements filled with information, as detailed as possible, that describes why the transaction failed and which resource and/or request caused this.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | SurveillanceDecision<br /> | BewakingBesluit<br /> | Flag<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-SurveillanceDecision|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | Hypersensitivity<br /> | Overgevoeligheid<br /> | AllergyIntolerance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Hypersensitivity|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | Reaction<br /> | Reactie<br /> | AllergyIntolerance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Reaction|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | Condition<br /> | Aandoening<br /> | Condition<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Condition|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | RegistrationData<br /> | RegistratieGegevens<br /> | Provenance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-RegistrationData|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | HealthcareProvider<br /> | Zorgaanbieder<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |-<br /> | ContactPerson<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.3|namespace=cio}}}}<br /> |}<br /> <br /> = Release notes =<br /> <br /> Release notes can be found on the [[cio:V2.0.0-beta.2_Ontwerp_CiO#Release_Notes| functional design page]].<br /> <br /> = Footnotes =</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=Sjabloon:VersieInfo&diff=223278 2024-07-24T09:00:42Z

<p>Luud Slagter: Updated 2.0.0-beta.3 for CiO</p> <hr /> <div>{{#switch: {{{namespace|{{NAMESPACE}}}}}:{{{release|{{ROOTPAGENAME}}}}}<br /> <br /> | MedMij:V2019.01 = {{#switch: {{{1}}}<br /> | BgZ = 2.2.2<br /> | Laboratoriumresultaten = 1.2.2<br /> | Medicatieproces = 9.0.7<br /> | MedicatieprocesVerstrekkingenvertaling = 9.A.1<br /> | AllergieIntolerantie1 = 1.2.2<br /> | AllergieIntolerantie = 2.1.2<br /> | AllergieIntolerantieVertaling = 1.A.15<br /> | eAfspraak = 1.2.2<br /> | Zelfmetingen = 1.3.2<br /> | PDFA = 2.1.2<br /> | PDFA1 = 1.3.2<br /> | Huisartsgegevens = 1.2.2<br /> | BgGGZ = 1.2.2<br /> | BgLZ = 1.1.2<br /> | Beelden = 1.1.2<br /> | Vragenlijsten = 1.1.2<br /> | package = 1.3.19<br /> | nictiz.fhir.nl.stu3.zib2017 = 1.3.19<br /> | Editie = 2019.01<br /> }}<br /> <br /> | MedMij:V2020.01 = {{#switch: {{{1}}}<br /> | BgZ = 3.1.20<br /> | Laboratoriumresultaten = 2.0.37<br /> | Medicatieproces = 9.0.7<br /> | MedicatieprocesVerstrekkingenvertaling = 9.A.1<br /> | AllergieIntolerantie1 = 2.0.37<br /> | AllergieIntolerantie = 3.0.37<br /> | AllergieIntolerantieVertaling = 2.A.14<br /> | eAfspraak = 2.0.37<br /> | Zelfmetingen = 2.0.37<br /> | PDFA = 3.0.39<br /> | PDFA1 = 3.0.39<br /> | Huisartsgegevens = 2.0.38<br /> | BgGGZ = 2.0.38<br /> | BgLZ = 2.0.24<br /> | Beelden = 2.0.37<br /> | Vragenlijsten = 2.0.39<br /> | Vragenlijsten1 = 1.0.39<br /> | Geboortezorg = 1.0.4<br /> | package = 2.2.18<br /> | nictiz.fhir.nl.stu3.zib2017 = 2.2.18<br /> | nictiz.fhir.nl.stu3.eafspraak = 1.0.6<br /> | nictiz.fhir.nl.stu3.images = 1.0.3<br /> | nictiz.fhir.nl.stu3.questionnaires = 2.0.8<br /> | nictiz.fhir.nl.stu3.bgz = 1.1.1<br /> | Editie = 2020.01<br /> }}<br /> <br /> | MedMij:V2020.02 = {{#switch: {{{1}}}<br /> | BgLZ = 3.1.18<br /> | package = 2.2.18<br /> | nictiz.fhir.nl.stu3.zib2017 = 2.2.18<br /> | Editie = 2020.02<br /> }}<br /> <br /> | MedMij:V6 = {{#switch: {{{1}}}<br /> | Dossierwijzigingsverzoek = 1.0.15<br /> | Vaccinatie-Immunisatie = 1.0.13<br /> | MedMij_FHIR_IG_R4 = 1.0.5<br /> | MedMij_FunctioneelOntwerp = 1.0.2<br /> | Kwalificatie = 1.0.4<br /> | package = 0.8.0-beta.1<br /> | nictiz.fhir.nl.r4.zib2020 = 0.8.0-beta.1<br /> | nictiz.fhir.nl.r4.nl-core = 0.8.0-beta.1<br /> | nictiz.fhir.nl.r4.patientcorrections = 1.0.6<br /> | nictiz.fhir.nl.r4.immunization = 1.0.3<br /> | Editie = 6.1.3<br /> }}<br /> <br /> | MedMij:IG:V1 = {{#switch: {{{1}}}<br /> | MedMij_FHIR_IG_R4 = 1.0.5<br /> }}<br /> <br /> | MedMij:FO:V1 = {{#switch: {{{1}}}<br /> | MedMij_FunctioneelOntwerp = 1.0.2<br /> }}<br /> <br /> | MedMij:Kwalificatie:V1 = {{#switch: {{{1}}}<br /> | MedMij_Kwalificatie = 1.0.4<br /> }}<br /> <br /> | FHIR:V1.0 = {{#switch: {{{1}}}<br /> | FHIR_IG_R4 = 1.0.4<br /> }}<br /> <br /> | mp:V9.1 = {{#switch: {{{1}}}<br /> | mp = 9.1<br /> | Medicatieproces = 9.1.0<br /> | MedicatieprocesVerstrekkingenvertaling = 9.A.5<br /> | package = 2.0.0<br /> | nictiz.fhir.nl.stu3.zib2017 = 2.0.0<br /> | nictiz.fhir.nl.stu3.medicationprocess= 9.1.0-beta<br /> }}<br /> <br /> | mp:V2.0.0 = {{#switch: {{{1}}}<br /> | mp9 = 2.0.0<br /> | nictiz.fhir.nl.r4.zib2020 = 0.5.0-beta1<br /> | nictiz.fhir.nl.r4.nl-core = 0.5.0-beta1<br /> | nictiz.fhir.nl.r4.medicationprocess9 = 1.0.0<br /> }}<br /> <br /> | mp:V3.0.0-beta.1 = {{#switch: {{{1}}}<br /> | mp9 = 3.0.0-beta.1<br /> | nictiz.fhir.nl.r4.zib2020 = 0.8.0-beta.1<br /> | nictiz.fhir.nl.r4.nl-core = 0.8.0-beta.1<br /> | nictiz.fhir.nl.r4.medicationprocess9 = 2.0.0-beta.1<br /> }}<br /> <br /> | mp:V3.0.0-beta.2 = {{#switch: {{{1}}}<br /> | mp9 = 3.0.0-beta.2<br /> | nictiz.fhir.nl.r4.zib2020 = 0.10.0-beta.1<br /> | nictiz.fhir.nl.r4.nl-core = 0.10.0-beta.1<br /> | nictiz.fhir.nl.r4.medicationprocess9 = 2.0.0-beta.2<br /> }}<br /> <br /> | mp:V3.0.0 = {{#switch: {{{1}}}<br /> | mp9 = 3.0.0-beta.3<br /> | nictiz.fhir.nl.r4.zib2020 = 0.10.0-beta.1<br /> | nictiz.fhir.nl.r4.nl-core = 0.10.0-beta.1<br /> | nictiz.fhir.nl.r4.medicationprocess9 = 2.0.0-beta.5<br /> }}<br /> <br /> | Lab:V3.0.0 = {{#switch: {{{1}}}<br /> | nictiz.fhir.nl.r4.zib2020 = 0.6.0-beta.2<br /> | nictiz.fhir.nl.r4.nl-core = 0.6.0-beta.2<br /> | nictiz.fhir.nl.r4.labexchange = 3.0.0-beta.1<br /> }}<br /> <br /> | vpk:V4.0 = {{#switch: {{{1}}}<br /> | eOverdracht = 4.0.0<br /> | nictiz.fhir.nl.stu3.zib2017 = 2.2.18<br /> | nictiz.fhir.nl.stu3.eoverdracht = 4.0.0<br /> }}<br /> <br /> | vpk:V4.1 = {{#switch: {{{1}}}<br /> | eOverdracht = 4.1.0-alpha.1<br /> | nictiz.fhir.nl.stu3.zib2017 = 2.2.18<br /> | nictiz.fhir.nl.stu3.eoverdracht = 4.1.0-alpha.1<br /> | nictiz.fhir.nl.stu3.zib2020-preadopt = 0.1.3<br /> }}<br /> <br /> | hg:V1 = {{#switch: {{{1}}}<br /> | ELZ = 0.2.0-beta.1<br /> | BITS = {{Sjabloon:VerwijzingServicemanagement}}<br /> | nictiz.fhir.nl.r4.elz = 0.2.0-beta.1<br /> }}<br /> <br /> | Gebz:V1 = {{#switch: {{{1}}}<br /> | MedMij_Integrale_Zwangerschapskaart = 0.1.0-beta.1<br /> | nictiz.fhir.nl.stu3.geboortezorg = 1.2.0<br /> }}<br /> <br /> | cio:V2.0.0-beta.1 = {{#switch: {{{1}}}<br /> | CiO = 2.0.0-beta.1<br /> | BITS = https://bits.nictiz.nl/projects/CIO<br /> | nictiz.fhir.nl.r4.nl-core = 0.9.0-beta.1<br /> | nictiz.fhir.nl.r4.medicationprocess9 = 2.0.0-beta.1<br /> | nictiz.fhir.nl.r4.cio = 1.0.0-beta.1<br /> }}<br /> <br /> | cio:V2.0.0-beta.2 = {{#switch: {{{1}}}<br /> | CiO = 2.0.0-beta.2<br /> | BITS = https://bits.nictiz.nl/projects/CIO<br /> | nictiz.fhir.nl.r4.nl-core = 0.10.0-beta.1<br /> | nictiz.fhir.nl.r4.cio = 1.0.0-beta.2<br /> }}<br /> <br /> | cio:V2.0.0-beta.3 = {{#switch: {{{1}}}<br /> | CiO = 2.0.0-beta.3<br /> | BITS = https://bits.nictiz.nl/projects/CIO<br /> | nictiz.fhir.nl.r4.nl-core = 0.10.0-beta.1<br /> | nictiz.fhir.nl.r4.cio = 1.0.0-beta.3<br /> }}<br /> <br /> | bbs:V1.0.0 = {{#switch: {{{1}}}<br /> | BBS = 1.0.0-alfa.1<br /> | BITS = https://bits.nictiz.nl/projects/BBS<br /> }}<br /> <br /> | bbs:V1.0.0b = {{#switch: {{{1}}}<br /> | BBS = 1.0.0-alpha.2<br /> | BITS = https://bits.nictiz.nl/projects/BBS<br /> }}<br /> <br /> | BgZ:V1.1.0 = {{#switch: {{{1}}}<br /> | BgZ = 1.1.0-alfa.1<br /> | BITS = https://bits.nictiz.nl/projects/MSZ<br /> }}<br /> <br /> | jgz:V7 = {{#switch: {{{1}}}<br /> | JGZ = 7.1.3<br /> | BITS = {{Sjabloon:VerwijzingServicemanagement}}<br /> }}<br /> <br /> | imm:V2 = {{#switch: {{{1}}}<br /> | Vaccinatie-Immunisatie = 2.0.0-alpha.3<br /> | nictiz.fhir.nl.r4.nl-core = 0.10.0-beta.1<br /> | nictiz.fhir.nl.r4.immunization = 2.0.0-alpha.3<br /> | BITS = {{Sjabloon:VerwijzingServicemanagement}}<br /> }}<br /> <br /> }}&lt;noinclude&gt;<br /> == Doel ==<br /> <br /> Er zijn allerlei situaties waarin de specifieke versie van een component een bepaalde versie van een ander component gebruikt, bijvoorbeeld een versie van een informatiestandaard die een bepaalde versie van een FHIR-package nodig heeft. Dit sjabloon is bedoeld om dit soort versie-afhankelijkheden te leggen.<br /> <br /> == Gebruik ==<br /> <br /> Dit sjabloon koppelt simpelweg de versie (om legacy-redenen 'release' genoemd) van de gebruikende component plus de naam van de gebruikte component aan de versienummer van deze gebruikte component.<br /> <br /> Het sjabloon kan op pagina's ingezet worden met:<br /> &lt;pre&gt;{{VersieInfo|[component](|release=[release])(|namespace=[namespace])}}&lt;/pre&gt;<br /> * &lt;code&gt;component&lt;/code&gt;: de naam van de ''gebruikte'' component, dus bv. de naam van het FHIR-package dat een standaard gebruikt.<br /> * &lt;code&gt;release&lt;/code&gt;: de versie(string) van de ''gebruikende'' component, dus bv. de versie van een informatiestandaard die het FHIR-package gebruikt. Als deze parameter wordt weggelaten, wordt als default de [https://www.mediawiki.org/wiki/Help:Magic_words#Page_names ROOTPAGENAME] van de (aanroepende) pagina gebruikt.<br /> * &lt;code&gt;namespace&lt;/code&gt;: als de gebruikende ''pagina'' zich in een andere namespace bevindt dan de namespace geregistreerd in dit sjabloon kan hier de namespace expliciet vermeld worden. Dit is vooral relevant voor verwijzingen waarin het versienummer wordt opgenomen.<br /> <br /> Dit wordt dan vervangen door het bijbehorende versienummer. De naam van 'component' dient uiteraard exact overeen te komen met de naam die in dit sjabloon staat.<br /> <br /> Bijvoorbeeld: binnen MedMij worden versienummers van individuele informatiestandaarden gekoppeld aan een bepaalde MedMij-release. Bv. de BgZ heeft binnen de MedMij-release &quot;V2019.01&quot; het versienummer 2.1.13. Dit kan opgezocht worden via:<br /> <br /> &lt;pre&gt;{{VersieInfo|BgZ|release=V2019.01}}&lt;/pre&gt;<br /> <br /> === Onderhoud versienummers ===<br /> <br /> Het sjabloon bestaat uit een geneste switch; de eerste tak kijkt naar de Release (de eerste parameter), de tweede naar de naam van de gezochte component. Deze informatie staat bovenaan de pagina wanneer deze bewerkt wordt.<br /> <br /> Wanneer het nodig is om een nieuwe release toe te voegen, volstaat het om het volgende stuk toe te voegen:<br /> &lt;pre&gt;<br /> | NAMESPACE:&lt;release&gt; = {{#switch: {{{2}}}<br /> | &lt;component1&gt; = x.x.x<br /> | &lt;component2&gt; = x.x.x<br /> ...<br /> | &lt;componentN&gt; = x.x.x<br /> <br /> }}<br /> &lt;/pre&gt;<br /> === Afwijkende versienummers in systeemrolcodes ===<br /> <br /> In sommige informatiestandaarden zijn er systeemrolcodes met een versie die afwijkt van die van de standaard als geheel. Typisch gebeurt dit wanneer er een use case is bijgekomen in een standaard; de major-versie wordt opgehoogd, maar de systeemrollen in de oorspronkelijke use case blijven de oorspronkelijke versie gebruiken (zolang er nog geen reden is om over te gaan naar een nieuwe versie).<br /> <br /> Er is gekozen voor een pragmatische aanpak in dit soort gevallen door simpelweg een tweede entry toe te voegen voor de afwijkende major-versie; de standaard &quot;PDF/A&quot; staat bijvoorbeeld twee keer in het lijstje, een keer als &quot;PDFA&quot; en een keer als &quot;PDFA1&quot; voor de oudere systeemrolcodes.<br /> &lt;/noinclude&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=cio:V2.0.0-beta.3_FHIR_CiO&diff=223277 2024-07-24T08:51:29Z

<p>Luud Slagter: Initial technical design beta.3</p> <hr /> <div>{{Vdraft/InformationBox|This FHIR IG is currently under development and can not be considered stable and ready for use. For questions and change requests regarding this IG, please create a ticket in [{{VersieInfo|BITS|release=V2.0.0-beta.2|namespace=cio}} BITS].}}<br /> <br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide CiO version {{VersieInfo|CiO|release=V2.0.0-beta.2|namespace=cio}}}}<br /> <br /> [[Bestand:Icoon Nictiz Cirkel Informatiestandaard Contra-indicaties en Overgevoeligheden (2).svg|link=|100px|CiO|rechts]] <br /> <br /> &lt;div class=&quot;toclimit-3&quot;&gt;__TOC__&lt;/div&gt;<br /> <br /> = Introduction =<br /> <br /> This is the implementation guide (IG) for the information standard CiO (Dutch: Contra-indicaties en overgevoeligheden, English: Contraindications and hypersensitivities), version {{VersieInfo|CiO|release=V2.0.0-beta.2}}. The functional specification can be found [[cio:V2.0.0-beta.2_Ontwerp_CiO|here]] and is implemented using [https://www.hl7.org/fhir/R4/ HL7 FHIR R4]. This implementation guide assumes that the reader is familiar with both the functional specification and this version of FHIR.<br /> <br /> 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 Overarching principles and the use of FHIR packages. Where the general IG uses the term ‘use case’, this IG uses the term ‘transaction’ for the various processes that are described.<br /> <br /> This IG first describes the boundaries and relationships in place, after which the implementation is described per transaction.<br /> <br /> = Boundaries and relationships =<br /> <br /> == Boundaries ==<br /> <br /> Note that this version of the CiO information standard is only focused on medication contraindications and hypersensitivities due to medication (see [[cio:V2.0.0-beta.2_Ontwerp_CiO#Algemeen|section 1.1 of the functional specification]]). Technically this scope is reflected in for instance the terminology used within the FHIR profiles or the naming of the cio-MedicationContraIndication profile. In this IG however, we will not further elaborate on this narrower scope and instead describe the technical implementation of this standard as general as possible, in order to make it easier to incorporate a broadening of the scope in subsequent versions of this IG.<br /> <br /> == Building blocks and profiles ==<br /> <br /> The exchange of data within the CiO standard version {{VersieInfo|CiO|release=V2.0.0-beta.2}} is partly based on the 2020 publication of the Dutch Health and Care Information Models (Dutch: ‘zorginformatiebouwstenen’ or ‘zibs’), and subsequent changes made that will be present in the 2024 prepublication. In particular, the prepublication of 2021 saw the introduction of the Hypersensitivity and Reaction zibs which are based on and still have quite some overlap with the zib AllergyIntolerance that already existed. In the prepublication of 2024 the zibs Hypersensitivity and Reaction have been overhauled in such a way that they only contain ‘diagnostic’ elements. The concepts within these zibs that were related to surveillance with respect to substances have been removed, resulting in a new zib SurveillanceDecision. Moreover, the zib Alert has changed in this prepublication such that the zib MedicationContraIndication has become superfluous, by adding a new AlertType reserved for medication contraindications. The functional data set of CiO has further built upon these four zibs, and the resulting objects (which are actually exchanged) are referred to as ‘building blocks’ in the data set, and can thus be seen as ‘extended zibs’ suitable for implementation.<br /> <br /> Due to new insights, the building blocks Hypersensitivity and Reaction in the functional data set have deviated quite a lot from the zib AllergyIntolerance present in the 2020 publication, making them incompatible in varying degrees from a technical point of view. Therefore it was not possible to implement the FHIR profiles for these 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 the nl-core profiles, meaning that they are not derived from nl-core-AllergyIntolerance. Similarly, for the building block MedicationContraIndication it was not possible to derive its profile from the nl-core-Alert profile corresponding to zib publication 2020, due to incompatible changes introduced in the zib Alert in the prepublication of 2024. Lastly, the zib SurveillanceDecision is newly introduced, so obviously no derivation from nl-core profiles is possible.<br /> <br /> In a subsequent version of the information standard, it is the intention to base the profiles for all building blocks on their respective nl-core profiles based on zib publication 2024. There are however some considerations to be taken into account, since it is only possible to use these nl-core profiles provided:<br /> * the underlying zibs are still part of the 2024 publication;<br /> * no incompatible changes will be added on the relevant zibs between the prepublication and publication of 2024;<br /> * they are defined in FHIR R4 (otherwise the cio profiles would also need to be converted to another FHIR version).<br /> <br /> It is important to note that there is still extensive discussion about the exact scope and content of the CiO building blocks, meaning that the current profiles definitely cannot be considered to be stable and ready for use. A list of discussion topics with regards to the technical implementation can be found in [[#Discussion|section 2.5]].<br /> <br /> {{NoteBoxNictizR4Package|p1=nictiz.fhir.nl.r4.cio|v1={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}|p2=nictiz.fhir.nl.r4.nl-core|v2={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> <br /> Note that the package versioning does not follow the versioning of the information standard, as CiO version 2.0.0 was the first release of the CiO information standard based on FHIR R4. This means that CiO version 2.0.0-beta.x makes use of version 1.0.0-beta.x of the nictiz.fhir.nl.r4.cio FHIR package.<br /> <br /> === Main building blocks ===<br /> <br /> As described above, the main building blocks have no dependency on any zib counterparts of the 2020 publication, resulting in so-called ‘cio’ profiles.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationContraIndication<br /> | MedicatieContraIndicatie<br /> | Flag<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-MedicationContraIndication|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | SurveillanceDecision<br /> | BewakingBesluit<br /> | Flag<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-SurveillanceDecision|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Hypersensitivity<br /> | Overgevoeligheid<br /> | AllergyIntolerance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Hypersensitivity|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Reaction<br /> | Reactie<br /> | AllergyIntolerance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Reaction|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Condition<br /> | Aandoening<br /> | Condition<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Condition|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | RegistrationData<br /> | RegistratieGegevens<br /> | Provenance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-RegistrationData|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |}<br /> <br /> The last two building blocks in the above table have a special status:<br /> * Condition is not a separate building block within the CiO data set, and the cio-Condition profile actually contains mappings to concepts within the Hypersensitivity and Reaction building blocks that relate to the underlying condition and diagnosis. Thus, in order to convey the complete Hypersensitivity or Reaction building block, it is necessary to use an instance conforming to the cio-Hypersensitivity or cio-Reaction profile, together with an instance conforming to the cio-Condition profile.<br /> * The RegistrationData building block is part of every other main building block in the data set, containing data that relates to the registering process instead of the medical concept itself. Such data is often not (completely) mappable within the profiles corresponding to the medical concept. Hence, whenever another main building block is exchanged, it is represented by its own profile in conjunction with an instance of the cio-RegistrationData profile. In the future, if more information standards will make use of the Provenance resource to represent the administrative concepts present in RegistrationData, it is intended to create an nl-core-RegistrationData profile that replaces the cio-RegistrationData profile.<br /> <br /> === Secondary building blocks ===<br /> <br /> Additionally, the standard uses several secondary building blocks referenced from the main building blocks. All secondary building blocks are part of the [[FHIR:V1.0_FHIR_IG_R4#Functional_definitions|‘nl-core’]] package.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | ContactPerson<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |}<br /> <br /> Note the following:<br /> * Each occurrence of the zib HealthProfessional is normally represented by '''two''' FHIR resources: an instance of nl-core-HealthProfessional-PractitionerRole and an instance of nl-core-HealthProfessional-Practitioner. Sending systems should only fill the reference to the PractitionerRole instance where relevant. Receiving systems can resolve the reference to the Practitioner resource from that PractitionerRole instance.<br /> * The zib HealthcareProvider is mapped to both a Location and Organization profile. In general the Location profile acts as the focal resource, because most references to this zib are concerned about the recording of the physical location where the care to patient takes place rather than the organizational information. However, within the CiO information standard, the HealthcareProvider is only referenced indirectly via the PractitionerRole resource, hence a reference to the Organization profile is sufficient in those cases. The Location profile is mentioned in the table above for completeness purposes.<br /> <br /> === Relations between building blocks ===<br /> <br /> [[Bestand:Resources diagram CiO (beta.2).drawio.png|1000px]]<br /> <br /> == Mappings between profiles and data set ==<br /> <br /> Each transaction starts with links to the functional definition in an ART-DECOR publication and references one or several FHIR profiles. The FHIR profiles contain mappings to all data elements that are present in the functional data set (prefixed with ‘cio-dataelement-20-’).<br /> <br /> 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}} or {{fhir|.patient}} of each FHIR instance of each main building block (with the exception of RegistrationData).<br /> <br /> 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 Identifier, for example RelationHypersensitivity (cio-dataelement-20-734) in building block Hypersensitivity. 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]].<br /> <br /> == Patient identification ==<br /> <br /> This implementation guide assumes that the client system is able to make a connection to the right server that contains the patient's information. It does not provide information on finding the right server nor does it provide information about security. Moreover, each transaction is performed in the context of a specific patient, whose context might have been established using the authentication mechanisms described in external specifications such as the MedMij ‘Afsprakenstelsel’ or through the usage of search parameters for patient identification. <br /> <br /> Each server is required to perform filtering based on the patient associated with the context for the request or based on the patient identification search parameters, which is a [https://www.hl7.org/fhir/r4/search.html#chaining chained search parameter] for all resource types except Patient, so only the records associated with the authenticated patient are returned.<br /> <br /> When patient identification requires the use of search parameters, the following search parameters SHALL be supported:<br /> * Patient: {{fhir|identifier}}<br /> * Flag: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> <br /> An example of a request that retrieves all Flag resources of a patient with a fake BSN of 111222333:<br /> <br /> &lt;pre&gt;GET [base]/Flag?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> <br /> Most request examples in this IG do not include patient identification mechanisms. Requesters are assumed to include these if necessary.<br /> <br /> == Discussion ==<br /> <br /> As stated before, the current profiles cannot be considered to be stable and ready for use. This is partly due to the ongoing discussion about the exact scope and content of the functional building blocks in CiO. However, there are also some topics regarding the technical implementation that need to be addressed before considering the resulting FHIR profiles to be ready for use:<br /> <br /> * The functional data set defines several relations between different building blocks (concepts with a name starting with ‘Relation…’), which have been implemented in FHIR as custom extensions of data type ‘Reference’. Some of these refer to instances of the same building block and are meant to track updates done between different instances of the same building block. In that sense the approach of the Medication Process information standard is followed here, where such relations are used for building blocks that are changed or stopped. In FHIR however it is possible to just update existing resources resulting in a new version of the same instance, and therefore it is up for debate whether this approach is deemed necessary and desirable for the CiO use cases. In particular one might wonder whether this approach is justified for Flag resources, since this resource has a different nature than for instance medication-related resources. The conclusion on this topic also depends on the way object identification and mutations will be handled on a functional level within the CiO information standard. This has not been fully thought out yet and will be taken into consideration for the 2.0.0-beta.3 release.<br /> * This is the first release of an information standard making use of the Provenance resource to represent the concepts present within the zib RegistrationData (instead of defining additional extensions for concepts like RegistrationDateTime and InformationSource). The exact use of this resource on a broader level needs to be further analyzed (and generalized).<br /> * Several concepts within the Hypersensitivity and Reaction building blocks that are related to the underlying condition and diagnosis have been mapped to elements within a separate Condition profile, instead of adding them as extensions within the AllergyIntolerance profiles. It needs to be discussed whether this approach is feasible (also taking into account international standards) and whether this Condition resource has a ‘right’ to exist. Moreover, the Hypersensitivity and Reaction building blocks are modeled by different AllergyIntolerance profiles, as they are both representing diagnostic insight of a health professional regarding (the predisposition to develop) a reaction, while in core FHIR the relation between a hypersensitivity and reactions due to that hypersensitivity are modeled within one AllergyIntolerance. This discrepancy might result in difficulties when exchanging information on hypersensitivities and reactions on a broader/international scale. Both modeling approaches mentioned here need to be taken into account while deciding on the definitive modeling of the aforementioned building blocks.<br /> * The exact requirements regarding the search parameters used within CiO aren't fully fledged yet, especially the {{fhir|_revinclude}} defined on {{fhir|Provenance.target}}, and the possible requirement of an {{fhir|_include}} on the contents of the {{fhir|flag-detail}} extension (the latter being out of scope for this release). Note that in general, references are required to be either resolvable or readily available in the search request results; since the reference between the Provenance resource and other resources is reversed with respect to the focal resource of the search requests, supporting the {{fhir|_revinclude}} on {{fhir|Provenance.target}} is required. Further discussion with software suppliers is necessary to finalize these requirements.<br /> <br /> = Transactions =<br /> <br /> This section describes the FHIR implementation of all transactions listed in [[cio:V2.0.0-beta.2_Ontwerp_CiO#Usecases|section 2 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’.<br /> <br /> == Medication Contraindication (Retrieve/Serve) ==<br /> <br /> The retrieve medication contraindications transaction is used by the client to retrieve medication contraindications from a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Transaction group<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Transaction<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Actor<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| System role<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| FHIR CapabilityStatement<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/sc-2.16.840.1.113883.2.4.3.11.60.26.3.2-2019-08-28T133341.html#_2.16.840.1.113883.2.4.3.11.60.26.4.16_20200622101830 MedicationContraIndication (PULL)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/tr-2.16.840.1.113883.2.4.3.11.60.26.4.17-2020-06-22T101830.html Retrieving medication contraindications]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|CIO-MCIR<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/cio-MedicationContraindications.RetrieveServe|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}|title=CapabilityStatement Retrieve/serve medication contraindications}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/tr-2.16.840.1.113883.2.4.3.11.60.26.4.18-2020-06-22T101830.html Serving medication contraindications]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|CIO-MCIB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> <br /> When a health professional or healthcare provider wants to obtain all medication contraindications or specific ones matching various parameters, they issue a retrieve medication contraindications request message. This message uses the HTTP GET method parameterized query against the server's FHIR Flag endpoint.<br /> <br /> The search interaction is performed by an HTTP GET conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query.<br /> <br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|350241000146102&amp;_revinclude=Provenance:target{&amp;[additional parameter(s)]}&lt;/pre&gt;<br /> <br /> ==== Search parameters ====<br /> <br /> All search parameters listed in the table below SHALL be supported for processing by servers and MAY be supported by clients, with the exception of the {{fhir|category}} parameter, as well as the {{fhir|&lt;nowiki&gt;_revinclude=Provenance:target&lt;/nowiki&gt;}} search result parameter, which SHALL be supported by clients as well (as these are always part of the search query in this transaction).<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | CiO search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Description<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Example<br /> |-<br /> | -<br /> | Search on MedicationContraIndication building blocks (not taking into account the RegistrationData building block). <br /> | {{fhir|category}} &lt;ref name=&quot;custom-searchparameter&quot;&gt;The search parameter consists of a custom FHIR search parameter not represented in the FHIR specification.&lt;/ref&gt;<br /> | Flag<br /> | Retrieves all Flag resources representing a MedicationContraIndication.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|350241000146102&lt;/pre&gt;<br /> |-<br /> | -<br /> | Include the RegistrationData building block referenced from the MedicationContraIndication.<br /> | {{fhir|&lt;nowiki&gt;_revinclude=Provenance:target&lt;/nowiki&gt;}}<br /> | Flag<br /> | Retrieves all Flag and corresponding Provenance resources representing a MedicationContraIndication.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|350241000146102&amp;_revinclude=Provenance:target&lt;/pre&gt;<br /> |-<br /> | PatientIdentificationNumber<br /> | Search on patient.<br /> | {{fhir|patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;&gt;This search parameter only needs to be supported when patient identification requires the use of search parameters, see [[#Patient_identification|section 2.4]].&lt;/ref&gt;<br /> | Flag<br /> | Retrieves all MedicationContraIndication building blocks of a patient with a fake BSN of 111222333.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|350241000146102&amp;patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&amp;_revinclude=Provenance:target&lt;/pre&gt;<br /> |-<br /> | ReferenceDate<br /> | Search on the MedicationContraIndication building blocks that were active on or after a certain date.<br /> | {{fhir|date}}<br /> | Flag<br /> | Retrieves all MedicationContraIndication building blocks that were active from 01-05-2023.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|350241000146102&amp;date=ge2023-05-01&amp;_revinclude=Provenance:target&lt;/pre&gt;<br /> |-<br /> | -<br /> | The client may request that the server returns resources related to the search results, in order to reduce the overall network delay of repeated retrievals of related resources.<br /> Supporting the include of the Patient resource referenced by building blocks is required. Others (PractitionerRole, Practitioner, RelatedPerson, Organization) are optional. However: all resources referenced per literal reference SHALL be resolvable [[FHIR:V1.0_FHIR_IG_R4#Including_referenced_resources|per the Nictiz IG]].<br /> | {{fhir|&lt;nowiki&gt;_include=Flag:patient&lt;/nowiki&gt;}}<br /> | Flag<br /> | Retrieves all MedicationContraIndication building blocks of a patient with a fake BSN of 111222333 and includes the Patient resource in the search results.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|350241000146102&amp;patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&amp;_revinclude=Provenance:target&amp;_include=Flag:patient&lt;/pre&gt;<br /> |}<br /> <br /> The following custom search parameter is defined for this transaction:<br /> <br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/Flag-category|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> <br /> === Serve (response message) ===<br /> <br /> The server returns an HTTP Status code appropriate to the processing outcome and returns a Bundle, with {{fhir|Bundle.type}} = {{term|searchset}}, including the resources matching the search query. The resources included in the Bundle SHALL conform to the profiles listed in the ‘List of profiles’ below.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationContraIndication<br /> | MedicatieContraIndicatie<br /> | Flag<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-MedicationContraIndication|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | RegistrationData<br /> | RegistratieGegevens<br /> | Provenance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-RegistrationData|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | HealthcareProvider<br /> | Zorgaanbieder<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | ContactPerson<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |}<br /> <br /> == Medication Contraindication (Send/Receive) ==<br /> <br /> The send medication contraindications transaction is used by the client to send medication contraindications to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Transaction group<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Transaction<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Actor<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| System role<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| FHIR CapabilityStatement<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/sc-2.16.840.1.113883.2.4.3.11.60.26.3.2-2019-08-28T133341.html#_2.16.840.1.113883.2.4.3.11.60.26.4.10_20200622101711 MedicationContraIndication (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/tr-2.16.840.1.113883.2.4.3.11.60.26.4.11-2020-06-22T101711.html Sending medication contraindications]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|CIO-MCIS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/cio-MedicationContraIndications.SendReceive|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}|title=CapabilityStatement Send/receive medication contraindications}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication contraindications<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|CIO-MCIO<br /> |}<br /> <br /> === Send (request message) ===<br /> <br /> Because the data sent in this transaction potentially consists of several building blocks along with secondary resources, a [https://www.hl7.org/fhir/r4/http.html#transaction {{term|transaction}} interaction] is used. This allows for sending a Bundle with a set of resources in a single interaction and makes it possible to [[FHIR:V1.0_FHIR_IG_R4#Including_.22secondary.22_resources_when_sending_information|include referenced secondary resources]] if needed. The interaction is performed by an HTTP POST command as shown:<br /> <br /> &lt;pre&gt;POST [base]&lt;/pre&gt;<br /> <br /> The body of the POST submission is a Bundle with {{fhir|Bundle.type}} = {{term|transaction}}. Each entry SHALL carry request details ({{fhir|Bundle.entry.request}}) that provide the HTTP method of the action to be executed. Usually, this will be POST, even for informative secondary resources.<br /> <br /> The resources included in the Bundle SHALL conform to the profiles listed in the ‘List of profiles’ below.<br /> <br /> === Receive (response message) ===<br /> <br /> The server returns an HTTP Status code appropriate to the processing outcome. If the transaction is successful, the server returns a Bundle with {{fhir|Bundle.type}} = {{term|transaction-response}}, that contains one entry for each entry in the request, in the same order, with the outcome of processing the entry. Included secondary resources are handled [[FHIR:V1.0_FHIR_IG_R4#Including_.22secondary.22_resources_when_sending_information|following the Nictiz IG]].<br /> <br /> If the transaction fails, the server returns an OperationOutcome with one or multiple {{fhir|.issue}} elements filled with information, as detailed as possible, that describes why the transaction failed and which resource and/or request caused this.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationContraIndication<br /> | MedicatieContraIndicatie<br /> | Flag<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-MedicationContraIndication|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | RegistrationData<br /> | RegistratieGegevens<br /> | Provenance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-RegistrationData|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | HealthcareProvider<br /> | Zorgaanbieder<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | ContactPerson<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |}<br /> <br /> == Medication Hypersensitivity (Retrieve/Serve) ==<br /> <br /> The retrieve medication hypersensitivities transaction is used by the client to retrieve medication hypersensitivities from a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Transaction group<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Transaction<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Actor<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| System role<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| FHIR CapabilityStatement<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/sc-2.16.840.1.113883.2.4.3.11.60.26.3.2-2019-08-28T133341.html#_2.16.840.1.113883.2.4.3.11.60.26.4.34_20201021150632 MedicationHypersensitivity (PULL)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/tr-2.16.840.1.113883.2.4.3.11.60.26.4.35-2020-10-21T150632.html Retrieving medication hypersensitivities]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|CIO-GOR<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/cio-MedicationHypersensitivities.RetrieveServe|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}|title=CapabilityStatement Retrieve/serve medication hypersensitivities}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/tr-2.16.840.1.113883.2.4.3.11.60.26.4.36-2020-10-21T150632.html Serving medication hypersensitivities]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|CIO-GOB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> <br /> When a health professional or healthcare provider wants to obtain all medication hypersensitivities or specific ones matching various parameters, they issue a retrieve medication hypersensitivities request message. This message uses the HTTP GET method parameterized query against the server's FHIR Flag endpoint.<br /> <br /> The search interaction is performed by an HTTP GET conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query.<br /> <br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|225419007&amp;_revinclude=Provenance:target{&amp;[additional parameter(s)]}&lt;/pre&gt;<br /> <br /> References within the {{fhir|flag-detail}} extension (in the Flag resources present in the search result) to instances conforming to the cio-Hypersensitivity or cio-Reaction profiles can be resolved afterwards by individual read operations. The same holds true for instances conforming to the cio-Condition profile referenced from {{fhir|Provenance.target}}.<br /> <br /> ==== Search parameters ====<br /> <br /> All search parameters listed in the table below SHALL be supported for processing by servers and MAY be supported by clients, with the exception of the {{fhir|category}} parameter, as well as the {{fhir|&lt;nowiki&gt;_revinclude=Provenance:target&lt;/nowiki&gt;}} search result parameter, which SHALL be supported by clients as well (as these are always part of the search query in this transaction).<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | CiO search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Description<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Example<br /> |-<br /> | -<br /> | Search on SurveillanceDecision building blocks (not taking into account the RegistrationData building block). <br /> | {{fhir|category}} &lt;ref name=&quot;custom-searchparameter&quot;&gt;The search parameter consists of a custom FHIR search parameter not represented in the FHIR specification.&lt;/ref&gt;<br /> | Flag<br /> | Retrieves all Flag resources representing a SurveillanceDecision.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|225419007&lt;/pre&gt;<br /> |-<br /> | -<br /> | Include the RegistrationData building block referenced from the SurveillanceDecision.<br /> | {{fhir|&lt;nowiki&gt;_revinclude=Provenance:target&lt;/nowiki&gt;}}<br /> | Flag<br /> | Retrieves all Flag and corresponding Provenance resources representing a SurveillanceDecision.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|225419007&amp;_revinclude=Provenance:target&lt;/pre&gt;<br /> |-<br /> | PatientIdentificationNumber<br /> | Search on patient.<br /> | {{fhir|patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;&gt;This search parameter only needs to be supported when patient identification requires the use of search parameters, see [[#Patient_identification|section 2.4]].&lt;/ref&gt;<br /> | Flag<br /> | Retrieves all SurveillanceDecision building blocks of a patient with a fake BSN of 111222333.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|225419007&amp;patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&amp;_revinclude=Provenance:target&lt;/pre&gt;<br /> |-<br /> | ReferenceDate<br /> | Search on the SurveillanceDecision building blocks that were active on or after a certain date.<br /> | {{fhir|date}}<br /> | Flag<br /> | Retrieves all SurveillanceDecision building blocks that were active from 01-05-2023.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|225419007&amp;date=ge2023-05-01&amp;_revinclude=Provenance:target&lt;/pre&gt;<br /> |-<br /> | -<br /> | The client may request that the server returns resources related to the search results, in order to reduce the overall network delay of repeated retrievals of related resources.<br /> References to AllergyIntolerance and Condition resources are resolved by individual read operations, as mentioned above. Supporting the include of the Patient resource referenced by building blocks is required. Others (PractitionerRole, Practitioner, RelatedPerson, Organization) are optional. However: all resources referenced per literal reference SHALL be resolvable [[FHIR:V1.0_FHIR_IG_R4#Including_referenced_resources|per the Nictiz IG]].<br /> | {{fhir|&lt;nowiki&gt;_include=Flag:patient&lt;/nowiki&gt;}}<br /> | Flag<br /> | Retrieves all SurveillanceDecision building blocks of a patient with a fake BSN of 111222333 and includes the Patient resource in the search results.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|225419007&amp;patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&amp;_revinclude=Provenance:target&amp;_include=Flag:patient&lt;/pre&gt;<br /> |}<br /> <br /> The following custom search parameter is defined for this transaction:<br /> <br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/Flag-category|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> <br /> === Serve (response message) ===<br /> <br /> The server returns an HTTP Status code appropriate to the processing outcome and returns a Bundle, with {{fhir|Bundle.type}} = {{term|searchset}}, including the resources matching the search query. The resources included in the Bundle SHALL conform to the profiles listed in the ‘List of profiles’ below.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | SurveillanceDecision<br /> | BewakingBesluit<br /> | Flag<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-SurveillanceDecision|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Hypersensitivity<br /> | Overgevoeligheid<br /> | AllergyIntolerance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Hypersensitivity|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Reaction<br /> | Reactie<br /> | AllergyIntolerance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Reaction|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Condition<br /> | Aandoening<br /> | Condition<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Condition|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | RegistrationData<br /> | RegistratieGegevens<br /> | Provenance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-RegistrationData|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | HealthcareProvider<br /> | Zorgaanbieder<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | ContactPerson<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |}<br /> <br /> == Medication Hypersensitivity (Send/Receive) ==<br /> <br /> The send medication hypersensitivities transaction is used by the client to send medication hypersensitivities to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Transaction group<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Transaction<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Actor<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| System role<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| FHIR CapabilityStatement<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/sc-2.16.840.1.113883.2.4.3.11.60.26.3.2-2019-08-28T133341.html#_2.16.840.1.113883.2.4.3.11.60.26.4.31_20201021150608 MedicationHypersensitivity (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/tr-2.16.840.1.113883.2.4.3.11.60.26.4.32-2020-10-21T150608.html Sending medication hypersensitivities ]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|CIO-GOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/cio-MedicationHypersensitivities.SendReceive|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}|title=CapabilityStatement Send/receive medication hypersensitivities }}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication hypersensitivities <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|CIO-GOO<br /> |}<br /> <br /> === Send (request message) ===<br /> <br /> Because the data sent in this transaction potentially consists of several building blocks along with secondary resources, a [https://www.hl7.org/fhir/r4/http.html#transaction {{term|transaction}} interaction] is used. This allows for sending a Bundle with a set of resources in a single interaction and makes it possible to [[FHIR:V1.0_FHIR_IG_R4#Including_.22secondary.22_resources_when_sending_information|include referenced secondary resources]] if needed. The interaction is performed by an HTTP POST command as shown:<br /> <br /> &lt;pre&gt;POST [base]&lt;/pre&gt;<br /> <br /> The body of the POST submission is a Bundle with {{fhir|Bundle.type}} = {{term|transaction}}. Each entry SHALL carry request details ({{fhir|Bundle.entry.request}}) that provide the HTTP method of the action to be executed. Usually, this will be POST, even for informative secondary resources.<br /> <br /> The resources included in the Bundle SHALL conform to the profiles listed in the ‘List of profiles’ below.<br /> <br /> === Receive (response message) ===<br /> <br /> The server returns an HTTP Status code appropriate to the processing outcome. If the transaction is successful, the server returns a Bundle with {{fhir|Bundle.type}} = {{term|transaction-response}}, that contains one entry for each entry in the request, in the same order, with the outcome of processing the entry. Included secondary resources are handled [[FHIR:V1.0_FHIR_IG_R4#Including_.22secondary.22_resources_when_sending_information|following the Nictiz IG]].<br /> <br /> If the transaction fails, the server returns an OperationOutcome with one or multiple {{fhir|.issue}} elements filled with information, as detailed as possible, that describes why the transaction failed and which resource and/or request caused this.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | SurveillanceDecision<br /> | BewakingBesluit<br /> | Flag<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-SurveillanceDecision|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Hypersensitivity<br /> | Overgevoeligheid<br /> | AllergyIntolerance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Hypersensitivity|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Reaction<br /> | Reactie<br /> | AllergyIntolerance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Reaction|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Condition<br /> | Aandoening<br /> | Condition<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Condition|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | RegistrationData<br /> | RegistratieGegevens<br /> | Provenance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-RegistrationData|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | HealthcareProvider<br /> | Zorgaanbieder<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | ContactPerson<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |}<br /> <br /> = Release notes =<br /> <br /> Release notes can be found on the [[cio:V2.0.0-beta.2_Ontwerp_CiO#Release_Notes| functional design page]].<br /> <br /> = Footnotes =</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=cio:V2.0.0-beta.2_testgegevens_overgevoeligheid_beschikbaarstellen&diff=212254 2024-03-27T17:08:14Z

<p>Luud Slagter: NICTIZ-13820: Updated test scenario references to addendum</p> <hr /> <div>{{DISPLAYTITLE:Contra-indicaties en Overgevoeligheden versie 2.0.0-beta.2 - testgegevens - geneesmiddelovergevoeligheden beschikbaarstellend systeem}}<br /> <br /> [[cio:V2.0.0_Kwalificatie_CiO|Terug naar alle testscenario's]]<br /> <br /> == Inleiding == <br /> Dit document biedt de mogelijkheid voor het testen van de volgende systeemrollen:<br /> * '''''G'''eneesmiddelovergevoeligheid '''B'''eschikbaarstellend systeem'' (CIO-GOB).<br /> <br /> De doelgroep van dit document is de leverancier die '''zelfstandig testen uitvoert ter voorbereiding op de kwalificatie'''. &lt;br&gt; <br /> Het testen geeft de mogelijkheid om de technische berichten te controleren. Visuele controle van screenshots is geen onderdeel van het testen.&lt;br&gt;<br /> &lt;br&gt;<br /> De testmaterialen kunnen worden aangevuld en gewijzigd (n.a.v. bevindingen). &lt;br&gt;<br /> Deze aanpassingen worden vermeld in de documenthistorie.&lt;br&gt;<br /> <br /> == Uit te voeren stappen ==<br /> <br /> Voer – voor ieder scenario in de 'Scenarioset' hoofdstukken – de volgende stappen uit:<br /> # Voer de gegevens van alle te testen geneesmiddelovergevoeligheden in voor de persoon genoemd in Persoonsgegevens.<br /> # De simulator verstuurt een 'Geneesmiddelovergevoeligheid raadplegen' bericht. <br /> # Ontvang het 'Geneesmiddelovergevoeligheid raadplegen' bericht en beantwoord deze met een 'Geneesmiddelovergevoeligheden beschikbaarstellen' bericht.<br /> <br /> == Leeswijzer ==<br /> Ieder navolgend hoofdstuk beschrijft een set scenario’s met steeds dezelfde paragraafindeling:<br /> # Scenario’s<br /> # Inhoudelijke gegevens<br /> <br /> ===Scenario's===<br /> In deze paragraaf zijn alle scenario's van het betreffende hoofdstuk beschreven. &lt;br&gt;<br /> <br /> De kolom 'beschrijving' geeft aan wat de testcase is en kan tevens aanvullende informatie en instructies bevatten.&lt;br&gt;<br /> Bij elk scenario staan de bouwstenen vermeld zoals die ook terug te vinden zijn in de paragraaf &quot;Inhoudelijke gegevens&quot; van het betreffende hoofdstuk.<br /> <br /> === Inhoudelijke gegevens ===<br /> Dit onderdeel bevat de ‘Persoonsgegevens’ zoals naam, adres en woonplaats, maar ook een (fictief) Burgerservicenummer (BSN). Daarnaast bevat deze paragraaf de specifieke gegevens die de leverancier beschikbaar moet stellen als Geneesmiddelovergevoeligheid beschikbaarstellend systeem.<br /> <br /> === Gebruikersschermen===<br /> Hoe de gebruikersschermen van een systeem er precies uitzien, is vrij in te vullen (immers: juist gebruikersvriendelijkheid is iets waarop leveranciers moeten kunnen concurreren), mits alle informatie in de juiste samenhang met de juiste semantiek (betekenis) is terug te vinden. <br /> Samenhang en correcte verwerking is onder andere belangrijk voor wijzigingen en stops.<br /> <br /> === Beschikbaarstellend systeem ===<br /> Het beschikbaarstellend systeem voert de gegevens uit de paragrafen &quot;Inhoudelijke gegevens&quot; in het XIS in. Voor een beschikbaarstellend systeem geldt dat sommige gegevens door dit systeem bepaald mogen of moeten worden:<br /> <br /> * Zorgverlener, zorgaanbieder (denk aan auteur). Dit mag een eigen (test)zorgverlener en organisatie zijn.<br /> * Identificatie van bouwstenen. LET OP: verwacht wordt dat hier 'eigen' identificaties aan worden toegekend in een eigen identificatiesysteem (eigen OID). De onderlinge referenties moeten natuurlijk wel kloppen. De identificatie van een geneesmiddelovergevoeligheid mag niet door het beschikbaarstellend systeem bepaald worden indien het aanpassingen betreft op andermans geneesmiddelovergevoeligheid.<br /> <br /> ===Datum T===<br /> T is de datum die voor het testen wordt gebruikt. Als ergens staat T – 100D betekent dit: 100 dagen eerder dan die afgesproken datum..&lt;br&gt;<br /> <br /> ==Scenarioset 0 Filtercriteria==<br /> <br /> === Scenario’s ===<br /> <br /> &lt;section begin=overview-bov-tst-0 /&gt;<br /> {| class=&quot;wikitable&quot;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot;<br /> | Scenario|| Beschrijving<br /> |-style=&quot;vertical-align:top;|style=&quot;background-color: white;&quot;<br /> |0.2|| Alle bewakingsbesluiten, overgevoeligheden en reacties, zonder aanvullend filtercriterium&lt;br/&gt;(Antwoord: bericht met 1 gestart (actief) bewakingsbesluit)<br /> |-style=&quot;vertical-align:top;|style=&quot;background-color: white;&quot;<br /> |0.2|| Alle bewakingsbesluiten, overgevoeligheden en reacties, met filter op peildatum (alles vanaf T-7D)&lt;br/&gt;(Antwoord: bericht zonder bewakingsbesluit)<br /> |-style=&quot;vertical-align:top;|style=&quot;background-color: white;&quot;<br /> |0.3|| Alle bewakingsbesluiten, overgevoeligheden en reacties, zonder aanvullend filtercriterium&lt;br/&gt;(Antwoord: bericht met 2 gestarte (actieve) bewakingsbesluiten, 1 gestopt bewakingsbesluit, 1 overgevoeligheid, 1 reactie)<br /> |-style=&quot;vertical-align:top;|style=&quot;background-color: white;&quot;<br /> |0.3|| Alle bewakingsbesluiten, overgevoeligheden en reacties, met filter op peildatum (alles vanaf T-1Y)&lt;br/&gt;(Antwoord: bericht met 1 gestart (actief) bewakingsbesluit, 1 gestopt bewakingsbesluit, 1 overgevoeligheid)<br /> |-style=&quot;vertical-align:top;|style=&quot;background-color: white;&quot;<br /> |}<br /> &lt;section end=overview-bov-tst-0 /&gt;<br /> <br /> ===Inhoudelijke gegevens===<br /> {{#lst:cio:V2.0.0-beta.2_testgegevens_bgmo_addendum|cio-bgo-tst-0.2-minimaalBB}}<br /> <br /> {{#lst:cio:V2.0.0-beta.2_testgegevens_bgmo_addendum|cio-bgo-tst-0.3-maximaalBB}}<br /> <br /> {{#lst:cio:V2.0.0-beta.2_testgegevens_bgmo_addendum|cio-bgo-tst-0.4-relatiesBB}}<br /> <br /> == Documenthistorie ==<br /> {| class=&quot;wikitable&quot;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> | Datum||Omschrijving<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |style=&quot;background-color: white;&quot;| 2024-01-29<br /> |style=&quot;background-color: white;&quot;| testmateriaal bij publicatie CiO 2.0.0-beta.2<br /> |}<br /> <br /> &lt;font style=&quot;color: #B5B5B5;&quot;&gt;<br /> Deze pagina maakt gebruik van diverse sections uit addendum 'database': [[cio:V2.0.0-beta.2_testgegevens_bgmo_addendum|&lt;font style=&quot;color: #B5B5B5;&quot;&gt;''testgegevens Beschikbaarstellen geneesmiddelovergevoeligheden addendum''&lt;/font&gt;]]. &lt;/font&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=cio:V2.0.0-beta.2_testgegevens_bgmo_addendum&diff=212221 2024-03-26T16:10:51Z

<p>Luud Slagter: NICTIZ-13820: Updated wiki file (included proper references)</p> <hr /> <div><br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:Beschikbaarstellen geneesmiddelovergevoeligheden: addendum inhoudelijke gegevens}}<br /> <br /> =Addenda voor inhoudelijke gegevens=<br /> &lt;section begin=cio-bgo-tst-0.2-minimaalBB /&gt;<br /> ==Scenario 0.2 - minimaal BB==<br /> <br /> === &lt;span id=&quot;Pat02&quot; title=&quot;Intern ID = Pat02&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;_Pat02&quot;&gt;&lt;span id=&quot;Pat02&quot; title=&quot;Intern ID = Pat02&quot;&gt;&lt;span id=&quot;Pat02&quot; title=&quot;Intern ID = Pat02&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Petra<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|P<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX_Drijkoningen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999900523 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|25 okt 1963<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Vrouw (code = 'F' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.5.1&quot;&gt;HL7 AdministrativeGender&lt;/span&gt;')<br /> |}<br /> === Geneesmiddelovergevoeligheid - IBUPROFEN===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - IBUPROFEN<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;12&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 dagen om 09:10:54 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 dagen om 09:10:54 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|IBUPROFEN (code = '1155' in codeSystem 'G-Standaard generieke namen (bestand 750)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|Zie [[#RegGeg-pat02-BB-01|Registratie gegevens: RegGeg-pat02-BB-01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|zwelling van lippen en tong na gebruik van ibuprofen tabletten<br /> |}<br /> === Bouwstenen===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;6&quot; | Bouwstenen<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;5&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGeg-pat02-BB-01&quot; title=&quot;Intern ID = RegGeg-pat02-BB-01&quot;&gt;Registratie gegevens RegGeg-pat02-BB-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat02-BB-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 dagen om 09:10:54 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;zv-Peter-van-Pulver&quot; title=&quot;Intern ID = zv-Peter-van-Pulver&quot;&gt;Zorgverlener zv-Peter-van-Pulver&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|000001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.139)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Peter<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels<br /> |style=&quot;background-color: white;&quot;|van<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Huisartsen, niet nader gespecificeerd (code = '0100' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder<br /> |style=&quot;background-color: white;&quot;|Zie [[#za-Huisartsenpraktijk-Pulver-en-Partners|Zorgaanbieder: za-Huisartsenpraktijk-Pulver-en-Partners]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;za-Huisartsenpraktijk-Pulver-en-Partners&quot; title=&quot;Intern ID = za-Huisartsenpraktijk-Pulver-en-Partners&quot;&gt;Zorgaanbieder za-Huisartsenpraktijk-Pulver-en-Partners&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder identificatienummer<br /> |style=&quot;background-color: white;&quot;|00001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.205)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie naam<br /> |style=&quot;background-color: white;&quot;|Huisartsenpraktijk Pulver &amp; Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Dorpstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|1234AA<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Ons Dorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.5.1119&quot;&gt;HL7 AddressUse&lt;/span&gt;')<br /> |}&lt;section end=cio-bgo-tst-0.2-minimaalBB /&gt;<br /> &lt;section begin=cio-bgo-tst-0.3-maximaalBB /&gt;<br /> ==Scenario 0.3 - maximaal BB, O, R==<br /> <br /> === &lt;span id=&quot;Pat03&quot; title=&quot;Intern ID = Pat03&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;_Pat03&quot;&gt;&lt;span id=&quot;Pat03&quot; title=&quot;Intern ID = Pat03&quot;&gt;&lt;span id=&quot;Pat03&quot; title=&quot;Intern ID = Pat03&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Erwin<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|E<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX_Dubbeld<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999900535 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|26 okt 1963<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Man (code = 'M' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.5.1&quot;&gt;HL7 AdministrativeGender&lt;/span&gt;')<br /> |}<br /> === Geneesmiddelovergevoeligheid - PENICILLINES===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - PENICILLINES<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;12&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 108 dagen om 11:15:46 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 108 dagen om 11:15:46 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|Zie [[#RegGegevens-pat03-BB-01|Registratie gegevens: RegGegevens-pat03-BB-01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Patiënt heeft aangegeven in het verleden allergische reacties te hebben gehad na gebruik penicilline.<br /> |}<br /> === Geneesmiddelovergevoeligheid - PENICILLINES===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - PENICILLINES<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;15&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Discontinued (qualifier value) (code = '410546004' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:23:05 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:23:05 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Relatie bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Identificatie<br /> |style=&quot;background-color: white;&quot;|pat03-BB-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|Zie [[#RegGegevens-pat03-BB-02|Registratie gegevens: RegGegevens-pat03-BB-02]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Bewaking op volledige groep penicillines stopgezet, omdat patiënt wel goed reageert op flucloxacilline.<br /> |}<br /> === Geneesmiddelovergevoeligheid - PENICILLINES===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - PENICILLINES<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;15&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:25:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:25:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Besluit grond<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Overgevoeligheid<br /> |style=&quot;background-color: white;&quot;|Zie [[#pat03-overgevoeligheid-01|Overgevoeligheid: pat03-overgevoeligheid-01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Veilig binnen onveilige groep<br /> |style=&quot;background-color: white;&quot;|FLUCLOXACILLINE (code = '40991' in codeSystem 'G-Standaard generieke namen (Bestand 750)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|Zie [[#RegGegevens-pat03-BB-03|Registratie gegevens: RegGegevens-pat03-BB-03]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|&lt;span id=&quot;pat03-overgevoeligheid-01&quot; title=&quot;Intern ID = pat03-overgevoeligheid-01&quot;&gt;Overgevoeligheid pat03-overgevoeligheid-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;22&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 105 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening ernst<br /> |style=&quot;background-color: white;&quot;|Matig (code = '6736007' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening aanwezigheid<br /> |style=&quot;background-color: white;&quot;|Known present (qualifier value) (code = '410515003' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening status datum<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Agens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van vaststellen<br /> |style=&quot;background-color: white;&quot;|History and physical examination with evaluation and management of patient (procedure) (code = '14736009' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zekerheid status<br /> |style=&quot;background-color: white;&quot;|Confirmed present (qualifier value) (code = '410605003' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Overgevoeligheid categorie<br /> |style=&quot;background-color: white;&quot;|geneesmiddelen (code = '419511003' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Verwacht risico bij blootstelling<br /> |style=&quot;background-color: white;&quot;|Severe (severity modifier) (qualifier value) (code = '24484000' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Diagnose naam<br /> |style=&quot;background-color: white;&quot;|overgevoeligheid voor meerdere geneesmiddelen (aandoening) (code = '735458004' in codeSystem 'SNOMED Clinical Terms')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Nadere specificatie diagnose naam<br /> |style=&quot;background-color: white;&quot;|Overgevoeligheid voor penicillines<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Diagnostisch inzicht datum<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose steller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|Zie [[#RegGegevens-pat03-overg-01|Registratie gegevens: RegGegevens-pat03-overg-01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Vastgesteld middels huidpriktest. Flucloxacilline wordt wel goed verdragen door patiënt.<br /> |}<br /> === Geneesmiddelovergevoeligheid - AMLODIPINE===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - AMLODIPINE<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;15&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 730 dagen om 09:57:02 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 730 dagen om 09:57:02 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Besluit grond<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Reactie<br /> |style=&quot;background-color: white;&quot;|Zie [[#pat03-reactie-01|Reactie: pat03-reactie-01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|AMLODIPINE (code = '62081' in codeSystem 'G-Standaard generieke namen (bestand 750)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|Zie [[#RegGegevens-pat03-BB-04|Registratie gegevens: RegGegevens-pat03-BB-04]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Invaliderende bijwerking bij amlodipine tablet gebruik i.h.k.v. angina pectoris<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|&lt;span id=&quot;pat03-reactie-01&quot; title=&quot;Intern ID = pat03-reactie-01&quot;&gt;Reactie pat03-reactie-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;26&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening ernst<br /> |style=&quot;background-color: white;&quot;|Ernstig (code = '24484000' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening aanwezigheid<br /> |style=&quot;background-color: white;&quot;|Known present (qualifier value) (code = '410515003' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening status datum<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Veroorzaker<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Veroorzakende stof<br /> |style=&quot;background-color: white;&quot;|NORVASC TABLET 5MG (code = '642916' in codeSystem 'G-Standaard HPK')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van blootstelling<br /> |style=&quot;background-color: white;&quot;|ORAAL (code = '9' in codeSystem 'G-Standaard Toedieningswegen (tabel 7)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Blootstelling datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Latentietijd reactie<br /> |style=&quot;background-color: white;&quot;|12 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Tijdsduur reactie<br /> |style=&quot;background-color: white;&quot;|2 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van vaststellen<br /> |style=&quot;background-color: white;&quot;|History taking (procedure) (code = '84100007' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zekerheid status<br /> |style=&quot;background-color: white;&quot;|Suspected (qualifier value) (code = '415684004' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reactie verschijnsel<br /> |style=&quot;background-color: white;&quot;|Invaliderende hoofdpijn bij gebruik amlodipine<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reactie verschijnsel<br /> |style=&quot;background-color: white;&quot;|Visusklachten<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Diagnose naam<br /> |style=&quot;background-color: white;&quot;|overgevoeligheidsreactie (aandoening) (code = '421961002' in codeSystem 'SNOMED Clinical Terms')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Nadere specificatie diagnose naam<br /> |style=&quot;background-color: white;&quot;|Overgevoeligheidsreactie op amlodipine<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Diagnostisch inzicht datum<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose steller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|Zie [[#RegGegevens-pat03-reactie-01|Registratie gegevens: RegGegevens-pat03-reactie-01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Toelichtingsveld bij reactie<br /> |}<br /> === Bouwstenen===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;6&quot; | Bouwstenen<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;5&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-01&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-01&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;9&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 108 dagen om 11:15:46 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Zie [[#Pat03|Patient: Pat03]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-02&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-02&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-02&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-02 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:23:05 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-03&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-03&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-03&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-03 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:25:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-04&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-04&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-04&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;9&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-04 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 730 dagen om 09:57:02 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Zie [[#Pat03|Patient: Pat03]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-overg-01&quot; title=&quot;Intern ID = RegGegevens-pat03-overg-01&quot;&gt;Registratie gegevens RegGegevens-pat03-overg-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-overgevoeligheid-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.3)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:25:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-reactie-01&quot; title=&quot;Intern ID = RegGegevens-pat03-reactie-01&quot;&gt;Registratie gegevens RegGegevens-pat03-reactie-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-reactie-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.4)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 730 dagen om 09:57:02 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;zv-Peter-van-Pulver&quot; title=&quot;Intern ID = zv-Peter-van-Pulver&quot;&gt;Zorgverlener zv-Peter-van-Pulver&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|000001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.139)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Peter<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels<br /> |style=&quot;background-color: white;&quot;|van<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Huisartsen, niet nader gespecificeerd (code = '0100' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder<br /> |style=&quot;background-color: white;&quot;|Zie [[#za-Huisartsenpraktijk-Pulver-en-Partners|Zorgaanbieder: za-Huisartsenpraktijk-Pulver-en-Partners]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;za-Huisartsenpraktijk-Pulver-en-Partners&quot; title=&quot;Intern ID = za-Huisartsenpraktijk-Pulver-en-Partners&quot;&gt;Zorgaanbieder za-Huisartsenpraktijk-Pulver-en-Partners&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder identificatienummer<br /> |style=&quot;background-color: white;&quot;|00001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.205)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie naam<br /> |style=&quot;background-color: white;&quot;|Huisartsenpraktijk Pulver &amp; Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Dorpstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|1234AA<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Ons Dorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.5.1119&quot;&gt;HL7 AddressUse&lt;/span&gt;')<br /> |}&lt;section end=cio-bgo-tst-0.3-maximaalBB /&gt;<br /> &lt;section begin=cio-bgo-tst-0.4-relatiesBB /&gt;<br /> ==Scenario 0.4 - relaties BB, O, R==<br /> <br /> === &lt;span id=&quot;Pat04&quot; title=&quot;Intern ID = Pat04&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;_Pat04&quot;&gt;&lt;span id=&quot;Pat04&quot; title=&quot;Intern ID = Pat04&quot;&gt;&lt;span id=&quot;Pat04&quot; title=&quot;Intern ID = Pat04&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Willem<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|W<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX_Zwaan<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999901199 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|30 nov 1985<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Man (code = 'M' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.5.1&quot;&gt;HL7 AdministrativeGender&lt;/span&gt;')<br /> |}<br /> === Geneesmiddelovergevoeligheid - PENICILLINES===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - PENICILLINES<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;15&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 60 dagen om 11:15:46 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 60 dagen om 11:15:46 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Besluit grond<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Overgevoeligheid<br /> |style=&quot;background-color: white;&quot;|Zie [[#pat04-overgevoeligheid-01|Overgevoeligheid: pat04-overgevoeligheid-01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|Zie [[#RegGegevens-pat04-BB-01|Registratie gegevens: RegGegevens-pat04-BB-01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Uit voorzorg breed bewaken<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|&lt;span id=&quot;pat04-overgevoeligheid-01&quot; title=&quot;Intern ID = pat04-overgevoeligheid-01&quot;&gt;Overgevoeligheid pat04-overgevoeligheid-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;22&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 65 dagen om 18:00 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening ernst<br /> |style=&quot;background-color: white;&quot;|Matig (code = '6736007' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening aanwezigheid<br /> |style=&quot;background-color: white;&quot;|Known present (qualifier value) (code = '410515003' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening status datum<br /> |style=&quot;background-color: white;&quot;|T - 60 dagen om 11:15:46 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Agens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Stof<br /> |style=&quot;background-color: white;&quot;|FLUCLOXACILLINE (code = '40991' in codeSystem 'G-Standaard generieke namen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van vaststellen<br /> |style=&quot;background-color: white;&quot;|History taking (procedure) (code = '84100007' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zekerheid status<br /> |style=&quot;background-color: white;&quot;|Suspected (qualifier value) (code = '415684004' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Overgevoeligheid categorie<br /> |style=&quot;background-color: white;&quot;|geneesmiddelen (code = '419511003' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Verwacht risico bij blootstelling<br /> |style=&quot;background-color: white;&quot;|Mild (qualifier value) (code = '255604002' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Diagnose naam<br /> |style=&quot;background-color: white;&quot;|overgevoeligheid voor meerdere geneesmiddelen (aandoening) (code = '735458004' in codeSystem 'SNOMED Clinical Terms')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Nadere specificatie diagnose naam<br /> |style=&quot;background-color: white;&quot;|overgevoeligheid voor Flucloxacilline<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Diagnostisch inzicht datum<br /> |style=&quot;background-color: white;&quot;|T - 60 dagen om 11:15:46 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose steller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|Zie [[#RegGegevens-pat04-overg-01|Registratie gegevens: RegGegevens-pat04-overg-01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|mogelijk sprake van overgevoeligheid op meerdere geneesmiddelen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|&lt;span id=&quot;pat04-reactie-01&quot; title=&quot;Intern ID = pat04-reactie-01&quot;&gt;Reactie pat04-reactie-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;27&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 65 dagen om 18:00 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening ernst<br /> |style=&quot;background-color: white;&quot;|Matig (code = '6736007' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening aanwezigheid<br /> |style=&quot;background-color: white;&quot;|Known present (qualifier value) (code = '410515003' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening status datum<br /> |style=&quot;background-color: white;&quot;|T - 60 dagen om 11:15:46 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Veroorzaker<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Veroorzakende stof<br /> |style=&quot;background-color: white;&quot;|FLUCLOXACILLINE (code = '40991' in codeSystem 'G-Standaard generieke namen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van blootstelling<br /> |style=&quot;background-color: white;&quot;|ORAAL (code = '9' in codeSystem 'G-Standaard Toedieningswegen (tabel 7)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Blootstelling datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 65 dagen om 10:00 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Latentietijd reactie<br /> |style=&quot;background-color: white;&quot;|8 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Tijdsduur reactie<br /> |style=&quot;background-color: white;&quot;|2 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van vaststellen<br /> |style=&quot;background-color: white;&quot;|History taking (procedure) (code = '84100007' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zekerheid status<br /> |style=&quot;background-color: white;&quot;|Suspected (qualifier value) (code = '415684004' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reactie verschijnsel<br /> |style=&quot;background-color: white;&quot;|huiduitslag, gegeneraliseerd<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Diagnose naam<br /> |style=&quot;background-color: white;&quot;|ongewenste reactie (aandoening) (code = '281647001' in codeSystem 'SNOMED Clinical Terms')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Nadere specificatie diagnose naam<br /> |style=&quot;background-color: white;&quot;|ongewenste reactie op flucloxacilline<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Diagnostisch inzicht datum<br /> |style=&quot;background-color: white;&quot;|T - 60 dagen om 11:15:46 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose steller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Relatie overgevoeligheid<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Identificatie<br /> |style=&quot;background-color: white;&quot;|pat04-overgevoeligheid-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|Zie [[#RegGegevens-pat04-reactie-01|Registratie gegevens: RegGegevens-pat04-reactie-01]]<br /> |}<br /> === Geneesmiddelovergevoeligheid - PENICILLINES===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - PENICILLINES<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;18&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Discontinued (qualifier value) (code = '410546004' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 10 dagen om 15:55:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 10 dagen om 15:55:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Besluit grond<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Overgevoeligheid<br /> |style=&quot;background-color: white;&quot;|Zie [[#pat04-overgevoeligheid-02|Overgevoeligheid: pat04-overgevoeligheid-02]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Relatie bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Identificatie<br /> |style=&quot;background-color: white;&quot;|pat04-BB-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|Zie [[#RegGegevens-pat04-BB-02|Registratie gegevens: RegGegevens-pat04-BB-02]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|de te bewaken stof moet aangepast worden<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|&lt;span id=&quot;pat04-overgevoeligheid-02&quot; title=&quot;Intern ID = pat04-overgevoeligheid-02&quot;&gt;Overgevoeligheid pat04-overgevoeligheid-02&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;25&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 65 dagen om 18:00 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening ernst<br /> |style=&quot;background-color: white;&quot;|Matig (code = '6736007' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening aanwezigheid<br /> |style=&quot;background-color: white;&quot;|Known absent (qualifier value) (code = '410516002' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening status datum<br /> |style=&quot;background-color: white;&quot;|T - 10 dagen om 15:55:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Agens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Stof<br /> |style=&quot;background-color: white;&quot;|FLUCLOXACILLINE (code = '40991' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.2.4.4.1.750&quot;&gt;G-Standaard SNK&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van vaststellen<br /> |style=&quot;background-color: white;&quot;|History taking (procedure) (code = '84100007' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zekerheid status<br /> |style=&quot;background-color: white;&quot;|Suspected (qualifier value) (code = '415684004' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Overgevoeligheid categorie<br /> |style=&quot;background-color: white;&quot;|geneesmiddelen (code = '419511003' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Verwacht risico bij blootstelling<br /> |style=&quot;background-color: white;&quot;|Mild (qualifier value) (code = '255604002' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Diagnose naam<br /> |style=&quot;background-color: white;&quot;|overgevoeligheid voor meerdere geneesmiddelen (aandoening) (code = '735458004' in codeSystem 'SNOMED Clinical Terms')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Nadere specificatie diagnose naam<br /> |style=&quot;background-color: white;&quot;|overgevoeligheid voor Flucloxacilline<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Diagnostisch inzicht datum<br /> |style=&quot;background-color: white;&quot;|T - 60 dagen om 11:15:46 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose steller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Relatie overgevoeligheid<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Identificatie<br /> |style=&quot;background-color: white;&quot;|pat04-overgevoeligheid-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|Zie [[#RegGegevens-pat04-overg-02|Registratie gegevens: RegGegevens-pat04-overg-02]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|mogelijk sprake van overgevoeligheid op meerdere geneesmiddelen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|&lt;span id=&quot;pat04-reactie-02&quot; title=&quot;Intern ID = pat04-reactie-02&quot;&gt;Reactie pat04-reactie-02&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;29&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 65 dagen om 18:00 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening ernst<br /> |style=&quot;background-color: white;&quot;|Matig (code = '6736007' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening aanwezigheid<br /> |style=&quot;background-color: white;&quot;|Known absent (qualifier value) (code = '410516002' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening status datum<br /> |style=&quot;background-color: white;&quot;|T - 10 dagen om 15:55:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Veroorzaker<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Veroorzakende stof<br /> |style=&quot;background-color: white;&quot;|FLUCLOXACILLINE (code = '40991' in codeSystem 'G-Standaard generieke namen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van blootstelling<br /> |style=&quot;background-color: white;&quot;|ORAAL (code = '9' in codeSystem 'G-Standaard Toedieningswegen (tabel 7)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Blootstelling datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 65 dagen om 10:00 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Latentietijd reactie<br /> |style=&quot;background-color: white;&quot;|8 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Tijdsduur reactie<br /> |style=&quot;background-color: white;&quot;|2 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van vaststellen<br /> |style=&quot;background-color: white;&quot;|History taking (procedure) (code = '84100007' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zekerheid status<br /> |style=&quot;background-color: white;&quot;|Suspected (qualifier value) (code = '415684004' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reactie verschijnsel<br /> |style=&quot;background-color: white;&quot;|huiduitslag, gegeneraliseerd<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Diagnose naam<br /> |style=&quot;background-color: white;&quot;|ongewenste reactie (aandoening) (code = '281647001' in codeSystem 'SNOMED Clinical Terms')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Diagnostisch inzicht datum<br /> |style=&quot;background-color: white;&quot;|T - 60 dagen om 11:15:46 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose steller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Relatie overgevoeligheid<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Identificatie<br /> |style=&quot;background-color: white;&quot;|pat04-overgevoeligheid-02 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.3)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Relatie reactie<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Identificatie<br /> |style=&quot;background-color: white;&quot;|pat04-reactie-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|Zie [[#RegGegevens-pat04-reactie-02|Registratie gegevens: RegGegevens-pat04-reactie-02]]<br /> |}<br /> === Geneesmiddelovergevoeligheid - PENICILLINES===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - PENICILLINES<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;19&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 10 dagen om 15:55:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 10 dagen om 15:55:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Besluit grond<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Overgevoeligheid<br /> |style=&quot;background-color: white;&quot;|Zie [[#pat04-overgevoeligheid-03|Overgevoeligheid: pat04-overgevoeligheid-03]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;4&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Veilig binnen onveilige groep<br /> |style=&quot;background-color: white;&quot;|FENOXYMETHYLPENICILLINE (code = '1051555' in codeSystem 'G Standaard HPK')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Veilig binnen onveilige groep<br /> |style=&quot;background-color: white;&quot;|BENZYLPENICILLINE VOOR INFUSIE (code = '2477696' in codeSystem 'G Standaard HPK')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Relatie bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Identificatie<br /> |style=&quot;background-color: white;&quot;|pat04-BB-02<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|Zie [[#RegGegevens-pat04-BB-03|Registratie gegevens: RegGegevens-pat04-BB-03]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|&lt;span id=&quot;pat04-overgevoeligheid-03&quot; title=&quot;Intern ID = pat04-overgevoeligheid-03&quot;&gt;Overgevoeligheid pat04-overgevoeligheid-03&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;25&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 65 dagen om 18:00 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening ernst<br /> |style=&quot;background-color: white;&quot;|Matig (code = '6736007' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening aanwezigheid<br /> |style=&quot;background-color: white;&quot;|Known present (qualifier value) (code = '410515003' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening status datum<br /> |style=&quot;background-color: white;&quot;|T - 10 dagen om 15:55:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Agens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van vaststellen<br /> |style=&quot;background-color: white;&quot;|History and physical examination with evaluation and management of patient (procedure) (code = '14736009' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zekerheid status<br /> |style=&quot;background-color: white;&quot;|Confirmed present (qualifier value) (code = '410605003' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Overgevoeligheid categorie<br /> |style=&quot;background-color: white;&quot;|geneesmiddelen (code = '419511003' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Verwacht risico bij blootstelling<br /> |style=&quot;background-color: white;&quot;|Mild (qualifier value) (code = '255604002' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Diagnose naam<br /> |style=&quot;background-color: white;&quot;|overgevoeligheid voor meerdere geneesmiddelen (aandoening) (code = '735458004' in codeSystem 'SNOMED Clinical Terms')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Nadere specificatie diagnose naam<br /> |style=&quot;background-color: white;&quot;|Overgevoeligheid voor penicillines<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Diagnostisch inzicht datum<br /> |style=&quot;background-color: white;&quot;|T - 10 dagen om 15:55:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose steller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Relatie overgevoeligheid<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Identificatie<br /> |style=&quot;background-color: white;&quot;|pat04-overgevoeligheid-02 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.3)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|Zie [[#RegGegevens-pat04-overg-03|Registratie gegevens: RegGegevens-pat04-overg-03]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Vastgesteld middels huidpriktest.<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|&lt;span id=&quot;pat04-reactie-03&quot; title=&quot;Intern ID = pat04-reactie-03&quot;&gt;Reactie pat04-reactie-03&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;30&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 65 dagen om 18:00 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening ernst<br /> |style=&quot;background-color: white;&quot;|Matig (code = '6736007' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening aanwezigheid<br /> |style=&quot;background-color: white;&quot;|Known present (qualifier value) (code = '410515003' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening status datum<br /> |style=&quot;background-color: white;&quot;|T - 10 dagen om 15:55:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Veroorzaker<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Veroorzakende stof<br /> |style=&quot;background-color: white;&quot;|FLUCLOXACILLINE (code = '40991' in codeSystem 'G-Standaard generieke namen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van blootstelling<br /> |style=&quot;background-color: white;&quot;|ORAAL (code = '9' in codeSystem 'G-Standaard Toedieningswegen (tabel 7)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Blootstelling datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 65 dagen om 10:00 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Latentietijd reactie<br /> |style=&quot;background-color: white;&quot;|8 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Tijdsduur reactie<br /> |style=&quot;background-color: white;&quot;|2 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van vaststellen<br /> |style=&quot;background-color: white;&quot;|History taking (procedure) (code = '84100007' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zekerheid status<br /> |style=&quot;background-color: white;&quot;|Confirmed present (qualifier value) (code = '410605003' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reactie verschijnsel<br /> |style=&quot;background-color: white;&quot;|huiduitslag, gegeneraliseerd<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Diagnose naam<br /> |style=&quot;background-color: white;&quot;|ongewenste reactie (aandoening) (code = '281647001' in codeSystem 'SNOMED Clinical Terms')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Nadere specificatie diagnose naam<br /> |style=&quot;background-color: white;&quot;|ongewenste reactie op flucloxacilline<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Diagnostisch inzicht datum<br /> |style=&quot;background-color: white;&quot;|T - 10 dagen om 15:55:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose steller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Relatie overgevoeligheid<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Identificatie<br /> |style=&quot;background-color: white;&quot;|pat04-overgevoeligheid-03<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Relatie reactie<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Identificatie<br /> |style=&quot;background-color: white;&quot;|pat04-reactie-02<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|Zie [[#RegGegevens-pat04-reactie-03|Registratie gegevens: RegGegevens-pat04-reactie-03]]<br /> |}<br /> === Bouwstenen===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;6&quot; | Bouwstenen<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;5&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat04-BB-01&quot; title=&quot;Intern ID = RegGegevens-pat04-BB-01&quot;&gt;Registratie gegevens RegGegevens-pat04-BB-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;9&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat04-BB-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 60 dagen om 11:15:46 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat04-BB-02&quot; title=&quot;Intern ID = RegGegevens-pat04-BB-02&quot;&gt;Registratie gegevens RegGegevens-pat04-BB-02&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat04-BB-02 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 10 dagen om 15:55:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat04-BB-03&quot; title=&quot;Intern ID = RegGegevens-pat04-BB-03&quot;&gt;Registratie gegevens RegGegevens-pat04-BB-03&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat04-BB-03 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 10 dagen om 15:55:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat04-overg-03&quot; title=&quot;Intern ID = RegGegevens-pat04-overg-03&quot;&gt;Registratie gegevens RegGegevens-pat04-overg-03&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat04-overgevoeligheid-03 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.3)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 10 dagen om 15:55:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat04-reactie-03&quot; title=&quot;Intern ID = RegGegevens-pat04-reactie-03&quot;&gt;Registratie gegevens RegGegevens-pat04-reactie-03&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat04-reactie-03 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.4)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 10 dagen om 15:55:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat04-overg-01&quot; title=&quot;Intern ID = RegGegevens-pat04-overg-01&quot;&gt;Registratie gegevens RegGegevens-pat04-overg-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat04-overgevoeligheid-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.3)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 60 dagen om 11:15:46 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat04-reactie-01&quot; title=&quot;Intern ID = RegGegevens-pat04-reactie-01&quot;&gt;Registratie gegevens RegGegevens-pat04-reactie-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat04-reactie-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.4)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 60 dagen om 11:15:46 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat04-overg-02&quot; title=&quot;Intern ID = RegGegevens-pat04-overg-02&quot;&gt;Registratie gegevens RegGegevens-pat04-overg-02&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat04-overgevoeligheid-02 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.3)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 10 dagen om 15:55:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat04-reactie-02&quot; title=&quot;Intern ID = RegGegevens-pat04-reactie-02&quot;&gt;Registratie gegevens RegGegevens-pat04-reactie-02&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat04-reactie-02 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.4)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 10 dagen om 15:55:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;zv-Peter-van-Pulver&quot; title=&quot;Intern ID = zv-Peter-van-Pulver&quot;&gt;Zorgverlener zv-Peter-van-Pulver&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|000001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.139)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Peter<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels<br /> |style=&quot;background-color: white;&quot;|van<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Huisartsen, niet nader gespecificeerd (code = '0100' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder<br /> |style=&quot;background-color: white;&quot;|Zie [[#za-Huisartsenpraktijk-Pulver-en-Partners|Zorgaanbieder: za-Huisartsenpraktijk-Pulver-en-Partners]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;za-Huisartsenpraktijk-Pulver-en-Partners&quot; title=&quot;Intern ID = za-Huisartsenpraktijk-Pulver-en-Partners&quot;&gt;Zorgaanbieder za-Huisartsenpraktijk-Pulver-en-Partners&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder identificatienummer<br /> |style=&quot;background-color: white;&quot;|00001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.205)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie naam<br /> |style=&quot;background-color: white;&quot;|Huisartsenpraktijk Pulver &amp; Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Dorpstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|1234AA<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Ons Dorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.5.1119&quot;&gt;HL7 AddressUse&lt;/span&gt;')<br /> |}&lt;section end=cio-bgo-tst-0.4-relatiesBB /&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=cio:V2.0.0-beta.2_testgegevens_bmci_addendum&diff=212220 2024-03-26T16:08:14Z

<p>Luud Slagter: NICTIZ-13820: Updated wiki file (included proper references)</p> <hr /> <div><br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:Beschikbaarstellen medicatiecontra-indicaties: addendum inhoudelijke gegevens}}<br /> <br /> =Addenda voor inhoudelijke gegevens=<br /> &lt;section begin=cio-bmci-tst-0.2-meerdereMCi /&gt;<br /> ==Scenario 0.2 - meerdere MCi==<br /> <br /> === &lt;span id=&quot;Pat02&quot; title=&quot;Intern ID = Pat02&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;_Pat02&quot;&gt;&lt;span id=&quot;Pat02&quot; title=&quot;Intern ID = Pat02&quot;&gt;&lt;span id=&quot;Pat02&quot; title=&quot;Intern ID = Pat02&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Petra<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|P<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX_Drijkoningen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999900523 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|25 okt 1963<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Vrouw (code = 'F' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.5.1&quot;&gt;HL7 AdministrativeGender&lt;/span&gt;')<br /> |}<br /> === Medicatie contra indicatie - Epilepsie===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Medicatie contra indicatie - Epilepsie<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Alert<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;8&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Alert type<br /> |style=&quot;background-color: white;&quot;|Potentiële contra-indicatie voor geneesmiddel (bevinding) (code = '350241000146102' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Alert naam<br /> |style=&quot;background-color: white;&quot;|Epilepsie (code = '42' in codeSystem 'G-standaard Contra Indicaties (Thesaurus 40)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 20 jaar om 13:20:48 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Vaststeller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-N-van-Erven|Zorgverlener: zv-N-van-Erven]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|Zie [[#RegGeg-pat02-mci-epi-01|Registratie gegevens: RegGeg-pat02-mci-epi-01]]<br /> |}<br /> === Medicatie contra indicatie - Zwangerschap===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Medicatie contra indicatie - Zwangerschap<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Alert<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;9&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Alert type<br /> |style=&quot;background-color: white;&quot;|Potentiële contra-indicatie voor geneesmiddel (bevinding) (code = '350241000146102' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Alert naam<br /> |style=&quot;background-color: white;&quot;|Zwangerschap (code = '1320' in codeSystem 'G-standaard Contra Indicaties (Thesaurus 40)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 370 maanden om 08:54:38 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Vaststeller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|Zie [[#RegGeg-pat02-mci-zwa-01|Registratie gegevens: RegGeg-pat02-mci-zwa-01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Additionele informatie over alert zwangerschap<br /> |}<br /> === Medicatie contra indicatie - Zwangerschap===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Medicatie contra indicatie - Zwangerschap<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Alert<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;13&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Alert type<br /> |style=&quot;background-color: white;&quot;|Potentiële contra-indicatie voor geneesmiddel (bevinding) (code = '350241000146102' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.6.96&quot;&gt;SNOMED CT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Alert naam<br /> |style=&quot;background-color: white;&quot;|Zwangerschap (code = '1320' in codeSystem 'G-standaard Contra Indicaties (Thesaurus 40)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 370 maanden om 08:54:38 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Eind datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 jaar om 10:11:42 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reden beeindiging alert<br /> |style=&quot;background-color: white;&quot;|patiënt niet meer zwanger<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Vaststeller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Relatie alert<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Identificatie<br /> |style=&quot;background-color: white;&quot;|pat02-mci-zwa-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|Zie [[#RegGeg-pat02-mci-zwa-02|Registratie gegevens: RegGeg-pat02-mci-zwa-02]]<br /> |}<br /> === Bouwstenen===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;6&quot; | Bouwstenen<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;5&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGeg-pat02-mci-epi-01&quot; title=&quot;Intern ID = RegGeg-pat02-mci-epi-01&quot;&gt;Registratie gegevens RegGeg-pat02-mci-epi-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;9&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat02-mci-epi-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.16)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-N-van-Erven|Zorgverlener: zv-N-van-Erven]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 20 jaar om 13:20:48 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Contactpersoon<br /> |style=&quot;background-color: white;&quot;|Zie [[#cp-A-Mann|Contactpersoon: cp-A-Mann]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGeg-pat02-mci-zwa-01&quot; title=&quot;Intern ID = RegGeg-pat02-mci-zwa-01&quot;&gt;Registratie gegevens RegGeg-pat02-mci-zwa-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;9&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat02-mci-zwa-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.16)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 jaar om 08:54:38 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGeg-pat02-mci-zwa-02&quot; title=&quot;Intern ID = RegGeg-pat02-mci-zwa-02&quot;&gt;Registratie gegevens RegGeg-pat02-mci-zwa-02&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;9&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat02-mci-zwa-02 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.16)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#zv-Peter-van-Pulver|Zorgverlener: zv-Peter-van-Pulver]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 370 maanden om 10:11:42 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Zie [[#Pat02|Patient: Pat02]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;cp-A-Mann&quot; title=&quot;Intern ID = cp-A-Mann&quot;&gt;Contactpersoon cp-A-Mann&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;9&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;5&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Adam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Mann<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Rol<br /> |style=&quot;background-color: white;&quot;|Eerste relatie/contactpersoon (code = '01' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.2.4.3.11.22.472&quot;&gt;Vektis Rolcode COD472-VEKT&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Relatie<br /> |style=&quot;background-color: white;&quot;|Partner (code = 'DOMPART' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.5.111&quot;&gt;HL7 RoleCode&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;zv-N-van-Erven&quot; title=&quot;Intern ID = zv-N-van-Erven&quot;&gt;Zorgverlener zv-N-van-Erven&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|000003332 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.139)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|N<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels<br /> |style=&quot;background-color: white;&quot;|van<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Erven<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Medisch specialisten, neurologie (code = '0330' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder<br /> |style=&quot;background-color: white;&quot;|Zie [[#za-Algemeen-Stadsziekenhuis|Zorgaanbieder: za-Algemeen-Stadsziekenhuis]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;zv-Peter-van-Pulver&quot; title=&quot;Intern ID = zv-Peter-van-Pulver&quot;&gt;Zorgverlener zv-Peter-van-Pulver&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;12&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|000001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.139)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;7&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Peter<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|P<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels<br /> |style=&quot;background-color: white;&quot;|van<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Huisartsen, niet nader gespecificeerd (code = '0100' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder<br /> |style=&quot;background-color: white;&quot;|Zie [[#za-Huisartsenpraktijk-Pulver-en-Partners|Zorgaanbieder: za-Huisartsenpraktijk-Pulver-en-Partners]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;za-Algemeen-Stadsziekenhuis&quot; title=&quot;Intern ID = za-Algemeen-Stadsziekenhuis&quot;&gt;Zorgaanbieder za-Algemeen-Stadsziekenhuis&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder identificatienummer<br /> |style=&quot;background-color: white;&quot;|00002222 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.205)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie naam<br /> |style=&quot;background-color: white;&quot;|Algemeen Stadsziekenhuis<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Afdeling specialisme<br /> |style=&quot;background-color: white;&quot;|Medisch specialisten, neurologie (code = '0330' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Hoofdstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|2143AA<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Zorgstad<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.5.1119&quot;&gt;HL7 AddressUse&lt;/span&gt;')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;za-Huisartsenpraktijk-Pulver-en-Partners&quot; title=&quot;Intern ID = za-Huisartsenpraktijk-Pulver-en-Partners&quot;&gt;Zorgaanbieder za-Huisartsenpraktijk-Pulver-en-Partners&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder identificatienummer<br /> |style=&quot;background-color: white;&quot;|00001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.205)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie naam<br /> |style=&quot;background-color: white;&quot;|Huisartsenpraktijk Pulver &amp; Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Dorpstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|1234AA<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Ons Dorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem '&lt;span title=&quot;2.16.840.1.113883.5.1119&quot;&gt;HL7 AddressUse&lt;/span&gt;')<br /> |}&lt;section end=cio-bmci-tst-0.2-meerdereMCi /&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=mp:V3.0.0-rc.2_MedicationProcess9_FHIR&diff=206726 2024-03-07T12:33:26Z

<p>Luud Slagter: /* Building blocks and profiles */</p> <hr /> <div>__NOINDEX__<br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide Medication Process 9 version {{VersieInfo|mp9|release=V3.0.0}} }}<br /> <br /> __TOC__<br /> <br /> = Introduction =<br /> 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.<br /> <br /> 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.<br /> <br /> This IG first describes the boundaries and relationships in place, after which the implementation is described per transaction.<br /> <br /> = Boundaries and relationships =<br /> == Building blocks and profiles ==<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> Because the way 90 million numbers are exchanged is not compatible with the 2020 publication of zib PharmaceuticalProduct, a fork of the corresponding nl-core profile called 'mp-PharmaceuticalProduct' has been introduced.<br /> <br /> {{NoteBoxNictizR4Package|p1=nictiz.fhir.nl.r4.medicationprocess9|v1={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|p2=nictiz.fhir.nl.r4.nl-core|v2={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> <br /> 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:<br /> * MP9 version 2.0.0 makes use of version 1.0.0 of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package;<br /> * MP9 version 3.0.0-beta.3 makes use of version 2.0.0-beta.5 of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package.<br /> <br /> === Medication building blocks ===<br /> <br /> As described above, the main medication building blocks have no dependency on any zib2020 counterparts, resulting in so-called ‘mp’ profiles. Moreover, note that the building block VariableDosingRegimen does not have a zib counterpart, hence it makes sense to include it as an mp profile as well.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |}<br /> <br /> === Supporting building blocks ===<br /> <br /> Additionally, the standard uses several supporting building blocks referenced from the main medication building blocks. All supporting building blocks are part of the [[FHIR:V1.0_FHIR_IG_R4#Functional_definitions|‘nl-core’ package]]&lt;ref&gt;Although the nl-core package is still in beta-status, HL7 Netherlands has validated the profiles mentioned and assigned the status 'STU-NL' for use in the MP9 Kickstart, see [[Media:HL7_Nederland_disclaimer_STU-NL.pdf]]&lt;/ref&gt;.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> Note the following:<br /> * Each occurrence of the zib HealthProfessional is normally represented by '''two''' FHIR resources: an instance of nl-core-HealthProfessional-PractitionerRole and an instance of nl-core-HealthProfessional-Practitioner. Sending systems should only fill the reference to the PractitionerRole instance where relevant. Receiving systems can resolve the reference to the Practitioner resource from that PractitionerRole instance.<br /> * The zib HealthcareProvider is mapped to both a Location and Organization profile. Most often, the Location profile acts as the focal resource, because most references to this zib are concerned about the recording of the physical location where the care to patient/client takes place rather than the organizational information. For the latter, the profile on Organization is used which is referenced using the {{fhir|Location.managingOrganization}} element. Sending systems should only fill the reference to the Location instance where relevant. Incidentally, concepts that are only concerned with organizational information can refer to the Organization instance.<br /> <br /> === Transaction specific profiles ===<br /> <br /> For several transactions, additional profiles are provided. For each transaction the profile relevant is explicitly mentioned in the corresponding subsection.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |}<br /> <br /> ====Bundle profiles====<br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == Mappings between profiles and data set ==<br /> 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.<br /> <br /> 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:<br /> * 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)<br /> ** 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.<br /> ** 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.<br /> * If an element in the functional definition is removed<br /> ** and the element had a zib mapping applied (not on an extension), the zib mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> ** and the element had a mapping applied to the previous version of MP9 (not on an extension), that mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> * If an element in the functional definition is removed and the element had a mapping applied on an extension, that extension is removed entirely. In particular no {{term|[DEPRECATED]}} mapping will be visible in the FHIR profile. This is done to ensure no redundant extensions remain in the FHIR profiles.<br /> <br /> Moreover, all mappings to earlier versions of MP9 (i.e. versions before the previous version) are entirely removed.<br /> <br /> Following the procedure outlined above thus results in the following:<br /> * 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.<br /> * All incompatible changes made in the latest version with respect to the previous version are marked.<br /> * Exceptions are extensions that would otherwise only contain deprecated mappings; these are removed fully.<br /> <br /> 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’]].<br /> <br /> 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.<br /> <br /> 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]].<br /> <br /> == Pharmaceutical treatment ==<br /> 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.<br /> <br /> == Patient identification ==<br /> This implementation guide assumes that the client system is able to make a connection to the right server that contains the patient's information. It does not provide information on finding the right server nor does it provide information about security. Moreover, each transaction is performed in the context of a specific patient, whose context might have been established using the authentication mechanisms described in external specifications such as the MedMij ‘Afsprakenstelsel’ or through the usage of search parameters for patient identification. <br /> <br /> Each server is required to perform filtering based on the patient associated with the context for the request or based on the patient identification search parameters, which is a [https://www.hl7.org/fhir/r4/search.html#chaining chained search parameter] for all resource types except Patient, so only the records associated with the authenticated patient are returned.<br /> <br /> When patient identification requires the use of search parameters, the following search parameters SHALL be supported:<br /> * Patient: {{fhir|identifier}}<br /> * MedicationRequest: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationDispense: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationStatement: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationAdministration: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> <br /> An example of a request that retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233:<br /> <br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> <br /> Note: All request examples in this document do not include patient identification mechanisms, partly because we want to generalize this technical design as much as possible (it being applicable to both MedMij and other contexts), and partly because this would convolute all search request examples. Requesters are assumed to include these if necessary. Since there currently are only transactions in the context of a single patient, the patient identification mechanism is actually implicitly assumed to be present in all search requests.<br /> <br /> == Resource identification ==<br /> 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}}.<br /> <br /> 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 &lt;code&gt;@root&lt;/code&gt; and &lt;code&gt;@extension&lt;/code&gt; (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.<br /> <br /> 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|release=V3.0.0}}}} 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]].<br /> <br /> == Differentiating between transactions ==<br /> All transactions described in this IG use the same medication building blocks in different combinations and settings, making it necessary to differentiate between them. Several mechanisms are used to achieve this. Aside from PUSH/PULL, the type of medication building blocks, supporting resources like List and Communication for specific transactions and fixing the value of specific FHIR elements in applicable profiles, the {{term|actionable}} tag is used. The latter is described more in depth in the following section. Next to that, a summarizing table is provided.<br /> <br /> Note that {{fhir|Resource.meta.profile}}, although present in each building block (see [[FHIR:V1.0_FHIR_IG_R4#Profile_use_and_declaration|the general FHIR IG on ‘Profile use and declaration’]]), SHOULD [https://hl7.org/fhir/r4/resource.html#profile-tags not be used for identification of the building block type] and therefore for differentiating between transactions.<br /> <br /> === Actionable tag ===<br /> To differentiate between sending or serving building blocks that are either of informative nature or of actionable nature, the {{term|actionable}} tag is used. [https://hl7.org/fhir/r4/resource.html#tag Tags] are {{datatype|Coding}} elements present in {{fhir|Resource.meta.tag}} used for workflow management.<br /> <br /> If applicable, the profiles used by a transaction require the use of {{fhir|.meta.tag}} with {{fhir|.system}} = {{term|&lt;nowiki&gt;http://terminology.hl7.org/CodeSystem/common-tags&lt;/nowiki&gt;}} and {{fhir|.code}} = {{term|actionable}} to indicate that the resource is part of a request intended to be acted upon. The absence of this tag indicates that the resource is merely of informative nature.<br /> <br /> It is up to systems to determine how and when the transactions using the {{term|actionable}} tag are handled from a functional perspective. Systems may store the resource including the {{term|actionable}} tag or remove it either upon storing or when the request is acted upon. However, systems SHALL make sure the tag is removed when serving or sending the resource as part of an informative transaction.<br /> <br /> === Summarizing table ===<br /> {| class=&quot;wikitable&quot; <br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | PUSH/PULL<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building blocks<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | {{term|actionable}} tag<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR element value<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Other<br /> |-<br /> | Medication data (Retrieve/Serve)<br /> | PULL<br /> | One or more of all building blocks<br /> | No<br /> |<br /> | <br /> |-<br /> | Medication data (Send/Receive)<br /> | PUSH<br /> | One or more of all building blocks<br /> | No<br /> |<br /> |<br /> |-<br /> | Medication overview (Retrieve/Serve)<br /> | PULL<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication overview (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication prescription (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, DispenseRequest (optional)<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|order}} (for both MedicationAgreement and DispenseRequest building blocks)<br /> | <br /> |-<br /> | Medication prescription processing (Send/Receive)<br /> | PUSH<br /> | AdministrationAgreement, MedicationDispense (optional)<br /> | Yes<br /> | <br /> | <br /> |-<br /> | Proposal dispense request (Send/Receive)<br /> | PUSH<br /> | DispenseRequest<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal dispense request (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to DispenseRequest<br /> |-<br /> | Proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to MedicationAgreement<br /> |}<br /> <br /> = Transactions =<br /> 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’.<br /> &lt;section begin=medmij1 /&gt;<br /> == Medication data (Retrieve/Serve) ==<br /> The retrieve medication data transaction is used by the client to retrieve medication data from a server. The client can retrieve its desired information by searching for specific medication building blocks.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.372_20220630000000 Medication data (PULL)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.373-2022-06-30T000000.html Retrieving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGR<br /> &lt;section end=medmij1 /&gt;<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Retrieve/serve medication data}}<br /> &lt;section begin=medmij2 /&gt;<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.374-2022-06-30T000000.html Serving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain all medication data or specific parts matching various parameters, they issue a retrieve medication data request message. This message uses the HTTP GET method parameterized query against the server's medication FHIR endpoints. These endpoints can be one of the following:<br /> * MedicationRequest<br /> * MedicationDispense<br /> * MedicationStatement<br /> * MedicationAdministration<br /> <br /> The search interaction is performed by an HTTP GET conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query. Multiple request messages may be needed to retrieve all desired information.<br /> <br /> &lt;pre&gt;GET [base]/[type]{?[parameters]}&lt;/pre&gt;<br /> <br /> ==== Search parameters ====<br /> All search parameters listed in the table below SHALL be supported for processing by servers and MAY be supported by clients.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | MP9 search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Description<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Example<br /> &lt;section end=medmij2 /&gt;<br /> |-<br /> | PatientIdentificationNumber<br /> | Search on patient.<br /> | {{fhir|patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;&gt;This search parameter only needs to be supported when patient identification requires the use of search parameters, see [[#Patient_identification|section 2.4]].&lt;/ref&gt;<br /> {{fhir|subject:Patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;/&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233.<br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> &lt;section begin=medmij3 /&gt;<br /> |-<br /> | Identification<br /> | Search on identifier.<br /> | {{fhir|identifier}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves a MedicationRequest resource with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?identifier=http://example.nl/fhir/NamingSystem/MedicationRequest|999922448&lt;/pre&gt;<br /> |-<br /> | Identification<br /> | Search on the pharmaceutical treatment identifier. <br /> Note: retrieval of all medication resources belonging to one pharmaceutical treatment requires to search on all medication resource types.<br /> | {{fhir|pharmaceutical-treatment-identifier}} &lt;ref name=&quot;custom-searchparameter&quot;&gt;The search parameter consists of a custom FHIR search parameter not represented in the FHIR specification. Note that for {{fhir|MedicationRequest.category}} and {{fhir|MedicationStatement.category}} a core search parameter is available, hence no custom one is needed in those cases.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that are part of a pharmaceutical treatment with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?pharmaceutical-treatment-identifier=http://example.nl/fhir/NamingSystem/pharmaceuticaltreatment|1247848&lt;/pre&gt;<br /> |-<br /> | rowspan=&quot;4&quot; | Type<br /> | rowspan=&quot;4&quot; | Search on type of medication building block. <br /> | rowspan=&quot;4&quot; | {{fhir|category}} &lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block DispenseRequest.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block VariableDosingRegimen.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&lt;/pre&gt;<br /> |-<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&lt;/pre&gt;<br /> Retrieves all MedicationDispense resources that represent the building block AdministrationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&lt;/pre&gt;<br /> |-<br /> | MedicationStatement<br /> | Retrieves all MedicationStatement resources that represent the building block MedicationUse2.<br /> &lt;pre&gt;GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&lt;/pre&gt;<br /> |-<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&lt;/pre&gt;<br /> |-<br /> | MedicationCode<br /> | Search on medication code.<br /> | {{fhir|medication.code}}&lt;ref&gt;[https://www.hl7.org/fhir/r4/search.html#chaining Chained search parameter]: searches the medicationReference required in each building block for its {{fhir|.code}}.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and have Carbasalaatcalcium Sandoz 600 30 as medication.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&lt;/pre&gt;<br /> |-<br /> | PeriodOfUse<br /> | 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.<br /> Whenever a search is done on the MedicationAgreement, VariableDosingRegimen or AdministrationAgreement building blocks it is required to also include the latest stopped building blocks of that kind within each pharmaceutical treatment, even if these have a period of use outside the PeriodOfUse that is being searched on.<br /> | {{fhir|period-of-use}}&lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement&lt;ref&gt;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.&lt;/ref&gt;<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and were in effect from 01-01-2010.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;period-of-use=ge2010-01-01&lt;/pre&gt;<br /> |-<br /> | DispensePeriod <br /> | Returns all medication dispenses within the specified time period.<br /> | {{fhir|whenhandedover}}<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense and were handed over within a 2 year period.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;whenhandedover=ge2010-01-01&amp;whenhandedover=le2011-12-31&lt;/pre&gt;<br /> |-<br /> | AdministrationPeriod <br /> | Returns all medication administrations within the specified time period.<br /> | {{fhir|effective-time}}<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2 and where administration happened on a specific day.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;effective-time=eq2022-01-01&lt;/pre&gt;<br /> |-<br /> | -<br /> | The client may request that the server returns resources related to the search results, in order to reduce the overall network delay of repeated retrievals of related resources.<br /> Supporting the include of the Patient and Medication resources referenced by building blocks is required. Others (Organization, Location, PractitionerRole, Practitioner, RelatedPerson, Observation) are optional. However: all resources referenced per literal reference SHALL be resolvable [[FHIR:V1.0_FHIR_IG_R4#Including_referenced_resources|per the Nictiz IG]].<br /> | {{fhir|&lt;nowiki&gt;_include=[type]:patient&lt;/nowiki&gt;}}<br /> {{fhir|&lt;nowiki&gt;_include=[type]:medication&lt;/nowiki&gt;}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that have Carbasalaatcalcium Sandoz 600 30 as medication and includes the Medication resource in the search results.<br /> &lt;pre&gt;GET [base]/MedicationRequest?medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&amp;_include=MedicationRequest:medication&lt;/pre&gt;<br /> |}<br /> <br /> The following custom search parameters are defined for this transaction:<br /> <br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/pharmaceutical-treatment-identifier|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/category|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/period-of-use|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> <br /> ==== Retrieve all medication data ====<br /> To retrieve all known medication data, a client has to execute the following requests to retrieve all known medication data per building block, including referenced Medication resources:<br /> <br /> &lt;pre&gt;<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&amp;_include=MedicationStatement:medication<br /> GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;_include=MedicationStatement:medication<br /> &lt;/pre&gt;<br /> <br /> Note that in this transaction, these search requests are always executed in the context of a single patient and thus should include a patient identification mechanism (see [[#Patient_identification|‘Patient identification’]]).<br /> <br /> === Serve (response message) ===<br /> The server returns an HTTP Status code appropriate to the processing outcome and returns a Bundle, with {{fhir|Bundle.type}} = {{term|searchset}}, including the resources matching the search query medication data. The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> &lt;section end=medmij3 /&gt;<br /> == Medication data (Send/Receive) ==<br /> The send medication data transaction is used by the client to send medication data to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.375_20220630000000 Medication data (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.376-2022-06-30T000000.html Sending medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication data}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication data<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because medication data consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below. Because of the informative nature of the transaction, '''no''' [[#Actionable_tag|{{term|actionable}} tags]] shall be present.<br /> <br /> === Receive (response message) ===<br /> The server checks each resource present within the Bundle it receives for the absence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication overview (Retrieve/Serve) ==<br /> The retrieve medication overview transaction is used by the client to retrieve a medication overview from the server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.388_20220630000000 Medication overview (PULL)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.389-2022-06-30T000000.html Retrieving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOR<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Retrieve/serve medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.390-2022-06-30T000000.html Serving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain a patient's medication overview, they issue a retrieve medication overview request message. This message uses an extended operation on the RESTful API to obtain a medication overview from a server. An operation is needed because the server will formulate the content of the response based on its internal business logic. The medication overview can not easily be described by standardized RESTful requests. <br /> <br /> The client executes a {{Simplifier|http://nictiz.nl/fhir/OperationDefinition/Medication-Overview|nictiz.fhir.nl.r4.medicationprocess9|title=medication-overview operation}} with an HTTP GET command conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query.<br /> <br /> &lt;pre&gt;<br /> GET [base]/$medication-overview<br /> &lt;/pre&gt;<br /> <br /> === Serve (response message) ===<br /> 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.<br /> <br /> 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].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication overview (Send/Receive) ==<br /> The send medication overview transaction is used by the client to send a medication overview to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.391_20220630000000 Medication overview (PUSH)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.392-2022-06-30T000000.html Sending medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication overview<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication overview consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> 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.<br /> <br /> 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].<br /> <br /> === Receive (response message) ===<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication prescription (Send/Receive) ==<br /> The send medication prescription transaction is used by the client to send a request to dispense medication (Dutch: verstrekkingsverzoek) or process modifications to a medication agreement (Dutch: medicatieafspraak) to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.141-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.394_20220630000000 Medication prescription (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.395-2022-06-30T000000.html Sending medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescription|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication prescription}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescription-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}) and optionally a DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below<br /> <br /> The mp-MedicationPrescription-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the MedicationAgreement and DispenseRequest building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|order}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Medication_prescription_processing_.28Send.2FReceive.29|‘Send medication prescription processing’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication prescription processing (Send/Receive) ==<br /> The send medication prescription processing transaction is used by the client to send data on the processing of a medication agreement (Dutch: medicatieafspraak) and possibly a dispense request (Dutch: verstrekkingsverzoek), in the form of an administration agreement (Dutch: toedieningsafspraak) and optionally a medication dispense (Dutch: medicatieverstrekking).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.143-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.406_20220630000000 Medication prescription processing (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.407-2022-06-30T000000.html Sending data on processing of medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescriptionProcessing|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication prescription processing}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving data on processing of medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because data on processing a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescriptionProcessing-Bundle profile, which contains at least an AdministrationAgreement building block and optionally a MedicationDispense building block. Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-MedicationPrescriptionProcessing-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the AdministrationAgreement and MedicationDispense building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Proposal dispense request (Send/Receive) ==<br /> The send proposal dispense request transaction is used by the client to inform the server about a new or modified proposal dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.400_20220630000000 Proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.401-2022-06-30T000000.html Sending proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal dispense request consists of a DispenseRequest building block along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalDispenseRequest-Bundle profile, which contains one DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalDispenseRequest-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the DispenseRequest building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_dispense_request_.28Send.2FReceive.29|‘Send reply proposal dispense request’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Reply proposal dispense request (Send/Receive) ==<br /> The send reply proposal dispense request transaction is used by the client to inform the server about a reply on a proposed dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.403_20220630000000 Reply proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.404-2022-06-30T000000.html Sending reply proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive reply proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal dispense request consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalDispenseRequest-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalDispenseRequest profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed dispense request that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalDispenseRequest-Bundle profile).<br /> <br /> The mp-ReplyProposalDispenseRequest profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Proposal medication agreement (Send/Receive) ==<br /> The send proposal medication agreement transaction is used by the client to inform the server about a new or modified proposal medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.397_20220630000000 Proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.398-2022-06-30T000000.html Sending proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal medication agreement consists of a MedicationAgreement building block along with supporting resources, a {{term|transaction}} interaction is used.<br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalMedicationAgreement-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalMedicationAgreement-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the MedicationAgreement building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_medication_agreement_.28Send.2FReceive.29|‘Send reply proposal medication agreement’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Reply proposal medication agreement (Send/Receive) ==<br /> The send reply proposal medication agreement transaction is used by the client to inform the server about a reply on a proposed medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.445_20220630000000 Reply proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.446-2022-06-30T000000.html Sending reply proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive reply proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal medication agreement consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalMedicationAgreement-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalMedicationAgreement profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed medication agreement that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalMedicationAgreement-Bundle profile).<br /> <br /> The mp-ReplyProposalMedicationAgreement profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> =Release notes=<br /> Release notes can be found [[mp:V3.0.0-beta.3_releasenotes|here]].<br /> <br /> =Footnotes=<br /> &lt;references/&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=mp:Medicatieoverdracht_Kickstart&diff=206725 2024-03-07T12:31:38Z

<p>Luud Slagter: /* Specificaties */</p> <hr /> <div>{{DISPLAYTITLE:Kickstart Medicatieoverdracht - Landingspagina documentatie leveranciers (Handboek)}}<br /> <br /> __NUMBEREDHEADINGS__<br /> =ALGEMEEN REFERENTIE=<br /> :*[https://www.zorginzicht.nl/binaries/content/assets/zorginzicht/kwaliteitsinstrumenten/Kwaliteitsstandaard+Overdracht+van+medicatiegegevens+in+de+keten.pdf Kwaliteitsstandaard: richtlijn overdracht van medicatiegegevens in de keten]&lt;br&gt;<br /> <br /> =BOUWDOCUMENTATIE=<br /> {{IssueBox|'''FHIR specs voor versie 3.0.0-beta.3 volgen op 7 maart'''}}<br /> ==Voorbereiding==<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/pva_kickstart/&lt;abbr title=&quot;Het Plan van aanpak versie 3.1 voor de uitvoering van de Kickstart. Het Plan van aanpak versie 3.1 beschrijft het doel, de opzet, aanpak en kaders voor de uitvoering van de Kickstart.&quot;&gt;Plan van aanpak versie 3.1&lt;/abbr&gt;]<br /> <br /> ==Specificaties==<br /> :'''Verzamelbestand informatiestandaarden'''<br /> :*[[mp:V2.0.0_Verwijzing_naar_documentatie_Medicatieproces9_tbv_Kickstart|Verzamelbestand met functionele, technische en infrastructurele documentatie Medicatieproces 9 t.b.v. Kickstart]]<br /> <br /> :'''Voorbereiding'''<br /> :*[[mp:Stap_0_Voorbereiding|Werkzaamheden in stap 0 Voorbereiding]]<br /> <br /> :'''Informatiestandaard Medicatieproces 9 versie 3.0.0-beta.3'''<br /> :*[[mp:V3.0.0-beta_Ontwerp_medicatieproces_9|&lt;abbr title=&quot;Het functioneel ontwerp van de informatiestandaard Medicatieproces 9 Het beschrijft de algemene werking en specifieke praktijksituaties.&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 3.0.0-beta.3 (NL)&lt;/abbr&gt;]] / [[mp:V3.0.0-beta_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 3.0.0-beta.3 (ENG)]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.<br /> &quot;&gt;Medicatieproces 9 versie 3.0.0-beta.3 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> :*[[mp:V3.0.0_MedicationProcess9_FHIR|&lt;abbr title=&quot;FHIR Implementation guide for Medicatieproces 9 versie 3.0.0-beta.3 FHIR in English&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.3 (ENG) &lt;/abbr&gt;]]<br /> :*[https://simplifier.net/packages/nictiz.fhir.nl.r4.medicationprocess9/2.0.0-beta.1/ FHIR R4 conformance resources for Medication Process 9 (MP9)]<br /> :*[[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|&lt;abbr title=&quot;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.3 voor patiënt usecases&quot;&gt;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.3 voor patiënt usecases&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.3 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.3 for patient use cases (ENG) &lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.3_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 3.0.0-beta.3&lt;/abbr&gt;]]<br /> :*Gebruikerseisen: [[mp:Besluiten_kernteams|&lt;abbr title=&quot;Deze pagina bevat de besluiten van de kernteams, met (indien van toepassing) de bijbehorende werkproceseisen, gebruikerseisen en -wensen.&quot;&gt;Besluiten kernteams Medicatieproces 9, inclusief gebruikerseisen en -wensen&lt;/abbr&gt;]]<br /> <br /> :'''Informatiestandaard Lab2zorg'''<br /> :*[[mp:LeeswijzerVoorschriftmetnierfunctiewaarde|&lt;abbr title=&quot;De leeswijzer geeft aan welk onderdeel van Lab2zorg binnen de scope van de Kickstart valt en welke documentatie daarop van toepassing is.&quot;&gt;Leeswijzer ten behoeve van het meesturen van de nierfunctiewaarde met het voorschrift&lt;/abbr&gt;]]<br /> :*[[Lab:Vcurrent_Ontwerp_Lab2zorg|&lt;abbr title=&quot;Het functioneel ontwerp van Lab2zorg. In de kickstart wordt het onderdeel lab2zorg gebruikt voor het meesturen van een nierfunctiewaarde met het voorschrift. Deze usecase staat beschreven in paragraaf 2.3 van het functioneel ontwerp lab2zorg.&quot;&gt;Functioneel ontwerp Lab2zorg versie 3.0.0&lt;/abbr&gt;]]<br /> :*[[Lab:Vcurrent_Kwalificatie|&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard uitwisseling laboratoriumgegevens de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties. Voor de kickstart wordt sturen/ontvangen laboratoriumresultaten uit lab2zorg gebruikt.&quot;&gt;Labuitwisseling versie 3.0.0 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]]<br /> :*[[Lab:V3.0.0_FHIR_Lab2zorg|&lt;abbr title=&quot;Technische FHIR specificaties van Lab2zorg in aanvulling op het functioneel ontwerp. Paragraaf 4.3 beschrijft het sturen van laboratoriumresultaten tussen zorgverleners dat in de kickstart gebruikt wordt.&quot;&gt;FHIR Lab2zorg version 3.0.0 (ENG)&lt;/abbr&gt;]]<br /> <br /> :'''Infrastructuur'''<br /> :*[https://decor.nictiz.nl/pub/vzvz/index.php?prefix=mp-vzvz-&lt;abbr title=&quot;&quot;&gt;ART-DECOR Publicatiepagina VZVZ: Medicatieproces op het LSP&lt;/abbr&gt;]<br /> :*[https://zt-medicatieoverdracht.scrollhelp.site/Medicatieoverdracht/Working-version/programma-van-eisen-medicatieoverdracht&lt;abbr title=&quot;De beschikbare Programma van Eisen waaraan de Kickstart deelnemers moeten voldoen. Deze documenten beschrijven de eisen om aan te sluiten op de AORTA-infrastructuur.&quot;&gt;Programma van eisen LSP (bèta)&lt;/abbr&gt;]<br /> :*[https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpublicvzvz.refined.site%2Fspace%2FA8%2F85000200%2FAORTA%2B8.3.0&amp;data=05%7C01%7Ctheunissen%40nictiz.nl%7C52a3bf5378624ff2978e08db8f44c3a3%7C3d542e8da3eb448f998ddd6880dc119c%7C0%7C0%7C638261297740578594%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=6%2FH9yQ0EAHEmGYHgbVoQo995poc34CXlV6UcBP4MSD8%3D&amp;reserved=0&lt;abbr title=&quot;Deze pagina bevat de algemene specificaties van de zorginfrastructuur AORTA v8.3.0.0&quot;&gt;Documentatie AORTA versie 8.3.0.0&lt;/abbr&gt;]<br /> <br /> ==IT-Infrastructuur==<br /> :*[https://decor.nictiz.nl/pub/vzvz/aorta-vzvz-html-20221128T172039/sc-2.16.840.1.113883.2.4.3.111.3.2.3.3-2016-09-20T163842.html Implementatie van de ping-pong toets]<br /> :*[https://decor.nictiz.nl/pub/vzvz/aorta-vzvz-html-20221128T172039/sc-2.16.840.1.113883.2.4.3.111.3.2.3.1-2016-09-20T091642.html Beheren TKID applicatie]<br /> :*[https://public.vzvz.nl/download/attachments/41779447/AORTA_Proces_VWI_Synchronisatie.pdf?api=v2:~:text=Het%20VWI%2Dsynchronisatie%20proces%20biedt,belang%20van%20pati%C3%ABnt%20en%20zorgaanbieder&lt;abbr title=&quot;Dit document beschrijft de procedure die ervoor zorgt dat elke GBZ-beheerder namens de zorgaanbieder kan vaststellen dat elk patiëntgegeven met toestemming van de patiënt op correcte wijze is aangemeld op de VWI.&quot;&gt;Proces VWI synchronisatie&lt;/abbr&gt;]<br /> :*[https://public.vzvz.nl/download/attachments/41779447/AORTA_Sgl_Ontw_Gebeurtenisverwerking.pdf?api=v2&lt;abbr title=&quot;Dit document beschrijft het ontwerp van de gebeurtenisverdeler component (GVE) en de component gebeurtenisafhandelaar (GAF) in de ZIM.&quot;&gt;Ontwerp gebeurtenisverwerking&lt;/abbr&gt;]<br /> :*[https://public.vzvz.nl/download/attachments/41779447/AORTA_Sgl_Ontw_Abonnementenregister.pdf?api=v2&lt;abbr title=&quot;Dit document beschrijft het ontwerp van de abonnementenregister component (ABR) in de ZIM.&quot;&gt;Ontwerp abonnementenregister&lt;/abbr&gt;]<br /> <br /> ==Implementatiehandleidingen==<br /> :*[[mp:Vkickstart_MigratieHybride|&lt;abbr title=&quot;Handleiding Migratie hybride fase Kickstart&quot;&gt;Implementatiehandleiding Migratie/hybride&lt;/abbr&gt;]]<br /> :*[[mp:Implementatiehandleiding_Consolidatie/afleidingsregels|&lt;abbr title=&quot;Handleiding Consolidatie/afleidingsregels Kickstart&quot;&gt;Implementatiehandleiding Consolidatie/afleidingsregels&lt;/abbr&gt;]]<br /> :*[https://www.aorta-lsp.nl/media/downloads/implementatiehandleiding-verwijsindex-aorta-v8200pdf/download&lt;abbr title=&quot;Implementatiehandleiding verwijsindex AORTA v8.2.0.0&quot;&gt;Implementatiehandleiding VWI AORTA&lt;/abbr&gt;]<br /> :*[https://www.vzvz.nl/media/downloads/zorg-ab-implementatiehandleiding-v27pdf/download&lt;abbr title=Dit document bevat informatie, instructies en voorbeelden ten behoeve van de implementatie van<br /> (applicaties/systemen die gebruik maken van) de web API's van ZORG-AB.&gt;Implementatiehandleiding ZORG-AB&lt;/abbr&gt;]<br /> :*[https://www.aorta-lsp.nl/media/downloads/implementatiehandleiding-inschrijftoken-aorta-v8200pdf/download&lt;abbr title=&quot;Handleiding voor de implementatie van het koppelvlak tussen het goed beheerde Zorgsystemen (GBZ) en het landelijk schakelpunt (LSP).&quot;&gt;Implementatie handleiding inschrijftoken&lt;/abbr&gt;]<br /> :*[https://www.aorta-lsp.nl/media/downloads/implementatiehandleiding-mandaattoken-aorta-v8200pdf/download&lt;abbr title=&quot;Specificatie van het mandaattoken.&quot;&gt;Implementatie handleiding mandaattoken&lt;/abbr&gt;]<br /> :*[https://www.aorta-lsp.nl/media/downloads/implementatiehandleiding-berichtauthenticatie-transactietoken-aorta-v8200pdf/download&lt;abbr title=&quot;Handleiding voor het uitrusten van de berichten met het SAML transactietoken.&quot;&gt;Implementatie handleiding transactiekosten&lt;/abbr&gt;]<br /> <br /> ==Ondersteunende materialen==<br /> :*[[mp:V3.0_Voorbeelden_doseringen|&lt;abbr title=&quot;Uitgewerkte voorbeelden voor het concept 'Gebruiksinstructie' uit de dataset van de Informatiestandaard Medicatieproces 9&quot;&gt;Voorbeelden doseringen&lt;/abbr&gt;]]<br /> :*[[mp:V9_2.0.0_HL7v3CDA_FHIRTiming|&lt;abbr title=&quot;Toedieningsschema HL7v3-template. Introductie van het FHIR timing datatype in CDA substanceAdministration.effectiveTime voor toedieningsschema's. Voorheen was dit de HL7v3 GTS (General Timing Specification). Bevat ook de inhoudelijke wijziging in de XML schema's (xsd's).&quot;&gt;Dosering in FHIR&lt;/abbr&gt;]]<br /> :*[https://github.com/Nictiz/Medicatieviewer&lt;abbr title=&quot;De Medicatieviewer transformeert een MP-9 XML volgens de standaard medicatieproces 9 voor medicatiegegevens of voor medicatieoverzicht in HTML om zo een voor mensen leesbaar overzicht te geven van de inhoud van de XML.&quot;&gt;Medicatieviewer&lt;/abbr&gt;]<br /> :*[https://informatiestandaarden.nictiz.nl/images/c/c9/Medicatieoverzicht_MP90.zip&lt;abbr title=&quot;Uitklapbaar Medicatieoverzicht voorbeeld in HTML-formaat.&quot;&gt;Medicatieoverzicht HTML voorbeeld&lt;/abbr&gt;]<br /> :*[[Mappingarchitectuur#Mappings_en_transacties|&lt;abbr title=&quot;Deze sectie toont verschillende mappings voor transacties uit verschillende informatiestandaarden.&quot;&gt;Mappingarchitectuur&lt;/abbr&gt;]]<br /> :*[[mp:Vdraft_RaadplegenReconcilieren|&lt;abbr title=&quot;Deze pagina bevat nadere toelichting over hoe te reconciliëren na raadplegen. Het bespreekt de volgorde van verwerken van de verschillende soorten binnengekomen informatie.&quot;&gt;Implementatie handleiding Raadplegen Reconciliëren&lt;/abbr&gt;]]<br /> :*[[7phcy:V09_HL7v3-domeinspecificatie_Pharmacy|&lt;abbr title=&quot;Deze pagina geeft nadere toelichting bij templates in ART-DECOR.&quot;&gt;Toelichting bericht templates Medicatieproces versie 9&lt;/abbr&gt;]]<br /> :*[https://www.aorta-lsp.nl/media/downloads/best-practices-vwi-synchronisatie-aorta-v8200pdf/download/&lt;abbr title=&quot;Ter verduidelijking van de implementatiehandleiding VWI. Extra informatie wordt gegeven over de afhandeling van berichten aan de XIS leveranciers en de beheerders om duidelijkheid te geven over de verwachte acties.&quot;&gt;Best practices: VWI synchronisatie &lt;/abbr&gt;]<br /> :*[https://www.aorta-lsp.nl/media/downloads/factsheet-tkidspdf/download/&lt;abbr title=&quot;Deze factsheet beschrijft de werking van TypeKwalificatie-ID’s (TKID’s) op het LSP.&quot;&gt;Factsheet tkid&lt;/abbr&gt;]<br /> :*[https://www.vzvz.nl/diensten/gemeenschappelijke-diensten/zorg-ab&lt;abbr title=&quot;Deze pagina bevat de algemene informatie omtrent Zorg-AG.&quot;&gt;Algemene informatie Zorg-AB&lt;/abbr&gt;]<br /> :*[https://www.vzvz.nl/diensten/gemeenschappelijke-diensten/zorg-id&lt;abbr title=&quot;Deze pagina bevat de algemene informatie omtrent Zorg-ID.&quot;&gt;Algemene informatie Zorg-ID&lt;/abbr&gt;]<br /> <br /> =TEST- EN VALIDATIEMATERIAAL=<br /> ==Testinformatie Kickstart==<br /> :*[[mp:Testen_Kickstart|Testen Kickstart]]<br /> <br /> ==Testscripts==<br /> {{IssueBox|'''De aanpassingen op de testscripts door de release van versie 3.0.0-beta.3 worden op dit moment doorgevoerd'''}}<br /> :'''Medicatieproces 9'''<br /> :*[[mp:Vcurrent_Kwalificatie#Medicatieproces_9_versie_3.0.0-beta.2_testmateriaal_en_kwalificatiescripts_voor_Kickstart|Testscripts Medicatieproces 9 versie 3.0.0-beta.2]]<br /> <br /> :'''Testscript gebruikerseisen boven sectoraal'''<br /> :*[https://informatiestandaarden.nictiz.nl/wiki/Bestand:Use_case_scenario%27s_en_testscripts_GERRIT_-_Pati%C3%ABnt_1tm4_-_stap_3-4_-_beta_versie_3.0_.pdf Use case scenario's en testscripts GERRIT - Patiënt 1tm4 - stap 3-4 - beta versie 3.0&lt;/abbr&gt;]<br /> :*[https://informatiestandaarden.nictiz.nl/wiki/Bestand:Use_case_scenario%27s_en_testscripts_Rijnmond_-_pati%C3%ABnt_1-4_-_stap_3-4_-_beta_versie_3.0_(1).pdf Use case scenario's en testscripts Rijnmond - patiënt 1-4 - stap 3-4 - beta versie 3.0&lt;/abbr&gt;]<br /> <br /> :'''Lab2zorg'''<br /> :*[[Lab:Vcurrent_Kwalificatie#Lab2zorg|&lt;abbr title=&quot;Testgegevens die als voorbereiding op de kwalificatie gebruikt kunnen worden, waarbij voor de kickstart alleen de scripts Laboratoriumresultaten (Sturen/Ontvangen) relevant zijn.&quot;&gt;Testscripts Lab2zorg versie 3.0.0&lt;/abbr&gt;]]<br /> :'''Algemene eisen MP9 &amp; Generieke voorzieningen'''<br /> :*[https://informatiestandaarden.nictiz.nl/images/5/5e/Testscripts_algemene_eisen_MP9_%26_Generieke_voorzieningen.zip Testscripts algemene eisen MP9 &amp; Generieke voorzieningen (zip bestand)]<br /> <br /> ==Validatiescripts==<br /> :*Kwalificatiescripts worden definitief opgeleverd als bekend is op welke versie gevalideerd wordt in de Kickstart.<br /> :*Acceptatiescripts worden gegenereerd op het moment dat de leverancier zich meldt; dit betreft maatwerk.<br /> <br /> =TOOLING=<br /> :*[https://informatiestandaarden.nictiz.nl/images/3/30/Tooling.pdf&lt;abbr title=&quot;Overzicht van de te gebruiken tooling.&quot;&gt;Beschikbare tooling&lt;/abbr&gt;]<br /> <br /> ==ART-DECOR==<br /> :*[https://decor.nictiz.nl/art-decor/home&lt;abbr title=&quot;Inlogpagina ART-DECOR&quot;&gt;Inloggen ART-DECOR&lt;/abbr&gt;]<br /> :*[[HL7v3 kwalificatiesimulator|&lt;abbr title=&quot;Uitleg over inloggen en gebruik van de kwalificatiesimulator (ART-DECOR)&quot;&gt;Testen met ART-DECOR / Kwalificatiesimulator&lt;/abbr&gt;]]<br /> :*[https://art-decor.org/mediawiki/index.php?title=Documentation&lt;abbr title=&quot;Handleidingen en documentatie van ART-DECOR &quot;&gt;ART-DECOR documentatie&lt;/abbr&gt;]<br /> :*[[7phcy:V2.0_Toelichting_samenhang_Wiki_en_ART-DECOR|&lt;abbr title=&quot;Deze toelichting beschrijft de samenhang tussen: de HL7v3-implementatiehandleiding Medicatieproces 9 wiki en de bijbehorende html-publicatie van ART-DECOR.&quot;&gt;Wiki &amp; ART-DECOR&lt;/abbr&gt;]]<br /> <br /> ==BITS==<br /> :*[https://bits.nictiz.nl/ Link naar BITS algemeen]<br /> :*[https://bits.nictiz.nl/projects/MP/issues/ Link naar openstaande issues Medicatieproces in BITS]<br /> :*[https://informatiestandaarden.nictiz.nl/images/8/87/Handleiding_BITS_voor_leveranciers.pdf Handleiding BITS validatieloket]<br /> <br /> ==Touchstone==<br /> :*[https://touchstone.aegis.net/touchstone/login&lt;abbr title=&quot;Inlogpagina Touchstone&quot;&gt;Inloggen Touchstone&lt;/abbr&gt;]<br /> :*[[mp:Vcurrent_Kwalificatie#Touchstone|Testen met Touchstone]]<br /> <br /> ==ZORG-AB==<br /> :*[https://zorg-ab-oas.vzvz.nl/&lt;abbr title=&quot;Testapplicatie Zorg-AB&quot;&gt;ZORG-AB testapplicatie&lt;/abbr&gt;]<br /> :*[https://www.vzvz.nl/diensten/gemeenschappelijke-diensten/zorg-ab&lt;abbr title=&quot;Deze pagina bevat informatie, instructies en voorbeelden ten behoeve van de implementatie van<br /> (applicaties/systemen die gebruik maken van) de web API's van ZORG-AB.&quot;&gt;Implementatie handleiding ZORG-AB&lt;/abbr&gt;]<br /> <br /> =INFORMATIEVOORZIENING=<br /> <br /> ==Vragen en antwoorden==<br /> :*[[mp:Medicatieoverdracht_Kickstart_Vragen|Vragen en antwoorden uit vragenuur op vrijdagen]]<br /> <br /> ==Kennissessie==<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/luistersessie-introductiesessie-medicatieproces/ &lt;abbr title=&quot;In deze kennissessie wordt een introductie gegeven van het programma Medicatieoverdracht, de richtlijn Overdracht van medicatiegegevens in de keten, de informatiestandaard Medicatieproces 9&quot;&gt;Kennissessie: Introductie Medicatieoverdracht&lt;/abbr&gt;]<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/kennissessie-wat-kan-ik-verwachten-van-medicatieoverdracht/ &lt;abbr title=&quot;In deze kennissessie wordt inzicht gegeven in de meerwaarde van het programma Medicatieoverdracht voor de zorgverlener en patiënt en de te nemen acties op procesniveau. Per rol (voorschrijver, apotheker, toediener en patiënt) worden de stappen die worden beproefd in de Kickstart toegelicht.&quot;&gt;Kennissessie: Wat kan ik verwachten van Medicatieoverdracht&lt;/abbr&gt;]<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/kennissessie-verdieping-medicatieoverdracht/ &lt;abbr title=&quot;Deze kennissessie is voor iedereen die meer wil weten over het medicatieproces: welke gegevensuitwisselingsmomenten zijn er (transacties), welke rollen horen daarbij, hoe werken de bouwsteen relaties precies etc.&quot;&gt;Kennissessie: Verdieping Medicatieoverdracht&lt;/abbr&gt;]<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/luistersessie-voorgenomen-besluiten-kernteam-medicatie// &lt;abbr title=&quot;Deze kennissessie geeft een beeld van hoe samen met zorgverleners uit de 10 betrokken sectoren afspraken tot stand zijn gekomen t.a.v. beleid, verantwoordelijkheden, zorgprocessen, eenheid van taal in terminologie en codestelsels om de implementatie van de richtlijn en informatiestandaard te ondersteunen. &quot;&gt;Kennissessie: (Voorgenomen) besluiten kernteam Medicatie&lt;/abbr&gt;]<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/luistersessies/&lt;abbr title=&quot;In deze kennissessie wordt de route van de bèta publicatie van de informatiestandaard Medicatieproces 9 naar de definitieve versie toegelicht. &quot;&gt;Kennissessie: Route Medicatieproces 9 v2.0.0 bèta naar definitief&lt;/abbr&gt;]<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/luistersessie-testmaterialen-medicatieproces-9-2-0-0-beta/ &lt;abbr title=&quot;In deze kennissessie worden de testmaterialen voor Medicatieproces 9 toegelicht. Wat kan er getest worden, wat is de samenhang tussen de materialen, inhoud van het materiaal, hoe te gebruiken en waar te vinden. &quot;&gt;Kennissessie: Testmaterialen Medicatieproces 9 v2.0.0 bèta&lt;/abbr&gt;]<br /> :*[https://informatiestandaarden.nictiz.nl/images/d/d2/202202_Introductie_AORTA_-_nieuwe_style.pdf &lt;abbr title=&quot;Introductiepresentatie AORTA. Een introductie van infrastructurele AORTA architectuur​, verschillende architectuurlagen​, verschillende componenten​.<br /> Relaties met andere stelsels en producten​.&quot;&gt;Presentatie: Introductie AORTA&lt;/abbr&gt;]<br /> <br /> ==PGO==<br /> :*[https://informatiestandaarden.nictiz.nl/images/6/61/PGOsessiesMedicatieproces_BijlageBijOnlineSessie.pdf &lt;abbr title=&quot;Deze kennissessie geeft een introductie van MedMij in relatie tot Medicatieproces 9.&quot;&gt;Presentatie: Medicatieoverdracht uitleg MedMij&lt;/abbr&gt;]<br /> :*[https://informatiestandaarden.nictiz.nl/images/2/29/PGOsessie_OpnameOnline.mp4 &lt;abbr title=&quot;Opname van de kennissessie: Een introductie van MedMij in relatie tot het Medicatieproces 9.&quot;&gt;Opname: Medicatieoverdracht uitleg presentatie MedMij&lt;/abbr&gt;]<br /> <br /> =MEMO'S=<br /> <br /> ==Informatieve memo's==<br /> :*[https://informatiestandaarden.nictiz.nl/images/7/79/MO_memo_MBH-ID_Transformatiedienst_20230315.pdf&lt;abbr title=&quot;Memo MBH-ID Transformatiedienst_20230315&quot;&gt;Memo MBH-ID Transformatiedienst 15-03-2023&lt;/abbr&gt;]<br /> :*[https://informatiestandaarden.nictiz.nl/images/4/48/MO_memo_vooraankondiging_20230307.pdf&lt;abbr title=&quot;Memo vooraankondiging_20230307&quot;&gt;Memo vooraankondiging 07-03-2023&lt;/abbr&gt;]<br /> <br /> =IN ONTWIKKELING=<br /> :'''Transitie naar Medicatieproces 9 (migratie en hybride situatie)'''<br /> :*[[Vdraft_Mappingarchitectuur#Medicatieproces_.28MP.29_Versie_MP9_2.0_en_versie_9.0.7|&lt;font color=&quot;BBB7B6&quot;&gt;Mappingarchitectuur met mappings MP 9.0.7 &lt;-&gt; MP9 2.0.0&lt;/font&gt;]]<br /> <br /> :'''Kickstart testen'''<br /> :*[[mp:Draft_Testtooling#BITS|&lt;font color=&quot;BBB7B6&quot;&gt;Tooling &amp; omgevingen Kickstart Medicatieoverdracht&lt;/font&gt;]]<br /> <br /> =ARCHIEF=<br /> :*[https://informatiestandaarden.nictiz.nl/images/4/42/Nulpunt_documentatie_Kickstart_contract_leveranciers_versie11_20220907.pdf&lt;abbr title=&quot;Document dat nulpunt beschrijft voor specificaties Kickstart ten behoeve van contract.&quot;&gt;Nulpunt documentatie Kickstart leveranciers versie 1.1 van 7 september 2022&lt;/abbr&gt;]<br /> :* Verzamelbestand in Excel met functionele, technische en infrastructurele documentatie Medicatieproces 9 t.b.v. Kickstart (niet meer te downloaden om verwarring te voorkomen)<br /> :*[https://www.aorta-lsp.nl/voor-wie/ict-leveranciers/aorta-documentatie/infrastructuur-aorta-v8200&lt;abbr title=&quot;Deze pagina bevat de algemene specificaties van de zorginfrastructuur AORTA v8.2.0.0&quot;&gt;Documentatie AORTA 8.2.0.0&lt;/abbr&gt;]<br /> <br /> :'''Informatiestandaard Medicatieproces 9.3.0.0-beta.2'''<br /> :*[[mp:V3.0.0-beta.2_Ontwerp_medicatieproces_9|&lt;abbr title=&quot;Het functioneel ontwerp van de informatiestandaard Medicatieproces 9 Het beschrijft de algemene werking en specifieke praktijksituaties.&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 3.0.0-beta.2 (NL)&lt;/abbr&gt;]] / [[mp:V3.0.0-beta.2_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 3.0.0-beta.2 (ENG)]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/index.html&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.&quot;&gt;Medicatieproces 9 versie 3.0.0-beta.2 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> :*[[mp:V3.0.0-beta.2_MedicationProcess9_FHIR|&lt;abbr title=&quot;FHIR Implementation guide for Medicatieproces 9 versie 3.0.0-beta.2 FHIR in English&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 (ENG) &lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|&lt;abbr title=&quot;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.2 voor patiënt usecases&quot;&gt;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.2 voor patiënt usecases&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.2_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases (ENG)&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.2_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 3.0.0-beta.2&lt;/abbr&gt;]]<br /> <br /> :'''Informatiestandaard Medicatieproces 9.3.0.0-beta.1'''<br /> :*[[mp:V3.0.0-beta.1_Ontwerp_medicatieproces_9|Functioneel ontwerp Medicatieproces 9 versie 3.0.0-beta.1 (NL)]] / [[mp:V3.0.0-beta.1_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 3.0.0-beta.1 (ENG)]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20230217T123829/index.html&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.&quot;&gt;Medicatieproces 9 versie 3.0.0-beta.1 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> :*[[mp:V3.0.0-beta.1_MedicationProcess9_FHIR|&lt;abbr title=&quot;FHIR Implementation guide for Medicatieproces 9 versie 3.0.0-beta.1 FHIR in English&quot;&gt;Implementation guide FHIR Medication Process 9 version 3.0.0-beta.1 (ENG)&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.1_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.1 for patient use cases (ENG)&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.1_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 3.0.0-beta.1&lt;/abbr&gt;]]<br /> <br /> :'''Informatiestandaard Medicatieproces 9.2.0.0'''<br /> :*[[mp:V2.0.0_Ontwerp_medicatieproces_9|&lt;abbr title=&quot;Het functioneel ontwerp van de informatiestandaard Medicatieproces 9. Het beschrijft de algemene werking en specifieke praktijksituaties.&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 2.0.0 (NL)&lt;/abbr&gt;]] / [[mp:V2.0.0_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 2.0.0 (ENG)]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20220402T205710/index.html&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.<br /> &quot;&gt;Medicatieproces 9 versie 2.0.0 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> :*[[mp:V2.0.0_MedicationProcess9_FHIR|&lt;abbr title=&quot;FHIR Implementation guide for Medicatieproces 9 versie 2.0.0 FHIR in English&quot;&gt;Implementation guide FHIR Medication Process 9 version 2.0.0 (ENG)&lt;/abbr&gt;]]<br /> :*[[mp:V2.0.0_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 2.0.0&lt;/abbr&gt;]]<br /> :*[[mp:V9_2.0.0_HL7v3CDA_FHIRTiming|HL7v3 CDA substanceAdministration.effectiveTime en FHIR timing]]<br /> :*[[7phcy:V09_HL7v3-domeinspecificatie_Pharmacy|HL7v3-domeinspecificatie Pharmacy Medicatieproces 9]]<br /> :*PGO/MedMij: [[MedMij:Vkickstart/OntwerpMedicatie|&lt;abbr title=&quot;Dit is de link naar het Functioneel Ontwerp Medicatieproces 9 patient use cases nodig voor uitwisseling van PGO binnen oa MedMij&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 2.0.0 voor patient use cases&lt;/abbr&gt;]]<br /> <br /> =PAGINAHISTORIE=<br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> !style=&quot;text-align:left;&quot;&quot; width=&quot;130&quot;|Datum<br /> !style=&quot;text-align:left;&quot;|Omschrijving<br /> |-<br /> | style=&quot;background-color: white;&quot;| 1 maart 2024<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; :'''Informatiestandaard Medicatieproces 9.3.0.0-beta.3''' gepubliceerd<br /> :*[[mp:V3.0.0-beta_Ontwerp_medicatieproces_9|&lt;abbr title=&quot;Het functioneel ontwerp van de informatiestandaard Medicatieproces 9 Het beschrijft de algemene werking en specifieke praktijksituaties.&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 3.0.0-beta.3 (NL)&lt;/abbr&gt;]] / [[mp:V3.0.0-beta_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 3.0.0-beta.3 (ENG)]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.<br /> &quot;&gt;Medicatieproces 9 versie 3.0.0-beta.3 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> :*[[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|&lt;abbr title=&quot;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.3 voor patiënt usecases&quot;&gt;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.3 voor patiënt usecases&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.3_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 3.0.0-beta.3&lt;/abbr&gt;]]<br /> :*Gebruikerseisen: [[mp:Besluiten_kernteams|&lt;abbr title=&quot;Deze pagina bevat de besluiten van de kernteams, met (indien van toepassing) de bijbehorende werkproceseisen, gebruikerseisen en -wensen.&quot;&gt;Besluiten kernteams Medicatieproces 9, inclusief gebruikerseisen en -wensen&lt;/abbr&gt;]]<br /> &lt;li&gt; '''Informatiestandaard Medicatieproces 9.3.0.0-beta.2''' naar archief<br /> :*[[mp:V3.0.0-beta.2_Ontwerp_medicatieproces_9|&lt;abbr title=&quot;Het functioneel ontwerp van de informatiestandaard Medicatieproces 9 Het beschrijft de algemene werking en specifieke praktijksituaties.&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 3.0.0-beta.2 (NL)&lt;/abbr&gt;]] / [[mp:V3.0.0-beta.2_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 3.0.0-beta.2 (ENG)]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/index.html&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.<br /> &quot;&gt;Medicatieproces 9 versie 3.0.0-beta.2 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> :*[[mp:V3.0.0_MedicationProcess9_FHIR|&lt;abbr title=&quot;FHIR Implementation guide for Medicatieproces 9 versie 3.0.0-beta.1 FHIR in English&quot;&gt;Implementation guide FHIR Medication Process 9 version 3.0.0-beta.2 (ENG) &lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|&lt;abbr title=&quot;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.2 voor patiënt usecases&quot;&gt;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.2 voor patiënt usecases&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.2_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 3.0.0-beta.2&lt;/abbr&gt;]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/index.html&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.<br /> &quot;&gt;Medicatieproces 9 versie 3.0.0-beta.2 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;] <br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 6 november 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; [[mp:V3.0.0-beta.1_MedicationProcess9_FHIR|&lt;abbr title=&quot;FHIR Implementation guide for Medicatieproces 9 versie 3.0.0-beta.1 FHIR in English&quot;&gt;Implementation guide FHIR Medication Process 9 version 3.0.0-beta.1 (ENG)&lt;/abbr&gt;]] naar archief<br /> &lt;li&gt; [https://simplifier.net/packages/nictiz.fhir.nl.r4.medicationprocess9/2.0.0-beta.1/ FHIR R4 conformance resources for Medication Process 9 (MP9)] naar archief<br /> &lt;li&gt; [[mp:V3.0.0-beta.1_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.1 for patient use cases&lt;/abbr&gt;]] naar archief<br /> &lt;li&gt; [https://simplifier.net/packages/nictiz.fhir.nl.r4.medicationprocess9/2.0.0-beta.2/ FHIR R4 conformance resources for Medication Process 9 (MP9)] geüpdatet naar beta.2 versie<br /> &lt;li&gt; [[mp:V3.0.0_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&lt;/abbr&gt;]] toegevoegd<br /> &lt;li&gt; [https://decor.nictiz.nl/pub/vzvz/index.php?prefix=mp-vzvz-&lt;abbr title=&quot;&quot;&gt;ART-DECOR Publicatiepagina VZVZ: Medicatieproces op het LSP&lt;/abbr&gt;] geüpdatet n.a.v. beta.2 versie<br /> &lt;li&gt; [https://zt-medicatieoverdracht.scrollhelp.site/Medicatieoverdracht/Working-version/programma-van-eisen-medicatieoverdracht&lt;abbr title=&quot;De beschikbare Programma van Eisen waaraan de Kickstart deelnemers moeten voldoen. Deze documenten beschrijven de eisen om aan te sluiten op de AORTA-infrastructuur.&quot;&gt;Programma van eisen LSP (bèta)&lt;/abbr&gt;] geüpdatet n.a.v. beta.2 versie<br /> &lt;li&gt; [https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpublicvzvz.refined.site%2Fspace%2FA8%2F85000200%2FAORTA%2B8.3.0&amp;data=05%7C01%7Ctheunissen%40nictiz.nl%7C52a3bf5378624ff2978e08db8f44c3a3%7C3d542e8da3eb448f998ddd6880dc119c%7C0%7C0%7C638261297740578594%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=6%2FH9yQ0EAHEmGYHgbVoQo995poc34CXlV6UcBP4MSD8%3D&amp;reserved=0&lt;abbr title=&quot;Deze pagina bevat de algemene specificaties van de zorginfrastructuur AORTA v8.3.0.0&quot;&gt;Documentatie AORTA versie 8.3.0.0&lt;/abbr&gt;] geüpdatet n.a.v. beta.2 versie<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 20 oktober 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; [[mp:V3.0.0-beta.2_releasenotes|Release notes Medicatieproces 9 versie 3.0.0-beta.2]] toegevoegd<br /> &lt;li&gt; 2.2 Specificaties: update n.a.v. beta.2 release<br /> *[[mp:V3.0.0-beta_Ontwerp_medicatieproces_9|&lt;abbr title=&quot;Het functioneel ontwerp van de informatiestandaard Medicatieproces 9 Het beschrijft de algemene werking en specifieke praktijksituaties.&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 3.0.0-beta.2 (NL)&lt;/abbr&gt;]] / [[mp:V3.0.0-beta_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 3.0.0-beta.2 (ENG)]]<br /> *[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20230217T123829/index.html&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.<br /> &quot;&gt;Medicatieproces 9 versie 3.0.0-beta.2 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> *[[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|&lt;abbr title=&quot;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.2 voor patiënt usecases&quot;&gt;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.2 voor patiënt usecases&lt;/abbr&gt;]]<br /> *[[mp:V3.0.0_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&lt;/abbr&gt;]]<br /> &lt;li&gt; 3.2 Testscript: update n.a.v. beta.2 release<br /> *[[mp:Vcurrent_Kwalificatie#Medicatieproces_9_versie_3.0.0-beta.1_testmateriaal_en_kwalificatiescripts_voor_Kickstart|Testscripts Medicatieproces 9 versie 3.0.0-beta.2]]<br /> &lt;li&gt; [[mp:V3.0.0-beta.1_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 3.0.0-beta.1&lt;/abbr&gt;]] naar archief<br /> &lt;li&gt; [[mp:V3.0.0-beta.1_Ontwerp_medicatieproces_9|Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.1]] &amp; [[mp:V3.0.0-beta.1_Ontwerp_medicatieproces_9_ENG|Functional Design Medication Process 9 version 3.0.0-beta.1 English version]] naar archief<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 11 oktober 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 3.2 Testscripts: Nieuwe versie Testscript gebruikerseisen boven sectoraal: [https://informatiestandaarden.nictiz.nl/wiki/Bestand:Use_case_scenario%27s_en_testscripts_GERRIT_-_Pati%C3%ABnt_1tm4_-_stap_3-4_-_beta_versie_3.0_.pdf Use case scenario's en testscripts GERRIT - Patiënt 1tm4 - stap 3-4 - beta versie 3.0&lt;/abbr&gt;] toegevoegd.<br /> &lt;li&gt; 3.2 Testscripts: Nieuwe versie Testscript gebruikerseisen boven sectoraal: [https://informatiestandaarden.nictiz.nl/wiki/Bestand:Use_case_scenario%27s_en_testscripts_Rijnmond_-_pati%C3%ABnt_1-4_-_stap_3-4_-_beta_versie_3.0_(1).pdf Use case scenario's en testscripts Rijnmond - patiënt 1-4 - stap 3-4 - beta versie 3.0&lt;/abbr&gt;] toegevoegd.<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 6 september 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 2.5 [[mp:V3.0_Voorbeelden_doseringen|&lt;abbr title=&quot;Uitgewerkte voorbeelden voor het concept 'Gebruiksinstructie' uit de dataset van de Informatiestandaard Medicatieproces 9&quot;&gt;Voorbeelden doseringen&lt;/abbr&gt;]] aangepast naar 9.3 versie.<br /> |-<br /> | style=&quot;background-color: white;&quot;| 4 september 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 3.2 Testscripts: Testscript gebruikerseisen boven sectoraal: [https://informatiestandaarden.nictiz.nl/wiki/Bestand:Use_case_scenario%27s_en_testscripts_GERRIT_-_Pati%C3%ABnt_1tm4_-_stap_3-4_-_beta_versie_3.0_.pdf Use case scenario's en testscripts GERRIT - Patiënt 1tm4 - stap 3-4 - beta versie 3.0&lt;/abbr&gt;] toegevoegd.<br /> &lt;li&gt; 3.2 Testscripts: Testscript gebruikerseisen boven sectoraal: [https://informatiestandaarden.nictiz.nl/wiki/Bestand:Use_case_scenario%27s_en_testscripts_Rijnmond_-_pati%C3%ABnt_1-4_-_stap_3-4_-_beta_versie_3.0_(1).pdf Use case scenario's en testscripts Rijnmond - patiënt 1-4 - stap 3-4 - beta versie 3.0&lt;/abbr&gt;] toegevoegd.<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 28 juli 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 2.2 Specificaties: Infrastructuur: [https://publicvzvz.refined.site/space/MED/86179842/Kickstart+van+Medicatieoverdracht Programma van eisen LSP (bèta)] link aangepast naar pagina met meest recente informatie<br /> &lt;li&gt; 2.2 Specificaties: Infrastructuur: [https://publicvzvz.refined.site/space/A8/85000200/AORTA+8.3.0 Documentatie AORTA versie 8.3.0.0] link aangepast naar pagina met meest recente informatie<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 2 juni 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 3.2 Testscripts: Algemene eisen MP9 &amp; Generieke voorzieningen toegevoegd<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 30 mei 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 2.1 Voorbereiding: Plan van aanpak versie 3.1. Addendum plan van aanpak Kickstart v3.1 - Aanpassing Kickstartplanning Mei 2023 toegevoegd aan onderliggende pagina<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 4 mei 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 2.2 Specificaties: [[mp:V2.0.0_Verwijzing_naar_documentatie_Medicatieproces9_tbv_Kickstart|Verzamelbestand met functionele, technische en infrastructurele documentatie Medicatieproces 9 t.b.v. Kickstart]] ge-update met linkjes naar 9.3 versie<br /> &lt;li&gt; 3.1 Testinformatie Kickstart: [[mp:Testen_Kickstart|Testen Kickstart]] toegevoegd.<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 25 april 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 2.2 Specificaties: [[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.1 voor patiënt usecases]] toegevoegd .&lt;br&gt;<br /> &lt;li&gt; 2.2 Specificaties: [[mp:V3.0.0_MedicationProcess9_FHIR_for_patient_use_cases|FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.1 for patient use cases]] toegevoegd.&lt;br&gt;<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 20 april 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 4.1 Testen met ART-DECOR: onderliggende pagina vervangen naar [[HL7v3 kwalificatiesimulator]] .&lt;br&gt;<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 11 april 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; Hoofdstuk 3.1 nieuwe versie testscripts toegevoegd: [[mp:Vcurrent_Kwalificatie#Medicatieproces_9_versie_3.0.0-beta.1_testmateriaal_en_kwalificatiescripts_voor_Kickstart|Medicatieproces 9 versie 3.0.0-beta.1]]&lt;br&gt;<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 21 maart 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; Hoofdstuk 6 MEMO'S toegevoegd&lt;br&gt;<br /> &lt;li&gt; Memo MBH-ID Transformatiedienst 15-03-2023 toegevoegd&lt;br&gt;<br /> &lt;li&gt; Memo vooraankondiging 07-03-2023 toegevoegd<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 6 maart 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; Implementatiehandleiding Consolidatie en afleidingsregels toegevoegd&lt;br&gt;<br /> &lt;li&gt; Specificaties Informatiestandaard Medicatieproces 9 versie 3.0.0-beta.1 toegevoegd<br /> * Functioneel ontwerp<br /> * Technisch ontwerp CDA<br /> * Technisch ontwerp FHIR<br /> * Release notes <br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 18 januari 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt;[https://decor.nictiz.nl/pub/vzvz/aorta-vzvz-html-20221128T172039/sc-2.16.840.1.113883.2.4.3.111.3.2.3.3-2016-09-20T163842.html Implementatie van de ping-pong toets]: link aangepast naar AORTA 8.3 versie<br /> &lt;li&gt;[https://decor.nictiz.nl/pub/vzvz/aorta-vzvz-html-20221128T172039/sc-2.16.840.1.113883.2.4.3.111.3.2.3.1-2016-09-20T091642.html Beheren TKID applicatie]: link aangepast naar AORTA 8.3 versie<br /> &lt;li&gt;[https://public.vzvz.nl/download/attachments/41779447/AORTA_Proces_VWI_Synchronisatie.pdf?api=v2 Proces VWI synchronisatie]: link aangepast naar AORTA 8.3 documentatie<br /> &lt;li&gt;[https://public.vzvz.nl/download/attachments/41779447/AORTA_Sgl_Ontw_Gebeurtenisverwerking.pdf?api=v2 Ontwerp gebeurtenisverwerking]: link aangepast naar AORTA 8.3 documentatie<br /> &lt;li&gt;[https://public.vzvz.nl/download/attachments/41779447/AORTA_Sgl_Ontw_Abonnementenregister.pdf?api=v2 Ontwerp abonnementenregister]: link aangepast naar AORTA 8.3 documentatie<br /> &lt;li&gt;[https://www.vzvz.nl/diensten/gemeenschappelijke-diensten/zorg-ab Implementatie handleiding ZORG-AB]: link aangepast naar Zorg-AB pagina met meest recente documentatie<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 29 september 2022<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt;Specificaties Lab2zorg: link toegevoegd naar de [[mp:LeeswijzerVoorschriftmetnierfunctiewaarde|leeswijzer ten behoeve van het meesturen van de nierfunctiewaarde met het voorschrift]]&lt;br&gt;<br /> De leeswijzer legt uit welk onderdeel van Lab2zorg binnen de scope van de Kickstart valt en welke documentatie daarop van toepassing is. De leeswijzer vervangt het aanvullingendocument.<br /> &lt;li&gt;Specificaties Lab2zorg: link verwijderd naar het [[Lab:V3.0.0_Ontwerp_Laboverdacht|functioneel ontwerp informatiestandaard uitwisseling Laboratoriumgegevens versie 3.0.0]]&lt;br&gt;<br /> De informatiestandaard beschrijft de algemene werking voor alle uitwisselingen van Laboratoriumgegevens. Het onderdeel lab2zorg hieruit wordt gebruikt in de kickstart.<br /> &lt;li&gt;Specificaties Lab2zorg: link verwijderd naar aanvullingendocument<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 12 september 2022<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt;Specificaties: link toegevoegd naar [[mp:Stap_0_Voorbereiding|Werkzaamheden in stap 0 Voorbereiding]]<br /> &lt;li&gt;Informatievoorziening: link toegevoegd naar [[mp:Medicatieoverdracht_Kickstart_Vragen|Vragen en antwoorden uit vragenuur op vrijdagen]]&lt;br&gt;<br /> Na elk vragenuur worden de vragen en antwoorden aan deze pagina toegevoegd<br /> &lt;li&gt;Archief: link naar oude versie nulpunt document verwijderd en link naar nieuwe toegevoegd [https://informatiestandaarden.nictiz.nl/images/4/42/Nulpunt_documentatie_Kickstart_contract_leveranciers_versie11_20220907.pdf Nulpunt documentatie leveranciers versie 1.1 van 7 september 2022] &lt;br&gt;<br /> Inhoudelijke wijziging versie 1.1: link naar document Werkzaamheden in stap 0 Voorbereiding toegevoegd<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 1 september 2022<br /> | style=&quot;background-color: white;&quot;| Formele publicatie van de pagina + update: <br /> &lt;ul&gt;<br /> &lt;li&gt;Titel aangepast<br /> &lt;li&gt;Algemeen referentie: onderdeel toegevoegd en kwaliteitsstandaard toegevoegd<br /> &lt;li&gt;Voorbereiding: checklists verwijderd<br /> &lt;li&gt;Specificaties: verzamelbestand omgezet van Excel naar wiki<br /> &lt;li&gt;Specificaties MP9: gebruikerseisen toegevoegd<br /> &lt;li&gt;Specificaties Lab2zorg: labdocumentatie toegevoegd<br /> &lt;li&gt;Specificaties Infrastructuur: aorta 8.2 vervangen door aorta 8.3 (8.2 naar archief)<br /> &lt;li&gt;Test- en validatiemateriaal: testscripts en kwalificatiescripts gesplitst, alleen testscripts MP9 gelinkt en labtestmateriaal toegevoegd<br /> &lt;li&gt;Tooling BITS: handleiding BITS toegevoegd<br /> &lt;li&gt;Archief: nulpunt 1 september 2022 toegevoegd<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 1 augustus 2022<br /> | style=&quot;background-color: white;&quot;| Correctie in ''Verzamelbestand met functionele, technische en infrastructurele documentatie Medicatieproces 9 t.b.v. Kickstart''<br /> |-<br /> | style=&quot;background-color: white;&quot;| juli 2022<br /> | style=&quot;background-color: white;&quot;| Pagina gepubliceerd<br /> |}</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=Sjabloon:VersieInfo&diff=206724 2024-03-07T12:30:42Z

<p>Luud Slagter: Updated package number of MP9 package</p> <hr /> <div>{{#switch: {{{namespace|{{NAMESPACE}}}}}:{{{release|{{ROOTPAGENAME}}}}}<br /> <br /> | MedMij:V2019.01 = {{#switch: {{{1}}}<br /> | BgZ = 2.2.2<br /> | Laboratoriumresultaten = 1.2.2<br /> | Medicatieproces = 9.0.7<br /> | MedicatieprocesVerstrekkingenvertaling = 9.A.1<br /> | AllergieIntolerantie1 = 1.2.2<br /> | AllergieIntolerantie = 2.1.2<br /> | AllergieIntolerantieVertaling = 1.A.15<br /> | eAfspraak = 1.2.2<br /> | Zelfmetingen = 1.3.2<br /> | PDFA = 2.1.2<br /> | PDFA1 = 1.3.2<br /> | Huisartsgegevens = 1.2.2<br /> | BgGGZ = 1.2.2<br /> | BgLZ = 1.1.2<br /> | Beelden = 1.1.2<br /> | Vragenlijsten = 1.1.2<br /> | package = 1.3.19<br /> | nictiz.fhir.nl.stu3.zib2017 = 1.3.19<br /> | Editie = 2019.01<br /> }}<br /> <br /> | MedMij:V2020.01 = {{#switch: {{{1}}}<br /> | BgZ = 3.1.18<br /> | Laboratoriumresultaten = 2.0.36<br /> | Medicatieproces = 9.0.7<br /> | MedicatieprocesVerstrekkingenvertaling = 9.A.1<br /> | AllergieIntolerantie1 = 2.0.35<br /> | AllergieIntolerantie = 3.0.35<br /> | AllergieIntolerantieVertaling = 2.A.14<br /> | eAfspraak = 2.0.35<br /> | Zelfmetingen = 2.0.36<br /> | PDFA = 3.0.37<br /> | PDFA1 = 3.0.37<br /> | Huisartsgegevens = 2.0.36<br /> | BgGGZ = 2.0.37<br /> | BgLZ = 2.0.24<br /> | Beelden = 2.0.35<br /> | Vragenlijsten = 2.0.37<br /> | Vragenlijsten1 = 1.0.37<br /> | Geboortezorg = 1.0.2<br /> | package = 2.2.18<br /> | nictiz.fhir.nl.stu3.zib2017 = 2.2.18<br /> | nictiz.fhir.nl.stu3.eafspraak = 1.0.6<br /> | nictiz.fhir.nl.stu3.images = 1.0.3<br /> | nictiz.fhir.nl.stu3.questionnaires = 2.0.8<br /> | nictiz.fhir.nl.stu3.bgz = 1.1.1<br /> | Editie = 2020.01<br /> }}<br /> <br /> | MedMij:V2020.02 = {{#switch: {{{1}}}<br /> | BgLZ = 3.1.17<br /> | package = 2.2.18<br /> | nictiz.fhir.nl.stu3.zib2017 = 2.2.18<br /> | Editie = 2020.02<br /> }}<br /> <br /> | MedMij:V6 = {{#switch: {{{1}}}<br /> | Dossierwijzigingsverzoek = 1.0.13<br /> | Vaccinatie-Immunisatie = 1.0.11<br /> | MedMij_FHIR_IG_R4 = 1.0.4<br /> | MedMij_FunctioneelOntwerp = 1.0.1<br /> | Kwalificatie = 1.0.3<br /> | package = 0.8.0-beta.1<br /> | nictiz.fhir.nl.r4.zib2020 = 0.8.0-beta.1<br /> | nictiz.fhir.nl.r4.nl-core = 0.8.0-beta.1<br /> | nictiz.fhir.nl.r4.patientcorrections = 1.0.6<br /> | nictiz.fhir.nl.r4.vaccinationimmunization = 1.0.3<br /> | nictiz.fhir.nl.r4.immunization = 1.0.3<br /> | Editie = 6.1.3<br /> }}<br /> <br /> | MedMij:IG:V1 = {{#switch: {{{1}}}<br /> | MedMij_FHIR_IG_R4 = 1.0.4<br /> }}<br /> <br /> | MedMij:FO:V1 = {{#switch: {{{1}}}<br /> | MedMij_FunctioneelOntwerp = 1.0.1<br /> }}<br /> <br /> | MedMij:Kwalificatie:V1 = {{#switch: {{{1}}}<br /> | MedMij_Kwalificatie = 1.0.3<br /> }}<br /> <br /> | FHIR:V1.0 = {{#switch: {{{1}}}<br /> | FHIR_IG_R4 = 1.0.3<br /> }}<br /> <br /> | mp:V9.1 = {{#switch: {{{1}}}<br /> | mp = 9.1<br /> | Medicatieproces = 9.1.0<br /> | MedicatieprocesVerstrekkingenvertaling = 9.A.5<br /> | package = 2.0.0<br /> | nictiz.fhir.nl.stu3.zib2017 = 2.0.0<br /> | nictiz.fhir.nl.stu3.medicationprocess= 9.1.0-beta<br /> }}<br /> <br /> | mp:V2.0.0 = {{#switch: {{{1}}}<br /> | mp9 = 2.0.0<br /> | nictiz.fhir.nl.r4.zib2020 = 0.5.0-beta1<br /> | nictiz.fhir.nl.r4.nl-core = 0.5.0-beta1<br /> | nictiz.fhir.nl.r4.medicationprocess9 = 1.0.0<br /> }}<br /> <br /> | mp:V3.0.0-beta.1 = {{#switch: {{{1}}}<br /> | mp9 = 3.0.0-beta.1<br /> | nictiz.fhir.nl.r4.zib2020 = 0.8.0-beta.1<br /> | nictiz.fhir.nl.r4.nl-core = 0.8.0-beta.1<br /> | nictiz.fhir.nl.r4.medicationprocess9 = 2.0.0-beta.1<br /> }}<br /> <br /> | mp:V3.0.0-beta.2 = {{#switch: {{{1}}}<br /> | mp9 = 3.0.0-beta.2<br /> | nictiz.fhir.nl.r4.zib2020 = 0.10.0-beta.1<br /> | nictiz.fhir.nl.r4.nl-core = 0.10.0-beta.1<br /> | nictiz.fhir.nl.r4.medicationprocess9 = 2.0.0-beta.2<br /> }}<br /> <br /> | mp:V3.0.0 = {{#switch: {{{1}}}<br /> | mp9 = 3.0.0-beta.3<br /> | nictiz.fhir.nl.r4.zib2020 = 0.10.0-beta.1<br /> | nictiz.fhir.nl.r4.nl-core = 0.10.0-beta.1<br /> | nictiz.fhir.nl.r4.medicationprocess9 = 2.0.0-beta.5<br /> }}<br /> <br /> | Lab:V3.0.0 = {{#switch: {{{1}}}<br /> | nictiz.fhir.nl.r4.zib2020 = 0.6.0-beta.2<br /> | nictiz.fhir.nl.r4.nl-core = 0.6.0-beta.2<br /> | nictiz.fhir.nl.r4.labexchange = 3.0.0-beta.1<br /> }}<br /> <br /> | vpk:V4.0 = {{#switch: {{{1}}}<br /> | eOverdracht = 4.0-rc.23<br /> | nictiz.fhir.nl.stu3.zib2017 = 2.2.18<br /> | nictiz.fhir.nl.stu3.eoverdracht = 1.0.0-rc.23<br /> | nictiz.fhir.nl.stu3.zib2020-preadopt = 0.1.3<br /> }}<br /> <br /> | hg:V1 = {{#switch: {{{1}}}<br /> | ELZ = 0.2.0-beta.1<br /> | BITS = https://bits.nictiz.nl/projects/ELZ<br /> | nictiz.fhir.nl.r4.elz = 0.2.0-beta.1<br /> }}<br /> <br /> | Gebz:V1 = {{#switch: {{{1}}}<br /> | MedMij_Integrale_Zwangerschapskaart = 0.1.0-beta.1<br /> | nictiz.fhir.nl.stu3.geboortezorg = 1.2.0<br /> }}<br /> <br /> | cio:V2.0.0-beta.1 = {{#switch: {{{1}}}<br /> | CiO = 2.0.0-beta.1<br /> | BITS = https://bits.nictiz.nl/projects/CIO<br /> | nictiz.fhir.nl.r4.nl-core = 0.9.0-beta.1<br /> | nictiz.fhir.nl.r4.medicationprocess9 = 2.0.0-beta.1<br /> | nictiz.fhir.nl.r4.cio = 1.0.0-beta.1<br /> }}<br /> <br /> | cio:V2.0.0-beta.2 = {{#switch: {{{1}}}<br /> | CiO = 2.0.0-beta.2<br /> | BITS = https://bits.nictiz.nl/projects/CIO<br /> | nictiz.fhir.nl.r4.nl-core = 0.10.0-beta.1<br /> | nictiz.fhir.nl.r4.cio = 1.0.0-beta.2<br /> }}<br /> <br /> | bbs:V1.0.0 = {{#switch: {{{1}}}<br /> | BBS = 1.0.0-alfa.1<br /> | BITS = https://bits.nictiz.nl/projects/BBS<br /> }}<br /> <br /> | bbs:V1.0.0b = {{#switch: {{{1}}}<br /> | BBS = 1.0.0-alpha.2<br /> | BITS = https://bits.nictiz.nl/projects/BBS<br /> }}<br /> <br /> | BgZ:V1.1.0 = {{#switch: {{{1}}}<br /> | BgZ = 1.1.0-alfa.1<br /> | BITS = https://bits.nictiz.nl/projects/MSZ<br /> }}<br /> <br /> | jgz:V7 = {{#switch: {{{1}}}<br /> | JGZ = 7.1.2<br /> | BITS = https://bits.nictiz.nl/projects/JGZ<br /> }}<br /> <br /> }}&lt;noinclude&gt;<br /> == Doel ==<br /> <br /> Er zijn allerlei situaties waarin de specifieke versie van een component een bepaalde versie van een ander component gebruikt, bijvoorbeeld een versie van een informatiestandaard die een bepaalde versie van een FHIR-package nodig heeft. Dit sjabloon is bedoeld om dit soort versie-afhankelijkheden te leggen.<br /> <br /> == Gebruik ==<br /> <br /> Dit sjabloon koppelt simpelweg de versie (om legacy-redenen 'release' genoemd) van de gebruikende component plus de naam van de gebruikte component aan de versienummer van deze gebruikte component.<br /> <br /> Het sjabloon kan op pagina's ingezet worden met:<br /> &lt;pre&gt;{{VersieInfo|[component](|release=[release])(|namespace=[namespace])}}&lt;/pre&gt;<br /> * &lt;code&gt;component&lt;/code&gt;: de naam van de ''gebruikte'' component, dus bv. de naam van het FHIR-package dat een standaard gebruikt.<br /> * &lt;code&gt;release&lt;/code&gt;: de versie(string) van de ''gebruikende'' component, dus bv. de versie van een informatiestandaard die het FHIR-package gebruikt. Als deze parameter wordt weggelaten, wordt als default de [https://www.mediawiki.org/wiki/Help:Magic_words#Page_names ROOTPAGENAME] van de (aanroepende) pagina gebruikt.<br /> * &lt;code&gt;namespace&lt;/code&gt;: als de gebruikende ''pagina'' zich in een andere namespace bevindt dan de namespace geregistreerd in dit sjabloon kan hier de namespace expliciet vermeld worden. Dit is vooral relevant voor verwijzingen waarin het versienummer wordt opgenomen.<br /> <br /> Dit wordt dan vervangen door het bijbehorende versienummer. De naam van 'component' dient uiteraard exact overeen te komen met de naam die in dit sjabloon staat.<br /> <br /> Bijvoorbeeld: binnen MedMij worden versienummers van individuele informatiestandaarden gekoppeld aan een bepaalde MedMij-release. Bv. de BgZ heeft binnen de MedMij-release &quot;V2019.01&quot; het versienummer 2.1.13. Dit kan opgezocht worden via:<br /> <br /> &lt;pre&gt;{{VersieInfo|BgZ|release=V2019.01}}&lt;/pre&gt;<br /> <br /> === Onderhoud versienummers ===<br /> <br /> Het sjabloon bestaat uit een geneste switch; de eerste tak kijkt naar de Release (de eerste parameter), de tweede naar de naam van de gezochte component. Deze informatie staat bovenaan de pagina wanneer deze bewerkt wordt.<br /> <br /> Wanneer het nodig is om een nieuwe release toe te voegen, volstaat het om het volgende stuk toe te voegen:<br /> &lt;pre&gt;<br /> | NAMESPACE:&lt;release&gt; = {{#switch: {{{2}}}<br /> | &lt;component1&gt; = x.x.x<br /> | &lt;component2&gt; = x.x.x<br /> ...<br /> | &lt;componentN&gt; = x.x.x<br /> <br /> }}<br /> &lt;/pre&gt;<br /> === Afwijkende versienummers in systeemrolcodes ===<br /> <br /> In sommige informatiestandaarden zijn er systeemrolcodes met een versie die afwijkt van die van de standaard als geheel. Typisch gebeurt dit wanneer er een use case is bijgekomen in een standaard; de major-versie wordt opgehoogd, maar de systeemrollen in de oorspronkelijke use case blijven de oorspronkelijke versie gebruiken (zolang er nog geen reden is om over te gaan naar een nieuwe versie).<br /> <br /> Er is gekozen voor een pragmatische aanpak in dit soort gevallen door simpelweg een tweede entry toe te voegen voor de afwijkende major-versie; de standaard &quot;PDF/A&quot; staat bijvoorbeeld twee keer in het lijstje, een keer als &quot;PDFA&quot; en een keer als &quot;PDFA1&quot; voor de oudere systeemrolcodes.<br /> &lt;/noinclude&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=mp:V3.0.0-rc.2_MedicationProcess9_FHIR&diff=206669 2024-03-06T20:43:18Z

<p>Luud Slagter: /* Retrieve all medication data */</p> <hr /> <div>__NOINDEX__<br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide Medication Process 9 version {{VersieInfo|mp9|release=V3.0.0}} }}<br /> <br /> __TOC__<br /> <br /> = Introduction =<br /> 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.<br /> <br /> 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.<br /> <br /> This IG first describes the boundaries and relationships in place, after which the implementation is described per transaction.<br /> <br /> = Boundaries and relationships =<br /> == Building blocks and profiles ==<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> Because the way 90 million numbers are exchanged is not compatible with the 2020 publication of zib PharmaceuticalProduct, a fork of the corresponding nl-core profile called 'mp-PharmaceuticalProduct' has been introduced.<br /> <br /> {{NoteBoxNictizR4Package|p1=nictiz.fhir.nl.r4.medicationprocess9|v1={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|p2=nictiz.fhir.nl.r4.nl-core|v2={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> <br /> 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:<br /> * MP9 version 2.0.0 makes use of version 1.0.0 of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package;<br /> * MP9 version 3.0.0-beta.x makes use of version 2.0.0-beta.x of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package.<br /> <br /> === Medication building blocks ===<br /> <br /> As described above, the main medication building blocks have no dependency on any zib2020 counterparts, resulting in so-called ‘mp’ profiles. Moreover, note that the building block VariableDosingRegimen does not have a zib counterpart, hence it makes sense to include it as an mp profile as well.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |}<br /> <br /> === Supporting building blocks ===<br /> <br /> Additionally, the standard uses several supporting building blocks referenced from the main medication building blocks. All supporting building blocks are part of the [[FHIR:V1.0_FHIR_IG_R4#Functional_definitions|‘nl-core’ package]]&lt;ref&gt;Although the nl-core package is still in beta-status, HL7 Netherlands has validated the profiles mentioned and assigned the status 'STU-NL' for use in the MP9 Kickstart, see [[Media:HL7_Nederland_disclaimer_STU-NL.pdf]]&lt;/ref&gt;.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> Note the following:<br /> * Each occurrence of the zib HealthProfessional is normally represented by '''two''' FHIR resources: an instance of nl-core-HealthProfessional-PractitionerRole and an instance of nl-core-HealthProfessional-Practitioner. Sending systems should only fill the reference to the PractitionerRole instance where relevant. Receiving systems can resolve the reference to the Practitioner resource from that PractitionerRole instance.<br /> * The zib HealthcareProvider is mapped to both a Location and Organization profile. Most often, the Location profile acts as the focal resource, because most references to this zib are concerned about the recording of the physical location where the care to patient/client takes place rather than the organizational information. For the latter, the profile on Organization is used which is referenced using the {{fhir|Location.managingOrganization}} element. Sending systems should only fill the reference to the Location instance where relevant. Incidentally, concepts that are only concerned with organizational information can refer to the Organization instance.<br /> <br /> === Transaction specific profiles ===<br /> <br /> For several transactions, additional profiles are provided. For each transaction the profile relevant is explicitly mentioned in the corresponding subsection.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |}<br /> <br /> ====Bundle profiles====<br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == Mappings between profiles and data set ==<br /> 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.<br /> <br /> 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:<br /> * 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)<br /> ** 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.<br /> ** 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.<br /> * If an element in the functional definition is removed<br /> ** and the element had a zib mapping applied (not on an extension), the zib mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> ** and the element had a mapping applied to the previous version of MP9 (not on an extension), that mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> * If an element in the functional definition is removed and the element had a mapping applied on an extension, that extension is removed entirely. In particular no {{term|[DEPRECATED]}} mapping will be visible in the FHIR profile. This is done to ensure no redundant extensions remain in the FHIR profiles.<br /> <br /> Moreover, all mappings to earlier versions of MP9 (i.e. versions before the previous version) are entirely removed.<br /> <br /> Following the procedure outlined above thus results in the following:<br /> * 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.<br /> * All incompatible changes made in the latest version with respect to the previous version are marked.<br /> * Exceptions are extensions that would otherwise only contain deprecated mappings; these are removed fully.<br /> <br /> 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’]].<br /> <br /> 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.<br /> <br /> 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]].<br /> <br /> == Pharmaceutical treatment ==<br /> 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.<br /> <br /> == Patient identification ==<br /> This implementation guide assumes that the client system is able to make a connection to the right server that contains the patient's information. It does not provide information on finding the right server nor does it provide information about security. Moreover, each transaction is performed in the context of a specific patient, whose context might have been established using the authentication mechanisms described in external specifications such as the MedMij ‘Afsprakenstelsel’ or through the usage of search parameters for patient identification. <br /> <br /> Each server is required to perform filtering based on the patient associated with the context for the request or based on the patient identification search parameters, which is a [https://www.hl7.org/fhir/r4/search.html#chaining chained search parameter] for all resource types except Patient, so only the records associated with the authenticated patient are returned.<br /> <br /> When patient identification requires the use of search parameters, the following search parameters SHALL be supported:<br /> * Patient: {{fhir|identifier}}<br /> * MedicationRequest: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationDispense: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationStatement: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationAdministration: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> <br /> An example of a request that retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233:<br /> <br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> <br /> Note: All request examples in this document do not include patient identification mechanisms, partly because we want to generalize this technical design as much as possible (it being applicable to both MedMij and other contexts), and partly because this would convolute all search request examples. Requesters are assumed to include these if necessary. Since there currently are only transactions in the context of a single patient, the patient identification mechanism is actually implicitly assumed to be present in all search requests.<br /> <br /> == Resource identification ==<br /> 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}}.<br /> <br /> 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 &lt;code&gt;@root&lt;/code&gt; and &lt;code&gt;@extension&lt;/code&gt; (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.<br /> <br /> 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|release=V3.0.0}}}} 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]].<br /> <br /> == Differentiating between transactions ==<br /> All transactions described in this IG use the same medication building blocks in different combinations and settings, making it necessary to differentiate between them. Several mechanisms are used to achieve this. Aside from PUSH/PULL, the type of medication building blocks, supporting resources like List and Communication for specific transactions and fixing the value of specific FHIR elements in applicable profiles, the {{term|actionable}} tag is used. The latter is described more in depth in the following section. Next to that, a summarizing table is provided.<br /> <br /> Note that {{fhir|Resource.meta.profile}}, although present in each building block (see [[FHIR:V1.0_FHIR_IG_R4#Profile_use_and_declaration|the general FHIR IG on ‘Profile use and declaration’]]), SHOULD [https://hl7.org/fhir/r4/resource.html#profile-tags not be used for identification of the building block type] and therefore for differentiating between transactions.<br /> <br /> === Actionable tag ===<br /> To differentiate between sending or serving building blocks that are either of informative nature or of actionable nature, the {{term|actionable}} tag is used. [https://hl7.org/fhir/r4/resource.html#tag Tags] are {{datatype|Coding}} elements present in {{fhir|Resource.meta.tag}} used for workflow management.<br /> <br /> If applicable, the profiles used by a transaction require the use of {{fhir|.meta.tag}} with {{fhir|.system}} = {{term|&lt;nowiki&gt;http://terminology.hl7.org/CodeSystem/common-tags&lt;/nowiki&gt;}} and {{fhir|.code}} = {{term|actionable}} to indicate that the resource is part of a request intended to be acted upon. The absence of this tag indicates that the resource is merely of informative nature.<br /> <br /> It is up to systems to determine how and when the transactions using the {{term|actionable}} tag are handled from a functional perspective. Systems may store the resource including the {{term|actionable}} tag or remove it either upon storing or when the request is acted upon. However, systems SHALL make sure the tag is removed when serving or sending the resource as part of an informative transaction.<br /> <br /> === Summarizing table ===<br /> {| class=&quot;wikitable&quot; <br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | PUSH/PULL<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building blocks<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | {{term|actionable}} tag<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR element value<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Other<br /> |-<br /> | Medication data (Retrieve/Serve)<br /> | PULL<br /> | One or more of all building blocks<br /> | No<br /> |<br /> | <br /> |-<br /> | Medication data (Send/Receive)<br /> | PUSH<br /> | One or more of all building blocks<br /> | No<br /> |<br /> |<br /> |-<br /> | Medication overview (Retrieve/Serve)<br /> | PULL<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication overview (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication prescription (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, DispenseRequest (optional)<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|order}} (for both MedicationAgreement and DispenseRequest building blocks)<br /> | <br /> |-<br /> | Medication prescription processing (Send/Receive)<br /> | PUSH<br /> | AdministrationAgreement, MedicationDispense (optional)<br /> | Yes<br /> | <br /> | <br /> |-<br /> | Proposal dispense request (Send/Receive)<br /> | PUSH<br /> | DispenseRequest<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal dispense request (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to DispenseRequest<br /> |-<br /> | Proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to MedicationAgreement<br /> |}<br /> <br /> = Transactions =<br /> 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’.<br /> &lt;section begin=medmij1 /&gt;<br /> == Medication data (Retrieve/Serve) ==<br /> The retrieve medication data transaction is used by the client to retrieve medication data from a server. The client can retrieve its desired information by searching for specific medication building blocks.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.372_20220630000000 Medication data (PULL)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.373-2022-06-30T000000.html Retrieving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGR<br /> &lt;section end=medmij1 /&gt;<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Retrieve/serve medication data}}<br /> &lt;section begin=medmij2 /&gt;<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.374-2022-06-30T000000.html Serving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain all medication data or specific parts matching various parameters, they issue a retrieve medication data request message. This message uses the HTTP GET method parameterized query against the server's medication FHIR endpoints. These endpoints can be one of the following:<br /> * MedicationRequest<br /> * MedicationDispense<br /> * MedicationStatement<br /> * MedicationAdministration<br /> <br /> The search interaction is performed by an HTTP GET conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query. Multiple request messages may be needed to retrieve all desired information.<br /> <br /> &lt;pre&gt;GET [base]/[type]{?[parameters]}&lt;/pre&gt;<br /> <br /> ==== Search parameters ====<br /> All search parameters listed in the table below SHALL be supported for processing by servers and MAY be supported by clients.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | MP9 search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Description<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Example<br /> &lt;section end=medmij2 /&gt;<br /> |-<br /> | PatientIdentificationNumber<br /> | Search on patient.<br /> | {{fhir|patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;&gt;This search parameter only needs to be supported when patient identification requires the use of search parameters, see [[#Patient_identification|section 2.4]].&lt;/ref&gt;<br /> {{fhir|subject:Patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;/&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233.<br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> &lt;section begin=medmij3 /&gt;<br /> |-<br /> | Identification<br /> | Search on identifier.<br /> | {{fhir|identifier}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves a MedicationRequest resource with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?identifier=http://example.nl/fhir/NamingSystem/MedicationRequest|999922448&lt;/pre&gt;<br /> |-<br /> | Identification<br /> | Search on the pharmaceutical treatment identifier. <br /> Note: retrieval of all medication resources belonging to one pharmaceutical treatment requires to search on all medication resource types.<br /> | {{fhir|pharmaceutical-treatment-identifier}} &lt;ref name=&quot;custom-searchparameter&quot;&gt;The search parameter consists of a custom FHIR search parameter not represented in the FHIR specification. Note that for {{fhir|MedicationRequest.category}} and {{fhir|MedicationStatement.category}} a core search parameter is available, hence no custom one is needed in those cases.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that are part of a pharmaceutical treatment with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?pharmaceutical-treatment-identifier=http://example.nl/fhir/NamingSystem/pharmaceuticaltreatment|1247848&lt;/pre&gt;<br /> |-<br /> | rowspan=&quot;4&quot; | Type<br /> | rowspan=&quot;4&quot; | Search on type of medication building block. <br /> | rowspan=&quot;4&quot; | {{fhir|category}} &lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block DispenseRequest.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block VariableDosingRegimen.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&lt;/pre&gt;<br /> |-<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&lt;/pre&gt;<br /> Retrieves all MedicationDispense resources that represent the building block AdministrationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&lt;/pre&gt;<br /> |-<br /> | MedicationStatement<br /> | Retrieves all MedicationStatement resources that represent the building block MedicationUse2.<br /> &lt;pre&gt;GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&lt;/pre&gt;<br /> |-<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&lt;/pre&gt;<br /> |-<br /> | MedicationCode<br /> | Search on medication code.<br /> | {{fhir|medication.code}}&lt;ref&gt;[https://www.hl7.org/fhir/r4/search.html#chaining Chained search parameter]: searches the medicationReference required in each building block for its {{fhir|.code}}.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and have Carbasalaatcalcium Sandoz 600 30 as medication.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&lt;/pre&gt;<br /> |-<br /> | PeriodOfUse<br /> | 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.<br /> Whenever a search is done on the MedicationAgreement, VariableDosingRegimen or AdministrationAgreement building blocks it is required to also include the latest stopped building blocks of that kind within each pharmaceutical treatment, even if these have a period of use outside the PeriodOfUse that is being searched on.<br /> | {{fhir|period-of-use}}&lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement&lt;ref&gt;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.&lt;/ref&gt;<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and were in effect from 01-01-2010.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;period-of-use=ge2010-01-01&lt;/pre&gt;<br /> |-<br /> | DispensePeriod <br /> | Returns all medication dispenses within the specified time period.<br /> | {{fhir|whenhandedover}}<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense and were handed over within a 2 year period.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;whenhandedover=ge2010-01-01&amp;whenhandedover=le2011-12-31&lt;/pre&gt;<br /> |-<br /> | AdministrationPeriod <br /> | Returns all medication administrations within the specified time period.<br /> | {{fhir|effective-time}}<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2 and where administration happened on a specific day.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;effective-time=eq2022-01-01&lt;/pre&gt;<br /> |-<br /> | -<br /> | The client may request that the server returns resources related to the search results, in order to reduce the overall network delay of repeated retrievals of related resources.<br /> Supporting the include of the Patient and Medication resources referenced by building blocks is required. Others (Organization, Location, PractitionerRole, Practitioner, RelatedPerson, Observation) are optional. However: all resources referenced per literal reference SHALL be resolvable [[FHIR:V1.0_FHIR_IG_R4#Including_referenced_resources|per the Nictiz IG]].<br /> | {{fhir|&lt;nowiki&gt;_include=[type]:patient&lt;/nowiki&gt;}}<br /> {{fhir|&lt;nowiki&gt;_include=[type]:medication&lt;/nowiki&gt;}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that have Carbasalaatcalcium Sandoz 600 30 as medication and includes the Medication resource in the search results.<br /> &lt;pre&gt;GET [base]/MedicationRequest?medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&amp;_include=MedicationRequest:medication&lt;/pre&gt;<br /> |}<br /> <br /> The following custom search parameters are defined for this transaction:<br /> <br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/pharmaceutical-treatment-identifier|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/category|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/period-of-use|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> <br /> ==== Retrieve all medication data ====<br /> To retrieve all known medication data, a client has to execute the following requests to retrieve all known medication data per building block, including referenced Medication resources:<br /> <br /> &lt;pre&gt;<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&amp;_include=MedicationStatement:medication<br /> GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;_include=MedicationStatement:medication<br /> &lt;/pre&gt;<br /> <br /> Note that in this transaction, these search requests are always executed in the context of a single patient and thus should include a patient identification mechanism (see [[#Patient_identification|‘Patient identification’]]).<br /> <br /> === Serve (response message) ===<br /> The server returns an HTTP Status code appropriate to the processing outcome and returns a Bundle, with {{fhir|Bundle.type}} = {{term|searchset}}, including the resources matching the search query medication data. The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> &lt;section end=medmij3 /&gt;<br /> == Medication data (Send/Receive) ==<br /> The send medication data transaction is used by the client to send medication data to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.375_20220630000000 Medication data (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.376-2022-06-30T000000.html Sending medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication data}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication data<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because medication data consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below. Because of the informative nature of the transaction, '''no''' [[#Actionable_tag|{{term|actionable}} tags]] shall be present.<br /> <br /> === Receive (response message) ===<br /> The server checks each resource present within the Bundle it receives for the absence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication overview (Retrieve/Serve) ==<br /> The retrieve medication overview transaction is used by the client to retrieve a medication overview from the server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.388_20220630000000 Medication overview (PULL)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.389-2022-06-30T000000.html Retrieving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOR<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Retrieve/serve medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.390-2022-06-30T000000.html Serving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain a patient's medication overview, they issue a retrieve medication overview request message. This message uses an extended operation on the RESTful API to obtain a medication overview from a server. An operation is needed because the server will formulate the content of the response based on its internal business logic. The medication overview can not easily be described by standardized RESTful requests. <br /> <br /> The client executes a {{Simplifier|http://nictiz.nl/fhir/OperationDefinition/Medication-Overview|nictiz.fhir.nl.r4.medicationprocess9|title=medication-overview operation}} with an HTTP GET command conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query.<br /> <br /> &lt;pre&gt;<br /> GET [base]/$medication-overview<br /> &lt;/pre&gt;<br /> <br /> === Serve (response message) ===<br /> 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.<br /> <br /> 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].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication overview (Send/Receive) ==<br /> The send medication overview transaction is used by the client to send a medication overview to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.391_20220630000000 Medication overview (PUSH)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.392-2022-06-30T000000.html Sending medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication overview<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication overview consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> 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.<br /> <br /> 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].<br /> <br /> === Receive (response message) ===<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication prescription (Send/Receive) ==<br /> The send medication prescription transaction is used by the client to send a request to dispense medication (Dutch: verstrekkingsverzoek) or process modifications to a medication agreement (Dutch: medicatieafspraak) to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.141-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.394_20220630000000 Medication prescription (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.395-2022-06-30T000000.html Sending medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescription|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication prescription}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescription-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}) and optionally a DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below<br /> <br /> The mp-MedicationPrescription-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the MedicationAgreement and DispenseRequest building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|order}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Medication_prescription_processing_.28Send.2FReceive.29|‘Send medication prescription processing’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication prescription processing (Send/Receive) ==<br /> The send medication prescription processing transaction is used by the client to send data on the processing of a medication agreement (Dutch: medicatieafspraak) and possibly a dispense request (Dutch: verstrekkingsverzoek), in the form of an administration agreement (Dutch: toedieningsafspraak) and optionally a medication dispense (Dutch: medicatieverstrekking).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.143-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.406_20220630000000 Medication prescription processing (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.407-2022-06-30T000000.html Sending data on processing of medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescriptionProcessing|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication prescription processing}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving data on processing of medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because data on processing a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescriptionProcessing-Bundle profile, which contains at least an AdministrationAgreement building block and optionally a MedicationDispense building block. Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-MedicationPrescriptionProcessing-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the AdministrationAgreement and MedicationDispense building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Proposal dispense request (Send/Receive) ==<br /> The send proposal dispense request transaction is used by the client to inform the server about a new or modified proposal dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.400_20220630000000 Proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.401-2022-06-30T000000.html Sending proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal dispense request consists of a DispenseRequest building block along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalDispenseRequest-Bundle profile, which contains one DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalDispenseRequest-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the DispenseRequest building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_dispense_request_.28Send.2FReceive.29|‘Send reply proposal dispense request’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Reply proposal dispense request (Send/Receive) ==<br /> The send reply proposal dispense request transaction is used by the client to inform the server about a reply on a proposed dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.403_20220630000000 Reply proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.404-2022-06-30T000000.html Sending reply proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive reply proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal dispense request consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalDispenseRequest-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalDispenseRequest profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed dispense request that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalDispenseRequest-Bundle profile).<br /> <br /> The mp-ReplyProposalDispenseRequest profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Proposal medication agreement (Send/Receive) ==<br /> The send proposal medication agreement transaction is used by the client to inform the server about a new or modified proposal medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.397_20220630000000 Proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.398-2022-06-30T000000.html Sending proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal medication agreement consists of a MedicationAgreement building block along with supporting resources, a {{term|transaction}} interaction is used.<br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalMedicationAgreement-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalMedicationAgreement-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the MedicationAgreement building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_medication_agreement_.28Send.2FReceive.29|‘Send reply proposal medication agreement’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Reply proposal medication agreement (Send/Receive) ==<br /> The send reply proposal medication agreement transaction is used by the client to inform the server about a reply on a proposed medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.445_20220630000000 Reply proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.446-2022-06-30T000000.html Sending reply proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive reply proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal medication agreement consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalMedicationAgreement-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalMedicationAgreement profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed medication agreement that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalMedicationAgreement-Bundle profile).<br /> <br /> The mp-ReplyProposalMedicationAgreement profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> =Release notes=<br /> Release notes can be found [[mp:V3.0.0-beta.3_releasenotes|here]].<br /> <br /> =Footnotes=<br /> &lt;references/&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=mp:V3.0.0-rc.2_MedicationProcess9_FHIR&diff=206668 2024-03-06T20:42:08Z

<p>Luud Slagter: /* Retrieve all medication data */</p> <hr /> <div>__NOINDEX__<br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide Medication Process 9 version {{VersieInfo|mp9|release=V3.0.0}} }}<br /> <br /> __TOC__<br /> <br /> = Introduction =<br /> 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.<br /> <br /> 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.<br /> <br /> This IG first describes the boundaries and relationships in place, after which the implementation is described per transaction.<br /> <br /> = Boundaries and relationships =<br /> == Building blocks and profiles ==<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> Because the way 90 million numbers are exchanged is not compatible with the 2020 publication of zib PharmaceuticalProduct, a fork of the corresponding nl-core profile called 'mp-PharmaceuticalProduct' has been introduced.<br /> <br /> {{NoteBoxNictizR4Package|p1=nictiz.fhir.nl.r4.medicationprocess9|v1={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|p2=nictiz.fhir.nl.r4.nl-core|v2={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> <br /> 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:<br /> * MP9 version 2.0.0 makes use of version 1.0.0 of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package;<br /> * MP9 version 3.0.0-beta.x makes use of version 2.0.0-beta.x of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package.<br /> <br /> === Medication building blocks ===<br /> <br /> As described above, the main medication building blocks have no dependency on any zib2020 counterparts, resulting in so-called ‘mp’ profiles. Moreover, note that the building block VariableDosingRegimen does not have a zib counterpart, hence it makes sense to include it as an mp profile as well.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |}<br /> <br /> === Supporting building blocks ===<br /> <br /> Additionally, the standard uses several supporting building blocks referenced from the main medication building blocks. All supporting building blocks are part of the [[FHIR:V1.0_FHIR_IG_R4#Functional_definitions|‘nl-core’ package]]&lt;ref&gt;Although the nl-core package is still in beta-status, HL7 Netherlands has validated the profiles mentioned and assigned the status 'STU-NL' for use in the MP9 Kickstart, see [[Media:HL7_Nederland_disclaimer_STU-NL.pdf]]&lt;/ref&gt;.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> Note the following:<br /> * Each occurrence of the zib HealthProfessional is normally represented by '''two''' FHIR resources: an instance of nl-core-HealthProfessional-PractitionerRole and an instance of nl-core-HealthProfessional-Practitioner. Sending systems should only fill the reference to the PractitionerRole instance where relevant. Receiving systems can resolve the reference to the Practitioner resource from that PractitionerRole instance.<br /> * The zib HealthcareProvider is mapped to both a Location and Organization profile. Most often, the Location profile acts as the focal resource, because most references to this zib are concerned about the recording of the physical location where the care to patient/client takes place rather than the organizational information. For the latter, the profile on Organization is used which is referenced using the {{fhir|Location.managingOrganization}} element. Sending systems should only fill the reference to the Location instance where relevant. Incidentally, concepts that are only concerned with organizational information can refer to the Organization instance.<br /> <br /> === Transaction specific profiles ===<br /> <br /> For several transactions, additional profiles are provided. For each transaction the profile relevant is explicitly mentioned in the corresponding subsection.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |}<br /> <br /> ====Bundle profiles====<br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == Mappings between profiles and data set ==<br /> 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.<br /> <br /> 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:<br /> * 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)<br /> ** 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.<br /> ** 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.<br /> * If an element in the functional definition is removed<br /> ** and the element had a zib mapping applied (not on an extension), the zib mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> ** and the element had a mapping applied to the previous version of MP9 (not on an extension), that mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> * If an element in the functional definition is removed and the element had a mapping applied on an extension, that extension is removed entirely. In particular no {{term|[DEPRECATED]}} mapping will be visible in the FHIR profile. This is done to ensure no redundant extensions remain in the FHIR profiles.<br /> <br /> Moreover, all mappings to earlier versions of MP9 (i.e. versions before the previous version) are entirely removed.<br /> <br /> Following the procedure outlined above thus results in the following:<br /> * 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.<br /> * All incompatible changes made in the latest version with respect to the previous version are marked.<br /> * Exceptions are extensions that would otherwise only contain deprecated mappings; these are removed fully.<br /> <br /> 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’]].<br /> <br /> 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.<br /> <br /> 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]].<br /> <br /> == Pharmaceutical treatment ==<br /> 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.<br /> <br /> == Patient identification ==<br /> This implementation guide assumes that the client system is able to make a connection to the right server that contains the patient's information. It does not provide information on finding the right server nor does it provide information about security. Moreover, each transaction is performed in the context of a specific patient, whose context might have been established using the authentication mechanisms described in external specifications such as the MedMij ‘Afsprakenstelsel’ or through the usage of search parameters for patient identification. <br /> <br /> Each server is required to perform filtering based on the patient associated with the context for the request or based on the patient identification search parameters, which is a [https://www.hl7.org/fhir/r4/search.html#chaining chained search parameter] for all resource types except Patient, so only the records associated with the authenticated patient are returned.<br /> <br /> When patient identification requires the use of search parameters, the following search parameters SHALL be supported:<br /> * Patient: {{fhir|identifier}}<br /> * MedicationRequest: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationDispense: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationStatement: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationAdministration: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> <br /> An example of a request that retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233:<br /> <br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> <br /> Note: All request examples in this document do not include patient identification mechanisms, partly because we want to generalize this technical design as much as possible (it being applicable to both MedMij and other contexts), and partly because this would convolute all search request examples. Requesters are assumed to include these if necessary. Since there currently are only transactions in the context of a single patient, the patient identification mechanism is actually implicitly assumed to be present in all search requests.<br /> <br /> == Resource identification ==<br /> 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}}.<br /> <br /> 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 &lt;code&gt;@root&lt;/code&gt; and &lt;code&gt;@extension&lt;/code&gt; (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.<br /> <br /> 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|release=V3.0.0}}}} 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]].<br /> <br /> == Differentiating between transactions ==<br /> All transactions described in this IG use the same medication building blocks in different combinations and settings, making it necessary to differentiate between them. Several mechanisms are used to achieve this. Aside from PUSH/PULL, the type of medication building blocks, supporting resources like List and Communication for specific transactions and fixing the value of specific FHIR elements in applicable profiles, the {{term|actionable}} tag is used. The latter is described more in depth in the following section. Next to that, a summarizing table is provided.<br /> <br /> Note that {{fhir|Resource.meta.profile}}, although present in each building block (see [[FHIR:V1.0_FHIR_IG_R4#Profile_use_and_declaration|the general FHIR IG on ‘Profile use and declaration’]]), SHOULD [https://hl7.org/fhir/r4/resource.html#profile-tags not be used for identification of the building block type] and therefore for differentiating between transactions.<br /> <br /> === Actionable tag ===<br /> To differentiate between sending or serving building blocks that are either of informative nature or of actionable nature, the {{term|actionable}} tag is used. [https://hl7.org/fhir/r4/resource.html#tag Tags] are {{datatype|Coding}} elements present in {{fhir|Resource.meta.tag}} used for workflow management.<br /> <br /> If applicable, the profiles used by a transaction require the use of {{fhir|.meta.tag}} with {{fhir|.system}} = {{term|&lt;nowiki&gt;http://terminology.hl7.org/CodeSystem/common-tags&lt;/nowiki&gt;}} and {{fhir|.code}} = {{term|actionable}} to indicate that the resource is part of a request intended to be acted upon. The absence of this tag indicates that the resource is merely of informative nature.<br /> <br /> It is up to systems to determine how and when the transactions using the {{term|actionable}} tag are handled from a functional perspective. Systems may store the resource including the {{term|actionable}} tag or remove it either upon storing or when the request is acted upon. However, systems SHALL make sure the tag is removed when serving or sending the resource as part of an informative transaction.<br /> <br /> === Summarizing table ===<br /> {| class=&quot;wikitable&quot; <br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | PUSH/PULL<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building blocks<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | {{term|actionable}} tag<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR element value<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Other<br /> |-<br /> | Medication data (Retrieve/Serve)<br /> | PULL<br /> | One or more of all building blocks<br /> | No<br /> |<br /> | <br /> |-<br /> | Medication data (Send/Receive)<br /> | PUSH<br /> | One or more of all building blocks<br /> | No<br /> |<br /> |<br /> |-<br /> | Medication overview (Retrieve/Serve)<br /> | PULL<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication overview (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication prescription (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, DispenseRequest (optional)<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|order}} (for both MedicationAgreement and DispenseRequest building blocks)<br /> | <br /> |-<br /> | Medication prescription processing (Send/Receive)<br /> | PUSH<br /> | AdministrationAgreement, MedicationDispense (optional)<br /> | Yes<br /> | <br /> | <br /> |-<br /> | Proposal dispense request (Send/Receive)<br /> | PUSH<br /> | DispenseRequest<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal dispense request (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to DispenseRequest<br /> |-<br /> | Proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to MedicationAgreement<br /> |}<br /> <br /> = Transactions =<br /> 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’.<br /> &lt;section begin=medmij1 /&gt;<br /> == Medication data (Retrieve/Serve) ==<br /> The retrieve medication data transaction is used by the client to retrieve medication data from a server. The client can retrieve its desired information by searching for specific medication building blocks.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.372_20220630000000 Medication data (PULL)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.373-2022-06-30T000000.html Retrieving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGR<br /> &lt;section end=medmij1 /&gt;<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Retrieve/serve medication data}}<br /> &lt;section begin=medmij2 /&gt;<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.374-2022-06-30T000000.html Serving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain all medication data or specific parts matching various parameters, they issue a retrieve medication data request message. This message uses the HTTP GET method parameterized query against the server's medication FHIR endpoints. These endpoints can be one of the following:<br /> * MedicationRequest<br /> * MedicationDispense<br /> * MedicationStatement<br /> * MedicationAdministration<br /> <br /> The search interaction is performed by an HTTP GET conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query. Multiple request messages may be needed to retrieve all desired information.<br /> <br /> &lt;pre&gt;GET [base]/[type]{?[parameters]}&lt;/pre&gt;<br /> <br /> ==== Search parameters ====<br /> All search parameters listed in the table below SHALL be supported for processing by servers and MAY be supported by clients.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | MP9 search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Description<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Example<br /> &lt;section end=medmij2 /&gt;<br /> |-<br /> | PatientIdentificationNumber<br /> | Search on patient.<br /> | {{fhir|patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;&gt;This search parameter only needs to be supported when patient identification requires the use of search parameters, see [[#Patient_identification|section 2.4]].&lt;/ref&gt;<br /> {{fhir|subject:Patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;/&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233.<br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> &lt;section begin=medmij3 /&gt;<br /> |-<br /> | Identification<br /> | Search on identifier.<br /> | {{fhir|identifier}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves a MedicationRequest resource with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?identifier=http://example.nl/fhir/NamingSystem/MedicationRequest|999922448&lt;/pre&gt;<br /> |-<br /> | Identification<br /> | Search on the pharmaceutical treatment identifier. <br /> Note: retrieval of all medication resources belonging to one pharmaceutical treatment requires to search on all medication resource types.<br /> | {{fhir|pharmaceutical-treatment-identifier}} &lt;ref name=&quot;custom-searchparameter&quot;&gt;The search parameter consists of a custom FHIR search parameter not represented in the FHIR specification. Note that for {{fhir|MedicationRequest.category}} and {{fhir|MedicationStatement.category}} a core search parameter is available, hence no custom one is needed in those cases.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that are part of a pharmaceutical treatment with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?pharmaceutical-treatment-identifier=http://example.nl/fhir/NamingSystem/pharmaceuticaltreatment|1247848&lt;/pre&gt;<br /> |-<br /> | rowspan=&quot;4&quot; | Type<br /> | rowspan=&quot;4&quot; | Search on type of medication building block. <br /> | rowspan=&quot;4&quot; | {{fhir|category}} &lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block DispenseRequest.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block VariableDosingRegimen.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&lt;/pre&gt;<br /> |-<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&lt;/pre&gt;<br /> Retrieves all MedicationDispense resources that represent the building block AdministrationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&lt;/pre&gt;<br /> |-<br /> | MedicationStatement<br /> | Retrieves all MedicationStatement resources that represent the building block MedicationUse2.<br /> &lt;pre&gt;GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&lt;/pre&gt;<br /> |-<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&lt;/pre&gt;<br /> |-<br /> | MedicationCode<br /> | Search on medication code.<br /> | {{fhir|medication.code}}&lt;ref&gt;[https://www.hl7.org/fhir/r4/search.html#chaining Chained search parameter]: searches the medicationReference required in each building block for its {{fhir|.code}}.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and have Carbasalaatcalcium Sandoz 600 30 as medication.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&lt;/pre&gt;<br /> |-<br /> | PeriodOfUse<br /> | 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.<br /> Whenever a search is done on the MedicationAgreement, VariableDosingRegimen or AdministrationAgreement building blocks it is required to also include the latest stopped building blocks of that kind within each pharmaceutical treatment, even if these have a period of use outside the PeriodOfUse that is being searched on.<br /> | {{fhir|period-of-use}}&lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement&lt;ref&gt;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.&lt;/ref&gt;<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and were in effect from 01-01-2010.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;period-of-use=ge2010-01-01&lt;/pre&gt;<br /> |-<br /> | DispensePeriod <br /> | Returns all medication dispenses within the specified time period.<br /> | {{fhir|whenhandedover}}<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense and were handed over within a 2 year period.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;whenhandedover=ge2010-01-01&amp;whenhandedover=le2011-12-31&lt;/pre&gt;<br /> |-<br /> | AdministrationPeriod <br /> | Returns all medication administrations within the specified time period.<br /> | {{fhir|effective-time}}<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2 and where administration happened on a specific day.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;effective-time=eq2022-01-01&lt;/pre&gt;<br /> |-<br /> | -<br /> | The client may request that the server returns resources related to the search results, in order to reduce the overall network delay of repeated retrievals of related resources.<br /> Supporting the include of the Patient and Medication resources referenced by building blocks is required. Others (Organization, Location, PractitionerRole, Practitioner, RelatedPerson, Observation) are optional. However: all resources referenced per literal reference SHALL be resolvable [[FHIR:V1.0_FHIR_IG_R4#Including_referenced_resources|per the Nictiz IG]].<br /> | {{fhir|&lt;nowiki&gt;_include=[type]:patient&lt;/nowiki&gt;}}<br /> {{fhir|&lt;nowiki&gt;_include=[type]:medication&lt;/nowiki&gt;}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that have Carbasalaatcalcium Sandoz 600 30 as medication and includes the Medication resource in the search results.<br /> &lt;pre&gt;GET [base]/MedicationRequest?medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&amp;_include=MedicationRequest:medication&lt;/pre&gt;<br /> |}<br /> <br /> The following custom search parameters are defined for this transaction:<br /> <br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/pharmaceutical-treatment-identifier|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/category|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/period-of-use|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> <br /> ==== Retrieve all medication data ====<br /> To retrieve all known medication data, a client has to execute the following requests to retrieve all known medication data per building block, including referenced Medication resources:<br /> <br /> &lt;pre&gt;<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&amp;_include=MedicationStatement:medication<br /> GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;_include=MedicationStatement:medication<br /> &lt;/pre&gt;<br /> <br /> Note that in the current transactions, these search requests are always executed in the context of a single patient and thus should include a patient identification mechanism (see [[#Patient_identification|‘Patient identification’]]).<br /> <br /> === Serve (response message) ===<br /> The server returns an HTTP Status code appropriate to the processing outcome and returns a Bundle, with {{fhir|Bundle.type}} = {{term|searchset}}, including the resources matching the search query medication data. The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> &lt;section end=medmij3 /&gt;<br /> == Medication data (Send/Receive) ==<br /> The send medication data transaction is used by the client to send medication data to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.375_20220630000000 Medication data (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.376-2022-06-30T000000.html Sending medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication data}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication data<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because medication data consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below. Because of the informative nature of the transaction, '''no''' [[#Actionable_tag|{{term|actionable}} tags]] shall be present.<br /> <br /> === Receive (response message) ===<br /> The server checks each resource present within the Bundle it receives for the absence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication overview (Retrieve/Serve) ==<br /> The retrieve medication overview transaction is used by the client to retrieve a medication overview from the server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.388_20220630000000 Medication overview (PULL)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.389-2022-06-30T000000.html Retrieving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOR<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Retrieve/serve medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.390-2022-06-30T000000.html Serving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain a patient's medication overview, they issue a retrieve medication overview request message. This message uses an extended operation on the RESTful API to obtain a medication overview from a server. An operation is needed because the server will formulate the content of the response based on its internal business logic. The medication overview can not easily be described by standardized RESTful requests. <br /> <br /> The client executes a {{Simplifier|http://nictiz.nl/fhir/OperationDefinition/Medication-Overview|nictiz.fhir.nl.r4.medicationprocess9|title=medication-overview operation}} with an HTTP GET command conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query.<br /> <br /> &lt;pre&gt;<br /> GET [base]/$medication-overview<br /> &lt;/pre&gt;<br /> <br /> === Serve (response message) ===<br /> 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.<br /> <br /> 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].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication overview (Send/Receive) ==<br /> The send medication overview transaction is used by the client to send a medication overview to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.391_20220630000000 Medication overview (PUSH)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.392-2022-06-30T000000.html Sending medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication overview<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication overview consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> 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.<br /> <br /> 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].<br /> <br /> === Receive (response message) ===<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication prescription (Send/Receive) ==<br /> The send medication prescription transaction is used by the client to send a request to dispense medication (Dutch: verstrekkingsverzoek) or process modifications to a medication agreement (Dutch: medicatieafspraak) to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.141-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.394_20220630000000 Medication prescription (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.395-2022-06-30T000000.html Sending medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescription|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication prescription}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescription-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}) and optionally a DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below<br /> <br /> The mp-MedicationPrescription-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the MedicationAgreement and DispenseRequest building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|order}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Medication_prescription_processing_.28Send.2FReceive.29|‘Send medication prescription processing’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication prescription processing (Send/Receive) ==<br /> The send medication prescription processing transaction is used by the client to send data on the processing of a medication agreement (Dutch: medicatieafspraak) and possibly a dispense request (Dutch: verstrekkingsverzoek), in the form of an administration agreement (Dutch: toedieningsafspraak) and optionally a medication dispense (Dutch: medicatieverstrekking).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.143-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.406_20220630000000 Medication prescription processing (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.407-2022-06-30T000000.html Sending data on processing of medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescriptionProcessing|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication prescription processing}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving data on processing of medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because data on processing a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescriptionProcessing-Bundle profile, which contains at least an AdministrationAgreement building block and optionally a MedicationDispense building block. Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-MedicationPrescriptionProcessing-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the AdministrationAgreement and MedicationDispense building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Proposal dispense request (Send/Receive) ==<br /> The send proposal dispense request transaction is used by the client to inform the server about a new or modified proposal dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.400_20220630000000 Proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.401-2022-06-30T000000.html Sending proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal dispense request consists of a DispenseRequest building block along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalDispenseRequest-Bundle profile, which contains one DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalDispenseRequest-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the DispenseRequest building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_dispense_request_.28Send.2FReceive.29|‘Send reply proposal dispense request’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Reply proposal dispense request (Send/Receive) ==<br /> The send reply proposal dispense request transaction is used by the client to inform the server about a reply on a proposed dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.403_20220630000000 Reply proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.404-2022-06-30T000000.html Sending reply proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive reply proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal dispense request consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalDispenseRequest-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalDispenseRequest profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed dispense request that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalDispenseRequest-Bundle profile).<br /> <br /> The mp-ReplyProposalDispenseRequest profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Proposal medication agreement (Send/Receive) ==<br /> The send proposal medication agreement transaction is used by the client to inform the server about a new or modified proposal medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.397_20220630000000 Proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.398-2022-06-30T000000.html Sending proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal medication agreement consists of a MedicationAgreement building block along with supporting resources, a {{term|transaction}} interaction is used.<br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalMedicationAgreement-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalMedicationAgreement-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the MedicationAgreement building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_medication_agreement_.28Send.2FReceive.29|‘Send reply proposal medication agreement’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Reply proposal medication agreement (Send/Receive) ==<br /> The send reply proposal medication agreement transaction is used by the client to inform the server about a reply on a proposed medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.445_20220630000000 Reply proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.446-2022-06-30T000000.html Sending reply proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive reply proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal medication agreement consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalMedicationAgreement-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalMedicationAgreement profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed medication agreement that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalMedicationAgreement-Bundle profile).<br /> <br /> The mp-ReplyProposalMedicationAgreement profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> =Release notes=<br /> Release notes can be found [[mp:V3.0.0-beta.3_releasenotes|here]].<br /> <br /> =Footnotes=<br /> &lt;references/&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=mp:V3.0.0-rc.2_MedicationProcess9_FHIR&diff=206667 2024-03-06T20:41:55Z

<p>Luud Slagter: /* Patient identification */</p> <hr /> <div>__NOINDEX__<br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide Medication Process 9 version {{VersieInfo|mp9|release=V3.0.0}} }}<br /> <br /> __TOC__<br /> <br /> = Introduction =<br /> 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.<br /> <br /> 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.<br /> <br /> This IG first describes the boundaries and relationships in place, after which the implementation is described per transaction.<br /> <br /> = Boundaries and relationships =<br /> == Building blocks and profiles ==<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> Because the way 90 million numbers are exchanged is not compatible with the 2020 publication of zib PharmaceuticalProduct, a fork of the corresponding nl-core profile called 'mp-PharmaceuticalProduct' has been introduced.<br /> <br /> {{NoteBoxNictizR4Package|p1=nictiz.fhir.nl.r4.medicationprocess9|v1={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|p2=nictiz.fhir.nl.r4.nl-core|v2={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> <br /> 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:<br /> * MP9 version 2.0.0 makes use of version 1.0.0 of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package;<br /> * MP9 version 3.0.0-beta.x makes use of version 2.0.0-beta.x of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package.<br /> <br /> === Medication building blocks ===<br /> <br /> As described above, the main medication building blocks have no dependency on any zib2020 counterparts, resulting in so-called ‘mp’ profiles. Moreover, note that the building block VariableDosingRegimen does not have a zib counterpart, hence it makes sense to include it as an mp profile as well.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |}<br /> <br /> === Supporting building blocks ===<br /> <br /> Additionally, the standard uses several supporting building blocks referenced from the main medication building blocks. All supporting building blocks are part of the [[FHIR:V1.0_FHIR_IG_R4#Functional_definitions|‘nl-core’ package]]&lt;ref&gt;Although the nl-core package is still in beta-status, HL7 Netherlands has validated the profiles mentioned and assigned the status 'STU-NL' for use in the MP9 Kickstart, see [[Media:HL7_Nederland_disclaimer_STU-NL.pdf]]&lt;/ref&gt;.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> Note the following:<br /> * Each occurrence of the zib HealthProfessional is normally represented by '''two''' FHIR resources: an instance of nl-core-HealthProfessional-PractitionerRole and an instance of nl-core-HealthProfessional-Practitioner. Sending systems should only fill the reference to the PractitionerRole instance where relevant. Receiving systems can resolve the reference to the Practitioner resource from that PractitionerRole instance.<br /> * The zib HealthcareProvider is mapped to both a Location and Organization profile. Most often, the Location profile acts as the focal resource, because most references to this zib are concerned about the recording of the physical location where the care to patient/client takes place rather than the organizational information. For the latter, the profile on Organization is used which is referenced using the {{fhir|Location.managingOrganization}} element. Sending systems should only fill the reference to the Location instance where relevant. Incidentally, concepts that are only concerned with organizational information can refer to the Organization instance.<br /> <br /> === Transaction specific profiles ===<br /> <br /> For several transactions, additional profiles are provided. For each transaction the profile relevant is explicitly mentioned in the corresponding subsection.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |}<br /> <br /> ====Bundle profiles====<br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == Mappings between profiles and data set ==<br /> 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.<br /> <br /> 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:<br /> * 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)<br /> ** 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.<br /> ** 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.<br /> * If an element in the functional definition is removed<br /> ** and the element had a zib mapping applied (not on an extension), the zib mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> ** and the element had a mapping applied to the previous version of MP9 (not on an extension), that mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> * If an element in the functional definition is removed and the element had a mapping applied on an extension, that extension is removed entirely. In particular no {{term|[DEPRECATED]}} mapping will be visible in the FHIR profile. This is done to ensure no redundant extensions remain in the FHIR profiles.<br /> <br /> Moreover, all mappings to earlier versions of MP9 (i.e. versions before the previous version) are entirely removed.<br /> <br /> Following the procedure outlined above thus results in the following:<br /> * 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.<br /> * All incompatible changes made in the latest version with respect to the previous version are marked.<br /> * Exceptions are extensions that would otherwise only contain deprecated mappings; these are removed fully.<br /> <br /> 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’]].<br /> <br /> 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.<br /> <br /> 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]].<br /> <br /> == Pharmaceutical treatment ==<br /> 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.<br /> <br /> == Patient identification ==<br /> This implementation guide assumes that the client system is able to make a connection to the right server that contains the patient's information. It does not provide information on finding the right server nor does it provide information about security. Moreover, each transaction is performed in the context of a specific patient, whose context might have been established using the authentication mechanisms described in external specifications such as the MedMij ‘Afsprakenstelsel’ or through the usage of search parameters for patient identification. <br /> <br /> Each server is required to perform filtering based on the patient associated with the context for the request or based on the patient identification search parameters, which is a [https://www.hl7.org/fhir/r4/search.html#chaining chained search parameter] for all resource types except Patient, so only the records associated with the authenticated patient are returned.<br /> <br /> When patient identification requires the use of search parameters, the following search parameters SHALL be supported:<br /> * Patient: {{fhir|identifier}}<br /> * MedicationRequest: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationDispense: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationStatement: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationAdministration: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> <br /> An example of a request that retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233:<br /> <br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> <br /> Note: All request examples in this document do not include patient identification mechanisms, partly because we want to generalize this technical design as much as possible (it being applicable to both MedMij and other contexts), and partly because this would convolute all search request examples. Requesters are assumed to include these if necessary. Since there currently are only transactions in the context of a single patient, the patient identification mechanism is actually implicitly assumed to be present in all search requests.<br /> <br /> == Resource identification ==<br /> 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}}.<br /> <br /> 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 &lt;code&gt;@root&lt;/code&gt; and &lt;code&gt;@extension&lt;/code&gt; (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.<br /> <br /> 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|release=V3.0.0}}}} 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]].<br /> <br /> == Differentiating between transactions ==<br /> All transactions described in this IG use the same medication building blocks in different combinations and settings, making it necessary to differentiate between them. Several mechanisms are used to achieve this. Aside from PUSH/PULL, the type of medication building blocks, supporting resources like List and Communication for specific transactions and fixing the value of specific FHIR elements in applicable profiles, the {{term|actionable}} tag is used. The latter is described more in depth in the following section. Next to that, a summarizing table is provided.<br /> <br /> Note that {{fhir|Resource.meta.profile}}, although present in each building block (see [[FHIR:V1.0_FHIR_IG_R4#Profile_use_and_declaration|the general FHIR IG on ‘Profile use and declaration’]]), SHOULD [https://hl7.org/fhir/r4/resource.html#profile-tags not be used for identification of the building block type] and therefore for differentiating between transactions.<br /> <br /> === Actionable tag ===<br /> To differentiate between sending or serving building blocks that are either of informative nature or of actionable nature, the {{term|actionable}} tag is used. [https://hl7.org/fhir/r4/resource.html#tag Tags] are {{datatype|Coding}} elements present in {{fhir|Resource.meta.tag}} used for workflow management.<br /> <br /> If applicable, the profiles used by a transaction require the use of {{fhir|.meta.tag}} with {{fhir|.system}} = {{term|&lt;nowiki&gt;http://terminology.hl7.org/CodeSystem/common-tags&lt;/nowiki&gt;}} and {{fhir|.code}} = {{term|actionable}} to indicate that the resource is part of a request intended to be acted upon. The absence of this tag indicates that the resource is merely of informative nature.<br /> <br /> It is up to systems to determine how and when the transactions using the {{term|actionable}} tag are handled from a functional perspective. Systems may store the resource including the {{term|actionable}} tag or remove it either upon storing or when the request is acted upon. However, systems SHALL make sure the tag is removed when serving or sending the resource as part of an informative transaction.<br /> <br /> === Summarizing table ===<br /> {| class=&quot;wikitable&quot; <br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | PUSH/PULL<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building blocks<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | {{term|actionable}} tag<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR element value<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Other<br /> |-<br /> | Medication data (Retrieve/Serve)<br /> | PULL<br /> | One or more of all building blocks<br /> | No<br /> |<br /> | <br /> |-<br /> | Medication data (Send/Receive)<br /> | PUSH<br /> | One or more of all building blocks<br /> | No<br /> |<br /> |<br /> |-<br /> | Medication overview (Retrieve/Serve)<br /> | PULL<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication overview (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication prescription (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, DispenseRequest (optional)<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|order}} (for both MedicationAgreement and DispenseRequest building blocks)<br /> | <br /> |-<br /> | Medication prescription processing (Send/Receive)<br /> | PUSH<br /> | AdministrationAgreement, MedicationDispense (optional)<br /> | Yes<br /> | <br /> | <br /> |-<br /> | Proposal dispense request (Send/Receive)<br /> | PUSH<br /> | DispenseRequest<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal dispense request (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to DispenseRequest<br /> |-<br /> | Proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to MedicationAgreement<br /> |}<br /> <br /> = Transactions =<br /> 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’.<br /> &lt;section begin=medmij1 /&gt;<br /> == Medication data (Retrieve/Serve) ==<br /> The retrieve medication data transaction is used by the client to retrieve medication data from a server. The client can retrieve its desired information by searching for specific medication building blocks.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.372_20220630000000 Medication data (PULL)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.373-2022-06-30T000000.html Retrieving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGR<br /> &lt;section end=medmij1 /&gt;<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Retrieve/serve medication data}}<br /> &lt;section begin=medmij2 /&gt;<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.374-2022-06-30T000000.html Serving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain all medication data or specific parts matching various parameters, they issue a retrieve medication data request message. This message uses the HTTP GET method parameterized query against the server's medication FHIR endpoints. These endpoints can be one of the following:<br /> * MedicationRequest<br /> * MedicationDispense<br /> * MedicationStatement<br /> * MedicationAdministration<br /> <br /> The search interaction is performed by an HTTP GET conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query. Multiple request messages may be needed to retrieve all desired information.<br /> <br /> &lt;pre&gt;GET [base]/[type]{?[parameters]}&lt;/pre&gt;<br /> <br /> ==== Search parameters ====<br /> All search parameters listed in the table below SHALL be supported for processing by servers and MAY be supported by clients.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | MP9 search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Description<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Example<br /> &lt;section end=medmij2 /&gt;<br /> |-<br /> | PatientIdentificationNumber<br /> | Search on patient.<br /> | {{fhir|patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;&gt;This search parameter only needs to be supported when patient identification requires the use of search parameters, see [[#Patient_identification|section 2.4]].&lt;/ref&gt;<br /> {{fhir|subject:Patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;/&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233.<br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> &lt;section begin=medmij3 /&gt;<br /> |-<br /> | Identification<br /> | Search on identifier.<br /> | {{fhir|identifier}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves a MedicationRequest resource with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?identifier=http://example.nl/fhir/NamingSystem/MedicationRequest|999922448&lt;/pre&gt;<br /> |-<br /> | Identification<br /> | Search on the pharmaceutical treatment identifier. <br /> Note: retrieval of all medication resources belonging to one pharmaceutical treatment requires to search on all medication resource types.<br /> | {{fhir|pharmaceutical-treatment-identifier}} &lt;ref name=&quot;custom-searchparameter&quot;&gt;The search parameter consists of a custom FHIR search parameter not represented in the FHIR specification. Note that for {{fhir|MedicationRequest.category}} and {{fhir|MedicationStatement.category}} a core search parameter is available, hence no custom one is needed in those cases.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that are part of a pharmaceutical treatment with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?pharmaceutical-treatment-identifier=http://example.nl/fhir/NamingSystem/pharmaceuticaltreatment|1247848&lt;/pre&gt;<br /> |-<br /> | rowspan=&quot;4&quot; | Type<br /> | rowspan=&quot;4&quot; | Search on type of medication building block. <br /> | rowspan=&quot;4&quot; | {{fhir|category}} &lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block DispenseRequest.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block VariableDosingRegimen.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&lt;/pre&gt;<br /> |-<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&lt;/pre&gt;<br /> Retrieves all MedicationDispense resources that represent the building block AdministrationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&lt;/pre&gt;<br /> |-<br /> | MedicationStatement<br /> | Retrieves all MedicationStatement resources that represent the building block MedicationUse2.<br /> &lt;pre&gt;GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&lt;/pre&gt;<br /> |-<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&lt;/pre&gt;<br /> |-<br /> | MedicationCode<br /> | Search on medication code.<br /> | {{fhir|medication.code}}&lt;ref&gt;[https://www.hl7.org/fhir/r4/search.html#chaining Chained search parameter]: searches the medicationReference required in each building block for its {{fhir|.code}}.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and have Carbasalaatcalcium Sandoz 600 30 as medication.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&lt;/pre&gt;<br /> |-<br /> | PeriodOfUse<br /> | 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.<br /> Whenever a search is done on the MedicationAgreement, VariableDosingRegimen or AdministrationAgreement building blocks it is required to also include the latest stopped building blocks of that kind within each pharmaceutical treatment, even if these have a period of use outside the PeriodOfUse that is being searched on.<br /> | {{fhir|period-of-use}}&lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement&lt;ref&gt;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.&lt;/ref&gt;<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and were in effect from 01-01-2010.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;period-of-use=ge2010-01-01&lt;/pre&gt;<br /> |-<br /> | DispensePeriod <br /> | Returns all medication dispenses within the specified time period.<br /> | {{fhir|whenhandedover}}<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense and were handed over within a 2 year period.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;whenhandedover=ge2010-01-01&amp;whenhandedover=le2011-12-31&lt;/pre&gt;<br /> |-<br /> | AdministrationPeriod <br /> | Returns all medication administrations within the specified time period.<br /> | {{fhir|effective-time}}<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2 and where administration happened on a specific day.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;effective-time=eq2022-01-01&lt;/pre&gt;<br /> |-<br /> | -<br /> | The client may request that the server returns resources related to the search results, in order to reduce the overall network delay of repeated retrievals of related resources.<br /> Supporting the include of the Patient and Medication resources referenced by building blocks is required. Others (Organization, Location, PractitionerRole, Practitioner, RelatedPerson, Observation) are optional. However: all resources referenced per literal reference SHALL be resolvable [[FHIR:V1.0_FHIR_IG_R4#Including_referenced_resources|per the Nictiz IG]].<br /> | {{fhir|&lt;nowiki&gt;_include=[type]:patient&lt;/nowiki&gt;}}<br /> {{fhir|&lt;nowiki&gt;_include=[type]:medication&lt;/nowiki&gt;}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that have Carbasalaatcalcium Sandoz 600 30 as medication and includes the Medication resource in the search results.<br /> &lt;pre&gt;GET [base]/MedicationRequest?medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&amp;_include=MedicationRequest:medication&lt;/pre&gt;<br /> |}<br /> <br /> The following custom search parameters are defined for this transaction:<br /> <br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/pharmaceutical-treatment-identifier|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/category|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/period-of-use|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> <br /> ==== Retrieve all medication data ====<br /> To retrieve all known medication data, a client has to execute the following requests to retrieve all known medication data per building block, including referenced Medication resources:<br /> <br /> &lt;pre&gt;<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&amp;_include=MedicationStatement:medication<br /> GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;_include=MedicationStatement:medication<br /> &lt;/pre&gt;<br /> <br /> Note that in the current use cases, these search requests are always executed in the context of a single patient and thus should include a patient identification mechanism (see [[#Patient_identification|‘Patient identification’]]).<br /> <br /> === Serve (response message) ===<br /> The server returns an HTTP Status code appropriate to the processing outcome and returns a Bundle, with {{fhir|Bundle.type}} = {{term|searchset}}, including the resources matching the search query medication data. The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> &lt;section end=medmij3 /&gt;<br /> == Medication data (Send/Receive) ==<br /> The send medication data transaction is used by the client to send medication data to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.375_20220630000000 Medication data (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.376-2022-06-30T000000.html Sending medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication data}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication data<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because medication data consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below. Because of the informative nature of the transaction, '''no''' [[#Actionable_tag|{{term|actionable}} tags]] shall be present.<br /> <br /> === Receive (response message) ===<br /> The server checks each resource present within the Bundle it receives for the absence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication overview (Retrieve/Serve) ==<br /> The retrieve medication overview transaction is used by the client to retrieve a medication overview from the server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.388_20220630000000 Medication overview (PULL)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.389-2022-06-30T000000.html Retrieving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOR<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Retrieve/serve medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.390-2022-06-30T000000.html Serving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain a patient's medication overview, they issue a retrieve medication overview request message. This message uses an extended operation on the RESTful API to obtain a medication overview from a server. An operation is needed because the server will formulate the content of the response based on its internal business logic. The medication overview can not easily be described by standardized RESTful requests. <br /> <br /> The client executes a {{Simplifier|http://nictiz.nl/fhir/OperationDefinition/Medication-Overview|nictiz.fhir.nl.r4.medicationprocess9|title=medication-overview operation}} with an HTTP GET command conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query.<br /> <br /> &lt;pre&gt;<br /> GET [base]/$medication-overview<br /> &lt;/pre&gt;<br /> <br /> === Serve (response message) ===<br /> 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.<br /> <br /> 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].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication overview (Send/Receive) ==<br /> The send medication overview transaction is used by the client to send a medication overview to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.391_20220630000000 Medication overview (PUSH)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.392-2022-06-30T000000.html Sending medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication overview<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication overview consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> 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.<br /> <br /> 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].<br /> <br /> === Receive (response message) ===<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication prescription (Send/Receive) ==<br /> The send medication prescription transaction is used by the client to send a request to dispense medication (Dutch: verstrekkingsverzoek) or process modifications to a medication agreement (Dutch: medicatieafspraak) to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.141-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.394_20220630000000 Medication prescription (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.395-2022-06-30T000000.html Sending medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescription|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication prescription}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescription-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}) and optionally a DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below<br /> <br /> The mp-MedicationPrescription-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the MedicationAgreement and DispenseRequest building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|order}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Medication_prescription_processing_.28Send.2FReceive.29|‘Send medication prescription processing’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication prescription processing (Send/Receive) ==<br /> The send medication prescription processing transaction is used by the client to send data on the processing of a medication agreement (Dutch: medicatieafspraak) and possibly a dispense request (Dutch: verstrekkingsverzoek), in the form of an administration agreement (Dutch: toedieningsafspraak) and optionally a medication dispense (Dutch: medicatieverstrekking).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.143-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.406_20220630000000 Medication prescription processing (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.407-2022-06-30T000000.html Sending data on processing of medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescriptionProcessing|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication prescription processing}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving data on processing of medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because data on processing a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescriptionProcessing-Bundle profile, which contains at least an AdministrationAgreement building block and optionally a MedicationDispense building block. Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-MedicationPrescriptionProcessing-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the AdministrationAgreement and MedicationDispense building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Proposal dispense request (Send/Receive) ==<br /> The send proposal dispense request transaction is used by the client to inform the server about a new or modified proposal dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.400_20220630000000 Proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.401-2022-06-30T000000.html Sending proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal dispense request consists of a DispenseRequest building block along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalDispenseRequest-Bundle profile, which contains one DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalDispenseRequest-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the DispenseRequest building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_dispense_request_.28Send.2FReceive.29|‘Send reply proposal dispense request’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Reply proposal dispense request (Send/Receive) ==<br /> The send reply proposal dispense request transaction is used by the client to inform the server about a reply on a proposed dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.403_20220630000000 Reply proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.404-2022-06-30T000000.html Sending reply proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive reply proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal dispense request consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalDispenseRequest-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalDispenseRequest profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed dispense request that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalDispenseRequest-Bundle profile).<br /> <br /> The mp-ReplyProposalDispenseRequest profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Proposal medication agreement (Send/Receive) ==<br /> The send proposal medication agreement transaction is used by the client to inform the server about a new or modified proposal medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.397_20220630000000 Proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.398-2022-06-30T000000.html Sending proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal medication agreement consists of a MedicationAgreement building block along with supporting resources, a {{term|transaction}} interaction is used.<br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalMedicationAgreement-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalMedicationAgreement-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the MedicationAgreement building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_medication_agreement_.28Send.2FReceive.29|‘Send reply proposal medication agreement’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Reply proposal medication agreement (Send/Receive) ==<br /> The send reply proposal medication agreement transaction is used by the client to inform the server about a reply on a proposed medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.445_20220630000000 Reply proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.446-2022-06-30T000000.html Sending reply proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive reply proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal medication agreement consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalMedicationAgreement-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalMedicationAgreement profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed medication agreement that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalMedicationAgreement-Bundle profile).<br /> <br /> The mp-ReplyProposalMedicationAgreement profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> =Release notes=<br /> Release notes can be found [[mp:V3.0.0-beta.3_releasenotes|here]].<br /> <br /> =Footnotes=<br /> &lt;references/&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=mp:V3.0.0-rc.2_MedicationProcess9_FHIR_for_patient_use_cases&diff=206666 2024-03-06T20:40:49Z

<p>Luud Slagter: /* Patient identification */</p> <hr /> <div>__NOINDEX__<br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide Medication Process 9 version {{VersieInfo|mp9|release=V3.0.0}} for patient use cases}}<br /> {{NoteBox|Deze versie zal worden getoetst tijdens de kickstart medicatieoverdracht. De versie is niet geschikt voor gebruik buiten deze beproeving.}}<br /> <br /> __TOC__<br /> <br /> = Introduction =<br /> This is the implementation guide (IG) for the information standard Medication Process 9 (MP9) version {{VersieInfo|mp9|release=V3.0.0}} for patient use cases (MedMij) using the HL7® FHIR® standard. The MP9 standard for MedMij is described in [[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|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 of both MP9 and MedMij and this version of FHIR.<br /> <br /> This document is a specification of [[mp:V3.0.0_MedicationProcess9_FHIR|FHIR Implementation Guide Medication Process 9]], only applicable to the patient use cases. The guidelines as specified in the [[MedMij:IG:V1/FHIR_IG|MedMij FHIR Implementation Guide]] apply. This document extends the [[FHIR:V1.0_FHIR_IG_R4|general FHIR Implementation Guide]] with the specification of the 'Afsprakenstelsel'.<br /> <br /> This IG first describes the boundaries and relationships where they differ between the MP9 and MedMij IG, after which the implementation is described per relevant transaction.<br /> <br /> = Boundaries and relationships =<br /> Both the [[mp:V3.0.0_MedicationProcess9_FHIR#Boundaries_and_relationships|MP9 Boundaries and relationships]] and the [[MedMij:IG:V1/FHIR_IG#Overarching_principles|MedMij Overarching principles]] apply. The following sections highlight the points where these two documents contradict and provides guidance on which principles to follow.<br /> <br /> == 'Use cases' or 'transactions' ==<br /> Where MP9 uses the term 'transaction', MedMij generally uses the term 'use case'. On this page, the terms are used interchangeable.<br /> <br /> == Patient identification ==<br /> Where MP9 describes the use of {{fhir|patient.identifier}} or {{fhir|subject:Patient.identifier}} search parameters, the MedMij use cases use the authentication method outlined by the [[MedMij:IG:V1/FHIR_IG#Afsprakenstelsel|MedMij 'Afsprakenstelsel']], using Oauth2 tokens.<br /> <br /> = Transactions =<br /> This section describes the FHIR implementation of the Retrieve and Serve Medication Data transactions (for MedMij) listed in [[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|the functional specification]]. Each transaction hyperlinks 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]]).<br /> {{#lst:mp:V3.0.0_MedicationProcess9_FHIR|medmij1}}<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.RetrieveServe.MedMij|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Retrieve/serve medication data (MedMij)}}<br /> {{#lst:mp:V3.0.0_MedicationProcess9_FHIR|medmij2}}<br /> {{#lst:mp:V3.0.0_MedicationProcess9_FHIR|medmij3}}<br /> <br /> =Release notes=<br /> Release notes can be found [[mp:V3.0.0-beta.2_releasenotes|here]].<br /> <br /> =Footnotes=<br /> &lt;references/&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=mp:Medicatieoverdracht_Kickstart&diff=206665 2024-03-06T20:39:53Z

<p>Luud Slagter: /* Specificaties */</p> <hr /> <div>{{DISPLAYTITLE:Kickstart Medicatieoverdracht - Landingspagina documentatie leveranciers (Handboek)}}<br /> <br /> __NUMBEREDHEADINGS__<br /> =ALGEMEEN REFERENTIE=<br /> :*[https://www.zorginzicht.nl/binaries/content/assets/zorginzicht/kwaliteitsinstrumenten/Kwaliteitsstandaard+Overdracht+van+medicatiegegevens+in+de+keten.pdf Kwaliteitsstandaard: richtlijn overdracht van medicatiegegevens in de keten]&lt;br&gt;<br /> <br /> =BOUWDOCUMENTATIE=<br /> {{IssueBox|'''FHIR specs voor versie 3.0.0-beta.3 volgen op 7 maart'''}}<br /> ==Voorbereiding==<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/pva_kickstart/&lt;abbr title=&quot;Het Plan van aanpak versie 3.1 voor de uitvoering van de Kickstart. Het Plan van aanpak versie 3.1 beschrijft het doel, de opzet, aanpak en kaders voor de uitvoering van de Kickstart.&quot;&gt;Plan van aanpak versie 3.1&lt;/abbr&gt;]<br /> <br /> ==Specificaties==<br /> :'''Verzamelbestand informatiestandaarden'''<br /> :*[[mp:V2.0.0_Verwijzing_naar_documentatie_Medicatieproces9_tbv_Kickstart|Verzamelbestand met functionele, technische en infrastructurele documentatie Medicatieproces 9 t.b.v. Kickstart]]<br /> <br /> :'''Voorbereiding'''<br /> :*[[mp:Stap_0_Voorbereiding|Werkzaamheden in stap 0 Voorbereiding]]<br /> <br /> :'''Informatiestandaard Medicatieproces 9.3.0.0-beta.3'''<br /> :*[[mp:V3.0.0-beta_Ontwerp_medicatieproces_9|&lt;abbr title=&quot;Het functioneel ontwerp van de informatiestandaard Medicatieproces 9 Het beschrijft de algemene werking en specifieke praktijksituaties.&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 3.0.0-beta.3 (NL)&lt;/abbr&gt;]] / [[mp:V3.0.0-beta_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 3.0.0-beta.3 (ENG)]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.<br /> &quot;&gt;Medicatieproces 9 versie 3.0.0-beta.3 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> :*[[mp:V3.0.0_MedicationProcess9_FHIR|&lt;abbr title=&quot;FHIR Implementation guide for Medicatieproces 9 versie 3.0.0-beta.3 FHIR in English&quot;&gt;Implementation guide FHIR Medication Process 9 version 3.0.0-beta.3 (ENG) &lt;/abbr&gt;]]<br /> :*[https://simplifier.net/packages/nictiz.fhir.nl.r4.medicationprocess9/2.0.0-beta.1/ FHIR R4 conformance resources for Medication Process 9 (MP9)]<br /> :*[[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|&lt;abbr title=&quot;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.3 voor patiënt usecases&quot;&gt;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.3 voor patiënt usecases&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.3 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.3 for patient use cases &lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.3_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 3.0.0-beta.3&lt;/abbr&gt;]]<br /> :*Gebruikerseisen: [[mp:Besluiten_kernteams|&lt;abbr title=&quot;Deze pagina bevat de besluiten van de kernteams, met (indien van toepassing) de bijbehorende werkproceseisen, gebruikerseisen en -wensen.&quot;&gt;Besluiten kernteams Medicatieproces 9, inclusief gebruikerseisen en -wensen&lt;/abbr&gt;]]<br /> <br /> :'''Informatiestandaard Lab2zorg'''<br /> :*[[mp:LeeswijzerVoorschriftmetnierfunctiewaarde|&lt;abbr title=&quot;De leeswijzer geeft aan welk onderdeel van Lab2zorg binnen de scope van de Kickstart valt en welke documentatie daarop van toepassing is.&quot;&gt;Leeswijzer ten behoeve van het meesturen van de nierfunctiewaarde met het voorschrift&lt;/abbr&gt;]]<br /> :*[[Lab:Vcurrent_Ontwerp_Lab2zorg|&lt;abbr title=&quot;Het functioneel ontwerp van Lab2zorg. In de kickstart wordt het onderdeel lab2zorg gebruikt voor het meesturen van een nierfunctiewaarde met het voorschrift. Deze usecase staat beschreven in paragraaf 2.3 van het functioneel ontwerp lab2zorg.&quot;&gt;Functioneel ontwerp Lab2zorg versie 3.0.0&lt;/abbr&gt;]]<br /> :*[[Lab:Vcurrent_Kwalificatie|&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard uitwisseling laboratoriumgegevens de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties. Voor de kickstart wordt sturen/ontvangen laboratoriumresultaten uit lab2zorg gebruikt.&quot;&gt;Labuitwisseling versie 3.0.0 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]]<br /> :*[[Lab:V3.0.0_FHIR_Lab2zorg|&lt;abbr title=&quot;Technische FHIR specificaties van Lab2zorg in aanvulling op het functioneel ontwerp. Paragraaf 4.3 beschrijft het sturen van laboratoriumresultaten tussen zorgverleners dat in de kickstart gebruikt wordt.&quot;&gt;FHIR Lab2zorg version 3.0.0 (ENG)&lt;/abbr&gt;]]<br /> <br /> :'''Infrastructuur'''<br /> :*[https://decor.nictiz.nl/pub/vzvz/index.php?prefix=mp-vzvz-&lt;abbr title=&quot;&quot;&gt;ART-DECOR Publicatiepagina VZVZ: Medicatieproces op het LSP&lt;/abbr&gt;]<br /> :*[https://zt-medicatieoverdracht.scrollhelp.site/Medicatieoverdracht/Working-version/programma-van-eisen-medicatieoverdracht&lt;abbr title=&quot;De beschikbare Programma van Eisen waaraan de Kickstart deelnemers moeten voldoen. Deze documenten beschrijven de eisen om aan te sluiten op de AORTA-infrastructuur.&quot;&gt;Programma van eisen LSP (bèta)&lt;/abbr&gt;]<br /> :*[https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpublicvzvz.refined.site%2Fspace%2FA8%2F85000200%2FAORTA%2B8.3.0&amp;data=05%7C01%7Ctheunissen%40nictiz.nl%7C52a3bf5378624ff2978e08db8f44c3a3%7C3d542e8da3eb448f998ddd6880dc119c%7C0%7C0%7C638261297740578594%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=6%2FH9yQ0EAHEmGYHgbVoQo995poc34CXlV6UcBP4MSD8%3D&amp;reserved=0&lt;abbr title=&quot;Deze pagina bevat de algemene specificaties van de zorginfrastructuur AORTA v8.3.0.0&quot;&gt;Documentatie AORTA versie 8.3.0.0&lt;/abbr&gt;]<br /> <br /> ==IT-Infrastructuur==<br /> :*[https://decor.nictiz.nl/pub/vzvz/aorta-vzvz-html-20221128T172039/sc-2.16.840.1.113883.2.4.3.111.3.2.3.3-2016-09-20T163842.html Implementatie van de ping-pong toets]<br /> :*[https://decor.nictiz.nl/pub/vzvz/aorta-vzvz-html-20221128T172039/sc-2.16.840.1.113883.2.4.3.111.3.2.3.1-2016-09-20T091642.html Beheren TKID applicatie]<br /> :*[https://public.vzvz.nl/download/attachments/41779447/AORTA_Proces_VWI_Synchronisatie.pdf?api=v2:~:text=Het%20VWI%2Dsynchronisatie%20proces%20biedt,belang%20van%20pati%C3%ABnt%20en%20zorgaanbieder&lt;abbr title=&quot;Dit document beschrijft de procedure die ervoor zorgt dat elke GBZ-beheerder namens de zorgaanbieder kan vaststellen dat elk patiëntgegeven met toestemming van de patiënt op correcte wijze is aangemeld op de VWI.&quot;&gt;Proces VWI synchronisatie&lt;/abbr&gt;]<br /> :*[https://public.vzvz.nl/download/attachments/41779447/AORTA_Sgl_Ontw_Gebeurtenisverwerking.pdf?api=v2&lt;abbr title=&quot;Dit document beschrijft het ontwerp van de gebeurtenisverdeler component (GVE) en de component gebeurtenisafhandelaar (GAF) in de ZIM.&quot;&gt;Ontwerp gebeurtenisverwerking&lt;/abbr&gt;]<br /> :*[https://public.vzvz.nl/download/attachments/41779447/AORTA_Sgl_Ontw_Abonnementenregister.pdf?api=v2&lt;abbr title=&quot;Dit document beschrijft het ontwerp van de abonnementenregister component (ABR) in de ZIM.&quot;&gt;Ontwerp abonnementenregister&lt;/abbr&gt;]<br /> <br /> ==Implementatiehandleidingen==<br /> :*[[mp:Vkickstart_MigratieHybride|&lt;abbr title=&quot;Handleiding Migratie hybride fase Kickstart&quot;&gt;Implementatiehandleiding Migratie/hybride&lt;/abbr&gt;]]<br /> :*[[mp:Implementatiehandleiding_Consolidatie/afleidingsregels|&lt;abbr title=&quot;Handleiding Consolidatie/afleidingsregels Kickstart&quot;&gt;Implementatiehandleiding Consolidatie/afleidingsregels&lt;/abbr&gt;]]<br /> :*[https://www.aorta-lsp.nl/media/downloads/implementatiehandleiding-verwijsindex-aorta-v8200pdf/download&lt;abbr title=&quot;Implementatiehandleiding verwijsindex AORTA v8.2.0.0&quot;&gt;Implementatiehandleiding VWI AORTA&lt;/abbr&gt;]<br /> :*[https://www.vzvz.nl/media/downloads/zorg-ab-implementatiehandleiding-v27pdf/download&lt;abbr title=Dit document bevat informatie, instructies en voorbeelden ten behoeve van de implementatie van<br /> (applicaties/systemen die gebruik maken van) de web API's van ZORG-AB.&gt;Implementatiehandleiding ZORG-AB&lt;/abbr&gt;]<br /> :*[https://www.aorta-lsp.nl/media/downloads/implementatiehandleiding-inschrijftoken-aorta-v8200pdf/download&lt;abbr title=&quot;Handleiding voor de implementatie van het koppelvlak tussen het goed beheerde Zorgsystemen (GBZ) en het landelijk schakelpunt (LSP).&quot;&gt;Implementatie handleiding inschrijftoken&lt;/abbr&gt;]<br /> :*[https://www.aorta-lsp.nl/media/downloads/implementatiehandleiding-mandaattoken-aorta-v8200pdf/download&lt;abbr title=&quot;Specificatie van het mandaattoken.&quot;&gt;Implementatie handleiding mandaattoken&lt;/abbr&gt;]<br /> :*[https://www.aorta-lsp.nl/media/downloads/implementatiehandleiding-berichtauthenticatie-transactietoken-aorta-v8200pdf/download&lt;abbr title=&quot;Handleiding voor het uitrusten van de berichten met het SAML transactietoken.&quot;&gt;Implementatie handleiding transactiekosten&lt;/abbr&gt;]<br /> <br /> ==Ondersteunende materialen==<br /> :*[[mp:V3.0_Voorbeelden_doseringen|&lt;abbr title=&quot;Uitgewerkte voorbeelden voor het concept 'Gebruiksinstructie' uit de dataset van de Informatiestandaard Medicatieproces 9&quot;&gt;Voorbeelden doseringen&lt;/abbr&gt;]]<br /> :*[[mp:V9_2.0.0_HL7v3CDA_FHIRTiming|&lt;abbr title=&quot;Toedieningsschema HL7v3-template. Introductie van het FHIR timing datatype in CDA substanceAdministration.effectiveTime voor toedieningsschema's. Voorheen was dit de HL7v3 GTS (General Timing Specification). Bevat ook de inhoudelijke wijziging in de XML schema's (xsd's).&quot;&gt;Dosering in FHIR&lt;/abbr&gt;]]<br /> :*[https://github.com/Nictiz/Medicatieviewer&lt;abbr title=&quot;De Medicatieviewer transformeert een MP-9 XML volgens de standaard medicatieproces 9 voor medicatiegegevens of voor medicatieoverzicht in HTML om zo een voor mensen leesbaar overzicht te geven van de inhoud van de XML.&quot;&gt;Medicatieviewer&lt;/abbr&gt;]<br /> :*[https://informatiestandaarden.nictiz.nl/images/c/c9/Medicatieoverzicht_MP90.zip&lt;abbr title=&quot;Uitklapbaar Medicatieoverzicht voorbeeld in HTML-formaat.&quot;&gt;Medicatieoverzicht HTML voorbeeld&lt;/abbr&gt;]<br /> :*[[Mappingarchitectuur#Mappings_en_transacties|&lt;abbr title=&quot;Deze sectie toont verschillende mappings voor transacties uit verschillende informatiestandaarden.&quot;&gt;Mappingarchitectuur&lt;/abbr&gt;]]<br /> :*[[mp:Vdraft_RaadplegenReconcilieren|&lt;abbr title=&quot;Deze pagina bevat nadere toelichting over hoe te reconciliëren na raadplegen. Het bespreekt de volgorde van verwerken van de verschillende soorten binnengekomen informatie.&quot;&gt;Implementatie handleiding Raadplegen Reconciliëren&lt;/abbr&gt;]]<br /> :*[[7phcy:V09_HL7v3-domeinspecificatie_Pharmacy|&lt;abbr title=&quot;Deze pagina geeft nadere toelichting bij templates in ART-DECOR.&quot;&gt;Toelichting bericht templates Medicatieproces versie 9&lt;/abbr&gt;]]<br /> :*[https://www.aorta-lsp.nl/media/downloads/best-practices-vwi-synchronisatie-aorta-v8200pdf/download/&lt;abbr title=&quot;Ter verduidelijking van de implementatiehandleiding VWI. Extra informatie wordt gegeven over de afhandeling van berichten aan de XIS leveranciers en de beheerders om duidelijkheid te geven over de verwachte acties.&quot;&gt;Best practices: VWI synchronisatie &lt;/abbr&gt;]<br /> :*[https://www.aorta-lsp.nl/media/downloads/factsheet-tkidspdf/download/&lt;abbr title=&quot;Deze factsheet beschrijft de werking van TypeKwalificatie-ID’s (TKID’s) op het LSP.&quot;&gt;Factsheet tkid&lt;/abbr&gt;]<br /> :*[https://www.vzvz.nl/diensten/gemeenschappelijke-diensten/zorg-ab&lt;abbr title=&quot;Deze pagina bevat de algemene informatie omtrent Zorg-AG.&quot;&gt;Algemene informatie Zorg-AB&lt;/abbr&gt;]<br /> :*[https://www.vzvz.nl/diensten/gemeenschappelijke-diensten/zorg-id&lt;abbr title=&quot;Deze pagina bevat de algemene informatie omtrent Zorg-ID.&quot;&gt;Algemene informatie Zorg-ID&lt;/abbr&gt;]<br /> <br /> =TEST- EN VALIDATIEMATERIAAL=<br /> ==Testinformatie Kickstart==<br /> :*[[mp:Testen_Kickstart|Testen Kickstart]]<br /> <br /> ==Testscripts==<br /> {{IssueBox|'''De aanpassingen op de testscripts door de release van versie 3.0.0-beta.3 worden op dit moment doorgevoerd'''}}<br /> :'''Medicatieproces 9'''<br /> :*[[mp:Vcurrent_Kwalificatie#Medicatieproces_9_versie_3.0.0-beta.2_testmateriaal_en_kwalificatiescripts_voor_Kickstart|Testscripts Medicatieproces 9 versie 3.0.0-beta.2]]<br /> <br /> :'''Testscript gebruikerseisen boven sectoraal'''<br /> :*[https://informatiestandaarden.nictiz.nl/wiki/Bestand:Use_case_scenario%27s_en_testscripts_GERRIT_-_Pati%C3%ABnt_1tm4_-_stap_3-4_-_beta_versie_3.0_.pdf Use case scenario's en testscripts GERRIT - Patiënt 1tm4 - stap 3-4 - beta versie 3.0&lt;/abbr&gt;]<br /> :*[https://informatiestandaarden.nictiz.nl/wiki/Bestand:Use_case_scenario%27s_en_testscripts_Rijnmond_-_pati%C3%ABnt_1-4_-_stap_3-4_-_beta_versie_3.0_(1).pdf Use case scenario's en testscripts Rijnmond - patiënt 1-4 - stap 3-4 - beta versie 3.0&lt;/abbr&gt;]<br /> <br /> :'''Lab2zorg'''<br /> :*[[Lab:Vcurrent_Kwalificatie#Lab2zorg|&lt;abbr title=&quot;Testgegevens die als voorbereiding op de kwalificatie gebruikt kunnen worden, waarbij voor de kickstart alleen de scripts Laboratoriumresultaten (Sturen/Ontvangen) relevant zijn.&quot;&gt;Testscripts Lab2zorg versie 3.0.0&lt;/abbr&gt;]]<br /> :'''Algemene eisen MP9 &amp; Generieke voorzieningen'''<br /> :*[https://informatiestandaarden.nictiz.nl/images/5/5e/Testscripts_algemene_eisen_MP9_%26_Generieke_voorzieningen.zip Testscripts algemene eisen MP9 &amp; Generieke voorzieningen (zip bestand)]<br /> <br /> ==Validatiescripts==<br /> :*Kwalificatiescripts worden definitief opgeleverd als bekend is op welke versie gevalideerd wordt in de Kickstart.<br /> :*Acceptatiescripts worden gegenereerd op het moment dat de leverancier zich meldt; dit betreft maatwerk.<br /> <br /> =TOOLING=<br /> :*[https://informatiestandaarden.nictiz.nl/images/3/30/Tooling.pdf&lt;abbr title=&quot;Overzicht van de te gebruiken tooling.&quot;&gt;Beschikbare tooling&lt;/abbr&gt;]<br /> <br /> ==ART-DECOR==<br /> :*[https://decor.nictiz.nl/art-decor/home&lt;abbr title=&quot;Inlogpagina ART-DECOR&quot;&gt;Inloggen ART-DECOR&lt;/abbr&gt;]<br /> :*[[HL7v3 kwalificatiesimulator|&lt;abbr title=&quot;Uitleg over inloggen en gebruik van de kwalificatiesimulator (ART-DECOR)&quot;&gt;Testen met ART-DECOR / Kwalificatiesimulator&lt;/abbr&gt;]]<br /> :*[https://art-decor.org/mediawiki/index.php?title=Documentation&lt;abbr title=&quot;Handleidingen en documentatie van ART-DECOR &quot;&gt;ART-DECOR documentatie&lt;/abbr&gt;]<br /> :*[[7phcy:V2.0_Toelichting_samenhang_Wiki_en_ART-DECOR|&lt;abbr title=&quot;Deze toelichting beschrijft de samenhang tussen: de HL7v3-implementatiehandleiding Medicatieproces 9 wiki en de bijbehorende html-publicatie van ART-DECOR.&quot;&gt;Wiki &amp; ART-DECOR&lt;/abbr&gt;]]<br /> <br /> ==BITS==<br /> :*[https://bits.nictiz.nl/ Link naar BITS algemeen]<br /> :*[https://bits.nictiz.nl/projects/MP/issues/ Link naar openstaande issues Medicatieproces in BITS]<br /> :*[https://informatiestandaarden.nictiz.nl/images/8/87/Handleiding_BITS_voor_leveranciers.pdf Handleiding BITS validatieloket]<br /> <br /> ==Touchstone==<br /> :*[https://touchstone.aegis.net/touchstone/login&lt;abbr title=&quot;Inlogpagina Touchstone&quot;&gt;Inloggen Touchstone&lt;/abbr&gt;]<br /> :*[[mp:Vcurrent_Kwalificatie#Touchstone|Testen met Touchstone]]<br /> <br /> ==ZORG-AB==<br /> :*[https://zorg-ab-oas.vzvz.nl/&lt;abbr title=&quot;Testapplicatie Zorg-AB&quot;&gt;ZORG-AB testapplicatie&lt;/abbr&gt;]<br /> :*[https://www.vzvz.nl/diensten/gemeenschappelijke-diensten/zorg-ab&lt;abbr title=&quot;Deze pagina bevat informatie, instructies en voorbeelden ten behoeve van de implementatie van<br /> (applicaties/systemen die gebruik maken van) de web API's van ZORG-AB.&quot;&gt;Implementatie handleiding ZORG-AB&lt;/abbr&gt;]<br /> <br /> =INFORMATIEVOORZIENING=<br /> <br /> ==Vragen en antwoorden==<br /> :*[[mp:Medicatieoverdracht_Kickstart_Vragen|Vragen en antwoorden uit vragenuur op vrijdagen]]<br /> <br /> ==Kennissessie==<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/luistersessie-introductiesessie-medicatieproces/ &lt;abbr title=&quot;In deze kennissessie wordt een introductie gegeven van het programma Medicatieoverdracht, de richtlijn Overdracht van medicatiegegevens in de keten, de informatiestandaard Medicatieproces 9&quot;&gt;Kennissessie: Introductie Medicatieoverdracht&lt;/abbr&gt;]<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/kennissessie-wat-kan-ik-verwachten-van-medicatieoverdracht/ &lt;abbr title=&quot;In deze kennissessie wordt inzicht gegeven in de meerwaarde van het programma Medicatieoverdracht voor de zorgverlener en patiënt en de te nemen acties op procesniveau. Per rol (voorschrijver, apotheker, toediener en patiënt) worden de stappen die worden beproefd in de Kickstart toegelicht.&quot;&gt;Kennissessie: Wat kan ik verwachten van Medicatieoverdracht&lt;/abbr&gt;]<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/kennissessie-verdieping-medicatieoverdracht/ &lt;abbr title=&quot;Deze kennissessie is voor iedereen die meer wil weten over het medicatieproces: welke gegevensuitwisselingsmomenten zijn er (transacties), welke rollen horen daarbij, hoe werken de bouwsteen relaties precies etc.&quot;&gt;Kennissessie: Verdieping Medicatieoverdracht&lt;/abbr&gt;]<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/luistersessie-voorgenomen-besluiten-kernteam-medicatie// &lt;abbr title=&quot;Deze kennissessie geeft een beeld van hoe samen met zorgverleners uit de 10 betrokken sectoren afspraken tot stand zijn gekomen t.a.v. beleid, verantwoordelijkheden, zorgprocessen, eenheid van taal in terminologie en codestelsels om de implementatie van de richtlijn en informatiestandaard te ondersteunen. &quot;&gt;Kennissessie: (Voorgenomen) besluiten kernteam Medicatie&lt;/abbr&gt;]<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/luistersessies/&lt;abbr title=&quot;In deze kennissessie wordt de route van de bèta publicatie van de informatiestandaard Medicatieproces 9 naar de definitieve versie toegelicht. &quot;&gt;Kennissessie: Route Medicatieproces 9 v2.0.0 bèta naar definitief&lt;/abbr&gt;]<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/luistersessie-testmaterialen-medicatieproces-9-2-0-0-beta/ &lt;abbr title=&quot;In deze kennissessie worden de testmaterialen voor Medicatieproces 9 toegelicht. Wat kan er getest worden, wat is de samenhang tussen de materialen, inhoud van het materiaal, hoe te gebruiken en waar te vinden. &quot;&gt;Kennissessie: Testmaterialen Medicatieproces 9 v2.0.0 bèta&lt;/abbr&gt;]<br /> :*[https://informatiestandaarden.nictiz.nl/images/d/d2/202202_Introductie_AORTA_-_nieuwe_style.pdf &lt;abbr title=&quot;Introductiepresentatie AORTA. Een introductie van infrastructurele AORTA architectuur​, verschillende architectuurlagen​, verschillende componenten​.<br /> Relaties met andere stelsels en producten​.&quot;&gt;Presentatie: Introductie AORTA&lt;/abbr&gt;]<br /> <br /> ==PGO==<br /> :*[https://informatiestandaarden.nictiz.nl/images/6/61/PGOsessiesMedicatieproces_BijlageBijOnlineSessie.pdf &lt;abbr title=&quot;Deze kennissessie geeft een introductie van MedMij in relatie tot Medicatieproces 9.&quot;&gt;Presentatie: Medicatieoverdracht uitleg MedMij&lt;/abbr&gt;]<br /> :*[https://informatiestandaarden.nictiz.nl/images/2/29/PGOsessie_OpnameOnline.mp4 &lt;abbr title=&quot;Opname van de kennissessie: Een introductie van MedMij in relatie tot het Medicatieproces 9.&quot;&gt;Opname: Medicatieoverdracht uitleg presentatie MedMij&lt;/abbr&gt;]<br /> <br /> =MEMO'S=<br /> <br /> ==Informatieve memo's==<br /> :*[https://informatiestandaarden.nictiz.nl/images/7/79/MO_memo_MBH-ID_Transformatiedienst_20230315.pdf&lt;abbr title=&quot;Memo MBH-ID Transformatiedienst_20230315&quot;&gt;Memo MBH-ID Transformatiedienst 15-03-2023&lt;/abbr&gt;]<br /> :*[https://informatiestandaarden.nictiz.nl/images/4/48/MO_memo_vooraankondiging_20230307.pdf&lt;abbr title=&quot;Memo vooraankondiging_20230307&quot;&gt;Memo vooraankondiging 07-03-2023&lt;/abbr&gt;]<br /> <br /> =IN ONTWIKKELING=<br /> :'''Transitie naar Medicatieproces 9 (migratie en hybride situatie)'''<br /> :*[[Vdraft_Mappingarchitectuur#Medicatieproces_.28MP.29_Versie_MP9_2.0_en_versie_9.0.7|&lt;font color=&quot;BBB7B6&quot;&gt;Mappingarchitectuur met mappings MP 9.0.7 &lt;-&gt; MP9 2.0.0&lt;/font&gt;]]<br /> <br /> :'''Kickstart testen'''<br /> :*[[mp:Draft_Testtooling#BITS|&lt;font color=&quot;BBB7B6&quot;&gt;Tooling &amp; omgevingen Kickstart Medicatieoverdracht&lt;/font&gt;]]<br /> <br /> =ARCHIEF=<br /> :*[https://informatiestandaarden.nictiz.nl/images/4/42/Nulpunt_documentatie_Kickstart_contract_leveranciers_versie11_20220907.pdf&lt;abbr title=&quot;Document dat nulpunt beschrijft voor specificaties Kickstart ten behoeve van contract.&quot;&gt;Nulpunt documentatie Kickstart leveranciers versie 1.1 van 7 september 2022&lt;/abbr&gt;]<br /> :* Verzamelbestand in Excel met functionele, technische en infrastructurele documentatie Medicatieproces 9 t.b.v. Kickstart (niet meer te downloaden om verwarring te voorkomen)<br /> :*[https://www.aorta-lsp.nl/voor-wie/ict-leveranciers/aorta-documentatie/infrastructuur-aorta-v8200&lt;abbr title=&quot;Deze pagina bevat de algemene specificaties van de zorginfrastructuur AORTA v8.2.0.0&quot;&gt;Documentatie AORTA 8.2.0.0&lt;/abbr&gt;]<br /> <br /> :'''Informatiestandaard Medicatieproces 9.3.0.0-beta.2'''<br /> :*[[mp:V3.0.0-beta.2_Ontwerp_medicatieproces_9|&lt;abbr title=&quot;Het functioneel ontwerp van de informatiestandaard Medicatieproces 9 Het beschrijft de algemene werking en specifieke praktijksituaties.&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 3.0.0-beta.2 (NL)&lt;/abbr&gt;]] / [[mp:V3.0.0-beta.2_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 3.0.0-beta.2 (ENG)]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/index.html&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.&quot;&gt;Medicatieproces 9 versie 3.0.0-beta.2 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> :*[[mp:V3.0.0-beta.2_MedicationProcess9_FHIR|&lt;abbr title=&quot;FHIR Implementation guide for Medicatieproces 9 versie 3.0.0-beta.2 FHIR in English&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 (ENG) &lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|&lt;abbr title=&quot;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.2 voor patiënt usecases&quot;&gt;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.2 voor patiënt usecases&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.2_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases (ENG)&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.2_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 3.0.0-beta.2&lt;/abbr&gt;]]<br /> <br /> :'''Informatiestandaard Medicatieproces 9.3.0.0-beta.1'''<br /> :*[[mp:V3.0.0-beta.1_Ontwerp_medicatieproces_9|Functioneel ontwerp Medicatieproces 9 versie 3.0.0-beta.1 (NL)]] / [[mp:V3.0.0-beta.1_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 3.0.0-beta.1 (ENG)]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20230217T123829/index.html&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.&quot;&gt;Medicatieproces 9 versie 3.0.0-beta.1 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> :*[[mp:V3.0.0-beta.1_MedicationProcess9_FHIR|&lt;abbr title=&quot;FHIR Implementation guide for Medicatieproces 9 versie 3.0.0-beta.1 FHIR in English&quot;&gt;Implementation guide FHIR Medication Process 9 version 3.0.0-beta.1 (ENG)&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.1_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.1 for patient use cases (ENG)&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.1_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 3.0.0-beta.1&lt;/abbr&gt;]]<br /> <br /> :'''Informatiestandaard Medicatieproces 9.2.0.0'''<br /> :*[[mp:V2.0.0_Ontwerp_medicatieproces_9|&lt;abbr title=&quot;Het functioneel ontwerp van de informatiestandaard Medicatieproces 9. Het beschrijft de algemene werking en specifieke praktijksituaties.&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 2.0.0 (NL)&lt;/abbr&gt;]] / [[mp:V2.0.0_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 2.0.0 (ENG)]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20220402T205710/index.html&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.<br /> &quot;&gt;Medicatieproces 9 versie 2.0.0 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> :*[[mp:V2.0.0_MedicationProcess9_FHIR|&lt;abbr title=&quot;FHIR Implementation guide for Medicatieproces 9 versie 2.0.0 FHIR in English&quot;&gt;Implementation guide FHIR Medication Process 9 version 2.0.0 (ENG)&lt;/abbr&gt;]]<br /> :*[[mp:V2.0.0_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 2.0.0&lt;/abbr&gt;]]<br /> :*[[mp:V9_2.0.0_HL7v3CDA_FHIRTiming|HL7v3 CDA substanceAdministration.effectiveTime en FHIR timing]]<br /> :*[[7phcy:V09_HL7v3-domeinspecificatie_Pharmacy|HL7v3-domeinspecificatie Pharmacy Medicatieproces 9]]<br /> :*PGO/MedMij: [[MedMij:Vkickstart/OntwerpMedicatie|&lt;abbr title=&quot;Dit is de link naar het Functioneel Ontwerp Medicatieproces 9 patient use cases nodig voor uitwisseling van PGO binnen oa MedMij&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 2.0.0 voor patient use cases&lt;/abbr&gt;]]<br /> <br /> =PAGINAHISTORIE=<br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> !style=&quot;text-align:left;&quot;&quot; width=&quot;130&quot;|Datum<br /> !style=&quot;text-align:left;&quot;|Omschrijving<br /> |-<br /> | style=&quot;background-color: white;&quot;| 1 maart 2024<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; :'''Informatiestandaard Medicatieproces 9.3.0.0-beta.3''' gepubliceerd<br /> :*[[mp:V3.0.0-beta_Ontwerp_medicatieproces_9|&lt;abbr title=&quot;Het functioneel ontwerp van de informatiestandaard Medicatieproces 9 Het beschrijft de algemene werking en specifieke praktijksituaties.&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 3.0.0-beta.3 (NL)&lt;/abbr&gt;]] / [[mp:V3.0.0-beta_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 3.0.0-beta.3 (ENG)]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.<br /> &quot;&gt;Medicatieproces 9 versie 3.0.0-beta.3 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> :*[[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|&lt;abbr title=&quot;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.3 voor patiënt usecases&quot;&gt;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.3 voor patiënt usecases&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.3_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 3.0.0-beta.3&lt;/abbr&gt;]]<br /> :*Gebruikerseisen: [[mp:Besluiten_kernteams|&lt;abbr title=&quot;Deze pagina bevat de besluiten van de kernteams, met (indien van toepassing) de bijbehorende werkproceseisen, gebruikerseisen en -wensen.&quot;&gt;Besluiten kernteams Medicatieproces 9, inclusief gebruikerseisen en -wensen&lt;/abbr&gt;]]<br /> &lt;li&gt; '''Informatiestandaard Medicatieproces 9.3.0.0-beta.2''' naar archief<br /> :*[[mp:V3.0.0-beta.2_Ontwerp_medicatieproces_9|&lt;abbr title=&quot;Het functioneel ontwerp van de informatiestandaard Medicatieproces 9 Het beschrijft de algemene werking en specifieke praktijksituaties.&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 3.0.0-beta.2 (NL)&lt;/abbr&gt;]] / [[mp:V3.0.0-beta.2_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 3.0.0-beta.2 (ENG)]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/index.html&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.<br /> &quot;&gt;Medicatieproces 9 versie 3.0.0-beta.2 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> :*[[mp:V3.0.0_MedicationProcess9_FHIR|&lt;abbr title=&quot;FHIR Implementation guide for Medicatieproces 9 versie 3.0.0-beta.1 FHIR in English&quot;&gt;Implementation guide FHIR Medication Process 9 version 3.0.0-beta.2 (ENG) &lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|&lt;abbr title=&quot;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.2 voor patiënt usecases&quot;&gt;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.2 voor patiënt usecases&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.2_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 3.0.0-beta.2&lt;/abbr&gt;]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/index.html&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.<br /> &quot;&gt;Medicatieproces 9 versie 3.0.0-beta.2 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;] <br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 6 november 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; [[mp:V3.0.0-beta.1_MedicationProcess9_FHIR|&lt;abbr title=&quot;FHIR Implementation guide for Medicatieproces 9 versie 3.0.0-beta.1 FHIR in English&quot;&gt;Implementation guide FHIR Medication Process 9 version 3.0.0-beta.1 (ENG)&lt;/abbr&gt;]] naar archief<br /> &lt;li&gt; [https://simplifier.net/packages/nictiz.fhir.nl.r4.medicationprocess9/2.0.0-beta.1/ FHIR R4 conformance resources for Medication Process 9 (MP9)] naar archief<br /> &lt;li&gt; [[mp:V3.0.0-beta.1_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.1 for patient use cases&lt;/abbr&gt;]] naar archief<br /> &lt;li&gt; [https://simplifier.net/packages/nictiz.fhir.nl.r4.medicationprocess9/2.0.0-beta.2/ FHIR R4 conformance resources for Medication Process 9 (MP9)] geüpdatet naar beta.2 versie<br /> &lt;li&gt; [[mp:V3.0.0_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&lt;/abbr&gt;]] toegevoegd<br /> &lt;li&gt; [https://decor.nictiz.nl/pub/vzvz/index.php?prefix=mp-vzvz-&lt;abbr title=&quot;&quot;&gt;ART-DECOR Publicatiepagina VZVZ: Medicatieproces op het LSP&lt;/abbr&gt;] geüpdatet n.a.v. beta.2 versie<br /> &lt;li&gt; [https://zt-medicatieoverdracht.scrollhelp.site/Medicatieoverdracht/Working-version/programma-van-eisen-medicatieoverdracht&lt;abbr title=&quot;De beschikbare Programma van Eisen waaraan de Kickstart deelnemers moeten voldoen. Deze documenten beschrijven de eisen om aan te sluiten op de AORTA-infrastructuur.&quot;&gt;Programma van eisen LSP (bèta)&lt;/abbr&gt;] geüpdatet n.a.v. beta.2 versie<br /> &lt;li&gt; [https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpublicvzvz.refined.site%2Fspace%2FA8%2F85000200%2FAORTA%2B8.3.0&amp;data=05%7C01%7Ctheunissen%40nictiz.nl%7C52a3bf5378624ff2978e08db8f44c3a3%7C3d542e8da3eb448f998ddd6880dc119c%7C0%7C0%7C638261297740578594%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=6%2FH9yQ0EAHEmGYHgbVoQo995poc34CXlV6UcBP4MSD8%3D&amp;reserved=0&lt;abbr title=&quot;Deze pagina bevat de algemene specificaties van de zorginfrastructuur AORTA v8.3.0.0&quot;&gt;Documentatie AORTA versie 8.3.0.0&lt;/abbr&gt;] geüpdatet n.a.v. beta.2 versie<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 20 oktober 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; [[mp:V3.0.0-beta.2_releasenotes|Release notes Medicatieproces 9 versie 3.0.0-beta.2]] toegevoegd<br /> &lt;li&gt; 2.2 Specificaties: update n.a.v. beta.2 release<br /> *[[mp:V3.0.0-beta_Ontwerp_medicatieproces_9|&lt;abbr title=&quot;Het functioneel ontwerp van de informatiestandaard Medicatieproces 9 Het beschrijft de algemene werking en specifieke praktijksituaties.&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 3.0.0-beta.2 (NL)&lt;/abbr&gt;]] / [[mp:V3.0.0-beta_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 3.0.0-beta.2 (ENG)]]<br /> *[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20230217T123829/index.html&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.<br /> &quot;&gt;Medicatieproces 9 versie 3.0.0-beta.2 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> *[[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|&lt;abbr title=&quot;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.2 voor patiënt usecases&quot;&gt;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.2 voor patiënt usecases&lt;/abbr&gt;]]<br /> *[[mp:V3.0.0_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&lt;/abbr&gt;]]<br /> &lt;li&gt; 3.2 Testscript: update n.a.v. beta.2 release<br /> *[[mp:Vcurrent_Kwalificatie#Medicatieproces_9_versie_3.0.0-beta.1_testmateriaal_en_kwalificatiescripts_voor_Kickstart|Testscripts Medicatieproces 9 versie 3.0.0-beta.2]]<br /> &lt;li&gt; [[mp:V3.0.0-beta.1_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 3.0.0-beta.1&lt;/abbr&gt;]] naar archief<br /> &lt;li&gt; [[mp:V3.0.0-beta.1_Ontwerp_medicatieproces_9|Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.1]] &amp; [[mp:V3.0.0-beta.1_Ontwerp_medicatieproces_9_ENG|Functional Design Medication Process 9 version 3.0.0-beta.1 English version]] naar archief<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 11 oktober 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 3.2 Testscripts: Nieuwe versie Testscript gebruikerseisen boven sectoraal: [https://informatiestandaarden.nictiz.nl/wiki/Bestand:Use_case_scenario%27s_en_testscripts_GERRIT_-_Pati%C3%ABnt_1tm4_-_stap_3-4_-_beta_versie_3.0_.pdf Use case scenario's en testscripts GERRIT - Patiënt 1tm4 - stap 3-4 - beta versie 3.0&lt;/abbr&gt;] toegevoegd.<br /> &lt;li&gt; 3.2 Testscripts: Nieuwe versie Testscript gebruikerseisen boven sectoraal: [https://informatiestandaarden.nictiz.nl/wiki/Bestand:Use_case_scenario%27s_en_testscripts_Rijnmond_-_pati%C3%ABnt_1-4_-_stap_3-4_-_beta_versie_3.0_(1).pdf Use case scenario's en testscripts Rijnmond - patiënt 1-4 - stap 3-4 - beta versie 3.0&lt;/abbr&gt;] toegevoegd.<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 6 september 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 2.5 [[mp:V3.0_Voorbeelden_doseringen|&lt;abbr title=&quot;Uitgewerkte voorbeelden voor het concept 'Gebruiksinstructie' uit de dataset van de Informatiestandaard Medicatieproces 9&quot;&gt;Voorbeelden doseringen&lt;/abbr&gt;]] aangepast naar 9.3 versie.<br /> |-<br /> | style=&quot;background-color: white;&quot;| 4 september 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 3.2 Testscripts: Testscript gebruikerseisen boven sectoraal: [https://informatiestandaarden.nictiz.nl/wiki/Bestand:Use_case_scenario%27s_en_testscripts_GERRIT_-_Pati%C3%ABnt_1tm4_-_stap_3-4_-_beta_versie_3.0_.pdf Use case scenario's en testscripts GERRIT - Patiënt 1tm4 - stap 3-4 - beta versie 3.0&lt;/abbr&gt;] toegevoegd.<br /> &lt;li&gt; 3.2 Testscripts: Testscript gebruikerseisen boven sectoraal: [https://informatiestandaarden.nictiz.nl/wiki/Bestand:Use_case_scenario%27s_en_testscripts_Rijnmond_-_pati%C3%ABnt_1-4_-_stap_3-4_-_beta_versie_3.0_(1).pdf Use case scenario's en testscripts Rijnmond - patiënt 1-4 - stap 3-4 - beta versie 3.0&lt;/abbr&gt;] toegevoegd.<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 28 juli 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 2.2 Specificaties: Infrastructuur: [https://publicvzvz.refined.site/space/MED/86179842/Kickstart+van+Medicatieoverdracht Programma van eisen LSP (bèta)] link aangepast naar pagina met meest recente informatie<br /> &lt;li&gt; 2.2 Specificaties: Infrastructuur: [https://publicvzvz.refined.site/space/A8/85000200/AORTA+8.3.0 Documentatie AORTA versie 8.3.0.0] link aangepast naar pagina met meest recente informatie<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 2 juni 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 3.2 Testscripts: Algemene eisen MP9 &amp; Generieke voorzieningen toegevoegd<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 30 mei 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 2.1 Voorbereiding: Plan van aanpak versie 3.1. Addendum plan van aanpak Kickstart v3.1 - Aanpassing Kickstartplanning Mei 2023 toegevoegd aan onderliggende pagina<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 4 mei 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 2.2 Specificaties: [[mp:V2.0.0_Verwijzing_naar_documentatie_Medicatieproces9_tbv_Kickstart|Verzamelbestand met functionele, technische en infrastructurele documentatie Medicatieproces 9 t.b.v. Kickstart]] ge-update met linkjes naar 9.3 versie<br /> &lt;li&gt; 3.1 Testinformatie Kickstart: [[mp:Testen_Kickstart|Testen Kickstart]] toegevoegd.<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 25 april 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 2.2 Specificaties: [[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.1 voor patiënt usecases]] toegevoegd .&lt;br&gt;<br /> &lt;li&gt; 2.2 Specificaties: [[mp:V3.0.0_MedicationProcess9_FHIR_for_patient_use_cases|FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.1 for patient use cases]] toegevoegd.&lt;br&gt;<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 20 april 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 4.1 Testen met ART-DECOR: onderliggende pagina vervangen naar [[HL7v3 kwalificatiesimulator]] .&lt;br&gt;<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 11 april 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; Hoofdstuk 3.1 nieuwe versie testscripts toegevoegd: [[mp:Vcurrent_Kwalificatie#Medicatieproces_9_versie_3.0.0-beta.1_testmateriaal_en_kwalificatiescripts_voor_Kickstart|Medicatieproces 9 versie 3.0.0-beta.1]]&lt;br&gt;<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 21 maart 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; Hoofdstuk 6 MEMO'S toegevoegd&lt;br&gt;<br /> &lt;li&gt; Memo MBH-ID Transformatiedienst 15-03-2023 toegevoegd&lt;br&gt;<br /> &lt;li&gt; Memo vooraankondiging 07-03-2023 toegevoegd<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 6 maart 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; Implementatiehandleiding Consolidatie en afleidingsregels toegevoegd&lt;br&gt;<br /> &lt;li&gt; Specificaties Informatiestandaard Medicatieproces 9 versie 3.0.0-beta.1 toegevoegd<br /> * Functioneel ontwerp<br /> * Technisch ontwerp CDA<br /> * Technisch ontwerp FHIR<br /> * Release notes <br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 18 januari 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt;[https://decor.nictiz.nl/pub/vzvz/aorta-vzvz-html-20221128T172039/sc-2.16.840.1.113883.2.4.3.111.3.2.3.3-2016-09-20T163842.html Implementatie van de ping-pong toets]: link aangepast naar AORTA 8.3 versie<br /> &lt;li&gt;[https://decor.nictiz.nl/pub/vzvz/aorta-vzvz-html-20221128T172039/sc-2.16.840.1.113883.2.4.3.111.3.2.3.1-2016-09-20T091642.html Beheren TKID applicatie]: link aangepast naar AORTA 8.3 versie<br /> &lt;li&gt;[https://public.vzvz.nl/download/attachments/41779447/AORTA_Proces_VWI_Synchronisatie.pdf?api=v2 Proces VWI synchronisatie]: link aangepast naar AORTA 8.3 documentatie<br /> &lt;li&gt;[https://public.vzvz.nl/download/attachments/41779447/AORTA_Sgl_Ontw_Gebeurtenisverwerking.pdf?api=v2 Ontwerp gebeurtenisverwerking]: link aangepast naar AORTA 8.3 documentatie<br /> &lt;li&gt;[https://public.vzvz.nl/download/attachments/41779447/AORTA_Sgl_Ontw_Abonnementenregister.pdf?api=v2 Ontwerp abonnementenregister]: link aangepast naar AORTA 8.3 documentatie<br /> &lt;li&gt;[https://www.vzvz.nl/diensten/gemeenschappelijke-diensten/zorg-ab Implementatie handleiding ZORG-AB]: link aangepast naar Zorg-AB pagina met meest recente documentatie<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 29 september 2022<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt;Specificaties Lab2zorg: link toegevoegd naar de [[mp:LeeswijzerVoorschriftmetnierfunctiewaarde|leeswijzer ten behoeve van het meesturen van de nierfunctiewaarde met het voorschrift]]&lt;br&gt;<br /> De leeswijzer legt uit welk onderdeel van Lab2zorg binnen de scope van de Kickstart valt en welke documentatie daarop van toepassing is. De leeswijzer vervangt het aanvullingendocument.<br /> &lt;li&gt;Specificaties Lab2zorg: link verwijderd naar het [[Lab:V3.0.0_Ontwerp_Laboverdacht|functioneel ontwerp informatiestandaard uitwisseling Laboratoriumgegevens versie 3.0.0]]&lt;br&gt;<br /> De informatiestandaard beschrijft de algemene werking voor alle uitwisselingen van Laboratoriumgegevens. Het onderdeel lab2zorg hieruit wordt gebruikt in de kickstart.<br /> &lt;li&gt;Specificaties Lab2zorg: link verwijderd naar aanvullingendocument<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 12 september 2022<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt;Specificaties: link toegevoegd naar [[mp:Stap_0_Voorbereiding|Werkzaamheden in stap 0 Voorbereiding]]<br /> &lt;li&gt;Informatievoorziening: link toegevoegd naar [[mp:Medicatieoverdracht_Kickstart_Vragen|Vragen en antwoorden uit vragenuur op vrijdagen]]&lt;br&gt;<br /> Na elk vragenuur worden de vragen en antwoorden aan deze pagina toegevoegd<br /> &lt;li&gt;Archief: link naar oude versie nulpunt document verwijderd en link naar nieuwe toegevoegd [https://informatiestandaarden.nictiz.nl/images/4/42/Nulpunt_documentatie_Kickstart_contract_leveranciers_versie11_20220907.pdf Nulpunt documentatie leveranciers versie 1.1 van 7 september 2022] &lt;br&gt;<br /> Inhoudelijke wijziging versie 1.1: link naar document Werkzaamheden in stap 0 Voorbereiding toegevoegd<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 1 september 2022<br /> | style=&quot;background-color: white;&quot;| Formele publicatie van de pagina + update: <br /> &lt;ul&gt;<br /> &lt;li&gt;Titel aangepast<br /> &lt;li&gt;Algemeen referentie: onderdeel toegevoegd en kwaliteitsstandaard toegevoegd<br /> &lt;li&gt;Voorbereiding: checklists verwijderd<br /> &lt;li&gt;Specificaties: verzamelbestand omgezet van Excel naar wiki<br /> &lt;li&gt;Specificaties MP9: gebruikerseisen toegevoegd<br /> &lt;li&gt;Specificaties Lab2zorg: labdocumentatie toegevoegd<br /> &lt;li&gt;Specificaties Infrastructuur: aorta 8.2 vervangen door aorta 8.3 (8.2 naar archief)<br /> &lt;li&gt;Test- en validatiemateriaal: testscripts en kwalificatiescripts gesplitst, alleen testscripts MP9 gelinkt en labtestmateriaal toegevoegd<br /> &lt;li&gt;Tooling BITS: handleiding BITS toegevoegd<br /> &lt;li&gt;Archief: nulpunt 1 september 2022 toegevoegd<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 1 augustus 2022<br /> | style=&quot;background-color: white;&quot;| Correctie in ''Verzamelbestand met functionele, technische en infrastructurele documentatie Medicatieproces 9 t.b.v. Kickstart''<br /> |-<br /> | style=&quot;background-color: white;&quot;| juli 2022<br /> | style=&quot;background-color: white;&quot;| Pagina gepubliceerd<br /> |}</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=mp:V3.0.0-rc.2_MedicationProcess9_FHIR&diff=206664 2024-03-06T20:22:53Z

<p>Luud Slagter: /* Retrieve all medication data */ MP-1443: Finetuned search requests w.r.t. patient identification mechanism</p> <hr /> <div>__NOINDEX__<br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide Medication Process 9 version {{VersieInfo|mp9|release=V3.0.0}} }}<br /> <br /> __TOC__<br /> <br /> = Introduction =<br /> 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.<br /> <br /> 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.<br /> <br /> This IG first describes the boundaries and relationships in place, after which the implementation is described per transaction.<br /> <br /> = Boundaries and relationships =<br /> == Building blocks and profiles ==<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> Because the way 90 million numbers are exchanged is not compatible with the 2020 publication of zib PharmaceuticalProduct, a fork of the corresponding nl-core profile called 'mp-PharmaceuticalProduct' has been introduced.<br /> <br /> {{NoteBoxNictizR4Package|p1=nictiz.fhir.nl.r4.medicationprocess9|v1={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|p2=nictiz.fhir.nl.r4.nl-core|v2={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> <br /> 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:<br /> * MP9 version 2.0.0 makes use of version 1.0.0 of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package;<br /> * MP9 version 3.0.0-beta.x makes use of version 2.0.0-beta.x of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package.<br /> <br /> === Medication building blocks ===<br /> <br /> As described above, the main medication building blocks have no dependency on any zib2020 counterparts, resulting in so-called ‘mp’ profiles. Moreover, note that the building block VariableDosingRegimen does not have a zib counterpart, hence it makes sense to include it as an mp profile as well.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |}<br /> <br /> === Supporting building blocks ===<br /> <br /> Additionally, the standard uses several supporting building blocks referenced from the main medication building blocks. All supporting building blocks are part of the [[FHIR:V1.0_FHIR_IG_R4#Functional_definitions|‘nl-core’ package]]&lt;ref&gt;Although the nl-core package is still in beta-status, HL7 Netherlands has validated the profiles mentioned and assigned the status 'STU-NL' for use in the MP9 Kickstart, see [[Media:HL7_Nederland_disclaimer_STU-NL.pdf]]&lt;/ref&gt;.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> Note the following:<br /> * Each occurrence of the zib HealthProfessional is normally represented by '''two''' FHIR resources: an instance of nl-core-HealthProfessional-PractitionerRole and an instance of nl-core-HealthProfessional-Practitioner. Sending systems should only fill the reference to the PractitionerRole instance where relevant. Receiving systems can resolve the reference to the Practitioner resource from that PractitionerRole instance.<br /> * The zib HealthcareProvider is mapped to both a Location and Organization profile. Most often, the Location profile acts as the focal resource, because most references to this zib are concerned about the recording of the physical location where the care to patient/client takes place rather than the organizational information. For the latter, the profile on Organization is used which is referenced using the {{fhir|Location.managingOrganization}} element. Sending systems should only fill the reference to the Location instance where relevant. Incidentally, concepts that are only concerned with organizational information can refer to the Organization instance.<br /> <br /> === Transaction specific profiles ===<br /> <br /> For several transactions, additional profiles are provided. For each transaction the profile relevant is explicitly mentioned in the corresponding subsection.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |}<br /> <br /> ====Bundle profiles====<br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == Mappings between profiles and data set ==<br /> 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.<br /> <br /> 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:<br /> * 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)<br /> ** 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.<br /> ** 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.<br /> * If an element in the functional definition is removed<br /> ** and the element had a zib mapping applied (not on an extension), the zib mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> ** and the element had a mapping applied to the previous version of MP9 (not on an extension), that mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> * If an element in the functional definition is removed and the element had a mapping applied on an extension, that extension is removed entirely. In particular no {{term|[DEPRECATED]}} mapping will be visible in the FHIR profile. This is done to ensure no redundant extensions remain in the FHIR profiles.<br /> <br /> Moreover, all mappings to earlier versions of MP9 (i.e. versions before the previous version) are entirely removed.<br /> <br /> Following the procedure outlined above thus results in the following:<br /> * 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.<br /> * All incompatible changes made in the latest version with respect to the previous version are marked.<br /> * Exceptions are extensions that would otherwise only contain deprecated mappings; these are removed fully.<br /> <br /> 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’]].<br /> <br /> 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.<br /> <br /> 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]].<br /> <br /> == Pharmaceutical treatment ==<br /> 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.<br /> <br /> == Patient identification ==<br /> This implementation guide assumes that the client system is able to make a connection to the right server that contains the patient's information. It does not provide information on finding the right server nor does it provide information about security. Moreover, each transaction is performed in the context of a specific patient, whose context might have been established using the authentication mechanisms described in external specifications such as the MedMij ‘Afsprakenstelsel’ or through the usage of search parameters for patient identification. <br /> <br /> Each server is required to perform filtering based on the patient associated with the context for the request or based on the patient identification search parameters, which is a [https://www.hl7.org/fhir/r4/search.html#chaining chained search parameter] for all resource types except Patient, so only the records associated with the authenticated patient are returned.<br /> <br /> When patient identification requires the use of search parameters, the following search parameters SHALL be supported:<br /> * Patient: {{fhir|identifier}}<br /> * MedicationRequest: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationDispense: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationStatement: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationAdministration: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> <br /> An example of a request that retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233:<br /> <br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> <br /> Note: All request examples in this document do not include patient identification mechanisms, partly because we want to generalize this technical design as much as possible (it being applicable to both MedMij and other use cases), and partly because this would convolute all search request examples. Requesters are assumed to include these if necessary. Since there currently are only use cases in the context of a single patient, the patient identification mechanism is actually implicitly assumed to be present in all search requests.<br /> <br /> == Resource identification ==<br /> 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}}.<br /> <br /> 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 &lt;code&gt;@root&lt;/code&gt; and &lt;code&gt;@extension&lt;/code&gt; (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.<br /> <br /> 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|release=V3.0.0}}}} 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]].<br /> <br /> == Differentiating between transactions ==<br /> All transactions described in this IG use the same medication building blocks in different combinations and settings, making it necessary to differentiate between them. Several mechanisms are used to achieve this. Aside from PUSH/PULL, the type of medication building blocks, supporting resources like List and Communication for specific transactions and fixing the value of specific FHIR elements in applicable profiles, the {{term|actionable}} tag is used. The latter is described more in depth in the following section. Next to that, a summarizing table is provided.<br /> <br /> Note that {{fhir|Resource.meta.profile}}, although present in each building block (see [[FHIR:V1.0_FHIR_IG_R4#Profile_use_and_declaration|the general FHIR IG on ‘Profile use and declaration’]]), SHOULD [https://hl7.org/fhir/r4/resource.html#profile-tags not be used for identification of the building block type] and therefore for differentiating between transactions.<br /> <br /> === Actionable tag ===<br /> To differentiate between sending or serving building blocks that are either of informative nature or of actionable nature, the {{term|actionable}} tag is used. [https://hl7.org/fhir/r4/resource.html#tag Tags] are {{datatype|Coding}} elements present in {{fhir|Resource.meta.tag}} used for workflow management.<br /> <br /> If applicable, the profiles used by a transaction require the use of {{fhir|.meta.tag}} with {{fhir|.system}} = {{term|&lt;nowiki&gt;http://terminology.hl7.org/CodeSystem/common-tags&lt;/nowiki&gt;}} and {{fhir|.code}} = {{term|actionable}} to indicate that the resource is part of a request intended to be acted upon. The absence of this tag indicates that the resource is merely of informative nature.<br /> <br /> It is up to systems to determine how and when the transactions using the {{term|actionable}} tag are handled from a functional perspective. Systems may store the resource including the {{term|actionable}} tag or remove it either upon storing or when the request is acted upon. However, systems SHALL make sure the tag is removed when serving or sending the resource as part of an informative transaction.<br /> <br /> === Summarizing table ===<br /> {| class=&quot;wikitable&quot; <br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | PUSH/PULL<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building blocks<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | {{term|actionable}} tag<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR element value<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Other<br /> |-<br /> | Medication data (Retrieve/Serve)<br /> | PULL<br /> | One or more of all building blocks<br /> | No<br /> |<br /> | <br /> |-<br /> | Medication data (Send/Receive)<br /> | PUSH<br /> | One or more of all building blocks<br /> | No<br /> |<br /> |<br /> |-<br /> | Medication overview (Retrieve/Serve)<br /> | PULL<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication overview (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication prescription (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, DispenseRequest (optional)<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|order}} (for both MedicationAgreement and DispenseRequest building blocks)<br /> | <br /> |-<br /> | Medication prescription processing (Send/Receive)<br /> | PUSH<br /> | AdministrationAgreement, MedicationDispense (optional)<br /> | Yes<br /> | <br /> | <br /> |-<br /> | Proposal dispense request (Send/Receive)<br /> | PUSH<br /> | DispenseRequest<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal dispense request (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to DispenseRequest<br /> |-<br /> | Proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to MedicationAgreement<br /> |}<br /> <br /> = Transactions =<br /> 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’.<br /> &lt;section begin=medmij1 /&gt;<br /> == Medication data (Retrieve/Serve) ==<br /> The retrieve medication data transaction is used by the client to retrieve medication data from a server. The client can retrieve its desired information by searching for specific medication building blocks.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.372_20220630000000 Medication data (PULL)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.373-2022-06-30T000000.html Retrieving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGR<br /> &lt;section end=medmij1 /&gt;<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Retrieve/serve medication data}}<br /> &lt;section begin=medmij2 /&gt;<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.374-2022-06-30T000000.html Serving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain all medication data or specific parts matching various parameters, they issue a retrieve medication data request message. This message uses the HTTP GET method parameterized query against the server's medication FHIR endpoints. These endpoints can be one of the following:<br /> * MedicationRequest<br /> * MedicationDispense<br /> * MedicationStatement<br /> * MedicationAdministration<br /> <br /> The search interaction is performed by an HTTP GET conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query. Multiple request messages may be needed to retrieve all desired information.<br /> <br /> &lt;pre&gt;GET [base]/[type]{?[parameters]}&lt;/pre&gt;<br /> <br /> ==== Search parameters ====<br /> All search parameters listed in the table below SHALL be supported for processing by servers and MAY be supported by clients.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | MP9 search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Description<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Example<br /> &lt;section end=medmij2 /&gt;<br /> |-<br /> | PatientIdentificationNumber<br /> | Search on patient.<br /> | {{fhir|patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;&gt;This search parameter only needs to be supported when patient identification requires the use of search parameters, see [[#Patient_identification|section 2.4]].&lt;/ref&gt;<br /> {{fhir|subject:Patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;/&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233.<br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> &lt;section begin=medmij3 /&gt;<br /> |-<br /> | Identification<br /> | Search on identifier.<br /> | {{fhir|identifier}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves a MedicationRequest resource with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?identifier=http://example.nl/fhir/NamingSystem/MedicationRequest|999922448&lt;/pre&gt;<br /> |-<br /> | Identification<br /> | Search on the pharmaceutical treatment identifier. <br /> Note: retrieval of all medication resources belonging to one pharmaceutical treatment requires to search on all medication resource types.<br /> | {{fhir|pharmaceutical-treatment-identifier}} &lt;ref name=&quot;custom-searchparameter&quot;&gt;The search parameter consists of a custom FHIR search parameter not represented in the FHIR specification. Note that for {{fhir|MedicationRequest.category}} and {{fhir|MedicationStatement.category}} a core search parameter is available, hence no custom one is needed in those cases.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that are part of a pharmaceutical treatment with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?pharmaceutical-treatment-identifier=http://example.nl/fhir/NamingSystem/pharmaceuticaltreatment|1247848&lt;/pre&gt;<br /> |-<br /> | rowspan=&quot;4&quot; | Type<br /> | rowspan=&quot;4&quot; | Search on type of medication building block. <br /> | rowspan=&quot;4&quot; | {{fhir|category}} &lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block DispenseRequest.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block VariableDosingRegimen.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&lt;/pre&gt;<br /> |-<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&lt;/pre&gt;<br /> Retrieves all MedicationDispense resources that represent the building block AdministrationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&lt;/pre&gt;<br /> |-<br /> | MedicationStatement<br /> | Retrieves all MedicationStatement resources that represent the building block MedicationUse2.<br /> &lt;pre&gt;GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&lt;/pre&gt;<br /> |-<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&lt;/pre&gt;<br /> |-<br /> | MedicationCode<br /> | Search on medication code.<br /> | {{fhir|medication.code}}&lt;ref&gt;[https://www.hl7.org/fhir/r4/search.html#chaining Chained search parameter]: searches the medicationReference required in each building block for its {{fhir|.code}}.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and have Carbasalaatcalcium Sandoz 600 30 as medication.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&lt;/pre&gt;<br /> |-<br /> | PeriodOfUse<br /> | 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.<br /> Whenever a search is done on the MedicationAgreement, VariableDosingRegimen or AdministrationAgreement building blocks it is required to also include the latest stopped building blocks of that kind within each pharmaceutical treatment, even if these have a period of use outside the PeriodOfUse that is being searched on.<br /> | {{fhir|period-of-use}}&lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement&lt;ref&gt;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.&lt;/ref&gt;<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and were in effect from 01-01-2010.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;period-of-use=ge2010-01-01&lt;/pre&gt;<br /> |-<br /> | DispensePeriod <br /> | Returns all medication dispenses within the specified time period.<br /> | {{fhir|whenhandedover}}<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense and were handed over within a 2 year period.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;whenhandedover=ge2010-01-01&amp;whenhandedover=le2011-12-31&lt;/pre&gt;<br /> |-<br /> | AdministrationPeriod <br /> | Returns all medication administrations within the specified time period.<br /> | {{fhir|effective-time}}<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2 and where administration happened on a specific day.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;effective-time=eq2022-01-01&lt;/pre&gt;<br /> |-<br /> | -<br /> | The client may request that the server returns resources related to the search results, in order to reduce the overall network delay of repeated retrievals of related resources.<br /> Supporting the include of the Patient and Medication resources referenced by building blocks is required. Others (Organization, Location, PractitionerRole, Practitioner, RelatedPerson, Observation) are optional. However: all resources referenced per literal reference SHALL be resolvable [[FHIR:V1.0_FHIR_IG_R4#Including_referenced_resources|per the Nictiz IG]].<br /> | {{fhir|&lt;nowiki&gt;_include=[type]:patient&lt;/nowiki&gt;}}<br /> {{fhir|&lt;nowiki&gt;_include=[type]:medication&lt;/nowiki&gt;}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that have Carbasalaatcalcium Sandoz 600 30 as medication and includes the Medication resource in the search results.<br /> &lt;pre&gt;GET [base]/MedicationRequest?medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&amp;_include=MedicationRequest:medication&lt;/pre&gt;<br /> |}<br /> <br /> The following custom search parameters are defined for this transaction:<br /> <br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/pharmaceutical-treatment-identifier|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/category|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/period-of-use|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> <br /> ==== Retrieve all medication data ====<br /> To retrieve all known medication data, a client has to execute the following requests to retrieve all known medication data per building block, including referenced Medication resources:<br /> <br /> &lt;pre&gt;<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&amp;_include=MedicationStatement:medication<br /> GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;_include=MedicationStatement:medication<br /> &lt;/pre&gt;<br /> <br /> Note that in the current use cases, these search requests are always executed in the context of a single patient and thus should include a patient identification mechanism (see [[#Patient_identification|‘Patient identification’]]).<br /> <br /> === Serve (response message) ===<br /> The server returns an HTTP Status code appropriate to the processing outcome and returns a Bundle, with {{fhir|Bundle.type}} = {{term|searchset}}, including the resources matching the search query medication data. The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> &lt;section end=medmij3 /&gt;<br /> == Medication data (Send/Receive) ==<br /> The send medication data transaction is used by the client to send medication data to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.375_20220630000000 Medication data (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.376-2022-06-30T000000.html Sending medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication data}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication data<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because medication data consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below. Because of the informative nature of the transaction, '''no''' [[#Actionable_tag|{{term|actionable}} tags]] shall be present.<br /> <br /> === Receive (response message) ===<br /> The server checks each resource present within the Bundle it receives for the absence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication overview (Retrieve/Serve) ==<br /> The retrieve medication overview transaction is used by the client to retrieve a medication overview from the server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.388_20220630000000 Medication overview (PULL)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.389-2022-06-30T000000.html Retrieving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOR<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Retrieve/serve medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.390-2022-06-30T000000.html Serving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain a patient's medication overview, they issue a retrieve medication overview request message. This message uses an extended operation on the RESTful API to obtain a medication overview from a server. An operation is needed because the server will formulate the content of the response based on its internal business logic. The medication overview can not easily be described by standardized RESTful requests. <br /> <br /> The client executes a {{Simplifier|http://nictiz.nl/fhir/OperationDefinition/Medication-Overview|nictiz.fhir.nl.r4.medicationprocess9|title=medication-overview operation}} with an HTTP GET command conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query.<br /> <br /> &lt;pre&gt;<br /> GET [base]/$medication-overview<br /> &lt;/pre&gt;<br /> <br /> === Serve (response message) ===<br /> 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.<br /> <br /> 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].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication overview (Send/Receive) ==<br /> The send medication overview transaction is used by the client to send a medication overview to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.391_20220630000000 Medication overview (PUSH)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.392-2022-06-30T000000.html Sending medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication overview<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication overview consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> 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.<br /> <br /> 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].<br /> <br /> === Receive (response message) ===<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication prescription (Send/Receive) ==<br /> The send medication prescription transaction is used by the client to send a request to dispense medication (Dutch: verstrekkingsverzoek) or process modifications to a medication agreement (Dutch: medicatieafspraak) to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.141-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.394_20220630000000 Medication prescription (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.395-2022-06-30T000000.html Sending medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescription|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication prescription}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescription-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}) and optionally a DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below<br /> <br /> The mp-MedicationPrescription-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the MedicationAgreement and DispenseRequest building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|order}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Medication_prescription_processing_.28Send.2FReceive.29|‘Send medication prescription processing’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication prescription processing (Send/Receive) ==<br /> The send medication prescription processing transaction is used by the client to send data on the processing of a medication agreement (Dutch: medicatieafspraak) and possibly a dispense request (Dutch: verstrekkingsverzoek), in the form of an administration agreement (Dutch: toedieningsafspraak) and optionally a medication dispense (Dutch: medicatieverstrekking).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.143-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.406_20220630000000 Medication prescription processing (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.407-2022-06-30T000000.html Sending data on processing of medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescriptionProcessing|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication prescription processing}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving data on processing of medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because data on processing a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescriptionProcessing-Bundle profile, which contains at least an AdministrationAgreement building block and optionally a MedicationDispense building block. Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-MedicationPrescriptionProcessing-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the AdministrationAgreement and MedicationDispense building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Proposal dispense request (Send/Receive) ==<br /> The send proposal dispense request transaction is used by the client to inform the server about a new or modified proposal dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.400_20220630000000 Proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.401-2022-06-30T000000.html Sending proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal dispense request consists of a DispenseRequest building block along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalDispenseRequest-Bundle profile, which contains one DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalDispenseRequest-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the DispenseRequest building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_dispense_request_.28Send.2FReceive.29|‘Send reply proposal dispense request’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Reply proposal dispense request (Send/Receive) ==<br /> The send reply proposal dispense request transaction is used by the client to inform the server about a reply on a proposed dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.403_20220630000000 Reply proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.404-2022-06-30T000000.html Sending reply proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive reply proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal dispense request consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalDispenseRequest-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalDispenseRequest profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed dispense request that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalDispenseRequest-Bundle profile).<br /> <br /> The mp-ReplyProposalDispenseRequest profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Proposal medication agreement (Send/Receive) ==<br /> The send proposal medication agreement transaction is used by the client to inform the server about a new or modified proposal medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.397_20220630000000 Proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.398-2022-06-30T000000.html Sending proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal medication agreement consists of a MedicationAgreement building block along with supporting resources, a {{term|transaction}} interaction is used.<br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalMedicationAgreement-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalMedicationAgreement-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the MedicationAgreement building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_medication_agreement_.28Send.2FReceive.29|‘Send reply proposal medication agreement’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Reply proposal medication agreement (Send/Receive) ==<br /> The send reply proposal medication agreement transaction is used by the client to inform the server about a reply on a proposed medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.445_20220630000000 Reply proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.446-2022-06-30T000000.html Sending reply proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive reply proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal medication agreement consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalMedicationAgreement-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalMedicationAgreement profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed medication agreement that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalMedicationAgreement-Bundle profile).<br /> <br /> The mp-ReplyProposalMedicationAgreement profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> =Release notes=<br /> Release notes can be found [[mp:V3.0.0-beta.3_releasenotes|here]].<br /> <br /> =Footnotes=<br /> &lt;references/&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=mp:V3.0.0-rc.2_MedicationProcess9_FHIR&diff=206663 2024-03-06T20:19:26Z

<p>Luud Slagter: /* Patient identification */</p> <hr /> <div>__NOINDEX__<br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide Medication Process 9 version {{VersieInfo|mp9|release=V3.0.0}} }}<br /> <br /> __TOC__<br /> <br /> = Introduction =<br /> 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.<br /> <br /> 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.<br /> <br /> This IG first describes the boundaries and relationships in place, after which the implementation is described per transaction.<br /> <br /> = Boundaries and relationships =<br /> == Building blocks and profiles ==<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> Because the way 90 million numbers are exchanged is not compatible with the 2020 publication of zib PharmaceuticalProduct, a fork of the corresponding nl-core profile called 'mp-PharmaceuticalProduct' has been introduced.<br /> <br /> {{NoteBoxNictizR4Package|p1=nictiz.fhir.nl.r4.medicationprocess9|v1={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|p2=nictiz.fhir.nl.r4.nl-core|v2={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> <br /> 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:<br /> * MP9 version 2.0.0 makes use of version 1.0.0 of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package;<br /> * MP9 version 3.0.0-beta.x makes use of version 2.0.0-beta.x of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package.<br /> <br /> === Medication building blocks ===<br /> <br /> As described above, the main medication building blocks have no dependency on any zib2020 counterparts, resulting in so-called ‘mp’ profiles. Moreover, note that the building block VariableDosingRegimen does not have a zib counterpart, hence it makes sense to include it as an mp profile as well.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |}<br /> <br /> === Supporting building blocks ===<br /> <br /> Additionally, the standard uses several supporting building blocks referenced from the main medication building blocks. All supporting building blocks are part of the [[FHIR:V1.0_FHIR_IG_R4#Functional_definitions|‘nl-core’ package]]&lt;ref&gt;Although the nl-core package is still in beta-status, HL7 Netherlands has validated the profiles mentioned and assigned the status 'STU-NL' for use in the MP9 Kickstart, see [[Media:HL7_Nederland_disclaimer_STU-NL.pdf]]&lt;/ref&gt;.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> Note the following:<br /> * Each occurrence of the zib HealthProfessional is normally represented by '''two''' FHIR resources: an instance of nl-core-HealthProfessional-PractitionerRole and an instance of nl-core-HealthProfessional-Practitioner. Sending systems should only fill the reference to the PractitionerRole instance where relevant. Receiving systems can resolve the reference to the Practitioner resource from that PractitionerRole instance.<br /> * The zib HealthcareProvider is mapped to both a Location and Organization profile. Most often, the Location profile acts as the focal resource, because most references to this zib are concerned about the recording of the physical location where the care to patient/client takes place rather than the organizational information. For the latter, the profile on Organization is used which is referenced using the {{fhir|Location.managingOrganization}} element. Sending systems should only fill the reference to the Location instance where relevant. Incidentally, concepts that are only concerned with organizational information can refer to the Organization instance.<br /> <br /> === Transaction specific profiles ===<br /> <br /> For several transactions, additional profiles are provided. For each transaction the profile relevant is explicitly mentioned in the corresponding subsection.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |}<br /> <br /> ====Bundle profiles====<br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == Mappings between profiles and data set ==<br /> 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.<br /> <br /> 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:<br /> * 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)<br /> ** 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.<br /> ** 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.<br /> * If an element in the functional definition is removed<br /> ** and the element had a zib mapping applied (not on an extension), the zib mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> ** and the element had a mapping applied to the previous version of MP9 (not on an extension), that mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> * If an element in the functional definition is removed and the element had a mapping applied on an extension, that extension is removed entirely. In particular no {{term|[DEPRECATED]}} mapping will be visible in the FHIR profile. This is done to ensure no redundant extensions remain in the FHIR profiles.<br /> <br /> Moreover, all mappings to earlier versions of MP9 (i.e. versions before the previous version) are entirely removed.<br /> <br /> Following the procedure outlined above thus results in the following:<br /> * 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.<br /> * All incompatible changes made in the latest version with respect to the previous version are marked.<br /> * Exceptions are extensions that would otherwise only contain deprecated mappings; these are removed fully.<br /> <br /> 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’]].<br /> <br /> 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.<br /> <br /> 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]].<br /> <br /> == Pharmaceutical treatment ==<br /> 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.<br /> <br /> == Patient identification ==<br /> This implementation guide assumes that the client system is able to make a connection to the right server that contains the patient's information. It does not provide information on finding the right server nor does it provide information about security. Moreover, each transaction is performed in the context of a specific patient, whose context might have been established using the authentication mechanisms described in external specifications such as the MedMij ‘Afsprakenstelsel’ or through the usage of search parameters for patient identification. <br /> <br /> Each server is required to perform filtering based on the patient associated with the context for the request or based on the patient identification search parameters, which is a [https://www.hl7.org/fhir/r4/search.html#chaining chained search parameter] for all resource types except Patient, so only the records associated with the authenticated patient are returned.<br /> <br /> When patient identification requires the use of search parameters, the following search parameters SHALL be supported:<br /> * Patient: {{fhir|identifier}}<br /> * MedicationRequest: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationDispense: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationStatement: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationAdministration: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> <br /> An example of a request that retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233:<br /> <br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> <br /> Note: All request examples in this document do not include patient identification mechanisms, partly because we want to generalize this technical design as much as possible (it being applicable to both MedMij and other use cases), and partly because this would convolute all search request examples. Requesters are assumed to include these if necessary. Since there currently are only use cases in the context of a single patient, the patient identification mechanism is actually implicitly assumed to be present in all search requests.<br /> <br /> == Resource identification ==<br /> 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}}.<br /> <br /> 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 &lt;code&gt;@root&lt;/code&gt; and &lt;code&gt;@extension&lt;/code&gt; (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.<br /> <br /> 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|release=V3.0.0}}}} 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]].<br /> <br /> == Differentiating between transactions ==<br /> All transactions described in this IG use the same medication building blocks in different combinations and settings, making it necessary to differentiate between them. Several mechanisms are used to achieve this. Aside from PUSH/PULL, the type of medication building blocks, supporting resources like List and Communication for specific transactions and fixing the value of specific FHIR elements in applicable profiles, the {{term|actionable}} tag is used. The latter is described more in depth in the following section. Next to that, a summarizing table is provided.<br /> <br /> Note that {{fhir|Resource.meta.profile}}, although present in each building block (see [[FHIR:V1.0_FHIR_IG_R4#Profile_use_and_declaration|the general FHIR IG on ‘Profile use and declaration’]]), SHOULD [https://hl7.org/fhir/r4/resource.html#profile-tags not be used for identification of the building block type] and therefore for differentiating between transactions.<br /> <br /> === Actionable tag ===<br /> To differentiate between sending or serving building blocks that are either of informative nature or of actionable nature, the {{term|actionable}} tag is used. [https://hl7.org/fhir/r4/resource.html#tag Tags] are {{datatype|Coding}} elements present in {{fhir|Resource.meta.tag}} used for workflow management.<br /> <br /> If applicable, the profiles used by a transaction require the use of {{fhir|.meta.tag}} with {{fhir|.system}} = {{term|&lt;nowiki&gt;http://terminology.hl7.org/CodeSystem/common-tags&lt;/nowiki&gt;}} and {{fhir|.code}} = {{term|actionable}} to indicate that the resource is part of a request intended to be acted upon. The absence of this tag indicates that the resource is merely of informative nature.<br /> <br /> It is up to systems to determine how and when the transactions using the {{term|actionable}} tag are handled from a functional perspective. Systems may store the resource including the {{term|actionable}} tag or remove it either upon storing or when the request is acted upon. However, systems SHALL make sure the tag is removed when serving or sending the resource as part of an informative transaction.<br /> <br /> === Summarizing table ===<br /> {| class=&quot;wikitable&quot; <br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | PUSH/PULL<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building blocks<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | {{term|actionable}} tag<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR element value<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Other<br /> |-<br /> | Medication data (Retrieve/Serve)<br /> | PULL<br /> | One or more of all building blocks<br /> | No<br /> |<br /> | <br /> |-<br /> | Medication data (Send/Receive)<br /> | PUSH<br /> | One or more of all building blocks<br /> | No<br /> |<br /> |<br /> |-<br /> | Medication overview (Retrieve/Serve)<br /> | PULL<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication overview (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication prescription (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, DispenseRequest (optional)<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|order}} (for both MedicationAgreement and DispenseRequest building blocks)<br /> | <br /> |-<br /> | Medication prescription processing (Send/Receive)<br /> | PUSH<br /> | AdministrationAgreement, MedicationDispense (optional)<br /> | Yes<br /> | <br /> | <br /> |-<br /> | Proposal dispense request (Send/Receive)<br /> | PUSH<br /> | DispenseRequest<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal dispense request (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to DispenseRequest<br /> |-<br /> | Proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to MedicationAgreement<br /> |}<br /> <br /> = Transactions =<br /> 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’.<br /> &lt;section begin=medmij1 /&gt;<br /> == Medication data (Retrieve/Serve) ==<br /> The retrieve medication data transaction is used by the client to retrieve medication data from a server. The client can retrieve its desired information by searching for specific medication building blocks.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.372_20220630000000 Medication data (PULL)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.373-2022-06-30T000000.html Retrieving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGR<br /> &lt;section end=medmij1 /&gt;<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Retrieve/serve medication data}}<br /> &lt;section begin=medmij2 /&gt;<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.374-2022-06-30T000000.html Serving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain all medication data or specific parts matching various parameters, they issue a retrieve medication data request message. This message uses the HTTP GET method parameterized query against the server's medication FHIR endpoints. These endpoints can be one of the following:<br /> * MedicationRequest<br /> * MedicationDispense<br /> * MedicationStatement<br /> * MedicationAdministration<br /> <br /> The search interaction is performed by an HTTP GET conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query. Multiple request messages may be needed to retrieve all desired information.<br /> <br /> &lt;pre&gt;GET [base]/[type]{?[parameters]}&lt;/pre&gt;<br /> <br /> ==== Search parameters ====<br /> All search parameters listed in the table below SHALL be supported for processing by servers and MAY be supported by clients.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | MP9 search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Description<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Example<br /> &lt;section end=medmij2 /&gt;<br /> |-<br /> | PatientIdentificationNumber<br /> | Search on patient.<br /> | {{fhir|patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;&gt;This search parameter only needs to be supported when patient identification requires the use of search parameters, see [[#Patient_identification|section 2.4]].&lt;/ref&gt;<br /> {{fhir|subject:Patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;/&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233.<br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> &lt;section begin=medmij3 /&gt;<br /> |-<br /> | Identification<br /> | Search on identifier.<br /> | {{fhir|identifier}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves a MedicationRequest resource with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?identifier=http://example.nl/fhir/NamingSystem/MedicationRequest|999922448&lt;/pre&gt;<br /> |-<br /> | Identification<br /> | Search on the pharmaceutical treatment identifier. <br /> Note: retrieval of all medication resources belonging to one pharmaceutical treatment requires to search on all medication resource types.<br /> | {{fhir|pharmaceutical-treatment-identifier}} &lt;ref name=&quot;custom-searchparameter&quot;&gt;The search parameter consists of a custom FHIR search parameter not represented in the FHIR specification. Note that for {{fhir|MedicationRequest.category}} and {{fhir|MedicationStatement.category}} a core search parameter is available, hence no custom one is needed in those cases.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that are part of a pharmaceutical treatment with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?pharmaceutical-treatment-identifier=http://example.nl/fhir/NamingSystem/pharmaceuticaltreatment|1247848&lt;/pre&gt;<br /> |-<br /> | rowspan=&quot;4&quot; | Type<br /> | rowspan=&quot;4&quot; | Search on type of medication building block. <br /> | rowspan=&quot;4&quot; | {{fhir|category}} &lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block DispenseRequest.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block VariableDosingRegimen.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&lt;/pre&gt;<br /> |-<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&lt;/pre&gt;<br /> Retrieves all MedicationDispense resources that represent the building block AdministrationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&lt;/pre&gt;<br /> |-<br /> | MedicationStatement<br /> | Retrieves all MedicationStatement resources that represent the building block MedicationUse2.<br /> &lt;pre&gt;GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&lt;/pre&gt;<br /> |-<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&lt;/pre&gt;<br /> |-<br /> | MedicationCode<br /> | Search on medication code.<br /> | {{fhir|medication.code}}&lt;ref&gt;[https://www.hl7.org/fhir/r4/search.html#chaining Chained search parameter]: searches the medicationReference required in each building block for its {{fhir|.code}}.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and have Carbasalaatcalcium Sandoz 600 30 as medication.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&lt;/pre&gt;<br /> |-<br /> | PeriodOfUse<br /> | 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.<br /> Whenever a search is done on the MedicationAgreement, VariableDosingRegimen or AdministrationAgreement building blocks it is required to also include the latest stopped building blocks of that kind within each pharmaceutical treatment, even if these have a period of use outside the PeriodOfUse that is being searched on.<br /> | {{fhir|period-of-use}}&lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement&lt;ref&gt;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.&lt;/ref&gt;<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and were in effect from 01-01-2010.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;period-of-use=ge2010-01-01&lt;/pre&gt;<br /> |-<br /> | DispensePeriod <br /> | Returns all medication dispenses within the specified time period.<br /> | {{fhir|whenhandedover}}<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense and were handed over within a 2 year period.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;whenhandedover=ge2010-01-01&amp;whenhandedover=le2011-12-31&lt;/pre&gt;<br /> |-<br /> | AdministrationPeriod <br /> | Returns all medication administrations within the specified time period.<br /> | {{fhir|effective-time}}<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2 and where administration happened on a specific day.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;effective-time=eq2022-01-01&lt;/pre&gt;<br /> |-<br /> | -<br /> | The client may request that the server returns resources related to the search results, in order to reduce the overall network delay of repeated retrievals of related resources.<br /> Supporting the include of the Patient and Medication resources referenced by building blocks is required. Others (Organization, Location, PractitionerRole, Practitioner, RelatedPerson, Observation) are optional. However: all resources referenced per literal reference SHALL be resolvable [[FHIR:V1.0_FHIR_IG_R4#Including_referenced_resources|per the Nictiz IG]].<br /> | {{fhir|&lt;nowiki&gt;_include=[type]:patient&lt;/nowiki&gt;}}<br /> {{fhir|&lt;nowiki&gt;_include=[type]:medication&lt;/nowiki&gt;}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that have Carbasalaatcalcium Sandoz 600 30 as medication and includes the Medication resource in the search results.<br /> &lt;pre&gt;GET [base]/MedicationRequest?medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&amp;_include=MedicationRequest:medication&lt;/pre&gt;<br /> |}<br /> <br /> The following custom search parameters are defined for this transaction:<br /> <br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/pharmaceutical-treatment-identifier|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/category|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/period-of-use|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> <br /> ==== Retrieve all medication data ====<br /> To retrieve all known medication data, a client has to execute the following requests to retrieve all known medication data per building block, including referenced Medication resources:<br /> <br /> &lt;pre&gt;<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&amp;_include=MedicationStatement:medication<br /> GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;_include=MedicationStatement:medication<br /> &lt;/pre&gt;<br /> <br /> === Serve (response message) ===<br /> The server returns an HTTP Status code appropriate to the processing outcome and returns a Bundle, with {{fhir|Bundle.type}} = {{term|searchset}}, including the resources matching the search query medication data. The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> &lt;section end=medmij3 /&gt;<br /> == Medication data (Send/Receive) ==<br /> The send medication data transaction is used by the client to send medication data to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.375_20220630000000 Medication data (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.376-2022-06-30T000000.html Sending medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication data}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication data<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because medication data consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below. Because of the informative nature of the transaction, '''no''' [[#Actionable_tag|{{term|actionable}} tags]] shall be present.<br /> <br /> === Receive (response message) ===<br /> The server checks each resource present within the Bundle it receives for the absence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication overview (Retrieve/Serve) ==<br /> The retrieve medication overview transaction is used by the client to retrieve a medication overview from the server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.388_20220630000000 Medication overview (PULL)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.389-2022-06-30T000000.html Retrieving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOR<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Retrieve/serve medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.390-2022-06-30T000000.html Serving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain a patient's medication overview, they issue a retrieve medication overview request message. This message uses an extended operation on the RESTful API to obtain a medication overview from a server. An operation is needed because the server will formulate the content of the response based on its internal business logic. The medication overview can not easily be described by standardized RESTful requests. <br /> <br /> The client executes a {{Simplifier|http://nictiz.nl/fhir/OperationDefinition/Medication-Overview|nictiz.fhir.nl.r4.medicationprocess9|title=medication-overview operation}} with an HTTP GET command conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query.<br /> <br /> &lt;pre&gt;<br /> GET [base]/$medication-overview<br /> &lt;/pre&gt;<br /> <br /> === Serve (response message) ===<br /> 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.<br /> <br /> 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].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication overview (Send/Receive) ==<br /> The send medication overview transaction is used by the client to send a medication overview to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.391_20220630000000 Medication overview (PUSH)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.392-2022-06-30T000000.html Sending medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication overview<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication overview consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> 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.<br /> <br /> 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].<br /> <br /> === Receive (response message) ===<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication prescription (Send/Receive) ==<br /> The send medication prescription transaction is used by the client to send a request to dispense medication (Dutch: verstrekkingsverzoek) or process modifications to a medication agreement (Dutch: medicatieafspraak) to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.141-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.394_20220630000000 Medication prescription (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.395-2022-06-30T000000.html Sending medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescription|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication prescription}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescription-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}) and optionally a DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below<br /> <br /> The mp-MedicationPrescription-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the MedicationAgreement and DispenseRequest building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|order}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Medication_prescription_processing_.28Send.2FReceive.29|‘Send medication prescription processing’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication prescription processing (Send/Receive) ==<br /> The send medication prescription processing transaction is used by the client to send data on the processing of a medication agreement (Dutch: medicatieafspraak) and possibly a dispense request (Dutch: verstrekkingsverzoek), in the form of an administration agreement (Dutch: toedieningsafspraak) and optionally a medication dispense (Dutch: medicatieverstrekking).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.143-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.406_20220630000000 Medication prescription processing (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.407-2022-06-30T000000.html Sending data on processing of medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescriptionProcessing|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication prescription processing}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving data on processing of medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because data on processing a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescriptionProcessing-Bundle profile, which contains at least an AdministrationAgreement building block and optionally a MedicationDispense building block. Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-MedicationPrescriptionProcessing-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the AdministrationAgreement and MedicationDispense building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Proposal dispense request (Send/Receive) ==<br /> The send proposal dispense request transaction is used by the client to inform the server about a new or modified proposal dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.400_20220630000000 Proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.401-2022-06-30T000000.html Sending proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal dispense request consists of a DispenseRequest building block along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalDispenseRequest-Bundle profile, which contains one DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalDispenseRequest-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the DispenseRequest building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_dispense_request_.28Send.2FReceive.29|‘Send reply proposal dispense request’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Reply proposal dispense request (Send/Receive) ==<br /> The send reply proposal dispense request transaction is used by the client to inform the server about a reply on a proposed dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.403_20220630000000 Reply proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.404-2022-06-30T000000.html Sending reply proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive reply proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal dispense request consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalDispenseRequest-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalDispenseRequest profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed dispense request that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalDispenseRequest-Bundle profile).<br /> <br /> The mp-ReplyProposalDispenseRequest profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Proposal medication agreement (Send/Receive) ==<br /> The send proposal medication agreement transaction is used by the client to inform the server about a new or modified proposal medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.397_20220630000000 Proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.398-2022-06-30T000000.html Sending proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal medication agreement consists of a MedicationAgreement building block along with supporting resources, a {{term|transaction}} interaction is used.<br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalMedicationAgreement-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalMedicationAgreement-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the MedicationAgreement building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_medication_agreement_.28Send.2FReceive.29|‘Send reply proposal medication agreement’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Reply proposal medication agreement (Send/Receive) ==<br /> The send reply proposal medication agreement transaction is used by the client to inform the server about a reply on a proposed medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.445_20220630000000 Reply proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.446-2022-06-30T000000.html Sending reply proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive reply proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal medication agreement consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalMedicationAgreement-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalMedicationAgreement profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed medication agreement that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalMedicationAgreement-Bundle profile).<br /> <br /> The mp-ReplyProposalMedicationAgreement profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> =Release notes=<br /> Release notes can be found [[mp:V3.0.0-beta.3_releasenotes|here]].<br /> <br /> =Footnotes=<br /> &lt;references/&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=mp:V3.0.0-rc.2_MedicationProcess9_FHIR&diff=206662 2024-03-06T20:18:48Z

<p>Luud Slagter: /* Patient identification */</p> <hr /> <div>__NOINDEX__<br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide Medication Process 9 version {{VersieInfo|mp9|release=V3.0.0}} }}<br /> <br /> __TOC__<br /> <br /> = Introduction =<br /> 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.<br /> <br /> 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.<br /> <br /> This IG first describes the boundaries and relationships in place, after which the implementation is described per transaction.<br /> <br /> = Boundaries and relationships =<br /> == Building blocks and profiles ==<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> Because the way 90 million numbers are exchanged is not compatible with the 2020 publication of zib PharmaceuticalProduct, a fork of the corresponding nl-core profile called 'mp-PharmaceuticalProduct' has been introduced.<br /> <br /> {{NoteBoxNictizR4Package|p1=nictiz.fhir.nl.r4.medicationprocess9|v1={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|p2=nictiz.fhir.nl.r4.nl-core|v2={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> <br /> 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:<br /> * MP9 version 2.0.0 makes use of version 1.0.0 of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package;<br /> * MP9 version 3.0.0-beta.x makes use of version 2.0.0-beta.x of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package.<br /> <br /> === Medication building blocks ===<br /> <br /> As described above, the main medication building blocks have no dependency on any zib2020 counterparts, resulting in so-called ‘mp’ profiles. Moreover, note that the building block VariableDosingRegimen does not have a zib counterpart, hence it makes sense to include it as an mp profile as well.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |}<br /> <br /> === Supporting building blocks ===<br /> <br /> Additionally, the standard uses several supporting building blocks referenced from the main medication building blocks. All supporting building blocks are part of the [[FHIR:V1.0_FHIR_IG_R4#Functional_definitions|‘nl-core’ package]]&lt;ref&gt;Although the nl-core package is still in beta-status, HL7 Netherlands has validated the profiles mentioned and assigned the status 'STU-NL' for use in the MP9 Kickstart, see [[Media:HL7_Nederland_disclaimer_STU-NL.pdf]]&lt;/ref&gt;.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> Note the following:<br /> * Each occurrence of the zib HealthProfessional is normally represented by '''two''' FHIR resources: an instance of nl-core-HealthProfessional-PractitionerRole and an instance of nl-core-HealthProfessional-Practitioner. Sending systems should only fill the reference to the PractitionerRole instance where relevant. Receiving systems can resolve the reference to the Practitioner resource from that PractitionerRole instance.<br /> * The zib HealthcareProvider is mapped to both a Location and Organization profile. Most often, the Location profile acts as the focal resource, because most references to this zib are concerned about the recording of the physical location where the care to patient/client takes place rather than the organizational information. For the latter, the profile on Organization is used which is referenced using the {{fhir|Location.managingOrganization}} element. Sending systems should only fill the reference to the Location instance where relevant. Incidentally, concepts that are only concerned with organizational information can refer to the Organization instance.<br /> <br /> === Transaction specific profiles ===<br /> <br /> For several transactions, additional profiles are provided. For each transaction the profile relevant is explicitly mentioned in the corresponding subsection.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |}<br /> <br /> ====Bundle profiles====<br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == Mappings between profiles and data set ==<br /> 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.<br /> <br /> 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:<br /> * 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)<br /> ** 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.<br /> ** 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.<br /> * If an element in the functional definition is removed<br /> ** and the element had a zib mapping applied (not on an extension), the zib mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> ** and the element had a mapping applied to the previous version of MP9 (not on an extension), that mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> * If an element in the functional definition is removed and the element had a mapping applied on an extension, that extension is removed entirely. In particular no {{term|[DEPRECATED]}} mapping will be visible in the FHIR profile. This is done to ensure no redundant extensions remain in the FHIR profiles.<br /> <br /> Moreover, all mappings to earlier versions of MP9 (i.e. versions before the previous version) are entirely removed.<br /> <br /> Following the procedure outlined above thus results in the following:<br /> * 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.<br /> * All incompatible changes made in the latest version with respect to the previous version are marked.<br /> * Exceptions are extensions that would otherwise only contain deprecated mappings; these are removed fully.<br /> <br /> 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’]].<br /> <br /> 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.<br /> <br /> 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]].<br /> <br /> == Pharmaceutical treatment ==<br /> 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.<br /> <br /> == Patient identification ==<br /> This implementation guide assumes that the client system is able to make a connection to the right server that contains the patient's information. It does not provide information on finding the right server nor does it provide information about security. Moreover, each transaction is performed in the context of a specific patient, whose context might have been established using the authentication mechanisms described in external specifications such as the MedMij ‘Afsprakenstelsel’ or through the usage of search parameters for patient identification. <br /> <br /> Each server is required to perform filtering based on the patient associated with the context for the request or based on the patient identification search parameters, which is a [https://www.hl7.org/fhir/r4/search.html#chaining chained search parameter] for all resource types except Patient, so only the records associated with the authenticated patient are returned.<br /> <br /> When patient identification requires the use of search parameters, the following search parameters SHALL be supported:<br /> * Patient: {{fhir|identifier}}<br /> * MedicationRequest: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationDispense: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationStatement: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationAdministration: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> <br /> An example of a request that retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233:<br /> <br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> <br /> Note: All request examples in this document do not include patient identification mechanisms, partly because we want to to generalize this technical design as much as possible (it being applicable to both MedMij and other use cases), and partly because this would convolute all search request examples. Requesters are assumed to include these if necessary. Since there currently are only use cases in the context of a single patient, the patient identification mechanism is actually implicitly assumed to be present in all search requests.<br /> <br /> == Resource identification ==<br /> 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}}.<br /> <br /> 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 &lt;code&gt;@root&lt;/code&gt; and &lt;code&gt;@extension&lt;/code&gt; (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.<br /> <br /> 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|release=V3.0.0}}}} 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]].<br /> <br /> == Differentiating between transactions ==<br /> All transactions described in this IG use the same medication building blocks in different combinations and settings, making it necessary to differentiate between them. Several mechanisms are used to achieve this. Aside from PUSH/PULL, the type of medication building blocks, supporting resources like List and Communication for specific transactions and fixing the value of specific FHIR elements in applicable profiles, the {{term|actionable}} tag is used. The latter is described more in depth in the following section. Next to that, a summarizing table is provided.<br /> <br /> Note that {{fhir|Resource.meta.profile}}, although present in each building block (see [[FHIR:V1.0_FHIR_IG_R4#Profile_use_and_declaration|the general FHIR IG on ‘Profile use and declaration’]]), SHOULD [https://hl7.org/fhir/r4/resource.html#profile-tags not be used for identification of the building block type] and therefore for differentiating between transactions.<br /> <br /> === Actionable tag ===<br /> To differentiate between sending or serving building blocks that are either of informative nature or of actionable nature, the {{term|actionable}} tag is used. [https://hl7.org/fhir/r4/resource.html#tag Tags] are {{datatype|Coding}} elements present in {{fhir|Resource.meta.tag}} used for workflow management.<br /> <br /> If applicable, the profiles used by a transaction require the use of {{fhir|.meta.tag}} with {{fhir|.system}} = {{term|&lt;nowiki&gt;http://terminology.hl7.org/CodeSystem/common-tags&lt;/nowiki&gt;}} and {{fhir|.code}} = {{term|actionable}} to indicate that the resource is part of a request intended to be acted upon. The absence of this tag indicates that the resource is merely of informative nature.<br /> <br /> It is up to systems to determine how and when the transactions using the {{term|actionable}} tag are handled from a functional perspective. Systems may store the resource including the {{term|actionable}} tag or remove it either upon storing or when the request is acted upon. However, systems SHALL make sure the tag is removed when serving or sending the resource as part of an informative transaction.<br /> <br /> === Summarizing table ===<br /> {| class=&quot;wikitable&quot; <br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | PUSH/PULL<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building blocks<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | {{term|actionable}} tag<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR element value<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Other<br /> |-<br /> | Medication data (Retrieve/Serve)<br /> | PULL<br /> | One or more of all building blocks<br /> | No<br /> |<br /> | <br /> |-<br /> | Medication data (Send/Receive)<br /> | PUSH<br /> | One or more of all building blocks<br /> | No<br /> |<br /> |<br /> |-<br /> | Medication overview (Retrieve/Serve)<br /> | PULL<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication overview (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication prescription (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, DispenseRequest (optional)<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|order}} (for both MedicationAgreement and DispenseRequest building blocks)<br /> | <br /> |-<br /> | Medication prescription processing (Send/Receive)<br /> | PUSH<br /> | AdministrationAgreement, MedicationDispense (optional)<br /> | Yes<br /> | <br /> | <br /> |-<br /> | Proposal dispense request (Send/Receive)<br /> | PUSH<br /> | DispenseRequest<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal dispense request (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to DispenseRequest<br /> |-<br /> | Proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to MedicationAgreement<br /> |}<br /> <br /> = Transactions =<br /> 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’.<br /> &lt;section begin=medmij1 /&gt;<br /> == Medication data (Retrieve/Serve) ==<br /> The retrieve medication data transaction is used by the client to retrieve medication data from a server. The client can retrieve its desired information by searching for specific medication building blocks.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.372_20220630000000 Medication data (PULL)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.373-2022-06-30T000000.html Retrieving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGR<br /> &lt;section end=medmij1 /&gt;<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Retrieve/serve medication data}}<br /> &lt;section begin=medmij2 /&gt;<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.374-2022-06-30T000000.html Serving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain all medication data or specific parts matching various parameters, they issue a retrieve medication data request message. This message uses the HTTP GET method parameterized query against the server's medication FHIR endpoints. These endpoints can be one of the following:<br /> * MedicationRequest<br /> * MedicationDispense<br /> * MedicationStatement<br /> * MedicationAdministration<br /> <br /> The search interaction is performed by an HTTP GET conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query. Multiple request messages may be needed to retrieve all desired information.<br /> <br /> &lt;pre&gt;GET [base]/[type]{?[parameters]}&lt;/pre&gt;<br /> <br /> ==== Search parameters ====<br /> All search parameters listed in the table below SHALL be supported for processing by servers and MAY be supported by clients.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | MP9 search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Description<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Example<br /> &lt;section end=medmij2 /&gt;<br /> |-<br /> | PatientIdentificationNumber<br /> | Search on patient.<br /> | {{fhir|patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;&gt;This search parameter only needs to be supported when patient identification requires the use of search parameters, see [[#Patient_identification|section 2.4]].&lt;/ref&gt;<br /> {{fhir|subject:Patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;/&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233.<br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> &lt;section begin=medmij3 /&gt;<br /> |-<br /> | Identification<br /> | Search on identifier.<br /> | {{fhir|identifier}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves a MedicationRequest resource with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?identifier=http://example.nl/fhir/NamingSystem/MedicationRequest|999922448&lt;/pre&gt;<br /> |-<br /> | Identification<br /> | Search on the pharmaceutical treatment identifier. <br /> Note: retrieval of all medication resources belonging to one pharmaceutical treatment requires to search on all medication resource types.<br /> | {{fhir|pharmaceutical-treatment-identifier}} &lt;ref name=&quot;custom-searchparameter&quot;&gt;The search parameter consists of a custom FHIR search parameter not represented in the FHIR specification. Note that for {{fhir|MedicationRequest.category}} and {{fhir|MedicationStatement.category}} a core search parameter is available, hence no custom one is needed in those cases.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that are part of a pharmaceutical treatment with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?pharmaceutical-treatment-identifier=http://example.nl/fhir/NamingSystem/pharmaceuticaltreatment|1247848&lt;/pre&gt;<br /> |-<br /> | rowspan=&quot;4&quot; | Type<br /> | rowspan=&quot;4&quot; | Search on type of medication building block. <br /> | rowspan=&quot;4&quot; | {{fhir|category}} &lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block DispenseRequest.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block VariableDosingRegimen.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&lt;/pre&gt;<br /> |-<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&lt;/pre&gt;<br /> Retrieves all MedicationDispense resources that represent the building block AdministrationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&lt;/pre&gt;<br /> |-<br /> | MedicationStatement<br /> | Retrieves all MedicationStatement resources that represent the building block MedicationUse2.<br /> &lt;pre&gt;GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&lt;/pre&gt;<br /> |-<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&lt;/pre&gt;<br /> |-<br /> | MedicationCode<br /> | Search on medication code.<br /> | {{fhir|medication.code}}&lt;ref&gt;[https://www.hl7.org/fhir/r4/search.html#chaining Chained search parameter]: searches the medicationReference required in each building block for its {{fhir|.code}}.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and have Carbasalaatcalcium Sandoz 600 30 as medication.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&lt;/pre&gt;<br /> |-<br /> | PeriodOfUse<br /> | 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.<br /> Whenever a search is done on the MedicationAgreement, VariableDosingRegimen or AdministrationAgreement building blocks it is required to also include the latest stopped building blocks of that kind within each pharmaceutical treatment, even if these have a period of use outside the PeriodOfUse that is being searched on.<br /> | {{fhir|period-of-use}}&lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement&lt;ref&gt;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.&lt;/ref&gt;<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and were in effect from 01-01-2010.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;period-of-use=ge2010-01-01&lt;/pre&gt;<br /> |-<br /> | DispensePeriod <br /> | Returns all medication dispenses within the specified time period.<br /> | {{fhir|whenhandedover}}<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense and were handed over within a 2 year period.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;whenhandedover=ge2010-01-01&amp;whenhandedover=le2011-12-31&lt;/pre&gt;<br /> |-<br /> | AdministrationPeriod <br /> | Returns all medication administrations within the specified time period.<br /> | {{fhir|effective-time}}<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2 and where administration happened on a specific day.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;effective-time=eq2022-01-01&lt;/pre&gt;<br /> |-<br /> | -<br /> | The client may request that the server returns resources related to the search results, in order to reduce the overall network delay of repeated retrievals of related resources.<br /> Supporting the include of the Patient and Medication resources referenced by building blocks is required. Others (Organization, Location, PractitionerRole, Practitioner, RelatedPerson, Observation) are optional. However: all resources referenced per literal reference SHALL be resolvable [[FHIR:V1.0_FHIR_IG_R4#Including_referenced_resources|per the Nictiz IG]].<br /> | {{fhir|&lt;nowiki&gt;_include=[type]:patient&lt;/nowiki&gt;}}<br /> {{fhir|&lt;nowiki&gt;_include=[type]:medication&lt;/nowiki&gt;}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that have Carbasalaatcalcium Sandoz 600 30 as medication and includes the Medication resource in the search results.<br /> &lt;pre&gt;GET [base]/MedicationRequest?medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&amp;_include=MedicationRequest:medication&lt;/pre&gt;<br /> |}<br /> <br /> The following custom search parameters are defined for this transaction:<br /> <br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/pharmaceutical-treatment-identifier|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/category|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/period-of-use|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> <br /> ==== Retrieve all medication data ====<br /> To retrieve all known medication data, a client has to execute the following requests to retrieve all known medication data per building block, including referenced Medication resources:<br /> <br /> &lt;pre&gt;<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&amp;_include=MedicationStatement:medication<br /> GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;_include=MedicationStatement:medication<br /> &lt;/pre&gt;<br /> <br /> === Serve (response message) ===<br /> The server returns an HTTP Status code appropriate to the processing outcome and returns a Bundle, with {{fhir|Bundle.type}} = {{term|searchset}}, including the resources matching the search query medication data. The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> &lt;section end=medmij3 /&gt;<br /> == Medication data (Send/Receive) ==<br /> The send medication data transaction is used by the client to send medication data to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.375_20220630000000 Medication data (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.376-2022-06-30T000000.html Sending medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication data}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication data<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because medication data consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below. Because of the informative nature of the transaction, '''no''' [[#Actionable_tag|{{term|actionable}} tags]] shall be present.<br /> <br /> === Receive (response message) ===<br /> The server checks each resource present within the Bundle it receives for the absence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication overview (Retrieve/Serve) ==<br /> The retrieve medication overview transaction is used by the client to retrieve a medication overview from the server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.388_20220630000000 Medication overview (PULL)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.389-2022-06-30T000000.html Retrieving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOR<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Retrieve/serve medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.390-2022-06-30T000000.html Serving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain a patient's medication overview, they issue a retrieve medication overview request message. This message uses an extended operation on the RESTful API to obtain a medication overview from a server. An operation is needed because the server will formulate the content of the response based on its internal business logic. The medication overview can not easily be described by standardized RESTful requests. <br /> <br /> The client executes a {{Simplifier|http://nictiz.nl/fhir/OperationDefinition/Medication-Overview|nictiz.fhir.nl.r4.medicationprocess9|title=medication-overview operation}} with an HTTP GET command conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query.<br /> <br /> &lt;pre&gt;<br /> GET [base]/$medication-overview<br /> &lt;/pre&gt;<br /> <br /> === Serve (response message) ===<br /> 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.<br /> <br /> 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].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication overview (Send/Receive) ==<br /> The send medication overview transaction is used by the client to send a medication overview to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.391_20220630000000 Medication overview (PUSH)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.392-2022-06-30T000000.html Sending medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication overview<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication overview consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> 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.<br /> <br /> 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].<br /> <br /> === Receive (response message) ===<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication prescription (Send/Receive) ==<br /> The send medication prescription transaction is used by the client to send a request to dispense medication (Dutch: verstrekkingsverzoek) or process modifications to a medication agreement (Dutch: medicatieafspraak) to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.141-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.394_20220630000000 Medication prescription (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.395-2022-06-30T000000.html Sending medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescription|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication prescription}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescription-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}) and optionally a DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below<br /> <br /> The mp-MedicationPrescription-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the MedicationAgreement and DispenseRequest building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|order}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Medication_prescription_processing_.28Send.2FReceive.29|‘Send medication prescription processing’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication prescription processing (Send/Receive) ==<br /> The send medication prescription processing transaction is used by the client to send data on the processing of a medication agreement (Dutch: medicatieafspraak) and possibly a dispense request (Dutch: verstrekkingsverzoek), in the form of an administration agreement (Dutch: toedieningsafspraak) and optionally a medication dispense (Dutch: medicatieverstrekking).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.143-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.406_20220630000000 Medication prescription processing (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.407-2022-06-30T000000.html Sending data on processing of medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescriptionProcessing|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication prescription processing}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving data on processing of medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because data on processing a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescriptionProcessing-Bundle profile, which contains at least an AdministrationAgreement building block and optionally a MedicationDispense building block. Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-MedicationPrescriptionProcessing-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the AdministrationAgreement and MedicationDispense building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Proposal dispense request (Send/Receive) ==<br /> The send proposal dispense request transaction is used by the client to inform the server about a new or modified proposal dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.400_20220630000000 Proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.401-2022-06-30T000000.html Sending proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal dispense request consists of a DispenseRequest building block along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalDispenseRequest-Bundle profile, which contains one DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalDispenseRequest-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the DispenseRequest building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_dispense_request_.28Send.2FReceive.29|‘Send reply proposal dispense request’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Reply proposal dispense request (Send/Receive) ==<br /> The send reply proposal dispense request transaction is used by the client to inform the server about a reply on a proposed dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.403_20220630000000 Reply proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.404-2022-06-30T000000.html Sending reply proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive reply proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal dispense request consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalDispenseRequest-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalDispenseRequest profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed dispense request that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalDispenseRequest-Bundle profile).<br /> <br /> The mp-ReplyProposalDispenseRequest profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Proposal medication agreement (Send/Receive) ==<br /> The send proposal medication agreement transaction is used by the client to inform the server about a new or modified proposal medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.397_20220630000000 Proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.398-2022-06-30T000000.html Sending proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal medication agreement consists of a MedicationAgreement building block along with supporting resources, a {{term|transaction}} interaction is used.<br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalMedicationAgreement-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalMedicationAgreement-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the MedicationAgreement building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_medication_agreement_.28Send.2FReceive.29|‘Send reply proposal medication agreement’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Reply proposal medication agreement (Send/Receive) ==<br /> The send reply proposal medication agreement transaction is used by the client to inform the server about a reply on a proposed medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.445_20220630000000 Reply proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.446-2022-06-30T000000.html Sending reply proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive reply proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal medication agreement consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalMedicationAgreement-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalMedicationAgreement profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed medication agreement that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalMedicationAgreement-Bundle profile).<br /> <br /> The mp-ReplyProposalMedicationAgreement profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> =Release notes=<br /> Release notes can be found [[mp:V3.0.0-beta.3_releasenotes|here]].<br /> <br /> =Footnotes=<br /> &lt;references/&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=mp:V3.0.0-rc.2_MedicationProcess9_FHIR&diff=206661 2024-03-06T20:15:20Z

<p>Luud Slagter: /* Search parameters */ MP-1487: Added subject:Patient.identifier to search parameters</p> <hr /> <div>__NOINDEX__<br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide Medication Process 9 version {{VersieInfo|mp9|release=V3.0.0}} }}<br /> <br /> __TOC__<br /> <br /> = Introduction =<br /> 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.<br /> <br /> 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.<br /> <br /> This IG first describes the boundaries and relationships in place, after which the implementation is described per transaction.<br /> <br /> = Boundaries and relationships =<br /> == Building blocks and profiles ==<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> Because the way 90 million numbers are exchanged is not compatible with the 2020 publication of zib PharmaceuticalProduct, a fork of the corresponding nl-core profile called 'mp-PharmaceuticalProduct' has been introduced.<br /> <br /> {{NoteBoxNictizR4Package|p1=nictiz.fhir.nl.r4.medicationprocess9|v1={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|p2=nictiz.fhir.nl.r4.nl-core|v2={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> <br /> 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:<br /> * MP9 version 2.0.0 makes use of version 1.0.0 of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package;<br /> * MP9 version 3.0.0-beta.x makes use of version 2.0.0-beta.x of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package.<br /> <br /> === Medication building blocks ===<br /> <br /> As described above, the main medication building blocks have no dependency on any zib2020 counterparts, resulting in so-called ‘mp’ profiles. Moreover, note that the building block VariableDosingRegimen does not have a zib counterpart, hence it makes sense to include it as an mp profile as well.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |}<br /> <br /> === Supporting building blocks ===<br /> <br /> Additionally, the standard uses several supporting building blocks referenced from the main medication building blocks. All supporting building blocks are part of the [[FHIR:V1.0_FHIR_IG_R4#Functional_definitions|‘nl-core’ package]]&lt;ref&gt;Although the nl-core package is still in beta-status, HL7 Netherlands has validated the profiles mentioned and assigned the status 'STU-NL' for use in the MP9 Kickstart, see [[Media:HL7_Nederland_disclaimer_STU-NL.pdf]]&lt;/ref&gt;.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> Note the following:<br /> * Each occurrence of the zib HealthProfessional is normally represented by '''two''' FHIR resources: an instance of nl-core-HealthProfessional-PractitionerRole and an instance of nl-core-HealthProfessional-Practitioner. Sending systems should only fill the reference to the PractitionerRole instance where relevant. Receiving systems can resolve the reference to the Practitioner resource from that PractitionerRole instance.<br /> * The zib HealthcareProvider is mapped to both a Location and Organization profile. Most often, the Location profile acts as the focal resource, because most references to this zib are concerned about the recording of the physical location where the care to patient/client takes place rather than the organizational information. For the latter, the profile on Organization is used which is referenced using the {{fhir|Location.managingOrganization}} element. Sending systems should only fill the reference to the Location instance where relevant. Incidentally, concepts that are only concerned with organizational information can refer to the Organization instance.<br /> <br /> === Transaction specific profiles ===<br /> <br /> For several transactions, additional profiles are provided. For each transaction the profile relevant is explicitly mentioned in the corresponding subsection.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |}<br /> <br /> ====Bundle profiles====<br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == Mappings between profiles and data set ==<br /> 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.<br /> <br /> 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:<br /> * 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)<br /> ** 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.<br /> ** 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.<br /> * If an element in the functional definition is removed<br /> ** and the element had a zib mapping applied (not on an extension), the zib mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> ** and the element had a mapping applied to the previous version of MP9 (not on an extension), that mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> * If an element in the functional definition is removed and the element had a mapping applied on an extension, that extension is removed entirely. In particular no {{term|[DEPRECATED]}} mapping will be visible in the FHIR profile. This is done to ensure no redundant extensions remain in the FHIR profiles.<br /> <br /> Moreover, all mappings to earlier versions of MP9 (i.e. versions before the previous version) are entirely removed.<br /> <br /> Following the procedure outlined above thus results in the following:<br /> * 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.<br /> * All incompatible changes made in the latest version with respect to the previous version are marked.<br /> * Exceptions are extensions that would otherwise only contain deprecated mappings; these are removed fully.<br /> <br /> 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’]].<br /> <br /> 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.<br /> <br /> 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]].<br /> <br /> == Pharmaceutical treatment ==<br /> 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.<br /> <br /> == Patient identification ==<br /> This implementation guide assumes that the client system is able to make a connection to the right server that contains the patient's information. It does not provide information on finding the right server nor does it provide information about security. Moreover, each transaction is performed in the context of a specific patient, whose context might have been established using the authentication mechanisms described in external specifications such as the MedMij ‘Afsprakenstelsel’ or through the usage of search parameters for patient identification. <br /> <br /> Each server is required to perform filtering based on the patient associated with the context for the request or based on the patient identification search parameters, which is a [https://www.hl7.org/fhir/r4/search.html#chaining chained search parameter] for all resource types except Patient, so only the records associated with the authenticated patient are returned.<br /> <br /> When patient identification requires the use of search parameters, the following search parameters SHALL be supported:<br /> * Patient: {{fhir|identifier}}<br /> * MedicationRequest: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationDispense: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationStatement: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationAdministration: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> <br /> An example of a request that retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233:<br /> <br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> <br /> All request examples in this document do not include patient identification mechanisms, partly because we want to to generalize this technical design as much as possible (it being applicable to both MedMij and other use cases), and partly because this would convolute all search request examples. Requesters are assumed to include these if necessary. Since there currently are only use cases in the context of a single patient, the patient identification mechanism is actually implicitly assumed to be present in all search requests.<br /> <br /> == Resource identification ==<br /> 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}}.<br /> <br /> 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 &lt;code&gt;@root&lt;/code&gt; and &lt;code&gt;@extension&lt;/code&gt; (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.<br /> <br /> 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|release=V3.0.0}}}} 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]].<br /> <br /> == Differentiating between transactions ==<br /> All transactions described in this IG use the same medication building blocks in different combinations and settings, making it necessary to differentiate between them. Several mechanisms are used to achieve this. Aside from PUSH/PULL, the type of medication building blocks, supporting resources like List and Communication for specific transactions and fixing the value of specific FHIR elements in applicable profiles, the {{term|actionable}} tag is used. The latter is described more in depth in the following section. Next to that, a summarizing table is provided.<br /> <br /> Note that {{fhir|Resource.meta.profile}}, although present in each building block (see [[FHIR:V1.0_FHIR_IG_R4#Profile_use_and_declaration|the general FHIR IG on ‘Profile use and declaration’]]), SHOULD [https://hl7.org/fhir/r4/resource.html#profile-tags not be used for identification of the building block type] and therefore for differentiating between transactions.<br /> <br /> === Actionable tag ===<br /> To differentiate between sending or serving building blocks that are either of informative nature or of actionable nature, the {{term|actionable}} tag is used. [https://hl7.org/fhir/r4/resource.html#tag Tags] are {{datatype|Coding}} elements present in {{fhir|Resource.meta.tag}} used for workflow management.<br /> <br /> If applicable, the profiles used by a transaction require the use of {{fhir|.meta.tag}} with {{fhir|.system}} = {{term|&lt;nowiki&gt;http://terminology.hl7.org/CodeSystem/common-tags&lt;/nowiki&gt;}} and {{fhir|.code}} = {{term|actionable}} to indicate that the resource is part of a request intended to be acted upon. The absence of this tag indicates that the resource is merely of informative nature.<br /> <br /> It is up to systems to determine how and when the transactions using the {{term|actionable}} tag are handled from a functional perspective. Systems may store the resource including the {{term|actionable}} tag or remove it either upon storing or when the request is acted upon. However, systems SHALL make sure the tag is removed when serving or sending the resource as part of an informative transaction.<br /> <br /> === Summarizing table ===<br /> {| class=&quot;wikitable&quot; <br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | PUSH/PULL<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building blocks<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | {{term|actionable}} tag<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR element value<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Other<br /> |-<br /> | Medication data (Retrieve/Serve)<br /> | PULL<br /> | One or more of all building blocks<br /> | No<br /> |<br /> | <br /> |-<br /> | Medication data (Send/Receive)<br /> | PUSH<br /> | One or more of all building blocks<br /> | No<br /> |<br /> |<br /> |-<br /> | Medication overview (Retrieve/Serve)<br /> | PULL<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication overview (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication prescription (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, DispenseRequest (optional)<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|order}} (for both MedicationAgreement and DispenseRequest building blocks)<br /> | <br /> |-<br /> | Medication prescription processing (Send/Receive)<br /> | PUSH<br /> | AdministrationAgreement, MedicationDispense (optional)<br /> | Yes<br /> | <br /> | <br /> |-<br /> | Proposal dispense request (Send/Receive)<br /> | PUSH<br /> | DispenseRequest<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal dispense request (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to DispenseRequest<br /> |-<br /> | Proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to MedicationAgreement<br /> |}<br /> <br /> = Transactions =<br /> 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’.<br /> &lt;section begin=medmij1 /&gt;<br /> == Medication data (Retrieve/Serve) ==<br /> The retrieve medication data transaction is used by the client to retrieve medication data from a server. The client can retrieve its desired information by searching for specific medication building blocks.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.372_20220630000000 Medication data (PULL)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.373-2022-06-30T000000.html Retrieving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGR<br /> &lt;section end=medmij1 /&gt;<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Retrieve/serve medication data}}<br /> &lt;section begin=medmij2 /&gt;<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.374-2022-06-30T000000.html Serving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain all medication data or specific parts matching various parameters, they issue a retrieve medication data request message. This message uses the HTTP GET method parameterized query against the server's medication FHIR endpoints. These endpoints can be one of the following:<br /> * MedicationRequest<br /> * MedicationDispense<br /> * MedicationStatement<br /> * MedicationAdministration<br /> <br /> The search interaction is performed by an HTTP GET conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query. Multiple request messages may be needed to retrieve all desired information.<br /> <br /> &lt;pre&gt;GET [base]/[type]{?[parameters]}&lt;/pre&gt;<br /> <br /> ==== Search parameters ====<br /> All search parameters listed in the table below SHALL be supported for processing by servers and MAY be supported by clients.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | MP9 search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Description<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Example<br /> &lt;section end=medmij2 /&gt;<br /> |-<br /> | PatientIdentificationNumber<br /> | Search on patient.<br /> | {{fhir|patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;&gt;This search parameter only needs to be supported when patient identification requires the use of search parameters, see [[#Patient_identification|section 2.4]].&lt;/ref&gt;<br /> {{fhir|subject:Patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;/&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233.<br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> &lt;section begin=medmij3 /&gt;<br /> |-<br /> | Identification<br /> | Search on identifier.<br /> | {{fhir|identifier}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves a MedicationRequest resource with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?identifier=http://example.nl/fhir/NamingSystem/MedicationRequest|999922448&lt;/pre&gt;<br /> |-<br /> | Identification<br /> | Search on the pharmaceutical treatment identifier. <br /> Note: retrieval of all medication resources belonging to one pharmaceutical treatment requires to search on all medication resource types.<br /> | {{fhir|pharmaceutical-treatment-identifier}} &lt;ref name=&quot;custom-searchparameter&quot;&gt;The search parameter consists of a custom FHIR search parameter not represented in the FHIR specification. Note that for {{fhir|MedicationRequest.category}} and {{fhir|MedicationStatement.category}} a core search parameter is available, hence no custom one is needed in those cases.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that are part of a pharmaceutical treatment with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?pharmaceutical-treatment-identifier=http://example.nl/fhir/NamingSystem/pharmaceuticaltreatment|1247848&lt;/pre&gt;<br /> |-<br /> | rowspan=&quot;4&quot; | Type<br /> | rowspan=&quot;4&quot; | Search on type of medication building block. <br /> | rowspan=&quot;4&quot; | {{fhir|category}} &lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block DispenseRequest.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block VariableDosingRegimen.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&lt;/pre&gt;<br /> |-<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&lt;/pre&gt;<br /> Retrieves all MedicationDispense resources that represent the building block AdministrationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&lt;/pre&gt;<br /> |-<br /> | MedicationStatement<br /> | Retrieves all MedicationStatement resources that represent the building block MedicationUse2.<br /> &lt;pre&gt;GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&lt;/pre&gt;<br /> |-<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&lt;/pre&gt;<br /> |-<br /> | MedicationCode<br /> | Search on medication code.<br /> | {{fhir|medication.code}}&lt;ref&gt;[https://www.hl7.org/fhir/r4/search.html#chaining Chained search parameter]: searches the medicationReference required in each building block for its {{fhir|.code}}.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and have Carbasalaatcalcium Sandoz 600 30 as medication.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&lt;/pre&gt;<br /> |-<br /> | PeriodOfUse<br /> | 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.<br /> Whenever a search is done on the MedicationAgreement, VariableDosingRegimen or AdministrationAgreement building blocks it is required to also include the latest stopped building blocks of that kind within each pharmaceutical treatment, even if these have a period of use outside the PeriodOfUse that is being searched on.<br /> | {{fhir|period-of-use}}&lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement&lt;ref&gt;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.&lt;/ref&gt;<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and were in effect from 01-01-2010.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;period-of-use=ge2010-01-01&lt;/pre&gt;<br /> |-<br /> | DispensePeriod <br /> | Returns all medication dispenses within the specified time period.<br /> | {{fhir|whenhandedover}}<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense and were handed over within a 2 year period.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;whenhandedover=ge2010-01-01&amp;whenhandedover=le2011-12-31&lt;/pre&gt;<br /> |-<br /> | AdministrationPeriod <br /> | Returns all medication administrations within the specified time period.<br /> | {{fhir|effective-time}}<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2 and where administration happened on a specific day.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;effective-time=eq2022-01-01&lt;/pre&gt;<br /> |-<br /> | -<br /> | The client may request that the server returns resources related to the search results, in order to reduce the overall network delay of repeated retrievals of related resources.<br /> Supporting the include of the Patient and Medication resources referenced by building blocks is required. Others (Organization, Location, PractitionerRole, Practitioner, RelatedPerson, Observation) are optional. However: all resources referenced per literal reference SHALL be resolvable [[FHIR:V1.0_FHIR_IG_R4#Including_referenced_resources|per the Nictiz IG]].<br /> | {{fhir|&lt;nowiki&gt;_include=[type]:patient&lt;/nowiki&gt;}}<br /> {{fhir|&lt;nowiki&gt;_include=[type]:medication&lt;/nowiki&gt;}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that have Carbasalaatcalcium Sandoz 600 30 as medication and includes the Medication resource in the search results.<br /> &lt;pre&gt;GET [base]/MedicationRequest?medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&amp;_include=MedicationRequest:medication&lt;/pre&gt;<br /> |}<br /> <br /> The following custom search parameters are defined for this transaction:<br /> <br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/pharmaceutical-treatment-identifier|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/category|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/period-of-use|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> <br /> ==== Retrieve all medication data ====<br /> To retrieve all known medication data, a client has to execute the following requests to retrieve all known medication data per building block, including referenced Medication resources:<br /> <br /> &lt;pre&gt;<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&amp;_include=MedicationStatement:medication<br /> GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;_include=MedicationStatement:medication<br /> &lt;/pre&gt;<br /> <br /> === Serve (response message) ===<br /> The server returns an HTTP Status code appropriate to the processing outcome and returns a Bundle, with {{fhir|Bundle.type}} = {{term|searchset}}, including the resources matching the search query medication data. The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> &lt;section end=medmij3 /&gt;<br /> == Medication data (Send/Receive) ==<br /> The send medication data transaction is used by the client to send medication data to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.375_20220630000000 Medication data (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.376-2022-06-30T000000.html Sending medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication data}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication data<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because medication data consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below. Because of the informative nature of the transaction, '''no''' [[#Actionable_tag|{{term|actionable}} tags]] shall be present.<br /> <br /> === Receive (response message) ===<br /> The server checks each resource present within the Bundle it receives for the absence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication overview (Retrieve/Serve) ==<br /> The retrieve medication overview transaction is used by the client to retrieve a medication overview from the server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.388_20220630000000 Medication overview (PULL)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.389-2022-06-30T000000.html Retrieving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOR<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Retrieve/serve medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.390-2022-06-30T000000.html Serving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain a patient's medication overview, they issue a retrieve medication overview request message. This message uses an extended operation on the RESTful API to obtain a medication overview from a server. An operation is needed because the server will formulate the content of the response based on its internal business logic. The medication overview can not easily be described by standardized RESTful requests. <br /> <br /> The client executes a {{Simplifier|http://nictiz.nl/fhir/OperationDefinition/Medication-Overview|nictiz.fhir.nl.r4.medicationprocess9|title=medication-overview operation}} with an HTTP GET command conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query.<br /> <br /> &lt;pre&gt;<br /> GET [base]/$medication-overview<br /> &lt;/pre&gt;<br /> <br /> === Serve (response message) ===<br /> 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.<br /> <br /> 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].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication overview (Send/Receive) ==<br /> The send medication overview transaction is used by the client to send a medication overview to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.391_20220630000000 Medication overview (PUSH)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.392-2022-06-30T000000.html Sending medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication overview<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication overview consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> 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.<br /> <br /> 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].<br /> <br /> === Receive (response message) ===<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication prescription (Send/Receive) ==<br /> The send medication prescription transaction is used by the client to send a request to dispense medication (Dutch: verstrekkingsverzoek) or process modifications to a medication agreement (Dutch: medicatieafspraak) to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.141-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.394_20220630000000 Medication prescription (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.395-2022-06-30T000000.html Sending medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescription|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication prescription}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescription-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}) and optionally a DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below<br /> <br /> The mp-MedicationPrescription-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the MedicationAgreement and DispenseRequest building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|order}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Medication_prescription_processing_.28Send.2FReceive.29|‘Send medication prescription processing’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication prescription processing (Send/Receive) ==<br /> The send medication prescription processing transaction is used by the client to send data on the processing of a medication agreement (Dutch: medicatieafspraak) and possibly a dispense request (Dutch: verstrekkingsverzoek), in the form of an administration agreement (Dutch: toedieningsafspraak) and optionally a medication dispense (Dutch: medicatieverstrekking).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.143-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.406_20220630000000 Medication prescription processing (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.407-2022-06-30T000000.html Sending data on processing of medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescriptionProcessing|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication prescription processing}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving data on processing of medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because data on processing a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescriptionProcessing-Bundle profile, which contains at least an AdministrationAgreement building block and optionally a MedicationDispense building block. Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-MedicationPrescriptionProcessing-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the AdministrationAgreement and MedicationDispense building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Proposal dispense request (Send/Receive) ==<br /> The send proposal dispense request transaction is used by the client to inform the server about a new or modified proposal dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.400_20220630000000 Proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.401-2022-06-30T000000.html Sending proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal dispense request consists of a DispenseRequest building block along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalDispenseRequest-Bundle profile, which contains one DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalDispenseRequest-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the DispenseRequest building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_dispense_request_.28Send.2FReceive.29|‘Send reply proposal dispense request’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Reply proposal dispense request (Send/Receive) ==<br /> The send reply proposal dispense request transaction is used by the client to inform the server about a reply on a proposed dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.403_20220630000000 Reply proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.404-2022-06-30T000000.html Sending reply proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive reply proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal dispense request consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalDispenseRequest-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalDispenseRequest profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed dispense request that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalDispenseRequest-Bundle profile).<br /> <br /> The mp-ReplyProposalDispenseRequest profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Proposal medication agreement (Send/Receive) ==<br /> The send proposal medication agreement transaction is used by the client to inform the server about a new or modified proposal medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.397_20220630000000 Proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.398-2022-06-30T000000.html Sending proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal medication agreement consists of a MedicationAgreement building block along with supporting resources, a {{term|transaction}} interaction is used.<br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalMedicationAgreement-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalMedicationAgreement-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the MedicationAgreement building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_medication_agreement_.28Send.2FReceive.29|‘Send reply proposal medication agreement’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Reply proposal medication agreement (Send/Receive) ==<br /> The send reply proposal medication agreement transaction is used by the client to inform the server about a reply on a proposed medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.445_20220630000000 Reply proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.446-2022-06-30T000000.html Sending reply proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive reply proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal medication agreement consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalMedicationAgreement-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalMedicationAgreement profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed medication agreement that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalMedicationAgreement-Bundle profile).<br /> <br /> The mp-ReplyProposalMedicationAgreement profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> =Release notes=<br /> Release notes can be found [[mp:V3.0.0-beta.3_releasenotes|here]].<br /> <br /> =Footnotes=<br /> &lt;references/&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=mp:V3.0.0-rc.2_MedicationProcess9_FHIR&diff=206660 2024-03-06T20:12:07Z

<p>Luud Slagter: /* Patient identification */ Tweaked description w.r.t. patient identification mechanism based on MVALEPIC-83</p> <hr /> <div>__NOINDEX__<br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide Medication Process 9 version {{VersieInfo|mp9|release=V3.0.0}} }}<br /> <br /> __TOC__<br /> <br /> = Introduction =<br /> 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.<br /> <br /> 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.<br /> <br /> This IG first describes the boundaries and relationships in place, after which the implementation is described per transaction.<br /> <br /> = Boundaries and relationships =<br /> == Building blocks and profiles ==<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> Because the way 90 million numbers are exchanged is not compatible with the 2020 publication of zib PharmaceuticalProduct, a fork of the corresponding nl-core profile called 'mp-PharmaceuticalProduct' has been introduced.<br /> <br /> {{NoteBoxNictizR4Package|p1=nictiz.fhir.nl.r4.medicationprocess9|v1={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|p2=nictiz.fhir.nl.r4.nl-core|v2={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> <br /> 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:<br /> * MP9 version 2.0.0 makes use of version 1.0.0 of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package;<br /> * MP9 version 3.0.0-beta.x makes use of version 2.0.0-beta.x of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package.<br /> <br /> === Medication building blocks ===<br /> <br /> As described above, the main medication building blocks have no dependency on any zib2020 counterparts, resulting in so-called ‘mp’ profiles. Moreover, note that the building block VariableDosingRegimen does not have a zib counterpart, hence it makes sense to include it as an mp profile as well.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |}<br /> <br /> === Supporting building blocks ===<br /> <br /> Additionally, the standard uses several supporting building blocks referenced from the main medication building blocks. All supporting building blocks are part of the [[FHIR:V1.0_FHIR_IG_R4#Functional_definitions|‘nl-core’ package]]&lt;ref&gt;Although the nl-core package is still in beta-status, HL7 Netherlands has validated the profiles mentioned and assigned the status 'STU-NL' for use in the MP9 Kickstart, see [[Media:HL7_Nederland_disclaimer_STU-NL.pdf]]&lt;/ref&gt;.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> Note the following:<br /> * Each occurrence of the zib HealthProfessional is normally represented by '''two''' FHIR resources: an instance of nl-core-HealthProfessional-PractitionerRole and an instance of nl-core-HealthProfessional-Practitioner. Sending systems should only fill the reference to the PractitionerRole instance where relevant. Receiving systems can resolve the reference to the Practitioner resource from that PractitionerRole instance.<br /> * The zib HealthcareProvider is mapped to both a Location and Organization profile. Most often, the Location profile acts as the focal resource, because most references to this zib are concerned about the recording of the physical location where the care to patient/client takes place rather than the organizational information. For the latter, the profile on Organization is used which is referenced using the {{fhir|Location.managingOrganization}} element. Sending systems should only fill the reference to the Location instance where relevant. Incidentally, concepts that are only concerned with organizational information can refer to the Organization instance.<br /> <br /> === Transaction specific profiles ===<br /> <br /> For several transactions, additional profiles are provided. For each transaction the profile relevant is explicitly mentioned in the corresponding subsection.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |}<br /> <br /> ====Bundle profiles====<br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == Mappings between profiles and data set ==<br /> 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.<br /> <br /> 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:<br /> * 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)<br /> ** 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.<br /> ** 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.<br /> * If an element in the functional definition is removed<br /> ** and the element had a zib mapping applied (not on an extension), the zib mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> ** and the element had a mapping applied to the previous version of MP9 (not on an extension), that mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> * If an element in the functional definition is removed and the element had a mapping applied on an extension, that extension is removed entirely. In particular no {{term|[DEPRECATED]}} mapping will be visible in the FHIR profile. This is done to ensure no redundant extensions remain in the FHIR profiles.<br /> <br /> Moreover, all mappings to earlier versions of MP9 (i.e. versions before the previous version) are entirely removed.<br /> <br /> Following the procedure outlined above thus results in the following:<br /> * 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.<br /> * All incompatible changes made in the latest version with respect to the previous version are marked.<br /> * Exceptions are extensions that would otherwise only contain deprecated mappings; these are removed fully.<br /> <br /> 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’]].<br /> <br /> 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.<br /> <br /> 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]].<br /> <br /> == Pharmaceutical treatment ==<br /> 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.<br /> <br /> == Patient identification ==<br /> This implementation guide assumes that the client system is able to make a connection to the right server that contains the patient's information. It does not provide information on finding the right server nor does it provide information about security. Moreover, each transaction is performed in the context of a specific patient, whose context might have been established using the authentication mechanisms described in external specifications such as the MedMij ‘Afsprakenstelsel’ or through the usage of search parameters for patient identification. <br /> <br /> Each server is required to perform filtering based on the patient associated with the context for the request or based on the patient identification search parameters, which is a [https://www.hl7.org/fhir/r4/search.html#chaining chained search parameter] for all resource types except Patient, so only the records associated with the authenticated patient are returned.<br /> <br /> When patient identification requires the use of search parameters, the following search parameters SHALL be supported:<br /> * Patient: {{fhir|identifier}}<br /> * MedicationRequest: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationDispense: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationStatement: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationAdministration: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> <br /> An example of a request that retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233:<br /> <br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> <br /> All request examples in this document do not include patient identification mechanisms, partly because we want to to generalize this technical design as much as possible (it being applicable to both MedMij and other use cases), and partly because this would convolute all search request examples. Requesters are assumed to include these if necessary. Since there currently are only use cases in the context of a single patient, the patient identification mechanism is actually implicitly assumed to be present in all search requests.<br /> <br /> == Resource identification ==<br /> 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}}.<br /> <br /> 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 &lt;code&gt;@root&lt;/code&gt; and &lt;code&gt;@extension&lt;/code&gt; (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.<br /> <br /> 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|release=V3.0.0}}}} 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]].<br /> <br /> == Differentiating between transactions ==<br /> All transactions described in this IG use the same medication building blocks in different combinations and settings, making it necessary to differentiate between them. Several mechanisms are used to achieve this. Aside from PUSH/PULL, the type of medication building blocks, supporting resources like List and Communication for specific transactions and fixing the value of specific FHIR elements in applicable profiles, the {{term|actionable}} tag is used. The latter is described more in depth in the following section. Next to that, a summarizing table is provided.<br /> <br /> Note that {{fhir|Resource.meta.profile}}, although present in each building block (see [[FHIR:V1.0_FHIR_IG_R4#Profile_use_and_declaration|the general FHIR IG on ‘Profile use and declaration’]]), SHOULD [https://hl7.org/fhir/r4/resource.html#profile-tags not be used for identification of the building block type] and therefore for differentiating between transactions.<br /> <br /> === Actionable tag ===<br /> To differentiate between sending or serving building blocks that are either of informative nature or of actionable nature, the {{term|actionable}} tag is used. [https://hl7.org/fhir/r4/resource.html#tag Tags] are {{datatype|Coding}} elements present in {{fhir|Resource.meta.tag}} used for workflow management.<br /> <br /> If applicable, the profiles used by a transaction require the use of {{fhir|.meta.tag}} with {{fhir|.system}} = {{term|&lt;nowiki&gt;http://terminology.hl7.org/CodeSystem/common-tags&lt;/nowiki&gt;}} and {{fhir|.code}} = {{term|actionable}} to indicate that the resource is part of a request intended to be acted upon. The absence of this tag indicates that the resource is merely of informative nature.<br /> <br /> It is up to systems to determine how and when the transactions using the {{term|actionable}} tag are handled from a functional perspective. Systems may store the resource including the {{term|actionable}} tag or remove it either upon storing or when the request is acted upon. However, systems SHALL make sure the tag is removed when serving or sending the resource as part of an informative transaction.<br /> <br /> === Summarizing table ===<br /> {| class=&quot;wikitable&quot; <br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | PUSH/PULL<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building blocks<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | {{term|actionable}} tag<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR element value<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Other<br /> |-<br /> | Medication data (Retrieve/Serve)<br /> | PULL<br /> | One or more of all building blocks<br /> | No<br /> |<br /> | <br /> |-<br /> | Medication data (Send/Receive)<br /> | PUSH<br /> | One or more of all building blocks<br /> | No<br /> |<br /> |<br /> |-<br /> | Medication overview (Retrieve/Serve)<br /> | PULL<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication overview (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication prescription (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, DispenseRequest (optional)<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|order}} (for both MedicationAgreement and DispenseRequest building blocks)<br /> | <br /> |-<br /> | Medication prescription processing (Send/Receive)<br /> | PUSH<br /> | AdministrationAgreement, MedicationDispense (optional)<br /> | Yes<br /> | <br /> | <br /> |-<br /> | Proposal dispense request (Send/Receive)<br /> | PUSH<br /> | DispenseRequest<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal dispense request (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to DispenseRequest<br /> |-<br /> | Proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to MedicationAgreement<br /> |}<br /> <br /> = Transactions =<br /> 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’.<br /> &lt;section begin=medmij1 /&gt;<br /> == Medication data (Retrieve/Serve) ==<br /> The retrieve medication data transaction is used by the client to retrieve medication data from a server. The client can retrieve its desired information by searching for specific medication building blocks.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.372_20220630000000 Medication data (PULL)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.373-2022-06-30T000000.html Retrieving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGR<br /> &lt;section end=medmij1 /&gt;<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Retrieve/serve medication data}}<br /> &lt;section begin=medmij2 /&gt;<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.374-2022-06-30T000000.html Serving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain all medication data or specific parts matching various parameters, they issue a retrieve medication data request message. This message uses the HTTP GET method parameterized query against the server's medication FHIR endpoints. These endpoints can be one of the following:<br /> * MedicationRequest<br /> * MedicationDispense<br /> * MedicationStatement<br /> * MedicationAdministration<br /> <br /> The search interaction is performed by an HTTP GET conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query. Multiple request messages may be needed to retrieve all desired information.<br /> <br /> &lt;pre&gt;GET [base]/[type]{?[parameters]}&lt;/pre&gt;<br /> <br /> ==== Search parameters ====<br /> All search parameters listed in the table below SHALL be supported for processing by servers and MAY be supported by clients.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | MP9 search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Description<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Example<br /> &lt;section end=medmij2 /&gt;<br /> |-<br /> | PatientIdentificationNumber<br /> | Search on patient.<br /> | {{fhir|patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;&gt;This search parameter only needs to be supported when patient identification requires the use of search parameters, see [[#Patient_identification|section 2.4]].&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233.<br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> &lt;section begin=medmij3 /&gt;<br /> |-<br /> | Identification<br /> | Search on identifier.<br /> | {{fhir|identifier}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves a MedicationRequest resource with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?identifier=http://example.nl/fhir/NamingSystem/MedicationRequest|999922448&lt;/pre&gt;<br /> |-<br /> | Identification<br /> | Search on the pharmaceutical treatment identifier. <br /> Note: retrieval of all medication resources belonging to one pharmaceutical treatment requires to search on all medication resource types.<br /> | {{fhir|pharmaceutical-treatment-identifier}} &lt;ref name=&quot;custom-searchparameter&quot;&gt;The search parameter consists of a custom FHIR search parameter not represented in the FHIR specification. Note that for {{fhir|MedicationRequest.category}} and {{fhir|MedicationStatement.category}} a core search parameter is available, hence no custom one is needed in those cases.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that are part of a pharmaceutical treatment with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?pharmaceutical-treatment-identifier=http://example.nl/fhir/NamingSystem/pharmaceuticaltreatment|1247848&lt;/pre&gt;<br /> |-<br /> | rowspan=&quot;4&quot; | Type<br /> | rowspan=&quot;4&quot; | Search on type of medication building block. <br /> | rowspan=&quot;4&quot; | {{fhir|category}} &lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block DispenseRequest.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block VariableDosingRegimen.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&lt;/pre&gt;<br /> |-<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&lt;/pre&gt;<br /> Retrieves all MedicationDispense resources that represent the building block AdministrationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&lt;/pre&gt;<br /> |-<br /> | MedicationStatement<br /> | Retrieves all MedicationStatement resources that represent the building block MedicationUse2.<br /> &lt;pre&gt;GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&lt;/pre&gt;<br /> |-<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&lt;/pre&gt;<br /> |-<br /> | MedicationCode<br /> | Search on medication code.<br /> | {{fhir|medication.code}}&lt;ref&gt;[https://www.hl7.org/fhir/r4/search.html#chaining Chained search parameter]: searches the medicationReference required in each building block for its {{fhir|.code}}.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and have Carbasalaatcalcium Sandoz 600 30 as medication.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&lt;/pre&gt;<br /> |-<br /> | PeriodOfUse<br /> | 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.<br /> Whenever a search is done on the MedicationAgreement, VariableDosingRegimen or AdministrationAgreement building blocks it is required to also include the latest stopped building blocks of that kind within each pharmaceutical treatment, even if these have a period of use outside the PeriodOfUse that is being searched on.<br /> | {{fhir|period-of-use}}&lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement&lt;ref&gt;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.&lt;/ref&gt;<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and were in effect from 01-01-2010.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;period-of-use=ge2010-01-01&lt;/pre&gt;<br /> |-<br /> | DispensePeriod <br /> | Returns all medication dispenses within the specified time period.<br /> | {{fhir|whenhandedover}}<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense and were handed over within a 2 year period.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;whenhandedover=ge2010-01-01&amp;whenhandedover=le2011-12-31&lt;/pre&gt;<br /> |-<br /> | AdministrationPeriod <br /> | Returns all medication administrations within the specified time period.<br /> | {{fhir|effective-time}}<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2 and where administration happened on a specific day.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;effective-time=eq2022-01-01&lt;/pre&gt;<br /> |-<br /> | -<br /> | The client may request that the server returns resources related to the search results, in order to reduce the overall network delay of repeated retrievals of related resources.<br /> Supporting the include of the Patient and Medication resources referenced by building blocks is required. Others (Organization, Location, PractitionerRole, Practitioner, RelatedPerson, Observation) are optional. However: all resources referenced per literal reference SHALL be resolvable [[FHIR:V1.0_FHIR_IG_R4#Including_referenced_resources|per the Nictiz IG]].<br /> | {{fhir|&lt;nowiki&gt;_include=[type]:patient&lt;/nowiki&gt;}}<br /> {{fhir|&lt;nowiki&gt;_include=[type]:medication&lt;/nowiki&gt;}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that have Carbasalaatcalcium Sandoz 600 30 as medication and includes the Medication resource in the search results.<br /> &lt;pre&gt;GET [base]/MedicationRequest?medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&amp;_include=MedicationRequest:medication&lt;/pre&gt;<br /> |}<br /> <br /> The following custom search parameters are defined for this transaction:<br /> <br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/pharmaceutical-treatment-identifier|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/category|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/period-of-use|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> <br /> ==== Retrieve all medication data ====<br /> To retrieve all known medication data, a client has to execute the following requests to retrieve all known medication data per building block, including referenced Medication resources:<br /> <br /> &lt;pre&gt;<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&amp;_include=MedicationStatement:medication<br /> GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;_include=MedicationStatement:medication<br /> &lt;/pre&gt;<br /> <br /> === Serve (response message) ===<br /> The server returns an HTTP Status code appropriate to the processing outcome and returns a Bundle, with {{fhir|Bundle.type}} = {{term|searchset}}, including the resources matching the search query medication data. The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> &lt;section end=medmij3 /&gt;<br /> == Medication data (Send/Receive) ==<br /> The send medication data transaction is used by the client to send medication data to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.375_20220630000000 Medication data (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.376-2022-06-30T000000.html Sending medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication data}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication data<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because medication data consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below. Because of the informative nature of the transaction, '''no''' [[#Actionable_tag|{{term|actionable}} tags]] shall be present.<br /> <br /> === Receive (response message) ===<br /> The server checks each resource present within the Bundle it receives for the absence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication overview (Retrieve/Serve) ==<br /> The retrieve medication overview transaction is used by the client to retrieve a medication overview from the server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.388_20220630000000 Medication overview (PULL)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.389-2022-06-30T000000.html Retrieving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOR<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Retrieve/serve medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.390-2022-06-30T000000.html Serving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain a patient's medication overview, they issue a retrieve medication overview request message. This message uses an extended operation on the RESTful API to obtain a medication overview from a server. An operation is needed because the server will formulate the content of the response based on its internal business logic. The medication overview can not easily be described by standardized RESTful requests. <br /> <br /> The client executes a {{Simplifier|http://nictiz.nl/fhir/OperationDefinition/Medication-Overview|nictiz.fhir.nl.r4.medicationprocess9|title=medication-overview operation}} with an HTTP GET command conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query.<br /> <br /> &lt;pre&gt;<br /> GET [base]/$medication-overview<br /> &lt;/pre&gt;<br /> <br /> === Serve (response message) ===<br /> 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.<br /> <br /> 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].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication overview (Send/Receive) ==<br /> The send medication overview transaction is used by the client to send a medication overview to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.391_20220630000000 Medication overview (PUSH)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.392-2022-06-30T000000.html Sending medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication overview<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication overview consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> 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.<br /> <br /> 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].<br /> <br /> === Receive (response message) ===<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication prescription (Send/Receive) ==<br /> The send medication prescription transaction is used by the client to send a request to dispense medication (Dutch: verstrekkingsverzoek) or process modifications to a medication agreement (Dutch: medicatieafspraak) to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.141-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.394_20220630000000 Medication prescription (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.395-2022-06-30T000000.html Sending medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescription|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication prescription}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescription-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}) and optionally a DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below<br /> <br /> The mp-MedicationPrescription-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the MedicationAgreement and DispenseRequest building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|order}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Medication_prescription_processing_.28Send.2FReceive.29|‘Send medication prescription processing’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication prescription processing (Send/Receive) ==<br /> The send medication prescription processing transaction is used by the client to send data on the processing of a medication agreement (Dutch: medicatieafspraak) and possibly a dispense request (Dutch: verstrekkingsverzoek), in the form of an administration agreement (Dutch: toedieningsafspraak) and optionally a medication dispense (Dutch: medicatieverstrekking).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.143-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.406_20220630000000 Medication prescription processing (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.407-2022-06-30T000000.html Sending data on processing of medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescriptionProcessing|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication prescription processing}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving data on processing of medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because data on processing a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescriptionProcessing-Bundle profile, which contains at least an AdministrationAgreement building block and optionally a MedicationDispense building block. Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-MedicationPrescriptionProcessing-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the AdministrationAgreement and MedicationDispense building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Proposal dispense request (Send/Receive) ==<br /> The send proposal dispense request transaction is used by the client to inform the server about a new or modified proposal dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.400_20220630000000 Proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.401-2022-06-30T000000.html Sending proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal dispense request consists of a DispenseRequest building block along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalDispenseRequest-Bundle profile, which contains one DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalDispenseRequest-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the DispenseRequest building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_dispense_request_.28Send.2FReceive.29|‘Send reply proposal dispense request’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Reply proposal dispense request (Send/Receive) ==<br /> The send reply proposal dispense request transaction is used by the client to inform the server about a reply on a proposed dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.403_20220630000000 Reply proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.404-2022-06-30T000000.html Sending reply proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive reply proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal dispense request consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalDispenseRequest-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalDispenseRequest profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed dispense request that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalDispenseRequest-Bundle profile).<br /> <br /> The mp-ReplyProposalDispenseRequest profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Proposal medication agreement (Send/Receive) ==<br /> The send proposal medication agreement transaction is used by the client to inform the server about a new or modified proposal medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.397_20220630000000 Proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.398-2022-06-30T000000.html Sending proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal medication agreement consists of a MedicationAgreement building block along with supporting resources, a {{term|transaction}} interaction is used.<br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalMedicationAgreement-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalMedicationAgreement-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the MedicationAgreement building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_medication_agreement_.28Send.2FReceive.29|‘Send reply proposal medication agreement’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Reply proposal medication agreement (Send/Receive) ==<br /> The send reply proposal medication agreement transaction is used by the client to inform the server about a reply on a proposed medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.445_20220630000000 Reply proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.446-2022-06-30T000000.html Sending reply proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive reply proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal medication agreement consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalMedicationAgreement-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalMedicationAgreement profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed medication agreement that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalMedicationAgreement-Bundle profile).<br /> <br /> The mp-ReplyProposalMedicationAgreement profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> =Release notes=<br /> Release notes can be found [[mp:V3.0.0-beta.3_releasenotes|here]].<br /> <br /> =Footnotes=<br /> &lt;references/&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=mp:V3.0.0-rc.2_MedicationProcess9_FHIR&diff=206659 2024-03-06T20:06:22Z

<p>Luud Slagter: /* Mappings between profiles and data set */ Add clarification w.r.t. deprecated mappings on extensions</p> <hr /> <div>__NOINDEX__<br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide Medication Process 9 version {{VersieInfo|mp9|release=V3.0.0}} }}<br /> <br /> __TOC__<br /> <br /> = Introduction =<br /> 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.<br /> <br /> 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.<br /> <br /> This IG first describes the boundaries and relationships in place, after which the implementation is described per transaction.<br /> <br /> = Boundaries and relationships =<br /> == Building blocks and profiles ==<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> Because the way 90 million numbers are exchanged is not compatible with the 2020 publication of zib PharmaceuticalProduct, a fork of the corresponding nl-core profile called 'mp-PharmaceuticalProduct' has been introduced.<br /> <br /> {{NoteBoxNictizR4Package|p1=nictiz.fhir.nl.r4.medicationprocess9|v1={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|p2=nictiz.fhir.nl.r4.nl-core|v2={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> <br /> 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:<br /> * MP9 version 2.0.0 makes use of version 1.0.0 of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package;<br /> * MP9 version 3.0.0-beta.x makes use of version 2.0.0-beta.x of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package.<br /> <br /> === Medication building blocks ===<br /> <br /> As described above, the main medication building blocks have no dependency on any zib2020 counterparts, resulting in so-called ‘mp’ profiles. Moreover, note that the building block VariableDosingRegimen does not have a zib counterpart, hence it makes sense to include it as an mp profile as well.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |}<br /> <br /> === Supporting building blocks ===<br /> <br /> Additionally, the standard uses several supporting building blocks referenced from the main medication building blocks. All supporting building blocks are part of the [[FHIR:V1.0_FHIR_IG_R4#Functional_definitions|‘nl-core’ package]]&lt;ref&gt;Although the nl-core package is still in beta-status, HL7 Netherlands has validated the profiles mentioned and assigned the status 'STU-NL' for use in the MP9 Kickstart, see [[Media:HL7_Nederland_disclaimer_STU-NL.pdf]]&lt;/ref&gt;.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> Note the following:<br /> * Each occurrence of the zib HealthProfessional is normally represented by '''two''' FHIR resources: an instance of nl-core-HealthProfessional-PractitionerRole and an instance of nl-core-HealthProfessional-Practitioner. Sending systems should only fill the reference to the PractitionerRole instance where relevant. Receiving systems can resolve the reference to the Practitioner resource from that PractitionerRole instance.<br /> * The zib HealthcareProvider is mapped to both a Location and Organization profile. Most often, the Location profile acts as the focal resource, because most references to this zib are concerned about the recording of the physical location where the care to patient/client takes place rather than the organizational information. For the latter, the profile on Organization is used which is referenced using the {{fhir|Location.managingOrganization}} element. Sending systems should only fill the reference to the Location instance where relevant. Incidentally, concepts that are only concerned with organizational information can refer to the Organization instance.<br /> <br /> === Transaction specific profiles ===<br /> <br /> For several transactions, additional profiles are provided. For each transaction the profile relevant is explicitly mentioned in the corresponding subsection.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |}<br /> <br /> ====Bundle profiles====<br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == Mappings between profiles and data set ==<br /> 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.<br /> <br /> 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:<br /> * 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)<br /> ** 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.<br /> ** 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.<br /> * If an element in the functional definition is removed<br /> ** and the element had a zib mapping applied (not on an extension), the zib mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> ** and the element had a mapping applied to the previous version of MP9 (not on an extension), that mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> * If an element in the functional definition is removed and the element had a mapping applied on an extension, that extension is removed entirely. In particular no {{term|[DEPRECATED]}} mapping will be visible in the FHIR profile. This is done to ensure no redundant extensions remain in the FHIR profiles.<br /> <br /> Moreover, all mappings to earlier versions of MP9 (i.e. versions before the previous version) are entirely removed.<br /> <br /> Following the procedure outlined above thus results in the following:<br /> * 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.<br /> * All incompatible changes made in the latest version with respect to the previous version are marked.<br /> * Exceptions are extensions that would otherwise only contain deprecated mappings; these are removed fully.<br /> <br /> 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’]].<br /> <br /> 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.<br /> <br /> 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]].<br /> <br /> == Pharmaceutical treatment ==<br /> 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.<br /> <br /> == Patient identification ==<br /> This implementation guide assumes that the client system is able to make a connection to the right server that contains the patient's information. It does not provide information on finding the right server nor does it provide information about security. Moreover, each transaction is performed in the context of a specific patient, whose context might have been established using the authentication mechanisms described in external specifications such as the MedMij ‘Afsprakenstelsel’ or through the usage of search parameters for patient identification. <br /> <br /> Each server is required to perform filtering based on the patient associated with the context for the request or based on the patient identification search parameters, which is a [https://www.hl7.org/fhir/r4/search.html#chaining chained search parameter] for all resource types except Patient, so only the records associated with the authenticated patient are returned.<br /> <br /> When patient identification requires the use of search parameters, the following search parameters SHALL be supported:<br /> * Patient: {{fhir|identifier}}<br /> * MedicationRequest: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationDispense: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationStatement: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationAdministration: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> <br /> An example of a request that retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233:<br /> <br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> <br /> All request examples in this document do not include patient identification mechanisms. Requesters are assumed to include these if necessary.<br /> <br /> == Resource identification ==<br /> 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}}.<br /> <br /> 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 &lt;code&gt;@root&lt;/code&gt; and &lt;code&gt;@extension&lt;/code&gt; (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.<br /> <br /> 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|release=V3.0.0}}}} 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]].<br /> <br /> == Differentiating between transactions ==<br /> All transactions described in this IG use the same medication building blocks in different combinations and settings, making it necessary to differentiate between them. Several mechanisms are used to achieve this. Aside from PUSH/PULL, the type of medication building blocks, supporting resources like List and Communication for specific transactions and fixing the value of specific FHIR elements in applicable profiles, the {{term|actionable}} tag is used. The latter is described more in depth in the following section. Next to that, a summarizing table is provided.<br /> <br /> Note that {{fhir|Resource.meta.profile}}, although present in each building block (see [[FHIR:V1.0_FHIR_IG_R4#Profile_use_and_declaration|the general FHIR IG on ‘Profile use and declaration’]]), SHOULD [https://hl7.org/fhir/r4/resource.html#profile-tags not be used for identification of the building block type] and therefore for differentiating between transactions.<br /> <br /> === Actionable tag ===<br /> To differentiate between sending or serving building blocks that are either of informative nature or of actionable nature, the {{term|actionable}} tag is used. [https://hl7.org/fhir/r4/resource.html#tag Tags] are {{datatype|Coding}} elements present in {{fhir|Resource.meta.tag}} used for workflow management.<br /> <br /> If applicable, the profiles used by a transaction require the use of {{fhir|.meta.tag}} with {{fhir|.system}} = {{term|&lt;nowiki&gt;http://terminology.hl7.org/CodeSystem/common-tags&lt;/nowiki&gt;}} and {{fhir|.code}} = {{term|actionable}} to indicate that the resource is part of a request intended to be acted upon. The absence of this tag indicates that the resource is merely of informative nature.<br /> <br /> It is up to systems to determine how and when the transactions using the {{term|actionable}} tag are handled from a functional perspective. Systems may store the resource including the {{term|actionable}} tag or remove it either upon storing or when the request is acted upon. However, systems SHALL make sure the tag is removed when serving or sending the resource as part of an informative transaction.<br /> <br /> === Summarizing table ===<br /> {| class=&quot;wikitable&quot; <br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | PUSH/PULL<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building blocks<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | {{term|actionable}} tag<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR element value<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Other<br /> |-<br /> | Medication data (Retrieve/Serve)<br /> | PULL<br /> | One or more of all building blocks<br /> | No<br /> |<br /> | <br /> |-<br /> | Medication data (Send/Receive)<br /> | PUSH<br /> | One or more of all building blocks<br /> | No<br /> |<br /> |<br /> |-<br /> | Medication overview (Retrieve/Serve)<br /> | PULL<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication overview (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication prescription (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, DispenseRequest (optional)<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|order}} (for both MedicationAgreement and DispenseRequest building blocks)<br /> | <br /> |-<br /> | Medication prescription processing (Send/Receive)<br /> | PUSH<br /> | AdministrationAgreement, MedicationDispense (optional)<br /> | Yes<br /> | <br /> | <br /> |-<br /> | Proposal dispense request (Send/Receive)<br /> | PUSH<br /> | DispenseRequest<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal dispense request (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to DispenseRequest<br /> |-<br /> | Proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to MedicationAgreement<br /> |}<br /> <br /> = Transactions =<br /> 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’.<br /> &lt;section begin=medmij1 /&gt;<br /> == Medication data (Retrieve/Serve) ==<br /> The retrieve medication data transaction is used by the client to retrieve medication data from a server. The client can retrieve its desired information by searching for specific medication building blocks.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.372_20220630000000 Medication data (PULL)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.373-2022-06-30T000000.html Retrieving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGR<br /> &lt;section end=medmij1 /&gt;<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Retrieve/serve medication data}}<br /> &lt;section begin=medmij2 /&gt;<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.374-2022-06-30T000000.html Serving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain all medication data or specific parts matching various parameters, they issue a retrieve medication data request message. This message uses the HTTP GET method parameterized query against the server's medication FHIR endpoints. These endpoints can be one of the following:<br /> * MedicationRequest<br /> * MedicationDispense<br /> * MedicationStatement<br /> * MedicationAdministration<br /> <br /> The search interaction is performed by an HTTP GET conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query. Multiple request messages may be needed to retrieve all desired information.<br /> <br /> &lt;pre&gt;GET [base]/[type]{?[parameters]}&lt;/pre&gt;<br /> <br /> ==== Search parameters ====<br /> All search parameters listed in the table below SHALL be supported for processing by servers and MAY be supported by clients.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | MP9 search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Description<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Example<br /> &lt;section end=medmij2 /&gt;<br /> |-<br /> | PatientIdentificationNumber<br /> | Search on patient.<br /> | {{fhir|patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;&gt;This search parameter only needs to be supported when patient identification requires the use of search parameters, see [[#Patient_identification|section 2.4]].&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233.<br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> &lt;section begin=medmij3 /&gt;<br /> |-<br /> | Identification<br /> | Search on identifier.<br /> | {{fhir|identifier}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves a MedicationRequest resource with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?identifier=http://example.nl/fhir/NamingSystem/MedicationRequest|999922448&lt;/pre&gt;<br /> |-<br /> | Identification<br /> | Search on the pharmaceutical treatment identifier. <br /> Note: retrieval of all medication resources belonging to one pharmaceutical treatment requires to search on all medication resource types.<br /> | {{fhir|pharmaceutical-treatment-identifier}} &lt;ref name=&quot;custom-searchparameter&quot;&gt;The search parameter consists of a custom FHIR search parameter not represented in the FHIR specification. Note that for {{fhir|MedicationRequest.category}} and {{fhir|MedicationStatement.category}} a core search parameter is available, hence no custom one is needed in those cases.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that are part of a pharmaceutical treatment with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?pharmaceutical-treatment-identifier=http://example.nl/fhir/NamingSystem/pharmaceuticaltreatment|1247848&lt;/pre&gt;<br /> |-<br /> | rowspan=&quot;4&quot; | Type<br /> | rowspan=&quot;4&quot; | Search on type of medication building block. <br /> | rowspan=&quot;4&quot; | {{fhir|category}} &lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block DispenseRequest.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block VariableDosingRegimen.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&lt;/pre&gt;<br /> |-<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&lt;/pre&gt;<br /> Retrieves all MedicationDispense resources that represent the building block AdministrationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&lt;/pre&gt;<br /> |-<br /> | MedicationStatement<br /> | Retrieves all MedicationStatement resources that represent the building block MedicationUse2.<br /> &lt;pre&gt;GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&lt;/pre&gt;<br /> |-<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&lt;/pre&gt;<br /> |-<br /> | MedicationCode<br /> | Search on medication code.<br /> | {{fhir|medication.code}}&lt;ref&gt;[https://www.hl7.org/fhir/r4/search.html#chaining Chained search parameter]: searches the medicationReference required in each building block for its {{fhir|.code}}.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and have Carbasalaatcalcium Sandoz 600 30 as medication.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&lt;/pre&gt;<br /> |-<br /> | PeriodOfUse<br /> | 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.<br /> Whenever a search is done on the MedicationAgreement, VariableDosingRegimen or AdministrationAgreement building blocks it is required to also include the latest stopped building blocks of that kind within each pharmaceutical treatment, even if these have a period of use outside the PeriodOfUse that is being searched on.<br /> | {{fhir|period-of-use}}&lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement&lt;ref&gt;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.&lt;/ref&gt;<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and were in effect from 01-01-2010.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;period-of-use=ge2010-01-01&lt;/pre&gt;<br /> |-<br /> | DispensePeriod <br /> | Returns all medication dispenses within the specified time period.<br /> | {{fhir|whenhandedover}}<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense and were handed over within a 2 year period.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;whenhandedover=ge2010-01-01&amp;whenhandedover=le2011-12-31&lt;/pre&gt;<br /> |-<br /> | AdministrationPeriod <br /> | Returns all medication administrations within the specified time period.<br /> | {{fhir|effective-time}}<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2 and where administration happened on a specific day.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;effective-time=eq2022-01-01&lt;/pre&gt;<br /> |-<br /> | -<br /> | The client may request that the server returns resources related to the search results, in order to reduce the overall network delay of repeated retrievals of related resources.<br /> Supporting the include of the Patient and Medication resources referenced by building blocks is required. Others (Organization, Location, PractitionerRole, Practitioner, RelatedPerson, Observation) are optional. However: all resources referenced per literal reference SHALL be resolvable [[FHIR:V1.0_FHIR_IG_R4#Including_referenced_resources|per the Nictiz IG]].<br /> | {{fhir|&lt;nowiki&gt;_include=[type]:patient&lt;/nowiki&gt;}}<br /> {{fhir|&lt;nowiki&gt;_include=[type]:medication&lt;/nowiki&gt;}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that have Carbasalaatcalcium Sandoz 600 30 as medication and includes the Medication resource in the search results.<br /> &lt;pre&gt;GET [base]/MedicationRequest?medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&amp;_include=MedicationRequest:medication&lt;/pre&gt;<br /> |}<br /> <br /> The following custom search parameters are defined for this transaction:<br /> <br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/pharmaceutical-treatment-identifier|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/category|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/period-of-use|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> <br /> ==== Retrieve all medication data ====<br /> To retrieve all known medication data, a client has to execute the following requests to retrieve all known medication data per building block, including referenced Medication resources:<br /> <br /> &lt;pre&gt;<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&amp;_include=MedicationStatement:medication<br /> GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;_include=MedicationStatement:medication<br /> &lt;/pre&gt;<br /> <br /> === Serve (response message) ===<br /> The server returns an HTTP Status code appropriate to the processing outcome and returns a Bundle, with {{fhir|Bundle.type}} = {{term|searchset}}, including the resources matching the search query medication data. The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> &lt;section end=medmij3 /&gt;<br /> == Medication data (Send/Receive) ==<br /> The send medication data transaction is used by the client to send medication data to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.375_20220630000000 Medication data (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.376-2022-06-30T000000.html Sending medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication data}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication data<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because medication data consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below. Because of the informative nature of the transaction, '''no''' [[#Actionable_tag|{{term|actionable}} tags]] shall be present.<br /> <br /> === Receive (response message) ===<br /> The server checks each resource present within the Bundle it receives for the absence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication overview (Retrieve/Serve) ==<br /> The retrieve medication overview transaction is used by the client to retrieve a medication overview from the server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.388_20220630000000 Medication overview (PULL)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.389-2022-06-30T000000.html Retrieving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOR<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Retrieve/serve medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.390-2022-06-30T000000.html Serving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain a patient's medication overview, they issue a retrieve medication overview request message. This message uses an extended operation on the RESTful API to obtain a medication overview from a server. An operation is needed because the server will formulate the content of the response based on its internal business logic. The medication overview can not easily be described by standardized RESTful requests. <br /> <br /> The client executes a {{Simplifier|http://nictiz.nl/fhir/OperationDefinition/Medication-Overview|nictiz.fhir.nl.r4.medicationprocess9|title=medication-overview operation}} with an HTTP GET command conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query.<br /> <br /> &lt;pre&gt;<br /> GET [base]/$medication-overview<br /> &lt;/pre&gt;<br /> <br /> === Serve (response message) ===<br /> 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.<br /> <br /> 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].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication overview (Send/Receive) ==<br /> The send medication overview transaction is used by the client to send a medication overview to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.391_20220630000000 Medication overview (PUSH)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.392-2022-06-30T000000.html Sending medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication overview<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication overview consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> 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.<br /> <br /> 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].<br /> <br /> === Receive (response message) ===<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication prescription (Send/Receive) ==<br /> The send medication prescription transaction is used by the client to send a request to dispense medication (Dutch: verstrekkingsverzoek) or process modifications to a medication agreement (Dutch: medicatieafspraak) to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.141-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.394_20220630000000 Medication prescription (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.395-2022-06-30T000000.html Sending medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescription|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication prescription}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescription-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}) and optionally a DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below<br /> <br /> The mp-MedicationPrescription-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the MedicationAgreement and DispenseRequest building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|order}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Medication_prescription_processing_.28Send.2FReceive.29|‘Send medication prescription processing’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication prescription processing (Send/Receive) ==<br /> The send medication prescription processing transaction is used by the client to send data on the processing of a medication agreement (Dutch: medicatieafspraak) and possibly a dispense request (Dutch: verstrekkingsverzoek), in the form of an administration agreement (Dutch: toedieningsafspraak) and optionally a medication dispense (Dutch: medicatieverstrekking).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.143-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.406_20220630000000 Medication prescription processing (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.407-2022-06-30T000000.html Sending data on processing of medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescriptionProcessing|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication prescription processing}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving data on processing of medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because data on processing a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescriptionProcessing-Bundle profile, which contains at least an AdministrationAgreement building block and optionally a MedicationDispense building block. Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-MedicationPrescriptionProcessing-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the AdministrationAgreement and MedicationDispense building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Proposal dispense request (Send/Receive) ==<br /> The send proposal dispense request transaction is used by the client to inform the server about a new or modified proposal dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.400_20220630000000 Proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.401-2022-06-30T000000.html Sending proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal dispense request consists of a DispenseRequest building block along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalDispenseRequest-Bundle profile, which contains one DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalDispenseRequest-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the DispenseRequest building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_dispense_request_.28Send.2FReceive.29|‘Send reply proposal dispense request’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Reply proposal dispense request (Send/Receive) ==<br /> The send reply proposal dispense request transaction is used by the client to inform the server about a reply on a proposed dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.403_20220630000000 Reply proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.404-2022-06-30T000000.html Sending reply proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive reply proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal dispense request consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalDispenseRequest-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalDispenseRequest profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed dispense request that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalDispenseRequest-Bundle profile).<br /> <br /> The mp-ReplyProposalDispenseRequest profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Proposal medication agreement (Send/Receive) ==<br /> The send proposal medication agreement transaction is used by the client to inform the server about a new or modified proposal medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.397_20220630000000 Proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.398-2022-06-30T000000.html Sending proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal medication agreement consists of a MedicationAgreement building block along with supporting resources, a {{term|transaction}} interaction is used.<br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalMedicationAgreement-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalMedicationAgreement-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the MedicationAgreement building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_medication_agreement_.28Send.2FReceive.29|‘Send reply proposal medication agreement’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Reply proposal medication agreement (Send/Receive) ==<br /> The send reply proposal medication agreement transaction is used by the client to inform the server about a reply on a proposed medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.445_20220630000000 Reply proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.446-2022-06-30T000000.html Sending reply proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive reply proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal medication agreement consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalMedicationAgreement-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalMedicationAgreement profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed medication agreement that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalMedicationAgreement-Bundle profile).<br /> <br /> The mp-ReplyProposalMedicationAgreement profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> =Release notes=<br /> Release notes can be found [[mp:V3.0.0-beta.3_releasenotes|here]].<br /> <br /> =Footnotes=<br /> &lt;references/&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=mp:Medicatieoverdracht_Kickstart&diff=206657 2024-03-06T16:35:22Z

<p>Luud Slagter: /* ARCHIEF */</p> <hr /> <div>{{DISPLAYTITLE:Kickstart Medicatieoverdracht - Landingspagina documentatie leveranciers (Handboek)}}<br /> <br /> __NUMBEREDHEADINGS__<br /> =ALGEMEEN REFERENTIE=<br /> :*[https://www.zorginzicht.nl/binaries/content/assets/zorginzicht/kwaliteitsinstrumenten/Kwaliteitsstandaard+Overdracht+van+medicatiegegevens+in+de+keten.pdf Kwaliteitsstandaard: richtlijn overdracht van medicatiegegevens in de keten]&lt;br&gt;<br /> <br /> =BOUWDOCUMENTATIE=<br /> {{IssueBox|'''FHIR specs voor versie 3.0.0-beta.3 volgen op 7 maart'''}}<br /> ==Voorbereiding==<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/pva_kickstart/&lt;abbr title=&quot;Het Plan van aanpak versie 3.1 voor de uitvoering van de Kickstart. Het Plan van aanpak versie 3.1 beschrijft het doel, de opzet, aanpak en kaders voor de uitvoering van de Kickstart.&quot;&gt;Plan van aanpak versie 3.1&lt;/abbr&gt;]<br /> <br /> ==Specificaties==<br /> :'''Verzamelbestand informatiestandaarden'''<br /> :*[[mp:V2.0.0_Verwijzing_naar_documentatie_Medicatieproces9_tbv_Kickstart|Verzamelbestand met functionele, technische en infrastructurele documentatie Medicatieproces 9 t.b.v. Kickstart]]<br /> <br /> :'''Voorbereiding'''<br /> :*[[mp:Stap_0_Voorbereiding|Werkzaamheden in stap 0 Voorbereiding]]<br /> <br /> :'''Informatiestandaard Medicatieproces 9.3.0.0-beta.3'''<br /> :*[[mp:V3.0.0-beta_Ontwerp_medicatieproces_9|&lt;abbr title=&quot;Het functioneel ontwerp van de informatiestandaard Medicatieproces 9 Het beschrijft de algemene werking en specifieke praktijksituaties.&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 3.0.0-beta.3 (NL)&lt;/abbr&gt;]] / [[mp:V3.0.0-beta_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 3.0.0-beta.3 (ENG)]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.<br /> &quot;&gt;Medicatieproces 9 versie 3.0.0-beta.3 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> :*[[mp:V3.0.0_MedicationProcess9_FHIR|&lt;abbr title=&quot;FHIR Implementation guide for Medicatieproces 9 versie 3.0.0-beta.2 FHIR in English&quot;&gt;Implementation guide FHIR Medication Process 9 version 3.0.0-beta.2 (ENG) &lt;/abbr&gt;]]<br /> :*[https://simplifier.net/packages/nictiz.fhir.nl.r4.medicationprocess9/2.0.0-beta.1/ FHIR R4 conformance resources for Medication Process 9 (MP9)]<br /> :*[[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|&lt;abbr title=&quot;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.3 voor patiënt usecases&quot;&gt;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.3 voor patiënt usecases&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases &lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.3_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 3.0.0-beta.3&lt;/abbr&gt;]]<br /> :*Gebruikerseisen: [[mp:Besluiten_kernteams|&lt;abbr title=&quot;Deze pagina bevat de besluiten van de kernteams, met (indien van toepassing) de bijbehorende werkproceseisen, gebruikerseisen en -wensen.&quot;&gt;Besluiten kernteams Medicatieproces 9, inclusief gebruikerseisen en -wensen&lt;/abbr&gt;]]<br /> <br /> :'''Informatiestandaard Lab2zorg'''<br /> :*[[mp:LeeswijzerVoorschriftmetnierfunctiewaarde|&lt;abbr title=&quot;De leeswijzer geeft aan welk onderdeel van Lab2zorg binnen de scope van de Kickstart valt en welke documentatie daarop van toepassing is.&quot;&gt;Leeswijzer ten behoeve van het meesturen van de nierfunctiewaarde met het voorschrift&lt;/abbr&gt;]]<br /> :*[[Lab:Vcurrent_Ontwerp_Lab2zorg|&lt;abbr title=&quot;Het functioneel ontwerp van Lab2zorg. In de kickstart wordt het onderdeel lab2zorg gebruikt voor het meesturen van een nierfunctiewaarde met het voorschrift. Deze usecase staat beschreven in paragraaf 2.3 van het functioneel ontwerp lab2zorg.&quot;&gt;Functioneel ontwerp Lab2zorg versie 3.0.0&lt;/abbr&gt;]]<br /> :*[[Lab:Vcurrent_Kwalificatie|&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard uitwisseling laboratoriumgegevens de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties. Voor de kickstart wordt sturen/ontvangen laboratoriumresultaten uit lab2zorg gebruikt.&quot;&gt;Labuitwisseling versie 3.0.0 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]]<br /> :*[[Lab:V3.0.0_FHIR_Lab2zorg|&lt;abbr title=&quot;Technische FHIR specificaties van Lab2zorg in aanvulling op het functioneel ontwerp. Paragraaf 4.3 beschrijft het sturen van laboratoriumresultaten tussen zorgverleners dat in de kickstart gebruikt wordt.&quot;&gt;FHIR Lab2zorg version 3.0.0 (ENG)&lt;/abbr&gt;]]<br /> <br /> :'''Infrastructuur'''<br /> :*[https://decor.nictiz.nl/pub/vzvz/index.php?prefix=mp-vzvz-&lt;abbr title=&quot;&quot;&gt;ART-DECOR Publicatiepagina VZVZ: Medicatieproces op het LSP&lt;/abbr&gt;]<br /> :*[https://zt-medicatieoverdracht.scrollhelp.site/Medicatieoverdracht/Working-version/programma-van-eisen-medicatieoverdracht&lt;abbr title=&quot;De beschikbare Programma van Eisen waaraan de Kickstart deelnemers moeten voldoen. Deze documenten beschrijven de eisen om aan te sluiten op de AORTA-infrastructuur.&quot;&gt;Programma van eisen LSP (bèta)&lt;/abbr&gt;]<br /> :*[https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpublicvzvz.refined.site%2Fspace%2FA8%2F85000200%2FAORTA%2B8.3.0&amp;data=05%7C01%7Ctheunissen%40nictiz.nl%7C52a3bf5378624ff2978e08db8f44c3a3%7C3d542e8da3eb448f998ddd6880dc119c%7C0%7C0%7C638261297740578594%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=6%2FH9yQ0EAHEmGYHgbVoQo995poc34CXlV6UcBP4MSD8%3D&amp;reserved=0&lt;abbr title=&quot;Deze pagina bevat de algemene specificaties van de zorginfrastructuur AORTA v8.3.0.0&quot;&gt;Documentatie AORTA versie 8.3.0.0&lt;/abbr&gt;]<br /> <br /> ==IT-Infrastructuur==<br /> :*[https://decor.nictiz.nl/pub/vzvz/aorta-vzvz-html-20221128T172039/sc-2.16.840.1.113883.2.4.3.111.3.2.3.3-2016-09-20T163842.html Implementatie van de ping-pong toets]<br /> :*[https://decor.nictiz.nl/pub/vzvz/aorta-vzvz-html-20221128T172039/sc-2.16.840.1.113883.2.4.3.111.3.2.3.1-2016-09-20T091642.html Beheren TKID applicatie]<br /> :*[https://public.vzvz.nl/download/attachments/41779447/AORTA_Proces_VWI_Synchronisatie.pdf?api=v2:~:text=Het%20VWI%2Dsynchronisatie%20proces%20biedt,belang%20van%20pati%C3%ABnt%20en%20zorgaanbieder&lt;abbr title=&quot;Dit document beschrijft de procedure die ervoor zorgt dat elke GBZ-beheerder namens de zorgaanbieder kan vaststellen dat elk patiëntgegeven met toestemming van de patiënt op correcte wijze is aangemeld op de VWI.&quot;&gt;Proces VWI synchronisatie&lt;/abbr&gt;]<br /> :*[https://public.vzvz.nl/download/attachments/41779447/AORTA_Sgl_Ontw_Gebeurtenisverwerking.pdf?api=v2&lt;abbr title=&quot;Dit document beschrijft het ontwerp van de gebeurtenisverdeler component (GVE) en de component gebeurtenisafhandelaar (GAF) in de ZIM.&quot;&gt;Ontwerp gebeurtenisverwerking&lt;/abbr&gt;]<br /> :*[https://public.vzvz.nl/download/attachments/41779447/AORTA_Sgl_Ontw_Abonnementenregister.pdf?api=v2&lt;abbr title=&quot;Dit document beschrijft het ontwerp van de abonnementenregister component (ABR) in de ZIM.&quot;&gt;Ontwerp abonnementenregister&lt;/abbr&gt;]<br /> <br /> ==Implementatiehandleidingen==<br /> :*[[mp:Vkickstart_MigratieHybride|&lt;abbr title=&quot;Handleiding Migratie hybride fase Kickstart&quot;&gt;Implementatiehandleiding Migratie/hybride&lt;/abbr&gt;]]<br /> :*[[mp:Implementatiehandleiding_Consolidatie/afleidingsregels|&lt;abbr title=&quot;Handleiding Consolidatie/afleidingsregels Kickstart&quot;&gt;Implementatiehandleiding Consolidatie/afleidingsregels&lt;/abbr&gt;]]<br /> :*[https://www.aorta-lsp.nl/media/downloads/implementatiehandleiding-verwijsindex-aorta-v8200pdf/download&lt;abbr title=&quot;Implementatiehandleiding verwijsindex AORTA v8.2.0.0&quot;&gt;Implementatiehandleiding VWI AORTA&lt;/abbr&gt;]<br /> :*[https://www.vzvz.nl/media/downloads/zorg-ab-implementatiehandleiding-v27pdf/download&lt;abbr title=Dit document bevat informatie, instructies en voorbeelden ten behoeve van de implementatie van<br /> (applicaties/systemen die gebruik maken van) de web API's van ZORG-AB.&gt;Implementatiehandleiding ZORG-AB&lt;/abbr&gt;]<br /> :*[https://www.aorta-lsp.nl/media/downloads/implementatiehandleiding-inschrijftoken-aorta-v8200pdf/download&lt;abbr title=&quot;Handleiding voor de implementatie van het koppelvlak tussen het goed beheerde Zorgsystemen (GBZ) en het landelijk schakelpunt (LSP).&quot;&gt;Implementatie handleiding inschrijftoken&lt;/abbr&gt;]<br /> :*[https://www.aorta-lsp.nl/media/downloads/implementatiehandleiding-mandaattoken-aorta-v8200pdf/download&lt;abbr title=&quot;Specificatie van het mandaattoken.&quot;&gt;Implementatie handleiding mandaattoken&lt;/abbr&gt;]<br /> :*[https://www.aorta-lsp.nl/media/downloads/implementatiehandleiding-berichtauthenticatie-transactietoken-aorta-v8200pdf/download&lt;abbr title=&quot;Handleiding voor het uitrusten van de berichten met het SAML transactietoken.&quot;&gt;Implementatie handleiding transactiekosten&lt;/abbr&gt;]<br /> <br /> ==Ondersteunende materialen==<br /> :*[[mp:V3.0_Voorbeelden_doseringen|&lt;abbr title=&quot;Uitgewerkte voorbeelden voor het concept 'Gebruiksinstructie' uit de dataset van de Informatiestandaard Medicatieproces 9&quot;&gt;Voorbeelden doseringen&lt;/abbr&gt;]]<br /> :*[[mp:V9_2.0.0_HL7v3CDA_FHIRTiming|&lt;abbr title=&quot;Toedieningsschema HL7v3-template. Introductie van het FHIR timing datatype in CDA substanceAdministration.effectiveTime voor toedieningsschema's. Voorheen was dit de HL7v3 GTS (General Timing Specification). Bevat ook de inhoudelijke wijziging in de XML schema's (xsd's).&quot;&gt;Dosering in FHIR&lt;/abbr&gt;]]<br /> :*[https://github.com/Nictiz/Medicatieviewer&lt;abbr title=&quot;De Medicatieviewer transformeert een MP-9 XML volgens de standaard medicatieproces 9 voor medicatiegegevens of voor medicatieoverzicht in HTML om zo een voor mensen leesbaar overzicht te geven van de inhoud van de XML.&quot;&gt;Medicatieviewer&lt;/abbr&gt;]<br /> :*[https://informatiestandaarden.nictiz.nl/images/c/c9/Medicatieoverzicht_MP90.zip&lt;abbr title=&quot;Uitklapbaar Medicatieoverzicht voorbeeld in HTML-formaat.&quot;&gt;Medicatieoverzicht HTML voorbeeld&lt;/abbr&gt;]<br /> :*[[Mappingarchitectuur#Mappings_en_transacties|&lt;abbr title=&quot;Deze sectie toont verschillende mappings voor transacties uit verschillende informatiestandaarden.&quot;&gt;Mappingarchitectuur&lt;/abbr&gt;]]<br /> :*[[mp:Vdraft_RaadplegenReconcilieren|&lt;abbr title=&quot;Deze pagina bevat nadere toelichting over hoe te reconciliëren na raadplegen. Het bespreekt de volgorde van verwerken van de verschillende soorten binnengekomen informatie.&quot;&gt;Implementatie handleiding Raadplegen Reconciliëren&lt;/abbr&gt;]]<br /> :*[[7phcy:V09_HL7v3-domeinspecificatie_Pharmacy|&lt;abbr title=&quot;Deze pagina geeft nadere toelichting bij templates in ART-DECOR.&quot;&gt;Toelichting bericht templates Medicatieproces versie 9&lt;/abbr&gt;]]<br /> :*[https://www.aorta-lsp.nl/media/downloads/best-practices-vwi-synchronisatie-aorta-v8200pdf/download/&lt;abbr title=&quot;Ter verduidelijking van de implementatiehandleiding VWI. Extra informatie wordt gegeven over de afhandeling van berichten aan de XIS leveranciers en de beheerders om duidelijkheid te geven over de verwachte acties.&quot;&gt;Best practices: VWI synchronisatie &lt;/abbr&gt;]<br /> :*[https://www.aorta-lsp.nl/media/downloads/factsheet-tkidspdf/download/&lt;abbr title=&quot;Deze factsheet beschrijft de werking van TypeKwalificatie-ID’s (TKID’s) op het LSP.&quot;&gt;Factsheet tkid&lt;/abbr&gt;]<br /> :*[https://www.vzvz.nl/diensten/gemeenschappelijke-diensten/zorg-ab&lt;abbr title=&quot;Deze pagina bevat de algemene informatie omtrent Zorg-AG.&quot;&gt;Algemene informatie Zorg-AB&lt;/abbr&gt;]<br /> :*[https://www.vzvz.nl/diensten/gemeenschappelijke-diensten/zorg-id&lt;abbr title=&quot;Deze pagina bevat de algemene informatie omtrent Zorg-ID.&quot;&gt;Algemene informatie Zorg-ID&lt;/abbr&gt;]<br /> <br /> =TEST- EN VALIDATIEMATERIAAL=<br /> ==Testinformatie Kickstart==<br /> :*[[mp:Testen_Kickstart|Testen Kickstart]]<br /> <br /> ==Testscripts==<br /> {{IssueBox|'''De aanpassingen op de testscripts door de release van versie 3.0.0-beta.3 worden op dit moment doorgevoerd'''}}<br /> :'''Medicatieproces 9'''<br /> :*[[mp:Vcurrent_Kwalificatie#Medicatieproces_9_versie_3.0.0-beta.2_testmateriaal_en_kwalificatiescripts_voor_Kickstart|Testscripts Medicatieproces 9 versie 3.0.0-beta.2]]<br /> <br /> :'''Testscript gebruikerseisen boven sectoraal'''<br /> :*[https://informatiestandaarden.nictiz.nl/wiki/Bestand:Use_case_scenario%27s_en_testscripts_GERRIT_-_Pati%C3%ABnt_1tm4_-_stap_3-4_-_beta_versie_3.0_.pdf Use case scenario's en testscripts GERRIT - Patiënt 1tm4 - stap 3-4 - beta versie 3.0&lt;/abbr&gt;]<br /> :*[https://informatiestandaarden.nictiz.nl/wiki/Bestand:Use_case_scenario%27s_en_testscripts_Rijnmond_-_pati%C3%ABnt_1-4_-_stap_3-4_-_beta_versie_3.0_(1).pdf Use case scenario's en testscripts Rijnmond - patiënt 1-4 - stap 3-4 - beta versie 3.0&lt;/abbr&gt;]<br /> <br /> :'''Lab2zorg'''<br /> :*[[Lab:Vcurrent_Kwalificatie#Lab2zorg|&lt;abbr title=&quot;Testgegevens die als voorbereiding op de kwalificatie gebruikt kunnen worden, waarbij voor de kickstart alleen de scripts Laboratoriumresultaten (Sturen/Ontvangen) relevant zijn.&quot;&gt;Testscripts Lab2zorg versie 3.0.0&lt;/abbr&gt;]]<br /> :'''Algemene eisen MP9 &amp; Generieke voorzieningen'''<br /> :*[https://informatiestandaarden.nictiz.nl/images/5/5e/Testscripts_algemene_eisen_MP9_%26_Generieke_voorzieningen.zip Testscripts algemene eisen MP9 &amp; Generieke voorzieningen (zip bestand)]<br /> <br /> ==Validatiescripts==<br /> :*Kwalificatiescripts worden definitief opgeleverd als bekend is op welke versie gevalideerd wordt in de Kickstart.<br /> :*Acceptatiescripts worden gegenereerd op het moment dat de leverancier zich meldt; dit betreft maatwerk.<br /> <br /> =TOOLING=<br /> :*[https://informatiestandaarden.nictiz.nl/images/3/30/Tooling.pdf&lt;abbr title=&quot;Overzicht van de te gebruiken tooling.&quot;&gt;Beschikbare tooling&lt;/abbr&gt;]<br /> <br /> ==ART-DECOR==<br /> :*[https://decor.nictiz.nl/art-decor/home&lt;abbr title=&quot;Inlogpagina ART-DECOR&quot;&gt;Inloggen ART-DECOR&lt;/abbr&gt;]<br /> :*[[HL7v3 kwalificatiesimulator|&lt;abbr title=&quot;Uitleg over inloggen en gebruik van de kwalificatiesimulator (ART-DECOR)&quot;&gt;Testen met ART-DECOR / Kwalificatiesimulator&lt;/abbr&gt;]]<br /> :*[https://art-decor.org/mediawiki/index.php?title=Documentation&lt;abbr title=&quot;Handleidingen en documentatie van ART-DECOR &quot;&gt;ART-DECOR documentatie&lt;/abbr&gt;]<br /> :*[[7phcy:V2.0_Toelichting_samenhang_Wiki_en_ART-DECOR|&lt;abbr title=&quot;Deze toelichting beschrijft de samenhang tussen: de HL7v3-implementatiehandleiding Medicatieproces 9 wiki en de bijbehorende html-publicatie van ART-DECOR.&quot;&gt;Wiki &amp; ART-DECOR&lt;/abbr&gt;]]<br /> <br /> ==BITS==<br /> :*[https://bits.nictiz.nl/ Link naar BITS algemeen]<br /> :*[https://bits.nictiz.nl/projects/MP/issues/ Link naar openstaande issues Medicatieproces in BITS]<br /> :*[https://informatiestandaarden.nictiz.nl/images/8/87/Handleiding_BITS_voor_leveranciers.pdf Handleiding BITS validatieloket]<br /> <br /> ==Touchstone==<br /> :*[https://touchstone.aegis.net/touchstone/login&lt;abbr title=&quot;Inlogpagina Touchstone&quot;&gt;Inloggen Touchstone&lt;/abbr&gt;]<br /> :*[[mp:Vcurrent_Kwalificatie#Touchstone|Testen met Touchstone]]<br /> <br /> ==ZORG-AB==<br /> :*[https://zorg-ab-oas.vzvz.nl/&lt;abbr title=&quot;Testapplicatie Zorg-AB&quot;&gt;ZORG-AB testapplicatie&lt;/abbr&gt;]<br /> :*[https://www.vzvz.nl/diensten/gemeenschappelijke-diensten/zorg-ab&lt;abbr title=&quot;Deze pagina bevat informatie, instructies en voorbeelden ten behoeve van de implementatie van<br /> (applicaties/systemen die gebruik maken van) de web API's van ZORG-AB.&quot;&gt;Implementatie handleiding ZORG-AB&lt;/abbr&gt;]<br /> <br /> =INFORMATIEVOORZIENING=<br /> <br /> ==Vragen en antwoorden==<br /> :*[[mp:Medicatieoverdracht_Kickstart_Vragen|Vragen en antwoorden uit vragenuur op vrijdagen]]<br /> <br /> ==Kennissessie==<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/luistersessie-introductiesessie-medicatieproces/ &lt;abbr title=&quot;In deze kennissessie wordt een introductie gegeven van het programma Medicatieoverdracht, de richtlijn Overdracht van medicatiegegevens in de keten, de informatiestandaard Medicatieproces 9&quot;&gt;Kennissessie: Introductie Medicatieoverdracht&lt;/abbr&gt;]<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/kennissessie-wat-kan-ik-verwachten-van-medicatieoverdracht/ &lt;abbr title=&quot;In deze kennissessie wordt inzicht gegeven in de meerwaarde van het programma Medicatieoverdracht voor de zorgverlener en patiënt en de te nemen acties op procesniveau. Per rol (voorschrijver, apotheker, toediener en patiënt) worden de stappen die worden beproefd in de Kickstart toegelicht.&quot;&gt;Kennissessie: Wat kan ik verwachten van Medicatieoverdracht&lt;/abbr&gt;]<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/kennissessie-verdieping-medicatieoverdracht/ &lt;abbr title=&quot;Deze kennissessie is voor iedereen die meer wil weten over het medicatieproces: welke gegevensuitwisselingsmomenten zijn er (transacties), welke rollen horen daarbij, hoe werken de bouwsteen relaties precies etc.&quot;&gt;Kennissessie: Verdieping Medicatieoverdracht&lt;/abbr&gt;]<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/luistersessie-voorgenomen-besluiten-kernteam-medicatie// &lt;abbr title=&quot;Deze kennissessie geeft een beeld van hoe samen met zorgverleners uit de 10 betrokken sectoren afspraken tot stand zijn gekomen t.a.v. beleid, verantwoordelijkheden, zorgprocessen, eenheid van taal in terminologie en codestelsels om de implementatie van de richtlijn en informatiestandaard te ondersteunen. &quot;&gt;Kennissessie: (Voorgenomen) besluiten kernteam Medicatie&lt;/abbr&gt;]<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/luistersessies/&lt;abbr title=&quot;In deze kennissessie wordt de route van de bèta publicatie van de informatiestandaard Medicatieproces 9 naar de definitieve versie toegelicht. &quot;&gt;Kennissessie: Route Medicatieproces 9 v2.0.0 bèta naar definitief&lt;/abbr&gt;]<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/luistersessie-testmaterialen-medicatieproces-9-2-0-0-beta/ &lt;abbr title=&quot;In deze kennissessie worden de testmaterialen voor Medicatieproces 9 toegelicht. Wat kan er getest worden, wat is de samenhang tussen de materialen, inhoud van het materiaal, hoe te gebruiken en waar te vinden. &quot;&gt;Kennissessie: Testmaterialen Medicatieproces 9 v2.0.0 bèta&lt;/abbr&gt;]<br /> :*[https://informatiestandaarden.nictiz.nl/images/d/d2/202202_Introductie_AORTA_-_nieuwe_style.pdf &lt;abbr title=&quot;Introductiepresentatie AORTA. Een introductie van infrastructurele AORTA architectuur​, verschillende architectuurlagen​, verschillende componenten​.<br /> Relaties met andere stelsels en producten​.&quot;&gt;Presentatie: Introductie AORTA&lt;/abbr&gt;]<br /> <br /> ==PGO==<br /> :*[https://informatiestandaarden.nictiz.nl/images/6/61/PGOsessiesMedicatieproces_BijlageBijOnlineSessie.pdf &lt;abbr title=&quot;Deze kennissessie geeft een introductie van MedMij in relatie tot Medicatieproces 9.&quot;&gt;Presentatie: Medicatieoverdracht uitleg MedMij&lt;/abbr&gt;]<br /> :*[https://informatiestandaarden.nictiz.nl/images/2/29/PGOsessie_OpnameOnline.mp4 &lt;abbr title=&quot;Opname van de kennissessie: Een introductie van MedMij in relatie tot het Medicatieproces 9.&quot;&gt;Opname: Medicatieoverdracht uitleg presentatie MedMij&lt;/abbr&gt;]<br /> <br /> =MEMO'S=<br /> <br /> ==Informatieve memo's==<br /> :*[https://informatiestandaarden.nictiz.nl/images/7/79/MO_memo_MBH-ID_Transformatiedienst_20230315.pdf&lt;abbr title=&quot;Memo MBH-ID Transformatiedienst_20230315&quot;&gt;Memo MBH-ID Transformatiedienst 15-03-2023&lt;/abbr&gt;]<br /> :*[https://informatiestandaarden.nictiz.nl/images/4/48/MO_memo_vooraankondiging_20230307.pdf&lt;abbr title=&quot;Memo vooraankondiging_20230307&quot;&gt;Memo vooraankondiging 07-03-2023&lt;/abbr&gt;]<br /> <br /> =IN ONTWIKKELING=<br /> :'''Transitie naar Medicatieproces 9 (migratie en hybride situatie)'''<br /> :*[[Vdraft_Mappingarchitectuur#Medicatieproces_.28MP.29_Versie_MP9_2.0_en_versie_9.0.7|&lt;font color=&quot;BBB7B6&quot;&gt;Mappingarchitectuur met mappings MP 9.0.7 &lt;-&gt; MP9 2.0.0&lt;/font&gt;]]<br /> <br /> :'''Kickstart testen'''<br /> :*[[mp:Draft_Testtooling#BITS|&lt;font color=&quot;BBB7B6&quot;&gt;Tooling &amp; omgevingen Kickstart Medicatieoverdracht&lt;/font&gt;]]<br /> <br /> =ARCHIEF=<br /> :*[https://informatiestandaarden.nictiz.nl/images/4/42/Nulpunt_documentatie_Kickstart_contract_leveranciers_versie11_20220907.pdf&lt;abbr title=&quot;Document dat nulpunt beschrijft voor specificaties Kickstart ten behoeve van contract.&quot;&gt;Nulpunt documentatie Kickstart leveranciers versie 1.1 van 7 september 2022&lt;/abbr&gt;]<br /> :* Verzamelbestand in Excel met functionele, technische en infrastructurele documentatie Medicatieproces 9 t.b.v. Kickstart (niet meer te downloaden om verwarring te voorkomen)<br /> :*[https://www.aorta-lsp.nl/voor-wie/ict-leveranciers/aorta-documentatie/infrastructuur-aorta-v8200&lt;abbr title=&quot;Deze pagina bevat de algemene specificaties van de zorginfrastructuur AORTA v8.2.0.0&quot;&gt;Documentatie AORTA 8.2.0.0&lt;/abbr&gt;]<br /> <br /> :'''Informatiestandaard Medicatieproces 9.3.0.0-beta.2'''<br /> :*[[mp:V3.0.0-beta.2_Ontwerp_medicatieproces_9|&lt;abbr title=&quot;Het functioneel ontwerp van de informatiestandaard Medicatieproces 9 Het beschrijft de algemene werking en specifieke praktijksituaties.&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 3.0.0-beta.2 (NL)&lt;/abbr&gt;]] / [[mp:V3.0.0-beta.2_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 3.0.0-beta.2 (ENG)]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/index.html&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.&quot;&gt;Medicatieproces 9 versie 3.0.0-beta.2 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> :*[[mp:V3.0.0-beta.2_MedicationProcess9_FHIR|&lt;abbr title=&quot;FHIR Implementation guide for Medicatieproces 9 versie 3.0.0-beta.2 FHIR in English&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 (ENG) &lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|&lt;abbr title=&quot;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.2 voor patiënt usecases&quot;&gt;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.2 voor patiënt usecases&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.2_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases (ENG)&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.2_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 3.0.0-beta.2&lt;/abbr&gt;]]<br /> <br /> :'''Informatiestandaard Medicatieproces 9.3.0.0-beta.1'''<br /> :*[[mp:V3.0.0-beta.1_Ontwerp_medicatieproces_9|Functioneel ontwerp Medicatieproces 9 versie 3.0.0-beta.1 (NL)]] / [[mp:V3.0.0-beta.1_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 3.0.0-beta.1 (ENG)]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20230217T123829/index.html&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.&quot;&gt;Medicatieproces 9 versie 3.0.0-beta.1 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> :*[[mp:V3.0.0-beta.1_MedicationProcess9_FHIR|&lt;abbr title=&quot;FHIR Implementation guide for Medicatieproces 9 versie 3.0.0-beta.1 FHIR in English&quot;&gt;Implementation guide FHIR Medication Process 9 version 3.0.0-beta.1 (ENG)&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.1_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.1 for patient use cases (ENG)&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.1_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 3.0.0-beta.1&lt;/abbr&gt;]]<br /> <br /> :'''Informatiestandaard Medicatieproces 9.2.0.0'''<br /> :*[[mp:V2.0.0_Ontwerp_medicatieproces_9|&lt;abbr title=&quot;Het functioneel ontwerp van de informatiestandaard Medicatieproces 9. Het beschrijft de algemene werking en specifieke praktijksituaties.&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 2.0.0 (NL)&lt;/abbr&gt;]] / [[mp:V2.0.0_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 2.0.0 (ENG)]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20220402T205710/index.html&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.<br /> &quot;&gt;Medicatieproces 9 versie 2.0.0 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> :*[[mp:V2.0.0_MedicationProcess9_FHIR|&lt;abbr title=&quot;FHIR Implementation guide for Medicatieproces 9 versie 2.0.0 FHIR in English&quot;&gt;Implementation guide FHIR Medication Process 9 version 2.0.0 (ENG)&lt;/abbr&gt;]]<br /> :*[[mp:V2.0.0_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 2.0.0&lt;/abbr&gt;]]<br /> :*[[mp:V9_2.0.0_HL7v3CDA_FHIRTiming|HL7v3 CDA substanceAdministration.effectiveTime en FHIR timing]]<br /> :*[[7phcy:V09_HL7v3-domeinspecificatie_Pharmacy|HL7v3-domeinspecificatie Pharmacy Medicatieproces 9]]<br /> :*PGO/MedMij: [[MedMij:Vkickstart/OntwerpMedicatie|&lt;abbr title=&quot;Dit is de link naar het Functioneel Ontwerp Medicatieproces 9 patient use cases nodig voor uitwisseling van PGO binnen oa MedMij&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 2.0.0 voor patient use cases&lt;/abbr&gt;]]<br /> <br /> =PAGINAHISTORIE=<br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> !style=&quot;text-align:left;&quot;&quot; width=&quot;130&quot;|Datum<br /> !style=&quot;text-align:left;&quot;|Omschrijving<br /> |-<br /> | style=&quot;background-color: white;&quot;| 1 maart 2024<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; :'''Informatiestandaard Medicatieproces 9.3.0.0-beta.3''' gepubliceerd<br /> :*[[mp:V3.0.0-beta_Ontwerp_medicatieproces_9|&lt;abbr title=&quot;Het functioneel ontwerp van de informatiestandaard Medicatieproces 9 Het beschrijft de algemene werking en specifieke praktijksituaties.&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 3.0.0-beta.3 (NL)&lt;/abbr&gt;]] / [[mp:V3.0.0-beta_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 3.0.0-beta.3 (ENG)]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.<br /> &quot;&gt;Medicatieproces 9 versie 3.0.0-beta.3 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> :*[[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|&lt;abbr title=&quot;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.3 voor patiënt usecases&quot;&gt;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.3 voor patiënt usecases&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.3_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 3.0.0-beta.3&lt;/abbr&gt;]]<br /> :*Gebruikerseisen: [[mp:Besluiten_kernteams|&lt;abbr title=&quot;Deze pagina bevat de besluiten van de kernteams, met (indien van toepassing) de bijbehorende werkproceseisen, gebruikerseisen en -wensen.&quot;&gt;Besluiten kernteams Medicatieproces 9, inclusief gebruikerseisen en -wensen&lt;/abbr&gt;]]<br /> &lt;li&gt; '''Informatiestandaard Medicatieproces 9.3.0.0-beta.2''' naar archief<br /> :*[[mp:V3.0.0-beta.2_Ontwerp_medicatieproces_9|&lt;abbr title=&quot;Het functioneel ontwerp van de informatiestandaard Medicatieproces 9 Het beschrijft de algemene werking en specifieke praktijksituaties.&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 3.0.0-beta.2 (NL)&lt;/abbr&gt;]] / [[mp:V3.0.0-beta.2_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 3.0.0-beta.2 (ENG)]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/index.html&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.<br /> &quot;&gt;Medicatieproces 9 versie 3.0.0-beta.2 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> :*[[mp:V3.0.0_MedicationProcess9_FHIR|&lt;abbr title=&quot;FHIR Implementation guide for Medicatieproces 9 versie 3.0.0-beta.1 FHIR in English&quot;&gt;Implementation guide FHIR Medication Process 9 version 3.0.0-beta.2 (ENG) &lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|&lt;abbr title=&quot;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.2 voor patiënt usecases&quot;&gt;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.2 voor patiënt usecases&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.2_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 3.0.0-beta.2&lt;/abbr&gt;]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/index.html&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.<br /> &quot;&gt;Medicatieproces 9 versie 3.0.0-beta.2 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;] <br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 6 november 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; [[mp:V3.0.0-beta.1_MedicationProcess9_FHIR|&lt;abbr title=&quot;FHIR Implementation guide for Medicatieproces 9 versie 3.0.0-beta.1 FHIR in English&quot;&gt;Implementation guide FHIR Medication Process 9 version 3.0.0-beta.1 (ENG)&lt;/abbr&gt;]] naar archief<br /> &lt;li&gt; [https://simplifier.net/packages/nictiz.fhir.nl.r4.medicationprocess9/2.0.0-beta.1/ FHIR R4 conformance resources for Medication Process 9 (MP9)] naar archief<br /> &lt;li&gt; [[mp:V3.0.0-beta.1_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.1 for patient use cases&lt;/abbr&gt;]] naar archief<br /> &lt;li&gt; [https://simplifier.net/packages/nictiz.fhir.nl.r4.medicationprocess9/2.0.0-beta.2/ FHIR R4 conformance resources for Medication Process 9 (MP9)] geüpdatet naar beta.2 versie<br /> &lt;li&gt; [[mp:V3.0.0_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&lt;/abbr&gt;]] toegevoegd<br /> &lt;li&gt; [https://decor.nictiz.nl/pub/vzvz/index.php?prefix=mp-vzvz-&lt;abbr title=&quot;&quot;&gt;ART-DECOR Publicatiepagina VZVZ: Medicatieproces op het LSP&lt;/abbr&gt;] geüpdatet n.a.v. beta.2 versie<br /> &lt;li&gt; [https://zt-medicatieoverdracht.scrollhelp.site/Medicatieoverdracht/Working-version/programma-van-eisen-medicatieoverdracht&lt;abbr title=&quot;De beschikbare Programma van Eisen waaraan de Kickstart deelnemers moeten voldoen. Deze documenten beschrijven de eisen om aan te sluiten op de AORTA-infrastructuur.&quot;&gt;Programma van eisen LSP (bèta)&lt;/abbr&gt;] geüpdatet n.a.v. beta.2 versie<br /> &lt;li&gt; [https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpublicvzvz.refined.site%2Fspace%2FA8%2F85000200%2FAORTA%2B8.3.0&amp;data=05%7C01%7Ctheunissen%40nictiz.nl%7C52a3bf5378624ff2978e08db8f44c3a3%7C3d542e8da3eb448f998ddd6880dc119c%7C0%7C0%7C638261297740578594%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=6%2FH9yQ0EAHEmGYHgbVoQo995poc34CXlV6UcBP4MSD8%3D&amp;reserved=0&lt;abbr title=&quot;Deze pagina bevat de algemene specificaties van de zorginfrastructuur AORTA v8.3.0.0&quot;&gt;Documentatie AORTA versie 8.3.0.0&lt;/abbr&gt;] geüpdatet n.a.v. beta.2 versie<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 20 oktober 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; [[mp:V3.0.0-beta.2_releasenotes|Release notes Medicatieproces 9 versie 3.0.0-beta.2]] toegevoegd<br /> &lt;li&gt; 2.2 Specificaties: update n.a.v. beta.2 release<br /> *[[mp:V3.0.0-beta_Ontwerp_medicatieproces_9|&lt;abbr title=&quot;Het functioneel ontwerp van de informatiestandaard Medicatieproces 9 Het beschrijft de algemene werking en specifieke praktijksituaties.&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 3.0.0-beta.2 (NL)&lt;/abbr&gt;]] / [[mp:V3.0.0-beta_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 3.0.0-beta.2 (ENG)]]<br /> *[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20230217T123829/index.html&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.<br /> &quot;&gt;Medicatieproces 9 versie 3.0.0-beta.2 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> *[[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|&lt;abbr title=&quot;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.2 voor patiënt usecases&quot;&gt;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.2 voor patiënt usecases&lt;/abbr&gt;]]<br /> *[[mp:V3.0.0_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&lt;/abbr&gt;]]<br /> &lt;li&gt; 3.2 Testscript: update n.a.v. beta.2 release<br /> *[[mp:Vcurrent_Kwalificatie#Medicatieproces_9_versie_3.0.0-beta.1_testmateriaal_en_kwalificatiescripts_voor_Kickstart|Testscripts Medicatieproces 9 versie 3.0.0-beta.2]]<br /> &lt;li&gt; [[mp:V3.0.0-beta.1_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 3.0.0-beta.1&lt;/abbr&gt;]] naar archief<br /> &lt;li&gt; [[mp:V3.0.0-beta.1_Ontwerp_medicatieproces_9|Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.1]] &amp; [[mp:V3.0.0-beta.1_Ontwerp_medicatieproces_9_ENG|Functional Design Medication Process 9 version 3.0.0-beta.1 English version]] naar archief<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 11 oktober 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 3.2 Testscripts: Nieuwe versie Testscript gebruikerseisen boven sectoraal: [https://informatiestandaarden.nictiz.nl/wiki/Bestand:Use_case_scenario%27s_en_testscripts_GERRIT_-_Pati%C3%ABnt_1tm4_-_stap_3-4_-_beta_versie_3.0_.pdf Use case scenario's en testscripts GERRIT - Patiënt 1tm4 - stap 3-4 - beta versie 3.0&lt;/abbr&gt;] toegevoegd.<br /> &lt;li&gt; 3.2 Testscripts: Nieuwe versie Testscript gebruikerseisen boven sectoraal: [https://informatiestandaarden.nictiz.nl/wiki/Bestand:Use_case_scenario%27s_en_testscripts_Rijnmond_-_pati%C3%ABnt_1-4_-_stap_3-4_-_beta_versie_3.0_(1).pdf Use case scenario's en testscripts Rijnmond - patiënt 1-4 - stap 3-4 - beta versie 3.0&lt;/abbr&gt;] toegevoegd.<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 6 september 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 2.5 [[mp:V3.0_Voorbeelden_doseringen|&lt;abbr title=&quot;Uitgewerkte voorbeelden voor het concept 'Gebruiksinstructie' uit de dataset van de Informatiestandaard Medicatieproces 9&quot;&gt;Voorbeelden doseringen&lt;/abbr&gt;]] aangepast naar 9.3 versie.<br /> |-<br /> | style=&quot;background-color: white;&quot;| 4 september 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 3.2 Testscripts: Testscript gebruikerseisen boven sectoraal: [https://informatiestandaarden.nictiz.nl/wiki/Bestand:Use_case_scenario%27s_en_testscripts_GERRIT_-_Pati%C3%ABnt_1tm4_-_stap_3-4_-_beta_versie_3.0_.pdf Use case scenario's en testscripts GERRIT - Patiënt 1tm4 - stap 3-4 - beta versie 3.0&lt;/abbr&gt;] toegevoegd.<br /> &lt;li&gt; 3.2 Testscripts: Testscript gebruikerseisen boven sectoraal: [https://informatiestandaarden.nictiz.nl/wiki/Bestand:Use_case_scenario%27s_en_testscripts_Rijnmond_-_pati%C3%ABnt_1-4_-_stap_3-4_-_beta_versie_3.0_(1).pdf Use case scenario's en testscripts Rijnmond - patiënt 1-4 - stap 3-4 - beta versie 3.0&lt;/abbr&gt;] toegevoegd.<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 28 juli 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 2.2 Specificaties: Infrastructuur: [https://publicvzvz.refined.site/space/MED/86179842/Kickstart+van+Medicatieoverdracht Programma van eisen LSP (bèta)] link aangepast naar pagina met meest recente informatie<br /> &lt;li&gt; 2.2 Specificaties: Infrastructuur: [https://publicvzvz.refined.site/space/A8/85000200/AORTA+8.3.0 Documentatie AORTA versie 8.3.0.0] link aangepast naar pagina met meest recente informatie<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 2 juni 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 3.2 Testscripts: Algemene eisen MP9 &amp; Generieke voorzieningen toegevoegd<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 30 mei 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 2.1 Voorbereiding: Plan van aanpak versie 3.1. Addendum plan van aanpak Kickstart v3.1 - Aanpassing Kickstartplanning Mei 2023 toegevoegd aan onderliggende pagina<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 4 mei 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 2.2 Specificaties: [[mp:V2.0.0_Verwijzing_naar_documentatie_Medicatieproces9_tbv_Kickstart|Verzamelbestand met functionele, technische en infrastructurele documentatie Medicatieproces 9 t.b.v. Kickstart]] ge-update met linkjes naar 9.3 versie<br /> &lt;li&gt; 3.1 Testinformatie Kickstart: [[mp:Testen_Kickstart|Testen Kickstart]] toegevoegd.<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 25 april 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 2.2 Specificaties: [[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.1 voor patiënt usecases]] toegevoegd .&lt;br&gt;<br /> &lt;li&gt; 2.2 Specificaties: [[mp:V3.0.0_MedicationProcess9_FHIR_for_patient_use_cases|FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.1 for patient use cases]] toegevoegd.&lt;br&gt;<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 20 april 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 4.1 Testen met ART-DECOR: onderliggende pagina vervangen naar [[HL7v3 kwalificatiesimulator]] .&lt;br&gt;<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 11 april 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; Hoofdstuk 3.1 nieuwe versie testscripts toegevoegd: [[mp:Vcurrent_Kwalificatie#Medicatieproces_9_versie_3.0.0-beta.1_testmateriaal_en_kwalificatiescripts_voor_Kickstart|Medicatieproces 9 versie 3.0.0-beta.1]]&lt;br&gt;<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 21 maart 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; Hoofdstuk 6 MEMO'S toegevoegd&lt;br&gt;<br /> &lt;li&gt; Memo MBH-ID Transformatiedienst 15-03-2023 toegevoegd&lt;br&gt;<br /> &lt;li&gt; Memo vooraankondiging 07-03-2023 toegevoegd<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 6 maart 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; Implementatiehandleiding Consolidatie en afleidingsregels toegevoegd&lt;br&gt;<br /> &lt;li&gt; Specificaties Informatiestandaard Medicatieproces 9 versie 3.0.0-beta.1 toegevoegd<br /> * Functioneel ontwerp<br /> * Technisch ontwerp CDA<br /> * Technisch ontwerp FHIR<br /> * Release notes <br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 18 januari 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt;[https://decor.nictiz.nl/pub/vzvz/aorta-vzvz-html-20221128T172039/sc-2.16.840.1.113883.2.4.3.111.3.2.3.3-2016-09-20T163842.html Implementatie van de ping-pong toets]: link aangepast naar AORTA 8.3 versie<br /> &lt;li&gt;[https://decor.nictiz.nl/pub/vzvz/aorta-vzvz-html-20221128T172039/sc-2.16.840.1.113883.2.4.3.111.3.2.3.1-2016-09-20T091642.html Beheren TKID applicatie]: link aangepast naar AORTA 8.3 versie<br /> &lt;li&gt;[https://public.vzvz.nl/download/attachments/41779447/AORTA_Proces_VWI_Synchronisatie.pdf?api=v2 Proces VWI synchronisatie]: link aangepast naar AORTA 8.3 documentatie<br /> &lt;li&gt;[https://public.vzvz.nl/download/attachments/41779447/AORTA_Sgl_Ontw_Gebeurtenisverwerking.pdf?api=v2 Ontwerp gebeurtenisverwerking]: link aangepast naar AORTA 8.3 documentatie<br /> &lt;li&gt;[https://public.vzvz.nl/download/attachments/41779447/AORTA_Sgl_Ontw_Abonnementenregister.pdf?api=v2 Ontwerp abonnementenregister]: link aangepast naar AORTA 8.3 documentatie<br /> &lt;li&gt;[https://www.vzvz.nl/diensten/gemeenschappelijke-diensten/zorg-ab Implementatie handleiding ZORG-AB]: link aangepast naar Zorg-AB pagina met meest recente documentatie<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 29 september 2022<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt;Specificaties Lab2zorg: link toegevoegd naar de [[mp:LeeswijzerVoorschriftmetnierfunctiewaarde|leeswijzer ten behoeve van het meesturen van de nierfunctiewaarde met het voorschrift]]&lt;br&gt;<br /> De leeswijzer legt uit welk onderdeel van Lab2zorg binnen de scope van de Kickstart valt en welke documentatie daarop van toepassing is. De leeswijzer vervangt het aanvullingendocument.<br /> &lt;li&gt;Specificaties Lab2zorg: link verwijderd naar het [[Lab:V3.0.0_Ontwerp_Laboverdacht|functioneel ontwerp informatiestandaard uitwisseling Laboratoriumgegevens versie 3.0.0]]&lt;br&gt;<br /> De informatiestandaard beschrijft de algemene werking voor alle uitwisselingen van Laboratoriumgegevens. Het onderdeel lab2zorg hieruit wordt gebruikt in de kickstart.<br /> &lt;li&gt;Specificaties Lab2zorg: link verwijderd naar aanvullingendocument<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 12 september 2022<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt;Specificaties: link toegevoegd naar [[mp:Stap_0_Voorbereiding|Werkzaamheden in stap 0 Voorbereiding]]<br /> &lt;li&gt;Informatievoorziening: link toegevoegd naar [[mp:Medicatieoverdracht_Kickstart_Vragen|Vragen en antwoorden uit vragenuur op vrijdagen]]&lt;br&gt;<br /> Na elk vragenuur worden de vragen en antwoorden aan deze pagina toegevoegd<br /> &lt;li&gt;Archief: link naar oude versie nulpunt document verwijderd en link naar nieuwe toegevoegd [https://informatiestandaarden.nictiz.nl/images/4/42/Nulpunt_documentatie_Kickstart_contract_leveranciers_versie11_20220907.pdf Nulpunt documentatie leveranciers versie 1.1 van 7 september 2022] &lt;br&gt;<br /> Inhoudelijke wijziging versie 1.1: link naar document Werkzaamheden in stap 0 Voorbereiding toegevoegd<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 1 september 2022<br /> | style=&quot;background-color: white;&quot;| Formele publicatie van de pagina + update: <br /> &lt;ul&gt;<br /> &lt;li&gt;Titel aangepast<br /> &lt;li&gt;Algemeen referentie: onderdeel toegevoegd en kwaliteitsstandaard toegevoegd<br /> &lt;li&gt;Voorbereiding: checklists verwijderd<br /> &lt;li&gt;Specificaties: verzamelbestand omgezet van Excel naar wiki<br /> &lt;li&gt;Specificaties MP9: gebruikerseisen toegevoegd<br /> &lt;li&gt;Specificaties Lab2zorg: labdocumentatie toegevoegd<br /> &lt;li&gt;Specificaties Infrastructuur: aorta 8.2 vervangen door aorta 8.3 (8.2 naar archief)<br /> &lt;li&gt;Test- en validatiemateriaal: testscripts en kwalificatiescripts gesplitst, alleen testscripts MP9 gelinkt en labtestmateriaal toegevoegd<br /> &lt;li&gt;Tooling BITS: handleiding BITS toegevoegd<br /> &lt;li&gt;Archief: nulpunt 1 september 2022 toegevoegd<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 1 augustus 2022<br /> | style=&quot;background-color: white;&quot;| Correctie in ''Verzamelbestand met functionele, technische en infrastructurele documentatie Medicatieproces 9 t.b.v. Kickstart''<br /> |-<br /> | style=&quot;background-color: white;&quot;| juli 2022<br /> | style=&quot;background-color: white;&quot;| Pagina gepubliceerd<br /> |}</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=mp:Medicatieoverdracht_Kickstart&diff=206656 2024-03-06T16:33:41Z

<p>Luud Slagter: /* ARCHIEF */ Updated hyperlinks in Archive</p> <hr /> <div>{{DISPLAYTITLE:Kickstart Medicatieoverdracht - Landingspagina documentatie leveranciers (Handboek)}}<br /> <br /> __NUMBEREDHEADINGS__<br /> =ALGEMEEN REFERENTIE=<br /> :*[https://www.zorginzicht.nl/binaries/content/assets/zorginzicht/kwaliteitsinstrumenten/Kwaliteitsstandaard+Overdracht+van+medicatiegegevens+in+de+keten.pdf Kwaliteitsstandaard: richtlijn overdracht van medicatiegegevens in de keten]&lt;br&gt;<br /> <br /> =BOUWDOCUMENTATIE=<br /> {{IssueBox|'''FHIR specs voor versie 3.0.0-beta.3 volgen op 7 maart'''}}<br /> ==Voorbereiding==<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/pva_kickstart/&lt;abbr title=&quot;Het Plan van aanpak versie 3.1 voor de uitvoering van de Kickstart. Het Plan van aanpak versie 3.1 beschrijft het doel, de opzet, aanpak en kaders voor de uitvoering van de Kickstart.&quot;&gt;Plan van aanpak versie 3.1&lt;/abbr&gt;]<br /> <br /> ==Specificaties==<br /> :'''Verzamelbestand informatiestandaarden'''<br /> :*[[mp:V2.0.0_Verwijzing_naar_documentatie_Medicatieproces9_tbv_Kickstart|Verzamelbestand met functionele, technische en infrastructurele documentatie Medicatieproces 9 t.b.v. Kickstart]]<br /> <br /> :'''Voorbereiding'''<br /> :*[[mp:Stap_0_Voorbereiding|Werkzaamheden in stap 0 Voorbereiding]]<br /> <br /> :'''Informatiestandaard Medicatieproces 9.3.0.0-beta.3'''<br /> :*[[mp:V3.0.0-beta_Ontwerp_medicatieproces_9|&lt;abbr title=&quot;Het functioneel ontwerp van de informatiestandaard Medicatieproces 9 Het beschrijft de algemene werking en specifieke praktijksituaties.&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 3.0.0-beta.3 (NL)&lt;/abbr&gt;]] / [[mp:V3.0.0-beta_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 3.0.0-beta.3 (ENG)]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.<br /> &quot;&gt;Medicatieproces 9 versie 3.0.0-beta.3 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> :*[[mp:V3.0.0_MedicationProcess9_FHIR|&lt;abbr title=&quot;FHIR Implementation guide for Medicatieproces 9 versie 3.0.0-beta.2 FHIR in English&quot;&gt;Implementation guide FHIR Medication Process 9 version 3.0.0-beta.2 (ENG) &lt;/abbr&gt;]]<br /> :*[https://simplifier.net/packages/nictiz.fhir.nl.r4.medicationprocess9/2.0.0-beta.1/ FHIR R4 conformance resources for Medication Process 9 (MP9)]<br /> :*[[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|&lt;abbr title=&quot;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.3 voor patiënt usecases&quot;&gt;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.3 voor patiënt usecases&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases &lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.3_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 3.0.0-beta.3&lt;/abbr&gt;]]<br /> :*Gebruikerseisen: [[mp:Besluiten_kernteams|&lt;abbr title=&quot;Deze pagina bevat de besluiten van de kernteams, met (indien van toepassing) de bijbehorende werkproceseisen, gebruikerseisen en -wensen.&quot;&gt;Besluiten kernteams Medicatieproces 9, inclusief gebruikerseisen en -wensen&lt;/abbr&gt;]]<br /> <br /> :'''Informatiestandaard Lab2zorg'''<br /> :*[[mp:LeeswijzerVoorschriftmetnierfunctiewaarde|&lt;abbr title=&quot;De leeswijzer geeft aan welk onderdeel van Lab2zorg binnen de scope van de Kickstart valt en welke documentatie daarop van toepassing is.&quot;&gt;Leeswijzer ten behoeve van het meesturen van de nierfunctiewaarde met het voorschrift&lt;/abbr&gt;]]<br /> :*[[Lab:Vcurrent_Ontwerp_Lab2zorg|&lt;abbr title=&quot;Het functioneel ontwerp van Lab2zorg. In de kickstart wordt het onderdeel lab2zorg gebruikt voor het meesturen van een nierfunctiewaarde met het voorschrift. Deze usecase staat beschreven in paragraaf 2.3 van het functioneel ontwerp lab2zorg.&quot;&gt;Functioneel ontwerp Lab2zorg versie 3.0.0&lt;/abbr&gt;]]<br /> :*[[Lab:Vcurrent_Kwalificatie|&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard uitwisseling laboratoriumgegevens de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties. Voor de kickstart wordt sturen/ontvangen laboratoriumresultaten uit lab2zorg gebruikt.&quot;&gt;Labuitwisseling versie 3.0.0 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]]<br /> :*[[Lab:V3.0.0_FHIR_Lab2zorg|&lt;abbr title=&quot;Technische FHIR specificaties van Lab2zorg in aanvulling op het functioneel ontwerp. Paragraaf 4.3 beschrijft het sturen van laboratoriumresultaten tussen zorgverleners dat in de kickstart gebruikt wordt.&quot;&gt;FHIR Lab2zorg version 3.0.0 (ENG)&lt;/abbr&gt;]]<br /> <br /> :'''Infrastructuur'''<br /> :*[https://decor.nictiz.nl/pub/vzvz/index.php?prefix=mp-vzvz-&lt;abbr title=&quot;&quot;&gt;ART-DECOR Publicatiepagina VZVZ: Medicatieproces op het LSP&lt;/abbr&gt;]<br /> :*[https://zt-medicatieoverdracht.scrollhelp.site/Medicatieoverdracht/Working-version/programma-van-eisen-medicatieoverdracht&lt;abbr title=&quot;De beschikbare Programma van Eisen waaraan de Kickstart deelnemers moeten voldoen. Deze documenten beschrijven de eisen om aan te sluiten op de AORTA-infrastructuur.&quot;&gt;Programma van eisen LSP (bèta)&lt;/abbr&gt;]<br /> :*[https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpublicvzvz.refined.site%2Fspace%2FA8%2F85000200%2FAORTA%2B8.3.0&amp;data=05%7C01%7Ctheunissen%40nictiz.nl%7C52a3bf5378624ff2978e08db8f44c3a3%7C3d542e8da3eb448f998ddd6880dc119c%7C0%7C0%7C638261297740578594%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=6%2FH9yQ0EAHEmGYHgbVoQo995poc34CXlV6UcBP4MSD8%3D&amp;reserved=0&lt;abbr title=&quot;Deze pagina bevat de algemene specificaties van de zorginfrastructuur AORTA v8.3.0.0&quot;&gt;Documentatie AORTA versie 8.3.0.0&lt;/abbr&gt;]<br /> <br /> ==IT-Infrastructuur==<br /> :*[https://decor.nictiz.nl/pub/vzvz/aorta-vzvz-html-20221128T172039/sc-2.16.840.1.113883.2.4.3.111.3.2.3.3-2016-09-20T163842.html Implementatie van de ping-pong toets]<br /> :*[https://decor.nictiz.nl/pub/vzvz/aorta-vzvz-html-20221128T172039/sc-2.16.840.1.113883.2.4.3.111.3.2.3.1-2016-09-20T091642.html Beheren TKID applicatie]<br /> :*[https://public.vzvz.nl/download/attachments/41779447/AORTA_Proces_VWI_Synchronisatie.pdf?api=v2:~:text=Het%20VWI%2Dsynchronisatie%20proces%20biedt,belang%20van%20pati%C3%ABnt%20en%20zorgaanbieder&lt;abbr title=&quot;Dit document beschrijft de procedure die ervoor zorgt dat elke GBZ-beheerder namens de zorgaanbieder kan vaststellen dat elk patiëntgegeven met toestemming van de patiënt op correcte wijze is aangemeld op de VWI.&quot;&gt;Proces VWI synchronisatie&lt;/abbr&gt;]<br /> :*[https://public.vzvz.nl/download/attachments/41779447/AORTA_Sgl_Ontw_Gebeurtenisverwerking.pdf?api=v2&lt;abbr title=&quot;Dit document beschrijft het ontwerp van de gebeurtenisverdeler component (GVE) en de component gebeurtenisafhandelaar (GAF) in de ZIM.&quot;&gt;Ontwerp gebeurtenisverwerking&lt;/abbr&gt;]<br /> :*[https://public.vzvz.nl/download/attachments/41779447/AORTA_Sgl_Ontw_Abonnementenregister.pdf?api=v2&lt;abbr title=&quot;Dit document beschrijft het ontwerp van de abonnementenregister component (ABR) in de ZIM.&quot;&gt;Ontwerp abonnementenregister&lt;/abbr&gt;]<br /> <br /> ==Implementatiehandleidingen==<br /> :*[[mp:Vkickstart_MigratieHybride|&lt;abbr title=&quot;Handleiding Migratie hybride fase Kickstart&quot;&gt;Implementatiehandleiding Migratie/hybride&lt;/abbr&gt;]]<br /> :*[[mp:Implementatiehandleiding_Consolidatie/afleidingsregels|&lt;abbr title=&quot;Handleiding Consolidatie/afleidingsregels Kickstart&quot;&gt;Implementatiehandleiding Consolidatie/afleidingsregels&lt;/abbr&gt;]]<br /> :*[https://www.aorta-lsp.nl/media/downloads/implementatiehandleiding-verwijsindex-aorta-v8200pdf/download&lt;abbr title=&quot;Implementatiehandleiding verwijsindex AORTA v8.2.0.0&quot;&gt;Implementatiehandleiding VWI AORTA&lt;/abbr&gt;]<br /> :*[https://www.vzvz.nl/media/downloads/zorg-ab-implementatiehandleiding-v27pdf/download&lt;abbr title=Dit document bevat informatie, instructies en voorbeelden ten behoeve van de implementatie van<br /> (applicaties/systemen die gebruik maken van) de web API's van ZORG-AB.&gt;Implementatiehandleiding ZORG-AB&lt;/abbr&gt;]<br /> :*[https://www.aorta-lsp.nl/media/downloads/implementatiehandleiding-inschrijftoken-aorta-v8200pdf/download&lt;abbr title=&quot;Handleiding voor de implementatie van het koppelvlak tussen het goed beheerde Zorgsystemen (GBZ) en het landelijk schakelpunt (LSP).&quot;&gt;Implementatie handleiding inschrijftoken&lt;/abbr&gt;]<br /> :*[https://www.aorta-lsp.nl/media/downloads/implementatiehandleiding-mandaattoken-aorta-v8200pdf/download&lt;abbr title=&quot;Specificatie van het mandaattoken.&quot;&gt;Implementatie handleiding mandaattoken&lt;/abbr&gt;]<br /> :*[https://www.aorta-lsp.nl/media/downloads/implementatiehandleiding-berichtauthenticatie-transactietoken-aorta-v8200pdf/download&lt;abbr title=&quot;Handleiding voor het uitrusten van de berichten met het SAML transactietoken.&quot;&gt;Implementatie handleiding transactiekosten&lt;/abbr&gt;]<br /> <br /> ==Ondersteunende materialen==<br /> :*[[mp:V3.0_Voorbeelden_doseringen|&lt;abbr title=&quot;Uitgewerkte voorbeelden voor het concept 'Gebruiksinstructie' uit de dataset van de Informatiestandaard Medicatieproces 9&quot;&gt;Voorbeelden doseringen&lt;/abbr&gt;]]<br /> :*[[mp:V9_2.0.0_HL7v3CDA_FHIRTiming|&lt;abbr title=&quot;Toedieningsschema HL7v3-template. Introductie van het FHIR timing datatype in CDA substanceAdministration.effectiveTime voor toedieningsschema's. Voorheen was dit de HL7v3 GTS (General Timing Specification). Bevat ook de inhoudelijke wijziging in de XML schema's (xsd's).&quot;&gt;Dosering in FHIR&lt;/abbr&gt;]]<br /> :*[https://github.com/Nictiz/Medicatieviewer&lt;abbr title=&quot;De Medicatieviewer transformeert een MP-9 XML volgens de standaard medicatieproces 9 voor medicatiegegevens of voor medicatieoverzicht in HTML om zo een voor mensen leesbaar overzicht te geven van de inhoud van de XML.&quot;&gt;Medicatieviewer&lt;/abbr&gt;]<br /> :*[https://informatiestandaarden.nictiz.nl/images/c/c9/Medicatieoverzicht_MP90.zip&lt;abbr title=&quot;Uitklapbaar Medicatieoverzicht voorbeeld in HTML-formaat.&quot;&gt;Medicatieoverzicht HTML voorbeeld&lt;/abbr&gt;]<br /> :*[[Mappingarchitectuur#Mappings_en_transacties|&lt;abbr title=&quot;Deze sectie toont verschillende mappings voor transacties uit verschillende informatiestandaarden.&quot;&gt;Mappingarchitectuur&lt;/abbr&gt;]]<br /> :*[[mp:Vdraft_RaadplegenReconcilieren|&lt;abbr title=&quot;Deze pagina bevat nadere toelichting over hoe te reconciliëren na raadplegen. Het bespreekt de volgorde van verwerken van de verschillende soorten binnengekomen informatie.&quot;&gt;Implementatie handleiding Raadplegen Reconciliëren&lt;/abbr&gt;]]<br /> :*[[7phcy:V09_HL7v3-domeinspecificatie_Pharmacy|&lt;abbr title=&quot;Deze pagina geeft nadere toelichting bij templates in ART-DECOR.&quot;&gt;Toelichting bericht templates Medicatieproces versie 9&lt;/abbr&gt;]]<br /> :*[https://www.aorta-lsp.nl/media/downloads/best-practices-vwi-synchronisatie-aorta-v8200pdf/download/&lt;abbr title=&quot;Ter verduidelijking van de implementatiehandleiding VWI. Extra informatie wordt gegeven over de afhandeling van berichten aan de XIS leveranciers en de beheerders om duidelijkheid te geven over de verwachte acties.&quot;&gt;Best practices: VWI synchronisatie &lt;/abbr&gt;]<br /> :*[https://www.aorta-lsp.nl/media/downloads/factsheet-tkidspdf/download/&lt;abbr title=&quot;Deze factsheet beschrijft de werking van TypeKwalificatie-ID’s (TKID’s) op het LSP.&quot;&gt;Factsheet tkid&lt;/abbr&gt;]<br /> :*[https://www.vzvz.nl/diensten/gemeenschappelijke-diensten/zorg-ab&lt;abbr title=&quot;Deze pagina bevat de algemene informatie omtrent Zorg-AG.&quot;&gt;Algemene informatie Zorg-AB&lt;/abbr&gt;]<br /> :*[https://www.vzvz.nl/diensten/gemeenschappelijke-diensten/zorg-id&lt;abbr title=&quot;Deze pagina bevat de algemene informatie omtrent Zorg-ID.&quot;&gt;Algemene informatie Zorg-ID&lt;/abbr&gt;]<br /> <br /> =TEST- EN VALIDATIEMATERIAAL=<br /> ==Testinformatie Kickstart==<br /> :*[[mp:Testen_Kickstart|Testen Kickstart]]<br /> <br /> ==Testscripts==<br /> {{IssueBox|'''De aanpassingen op de testscripts door de release van versie 3.0.0-beta.3 worden op dit moment doorgevoerd'''}}<br /> :'''Medicatieproces 9'''<br /> :*[[mp:Vcurrent_Kwalificatie#Medicatieproces_9_versie_3.0.0-beta.2_testmateriaal_en_kwalificatiescripts_voor_Kickstart|Testscripts Medicatieproces 9 versie 3.0.0-beta.2]]<br /> <br /> :'''Testscript gebruikerseisen boven sectoraal'''<br /> :*[https://informatiestandaarden.nictiz.nl/wiki/Bestand:Use_case_scenario%27s_en_testscripts_GERRIT_-_Pati%C3%ABnt_1tm4_-_stap_3-4_-_beta_versie_3.0_.pdf Use case scenario's en testscripts GERRIT - Patiënt 1tm4 - stap 3-4 - beta versie 3.0&lt;/abbr&gt;]<br /> :*[https://informatiestandaarden.nictiz.nl/wiki/Bestand:Use_case_scenario%27s_en_testscripts_Rijnmond_-_pati%C3%ABnt_1-4_-_stap_3-4_-_beta_versie_3.0_(1).pdf Use case scenario's en testscripts Rijnmond - patiënt 1-4 - stap 3-4 - beta versie 3.0&lt;/abbr&gt;]<br /> <br /> :'''Lab2zorg'''<br /> :*[[Lab:Vcurrent_Kwalificatie#Lab2zorg|&lt;abbr title=&quot;Testgegevens die als voorbereiding op de kwalificatie gebruikt kunnen worden, waarbij voor de kickstart alleen de scripts Laboratoriumresultaten (Sturen/Ontvangen) relevant zijn.&quot;&gt;Testscripts Lab2zorg versie 3.0.0&lt;/abbr&gt;]]<br /> :'''Algemene eisen MP9 &amp; Generieke voorzieningen'''<br /> :*[https://informatiestandaarden.nictiz.nl/images/5/5e/Testscripts_algemene_eisen_MP9_%26_Generieke_voorzieningen.zip Testscripts algemene eisen MP9 &amp; Generieke voorzieningen (zip bestand)]<br /> <br /> ==Validatiescripts==<br /> :*Kwalificatiescripts worden definitief opgeleverd als bekend is op welke versie gevalideerd wordt in de Kickstart.<br /> :*Acceptatiescripts worden gegenereerd op het moment dat de leverancier zich meldt; dit betreft maatwerk.<br /> <br /> =TOOLING=<br /> :*[https://informatiestandaarden.nictiz.nl/images/3/30/Tooling.pdf&lt;abbr title=&quot;Overzicht van de te gebruiken tooling.&quot;&gt;Beschikbare tooling&lt;/abbr&gt;]<br /> <br /> ==ART-DECOR==<br /> :*[https://decor.nictiz.nl/art-decor/home&lt;abbr title=&quot;Inlogpagina ART-DECOR&quot;&gt;Inloggen ART-DECOR&lt;/abbr&gt;]<br /> :*[[HL7v3 kwalificatiesimulator|&lt;abbr title=&quot;Uitleg over inloggen en gebruik van de kwalificatiesimulator (ART-DECOR)&quot;&gt;Testen met ART-DECOR / Kwalificatiesimulator&lt;/abbr&gt;]]<br /> :*[https://art-decor.org/mediawiki/index.php?title=Documentation&lt;abbr title=&quot;Handleidingen en documentatie van ART-DECOR &quot;&gt;ART-DECOR documentatie&lt;/abbr&gt;]<br /> :*[[7phcy:V2.0_Toelichting_samenhang_Wiki_en_ART-DECOR|&lt;abbr title=&quot;Deze toelichting beschrijft de samenhang tussen: de HL7v3-implementatiehandleiding Medicatieproces 9 wiki en de bijbehorende html-publicatie van ART-DECOR.&quot;&gt;Wiki &amp; ART-DECOR&lt;/abbr&gt;]]<br /> <br /> ==BITS==<br /> :*[https://bits.nictiz.nl/ Link naar BITS algemeen]<br /> :*[https://bits.nictiz.nl/projects/MP/issues/ Link naar openstaande issues Medicatieproces in BITS]<br /> :*[https://informatiestandaarden.nictiz.nl/images/8/87/Handleiding_BITS_voor_leveranciers.pdf Handleiding BITS validatieloket]<br /> <br /> ==Touchstone==<br /> :*[https://touchstone.aegis.net/touchstone/login&lt;abbr title=&quot;Inlogpagina Touchstone&quot;&gt;Inloggen Touchstone&lt;/abbr&gt;]<br /> :*[[mp:Vcurrent_Kwalificatie#Touchstone|Testen met Touchstone]]<br /> <br /> ==ZORG-AB==<br /> :*[https://zorg-ab-oas.vzvz.nl/&lt;abbr title=&quot;Testapplicatie Zorg-AB&quot;&gt;ZORG-AB testapplicatie&lt;/abbr&gt;]<br /> :*[https://www.vzvz.nl/diensten/gemeenschappelijke-diensten/zorg-ab&lt;abbr title=&quot;Deze pagina bevat informatie, instructies en voorbeelden ten behoeve van de implementatie van<br /> (applicaties/systemen die gebruik maken van) de web API's van ZORG-AB.&quot;&gt;Implementatie handleiding ZORG-AB&lt;/abbr&gt;]<br /> <br /> =INFORMATIEVOORZIENING=<br /> <br /> ==Vragen en antwoorden==<br /> :*[[mp:Medicatieoverdracht_Kickstart_Vragen|Vragen en antwoorden uit vragenuur op vrijdagen]]<br /> <br /> ==Kennissessie==<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/luistersessie-introductiesessie-medicatieproces/ &lt;abbr title=&quot;In deze kennissessie wordt een introductie gegeven van het programma Medicatieoverdracht, de richtlijn Overdracht van medicatiegegevens in de keten, de informatiestandaard Medicatieproces 9&quot;&gt;Kennissessie: Introductie Medicatieoverdracht&lt;/abbr&gt;]<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/kennissessie-wat-kan-ik-verwachten-van-medicatieoverdracht/ &lt;abbr title=&quot;In deze kennissessie wordt inzicht gegeven in de meerwaarde van het programma Medicatieoverdracht voor de zorgverlener en patiënt en de te nemen acties op procesniveau. Per rol (voorschrijver, apotheker, toediener en patiënt) worden de stappen die worden beproefd in de Kickstart toegelicht.&quot;&gt;Kennissessie: Wat kan ik verwachten van Medicatieoverdracht&lt;/abbr&gt;]<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/kennissessie-verdieping-medicatieoverdracht/ &lt;abbr title=&quot;Deze kennissessie is voor iedereen die meer wil weten over het medicatieproces: welke gegevensuitwisselingsmomenten zijn er (transacties), welke rollen horen daarbij, hoe werken de bouwsteen relaties precies etc.&quot;&gt;Kennissessie: Verdieping Medicatieoverdracht&lt;/abbr&gt;]<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/luistersessie-voorgenomen-besluiten-kernteam-medicatie// &lt;abbr title=&quot;Deze kennissessie geeft een beeld van hoe samen met zorgverleners uit de 10 betrokken sectoren afspraken tot stand zijn gekomen t.a.v. beleid, verantwoordelijkheden, zorgprocessen, eenheid van taal in terminologie en codestelsels om de implementatie van de richtlijn en informatiestandaard te ondersteunen. &quot;&gt;Kennissessie: (Voorgenomen) besluiten kernteam Medicatie&lt;/abbr&gt;]<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/luistersessies/&lt;abbr title=&quot;In deze kennissessie wordt de route van de bèta publicatie van de informatiestandaard Medicatieproces 9 naar de definitieve versie toegelicht. &quot;&gt;Kennissessie: Route Medicatieproces 9 v2.0.0 bèta naar definitief&lt;/abbr&gt;]<br /> :*[https://www.samenvoormedicatieoverdracht.nl/kennisbank/luistersessie-testmaterialen-medicatieproces-9-2-0-0-beta/ &lt;abbr title=&quot;In deze kennissessie worden de testmaterialen voor Medicatieproces 9 toegelicht. Wat kan er getest worden, wat is de samenhang tussen de materialen, inhoud van het materiaal, hoe te gebruiken en waar te vinden. &quot;&gt;Kennissessie: Testmaterialen Medicatieproces 9 v2.0.0 bèta&lt;/abbr&gt;]<br /> :*[https://informatiestandaarden.nictiz.nl/images/d/d2/202202_Introductie_AORTA_-_nieuwe_style.pdf &lt;abbr title=&quot;Introductiepresentatie AORTA. Een introductie van infrastructurele AORTA architectuur​, verschillende architectuurlagen​, verschillende componenten​.<br /> Relaties met andere stelsels en producten​.&quot;&gt;Presentatie: Introductie AORTA&lt;/abbr&gt;]<br /> <br /> ==PGO==<br /> :*[https://informatiestandaarden.nictiz.nl/images/6/61/PGOsessiesMedicatieproces_BijlageBijOnlineSessie.pdf &lt;abbr title=&quot;Deze kennissessie geeft een introductie van MedMij in relatie tot Medicatieproces 9.&quot;&gt;Presentatie: Medicatieoverdracht uitleg MedMij&lt;/abbr&gt;]<br /> :*[https://informatiestandaarden.nictiz.nl/images/2/29/PGOsessie_OpnameOnline.mp4 &lt;abbr title=&quot;Opname van de kennissessie: Een introductie van MedMij in relatie tot het Medicatieproces 9.&quot;&gt;Opname: Medicatieoverdracht uitleg presentatie MedMij&lt;/abbr&gt;]<br /> <br /> =MEMO'S=<br /> <br /> ==Informatieve memo's==<br /> :*[https://informatiestandaarden.nictiz.nl/images/7/79/MO_memo_MBH-ID_Transformatiedienst_20230315.pdf&lt;abbr title=&quot;Memo MBH-ID Transformatiedienst_20230315&quot;&gt;Memo MBH-ID Transformatiedienst 15-03-2023&lt;/abbr&gt;]<br /> :*[https://informatiestandaarden.nictiz.nl/images/4/48/MO_memo_vooraankondiging_20230307.pdf&lt;abbr title=&quot;Memo vooraankondiging_20230307&quot;&gt;Memo vooraankondiging 07-03-2023&lt;/abbr&gt;]<br /> <br /> =IN ONTWIKKELING=<br /> :'''Transitie naar Medicatieproces 9 (migratie en hybride situatie)'''<br /> :*[[Vdraft_Mappingarchitectuur#Medicatieproces_.28MP.29_Versie_MP9_2.0_en_versie_9.0.7|&lt;font color=&quot;BBB7B6&quot;&gt;Mappingarchitectuur met mappings MP 9.0.7 &lt;-&gt; MP9 2.0.0&lt;/font&gt;]]<br /> <br /> :'''Kickstart testen'''<br /> :*[[mp:Draft_Testtooling#BITS|&lt;font color=&quot;BBB7B6&quot;&gt;Tooling &amp; omgevingen Kickstart Medicatieoverdracht&lt;/font&gt;]]<br /> <br /> =ARCHIEF=<br /> :*[https://informatiestandaarden.nictiz.nl/images/4/42/Nulpunt_documentatie_Kickstart_contract_leveranciers_versie11_20220907.pdf&lt;abbr title=&quot;Document dat nulpunt beschrijft voor specificaties Kickstart ten behoeve van contract.&quot;&gt;Nulpunt documentatie Kickstart leveranciers versie 1.1 van 7 september 2022&lt;/abbr&gt;]<br /> :* Verzamelbestand in Excel met functionele, technische en infrastructurele documentatie Medicatieproces 9 t.b.v. Kickstart (niet meer te downloaden om verwarring te voorkomen)<br /> :*[https://www.aorta-lsp.nl/voor-wie/ict-leveranciers/aorta-documentatie/infrastructuur-aorta-v8200&lt;abbr title=&quot;Deze pagina bevat de algemene specificaties van de zorginfrastructuur AORTA v8.2.0.0&quot;&gt;Documentatie AORTA 8.2.0.0&lt;/abbr&gt;]<br /> <br /> :'''Informatiestandaard Medicatieproces 9.3.0.0-beta.2'''<br /> :*[[mp:V3.0.0-beta.2_Ontwerp_medicatieproces_9|&lt;abbr title=&quot;Het functioneel ontwerp van de informatiestandaard Medicatieproces 9 Het beschrijft de algemene werking en specifieke praktijksituaties.&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 3.0.0-beta.2 (NL)&lt;/abbr&gt;]] / [[mp:V3.0.0-beta.2_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 3.0.0-beta.2 (ENG)]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/index.html&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.&quot;&gt;Medicatieproces 9 versie 3.0.0-beta.2 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> :*[[mp:V3.0.0-beta.2_MedicationProcess9_FHIR|&lt;abbr title=&quot;FHIR Implementation guide for Medicatieproces 9 versie 3.0.0-beta.2 FHIR in English&quot;&gt;Implementation guide FHIR Medication Process 9 version 3.0.0-beta.2 (ENG) &lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|&lt;abbr title=&quot;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.2 voor patiënt usecases&quot;&gt;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.2 voor patiënt usecases&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.2_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.2_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 3.0.0-beta.2&lt;/abbr&gt;]]<br /> <br /> :'''Informatiestandaard Medicatieproces 9.3.0.0-beta.1'''<br /> :*[[mp:V3.0.0-beta.1_Ontwerp_medicatieproces_9|Functioneel ontwerp Medicatieproces 9 versie 3.0.0-beta.1 (NL)]] / [[mp:V3.0.0-beta.1_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 3.0.0-beta.1 (ENG)]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20230217T123829/index.html&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.&quot;&gt;Medicatieproces 9 versie 3.0.0-beta.1 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> :*[[mp:V3.0.0-beta.1_MedicationProcess9_FHIR|&lt;abbr title=&quot;FHIR Implementation guide for Medicatieproces 9 versie 3.0.0-beta.1 FHIR in English&quot;&gt;Implementation guide FHIR Medication Process 9 version 3.0.0-beta.1 (ENG)&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.1_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.1 for patient use cases&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.1_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 3.0.0-beta.1&lt;/abbr&gt;]]<br /> <br /> :'''Informatiestandaard Medicatieproces 9.2.0.0'''<br /> :*[[mp:V2.0.0_Ontwerp_medicatieproces_9|&lt;abbr title=&quot;Het functioneel ontwerp van de informatiestandaard Medicatieproces 9. Het beschrijft de algemene werking en specifieke praktijksituaties.&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 2.0.0 (NL)&lt;/abbr&gt;]] / [[mp:V2.0.0_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 2.0.0 (ENG)]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20220402T205710/index.html&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.<br /> &quot;&gt;Medicatieproces 9 versie 2.0.0 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> :*[[mp:V2.0.0_MedicationProcess9_FHIR|&lt;abbr title=&quot;FHIR Implementation guide for Medicatieproces 9 versie 2.0.0 FHIR in English&quot;&gt;Implementation guide FHIR Medication Process 9 version 2.0.0 (ENG)&lt;/abbr&gt;]]<br /> :*[[mp:V2.0.0_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 2.0.0&lt;/abbr&gt;]]<br /> :*[[mp:V9_2.0.0_HL7v3CDA_FHIRTiming|HL7v3 CDA substanceAdministration.effectiveTime en FHIR timing]]<br /> :*[[7phcy:V09_HL7v3-domeinspecificatie_Pharmacy|HL7v3-domeinspecificatie Pharmacy Medicatieproces 9]]<br /> :*PGO/MedMij: [[MedMij:Vkickstart/OntwerpMedicatie|&lt;abbr title=&quot;Dit is de link naar het Functioneel Ontwerp Medicatieproces 9 patient use cases nodig voor uitwisseling van PGO binnen oa MedMij&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 2.0.0 voor patient use cases&lt;/abbr&gt;]]<br /> <br /> =PAGINAHISTORIE=<br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> !style=&quot;text-align:left;&quot;&quot; width=&quot;130&quot;|Datum<br /> !style=&quot;text-align:left;&quot;|Omschrijving<br /> |-<br /> | style=&quot;background-color: white;&quot;| 1 maart 2024<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; :'''Informatiestandaard Medicatieproces 9.3.0.0-beta.3''' gepubliceerd<br /> :*[[mp:V3.0.0-beta_Ontwerp_medicatieproces_9|&lt;abbr title=&quot;Het functioneel ontwerp van de informatiestandaard Medicatieproces 9 Het beschrijft de algemene werking en specifieke praktijksituaties.&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 3.0.0-beta.3 (NL)&lt;/abbr&gt;]] / [[mp:V3.0.0-beta_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 3.0.0-beta.3 (ENG)]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20240229T110214/&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.<br /> &quot;&gt;Medicatieproces 9 versie 3.0.0-beta.3 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> :*[[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|&lt;abbr title=&quot;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.3 voor patiënt usecases&quot;&gt;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.3 voor patiënt usecases&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.3_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 3.0.0-beta.3&lt;/abbr&gt;]]<br /> :*Gebruikerseisen: [[mp:Besluiten_kernteams|&lt;abbr title=&quot;Deze pagina bevat de besluiten van de kernteams, met (indien van toepassing) de bijbehorende werkproceseisen, gebruikerseisen en -wensen.&quot;&gt;Besluiten kernteams Medicatieproces 9, inclusief gebruikerseisen en -wensen&lt;/abbr&gt;]]<br /> &lt;li&gt; '''Informatiestandaard Medicatieproces 9.3.0.0-beta.2''' naar archief<br /> :*[[mp:V3.0.0-beta.2_Ontwerp_medicatieproces_9|&lt;abbr title=&quot;Het functioneel ontwerp van de informatiestandaard Medicatieproces 9 Het beschrijft de algemene werking en specifieke praktijksituaties.&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 3.0.0-beta.2 (NL)&lt;/abbr&gt;]] / [[mp:V3.0.0-beta.2_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 3.0.0-beta.2 (ENG)]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/index.html&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.<br /> &quot;&gt;Medicatieproces 9 versie 3.0.0-beta.2 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> :*[[mp:V3.0.0_MedicationProcess9_FHIR|&lt;abbr title=&quot;FHIR Implementation guide for Medicatieproces 9 versie 3.0.0-beta.1 FHIR in English&quot;&gt;Implementation guide FHIR Medication Process 9 version 3.0.0-beta.2 (ENG) &lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|&lt;abbr title=&quot;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.2 voor patiënt usecases&quot;&gt;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.2 voor patiënt usecases&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&lt;/abbr&gt;]]<br /> :*[[mp:V3.0.0-beta.2_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 3.0.0-beta.2&lt;/abbr&gt;]]<br /> :*[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/index.html&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.<br /> &quot;&gt;Medicatieproces 9 versie 3.0.0-beta.2 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;] <br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 6 november 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; [[mp:V3.0.0-beta.1_MedicationProcess9_FHIR|&lt;abbr title=&quot;FHIR Implementation guide for Medicatieproces 9 versie 3.0.0-beta.1 FHIR in English&quot;&gt;Implementation guide FHIR Medication Process 9 version 3.0.0-beta.1 (ENG)&lt;/abbr&gt;]] naar archief<br /> &lt;li&gt; [https://simplifier.net/packages/nictiz.fhir.nl.r4.medicationprocess9/2.0.0-beta.1/ FHIR R4 conformance resources for Medication Process 9 (MP9)] naar archief<br /> &lt;li&gt; [[mp:V3.0.0-beta.1_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.1 for patient use cases&lt;/abbr&gt;]] naar archief<br /> &lt;li&gt; [https://simplifier.net/packages/nictiz.fhir.nl.r4.medicationprocess9/2.0.0-beta.2/ FHIR R4 conformance resources for Medication Process 9 (MP9)] geüpdatet naar beta.2 versie<br /> &lt;li&gt; [[mp:V3.0.0_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&lt;/abbr&gt;]] toegevoegd<br /> &lt;li&gt; [https://decor.nictiz.nl/pub/vzvz/index.php?prefix=mp-vzvz-&lt;abbr title=&quot;&quot;&gt;ART-DECOR Publicatiepagina VZVZ: Medicatieproces op het LSP&lt;/abbr&gt;] geüpdatet n.a.v. beta.2 versie<br /> &lt;li&gt; [https://zt-medicatieoverdracht.scrollhelp.site/Medicatieoverdracht/Working-version/programma-van-eisen-medicatieoverdracht&lt;abbr title=&quot;De beschikbare Programma van Eisen waaraan de Kickstart deelnemers moeten voldoen. Deze documenten beschrijven de eisen om aan te sluiten op de AORTA-infrastructuur.&quot;&gt;Programma van eisen LSP (bèta)&lt;/abbr&gt;] geüpdatet n.a.v. beta.2 versie<br /> &lt;li&gt; [https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpublicvzvz.refined.site%2Fspace%2FA8%2F85000200%2FAORTA%2B8.3.0&amp;data=05%7C01%7Ctheunissen%40nictiz.nl%7C52a3bf5378624ff2978e08db8f44c3a3%7C3d542e8da3eb448f998ddd6880dc119c%7C0%7C0%7C638261297740578594%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=6%2FH9yQ0EAHEmGYHgbVoQo995poc34CXlV6UcBP4MSD8%3D&amp;reserved=0&lt;abbr title=&quot;Deze pagina bevat de algemene specificaties van de zorginfrastructuur AORTA v8.3.0.0&quot;&gt;Documentatie AORTA versie 8.3.0.0&lt;/abbr&gt;] geüpdatet n.a.v. beta.2 versie<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 20 oktober 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; [[mp:V3.0.0-beta.2_releasenotes|Release notes Medicatieproces 9 versie 3.0.0-beta.2]] toegevoegd<br /> &lt;li&gt; 2.2 Specificaties: update n.a.v. beta.2 release<br /> *[[mp:V3.0.0-beta_Ontwerp_medicatieproces_9|&lt;abbr title=&quot;Het functioneel ontwerp van de informatiestandaard Medicatieproces 9 Het beschrijft de algemene werking en specifieke praktijksituaties.&quot;&gt;Functioneel ontwerp Medicatieproces 9 versie 3.0.0-beta.2 (NL)&lt;/abbr&gt;]] / [[mp:V3.0.0-beta_Ontwerp_medicatieproces_9_ENG|Functional design Medication Process 9 version 3.0.0-beta.2 (ENG)]]<br /> *[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20230217T123829/index.html&lt;abbr title=&quot;ART-DECOR bevat voor de informatiestandaard medicatieproces 9: de dataset, de scenario's en transacties, en een praktische implementatiehandleiding van de uitwisselspecificaties.<br /> &quot;&gt;Medicatieproces 9 versie 3.0.0-beta.2 publicatie vanuit ART-DECOR (dataset, scenario/transacties, HL7v3 CDA templates)&lt;/abbr&gt;]<br /> *[[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|&lt;abbr title=&quot;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.2 voor patiënt usecases&quot;&gt;Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.2 voor patiënt usecases&lt;/abbr&gt;]]<br /> *[[mp:V3.0.0_MedicationProcess9_FHIR_for_patient_use_cases|&lt;abbr title=&quot;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&quot;&gt;FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.2 for patient use cases&lt;/abbr&gt;]]<br /> &lt;li&gt; 3.2 Testscript: update n.a.v. beta.2 release<br /> *[[mp:Vcurrent_Kwalificatie#Medicatieproces_9_versie_3.0.0-beta.1_testmateriaal_en_kwalificatiescripts_voor_Kickstart|Testscripts Medicatieproces 9 versie 3.0.0-beta.2]]<br /> &lt;li&gt; [[mp:V3.0.0-beta.1_releasenotes|&lt;abbr title=&quot;Overzicht van de release notes voor de huidige versie ten opzichte van de laatste release.&quot;&gt;Release notes Medicatieproces 9 versie 3.0.0-beta.1&lt;/abbr&gt;]] naar archief<br /> &lt;li&gt; [[mp:V3.0.0-beta.1_Ontwerp_medicatieproces_9|Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.1]] &amp; [[mp:V3.0.0-beta.1_Ontwerp_medicatieproces_9_ENG|Functional Design Medication Process 9 version 3.0.0-beta.1 English version]] naar archief<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 11 oktober 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 3.2 Testscripts: Nieuwe versie Testscript gebruikerseisen boven sectoraal: [https://informatiestandaarden.nictiz.nl/wiki/Bestand:Use_case_scenario%27s_en_testscripts_GERRIT_-_Pati%C3%ABnt_1tm4_-_stap_3-4_-_beta_versie_3.0_.pdf Use case scenario's en testscripts GERRIT - Patiënt 1tm4 - stap 3-4 - beta versie 3.0&lt;/abbr&gt;] toegevoegd.<br /> &lt;li&gt; 3.2 Testscripts: Nieuwe versie Testscript gebruikerseisen boven sectoraal: [https://informatiestandaarden.nictiz.nl/wiki/Bestand:Use_case_scenario%27s_en_testscripts_Rijnmond_-_pati%C3%ABnt_1-4_-_stap_3-4_-_beta_versie_3.0_(1).pdf Use case scenario's en testscripts Rijnmond - patiënt 1-4 - stap 3-4 - beta versie 3.0&lt;/abbr&gt;] toegevoegd.<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 6 september 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 2.5 [[mp:V3.0_Voorbeelden_doseringen|&lt;abbr title=&quot;Uitgewerkte voorbeelden voor het concept 'Gebruiksinstructie' uit de dataset van de Informatiestandaard Medicatieproces 9&quot;&gt;Voorbeelden doseringen&lt;/abbr&gt;]] aangepast naar 9.3 versie.<br /> |-<br /> | style=&quot;background-color: white;&quot;| 4 september 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 3.2 Testscripts: Testscript gebruikerseisen boven sectoraal: [https://informatiestandaarden.nictiz.nl/wiki/Bestand:Use_case_scenario%27s_en_testscripts_GERRIT_-_Pati%C3%ABnt_1tm4_-_stap_3-4_-_beta_versie_3.0_.pdf Use case scenario's en testscripts GERRIT - Patiënt 1tm4 - stap 3-4 - beta versie 3.0&lt;/abbr&gt;] toegevoegd.<br /> &lt;li&gt; 3.2 Testscripts: Testscript gebruikerseisen boven sectoraal: [https://informatiestandaarden.nictiz.nl/wiki/Bestand:Use_case_scenario%27s_en_testscripts_Rijnmond_-_pati%C3%ABnt_1-4_-_stap_3-4_-_beta_versie_3.0_(1).pdf Use case scenario's en testscripts Rijnmond - patiënt 1-4 - stap 3-4 - beta versie 3.0&lt;/abbr&gt;] toegevoegd.<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 28 juli 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 2.2 Specificaties: Infrastructuur: [https://publicvzvz.refined.site/space/MED/86179842/Kickstart+van+Medicatieoverdracht Programma van eisen LSP (bèta)] link aangepast naar pagina met meest recente informatie<br /> &lt;li&gt; 2.2 Specificaties: Infrastructuur: [https://publicvzvz.refined.site/space/A8/85000200/AORTA+8.3.0 Documentatie AORTA versie 8.3.0.0] link aangepast naar pagina met meest recente informatie<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 2 juni 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 3.2 Testscripts: Algemene eisen MP9 &amp; Generieke voorzieningen toegevoegd<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 30 mei 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 2.1 Voorbereiding: Plan van aanpak versie 3.1. Addendum plan van aanpak Kickstart v3.1 - Aanpassing Kickstartplanning Mei 2023 toegevoegd aan onderliggende pagina<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 4 mei 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 2.2 Specificaties: [[mp:V2.0.0_Verwijzing_naar_documentatie_Medicatieproces9_tbv_Kickstart|Verzamelbestand met functionele, technische en infrastructurele documentatie Medicatieproces 9 t.b.v. Kickstart]] ge-update met linkjes naar 9.3 versie<br /> &lt;li&gt; 3.1 Testinformatie Kickstart: [[mp:Testen_Kickstart|Testen Kickstart]] toegevoegd.<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 25 april 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 2.2 Specificaties: [[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|Functioneel Ontwerp Medicatieproces 9 versie 3.0.0-beta.1 voor patiënt usecases]] toegevoegd .&lt;br&gt;<br /> &lt;li&gt; 2.2 Specificaties: [[mp:V3.0.0_MedicationProcess9_FHIR_for_patient_use_cases|FHIR Implementation Guide Medication Process 9 version 3.0.0-beta.1 for patient use cases]] toegevoegd.&lt;br&gt;<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 20 april 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; 4.1 Testen met ART-DECOR: onderliggende pagina vervangen naar [[HL7v3 kwalificatiesimulator]] .&lt;br&gt;<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 11 april 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; Hoofdstuk 3.1 nieuwe versie testscripts toegevoegd: [[mp:Vcurrent_Kwalificatie#Medicatieproces_9_versie_3.0.0-beta.1_testmateriaal_en_kwalificatiescripts_voor_Kickstart|Medicatieproces 9 versie 3.0.0-beta.1]]&lt;br&gt;<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 21 maart 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; Hoofdstuk 6 MEMO'S toegevoegd&lt;br&gt;<br /> &lt;li&gt; Memo MBH-ID Transformatiedienst 15-03-2023 toegevoegd&lt;br&gt;<br /> &lt;li&gt; Memo vooraankondiging 07-03-2023 toegevoegd<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 6 maart 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt; Implementatiehandleiding Consolidatie en afleidingsregels toegevoegd&lt;br&gt;<br /> &lt;li&gt; Specificaties Informatiestandaard Medicatieproces 9 versie 3.0.0-beta.1 toegevoegd<br /> * Functioneel ontwerp<br /> * Technisch ontwerp CDA<br /> * Technisch ontwerp FHIR<br /> * Release notes <br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 18 januari 2023<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt;[https://decor.nictiz.nl/pub/vzvz/aorta-vzvz-html-20221128T172039/sc-2.16.840.1.113883.2.4.3.111.3.2.3.3-2016-09-20T163842.html Implementatie van de ping-pong toets]: link aangepast naar AORTA 8.3 versie<br /> &lt;li&gt;[https://decor.nictiz.nl/pub/vzvz/aorta-vzvz-html-20221128T172039/sc-2.16.840.1.113883.2.4.3.111.3.2.3.1-2016-09-20T091642.html Beheren TKID applicatie]: link aangepast naar AORTA 8.3 versie<br /> &lt;li&gt;[https://public.vzvz.nl/download/attachments/41779447/AORTA_Proces_VWI_Synchronisatie.pdf?api=v2 Proces VWI synchronisatie]: link aangepast naar AORTA 8.3 documentatie<br /> &lt;li&gt;[https://public.vzvz.nl/download/attachments/41779447/AORTA_Sgl_Ontw_Gebeurtenisverwerking.pdf?api=v2 Ontwerp gebeurtenisverwerking]: link aangepast naar AORTA 8.3 documentatie<br /> &lt;li&gt;[https://public.vzvz.nl/download/attachments/41779447/AORTA_Sgl_Ontw_Abonnementenregister.pdf?api=v2 Ontwerp abonnementenregister]: link aangepast naar AORTA 8.3 documentatie<br /> &lt;li&gt;[https://www.vzvz.nl/diensten/gemeenschappelijke-diensten/zorg-ab Implementatie handleiding ZORG-AB]: link aangepast naar Zorg-AB pagina met meest recente documentatie<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 29 september 2022<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt;Specificaties Lab2zorg: link toegevoegd naar de [[mp:LeeswijzerVoorschriftmetnierfunctiewaarde|leeswijzer ten behoeve van het meesturen van de nierfunctiewaarde met het voorschrift]]&lt;br&gt;<br /> De leeswijzer legt uit welk onderdeel van Lab2zorg binnen de scope van de Kickstart valt en welke documentatie daarop van toepassing is. De leeswijzer vervangt het aanvullingendocument.<br /> &lt;li&gt;Specificaties Lab2zorg: link verwijderd naar het [[Lab:V3.0.0_Ontwerp_Laboverdacht|functioneel ontwerp informatiestandaard uitwisseling Laboratoriumgegevens versie 3.0.0]]&lt;br&gt;<br /> De informatiestandaard beschrijft de algemene werking voor alle uitwisselingen van Laboratoriumgegevens. Het onderdeel lab2zorg hieruit wordt gebruikt in de kickstart.<br /> &lt;li&gt;Specificaties Lab2zorg: link verwijderd naar aanvullingendocument<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 12 september 2022<br /> | style=&quot;background-color: white;&quot;| <br /> &lt;ul&gt;<br /> &lt;li&gt;Specificaties: link toegevoegd naar [[mp:Stap_0_Voorbereiding|Werkzaamheden in stap 0 Voorbereiding]]<br /> &lt;li&gt;Informatievoorziening: link toegevoegd naar [[mp:Medicatieoverdracht_Kickstart_Vragen|Vragen en antwoorden uit vragenuur op vrijdagen]]&lt;br&gt;<br /> Na elk vragenuur worden de vragen en antwoorden aan deze pagina toegevoegd<br /> &lt;li&gt;Archief: link naar oude versie nulpunt document verwijderd en link naar nieuwe toegevoegd [https://informatiestandaarden.nictiz.nl/images/4/42/Nulpunt_documentatie_Kickstart_contract_leveranciers_versie11_20220907.pdf Nulpunt documentatie leveranciers versie 1.1 van 7 september 2022] &lt;br&gt;<br /> Inhoudelijke wijziging versie 1.1: link naar document Werkzaamheden in stap 0 Voorbereiding toegevoegd<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 1 september 2022<br /> | style=&quot;background-color: white;&quot;| Formele publicatie van de pagina + update: <br /> &lt;ul&gt;<br /> &lt;li&gt;Titel aangepast<br /> &lt;li&gt;Algemeen referentie: onderdeel toegevoegd en kwaliteitsstandaard toegevoegd<br /> &lt;li&gt;Voorbereiding: checklists verwijderd<br /> &lt;li&gt;Specificaties: verzamelbestand omgezet van Excel naar wiki<br /> &lt;li&gt;Specificaties MP9: gebruikerseisen toegevoegd<br /> &lt;li&gt;Specificaties Lab2zorg: labdocumentatie toegevoegd<br /> &lt;li&gt;Specificaties Infrastructuur: aorta 8.2 vervangen door aorta 8.3 (8.2 naar archief)<br /> &lt;li&gt;Test- en validatiemateriaal: testscripts en kwalificatiescripts gesplitst, alleen testscripts MP9 gelinkt en labtestmateriaal toegevoegd<br /> &lt;li&gt;Tooling BITS: handleiding BITS toegevoegd<br /> &lt;li&gt;Archief: nulpunt 1 september 2022 toegevoegd<br /> &lt;/ul&gt;<br /> |-<br /> | style=&quot;background-color: white;&quot;| 1 augustus 2022<br /> | style=&quot;background-color: white;&quot;| Correctie in ''Verzamelbestand met functionele, technische en infrastructurele documentatie Medicatieproces 9 t.b.v. Kickstart''<br /> |-<br /> | style=&quot;background-color: white;&quot;| juli 2022<br /> | style=&quot;background-color: white;&quot;| Pagina gepubliceerd<br /> |}</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=mp:V3.0.0-beta.2_MedicationProcess9_FHIR_for_patient_use_cases&diff=206655 2024-03-06T16:33:23Z

<p>Luud Slagter: Updated technical design (hyperlinks, banner)</p> <hr /> <div>{{StartUitgefaseerd|06-03-2024|Zie de [[MP:Medicatieoverdracht_Kickstart|kickstart landingspagina Medicatieproces 9]] voor de actuele versie van de informatiestandaard voor de kickstart.|Consult the [[MP:Medicatieoverdracht_Kickstart|kickstart overview page Medication Process 9]] for the current versions of the information standard for the kickstart.}}<br /> <br /> {{IssueBox|'''&lt;big&gt;This is an archived version. [[MP:Medicatieoverdracht_Kickstart|Consult the kickstart overview page for the current versions]].&lt;/big&gt;'''}}<br /> <br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide Medication Process 9 version {{VersieInfo|mp9|release=V3.0.0-beta.2}} for patient use cases}}<br /> {{NoteBox|Deze versie zal worden getoetst tijdens de kickstart medicatieoverdracht. De versie is niet geschikt voor gebruik buiten deze beproeving.}}<br /> <br /> __TOC__<br /> <br /> = Introduction =<br /> This is the implementation guide (IG) for the information standard Medication Process 9 (MP9) version {{VersieInfo|mp9|release=V3.0.0-beta.2}} for patient use cases (MedMij) using the HL7® FHIR® standard. The MP9 standard for MedMij is described in [[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|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 of both MP9 and MedMij and this version of FHIR.<br /> <br /> This document is a specification of [[mp:V3.0.0-beta.2_MedicationProcess9_FHIR|FHIR Implementation Guide Medication Process 9]], only applicable to the patient use cases. The guidelines as specified in the [[MedMij:IG:V1/FHIR_IG|MedMij FHIR Implementation Guide]] apply. This document extends the [[FHIR:V1.0_FHIR_IG_R4|general FHIR Implementation Guide]] with the specification of the 'Afsprakenstelsel'.<br /> <br /> This IG first describes the boundaries and relationships where they differ between the MP9 and MedMij IG, after which the implementation is described per relevant transaction.<br /> <br /> = Boundaries and relationships =<br /> Both the [[mp:V3.0.0-beta.2_MedicationProcess9_FHIR#Boundaries_and_relationships|MP9 Boundaries and relationships]] and the [[MedMij:IG:V1/FHIR_IG#Overarching_principles|MedMij Overarching principles]] apply. The following sections highlight the points where these two documents contradict and provides guidance on which principles to follow.<br /> <br /> == 'Use cases' or 'transactions' ==<br /> Where MP9 uses the term 'transaction', MedMij generally uses the term 'use case'. On this page, the terms are used interchangeable.<br /> <br /> == Patient identification ==<br /> Where MP9 describes the use of {{fhir|patient.identifier}} search parameters, the MedMij use cases use the authentication method outlined by the [[MedMij:IG:V1/FHIR_IG#Afsprakenstelsel|MedMij 'Afsprakenstelsel']], using Oauth2 tokens.<br /> <br /> = Transactions =<br /> This section describes the FHIR implementation of the Retrieve and Serve Medication Data transactions (for MedMij) listed in [[mp:V3.0.0_Ontwerp_medicatieproces_9_voor_patient_usecases|the functional specification]]. Each transaction hyperlinks 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]]).<br /> {{#lst:mp:V3.0.0-beta.2_MedicationProcess9_FHIR|medmij1}}<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.RetrieveServe.MedMij|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}|title=CapabilityStatement Retrieve/serve medication data (MedMij)}}<br /> {{#lst:mp:V3.0.0-beta.2_MedicationProcess9_FHIR|medmij2}}<br /> {{#lst:mp:V3.0.0-beta.2_MedicationProcess9_FHIR|medmij3}}<br /> <br /> =Release notes=<br /> Release notes can be found [[mp:V3.0.0-beta.2_releasenotes|here]].<br /> <br /> =Footnotes=<br /> &lt;references/&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=mp:V3.0.0-beta.2_MedicationProcess9_FHIR&diff=206654 2024-03-06T16:11:25Z

<p>Luud Slagter: Updated hyperlinks within technical design</p> <hr /> <div>{{StartUitgefaseerd|06-03-2024|Zie de [[MP:Medicatieoverdracht_Kickstart|kickstart landingspagina Medicatieproces 9]] voor de actuele versie van de informatiestandaard voor de kickstart.|Consult the [[MP:Medicatieoverdracht_Kickstart|kickstart overview page Medication Process 9]] for the current versions of the information standard for the kickstart.}}<br /> <br /> {{IssueBox|'''&lt;big&gt;This is an archived version. [[MP:Medicatieoverdracht_Kickstart|Consult the kickstart overview page for the current versions]].&lt;/big&gt;'''}}<br /> <br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide Medication Process 9 version {{VersieInfo|mp9|release=V3.0.0-beta.2}} }}<br /> <br /> __TOC__<br /> <br /> = Introduction =<br /> This is the implementation guide (IG) for the information standard Medication Process 9 (MP9) version {{VersieInfo|mp9|release=V3.0.0-beta.2}} using the HL7® FHIR® standard. The MP9 standard is described in [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-beta.2_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.<br /> <br /> 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.<br /> <br /> This IG first describes the boundaries and relationships in place, after which the implementation is described per transaction.<br /> <br /> = Boundaries and relationships =<br /> == Building blocks and profiles ==<br /> <br /> The exchange of data within the MP9 standard version {{VersieInfo|mp9|release=V3.0.0-beta.2}} 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. <br /> <br /> 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.<br /> <br /> Because the way 90 million numbers are exchanged is not compatible with the 2020 publication of zib PharmaceuticalProduct, a fork of the corresponding nl-core profile called 'mp-PharmaceuticalProduct' has been introduced.<br /> <br /> {{NoteBoxNictizR4Package|p1=nictiz.fhir.nl.r4.medicationprocess9|v1={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}|p2=nictiz.fhir.nl.r4.nl-core|v2={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> <br /> 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:<br /> * MP9 version 2.0.0 makes use of version 1.0.0 of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package;<br /> * MP9 version 3.0.0-beta.x makes use of version 2.0.0-beta.x of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package.<br /> <br /> === Medication building blocks ===<br /> <br /> As described above, the main medication building blocks have no dependency on any zib2020 counterparts, resulting in so-called ‘mp’ profiles. Moreover, note that the building block VariableDosingRegimen does not have a zib counterpart, hence it makes sense to include it as an mp profile as well.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |}<br /> <br /> === Supporting building blocks ===<br /> <br /> Additionally, the standard uses several supporting building blocks referenced from the main medication building blocks. All supporting building blocks are part of the [[FHIR:V1.0_FHIR_IG_R4#Functional_definitions|‘nl-core’ package]]&lt;ref&gt;Although the nl-core package is still in beta-status, HL7 Netherlands has validated the profiles mentioned and assigned the status 'STU-NL' for use in the MP9 Kickstart, see [[Media:HL7_Nederland_disclaimer_STU-NL.pdf]]&lt;/ref&gt;.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |}<br /> <br /> Note the following:<br /> * Each occurrence of the zib HealthProfessional is normally represented by '''two''' FHIR resources: an instance of nl-core-HealthProfessional-PractitionerRole and an instance of nl-core-HealthProfessional-Practitioner. Sending systems should only fill the reference to the PractitionerRole instance where relevant. Receiving systems can resolve the reference to the Practitioner resource from that PractitionerRole instance.<br /> * The zib HealthcareProvider is mapped to both a Location and Organization profile. Most often, the Location profile acts as the focal resource, because most references to this zib are concerned about the recording of the physical location where the care to patient/client takes place rather than the organizational information. For the latter, the profile on Organization is used which is referenced using the {{fhir|Location.managingOrganization}} element. Sending systems should only fill the reference to the Location instance where relevant. Incidentally, concepts that are only concerned with organizational information can refer to the Organization instance.<br /> <br /> === Transaction specific profiles ===<br /> <br /> For several transactions, additional profiles are provided. For each transaction the profile relevant is explicitly mentioned in the corresponding subsection.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |}<br /> <br /> ====Bundle profiles====<br /> 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.2_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.<br /> <br /> 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.<br /> <br /> Where the functional specification of a transaction expects a HealthProfessional building block, both [[mp:V3.0.0-beta.2_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.<br /> <br /> == Mappings between profiles and data set ==<br /> 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.<br /> <br /> 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:<br /> * 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)<br /> ** 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.<br /> ** 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.<br /> * If an element in the functional definition is removed<br /> ** and the element had a zib mapping applied, the zib mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> ** and the element had a mapping applied to the previous version of MP9, that mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> <br /> Moreover, all mappings to earlier versions of MP9 (i.e. versions before the previous version) are entirely removed.<br /> <br /> Following the procedure outlined above thus results in the following:<br /> * 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.<br /> * All incompatible changes made in the latest version with respect to the previous version are marked.<br /> <br /> 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’]].<br /> <br /> 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.<br /> <br /> 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]].<br /> <br /> == Pharmaceutical treatment ==<br /> 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.2_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.<br /> <br /> == Patient identification ==<br /> This implementation guide assumes that the client system is able to make a connection to the right server that contains the patient's information. It does not provide information on finding the right server nor does it provide information about security. Moreover, each transaction is performed in the context of a specific patient, whose context might have been established using the authentication mechanisms described in external specifications such as the MedMij ‘Afsprakenstelsel’ or through the usage of search parameters for patient identification. <br /> <br /> Each server is required to perform filtering based on the patient associated with the context for the request or based on the patient identification search parameters, which is a [https://www.hl7.org/fhir/r4/search.html#chaining chained search parameter] for all resource types except Patient, so only the records associated with the authenticated patient are returned.<br /> <br /> When patient identification requires the use of search parameters, the following search parameters SHALL be supported:<br /> * Patient: {{fhir|identifier}}<br /> * MedicationRequest: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationDispense: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationStatement: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationAdministration: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> <br /> An example of a request that retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233:<br /> <br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> <br /> All request examples in this document do not include patient identification mechanisms. Requesters are assumed to include these if necessary.<br /> <br /> == Resource identification ==<br /> 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}}.<br /> <br /> 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 &lt;code&gt;@root&lt;/code&gt; and &lt;code&gt;@extension&lt;/code&gt; (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.<br /> <br /> 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|release=V3.0.0-beta.2}}}} 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]].<br /> <br /> == Differentiating between transactions ==<br /> All transactions described in this IG use the same medication building blocks in different combinations and settings, making it necessary to differentiate between them. Several mechanisms are used to achieve this. Aside from PUSH/PULL, the type of medication building blocks, supporting resources like List and Communication for specific transactions and fixing the value of specific FHIR elements in applicable profiles, the {{term|actionable}} tag is used. The latter is described more in depth in the following section. Next to that, a summarizing table is provided.<br /> <br /> Note that {{fhir|Resource.meta.profile}}, although present in each building block (see [[FHIR:V1.0_FHIR_IG_R4#Profile_use_and_declaration|the general FHIR IG on ‘Profile use and declaration’]]), SHOULD [https://hl7.org/fhir/r4/resource.html#profile-tags not be used for identification of the building block type] and therefore for differentiating between transactions.<br /> <br /> === Actionable tag ===<br /> To differentiate between sending or serving building blocks that are either of informative nature or of actionable nature, the {{term|actionable}} tag is used. [https://hl7.org/fhir/r4/resource.html#tag Tags] are {{datatype|Coding}} elements present in {{fhir|Resource.meta.tag}} used for workflow management.<br /> <br /> If applicable, the profiles used by a transaction require the use of {{fhir|.meta.tag}} with {{fhir|.system}} = {{term|&lt;nowiki&gt;http://terminology.hl7.org/CodeSystem/common-tags&lt;/nowiki&gt;}} and {{fhir|.code}} = {{term|actionable}} to indicate that the resource is part of a request intended to be acted upon. The absence of this tag indicates that the resource is merely of informative nature.<br /> <br /> It is up to systems to determine how and when the transactions using the {{term|actionable}} tag are handled from a functional perspective. Systems may store the resource including the {{term|actionable}} tag or remove it either upon storing or when the request is acted upon. However, systems SHALL make sure the tag is removed when serving or sending the resource as part of an informative transaction.<br /> <br /> === Summarizing table ===<br /> {| class=&quot;wikitable&quot; <br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | PUSH/PULL<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building blocks<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | {{term|actionable}} tag<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR element value<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Other<br /> |-<br /> | Medication data (Retrieve/Serve)<br /> | PULL<br /> | One or more of all building blocks<br /> | No<br /> |<br /> | <br /> |-<br /> | Medication data (Send/Receive)<br /> | PUSH<br /> | One or more of all building blocks<br /> | No<br /> |<br /> |<br /> |-<br /> | Medication overview (Retrieve/Serve)<br /> | PULL<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication overview (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication prescription (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, DispenseRequest (optional)<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|order}} (for both MedicationAgreement and DispenseRequest building blocks)<br /> | <br /> |-<br /> | Medication prescription processing (Send/Receive)<br /> | PUSH<br /> | AdministrationAgreement, MedicationDispense (optional)<br /> | Yes<br /> | <br /> | <br /> |-<br /> | Proposal dispense request (Send/Receive)<br /> | PUSH<br /> | DispenseRequest<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal dispense request (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to DispenseRequest<br /> |-<br /> | Proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to MedicationAgreement<br /> |}<br /> <br /> = Transactions =<br /> This section describes the FHIR implementation of all transactions listed in [[mp:V3.0.0-beta.2_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’.<br /> &lt;section begin=medmij1 /&gt;<br /> == Medication data (Retrieve/Serve) ==<br /> The retrieve medication data transaction is used by the client to retrieve medication data from a server. The client can retrieve its desired information by searching for specific medication building blocks.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.372_20220630000000 Medication data (PULL)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.373-2022-06-30T000000.html Retrieving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGR<br /> &lt;section end=medmij1 /&gt;<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}|title=CapabilityStatement Retrieve/serve medication data}}<br /> &lt;section begin=medmij2 /&gt;<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.374-2022-06-30T000000.html Serving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain all medication data or specific parts matching various parameters, they issue a retrieve medication data request message. This message uses the HTTP GET method parameterized query against the server's medication FHIR endpoints. These endpoints can be one of the following:<br /> * MedicationRequest<br /> * MedicationDispense<br /> * MedicationStatement<br /> * MedicationAdministration<br /> <br /> The search interaction is performed by an HTTP GET conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query. Multiple request messages may be needed to retrieve all desired information.<br /> <br /> &lt;pre&gt;GET [base]/[type]{?[parameters]}&lt;/pre&gt;<br /> <br /> ==== Search parameters ====<br /> All search parameters listed in the table below SHALL be supported for processing by servers and MAY be supported by clients.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | MP9 search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Description<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Example<br /> &lt;section end=medmij2 /&gt;<br /> |-<br /> | PatientIdentificationNumber<br /> | Search on patient.<br /> | {{fhir|patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;&gt;This search parameter only needs to be supported when patient identification requires the use of search parameters, see [[#Patient_identification|section 2.4]].&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233.<br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> &lt;section begin=medmij3 /&gt;<br /> |-<br /> | Identification<br /> | Search on identifier.<br /> | {{fhir|identifier}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves a MedicationRequest resource with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?identifier=http://example.nl/fhir/NamingSystem/MedicationRequest|999922448&lt;/pre&gt;<br /> |-<br /> | Identification<br /> | Search on the pharmaceutical treatment identifier. <br /> Note: retrieval of all medication resources belonging to one pharmaceutical treatment requires to search on all medication resource types.<br /> | {{fhir|pharmaceutical-treatment-identifier}} &lt;ref name=&quot;custom-searchparameter&quot;&gt;The search parameter consists of a custom FHIR search parameter not represented in the FHIR specification. Note that for {{fhir|MedicationRequest.category}} and {{fhir|MedicationStatement.category}} a core search parameter is available, hence no custom one is needed in those cases.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that are part of a pharmaceutical treatment with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?pharmaceutical-treatment-identifier=http://example.nl/fhir/NamingSystem/pharmaceuticaltreatment|1247848&lt;/pre&gt;<br /> |-<br /> | rowspan=&quot;4&quot; | Type<br /> | rowspan=&quot;4&quot; | Search on type of medication building block. <br /> | rowspan=&quot;4&quot; | {{fhir|category}} &lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block DispenseRequest.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block VariableDosingRegimen.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&lt;/pre&gt;<br /> |-<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&lt;/pre&gt;<br /> Retrieves all MedicationDispense resources that represent the building block AdministrationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&lt;/pre&gt;<br /> |-<br /> | MedicationStatement<br /> | Retrieves all MedicationStatement resources that represent the building block MedicationUse2.<br /> &lt;pre&gt;GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&lt;/pre&gt;<br /> |-<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&lt;/pre&gt;<br /> |-<br /> | MedicationCode<br /> | Search on medication code.<br /> | {{fhir|medication.code}}&lt;ref&gt;[https://www.hl7.org/fhir/r4/search.html#chaining Chained search parameter]: searches the medicationReference required in each building block for its {{fhir|.code}}.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and have Carbasalaatcalcium Sandoz 600 30 as medication.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&lt;/pre&gt;<br /> |-<br /> | PeriodOfUse<br /> | 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.<br /> Whenever a search is done on the MedicationAgreement, VariableDosingRegimen or AdministrationAgreement building blocks it is required to also include the latest stopped building blocks of that kind within each pharmaceutical treatment, even if these have a period of use outside the PeriodOfUse that is being searched on.<br /> | {{fhir|period-of-use}}&lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement&lt;ref&gt;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.&lt;/ref&gt;<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and were in effect from 01-01-2010.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;period-of-use=ge2010-01-01&lt;/pre&gt;<br /> |-<br /> | DispensePeriod <br /> | Returns all medication dispenses within the specified time period.<br /> | {{fhir|whenhandedover}}<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense and were handed over within a 2 year period.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;whenhandedover=ge2010-01-01&amp;whenhandedover=le2011-12-31&lt;/pre&gt;<br /> |-<br /> | AdministrationPeriod <br /> | Returns all medication administrations within the specified time period.<br /> | {{fhir|effective-time}}<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2 and where administration happened on a specific day.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;effective-time=eq2022-01-01&lt;/pre&gt;<br /> |-<br /> | -<br /> | The client may request that the server returns resources related to the search results, in order to reduce the overall network delay of repeated retrievals of related resources.<br /> Supporting the include of the Patient and Medication resources referenced by building blocks is required. Others (Organization, Location, PractitionerRole, Practitioner, RelatedPerson, Observation) are optional. However: all resources referenced per literal reference SHALL be resolvable [[FHIR:V1.0_FHIR_IG_R4#Including_referenced_resources|per the Nictiz IG]].<br /> | {{fhir|&lt;nowiki&gt;_include=[type]:patient&lt;/nowiki&gt;}}<br /> {{fhir|&lt;nowiki&gt;_include=[type]:medication&lt;/nowiki&gt;}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that have Carbasalaatcalcium Sandoz 600 30 as medication and includes the Medication resource in the search results.<br /> &lt;pre&gt;GET [base]/MedicationRequest?medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&amp;_include=MedicationRequest:medication&lt;/pre&gt;<br /> |}<br /> <br /> The following custom search parameters are defined for this transaction:<br /> <br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/pharmaceutical-treatment-identifier|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/category|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/period-of-use|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> <br /> ==== Retrieve all medication data ====<br /> To retrieve all known medication data, a client has to execute the following requests to retrieve all known medication data per building block, including referenced Medication resources:<br /> <br /> &lt;pre&gt;<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&amp;_include=MedicationStatement:medication<br /> GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;_include=MedicationStatement:medication<br /> &lt;/pre&gt;<br /> <br /> === Serve (response message) ===<br /> The server returns an HTTP Status code appropriate to the processing outcome and returns a Bundle, with {{fhir|Bundle.type}} = {{term|searchset}}, including the resources matching the search query medication data. The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |}<br /> &lt;section end=medmij3 /&gt;<br /> == Medication data (Send/Receive) ==<br /> The send medication data transaction is used by the client to send medication data to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.375_20220630000000 Medication data (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.376-2022-06-30T000000.html Sending medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}|title=CapabilityStatement Send/receive medication data}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication data<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because medication data consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below. Because of the informative nature of the transaction, '''no''' [[#Actionable_tag|{{term|actionable}} tags]] shall be present.<br /> <br /> === Receive (response message) ===<br /> The server checks each resource present within the Bundle it receives for the absence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |}<br /> <br /> == Medication overview (Retrieve/Serve) ==<br /> The retrieve medication overview transaction is used by the client to retrieve a medication overview from the server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.388_20220630000000 Medication overview (PULL)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.389-2022-06-30T000000.html Retrieving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOR<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}|title=CapabilityStatement Retrieve/serve medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.390-2022-06-30T000000.html Serving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain a patient's medication overview, they issue a retrieve medication overview request message. This message uses an extended operation on the RESTful API to obtain a medication overview from a server. An operation is needed because the server will formulate the content of the response based on its internal business logic. The medication overview can not easily be described by standardized RESTful requests. <br /> <br /> The client executes a {{Simplifier|http://nictiz.nl/fhir/OperationDefinition/Medication-Overview|nictiz.fhir.nl.r4.medicationprocess9|title=medication-overview operation}} with an HTTP GET command conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query.<br /> <br /> &lt;pre&gt;<br /> GET [base]/$medication-overview<br /> &lt;/pre&gt;<br /> <br /> === Serve (response message) ===<br /> 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.<br /> <br /> The clinical content of the medication overview is defined in the [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-beta.2_Ontwerp_medicatieproces_9_ENG#Medication_overview_and_inference_rules functional specification].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |}<br /> <br /> == Medication overview (Send/Receive) ==<br /> The send medication overview transaction is used by the client to send a medication overview to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.391_20220630000000 Medication overview (PUSH)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.392-2022-06-30T000000.html Sending medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}|title=CapabilityStatement Send/receive medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication overview<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication overview consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> 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.<br /> <br /> The clinical content of the medication overview is defined in the [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-beta.2_Ontwerp_medicatieproces_9_ENG#Medication_overview_and_inference_rules functional specification].<br /> <br /> === Receive (response message) ===<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |}<br /> <br /> == Medication prescription (Send/Receive) ==<br /> The send medication prescription transaction is used by the client to send a request to dispense medication (Dutch: verstrekkingsverzoek) or process modifications to a medication agreement (Dutch: medicatieafspraak) to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.141-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.394_20220630000000 Medication prescription (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.395-2022-06-30T000000.html Sending medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescription|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}|title=CapabilityStatement Send/receive medication prescription}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescription-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}) and optionally a DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below<br /> <br /> The mp-MedicationPrescription-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the MedicationAgreement and DispenseRequest building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|order}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Medication_prescription_processing_.28Send.2FReceive.29|‘Send medication prescription processing’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |}<br /> <br /> == Medication prescription processing (Send/Receive) ==<br /> The send medication prescription processing transaction is used by the client to send data on the processing of a medication agreement (Dutch: medicatieafspraak) and possibly a dispense request (Dutch: verstrekkingsverzoek), in the form of an administration agreement (Dutch: toedieningsafspraak) and optionally a medication dispense (Dutch: medicatieverstrekking).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.143-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.406_20220630000000 Medication prescription processing (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.407-2022-06-30T000000.html Sending data on processing of medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescriptionProcessing|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}|title=CapabilityStatement Send/receive medication prescription processing}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving data on processing of medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because data on processing a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescriptionProcessing-Bundle profile, which contains at least an AdministrationAgreement building block and optionally a MedicationDispense building block. Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-MedicationPrescriptionProcessing-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the AdministrationAgreement and MedicationDispense building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |}<br /> <br /> == Proposal dispense request (Send/Receive) ==<br /> The send proposal dispense request transaction is used by the client to inform the server about a new or modified proposal dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.400_20220630000000 Proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.401-2022-06-30T000000.html Sending proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}|title=CapabilityStatement Send/receive proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal dispense request consists of a DispenseRequest building block along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalDispenseRequest-Bundle profile, which contains one DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalDispenseRequest-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the DispenseRequest building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_dispense_request_.28Send.2FReceive.29|‘Send reply proposal dispense request’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |}<br /> <br /> == Reply proposal dispense request (Send/Receive) ==<br /> The send reply proposal dispense request transaction is used by the client to inform the server about a reply on a proposed dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.403_20220630000000 Reply proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.404-2022-06-30T000000.html Sending reply proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}|title=CapabilityStatement Send/receive reply proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal dispense request consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalDispenseRequest-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalDispenseRequest profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed dispense request that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalDispenseRequest-Bundle profile).<br /> <br /> The mp-ReplyProposalDispenseRequest profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |}<br /> <br /> == Proposal medication agreement (Send/Receive) ==<br /> The send proposal medication agreement transaction is used by the client to inform the server about a new or modified proposal medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.397_20220630000000 Proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.398-2022-06-30T000000.html Sending proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}|title=CapabilityStatement Send/receive proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal medication agreement consists of a MedicationAgreement building block along with supporting resources, a {{term|transaction}} interaction is used.<br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalMedicationAgreement-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalMedicationAgreement-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the MedicationAgreement building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_medication_agreement_.28Send.2FReceive.29|‘Send reply proposal medication agreement’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |}<br /> <br /> == Reply proposal medication agreement (Send/Receive) ==<br /> The send reply proposal medication agreement transaction is used by the client to inform the server about a reply on a proposed medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.445_20220630000000 Reply proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.446-2022-06-30T000000.html Sending reply proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}|title=CapabilityStatement Send/receive reply proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal medication agreement consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalMedicationAgreement-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalMedicationAgreement profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed medication agreement that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalMedicationAgreement-Bundle profile).<br /> <br /> The mp-ReplyProposalMedicationAgreement profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |}<br /> <br /> =Release notes=<br /> Release notes can be found [[mp:V3.0.0-beta.2_releasenotes|here]].<br /> <br /> =Footnotes=<br /> &lt;references/&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=mp:V3.0.0-beta.2_MedicationProcess9_FHIR&diff=206653 2024-03-06T16:08:29Z

<p>Luud Slagter: Updated hyperlinks to beta.2</p> <hr /> <div>{{StartUitgefaseerd|06-03-2024|Zie de [[MP:Medicatieoverdracht_Kickstart|kickstart landingspagina Medicatieproces 9]] voor de actuele versie van de informatiestandaard voor de kickstart.|Consult the [[MP:Medicatieoverdracht_Kickstart|kickstart overview page Medication Process 9]] for the current versions of the information standard for the kickstart.}}<br /> <br /> {{IssueBox|'''&lt;big&gt;This is an archived version. [[MP:Medicatieoverdracht_Kickstart|Consult the kickstart overview page for the current versions]].&lt;/big&gt;'''}}<br /> <br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide Medication Process 9 version {{VersieInfo|mp9|release=V3.0.0-beta.2}} }}<br /> <br /> __TOC__<br /> <br /> = Introduction =<br /> This is the implementation guide (IG) for the information standard Medication Process 9 (MP9) version {{VersieInfo|mp9|release=V3.0.0-beta.2}} using the HL7® FHIR® standard. The MP9 standard is described in [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-beta.2_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.<br /> <br /> 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.<br /> <br /> This IG first describes the boundaries and relationships in place, after which the implementation is described per transaction.<br /> <br /> = Boundaries and relationships =<br /> == Building blocks and profiles ==<br /> <br /> The exchange of data within the MP9 standard version {{VersieInfo|mp9|release=V3.0.0-beta.2}} 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. <br /> <br /> 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.<br /> <br /> Because the way 90 million numbers are exchanged is not compatible with the 2020 publication of zib PharmaceuticalProduct, a fork of the corresponding nl-core profile called 'mp-PharmaceuticalProduct' has been introduced.<br /> <br /> {{NoteBoxNictizR4Package|p1=nictiz.fhir.nl.r4.medicationprocess9|v1={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}|p2=nictiz.fhir.nl.r4.nl-core|v2={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> <br /> 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:<br /> * MP9 version 2.0.0 makes use of version 1.0.0 of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package;<br /> * MP9 version 3.0.0-beta.x makes use of version 2.0.0-beta.x of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package.<br /> <br /> === Medication building blocks ===<br /> <br /> As described above, the main medication building blocks have no dependency on any zib2020 counterparts, resulting in so-called ‘mp’ profiles. Moreover, note that the building block VariableDosingRegimen does not have a zib counterpart, hence it makes sense to include it as an mp profile as well.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |}<br /> <br /> === Supporting building blocks ===<br /> <br /> Additionally, the standard uses several supporting building blocks referenced from the main medication building blocks. All supporting building blocks are part of the [[FHIR:V1.0_FHIR_IG_R4#Functional_definitions|‘nl-core’ package]]&lt;ref&gt;Although the nl-core package is still in beta-status, HL7 Netherlands has validated the profiles mentioned and assigned the status 'STU-NL' for use in the MP9 Kickstart, see [[Media:HL7_Nederland_disclaimer_STU-NL.pdf]]&lt;/ref&gt;.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |}<br /> <br /> Note the following:<br /> * Each occurrence of the zib HealthProfessional is normally represented by '''two''' FHIR resources: an instance of nl-core-HealthProfessional-PractitionerRole and an instance of nl-core-HealthProfessional-Practitioner. Sending systems should only fill the reference to the PractitionerRole instance where relevant. Receiving systems can resolve the reference to the Practitioner resource from that PractitionerRole instance.<br /> * The zib HealthcareProvider is mapped to both a Location and Organization profile. Most often, the Location profile acts as the focal resource, because most references to this zib are concerned about the recording of the physical location where the care to patient/client takes place rather than the organizational information. For the latter, the profile on Organization is used which is referenced using the {{fhir|Location.managingOrganization}} element. Sending systems should only fill the reference to the Location instance where relevant. Incidentally, concepts that are only concerned with organizational information can refer to the Organization instance.<br /> <br /> === Transaction specific profiles ===<br /> <br /> For several transactions, additional profiles are provided. For each transaction the profile relevant is explicitly mentioned in the corresponding subsection.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |}<br /> <br /> ====Bundle profiles====<br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == Mappings between profiles and data set ==<br /> 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.<br /> <br /> 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:<br /> * 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)<br /> ** 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.<br /> ** 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.<br /> * If an element in the functional definition is removed<br /> ** and the element had a zib mapping applied, the zib mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> ** and the element had a mapping applied to the previous version of MP9, that mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> <br /> Moreover, all mappings to earlier versions of MP9 (i.e. versions before the previous version) are entirely removed.<br /> <br /> Following the procedure outlined above thus results in the following:<br /> * 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.<br /> * All incompatible changes made in the latest version with respect to the previous version are marked.<br /> <br /> 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’]].<br /> <br /> 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.<br /> <br /> 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]].<br /> <br /> == Pharmaceutical treatment ==<br /> 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.2_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.<br /> <br /> == Patient identification ==<br /> This implementation guide assumes that the client system is able to make a connection to the right server that contains the patient's information. It does not provide information on finding the right server nor does it provide information about security. Moreover, each transaction is performed in the context of a specific patient, whose context might have been established using the authentication mechanisms described in external specifications such as the MedMij ‘Afsprakenstelsel’ or through the usage of search parameters for patient identification. <br /> <br /> Each server is required to perform filtering based on the patient associated with the context for the request or based on the patient identification search parameters, which is a [https://www.hl7.org/fhir/r4/search.html#chaining chained search parameter] for all resource types except Patient, so only the records associated with the authenticated patient are returned.<br /> <br /> When patient identification requires the use of search parameters, the following search parameters SHALL be supported:<br /> * Patient: {{fhir|identifier}}<br /> * MedicationRequest: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationDispense: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationStatement: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationAdministration: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> <br /> An example of a request that retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233:<br /> <br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> <br /> All request examples in this document do not include patient identification mechanisms. Requesters are assumed to include these if necessary.<br /> <br /> == Resource identification ==<br /> 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}}.<br /> <br /> 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 &lt;code&gt;@root&lt;/code&gt; and &lt;code&gt;@extension&lt;/code&gt; (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.<br /> <br /> 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|release=V3.0.0-beta.2}}}} 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]].<br /> <br /> == Differentiating between transactions ==<br /> All transactions described in this IG use the same medication building blocks in different combinations and settings, making it necessary to differentiate between them. Several mechanisms are used to achieve this. Aside from PUSH/PULL, the type of medication building blocks, supporting resources like List and Communication for specific transactions and fixing the value of specific FHIR elements in applicable profiles, the {{term|actionable}} tag is used. The latter is described more in depth in the following section. Next to that, a summarizing table is provided.<br /> <br /> Note that {{fhir|Resource.meta.profile}}, although present in each building block (see [[FHIR:V1.0_FHIR_IG_R4#Profile_use_and_declaration|the general FHIR IG on ‘Profile use and declaration’]]), SHOULD [https://hl7.org/fhir/r4/resource.html#profile-tags not be used for identification of the building block type] and therefore for differentiating between transactions.<br /> <br /> === Actionable tag ===<br /> To differentiate between sending or serving building blocks that are either of informative nature or of actionable nature, the {{term|actionable}} tag is used. [https://hl7.org/fhir/r4/resource.html#tag Tags] are {{datatype|Coding}} elements present in {{fhir|Resource.meta.tag}} used for workflow management.<br /> <br /> If applicable, the profiles used by a transaction require the use of {{fhir|.meta.tag}} with {{fhir|.system}} = {{term|&lt;nowiki&gt;http://terminology.hl7.org/CodeSystem/common-tags&lt;/nowiki&gt;}} and {{fhir|.code}} = {{term|actionable}} to indicate that the resource is part of a request intended to be acted upon. The absence of this tag indicates that the resource is merely of informative nature.<br /> <br /> It is up to systems to determine how and when the transactions using the {{term|actionable}} tag are handled from a functional perspective. Systems may store the resource including the {{term|actionable}} tag or remove it either upon storing or when the request is acted upon. However, systems SHALL make sure the tag is removed when serving or sending the resource as part of an informative transaction.<br /> <br /> === Summarizing table ===<br /> {| class=&quot;wikitable&quot; <br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | PUSH/PULL<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building blocks<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | {{term|actionable}} tag<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR element value<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Other<br /> |-<br /> | Medication data (Retrieve/Serve)<br /> | PULL<br /> | One or more of all building blocks<br /> | No<br /> |<br /> | <br /> |-<br /> | Medication data (Send/Receive)<br /> | PUSH<br /> | One or more of all building blocks<br /> | No<br /> |<br /> |<br /> |-<br /> | Medication overview (Retrieve/Serve)<br /> | PULL<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication overview (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication prescription (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, DispenseRequest (optional)<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|order}} (for both MedicationAgreement and DispenseRequest building blocks)<br /> | <br /> |-<br /> | Medication prescription processing (Send/Receive)<br /> | PUSH<br /> | AdministrationAgreement, MedicationDispense (optional)<br /> | Yes<br /> | <br /> | <br /> |-<br /> | Proposal dispense request (Send/Receive)<br /> | PUSH<br /> | DispenseRequest<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal dispense request (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to DispenseRequest<br /> |-<br /> | Proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to MedicationAgreement<br /> |}<br /> <br /> = Transactions =<br /> This section describes the FHIR implementation of all transactions listed in [[mp:V3.0.0-beta.2_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’.<br /> &lt;section begin=medmij1 /&gt;<br /> == Medication data (Retrieve/Serve) ==<br /> The retrieve medication data transaction is used by the client to retrieve medication data from a server. The client can retrieve its desired information by searching for specific medication building blocks.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.372_20220630000000 Medication data (PULL)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.373-2022-06-30T000000.html Retrieving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGR<br /> &lt;section end=medmij1 /&gt;<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}|title=CapabilityStatement Retrieve/serve medication data}}<br /> &lt;section begin=medmij2 /&gt;<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.374-2022-06-30T000000.html Serving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain all medication data or specific parts matching various parameters, they issue a retrieve medication data request message. This message uses the HTTP GET method parameterized query against the server's medication FHIR endpoints. These endpoints can be one of the following:<br /> * MedicationRequest<br /> * MedicationDispense<br /> * MedicationStatement<br /> * MedicationAdministration<br /> <br /> The search interaction is performed by an HTTP GET conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query. Multiple request messages may be needed to retrieve all desired information.<br /> <br /> &lt;pre&gt;GET [base]/[type]{?[parameters]}&lt;/pre&gt;<br /> <br /> ==== Search parameters ====<br /> All search parameters listed in the table below SHALL be supported for processing by servers and MAY be supported by clients.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | MP9 search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Description<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Example<br /> &lt;section end=medmij2 /&gt;<br /> |-<br /> | PatientIdentificationNumber<br /> | Search on patient.<br /> | {{fhir|patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;&gt;This search parameter only needs to be supported when patient identification requires the use of search parameters, see [[#Patient_identification|section 2.4]].&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233.<br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> &lt;section begin=medmij3 /&gt;<br /> |-<br /> | Identification<br /> | Search on identifier.<br /> | {{fhir|identifier}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves a MedicationRequest resource with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?identifier=http://example.nl/fhir/NamingSystem/MedicationRequest|999922448&lt;/pre&gt;<br /> |-<br /> | Identification<br /> | Search on the pharmaceutical treatment identifier. <br /> Note: retrieval of all medication resources belonging to one pharmaceutical treatment requires to search on all medication resource types.<br /> | {{fhir|pharmaceutical-treatment-identifier}} &lt;ref name=&quot;custom-searchparameter&quot;&gt;The search parameter consists of a custom FHIR search parameter not represented in the FHIR specification. Note that for {{fhir|MedicationRequest.category}} and {{fhir|MedicationStatement.category}} a core search parameter is available, hence no custom one is needed in those cases.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that are part of a pharmaceutical treatment with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?pharmaceutical-treatment-identifier=http://example.nl/fhir/NamingSystem/pharmaceuticaltreatment|1247848&lt;/pre&gt;<br /> |-<br /> | rowspan=&quot;4&quot; | Type<br /> | rowspan=&quot;4&quot; | Search on type of medication building block. <br /> | rowspan=&quot;4&quot; | {{fhir|category}} &lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block DispenseRequest.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block VariableDosingRegimen.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&lt;/pre&gt;<br /> |-<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&lt;/pre&gt;<br /> Retrieves all MedicationDispense resources that represent the building block AdministrationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&lt;/pre&gt;<br /> |-<br /> | MedicationStatement<br /> | Retrieves all MedicationStatement resources that represent the building block MedicationUse2.<br /> &lt;pre&gt;GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&lt;/pre&gt;<br /> |-<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&lt;/pre&gt;<br /> |-<br /> | MedicationCode<br /> | Search on medication code.<br /> | {{fhir|medication.code}}&lt;ref&gt;[https://www.hl7.org/fhir/r4/search.html#chaining Chained search parameter]: searches the medicationReference required in each building block for its {{fhir|.code}}.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and have Carbasalaatcalcium Sandoz 600 30 as medication.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&lt;/pre&gt;<br /> |-<br /> | PeriodOfUse<br /> | 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.<br /> Whenever a search is done on the MedicationAgreement, VariableDosingRegimen or AdministrationAgreement building blocks it is required to also include the latest stopped building blocks of that kind within each pharmaceutical treatment, even if these have a period of use outside the PeriodOfUse that is being searched on.<br /> | {{fhir|period-of-use}}&lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement&lt;ref&gt;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.&lt;/ref&gt;<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and were in effect from 01-01-2010.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;period-of-use=ge2010-01-01&lt;/pre&gt;<br /> |-<br /> | DispensePeriod <br /> | Returns all medication dispenses within the specified time period.<br /> | {{fhir|whenhandedover}}<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense and were handed over within a 2 year period.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;whenhandedover=ge2010-01-01&amp;whenhandedover=le2011-12-31&lt;/pre&gt;<br /> |-<br /> | AdministrationPeriod <br /> | Returns all medication administrations within the specified time period.<br /> | {{fhir|effective-time}}<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2 and where administration happened on a specific day.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;effective-time=eq2022-01-01&lt;/pre&gt;<br /> |-<br /> | -<br /> | The client may request that the server returns resources related to the search results, in order to reduce the overall network delay of repeated retrievals of related resources.<br /> Supporting the include of the Patient and Medication resources referenced by building blocks is required. Others (Organization, Location, PractitionerRole, Practitioner, RelatedPerson, Observation) are optional. However: all resources referenced per literal reference SHALL be resolvable [[FHIR:V1.0_FHIR_IG_R4#Including_referenced_resources|per the Nictiz IG]].<br /> | {{fhir|&lt;nowiki&gt;_include=[type]:patient&lt;/nowiki&gt;}}<br /> {{fhir|&lt;nowiki&gt;_include=[type]:medication&lt;/nowiki&gt;}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that have Carbasalaatcalcium Sandoz 600 30 as medication and includes the Medication resource in the search results.<br /> &lt;pre&gt;GET [base]/MedicationRequest?medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&amp;_include=MedicationRequest:medication&lt;/pre&gt;<br /> |}<br /> <br /> The following custom search parameters are defined for this transaction:<br /> <br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/pharmaceutical-treatment-identifier|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/category|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/period-of-use|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> <br /> ==== Retrieve all medication data ====<br /> To retrieve all known medication data, a client has to execute the following requests to retrieve all known medication data per building block, including referenced Medication resources:<br /> <br /> &lt;pre&gt;<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&amp;_include=MedicationStatement:medication<br /> GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;_include=MedicationStatement:medication<br /> &lt;/pre&gt;<br /> <br /> === Serve (response message) ===<br /> The server returns an HTTP Status code appropriate to the processing outcome and returns a Bundle, with {{fhir|Bundle.type}} = {{term|searchset}}, including the resources matching the search query medication data. The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |}<br /> &lt;section end=medmij3 /&gt;<br /> == Medication data (Send/Receive) ==<br /> The send medication data transaction is used by the client to send medication data to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.375_20220630000000 Medication data (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.376-2022-06-30T000000.html Sending medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}|title=CapabilityStatement Send/receive medication data}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication data<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because medication data consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below. Because of the informative nature of the transaction, '''no''' [[#Actionable_tag|{{term|actionable}} tags]] shall be present.<br /> <br /> === Receive (response message) ===<br /> The server checks each resource present within the Bundle it receives for the absence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |}<br /> <br /> == Medication overview (Retrieve/Serve) ==<br /> The retrieve medication overview transaction is used by the client to retrieve a medication overview from the server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.388_20220630000000 Medication overview (PULL)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.389-2022-06-30T000000.html Retrieving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOR<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}|title=CapabilityStatement Retrieve/serve medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.390-2022-06-30T000000.html Serving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain a patient's medication overview, they issue a retrieve medication overview request message. This message uses an extended operation on the RESTful API to obtain a medication overview from a server. An operation is needed because the server will formulate the content of the response based on its internal business logic. The medication overview can not easily be described by standardized RESTful requests. <br /> <br /> The client executes a {{Simplifier|http://nictiz.nl/fhir/OperationDefinition/Medication-Overview|nictiz.fhir.nl.r4.medicationprocess9|title=medication-overview operation}} with an HTTP GET command conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query.<br /> <br /> &lt;pre&gt;<br /> GET [base]/$medication-overview<br /> &lt;/pre&gt;<br /> <br /> === Serve (response message) ===<br /> 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.<br /> <br /> The clinical content of the medication overview is defined in the [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-beta.2_Ontwerp_medicatieproces_9_ENG#Medication_overview_and_inference_rules functional specification].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |}<br /> <br /> == Medication overview (Send/Receive) ==<br /> The send medication overview transaction is used by the client to send a medication overview to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.391_20220630000000 Medication overview (PUSH)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.392-2022-06-30T000000.html Sending medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}|title=CapabilityStatement Send/receive medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication overview<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication overview consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> 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.<br /> <br /> The clinical content of the medication overview is defined in the [https://informatiestandaarden.nictiz.nl/wiki/mp:V3.0.0-beta.2_Ontwerp_medicatieproces_9_ENG#Medication_overview_and_inference_rules functional specification].<br /> <br /> === Receive (response message) ===<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |}<br /> <br /> == Medication prescription (Send/Receive) ==<br /> The send medication prescription transaction is used by the client to send a request to dispense medication (Dutch: verstrekkingsverzoek) or process modifications to a medication agreement (Dutch: medicatieafspraak) to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.141-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.394_20220630000000 Medication prescription (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.395-2022-06-30T000000.html Sending medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescription|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}|title=CapabilityStatement Send/receive medication prescription}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescription-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}) and optionally a DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below<br /> <br /> The mp-MedicationPrescription-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the MedicationAgreement and DispenseRequest building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|order}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Medication_prescription_processing_.28Send.2FReceive.29|‘Send medication prescription processing’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |}<br /> <br /> == Medication prescription processing (Send/Receive) ==<br /> The send medication prescription processing transaction is used by the client to send data on the processing of a medication agreement (Dutch: medicatieafspraak) and possibly a dispense request (Dutch: verstrekkingsverzoek), in the form of an administration agreement (Dutch: toedieningsafspraak) and optionally a medication dispense (Dutch: medicatieverstrekking).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.143-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.406_20220630000000 Medication prescription processing (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.407-2022-06-30T000000.html Sending data on processing of medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescriptionProcessing|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}|title=CapabilityStatement Send/receive medication prescription processing}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving data on processing of medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because data on processing a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescriptionProcessing-Bundle profile, which contains at least an AdministrationAgreement building block and optionally a MedicationDispense building block. Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-MedicationPrescriptionProcessing-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the AdministrationAgreement and MedicationDispense building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |}<br /> <br /> == Proposal dispense request (Send/Receive) ==<br /> The send proposal dispense request transaction is used by the client to inform the server about a new or modified proposal dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.400_20220630000000 Proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.401-2022-06-30T000000.html Sending proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}|title=CapabilityStatement Send/receive proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal dispense request consists of a DispenseRequest building block along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalDispenseRequest-Bundle profile, which contains one DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalDispenseRequest-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the DispenseRequest building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_dispense_request_.28Send.2FReceive.29|‘Send reply proposal dispense request’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |}<br /> <br /> == Reply proposal dispense request (Send/Receive) ==<br /> The send reply proposal dispense request transaction is used by the client to inform the server about a reply on a proposed dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.403_20220630000000 Reply proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.404-2022-06-30T000000.html Sending reply proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}|title=CapabilityStatement Send/receive reply proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal dispense request consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalDispenseRequest-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalDispenseRequest profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed dispense request that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalDispenseRequest-Bundle profile).<br /> <br /> The mp-ReplyProposalDispenseRequest profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |}<br /> <br /> == Proposal medication agreement (Send/Receive) ==<br /> The send proposal medication agreement transaction is used by the client to inform the server about a new or modified proposal medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.397_20220630000000 Proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.398-2022-06-30T000000.html Sending proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}|title=CapabilityStatement Send/receive proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal medication agreement consists of a MedicationAgreement building block along with supporting resources, a {{term|transaction}} interaction is used.<br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalMedicationAgreement-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalMedicationAgreement-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the MedicationAgreement building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_medication_agreement_.28Send.2FReceive.29|‘Send reply proposal medication agreement’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |}<br /> <br /> == Reply proposal medication agreement (Send/Receive) ==<br /> The send reply proposal medication agreement transaction is used by the client to inform the server about a reply on a proposed medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.445_20220630000000 Reply proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.446-2022-06-30T000000.html Sending reply proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}|title=CapabilityStatement Send/receive reply proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal medication agreement consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalMedicationAgreement-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalMedicationAgreement profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed medication agreement that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalMedicationAgreement-Bundle profile).<br /> <br /> The mp-ReplyProposalMedicationAgreement profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0-beta.2}}}}<br /> |}<br /> <br /> =Release notes=<br /> Release notes can be found [[mp:V3.0.0-beta.2_releasenotes|here]].<br /> <br /> =Footnotes=<br /> &lt;references/&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=Sjabloon:MpFhirSendTransaction&diff=206652 2024-03-06T16:07:04Z

<p>Luud Slagter: Updated version of FHIR IG</p> <hr /> <div>A [https://www.hl7.org/fhir/r4/http.html#transaction {{term|transaction}} interaction] allows for sending a Bundle with a set of resources in a single interaction and makes it possible to [[FHIR:V1.0_FHIR_IG_R4#Including_.22secondary.22_resources_when_sending_information|include referenced secondary resources]]. The interaction is performed by an HTTP POST command as shown:<br /> <br /> &lt;pre&gt;POST [base]&lt;/pre&gt;<br /> <br /> The body of the POST submission is a Bundle with {{fhir|Bundle.type}} = {{term|transaction}}. Each entry carries request details ({{fhir|Bundle.entry.request}}) that provides the HTTP method of the action to be executed. Usually, this will be POST, even for informative 'secondary' resources.<br /> &lt;noinclude&gt;<br /> = Gemeenschappelijke tekst over FHIR Transaction =<br /> Gebruikt binnen het MP9 2.0.0 FHIR TO en latere versies<br /> &lt;/noinclude&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=Sjabloon:MpFhirReceiveTransaction&diff=206651 2024-03-06T16:06:34Z

<p>Luud Slagter: Updated version of FHIR IG</p> <hr /> <div>The server returns an HTTP Status code appropriate to the processing outcome. If the transaction is successful, the server returns a Bundle with {{fhir|Bundle.type}} = {{term|transaction-response}}, that contains one entry for each entry in the request, in the same order, with the outcome of processing the entry. Included ‘secondary resources’ are handled [[FHIR:V1.0_FHIR_IG_R4#Including_.22secondary.22_resources_when_sending_information|following the Nictiz IG]].<br /> <br /> If the transaction fails, the server returns an OperationOutcome with one or multiple {{fhir|.issue}} elements filled with information, as detailed as possible, that describes why the transaction failed and which resource and/or request caused this.<br /> &lt;noinclude&gt;<br /> = Gemeenschappelijke tekst over FHIR Transaction Receiving =<br /> Gebruikt binnen het MP9 2.0.0 FHIR TO en latere versies<br /> &lt;/noinclude&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=Sjabloon:VersieInfo&diff=206650 2024-03-06T15:55:34Z

<p>Luud Slagter: Added V3.0.0-beta.2 for mp</p> <hr /> <div>{{#switch: {{{namespace|{{NAMESPACE}}}}}:{{{release|{{ROOTPAGENAME}}}}}<br /> <br /> | MedMij:V2019.01 = {{#switch: {{{1}}}<br /> | BgZ = 2.2.2<br /> | Laboratoriumresultaten = 1.2.2<br /> | Medicatieproces = 9.0.7<br /> | MedicatieprocesVerstrekkingenvertaling = 9.A.1<br /> | AllergieIntolerantie1 = 1.2.2<br /> | AllergieIntolerantie = 2.1.2<br /> | AllergieIntolerantieVertaling = 1.A.15<br /> | eAfspraak = 1.2.2<br /> | Zelfmetingen = 1.3.2<br /> | PDFA = 2.1.2<br /> | PDFA1 = 1.3.2<br /> | Huisartsgegevens = 1.2.2<br /> | BgGGZ = 1.2.2<br /> | BgLZ = 1.1.2<br /> | Beelden = 1.1.2<br /> | Vragenlijsten = 1.1.2<br /> | package = 1.3.19<br /> | nictiz.fhir.nl.stu3.zib2017 = 1.3.19<br /> | Editie = 2019.01<br /> }}<br /> <br /> | MedMij:V2020.01 = {{#switch: {{{1}}}<br /> | BgZ = 3.1.18<br /> | Laboratoriumresultaten = 2.0.36<br /> | Medicatieproces = 9.0.7<br /> | MedicatieprocesVerstrekkingenvertaling = 9.A.1<br /> | AllergieIntolerantie1 = 2.0.35<br /> | AllergieIntolerantie = 3.0.35<br /> | AllergieIntolerantieVertaling = 2.A.14<br /> | eAfspraak = 2.0.35<br /> | Zelfmetingen = 2.0.36<br /> | PDFA = 3.0.37<br /> | PDFA1 = 3.0.37<br /> | Huisartsgegevens = 2.0.36<br /> | BgGGZ = 2.0.37<br /> | BgLZ = 2.0.24<br /> | Beelden = 2.0.35<br /> | Vragenlijsten = 2.0.37<br /> | Vragenlijsten1 = 1.0.37<br /> | Geboortezorg = 1.0.2<br /> | package = 2.2.18<br /> | nictiz.fhir.nl.stu3.zib2017 = 2.2.18<br /> | nictiz.fhir.nl.stu3.eafspraak = 1.0.6<br /> | nictiz.fhir.nl.stu3.images = 1.0.3<br /> | nictiz.fhir.nl.stu3.questionnaires = 2.0.8<br /> | nictiz.fhir.nl.stu3.bgz = 1.1.1<br /> | Editie = 2020.01<br /> }}<br /> <br /> | MedMij:V2020.02 = {{#switch: {{{1}}}<br /> | BgLZ = 3.1.17<br /> | package = 2.2.18<br /> | nictiz.fhir.nl.stu3.zib2017 = 2.2.18<br /> | Editie = 2020.02<br /> }}<br /> <br /> | MedMij:V6 = {{#switch: {{{1}}}<br /> | Dossierwijzigingsverzoek = 1.0.13<br /> | Vaccinatie-Immunisatie = 1.0.11<br /> | MedMij_FHIR_IG_R4 = 1.0.4<br /> | MedMij_FunctioneelOntwerp = 1.0.1<br /> | Kwalificatie = 1.0.3<br /> | package = 0.8.0-beta.1<br /> | nictiz.fhir.nl.r4.zib2020 = 0.8.0-beta.1<br /> | nictiz.fhir.nl.r4.nl-core = 0.8.0-beta.1<br /> | nictiz.fhir.nl.r4.patientcorrections = 1.0.6<br /> | nictiz.fhir.nl.r4.vaccinationimmunization = 1.0.3<br /> | nictiz.fhir.nl.r4.immunization = 1.0.3<br /> | Editie = 6.1.3<br /> }}<br /> <br /> | MedMij:IG:V1 = {{#switch: {{{1}}}<br /> | MedMij_FHIR_IG_R4 = 1.0.4<br /> }}<br /> <br /> | MedMij:FO:V1 = {{#switch: {{{1}}}<br /> | MedMij_FunctioneelOntwerp = 1.0.1<br /> }}<br /> <br /> | MedMij:Kwalificatie:V1 = {{#switch: {{{1}}}<br /> | MedMij_Kwalificatie = 1.0.3<br /> }}<br /> <br /> | FHIR:V1.0 = {{#switch: {{{1}}}<br /> | FHIR_IG_R4 = 1.0.3<br /> }}<br /> <br /> | mp:V9.1 = {{#switch: {{{1}}}<br /> | mp = 9.1<br /> | Medicatieproces = 9.1.0<br /> | MedicatieprocesVerstrekkingenvertaling = 9.A.5<br /> | package = 2.0.0<br /> | nictiz.fhir.nl.stu3.zib2017 = 2.0.0<br /> | nictiz.fhir.nl.stu3.medicationprocess= 9.1.0-beta<br /> }}<br /> <br /> | mp:V2.0.0 = {{#switch: {{{1}}}<br /> | mp9 = 2.0.0<br /> | nictiz.fhir.nl.r4.zib2020 = 0.5.0-beta1<br /> | nictiz.fhir.nl.r4.nl-core = 0.5.0-beta1<br /> | nictiz.fhir.nl.r4.medicationprocess9 = 1.0.0<br /> }}<br /> <br /> | mp:V3.0.0-beta.1 = {{#switch: {{{1}}}<br /> | mp9 = 3.0.0-beta.1<br /> | nictiz.fhir.nl.r4.zib2020 = 0.8.0-beta.1<br /> | nictiz.fhir.nl.r4.nl-core = 0.8.0-beta.1<br /> | nictiz.fhir.nl.r4.medicationprocess9 = 2.0.0-beta.1<br /> }}<br /> <br /> | mp:V3.0.0-beta.2 = {{#switch: {{{1}}}<br /> | mp9 = 3.0.0-beta.2<br /> | nictiz.fhir.nl.r4.zib2020 = 0.10.0-beta.1<br /> | nictiz.fhir.nl.r4.nl-core = 0.10.0-beta.1<br /> | nictiz.fhir.nl.r4.medicationprocess9 = 2.0.0-beta.2<br /> }}<br /> <br /> | mp:V3.0.0 = {{#switch: {{{1}}}<br /> | mp9 = 3.0.0-beta.3<br /> | nictiz.fhir.nl.r4.zib2020 = 0.10.0-beta.1<br /> | nictiz.fhir.nl.r4.nl-core = 0.10.0-beta.1<br /> | nictiz.fhir.nl.r4.medicationprocess9 = 2.0.0-beta.3<br /> }}<br /> <br /> | Lab:V3.0.0 = {{#switch: {{{1}}}<br /> | nictiz.fhir.nl.r4.zib2020 = 0.6.0-beta.2<br /> | nictiz.fhir.nl.r4.nl-core = 0.6.0-beta.2<br /> | nictiz.fhir.nl.r4.labexchange = 3.0.0-beta.1<br /> }}<br /> <br /> | vpk:V4.0 = {{#switch: {{{1}}}<br /> | eOverdracht = 4.0-rc.23<br /> | nictiz.fhir.nl.stu3.zib2017 = 2.2.18<br /> | nictiz.fhir.nl.stu3.eoverdracht = 1.0.0-rc.23<br /> | nictiz.fhir.nl.stu3.zib2020-preadopt = 0.1.3<br /> }}<br /> <br /> | hg:V1 = {{#switch: {{{1}}}<br /> | ELZ = 0.2.0-beta.1<br /> | BITS = https://bits.nictiz.nl/projects/ELZ<br /> | nictiz.fhir.nl.r4.elz = 0.2.0-beta.1<br /> }}<br /> <br /> | Gebz:V1 = {{#switch: {{{1}}}<br /> | MedMij_Integrale_Zwangerschapskaart = 0.1.0-beta.1<br /> | nictiz.fhir.nl.stu3.geboortezorg = 1.2.0<br /> }}<br /> <br /> | cio:V2.0.0-beta.1 = {{#switch: {{{1}}}<br /> | CiO = 2.0.0-beta.1<br /> | BITS = https://bits.nictiz.nl/projects/CIO<br /> | nictiz.fhir.nl.r4.nl-core = 0.9.0-beta.1<br /> | nictiz.fhir.nl.r4.medicationprocess9 = 2.0.0-beta.1<br /> | nictiz.fhir.nl.r4.cio = 1.0.0-beta.1<br /> }}<br /> <br /> | cio:V2.0.0-beta.2 = {{#switch: {{{1}}}<br /> | CiO = 2.0.0-beta.2<br /> | BITS = https://bits.nictiz.nl/projects/CIO<br /> | nictiz.fhir.nl.r4.nl-core = 0.10.0-beta.1<br /> | nictiz.fhir.nl.r4.cio = 1.0.0-beta.2<br /> }}<br /> <br /> | bbs:V1.0.0 = {{#switch: {{{1}}}<br /> | BBS = 1.0.0-alfa.1<br /> | BITS = https://bits.nictiz.nl/projects/BBS<br /> }}<br /> <br /> | bbs:V1.0.0b = {{#switch: {{{1}}}<br /> | BBS = 1.0.0-alpha.2<br /> | BITS = https://bits.nictiz.nl/projects/BBS<br /> }}<br /> <br /> | BgZ:V1.1.0 = {{#switch: {{{1}}}<br /> | BgZ = 1.1.0-alfa.1<br /> | BITS = https://bits.nictiz.nl/projects/MSZ<br /> }}<br /> <br /> | jgz:V7 = {{#switch: {{{1}}}<br /> | JGZ = 7.1.2<br /> | BITS = https://bits.nictiz.nl/projects/JGZ<br /> }}<br /> <br /> }}&lt;noinclude&gt;<br /> == Doel ==<br /> <br /> Er zijn allerlei situaties waarin de specifieke versie van een component een bepaalde versie van een ander component gebruikt, bijvoorbeeld een versie van een informatiestandaard die een bepaalde versie van een FHIR-package nodig heeft. Dit sjabloon is bedoeld om dit soort versie-afhankelijkheden te leggen.<br /> <br /> == Gebruik ==<br /> <br /> Dit sjabloon koppelt simpelweg de versie (om legacy-redenen 'release' genoemd) van de gebruikende component plus de naam van de gebruikte component aan de versienummer van deze gebruikte component.<br /> <br /> Het sjabloon kan op pagina's ingezet worden met:<br /> &lt;pre&gt;{{VersieInfo|[component](|release=[release])(|namespace=[namespace])}}&lt;/pre&gt;<br /> * &lt;code&gt;component&lt;/code&gt;: de naam van de ''gebruikte'' component, dus bv. de naam van het FHIR-package dat een standaard gebruikt.<br /> * &lt;code&gt;release&lt;/code&gt;: de versie(string) van de ''gebruikende'' component, dus bv. de versie van een informatiestandaard die het FHIR-package gebruikt. Als deze parameter wordt weggelaten, wordt als default de [https://www.mediawiki.org/wiki/Help:Magic_words#Page_names ROOTPAGENAME] van de (aanroepende) pagina gebruikt.<br /> * &lt;code&gt;namespace&lt;/code&gt;: als de gebruikende ''pagina'' zich in een andere namespace bevindt dan de namespace geregistreerd in dit sjabloon kan hier de namespace expliciet vermeld worden. Dit is vooral relevant voor verwijzingen waarin het versienummer wordt opgenomen.<br /> <br /> Dit wordt dan vervangen door het bijbehorende versienummer. De naam van 'component' dient uiteraard exact overeen te komen met de naam die in dit sjabloon staat.<br /> <br /> Bijvoorbeeld: binnen MedMij worden versienummers van individuele informatiestandaarden gekoppeld aan een bepaalde MedMij-release. Bv. de BgZ heeft binnen de MedMij-release &quot;V2019.01&quot; het versienummer 2.1.13. Dit kan opgezocht worden via:<br /> <br /> &lt;pre&gt;{{VersieInfo|BgZ|release=V2019.01}}&lt;/pre&gt;<br /> <br /> === Onderhoud versienummers ===<br /> <br /> Het sjabloon bestaat uit een geneste switch; de eerste tak kijkt naar de Release (de eerste parameter), de tweede naar de naam van de gezochte component. Deze informatie staat bovenaan de pagina wanneer deze bewerkt wordt.<br /> <br /> Wanneer het nodig is om een nieuwe release toe te voegen, volstaat het om het volgende stuk toe te voegen:<br /> &lt;pre&gt;<br /> | NAMESPACE:&lt;release&gt; = {{#switch: {{{2}}}<br /> | &lt;component1&gt; = x.x.x<br /> | &lt;component2&gt; = x.x.x<br /> ...<br /> | &lt;componentN&gt; = x.x.x<br /> <br /> }}<br /> &lt;/pre&gt;<br /> === Afwijkende versienummers in systeemrolcodes ===<br /> <br /> In sommige informatiestandaarden zijn er systeemrolcodes met een versie die afwijkt van die van de standaard als geheel. Typisch gebeurt dit wanneer er een use case is bijgekomen in een standaard; de major-versie wordt opgehoogd, maar de systeemrollen in de oorspronkelijke use case blijven de oorspronkelijke versie gebruiken (zolang er nog geen reden is om over te gaan naar een nieuwe versie).<br /> <br /> Er is gekozen voor een pragmatische aanpak in dit soort gevallen door simpelweg een tweede entry toe te voegen voor de afwijkende major-versie; de standaard &quot;PDF/A&quot; staat bijvoorbeeld twee keer in het lijstje, een keer als &quot;PDFA&quot; en een keer als &quot;PDFA1&quot; voor de oudere systeemrolcodes.<br /> &lt;/noinclude&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=mp:V3.0.0-beta.2_MedicationProcess9_FHIR&diff=206649 2024-03-06T15:51:45Z

<p>Luud Slagter: Updated TO to latest beta.2 version</p> <hr /> <div>__NOINDEX__<br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide Medication Process 9 version {{VersieInfo|mp9|release=V3.0.0}} }}<br /> <br /> __TOC__<br /> <br /> = Introduction =<br /> 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.<br /> <br /> 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.<br /> <br /> This IG first describes the boundaries and relationships in place, after which the implementation is described per transaction.<br /> <br /> = Boundaries and relationships =<br /> == Building blocks and profiles ==<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> Because the way 90 million numbers are exchanged is not compatible with the 2020 publication of zib PharmaceuticalProduct, a fork of the corresponding nl-core profile called 'mp-PharmaceuticalProduct' has been introduced.<br /> <br /> {{NoteBoxNictizR4Package|p1=nictiz.fhir.nl.r4.medicationprocess9|v1={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|p2=nictiz.fhir.nl.r4.nl-core|v2={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> <br /> 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:<br /> * MP9 version 2.0.0 makes use of version 1.0.0 of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package;<br /> * MP9 version 3.0.0-beta.x makes use of version 2.0.0-beta.x of the nictiz.fhir.nl.r4.medicationprocess9 FHIR package.<br /> <br /> === Medication building blocks ===<br /> <br /> As described above, the main medication building blocks have no dependency on any zib2020 counterparts, resulting in so-called ‘mp’ profiles. Moreover, note that the building block VariableDosingRegimen does not have a zib counterpart, hence it makes sense to include it as an mp profile as well.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |}<br /> <br /> === Supporting building blocks ===<br /> <br /> Additionally, the standard uses several supporting building blocks referenced from the main medication building blocks. All supporting building blocks are part of the [[FHIR:V1.0_FHIR_IG_R4#Functional_definitions|‘nl-core’ package]]&lt;ref&gt;Although the nl-core package is still in beta-status, HL7 Netherlands has validated the profiles mentioned and assigned the status 'STU-NL' for use in the MP9 Kickstart, see [[Media:HL7_Nederland_disclaimer_STU-NL.pdf]]&lt;/ref&gt;.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> Note the following:<br /> * Each occurrence of the zib HealthProfessional is normally represented by '''two''' FHIR resources: an instance of nl-core-HealthProfessional-PractitionerRole and an instance of nl-core-HealthProfessional-Practitioner. Sending systems should only fill the reference to the PractitionerRole instance where relevant. Receiving systems can resolve the reference to the Practitioner resource from that PractitionerRole instance.<br /> * The zib HealthcareProvider is mapped to both a Location and Organization profile. Most often, the Location profile acts as the focal resource, because most references to this zib are concerned about the recording of the physical location where the care to patient/client takes place rather than the organizational information. For the latter, the profile on Organization is used which is referenced using the {{fhir|Location.managingOrganization}} element. Sending systems should only fill the reference to the Location instance where relevant. Incidentally, concepts that are only concerned with organizational information can refer to the Organization instance.<br /> <br /> === Transaction specific profiles ===<br /> <br /> For several transactions, additional profiles are provided. For each transaction the profile relevant is explicitly mentioned in the corresponding subsection.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |}<br /> <br /> ====Bundle profiles====<br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == Mappings between profiles and data set ==<br /> 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.<br /> <br /> 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:<br /> * 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)<br /> ** 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.<br /> ** 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.<br /> * If an element in the functional definition is removed<br /> ** and the element had a zib mapping applied, the zib mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> ** and the element had a mapping applied to the previous version of MP9, that mapping gets a suffix {{term|[DEPRECATED]}}, and all other profiling characteristics are removed.<br /> <br /> Moreover, all mappings to earlier versions of MP9 (i.e. versions before the previous version) are entirely removed.<br /> <br /> Following the procedure outlined above thus results in the following:<br /> * 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.<br /> * All incompatible changes made in the latest version with respect to the previous version are marked.<br /> <br /> 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’]].<br /> <br /> 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.<br /> <br /> 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]].<br /> <br /> == Pharmaceutical treatment ==<br /> 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.<br /> <br /> == Patient identification ==<br /> This implementation guide assumes that the client system is able to make a connection to the right server that contains the patient's information. It does not provide information on finding the right server nor does it provide information about security. Moreover, each transaction is performed in the context of a specific patient, whose context might have been established using the authentication mechanisms described in external specifications such as the MedMij ‘Afsprakenstelsel’ or through the usage of search parameters for patient identification. <br /> <br /> Each server is required to perform filtering based on the patient associated with the context for the request or based on the patient identification search parameters, which is a [https://www.hl7.org/fhir/r4/search.html#chaining chained search parameter] for all resource types except Patient, so only the records associated with the authenticated patient are returned.<br /> <br /> When patient identification requires the use of search parameters, the following search parameters SHALL be supported:<br /> * Patient: {{fhir|identifier}}<br /> * MedicationRequest: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationDispense: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationStatement: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> * MedicationAdministration: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> <br /> An example of a request that retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233:<br /> <br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> <br /> All request examples in this document do not include patient identification mechanisms. Requesters are assumed to include these if necessary.<br /> <br /> == Resource identification ==<br /> 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}}.<br /> <br /> 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 &lt;code&gt;@root&lt;/code&gt; and &lt;code&gt;@extension&lt;/code&gt; (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.<br /> <br /> 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|release=V3.0.0}}}} 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]].<br /> <br /> == Differentiating between transactions ==<br /> All transactions described in this IG use the same medication building blocks in different combinations and settings, making it necessary to differentiate between them. Several mechanisms are used to achieve this. Aside from PUSH/PULL, the type of medication building blocks, supporting resources like List and Communication for specific transactions and fixing the value of specific FHIR elements in applicable profiles, the {{term|actionable}} tag is used. The latter is described more in depth in the following section. Next to that, a summarizing table is provided.<br /> <br /> Note that {{fhir|Resource.meta.profile}}, although present in each building block (see [[FHIR:V1.0_FHIR_IG_R4#Profile_use_and_declaration|the general FHIR IG on ‘Profile use and declaration’]]), SHOULD [https://hl7.org/fhir/r4/resource.html#profile-tags not be used for identification of the building block type] and therefore for differentiating between transactions.<br /> <br /> === Actionable tag ===<br /> To differentiate between sending or serving building blocks that are either of informative nature or of actionable nature, the {{term|actionable}} tag is used. [https://hl7.org/fhir/r4/resource.html#tag Tags] are {{datatype|Coding}} elements present in {{fhir|Resource.meta.tag}} used for workflow management.<br /> <br /> If applicable, the profiles used by a transaction require the use of {{fhir|.meta.tag}} with {{fhir|.system}} = {{term|&lt;nowiki&gt;http://terminology.hl7.org/CodeSystem/common-tags&lt;/nowiki&gt;}} and {{fhir|.code}} = {{term|actionable}} to indicate that the resource is part of a request intended to be acted upon. The absence of this tag indicates that the resource is merely of informative nature.<br /> <br /> It is up to systems to determine how and when the transactions using the {{term|actionable}} tag are handled from a functional perspective. Systems may store the resource including the {{term|actionable}} tag or remove it either upon storing or when the request is acted upon. However, systems SHALL make sure the tag is removed when serving or sending the resource as part of an informative transaction.<br /> <br /> === Summarizing table ===<br /> {| class=&quot;wikitable&quot; <br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Transaction<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | PUSH/PULL<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building blocks<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | {{term|actionable}} tag<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR element value<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Other<br /> |-<br /> | Medication data (Retrieve/Serve)<br /> | PULL<br /> | One or more of all building blocks<br /> | No<br /> |<br /> | <br /> |-<br /> | Medication data (Send/Receive)<br /> | PUSH<br /> | One or more of all building blocks<br /> | No<br /> |<br /> |<br /> |-<br /> | Medication overview (Retrieve/Serve)<br /> | PULL<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication overview (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, AdministrationAgreement, MedicationUse<br /> | No<br /> |<br /> | Includes MedicationOverview List resource in Bundle<br /> |-<br /> | Medication prescription (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement, DispenseRequest (optional)<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|order}} (for both MedicationAgreement and DispenseRequest building blocks)<br /> | <br /> |-<br /> | Medication prescription processing (Send/Receive)<br /> | PUSH<br /> | AdministrationAgreement, MedicationDispense (optional)<br /> | Yes<br /> | <br /> | <br /> |-<br /> | Proposal dispense request (Send/Receive)<br /> | PUSH<br /> | DispenseRequest<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal dispense request (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to DispenseRequest<br /> |-<br /> | Proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | MedicationAgreement<br /> | Yes<br /> | {{fhir|MedicationRequest.intent}} = {{term|plan}}<br /> | <br /> |-<br /> | Reply proposal medication agreement (Send/Receive)<br /> | PUSH<br /> | <br /> | Yes<br /> | <br /> | Communication resource with reference to MedicationAgreement<br /> |}<br /> <br /> = Transactions =<br /> 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’.<br /> &lt;section begin=medmij1 /&gt;<br /> == Medication data (Retrieve/Serve) ==<br /> The retrieve medication data transaction is used by the client to retrieve medication data from a server. The client can retrieve its desired information by searching for specific medication building blocks.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.372_20220630000000 Medication data (PULL)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.373-2022-06-30T000000.html Retrieving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGR<br /> &lt;section end=medmij1 /&gt;<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Retrieve/serve medication data}}<br /> &lt;section begin=medmij2 /&gt;<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.374-2022-06-30T000000.html Serving medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain all medication data or specific parts matching various parameters, they issue a retrieve medication data request message. This message uses the HTTP GET method parameterized query against the server's medication FHIR endpoints. These endpoints can be one of the following:<br /> * MedicationRequest<br /> * MedicationDispense<br /> * MedicationStatement<br /> * MedicationAdministration<br /> <br /> The search interaction is performed by an HTTP GET conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query. Multiple request messages may be needed to retrieve all desired information.<br /> <br /> &lt;pre&gt;GET [base]/[type]{?[parameters]}&lt;/pre&gt;<br /> <br /> ==== Search parameters ====<br /> All search parameters listed in the table below SHALL be supported for processing by servers and MAY be supported by clients.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | MP9 search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Description<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Example<br /> &lt;section end=medmij2 /&gt;<br /> |-<br /> | PatientIdentificationNumber<br /> | Search on patient.<br /> | {{fhir|patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;&gt;This search parameter only needs to be supported when patient identification requires the use of search parameters, see [[#Patient_identification|section 2.4]].&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources of a patient with a fake BSN of 11122233.<br /> &lt;pre&gt;GET [base]/MedicationRequest?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> &lt;section begin=medmij3 /&gt;<br /> |-<br /> | Identification<br /> | Search on identifier.<br /> | {{fhir|identifier}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves a MedicationRequest resource with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?identifier=http://example.nl/fhir/NamingSystem/MedicationRequest|999922448&lt;/pre&gt;<br /> |-<br /> | Identification<br /> | Search on the pharmaceutical treatment identifier. <br /> Note: retrieval of all medication resources belonging to one pharmaceutical treatment requires to search on all medication resource types.<br /> | {{fhir|pharmaceutical-treatment-identifier}} &lt;ref name=&quot;custom-searchparameter&quot;&gt;The search parameter consists of a custom FHIR search parameter not represented in the FHIR specification. Note that for {{fhir|MedicationRequest.category}} and {{fhir|MedicationStatement.category}} a core search parameter is available, hence no custom one is needed in those cases.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that are part of a pharmaceutical treatment with a specific identifier.<br /> &lt;pre&gt;GET [base]/MedicationRequest?pharmaceutical-treatment-identifier=http://example.nl/fhir/NamingSystem/pharmaceuticaltreatment|1247848&lt;/pre&gt;<br /> |-<br /> | rowspan=&quot;4&quot; | Type<br /> | rowspan=&quot;4&quot; | Search on type of medication building block. <br /> | rowspan=&quot;4&quot; | {{fhir|category}} &lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block DispenseRequest.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&lt;/pre&gt;<br /> Retrieves all MedicationRequest resources that represent the building block VariableDosingRegimen.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&lt;/pre&gt;<br /> |-<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&lt;/pre&gt;<br /> Retrieves all MedicationDispense resources that represent the building block AdministrationAgreement.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&lt;/pre&gt;<br /> |-<br /> | MedicationStatement<br /> | Retrieves all MedicationStatement resources that represent the building block MedicationUse2.<br /> &lt;pre&gt;GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&lt;/pre&gt;<br /> |-<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&lt;/pre&gt;<br /> |-<br /> | MedicationCode<br /> | Search on medication code.<br /> | {{fhir|medication.code}}&lt;ref&gt;[https://www.hl7.org/fhir/r4/search.html#chaining Chained search parameter]: searches the medicationReference required in each building block for its {{fhir|.code}}.&lt;/ref&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and have Carbasalaatcalcium Sandoz 600 30 as medication.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&lt;/pre&gt;<br /> |-<br /> | PeriodOfUse<br /> | 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.<br /> Whenever a search is done on the MedicationAgreement, VariableDosingRegimen or AdministrationAgreement building blocks it is required to also include the latest stopped building blocks of that kind within each pharmaceutical treatment, even if these have a period of use outside the PeriodOfUse that is being searched on.<br /> | {{fhir|period-of-use}}&lt;ref name=&quot;custom-searchparameter&quot;/&gt;<br /> | MedicationRequest, MedicationDispense, MedicationStatement&lt;ref&gt;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.&lt;/ref&gt;<br /> | Retrieves all MedicationRequest resources that represent the building block MedicationAgreement and were in effect from 01-01-2010.<br /> &lt;pre&gt;GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;period-of-use=ge2010-01-01&lt;/pre&gt;<br /> |-<br /> | DispensePeriod <br /> | Returns all medication dispenses within the specified time period.<br /> | {{fhir|whenhandedover}}<br /> | MedicationDispense<br /> | Retrieves all MedicationDispense resources that represent the building block MedicationDispense and were handed over within a 2 year period.<br /> &lt;pre&gt;GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;whenhandedover=ge2010-01-01&amp;whenhandedover=le2011-12-31&lt;/pre&gt;<br /> |-<br /> | AdministrationPeriod <br /> | Returns all medication administrations within the specified time period.<br /> | {{fhir|effective-time}}<br /> | MedicationAdministration<br /> | Retrieves all MedicationAdministration resources that represent the building block MedicationAdministration2 and where administration happened on a specific day.<br /> &lt;pre&gt;GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;effective-time=eq2022-01-01&lt;/pre&gt;<br /> |-<br /> | -<br /> | The client may request that the server returns resources related to the search results, in order to reduce the overall network delay of repeated retrievals of related resources.<br /> Supporting the include of the Patient and Medication resources referenced by building blocks is required. Others (Organization, Location, PractitionerRole, Practitioner, RelatedPerson, Observation) are optional. However: all resources referenced per literal reference SHALL be resolvable [[FHIR:V1.0_FHIR_IG_R4#Including_referenced_resources|per the Nictiz IG]].<br /> | {{fhir|&lt;nowiki&gt;_include=[type]:patient&lt;/nowiki&gt;}}<br /> {{fhir|&lt;nowiki&gt;_include=[type]:medication&lt;/nowiki&gt;}}<br /> | MedicationRequest, MedicationDispense, MedicationStatement, MedicationAdministration<br /> | Retrieves all MedicationRequest resources that have Carbasalaatcalcium Sandoz 600 30 as medication and includes the Medication resource in the search results.<br /> &lt;pre&gt;GET [base]/MedicationRequest?medication.code=urn:oid:2.16.840.1.113883.2.4.4.8|13610554&amp;_include=MedicationRequest:medication&lt;/pre&gt;<br /> |}<br /> <br /> The following custom search parameters are defined for this transaction:<br /> <br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/pharmaceutical-treatment-identifier|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/category|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/period-of-use|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> <br /> ==== Retrieve all medication data ====<br /> To retrieve all known medication data, a client has to execute the following requests to retrieve all known medication data per building block, including referenced Medication resources:<br /> <br /> &lt;pre&gt;<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|33633005&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|52711000146108&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationRequest?category=http://snomed.info/sct|395067002&amp;_include=MedicationRequest:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|373784005&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&amp;_include=MedicationDispense:medication<br /> GET [base]/MedicationStatement?category=http://snomed.info/sct|422979000&amp;_include=MedicationStatement:medication<br /> GET [base]/MedicationAdministration?category=http://snomed.info/sct|18629005&amp;_include=MedicationStatement:medication<br /> &lt;/pre&gt;<br /> <br /> === Serve (response message) ===<br /> The server returns an HTTP Status code appropriate to the processing outcome and returns a Bundle, with {{fhir|Bundle.type}} = {{term|searchset}}, including the resources matching the search query medication data. The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> &lt;section end=medmij3 /&gt;<br /> == Medication data (Send/Receive) ==<br /> The send medication data transaction is used by the client to send medication data to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.139-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.375_20220630000000 Medication data (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.376-2022-06-30T000000.html Sending medication data]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication data}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication data<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MGO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because medication data consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The resources included in the Bundle SHALL conform to the profiles listed in the 'List of profiles' below. Because of the informative nature of the transaction, '''no''' [[#Actionable_tag|{{term|actionable}} tags]] shall be present.<br /> <br /> === Receive (response message) ===<br /> The server checks each resource present within the Bundle it receives for the absence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | VariableDosingRegimen<br /> | WisselendDoseerschema<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-VariableDosingRegimen|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAdministration2<br /> | Medicatietoediening2<br /> | MedicationAdministration<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAdministration2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication overview (Retrieve/Serve) ==<br /> The retrieve medication overview transaction is used by the client to retrieve a medication overview from the server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.388_20220630000000 Medication overview (PULL)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.389-2022-06-30T000000.html Retrieving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOR<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.RetrieveServe|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Retrieve/serve medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.390-2022-06-30T000000.html Serving medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> When a patient or healthcare professional wants to obtain a patient's medication overview, they issue a retrieve medication overview request message. This message uses an extended operation on the RESTful API to obtain a medication overview from a server. An operation is needed because the server will formulate the content of the response based on its internal business logic. The medication overview can not easily be described by standardized RESTful requests. <br /> <br /> The client executes a {{Simplifier|http://nictiz.nl/fhir/OperationDefinition/Medication-Overview|nictiz.fhir.nl.r4.medicationprocess9|title=medication-overview operation}} with an HTTP GET command conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query.<br /> <br /> &lt;pre&gt;<br /> GET [base]/$medication-overview<br /> &lt;/pre&gt;<br /> <br /> === Serve (response message) ===<br /> 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.<br /> <br /> 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].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication overview (Send/Receive) ==<br /> The send medication overview transaction is used by the client to send a medication overview to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.140-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.391_20220630000000 Medication overview (PUSH)]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.392-2022-06-30T000000.html Sending medication overview]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.SendReceive|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication overview}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication overview<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-MOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication overview consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> 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.<br /> <br /> 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].<br /> <br /> === Receive (response message) ===<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | MedicationOverview<br /> | rowspan=&quot;2&quot; | MedicatieOverzicht<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | List<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationOverview|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationUse2<br /> | Medicatiegebruik2<br /> | MedicationStatement<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationUse2|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Contact<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication prescription (Send/Receive) ==<br /> The send medication prescription transaction is used by the client to send a request to dispense medication (Dutch: verstrekkingsverzoek) or process modifications to a medication agreement (Dutch: medicatieafspraak) to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.141-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.394_20220630000000 Medication prescription (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.395-2022-06-30T000000.html Sending medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescription|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication prescription}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VOO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescription-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}) and optionally a DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|order}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below<br /> <br /> The mp-MedicationPrescription-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the MedicationAgreement and DispenseRequest building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|order}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Medication_prescription_processing_.28Send.2FReceive.29|‘Send medication prescription processing’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescription<br /> | Voorschrift<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescription-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Medication prescription processing (Send/Receive) ==<br /> The send medication prescription processing transaction is used by the client to send data on the processing of a medication agreement (Dutch: medicatieafspraak) and possibly a dispense request (Dutch: verstrekkingsverzoek), in the form of an administration agreement (Dutch: toedieningsafspraak) and optionally a medication dispense (Dutch: medicatieverstrekking).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.143-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.406_20220630000000 Medication prescription processing (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.407-2022-06-30T000000.html Sending data on processing of medication prescription]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescriptionProcessing|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive medication prescription processing}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving data on processing of medication prescription<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VAO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because data on processing a medication prescription consists of several building blocks along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-MedicationPrescriptionProcessing-Bundle profile, which contains at least an AdministrationAgreement building block and optionally a MedicationDispense building block. Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-MedicationPrescriptionProcessing-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a prescription and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The server checks the AdministrationAgreement and MedicationDispense building blocks present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]].<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationPrescriptionProcessing<br /> | VoorschriftAfhandeling<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationPrescriptionProcessing-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | AdministrationAgreement<br /> | Toedieningsafspraak<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-AdministrationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationDispense<br /> | Medicatieverstrekking<br /> | MedicationDispense<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationDispense|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Proposal dispense request (Send/Receive) ==<br /> The send proposal dispense request transaction is used by the client to inform the server about a new or modified proposal dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.400_20220630000000 Proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.401-2022-06-30T000000.html Sending proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal dispense request consists of a DispenseRequest building block along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalDispenseRequest-Bundle profile, which contains one DispenseRequest building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalDispenseRequest-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the DispenseRequest building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_dispense_request_.28Send.2FReceive.29|‘Send reply proposal dispense request’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalDispenseRequest<br /> | VoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Reply proposal dispense request (Send/Receive) ==<br /> The send reply proposal dispense request transaction is used by the client to inform the server about a reply on a proposed dispense request (Dutch: verstrekkingsverzoek).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.403_20220630000000 Reply proposal dispense request (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.404-2022-06-30T000000.html Sending reply proposal dispense request]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive reply proposal dispense request}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal dispense request<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VVS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal dispense request consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalDispenseRequest-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalDispenseRequest profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed dispense request that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalDispenseRequest-Bundle profile).<br /> <br /> The mp-ReplyProposalDispenseRequest profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalDispenseRequest<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelVerstrekkingsverzoek<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalDispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | DispenseRequest<br /> | Verstrekkingsverzoek<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-DispenseRequest|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Proposal medication agreement (Send/Receive) ==<br /> The send proposal medication agreement transaction is used by the client to inform the server about a new or modified proposal medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.397_20220630000000 Proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.398-2022-06-30T000000.html Sending proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a proposal medication agreement consists of a MedicationAgreement building block along with supporting resources, a {{term|transaction}} interaction is used.<br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ProposalMedicationAgreement-Bundle profile, which contains at least a MedicationAgreement building block (with {{fhir|MedicationRequest.intent}} = {{term|plan}}). Additionally, one instance of nl-core-Patient, nl-core-BodyHeight and nl-core-BodyWeight, and multiple instances of mp-PharmaceuticalProduct might be included, as well as other supporting resources. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> The mp-ProposalMedicationAgreement-Bundle profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resources sent are part of a proposal and of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the MedicationAgreement building block present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the value of {{fhir|MedicationRequest.intent}} = {{term|plan}} to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing an invocation of the [[#Reply_proposal_medication_agreement_.28Send.2FReceive.29|‘Send reply proposal medication agreement’ transaction]] is expected.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | ProposalMedicationAgreement<br /> | VoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | PharmaceuticalProduct<br /> | FarmaceutischProduct<br /> | Medication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-PharmaceuticalProduct|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyHeight<br /> | Lichaamslengte<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyHeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | BodyWeight<br /> | Lichaamsgewicht<br /> | Observation<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-BodyWeight|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> == Reply proposal medication agreement (Send/Receive) ==<br /> The send reply proposal medication agreement transaction is used by the client to inform the server about a reply on a proposed medication agreement (Dutch: medicatieafspraak).<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;text-align:left;&quot;| '''Transaction group'''<br /> ! style=&quot;text-align:left;&quot;| '''Transaction'''<br /> ! style=&quot;text-align:left;&quot;| '''Actor'''<br /> ! style=&quot;text-align:left;&quot;| '''System role'''<br /> ! style=&quot;text-align:left;&quot;| '''FHIR CapabilityStatement'''<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/sc-2.16.840.1.113883.2.4.3.11.60.20.77.3.142-2022-06-30T000000.html#_2.16.840.1.113883.2.4.3.11.60.20.77.4.445_20220630000000 Reply proposal medication agreement (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/medicatieproces/mp-html-20231017T223005/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.446-2022-06-30T000000.html Sending reply proposal medication agreement]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMO<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}|title=CapabilityStatement Send/receive reply proposal medication agreement}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving reply proposal medication agreement<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|MP-VMS<br /> |}<br /> <br /> === Send (request message) ===<br /> Because a reply proposal medication agreement consists of a Communication resource (which contains the reply itself) along with supporting resources, a {{term|transaction}} interaction is used. <br /> <br /> {{MpFhirSendTransaction}}<br /> <br /> The Bundle SHALL conform to the mp-ReplyProposalMedicationAgreement-Bundle profile, which contains at least one Communication resource that conforms to the mp-ReplyProposalMedicationAgreement profile. Additionally, one instance of nl-core-Patient and other supporting resources might be included. All resources included in the Bundle SHALL conform to their respective profiles listed in the 'List of profiles' below.<br /> <br /> Note that the proposed medication agreement that is replied to is internally resolvable by the server, hence it does not need to be included in the Bundle (and is thus not explicitly modelled in the mp-ReplyProposalMedicationAgreement-Bundle profile).<br /> <br /> The mp-ReplyProposalMedicationAgreement profile prescribes the use of [[#Actionable_tag|{{term|actionable}} tags]] to indicate that the resource sent is of actionable nature.<br /> <br /> === Receive (response message) ===<br /> The client checks the Communication resource present within the Bundle it receives for the presence of [[#Actionable_tag|{{term|actionable}} tags]] and the type of building block referenced to determine the transaction type.<br /> <br /> {{MpFhirReceiveTransaction}}<br /> <br /> Aside from the technical processing outcome described above, after functional processing this transaction might lead to an invocation of the [[#Medication_prescription_.28Send.2FReceive.29|‘Send medication prescription’ transaction]].<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block/transaction profile (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | rowspan=&quot;2&quot; | ReplyProposalMedicationAgreement<br /> | rowspan=&quot;2&quot; | AntwoordVoorstelMedicatieafspraak<br /> | Bundle<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement-Bundle|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Communication<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-ReplyProposalMedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | MedicationAgreement<br /> | Medicatieafspraak<br /> | MedicationRequest<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp-MedicationAgreement|nictiz.fhir.nl.r4.medicationprocess9|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.medicationprocess9|release=V3.0.0}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V3.0.0}}}}<br /> |}<br /> <br /> =Release notes=<br /> Release notes can be found [[mp:V3.0.0-beta.2_releasenotes|here]].<br /> <br /> =Footnotes=<br /> &lt;references/&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=MedMij:Vprepub-2020.01/CIO1.0-AddendaInhoudelijkeGegevensAI&diff=201116 2024-02-21T12:22:01Z

<p>Luud Slagter: MM-5064: Updated wiki tables</p> <hr /> <div><br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:Beschikbaarstellen allergie intolerantie gegevens: addendum inhoudelijke gegevens kwalificatie}}<br /> <br /> =Addenda voor inhoudelijke gegevens=<br /> &lt;section begin=bs-aig-1-1 /&gt;<br /> ==Scenario 1.1 - Alle AllergieIntolerantie-gegevens van een persoon==<br /> <br /> === &lt;span id=&quot;AI_Patient_01&quot; title=&quot;Intern ID = AI_Patient_01&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;_AI_Patient_01&quot;&gt;&lt;span id=&quot;AI_Patient_01&quot; title=&quot;Intern ID = AI_Patient_01&quot;&gt;&lt;span id=&quot;AI_Patient_01&quot; title=&quot;Intern ID = AI_Patient_01&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;8&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Véronique<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|V.<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Roepnaam<br /> |style=&quot;background-color: white;&quot;|Véronique<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Naamgebruik<br /> |style=&quot;background-color: white;&quot;|Eigen geslachtsnaam (code = 'NL1' in codeSystem '2.16.840.1.113883.2.4.3.11.60.101.5.4')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX-TEST-D<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;7&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Knolweg<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1000<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|9999 XA<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Stitswerd<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Land<br /> |style=&quot;background-color: white;&quot;|Nederland (code = '6030' in codeSystem 'GBA Tabel 34 Landen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Woon-/verblijfadres (code = 'PHYS' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Contactgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Telefoonnummers<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;4&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Telefoonnummer<br /> |style=&quot;background-color: white;&quot;|06-12345678<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Telecom type<br /> |style=&quot;background-color: white;&quot;|Mobiel telefoonnummer (code = 'MC' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Nummer soort<br /> |style=&quot;background-color: white;&quot;|Tijdelijk telefoonnummer (code = 'TMP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Email adressen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Email adres<br /> |style=&quot;background-color: white;&quot;|XXX-TEST-D@123mail.com<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Email soort<br /> |style=&quot;background-color: white;&quot;|Privé e-mailadres (code = 'HP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999990238 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|4 apr 1970<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Vrouw (code = 'F' in codeSystem 'HL7 AdministrativeGender')<br /> |}<br /> === Allergie intolerantie===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Allergie intolerantie<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Zibroot<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|AI_01_01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.1)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgverlener_03|Zorgverlener: AI_Zorgverlener_03]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgverlener_03|Zorgverlener: AI_Zorgverlener_03]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Onderwerp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Patient_01|Patient: AI_Patient_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Veroorzakende stof<br /> |style=&quot;background-color: white;&quot;|PREDNISOLON CAPSULE 65MG FNA MR (code = '1112821' in codeSystem 'G-Standaard HPK')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Allergie categorie<br /> |style=&quot;background-color: white;&quot;|Medicijn (code = '419511003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Allergie status<br /> |style=&quot;background-color: white;&quot;|Achterhaald (code = 'obsolete' in codeSystem 'HL7 ActStatus')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Mate van kritiek zijn<br /> |style=&quot;background-color: white;&quot;|Matig (code = '6736007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Laatste reactie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 17:45 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Geldt alleen voor dit merk.<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Reactie<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Symptoom<br /> |style=&quot;background-color: white;&quot;|Toxische epidermale necrolyse (code = '23067006' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Specifieke stof<br /> |style=&quot;background-color: white;&quot;|Prednisolon (code = '4170' in codeSystem 'G-Standaard SNK')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reactie beschrijving<br /> |style=&quot;background-color: white;&quot;|Blaren op grote delen van de huid<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Ernst<br /> |style=&quot;background-color: white;&quot;|Ernstig (code = '24484000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reactie tijdstip<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 17:45 uur<br /> |}<br /> === Allergie intolerantie===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Allergie intolerantie<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Zibroot<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|AI_01_02 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.1)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgverlener_03|Zorgverlener: AI_Zorgverlener_03]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgverlener_03|Zorgverlener: AI_Zorgverlener_03]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Onderwerp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Patient_01|Patient: AI_Patient_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Veroorzakende stof<br /> |style=&quot;background-color: white;&quot;|Prednisolon (code = '4170' in codeSystem 'G-Standaard SNK')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Allergie categorie<br /> |style=&quot;background-color: white;&quot;|Medicijn (code = '419511003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Allergie status<br /> |style=&quot;background-color: white;&quot;|Actief (code = 'active' in codeSystem 'HL7 ActStatus')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 100 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Mate van kritiek zijn<br /> |style=&quot;background-color: white;&quot;|Ernstig (code = '24484000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Laatste reactie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 100 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Reactie<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Symptoom<br /> |style=&quot;background-color: white;&quot;|Toxische epidermale necrolyse (code = '23067006' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reactie beschrijving<br /> |style=&quot;background-color: white;&quot;|Blaren op grote delen van de huid<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Ernst<br /> |style=&quot;background-color: white;&quot;|Ernstig (code = '24484000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van blootstelling<br /> |style=&quot;background-color: white;&quot;|via de maag (code = '445768003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reactie tijdstip<br /> |style=&quot;background-color: white;&quot;|T - 100 dagen om 11:00 uur<br /> |}<br /> === Allergie intolerantie===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Allergie intolerantie<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Zibroot<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|AI_01_03 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.1)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgverlener_03|Zorgverlener: AI_Zorgverlener_03]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgverlener_03|Zorgverlener: AI_Zorgverlener_03]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Onderwerp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Patient_01|Patient: AI_Patient_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Veroorzakende stof<br /> |style=&quot;background-color: white;&quot;|Prednisolon oraal (code = '3158' in codeSystem 'G-Standaard SSK')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Allergie categorie<br /> |style=&quot;background-color: white;&quot;|Medicijn (code = '419511003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Allergie status<br /> |style=&quot;background-color: white;&quot;|Actief (code = 'active' in codeSystem 'HL7 ActStatus')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 150 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Mate van kritiek zijn<br /> |style=&quot;background-color: white;&quot;|Ernstig (code = '24484000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Laatste reactie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 150 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Reactie<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;4&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Symptoom<br /> |style=&quot;background-color: white;&quot;|Exantheem (code = '271807003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reactie beschrijving<br /> |style=&quot;background-color: white;&quot;|Vlekken en bultjes op de huid<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Ernst<br /> |style=&quot;background-color: white;&quot;|Ernstig (code = '24484000' in codeSystem 'SNOMED CT')<br /> |}<br /> === Allergie intolerantie===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Allergie intolerantie<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Zibroot<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|AI_01_04 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.1)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgverlener_03|Zorgverlener: AI_Zorgverlener_03]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgverlener_03|Zorgverlener: AI_Zorgverlener_03]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Onderwerp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Patient_01|Patient: AI_Patient_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Veroorzakende stof<br /> |style=&quot;background-color: white;&quot;|Corticosteroïden groep 1 (code = '74' in codeSystem 'G-Standaard TH122 Ongewenste groepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Allergie categorie<br /> |style=&quot;background-color: white;&quot;|Medicijn (code = '419511003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Allergie status<br /> |style=&quot;background-color: white;&quot;|Actief (code = 'active' in codeSystem 'HL7 ActStatus')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 200 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Mate van kritiek zijn<br /> |style=&quot;background-color: white;&quot;|Ernstig (code = '24484000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Laatste reactie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 200 dagen om 16:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Reactie<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Symptoom<br /> |style=&quot;background-color: white;&quot;|Exantheem (code = '271807003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Ernst<br /> |style=&quot;background-color: white;&quot;|Ernstig (code = '24484000' in codeSystem 'SNOMED CT')<br /> |}<br /> === Allergie intolerantie===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;6&quot; | Allergie intolerantie<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;5&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|Zibroot<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;13&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|AI_01_05 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.1)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;4&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Betrokkene als bron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Contactpersoon<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Contactpersoon_01|Contactpersoon: AI_Contactpersoon_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgverlener_01|Zorgverlener: AI_Zorgverlener_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Onderwerp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Patient_01|Patient: AI_Patient_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;5&quot;|Veroorzakende stof<br /> |style=&quot;background-color: white;&quot;|Latex (code = '111088007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;5&quot;|Allergie categorie<br /> |style=&quot;background-color: white;&quot;|Stof of product (code = '419199007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;5&quot;|Allergie status<br /> |style=&quot;background-color: white;&quot;|Actief (code = 'active' in codeSystem 'HL7 ActStatus')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;5&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 3500 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;5&quot;|Mate van kritiek zijn<br /> |style=&quot;background-color: white;&quot;|Matig (code = '6736007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;5&quot;|Laatste reactie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 265 dagen om 14:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;5&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Dhr. werkt in de zorg en dient latexvrije handschoenen te dragen.<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|Reactie<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;4&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Symptoom<br /> |style=&quot;background-color: white;&quot;|Jeuk (code = '418363000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Ernst<br /> |style=&quot;background-color: white;&quot;|Matig (code = '6736007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Reactie tijdstip<br /> |style=&quot;background-color: white;&quot;|T - 265 dagen om 14:30 uur<br /> |}<br /> === Allergie intolerantie===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Allergie intolerantie<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Zibroot<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|AI_01_06 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.1)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Patient_01|Patient: AI_Patient_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgverlener_02|Zorgverlener: AI_Zorgverlener_02]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Onderwerp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Patient_01|Patient: AI_Patient_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Veroorzakende stof<br /> |style=&quot;background-color: white;&quot;|Pinda (code = '91935009' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Allergie categorie<br /> |style=&quot;background-color: white;&quot;|Voeding (code = '418471000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Allergie status<br /> |style=&quot;background-color: white;&quot;|Niet meer aanwezig (code = 'completed' in codeSystem 'HL7 ActStatus')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 5000 dagen<br /> |}<br /> === Allergie intolerantie===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Allergie intolerantie<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Zibroot<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|AI_01_07 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.1)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgverlener_01|Zorgverlener: AI_Zorgverlener_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgverlener_01|Zorgverlener: AI_Zorgverlener_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Onderwerp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Patient_01|Patient: AI_Patient_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Veroorzakende stof<br /> |style=&quot;background-color: white;&quot;|Pollen (code = '256259004' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Allergie categorie<br /> |style=&quot;background-color: white;&quot;|Omgeving (code = '426232007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Allergie status<br /> |style=&quot;background-color: white;&quot;|Actief (code = 'active' in codeSystem 'HL7 ActStatus')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 500 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Mate van kritiek zijn<br /> |style=&quot;background-color: white;&quot;|Matig (code = '6736007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Laatste reactie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 99 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Reactie<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;5&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Symptoom<br /> |style=&quot;background-color: white;&quot;|Overgevoeligheidsreactie van de bovenste luchtwegen (code = '490008' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Specifieke stof<br /> |style=&quot;background-color: white;&quot;|Graspollen (code = '256277009' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reactie beschrijving<br /> |style=&quot;background-color: white;&quot;|Veelvuldig niezen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Ernst<br /> |style=&quot;background-color: white;&quot;|Matig (code = '6736007' in codeSystem 'SNOMED CT')<br /> |}<br /> === &lt;span id=&quot;AI_Zorgverlener_01&quot; title=&quot;Intern ID = AI_Zorgverlener_01&quot;&gt;Zorgverlener&lt;/span&gt; - 1.1===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;_AI_Zorgverlener_01&quot;&gt;&lt;span id=&quot;AI_Zorgverlener_01&quot; title=&quot;Intern ID = AI_Zorgverlener_01&quot;&gt;&lt;span id=&quot;AI_Zorgverlener_01&quot; title=&quot;Intern ID = AI_Zorgverlener_01&quot;&gt;Zorgverlener&lt;/span&gt; - 1.1&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|111111121 (in identificerend systeem: UZI Personen)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|A.B.<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Naamgebruik<br /> |style=&quot;background-color: white;&quot;|Eigen geslachtsnaam (code = 'NL1' in codeSystem '2.16.840.1.113883.2.4.3.11.60.101.5.4')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Comenius<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam partner<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels partner<br /> |style=&quot;background-color: white;&quot;|de<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam partner<br /> |style=&quot;background-color: white;&quot;|Vries<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Huisartsen, niet nader gespecificeerd (code = '0100' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Contactgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Telefoonnummers<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;4&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Telefoonnummer<br /> |style=&quot;background-color: white;&quot;|+3143321654<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Telecom type<br /> |style=&quot;background-color: white;&quot;|Vast telefoonnummer (code = 'LL' in codeSystem '2.16.840.1.113883.2.4.3.11.60.40.4.22.1')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Nummer soort<br /> |style=&quot;background-color: white;&quot;|Zakelijk telefoonnummer (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Email adressen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Email adres<br /> |style=&quot;background-color: white;&quot;|comenius@hpdetest.nl<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Email soort<br /> |style=&quot;background-color: white;&quot;|Zakelijk e-mailadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Zorgaanbieder<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgaanbieder<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgaanbieder_01|Zorgaanbieder: AI_Zorgaanbieder_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverleners rol<br /> |style=&quot;background-color: white;&quot;|Hoofdbehandelaar (code = 'RESP' in codeSystem 'HL7 ParticipationType')<br /> |}<br /> === &lt;span id=&quot;AI_Zorgverlener_02&quot; title=&quot;Intern ID = AI_Zorgverlener_02&quot;&gt;Zorgverlener&lt;/span&gt; - 1.1===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;_AI_Zorgverlener_02&quot;&gt;&lt;span id=&quot;AI_Zorgverlener_02&quot; title=&quot;Intern ID = AI_Zorgverlener_02&quot;&gt;&lt;span id=&quot;AI_Zorgverlener_02&quot; title=&quot;Intern ID = AI_Zorgverlener_02&quot;&gt;Zorgverlener&lt;/span&gt; - 1.1&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|222222232 (in identificerend systeem: UZI Personen)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;8&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Ottobert<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|O.<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Naamgebruik<br /> |style=&quot;background-color: white;&quot;|Eigen geslachtsnaam (code = 'NL1' in codeSystem '2.16.840.1.113883.2.4.3.11.60.101.5.4')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels<br /> |style=&quot;background-color: white;&quot;|van<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Bekhoven<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Huisartsen, niet nader gespecificeerd (code = '0100' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;7&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Valkendael<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|45<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|6245 HK<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Maastricht<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Land<br /> |style=&quot;background-color: white;&quot;|Nederland (code = '6030' in codeSystem 'GBA Tabel 34 Landen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Contactgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Telefoonnummers<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;4&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Telefoonnummer<br /> |style=&quot;background-color: white;&quot;|06-32165488<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Telecom type<br /> |style=&quot;background-color: white;&quot;|Mobiel telefoonnummer (code = 'MC' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Nummer soort<br /> |style=&quot;background-color: white;&quot;|Zakelijk telefoonnummer (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Email adressen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Email adres<br /> |style=&quot;background-color: white;&quot;|o.vanbekhoven@testmedischcentrum.nl<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Email soort<br /> |style=&quot;background-color: white;&quot;|Zakelijk e-mailadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverleners rol<br /> |style=&quot;background-color: white;&quot;|Behandelaar (code = 'ATND' in codeSystem 'HL7 ParticipationType')<br /> |}<br /> === &lt;span id=&quot;AI_Zorgverlener_03&quot; title=&quot;Intern ID = AI_Zorgverlener_03&quot;&gt;Zorgverlener&lt;/span&gt; - 1.1===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;_AI_Zorgverlener_03&quot;&gt;&lt;span id=&quot;AI_Zorgverlener_03&quot; title=&quot;Intern ID = AI_Zorgverlener_03&quot;&gt;&lt;span id=&quot;AI_Zorgverlener_03&quot; title=&quot;Intern ID = AI_Zorgverlener_03&quot;&gt;Zorgverlener&lt;/span&gt; - 1.1&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|333333343 (in identificerend systeem: UZI Personen)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|M.<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Naamgebruik<br /> |style=&quot;background-color: white;&quot;|Eigen geslachtsnaam (code = 'NL1' in codeSystem '2.16.840.1.113883.2.4.3.11.60.101.5.4')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Boot<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Allergoloog (gesloten register) (code = '01.002' in codeSystem 'RoleCodeNL - zorgverlenertype (personen)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;8&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Kamerlingh Onnesstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|2<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummertoevoeging<br /> |style=&quot;background-color: white;&quot;|huis<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|2999 AZ<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Leiderdorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Land<br /> |style=&quot;background-color: white;&quot;|Nederland (code = '6030' in codeSystem 'GBA Tabel 34 Landen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Contactgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Telefoonnummers<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;4&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Telefoonnummer<br /> |style=&quot;background-color: white;&quot;|0800-654321<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Telecom type<br /> |style=&quot;background-color: white;&quot;|Vast telefoonnummer (code = 'LL' in codeSystem '2.16.840.1.113883.2.4.3.11.60.40.4.22.1')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Nummer soort<br /> |style=&quot;background-color: white;&quot;|Zakelijk telefoonnummer (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Email adressen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Email adres<br /> |style=&quot;background-color: white;&quot;|m.boot@deallergoloog.nl<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Email soort<br /> |style=&quot;background-color: white;&quot;|Zakelijk e-mailadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverleners rol<br /> |style=&quot;background-color: white;&quot;|Behandelaar (code = 'ATND' in codeSystem 'HL7 ParticipationType')<br /> |}<br /> === &lt;span id=&quot;AI_Zorgaanbieder_01&quot; title=&quot;Intern ID = AI_Zorgaanbieder_01&quot;&gt;Zorgaanbieder&lt;/span&gt; - 1.1===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;_AI_Zorgaanbieder_01&quot;&gt;&lt;span id=&quot;AI_Zorgaanbieder_01&quot; title=&quot;Intern ID = AI_Zorgaanbieder_01&quot;&gt;&lt;span id=&quot;AI_Zorgaanbieder_01&quot; title=&quot;Intern ID = AI_Zorgaanbieder_01&quot;&gt;Zorgaanbieder&lt;/span&gt; - 1.1&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder identificatienummer<br /> |style=&quot;background-color: white;&quot;|01057999 (in identificerend systeem: AGB-Z)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie naam<br /> |style=&quot;background-color: white;&quot;|Huisartsenpraktijk 'de Test'<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Contactgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Telefoonnummers<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;4&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Telefoonnummer<br /> |style=&quot;background-color: white;&quot;|0800-987653<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Telecom type<br /> |style=&quot;background-color: white;&quot;|Vast telefoonnummer (code = 'LL' in codeSystem '2.16.840.1.113883.2.4.3.11.60.40.4.22.1')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Nummer soort<br /> |style=&quot;background-color: white;&quot;|Zakelijk telefoonnummer (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Email adressen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Email adres<br /> |style=&quot;background-color: white;&quot;|info@hpdetest.nl<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Email soort<br /> |style=&quot;background-color: white;&quot;|Zakelijk e-mailadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;7&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Dorpstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|14<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|9244 ZZ<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Beetsterzwaag<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Land<br /> |style=&quot;background-color: white;&quot;|Nederland (code = '6030' in codeSystem 'GBA Tabel 34 Landen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie type<br /> |style=&quot;background-color: white;&quot;|Huisartspraktijk (zelfstandig of groepspraktijk) (code = 'Z3' in codeSystem '2.16.840.1.113883.2.4.15.1060')<br /> |}<br /> === &lt;span id=&quot;AI_Contactpersoon_01&quot; title=&quot;Intern ID = AI_Contactpersoon_01&quot;&gt;Contactpersoon&lt;/span&gt; - 1.1===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;_AI_Contactpersoon_01&quot;&gt;&lt;span id=&quot;AI_Contactpersoon_01&quot; title=&quot;Intern ID = AI_Contactpersoon_01&quot;&gt;&lt;span id=&quot;AI_Contactpersoon_01&quot; title=&quot;Intern ID = AI_Contactpersoon_01&quot;&gt;Contactpersoon&lt;/span&gt; - 1.1&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;8&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Abraham<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|B.M.H.<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Roepnaam<br /> |style=&quot;background-color: white;&quot;|Bram<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Naamgebruik<br /> |style=&quot;background-color: white;&quot;|Eigen geslachtsnaam (code = 'NL1' in codeSystem '2.16.840.1.113883.2.4.3.11.60.101.5.4')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Pasveer<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Contactgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;9&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Telefoonnummers<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Telefoonnummer<br /> |style=&quot;background-color: white;&quot;|06-12345670<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Telecom type<br /> |style=&quot;background-color: white;&quot;|Mobiel telefoonnummer (code = 'MC' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Email adressen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Email adres<br /> |style=&quot;background-color: white;&quot;|brampasveer_123@hotmail.com<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Email soort<br /> |style=&quot;background-color: white;&quot;|Privé e-mailadres (code = 'HP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;8&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Bolweg<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|99<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummerletter<br /> |style=&quot;background-color: white;&quot;|b<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|9999 XX<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Stitswerd<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Land<br /> |style=&quot;background-color: white;&quot;|Nederland (code = '6030' in codeSystem 'GBA Tabel 34 Landen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Woon-/verblijfadres (code = 'PHYS' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Rol<br /> |style=&quot;background-color: white;&quot;|Vriend(in)/kennis (code = '20' in codeSystem '2.16.840.1.113883.2.4.3.11.22.472')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Relatie<br /> |style=&quot;background-color: white;&quot;|Anders (code = 'OTH' in codeSystem 'HL7 NullFlavor'): Boezemvriend<br /> |}&lt;section end=bs-aig-1-1 /&gt;<br /> &lt;section begin=bs-aig-1-2 /&gt;<br /> ==Scenario 1.2 - Een persoon zonder AllergieIntolerantie-gegevens==<br /> <br /> === &lt;span id=&quot;AI_Patient_02&quot; title=&quot;Intern ID = AI_Patient_02&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;_AI_Patient_02&quot;&gt;&lt;span id=&quot;AI_Patient_02&quot; title=&quot;Intern ID = AI_Patient_02&quot;&gt;&lt;span id=&quot;AI_Patient_02&quot; title=&quot;Intern ID = AI_Patient_02&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;8&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Willem<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|W.<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Roepnaam<br /> |style=&quot;background-color: white;&quot;|Wim<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Naamgebruik<br /> |style=&quot;background-color: white;&quot;|Eigen geslachtsnaam (code = 'NL1' in codeSystem '2.16.840.1.113883.2.4.3.11.60.101.5.4')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX-TEST-F<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;7&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Knolweg<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1001<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|9999 XX<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Stitswerd<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Land<br /> |style=&quot;background-color: white;&quot;|Nederland (code = '6030' in codeSystem '2.16.840.1.113883.2.4.4.16.34')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Postadres (code = 'PST' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999990251 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|5 mei 1970<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Man (code = 'M' in codeSystem 'HL7 AdministrativeGender')<br /> |}&lt;section end=bs-aig-1-2 /&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=MedMij:V2020.01/CIO1.0-AddendaInhoudelijkeGegevensAI&diff=299726 2024-02-21T12:22:01Z

<p>Luud Slagter: MM-5064: Updated wiki tables</p> <hr /> <div><br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:Beschikbaarstellen allergie intolerantie gegevens: addendum inhoudelijke gegevens kwalificatie}}<br /> <br /> =Addenda voor inhoudelijke gegevens=<br /> &lt;section begin=bs-aig-1-1 /&gt;<br /> ==Scenario 1.1 - Alle AllergieIntolerantie-gegevens van een persoon==<br /> <br /> === &lt;span id=&quot;AI_Patient_01&quot; title=&quot;Intern ID = AI_Patient_01&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;_AI_Patient_01&quot;&gt;&lt;span id=&quot;AI_Patient_01&quot; title=&quot;Intern ID = AI_Patient_01&quot;&gt;&lt;span id=&quot;AI_Patient_01&quot; title=&quot;Intern ID = AI_Patient_01&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;8&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Véronique<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|V.<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Roepnaam<br /> |style=&quot;background-color: white;&quot;|Véronique<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Naamgebruik<br /> |style=&quot;background-color: white;&quot;|Eigen geslachtsnaam (code = 'NL1' in codeSystem '2.16.840.1.113883.2.4.3.11.60.101.5.4')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX-TEST-D<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;7&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Knolweg<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1000<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|9999 XA<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Stitswerd<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Land<br /> |style=&quot;background-color: white;&quot;|Nederland (code = '6030' in codeSystem 'GBA Tabel 34 Landen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Woon-/verblijfadres (code = 'PHYS' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Contactgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Telefoonnummers<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;4&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Telefoonnummer<br /> |style=&quot;background-color: white;&quot;|06-12345678<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Telecom type<br /> |style=&quot;background-color: white;&quot;|Mobiel telefoonnummer (code = 'MC' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Nummer soort<br /> |style=&quot;background-color: white;&quot;|Tijdelijk telefoonnummer (code = 'TMP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Email adressen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Email adres<br /> |style=&quot;background-color: white;&quot;|XXX-TEST-D@123mail.com<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Email soort<br /> |style=&quot;background-color: white;&quot;|Privé e-mailadres (code = 'HP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999990238 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|4 apr 1970<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Vrouw (code = 'F' in codeSystem 'HL7 AdministrativeGender')<br /> |}<br /> === Allergie intolerantie===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Allergie intolerantie<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Zibroot<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|AI_01_01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.1)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgverlener_03|Zorgverlener: AI_Zorgverlener_03]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgverlener_03|Zorgverlener: AI_Zorgverlener_03]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Onderwerp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Patient_01|Patient: AI_Patient_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Veroorzakende stof<br /> |style=&quot;background-color: white;&quot;|PREDNISOLON CAPSULE 65MG FNA MR (code = '1112821' in codeSystem 'G-Standaard HPK')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Allergie categorie<br /> |style=&quot;background-color: white;&quot;|Medicijn (code = '419511003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Allergie status<br /> |style=&quot;background-color: white;&quot;|Achterhaald (code = 'obsolete' in codeSystem 'HL7 ActStatus')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Mate van kritiek zijn<br /> |style=&quot;background-color: white;&quot;|Matig (code = '6736007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Laatste reactie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 17:45 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Geldt alleen voor dit merk.<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Reactie<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Symptoom<br /> |style=&quot;background-color: white;&quot;|Toxische epidermale necrolyse (code = '23067006' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Specifieke stof<br /> |style=&quot;background-color: white;&quot;|Prednisolon (code = '4170' in codeSystem 'G-Standaard SNK')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reactie beschrijving<br /> |style=&quot;background-color: white;&quot;|Blaren op grote delen van de huid<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Ernst<br /> |style=&quot;background-color: white;&quot;|Ernstig (code = '24484000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reactie tijdstip<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 17:45 uur<br /> |}<br /> === Allergie intolerantie===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Allergie intolerantie<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Zibroot<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|AI_01_02 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.1)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgverlener_03|Zorgverlener: AI_Zorgverlener_03]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgverlener_03|Zorgverlener: AI_Zorgverlener_03]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Onderwerp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Patient_01|Patient: AI_Patient_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Veroorzakende stof<br /> |style=&quot;background-color: white;&quot;|Prednisolon (code = '4170' in codeSystem 'G-Standaard SNK')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Allergie categorie<br /> |style=&quot;background-color: white;&quot;|Medicijn (code = '419511003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Allergie status<br /> |style=&quot;background-color: white;&quot;|Actief (code = 'active' in codeSystem 'HL7 ActStatus')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 100 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Mate van kritiek zijn<br /> |style=&quot;background-color: white;&quot;|Ernstig (code = '24484000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Laatste reactie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 100 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Reactie<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Symptoom<br /> |style=&quot;background-color: white;&quot;|Toxische epidermale necrolyse (code = '23067006' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reactie beschrijving<br /> |style=&quot;background-color: white;&quot;|Blaren op grote delen van de huid<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Ernst<br /> |style=&quot;background-color: white;&quot;|Ernstig (code = '24484000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van blootstelling<br /> |style=&quot;background-color: white;&quot;|via de maag (code = '445768003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reactie tijdstip<br /> |style=&quot;background-color: white;&quot;|T - 100 dagen om 11:00 uur<br /> |}<br /> === Allergie intolerantie===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Allergie intolerantie<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Zibroot<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|AI_01_03 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.1)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgverlener_03|Zorgverlener: AI_Zorgverlener_03]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgverlener_03|Zorgverlener: AI_Zorgverlener_03]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Onderwerp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Patient_01|Patient: AI_Patient_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Veroorzakende stof<br /> |style=&quot;background-color: white;&quot;|Prednisolon oraal (code = '3158' in codeSystem 'G-Standaard SSK')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Allergie categorie<br /> |style=&quot;background-color: white;&quot;|Medicijn (code = '419511003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Allergie status<br /> |style=&quot;background-color: white;&quot;|Actief (code = 'active' in codeSystem 'HL7 ActStatus')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 150 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Mate van kritiek zijn<br /> |style=&quot;background-color: white;&quot;|Ernstig (code = '24484000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Laatste reactie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 150 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Reactie<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;4&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Symptoom<br /> |style=&quot;background-color: white;&quot;|Exantheem (code = '271807003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reactie beschrijving<br /> |style=&quot;background-color: white;&quot;|Vlekken en bultjes op de huid<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Ernst<br /> |style=&quot;background-color: white;&quot;|Ernstig (code = '24484000' in codeSystem 'SNOMED CT')<br /> |}<br /> === Allergie intolerantie===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Allergie intolerantie<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Zibroot<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|AI_01_04 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.1)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgverlener_03|Zorgverlener: AI_Zorgverlener_03]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgverlener_03|Zorgverlener: AI_Zorgverlener_03]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Onderwerp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Patient_01|Patient: AI_Patient_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Veroorzakende stof<br /> |style=&quot;background-color: white;&quot;|Corticosteroïden groep 1 (code = '74' in codeSystem 'G-Standaard TH122 Ongewenste groepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Allergie categorie<br /> |style=&quot;background-color: white;&quot;|Medicijn (code = '419511003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Allergie status<br /> |style=&quot;background-color: white;&quot;|Actief (code = 'active' in codeSystem 'HL7 ActStatus')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 200 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Mate van kritiek zijn<br /> |style=&quot;background-color: white;&quot;|Ernstig (code = '24484000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Laatste reactie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 200 dagen om 16:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Reactie<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Symptoom<br /> |style=&quot;background-color: white;&quot;|Exantheem (code = '271807003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Ernst<br /> |style=&quot;background-color: white;&quot;|Ernstig (code = '24484000' in codeSystem 'SNOMED CT')<br /> |}<br /> === Allergie intolerantie===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;6&quot; | Allergie intolerantie<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;5&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|Zibroot<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;13&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|AI_01_05 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.1)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;4&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Betrokkene als bron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Contactpersoon<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Contactpersoon_01|Contactpersoon: AI_Contactpersoon_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgverlener_01|Zorgverlener: AI_Zorgverlener_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Onderwerp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Patient_01|Patient: AI_Patient_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;5&quot;|Veroorzakende stof<br /> |style=&quot;background-color: white;&quot;|Latex (code = '111088007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;5&quot;|Allergie categorie<br /> |style=&quot;background-color: white;&quot;|Stof of product (code = '419199007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;5&quot;|Allergie status<br /> |style=&quot;background-color: white;&quot;|Actief (code = 'active' in codeSystem 'HL7 ActStatus')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;5&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 3500 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;5&quot;|Mate van kritiek zijn<br /> |style=&quot;background-color: white;&quot;|Matig (code = '6736007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;5&quot;|Laatste reactie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 265 dagen om 14:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;5&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Dhr. werkt in de zorg en dient latexvrije handschoenen te dragen.<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|Reactie<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;4&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Symptoom<br /> |style=&quot;background-color: white;&quot;|Jeuk (code = '418363000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Ernst<br /> |style=&quot;background-color: white;&quot;|Matig (code = '6736007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Reactie tijdstip<br /> |style=&quot;background-color: white;&quot;|T - 265 dagen om 14:30 uur<br /> |}<br /> === Allergie intolerantie===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Allergie intolerantie<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Zibroot<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|AI_01_06 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.1)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Patient_01|Patient: AI_Patient_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgverlener_02|Zorgverlener: AI_Zorgverlener_02]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Onderwerp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Patient_01|Patient: AI_Patient_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Veroorzakende stof<br /> |style=&quot;background-color: white;&quot;|Pinda (code = '91935009' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Allergie categorie<br /> |style=&quot;background-color: white;&quot;|Voeding (code = '418471000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Allergie status<br /> |style=&quot;background-color: white;&quot;|Niet meer aanwezig (code = 'completed' in codeSystem 'HL7 ActStatus')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 5000 dagen<br /> |}<br /> === Allergie intolerantie===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Allergie intolerantie<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Zibroot<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|AI_01_07 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.1)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgverlener_01|Zorgverlener: AI_Zorgverlener_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgverlener_01|Zorgverlener: AI_Zorgverlener_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Onderwerp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Patient_01|Patient: AI_Patient_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Veroorzakende stof<br /> |style=&quot;background-color: white;&quot;|Pollen (code = '256259004' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Allergie categorie<br /> |style=&quot;background-color: white;&quot;|Omgeving (code = '426232007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Allergie status<br /> |style=&quot;background-color: white;&quot;|Actief (code = 'active' in codeSystem 'HL7 ActStatus')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 500 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Mate van kritiek zijn<br /> |style=&quot;background-color: white;&quot;|Matig (code = '6736007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Laatste reactie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 99 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Reactie<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;5&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Symptoom<br /> |style=&quot;background-color: white;&quot;|Overgevoeligheidsreactie van de bovenste luchtwegen (code = '490008' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Specifieke stof<br /> |style=&quot;background-color: white;&quot;|Graspollen (code = '256277009' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reactie beschrijving<br /> |style=&quot;background-color: white;&quot;|Veelvuldig niezen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Ernst<br /> |style=&quot;background-color: white;&quot;|Matig (code = '6736007' in codeSystem 'SNOMED CT')<br /> |}<br /> === &lt;span id=&quot;AI_Zorgverlener_01&quot; title=&quot;Intern ID = AI_Zorgverlener_01&quot;&gt;Zorgverlener&lt;/span&gt; - 1.1===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;_AI_Zorgverlener_01&quot;&gt;&lt;span id=&quot;AI_Zorgverlener_01&quot; title=&quot;Intern ID = AI_Zorgverlener_01&quot;&gt;&lt;span id=&quot;AI_Zorgverlener_01&quot; title=&quot;Intern ID = AI_Zorgverlener_01&quot;&gt;Zorgverlener&lt;/span&gt; - 1.1&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|111111121 (in identificerend systeem: UZI Personen)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|A.B.<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Naamgebruik<br /> |style=&quot;background-color: white;&quot;|Eigen geslachtsnaam (code = 'NL1' in codeSystem '2.16.840.1.113883.2.4.3.11.60.101.5.4')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Comenius<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam partner<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels partner<br /> |style=&quot;background-color: white;&quot;|de<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam partner<br /> |style=&quot;background-color: white;&quot;|Vries<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Huisartsen, niet nader gespecificeerd (code = '0100' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Contactgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Telefoonnummers<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;4&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Telefoonnummer<br /> |style=&quot;background-color: white;&quot;|+3143321654<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Telecom type<br /> |style=&quot;background-color: white;&quot;|Vast telefoonnummer (code = 'LL' in codeSystem '2.16.840.1.113883.2.4.3.11.60.40.4.22.1')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Nummer soort<br /> |style=&quot;background-color: white;&quot;|Zakelijk telefoonnummer (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Email adressen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Email adres<br /> |style=&quot;background-color: white;&quot;|comenius@hpdetest.nl<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Email soort<br /> |style=&quot;background-color: white;&quot;|Zakelijk e-mailadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Zorgaanbieder<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgaanbieder<br /> |style=&quot;background-color: white;&quot;|Zie [[#AI_Zorgaanbieder_01|Zorgaanbieder: AI_Zorgaanbieder_01]]<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverleners rol<br /> |style=&quot;background-color: white;&quot;|Hoofdbehandelaar (code = 'RESP' in codeSystem 'HL7 ParticipationType')<br /> |}<br /> === &lt;span id=&quot;AI_Zorgverlener_02&quot; title=&quot;Intern ID = AI_Zorgverlener_02&quot;&gt;Zorgverlener&lt;/span&gt; - 1.1===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;_AI_Zorgverlener_02&quot;&gt;&lt;span id=&quot;AI_Zorgverlener_02&quot; title=&quot;Intern ID = AI_Zorgverlener_02&quot;&gt;&lt;span id=&quot;AI_Zorgverlener_02&quot; title=&quot;Intern ID = AI_Zorgverlener_02&quot;&gt;Zorgverlener&lt;/span&gt; - 1.1&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|222222232 (in identificerend systeem: UZI Personen)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;8&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Ottobert<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|O.<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Naamgebruik<br /> |style=&quot;background-color: white;&quot;|Eigen geslachtsnaam (code = 'NL1' in codeSystem '2.16.840.1.113883.2.4.3.11.60.101.5.4')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels<br /> |style=&quot;background-color: white;&quot;|van<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Bekhoven<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Huisartsen, niet nader gespecificeerd (code = '0100' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;7&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Valkendael<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|45<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|6245 HK<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Maastricht<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Land<br /> |style=&quot;background-color: white;&quot;|Nederland (code = '6030' in codeSystem 'GBA Tabel 34 Landen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Contactgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Telefoonnummers<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;4&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Telefoonnummer<br /> |style=&quot;background-color: white;&quot;|06-32165488<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Telecom type<br /> |style=&quot;background-color: white;&quot;|Mobiel telefoonnummer (code = 'MC' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Nummer soort<br /> |style=&quot;background-color: white;&quot;|Zakelijk telefoonnummer (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Email adressen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Email adres<br /> |style=&quot;background-color: white;&quot;|o.vanbekhoven@testmedischcentrum.nl<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Email soort<br /> |style=&quot;background-color: white;&quot;|Zakelijk e-mailadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverleners rol<br /> |style=&quot;background-color: white;&quot;|Behandelaar (code = 'ATND' in codeSystem 'HL7 ParticipationType')<br /> |}<br /> === &lt;span id=&quot;AI_Zorgverlener_03&quot; title=&quot;Intern ID = AI_Zorgverlener_03&quot;&gt;Zorgverlener&lt;/span&gt; - 1.1===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;_AI_Zorgverlener_03&quot;&gt;&lt;span id=&quot;AI_Zorgverlener_03&quot; title=&quot;Intern ID = AI_Zorgverlener_03&quot;&gt;&lt;span id=&quot;AI_Zorgverlener_03&quot; title=&quot;Intern ID = AI_Zorgverlener_03&quot;&gt;Zorgverlener&lt;/span&gt; - 1.1&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|333333343 (in identificerend systeem: UZI Personen)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|M.<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Naamgebruik<br /> |style=&quot;background-color: white;&quot;|Eigen geslachtsnaam (code = 'NL1' in codeSystem '2.16.840.1.113883.2.4.3.11.60.101.5.4')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Boot<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Allergoloog (gesloten register) (code = '01.002' in codeSystem 'RoleCodeNL - zorgverlenertype (personen)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;8&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Kamerlingh Onnesstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|2<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummertoevoeging<br /> |style=&quot;background-color: white;&quot;|huis<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|2999 AZ<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Leiderdorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Land<br /> |style=&quot;background-color: white;&quot;|Nederland (code = '6030' in codeSystem 'GBA Tabel 34 Landen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Contactgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Telefoonnummers<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;4&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Telefoonnummer<br /> |style=&quot;background-color: white;&quot;|0800-654321<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Telecom type<br /> |style=&quot;background-color: white;&quot;|Vast telefoonnummer (code = 'LL' in codeSystem '2.16.840.1.113883.2.4.3.11.60.40.4.22.1')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Nummer soort<br /> |style=&quot;background-color: white;&quot;|Zakelijk telefoonnummer (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Email adressen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Email adres<br /> |style=&quot;background-color: white;&quot;|m.boot@deallergoloog.nl<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Email soort<br /> |style=&quot;background-color: white;&quot;|Zakelijk e-mailadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverleners rol<br /> |style=&quot;background-color: white;&quot;|Behandelaar (code = 'ATND' in codeSystem 'HL7 ParticipationType')<br /> |}<br /> === &lt;span id=&quot;AI_Zorgaanbieder_01&quot; title=&quot;Intern ID = AI_Zorgaanbieder_01&quot;&gt;Zorgaanbieder&lt;/span&gt; - 1.1===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;_AI_Zorgaanbieder_01&quot;&gt;&lt;span id=&quot;AI_Zorgaanbieder_01&quot; title=&quot;Intern ID = AI_Zorgaanbieder_01&quot;&gt;&lt;span id=&quot;AI_Zorgaanbieder_01&quot; title=&quot;Intern ID = AI_Zorgaanbieder_01&quot;&gt;Zorgaanbieder&lt;/span&gt; - 1.1&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder identificatienummer<br /> |style=&quot;background-color: white;&quot;|01057999 (in identificerend systeem: AGB-Z)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie naam<br /> |style=&quot;background-color: white;&quot;|Huisartsenpraktijk 'de Test'<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Contactgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Telefoonnummers<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;4&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Telefoonnummer<br /> |style=&quot;background-color: white;&quot;|0800-987653<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Telecom type<br /> |style=&quot;background-color: white;&quot;|Vast telefoonnummer (code = 'LL' in codeSystem '2.16.840.1.113883.2.4.3.11.60.40.4.22.1')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Nummer soort<br /> |style=&quot;background-color: white;&quot;|Zakelijk telefoonnummer (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Email adressen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Email adres<br /> |style=&quot;background-color: white;&quot;|info@hpdetest.nl<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Email soort<br /> |style=&quot;background-color: white;&quot;|Zakelijk e-mailadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;7&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Dorpstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|14<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|9244 ZZ<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Beetsterzwaag<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Land<br /> |style=&quot;background-color: white;&quot;|Nederland (code = '6030' in codeSystem 'GBA Tabel 34 Landen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie type<br /> |style=&quot;background-color: white;&quot;|Huisartspraktijk (zelfstandig of groepspraktijk) (code = 'Z3' in codeSystem '2.16.840.1.113883.2.4.15.1060')<br /> |}<br /> === &lt;span id=&quot;AI_Contactpersoon_01&quot; title=&quot;Intern ID = AI_Contactpersoon_01&quot;&gt;Contactpersoon&lt;/span&gt; - 1.1===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;_AI_Contactpersoon_01&quot;&gt;&lt;span id=&quot;AI_Contactpersoon_01&quot; title=&quot;Intern ID = AI_Contactpersoon_01&quot;&gt;&lt;span id=&quot;AI_Contactpersoon_01&quot; title=&quot;Intern ID = AI_Contactpersoon_01&quot;&gt;Contactpersoon&lt;/span&gt; - 1.1&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;8&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Abraham<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|B.M.H.<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Roepnaam<br /> |style=&quot;background-color: white;&quot;|Bram<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Naamgebruik<br /> |style=&quot;background-color: white;&quot;|Eigen geslachtsnaam (code = 'NL1' in codeSystem '2.16.840.1.113883.2.4.3.11.60.101.5.4')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Pasveer<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Contactgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;9&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Telefoonnummers<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Telefoonnummer<br /> |style=&quot;background-color: white;&quot;|06-12345670<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Telecom type<br /> |style=&quot;background-color: white;&quot;|Mobiel telefoonnummer (code = 'MC' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Email adressen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Email adres<br /> |style=&quot;background-color: white;&quot;|brampasveer_123@hotmail.com<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Email soort<br /> |style=&quot;background-color: white;&quot;|Privé e-mailadres (code = 'HP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;8&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Bolweg<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|99<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummerletter<br /> |style=&quot;background-color: white;&quot;|b<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|9999 XX<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Stitswerd<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Land<br /> |style=&quot;background-color: white;&quot;|Nederland (code = '6030' in codeSystem 'GBA Tabel 34 Landen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Woon-/verblijfadres (code = 'PHYS' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Rol<br /> |style=&quot;background-color: white;&quot;|Vriend(in)/kennis (code = '20' in codeSystem '2.16.840.1.113883.2.4.3.11.22.472')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Relatie<br /> |style=&quot;background-color: white;&quot;|Anders (code = 'OTH' in codeSystem 'HL7 NullFlavor'): Boezemvriend<br /> |}&lt;section end=bs-aig-1-1 /&gt;<br /> &lt;section begin=bs-aig-1-2 /&gt;<br /> ==Scenario 1.2 - Een persoon zonder AllergieIntolerantie-gegevens==<br /> <br /> === &lt;span id=&quot;AI_Patient_02&quot; title=&quot;Intern ID = AI_Patient_02&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;_AI_Patient_02&quot;&gt;&lt;span id=&quot;AI_Patient_02&quot; title=&quot;Intern ID = AI_Patient_02&quot;&gt;&lt;span id=&quot;AI_Patient_02&quot; title=&quot;Intern ID = AI_Patient_02&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;8&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Willem<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|W.<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Roepnaam<br /> |style=&quot;background-color: white;&quot;|Wim<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Naamgebruik<br /> |style=&quot;background-color: white;&quot;|Eigen geslachtsnaam (code = 'NL1' in codeSystem '2.16.840.1.113883.2.4.3.11.60.101.5.4')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX-TEST-F<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;7&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Knolweg<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1001<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|9999 XX<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Stitswerd<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Land<br /> |style=&quot;background-color: white;&quot;|Nederland (code = '6030' in codeSystem '2.16.840.1.113883.2.4.4.16.34')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Postadres (code = 'PST' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999990251 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|5 mei 1970<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Man (code = 'M' in codeSystem 'HL7 AdministrativeGender')<br /> |}&lt;section end=bs-aig-1-2 /&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=cio:V2.0.0-beta.2_FHIR_CiO&diff=200561 2024-02-06T14:39:34Z

<p>Luud Slagter: /* Transactions */ Updated system roles</p> <hr /> <div>{{Vdraft/InformationBox|This FHIR IG is currently under development and can not be considered stable and ready for use. For questions and change requests regarding this IG, please create a ticket in [{{VersieInfo|BITS|release=V2.0.0-beta.2|namespace=cio}} BITS].}}<br /> <br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:FHIR Implementation Guide CiO version {{VersieInfo|CiO|release=V2.0.0-beta.2|namespace=cio}}}}<br /> <br /> [[Bestand:Icoon Nictiz Cirkel Informatiestandaard Contra-indicaties en Overgevoeligheden (2).svg|link=|100px|CiO|rechts]] <br /> <br /> &lt;div class=&quot;toclimit-3&quot;&gt;__TOC__&lt;/div&gt;<br /> <br /> = Introduction =<br /> <br /> This is the implementation guide (IG) for the information standard CiO (Dutch: Contra-indicaties en overgevoeligheden, English: Contraindications and hypersensitivities), version {{VersieInfo|CiO|release=V2.0.0-beta.2}}. The functional specification can be found [[cio:V2.0.0-beta.2_Ontwerp_CiO|here]] and is implemented using [https://www.hl7.org/fhir/R4/ HL7 FHIR R4]. This implementation guide assumes that the reader is familiar with both the functional specification and this version of FHIR.<br /> <br /> 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 Overarching principles and the use of FHIR packages. Where the general IG uses the term ‘use case’, this IG uses the term ‘transaction’ for the various processes that are described.<br /> <br /> This IG first describes the boundaries and relationships in place, after which the implementation is described per transaction.<br /> <br /> = Boundaries and relationships =<br /> <br /> == Boundaries ==<br /> <br /> Note that this version of the CiO information standard is only focused on medication contraindications and hypersensitivities due to medication (see [[cio:V2.0.0-beta.2_Ontwerp_CiO#Algemeen|section 1.1 of the functional specification]]). Technically this scope is reflected in for instance the terminology used within the FHIR profiles or the naming of the cio-MedicationContraIndication profile. In this IG however, we will not further elaborate on this narrower scope and instead describe the technical implementation of this standard as general as possible, in order to make it easier to incorporate a broadening of the scope in subsequent versions of this IG.<br /> <br /> == Building blocks and profiles ==<br /> <br /> The exchange of data within the CiO standard version {{VersieInfo|CiO|release=V2.0.0-beta.2}} is partly based on the 2020 publication of the Dutch Health and Care Information Models (Dutch: ‘zorginformatiebouwstenen’ or ‘zibs’), and subsequent changes made that will be present in the 2024 prepublication. In particular, the prepublication of 2021 saw the introduction of the Hypersensitivity and Reaction zibs which are based on and still have quite some overlap with the zib AllergyIntolerance that already existed. In the prepublication of 2024 the zibs Hypersensitivity and Reaction have been overhauled in such a way that they only contain ‘diagnostic’ elements. The concepts within these zibs that were related to surveillance with respect to substances have been removed, resulting in a new zib SurveillanceDecision. Moreover, the zib Alert has changed in this prepublication such that the zib MedicationContraIndication has become superfluous, by adding a new AlertType reserved for medication contraindications. The functional data set of CiO has further built upon these four zibs, and the resulting objects (which are actually exchanged) are referred to as ‘building blocks’ in the data set, and can thus be seen as ‘extended zibs’ suitable for implementation.<br /> <br /> Due to new insights, the building blocks Hypersensitivity and Reaction in the functional data set have deviated quite a lot from the zib AllergyIntolerance present in the 2020 publication, making them incompatible in varying degrees from a technical point of view. Therefore it was not possible to implement the FHIR profiles for these 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 the nl-core profiles, meaning that they are not derived from nl-core-AllergyIntolerance. Similarly, for the building block MedicationContraIndication it was not possible to derive its profile from the nl-core-Alert profile corresponding to zib publication 2020, due to incompatible changes introduced in the zib Alert in the prepublication of 2024. Lastly, the zib SurveillanceDecision is newly introduced, so obviously no derivation from nl-core profiles is possible.<br /> <br /> In a subsequent version of the information standard, it is the intention to base the profiles for all building blocks on their respective nl-core profiles based on zib publication 2024. There are however some considerations to be taken into account, since it is only possible to use these nl-core profiles provided:<br /> * the underlying zibs are still part of the 2024 publication;<br /> * no incompatible changes will be added on the relevant zibs between the prepublication and publication of 2024;<br /> * they are defined in FHIR R4 (otherwise the cio profiles would also need to be converted to another FHIR version).<br /> <br /> It is important to note that there is still extensive discussion about the exact scope and content of the CiO building blocks, meaning that the current profiles definitely cannot be considered to be stable and ready for use. A list of discussion topics with regards to the technical implementation can be found in [[#Discussion|section 2.5]].<br /> <br /> {{NoteBoxNictizR4Package|p1=nictiz.fhir.nl.r4.cio|v1={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}|p2=nictiz.fhir.nl.r4.nl-core|v2={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> <br /> Note that the package versioning does not follow the versioning of the information standard, as CiO version 2.0.0 was the first release of the CiO information standard based on FHIR R4. This means that CiO version 2.0.0-beta.x makes use of version 1.0.0-beta.x of the nictiz.fhir.nl.r4.cio FHIR package.<br /> <br /> === Main building blocks ===<br /> <br /> As described above, the main building blocks have no dependency on any zib counterparts of the 2020 publication, resulting in so-called ‘cio’ profiles.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationContraIndication<br /> | MedicatieContraIndicatie<br /> | Flag<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-MedicationContraIndication|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | SurveillanceDecision<br /> | BewakingBesluit<br /> | Flag<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-SurveillanceDecision|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Hypersensitivity<br /> | Overgevoeligheid<br /> | AllergyIntolerance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Hypersensitivity|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Reaction<br /> | Reactie<br /> | AllergyIntolerance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Reaction|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Condition<br /> | Aandoening<br /> | Condition<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Condition|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | RegistrationData<br /> | RegistratieGegevens<br /> | Provenance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-RegistrationData|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |}<br /> <br /> The last two building blocks in the above table have a special status:<br /> * Condition is not a separate building block within the CiO data set, and the cio-Condition profile actually contains mappings to concepts within the Hypersensitivity and Reaction building blocks that relate to the underlying condition and diagnosis. Thus, in order to convey the complete Hypersensitivity or Reaction building block, it is necessary to use an instance conforming to the cio-Hypersensitivity or cio-Reaction profile, together with an instance conforming to the cio-Condition profile.<br /> * The RegistrationData building block is part of every other main building block in the data set, containing data that relates to the registering process instead of the medical concept itself. Such data is often not (completely) mappable within the profiles corresponding to the medical concept. Hence, whenever another main building block is exchanged, it is represented by its own profile in conjunction with an instance of the cio-RegistrationData profile. In the future, if more information standards will make use of the Provenance resource to represent the administrative concepts present in RegistrationData, it is intended to create an nl-core-RegistrationData profile that replaces the cio-RegistrationData profile.<br /> <br /> === Secondary building blocks ===<br /> <br /> Additionally, the standard uses several secondary building blocks referenced from the main building blocks. All secondary building blocks are part of the [[FHIR:V1.0_FHIR_IG_R4#Functional_definitions|‘nl-core’]] package.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthcareProvider<br /> | rowspan=&quot;2&quot; | Zorgaanbieder<br /> | Location<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | ContactPerson<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |}<br /> <br /> Note the following:<br /> * Each occurrence of the zib HealthProfessional is normally represented by '''two''' FHIR resources: an instance of nl-core-HealthProfessional-PractitionerRole and an instance of nl-core-HealthProfessional-Practitioner. Sending systems should only fill the reference to the PractitionerRole instance where relevant. Receiving systems can resolve the reference to the Practitioner resource from that PractitionerRole instance.<br /> * The zib HealthcareProvider is mapped to both a Location and Organization profile. In general the Location profile acts as the focal resource, because most references to this zib are concerned about the recording of the physical location where the care to patient takes place rather than the organizational information. However, within the CiO information standard, the HealthcareProvider is only referenced indirectly via the PractitionerRole resource, hence a reference to the Organization profile is sufficient in those cases. The Location profile is mentioned in the table above for completeness purposes.<br /> <br /> === Relations between building blocks ===<br /> <br /> [[Bestand:Resources diagram CiO (beta.2).drawio.png|1000px]]<br /> <br /> == Mappings between profiles and data set ==<br /> <br /> Each transaction starts with links to the functional definition in an ART-DECOR publication and references one or several FHIR profiles. The FHIR profiles contain mappings to all data elements that are present in the functional data set (prefixed with ‘cio-dataelement-20-’).<br /> <br /> 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}} or {{fhir|.patient}} of each FHIR instance of each main building block (with the exception of RegistrationData).<br /> <br /> 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 Identifier, for example RelationHypersensitivity (cio-dataelement-20-734) in building block Hypersensitivity. 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]].<br /> <br /> == Patient identification ==<br /> <br /> This implementation guide assumes that the client system is able to make a connection to the right server that contains the patient's information. It does not provide information on finding the right server nor does it provide information about security. Moreover, each transaction is performed in the context of a specific patient, whose context might have been established using the authentication mechanisms described in external specifications such as the MedMij ‘Afsprakenstelsel’ or through the usage of search parameters for patient identification. <br /> <br /> Each server is required to perform filtering based on the patient associated with the context for the request or based on the patient identification search parameters, which is a [https://www.hl7.org/fhir/r4/search.html#chaining chained search parameter] for all resource types except Patient, so only the records associated with the authenticated patient are returned.<br /> <br /> When patient identification requires the use of search parameters, the following search parameters SHALL be supported:<br /> * Patient: {{fhir|identifier}}<br /> * Flag: {{fhir|patient.identifier}} and {{fhir|subject:Patient.identifier}}<br /> <br /> An example of a request that retrieves all Flag resources of a patient with a fake BSN of 111222333:<br /> <br /> &lt;pre&gt;GET [base]/Flag?patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&lt;/pre&gt;<br /> <br /> Most request examples in this IG do not include patient identification mechanisms. Requesters are assumed to include these if necessary.<br /> <br /> == Discussion ==<br /> <br /> As stated before, the current profiles cannot be considered to be stable and ready for use. This is partly due to the ongoing discussion about the exact scope and content of the functional building blocks in CiO. However, there are also some topics regarding the technical implementation that need to be addressed before considering the resulting FHIR profiles to be ready for use:<br /> <br /> * The functional data set defines several relations between different building blocks (concepts with a name starting with ‘Relation…’), which have been implemented in FHIR as custom extensions of data type ‘Reference’. Some of these refer to instances of the same building block and are meant to track updates done between different instances of the same building block. In that sense the approach of the Medication Process information standard is followed here, where such relations are used for building blocks that are changed or stopped. In FHIR however it is possible to just update existing resources resulting in a new version of the same instance, and therefore it is up for debate whether this approach is deemed necessary and desirable for the CiO use cases. In particular one might wonder whether this approach is justified for Flag resources, since this resource has a different nature than for instance medication-related resources. The conclusion on this topic also depends on the way object identification and mutations will be handled on a functional level within the CiO information standard. This has not been fully thought out yet and will be taken into consideration for the 2.0.0-beta.3 release.<br /> * This is the first release of an information standard making use of the Provenance resource to represent the concepts present within the zib RegistrationData (instead of defining additional extensions for concepts like RegistrationDateTime and InformationSource). The exact use of this resource on a broader level needs to be further analyzed (and generalized).<br /> * Several concepts within the Hypersensitivity and Reaction building blocks that are related to the underlying condition and diagnosis have been mapped to elements within a separate Condition profile, instead of adding them as extensions within the AllergyIntolerance profiles. It needs to be discussed whether this approach is feasible (also taking into account international standards) and whether this Condition resource has a ‘right’ to exist. Moreover, the Hypersensitivity and Reaction building blocks are modeled by different AllergyIntolerance profiles, as they are both representing diagnostic insight of a health professional regarding (the predisposition to develop) a reaction, while in core FHIR the relation between a hypersensitivity and reactions due to that hypersensitivity are modeled within one AllergyIntolerance. This discrepancy might result in difficulties when exchanging information on hypersensitivities and reactions on a broader/international scale. Both modeling approaches mentioned here need to be taken into account while deciding on the definitive modeling of the aforementioned building blocks.<br /> * The exact requirements regarding the search parameters used within CiO aren't fully fledged yet, especially the {{fhir|_revinclude}} defined on {{fhir|Provenance.target}}, and the possible requirement of an {{fhir|_include}} on the contents of the {{fhir|flag-detail}} extension (the latter being out of scope for this release). Note that in general, references are required to be either resolvable or readily available in the search request results; since the reference between the Provenance resource and other resources is reversed with respect to the focal resource of the search requests, supporting the {{fhir|_revinclude}} on {{fhir|Provenance.target}} is required. Further discussion with software suppliers is necessary to finalize these requirements.<br /> <br /> = Transactions =<br /> <br /> This section describes the FHIR implementation of all transactions listed in [[cio:V2.0.0-beta.2_Ontwerp_CiO#Usecases|section 2 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’.<br /> <br /> == Medication Contraindication (Retrieve/Serve) ==<br /> <br /> The retrieve medication contraindications transaction is used by the client to retrieve medication contraindications from a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Transaction group<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Transaction<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Actor<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| System role<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| FHIR CapabilityStatement<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/sc-2.16.840.1.113883.2.4.3.11.60.26.3.2-2019-08-28T133341.html#_2.16.840.1.113883.2.4.3.11.60.26.4.16_20200622101830 MedicationContraIndication (PULL)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/tr-2.16.840.1.113883.2.4.3.11.60.26.4.17-2020-06-22T101830.html Retrieving medication contraindications]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|CIO-MCIR<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/cio-MedicationContraindications.RetrieveServe|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}|title=CapabilityStatement Retrieve/serve medication contraindications}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/tr-2.16.840.1.113883.2.4.3.11.60.26.4.18-2020-06-22T101830.html Serving medication contraindications]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|CIO-MCIB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> <br /> When a health professional or healthcare provider wants to obtain all medication contraindications or specific ones matching various parameters, they issue a retrieve medication contraindications request message. This message uses the HTTP GET method parameterized query against the server's FHIR Flag endpoint.<br /> <br /> The search interaction is performed by an HTTP GET conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query.<br /> <br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|350241000146102&amp;_revinclude=Provenance:target{&amp;[additional parameter(s)]}&lt;/pre&gt;<br /> <br /> ==== Search parameters ====<br /> <br /> All search parameters listed in the table below SHALL be supported for processing by servers and MAY be supported by clients, with the exception of the {{fhir|category}} parameter, as well as the {{fhir|&lt;nowiki&gt;_revinclude=Provenance:target&lt;/nowiki&gt;}} search result parameter, which SHALL be supported by clients as well (as these are always part of the search query in this transaction).<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | CiO search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Description<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Example<br /> |-<br /> | -<br /> | Search on MedicationContraIndication building blocks (not taking into account the RegistrationData building block). <br /> | {{fhir|category}} &lt;ref name=&quot;custom-searchparameter&quot;&gt;The search parameter consists of a custom FHIR search parameter not represented in the FHIR specification.&lt;/ref&gt;<br /> | Flag<br /> | Retrieves all Flag resources representing a MedicationContraIndication.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|350241000146102&lt;/pre&gt;<br /> |-<br /> | -<br /> | Include the RegistrationData building block referenced from the MedicationContraIndication.<br /> | {{fhir|&lt;nowiki&gt;_revinclude=Provenance:target&lt;/nowiki&gt;}}<br /> | Flag<br /> | Retrieves all Flag and corresponding Provenance resources representing a MedicationContraIndication.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|350241000146102&amp;_revinclude=Provenance:target&lt;/pre&gt;<br /> |-<br /> | PatientIdentificationNumber<br /> | Search on patient.<br /> | {{fhir|patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;&gt;This search parameter only needs to be supported when patient identification requires the use of search parameters, see [[#Patient_identification|section 2.4]].&lt;/ref&gt;<br /> | Flag<br /> | Retrieves all MedicationContraIndication building blocks of a patient with a fake BSN of 111222333.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|350241000146102&amp;patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&amp;_revinclude=Provenance:target&lt;/pre&gt;<br /> |-<br /> | ReferenceDate<br /> | Search on the MedicationContraIndication building blocks that were active on or after a certain date.<br /> | {{fhir|date}}<br /> | Flag<br /> | Retrieves all MedicationContraIndication building blocks that were active from 01-05-2023.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|350241000146102&amp;date=ge2023-05-01&amp;_revinclude=Provenance:target&lt;/pre&gt;<br /> |-<br /> | -<br /> | The client may request that the server returns resources related to the search results, in order to reduce the overall network delay of repeated retrievals of related resources.<br /> Supporting the include of the Patient resource referenced by building blocks is required. Others (PractitionerRole, Practitioner, RelatedPerson, Organization) are optional. However: all resources referenced per literal reference SHALL be resolvable [[FHIR:V1.0_FHIR_IG_R4#Including_referenced_resources|per the Nictiz IG]].<br /> | {{fhir|&lt;nowiki&gt;_include=Flag:patient&lt;/nowiki&gt;}}<br /> | Flag<br /> | Retrieves all MedicationContraIndication building blocks of a patient with a fake BSN of 111222333 and includes the Patient resource in the search results.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|350241000146102&amp;patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&amp;_revinclude=Provenance:target&amp;_include=Flag:patient&lt;/pre&gt;<br /> |}<br /> <br /> The following custom search parameter is defined for this transaction:<br /> <br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/Flag-category|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> <br /> === Serve (response message) ===<br /> <br /> The server returns an HTTP Status code appropriate to the processing outcome and returns a Bundle, with {{fhir|Bundle.type}} = {{term|searchset}}, including the resources matching the search query. The resources included in the Bundle SHALL conform to the profiles listed in the ‘List of profiles’ below.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationContraIndication<br /> | MedicatieContraIndicatie<br /> | Flag<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-MedicationContraIndication|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | RegistrationData<br /> | RegistratieGegevens<br /> | Provenance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-RegistrationData|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | HealthcareProvider<br /> | Zorgaanbieder<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | ContactPerson<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |}<br /> <br /> == Medication Contraindication (Send/Receive) ==<br /> <br /> The send medication contraindications transaction is used by the client to send medication contraindications to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Transaction group<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Transaction<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Actor<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| System role<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| FHIR CapabilityStatement<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/sc-2.16.840.1.113883.2.4.3.11.60.26.3.2-2019-08-28T133341.html#_2.16.840.1.113883.2.4.3.11.60.26.4.10_20200622101711 MedicationContraIndication (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/tr-2.16.840.1.113883.2.4.3.11.60.26.4.11-2020-06-22T101711.html Sending medication contraindications]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|CIO-MCIS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/cio-MedicationContraIndications.SendReceive|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}|title=CapabilityStatement Send/receive medication contraindications}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication contraindications<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|CIO-MCIO<br /> |}<br /> <br /> === Send (request message) ===<br /> <br /> Because the data sent in this transaction potentially consists of several building blocks along with secondary resources, a [https://www.hl7.org/fhir/r4/http.html#transaction {{term|transaction}} interaction] is used. This allows for sending a Bundle with a set of resources in a single interaction and makes it possible to [[FHIR:V1.0_FHIR_IG_R4#Including_.22secondary.22_resources_when_sending_information|include referenced secondary resources]] if needed. The interaction is performed by an HTTP POST command as shown:<br /> <br /> &lt;pre&gt;POST [base]&lt;/pre&gt;<br /> <br /> The body of the POST submission is a Bundle with {{fhir|Bundle.type}} = {{term|transaction}}. Each entry SHALL carry request details ({{fhir|Bundle.entry.request}}) that provide the HTTP method of the action to be executed. Usually, this will be POST, even for informative secondary resources.<br /> <br /> The resources included in the Bundle SHALL conform to the profiles listed in the ‘List of profiles’ below.<br /> <br /> === Receive (response message) ===<br /> <br /> The server returns an HTTP Status code appropriate to the processing outcome. If the transaction is successful, the server returns a Bundle with {{fhir|Bundle.type}} = {{term|transaction-response}}, that contains one entry for each entry in the request, in the same order, with the outcome of processing the entry. Included secondary resources are handled [[FHIR:V1.0_FHIR_IG_R4#Including_.22secondary.22_resources_when_sending_information|following the Nictiz IG]].<br /> <br /> If the transaction fails, the server returns an OperationOutcome with one or multiple {{fhir|.issue}} elements filled with information, as detailed as possible, that describes why the transaction failed and which resource and/or request caused this.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | MedicationContraIndication<br /> | MedicatieContraIndicatie<br /> | Flag<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-MedicationContraIndication|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | RegistrationData<br /> | RegistratieGegevens<br /> | Provenance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-RegistrationData|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | HealthcareProvider<br /> | Zorgaanbieder<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | ContactPerson<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |}<br /> <br /> == Medication Hypersensitivity (Retrieve/Serve) ==<br /> <br /> The retrieve medication hypersensitivities transaction is used by the client to retrieve medication hypersensitivities from a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Transaction group<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Transaction<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Actor<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| System role<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| FHIR CapabilityStatement<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/sc-2.16.840.1.113883.2.4.3.11.60.26.3.2-2019-08-28T133341.html#_2.16.840.1.113883.2.4.3.11.60.26.4.34_20201021150632 MedicationHypersensitivity (PULL)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/tr-2.16.840.1.113883.2.4.3.11.60.26.4.35-2020-10-21T150632.html Retrieving medication hypersensitivities]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|CIO-GOR<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/cio-MedicationHypersensitivities.RetrieveServe|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}|title=CapabilityStatement Retrieve/serve medication hypersensitivities}}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/tr-2.16.840.1.113883.2.4.3.11.60.26.4.36-2020-10-21T150632.html Serving medication hypersensitivities]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|CIO-GOB<br /> |}<br /> <br /> === Retrieve (request message) ===<br /> <br /> When a health professional or healthcare provider wants to obtain all medication hypersensitivities or specific ones matching various parameters, they issue a retrieve medication hypersensitivities request message. This message uses the HTTP GET method parameterized query against the server's FHIR Flag endpoint.<br /> <br /> The search interaction is performed by an HTTP GET conform the [http://hl7.org/fhir/R4/search.html FHIR search specification], as shown below. This URL is configurable by the client by configuring the search query.<br /> <br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|225419007&amp;_revinclude=Provenance:target{&amp;[additional parameter(s)]}&lt;/pre&gt;<br /> <br /> References within the {{fhir|flag-detail}} extension (in the Flag resources present in the search result) to instances conforming to the cio-Hypersensitivity or cio-Reaction profiles can be resolved afterwards by individual read operations. The same holds true for instances conforming to the cio-Condition profile referenced from {{fhir|Provenance.target}}.<br /> <br /> ==== Search parameters ====<br /> <br /> All search parameters listed in the table below SHALL be supported for processing by servers and MAY be supported by clients, with the exception of the {{fhir|category}} parameter, as well as the {{fhir|&lt;nowiki&gt;_revinclude=Provenance:target&lt;/nowiki&gt;}} search result parameter, which SHALL be supported by clients as well (as these are always part of the search query in this transaction).<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | CiO search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Description<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR search parameter<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Example<br /> |-<br /> | -<br /> | Search on SurveillanceDecision building blocks (not taking into account the RegistrationData building block). <br /> | {{fhir|category}} &lt;ref name=&quot;custom-searchparameter&quot;&gt;The search parameter consists of a custom FHIR search parameter not represented in the FHIR specification.&lt;/ref&gt;<br /> | Flag<br /> | Retrieves all Flag resources representing a SurveillanceDecision.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|225419007&lt;/pre&gt;<br /> |-<br /> | -<br /> | Include the RegistrationData building block referenced from the SurveillanceDecision.<br /> | {{fhir|&lt;nowiki&gt;_revinclude=Provenance:target&lt;/nowiki&gt;}}<br /> | Flag<br /> | Retrieves all Flag and corresponding Provenance resources representing a SurveillanceDecision.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|225419007&amp;_revinclude=Provenance:target&lt;/pre&gt;<br /> |-<br /> | PatientIdentificationNumber<br /> | Search on patient.<br /> | {{fhir|patient.identifier}} &lt;ref name=&quot;patient-searchparameter&quot;&gt;This search parameter only needs to be supported when patient identification requires the use of search parameters, see [[#Patient_identification|section 2.4]].&lt;/ref&gt;<br /> | Flag<br /> | Retrieves all SurveillanceDecision building blocks of a patient with a fake BSN of 111222333.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|225419007&amp;patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&amp;_revinclude=Provenance:target&lt;/pre&gt;<br /> |-<br /> | ReferenceDate<br /> | Search on the SurveillanceDecision building blocks that were active on or after a certain date.<br /> | {{fhir|date}}<br /> | Flag<br /> | Retrieves all SurveillanceDecision building blocks that were active from 01-05-2023.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|225419007&amp;date=ge2023-05-01&amp;_revinclude=Provenance:target&lt;/pre&gt;<br /> |-<br /> | -<br /> | The client may request that the server returns resources related to the search results, in order to reduce the overall network delay of repeated retrievals of related resources.<br /> References to AllergyIntolerance and Condition resources are resolved by individual read operations, as mentioned above. Supporting the include of the Patient resource referenced by building blocks is required. Others (PractitionerRole, Practitioner, RelatedPerson, Organization) are optional. However: all resources referenced per literal reference SHALL be resolvable [[FHIR:V1.0_FHIR_IG_R4#Including_referenced_resources|per the Nictiz IG]].<br /> | {{fhir|&lt;nowiki&gt;_include=Flag:patient&lt;/nowiki&gt;}}<br /> | Flag<br /> | Retrieves all SurveillanceDecision building blocks of a patient with a fake BSN of 111222333 and includes the Patient resource in the search results.<br /> &lt;pre&gt;GET [base]/Flag?category=http://snomed.info/sct|225419007&amp;patient.identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&amp;_revinclude=Provenance:target&amp;_include=Flag:patient&lt;/pre&gt;<br /> |}<br /> <br /> The following custom search parameter is defined for this transaction:<br /> <br /> * {{Simplifier|http://nictiz.nl/fhir/SearchParameter/Flag-category|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> <br /> === Serve (response message) ===<br /> <br /> The server returns an HTTP Status code appropriate to the processing outcome and returns a Bundle, with {{fhir|Bundle.type}} = {{term|searchset}}, including the resources matching the search query. The resources included in the Bundle SHALL conform to the profiles listed in the ‘List of profiles’ below.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | SurveillanceDecision<br /> | BewakingBesluit<br /> | Flag<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-SurveillanceDecision|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Hypersensitivity<br /> | Overgevoeligheid<br /> | AllergyIntolerance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Hypersensitivity|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Reaction<br /> | Reactie<br /> | AllergyIntolerance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Reaction|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Condition<br /> | Aandoening<br /> | Condition<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Condition|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | RegistrationData<br /> | RegistratieGegevens<br /> | Provenance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-RegistrationData|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | HealthcareProvider<br /> | Zorgaanbieder<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | ContactPerson<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |}<br /> <br /> == Medication Hypersensitivity (Send/Receive) ==<br /> <br /> The send medication hypersensitivities transaction is used by the client to send medication hypersensitivities to a server.<br /> <br /> {| class=&quot;wikitable&quot; &quot;cellpadding=&quot;10&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Transaction group<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Transaction<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| Actor<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| System role<br /> ! style=&quot;font-weight: bold;text-align:left;&quot;| FHIR CapabilityStatement<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/sc-2.16.840.1.113883.2.4.3.11.60.26.3.2-2019-08-28T133341.html#_2.16.840.1.113883.2.4.3.11.60.26.4.31_20201021150608 MedicationHypersensitivity (PUSH)] <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|[https://decor.nictiz.nl/pub/cio/cio-html-20231214T100742/tr-2.16.840.1.113883.2.4.3.11.60.26.4.32-2020-10-21T150608.html Sending medication hypersensitivities ]<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Client <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|CIO-GOS<br /> |style=&quot;background-color: white;vertical-align:top;&quot; rowspan=&quot;2&quot;|{{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/cio-MedicationHypersensitivities.SendReceive|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}|title=CapabilityStatement Send/receive medication hypersensitivities }}<br /> |-<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Receiving medication hypersensitivities <br /> |style=&quot;background-color: white;vertical-align:top;&quot;|Server<br /> |style=&quot;background-color: white;vertical-align:top;&quot;|CIO-GOO<br /> |}<br /> <br /> === Send (request message) ===<br /> <br /> Because the data sent in this transaction potentially consists of several building blocks along with secondary resources, a [https://www.hl7.org/fhir/r4/http.html#transaction {{term|transaction}} interaction] is used. This allows for sending a Bundle with a set of resources in a single interaction and makes it possible to [[FHIR:V1.0_FHIR_IG_R4#Including_.22secondary.22_resources_when_sending_information|include referenced secondary resources]] if needed. The interaction is performed by an HTTP POST command as shown:<br /> <br /> &lt;pre&gt;POST [base]&lt;/pre&gt;<br /> <br /> The body of the POST submission is a Bundle with {{fhir|Bundle.type}} = {{term|transaction}}. Each entry SHALL carry request details ({{fhir|Bundle.entry.request}}) that provide the HTTP method of the action to be executed. Usually, this will be POST, even for informative secondary resources.<br /> <br /> The resources included in the Bundle SHALL conform to the profiles listed in the ‘List of profiles’ below.<br /> <br /> === Receive (response message) ===<br /> <br /> The server returns an HTTP Status code appropriate to the processing outcome. If the transaction is successful, the server returns a Bundle with {{fhir|Bundle.type}} = {{term|transaction-response}}, that contains one entry for each entry in the request, in the same order, with the outcome of processing the entry. Included secondary resources are handled [[FHIR:V1.0_FHIR_IG_R4#Including_.22secondary.22_resources_when_sending_information|following the Nictiz IG]].<br /> <br /> If the transaction fails, the server returns an OperationOutcome with one or multiple {{fhir|.issue}} elements filled with information, as detailed as possible, that describes why the transaction failed and which resource and/or request caused this.<br /> <br /> === List of profiles ===<br /> <br /> The table below includes all profiles that are explicitly mentioned in the data set of this transaction, and thus need to be supported.<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (EN)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | Building block (NL)<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR resource<br /> ! style=&quot;font-weight: bold;text-align:left;&quot; | FHIR profile<br /> |-<br /> | SurveillanceDecision<br /> | BewakingBesluit<br /> | Flag<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-SurveillanceDecision|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Hypersensitivity<br /> | Overgevoeligheid<br /> | AllergyIntolerance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Hypersensitivity|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Reaction<br /> | Reactie<br /> | AllergyIntolerance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Reaction|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Condition<br /> | Aandoening<br /> | Condition<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-Condition|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | RegistrationData<br /> | RegistratieGegevens<br /> | Provenance<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/cio-RegistrationData|nictiz.fhir.nl.r4.cio|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.cio|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Patient<br /> | Patient<br /> | Patient<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | rowspan=&quot;2&quot; | HealthProfessional<br /> | rowspan=&quot;2&quot; | Zorgverlener<br /> | PractitionerRole<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | Practitioner<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | HealthcareProvider<br /> | Zorgaanbieder<br /> | Organization<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |-<br /> | ContactPerson<br /> | Contactpersoon<br /> | RelatedPerson<br /> | {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson|nictiz.fhir.nl.r4.nl-core|pkgVersion={{VersieInfo|nictiz.fhir.nl.r4.nl-core|release=V2.0.0-beta.2|namespace=cio}}}}<br /> |}<br /> <br /> = Release notes =<br /> <br /> Release notes can be found on the [[cio:V2.0.0-beta.2_Ontwerp_CiO#Release_Notes| functional design page]].<br /> <br /> = Footnotes =</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=cio:V2.0.0-beta.2_testgegevens_bgmo_addendum&diff=197169 2024-01-25T09:22:16Z

<p>Luud Slagter: NICTIZ-9056: Small textual improvement</p> <hr /> <div><br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:Beschikbaarstellen geneesmiddelovergevoeligheden: addendum inhoudelijke gegevens}}<br /> <br /> =Addenda voor inhoudelijke gegevens=<br /> &lt;section begin=cio-bgmo-tst-0.2-minimaalBB /&gt;<br /> ==Scenario 0.2 - minimaal BB==<br /> <br /> === &lt;span id=&quot;Pat02&quot; title=&quot;Intern ID Pat02&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;Pat02&quot; title=&quot;Intern ID = Pat02&quot;&gt;&lt;span id=&quot;Pat02&quot; title=&quot;Intern ID Pat02&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Wilma<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|W<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX_Zwaan<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999901199 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|30 nov 1965<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Vrouw (code = 'F' in codeSystem 'HL7 AdministrativeGender')<br /> |}<br /> === Geneesmiddelovergevoeligheid - IBUPROFEN===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - IBUPROFEN<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 dagen om 09:10:54 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|IBUPROFEN (code = '1155' in codeSystem 'G-Standaard generieke namen (bestand 750)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGeg-pat02-BB-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|zwelling van lippen en tong na gebruik van ibuprofen tabletten<br /> |}<br /> === Bouwstenen===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;6&quot; | Bouwstenen<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;5&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGeg-pat02-BB-01&quot; title=&quot;Intern ID = RegGeg-pat02-BB-01&quot;&gt;Registratie gegevens RegGeg-pat02-BB-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat02-BB-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 dagen om 09:10:54 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;zv-Peter-van-Pulver&quot; title=&quot;Intern ID = zv-Peter-van-Pulver&quot;&gt;Zorgverlener zv-Peter-van-Pulver&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|000001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.139)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Peter<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels<br /> |style=&quot;background-color: white;&quot;|van<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Huisartsen, niet nader gespecificeerd (code = '0100' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder<br /> |style=&quot;background-color: white;&quot;|za-Huisartsenpraktijk-Pulver-en-Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;za-Huisartsenpraktijk-Pulver-en-Partners&quot; title=&quot;Intern ID = za-Huisartsenpraktijk-Pulver-en-Partners&quot;&gt;Zorgaanbieder za-Huisartsenpraktijk-Pulver-en-Partners&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder identificatienummer<br /> |style=&quot;background-color: white;&quot;|00001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.205)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie naam<br /> |style=&quot;background-color: white;&quot;|Huisartsenpraktijk Pulver &amp; Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Dorpstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|1234AA<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Ons Dorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |}&lt;section end=cio-bgmo-tst-0.2-minimaalBB /&gt;<br /> &lt;section begin=cio-bgmo-tst-0.3-maximaalBB /&gt;<br /> ==Scenario 0.3 - maximaal BB, O, R==<br /> <br /> === &lt;span id=&quot;Pat03&quot; title=&quot;Intern ID Pat03&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;Pat03&quot; title=&quot;Intern ID = Pat03&quot;&gt;&lt;span id=&quot;Pat03&quot; title=&quot;Intern ID Pat03&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|David<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|D<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX_Lamet<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999901229 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|3 dec 1965<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Man (code = 'M' in codeSystem 'HL7 AdministrativeGender')<br /> |}<br /> === Geneesmiddelovergevoeligheid - PENICILLINES===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - PENICILLINES<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 108 dagen om 11:15:46 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-BB-01<br /> |}<br /> === Geneesmiddelovergevoeligheid - PENICILLINES===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - PENICILLINES<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Discontinued (qualifier value) (code = '410546004' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:23:05 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-BB-02<br /> |}<br /> === Geneesmiddelovergevoeligheid - PENICILLINES===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - PENICILLINES<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;14&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:25:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Besluit grond<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Overgevoeligheid<br /> |style=&quot;background-color: white;&quot;|pat03-overgevoeligheid-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Veilig binnen onveilige groep<br /> |style=&quot;background-color: white;&quot;|FLUCLOXACILLINE (code = '40991' in codeSystem 'G-Standaard generieke namen (Bestand 750)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-BB-03<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|&lt;span id=&quot;pat03-overgevoeligheid-01&quot; title=&quot;Intern ID = pat03-overgevoeligheid-01&quot;&gt;Overgevoeligheid pat03-overgevoeligheid-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;21&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 105 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening ernst<br /> |style=&quot;background-color: white;&quot;|Matig (code = '6736007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening aanwezigheid<br /> |style=&quot;background-color: white;&quot;|Known present (qualifier value) (code = '410515003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening status datum<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Agens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van vaststellen<br /> |style=&quot;background-color: white;&quot;|History and physical examination with evaluation and management of patient (procedure) (code = '14736009' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zekerheid status<br /> |style=&quot;background-color: white;&quot;|Confirmed present (qualifier value) (code = '410605003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Overgevoeligheid categorie<br /> |style=&quot;background-color: white;&quot;|geneesmiddelen (code = '419511003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Verwacht risico bij blootstelling<br /> |style=&quot;background-color: white;&quot;|Severe (severity modifier) (qualifier value) (code = '24484000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Diagnose naam<br /> |style=&quot;background-color: white;&quot;|overgevoeligheid voor meerdere geneesmiddelen (aandoening) (code = '735458004' in codeSystem 'SNOMED Clinical Terms')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Diagnostisch inzicht datum<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose steller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-overg-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Vastgesteld middels huidpriktest. Flucloxacilline wordt wel goed verdragen door patiënt.<br /> |}<br /> === Geneesmiddelovergevoeligheid - AMLODIPINE===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - AMLODIPINE<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;14&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 730 dagen om 09:57:02 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Besluit grond<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Reactie<br /> |style=&quot;background-color: white;&quot;|pat03-reactie-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|AMLODIPINE (code = '62081' in codeSystem 'G-Standaard generieke namen (bestand 750)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-BB-04<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Invaliderende bijwerking bij amlodipine tablet gebruik i.h.k.v. angina pectoris<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|&lt;span id=&quot;pat03-reactie-01&quot; title=&quot;Intern ID = pat03-reactie-01&quot;&gt;Reactie pat03-reactie-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;21&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening ernst<br /> |style=&quot;background-color: white;&quot;|Ernstig (code = '24484000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening aanwezigheid<br /> |style=&quot;background-color: white;&quot;|Known present (qualifier value) (code = '410515003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening status datum<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Veroorzaker<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Veroorzakende stof<br /> |style=&quot;background-color: white;&quot;|NORVASC TABLET 5MG (code = '642916G-Standaard HPK')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van blootstelling<br /> |style=&quot;background-color: white;&quot;|ORAAL (code = '9' in codeSystem 'G-Standaard Toedieningswegen (tabel 7)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Blootstelling datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van vaststellen<br /> |style=&quot;background-color: white;&quot;|History taking (procedure) (code = '84100007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zekerheid status<br /> |style=&quot;background-color: white;&quot;|Suspected (qualifier value) (code = '415684004' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reactie verschijnsel<br /> |style=&quot;background-color: white;&quot;|Invaliderende hoofdpijn bij gebruik amlodipine<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Diagnose naam<br /> |style=&quot;background-color: white;&quot;|overgevoeligheidsreactie (aandoening) (code = '421961002' in codeSystem 'SNOMED Clinical Terms')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Diagnostisch inzicht datum<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose steller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-reactie-01<br /> |}<br /> === Bouwstenen===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;6&quot; | Bouwstenen<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;5&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-01&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-01&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;8&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Pat03<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-02&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-02&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-02&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;5&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-02 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-03&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-03&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-03&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-03 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:25:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-04&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-04&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-04&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;9&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-04 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 730 dagen om 09:57:02 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Pat03<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-overg-01&quot; title=&quot;Intern ID = RegGegevens-pat03-overg-01&quot;&gt;Registratie gegevens RegGegevens-pat03-overg-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-overgevoeligheid-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.3)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:25:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-reactie-01&quot; title=&quot;Intern ID = RegGegevens-pat03-reactie-01&quot;&gt;Registratie gegevens RegGegevens-pat03-reactie-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-reactie-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.4)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 730 dagen om 09:57:02 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;zv-Peter-van-Pulver&quot; title=&quot;Intern ID = zv-Peter-van-Pulver&quot;&gt;Zorgverlener zv-Peter-van-Pulver&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|000001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.139)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Peter<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels<br /> |style=&quot;background-color: white;&quot;|van<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Huisartsen, niet nader gespecificeerd (code = '0100' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder<br /> |style=&quot;background-color: white;&quot;|za-Huisartsenpraktijk-Pulver-en-Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;za-Huisartsenpraktijk-Pulver-en-Partners&quot; title=&quot;Intern ID = za-Huisartsenpraktijk-Pulver-en-Partners&quot;&gt;Zorgaanbieder za-Huisartsenpraktijk-Pulver-en-Partners&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder identificatienummer<br /> |style=&quot;background-color: white;&quot;|00001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.205)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie naam<br /> |style=&quot;background-color: white;&quot;|Huisartsenpraktijk Pulver &amp; Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Dorpstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|1234AA<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Ons Dorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |}&lt;section end=cio-bgmo-tst-0.3-maximaalBB /&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=cio:V2.0.0-beta.2_testgegevens_bmci_addendum&diff=197163 2024-01-25T09:19:52Z

<p>Luud Slagter: NICTIZ-9056: Small textual improvement</p> <hr /> <div><br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:Beschikbaarstellen medicatiecontra-indicaties: addendum inhoudelijke gegevens}}<br /> <br /> =Addenda voor inhoudelijke gegevens=<br /> &lt;section begin=cio-bmci-tst-0.2-meerdereMCi /&gt;<br /> ==Scenario 0.2 - meerdere MCi==<br /> <br /> === &lt;span id=&quot;Pat02&quot; title=&quot;Intern ID Pat02&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;Pat02&quot; title=&quot;Intern ID = Pat02&quot;&gt;&lt;span id=&quot;Pat02&quot; title=&quot;Intern ID Pat02&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Wilma<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|W<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX_Zwaan<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999901199 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|30 nov 1965<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Vrouw (code = 'F' in codeSystem 'HL7 AdministrativeGender')<br /> |}<br /> === Medicatie contra indicatie - Epilepsie===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Medicatie contra indicatie - Epilepsie<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Alert<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;8&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Alert type<br /> |style=&quot;background-color: white;&quot;|Potentiële contra-indicatie voor geneesmiddel (bevinding) (code = '350241000146102' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Alert naam<br /> |style=&quot;background-color: white;&quot;|Epilepsie (code = '42' in codeSystem 'G-standaard Contra Indicaties (Thesaurus 40)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 20 jaar om 13:20:48 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Vaststeller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-N-van-Erven<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGeg-pat02-mci-epi-01<br /> |}<br /> === Medicatie contra indicatie - Zwangerschap===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Medicatie contra indicatie - Zwangerschap<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Alert<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;9&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Alert type<br /> |style=&quot;background-color: white;&quot;|Potentiële contra-indicatie voor geneesmiddel (bevinding) (code = '350241000146102' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Alert naam<br /> |style=&quot;background-color: white;&quot;|Zwangerschap (code = '1320' in codeSystem 'G-standaard Contra Indicaties (Thesaurus 40)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 jaar en 10 maanden om 08:54:38 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Vaststeller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGeg-pat02-mci-zwa-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Additionele informatie over alert zwangerschap<br /> |}<br /> === Medicatie contra indicatie - Zwangerschap===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Medicatie contra indicatie - Zwangerschap<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Alert<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;13&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Alert type<br /> |style=&quot;background-color: white;&quot;|Potentiële contra-indicatie voor geneesmiddel (bevinding) (code = '350241000146102' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Alert naam<br /> |style=&quot;background-color: white;&quot;|Zwangerschap (code = '1320' in codeSystem 'G-standaard Contra Indicaties (Thesaurus 40)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 jaar en 10 maanden om 08:54:38 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Eind datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 jaar om 10:11:42 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reden beeindiging alert<br /> |style=&quot;background-color: white;&quot;|patiënt niet meer zwanger<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Vaststeller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Relatie alert<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Identificatie<br /> |style=&quot;background-color: white;&quot;|pat02-mci-zwa-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGeg-pat02-mci-zwa-02<br /> |}<br /> === Bouwstenen===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;6&quot; | Bouwstenen<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;5&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGeg-pat02-mci-epi-01&quot; title=&quot;Intern ID = RegGeg-pat02-mci-epi-01&quot;&gt;Registratie gegevens RegGeg-pat02-mci-epi-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat02-mci-epi-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.16)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-N-van-Erven<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 20 jaar om 13:20:48 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGeg-pat02-mci-zwa-01&quot; title=&quot;Intern ID = RegGeg-pat02-mci-zwa-01&quot;&gt;Registratie gegevens RegGeg-pat02-mci-zwa-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat02-mci-zwa-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.16)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 jaar om 08:54:38 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGeg-pat02-mci-zwa-02&quot; title=&quot;Intern ID = RegGeg-pat02-mci-zwa-02&quot;&gt;Registratie gegevens RegGeg-pat02-mci-zwa-02&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat02-mci-zwa-02 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.16)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 jaar en 10 maanden om 10:11:42 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;zv-N-van-Erven&quot; title=&quot;Intern ID = zv-N-van-Erven&quot;&gt;Zorgverlener zv-N-van-Erven&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|000003332 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.139)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|N<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels<br /> |style=&quot;background-color: white;&quot;|van<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Erven<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Medisch specialisten, neurologie (code = '0330' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder<br /> |style=&quot;background-color: white;&quot;|za-Algemeen-Stadsziekenhuis<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;zv-Peter-van-Pulver&quot; title=&quot;Intern ID = zv-Peter-van-Pulver&quot;&gt;Zorgverlener zv-Peter-van-Pulver&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;12&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|000001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.139)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;7&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Peter<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|P<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels<br /> |style=&quot;background-color: white;&quot;|van<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Huisartsen, niet nader gespecificeerd (code = '0100' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder<br /> |style=&quot;background-color: white;&quot;|za-Huisartsenpraktijk-Pulver-en-Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;za-Algemeen-Stadsziekenhuis&quot; title=&quot;Intern ID = za-Algemeen-Stadsziekenhuis&quot;&gt;Zorgaanbieder za-Algemeen-Stadsziekenhuis&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder identificatienummer<br /> |style=&quot;background-color: white;&quot;|00002222 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.205)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie naam<br /> |style=&quot;background-color: white;&quot;|Algemeen Stadsziekenhuis<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Afdeling specialisme<br /> |style=&quot;background-color: white;&quot;|Medisch specialisten, neurologie (code = '0330' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Hoofdstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|2143AA<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Zorgstad<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;za-Huisartsenpraktijk-Pulver-en-Partners&quot; title=&quot;Intern ID = za-Huisartsenpraktijk-Pulver-en-Partners&quot;&gt;Zorgaanbieder za-Huisartsenpraktijk-Pulver-en-Partners&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder identificatienummer<br /> |style=&quot;background-color: white;&quot;|00001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.205)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie naam<br /> |style=&quot;background-color: white;&quot;|Huisartsenpraktijk Pulver &amp; Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Dorpstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|1234AA<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Ons Dorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |}&lt;section end=cio-bmci-tst-0.2-meerdereMCi /&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=cio:V2.0.0-beta.2_testgegevens_bgmo_addendum&diff=197138 2024-01-24T11:03:05Z

<p>Luud Slagter: NICTIZ-9056: Removed empty scenarios</p> <hr /> <div><br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:Beschikbaarstellen geneesmiddelovergevoeligheden: addendum inhoudelijke gegevens}}<br /> <br /> =Addenda voor inhoudelijke gegevens=<br /> &lt;section begin=cio-bgmo-tst-0.2-minimaalBB /&gt;<br /> ==Scenario 0.2 - minimaal BB - ==<br /> <br /> === &lt;span id=&quot;Pat02&quot; title=&quot;Intern ID Pat02&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;Pat02&quot; title=&quot;Intern ID = Pat02&quot;&gt;&lt;span id=&quot;Pat02&quot; title=&quot;Intern ID Pat02&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Wilma<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|W<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX_Zwaan<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999901199 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|30 nov 1965<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Vrouw (code = 'F' in codeSystem 'HL7 AdministrativeGender')<br /> |}<br /> === Geneesmiddelovergevoeligheid - IBUPROFEN===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - IBUPROFEN<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 dagen om 09:10:54 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|IBUPROFEN (code = '1155' in codeSystem 'G-Standaard generieke namen (bestand 750)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGeg-pat02-BB-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|zwelling van lippen en tong na gebruik van ibuprofen tabletten<br /> |}<br /> === Bouwstenen===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;6&quot; | Bouwstenen<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;5&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGeg-pat02-BB-01&quot; title=&quot;Intern ID = RegGeg-pat02-BB-01&quot;&gt;Registratie gegevens RegGeg-pat02-BB-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat02-BB-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 dagen om 09:10:54 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;zv-Peter-van-Pulver&quot; title=&quot;Intern ID = zv-Peter-van-Pulver&quot;&gt;Zorgverlener zv-Peter-van-Pulver&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|000001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.139)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Peter<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels<br /> |style=&quot;background-color: white;&quot;|van<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Huisartsen, niet nader gespecificeerd (code = '0100' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder<br /> |style=&quot;background-color: white;&quot;|za-Huisartsenpraktijk-Pulver-en-Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;za-Huisartsenpraktijk-Pulver-en-Partners&quot; title=&quot;Intern ID = za-Huisartsenpraktijk-Pulver-en-Partners&quot;&gt;Zorgaanbieder za-Huisartsenpraktijk-Pulver-en-Partners&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder identificatienummer<br /> |style=&quot;background-color: white;&quot;|00001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.205)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie naam<br /> |style=&quot;background-color: white;&quot;|Huisartsenpraktijk Pulver &amp; Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Dorpstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|1234AA<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Ons Dorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |}&lt;section end=cio-bgmo-tst-0.2-minimaalBB /&gt;<br /> &lt;section begin=cio-bgmo-tst-0.3-maximaalBB /&gt;<br /> ==Scenario 0.3 - maximaal BB, O, R - ==<br /> <br /> === &lt;span id=&quot;Pat03&quot; title=&quot;Intern ID Pat03&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;Pat03&quot; title=&quot;Intern ID = Pat03&quot;&gt;&lt;span id=&quot;Pat03&quot; title=&quot;Intern ID Pat03&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|David<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|D<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX_Lamet<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999901229 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|3 dec 1965<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Man (code = 'M' in codeSystem 'HL7 AdministrativeGender')<br /> |}<br /> === Geneesmiddelovergevoeligheid - PENICILLINES===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - PENICILLINES<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 108 dagen om 11:15:46 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-BB-01<br /> |}<br /> === Geneesmiddelovergevoeligheid - PENICILLINES===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - PENICILLINES<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Discontinued (qualifier value) (code = '410546004' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:23:05 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-BB-02<br /> |}<br /> === Geneesmiddelovergevoeligheid - PENICILLINES===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - PENICILLINES<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;14&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:25:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Besluit grond<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Overgevoeligheid<br /> |style=&quot;background-color: white;&quot;|pat03-overgevoeligheid-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Veilig binnen onveilige groep<br /> |style=&quot;background-color: white;&quot;|FLUCLOXACILLINE (code = '40991' in codeSystem 'G-Standaard generieke namen (Bestand 750)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-BB-03<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|&lt;span id=&quot;pat03-overgevoeligheid-01&quot; title=&quot;Intern ID = pat03-overgevoeligheid-01&quot;&gt;Overgevoeligheid pat03-overgevoeligheid-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;21&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 105 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening ernst<br /> |style=&quot;background-color: white;&quot;|Matig (code = '6736007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening aanwezigheid<br /> |style=&quot;background-color: white;&quot;|Known present (qualifier value) (code = '410515003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening status datum<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Agens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van vaststellen<br /> |style=&quot;background-color: white;&quot;|History and physical examination with evaluation and management of patient (procedure) (code = '14736009' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zekerheid status<br /> |style=&quot;background-color: white;&quot;|Confirmed present (qualifier value) (code = '410605003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Overgevoeligheid categorie<br /> |style=&quot;background-color: white;&quot;|geneesmiddelen (code = '419511003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Verwacht risico bij blootstelling<br /> |style=&quot;background-color: white;&quot;|Severe (severity modifier) (qualifier value) (code = '24484000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Diagnose naam<br /> |style=&quot;background-color: white;&quot;|overgevoeligheid voor meerdere geneesmiddelen (aandoening) (code = '735458004' in codeSystem 'SNOMED Clinical Terms')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Diagnostisch inzicht datum<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose steller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-overg-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Vastgesteld middels huidpriktest. Flucloxacilline wordt wel goed verdragen door patiënt.<br /> |}<br /> === Geneesmiddelovergevoeligheid - AMLODIPINE===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - AMLODIPINE<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;14&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 730 dagen om 09:57:02 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Besluit grond<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Reactie<br /> |style=&quot;background-color: white;&quot;|pat03-reactie-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|AMLODIPINE (code = '62081' in codeSystem 'G-Standaard generieke namen (bestand 750)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-BB-04<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Invaliderende bijwerking bij amlodipine tablet gebruik i.h.k.v. angina pectoris<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|&lt;span id=&quot;pat03-reactie-01&quot; title=&quot;Intern ID = pat03-reactie-01&quot;&gt;Reactie pat03-reactie-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;21&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening ernst<br /> |style=&quot;background-color: white;&quot;|Ernstig (code = '24484000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening aanwezigheid<br /> |style=&quot;background-color: white;&quot;|Known present (qualifier value) (code = '410515003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening status datum<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Veroorzaker<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Veroorzakende stof<br /> |style=&quot;background-color: white;&quot;|NORVASC TABLET 5MG (code = '642916G-Standaard HPK')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van blootstelling<br /> |style=&quot;background-color: white;&quot;|ORAAL (code = '9' in codeSystem 'G-Standaard Toedieningswegen (tabel 7)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Blootstelling datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van vaststellen<br /> |style=&quot;background-color: white;&quot;|History taking (procedure) (code = '84100007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zekerheid status<br /> |style=&quot;background-color: white;&quot;|Suspected (qualifier value) (code = '415684004' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reactie verschijnsel<br /> |style=&quot;background-color: white;&quot;|Invaliderende hoofdpijn bij gebruik amlodipine<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Diagnose naam<br /> |style=&quot;background-color: white;&quot;|overgevoeligheidsreactie (aandoening) (code = '421961002' in codeSystem 'SNOMED Clinical Terms')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Diagnostisch inzicht datum<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose steller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-reactie-01<br /> |}<br /> === Bouwstenen===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;6&quot; | Bouwstenen<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;5&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-01&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-01&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;8&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Pat03<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-02&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-02&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-02&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;5&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-02 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-03&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-03&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-03&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-03 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:25:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-04&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-04&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-04&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;9&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-04 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 730 dagen om 09:57:02 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Pat03<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-overg-01&quot; title=&quot;Intern ID = RegGegevens-pat03-overg-01&quot;&gt;Registratie gegevens RegGegevens-pat03-overg-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-overgevoeligheid-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.3)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:25:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-reactie-01&quot; title=&quot;Intern ID = RegGegevens-pat03-reactie-01&quot;&gt;Registratie gegevens RegGegevens-pat03-reactie-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-reactie-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.4)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 730 dagen om 09:57:02 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;zv-Peter-van-Pulver&quot; title=&quot;Intern ID = zv-Peter-van-Pulver&quot;&gt;Zorgverlener zv-Peter-van-Pulver&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|000001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.139)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Peter<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels<br /> |style=&quot;background-color: white;&quot;|van<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Huisartsen, niet nader gespecificeerd (code = '0100' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder<br /> |style=&quot;background-color: white;&quot;|za-Huisartsenpraktijk-Pulver-en-Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;za-Huisartsenpraktijk-Pulver-en-Partners&quot; title=&quot;Intern ID = za-Huisartsenpraktijk-Pulver-en-Partners&quot;&gt;Zorgaanbieder za-Huisartsenpraktijk-Pulver-en-Partners&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder identificatienummer<br /> |style=&quot;background-color: white;&quot;|00001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.205)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie naam<br /> |style=&quot;background-color: white;&quot;|Huisartsenpraktijk Pulver &amp; Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Dorpstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|1234AA<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Ons Dorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |}&lt;section end=cio-bgmo-tst-0.3-maximaalBB /&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=cio:V2.0.0-beta.2_testgegevens_bmci_addendum&diff=197137 2024-01-24T11:02:38Z

<p>Luud Slagter: NICTIZ-9056: Removed empty scenarios, added additional elements</p> <hr /> <div><br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:Beschikbaarstellen medicatiecontra-indicaties: addendum inhoudelijke gegevens}}<br /> <br /> =Addenda voor inhoudelijke gegevens=<br /> &lt;section begin=cio-bmci-tst-0.2-meerdereMCi /&gt;<br /> ==Scenario 0.2 - meerdere MCi - ==<br /> <br /> === &lt;span id=&quot;Pat02&quot; title=&quot;Intern ID Pat02&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;Pat02&quot; title=&quot;Intern ID = Pat02&quot;&gt;&lt;span id=&quot;Pat02&quot; title=&quot;Intern ID Pat02&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Wilma<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|W<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX_Zwaan<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999901199 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|30 nov 1965<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Vrouw (code = 'F' in codeSystem 'HL7 AdministrativeGender')<br /> |}<br /> === Medicatie contra indicatie - Epilepsie===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Medicatie contra indicatie - Epilepsie<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Alert<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;8&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Alert type<br /> |style=&quot;background-color: white;&quot;|Potentiële contra-indicatie voor geneesmiddel (bevinding) (code = '350241000146102' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Alert naam<br /> |style=&quot;background-color: white;&quot;|Epilepsie (code = '42' in codeSystem 'G-standaard Contra Indicaties (Thesaurus 40)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 20 jaar om 13:20:48 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Vaststeller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-N-van-Erven<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGeg-pat02-mci-epi-01<br /> |}<br /> === Medicatie contra indicatie - Zwangerschap===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Medicatie contra indicatie - Zwangerschap<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Alert<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;9&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Alert type<br /> |style=&quot;background-color: white;&quot;|Potentiële contra-indicatie voor geneesmiddel (bevinding) (code = '350241000146102' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Alert naam<br /> |style=&quot;background-color: white;&quot;|Zwangerschap (code = '1320' in codeSystem 'G-standaard Contra Indicaties (Thesaurus 40)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 jaar en 10 maanden om 08:54:38 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Vaststeller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGeg-pat02-mci-zwa-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Additionele informatie over alert zwangerschap<br /> |}<br /> === Medicatie contra indicatie - Zwangerschap===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Medicatie contra indicatie - Zwangerschap<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Alert<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;13&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Alert type<br /> |style=&quot;background-color: white;&quot;|Potentiële contra-indicatie voor geneesmiddel (bevinding) (code = '350241000146102' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Alert naam<br /> |style=&quot;background-color: white;&quot;|Zwangerschap (code = '1320' in codeSystem 'G-standaard Contra Indicaties (Thesaurus 40)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 jaar en 10 maanden om 08:54:38 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Eind datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 jaar om 10:11:42 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reden beeindiging alert<br /> |style=&quot;background-color: white;&quot;|patiënt niet meer zwanger<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Vaststeller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Relatie alert<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Identificatie<br /> |style=&quot;background-color: white;&quot;|pat02-mci-zwa-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGeg-pat02-mci-zwa-02<br /> |}<br /> === Bouwstenen===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;6&quot; | Bouwstenen<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;5&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGeg-pat02-mci-epi-01&quot; title=&quot;Intern ID = RegGeg-pat02-mci-epi-01&quot;&gt;Registratie gegevens RegGeg-pat02-mci-epi-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat02-mci-epi-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.16)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-N-van-Erven<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 20 jaar om 13:20:48 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGeg-pat02-mci-zwa-01&quot; title=&quot;Intern ID = RegGeg-pat02-mci-zwa-01&quot;&gt;Registratie gegevens RegGeg-pat02-mci-zwa-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat02-mci-zwa-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.16)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 jaar om 08:54:38 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGeg-pat02-mci-zwa-02&quot; title=&quot;Intern ID = RegGeg-pat02-mci-zwa-02&quot;&gt;Registratie gegevens RegGeg-pat02-mci-zwa-02&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat02-mci-zwa-02 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.16)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 jaar en 10 maanden om 10:11:42 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;zv-N-van-Erven&quot; title=&quot;Intern ID = zv-N-van-Erven&quot;&gt;Zorgverlener zv-N-van-Erven&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|000003332 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.139)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|N<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels<br /> |style=&quot;background-color: white;&quot;|van<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Erven<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Medisch specialisten, neurologie (code = '0330' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder<br /> |style=&quot;background-color: white;&quot;|za-Algemeen-Stadsziekenhuis<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;zv-Peter-van-Pulver&quot; title=&quot;Intern ID = zv-Peter-van-Pulver&quot;&gt;Zorgverlener zv-Peter-van-Pulver&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;12&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|000001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.139)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;7&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Peter<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|P<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels<br /> |style=&quot;background-color: white;&quot;|van<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Huisartsen, niet nader gespecificeerd (code = '0100' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder<br /> |style=&quot;background-color: white;&quot;|za-Huisartsenpraktijk-Pulver-en-Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;za-Algemeen-Stadsziekenhuis&quot; title=&quot;Intern ID = za-Algemeen-Stadsziekenhuis&quot;&gt;Zorgaanbieder za-Algemeen-Stadsziekenhuis&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder identificatienummer<br /> |style=&quot;background-color: white;&quot;|00002222 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.205)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie naam<br /> |style=&quot;background-color: white;&quot;|Algemeen Stadsziekenhuis<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Afdeling specialisme<br /> |style=&quot;background-color: white;&quot;|Medisch specialisten, neurologie (code = '0330' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Hoofdstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|2143AA<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Zorgstad<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;za-Huisartsenpraktijk-Pulver-en-Partners&quot; title=&quot;Intern ID = za-Huisartsenpraktijk-Pulver-en-Partners&quot;&gt;Zorgaanbieder za-Huisartsenpraktijk-Pulver-en-Partners&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder identificatienummer<br /> |style=&quot;background-color: white;&quot;|00001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.205)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie naam<br /> |style=&quot;background-color: white;&quot;|Huisartsenpraktijk Pulver &amp; Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Dorpstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|1234AA<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Ons Dorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |}&lt;section end=cio-bmci-tst-0.2-meerdereMCi /&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=cio:V2.0.0-beta.2_testgegevens_bgmo_addendum&diff=197136 2024-01-24T06:50:39Z

<p>Luud Slagter: NICTIZ-9056: Updated missing G-standard code</p> <hr /> <div><br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:Beschikbaarstellen geneesmiddelovergevoeligheden: addendum inhoudelijke gegevens}}<br /> <br /> =Addenda voor inhoudelijke gegevens=<br /> &lt;section begin=cio-bgmo-tst-0.1-geenBB /&gt;<br /> ==Scenario 0.1 - geen BB, O, R - ==<br /> <br /> === &lt;span id=&quot;Pat01&quot; title=&quot;Intern ID Pat01&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;Pat01&quot; title=&quot;Intern ID = Pat01&quot;&gt;&lt;span id=&quot;Pat01&quot; title=&quot;Intern ID Pat01&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Manus<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|M<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX_Nadorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999901205 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|1 dec 1985<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Man (code = 'M' in codeSystem 'HL7 AdministrativeGender')<br /> |}&lt;section end=cio-bgmo-tst-0.1-geenBB /&gt;<br /> &lt;section begin=cio-bgmo-tst-0.2-minimaalBB /&gt;<br /> ==Scenario 0.2 - minimaal BB - ==<br /> <br /> === &lt;span id=&quot;Pat02&quot; title=&quot;Intern ID Pat02&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;Pat02&quot; title=&quot;Intern ID = Pat02&quot;&gt;&lt;span id=&quot;Pat02&quot; title=&quot;Intern ID Pat02&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Wilma<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|W<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX_Zwaan<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999901199 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|30 nov 1965<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Vrouw (code = 'F' in codeSystem 'HL7 AdministrativeGender')<br /> |}<br /> === Geneesmiddelovergevoeligheid - IBUPROFEN===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - IBUPROFEN<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 dagen om 09:10:54 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|IBUPROFEN (code = '1155' in codeSystem 'G-Standaard generieke namen (bestand 750)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGeg-pat02-BB-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|zwelling van lippen en tong na gebruik van ibuprofen tabletten<br /> |}<br /> === Bouwstenen===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;6&quot; | Bouwstenen<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;5&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGeg-pat02-BB-01&quot; title=&quot;Intern ID = RegGeg-pat02-BB-01&quot;&gt;Registratie gegevens RegGeg-pat02-BB-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat02-BB-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 dagen om 09:10:54 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;zv-Peter-van-Pulver&quot; title=&quot;Intern ID = zv-Peter-van-Pulver&quot;&gt;Zorgverlener zv-Peter-van-Pulver&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|000001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.139)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Peter<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels<br /> |style=&quot;background-color: white;&quot;|van<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Huisartsen, niet nader gespecificeerd (code = '0100' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder<br /> |style=&quot;background-color: white;&quot;|za-Huisartsenpraktijk-Pulver-en-Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;za-Huisartsenpraktijk-Pulver-en-Partners&quot; title=&quot;Intern ID = za-Huisartsenpraktijk-Pulver-en-Partners&quot;&gt;Zorgaanbieder za-Huisartsenpraktijk-Pulver-en-Partners&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder identificatienummer<br /> |style=&quot;background-color: white;&quot;|00001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.205)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie naam<br /> |style=&quot;background-color: white;&quot;|Huisartsenpraktijk Pulver &amp; Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Dorpstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|1234AA<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Ons Dorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |}&lt;section end=cio-bgmo-tst-0.2-minimaalBB /&gt;<br /> &lt;section begin=cio-bgmo-tst-0.3-maximaalBB /&gt;<br /> ==Scenario 0.3 - maximaal BB, O, R - ==<br /> <br /> === &lt;span id=&quot;Pat03&quot; title=&quot;Intern ID Pat03&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;Pat03&quot; title=&quot;Intern ID = Pat03&quot;&gt;&lt;span id=&quot;Pat03&quot; title=&quot;Intern ID Pat03&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|David<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|D<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX_Lamet<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999901229 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|3 dec 1965<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Man (code = 'M' in codeSystem 'HL7 AdministrativeGender')<br /> |}<br /> === Geneesmiddelovergevoeligheid - PENICILLINES===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - PENICILLINES<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 108 dagen om 11:15:46 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-BB-01<br /> |}<br /> === Geneesmiddelovergevoeligheid - PENICILLINES===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - PENICILLINES<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Discontinued (qualifier value) (code = '410546004' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:23:05 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-BB-02<br /> |}<br /> === Geneesmiddelovergevoeligheid - PENICILLINES===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - PENICILLINES<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;14&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:25:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Besluit grond<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Overgevoeligheid<br /> |style=&quot;background-color: white;&quot;|pat03-overgevoeligheid-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Veilig binnen onveilige groep<br /> |style=&quot;background-color: white;&quot;|FLUCLOXACILLINE (code = '40991' in codeSystem 'G-Standaard generieke namen (Bestand 750)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-BB-03<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|&lt;span id=&quot;pat03-overgevoeligheid-01&quot; title=&quot;Intern ID = pat03-overgevoeligheid-01&quot;&gt;Overgevoeligheid pat03-overgevoeligheid-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;21&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 105 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening ernst<br /> |style=&quot;background-color: white;&quot;|Matig (code = '6736007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening aanwezigheid<br /> |style=&quot;background-color: white;&quot;|Known present (qualifier value) (code = '410515003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening status datum<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Agens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van vaststellen<br /> |style=&quot;background-color: white;&quot;|History and physical examination with evaluation and management of patient (procedure) (code = '14736009' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zekerheid status<br /> |style=&quot;background-color: white;&quot;|Confirmed present (qualifier value) (code = '410605003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Overgevoeligheid categorie<br /> |style=&quot;background-color: white;&quot;|geneesmiddelen (code = '419511003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Verwacht risico bij blootstelling<br /> |style=&quot;background-color: white;&quot;|Severe (severity modifier) (qualifier value) (code = '24484000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Diagnose naam<br /> |style=&quot;background-color: white;&quot;|overgevoeligheid voor meerdere geneesmiddelen (aandoening) (code = '735458004' in codeSystem 'SNOMED Clinical Terms')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Diagnostisch inzicht datum<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose steller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-overg-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Vastgesteld middels huidpriktest. Flucloxacilline wordt wel goed verdragen door patiënt.<br /> |}<br /> === Geneesmiddelovergevoeligheid - AMLODIPINE===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - AMLODIPINE<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;14&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 730 dagen om 09:57:02 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Besluit grond<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Reactie<br /> |style=&quot;background-color: white;&quot;|pat03-reactie-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|AMLODIPINE (code = '62081' in codeSystem 'G-Standaard generieke namen (bestand 750)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-BB-04<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Invaliderende bijwerking bij amlodipine tablet gebruik i.h.k.v. angina pectoris<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|&lt;span id=&quot;pat03-reactie-01&quot; title=&quot;Intern ID = pat03-reactie-01&quot;&gt;Reactie pat03-reactie-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;21&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening ernst<br /> |style=&quot;background-color: white;&quot;|Ernstig (code = '24484000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening aanwezigheid<br /> |style=&quot;background-color: white;&quot;|Known present (qualifier value) (code = '410515003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening status datum<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Veroorzaker<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Veroorzakende stof<br /> |style=&quot;background-color: white;&quot;|NORVASC TABLET 5MG (code = '642916G-Standaard HPK')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van blootstelling<br /> |style=&quot;background-color: white;&quot;|ORAAL (code = '9' in codeSystem 'G-Standaard Toedieningswegen (tabel 7)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Blootstelling datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van vaststellen<br /> |style=&quot;background-color: white;&quot;|History taking (procedure) (code = '84100007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zekerheid status<br /> |style=&quot;background-color: white;&quot;|Suspected (qualifier value) (code = '415684004' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reactie verschijnsel<br /> |style=&quot;background-color: white;&quot;|Invaliderende hoofdpijn bij gebruik amlodipine<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Diagnose naam<br /> |style=&quot;background-color: white;&quot;|overgevoeligheidsreactie (aandoening) (code = '421961002' in codeSystem 'SNOMED Clinical Terms')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Diagnostisch inzicht datum<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose steller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-reactie-01<br /> |}<br /> === Bouwstenen===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;6&quot; | Bouwstenen<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;5&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-01&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-01&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;8&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Pat03<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-02&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-02&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-02&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;5&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-02 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-03&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-03&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-03&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-03 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:25:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-04&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-04&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-04&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;9&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-04 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 730 dagen om 09:57:02 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Pat03<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-overg-01&quot; title=&quot;Intern ID = RegGegevens-pat03-overg-01&quot;&gt;Registratie gegevens RegGegevens-pat03-overg-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-overgevoeligheid-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.3)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:25:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-reactie-01&quot; title=&quot;Intern ID = RegGegevens-pat03-reactie-01&quot;&gt;Registratie gegevens RegGegevens-pat03-reactie-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-reactie-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.4)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 730 dagen om 09:57:02 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;zv-Peter-van-Pulver&quot; title=&quot;Intern ID = zv-Peter-van-Pulver&quot;&gt;Zorgverlener zv-Peter-van-Pulver&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|000001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.139)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Peter<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels<br /> |style=&quot;background-color: white;&quot;|van<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Huisartsen, niet nader gespecificeerd (code = '0100' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder<br /> |style=&quot;background-color: white;&quot;|za-Huisartsenpraktijk-Pulver-en-Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;za-Huisartsenpraktijk-Pulver-en-Partners&quot; title=&quot;Intern ID = za-Huisartsenpraktijk-Pulver-en-Partners&quot;&gt;Zorgaanbieder za-Huisartsenpraktijk-Pulver-en-Partners&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder identificatienummer<br /> |style=&quot;background-color: white;&quot;|00001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.205)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie naam<br /> |style=&quot;background-color: white;&quot;|Huisartsenpraktijk Pulver &amp; Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Dorpstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|1234AA<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Ons Dorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |}&lt;section end=cio-bgmo-tst-0.3-maximaalBB /&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=cio:V2.0.0-beta.2_testgegevens_bgmo_addendum&diff=197135 2024-01-23T17:11:45Z

<p>Luud Slagter: NICTIZ-9056: Updated wiki instances</p> <hr /> <div><br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:Beschikbaarstellen geneesmiddelovergevoeligheden: addendum inhoudelijke gegevens}}<br /> <br /> =Addenda voor inhoudelijke gegevens=<br /> &lt;section begin=cio-bgmo-tst-0.1-geenBB /&gt;<br /> ==Scenario 0.1 - geen BB, O, R - ==<br /> <br /> === &lt;span id=&quot;Pat01&quot; title=&quot;Intern ID Pat01&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;Pat01&quot; title=&quot;Intern ID = Pat01&quot;&gt;&lt;span id=&quot;Pat01&quot; title=&quot;Intern ID Pat01&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Manus<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|M<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX_Nadorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999901205 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|1 dec 1985<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Man (code = 'M' in codeSystem 'HL7 AdministrativeGender')<br /> |}&lt;section end=cio-bgmo-tst-0.1-geenBB /&gt;<br /> &lt;section begin=cio-bgmo-tst-0.2-minimaalBB /&gt;<br /> ==Scenario 0.2 - minimaal BB - ==<br /> <br /> === &lt;span id=&quot;Pat02&quot; title=&quot;Intern ID Pat02&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;Pat02&quot; title=&quot;Intern ID = Pat02&quot;&gt;&lt;span id=&quot;Pat02&quot; title=&quot;Intern ID Pat02&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Wilma<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|W<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX_Zwaan<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999901199 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|30 nov 1965<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Vrouw (code = 'F' in codeSystem 'HL7 AdministrativeGender')<br /> |}<br /> === Geneesmiddelovergevoeligheid - IBUPROFEN===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - IBUPROFEN<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 dagen om 09:10:54 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|IBUPROFEN (code = '1155' in codeSystem 'G-Standaard generieke namen (bestand 750)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGeg-pat02-BB-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|zwelling van lippen en tong na gebruik van ibuprofen tabletten<br /> |}<br /> === Bouwstenen===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;6&quot; | Bouwstenen<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;5&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGeg-pat02-BB-01&quot; title=&quot;Intern ID = RegGeg-pat02-BB-01&quot;&gt;Registratie gegevens RegGeg-pat02-BB-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat02-BB-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 dagen om 09:10:54 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;zv-Peter-van-Pulver&quot; title=&quot;Intern ID = zv-Peter-van-Pulver&quot;&gt;Zorgverlener zv-Peter-van-Pulver&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|000001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.139)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Peter<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels<br /> |style=&quot;background-color: white;&quot;|van<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Huisartsen, niet nader gespecificeerd (code = '0100' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder<br /> |style=&quot;background-color: white;&quot;|za-Huisartsenpraktijk-Pulver-en-Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;za-Huisartsenpraktijk-Pulver-en-Partners&quot; title=&quot;Intern ID = za-Huisartsenpraktijk-Pulver-en-Partners&quot;&gt;Zorgaanbieder za-Huisartsenpraktijk-Pulver-en-Partners&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder identificatienummer<br /> |style=&quot;background-color: white;&quot;|00001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.205)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie naam<br /> |style=&quot;background-color: white;&quot;|Huisartsenpraktijk Pulver &amp; Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Dorpstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|1234AA<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Ons Dorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |}&lt;section end=cio-bgmo-tst-0.2-minimaalBB /&gt;<br /> &lt;section begin=cio-bgmo-tst-0.3-maximaalBB /&gt;<br /> ==Scenario 0.3 - maximaal BB, O, R - ==<br /> <br /> === &lt;span id=&quot;Pat03&quot; title=&quot;Intern ID Pat03&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;Pat03&quot; title=&quot;Intern ID = Pat03&quot;&gt;&lt;span id=&quot;Pat03&quot; title=&quot;Intern ID Pat03&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|David<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|D<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX_Lamet<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999901229 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|3 dec 1965<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Man (code = 'M' in codeSystem 'HL7 AdministrativeGender')<br /> |}<br /> === Geneesmiddelovergevoeligheid - PENICILLINES===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - PENICILLINES<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 108 dagen om 11:15:46 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-BB-01<br /> |}<br /> === Geneesmiddelovergevoeligheid - PENICILLINES===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - PENICILLINES<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Discontinued (qualifier value) (code = '410546004' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:23:05 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-BB-02<br /> |}<br /> === Geneesmiddelovergevoeligheid - PENICILLINES===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - PENICILLINES<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;14&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:25:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Besluit grond<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Overgevoeligheid<br /> |style=&quot;background-color: white;&quot;|pat03-overgevoeligheid-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Veilig binnen onveilige groep<br /> |style=&quot;background-color: white;&quot;|(code = '40991' in codeSystem 'G-Standaard SNK')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-BB-03<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|&lt;span id=&quot;pat03-overgevoeligheid-01&quot; title=&quot;Intern ID = pat03-overgevoeligheid-01&quot;&gt;Overgevoeligheid pat03-overgevoeligheid-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;21&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 105 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening ernst<br /> |style=&quot;background-color: white;&quot;|Matig (code = '6736007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening aanwezigheid<br /> |style=&quot;background-color: white;&quot;|Known present (qualifier value) (code = '410515003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening status datum<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Agens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van vaststellen<br /> |style=&quot;background-color: white;&quot;|History and physical examination with evaluation and management of patient (procedure) (code = '14736009' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zekerheid status<br /> |style=&quot;background-color: white;&quot;|Confirmed present (qualifier value) (code = '410605003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Overgevoeligheid categorie<br /> |style=&quot;background-color: white;&quot;|geneesmiddelen (code = '419511003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Verwacht risico bij blootstelling<br /> |style=&quot;background-color: white;&quot;|Severe (severity modifier) (qualifier value) (code = '24484000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Diagnose naam<br /> |style=&quot;background-color: white;&quot;|overgevoeligheid voor meerdere geneesmiddelen (aandoening) (code = '735458004' in codeSystem 'SNOMED Clinical Terms')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Diagnostisch inzicht datum<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose steller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-overg-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Vastgesteld middels huidpriktest. Flucloxacilline wordt wel goed verdragen door patiënt.<br /> |}<br /> === Geneesmiddelovergevoeligheid - AMLODIPINE===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - AMLODIPINE<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;14&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 730 dagen om 09:57:02 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Besluit grond<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Reactie<br /> |style=&quot;background-color: white;&quot;|pat03-reactie-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|AMLODIPINE (code = '62081' in codeSystem 'G-Standaard generieke namen (bestand 750)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-BB-04<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Invaliderende bijwerking bij amlodipine tablet gebruik i.h.k.v. angina pectoris<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|&lt;span id=&quot;pat03-reactie-01&quot; title=&quot;Intern ID = pat03-reactie-01&quot;&gt;Reactie pat03-reactie-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;21&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening ernst<br /> |style=&quot;background-color: white;&quot;|Ernstig (code = '24484000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening aanwezigheid<br /> |style=&quot;background-color: white;&quot;|Known present (qualifier value) (code = '410515003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening status datum<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Veroorzaker<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Veroorzakende stof<br /> |style=&quot;background-color: white;&quot;|NORVASC TABLET 5MG (code = '642916G-Standaard HPK')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van blootstelling<br /> |style=&quot;background-color: white;&quot;|ORAAL (code = '9' in codeSystem 'G-Standaard Toedieningswegen (tabel 7)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Blootstelling datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van vaststellen<br /> |style=&quot;background-color: white;&quot;|History taking (procedure) (code = '84100007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zekerheid status<br /> |style=&quot;background-color: white;&quot;|Suspected (qualifier value) (code = '415684004' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reactie verschijnsel<br /> |style=&quot;background-color: white;&quot;|Invaliderende hoofdpijn bij gebruik amlodipine<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Diagnose naam<br /> |style=&quot;background-color: white;&quot;|overgevoeligheidsreactie (aandoening) (code = '421961002' in codeSystem 'SNOMED Clinical Terms')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Diagnostisch inzicht datum<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose steller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-reactie-01<br /> |}<br /> === Bouwstenen===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;6&quot; | Bouwstenen<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;5&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-01&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-01&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;8&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Pat03<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-02&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-02&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-02&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;5&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-02 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-03&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-03&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-03&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-03 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:25:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-04&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-04&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-04&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;9&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-04 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 730 dagen om 09:57:02 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Pat03<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-overg-01&quot; title=&quot;Intern ID = RegGegevens-pat03-overg-01&quot;&gt;Registratie gegevens RegGegevens-pat03-overg-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-overgevoeligheid-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.3)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:25:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-reactie-01&quot; title=&quot;Intern ID = RegGegevens-pat03-reactie-01&quot;&gt;Registratie gegevens RegGegevens-pat03-reactie-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-reactie-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.4)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 730 dagen om 09:57:02 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;zv-Peter-van-Pulver&quot; title=&quot;Intern ID = zv-Peter-van-Pulver&quot;&gt;Zorgverlener zv-Peter-van-Pulver&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|000001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.139)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Peter<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels<br /> |style=&quot;background-color: white;&quot;|van<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Huisartsen, niet nader gespecificeerd (code = '0100' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder<br /> |style=&quot;background-color: white;&quot;|za-Huisartsenpraktijk-Pulver-en-Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;za-Huisartsenpraktijk-Pulver-en-Partners&quot; title=&quot;Intern ID = za-Huisartsenpraktijk-Pulver-en-Partners&quot;&gt;Zorgaanbieder za-Huisartsenpraktijk-Pulver-en-Partners&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder identificatienummer<br /> |style=&quot;background-color: white;&quot;|00001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.205)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie naam<br /> |style=&quot;background-color: white;&quot;|Huisartsenpraktijk Pulver &amp; Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Dorpstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|1234AA<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Ons Dorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |}&lt;section end=cio-bgmo-tst-0.3-maximaalBB /&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=cio:V2.0.0-beta.2_testgegevens_bgmo_addendum&diff=197134 2024-01-23T16:57:38Z

<p>Luud Slagter: NICTIZ-9056/1047: Updated content and fixed titles</p> <hr /> <div><br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:Beschikbaarstellen geneesmiddelovergevoeligheden: addendum inhoudelijke gegevens}}<br /> <br /> =Addenda voor inhoudelijke gegevens=<br /> &lt;section begin=cio-bgmo-tst-0.1-geenBB /&gt;<br /> ==Scenario 0.1 - geen BB, O, R - ==<br /> <br /> === &lt;span id=&quot;Pat01&quot; title=&quot;Intern ID Pat01&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;Pat01&quot; title=&quot;Intern ID = Pat01&quot;&gt;&lt;span id=&quot;Pat01&quot; title=&quot;Intern ID Pat01&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Manus<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|M<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX_Nadorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999901205 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|1 dec 1985<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Man (code = 'M' in codeSystem 'HL7 AdministrativeGender')<br /> |}&lt;section end=cio-bgmo-tst-0.1-geenBB /&gt;<br /> &lt;section begin=cio-bgmo-tst-0.2-minimaalBB /&gt;<br /> ==Scenario 0.2 - minimaal BB - ==<br /> <br /> === &lt;span id=&quot;Pat02&quot; title=&quot;Intern ID Pat02&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;Pat02&quot; title=&quot;Intern ID = Pat02&quot;&gt;&lt;span id=&quot;Pat02&quot; title=&quot;Intern ID Pat02&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Wilma<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|W<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX_Zwaan<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999901199 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|30 nov 1965<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Vrouw (code = 'F' in codeSystem 'HL7 AdministrativeGender')<br /> |}<br /> === Geneesmiddelovergevoeligheid - IBUPROFEN===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - IBUPROFEN<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 dagen om 09:10:54 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|IBUPROFEN (code = '1155' in codeSystem 'G-Standaard generieke namen (bestand 750)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGeg-pat02-BB-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|zwelling van lippen en tong na gebruik van ibuprofen tabletten<br /> |}<br /> === Bouwstenen===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;6&quot; | Bouwstenen<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;5&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGeg-pat02-BB-01&quot; title=&quot;Intern ID = RegGeg-pat02-BB-01&quot;&gt;Registratie gegevens RegGeg-pat02-BB-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat02-BB-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 dagen om 09:10:54 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;zv-Peter-van-Pulver&quot; title=&quot;Intern ID = zv-Peter-van-Pulver&quot;&gt;Zorgverlener zv-Peter-van-Pulver&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|000001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.139)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Peter<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels<br /> |style=&quot;background-color: white;&quot;|van<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Huisartsen, niet nader gespecificeerd (code = '0100' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder<br /> |style=&quot;background-color: white;&quot;|za-Huisartsenpraktijk-Pulver-en-Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;za-Huisartsenpraktijk-Pulver-en-Partners&quot; title=&quot;Intern ID = za-Huisartsenpraktijk-Pulver-en-Partners&quot;&gt;Zorgaanbieder za-Huisartsenpraktijk-Pulver-en-Partners&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder identificatienummer<br /> |style=&quot;background-color: white;&quot;|00001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.205)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie naam<br /> |style=&quot;background-color: white;&quot;|Huisartsenpraktijk Pulver &amp; Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Dorpstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|1234AA<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Ons Dorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |}&lt;section end=cio-bgmo-tst-0.2-minimaalBB /&gt;<br /> &lt;section begin=cio-bgmo-tst-0.3-maximaalBB /&gt;<br /> ==Scenario 0.3 - maximaal BB, O, R - ==<br /> <br /> === &lt;span id=&quot;Pat03&quot; title=&quot;Intern ID Pat03&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;Pat03&quot; title=&quot;Intern ID = Pat03&quot;&gt;&lt;span id=&quot;Pat03&quot; title=&quot;Intern ID Pat03&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|David<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|D<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX_Lamet<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999901229 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|3 dec 1965<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Man (code = 'M' in codeSystem 'HL7 AdministrativeGender')<br /> |}<br /> === Geneesmiddelovergevoeligheid - PENICILLINES===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - PENICILLINES<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 108 dagen om 11:15:46 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-BB-01<br /> |}<br /> === Geneesmiddelovergevoeligheid - PENICILLINES===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - PENICILLINES<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Discontinued (qualifier value) (code = '410546004' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:23:05 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-BB-02<br /> |}<br /> === Geneesmiddelovergevoeligheid - PENICILLINES===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - PENICILLINES<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;14&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:25:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Besluit grond<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Overgevoeligheid<br /> |style=&quot;background-color: white;&quot;|pat03-overgevoeligheid-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Veilig binnen onveilige groep<br /> |style=&quot;background-color: white;&quot;|(code = '40991' in codeSystem 'G-Standaard SNK')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-BB-03<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|&lt;span id=&quot;pat03-overgevoeligheid-01&quot; title=&quot;Intern ID = pat03-overgevoeligheid-01&quot;&gt;Overgevoeligheid pat03-overgevoeligheid-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;21&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 105 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening ernst<br /> |style=&quot;background-color: white;&quot;|Matig (code = '6736007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening aanwezigheid<br /> |style=&quot;background-color: white;&quot;|Known present (qualifier value) (code = '410515003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening status datum<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Agens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Stof<br /> |style=&quot;background-color: white;&quot;|PENICILLINES (code = '35' in codeSystem 'G-Standaard Ongewenste medicatiegroepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van vaststellen<br /> |style=&quot;background-color: white;&quot;|History and physical examination with evaluation and management of patient (procedure) (code = '14736009' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zekerheid status<br /> |style=&quot;background-color: white;&quot;|Confirmed present (qualifier value) (code = '410605003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Overgevoeligheid categorie<br /> |style=&quot;background-color: white;&quot;|geneesmiddelen (code = '419511003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Verwacht risico bij blootstelling<br /> |style=&quot;background-color: white;&quot;|Severe (severity modifier) (qualifier value) (code = '24484000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Diagnose naam<br /> |style=&quot;background-color: white;&quot;|(code = '' in codeSystem 'SNOMED Clinical Terms')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Diagnostisch inzicht datum<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose steller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-overg-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Vastgesteld middels huidpriktest. Flucloxacilline wordt wel goed verdragen door patiënt.<br /> |}<br /> === Geneesmiddelovergevoeligheid - AMLODIPINE===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid - AMLODIPINE<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;14&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 730 dagen om 09:57:02 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Besluit grond<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Reactie<br /> |style=&quot;background-color: white;&quot;|pat03-reactie-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|AMLODIPINE (code = '62081' in codeSystem 'G-Standaard generieke namen (bestand 750)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-BB-04<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Invaliderende bijwerking bij amlodipine tablet gebruik i.h.k.v. angina pectoris<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|&lt;span id=&quot;pat03-reactie-01&quot; title=&quot;Intern ID = pat03-reactie-01&quot;&gt;Reactie pat03-reactie-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;21&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening ernst<br /> |style=&quot;background-color: white;&quot;|Ernstig (code = '24484000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening aanwezigheid<br /> |style=&quot;background-color: white;&quot;|Known present (qualifier value) (code = '410515003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening status datum<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Veroorzaker<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Veroorzakende stof<br /> |style=&quot;background-color: white;&quot;|NORVASC (code = '642916G-Standaard HPK')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van blootstelling<br /> |style=&quot;background-color: white;&quot;|(code = '9' in codeSystem 'G-Standaard Toedieningswegen (tabel 7)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Blootstelling datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van vaststellen<br /> |style=&quot;background-color: white;&quot;|History taking (procedure) (code = '84100007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zekerheid status<br /> |style=&quot;background-color: white;&quot;|Suspected (qualifier value) (code = '415684004' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reactie verschijnsel<br /> |style=&quot;background-color: white;&quot;|Invaliderende hoofdpijn bij gebruik amlodipine<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Diagnose naam<br /> |style=&quot;background-color: white;&quot;|(code = '' in codeSystem 'SNOMED Clinical Terms')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Diagnostisch inzicht datum<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose steller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-reactie-01<br /> |}<br /> === Bouwstenen===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;6&quot; | Bouwstenen<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;5&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-01&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-01&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;8&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Pat03<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-02&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-02&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-02&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;5&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-02 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-03&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-03&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-03&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-03 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:25:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-04&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-04&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-04&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;9&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-04 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 730 dagen om 09:57:02 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Pat03<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-overg-01&quot; title=&quot;Intern ID = RegGegevens-pat03-overg-01&quot;&gt;Registratie gegevens RegGegevens-pat03-overg-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-overgevoeligheid-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.3)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:25:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-reactie-01&quot; title=&quot;Intern ID = RegGegevens-pat03-reactie-01&quot;&gt;Registratie gegevens RegGegevens-pat03-reactie-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-reactie-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.4)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 730 dagen om 09:57:02 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;zv-Peter-van-Pulver&quot; title=&quot;Intern ID = zv-Peter-van-Pulver&quot;&gt;Zorgverlener zv-Peter-van-Pulver&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|000001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.139)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Peter<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels<br /> |style=&quot;background-color: white;&quot;|van<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Huisartsen, niet nader gespecificeerd (code = '0100' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder<br /> |style=&quot;background-color: white;&quot;|za-Huisartsenpraktijk-Pulver-en-Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;za-Huisartsenpraktijk-Pulver-en-Partners&quot; title=&quot;Intern ID = za-Huisartsenpraktijk-Pulver-en-Partners&quot;&gt;Zorgaanbieder za-Huisartsenpraktijk-Pulver-en-Partners&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder identificatienummer<br /> |style=&quot;background-color: white;&quot;|00001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.205)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie naam<br /> |style=&quot;background-color: white;&quot;|Huisartsenpraktijk Pulver &amp; Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Dorpstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|1234AA<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Ons Dorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |}&lt;section end=cio-bgmo-tst-0.3-maximaalBB /&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=cio:V2.0.0-beta.2_testgegevens_bmci_addendum&diff=197133 2024-01-23T16:57:08Z

<p>Luud Slagter: NICTIZ-9056/1047: Updated content and fixed titles</p> <hr /> <div><br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:Beschikbaarstellen medicatiecontra-indicaties: addendum inhoudelijke gegevens}}<br /> <br /> =Addenda voor inhoudelijke gegevens=<br /> &lt;section begin=cio-bmci-tst-0.1-geenMCi /&gt;<br /> ==Scenario 0.1 - geen MCi - ==<br /> <br /> === &lt;span id=&quot;Pat01&quot; title=&quot;Intern ID Pat01&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;Pat01&quot; title=&quot;Intern ID = Pat01&quot;&gt;&lt;span id=&quot;Pat01&quot; title=&quot;Intern ID Pat01&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Manus<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|M<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX_Nadorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999901205 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|1 dec 1985<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Man (code = 'M' in codeSystem 'HL7 AdministrativeGender')<br /> |}<br /> === Medicatie contra indicatie===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;4&quot; | Medicatie contra indicatie<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;3&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Alert<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Alert naam<br /> |style=&quot;background-color: white;&quot;|(code = '' in codeSystem 'G-standaard Contra Indicaties (Thesaurus 40)')<br /> |}&lt;section end=cio-bmci-tst-0.1-geenMCi /&gt;<br /> &lt;section begin=cio-bmci-tst-0.2-meerdereMCi /&gt;<br /> ==Scenario 0.2 - meerdere MCi - ==<br /> <br /> === &lt;span id=&quot;Pat02&quot; title=&quot;Intern ID Pat02&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;Pat02&quot; title=&quot;Intern ID = Pat02&quot;&gt;&lt;span id=&quot;Pat02&quot; title=&quot;Intern ID Pat02&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Wilma<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|W<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX_Zwaan<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999901199 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|30 nov 1965<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Vrouw (code = 'F' in codeSystem 'HL7 AdministrativeGender')<br /> |}<br /> === Medicatie contra indicatie - Epilepsie===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;4&quot; | Medicatie contra indicatie - Epilepsie<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;3&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Alert<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;5&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Alert type<br /> |style=&quot;background-color: white;&quot;|Potentiële contra-indicatie voor geneesmiddel (bevinding) (code = '350241000146102' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Alert naam<br /> |style=&quot;background-color: white;&quot;|Epilepsie (code = '42' in codeSystem 'G-standaard Contra Indicaties (Thesaurus 40)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 20 jaar om 13:20:48 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGeg-pat02-mci-epi-01<br /> |}<br /> === Medicatie contra indicatie - Zwangerschap===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;4&quot; | Medicatie contra indicatie - Zwangerschap<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;3&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Alert<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;5&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Alert type<br /> |style=&quot;background-color: white;&quot;|Potentiële contra-indicatie voor geneesmiddel (bevinding) (code = '350241000146102' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Alert naam<br /> |style=&quot;background-color: white;&quot;|Zwangerschap (code = '1320' in codeSystem 'G-standaard Contra Indicaties (Thesaurus 40)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 jaar om 08:54:38 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGeg-pat02-mci-zwa-01<br /> |}<br /> === Medicatie contra indicatie - Zwangerschap===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Medicatie contra indicatie - Zwangerschap<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Alert<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;9&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Alert type<br /> |style=&quot;background-color: white;&quot;|Potentiële contra-indicatie voor geneesmiddel (bevinding) (code = '350241000146102' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Alert naam<br /> |style=&quot;background-color: white;&quot;|Zwangerschap (code = '1320' in codeSystem 'G-standaard Contra Indicaties (Thesaurus 40)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 jaar en 10 maanden om 08:54:38 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Eind datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 jaar om 10:11:42 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Relatie alert<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Identificatie<br /> |style=&quot;background-color: white;&quot;|pat02-mci-zwa-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGeg-pat02-mci-zwa-02<br /> |}<br /> === Bouwstenen===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;6&quot; | Bouwstenen<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;5&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGeg-pat02-mci-epi-01&quot; title=&quot;Intern ID = RegGeg-pat02-mci-epi-01&quot;&gt;Registratie gegevens RegGeg-pat02-mci-epi-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat02-mci-epi-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.16)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-N-van-Erven<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 20 jaar om 13:20:48 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGeg-pat02-mci-zwa-01&quot; title=&quot;Intern ID = RegGeg-pat02-mci-zwa-01&quot;&gt;Registratie gegevens RegGeg-pat02-mci-zwa-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat02-mci-zwa-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.16)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 jaar om 08:54:38 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGeg-pat02-mci-zwa-02&quot; title=&quot;Intern ID = RegGeg-pat02-mci-zwa-02&quot;&gt;Registratie gegevens RegGeg-pat02-mci-zwa-02&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat02-mci-zwa-02 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.16)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 jaar en 10 maanden om 10:11:42 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;zv-N-van-Erven&quot; title=&quot;Intern ID = zv-N-van-Erven&quot;&gt;Zorgverlener zv-N-van-Erven&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|000003332 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.139)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|N<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels<br /> |style=&quot;background-color: white;&quot;|van<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Erven<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Medisch specialisten, neurologie (code = '0330' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder<br /> |style=&quot;background-color: white;&quot;|za-Algemeen-Stadsziekenhuis<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;zv-Peter-van-Pulver&quot; title=&quot;Intern ID = zv-Peter-van-Pulver&quot;&gt;Zorgverlener zv-Peter-van-Pulver&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;12&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|000001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.139)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;7&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Peter<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|P<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels<br /> |style=&quot;background-color: white;&quot;|van<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Huisartsen, niet nader gespecificeerd (code = '0100' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder<br /> |style=&quot;background-color: white;&quot;|za-Huisartsenpraktijk-Pulver-en-Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;za-Algemeen-Stadsziekenhuis&quot; title=&quot;Intern ID = za-Algemeen-Stadsziekenhuis&quot;&gt;Zorgaanbieder za-Algemeen-Stadsziekenhuis&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder identificatienummer<br /> |style=&quot;background-color: white;&quot;|00002222 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.205)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie naam<br /> |style=&quot;background-color: white;&quot;|Algemeen Stadsziekenhuis<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Afdeling specialisme<br /> |style=&quot;background-color: white;&quot;|Medisch specialisten, neurologie (code = '0330' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Hoofdstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|2143AA<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Zorgstad<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;za-Huisartsenpraktijk-Pulver-en-Partners&quot; title=&quot;Intern ID = za-Huisartsenpraktijk-Pulver-en-Partners&quot;&gt;Zorgaanbieder za-Huisartsenpraktijk-Pulver-en-Partners&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder identificatienummer<br /> |style=&quot;background-color: white;&quot;|00001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.205)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie naam<br /> |style=&quot;background-color: white;&quot;|Huisartsenpraktijk Pulver &amp; Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Dorpstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|1234AA<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Ons Dorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |}&lt;section end=cio-bmci-tst-0.2-meerdereMCi /&gt;</div>

Luud Slagter https://informatiestandaarden.nictiz.nl/index.php?title=cio:V2.0.0-beta.2_testgegevens_bgmo_addendum&diff=197118 2024-01-23T13:11:16Z

<p>Luud Slagter: NICTIZ-9056: Updated wiki instance based on correct release</p> <hr /> <div><br /> __NUMBEREDHEADINGS__<br /> {{DISPLAYTITLE:Beschikbaarstellen geneesmiddelovergevoeligheden: addendum inhoudelijke gegevens}}<br /> <br /> =Addenda voor inhoudelijke gegevens=<br /> &lt;section begin=cio-bgmo-tst-0.1-geenBB /&gt;<br /> ==Scenario scenario 0.1 - geen BB, O, R - ==<br /> <br /> === &lt;span id=&quot;Pat01&quot; title=&quot;Intern ID Pat01&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;Pat01&quot; title=&quot;Intern ID = Pat01&quot;&gt;&lt;span id=&quot;Pat01&quot; title=&quot;Intern ID Pat01&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Manus<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|M<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX_Nadorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999901205 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|1 dec 1985<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Man (code = 'M' in codeSystem 'HL7 AdministrativeGender')<br /> |}&lt;section end=cio-bgmo-tst-0.1-geenBB /&gt;<br /> &lt;section begin=cio-bgmo-tst-0.2-minimaalBB /&gt;<br /> ==Scenario scenario 0.2 - minimaal BB - ==<br /> <br /> === &lt;span id=&quot;Pat02&quot; title=&quot;Intern ID Pat02&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;Pat02&quot; title=&quot;Intern ID = Pat02&quot;&gt;&lt;span id=&quot;Pat02&quot; title=&quot;Intern ID Pat02&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Wilma<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|W<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX_Zwaan<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999901199 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|30 nov 1965<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Vrouw (code = 'F' in codeSystem 'HL7 AdministrativeGender')<br /> |}<br /> === Geneesmiddelovergevoeligheid===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 dagen om 09:10:54 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|(code = '1155' in codeSystem 'G-Standaard SNK')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGeg-pat02-BB-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|zwelling van lippen en tong na gebruik van ibuprofen tabletten<br /> |}<br /> === Bouwstenen===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;6&quot; | Bouwstenen<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;5&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGeg-pat02-BB-01&quot; title=&quot;Intern ID = RegGeg-pat02-BB-01&quot;&gt;Registratie gegevens RegGeg-pat02-BB-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat02-BB-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 30 dagen om 09:10:54 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;zv-Peter-van-Pulver&quot; title=&quot;Intern ID = zv-Peter-van-Pulver&quot;&gt;Zorgverlener zv-Peter-van-Pulver&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|000001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.139)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Peter<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels<br /> |style=&quot;background-color: white;&quot;|van<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Huisartsen, niet nader gespecificeerd (code = '0100' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder<br /> |style=&quot;background-color: white;&quot;|za-Huisartsenpraktijk-Pulver-en-Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;za-Huisartsenpraktijk-Pulver-en-Partners&quot; title=&quot;Intern ID = za-Huisartsenpraktijk-Pulver-en-Partners&quot;&gt;Zorgaanbieder za-Huisartsenpraktijk-Pulver-en-Partners&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder identificatienummer<br /> |style=&quot;background-color: white;&quot;|00001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.205)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie naam<br /> |style=&quot;background-color: white;&quot;|Huisartsenpraktijk Pulver &amp; Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Dorpstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|1234AA<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Ons Dorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |}&lt;section end=cio-bgmo-tst-0.2-minimaalBB /&gt;<br /> &lt;section begin=cio-bgmo-tst-0.3-maximaalBB /&gt;<br /> ==Scenario scenario 0.3 - maximaal BB, O, R - ==<br /> <br /> === &lt;span id=&quot;Pat03&quot; title=&quot;Intern ID Pat03&quot;&gt;Patient&lt;/span&gt;===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | &lt;span id=&quot;Pat03&quot; title=&quot;Intern ID = Pat03&quot;&gt;&lt;span id=&quot;Pat03&quot; title=&quot;Intern ID Pat03&quot;&gt;Patient&lt;/span&gt;&lt;/span&gt;<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|David<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Initialen<br /> |style=&quot;background-color: white;&quot;|D<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|XXX_Lamet<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|999901229 (in identificerend systeem: BSN)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geboortedatum<br /> |style=&quot;background-color: white;&quot;|3 dec 1965<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Geslacht<br /> |style=&quot;background-color: white;&quot;|Man (code = 'M' in codeSystem 'HL7 AdministrativeGender')<br /> |}<br /> === Geneesmiddelovergevoeligheid===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 108 dagen om 11:15:46 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|(code = '35' in codeSystem 'G-Standaard TH122 Ongewenste groepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-BB-01<br /> |}<br /> === Geneesmiddelovergevoeligheid===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Discontinued (qualifier value) (code = '410546004' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:23:05 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|(code = '35' in codeSystem 'G-Standaard TH122 Ongewenste groepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-BB-02<br /> |}<br /> === Geneesmiddelovergevoeligheid===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;14&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:25:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Besluit grond<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Overgevoeligheid<br /> |style=&quot;background-color: white;&quot;|pat03-overgevoeligheid-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|(code = '35' in codeSystem 'G-Standaard TH122 Ongewenste groepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Veilig binnen onveilige groep<br /> |style=&quot;background-color: white;&quot;|(code = '40991' in codeSystem 'G-Standaard SNK')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-BB-03<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|&lt;span id=&quot;pat03-overgevoeligheid-01&quot; title=&quot;Intern ID = pat03-overgevoeligheid-01&quot;&gt;Overgevoeligheid pat03-overgevoeligheid-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;21&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 105 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening ernst<br /> |style=&quot;background-color: white;&quot;|Matig (code = '6736007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening aanwezigheid<br /> |style=&quot;background-color: white;&quot;|Known present (qualifier value) (code = '410515003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening status datum<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Agens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Stof<br /> |style=&quot;background-color: white;&quot;|(code = '35' in codeSystem 'G-Standaard TH122 Ongewenste groepen')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van vaststellen<br /> |style=&quot;background-color: white;&quot;|History and physical examination with evaluation and management of patient (procedure) (code = '14736009' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zekerheid status<br /> |style=&quot;background-color: white;&quot;|Confirmed present (qualifier value) (code = '410605003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Overgevoeligheid categorie<br /> |style=&quot;background-color: white;&quot;|geneesmiddelen (code = '419511003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Verwacht risico bij blootstelling<br /> |style=&quot;background-color: white;&quot;|Severe (severity modifier) (qualifier value) (code = '24484000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Diagnose naam<br /> |style=&quot;background-color: white;&quot;|(code = '' in codeSystem 'SNOMED Clinical Terms')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Diagnostisch inzicht datum<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose steller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-overg-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Vastgesteld middels huidpriktest. Flucloxacilline wordt wel goed verdragen door patiënt.<br /> |}<br /> === Geneesmiddelovergevoeligheid===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;5&quot; | Geneesmiddelovergevoeligheid<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;4&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Bewaking besluit<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;14&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit type<br /> |style=&quot;background-color: white;&quot;|Started (qualifier value) (code = '385652002' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Besluit ingangs datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 730 dagen om 09:57:02 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Besluit grond<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Reactie<br /> |style=&quot;background-color: white;&quot;|pat03-reactie-01<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Te bewaken stof<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Onveilige stof<br /> |style=&quot;background-color: white;&quot;|(code = '62081' in codeSystem 'G-Standaard SNK')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Beslisser<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-BB-04<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Toelichting<br /> |style=&quot;background-color: white;&quot;|Invaliderende bijwerking bij amlodipine tablet gebruik i.h.k.v. angina pectoris<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|&lt;span id=&quot;pat03-reactie-01&quot; title=&quot;Intern ID = pat03-reactie-01&quot;&gt;Reactie pat03-reactie-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;21&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening begin datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening ernst<br /> |style=&quot;background-color: white;&quot;|Ernstig (code = '24484000' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening aanwezigheid<br /> |style=&quot;background-color: white;&quot;|Known present (qualifier value) (code = '410515003' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Aandoening status datum<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Veroorzaker<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Veroorzakende stof<br /> |style=&quot;background-color: white;&quot;|(code = '642916')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van blootstelling<br /> |style=&quot;background-color: white;&quot;|(code = '9' in codeSystem 'G-Standaard Toedieningswegen (tabel 7)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Blootstelling datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Wijze van vaststellen<br /> |style=&quot;background-color: white;&quot;|History taking (procedure) (code = '84100007' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zekerheid status<br /> |style=&quot;background-color: white;&quot;|Suspected (qualifier value) (code = '415684004' in codeSystem 'SNOMED CT')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Reactie verschijnsel<br /> |style=&quot;background-color: white;&quot;|Invaliderende hoofdpijn bij gebruik amlodipine<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Diagnose naam<br /> |style=&quot;background-color: white;&quot;|(code = '' in codeSystem 'SNOMED Clinical Terms')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Diagnostisch inzicht datum<br /> |style=&quot;background-color: white;&quot;|T - 732 dagen<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Diagnose steller<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Registratie gegevens<br /> |style=&quot;background-color: white;&quot;|RegGegevens-pat03-reactie-01<br /> |}<br /> === Bouwstenen===<br /> <br /> {| class=&quot;wikitable&quot; width=&quot;85%&quot;<br /> |style=&quot;background-color: #1F497D;; color: white; font-weight: bold; text-align:center;&quot; colspan=&quot;6&quot; | Bouwstenen<br /> |-style=&quot;background-color: #1F497D;; color: white; text-align:left;&quot; <br /> |colspan=&quot;5&quot; width=&quot;30%&quot;| Gegevenselement<br /> || Waarde<br /> <br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-01&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-01&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;8&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Pat03<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-02&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-02&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-02&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;5&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-02 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-03&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-03&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-03&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-03 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:25:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-BB-04&quot; title=&quot;Intern ID = RegGegevens-pat03-BB-04&quot;&gt;Registratie gegevens RegGegevens-pat03-BB-04&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;9&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-BB-04 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.754)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 730 dagen om 09:57:02 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Informatiebron<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Patient<br /> |style=&quot;background-color: white;&quot;|Pat03<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-overg-01&quot; title=&quot;Intern ID = RegGegevens-pat03-overg-01&quot;&gt;Registratie gegevens RegGegevens-pat03-overg-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-overgevoeligheid-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.3)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 50 dagen om 14:25:30 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;RegGegevens-pat03-reactie-01&quot; title=&quot;Intern ID = RegGegevens-pat03-reactie-01&quot;&gt;Registratie gegevens RegGegevens-pat03-reactie-01&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Identificatienummer<br /> |style=&quot;background-color: white;&quot;|pat03-reactie-01 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.4)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Auteur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;2&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Zorgverlener<br /> |style=&quot;background-color: white;&quot;|zv-Peter-van-Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Registratie datum tijd<br /> |style=&quot;background-color: white;&quot;|T - 730 dagen om 09:57:02 uur<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;zv-Peter-van-Pulver&quot; title=&quot;Intern ID = zv-Peter-van-Pulver&quot;&gt;Zorgverlener zv-Peter-van-Pulver&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;11&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgverlener identificatienummer<br /> |style=&quot;background-color: white;&quot;|000001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.139)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Naamgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Voornamen<br /> |style=&quot;background-color: white;&quot;|Peter<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;4&quot;|Geslachtsnaam<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;3&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Voorvoegsels<br /> |style=&quot;background-color: white;&quot;|van<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;2&quot;|Achternaam<br /> |style=&quot;background-color: white;&quot;|Pulver<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Specialisme<br /> |style=&quot;background-color: white;&quot;|Huisartsen, niet nader gespecificeerd (code = '0100' in codeSystem 'COD016-VEKT Vektis Zorgverlenersspecificatie (subberoepsgroep)')<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder<br /> |style=&quot;background-color: white;&quot;|za-Huisartsenpraktijk-Pulver-en-Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;6&quot;|&lt;span id=&quot;za-Huisartsenpraktijk-Pulver-en-Partners&quot; title=&quot;Intern ID = za-Huisartsenpraktijk-Pulver-en-Partners&quot;&gt;Zorgaanbieder za-Huisartsenpraktijk-Pulver-en-Partners&lt;/span&gt;<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;10&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Zorgaanbieder identificatienummer<br /> |style=&quot;background-color: white;&quot;|00001111 (in identificerend systeem: 2.16.840.1.113883.2.4.3.11.999.26.1.205)<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;4&quot;|Organisatie naam<br /> |style=&quot;background-color: white;&quot;|Huisartsenpraktijk Pulver &amp; Partners<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot; <br /> |colspan=&quot;5&quot;|Adresgegevens<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |rowspan=&quot;6&quot;|<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Straat<br /> |style=&quot;background-color: white;&quot;|Dorpstraat<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Huisnummer<br /> |style=&quot;background-color: white;&quot;|1<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Postcode<br /> |style=&quot;background-color: white;&quot;|1234AA<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Woonplaats<br /> |style=&quot;background-color: white;&quot;|Ons Dorp<br /> |-style=&quot;vertical-align:top; background-color: #E3E3E3;;&quot;<br /> |colspan=&quot;3&quot;|Adres soort<br /> |style=&quot;background-color: white;&quot;|Werkadres (code = 'WP' in codeSystem 'HL7 AddressUse')<br /> |}&lt;section end=cio-bgmo-tst-0.3-maximaalBB /&gt;</div>

Luud Slagter