MedMij:Vprepub-2020.01/FHIR GP Data - Bewerkingsoverzicht

Pieter Edelman: MM-2136: Make clear that the optional "periodOfUse" is about the source data, not the query parameter

2021-06-21T08:03:18Z

MM-2136: Make clear that the optional "periodOfUse" is about the source data, not the query parameter

← Oudere versie		Versie van 21 jun 2021 08:03
Regel 120:		Regel 120:
	\| style="vertical-align:top;"\|Current medication		\| style="vertical-align:top;"\|Current medication
	\| style="vertical-align:top;"\|[https://zibs.nl/wiki/MedicationAgreement-v1.0(2017EN) MedicationAgreement v1.0 (2017)]		\| style="vertical-align:top;"\|[https://zibs.nl/wiki/MedicationAgreement-v1.0(2017EN) MedicationAgreement v1.0 (2017)]
	\| style="vertical-align:top;"\|MedicationAgreement <br/>The prescriber proposed use of medication that the patient agrees with. The agreement may signal starting, repeating, updating or stopping the medication. The list of MedicationAgreements is also known as the list of medication the patient is '''currently''' using. Note that ~~current~~ means that the period of use is still active. This is conveyed in the MedicationRequest.extension periodOfUse. This may or may not me populated. If it is not, the Medicationagreement is assumed to be current. The search parameter {{Simplifier\|http://nictiz.nl/fhir/SearchParameter/Medications-periodofuse\|nictiz.fhir.nl.stu3.zib2017\|title=periodofuse}} allows filtering for current ~~medicationagreements~~		\| style="vertical-align:top;"\|MedicationAgreement <br/>The prescriber proposed use of medication that the patient agrees with. The agreement may signal starting, repeating, updating or stopping the medication. The list of MedicationAgreements is also known as the list of medication the patient is '''currently''' using. Note that "currently" means that the period of use is still active. This is conveyed in the MedicationRequest extension {{fhir\|periodOfUse}}. This extension may or may not be populated. If it is not, the Medicationagreement is assumed to be current. The search parameter {{Simplifier\|http://nictiz.nl/fhir/SearchParameter/Medications-periodofuse\|nictiz.fhir.nl.stu3.zib2017\|title=periodofuse}} allows filtering for current MedicationAgreements.
	\| style="vertical-align:top;"\|<pre>GET [base]/MedicationRequest?periodofuse=ge[today]&category=http://snomed.info/sct\|16076005&_include=MedicationRequest:medication</pre>		\| style="vertical-align:top;"\|<pre>GET [base]/MedicationRequest?periodofuse=ge[today]&category=http://snomed.info/sct\|16076005&_include=MedicationRequest:medication</pre>
	\|-		\|-

Pieter Edelman: MM-1521: Add guidance of referencing nl-core-episodeofcare with new extension (plus minor wording fixes regarding episodes and encounters)

2021-04-19T11:36:22Z

MM-1521: Add guidance of referencing nl-core-episodeofcare with new extension (plus minor wording fixes regarding episodes and encounters)

← Oudere versie		Versie van 19 apr 2021 11:36
Regel 162:		Regel 162:
	\| Information from an encounter, recorded in free text using the SOAP structure. The acronym SOAP stands for Subjective, Objective, Assessment and Plan. The E entry contains the consultation conclusion and the P entry contains potential next steps.<br/><br/>Note that the profile for SOAP entries is yet to be created and the code system value is preliminary		\| Information from an encounter, recorded in free text using the SOAP structure. The acronym SOAP stands for Subjective, Objective, Assessment and Plan. The E entry contains the consultation conclusion and the P entry contains potential next steps.<br/><br/>Note that the profile for SOAP entries is yet to be created and the code system value is preliminary
	\| <pre>GET [base]/Composition?type=http://loinc.org\|67781-5</pre>		\| <pre>GET [base]/Composition?type=http://loinc.org\|67781-5</pre>
	{{NoteBox\|The underlying guideline does not explicitly mention encounters nor partial encounters (Dutch: ''~~Deelcontacten~~''), but journal entries are normally 'grouped' as encounters based on the entry complaint (journal entry type Subjective). If multiple entry complaints have been discussed based during a single encounter, these are regarded as partial encounters.		{{NoteBox\|The underlying guideline does not explicitly mention encounters nor partial encounters (Dutch: ''deelcontacten''), but journal entries are normally 'grouped' as encounters based on the entry complaint (journal entry type Subjective). If multiple entry complaints have been discussed based during a single encounter, these are regarded as partial encounters.

	The expectation of each ~~EncounterReport~~ (Composition) is that it combines the journal entries that constitute a partial encounter. If there is just one issue discussed during the encounter, there is only one ~~EncounterReport~~. If there is more than one partial contact, there could be multiple ~~EncounterReports~~ pointing to the same encounter.		The expectation of each encounter report (Composition) is that it combines the journal entries that constitute a partial encounter. If there is just one issue discussed during the encounter, there is only one encounter report. If there is more than one partial contact, there could be multiple encounter reports pointing to the same encounter.

	Note that while FHIR supports ~~Encounters~~ being part of other ~~Encounters~~, this does not reflect how GP systems are organized. Encounter parts do not not have individual properties to manage and act as a kind of virtual compartment within the ~~Encounter~~.}}		Note that while FHIR supports Encounter resources being part of other Encounter resources, this does not reflect how GP systems are organized. Encounter parts do not not have individual properties to manage and act as a kind of virtual compartment within the encounter.}}
	\|-		\|-
	\| style="background-color: white;vertical-align:top;"\| 13		\| style="background-color: white;vertical-align:top;"\| 13
Regel 255:		Regel 255:
	==List of profiles==		==List of profiles==
	The profiles represent their entire respective HCIM, to make them applicable in a broader context than the exchange of GP Patient Data or a MedMij context. An example for reuse of existing profiles are those of the patient administration resources and vital signs.		The profiles represent their entire respective HCIM, to make them applicable in a broader context than the exchange of GP Patient Data or a MedMij context. An example for reuse of existing profiles are those of the patient administration resources and vital signs.

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

	{\| class="wikitable collapsible" cellpadding="10"		{\| class="wikitable collapsible" cellpadding="10"
	! style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:center; border: 1px solid black;" colspan="6" \| Bijlage 1 Richtlijn Online inzage in het H-EPD door patiënt		! style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:center; border: 1px solid black;" colspan="6" \| Bijlage 1 Richtlijn Online inzage in het H-EPD door patiënt
Regel 348:		Regel 346:
	\| {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/gp-Encounter\|nictiz.fhir.nl.stu3.zib2017}}		\| {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/gp-Encounter\|nictiz.fhir.nl.stu3.zib2017}}
	\|}		\|}
			===Referencing encounters and episodes===
			During early testing of the published information standard, an omission was found. Any journal entry or other activity, and in some cases medication agreement and diagnostic results is associated with an encounter (Encounter resource in FHIR), but an additional association with one or more episodes (EpisodeOfCare in FHIR) is also normal GP practice. However, it is not possible to do this natively in the currently used FHIR version STU3: many resources define the element {{fhir\|.context}} (Encounter <nowiki>\|</nowiki> EpisodeOfCare), but restricts its cardinality to 0..1, meaning that a resource can be connected to either an Encounter or EpisodeOfCare resource, but not both.

			The recommendation is to use {{fhir\|.context}} for associating the Encounter, not the EpisodeOfCare. This approach aligns with the changes in FHIR version R4, where the {{fhir\|.context}} element is replaced by {{fhir\|.encounter}} to support just a reference to an Encounter resource. EpisodeOfCare resource can be referenced through a new extension published in the spring of 2021 (package 2.1.1): {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/extension-context-nl-core-episodeofcare\|nictiz.fhir.nl.stu3.zib2017}}.

			Compatibility note: systems that went in production before this new extension was published will not be able to interpret it, unless they update for it. These systems will ignore the extension and read - as specified - the {{fhir\|.context}} which is normally claimed by a reference to Encounter. Updated and newer systems may now anticipate episode associations on journal entries, diagnostic results, medication agreements and potential other encounter activities, as applicable. For more details, please see [https://bits.nictiz.nl/browse/MM-1521 issue MM-1521].

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

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

2021-03-22T09:17:50Z

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

← Oudere versie		Versie van 22 mrt 2021 09:17
Regel 256:		Regel 256:
	The profiles represent their entire respective HCIM, to make them applicable in a broader context than the exchange of GP Patient Data or a MedMij context. An example for reuse of existing profiles are those of the patient administration resources and vital signs.		The profiles represent their entire respective HCIM, to make them applicable in a broader context than the exchange of GP Patient Data or a MedMij context. An example for reuse of existing profiles are those of the patient administration resources and vital signs.

	{{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 collapsible" cellpadding="10"		{\| class="wikitable collapsible" cellpadding="10"

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

2020-12-01T12:51:01Z

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

← Oudere versie		Versie van 1 dec 2020 12:51
Regel 1:		Regel 1:
	__NUMBEREDHEADINGS__		__NUMBEREDHEADINGS__
	{{DISPLAYTITLE:MedMij FHIR Implementation Guide GP Patient Data {{VersieInfo\|Huisartsgegevens}}}}		{{DISPLAYTITLE:MedMij FHIR Implementation Guide GP Patient Data {{VersieInfo\|Huisartsgegevens}}}}
	{{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/OntwerpHuisartsgegevens\|Functioneel]]		circle 1013 224 212 [[MedMij:Vprepub-2020.01/OntwerpHuisartsgegevens\|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>
Regel 15:		Regel 15:

	==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]]

	The input document "[[MedMij:Vprepub/OntwerpHuisartsgegevens#richtlijn-huisarts-patient\|Richtlijn online inzage in het H-EPD door patiënt]]" (Dutch) described online access of GP data by patients. The use case evolves around a GP specific Patient Data that consists of 10 sections plus the patient and the healthcare provider (GP). These sections correspond to the "[[MedMij:Vprepub/OntwerpHuisartsgegevens#his-referentiemodel-2016\|HIS referentiemodel Publieksversie 2016]]" (Dutch). ''HIS referentiemodel'' is the GP information system reference model (GP-IS-RM).		The input document "[[MedMij:Vprepub-2020.01/OntwerpHuisartsgegevens#richtlijn-huisarts-patient\|Richtlijn online inzage in het H-EPD door patiënt]]" (Dutch) described online access of GP data by patients. The use case evolves around a GP specific Patient Data that consists of 10 sections plus the patient and the healthcare provider (GP). These sections correspond to the "[[MedMij:Vprepub-2020.01/OntwerpHuisartsgegevens#his-referentiemodel-2016\|HIS referentiemodel Publieksversie 2016]]" (Dutch). ''HIS referentiemodel'' is the GP information system reference model (GP-IS-RM).

	Some but not all sections in the GP Patient Data correspond to Health and Care Information Models ([https://zibs.nl/wiki/HCIM_Mainpage HCIMs] (English) or [https://zibs.nl/wiki/ZIB_Hoofdpagina zibs] (Dutch)). A joint initiative project between [http://www.nictiz.nl Nictiz] and the Dutch GP association [https://www.nhg.org NHG] is underway to analyse the relationship between the GP-IS-RM and the HCIMs and propose updates where needed. This analysis will not yield results before 2019. This specification thus predates the analysis, and will updated accordingly moving forward.		Some but not all sections in the GP Patient Data correspond to Health and Care Information Models ([https://zibs.nl/wiki/HCIM_Mainpage HCIMs] (English) or [https://zibs.nl/wiki/ZIB_Hoofdpagina zibs] (Dutch)). A joint initiative project between [http://www.nictiz.nl Nictiz] and the Dutch GP association [https://www.nhg.org NHG] is underway to analyse the relationship between the GP-IS-RM and the HCIMs and propose updates where needed. This analysis will not yield results before 2019. This specification thus predates the analysis, and will updated accordingly moving forward.
Regel 23:		Regel 23:
	This page will elaborate further on the HL7 FHIR details needed to exchange the GP Patient Data information using FHIR.		This page will elaborate further on the HL7 FHIR details needed to exchange the GP Patient Data information using FHIR.

	'''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]].

	==Actors involved==		==Actors involved==
Regel 74:		Regel 74:
	! style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:10px"\| HCIM EN		! style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:10px"\| HCIM EN
	! style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:10px"\| Content		! style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:10px"\| Content
	! style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:10px"\| Search URL<ref>See [[MedMij:Vprepub/FHIR_IG#Search_URLs_and_search_parameters\|Search URLs and search parameters]] for the interpretation of these search URLs</ref>		! style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:10px"\| Search URL<ref>See [[MedMij:Vprepub-2020.01/FHIR_IG#Search_URLs_and_search_parameters\|Search URLs and search parameters]] for the interpretation of these search URLs</ref>
	\|-		\|-
	\| style="background-color: white;vertical-align:top;"\| 1		\| style="background-color: white;vertical-align:top;"\| 1
Regel 138:		Regel 138:
	\| style="background-color: white;vertical-align:top;" rowspan="9"\| Diagnostic and lab results		\| style="background-color: white;vertical-align:top;" rowspan="9"\| Diagnostic and lab results
	\| style="background-color: white;vertical-align:top;"\| [https://zibs.nl/wiki/LaboratoryTestResult-v4.0(2017EN) LaboratoryTestResult v4.0 (2017)]		\| style="background-color: white;vertical-align:top;"\| [https://zibs.nl/wiki/LaboratoryTestResult-v4.0(2017EN) LaboratoryTestResult v4.0 (2017)]
	\| style="background-color: white;vertical-align:top;" rowspan="9"\|A lab test is an objectifiable diagnostic procedure. The result is the outcome of the procedure. Lab tests include vital signs like blood pressure, weight and lab results like ferro in blood.<br/><br/>Note that GP (lab) results are normally coded using [https://referentiemodel.nhg.org/tabellen/nhg-tabel-45-diagnostische-bepalingen NHG Tabel 45]. While some of these codes might be convertible to LOINC or SNOMED CT, this is '''not''' expected at present. Bridging code systems between primary and secondary care is part of a larger national discussion<br/><br/>Note that the date parameter is optional and needs calculation, e.g. current-date() - 14 months. The business rules in the [[MedMij:Vprepub/OntwerpHuisartsgegevens#richtlijn-huisarts-patient\|guide lines]] determine the maximum range for the returned results. If the date parameter is omitted, the maximum range is assumed		\| style="background-color: white;vertical-align:top;" rowspan="9"\|A lab test is an objectifiable diagnostic procedure. The result is the outcome of the procedure. Lab tests include vital signs like blood pressure, weight and lab results like ferro in blood.<br/><br/>Note that GP (lab) results are normally coded using [https://referentiemodel.nhg.org/tabellen/nhg-tabel-45-diagnostische-bepalingen NHG Tabel 45]. While some of these codes might be convertible to LOINC or SNOMED CT, this is '''not''' expected at present. Bridging code systems between primary and secondary care is part of a larger national discussion<br/><br/>Note that the date parameter is optional and needs calculation, e.g. current-date() - 14 months. The business rules in the [[MedMij:Vprepub-2020.01/OntwerpHuisartsgegevens#richtlijn-huisarts-patient\|guide lines]] determine the maximum range for the returned results. If the date parameter is omitted, the maximum range is assumed
	\| style="background-color: white;" rowspan="9"\| <pre>GET [base]/Observation?code=https://referentiemodel.nhg.org/tabellen/nhg-tabel-45-diagnostische-bepalingen\|&_include=Observation:related-target&_include=Observation:specimen&date=ge2017-01-01</pre>		\| style="background-color: white;" rowspan="9"\| <pre>GET [base]/Observation?code=https://referentiemodel.nhg.org/tabellen/nhg-tabel-45-diagnostische-bepalingen\|&_include=Observation:related-target&_include=Observation:specimen&date=ge2017-01-01</pre>
	\|-		\|-
Regel 256:		Regel 256:
	The profiles represent their entire respective HCIM, to make them applicable in a broader context than the exchange of GP Patient Data or a MedMij context. An example for reuse of existing profiles are those of the patient administration resources and vital signs.		The profiles represent their entire respective HCIM, to make them applicable in a broader context than the exchange of GP Patient Data or a MedMij context. An example for reuse of existing profiles are those of the patient administration resources and vital signs.

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

	{\| class="wikitable collapsible" cellpadding="10"		{\| class="wikitable collapsible" cellpadding="10"
Regel 350:		Regel 350:

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

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

2020-12-01T12:49:24Z

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

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

Pieter Edelman: HOTFIX: Remove unnecessary parameter "release" from VersieInfo template

2020-11-25T08:15:16Z

HOTFIX: Remove unnecessary parameter "release" from VersieInfo template

← Oudere versie		Versie van 25 nov 2020 08:15
Regel 1:		Regel 1:
	__NUMBEREDHEADINGS__		__NUMBEREDHEADINGS__
	{{DISPLAYTITLE:MedMij FHIR Implementation Guide GP Patient Data {{VersieInfo\|Huisartsgegevens~~\|release=Vprepub~~}}}}		{{DISPLAYTITLE:MedMij FHIR Implementation Guide GP Patient Data {{VersieInfo\|Huisartsgegevens}}}}
	{{MedMij:Vprepub/Issuebox_FHIR_IG}}		{{MedMij:Vprepub/Issuebox_FHIR_IG}}

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

2020-11-20T13:15:05Z

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

← Oudere versie		Versie van 20 nov 2020 13:15
Regel 256:		Regel 256:
	The profiles represent their entire respective HCIM, to make them applicable in a broader context than the exchange of GP Patient Data or a MedMij context. An example for reuse of existing profiles are those of the patient administration resources and vital signs.		The profiles represent their entire respective HCIM, to make them applicable in a broader context than the exchange of GP Patient Data or a MedMij context. An example for reuse of existing profiles are those of the patient administration resources and vital signs.

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

	{\| class="wikitable collapsible" cellpadding="10"		{\| class="wikitable collapsible" cellpadding="10"

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

2020-11-13T15:38: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:38
Regel 256:		Regel 256:
	The profiles represent their entire respective HCIM, to make them applicable in a broader context than the exchange of GP Patient Data or a MedMij context. An example for reuse of existing profiles are those of the patient administration resources and vital signs.		The profiles represent their entire respective HCIM, to make them applicable in a broader context than the exchange of GP Patient Data or a MedMij context. An example for reuse of existing profiles are those of the patient administration resources and vital signs.

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

	{\| class="wikitable collapsible" cellpadding="10"		{\| class="wikitable collapsible" cellpadding="10"
Regel 348:		Regel 348:
	\| {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/gp-Encounter\|nictiz.fhir.nl.stu3.zib2017}}		\| {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/gp-Encounter\|nictiz.fhir.nl.stu3.zib2017}}
	\|}		\|}
	~~{{Sjabloon:Voorbeelden}}~~

	~~==Terminology, NamingSystems, Mappings==~~
	~~{{MedMij:Vissue-MM-1386/Template_Terminologies_NamingSystems_Mappings}}~~

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

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

2020-10-21T10:07:33Z

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

← Oudere versie		Versie van 21 okt 2020 10:07
Regel 351:		Regel 351:

	==Terminology, NamingSystems, Mappings==		==Terminology, NamingSystems, Mappings==
			{{MedMij:Vissue-MM-1386/Template_Terminologies_NamingSystems_Mappings}}
	~~===Terminology===~~
	~~Relevant value sets can be found [https~~://simplifier.net/NictizSTU3-Zib2017/~resources?category=ValueSet here]. All resources can be downloaded in a .zip in XML or JSON format. In the .zip, the value sets are stored in the directory 'value sets'.

	~~===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/OntwerpHuisartsgegevens#Release_notes\| functional design page]].		Release notes can be found on the [[MedMij:Vprepub/OntwerpHuisartsgegevens#Release_notes\| functional design page]].

Pieter Edelman: MM-1011: Replace the generic term "StructureDefinitions" with the more specfic term "profiles"

2020-09-21T08:07:32Z

MM-1011: Replace the generic term "StructureDefinitions" with the more specfic term "profiles"

← Oudere versie		Versie van 21 sep 2020 08:07
Regel 65:		Regel 65:
	<code>GET [base]/[type]{?[parameters]}</code>		<code>GET [base]/[type]{?[parameters]}</code>

	The table below shows in the first four columns the GP Patient Data sections, the GP-IS-RM sections / HCIMs that constitute those sections and the specific content of the GP Patient Data. The last column shows the FHIR search queries to obtain the GP Patient Data information. These queries are based on ~~StructureDefinitions~~ listed in [[#~~List_of_StructureDefinitions~~\| this section]]. As noted in the [[#Introduction\|introduction]], the associated HCIMs are ahead of a separate joint initiative project that aims to analyse and harmonize this further.		The table below shows in the first four columns the GP Patient Data sections, the GP-IS-RM sections / HCIMs that constitute those sections and the specific content of the GP Patient Data. The last column shows the FHIR search queries to obtain the GP Patient Data information. These queries are based on profiles listed in [[#List_of_profiles\|this section]]. As noted in the [[#Introduction\|introduction]], the associated HCIMs are ahead of a separate joint initiative project that aims to analyse and harmonize this further.

	{\| class="wikitable collapsible" cellpadding="10"		{\| class="wikitable collapsible" cellpadding="10"
Regel 179:		Regel 179:

	===Server - XIS===		===Server - XIS===
	The returned data to the PHR should conform to the profiles listed in [[#~~List_of_StructureDefinitions~~]].		The returned data to the PHR should conform to the profiles listed in [[#List_of_profiles]].

	===Custom search parameters===		===Custom search parameters===
Regel 253:		Regel 253:
	<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 + 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.

	==List of ~~StructureDefinitions~~==		==List of profiles==
	The profiles represent their entire respective HCIM, to make them applicable in a broader context than the exchange of GP Patient Data or a MedMij context. An example for reuse of existing profiles are those of the patient administration resources and vital signs.		The profiles represent their entire respective HCIM, to make them applicable in a broader context than the exchange of GP Patient Data or a MedMij context. An example for reuse of existing profiles are those of the patient administration resources and vital signs.

← Oudere versie		Versie van 21 jun 2021 08:03
Regel 120:		Regel 120:
	\| style="vertical-align:top;"\|Current medication		\| style="vertical-align:top;"\|Current medication
	\| style="vertical-align:top;"\|[https://zibs.nl/wiki/MedicationAgreement-v1.0(2017EN) MedicationAgreement v1.0 (2017)]		\| style="vertical-align:top;"\|[https://zibs.nl/wiki/MedicationAgreement-v1.0(2017EN) MedicationAgreement v1.0 (2017)]
	\| style="vertical-align:top;"\|MedicationAgreement <br/>The prescriber proposed use of medication that the patient agrees with. The agreement may signal starting, repeating, updating or stopping the medication. The list of MedicationAgreements is also known as the list of medication the patient is '''currently''' using. Note that ~~current~~ means that the period of use is still active. This is conveyed in the MedicationRequest.extension periodOfUse. This may or may not me populated. If it is not, the Medicationagreement is assumed to be current. The search parameter {{Simplifier\|http://nictiz.nl/fhir/SearchParameter/Medications-periodofuse\|nictiz.fhir.nl.stu3.zib2017\|title=periodofuse}} allows filtering for current ~~medicationagreements~~		\| style="vertical-align:top;"\|MedicationAgreement <br/>The prescriber proposed use of medication that the patient agrees with. The agreement may signal starting, repeating, updating or stopping the medication. The list of MedicationAgreements is also known as the list of medication the patient is '''currently''' using. Note that "currently" means that the period of use is still active. This is conveyed in the MedicationRequest extension {{fhir\|periodOfUse}}. This extension may or may not be populated. If it is not, the Medicationagreement is assumed to be current. The search parameter {{Simplifier\|http://nictiz.nl/fhir/SearchParameter/Medications-periodofuse\|nictiz.fhir.nl.stu3.zib2017\|title=periodofuse}} allows filtering for current MedicationAgreements.
	\| style="vertical-align:top;"\|<pre>GET [base]/MedicationRequest?periodofuse=ge[today]&category=http://snomed.info/sct\|16076005&_include=MedicationRequest:medication</pre>		\| style="vertical-align:top;"\|<pre>GET [base]/MedicationRequest?periodofuse=ge[today]&category=http://snomed.info/sct\|16076005&_include=MedicationRequest:medication</pre>
	\|-		\|-