Stream: implementers
Topic: Extension node in FHIR
Steffy Thankam Wilson (Feb 01 2022 at 09:11):
Hi, there are some doubts about the extension node in the FHIR.In the Extension node, there are some other attributes like url and valueCoding. In url attribute, is it necessary to specify a valid url .
Oliver Egger (Feb 01 2022 at 09:20):
the url defines the content and meaning of the extension, see also here https://hl7.org/fhir/extensibility.html#extension
Steffy Thankam Wilson (Feb 01 2022 at 09:24):
if the node added doesn't have a valid url then what to do?
René Spronk (Feb 01 2022 at 09:32):
The url needs to be valid as per the relevant RFC (for the construction of urls). It need not 'resolve', it's just an identifier after all.
Notification Bot (Feb 01 2022 at 13:52):
Steffy Thankam Wilson has marked this topic as resolved.
Notification Bot (Feb 01 2022 at 13:52):
Steffy Thankam Wilson has marked this topic as unresolved.
Lloyd McKenzie (Feb 01 2022 at 14:30):
However, FHIR also has a requirement that if you transmit an instance that contains an extension, the recipient must have access to the definition of the extension. The simplest way to ensure this is for the extension URL to resolve. If you publish an extension where the URL doesn't resolve, then you either need to pre-coordinate with your recipients (and they need to pre-coordinate with their recipients), or the extension needs to be registered in a registry agreed with the community who will exchange the data.
Jose Costa Teixeira (Feb 01 2022 at 22:02):
...in other words, the URLs better resolve, right?
Lloyd McKenzie (Feb 01 2022 at 23:31):
More "URLs don't have to resolve, but your life is easier when they do"
Last updated: Apr 12 2022 at 19:14 UTC
