Stream: Announcements
Topic: Ballot
Grahame Grieve (Dec 14 2017 at 04:53):
Reminder: on Dec 22, 2017 the FHIR R4 ballot cycle commences with a draft for comment ballot. Please note the following:
- this is the first normative ballot cycle - some of the FHIR content will be balloted as normative
- this particular is the first of three ballots to lead to the normative parts of R4
- once it finally passes normative, there can be no breaking changes (well, it takes many years)
- any substantive change during ballot reconciliation requires reballot - therefore committees balloting normative comment will be highly motivated to refuse proposals for change
- after this draft for ballot, there is no way to change what is selected to be balloted as normative or not for the rest of this cycle, nor to make substantiative changes to it
We therefore looking for good review on this draft for comment ballot on the following things:
- what content has been selected for normative
- how the normative status is presented (clearly, hopefully)
- the technical content of the normative material
- any suggestions for content that needs further implementation experience in the next few months
We need you @all to comment on this stuff. And if you want to do that, you have to sign up for the HL7 ballot at http://www.hl7.org/participate/onlineballoting.cfm?ref=common by Dec 21st - that's a week away. Please do that and comment on the normative preparations.
If you want to comment now, the normative preparations are mostly done, and visible at build.fhir.org. Any comments received before the ballot are most appreciated. Note that there following things have been added:
- every page has a status bar now
- normative markers for normative content and resources (see http://build.fhir.org/documentation.html, http://build.fhir.org/resourcelist.html, http://build.fhir.org/terminologies-systems.html, and http://build.fhir.org/terminologies-valuesets.html_
- status markers on elements and operations (see http://build.fhir.org/bundle-definitions.html#Bundle.signature and http://build.fhir.org/codesystem-operations.html#compose)
- a dependency analysis for resources (see e.g . http://build.fhir.org/patient-dependencies.html)
- a description of the ballot: http://build.fhir.org/ballot-intro.html
Ewout Kramer (Dec 18 2017 at 09:21):
Two questions:
- I don't see any normative markers on the mentioned link
http://build.fhir.org/terminologies-systems.html, is that correct? - The status markers like those on
Bundle.signatureallow marking parts of normative conent as "trial use", is that the intent? So there will be a "super normative" when all parts of a normative resource are normative? Or will there always be non-normative parts in normative resources?
Lloyd McKenzie (Dec 18 2017 at 15:40):
Please discuss on implementers or social
Grahame Grieve (Dec 20 2017 at 23:41):
Further Ballot related announcement:
- As advised before Dec 22 is when ballot registration closes. Remember to register
- FHIR v3.2 is now available at http://hl7.org/fhir/2018Jan - this is the ballot version, and also the basis for the New Orleans Connectathon
- servers, reference implementations etc that support this version are starting to roll out today
Note: although this is the offiical basis for the New Orleans we know that some tracks and some attendees will be using past versions of FHIR
Grahame Grieve (Dec 21 2017 at 06:34):
Last announcement: https://onfhir.hl7.org/2017/12/21/fhir-r4-ballot-community-consultation/ - note: this has some community consultation items in there
Grahame Grieve (Aug 19 2018 at 21:55):
The end of ballot sign up is approaching - you have 4 days (until end of Sep 23rd US eastern) to sign up to vote on the following ballots:
Core: (posted at http://hl7.org/fhir/2018Sep/ballot-intro.html)
R4 General (Trial Use)
R4 Infrastructure Normative
R4: Observation Normative
R4: Patient Normative
R4: Terminology and Conformance Normative
International IGs:
- International Patient Summary
- LOINC – IVD Test Code (LIVD) Mapping
- Point-of-Care Device (PoCD)
- Potential Drug-Drug Interaction (PDDI) Clinical Decision Support (CDS)
- Validated Healthcare Directory
- Structured Data Capture (SDC) (delayed)
US Realm IGs
- Electronic Case Reporting (eCR)
- Coverage Requirements Discovery
- Data Exchange for Quality Measures
- Bidirectional Services eReferrals (BSeR)
- Occupational Data for Health (ODH)
- Breast Cancer Data (delayed)
- Patient Reported Outcomes (PRO) (delayed)
- Women’s Health Technology Coordinated Registry Network (CRN) (delayed)
Notes:
- you can't currently sign up for the Breast Cancer IG - that might change, and I will announce that here
- Several of these ballots are delayed - they are expected to open a week late (time still unsure?). Sign up will remain open until just before they open
- most of the US realm IGs were erroneously announced as UV not US. This list here is correct.
- Change of scope: SDC is changing from US realm to international ballot this cycle
*
Grahame Grieve (Aug 19 2018 at 21:56):
Note that the core ballots are all cycle #2 ballots. What this means is that the scope is limited to the changes made from the 2018-May ballot cycle. Feedback not related to changes made will most likely be found "not related" and/or deferred to consideration as part of R5
Grahame Grieve (Aug 19 2018 at 21:56):
I don't believe that this limitation applies for any of the IGs
Grahame Grieve (Aug 19 2018 at 21:58):
Note that we had previously announced that the normative ballot cycle #2 ballots would be closed pool, limited to the people who signed up for ballot #1. It turns out that this is not the case, so if you were signed up for ballot #1, and you want to vote again you need to sign up for ballot #2 again. And if you didn't sign up to ballot #1, you can sign up anyway
Grahame Grieve (Aug 19 2018 at 22:01):
This ballot, if any substantive changes are made to the normative packages, then they will fail normative and fall back to trial-use status. Also, if this ballot fails - that is, the ballot pool votes negatively on the changes since ballot #1, then they will fall back to trial-use. Please join and vote in favor of closing out R4
Grahame Grieve (Aug 19 2018 at 22:47):
I wrote "Sep 23" above, but it was meant to be Aug 23. Sorry if that caused any confusion
Grahame Grieve (Aug 22 2018 at 22:29):
further information about the ballot: all the ballot content that is opening on time is now ready.
FHIR core ballots: http://hl7.org/fhir/2018Sep
FHIR Igs (International)
- International Patient Summary: http://hl7.org/fhir/uv/ips/2018Sep
- Loinc/IVD Test mapping: http://hl7.org/fhir/uv/livd/2018Sep
- Point of Care Devices: http://hl7.org/fhir/uv/pocd/2018Sep
- Potential Drug/Drug Interaction: http://hl7.org/fhir/uv/pddi/2018Sep
- Validated Healthcare Directory: http://hl7.org/fhir/uv/vhdir/2018Sep
FHIR Igs (US Realm)
- Coverage Requirements Determination (Da Vinci): http://hl7.org/fhir/us/davinci-crd/2018Sep
- Data Exchange for Quality Measures (Da Vinci):http://hl7.org/fhir/us/davinci-deqm/2018Sep
- Electronic Case Reporting: http://hl7.org/fhir/us/ecr/2018Sep
- Occupational Data for Health: http://hl7.org/fhir/us/odh/2018Sep
In addition, I have posted the final version of STU 3 for QI Core here: http://hl7.org/fhir/us/qicore/2018Sep
Richard Townley-O'Neill (Aug 22 2018 at 23:07):
http://hl7.org/fhir/us/qicore/2018Sep returns a 404
Grahame Grieve (Aug 22 2018 at 23:19):
that's because I meant to write http://hl7.org/fhir/us/qicore/STU3
Jon Behr (Sep 12 2018 at 12:21):
Excuse my ignorance - does this mean the occupationalData will only available as a resource to use in the US? The elements within it look laregly transferable (am UK based).
Bryn Rhodes (Sep 12 2018 at 14:05):
That's it's balloted as US realm means that it has terminology bindings or other considerations that are applicable only in the US. The resources on which it is based are part of the FHIR spec, so can be used universally, but to use it in the UK there would likely need to be UK-specific bindings and/or considerations. Does that help?
Lloyd McKenzie (Sep 12 2018 at 14:14):
Discussion should happen on the #implementers thread, not here.
Yunwei Wang (Sep 19 2018 at 19:22):
After create a tracker for ballot comment, do I need to choose an item from Ballot dropdown? I don't see 2018-Sep in the list.
Lloyd McKenzie (Sep 19 2018 at 21:17):
No. No user should ever touch the ballot dropdown. It'll be populated by the automatic load process from your submitted ballot spreadsheet that references the gForge tracker item.
Lloyd McKenzie (Sep 21 2018 at 15:54):
Reminder to everyone that the Normative and STU ballots on the core specification as well as a number of the implementation guides are due at end of day (midnight Eastern) on Monday Sept. 24. There's another subset that close on the Sunday right before the WGM. Happy balloting this weekend... :)
Lloyd McKenzie (Sep 24 2018 at 17:23):
At present, some of the FHIR Normative ballots have less than a 30% response rate. If, by midnight Eastern tonight we don't have at least a 50% response, the ballots will fail. We do have the ability to do a one-time extension to allow additional submissions to come in, but doing so will make it difficult to triage the comments for consideration in Baltimore which in turn puts other aspects of the publication timeline at risk. (And if we don't make 50% by the end of any extension period, we fail with no further recourse.)
TL/DR: Get your ballot responses in ASAP!
Lloyd McKenzie (Sep 24 2018 at 23:43):
Thanks for everyone getting their ballots in. It turns out that the scare was due to an error in the ballot website's summary screen. While the summary screen shows that we're short of 40% participation, the detail screens show that we're actually approaching 80% participation. So there will not be an extension. There's just over 4 hours to get in your ballot comments if you want them to be considered as part of the ballot response.
Peter Jordan (Sep 25 2018 at 00:31):
Looks as if that summary page is still counting all the duplicate entries that have produced multiple emails to participants over the past few weeks.
Lynn Laakso (Feb 28 2022 at 16:18):
HL7 Announcement of Formation of Regular Cycle Consensus Groups for 2022May - sign up for ballot pools at www.hl7.org/permalink/?BallotDesktop or review the list of items open for enrollment at https://confluence.hl7.org/x/6rdiBQ.
Lynn Laakso (Mar 21 2022 at 12:20):
Ballot consensus pool enrollment for regular cycle May ballots closes next Thursday, March 31 - sign up now!
HL7 Announcement of Formation of Regular Cycle Consensus Groups for 2022May - sign up for ballot pools at www.hl7.org/permalink/?BallotDesktop or review the list of items open for enrollment at https://confluence.hl7.org/x/6rdiBQ.
Lynn Laakso (Mar 21 2022 at 12:21):
Ballot voting for early May 2022 cycle ends Wednesday March 23 - don't forget to vote!
Last updated: Apr 12 2022 at 19:14 UTC
