Skip to content
OpenDQM

Roadmap

Today

Section titled “Today”

Four measures across two engines, against every published test case for those measures:

  • CMS122, CMS125 and CMS130 on fqm-execution;
  • CMS122, CMS125 and CMS165 on HAPI FHIR Clinical Reasoning.

Also working: a Bulk Data loader, a profile-declaration tool, a ConceptMap proposer and a reviewer gate.

Minimum viable product, February 2027

Section titled “Minimum viable product, February 2027”
  • Ten dQMs, including the ACO quality measure set. Each has a differential comparison against a Cypress-certified production calculator.
  • The HL7 validator in the pipeline.
  • A retrieve tracer that names the empty retrieves and missing elements behind every zero.
  • The bias report and an owner-routed feed of findings.
  • Signed rule sets for two ambulatory EHR platforms.
  • Fault-injected copies of the published test decks for each observed defect class, drawn from 15 EHR platforms.
  • A governance charter covering signer scope, liability and how findings about vendors are disclosed.
  • Public open-source release of the core, the conformance harness and the test decks.

Later, by September 2027

Section titled “Later, by September 2027”
  • The full converted set of about 70 measures.
  • The first hospital data source, which needs inpatient encounter, medication-administration and discharge data that ambulatory exports do not carry, and a facility partner.
  • Multi-tenant isolation and a third ambulatory platform.

Who runs it

Section titled “Who runs it”
  • An organisation with technical staff installs the container.
  • A registry or accountable care organisation (ACO) operates it for its members.
  • A neutral reference instance would give implementers an arbiter when they disagree, and a channel that returns defects to measure stewards.

Attribution, eligibility and submission stay outside the calculator. They are program rules.

Risks

Section titled “Risks”
  • Engine defects. Both engines have defects. Fixes not accepted upstream are carried as manifest entries.
  • Package collisions. Two packages publish value sets under one canonical URL with different ids. Loading CMS122 beside CMS125 broke 15 of 55 cases. For the MVP, the answer is to isolate each measure.

Security and privacy

Section titled “Security and privacy”

The calculator runs inside the data owner’s boundary, under HIPAA. Its conformance evidence is synthetic by design and can be shared without patient data.