UDS quality measures vs HEDIS: what FQHCs actually have to report

Every FQHC quality director knows the feeling: the UDS submission window is approaching, and at the same time three Medicaid managed care plans are sending gap lists and asking about HEDIS rates. The measures look almost identical. The work is not.

That is because UDS and HEDIS are two different programs with two different owners, two different populations, and two different sets of rules that happen to measure much of the same clinical care. Understanding exactly where they align and where they diverge is the difference between running one coordinated quality operation and running two parallel ones with the same overworked staff.

This article explains what UDS reporting requires, how it relates to HEDIS, and why the operational answer is a single outreach-and-documentation workflow that feeds both.

What the Uniform Data System is

The Uniform Data System (UDS) is the standardized annual reporting system that HRSA's Bureau of Primary Health Care requires from every Health Center Program awardee and look-alike. If your organization receives Section 330 funding or holds look-alike designation, UDS reporting is a condition of the program, not an option. HRSA publishes the requirements, manuals, and training through the Bureau of Primary Health Care UDS resources.

UDS covers far more than clinical quality. A full submission includes patient demographics and socioeconomic characteristics, staffing and utilization, services provided, clinical quality measures, financial costs, and revenue. HRSA uses the data to demonstrate the Health Center Program's reach and value to Congress, to compare health centers against one another, and to award quality recognition.

Reporting runs on a calendar-year basis, with submissions due early in the following year. The exact tables, measure specifications, and submission mechanics are updated regularly, and HRSA has been modernizing the system toward patient-level electronic submission through its UDS Modernization Initiative, so always check the current UDS manual for the reporting year you are working on rather than relying on last year's specs.

Two things make UDS different from anything a health plan asks of you. First, it is all-payer and all-patient: the denominator logic starts from patients your health center saw during the year, regardless of insurance. Uninsured patients count. Second, it is reported by you, from your records, on your systems. There is no payer calculating your rate from claims; your EHR data and your documentation quality directly determine your reported performance.

The UDS clinical quality tables

Within the full UDS submission, the clinical quality tables are where the care gap work lives. These tables report screening, preventive, and chronic care measures across the health center's patient population, and they are the numbers HRSA uses for quality benchmarking and recognition.

The measure set has historically included measures such as:

• Cervical, breast, and colorectal cancer screening
• Childhood immunization status
• Depression screening and follow-up
• Screening for tobacco use and cessation intervention
• Body mass index screening and follow-up
• Controlling high blood pressure
• Diabetes: hemoglobin A1c poor control
• Statin therapy for the prevention and treatment of cardiovascular disease
• HIV screening and linkage to care
• Prenatal care and birth outcome measures
• Dental sealants for children at elevated caries risk

The precise list and specifications change across reporting years, so treat the above as illustrative and confirm against the current UDS manual.

A crucial structural fact: most UDS clinical quality measures are aligned with CMS electronic clinical quality measures (eCQMs), the same specifications used in other federal quality programs. That means the measure logic is designed to be computed from structured EHR data. If a mammogram result lives in a scanned PDF instead of a structured field, it may exist clinically but not exist for UDS purposes. Documentation structure is performance.

What HEDIS is and where FQHCs meet it

HEDIS, the Healthcare Effectiveness Data and Information Set, is a registered trademark of NCQA (the National Committee for Quality Assurance) and is the dominant quality measure set used by US health plans; the specifications are published at ncqa.org/hedis. Health plans, not providers, are the reporting entities: a Medicaid managed care plan calculates its HEDIS rates across its enrolled members and reports them to NCQA and to state Medicaid agencies. How plans gather that evidence is covered in our explainer on HEDIS data collection methods.

FQHCs meet HEDIS indirectly but forcefully. States hold Medicaid managed care plans accountable for HEDIS performance, and plans push that accountability down to contracted providers through quality incentive programs, pay-for-performance arrangements, and monthly care gap lists. When a plan sends your health center a list of members due for colorectal cancer screening, that list is typically generated from HEDIS measure logic run against the plan's claims and supplemental data.

The consequence: an FQHC contracted with three Medicaid plans is effectively scored on HEDIS three separate times, each time only on the slice of its patients enrolled in that particular plan, each time from that plan's data, which may or may not reflect care the health center delivered. For a deeper walkthrough of raising those scores in a community health center setting, see our guide to HEDIS measure improvement for CHCs.

UDS vs HEDIS: side-by-side comparison

The table lines up the two programs dimension by dimension. The paragraph that follows explains why the overlap in clinical content does not translate into matching results.

The overlap in clinical content is real: cancer screenings, blood pressure control, diabetes care, depression screening, and well-child care appear in both worlds. But a patient can count toward your UDS numerator and be invisible to a plan's HEDIS rate (because the claim never carried the right code, or the service predated enrollment), and vice versa. The two programs are cousins, not twins.

The dual-reporting burden in Medicaid managed care

Here is what the dual burden looks like operationally at a typical FQHC:

• Same patient, multiple scorecards. A diabetic patient with Medicaid managed care coverage counts in your UDS diabetes measure and in her plan's HEDIS diabetes measures, under different denominator rules and different data pipelines.
• Multiple gap lists, one staff. Each contracted plan sends its own care gap list in its own format on its own schedule, while your internal team also works UDS measures from EHR reports. Without deduplication, the same patient gets called three times, or nobody owns her at all.
• Two documentation standards. UDS wants structured EHR data that eCQM logic can read. Plans want claims and supplemental data feeds that HEDIS logic can read. Care documented in a free-text note can fail both.
• Timeline whiplash. UDS is a year-end sprint; plan quality programs run all year with measurement-year deadlines. Teams that only mobilize for UDS season discover in December that half the year's outreach opportunity is gone, for both programs.

Community health centers already run lean. Benchmarks for what outreach teams realistically close in this setting are covered in our care gap outreach benchmarks for FQHCs and CHCs, and the honest summary is that manual dual-tracking wastes a meaningful share of the capacity those benchmarks assume.

One workflow that feeds both

The way out is not to pick one program over the other. It is to stop treating them as separate work. UDS and HEDIS reward the same underlying events: an eligible patient identified, contacted, scheduled, seen, and documented in structured data. Build one loop that does that well and let each program read from it. (If your team is strong on tracking gaps but weak on closing them, our comparison of care gap management vs care gap closure explains why that loop needs its own owner.)

A practical sequence:

1. Build one master gap registry. Combine your EHR-derived UDS measure gaps with every plan's care gap list into a single deduplicated patient-level worklist. One patient, one row, all open gaps and all attributed plans on that row.
2. Reconcile before you outreach. Check each externally reported gap against the EHR first. A plan's list reflects its claims lag and its data; a patient flagged as unscreened may have had the colonoscopy last month. Closing false gaps by data submission is cheaper than closing them by phone call.
3. Prioritize by shared impact. Gaps that count in both UDS and a plan incentive program outrank gaps that count in only one. Multi-gap patients outrank single-gap patients, because one visit can close several measures.
4. Run outreach continuously, not seasonally. Monthly outreach cycles beat a Q4 scramble, keep call volume manageable, and capture services early enough for claims to post before plan deadlines.
5. Document once, structurally. Train teams to record results, refusals, and exclusions in the structured fields that eCQM and HEDIS logic read. A refusal documented correctly is a valid outcome; one buried in a note is a permanent open gap.
6. Feed evidence back both ways. Push supplemental data or records to plans so their HEDIS rates reflect your work, and validate your UDS extracts quarterly so year-end submission is a confirmation, not an archaeology project.

This is exactly the class of workflow that automation handles well, because the hard parts are volume and consistency, not judgment. AI-driven approaches to this loop in the safety-net context are covered in our piece on FQHC care gap closure with AI, and the broader system view lives on our care gap closure automation pillar page.

One more integration point worth naming: many quality measures close through referrals (colonoscopies, mammograms, retinal exams), so gap closure performance is partly referral performance. If referred patients never complete, your measures stay open no matter how good your outreach is. Our guide to FQHC referral coordination covers that half of the loop.

The bottom line

UDS is mandatory, health-center-reported, all-payer quality reporting to HRSA. HEDIS is plan-reported quality measurement that reaches FQHCs through Medicaid managed care contracts, gap lists, and incentive dollars. The clinical content overlaps heavily; the rules, denominators, and data pipelines do not. Treating them as two programs staffed separately doubles the burden on teams that cannot afford it. Treating them as one continuous identify-outreach-document-submit loop, built on structured documentation and run all year, lets every completed screening count everywhere it should.

Frequently asked questions

Sources

• HRSA Bureau of Primary Health Care, Uniform Data System (UDS) training and technical assistance: reporting requirements and manuals
• HRSA Bureau of Primary Health Care, Uniform Data System (UDS) Modernization Initiative
• HRSA Bureau of Primary Health Care, UDS clinical quality measures and Healthy People 2030 objectives and benchmarks (national programs crosswalk)
• NCQA, HEDIS measures and technical resources
• CMS eCQI Resource Center, about electronic clinical quality measures (eCQMs)