Testing X12 837I NM1: The Fields Your System Actually Needs to Handle
An 837P claim usually needs one physician's name on it. An 837I claim for a surgical inpatient stay can legitimately need three — the facility billing the claim, the attending physician who's responsible for the patient, and the operating physician who performed the procedure — and all three ride on the exact same NM1 segment structure, distinguished only by the entity code in NM101.
NM1 (Individual or Organizational Name) on an X12 837I institutional claim carries the name and identifying number of a claim party, repeated once per loop. Where an 837P mostly uses it for the billing provider and subscriber, an 837I claim also relies on it to identify the attending physician and, when applicable, the operating physician tied to the facility stay.
The elements that actually matter in practice
Example
A synthetic attending physician occurrence: entity code 71 for attending physician, entity type 1 for a person, qualifier XX identifying the ID that follows as an NPI. Synthetic claim data.
Where this trips people up
Teams that build their 837I test data by copying an 837P NM1 loop structure frequently forget the attending physician loop entirely, since a professional claim never carries one. The claim passes basic syntax checks and gets submitted, then comes back rejected because most payers treat the attending physician as required on facility claims, not optional. The second common miss is dropping the operating physician's NM1 loop on a surgical claim while keeping the attending — the two roles are easy to conflate when a synthetic dataset only ever populates one physician per test case.