Skip to content
FonteumPublic-records evidence

TERMINAL · ENTITY CARD · ORGANIZATION

VENZA CARE ADMIN SERVICES LLC

Canonical entity in the resolved graph · NJ · methodology entity-graph/v1 · add1080e-341d-434d-a0ce-c6445a315874

active

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
SchemeValueSource tableLink methodConfidenceSinceProvenance
pac_id3870071210snf_all_ownersdeterministic_pac_in_all_owners1.0002026-06-14
evidence
recorded: 2026-06-14
methodology: entity-graph/v1
evidence: {"rule":"D-OWNER","source_pk":235295,"type_owner":"O","enrollment_id":"O20230427002743"}

Graph edges

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

Current 1-hop graph edges
RelationshipEntityConfidenceSource tableProvenance
owns →DECATUR SNF OPERATIONS LLC (AL)1.000snf_all_owners
evidence
recorded: 2026-06-16
methodology: entity-graph/v1
attributes: {"role_code":"43","association_date":"08/31/2025","percentage_ownership":null}
evidence: {"rule":"D-OWNER","owner_pac":"3870071210","source_pk":235295,"type_owner":"O","enrollment_id":"O20230427002743","role_code_owner":"43","role_text_owner":"OPERATIONAL/MANAGERIAL CONTROL","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":null,"enrollment_organization_name":"DECATUR SNF OPERATIONS LLC"}
owns →ADAMS SNF OPERATIONS LLC (AL)1.000snf_all_owners
evidence
recorded: 2026-06-16
methodology: entity-graph/v1
attributes: {"role_code":"43","association_date":"08/31/2025","percentage_ownership":null}
evidence: {"rule":"D-OWNER","owner_pac":"3870071210","source_pk":235492,"type_owner":"O","enrollment_id":"O20230503000624","role_code_owner":"43","role_text_owner":"OPERATIONAL/MANAGERIAL CONTROL","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":null,"enrollment_organization_name":"ADAMS SNF OPERATIONS LLC"}
owns →REGENCY HOUSE SNF OPERATIONS LLC (LA)1.000snf_all_owners
evidence
recorded: 2026-06-16
methodology: entity-graph/v1
attributes: {"role_code":"43","association_date":"08/31/2025","percentage_ownership":null}
evidence: {"rule":"D-OWNER","owner_pac":"3870071210","source_pk":263071,"type_owner":"O","enrollment_id":"O20241205002093","role_code_owner":"43","role_text_owner":"OPERATIONAL/MANAGERIAL CONTROL","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":null,"enrollment_organization_name":"REGENCY HOUSE SNF OPERATIONS LLC"}
owns →WHITESBURG SNF OPERATIONS LLC (AL)1.000snf_all_owners
evidence
recorded: 2026-06-16
methodology: entity-graph/v1
attributes: {"role_code":"43","association_date":"08/31/2025","percentage_ownership":null}
evidence: {"rule":"D-OWNER","owner_pac":"3870071210","source_pk":265229,"type_owner":"O","enrollment_id":"O20250128002724","role_code_owner":"43","role_text_owner":"OPERATIONAL/MANAGERIAL CONTROL","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":null,"enrollment_organization_name":"WHITESBURG SNF OPERATIONS LLC"}
owns →SMITHFIELD SNF OPERATIONS LLC (NC)1.000snf_all_owners
evidence
recorded: 2026-06-16
methodology: entity-graph/v1
attributes: {"role_code":"43","association_date":"08/31/2025","percentage_ownership":null}
evidence: {"rule":"D-OWNER","owner_pac":"3870071210","source_pk":278811,"type_owner":"O","enrollment_id":"O20251021002421","role_code_owner":"43","role_text_owner":"OPERATIONAL/MANAGERIAL CONTROL","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":null,"enrollment_organization_name":"SMITHFIELD SNF OPERATIONS LLC"}

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.

As of
Diff

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

Request access