Stream: implementers
Topic: Updating non-reference values in bundle processing
Lee Surprenant (Feb 14 2022 at 16:43):
Originally brought up at https://chat.fhir.org/#narrow/stream/179166-implementers/topic/Allowed.20uri.20schemes.20for.20Bundle.2Eentry.2EfullUrl.20and.20referenc.2E.2E.2E/near/271667102 but I thought this part deserved its own topic.
https://build.fhir.org/http.html#trules says:
Servers SHALL replace all matching links in the bundle, whether they are found in the resource ids, resource references, elements of type uri, url, oid, uuid, and <a href="" & <img src="" in the narrative. Elements of type canonical are not replaced.
I definitely understand the value of replacing literal reference values so that the posted resources can reference one another, but what are the use cases for replacing the value of elements of type uri, url, oid, uuid? Are there base spec resources that refer to other resources with those element types instead of Reference or canonical?
Lee Surprenant (Feb 15 2022 at 12:52):
It would also be nice to have some clarification on "SHALL replace all matching links in the bundle" ...I'm assuming only "complete" matches should be updated and not "partial/contains" ones.
For example, narrative text with an <a href="https://example.com/patient-browser?resource=resource:1"> should NOT be updated if the posted transaction bundle includes a create (POST) of a Patient resource with fullUrl resource:1, correct?
Last updated: Apr 12 2022 at 19:14 UTC
