FHIR Chat · Package.canonical, ImplementationGuide.url, and Templating · IG creation

Stream: IG creation

Topic: Package.canonical, ImplementationGuide.url, and Templating


view this post on Zulip Chris Moesel (Feb 20 2020 at 18:32):

We're looking at supporting more advanced IG configuration in SUSHI -- and part of that may involve using ImplementationGuide as a config rather than package.json. In package.json, we have something like:

"canonical" : "http://somewhere.org/fhir/uv/myig",

This is the canonical root of the IG.

In the sample-ig ImplementationGuide instance, however, we have:

<url value="http://somewhere.org/fhir/uv/myig/ImplementationGuide/example.fhir.uv.myig"/>

This is the canonical URL of the ImplementationGuide instance itself (not the canonical root of the IG). Is this right? In the core FHIR spec example for Implementation Guide, the url is the canonical root (like the one in package.json). I can't tell if the difference in the sample-ig is intentional or a mistake.

Either way, we may need to determine the canonical root of the IG from the ImplementationGuide instance in SUSHI, and I'm just trying to figure out if I need to parse it out of the ImplementationGuide url (essentially slicing off the tail end of the path) or if I can rely on the ImplementationGuide url already being the root. (Maybe to be safe I ought to support both).

view this post on Zulip Rob Hausam (Feb 20 2020 at 18:59):

I agree that we need to have clarity on this.

view this post on Zulip Grahame Grieve (Feb 20 2020 at 20:19):

so the Implementation Guide itself has a canonical URL, and also the ImplementationGuide resource for the iG has a canonical URL.

The difference between the two is subtle, and painful for the tools, and also important..

The IG publisher enforces that the IG resource canonical URL is [canonical]/ImplementationGuide/[package-id]


Last updated: Apr 12 2022 at 19:14 UTC