Skip to content
FonteumPublic-records evidence
HRSAWorkforce and accessObserved 2026-06-15

HRSA Uniform Data System (UDS)

Annual self-reported performance data for federally funded health centers (FQHCs). The Grant Year 2024 extract covers 1,359 Health Center Program awardees, 16,334 service-delivery sites, and 18,046 clinical-quality-measure rows across 14 measures, serving 32.4 million patients. Awardee-level aggregate reporting; the public extract carries no NPI or CCN. Source: Health Resources & Services Administration · 2026-06-15

1,359
Health Center Program awardees
Catalog observation: 2026-06-15
Fonteum catalog observation · 2026-06-15
2024
Temporal coverage
Nominal publisher cadence: annual
HRSA · 2026-06-15
Organization
Illustrative mapping target
Example mapping · hrsa-uds/v1
Fonteum methodology

Illustrative FHIR Organization mapping

How one record can be normalized.

Illustrative mapping
{
  "resourceType": "Organization",
  "id": "uds-example",
  "_source": "hrsa-uds",
  "_methodology": "hrsa-uds/v1",
  "name": "Example Health Center Program Awardee",
  "type": [{ "text": "Federally Qualified Health Center" }]
}

This example documents a normalized shape; it does not establish that a FHIR endpoint or bulk export is available for this catalog entry. When a record includes _source, _methodology, snapshot-date, or confidence fields, those fields are nullable and delivery surfaces can return different subsets. Published bulk files are listed separately in the bulk manifest.

Fields in this record

What each field in the illustrative Organization mapping means.

The fields below are derived from the displayed illustrative FHIR Organization mapping. When a record includes source-metadata fields (_source, _methodology, and a snapshot date), they describe that delivered record. Those fields are nullable and may be absent from a response; identity fields key the record and data fields carry the measured values.

Field-level documentation for HRSA Uniform Data System (UDS)
FieldTypeRole
resourceTypestringIdentity
idstringIdentity
_sourcestringProvenance
_methodologystringProvenance
namestringData
typearrayData

Dataset facts

Dataset facts for HRSA Uniform Data System (UDS)
FieldValue
AgencyHealth Resources & Services AdministrationHRSA · 2026-06-15
CategoryWorkforce and access
Records1,359 Health Center Program awardees(catalog observation 2026-06-15)
Temporal coverage2024
Publisher cadence (nominal)Annual
Load timingNo load-time guarantee; date shown is the catalog observation for this row count.
Catalog observation date2026-06-15
Illustrative FHIR mappingOrganization
Methodologyhrsa-uds/v1
MeasuredAwardee patient counts, payer mix, staffing FTEs, and clinical quality measure rates per grant year
Upstream sourcedata.hrsa.gov

Get access

How to reach this dataset.

Dataset-specific delivery formats are confirmed during pilot review. This catalog entry does not promise a bulk file or FHIR endpoint. Pilot requests are reviewed within one business day; there is no charge during the pilot period.

Related · Workforce and access

HRSA
HRSA Health Professional Shortage Areas

Federal Health Professional Shortage Area (HPSA) designations — geographic areas, populations, and facilities with a critical shortage of primary-care, dental, or mental-health providers.

HRSA
HRSA 340B Covered Entities

HRSA 340B drug-pricing program covered entities. This catalog entry records no loaded rows at the June 14, 2026 observation; it does not claim a completed ingest or row-level provenance.

Browse all datasets →

What’s on file, by the numbers

Platform snapshot · 2026-08-11

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file
26.2Msource-linked factsSource-linked field facts in the dated platform snapshot
90sources with dataDistinct snapshot source IDs with at least one positive record count
73fresh sourcesDistinct source IDs whose latest positive-data snapshot falls within the preceding 45 days
111sources integratedActive registry rows; integration does not establish a load
13state Medicaid jurisdictionsDistinct states represented in the state-exclusions serving table

Integrated, with-data, and fresh-observation counts are separate. No platform-wide source-completeness count is published. Completeness is source-specific and must be evaluated against the named source's expected scope. State coverage is a separate jurisdiction measure.

Source authority is record-specific

Use the issuer named on the record.

Fonteum spans federal, state, and global public publishers. A source page or returned record identifies its issuer and dataset where that metadata is available. A platform registry count does not assign every page to one authority or establish loaded, fresh, or complete coverage.

Browse source records and their stated limitations →

Reproducible by design

Inspect the evidence each published figure actually supplies.

Source and date

Research pages expose the named public file and observation date where those fields are available. Source-file SHA-256 coverage is separate; facts do not currently link deterministically to signatures.

Available derivation

Studies with a retained release and committed derivation link the SQL or method used. Other studies state the evidence and reproduction limits they actually have.

Daily observations

Dated table row-count observations can detect local drift. They do not imply that an upstream publisher released or Fonteum ingested new data that day.

Named medical review

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

Read the full provenance and attestation methodology →

Request access