837 Transaction Set Listing

008020X325 Health Care Claim: Dental
Usage
Repeats

ISA - INTERCHANGE CONTROL HEADER

X12 Name:
Interchange Control Header
X12 Purpose:
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
  1. For compliant implementations under this implementation guide, ISA13, the Interchange Control Number, must be a positive unsigned number. Therefore, the ISA segment can be considered a fixed record length segment.
  2. The first element separator defines the element separator to be used through the entire interchange.
  3. Spaces in the example interchanges are represented by "." for clarity.
  4. The ISA segment terminator defines the segment terminator used throughout the entire interchange.
  5. All positions within each of the data elements must be filled.
TR3 Example:
ISA✱00✱..........✱01✱SECRET....✱ZZ✱SENDERS.ID.....✱ZZ✱RECEIVERS.ID...✱030101✱1253✱^✱00802✱000000905✱0✱T✱:~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
I01
Authorization Information Qualifier
M 1
ID
2
Code identifying the type of information in the Authorization Information
CODE
DEFINITION
00
No Authorization Information Present (No Meaningful Information in I02)
03
Additional Data Identification
Required
2
I02
Authorization Information
M 1
AN
10
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
This element is fixed in length with identical minimum and maximum lengths. Spaces are inserted to meet the minimum length in an AN data element. With the associated code 00 in ISA01 or ISA03, an all space value indicates no information.
Required
3
I03
Security Information Qualifier
M 1
ID
2
Code identifying the type of information in the Security Information
CODE
DEFINITION
00
No Security Information Present (No Meaningful Information in I04)
01
Password
Required
4
I04
Security Information
M 1
AN
10
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
This element is fixed in length with identical minimum and maximum lengths. Spaces are inserted to meet the minimum length in an AN data element. With the associated code 00 in ISA01 or ISA03, an all space value indicates no information.
Required
5
I05
Interchange ID Qualifier
M 1
ID
2
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
This ID qualifies the Sender in ISA06.
CODE
DEFINITION
01
Duns (Dun & Bradstreet)
14
Duns Plus Suffix
20
Health Industry Number (HIN)
CODE SOURCE: 121: Health Industry Number
27
Carrier Identification Number as assigned by Centers for Medicare & Medicaid Services (CMS)
28
Fiscal Intermediary Identification Number as assigned by Centers for Medicare & Medicaid Services (CMS)
29
Medicare Provider and Supplier Identification Number as assigned by Centers for Medicare & Medicaid Services (CMS)
30
U.S. Federal Tax Identification Number
33
National Association of Insurance Commissioners Company Code (NAIC)
ZZ
Mutually Defined
Required
6
I06
Interchange Sender ID
M 1
AN
15
Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Required
7
I05
Interchange ID Qualifier
M 1
ID
2
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
This ID qualifies the Receiver in ISA08.
CODE
DEFINITION
01
Duns (Dun & Bradstreet)
14
Duns Plus Suffix
20
Health Industry Number (HIN)
CODE SOURCE: 121: Health Industry Number
27
Carrier Identification Number as assigned by Centers for Medicare & Medicaid Services (CMS)
28
Fiscal Intermediary Identification Number as assigned by Centers for Medicare & Medicaid Services (CMS)
29
Medicare Provider and Supplier Identification Number as assigned by Centers for Medicare & Medicaid Services (CMS)
30
U.S. Federal Tax Identification Number
33
National Association of Insurance Commissioners Company Code (NAIC)
ZZ
Mutually Defined
Required
8
I07
Interchange Receiver ID
M 1
AN
15
Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them
Required
9
I08
Interchange Date
M 1
DT
6
Date of the interchange
The date format is YYMMDD.
Required
10
I09
Interchange Time
M 1
TM
4
Time of the interchange
The time format is HHMM.
Required
11
I65
Repetition Separator
M 1
Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator
Required
12
I11
Interchange Control Version Number Code
M 1
ID
5
Code specifying the version number of the interchange control segments, the version of the data elements within the control segments, and the code values within those data elements.
INDUSTRY NAME: Interchange Control Version Number
CODE
DEFINITION
00802
00802 Standards Approved for Publication by ASC X12 Procedures Review Board through December 2020
Required
13
I12
Interchange Control Number
M 1
N
9
A control number assigned by the interchange sender
  1. The Interchange Control Number, ISA13, must be identical to the associated Interchange Trailer IEA02.
  2. Must be a positive unsigned number and must be identical to the value in IEA02.
Required
14
I13
Acknowledgment Requested Code
M 1
ID
1
Code indicating sender's request for an interchange acknowledgment
INDUSTRY NAME: Acknowledgment Requested
X12.5 - Interchange Control Structure, provides the purpose of the TA1 segment. The X12 Acknowledgment Reference Model provides considerable information about the TA1 segment.
CODE
DEFINITION
0
No Interchange Acknowledgment Requested
Use when the interchange contains ONLY acknowledgment Functional Groups (e.g. 999 or 824) or a TA1.
1
Interchange Acknowledgment Requested (TA1)
Use when batch process requires the return of a TA1 for the interchange.
2
Interchange Acknowledgment Requested only when Interchange is "Rejected Because Of Errors"
Use when the transaction is for real-time processing.
3
Interchange Acknowledgment Requested only when Interchange is "Rejected Because Of Errors" or "Accepted but Errors are Noted"
Use when batch processing requires the return of a TA1 for the interchange only when errors are noted.
Required
15
I14
Interchange Usage Indicator Code
M 1
ID
1
Code indicating whether data enclosed by this interchange envelope is test, production or information
INDUSTRY NAME: Interchange Usage Indicator
CODE
DEFINITION
I
Information
Use when the interchange contains ONLY a TA1.
P
Production Data
T
Test Data
Required
16
I15
Component Element Separator
M 1
Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

GS*HC - FUNCTIONAL GROUP HEADER

X12 Name:
Functional Group Header
X12 Purpose:
To indicate the beginning of a functional group and to provide control information
X12 Comments:
A functional group of related transaction sets, within the scope of X12 standards, consists of a collection of similar transaction sets enclosed by a functional group header and a functional group trailer.
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
GS✱XX✱SENDER CODE✱RECEIVER CODE✱19991231✱0802✱1✱X✱008020X325~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
479
Functional Identifier Code
M 1
ID
2
Code identifying a group of application related transaction sets
This is the 2-character Functional Identifier Code assigned to each transaction set by X12. The specific code for a transaction set defined by this implementation guide is presented in Section 1.2, Version Information.
CODE
DEFINITION
HC
Health Care Claim (837)
Required
2
142
Application Sender's Code
M 1
AN
2/15
Code identifying party sending transmission; codes agreed to by trading partners
Use this code to identify the unit sending the information.
Required
3
124
Application Receiver's Code
M 1
AN
2/15
Code identifying party receiving transmission; codes agreed to by trading partners
Use this code to identify the unit receiving the information.
Required
4
373
Date
M 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: GS04 is the group date.
Use this date for the functional group creation date.
Required
5
337
Time
M 1
TM
4/8
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
SEMANTIC: GS05 is the group time.
Use this time for the creation time. The recommended format is HHMM.
Required
6
28
Group Control Number
M 1
N
1/9
Assigned number originated and maintained by the sender
SEMANTIC: The data interchange control number GS06 in this header must be identical to the same data element in the associated functional group trailer, GE02.
For implementations compliant with this guide, GS06 must be unique within a single transmission (that is, within a single ISA to IEA enveloping structure). The authors recommend that GS06 be unique within all transmissions over a period of time to be determined by the sender.
Required
7
455
Responsible Agency Code
M 1
ID
1/2
Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480
CODE
DEFINITION
X
Accredited Standards Committee X12
Required
8
480
Version / Release / Industry Identifier Code
M 1
AN
1/12
Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed
INDUSTRY NAME: Version, Release, or Industry Identifier Code
This is the unique Version/Release/Industry Identifier Code assigned to an implementation by X12N. The specific code for a transaction set defined by this implementation guide is presented in Section 1.2, Version Information.
CODE SOURCE 881: Version / Release / Industry Identifier Code
CODE
DEFINITION
008020X325
Health Care Claim: Dental

ST*837 - TRANSACTION SET HEADER

X12 Name:
Transaction Set Header
X12 Purpose:
To indicate the start of a transaction set and to assign a control number
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
ST✱837✱0002✱008020X325~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
143
Transaction Set Identifier Code
M 1
ID
3
Code identifying a Transaction Set
SEMANTIC: The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
CODE
DEFINITION
837
Health Care Claim
Required
2
329
Transaction Set Control Number
M 1
AN
4/9
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
The Transaction Set Control Numbers in ST02 and SE02 must be identical and must be a numeric value. The number (i.e. numeric value) is assigned by the originator and must be unique within a functional group (GS-GE). For example, start with the numeric value 0001 and increment from there. The Transaction Set Control Number also aids in error resolution research.
Required
3
1705
Implementation Convention Reference
O 1
AN
1/35
Reference assigned to identify Implementation Convention
SEMANTIC: The implementation convention reference (ST03) is used by the translation routines of the interchange partners to select the appropriate implementation convention to match the transaction set definition. When used, this implementation convention reference takes precedence over the implementation reference specified in the GS08.
INDUSTRY NAME: Implementation Guide Version Name
  1. This element must be populated with the guide identifier named in Section 1.2.
  2. This field contains the same value as GS08. Some translator products strip off the ISA and GS segments prior to application (ST-SE) processing. Providing the information from the GS08 at this level will ensure that the appropriate application mapping is used at translation time.
CODE
DEFINITION
008020X325
Health Care Claim: Dental

BHT*0019 - BEGINNING OF HIERARCHICAL TRANSACTION

X12 Name:
Beginning of Hierarchical Transaction
X12 Purpose:
To define the business hierarchical structure of the transaction set and identify the business application purpose and reference data, i.e., number, date, and time
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
The second example denotes the case where the entire transaction set contains ENCOUNTERS.
TR3 Example:
  1. BHT✱0019✱00✱0123✱20220618✱0932✱CH~
  2. BHT✱0019✱00✱44445✱20220213✱0345✱RP~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1005
Hierarchical Structure Code
M 1
ID
4
Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set
Used to specify the sequential order of HL segments. The HL loops in the data stream must comply with this sequential order. An HL parent loop must be followed by any subordinate child loops prior to commencing a new HL parent loop at the same hierarchical level.
CODE
DEFINITION
0019
Information Source, Subscriber, Dependent
Required
2
353
Transaction Set Purpose Code
M 1
ID
2
Code identifying purpose of transaction set
BHT02 is intended to convey the electronic transmission status of the 837 batch contained in this ST-SE envelope. The terms "original" and "reissue" refer to the electronic transmission status of the 837 batch, not the billing status.
CODE
DEFINITION
00
Original
Use when the transmission has never been sent to the receiver.
18
Reissue
Use when the sender needs to indicate the transmission has been previously sent.
Required
3
127
Reference Identification
O 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: BHT03 is the number assigned by the originator to identify the transaction within the originator's business application system.
INDUSTRY NAME: Originator Application Transaction Identifier
  1. The inventory file number of the transmission assigned by the submitter's system. This number operates as a batch control number.
  2. Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Required
4
373
Date
O 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: BHT04 is the date the transaction was created within the business application system.
INDUSTRY NAME: Transaction Set Creation Date
Required
5
337
Time
O 1
TM
4/8
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
SEMANTIC: BHT05 is the time the transaction was created within the business application system.
INDUSTRY NAME: Transaction Set Creation Time
Required
6
640
Transaction Type Code
O 1
ID
2
Code specifying the type of transaction
INDUSTRY NAME: Claim or Encounter Identifier
CODE
DEFINITION
31
Subrogation Demand
Use when willing trading partners agree to perform post payment claim recovery through the submission of subrogation claims.
NOTE: At the time of this writing, Subrogation Demand is not a HIPAA mandated use of the 837 transaction.
CH
Chargeable
Use when the transaction contains only fee for service claims or claims with at least one chargeable line item. If it is not clear whether a transaction contains claims or capitated encounters, or if the transaction contains a mix of claims and capitated encounters, use CH.
RP
Reporting
Use when the entire ST-SE envelope contains only capitated encounters and the transaction is being sent to an entity for purposes other than adjudication of a claim.

NM1*41 - SUBMITTER NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Loop 1000 contains submitter and receiver information. If any intermediary receivers change or add data in any way, then they add an occurrence to the loop as a form of identification. The added loop occurrence must be the last occurrence of the loop.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
The submitter is the entity responsible for the creation and formatting of this transaction.
TR3 Example:
NM1✱41✱2✱ABC SUBMITTER✱✱✱✱✱46✱999999999~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
41
Submitter
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
2
Non-Person Entity
Required
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Submitter Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Submitter First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when NM102 = 1 (person) and the Middle Name or Initial is known to the sender. If not required by this implementation guide, do not send.
INDUSTRY NAME: Submitter Middle Name or Initial
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Not Used
7
1039
Name Suffix
O 1
AN
1/10
Required
8
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
CODE
DEFINITION
46
Electronic Transmitter Identification Number (ETIN)
Required
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
INDUSTRY NAME: Submitter Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

PER*IC - SUBMITTER EDI CONTACT INFORMATION

X12 Name:
Administrative Communications Contact
X12 Purpose:
To identify a person or office to whom administrative communications should be directed
X12 Syntax:
  1. P0304
    If either PER03 or PER04 is present, then the other is required.
  2. P0506
    If either PER05 or PER06 is present, then the other is required.
  3. P0708
    If either PER07 or PER08 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
2
TR3 Notes:
  1. When the communication number represents a telephone number in the United States and other countries using the North American Dialing Plan (for voice, data, fax, etc.), the communication number must always include the area code and phone number using the format AAABBBCCCC where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number. Therefore, the following telephone number (555) 555-1234 would be represented as 5555551234. Do not submit long distance access numbers, such as 1, in the telephone number. Telephone extensions, when applicable, must be submitted in the next element immediately following the telephone number. When submitting telephone extensions, only submit the numeric extension, do not include data that indicates an extension, such as "ext" or "x-".
  2. The contact information in this segment identifies the person in the submitter organization who deals with data transmission issues. If data transmission problems arise, this is the person to contact in the submitter organization.
  3. There are 2 repetitions of the PER segment to allow for six possible communication numbers including extensions.
TR3 Example:
PER✱IC✱JOHN SMITH✱TE✱5555551234✱EX✱123~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
366
Contact Function Code
M 1
ID
2
Code identifying the major duty or responsibility of the person or group named
CODE
DEFINITION
IC
Information Contact
Situational
2
93
Name
O 1
AN
1/60
Free-form name
SITUATIONAL RULE: Required when the contact name is different than the name contained in the Submitter Name (NM1) segment of this loopANDit is the first iteration of the Submitter EDI Contact Information (PER) segment.If not required by this implementation guide, do not send.
INDUSTRY NAME: Submitter Contact Name
Required
3
365
Communication Number Qualifier
X 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0304
CODE
DEFINITION
EM
Electronic Mail
FX
Facsimile
TE
Telephone
Required
4
364
Communication Number
X 1
AN
1/2048
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0304
The maximum number of characters to be supported for this field is 256.
Situational
5
365
Communication Number Qualifier
X 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when this information is deemed necessary by the submitter. If not required by this implementation guide, do not send.
CODE
DEFINITION
EM
Electronic Mail
EX
Telephone Extension
FX
Facsimile
TE
Telephone
Situational
6
364
Communication Number
X 1
AN
1/2048
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when this information is deemed necessary by the submitter. If not required by this implementation guide, do not send.
The maximum number of characters to be supported for this field is 256.
Situational
7
365
Communication Number Qualifier
X 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when this information is deemed necessary by the submitter. If not required by this implementation guide, do not send.
CODE
DEFINITION
EM
Electronic Mail
EX
Telephone Extension
FX
Facsimile
TE
Telephone
Situational
8
364
Communication Number
X 1
AN
1/2048
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when this information is deemed necessary by the submitter. If not required by this implementation guide, do not send.
The maximum number of characters to be supported for this field is 256.
Not Used
9
443
Contact Inquiry Reference
O 1
AN
1/20

NM1*40 - RECEIVER NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Loop 1000 contains submitter and receiver information. If any intermediary receivers change or add data in any way, then they add an occurrence to the loop as a form of identification. The added loop occurrence must be the last occurrence of the loop.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
NM1✱40✱2✱XYZ RECEIVER✱✱✱✱✱46✱111222333~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
40
Receiver
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
2
Non-Person Entity
Required
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Receiver Name
Not Used
4
1036
Name First
O 1
AN
1/35
Not Used
5
1037
Name Middle
O 1
AN
1/25
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Not Used
7
1039
Name Suffix
O 1
AN
1/10
Required
8
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
CODE
DEFINITION
46
Electronic Transmitter Identification Number (ETIN)
Required
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
INDUSTRY NAME: Receiver Primary Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

HL - BILLING PROVIDER LEVEL

X12 Name:
Hierarchical Level
X12 Purpose:
To identify dependencies among and the content of hierarchically related groups of data segments
X12 Comments:
  1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
  2. The HL segment defines a top-down/left-right ordered structure.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
HL✱1✱✱20✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
628
Hierarchical ID Number
M 1
AN
1/12
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
COMMENT: HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
The first HL01 within each ST-SE envelope must begin with "1", and be incremented by one each time an HL is used in the transaction. Only numeric values are allowed in HL01.
Not Used
2
734
Hierarchical Parent ID Number
O 1
AN
1/12
Required
3
735
Hierarchical Level Code
M 1
ID
1/2
Code specifying the characteristic of a level in a hierarchical structure
COMMENT: HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
CODE
DEFINITION
20
Information Source
Required
4
736
Hierarchical Child Code
O 1
ID
1
Code indicating if there are hierarchical child data segments subordinate to the level being described
COMMENT: HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
CODE
DEFINITION
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.

PRV*BI - BILLING PROVIDER SPECIALTY INFORMATION

X12 Name:
Provider Information
X12 Purpose:
To specify the identifying characteristics of a provider
X12 Syntax:
P0203
If either PRV02 or PRV03 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the Billing Provider is also the Rendering Provider for at least one of the claims in this transaction.
If not required by this implementation guide, do not send.
TR3 Example:
PRV✱BI✱PXC✱1223G0001X~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1221
Provider Code
M 1
ID
1/3
Code identifying the type of provider
CODE
DEFINITION
BI
Billing
Required
2
128
Reference Identification Qualifier
X 1
ID
2/3
Code identifying the Reference Identification
SEGMENT SYNTAX: P0203
CODE
DEFINITION
PXC
Health Care Provider Taxonomy Code
CODE SOURCE: 682: Health Care Provider Taxonomy
Required
3
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: P0203
INDUSTRY NAME: Provider Taxonomy Code
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
4
156
State or Province Code
O 1
ID
2
Not Used
5
C035
Provider Specialty Information
O 1
Not Used
6
1223
Provider Organization Code
O 1
ID
3

CUR*85 - FOREIGN CURRENCY INFORMATION

X12 Name:
Currency
X12 Purpose:
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
X12 Syntax:
  1. C0807
    If CUR08 is present, then CUR07 is required.
  2. C0907
    If CUR09 is present, then CUR07 is required.
  3. L101112
    If CUR10 is present, then at least one of CUR11 or CUR12 are required.
  4. C1110
    If CUR11 is present, then CUR10 is required.
  5. C1210
    If CUR12 is present, then CUR10 is required.
  6. L131415
    If CUR13 is present, then at least one of CUR14 or CUR15 are required.
  7. C1413
    If CUR14 is present, then CUR13 is required.
  8. C1513
    If CUR15 is present, then CUR13 is required.
  9. L161718
    If CUR16 is present, then at least one of CUR17 or CUR18 are required.
  10. C1716
    If CUR17 is present, then CUR16 is required.
  11. C1816
    If CUR18 is present, then CUR16 is required.
  12. L192021
    If CUR19 is present, then at least one of CUR20 or CUR21 are required.
  13. C2019
    If CUR20 is present, then CUR19 is required.
  14. C2119
    If CUR21 is present, then CUR19 is required.
X12 Comments:
See Figures Appendix for examples detailing the use of the CUR segment.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the amounts represented in this transaction are currencies other than the United States dollar. If not required by this implementation guide, do not send.
TR3 Notes:
It is REQUIRED that all amounts reported within the transaction are of the currency named in this segment. If this segment is not used, then it is required that all amounts in this transaction be expressed in US dollars.
TR3 Example:
CUR✱85✱CAD~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
85
Billing Provider
Required
2
100
Currency Code
M 1
ID
3
Code specifying the Standard ISO code for country in whose currency the charges are specified
The submitter must use the Currency Code, not the Country Code, for this element. For example the Currency Code CAD = Canadian dollars would be valid, while CA = Canada would be invalid.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
3
280
Exchange Rate
O 1
R
4/10
Not Used
4
98
Entity Identifier Code
O 1
ID
2/3
Not Used
5
100
Currency Code
O 1
ID
3
Not Used
6
669
Currency Market/Exchange Code
O 1
ID
3
Not Used
7
374
Date/Time Qualifier
X 1
ID
3
Not Used
8
373
Date
O 1
DT
8
Not Used
9
337
Time
O 1
TM
4/8
Not Used
10
374
Date/Time Qualifier
X 1
ID
3
Not Used
11
373
Date
X 1
DT
8
Not Used
12
337
Time
X 1
TM
4/8
Not Used
13
374
Date/Time Qualifier
X 1
ID
3
Not Used
14
373
Date
X 1
DT
8
Not Used
15
337
Time
X 1
TM
4/8
Not Used
16
374
Date/Time Qualifier
X 1
ID
3
Not Used
17
373
Date
X 1
DT
8
Not Used
18
337
Time
X 1
TM
4/8
Not Used
19
374
Date/Time Qualifier
X 1
ID
3
Not Used
20
373
Date
X 1
DT
8
Not Used
21
337
Time
X 1
TM
4/8

NM1*85 - BILLING PROVIDER NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Loop 2010 contains information about entities that apply to all claims in loop 2300. For example, these entities may include billing provider, pay-to provider address, insurer, primary administrator, contract holder, pay-to plan, pay-to factoring agent, or claimant.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
  1. When the entity is not a Health Care provider (for example, personal care services, carpenters, etc.), the Billing Provider should be the legal entity. However, willing trading partners may agree upon varying definitions. Proprietary identifiers necessary for the receiver to identify the entity are to be reported in the Loop ID-2010BB REF, Billing Provider Secondary Identification segment.
  2. When the Billing Provider is an organization health care provider, the organization health care provider's NPI or its subpart's NPI is reported in NM109. When a health care provider organization has determined that it needs to enumerate its subparts, it will report the NPI of a subpart as the Billing Provider. The subpart reported as the Billing Provider MUST always represent the most detailed level of enumeration as determined by the organization health care provider and MUST be the same identifier sent to any trading partner. For additional explanation, see section 1.10.3 Organization Health Care Provider Subpart Presentation.
TR3 Example:
NM1✱85✱1✱SMITH✱JOHN✱B✱✱✱XX✱1234567890~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
85
Billing Provider
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
2
Non-Person Entity
Required
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Billing Provider Last or Organizational Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Billing Provider First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when NM102 = 1 (person) and the Middle Name or Initial is known to the sender. If not required by this implementation guide, do not send.
INDUSTRY NAME: Billing Provider Middle Name or Initial
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when NM102 = 1 (person) and the Suffix is known to the sender. If not required by this implementation guide do not send.
INDUSTRY NAME: Billing Provider Name Suffix
Situational
8
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when NM109 is used. If not required by this implementation guide, do not send.
CODE
DEFINITION
XX
Standard Unique Health Identifier for Health Care Providers (NPI)
CODE SOURCE: 537: National Provider Identifier (NPI)
Situational
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required for providers in the United States or its territories when the provider is eligible to receive a National Provider Identifier (NPI).ORRequired for providers not in the United States or its territories when the provider has received an NPI. If not required by this implementation guide, do not send.
INDUSTRY NAME: Billing Provider Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

N3 - BILLING PROVIDER ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
  1. Post Office Box or Lock Box addresses are to be sent in the Pay-To Address Loop (Loop ID-2010AB), if necessary.
  2. The Billing Provider Address must be a street address. If billing provider location is in an area where there are no street addresses, enter a description of the location (for example, "crossroad of State Road 34 and 45" or "Exit near Mile marker 265 on Interstate 80").
TR3 Example:
N3✱123 MAIN STREET~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Billing Provider Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when a second address line is needed. If not required by this implementation guide, do not send.
INDUSTRY NAME: Billing Provider Address Line

N4 - BILLING PROVIDER CITY, STATE, ZIP CODE

X12 Name:
Geographic Location
X12 Purpose:
To specify the geographic place of the named party
X12 Syntax:
  1. E0207
    Only one of N402 or N407 may be present.
  2. E0308
    Only one of N403 or N408 may be present.
  3. C0605
    If N406 is present, then N405 is required.
  4. C0704
    If N407 is present, then N404 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
N4✱KANSAS CITY✱MO✱641051909~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
INDUSTRY NAME: Billing Provider City Name
Situational
2
156
State or Province Code
X 1
ID
2
Code specifying the Standard State/Province as defined by appropriate government agency
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: Billing Provider State or Province Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
X 1
ID
3/15
Code specifying international postal zone code excluding punctuation and blanks (zip code for United States)
COMMENT: N403 contains the postal code in an unstructured format. N408 contains the postal code in a structured format. When a postal code data field is used, the parties shall agree as to which data element (N403 or N408) shall be used in the transaction set.
SEGMENT SYNTAX: E0308
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada, or when a postal code exists for the country in N404. If not required by this implementation guide, do not send.
INDUSTRY NAME: Billing Provider Postal Zone or ZIP Code
When reporting the ZIP code for U.S. addresses, the full nine digit ZIP code must be provided.
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
X 1
ID
2/3
Code identifying the country
SEGMENT SYNTAX: C0704
SITUATIONAL RULE: Required when the address is outside the United States of America. If not required by this implementation guide, do not send.
INDUSTRY NAME: Billing Provider Country Code
Use the alpha-2 country codes from Part 1 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
5
309
Location Qualifier
X 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
X 1
ID
1/3
Code identifying the country subdivision
SEGMENT SYNTAX: E0207, C0704
SITUATIONAL RULE: Required when the address is not in the United States of America, including its territories, or Canada, and the country in N404 has administrative subdivisions such as but not limited to states, provinces, cantons, etc. If not required by this implementation guide, do not send.
INDUSTRY NAME: Billing Provider Country Subdivision Code
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
8
1702
Postal Code-Formatted
X 1
AN
3/20

REF - BILLING PROVIDER TAX IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
This is the tax identification number (TIN) of the Billing Provider in 2010AA.
TR3 Example:
REF✱EI✱123456789~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
EI
Employer's Identification Number
Use when reporting the Employer's Identification Number (EIN).

The Employer's Identification Number must be a string of exactly nine numbers with no separators.

For example, "001122333" would be valid, while sending "001-12-2333" or "00-1122333" would be invalid.
SY
Social Security Number
Use when reporting a Social Security Number.

The Social Security Number must be a string of exactly nine numbers with no separators.

For example, sending "111002222" would be valid, while sending "111-00-2222" would be invalid.
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Billing Provider Tax Identification Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

PER*IC - BILLING PROVIDER CONTACT INFORMATION

X12 Name:
Administrative Communications Contact
X12 Purpose:
To identify a person or office to whom administrative communications should be directed
X12 Syntax:
  1. P0304
    If either PER03 or PER04 is present, then the other is required.
  2. P0506
    If either PER05 or PER06 is present, then the other is required.
  3. P0708
    If either PER07 or PER08 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
2
Situational Rule:
Required when this information is different than that contained in the Loop ID-1000A (Submitter) PER segment
AND
Loop ID-2010AC (Pay-to Plan) or Loop ID-2010AD (Pay-to Factoring Agent) is present. If not required by implementation guide, do not send.
TR3 Notes:
  1. When the communication number represents a telephone number in the United States and other countries using the North American Dialing Plan (for voice, data, fax, etc.), the communication number must always include the area code and phone number using the format AAABBBCCCC where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number. Therefore, the following telephone number (555) 555-1234 would be represented as 5555551234. Do not submit long distance access numbers, such as 1, in the telephone number. Telephone extensions, when applicable, must be submitted in the next element immediately following the telephone number. When submitting telephone extensions, only submit the numeric extension, do not include data that indicates an extension, such as "ext" or "x-".
  2. There are 2 repetitions of the PER segment to allow for six possible communication numbers including extensions.
TR3 Example:
PER✱IC✱JOHN SMITH✱TE✱5555551234✱EX✱123~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
366
Contact Function Code
M 1
ID
2
Code identifying the major duty or responsibility of the person or group named
CODE
DEFINITION
IC
Information Contact
Situational
2
93
Name
O 1
AN
1/60
Free-form name
SITUATIONAL RULE: Required in the first iteration of the Billing Provider Contact Information segment. If not required by this implementation guide, do not send.
INDUSTRY NAME: Billing Provider Contact Name
Required
3
365
Communication Number Qualifier
X 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0304
CODE
DEFINITION
EM
Electronic Mail
FX
Facsimile
TE
Telephone
Required
4
364
Communication Number
X 1
AN
1/2048
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0304
The maximum number of characters to be supported for this field is 256.
Situational
5
365
Communication Number Qualifier
X 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when this information is deemed necessary by the submitter. If not required by this implementation guide, do not send.
CODE
DEFINITION
EM
Electronic Mail
EX
Telephone Extension
FX
Facsimile
TE
Telephone
Situational
6
364
Communication Number
X 1
AN
1/2048
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when this information is deemed necessary by the submitter. If not required by this implementation guide, do not send.
The maximum number of characters to be supported for this field is 256.
Situational
7
365
Communication Number Qualifier
X 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when this information is deemed necessary by the submitter. If not required by this implementation guide, do not send.
CODE
DEFINITION
EM
Electronic Mail
EX
Telephone Extension
FX
Facsimile
TE
Telephone
Situational
8
364
Communication Number
X 1
AN
1/2048
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when this information is deemed necessary by the submitter. If not required by this implementation guide, do not send.
The maximum number of characters to be supported for this field is 256.
Not Used
9
443
Contact Inquiry Reference
O 1
AN
1/20

NM1*87 - PAY-TO ADDRESS

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Loop 2010 contains information about entities that apply to all claims in loop 2300. For example, these entities may include billing provider, pay-to provider address, insurer, primary administrator, contract holder, pay-to plan, pay-to factoring agent, or claimant.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when the address for payment is different than that of the Billing Provider. If not required by this implementation guide, do not send.
TR3 Notes:
Loop ID-2010AB only contains address information when different from the Billing Provider Address. There are no applicable identifiers for Pay-To Address information.
TR3 Example:
NM1✱87✱2~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
87
Pay-to Provider
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
2
Non-Person Entity
Not Used
3
1035
Name Last or Organization Name
X 1
AN
1/80
Not Used
4
1036
Name First
O 1
AN
1/35
Not Used
5
1037
Name Middle
O 1
AN
1/25
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Not Used
7
1039
Name Suffix
O 1
AN
1/10
Not Used
8
66
Identification Code Qualifier
X 1
ID
1/2
Not Used
9
67
Identification Code
X 1
AN
2/80
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

N3 - PAY-TO ADDRESS - ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
  1. N3✱1234 MAIN STREET✱FLOOR 5~
  2. N3✱PO BOX 123~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Pay-To Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when a second address line is needed. If not required by this implementation guide, do not send.
INDUSTRY NAME: Pay-To Address Line

N4 - PAY-TO ADDRESS CITY, STATE, ZIP CODE

X12 Name:
Geographic Location
X12 Purpose:
To specify the geographic place of the named party
X12 Syntax:
  1. E0207
    Only one of N402 or N407 may be present.
  2. E0308
    Only one of N403 or N408 may be present.
  3. C0605
    If N406 is present, then N405 is required.
  4. C0704
    If N407 is present, then N404 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
N4✱KANSAS CITY✱MO✱64108~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
INDUSTRY NAME: Pay-to Address City Name
Situational
2
156
State or Province Code
X 1
ID
2
Code specifying the Standard State/Province as defined by appropriate government agency
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: Pay-To Address State or Province Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
X 1
ID
3/15
Code specifying international postal zone code excluding punctuation and blanks (zip code for United States)
COMMENT: N403 contains the postal code in an unstructured format. N408 contains the postal code in a structured format. When a postal code data field is used, the parties shall agree as to which data element (N403 or N408) shall be used in the transaction set.
SEGMENT SYNTAX: E0308
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada, or when a postal code exists for the country in N404. If not required by this implementation guide, do not send.
INDUSTRY NAME: Pay-to Address Postal Zone or ZIP Code
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
X 1
ID
2/3
Code identifying the country
SEGMENT SYNTAX: C0704
SITUATIONAL RULE: Required when the address is outside the United States of America. If not required by this implementation guide, do not send.
INDUSTRY NAME: Pay-to Address Country Code
Use the alpha-2 country codes from Part 1 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
5
309
Location Qualifier
X 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
X 1
ID
1/3
Code identifying the country subdivision
SEGMENT SYNTAX: E0207, C0704
SITUATIONAL RULE: Required when the address is not in the United States of America, including its territories, or Canada, and the country in N404 has administrative subdivisions such as but not limited to states, provinces, cantons, etc. If not required by this implementation guide, do not send.
INDUSTRY NAME: Pay-to Address Country Subdivision Code
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
8
1702
Postal Code-Formatted
X 1
AN
3/20

NM1*PTP - PAY-TO PLAN NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Loop 2010 contains information about entities that apply to all claims in loop 2300. For example, these entities may include billing provider, pay-to provider address, insurer, primary administrator, contract holder, pay-to plan, pay-to factoring agent, or claimant.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when BHT06 = 31 (Subrogation Demand). If not required by this implementation guide, do not send.
TR3 Example:
NM1✱PTP✱2✱ABC PAY TO PLAN✱✱✱✱✱XV✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
PTP
Pay-to Plan Name
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
2
Non-Person Entity
Required
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Pay-To Plan Organizational Name
Not Used
4
1036
Name First
O 1
AN
1/35
Not Used
5
1037
Name Middle
O 1
AN
1/25
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Not Used
7
1039
Name Suffix
O 1
AN
1/10
Situational
8
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when NM109 is used. If not required by this implementation guide, do not send.
CODE
DEFINITION
XV
Standard Unique Health Plan Identifier (HPID)
CODE SOURCE: 540: Health Plan Identifier (HPID)
Situational
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when reporting the Health Plan ID (HPID) or Other Entity Identifier (OEID). If not required by this implementation guide, do not send.
INDUSTRY NAME: Pay-To Plan Primary Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

N3 - PAY-TO PLAN ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
N3✱123 MAIN STREET~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Pay-To Plan Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when a second address line is needed. If not required by this implementation guide, do not send.
INDUSTRY NAME: Pay-To Plan Address Line

N4 - PAY-TO PLAN CITY, STATE, ZIP CODE

X12 Name:
Geographic Location
X12 Purpose:
To specify the geographic place of the named party
X12 Syntax:
  1. E0207
    Only one of N402 or N407 may be present.
  2. E0308
    Only one of N403 or N408 may be present.
  3. C0605
    If N406 is present, then N405 is required.
  4. C0704
    If N407 is present, then N404 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
N4✱KANSAS CITY✱MO✱64108~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
INDUSTRY NAME: Pay-To Plan City Name
Situational
2
156
State or Province Code
X 1
ID
2
Code specifying the Standard State/Province as defined by appropriate government agency
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: Pay-To Plan State or Province Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
X 1
ID
3/15
Code specifying international postal zone code excluding punctuation and blanks (zip code for United States)
COMMENT: N403 contains the postal code in an unstructured format. N408 contains the postal code in a structured format. When a postal code data field is used, the parties shall agree as to which data element (N403 or N408) shall be used in the transaction set.
SEGMENT SYNTAX: E0308
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada, or when a postal code exists for the country in N404. If not required by this implementation guide, do not send.
INDUSTRY NAME: Pay-To Plan Postal Zone or ZIP Code
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
X 1
ID
2/3
Code identifying the country
SEGMENT SYNTAX: C0704
SITUATIONAL RULE: Required when the address is outside the United States of America. If not required by this implementation guide, do not send.
INDUSTRY NAME: Pay-to Plan Country Code
Use the alpha-2 country codes from Part 1 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
5
309
Location Qualifier
X 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
X 1
ID
1/3
Code identifying the country subdivision
SEGMENT SYNTAX: E0207, C0704
SITUATIONAL RULE: Required when the address is not in the United States of America, including its territories, or Canada, and the country in N404 has administrative subdivisions such as but not limited to states, provinces, cantons, etc. If not required by this implementation guide, do not send.
INDUSTRY NAME: Pay-to Plan Country Subdivision Code
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
8
1702
Postal Code-Formatted
X 1
AN
3/20

REF*2U - PAY-TO PLAN SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when NM109 of this loop is not used.
OR
Required when an additional identification number to that provided in the NM109 of this loop is necessary to identify the entity.
If not required by this implementation guide, do not send.
TR3 Example:
REF✱2U✱98765~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
2U
Payer Identification Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Pay-to Plan Secondary Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*EI - PAY-TO PLAN TAX IDENTIFICATION NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
REF✱EI✱123456789~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
EI
Employer's Identification Number
Use when reporting the Employer's Identification Number (EIN).

The Employer's Identification Number must be a string of exactly nine numbers with no separators.

For example, "001122333" would be valid, while sending "001-12-2333" or "00-1122333" would be invalid.
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Pay-To Plan Tax Identification Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

NM1*O4 - PAY-TO FACTORING AGENT NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Loop 2010 contains information about entities that apply to all claims in loop 2300. For example, these entities may include billing provider, pay-to provider address, insurer, primary administrator, contract holder, pay-to plan, pay-to factoring agent, or claimant.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when willing trading partners agree to use this implementation, and a Factoring Agent owns the rights to the financial obligation for this claim, and payment is intended to be made to this entity. If not required by this implementation guide, do not send.
TR3 Notes:
  1. This segment is not a HIPAA requirement as of this writing.
  2. This loop must not be used if the 2010AC Pay-to Plan loop is used.
TR3 Example:
NM1✱O4✱2✱XYZ AGENT✱✱✱✱✱XV✱1234567890~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
O4
Factor
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
2
Non-Person Entity
Required
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Pay-to Factoring Agent Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when NM102 = 1 (person) and the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Pay-to Factoring Agent First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when NM102 = 1 (person) and the middle name or initial of the person is needed to identify the individual. If not required by this implementation guide, do not send.
INDUSTRY NAME: Pay-to Factoring Agent Middle Name or Initial
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when NM102 = 1 (person) and the name suffix of the person is needed to identify the individual. If not required by this implementation guide, do not send.
INDUSTRY NAME: Pay-to Factoring Agent Name Suffix
Situational
8
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when NM109 is used. If not required by this implementation guide, do not send.
CODE
DEFINITION
XV
Standard Unique Health Plan Identifier (HPID)
CODE SOURCE: 540: Health Plan Identifier (HPID)
Situational
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when reporting the Health Plan ID (HPID) or Other Entity Identifier (OEID). If not required by this implementation guide, do not send.
INDUSTRY NAME: Pay-to Factoring Agent Primary Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

N3 - PAY-TO FACTORING AGENT ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
N3✱123 MAIN STREET~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Pay-to Factoring Agent Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when a second address line is needed. If not required by this implementation guide, do not send.
INDUSTRY NAME: Pay-to Factoring Agent Address Line

N4 - PAY-TO FACTORING AGENT CITY, STATE, ZIP CODE

X12 Name:
Geographic Location
X12 Purpose:
To specify the geographic place of the named party
X12 Syntax:
  1. E0207
    Only one of N402 or N407 may be present.
  2. E0308
    Only one of N403 or N408 may be present.
  3. C0605
    If N406 is present, then N405 is required.
  4. C0704
    If N407 is present, then N404 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
N4✱KANSAS CITY✱MO✱64108~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
INDUSTRY NAME: Pay-to Factoring Agent City Name
Situational
2
156
State or Province Code
X 1
ID
2
Code specifying the Standard State/Province as defined by appropriate government agency
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: Pay-to Factoring Agent State or Province Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
X 1
ID
3/15
Code specifying international postal zone code excluding punctuation and blanks (zip code for United States)
COMMENT: N403 contains the postal code in an unstructured format. N408 contains the postal code in a structured format. When a postal code data field is used, the parties shall agree as to which data element (N403 or N408) shall be used in the transaction set.
SEGMENT SYNTAX: E0308
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada, or when a postal code exists for the country in N404. If not required by this implementation guide, do not send.
INDUSTRY NAME: Pay-to Factoring Agent Postal Zone or ZIP Code
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
X 1
ID
2/3
Code identifying the country
SEGMENT SYNTAX: C0704
SITUATIONAL RULE: Required when the address is outside the United States of America. If not required by this implementation guide, do not send.
INDUSTRY NAME: Pay-to Factoring Agent Country Code
Use the alpha-2 country codes from Part 1 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
5
309
Location Qualifier
X 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
X 1
ID
1/3
Code identifying the country subdivision
SEGMENT SYNTAX: E0207, C0704
SITUATIONAL RULE: Required when the address is not in the United States of America, including its territories, or Canada, and the country in N404 has administrative subdivisions such as but not limited to states, provinces, cantons, etc. If not required by this implementation guide, do not send.
INDUSTRY NAME: Pay-to Factoring Agent Country Subdivision Code
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
8
1702
Postal Code-Formatted
X 1
AN
3/20

REF*2U - PAY-TO FACTORING AGENT SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when NM109 of this loop is not used.
OR
Required when an additional identification number to that provided in the NM109 of this loop is necessary to identify the entity.
If not required by this implementation guide, do not send.
TR3 Example:
REF✱2U✱251338~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
2U
Payer Identification Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Pay-to Factoring Agent Secondary Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF - PAY-TO FACTORING AGENT TAX IDENTIFICATION NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
REF✱EI✱123456789~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
EI
Employer's Identification Number
Use when reporting the Employer's Identification Number (EIN).

The Employer's Identification Number must be a string of exactly nine numbers with no separators.

For example, "001122333" would be valid, while sending "001-12-2333" or "00-1122333" would be invalid.
SY
Social Security Number
Use when reporting a Social Security Number.

The Social Security Number must be a string of exactly nine numbers with no separators.

For example, sending "111002222" would be valid, while sending "111-00-2222" would be invalid.
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Pay-to Factoring Agent Tax Identification Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

PER*IC - PAY-TO FACTORING AGENT CONTACT INFORMATION

X12 Name:
Administrative Communications Contact
X12 Purpose:
To identify a person or office to whom administrative communications should be directed
X12 Syntax:
  1. P0304
    If either PER03 or PER04 is present, then the other is required.
  2. P0506
    If either PER05 or PER06 is present, then the other is required.
  3. P0708
    If either PER07 or PER08 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
2
Situational Rule:
Required when this information is different than that contained in the Loop ID-1000A - Submitter PER segment. If not required by this implementation guide, do not send.
TR3 Notes:
  1. When the communication number represents a telephone number in the United States and other countries using the North American Dialing Plan (for voice, data, fax, etc.), the communication number must always include the area code and phone number using the format AAABBBCCCC where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number. Therefore, the following telephone number (555) 555-1234 would be represented as 5555551234. Do not submit long distance access numbers, such as 1, in the telephone number. Telephone extensions, when applicable, must be submitted in the next element immediately following the telephone number. When submitting telephone extensions, only submit the numeric extension, do not include data that indicates an extension, such as "ext" or "x-".
  2. There are 2 repetitions of the PER segment to allow for six possible communication numbers including extensions.
TR3 Example:
PER✱IC✱JOHN SMITH✱TE✱5555551234✱EX✱123~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
366
Contact Function Code
M 1
ID
2
Code identifying the major duty or responsibility of the person or group named
CODE
DEFINITION
IC
Information Contact
Situational
2
93
Name
O 1
AN
1/60
Free-form name
SITUATIONAL RULE: Required when the contact name is different than the name contained in the Submitter Name (NM1) segment. If not required by this implementation guide, do not send.
INDUSTRY NAME: Pay-to Factoring Agent Contact Name
Required
3
365
Communication Number Qualifier
X 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0304
CODE
DEFINITION
EM
Electronic Mail
FX
Facsimile
TE
Telephone
Required
4
364
Communication Number
X 1
AN
1/2048
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0304
The maximum number of characters to be supported for this field is 256.
Situational
5
365
Communication Number Qualifier
X 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when this information is deemed necessary by the submitter. If not required by this implementation guide, do not send.
CODE
DEFINITION
EM
Electronic Mail
EX
Telephone Extension
FX
Facsimile
TE
Telephone
Situational
6
364
Communication Number
X 1
AN
1/2048
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when this information is deemed necessary by the submitter. If not required by this implementation guide, do not send.
The maximum number of characters to be supported for this field is 256.
Situational
7
365
Communication Number Qualifier
X 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when this information is deemed necessary by the submitter. If not required by this implementation guide, do not send.
CODE
DEFINITION
EM
Electronic Mail
EX
Telephone Extension
FX
Facsimile
TE
Telephone
Situational
8
364
Communication Number
X 1
AN
1/2048
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when this information is deemed necessary by the submitter. If not required by this implementation guide, do not send.
The maximum number of characters to be supported for this field is 256.
Not Used
9
443
Contact Inquiry Reference
O 1
AN
1/20

HL - SUBSCRIBER LEVEL

X12 Name:
Hierarchical Level
X12 Purpose:
To identify dependencies among and the content of hierarchically related groups of data segments
X12 Comments:
  1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
  2. The HL segment defines a top-down/left-right ordered structure.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
  1. If a patient can be uniquely identified to the destination payer in Loop ID-2010BB by a unique Member Identification Number, then the patient is reported in the subscriber loop, and the patient HL in Loop ID-2000C is not used.
  2. If the patient is not the subscriber and cannot be identified to the destination payer by a unique Member Identification Number or it is not known to the sender if the Member Identification number is unique, both this HL and the patient HL in Loop ID-2000C are required.
TR3 Example:
HL✱2✱1✱22✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
628
Hierarchical ID Number
M 1
AN
1/12
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
COMMENT: HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
The first HL01 within each ST-SE envelope must begin with "1", and be incremented by one each time an HL is used in the transaction. Only numeric values are allowed in HL01.
Required
2
734
Hierarchical Parent ID Number
O 1
AN
1/12
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
COMMENT: HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Required
3
735
Hierarchical Level Code
M 1
ID
1/2
Code specifying the characteristic of a level in a hierarchical structure
COMMENT: HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
CODE
DEFINITION
22
Subscriber
Required
4
736
Hierarchical Child Code
O 1
ID
1
Code indicating if there are hierarchical child data segments subordinate to the level being described
COMMENT: HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
Refer to Section 1.4.4.2.2.2 Subscriber / Patient Hierarchical Level (HL) Segments for instructions on submitting subscriber and dependent claims in the same batch.
CODE
DEFINITION
0
No Subordinate HL Segment in This Hierarchical Structure.
Use when the patient can be uniquely identified to the destination payer in Loop ID-2010BB by a unique Member Identification Number.
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.
Use when the patient is not the subscriber and cannot be identified to the destination payer in Loop ID 2010BB by a unique Member Identification Number.

SBR - SUBSCRIBER INFORMATION

X12 Name:
Subscriber Information
X12 Purpose:
To record information specific to the primary insured and the insurance carrier for that insured
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
SBR✱P✱✱GRP01020102✱✱✱✱✱✱CI~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1138
Payer Responsibility Sequence Number Code
M 1
ID
1
Code identifying the insurance carrier's level of responsibility for a payment of a claim
INDUSTRY NAME: Payer Responsibility Sequence Code
  1. Within a given claim, the various values for the Payer Responsibility Sequence Number Code (other than value "U") may occur no more than once.
  2. This code value identifies, in the opinion of the submitter, the relative adjudication order of the destination payer among all of the payers identified in this claim.
CODE
DEFINITION
A
Payer Responsibility Four
B
Payer Responsibility Five
C
Payer Responsibility Six
D
Payer Responsibility Seven
E
Payer Responsibility Eight
F
Payer Responsibility Nine
G
Payer Responsibility Ten
H
Payer Responsibility Eleven
P
Primary
S
Secondary
T
Tertiary
U
Unknown
Use when sending payer to payer COB claims and the original payer determined the presence of this coverage from eligibility files received from this payer

OR

Use when the original claim did not provide the responsibility sequence for this payer.
Situational
2
1069
Individual Relationship Code
O 1
ID
2
Code indicating the relationship between two individuals or entities
SEMANTIC: SBR02 specifies the relationship to the person insured.
SITUATIONAL RULE: Required when the patient is the subscriber or is considered to be the subscriber. If not required by this implementation guide, do not send.
CODE
DEFINITION
18
Self
Situational
3
127
Reference Identification
O 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: SBR03 is policy or group number.
SITUATIONAL RULE: Required when the subscriber's identification card shows a group number.ORRequired when the subscriber's group number is otherwise gathered (e.g. eligibility inquiry).If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Group or Policy Number
  1. This is not the number uniquely identifying the subscriber. The unique subscriber number is submitted in Loop ID-2010BA-NM109.
  2. Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Situational
4
93
Name
O 1
AN
1/60
Free-form name
SEMANTIC: SBR04 is plan name.
SITUATIONAL RULE: Required when the subscriber's identification card shows a group name.ORRequired when the subscriber's group name is otherwise gathered (e.g. eligibility inquiry). If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver.
INDUSTRY NAME: Subscriber Group Name
Not Used
5
1336
Insurance Type Code
O 1
ID
1/3
Not Used
6
1143
Coordination of Benefits Code
O 1
ID
1
Not Used
7
1073
Yes/No Condition or Response Code
O 1
ID
1
Not Used
8
584
Employment Status Code
O 1
ID
2
Required
9
1032
Claim Filing Indicator Code
O 1
ID
1/2
Code identifying type of claim
CODE
DEFINITION
11
Other Non-Federal Programs
12
Preferred Provider Organization (PPO)
13
Point of Service (POS)
14
Exclusive Provider Organization (EPO)
15
Indemnity Insurance
16
Health Maintenance Organization (HMO) Medicare Risk
17
Dental Maintenance Organization
AM
Automobile Medical
BL
Blue Cross/Blue Shield
CH
Champus
Use when submitting Champus or Tricare claims.
CI
Commercial Insurance Co.
DS
Disability
FI
Federal Employees Program
HM
Health Maintenance Organization
LM
Liability Medical
MA
Medicare Part A
MB
Medicare Part B
MC
Medicaid
MD
Medicare Part D
ME
Medicare Advantage Plan
TV
Title V
UK
Unknown
VA
Veterans Affairs Plan
WC
Workers' Compensation Health Claim
ZZ
Mutually Defined
Use when no other code value applies.
Not Used
10
1732
Source of Payment Typology Code
O 1
ID
2/6

NM1*IL - SUBSCRIBER NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Loop 2010 contains information about entities that apply to all claims in loop 2300. For example, these entities may include billing provider, pay-to provider address, insurer, primary administrator, contract holder, pay-to plan, pay-to factoring agent, or claimant.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
In Workers' Compensation or other Property & Casualty claims, the "subscriber" may be a non-person entity (for example, the employer). However, this varies by state.
TR3 Example:
NM1✱IL✱1✱DOE✱JOHN✱T✱✱JR✱MI✱123456~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
IL
Insured or Subscriber
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
2
Non-Person Entity
Required
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Subscriber Last Name or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when NM102 = 1 (person) and the Middle Name or Initial is known to the sender. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Middle Name or Initial
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when NM102 = 1 (person) and the Suffix is known to the sender. If not required by this implementation guide do not send.
INDUSTRY NAME: Subscriber Name Suffix
Examples: I, II, III, IV, Jr, Sr
This data element is used only to indicate generation or patronymic.
Situational
8
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when NM109 is used. If not required by this implementation guide, do not send.
CODE
DEFINITION
II
Standard Unique Health Identifier for each Individual in the United States
Use when reporting the HIPAA Individual Patient Identifier.
MI
Member Identification Number
Use when indicating the subscriber's identification number as assigned by the payer.
Situational
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when NM102 = 1 (person). If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Primary Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

N3 - SUBSCRIBER ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when Loop-ID 2000C Patient Level is not used

OR

Required when the Claim Filing Indicator Code in Loop ID-2000B SBR09 = WC (Workers' Compensation). If not required by this implementation guide, do not send.
TR3 Example:
N3✱123 MAIN STREET~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Subscriber Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when a second address line is needed. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Address Line

N4 - SUBSCRIBER CITY, STATE, ZIP CODE

X12 Name:
Geographic Location
X12 Purpose:
To specify the geographic place of the named party
X12 Syntax:
  1. E0207
    Only one of N402 or N407 may be present.
  2. E0308
    Only one of N403 or N408 may be present.
  3. C0605
    If N406 is present, then N405 is required.
  4. C0704
    If N407 is present, then N404 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when Loop-ID 2000C Patient Level is not used

OR

Required when the Claim Filing Indicator Code in Loop ID-2000B SBR09 = WC (Workers' Compensation). If not required by this implementation guide, do not send.
TR3 Example:
N4✱KANSAS CITY✱MO✱64108~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
INDUSTRY NAME: Subscriber City Name
Situational
2
156
State or Province Code
X 1
ID
2
Code specifying the Standard State/Province as defined by appropriate government agency
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber State or Province Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
X 1
ID
3/15
Code specifying international postal zone code excluding punctuation and blanks (zip code for United States)
COMMENT: N403 contains the postal code in an unstructured format. N408 contains the postal code in a structured format. When a postal code data field is used, the parties shall agree as to which data element (N403 or N408) shall be used in the transaction set.
SEGMENT SYNTAX: E0308
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada, or when a postal code exists for the country in N404. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Postal Zone or ZIP Code
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
X 1
ID
2/3
Code identifying the country
SEGMENT SYNTAX: C0704
SITUATIONAL RULE: Required when the address is outside the United States of America. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Country Code
Use the alpha-2 country codes from Part 1 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
5
309
Location Qualifier
X 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
X 1
ID
1/3
Code identifying the country subdivision
SEGMENT SYNTAX: E0207, C0704
SITUATIONAL RULE: Required when the address is not in the United States of America, including its territories, or Canada, and the country in N404 has administrative subdivisions such as but not limited to states, provinces, cantons, etc. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Country Subdivision Code
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
8
1702
Postal Code-Formatted
X 1
AN
3/20

DMG*D8 - SUBSCRIBER DEMOGRAPHIC INFORMATION

X12 Name:
Demographic Information
X12 Purpose:
To supply demographic information
X12 Syntax:
  1. P0102
    If either DMG01 or DMG02 is present, then the other is required.
  2. P1011
    If either DMG10 or DMG11 is present, then the other is required.
  3. C1105
    If DMG11 is present, then DMG05 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when Loop-ID 2000C Patient Level is not used. If not required by this implementation guide, do not send.
TR3 Example:
DMG✱D8✱19690815✱M~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEGMENT SYNTAX: P0102
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
2
1251
Date Time Period
X 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
SEMANTIC: DMG02 is the date of birth.
SEGMENT SYNTAX: P0102
INDUSTRY NAME: Subscriber Birth Date
Required
3
1068
Gender Code
O 1
ID
1
Code indicating the sex of the individual
INDUSTRY NAME: Subscriber Gender Code
CODE
DEFINITION
F
Female
M
Male
U
Unknown
Use when the patient's gender cannot be explicitly identified as Male or Female and there are no reporting restrictions.
Not Used
4
1067
Marital Status Code
O 1
ID
1
Not Used
5
C056
Composite Race or Ethnicity Information
X 25
Not Used
6
1066
Citizenship Status Code
O 1
ID
1/2
Not Used
7
26
Country Code
O 1
ID
2/3
Not Used
8
659
Basis of Verification Code
O 1
ID
1/2
Not Used
9
380
Quantity
O 1
R
1/15
Not Used
10
1270
Code List Qualifier Code
X 1
ID
1/3
Not Used
11
1271
Industry Code
X 1
AN
1/30
Not Used
12
26
Country Code
O 1
ID
2/3

REF*SY - SUBSCRIBER SOCIAL SECURITY NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when an additional identification number to that provided in NM109 of this loop is necessary for the claim processor to identify the entity. If not required by this implementation guide, do not send.
TR3 Example:
REF✱EJ✱660415~REF✱SY✱123456789~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
SY
Social Security Number
Use when reporting a Social Security Number.

The Social Security Number must be a string of exactly nine numbers with no separators.

For example, sending "111002222" would be valid, while sending "111-00-2222" would be invalid.
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Subscriber Social Security Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*Y4 - PROPERTY & CASUALTY CLAIM NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the services included in this claim are part of a Property & Casualty claim that is not related to Workers' Compensation.

OR

Required when the services included in this claim are considered Workers' Compensation and the claim number has been established by the payer at the time of service. If not required by this implementation guide, do not send.
TR3 Notes:
  1. This is a Property & Casualty payer-assigned claim number. Providers receive this number from the Property & Casualty payer during eligibility determinations or some other communication with that payer. See Section 1.4.3, Property & Casualty, for additional information about Property & Casualty claims.
  2. This segment is not a HIPAA requirement as of this writing.
  3. In the case where the patient is the same person as the subscriber, the Property & Casualty Claim Number is sent in Loop ID-2010BA. In the case where the patient is a different person than the subscriber, this number is sent in Loop ID-2010CA. If Loop ID-2010CA is sent, then the Property & Casualty Claim Number must not be sent in Loop ID-2010BA.
TR3 Example:
REF✱Y4✱4445555~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
Y4
Agency Claim Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Property Casualty Claim Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

PER*IC - PROPERTY & CASUALTY SUBSCRIBER CONTACT INFORMATION

X12 Name:
Administrative Communications Contact
X12 Purpose:
To identify a person or office to whom administrative communications should be directed
X12 Syntax:
  1. P0304
    If either PER03 or PER04 is present, then the other is required.
  2. P0506
    If either PER05 or PER06 is present, then the other is required.
  3. P0708
    If either PER07 or PER08 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required for Property & Casualty claims when this information is deemed necessary by the submitter. If not required by this implementation guide, do not send.
TR3 Notes:
  1. When the communication number represents a telephone number in the United States and other countries using the North American Dialing Plan (for voice, data, fax, etc.), the communication number must always include the area code and phone number using the format AAABBBCCCC where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number. Therefore, the following telephone number (555) 555-1234 would be represented as 5555551234. Do not submit long distance access numbers, such as 1, in the telephone number. Telephone extensions, when applicable, must be submitted in the next element immediately following the telephone number. When submitting telephone extensions, only submit the numeric extension, do not include data that indicates an extension, such as "ext" or "x-".
  2. For Property & Casualty, the Property & Casualty Subscriber Contact may be used to report the name and telephone number of the policyholder. The policyholder for automobile accident claims is typically the individual or company listed on the proof of insurance card. The policyholder for workers' compensation claims is typically the patient's employer. When the policyholder or "subscriber" is a non-person entity, it is recommended that the health care provider use the name of a responsible individual within that organization.
TR3 Example:
PER✱IC✱JOHN SMITH✱TE✱5555551234✱EX✱123~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
366
Contact Function Code
M 1
ID
2
Code identifying the major duty or responsibility of the person or group named
CODE
DEFINITION
IC
Information Contact
Situational
2
93
Name
O 1
AN
1/60
Free-form name
SITUATIONAL RULE: Required when the Subscriber contact is a person other than the person identified in the Subscriber Name NM1 (Loop ID-2010BA). If not required by this implementation guide, do not send.
Required
3
365
Communication Number Qualifier
X 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0304
CODE
DEFINITION
TE
Telephone
Required
4
364
Communication Number
X 1
AN
1/2048
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0304
The maximum number of characters to be supported for this field is 256.
Situational
5
365
Communication Number Qualifier
X 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when this information is deemed necessary by the submitter. If not required by this implementation guide, do not send.
CODE
DEFINITION
EX
Telephone Extension
Situational
6
364
Communication Number
X 1
AN
1/2048
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when this information is deemed necessary by the submitter. If not required by this implementation guide, do not send.
The maximum number of characters to be supported for this field is 256.
Not Used
7
365
Communication Number Qualifier
X 1
ID
2
Not Used
8
364
Communication Number
X 1
AN
1/2048
Not Used
9
443
Contact Inquiry Reference
O 1
AN
1/20

NM1*PR - PAYER NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Loop 2010 contains information about entities that apply to all claims in loop 2300. For example, these entities may include billing provider, pay-to provider address, insurer, primary administrator, contract holder, pay-to plan, pay-to factoring agent, or claimant.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
  1. This is the destination payer.
  2. For the purposes of this implementation the term payer is synonymous with several other terms, such as, repricer and third party administrator.
TR3 Example:
NM1✱PR✱2✱ABC INSURANCE CO✱✱✱✱✱XV✱11122333~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
PR
Payer
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
2
Non-Person Entity
Required
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Payer Name
Not Used
4
1036
Name First
O 1
AN
1/35
Not Used
5
1037
Name Middle
O 1
AN
1/25
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Not Used
7
1039
Name Suffix
O 1
AN
1/10
Situational
8
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when NM109 is used. If not required by this implementation guide, do not send.
CODE
DEFINITION
XV
Standard Unique Health Plan Identifier (HPID)
CODE SOURCE: 540: Health Plan Identifier (HPID)
Situational
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when reporting the Health Plan ID (HPID) or Other Entity Identifier (OEID). If not required by this implementation guide, do not send.
INDUSTRY NAME: Payer Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

N3 - PAYER ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the payer address is available. If not required by this implementation guide, do not send.
TR3 Example:
N3✱123 MAIN STREET~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Payer Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when a second address line is needed. If not required by this implementation guide, do not send.
INDUSTRY NAME: Payer Address Line

N4 - PAYER CITY, STATE, ZIP CODE

X12 Name:
Geographic Location
X12 Purpose:
To specify the geographic place of the named party
X12 Syntax:
  1. E0207
    Only one of N402 or N407 may be present.
  2. E0308
    Only one of N403 or N408 may be present.
  3. C0605
    If N406 is present, then N405 is required.
  4. C0704
    If N407 is present, then N404 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the payer address is available. If not required by this implementation guide, do not send.
TR3 Example:
N4✱KANSAS CITY✱MO✱64108~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
INDUSTRY NAME: Payer City Name
Situational
2
156
State or Province Code
X 1
ID
2
Code specifying the Standard State/Province as defined by appropriate government agency
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: Payer State or Province Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
X 1
ID
3/15
Code specifying international postal zone code excluding punctuation and blanks (zip code for United States)
COMMENT: N403 contains the postal code in an unstructured format. N408 contains the postal code in a structured format. When a postal code data field is used, the parties shall agree as to which data element (N403 or N408) shall be used in the transaction set.
SEGMENT SYNTAX: E0308
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada, or when a postal code exists for the country in N404. If not required by this implementation guide, do not send.
INDUSTRY NAME: Payer Postal Zone or ZIP Code
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
X 1
ID
2/3
Code identifying the country
SEGMENT SYNTAX: C0704
SITUATIONAL RULE: Required when the address is outside the United States of America. If not required by this implementation guide, do not send.
INDUSTRY NAME: Payer Country
Use the alpha-2 country codes from Part 1 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
5
309
Location Qualifier
X 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
X 1
ID
1/3
Code identifying the country subdivision
SEGMENT SYNTAX: E0207, C0704
SITUATIONAL RULE: Required when the address is not in the United States of America, including its territories, or Canada, and the country in N404 has administrative subdivisions such as but not limited to states, provinces, cantons, etc. If not required by this implementation guide, do not send.
INDUSTRY NAME: Payer Country Subdivision
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
8
1702
Postal Code-Formatted
X 1
AN
3/20

REF*2U - PAYER SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when NM109 of this loop is not used.
OR
Required when an additional identification number to that provided in the NM109 of this loop is necessary to identify the entity.
If not required by this implementation guide, do not send.
TR3 Example:
REF✱2U✱435261708~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
2U
Payer Identification Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Payer Secondary Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF - BILLING PROVIDER SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
2
Situational Rule:
Required when NM109 in Loop 2010AA is not used and an identification number other than the NPI is necessary for the receiver to identify the provider. If not required by this implementation guide, do not send.
TR3 Example:
REF✱A6✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
A6
Provider Identifier
Use when reporting a proprietary provider number assigned by the destination payer identified in the Payer Name loop, Loop ID-2010BB, associated with this claim. This is true regardless of whether that payer is a government, private, commercial, or any other payer.
LU
Location Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Billing Provider Secondary Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

HL - PATIENT LEVEL

X12 Name:
Hierarchical Level
X12 Purpose:
To identify dependencies among and the content of hierarchically related groups of data segments
X12 Comments:
  1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
  2. The HL segment defines a top-down/left-right ordered structure.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when Loop ID-2000B HL04 = 1. If not required by this implementation guide, do not send.
TR3 Notes:
If a patient can be uniquely identified to the destination payer in Loop ID-2010BB by a unique Member Identification Number, then the patient is reported in the subscriber loop, and the patient HL in Loop ID-2000C is not used.
TR3 Example:
HL✱3✱2✱23✱0~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
628
Hierarchical ID Number
M 1
AN
1/12
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
COMMENT: HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
The first HL01 within each ST-SE envelope must begin with "1", and be incremented by one each time an HL is used in the transaction. Only numeric values are allowed in HL01.
Required
2
734
Hierarchical Parent ID Number
O 1
AN
1/12
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
COMMENT: HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Required
3
735
Hierarchical Level Code
M 1
ID
1/2
Code specifying the characteristic of a level in a hierarchical structure
COMMENT: HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
CODE
DEFINITION
23
Dependent
Required
4
736
Hierarchical Child Code
O 1
ID
1
Code indicating if there are hierarchical child data segments subordinate to the level being described
COMMENT: HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
CODE
DEFINITION
0
No Subordinate HL Segment in This Hierarchical Structure.

PAT - PATIENT INFORMATION

X12 Name:
Patient Information
X12 Purpose:
To supply patient information
X12 Syntax:
  1. P0506
    If either PAT05 or PAT06 is present, then the other is required.
  2. P0708
    If either PAT07 or PAT08 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
PAT✱01~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1069
Individual Relationship Code
O 1
ID
2
Code indicating the relationship between two individuals or entities
Specifies the patient's relationship to the person insured.
CODE
DEFINITION
01
Spouse
19
Child
20
Employee
21
Unknown
39
Organ Donor
40
Cadaver Donor
53
Life Partner
G8
Other Relationship
Not Used
2
1384
Patient Location Code
O 1
ID
1
Not Used
3
584
Employment Status Code
O 1
ID
2
Not Used
4
1220
Student Status Code
O 1
ID
1
Not Used
5
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Not Used
6
1251
Date Time Period
X 1
AN
1/35
Not Used
7
355
Unit or Basis for Measurement Code
X 1
ID
2
Not Used
8
81
Weight
X 1
R
1/10
Not Used
9
1073
Yes/No Condition or Response Code
O 1
ID
1

NM1*QC - PATIENT NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Loop 2010 contains information about entities that apply to all claims in loop 2300. For example, these entities may include billing provider, pay-to provider address, insurer, primary administrator, contract holder, pay-to plan, pay-to factoring agent, or claimant.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
NM1✱QC✱1✱DOE✱SALLY✱J~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
QC
Patient
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Required
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Patient Last Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when the Middle Name or Initial is known to the sender. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Middle Name or Initial
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when the Suffix is known to the sender. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Name Suffix
Not Used
8
66
Identification Code Qualifier
X 1
ID
1/2
Not Used
9
67
Identification Code
X 1
AN
2/80
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

N3 - PATIENT ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
N3✱123 MAIN STREET~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Patient Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when a second address line is needed. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Address Line

N4 - PATIENT CITY, STATE, ZIP CODE

X12 Name:
Geographic Location
X12 Purpose:
To specify the geographic place of the named party
X12 Syntax:
  1. E0207
    Only one of N402 or N407 may be present.
  2. E0308
    Only one of N403 or N408 may be present.
  3. C0605
    If N406 is present, then N405 is required.
  4. C0704
    If N407 is present, then N404 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
N4✱KANSAS CITY✱MO✱64108~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
INDUSTRY NAME: Patient City Name
Situational
2
156
State or Province Code
X 1
ID
2
Code specifying the Standard State/Province as defined by appropriate government agency
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient State or Province Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
X 1
ID
3/15
Code specifying international postal zone code excluding punctuation and blanks (zip code for United States)
COMMENT: N403 contains the postal code in an unstructured format. N408 contains the postal code in a structured format. When a postal code data field is used, the parties shall agree as to which data element (N403 or N408) shall be used in the transaction set.
SEGMENT SYNTAX: E0308
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada, or when a postal code exists for the country in N404. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Postal Zone or ZIP Code
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
X 1
ID
2/3
Code identifying the country
SEGMENT SYNTAX: C0704
SITUATIONAL RULE: Required when the address is outside the United States of America. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Country Code
Use the alpha-2 country codes from Part 1 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
5
309
Location Qualifier
X 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
X 1
ID
1/3
Code identifying the country subdivision
SEGMENT SYNTAX: E0207, C0704
SITUATIONAL RULE: Required when the address is not in the United States of America, including its territories, or Canada, and the country in N404 has administrative subdivisions such as but not limited to states, provinces, cantons, etc. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Country Subdivision Code
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
8
1702
Postal Code-Formatted
X 1
AN
3/20

DMG*D8 - PATIENT DEMOGRAPHIC INFORMATION

X12 Name:
Demographic Information
X12 Purpose:
To supply demographic information
X12 Syntax:
  1. P0102
    If either DMG01 or DMG02 is present, then the other is required.
  2. P1011
    If either DMG10 or DMG11 is present, then the other is required.
  3. C1105
    If DMG11 is present, then DMG05 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
DMG✱D8✱19690815✱M~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEGMENT SYNTAX: P0102
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
2
1251
Date Time Period
X 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
SEMANTIC: DMG02 is the date of birth.
SEGMENT SYNTAX: P0102
INDUSTRY NAME: Patient Birth Date
Required
3
1068
Gender Code
O 1
ID
1
Code indicating the sex of the individual
INDUSTRY NAME: Patient Gender Code
CODE
DEFINITION
F
Female
M
Male
U
Unknown
Use when the patient's gender cannot be explicitly identified as Male or Female and there are no reporting restrictions.
Not Used
4
1067
Marital Status Code
O 1
ID
1
Not Used
5
C056
Composite Race or Ethnicity Information
X 25
Not Used
6
1066
Citizenship Status Code
O 1
ID
1/2
Not Used
7
26
Country Code
O 1
ID
2/3
Not Used
8
659
Basis of Verification Code
O 1
ID
1/2
Not Used
9
380
Quantity
O 1
R
1/15
Not Used
10
1270
Code List Qualifier Code
X 1
ID
1/3
Not Used
11
1271
Industry Code
X 1
AN
1/30
Not Used
12
26
Country Code
O 1
ID
2/3

REF*Y4 - PROPERTY & CASUALTY CLAIM NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the services included in this claim are part of a Property & Casualty claim that is not related to Workers' Compensation.

OR

Required when the services included in this claim are considered Workers' Compensation and the claim number has been established by the payer at the time of service. If not required by this implementation guide, do not send.
TR3 Notes:
  1. This is a Property & Casualty payer-assigned claim number. Providers receive this number from the Property & Casualty payer during eligibility determinations or some other communication with that payer. See Section 1.4.3, Property & Casualty, for additional information about Property & Casualty claims.
  2. This segment is not a HIPAA requirement as of this writing.
TR3 Example:
REF✱Y4✱4445555~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
Y4
Agency Claim Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Property & Casualty Claim Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF - PROPERTY & CASUALTY PATIENT IDENTIFIER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when an identification number is needed by the receiver to identify the patient for Property & Casualty claims. If not required by this implementation guide, do not send.
TR3 Example:
REF✱EJ✱660415~REF✱SY✱123456789~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
1W
Member Identification Number
Use when reporting a patient identification number for the destination payer identified in the Payer Name loop, Loop ID 2010BB, associated with this claim.
SY
Social Security Number
Use when reporting a Social Security Number.

The Social Security Number must be a string of exactly nine numbers with no separators.

For example, sending "111002222" would be valid, while sending "111-00-2222" would be invalid.
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Property & Casualty Patient Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

PER*IC - PROPERTY & CASUALTY PATIENT CONTACT INFORMATION

X12 Name:
Administrative Communications Contact
X12 Purpose:
To identify a person or office to whom administrative communications should be directed
X12 Syntax:
  1. P0304
    If either PER03 or PER04 is present, then the other is required.
  2. P0506
    If either PER05 or PER06 is present, then the other is required.
  3. P0708
    If either PER07 or PER08 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required for Property & Casualty claims when this information is different than the information provided in the Subscriber Contact Information PER segment in Loop ID-2010BA and this information is deemed necessary by the submitter. If not required by this implementation guide, do not send.
TR3 Notes:
When the communication number represents a telephone number in the United States and other countries using the North American Dialing Plan (for voice, data, fax, etc.), the communication number must always include the area code and phone number using the format AAABBBCCCC where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number. Therefore, the following telephone number (555) 555-1234 would be represented as 5555551234. Do not submit long distance access numbers, such as 1, in the telephone number. Telephone extensions, when applicable, must be submitted in the next element immediately following the telephone number. When submitting telephone extensions, only submit the numeric extension, do not include data that indicates an extension, such as "ext" or "x-".
TR3 Example:
PER✱IC✱JOHN SMITH✱TE✱5555551234✱EX✱123~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
366
Contact Function Code
M 1
ID
2
Code identifying the major duty or responsibility of the person or group named
CODE
DEFINITION
IC
Information Contact
Situational
2
93
Name
O 1
AN
1/60
Free-form name
SITUATIONAL RULE: Required when the Patient contact is a person other than the person identified in the Patient Name NM1 (Loop ID-2010CA). If not required by this implementation guide, do not send.
INDUSTRY NAME: Property & Casualty Patient Contact Name
Required
3
365
Communication Number Qualifier
X 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0304
CODE
DEFINITION
TE
Telephone
Required
4
364
Communication Number
X 1
AN
1/2048
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0304
The maximum number of characters to be supported for this field is 256.
Situational
5
365
Communication Number Qualifier
X 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when this information is deemed necessary by the submitter. If not required by this implementation guide, do not send.
CODE
DEFINITION
EX
Telephone Extension
Situational
6
364
Communication Number
X 1
AN
1/2048
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when this information is deemed necessary by the submitter. If not required by this implementation guide, do not send.
The maximum number of characters to be supported for this field is 256.
Not Used
7
365
Communication Number Qualifier
X 1
ID
2
Not Used
8
364
Communication Number
X 1
AN
1/2048
Not Used
9
443
Contact Inquiry Reference
O 1
AN
1/20

CLM - CLAIM INFORMATION

X12 Name:
Health Claim
X12 Purpose:
To specify basic data about the claim
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
  1. The developers of this implementation guide recommend that trading partners limit the size of the transaction (ST-SE envelope) to a maximum of 5000 CLM segments. There is no recommended limit to the number of ST-SE transactions within a GS-GE or ISA-IEA. Willing trading partners can agree to set limits higher.
  2. For purposes of this documentation, the claim detail information is presented only in the patient level. Specific claim detail information can be given in either the subscriber or the patient hierarchical level. Because of this, the claim information is said to "float". Claim information is positioned in the same hierarchical level that describes its owner-participant, either the subscriber or the patient. In other words, the claim information, Loop ID-2300, is placed following Loop ID-2010BB in the Subscriber Hierarchical Level (HL) when patient information is sent in Loop ID-2010BA of the Subscriber HL. Claim information is placed in the Patient HL when the patient information is sent in Loop ID-2010CA of the Patient HL. When the patient is the subscriber or is considered to be the subscriber, Loop ID-2000C and Loop ID-2010CA are not sent. See Subscriber/Patient HL Segment explanation in section 1.4.4.2.2.2 for details.
TR3 Example:
CLM✱013193000001✱500✱✱✱11:B:1✱Y✱A✱Y✱Y~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1028
Claim Submitter's Identifier
M 1
AN
1/38
Identifier used to track a claim from creation by the health care provider through payment
INDUSTRY NAME: Provider's Assigned Claim Identifier
  1. The maximum number of characters to be supported for this field is '35'. Characters beyond the maximum are not required to be stored nor returned by any 837-receiving system.
  2. When Loop ID-2010AC is not present, this identifier is generated by the provider for the purpose of reassociation to their claim accounts receivable, and must not be modified. This identifier, as submitted in the 837, is returned in the 835 and/or other transactions. This identifier is not to be validated beyond standard TR3 syntax and semantic rules.
  3. When Loop ID-2010AC is present, CLM01 represents the Pay-To Plan's claim number (ICN/DCN) assigned during their processing of the claim. See Section 1.4.2.4 Coordination of Benefits - Subrogation for information on subrogation claim reporting.
  4. The developers of this implementation guide strongly recommend that submitters use unique identifiers for this data element for each individual claim.
Required
2
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: CLM02 is the total amount of all submitted charges of service segments for this claim.
INDUSTRY NAME: Total Claim Charge Amount
  1. The Total Claim Charge Amount must be greater than or equal to zero.
  2. The total claim charge amount must balance to the sum of all service line charge amounts reported in the Dental Service (SV3) segments for this claim.
  3. Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
Not Used
3
1032
Claim Filing Indicator Code
O 1
ID
1/2
Not Used
4
1343
Non-Institutional Claim Type Code
O 1
ID
1/2
Required
5
C023
Health Care Service Location Information
O 1
To provide information that identifies the place of service or the type of bill related to the location at which a health care service was rendered
X12 COMPOSITE SEMANTIC NOTES:
  1. C023-01 does not contain the last position of the Uniform Bill Type Code (the Claim Frequency Code).
  2. C023-02 qualifies C023-01.
CLM05 applies to all service lines unless it is overridden at the line level.
Required
5-1
1331
Facility Code Value
M 1
AN
1/3
Code identifying where services were, or may be, performed; the National Uniform Billing Committee (NUBC) Facility Type Code for Institutional Services or the Place of Service Codes for Professional or Dental Services.
INDUSTRY NAME: Place of Service Code
Required
5-2
1332
Facility Code Qualifier
M 1
ID
1/2
Code identifying the type of facility referenced
CODE
DEFINITION
B
Place of Service Codes for Professional or Dental Services
CODE SOURCE: 237: Place of Service Codes for Professional Claims
Required
5-3
1325
Claim Frequency Type Code
O 1
ID
1
Code specifying the Type of Bill Frequency Code. It is the last digit of Type of Bill in the UB manual, as defined by the National Uniform Billing Committee
INDUSTRY NAME: Claim Frequency Code
CODE SOURCE 235: Claim Frequency Type Code
Required
6
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: CLM06 is provider signature on file indicator. A "Y" value indicates the provider signature is on file; an "N" value indicates the provider signature is not on file.
INDUSTRY NAME: Provider or Supplier Signature Indicator
CODE
DEFINITION
N
No
Y
Yes
Situational
7
1359
Provider Accept Assignment Code
O 1
ID
1
Code indicating whether the provider accepts assignment
SITUATIONAL RULE: Required when the subscriber's health plan for the destination payer is Medicare, including Medicare Fee For Service (FFS) or a Medicare Advantage Plan (Medicare Part C).If not required by this implementation guide, do not send.
INDUSTRY NAME: Assignment or Plan Participation Code
  1. This element is NOT for reporting whether the patient has or has not assigned benefits to the provider. The benefit assignment indicator is in CLM08.
  2. This element indicates the provider's assignment with the Medicare Fee For Service (FFS) program and by extension the Medicare Advantage Plan (Medicare Part C).
  3. The value in this element does not supersede an agreement between the provider and payer regarding assignment or participation status unless that agreement allows claim by claim exceptions.
  4. On COB claims where Medicare is not the destination payer, assignment or participation designation with Medicare is not reported in this CLM07 element; rather, it is reported in the Loop 2320 Other Insurance Coverage Information (OI Segment) corresponding to Medicare as the other payer.
CODE
DEFINITION
A
Assigned
Use when the provider has a participation agreement with Medicare.
OR
Use when the provider does not have a participation agreement with Medicare but has elected to accept assignment for this claim.
C
Not Assigned
Use when the provider does not have a participation agreement with Medicare and has elected not to accept assignment for this claim.
Required
8
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: CLM08 is assignment of benefits indicator. A "Y" value indicates insured or authorized person authorizes benefits to be assigned to the provider; an "N" value indicates benefits have not been assigned to the provider.
INDUSTRY NAME: Benefits Assignment Certification Indicator
This element is for reporting whether the patient has or has not assigned benefits to the provider.
CODE
DEFINITION
N
No
Y
Yes
Required
9
1363
Release of Information Code
O 1
ID
1
Code indicating whether the provider has on file a signed statement by the patient authorizing the release of medical data to other organizations
The Release of Information response is limited to the information carried in this claim.
CODE
DEFINITION
I
Informed Consent to Release Medical Information for Conditions or Diagnoses Regulated by Federal Statutes
Use when the provider has not collected a signature AND state or federal laws do not require a signature be collected.
Y
Yes, Provider has a Signed Statement Permitting Release of Medical Billing Data Related to a Claim
Use when Provider has a signed statement permitting release of dental billing data related to a claim.
Not Used
10
1351
Patient Signature Source Code
O 1
ID
1
Situational
11
C024
Related Causes Information
O 1
To identify one or more related causes and associated state or country information
X12 COMPOSITE COMMENTS: C024-04 and C024-05 apply only to auto accidents when C024-01, C024-02, or C024-03 is equal to "AA".
SITUATIONAL RULE: Required when the services provided are employment related or the result of an accident. If not required by this implementation guide, do not send.
If DTP - Date of Accident (DTP01=439) is used, then CLM11 is required.
Required
11-1
1362
Related-Causes Code
M 1
ID
2/3
Code identifying an accompanying cause of an illness, injury or an accident
INDUSTRY NAME: Related Causes Code
CODE
DEFINITION
AA
Auto Accident
EM
Employment
Use when reporting an employment related illness.
OA
Other Accident
Situational
11-2
1362
Related-Causes Code
O 1
ID
2/3
Code identifying an accompanying cause of an illness, injury or an accident
SITUATIONAL RULE: Required when the services are related to an employment related accident and the CLM11-01 value is "AA" or "OA". If not required by this implementation guide, do not send.
INDUSTRY NAME: Related Causes Code
CODE
DEFINITION
EM
Employment
Not Used
11-3
1362
Related-Causes Code
O 1
ID
2/3
Situational
11-4
156
State or Province Code
O 1
ID
2
Code specifying the Standard State/Province as defined by appropriate government agency
SITUATIONAL RULE: Required when CLM11-01 has a value of "AA" and the automobile accident occurred in the US, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: Auto Accident State or Province Code
CODE SOURCE 22: States and Provinces
Situational
11-5
26
Country Code
O 1
ID
2/3
Code identifying the country
SITUATIONAL RULE: Required when CLM11-01 has a value of "AA" and the accident occurred in a country other than US, including its territories, or Canada. If not required by this implementation guide, do not send.
Use the alpha-2 country codes from Part 1 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Situational
12
1366
Special Program Code
O 1
ID
2/3
Code indicating the Special Program under which the services rendered to the patient were performed
SITUATIONAL RULE: Required when the services were rendered under one of the following circumstances, programs, or projects for Medicaid. If not required by this implementation guide, do not send.
INDUSTRY NAME: Special Program Indicator
CODE
DEFINITION
01
Early & Periodic Screening, Diagnosis, and Treatment (EPSDT) or Child Health Assessment Program (CHAP)
02
Physically Handicapped Children's Program
03
Special Federal Funding
05
Disability
Not Used
13
1073
Yes/No Condition or Response Code
O 1
ID
1
Not Used
14
1338
Level of Service Code
O 1
ID
1/3
Not Used
15
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
16
1360
Provider Agreement Code
O 1
ID
1
Code indicating the type of agreement under which the provider is submitting this claim
SITUATIONAL RULE: Required when a non-participating (non-par) provider is submitting a participating (par) claim and the destination payer is not Medicare, including Medicare Fee For Service (FFS) or a Medicare Advantage Plan (Medicare Part C). If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver.
CODE
DEFINITION
P
Participation Agreement
Use when a non-par provider is sending a par claim as allowed under certain plans.
Not Used
17
1029
Claim Status Code
O 1
ID
1/2
Not Used
18
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
19
1383
Claim Submission Reason Code
O 1
ID
2
Code identifying reason for claim submission
SITUATIONAL RULE: Required when the entire claim is being submitted as a predetermination request. If not required by this implementation guide, do not send.
INDUSTRY NAME: Predetermination of Benefits Code
The Predetermination of Benefits Code, when sent, indicates that the entire claim is being sent for predetermination. When the code is not sent, the entire claim is being submitted for payment.
CODE
DEFINITION
PB
Predetermination of Dental Benefits
Situational
20
1514
Delay Reason Code
O 1
ID
1/2
Code indicating the reason why a request was delayed
SITUATIONAL RULE: Required when the claim is submitted late (past contracted date of filing limitations). If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Proof of Eligibility Unknown or Unavailable
2
Litigation
3
Authorization Delays
4
Delay in Certifying Provider
5
Delay in Supplying Billing Forms
6
Delay in Delivery of Custom-made Appliances
7
Third Party Processing Delay
8
Delay in Eligibility Determination
9
Original Claim Rejected or Denied Due to a Reason Unrelated to the Billing Limitation Rules
10
Administration Delay in the Prior Approval Process
11
Other
15
Natural Disaster
Situational
21
1774
Claim Authorization Exception Code
O 1
ID
1/2
Code identifying the reason for requesting an exception to standard processing of the claim
SITUATIONAL RULE: Required when mandated by government law or regulation to obtain authorization for specific service(s) but, for the reasons listed, the service was performed without obtaining an authorization. If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Immediate/Urgent Care
2
Services Rendered in a Retroactive Period
3
Emergency Care
4
Subscriber has Temporary Medicaid
Use when reporting the subscriber has Temporary Medicaid.
5
Request from County for Second Opinion to Determine if Recipient Can Work
6
Request for Override Pending
7
Special Handling

DTP*523 - ORIGINAL CLAIM CREATION DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
This is the date that the provider created this iteration of the claim from their business application system for transmission to the payer. This date must not be changed by subsequent entities who may handle the claim. Subsequent entities must use the BHT04 (Transaction Set Creation Date) for this purpose.
TR3 Example:
DTP✱523✱D8✱20220517~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
523
Date of Claim
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times

DTP*439 - ACCIDENT DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the services provided are the result of an accident (Loop 2300 CLM11-01 has a value of "AA" or "OA"). If not required by this implementation guide, do not send.
TR3 Example:
DTP✱439✱D8✱20221030~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
439
Accident
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Accident Date

DTP*452 - ORTHODONTIC BANDING DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when reporting the date orthodontic appliances were placed. If not required by this implementation guide, do not send.
TR3 Notes:
This date applies to all service lines within Loop ID-2400 unless a DTP segment occurs in Loop ID-2400 with the same value in DTP01. In that case, the DTP in Loop ID-2400 overrides the DTP in Loop ID-2300 for that service line only.
TR3 Example:
DTP✱452✱D8✱20221030~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
452
Appliance Placement
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Orthodontic Banding Date

DTP*472 - SERVICE DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when all the service lines for this claim were performed and the claim is not a predetermination request (Loop ID 2300 CLM19 (Predetermination of Benefits Code) is not used). If not required by this implementation guide, do not send.
TR3 Notes:
This date applies to all service lines within Loop ID-2400 unless a DTP segment occurs in Loop ID-2400 with the same value in DTP01. In that case, the DTP in Loop ID-2400 overrides the DTP in Loop ID-2300 for that service line only.
TR3 Example:
DTP✱472✱D8✱20221030~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
472
Service
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
RD8
Range of Dates Expressed in Format CCYYMMDD-CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Service Date

DTP*050 - REPRICER RECEIVED DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when a repricer is passing the claim on to the payer. If not required by this implementation guide, do not send.
TR3 Notes:
This segment is not completed by providers. The information is completed by repricers only.
TR3 Example:
DTP✱050✱D8✱20221030~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
050
Received
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Repricer Received Date

DN1 - ORTHODONTIC TREATMENT INFORMATION

X12 Name:
Orthodontic Information
X12 Purpose:
To supply orthodontic information
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the claim contains services related to treatment for orthodontic purposes. If not required by this implementation guide, do not send.
TR3 Notes:
When reporting this segment, at least one of DN101, DN102, or DN103 must be present.
TR3 Example:
  1. DN1✱36✱27~
  2. DN1✱✱✱✱Y~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Situational
1
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: DN101 is the estimated number of treatment months.
SITUATIONAL RULE: Required when reporting the total months of orthodontic treatment. If not required by this implementation guide, do not send.
INDUSTRY NAME: Orthodontic Treatment Months Count
Situational
2
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: DN102 is the number of treatment months remaining.
SITUATIONAL RULE: Required when reporting the number of months of orthodontic treatment remaining for a transfer patient. If not required by this implementation guide, do not send.
INDUSTRY NAME: Orthodontic Treatment Months Remaining Count
Situational
3
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: DN103 is the orthodontic indicator. A "Y" value indicates that the claim contains services related to treatment for orthodontic purposes. An "N" value indicates that the services for this claim are not for orthodontic purposes.
SITUATIONAL RULE: Required when the services reported on this claim are for orthodontic purposes and both DN101 and DN102 are not used. If not required by this implementation guide, do not send.
INDUSTRY NAME: Orthodontic Treatment Indicator
Not Used
4
352
Description
O 1
AN
1/80

DN2 - TOOTH STATUS

X12 Name:
Tooth Summary
X12 Purpose:
To specify the status of individual teeth
X12 Syntax:
P0405
If either DN204 or DN205 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
35
Situational Rule:
Required when the submitter is reporting a missing tooth or a tooth to be extracted in the future. If not required by this implementation guide, do not send.
TR3 Example:
DN2✱8✱E✱✱✱✱JP~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
127
Reference Identification
M 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: DN201 is the tooth number.
INDUSTRY NAME: Tooth Number
  1. The Universal National Tooth Designation System must be used to identify tooth numbers for this element. See Code Source 135: American Dental Association.
  2. Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Required
2
1368
Tooth Status Code
O 1
ID
1/2
Code specifying the status of the tooth
CODE
DEFINITION
E
To Be Extracted
M
Missing
Not Used
3
380
Quantity
O 1
R
1/15
Not Used
4
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Not Used
5
1251
Date Time Period
X 1
AN
1/35
Required
6
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
SEMANTIC: DN206 designates the code set used to identify the tooth in DN201.
CODE
DEFINITION
JP
Universal National Tooth Designation System
CODE SOURCE: 135: American Dental Association

PWK - CLAIM SUPPLEMENTAL INFORMATION

X12 Name:
Paperwork
X12 Purpose:
To identify the type or transmission or both of paperwork or supporting information
X12 Syntax:
  1. P0506
    If either PWK05 or PWK06 is present, then the other is required.
  2. P1011
    If either PWK10 or PWK11 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
10
Situational Rule:
Required when there is an attachment available for this claim. If not required by this implementation guide, do not send.
TR3 Example:
PWK✱OZ✱BM✱✱✱AC✱DMN0012~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
755
Report Type Code
M 1
ID
2
Code indicating the title or contents of a document, report or supporting item
INDUSTRY NAME: Attachment Report Type Code
CODE
DEFINITION
B4
Referral Form
DA
Dental Models
DG
Diagnostic Report
EB
Explanation of Benefits (Coordination of Benefits or Medicare Secondary Payor)
OZ
Support Data for Claim
P6
Periodontal Charts
RB
Radiology Films
RR
Radiology Reports
Required
2
756
Report Transmission Code
O 1
ID
1/2
Code specifing timing, transmission method or format by which reports are to be sent
INDUSTRY NAME: Attachment Transmission Code
CODE
DEFINITION
AA
Available on Request at Provider Site
Use when the provider deems it necessary to identify additional information that is being held at the provider's office and is available upon request by the payer (or appropriate entity).
BM
By Mail
Use when paper attachments are sent by mail.
EL
Electronically Only
Use when attachments are sent electronically and transmitted in another functional group (for example, X12N 275 - Additional Information to Support a Health Care Claim or Encounter).
EM
E-Mail
Use when attachments are sent by e-mail.
FT
File Transfer
Use when attachments are sent by File Transfer to payer or maintained by an attachment warehouse or similar vendor.
FX
By Fax
Use when paper attachments are sent by fax.
Not Used
3
757
Report Copies Needed
O 1
N
1/2
Not Used
4
98
Entity Identifier Code
O 1
ID
2/3
Situational
5
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
COMMENT: PWK05 and PWK06 may be used to identify the addressee by a code number.
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when PWK02 = "BM", "EL", "EM", "FX" or "FT". If not required by this implementation guide, do not send.
CODE
DEFINITION
AC
Attachment Control Number
Situational
6
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when PWK02 = "BM", "EL", "EM", "FX" or "FT". If not required by this implementation guide, do not send.
INDUSTRY NAME: Attachment Control Number
  1. PWK06 is a unique identifier assigned by the provider to be used to identify the supplemental documentation for this claim. When using the X12N 275 - Additional Information to Support a Health Care Claim or Encounter, the number in PWK06 is carried in the TRN Segment.
  2. For the purpose of this implementation, the maximum field length is 50.
Not Used
7
352
Description
O 1
AN
1/80
Not Used
8
C002
Actions Indicated
O 1
Not Used
9
1525
Request Category Code
O 1
ID
1/2
Not Used
10
1270
Code List Qualifier Code
X 1
ID
1/3
Not Used
11
1271
Industry Code
X 1
AN
1/30

AMT*F5 - PATIENT AMOUNT PAID

X12 Name:
Monetary Amount Information
X12 Purpose:
To indicate the total monetary amount
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when patient has made payment specifically toward this claim. If not required by this implementation guide, do not send.
TR3 Notes:
Patient Amount Paid refers to the sum of all amounts paid on the claim by the patient or his or her representative(s).
TR3 Example:
AMT✱F5✱152.45~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
522
Amount Qualifier Code
M 1
ID
1/3
Code specifying the amount qualifier
CODE
DEFINITION
F5
Patient Amount Paid
Required
2
782
Monetary Amount
M 1
R
1/18
Monetary amount
INDUSTRY NAME: Patient Amount Paid
Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
Not Used
3
478
Credit/Debit Flag Code
O 1
ID
1

REF*G3 - PREDETERMINATION IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when sending the Predetermination of Benefits Identification Number for services that have been previously predetermined and are now being submitted for payment. If not required by this implementation guide, do not send.
TR3 Notes:
Reference numbers at this position apply to the entire claim.
TR3 Example:
REF✱G3✱13579~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
G3
Predetermination of Benefits Identification Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Predetermination of Benefits Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*82 - DENTAL READINESS CLASSIFICATION CODE

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when submitting a claim for the TRICARE - Active Duty Dental Program
AND
when not submitting a predetermination.
If not required by this implementation guide, do not send.
TR3 Example:
REF✱82✱DRC1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
82
Data Item Description (DID) Reference
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Dental Readiness Code
  1. DRC1 - (Class 1) Active duty service members with current dental examinations who do not require dental treatment or reevaluation.
  2. DRC2 - (Class 2) Active duty service members with current dental examinations whose oral conditions are unlikely to result in dental emergencies within 12 months.
  3. DRC3 - (Class 3) Active duty service members who require urgent or emergent dental treatment.
  4. Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*F8 - PAYER CLAIM CONTROL NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when CLM05-03 (Claim Frequency Code) indicates this claim is a replacement or void to a previously adjudicated claim. If not required by this implementation guide, do not send.
TR3 Notes:
This information is specific to the destination payer reported in Loop ID-2010BB.
TR3 Example:
REF✱F8✱R555588~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
F8
Original Reference Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Payer Claim Control Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*9F - REFERRAL NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when a referral number is assigned by the payer or Utilization Management Organization (UMO) and the referral applies to the entire claim. If not required by this implementation guide, do not send.
TR3 Notes:
  1. This segment must not be used to report the Predetermination of Benefits Identification Number.
  2. Information in this Loop ID-2300 applies to the entire claim unless overridden on a service line by the presence of Loop ID-2400 with the same value in REF01.
TR3 Example:
REF✱9F✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
9F
Referral Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Referral Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*G1 - PRIOR AUTHORIZATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when a prior authorization number is assigned by the payer or Utilization Management Organization (UMO) and the prior authorization applies to the entire claim. If not required by this implementation guide, do not send.
TR3 Notes:
  1. This segment must not be used to report the Predetermination of Benefits Identification Number.
  2. Generally, prior authorization numbers are assigned by the payer or UMO to authorize a service prior to it being performed. The UMO (Utilization Management Organization) is generally the entity empowered to make a decision regarding the outcome of a health services review or is the owner of information. The prior authorization number carried in this REF is specific to the destination payer reported in the Loop ID-2010BB. If other payers have similar numbers for this claim, report that information in the Loop ID-2330B REF which holds that payer's information.
TR3 Example:
REF✱G1✱13579~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
G1
Prior Authorization Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Prior Authorization Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*9A - REPRICED CLAIM NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when this information is deemed necessary by the repricer. If not required by this implementation guide, do not send.
TR3 Notes:
  1. This information is specific to the destination payer reported in Loop ID-2010BB.
  2. This segment is not completed by providers. The information is completed by repricers only.
TR3 Example:
REF✱9A✱RJ55555~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
9A
Repriced Claim Reference Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Repriced Claim Reference Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*9C - ADJUSTED REPRICED CLAIM NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when this information is deemed necessary by the repricer. If not required by this implementation guide, do not send.
TR3 Notes:
  1. This information is specific to the destination payer reported in Loop ID-2010BB.
  2. This segment is not completed by providers. The information is completed by repricers only.
TR3 Example:
REF✱9C✱RP44444444~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
9C
Adjusted Repriced Claim Reference Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Adjusted Repriced Claim Reference Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*D9 - CLAIM IDENTIFIER FOR TRANSMISSION INTERMEDIARIES

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when this information is deemed necessary by transmission intermediaries (clearinghouses and others) who need to attach their own unique claim number. If not required by this implementation guide, do not send.
TR3 Example:
REF✱D9✱TJ98UU321~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
Number assigned by clearinghouse, van, etc.
CODE
DEFINITION
D9
Claim Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Claim Identifier for Transmission Intermediaries
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*SOJ - PROPERTY & CASUALTY STATE OF CLAIM JURISDICTION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the services are considered part of a Property & Casualty claim where either Loop ID 2010BA or Loop ID 2010CA REF segment (Property & Casualty Claim Number) is used and the claim is being submitted under state jurisdictionally defined statutes, rules, or regulations for electronic exchange of health information. If not required by this implementation guide, do not send.
TR3 Notes:
  1. This segment is not a HIPAA requirement as of this writing.
  2. This is not the state of jurisdiction for determination of benefits but is the state whose rules under which the electronic claim has been submitted.
TR3 Example:
REF✱SOJ✱IL~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
SOJ
State of Claim Jurisdiction
CODE SOURCE: 22: States and Provinces
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: State of Claim Jurisdiction
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

K3 - FILE INFORMATION

X12 Name:
File Information
X12 Purpose:
To transmit a fixed-format record or matrix contents
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
10
Situational Rule:
Required when X12N has reviewed and approved the data requirements of a regulatory/legislative authority for use of the K3 Segment and has concluded that there is no current method to meet the requirement. (See Section 1.4.6.1 for obtaining X12N approval). If not required by this implementation guide, do not send.
TR3 Notes:
  1. The K3 segment is used only when necessary to meet the unexpected data requirement of a regulatory/legislative authority. Before this segment can be used:

    - X12N must conclude there is no other available option in the implementation guide to meet the emergency regulatory/legislative requirement.

    - The requester must submit a change request accompanied by the relevant business documentation and receive approval for the request.

    Upon review of the request, X12N will issue an approval or denial decision to the requesting entity. Approved usage(s) of the K3 Segment will be reviewed by the applicable X12N work group to develop a permanent change to include the business case in future transaction implementations.
  2. Only when all of the requirements above have been met, may the regulatory agency require the temporary use of the K3 segment.
TR3 Example:
K3✱STATE DATA REQUIREMENT~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
449
Fixed Format Information
M 1
AN
1/80
Data in fixed format agreed upon by sender and receiver
INDUSTRY NAME: Temporary Solution for a Statutory/Regulatory Requirement
Not Used
2
1333
Record Format Code
O 1
ID
1/2
Not Used
3
C001
Composite Unit of Measure
O 1

NTE*ADD - CLAIM NOTE

X12 Name:
Note/Special Instruction
X12 Purpose:
To transmit information in a free-form format, if necessary, for comment or special instruction
X12 Comments:
The NTE segment permits free-form information/data which, under ANSI X12 standard implementations, is not machine processible. The use of the NTE segment should therefore be avoided, if at all possible, in an automated environment.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
5
Situational Rule:
Required when in the judgment of the provider, the information is needed to substantiate the medical treatment and is not supported elsewhere within the claim data set.
If not required by this implementation guide, do not send.
TR3 Notes:
The developers of this implementation guide discourage using narrative information within the 837. Trading partners who use narrative information with claims are strongly encouraged to codify that information within the X12 environment.
TR3 Example:
NTE✱ADD✱PATIENT IS EXTREMELY SENSITIVE TO PAIN AND REQUIRES ADDITIONAL SEDATION~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
363
Note Reference Code
O 1
ID
3
Code identifying the functional area or purpose for which the note applies
CODE
DEFINITION
ADD
Additional Information
Required
2
352
Description
M 1
AN
1/80
A free-form description to clarify the related data elements and their content
INDUSTRY NAME: Claim Note Text

HI - HEALTH CARE DIAGNOSIS CODE

X12 Name:
Health Care Information Codes
X12 Purpose:
To supply information related to the delivery of health care
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the diagnosis may have an impact on the adjudication of the claim in cases where specific dental procedures may minimize the risks associated with the connection between the patient's oral and systemic health conditions. If not required by this implementation guide, do not send.
TR3 Notes:
Do not transmit the decimal point for ICD codes.
TR3 Example:
HI✱ABF:K029✱ABF:M2602✱ABF:M2604~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
C022
Health Care Code Information
M 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
  7. C022-10 is the attribute of the code in C022-02 from the same code list.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported when C022-02 is a Diagnosis Code and range of diagnosis codes were NOT given in C022-08.
Required
1-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
CODE
DEFINITION
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
TQ
Systemized Nomenclature of Dentistry (SNODENT)
Use when reporting SNODENT Codes. This code set is not allowed for use under HIPAA at the time of this writing and can only be used:

If a new rule names the SNODENT codes as an allowable code set under HIPAA,
OR
Use when the Secretary of Health and Human Services grants an exception to use the code set as a pilot project.
CODE SOURCE: 135: American Dental Association
Required
1-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Diagnosis Code
Not Used
1-3
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Not Used
1-4
1251
Date Time Period
X 1
AN
1/35
Not Used
1-5
782
Monetary Amount
O 1
R
1/18
Not Used
1-6
380
Quantity
O 1
R
1/15
Not Used
1-7
799
Version Identifier
O 1
AN
1/30
Not Used
1-8
1271
Industry Code
X 1
AN
1/30
Not Used
1-9
1271
Industry Code
X 1
AN
1/30
Not Used
1-10
1271
Industry Code
O 1
AN
1/30
Situational
2
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
  7. C022-10 is the attribute of the code in C022-02 from the same code list.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported when C022-02 is a Diagnosis Code and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when it is necessary to report an additional diagnosis and the preceding HI data elements have been used to report other diagnoses. If not required by this implementation guide, do not send.
Required
2-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
CODE
DEFINITION
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
TQ
Systemized Nomenclature of Dentistry (SNODENT)
Use when reporting SNODENT Codes. This code set is not allowed for use under HIPAA at the time of this writing and can only be used:

If a new rule names the SNODENT codes as an allowable code set under HIPAA,
OR
Use when the Secretary of Health and Human Services grants an exception to use the code set as a pilot project.
CODE SOURCE: 135: American Dental Association
Required
2-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Diagnosis Code
Not Used
2-3
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Not Used
2-4
1251
Date Time Period
X 1
AN
1/35
Not Used
2-5
782
Monetary Amount
O 1
R
1/18
Not Used
2-6
380
Quantity
O 1
R
1/15
Not Used
2-7
799
Version Identifier
O 1
AN
1/30
Not Used
2-8
1271
Industry Code
X 1
AN
1/30
Not Used
2-9
1271
Industry Code
X 1
AN
1/30
Not Used
2-10
1271
Industry Code
O 1
AN
1/30
Situational
3
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
  7. C022-10 is the attribute of the code in C022-02 from the same code list.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported when C022-02 is a Diagnosis Code and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when it is necessary to report an additional diagnosis and the preceding HI data elements have been used to report other diagnoses. If not required by this implementation guide, do not send.
Required
3-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
See element HI02-01 for a list of valid values.
CODE
DEFINITION
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
TQ
Systemized Nomenclature of Dentistry (SNODENT)
Use when reporting SNODENT Codes. This code set is not allowed for use under HIPAA at the time of this writing and can only be used:

If a new rule names the SNODENT codes as an allowable code set under HIPAA,
OR
Use when the Secretary of Health and Human Services grants an exception to use the code set as a pilot project.
CODE SOURCE: 135: American Dental Association
Required
3-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Diagnosis Code
Not Used
3-3
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Not Used
3-4
1251
Date Time Period
X 1
AN
1/35
Not Used
3-5
782
Monetary Amount
O 1
R
1/18
Not Used
3-6
380
Quantity
O 1
R
1/15
Not Used
3-7
799
Version Identifier
O 1
AN
1/30
Not Used
3-8
1271
Industry Code
X 1
AN
1/30
Not Used
3-9
1271
Industry Code
X 1
AN
1/30
Not Used
3-10
1271
Industry Code
O 1
AN
1/30
Situational
4
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
  7. C022-10 is the attribute of the code in C022-02 from the same code list.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported when C022-02 is a Diagnosis Code and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when it is necessary to report an additional diagnosis and the preceding HI data elements have been used to report other diagnoses. If not required by this implementation guide, do not send.
Required
4-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
See element HI02-01 for a list of valid values.
CODE
DEFINITION
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
TQ
Systemized Nomenclature of Dentistry (SNODENT)
Use when reporting SNODENT Codes. This code set is not allowed for use under HIPAA at the time of this writing and can only be used:

If a new rule names the SNODENT codes as an allowable code set under HIPAA,
OR
Use when the Secretary of Health and Human Services grants an exception to use the code set as a pilot project.
CODE SOURCE: 135: American Dental Association
Required
4-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Diagnosis Code
Not Used
4-3
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Not Used
4-4
1251
Date Time Period
X 1
AN
1/35
Not Used
4-5
782
Monetary Amount
O 1
R
1/18
Not Used
4-6
380
Quantity
O 1
R
1/15
Not Used
4-7
799
Version Identifier
O 1
AN
1/30
Not Used
4-8
1271
Industry Code
X 1
AN
1/30
Not Used
4-9
1271
Industry Code
X 1
AN
1/30
Not Used
4-10
1271
Industry Code
O 1
AN
1/30
Not Used
5
C022
Health Care Code Information
O 1
Not Used
6
C022
Health Care Code Information
O 1
Not Used
7
C022
Health Care Code Information
O 1
Not Used
8
C022
Health Care Code Information
O 1
Not Used
9
C022
Health Care Code Information
O 1
Not Used
10
C022
Health Care Code Information
O 1
Not Used
11
C022
Health Care Code Information
O 1
Not Used
12
C022
Health Care Code Information
O 1

HI - CONDITION INFORMATION

X12 Name:
Health Care Information Codes
X12 Purpose:
To supply information related to the delivery of health care
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when it is necessary to report Condition Codes for Workers' Compensation claims. If not required by this implementation guide, do not send.
TR3 Example:
HI✱BG:W3~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
C022
Health Care Code Information
M 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
  7. C022-10 is the attribute of the code in C022-02 from the same code list.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported when C022-02 is a Diagnosis Code and range of diagnosis codes were NOT given in C022-08.
Required
1-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
CODE
DEFINITION
BG
Condition
The allowed Condition Codes are for Workers' Compensation claims only and have been defined by the National Uniform Claim Committee on their website:
http://www.nucc.org
CODE SOURCE: 641: Condition Code List
Required
1-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Condition Code
Not Used
1-3
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Not Used
1-4
1251
Date Time Period
X 1
AN
1/35
Not Used
1-5
782
Monetary Amount
O 1
R
1/18
Not Used
1-6
380
Quantity
O 1
R
1/15
Not Used
1-7
799
Version Identifier
O 1
AN
1/30
Not Used
1-8
1271
Industry Code
X 1
AN
1/30
Not Used
1-9
1271
Industry Code
X 1
AN
1/30
Not Used
1-10
1271
Industry Code
O 1
AN
1/30
Situational
2
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
  7. C022-10 is the attribute of the code in C022-02 from the same code list.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported when C022-02 is a Diagnosis Code and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when it is necessary to report an additional condition code and the preceding HI data elements have been used to report other condition codes. If not required by this implementation guide, do not send.
Required
2-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
CODE
DEFINITION
BG
Condition
The allowed Condition Codes are for Workers' Compensation claims only and have been defined by the National Uniform Claim Committee on their website:
http://www.nucc.org
CODE SOURCE: 641: Condition Code List
Required
2-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Condition Code
Not Used
2-3
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Not Used
2-4
1251
Date Time Period
X 1
AN
1/35
Not Used
2-5
782
Monetary Amount
O 1
R
1/18
Not Used
2-6
380
Quantity
O 1
R
1/15
Not Used
2-7
799
Version Identifier
O 1
AN
1/30
Not Used
2-8
1271
Industry Code
X 1
AN
1/30
Not Used
2-9
1271
Industry Code
X 1
AN
1/30
Not Used
2-10
1271
Industry Code
O 1
AN
1/30
Situational
3
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
  7. C022-10 is the attribute of the code in C022-02 from the same code list.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported when C022-02 is a Diagnosis Code and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when it is necessary to report an additional condition code and the preceding HI data elements have been used to report other condition codes. If not required by this implementation guide, do not send.
Required
3-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
CODE
DEFINITION
BG
Condition
The allowed Condition Codes are for Workers' Compensation claims only and have been defined by the National Uniform Claim Committee on their website:
http://www.nucc.org
CODE SOURCE: 641: Condition Code List
Required
3-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Condition Code
Not Used
3-3
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Not Used
3-4
1251
Date Time Period
X 1
AN
1/35
Not Used
3-5
782
Monetary Amount
O 1
R
1/18
Not Used
3-6
380
Quantity
O 1
R
1/15
Not Used
3-7
799
Version Identifier
O 1
AN
1/30
Not Used
3-8
1271
Industry Code
X 1
AN
1/30
Not Used
3-9
1271
Industry Code
X 1
AN
1/30
Not Used
3-10
1271
Industry Code
O 1
AN
1/30
Situational
4
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
  7. C022-10 is the attribute of the code in C022-02 from the same code list.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported when C022-02 is a Diagnosis Code and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when it is necessary to report an additional condition code and the preceding HI data elements have been used to report other condition codes. If not required by this implementation guide, do not send.
Required
4-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
CODE
DEFINITION
BG
Condition
The allowed Condition Codes are for Workers' Compensation claims only and have been defined by the National Uniform Claim Committee on their website:
http://www.nucc.org
CODE SOURCE: 641: Condition Code List
Required
4-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Condition Code
Not Used
4-3
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Not Used
4-4
1251
Date Time Period
X 1
AN
1/35
Not Used
4-5
782
Monetary Amount
O 1
R
1/18
Not Used
4-6
380
Quantity
O 1
R
1/15
Not Used
4-7
799
Version Identifier
O 1
AN
1/30
Not Used
4-8
1271
Industry Code
X 1
AN
1/30
Not Used
4-9
1271
Industry Code
X 1
AN
1/30
Not Used
4-10
1271
Industry Code
O 1
AN
1/30
Not Used
5
C022
Health Care Code Information
O 1
Not Used
6
C022
Health Care Code Information
O 1
Not Used
7
C022
Health Care Code Information
O 1
Not Used
8
C022
Health Care Code Information
O 1
Not Used
9
C022
Health Care Code Information
O 1
Not Used
10
C022
Health Care Code Information
O 1
Not Used
11
C022
Health Care Code Information
O 1
Not Used
12
C022
Health Care Code Information
O 1

HCP - CLAIM PRICING/REPRICING INFORMATION

X12 Name:
Health Care Pricing
X12 Purpose:
To specify pricing or repricing information about a health care claim or line item
X12 Syntax:
  1. R0113
    At least one of HCP01 or HCP13 is required.
  2. P0910
    If either HCP09 or HCP10 is present, then the other is required.
  3. P1112
    If either HCP11 or HCP12 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when this information is deemed necessary by the repricer. If not required by this implementation guide, do not send.
TR3 Notes:
  1. This information is specific to the destination payer reported in Loop ID-2010BB.
  2. This segment is not completed by providers. The information is completed by repricers only.
TR3 Example:
HCP✱03✱100✱10✱RPO12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1473
Pricing Methodology Code
X 1
ID
2
Code specifying pricing methodology at which the claim or line item has been priced or repriced
SEGMENT SYNTAX: R0113
INDUSTRY NAME: Pricing Methodology
Specific code use is determined by Trading Partner Agreement due to the variances in contracting policies in the industry.
CODE
DEFINITION
00
Zero Pricing (Not Covered Under Contract)
01
Priced as Billed at 100%
02
Priced at the Standard Fee Schedule
03
Priced at a Contractual Percentage
04
Bundled Pricing
05
Peer Review Pricing
07
Flat Rate Pricing
08
Combination Pricing
09
Maternity Pricing
10
Other Pricing
11
Lower of Cost
12
Ratio of Cost
13
Cost Reimbursed
14
Adjustment Pricing
Required
2
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: HCP02 is the allowed amount.
INDUSTRY NAME: Repriced Allowed Amount
Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
Situational
3
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: HCP03 is the savings amount.
SITUATIONAL RULE: Required when this information is deemed necessary by the repricer. If not required by this implementation guide, do not send.
INDUSTRY NAME: Repriced Savings Amount
Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
Situational
4
127
Reference Identification
O 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: HCP04 is the repricing organization identification number.
SITUATIONAL RULE: Required when this information is deemed necessary by the repricer. If not required by this implementation guide, do not send.
INDUSTRY NAME: Repricing Organization Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Situational
5
118
Rate
O 1
R
1/9
Rate expressed in the standard monetary denomination for the currency specified
SEMANTIC: HCP05 is the pricing rate associated with per diem or flat rate repricing.
SITUATIONAL RULE: Required when this information is deemed necessary by the repricer. If not required by this implementation guide, do not send.
INDUSTRY NAME: Repricing Per Diem or Flat Rate Amount
Not Used
6
127
Reference Identification
O 1
AN
1/80
Not Used
7
782
Monetary Amount
O 1
R
1/18
Not Used
8
234
Product/Service ID
O 1
AN
1/80
Not Used
9
235
Product/Service ID Qualifier
X 1
ID
2
Not Used
10
234
Product/Service ID
X 1
AN
1/80
Not Used
11
355
Unit or Basis for Measurement Code
X 1
ID
2
Not Used
12
380
Quantity
X 1
R
1/15
Situational
13
901
Reject Reason Code
X 1
ID
2
Code identifying reason for rejection as assigned by issuer
SEMANTIC: HCP13 is the rejection message returned from the third party organization.
SEGMENT SYNTAX: R0113
SITUATIONAL RULE: Required when this information is deemed necessary by the repricer. If not required by this implementation guide, do not send.
CODE
DEFINITION
T1
Cannot Identify Provider as TPO (Third Party Organization) Participant
T6
Claim does not contain enough information for re-pricing
Situational
14
1526
Policy Compliance Code
O 1
ID
1/2
Code specifying policy compliance
SITUATIONAL RULE: Required when this information is deemed necessary by the repricer. If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Procedure Followed (Compliance)
2
Not Followed - Call Not Made (Non-Compliance Call Not Made)
3
Not Medically Necessary (Non-Compliance Non-Medically Necessary)
4
Not Followed Other (Non-Compliance Other)
5
Emergency Admit to Non-Network Hospital
Situational
15
1527
Exception Code
O 1
ID
1/2
Code specifying the exception reason for consideration of out-of-network health care services
SEMANTIC: HCP15 is the exception reason generated by a third party organization.
SITUATIONAL RULE: Required when this information is deemed necessary by the repricer. If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Non-Network Professional Provider in Network Hospital
2
Emergency Care
3
Services or Specialist not in Network
4
Out-of-Service Area
5
State Mandates
6
Other

NM1 - REFERRING PROVIDER NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Loop 2310 contains information about the claim level providers including, but not limited to: rendering, referring, and attending.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when this claim involves a referral. If not required by this implementation guide, do not send.
TR3 Notes:
  1. When there is only one referral on the claim, use code "DN - Referring Provider". When more than one referral exists and there is a requirement to report the additional referral, use code DN to indicate the referral received by the rendering provider on this claim. Use code "P3 - Primary Care Provider" to indicate the initial referral from the primary care provider, or whatever provider wrote the initial referral for this patient's episode of care being submitted in this transaction.
  2. See the NUCC website www.nucc.org for the definitions of professional providers.
TR3 Example:
NM1✱DN✱1✱WELBY✱MARCUS✱W✱✱JR✱XX✱1234567891~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
DN
Referring Provider
P3
Primary Care Provider
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Required
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Referring Provider Last Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Referring Provider First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when the Middle Name or Initial is known to the sender. If not required by this implementation guide, do not send.
INDUSTRY NAME: Referring Provider Middle Name or Initial
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when the Suffix is known to the sender. If not required by this implementation guide, do not send.
INDUSTRY NAME: Referring Provider Name Suffix
Situational
8
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when NM109 is used. If not required by this implementation guide, do not send.
CODE
DEFINITION
XX
Standard Unique Health Identifier for Health Care Providers (NPI)
CODE SOURCE: 537: National Provider Identifier (NPI)
Situational
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when the provider has received an NPI and the NPI is available to the submitter. If not required by this implementation guide, do not send.
INDUSTRY NAME: Referring Provider Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

REF*A6 - REFERRING PROVIDER SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when NM109 of this loop is not used and an identifier is necessary for the receiver to identify the provider. If not required by this implementation guide, do not send.
TR3 Example:
REF✱A6✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
A6
Provider Identifier
Use when reporting a proprietary provider number assigned by the destination payer identified in the Payer Name loop, Loop ID-2010BB, associated with this claim. This is true regardless of whether that payer is a government, private, commercial, or any other payer.
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Referring Provider Secondary Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

NM1*82 - RENDERING PROVIDER NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Loop 2310 contains information about the claim level providers including, but not limited to: rendering, referring, and attending.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when the Rendering Provider NM1 information is different than that carried in the Billing Provider loop (Loop ID-2010AA) and the Assistant Surgeon loop (Loop ID-2310D) is not used. If not required by this implementation guide, do not send.
TR3 Notes:
  1. Information in this Loop ID-2310 applies to the entire claim unless overridden on a service line by the presence of Loop ID-2420 with the same value in NM101.
  2. See the NUCC website www.nucc.org for the definitions of professional providers.
TR3 Example:
NM1✱82✱1✱DOE✱JANE✱C✱✱✱XX✱1234567804~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
82
Rendering Provider
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Required
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Rendering Provider Last Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Rendering Provider First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when NM102 = 1 (person) and the Middle Name or Initial is known to the sender. If not required by this implementation guide, do not send.
INDUSTRY NAME: Rendering Provider Middle Name or Initial
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when the Suffix is known to the sender. If not required by this implementation guide, do not send.
INDUSTRY NAME: Rendering Provider Name Suffix
Situational
8
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when NM109 is used. If not required by this implementation guide, do not send.
CODE
DEFINITION
XX
Standard Unique Health Identifier for Health Care Providers (NPI)
CODE SOURCE: 537: National Provider Identifier (NPI)
Situational
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required for providers in the United States or its territories when the provider is eligible to receive a National Provider Identifier (NPI).ORRequired for providers not in the United States or its territories when the provider has received an NPI. If not required by this implementation guide, do not send.
INDUSTRY NAME: Rendering Provider Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

PRV*PE - RENDERING PROVIDER SPECIALTY INFORMATION

X12 Name:
Provider Information
X12 Purpose:
To specify the identifying characteristics of a provider
X12 Syntax:
P0203
If either PRV02 or PRV03 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
The PRV segment in Loop ID-2310 applies to the entire claim unless overridden on the service line level by the presence of a PRV segment with the same value in PRV01.
TR3 Example:
PRV✱PE✱PXC✱1223G0001X~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1221
Provider Code
M 1
ID
1/3
Code identifying the type of provider
CODE
DEFINITION
PE
Performing
Required
2
128
Reference Identification Qualifier
X 1
ID
2/3
Code identifying the Reference Identification
SEGMENT SYNTAX: P0203
CODE
DEFINITION
PXC
Health Care Provider Taxonomy Code
CODE SOURCE: 682: Health Care Provider Taxonomy
Required
3
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: P0203
INDUSTRY NAME: Provider Taxonomy Code
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
4
156
State or Province Code
O 1
ID
2
Not Used
5
C035
Provider Specialty Information
O 1
Not Used
6
1223
Provider Organization Code
O 1
ID
3

REF - RENDERING PROVIDER SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
2
Situational Rule:
Required when NM109 of this loop is not used and an identifier is necessary for the receiver to identify the provider. If not required by this implementation guide, do not send.
TR3 Notes:
The REF segment in Loop ID-2310 applies to the entire claim unless overridden on the service line level by the presence of a REF segment with the same value in REF01.
TR3 Example:
REF✱A6✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
A6
Provider Identifier
Use when reporting a proprietary provider number assigned by the destination payer identified in the Payer Name loop, Loop ID-2010BB, associated with this claim. This is true regardless of whether that payer is a government, private, commercial, or any other payer.
LU
Location Number
Use when reporting the provider's location when different than the billing or service location.
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Rendering Provider Secondary Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

NM1*77 - SERVICE LOCATION NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Loop 2310 contains information about the claim level providers including, but not limited to: rendering, referring, and attending.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when the name and/or the address of Service Location is different than that carried in Loop ID-2010AA (Billing Provider)
AND
the Service Location is not a subpart of the Billing Provider with its own NPI that is different than the NPI reported in Loop ID-2010AA NM109. If not required by this implementation guide, do not send.
TR3 Notes:
  1. Information in this Loop ID-2310 applies to the entire claim unless overridden on a service line by the presence of Loop ID-2420 with the same value in NM101.
  2. When an organization health care provider's NPI is provided to identify the Service Location, the organization health care provider must be external to the entity identified as the Billing Provider (for example, reference lab). It is not permissible to report an organization health care provider NPI as the Service Location if the entity being identified is a component (for example, subpart) of the Billing Provider. In that case, the subpart must be the Billing Provider.
  3. The purpose of this loop is to identify specifically where the service was rendered.
TR3 Example:
NM1✱77✱2✱ABC CLINIC✱✱✱✱✱XX✱1234567891~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
77
Service Location
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
2
Non-Person Entity
Situational
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
SITUATIONAL RULE: Required when the Service Location is an organization health care provider who is external to the entity identified as the Billing Provider in Loop ID-2010AA. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Location Name
Not Used
4
1036
Name First
O 1
AN
1/35
Not Used
5
1037
Name Middle
O 1
AN
1/25
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Not Used
7
1039
Name Suffix
O 1
AN
1/10
Situational
8
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when NM109 is used. If not required by this implementation guide, do not send.
CODE
DEFINITION
XX
Standard Unique Health Identifier for Health Care Providers (NPI)
CODE SOURCE: 537: National Provider Identifier (NPI)
Situational
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when the service location to be identified has an NPI and is not a component or subpart of the Billing Provider entity.If not required by this implementation guide, do not send.
INDUSTRY NAME: Laboratory or Facility Primary Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

N3 - SERVICE LOCATION ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
If service location is in an area where there are no street addresses, enter a description of the location (for example, "crossroad of State Road 34 and 45" or "Exit near Mile marker 265 on Interstate 80").
TR3 Example:
N3✱123 MAIN STREET~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Service Location Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when a second address line is needed. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Location Address Line

N4 - SERVICE LOCATION CITY, STATE, ZIP CODE

X12 Name:
Geographic Location
X12 Purpose:
To specify the geographic place of the named party
X12 Syntax:
  1. E0207
    Only one of N402 or N407 may be present.
  2. E0308
    Only one of N403 or N408 may be present.
  3. C0605
    If N406 is present, then N405 is required.
  4. C0704
    If N407 is present, then N404 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
N4✱KANSAS CITY✱MO✱641051909~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
INDUSTRY NAME: Service Location City Name
Situational
2
156
State or Province Code
X 1
ID
2
Code specifying the Standard State/Province as defined by appropriate government agency
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Location State or Province Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
X 1
ID
3/15
Code specifying international postal zone code excluding punctuation and blanks (zip code for United States)
COMMENT: N403 contains the postal code in an unstructured format. N408 contains the postal code in a structured format. When a postal code data field is used, the parties shall agree as to which data element (N403 or N408) shall be used in the transaction set.
SEGMENT SYNTAX: E0308
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada, or when a postal code exists for the country in N404. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Location Postal Zone or ZIP Code
When reporting the ZIP code for U.S. addresses, the full nine digit ZIP code must be provided.
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
X 1
ID
2/3
Code identifying the country
SEGMENT SYNTAX: C0704
SITUATIONAL RULE: Required when the address is outside the United States of America. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Location Country Code
Use the alpha-2 country codes from Part 1 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
5
309
Location Qualifier
X 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
X 1
ID
1/3
Code identifying the country subdivision
SEGMENT SYNTAX: E0207, C0704
SITUATIONAL RULE: Required when the address is not in the United States of America, including its territories, or Canada, and the country in N404 has administrative subdivisions such as but not limited to states, provinces, cantons, etc. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Location Country Subdivision Code
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
8
1702
Postal Code-Formatted
X 1
AN
3/20

REF - SERVICE LOCATION SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
2
Situational Rule:
Required when NM109 of this loop is not used,
AND
the Billing Provider Loop ID-2010AA NM109 is not used,
AND
an identifier is necessary for the receiver to identify the provider.

If not required by this implementation guide, do not send.
TR3 Example:
REF✱A6✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
A6
Provider Identifier
Use when reporting a proprietary provider number assigned by the destination payer identified in the Payer Name loop, Loop ID-2010BB, associated with this claim. This is true regardless of whether that payer is a government, private, commercial, or any other payer.
LU
Location Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Service Location Secondary Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

NM1*DD - ASSISTANT SURGEON NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Loop 2310 contains information about the claim level providers including, but not limited to: rendering, referring, and attending.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when the Rendering Provider provided these services in the role of the Assisting Surgeon.
If not required by this implementation guide, do not send.
TR3 Notes:
Information in this Loop ID-2310 applies to the entire claim unless overridden on a service line by the presence of Loop ID-2420 with the same value in NM101.
TR3 Example:
NM1✱DD✱1✱SMITH✱JOHN✱S✱✱✱XX✱1234567890~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
DD
Assistant Surgeon
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Required
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Assistant Surgeon Last Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Assistant Surgeon First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when the Middle Name or Initial is known to the sender. If not required by this implementation guide, do not send.
INDUSTRY NAME: Assistant Surgeon Middle Name or Initial
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when the Suffix is known to the sender. If not required by this implementation guide, do not send.
INDUSTRY NAME: Assistant Surgeon Name Suffix
Examples: I, II, III, IV, Jr, Sr
This data element is used only to indicate generation or patronymic.
Situational
8
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when NM109 is used. If not required by this implementation guide, do not send.
CODE
DEFINITION
XX
Standard Unique Health Identifier for Health Care Providers (NPI)
CODE SOURCE: 537: National Provider Identifier (NPI)
Situational
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required for providers in the United States or its territories when the provider is eligible to receive a National Provider Identifier (NPI).ORRequired for providers not in the United States or its territories when the provider has received an NPI. If not required by this implementation guide, do not send.
INDUSTRY NAME: Assistant Surgeon Primary Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

PRV*AS - ASSISTANT SURGEON SPECIALTY INFORMATION

X12 Name:
Provider Information
X12 Purpose:
To specify the identifying characteristics of a provider
X12 Syntax:
P0203
If either PRV02 or PRV03 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
Information in this Loop ID-2310 applies to the entire claim unless overridden on a service line by the presence of Loop ID-2420 with the same value in NM101.
TR3 Example:
PRV✱AS✱PXC✱1223S0112X~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1221
Provider Code
M 1
ID
1/3
Code identifying the type of provider
CODE
DEFINITION
AS
Assistant Surgeon
Required
2
128
Reference Identification Qualifier
X 1
ID
2/3
Code identifying the Reference Identification
SEGMENT SYNTAX: P0203
CODE
DEFINITION
PXC
Health Care Provider Taxonomy Code
CODE SOURCE: 682: Health Care Provider Taxonomy
Required
3
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: P0203
INDUSTRY NAME: Provider Taxonomy Code
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
4
156
State or Province Code
O 1
ID
2
Not Used
5
C035
Provider Specialty Information
O 1
Not Used
6
1223
Provider Organization Code
O 1
ID
3

REF - ASSISTANT SURGEON SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
2
Situational Rule:
Required when NM109 of this loop is not used and an identifier is necessary for the receiver to identify the provider. If not required by this implementation guide, do not send.
TR3 Example:
REF✱A6✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
A6
Provider Identifier
Use when reporting a proprietary provider number assigned by the destination payer identified in the Payer Name loop, Loop ID-2010BB, associated with this claim. This is true regardless of whether that payer is a government, private, commercial, or any other payer.
LU
Location Number
Use when reporting the provider's location when different than the billing or service location.
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Assistant Surgeon Secondary Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

NM1*DQ - SUPERVISING PROVIDER NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Loop 2310 contains information about the claim level providers including, but not limited to: rendering, referring, and attending.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when the rendering provider is supervised by a physician or dentist. If not required by this implementation guide, do not send.
TR3 Notes:
  1. Information in this Loop ID-2310 applies to the entire claim unless overridden on a service line by the presence of Loop ID-2420 with the same value in NM101.
  2. See the NUCC website www.nucc.org for the definitions of professional providers.
TR3 Example:
NM1✱DQ✱1✱SMITH✱JOHN✱S✱✱✱XX✱1234567890~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
DQ
Supervising Physician
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Required
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Supervising Provider Last Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Supervising Provider First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when the Middle Name or Initial is known to the sender. If not required by this implementation guide, do not send.
INDUSTRY NAME: Supervising Provider Middle Name or Initial
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when the Suffix is known to the sender. If not required by this implementation guide, do not send.
INDUSTRY NAME: Supervising Provider Name Suffix
Situational
8
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when NM109 is used. If not required by this implementation guide, do not send.
CODE
DEFINITION
XX
Standard Unique Health Identifier for Health Care Providers (NPI)
CODE SOURCE: 537: National Provider Identifier (NPI)
Situational
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required for providers in the United States or its territories when the provider is eligible to receive a National Provider Identifier (NPI).ORRequired for providers not in the United States or its territories when the provider has received an NPI. If not required by this implementation guide, do not send.
INDUSTRY NAME: Supervising Provider Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

REF*A6 - SUPERVISING PROVIDER SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
X12 Set Notes:
NOTE: Loop 2310 contains information about the claim level providers including, but not limited to: rendering, referring, and attending.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when NM109 of this loop is not used and an identifier is necessary for the receiver to identify the provider. If not required by this implementation guide, do not send.
TR3 Notes:
The REF segment in Loop ID-2310 applies to the entire claim unless overridden on the service line level by the presence of a REF segment with the same value in REF01.
TR3 Example:
REF✱A6✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
A6
Provider Identifier
Use when reporting a proprietary provider number by the non-destination payer identified in the Other Payer Name Loop ID-2330B for this iteration of Loop ID-2320. This is true regardless of whether that payer is a government, private, commercial, or any other payer.
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

SBR - OTHER SUBSCRIBER INFORMATION

X12 Name:
Subscriber Information
X12 Purpose:
To record information specific to the primary insured and the insurance carrier for that insured
X12 Set Notes:
NOTE: Loop 2320 contains insurance information about: paying and other Insurance Carriers for that Subscriber, Subscriber of the Other Insurance Carriers, School or Employer Information for that Subscriber.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when other payers are known to potentially be involved in paying on this claim. If not required by this implementation guide, do not send.
TR3 Notes:
  1. All information contained in Loop ID-2320 applies only to the payer identified in Loop ID-2330B of this iteration of Loop ID-2320. If information for an additional payer is necessary, repeat Loop ID-2320 with its respective 2330 Loops.
  2. See Section 1.4.2 for more information on Coordination of Benefits.
TR3 Example:
SBR✱S✱01✱GR00786✱✱✱✱✱✱13~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1138
Payer Responsibility Sequence Number Code
M 1
ID
1
Code identifying the insurance carrier's level of responsibility for a payment of a claim
INDUSTRY NAME: Other Payer Responsibility Sequence Code
  1. Within a given claim, the various values for the Payer Responsibility Sequence Number Code (other than value "U") may occur no more than once.
  2. When sending Line Adjudication Information for this payer, the identifier sent in SVD01 (Other Payer Responsibility Sequence Code) of Loop ID-2430 (Line Adjudication Information) must match this value when used.
  3. This code value identifies, in the opinion of the submitter, the relative adjudication order of the non-destination payer in this iteration of Loop ID-2320 among all of the payers identified in this claim.
CODE
DEFINITION
A
Payer Responsibility Four
B
Payer Responsibility Five
C
Payer Responsibility Six
D
Payer Responsibility Seven
E
Payer Responsibility Eight
F
Payer Responsibility Nine
G
Payer Responsibility Ten
H
Payer Responsibility Eleven
P
Primary
S
Secondary
T
Tertiary
U
Unknown
Use when sending payer to payer COB claims and the original payer determined the presence of this coverage from eligibility files received from this payer

OR

Use when the original claim did not provide the responsibility sequence for this payer.
Required
2
1069
Individual Relationship Code
O 1
ID
2
Code indicating the relationship between two individuals or entities
SEMANTIC: SBR02 specifies the relationship to the person insured.
CODE
DEFINITION
01
Spouse
18
Self
19
Child
20
Employee
21
Unknown
39
Organ Donor
40
Cadaver Donor
53
Life Partner
G8
Other Relationship
Situational
3
127
Reference Identification
O 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: SBR03 is policy or group number.
SITUATIONAL RULE: Required when the subscriber's identification card shows a group number.ORRequired when the subscriber's group number is otherwise gathered (e.g. eligibility inquiry).If not required by this implementation guide, do not send.
INDUSTRY NAME: Insured Group or Policy Number
  1. This is not the number uniquely identifying the subscriber. The unique subscriber number is submitted in Loop 2330A-NM109 for this iteration of Loop ID-2320.
  2. Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Situational
4
93
Name
O 1
AN
1/60
Free-form name
SEMANTIC: SBR04 is plan name.
SITUATIONAL RULE: Required when the subscriber's identification card shows a group name.ORRequired when the subscriber's group name is otherwise gathered (e.g. eligibility inquiry). If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver.
INDUSTRY NAME: Other Insured Group Name
Not Used
5
1336
Insurance Type Code
O 1
ID
1/3
Not Used
6
1143
Coordination of Benefits Code
O 1
ID
1
Not Used
7
1073
Yes/No Condition or Response Code
O 1
ID
1
Not Used
8
584
Employment Status Code
O 1
ID
2
Required
9
1032
Claim Filing Indicator Code
O 1
ID
1/2
Code identifying type of claim
CODE
DEFINITION
11
Other Non-Federal Programs
12
Preferred Provider Organization (PPO)
13
Point of Service (POS)
14
Exclusive Provider Organization (EPO)
15
Indemnity Insurance
16
Health Maintenance Organization (HMO) Medicare Risk
17
Dental Maintenance Organization
AM
Automobile Medical
BL
Blue Cross/Blue Shield
CH
Champus
Use when submitting Champus or Tricare claims.
CI
Commercial Insurance Co.
DS
Disability
FI
Federal Employees Program
HM
Health Maintenance Organization
LM
Liability Medical
MA
Medicare Part A
MB
Medicare Part B
MC
Medicaid
MD
Medicare Part D
ME
Medicare Advantage Plan
TV
Title V
UK
Unknown
VA
Veterans Affairs Plan
WC
Workers' Compensation Health Claim
ZZ
Mutually Defined
Use when no other code value applies.
Not Used
10
1732
Source of Payment Typology Code
O 1
ID
2/6

RAS - CLAIM ADJUSTMENT INFORMATION

X12 Name:
Reason Adjustment
X12 Purpose:
To supply Claim Adjustment Reason Codes and amounts as needed for an entire claim or for a particular service within the claim being paid
X12 Comments:
Adjustment information is intended to help the provider balance the remittance information. Adjustment amounts must fully explain the difference between submitted charges and the amount paid.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
99
Situational Rule:
Required when the payer identified in Other Payer Name (Loop ID-2330B) made claim level adjustments to the dollar amount charged. If not required by this implementation guide, do not send.
TR3 Notes:
See Section 1.4.5, Balancing, for additional information.
TR3 Example:
RAS✱125.32✱PR✱1~RAS✱25✱PR✱3~RAS✱200✱CO✱6^7~RAS✱500✱CO✱45:HE:MA01~RAS✱1225✱CO✱16:HE:M24^15:HE:N517~RAS✱2225✱CO✱16:HE:M44:M45:M49^146:HE:MA63:MA65~RAS✱2100✱OA✱18:HE:N522:N702~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
782
Monetary Amount
M 1
R
1/18
Monetary amount
SEMANTIC: RAS01 is the amount of adjustment.
INDUSTRY NAME: Adjustment Amount
  1. This monetary amount is the adjustment amount. A negative amount increases the payment, and a positive amount decreases the payment. This amount must not be zero (0).
  2. Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
Required
2
1785
Claim Adjustment Group Code
M 1
AN
1/10
Code identifying the general category of payment adjustment.
CODE SOURCE 974: Claim Adjustment Group Codes
Required
3
C058
Adjustment Reason
M 15
To provide a reason and related explanation for a Health Care Claim or Service change in payment versus the original submitted charges
SEMANTIC: Position of data in the repeating composite data element conveys no significance.
X12 COMPOSITE SYNTAX NOTES:
  1. P0203
    If either C05802 or C05803 is present, then the other is required.
  2. C0403
    If C05804 is present, then C05803 is required.
  3. C0504
    If C05805 is present, then C05804 is required.
  4. C0605
    If C05806 is present, then C05805 is required.
  5. C0706
    If C05807 is present, then C05806 is required.
X12 COMPOSITE SEMANTIC NOTES: C05802 qualifies C05803, C05804, C05805, C05806 and C05807.
  1. More than one iteration of this composite may only be provided when the entire claim submitted charge is being adjusted by this RAS segment and there are multiple adjustment reasons that are each applicable for the adjustment of that full amount in RAS01.
  2. This composite identifies the reason for the adjustment of the dollar amount identified in RAS01.
Required
3-1
1034
Claim Adjustment Reason Code
M 1
ID
1/5
Code identifying the detailed reason the adjustment was made
INDUSTRY NAME: Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Situational
3-2
1270
Code List Qualifier Code
X 1
ID
1/3
Code identifying a specific industry code list
COMPOSITE SYNTAX: P0203
SITUATIONAL RULE: Required when the payer identified in Other Payer Name Loop ID-2330B reported a remark code associated with this claim adjustment reason code in the remittance advice. If not required by this implementation guide, do not send.
CODE
DEFINITION
HE
Remittance Advice Remark Code
CODE SOURCE: 411: Remittance Advice Remark Code
RM
Insurance Industry Specific Remark Codes
CODE SOURCE: 973: Insurance Industry Specific Remark Codes
Situational
3-3
1271
Industry Code
X 1
AN
1/30
Code indicating a code from a specific industry code list
COMPOSITE SYNTAX: P0203, C0403
SITUATIONAL RULE: Required when the payer identified in Other Payer Name Loop ID-2330B reported a remark code associated with this claim adjustment reason code in the remittance advice. If not required by this implementation guide, do not send.
INDUSTRY NAME: Remark Code
Situational
3-4
1271
Industry Code
X 1
AN
1/30
Code indicating a code from a specific industry code list
COMPOSITE SYNTAX: C0403, C0504
SITUATIONAL RULE: Required when the payer identified in Other Payer Name Loop ID-2330B reported a remark code associated with this claim adjustment reason code in the remittance advice. If not required by this implementation guide, do not send.
INDUSTRY NAME: Remark Code
Situational
3-5
1271
Industry Code
X 1
AN
1/30
Code indicating a code from a specific industry code list
COMPOSITE SYNTAX: C0504, C0605
SITUATIONAL RULE: Required when the payer identified in Other Payer Name Loop ID-2330B reported a remark code associated with this claim adjustment reason code in the remittance advice. If not required by this implementation guide, do not send.
INDUSTRY NAME: Remark Code
Situational
3-6
1271
Industry Code
X 1
AN
1/30
Code indicating a code from a specific industry code list
COMPOSITE SYNTAX: C0605, C0706
SITUATIONAL RULE: Required when the payer identified in Other Payer Name Loop ID-2330B reported a remark code associated with this claim adjustment reason code in the remittance advice. If not required by this implementation guide, do not send.
INDUSTRY NAME: Remark Code
Situational
3-7
1271
Industry Code
O 1
AN
1/30
Code indicating a code from a specific industry code list
COMPOSITE SYNTAX: C0706
SITUATIONAL RULE: Required when the payer identified in Other Payer Name Loop ID-2330B reported a remark code associated with this claim adjustment reason code in the remittance advice. If not required by this implementation guide, do not send.
INDUSTRY NAME: Remark Code
Not Used
4
380
Quantity
O 1
R
1/15

AMT*D - COORDINATION OF BENEFITS (COB) PAYER PAID AMOUNT

X12 Name:
Monetary Amount Information
X12 Purpose:
To indicate the total monetary amount
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the claim has been adjudicated by the payer identified in Loop ID-2330B of this loop.

OR

Required when Loop ID-2010AC is present.

If not required by this implementation guide, do not send.
TR3 Notes:
When Loop 2010AC is a Medicaid Agency, this amount represents the maximum amount of liability the Medicaid agency is requesting to recover by submitting the subrogation claim.
TR3 Example:
AMT✱D✱411~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
522
Amount Qualifier Code
M 1
ID
1/3
Code specifying the amount qualifier
CODE
DEFINITION
D
Payor Amount Paid
Required
2
782
Monetary Amount
M 1
R
1/18
Monetary amount
INDUSTRY NAME: Payer Paid Amount
  1. It is acceptable to show "0" as the amount paid.
  2. Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
Not Used
3
478
Credit/Debit Flag Code
O 1
ID
1

AMT*B6 - CLAIM ALLOWED AMOUNT

X12 Name:
Monetary Amount Information
X12 Purpose:
To indicate the total monetary amount
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when submitting a Coordination of Benefits (COB) claim, and the Other Payer identified in Loop ID- 2330B of this iteration of Loop ID-2320 has adjudicated this claim and provided the 835 with only claim level allowed amount information.

OR

Required when submitting a Coordination of Benefits (COB) claim, and the Other Payer identified in Loop ID-2330B of this iteration of Loop ID- 2320 has adjudicated this claim and the payer issued a paper, virtual, or other alternate format of remittance advice with the allowed amount reported and the submitter does not have the ability to report line item information.

OR

Required when submitting a Coordination of Benefits (COB) claim, and the Other Payer identified in Loop ID-2330B of this iteration of Loop ID- 2320 is the same as the submitter reported in Loop ID-1000A. If not required by this implementation guide, do not send.
TR3 Notes:
  1. This is Loop ID-2100 Claim Allowed Amount (AMT02) when reported on an 835.
  2. This is the total claim allowed amount when remittance information is reported using other formats.
  3. In situations other than payer to payer COB, this amount is not sent if it is not explicitly available on an 835 or other remittance. If the allowed amount is not available, do not calculate the amount.
  4. When the Claim Allowed Amount is zero dollars, report zero (0).
TR3 Example:
AMT✱B6✱425~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
522
Amount Qualifier Code
M 1
ID
1/3
Code specifying the amount qualifier
CODE
DEFINITION
B6
Allowed - Actual
Required
2
782
Monetary Amount
M 1
R
1/18
Monetary amount
INDUSTRY NAME: Claim Allowed Amount
Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
Not Used
3
478
Credit/Debit Flag Code
O 1
ID
1

AMT*EAF - REMAINING PATIENT LIABILITY AMOUNT

X12 Name:
Monetary Amount Information
X12 Purpose:
To indicate the total monetary amount
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the claim is submitted by the provider and the Other Payer identified in Loop ID-2330B of this iteration of Loop ID-2320 has adjudicated this claim, and provided claim level information only,

AND

In the provider's opinion, the amount billable to the patient, is different than the sum of the amounts (RAS01) associated with Patient Responsibility (PR) Claim Adjustment Group Code (RAS02) in this 2320 loop. If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver.
TR3 Notes:
  1. In the judgment of the provider, this is the remaining amount to be paid after adjudication by the Other Payer identified in Loop ID-2330B of this iteration of Loop ID-2320. The amount reported here may, or may not, equal the sum of the amounts reported as Patient Responsibility (PR) in the RAS segments.
  2. This segment is not used in Payer-to-Payer Coordination of Benefits (COB).
  3. This segment is not used if the line level (Loop ID-2430) Remaining Patient Liability AMT segment is used for this Other Payer.
TR3 Example:
AMT✱EAF✱75~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
522
Amount Qualifier Code
M 1
ID
1/3
Code specifying the amount qualifier
CODE
DEFINITION
EAF
Amount Owed
Required
2
782
Monetary Amount
M 1
R
1/18
Monetary amount
INDUSTRY NAME: Remaining Patient Liability
Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
Not Used
3
478
Credit/Debit Flag Code
O 1
ID
1

AMT*A8 - COORDINATION OF BENEFITS (COB) TOTAL NON-COVERED AMOUNT

X12 Name:
Monetary Amount Information
X12 Purpose:
To indicate the total monetary amount
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the destination payer's cost avoidance policy allows providers to bypass claim submission to the payer identified in the Other Payer Loop ID-2330B of this iteration of Loop ID-2320. If not required by this implementation guide, do not send.
TR3 Notes:
When this segment is used, the amount reported in AMT02 must equal the total claim charge amount reported in CLM02. Neither the prior payer paid AMT, nor any RAS segments are used as this claim has not been adjudicated by this payer.
TR3 Example:
AMT✱A8✱273~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
522
Amount Qualifier Code
M 1
ID
1/3
Code specifying the amount qualifier
CODE
DEFINITION
A8
Noncovered Charges - Actual
Required
2
782
Monetary Amount
M 1
R
1/18
Monetary amount
INDUSTRY NAME: Non-Covered Charge Amount
Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
Not Used
3
478
Credit/Debit Flag Code
O 1
ID
1

OI - OTHER INSURANCE COVERAGE INFORMATION

X12 Name:
Other Health Insurance Information
X12 Purpose:
To specify information associated with other health insurance coverage
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
All information contained in the OI segment applies only to the payer identified in Loop ID-2330B of this iteration of Loop ID-2320.
TR3 Example:
OI✱✱✱✱✱✱✱A✱N✱✱N~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Not Used
1
1032
Claim Filing Indicator Code
O 1
ID
1/2
Not Used
2
1383
Claim Submission Reason Code
O 1
ID
2
Not Used
3
1073
Yes/No Condition or Response Code
O 1
ID
1
Not Used
4
1351
Patient Signature Source Code
O 1
ID
1
Not Used
5
1360
Provider Agreement Code
O 1
ID
1
Not Used
6
1363
Release of Information Code
O 1
ID
1
Situational
7
1359
Provider Accept Assignment Code
O 1
ID
1
Code indicating whether the provider accepts assignment
SITUATIONAL RULE: Required when the other payer reported in this 2320 loop is Medicare, including Medicare Fee For Service (FFS) or a Medicare Advantage Plan (Medicare Part C). If not required by this implementation guide, do not send.
INDUSTRY NAME: Medicare Assignment Code
For payer to payer COB claims, this code indicates how the claim was adjudicated by the previous payer, which may be different than the assignment/participation indicator submitted on the original claim.
CODE
DEFINITION
A
Assigned
Use when the claim was processed as assigned.
B
Assignment Accepted on Clinical Lab Services Only
Use when the claim was processed as assigned.
C
Not Assigned
Use when the claim was processed as non-assigned.
Situational
8
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: OI08 is payer-to-payer adjustment code. A "Y" value indicates a payer-to-payer COB claim is an adjustment. An "N" value indicates payer-to-payer COB claim is not an adjustment.
SITUATIONAL RULE: Required when the claim is for payer to payer COB. If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Payer Claim Adjustment Indicator
CODE
DEFINITION
N
No
Y
Yes
Not Used
9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
10
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: OI10 is payer-to-payer void code. A "Y" value indicates a payer-to-payer COB claim is a void. An "N" value indicates payer-to-payer COB claim is not a void.
SITUATIONAL RULE: Required when the claim is for payer to payer COB. If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Payer Voided Claim Indicator
CODE
DEFINITION
N
No
Y
Yes
Not Used
11
1073
Yes/No Condition or Response Code
O 1
ID
1

MOA - OUTPATIENT ADJUDICATION INFORMATION

X12 Name:
Outpatient Adjudication
X12 Purpose:
To provide claim level data related to the adjudication of outpatient claims
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when outpatient adjudication information is reported in the remittance advice. If not required by this implementation guide, do not send.
TR3 Example:
MOA✱50✱100~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Situational
1
954
Percentage as Decimal
O 1
R
1/10
Percentage expressed as a decimal (e.g., 0.0 through 1.0 represents 0% through 100%)
SEMANTIC: MOA01 is the reimbursement rate.
SITUATIONAL RULE: Required when returned in the remittance advice. If not required by this implementation guide, do not send.
INDUSTRY NAME: Reimbursement Rate
Situational
2
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: MOA02 is the claim Healthcare Common Procedure Coding System (HCPCS) payable amount.
SITUATIONAL RULE: Required when returned in the remittance advice. If not required by this implementation guide, do not send.
INDUSTRY NAME: HCPCS Payable Amount
Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
Not Used
3
127
Reference Identification
O 1
AN
1/80
Not Used
4
127
Reference Identification
O 1
AN
1/80
Not Used
5
127
Reference Identification
O 1
AN
1/80
Not Used
6
127
Reference Identification
O 1
AN
1/80
Not Used
7
127
Reference Identification
O 1
AN
1/80
Not Used
8
782
Monetary Amount
O 1
R
1/18
Situational
9
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: MOA09 is the professional component amount billed but not payable.
SITUATIONAL RULE: Required when returned in the remittance advice. If not required by this implementation guide, do not send.
INDUSTRY NAME: Non-Payable Professional Component Billed Amount
Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.

LQ - HEALTH CARE REMARK CODES

X12 Name:
Industry Code Identification
X12 Purpose:
To identify standard industry codes
X12 Syntax:
C0102
If LQ01 is present, then LQ02 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
99
Situational Rule:
Required when it is necessary to report claim level remark codes that are not associated with a claim adjustment reason code in a RAS Segment in this Loop ID 2320. If not required by this implementation guide, do not send.
TR3 Notes:
Remark codes from paper remittance advice that are not associated with a claim adjustment reason code in the RAS Segment are reported in this segment.
TR3 Example:
LQ✱HE✱MA15~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1270
Code List Qualifier Code
O 1
ID
1/3
Code identifying a specific industry code list
SEGMENT SYNTAX: C0102
CODE
DEFINITION
HE
Remittance Advice Remark Code
CODE SOURCE: 411: Remittance Advice Remark Code
RM
Insurance Industry Specific Remark Codes
CODE SOURCE: 973: Insurance Industry Specific Remark Codes
RX
National Council for Prescription Drug Programs Reject Codes
CODE SOURCE: 530: National Council for Prescription Drug Programs Reject Codes
Required
2
1271
Industry Code
X 1
AN
1/30
Code indicating a code from a specific industry code list
SEGMENT SYNTAX: C0102
INDUSTRY NAME: Remark Code

NM1*IL - OTHER SUBSCRIBER NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Segments NM1-N4 contain name and address information of the insurance carriers referenced in loop 2320.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
  1. If a patient can be uniquely identified by the Other Payer reported in Loop ID-2330B by a unique Member Identification Number, then the patient is reported in the subscriber loop.
  2. See Section 1.4.2 for more information on Coordination of Benefits.
TR3 Example:
NM1✱IL✱1✱DOE✱JOHN✱T✱✱JR✱MI✱123456~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
IL
Insured or Subscriber
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
2
Non-Person Entity
Required
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Other Subscriber Last Name or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Subscriber First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when NM102 = 1 (person) and the Middle Name or Initial is known to the sender. If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Subscriber Middle Name or Initial
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when NM102 = 1 (person) and the Suffix is known to the sender. If not required by this implementation guide do not send.
INDUSTRY NAME: Other Subscriber Name Suffix
Required
8
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
CODE
DEFINITION
II
Standard Unique Health Identifier for each Individual in the United States
Use when reporting the HIPAA Individual Patient Identifier.
MI
Member Identification Number
Use when indicating the subscriber's identification number as assigned by the payer.
Required
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
INDUSTRY NAME: Other Subscriber Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

N3 - OTHER SUBSCRIBER ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the information is available. If not required by this implementation guide, do not send.
TR3 Example:
N3✱123 MAIN STREET~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Other Subscriber Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when a second address line is needed. If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Subscriber Address Line

N4 - OTHER SUBSCRIBER CITY, STATE, ZIP CODE

X12 Name:
Geographic Location
X12 Purpose:
To specify the geographic place of the named party
X12 Syntax:
  1. E0207
    Only one of N402 or N407 may be present.
  2. E0308
    Only one of N403 or N408 may be present.
  3. C0605
    If N406 is present, then N405 is required.
  4. C0704
    If N407 is present, then N404 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the information is available and Loop ID-2330A N3 Segment is sent in this iteration of Loop ID-2320. If not required by this implementation guide, do not send.
TR3 Example:
N4✱KANSAS CITY✱MO✱64108~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
INDUSTRY NAME: Other Subscriber City Name
Situational
2
156
State or Province Code
X 1
ID
2
Code specifying the Standard State/Province as defined by appropriate government agency
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Subscriber State or Province Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
X 1
ID
3/15
Code specifying international postal zone code excluding punctuation and blanks (zip code for United States)
COMMENT: N403 contains the postal code in an unstructured format. N408 contains the postal code in a structured format. When a postal code data field is used, the parties shall agree as to which data element (N403 or N408) shall be used in the transaction set.
SEGMENT SYNTAX: E0308
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada, or when a postal code exists for the country in N404. If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Subscriber Postal Zone or ZIP Code
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
X 1
ID
2/3
Code identifying the country
SEGMENT SYNTAX: C0704
SITUATIONAL RULE: Required when the address is outside the United States of America. If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Subscriber Country Code
Use the alpha-2 country codes from Part 1 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
5
309
Location Qualifier
X 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
X 1
ID
1/3
Code identifying the country subdivision
SEGMENT SYNTAX: E0207, C0704
SITUATIONAL RULE: Required when the address is not in the United States of America, including its territories, or Canada, and the country in N404 has administrative subdivisions such as but not limited to states, provinces, cantons, etc. If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Subscriber Country Subdivision Code
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
8
1702
Postal Code-Formatted
X 1
AN
3/20

REF*SY - OTHER SUBSCRIBER SOCIAL SECURITY NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when an additional identification number to that provided in NM109 of this loop is necessary for the claim processor to identify the entity. If not required by this implementation guide, do not send.
TR3 Example:
REF✱EJ✱660415~REF✱SY✱123456789~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
SY
Social Security Number
Use when reporting a Social Security Number.

The Social Security Number must be a string of exactly nine numbers with no separators.

For example, sending "111002222" would be valid, while sending "111-00-2222" would be invalid.
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Other Subscriber Social Security Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

NM1*PR - OTHER PAYER NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Segments NM1-N4 contain name and address information of the insurance carriers referenced in loop 2320.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
See Section 1.4.2 for more information on Coordination of Benefits.
TR3 Example:
NM1✱PR✱2✱ABC INSURANCE CO✱✱✱✱✱XV✱11122333~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
PR
Payer
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
2
Non-Person Entity
Required
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Other Payer Organization Name
Not Used
4
1036
Name First
O 1
AN
1/35
Not Used
5
1037
Name Middle
O 1
AN
1/25
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Not Used
7
1039
Name Suffix
O 1
AN
1/10
Situational
8
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when NM109 is used. If not required by this implementation guide, do not send.
CODE
DEFINITION
XV
Standard Unique Health Plan Identifier (HPID)
CODE SOURCE: 540: Health Plan Identifier (HPID)
Situational
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when reporting the Health Plan ID (HPID) or Other Entity Identifier (OEID). If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Payer Primary Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

N3 - OTHER PAYER ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the payer address is available. If not required by this implementation guide, do not send.
TR3 Example:
N3✱123 MAIN STREET~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Other Payer Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when a second address line is needed. If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Payer Address Line

N4 - OTHER PAYER CITY, STATE, ZIP CODE

X12 Name:
Geographic Location
X12 Purpose:
To specify the geographic place of the named party
X12 Syntax:
  1. E0207
    Only one of N402 or N407 may be present.
  2. E0308
    Only one of N403 or N408 may be present.
  3. C0605
    If N406 is present, then N405 is required.
  4. C0704
    If N407 is present, then N404 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the payer address is available. If not required by this implementation guide, do not send.
TR3 Example:
N4✱KANSAS CITY✱MO✱64108~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
INDUSTRY NAME: Other Payer City Name
Situational
2
156
State or Province Code
X 1
ID
2
Code specifying the Standard State/Province as defined by appropriate government agency
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Payer State or Province Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
X 1
ID
3/15
Code specifying international postal zone code excluding punctuation and blanks (zip code for United States)
COMMENT: N403 contains the postal code in an unstructured format. N408 contains the postal code in a structured format. When a postal code data field is used, the parties shall agree as to which data element (N403 or N408) shall be used in the transaction set.
SEGMENT SYNTAX: E0308
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada, or when a postal code exists for the country in N404. If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Payer Postal Zone or ZIP Code
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
X 1
ID
2/3
Code identifying the country
SEGMENT SYNTAX: C0704
SITUATIONAL RULE: Required when the address is outside the United States of America. If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Payer Country Code
Use the alpha-2 country codes from Part 1 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
5
309
Location Qualifier
X 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
X 1
ID
1/3
Code identifying the country subdivision
SEGMENT SYNTAX: E0207, C0704
SITUATIONAL RULE: Required when the address is not in the United States of America, including its territories, or Canada, and the country in N404 has administrative subdivisions such as but not limited to states, provinces, cantons, etc. If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Payer Country Subdivision Code
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
8
1702
Postal Code-Formatted
X 1
AN
3/20

DTP*573 - PAYMENT EFFECTIVE DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the payer identified in this loop has previously adjudicated the claim and Loop ID-2430, Payment Effective Date, is not used. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱573✱D8✱20221030~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
573
Date Claim Paid
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Payment Effective Date

REF*2U - OTHER PAYER SECONDARY IDENTIFIER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when NM109 of this loop is not used.
OR
Required when an additional identification number to that provided in the NM109 of this loop is necessary to identify the entity.
If not required by this implementation guide, do not send.
TR3 Example:
REF✱2U✱98765~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
2U
Payer Identification Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Other Payer Secondary Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*G1 - OTHER PAYER PRIOR AUTHORIZATION NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the payer identified in this loop has assigned a prior authorization number and the prior authorization applies to the entire claim. If not required by this implementation guide, do not send.
TR3 Notes:
  1. This segment must not be used to report the Predetermination of Benefits Identification Number.
  2. When prior authorization is submitted at this level (Loop ID-2330B) it applies to all the service lines that do not have an overriding REF - Prior Authorization (Loop ID-2400).
TR3 Example:
REF✱G1✱13579~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
G1
Prior Authorization Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Other Payer Prior Authorization Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*9F - OTHER PAYER REFERRAL NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the payer identified in this loop has assigned a referral number to this claim.
If not required by this implementation guide, do not send.
TR3 Example:
REF✱9F✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
9F
Referral Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Other Payer Referral Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*G3 - OTHER PAYER PREDETERMINATION IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the payer identified in this loop has assigned a predetermination identification number to this claim.
If not required by this implementation guide, do not send.
TR3 Example:
REF✱G3✱13579~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
G3
Predetermination of Benefits Identification Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Other Payer Predetermination of Benefits Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*F8 - OTHER PAYER CLAIM CONTROL NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when this is a payer-to-payer COB claim.

OR

Required when the Other Payer's Claim Control Number is available. If not required by this implementation guide, do not send.
TR3 Example:
REF✱F8✱R555588~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
F8
Original Reference Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Other Payer's Claim Control Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*1K - OTHER PAYER PREVIOUS CLAIM CONTROL NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the claim has been adjusted by the other payer in a payer-to-payer COB situation.

AND

Loop ID-2330 REF F8 is used.

If not required by this implementation guide, do not send.
TR3 Notes:
This is the ICN/DCN of the adjusted claim. When the original claim has been adjusted multiple times, this is the Payer Claim Control Number that represents the adjudication this claim is replacing.
TR3 Example:
REF✱1K✱98765~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
1K
Payor's Claim Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Other Payer Previous Claim Control Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

NM1 - OTHER PAYER REFERRING PROVIDER

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Segments NM1-N4 contain name and address information of the insurance carriers referenced in loop 2320.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when the corresponding Loop ID-2310 NM109 is not used and one or more additional payer-specific provider identifiers are required by this non-destination payer (Loop ID-2330B). If not required by this implementation guide, do not send.
TR3 Notes:
  1. When there is only one referral on the claim, use code "DN - Referring Provider". When more than one referral exists and there is a requirement to report the additional referral, use code DN to indicate the referral received by the rendering provider on this claim. Use code "P3 - Primary Care Provider" to indicate the initial referral from the primary care provider, or whatever provider wrote the initial referral for this patient's episode of care being submitted in this transaction.
  2. See the NUCC website www.nucc.org for the definitions of professional providers.
TR3 Example:
NM1✱DN✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
DN
Referring Provider
P3
Primary Care Provider
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Not Used
3
1035
Name Last or Organization Name
X 1
AN
1/80
Not Used
4
1036
Name First
O 1
AN
1/35
Not Used
5
1037
Name Middle
O 1
AN
1/25
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Not Used
7
1039
Name Suffix
O 1
AN
1/10
Not Used
8
66
Identification Code Qualifier
X 1
ID
1/2
Not Used
9
67
Identification Code
X 1
AN
2/80
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

REF*A6 - OTHER PAYER REFERRING PROVIDER SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
REF✱A6✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
A6
Provider Identifier
Use when reporting a proprietary provider number by the non-destination payer identified in the Other Payer Name Loop ID-2330B for this iteration of Loop ID-2320. This is true regardless of whether that payer is a government, private, commercial, or any other payer.
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Other Payer Referring Provider Secondary Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

NM1*82 - OTHER PAYER RENDERING PROVIDER

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Segments NM1-N4 contain name and address information of the insurance carriers referenced in loop 2320.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when the corresponding Loop ID-2310 NM109 is not used and one or more additional payer-specific provider identifiers are required by this non-destination payer (Loop ID-2330B). If not required by this implementation guide, do not send.
TR3 Notes:
See the NUCC website www.nucc.org for the definitions of professional providers.
TR3 Example:
NM1✱82✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
82
Rendering Provider
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Not Used
3
1035
Name Last or Organization Name
X 1
AN
1/80
Not Used
4
1036
Name First
O 1
AN
1/35
Not Used
5
1037
Name Middle
O 1
AN
1/25
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Not Used
7
1039
Name Suffix
O 1
AN
1/10
Not Used
8
66
Identification Code Qualifier
X 1
ID
1/2
Not Used
9
67
Identification Code
X 1
AN
2/80
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

REF - OTHER PAYER RENDERING PROVIDER SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
2
TR3 Example:
REF✱A6✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
A6
Provider Identifier
Use when reporting a proprietary provider number by the non-destination payer identified in the Other Payer Name Loop ID-2330B for this iteration of Loop ID-2320. This is true regardless of whether that payer is a government, private, commercial, or any other payer.
LU
Location Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Other Payer Rendering Provider Secondary Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

NM1*85 - OTHER PAYER BILLING PROVIDER

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Segments NM1-N4 contain name and address information of the insurance carriers referenced in loop 2320.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when the provider sent in the corresponding Loop ID-2010AA is not a Health Care Provider and one or more additional payer-specific provider identification numbers are required by this non-destination payer (Loop ID-2330B) to identify the provider. If not required by this implementation guide, do not send.
TR3 Example:
NM1✱85✱2~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
85
Billing Provider
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
2
Non-Person Entity
Not Used
3
1035
Name Last or Organization Name
X 1
AN
1/80
Not Used
4
1036
Name First
O 1
AN
1/35
Not Used
5
1037
Name Middle
O 1
AN
1/25
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Not Used
7
1039
Name Suffix
O 1
AN
1/10
Not Used
8
66
Identification Code Qualifier
X 1
ID
1/2
Not Used
9
67
Identification Code
X 1
AN
2/80
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

REF - OTHER PAYER BILLING PROVIDER SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
2
TR3 Example:
REF✱A6✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
A6
Provider Identifier
Use when reporting a proprietary provider number by the non-destination payer identified in the Other Payer Name Loop ID-2330B for this iteration of Loop ID-2320. This is true regardless of whether that payer is a government, private, commercial, or any other payer.
LU
Location Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Other Payer Billing Provider Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

NM1*77 - OTHER PAYER SERVICE LOCATION

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Segments NM1-N4 contain name and address information of the insurance carriers referenced in loop 2320.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when the corresponding Loop ID-2310 NM109 is not used and one or more additional payer-specific provider identifiers are required by this non-destination payer (Loop ID-2330B). If not required by this implementation guide, do not send.
TR3 Example:
NM1✱77✱2~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
77
Service Location
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
2
Non-Person Entity
Not Used
3
1035
Name Last or Organization Name
X 1
AN
1/80
Not Used
4
1036
Name First
O 1
AN
1/35
Not Used
5
1037
Name Middle
O 1
AN
1/25
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Not Used
7
1039
Name Suffix
O 1
AN
1/10
Not Used
8
66
Identification Code Qualifier
X 1
ID
1/2
Not Used
9
67
Identification Code
X 1
AN
2/80
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

REF - OTHER PAYER SERVICE LOCATION SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
2
TR3 Example:
REF✱A6✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
A6
Provider Identifier
Use when reporting a proprietary provider number by the non-destination payer identified in the Other Payer Name Loop ID-2330B for this iteration of Loop ID-2320. This is true regardless of whether that payer is a government, private, commercial, or any other payer.
LU
Location Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Other Payer Service Location Secondary Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

NM1*DD - OTHER PAYER ASSISTANT SURGEON

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Segments NM1-N4 contain name and address information of the insurance carriers referenced in loop 2320.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when the corresponding Loop ID-2310 NM109 is not used and one or more additional payer-specific provider identifiers are required by this non-destination payer (Loop ID-2330B). If not required by this implementation guide, do not send.
TR3 Example:
NM1✱DD✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
DD
Assistant Surgeon
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Not Used
3
1035
Name Last or Organization Name
X 1
AN
1/80
Not Used
4
1036
Name First
O 1
AN
1/35
Not Used
5
1037
Name Middle
O 1
AN
1/25
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Not Used
7
1039
Name Suffix
O 1
AN
1/10
Not Used
8
66
Identification Code Qualifier
X 1
ID
1/2
Not Used
9
67
Identification Code
X 1
AN
2/80
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

REF - OTHER PAYER ASSISTANT SURGEON SECONDARY IDENTIFIER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
2
TR3 Example:
REF✱A6✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
A6
Provider Identifier
Use when reporting a proprietary provider number by the non-destination payer identified in the Other Payer Name Loop ID-2330B for this iteration of Loop ID-2320. This is true regardless of whether that payer is a government, private, commercial, or any other payer.
LU
Location Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Other Payer Assistant Surgeon Secondary Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

NM1*DQ - OTHER PAYER SUPERVISING PROVIDER

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Segments NM1-N4 contain name and address information of the insurance carriers referenced in loop 2320.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when the corresponding Loop ID-2310 NM109 is not used and one or more additional payer-specific provider identifiers are required by this non-destination payer (Loop ID-2330B). If not required by this implementation guide, do not send.
TR3 Example:
NM1✱DQ✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
DQ
Supervising Physician
Use when reporting the supervising dentist or physician.
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Not Used
3
1035
Name Last or Organization Name
X 1
AN
1/80
Not Used
4
1036
Name First
O 1
AN
1/35
Not Used
5
1037
Name Middle
O 1
AN
1/25
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Not Used
7
1039
Name Suffix
O 1
AN
1/10
Not Used
8
66
Identification Code Qualifier
X 1
ID
1/2
Not Used
9
67
Identification Code
X 1
AN
2/80
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

REF*A6 - OTHER PAYER SUPERVISING PROVIDER SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
REF✱A6✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
A6
Provider Identifier
Use when reporting a proprietary provider number by the non-destination payer identified in the Other Payer Name Loop ID-2330B for this iteration of Loop ID-2320. This is true regardless of whether that payer is a government, private, commercial, or any other payer.
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

LX - SERVICE LINE NUMBER

X12 Name:
Transaction Set Line Number
X12 Purpose:
To reference a line number in a transaction set
X12 Set Notes:
NOTE: Loop 2400 contains Service Line information.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
  1. The LX functions as a line counter.
  2. The Service Line LX segment must begin with one and is incremented by one for each additional service line of a claim.
  3. LX01 is used to indicate bundling in SVD06 in the Line Item Adjudication loop. See Section 1.4.2.3 for more information on bundling and unbundling.
TR3 Example:
LX✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
554
Assigned Number
M 1
N
1/9
Number assigned for differentiation within a transaction set

SV3 - DENTAL SERVICE

X12 Name:
Dental Service
X12 Purpose:
To specify the service line item detail for dental work
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
SV3✱AD:D2150✱80~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
C003
Composite Medical Procedure Identifier
M 1
To identify a medical procedure by its standardized codes and applicable modifiers
X12 COMPOSITE SEMANTIC NOTES:
  1. C003-01 qualifies C003-02 and C003-08.
  2. If C003-08 is used, then C003-02 represents the beginning value in the range in which the code occurs.
  3. C003-03 modifies the value in C003-02 and C003-08.
  4. C003-04 modifies the value in C003-02 and C003-08.
  5. C003-05 modifies the value in C003-02 and C003-08.
  6. C003-06 modifies the value in C003-02 and C003-08.
  7. C003-07 is the description of the procedure identified in C003-02.
  8. C003-08 represents the ending value in the range in which the code occurs.
  9. C003-09 modifies the value in C003-02 and C003-08.
  10. C003-10 modifies the value in C003-02 and C003-08.
  11. C003-11 modifies the value in C003-02 and C003-08.
  12. C003-12 modifies the value in C003-02 and C003-08.
Required
1-1
235
Product/Service ID Qualifier
M 1
ID
2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
INDUSTRY NAME: Product or Service ID Qualifier
CODE
DEFINITION
AD
American Dental Association Codes
CODE SOURCE: 135: American Dental Association
Required
1-2
234
Product/Service ID
M 1
AN
1/80
Identifying number for a product or service
INDUSTRY NAME: Procedure Code
Situational
1-3
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when a modifier clarifies or improves the reporting accuracy of the associated procedure code. This is the first procedure code modifier. If not required by this implementation guide, do not send.
A modifier must be from code source 135 (American Dental Association) found in the 'Code on Dental Procedures and Nomenclature'.
Situational
1-4
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when a second modifier clarifies or improves the reporting accuracy of the associated procedure code. If not required by this implementation guide, do not send.
A modifier must be from code source 135 (American Dental Association) found in the 'Code on Dental Procedures and Nomenclature'.
Situational
1-5
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when a third modifier clarifies or improves the reporting accuracy of the associated procedure code. If not required by this implementation guide, do not send.
A modifier must be from code source 135 (American Dental Association) found in the 'Code on Dental Procedures and Nomenclature'.
Situational
1-6
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when a fourth modifier clarifies or improves the reporting accuracy of the associated procedure code. If not required by this implementation guide, do not send.
A modifier must be from code source 135 (American Dental Association) found in the 'Code on Dental Procedures and Nomenclature'.
Situational
1-7
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
SITUATIONAL RULE: Required when, in the judgment of the submitter, the procedure code does not definitively describe the service/product/supply and loop 2410 is not used.ORRequired when SV301-02 is a non-specific procedure code as defined by the payer. If not required by this implementation guide, do not send.
INDUSTRY NAME: Procedure Code Description
Non-specific codes may include in their descriptors terms such as: Not Otherwise Classified (NOC); Unlisted; Unspecified; Unclassified; Other, Miscellaneous; Prescription Drug; Generic; or Prescription Drug, Brand Name.

Some procedures (such as anesthesia and laboratory) have code descriptors that include "Not Otherwise Specified"; however, these are not considered "non-specific" procedure codes.
Not Used
1-8
234
Product/Service ID
O 1
AN
1/80
Not Used
1-9
1339
Procedure Modifier
O 1
AN
2
Not Used
1-10
1339
Procedure Modifier
O 1
AN
2
Not Used
1-11
1339
Procedure Modifier
O 1
AN
2
Not Used
1-12
1339
Procedure Modifier
O 1
AN
2
Required
2
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: SV302 is the submitted service line item amount.
INDUSTRY NAME: Line Item Charge Amount
  1. Zero "0" is an acceptable value for this element.
  2. Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
  3. This is the total charge amount for this service line.
Situational
3
1331
Facility Code Value
O 1
AN
1/3
Code identifying where services were, or may be, performed; the National Uniform Billing Committee (NUBC) Facility Type Code for Institutional Services or the Place of Service Codes for Professional or Dental Services.
SEMANTIC: SV303 is the place of service code representing the location where the dental treatment was rendered.
SITUATIONAL RULE: Required when value is different than value carried in CLM05-01 in Loop ID-2300. If not required by this implementation guide, do not send.
INDUSTRY NAME: Place of Service Code
See CODE SOURCE 237: Place of Service Codes for Professional Claims
Situational
4
C006
Oral Cavity Designation
O 1
To identify one or more areas of the oral cavity
SITUATIONAL RULE: Required when the nomenclature associated with the procedure reported in SV301-02 refers to quadrant or arch and the area of the oral cavity is not uniquely defined by the procedure description. Report individual tooth numbers in one or more TOO segments.
Do not use this element for reporting of individual teeth. If it is necessary to report one or more individual teeth, use the Tooth Information (TOO) segment in this loop.
Required
4-1
1361
Oral Cavity Designation Code
M 1
ID
1/3
Code Identifying the area of the oral cavity in which service is rendered
CODE SOURCE 135: American Dental Association
Situational
4-2
1361
Oral Cavity Designation Code
O 1
ID
1/3
Code Identifying the area of the oral cavity in which service is rendered
SITUATIONAL RULE: Required when reporting a second area of the oral cavity. If not required by this implementation guide, do not send.
CODE SOURCE 135: American Dental Association
Situational
4-3
1361
Oral Cavity Designation Code
O 1
ID
1/3
Code Identifying the area of the oral cavity in which service is rendered
SITUATIONAL RULE: Required when reporting a third area of the oral cavity. If not required by this implementation guide, do not send.
CODE SOURCE 135: American Dental Association
Situational
4-4
1361
Oral Cavity Designation Code
O 1
ID
1/3
Code Identifying the area of the oral cavity in which service is rendered
SITUATIONAL RULE: Required when reporting a fourth area of the oral cavity. If not required by this implementation guide, do not send.
CODE SOURCE 135: American Dental Association
Situational
4-5
1361
Oral Cavity Designation Code
O 1
ID
1/3
Code Identifying the area of the oral cavity in which service is rendered
SITUATIONAL RULE: Required when reporting a fifth area of the oral cavity. If not required by this implementation guide, do not send.
CODE SOURCE 135: American Dental Association
Situational
5
1358
Prosthesis, Crown or Inlay Code
O 1
ID
1
Code specifying the placement status for the dental work
SITUATIONAL RULE: Required to indicate the placement status of the prosthetic on this line. If not required by this implementation guide, do not send.
INDUSTRY NAME: Prosthesis, Crown, or Inlay Code
CODE
DEFINITION
I
Initial Placement
R
Replacement
Situational
6
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: SV306 is the number of procedures.
SITUATIONAL RULE: Required when the procedure reported in SV301-02 was performed more than once and it is not required to identify areas of the oral cavity or individual teeth.If not required by this implementation guide, do not send.
INDUSTRY NAME: Procedure Count
Number of procedures
Not Used
7
352
Description
O 1
AN
1/80
Not Used
8
1327
Copay Status Code
O 1
ID
1
Not Used
9
1360
Provider Agreement Code
O 1
ID
1
Not Used
10
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
11
1328
Diagnosis Code Pointer
O 12
N
1/2
A pointer to the diagnosis code in the order of importance to this service
SEMANTIC: The first pointer designates the primary diagnosis and remaining diagnosis pointers indicate declining level of importance.
SITUATIONAL RULE: Required when this service relates to a specific diagnosis and is needed to substantiate the medical treatment. If not required by this implementation guide, do not send.
The first pointer designates the primary diagnosis for this service line. Remaining diagnosis pointers indicate declining level of importance to service line. Acceptable values are 1 through 4, and correspond to Composite Data Elements 01 through 04 in the Health Care Diagnosis Code HI segment in the Claim Loop ID-2300.

TOO*JP - TOOTH INFORMATION

X12 Name:
Tooth Identification
X12 Purpose:
To identify a tooth by number and, if applicable, one or more tooth surfaces
X12 Syntax:
P0102
If either TOO01 or TOO02 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
32
Situational Rule:
Required when reporting tooth information related to this service line. If not required by this implementation guide, do not send.
TR3 Example:
TOO✱JP✱12✱L:O~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1270
Code List Qualifier Code
X 1
ID
1/3
Code identifying a specific industry code list
SEGMENT SYNTAX: P0102
CODE
DEFINITION
JP
Universal National Tooth Designation System
CODE SOURCE: 135: American Dental Association
Required
2
1271
Industry Code
X 1
AN
1/30
Code indicating a code from a specific industry code list
SEGMENT SYNTAX: P0102
INDUSTRY NAME: Tooth Code
This element may only be used to report individual teeth. It may not be used to report areas of the oral cavity such as quadrants or sextants. Areas of the oral cavity must be reported in one or more of the components of SV304.
Situational
3
C005
Tooth Surface
O 1
To identify one or more tooth surface codes
SITUATIONAL RULE: Required when the procedure code requires tooth surface codes. If not required by this implementation guide, do not send.
Required
3-1
1369
Tooth Surface Code
M 1
ID
1/2
Code identifying the area of the tooth that was treated
CODE
DEFINITION
B
Buccal
D
Distal
F
Facial
I
Incisal
L
Lingual
M
Mesial
O
Occlusal
Situational
3-2
1369
Tooth Surface Code
O 1
ID
1/2
Code identifying the area of the tooth that was treated
SITUATIONAL RULE: Required when it is necessary to report an additional tooth surface. If not required by this implementation guide, do not send.
Additional tooth surface codes can be carried in TOO03-02 through TOO03-05. The code values are the same as in TOO03-01.
CODE
DEFINITION
B
Buccal
D
Distal
F
Facial
I
Incisal
L
Lingual
M
Mesial
O
Occlusal
Situational
3-3
1369
Tooth Surface Code
O 1
ID
1/2
Code identifying the area of the tooth that was treated
SITUATIONAL RULE: Required when it is necessary to report an additional tooth surface. If not required by this implementation guide, do not send.
CODE
DEFINITION
B
Buccal
D
Distal
F
Facial
I
Incisal
L
Lingual
M
Mesial
O
Occlusal
Situational
3-4
1369
Tooth Surface Code
O 1
ID
1/2
Code identifying the area of the tooth that was treated
SITUATIONAL RULE: Required when it is necessary to report an additional tooth surface. If not required by this implementation guide, do not send.
CODE
DEFINITION
B
Buccal
D
Distal
F
Facial
I
Incisal
L
Lingual
M
Mesial
O
Occlusal
Situational
3-5
1369
Tooth Surface Code
O 1
ID
1/2
Code identifying the area of the tooth that was treated
SITUATIONAL RULE: Required when it is necessary to report an additional tooth surface. If not required by this implementation guide, do not send.
CODE
DEFINITION
B
Buccal
D
Distal
F
Facial
I
Incisal
L
Lingual
M
Mesial
O
Occlusal

DTP*472 - SERVICE DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the service was performed and the service date is different than the date reported in the Service Date segment in the 2300 loop. If not required by this implementation guide, do not send.
TR3 Notes:
Do not use this DTP segment when submitting a Predetermination of Dental Benefits.
TR3 Example:
DTP✱472✱D8✱20221030~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
472
Service
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Service Date

DTP - PRIOR PLACEMENT DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the value of SV305 for this iteration of the Loop ID-2400 loop is "R". If not required by this implementation guide, do not send.
TR3 Example:
DTP✱441✱D8✱20220401~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
139
Estimated
Use when the exact Prior Placement Date is not known.
441
Prior Placement
Use when the exact Prior Placement Date is known.
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Prior Placement Date

DTP*452 - ORTHODONTIC BANDING DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the orthodontic appliance placement date is different than the orthodontic appliance placement date in the DTP segment in the Loop ID-2300 loop. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱452✱D8✱20221030~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
452
Appliance Placement
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Orthodontic Banding Date

DTP*446 - REPLACEMENT DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when reporting the date that an orthodontic appliance was replaced. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱446✱D8✱20221030~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
446
Replacement
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Replacement Date

REF*G3 - SERVICE PREDETERMINATION IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
11
Situational Rule:
Required when sending the Predetermination of Benefits Identification Number for the line item that has been previously predetermined that is now being submitted for payment and is different than the number reported at the claim level (Loop ID-2300). If not required by this implementation guide, do not send.
TR3 Notes:
Reference numbers at this position apply to the current line item only.
TR3 Example:
REF✱G3✱13579~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
G3
Predetermination of Benefits Identification Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Predetermination of Benefits Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Situational
4
C040
Reference Identifier
O 1
To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier
SEMANTIC: REF04 contains data relating to the value cited in REF02.
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C04003 or C04004 is present, then the other is required.
  2. P0506
    If either C04005 or C04006 is present, then the other is required.
SITUATIONAL RULE: Required when the identifier reported in REF02 of this segment is for a non-destination payer.
Required
4-1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
2U
Payer Identification Number
Required
4-2
127
Reference Identification
M 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
INDUSTRY NAME: Other Payer Responsibility Sequence Code
  1. The value reported in this field must match the corresponding Other Payer Responsibility Sequence Code reported in Loop ID-2320 SBR01.
  2. Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
4-3
128
Reference Identification Qualifier
X 1
ID
2/3
Not Used
4-4
127
Reference Identification
X 1
AN
1/80
Not Used
4-5
128
Reference Identification Qualifier
X 1
ID
2/3
Not Used
4-6
127
Reference Identification
X 1
AN
1/80

REF*G1 - PRIOR AUTHORIZATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
11
Situational Rule:
Required when the service line involved a prior authorization number that is different than the number reported at the claim level (Loop ID-2300)

OR

Required when a prior authorization only applies to this service line (Loop ID-2400) and no claim level (Loop ID-2300) prior authorization was reported. If not required by this implementation guide, do not send.
TR3 Notes:
This segment must not be used to report the Predetermination of Benefits Identification Number.
TR3 Example:
REF✱G1✱13579~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
G1
Prior Authorization Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Prior Authorization Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Situational
4
C040
Reference Identifier
O 1
To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier
SEMANTIC: REF04 contains data relating to the value cited in REF02.
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C04003 or C04004 is present, then the other is required.
  2. P0506
    If either C04005 or C04006 is present, then the other is required.
SITUATIONAL RULE: Required when the identifier reported in REF02 of this segment is for a non-destination payer.
Required
4-1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
2U
Payer Identification Number
Required
4-2
127
Reference Identification
M 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
INDUSTRY NAME: Other Payer Responsibility Sequence Code
  1. The value reported in this field must match the corresponding Other Payer Responsibility Sequence Code reported in Loop ID-2320 SBR01.
  2. Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
4-3
128
Reference Identification Qualifier
X 1
ID
2/3
Not Used
4-4
127
Reference Identification
X 1
AN
1/80
Not Used
4-5
128
Reference Identification Qualifier
X 1
ID
2/3
Not Used
4-6
127
Reference Identification
X 1
AN
1/80

REF*6R - LINE ITEM CONTROL NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
  1. If the provider does not use a unique line item control number or the originating claim did not have a line item control number (i.e., Payer to Payer COB, paper to electronic), then use the LX01 value.
  2. Submitters are STRONGLY encouraged to routinely send a unique line item control number on all service lines, particularly if the submitter automatically posts their remittance advice. Submitting a unique line item control number allows the capability to automatically post by service line.
  3. The line item control number needs to be unique within a Provider's Assigned Claim Identifier (CLM01). Payers are required to return this number in the remittance advice transaction (835) if the provider sends it to them in the 837 and adjudication is based upon line item detail regardless of whether bundling or unbundling has occurred.
TR3 Example:
REF✱6R✱54321~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
6R
Provider Control Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Line Item Control Number
  1. The maximum number of characters to be supported for this field is 30. A submitter may submit fewer characters depending upon their needs. Characters beyond 30 are not required to be stored nor returned by any 837-receiving system.
  2. Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*9B - REPRICED LINE ITEM REFERENCE NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when this information is deemed necessary by the repricer. If not required by this implementation guide, do not send.
TR3 Notes:
  1. This information is specific to the destination payer reported in Loop ID-2010BB.
  2. This segment is not completed by providers. The information is completed by repricers only.
TR3 Example:
REF✱9B✱444444~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
9B
Repriced Line Item Reference Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Repriced Line Item Reference Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*9D - ADJUSTED REPRICED LINE ITEM REFERENCE NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when this information is deemed necessary by the repricer. If not required by this implementation guide, do not send.
TR3 Notes:
  1. This information is specific to the destination payer reported in Loop ID-2010BB.
  2. This segment is not completed by providers. The information is completed by repricers only.
TR3 Example:
REF✱9D✱444444~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
9D
Adjusted Repriced Line Item Reference Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Adjusted Repriced Line Item Reference Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*9F - REFERRAL NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
11
Situational Rule:
Required when this service line involved a referral number AND it is different than the number reported at the claim level (Loop-ID 2300).

OR

Required when this service line involved a referral number AND a claim level referral (Loop ID 2300) was not reported. If not required by this implementation guide, do not send.
TR3 Example:
REF✱9F✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
9F
Referral Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Referral Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Situational
4
C040
Reference Identifier
O 1
To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier
SEMANTIC: REF04 contains data relating to the value cited in REF02.
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C04003 or C04004 is present, then the other is required.
  2. P0506
    If either C04005 or C04006 is present, then the other is required.
SITUATIONAL RULE: Required when the identifier reported in REF02 of this segment is for a non-destination payer.
Required
4-1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
2U
Payer Identification Number
Required
4-2
127
Reference Identification
M 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
INDUSTRY NAME: Other Payer Responsibility Sequence Code
  1. The value reported in this field must match the corresponding Other Payer Responsibility Sequence Code reported in Loop ID-2320 SBR01.
  2. Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
4-3
128
Reference Identification Qualifier
X 1
ID
2/3
Not Used
4-4
127
Reference Identification
X 1
AN
1/80
Not Used
4-5
128
Reference Identification Qualifier
X 1
ID
2/3
Not Used
4-6
127
Reference Identification
X 1
AN
1/80

AMT*SCT - STATE CARE TAX

X12 Name:
Monetary Amount Information
X12 Purpose:
To indicate the total monetary amount
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when State Care Tax applies to the service line and the submitter is required to report this information to the receiver. If not required by this implementation guide, do not send.
TR3 Notes:
  1. Sales Tax is not reported in this Segment.
  2. The State Care Tax Amount must be included in the Line Item Charge Amount (SV302) of the related Service Line.
TR3 Example:
AMT✱SCT✱20~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
522
Amount Qualifier Code
M 1
ID
1/3
Code specifying the amount qualifier
CODE
DEFINITION
SCT
State Care Tax
Required
2
782
Monetary Amount
M 1
R
1/18
Monetary amount
INDUSTRY NAME: State Care Tax
Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
Not Used
3
478
Credit/Debit Flag Code
O 1
ID
1

K3 - FILE INFORMATION

X12 Name:
File Information
X12 Purpose:
To transmit a fixed-format record or matrix contents
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
10
Situational Rule:
Required when X12N has reviewed and approved the data requirements of a regulatory/legislative authority for use of the K3 Segment and has concluded that there is no current method to meet the requirement. (See Section 1.4.6.1 for obtaining X12N approval). If not required by this implementation guide, do not send.
TR3 Notes:
  1. The K3 segment is used only when necessary to meet the unexpected data requirement of a regulatory/legislative authority. Before this segment can be used:

    - X12N must conclude there is no other available option in the implementation guide to meet the emergency regulatory/legislative requirement.

    - The requester must submit a change request accompanied by the relevant business documentation and receive approval for the request.

    Upon review of the request, X12N will issue an approval or denial decision to the requesting entity. Approved usage(s) of the K3 Segment will be reviewed by the applicable X12N work group to develop a permanent change to include the business case in future transaction implementations.
  2. Only when all of the requirements above have been met, may the regulatory agency require the temporary use of the K3 segment.
TR3 Example:
K3✱STATE DATA REQUIREMENT~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
449
Fixed Format Information
M 1
AN
1/80
Data in fixed format agreed upon by sender and receiver
INDUSTRY NAME: Temporary Solution for a Statutory/Regulatory Requirement
Not Used
2
1333
Record Format Code
O 1
ID
1/2
Not Used
3
C001
Composite Unit of Measure
O 1

HCP - LINE PRICING/REPRICING INFORMATION

X12 Name:
Health Care Pricing
X12 Purpose:
To specify pricing or repricing information about a health care claim or line item
X12 Syntax:
  1. R0113
    At least one of HCP01 or HCP13 is required.
  2. P0910
    If either HCP09 or HCP10 is present, then the other is required.
  3. P1112
    If either HCP11 or HCP12 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when this information is deemed necessary by the repricer. If not required by this implementation guide, do not send.
TR3 Notes:
  1. This information is specific to the destination payer reported in Loop ID-2010BB.
  2. This segment is not completed by providers. The information is completed by repricers only.
TR3 Example:
HCP✱03✱100✱10✱RPO12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1473
Pricing Methodology Code
X 1
ID
2
Code specifying pricing methodology at which the claim or line item has been priced or repriced
SEGMENT SYNTAX: R0113
INDUSTRY NAME: Pricing Methodology
Specific code use is determined by Trading Partner Agreement due to the variances in contracting policies in the industry.
CODE
DEFINITION
00
Zero Pricing (Not Covered Under Contract)
01
Priced as Billed at 100%
02
Priced at the Standard Fee Schedule
03
Priced at a Contractual Percentage
04
Bundled Pricing
05
Peer Review Pricing
07
Flat Rate Pricing
08
Combination Pricing
09
Maternity Pricing
10
Other Pricing
11
Lower of Cost
12
Ratio of Cost
13
Cost Reimbursed
14
Adjustment Pricing
Required
2
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: HCP02 is the allowed amount.
INDUSTRY NAME: Repriced Allowed Amount
Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
Situational
3
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: HCP03 is the savings amount.
SITUATIONAL RULE: Required when this information is deemed necessary by the repricer. If not required by this implementation guide, do not send.
INDUSTRY NAME: Repriced Savings Amount
Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
Situational
4
127
Reference Identification
O 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: HCP04 is the repricing organization identification number.
SITUATIONAL RULE: Required when this information is deemed necessary by the repricer. If not required by this implementation guide, do not send.
INDUSTRY NAME: Repricing Organization Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Situational
5
118
Rate
O 1
R
1/9
Rate expressed in the standard monetary denomination for the currency specified
SEMANTIC: HCP05 is the pricing rate associated with per diem or flat rate repricing.
SITUATIONAL RULE: Required when this information is deemed necessary by the repricer. If not required by this implementation guide, do not send.
INDUSTRY NAME: Repricing Per Diem or Flat Rate Amount
Not Used
6
127
Reference Identification
O 1
AN
1/80
Not Used
7
782
Monetary Amount
O 1
R
1/18
Not Used
8
234
Product/Service ID
O 1
AN
1/80
Situational
9
235
Product/Service ID Qualifier
X 1
ID
2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
SEGMENT SYNTAX: P0910
SITUATIONAL RULE: Required when this information is deemed necessary by the repricer. If not required by this implementation guide, do not send.
INDUSTRY NAME: Product or Service ID Qualifier
CODE
DEFINITION
AD
American Dental Association Codes
CODE SOURCE: 135: American Dental Association
Situational
10
234
Product/Service ID
X 1
AN
1/80
Identifying number for a product or service
SEMANTIC: HCP10 is the approved procedure code.
SEGMENT SYNTAX: P0910
SITUATIONAL RULE: Required when this information is deemed necessary by the repricer. If not required by this implementation guide, do not send.
INDUSTRY NAME: Repriced Approved HCPCS Code
Situational
11
355
Unit or Basis for Measurement Code
X 1
ID
2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
SEGMENT SYNTAX: P1112
SITUATIONAL RULE: Required when this information is deemed necessary by the repricer. If not required by this implementation guide, do not send.
CODE
DEFINITION
UN
Unit
Situational
12
380
Quantity
X 1
R
1/15
Numeric value of quantity
SEMANTIC: HCP12 is the approved service units or inpatient days.
SEGMENT SYNTAX: P1112
SITUATIONAL RULE: Required when this information is deemed necessary by the repricer. If not required by this implementation guide, do not send.
INDUSTRY NAME: Repriced Approved Service Unit Count
  1. Note: When a decimal is needed to report units, include it in this element, for example, "15.6".
  2. The maximum length for this field is 8 digits excluding the decimal. When a decimal is used, the maximum number of digits allowed to the right of the decimal is three. A zero or negative value is not allowed.
Situational
13
901
Reject Reason Code
X 1
ID
2
Code identifying reason for rejection as assigned by issuer
SEMANTIC: HCP13 is the rejection message returned from the third party organization.
SEGMENT SYNTAX: R0113
SITUATIONAL RULE: Required when this information is deemed necessary by the repricer. If not required by this implementation guide, do not send.
CODE
DEFINITION
T1
Cannot Identify Provider as TPO (Third Party Organization) Participant
T6
Claim does not contain enough information for re-pricing
Situational
14
1526
Policy Compliance Code
O 1
ID
1/2
Code specifying policy compliance
SITUATIONAL RULE: Required when this information is deemed necessary by the repricer. If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Procedure Followed (Compliance)
2
Not Followed - Call Not Made (Non-Compliance Call Not Made)
3
Not Medically Necessary (Non-Compliance Non-Medically Necessary)
4
Not Followed Other (Non-Compliance Other)
5
Emergency Admit to Non-Network Hospital
Situational
15
1527
Exception Code
O 1
ID
1/2
Code specifying the exception reason for consideration of out-of-network health care services
SEMANTIC: HCP15 is the exception reason generated by a third party organization.
SITUATIONAL RULE: Required when this information is deemed necessary by the repricer. If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Non-Network Professional Provider in Network Hospital
2
Emergency Care
3
Services or Specialist not in Network
4
Out-of-Service Area
5
State Mandates
6
Other

NM1*82 - RENDERING PROVIDER NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Loop 2420 contains information about the service line providers including, but not limited to: rendering, referring and attending. These segments override the information in the claim - level segments if the entity identifier codes in each NM1 segment are the same.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when the Rendering Provider NM1 information is different than that carried in the Loop ID-2310B Rendering Provider and the Assistant Surgeon (Loop ID-2420C) loop is not present
OR
Required when each of the following conditions apply:
• the Rendering Provider information is carried at the Billing Provider level (Loop ID-2010AA)
• this particular line item has different Rendering Provider information than that which is carried in the Loop ID-2010AA Billing Provider
• the Assistant Surgeon loop (Loop ID-2420C) is not used.
If not required by this implementation guide, do not send.
TR3 Notes:
See the NUCC website www.nucc.org for the definitions of professional providers.
TR3 Example:
NM1✱82✱1✱DOE✱JANE✱C✱✱✱XX✱1234567804~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
82
Rendering Provider
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Required
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Rendering Provider Last Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Rendering Provider First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when NM102 = 1 (person) and the Middle Name or Initial is known to the sender. If not required by this implementation guide, do not send.
INDUSTRY NAME: Rendering Provider Middle Name or Initial
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when the Suffix is known to the sender. If not required by this implementation guide, do not send.
INDUSTRY NAME: Rendering Provider Name Suffix
Situational
8
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when NM109 is used. If not required by this implementation guide, do not send.
CODE
DEFINITION
XX
Standard Unique Health Identifier for Health Care Providers (NPI)
CODE SOURCE: 537: National Provider Identifier (NPI)
Situational
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required for providers in the United States or its territories when the provider is eligible to receive a National Provider Identifier (NPI).ORRequired for providers not in the United States or its territories when the provider has received an NPI. If not required by this implementation guide, do not send.
INDUSTRY NAME: Rendering Provider Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

PRV*PE - RENDERING PROVIDER SPECIALTY INFORMATION

X12 Name:
Provider Information
X12 Purpose:
To specify the identifying characteristics of a provider
X12 Syntax:
P0203
If either PRV02 or PRV03 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
PRV✱PE✱PXC✱1223G0001X~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1221
Provider Code
M 1
ID
1/3
Code identifying the type of provider
CODE
DEFINITION
PE
Performing
Required
2
128
Reference Identification Qualifier
X 1
ID
2/3
Code identifying the Reference Identification
SEGMENT SYNTAX: P0203
CODE
DEFINITION
PXC
Health Care Provider Taxonomy Code
CODE SOURCE: 682: Health Care Provider Taxonomy
Required
3
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: P0203
INDUSTRY NAME: Provider Taxonomy Code
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
4
156
State or Province Code
O 1
ID
2
Not Used
5
C035
Provider Specialty Information
O 1
Not Used
6
1223
Provider Organization Code
O 1
ID
3

REF - RENDERING PROVIDER SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
20
Situational Rule:
Required when NM109 of this loop is not used and an identifier is necessary for the receiver to identify the provider. If not required by this implementation guide, do not send.
TR3 Notes:
If REF04 is not used, REF02 is a proprietary provider number assigned by the destination payer identified in the Payer Name loop, Loop ID-2010BB, associated with this claim.

If REF04 is used, REF02 is a proprietary provider number assigned by the non-destination payer identified in the Other Payer Name loop, Loop ID-2330B, associated with this claim.
TR3 Example:
REF✱A6✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
A6
Provider Identifier
Use when reporting a proprietary provider number assigned by the destination payer identified in the Payer Name loop, Loop ID-2010BB, associated with this claim
OR
Use when reporting a proprietary provider number assigned by the non-destination payer identified in REF04-02 of this segment. This is true regardless of whether that payer is a government, private, commercial or any other payer.
LU
Location Number
Use when reporting the provider's location when different than the billing or service location.
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Rendering Provider Secondary Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Situational
4
C040
Reference Identifier
O 1
To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier
SEMANTIC: REF04 contains data relating to the value cited in REF02.
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C04003 or C04004 is present, then the other is required.
  2. P0506
    If either C04005 or C04006 is present, then the other is required.
SITUATIONAL RULE: Required when the identifier reported in REF02 of this segment is for a non-destination payer.
Required
4-1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
2U
Payer Identification Number
Required
4-2
127
Reference Identification
M 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
INDUSTRY NAME: Other Payer Responsibility Sequence Code
  1. The value reported in this field must match the corresponding Other Payer Responsibility Sequence Code reported in Loop ID-2320 SBR01.
  2. Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
4-3
128
Reference Identification Qualifier
X 1
ID
2/3
Not Used
4-4
127
Reference Identification
X 1
AN
1/80
Not Used
4-5
128
Reference Identification Qualifier
X 1
ID
2/3
Not Used
4-6
127
Reference Identification
X 1
AN
1/80

NM1*DD - ASSISTANT SURGEON NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Loop 2420 contains information about the service line providers including, but not limited to: rendering, referring and attending. These segments override the information in the claim - level segments if the entity identifier codes in each NM1 segment are the same.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when the Rendering Provider provided these services in the role of the Assistant Surgeon and the Assistant Surgeon information in this loop is different from the Assistant Surgeon information sent in Loop ID-2310D.
If not required by this implementation guide, do not send.
TR3 Example:
NM1✱DD✱1✱SMITH✱JOHN✱S✱✱✱XX✱1234567890~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
DD
Assistant Surgeon
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Required
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Assistant Surgeon Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Assistant Surgeon First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when the Middle Name or Initial is known to the sender. If not required by this implementation guide, do not send.
INDUSTRY NAME: Assistant Surgeon Middle Name or Initial
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when the Suffix is known to the sender. If not required by this implementation guide, do not send.
INDUSTRY NAME: Assistant Surgeon Name Suffix
Situational
8
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when NM109 is used. If not required by this implementation guide, do not send.
CODE
DEFINITION
XX
Standard Unique Health Identifier for Health Care Providers (NPI)
CODE SOURCE: 537: National Provider Identifier (NPI)
Situational
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required for providers in the United States or its territories when the provider is eligible to receive a National Provider Identifier (NPI).ORRequired for providers not in the United States or its territories when the provider has received an NPI. If not required by this implementation guide, do not send.
INDUSTRY NAME: Assistant Surgeon Primary Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

PRV*AS - ASSISTANT SURGEON SPECIALTY INFORMATION

X12 Name:
Provider Information
X12 Purpose:
To specify the identifying characteristics of a provider
X12 Syntax:
P0203
If either PRV02 or PRV03 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the Assistant Surgeon specialty information is needed to facilitate reimbursement of the claim. If not required by this implementation guide, do not send.
TR3 Example:
PRV✱AS✱PXC✱1223S0112X~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1221
Provider Code
M 1
ID
1/3
Code identifying the type of provider
CODE
DEFINITION
AS
Assistant Surgeon
Required
2
128
Reference Identification Qualifier
X 1
ID
2/3
Code identifying the Reference Identification
SEGMENT SYNTAX: P0203
CODE
DEFINITION
PXC
Health Care Provider Taxonomy Code
CODE SOURCE: 682: Health Care Provider Taxonomy
Required
3
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: P0203
INDUSTRY NAME: Provider Taxonomy Code
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
4
156
State or Province Code
O 1
ID
2
Not Used
5
C035
Provider Specialty Information
O 1
Not Used
6
1223
Provider Organization Code
O 1
ID
3

REF - ASSISTANT SURGEON SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
20
Situational Rule:
Required when NM109 of this loop is not used and an identifier is necessary for the receiver to identify the provider. If not required by this implementation guide, do not send.
TR3 Notes:
If REF04 is not used, REF02 is a proprietary provider number assigned by the destination payer identified in the Payer Name loop, Loop ID-2010BB, associated with this claim.

If REF04 is used, REF02 is a proprietary provider number assigned by the non-destination payer identified in the Other Payer Name loop, Loop ID-2330B, associated with this claim.
TR3 Example:
REF✱A6✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
A6
Provider Identifier
Use when reporting a proprietary provider number assigned by the destination payer identified in the Payer Name loop, Loop ID-2010BB, associated with this claim
OR
Use when reporting a proprietary provider number assigned by the non-destination payer identified in REF04-02 of this segment. This is true regardless of whether that payer is a government, private, commercial or any other payer.
LU
Location Number
Use when reporting the provider's location when different than the billing or service location.
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Assistant Surgeon Secondary Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Situational
4
C040
Reference Identifier
O 1
To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier
SEMANTIC: REF04 contains data relating to the value cited in REF02.
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C04003 or C04004 is present, then the other is required.
  2. P0506
    If either C04005 or C04006 is present, then the other is required.
SITUATIONAL RULE: Required when the identifier reported in REF02 of this segment is for a non-destination payer.
Required
4-1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
2U
Payer Identification Number
Required
4-2
127
Reference Identification
M 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
INDUSTRY NAME: Other Payer Responsibility Sequence Code
  1. The value reported in this field must match the corresponding Other Payer Responsibility Sequence Code reported in Loop ID-2320 SBR01.
  2. Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
4-3
128
Reference Identification Qualifier
X 1
ID
2/3
Not Used
4-4
127
Reference Identification
X 1
AN
1/80
Not Used
4-5
128
Reference Identification Qualifier
X 1
ID
2/3
Not Used
4-6
127
Reference Identification
X 1
AN
1/80

NM1*DQ - SUPERVISING PROVIDER NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Loop 2420 contains information about the service line providers including, but not limited to: rendering, referring and attending. These segments override the information in the claim - level segments if the entity identifier codes in each NM1 segment are the same.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when the rendering provider is supervised by a physician or dentist and the supervising physician or dentist for this service line is different than that listed at the claim level. If not required by this implementation guide, do not send.
TR3 Notes:
See the NUCC website www.nucc.org for the definitions of professional providers.
TR3 Example:
NM1✱DQ✱1✱SMITH✱JOHN✱A✱✱✱XX✱2223334444~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
DQ
Supervising Physician
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Required
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Supervising Provider Last Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Supervising Provider First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when the Middle Name or Initial is known to the sender. If not required by this implementation guide, do not send.
INDUSTRY NAME: Supervising Provider Middle Name or Initial
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when the Suffix is known to the sender. If not required by this implementation guide, do not send.
INDUSTRY NAME: Supervising Provider Name Suffix
Situational
8
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when NM109 is used. If not required by this implementation guide, do not send.
CODE
DEFINITION
XX
Standard Unique Health Identifier for Health Care Providers (NPI)
CODE SOURCE: 537: National Provider Identifier (NPI)
Situational
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required for providers in the United States or its territories when the provider is eligible to receive a National Provider Identifier (NPI).ORRequired for providers not in the United States or its territories when the provider has received an NPI. If not required by this implementation guide, do not send.
INDUSTRY NAME: Supervising Provider Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

REF*A6 - SUPERVISING PROVIDER SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when NM109 of this loop is not used and an identifier is necessary for the receiver to identify the provider. If not required by this implementation guide, do not send.
TR3 Notes:
  1. When it is necessary to assign the identifier in REF01 of this segment to one or more non-destination payers, the composite data element in REF04 is used to identify the payer that assigned this identifier.
  2. If REF04 is not used, REF02 is a proprietary provider number assigned by the destination payer identified in the Payer Name loop, Loop ID-2010BB, associated with this claim.

    If REF04 is used, REF02 is a proprietary provider number assigned by the non-destination payer identified in the Other Payer Name loop, Loop ID-2330B, associated with this claim.
TR3 Example:
REF✱A6✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
A6
Provider Identifier
Use when reporting a proprietary provider number by the non-destination payer identified in the Other Payer Name Loop ID-2330B for this iteration of Loop ID-2320. This is true regardless of whether that payer is a government, private, commercial, or any other payer.
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
Not Used
3
352
Description
X 1
AN
1/80
Situational
4
C040
Reference Identifier
O 1
To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier
SEMANTIC: REF04 contains data relating to the value cited in REF02.
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C04003 or C04004 is present, then the other is required.
  2. P0506
    If either C04005 or C04006 is present, then the other is required.
SITUATIONAL RULE: Required when the identifier reported in REF02 of this segment is for a non-destination payer.
Required
4-1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
2U
Payer Identification Number
Required
4-2
127
Reference Identification
M 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
INDUSTRY NAME: Other Payer Responsibility Sequence Code
  1. The value reported in this field must match the corresponding Other Payer Responsibility Sequence Code reported in Loop ID-2320 SBR01.
  2. Maximum length of this element is constrained by B.1.1.3.1.
Not Used
4-3
128
Reference Identification Qualifier
X 1
ID
2/3
Not Used
4-4
127
Reference Identification
X 1
AN
1/80
Not Used
4-5
128
Reference Identification Qualifier
X 1
ID
2/3
Not Used
4-6
127
Reference Identification
X 1
AN
1/80

NM1*77 - SERVICE LOCATION NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Loop 2420 contains information about the service line providers including, but not limited to: rendering, referring and attending. These segments override the information in the claim - level segments if the entity identifier codes in each NM1 segment are the same.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when the name and/or the address of Service Location is different than that carried in Loop ID-2310C Service Location
AND
the Service Location is not a subpart of the Billing Provider with its own unique NPI.

OR

Required when Loop ID-2310C is Not Used
AND
the Service Location is not a subpart of the Billing Provider with its own unique NPI
AND
the name and/or the address of Service Location is different than that carried in Loop ID-2010AA Billing Provider. If not required by this implementation guide, do not send.
TR3 Notes:
When an organization health care provider's NPI is provided to identify the Service Location, the organization health care provider must be external to the entity identified as the Billing Provider (for example, reference lab). It is not permissible to report an organization health care provider NPI as the Service Location if the entity being identified is a component (for example, subpart) of the Billing Provider. In that case, the subpart must be the Billing Provider.
TR3 Example:
NM1✱77✱2✱ABC CLINIC✱✱✱✱✱XX✱1234567891~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
77
Service Location
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
2
Non-Person Entity
Situational
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
SITUATIONAL RULE: Required when the Service Location is an organization health care provider. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Location Name
Not Used
4
1036
Name First
O 1
AN
1/35
Not Used
5
1037
Name Middle
O 1
AN
1/25
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Not Used
7
1039
Name Suffix
O 1
AN
1/10
Situational
8
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when NM109 is used. If not required by this implementation guide, do not send.
CODE
DEFINITION
XX
Standard Unique Health Identifier for Health Care Providers (NPI)
CODE SOURCE: 537: National Provider Identifier (NPI)
Situational
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when the service location to be identified has an NPI and is not a component or subpart of the Billing Provider entity.If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Location Primary Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

N3 - SERVICE LOCATION ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
If service location is in an area where there are no street addresses, enter a description of the location (for example, "crossroad of State Road 34 and 45" or "Exit near Mile marker 265 on Interstate 80").
TR3 Example:
N3✱123 MAIN STREET~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Service Location Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when a second address line is needed. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Location Address Line

N4 - SERVICE LOCATION CITY, STATE, ZIP CODE

X12 Name:
Geographic Location
X12 Purpose:
To specify the geographic place of the named party
X12 Syntax:
  1. E0207
    Only one of N402 or N407 may be present.
  2. E0308
    Only one of N403 or N408 may be present.
  3. C0605
    If N406 is present, then N405 is required.
  4. C0704
    If N407 is present, then N404 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
N4✱KANSAS CITY✱MO✱641051909~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
INDUSTRY NAME: Service Location City Name
Situational
2
156
State or Province Code
X 1
ID
2
Code specifying the Standard State/Province as defined by appropriate government agency
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Location State or Province Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
X 1
ID
3/15
Code specifying international postal zone code excluding punctuation and blanks (zip code for United States)
COMMENT: N403 contains the postal code in an unstructured format. N408 contains the postal code in a structured format. When a postal code data field is used, the parties shall agree as to which data element (N403 or N408) shall be used in the transaction set.
SEGMENT SYNTAX: E0308
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada, or when a postal code exists for the country in N404. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Location Postal Zone or ZIP Code
When reporting the ZIP code for U.S. addresses, the full nine digit ZIP code must be provided.
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
X 1
ID
2/3
Code identifying the country
SEGMENT SYNTAX: C0704
SITUATIONAL RULE: Required when the address is outside the United States of America. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Location Country Code
Use the alpha-2 country codes from Part 1 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
5
309
Location Qualifier
X 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
X 1
ID
1/3
Code identifying the country subdivision
SEGMENT SYNTAX: E0207, C0704
SITUATIONAL RULE: Required when the address is not in the United States of America, including its territories, or Canada, and the country in N404 has administrative subdivisions such as but not limited to states, provinces, cantons, etc. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Location Country Subdivision Code
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
8
1702
Postal Code-Formatted
X 1
AN
3/20

REF - SERVICE LOCATION SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
20
Situational Rule:
Required when NM109 of this loop is not used,
AND
the Billing Provider Loop ID-2010AA NM109 is not used,
AND
an identifier is necessary for the receiver to identify the provider. If not required by this implementation guide, do not send.
TR3 Notes:
If REF04 is not used, REF02 is a proprietary provider number assigned by the destination payer identified in the Payer Name loop, Loop ID-2010BB, associated with this claim.

If REF04 is used, REF02 is a proprietary provider number assigned by the non-destination payer identified in the Other Payer Name loop, Loop ID-2330B, associated with this claim.
TR3 Example:
REF✱A6✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
A6
Provider Identifier
Use when reporting a proprietary provider number assigned by the destination payer identified in the Payer Name loop, Loop ID-2010BB, associated with this claim
OR
Use when reporting a proprietary provider number assigned by the non-destination payer identified in REF04-02 of this segment. This is true regardless of whether that payer is a government, private, commercial or any other payer.
LU
Location Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Service Location Secondary Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Situational
4
C040
Reference Identifier
O 1
To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier
SEMANTIC: REF04 contains data relating to the value cited in REF02.
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C04003 or C04004 is present, then the other is required.
  2. P0506
    If either C04005 or C04006 is present, then the other is required.
SITUATIONAL RULE: Required when the identifier reported in REF02 of this segment is for a non-destination payer.
Required
4-1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
2U
Payer Identification Number
Required
4-2
127
Reference Identification
M 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
INDUSTRY NAME: Other Payer Responsibility Sequence Code
  1. The value reported in this field must match the corresponding Other Payer Responsibility Sequence Code reported in Loop ID-2320 SBR01.
  2. Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
4-3
128
Reference Identification Qualifier
X 1
ID
2/3
Not Used
4-4
127
Reference Identification
X 1
AN
1/80
Not Used
4-5
128
Reference Identification Qualifier
X 1
ID
2/3
Not Used
4-6
127
Reference Identification
X 1
AN
1/80

SVD - LINE ADJUDICATION INFORMATION

X12 Name:
Service Line Adjudication
X12 Purpose:
To convey service line adjudication information for coordination of benefits between the initial payers of a health care claim and all subsequent payers
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when the claim has been previously adjudicated by the payer identified in Loop ID-2330B and this service line has payments and/or adjustments applied to it. If not required by this implementation guide, do not send.
TR3 Notes:
Refer to Section 1.4.2.3 Coordination of Benefits - Service Line Procedure Code Bundling and Unbundling.
TR3 Example:
SVD✱1✱50.5✱AD:D0330✱✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1138
Payer Responsibility Sequence Number Code
M 1
ID
1
Code identifying the insurance carrier's level of responsibility for a payment of a claim
SEMANTIC: SVD01 is the payer identification code.
INDUSTRY NAME: Other Payer Responsibility Sequence Code
The value reported in this field must match the corresponding Other Payer Responsibility Sequence Code reported in Loop ID-2320 SBR01.
Required
2
782
Monetary Amount
M 1
R
1/18
Monetary amount
SEMANTIC: SVD02 is the amount paid for this service line.
INDUSTRY NAME: Service Line Paid Amount
  1. Zero "0" is an acceptable value for this element.
  2. Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
Required
3
C003
Composite Medical Procedure Identifier
O 1
To identify a medical procedure by its standardized codes and applicable modifiers
COMMENT: SVD03 represents the medical procedure code upon which adjudication of this service line was based. This may be different than the submitted medical procedure code.
X12 COMPOSITE SEMANTIC NOTES:
  1. C003-01 qualifies C003-02 and C003-08.
  2. If C003-08 is used, then C003-02 represents the beginning value in the range in which the code occurs.
  3. C003-03 modifies the value in C003-02 and C003-08.
  4. C003-04 modifies the value in C003-02 and C003-08.
  5. C003-05 modifies the value in C003-02 and C003-08.
  6. C003-06 modifies the value in C003-02 and C003-08.
  7. C003-07 is the description of the procedure identified in C003-02.
  8. C003-08 represents the ending value in the range in which the code occurs.
  9. C003-09 modifies the value in C003-02 and C003-08.
  10. C003-10 modifies the value in C003-02 and C003-08.
  11. C003-11 modifies the value in C003-02 and C003-08.
  12. C003-12 modifies the value in C003-02 and C003-08.
This element contains the procedure code that was used to adjudicate this service line.
Required
3-1
235
Product/Service ID Qualifier
M 1
ID
2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
INDUSTRY NAME: Product or Service ID Qualifier
CODE
DEFINITION
AD
American Dental Association Codes
CODE SOURCE: 135: American Dental Association
ER
Jurisdiction Specific Procedure and Supply Codes
Use when applicable for Property & Casualty claims
CODE SOURCE: 576: Workers Compensation Specific Procedure and Supply Codes
Required
3-2
234
Product/Service ID
M 1
AN
1/80
Identifying number for a product or service
INDUSTRY NAME: Procedure Code
Situational
3-3
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when the adjudicated procedure code includes a procedure code modifier reported by the payer. If not required by this implementation guide, do not send.
This is the first procedure code modifier.

A modifier must be from code source 135 (American Dental Association) found in the 'Code on Dental Procedures and Nomenclature'.
Situational
3-4
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when the adjudicated procedure code includes a procedure code modifier reported by the payer. If not required by this implementation guide, do not send.
This is the second procedure code modifier.

A modifier must be from code source 135 (American Dental Association) found in the 'Code on Dental Procedures and Nomenclature'.
Situational
3-5
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when the adjudicated procedure code includes a procedure code modifier reported by the payer. If not required by this implementation guide, do not send.
This is the third procedure code modifier.

A modifier must be from code source 135 (American Dental Association) found in the 'Code on Dental Procedures and Nomenclature'.
Situational
3-6
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when the adjudicated procedure code includes a procedure code modifier reported by the payer. If not required by this implementation guide, do not send.
This is the fourth procedure code modifier.

A modifier must be from code source 135 (American Dental Association) found in the 'Code on Dental Procedures and Nomenclature'.
Not Used
3-7
352
Description
O 1
AN
1/80
Not Used
3-8
234
Product/Service ID
O 1
AN
1/80
Not Used
3-9
1339
Procedure Modifier
O 1
AN
2
Not Used
3-10
1339
Procedure Modifier
O 1
AN
2
Not Used
3-11
1339
Procedure Modifier
O 1
AN
2
Not Used
3-12
1339
Procedure Modifier
O 1
AN
2
Not Used
4
234
Product/Service ID
O 1
AN
1/80
Required
5
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: SVD05 is the paid units of service.
INDUSTRY NAME: Paid Service Unit Count
  1. This is the number of paid units from the remittance advice. When paid units are not present on the paper remittance advice or known by the provider, the value must be one.
  2. The maximum length for this field is 8 digits excluding the decimal. When a decimal is used, the maximum number of digits allowed to the right of the decimal is three. A negative value is not allowed.
Situational
6
554
Assigned Number
O 1
N
1/9
Number assigned for differentiation within a transaction set
COMMENT: SVD06 is only used for bundling of service lines. It references the LX Assigned Number of the service line into which this service line was bundled.
SITUATIONAL RULE: Required when payer bundled this service line. If not required by this implementation guide, do not send.
INDUSTRY NAME: Bundled Line Number

RAS - SERVICE ADJUSTMENT INFORMATION

X12 Name:
Reason Adjustment
X12 Purpose:
To supply Claim Adjustment Reason Codes and amounts as needed for an entire claim or for a particular service within the claim being paid
X12 Comments:
Adjustment information is intended to help the provider balance the remittance information. Adjustment amounts must fully explain the difference between submitted charges and the amount paid.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
99
Situational Rule:
Required when the payer identified in this Line Adjudication Information Loop ID-2430 made line level adjustments which caused the dollar amount paid for the service line (SVD02) to differ from the amount originally charged for this service. If not required by this implementation guide, do not send.
TR3 Example:
RAS✱125.32✱PR✱1~RAS✱25✱PR✱3~RAS✱200✱CO✱6^7~RAS✱500✱CO✱45:HE:MA01~RAS✱1225✱CO✱16:HE:M24^15:HE:N517✱2~RAS✱2225✱CO✱16:HE:M44:M45:M49^146:HE:MA63:MA65~RAS✱2100✱OA✱18:HE:N522:N702~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
782
Monetary Amount
M 1
R
1/18
Monetary amount
SEMANTIC: RAS01 is the amount of adjustment.
INDUSTRY NAME: Adjustment Amount
  1. This monetary amount is the adjustment amount. A negative amount increases the payment, and a positive amount decreases the payment. This amount must not be zero (0).
  2. Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
Required
2
1785
Claim Adjustment Group Code
M 1
AN
1/10
Code identifying the general category of payment adjustment.
CODE SOURCE 974: Claim Adjustment Group Codes
Required
3
C058
Adjustment Reason
M 15
To provide a reason and related explanation for a Health Care Claim or Service change in payment versus the original submitted charges
SEMANTIC: Position of data in the repeating composite data element conveys no significance.
X12 COMPOSITE SYNTAX NOTES:
  1. P0203
    If either C05802 or C05803 is present, then the other is required.
  2. C0403
    If C05804 is present, then C05803 is required.
  3. C0504
    If C05805 is present, then C05804 is required.
  4. C0605
    If C05806 is present, then C05805 is required.
  5. C0706
    If C05807 is present, then C05806 is required.
X12 COMPOSITE SEMANTIC NOTES: C05802 qualifies C05803, C05804, C05805, C05806 and C05807.
  1. This composite identifies the reason for the adjustment of the dollar amount identified in RAS01.
  2. More than one iteration of this composite may only be provided when the entire service submitted charge is being adjusted by this RAS segment and there are multiple adjustment reasons that are each applicable for the adjustment of that full amount in RAS01.
Required
3-1
1034
Claim Adjustment Reason Code
M 1
ID
1/5
Code identifying the detailed reason the adjustment was made
INDUSTRY NAME: Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Situational
3-2
1270
Code List Qualifier Code
X 1
ID
1/3
Code identifying a specific industry code list
COMPOSITE SYNTAX: P0203
SITUATIONAL RULE: Required when provided in the RAS Segment of the 835 for the payer identified in the Loop ID-2430 SVD01. If not required by this implementation guide, do not send.
CODE
DEFINITION
HE
Remittance Advice Remark Code
CODE SOURCE: 411: Remittance Advice Remark Code
RM
Insurance Industry Specific Remark Codes
CODE SOURCE: 973: Insurance Industry Specific Remark Codes
RX
National Council for Prescription Drug Programs Reject Codes
CODE SOURCE: 530: National Council for Prescription Drug Programs Reject Codes
Situational
3-3
1271
Industry Code
X 1
AN
1/30
Code indicating a code from a specific industry code list
COMPOSITE SYNTAX: P0203, C0403
SITUATIONAL RULE: Required when provided in the RAS Segment of the 835 for the payer identified in the Loop ID-2430 SVD01. If not required by this implementation guide, do not send.
INDUSTRY NAME: Remark Code
Situational
3-4
1271
Industry Code
X 1
AN
1/30
Code indicating a code from a specific industry code list
COMPOSITE SYNTAX: C0403, C0504
SITUATIONAL RULE: Required when provided in the RAS Segment of the 835 for the payer identified in the Loop ID-2430 SVD01. If not required by this implementation guide, do not send.
INDUSTRY NAME: Remark Code
Situational
3-5
1271
Industry Code
X 1
AN
1/30
Code indicating a code from a specific industry code list
COMPOSITE SYNTAX: C0504, C0605
SITUATIONAL RULE: Required when provided in the RAS Segment of the 835 for the payer identified in the Loop ID-2430 SVD01. If not required by this implementation guide, do not send.
INDUSTRY NAME: Remark Code
Situational
3-6
1271
Industry Code
X 1
AN
1/30
Code indicating a code from a specific industry code list
COMPOSITE SYNTAX: C0605, C0706
SITUATIONAL RULE: Required when provided in the RAS Segment of the 835 for the payer identified in the Loop ID-2430 SVD01. If not required by this implementation guide, do not send.
INDUSTRY NAME: Remark Code
Situational
3-7
1271
Industry Code
O 1
AN
1/30
Code indicating a code from a specific industry code list
COMPOSITE SYNTAX: C0706
SITUATIONAL RULE: Required when provided in the RAS Segment of the 835 for the payer identified in the Loop ID-2430 SVD01. If not required by this implementation guide, do not send.
INDUSTRY NAME: Remark Code
Situational
4
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: RAS04 is the units of service being adjusted.
SITUATIONAL RULE: Required when the number of service units has been adjusted. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Quantity
A positive value decreases the quantity, and a negative value increases the quantity.

DTP*573 - PAYMENT EFFECTIVE DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
DTP✱573✱D8✱20221030~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
573
Date Claim Paid
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Payment Effective Date

AMT*B6 - SERVICE ALLOWED AMOUNT

X12 Name:
Monetary Amount Information
X12 Purpose:
To indicate the total monetary amount
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when submitting a Coordination of Benefits (COB) claim, and:

The Other Payer referenced in SVD01 (of this iteration of Loop ID-2430) has adjudicated this claim and provided the 835 with line level allowed amount information to the submitter.

OR

The Other Payer identified in SVD01 (of this iteration of Loop ID-2430) has adjudicated this claim and the submitter received a paper, virtual, or other alternate format of remittance advice with the allowed amount reported.

OR

The Other Payer referenced in SVD01 (of this iteration of Loop ID-2430) is the same as the submitter reported in Loop ID-1000A.

If not required by this implementation guide, do not send.
TR3 Notes:
  1. This is the 835 Loop ID-2110 Claim Allowed Amount (AMT02) when the remittance information is reported on an 835.
  2. This is the service line allowed amount when remittance information is reported using other formats.
  3. This amount is not sent if it is not explicitly available on an 835 or other remittance. If the allowed amount is not available, do not calculate the amount.
  4. When the service line allowed amount is zero dollars, report zero (0).
TR3 Example:
AMT✱B6✱425~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
522
Amount Qualifier Code
M 1
ID
1/3
Code specifying the amount qualifier
CODE
DEFINITION
B6
Allowed - Actual
Required
2
782
Monetary Amount
M 1
R
1/18
Monetary amount
INDUSTRY NAME: Service Allowed Amount
Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
Not Used
3
478
Credit/Debit Flag Code
O 1
ID
1

AMT*EAF - REMAINING PATIENT LIABILITY AMOUNT

X12 Name:
Monetary Amount Information
X12 Purpose:
To indicate the total monetary amount
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the Other Payer identified in SVD01 of this iteration of Loop ID 2430 has adjudicated the claim,

AND

The claim level (Loop ID-2320) Remaining Patient Liability AMT segment for this other payer is not used,

AND

The provider has the ability to report line item information,

AND

In the provider's opinion, the amount billable to the patient, is different than the sum of the amounts (RAS01) associated with Patient Responsibility (PR) Claim Adjustment Group Code (RAS02) in this 2430 loop. If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver.
TR3 Notes:
  1. This segment is not used in Payer-to-Payer Coordination of Benefits (COB).
  2. In the judgment of the provider, this is the remaining amount to be paid after adjudication by the Other Payer referenced in SVD01 of this iteration of Loop ID-2430.
  3. This segment is not used if the claim level (Loop ID-2320) Remaining Patient Liability AMT segment is used for this Other Payer.
TR3 Example:
AMT✱EAF✱75~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
522
Amount Qualifier Code
M 1
ID
1/3
Code specifying the amount qualifier
CODE
DEFINITION
EAF
Amount Owed
Required
2
782
Monetary Amount
M 1
R
1/18
Monetary amount
INDUSTRY NAME: Remaining Patient Liability
Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
Not Used
3
478
Credit/Debit Flag Code
O 1
ID
1

LQ - HEALTH CARE REMARK CODES

X12 Name:
Industry Code Identification
X12 Purpose:
To identify standard industry codes
X12 Syntax:
C0102
If LQ01 is present, then LQ02 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
99
Situational Rule:
Required when returned in the remittance advice. If not required by this implementation guide, do not send.
TR3 Notes:
Remark codes from a paper remittance advice are reported in this Segment.
TR3 Example:
LQ✱HE✱MA15~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1270
Code List Qualifier Code
O 1
ID
1/3
Code identifying a specific industry code list
SEGMENT SYNTAX: C0102
CODE
DEFINITION
HE
Remittance Advice Remark Code
CODE SOURCE: 411: Remittance Advice Remark Code
RM
Insurance Industry Specific Remark Codes
CODE SOURCE: 973: Insurance Industry Specific Remark Codes
RX
National Council for Prescription Drug Programs Reject Codes
CODE SOURCE: 530: National Council for Prescription Drug Programs Reject Codes
Required
2
1271
Industry Code
X 1
AN
1/30
Code indicating a code from a specific industry code list
SEGMENT SYNTAX: C0102
INDUSTRY NAME: Remark Code

SE - TRANSACTION SET TRAILER

X12 Name:
Transaction Set Trailer
X12 Purpose:
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
X12 Comments:
SE is the last segment of each transaction set.
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
SE✱1230✱0002~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
96
Number of Included Segments
M 1
N
1/10
Total number of segments included in a transaction set including ST and SE segments
INDUSTRY NAME: Transaction Segment Count
Required
2
329
Transaction Set Control Number
M 1
AN
4/9
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
The Transaction Set Control Number in ST02 and SE02 must be identical.

GE - FUNCTIONAL GROUP TRAILER

X12 Name:
Functional Group Trailer
X12 Purpose:
To indicate the end of a functional group and to provide control information
X12 Comments:
The use of identical data interchange control numbers in the associated functional group header and trailer is designed to maximize functional group integrity. The control number is the same as that used in the corresponding header.
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
GE✱1✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
97
Number of Transaction Sets Included
M 1
N
1/6
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Required
2
28
Group Control Number
M 1
N
1/9
Assigned number originated and maintained by the sender
SEMANTIC: The data interchange control number GE02 in this trailer must be identical to the same data element in the associated functional group header, GS06.

IEA - INTERCHANGE CONTROL TRAILER

X12 Name:
Interchange Control Trailer
X12 Purpose:
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
IEA✱1✱000000905~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
I16
Number of Included Functional Groups
M 1
N
1/5
A count of the number of functional groups included in an interchange
Required
2
I12
Interchange Control Number
M 1
N
9
A control number assigned by the interchange sender
The Value in IEA02 must be identical to the value in ISA13.
logo

837 Health Care Claim: Dental (008020X325)

SEPTEMBER 2021

Copyright © 2008-21, X12 Incorporated, Format © 2008-21 Washington Publishing Company. Exclusively published by the Washington Publishing Company. No part of this publication may be distributed, posted, reproduced, stored in a retrieval system, or transmitted in any form or by any means without the prior written permission of the copyright owner.

All rights reserved.

Abstract

The Health Care Claim: Dental Implementation Guide describes the use of the X12 Health Care Claim (837) transaction set to submit and transfer dental claims and encounters to primary, secondary, and subsequent payers.

Trading partners include but are not limited to:

  • Health care providers, such as physicians, practitioners, and suppliers
  • Health care and property/casualty (including workers' compensation payers)
  • Clearinghouses, repricers, VANS, etc.

Preface

X12 standards are developed to identify the broadest data requirements for a transaction set. Type 3 Technical Reports (TR3), also known as implementation guides, define the explicit data requirements for a specific business purpose. Trading partners who implement according to the instructions in this TR3 can exchange data consistently with multiple trading partners.

As X12 does not define transport requirements, trading partners define their specific transport requirements separately.

1.1 Implementation Purpose and Scope

For the health care industry to achieve the potential administrative cost savings with Electronic Data Interchange (EDI), standards have been developed to facilitate consistent implementation by all organizations. To facilitate a smooth transition into the EDI environment, uniform implementation is critical.

This is the technical report document for the X12N 837 Health Care Claims (837) transaction for dental claims, encounters, and/or requests for predetermination of benefits (estimates). Unless noted otherwise, the term "claim" in this guide applies to all these uses. See the X12 Wordbook for definitions. This document provides a definitive statement of what trading partners must be able to support in this version of the 837.

1.2 Version Information

This implementation guide is based on the October 2020 X12 standards, referred to as Version 8, Release 2 (008020).

The unique Version/Release/Industry Identifier Code for transaction sets that are defined by this implementation guide is 008020X325.

The two-character Functional Identifier Code for the transaction set included in this implementation guide:

  • HC   Health Care Claim (837)

The Version/Release/Industry Identifier Code and the applicable Functional Identifier Code must be transmitted in the Functional Group Header (GS segment) that begins a functional group of these transaction sets. For more information, see the descriptions of GS01 and GS08 in Appendix C EDI Control Directory.

1.3.1 Batch and Real-Time Usage

There are multiple methods available for sending and receiving business transactions electronically. Two common modes for EDI transactions are batch and real-time.

Batch - In a batch mode the sender does not remain connected while the receiver processes the transactions. Processing is usually completed according to a set schedule. If there is an associated business response transaction (such as a 271 Response to a 270 Request for Eligibility), the receiver creates the response transaction and stores it for future delivery or transmits the response transaction back to the sender of the original transaction. The sender of the original transmission reconnects at a later time and picks up the response transaction. Note: The sender of the original transmission may not always be the entity that picks up the response transaction at a later time (e.g. Provider submitting through a clearinghouse.)

Real-Time - In real-time mode the sender remains connected while the receiver processes the transactions and returns a response transaction to the sender. This implementation guide does not set specific response time parameters for implementers.

This implementation guide was based on requirements for batch mode. Willing trading partners may use batch or real-time mode.

1.3.2 Other Usage Limitations

When processing in batch mode, receiving trading partners may have system limitations which control the size of the transmission they can receive. Some submitters may have the capability and the desire to transmit large 837 transactions with thousands of claims contained in them. The developers of this implementation guide recommend that trading partners limit the size of the transaction (ST-SE envelope) to a maximum of 5000 CLM segments. Willing trading partners can agree to higher limits. There is no recommended limit to the number of ST-SE transactions within a GS-GE or ISA-IEA.

When a claim is processed in real-time, only one CLM per ISA/IEA is allowed and must be responded to in a single communication session.

1.4 Business Usage

This transaction set can be used to submit health care claim billing information, encounter information, or requests for predetermination from providers of health care services to payers, either directly or via intermediary billing services and claims clearinghouses. It can also be used to transmit health care claims and billing payment information between payers with different payment responsibilities where coordination of benefits (COB) is required or between payers and regulatory agencies to monitor the rendering, billing, and/or payment of health care services within a specific health care/insurance industry segment.

For purposes of this standard, providers of health care products or services may include entities such as physicians, dentists, hospitals, pharmacies, other medical facilities or suppliers, and entities providing medical information to meet regulatory requirements. The payer is a third party entity that pays claims or administers the insurance product or benefit or both. For example, a payer may be an insurance company, health maintenance organization (HMO), preferred provider organization (PPO), government agency (Medicare, Medicaid, TRICARE, etc.) or an entity such as a third party administrator (TPA), repricer, or third party organization (TPO) that may be contracted by one of those groups. A regulatory agency is an entity responsible, by law or rule, for administering and monitoring a statutory benefits program or a specific segment of the health care/insurance industry.

The transaction defined by this implementation guide is generally intended to originate with the health care provider or health care provider's designated agent. In some instances, a health care payer may originate an 837 to report a health care encounter to another payer or sponsoring organization. In other cases, where a Factoring Agent is involved, the Factoring Agent, who has acquired the ownership of the receivable, but has not provided the medical service or product related to a claim, may originate an 837 to another payer for reimbursement. The 837 Transaction provides all necessary information to allow the destination payer to at least begin to adjudicate the claim. The 837 coordinates with a variety of other transactions including, but not limited to, the following: Health Care Status Notification (277), Health Care Claim Payment/Advice (835) and the Implementation Acknowledgment (999). See Section 1.6 - Transaction Acknowledgments, and Section 1.7 - Related Transactions, for a summary description of these interactions.

NOTE:
The 837 is not intended for use in exchanging referrals and certifications. Use the 278 Health Care Services Review - Request for Review and Response transaction instead.

1.4.1 Health Care Transaction Flow

Each X12 implementation guide explains how to use X12 transaction sets to meet a single defined business purpose. The diagrams found at https://www.x12.org/flow depict the business functions supported by the X12 health care implementation guides.

1.4.2 Coordination of Benefits

Note:
This section does not apply to predetermination requests.

COB functionality supported in this implementation guide minimizes manual intervention and/or the necessity for paper supporting documentation. Electronic COB is predicated upon using two transactions – the 837 and the 835 Health Care Claim Payment/Advice. See Section 1.4.2.1 - Coordination of Benefits Data Models - Detail for information about using these transactions to achieve a totally electronic interchange of COB information. Refer to Chapter 3, for information on examples. Section 1.4.2.2 - Coordination of Benefits Claims from Paper or Proprietary Remittance Advices provides guidance on creating electronic COB claims when the payer's remittance was a paper or proprietary remittance advice.

1.4.2.1 Coordination of Benefits Data Models - Detail

The 837 Transaction handles two different models of benefit coordination. Both models are discussed in this section. Section 3, Examples, contains detailed examples of the Provider-to-Payer-to-Provider model. Each COB related data element contains notes within this implementation guide specifying when it is used. The HIPAA final rules contain additional information on COB.

Since prior implementation guides used the CAS segment for adjustments at both the claim and service levels, there will be a need to convert to the RAS segment when implementing this guide's instructions.

The CAS segment supported up to six separate adjustments (amount, CARC and quantity) consistent with a single Claim Adjustment Group Code. The RAS segment supports only one adjustment per segment. As a result, converting from the CAS to the RAS will involve the creation of more RAS segments than the number of CAS segments in prior versions. There is a one to one relationship between a CAS amount, CARC and quantity trio and a single RAS segment.

In prior versions that used the CAS segment, Remark Codes that were related to an adjustment were reported in the MIA or MOA segment at the claim level or the LQ segment at the service level. With the RAS segment, the Remark Codes must now be associated directly with the related CARC, when a relationship to a specific CARC exists. This change requires a modification from a business perspective and is not a simple mapping change. This change clarifies the fact that Remark Codes serve multiple functions within the 835 transaction. Sometimes they are related to a CARC and are a critical part of the message of a specific RAS segment/CARC. Other times they have no correlation to the RAS segment and provide additional information that is part of the general claim or service adjudication message.

Whenever a Remark Code is associated with a CARC or a CARC requires the presence of a Remark Code, the Remark Code must be reported in the RAS03 composite data structure with the CARC. Remark Codes that are not associated with a specific CARC must still be reported in the LQ segment.

Model 1 – Provider-to-Payer-to-Provider

Step 1. In model 1, the provider originates the transaction and sends the claim information to Payer A, the primary payer. See Figure 1.1 - Provider-to-Payer-to-Provider COB Model. The Subscriber loop (Loop ID-2000B) contains information about the person who holds the policy with Payer A. Loop ID-2320 contains information about Payer B and the subscriber who holds the policy with Payer B. In this model, the primary payer adjudicates the claim and sends an electronic remittance advice (RA) transaction (835) back to the provider. The 835 contains any claim adjustment reason codes that apply to that specific claim. The claim adjustment reason codes detail what was adjusted and why.

Figure 1.1 - Provider-to-Payer-to-Provider COB Model

Provider-to-Payer-to-Provider COB Model

Step 2. Upon receipt of the 835, the provider sends a second health care claim transaction (837) to Payer B, the secondary payer. The Subscriber loop (Loop ID-2000B) now contains information about the subscriber who holds the policy with Payer B. The Other Subscriber Information loop (Loop ID-2320) now contains information about the subscriber for Payer A. Any total amounts paid at the claim level go in the AMT segment with qualifier D (Payer Amount Paid) in Loop ID-2320. All claim level adjustment codes are retrieved from the 835 from Payer A and put in the RAS (Claim Adjustment Information) segment in Loop ID-2320. Claim Level Allowed Amounts reported in the 835 are included in an AMT with qualifier B6 (Allowed - Actual) in Loop ID-2320. Line Level adjustment reason codes are retrieved similarly from the 835 and go in the RAS (Service Adjustment Information) segment in the 2430 loop. Line Level Allowed Amounts reported in the 835 are included in an AMT with qualifier B6 in Loop ID-2430. Payer B adjudicates the claim and sends the provider an electronic remittance advice.

Step 3. If there are additional payers (not shown in Figure 1.1 - Provider-to-Payer-to-Provider COB Model), step 2 is repeated with the Subscriber loop (Loop ID-2000B) having information about the subscriber who holds the policy with Payer C, the tertiary payer. COB information specific to Payer A continues to be included as written in step 2 with an occurrence of Loop ID-2320 and specifying the payer as primary. If necessary, Loop ID-2430 is included for any line level adjudications. COB information specific to Payer B is included by repeating the Loop ID-2320 again and specifying the payer as secondary. If necessary, Loop ID-2430 is included for Payer B line level adjudications.

Model 2 – Provider-to-Payer-to-Payer

Step 1. In model 2, the provider originates the transaction and sends claim information to Payer A, the primary payer. See Figure 1.2 - Provider-to-Payer-to-Payer COB Model. The Subscriber loop (Loop ID-2000B) contains information about the person who holds the policy with Payer A. Subscriber/payer information about secondary coverage is included in Loop ID-2320 or is on file at Payer A as a result of an eligibility file sent by Payer B. In this model, the primary payer adjudicates the claim and sends an 835 back to the provider.

Figure 1.2 - Provider-to-Payer-to-Payer COB Model

Provider-to-Payer-to-Payer COB Model

Step 2. All COB information from Payer A is placed in the appropriate Loop ID-2320 and/or Loop ID-2430. In reformatting the claim, Payer A takes the information about their subscriber and places it in Loop ID-2320. Payer A also takes the information about Payer B, the secondary payer/subscriber, and places it in the appropriate fields in the Subscriber Loop ID-2000B. Then Payer A sends the claim to Payer B.

Step 3. Payer B receives the claim from Payer A and adjudicates the claim. Payer B sends an 835 to the provider. If there is a tertiary payer, Payer B performs step 2 in either Model 1 or Model 2.

1.4.2.1.1 Coordination of Benefits - Claim Level

The destination payer's information is located in Loop ID-2010BB. In addition, any destination payer-specific claim information (for example, referral number) is located in the 2300 loop. All provider identifiers in the 2310 loops are specific to the destination payer. Loop ID-2320 occurs once for each payer responsible for the claim, except for the payer receiving the 837 transaction set (destination payer). Provider identifiers in the 2330 loops are specific to the corresponding non-destination payer.

Loop ID-2320 contains the following:

  • claim level adjustments
  • various amounts
  • other payer information
  • assignment of benefits indicator
  • patient signature indicator

Inside Loop ID-2320, Loop ID-2330 contains the information for the payer and the subscriber. As the claim moves from payer to payer, the destination payer's information in Loop ID-2000B and Loop ID-2010BB must be exchanged with the next payer's information from Loop ID-2320/2330.

1.4.2.1.2 Coordination of Benefits - Service Line Level

Loop ID-2430 is a situational loop that can occur up to 15 times for each service line. As each payer adjudicates the service lines, occurrences may be added to this loop to explain how the payer adjudicated the service line.

Loop ID-2430 contains the following:

  • ID of the payer who adjudicated the service line
  • amount paid for the service line
  • procedure code upon which adjudication of the service line was based. This code may be different than the submitted procedure code. (This procedure code also can be used for unbundling or bundling service lines.)
  • paid units of service
  • service level adjustments
  • adjudication date

To enable accurate matching of billed service lines with paid service lines, the payer must return the original billed procedure code(s) and/or modifiers in the SVC06 composite data element of the 835 if they are different from those used to pay the line.

1.4.2.2 Coordination of Benefits Claims from Paper or Proprietary Remittance Advices

Claim submitters may at times need or choose to create electronic secondary/tertiary coordination of benefit (COB) claims to subsequent payers due to regulatory or business relationships when the prior payer's remittance was a paper or proprietary remittance advice. This situation may occur when the prior payer(s) is not a regular trading partner of the claim submitter or the prior payer(s) is a HIPAA non-covered entity and produces a proprietary electronic remittance (e.g., Workers' Compensation).

Provider information systems that have the functionality to generate electronic claim transactions to payers have the majority of the information necessary to create a COB claim. Ideally, payers have adopted usage of the standard codes sets for paper remittance advices or have provided crosswalks for their paper or nonstandard electronic remittances to accommodate creation of COB claims. However, this will not always occur.

When standard codes are not available from a prior payer(s) paper/proprietary remittance advice(s), the COB claim submitter must translate the proprietary adjustment/denial edit messages to standard codes.

Generally, a subsequent COB payer(s) determines payment on a combination of "Group Code" and "Claim Adjustment Reason Code" provided in the RAS segment(s) at either the claim or service line. Group Codes are included in an external code list (see Appendix A for code list reference) and include Patient Responsibility, Contractual Obligation, Payer Initiated, and Other Adjustments.

The Claim Adjustment Reason Code (CARC) is equally important in subsequent payers' determination of payment responsibility. In most instances, paper or proprietary monetary adjustments may easily be cross-walked to the standard CARCs using the CARC list available at https://x12.org/codes/claim-adjustment-reason-codes.

Payment adjustments by the prior payer(s) that are not readily cross-walked to standard CARCs are reported using default CARC 192 (*Nonstandard adjustment code from paper remittance advice).

Submitters must not use default code 192 when a more specific code is available. Some CARCs, such as CARC 96 (*Non-covered charges.), require a Remittance Advice Remark Code (RARC) to further explain the reason for the adjustment. It is important to include the most descriptive CARC available, along with appropriate associated RARCs. Note: Some Claim Adjustment Reason Codes require at least one Remittance Advice Remark Code (RARC) to further explain the reason for adjustment. The claim submitter is responsible for determining the most appropriate Remittance Advice Remark Code to use.

*NOTE - All code descriptions are as of the publication of this book. Please refer to https://x12.org/codes for the most current description.

1.4.2.3 Coordination of Benefits - Subrogation

At the time of this publication, subrogation is not a HIPAA mandated business usage of the X12 837 Health Care Claim; however, willing trading partners may use this Implementation Guide for this purpose.

This Implementation Guide provides the ability for willing trading partners to allow direct billing by one payer to another payer for the purpose of claim subrogation. These pay-to-plan claims are identified by:

  • The BHT06 Value of 31 - Subrogation Demand
    and
  • The inclusion of Loop ID-2010AC Pay-to Plan Name Loop.

The payer seeking payment is also identified in Loop ID-2330B (Other Payer Name). Loop ID-2320 (Other Subscriber Information) and Loop ID-2430 (Line Adjudication Information) includes all required segments to indicate adjudication results of the original claim that was submitted to that payer by the Billing Provider.

For Subrogation claims, the submitting payer's own Payer Claim Control Number is reported in Loop ID-2300 (Claim Information) data element CLM01 (Claim Submitter's Identifier), rather than the Provider's Assigned Claim Identifier. The submitting payer's Payer Claim Control Number is reported here so that the identifier can be carried through for payment re-association purposes.

Receiving payers are to direct information requests about subrogation claims to the submitting payer (as identified in Loop ID-2330B (Other Payer Name)) rather than to the original billing provider.

1.4.2.4 Claim / Service Adjustment Information Segment

The Claim Adjustment Information and Service Adjustment Information Segments (Loop ID 2320 and 2430 RAS segment, which replaces the CAS segment from previous implementation guides) provide the amounts, reasons, and quantities of any adjustments that the prior payer(s) made to the original submitted charge and to the units related to the claim or service(s). The sum of the adjustments at the claim and service level is the total adjustment for the entire claim. Adjustments reported at the Service level (Loop ID 2430) are not repeated at the claim level (Loop ID 2320) and vice versa.

Each RAS segment identifies a single adjustment to the original submitted charge for the claim/service by:

Amount – this is the amount of the adjustment. A positive value reduces the payment; a negative value increases the payment. This is required, and must not be zero.

Adjustment Group Code – identifies and categorizes the general class of the adjustment and any related responsibility from a set of codes in a standard external code list. This is required.

CARC/RARC Composites
The Claim Adjustment Reason Code and the five iterations of the Remark Code are part of a composite data structure. The composite repeats up to fifteen times. More than one iteration of this composite (CARC and Remark Codes) may only be provided when the entire charge amount (claim or service) is being adjusted by the RAS segment and there are multiple adjustment reasons (CARC/Remark Codes) that are each applicable for the adjustment of the full amount in RAS01.

Remark Codes within a specific iteration of the composite are directly related to the CARC in that iteration of the composite. See the RAS segment detail in the 2320 and 2430 loops for complete structural information.

Claim Adjustment Reason Code (CARC) – identifies the reason for the adjustment using a code from a standard external code list. At least one is required.

Additional CARCs can be provided for a single amount, when the amount represents a total adjustment explained by more than 1 reason. Multiple CARCs must all relate to the adjustment amount reported in RAS01 and Group Code reported in RAS02. All CARCs related to the adjustment amount reported in RAS01 must be reported in the RAS segment to eliminate the need for repetitive claim submission and adjustment notification.

Each unique adjustment amount requires its own RAS segment.

If an adjustment amount has only 1 reason, do not combine with any other adjustments in a RAS. For example, patient responsibility amounts for deductible and co-pay would not be combined in one RAS segment, since each has their own individual adjustment amount. Two separate RAS segments are required.

Remark Code – identifies additional information related specifically to a CARC that further clarifies the adjustment reason. Up to five Remark Codes can be associated with each CARC. The Remark Codes can only be from one of the standard external code lists listed in the RAS segment detail in the 2320 and 2430 loops, including the Remittance Advice Remark Code (RARC) external code list, the Insurance Industry Specific Remark Code (IISRC) external code list or the standard NCPDP Reject Codes external code list.

Remark Codes are situational and are required when they are necessary for the provider to fully understand the adjustment message for the claim adjustment reason. Note – when a CARC description requires the presence of a Remark Code to complete the message, that Remark Code must be provided in the related RAS03 composite directly associated with the CARC.

Certain informational Remark Codes can be used without any association to a specific CARC, at either the claim or service level (some of these remark codes begin with the word "ALERT"). Remark codes used without any association to a specific CARC are included in the claim level (2320 loop) or service level (2430 loop) Health Care Remark Codes (LQ) segment.

Adjustment Quantity – This is the non-covered days (2320 loop) or non-covered units of service (2430 loop) when the adjustment amount is related to a reduction in the related units. The Adjustment Quantity is situational and is required when the adjustment is related to non-covered days or units of service. At the Service line level (2430 loop) this element represents adjusted service unit count. The Service level (2430 loop) includes a balancing requirement related to the adjusted service unit count - the submitted Service Units Count minus the Adjustment Quantities (2430 RAS04 elements) must equal the Paid Units of Service (SVD05).

1.4.3 Property & Casualty

Property & Casualty (P&C) is the broad term given to lines of business including, but not limited to, liability, auto medical payment coverage, auto no-fault, homeowners, workers' compensation, boat, recreational vehicle (RV), and all-terrain vehicle (ATV). Most P&C policies carry a medical expense reimbursement benefit as part of the coverage.

For most P&C claim events, member ID's/policy numbers do not necessarily identify the covered persons, since even strangers to the policy (e.g. passengers in the vehicle, customers, and visitors) can receive medical expense reimbursement coverage under a P&C policy. The P&C insurance card identifies the policyholder(s) and the covered vehicle(s)/property. The policy number is rarely used to identify the covered events associated to the submission of a claim (bill). Instead, the P&C claim number is used to tie the bill to a covered event. The claim number is the key to associating the patient to a unique event. It is possible to have more than one patient associated to an event and more than one event per patient, each with unique coverage requirements with its associated limits, as well as any adjudication rules that would apply.

P&C bills or predetermination requests must include both the bill information as well as the information related to the event that caused the injury or illness. Information concerning the event is necessary to associate a bill or predetermination request with the P&C claim event.

P&C insurance is governed by state insurance regulations, statutes, Departments of Labor, Workers' Compensation Boards, or other jurisdictionally defined entities, which often mandate compliance with Jurisdiction-specific procedures.

The date of accident/occurrence/onset of symptoms (Date of Loss) is a critical piece of information and must always be transmitted in the Accident Date DTP segment within Loop ID-2300 (Claim loop). The Date of Loss is used to determine the eligibility of coverage for the unique claim event.

The unique identification number assigned by the payer for the specific event, referred to in P&C as a claim number, must be provided. The claim number is transmitted in the Property & Casualty Claim Number REF segment of Loop ID-2010BA if the patient is the subscriber or Loop ID-2010CA if the patient is not the subscriber.

Failure to submit the required Accident Date and Property & Casualty Claim Number is inconsistent with the TR3 and will result in the claim being rejected or delayed in the adjudication process depending on the business practices of the payer.

When sending an appeal or reconsideration Property & Casualty bill, it is important to indicate that the bill is a replacement bill in CLM05-03 with a value of 7, and to include the payer's claim control number of the original bill in the Payer Claim Control Number REF segment in Loop ID-2300.

The insured reported in the Subscriber detail segments may be a non-person such as an employer or a business.

1.4.4 Data Overview

The data overview introduces the 837 transaction set structure and describes the positioning of business data within the structure. For a review of X12 nomenclature, segments, data elements, hierarchical levels, and looping structure, see Appendix B, X12 Control and Guidance, and Appendix C, EDI Control Directory.

1.4.4.1 Loop Labeling, Sequence, and Use

The 837 transaction uses two naming conventions for loops. Loops are labeled with a descriptive name as well as with a shorthand label. Loop ID-2000A BILLING PROVIDER contains information about the billing provider, pay-to address and pay-to plan. The descriptive name – BILLING PROVIDER – informs the user of the overall focus of the loop. The Loop ID is a short-hand name, for example 2000A, that gives, at a glance, the position of the loop within the overall transaction. Loop ID-2010AA BILLING PROVIDER NAME, Loop ID-2010AB PAY-TO ADDRESS, and Loop ID-2010AC PAY-TO PLAN NAME are sub loops of Loop ID-2000A. When a loop is used more than once, a letter is appended to its numeric portion to allow the user to distinguish the various iterations of that loop when using the shorthand name of the loop. For example, loop 2000 has three possible iterations: Billing Provider Hierarchical Level (HL), Subscriber HL and Patient HL. These loops are labeled 2000A, 2000B and 2000C respectively. Under this guide, the hierarchical levels must be looked at as nested loops and constructed in that fashion, where 2000A is the highest level loop, 2000B is nested inside of 2000A and 2000C is nested inside of 2000B.

The order of multiple subloops that do not involve hierarchical structure and that do have the same numeric position within the transaction is less important. Such subloops do not need to be sent in the same order in which they appear in this implementation guide. For such subloops in this transaction, the numeric portion of the loop ID does not end in 00. For example, Loop ID-2010 has two possibilities within Loop ID-2000B (Loop ID-2010BA Subscriber Name and Loop ID-2010BB Payer Name). Each of these 2010 loops is at the same numeric position in the transaction. Since they do not specify an HL, it is not necessary to use them in any particular order. However, it is not acceptable to send subloop 2330 before loop 2310 because these are not equivalent subloops.

In a similar manner, if a single loop has multiple iterations (repetitions) of a particular segment, the sequence of those segments within a transaction is not important and is not required to follow the same order in which they appear in this implementation guide. For example, there are many DTP segments in the 2300 loop. It is not required that Accident Date be sent before Service Date. However, it is required that the DTP segment in the 2300 loop come after the CLM segment because it is carried in a different position within the 2300 loop.

1.4.4.2 Data Use by Business Use

The 837 is divided into two tables. Table 1 contains transaction control information and is described in Section 1.4.4.2.1 - Table 1 - Transaction Control Information. Table 2 contains the detail information for the transaction's business function and is described in Section 1.4.4.2.2 - Table 2 - Detail Information.

1.4.4.2.1 Table 1 - Transaction Control Information

Table 1 is named the Header level (see Figure 1.3 - Header Level). Table 1 identifies the start of a transaction, the specific transaction set, the transaction's business purpose, and the submitter/receiver identification numbers.

Figure 1.3 - Header Level

Header Level

1.4.4.2.1.1 Transaction Set Header (ST) Segment

The Transaction Set Header (ST) segment identifies the transaction set by using 837 as the data value for the transaction set identifier code data element, ST01. The transaction set originator assigns the unique transaction set control number that is contained in ST02.

Because the 837 is multi-functional, it is important for the receiver to know which business purpose is served. ST03 contains a reference to the specific implementation guide used to create this 837 transaction.

1.4.4.2.1.2 Beginning of Hierarchical Transaction (BHT) Segment

The BHT segment indicates that the transaction uses a hierarchical data structure. The data elements within the BHT are used in the following way:

  • BHT01 - The Hierarchical Structure Code designates the type of business data within each hierarchical level. The 0019 value used in the claim BHT01 specifies the order of subsequent hierarchical levels to be:
    • Information source (Billing Provider)
    • Subscriber (can be the patient when the patient is the subscriber or is considered to be the subscriber)
    • Dependent (Patient, when the patient is not considered to be the subscriber)
  • BHT02 - The transaction purpose code indicates "original" by using data value 00 or "reissue" by using data value 18.
  • BHT03 - originator's reference number; generated by the business application system of the entity building the original transaction.
  • BHT04 - date of transaction creation; generated by the business application system of the entity building the original transaction.
  • BHT05 - time of transaction creation; generated by the business application system of the entity building the original transaction.
  • BHT06 - designates transaction as Subrogation, fee-for-service, or capitated services.

1.4.4.2.2 Table 2 - Detail Information

Table 2 uses the hierarchical level structure. Each hierarchical level is comprised of a series of loops. Numbers identify the loops. The hierarchical level in Loop ID-2000 identifies the participants and the relationship to other participants. The individual or entity information is contained in Loop ID-2010.

1.4.4.2.2.1 Hierarchical Level (HL) Segments

The following describes the HL structure within the claim transaction.

The Billing Provider or Subscriber HLs may contain multiple "child" HLs. A child HL indicates an HL that is nested within (subordinate to) the previous HL. Hierarchical levels may also have a parent HL. A parent HL is the HL that is one level out in the nesting structure. An example follows.

Billing provider HL Parent HL to the Subscriber HL
Subscriber HL Parent HL to the Patient HL; Child HL to the Billing Provider HL
Patient HL Child HL to the Subscriber HL

For the Subscriber HL, the Billing Provider HL is the parent. The Patient HL is the child. The Subscriber HL is contained within the Billing Provider HL. The Patient HL is contained within the Subscriber HL.

1.4.4.2.2.2 Subscriber / Patient Hierarchical Level (HL) Segments

The following information illustrates claim submissions when the patient is the subscriber and when the patient is not the subscriber.

NOTES
Specific claim detail information can be given in either the subscriber or the dependent hierarchical level. Because of this, the claim information is said to "float." Claim information is positioned in the same hierarchical level that describes its owner-participant, either the subscriber or the patient. In other words, the claim information is placed at the subscriber hierarchical level when the patient is the subscriber or considered to be the subscriber, or it is placed at the patient/dependent hierarchical level when the patient is the dependent of the subscriber and cannot be uniquely identified on their own.

Claim submission when the patient is the subscriber or is considered to be the subscriber:

Billing provider (HL03=20)

Subscriber (HL03=22)

Claim level information

Line level information, as needed

Claim/encounter submission when the patient is not the subscriber:

Billing provider (HL03=20)

Subscriber (HL03=22)

Patient (HL03=23)

Claim level information

Line level information, as needed

1.4.4.2.2.3 Hierarchical Level (HL) Structural Example

If the billing provider is submitting claims for more than one subscriber, each of whom may or may not have dependents, the HL structure between the transaction set header and trailer (ST-SE) could look like the following:

BILLING PROVIDER

SUBSCRIBER #1 (Patient #1)

Claim level information

Line level information, as needed

SUBSCRIBER #2

PATIENT #P2.1 (for example, subscriber #2 spouse)

Claim level information

Line level information, as needed

PATIENT #P2.2 (for example, subscriber #2 first child)

Claim level information

Line level information, as needed

PATIENT #P2.3 (for example, subscriber #2 second child)

Claim level information

Line level information, as needed

SUBSCRIBER #3 (Patient #3)

Claim level information

Line level information, as needed

SUBSCRIBER #4 (Patient #4)

Claim level information

Line level information, as needed

SUBSCRIBER #4 (repeated)

PATIENT #P4.1 (for example, #4 subscriber's first child)

Claim level information

Line level information, as needed

Based on the previous example, the HL structure will be as follows:

HL*1**20*1~ (BILLING PROVIDER)

1   = HL sequence number

**(blank)

    = there is no parent HL (characteristic of the billing provider HL)

20  = information source

1   = there is at least one child HL to this HL

HL*2*1*22*0~ (SUBSCRIBER #1)

2   = HL sequence number

1   = parent HL

22  = subscriber

0   = no subordinate HLs to this HL (there is no child HL to this HL - claim level data follows)

HL*3*1*22*1~ (SUBSCRIBER #2)

3   = HL sequence number

1   = parent HL

22  = subscriber

1   = there is at least one child HL to this HL

HL*4*3*23*0~ (PATIENT #P2.1)

4   = HL sequence number

3   = parent HL

23  = dependent

0   = no subordinate HLs in this HL (there is no child HL to this HL - data follows)

HL*5*3*23*0~ (PATIENT #P2.2)

5   = HL sequence number

3   = parent HL

23  = dependent

0   = no subordinate HLs in this HL (there is no child HL to this HL - claim level data follows)

HL*6*3*23*0~ (PATIENT #P2.3)

6   = HL sequence number

3   = parent HL

23  = dependent

0   = no subordinate HLs in this HL (there is no child HL to this HL - claim level data follows)

HL*7*1*22*0~ (SUBSCRIBER AND PATIENT #3)

7   = HL sequence number

1   = parent HL

22  = subscriber

0   = no subordinate HLs in this HL (there is no child HL to this HL - claim level data follows)

HL*8*1*22*0~ (SUBSCRIBER AND PATIENT #4)

8   = HL sequence number

1   = parent HL

22  = subscriber

0   = no subordinate HLs

HL*9*1*22*1~ (SUBSCRIBER #4)

9   = HL sequence number

1   = parent HL

22  = subscriber

1   = there is at least one child HL to this HL

HL*10*9*23*0~ (PATIENT #P4.1)

10  = HL sequence number

9   = parent HL

23  = dependent

0   = no subordinate HLs

If another billing provider is listed in the same ST-SE functional group, it could be listed as follows: HL*100**20*1~. The HL sequence number of 100 indicates that there are 99 previous HL segments and it is the billing provider level HL (HL03 = 20).

1.4.4.2.2.4 Hierarchical Level (HL) Structural Summary

The following information summarizes coding and structure of the HL segment:

  • HL segments are numbered sequentially within a transaction (ST to SE), beginning with 1. The sequential number is found in HL01, which is the first data element in the HL segment. Sequence number must be numeric.
  • The second element, HL02, indicates the sequential number of the parent hierarchical level. The billing provider/information source is the highest hierarchical level and therefore has no parent.
  • The data value in data element HL03 describes the hierarchical level entity. For example, when HL03 equals 20, the hierarchical level is the billing provider; when HL03 equals 23, the hierarchical level is the dependent (patient).
  • Data element HL04 indicates whether or not subordinate hierarchical levels exist. A value of "1" indicates subordinate hierarchical levels. A value of "0" indicates no subordinate hierarchical levels exist for this HL.

1.4.4.2.2.5 Claim Structure

After the HL structure is defined and the Subscriber and/or Patient information is listed, the specific claim information follows:

  • Loop ID-2300 contains claim level information.
  • Loop ID-2310 identifies various claim specific providers who may have been involved in the health care services being reported in the transaction.
  • Loop ID-2320 identifies claim level adjudication information associated with non-destination, other payer information for the purpose of coordination of benefits.
  • Loop ID-2330 identifies the subscriber, payer, and provider identifiers associated with the non-destination, other payer.
  • Loop ID-2400 is required for all claims and identifies service line information.
  • Loop ID-2420 identifies any service line providers who are different than claim level providers.
  • Loop ID-2430 identifies any service line adjudication information from another payer.

1.4.4.2.2.6 Provider Taxonomy Code Reporting

The Health Care Provider Taxonomy code set describes the provider grouping, classification and area of specialization, and is maintained by the National Uniform Claim Committee (NUCC).

For use in an 837 claim, the provider determines the code value from the code set (external Code Source 682) that most accurately describes the discrete specialization under which the provider performed the services reported on the claim. The payer may request providers submit a specialty under which they are credentialed but may not otherwise dictate the code value to be reported.

1.4.5 Balancing

In order to ensure internal claim integrity, amounts reported in the 837 MUST balance at two different levels – the claim and the service line.

1.4.5.1 Claim Level

There are two different ways the claim information must balance. They are as follows.

1) Claim Charge Amounts
The total claim charge amount reported in Loop ID-2300 CLM02 must balance to the sum of all service line charge amounts reported in Loop ID-2400 SV302.

2) Claim Payment Amounts
Note: This type of balancing does not apply to predetermination requests.

Balancing of claim payment information is done payer by payer. For a given payer, the sum of all line level payment amounts (Loop ID-2430 SVD02) less any claim level adjustment amounts (Loop ID-2320 RAS adjustments) must balance to the claim level payment amount (Loop ID-2320 AMT02).

When a previous payer's adjudication data is only at the claim level, the claim level Payer Paid Amount (Loop ID-2320 AMT02) must equal the Total Claim Charge Amount (Loop ID-2300 CLM02) less any claim level adjustment amounts for that payer (Loop ID-2320 RAS adjustments).

Line Level Payment Amounts
Line level payment information is reported in Loop ID-2430 SVD02. In order to perform the balancing function, the receiver must know which payer the line payment belongs to. This is accomplished using the identifier reported in Loop ID-2430 SVD01. The value reported in this field must match the corresponding Other Payer Responsibility Sequence Code reported in Loop ID-2320 SBR01.

Adjustment Calculations
Adjustments are reported in element RAS01 in the RAS segments of Loop ID-2320 (claim level) and Loop ID-2430 (line level). Adjustment amounts in RAS01 DECREASE the payment amount when the adjustment amount is POSITIVE, and INCREASE the payment amount when the adjustment amount is NEGATIVE.

Claim Level Payment Amount
At the claim level, the payer's total claim payment is reported within the Loop ID-2320 Coordination of Benefits (COB) Payer Paid Amount AMT segment with a D qualifier in AMT01. The associated payer is defined within the Loop ID-2330B child loop.

Example:
Claim Charge = 100.00
Claim Payment = 80.00
Claim Adjustment = 5.00

Line 1 Charge = 80.00
Line 1 Payment = 70.00
Line 1 Adjustment = 10.00

Line 2 Charge = 20.00
Line 2 Payment = 15.00
Line 2 Adjustment = 5.00

Claim payment ($80) = Line 1 payment ($70) plus Line 2 payment ($15) minus claim adjustment ($5).

1.4.5.2 Service Line

Note: This section does not apply to predetermination requests.

Line Adjudication Information (Loop ID-2430) is reported when the payer identified in Loop ID-2330B has adjudicated the claim and service line payments and/or adjustments have been applied.

Service line balancing occurs independently by Payer for each service line. In order to balance, the sum of all service line adjustments and all service line payments for each Payer must balance to the Line Item Charge Amount for that service line. Note that, for a single service line, multiple 2430 loops may be required when the Payer has unbundled the service.

The calculation for each payer is as follows:

{Sum of all Loop-ID 2430 RAS01 Adjustment Amounts for that Payer}
plus
{Sum of all Loop-ID 2430 SVD02 Service Line Paid Amounts for that Payer}
=
{Loop ID-2400 SV102 Line Item Charge Amount}

Example:
Line 1 Charge = 80.00
Line 1 Payment = 70.00
Line 1 Adjustment = 10.00

Line 2 Charge = 20.00
Line 2 Payment = 15.00
Line 2 Adjustment = 5.00

Line 1 adjustment ($10) plus Line 1 payment ($70) = Line 1 charge ($80)

Line 2 adjustment ($5) plus Line 2 payment ($15) = Line 2 charge ($20)

1.4.6 Obtaining Approval for use of K3 Segment

The K3 Segment was added to X12N transactions to support a temporary solution for unexpected data requirements of a regulatory/legislative authority. It cannot be used for any other purpose.

1.4.6.1 Requester Submission

Before a proposal can be considered by X12N, a change request must be submitted with the relevant business documentation to the X12 change request website at https://x12.org/resources/forms/maintenance-requests.

1.4.6.2 X12N Review/Approval

X12N will review the request to determine the business need. If X12N determines that there is business need and there is no method to meet the requirement, the requester will receive approval to use the K3 Segment on a temporary basis until a permanent location can be defined within a future transaction implementation.

1.4.6.3 Formatting of K3 Content

The format in which the requirements will be met within the K3 Segment itself must be coordinated between the requester and X12N to ensure a consistent implementation of the requirements for all trading partners. X12N will work with the requester to define those format requirements and will post an RFI (Request for Interpretation) to the X12 Interpretation Portal at https://x12.org/resources/forms/request-interpretation on behalf of the requester.

1.5 Business Terminology

To ensure consistent use of terms, definitions, and acronyms across X12 products, X12 maintains the Wordbook, a comprehensive corporate glossary. The included terms are either proprietary to X12, cite definitions published by another authority, or represent common terms and definitions that are relevant to X12's work. The terms and definitions defined in the Wordbook are used in X12 work products when applicable, without modification or revision. The Wordbook can be referenced online at wordbook.x12.org.

1.6 Transaction Acknowledgments

The purpose of transaction acknowledgments is to report to the sender whether the transaction being acknowledged was accepted or rejected.

The X12 Technical Report Type 2, Acknowledgment Reference Model provides guidance on several control structures and transaction set standards intended to augment EDI auditing and control systems.

1.7 Related Transactions

There are one or more transactions related to the transactions described in this implementation guide.

1.7.1 Health Care Claim Payment/Advice (835)

Information in the Health Care Claim Payment/Advice (835) transaction is generated by the payer's adjudication system. However, in a coordination of benefits (COB) situation where the provider is sending an 837 claim to a secondary payer for payment, information from the 835 may be included in the secondary 837. Data from specific segments/elements in the 835 are crosswalked directly into the subsequent 837.

The payer's response to a predetermination request (837) will also be returned in a Health Care Claim Payment/Advice (835) transaction when the predetermination request was processed successfully. Refer to the Health Care Claim Payment / Remittance Advice TR3 for information on coding specific to a response to a predetermination request. If the services described in the predetermination request are subsequently rendered and then submitted in an 837 claim for payment, another 835 will be returned to advise of the finalized adjudication results and payment.

The 835 response to a real-time claim for payment or a real-time predetermination request may be returned in either batch or real-time mode.

1.8 Trading Partner Agreements

Trading partner agreements are used to establish and document the relationship between trading partners. A trading partner agreement must not override the specifications in this implementation guide if a transmission is reported in GS08 to be a product of this implementation guide.

1.9 Transaction Compliance

There are three types of compliance that may be relevant to a transmitted transaction.

Compliance with implementation guide requirements

Compliance with state and federal regulation

Compliance with trading partner contractual agreements

1.9.1 Transaction Compliance with Implementation Guide Requirements

A transaction complies with X12 implementation guide requirements if the transaction satisfies all format and content rules and constraints specified in the applicable X12 standards and the implementation guide (also known as a TR3) itself.

Should additional clarification of an X12 implementation guide requirement be desired, two options are available.

X12 does not specify the business rules that the receiving entity must use to decide when to accept or reject a transaction. The receiver will handle transactions that are not TR3-compliant based on its own business process.

A receiver may specify its business rules in a trading partner agreement or companion document. As stated in §1.8, these documents do not override TR3 requirements, nor change how transaction compliance with this TR3 is determined.

1.9.2 Transaction Compliance with State and Federal Regulations

This implementation guide has been developed for use as an insurance industry implementation guide. At the time of publication it has not been adopted as a state or federal standard. Should this implementation guide be adopted as a standard, the adopting authority will establish compliance dates for its use by impacted entities.

X12 is not the authority for determining compliance with regulatory requirements that might further constrain implementation guide requirements. Questions of compliance for regulatory requirements should be directed to the governing authority.

X12 does not specify the business rules that the receiving entity must use to decide when to accept or reject a transaction. The receiver will handle transactions that do not comply with applicable regulatory requirements as specified by the applicable regulation(s) or governing authority.

1.9.3 Transaction Compliance with Contractual Requirements

X12 is not the authority for determining compliance with contractual requirements that might further constrain implementation guide requirements. Questions of compliance for contractual requirements should be directed to the contracting entity.

X12 does not specify the business rules that the receiving entity must use to decide when to accept or reject a transaction. The receiver will handle transactions that do not comply with contractual requirements as specified by the applicable contract or contracting entity.

1.10 National Provider Identifier Usage within the HIPAA 837 Transaction

Implementation and use of the National Provider Identifier (NPI) has a direct impact on the generation of 837 transaction sets. Previous versions contained placeholder codes and elements in anticipation of the official Rule. With publication of the final rule and industry input on implementation direction, the authors have identified the following areas for clarification and direction for use within the implementation guide.

  • Providers who are not eligible for enumeration
  • Organization health care provider subpart representation
  • Subparts and the billing provider

1.10.1 Providers who are Not Eligible for Enumeration

Atypical providers are service providers that do not meet the definition of health care provider. Examples include taxi drivers, carpenters, personal care providers, etc. Although they are not eligible to receive an NPI, these providers perform services that are reimbursed by some health plans. This implementation guide accommodates both the NPI (to identify health care providers) and proprietary identifiers (to identify atypical/non-health care providers).

1.10.2 Organization Health Care Provider Subpart Representation

Historically, there has been no standard representation of organization health care providers. How the health care provider entity has been identified has varied by trading partner. The NPI subpart concept provides an organization health care provider the ability to represent itself in a manner consistent to all trading partners. In the health care claim, there are two possible locations for organization health care provider entities to be reported. They are Billing Provider and Service Location.

Billing Provider. In many instances the Billing Provider is an organization; therefore, the Billing Provider NPI reported would belong to an organization health care provider. The Billing Provider may be an individual only when the services were performed by, and will be paid to, an independent, non-incorporated individual. When an organization health care provider has determined that it has subparts requiring enumeration, that organization health care provider will report the NPI of the subpart as the Billing Provider. The subpart reported as the Billing Provider MUST always represent the most detailed level of enumeration as determined by the organization health care provider and MUST be the same identifier sent to any trading partner.

NOTE
The Billing Provider must be a health care or atypical service provider (as described in the Section 1.10.1 Providers who are Not Eligible for Enumeration).

Service Location. An organization health care provider's NPI used to identify the Service Location must be external to the entity identified as the Billing Provider (for example; reference lab). It is not permissible to report an organization health care provider's NPI as the Service Location if the Service Location is a subpart of the Billing Provider.

1.10.3 Subparts and the 2010AA - Billing Provider Name Loop

When the Billing Provider is an organization health care provider, the NPI of the organization health care provider or its subpart is reported in NM109. When an organization health care provider has determined a need to enumerate subparts, it is required that a subpart's NPI be reported as the Billing Provider. The subpart reported as the Billing Provider MUST always represent the most detailed level of enumeration and MUST be the same identifier sent to any trading partner. For additional explanation, see Section 1.10.2 - Organization Health Care Provider Subpart Representation.

The Billing Provider may be an individual only when the health care provider performing services is an independent, unincorporated entity. In these cases, the Billing Provider is the individual whose Tax Identification Number (TIN) is used for IRS Form 1099 purposes. That individual's NPI is reported in NM109, and the individual's TIN must be reported in the REF segment of Loop ID-2010AA. The individual's NPI must be reported when the individual provider is eligible for an NPI.

The TIN of the Billing Provider, used for IRS Form 1099 purposes, must be reported in the REF segment of Loop ID-2010AA Billing Provider.

When the Billing Provider is an atypical provider, the Billing Provider should be the legal entity. However, willing trading partners may agree upon varying definitions. Proprietary or legacy identifiers necessary for the trading partner to identify the entity are to be reported in the REF segment of Loop ID-2010BB Payer Name. The TIN, used for IRS Form 1099 purposes, must be reported in the REF segment of Loop ID-2010AA Billing Provider.

1.11 Coding of Drugs in the 837 Claim

The Dental claim does not support coding of drug claims. If it is necessary to code drug claims, use the professional or institutional claim as appropriate.

1.12.1 Individuals with one Legal Name

In those situations where an individual has only one legal name, report that name in the last name data element of the NM1 segment, specifically the NM103. The first and middle name data elements for that NM1 segment are then not used. This guideline is true for all loops containing an NM1 segment that may identify an individual.

1.12.2 Situational Data specific to Payer's Adjudication

This implementation guide contains a number of Situational Rules which state the element or segment is required when a payer's adjudication is known to be impacted by that information. These rules must not be construed as allowing the current payer to reject a claim or transaction if the information is submitted but not used by that payer. The condition in these situational rules is based on a known impact to any potential payer's adjudication.

The purpose is to enable proper adjudication for any potential downstream payers as well as allow affected providers to collect and report information consistently for all trading partners when desired. As a result, the submitter is not restricted from sending the information to other payers in addition to the specific payer that has a known adjudication impact. In a payer-to-payer COB model, each payer should pass all data received in case it is needed by a subsequent payer.

1.12.3 Multiple REF Segments with the same Qualifier

A repeat of a REF segment within the same loop is not allowed when the qualifier in the REF01 data element is the same. However, there is one important exception to this rule. Within the 837, there are data elements reported in Loop ID-2400 and the various 2420 loops which are payer specific (for example: Referral Number, Prior Authorization Number, Provider Identifiers...). When these pieces of information are reported, the composite data element in REF04 is used to identify the associated payer. In all cases, the reported data belongs to the destination payer when REF04 is not used. When REF04 is used, the value reported in the first component (REF04-01) equals 2U. This qualifier indicates the value reported in the following component (REF04-02) is a payer identifier. This payer identifier "links" to one of the payer identifiers found in Loop ID-2330B NM109.

1.12.4 Provider Tax IDs

For purposes of this implementation, the Billing Provider is the provider or provider organization to which payment is intended to be made. This payment is included in the provider's 1099 reporting. The Employer Identification Number (EIN) or Social Security Number (SSN) for the billing provider is only reported in the Billing Provider Tax Identification REF segment in Loop ID-2010AA Billing Provider. The EIN and SSN qualifiers are not valid in any provider REF segments other than the 2010AA Billing Provider loop. Other reference qualifiers must be used in the REF segments in those loops to provide identifying information, such as "A6" for Provider's Identifier.

1.12.5 Inpatient and Outpatient Designation

Not applicable for this guide.

1.12.6 Date of Service for Predetermination Requests

Since the date of service associated with a predetermination request is assumed to be the date the transaction is created, validation of all medical code sets (such as procedure codes and diagnosis codes) is based upon the creation date reported in the DTP Segment (Original Claim Creation Date). The determination of reimbursement rates, patient responsibility, or any other situation where the service date would have significance, are to be based upon the date of payer adjudication.

2. Transaction Set

NOTE
See X12 documents X12.5, X12.6, and X12.59 to review transaction set structure, including descriptions of segments, levels, and loops.

2.1 Presentation Examples

The X12 standards are generic. For example, multiple trading communities use the same PER segment to specify administrative communication contacts. Each community decides which elements to use and which code values in those elements are applicable.

This implementation guide uses a format that depicts both the generalized standard and the insurance industry-specific implementation. In this implementation guide, IMPLEMENTATION specifies the requirements for this implementation. X12 STANDARD is included as a reference only.

The transaction set presentation is comprised of two main sections with subsections within the main sections:

Transaction Set Listing

There are two sub-sections under this general title. The first sub-section concerns this implementation of a generic X12 transaction set. The second sub-section concerns the generic X12 standard itself.

This section lists the levels, loops, and segments contained in this implementation. It also serves as an index to the segment detail.

This section is included as a reference.

Segment Detail

There are three sub-sections under this general title. This section repeats once for each segment used in this implementation providing segment specific detail and X12 standard detail.

This section is included as a reference.

This section is included as a reference. It provides a pictorial view of the standard and shows which elements are used in this implementation.

This section specifies the implementation details of each data element.

These illustrations (Figures 2.1 through 2.5) are examples and are not extracted from the Section 2 detail in this implementation guide. Annotated illustrations, presented below in the same order they appear in this implementation guide, describe the format of the transaction set that follows.

Figure 2.1 - Transaction Set Key - Implementation

Transaction Set Key - Implementation

Figure 2.2 - Transaction Set Key - Standard

Transaction Set Key - Standard

Figure 2.3 - Segment Key - Implementation

Segment Key - Implementation

Figure 2.4 - Segment Key - Diagram

Segment Key - Diagram

Figure 2.5 - Segment Key - Element Summary

Segment Key - Element Summary

2.2.1 Industry Usage

Industry Usage describes when loops, segments, and elements are to be sent when complying with this implementation guide. The three choices for Usage are required, not used, and situational. To avoid confusion, these are named differently than the X12 standard Condition Designators (mandatory, optional, and relational).

Required  

This loop/segment/element must always be sent.

Required segments in Situational loops only occur when the loop is used.

Required elements in Situational segments only occur when the segment is used.

Required component elements in Situational composite elements only occur when the composite element is used.

Not Used  

This element must never be sent.

Situational  

Use of this loop/segment/element varies, depending on data content and business context as described in the defining rule. The defining rule is documented in a Situational Rule attached to the item.

There are two forms of Situational Rules.

"Required when <explicit condition statement>. If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver."

The data qualified by such a situational rule cannot be required, requested or rejected by the receiver when the condition is not applicable. Transmission of this data is solely at the sender's discretion when the stated condition does not apply.

"Required when <explicit condition statement>. If not required by this implementation guide, do not send."

The data qualified by such a situational rule must not be sent except as described in the explicit condition statement.

2.2.1.1 Determining Transaction Compliance with Industry Usage Requirements

A transmitted transaction complies with the governing implementation guide when it satisfies the requirements as defined within the implementation guide. Specifically, the presence or absence of an item (loop, segment, or element) complies with the industry usage specified by this implementation guide according to the following table.

Industry Usage

Business
Condition
is

Item
is

Transaction
Complies with
Implementation
Guide?

Required

N/A

Sent

Yes

Not Sent

No

Not Used

N/A

Sent

No

Not Sent

Yes

Situational (Required when <explicit condition statement>. If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver.)

True

Sent

Yes

Not Sent

No

Not True

Sent

Yes

Not Sent

Yes

Situational (Required when <explicit condition statement>. If not required by this implementation guide, do not send.)

True

Sent

Yes

Not Sent

No

Not True

Sent

No

Not Sent

Yes

2.2.2 Loops

Loop requirements depend on the context or location of the loop within the transaction. See Appendix B for more information on loops.

  • A nested loop can be used only when the associated higher level loop is used.
  • The usage of a loop is the same as the usage of its beginning segment.
    • If a loop's beginning segment is Required, the loop is Required and must occur at least once unless it is nested in a loop that is not being used.
    • If a loop's beginning segment is Situational, the loop is Situational.
  • Subsequent segments within a loop can be sent only when the beginning segment is used.
  • Required segments in Situational loops occur only when the loop is used.

3. Examples

Business scenario examples for use of this transaction can be found on the X12 Examples website at http://examples.x12.org. The X12 Examples website provides convenient access to examples of X12 transaction transmissions, including the data stream and a description of the associated scenario.

 

Appendix A. External Code Sources

Prior to this publication, X12 TR3s contained a subset of the overall Code Source Directory, formerly known as Appendix A of X12.3. External code lists are not part of the X12 standard and are provided for information purposes only. The full listing is available in Glass, X12's On-Line viewer.

Read more about Glass here: https://glasshelp.x12.org/.

Where an external code source is referenced in this publication, the implementer is required to use only the codes from that list. Codes must be reported as listed in the code source (e.g. with leading zeroes). Implementers must follow the instructions for code use that are supplied by the code set owner.

 

B.1.1 Referenced and Related Standards

This technical report is based on the X12 EDI standard which comprises a series of interdependent publications. Implementers are advised to consult these publications when using this technical report.

The following standards are required to interpret, understand, and use this technical report:

  • X12.5 - Interchange Control Structure
  • X12.6 - Application Control Structure

The following guideline is useful to interpret, understand, and use this technical report:

  • Compliance in X12

The following reference model is useful to interpret, understand, and use this technical report:

  • Acknowledgment Reference Model

All of the documents above are available online using links to X12's Online Viewer.

 

B.1.1.1 Transmission Control Schematic

Refer to X12.5 - Interchange Control Structures, Section 3.5 - Order of Control Segments, and Chapter 5 Interchange Segment Specifications.

Similar transaction sets, called "functional groups," can be sent together within a transmission. Each functional group is prefaced by a group start segment; and a functional group is terminated by a group end segment. One or more functional groups are prefaced by an interchange header and followed by an interchange trailer. Figure B.1 - Transmission Control Schematic, illustrates this interchange control.

Figure B.1 - Transmission Control Schematic

Transmission Control Schematic

 

B.1.1.2 Constraints applicable to the suite of TR3s

Refer to X12.6 - Application Control Structure, Section 3.2.8 - Minimums/Maximums.

Data element minimum and maximum lengths are set by the X12 standard. This implementation guide may further restrict minimum and maximum lengths within the bounds set by the standard. Such restrictions may occur implicitly by virtue of the allowed qualifier for the data element, or they may be stated explicitly in a note attached to the element or in the general limitations below.

 

B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification

The current X12 standard allows a maximum length greater than 50 characters for data element 127. For implementations governed by this implementation guide, unless another value is specified in an attached note, the maximum length of each occurrence of this data element is constrained to 50 characters.

 

B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount

For implementations governed by this implementation guide, unless another value is specified for an instance of Data Element 782 within Section 2 (Transaction Set), each occurrence of Data Element 782 (Monetary Amount) will be limited to a maximum length of 10 characters including reported or implied places for cents (implied value of 00 after the decimal point). Note that the decimal point and leading sign, if sent, are not part of the character count.

EXAMPLE

  • The following transmitted value represents the largest positive dollar amount that can be sent: 99999999.99
  • The following transmitted value is the longest string of characters that can be sent representing whole dollars. 99999999
  • The following transmitted value is the longest string of characters that can be sent representing negative dollars and cents. -99999999.99
  • The following transmitted value is the longest string of characters that can be sent representing negative whole dollars. -99999999
 

B.1.1.3 Decimal

While the X12 standard supports usage of exponential notation, this guide prohibits that usage.

Appendix D. Change Summary

This Implementation Guide (008020X325) defines the X12 requirements for the Health Care Claim: Dental. It is based on version/release/subrelease 008020 of the X12 standards.