Stream: implementers
Topic: computable list of published implementation guides?
Sean McIlvenna (Oct 04 2018 at 03:24):
I'm looking for a computable list of published implementation guides that I can use to populate a drop-down based on... Is there a json or xml file posted on build.fhir.org or www.hl7.org/fhir that has a list of all published IGs?
Lloyd McKenzie (Oct 04 2018 at 03:33):
"all" is a bit ambitious - but these are all of the ones in the HL7 registry: https://github.com/FHIR/ig-registry/blob/master/fhir-ig-list.json
Lloyd McKenzie (Oct 04 2018 at 03:33):
If you're looking for more, you can hit Simplifier
Grahame Grieve (Oct 04 2018 at 10:35):
that's the best source at the moment
Sean McIlvenna (Oct 04 2018 at 12:02):
How does this map to ImplementationGuide.dependsOn?
ImplementationGuide.dependsOn.uri = guides.editions.url
ImplementationGuide.dependsOn.packageId = guides.npm-name
ImplementationGuide.dependsOn.version = guides.editions.ig-version
?
Sean McIlvenna (Oct 08 2018 at 18:03):
based on the .json data in fhir-ig-list.json, I'm not thinking this cannot be mapped 1:1 to ImplementationGuide.dependsOn...???
Grahame Grieve (Oct 08 2018 at 18:28):
what can't be mapped?
Sean McIlvenna (Oct 08 2018 at 20:01):
@Grahame Grieve the json seems to have some rather non-standard names for the guides, as well as non-standard versions.. I see a lot of "n/a", some are "?".. even the url seems to occasionally point to a specific html file, rather than the root of the guide
Grahame Grieve (Oct 08 2018 at 20:03):
two igs have versions of n/a from before we sorted ig versions
Grahame Grieve (Oct 08 2018 at 20:03):
if you think they're wrong, you can make a pull request
Grahame Grieve (Oct 08 2018 at 20:04):
what names are non-standard?
Sean McIlvenna (Oct 08 2018 at 20:32):
ok, that makes sense
Sean McIlvenna (Oct 08 2018 at 20:32):
as for the name... I was using the wrong field
Sean McIlvenna (Oct 08 2018 at 20:32):
I should have been using npm-name field
Sean McIlvenna (Oct 08 2018 at 20:32):
rather than .name
Grahame Grieve (Oct 08 2018 at 21:07):
indeed
Sean McIlvenna (Oct 25 2018 at 16:17):
@Grahame Grieve , I'm using fhir-ig-list.json to populate the ImplementationGuide.dependsOn values. However, the IG publisher is failing when I use the values in fhir-ig-list.json. It looks like the version and npm-name are not accepted by the ig publisher. Is there a better way to "select" a published ig as a dependency?
Sean McIlvenna (Oct 25 2018 at 16:17):
@Rick Geimer
Grahame Grieve (Oct 26 2018 at 13:14):
However, the IG publisher is failing when I use the values in fhir-ig-list.json. It looks like the version and npm-name are not accepted by the ig publisher
I don't know what that means. can you be specific?
Sean McIlvenna (Oct 26 2018 at 16:41):
For example, if I use
"hl7.fhir.us.core" for ImplementationGuide.dependsOn.packageId
"1.0.0" for ImplementationGuide.dependsOn.version
and "http://hl7.org/fhir/us/core/" for ImplementationGuide.dependsOn.uri
(values directly from fhir-ig-list.json)
then the FHIR IG Publisher build fails.
I have to instead use
"uscore", "1.0.1" and "http://hl7.org/fhir/us/core" (without a trailing slash)
Sean McIlvenna (Oct 26 2018 at 16:42):
In other words, no combination of values from the fhir-ig-list.json file can be used to populate the ImplementationGuide.dependsOn properties, without the FHIR IG Publisher failing
Sean McIlvenna (Oct 26 2018 at 16:42):
@Grahame Grieve
Grahame Grieve (Oct 27 2018 at 07:53):
that's not right. I'll investigate
Last updated: Apr 12 2022 at 19:14 UTC
