Every correction we've issued, dated.
When a published figure is wrong, we correct it in place, mark the change with a date, and log the substance of the correction here. When a study's premise is wrong, we retract; the retraction stays at the original URL so external citations don't 404.
See the corrections policy for the full process. Reader-submitted corrections route through the per-vertical corrections forms and the Ownlisted contact form.
- Entries
- 0
- Maintained by
- Editorial Lead
- Submit a correction
- Contact form
No corrections have been accepted in the public log yet. When corrections occur, they will appear here with the date, page, original claim, corrected claim, and source.
Empty is not a claim the dataset is perfect — it means none have been accepted in the public log yet. The corrections process is live and every reader-flagged inaccuracy is treated as a P1 issue.
How to submit a correction
The fastest path is /contact or email corrections@fonteum.com. Include:
- The page URL where the disputed claim appears.
- The exact text of the disputed claim, copied verbatim.
- The corrected claim and the public source that supports it (a state-board record, a CMS page, an academic citation).
- Optional: your role (reader / journalist / business owner / source agency) — useful for prioritization, never published without consent.
We acknowledge every submission within two business days. Accepted corrections post to this log with the five fields above.
Updates to the methodology — what the methodology now requires that it didn’t require before — are not corrections. They’re doctrine revisions. Listed separately here so the corrections log isn’t inflated with policy edits.
Recent methodology updates
2026-05-03
SOP §137 · UX / surface
Data Graph Visual v2 — moat as a one-second picture.
2026-05-03
SOP §136 · Doctrine
Sources Library v2 — status field + restricted-sources doctrine.
2026-05-03
SOP §135 · UX / surface
/press rebuilt as a journalist + data-user landing page.
2026-05-03
SOP §134 · UX / surface
/data-platform — B2B / data-product surface.
2026-05-03
SOP §133 · UX / surface
Brand chart palette + StatTable typography polish.
Snapshot publishes — CMS Care Compare extracts, BLS annual pulls, source-pack ingestion runs — are not corrections and not methodology updates. They’re dated data refreshes. Listed separately so the reader can tell at a glance which kind of change a given entry is.
Recent data refreshes
2026-05-03
SOP §117 · Data snapshot
CMS Care Compare research bundle (home health + hospice).
Two more Tier-1 research snapshots published from the CMS Care Compare cluster: home-health quality by state and hospice provider availability by state. Source/date/limitations triplet on every cited field; Fonteum does not independently rate, inspect, verify, endorse, or guarantee any agency or hospice.
2026-05-03
SOP §116 · Data snapshot
Dialysis facility research snapshot published.
First state-level snapshot of CMS Care Compare dialysis facility quality data. Tier-1 research-only — no facility profile writes; data appears in /research aggregates only.
2026-05-03
SOP §115 · Data snapshot
Nursing-home research snapshot published.
First state-level snapshot of CMS Care Compare Nursing Home Provider Information master dataset. Special Focus Facility status reported at state-aggregate level only — never on individual facility profiles. CMS ratings appear as CMS ratings.
- Editorial policy → The full corrections process (7-day window, retractions), independence rules, and the doctrine block.
- Methodology → How figures are sourced, refreshed, and checked — plus the full methodology changelog.
- Source library → Every dataset Fonteum cites, with tier and limitations.
- Data provenance → Field-by-field source register.
Compliance posture
We don’t sell ranking and don’t accept payment to move a provider up the list. For final hire decisions, verify licensing, insurance, and references directly with the applicable licensing or credentialing body.
No bulk-licensing source family is currently ingested for this vertical. Hire-time checking still routes through the body named above.