Ask a room of health system CIOs what’s slowing down data interoperability, and you might expect the answer to be technical: legacy systems, interface complexity, inconsistent standards. But in a recent CHIME-facilitated focus group convened by MRO, trust emerged as a more significant barrier than technology itself.
Specifically, the fear that sharing more data with payers means giving them more ammunition to deny claims, delay payment, or claw back revenue after the fact.
Why Providers Don’t Trust Payers with Their Data
One participant, describing their organization’s hesitation around expanding data sharing with payers, put it plainly:
“There’s a huge fear still that if we give this data to the payers, we know they’re going to abuse it, we know that they’re going to not pay us as much, just because of past experience. And so the friction point is, how do we get through that part? Once we start sharing that data, they’re going to grab more of it.”
The concern here is specific and experience-based. Providers believe data transparency will be used against them financially, not just operationally. The real issue is misalignment between payers and providers, sitting beyond questions of data governance or system integration, and no amount of better plumbing closes that gap.
EHR Payer Direct Access Creates a New Source of Provider Discomfort
Adding to the tension, many EHR platforms now offer payer direct access features, sometimes with incentive programs attached that reward providers for enabling deeper data connectivity. That puts organizations in an uncomfortable position: the platform they already trust with their clinical data is actively encouraging a kind of sharing that their finance and revenue cycle teams are actively wary of.
It raises a real strategic question for health system leaders. Is participating in these payer access programs a genuine opportunity to reduce administrative friction, or does it create new exposure to denials and clawbacks that outweighs the convenience? The honest answer from this group was that nobody has fully resolved that question yet. Most organizations are still working through it case by case.
Patients Pay the Price for Payer-Provider Misalignment
The payer-provider trust gap doesn’t stay contained to back-office negotiations. It shows up directly in the patient experience, most visibly around cost transparency. One participant described the frustration in very personal terms:
“Why does it take three weeks to get an estimate, and then that estimate is not what I’m going to get a bill for from the provider?”
The comparison that came up naturally in the room was retail and e-commerce. Patients now expect the kind of pricing clarity and tracking they get from an online purchase, and healthcare consistently falls short of that bar. Part of the reason it falls short isn’t a lack of data. It’s that the underlying payer-provider relationship makes real-time, reliable estimates harder to produce and stand behind, since so much of the actual reimbursement picture depends on negotiations and adjudication that happen well after the fact.
3 Steps Health Systems Are Taking to Reduce Payer Data Sharing Friction
None of the leaders in this discussion described a clean solution. But a few practical patterns emerged from how they’re navigating the tension:
- Evaluating payer access features case by case, not wholesale. Rather than treating “should we enable payer direct access” as a single yes or no decision, organizations are weighing specific features individually, looking at what data is exposed, to whom, and what the realistic downside risk is if that data is used to challenge a claim later.
- Investing in visibility into where data actually goes. One participant described working with legal and their EHR vendor to build a dashboard that surfaced exactly which data was being shared and in what volume, in part as a response to TEFCA participation requirements. That exercise brought to light that vendors weren’t fully disclosing who they were actually sharing data with downstream, a finding that reinforced why this kind of visibility matters well beyond payer relationships specifically.
- Treating this as a governance and contracting issue, not just a technical one. The organizations that seemed furthest along weren’t the ones with the most advanced integration technology. They were the ones that had brought legal, compliance, and IT together to actively review data-sharing agreements and interfaces on an ongoing basis, rather than setting them up once and letting them run indefinitely.
What It Actually Takes to Close the Payer-Provider Trust Gap
Neither better technology nor policy shifts like TEFCA will resolve payer-provider data friction on their own. It’s a trust problem sitting inside a much larger structural relationship, and the organizations navigating it most effectively right now are the ones treating it as exactly that: an ongoing negotiation to manage deliberately, not a one-time integration to complete and move on to the next thing.
For health system leaders, that likely means the right question isn’t “how do we share more data faster?” It’s “how do we share data in a way we can defend, explain, and audit if it’s ever challenged?” That’s a slower, less exciting answer than most vendors offer, but based on what this group described, it’s also the more accurate one.
It’s also the approach MRO has built payer-facing work around. Rather than treating data sharing as a single connection to open up and forget about, MRO’s payer relations team maintains direct partnerships with the majority of health plans on behalf of our provider clients. This partnership specifically reduces the kind of abrasion described above before it turns into a denial or a dispute. On the compliance side, that means:
- Enforcing minimum necessary data disclosure by default
- Running multi-layered quality checks on what’s actually being released
- Giving provider organizations real visibility into exactly what’s being shared, with whom, and how often
If a payer relationship is ever challenged, there’s a clear, auditable record to point to rather than a guess. It’s not a faster fix. It’s a more defensible one, which is the tradeoff most of the leaders in this discussion were actually asking for.
This post draws on insights from a CHIME-facilitated focus group of healthcare IT and informatics leaders convened by MRO. Participant identities have been kept anonymous by mutual agreement.
