FHIR Chat · uri creation · implementers

Stream: implementers

Topic: uri creation


view this post on Zulip Ruth berge (Dec 21 2020 at 06:31):

I've reviewed the FHIR spec and Lloyd McKenzies google paper from 2017 discussing URI's. The question I have is whether it is "legal" (a term Lloyd used in a response relating to this) to use an organization's root web address as the basis for a URI and then assign to it further explanation like "http://thiscompany.com/fhir/memberidentifier/someothersubsystem". Is it really that simple?

view this post on Zulip Lin Zhang (Dec 21 2020 at 09:41):

Also a kind-of agonizing question for me

view this post on Zulip René Spronk (Dec 21 2020 at 11:12):

Let's say you need an identification scheme for 'CocaCola lot numbers for cans produced in its plant in Berlin, Germany' - how would you get hold of the URI? You could try asking the Coca Cola company, but in all likely hood they haven't assigned a URI to this, they won't likely know what you're talking about anyway.
Now I could assign a URI like www.MyConsultancyCompany.com/idschemes/cocacola/cans/berlin/lot, but essentially my organization has nothing to do with the id scheme at all. Cocacola.com/cans/berlin/lot makes a lot more sense.
Is it 'legal' to re-use the company name in this way? Interesting question, albeit for lawyers, not for the average reader of this forum. You can always revert back to using OID based URNs, the OID parts do not have any semantics.

view this post on Zulip Lin Zhang (Dec 21 2020 at 11:53):

@René Spronk That's helpful. Thanks a lot.

view this post on Zulip Ruth berge (Dec 21 2020 at 16:09):

Thank you @René Spronk , but to add context, if you were in a position to tell Coca Cola that they need a uri, would you ask them if you can use their root url in the way described? Would you tell them to apply to the IANA for a uri? What other options? @Lloyd McKenzie (for use and Canada)

view this post on Zulip Lloyd McKenzie (Dec 21 2020 at 16:19):

No need to apply to IANA for a URI. Your choice is either get a URL from the specified company, define one yourself, or use a URN (e.g. OID or UUID). In general, human readable and at least potentially resolvable URLs are better for implementers

view this post on Zulip Ruth berge (Dec 21 2020 at 18:57):

I am concerned still about how to make sure a system name remains the same over time, so that 5 years from now the url hasn't switch to "newcoke" for example. Or that the domain is sold to another company. Assuming that this is indeed covered by the assignment of the url itself , then a potential future for this is to either create a web page that resolves the link in some way and/or create the trial use Naming System resource to resolve the link to an old and any other mapping. That seems to be what FHIR (as a group) is suggesting.

view this post on Zulip Lloyd McKenzie (Dec 21 2020 at 21:37):

There are a set of globally registered naming systems that, once established for a given identifier or code system, are expected to not change (though it's possible that they won't resolve in the future). Ideally, countries would maintain the same for national/regional shared identifiers and code systems. It's up to organizations to ensure consistency of naming systems within the organization. For stuff that's not registered with a central trusted authority, there's both no guarantee that the owner won't change it, nor a guarantee that other organizations will use the same URL.


Last updated: Apr 12 2022 at 19:14 UTC