Module 5

Data, Integration & Infrastructure

Understand the data flows that power Belong's platform — from payer claims to EHR data to real-time hospital alerts.

Core Data Sources

Payer Claims Feed

Medical, pharmacy, and lab claims. Lags 30–90 days but comprehensive.

ADT Notifications

Real-time hospital admission/discharge/transfer alerts. Critical for TOC.

EHR Data (FHIR)

Clinical notes, diagnoses, medications, labs from provider EMR systems.

Pharmacy Data

Medication fills and adherence data. Key for HEDIS medication adherence.

Member Demographics

Enrollment, eligibility, contact info from payer or CMS enrollment files.

SDOH Screening

Social determinants data from in-home assessments and community health workers.

The Integration Challenge

Belong operates across multiple health plan partners, each with different data formats, submission timelines, and API capabilities. Building a unified member record requires normalization across these sources — mapping ICD-10, CPT, NDC, and SNOMED codes into a coherent clinical picture.

Knowledge Check

Question 1 of 3

Why does Belong need claims data from the health plan?

💡 Reflection: If you were designing Belong's data pipeline, what would be the single most important real-time data feed to prioritize and why?

← Module 4Module 6: Regulatory & Contracting →