FHIR Chat · Dependency issue · IG creation

Stream: IG creation

Topic: Dependency issue


view this post on Zulip Rick Geimer (Jan 04 2019 at 15:19):

Hi all. Getting the following error on an IG with a dependency on C-CDA on FHIR:

Publishing Content Failed: Unable to find the package source for 'hl7.fhir.us.ccda#1.0.0' at http://hl7.org/fhir/us/ccda/STU1/index.html/package.tgz (27.0806sec)

Anybody run into this with other IG dependencies?

view this post on Zulip Chris Moesel (Jan 08 2019 at 14:17):

Yeah -- I've run into it trying to do a dependency on the Argonaut IG. As far as I know, it's still unresolved.

view this post on Zulip Rick Geimer (Jan 13 2019 at 17:03):

I just ran into this with a QI Core dependency as well:

Load uscore (http://hl7.org/fhir/us/core) from hl7.fhir.us.core#2.0.0 (33.0039sec)
Fetch Package history from http://www.hl7.org/fhir/us/qicore/package-list.json
Fetch hl7.fhir.us.qicore-3.0.1 package from http://www.hl7.org/fhir/us/qicore/STU3/index.html/package.tgz (33.0750sec)
Publishing Content Failed: http://www.hl7.org/fhir/us/qicore/STU3/index.html/package.tgz (33.0799sec)

Not sure why it is trying to parse "index.html" as if it were a directory. The actual dependency in my IG is "http://www.hl7.org/fhir/us/qicore".

view this post on Zulip Rick Geimer (Jan 13 2019 at 17:09):

Perhaps package-list.json in QI Core (and C-CDA on FHIR) needs to be updated. Here is a snippet:

{
"version" : "3.0.1",
"date" : "2018-08-21",
"descmd" : "STU 3 (v3.1.0)\r\n* Added profile for PractitionerRole and removed Practitioner.role extension\r\n* Added profile for Task\r\n* Established pattern for representing QDM Principal Diagnosis in Encounters\r\n* Relaxed conformance requirements from all profiles to profiles that are relevant to a particular use case",
"desc" : "STU 3 (v3.1.0)",
"path" : "http://www.hl7.org/fhir/us/qicore/STU3/index.html",
"status" : "trial-use",
"sequence" : "STU 3",
"current" : true
}

I'm guessing that path should be "http://www.hl7.org/fhir/us/qicore/STU3"

@Grahame Grieve Is this something you can fix in the various published IGs (possibly by re-running them against the latest IG publisher)?


Last updated: Apr 12 2022 at 19:14 UTC