A calculator that accounts for every patient
The OpenDQM calculator runs the published dQM packages against real EHR exports, and for every patient it does not count, says which data was missing and who owns the fix. The big idea, in plain words →
A calculator that accounts for every patient
The OpenDQM calculator runs the published dQM packages against real EHR exports, and for every patient it does not count, says which data was missing and who owns the fix. The big idea, in plain words →
Written from production experience
Vendor documentation tells you what an API accepts. Recipes tell you what it actually returns, what it silently leaves out, and how to check.
Organised by EHR and measure
Every recipe names the EHR, the measures it supports, who contributed it and when it was last verified — so you can tell what is current.
Community-maintained
Recipes come from developers at many organisations. Found a better way, or a vendor change? Send it in.
No PHI, ever
Examples use synthetic data and public vendor sandboxes only. See the content rules.