Clinical Decision Support
Project Summary for Clinical Quality Expression Language
Visit Project Insight to see the full project details.
Project Details
Number | 1108 View Ballot Items List (with NIBs) |
---|---|
Name | Clinical Quality Expression Language |
Sponsor(s) | Clinical Decision Support Work Group |
Co-Sponsor(s) | Clinical Quality Information Work Group, Implementable Technology Specifications Work Group |
Steering Division | Clinical |
Description | This project will define a common canonical representation of expression logic for clinical quality drawing on the requirements of the Quality Data Model (QDM), Health Quality Measure Format (HQMF), Clinical Decision Support Knowledge Artifact Specification (CDS KAS), and the conceptual requirements established in Health Quality Reasoning and Expression Logic specification. This project will also define a serialization mechanism for that canonical representation to enable point-to-point sharing of clinical knowledge. In addition, the project will define a 'conformance profile' consisting of a human-readable syntax targeted for measure and decision support artifact authors that can then be translated into the canonical representation. The canonical representation will be defined as a logical model with an accompanying ITS describing how it can be serialized using a specific interchange technology such as XML. The conformance profile syntax will be defined using the ANTLR4 grammar framework. The project is also expected to include tooling to support language processing applications with the resulting canonical representation, as well as the high-level syntax. |
Project Facilitator | Bryn Rhodes |
Status | Archived |
SD Approval Date | May 23, 2014 |
TSC Approval Date | Jul 28, 2014 |
Project Type | Ballot - STU to Normative |
Objectives / Deliverables | Develop syntax and supporting tooling - Target: 2014 Jun Submit for Comment Only Ballot - Target: 2014 Sep Ballot Complete Comment Only Reconciliation - Target: 2014 Sep WGM Submit for DSTU Ballot - Target: 2015 Jan Ballot Complete DSTU Ballot Reconciliation - Target: 2015 Jan WGM Pilot artifacts using the syntax and tooling - Target: 2014 Jun DSTU Updates - Target: 2015 Jan - 2017 Jan DSTU Period - 24 months - Target: 2015 Jan - 2017 Jan STU Update and Extension to incorporate feedback from quality artifact authors - Target: 2017 Jan - 2018 Jan STU 3 Ballot to incorporate additional feedback - Target: 2018 May Ballot Complete STU 3 Ballot Reconciliation - Target: 2018 May WGM Publish STU 3 - Target: 2018 Jun Continue supporting implementation and testing - Target: 2018 Jun - 2018 Dec Submit for Normative Ballot - Target: 2019 Jan Ballot Complete Normative Reconciliation - Target: 2019 Jan WGM Submit Publication Request - Target: 2019 Feb Receive ANSI Approval - Target: 2019 Mar Project End Date - Target: 2019 Mar |
Next Milestone Date | 2022 September WGM |
Project End Date | 2023 January WGM |
Project Intent | Create New Standard |
Project Need | Although several standards exist for the expression of clinical quality logic, these standards are not widely adopted, and present various barriers to point-to-point sharing of clinical knowledge artifacts such as lack of tooling, complexity of implementation, or insufficient expressivity. For a more in-depth discussion of the evaluation and analysis of the various candidate standards involved, please refer to the associated Health eDecisions Research History document. Rather than attempt to address these shortcomings in one of the available syntaxes, we propose that the solution is to enable shared understanding by defining a syntax-independent, canonical representation of the logic involved in any given artifact, and point-to-point sharing by defining a serialization for that representation. The canonical representation would be informed conceptually by the requirements of the clinical quality domains of measurement and improvement; and technically by compiler design best practices. The resulting canonical representation would provide a basis for sharing logic in a way that is at once verifiable, computable, and serves as the input to language processing applications such as translation, tooling, or even execution engines. In addition, a high-level domain specific language focused on clinical quality and targeted at measure and decision support artifact authors that can then be rendered in this canonical representation is needed because none of the existing syntaxes are suitable for clinical domain expert use. |
Success Criteria | |
Dependancies | |
Collaboration Efforts | |
Ballot Cycle Info | 2020 May Ballot Cycle Info: NORMATIVE Ballot results: Met basic vote requirements. 12 Negatives to reconcile Document Name: HL7 Cross-Paradigm Specification: Clinical Quality Language, Release 1 2019 May Ballot Cycle Info: STU Ballot results: Met basic vote requirements. 8 Negatives to reconcile Document Name: HL7 Cross-Paradigm Specification: Clinical Quality Language, Release 1 2018 May Ballot Cycle Info: STU Ballot results: Did not meet basic vote requirements. Document Name: HL7 Cross-Paradigm Specification: Clinical Quality Language, Release 1 2017 Jan Ballot Cycle Info: STU Ballot results: Met basic vote requirements. 5 Negatives to reconcile Document Name: HL7 Cross-Paradigm Specification: Clinical Quality Language, Release 1 Submitter: Lynn Laakso MPA 2015 Jan Ballot Cycle Info: DSTU Ballot results: Met basic vote requirements. 7 Negatives to reconcile Document Name: HL7 Standard: Clinical Quality Language, Release 1 - US Realm 2014 Sept Ballot Cycle Info: COMMENT ONLY Ballot results: Met basic vote requirements. 5 Negatives to reconcile Document Name: HL7 Version 3 Standard: Clinical Quality Expression Lanaguage, Release 1 (HL7 Standard: Clinical Quality Language) Submitted By: Kensaku Kawamoto |
Misc Notes | 2020 Dec: Received ANSI approval for HL7 Cross-Paradigm Specification: Clinical Quality Language, Release 1. PMO archiving project. 2020 Nov: TSC approved STU Extension Request for HL7 Specification: Clinical Quality Language (CQL), Release 1, STU3 for 2 years 2020 Sept: TSC approved Normative publication request for HL7 Cross-Paradigm Specification: Clinical Quality Language, Release 1 2020 March: TSC approved Normative Notification for Clinical Quality Expression Language 2018: TSC approved STU Publication Request for HL7 Cross-Paradigm Specification: Clinical Quality Language, Release 1 at TSC Tracker 17883 thru September 20, 2020 2018 February: BRhodes sent updated dates via a revised PSS. 2017 June: The TSC approved STU Publication Request for HL7 Cross-Paradigm Specification: Clinical Quality Language, Release 1 at TSC Tracker 13523 through 2018-07-10 July 2016: TSC approved The Unballoted DSTU Update Publication Request for HL7 Cross-Paradigm Specification: Clinical Quality Language, Release 1.1 at TSC Tracker 10115 through May 20, 2017. HL7 Standard: Clinical Quality Langauge Specification, Release 1 in DSTU through May 20, 2017 April 2014: Work Group submitted DSTU publication request New Product Definition Notes: This project will extract the expression language definition components of the CDS Knowledge Artifact Specification into a new specification that can be referenced independently, and which will serve as a mechanism for serialization of expression logic. The resulting specification will then be expanded to define CQL syntax, a high-level clinically-focused expression language that can be used to directly author logic for measures and decision support rules. This expression language will be a one-to-one mapping with the XML representation, and so will support translation directly to and from the XML. |
Product Type | - New Product Definition - |
Project Document Repository | http://wiki.hl7.org/index.php?title=Clinical_Quality_Language |
Backwards Compatibility | N/A |
Stakeholders | Quality Reporting Agencies |
Vendors | EHR, PHR; Health Care IT |
Providers | Healthcare Institutions (hospitals, long term care, home care, mental health) |
SDO/Profilers | |
Realms | Realm Specific - Enter "U.S." or name of HL7 Affiliate below |
HL7 Affiliate | U.S. |
Roadmap Reference | |
Start Date | May 14, 2014 |
* A Project Insight User ID and password is required to access Project Insight. Contact the HL7 PMO at pmo@HL7.org for more information.
Visit the Projects, Ballots and Standards Metrics Excel Report to view projects that are behind 120+ days along with other ballots and standards requiring a Work Group's attention.
Visit the Projects, Ballots and Standards Metrics Excel Report to view projects that are behind 120+ days along with other ballots and standards requiring a Work Group's attention.