Stream: implementers
Topic: Extension versions
Jay Lyle (Mar 19 2019 at 12:32):
I have heard informally that extensions are not version-specific. It looks like they are: the extensions I see in Simplifier populate "fhirVersion", & the HL7 registries are different across the published releases (though I can't figure out how to view extension SDs there). But fhirVersion isn't a required element in SD. Must extensions have versions? Could they be re-used across FHIR versions?
Lloyd McKenzie (Mar 19 2019 at 15:18):
The StructureDefinitions identify what version of FHIR they're expressed in, but not what version of FHIR they apply to. We haven't discussed scoping extensions by FHIRVersion. @Grahame Grieve ?
Grahame Grieve (Mar 19 2019 at 19:32):
I believe that we said that StructureDefinition.fhirVersion is the version they are describing. That's certainly how I use it
Jay Lyle (Mar 26 2019 at 14:47):
I hear Lloyd drawing a distinction between a) the version of the extension definition and b) the version to which it applies, and Grahame saying it's b.
So, to make an extension usable on two different FHIR versions, you'd need to create two extensions. Or extend StructureDefinition.fhirVersion cardinality. Right?
Would leaving it blank make it available to resources of all versions, or none?
Lloyd McKenzie (Mar 26 2019 at 15:06):
At some point, we definitely want to be able to say "This extension applies to version X and on." How would we do that?
Grahame Grieve (Mar 26 2019 at 20:54):
we could extend StructureDefinition.fhirVersion so it is an NPM type version definition e.g. 3.0+
Grahame Grieve (Mar 26 2019 at 20:54):
though i don't think that's quite the same
Last updated: Apr 12 2022 at 19:14 UTC
