FHIR Chat · Bundle.entry.fullUrl · implementers

Stream: implementers

Topic: Bundle.entry.fullUrl


view this post on Zulip Patrick Childers (Jan 16 2017 at 20:20):

Shouldn't Bundle.entry.fullUrl be named Bundle.entry.fullUri as it isn't required to be a URL? Has this been discussed for a future spec revision?

view this post on Zulip Grahame Grieve (Jan 16 2017 at 20:34):

we consistly use url rather than uri to encourage url, since we strongly prefer url

view this post on Zulip Michael Donnelly (Jan 16 2017 at 20:37):

Not disagreeing, just curious: why do you prefer URL to URI?

view this post on Zulip Patrick Childers (Jan 16 2017 at 20:40):

That makes sense, I was working on a patient referral use case and reading over https://lightmyfhir.org/2016/02/26/fhir-transactions/ to understand more about sending bundles to import. And it seemed like URNs would be the preferred mechanism as to handle the server behavior for generating ids.

view this post on Zulip Michel Rutten (Jan 16 2017 at 20:44):

How about https://www.hl7.org/fhir/implementationguide-definitions.html#ImplementationGuide.dependency.uri ?

view this post on Zulip Rick Geimer (Jan 16 2017 at 20:47):

@Michael Donnelly URLs are preferred because they are directly resolvable, unlike urn:uuid:blah-blah-blah

view this post on Zulip Michael Donnelly (Jan 16 2017 at 21:45):

Ah, that makes sense.


Last updated: Apr 12 2022 at 19:14 UTC