My enhancement now extends support beyond VSAC, enabling the use of FHIR-compliant terminology servers for private or custom-defined Value Sets. This added feature allows healthcare organizations to leverage their own FHIR-based terminology repositories, improving flexibility for institutions that need localized or proprietary clinical vocabularies while maintaining compliance with existing standards. Users can specify a FHIR Base URL to direct queries toward non-VSAC terminology servers, ensuring broader accessibility to domain-specific terminologies.
Clinical Query Language (CQL) is a flexible, domain-independent query language designed to support clinical decision-making by enabling intuitive and standardized queries without requiring extensive technical knowledge. It works with any data model, integrates with widely used programming languages, and relies on the Expression Logical Model (ELM) as an intermediary format to ensure consistency with existing healthcare data standards. The open-source CQL-to-ELM Translator, built in Java, facilitates seamless execution of CQL queries by converting them into ELM representations, supporting various customization options and integrating with FHIR, QDM, and QUICK models to enhance clinical data interoperability.
Clinical Query Language (CQL) is a high-level query language to represent and generate unambiguous quality measures or clinical decision rules. I am not a CQL expert. These are my notes from a system development perspective. I am trying to make sense of this emerging concept and add my notes here in the hope that others may find this useful.
U.S. Navy photo by Chief Warrant Officer 4 Seth Rossman. / Public domain (wikimedia)
Clinical Query Language is designed to be intuitive for clinicians authoring the queries for quality measures and clinical decision support. The decision support rules are mostly alert type rules at the individual and population level that is calculated from a database (not usually diagnostic decision support). You can use any data model with CQL.
Here is an example segment of CQL:
define “InDemographic”: AgeInYearsAt(start of MeasurementPeriod) >= 16 and AgeInYearsAt(start of MeasurementPeriod) < 24 and “Patient”.”gender” in “Female Administrative Sex”
As Clinical Query Language follows strict semantics, you can autogenerate lexers, parsers and visitors using ANTLR. In simple terms, CQL’s semantics can be represented as a ‘grammar’ that ANTLR can read and generate code to process any CQL in a variety of programming languages, including Java, Javascript, Python, C# and Go. The CQL grammar files are here: https://cql.hl7.org/08-a-cqlsyntax.html. Incidentally, CQL grammar inherits from fhirpath.
If you wish to generate code from these files, there are two things to note:
You need to rename CQL.g4 to cql.g4 as the library names are case-sensitive and should correspond to the filename.
Put fhirpath.g4 in the same folder as cql.g4, and cql refers to fhirpath grammar.
Clinical Query Language aims to provide a high-level domain-independent language for clinicians that can be translated into low-level database logic. As CQL does not prescribe a data model, an intermediary format linking CQL to the data management logic is required. That is called the Expression Logical Model (ELM) which we will discuss in part 2.
Update: cql-exec-vsac is a VSAC-enabled code service for the JavaScript CQL Execution project. This allows the CQL Execution Engine to execute CQL containing references to Value Sets that are published in the National Library of Medicine’s (NLM) Value Set Authority Center (VSAC). I have added a feature that adds support for any FHIR server other than VSAC to support private terminology servers. Check it out!
