Reference·REF Segment·REF*G1
X12 837P Reference

X12 837P REF*G1 Field Guide: Prior Authorization Number Codes and Common Mistakes

Jul 27, 2026 · 4 min read
← REF02 REF*F8 →

A service that required prior authorization but whose claim omits REF*G1 doesn't fail at the clearinghouse — it sails through structurally clean and gets denied by the payer for lack of authorization on file, days after submission.

Quick answer

REF*G1 is the REF segment carrying qualifier G1, used in an 837P claim to state the prior authorization number a payer issued in advance of a service that required pre-approval.

What this element contains

REF01
G1 — the fixed qualifier value that marks this as a prior authorization number
REF02
The authorization number itself — assigned by the payer, usually returned from an earlier 278 prior authorization transaction
When required
Payer- and service-specific — some procedures, DME, and specialty drugs require it; most routine office visits do not

Example

Synthetic example Generated by Synthibase
REF*G1*AUTH88213221*

AUTH88213221 is the synthetic prior authorization number the payer issued before the service was rendered. Synthetic claim data.

Where this trips people up

Test suites built around a single claim template tend to either always include REF*G1 or never include it, when in reality whether it's required depends on the specific service and payer. That means the denial path for a claim that needed authorization but didn't get it — or got the wrong number — usually never gets exercised until a real claim trips it in production.

Testing X12 837P REF: 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-required claims correctly
Synthibase generates synthetic 837P claims that link REF*G1 authorization numbers back to synthetic 278 transactions, so authorization-matching logic gets tested end to end 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.