Quality Measures Engine
Overview
Quality measures are core infrastructure for value-based care, but most HEDIS workflows still rely on expensive vendor implementations, brittle extracts, or opaque logic. Quality Measures Engine puts certified measure calculation directly in your warehouse, on top of the same Tuva data model your team already uses for analytics.
Because the package is built for Tuva, teams already running Tuva do not need a separate data integration project. Install the package, run it, and start working with patient-level measure and care gap outputs.
What You Get
- NCQA-certified HEDIS measure calculation directly on top of the Tuva data model
- Patient-by-measure outputs for initial population, exclusions, numerator inclusion, and open care gaps
- Granular data in your warehouse for provider, population, contract, and patient-level analytics
- Warehouse-native dbt package deployment with no separate SaaS platform to manage
- Transparent annual pricing where you pay per measure
Who This Is For
- Health plans, ACOs, and risk-bearing providers that need NCQA-certified HEDIS measures
- Teams already running Tuva that want to calculate measures in minutes with no data integration work
- Organizations not yet on Tuva that want a warehouse-native measure engine and can map data to the required inputs
- Analytics teams that need atomic care gap data, not just measure-level rollups
What the Engine Produces
The engine produces the most granular measure output: every relevant patient, every measure, and the exact flags needed to understand measure status. For each patient-measure combination, you can see whether the patient qualified for the initial population, which exclusions applied, whether numerator criteria were met, and whether the measure is an open care gap.
With that atomic data in your warehouse, your team can build any analytics you need: which patients have open care gaps, how performance changes by provider or population, and how closing specific gaps would improve a provider's measure performance.
Quality Measures Engine vs Traditional HEDIS Workflows
| Category | Quality Measures Engine | Traditional HEDIS Workflows |
|---|---|---|
| Deployment | Run the package in minutes when your data is already in Tuva | Separate implementation and integration work |
| Data integration | No integration work for existing Tuva users | Custom extracts, mappings, and vendor handoffs |
| Outputs | Atomic patient-by-measure data for populations, exclusions, numerators, and care gaps | Often limited rollups or opaque exports |
| Analytics | Slice care gaps, provider impact, populations, and measure performance inside your warehouse | Analytics limited by vendor UI or export format |
| Pricing | Simple annual fee where you pay per measure | Broad contracts that can easily reach $500K to $1M+ |
Trademark Notice
HEDIS is a registered trademark of the National Committee for Quality Assurance (NCQA). Quality Measures Engine is not affiliated with or endorsed by NCQA.