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. The problem isn't your vendors. It isn't your strategy. It's 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 isn't managing health. It's managing history.
The Data Gap Nobody Wants to Name
Your entire benefits ecosystem runs on medical claims. That's how ERISA and HIPAA were designed. 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? 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 actually permits sharing for treatment, payment, and health care operations - which explicitly includes population health activities. The 2013 Omnibus Rule made this crystal clear. The real barrier isn't the law. It's that 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 clinical data. Every time a member fills a script, the PBM sees it instantly. Every lab claim that runs through the pharmacy system triggers a data point. These are real-time signals your PHM platform never sees - simply because nobody asked for them.
Here's what you can ask your PBM to do starting tomorrow:
- Flag members with HbA1c above 9% within 24 hours of the lab claim - not 60 days later.
- Trigger a secure notification to your care team the same day a member picks up a new GLP-1 or insulin.
- Use prior authorization data to identify members with uncontrolled hypertension who are failing stepped therapy - before they end up in the ER.
This isn't futuristic. Large self-funded employers are already piloting these exact data feeds. The only reason it isn't standard practice is that vendors profit from data latency. They sell you dashboards that look impressive but are built on stale information. 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 share protected health information with another business associate (your PHM vendor) for health care operations, including population health. The 2013 Omnibus Rule explicitly supports this.
The catch: your contracts must authorize the disclosure. Most don't. You need a simple data use agreement (DUA) between your plan, your PBM, and your PHM platform. 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 clinical 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.
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. The technology exists. The compliance path is clear. What's missing is employer demand.
Stop flying blind. Demand the data your employees' doctors already have. 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.
