https://informatiestandaarden.test-nictiz.nl/index.php?action=history&feed=atom&title=FHIR%3AVissue-MM-3839_FHIR_IG_STU3 2026-04-07T10:33:50Z Bewerkingsoverzicht voor deze pagina op de wiki MediaWiki 1.43.0 https://informatiestandaarden.test-nictiz.nl/index.php?title=FHIR:Vissue-MM-3839_FHIR_IG_STU3&diff=146165&oldid=prev 2022-12-02T10:14:56Z

<p><span class="autocomment">Referring other resources when sending information</span></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="nl"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Oudere versie</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Versie van 2 dec 2022 10:14</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l400">Regel 400:</td> <td colspan="2" class="diff-lineno">Regel 400:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* Sending secondary resources SHALL only be done when the information standard specifies that a {{fhir|batch}} or {{fhir|transaction}} operation is to be used.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* Sending secondary resources SHALL only be done when the information standard specifies that a {{fhir|batch}} or {{fhir|transaction}} operation is to be used.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* If so, the client MAY send a bare-bones instance as the secondary resource containing just minimal information, but this SHOULD include the information necessary for the server to match its own copy. The information standard MAY specify which information is minimally needed for such a secondary resource and MAY also restrict the information that is sent in the secondary resource.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* If so, the client MAY send a bare-bones instance as the secondary resource containing just minimal information, but this SHOULD include the information necessary for the server to match its own copy. The information standard MAY specify which information is minimally needed for such a secondary resource and MAY also restrict the information that is sent in the secondary resource.</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>* The client MUST include a {{fhir|Bundle.entry.request}} for each of the resources in the Bundle, including the secondary resources that are only there for referencing purposes. {{fhir|.request}} SHOULD be a &lt;code&gt;POST&lt;/code&gt; to the appropriate endpoint to indicate the {{fhir|create}} operation. As an alternative, the {{fhir|update}} operation MAY be used, but this is strongly discouraged; if the client has knowledge on the id of the resource on the server, an absolute URL is strongly preferred.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>* The client MUST include a {{fhir|Bundle.entry.request}} for each of the resources in the Bundle, including the secondary resources that are only there for referencing purposes<ins style="font-weight: bold; text-decoration: none;">&lt;ref&gt;Although {{fhir|Bundle.entry.request}} is not formally required in FHIR STU3, it is made clear in FHIR R4 that the expected behavior actually is to include it.&lt;/ref&gt;</ins>. {{fhir|.request}} SHOULD be a &lt;code&gt;POST&lt;/code&gt; to the appropriate endpoint to indicate the {{fhir|create}} operation. As an alternative, the {{fhir|update}} operation MAY be used, but this is strongly discouraged; if the client has knowledge on the id of the resource on the server, an absolute URL is strongly preferred.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* If the server can unequivocally de-duplicate this secondary resource (for example, because the patient is already known from the security context or the healthcare provider is recognized by the UZI number), it MAY choose to ignore the differences of this resource or it MAY incorporate them (see the [https://www.hl7.org/fhir/stu3/http.html#transactional-integrity the section on transactional integity] in the FHIR specification). Please note that absence of information should not result in deletion of information on the server, as the client could send a bare-bones instance.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* If the server can unequivocally de-duplicate this secondary resource (for example, because the patient is already known from the security context or the healthcare provider is recognized by the UZI number), it MAY choose to ignore the differences of this resource or it MAY incorporate them (see the [https://www.hl7.org/fhir/stu3/http.html#transactional-integrity the section on transactional integity] in the FHIR specification). Please note that absence of information should not result in deletion of information on the server, as the client could send a bare-bones instance.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>** If a {{fhir|transaction}} operation is used and the server chooses to ignore the differences, it SHOULD do so silently by responding with a 200 OK status code for the corresponding {{fhir|Bundle.entry.response.status}} in the response Bundle.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>** If a {{fhir|transaction}} operation is used and the server chooses to ignore the differences, it SHOULD do so silently by responding with a 200 OK status code for the corresponding {{fhir|Bundle.entry.response.status}} in the response Bundle.</div></td></tr> </table>

Pieter Edelman https://informatiestandaarden.test-nictiz.nl/index.php?title=FHIR:Vissue-MM-3839_FHIR_IG_STU3&diff=146164&oldid=prev 2022-12-02T10:13:05Z

<p><span class="autocomment">Referring other resources when sending information</span></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="nl"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Oudere versie</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Versie van 2 dec 2022 10:13</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l400">Regel 400:</td> <td colspan="2" class="diff-lineno">Regel 400:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* Sending secondary resources SHALL only be done when the information standard specifies that a {{fhir|batch}} or {{fhir|transaction}} operation is to be used.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* Sending secondary resources SHALL only be done when the information standard specifies that a {{fhir|batch}} or {{fhir|transaction}} operation is to be used.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* If so, the client MAY send a bare-bones instance as the secondary resource containing just minimal information, but this SHOULD include the information necessary for the server to match its own copy. The information standard MAY specify which information is minimally needed for such a secondary resource and MAY also restrict the information that is sent in the secondary resource.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* If so, the client MAY send a bare-bones instance as the secondary resource containing just minimal information, but this SHOULD include the information necessary for the server to match its own copy. The information standard MAY specify which information is minimally needed for such a secondary resource and MAY also restrict the information that is sent in the secondary resource.</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>* The client MUST include a {{fhir|Bundle.entry.request}} for each of the resources in the Bundle, including the secondary resources that are only there for referencing purposes<del style="font-weight: bold; text-decoration: none;">&lt;ref&gt;Although {{fhir|Bundle.entry.request}} is not formally required in FHIR STU3, it is made clear in FHIR R4 that the expected behavior actually is to include it.&lt;/ref&gt;</del>. {{fhir|.request}} SHOULD be a &lt;code&gt;POST&lt;/code&gt; to the appropriate endpoint. As an alternative, <del style="font-weight: bold; text-decoration: none;">&lt;code&gt;PUT&lt;/code&gt; </del>MAY be used, but is strongly discouraged; if the client has knowledge on the id of the resource on the server, an absolute URL is strongly preferred.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>* The client MUST include a {{fhir|Bundle.entry.request}} for each of the resources in the Bundle, including the secondary resources that are only there for referencing purposes. {{fhir|.request}} SHOULD be a &lt;code&gt;POST&lt;/code&gt; to the appropriate endpoint <ins style="font-weight: bold; text-decoration: none;">to indicate the {{fhir|create}} operation</ins>. As an alternative, <ins style="font-weight: bold; text-decoration: none;">the {{fhir|update}} operation </ins>MAY be used, but <ins style="font-weight: bold; text-decoration: none;">this </ins>is strongly discouraged; if the client has knowledge on the id of the resource on the server, an absolute URL is strongly preferred.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* If the server can unequivocally de-duplicate this secondary resource (for example, because the patient is already known from the security context or the healthcare provider is recognized by the UZI number), it MAY choose to ignore the differences of this resource or it MAY incorporate them (see the [https://www.hl7.org/fhir/stu3/http.html#transactional-integrity the section on transactional integity] in the FHIR specification). Please note that absence of information should not result in deletion of information on the server, as the client could send a bare-bones instance.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* If the server can unequivocally de-duplicate this secondary resource (for example, because the patient is already known from the security context or the healthcare provider is recognized by the UZI number), it MAY choose to ignore the differences of this resource or it MAY incorporate them (see the [https://www.hl7.org/fhir/stu3/http.html#transactional-integrity the section on transactional integity] in the FHIR specification). Please note that absence of information should not result in deletion of information on the server, as the client could send a bare-bones instance.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>** If a {{fhir|transaction}} operation is used and the server chooses to ignore the differences, it SHOULD do so silently by responding with a 200 OK status code for the corresponding {{fhir|Bundle.entry.response.status}} in the response Bundle.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>** If a {{fhir|transaction}} operation is used and the server chooses to ignore the differences, it SHOULD do so silently by responding with a 200 OK status code for the corresponding {{fhir|Bundle.entry.response.status}} in the response Bundle.</div></td></tr> </table>

Pieter Edelman https://informatiestandaarden.test-nictiz.nl/index.php?title=FHIR:Vissue-MM-3839_FHIR_IG_STU3&diff=146163&oldid=prev 2022-12-02T10:12:27Z

<p>Clone of V1.0 production page for issue MM-3839</p> <a href="https://informatiestandaarden.test-nictiz.nl/index.php?title=FHIR:Vissue-MM-3839_FHIR_IG_STU3&amp;diff=146163">Wijzigingen bekijken</a>

Pieter Edelman