HL7 v2 Reference

What Is HL7 v2 IN1-4? Insurance Company Name, Explained for Testers

Jul 27, 2026 · 4 min read

Insurance Company Name seems like the easiest field on the segment to validate — right up until you're matching "Acme Regional" against "ACME REGIONAL HEALTH PLAN INC" from a different feed.

Quick answer

IN1-4 is an XON (Extended Composite Name and ID for Organizations) field holding the payer's organization name for this coverage. It's typically the field displayed to end users, even though IN1-2 and IN1-3 are what downstream systems actually key matching logic off.

What this field contains

Component 1

Organization name — the free-text payer name, e.g. Acme Regional Health Plan — no standardized casing or abbreviation rules enforced

Component 10

Organization ID — an optional identifier component that duplicates information already carried in IN1-3

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-4 supplies the plain organization name Acme Regional Health Plan, with no additional XON components populated.

Where this trips people up

Because IN1-4 is free text with no standard code table behind it, the same payer shows up spelled, capitalized, and abbreviated differently across sending systems. Test suites built with a single canonical spelling never catch the fuzzy-matching or normalization logic failing on a variant like "ACME RGNL HLTH PLAN" — which is exactly the kind of input that shows up once real interfaces go live.

→

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

→

How to Reduce Claim Denials Through Better Pre-Submission Testing

→

How to Build a Synthetic Patient Registry for Healthcare Testing

Test against realistic payer-name variation, not one clean spelling

Synthibase varies payer name formatting across generated messages the way real-world feeds do, so normalization and matching logic gets tested against messy input before production does it for you.

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.