Per-source refresh cadence — upstream schedule + Fonteum pull schedule.
Every displayable field on every Fonteum record carries an explicit last_checked timestamp. We never display a record without it. Stale records appear with explicit staleness markers in source-coverage metadata, not silently as fresh.
| Source | Scope | Upstream | Fonteum pull | Notes |
|---|---|---|---|---|
| NPPES (CMS NPI Registry) | All Type-1 and Type-2 NPIs nationwide | Daily-updated public API; monthly bulk file | Quarterly snapshot today; monthly is the target as we scale | Each specialty supply study is a dated snapshot. Re-pulls are explicit, not silent. |
| CMS Care Compare | Hospitals, home health, hospice, nursing homes, dialysis | Quarterly federal release | Quarterly, aligned to upstream release | Methodology release notes published with each snapshot. |
| HRSA HPSA (Health Professional Shortage Areas) | Federal designation of underserved-area boundaries | Continuously updated by HRSA; major revisions ~quarterly | Research-context only; refreshed alongside relevant studies | Used for research framing, not per-provider profile fields. |
| BLS OEWS / QCEW + BEA Regional | Federal labor and regional-economic statistics | Annual (OEWS), quarterly (QCEW), annual (BEA Regional) | Refreshed alongside relevant research releases | Research-context only. Public-domain federal data. |
| U.S. Census Bureau (PEP V2025 + ACS) | State and county population denominators | Annual PEP releases; ACS 5-year releases annually | Refreshed as new vintages release; documented in source helper files | Per-capita figures across the research series share a consistent denominator family. |
Refresh cadence is a function of two things: how often the upstream source publishes, and how often we pull. We commit to honesty on both. We never silently bump a snapshot date forward without re-pulling, and we never display a record that doesn't carry a last_checked timestamp.
A customer integrating Fonteum data can rely on this contract: any record we display either has a recent last_checked, or it's flagged as stale in source-coverage metadata. If a customer's integration needs a stricter freshness contract, that's the conversation that moves a Pilot to Standard tier.