Development Roadmap

Our planned features and milestones for CQL Studio.

  • Initial Release - Core CQL editing and execution
  • Engine Testing Suite - Comprehensive CQL engine test runner and reporting tools
  • Basic IDE Features - Syntax highlighting and error detection
  • Local and Hosted Deployment - Flexible deployment options for local development and cloud-hosted environments
  • Terminology Integration - Integration FHIR terminology servers for value set and code system integration
  • CQL Validation and ELM Translation - Integration validation errors and on-demand ELM translation
  • Patient-Specific Context Testing - Testing CQL with patient-specific data contexts
  • Live CQL Testing - Seamless CQL execution with FHIR CQL engines
  • Basic AI Integration - Simple BYOLLM support for AI-assisted CQL development

  • Direct VSAC Integration - Search and import value sets used in the U.S.
  • AI-Assisted Drafting - CQL generation from clinical narrative and human content
  • FHIR Registry Integration - In-app search and import of FHIR profiles, value sets, and data directly from FHIR registries
  • Experimental "SQL on FHIR" - Bypass CQL engines and run measures via in-browser SQL queries with embedded PGlite and WASM.
  • Measure Development - FHIR Measure and MeasureReport editors for authoring and testing of CQL-based clinical quality measures
  • AI Rich Context and Orchestration - Stronger AI support with IDE-wide awareness
  • AI Web Search Support - Opt-in support for web search and retrieval of information from the web
  • AI External MCP Support - Integration with Model Context Protocol for AI-assisted development

  • Multi-Engine Delta Testing - Support for multiple concurrent CQL engines
  • Plugin System - Extensible architecture for custom functionality
  • Strict Best Practices for Authoring - Lint-like guidance and recommendations for effective, conventionalized CQL authoring
  • CRMI Package Export and Publication - Support for CRMI packaging and publication workflows

  • Alignment with CMS MADiE - TBD - Likely to focus on artifact and package import/export cross-compatibility and registry support.
  • Terminology Endpoint Routing - Support for automatic routing of terminology requests to multiple terminology servers, pending specification updates
  • FHIR Library-Specific Engine Compatibility Reporting - Engine compatibility reporting for FHIR Library resources
  • Application Extensions - Support for pluggable non-standard FHIR extensions
  • Private FHIR IG-Specific Features - Features tailored for private FHIR Implementation Guide conformance