In Value-Based Care, You Get Paid for Outcomes. Disconnected Systems Quietly Tax Them.

Value-based care changes the question. Under fee-for-service, you’re paid for volume — the visit, the test, the procedure. Under value-based care, a growing share of Medicare and Medicaid reimbursement is tied to outcomes, quality scores, and the total cost of caring for a population you’re accountable for — whether those patients walk in or not.

Ask the industry how digital transformation supports that shift and you’ll get a shopping list: interoperable EHRs, AI risk stratification, remote patient monitoring, telehealth, patient portals. All of it real. All of it useful. And all of it built on two assumptions that, in the organizations most under pressure to make value-based care pay, quietly don’t hold. The first: that your systems can actually talk to each other. The second: that the patient can get through the front door in the first place.

Your EHR was never the whole record

Here’s the part that gets glossed over: even a modern, well-run health system doesn’t keep its clinical data in one place. The EHR is the hub, but the record is spread across it by design — lab results in a laboratory system, images in radiology and PACS, medications in pharmacy, the patient’s identity and visits in registration and admission-discharge-transfer, the money in billing and claims, outreach in a separate engagement platform. That’s the normal state of a capable organization, not a broken one. It’s also why health systems stand up data warehouses and data lakes in the first place — to pull those silos into one longitudinal view.

Now add the two things that turn a manageable spread into a real cost: a legacy platform old enough that it can’t exchange data cleanly with newer tools, and the acquisitions that leave two, three, four of each of those systems running side by side because no one had the mandate or the runway to merge them.

The break shows up in two places at once

When those systems don’t agree, it fails in two places at the same time. The physician feels it first — toggling between systems, piecing a history together from fragments, never quite sure they’re seeing the whole patient. And the patient feels it at the front door — a provider directory a specialty behind, a booking flow that can’t see a referral, a portal that contradicts what the office just said.

Under fee-for-service, that’s friction. Under value-based care, it’s margin: the care that gets deferred, duplicated, or leaked out of network when systems disagree is care you’re now financially accountable for.

What I don’t touch — and what I’ll still tell you

Let me be precise about my lane. I don’t rip out or run your EHR, your lab system, or your imaging archive. Those are IT-owned clinical systems, and keeping them is often the right call. But not implementing a system doesn’t mean staying quiet about it. I can tell you whether it can integrate with what you’re trying to add, what that will realistically take, and where it’s quietly costing you at the front door — and I can sit in the diligence, the vendor conversations, and the roadmap decisions as counsel. A recommendation doesn’t require me to hold the wrench.

The best case isn’t rip-and-replace. It’s making everything agree.

In the best version of this, no one works from a partial picture. A master data layer — a single source of truth — pulls the clinical, operational, provider, and location data into one complete view, so a physician works from one system with the whole record even though the source data still lives where it always did. You don’t have to consolidate every system to stop them from disagreeing. You have to make them agree.

And the same reconciled data does triple duty: it gives the physician the complete record, it feeds the patient-facing front door so what a patient sees is finally true, and it feeds the quality and cost reporting your value-based contracts are graded on. One integration problem, solved once, pays off in three directions.

Where systems genuinely can’t be salvaged, consolidation is the other path — the same post-acquisition work of collapsing many platforms into one. Which route fits is exactly what the diagnosis is for.

I’ve done this against a deadline that couldn’t move

This isn’t theoretical for me. During a 2021 launch of a new self-collection service across more than 500 locations at a large healthcare company, accurate, real-time availability had to be pulled from two systems at once — the legacy database being retired and its pre-release, internal-only replacement — against a hard, immovable date. Nothing about that launch could wait for the new system to be finished. The answer was to architect around both at once, so the public experience worked flawlessly while the systems behind it were made to agree. That is this exact problem, solved under pressure.

Value-based care doesn’t reward the organization with the most clinical technology. It rewards the one whose systems agree — with each other, and with the patient. That’s not a care problem. It’s a front-door and data problem. And it’s the one I do.

Sources: Care Fragmentation, Quality, and Costs Among Chronically Ill Patients, American Journal of Managed Care — highly fragmented care nearly doubled annual cost ($10,396 vs. $5,854), with more preventable hospitalizations and care gaps (506,376 patients). U.S. Senate Finance Committee ghost-network secret-shopper study — 33% of Medicare Advantage provider-directory listings inaccurate or unreachable (2023). American Medical Association physician survey — 52% of physicians report patients hit inaccurate-directory coverage problems at least monthly (2017–2018). Office of the National Coordinator for Health IT — 71% of hospitals had routine access to outside records, but only 42% of clinicians used it often. Building a Healthcare Data Warehouse, Frontiers in Digital Health (2025); Linking Patient Encounters Across Primary and Ancillary EHR Systems, National Library of Medicine / PMC (2024).