Chapter 27 — Key Takeaways

What HIPAA did and did not do

Three requirement levels: required · SITUATIONAL · not used. Situational is where every companion guide lives.

The companion guide has now been named FOUR times.

Ch. 14 §14.8 bilateral conventions · Ch. 21 §21.11 proprietary edits · Ch. 25 §25.9 required fields · Ch. 27 the transaction itself. That should tell you something.

A claim is a standard transaction, carrying standard code sets, identifying parties by standard identifiers — three different things that can be wrong, arriving as messages a biller may not be able to tell apart.

Versions (4010 → 5010) are industry events, not software updates, and they break whatever your practice does least often.

The transaction set

Odd asks, even answers. A memory hook, not a rule, and it works.

The exam trap: 835 versus 277. A 277 gives status; an 835 gives what was paid — and only the 835 carries the CARC and RARC codes Ch. 28 §28.4 needs.

The 837

An 837 is not a picture of a form. It is the form's data with the boxes removed.

The six-service-line limit belongs to the PAPER FORM. So does much else. Software that imposes it is imposing a constraint the transaction does not have — when a system says a claim must be split, ask whose rule that is.

The four modifier positions are SV101-3 through SV101-6 — so Ch. 14 §14.3's rule is in the transaction, which is why modifier 99 exists.

Loops and segments, in three words

A LOOP is a level. A SEGMENT is a line of data. A DATA ELEMENT is one field.

   INTERCHANGE → 1000A/B submitter/receiver → 2000A billing provider
     → 2000B subscriber → 2000C patient (if different)
       → 2300 THE CLAIM (charges, POS, DIAGNOSES)
         → 2400 ONE SERVICE LINE (code, modifiers, charge, units, POINTERS)

   SV1*HC:99214:25*185.00*UN*1***1:2:3:4~

Pointers are LETTERS on the form and NUMBERS in the transaction. Same claim. An empty position between two delimiters still exists — which is why a payer can reject an element you never filled in.

The clearinghouse

Four things it does: connectivity · validation · routing · translation.

It fixes some things SILENTLY, and that is not entirely a favor.

The file you sent and the file the payer received are two artifacts. A defect your clearinghouse consistently repairs is a defect you will never find — until you change clearinghouses, at which point it arrives as a mass rejection of something that "has always worked."

Clearinghouse edits are somebody's implementation of somebody else's rule. They can be stale and over-strict, and they are not the payer's edits. Passing them proves the claim is well-formed and plausible. It predicts nothing about adjudication.

THREE ENROLLMENTS, separate, per payer:

The acknowledgments

   TA1     "Was the ENVELOPE readable?"          interchange
   999     "Was the FILE SYNTACTICALLY VALID?"   functional group
   277CA   "Did the PAYER ACCEPT THE CLAIM?"     claim level ◄── the one that matters

A 999 ACCEPTANCE IS NOT PROOF THAT YOUR CLAIM IS IN THE PAYER'S SYSTEM.

A 277CA message has three parts: a status category (A1 received · A2 accepted · A3/A7 returned), a status code (the specific reason), and an ENTITY IDENTIFIER — whose information.

The entity is the part people skip and it is frequently the whole answer. "Invalid NPI — referring" means look at item 17b. "Invalid NPI — BILLING" is an emergency, because that value is the same on every claim you send.

Ask your clearinghouse four questions, once: how to retrieve a transmitted 837 · where the 999 and 277CA live · what the report is called and who receives it · retention. Fifteen minutes.

Rejection versus denial

A rejection is more dangerous than a denial, and that is the opposite of most people's intuition.

A denial is visible, tracked, worked. A rejection sits in a report — has no CARC or RARC, and does not appear in your denial rate.

Day 1: ~2–3 minutes. Day 120: a different order of magnitude, and sometimes the answer is "nothing." A defect costs roughly its distance from the point of origin — Ch. 24 §24.1's ratio again.

Proof of timely filing, strongest first: a payer acknowledgment naming the claim · a clearinghouse transmission report · your system's history · a note about a call.

The trap: a claim rejected and resubmitted late was never timely filed — and the acknowledgment you are about to produce proves it.

Attachments, modes, status

There is still no universal electronic attachment mechanism. The 275 exists with incomplete adoption; esMD handles Medicare records requests; payer portals and clearinghouse services work and are not standard; fax persists.

Three defenses: identify the document so it can be matched · use the payer's stated method · record the submission.

Claims go in BATCH; eligibility runs REAL TIME — because an eligibility answer is a lookup and a claim requires adjudication.

Use the 276 for claims genuinely unaccounted for — not as a substitute for reading acknowledgments you already have.

Key terms

EDI · X12 · implementation guide · required/situational/not used · companion guide · 270/271 · 276/277 · 277CA · 278 · 835 · 837P/I/D · 999 · TA1 · loop · segment · data element · SV107 · clearinghouse · front-end rejection · rejection vs. denial · timely filing · proof of timely filing · batch · real time · claim status inquiry · attachment · 275 · esMD · EDI/ERA/EFT enrollment · status category code · entity identifier

Monday morning

You should be able to:

• Name the transactions and say what each is for.
• Translate a rejection naming a loop and segment into an item number.
• Say what your clearinghouse fixes for you — or admit you do not know, and go find out.
• Name the three enrollments and check which ones you have.
• Say what a 999 proves and what only a 277CA proves.
• Never call a rejection a denial.
• Produce a transmitted 837 and its acknowledgments on request.

The Encounter through the pipeline.

   DAY 0  Mar 14  visit, charge capture, \$30.00 copay, note signed 6:42 p.m.
   DAY 1  Mar 15  coded: 99214-25 · 20610-RT · J1030 · 36415
                  pointers set: ABCD · A · A · B
   DAY 2  Mar 16  scrubber clean · 837P transmitted 11:05 p.m.
   DAY 3  Mar 17  999 ACCEPTED · 277CA ACCEPTED
                  ► three days from service to acknowledged
   DAY 17 Mar 31  835: \$70.30 paid · LINE 1 DENIED CO-97 / N19

The pipeline worked perfectly and could not have caught the denial that was coming.

A scrubber checks rules. A clearinghouse checks format. A 277CA confirms receipt. None evaluates whether this payer, on this contract, will pay an E/M with modifier 25 alongside a minor procedure. That is adjudication, and the only way to learn it is to read what comes back.

Q4 remains open.