Category: Data & AI Infrastructure
A patient's path runs through primary care, specialists, hospitals, and pharmacies — but each system only sees its own segment, so the moments that matter most often happen in nobody's data.
The questions pharma teams ask most — where are patients lost before diagnosis, why is treatment started late or stopped early, what happens after a therapy switch — are questions about transitions between care settings. Those transitions are exactly where single-source data goes blind: the EHR sees what one health system did, claims see what was billed, and neither follows the patient across the boundary. Longitudinal patient-journey platforms link de-identified records across settings to reconstruct the path end to end, turning transition blind spots into analyzable events.
The foundation is linkage: de-identified records from claims, EHR, pharmacy, and lab sources are joined per patient through privacy-preserving tokens, producing a timeline of encounters, diagnoses, prescriptions, and procedures that spans care settings. On top of that timeline, analytics identify the patterns that matter — time from first symptom coding to specialist referral, gaps between diagnosis and treatment start, sequences that precede discontinuation. What these platforms honestly cannot see is anything that never generates a record: symptoms unreported, care sought outside the covered network, cash-pay medication, or the reasons behind a decision. Journey data shows what happened and when, not why — the 'why' still requires research designed to ask it.
Continuity is the property to test: a journey analysis is only as good as the platform's ability to keep following the same patient across settings and over years. Ask what fraction of patients in your indication have continuous multi-year observation across the data types your question needs, and how the platform handles patients who move between insurers or health systems — the exact moments where continuity typically breaks. Also probe the analytical layer. Prebuilt journey metrics embed definitions — what counts as a treatment gap, how a line of therapy is defined — and those definitions must be inspectable and adjustable, because a metric whose logic you can't see is a conclusion you can't defend.
Most teams begin with one well-defined journey question in one indication — commonly the diagnosis pathway (where patients stall before reaching the right specialist) or the treatment-persistence pathway (where and when discontinuation concentrates). Grounding the pilot in a question the brand or medical team already debates gives the output an immediate audience and a reality check: people who know the disease can tell quickly whether the reconstructed journey matches clinical reality or reflects a data artifact.
Never fully complete — coverage depends on which sources are linked and how long patients stay observable within them. Credible vendors quantify continuity for your specific cohort rather than asserting completeness. The practical standard is whether the observable journey is representative enough to support the decision at hand.
It can show where and when drop-off concentrates with real precision, which is often decisive by itself. But motivations — cost concerns, side effects, access barriers — usually leave no coded trace. Teams typically pair journey analytics with targeted primary research at the drop-off points the data reveals.
The linkage is performed on de-identified, tokenized records, and reputable platforms apply statistical safeguards against re-identification, particularly in small populations. Rare-disease work deserves extra scrutiny: ask specifically how the vendor protects cohorts small enough that a detailed journey could narrow to individuals.
Claims alone capture billed events within one payer relationship and lose the patient at every insurance change. Journey platforms link across payers, providers, and data types, and add the longitudinal analytics layer. Whether that difference matters depends on your question — utilization questions may not need it; transition questions almost always do.
Intercept Pharmaceuticals worked with Komodo Health to apply its Healthcare Map real-world data to primary biliary cholangitis, supporting patient-journey and treatment-pattern analyses for its Ocaliva franchise.
Vendor: Komodo Health · press release (Komodo Health (Business Wire)) · 2022-11-10 — Partner: Intercept Pharmaceuticals
Panalgo, a Norstella company, launched LinQNotes and Ella AI to speed real-world data analysis that supports market access and commercial decision-making.
Vendor: Norstella · press release (Norstella) · 2025-05-14