Stream: IG creation
Topic: Should URI of StructureDefinition point to FHIR Endpoint?
Moritz Kähler (Feb 22 2022 at 09:33):
When I want to deploy multiple IGs into one FHIR server I see following challenges:
- How to avoid Id collisions between the profiles of different IGs?
- Should the URI of a StructureDefinition resource point to a valid FHIR endpoint?
How should the URL look in this scenario?
Would you recommend:
A) http://myCompany.org/fhir/IG-A/StructureDefinition/Profile1
or
B) http://myCompany.org/fhir/StructureDefinition/Profile1- IG-A
The advantage of A) is, that I have more freedom regarding the profile names.
Disadvantages of A) are risk of ID collisions and the URL can't be resolved in a FHIR server
So would you recommend to build URLs as described in B)?
Lloyd McKenzie (Feb 22 2022 at 14:46):
- There's no expectation that the id of a resource will be unique across all IGs. What matters is that the URL is unique across all IGs. The id of a resource will typically vary as it moves from server to server.
- There's no specific rule, but given that content in different IGs is typically managed separately, treating the IG as the namespace is safest. HL7 international uses approach A for its IGs - and sets up redirects so that canonical URLs redirect to the appropriate hosted pages.
Last updated: Apr 12 2022 at 19:14 UTC
