Last month, your wellness dashboard probably showed some pretty impressive telehealth adoption numbers. Your health plan sent over a glossy report about their state-of-the-art EHR integration. Everything looks great on paper.
Those reports left out one detail: these systems barely communicate. And that gap is quietly creating two completely different healthcare experiences inside the same benefits plan. Your frontline employees are getting the worse one.
Two Employees, Same Plan, Completely Different Care
Meet Sarah and Marcus. Same company, same health plan, both used telehealth last month for new health issues.
Sarah's a salaried marketing manager with an established relationship with her primary care doctor. She used telehealth for a UTI while traveling, and the visit notes automatically showed up in her PCP's system. Two weeks later, when she followed up in person, her doctor had the complete picture. No duplicated tests, no confusion, a clean handoff.
Marcus works in the warehouse on rotating shifts. He hasn't established a regular doctor. When is he supposed to go? He uses telehealth as his primary care because he can access it from his phone during breaks. Last month, he got prescribed medication for high blood pressure through a telehealth visit.
Three weeks later, Marcus injured his shoulder at work and went to urgent care. The doctor pulled up his records and saw nothing about that blood pressure medication or the telehealth visit that produced it. The urgent care team prescribed pain medication that interacts badly with blood pressure meds. Your pharmacy benefit manager never flagged it because those prescriptions came from disconnected systems.
This exact scenario is playing out hundreds of times across your employee population right now. And you're paying for every instance.
The Hidden Costs Buried in Your Claims Data
I've spent years analyzing claims data from mid-sized employers. Once you know what patterns to look for, they jump off the page:
Duplicated diagnostic testing: Between 5-8% of employees undergo repeated tests within 60 days because providers can't see results from telehealth visits. Each duplication costs $240 to $1,200.
Preventable ER visits: About 2-3% of telehealth users end up in emergency rooms for conditions recently addressed virtually. Why? Because ER physicians can't access telehealth notes and start from scratch. That's an extra $1,500 to $8,000 per visit that shouldn't have happened.
Medication therapy failures: When telehealth prescriptions exist in a separate universe from primary care records, you get conflicting treatments, confused patients, and therapy failures requiring more expensive interventions. That's typically $2,000 to $5,000 in added costs per affected employee annually. A drug utilization review should catch an interaction when both fills route through the same PBM. It misses when a telehealth platform fills through its own pharmacy network or a discount program outside your PBM, or when the danger lives in clinical notes the PBM never sees.
Preventive care tracking breakdown: Your wellness incentive program can't see preventive services delivered through telehealth or retail clinics. So you're either over-rewarding based on employee attestation or under-rewarding employees who completed services that aren't visible to your tracking system.
For a company with 1,000 employees, these integration gaps conservatively cost around $140,000 annually. That's $140 per employee in pure waste buried in your overall claims trends.
Why Everyone Thinks Someone Else Solved This
Most benefits teams treat telehealth-EHR integration as an IT problem. Or they assume their vendors have it all figured out. That is a fundamental misunderstanding of where this issue lives.
Your telehealth vendor and your primary care providers' EHR systems are probably technically capable of communicating. They might even both proudly claim FHIR compliance, the industry's interoperability standard that was supposed to solve all this. But compliance doesn't equal actual data exchange.
The Economics Don't Support Real Integration
Telehealth vendors build deep integrations with large health systems, those enterprise customers who sign big contracts. But employer health plans get the bare minimum. Why? Because proper integration costs money. Employers have less negotiating leverage than hospital systems. And there's been little competitive pressure. Most employers don't ask detailed questions about integration depth during vendor selection.
So what you're probably getting: basic claims data and encounter codes. Patient X had a visit on Y date for Z diagnosis. What you're probably not getting: clinical notes, diagnostic images, treatment plans, medication reconciliation, care coordination notes, all the information that would enable actual care continuity.
Why the Data Still Doesn't Move
Even where technical integration exists, records still don't move the way employees assume.
An employee uses your telehealth benefit for a skin condition and gets a topical medication. Three weeks later, they see their PCP for a diabetes follow-up. The PCP's EHR shows no record of that prescription, which happens to interact with diabetes medications. HIPAA generally permits providers to share records for treatment without an authorization, so consent rarely explains the failure. The gap is technical and commercial: the telehealth platform and the PCP's EHR are separate systems, and integration gets built only when a customer pays for it or the law requires it. Where the data sits in a consumer-facing app, app-level permissions add another layer most employees never complete. They assume the systems talk to each other. They don't.
Standards That Don't Actually Standardize
Healthcare loves acronyms: HL7, FHIR, CCD, CCDA. Standardized data formats for interoperability. In practice, these standards have so many implementation options that two systems can be fully compliant yet unable to exchange meaningful data. It's like saying two people both speak English. True, but one speaks Shakespearean English and the other speaks contemporary Australian slang. Compliance doesn't guarantee comprehension.
Information Blocking Rules Changed the Baseline
The vendor incentive problem assumes interoperability stays voluntary and commercial: vendors build integrations only when a big customer pays for them. That assumption is dated. The 21st Century Cures Act's information blocking rule, administered by ONC, already prohibits health care providers, certified health IT developers, and health information networks from interfering with the access, exchange, or use of electronic health information. Reporting channels are live, and a third party can submit an information blocking claim on a client's behalf. ONC's 2025 guidance treats restricting a customer's choice of QHIN as interference.
TEFCA, the Trusted Exchange Framework and Common Agreement, is the operational piece. Several QHINs are now designated and operating, and the HTI-2 final rule published in December 2024 tightened the Manner Exception and QHIN governance. The practical effect for benefits leaders: you now have regulatory leverage in vendor negotiations that did not exist when telehealth platforms first shipped. The useful question is whether a vendor's current behavior would hold up under an information blocking complaint. That changes the economics of the integration-is-expensive excuse, and it is a lever most benefits teams have not yet pulled.
The Equity Problem That Should Keep You Up at Night
Poor telehealth-EHR integration disproportionately harms the employees who can least afford fragmented care.
Think about your typical salaried, benefits-literate employees. They generally have established PCP relationships with providers using strong EHR systems, use telehealth as a supplement, can manage consent processes, and have schedule flexibility to coordinate care. Now think about your hourly, frontline, service employees. They increasingly use telehealth as primary care because shift work makes regular visits nearly impossible. They don't have an established medical home, lack health literacy to recognize integration gaps, and can't afford time off to fix disconnected system problems.
The employees who most desperately need coordinated care, those juggling multiple jobs, facing transportation barriers, and carrying higher chronic disease burdens, are getting the most fragmented experience. And because they're often your highest healthcare utilizers, their fragmented care drives your total cost trends up.
What the Smart Innovators Are Doing Differently
Some innovative benefits models are tackling this by sidestepping traditional integration headaches. The WellthCare approach offers some instructive examples. WellthCare, the first Health-to-Wealth Benefit System, builds this parallel prevention record by rewarding every verified preventive action with store dollars and automatic retirement contributions, creating a portable health-to-wealth record employees own.
Building a Parallel Prevention Record
Instead of trying to achieve perfect EHR interoperability (which may never happen), create a lightweight, portable health record focused on preventive actions. Track high-value preventive activities across all care settings with standardized codes. This creates a single source of truth for prevention status that employees own and control. They can share it across providers without working through complex consent workflows. You don't need to consolidate all clinical data. You only need the data driving the behaviors you're incentivizing.
Multi-Source Verification Without Assuming Integration
Rather than relying on one data stream, pull from multiple sources: claims feeds from primary health plans, direct integrations with telehealth platforms where they exist, lab data feeds from Quest and LabCorp, pharmacy fill data, secure employee upload options, and AI-powered interpretation of unstructured clinical notes. Build redundant verification pathways that work despite system fragmentation.
Aligning Employee Incentives With Data Completeness
When employees benefit immediately from keeping their preventive actions visible, through instant Store dollars, automatic retirement contributions, and transparent reward balances, they become active participants in closing integration gaps.
The Concierge Layer That Fills the Gaps
An AI health concierge that works serves as a human-system interface. It can proactively ask employees about care received outside the primary system, guide them through data sharing processes, identify care gaps by asking about symptoms or concerns, and recommend when telehealth is appropriate versus in-person follow-up. Don't assume perfect technical integration will ever arrive. Build intelligent interfaces that compensate for system limitations while improving the employee experience.
What You Can Do Starting This Week
You don't need to rebuild everything tomorrow. Start with this phased approach.
Phase 1: Understand Your Current Reality (30–60 Days)
Audit your actual integration depth. Don't accept vendor marketing claims. Request sample data flows between your telehealth vendor and health plan. Ask for specific fields being transmitted: encounter codes only or full clinical notes? Frequency and reliability of transmission? Error rates and lag times? Pull claims data and compare: for a sample of employees who used telehealth last quarter, how many visits show up in their primary care EHR records? Calculate your integration completeness rate. Most organizations are shocked to discover it's below half.
Map your consent and data-sharing workflows. Document exactly what an employee must do to authorize data sharing across each platform. How many portals? How many separate consent actions or app permissions? Is this explained during enrollment? Calculate completion rate. If fewer than 30% have completed all steps, the blocker is the data-sharing path rather than the integration itself.
Analyze duplication and coordination failures. Pull claims data for the past year and look for patterns: diagnostic tests within 60 days of each other, multiple visits for the same diagnosis code across care settings, medication fills suggesting uncoordinated care, ER visits within 30 days of telehealth encounters. These patterns reveal where integration gaps cost you real money.
Phase 2: Quick Wins (60–90 Days)
Renegotiate vendor contracts with actual integration requirements. Specify what clinical data will be shared, in what format, how frequently, with what guarantees. Define specific FHIR implementation guides. Include uptime SLAs for data feeds, clear ownership of consent workflows, and financial penalties for integration failures below thresholds.
Fix your preventive care verification process. Move from claims-only verification to multi-source validation. Set up automatic verification when data flows through claims or EHR, but also create a secure employee portal for uploading documentation from services outside network. Use AI to extract structured data from PDFs. Build in grace periods with proactive outreach. Provide care coordinator support for complex cases.
Create integration navigators within your member services team. Train staff or health coaches to help employees understand why data sharing matters, walk through consent processes step by step, troubleshoot when records don't transfer, and manually bridge gaps for employees managing chronic conditions across providers.
Phase 3: Structural Solutions (6–12 Months)
Implement a health data aggregation layer. Create a central hub that aggregates data from telehealth, primary care, labs, pharmacy, and wearables. Normalize into standardized formats, make available to authorized providers, and feed prevention tracking systems. Vendors like Redox, Health Gorilla, and Particle Health offer this. These platforms typically price per transaction or API call rather than a flat per-employee fee, so cost scales with actual usage. It pays for itself quickly.
Pilot a prevention-first network design. Partner with primary care groups and telehealth vendors willing to commit to true integration. Offer lower copays for employees who establish care with integrated providers. Pay care coordination fees to PCPs. Set up shared savings when integration reduces duplicated services. Start with a volunteer population and measure outcomes against a control group. When you can show 20–30% waste reduction with better satisfaction, you'll have the business case to expand.
The ROI Case for Your CFO
Let me lay out conservative assumptions for a 1,000-employee population:
Annual Cost Savings: Reduced duplicated diagnostics: $25,000. Prevented ER visits: $10,000. Improved medication adherence: $30,000. Improved preventive care completion: $75,000. Total: $140,000.
Investment Required: Enhanced telehealth contract with integration requirements: $15,000/year. Health data aggregation platform: $30,000/year. Additional care coordination staff: $40,000/year. Total: $85,000.
Net Savings: $55,000 in Year 1. ROI: 65%.
These estimates don't include reduced absenteeism, improved retention, reduced HR staff time, or lower call volume. Scale to your population.
The Compliance Risks You're Already Taking
Poor integration also creates regulatory exposures: HIPAA concerns, incomplete audit trails, complicated access rights, nightmare breach notification. ACA preventive care requirements, risk of incorrect cost-sharing or quality reporting failures. Mental health parity, specialized mental health telehealth platforms often have limited EHR integration, potentially creating unequal care coordination. ERISA fiduciary duty, if integration failures cause unnecessary expenses and outcomes, and you're not addressing them, you may have exposure. These aren't theoretical. They're audit findings waiting to happen.
The Future Is Orchestration, Not Just Integration
The next evolution moves past connecting systems and toward intelligent care orchestration. An AI concierge that knows your complete health picture across platforms can proactively recommend: "Based on your telehealth visit last week, schedule this lab work. Here are three convenient locations, all verified as 100% covered." It identifies potential medication interactions, alerts you when screenings are due, and makes consent and data sharing automated and invisible. Parts of that technology exist today. The missing piece is benefits leaders who treat care coordination as a benefits design decision instead of an IT project.
What This Really Means
The telehealth-EHR integration gap reveals something fundamental: we've been buying tools instead of creating experiences. We negotiate contracts based on per-visit costs and network size. We evaluate EHR systems on feature checklists and compliance boxes. We measure wellness by participation rates. But we haven't asked: does this create a connected care experience for a single mother working two jobs, accessing care through her phone at 11 PM?
The winning benefits teams won't be the ones with the most vendors or fanciest technology. They'll treat integration as a feature of experience design rather than a technical spec. They'll build systems that work despite vendor limitations. They'll create verification that doesn't punish employees for system failures. They'll measure success by care continuity rather than utilization. They'll understand that one-size-fits-all integration creates one-size-fits-none care experiences.
Your Action Item for This Week
Pull claims data for employees who used telehealth last quarter. Compare against wellness tracking and primary care EHR records. Calculate three numbers: (1) percentage of telehealth visits appearing in primary care records, (2) percentage of preventive services delivered via telehealth captured in your wellness tracking, (3) number of duplicated diagnostic tests within 60 days of telehealth encounters. If those numbers trouble you, and they probably will, you have an integration problem worth solving.
Unlike many benefits challenges, this one has clear, measurable solutions that pay for themselves within the first year. The most innovative benefits strategies don't wait for the system to fix itself. They build coordination layers that work despite fragmentation. That's both good administration and fiduciary prudence.