Health Care Facilities Data: Hospital Capacity, NPI Records, FQHC Benchmarks and Shortage Scores · Head-to-head
HRSA Data Downloads - AHRF, Health Center Sites, HPSA & Transplant Files vs HRSA Health Center Program Uniform Data System (UDS) Data 2025
Which health care facilities data: hospital capacity, npi records, fqhc benchmarks and shortage scores data fits your job: HRSA Data Downloads - AHRF, Health Center Sites, HPSA & Transplant Files, or HRSA Health Center Program Uniform Data System Data 2025. API, files, or your warehouse. Daily, weekly, or hourly.
HRSA Data Downloads - AHRF, Health Center Sites, HPSA & Transplant Files
HRSA Health Center Program Uniform Data System (UDS) Data 2025
Where the fields line up
2 shared fields — join on these.
| Field | HRSA Data Downloads - AHRF, Health Center Sites, HPSA & Transplant Files | HRSA Health Center Program Uniform Data System Data 2025 |
|---|---|---|
FQHC Site NPI Number | documented | National Provider Identifier for the FQHC site where enrolled; blank when none. |
Geocoding Artifact Address Primary X Coordinate | documented | Longitude coordinate produced by geocoding of the site address. |
Coverage, side by side
| HRSA Data Downloads - AHRF, Health Center Sites, HPSA & Transplant Files | HRSA Health Center Program Uniform Data System Data 2025 | |
|---|---|---|
| Geographic | `fips_st_cnty` five-character county FIPS (01001); HPSA ID; MUA/P ID; boundary shapefiles | State/territory roll-ups, HealthCenterZipCodes sheet, patient-zip tabulations |
What each contains
They tie on 1 attribute. Pick by fit, not by loyalty.
| HRSA Data Downloads - AHRF, Health Center Sites, HPSA & Transplant Files | HRSA Health Center Program Uniform Data System Data 2025 | |
|---|---|---|
| Site name | `Site Name` (e.g. GOOD SAMARITAN SHELTER) | `SiteName` (e.g. CHICOPEE HEALTH CENTER) |
| Geocoding | `Geocoding Artifact Address Primary X Coordinate` / Y (longitude/latitude decimal degrees) | `Geocoding Artifact Address Primary X Coordinate` (longitude) plus Y |
| Provider identifier | `FQHC Site NPI Number` | `FQHC Site NPI Number` |
| Operational status | `Site Status Description` enum (Active) | `SiteStatus` enum (Active) |
| Operating hours | `Operating Hours per Week` (20.00) | `TotalWeeklyHoursOfOperation` (47.00) |
| Organization keys | Grantee organization columns inside the sites file (e.g. Health Center Name, H80CS00046) | `BHCMISID` (010030) + `GrantNumber` (H80CS00803) |
| Geography keys | `fips_st_cnty` five-character county FIPS (01001); HPSA ID; MUA/P ID; boundary shapefiles | State/territory roll-ups, HealthCenterZipCodes sheet, patient-zip tabulations |
| Shortage measures | `HPSA Score` (24), `IMU Score` (57.50), `% of Population Below 100% Poverty` | none |
| Program measures | none | `T3a_*... T9e_*` coded columns for UDS Tables 3A-9E (patients, visits, staffing, quality, finances) |
| Facility counts | `hosp_23`, `critcl_access_hosp_23` and 714 more AHRF county columns | none |
| Transplant volumes | `Donor Count` (118954 in the Donor Demographics tab) | none |
| Documentation aids | Metadata dictionaries (attribute, physical column, definition, valid values) beside each mart | Coversheet (ReportingYear, center count), Edits sheet, 2024-2025 crosswalk |
What each does better
HRSA Data Downloads - AHRF, Health Center Sites, HPSA & Transplant Files
Breadth across the whole safety net. Over 100 files on one shelf: the 86-file AHRF 2024-2025 release, the daily sites CSV (~10.5 MB), three discipline-specific HPSA attribute marts (primary care, dental, mental health; the primary care file alone ~48 MB and 66 columns), MUA_DET.csv with 63 columns including IMU Scores, shapefile zips carrying designation boundaries and centroid points, and an organ donation/transplantation file built on OPTN data through March 31, 2026. UDS Data 2025 speaks only to Health Center Program grantees.
County context no reporting workbook contains. AHRF's thematic facilities file runs 716 columns per county FIPS code - hospitals by type (short-term general, long-term, psychiatric, rehabilitation, children's, critical access, VA), admissions, medical school affiliation, Medicare/Medicaid provider counts. Benchmark a clinic's county against every other facility in it, not just against peer grantees.
Shortage geography as polygons, not just lists. HPSA rows carry HPSA IDs (example 1689996802), scores up to 24 in the captured sample, status enums and population-below-poverty shares; MUA/P rows add IMU Scores (example 57.50). Boundary and point shapefiles mean a GIS overlay needs no geocoding step of your own.
A directory you can dial. Site rows include telephone number, web address, Medicare billing number, grantee organization details, HHS region and congressional district - enough to run outreach or provider-directory work straight off the file.
HRSA Health Center Program Uniform Data System Data 2025
Performance measures, not rosters. UDS Tables 3A through 9E pack patients, visits, staffing, clinical processes and outcomes, and finances into coded columns keyed to the UDS manual - T3a_L1_Ca and friends.
Patient characteristics and recognition layers. Around the workbook sit a Patient Characteristics Snapshot (poverty level, insurance status, race, ethnicity), a Hypertension Control Dashboard with five-year trends, state-versus-national comparisons and Community Health Quality Recognition badge listings. HRSA sizes the program's reach: roughly 1,400 organizations serving 1 in 8 US children, 1 in 5 rural residents and 1 in 15 adults 65 and older.
Analytic scaffolding the raw files lack. Every awardee keys on BHCMISID (example 010030) and GrantNumber; site rows add TotalWeeklyHoursOfOperation, UrbanRuralFlag and named project directors. An Edits sheet documents HRSA's edit checks, a Coversheet stamps ReportingYear 2025 and 1,356 centers, and a 2024-2025 crosswalk bridges consecutive years for panel building.
Where they're equivalent
Both cover the United States including territories, and both reach the individual service delivery site - the identical 56-column sites table, down to coordinates and NPI numbers, ships in each record. The real difference is what surrounds that shared core - a hundred adjacent programs on one side, the full reporting depth of one program on the other.
Or take both in one feed
Yes - they interlock because they share identifiers rather than competing with them. A defensible workflow: take the Service Delivery and Look-Alike Sites table (identical in both records) as the spine, attach UDS Tables 3A-9E by GrantNumber or BHCMISID to get performance per site, overlay HPSA/MUA-P boundaries via the shared latitude/longitude fields to test whether high-scoring shortage areas coincide with low-performing grantees, then bring in AHRF's 716-column county file for market context such as critical access hospital density.
Align before joining: the UDS measure columns arrive as coded names (T3a_L1_Ca) defined outside the workbook, so keep the mapping alongside your pipeline; the two halves also advance on different calendars - a current site roster against a reporting-year close-out - so timestamp each layer before merging and expect the roster to lead the measures.
Datadory ships either record alone or both merged onto one key structure, delivered daily, weekly, or hourly - your call. Or take both in one feed.
API, files, or your warehouse. Daily, weekly, or hourly.
Fair questions
Do both datasets contain the same health center site list?
Essentially yes - the Service Delivery and Look-Alike Sites table ships in both records with the same 56 columns: Site Name, FQHC Site NPI Number, operating hours, addresses and geocoded coordinates. The identical sample row (GOOD SAMARITAN SHELTER, Santa Maria CA) appears in each.
Which dataset has shortage area designations like HPSA scores?
It publishes discipline-specific HPSA attribute marts (66 columns: HPSA ID, HPSA Score, status, FTE, population below 100% poverty), MUA_DET.csv with 63 columns including IMU Scores, and shapefile zips for designation boundaries and centroid points. UDS Data 2025 contains no shortage designations - though joining on coordinates lets you test grantee performance inside designated areas.
Can I match records between the two datasets?
Coordinates match too, since both sides use HRSA's own geocoder output. Expect the roster to lead the measures, since the site table refreshes continuously while UDS settles once per reporting year.
Which dataset reaches further back in time?
HRSA Health Center Program Uniform Data System (UDS) Data 2025 holds the longest consistent series: H80 workbooks from 1999 through 2025 with identical measure definitions, plus five-year trend summaries.
Can Datadory deliver both datasets together?
Yes. Either record arrives alone or merged onto one key structure - sites joined to measures on grant number and NPI, shortage geometry overlaid on coordinates - delivered daily, weekly, or hourly, your call. Name the counties, measures and windows when you request the sample and it lands pre-cut, with field definitions and coverage profiles attached.