Stream: IG creation
Topic: FMG Review: Ballot Issues
Sarah Gaunt (Nov 26 2020 at 00:14):
Just looking at the FMG review for the IGs going to ballot (meeting notes and Google Sheet). I see this:
Vital Records Common Profiles Library ... Codes in canonical and package id are different.
But I can't figure out what is being flagged as wrong. The QA says: vr-common-library . PackageId = hl7.fhir.us.vr-common-library, Canonical = http://hl7.org/fhir/us/vr-common-library
which seems to match? What am I missing? (I just fixed the HTA issues).
http://build.fhir.org/ig/HL7/vr-common-library/branches/master/qa.html
Sarah Gaunt (Nov 26 2020 at 00:38):
Oh, I think I see it. The id of the ImplementationGuide should be fhir-us-vr-common-library...
i.e. the url for the IG should be: http://hl7.org/fhir/us/vr-common-library/ImplementationGuide/fhir-us-vr-common-library?
Sarah Gaunt (Nov 26 2020 at 00:40):
Sorry, but I'm finding this super confusing and I can't find an error message for it anywhere.
Lloyd McKenzie (Nov 26 2020 at 00:55):
Also check what's in your package-list.json
Sarah Gaunt (Nov 26 2020 at 00:59):
So to get this straight in my head am I correct in assuming (for HL7 US Realm IGs anyway) the following:
- package-id = hl7.fhir.us.<ig-code>
- canonical url = http://hl7.org/fhir/us/<ig-code>
- ImplementationGuide.id = hl7-fhir-us-<ig-code>
In the case of the Vital Records Common Profiles Library <ig-code> = "vr-common-library".
Sarah Gaunt (Nov 26 2020 at 01:00):
This is what I have - thinking the first and second bullets are wrong:
- ImplementationGuide.url = http://hl7.org/fhir/us/vr-common-library/ImplementationGuide/vr-common-library
- ImplementationGuide.id = vr-common-library
- ImplementationGuide.packageId = hl7.fhir.us.vr-common-library
- package-list.json package-id = hl7.fhir.us.vr-common-library
- package-list.canonical = http://hl7.org/fhir/us/vr-common-library
Lloyd McKenzie (Nov 26 2020 at 01:53):
That looks right to me...
Sarah Gaunt (Nov 26 2020 at 03:07):
Thank you.
Sarah Gaunt (Nov 26 2020 at 23:22):
So how do I/we/ @Grahame Grieve go about coordinating the dependency that both BFDR and eCR have on the Vital Records Common Library? i.e. the fact that right now, both of those IGs point to the current/ci build version of the Vital Records Common Library. From the email Melva sent:
Dependency error - You need to lock to a specific version of vr-common-library - ideally the most recent ballot snapshot. If they need newer content than that, they'll have to make an arrangement with Grahame to have a snapshot taken of vr-common-library that they can point to.
FYI: Vital Records Common Library is error free, it just has one warning left which is to do with the Jira spec (and I may or may not get to fixing that this week, otherwise I'll ask @David deRoode to fix it early next week, as he actually knows what he is doing in that space!).
Sarah Gaunt (Nov 26 2020 at 23:23):
Can we maybe get the Library ready for ballot earlier than the other two (like very soon) so that we can point to that version?
Sarah Gaunt (Nov 26 2020 at 23:23):
Or do we have to wait for the work group to vote to go to ballot on the 3rd before we can progress this?
Sarah Gaunt (Nov 26 2020 at 23:25):
Or is it as simple as changing the reference in the dependency to what we know will be the correct url? i.e. http://hl7.org/fhir/us/vr-common-library/2021Jan
Grahame Grieve (Nov 26 2020 at 23:26):
you can't refer to it until it exists
Grahame Grieve (Nov 26 2020 at 23:26):
are they all being submitted at once?
Sarah Gaunt (Nov 26 2020 at 23:26):
Yes.
Sarah Gaunt (Nov 26 2020 at 23:27):
Well, they are all going to ballot at the same time. But the Library that the other two depend on is pretty much ready to go now.
Sarah Gaunt (Nov 26 2020 at 23:28):
The only issue left is the jira spec issue.
Grahame Grieve (Nov 26 2020 at 23:28):
hmm. It's pretty much going to be case of Lynn publishing the library first, and then once she's done that, you update the reference to specify the version she publishes in the others, instead of 'current', and then she publishes the others
Grahame Grieve (Nov 26 2020 at 23:28):
I'll have to think if I can come up with a better way
Sarah Gaunt (Nov 26 2020 at 23:29):
Ok, that sounds fine for now anyway. I'll just have to co-ordinate with her.
Sarah Gaunt (Nov 26 2020 at 23:37):
@Lynn Laakso just tagging you so you are aware of this dependency/publication issue. We can chat/co-ordinate closer to ballot on how to synchronize the publication of the three FHIR IGs. Also tagging @Melva Peters so she is aware of the conversation.
Lloyd McKenzie (Nov 27 2020 at 03:47):
@Grahame Grieve What if we need a published snapshot of an in-development guide to point to when we're not balloting that guide (it's been balloted but it won't be ready to publish in the timeframe we want to publish the referencing IG, and the balloted version doesn't contain the necessary content). How do we request that a snapshot be created?
Grahame Grieve (Nov 27 2020 at 05:29):
you'd have to ask the FMG a question like that
Lloyd McKenzie (Nov 27 2020 at 17:25):
The FMG discussed in in principle a few months ago and decided that it was possible - the same sort of thing as producing a connectathon snapshot. I'm asking about the practicalities of "how do we get a connectathon snapshot of an IG created?"
Sarah Gaunt (Nov 27 2020 at 20:11):
So are you saying that it is then "legal" to publish an IG that depends on another non-published/draft IG? I thought that was not allowed?
Grahame Grieve (Nov 27 2020 at 20:29):
it's not allowed to depend on current, because that's not stable, but it's allowed to depend on an unballoted publication
Grahame Grieve (Nov 27 2020 at 20:29):
I think that's what Lloyd is saying
David Pyke (Nov 27 2020 at 21:51):
That would be very helpful if it were possible to have a dependency on an un-published version of an IG, whetehr a connectathon snapshot or otherwise. I've needed that in the past and had to work around the lack of that
Lloyd McKenzie (Nov 27 2020 at 22:44):
That is what Lloyd's saying. It's allowed when doing STU. When we get to normative IGs, the rules will be a bit different.
Last updated: Apr 12 2022 at 19:14 UTC