Stream: australia
Topic: hl7.fhir.au.base dependency
Stephen Pisani (Jan 05 2021 at 01:41):
Hi - I'm trying to import the hl7.fhir.au.base FHIR Package into my FHIR Server. The FHIR server checks that I have the relevant dependencies to do this. It complains because the hl7.fhir.au.base documents the dependency: "hl7.fhir.r4.core": "4.0.0". OK - I need to first import hl7.fhir.r4.core v4.0.0.
however - searching registry.fhir.org, I cannot find this version. All that is published version hl7.fhir.r4.core: 4.0.1.
Is the hl7.fhir.au.base dependency incorrect (should it point to 4.0.1?). If not - where can I get hl7.fhir.r4.core version 4.0.0 ??
thanks -
Lloyd McKenzie (Jan 05 2021 at 02:33):
@Grahame Grieve
Richard Townley-O'Neill (Jan 08 2021 at 02:56):
Are you using a recent version? Where are you getting au base from?
http://hl7.org.au/fhir/history.html ?
Richard Townley-O'Neill (Jan 08 2021 at 02:58):
The latest versions do use 4.0.1
Ward Weistra (Jan 14 2021 at 15:26):
@Richard Townley-O'Neill the version 2.0.0 in the FHIR package registry indeed has a dependency on hl7.fhir.r4.core 4.0.0 (see the package manifest), which has never been published.
The package registry picks up every combination of package name and package version only once, since packages are guaranteed to never change. Perhaps the dependency on the core was updated only after it was first offered to the registry?
The only option to get a new package version (incl updated dependencies) in the registry is to publish a new version, eg 2.0.1.
Richard Townley-O'Neill (Jan 15 2021 at 04:43):
Thanks @Ward Weistra
@Brett Esler I think this is for you.
Richard Townley-O'Neill (Jan 15 2021 at 04:48):
I work with AU Base through GitHub and hadn't tried to use it from the FHIR package registry.
Brett Esler (Jan 25 2021 at 04:50):
Hi - @Stephen Pisani assume you are trying to implement provider directory specification v2.0.1 http://hl7.org.au/fhir/pd/history.html - at the time FHIR core 4.0.0 was published; the PD (2.0.1) and AU Base (2.0.0) builds refererenced refer to that. FHIR core 4.0.0 was withdrawn and replaced with 4.0.1 - AU Base 2.0.0 still refers to core 4.0.0. AU Base snapshot 2.1.0 was created to reference FHIR core 4.0.1 but PD snapshot was never generated. PD CI build refers to AU Base 2.1.0; FHIR Core 4.0.1 - a snapshot for PD will appear as yet unscheduled; PD CI includes other fixes
Brett Esler (Jan 25 2021 at 04:53):
@Ward Weistra what to do with IGs with FHIR core 4.0.0 dependency (was current at the time); best to withdraw these?
Ward Weistra (Jan 25 2021 at 14:07):
@Brett Esler Retracting is not really an option in the current package-based world. You've become a victim of the FHIR Core still having been able to 'retract' the 4.0.0 version, since it was never published in the package server and your package having been published with that dependency...
The package ecosystem is made exactly to prevent these kinds of deleted dependencies (published packages will never be deleted), so this shouldn't happen in the future.
The only option is to bring out a new version of the packages with the missing dependency, with an updated dependency on the core package. The FHIR package spec currently doesn't have a generic definition of unlisting/deprecating packages, but that would probably be best to do with of those current versions.
Brett Esler (Jan 25 2021 at 21:12):
Thanks @Ward Weistra for info. The plan for AU IGs here will be
- AU Base - withdraw v2.0.0 referencing non-existant FHIR core 4.0.0
- AU Provider Directory (PD) - withdraw AU PD 2.0.1 referencing AU Base v2.0.0, FHIR core 4.0.0 - use AU Base v2.1.0 instead (fixed + existing)
- AU Provider Directory (PD) - create snapshot AU PD 2.1.0? referencing AU Base v2.1.0, FHIR core 4.0.1 (note AU PD CI build already references AU Base v2.1.0)
- i.e remove faulty versions from package lists; create a stable AU PD version for use
Last updated: Apr 12 2022 at 19:14 UTC
