Let me paint a picture you might recognize.
You've invested in a slick population health platform. Your diabetes coaching program is live. Your hypertension trackers are deployed. Yet after six months, your costs haven't budged, your stop-loss carrier is rattling the cage, and your HR team can't figure out why engagement is flat.
I've been in this industry for two decades. I've seen this exact scenario play out dozens of times. You can rule out your vendors, and you can rule out your strategy. The culprit is a hidden data gap that almost nobody in benefits talks about.
You're trying to manage chronic disease using claims data that's 60 to 90 days old. That's like driving a car by looking only in the rearview mirror. Your population health program is managing history, not health.
The Data Gap Nobody Wants to Name
Your entire benefits ecosystem runs on medical claims. HIPAA standardized that billing language, and ERISA reporting rides on the same feeds. But claims data was never built for real-time care management. It's billing data - clean, standardized, and completely retrospective.
Take a diabetic employee in your plan. Here's what your claims data sees:
- An HbA1c lab from 85 days ago
- One ER visit for hypoglycemia last quarter
- A monthly insulin script filled on schedule
Now here's the clinical reality your PHM system misses completely:
- Their continuous glucose monitor shows dangerous overnight lows
- Their blood pressure cuff readings have been climbing for two weeks
- The doctor changed their medication, but the employee never picked up the new script because of a $75 copay
- A recent PCP note flags food insecurity - the member is skipping meals to afford insulin
Your wellness coaches call to talk about "medication adherence." The real problem is that the employee can't afford to eat. That information is locked in a doctor's EHR that your benefits system cannot touch. This is the administrative-clinical disconnect. It's the single biggest barrier to effective chronic disease management, and it's almost never addressed in benefits strategy.
Why This Gap Exists (Three Structural Traps)
Trap #1: HIPAA as a convenient excuse
I hear it all the time: "We can't share clinical data because of HIPAA." But the Privacy Rule permits uses and disclosures for treatment, payment, and health care operations. The regulation's definition of health care operations in 45 CFR 164.501 includes "population-based activities relating to improving health or reducing health care costs." The 2013 Omnibus Rule changed a different thing: it made business associates directly liable for HIPAA violations, which raised the stakes across your vendor chain. The real barrier is that the data-sharing agreements between your vendors simply don't exist. Nobody's demanded them.
Trap #2: Your stop-loss carrier is flying blind too
Your stop-loss underwriter is pricing your chronic disease risk using the same stale claims you are. They could request real-time lab or pharmacy feeds from your carriers. But their contracts don't require it. So your highest-risk claimants remain invisible until they hit a $100,000 claim - then everyone acts surprised.
Trap #3: Your vendor stack is a collection of silos
Your TPA, your wellness platform, your digital health apps, your EAP - each one keeps its own data. None of them talk to the local health system's EHR. The only shared layer is the carrier's claims warehouse, which again is months behind. Your PHM platform is operating in a blindfold.
Here's the Fix You Haven't Heard
Most benefits pros think they need to rip and replace their entire tech stack. They don't. The fix is much simpler: demand better data feeds from vendors you already use.
Your pharmacy benefit manager (PBM) sits at the center of real-time pharmacy data. Nearly every prescription claim is adjudicated in real time at the point of sale, so the moment a member fills, refills, or abandons a script, the PBM sees the drug, the dose, the prescriber, and the out-of-pocket amount. These are signals your PHM platform never sees, simply because nobody asked for them. Labs are different: most lab results bill through the medical side, not the pharmacy benefit, so they arrive with the rest of your claims unless you build a separate feed.
Here's what you can ask your PBM to do starting tomorrow:
- Flag a member who stops refilling a diabetes or blood pressure medication within a day of a missed fill, so a care manager can reach them before the gap widens.
- Trigger a secure notification to your care team the same day a member picks up a new GLP-1 or insulin, so someone can review the new prescription, the dose, and any side-effect risk.
- Use prior authorization and fill data to spot members whose hypertension therapy isn't working before they end up in the ER.
For HbA1c and other lab values, your PBM is usually not the source. Those results bill through the medical side and sit in lab and EHR systems. A feed from your lab vendor, a health information exchange, or a clinical data network closes that gap, and it is the same data use agreement conversation as the pharmacy feed.
This isn't futuristic. Pharmacy point-of-sale data already powers adherence and care-gap programs through networks like Surescripts, whose medication history feeds reach care management workflows. Extending that feed to your PHM platform is a contract change. The reason it isn't standard practice in your stack is that nobody has written the sharing into the vendor agreements. Change requires you, the employer, to demand faster, cleaner data.
The Compliance Path (Shorter Than You Think)
Will this raise HIPAA concerns? Yes. But they're manageable - and far smaller than most benefits leaders assume.
Under HIPAA, a business associate (your PBM) can disclose protected health information directly to another business associate (your PHM vendor) for the plan's health care operations, including population health, without routing it back through you first. Regulators have cautioned that HIPAA cannot be used to impede the flow of PHI for a plan's health care operations.
The catch: your business associate agreements must authorize the disclosure. Most don't. The fix is a data use agreement (DUA) between your plan, your PBM, and your PHM platform that spells out what can be shared and for what purpose. That's a legal step most teams skip. Don't. It takes a few hours with counsel and can unlock years of better care management.
Three Questions for Your Vendors Tomorrow
Take these to your next quarterly business review. Write them down. Ask for specific answers.
- "What's the average claim lag for lab data in our PHM queue - and can we get it in under 72 hours?" If they say 60 days, you have a data problem, not a program problem.
- "Does our PBM contract allow real-time pharmacy data sharing with our care management vendor? If not, what language do we need to add?" Most contracts don't. But they can be amended.
- "Are you using pharmacy claims at point-of-sale as a live signal, or only as a retrospective cost tracker?" If it's the latter, you're leaving a powerful resource untapped.
Real-Time Data Only Helps If Someone Acts on It
A faster flag is not the same as a better outcome. Clinical decision support has a well-documented failure mode called alert fatigue. When alerts fire too often or carry too little context, clinicians override them, and studies have measured override rates as high as 96%. A care manager who receives two hundred new pharmacy alerts a week will triage them the same way a doctor triages a noisy EHR.
When you negotiate the data feed, negotiate the workflow with it. Decide who receives each flag, how it gets prioritized, and what the first action is. A new-medication alert that reaches a nurse who can call the member the same day is valuable. The same alert dropped into a dashboard nobody opens is another number. Demand one signal that reliably turns into one action.
The Real Bottom Line
Population health management for chronic disease will never reach its potential until your benefits system sees what the clinician sees in near real time, and until someone is accountable for acting on it. The technology exists. The compliance path is clear. What's missing is employer demand for the data and for the workflow around it.
Stop flying blind. Demand the data your employees' doctors already have, and pair it with a workflow that acts on it. Your population's health and your plan's bottom line depend on it.
Have you integrated real-time clinical data into your PHM program? I'd love to hear what worked and what didn't. Drop a comment or connect.
This article is for general information only and is not legal, tax, or medical advice. Employers should consult their own advisors.