Technical Reading and Document Literacy in Healthcare Administration

Why Technical Reading Matters in Medical Billing and Coding

Medical billing and coding professionals work with dense, precise documents every day. A single misread remark code or an overlooked policy update can result in a denied claim, a billing error, or—most seriously—a compliance violation. Strong technical reading is not a background skill; it is a core job competency. This lesson builds your ability to locate, interpret, and summarize information from four document types you will encounter constantly: explanation-of-benefits (EOB) forms, payer policy bulletins, coding guideline sections, and compliance notices.

Reading an Explanation of Benefits (EOB)

An EOB is a document sent by a payer to the provider and sometimes to the patient after a claim is processed. It is not a bill. It is a record of how the payer adjudicated each line item on the claim.

Every EOB contains several standard fields for each line item:

• Billed amount – the charge the provider submitted
• Allowed amount – the maximum the payer will recognize under the contract or fee schedule
• Plan payment – what the payer paid the provider
• Patient responsibility – what the patient owes (deductible, coinsurance, or copay)
• Remark and reason codes – short codes that explain adjustments or denials

When you read an EOB, work line by line. Confirm the math: allowed amount minus plan payment minus patient responsibility should account for the full allowed amount. If the numbers do not reconcile, that is a signal to investigate before posting payment or billing the patient.

Patient safety note: When translating EOB information for a patient, never speculate about clinical decisions, diagnoses, or treatment necessity. Explain only the financial and administrative meaning of what is written. If a patient has clinical questions, direct them to the treating provider.

Remark Codes and Reason Codes

Reason codes (also called claim adjustment reason codes, or CARCs) explain why an adjustment was made. Remark codes (remittance advice remark codes, or RARCs) provide additional explanation. Both are maintained by a national code set and appear on the remittance advice or EOB. You must look codes up in the current code list rather than guessing their meaning. Using an outdated list can lead to incorrect claim follow-up actions.

Reading Payer Policy Bulletins

Payers publish policy bulletins to announce changes in coverage rules, billing requirements, prior authorization criteria, and fee schedules. These bulletins may arrive by mail, email, or through an online provider portal. Staying current with policy bulletins is part of your professional responsibility.

When comparing two versions of a bulletin, use a systematic approach:

1. Read both versions fully before marking anything.

2. Identify sections that changed, were added, or were removed.

3. For each change, ask: Does this affect how I submit a claim, what I code, or when I need authorization?

4. Document the effective date of each change—billing under a superseded policy is a compliance risk.

Compliance note: Billing in a manner that contradicts a payer's current published policy, even accidentally, can be characterized as a billing error or, in serious cases, a false claim. Monitoring policy updates is an ongoing duty, not a one-time task.

Reading Coding Guidelines

The ICD-10-CM Official Guidelines for Coding and Reporting are published annually by the Centers for Medicare & Medicaid Services (CMS) and the National Center for Health Statistics (NCHS) and are available free of charge from CMS. They are the authoritative source for how ICD-10-CM codes are assigned. The guidelines have the force of a HIPAA standard and must be followed.

The guidelines use specific language that has defined meaning:

• "Code first" – a sequencing instruction telling you to list another code before this one
• "Use additional code" – an instruction to add a code to capture more detail
• "Excludes1" – indicates two conditions cannot be reported together on the same claim
• "Excludes2" – indicates the excluded condition is not part of this code but may be reported separately when both are present

When you encounter text you do not understand, look for the answer within the guidelines themselves before going elsewhere. The guidelines include a section on conventions that defines their own terminology.

Summarizing for a Non-Clinical Audience

One practical skill tested in this lesson is translating administrative language into plain English for a patient. A good patient-facing summary:

• Uses no jargon without explanation
• States clearly what the patient owes and why
• Does not editorialize or express opinions about the payer's decision
• Is professional and calm in tone
• Stays within your scope—you explain the EOB; you do not advise the patient on whether to appeal a medical necessity denial without involving the provider or appropriate staff

Example of a plain-language statement: "Your plan paid $120 toward this service. After your deductible of $30 is applied, you owe $30 to the provider. The remaining $50 was not covered because it exceeded your plan's allowed amount for this service."

Accuracy as a Safety and Compliance Standard

Errors in reading administrative documents create downstream harm: patients receive incorrect bills, providers lose legitimate reimbursement, and the practice faces audit risk. Approach every document with the assumption that every number and every code matters. When something is unclear, use primary sources—the guidelines, the payer's published policy, the official code list—before drawing a conclusion.