38 min read

> "Almost nobody submits this on paper anymore, and everybody still has to know it, because the

Prerequisites

  • 3
  • 6
  • 24

Learning Objectives

  • Say what the CMS-1500 is, who maintains it, and what its relationship to the 837P is.
  • Complete the patient and insured blocks, items 1–13.
  • Complete the condition and referral blocks, items 14–23.
  • Complete item 24 column by column.
  • Apply diagnosis pointers and the four-per-line rule.
  • Distinguish the rendering, billing, and service facility providers.
  • Use Type 1 and Type 2 NPIs correctly and name the identifiers that no longer belong on the form.
  • Select a place of service code.
  • Name the fields that most often cause a rejection.
  • Build Account 10-4471's claim, box by box.
  • Explain why the paper form is designed the way it is, and what reads it.
  • Say what a companion guide settles that the NUCC manual does not.
  • Find the errors in a claim you did not build, without looking only at the codes.

Chapter 25: The CMS-1500: Completing the Professional Claim Field by Field

"Almost nobody submits this on paper anymore, and everybody still has to know it, because the electronic claim is this form with the boxes removed." — constructed

Overview

Everything in this book so far has been about what belongs on a claim. This chapter is the claim.

The CMS-1500 is the professional claim form — the one used by physicians, non-physician practitioners, suppliers, and most non-institutional providers. Chapter 26 covers the institutional form; Chapter 27 covers the electronic transaction both of them become.

Two things to settle before the field-by-field work.

Almost nobody submits paper. Electronic submission is the norm and is required for most Medicare claims, with narrow exceptions. So why learn the form?

Because the electronic claim carries the same data in a different container. The 837P's loops and segments map onto these items. When a claim rejects for "missing or invalid item 17b," the message is describing a form nobody printed — and a biller who does not know what item 17b is cannot fix it.

And the form is a shared vocabulary. Payers, clearinghouses, and vendors describe claim problems by item number. It is the industry's coordinate system, and it will outlive the paper.

One more structural note. The form is maintained by the National Uniform Claim Committee (NUCC), not by CMS alone, and the NUCC publishes a reference instruction manual that says what each item wants. It is free. Almost nobody in a billing office has read it, and it answers the majority of "what goes in this box" questions definitively.

In this chapter, you will learn to:

  • Say what the form is and how it relates to the 837P
  • Complete items 1–13, 14–23, and 24
  • Apply diagnosis pointers and the four-per-line rule
  • Tell the rendering, billing, and service facility providers apart
  • Use Type 1 and Type 2 NPIs
  • Select a place of service code
  • Name the fields that cause rejections
  • Build Account 10-4471's claim

25.1 What the form is and who maintains it

The CMS-1500 is the standard claim form for professional services. Its electronic equivalent is the 837P.

The National Uniform Claim Committee maintains it, in consultation with CMS and the industry. The current version is identified by a date printed on the form itself — the 02/12 version at the time of writing — and the version matters, because items changed between versions and payer instructions reference specific ones.

Three consequences of the NUCC's role.

The NUCC's reference instruction manual is the authority on what each item wants. Free, downloadable, and updated. When a payer's instruction and your assumption disagree, the manual is where you find out which of you is wrong.

Payers may add requirements. The manual says what the item is for; a payer may specify how it wants the item populated, and its provider manual governs its own claims. Chapter 24 §24.5's lesson applies here too: the payer's document is operative for that payer.

And items get repurposed. An item that once carried one thing may now carry another, or nothing. §25.7 covers the identifiers that no longer belong on the form, and they are still being submitted.

Paper versus electronic

   THE SAME DATA, TWO CONTAINERS

   CMS-1500 item 24A ......... 837P: the service line date segment
   CMS-1500 item 21 .......... 837P: the health care diagnosis code segment
   CMS-1500 item 33a ......... 837P: the billing provider NPI

   A rejection message naming an ITEM is describing the form.
   A rejection message naming a LOOP or SEGMENT is describing the 837P.
   ► They are the same problem in two vocabularies, and a biller
     needs both. Chapter 27 §27.4 covers the second.

The physical form, and why it looks like that

A paper CMS-1500 has requirements that seem arbitrary until you know what reads it.

It is designed to be scanned. Payers process paper claims through optical character recognition, and the form's specifications exist to make that possible.

Which produces four rules that surprise people:

The form is printed in a specific red ink — commonly described as red drop-out ink — which the scanner is calibrated not to see. The scanner reads what is in the boxes and ignores the boxes themselves. A photocopy of a blank form is black, the scanner sees the lines, and the claim fails.

Nothing may be handwritten. Handwriting defeats character recognition.

Nothing may fall outside its box, and characters must not touch the printed lines.

And no highlighting, no correction fluid, no staples through the data area. All of them create marks the scanner interprets.

Two reasons this is worth a paragraph rather than a footnote.

Practices still submit paper occasionally — for a payer that requires it, for an attachment situation Chapter 27 §27.8 describes, for a claim a system cannot produce electronically. When they do, the requirements apply, and a claim rejected for illegibility looks like a mystery to someone who has never been told the form is machine-read.

And it explains the form's shape. The rigid field positions, the fixed number of service lines, the abbreviations — these are not design choices, they are consequences of a scanner, and knowing that makes the form legible as an object rather than an arbitrary bureaucratic artifact.


25.2 The patient and insured blocks: items 1–13

The top third of the form answers three questions: who is the patient, who holds the coverage, and is there other coverage?

The items that matter and what goes wrong in each:

Item What it wants What goes wrong
1 The type of coverage — Medicare, Medicaid, TRICARE, group health, other checked by habit rather than by the card
1a The insured's ID number Chapter 24 §24.2's transcription errors land here
2 Patient's name, last, first, middle initial must match the payer's record
3 Patient's birth date and sex one transposed digit and the patient does not exist
4 The INSURED's name left blank when the patient is not the subscriber
5 Patient's address Chapter 24's Case Study 1
6 Patient's relationship to the insured self, spouse, child, other — assumed rather than asked
7 The insured's address
9, 9a–9d Other insured — the secondary coverage block left blank when other coverage exists
10a–10c Is the condition related to employment, an auto accident, or another accident? the coordination-of-benefits trigger — Chapter 24 §24.2
10d Claim codes, as required by the payer
11, 11a–11d The insured's policy/group number and whether there is another health benefit plan
12 Patient's signature authorizing release of information "signature on file"
13 Insured's signature authorizing payment to the provider "signature on file"

Three things worth stopping on

Item 4 versus item 2. The patient and the insured are frequently different people, and item 4 exists for that. A claim for a child on a parent's policy has the child in item 2 and the parent in item 4 — and a claim with item 4 blank asserts they are the same person.

Items 10a–10c are the coordination-of-benefits question in claim form. Chapter 24 §24.2 said the front desk asks about accidents and employment; this is where the answer goes. A "yes" in 10a routes the claim toward workers' compensation and is a statement the practice is making about the cause of the condition.

"Signature on file." Items 12 and 13 are commonly completed with the phrase rather than a signature, which is permitted when a signed authorization is actually on file.

Items 9a–9d, and the block everyone leaves blank

The "other insured" block is the most consistently under-completed part of the form, and its emptiness is usually not a decision.

Items 9, 9a, and 9d capture the OTHER coverage — the secondary policy, its holder, and the plan name — when the patient has more than one.

Three things follow from filling it in, and all three are the point:

The primary payer learns that other coverage exists, which is the coordination-of-benefits information Chapter 24 §24.7's questionnaire was collecting.

The secondary claim becomes possible. Chapter 28 §28.10 covers secondary billing, and a secondary claim generally needs the primary's remittance plus the secondary's identifying information. If that information was never captured, the secondary claim has to start from a phone call.

And the patient's balance may not be theirs. A balance transferred to a patient who has secondary coverage nobody recorded is a bill sent to the wrong party — which is Chapter 24's Case Study 1 in a different costume.

The block is blank on most claims and correctly blank on most claims, because most patients have one policy. The failure is not that it is usually empty. It is that nobody distinguishes "empty because there is none" from "empty because nobody asked."

⚖️ Compliance Check

"Signature on file" asserts that a signature is on file.

This is the ninth or tenth time this book has met the same shape, and it is worth naming as a pattern rather than as a new fact: a form field that stands in for a document is an assertion about that document's existence.

Chapter 22's routine ABN produced GAa valid ABN is on file. Chapter 20's waste policy produced JWthis much was discarded. Chapter 19's automatic modifier produced KXthe documentation supports necessity.

"Signature on file" is the same assertion in the oldest field on the form.

Two practical requirements. The authorization must exist, and it must be current under the payer's rules — some require periodic renewal. A practice that populates the phrase by default, across all patients, without a process that files anything, has automated a false statement and has done so in the field that authorizes releasing the patient's medical information.


25.3 The condition and referral blocks: items 14–23

The middle band of the form is about circumstances: when did this start, who sent the patient, and what else does the payer need to know?

Item What it wants
14 Date of current illness, injury, or pregnancy, with a qualifier saying which
15 Other date — a second date with its own qualifier
16 Dates the patient was unable to work
17, 17a, 17b The referring, ordering, or supervising provider — name, a qualifier, and the NPI in 17b
18 Hospitalization dates related to the service
19 Additional claim information — the narrative field
20 Outside lab and charges — Chapter 19 §19.5's purchased test question
21 The DIAGNOSIS CODES — up to twelve, lettered A through L, with an ICD indicator
22 Resubmission code and the original reference number — Chapter 29 §29.6's corrected claims
23 Prior authorization number or CLIA number, as applicable

The four to know cold

Item 17b — the referring provider's NPI. Chapter 19 §19.5 called the referring provider field the highest-volume denial in diagnostic billing. This is that field. Blank, wrong person, unenrolled, or mismatched — four causes, one item.

Item 19 — additional claim information. The narrative field. Chapter 20 §20.3's unclassified drug codes require the drug name, dose, and route here, and a claim with an unclassified code and an empty item 19 says we gave a drug.

Item 21 — the diagnosis codes. Up to twelve, lettered A through L. The ICD indicator says which code set is in use — a small field with an outsized effect, since a claim carrying ICD-10-CM codes with the wrong indicator is describing codes that do not exist in the set it claims.

Note the asymmetry that trips everyone: TWELVE diagnoses on the claim, but only FOUR per line. §25.5.

Item 23 — the prior authorization number, and for laboratory claims the CLIA certificate number — Chapter 19 §19.6. One item, two entirely different purposes, and which applies depends on what you are billing.

Items 14 and 15, and their qualifiers

Two date fields that mean nothing without the small code beside them.

Item 14 carries a date and a qualifier saying what the date IS — onset of the current illness, the date of injury, or the last menstrual period. The same date means different things under different qualifiers, and a claim carrying a date with no qualifier has supplied a number without a meaning.

Item 15 carries a second date with its own qualifier — an initial treatment date, a date last seen, a date of a prior related surgery, and others.

These are the fields most often populated by a system default and least often examined. They matter on injury claims, on obstetric claims (Chapter 18 §18.6), and on any claim where a payer's policy has a timing element — which is Chapter 22 §22.7's frequency limitations arriving on a form.

Item 22, and what a corrected claim actually is

Item 22 is small and it decides whether you are correcting a claim or creating a second one.

It carries a resubmission code — indicating a replacement or a voidand the original claim's reference number.

Three failure modes, and Chapter 29 §29.6 covers the workflow:

Resubmitting with item 22 blank creates a DUPLICATE, not a correction. The payer receives what looks like a second claim for the same service and denies it as a duplicate — and the original problem is still unfixed.

Resubmitting with the wrong original reference number attaches your correction to somebody else's claim.

And voiding when you meant to replace withdraws the claim entirely, which is occasionally what you want and usually is not.

Chapter 17's Case Study 2 was months of duplicate denials that turned out to be somebody else's claim. This is the field that distinguishes my corrected claim from a second claimand a practice that resubmits without it will spend those months regularly.


25.4 The service lines: item 24, column by column

Item 24 is the claim. Six service lines, each with the same columns.

   24A  DATE(S) OF SERVICE        from and to
   24B  PLACE OF SERVICE          the two-digit code — §25.8
   24C  EMG                       emergency indicator, if the payer wants it
   24D  PROCEDURES, SERVICES,     the CPT/HCPCS code
        OR SUPPLIES               ► and up to FOUR MODIFIERS
   24E  DIAGNOSIS POINTER         the LETTERS from item 21 — §25.5
   24F  $ CHARGES                 the practice's charge — Ch. 23 §23.7
   24G  DAYS OR UNITS             ► Ch. 20 §20.3's arithmetic lands here
   24H  EPSDT / Family Plan
   24I  ID QUALIFIER              } the RENDERING provider — §25.6
   24J  RENDERING PROVIDER ID     }

The shaded area, which is half a line and does real work

Each of the six service lines has a shaded upper portion, and it is not decoration.

The shaded area carries SUPPLEMENTAL information about the service on the line below it — data the payer requires that has no dedicated item of its own.

What lands there, in rough order of how often you will meet it:

NDC data for drug lines. Chapter 20 §20.8's whole problem arrives here: a qualifier, the 11-digit NDC, a unit-of-measure qualifier, and a quantity — and Chapter 20 established that the NDC quantity and the HCPCS units in 24G are different numbers in different units of measure, correctly.

Narrative descriptions for unlisted codes. Chapter 13 §13.9's special report and Chapter 20 §20.3's unclassified drugs both need words on the claim, and the shaded area is one of the two places they can go — item 19 being the other.

Supplemental provider identifiers, where a payer still requires one.

And anesthesia minutes, on payers that want them at the line level rather than in units.

Two practical notes. The shaded area is per line, which means a claim with two drug lines carries two NDCs, each above its own drug. And most billers never see it, because their system populates it from a charge master mapping — which is exactly Chapter 20 §20.8's recommended fix, and which means when it is wrong, it is wrong on every claim until somebody looks at the mapping.

The columns that cause the most trouble

24D's modifier positions — there are four. Chapter 14 §14.3 said so and this is why. A line needing more than four uses modifier 99, and the additional modifiers go in item 19.

24G, days or units. Chapter 20 §20.3's units arithmetic produces a number, and this is where it goes. A J-code's units, an anesthesia charge's units, a therapy code's units — all here, and Chapter 21's medically unlikely edits check this column.

24F, charges. The practice's charge, not the allowed amount, not the expected payment. Chapter 23 §23.7's one rule applies: a charge below the allowed amount caps the payment.

🎓 Exam Watch

Item 24 questions are constant and they cluster into four:

"How many modifiers fit on a line?"four, in 24D. More requires 99 plus item 19.

"How many diagnoses fit in item 21? How many point to one line?"twelve in item 21, four in 24E. The asymmetry is the question.

"What goes in 24F?"the charge. Not the allowed amount. Candidates who have just learned Chapter 23 reach for the wrong one.

"Where do units go?"24G.

And one that looks like trivia and is not: "How many service lines does the form have?"six. A claim with more services than that becomes multiple claims, which raises the sequencing question Chapter 18 §18.8 covered — the highest-valued procedure should be on the first line of the first claim.


25.5 Diagnosis pointers and the four-per-line rule

The single most under-taught field on the form, and Chapter 22 §22.6 established why it matters: the pointer is the linkage between a service and the diagnoses that justify it.

Item 21 holds up to twelve diagnoses, lettered A through L.

Item 24E holds up to four LETTERS per service line, indicating which of those diagnoses support that service.

Four rules.

Point letters, not numbers. The 02/12 version uses letters. Older habits produce numbers, and some systems still display numbers while transmitting letters.

Point only what supports THAT line. A claim's twelve diagnoses do not all support every service. Pointing all four positions at everything is not thoroughness — it is a claim that the venipuncture was performed for the hypertension.

Sequence matters. The first pointer is the primary reason for that service.

And a service pointed at a diagnosis that does not support it will deny — Chapter 22 §22.6 — even when a supporting diagnosis is elsewhere on the claim.

🔢 Code It

Account 10-4471's pointers, and why they are what they are.

Item 21 carries four diagnoses:

text A = M25.561 pain in right knee B = E11.9 type 2 diabetes without complications C = I10 essential hypertension D = E78.5 hyperlipidemia

Now point each service line.

Line Code Pointers Why
1 99214-25 A B C D the E/M addressed all four problems — that is what made it separately identifiable (Ch. 14 §14.4)
2 20610-RT A the injection treated the knee. It has nothing to do with the diabetes
3 J1030 A the drug was injected into the knee
4 36415 B the venipuncture was for the A1c — a diabetes test

Three things to notice.

Line 1 is the only line using all four, and it is using them because the E/M genuinely addressed four problems. This is Chapter 15's problems element and Chapter 14's modifier 25 evidence appearing as a claim field.

Line 4 points at B, not A. The blood was drawn for the hemoglobin A1c and the lipid panel. Pointing it at the knee would be asserting that a venipuncture treats knee pain.

And nothing points at D alone, even though the lipid panel was ordered for the hyperlipidemia — because Chapter 19 §19.12 established that the lab tests are on the reference laboratory's claim, not Northgate's. The panel's pointer lives on somebody else's form.

A claim's pointers are a set of small arguments, one per line, and each one has to be true.

🔍 Check Your Understanding

A claim's item 21 reads:

text A = J44.1 COPD with acute exacerbation B = I10 essential hypertension C = E11.9 type 2 diabetes without complications

The claim has three service lines: an office visit, a spirometry, and a hemoglobin A1c drawn in office.

Point each line, and say what is wrong with the alternative.

Answer:

The office visit → A B C. All three conditions were addressed, assuming the note supports it — and Chapter 15 §15.5's definition of "addressed" decides whether it does.

The spirometry → A. It is a pulmonary function test. Pointing it at the hypertension asserts that spirometry evaluates blood pressure.

The venipuncture → C. The blood was drawn for the A1c.

Now the alternative students reach for: point everything at A B C.

It is faster, it never looks obviously wrong, and it is three false statements instead of one true one. Two of them will pass adjudication and one may not — but the problem is not primarily that it denies. It is that the claim now asserts a set of clinical relationships that do not exist, and Chapter 22 §22.6 established that the pointer is the medical necessity linkage.

The rule to carry: a pointer is a claim about why a service was performed. If you would not say the sentence out loud, do not point the line.


25.6 Rendering, billing, and service facility providers

Three provider identities on one form, and confusing them is a recurring, expensive error.

Who Where What it means
RENDERING 24I / 24J the individual who performed the service
BILLING 33, 33a, 33b the entity submitting and being paid
SERVICE FACILITY 32, 32a, 32b where the service was performed, if not the billing address

Three rules that resolve most confusion.

The rendering provider is a person. Chapter 15 §15.11's incident-to and split/shared questions land here: the rendering provider field says who performed it, and an incident-to claim reports the supervising physician because the service is billed as the physician's.

⚠️ Where Claims Die

Whose NPI goes in 24J on an incident-to claim is the question that carries the most money per keystroke in this chapter.

Chapter 15 §15.11 established the rule: incident-to permits qualifying office services furnished by auxiliary personnel to be billed under the physician's NPI at 100% rather than the 85% that applies when a non-physician practitioner bills under their own.

So the field decides the payment, and it decides it by naming a person.

Three ways it goes wrong, and they are not equally serious:

The NPP's NPI is entered on a claim that qualified for incident-to. An underpayment — 85% where 100% was available. Silent, and it accrues.

The physician's NPI is entered on a claim that did NOT qualify — a new problem, a new patient, no established plan of care, or no physician in the office suite. That is an overpayment, and it is a claim asserting that a physician performed or supervised a service under conditions that did not exist.

And the default. Chapter 15 §15.11's failure mode: a practice that configures the physician's NPI as the default for all established patients and never re-evaluates per encounter. Every visit where someone raises something new is then billed at 100% when it was entitled to 85% — with no denial, no edit, and no phone call.

The field is one entry and the rule requires a per-encounter judgment. Those two facts are in permanent tension, and no system default resolves it.

The billing provider is usually an organization, and the payment goes to it.

And item 32 is not optional decoration. When the service was performed somewhere other than the billing address — an outpatient site, a nursing facility, a patient's home — item 32 says where. Chapter 23 §23.5's site-of-service differential depends on the place of service code, and item 32 is how the payer knows the code is plausible.

⚠️ Where Claims Die

Item 33's billing provider and item 32's service facility disagreeing with item 24B's place of service is a specific, silent, and expensive failure.

Chapter 23's Case Study 1 was exactly this: a practice converted to a hospital outpatient department, place of service still 11, and the claim paid at the office rate for a service performed in a facility.

The internal consistency check is one query and almost nobody runs it:

text Does the place of service in 24B match the site in item 32? Does item 32's site match where the service was actually rendered? Is the billing provider in 33 the entity entitled to the payment?

All three can be individually plausible and jointly wrong, which is why the check has to compare them to each other rather than validate them separately.

Item 27 — accept assignment, and what a checkbox decides

One checkbox, and it determines what the practice may collect.

Accepting assignment means the provider agrees to accept the payer's allowed amount as payment in full — collecting the patient's cost-sharing and writing off the difference between the charge and the allowed amount as a contractual adjustment. Chapter 2 §2.5.

In network, this is generally not a choice. A participating provider agreed to it in the contract, and the checkbox reports a fact rather than making a decision.

Out of network is where it becomes a decision, and the consequences differ by payer type:

Under Medicare, a non-participating provider who does not accept assignment may collect more than the Medicare-allowed amount — up to a statutory ceiling — and is paid differently. The rules are specific and they are the reason "participating" and "non-participating" are formal statuses rather than descriptions.

Under commercial coverage, out-of-network balance billing was historically permitted and is now restricted in defined circumstances by federal law — Chapter 32 §32.4.

Why a coder should care about a checkbox: because item 27 and item 28's total are what the patient's eventual balance is computed from, and because a claim that reports non-assignment when the provider is contractually assigned has misrepresented the practice's own agreement.


25.7 NPI, taxonomy, and identifiers that do not belong here

The NPI

The National Provider Identifier is a ten-digit identifier assigned to health care providers. It is the identifier, and it replaced a proliferation of payer-specific numbers.

Two types, and the distinction is constantly confused:

Type 1 an INDIVIDUAL provider — a person. Follows the person for their career
Type 2 an ORGANIZATION — a group, a facility, a supplier

A solo physician practicing as an organization may have both, and they are not interchangeable: the individual's Type 1 goes in the rendering field; the organization's Type 2 goes in the billing field.

An NPI is not proof of anything except identity. It does not establish enrollment, participation, or eligibility to be paid — which is Chapter 19 §19.5's referring-provider denial: a valid NPI belonging to a physician who is not enrolled with that payer produces a denial the billing office cannot fix.

Taxonomy

A taxonomy code identifies the provider's specialty, and payers use it to distinguish among providers who share an organization or to apply specialty-specific rules.

It matters more than most billers realize, because Chapter 15 §15.2's new-versus-established test and Chapter 16 §16.2's initial-versus-subsequent test both turn on specialty as the payer has it recorded — and taxonomy is part of how it is recorded.

The identifiers that no longer belong

The form once carried a variety of legacy identifiers, and some are still submitted out of habit:

  • Payer-specific provider numbers that the NPI replaced
  • Tax identification numbers in fields that no longer want them
  • Numbers in items that were repurposed between form versions

Two effects, and the second is worse. A legacy identifier in an unexpected field may cause a rejection — annoying and visible. Or it may be ignored, in which case the practice keeps populating a field that does nothing, forever, and nobody ever learns.


25.8 Place of service codes

Chapter 23 §23.5 owns the payment consequence. This section owns the field.

Item 24B, two digits, per line — which means a single claim can carry lines with different places of service, and that is correct when it happened.

The codes you will use are in Chapter 23 §23.5's table: 11 office · 12 home · 19 off-campus outpatient hospital · 21 inpatient hospital · 22 on-campus outpatient hospital · 23 emergency department · 24 ambulatory surgical center · 31 skilled nursing facility · 02/10 telehealth.

Three field-level notes.

It is per line, not per claim. A physician who sees a patient in the office and later that day in a facility may have both on one claim, correctly.

It must be consistent with item 32. §25.6.

And the telehealth codes have moved. Chapter 23 §23.5 said to verify current policy rather than carry a habit, and it is worth repeating in the chapter where the field actually is.


25.9 The fields that most often cause a rejection

A rejection is not a denial — Chapter 27 §27.7 draws the distinction and Chapter 29 §29.1 depends on it. A rejected claim was never adjudicated.

The rejection causes, in rough order of frequency:

   1.  PATIENT NOT FOUND ........... items 1a, 2, 3
       name, ID, or date of birth does not match the payer's record
       ► Chapter 24 §24.2 is the prevention

   2.  SUBSCRIBER / RELATIONSHIP ... items 4, 6, 11
       patient is not the subscriber and item 4 is blank

   3.  REFERRING PROVIDER ......... item 17b
       blank, wrong person, unenrolled, or name/NPI mismatch
       ► Chapter 19 §19.5

   4.  DIAGNOSIS PROBLEMS .......... item 21
       invalid code, wrong ICD indicator, or a code that
       requires more characters

   5.  POINTER PROBLEMS ............ item 24E
       pointing at a letter that has no diagnosis behind it

   6.  BILLING PROVIDER ............ items 33, 33a
       NPI/name mismatch, or an NPI not enrolled with the payer

   7.  MISSING REQUIRED FIELD ...... varies by payer
       ► the payer's companion guide says which

Two observations about that list.

Six of the seven are front-end fields. Chapter 24's argument, arriving as a rejection report.

And every one of them is cheap to fix and expensive to ignore, because a rejection that nobody reads is a claim that never existed — Chapter 24 §24.1's fifth row.

The companion guide, which answers cause seven

"Missing required field — varies by payer" is not a satisfying seventh entry, and there is a document that resolves it.

A companion guide is a payer's published document stating how it wants the standard transaction populated — which optional fields it requires, what values it accepts, and what it will reject.

Three facts.

Almost every payer of any size publishes one, usually in a provider portal, usually as a PDF nobody in the billing office has opened.

It is specific in exactly the way the NUCC manual is not. The NUCC manual says what an item is for; the companion guide says what this payer requires in it, and where they differ for that payer's claims, the companion guide governs.

And it is the answer to the recurring question "why does this payer reject what everyone else accepts?" The answer is usually printed, and usually nobody has looked.

This is the third time this book has recommended reading a payer's own published document — after Chapter 14 §14.8's bilateral conventions and Chapter 21 §21.11's proprietary edits. The pattern is not a coincidence: the questions a billing office cannot answer from general knowledge are almost always answered somewhere in the payer's own materials, and the barrier is that nobody has time to go looking until something has already gone wrong.

📋 Read the Chart

Source: a CMS-1500 built by someone else, handed to you to find out why it denied What it says:

text 2 [patient name] 4 [blank] 6 SELF 11d YES 17 [performing physician] 17b [that physician's NPI] 21 ICD indicator 0 A M54.50 B E11.9 22 [blank] 24 A: 03/02 B: 22 D: 99213 E: A B F: 145.00 G: 1 A: 03/02 B: 11 D: 97110 E: A F: 90.00 G: 2 27 NO 32 [blank] 33 [group name] 33a [Type 2 NPI]

What it means: at least five things are wrong, and only one of them is a coding error.

Item 4 blank with item 11d "yes." The claim says there is another health benefit plan and then supplies no other insured. Either 11d is wrong or items 9 and 4 are incomplete — and §25.2's block is the reason to find out which.

Item 17 populated with the performing physician. Nobody referred this patient to themselves. A referring provider who is also the rendering provider is usually a data-entry default, and it introduces §25.9's third rejection cause where none existed.

Two different places of service on one claim, 22 and 11. That is permissible — §25.8 — but item 32 is blank, so the claim asserts a hospital outpatient service performed at the billing address. Chapter 23's Case Study 1 is exactly this, and it is the line that will pay wrong without denying.

97110 with 2 units and no time documented in the record — Chapter 19 §19.11's timed-code arithmetic, arriving as a units field. 2 units requires 23 minutes of total timed services, and the claim asserts it.

And item 27 "no" on a claim from a group billing under a Type 2 NPI. If this group is contracted with the payer, non-assignment misrepresents its own agreement — §25.6.

What to do about it: not fix the codes. Four of the five are non-clinical fields, and a coder who reviews only items 21 and 24D will hand this claim back unchanged.

Where it appears: on every denied claim anyone asks you to look at. The instinct is to check the codes. The codes are usually fine.

📞 On the Phone

"Your claim rejected for item 17b."

The message names a box on a form nobody printed, and a biller who freezes at that has a vocabulary problem rather than a claim problem.

What to do, in order:

Translate the item. 17b is the referring provider's NPI. §25.3.

Determine which of the four causes it is. Blank? Wrong person? Not enrolled with this payer? Name and NPI not matching what the payer has? Chapter 19 §19.5's list, and the four have different fixes.

If it is the third, stop working it as a billing problem. An unenrolled referring provider is a credentialing matter and no amount of resubmission changes it. Escalate it and tell the ordering office, because their other referrals are rejecting too and they may not know.

What works on the call: "Can you tell me what the plan has on file for that NPI — the name and whether the provider is currently enrolled? I want to know whether this is a data mismatch on our end or an enrollment issue on theirs."

And write the answer down against the provider, not against the claim. The next twelve claims naming that physician will have the same problem, and a note on one claim helps none of them.


25.10 🗂️ The Encounter — building Account 10-4471's claim

Everything the book has established, on one form.

(Constructed. Consistent with the account as this book has built it since Chapter 1.)

The top: who and what coverage

   1    Group Health Plan                    ► Northfield Mutual, commercial PPO
   1a   [insured's ID]                       ► from the card, not from memory
   2    [patient name]                        ► as it appears on the card
   3    [birth date] / F
   4    SAME                                  ► the patient IS the subscriber
   5    [patient address]
   6    SELF
   9    [blank]                               ► no secondary coverage
   10a  NO   10b  NO   10c  NO                ► not employment, auto, or other accident
   11   [group number]
   11d  NO                                    ► no other health benefit plan
   12   SIGNATURE ON FILE                     ► and it is
   13   SIGNATURE ON FILE

The middle: circumstances and diagnoses

   14   [blank or the onset qualifier]
   17   [blank]                               ► no referring provider; the patient's
                                                own PCP performed the service
   19   [blank]
   20   NO                                    ► no outside lab charges on THIS claim
                                                (Ch. 19 §19.12 — the reference lab bills its own)
   21   ICD indicator: 0                      ► ICD-10-CM
        A  M25.561      B  E11.9
        C  I10          D  E78.5
   22   [blank]                               ► not a corrected claim... yet (Ch. 29 §29.6)
   23   [blank]                               ► no prior authorization required (Ch. 24 §24.11)

Item 17 is blank and that is correct. The physician who performed the service is the patient's own primary care physician — there is no referring provider, because nobody referred her. §25.9's third rejection cause cannot arise on this claim, and a biller who populated item 17 with the performing physician would have created a problem out of nothing.

Item 21's four diagnoses are in a deliberate order. A is M25.561, the knee — the reason three of the four service lines exist. B, C, and D are the chronic conditions, in the order the assessment addressed them. Sequencing is not arbitrary: the first-listed diagnosis is conventionally the principal reason for the encounter, and on this claim the knee is what made the visit different from the two the patient had already had this year.

And item 21 is where Q2 lives, quietly. B is E11.9 — type 2 diabetes without complications — which Chapter 9 established was correct for March 14 and which Chapter 36 will establish is incomplete as a description of the patient. The claim is right. The record is thin. Those are different findings, and this field is where the difference eventually costs something.

Item 20 is "no." Chapter 19 §19.12: the reference laboratory bills 83036 and 80061 on its own claim. Northgate did not purchase those tests and does not report them here.

The service lines

   24  A: DOS      B: POS   D: CODE/MOD    E: PTR    F: CHARGE   G: UNITS
   ─────────────────────────────────────────────────────────────────────
   1   03/14–03/14   11     99214  25      A B C D    185.00       1
   2   03/14–03/14   11     20610  RT      A          150.00       1
   3   03/14–03/14   11     J1030            A         18.00       1
   4   03/14–03/14   11     36415            B         14.00       1
   ─────────────────────────────────────────────────────────────────────
   28  TOTAL CHARGE                                    367.00

Every column, justified by a chapter:

Column Value Established in
24B place of service 11 — office Ch. 23 §23.5 · §25.8
24D line 1 modifier 25 Ch. 14 §14.4 — Q1, answered
24D line 2 modifier RT Ch. 14 §14.8
24E pointers A B C D / A / A / B §25.5
24F charges the practice's charge Ch. 23 §23.7 — Q6: nobody can derive \$185.00
24G units 1 on J1030 Ch. 20 §20.3 — 40 mg ÷ 40 mg

The bottom: providers and the total

   27   ACCEPT ASSIGNMENT?  YES        ► in network; Ch. 2 §2.5
   28   TOTAL CHARGE        $367.00
   29   AMOUNT PAID         $30.00     ► the copay collected at check-in (Ch. 24 §24.11)
   31   [physician signature / date]
   32   [blank]                        ► service performed at the billing address
   33   Northgate Family Medicine
   33a  [Type 2 NPI]                   ► the ORGANIZATION
   24J  [Type 1 NPI]                   ► the PHYSICIAN who performed it

Item 29 is the one people forget. The \$30.00 collected at check-in goes here, and a claim that omits it asks the payer to pay an amount the practice has already partly collected. Chapter 28 §28.5 covers what the remittance does with it.

What is missing, and correctly

Three things this book has spent chapters establishing are NOT on this form:

The lidocaine. Chapter 17 §17.1's surgical package, Chapter 20 §20.10's usual supplies, Chapter 21 §21.6's standards of practice. Three independent reasons, one absent line.

83036 and 80061. On the reference laboratory's claim — Chapter 19 §19.12.

And 99000, specimen handling. Chapter 19 §19.12 said Northgate has never asked whether it is payable. It is still not asking.

This is the whole book on one page.

Every field on it was decided by something, and by this point in the book you can name what.

What happens to it next

This form is now finished, and it is about to stop being a form.

Chapter 27 turns it into an 837P — the same data as loops and segments — hands it to a clearinghouse, and follows the acknowledgments back. Three days elapse between the note being signed on day 0 and the payer acknowledging receipt on day 3, and Chapter 1's Encounter timeline has already told you that.

Chapter 28 reads what comes back on day 17: a remittance paying three lines and denying one, with CO-97 and RARC N19 on line 1 — the line whose modifier 25 Chapter 14 defended, whose edit Chapter 21 walked, and whose override was correct.

The claim is right. Everything on it has been justified by a chapter. And it is still going to be denied, which is the thing about this work that no amount of accuracy prevents and which Part VI is about.


Summary

The CMS-1500 is the professional claim form; the 837P is the same data in a different container. Maintained by the NUCC, whose free reference instruction manual answers most "what goes in this box" questions. A rejection naming an ITEM describes the form; one naming a LOOP describes the 837P.

The paper form is designed to be SCANNED — red drop-out ink, no handwriting, nothing outside its box, no highlighting or correction fluid. The rigid field positions and the six service lines are consequences of a scanner, not arbitrary bureaucracy.

Items 1–13 — patient, insured, other coverage. Item 4 exists because the patient and the insured are frequently different people. Items 10a–10c are the coordination-of-benefits question in claim form. Items 9a–9d capture OTHER coverage, and their emptiness is usually not a decision — the failure is not that the block is blank; it is that nobody distinguishes "blank because there is none" from "blank because nobody asked." "Signature on file" asserts that a signature IS on file — the same shape as GA, JW, and KX, in the oldest field on the form.

Items 14–23 — circumstances. 14 and 15 carry dates that mean nothing without their qualifiers. 17b is the referring provider's NPI and Chapter 19 §19.5's highest-volume diagnostic denial. 19 is the narrative field, where unclassified drug information goes. 21 holds twelve diagnoses, A–L, with an ICD indicator. 22 carries the resubmission code and the original reference numberresubmitting with it blank creates a DUPLICATE, not a correction. 23 holds a prior authorization number OR a CLIA number, depending on what you are billing.

Item 24 — six service lines. 24B place of service, per line. 24D the code and up to four modifiers (more requires 99 plus item 19). 24E the pointers. 24F the charge, not the allowed amount. 24G the units. And each line's SHADED AREA carries supplemental data — NDC information on drug lines, narratives for unlisted codes, and anesthesia minutes on payers that want them. It is per line, and most billers never see it because a charge master mapping populates it — which means when it is wrong, it is wrong on every claim.

TWELVE DIAGNOSES ON THE CLAIM. FOUR POINTERS PER LINE.

Point letters. Point only what supports THAT line. Sequence matters. A service pointed at a diagnosis that does not support it denies even when a supporting diagnosis is elsewhere on the claim.

Three provider identities: RENDERING (24I/24J, a person) · BILLING (33, usually an organization, and who gets paid) · SERVICE FACILITY (32, where, when not the billing address).

Whose NPI goes in 24J on an incident-to claim carries the most money per keystroke in this chapter — 100% under the physician's, 85% under the NPP's. The NPP's NPI on a qualifying claim is a silent underpayment; the physician's NPI on a non-qualifying one is an overpayment asserting a supervision that did not occur. The field is one entry and the rule requires a per-encounter judgment.

NPI: Type 1 is an individual, Type 2 is an organization, and they are not interchangeable. An NPI proves identity and nothing else — not enrollment, not participation, not eligibility to be paid. Taxonomy carries specialty, which is what Chapter 15's new/established and Chapter 16's initial/subsequent tests actually turn on.

Item 27, accept assignment, reports agreement to take the allowed amount as payment in full. In network it reports a fact; out of network it is a decision, with different rules under Medicare (participating versus non-participating, and a statutory ceiling) and under commercial coverage, where federal law now restricts balance billing in defined circumstances.

Rejections cluster into seven causes and six of them are front-end fields. A rejection that nobody reads is a claim that never existed. And cause seven — "missing required field, varies by payer" — is answered by the payer's COMPANION GUIDE, which almost every payer publishes and almost nobody opens. The NUCC manual says what an item is FOR; the companion guide says what THIS payer requires in it.

Account 10-4471's claim: place of service 11 on every line · 99214-25 pointing A B C D because the E/M addressed all four problems · 20610-RT and J1030 pointing A · 36415 pointing B, because the blood was drawn for the A1c · \$367.00** total · **\$30.00 in item 29 · item 17 blank, correctly, because nobody referred her · item 20 "no", because the reference laboratory bills its own tests.

And three things are absent, correctly: the lidocaine, the two laboratory tests, and 99000. Every one of them was decided by a chapter, and by now you can name which.


Key Terms

CMS-1500 — the standard claim form for professional services. (Ch.25)

NUCC — the National Uniform Claim Committee, which maintains the form and publishes its reference instruction manual. (Ch.25)

Item number — the numbered field on the form; the industry's coordinate system for describing claim problems. (Ch.25)

837P — the electronic professional claim transaction carrying the same data. (Ch.25)

Patient versus insured — the distinction underlying items 2 and 4; the person receiving care and the person holding the policy are frequently different. (Ch.25)

Signature on file — the phrase entered in items 12 and 13 in place of a signature, asserting that a signed authorization exists and is current. (Ch.25)

Diagnosis pointer — the letter or letters in item 24E linking a service line to the diagnoses in item 21 that justify it. (Ch.25)

ICD indicator — the field in item 21 stating which diagnosis code set is in use. (Ch.25)

Rendering provider — the individual who performed the service, identified in 24I/24J. (Ch.25)

Billing provider — the entity submitting the claim and receiving payment, identified in item 33. (Ch.25)

Service facility — where the service was performed when that is not the billing address, identified in item 32. (Ch.25)

NPI — the National Provider Identifier, a ten-digit identifier that proves identity and nothing else. (Ch.25)

Type 1 NPI — an individual provider's identifier. (Ch.25)

Type 2 NPI — an organization's identifier. (Ch.25)

Taxonomy code — the code identifying a provider's specialty, which payers use to apply specialty-specific rules. (Ch.25)

Place of service code — the two-digit code in item 24B, entered per line, selecting the facility or non-facility payment. (Ch.25)

Accept assignment — item 27; the provider's agreement to accept the allowed amount as payment in full. In network it reports a fact; out of network it is a decision. (Ch.25)

Companion guide — a payer's published document stating how it requires the standard transaction to be populated. Governs that payer's claims where it differs from general instruction. (Ch.25)

Resubmission code — the item 22 value indicating a replacement or a void, submitted with the original claim's reference number. Omitting it creates a duplicate rather than a correction. (Ch.25)

Shaded area — the upper portion of each service line, carrying supplemental information including NDC data for drug lines. (Ch.25)

Red drop-out ink — the printing specification allowing a scanner to read a paper claim's contents while ignoring the form's own lines. (Ch.25)


Spaced Review

  1. Why learn a form almost nobody submits on paper? Give two reasons.

  2. Who maintains the CMS-1500, and what free document answers most "what goes in this box" questions?

  3. A claim is for a child covered on a parent's policy. What goes in item 2, and what goes in item 4?

  4. What do items 10a–10c ask, and which chapter's front-desk question do they correspond to?

  5. "Signature on file" is an assertion. Name three other fields in this book that make the same kind of assertion, and what each one asserts.

  6. What is in item 17b, and what four things go wrong with it?

  7. How many diagnoses fit in item 21? How many pointers per service line? Why is the asymmetry a problem?

  8. Account 10-4471's line 4 is 36415 and points at B, not A. Explain.

  9. Distinguish the rendering, billing, and service facility providers, and give the items for each.

  10. Distinguish a Type 1 from a Type 2 NPI. What does an NPI prove, and what does it not?

  11. (Chapter 23) Item 24B says 11 and item 32 names a hospital outpatient department. What has happened, and which case study is it?

  12. Name three things that are correctly absent from Account 10-4471's claim, and the chapter that decided each.

  13. Why is a paper claim printed in red ink, and why may nothing be handwritten? What does that explain about the form's shape?

  14. Items 9a–9d are blank on most claims. What is the failure, and why is it not "the block is empty"?

  15. A claim is resubmitted with item 22 blank. What has the practice created, and what has it not fixed?

  16. What is a companion guide, and what does it settle that the NUCC manual does not? Name the two other payer-published documents this book has told you to read.

  17. A drug line requires an NDC. Where on the form does it go, and why is its quantity a different number from the units in 24G?