Trekker voor Nederland
|Advies van trekker|
Pool enrollment opens
Pool enrollment closes
|Clinical Quality Information||1499||HL7 FHIR® Implementation Guide: Quality Measures, Release 1- US Realm|
Requesting alternate ballot title "FHIR Quality Measure IG"
|FHIR||1st STU Ballot||FHIR Clinical Reasoning provides infrastructure requirements for representing a health quality measure as an electronic format. A quality measure is a quantitative tool to assess the performance of an individual or organization’s performance in relation to a specified process or outcome via the measurement of an action, process, or outcome of clinical care.||William Goossen||2019/02/25||2019/03/28|
|Electronic Health Records||1445||Reaffirmation of HL7 EHR Behavioral Health Functional Profile, Release 1||EHR||1st Normative Ballot||This is a reaffirmation ballot for an existing standard that needed to be renewed. |
This HL7 EHR Behavioral Health Functional Profile (EHR BH FP) contains the functions and conformance criteria deemed important for behavioral health care providers' clinical records systems. At a minimum, this profile provides a shopping list of capabilities a behavioral health provider should consupports treatment processes and efficiencies for behavioral health, mental health and substance abuse organizations
|Anneke, William Goossen||Affirmative||2019/02/25||2019/03/28|
|Electronic Health Records||1446||Reaffirmation of HL7 EHR Child Health Functional Profile, Release 1||EHR||1st Normative Ballot||This is a reaffirmation ballot of an existing standard. The HL7 Child Health Functional Profile for EHR Systems (Child Health Profile) is designed to assist children's healthcare providers and associated IT vendors to create functionality that ensures safe and reliable care of children through the effective use of information technology.||Anneke, William Goossen||Affirmative||2019/02/25||2019/03/28|
|Electronic Health Records||1447||Reaffirmation of HL7 EHR Clinical Research Functional Profile, Release 1||EHR||1st Normative Ballot||This is a reaffirmation ballot for an existing standard.The EHR Clinical Research Functional Profile (EHR CR FP) provides high-level functional requirements necessary for using electronic health record (EHR) data for regulated clinical research.||Anneke, William Goossen||Affirmative||2019/02/25||2019/03/28|
|Orders and Observations||1444||Reaffirmation of HL7 Version 3 Standard: Clinical Statement Pattern, Release 1||V3||1st Normative Ballot||This as an re-affirmation ballot on the Clinical Statement Pattern Release 1 to continue the ability to reference the content from other HL7 V3 standards and implementation guides.||Anneke Goossen||Affirmative||2019/02/25||2019/03/28|
|Structured Documents||977||HL7 CDA® R2 Implementation Guide: Questionnaire Response Document, Release 1||CDA||2nd Normative Ballot||This 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 2017JAN , 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, 2, 3, 4, 5, 6, 7, 9, 10, 11, 13, 16, 18, 31, 56, 60.
Comments during this second (N2) ballot are resticted to
those (subsantive) changes only. The corresponding final
reconciliation spreadsheet can be found here:
|Anneke, William Goossen||Affirmative||2019/02/25||2019/03/28|
|Orders and Observations||1238||HL7 Domain Analysis Model: Unique Device Identifier (UDI) Implementation Guidance, Release 1||HL7||3rd Informative Ballot||The focus of this ballot is to address the implantable |
devices unique identification needs and support for implantable device list (e.g. Meaningful Use 2015 certification requirements).Since the last ballot of this material in 2018JAN , the following changes have been made: This version addresses the comments received in the first
|Roel Barelds||Negative |
|Security||914||HL7 Version 3 Standard: Privacy and Security Architecture Framework, Release 1|
Requesting alternate ballot title "HL7 Version 3 Standard: Privacy and Security Architecture Framework (PSAF)"
|V3||2nd Normative Ballot||The Privacy and Security Architecture Framework (PSAF) is comprised of: Volumes 1 and 2, Trust Framework for Federated Authorization conceptual and behavioral models; |
Volume 3 Provenance, which addresses topics needed for trustworthy information exchange; and Volume 4 Audit, which provides a conceptual model for the audit service interfaces. These volumes form the basis of HL7 implementable privacy and security specifications. Only Volumes 3 and 4 are in scope for comments.
Since the last ballot of this material in 2018MAY , the following changes have been made: PSAF Volume 3 Provenance changes: Clarification on architecture's concept of a Federated Provenance Domain and capabilities for tracking the trustworthiness of participant's submission of discoverable provenance to that domain. PSAF Volume 4 Audit is a refactoring of the PASS Audit Conceptual Model, which passed normative ballot in 2017. The previous Audit specification missed the publication deadline of one year after approval as normative, and therefore required reballoting.
|Financial Management||1428||HL7 FHIR® Implementation Guide: Coverage Requirements Discovery, Release 1 - US Realm||FHIR||2nd STU Ballot||In the US clinicians are often unaware of the expectations of payor organizations around care delivery, requirements for pre-authorizations and other processes. This results in denied payment, changes to therapy after initiation and/or additional overhead costs are incurred. Defining a standardized mechanism by which care delivery organizations and providers can query payors to find relevant guidance prior to care delivery will increase efficient delivery of care and corresponding payment.|
Since the last ballot of this material in 2018SEP , the following changes have been made: Changes were made throughout the guide to respond to comments made during the prior ballot period "Ballot for Comment".
|FHIR Infrastructure||1390||HL7 FHIR® Implementation Guide: Structured Data Capture (SDC), Release 2||FHIR||1st STU Ballot||SDC provides guidance on how to use Questionnaire and QuestionnaireResponse for more sophisticated questionnaires, such as are used in the research, payment, public health and other areas. It includes controls over rendering, data entry, calculations, population from existing data, converting questionnaire responses to other FHIR resources and describes how to produce adaptive questionnaires.|
Since the last ballot of this material in 2018SEP , the following changes have been made: The updated SDC specification changes expectations for population and introduces extraction and adaptive questionnaire capabilities. It lightens expectations for conformance and provides additional rendering and calculation capabilities.
|FHIR Infrastructure||1433||HL7 FHIR® Implementation Guide: Patient Reported Outcomes (PRO), Release 1 - US Realm||FHIR||1st STU Ballot||The Patient Reported Outcomes (PRO) FHIR Implementation Guide (IG) will focus on capturing and exchanging patient reported outcome data electronically using the FHIR standard. The data that is captured will be made available to both providers and authorized researchers. While the PRO FHIR IG can be applied to multiple use cases, the current requirements have been drawn from PCORnet use cases and implementations.|
Since the last ballot of this material in 2018SEP , the following changes have been made: The version of the IG is backwards compatible with the previous version of the IG. The IG is built on the latest release of FHIR namely R4. The changes from the previous version to the current version including clarifying various parts of the IG based on ballot comments received, adding examples and updating implementation guidance for developers.
|Anneke, William Goossen||abstain||2019/02/25||2019/03/28|
|Clinical Quality Information||1429||HL7 FHIR® Implementation Guide: Data Exchange for Quality Measures, Release 1 - US Realm||FHIR||2nd STU Ballot||This 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 2018SEP , the following changes have been made: This ballot 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.
|Anneke, William Goossen||abstainAffirmative||2019/02/25||2019/03/28|
|Publishing||773||HL7 Version 2.9 Messaging Standard||V29||5th Normative Ballot||This is another ballot for V2.9 Normative edition with reconciled comments from the previous ballot cycle of Jan. 2019.|
Since the last ballot of this material in 2019JAN , the following changes have been made: This is another ballot for V2.9 Normative edition with reconciled comments from the previous ballot cycle of Jan. 2019.