Explanation of Benefits UX: Answer What They Owe Before the Claim Codes
Every health plan and benefits platform eventually ships an Explanation of Benefits. Members open it after a visit, a lab, a pharmacy fill, or a hospital stay, and they ask the same three questions in the same order: what did I get, what do I owe, and what do I do next. Most EOBs answer those questions somewhere in the middle of a dense claim dump that was designed for audit, not for a person on a phone.
Support queues fill with "I thought this was a bill" and "why does this say I owe money when the provider already charged me." That traffic is a design problem. We treat explanation of benefits UX as a product surface with two jobs that must stop competing for the same square inches, and we build the member layer first.
Two jobs, one document
An EOB has a compliance job and a member job.
The compliance job is a defensible record: what was billed, what the plan paid, what the member owes, appeal rights, and every required disclosure. Legal, compliance, audit, and revenue cycle own that layer. Every line matters. Nothing comes out without review.
The member job is comprehension and action. It answers the three questions above in under ten seconds, on a phone, without a glossary. Almost no team owns that job. It is treated as leftover space after the legal layer is laid out.
When both jobs fight for the same layout, the legal layer always wins. Members then call, and the plan pays for that call volume forever. The fix is separation, not deletion. Keep every required line. Put a designed patient summary on top of it.
The patient summary we ship first
The top of every EOB, digital or PDF, should answer the member in this order:
- What this is. One sentence, prominent: "This is a record of what your plan covered. This is not a bill." Almost every confused call starts with a member who thought the EOB was a demand for payment. Say it before they scroll.
- What you got. A human description of the service with a date and a provider name. "Office visit with Dr. Lee on March 14" beats a CPT string or an internal claim label. Clinical and coding detail can live below.
- What you owe. One dollar amount, large type, with enough space that the eye lands on it. If the answer is zero, say "You owe nothing." If the provider will bill separately, say that in the same breath: "Your provider will send a bill. Expect it within 30 days."
- What to do next. One sentence with a date or a clear "no action needed." Appeal windows, payment instructions, and contact paths belong here when they apply, not buried three pages down.
Everything else (line items, network status, deductible math, denial codes, definitions, appeal rights) stays in the legal layer below. Members who want detail can find it. Members who need the answer for dinner table budgeting get it without scrolling through claim codes.
Three numbers that earn trust
When we redesign member statements and EOBs, we open with three totals that mean the same thing every time:
- Charged: what the provider billed.
- Plan paid / you saved: what the plan covered, shown as clearly as the cost.
- You paid or owe: the member responsibility.
Plans often hide the "you saved" number because the product team thinks members only care about what they owe. Members who never see the plan's contribution walk away thinking coverage did nothing. Showing savings next to cost is how the EOB proves the premium was worth paying.
Year to date progress against the deductible and the out of pocket maximum belongs on the same first screen, with remaining dollars and a plain label. "Catastrophic" and similar internal benefit names confuse people who are already under stress. Use the words members use: deductible left, out of pocket left.
Digital EOBs beat PDF dumps
Shipping a PDF of the print EOB into a portal is not a digital experience. Members need a status page that behaves like a product:
- Search and filter by date, member on the family plan, provider, and claim status.
- A claim detail view that opens with the patient summary, then the line items.
- Denial and partial pay states that name the reason in plain language and link to the exact appeal or document request, with the deadline visible.
- Family vs individual views that do not force a parent to reconstruct who got which service from a single unsorted list.
- Download and print that still include the legal layer, so the paper copy remains defensible.
If the only "digital" surface is an email with a PDF attachment and no in-product status, members will call. The call is cheaper to prevent than to staff.
Denied and partially paid claims
Denials are where EOB UX either builds trust or destroys it. A code plus a one line remark that only a biller can decode is a support ticket. We require:
- A plain language reason next to the code.
- Whether the member, the provider, or the plan must act next.
- The deadline and the link or form to act.
- A path to a human when the denial is medical or financial, not a FAQ loop.
Partial pays need the same care. "Allowed amount," "usual and customary," and "provider write off" mean nothing without a one line translation and a clear residual balance. If the member owes nothing because the provider accepted the plan rate, say that. Silence reads as a surprise bill later.
Coordination with the real bill
Members often receive an EOB and a provider bill in the same week, with different numbers and no shared claim ID they can see. That gap drives duplicate payments and angry calls to both parties.
What we insist on between the plan product and the provider billing surface:
- A shared claim reference the member can quote on either side.
- Language that distinguishes "plan record" from "provider bill" on both documents.
- Timing guidance: when the EOB arrives relative to the bill, and what to do if the amounts disagree.
- A dispute path that does not require the member to mediate between two back offices with no shared screen.
If you only control the plan side, still write the EOB as if the bill will show up. Tell the member which number should match, and who to call when it does not.
What we reject
When we review explanation of benefits UX, these get flagged every time:
- An EOB that never says "this is not a bill" above the fold.
- CPT codes and internal claim labels as the only description of the service.
- Member responsibility buried below network analysis and remark codes.
- Savings and plan payment hidden or omitted while costs are large.
- Denial reasons that only a coder can read, with no next step or deadline.
- A portal that only hosts PDFs with no search, filter, or claim status.
- Family claims dumped into one chronological list with no per member view.
- No shared claim reference between the EOB and the provider bill.
- Appeal rights present only as a dense legal block with no actionable link.
- Chatbots as the only path after a denial involving medical necessity or high dollars.
How we approach it
Explanation of benefits UX sits at the intersection of regulated copy and product design. The wins come from a clear patient summary, honest three number totals, denial states that name the next move, and a digital claim status that members can actually use. Our senior team works in working software, so we ship the summary, the claim detail, and the denial paths as real screens your engineers can merge, with the legal layer preserved for counsel. AI helps us cluster call themes and find where members get stuck; people with health and insurance product experience decide what changes and in what order.
If your EOBs generate "I thought this was a bill" calls, we can map the member layer and the legal layer and show what to ship first. Book a discovery call or email us at ash@uxsignalstudio.com.