Reference·HCR Segment·HCR02
X12 278 Reference

HCR02 in X12 278: A Field Guide to Certification Number

Jul 27, 2026 · 4 min read
← HCR01 HCR*A1 →

HCR02 is the one field a provider's billing office actually keeps a copy of, because it's what gets typed into the claim months later — and it's also the field most likely to be empty, which is correct behavior, not a bug, whenever the request wasn't fully certified.

Quick answer

HCR02 is the certification number the payer assigns in a 278 response when a prior authorization request is approved, and it is the number the requester later carries into the corresponding 837 claim as a REF*G1 value.

What this element contains

HCR02
Certification number — a payer-assigned identifier, format and length vary by payer since X12 does not standardize it
Populated
Typically when HCR01 is A1 or A3 — full or partial certification usually comes with a number to reference later
Blank
Typically when HCR01 is A4 or A6 — a denial or pending review has nothing to certify yet

Example

Synthetic example Generated by Synthibase
HCR*A1*AUTH88213221*Approved as submitted

AUTH88213221 is the synthetic certification number this payer would expect to see cited on the matching claim. Synthetic test data.

Where this trips people up

Some claim-scrubbing tools flag any 837 claim missing a REF*G1 authorization number as incomplete, without checking whether the original 278 response actually returned one. If HCR01 was A4 or A6, HCR02 being blank is correct, and there was never a certification number to carry forward — the scrubber's flag is a false positive that only shows up when testing includes denied and pended responses alongside certified ones.

Testing X12 278 HCR: The Fields Your System Actually Needs to Handle
X12 278 Prior Authorization: Format, Fields, and Testing Guide
How to Reduce Claim Denials Through Better Pre-Submission Testing
Test authorization-to-claim matching end to end
Synthibase generates synthetic 278 responses whose HCR02 certification numbers link directly to synthetic 837 claims, so authorization-matching logic gets tested against both populated and correctly blank values before go-live.
Start free trial →
This page is written independently by Synthibase for testing and informational purposes. It is not an official publication of HL7 International or X12/Washington Publishing Company, and is not a substitute for reviewing the official standard or your trading partner's companion guide. See our Terms of Service for full legal terms.