Skip to end of metadata
Go to start of metadata

Health Level Seven International



December 27, 2019

Health Level Seven International® invites you to take part in the regular cycle ballot openings for balloting HL7 candidate standards and documents for the February 2020 ballot cycle. 

The candidate standards and other documents described in this announcement are balloting prior to HL7's February 2020 Working Group Meeting (WGM). Comments received from consensus group members will be addressed at that WGM running February 2-7, 2020 in Sydney NSW Australia.


Special note: 

FHIR has recently changed from using gForge to using Jira to capture feedback.  While submitting ballot comments using spreadsheets is still supported, balloters responding to FHIR ballots are encouraged to submit items into Jira instead and only use spreadsheets to reference their submitted Jira comments.  Ballot votes on individual comments must still be submitted with spreadsheets even if the comments are submitted using Jira, though we anticipate migration of the full ballot process to Jira (eliminating the need for spreadsheets) later this year.

Since we expect to be transitioning FHIR tracking items JIRA during the ballot period, balloters are advised to use spreadsheets to submit their ballot comments. 

Thanks for your cooperation.

Ballot Period Open/Close Dates

Voting for consensus group members in most ballots in this document will open and close on the following dates.  Exceptions for a specific ballot are listed with that ballot description.

Ballot Open Date: Friday, December 27, 2019

Ballot Close Date: Monday, January 27, 2020

Consensus Group Enrollment Period

Consensus Group Enrollment Period is now closed

Important Note:  Consensus group signup closes when ballot voting begins.

Changes from the initial announcement are identified in the Update to Ballot Announcement for February 2020 Ballot Cycle  document released when this ballot cycle opens.

All those engaged in balloting should be informed that any subsequent ballot of material previously balloted at the normative level will supersede all previous ballots. Any votes or comments from previous ballots will not count towards the new normative ballot; for any comments to be considered again, voters will need to cast a new ballot with comments.


The grid below provides the name of the sponsoring and co-sponsoring Work Group(s) announcing the ballot opening for the ballot listed. Those interested in ballots for a certain attribute can sort the grid: by Work Group, or by product family for example.

Work GroupProject IDBallot NameFamilyBallot IterationBallot DescriptionLast BallotedUnique Ballot ID
Clinical Decision Support1535HL7 CDS Hooks: Patient-View Hook, Release 1HL7 1st STU BallotThis document describes a CDS Hooks Hook Definition for the patient-view hook, which occurs when a user has just opened a patient's record.Since the last ballot of this material in 2020FEB , the following changes have been made: This material was initially balloted as part of the CDS Hooks specification. Hook definitions were removed from the CDS Hooks specification itself to allow hooks to mature independently. This ballot has not materially changed the content of the hook definition.HL7_CDSHOOKS_PATVIEW_R1_D1_2020FEB
Clinical Quality Information1499HL7 FHIR® Implementation Guide: Quality Measures, Release 1- US RealmFHIR 2nd STU BallotThis implementation guide describes an approach to representing electronic Clinical Quality Measures (eCQMs) using the FHIR Clinical Reasoning Module and Clinical Quality Language (CQL) in the U.S. Realm. However, this Implementation Guide can be usable for multiple use cases across domains, and much of the content is likely to be usable outside the U.S. Realm.Since the last ballot of this material in 2020FEB , the following changes have been made: This ballot supporting the FHIR R4 version includes numerous changes in support of reconciliation efforts with comment submitters, as well as the inclusion of use cases to support more general quality measurement and public health reporting use cases. FHIR_IG_QM_R1_D2_2020FEB
Clinical Quality Information1429HL7 FHIR® Implementation Guide: Data Exchange for Quality Measures, Release 1 - US RealmFHIR 3rd STU BallotThis Implementation Guide defines common data exchange patterns usable for a broad range of value-based health care use cases, including quality measurement and reporting, and public health care reporting.Since the last ballot of this material in 2020FEB , the following changes have been made: This ballot supporting the FHIR R4 version includes numerous changes in support of reconciliation efforts with comment submitters, as well as the inclusion of use cases to support more general quality measurement and public health reporting use cases. Substantive changes include: 1) Ensuring the guidance addresses challenges associated with pull and subscription exchange mechanisms. 2) Ensuring the exchange mechanisms can support the use of messaging protocols. 3) Ensuring support for additional use cases including Colorectal Cancer Screening and Hospital Reporting for Venous Thromboembolism and Stroke reporting. 4) Ensuring support for communication of quality measurement results. FHIR_IG_QMEXCHANGE_R1_D3_2020FEB
Conformance1396Version 2 Conformance Methodology, Release 1V2X-Related 1st Normative BallotThis specification provides the rules and documentation requirements for profiling HL7 v2 base message definitions. It also provides guidance on how to assemble a set of message profiles to satisfy the requirements of a set of use cases documented in an implementation guide. A goal is to provide specifiers and implementers the mechanisms to define requirements in a clear and precise manner. The intent is to update the conformance methods used and to separate conformance from the base standard.Since the last ballot of this material in 2020FEB , the following changes have been made: The profile XML schema has been removed from the specification and replaced with a link to the content.V2_CONFORM_R1_N1_2020FEB
Financial Management1538HL7 FHIR® Implementation Guide: Consumer-Directed Payer Data Exchange, Release 1- US RealmFHIR 1st STU BallotA FHIR R4 based implementation guide for an API similar to the FHIR R3 based CMS Medicare Blue Button 2.0 API that will allow consumer-directed exchange of commercial Health Plan/Payer adjudicated claims data to meet the requirements of the CMS Interoperability and Patient Access proposed rule.Since the last ballot of this material in 2020FEB , the following changes have been made: NONEFHIR_IG_BLUEBUTTON_R1_D1_2020FEB
Financial Management1517HL7 FHIR® Implementation Guide: Risk Based Contract Member Identification, Release 1 - US RealmFHIR 1st STU BallotThe purpose of this implementation guide is to define the mechanisms (protocols), data structures and value sets to be used for exchanging the Member Attribution Lists (MAL) between providers and payers. The list can be used by providers and payers to implement use cases for Value Based Contracts (VBC), Quality Reporting, Da Vinci Payer Data Exchange (PDex), Da Vinci Clinical Data Exchange (CDex) among others.Since the last ballot of this material in 2020FEB , the following changes have been made: N/AFHIR_IG_RISK_CONTRACT_R1_D1_2020FEB
Imaging Integration1392HL7 FHIR® Implementation Guide: FHIRcast, Release 1FHIR 2nd STU BallotThis STU proposes an addition to the current FHIRcast specification which will allow FHIRcast client applications (subscribers) to receive event notifications via a websocket connection, in addition to existing REST web service callback mechanisms.Since the last ballot of this material in 2020FEB , the following changes have been made: The proposed specification will adhere to the current FHIRcast specification in all cases, unless otherwise specified. All communication from client to server will conform to WebSub and FHIRcast REST API specifications. Only Hub notifications to the client will be over Websockets.
FHIR_IG_FHIRCast_R1_D2_2020FEB
Infrastructure and Messaging1516HL7 FHIR® Implementation Guide: Alerts, Release 1- US RealmFHIR 1st STU BallotThe first IG in the framework for notifications among patient's care team members, this IG focuses on the unsolicited notifications for admission and discharge events using FHIR messaging.Since the last ballot of this material in 2020FEB , the following changes have been made: First ballot roundFHIR_IG_ALERTS_R1_D1_2020FEB
Infrastructure and Messaging1562Reaffirmation of HL7 Version 3 Standard: Shared Messages Release 3V3 1st Normative BallotHL7 Version 3 Shared Messages are a work product produced for expressing common, useful and reusable message types. A Shared Message can be envisioned as a message type that is reusable in interactions in any of the domains within the HL7 standard. This document provides data on common messages such as acknowledgements shared across multiple domains.Since the last ballot of this material in 2020FEB , the following changes have been made: None: reaffirmationREAFF_V3_COMT_R3_N1_2020FEB
Infrastructure and Messaging1542Version 2 Guidance: Quality Criteria, Release 1V2X-Related 1st Informative BallotThis project is to develop and publish clear quality criteria for implementation guides using the Version 2 standard. The criteria will touch on the content of the documents (use cases, technical requirements, constraints applied according to conformance methodology, validity of message examples, etc) as well as the format of the document.Since the last ballot of this material in 2020FEB , the following changes have been made: First ballotV2_QUAL_CRIT_R1_I1_2020FEB
Orders and Observations1067HL7 Version 3 Domain Analysis Model: Laboratory Orders, Release 2HL7 1st Informative BallotThis document provides the artifacts that are relevant for the conceptual modeling, comparable to the Domain Analysis Model according to old methodology. The specification provides the foundation to progress development of a Laboratory Order template capability within Composite Order, as well as demonstrating the use of SAIF conceptual artifacts. Subsequent versions will elaborate the conceptual model and begin definition of the logical model.
Since the last ballot of this material in 2020FEB , the following changes have been made: Change from STU to Informative specificationHL7_DAM_LABORD_R2_I1_2020FEB
Orders and Observations1362Reaffirmation of HL7 Version 3 Standard: Implantable Device Cardiac - Follow-up Device Summary, Release 2V3 1st Normative BallotThe HL7 Version 3 Implantable Device Cardiac (IDC) Follow-up Summary is a message model for describing an observation of an interrogator at a physical location who is performing an interrogation of a therapeutic medical device (bound to a patient) using identifiable interrogation equipment.Since the last ballot of this material in 2020FEB , the following changes have been made: no changesREAFF_V3_IDC_R2_N1_2020FEB
Orders and Observations902HL7 Version 3 Standard: Orders; Diet and Nutrition, Release 1V3 1st Informative BallotThe HL7 v3 Nutrition Orders Standard – Universal Realm is a messaging specification intended to standardize the electronic transmission and exchange of nutrition orders including oral diets, enteral nutrition (tube feeding and infant formula requirements) and nutritional supplements in health care facilities across the continuum of care. Nutrition orders along with documented food allergies, intolerances and food preferences are required to safely provide inpatients or residents with nutritionaSince the last ballot of this material in 2020FEB , the following changes have been made: change from STU to informative levelV3_ORD_DIETNUT_R1_I1_2020FEB
Orders and Observations1009HL7 Version 3 Standard: Care Provision; Food and Medication Preferences, Release 1V3 1st Informative BallotThe HL7 v3 Care Provision – Nutrition and Drug Preferences is a messaging specification intended to support and standardize the exchange of patient and resident preferences related to foods and medications. This Universal standard provides a better way to communicate patient food and medication preferences among applications and providers and will help avoid situations which currently lead to preferences being reported as allergies.Since the last ballot of this material in 2020FEB , the following changes have been made: Change from STU to Informative SpecificationV3_PC_FMPREF_R1_I1_2020FEB
Orders and Observations1010HL7 Version 3 Specification: Ordering Service Interface, Release 1V3 1st Informative BallotThe Ordering Service complements existing SOA services and the SAIF Behavioural Framework (BF) for HL7. It provides a Service Functional Model (SFM) for ordering pharmacy, laboratory, radiology, consult and nutritional services individually or part of an order set. The Ordering Service supports interactive applications utilized by healthcare providers, and service-to-service interactions as might be required by a Clinical Decision Support system. Since the last ballot of this material in 2020FEB , the following changes have been made: Change from STU to InformativeV3_SPEC_ORDERSRVINT_R1_I1_2020FEB
Patient Administration1579Reaffirm HL7 Version 3 Standard: Patient Administration; Person Registry, Release 1V3 1st Normative BallotThe Person topic defines messages exchanged with Person Registries. The Person information model defines common identifying and demographic data elements that might be collected for persons regardless of the roles they play.Since the last ballot of this material in 2020FEB , the following changes have been made: No changes made to standard, reaffirmation.REAFF_V3_PA_PRSNREG_R1_N1_2020FEB
Pharmacy1543HL7 FHIR® Implementation Guide: Consumer-facing Real-time Pharmacy Benefit Check, Release 1- US RealmFHIR 1st STU BallotThis FHIR R4 based implementation guide for an API is similar to the NCPDP Real-Time Pharmacy Benefit Check B2B standard that will allow consumers access to the same information as their providers including information related to their cash price. This information includes formulary and benefit information, OOP costs, therapeutic alternatives, and cash price through an API that would be accessible by the consumer through a third-party application.
The final Medicare Part D rule for 2020 (https:
Since the last ballot of this material in 2020FEB , the following changes have been made: This is the initial version of the FHIR Implementation Guide to support consumer facing real time pharmacy benefit checks.FHIR_IG_RX_BENEFITCHECK_R1_D1_2020FEB
Public Health897HL7 Version 2.6 Implementation Guide: Critical Congenital Heart Defects (CCHD) pulse oximetry screening results, Release 1V26 2nd Normative BallotThis implementation guide will focus on standardizing on how CCHD newborn screening information is transmitted from a point of care device to an interested consumer such as public health.Since the last ballot of this material in 2020FEB , the following changes have been made: Apply changes resulting from the Sept 2018 ballot cycle, including the migration of authoring to the NIST IGAMT tool. As well, the look and feel of the IG will be updated to match more recently released v2 IGs.V26_IG_CCHD_R1_N2_2020FEB
Public Health898HL7 Version 2.6 Implementation Guide: Early Hearing Detection and Intervention (EHDI) Results, Release 1V26 2nd Normative BallotThis guide will focus on standardizing on how newborn hearing screening
information is transmitted from a point of care device to an interested consumer such as
public health
Since the last ballot of this material in 2020FEB , the following changes have been made: Apply changes resulting from the Sept 2018 ballot cycle, including the migration of authoring to the NIST IGAMT tool. As well, the look and feel of the IG will be updated to match more recently released v2 IGs.V26_IG_EHDI_R1_N2_2020FEB
Security914HL7 Version 3 Standard: Privacy and Security Architecture Framework, Release 1V3 4th Normative BallotThe Privacy and Security Architecture Framework (PSAF) Provenance Volume 3 is the remaining PSAF volume to be balloted as normative. This ballot rectifies approved disposition changes from the September 2019 ballot including clarification that scope includes both enterprise and federated architectures, the normative vs. informative portions, and various simplifications and corrections noted by commenters. It does not extend the substantive content beyond responding to September ballot comments.Since the last ballot of this material in 2020FEB , the following changes have been made: Changes include clarification that scope includes both enterprise and federated architectures, the normative vs. informative portions, relationship to other Provenance standards, and various simplifications and corrections noted by commenters.V3_PSAF_R1_N4_2020FEB
Services Oriented Architecture1420HL7 Model-based Transformation Service, Release 1HL7 1st STU BallotThis document provides a general platform independent Service Functional Model (SFM) specification for an HL7 model-based bi-directional transformation service with exemplary mappings illustrating typical usage. The scope of the SFM is limited to the exchange of data between a source and a target where the source and target are different HL7 Standards (V2, CDA, FHIR). Since the last ballot of this material in 2020FEB , the following changes have been made: Since the previous informative ballot, additional use cases and the Service Functional Model specification for operation and adminstration have been added along with additional mapping formalisations and exemplars. HL7_MODEL_XFORM_R1_D1_2020FEB
Structured Documents977HL7 CDA® R2 Implementation Guide: Questionnaire Response Document, Release 1CDA 3rd Normative BallotThis ballot is for an implementation guide defining
Questionnaire Response Document for purpose of
representing patient responses to questionnaires as a
structured document reusing and/or enhancing existing
CDA templates where possible creating new CDA
templates where necessary.
Since the last ballot of this material in 2020FEB , the following changes have been made: This is the second Normative ballot for this document.
The changes made to the document reflect the resolutions
that were agreed to by the working group. Both substantive
and non-substantive changes were made. As this is the
second Normative ballot for this IG, the ballot comments are
limited to only the substantive changes. The substantive
changes were due to the following N1 comments:
2, 5, 8.
Comments during this second (N2) ballot are resticted to
those (subsantive) changes only. The corresponding final
reconciliation spreadsheet can be found here:
https://wiki.hl7.org/w/images/wiki.hl7.org/3/31/CDAR2_IG_QRDOC_R1_N2_FinalReconciliationSpreadsheet_Oct.31.2019.xls
CDAR2_IG_QRDOC_R1_N3_2020FEB
Structured Documents976HL7 CDA® R2 Implementation Guide: Structured Form Definition Document, Release 1CDA 2nd Normative BallotThis ballot is for an implementation guide defining a
Structured Form Definition Document for purpose
of representing patient questionnaires as a structured
document reusing and/or enhancing existing CDA templates
where possible creating new CDA templates where necessary.
Since the last ballot of this material in 2020FEB , the following changes have been made: This is the second Normative ballot for this document.
The changes made to the document reflect the resolutions
that were agreed to by the working group. Both substantive
and non-substantive changes were made. As this is the
second Normative ballot for this IG, the ballot comments are
limited to only the substantive changes. The substantive
changes were due to the following N1 comments: 1, 7, 11,
21, 25, 28, 29, 32, 33, 34, 35, 36, 37, 38, 39, 45, 46, 47.
Comments during this second (N2) ballot are resticted to
those (subsantive) changes only. The corresponding final
reconciliation spreadsheet can be found here:
http://wiki.hl7.org/images/5/50/CDAR2_IG_SFDEFDOC_R1_N1_2017JAN_amalgamated_January042018-FINAL_Jan292019.xls
CDAR2_IG_SFDEFDOC_R1_N2_2020FEB


For more information on ballot procedure, such as general guidelines, and voting, see Ballot Procedures and Guidelines

For Help, see Balloting Help

  • No labels