Schema Care

CMS 1500 OCR: Reading Paper Claim Forms Field by Field

By Schema CarePublished Updated

CMS 1500 OCR reads a paper professional claim by dropping the red form template, finding the typed characters left behind, and assigning each one to its item number. It works best on original red forms with machine print. The service line grid in item 24, signatures and dates still need a person to check before the data is used.

Why are paper CMS 1500 forms printed in red dropout ink?

Paper CMS 1500 forms are printed in red dropout ink so a scanner can make the form itself disappear. The scanner filters out that exact red, which leaves only the black characters a biller typed. The OCR engine then reads clean text instead of text tangled with box lines, labels and shading.

The NUCC 1500 Claim Form FAQ answers this directly. It says the form must be in red ink to be read by a scanner, and that the specified red "allows scanners to drop the form template during the imaging of the paper." The same answer warns that a vendor may choose not to process claim forms submitted in black ink.

The ink is not any red. The printing standards in the CMS Medicare Claims Processing Manual, chapter 26 name a specific OCR dropout ink, Flint J-6983, or an exact match, and forbid contamination with black ink or pigment. The chapter says compliance with the printing standards exists to support image processing such as optical character recognition, fax transmission and image storage. It also fixes the margins, the paper size and how far the printed image may skew.

One small mark stays black on purpose. The chapter 26 standards print the "1500" symbol in black. On the current 02/12 version, the NUCC FAQ adds that the symbol at the top is a QR code that scanners can be programmed to read, so software can tell it is looking at the 02/12 form rather than an older layout.

Many billers still call this form the HCFA 1500. The glossary in the NUCC 1500 Reference Instruction Manual explains why: CMS was formerly the Health Care Financing Administration, or HCFA. HCFA 1500 OCR and CMS 1500 OCR mean the same job.

The meaning of each box, from the insured's ID to the billing provider, belongs to a separate guide. The walkthrough of what the CMS 1500 patient and insured boxes 1 to 13 ask for covers each item in turn. This post covers how software reads them.

What happens to CMS 1500 OCR on black-and-white copies and faxes?

CMS 1500 OCR on a black-and-white copy or a fax loses the dropout trick. The red template turns into gray or black lines that the scanner cannot filter out, so every printed label and box border competes with the typed data. Characters that touch a line get clipped or merged, and the engine misreads more of them.

The problem has three common forms. A photocopy on a black-only copier turns the template into dark lines. A fax adds low resolution and speckle on top of that. A claim printed from software onto plain white paper, with the form drawn in black, never had dropout ink to begin with.

For Medicare, the rule is plain. Chapter 26 states that photocopies of the CMS-1500 claim form are not acceptable, and that forms must follow the NUCC printing specifications whether bought from a printer or printed in-house. Other payers set their own rules, and the NUCC FAQ notes only that a vendor may refuse black-ink forms.

When the copy is all you have, a few habits keep the damage down:

  • Rescan from the original if the original still exists in the office.
  • Scan at a resolution high enough for small print. The guide to the best scan resolution for medical document OCR covers when to go higher and what to do with faxes you cannot rescan.
  • Expect lower confidence across the whole page, and set the review rule so that more fields from that page go to a person.
  • Treat any field that sits on a box border as suspect, because a clipped character often looks like a valid but different one.

A field-level score helps here more than a page-level one. A fax may produce a clean member ID and a smeared charge on the same page, and only the charge needs a second look.

How CMS 1500 OCR reads the box 24 service line grid

CMS 1500 OCR reads item 24 as a grid of six service lines, each split into columns 24A through 24J. The hard part is keeping every value on its own line. Typed data often drifts above or below the boxes, so the engine has to decide which line a charge or code belongs to.

Chapter 26 describes the layout. The six service lines are divided horizontally. The top part of each line is shaded and holds supplemental information, such as a National Drug Code, and the manual states that this split "is not intended to allow the billing of 12 service lines." The lower, unshaded part carries the billed service.

A reader needs the date in 24A, place of service in 24B, procedure code and modifiers in 24D, pointer in 24E, charge in 24F, units in 24G and rendering NPI in 24J from each line. What each column holds is set out in reading one CMS 1500 service line across columns 24A to 24J.

The diagnosis pointer in 24E links each line to a code in item 21. Chapter 26 says the pointer on the 02/12 form is a letter from A to L. The NUCC manual adds that item 21 holds no more than 12 diagnosis codes, entered without the decimal point because it is implied.

Line alignment is where most grid errors start. A printer that feeds paper a little high pushes the second line's charge into the first line's shaded area. A good reader anchors each line on its date in 24A and its procedure code in 24D, then assigns the other values by horizontal position. When a value sits halfway between two lines, it should be flagged, not guessed.

The shaded part adds a second trap. A National Drug Code in the shaded area is a long string of digits preceded by the qualifier N4, according to chapter 26. A reader that ignores the shaded area loses it, and one that treats it as a service line invents a seventh line.

The grid also gives you a built-in check. Chapter 26 defines item 28 as the total of all charges in item 24F. If the extracted line charges do not add up to the extracted total, at least one value is wrong, and you know before anyone keys it.

Claims longer than six lines spill onto more pages. The NUCC manual says diagnosis codes from the first page must be repeated on later pages, and a claim with more than 50 service lines must be split. The general method for turning any scanned claim into fields, from intake to output, is set out in the guide to claims data extraction steps from scan to structured fields.

CMS 1500 data extraction output: what each field should look like

CMS 1500 data extraction output should give every item its own named field, a value in a fixed format, a confidence score and the place on the page where the value was found. Service lines come back as a list of six or fewer rows, one per printed line. Codes keep their exact characters, and amounts become plain numbers.

Formats matter because the paper form allows several. Chapter 26 requires an 8-digit date in birth date fields such as item 3, and allows a 6-digit or 8-digit date in other date fields. A clean output picks one format for every date, so "03 | 14 | 26" and "03142026" both become the same value.

The fields most downstream uses need are a short list:

  • Item 1a, the insured's ID number, kept exactly as printed, letters and all.
  • Item 2 and item 3, the patient's name and 8-digit birth date.
  • Item 21, the ICD indicator and up to 12 diagnosis codes, each with its letter A to L.
  • Item 24, one row per service line, with columns 24A to 24G and 24J.
  • Item 26, the patient account number the provider assigned.
  • Item 28, the total charge.
  • Item 33 and 33a, the billing provider's name and NPI.

An NPI can be checked as soon as it is read. The CMS NPI check digit requirements say an NPI is 9 digits followed by one check digit, calculated with the Luhn formula. Any single misread digit breaks the check.

A fictional CMS 1500 extraction sample

Everything in this sample is invented: the patient, the member ID, the codes chosen and the amounts. The review threshold in the example is set at 90%.

ItemRead as (example)ScoreWhere on page 1Outcome
1a Insured's IDXQT40011882297%Top right, row 1Passes
2 Patient nameSAMPLE, DANA96%Left, row 2Passes
3 Birth date07 22 198195%Center, row 2Passes
21 A DiagnosisJ06993%Item 21, line APasses
24A line 1 Date03 14 2694%Grid line 1, col APasses
24D line 1 Code9921396%Grid line 1, col DPasses
24F line 1 Charge145 0072%Grid line 1, col FSent to review
28 Total charge145 0095%Bottom, item 28Passes
33a Billing NPI123456789398%Bottom rightPasses

The line 1 charge scored low because the typed digits sat on the column border. It goes to a reviewer, who sees it on the page, confirms $145.00, and the sum check against item 28 passes. The NPI shown is the worked example from the CMS check digit document, used here as a sample.

Schema Care reads CMS-1500 and UB-04 fields, including diagnosis and procedure codes, and returns each one with a score and its page location; the document types Schema Care reads are listed on the homepage.

CMS 1500 OCR fields that still need a person

CMS 1500 OCR fields that still need a person are the ones where a correct-looking read can still be wrong: signatures, signature dates, the item 24 grid on misaligned print, and any handwritten entry. Confidence measures how sure the engine is about the characters, not whether the content makes sense on the claim.

Signatures are the clearest case. Chapter 26 says item 12 and item 13 can carry the patient's signature or "signature on file", and item 31 carries the provider's signature with a date. Software can tell that something is written in the box. It cannot tell whether the right person signed, so a person should confirm any signature field that matters to your process.

Dates deserve review even with high scores. A 6-digit date like 03 04 26 reads cleanly, but a swapped month and day reads cleanly too. Check service dates against the claim's other dates and against the visit record.

Handwritten entries need their own rules. A typed form with a handwritten correction in item 21 should never pass on the strength of the typed fields around it. The guide to which handwritten claim form fields OCR reads well sorts them by risk, and the main post on handwritten claim forms and OCR covers corrections and overwrites.

Some fields need review because of what they control rather than how they read. A diagnosis pointer that resolves to an empty line in item 21, or a procedure code that is valid but wrong for the visit, will score high and still cause a rejection. Pair the confidence rule with a few cross-field checks: pointers that resolve, line charges that sum to item 28, and an NPI that passes its check digit.

Institutional claims bring a different set of problems. Facility bills use the UB-04, with revenue code lines and many more locators, and the guide to UB-04 OCR for institutional claims covers how that form is read and checked.

All posts in Claims and Medical Bills