Reference·IN2 Segment·IN2-6
HL7 v2 Reference

Testing HL7 v2 IN2-6: What Employer Information Data Actually Needs to Handle

Jul 27, 2026 · 4 min read
← IN2-4

IN2-6 is a small coded field, so it's easy to assume it barely matters - until a leave-of-absence code is the one signal that should have flagged a coverage lapse before a claim went out.

Quick answer

IN2-6 carries a coded value summarizing the insured's employment status with the employer named in IN2-4 - commonly something like full-time, part-time, or on leave. Receiving systems that care about coverage continuity sometimes use this code as a quick signal for whether group eligibility might be at risk.

What this field contains

Data type
IS (Coded value for user-defined tables) — a short coded token drawn from a site- or implementation-defined table
FT
Full-time — the most commonly populated value in synthetic and real test data alike
PT / LOA
Part-time / leave of absence — far less common in test data, but exactly where coverage-risk logic needs exercising

Example

Synthetic example Generated by Synthibase
IN2|EMP-22910|000-45-6789||ACME MANUFACTURING CO||FT

IN2-6 is set to FT, indicating the insured is a full-time employee of Acme Manufacturing Co at the time this message was generated.

Where this trips people up

Because full-time is the overwhelmingly common real-world value, test data sets tend to hardcode IN2-6 to FT across every record. That means any logic built to react to a part-time or leave-of-absence code - flagging a policy for review, adjusting eligibility windows - sits untested until an actual leave-of-absence case shows up in production and the code path runs for the first time against real data.

HL7 v2 IN2 Explained: Structure, Fields, and Common Mistakes
COB Claims Testing: How to Generate Coordination of Benefits Scenarios
How to Write EDI Test Cases That Actually Catch Go-Live Failures
Exercise every employment-status code, not just full-time
Synthibase varies IN2-6 across full-time, part-time, and leave-of-absence values in generated messages, so coverage-risk logic tied to employment status actually gets tested before it meets production data.
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.