Stream: fhir-messages
Topic: references
Jeremy Chapman (Feb 11 2021 at 22:00):
If I have a bundle, with a Messageheader in an entry that has a fullUrl of "urn:uuid:ee35a7da-f8a2-475b-bee2-559969b78081", and my MessageHeader.focus.reference is a relative reference of "Patient/123" what should the full url of my Patient resource entry be for it to resolve correctly? and is there a function in the .net library that will resolve it for me?
Vassil Peytchev (Feb 11 2021 at 22:31):
In such a case, my understanding is that the fullUrl must be a RESTful URL, [base]/Patient/123 (which also implies that the resource is available at that URL).
I don't know how the .net library handles this, you may want to ask in thge #dotnet stream.
Jeremy Chapman (Feb 11 2021 at 22:35):
So does that mean that you can't resolve the reference, because the base is urn:uuid:ee35a7da-f8a2-475b-bee2-559969b78081 which is not restful? if the reference is relative, than the fullUrl of the patient resource would need to be urn:uuid:ee35a7da-f8a2-475b-bee2-559969b78081/Patient/123 which is not allowed because it's not restful?
Vassil Peytchev (Feb 11 2021 at 22:42):
No, what I am saying is that if you want to have a relative reference within the bundle, you cannot have a fullUrl that is a URN representing a UUID or OID. The fullUrl in this case must be have a base consisting of http[s]://server/[path/]
It is the combination of http://build.fhir.org/references.html#literal, http://build.fhir.org/http.html#root, and http://build.fhir.org/bundle.html#references
Lloyd McKenzie (Feb 12 2021 at 00:09):
Patient/123 is not a legal reference from a resource with fullUrl urn:uuid:[whatever]. That's because the local reference will get converted to urn:uuid:123. If you're inside a resource that has a uuid fullUrl, all of your references must be either contained references, local references that are uuids or full references (which could be urn:uuid:whatever or http://whatever)
Last updated: Apr 12 2022 at 19:14 UTC
