What Is X12 837P REF02? Reference Identification, Explained for Testers
REF02 is just a string — nothing in the segment itself enforces that a value claiming to be a prior authorization number actually looks like one the payer issued, which is exactly the kind of thing that slips past syntax validation and only fails once a real adjudication system checks it.
REF02 is the second element of the REF segment — the actual reference value being carried, whose format, length, and meaning depend entirely on the qualifier code sitting in REF01 immediately before it.
What this element contains
Example
AUTH88213221 in REF02 is only meaningful because REF01 = G1 tells the reader it is a prior authorization number. Synthetic claim data.
Where this trips people up
Test data generators that produce REF02 values with a random string generator, decoupled from what a real payer-issued authorization or referral number actually looks like, pass structural validation every time but fail any downstream check that verifies the reference against the payer's own records — a gap that stays invisible until claims hit a real adjudication system.