Skip to content
FonteumThe Graph

By use case

Exclusion & monitoring (self-serve)Free roster screen — no accountExclusion & sanctions screeningCredentialing & provider-data enrichmentAudit evidence & defensible programsProvider data for AI / RAGM&A & network diligence

By buyer

Compliance & riskJournalists & newsroomsDevelopers & AI teams

By industry

HealthcareProviders & facilitiesSanctionsOFAC / EU / UK / UN / OIG / SAMFederal contractingSAM · USASpending · FAPIIS

The capability layer

APIREST + bulk accessFor AI agentsModel Context Protocol serverFHIR R4 APIBulk exportAudit packSigned report artifacts; source facts remain separately citedReconciliationSource-vs-source diffsAI answers with sourcesHow records link upHistoryRetained versions for named sources

The differentiator

Coverage & sourcesThe catalogFreshnessMethodologyCare CompareFacility qualityAI answers, comparedBrowse all datasets →
Research

The dev on-ramp

DocsAPI referenceConnect your AI agent (MCP)One-paste installFHIR sandboxLive API surfaceQuickstartStatusChangelogSDKs & integrations
Pricing
Sign inFree roster screen →Get a signed certificate →

Solutions

Exclusion & monitoring (self-serve)Exclusion & sanctions screeningCredentialing & provider-data enrichmentAudit evidence & defensible programsProvider data for AI / RAGM&A & network diligenceCompliance & riskJournalists & newsroomsDevelopers & AI teamsHealthcareSanctionsFederal contracting

Platform

APIFor AI agentsFHIR R4 APIBulk exportAudit packReconciliationAI answers with sourcesHow records link upHistory

Data

Coverage & sourcesFreshnessMethodologyCare CompareAI answers, comparedBrowse all datasets →
Research

Developers

DocsAPI referenceConnect your AI agent (MCP)FHIR sandboxQuickstartStatusChangelogSDKs & integrations
Pricing
Sign inFree roster screen →Get a signed certificate →

USE CASE · M&A & NETWORK DILIGENCE

Map who controls a provider network before the deal closes.

Resolve ownership and chain affiliation, then price the enforcement exposure — SNF ownership chains, PBJ staffing, and CMS deficiency history joined from federal primary sources, with linked-source metadata retained where available. Built for diligence counsel and payer SIUs who need a defensible record, and the analysts who build the model.

Request access →Compliance & risk teamsSee the data API →Developers & AI teams

280,207Source: CMS SNF All Owners
SNF ownership rows deficiency citationsLinked-field provenanceNamed CMS observations

✓ No PHI✓ Federal primary source✓ Ownership chain✓ Hash-bearing export metadata

The diligence exposure

Inherited enforcement risk you did not price.

A provider network carries ownership relationships and a regulatory history that the deal model has to price. Miss an operating-organization tie or a chain affiliation and the acquirer inherits enforcement exposure — civil monetary penalties, false-claims liability — it never underwrote. A target's realized-harm history is the floor:

5.59%Source: CMS Care Compare — Nursing Home Compare · As of 2026-05-07
of all federal nursing-home citations reach scope/severity G or above, and the rate varies sharply by state — Illinois averages 4.57 G+ citations per facility against New Hampshire's 0.31, a difference aggregate ratings smooth over.

Fonteum surfaces each ownership tie and citation from the CMS record itself, so the exposure is on the table before the deal closes — not discovered after.

The analyst pain

Three CMS files, joined by hand, lineage lost.

Ownership, staffing, and deficiency history live in three different CMS files on three cadences. Stitching them into a portfolio view means a brittle ETL job — and once joined, the lineage of which file produced which field is gone, so counsel cannot trace a figure back to its source.

One GETresolves a facility's ownership and returns source, observation-date, and limitation metadata when linked — including the

82.4%Source: CMS SNF All Owners
of top-10-chain rows that carry a missing ownership_percentage in the federal file, flagged rather than imputed.


How it works

The federal sources joined, and what each one prices.

280,207Source: CMS SNF All Owners

Ownership chain

CMS SNF All Owners across 14,425 facilities — managing org, operating org, and individual owners with percentage interest and role, PECOS-derived under ACA §6101.

1.3M+Source: CMS PBJ Daily Nurse Staffing · As of 2025-06-30

Staffing signal

PBJ daily nurse-staffing records per quarter across 14,537 facilities — RN, LPN, and CNA payroll hours, the leading operating signal after the staffing-floor rescission.

418,148Source: CMS Care Compare — Nursing Home Compare · As of 2026-05-07

Regulatory history

CMS Care Compare deficiency citations across 14,635 facilities — deficiency tag, harm scope, and survey event ID, the audit trail for enforcement risk.

Nullable

Provenance

Source-linked values retain a source name, observation date, and documented limitation; values without a linked provenance row are not presented as source-linked.

Integration & workflow

One record. Two ways in.

Analysts resolve ownership by facility over REST. Diligence teams scope a portfolio and export the joined record. Both surfaces expose the same available source and observation metadata.

GET /api/v1/ask?question=ownership&scheme=ccn&value={ccn}

curl "https://fonteum.com/api/v1/ask?question=ownership&scheme=ccn&value=015009" \
  -H "Accept: application/json"

Response

{
  "question": "ownership",
  "subject": { "scheme": "ccn", "value": "015009" },
  "answer_text": "Facility 015009 is operated by 1 organization with 3 owner records on file.",
  "facts": [
    {
      "role": "operating_organization",
      "owner_type": "organization",
      "ownership_percentage": null,
      "provenance": {
        "_source": "CMS SNF All Owners",
        "_source_url": "https://data.cms.gov/provider-data/",
        "_snapshot": "2026-05-01",
        "_last_checked": "2026-06-17",
        "_methodology": "ownership/v1",
        "_confidence": 1.0,
        "_limitation": "ownership_percentage absent in source row"
      }
    }
  ],
  "citations": [
    { "source": "CMS SNF All Owners", "source_url": "https://data.cms.gov/provider-data/" }
  ]
}

The ask endpoint is deterministic — no language model. '0 records on file' is an answer, never a silent empty; a source read failure returns 502, never a masked empty. For a full target portfolio, the FHIR R4 bulk $export returns NDJSON keyed to the facilities you scope.

  1. 01Scope the target portfolio to the facilities under evaluation, keyed by CCN.
  2. 02Resolve each facility's ownership chain — managing organization, operating organization, individual owners — from the CMS SNF All Owners record.
  3. 03Overlay the operating signal: PBJ staffing trend and the G+ deficiency history, joined to the same facilities.
  4. 04Export the joined dataset with the CMS-file and observation metadata available for source-linked values.
  5. 05Hand counsel a record they can re-derive: the federal source, not a commercial interpretation, underwrites the enforcement exposure.

Sample audit-evidence artifact

M&A DILIGENCE — FACILITY OWNERSHIP RECORD
Facility (CCN) ...... 015009
Operating org ....... [present]        [SNF All Owners · 2026-05-01]
Owner records ....... 3                [SNF All Owners · 2026-05-01]
Ownership % ......... null (absent in source) — flagged, not imputed
PBJ staffing trend .. declining RN hrs [PBJ · 2026-05-01]
G+ deficiencies ..... 2 in 36 months   [Care Compare NH · 2026-05-01]
Methodology ......... ownership/v1
Re-derivable ........ GET /api/v1/ask?question=ownership&scheme=ccn&value=015009

The exported record preserves linked federal provenance metadata so counsel can re-derive source-linked values from the named CMS input.


Proof — not logos

The displayed study figures cite public CMS inputs.

280,207Source: CMS SNF All Owners

Ownership rows

The dated CMS SNF All Owners study snapshot across 14,425 facilities — managing organizations, operating organizations, and individual owners, PECOS-derived.

418,148Source: CMS Care Compare — Nursing Home Compare · As of 2026-05-07

Deficiency citations

The CMS Care Compare citation record across 14,635 facilities — each with deficiency tag, harm scope, and survey event ID, openly downloadable.

ownership/v1

Methodology version

The version documents the query method. Re-deriving a past record also requires the retained source snapshot; methodology alone does not preserve history.

Scoped

Attestation

An export can include separate snapshot-attestation metadata where present. It does not create a deterministic signature link for every diligence fact.

“Counsel underwrites the federal record, not a vendor's interpretation of it. The source, the snapshot, and the documented gap are the product.”

M&A & NETWORK DILIGENCE

Resolve a target portfolio's ownership and enforcement history.

Request access→ Explore the SNF ownership data

Questions

Before the security questionnaire.

What federal data backs an M&A or network-diligence review?

Three CMS layers, joined by facility. CMS SNF All Owners —

280,207Source: CMS SNF All Owners
PECOS-derived ownership rows across 14,425 facilities, capturing managing organization, operating organization, and individual owner percentage interests. CMS PBJ Daily Nurse Staffing — daily payroll-hour records per quarter across 14,537 facilities. CMS Care Compare NH Deficiencies — citation records across 14,635 facilities, including deficiency tags, harm scope, and survey event IDs when present. Displayed citations identify the originating CMS file and observation date.

Can I resolve the ownership chain for a target portfolio?

Yes. The CMS SNF All Owners record resolves managing organization, operating organization, and individual owners with percentage interest and role type, keyed by facility. A material caveat surfaces directly in the federal file: a Health Affairs 2024 analysis, reproducible from the public CMS data, found

82.4%Source: CMS SNF All Owners
of top-10-chain rows carry a missing ownership_percentage. Fonteum surfaces that gap as a documented limitation rather than imputing a value — because to an acquirer, an absent percentage is itself material.

How is this different from a commercial healthcare-intelligence dataset?

The data property, not the vendor. A derived dataset typically surfaces CMS data as a rolled-up score with no path back to the underlying record. Fonteum publishes the CMS citation itself — deficiency tag, harm scope, survey event ID — alongside the source citation and methodology version, so counsel underwrites against the federal record rather than an interpretation of it. The full set of

418,148Source: CMS Care Compare — Nursing Home Compare · As of 2026-05-07
citations across 14,635 facilities is openly downloadable.

Why does the PBJ staffing layer matter more after the 2025 rule rescission?

CMS Payroll-Based Journal data reports actual RN, LPN, and CNA payroll hours —

1.3M+Source: CMS PBJ Daily Nurse Staffing · As of 2025-06-30
daily records per quarter across 14,537 facilities. The federal 3.48-hour minimum staffing standard was rescinded December 3, 2025 (effective February 2, 2026), so there is no national floor to underwrite against — which makes per-facility staffing transparency the remaining accountability signal. A facility drifting toward contract-heavy or sustained-low RN hours shows in the payroll record before a star-rating change or a survey deficiency.

What is the G+ harm flag and why is it the regulatory-risk floor?

CMS assigns each survey deficiency a scope-and-severity letter from A to L. Citations at G or above denote actual harm to a resident and carry the heaviest enforcement consequences, including civil monetary penalties and denial of payment for new admissions. In the federal record of

418,148Source: CMS Care Compare — Nursing Home Compare · As of 2026-05-07
citations across 14,635 facilities, fall at G or above. Because a G+ citation marks realized harm with documented enforcement exposure, a target's G+ history is the minimum any diligence model must price in.

Is any patient data involved?

No. Every layer is public federal record keyed by CCN, NPI, and PECOS-ID. There is no PHI in the pipeline and none is required to resolve ownership, read a staffing trend, or pull a deficiency history.

Go deeper

The data and research behind the diligence record.

Solutions

All solutions — by use case & buyer →

Platform

The capability layer — entity graph & bulk export →

Data catalog

CMS SNF All Owners →

Data catalog

CMS PBJ daily nurse staffing →

Brand hub

Ownership & chain analysis →

Research

Nursing-home ownership concentration →

Research

Hospital ownership changes (CHOW) →

Research

Nursing-home deficiency correction time →

Developers

API, FHIR, and bulk export — the dev hub →

FONTEUM · M&A DILIGENCE

Run network diligence on public federal data only. No PHI.

Request access→ Read the methodology

What’s on file, by the numbers

Platform snapshot · 2026-07-15

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file
26.2Msource-linked factsSource-linked field facts in the dated platform snapshot
—sources liveCrosswalk-resolved sources with a proved content transition in 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

Built on the authoritative federal record

The primary sources, named on every page.

These are the federal agencies whose public datasets Fonteum ingests and attributes — the issuing authorities, not customers or partners. Every figure on the site links back to one of them.

  • CMS
  • HHS-OIG
  • HRSA
  • FDA
  • NLM
  • NUCC
  • Census
  • BLS
  • BEA

See the full source registry, with license and refresh cadence for each →

Reproducible by design

Published figures name their source and date.

Source and date

Published research identifies its government file and observation date. Source-file SHA-256 coverage is disclosed separately; facts do not currently link deterministically to signatures.

Reproducible SQL

Each study ships the exact query behind its figures, run against the same dated copy of the federal file we used. Re-run it yourself.

Daily observations

The platform records table row counts daily. Those observations 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 →

Fonteum
Platform
Platform overviewAPIFor AI agents (MCP)FHIR R4 APIBulk exportAudit packReconciliationAI answers with sourcesHow records link upHistory
Solutions
All solutionsExclusion & sanctions screeningCredentialing & enrichmentAudit evidenceProvider data for AI / RAGUse casesM&A & network diligenceCompliance & riskJournalists & newsroomsDevelopers & AI teams
Data & sources
Coverage & sourcesBrowse all datasetsState Medicaid exclusionsFreshnessMethodologyCare CompareNursing homesRecall recordsSanctions screeningOIG LEIE listOwnershipStaffingDeficienciesSpecial Focus Facilities
Federal contracting
OverviewAwards during active exclusionFederal debarment scorecardProcurement questionsContractor lookup8(a) certification guide
Developers
Developer hubDocsAPI referenceQuickstartStatusChangelogSDKs & integrationsWebhooks
Research & guides
Research hubLearnHow it worksGuidesHealthcare provider dataExclusion & sanctions screeningProvider credentialing dataHealthcare data for AIHospital margin gapProvider access gapsGlossaryComparisonsSourced data vs plain LLM answersCitationsManifestoWhy Fonteum
Company
AboutPressCustomersPricingContactEditorial policyCorrections
Trust & legal
TrustTrust markQualitySecurityPrivacy policyTerms of serviceAPI termsMedical disclaimer

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

© 2026 Fonteum LLC. All rights reserved.

·hello@fonteum.com

A public-records graph that exposes source and observation metadata where supplied.

Fonteum's provenance ledger contained 26.2M source-linked facts on July 12, 2026. All but 14 carried a source-file SHA-256; 0 linked deterministically to a signature. Inspect a supplied snapshot id at fonteum.com/verify · source-mark coverage and limitations.
Request access→