Stream: IG creation
Topic: IG version v conformance resource version
Eric Haas (Oct 19 2018 at 23:53):
Re versioning: here is what we are currently doing in US Core: http://wiki.hl7.org/index.php?title=IG_Publisher_Documentation#Version
So Brett and I chatted about this this AM, I think we need create an IG version 1.1.0 for the IG ( in the IG Resource - I presume) and then add the version element in the source for all the conformance resources in the IG ( either 1.1.0 or 1.0.1 depending) instead of creating a blanket version. Does this matter to implementers.- I guess we need to ask....
@Grahame Grieve I have a lot of liquid using IG version specification {{site.data.fhir.ig.version}}. I believe this is defined in the ig.json file because it does not change when I update the IG resource. But in example Jekyll data file below it looks like it was intended to be defined by the IG resource. If we switch to having the IG version separate from the conformance resources then this becomes important to my templates. I can always create my own custom variables but I think the intent was to use the IG resource as input.
here is my _data/fhir.json :
{
"path": "http://build.fhir.org/",
"canonical": "http://www.fhir.org/guides/test3",
"igId": "ig",
"igName": "IG_Test3FOO",
"igVer": "0.0.0",
"errorCount": 20,
"version": "3.6.0",
"revision": "ba2a53f1",
"versionFull": "3.6.0-ba2a53f1",
"toolingVersion": "3.6.0",
"toolingRevision": "2",
"toolingVersionFull": "3.6.0 (2)",
"totalFiles": 9,
"processedFiles": 7,
"genDate": "Fri, Oct 19, 2018 16:36-0700",
"ig": {
"id": "ig",
"name": "IG_Test3FOO",
"url": "http://www.fhir.org/guides/test3/ImplementationGuide/ig",
"version": "0.0.0",
"status": "draft",
"experimental": false,
"publisher": "Health eData Inc",
"copyright": "Used by permission of Health eData Inc, all rights reserved Creative Commons License",
"fhirVersion": "3.6.0"
},
"uscore": "http://hl7.org/fhir/us/core"
}
Last updated: Apr 12 2022 at 19:14 UTC
