Firefly has told us that version-linking (as an automated feature) is a common request, so that is on their roadmap for release. I'm not sure if that applies to just ValueSet and CodeSystem, or also to Profiles.
Currently to do so to date has been very tricky, it's an entirely manual process with our current tooling. We're also not sure what the best practices are internationally, we'll take a look at this
Yes, version should be populated in the conformance resources (profiles, extensions, valuesets, etc.) in an IG.
Depending on the tooling used to create the implementation guide, this can be done automatically (along with selecting to propagate date, contact, context, jurisdiction, license, publisher, copyright, and status elements). My guess is that between PSCA 1.0.0 and PSCA 2.1.1 Infoway changed the tooling, and forgot to account for the difference in capabilities.
However, if PSCA 2.1.1 is still in draft, this is an easy and quick fix for them.
I saw that most of the releases of IG do not contain the version for each of the profiles. I was wondering if there was a general guidance that prevented populating them.
Improving the quality of patient care through the effective sharing of clinical information among health care organizations, clinicians and their patients.
StructureDefinition.version in the IG
Print
Email
Twitter