Stream: genomics/committers
Topic: FHIR IG Publication
Kevin Power (Oct 08 2019 at 22:18):
I found the following that provides a nice checklist of things we need for publication (and I think we are in good shape on these checklist items):
https://wiki.hl7.org/FHIR_Implementation_Guide_Publishing_Requirements
However, it does not really give a "So, you are ready to publish, do these steps!" - anyone aware of such a thing?
Kevin Power (Oct 08 2019 at 22:41):
OK, I did find this:
https://wiki.hl7.org/Process_for_Publishing_a_FHIR_IG
It seems I don't have the necessary permissions, so not sure where to go from here. I feel I am simply missing some documentation somewhere?
Kevin Power (Oct 08 2019 at 22:50):
And I figured if I kept digging around, I would find it:
https://confluence.hl7.org/pages/viewpage.action?pageId=40740908
Kevin Power (Oct 08 2019 at 22:55):
Hmm, comments on this statement listed as a Dependency to the first step:
"Content of IG must be at FMM level 2 (if publishing as STU) or FMM level 5 (Normative) prior to submission of publication request "
FMM level 2 says this:
"FMM 2 PLUS the artifact has been tested and successfully supports interoperability among at least three independently developed systems leveraging most of the scope (e.g. at least 80% of the core data elements) using semi-realistic data and scenarios based on at least one of the declared scopes of the artifact (e.g. at a connectathon). These interoperability results must have been reported to and accepted by the FMG"
Bret H (Oct 08 2019 at 23:14):
mCode, ELIMU, Geisenger? We did it in the past I'd ask Llyod and maybe Gil. as I recall Implementation Guides for FHIR have a different criteria for publishing. @Lloyd McKenzie
Lloyd McKenzie (Oct 09 2019 at 02:27):
There have been several connectathons on the genetic stuff, I believe? Do you feel that you've exercised most of the stuff you're bringing forward? (Technically, the requirement for FMM2 is a requirement for going to ballot, not publishing, and it was introduced after you went to ballot, so doesn't really apply anyhow.)
Patrick Werner (Oct 09 2019 at 09:11):
Yes we tested the IG at 5+ Connectathons, this won't be the final version. But i think it is stabel/evolved enough to publish the current version
Kevin Power (Oct 09 2019 at 13:32):
Thanks for all the responses everyone. Will move forward with the request once we are done, but wanted everyone to know in case we are asked for proof of the FMM 2.
Patrick Werner (Oct 09 2019 at 16:24):
I pushed the IG version to 0.4 (last release was 0.3), after this publication we should directly push to 0.5 to avoid confusion. What do you think?
Kevin Power (Oct 09 2019 at 16:41):
I am not sure what the right version # is honestly, was going to ask that when we make the submission request.
Jamie Jones (Oct 09 2019 at 16:54):
1.0 has a nice ring to it ;)
Kevin Power (Oct 09 2019 at 16:55):
OK - the question of the year. Do we feel we are ready? @James Jones @Patrick Werner ?
Jamie Jones (Oct 09 2019 at 16:56):
I'm making a last check at all the pages
Kevin Power (Oct 09 2019 at 16:57):
Good list to check against here:
https://wiki.hl7.org/FHIR_Implementation_Guide_Publishing_Requirements
Jamie Jones (Oct 09 2019 at 16:58):
http://www.hl7.org/fhir/uv/genomics-reporting/history.cfml doesn't list version...
Jamie Jones (Oct 09 2019 at 16:58):
is that an exception? the header looks totally different, also the text mentions veterinary still
Kevin Power (Oct 09 2019 at 17:00):
Yup, that is what my last commit fixed. Or tried to. That page is generated from our 'package-list.json' file, and I think it only gets updated when we publish.
Jamie Jones (Oct 09 2019 at 17:00):
we link to it from our navbar but yeah, seems like it is a special case
Jamie Jones (Oct 09 2019 at 17:12):
Okay I think I understand this now. Once Bret resolves the broken anchor in queries and we fix the margins on index.html I would say it is ready to put up on the fridge
Bret H (Oct 09 2019 at 17:13):
broken anchor ? i can't find the problem yet
Bret H (Oct 09 2019 at 17:15):
doesn't look like any <a> tags are bad. maybe need to escape some character?
Jamie Jones (Oct 09 2019 at 17:17):
It looks like we may have to actually declare one
Bret H (Oct 09 2019 at 17:17):
ok.
Jamie Jones (Oct 09 2019 at 17:17):
looking at the source for the rendered page, it's generating a link: <a name="2.3"/>
Jamie Jones (Oct 09 2019 at 17:18):
may have to add in a <a name="IDqueries"></a>
Bret H (Oct 09 2019 at 17:18):
where?
Jamie Jones (Oct 09 2019 at 17:20):
right before <h4>Variant ID based query</h4>. Not sure why it's needed, publisher is weird
Jamie Jones (Oct 09 2019 at 17:21):
I guess each header needs an anchor, so if we don't tell it where it just takes the next element?
Bret H (Oct 09 2019 at 17:22):
need to wait for compile
Kevin Power (Oct 09 2019 at 20:23):
OK, I think everything should be good. Any other changes?
Jamie Jones (Oct 09 2019 at 20:36):
None from me!
Bret H (Oct 09 2019 at 22:53):
oops "specific instance of Obbsewrvation varaint."
Kevin Power (Oct 09 2019 at 22:53):
Fix it :slight_smile:
Bret H (Oct 09 2019 at 22:58):
done. I spelt checkd it
Kevin Power (Oct 10 2019 at 13:57):
Fellow committers - I am going to be out of the office this afternoon and tomorrow. I might have some time to continue working on the document I shared with the list serv yesterday, but I am not sure how much time I will have. Would anyone else be willing/able to continue driving completing that document and moving it on?
Kevin Power (Oct 10 2019 at 14:23):
@Patrick Werner / @James Jones / @Bret H ? ^^^ Anyone else would be welcome as well.
Sorry I didn't get this done before now.
Bret H (Oct 10 2019 at 16:13):
I am around. We're not getting a good response yet. I think the document won't be ready till next week. But I am happy to add the information as it comes in. @Kevin Power
Kevin Power (Oct 10 2019 at 16:15):
Thanks @Bret H
Kevin Power (Oct 14 2019 at 13:13):
@Bret H - any progress on the document?
Patrick Werner (Oct 14 2019 at 15:30):
hey everyone. I'm almost healthy again. I'd like to support the document creation. Should we put the doc on google docs to avoid merge problems?
Kevin Power (Oct 14 2019 at 15:34):
See here: https://drive.google.com/open?id=1JHNwl2sqIC8G7qWwVhLjPXXuTfX8BNT-
Kevin Power (Oct 14 2019 at 15:41):
btw - I think I made it editable for everyone now.
Patrick Werner (Oct 14 2019 at 15:51):
i can't edit it :-(
This is the link the doc inside google docs:
https://docs.google.com/document/d/1JHNwl2sqIC8G7qWwVhLjPXXuTfX8BNT-/edit
Kevin Power (Oct 14 2019 at 15:53):
Yea, there is some weird formatting when using Google Docs to edit the Word document. You might have to download a copy, then re-upload?
Bret H (Oct 14 2019 at 18:04):
FYI from Phillips @Alexander Mankovich synopsis: Phillips participated in Connecathon work bridging contents of their internal data model and the model as outlined in the IG for oncology reporting an output of this exercise is the oncology example in the somatic reporting section of the guide). @Kevin Power
Sorry did not have time to write this weekend. A bit impacted with surprises on pilot project and incoming projects.
Kevin Power (Oct 14 2019 at 18:12):
Thanks @Alexander Mankovich and @Bret H - I have added this to the document and uploaded a new version:
https://drive.google.com/file/d/1JHNwl2sqIC8G7qWwVhLjPXXuTfX8BNT-/view
Patrick Werner (Oct 15 2019 at 12:06):
(bad idea deleted)
Kevin Power (Oct 15 2019 at 14:18):
Yea, it messes with the layout so much, I decided not to convert it to a google doc.
Kevin Power (Oct 15 2019 at 14:20):
If you access the link to the word doc, you can click the Download button to get get a local copy.
Kevin Power (Oct 15 2019 at 14:21):
If you make some changes you want to upload, you can view the Drive folder its in: https://drive.google.com/drive/u/0/folders/1QyZYQymEkQRP6cG4VmAkPhw22MA-sEdD
Kevin Power (Oct 15 2019 at 14:22):
Select the file, click on the 3 dots, and select Manage Versions. From there, you should see an option to UPLOAD NEW VERSION.
If you don't see that option, maybe I haven't fully enabled editing?
Patrick Werner (Oct 15 2019 at 15:04):
way better than my messed up solution
Bret H (Oct 21 2019 at 21:04):
Good job. @Patrick Werner @James Jones @Kevin Power @ Bob Milius @l
Last updated: Apr 12 2022 at 19:14 UTC
