The Explanation of Benefits — the EOB — is the single most-complained-about document in US healthcare. It arrives in the mail, it looks like a bill but is labeled “this is not a bill,” it lists procedures the patient does not remember, charges they do not understand, adjustments that read like accounting code, and a number at the bottom that may or may not be what they owe. Most patients respond by calling the billing line.
The patient billing statement that follows is usually worse. It is written by the revenue cycle team, designed by no one, constrained by compliance language nobody is willing to remove, and printed in a layout that has not been touched since the early 2000s. Together, the EOB and the statement are the single highest-leverage patient experience intervention available to most health systems and payors.
Almost nobody fixes them. Here is why, and how to actually do it.
Why nobody fixes them
The EOB and the billing statement are the most-redlined documents in healthcare. Every word has been argued over by legal, compliance, and audit. Every line has a reason it is there. Every disclaimer is the residue of a lawsuit or a regulator’s letter. Designers who attempt a redesign quickly hit a wall:
- Legal will not approve removing the disclaimers.
- Compliance will not approve renaming the line items.
- Audit will not approve restructuring the totals.
- Revenue cycle will not approve anything that risks the dispute timer or the appeal window.
- IT will not approve a redesign that requires re-coding the EOB generation system.
A naïve redesign that ignores any of these stakeholders gets killed in review. A redesign that tries to satisfy all of them in a single pass gets watered down into a cosmetic refresh — a new typeface and a slightly better margin. The patient still cannot read it.
The reason real EOB redesigns work is not that they out-design legal. It is that they reframe what legal is reviewing.
The reframe: keep the legal layer, redesign the patient layer
The single move that makes EOB redesigns ship is recognizing that the EOB has two jobs.
-
The legal/compliance job — be a defensible record of what was billed, what was paid, what the patient owes, and what the patient can do about it. This job is owned by legal, compliance, audit, and revenue cycle. Every word matters. Nothing can be removed without review.
-
The patient job — answer three questions: What did I get? What do I owe? What do I do next? This job is owned by nobody. It is the residue of the legal job, not the design of it.
The conventional EOB tries to do both jobs in the same layout. The patient layer is squeezed into whatever space the legal layer leaves over. The patient cannot answer their three questions because the answers are scattered across a document that was not designed to answer them.
The redesign separates the two. The EOB becomes a two-layer document:
- A patient summary at the top, designed to answer the three questions in plain language with prominent numbers and visual hierarchy.
- The legal/compliance record below it, preserved as-is, in language that legal can defend.
Critically, the legal layer does not get cut. Every disclaimer, every line item, every appeal-rights paragraph stays. The redesign happens above it.
This works because legal is reviewing the bottom of the page. The patient is reading the top of the page. The two jobs stop competing for the same square inches.
What the patient summary actually contains
The patient summary, at the top of every EOB, is a small designed surface with a strict job description. It should contain exactly the following, in this order:
1. “What this is” — one sentence. “This is a record of what your insurance covered. This is not a bill.” Plain, prominent, repeated in plain language. Almost every patient complaint about EOBs starts with “I thought this was a bill.” Answer the question before the patient asks it.
2. “What you got” — a one-line description of the service. Not the CPT code. Not the clinical name. “Office visit with Dr. Lee on March 14” beats “E/M Level 4 Office Visit, Estab. Pt., 30 min.” The clinical detail can live in the legal layer. The patient summary uses the human description.
3. “What you owe” — the dollar amount, prominent. A single number. Large type. Surrounded by enough white space that the eye lands on it. If the answer is “nothing,” say that. If the answer is “your provider will send you a bill,” say that. Patients are looking for this number. Make it impossible to miss.
4. “What to do next” — one sentence, with a date. “Pay this amount when you receive the bill from your provider. The bill will arrive within 30 days.” Or “No action needed.” Or “Call us by April 30 if you believe this is incorrect.” The next action, plus the timing.
Everything else — the breakdown of charges, the in-network/out-of-network analysis, the deductible math, the appeal rights — lives in the legal layer below. Patients who want detail can find it. Patients who just want to answer their three questions can do it in 10 seconds.
How to get this through legal
The reason this design survives legal review is that legal does not have to approve the patient summary as a regulatory artifact. They have to approve that the regulatory artifact still exists. As long as the legal layer is preserved unchanged, the patient summary is supplementary. It is not removing required content. It is adding helpful content on top of it.
This is a different conversation than “can we shorten the appeal-rights paragraph.” That conversation is unwinnable. This conversation is “can we add a plain-language summary at the top of the document.” That conversation is winnable, because legal’s risk is unchanged.
In practice, the work looks like this:
- Joint working session with legal at the start. Not at the end. Frame the project as “patient layer addition, legal layer preserved.” Get explicit alignment that the legal layer is out of scope for redesign.
- A locked legal layer. Take the existing legal layer, lock it, and commit to not modifying it in this redesign. Note any improvements you would make in a future redesign, but keep them out of this one.
- Iterate on the patient layer with patients. Usability test the summary with real patients — ideally a mix of ages, health literacy levels, and language backgrounds. The bar is comprehension, not aesthetic preference.
- Compliance review of the patient layer. Show compliance the patient layer as an addition. Their question is “does this contradict, mislead, or replace required content.” Design the layer so the answer is no.
- Ship the smallest viable redesign first. Patient summary only. Same legal layer. Same generation system. The smaller the change, the faster it ships.
What measurably improves
When the redesign ships, the metrics that move are not satisfaction scores. They are operational.
- Call volume to the billing line drops. Specifically, calls that start with “I got something from you and I do not understand it” drop substantially. We have seen 25–40% reductions in initial-inquiry billing calls after a patient-summary redesign.
- Time-to-payment decreases. Patients who understand what they owe pay faster. A few-day reduction in average days-to-pay is a real revenue cycle outcome.
- Dispute volume changes shape. Patients still dispute, but the disputes become more specific and less general. “I don’t understand my bill” disputes drop; “I was charged twice for the same visit” disputes rise as a share. Specific disputes are easier to resolve.
- NPS / patient satisfaction on billing-touched journeys improves. This is the slowest-moving metric but it does move.
None of these are visible from the document itself. They show up downstream in the billing line, the dispute queue, and the cash collection cycle. The case for the redesign, made up front, is operational — not aesthetic.
The pattern this is an example of
The EOB redesign is a specific case of a more general healthcare design pattern: when a document or interface has both a compliance job and a user job, design the user layer on top of the compliance layer rather than inside it. The same pattern applies to patient billing statements, post-visit summaries, consent forms, lab result notifications, and prior-authorization decisions. In every one of these, the legal layer is doing real work that should not be removed, and the user layer is being squeezed into whatever space is left over.
Two layers, designed separately, shipped together. That is the move. It survives legal because legal is reviewing the layer they care about, unchanged. It works for patients because the patient summary is doing the patient’s job, finally, with the full square inches it needs.
The EOB is the most visible place to apply this pattern. It is also the place where the operational return is fastest. Any health system or payor that wants to make one durable patient experience improvement in the next twelve months should redesign the EOB. It will outperform almost any other single intervention available.