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.
| Scheme | Value | Source table | Link method | Confidence | Since | Provenance |
|---|---|---|---|---|---|---|
| pac_id | 5294223038 | snf_all_owners | deterministic_pac_in_all_owners | 1.000 | 2026-06-14 | evidencerecorded: 2026-06-14 methodology: entity-graph/v1 evidence: {"rule":"D-OWNER","source_pk":145389,"type_owner":"I","enrollment_id":"O20150219001262"} |
Graph edges
One-hop relationships — ownership, chain membership, operation — each backed by a federal source row.
| Relationship | Entity | Confidence | Source table | Provenance |
|---|---|---|---|---|
| owns → | BEAVER VALLEY HOSPITAL (UT) | 1.000 | snf_all_owners | evidencerecorded: 2026-06-14 methodology: entity-graph/v1 attributes: {"role_code":"41","association_date":"09/18/2018","percentage_ownership":14} evidence: {"rule":"D-OWNER","owner_pac":"5294223038","source_pk":147879,"type_owner":"I","enrollment_id":"O20150513000350","role_code_owner":"41","role_text_owner":"CORPORATE DIRECTOR","dst_resolved_via":"pac_id","percentage_ownership_raw":14,"enrollment_organization_name":"BEAVER VALLEY HOSPITAL"} |
| owns → | BEAVER VALLEY HOSPITAL (UT) | 1.000 | snf_all_owners | evidencerecorded: 2026-06-16 methodology: entity-graph/v1 attributes: {"role_code":"41","association_date":"09/18/2018","percentage_ownership":14} evidence: {"rule":"D-OWNER","owner_pac":"5294223038","source_pk":145389,"type_owner":"I","enrollment_id":"O20150219001262","role_code_owner":"41","role_text_owner":"CORPORATE DIRECTOR","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":14,"enrollment_organization_name":"BEAVER VALLEY HOSPITAL"} |
| owns → | BEAVER VALLEY HOSPITAL (UT) | 1.000 | snf_all_owners | evidencerecorded: 2026-06-16 methodology: entity-graph/v1 attributes: {"role_code":"41","association_date":"09/18/2018","percentage_ownership":14} evidence: {"rule":"D-OWNER","owner_pac":"5294223038","source_pk":145409,"type_owner":"I","enrollment_id":"O20150219001347","role_code_owner":"41","role_text_owner":"CORPORATE DIRECTOR","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":14,"enrollment_organization_name":"BEAVER VALLEY HOSPITAL"} |
| owns → | BEAVER VALLEY HOSPITAL (UT) | 1.000 | snf_all_owners | evidencerecorded: 2026-06-16 methodology: entity-graph/v1 attributes: {"role_code":"41","association_date":"09/18/2018","percentage_ownership":14} evidence: {"rule":"D-OWNER","owner_pac":"5294223038","source_pk":147879,"type_owner":"I","enrollment_id":"O20150513000350","role_code_owner":"41","role_text_owner":"CORPORATE DIRECTOR","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":14,"enrollment_organization_name":"BEAVER VALLEY HOSPITAL"} |
| owns → | BEAVER VALLEY HOSPITAL (UT) | 1.000 | snf_all_owners | evidencerecorded: 2026-06-16 methodology: entity-graph/v1 attributes: {"role_code":"41","association_date":"09/18/2018","percentage_ownership":14} evidence: {"rule":"D-OWNER","owner_pac":"5294223038","source_pk":154829,"type_owner":"I","enrollment_id":"O20160104000977","role_code_owner":"41","role_text_owner":"CORPORATE DIRECTOR","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":14,"enrollment_organization_name":"BEAVER VALLEY HOSPITAL"} |
| owns → | BEAVER VALLEY HOSPITAL (UT) | 1.000 | snf_all_owners | evidencerecorded: 2026-06-16 methodology: entity-graph/v1 attributes: {"role_code":"63","association_date":"09/18/2018","percentage_ownership":null} evidence: {"rule":"D-OWNER","owner_pac":"5294223038","source_pk":161970,"type_owner":"I","enrollment_id":"O20161123000166","role_code_owner":"63","role_text_owner":"MANAGING CONTROL - GOVERNING BODY","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":null,"enrollment_organization_name":"BEAVER VALLEY HOSPITAL"} |
Current record
Current claims returned for this entity, grouped by provenance subject. The table exposes the source identifier recorded for each claim.
Point-in-time
Query retained claim coordinates under bitemporal-read/v1. Most facts have no superseded row; dates outside retained coverage may return no prior version, and diffs require both coordinates.
Pick a date to reconstruct, or two dates to diff. Equivalent JSON: /api/v1/history/{subject_type}/{subject_id}?at=… and …/diff?from=…&to=…