MedMij:Vprepub-2019.01 FHIR MedicationProcess - Bewerkingsoverzicht

Pieter Edelman: MM-3705: The use case Medication overview has been deprecated

2022-10-18T12:25:35Z

MM-3705: The use case Medication overview has been deprecated

← Oudere versie		Versie van 18 okt 2022 12:25
Regel 55:		Regel 55:

	=Use case: retrieve medication overview=		=Use case: retrieve medication overview=
	{{~~IssueBox~~\|The ~~MedMij DVZA qualification for 'serve~~ medication overview~~' ('systeemrolcode' MP9.0.7~~-~~MOB~~-~~FHIR) is not available (anymore)~~. ~~Please contact us via [mailto:standaarden@medmij~~.~~nl standaarden@medmij.nl] if you~~ are ~~a DVZA and wish to exchange medication related information~~.}}		{{StartUitgefaseerdVrijeTekst\|The use case "retrieve medication overview" has been deprecated as of 2022-10-25. This use case can no longer be used on the MedMij network. The other two use cases described on this page are still active.}}
	{{FHIR-IG-Afsprakenstelsel-Note}}		{{FHIR-IG-Afsprakenstelsel-Note}}

Regel 176:		Regel 176:
	Search parameter types:		Search parameter types:
	* [http://hl7.org/fhir/STU3/search.html#token token]		* [http://hl7.org/fhir/STU3/search.html#token token]
			{{EindUitgefaseerd}}

	=Use case: retrieve medication information=		=Use case: retrieve medication information=

Mariëtte Lenselink: MM-3382 warning plaatsen

2022-07-27T10:56:33Z

MM-3382 warning plaatsen

← Oudere versie		Versie van 27 jul 2022 10:56
Regel 55:		Regel 55:

	=Use case: retrieve medication overview=		=Use case: retrieve medication overview=
			{{IssueBox\|The MedMij DVZA qualification for 'serve medication overview' ('systeemrolcode' MP9.0.7-MOB-FHIR) is not available (anymore). Please contact us via [mailto:standaarden@medmij.nl standaarden@medmij.nl] if you are a DVZA and wish to exchange medication related information.}}
	{{FHIR-IG-Afsprakenstelsel-Note}}		{{FHIR-IG-Afsprakenstelsel-Note}}

Mik de Jong: MM-3017: Link gewijzigd van https://simplifier.net/NictizSTU3-Zib2017/~packages naar https://simplifier.net/packages/nictiz.fhir.nl.stu3.zib2017

2022-03-25T15:51:57Z

MM-3017: Link gewijzigd van https://simplifier.net/NictizSTU3-Zib2017/~packages naar https://simplifier.net/packages/nictiz.fhir.nl.stu3.zib2017

← Oudere versie		Versie van 25 mrt 2022 15:51
Regel 125:		Regel 125:
	'''Note''' that the medication building blocks are grouped per 'medication treatment' conform the [https://informatiestandaarden.nictiz.nl/wiki/mp:V9.0.7_Ontwerp_medicatieproces#Medicamenteuze_behandeling Medication Process specification]. Grouping SHALL be done by use of a 'medication treatment' identifier. This identifier shall be the same across different related medication resources that constitute a medication treatment. The {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/zib-Medication-MedicationTreatment\|nictiz.fhir.nl.stu3.zib2017\|pkgVersion=1.3.12\|title=zib-Medication-MedicationTreatment extension}} is added to all medication profiles and can be used for this grouping purpose.		'''Note''' that the medication building blocks are grouped per 'medication treatment' conform the [https://informatiestandaarden.nictiz.nl/wiki/mp:V9.0.7_Ontwerp_medicatieproces#Medicamenteuze_behandeling Medication Process specification]. Grouping SHALL be done by use of a 'medication treatment' identifier. This identifier shall be the same across different related medication resources that constitute a medication treatment. The {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/zib-Medication-MedicationTreatment\|nictiz.fhir.nl.stu3.zib2017\|pkgVersion=1.3.12\|title=zib-Medication-MedicationTreatment extension}} is added to all medication profiles and can be used for this grouping purpose.

	{{NoteBoxPackage\|https://simplifier.net/~~NictizSTU3-Zib2017~~/~~~packages~~\|1.3.x\|MedMij:V2019.01_FHIR_IG}}		{{NoteBoxPackage\|https://simplifier.net/packages/nictiz.fhir.nl.stu3.zib2017\|1.3.x\|MedMij:V2019.01_FHIR_IG}}

	{\| class="wikitable"		{\| class="wikitable"
Regel 358:		Regel 358:
	'''Note''' that the medication building blocks are grouped per 'medication treatment' conform the [https://informatiestandaarden.nictiz.nl/wiki/mp:V9.0.7_Ontwerp_medicatieproces#Medicamenteuze_behandeling Medication Process specification]. Grouping SHALL be done by use of a 'medication treatment' identifier. This identifier shall be the same across different related medication resources that constitute a medication treatment. The {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/zib-Medication-MedicationTreatment\|nictiz.fhir.nl.stu3.zib2017\|pkgVersion=1.3.12\|title=zib-Medication-MedicationTreatment extension}} is added to all medication profiles and can be used for this grouping purpose.		'''Note''' that the medication building blocks are grouped per 'medication treatment' conform the [https://informatiestandaarden.nictiz.nl/wiki/mp:V9.0.7_Ontwerp_medicatieproces#Medicamenteuze_behandeling Medication Process specification]. Grouping SHALL be done by use of a 'medication treatment' identifier. This identifier shall be the same across different related medication resources that constitute a medication treatment. The {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/zib-Medication-MedicationTreatment\|nictiz.fhir.nl.stu3.zib2017\|pkgVersion=1.3.12\|title=zib-Medication-MedicationTreatment extension}} is added to all medication profiles and can be used for this grouping purpose.

	{{NoteBoxPackage\|https://simplifier.net/~~NictizSTU3-Zib2017~~/~~~packages~~\|1.3.x\|MedMij:V2019.01_FHIR_IG}}		{{NoteBoxPackage\|https://simplifier.net/packages/nictiz.fhir.nl.stu3.zib2017\|1.3.x\|MedMij:V2019.01_FHIR_IG}}

	{\| class="wikitable" width="1400px"		{\| class="wikitable" width="1400px"
Regel 533:		Regel 533:
	These profiles are derived from the HCIM profiles. This use case has a very specific and stable underlying dataset. Therefore, the profiles contain many mandatory elements. Within the Medication Process dataset, there is a difference between the concept cardinalities '1..* Required' and '1..* Mandatory'.: The first means the element is required to be present, if the system possesses the information and the latter means the element should always be present. Both are mapped to a mandatory cardinality in the FHIR profiles. If the XIS is not able to provide the required information for a mandatory element, it shall use a [http://hl7.org/fhir/STU3/extension-iso21090-nullflavor.html nullFlavor extension] to indicate that and why the information is not present. The PHR should be able to process nullFlavor extensions and values.		These profiles are derived from the HCIM profiles. This use case has a very specific and stable underlying dataset. Therefore, the profiles contain many mandatory elements. Within the Medication Process dataset, there is a difference between the concept cardinalities '1..* Required' and '1..* Mandatory'.: The first means the element is required to be present, if the system possesses the information and the latter means the element should always be present. Both are mapped to a mandatory cardinality in the FHIR profiles. If the XIS is not able to provide the required information for a mandatory element, it shall use a [http://hl7.org/fhir/STU3/extension-iso21090-nullflavor.html nullFlavor extension] to indicate that and why the information is not present. The PHR should be able to process nullFlavor extensions and values.

	{{NoteBoxPackage\|https://simplifier.net/~~NictizSTU3-Zib2017~~/~~~packages~~\|1.3.x\|MedMij:V2019.01_FHIR_IG}}		{{NoteBoxPackage\|https://simplifier.net/packages/nictiz.fhir.nl.stu3.zib2017\|1.3.x\|MedMij:V2019.01_FHIR_IG}}

	{\| class="wikitable" width="1400px"		{\| class="wikitable" width="1400px"

Niek van Galen: Tekst vervangen - "pkgVersion=1.3.10" door "pkgVersion=1.3.12"

2021-04-07T09:31:48Z

Tekst vervangen - "pkgVersion=1.3.10" door "pkgVersion=1.3.12"

Wijzigingen bekijken

Niek van Galen: MM-1656: added guidance on search requests + added examples

2021-03-22T10:08:40Z

MM-1656: added guidance on search requests + added examples

← Oudere versie		Versie van 22 mrt 2021 10:08
Regel 304:		Regel 304:
	'''UsePeriod'''		'''UsePeriod'''
	<pre>1. [base]/MedicationRequest?periodofuse=ge2010-01-01		<pre>1. [base]/MedicationRequest?periodofuse=ge2010-01-01
	2. [base]/MedicationDispense?periodofuse=ge2010-01-01&periodofuse=le2011-12-31		2. [base]/MedicationRequest?periodofuse=le2009-12-31
	3. [base]/MedicationRequest?category=http://snomed.info/sct\|16076005&periodofuse=ge2010-01-01</pre>		3. [base]/MedicationDispense?periodofuse=ge2010-01-01&periodofuse=le2011-12-31
	# Retrieves all MedicationRequest resources that were in effect ~~after~~ 01-01-2010.		4. [base]/MedicationRequest?periodofuse=eq2010-01-01
			5. [base]/MedicationRequest?category=http://snomed.info/sct\|16076005&periodofuse=ge2010-01-01</pre>
			# Retrieves all MedicationRequest resources that were in effect from 01-01-2010.
			# Retrieves all MedicationRequest resources that were in effect before 01-01-2010.
	# Retrieves all MedicationDispense resources that were in effect within a 2 year period.		# Retrieves all MedicationDispense resources that were in effect within a 2 year period.
	# Retrieves all MedicationRequest resources that represent a HCIM MedicationAgreement and were in effect ~~after~~ 01-01-2010.		# Retrieves all MedicationDispense resources that were in effect on 01-01-2010.
			# Retrieves all MedicationRequest resources that represent a HCIM MedicationAgreement and were in effect from 01-01-2010.

	'''DispensePeriod'''		'''DispensePeriod'''
	<pre>1. [base]/MedicationDispense?whenhandedover=ge2010-01-01		<pre>1. [base]/MedicationDispense?whenhandedover=ge2010-01-01
	2. [base]/MedicationDispense?whenhandedover=ge2010-01-01&whenhandedover=le2011-12-31		2. [base]/MedicationDispense?whenhandedover=le2009-12-31
	3. [base]/MedicationDispense?whenhandedover=ge2010-01-01&category=http://snomed.info/sct\|373784005		3. [base]/MedicationDispense?whenhandedover=ge2010-01-01&whenhandedover=le2011-12-31
			4. [base]/MedicationDispense?whenhandedover=eq2010-01-01
			5. [base]/MedicationDispense?whenhandedover=ge2010-01-01&category=http://snomed.info/sct\|373784005
	</pre>		</pre>
	# Retrieves all MedicationDispense resources that were handed over ~~after~~ 01-01-2010.		# Retrieves all MedicationDispense resources that were handed over from 01-01-2010.
			# Retrieves all MedicationDispense resources that were handed over before 01-01-2010.
	# Retrieves all MedicationDispense resources that were handed over within a 2 year period.		# Retrieves all MedicationDispense resources that were handed over within a 2 year period.
	# Retrieves all MedicationDispense resources that represent a HCIM Dispense and ~~were~~ handed over ~~after~~ 01-01-2010.		# Retrieves all MedicationDispense resources that were handed over on 01-01-2010.
			# Retrieves all MedicationDispense resources that represent a HCIM Dispense and handed over from 01-01-2010.

	'''MedicationTreatment'''		'''MedicationTreatment'''
Regel 412:		Regel 420:

	* {{Simplifier\|http://nictiz.nl/fhir/SearchParameter/Medications-category\|nictiz.fhir.nl.stu3.zib2017\|pkgVersion=1.3.10}}		* {{Simplifier\|http://nictiz.nl/fhir/SearchParameter/Medications-category\|nictiz.fhir.nl.stu3.zib2017\|pkgVersion=1.3.10}}
	* {{Simplifier\|http://nictiz.nl/fhir/SearchParameter/Medications-periodofuse\|nictiz.fhir.nl.stu3.zib2017\|pkgVersion=1.3.10}}
	* {{Simplifier\|http://nictiz.nl/fhir/SearchParameter/Medications-medicationtreatment\|nictiz.fhir.nl.stu3.zib2017\|pkgVersion=1.3.10}}		* {{Simplifier\|http://nictiz.nl/fhir/SearchParameter/Medications-medicationtreatment\|nictiz.fhir.nl.stu3.zib2017\|pkgVersion=1.3.10}}
	* {{Simplifier\|http://nictiz.nl/fhir/SearchParameter/Medications-periodofuse\|nictiz.fhir.nl.stu3.zib2017\|pkgVersion=1.3.10}} *		* {{Simplifier\|http://nictiz.nl/fhir/SearchParameter/Medications-periodofuse\|nictiz.fhir.nl.stu3.zib2017\|pkgVersion=1.3.10}} *

	<nowiki>*</nowiki> This SearchParameter searches on the FHIR DataType Period in the PeriodOfUse extension, which is added to profiles on MedicationRequest and MedicationDispense resources. Clients use date parameter searches as described by the [http://hl7.org/fhir/stu3/search.html#date FHIR specification]. Servers are expected to take the [http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse-Duration MedicationUse-Duration extension] into account when processing a client's search. This means that either a Period.start + Period.end or Period.start + Duration is used to determine the search results. To illustrate the expected behavior: if a Period.start and a Duration is known, but not the Period, the Duration should be added to the Period.start date to calculate the Period.end. The calculated Period.end date is then used to determine the search results.		<nowiki>*</nowiki> This SearchParameter searches on the FHIR DataType Period in the PeriodOfUse extension, which is added to profiles on MedicationRequest and MedicationDispense resources. Clients use date parameter searches as described by the [http://hl7.org/fhir/stu3/search.html#date FHIR specification]. Servers are expected to take the [http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse-Duration MedicationUse-Duration extension] into account when processing a client's search. This means that either a Period.start AND Period.end or Period.start AND Duration or Period.end AND Duration is used to determine the search results. To illustrate the expected behavior: if a Period.start and a Duration is known, but not the Period.end, the Duration should be added to the Period.start date to calculate the Period.end. The calculated Period.end date is then used to determine the search results.

	=Use case: retrieve Dispense612ToFHIRConversion from the LSP=		=Use case: retrieve Dispense612ToFHIRConversion from the LSP=

Niek van Galen: /* Message resource content */ HOTFIX: removed a whitespace that caused a faulty URL

2021-01-13T15:14:22Z

Message resource content: HOTFIX: removed a whitespace that caused a faulty URL

← Oudere versie		Versie van 13 jan 2021 15:14
Regel 536:		Regel 536:
	\| Patient		\| Patient
	\| Patient		\| Patient
	\| {{Simplifier\| http://nictiz.nl/fhir/StructureDefinition/mp612-DispenseToFHIRConversion-Patient\|nictiz.fhir.nl.stu3.zib2017\|pkgVersion=1.3.10}}		\| {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/mp612-DispenseToFHIRConversion-Patient\|nictiz.fhir.nl.stu3.zib2017\|pkgVersion=1.3.10}}
	\|-		\|-
	\| Zorgaanbieder		\| Zorgaanbieder

Pieter Edelman: Create prepub environment from MedMij:V2019.01

2020-12-01T13:37:54Z

Create prepub environment from MedMij:V2019.01

← Oudere versie		Versie van 1 dec 2020 13:37
Regel 1:		Regel 1:
			__NOINDEX__
	__NUMBEREDHEADINGS__		__NUMBEREDHEADINGS__
	{{DISPLAYTITLE:MedMij FHIR Implementation Guide Medication Process {{VersieInfo\|Medicatieproces\|release=V2019.01}}}}		{{DISPLAYTITLE:MedMij FHIR Implementation Guide Medication Process {{VersieInfo\|Medicatieproces\|release=V2019.01}}}}
Regel 6:		Regel 7:
	<imagemap>Bestand:Leeswijzer-technisch-banner 03 white.png\|center\|400px\|alt=Afspraken-Functioneel-Technisch		<imagemap>Bestand:Leeswijzer-technisch-banner 03 white.png\|center\|400px\|alt=Afspraken-Functioneel-Technisch
	circle 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]		circle 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
	circle 1013 224 212 [[MedMij:~~V2019~~.01_OntwerpMedicatie\|Functional]]		circle 1013 224 212 [[MedMij:Vprepub-2019.01_OntwerpMedicatie\|Functional]]
	circle 1787 230 212 [[MedMij:~~V2019~~.01_FHIR_IG\|Tecnical]]		circle 1787 230 212 [[MedMij:Vprepub-2019.01_FHIR_IG\|Tecnical]]
	desc none		desc none
	</imagemap>		</imagemap>
Regel 14:		Regel 15:

	=Introduction=		=Introduction=
	[[Bestand:Functioneel-02.png\|link=MedMij:~~V2019~~.01_Ontwerpen \|100px\|rechts\|Functional design\|Go to functional design]]		[[Bestand:Functioneel-02.png\|link=MedMij:Vprepub-2019.01_Ontwerpen \|100px\|rechts\|Functional design\|Go to functional design]]

	This page describes patient's use cases, in a personal health record (PHR) context, in relation to the information standard [https://www.nictiz.nl/standaardisatie/informatiestandaarden/informatiestandaard-medicatieproces/ Medication Process] (MP). These use cases are based on version 9.x of this standard. Functional specification of these use cases are described in the [[MedMij:~~V2019~~.01_Ontwerpen\| functional design wiki page]]. The technical specification is described here. HL7 FHIR STU3 is used for this purpose.		This page describes patient's use cases, in a personal health record (PHR) context, in relation to the information standard [https://www.nictiz.nl/standaardisatie/informatiestandaarden/informatiestandaard-medicatieproces/ Medication Process] (MP). These use cases are based on version 9.x of this standard. Functional specification of these use cases are described in the [[MedMij:Vprepub-2019.01_Ontwerpen\| functional design wiki page]]. The technical specification is described here. HL7 FHIR STU3 is used for this purpose.

	The Medication Process information building blocks are adopted by 'Registratie aan de Bron' and converted to Health and Care Information models (HCIM), also called zibs. In order to exchange medication information between systems, FHIR representations of these HCIMs are made and used in the transactions described on this page.		The Medication Process information building blocks are adopted by 'Registratie aan de Bron' and converted to Health and Care Information models (HCIM), also called zibs. In order to exchange medication information between systems, FHIR representations of these HCIMs are made and used in the transactions described on this page.

	Use cases:		Use cases:
	* [[MedMij:~~V2019~~.01_FHIR_MedicationProcess#Use_case:_retrieve_medication_overview\|Retrieve a medication overview]]		* [[MedMij:Vprepub-2019.01_FHIR_MedicationProcess#Use_case:_retrieve_medication_overview\|Retrieve a medication overview]]
	* [[MedMij:~~V2019~~.01_FHIR_MedicationProcess#Use_case:_retrieve_medication_information\|Retrieve medication information]]		* [[MedMij:Vprepub-2019.01_FHIR_MedicationProcess#Use_case:_retrieve_medication_information\|Retrieve medication information]]
	* [[MedMij:~~V2019~~.01_FHIR_MedicationProcess#Use_case:_retrieve_Dispense612ToFHIRConversion_from_the_LSP\|Retrieve Dispense612ToFHIRConversion]]		* [[MedMij:Vprepub-2019.01_FHIR_MedicationProcess#Use_case:_retrieve_Dispense612ToFHIRConversion_from_the_LSP\|Retrieve Dispense612ToFHIRConversion]]

	=Actors involved=		=Actors involved=
Regel 589:		Regel 590:

	=Terminology, NamingSystems, Mappings=		=Terminology, NamingSystems, Mappings=
	{{MedMij:~~V2019~~.01_Template_Terminologies_NamingSystems_Mappings\|id1=Message_content\|t1=Retrieve medication overview response message content\|id2=Message_resource_content\|t2=Retrieve medication information response message \|id3=Message_resource_content_2\|t3=Retrieve Dispense612ToFHIRConversion response message }}		{{MedMij:Vprepub-2019.01_Template_Terminologies_NamingSystems_Mappings\|id1=Message_content\|t1=Retrieve medication overview response message content\|id2=Message_resource_content\|t2=Retrieve medication information response message \|id3=Message_resource_content_2\|t3=Retrieve Dispense612ToFHIRConversion response message }}

	=Examples=		=Examples=
Regel 598:		Regel 599:

	=Release notes=		=Release notes=
	Release notes can be found on the [[MedMij:~~V2019~~.01_OntwerpMedicatie#Release_notes\| functional design page]].		Release notes can be found on the [[MedMij:Vprepub-2019.01_OntwerpMedicatie#Release_notes\| functional design page]].

Pieter Edelman: Gekopieerd van MedMij:V2019.01 FHIR MedicationProcess, versie 18426

2020-12-01T13:37:44Z

Gekopieerd van MedMij:V2019.01 FHIR MedicationProcess, versie 18426

← Oudere versie	Versie van 1 dec 2020 13:37
(geen verschil)

Jorn Duwel: MM-1386: changes for KCR Oktober

2020-10-27T09:23:38Z

MM-1386: changes for KCR Oktober

← Oudere versie		Versie van 27 okt 2020 09:23
Regel 589:		Regel 589:

	=Terminology, NamingSystems, Mappings=		=Terminology, NamingSystems, Mappings=
			{{MedMij:V2019.01_Template_Terminologies_NamingSystems_Mappings\|id1=Message_content\|t1=Retrieve medication overview response message content\|id2=Message_resource_content\|t2=Retrieve medication information response message \|id3=Message_resource_content_2\|t3=Retrieve Dispense612ToFHIRConversion response message }}
	~~===Terminology===~~
	~~Relevant ValueSets can be found through the ValueSet bindings in the listed StructureDefinitions. All ValueSets can be found here [https~~:~~//simplifier~~.~~net/NictizSTU3-Zib2017/~resources?category~~=~~ValueSet here] and can be downloaded as a .zip in XML or JSON format.~~

	===~~NamingSystems~~===
	~~Relevant NamingSystems can be found [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=NamingSystem here].~~

	~~===Mappings===~~
	A FHIR ConceptMap resource is provided when a FHIR value set is used instead of a HCIM value set. A ConceptMap maps the values between the two value sets. These ConceptMaps can be found [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=ConceptMap here].

	~~An explanation about mappings can be found at [[MedMij:V2019.01_FHIR_IG#Mapping_of_coded_concepts\|Mapping of coded concepts]].~~

	=Examples=		=Examples=

Pieter Edelman: MM-1379: Remove broken embedded Simplifier rendering

2020-09-29T09:32:46Z

MM-1379: Remove broken embedded Simplifier rendering

← Oudere versie		Versie van 29 sep 2020 09:32
Regel 112:		Regel 112:
	=====Message content=====		=====Message content=====
	The outcome of the {{Simplifier\|http://nictiz.nl/fhir/OperationDefinition/Medication-Overview\|nictiz.fhir.nl.stu3.zib2017\|pkgVersion=1.3.10\|title=medication-overview operation}} is the body of the medication overview request message. Successful processing of this operation should result in a Bundle recourse, containing one List and one Patient resource as entries along with all the resources that represent the current medication overview. These resources SHALL be referenced from the List resource. The clinical content of the medication overview is defined in the [https://informatiestandaarden.nictiz.nl/wiki/mp:V9.0.7_Ontwerp_medicatieproces#Medicatieoverzicht_en_afleidingsregels Medication Process specification]. The functional dataset of the medication overview can be found on [http://decor.nictiz.nl/medicatieproces/mp-html-20170829T141253/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.148-2016-11-08T103441.html decor.nictiz.nl].		The outcome of the {{Simplifier\|http://nictiz.nl/fhir/OperationDefinition/Medication-Overview\|nictiz.fhir.nl.stu3.zib2017\|pkgVersion=1.3.10\|title=medication-overview operation}} is the body of the medication overview request message. Successful processing of this operation should result in a Bundle recourse, containing one List and one Patient resource as entries along with all the resources that represent the current medication overview. These resources SHALL be referenced from the List resource. The clinical content of the medication overview is defined in the [https://informatiestandaarden.nictiz.nl/wiki/mp:V9.0.7_Ontwerp_medicatieproces#Medicatieoverzicht_en_afleidingsregels Medication Process specification]. The functional dataset of the medication overview can be found on [http://decor.nictiz.nl/medicatieproces/mp-html-20170829T141253/tr-2.16.840.1.113883.2.4.3.11.60.20.77.4.148-2016-11-08T103441.html decor.nictiz.nl].


	~~<html>~~
	~~<iframe width="750" frameborder="1" height="400" src=https://www.simplifier.net/embed/render?id=NictizSTU3-Zib2017/Medication-Overview frameborder="0" align="middle"></iframe>~~
	~~</html>~~

	The content in the response message SHALL be a valid instance of the following profiles. Clicking on the link will open the formal definition on Simplifier.net.		The content in the response message SHALL be a valid instance of the following profiles. Clicking on the link will open the formal definition on Simplifier.net.

← Oudere versie		Versie van 25 mrt 2022 15:51
Regel 125:		Regel 125:
	'''Note''' that the medication building blocks are grouped per 'medication treatment' conform the [https://informatiestandaarden.nictiz.nl/wiki/mp:V9.0.7_Ontwerp_medicatieproces#Medicamenteuze_behandeling Medication Process specification]. Grouping SHALL be done by use of a 'medication treatment' identifier. This identifier shall be the same across different related medication resources that constitute a medication treatment. The {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/zib-Medication-MedicationTreatment\|nictiz.fhir.nl.stu3.zib2017\|pkgVersion=1.3.12\|title=zib-Medication-MedicationTreatment extension}} is added to all medication profiles and can be used for this grouping purpose.		'''Note''' that the medication building blocks are grouped per 'medication treatment' conform the [https://informatiestandaarden.nictiz.nl/wiki/mp:V9.0.7_Ontwerp_medicatieproces#Medicamenteuze_behandeling Medication Process specification]. Grouping SHALL be done by use of a 'medication treatment' identifier. This identifier shall be the same across different related medication resources that constitute a medication treatment. The {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/zib-Medication-MedicationTreatment\|nictiz.fhir.nl.stu3.zib2017\|pkgVersion=1.3.12\|title=zib-Medication-MedicationTreatment extension}} is added to all medication profiles and can be used for this grouping purpose.

	{{NoteBoxPackage\|https://simplifier.net/~~NictizSTU3-Zib2017~~/~~~packages~~\|1.3.x\|MedMij:V2019.01_FHIR_IG}}		{{NoteBoxPackage\|https://simplifier.net/packages/nictiz.fhir.nl.stu3.zib2017\|1.3.x\|MedMij:V2019.01_FHIR_IG}}

	{\| class="wikitable"		{\| class="wikitable"
Regel 358:		Regel 358:
	'''Note''' that the medication building blocks are grouped per 'medication treatment' conform the [https://informatiestandaarden.nictiz.nl/wiki/mp:V9.0.7_Ontwerp_medicatieproces#Medicamenteuze_behandeling Medication Process specification]. Grouping SHALL be done by use of a 'medication treatment' identifier. This identifier shall be the same across different related medication resources that constitute a medication treatment. The {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/zib-Medication-MedicationTreatment\|nictiz.fhir.nl.stu3.zib2017\|pkgVersion=1.3.12\|title=zib-Medication-MedicationTreatment extension}} is added to all medication profiles and can be used for this grouping purpose.		'''Note''' that the medication building blocks are grouped per 'medication treatment' conform the [https://informatiestandaarden.nictiz.nl/wiki/mp:V9.0.7_Ontwerp_medicatieproces#Medicamenteuze_behandeling Medication Process specification]. Grouping SHALL be done by use of a 'medication treatment' identifier. This identifier shall be the same across different related medication resources that constitute a medication treatment. The {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/zib-Medication-MedicationTreatment\|nictiz.fhir.nl.stu3.zib2017\|pkgVersion=1.3.12\|title=zib-Medication-MedicationTreatment extension}} is added to all medication profiles and can be used for this grouping purpose.

	{{NoteBoxPackage\|https://simplifier.net/~~NictizSTU3-Zib2017~~/~~~packages~~\|1.3.x\|MedMij:V2019.01_FHIR_IG}}		{{NoteBoxPackage\|https://simplifier.net/packages/nictiz.fhir.nl.stu3.zib2017\|1.3.x\|MedMij:V2019.01_FHIR_IG}}

	{\| class="wikitable" width="1400px"		{\| class="wikitable" width="1400px"
Regel 533:		Regel 533:
	These profiles are derived from the HCIM profiles. This use case has a very specific and stable underlying dataset. Therefore, the profiles contain many mandatory elements. Within the Medication Process dataset, there is a difference between the concept cardinalities '1..* Required' and '1..* Mandatory'.: The first means the element is required to be present, if the system possesses the information and the latter means the element should always be present. Both are mapped to a mandatory cardinality in the FHIR profiles. If the XIS is not able to provide the required information for a mandatory element, it shall use a [http://hl7.org/fhir/STU3/extension-iso21090-nullflavor.html nullFlavor extension] to indicate that and why the information is not present. The PHR should be able to process nullFlavor extensions and values.		These profiles are derived from the HCIM profiles. This use case has a very specific and stable underlying dataset. Therefore, the profiles contain many mandatory elements. Within the Medication Process dataset, there is a difference between the concept cardinalities '1..* Required' and '1..* Mandatory'.: The first means the element is required to be present, if the system possesses the information and the latter means the element should always be present. Both are mapped to a mandatory cardinality in the FHIR profiles. If the XIS is not able to provide the required information for a mandatory element, it shall use a [http://hl7.org/fhir/STU3/extension-iso21090-nullflavor.html nullFlavor extension] to indicate that and why the information is not present. The PHR should be able to process nullFlavor extensions and values.

	{{NoteBoxPackage\|https://simplifier.net/~~NictizSTU3-Zib2017~~/~~~packages~~\|1.3.x\|MedMij:V2019.01_FHIR_IG}}		{{NoteBoxPackage\|https://simplifier.net/packages/nictiz.fhir.nl.stu3.zib2017\|1.3.x\|MedMij:V2019.01_FHIR_IG}}

	{\| class="wikitable" width="1400px"		{\| class="wikitable" width="1400px"