Claim Forms, Charge Capture, and Financial Communication

Claim Forms and Charge Data

A claim form converts encounter data into a structured payer request for payment. The CCA exam may ask which form is used, which data element is missing, or which department should be contacted. You do not need to memorize every field, but you must know the broad distinction between institutional and professional claims and the standard transactions defined under HIPAA.

Institutional Claims (Facility)

Facility billing uses the UB-04, also called the CMS-1450, on paper, or the electronic 837I (institutional) transaction. These claims may include patient demographics, the three-digit type of bill, revenue codes (four-digit codes identifying the cost center, such as 0250 for pharmacy), ICD-10-CM diagnoses, ICD-10-PCS procedures for inpatient facility claims, CPT/HCPCS for outpatient services, total charges, units, and the National Provider Identifier (NPI). A common exam trap pairs an inpatient hospital scenario with the CMS-1500 — that is wrong, because the hospital bills on the UB-04/837I.

Professional Claims

Physician and other professional services are billed on the CMS-1500 paper form or the electronic 837P (professional) transaction. These claims rely on CPT/HCPCS procedure codes, ICD-10-CM diagnosis codes, diagnosis pointers (which link each service line to up to four diagnoses), modifiers, place of service (POS) codes, units, the rendering and billing NPI, and charges.

Charge Capture and the Chargemaster

Charge capture is the process of recording every billable service, supply, drug, and procedure. The chargemaster (charge description master, or CDM) is the facility's master list of chargeable items with their associated HCPCS/CPT codes, revenue codes, and prices. A coder may identify mismatches between the documentation, the coded services, the modifiers, the units, the revenue codes, and the charges.

Apply two symmetric rules. A missing charge is never solved by adding an unsupported code to justify it. An unsupported charge is never solved by leaving it on the claim. In both cases the coder compares the charge or code to the record, facility policy, and payer rules, then routes the issue to billing, revenue integrity, or the department that owns the charge.

Communication With Finance

Financial communication must be factual and specific. A useful message identifies the account number, service date, the code or edit at issue, the documentation reviewed, the rule applied, and the recommended correction or next step. Avoid vague messages such as "the payer denied it" or "change the code so it pays." Clear, sourced communication supports clean claims and defensible appeals.

Element-to-Form Cheat Sheet

When a scenario lists revenue codes and a type of bill, think facility. When it lists diagnosis pointers, modifiers, and a place-of-service code, think professional. Matching the data elements to the correct claim format is one of the most directly testable skills in this domain.

HIPAA Transactions and Reading a Claim

Under the HIPAA Administrative Simplification rules, electronic claims use ASC X12 5010 transaction standards. You should associate each transaction number with its purpose so a question that names a transaction is answerable on sight.

When a scenario says a coder is verifying coverage before service, that is a 270/271 eligibility check — a front-end activity. When the payer returns payment detail, that is the 835 remittance advice that feeds denial management.

Type of Bill and Revenue Code Logic

On the UB-04, the three-digit type of bill (TOB) encodes the facility type, bill classification, and frequency. A common exam-friendly anchor is that the leading digit signals the facility (1 = hospital), the second the care type (1 = inpatient, 3 = outpatient), and the third the sequence (0 = nonpayment/zero claim, 1 = original, 7 = replacement, 8 = void). Revenue codes then tell the payer where a charge originated (for example, 0450 emergency room, 0636 drugs requiring detailed coding). The exam will not require you to build a TOB, but it may ask you to recognize that revenue codes and TOB are institutional-only elements.

Charge Capture Failure Modes

Two failure modes recur: a charge without documentation (an item billed but not recorded as performed or used) and documentation without a charge (a service performed but never charged, called lost charges or revenue leakage). Both are routed to revenue integrity. The coder never invents a code to back a charge and never leaves an unsupported charge on the account; the record governs, and the chargemaster is corrected through policy rather than at the keyboard.