cqframework / cql-tests Goto Github PK

1.0 6.0 3.0 93 KB

Clinical Quality Language Tests Repository

License: Apache License 2.0

cql-tests's Introduction

CQL Tests Repository

This repository contains a suite of test cases for Clinical Quality Language that allow implementations to determine the correct expected behavior of CQL language capabilities. The tests here were initially copied from the informative test cases published as part of the CQL specification.

Github permalink to initial source

Test Case Format

The test cases are expressed in an XML format that is common across the FHIRPath and CQL specifications, documented in the XML Schema file:

Test Schema

Change Management

Changes to the tests maintained within this repository are managed using as lightweight a process as possible, while still ensuring stable, viable, production quality software. These processes are described in the Change Management topic.

Documentation

Documentation for this repository is maintained in the wiki

cql-tests's People

Contributors

Stargazers

Watchers

Forkers

marciantemark suyashkumar evan-gordon

cql-tests's Issues

Epic: Date/Time Functions (section 18 of the "Logical Specification" in the CQL Spec)

https://cql.hl7.org/2020May/04-logicalspecification.html

Epic: Conditional Functions (section 15 in CQL Spec)

This is an Epic to collect all issues related to conditional functions in CQL spec (section 15)

Epic: List Functions (section 20 of the "Logical Specification" in the CQL Spec)

https://cql.hl7.org/2020May/04-logicalspecification.html

Proposal for Multi-Library, Multi-Resource Tests

This is based off of a discussion we had at the spring 2024 HL7 Connectathon.

The group discussed at length about adding the ability to run tests that support multiple libraries as well as accepting input resources. Since the current tests only support single statements we cannot currently test features like valuesets or the code in valueset feature. Other features like fluent functions would also be benefitted by this feature.

The team discussed a potential format for defining a test group that overcomes these and other existing gaps and came up with the following example json. The following is an example meta file for defining the inputs to a test runner which would be needed to run one of these tests and also like the associated file outputs to be asserted on.

testGroupName.json

{
  "description": "...",
  "cqlLibraries": [
    "testFile.cql"
  ],
  "resources": [
    "patient.json"
  ],
  "valuesets": [
    "valueset.json"
  ],
  "outputFile": "output.json"
}

For the output file we as a team discussed using the json definition defined here https://github.com/cqframework/clinical_quality_language/wiki/CQL-Serialization for the expected output format.

This is intended to be a "holder" for all issues that are related to comparison functions as defined in section 12 of the the logical specification https://cql.hl7.org/2020May/04-logicalspecification.html Here are some notes:
https://github.com/FirelyTeam/firely-cql-sdk/wiki/Specification-Test-Nonconformity-&-Notes