UDS reporting: a practical guide for health center quality teams.

What UDS is, and why it matters

The Uniform Data System (UDS) is the annual report that every Health Center Program awardee — and every look-alike — submits to HRSA’s Bureau of Primary Health Care. It’s the standardized picture of who your health center served, what services you delivered, the quality of the clinical care, and what it cost. HRSA aggregates UDS data into the public record of the health center program: nearly 1,400 health centers serving more than 31 million patients, all reporting on the same definitions so the numbers can actually be compared.

That comparability is the point — and the pressure. UDS data feeds HRSA’s oversight of your grant, national and state benchmarks, quality recognition, and increasingly the public’s view of your organization. The clinical quality rates you submit get ranked against every other health center in the country. Boards see them. Funders see them. So does anyone with a browser, via HRSA’s data site.

The annual cycle

UDS reports on the calendar year: January 1 through December 31. Submission happens through HRSA’s Electronic Handbooks (EHBs) in a window that opens January 1 and closes February 15 of the following year — for example, calendar-year 2025 data was due February 15, 2026. HRSA also opens a Preliminary Reporting Environment (PRE) before the official window so teams can enter data early, though nothing can be submitted before January 1. After submission, a UDS reviewer works your report: expect questions, edits, and revision requests through the spring before the data is finalized.

Two practical notes on the calendar. First, confirm the current year’s dates and requirements against HRSA’s official UDS reporting guidance — the cycle is stable, but tables, measures, and definitions change year to year, and the annual UDS manual is the authority. Second, take the deadline seriously: HRSA states that failure to submit a timely, accurate, and complete report can result in a condition being placed on your grant award.

What’s in the report

At a high level, UDS covers four territories:

• Patients and demographics. Counts by ZIP code, age, race and ethnicity, language, income relative to poverty level, and insurance status. This is where your patient universe gets defined — and that universe drives denominators downstream.
• Services, staffing, and utilization. Visits and virtual visits by service line, staffing by position, and selected diagnoses and services rendered.
• Clinical quality measures. The clinical tables: screening and preventive care rates, chronic disease control outcomes, prenatal and perinatal care. These are the tables quality teams own, and the ones this guide is mostly about.
• Costs and revenue. What care cost to deliver and how it was paid for, including grant and program income detail.

Why the clinical tables are the painful ones

Demographics and finance tables mostly summarize systems built to count things. The clinical tables ask a harder question — “of the patients who should have received this care, how many did?” — and answering it accurately stresses every weak point in your data:

• EHR data quality. A measure can only see structured data. The mammogram report scanned into a media tab, the A1c value typed into a note, the colonoscopy your patient had at the hospital that never produced a structured result — all real care, all invisible to a query until someone fixes the documentation.
• Mapping. UDS measures are built on specific code sets and definitions that get updated annually. If your EHR’s report logic, your local mappings, and the current UDS manual disagree, you get three different rates and no obvious truth.
• Denominators. Who counts as a patient for each table, which visits qualify them, and which exclusions apply are precise definitional questions. Small denominator errors move rates more than most interventions do.
• Supplemental data. Immunization registries, payer files, hospital labs, care received outside your walls — evidence that closes gaps often lives outside the EHR, and if it never flows back as structured data, your reported rate understates your real performance.

The common thread: UDS season doesn’t create these problems, it reveals them — eleven months too late to fix the year being reported.

A preparation playbook

The teams that have calm Februaries treat UDS as a monthly discipline, not an annual event.

1. Monitor measures monthly, not in February. Run your clinical quality measures every month against current-year definitions. A rate that drifts in March is a documentation or mapping problem you can fix; the same drift discovered in January is just a worse number. Month-over-month trend lines also catch breakage — if a measure falls off a cliff, a feed or mapping broke, not your clinicians.
2. Reconcile EHR counts against payer registries. Your payers compute overlapping measures from claims. Where the payer says a patient is compliant and your EHR says they aren’t — or vice versa — you’ve found either missing supplemental data or a measure-logic difference. Reconcile quarterly; every mismatch you resolve improves both your UDS rate and your payer program performance.
3. Document exclusions as they happen. Patients who refuse screening, hospice patients, clinically excluded cases — capture these in structured fields at the point of care, with the reason. Reconstructing exclusions in January from memory and free text is slow and audit-fragile.
4. Validate patient counts and attribution. Confirm that your patient universe — who had a qualifying visit, in which service line, under which provider — matches the definitions before you trust any rate built on it. Duplicate records and mis-assigned visits quietly distort both numerators and denominators.
5. Dry-run the clinical tables in the fall. Produce a full draft on third-quarter data. Every problem you find in October is one you won’t find in February — and the PRE gives you a place to stage early entries.
6. Read the manual changes every year. Assign someone to diff the new UDS manual against last year’s and translate the changes into your report logic before January, not during the submission window.

Plan for the review, not just the deadline

February 15 is the start of a conversation, not the end of one. Your UDS reviewer will compare this year’s figures against last year’s and against peers, and ask about anything that moved sharply. The teams that close out review quickly are the ones who anticipated the questions: keep a short methodology memo as you prepare — what changed in your EHR, your mappings, your service lines, your patient mix — and annotate any rate that swung more than a few points with the reason. If a number will surprise the reviewer, it should not surprise you. Writing the explanation in November, while the cause is fresh, beats reconstructing it in April from a reviewer’s edit request.

What changes with unified data and continuous measurement

Most of the February pain is assembly: pulling data from the EHR, registries, payer files, and spreadsheets into one defensible picture, once a year, under deadline. A platform that maintains a unified patient record continuously — EHR, claims, registry, and payer-portal data merged and identity-matched as it lands — and computes quality measures nightly inverts the work. The numbers exist all year. Supplemental evidence is already merged and deduplicated. Anomalies get flagged when a feed breaks, not when a reviewer asks why a rate moved. UDS season becomes what it should be: verifying numbers you already trust, then submitting them.

That’s the approach we take at Quaility — 39 clinical quality measures computed nightly on a unified patient record, with a UDS data explorer built for exactly this season. At our first deployment — a Los Angeles community health center — that foundation supported moving three quality measures past the 75th national percentile in a year.

Measured outcomes at our first deployment — a Los Angeles community health center.