Field Note: Reading the Explanation of Benefits

Field Note: Reading the Explanation of Benefits

The document says "This is not a bill." I have read that sentence many times now. It is printed near the top of every Explanation of Benefits I have received, in the kind of font chosen to be noticed without being read. And yet everything else on the page behaves exactly like a bill — columns of charges, adjustments, amounts owed, provider names rendered in capital letters as though volume were clarity. The gap between what the document announces and what it performs is not an accident. It is the argument.

An Explanation of Benefits is, in theory, a transparency instrument. It exists to show you what happened between your insurer and your provider after a claim was filed on your behalf. You are the subject of the transaction. You are not, strictly speaking, a party to it. This distinction is the first thing the document teaches you, if you read it carefully enough to learn anything at all.

Most people do not read them carefully. This is also not an accident.

The architecture of an EOB discourages comprehension. The columns are labeled in passive constructions: "amount billed," "amount allowed," "plan paid," "member responsibility." Each phrase is technically precise and contextually unintelligible. Amount billed by whom, to whom, under what schedule? Allowed by which agreement, negotiated when, on what basis? The document answers none of these questions. It presents the outcomes of a process it does not describe, using vocabulary that implies you already understand the process. The assumption of prior knowledge is doing a great deal of work here.

What the document actually records is the settlement of a negotiation you were not part of and were not meant to understand. Your provider billed a number. Your insurer, under a contracted rate established long before your appointment, reduced that number. The difference — sometimes called the "adjustment" or the "discount" — vanishes from your responsibility without explanation. The number that remains is divided between what the plan pays and what you owe. This is presented as information. It is, more precisely, a ledger entry from a relationship in which you are simultaneously the reason for the transaction and peripheral to it.

The design rewards a particular kind of reader: one who already works in billing, or benefits administration, or healthcare finance — someone who brings the contextual knowledge the document withholds. For everyone else, the EOB is legible in the way that a contract is legible. You can read every word and still not know what you agreed to.

This is where institutional design becomes interesting. The form is required. The insurer must send it. There are regulations governing what it must contain. Compliance is documented, audited, verifiable. The institution can demonstrate, at any point, that it informed you. Whether the information was intelligible is a different question, and it is not the question the regulation asks. The institution has fulfilled its obligation to inform you by sending you something you cannot easily use. The obligation and the function have been quietly separated.

Who bears the cost of this separation? Primarily the person who receives the document and either ignores it, misreads it, or files it without understanding whether the charges are correct. Billing errors exist. Duplicate charges exist. Claims processed under the wrong code exist. An informed reader of an EOB might catch these. An average reader will not, because the document does not equip an average reader to catch them. The people most likely to be charged incorrectly are also the people least likely to have the professional vocabulary to notice.

The people least likely to be charged incorrectly — or most likely to identify and contest errors when they occur — are the people with institutional access: benefits coordinators, patient advocates, medical billing specialists. These are, structurally, the same people who already have the most leverage in the system. The document does not create this asymmetry. It maintains it.

The transferable principle is this: when an institution is required to inform you, examine what form that information takes. Compliance with a disclosure requirement is not the same as disclosure. A document can be technically complete and functionally opaque. The gap between those two conditions is not neutral — it has a direction, and the direction consistently favors the party that designed the document over the party that receives it. Legibility is a choice. When it is consistently withheld from the same populations, that pattern is also a choice, even when no individual within the institution made it consciously.

I kept the EOBs. I have a folder. I read them now the way I read contracts — not to understand them immediately, but to mark where I stop understanding, which is where the actual information lives.