This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Clinical Quality Language"

From HL7Wiki
Jump to navigation Jump to search
 
(14 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
 
+
Return to [[Clinical_Decision_Support_Workgroup|Clinical Decision Support Work Group]]
Return to [[Clinical_Decision_Support_Workgroup]]
 
  
 
Project Co-Sponsors:
 
Project Co-Sponsors:
*[[Clinical_Quality_Information_Work_Group]]
+
*[[Clinical_Quality_Information_Work_Group|Clinical Quality Information Work Group]]
  
 
==Project Information==
 
==Project Information==
  
 
[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=view&ProjectNumber=1108 Project Insight 1108] Entry
 
[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=view&ProjectNumber=1108 Project Insight 1108] Entry
 +
 +
CQL Repository
 +
[https://github.com/cqframework/clinical_quality_language Clinical Quality Language GitHub Repository]
 +
 +
CQL Page on the eCQI Resource Center
 +
[https://ecqi.healthit.gov/cql CQL Resources]
  
 
==Meeting Information==
 
==Meeting Information==
*[http://www.hl7.org/concalls/CallDetails.aspx?concall=25050|Weekly Office Hours]
+
Clinical Quality Language comments and issues are discussed on a regular basis in the CDS WG weekly meeting.
 +
 
 +
==Status==
 +
The Clinical Quality Language Specification has passed a second round of balloting and is published as an STU 2 specification by HL7. The publication package is available to HL7 members [http://www.hl7.org/implement/standards/product_brief.cfm?product_id=400 here].
  
The Clinical Quality Language Team hosts a weekly "Office Hours" call to support community efforts to use CQL in pilot or prototypical implementations.
+
The STU comments page for the publication is available [http://www.hl7.org/dstucomments/showdetail.cfm?dstuid=211 here].
  
 +
Errata and change requests dealing with the specification should be submitted as STU comments at the above link. The Clinical Decision Support Work Group will review and discuss STU comments as needed.
  
==Status==
+
The current plan for the specification is to ballot as normative in the May 2018 cycle. Should the need for critical updates arise prior to that publication, the STU update process will be considered.
The Clinical Quality Language Specification has passed the DSTU ballot and has been submitted to HL7 for publication.
 
  
The final reconciled ballot spreadsheet is available [https://docs.google.com/spreadsheets/d/16z1ZfHC4n_EqKA1hFooUTOjTEWlyZdWq88KvmrHk-BQ/edit?usp=sharing here].
+
Issues related to the associated tooling should be submitted as Issues on the GitHub site: [https://github.com/cqframework/clinical_quality_language/issues CQL GitHub Issues]
  
 
==Project Documents==
 
==Project Documents==
A brief introductory presentation to CQL can be found here.
+
A brief introductory presentation to CQL can be found [http://wiki.hl7.org/index.php?title=File:CQL_Introduction_20150428.pptx here].

Latest revision as of 22:43, 28 September 2017

Return to Clinical Decision Support Work Group

Project Co-Sponsors:

Project Information

Project Insight 1108 Entry

CQL Repository Clinical Quality Language GitHub Repository

CQL Page on the eCQI Resource Center CQL Resources

Meeting Information

Clinical Quality Language comments and issues are discussed on a regular basis in the CDS WG weekly meeting.

Status

The Clinical Quality Language Specification has passed a second round of balloting and is published as an STU 2 specification by HL7. The publication package is available to HL7 members here.

The STU comments page for the publication is available here.

Errata and change requests dealing with the specification should be submitted as STU comments at the above link. The Clinical Decision Support Work Group will review and discuss STU comments as needed.

The current plan for the specification is to ballot as normative in the May 2018 cycle. Should the need for critical updates arise prior to that publication, the STU update process will be considered.

Issues related to the associated tooling should be submitted as Issues on the GitHub site: CQL GitHub Issues

Project Documents

A brief introductory presentation to CQL can be found here.