Since announcing CQL Tests UI, the application has continued to receive enhancements that add the ability to execute new test runs yourself using the official CQFramework-family of CQL tests.
What’s New: The Runner Integration
The upcoming release introduces a complete CQL Test Runner integration that will allow users to execute CQL compliance tests directly from the web interface. No more switching between tools or managing configuration files manually.
Key Features Added
Live Test Execution: The new runner component will let you configure and execute the separately-running CQL test runner service against any CQL-capable FHIR server with a few clicks. Tests will run asynchronously in the background via the test runner, and results will be reported via the UI where they can be seamlessly loaded into the existing viewer.
Flexible Configuration: The interface provides a user-friendly way to configure FHIR server endpoints, build settings, and test parameters. For power users, there will be a full JSON editor with syntax highlighting.
Separate Deployment: The CQL Test Runner itself will operate as a separate service that needs to be deployed independently. It will be released as a Docker container.
Results Integration: Once tests complete, you’ll be able to immediately view results in the existing results viewer or download them as JSON. The integration will be seamless – test results will flow directly into the visualization tools you’re already familiar with.
Looking Forward
As the project continues to evolve, I’d personally like to see CQL Tests UI grow into an even more full-featured CQL authoring environment. There is exciting potential to combine or align with efforts from the CDS Connect Authoring Tool Community Edition, bringing together the best of test execution and authoring capabilities in a single, user-friendly interface.
Please share your thoughts with me via the GitHub repository, the FHIR Zulip community, or during the HL7 CQI and HL7 CDS working group calls.
Leave a Reply