Reference·IN1 Segment·IN1-1
HL7 v2 Reference

HL7 v2 IN1-1 (Set ID): Format, Values, and Testing Notes

Jul 27, 2026 · 4 min read
IN1-2 →

One IN1 segment tests fine every time — it's the second and third one, sequenced with IN1-1, where coordination-of-benefits logic actually gets exercised.

Quick answer

IN1-1 is a simple incrementing integer that numbers each IN1 segment when a message carries coverage for more than one payer. The first occurrence is 1, the second is 2, and so on — receiving systems typically use this sequence, combined with IN1-21 through IN1-23, to determine primary versus secondary coverage.

What this field contains

Data type
SI (Sequence ID) — a positive integer with no leading zeros or decorative formatting
1
First occurrence — conventionally the primary payer, though primacy is technically driven by IN1-22, not by IN1-1 order alone
2, 3…
Subsequent occurrences — secondary and tertiary coverage; each needs its own complete IN1 segment

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-1 is set to 1, marking this as the first (typically primary) insurance segment in the message.

Where this trips people up

Test generators love producing exactly one IN1 segment per message because it's the simplest valid case. That means the code path for parsing a second or third IN1 segment — and correctly attaching it to the same patient — often ships untested. When a real message arrives with three payers because a patient has Medicare, a supplemental plan, and a workers' comp claim, that's the first time the multi-segment loop actually runs.

HL7 v2 IN1 Segment Guide: Fields, Format, and Testing Gotchas
COB Claims Testing: How to Generate Coordination of Benefits Scenarios
HL7 ADT Messages: A01 through A08 Explained
Test multi-payer scenarios, not just the single-IN1 happy path
Synthibase can generate messages with two or three stacked IN1 segments and realistic coordination-of-benefits ordering, so your parser is actually exercised on the cases that break 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.