Insurance Company ID is deceptively simple — until you hit a payer that supplies both a clearinghouse ID and an internal system ID in the same repeating field.
Quick answer
IN1-3 is a repeatable CX (Extended Composite ID) field that identifies the insurance company or payer organization for this coverage record, as opposed to IN1-2 which identifies the specific plan the patient is enrolled in.
What this field contains
Component 1
ID number — the payer's identifier, e.g. 66214 — often a clearinghouse or NAIC-style code
Component 4-6
Assigning authority — optionally names the system or authority that issued the ID; commonly left blank in practice
Repetition
Multiple values — the field can repeat when a payer is known under more than one identifier system
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-3 holds the bare identifier 66214 for the payer organization, with no assigning-authority components populated.
Where this trips people up
Because IN1-3 can legally repeat (separated by the repetition delimiter), a parser built and tested only against single-value input will silently take the first repetition and drop the rest when a real feed sends both a clearinghouse ID and an internal payer ID together. That data loss is invisible in a UI that only ever displays one ID field, so it tends to surface as a mismatch during claims submission rather than during testing.
Test repeating fields the way real payer feeds actually use them
Synthibase can generate IN1-3 values with realistic repetitions and assigning-authority variations, exposing parsing gaps before they cost you a rejected claim.
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.