6.1 Billing Data Elements & Claim Forms (UB-04 vs CMS-1500)

Every claim a payer approves — and every dollar a hospital ultimately collects — traces back to information entered long before a bill is ever generated. Patient access is often called the "front door" of the revenue cycle for exactly this reason: registration data becomes claim data. A misspelled name, a wrong policy number, or a missing occurrence code captured at check-in does not stay a front-end problem. Weeks later it resurfaces as a denied, delayed, or underpaid claim. Understanding what data elements feed a claim — and which of the two major claim forms that data lands on — is core CHAA exam content and core job knowledge for anyone who touches patient access.

Core Billing Data Elements

Four categories of data, most of them captured or verified during registration, combine to build an accurate claim.

Diagnosis codes (ICD-10-CM). The International Classification of Diseases, 10th Revision, Clinical Modification codes describe why the patient received care — the diagnosis, symptom, or reason for the encounter. ICD-10-CM codes establish medical necessity, the justification a payer needs before it will pay for a service.

Procedure codes (CPT and HCPCS). Current Procedural Terminology (CPT) codes, maintained by the American Medical Association, describe what was done — the specific service, test, or procedure performed. The Healthcare Common Procedure Coding System (HCPCS) extends this with Level II codes for supplies, equipment, drugs, and services CPT does not cover, such as ambulance transport, durable medical equipment, and certain injectable drugs. Together, diagnosis and procedure codes answer the payer's two core questions: why was the patient seen, and what was done for them.

Revenue codes. Used on institutional claims, four-digit revenue codes identify the hospital department or cost center where a charge originated — for example, the emergency room, operating room, pharmacy, or laboratory. Revenue codes group charges by location and service type rather than by individual procedure.

Occurrence codes and condition codes. Both appear on the institutional claim form, and both affect how a payer processes the bill, but they answer different questions. An occurrence code always pairs a two-character code with a specific date and answers "when did this happen?" — for example, code 11 for admission date, code 24 for discharge date, or code 01 for an accident date. A condition code describes a circumstance or attribute of the claim that changes how the payer reads it as a whole — for example, that the patient is an HMO enrollee, that the condition is employment-related, or that care relates to an auto accident. In short: occurrence codes are about when; condition codes are about what kind of situation.

UB-04 vs. CMS-1500: Two Forms, Two Billing Roles

A single hospital visit can generate both forms at once. If a patient has outpatient surgery, the hospital bills a UB-04 for the operating room, supplies, and nursing care, while the surgeon and anesthesiologist separately bill CMS-1500 forms for their professional services. Patient access staff rarely decide which form a service lands on, but the demographic, insurance, and clinical data captured at registration populates both.

How Access Data Becomes Claim Data

Every data element on a claim form has to originate somewhere, and for most fields that origin is patient access.

• Patient and insurance demographics captured at scheduling or registration populate the subscriber, guarantor, and payer fields on both forms.
• The visit type and admission source recorded at check-in drive occurrence codes such as admission date and, for inpatient stays, discharge date.
• The reason for the visit, documented from the physician order, supports the diagnosis coding that HIM and coding staff later finalize into ICD-10-CM.
• Authorization and referral numbers collected during financial clearance populate the corresponding claim fields payers use to match the claim to an approved authorization.

Because so much claim data originates at the front end, an access associate who understands how their data entry maps to a UB-04 field locator or a CMS-1500 box is far more likely to catch an error before it becomes a denial. This is also why the CHAA blueprint places "impact of data element collection for UB-04 and CMS-1500 billing forms" inside the revenue cycle domain rather than treating it as a coding-only topic — data quality is a shared responsibility that begins the moment a patient is scheduled, not a problem HIM and billing solve alone after the fact.

Who Maintains the Forms

The UB-04 is maintained by the National Uniform Billing Committee (NUBC), which standardizes its field locators (FLs) and the codes reported in them, including revenue, occurrence, and condition codes. The CMS-1500 is maintained by the National Uniform Claim Committee (NUCC), which standardizes its 33 numbered boxes. Both committees update guidance periodically, so access staff should expect field requirements to evolve rather than treating any one version of a field guide as permanent.

Timeliness Compounds Accuracy

Accurate data is only half of the equation; timely entry is the other half. A registration completed same-day, with eligibility, authorization, and demographics entered promptly, gives coding and billing the longest possible runway to catch a discrepancy before a claim's timely-filing deadline. Delayed entry does not just slow the claim — it shrinks the window available to fix a problem before that deadline expires, turning a correctable error into an unbillable one. This is the same "timely input of data" expectation covered under information systems, applied here directly to revenue outcomes.