Proof of open and closed care gaps.
A HEDIS measure engine returns every result as a FHIR MeasureReport with the population math attached — open gaps actionable, closed ones defensible.
Join the teams running quality work on results with the math attached.
Read customer stories
Care Gap Identification
Every result is a calculation you can open.
Documented HEDIS measures, evaluated on the record
Measure logic runs against the consolidated record — initial population, denominator and exclusions, numerator — after new data is processed.
A FHIR bundle, not a score
Results return the Patient, the MeasureReport, and the supporting Parameters behind the calculation.
Closed gaps come back too
A MeasureReport records the numerator result either way, so satisfied gaps return with the same supporting calculation as open ones.
Re-evaluated as data lands
Evaluation runs on the analytics cycle after new Network Query results or real-time notification data is processed.
Benefits
Stop hunting for gaps the record already answers.The measure engine reads the history so your quality team reads results.
Hours of chart-chasing, gone from the workflow.
Gap identification runs on the retrieved record — external history included — so the search that used to be manual arrives as a result list.
Color Health — "Metriport surfaces the patient data and care gaps we would have otherwise spent hours hunting down."
Outreach stops chasing work that is already done.
Closed gaps return with the same calculation as open ones, so a patient whose screening happened elsewhere leaves the call list before anyone dials.
Read the care-gaps docsDefensible numbers, patient by patient.
Every result carries its population math. When an auditor, a payer, or your own analyst asks why, the answer is in the MeasureReport rather than in a spreadsheet.
See the Data WarehouseHow it works
Evaluate the measures, open the math, route the results.Patient-level and organization-level, through the same API.
Evaluate supported HEDIS measures
Measure logic applies after consolidated data is processed. The supported list lives in the docs.
Review the patient-level calculation
The result is a FHIR Bundle: the Patient, the MeasureReport, and the supporting Parameters.
Query the record behind the result
Gap results resolve into the same consolidated record everything else on the platform reads.
Support
FAQs
Metriport documents a current set of supported HEDIS measures. Review the care-gaps documentation for the supported measure list.
Care-gap evaluation runs on the analytics cycle after new Network Query results or real-time notification data is processed.
The API returns a FHIR Bundle containing the Patient, MeasureReport, and supporting Parameters details for the calculation.
Yes. A MeasureReport records the numerator result either way, so a gap that has already been satisfied is returned with the same supporting calculation as an open one — which is what keeps outreach from chasing work that is already done.
Explore our platform
All our products
Where does the data come from?
Where does my team actually use it?
What does it tell me that I didn’t know?