MedMij:V2020.01/FHIR LaboratoryResults - Bewerkingsoverzicht

Niek van Galen: Beveiligde "MedMij:V2020.01/FHIR LaboratoryResults": Protect production page from accidental edits ([Bewerken=Alleen beheerders toestaan] (vervalt niet) [Hernoemen=Alleen beheerders toestaan] (vervalt niet))

2022-11-22T13:35:07Z

Beveiligde "MedMij:V2020.01/FHIR LaboratoryResults": Protect production page from accidental edits ([Bewerken=Alleen beheerders toestaan] (vervalt niet) [Hernoemen=Alleen beheerders toestaan] (vervalt niet))

← Oudere versie	Versie van 22 nov 2022 13:35
(geen verschil)

Niek van Galen: Publish prepub to live environment

2022-11-22T13:34:53Z

Publish prepub to live environment

← Oudere versie		Versie van 22 nov 2022 13:34
Regel 1:		Regel 1:
	__NUMBEREDHEADINGS__		__NUMBEREDHEADINGS__
	{{DISPLAYTITLE:MedMij FHIR Implementation Guide LaboratoryResults {{VersieInfo\|Laboratoriumresultaten}}}}		{{DISPLAYTITLE:MedMij FHIR Implementation Guide LaboratoryResults {{VersieInfo\|Laboratoriumresultaten}}}}
	{{MedMij:~~Vprepub-2020~~.01/Issuebox_FHIR_IG}}		{{MedMij:V2020.01/Issuebox_FHIR_IG}}

	[[Bestand:MedMij2.png \|link=https://www.medmij.nl/\|rechts\|Naar medmij.nl]]		[[Bestand:MedMij2.png \|link=https://www.medmij.nl/\|rechts\|Naar medmij.nl]]
Regel 7:		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:~~Vprepub-2020~~.01/OntwerpLabresult\|Functioneel]]		circle 1013 224 212 [[MedMij:V2020.01/OntwerpLabresult\|Functioneel]]
	circle 1787 230 212 [[MedMij:~~Vprepub-2020~~.01/FHIR_IG\|Technisch]]		circle 1787 230 212 [[MedMij:V2020.01/FHIR_IG\|Technisch]]
	desc none		desc none
	</imagemap>		</imagemap>

	=Introduction=		=Introduction=
	[[Bestand:Functioneel-02.png\|link=MedMij:~~Vprepub-2020~~.01/Ontwerpen \|100px\|rechts\|Functional design\|Go to functional design]]		[[Bestand:Functioneel-02.png\|link=MedMij:V2020.01/Ontwerpen \|100px\|rechts\|Functional design\|Go to functional design]]

	This page describes patient's use cases for the retrieval of laboratory results, in a personal health environment (PHR) context. Functional specifications are described at the [[MedMij:~~Vprepub-2020~~.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 for the retrieval of laboratory results, in a personal health environment (PHR) context. Functional specifications are described at the [[MedMij:V2020.01/Ontwerpen\| functional design wiki page]]. The technical specification is described here. HL7 FHIR STU3 is used for this purpose.

	'''Note''': This implementation guide builds on the general guidelines described in the [[MedMij:~~Vprepub-2020~~.01/FHIR_IG#Use case overarching principles\|use case overarching principles]].		'''Note''': This implementation guide builds on the general guidelines described in the [[MedMij:V2020.01/FHIR_IG#Use case overarching principles\|use case overarching principles]].

	Many laboratory result observations have important relationships to other observations and need to be grouped together. [http://hl7.org/fhir/observation.html#10.1.4.1 The FHIR specification] defines three structures to do this: DiagnosticReport and DiagnosticReport.result, Observation and Observation.component, and Observation and Observation.related. For the transactions of laboratory results retrieval, the following two grouping structures are relevant.		Many laboratory result observations have important relationships to other observations and need to be grouped together. [http://hl7.org/fhir/observation.html#10.1.4.1 The FHIR specification] defines three structures to do this: DiagnosticReport and DiagnosticReport.result, Observation and Observation.component, and Observation and Observation.related. For the transactions of laboratory results retrieval, the following two grouping structures are relevant.
Regel 29:		Regel 29:
	Both structures may exist in a XIS. Therefore, two transactions are defined to retrieve a patient's laboratory results. The transaction content either consists of a single and related laboratory results structure or a complete diagnostic report that adds more clinical meaning to the single and related laboratory results. The transactions:		Both structures may exist in a XIS. Therefore, two transactions are defined to retrieve a patient's laboratory results. The transaction content either consists of a single and related laboratory results structure or a complete diagnostic report that adds more clinical meaning to the single and related laboratory results. The transactions:

	* [[MedMij:~~Vprepub-2020~~.01/FHIR_LaboratoryResults#Use_case:_retrieve_laboratory_results\| Retrieve laboratory results]]		* [[MedMij:V2020.01/FHIR_LaboratoryResults#Use_case:_retrieve_laboratory_results\| Retrieve laboratory results]]
	* [[MedMij:~~Vprepub-2020~~.01/FHIR_LaboratoryResults#Use_case:_retrieve_laboratory_results_DiagnosticReport\| Retrieve laboratory results DiagnosticReport]]		* [[MedMij:V2020.01/FHIR_LaboratoryResults#Use_case:_retrieve_laboratory_results_DiagnosticReport\| Retrieve laboratory results DiagnosticReport]]

	=Actors involved=		=Actors involved=
Regel 132:		Regel 132:
	The returned data to the PHR should conform to the HCIMs and their associated profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.		The returned data to the PHR should conform to the HCIMs and their associated profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.

	{{MedMij:~~Vprepub-2020~~.01/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}		{{MedMij:V2020.01/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}

	{\| class="wikitable" width="1400px"		{\| class="wikitable" width="1400px"
Regel 234:		Regel 234:
	The returned data to the PHR should conform to the HCIMS and their associate profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.		The returned data to the PHR should conform to the HCIMS and their associate profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.

	{{MedMij:~~Vprepub-2020~~.01/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017\|v1Min=2.0.0}}		{{MedMij:V2020.01/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017\|v1Min=2.0.0}}

	{\| class="wikitable" width="1400px"		{\| class="wikitable" width="1400px"
Regel 269:		Regel 269:

	=Release notes=		=Release notes=
	Release notes can be found on the [[MedMij:~~Vprepub-2020~~.01/OntwerpLabresult#Release_notes\| functional design page]].		Release notes can be found on the [[MedMij:V2020.01/OntwerpLabresult#Release_notes\| functional design page]].

Niek van Galen: Gekopieerd van MedMij:Vprepub-2020.01/FHIR LaboratoryResults, versie 35004

2022-11-22T13:34:19Z

Gekopieerd van MedMij:Vprepub-2020.01/FHIR LaboratoryResults, versie 35004

← Oudere versie	Versie van 22 nov 2022 13:34
(geen verschil)

Pieter Edelman: HOTFIX: Remove incorrect call to included template

2021-03-30T11:36:21Z

HOTFIX: Remove incorrect call to included template

← Oudere versie		Versie van 30 mrt 2021 11:36
Regel 132:		Regel 132:
	The returned data to the PHR should conform to the HCIMs and their associated profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.		The returned data to the PHR should conform to the HCIMs and their associated profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.

	{{MedMij:Vprepub-~~V2020~~.01/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}		{{MedMij:Vprepub-2020.01/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}

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

Niek van Galen: MM-1899: updated notebox to be ready for a minimum and maximum package version

2021-03-22T09:19:09Z

MM-1899: updated notebox to be ready for a minimum and maximum package version

← Oudere versie		Versie van 22 mrt 2021 09:19
Regel 132:		Regel 132:
	The returned data to the PHR should conform to the HCIMs and their associated profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.		The returned data to the PHR should conform to the HCIMs and their associated profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.

	{{MedMij:Vprepub-~~2020~~.01/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}		{{MedMij:Vprepub-V2020.01/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}

	{\| class="wikitable" width="1400px"		{\| class="wikitable" width="1400px"
Regel 234:		Regel 234:
	The returned data to the PHR should conform to the HCIMS and their associate profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.		The returned data to the PHR should conform to the HCIMS and their associate profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.

	{{MedMij:Vprepub-2020.01/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}		{{MedMij:Vprepub-2020.01/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017\|v1Min=2.0.0}}

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

Pieter Edelman: Tekst vervangen - "MedMij:Vprepub" door "MedMij:Vprepub-2020.01"

2020-12-01T12:59:24Z

Tekst vervangen - "MedMij:Vprepub" door "MedMij:Vprepub-2020.01"

← Oudere versie		Versie van 1 dec 2020 12:59
Regel 1:		Regel 1:
	__NUMBEREDHEADINGS__		__NUMBEREDHEADINGS__
	{{DISPLAYTITLE:MedMij FHIR Implementation Guide LaboratoryResults {{VersieInfo\|Laboratoriumresultaten}}}}		{{DISPLAYTITLE:MedMij FHIR Implementation Guide LaboratoryResults {{VersieInfo\|Laboratoriumresultaten}}}}
	{{MedMij:Vprepub/Issuebox_FHIR_IG}}		{{MedMij:Vprepub-2020.01/Issuebox_FHIR_IG}}

	[[Bestand:MedMij2.png \|link=https://www.medmij.nl/\|rechts\|Naar medmij.nl]]		[[Bestand:MedMij2.png \|link=https://www.medmij.nl/\|rechts\|Naar medmij.nl]]
Regel 7:		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:Vprepub/OntwerpLabresult\|Functioneel]]		circle 1013 224 212 [[MedMij:Vprepub-2020.01/OntwerpLabresult\|Functioneel]]
	circle 1787 230 212 [[MedMij:Vprepub/FHIR_IG\|Technisch]]		circle 1787 230 212 [[MedMij:Vprepub-2020.01/FHIR_IG\|Technisch]]
	desc none		desc none
	</imagemap>		</imagemap>

	=Introduction=		=Introduction=
	[[Bestand:Functioneel-02.png\|link=MedMij:Vprepub/Ontwerpen \|100px\|rechts\|Functional design\|Go to functional design]]		[[Bestand:Functioneel-02.png\|link=MedMij:Vprepub-2020.01/Ontwerpen \|100px\|rechts\|Functional design\|Go to functional design]]

	This page describes patient's use cases for the retrieval of laboratory results, in a personal health environment (PHR) context. Functional specifications are described at the [[MedMij:Vprepub/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 for the retrieval of laboratory results, in a personal health environment (PHR) context. Functional specifications are described at the [[MedMij:Vprepub-2020.01/Ontwerpen\| functional design wiki page]]. The technical specification is described here. HL7 FHIR STU3 is used for this purpose.

	'''Note''': This implementation guide builds on the general guidelines described in the [[MedMij:Vprepub/FHIR_IG#Use case overarching principles\|use case overarching principles]].		'''Note''': This implementation guide builds on the general guidelines described in the [[MedMij:Vprepub-2020.01/FHIR_IG#Use case overarching principles\|use case overarching principles]].

	Many laboratory result observations have important relationships to other observations and need to be grouped together. [http://hl7.org/fhir/observation.html#10.1.4.1 The FHIR specification] defines three structures to do this: DiagnosticReport and DiagnosticReport.result, Observation and Observation.component, and Observation and Observation.related. For the transactions of laboratory results retrieval, the following two grouping structures are relevant.		Many laboratory result observations have important relationships to other observations and need to be grouped together. [http://hl7.org/fhir/observation.html#10.1.4.1 The FHIR specification] defines three structures to do this: DiagnosticReport and DiagnosticReport.result, Observation and Observation.component, and Observation and Observation.related. For the transactions of laboratory results retrieval, the following two grouping structures are relevant.
Regel 29:		Regel 29:
	Both structures may exist in a XIS. Therefore, two transactions are defined to retrieve a patient's laboratory results. The transaction content either consists of a single and related laboratory results structure or a complete diagnostic report that adds more clinical meaning to the single and related laboratory results. The transactions:		Both structures may exist in a XIS. Therefore, two transactions are defined to retrieve a patient's laboratory results. The transaction content either consists of a single and related laboratory results structure or a complete diagnostic report that adds more clinical meaning to the single and related laboratory results. The transactions:

	* [[MedMij:Vprepub/FHIR_LaboratoryResults#Use_case:_retrieve_laboratory_results\| Retrieve laboratory results]]		* [[MedMij:Vprepub-2020.01/FHIR_LaboratoryResults#Use_case:_retrieve_laboratory_results\| Retrieve laboratory results]]
	* [[MedMij:Vprepub/FHIR_LaboratoryResults#Use_case:_retrieve_laboratory_results_DiagnosticReport\| Retrieve laboratory results DiagnosticReport]]		* [[MedMij:Vprepub-2020.01/FHIR_LaboratoryResults#Use_case:_retrieve_laboratory_results_DiagnosticReport\| Retrieve laboratory results DiagnosticReport]]

	=Actors involved=		=Actors involved=
Regel 132:		Regel 132:
	The returned data to the PHR should conform to the HCIMs and their associated profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.		The returned data to the PHR should conform to the HCIMs and their associated profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.

	{{MedMij:Vprepub/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}		{{MedMij:Vprepub-2020.01/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}

	{\| class="wikitable" width="1400px"		{\| class="wikitable" width="1400px"
Regel 234:		Regel 234:
	The returned data to the PHR should conform to the HCIMS and their associate profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.		The returned data to the PHR should conform to the HCIMS and their associate profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.

	{{MedMij:Vprepub/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}		{{MedMij:Vprepub-2020.01/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}

	{\| class="wikitable" width="1400px"		{\| class="wikitable" width="1400px"
Regel 269:		Regel 269:

	=Release notes=		=Release notes=
	Release notes can be found on the [[MedMij:Vprepub/OntwerpLabresult#Release_notes\| functional design page]].		Release notes can be found on the [[MedMij:Vprepub-2020.01/OntwerpLabresult#Release_notes\| functional design page]].

Pieter Edelman: Pieter Edelman heeft de pagina MedMij:Vprepub/FHIR LaboratoryResults hernoemd naar MedMij:Vprepub-2020.01/FHIR LaboratoryResults zonder een doorverwijzing achter te laten: Generaliseren van prepub-mechanisme

2020-12-01T12:49:25Z

Pieter Edelman heeft de pagina MedMij:Vprepub/FHIR LaboratoryResults hernoemd naar MedMij:Vprepub-2020.01/FHIR LaboratoryResults zonder een doorverwijzing achter te laten: Generaliseren van prepub-mechanisme

← Oudere versie	Versie van 1 dec 2020 12:49
(geen verschil)

Pieter Edelman: Tekst vervangen - "MedMij:Vissue-MM-1522/NoteBoxPackage" door "MedMij:Vprepub/NoteBoxPackage"

2020-11-20T13:14:15Z

Tekst vervangen - "MedMij:Vissue-MM-1522/NoteBoxPackage" door "MedMij:Vprepub/NoteBoxPackage"

← Oudere versie		Versie van 20 nov 2020 13:14
Regel 132:		Regel 132:
	The returned data to the PHR should conform to the HCIMs and their associated profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.		The returned data to the PHR should conform to the HCIMs and their associated profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.

	{{MedMij:~~Vissue-MM-1522~~/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}		{{MedMij:Vprepub/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}

	{\| class="wikitable" width="1400px"		{\| class="wikitable" width="1400px"
Regel 234:		Regel 234:
	The returned data to the PHR should conform to the HCIMS and their associate profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.		The returned data to the PHR should conform to the HCIMS and their associate profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.

	{{MedMij:~~Vissue-MM-1522~~/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}		{{MedMij:Vprepub/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}

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

Jorn Duwel: MM-1522: Removing 'Terminology...' section, removing references to Sjabloon:Voorbeelden, updating NoteBoxPackage to 2020.01 version

2020-11-13T15:36:43Z

MM-1522: Removing 'Terminology...' section, removing references to Sjabloon:Voorbeelden, updating NoteBoxPackage to 2020.01 version

← Oudere versie		Versie van 13 nov 2020 15:36
Regel 132:		Regel 132:
	The returned data to the PHR should conform to the HCIMs and their associated profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.		The returned data to the PHR should conform to the HCIMs and their associated profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.

	{{MedMij:NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}		{{MedMij:Vissue-MM-1522/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}

	{\| class="wikitable" width="1400px"		{\| class="wikitable" width="1400px"
Regel 159:		Regel 159:
	\| {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation\|nictiz.fhir.nl.stu3.zib2017}}		\| {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation\|nictiz.fhir.nl.stu3.zib2017}}
	\|}		\|}
	~~{{Sjabloon:Voorbeelden}}~~

	====Expected Actions====		====Expected Actions====
	The PHR shall process the results according to application-defined rules. The PHR should be robust as the response may contain observation and specimen resources that match the query parameters.		The PHR shall process the results according to application-defined rules. The PHR should be robust as the response may contain observation and specimen resources that match the query parameters.

	~~===Examples===~~
	~~{{Sjabloon:Voorbeelden}}~~

	=Use case: retrieve laboratory results DiagnosticReport=		=Use case: retrieve laboratory results DiagnosticReport=
Regel 238:		Regel 234:
	The returned data to the PHR should conform to the HCIMS and their associate profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.		The returned data to the PHR should conform to the HCIMS and their associate profiles listed in the table below. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.

	{{MedMij:NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}		{{MedMij:Vissue-MM-1522/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}

	{\| class="wikitable" width="1400px"		{\| class="wikitable" width="1400px"
Regel 268:		Regel 264:
	\| {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation\|nictiz.fhir.nl.stu3.zib2017}}		\| {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation\|nictiz.fhir.nl.stu3.zib2017}}
	\|}		\|}
	~~{{Sjabloon:Voorbeelden}}~~

	====Expected Actions====		====Expected Actions====
	The PHR shall process the results according to application-defined rules. The PHR should be robust as the response may contain DiagnosticReport, Observation and Specimen resources that match the query parameters.		The PHR shall process the results according to application-defined rules. The PHR should be robust as the response may contain DiagnosticReport, Observation and Specimen resources that match the query parameters.

	~~=Terminology, NamingSystems, Mappings=~~
	{{MedMij:Vissue-MM-1386/Template_Terminologies_NamingSystems_Mappings\|id1=Message_Semantics_2\|t1=Retrieve laboratory results response message semantics\|id2=Message_Semantics_4\|t2=Retrieve laboratory results DiagnosticReport response message semantics}}

	=Release notes=		=Release notes=
	Release notes can be found on the [[MedMij:Vprepub/OntwerpLabresult#Release_notes\| functional design page]].		Release notes can be found on the [[MedMij:Vprepub/OntwerpLabresult#Release_notes\| functional design page]].

Jorn Duwel: MM-1386: Refer to the relevant packages in the 'Terminology, ...' section

2020-10-21T10:06:44Z

MM-1386: Refer to the relevant packages in the 'Terminology, ...' section

← Oudere versie		Versie van 21 okt 2020 10:06
Regel 274:		Regel 274:

	=Terminology, NamingSystems, Mappings=		=Terminology, NamingSystems, Mappings=
			{{MedMij:Vissue-MM-1386/Template_Terminologies_NamingSystems_Mappings\|id1=Message_Semantics_2\|t1=Retrieve laboratory results response message semantics\|id2=Message_Semantics_4\|t2=Retrieve laboratory results DiagnosticReport response message semantics}}
	~~===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:Vprepub/FHIR_IG#Mapping_of_coded_concepts\|Mapping of coded concepts]].~~

	=Release notes=		=Release notes=
	Release notes can be found on the [[MedMij:Vprepub/OntwerpLabresult#Release_notes\| functional design page]].		Release notes can be found on the [[MedMij:Vprepub/OntwerpLabresult#Release_notes\| functional design page]].