LCS-SP LLC

Cross-source identifiers

Every current identifier attachment, with the link method and confidence carried verbatim — deterministic links are 1.000; probabilistic links surface their real matcher confidence, never rounded up.

Current identifier attachments with link confidence
Scheme	Value	Source table	Link method	Confidence	Since	Provenance
npi	1306259122	nppes_providers	deterministic_pk	1.000	2026-06-10	evidence recorded: 2026-06-10 methodology: entity-graph/v1 evidence: {"rule":"D-NPI","source_pk":"1306259122","entity_type_code":"2"}
pac_id	8527284850	pecos_providers	exact_npi_in_pecos	1.000

Graph edges

One-hop relationships — ownership, chain membership, operation — each backed by a federal source row.

Current 1-hop graph edges
Relationship	Entity	Confidence	Source table	Provenance
← owns	ALAN NAUL	1.000	snf_all_owners	evidence

Current record

Every current claim asserted about this entity, grouped by provenance subject. Each cell carries its upstream federal source.

org · 1306259122 JSON

Current claims for org 1306259122
Metric	Value	Asserted	Source
dba_name	<UNAVAIL>	2026-06-10	Centers for Medicare & Medicaid Services

Provider screening signals

NPI-keyed source families read directly for 1306259122: federal and state integrity lists, CMS Open Payments, Order and Referring eligibility, Medicare opt-out, and enrollment revalidation. Each cell carries its own source and 14-tuple provenance. A screening aid — re-confirm any match against the primary source before acting; absence means nothing on file in the data Fonteum currently holds, never a guarantee none exists.

Sanctions & integrity

None on file

Nothing on file across the 14 integrity lists Fonteum currently holds — not a guarantee none exists elsewhere.

Screened: OIG LEIE, SAM.gov Exclusions, NY Medicaid (OMIG), OH Medicaid (ODM), GA Medicaid (DCH OIG), PA Medicaid (Medicheck), NC Medicaid (DHHS), MD Medicaid, WA Medicaid, IA Medicaid, MS Medicaid, MT Medicaid, OIG CIA, CMS Penalties

Source:OIG LEIE +13 moreChecked 2026-06-16

14-tuple provenance (14)

Point-in-time

Reconstruct this record as of any date, or diff it between two dates — both axes of the bitemporal store (bitemporal-read/v1): valid time (when a fact was true per the source) and recorded time (what the store knew when).

Pick a date to reconstruct, or two dates to diff. Equivalent JSON: /api/v1/history/{subject_type}/{subject_id}?at=… and …/diff?from=…&to=…

Cross-source identifiers

Graph edges

Current record

org · 1306259122 JSON

Provider screening signals

Sanctions & integrity

Point-in-time

Industry payments

Order & referring eligibility

Medicare opt-out

Revalidation