Reference·IN1 Segment·IN1-36
HL7 v2 Reference

Testing HL7 v2 IN1-36: What Policy Number Actually Needs to Handle

Jul 27, 2026 · 4 min read
← IN1-17

Policy number sits so far down the IN1 segment that some sending systems truncate their messages before ever reaching it — and your parser needs to handle that gracefully.

Quick answer

IN1-36 is a free-text (ST) field holding the subscriber's policy number — the identifier the payer uses to look up the individual coverage record, as distinct from the group-level identifier in IN1-8.

What this field contains

Data type
ST (String) — unformatted text; length and character set vary entirely by payer
Position
Last field on IN1 — being field 36 of 36, it is the first thing dropped when a sending system truncates trailing empty fields incorrectly
Common pitfall
Confused with group number — both IN1-8 and IN1-36 are free-text identifiers with no distinguishing format

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-36, the final field on the segment, carries policy number POL-77213840.

Where this trips people up

Because IN1-36 is the very last field on the segment, some sending systems truncate the message right after the last populated field rather than padding out to field 36 with empty placeholders — which is valid HL7 but breaks naive parsers that expect a fixed field count. A parser that indexes fields by position instead of counting delimiters will read a truncated segment and either throw an error or silently return an empty policy number, and test suites built only against fully-padded examples won't catch it.

HL7 v2 IN1 Segment Guide: Fields, Format, and Testing Gotchas
How to Write EDI Test Cases That Actually Catch Go-Live Failures
How to Reduce Claim Denials Through Better Pre-Submission Testing
Test truncated segments, not just fully-padded examples
Synthibase generates HL7 messages with realistic trailing-field truncation alongside fully-populated segments, so your parser is proven against both before a real feed catches it out.
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.