837 Transaction Set Listing

008020X300 Post-adjudicated Claims Data Reporting: 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✱008020X300~
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
008020X300
Post-adjudicated Claims Data Reporting: 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✱987654✱008010X300~
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 Number in ST02 and SE02 must be identical. The number must be unique within a specific interchange (ISA-IEA), but can repeat in other interchanges.
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
008020X300
Post-adjudicated Claims Data Reporting: 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 Example:
BHT✱0019✱00✱44445✱20120213✱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
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
Original transmissions are transmissions which have never been sent to the receiver.
18
Reissue
If a transmission was disrupted and the receiver requests a retransmission, the sender uses "Reissue" 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
RP
Reporting

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
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
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)
Established by trading partner agreement
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 combinations of 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
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.
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.
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 HIERARCHICAL 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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
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. 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 social security number is used for 1099 purposes. That individual's NPI is reported in NM109, and the individual's Tax Identification Number must be reported in the REF segment of this loop. The individual's NPI must be reported when the individual provider is eligible for an NPI.
  2. When the individual or the organization is not a health care provider and, thus, not eligible to receive an NPI (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.
  3. The information provided in this segment is intended to be representative of the information as known to the payer's system.
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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.If not required by this implementation guide, do not send.
If, for whatever reason, the data is not stored within the payer's system, do not use.
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 available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Billing Provider Identifier
If, for whatever reason, the data is not stored within the payer's system, do not use.
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:
The Billing Provider Address is to be the provider's address as known to the payer's enrollment files. When the provider address is not on file, report the address as received.
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 available in the payer's system.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 Notes:
The Billing Provider Address is to be the provider's address as known to the payer's enrollment files. When the provider address is not on file, report the address as received.
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: 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.
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.
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 entity paid for the submitted services.
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
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
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

REF*0B - BILLING PROVIDER LICENSE INFORMATION

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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
REF✱0B✱654321~
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
0B
State License 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 License Information
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:
1
Situational Rule:
Required when available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
REF✱G2✱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
G2
Provider Commercial Number
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 - SUBSCRIBER HIERARCHICAL 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:
When submitting Medicare and/or Medicaid encounters, the patient is always the subscriber and the Patient HL in Loop 2000C is not used.
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.
  1. The claim (Loop ID-2300) can be used when HL04 has no subordinate levels (HL04 = 0) or when HL04 has subordinate levels indicated (HL04 = 1).
  2. In the first case (HL04 = 0), the subscriber is the patient and there are no dependent claims.
  3. The second case (HL04 = 1) happens when claims for one or more dependents of the subscriber are being sent under the same billing provider HL (for example, a spouse and son are both treated by the same provider). In that case, the subscriber HL04 = 1 because there is at least one dependent to this subscriber. The dependent HL (spouse) would then be sent followed by the Loop ID-2300 for the spouse. The next HL would be the dependent HL for the son followed by the Loop ID-2300 for the son.
  4. In order to send claims for the subscriber and one or more dependents, the Subscriber HL, with Relationship Code SBR02=18 (Self), would be followed by the Subscriber's Loop ID-2300 for the Subscriber's claims. Then the Subscriber HL would be repeated, followed by one or more Patient HL loops for the dependents, with the proper Relationship Code in PAT01, each followed by their respective Loop ID-2300 for each dependent's claims.
CODE
DEFINITION
0
No Subordinate HL Segment in This Hierarchical Structure.
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.

SBR*N - 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✱N✱18~
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
CODE
DEFINITION
N
Unconfirmed
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. If not required by this implementation guide, do not send.
CODE
DEFINITION
18
Self
Not Used
3
127
Reference Identification
O 1
AN
1/80
Not Used
4
93
Name
O 1
AN
1/60
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
Not Used
9
1032
Claim Filing Indicator Code
O 1
ID
1/2
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:
  1. In worker's compensation or other property and casualty claims, the "subscriber" may be a non-person entity (for example, the employer). However, this varies by state.
  2. When submitting to an All Payer Claims Database or Health Benefit Exchange, this is the Subscriber as defined within the payers enrollment files. When submitting Medicare or Medicaid encounters, the patient is always the subscriber.
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
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when available in the payer's system.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 available in the payer's system.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 available in the payer's system.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 an identifier has been assigned by the receiver. If not required by this implementation guide, do not send.
CODE
DEFINITION
II
Standard Unique Health Identifier for each Individual in the United States
Required if the HIPAA Individual Patient Identifier is mandated use. If not required, use value `MI' instead.
MI
Member Identification Number
Situational
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when an identifier has been assigned by the receiver. 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:
Required
Segment Repeat:
1
TR3 Notes:
The information provided in this segment is intended to be representative of the information as known to the payer's system.
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 available in the payer's system.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:
Required
Segment Repeat:
1
TR3 Notes:
The information provided in this segment is intended to be representative of the information as known to the payer's system.
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 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.
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.
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:
Required
Segment Repeat:
1
TR3 Notes:
The information provided in this segment is intended to be representative of the information as known to the payer's system.
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
A
Not Provided
Use when the gender cannot be sent due to reporting restrictions.
F
Female
I
Nonbinary
M
Male
T
Self-reported as Transgender
U
Unknown
Use when the gender is unknown.
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:

The entity identified as the data receiver in Loop ID 2010BB is an All Payer Claims Database or Health Insurance Exchange.
AND
The social security number is allowed to be used for this purpose under applicable law or regulation.
AND
The social security number is available in the payer's system.

If not required by this implementation guide, do not send.
TR3 Notes:
Trading partners using this segment are encouraged to explicitly address necessary safeguards in the trading partner agreement.
TR3 Example:
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
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 Supplemental 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*Y4 - PROPERTY AND 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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
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 - SUBSCRIBER 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:
5
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement
AND
The data is available in the payer's system.
If not required by this implementation guide, then do not send.
TR3 Example:
REF✱1W✱ABC123456~
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
1H
CHAMPUS Identification Number
Use to report Tricare identifier
1W
Member Identification Number
ABB
Personal ID Number
F6
Health Insurance Claim (HIC) Number
NQ
Medicaid Recipient 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: Subscriber 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*ZD - DATA RECEIVER

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✱ZD✱2✱Medicaid Agency~
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
ZD
Party to Receive Reports
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: Data 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
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

HL - PATIENT HIERARCHICAL 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 the data receiver is a reporting entity, such as an APCD or Health Insurance Exchange, AND the patient is not the subscriber.
TR3 Notes:
  1. The information reported in this loop describes the patient as known by the payer's system.
  2. When submitting Medicare and/or Medicaid encounters, the patient is always the subscriber and the Patient HL in Loop 2000C is not used.
  3. There are no HLs subordinate to the Patient HL.
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.
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
The code DEPENDENT conveys that the information in this HL applies to the patient when the subscriber and the patient are not the same person.
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 Notes:
The information provided in this segment is intended to be representative of the information as known to the payer's system.
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 Notes:
The information provided in this segment is intended to be representative of the information as known to the payer's system.
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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient 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 the patient has been assigned an identifier that is different than the subscriber identifier reported in Loop ID 2010BA NM109.If not required by this implementation guide, do not send.
CODE
DEFINITION
II
Standard Unique Health Identifier for each Individual in the United States
Required if the HIPAA Individual Patient Identifier is mandated use. If not required, use value `MI' instead.
MI
Member Identification Number
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 patient has been assigned an identifier that is different than the subscriber identifier reported in Loop ID 2010BA NM109.If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient 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 - 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 Notes:
The information provided in this segment is intended to be representative of the information as known to the payer's system.
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 available in the payer's system.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 Notes:
The information provided in this segment is intended to be representative of the information as known to the payer's system.
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 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.
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.
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 Notes:
The information provided in this segment is intended to be representative of the information as known to the payer's system.
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
A
Not Provided
Use when the gender cannot be sent due to reporting restrictions.
F
Female
I
Nonbinary
M
Male
T
Self-reported as Transgender
U
Unknown
Use when the gender is unknown.
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 - PATIENT 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:

The entity identified as the data receiver in Loop ID 2010BB is an All Payer Claims Database or Health Insurance Exchange.
AND
The social security number is allowed to be used for this purpose under applicable law or regulation.
AND
The social security number is available in the payer's system.

If not required by this implementation guide, do not send.
TR3 Notes:
Trading partners using this segment are encouraged to explicitly address necessary safeguards in the trading partner agreement.
TR3 Example:
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
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: Patient 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 AND 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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
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 - PATIENT 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:
5
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement
AND
The data is available in the payer's system.
If not required by this implementation guide, then do not send.
TR3 Example:
REF✱1W✱ABC123456~
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
1H
CHAMPUS Identification Number
Use to report Tricare identifier
1W
Member Identification Number
ABB
Personal ID Number
F6
Health Insurance Claim (HIC) Number
NQ
Medicaid Recipient 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: Patient 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

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:
For purposes of this documentation, the claim detail information is presented only in the dependent 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, Loop ID-2000C and Loop ID-2010CA are not sent.
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: Patient Control Number
The maximum number of characters to be supported for this field is `20'. Characters beyond the maximum are not required to be stored nor returned by any 837-receiving system.
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. This amount represents the sum of the line charge amounts included in this portion of the claim.
  4. 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 over written 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
This is the Claim Frequency Code as received on the most recently submitted claim from the provider.
CODE SOURCE 235: Claim Frequency Type Code
Situational
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.
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
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 available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Assignment or Plan Participation Code
Within this element the context of the word assignment is related to the relationship between the provider and the payer.
CODE
DEFINITION
A
Assigned
C
Not Assigned
Situational
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.
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Benefits Assignment Certification Indicator
This element answers the question whether or not the insured has authorized the plan to remit payment directly to the provider.
CODE
DEFINITION
N
No
W
Not Applicable
Use code `W' when the patient refuses to assign benefits.
Y
Yes
Situational
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
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
CODE
DEFINITION
I
Informed Consent to Release Medical Information for Conditions or Diagnoses Regulated by Federal Statutes
Y
Yes, Provider has a Signed Statement Permitting Release of Medical 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 available in the payer's system.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
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 available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Related Causes Code
CODE
DEFINITION
AA
Auto Accident
EM
Employment
OA
Other Accident
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 available in the payer's system.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 available in the payer's system.If not required by this implementation guide, do not send.
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 available in the payer's system.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
Not Used
16
1360
Provider Agreement Code
O 1
ID
1
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
Not Used
19
1383
Claim Submission Reason Code
O 1
ID
2
Situational
20
1514
Delay Reason Code
O 1
ID
1/2
Code indicating the reason why a request was delayed
SITUATIONAL RULE: Required when available in the payer's system.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
Not Used
21
1774
Claim Authorization Exception Code
O 1
ID
1/2

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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
DTP✱439✱D8✱20120108~
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 - APPLIANCE 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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
  1. Dates in Loop ID-2300 apply 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.
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
DTP✱452✱D8✱20120108~
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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
  1. Dates in Loop ID-2300 apply 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.
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
DTP✱472✱D8✱20120108~
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

DN1 - ORTHODONTIC TOTAL MONTHS OF TREATMENT

X12 Name:
Orthodontic Information
X12 Purpose:
To supply orthodontic information
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
  1. When reporting this segment, at least one of DN101, DN102 or DN104 must be present.
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
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 available in the payer's system.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 available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Orthodontic Treatment Months Remaining Count
Not Used
3
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
4
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
SEMANTIC: DN104 is the appliance description.
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Orthodontic Treatment Indicator
The only allowed value for DN104 is "Y", which indicates that services reported on this claim are for orthodontic purposes and that both DN101 and DN102 were not submitted.

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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
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

CN1 - CONTRACT INFORMATION

X12 Name:
Contract Information
X12 Purpose:
To specify basic data about the contract or contract line item
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when this information is necessary to satisfy contract requirements.

If not required by this implementation guide, do not send.
TR3 Example:
CN1✱02✱550~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1166
Contract Type Code
M 1
ID
2
Code identifying a contract type
CODE
DEFINITION
02
Per Diem
03
Variable Per Diem
04
Flat
05
Capitated
06
Percent
09
Other
Situational
2
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: CN102 is the contract amount.
SITUATIONAL RULE: Required when this information is necessary to satisfy contract requirements.If not required by this implementation guide, do not send.
INDUSTRY NAME: Contract 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
332
Percent, Decimal Format
O 1
R
1/6
Percent given in decimal format (e.g., 0.0 through 100.0 represents 0% through 100%)
SEMANTIC: CN103 is the allowance or charge percent.
SITUATIONAL RULE: Required when this information is necessary to satisfy contract requirements.If not required by this implementation guide, do not send.
INDUSTRY NAME: Contract Percentage
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: CN104 is the contract code.
SITUATIONAL RULE: Required when this information is necessary to satisfy contract requirements.If not required by this implementation guide, do not send.
INDUSTRY NAME: Contract 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.
Situational
5
338
Terms Discount Percent
O 1
R
1/6
Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date
SITUATIONAL RULE: Required when this information is necessary to satisfy contract requirements.If not required by this implementation guide, do not send.
INDUSTRY NAME: Terms Discount Percentage
Situational
6
799
Version Identifier
O 1
AN
1/30
Revision level of a particular format, program, technique or algorithm
SEMANTIC: CN106 is an additional identifying number for the contract.
SITUATIONAL RULE: Required when this information is necessary to satisfy contract requirements.If not required by this implementation guide, do not send.
INDUSTRY NAME: Contract Version Identifier

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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
  1. Patient Amount Paid refers to the sum of all amounts paid on the claim by the patient or his or her representative(s).
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
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*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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
  1. Numbers at this position apply to the entire claim unless they are overridden in the REF segment in Loop ID-2400. A reference identification is considered to be overridden if the value in REF01 is the same in both the Loop ID-2300 REF segment and the Loop ID-2400 REF segment. In that case, the Loop ID-2400 REF applies only to that specific line.
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
  1. Numbers at this position apply to the entire claim unless they are overridden in the REF segment in Loop ID-2400. A reference identification is considered to be overridden if the value in REF01 is the same in both the Loop ID-2300 REF segment and the Loop ID-2400 REF segment. In that case, the Loop ID-2400 REF applies only to that specific line.
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
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*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 (Automated Clearinghouses, and others) who need to attach their own unique claim number. If not required by this implementation guide, do not send.
TR3 Notes:
The data conveyed in this segment is not related to the provider submission to the payer.

This segment is used only when the payer is submitting this transaction to the Data Receiver through an intermediary that assigns their own unique claim number.
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
  1. The value carried in this element is limited to a maximum of 20 positions.
  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

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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
  1. The K3 segment is expected to be used only when necessary to meet the unexpected data requirement of a legislative authority. Before this segment can be used:

    - The X12N Health Care Claim workgroup must conclude there is no other available option in the implementation guide to meet the emergency legislative requirement.

    - The requestor must submit a proposal for approval accompanied by the relevant business documentation to the X12N Health Care Claim workgroup chairs 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 X12N Health Care Claim workgroup 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.
  3. X12N will submit the necessary data maintenance and refer the request to the appropriate data content committee(s).
  4. If, for whatever reason, the data is not stored within the payer's system, do not use.
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
Not Used
2
1333
Record Format Code
O 1
ID
1/2
Not Used
3
C001
Composite Unit of Measure
O 1

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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
  1. Do not transmit the decimal point for ICD codes. The decimal point is implied.
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
HI✱BK:52403✱BF:52404~
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.
The diagnosis listed in this element is assumed to be the principal diagnosis.
Required
1-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
CODE
DEFINITION
ABK
International Classification of Diseases Clinical Modification (ICD-10-CM) Principal Diagnosis
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
TQ
Systemized Nomenclature of Dentistry (SNODENT)
This code set is not allowed for use under HIPAA at the time of this writing. The qualifier can only be used:

If a new rule names the SNODENT codes as an allowable code set under HIPAA,
OR
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: Principal 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 available in the payer's system.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)
This code set is not allowed for use under HIPAA at the time of this writing. The qualifier can only be used:

If a new rule names the SNODENT codes as an allowable code set under HIPAA,
OR
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 available in the payer's system.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-1 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)
This code set is not allowed for use under HIPAA at the time of this writing. The qualifier can only be used:

If a new rule names the SNODENT codes as an allowable code set under HIPAA,
OR
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 available in the payer's system.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-1 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)
This code set is not allowed for use under HIPAA at the time of this writing. The qualifier can only be used:

If a new rule names the SNODENT codes as an allowable code set under HIPAA,
OR
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

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 available in the payer's system.
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 in the first iteration of this loop to indicate the referral received by the rendering provider on this claim. Use code "P3 - Primary Care Provider" in the second iteration of the loop 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 billed/reported in this transaction.
  2. When reporting the provider who ordered services such as diagnostic and lab, use the 2310A loop at the claim level.
  3. If, for whatever reason, the data is not stored within the payer's system, do not use.
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
Use on the first iteration of this loop. Use if loop is used only once.
P3
Primary Care Provider
Use only if loop is used twice. Use only on second iteration of this loop.
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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Referring Provider Identifier
If, for whatever reason, the data is not stored within the payer's system, do not use.
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*RF - REFERRING 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:
Situational
Segment Repeat:
1
Situational Rule:
Required when available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
PRV✱RF✱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
RF
Referring
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 - 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:
2
Situational Rule:
Required when available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
  1. 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.
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
REF✱G2✱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
0B
State License Number
G2
Provider Commercial Number
This code designates a proprietary provider number for the submitting payer identified in the Payer Name loop, Loop ID-2330A where 2320 SBR06 equals 6. This is to be used by all payers including: Medicare, Medicaid, Blue Cross, etc.
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 information is different than that carried in Loop ID-2010AA - Billing Provider.

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. Information in 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. Used for all types of rendering providers including laboratories. The Rendering Provider is the person or company (laboratory or other facility) who rendered the care. In the case where a substitute provider (locum tenens) was used, enter that provider's information here.
  3. If, for whatever reason, the data is not stored within the payer's system, do not use.
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
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: Rendering Provider Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when available in the payer's system.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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Rendering Provider Identifier
If, for whatever reason, the data is not stored within the payer's system, do not use.
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:
Situational
Segment Repeat:
1
Situational Rule:
Required when available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
  1. 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.
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
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:
3
Situational Rule:
Required when available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
  1. 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.
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
REF✱G2✱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
0B
State License Number
G2
Provider Commercial Number
This code designates a proprietary provider number for the submitting payer identified in the Payer Name loop, Loop ID-2330A where 2320 SBR06 equals 6. This is to be used by all payers including: Medicare, Medicaid, Blue Cross, etc.
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: 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 FACILITY 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:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
  1. Information in 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. This is the Service Location as reported on the originally submitted claim from the provider. If the Service Location loop was not used on the original claim, use the address information reported in Loop 2010AA of the provider's claim.
TR3 Example:
NM1✱77✱2✱A-OK MOBILE CLINIC✱✱✱✱✱XX✱1112233301~
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
Required
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Laboratory or Facility 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 received on the provider's original claim submission; the Service Location information originates from the 2310 Service Location loop of the provider submitted claim; and the NPI is different than the NPI reported in NM109 of Loop ID 2010AA (Billing Provider).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 received on the provider's original claim submission; the Service Location information originates from the 2310 Service Location loop of the provider submitted claim; and the NPI is different than the NPI reported in NM109 of Loop ID 2010AA (Billing Provider).If not required by this implementation guide, do not send.
INDUSTRY NAME: Laboratory or Facility Primary Identifier
When an NPI is reported at this level, it must be different than the NPI reported in NM109 of Loop ID 2010AA (Billing Provider). When an NPI is present in this position, the service was performed in a location that is not a component of the Billing Provider.
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 FACILITY LOCATION 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:
This is the Service Location as reported on the originally submitted claim from the provider. If the Service Location loop was not used on the original claim, use the address information reported in Loop 2010AA of the provider's claim.
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: Laboratory or Facility Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Laboratory or Facility Address Line

N4 - SERVICE FACILITY 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:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
This is the Service Location as reported on the originally submitted claim from the provider. If the Service Location loop was not used on the original claim, use the address information reported in Loop 2010AA of the provider's claim.
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: Laboratory or Facility 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: Laboratory or Facility 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: Laboratory or Facility 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.
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.
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 FACILITY 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:
Required
Segment Usage:
Situational
Segment Repeat:
3
Situational Rule:
Required when available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
REF✱G2✱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
0B
State License Number
G2
Provider Commercial Number
This code designates a proprietary provider number for the submitting payer identified in the Payer Name loop, Loop ID-2330A where 2320 SBR06 equals 6. This is to be used by all payers including: Medicare, Medicaid, Blue Cross, etc.
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: Laboratory or Facility 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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
  1. Information in 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. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
NM1✱DD✱1✱SMITH✱JOHN✱S✱✱✱XX✱1234567899~
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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Assistant Surgeon Primary Identifier
If, for whatever reason, the data is not stored within the payer's system, do not use.
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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
  1. Information in 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. If, for whatever reason, the data is not stored within the payer's system, do not use.
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:
3
Situational Rule:
Required when available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
REF✱0B✱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
0B
State License Number
G2
Provider Commercial Number
This code designates a proprietary provider number for the submitting payer identified in the Payer Name loop, Loop ID-2330A where 2320 SBR06 equals 6. This is to be used by all payers including: Medicare, Medicaid, Blue Cross, etc.
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: 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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
  1. Information in 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. If, for whatever reason, the data is not stored within the payer's system, do not use.
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
Use this code for 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
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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Supervising Provider Identifier
If, for whatever reason, the data is not stored within the payer's system, do not use.
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 - 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:
4
Situational Rule:
Required when available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
REF✱G2✱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
0B
State License Number
G2
Provider Commercial Number
This code designates a proprietary provider number for the submitting payer identified in the Payer Name loop, Loop ID-2330A where 2320 SBR06 equals 6. This is to be used by all payers including: Medicare, Medicaid, Blue Cross, etc.
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: Supervising 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

SBR*R - 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:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
All information contained in Loop ID-2320A applies only to the submitting payer. It is specific only to that payer. If information for an additional payer is necessary, use Loop ID-2320B with its respective 2330 Loops.

Loop ID-2320A and its subordinate 2330 and 2430 loops convey information demonstrating how this claim was adjudicated by the submitting payer.
TR3 Example:
SBR✱P✱18✱G00786✱✱✱6✱✱✱CI✱512~
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
CODE
DEFINITION
R
Non-specified
When sending Line Adjudication Information for this payer, the identifier sent in SVD01 (Payer Responsibility Sequence Code) of Loop ID-2430 (Line Adjudication Information) must match this value when used.
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 submitting payer has assigned a group identifier to this benefit plan. If not required by this implementation guide, do not send.
INDUSTRY NAME: Insured Group or Policy Number
  1. Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
  2. This is not the number uniquely identifying the subscriber. The unique subscriber number is submitted in Loop ID-2010BA.
Situational
4
93
Name
O 1
AN
1/60
Free-form name
SEMANTIC: SBR04 is plan name.
SITUATIONAL RULE: Required when the submitting payer has assigned a group name to this benefit plan and SBR03 is not used. If not required by this implementation guide, do not send.
INDUSTRY NAME: Group, Insurance Policy or Plan Network Name
Not Used
5
1336
Insurance Type Code
O 1
ID
1/3
Required
6
1143
Coordination of Benefits Code
O 1
ID
1
Code identifying whether there is a coordination of benefits
CODE
DEFINITION
6
No Coordination of Benefits
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
SA
Self-administered Group
TV
Title V
UK
Unknown
VA
Veterans Affairs Plan
WC
Workers' Compensation Health Claim
ZZ
Mutually Defined
Use when no other code value applies.
Required
10
1732
Source of Payment Typology Code
O 1
ID
2/6
Code identifying payer types in the most granular way
INDUSTRY NAME: Source of Payment
The Source of Payment Typology provides a standard for reporting the payer and the payer's product. The Source of Payment Typology is determined by the organization that provides the payment and must be reported using the most granular level of detail defining the payer and the payer's product.
CODE SOURCE 944: Source of Payment Typology

CAS - CLAIM LEVEL ADJUSTMENTS

X12 Name:
Claims Adjustment
X12 Purpose:
To supply adjustment reason codes and amounts as needed for an entire claim or for a particular service within the claim being paid
X12 Syntax:
  1. L050607
    If CAS05 is present, then at least one of CAS06 or CAS07 are required.
  2. C0605
    If CAS06 is present, then CAS05 is required.
  3. C0705
    If CAS07 is present, then CAS05 is required.
  4. L080910
    If CAS08 is present, then at least one of CAS09 or CAS10 are required.
  5. C0908
    If CAS09 is present, then CAS08 is required.
  6. C1008
    If CAS10 is present, then CAS08 is required.
  7. L111213
    If CAS11 is present, then at least one of CAS12 or CAS13 are required.
  8. C1211
    If CAS12 is present, then CAS11 is required.
  9. C1311
    If CAS13 is present, then CAS11 is required.
  10. L141516
    If CAS14 is present, then at least one of CAS15 or CAS16 are required.
  11. C1514
    If CAS15 is present, then CAS14 is required.
  12. C1614
    If CAS16 is present, then CAS14 is required.
  13. L171819
    If CAS17 is present, then at least one of CAS18 or CAS19 are required.
  14. C1817
    If CAS18 is present, then CAS17 is required.
  15. C1917
    If CAS19 is present, then CAS17 is required.
X12 Comments:
Adjustment information is intended to help the provider balance the remittance information. Adjustment amounts should fully explain the difference between submitted charges and the amount paid.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
5
Situational Rule:
Required when the claim has claim level adjustment information. If not required by this implementation guide, do not send.
TR3 Notes:
  1. Only one Group Code is allowed per CAS. If it is necessary to send more than one Group Code at the claim level, repeat the CAS segment.
  2. A single CAS segment contains six repetitions of the "adjustment trio" composed of adjustment reason code, adjustment amount, and adjustment quantity. These six adjustment trios are used to report up to six adjustments related to a particular Claim Adjustment Group Code (CAS01). The first non-zero adjustment is reported in the first adjustment trio (CAS02-CAS04). If there is a second non-zero adjustment, it is reported in the second adjustment trio (CAS05-CAS07), and so on through the sixth adjustment trio (CAS17-CAS19).
  3. Codes and amounts must be reported the same as if creating the 835 to send to the provider.
TR3 Example:
  1. CAS✱PR✱1✱7.93~
  2. CAS✱OA✱93✱15.06~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
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
2
1034
Claim Adjustment Reason Code
M 15
ID
1/5
Code identifying the detailed reason the adjustment was made
INDUSTRY NAME: Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Required
3
782
Monetary Amount
M 1
R
1/18
Monetary amount
SEMANTIC: CAS03 is the amount of adjustment.
INDUSTRY NAME: Adjustment 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
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: CAS04 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
Situational
5
1034
Claim Adjustment Reason Code
X 1
ID
1/5
Code identifying the detailed reason the adjustment was made
SEGMENT SYNTAX: L050607, C0605, C0705
SITUATIONAL RULE: Required when it is necessary to report an additional non-zero adjustment, beyond what has already been supplied, to this claim for the Claim Adjustment Group Code reported in CAS01. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Situational
6
782
Monetary Amount
X 1
R
1/18
Monetary amount
SEMANTIC: CAS06 is the amount of the adjustment.
SEGMENT SYNTAX: L050607, C0605
SITUATIONAL RULE: Required when CAS05 is present. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment 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
7
380
Quantity
X 1
R
1/15
Numeric value of quantity
SEMANTIC: CAS07 is the units of service being adjusted.
SEGMENT SYNTAX: L050607, C0705
SITUATIONAL RULE: Required when CAS05 is present and is related to a units of service adjustment. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Quantity
Situational
8
1034
Claim Adjustment Reason Code
X 1
ID
1/5
Code identifying the detailed reason the adjustment was made
SEGMENT SYNTAX: L080910, C0908, C1008
SITUATIONAL RULE: Required when it is necessary to report an additional non-zero adjustment, beyond what has already been supplied, to this claim for the Claim Adjustment Group Code reported in CAS01. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Situational
9
782
Monetary Amount
X 1
R
1/18
Monetary amount
SEMANTIC: CAS09 is the amount of the adjustment.
SEGMENT SYNTAX: L080910, C0908
SITUATIONAL RULE: Required when CAS08 is present. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment 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
10
380
Quantity
X 1
R
1/15
Numeric value of quantity
SEMANTIC: CAS10 is the units of service being adjusted.
SEGMENT SYNTAX: L080910, C1008
SITUATIONAL RULE: Required when CAS08 is present and is related to a units of service adjustment. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Quantity
Situational
11
1034
Claim Adjustment Reason Code
X 1
ID
1/5
Code identifying the detailed reason the adjustment was made
SEGMENT SYNTAX: L111213, C1211, C1311
SITUATIONAL RULE: Required when it is necessary to report an additional non-zero adjustment, beyond what has already been supplied, to this claim for the Claim Adjustment Group Code reported in CAS01. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Situational
12
782
Monetary Amount
X 1
R
1/18
Monetary amount
SEMANTIC: CAS12 is the amount of the adjustment.
SEGMENT SYNTAX: L111213, C1211
SITUATIONAL RULE: Required when CAS11 is present. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment 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
13
380
Quantity
X 1
R
1/15
Numeric value of quantity
SEMANTIC: CAS13 is the units of service being adjusted.
SEGMENT SYNTAX: L111213, C1311
SITUATIONAL RULE: Required when CAS11 is present and is related to a units of service adjustment. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Quantity
Situational
14
1034
Claim Adjustment Reason Code
X 1
ID
1/5
Code identifying the detailed reason the adjustment was made
SEGMENT SYNTAX: L141516, C1514, C1614
SITUATIONAL RULE: Required when it is necessary to report an additional non-zero adjustment, beyond what has already been supplied, to this claim for the Claim Adjustment Group Code reported in CAS01. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Situational
15
782
Monetary Amount
X 1
R
1/18
Monetary amount
SEMANTIC: CAS15 is the amount of the adjustment.
SEGMENT SYNTAX: L141516, C1514
SITUATIONAL RULE: Required when CAS14 is present. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment 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
16
380
Quantity
X 1
R
1/15
Numeric value of quantity
SEMANTIC: CAS16 is the units of service being adjusted.
SEGMENT SYNTAX: L141516, C1614
SITUATIONAL RULE: Required when CAS14 is present and is related to a units of service adjustment. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Quantity
Situational
17
1034
Claim Adjustment Reason Code
X 1
ID
1/5
Code identifying the detailed reason the adjustment was made
SEGMENT SYNTAX: L171819, C1817, C1917
SITUATIONAL RULE: Required when it is necessary to report an additional non-zero adjustment, beyond what has already been supplied, to this claim for the Claim Adjustment Group Code reported in CAS01. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Situational
18
782
Monetary Amount
X 1
R
1/18
Monetary amount
SEMANTIC: CAS18 is the amount of the adjustment.
SEGMENT SYNTAX: L171819, C1817
SITUATIONAL RULE: Required when CAS17 is present. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment 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
19
380
Quantity
X 1
R
1/15
Numeric value of quantity
SEMANTIC: CAS19 is the units of service being adjusted.
SEGMENT SYNTAX: L171819, C1917
SITUATIONAL RULE: Required when CAS17 is present and is related to a units of service adjustment. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Quantity

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:
Required
Segment Usage:
Required
Segment Repeat:
1
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. Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
  2. It is acceptable to show "0" as the amount paid.
Not Used
3
478
Credit/Debit Flag Code
O 1
ID
1

OI - PAYER CLAIM ADJUSTMENT/VOID INDICATOR

X12 Name:
Other Health Insurance Information
X12 Purpose:
To specify information associated with other health insurance coverage
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
OI09 and OI11 cannot both be 'Y'. Only OI09 or OI11 can be 'Y', or both can be 'N'.
TR3 Example:
OI✱✱✱✱✱✱✱✱✱Y✱✱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
Not Used
7
1359
Provider Accept Assignment Code
O 1
ID
1
Not Used
8
1073
Yes/No Condition or Response Code
O 1
ID
1
Required
9
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: OI09 is payer to data reporting adjustment code. A "Y" value indicates a payer-to-data reporting entity claim is an adjustment. An "N" value indicates payer-to-data reporting entity claim is not an adjustment.
INDUSTRY NAME: Payer Claim Adjustment Indicator
CODE
DEFINITION
N
No
Y
Yes
Not Used
10
1073
Yes/No Condition or Response Code
O 1
ID
1
Required
11
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: OI11 is payer to data reporting void code. A "Y" value indicates a payer-to-data reporting entity claim is a void. An "N" value indicates payer-to-data reporting entity claim is not a void.
INDUSTRY NAME: Payer Claim Void Indicator
CODE
DEFINITION
N
No
Y
Yes

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:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the submitting payer would be required to provide this information when generating an 835 for the provider. If not required by this implementation guide, do not send.
TR3 Example:
MOA✱✱✱A4~
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 the submitting payer would be required to provide this information when generating an 835 for the provider. 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 the submitting payer would be required to provide this information when generating an 835 for the provider. 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.
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: MOA03 is the Remittance Advice Remark Code. See Code Source 411.
SITUATIONAL RULE: Required when the submitting payer would be required to provide this information when generating an 835 for the provider. If not required by this implementation guide, do not send.
INDUSTRY NAME: Claim Payment Remark 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.
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: MOA04 is the Remittance Advice Remark Code. See Code Source 411.
SITUATIONAL RULE: Required when the submitting payer would be required to provide this information when generating an 835 for the provider. If not required by this implementation guide, do not send.
INDUSTRY NAME: Claim Payment Remark 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.
Situational
5
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: MOA05 is the Remittance Advice Remark Code. See Code Source 411.
SITUATIONAL RULE: Required when the submitting payer would be required to provide this information when generating an 835 for the provider. If not required by this implementation guide, do not send.
INDUSTRY NAME: Claim Payment Remark 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.
Situational
6
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: MOA06 is the Remittance Advice Remark Code. See Code Source 411.
SITUATIONAL RULE: Required when the submitting payer would be required to provide this information when generating an 835 for the provider. If not required by this implementation guide, do not send.
INDUSTRY NAME: Claim Payment Remark 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.
Situational
7
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: MOA07 is the Remittance Advice Remark Code. See Code Source 411.
SITUATIONAL RULE: Required when the submitting payer would be required to provide this information when generating an 835 for the provider. If not required by this implementation guide, do not send.
INDUSTRY NAME: Claim Payment Remark 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.
Situational
8
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: MOA08 is the End Stage Renal Disease (ESRD) payment amount.
SITUATIONAL RULE: Required when the submitting payer would be required to provide this information when generating an 835 for the provider. If not required by this implementation guide, do not send.
INDUSTRY NAME: End Stage Renal Disease Payment 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
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 the submitting payer would be required to provide this information when generating an 835 for the provider. 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.

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: 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 Example:
NM1✱PR✱2✱ABC Payer✱✱✱✱✱PI✱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
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
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
PI
Payor Identification
Required
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
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

DTP*573 - CLAIM CHECK OR REMITTANCE 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 Example:
DTP✱573✱D8✱20200601~
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: Adjudication or Payment Date

REF - 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:
5
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement
AND
The data is available in the payer's system.
If not required by this implementation guide, then 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
0B
State License Number
2U
Payer Identification Number
EI
Employer's Identification Number
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.
FY
Claim Office Number
NF
National Association of Insurance Commissioners (NAIC) Code
CODE SOURCE: 245: National Association of Insurance Commissioners (NAIC) Code
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*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:
Required
Segment Repeat:
1
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
This is the submitting payer's internal Claim 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: 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*BP - 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 submitting payer has adjusted this claim. If not required by this implementation guide, do not send.
TR3 Example:
REF✱BP✱R5555589~
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
BP
Adjustment 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: 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

REF*PHC - METHOD OF CLAIM/ENCOUNTER SUBMISSION

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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Example:
REF✱PHC✱E~
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
PHC
Process Handling Code
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: Method of Claim Submission
  1. Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
  2. The information reported in this element must reflect the method in which this claim was received by the submitting payer. Codes reported in REF02 must be one of the following:
    C - Crossover
    Use when the claim was automatically crossed over from one payer to another.
    D - Direct Data Entry
    Use when the claim was manually entered through a DDE terminal or web portal.
    E - Electronic Submission
    Use when the claim was electronically submitted through a transmission or via upload by web portal.
    O - Other
    Use when the claim was submitted in a different format other than DDE, web portal, electronic or paper.
    P - Paper
    Use when the claim was submitted via paper, including paper claims put through an OCR process by the payer.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*CE - IN PLAN NETWORK INDICATOR

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 Example:
REF✱CE✱✱YES~
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
CE
Class of Contract Code
Not Used
2
127
Reference Identification
X 1
AN
1/80
Required
3
352
Description
X 1
AN
1/80
A free-form description to clarify the related data elements and their content
SEGMENT SYNTAX: R0203
INDUSTRY NAME: In Plan Network Indicator
The allowed values for this data element are 'YES' and 'NO'.
Not Used
4
C040
Reference Identifier
O 1

SBR - OTHER PAYER 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 the submitting payer has payer and adjudication information from prior payers. If not required by this implementation guide, do not send.
TR3 Notes:
  1. All information contained in Loop ID-2320B applies only to the payer identified in Loop ID-2330BA. It is specific only to that payer. If information for an additional payer is necessary, repeat Loop ID-2320B with its respective 2330 Loops.
  2. Loop ID-2320B and its subordinate 2330 and 2430 loops convey information demonstrating how this claim was adjudicated by the payers who have previously adjudicated the claim.
  3. This loop is not to be provided for payers who have not adjudicated the claim. For example, the provider submitted claim includes payer information that is subsequent to the payer submitting this transaction.
  4. The payer and adjudication information related to this iteration of Loop ID-2320B and 2430 represents processing performed prior to the adjudication of this claim by the submitting payer and the Other Payer information is to be reported as received from the provider.
TR3 Example:
SBR✱P✱18✱G00786✱✱✱1✱✱✱CI✱512~
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 (Payer Responsibility Sequence Code) of Loop ID-2430 (Line Adjudication Information) must match this value when used.
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
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 this information was provided on the original claim from the provider. 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 ID-2330BB NM109 for this iteration of Loop ID-2320B.
  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 this information was provided on the original claim from the provider. If not required by this implementation guide, do not send.
INDUSTRY NAME: Group, Insurance Policy or Plan Network Name
Not Used
5
1336
Insurance Type Code
O 1
ID
1/3
Required
6
1143
Coordination of Benefits Code
O 1
ID
1
Code identifying whether there is a coordination of benefits
CODE
DEFINITION
1
Coordination of Benefits
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
SA
Self-administered Group
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

CAS - CLAIM LEVEL ADJUSTMENTS

X12 Name:
Claims Adjustment
X12 Purpose:
To supply adjustment reason codes and amounts as needed for an entire claim or for a particular service within the claim being paid
X12 Syntax:
  1. L050607
    If CAS05 is present, then at least one of CAS06 or CAS07 are required.
  2. C0605
    If CAS06 is present, then CAS05 is required.
  3. C0705
    If CAS07 is present, then CAS05 is required.
  4. L080910
    If CAS08 is present, then at least one of CAS09 or CAS10 are required.
  5. C0908
    If CAS09 is present, then CAS08 is required.
  6. C1008
    If CAS10 is present, then CAS08 is required.
  7. L111213
    If CAS11 is present, then at least one of CAS12 or CAS13 are required.
  8. C1211
    If CAS12 is present, then CAS11 is required.
  9. C1311
    If CAS13 is present, then CAS11 is required.
  10. L141516
    If CAS14 is present, then at least one of CAS15 or CAS16 are required.
  11. C1514
    If CAS15 is present, then CAS14 is required.
  12. C1614
    If CAS16 is present, then CAS14 is required.
  13. L171819
    If CAS17 is present, then at least one of CAS18 or CAS19 are required.
  14. C1817
    If CAS18 is present, then CAS17 is required.
  15. C1917
    If CAS19 is present, then CAS17 is required.
X12 Comments:
Adjustment information is intended to help the provider balance the remittance information. Adjustment amounts should fully explain the difference between submitted charges and the amount paid.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
5
Situational Rule:
Required when the claim has claim level adjustment information. If not required by this implementation guide, do not send.
TR3 Notes:
  1. Submitters must use this CAS segment to report prior payers' claim level adjustments that cause the amount paid to differ from the amount originally charged.
  2. Only one Group Code is allowed per CAS. If it is necessary to send more than one Group Code at the claim level, repeat the CAS segment.
  3. A single CAS segment contains six repetitions of the "adjustment trio" composed of adjustment reason code, adjustment amount, and adjustment quantity. These six adjustment trios are used to report up to six adjustments related to a particular Claim Adjustment Group Code (CAS01). The first non-zero adjustment is reported in the first adjustment trio (CAS02-CAS04). If there is a second non-zero adjustment, it is reported in the second adjustment trio (CAS05-CAS07), and so on through the sixth adjustment trio (CAS17-CAS19).
  4. When the CAS information for the prior payer listed in Loop ID-2330BA in this instance of Loop ID-2320B was reported on the claim, the codes and associated amounts must be reported as received.
  5. When the prior payer in Loop ID-2330BA of this instance of Loop ID-2320B is the same as the submitting payer, and the Coordination of Benefits (COB) was performed without submission from the provider, CAS segments are to be populated as remitted to the provider on the 835.
TR3 Example:
  1. CAS✱PR✱1✱7.93~
  2. CAS✱OA✱93✱15.06~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
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
2
1034
Claim Adjustment Reason Code
M 15
ID
1/5
Code identifying the detailed reason the adjustment was made
INDUSTRY NAME: Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Required
3
782
Monetary Amount
M 1
R
1/18
Monetary amount
SEMANTIC: CAS03 is the amount of adjustment.
INDUSTRY NAME: Adjustment 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
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: CAS04 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
Situational
5
1034
Claim Adjustment Reason Code
X 1
ID
1/5
Code identifying the detailed reason the adjustment was made
SEGMENT SYNTAX: L050607, C0605, C0705
SITUATIONAL RULE: Required when it is necessary to report an additional non-zero adjustment, beyond what has already been supplied, to this claim for the Claim Adjustment Group Code reported in CAS01. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Situational
6
782
Monetary Amount
X 1
R
1/18
Monetary amount
SEMANTIC: CAS06 is the amount of the adjustment.
SEGMENT SYNTAX: L050607, C0605
SITUATIONAL RULE: Required when CAS05 is present. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment 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
7
380
Quantity
X 1
R
1/15
Numeric value of quantity
SEMANTIC: CAS07 is the units of service being adjusted.
SEGMENT SYNTAX: L050607, C0705
SITUATIONAL RULE: Required when CAS05 is present and is related to a units of service adjustment. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Quantity
Situational
8
1034
Claim Adjustment Reason Code
X 1
ID
1/5
Code identifying the detailed reason the adjustment was made
SEGMENT SYNTAX: L080910, C0908, C1008
SITUATIONAL RULE: Required when it is necessary to report an additional non-zero adjustment, beyond what has already been supplied, to this claim for the Claim Adjustment Group Code reported in CAS01. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Situational
9
782
Monetary Amount
X 1
R
1/18
Monetary amount
SEMANTIC: CAS09 is the amount of the adjustment.
SEGMENT SYNTAX: L080910, C0908
SITUATIONAL RULE: Required when CAS08 is present. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment 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
10
380
Quantity
X 1
R
1/15
Numeric value of quantity
SEMANTIC: CAS10 is the units of service being adjusted.
SEGMENT SYNTAX: L080910, C1008
SITUATIONAL RULE: Required when CAS08 is present and is related to a units of service adjustment. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Quantity
Situational
11
1034
Claim Adjustment Reason Code
X 1
ID
1/5
Code identifying the detailed reason the adjustment was made
SEGMENT SYNTAX: L111213, C1211, C1311
SITUATIONAL RULE: Required when it is necessary to report an additional non-zero adjustment, beyond what has already been supplied, to this claim for the Claim Adjustment Group Code reported in CAS01. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Situational
12
782
Monetary Amount
X 1
R
1/18
Monetary amount
SEMANTIC: CAS12 is the amount of the adjustment.
SEGMENT SYNTAX: L111213, C1211
SITUATIONAL RULE: Required when CAS11 is present. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment 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
13
380
Quantity
X 1
R
1/15
Numeric value of quantity
SEMANTIC: CAS13 is the units of service being adjusted.
SEGMENT SYNTAX: L111213, C1311
SITUATIONAL RULE: Required when CAS11 is present and is related to a units of service adjustment. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Quantity
Situational
14
1034
Claim Adjustment Reason Code
X 1
ID
1/5
Code identifying the detailed reason the adjustment was made
SEGMENT SYNTAX: L141516, C1514, C1614
SITUATIONAL RULE: Required when it is necessary to report an additional non-zero adjustment, beyond what has already been supplied, to this claim for the Claim Adjustment Group Code reported in CAS01. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Situational
15
782
Monetary Amount
X 1
R
1/18
Monetary amount
SEMANTIC: CAS15 is the amount of the adjustment.
SEGMENT SYNTAX: L141516, C1514
SITUATIONAL RULE: Required when CAS14 is present. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment 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
16
380
Quantity
X 1
R
1/15
Numeric value of quantity
SEMANTIC: CAS16 is the units of service being adjusted.
SEGMENT SYNTAX: L141516, C1614
SITUATIONAL RULE: Required when CAS14 is present and is related to a units of service adjustment. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Quantity
Situational
17
1034
Claim Adjustment Reason Code
X 1
ID
1/5
Code identifying the detailed reason the adjustment was made
SEGMENT SYNTAX: L171819, C1817, C1917
SITUATIONAL RULE: Required when it is necessary to report an additional non-zero adjustment, beyond what has already been supplied, to this claim for the Claim Adjustment Group Code reported in CAS01. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Situational
18
782
Monetary Amount
X 1
R
1/18
Monetary amount
SEMANTIC: CAS18 is the amount of the adjustment.
SEGMENT SYNTAX: L171819, C1817
SITUATIONAL RULE: Required when CAS17 is present. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment 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
19
380
Quantity
X 1
R
1/15
Numeric value of quantity
SEMANTIC: CAS19 is the units of service being adjusted.
SEGMENT SYNTAX: L171819, C1917
SITUATIONAL RULE: Required when CAS17 is present and is related to a units of service adjustment. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Quantity

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:
Required
Segment Repeat:
1
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*EAF - REMAINING PATIENT LIABILITY

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 available in the payer's system.
If not required by this implementation guide, do not send.
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

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 this information was provided on the original claim from the provider. If not required by this implementation guide, do not send.
TR3 Example:
MOA✱✱✱A4~
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 this information was provided on the original claim from the provider. 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 this information was provided on the original claim from the provider. 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.
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: MOA03 is the Remittance Advice Remark Code. See Code Source 411.
SITUATIONAL RULE: Required when this information was provided on the original claim from the provider. If not required by this implementation guide, do not send.
INDUSTRY NAME: Claim Payment Remark 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.
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: MOA04 is the Remittance Advice Remark Code. See Code Source 411.
SITUATIONAL RULE: Required when this information was provided on the original claim from the provider. If not required by this implementation guide, do not send.
INDUSTRY NAME: Claim Payment Remark 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.
Situational
5
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: MOA05 is the Remittance Advice Remark Code. See Code Source 411.
SITUATIONAL RULE: Required when this information was provided on the original claim from the provider. If not required by this implementation guide, do not send.
INDUSTRY NAME: Claim Payment Remark 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.
Situational
6
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: MOA06 is the Remittance Advice Remark Code. See Code Source 411.
SITUATIONAL RULE: Required when this information was provided on the original claim from the provider. If not required by this implementation guide, do not send.
INDUSTRY NAME: Claim Payment Remark 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.
Situational
7
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: MOA07 is the Remittance Advice Remark Code. See Code Source 411.
SITUATIONAL RULE: Required when this information was provided on the original claim from the provider. If not required by this implementation guide, do not send.
INDUSTRY NAME: Claim Payment Remark 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.
Situational
8
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: MOA08 is the End Stage Renal Disease (ESRD) payment amount.
SITUATIONAL RULE: Required when this information was provided on the original claim from the provider. If not required by this implementation guide, do not send.
INDUSTRY NAME: End Stage Renal Disease Payment 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
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 this information was provided on the original claim from the provider. 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.

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 Example:
NM1✱PR✱2✱ABC INSURANCE CO✱✱✱✱✱PI✱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
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
PI
Payor Identification
Required
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
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

DTP*573 - CLAIM CHECK OR REMITTANCE 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 Example:
DTP✱573✱D8✱20200601~
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: Adjudication or Payment Date

REF - 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:
5
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement
AND
The data is available in the payer's system.
If not required by this implementation guide, then 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
0B
State License Number
2U
Payer Identification Number
EI
Employer's Identification Number
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.
NF
National Association of Insurance Commissioners (NAIC) Code
CODE SOURCE: 245: National Association of Insurance Commissioners (NAIC) Code
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

NM1*IL - OTHER PAYER 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:
The information in this segment represents the Subscriber for the payer identified in Loop ID-2330BA.
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 Payer Subscriber Last Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Payer Subscriber First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Payer Subscriber Middle Name
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 available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Payer 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
Required
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
INDUSTRY NAME: Other Payer 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 PAYER 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 available in the payer's system.
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 Subscriber Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Payer Subscriber Address Line

N4 - OTHER PAYER 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 available in the payer's system.
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 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 Payer Subscriber State 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 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 Payer 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 Payer 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 PAYER 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:
The social security number is allowed to be used for this purpose under applicable law or regulation.
AND
The social security number is available in the payer's system.

If not required by this implementation guide, do not send.
TR3 Notes:
Trading partners using this segment are encouraged to explicitly address necessary safeguards in the trading partner agreement.
TR3 Example:
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
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 Payer 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*QC - OTHER PAYER 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: 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 entity reported in Loop ID 2330BB (Other Payer Subscriber Name) is not the patient.
TR3 Notes:
The information in this segment represents the Patient for the payer identified in Loop ID-2330BA.
TR3 Example:
NM1✱QC✱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
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: Other Payer Patient Last Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Payer Patient First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Payer Patient Middle Name
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 available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Payer Patient 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
II
Standard Unique Health Identifier for each Individual in the United States
Use when reporting the HIPAA Individual Patient Identifier.
MI
Member Identification Number
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 patient has been assigned an identifier that is different than the subscriber identifier reported in Loop ID-2330BB NM109. If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Payer Patient 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 PATIENT ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when available in the payer's system.
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 Patient Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Payer Patient Address Line

N4 - OTHER PAYER 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:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when available in the payer's system.
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 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: Other Payer Patient State 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 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: Other Payer 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: Other Payer 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

REF*SY - OTHER PAYER PATIENT 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:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when:
The social security number is allowed to be used for this purpose under applicable law or regulation.
AND
The social security number is available in the payer's system.

If not required by this implementation guide, do not send.
TR3 Notes:
Trading partners using this segment are encouraged to explicitly address necessary safeguards in the trading partner agreement.
TR3 Example:
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
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 Payer Patient 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

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.4 for more information on bundling and section 1.4.2.6 for more information on 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✱✱✱✱1~
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
CDT = Current Dental Terminology
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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Procedure Code Description
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. This is the total charge amount for this service line. The amount is inclusive of the provider's base charge and any applicable tax amounts reported within this line's AMT segments.
  2. Zero "0" is an acceptable value for this element.
  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.
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 available in the payer's system.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 available in the payer's system.If not required by this implementation guide, do not send.
  1. 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.
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.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 when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Prosthesis, Crown, or Inlay Code
If, for whatever reason, the data is not stored within the payer's system, do not use.
CODE
DEFINITION
I
Initial Placement
R
Replacement
When SV305 = R, then the DTP segment in the 2400 loop for Prior Placement is Required.
Situational
6
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: SV306 is the number of procedures.
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Procedure Count
  1. Number of procedures
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
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
Not Used
11
1328
Diagnosis Code Pointer
O 12
N
1/2

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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
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
  1. See Appendix A for code source 135: American Dental Association Codes.
  2. 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 available in the payer's system.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 available in the payer's system.If not required by this implementation guide, do not send.
Additional tooth surface codes can be carried in TOO03-2 through TOO03-5. The code values are the same as in TOO03-1.
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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
  1. Do not use this DTP segment when submitting a Treatment Start Date, Treatment Completion Date or both.
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
DTP✱472✱D8✱20120108~
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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
DTP✱441✱D8✱20120401~
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
Required when the exact Prior Placement Date is not known.
441
Prior Placement
Required 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 - APPLIANCE 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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
DTP✱452✱D8✱20120108~
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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
DTP✱446✱D8✱20120127~
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

DTP*196 - TREATMENT START 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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
  1. When the Treatment Start Date is used, the Date of Service must not be used.
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
DTP✱196✱D8✱20120115~
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
196
Start
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: Treatment Start Date

DTP*198 - TREATMENT COMPLETION 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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
  1. When the Treatment Completion Date is used, the Date of Service must not be used.
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
DTP✱198✱D8✱20120129~
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
198
Completion
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: Treatment Completion Date

CN1 - CONTRACT INFORMATION

X12 Name:
Contract Information
X12 Purpose:
To specify basic data about the contract or contract line item
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when this information is necessary to satisfy contract requirements.

If not required by this implementation guide, do not send.
TR3 Example:
CN1✱02✱550~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1166
Contract Type Code
M 1
ID
2
Code identifying a contract type
CODE
DEFINITION
02
Per Diem
03
Variable Per Diem
04
Flat
05
Capitated
06
Percent
09
Other
Situational
2
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: CN102 is the contract amount.
SITUATIONAL RULE: Required when this information is necessary to satisfy contract requirements.If not required by this implementation guide, do not send.
INDUSTRY NAME: Contract 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
332
Percent, Decimal Format
O 1
R
1/6
Percent given in decimal format (e.g., 0.0 through 100.0 represents 0% through 100%)
SEMANTIC: CN103 is the allowance or charge percent.
SITUATIONAL RULE: Required when this information is necessary to satisfy contract requirements.If not required by this implementation guide, do not send.
INDUSTRY NAME: Contract Percentage
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: CN104 is the contract code.
SITUATIONAL RULE: Required when this information is necessary to satisfy contract requirements.If not required by this implementation guide, do not send.
INDUSTRY NAME: Contract 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.
Situational
5
338
Terms Discount Percent
O 1
R
1/6
Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date
SITUATIONAL RULE: Required when this information is necessary to satisfy contract requirements.If not required by this implementation guide, do not send.
INDUSTRY NAME: Terms Discount Percentage
Situational
6
799
Version Identifier
O 1
AN
1/30
Revision level of a particular format, program, technique or algorithm
SEMANTIC: CN106 is an additional identifying number for the contract.
SITUATIONAL RULE: Required when this information is necessary to satisfy contract requirements.If not required by this implementation guide, do not send.
INDUSTRY NAME: Contract Version Identifier

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:
5
Situational Rule:
Required when available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
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 or 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*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:
5
Situational Rule:
Required when available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
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

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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
  1. The K3 segment is expected to be used only when necessary to meet the unexpected data requirement of a legislative authority. Before this segment can be used:

    - The X12N Health Care Claim workgroup must conclude there is no other available option in the implementation guide to meet the emergency legislative requirement.

    - The requestor must submit a proposal for approval accompanied by the relevant business documentation to the X12N Health Care Claim workgroup chairs 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 X12N Health Care Claim workgroup 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.
  3. X12N will submit the necessary data maintenance and refer the request to the appropriate data content committee(s).
  4. If, for whatever reason, the data is not stored within the payer's system, do not use.
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
Not Used
2
1333
Record Format Code
O 1
ID
1/2
Not Used
3
C001
Composite Unit of Measure
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 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.

OR

Required when Loop ID-2310B Rendering Provider is not used AND this particular line item has different Rendering Provider information than that which is carried in Loop ID-2010AA Billing Provider.

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. Used for all types of rendering providers including laboratories. The Rendering Provider is the person or company (laboratory or other facility) who rendered the care. In the case where a substitute provider (locum tenens) was used, enter that provider's information here.
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
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
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: Rendering Provider Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when available in the payer's system.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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Rendering Provider Identifier
If, for whatever reason, the data is not stored within the payer's system, do not use.
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:
Situational
Segment Repeat:
1
Situational Rule:
Required when available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
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:
3
Situational Rule:
Required when available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
REF✱G2✱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
0B
State License Number
G2
Provider Commercial Number
This code designates a proprietary provider number for the submitting payer identified in the Payer Name loop, Loop ID-2330A where 2320 SBR06 equals 6. This is to be used by all payers including: Medicare, Medicaid, Blue Cross, etc.
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: 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*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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
NM1✱DD✱1✱SMITH✱JOHN✱S✱✱✱XX✱1234567899~
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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Assistant Surgeon Primary Identifier
If, for whatever reason, the data is not stored within the payer's system, do not use.
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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
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:
3
Situational Rule:
Required when available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
REF✱G2✱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
0B
State License Number
G2
Provider Commercial Number
This code designates a proprietary provider number for the submitting payer identified in the Payer Name loop, Loop ID-2330A where 2320 SBR06 equals 6. This is to be used by all payers including: Medicare, Medicaid, Blue Cross, etc.
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: 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 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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
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
Use this code for 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
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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.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 available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Supervising Provider Identifier
If, for whatever reason, the data is not stored within the payer's system, do not use.
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 - 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:
3
Situational Rule:
Required when available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
REF✱0B✱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
0B
State License Number
G2
Provider Commercial Number
This code designates a proprietary provider number for the submitting payer identified in the Payer Name loop, Loop ID-2330A where 2320 SBR06 equals 6. This is to be used by all payers including: Medicare, Medicaid, Blue Cross, etc.
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: Supervising 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

SVD*R - 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 2320 SBR06 = 6 and an 835 sent to the provider would have included service line detail.
OR
Required when the related Loop ID 2320 SBR06 = 1; and the data was present on the provider submitted claim.

If not required by this implementation guide, do not send.
TR3 Notes:
When SVD01 matches the SBR01 in Loop ID-2320B, the payer and adjudication information related to this iteration of Loop ID-2320B and 2430 represents processing performed prior to the adjudication of this claim and the Other Payer information is to be reported as received from the provider.

When SVD01 matches the SBR01 in Loop ID-2320A, the payer and adjudication information related to this iteration of Loop ID-2320A and 2430 represents the adjudication results of the submitting payer.
TR3 Example:
SVD✱P✱55✱HC:84550✱✱3~
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: Payer Responsibility Sequence Code
The value reported in this field indicates the payer responsible for the reimbursement described in this iteration of Loop ID-2430. The value indicates the Payer by matching the SBR01 (Payer Responsibility Sequence Code) in Loop ID-2320A, or the Other Payer by matching the SBR01 (Other Payer Responsibility Sequence Code) in Loop ID-2320B.
CODE
DEFINITION
R
Non-specified
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 pay 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
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 provider. 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 provider. 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 provider. 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 provider. 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
Situational
3-9
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 provider. If not required by this implementation guide, do not send.
Situational
3-10
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 provider. If not required by this implementation guide, do not send.
Situational
3-11
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 provider. If not required by this implementation guide, do not send.
Situational
3-12
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 provider. If not required by this implementation guide, do not send.
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. 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.
  2. When SVD01 matches the SBR01 in Loop ID-2320A, this is the number of paid units which would have been sent on the remittance advice. When paid units are not present on the remittance advice, the value must be one.

    When SVD01 matches the SBR01 in Loop ID-2320B, this is the number of paid units as reported on the submitted claim. When paid units are not present on the submitted claim, the value must be one.
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

CAS - LINE ADJUSTMENT

X12 Name:
Claims Adjustment
X12 Purpose:
To supply adjustment reason codes and amounts as needed for an entire claim or for a particular service within the claim being paid
X12 Syntax:
  1. L050607
    If CAS05 is present, then at least one of CAS06 or CAS07 are required.
  2. C0605
    If CAS06 is present, then CAS05 is required.
  3. C0705
    If CAS07 is present, then CAS05 is required.
  4. L080910
    If CAS08 is present, then at least one of CAS09 or CAS10 are required.
  5. C0908
    If CAS09 is present, then CAS08 is required.
  6. C1008
    If CAS10 is present, then CAS08 is required.
  7. L111213
    If CAS11 is present, then at least one of CAS12 or CAS13 are required.
  8. C1211
    If CAS12 is present, then CAS11 is required.
  9. C1311
    If CAS13 is present, then CAS11 is required.
  10. L141516
    If CAS14 is present, then at least one of CAS15 or CAS16 are required.
  11. C1514
    If CAS15 is present, then CAS14 is required.
  12. C1614
    If CAS16 is present, then CAS14 is required.
  13. L171819
    If CAS17 is present, then at least one of CAS18 or CAS19 are required.
  14. C1817
    If CAS18 is present, then CAS17 is required.
  15. C1917
    If CAS19 is present, then CAS17 is required.
X12 Comments:
Adjustment information is intended to help the provider balance the remittance information. Adjustment amounts should fully explain the difference between submitted charges and the amount paid.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
5
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 Notes:
A single CAS segment contains six repetitions of the "adjustment trio" composed of adjustment reason code, adjustment amount, and adjustment quantity. These six adjustment trios are used to report up to six adjustments related to a particular Claim Adjustment Group Code (CAS01). The first non-zero adjustment is reported in the first adjustment trio (CAS02-CAS04). If there is a second non-zero adjustment, it is reported in the second adjustment trio (CAS05-CAS07), and so on through the sixth adjustment trio (CAS17-CAS19).
TR3 Example:
  1. CAS✱PR✱1✱7.93~
  2. CAS✱OA✱93✱15.06~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
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
2
1034
Claim Adjustment Reason Code
M 15
ID
1/5
Code identifying the detailed reason the adjustment was made
INDUSTRY NAME: Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Required
3
782
Monetary Amount
M 1
R
1/18
Monetary amount
SEMANTIC: CAS03 is the amount of adjustment.
INDUSTRY NAME: Adjustment 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
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: CAS04 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
Situational
5
1034
Claim Adjustment Reason Code
X 1
ID
1/5
Code identifying the detailed reason the adjustment was made
SEGMENT SYNTAX: L050607, C0605, C0705
SITUATIONAL RULE: Required when it is necessary to report an additional non-zero adjustment, beyond what has already been supplied, to this service line for the Claim Adjustment Group Code reported in CAS01. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Situational
6
782
Monetary Amount
X 1
R
1/18
Monetary amount
SEMANTIC: CAS06 is the amount of the adjustment.
SEGMENT SYNTAX: L050607, C0605
SITUATIONAL RULE: Required when CAS05 is present. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment 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
7
380
Quantity
X 1
R
1/15
Numeric value of quantity
SEMANTIC: CAS07 is the units of service being adjusted.
SEGMENT SYNTAX: L050607, C0705
SITUATIONAL RULE: Required when CAS05 is present and is related to a units of service adjustment. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Quantity
Situational
8
1034
Claim Adjustment Reason Code
X 1
ID
1/5
Code identifying the detailed reason the adjustment was made
SEGMENT SYNTAX: L080910, C0908, C1008
SITUATIONAL RULE: Required when it is necessary to report an additional non-zero adjustment, beyond what has already been supplied, to this service line for the Claim Adjustment Group Code reported in CAS01. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Situational
9
782
Monetary Amount
X 1
R
1/18
Monetary amount
SEMANTIC: CAS09 is the amount of the adjustment.
SEGMENT SYNTAX: L080910, C0908
SITUATIONAL RULE: Required when CAS08 is present. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment 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
10
380
Quantity
X 1
R
1/15
Numeric value of quantity
SEMANTIC: CAS10 is the units of service being adjusted.
SEGMENT SYNTAX: L080910, C1008
SITUATIONAL RULE: Required when CAS08 is present and is related to a units of service adjustment. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Quantity
Situational
11
1034
Claim Adjustment Reason Code
X 1
ID
1/5
Code identifying the detailed reason the adjustment was made
SEGMENT SYNTAX: L111213, C1211, C1311
SITUATIONAL RULE: Required when it is necessary to report an additional non-zero adjustment, beyond what has already been supplied, to this service line for the Claim Adjustment Group Code reported in CAS01. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Situational
12
782
Monetary Amount
X 1
R
1/18
Monetary amount
SEMANTIC: CAS12 is the amount of the adjustment.
SEGMENT SYNTAX: L111213, C1211
SITUATIONAL RULE: Required when CAS11 is present. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment 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
13
380
Quantity
X 1
R
1/15
Numeric value of quantity
SEMANTIC: CAS13 is the units of service being adjusted.
SEGMENT SYNTAX: L111213, C1311
SITUATIONAL RULE: Required when CAS11 is present and is related to a units of service adjustment. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Quantity
Situational
14
1034
Claim Adjustment Reason Code
X 1
ID
1/5
Code identifying the detailed reason the adjustment was made
SEGMENT SYNTAX: L141516, C1514, C1614
SITUATIONAL RULE: Required when it is necessary to report an additional non-zero adjustment, beyond what has already been supplied, to this service line for the Claim Adjustment Group Code reported in CAS01. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Situational
15
782
Monetary Amount
X 1
R
1/18
Monetary amount
SEMANTIC: CAS15 is the amount of the adjustment.
SEGMENT SYNTAX: L141516, C1514
SITUATIONAL RULE: Required when CAS14 is present. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment 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
16
380
Quantity
X 1
R
1/15
Numeric value of quantity
SEMANTIC: CAS16 is the units of service being adjusted.
SEGMENT SYNTAX: L141516, C1614
SITUATIONAL RULE: Required when CAS14 is present and is related to a units of service adjustment. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Quantity
Situational
17
1034
Claim Adjustment Reason Code
X 1
ID
1/5
Code identifying the detailed reason the adjustment was made
SEGMENT SYNTAX: L171819, C1817, C1917
SITUATIONAL RULE: Required when it is necessary to report an additional non-zero adjustment, beyond what has already been supplied, to this service line for the Claim Adjustment Group Code reported in CAS01. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Situational
18
782
Monetary Amount
X 1
R
1/18
Monetary amount
SEMANTIC: CAS18 is the amount of the adjustment.
SEGMENT SYNTAX: L171819, C1817
SITUATIONAL RULE: Required when CAS17 is present. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment 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
19
380
Quantity
X 1
R
1/15
Numeric value of quantity
SEMANTIC: CAS19 is the units of service being adjusted.
SEGMENT SYNTAX: L171819, C1917
SITUATIONAL RULE: Required when CAS17 is present and is related to a units of service adjustment. If not required by this implementation guide, do not send.
INDUSTRY NAME: Adjustment Quantity

DTP*573 - LINE CHECK OR REMITTANCE 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✱20200601~
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: Adjudication or Payment Date

AMT*EAF - REMAINING PATIENT LIABILITY

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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
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

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✱987654~
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. The number must be unique within a specific interchange (ISA-IEA), but can repeat in other interchanges.

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 Post-adjudicated Claims Data Reporting: Dental (008020X300)

FEBRUARY 2022

Copyright © 2008-22, X12 Incorporated, Format © 2008-22 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 Post-Adjudicated Claims Data Reporting: Dental Implementation Guide describes the use of the X12 Health Care Claim (837) transaction set for reporting health care dental service post-adjudicated data:

  • to satisfy state and federal reporting requirements such as; Medicare and Medicaid encounters, All Payer Claims Databases, and Health Care Insurance Exchanges
  • for use in health data analysis from payer data

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 and need to be implemented consistently by all organizations. To facilitate a smooth transition into the EDI environment, uniform implementation is critical.

The purpose of this implementation guide is to define the transaction set used to exchange post-adjudicated claims data. The entities involved in this exchange include payers and organizations that receive post-adjudicated claim data. This exchange may be performed directly or via transmission intermediaries, such as clearinghouses and value added networks. For further clarification on definitions of the participants, see X12 Wordbook for definitions.

This is the technical report document for the X12N 837 Health Care Claims (837) transaction for dental post-adjudicated data reporting.

This document provides a definitive statement of what trading partners must be able to support in this implementation 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 008020X300.

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. This implementation guide limits 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 is used by trading partners to exchange post-adjudicated claims data. Trading partners include:

  • payers
  • All Payer Claims Database administrators
  • Health Insurance Exchange administrators
  • other data reporting entities

For purposes of this standard, the payer is an entity that pays claims or administers the insurance product, benefit, or both. For example, a payer may be an insurance company, health maintenance organization (HMO), government agency (Medicare, Medicaid, TRICARE, etc.) or an entity such as a third party administrator (TPA), 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 intended to originate with the payer to report encounter or post-adjudicated claim data to:

  • another payer.
  • an All Payer Claims Database maintained by public health entities.
  • a Health Insurance Exchange.

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 Data Changed By Adjudication

Payer adjudication practices may result in altered representations of claim data. This section describes a few of those possible scenarios and how to represent that data in a way that allows the receiver to understand what transpired. The examples follow the claim from the originating provider, through adjudication to the 835 transaction, and then show how the adjudicated data is presented in the data reporting transaction. Only the noteworthy segments are shown in the examples.

1.4.2.1 Typical adjudication

Claim and Line adjudicated as submitted.
The original claim from the provider included a single line item and was adjudicated as a single line item by the payer.

Provider claim: CLM*1CL*100***11:B:1~
SV3*AD:A*100****1~
835 to provider: CLP*1CL*1*100*75**12*2011092600001~
SVC*AD:A*100*75**1~
CAS*CO*45*25~
Health Plan Claim: CLM*1CL*100***11:B:1~
REF*F8*2011092600001~
SV3*AD:A*100****1~
SVD*<Related SBR01 value>*75*AD:A**1~
CAS*CO*45*25~

1.4.2.2 Adjudicated procedure different than submitted

Adjudicated procedure is different than the submitted procedure.
The original claim from the provider included a single line item with procedure code A. During adjudication, the payer changed the procedure code to B.

Provider claim: CLM*2CL*100***11:B:1~
SV3*AD:A*100****1~AD:~
835 to provider: CLP*2CL*1*100*50**12*2011092600002~
SVC*AD:B*100*50**1*AD:A~
CAS*CO*45*50~
Health Plan Claim: CLM*2CL*100***11:B:1~
REF*F8*2011092600002~
SV3*AD:A*100****1~
SVD*<Related SBR01 value>*50*AD:B**1~
CAS*CO*45*50~

1.4.2.3 Adjudicated Line Split

Adjudicated procedure is different than the submitted procedure.
The original claim from the provider included a single line item with a range of service dates that spanned across eligibility or benefit years requiring split processing by the payer.

Provider claim: CLM*3CL*300***11:B:1~
SV3*AD:A*300****3~
DTP*472*RD8*20101231-20110102~
835 to provider:

CLP*3CL*1*300*225**12*2011092600003~
SVC*AD:A*100*75**1~
DTM*472*20101231~
CAS*CO*45*25~

SVC*AD:A*200*150**2~
DTM*150*20110101~
DTM*151*20110102~
CAS*CO*45*50~

Health Plan claim: CLM*3CL*300***11:B:1~
REF*F8*2011092600003~
SV3*AD:A*300****3~
DTP*472*RD8*20101231-20110102~
SVD*<Related SBR01 value>*75*AD:A**1~
CAS*CO*45*25~
SVD*<Related SBR01 value>*150*AD:A**2~
CAS*CO*45*50~

1.4.2.4 Bundled Lines

Submitted lines combined into a single line for processing and pricing.
The original claim from the provider included two line items the payer considers payable as a single service. As a result, the payer adds a code that represents those combined services to the adjudication system.

Provider claim: CLM*4CL*200***11:B:1~
SV3*AD:A*100****1~
SV3*AD:B*100****1~
835 example:

CLP*4CL*1*200*100*20*12*2011092600004~
SVC*AD:C*100*100***AD:A~
CAS*OA*94*-100~
CAS*CO*45*80~
CAS*PR*2*20~

SVC*AD:C*100*0**0*AD:B*1~
CAS*OA*97*100~

Health Plan Claim:

CLM*4CL*300***11:B:1~
REF*F8*2011092600004~
SV3*AD:A*100****1~
SVD*<Related SBR01 value>*100*AD:C**1~
CAS*OA*94*-100~
CAS*CO*45*80~
CAS*PR*2*20~

SV2*AD:B*100****1~
SVD*<Related SBR01 value>*0*AD:C**1~
CAS*OA*97*100~

1.4.2.5 Split Claims

Submitted lines split into multiple claims for processing.
The original claim from the provider included two line items. For processing reasons, the payer created two separate claims with a single line.

Provider Claim:

CLM*5CL*220***11:B:1~
SV3*AD:A*100****1~
DTP*472*D8*20101231~

SV2*AD:B****1~AD:~
DTP*472*D8*20110101~

835 to provider:

CLP*5CL*1*100*50**12*2011092600005~
SVC*AD:A*100*50~
DTM*472*20101231~
CAS*CO*45*500~

CLP*5CL*1*100*50**12*2011092600015~
SVC*AD:B*120*60~
DTM*472*20110101~
CAS*CO*45*60~

Health Plan claim:

CLM*5CL*100***11:B:1~
REF*F8*2011092600005~
SV3*AD:A*100****1~
DTP*472*D8*20101231~
SVD*<Related SBR01 value>*50*AD:A**1~
CAS*CO*45*50~

CLM*5CL*120***11:B:1~
REF*F8*2011092600015~
SV3*AD:A*100****1~
DTP*472*D8*20110101~
SVD*<Related SBR01 value>*60*AD:B**2~
CAS*CO*45*60~

1.4.2.6 Unbundled Lines

Submitted lines split into multiple lines for processing and pricing.
The original claim from the provider included a single line items the payer considers payable as multiple services. As a result, the payer adds line items and adjudicates using procedure codes that represent the independent services to the adjudication system.

Provider Claim: CLM*6CL*200***11:B:1~
SV3*AD:A*100****1~
DTP*472*D8*20110926~
835 to provider: CLP*6CL*1*200*120**12*2011092600006~
SVC*AD:B*200*60***AD:A~
CAS*CO*45*140~
SVC*AD:C*0*60***AD:A~
CAS*OA*94*-60~
Health Plan claim:

CLM*6CL*200***11:B:1~
REF*F8*2011092600006~
SV3*AD:A*100****1~
SVD*<Related SBR01 value>*60*AD:B**1*AD:A~
CAS*CO*45*140~

SVD*<Related SBR01 value>*60*AD:C**1*AD:A~
CAS*OA*94*-60~

1.4.3 Subscriber / Patient Information

The structure of this implementation guide is different from a "normal" provider submitted claim in that, as an entity, the Data Receiver does not always assign subscriber or patient identifier of their own. With the exception of Medicare and Medicaid encounters, the desire of the receiver is to retain the subscriber/patient relationship as known to the submitting entity.

Header Level Subscriber/Patient Information (Loops 2010BA and 2010CA)
For submissions directed to entities such as an All Payer Claims Database or Health Insurance Exchange, the Subscriber identified in loop 2010BA is the actual subscriber as known to the submitting plan, and report identifiers as assigned by the receiving entity and social security numbers when allowed by applicable law and properly secured.

Since the Data Receiver is not serving in the role of a payer, things like the Payer Responsibility Sequence Code (SBR01) and others are not applicable. Where able, these elements have been changed to Not Used. If the element is defined as Mandatory in the standard (SBR01 for example), a default has been defined.

In the case of submissions to Medicare and Medicaid agencies, the Subscriber identified in loop 2010BA is the patient and therefore the patient loop is never used.

Submitting Payer (Loop-ID 2320A)
In this scenario, the subscriber is the actual subscriber as defined by the payer's enrollment files. The patient information is used when the patient is a dependent of the subscriber as defined by the payer's enrollment files.

Coordination of Benefits Submission (Loop-ID 2320B)
In this scenario, the subscriber and patient information is reported as received on the claim submitted to the payer requesting payment.

1.4.4 Provider Taxonomy Code Reporting

Provider Taxonomy Codes describe provider type, classification, and area of specialization and are maintained by the National Uniform Claims Committee. For use in post-adjudication reporting, the taxonomy reported is determined by the payer's adjudication process. When the payer does not use taxonomies in their processing, the taxonomy may not be included in the transaction.

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
Balancing of claim payment information is done payer by payer. For the submitting payer that has service line adjudication data, the sum of all line level payment amounts for the submitting payer (Loop ID-2430 SVD02 Service Line Paid Amount where Loop ID-2430 SVD01 Payer Responsibility Sequence Code = Loop ID-2320A SBR01 Payer Responsibility Sequence Code) less any claim level adjustment amounts (Loop ID-2320A CAS adjustments) must balance to the clam level payment amount (Loop ID-2320A AMT02 Payer Paid Amount). Expressed as a calculation for the submitting payer that has service line adjudication data: {Loop ID-2320A AMT02 Payer Paid Amount} = {sum of Loop ID-2430 SVD02 Service Line Paid Amounts} minus {sum of Loop ID-2320A CAS adjustment amounts.

For a given other payer that has service line adjudication data, the sum of all line level payment amounts for that other payer (Loop ID-2430 SVD02 Service Line Paid Amount where Loop ID-2430 SVD01 Payer Responsibility Sequence Code = Loop-ID-2320B SBR01 Other Payer Responsibility Sequence Code) less any claim level adjustment amounts (Loop ID-2320B CAS adjustments) must balance to the claim level payment amount (Loop ID-2320B AMT02 Payer Paid Amount). Expressed as a calculation for a given other payer that has service line adjudication date: {Loop ID-2320B AMT02 Payer Paid Amount} = {sum of Loop ID-2430 SVD02 Service Line Paid Amounts} minus {sum of Loop ID-2320B CAS adjustment amounts}.

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. This identifier must match the identifier of the corresponding payer identifier reported in Loop ID-2320 SBR01.

Adjustment Calculations
Adjustments are reported in the CAS segments of Loop ID-2320 (claim level) and Loop ID-2430 (line level). Adjustment amounts 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. Note that this example includes adjustments at both the service line and a separate claim level adjustment. Claim adjustments ARE NOT the sum of the line adjustments.

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

Service line balancing applies independently for each Payer's Line Adjudication Information loop, Loop ID-2430. In order to balance, the sum of all service line adjustments and the service line payment within a Payer's 2430 Line Adjudication Information loop must balance to the Line Item Charge Amount for that service line.

When a single service line has multiple 2430 loops for the same Payer, balancing logic must be modified. In the case of 2430 loops from two benefit plans from the same Payer, each SVD loop must balance independently as described above. Whereas, in the case of a single payer's adjudication unbundling services resulting in multiple 2430 loops, one for each unbundled service, the payments and adjustments for all such loops for that Payer must be summed together to balance to the Line Item Charge.

The balancing calculation for each 2430 loop (other than the exceptions listed above) is as follows:

{Sum of all Loop-ID 2430 CAS Adjustment Amounts},
plus
{Loop-ID 2430 SVD02 Service Line Paid Amount}
=
{Loop ID-2400 SV203 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.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. Some of the information reported in the 835 must be included in the Post-Adjudicated Claims Data Reporting 837.

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.

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 X12 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 (008020X300) defines the X12 requirements for the Post-adjudicated Claims Data Reporting: Dental. It is based on version/release/subrelease 008020 of the X12 standards.