HL7 v2 Reference

HL7 v2 IN1-17 (Insured's Relationship to Patient): Format, Values, and Testing Notes

Jul 27, 2026 · 4 min read

Every eligibility bug involving a child's coverage traces back to the same root cause: nobody tested relationship code 03 before it shipped.

Quick answer

IN1-17 is a CE field carrying a coded value for the insured party's relationship to the patient — self, spouse, child, or other. It determines whether the system should expect the patient's demographics to match the subscriber's, or whether a separate subscriber record needs to be tracked.

Valid code values

Self — patient is the policyholder; patient and subscriber demographics should match exactly

Spouse — subscriber is the patient's spouse; expect differing name and possibly address

Child — subscriber is a parent or guardian; patient is a dependent minor in most cases

Other — catch-all for relationships not covered by the other codes, e.g. domestic partner in some implementations

Example

Synthetic example Generated by Synthibase

IN1|1|PPO2200^ACME REGIONAL HEALTH PLAN^ACMEID|66214|ACME REGIONAL HEALTH PLAN||||GRP-9042217||||||||DOE^JANE^M|01|||||||||||||||||||POL-77213840

IN1-17 is set to 01 (Self), meaning Jane M. Doe in IN1-16 is both the patient and the policyholder.

Where this trips people up

Test suites overwhelmingly default to relationship code 01 because it's the simplest case — patient and subscriber are the same person, so no cross-field validation is needed. The moment a real message arrives with code 03 for a dependent child, any logic that assumed patient and insured demographics always match starts silently misfiling eligibility responses, and that gap only surfaces once pediatric encounters start flowing through.

→

HL7 v2 IN1 Segment Guide: Fields, Format, and Testing Gotchas

→

COB Claims Testing: How to Generate Coordination of Benefits Scenarios

→

How to Build a Synthetic Patient Registry for Healthcare Testing

Test dependent coverage, not just the self-insured case

Synthibase generates IN1 segments spanning the full relationship code range — spouses, dependent children, and other relationships — so demographic-matching logic gets tested against the cases that actually appear in production.

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.