What is Patient 360?

Patient 360 is a comprehensive data management solution within LakeFusion that creates a unified, real-time view of all patient-related information across the healthcare ecosystem. By leveraging Databricks Lakehouse technology, the solution harmonizes patient data from multiple sources, ensuring consistency, accuracy, and accessibility across clinical, operational, and administrative functions.

Sources Integrated

Patient 360 aggregates and standardizes data from the following systems:

• Electronic Health Record (EHR) systems

• Electronic Medical Record (EMR) systems

• Insurance claims and payment systems

• Patient demographic and eligibility databases

• Pharmacy and prescription systems

• Laboratory information systems

• Healthcare billing and transactional systems

• Operational performance metrics and analytics

Use Case

Source Records
Patient information originates from multiple systems, often containing unique yet overlapping data.
Example records:

• EHR System: Name – Jane Smithson, Email – jane.smith@gmail.com

• EMR System: Name – J Smith, Email – j.smith@yahoo.com

• Lab Information System: Name – Janette Smith, Email – jane.s@gmail.com

Consolidated Entity Creation
Once ingested into LakeFusion, records are consolidated into entities based on shared attributes such as name, email, or patient ID.
For example, Jane Smithson, J Smith, and Janette Smith are grouped under a single patient entity, preserving differences while enabling traceability.

Match Records
LakeFusion identifies duplicate or related records using:

• LLM Vector Search, which transforms attributes into vectors to calculate semantic similarity and capture variations in patient names or emails

• Custom Matching Rules, which apply field-specific logic for matching based on attributes like email address, phone number, or unique patient identifiers

Survivorship Rules
To reconcile conflicting data points, LakeFusion applies survivorship logic:

• Priority-Based Rules, such as trusting data from authoritative systems in the order: EHR > EMR > Lab Information System

• Recency-Based Rules, retaining the most up-to-date values when timestamped data is available

Merged Record
LakeFusion generates a Golden Record by selecting the most reliable and current attributes from the matched entities.
Example output:

• Final Name: Janette Smithson

• Final Email: j.smith@yahoo.com

Bronze, Silver, and Gold Data Tiers

Provider 360 aligns with the Medallion Architecture for structured data processing and consumption:

Tier	Description
Bronze	Raw ingestion of provider data from all integrated sources
Silver	Cleaned, standardized, deduplicated provider profiles
Gold	Verified Golden Records for operational use, network analysis, and reporting

This tiered architecture ensures data transparency, reusability, and performance across the provider lifecycle.