Stream: implementers
Topic: Fake URLs in Bundle.entry.fullUrl
Rick Geimer (Feb 22 2021 at 19:58):
Wanted to start a discussion about using fake URLs such as http://example.org/not-a-real-fhir-server as the FHIR base URL in Bundle.entry.fullUrl. This came up while discussing https://jira.hl7.org/browse/FHIR-29319 and https://jira.hl7.org/browse/FHIR-29271, to allow relative URLs with version info, where (I think) having a UUID URI would not work.
Lloyd McKenzie (Feb 22 2021 at 19:59):
That wouldn't be conformant, I don't think
Lloyd McKenzie (Feb 22 2021 at 19:59):
If you're specifying a URL, then it's expected to actually be a URL.
Lloyd McKenzie (Feb 22 2021 at 19:59):
Why couldn't a UUID work?
Rick Geimer (Feb 22 2021 at 20:00):
This was the example we discussed in FHIR-I when the topic came up:
http://example.org/not-a-fhir-server/Patient/guid-here/_history/1
Rick Geimer (Feb 22 2021 at 20:01):
I don't think we could use urn:uuid:guid-here/_history/1 for fullUrl, right?
Vassil Peytchev (Feb 22 2021 at 22:06):
Why is adding an extension not good enough?
Lloyd McKenzie (Feb 23 2021 at 00:47):
Fake URL was a proposal, but it's not a great idea - it's technically non-conformant
Gino Canessa (Feb 23 2021 at 16:33):
Rick Geimer said:
I don't think we could use urn:uuid:guid-here/_history/1 for fullUrl, right?
This is correct - appending segments to urn:uuid is non-conformant (to the RFC, not specifically anything in FHIR).
Last updated: Apr 12 2022 at 19:14 UTC
