Lesson 0012

PCN Is Not PCCN

The practical product skill: know which claim identifier belongs to your app, the submitted claim, the clearinghouse, the payer, or the service line.

Your Tangible Win

After this lesson, you should be able to classify an identifier into one lane: APP, PCN, CHID, PCCN, or LINE.

Primary source to read after the lesson: Stedi: Resubmit or cancel claims.

The Core Idea

A claim workflow needs multiple identifiers because different systems assign identifiers at different moments. Stedi distinguishes the Patient Control Number, which you assign to the claim, from the Payer Claim Control Number, which the payer assigns when a claim enters its adjudication system (Stedi PCCN guidance).

CMS describes 276/277 claim status as a way to obtain and automatically post claim status information (CMS Claim Status Request and Response). CMS also says remittance advice reports adjudication decisions for claims and lines so providers can associate those decisions with the submitted claims and lines (CMS Remittance Advice).

Five Identifier Lanes

Lane Who Assigns It What It Is For
APP Your application. Database identity, permissions, audit trail, internal joins.
PCN Submitting provider, billing system, or your app. Correlating acknowledgments and ERAs back to the submitted claim.
CHID Clearinghouse or API vendor. Retrieving transactions, file executions, events, or vendor timelines.
PCCN Payer. Referencing the claim inside the payer adjudication system.
LINE Submitting provider, billing system, or your app. Correlating service-line errors and payment details.

The Dangerous Field

Do not store all of these in one column called claim_id. That works only until a 277CA, 835 ERA, replacement claim, duplicate ERA, or clearinghouse webhook needs a different identifier.

If You See Store As Why
claimInformation.patientControlNumber PCN Stedi maps it to X12 CLM01 and uses it to correlate 277CA and 835 responses.
claimReference.correlationId CHID Stedi assigns it as a tracking number when the claim is submitted.
tradingPartnerClaimNumber PCCN Stedi identifies it as the payer claim control number from a 277CA or status response.
providerControlNumber LINE Stedi maps it to the service-line control number used for line-level correlation.

Why This Matters

Rejected Claim

You may have APP, PCN, and CHID, but no PCCN yet.

Accepted Claim

A payer acknowledgment or status response may introduce PCCN, proving the payer can reference the claim.

Replacement

You may need a new PCN while still linking to the original PCCN, depending on payer rules.

Mini Case

A product stores one value named claim_id. At first it holds the app's database ID. Later a developer overwrites it with the payer's claim number from an ERA. Now the original app claim cannot be joined to its old submission attempts.

Product diagnosis: internal identity was overwritten by payer identity. The product needed separate columns or related records for app claim ID, patient control number, clearinghouse IDs, payer claim control number, and service-line control numbers.

Scenario Practice

Choose the identifier lane. Use only the code: APP, PCN, CHID, PCCN, or LINE.

1. Your database primary key for the claim row is claim_742. Which lane?
2. The submitted claim has claimInformation.patientControlNumber. Which lane?
3. The API response includes claimReference.correlationId. Which lane?
4. A payer response returns tradingPartnerClaimNumber. Which lane?
5. A service line has providerControlNumber. Which lane?
6. A claim was rejected before entering payer adjudication. Which identifier is safest for matching the 277CA back to your submitted claim?

What to Ask Me Next

Ask follow-up questions when you want to turn this into schema design. Good next questions: "What columns should a claim table have?", "How do I model 277CA and ERA correlation?", or "How do replacement claims link to originals?"

For review, keep the claim identifier map nearby.