A party hierarchy describes which person or organization a response context refers to. HL supplies a hierarchical level and an optional parent identifier. NM1 identifies the party associated with that level.
HL parent-child relationships
The single-benefit response contains three levels:
text
HL*1**20*1~
HL*2*1*21*1~
HL*3*2*22*0~HL01numbers each level:1,2, and3.HL02identifies the parent. It is empty at the top level, then contains1and2in the following segments.HL03identifies the kind of level. The values shown are information source (20), information receiver (21), and subscriber (22).HL04indicates whether the level has children. The subscriber level uses0because it has no child level in this example.
For field details, see the HL fields.
NM1 party identification
An NM1 segment identifies the party at the current level:
text
NM1*PR*2*CEDAR VALLEY HEALTH PLAN*****PI*99001~
NM1*1P*2*OAK STREET MEDICAL GROUP*****XX*1234567810~
NM1*IL*1*REED*JORDAN~NM101identifies the party's role: payer (PR), provider (1P), or insured or subscriber (IL) in these examples.NM102=2identifies the payer and provider as organizations.NM102=1identifies the subscriber as a person.NM103contains an organization name or a person's family name.NM104contains the person's given name when present.NM108contains the identifier type andNM109contains the identifier. The 005010X279A1 implementation guide (X279A1) requires both for the information source (loop2100A) and the information receiver (loop2100B). HerePImarks a payer identifier andXXmarks a National Provider Identifier. Both values were written for this guide. The subscriberNM1(loop2100C) leaves them out. X279A1 doesn't require them there.
For field details, see the NM1 fields.
The sequence shows one hierarchy. Read HL and NM1 together with the transaction profile and companion guide to determine which relationships and identity rules apply to your route.