Value-Based Insurance Design is one of those ideas that sounds like a no-brainer. Make insulin cheap. Make mental health visits free. Nudge people away from that $3,000 MRI for simple back pain. It’s smart economics wrapped in a moral imperative, and it’s been the “next big thing” in benefits for almost twenty years now. Yet here we are, with only about one in five large employers actually doing anything meaningful with it. The standard explanation is that the ROI case hasn’t been made airtight enough. I don’t buy that for a second. The real reason VBID hasn’t scaled is far less shiny: your benefits technology stack is nowhere near ready for it, and neither is your compliance framework.
I’ve watched organizations spend a year trying to get a “simple” value-based copay to work correctly. One client-a Fortune 500 manufacturer-thought they’d rolled out a clean program: zero-dollar copays for guideline-directed meds after a heart attack. Should be easy, right? Eighteen months later, we were still debugging why the TPA’s accumulator wasn’t counting those zero-dollar fills toward the out-of-pocket max. Members were getting wrong EOBs, the call center was drowning, and we were dangerously close to an ERISA violation because the plan documents didn’t match reality. That’s not a clinical design failure. That’s an infrastructure failure dressed up as a benefits initiative.
The Integration Mess Nobody Talks About
Traditional plan design is dumb, and I mean that as a compliment. A fixed copay is a fixed copay. The claims system doesn’t need to know why you’re filling a drug or what your lab results are. VBID smashes that simplicity. It asks the claims engine to make clinical decisions. For the heart attack meds to be free, your PBM needs to know you had a heart attack-which means the medical carrier has to send diagnosis codes to the pharmacy side in near real time. Most carriers don’t do that. They don’t even speak a common data language. So you end up building or buying some middleware aggregation layer, complete with custom APIs, and you pray it doesn’t break every time someone updates a code set. This isn’t a one-time setup, either. It’s an ongoing integration maintenance tax.
And it’s not just pharmacy. Imagine you want to make low-value imaging more expensive at the point of care. That means the provider’s EHR has to flash a warning that your plan considers this test wasteful. We have almost no leverage to make that happen across a scattered network of provider systems. The fallback is retroactive claim re-pricing-your employee gets the MRI, thinks their cost is $50, and then weeks later an EOB arrives with a surprise $300 bill because it was flagged as low-value. That’s not “nudging.” That’s a trust-destroying bait-and-switch.
The Compliance Trapdoor
VBID’s whole premise is treating people differently based on their health. That should immediately make every ERISA attorney in the room very, very uncomfortable. If you waive copays for diabetics who stick to their treatment plan, you’ve arguably created a health-contingent wellness program, which brings the ADA, GINA, and a pile of EEOC regulatory chaos to your doorstep. The rules on this stuff are in shambles, and most employers are relying on safe harbors that are years out of date.
Then there’s the plan document issue. A standard SPD is basically a static contract. A VBID plan document needs to say things like “the copay is $10 if the diagnosis code is on the Value-Based List as updated quarterly.” That means every time you tweak the list-which you should, because clinical evidence changes-you’re doing a material plan amendment. SMM or 60-day notice. Every quarter. Nobody does that. And that neglect is a fiduciary breach waiting to happen.
Oh, and if you have an HSA-eligible HDHP, you’re playing in a sandbox that’s even smaller. The IRS gave us a nice little safe harbor in 2019 for pre-deductible chronic care, but it covers a laughably short list of drugs. Stray from that list, and you’ve just unwound the HSA compliance for every single enrolled member. Good luck explaining that tax mess.
Who Decides What’s Valuable, Anyway?
This is the quiet governance crisis that benefits leaders don’t budget for. A value-based drug list isn’t the same as a PBM’s standard formulary. You need clinical pharmacists digging through comparative-effectiveness research, applying it to your population, and defending the decisions when a member’s doctor calls angry. For medical services, there are over 600 low-value procedures on the Choosing Wisely list. Translating that into claim edits is a content-management monster. Do you have the staff to maintain that? Most employers don’t. They rely on consultants who hand them a one-off list and then disappear.
Communication is another hidden landmine. You can’t just tell employees “we’re rewarding high-value care.” They’ll hear “we’re rationing.” The successful rollouts I’ve seen frame it like a corporate discount perk. But you still need deep transparency. One client built an online lookup tool so people could see their cost-share tier by CPT code. It cost $200,000 and almost nobody used it. The lesson: communication has to be embedded in the moment of care-an SMS when a referral is placed, or a clear note on the pre-check-in screen. That’s a technical lift all over again.
So Where Do You Start, If You’re Not Ready to Buy a New Tech Stack?
VBID isn’t a lost cause. It’s just been sold as a plan design fix when it’s actually a systems transformation. If you’re going to pursue it, do it with open eyes and a very honest budget.
- Audit your data flows first. Can your medical carrier send a diagnosis feed to your PBM in near real time? If not, you can only do blunt, population-level rules-like making all ACE inhibitors $0, regardless of why they’re prescribed. That still helps, but it’s far from the targeted dream.
- Pilot with an integrated stack. If your health plan owns its PBM and has a unified platform, you’ll bypass most of the integration hell. Multi-vendor point solutions sound cool until you’re the one gluing them together.
- Get an ERISA attorney to map every value tier to a plan amendment schedule before go-live. Don’t trust your TPA’s compliance team on this. They’re not your fiduciary.
- Try the narrow-network shortcut. Instead of varying cost by service value, vary it by provider value. Zero copays at a Center of Excellence? That’s based on contract status, which your claims system already tracks. Much cleaner.
- Plan for a year of hand-holding. Your call center will get crushed at first. Train advocates, build visual EOBs, and accept that you’ll be explaining the meaning of “value” one member at a time.
Value-Based Insurance Design isn’t a failure. But it’s a clinical strategy dropped into an industrial-era administrative machine. The employers who pull it off will be the ones who stop treating it like a clever copay tweak and start treating it like a digital transformation project that happens to have a clinical soul. If you don’t have the stomach for the infrastructure work, you’re not buying a forward-thinking benefit. You’re just buying a headline that will unravel at the first EOB.