quadevs

HEDIS reporting software and measure pipelines

Pipelines that compute HEDIS measures from claims and chart documents, and report generators an auditor can replay.

HEDIS measures are the NCQA quality metrics health plans report each year, breast cancer screening among them. Producing them means collecting claims and chart documents, normalizing them for the measure year and computing numerator, denominator and exclusions so that an auditor can rebuild every figure.

Parts of a HEDIS pipeline

  • Document intake

    Fax lines and insurance portals feed classification. Each source has its own retry queue, so one failing portal never holds up the faxes or the other feeds.

  • Measure production

    Numerators, denominators and exclusions computed per measure year and stored with their inputs.

  • Submission replay

    Past submissions, rebuilt on request.

  • Stuck-order alerts

    Slack incidents, diagnostics attached.

  • Clinical report generator

    Branded PDF reports with charts and signature blocks, generated in batch for a whole cohort.

HEDIS and reporting systems we built

Starting a HEDIS project

  1. Measures and sources

    Tell us which measures you report, where the data comes from and where the current run breaks.

  2. Rebuild last year

    We reproduce one past submission from its raw inputs to find where the numbers drift.

  3. Parallel run

    The new pipeline runs beside the old process until both produce the same figures, then takes over.

And much more. Ask about your project

Common questions

Can the new pipeline run beside our current HEDIS process?
Yes, and we recommend it. Both run on the same measure year until they produce the same figures. Then the old process is switched off.
What are HEDIS measures?
HEDIS (Healthcare Effectiveness Data and Information Set) is a set of more than 90 measures maintained by NCQA. Health plans use them to report on preventive care, chronic conditions and access to care. Each measure defines who belongs in the denominator and which event moves a member into the numerator.
Why should a HEDIS pipeline be reproducible?
Results go through audit, and the auditor can ask why any member landed in a numerator. A pipeline that stores its inputs with every run answers that with a query. Without stored inputs, the team reconstructs the answer by hand.

Further reading in Insights

Which HEDIS measures do you report?

Name the measure year, the data sources and the point where audit preparation turns manual.

Your project brief

A short brief gets a real reply within one business day.

Budget range (optional)

By sending this you agree we can use your email to reply. Privacy policy.

Or email hello@quadevs.com.