MedMij:Vpoc 1.0/FHIR iWlz - Bewerkingsoverzicht

Jorn Duwel: /* Send transaction Bundle */

2022-11-09T10:29:54Z

‎Send transaction Bundle

Jorn Duwel: v1.0-poc8

2022-11-04T16:07:44Z

v1.0-poc8

Jorn Duwel op 2 nov 2022 om 08:36

2022-11-02T08:36:22Z

Jorn Duwel op 2 nov 2022 om 08:36

2022-11-02T08:36:09Z

Jorn Duwel: v1.0-poc5a

2022-01-31T16:17:46Z

v1.0-poc5a

Jorn Duwel: v1.0-poc5a

2022-01-31T16:17:31Z

v1.0-poc5a

Jorn Duwel: v1.0-poc5

2022-01-10T16:36:19Z

v1.0-poc5

Jorn Duwel: v1.0-poc4

2021-12-24T11:09:27Z

v1.0-poc4

Jorn Duwel: Fix FO link

2021-12-24T10:57:08Z

Fix FO link

Jorn Duwel: Up package version to poc3

2021-12-24T10:56:36Z

Up package version to poc3

@@ Regel 157: / Regel 157: @@
 In this transaction Bundle, both the Patient resource and the QuestionnaireResponse have an {{fhir|entry.request.method}} of 'POST' ({{fhir|create}} interaction).
-''Note:'' because the PHR's client can only edit several parts of the resource, the {{fhir|create}} interaction does not force the server to accept the entire resource as is. For example, the updated content may be reviewed before merging it with the exisitng information. Performing a {{fhir|read}} interaction on the Patient resource shortly after 'PUT'ting an edited version may therefore lead to unexpected results. See the [https://www.hl7.org/fhir/stu3/http.html#transactional-integrity FHIR specification on transactional integrity] for more discussion. However, it is the responsibility of the server to maintain only one version of the Patient resource.
+''Note:'' because the PHR's client can only edit several parts of the resource, the {{fhir|create}} interaction does not force the server to accept the entire resource as is. For example, the updated content may be reviewed before merging it with the exisitng information. Performing a {{fhir|read}} interaction on the Patient resource shortly after 'POST'ting an edited version may therefore lead to unexpected results. See the [https://www.hl7.org/fhir/stu3/http.html#transactional-integrity FHIR specification on transactional integrity] for more discussion. However, it is the responsibility of the server to maintain only one version of the Patient resource.
 Because of the static nature of the iwlz-Clientvoorkeuren-Questionnaire within this PoC, see also [[MedMij:Vprepub-poc_1.0/FHIR_iWlz#Use_of_Questionnaire_and_QuestionnaireResponse_profiles|this paragraph]], there is no explicit connection between the QuestionnaireResponse and the Questionnaire resources using the {{fhir|QuestionnaireResponse.questionnaire}} element. The PHR can use any preferred method to compose the QuestionnaireResponse resource, as long as it conforms to the profile. For each {{fhir|QuestionnaireResponse.item}}, the PHR SHOULD fill the {{fhir|.item.text}} element with the exact text that is used during user input.

@@ Regel 1: / Regel 1: @@
 __NUMBEREDHEADINGS__
 __NOINDEX__
-{{DISPLAYTITLE:MedMij FHIR Implementation Guide: iWlz 1.0 Proof of concept (1.0-poc7) {{Sjabloon:VersieInfo|iWlz}}}}
+{{DISPLAYTITLE:MedMij FHIR Implementation Guide: iWlz 1.0 Proof of concept (1.0-poc8) {{Sjabloon:VersieInfo|iWlz}}}}
 {{NoteBox|This version will be tested in a proof of concept and should not be used outside this POC}}
@@ Regel 78: / Regel 78: @@
 The data returned to the PHR should conform the profiles listed in the table below and (if applicable) their associated HCIMs. The resources in the response message SHALL be a valid instance of these profiles.
-{{MedMij:V2020.01/NoteBoxPackage|p1=nictiz.fhir.nl.stu3.zib2017|v1Min=2.0.0|p2=nictiz.fhir.nl.stu3.iwlz|v2=1.0.0-poc7}}
+{{MedMij:V2020.01/NoteBoxPackage|p1=nictiz.fhir.nl.stu3.zib2017|v1Min=2.0.0|p2=nictiz.fhir.nl.stu3.iwlz|v2=1.0.0-poc8}}
 {| class="wikitable"
@@ Regel 143: / Regel 143: @@
 The following custom operation is used: {{Simplifier|http://nictiz.nl/fhir/OperationDefinition/iwlz-Indicaties|nictiz.fhir.nl.stu3.zib2017}}.
-=Use case: send client preferences=
+=Use case: send client profile=
 This use case applies when a client qualifies for receiving long term care based on the WLZ and the client wants to share his preferences, contact information and contact persons.
-The client preferences are based on a iwlz-Clientvoorkeuren-Questionnaire resource to be filled by the client, leading to an iwlz-Clientvoorkeuren-QuestionnaireResponse resource. The contact information and contact persons filled in or edited by the client lead to an edited iwl-Persoon Patient resource. The Patient resource that can be edited should be retrieved from the Composition document Bundle that was received during the previous use case.
+The client preferences are based on a iwlz-Clientvoorkeuren-Questionnaire resource to be filled by the client, leading to an iwlz-Clientvoorkeuren-QuestionnaireResponse resource. The contact information and contact persons filled in or edited by the client lead to an edited iwl-Persoon Patient resource.
 ==Send transaction Bundle==
@@ Regel 155: / Regel 155: @@
 </pre>
-In this transaction Bundle, the Patient resource has an {{fhir|entry.request.method}} of 'PUT' ({{fhir|update}} interaction), the QuestionnaireResponse has a {{fhir|method}} of 'POST' ({{fhir|create}} interaction).
+In this transaction Bundle, both the Patient resource and the QuestionnaireResponse have an {{fhir|entry.request.method}} of 'POST' ({{fhir|create}} interaction).
-''Note:'' because the PHR's client can only edit several parts of the resource, the {{fhir|update}} interaction does not force the server to accept the entire resource as is. For example, the updated content may be reviewed before merging it with the exisitng information. Performing a {{fhir|read}} interaction on the Patient resource shortly after 'PUT'ting an edited version may therefore lead to unexpected results. See the [https://www.hl7.org/fhir/stu3/http.html#transactional-integrity FHIR specification on transactional integrity] for more discussion. However, it is the responsibility of the server to maintain only one version of the Patient resource.
+''Note:'' because the PHR's client can only edit several parts of the resource, the {{fhir|create}} interaction does not force the server to accept the entire resource as is. For example, the updated content may be reviewed before merging it with the exisitng information. Performing a {{fhir|read}} interaction on the Patient resource shortly after 'PUT'ting an edited version may therefore lead to unexpected results. See the [https://www.hl7.org/fhir/stu3/http.html#transactional-integrity FHIR specification on transactional integrity] for more discussion. However, it is the responsibility of the server to maintain only one version of the Patient resource.
 The PHR shall guarantee consistency of all FHIR resource elements with the profiles listed in the table below and (if applicable) their associated HCIMs. The resources in the request message SHALL be a valid instance of these profiles.
-{{MedMij:V2020.01/NoteBoxPackage|p1=nictiz.fhir.nl.stu3.zib2017|v1Min=2.0.0|p2=nictiz.fhir.nl.stu3.iwlz|v2=1.0.0-poc7}}
+{{MedMij:V2020.01/NoteBoxPackage|p1=nictiz.fhir.nl.stu3.zib2017|v1Min=2.0.0|p2=nictiz.fhir.nl.stu3.iwlz|v2=1.0.0-poc8}}
 {| class="wikitable"

@@ Regel 2: / Regel 2: @@
 __NOINDEX__
 {{DISPLAYTITLE:MedMij FHIR Implementation Guide: iWlz 1.0 Proof of concept (1.0-poc7) {{Sjabloon:VersieInfo|iWlz}}}}
 {{NoteBox|This version will be tested in a proof of concept and should not be used outside this POC}}

@@ Regel 1: / Regel 1: @@
 __NUMBEREDHEADINGS__
 __NOINDEX__
-{{DISPLAYTITLE:MedMij FHIR Implementation Guide: iWlz 1.0 Proof of concept (1.0-poc5a) {{Sjabloon:VersieInfo|iWlz}}}}
+{{DISPLAYTITLE:MedMij FHIR Implementation Guide: iWlz 1.0 Proof of concept (1.0-poc7) {{Sjabloon:VersieInfo|iWlz}}}}
 {{NoteBox|This version will be tested in a proof of concept and should not be used outside this POC}}
@@ Regel 67: / Regel 68: @@
 The 'indicatiegegevens' are built up of individual FHIR resources, selected by the user of the XIS to form a coherent set of information relevant to the client. The Composition resource assembles the references to all individual related FHIR resources. For this purpose, the Composition profile described in [[#FHIR profiles|FHIR profiles]] SHALL be used.
-Retrieving all 'indicatiegegevens' is a two-step process. Firstly, the available Composition resources are retrieved. For each Composition, the {{fhir|Composition.id}} is used for the second step in which all related information is retrieved.
+The PHR can retrieve all available Composition resources ''and'' all referenced resources as a single searchset Bundle by using the following {{Simplifier|http://nictiz.nl/fhir/OperationDefinition/iwlz-Indicaties|nictiz.fhir.nl.stu3.iwlz|title=custom operation}}<ref>Originally, this was a two step process using the FHIR core {{fhir|$document}} operation. However, this use case does not match the intended use of this operation. Discussions are ongoing on the introduction of a new operation in a future version of FHIR to be able to search and retrieve document Compositions simultaneously, see {{Simplifier|http://nictiz.nl/fhir/OperationDefinition/iwlz-Indicaties|nictiz.fhir.nl.stu3.iwlz|title=the OperationDefinition}} for more information.</ref>:
-The first step can be omitted, if a different mechanism to transfer the {{fhir|Composition.id}} to the PHR is implemented.
+The result is a searchset Bundle with all Compositions available ''and'' all referenced resources. ''Note:'' the Composition lists just the resources that act as entry points for the various concepts in the transaction, but each of these referenced resources may further refer to other resources not listed there. The server SHALL produce a complete Bundle containing not only the resources listed directly in the Composition, but all the indirectly referenced resources as well.
-==Retrieve all Composition resources==
+The Compositions returned can be sorted and/or presented to the user by the PHR based on {{fhir|Composition.event.period}} to determine active and/or the most recent 'indicatie'.
-<pre>GET [base]/Composition?type=http://snomed.info/sct|304784009</pre>
+Because each Composition resource and the resources it references are a set of coherent resources that are a representation of the 'indicatie' and that cannot be interpreted individually, XIS Servers are not expected to support resolving the individual resources of the Composition document Bundle by their {{fhir|fullUrl}}. PHR systems should only use the document operation to retrieve the 'indicatie' in full.
 The data returned to the PHR should conform the profiles listed in the table below and (if applicable) their associated HCIMs. The resources in the response message SHALL be a valid instance of these profiles.
-{{MedMij:V2020.01/NoteBoxPackage|p1=nictiz.fhir.nl.stu3.zib2017|v1Min=2.0.0|p2=nictiz.fhir.nl.stu3.iwlz|v2=1.0.0-poc5}}
+{{MedMij:V2020.01/NoteBoxPackage|p1=nictiz.fhir.nl.stu3.zib2017|v1Min=2.0.0|p2=nictiz.fhir.nl.stu3.iwlz|v2=1.0.0-poc7}}
 {| class="wikitable"
@@ Regel 146: / Regel 140: @@
 | {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017}}
 |}
 =Use case: send client preferences=
@@ Regel 165: / Regel 162: @@
 The PHR shall guarantee consistency of all FHIR resource elements with the profiles listed in the table below and (if applicable) their associated HCIMs. The resources in the request message SHALL be a valid instance of these profiles.
-{{MedMij:V2020.01/NoteBoxPackage|p1=nictiz.fhir.nl.stu3.zib2017|v1Min=2.0.0|p2=nictiz.fhir.nl.stu3.iwlz|v2=1.0.0-poc5}}
+{{MedMij:V2020.01/NoteBoxPackage|p1=nictiz.fhir.nl.stu3.zib2017|v1Min=2.0.0|p2=nictiz.fhir.nl.stu3.iwlz|v2=1.0.0-poc7}}
 {| class="wikitable"

@@ Regel 1: / Regel 1: @@
 __NUMBEREDHEADINGS__
 __NOINDEX__
-{{DISPLAYTITLE:MedMij FHIR Implementation Guide: iWlz 1.0 Proof of concept (1.0-poc5) {{Sjabloon:VersieInfo|iWlz}}}}
+{{DISPLAYTITLE:MedMij FHIR Implementation Guide: iWlz 1.0 Proof of concept (1.0-poc5a) {{Sjabloon:VersieInfo|iWlz}}}}
 {{NoteBox|This version will be tested in a proof of concept and should not be used outside this POC}}

@@ Regel 76: / Regel 76: @@
 <pre>GET [base]/Composition?type=http://snomed.info/sct|304784009</pre>
-The result is a searchset Bundle with all Compositions available. In most cases, only one Composition resource is available, but otherwise the Compositions can be sorted based on {{fhir|Composition.event.period}}).
+The result is a searchset Bundle with all Compositions available. In contrary to [https://informatiestandaarden.nictiz.nl/wiki/MedMij:V2020.01/FHIR_IG#Including_referenced_resources paragraph 5.7.2.1 of the MedMij IG], referenced resources are not expected to be included at this point. In most cases, only one Composition resource is available, but otherwise the Compositions can be sorted based on {{fhir|Composition.event.period}}).
 ==Retrieve selected Composition document Bundle==
 For each Composition retrieved during the preceding step, the PHR uses the {{fhir|Composition.id}} and the [http://hl7.org/fhir/stu3/composition-operations.html#document {{fhir|$document}} operation] to retrieve both the Composition ''and'' all referenced resources as a single document Bundle.<br/> <pre>GET [base]/Composition/[id]/$document</pre> ''Note:'' the Composition lists just the resources that act as entry points for the various concepts in the transaction, but each of these referenced resources may further refer to other resources not listed there. The server SHALL produce a complete Bundle containing not only the resources listed directly in the Composition, but all the indirectly referenced resources as well.
 The data returned to the PHR should conform the profiles listed in the table below and (if applicable) their associated HCIMs. The resources in the response message SHALL be a valid instance of these profiles.

@@ Regel 7: / Regel 7: @@
 <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 1013 224 212 [[MedMij:Vprepub-poc_1.0/OntwerpiWlz|Functioneel]]
+circle 1013 224 212 [[MedMij:Vpoc_1.0/OntwerpiWlz|Functioneel]]
 circle 1787 230 212 [[MedMij:V2020.01/FHIR_IG|Technisch]]
 desc none

@@ Regel 83: / Regel 83: @@
 The data returned to the PHR should conform the profiles listed in the table below and (if applicable) their associated HCIMs. The resources in the response message SHALL be a valid instance of these profiles.
-{{MedMij:V2020.01/NoteBoxPackage|p1=nictiz.fhir.nl.stu3.zib2017|v1Min=2.0.0|p2=nictiz.fhir.nl.stu3.iwlz|v2=1.0.0-poc2}}
+{{MedMij:V2020.01/NoteBoxPackage|p1=nictiz.fhir.nl.stu3.zib2017|v1Min=2.0.0|p2=nictiz.fhir.nl.stu3.iwlz|v2=1.0.0-poc3}}
 {| class="wikitable"
@@ Regel 145: / Regel 145: @@
 The PHR shall guarantee consistency of all FHIR resource elements with the profiles listed in the table below and (if applicable) their associated HCIMs. The resources in the request message SHALL be a valid instance of these profiles.
-{{MedMij:V2020.01/NoteBoxPackage|p1=nictiz.fhir.nl.stu3.zib2017|v1Min=2.0.0|p2=nictiz.fhir.nl.stu3.iwlz|v2=1.0.0-poc2}}
+{{MedMij:V2020.01/NoteBoxPackage|p1=nictiz.fhir.nl.stu3.zib2017|v1Min=2.0.0|p2=nictiz.fhir.nl.stu3.iwlz|v2=1.0.0-poc3}}
 {| class="wikitable"