Person 360 — both sides of one patient
Every row in person_360 is one real person, resolved across both sides of the
platform: their clinical record (encounters, conditions, medications from the
provider feed) sits beside their payer record (claims, enrolled member-months,
dollars) — stitched together by the same-as identity match. This is the payoff of
integrating clinical and payer data on one spine.
Resolved Persons
Clinical Encounters
Payer Claims
Total Paid
The whole resolved population, both sides at once
Each dot is one resolved person: their clinical volume (encounters) against their payer volume (claims). The clinical and payer sides move together because they describe the same people.
Pick a person — see both sides
Walker Kuhic
Resolved on ssn+name+dob · member
SUB000189-0 · - · -Clinical side — what the provider feed knows
Encounters
Conditions
Medications
Payer side — what the claims feed knows
Claims
Member-Months
Paid
Total Billed
In-Network Claim Rate
Their timeline — encounters and claims over time
The dated, both-sides story for Walker Kuhic — every
clinical encounter and payer claim, interleaved chronologically. This comes from
person_events, a separate person-grain event mart (person_360 above stays a
one-row-per-person summary); the person-resolution join lives in that mart, not
here — the page below only filters by the person picked above.