Stream: conformance
Topic: Package dependency vs SD.fhirVersion
Alexander Henket (Dec 02 2019 at 09:24):
Package dependency FHIR Core and StructureDefinition.fhirVersion seem to have overlap and could contradict.
Is there any guidance on how to deal with that?
- if you have a package dependency: should you just skip SD.fhirVersion?
- if package dependency is 3.0.2 and SD.fhirVersion is 3.0.1: is that an issue?
Maybe there are more issues, we haven't identified.
Grahame Grieve (Dec 02 2019 at 09:41):
there's no formal guidance. The Java loader will currently only load for a single version, so the two must tell the same story, but this will change in the future.
Grahame Grieve (Dec 02 2019 at 09:41):
the version checking is only on maj/min - the patch is ignored
Alexander Henket (Dec 02 2019 at 11:58):
So 3.0.1 versus 3.0.2 is not an issue then. For now that saves us updating all our profiles.
The Java loader will currently only load for a single version, so the two must tell the same story, but this will change in the future.
Interesting... what is the intended change? (for as far as that has been decided today that is)
Grahame Grieve (Dec 02 2019 at 12:18):
The ig publisher is going to support publishing multiple version igs. As part of that, the package loader will have to be able to load across multiple versions.
I’ll also take that chance to resolve that you must tell the validation what version, you can’t let it figure that out for itself from the profiles and instances
Last updated: Apr 12 2022 at 19:14 UTC
