Healthcare has spent 15 years building the pipes. The next problem is harder: what flows through them is only as valuable as the identity underneath it.
A new quarterly insight report from First Analysis maps the full clinical data infrastructure stack across four eras, from early EHR digitization through today’s emerging systems of action. Their analysis identifies a specific, non-negotiable prerequisite that sits beneath every exchange, normalization, and delivery capability in the stack. They call it the identity and data quality sub-layer. They name Verato® as the company that owns it.
This is not a niche distinction. It is an architectural one — and it explains why every investment your organization makes in interoperability, AI, risk adjustment, and care coordination depends on solving identity first.
The four-era framework and where identity fits
The layered technical architecture — including EHRs, exchange networks, normalization engines, and delivery tools — that moves clinical information from where it’s generated to where it’s needed.
First Analysis describes the evolution of clinical data in four eras: getting data into systems (2009–2018), getting systems to talk (2018–present), getting data to where it can do something (emerging now), and eventually getting out of the way entirely as AI agents act autonomously. Each era builds on the one below it.
Running beneath all four eras is what First Analysis calls the persistent infrastructure layer — the exchange and transport substrate on which every successive application era runs. Within that substrate, they identify three critical sub-layers: data exchange, clinical terminology, and identity and data quality.
Verato sits in the identity and data quality sub-layer. The report is direct about why: exchange only works if the patient on the other end is reliably identified and the data arriving is clean. The “who is this patient?” question is not a feature. It is a precondition.
What an integration engine cannot solve
A system that creates and maintains a single, authoritative identifier for each patient across multiple disparate source systems — clinical, claims, and administrative. An enterprise master patient index (EMPI) extends this capability across health system or network boundaries.
HL7 v2 is the legacy messaging standard still used by most health systems for real-time clinical event notifications (ADT, lab results, orders). FHIR (Fast Healthcare Interoperability Resources) is the modern API-based standard mandated by the 21st Century Cures Act. Both require clean patient identity to function reliably.
Tools like Rhapsody are integration and normalization engines. Their strength is HL7 v2 message translation — converting the legacy clinical message infrastructure that most health systems still run into formats that modern analytics and application platforms can consume. That work is real and strategically important.
But normalization assumes the records being normalized belong to the right patient. An integration engine translates message format. It does not resolve identity. If the same patient exists as three separate records across your source systems — one from the EHR, one from the claims system, one from a community health encounter — a normalization engine passes all three downstream. The fragmentation travels with the data.
Duplicate records occur when the same patient is registered more than once across one or more systems, often with slight variations in name, date of birth, or address. Industry estimates suggest 8–12% of patient records in large health systems are duplicates, with rates rising significantly across organizations following mergers and acquisitions.
This is the gap Verato® fills. Verato MDM Cloud™ applies Verato Referential Matching® — a patented, third-generation approach to referential matching powered by a proprietary reference database of more than 350 million patient identities — to resolve who a patient actually is before that record enters the exchange layer. The result is that the data flowing through integration engines, FHIR APIs, and analytics platforms is matched to a verified, deduplicated identity. The pipes carry clean signal.
Why this matters differently for payers and providers
- Hierarchical Condition Category (HCC) coding is the mechanism Medicare Advantage plans use to document member health complexity for risk-adjusted reimbursement. Inaccurate or incomplete HCC capture — often caused by clinical data that never reaches the payer — results in revenue leakage.
- HEDIS (Healthcare Effectiveness Data and Information Set) measures are the standardized quality metrics used to calculate Star Ratings for Medicare Advantage plans. Star Rating performance drives significant bonus payment eligibility. A meaningful portion of open quality gaps represent care that was delivered but never documented in a form the plan’s systems can recognize.
For payers, identity errors are a revenue problem. When clinical evidence fails to reach the plan’s systems because it was attached to a mismatched or duplicate record, the plan under-captures HCC codes and understates member complexity. Risk adjustment leakage follows. HEDIS gaps stay open not because care wasn’t delivered, but because the data trail broke at the identity layer.
For providers, identity errors are a care quality problem and a cost problem simultaneously. Mismatched records at transitions of care — the highest-risk moments in any patient journey — mean the home health nurse, the skilled nursing facility admissions team, and the specialist seeing a referred patient are all making decisions with incomplete information. The 47-page PDF discharge summary that arrives two days late is, at its root, an identity and data quality failure.
Patient matching is the process of determining whether records from different systems belong to the same individual. Accurate patient matching is required for safe care transitions, accurate risk adjustment, interoperability compliance, and AI/analytics model performance.
Identity is AI’s first dependency
AI applications in healthcare — including ambient documentation, prospective risk capture, prior authorization automation, and autonomous agentic workflows — depend entirely on the quality and accuracy of the underlying patient data. Identity accuracy is not operational overhead for AI; it is infrastructure.
First Analysis frames this cleanly in their report: every AI initiative at a health plan that runs into its data pipelines as the binding constraint is a potential customer for the action layer. Autonomous agents need clean, trusted, governed data at machine speed.
AI models do not improve bad identity data. They inherit it. A population health model trained on fragmented, duplicated records produces fragmented, duplicated insights. A care gap alert surfaced to the wrong patient record is not a feature — it is a liability. The organizations deploying AI in care management, risk adjustment, and prior authorization today are discovering that their data pipelines are the constraint, and that the constraint begins at identity.
Verato resolves it upstream, before the AI ever runs.
What independent validation looks like
The market is not quietly converging on this conclusion. It is loudly arriving at it from multiple directions simultaneously.
Verato® has been named the #1 vendor in Enterprise Patient Identity, Enterprise Master Patient Index (EMPI), and Patient Matching for Revenue Cycle Management in Black Book Research’s 2026 State of Health & Hospital Systems RCM Technology & Services report. Verato has also been recognized in the 2026 Gartner Magic Quadrant for Master Data Management (MDM).
And in Snowflake’s “The Modern Marketing Data Stack 2026: Governing the Agentic Enterprise” report — which tracks the technologies gaining the most active traction inside Snowflake’s customer base across more than 11,100 organizations — Verato® was named “One to Watch” in the Integration and Data Modeling category.
An agentic enterprise uses AI agents that can autonomously query data sources, interpret results, and take action — without human initiation at each step. For these agents to function reliably, the underlying data must be accurate, governed, and attached to verified identities. Identity resolution is the enabling prerequisite for the agentic enterprise.
The Snowflake recognition matters beyond the headline. Snowflake is where enterprise data platforms are consolidating. It is where health plans, health systems, and life sciences organizations are running analytics, AI workloads, and increasingly, agentic applications. Being named a One to Watch in Integration and Data Modeling in that ecosystem signals that Verato’s identity layer is being pulled into the data stacks that will power the next generation of healthcare AI — not as a compliance checkbox, but as a functional dependency.
These are not self-reported rankings. Together — First Analysis, Black Book Research, Gartner, and Snowflake — they represent a convergence of independent analyst validation, peer-reviewed customer assessment, and platform ecosystem data. The conclusion is consistent across all four: identity is the foundation layer, and Verato is the company that owns it.
The precondition is the opportunity
Healthcare interoperability has spent a decade focused on the pipes — the exchange standards, the FHIR APIs, the TEFCA networks. That infrastructure is now largely built. The value question has shifted: what flows through the pipes, and can it be trusted?
The answer depends on identity. A normalized record matched to the wrong patient creates clinical risk. A data liquidity network without trusted identity is a liability as much as an asset. The First Analysis framework makes this explicit: the identity and data quality sub-layer is not optional infrastructure.
It is the precondition.
Read the full First Analysis Quarterly Insight report to understand the complete clinical data infrastructure stack, how the four eras map to where value is being created, and why the exchange and transport layer — including the identity sub-layer — grows in strategic importance as application sophistication increases.
