Reference·SBR Segment·SBR02
X12 837P Reference

X12 837P SBR02 Field Guide: Individual Relationship Code Values and Common Mistakes

Jul 27, 2026 · 4 min read
← SBR01 SBR03 →

SBR02 has to agree with whatever the patient loop elsewhere in the claim implies about the subscriber relationship — when the two disagree, the claim doesn't fail on syntax, it fails on a payer edit that's much harder to trace back to this one field.

Quick answer

SBR02 is the Individual Relationship Code in an X12 837P claim — it states how the patient being treated relates to the subscriber who holds the insurance policy named in that SBR loop.

Valid code values

18
Self — the patient is the subscriber
01
Spouse — the patient is the subscriber's spouse
19
Child — the patient is the subscriber's child
G8
Other Relationship — used when none of the specific relationship codes apply

Example

Synthetic example Generated by Synthibase
SBR*P*18*GRP-9042217*ACME REGIONAL HEALTH PLAN*****CI*

The 18 following SBR01 is SBR02, indicating the patient is the subscriber. Synthetic claim data.

Where this trips people up

When SBR02 is 18 (self), most 837P implementation guides expect the claim to omit a separate patient loop and use the subscriber's demographics directly — test data that sets SBR02 to 18 but still builds out a distinct patient loop produces a claim that's internally contradictory, and payers vary widely in whether they catch it or just adjudicate against the wrong person.

X12 837P SBR Segment Guide: Fields, Format, and Testing Gotchas
COB Claims Testing: How to Generate Coordination of Benefits Scenarios
EDI Rejection Codes: Complete List and How to Fix Them
Keep subscriber and patient loops consistent
Synthibase generates synthetic 837P claims where SBR02 and the patient loop always agree, so relationship-mismatch edits never contaminate your test results.
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.