DATA FRESHNESS
Publisher cadence and loaded observations are different dates.
The publisher schedule below describes when an upstream source ordinarily releases data. The loaded observation states what production actually held when checked. Where that observation was not established, this page says so instead of inferring freshness from a configured job.
SOURCE-BY-SOURCE
| Source | Scope | Upstream | Loaded observation | Notes |
|---|---|---|---|---|
| NPPES (CMS NPI Registry) | All Type-1 and Type-2 NPIs nationwide | Daily-updated public API; monthly bulk file | Newest production system timestamp: 2026-06-10 (checked 2026-07-12) | CMS publishes more often than this loaded observation. The page does not imply every weekly release was ingested. |
| CMS Care Compare | Hospitals, home health, hospice, nursing homes, dialysis | Quarterly federal release | Newest loaded source date across checked modules: 2026-05-07 (checked 2026-07-12) | Loaded modules can lag the next CMS release; consult the record's source date. |
| HRSA HPSA (Health Professional Shortage Areas) | Federal designation of underserved-area boundaries | Continuously updated by HRSA; major revisions ~quarterly | Not established by the July 12 serving-table audit | Used for research framing; consult the dated study or response rather than inferring freshness from HRSA's cadence. |
| BLS OEWS / QCEW + BEA Regional | Federal labor and regional-economic statistics | Annual (OEWS), quarterly (QCEW), annual (BEA Regional) | Not established by the July 12 serving-table audit | Research-context only. Each published study states the vintage it used. |
| U.S. Census Bureau (PEP V2025 + ACS) | State and county population denominators | Annual PEP releases; ACS 5-year releases annually | Not established by the July 12 serving-table audit | Per-capita studies must state the Census vintage used; publisher cadence is not a loaded-date claim. |
HOW TO READ FRESHNESS
A source date identifies the release represented by the loaded data. An observation timestamp identifies when Fonteum inspected or served it. A publisher cadence and a configured job describe schedules; neither proves that a newer release was loaded.
Consumers should use the dates supplied by the specific response or dataset and confirm consequential facts at the official source. A stricter delivery commitment belongs in a written agreement scoped to named datasets.