Reference·NM1 Segment·NM101
X12 275 Reference

X12 275 NM101 (Entity Identifier Code): Format, Values, and Testing Notes

Jul 28, 2026 · 4 min read
NM103 →

NM101 is only two characters, but it's the code that tells the receiving system whose name it's about to read. In a 275 built around the patient, get this wrong and the identity check downstream is comparing the wrong record entirely.

Quick answer

NM101 is the first element of the NM1 segment — a code that identifies which party this occurrence of NM1 describes. In a 275 attachment transaction, the value QC marks the occurrence as representing the patient whose records are attached.

Valid code values

QC
Patient — the standard value used to identify the patient in a 275 NM1 occurrence
1P
Provider — used when a separate NM1 occurrence identifies the provider submitting or requesting the attachment

Example

Synthetic example Generated by Synthibase
NM1*QC*1*OYELARAN*BAYO****MI*WT205819443*

A synthetic NM1 using entity code QC to mark this occurrence as the patient, Bayo Oyelaran. Synthetic data only.

Where this trips people up

Test data generated by copying an NM1 example from a different transaction type sometimes leaves a provider or payer entity code in place instead of QC, since the segment structure looks identical either way. The file still validates syntactically, but any downstream logic that filters specifically for the patient occurrence never finds one, and the attachment ends up with no confirmed patient identity attached to it at all.

X12 275 NM1 Explained: Structure, Fields, and Common Mistakes
How to Write EDI Test Cases That Actually Catch Go-Live Failures
How to Validate X12 EDI Files Before Payer Submission
Generate correctly coded patient identities every time
Synthibase generates synthetic 275 NM1 segments with the correct patient entity code applied consistently, so identity-matching logic is tested against realistic data instead of copy-pasted placeholders.
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.