837 Transaction Set Listing

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. All positions within each of the data elements must be filled.
  2. 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.
  3. The first element separator defines the element separator to be used through the entire interchange.
  4. The ISA segment terminator defines the segment terminator used throughout the entire interchange.
  5. Spaces in the example interchanges are represented by "." for clarity.
TR3 Example:
ISA✱00✱..........✱01✱SECRET....✱ZZ✱SUBMITTERS.ID..✱ZZ✱RECEIVERS.ID...✱030101✱1253✱^✱00501✱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)
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)
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)
27
Carrier Identification Number as assigned by Health Care Financing Administration (HCFA)
28
Fiscal Intermediary Identification Number as assigned by Health Care Financing Administration (HCFA)
29
Medicare Provider and Supplier Identification Number as assigned by Health Care Financing Administration (HCFA)
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)
27
Carrier Identification Number as assigned by Health Care Financing Administration (HCFA)
28
Fiscal Intermediary Identification Number as assigned by Health Care Financing Administration (HCFA)
29
Medicare Provider and Supplier Identification Number as assigned by Health Care Financing Administration (HCFA)
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
M 1
ID
5
Code specifying the version number of the interchange control segments
CODE
DEFINITION
00501
Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
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
M 1
ID
1
Code indicating sender's request for an interchange acknowledgment
See Section B.1.1.5.1 for interchange acknowledgment information.
CODE
DEFINITION
0
No Interchange Acknowledgment Requested
1
Interchange Acknowledgment Requested (TA1)
Required
15
I14
Interchange Usage Indicator
M 1
ID
1
Code indicating whether data enclosed by this interchange envelope is test, production or information
CODE
DEFINITION
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✱20071231✱0802✱1✱X✱005010X298A1~
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
005010X298A1
Post-adjudicated Claims Data Reporting: Professional

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✱005010X298A1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
143
Transaction Set Identifier Code
M 1
ID
3
Code uniquely 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
005010X298A1
Post-adjudicated Claims Data Reporting: Professional

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/50
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
The inventory file number of the transmission assigned by the submitter's system. This number operates as a batch control number.
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 qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
2
Non-Person Entity
Required
3
1035
Name Last or Organization Name
O 1
AN
1/60
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
O 1
ID
1/2
Code designating 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
O 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
O 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/60

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
O 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
O 1
AN
1/256
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0304
Situational
5
365
Communication Number Qualifier
O 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
O 1
AN
1/256
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
O 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
O 1
AN
1/256
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 qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
2
Non-Person Entity
Required
3
1035
Name Last or Organization Name
O 1
AN
1/60
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
O 1
ID
1/2
Code designating 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
O 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
O 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/60

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 defining 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✱207Q00000X~
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
O 1
ID
2/3
Code qualifying 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
O 1
AN
1/50
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
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 (Standard ISO) 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
O 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
O 1
ID
3
Not Used
11
373
Date
O 1
DT
8
Not Used
12
337
Time
O 1
TM
4/8
Not Used
13
374
Date/Time Qualifier
O 1
ID
3
Not Used
14
373
Date
O 1
DT
8
Not Used
15
337
Time
O 1
TM
4/8
Not Used
16
374
Date/Time Qualifier
O 1
ID
3
Not Used
17
373
Date
O 1
DT
8
Not Used
18
337
Time
O 1
TM
4/8
Not Used
19
374
Date/Time Qualifier
O 1
ID
3
Not Used
20
373
Date
O 1
DT
8
Not Used
21
337
Time
O 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, insurer, primary administrator, contract holder, 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 intent is to capture the information as stored in the payer's system.
  4. 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✱2✱ABC Group Practice✱✱✱✱✱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 qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
2
Non-Person Entity
Required
3
1035
Name Last or Organization Name
O 1
AN
1/60
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
O 1
ID
1/2
Code designating 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
Centers for Medicare and Medicaid Services National Provider Identifier
CODE SOURCE: 537: Centers for Medicare & Medicaid Services National Provider Identifier
Situational
9
67
Identification Code
O 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
O 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/60

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. C0605
    If N406 is present, then N405 is required.
  3. 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
O 1
ID
2
Code (Standard State/Province) as defined by appropriate government agency
COMMENT: N402 is required only if city name (N401) is in the U.S. or Canada.
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
O 1
ID
3/15
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
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
O 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
O 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
O 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

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 qualifying 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
O 1
AN
1/50
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
Not Used
3
352
Description
O 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 qualifying the Reference Identification
CODE
DEFINITION
0B
State License Number
Required
2
127
Reference Identification
O 1
AN
1/50
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
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF - BILLING PROVIDER SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
2
Situational Rule:
Required when 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 qualifying the Reference Identification
CODE
DEFINITION
G2
Provider Commercial Number
LU
Location Number
Required
2
127
Reference Identification
O 1
AN
1/50
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
Not Used
3
352
Description
O 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 defining 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: Requried 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/50
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

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, insurer, primary administrator, contract holder, 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 qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
2
Non-Person Entity
Required
3
1035
Name Last or Organization Name
O 1
AN
1/60
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
O 1
ID
1/2
Code designating 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
O 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
O 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/60

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. C0605
    If N406 is present, then N405 is required.
  3. 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
O 1
ID
2
Code (Standard State/Province) as defined by appropriate government agency
COMMENT: N402 is required only if city name (N401) is in the U.S. or Canada.
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
O 1
ID
3/15
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
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
O 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
O 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
O 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

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
O 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
O 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
SEMANTIC: DMG02 is the date of birth.
SEGMENT SYNTAX: P0102
INDUSTRY NAME: Subscriber Birth Date
Required
3
1068
Gender Code
O 1
ID
1
Code indicating the sex of the individual
INDUSTRY NAME: Subscriber Gender Code
CODE
DEFINITION
F
Female
M
Male
U
Unknown
Not Used
4
1067
Marital Status Code
O 1
ID
1
Not Used
5
C056
Composite Race or Ethnicity Information
O 10
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
O 1
ID
1/3
Not Used
11
1271
Industry Code
O 1
AN
1/30

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 qualifying 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
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Subscriber Social Security Number
Not Used
3
352
Description
O 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 qualifying the Reference Identification
CODE
DEFINITION
Y4
Agency Claim Number
Required
2
127
Reference Identification
O 1
AN
1/50
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
Not Used
3
352
Description
O 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, insurer, primary administrator, contract holder, 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 qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
2
Non-Person Entity
Required
3
1035
Name Last or Organization Name
O 1
AN
1/60
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
O 1
ID
1/2
Not Used
9
67
Identification Code
O 1
AN
2/80
Not Used
10
706
Entity Relationship Code
O 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/60

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.
  4. This loop is not used for Medicare and Medicaid encounters.
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 defining 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
O 1
ID
2/3
Not Used
6
1251
Date Time Period
O 1
AN
1/35
Not Used
7
355
Unit or Basis for Measurement Code
O 1
ID
2
Not Used
8
81
Weight
O 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, insurer, primary administrator, contract holder, 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 qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Required
3
1035
Name Last or Organization Name
O 1
AN
1/60
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
O 1
ID
1/2
Code designating 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
O 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
O 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/60

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. C0605
    If N406 is present, then N405 is required.
  3. 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
O 1
ID
2
Code (Standard State/Province) as defined by appropriate government agency
COMMENT: N402 is required only if city name (N401) is in the U.S. or Canada.
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
O 1
ID
3/15
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
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
O 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
O 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
O 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

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
O 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
O 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
SEMANTIC: DMG02 is the date of birth.
SEGMENT SYNTAX: P0102
INDUSTRY NAME: Patient Birth Date
Required
3
1068
Gender Code
O 1
ID
1
Code indicating the sex of the individual
INDUSTRY NAME: Patient Gender Code
CODE
DEFINITION
F
Female
M
Male
U
Unknown
Not Used
4
1067
Marital Status Code
O 1
ID
1
Not Used
5
C056
Composite Race or Ethnicity Information
O 10
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
O 1
ID
1/3
Not Used
11
1271
Industry Code
O 1
AN
1/30

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 qualifying 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
O 1
AN
1/50
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
Not Used
3
352
Description
O 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 qualifying the Reference Identification
CODE
DEFINITION
Y4
Agency Claim Number
Required
2
127
Reference Identification
O 1
AN
1/50
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
Not Used
3
352
Description
O 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✱A37YH556✱500✱✱✱11:B:1~
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 Professional Service (SV1) segments for this claim.
  3. This amount represents the sum of the line charge amounts included in this portion of the claim.
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: C023-02 qualifies C023-01 and C023-03.
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/2
Code identifying where services were, or may be, performed; the first and second positions of the Uniform Bill 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
O 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 frequency of the claim; this is the third position of the Uniform Billing Claim Form Bill Type
INDUSTRY NAME: Claim Frequency Code
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: Yes No Condition or Response Code
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.
Within this element the context of the word assignment is related to the relationship between the provider and the payer. This is NOT the field for reporting whether the patient has or has not assigned benefits to the provider. The benefit assignment indicator is in CLM08.
CODE
DEFINITION
A
Assigned
B
Assignment Accepted on Clinical Lab Services Only
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: Yes No Condition or Response Code
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
Situational
10
1351
Patient Signature Source Code
O 1
ID
1
Code indicating how the patient or subscriber authorization signatures were obtained and how they are being retained by the provider
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
CODE
DEFINITION
P
Signature generated by provider because the patient was not physically present for services
Signature generated by an entity other than the patient according to State or Federal law.
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 (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
02
Physically Handicapped Children's Program
03
Special Federal Funding
05
Disability
09
Second Opinion or Surgery
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

DTP*431 - ONSET OF CURRENT ILLNESS OR SYMPTOM 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. This date is the onset of acute symptoms for the current illness or condition.
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
DTP✱431✱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
431
Onset of Current Symptoms or Illness
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: Onset of Current Illness or Injury Date

DTP*454 - INITIAL TREATMENT 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✱454✱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
454
Initial Treatment
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: Initial Treatment Date

DTP*304 - LAST SEEN 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. This is the date that the patient was seen by the attending or supervising physician for the qualifying medical condition related to the services performed.
  3. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
DTP✱304✱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
304
Latest Visit or Consultation
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: Last Seen Date

DTP*453 - ACUTE MANIFESTATION 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✱453✱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
453
Acute Manifestation of a Chronic Condition
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: Acute Manifestation Date

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*484 - LAST MENSTRUAL PERIOD 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✱484✱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
484
Last Menstrual Period
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: Last Menstrual Period Date

DTP*455 - LAST X-RAY 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✱455✱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
455
Last X-Ray
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: Last X-Ray Date

DTP*471 - HEARING AND VISION PRESCRIPTION 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✱471✱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
471
Prescription
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: Prescription Date

DTP - DISABILITY DATES

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✱360✱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
314
Disability
Use code 314 when both disability start and end date are being reported.
360
Initial Disability Period Start
Use code 360 if patient is currently disabled and disability end date is unknown.
361
Initial Disability Period End
Use code 361 if patient is no longer disabled and the start date is unknown.
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
Use code D8 when DTP01 is 360 or 361.
RD8
Range of Dates Expressed in Format CCYYMMDD-CCYYMMDD
Use code RD8 when DTP01 is 314.
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: Disability Dates

DTP*297 - LAST WORKED 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✱297✱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
297
Initial Disability Period Last Day Worked
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: Last Worked Date

DTP*296 - AUTHORIZED RETURN TO WORK 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✱296✱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
296
Initial Disability Period Return To Work
This is the date the provider has authorized the patient to return to work.
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: Work Return Date

DTP*435 - ADMISSION 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✱435✱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
435
Admission
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: Related Hospitalization Admission Date

DTP*096 - DISCHARGE 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✱096✱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
096
Discharge
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: Related Hospitalization Discharge Date

DTP - ASSUMED AND RELINQUISHED CARE DATES

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:
2
Situational Rule:
Required when available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
  1. Assumed Care Date is the date care was assumed by another provider during post-operative care. Relinquished Care Date is the date the provider filing this claim ceased post-operative care. See Medicare guidelines for further explanation of these dates.

    Example: Surgeon "A" relinquished post-operative care to Physician "B" five days after surgery. When Surgeon "A" submits a claim, "A" will use code "091 - Report End" to indicate the day the surgeon relinquished care of this patient to Physician "B". When Physician "B" submits a claim, "B" will use code "090 - Report Start" to indicate the date they assumed care of this patient from Surgeon "A".
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
DTP✱090✱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
090
Report Start
Assumed Care Date - Use code "090" to indicate the date the provider filing this claim assumed care from another provider during post-operative care.
091
Report End
Relinquished Care Date - Use code "091" to indicate the date the provider filing this claim relinquished post-operative care to another provider.
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: Assumed or Relinquished Care Date

DTP*444 - PROPERTY AND CASUALTY DATE OF FIRST CONTACT

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. This is the date the patient first consulted the service provider for this condition. The date of first contact is the date the patient first consulted the provider by any means. It is not necessarily the Initial Treatment Date.
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
DTP✱444✱D8✱20121013~
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
444
First Visit or Consultation
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times

DTP*050 - REPRICER RECEIVED DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when 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✱050✱D8✱20121030~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
050
Received
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Repricer Received Date

PWK - CLAIM SUPPLEMENTAL INFORMATION

X12 Name:
Paperwork
X12 Purpose:
To identify the type or transmission or both of paperwork or supporting information
X12 Syntax:
P0506
If either PWK05 or PWK06 is present, then the other is required.
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:
If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
PWK✱OZ✱BM✱✱✱AC✱DMN0012~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
755
Report Type Code
M 1
ID
2
Code indicating the title or contents of a document, report or supporting item
INDUSTRY NAME: Attachment Report Type Code
CODE
DEFINITION
03
Report Justifying Treatment Beyond Utilization Guidelines
04
Drugs Administered
05
Treatment Diagnosis
06
Initial Assessment
07
Functional Goals
08
Plan of Treatment
09
Progress Report
10
Continued Treatment
11
Chemical Analysis
13
Certified Test Report
15
Justification for Admission
21
Recovery Plan
A3
Allergies/Sensitivities Document
A4
Autopsy Report
AM
Ambulance Certification
AS
Admission Summary
B2
Prescription
B3
Physician Order
B4
Referral Form
BR
Benchmark Testing Results
BS
Baseline
BT
Blanket Test Results
CB
Chiropractic Justification
CK
Consent Form(s)
CT
Certification
D2
Drug Profile Document
DA
Dental Models
DB
Durable Medical Equipment Prescription
DG
Diagnostic Report
DJ
Discharge Monitoring Report
DS
Discharge Summary
EB
Explanation of Benefits (Coordination of Benefits or Medicare Secondary Payor)
HC
Health Certificate
HR
Health Clinic Records
I5
Immunization Record
IR
State School Immunization Records
LA
Laboratory Results
M1
Medical Record Attachment
MT
Models
NN
Nursing Notes
OB
Operative Note
OC
Oxygen Content Averaging Report
OD
Orders and Treatments Document
OE
Objective Physical Examination (including vital signs) Document
OX
Oxygen Therapy Certification
OZ
Support Data for Claim
P4
Pathology Report
P5
Patient Medical History Document
PE
Parenteral or Enteral Certification
PN
Physical Therapy Notes
PO
Prosthetics or Orthotic Certification
PQ
Paramedical Results
PY
Physician's Report
PZ
Physical Therapy Certification
RB
Radiology Films
RR
Radiology Reports
RT
Report of Tests and Analysis Report
RX
Renewable Oxygen Content Averaging Report
SG
Symptoms Document
V5
Death Notification
XP
Photographs
Required
2
756
Report Transmission Code
O 1
ID
1/2
Code defining timing, transmission method or format by which reports are to be sent
INDUSTRY NAME: Attachment Transmission Code
CODE
DEFINITION
AA
Available on Request at Provider Site
This means that the additional information is not being sent with the claim at this time. Instead, it is available to the payer (or appropriate entity) at their request.
BM
By Mail
EL
Electronically Only
Indicates that the attachment is being transmitted in a separate X12 functional group.
EM
E-Mail
FT
File Transfer
Required when the actual attachment is maintained by an attachment warehouse or similar vendor.
FX
By Fax
Not Used
3
757
Report Copies Needed
O 1
N
1/2
Not Used
4
98
Entity Identifier Code
O 1
ID
2/3
Situational
5
66
Identification Code Qualifier
O 1
ID
1/2
Code designating the system/method of code structure used for Identification Code (67)
COMMENT: PWK05 and PWK06 may be used to identify the addressee by a code number.
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
CODE
DEFINITION
AC
Attachment Control Number
Situational
6
67
Identification Code
O 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Attachment Control Number
  1. PWK06 is used to identify the attached electronic documentation. The number in PWK06 is carried in the TRN of the electronic attachment.
  2. For the purpose of this implementation, the maximum field length is 50.
Not Used
7
352
Description
O 1
AN
1/80
Not Used
8
C002
Actions Indicated
O 1
Not Used
9
1525
Request Category Code
O 1
ID
1/2

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
01
Diagnosis Related Group (DRG)
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
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/50
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
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 to qualify amount
CODE
DEFINITION
F5
Patient Amount Paid
Required
2
782
Monetary Amount
M 1
R
1/18
Monetary amount
INDUSTRY NAME: Patient Amount Paid
Not Used
3
478
Credit/Debit Flag Code
O 1
ID
1

REF*4N - SERVICE AUTHORIZATION EXCEPTION CODE

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when 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✱4N✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
4N
Special Payment Reference Number
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Service Authorization Exception Code
Allowable values for this element are:
1 Immediate/Urgent Care
2 Services Rendered in a Retroactive Period
3 Emergency Care
4 Client has Temporary Medicaid
5 Request from County for Second Opinion to Determine
if Recipient Can Work
6 Request for Override Pending
7 Special Handling
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*EW - MAMMOGRAPHY CERTIFICATION 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✱EW✱T554~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
EW
Mammography Certification Number
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Mammography Certification Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*9F - REFERRAL NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when 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 qualifying the Reference Identification
CODE
DEFINITION
9F
Referral Number
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Referral Number
Not Used
3
352
Description
O 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 qualifying the Reference Identification
CODE
DEFINITION
G1
Prior Authorization Number
Required
2
127
Reference Identification
O 1
AN
1/50
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
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*F8 - PAYER CLAIM CONTROL NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when 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✱F8✱R555588~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
F8
Original Reference Number
Required
2
127
Reference Identification
O 1
AN
1/50
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
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*X4 - CLINICAL LABORATORY IMPROVEMENT AMENDMENT (CLIA) 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. If a CLIA number is indicated at the line level (Loop ID-2400) in addition to the claim level (Loop ID-2300), that would indicate an exception to the CLIA number at the claim level for that individual line.
  2. In cases where this claim contains both in-house and outsourced laboratory services, the CLIA Number for laboratory services performed by the Billing or Rendering Provider is reported in this loop. The CLIA number for laboratory services which were outsourced is reported in Loop ID-2400.
  3. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
REF✱X4✱12D4567890~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
X4
Clinical Laboratory Improvement Amendment Number
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Clinical Laboratory Improvement Amendment Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*9A - REPRICED CLAIM NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when 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✱9A✱RJ55555~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
9A
Repriced Claim Reference Number
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Repriced Claim Reference Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*9C - ADJUSTED REPRICED CLAIM NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when 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✱9C✱RP44444444~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
9C
Adjusted Repriced Claim Reference Number
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Adjusted Repriced Claim Reference Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*LX - INVESTIGATIONAL DEVICE EXEMPTION 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✱LX✱432907~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
LX
Qualified Products List
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Investigational Device Exemption Identifier
Not Used
3
352
Description
O 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 qualifying the Reference Identification
Number assigned by clearinghouse, van, etc.
CODE
DEFINITION
D9
Claim Number
Required
2
127
Reference Identification
O 1
AN
1/50
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
The value carried in this element is limited to a maximum of 20 positions.
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*EA - MEDICAL RECORD 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✱EA✱44444TH56~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
EA
Medical Record Identification Number
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Medical Record Number
Not Used
3
352
Description
O 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

NTE - CLAIM NOTE

X12 Name:
Note/Special Instruction
X12 Purpose:
To transmit information in a free-form format, if necessary, for comment or special instruction
X12 Comments:
The NTE segment permits free-form information/data which, under ANSI X12 standard implementations, is not machine processible. The use of the NTE segment should therefore be avoided, if at all possible, in an automated environment.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
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 the NTE segment in Loop ID-2300 applies to the entire claim unless overridden by information in the NTE segment in Loop ID-2400. Information is considered to be overridden when the value in NTE01 in Loop ID-2400 is the same as the value in NTE01 in Loop ID-2300.
  2. The developers of this implementation guide discourage using narrative information within the 837. Trading partners who use narrative information with claims are strongly encouraged to codify that information within the X12 environment.
  3. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
NTE✱ADD✱SURGERY WAS UNUSUALLY LONG BECAUSE [FILL IN REASON]~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
363
Note Reference Code
O 1
ID
3
Code identifying the functional area or purpose for which the note applies
CODE
DEFINITION
AAD
Nationality Details
CER
Certification Narrative
DCP
Goals, Rehabilitation Potential, or Discharge Plans
DGN
Diagnosis Description
TPO
Third Party Organization Notes
Required
2
352
Description
M 1
AN
1/80
A free-form description to clarify the related data elements and their content
INDUSTRY NAME: Claim Note Text

CR1*LB - AMBULANCE TRANSPORT INFORMATION

X12 Name:
Ambulance Certification
X12 Purpose:
To supply information related to the ambulance service rendered to a patient
X12 Syntax:
  1. P0102
    If either CR101 or CR102 is present, then the other is required.
  2. P0506
    If either CR105 or CR106 is present, then the other is required.
X12 Set Notes:
NOTE: The CR1 through CR5 and CRC certification segments appear on both the claim level and the service line level because certifications can be submitted for all services on a claim or for individual services. Certification information at the claim level applies to all service lines of the claim, unless overridden by certification information at the service line level.
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. The CR1 segment in Loop ID-2300 applies to the entire claim unless overridden by a CR1 segment at the service line level in Loop ID-2400 with the same value in CR101.
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
CR1✱LB✱140✱✱A✱DH✱12✱✱✱✱UNCONSCIOUS~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Situational
1
355
Unit or Basis for Measurement Code
O 1
ID
2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
SEGMENT SYNTAX: P0102
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
CODE
DEFINITION
LB
Pound
Situational
2
81
Weight
O 1
R
1/10
Numeric value of weight
SEMANTIC: CR102 is the weight of the patient at time of transport.
SEGMENT SYNTAX: P0102
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Weight
Not Used
3
1316
Ambulance Transport Code
O 1
ID
1
Required
4
1317
Ambulance Transport Reason Code
O 1
ID
1
Code indicating the reason for ambulance transport
CODE
DEFINITION
A
Patient was transported to nearest facility for care of symptoms, complaints, or both
Can be used to indicate that the patient was transferred to a residential facility.
B
Patient was transported for the benefit of a preferred physician
C
Patient was transported for the nearness of family members
D
Patient was transported for the care of a specialist or for availability of specialized equipment
E
Patient Transferred to Rehabilitation Facility
Required
5
355
Unit or Basis for Measurement Code
O 1
ID
2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
SEGMENT SYNTAX: P0506
CODE
DEFINITION
DH
Miles
Required
6
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: CR106 is the distance traveled during transport.
SEGMENT SYNTAX: P0506
INDUSTRY NAME: Transport Distance
0 (zero) is a valid value when ambulance services do not include a charge for mileage.
Not Used
7
166
Address Information
O 1
AN
1/55
Not Used
8
166
Address Information
O 1
AN
1/55
Situational
9
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
SEMANTIC: CR109 is the purpose for the round trip ambulance service.
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Round Trip Purpose Description
Situational
10
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
SEMANTIC: CR110 is the purpose for the usage of a stretcher during ambulance service.
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Stretcher Purpose Description

CR2 - SPINAL MANIPULATION SERVICE INFORMATION

X12 Name:
Chiropractic Certification
X12 Purpose:
To supply information related to the chiropractic service rendered to a patient
X12 Syntax:
  1. P0102
    If either CR201 or CR202 is present, then the other is required.
  2. C0403
    If CR204 is present, then CR203 is required.
  3. P0506
    If either CR205 or CR206 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:
CR2✱✱✱✱✱✱✱✱M~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Not Used
1
609
Count
O 1
N
1/9
Not Used
2
380
Quantity
O 1
R
1/15
Not Used
3
1367
Subluxation Level Code
O 1
ID
2/3
Not Used
4
1367
Subluxation Level Code
O 1
ID
2/3
Not Used
5
355
Unit or Basis for Measurement Code
O 1
ID
2
Not Used
6
380
Quantity
O 1
R
1/15
Not Used
7
380
Quantity
O 1
R
1/15
Required
8
1342
Nature of Condition Code
O 1
ID
1
Code indicating the nature of a patient's condition
INDUSTRY NAME: Patient Condition Code
CODE
DEFINITION
A
Acute Condition
C
Chronic Condition
D
Non-acute
E
Non-Life Threatening
F
Routine
G
Symptomatic
M
Acute Manifestation of a Chronic Condition
Not Used
9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
10
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
SEMANTIC: CR210 is a description of the patient's condition.
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Condition Description
Situational
11
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
SEMANTIC: CR211 is an additional description of the patient's condition.
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Condition Description
Not Used
12
1073
Yes/No Condition or Response Code
O 1
ID
1

CRC*07 - AMBULANCE CERTIFICATION

X12 Name:
Conditions Indicator
X12 Purpose:
To supply information on conditions
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:
  1. The CRC segment in Loop ID-2300 applies to the entire claim unless overridden by a CRC segment at the service line level in Loop ID-2400 with the same value in CRC01.
  2. Repeat this segment only when it is necessary to report additional unique values to those reported in CRC03 thru CRC07.
  3. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
CRC✱07✱Y✱01~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1136
Code Category
M 1
ID
2
Specifies the situation or category to which the code applies
SEMANTIC: CRC01 qualifies CRC03 through CRC07.
CODE
DEFINITION
07
Ambulance Certification
Required
2
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: CRC02 is a Certification Condition Code applies indicator. A "Y" value indicates the condition codes in CRC03 through CRC07 apply; an "N" value indicates the condition codes in CRC03 through CRC07 do not apply.
INDUSTRY NAME: Certification Condition Indicator
CODE
DEFINITION
N
No
Y
Yes
Required
3
1321
Condition Indicator
M 1
ID
2/3
Code indicating a condition
INDUSTRY NAME: Condition Code
CODE
DEFINITION
01
Patient was admitted to a hospital
04
Patient was moved by stretcher
05
Patient was unconscious or in shock
06
Patient was transported in an emergency situation
07
Patient had to be physically restrained
08
Patient had visible hemorrhaging
09
Ambulance service was medically necessary
12
Patient is confined to a bed or chair
Use code 12 to indicate patient was bedridden during transport.
Situational
4
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use the codes listed in CRC03.
CODE
DEFINITION
01
Patient was admitted to a hospital
04
Patient was moved by stretcher
05
Patient was unconscious or in shock
06
Patient was transported in an emergency situation
07
Patient had to be physically restrained
08
Patient had visible hemorrhaging
09
Ambulance service was medically necessary
12
Patient is confined to a bed or chair
Use code 12 to indicate patient was bedridden during transport.
Situational
5
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use the codes listed in CRC03.
CODE
DEFINITION
01
Patient was admitted to a hospital
04
Patient was moved by stretcher
05
Patient was unconscious or in shock
06
Patient was transported in an emergency situation
07
Patient had to be physically restrained
08
Patient had visible hemorrhaging
09
Ambulance service was medically necessary
12
Patient is confined to a bed or chair
Use code 12 to indicate patient was bedridden during transport.
Situational
6
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use the codes listed in CRC03.
CODE
DEFINITION
01
Patient was admitted to a hospital
04
Patient was moved by stretcher
05
Patient was unconscious or in shock
06
Patient was transported in an emergency situation
07
Patient had to be physically restrained
08
Patient had visible hemorrhaging
09
Ambulance service was medically necessary
12
Patient is confined to a bed or chair
Use code 12 to indicate patient was bedridden during transport.
Situational
7
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use the codes listed in CRC03.
CODE
DEFINITION
01
Patient was admitted to a hospital
04
Patient was moved by stretcher
05
Patient was unconscious or in shock
06
Patient was transported in an emergency situation
07
Patient had to be physically restrained
08
Patient had visible hemorrhaging
09
Ambulance service was medically necessary
12
Patient is confined to a bed or chair
Use code 12 to indicate patient was bedridden during transport.

CRC - PATIENT CONDITION INFORMATION: VISION

X12 Name:
Conditions Indicator
X12 Purpose:
To supply information on conditions
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:
CRC✱E1✱Y✱L1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1136
Code Category
M 1
ID
2
Specifies the situation or category to which the code applies
SEMANTIC: CRC01 qualifies CRC03 through CRC07.
CODE
DEFINITION
E1
Spectacle Lenses
E2
Contact Lenses
E3
Spectacle Frames
Required
2
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: CRC02 is a Certification Condition Code applies indicator. A "Y" value indicates the condition codes in CRC03 through CRC07 apply; an "N" value indicates the condition codes in CRC03 through CRC07 do not apply.
INDUSTRY NAME: Certification Condition Indicator
CODE
DEFINITION
N
No
Y
Yes
Required
3
1321
Condition Indicator
M 1
ID
2/3
Code indicating a condition
INDUSTRY NAME: Condition Code
CODE
DEFINITION
L1
General Standard of 20 Degree or .5 Diopter Sphere or Cylinder Change Met
L2
Replacement Due to Loss or Theft
L3
Replacement Due to Breakage or Damage
L4
Replacement Due to Patient Preference
L5
Replacement Due to Medical Reason
Situational
4
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use the codes listed in CRC03.
CODE
DEFINITION
L1
General Standard of 20 Degree or .5 Diopter Sphere or Cylinder Change Met
L2
Replacement Due to Loss or Theft
L3
Replacement Due to Breakage or Damage
L4
Replacement Due to Patient Preference
L5
Replacement Due to Medical Reason
Situational
5
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use the codes listed in CRC03.
CODE
DEFINITION
L1
General Standard of 20 Degree or .5 Diopter Sphere or Cylinder Change Met
L2
Replacement Due to Loss or Theft
L3
Replacement Due to Breakage or Damage
L4
Replacement Due to Patient Preference
L5
Replacement Due to Medical Reason
Situational
6
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use the codes listed in CRC03.
CODE
DEFINITION
L1
General Standard of 20 Degree or .5 Diopter Sphere or Cylinder Change Met
L2
Replacement Due to Loss or Theft
L3
Replacement Due to Breakage or Damage
L4
Replacement Due to Patient Preference
L5
Replacement Due to Medical Reason
Situational
7
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use the codes listed in CRC03.
CODE
DEFINITION
L1
General Standard of 20 Degree or .5 Diopter Sphere or Cylinder Change Met
L2
Replacement Due to Loss or Theft
L3
Replacement Due to Breakage or Damage
L4
Replacement Due to Patient Preference
L5
Replacement Due to Medical Reason

CRC*75 - HOMEBOUND INDICATOR

X12 Name:
Conditions Indicator
X12 Purpose:
To supply information on conditions
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:
CRC✱75✱Y✱IH~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1136
Code Category
M 1
ID
2
Specifies the situation or category to which the code applies
SEMANTIC: CRC01 qualifies CRC03 through CRC07.
INDUSTRY NAME: Condition Code
CODE
DEFINITION
75
Functional Limitations
Required
2
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: CRC02 is a Certification Condition Code applies indicator. A "Y" value indicates the condition codes in CRC03 through CRC07 apply; an "N" value indicates the condition codes in CRC03 through CRC07 do not apply.
INDUSTRY NAME: Certification Condition Indicator
CODE
DEFINITION
Y
Yes
Required
3
1321
Condition Indicator
M 1
ID
2/3
Code indicating a condition
INDUSTRY NAME: Homebound Indicator
CODE
DEFINITION
IH
Independent at Home
Not Used
4
1321
Condition Indicator
O 1
ID
2/3
Not Used
5
1321
Condition Indicator
O 1
ID
2/3
Not Used
6
1321
Condition Indicator
O 1
ID
2/3
Not Used
7
1321
Condition Indicator
O 1
ID
2/3

CRC*ZZ - EPSDT REFERRAL

X12 Name:
Conditions Indicator
X12 Purpose:
To supply information on conditions
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:
CRC✱ZZ✱Y✱ST~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1136
Code Category
M 1
ID
2
Specifies the situation or category to which the code applies
SEMANTIC: CRC01 qualifies CRC03 through CRC07.
INDUSTRY NAME: Code Qualifier
CODE
DEFINITION
ZZ
Mutually Defined
EPSDT Screening referral information.
Required
2
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: CRC02 is a Certification Condition Code applies indicator. A "Y" value indicates the condition codes in CRC03 through CRC07 apply; an "N" value indicates the condition codes in CRC03 through CRC07 do not apply.
INDUSTRY NAME: Certification Condition Code Applies Indicator
The response answers the question: Was an EPSDT referral given to the patient?
CODE
DEFINITION
N
No
If no, then choose "NU" in CRC03 indicating no referral given.
Y
Yes
Required
3
1321
Condition Indicator
M 1
ID
2/3
Code indicating a condition
The codes for CRC03 also can be used for CRC04 through CRC05.
CODE
DEFINITION
AV
Available - Not Used
Patient refused referral.
NU
Not Used
This condition indicator must be used when the submitter answers "N" in CRC02.
S2
Under Treatment
Patient is currently under treatment for referred diagnostic or corrective health problem.
ST
New Services Requested
Patient is referred to another provider for diagnostic or corrective treatment for at least one health problem identified during an initial or periodic screening service (not including dental referrals).
OR
Patient is scheduled for another appointment with screening provider for diagnostic or corrective treatment for at least one health problem identified during an initial or periodic screening service (not including dental referrals).
Situational
4
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
Use the codes listed in CRC03.
CODE
DEFINITION
AV
Available - Not Used
Patient refused referral.
NU
Not Used
This condition indicator must be used when the submitter answers "N" in CRC02.
S2
Under Treatment
Patient is currently under treatment for referred diagnostic or corrective health problem.
ST
New Services Requested
Patient is referred to another provider for diagnostic or corrective treatment for at least one health problem identified during an initial or periodic screening service (not including dental referrals).
OR
Patient is scheduled for another appointment with screening provider for diagnostic or corrective treatment for at least one health problem identified during an initial or periodic screening service (not including dental referrals).
Situational
5
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
Use the codes listed in CRC03.
CODE
DEFINITION
AV
Available - Not Used
Patient refused referral.
NU
Not Used
This condition indicator must be used when the submitter answers "N" in CRC02.
S2
Under Treatment
Patient is currently under treatment for referred diagnostic or corrective health problem.
ST
New Services Requested
Patient is referred to another provider for diagnostic or corrective treatment for at least one health problem identified during an initial or periodic screening service (not including dental referrals).
OR
Patient is scheduled for another appointment with screening provider for diagnostic or corrective treatment for at least one health problem identified during an initial or periodic screening service (not including dental referrals).
Not Used
6
1321
Condition Indicator
O 1
ID
2/3
Not Used
7
1321
Condition Indicator
O 1
ID
2/3

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:
Required
Segment Repeat:
1
TR3 Notes:
Do not transmit the decimal point for ICD codes. The decimal point is implied.
TR3 Example:
HI✱BK:8901✱BF:87200✱BF:5559~
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (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
INDUSTRY NAME: Diagnosis Type Code
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)
BK
International Classification of Diseases Clinical Modification (ICD-9-CM) Principal Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
Required
1-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Diagnosis Code
Not Used
1-3
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
1-4
1251
Date Time Period
O 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
O 1
AN
1/30
Not Used
1-9
1073
Yes/No Condition or Response Code
O 1
ID
1
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (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
INDUSTRY NAME: Diagnosis Type Code
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)
BF
International Classification of Diseases Clinical Modification (ICD-9-CM) Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
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
O 1
ID
2/3
Not Used
2-4
1251
Date Time Period
O 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
O 1
AN
1/30
Not Used
2-9
1073
Yes/No Condition or Response Code
O 1
ID
1
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (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
INDUSTRY NAME: Diagnosis Type Code
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)
BF
International Classification of Diseases Clinical Modification (ICD-9-CM) Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
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
O 1
ID
2/3
Not Used
3-4
1251
Date Time Period
O 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
O 1
AN
1/30
Not Used
3-9
1073
Yes/No Condition or Response Code
O 1
ID
1
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (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
INDUSTRY NAME: Diagnosis Type Code
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)
BF
International Classification of Diseases Clinical Modification (ICD-9-CM) Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
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
O 1
ID
2/3
Not Used
4-4
1251
Date Time Period
O 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
O 1
AN
1/30
Not Used
4-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
5
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (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
5-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
INDUSTRY NAME: Diagnosis Type Code
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)
BF
International Classification of Diseases Clinical Modification (ICD-9-CM) Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
Required
5-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
5-3
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
5-4
1251
Date Time Period
O 1
AN
1/35
Not Used
5-5
782
Monetary Amount
O 1
R
1/18
Not Used
5-6
380
Quantity
O 1
R
1/15
Not Used
5-7
799
Version Identifier
O 1
AN
1/30
Not Used
5-8
1271
Industry Code
O 1
AN
1/30
Not Used
5-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
6
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (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
6-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
INDUSTRY NAME: Diagnosis Type Code
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)
BF
International Classification of Diseases Clinical Modification (ICD-9-CM) Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
Required
6-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
6-3
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
6-4
1251
Date Time Period
O 1
AN
1/35
Not Used
6-5
782
Monetary Amount
O 1
R
1/18
Not Used
6-6
380
Quantity
O 1
R
1/15
Not Used
6-7
799
Version Identifier
O 1
AN
1/30
Not Used
6-8
1271
Industry Code
O 1
AN
1/30
Not Used
6-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
7
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (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
7-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
INDUSTRY NAME: Diagnosis Type Code
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)
BF
International Classification of Diseases Clinical Modification (ICD-9-CM) Diagnosis
ICD-9 Codes
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
Required
7-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
7-3
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
7-4
1251
Date Time Period
O 1
AN
1/35
Not Used
7-5
782
Monetary Amount
O 1
R
1/18
Not Used
7-6
380
Quantity
O 1
R
1/15
Not Used
7-7
799
Version Identifier
O 1
AN
1/30
Not Used
7-8
1271
Industry Code
O 1
AN
1/30
Not Used
7-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
8
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (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
8-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
INDUSTRY NAME: Diagnosis Type Code
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)
BF
International Classification of Diseases Clinical Modification (ICD-9-CM) Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
Required
8-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
8-3
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
8-4
1251
Date Time Period
O 1
AN
1/35
Not Used
8-5
782
Monetary Amount
O 1
R
1/18
Not Used
8-6
380
Quantity
O 1
R
1/15
Not Used
8-7
799
Version Identifier
O 1
AN
1/30
Not Used
8-8
1271
Industry Code
O 1
AN
1/30
Not Used
8-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
9
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (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
9-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
INDUSTRY NAME: Diagnosis Type Code
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)
BF
International Classification of Diseases Clinical Modification (ICD-9-CM) Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
Required
9-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
9-3
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
9-4
1251
Date Time Period
O 1
AN
1/35
Not Used
9-5
782
Monetary Amount
O 1
R
1/18
Not Used
9-6
380
Quantity
O 1
R
1/15
Not Used
9-7
799
Version Identifier
O 1
AN
1/30
Not Used
9-8
1271
Industry Code
O 1
AN
1/30
Not Used
9-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
10
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (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
10-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
INDUSTRY NAME: Diagnosis Type Code
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)
BF
International Classification of Diseases Clinical Modification (ICD-9-CM) Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
Required
10-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
10-3
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
10-4
1251
Date Time Period
O 1
AN
1/35
Not Used
10-5
782
Monetary Amount
O 1
R
1/18
Not Used
10-6
380
Quantity
O 1
R
1/15
Not Used
10-7
799
Version Identifier
O 1
AN
1/30
Not Used
10-8
1271
Industry Code
O 1
AN
1/30
Not Used
10-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
11
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (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
11-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
INDUSTRY NAME: Diagnosis Type Code
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)
BF
International Classification of Diseases Clinical Modification (ICD-9-CM) Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
Required
11-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
11-3
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
11-4
1251
Date Time Period
O 1
AN
1/35
Not Used
11-5
782
Monetary Amount
O 1
R
1/18
Not Used
11-6
380
Quantity
O 1
R
1/15
Not Used
11-7
799
Version Identifier
O 1
AN
1/30
Not Used
11-8
1271
Industry Code
O 1
AN
1/30
Not Used
11-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
12
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (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
12-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
INDUSTRY NAME: Diagnosis Type Code
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)
BF
International Classification of Diseases Clinical Modification (ICD-9-CM) Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
Required
12-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
12-3
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
12-4
1251
Date Time Period
O 1
AN
1/35
Not Used
12-5
782
Monetary Amount
O 1
R
1/18
Not Used
12-6
380
Quantity
O 1
R
1/15
Not Used
12-7
799
Version Identifier
O 1
AN
1/30
Not Used
12-8
1271
Industry Code
O 1
AN
1/30
Not Used
12-9
1073
Yes/No Condition or Response Code
O 1
ID
1

HI - ANESTHESIA RELATED PROCEDURE

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:
If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
HI✱BP:33414~
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (Diagnosis Code) and range of diagnosis codes were NOT given in C022-08.
Required
1-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
CODE
DEFINITION
BP
Health Care Financing Administration Common Procedural Coding System Principal Procedure
CODE SOURCE: 130: Healthcare Common Procedure Coding System
Required
1-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Anesthesia Related Surgical Procedure
Not Used
1-3
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
1-4
1251
Date Time Period
O 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
O 1
AN
1/30
Not Used
1-9
1073
Yes/No Condition or Response Code
O 1
ID
1
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (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
BO
Health Care Financing Administration Common Procedural Coding System
CODE SOURCE: 130: Healthcare Common Procedure Coding System
Required
2-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
Not Used
2-3
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
2-4
1251
Date Time Period
O 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
O 1
AN
1/30
Not Used
2-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Not Used
3
C022
Health Care Code Information
O 1
Not Used
4
C022
Health Care Code Information
O 1
Not Used
5
C022
Health Care Code Information
O 1
Not Used
6
C022
Health Care Code Information
O 1
Not Used
7
C022
Health Care Code Information
O 1
Not Used
8
C022
Health Care Code Information
O 1
Not Used
9
C022
Health Care Code Information
O 1
Not Used
10
C022
Health Care Code Information
O 1
Not Used
11
C022
Health Care Code Information
O 1
Not Used
12
C022
Health Care Code Information
O 1

HI - CONDITION INFORMATION

X12 Name:
Health Care Information Codes
X12 Purpose:
To supply information related to the delivery of health care
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
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:
HI✱BG:17✱BG:67~
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (Diagnosis Code) and range of diagnosis codes were NOT given in C022-08.
Required
1-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
CODE
DEFINITION
BG
Condition
CODE SOURCE: 641: Condition Code List
Required
1-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Condition Code
Not Used
1-3
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
1-4
1251
Date Time Period
O 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
O 1
AN
1/30
Not Used
1-9
1073
Yes/No Condition or Response Code
O 1
ID
1
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (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
BG
Condition
CODE SOURCE: 641: Condition Code List
Required
2-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Condition Code
Not Used
2-3
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
2-4
1251
Date Time Period
O 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
O 1
AN
1/30
Not Used
2-9
1073
Yes/No Condition or Response Code
O 1
ID
1
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (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
CODE
DEFINITION
BG
Condition
CODE SOURCE: 641: Condition Code List
Required
3-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Condition Code
Not Used
3-3
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
3-4
1251
Date Time Period
O 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
O 1
AN
1/30
Not Used
3-9
1073
Yes/No Condition or Response Code
O 1
ID
1
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (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
CODE
DEFINITION
BG
Condition
CODE SOURCE: 641: Condition Code List
Required
4-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Condition Code
Not Used
4-3
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
4-4
1251
Date Time Period
O 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
O 1
AN
1/30
Not Used
4-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
5
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (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
5-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
CODE
DEFINITION
BG
Condition
CODE SOURCE: 641: Condition Code List
Required
5-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Condition Code
Not Used
5-3
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
5-4
1251
Date Time Period
O 1
AN
1/35
Not Used
5-5
782
Monetary Amount
O 1
R
1/18
Not Used
5-6
380
Quantity
O 1
R
1/15
Not Used
5-7
799
Version Identifier
O 1
AN
1/30
Not Used
5-8
1271
Industry Code
O 1
AN
1/30
Not Used
5-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
6
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (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
6-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
CODE
DEFINITION
BG
Condition
CODE SOURCE: 641: Condition Code List
Required
6-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Condition Code
Not Used
6-3
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
6-4
1251
Date Time Period
O 1
AN
1/35
Not Used
6-5
782
Monetary Amount
O 1
R
1/18
Not Used
6-6
380
Quantity
O 1
R
1/15
Not Used
6-7
799
Version Identifier
O 1
AN
1/30
Not Used
6-8
1271
Industry Code
O 1
AN
1/30
Not Used
6-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
7
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (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
7-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
CODE
DEFINITION
BG
Condition
CODE SOURCE: 641: Condition Code List
Required
7-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Condition Code
Not Used
7-3
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
7-4
1251
Date Time Period
O 1
AN
1/35
Not Used
7-5
782
Monetary Amount
O 1
R
1/18
Not Used
7-6
380
Quantity
O 1
R
1/15
Not Used
7-7
799
Version Identifier
O 1
AN
1/30
Not Used
7-8
1271
Industry Code
O 1
AN
1/30
Not Used
7-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
8
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (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
8-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
CODE
DEFINITION
BG
Condition
CODE SOURCE: 641: Condition Code List
Required
8-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Condition Code
Not Used
8-3
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
8-4
1251
Date Time Period
O 1
AN
1/35
Not Used
8-5
782
Monetary Amount
O 1
R
1/18
Not Used
8-6
380
Quantity
O 1
R
1/15
Not Used
8-7
799
Version Identifier
O 1
AN
1/30
Not Used
8-8
1271
Industry Code
O 1
AN
1/30
Not Used
8-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
9
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (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
9-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
CODE
DEFINITION
BG
Condition
CODE SOURCE: 641: Condition Code List
Required
9-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Condition Code
Not Used
9-3
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
9-4
1251
Date Time Period
O 1
AN
1/35
Not Used
9-5
782
Monetary Amount
O 1
R
1/18
Not Used
9-6
380
Quantity
O 1
R
1/15
Not Used
9-7
799
Version Identifier
O 1
AN
1/30
Not Used
9-8
1271
Industry Code
O 1
AN
1/30
Not Used
9-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
10
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (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
10-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
CODE
DEFINITION
BG
Condition
CODE SOURCE: 641: Condition Code List
Required
10-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Condition Code
Not Used
10-3
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
10-4
1251
Date Time Period
O 1
AN
1/35
Not Used
10-5
782
Monetary Amount
O 1
R
1/18
Not Used
10-6
380
Quantity
O 1
R
1/15
Not Used
10-7
799
Version Identifier
O 1
AN
1/30
Not Used
10-8
1271
Industry Code
O 1
AN
1/30
Not Used
10-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
11
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (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
11-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
CODE
DEFINITION
BG
Condition
CODE SOURCE: 641: Condition Code List
Required
11-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Condition Code
Not Used
11-3
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
11-4
1251
Date Time Period
O 1
AN
1/35
Not Used
11-5
782
Monetary Amount
O 1
R
1/18
Not Used
11-6
380
Quantity
O 1
R
1/15
Not Used
11-7
799
Version Identifier
O 1
AN
1/30
Not Used
11-8
1271
Industry Code
O 1
AN
1/30
Not Used
11-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
12
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 and C022-08.
  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 used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (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
12-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
CODE
DEFINITION
BG
Condition
CODE SOURCE: 641: Condition Code List
Required
12-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Condition Code
Not Used
12-3
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
12-4
1251
Date Time Period
O 1
AN
1/35
Not Used
12-5
782
Monetary Amount
O 1
R
1/18
Not Used
12-6
380
Quantity
O 1
R
1/15
Not Used
12-7
799
Version Identifier
O 1
AN
1/30
Not Used
12-8
1271
Industry Code
O 1
AN
1/30
Not Used
12-9
1073
Yes/No Condition or Response Code
O 1
ID
1

HCP - CLAIM PRICING/REPRICING INFORMATION

X12 Name:
Health Care Pricing
X12 Purpose:
To specify pricing or repricing information about a health care claim or line item
X12 Syntax:
  1. R0113
    At least one of HCP01 or HCP13 is required.
  2. P0910
    If either HCP09 or HCP10 is present, then the other is required.
  3. P1112
    If either HCP11 or HCP12 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when 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:
HCP✱03✱100✱10✱RPO12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1473
Pricing Methodology
O 1
ID
2
Code specifying pricing methodology at which the claim or line item has been priced or repriced
SEGMENT SYNTAX: R0113
Specific code use is determined by Trading Partner Agreement due to the variances in contracting policies in the industry.
CODE
DEFINITION
00
Zero Pricing (Not Covered Under Contract)
01
Priced as Billed at 100%
02
Priced at the Standard Fee Schedule
03
Priced at a Contractual Percentage
04
Bundled Pricing
05
Peer Review Pricing
06
Per Diem Pricing
07
Flat Rate Pricing
08
Combination Pricing
09
Maternity Pricing
10
Other Pricing
11
Lower of Cost
12
Ratio of Cost
13
Cost Reimbursed
14
Adjustment Pricing
Required
2
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: HCP02 is the allowed amount.
INDUSTRY NAME: Repriced Allowed Amount
Situational
3
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: HCP03 is the savings amount.
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Repriced Saving Amount
Situational
4
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: HCP04 is the repricing organization identification number.
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Repricing Organization Identifier
Situational
5
118
Rate
O 1
R
1/9
Rate expressed in the standard monetary denomination for the currency specified
SEMANTIC: HCP05 is the pricing rate associated with per diem or flat rate repricing.
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Repricing Per Diem or Flat Rate Amount
Situational
6
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: HCP06 is the approved DRG code.
COMMENT: HCP06, HCP07, HCP08, HCP10, and HCP12 are fields that will contain different values from the original submitted values.
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Repriced Approved Ambulatory Patient Group (APG) Code
Situational
7
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: HCP07 is the approved DRG amount.
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Repriced Approved Ambulatory Patient Group (APG) Amount
Not Used
8
234
Product/Service ID
O 1
AN
1/48
Not Used
9
235
Product/Service ID Qualifier
O 1
ID
2
Not Used
10
234
Product/Service ID
O 1
AN
1/48
Not Used
11
355
Unit or Basis for Measurement Code
O 1
ID
2
Not Used
12
380
Quantity
O 1
R
1/15
Situational
13
901
Reject Reason Code
O 1
ID
2
Code assigned by issuer to identify reason for rejection
SEMANTIC: HCP13 is the rejection message returned from the third party organization.
SEGMENT SYNTAX: R0113
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
CODE
DEFINITION
T1
Cannot Identify Provider as TPO (Third Party Organization) Participant
T2
Cannot Identify Payer as TPO (Third Party Organization) Participant
T3
Cannot Identify Insured as TPO (Third Party Organization) Participant
T4
Payer Name or Identifier Missing
T5
Certification Information Missing
T6
Claim does not contain enough information for re-pricing
Situational
14
1526
Policy Compliance Code
O 1
ID
1/2
Code specifying policy compliance
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Procedure Followed (Compliance)
2
Not Followed - Call Not Made (Non-Compliance Call Not Made)
3
Not Medically Necessary (Non-Compliance Non-Medically Necessary)
4
Not Followed Other (Non-Compliance Other)
5
Emergency Admit to Non-Network Hospital
Situational
15
1527
Exception Code
O 1
ID
1/2
Code specifying the exception reason for consideration of out-of-network health care services
SEMANTIC: HCP15 is the exception reason generated by a third party organization.
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Non-Network Professional Provider in Network Hospital
2
Emergency Care
3
Services or Specialist not in Network
4
Out-of-Service Area
5
State Mandates
6
Other

NM1 - REFERRING PROVIDER NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Loop 2310 contains information about the rendering, referring, or attending provider.
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. When reporting the provider who ordered services such as diagnostic and lab, use Loop ID-2310A at the claim level. For ordered services such as Durable Medical Equipment, use Loop ID-2420E at the line level.
  3. 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.
  4. 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 qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Required
3
1035
Name Last or Organization Name
O 1
AN
1/60
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
O 1
ID
1/2
Code designating 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
Centers for Medicare and Medicaid Services National Provider Identifier
CODE SOURCE: 537: Centers for Medicare & Medicaid Services National Provider Identifier
Situational
9
67
Identification Code
O 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
O 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/60

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 qualifying 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-2330B where 2320 SBR06 equals 6. This is to be used by all payers including: Medicare, Medicaid, Blue Cross, etc.
Required
2
127
Reference Identification
O 1
AN
1/50
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
Not Used
3
352
Description
O 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 rendering, referring, or attending provider.
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 qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
2
Non-Person Entity
Required
3
1035
Name Last or Organization Name
O 1
AN
1/60
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
O 1
ID
1/2
Code designating 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
Centers for Medicare and Medicaid Services National Provider Identifier
CODE SOURCE: 537: Centers for Medicare & Medicaid Services National Provider Identifier
Situational
9
67
Identification Code
O 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
O 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/60

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
O 1
ID
2/3
Code qualifying 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
O 1
AN
1/50
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
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 qualifying 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-2330B 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
O 1
AN
1/50
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
Not Used
3
352
Description
O 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 rendering, referring, or attending provider.
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✱ABC CLINIC✱✱✱✱✱XX✱1234567891~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
77
Service Location
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
2
Non-Person Entity
Required
3
1035
Name Last or Organization Name
O 1
AN
1/60
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
O 1
ID
1/2
Code designating 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
Centers for Medicare and Medicaid Services National Provider Identifier
CODE SOURCE: 537: Centers for Medicare & Medicaid Services National Provider Identifier
Situational
9
67
Identification Code
O 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
O 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/60

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. C0605
    If N406 is present, then N405 is required.
  3. 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
O 1
ID
2
Code (Standard State/Province) as defined by appropriate government agency
COMMENT: N402 is required only if city name (N401) is in the U.S. or Canada.
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
O 1
ID
3/15
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
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
O 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
O 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
O 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

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 qualifying 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-2330B 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
O 1
AN
1/50
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
Not Used
3
352
Description
O 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 rendering, referring, or attending provider.
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✱DOE✱JOHN✱B✱✱✱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
DQ
Supervising Physician
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Required
3
1035
Name Last or Organization Name
O 1
AN
1/60
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
O 1
ID
1/2
Code designating 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
Centers for Medicare and Medicaid Services National Provider Identifier
CODE SOURCE: 537: Centers for Medicare & Medicaid Services National Provider Identifier
Situational
9
67
Identification Code
O 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
O 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/60

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✱G2✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying 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-2330B 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
O 1
AN
1/50
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
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

NM1*PW - AMBULANCE PICK-UP LOCATION

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Loop 2310 contains information about the rendering, referring, or attending provider.
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✱PW✱2~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
PW
Pickup Address
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
2
Non-Person Entity
Not Used
3
1035
Name Last or Organization Name
O 1
AN
1/60
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
O 1
ID
1/2
Not Used
9
67
Identification Code
O 1
AN
2/80
Not Used
10
706
Entity Relationship Code
O 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/60

N3 - AMBULANCE PICK-UP LOCATION ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
  1. If the ambulance pickup location is in an area where there are no street addresses, enter a description of where the service was rendered (for example, "crossroad of State Road 34 and 45" or "Exit near Mile marker 265 on Interstate 80".)
  2. 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: Ambulance Pick-up 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: Ambulance Pick-up Address Line

N4 - AMBULANCE PICK-UP 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. C0605
    If N406 is present, then N405 is required.
  3. C0704
    If N407 is present, then N404 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:
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: Ambulance Pick-up City Name
Situational
2
156
State or Province Code
O 1
ID
2
Code (Standard State/Province) as defined by appropriate government agency
COMMENT: N402 is required only if city name (N401) is in the U.S. or Canada.
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: Ambulance Pick-up State or Province Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
O 1
ID
3/15
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
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: Ambulance Pick-up Postal Zone or ZIP Code
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
O 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
O 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
O 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

NM1*45 - AMBULANCE DROP-OFF LOCATION

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Loop 2310 contains information about the rendering, referring, or attending provider.
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:
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.
TR3 Example:
NM1✱45✱2✱ST JOES HOSPITAL~
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
45
Drop-off Location
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
2
Non-Person Entity
Situational
3
1035
Name Last or Organization Name
O 1
AN
1/60
Individual last name or organizational name
SEGMENT SYNTAX: C1203
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Ambulance Drop-off Location
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
O 1
ID
1/2
Not Used
9
67
Identification Code
O 1
AN
2/80
Not Used
10
706
Entity Relationship Code
O 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/60

N3 - AMBULANCE DROP-OFF LOCATION ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 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: Ambulance Drop-off 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: Ambulance Drop-off Address Line

N4 - AMBULANCE DROP-OFF 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. C0605
    If N406 is present, then N405 is required.
  3. C0704
    If N407 is present, then N404 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
N4✱KANSAS CITY✱MO✱64108~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
INDUSTRY NAME: Ambulance Drop-off City Name
Situational
2
156
State or Province Code
O 1
ID
2
Code (Standard State/Province) as defined by appropriate government agency
COMMENT: N402 is required only if city name (N401) is in the U.S. or Canada.
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: Ambulance Drop-off State or Province Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
O 1
ID
3/15
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
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: Ambulance Drop-off Postal Zone or ZIP Code
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
O 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: Ambulance Drop-off 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
O 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
O 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: Ambulance Drop-off Country Subdivision Code
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds

SBR - OTHER SUBSCRIBER INFORMATION

X12 Name:
Subscriber Information
X12 Purpose:
To record information specific to the primary insured and the insurance carrier for that insured
X12 Set Notes:
NOTE: Loop 2320 contains insurance information about: paying and other Insurance Carriers for that Subscriber, Subscriber of the Other Insurance Carriers, School or Employer Information for that Subscriber.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
  1. All information contained in Loop ID-2320 applies only to the payer identified in Loop ID-2330B of this iteration of Loop ID-2320. It is specific only to that payer. If information for an additional payer is necessary, repeat Loop ID-2320 with its respective 2330 Loops.
  2. Loop ID 2320 and its suboordinate 2330 and 2430 loops convey information demonstrating how this claim was adjudicated by both the submitting payer and other payers who have previously adjudicated the claim.

    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.

    SBR06 identifies to the receiver whether the respective iteration of Loop ID 2320 was adjudicated by the submitting plan or an Other Payer.

    When SBR06 = 1, the payer and adjudication information related to this iteration of Loop ID 2320 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 SBR06 = 6, the payer and adjudication information related to this iteration of Loop ID 2320 and 2430 represents the adjudication results of the submitting payer.
TR3 Example:
SBR✱P✱18✱G00786✱✱✱6✱✱✱CI~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1138
Payer Responsibility Sequence Number Code
M 1
ID
1
Code identifying the insurance carrier's level of responsibility for a payment of a claim
When this field is populated based upon the adjudication of the submitting payer, the selection of this code value is similar to how CLP02 in the 835 transaction is performed.
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/50
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 SBR06 = 6; and the submitting payer has assigned a group identifier to this benefit plan.ORRequired when SBR06 = 1; and 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
This is not the number uniquely identifying the subscriber. The unique subscriber number is submitted in Loop 2330A-NM109 for this iteration of Loop ID-2320.
Situational
4
93
Name
O 1
AN
1/60
Free-form name
SEMANTIC: SBR04 is plan name.
SITUATIONAL RULE: Required when SBR06 = 6; and the submitting payer has assigned a group name to this benefit plan; and SBR03 is not used.ORRequired when SBR06 = 1; and this information was provided on the original claim from the provider.If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Insured Group 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
Use this code when the payer and adjudication information related to this iteration of Loop ID 2320 and 2430 was submitted on the original claim from the provider.
6
No Coordination of Benefits
Use this code when the payer and adjudication information related to this iteration of Loop ID 2320 and 2430 represents the adjudication of the payer submitting this transaction.
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
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
OF
Other Federal Program
Use code OF when submitting Medicare Part D claims.
TV
Title V
VA
Veterans Affairs Plan
WC
Workers' Compensation Health Claim
ZZ
Mutually Defined
Use Code ZZ when Type of Insurance is not known.

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. 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 payer identified is not the submitting payer, codes and associated amounts must be reported as submitted by the provider.

    When the payer identified is the submitting payer, 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
1033
Claim Adjustment Group Code
M 1
ID
1/2
Code identifying the general category of payment adjustment
CODE
DEFINITION
CO
Contractual Obligations
OA
Other adjustments
PI
Payor Initiated Reductions
PR
Patient Responsibility
Required
2
1034
Claim Adjustment Reason Code
M 1
ID
1/5
Code identifying the detailed reason the adjustment was made
INDUSTRY NAME: Adjustment Reason Code
See CODE SOURCE 139: Claim 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
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
O 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
O 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
Situational
7
380
Quantity
O 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
O 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
O 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
Situational
10
380
Quantity
O 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
O 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
O 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
Situational
13
380
Quantity
O 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
O 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
O 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
Situational
16
380
Quantity
O 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
O 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
O 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
Situational
19
380
Quantity
O 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 to qualify amount
CODE
DEFINITION
D
Payor Amount Paid
Required
2
782
Monetary Amount
M 1
R
1/18
Monetary amount
INDUSTRY NAME: Payer Paid Amount
It is acceptable to show "0" as the amount paid.
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:
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. In the judgment of the provider, this is the remaining amount to be paid after adjudication by the Other Payer identified in Loop ID-2330B of this iteration of Loop ID-2320.
  2. 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 to qualify amount
CODE
DEFINITION
EAF
Amount Owed
Required
2
782
Monetary Amount
M 1
R
1/18
Monetary amount
INDUSTRY NAME: Remaining Patient Liability
Not Used
3
478
Credit/Debit Flag Code
O 1
ID
1

MOA - OUTPATIENT ADJUDICATION INFORMATION

X12 Name:
Medicare Outpatient Adjudication
X12 Purpose:
To convey claim-level data related to the adjudication of Medicare claims not related to an inpatient setting
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when SBR06 = 6; and the submitting payer would be required to provide this information when generating an 835 for the provider.

OR

Required when SBR06 = 1; and 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 SBR06 = 6; and the submitting payer would be required to provide this information when generating an 835 for the provider.ORRequired when SBR06 = 1; and 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 Health Care Financing Administration Common Procedural Coding System (HCPCS) payable amount.
SITUATIONAL RULE: Required when SBR06 = 6; and the submitting payer would be required to provide this information when generating an 835 for the provider.ORRequired when SBR06 = 1; and 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
Situational
3
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: MOA03 is the Claim Payment Remark Code. See Code Source 411.
SITUATIONAL RULE: Required when SBR06 = 6; and the submitting payer would be required to provide this information when generating an 835 for the provider.ORRequired when SBR06 = 1; and 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
Situational
4
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: MOA04 is the Claim Payment Remark Code. See Code Source 411.
SITUATIONAL RULE: Required when SBR06 = 6; and the submitting payer would be required to provide this information when generating an 835 for the provider.ORRequired when SBR06 = 1; and 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
Situational
5
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: MOA05 is the Claim Payment Remark Code. See Code Source 411.
SITUATIONAL RULE: Required when SBR06 = 6; and the submitting payer would be required to provide this information when generating an 835 for the provider.ORRequired when SBR06 = 1; and 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
Situational
6
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: MOA06 is the Claim Payment Remark Code. See Code Source 411.
SITUATIONAL RULE: Required when SBR06 = 6; and the submitting payer would be required to provide this information when generating an 835 for the provider.ORRequired when SBR06 = 1; and 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
Situational
7
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: MOA07 is the Claim Payment Remark Code. See Code Source 411.
SITUATIONAL RULE: Required when SBR06 = 6; and the submitting payer would be required to provide this information when generating an 835 for the provider.ORRequired when SBR06 = 1; and 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
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 SBR06 = 6; and the submitting payer would be required to provide this information when generating an 835 for the provider.ORRequired when SBR06 = 1; and 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
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 SBR06 = 6; and the submitting payer would be required to provide this information when generating an 835 for the provider.ORRequired when SBR06 = 1; and 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

NM1*IL - OTHER SUBSCRIBER NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Segments NM1-N4 contain name and address information of the insurance carriers referenced in loop 2320.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
When SBR06 = 1, the information in this segment represents the Subscriber as submitted by the provider for the payer identified in Loop ID 2330B.

When SBR06 = 6, the information in this segment represents the Subscriber as known by the submitting payer.
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 qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
2
Non-Person Entity
Required
3
1035
Name Last or Organization Name
O 1
AN
1/60
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Other Insured 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 Insured 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 Insured 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 Insured Name Suffix
Required
8
66
Identification Code Qualifier
O 1
ID
1/2
Code designating 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
Required if the HIPAA Individual Patient Identifier is mandated use. If not required, use value `MI' instead.
MI
Member Identification Number
Required
9
67
Identification Code
O 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
INDUSTRY NAME: Other Insured Identifier
Not Used
10
706
Entity Relationship Code
O 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/60

N3 - OTHER SUBSCRIBER ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when 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:
N3✱123 MAIN STREET~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Other Subscriber Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Insured Address Line
If, for whatever reason, the data is not stored within the payer's system, do not use.

N4 - OTHER SUBSCRIBER CITY, STATE, ZIP CODE

X12 Name:
Geographic Location
X12 Purpose:
To specify the geographic place of the named party
X12 Syntax:
  1. E0207
    Only one of N402 or N407 may be present.
  2. C0605
    If N406 is present, then N405 is required.
  3. 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 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
N4✱KANSAS CITY✱MO✱64108~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
INDUSTRY NAME: Other Subscriber City Name
Situational
2
156
State or Province Code
O 1
ID
2
Code (Standard State/Province) as defined by appropriate government agency
COMMENT: N402 is required only if city name (N401) is in the U.S. or Canada.
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Subscriber State or Province Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
O 1
ID
3/15
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada, or when a postal code exists for the country in N404. If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Subscriber Postal Zone or ZIP Code
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
O 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
O 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
O 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

REF*SY - OTHER SUBSCRIBER SOCIAL SECURITY NUMBER

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

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 qualifying 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
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Other Insured Additional Identifier
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

NM1*PR - OTHER PAYER NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Segments NM1-N4 contain name and address information of the insurance carriers referenced in loop 2320.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 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 qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
2
Non-Person Entity
Required
3
1035
Name Last or Organization Name
O 1
AN
1/60
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
O 1
ID
1/2
Code designating the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
On or after the mandated implementation date for the HIPAA National Plan Identifier (National Plan ID), XV must be sent.

Prior to the mandated implementation date and prior to any phase-in period identified by Federal regulation, PI must be sent.

If a phase-in period is designated, PI must be sent unless:
1. Both the sender and receiver agree to use the National Plan ID,
2. The receiver has a National Plan ID, and
3. The sender has the capability to send the National Plan ID.

If all of the above conditions are true, XV must be sent. In this case the Payer Identification Number that would have been sent using qualifier PI can be sent in the corresponding REF segment using qualifier 2U.
CODE
DEFINITION
PI
Payor Identification
XV
Centers for Medicare and Medicaid Services PlanID
CODE SOURCE: 540: Centers for Medicare and Medicaid Services PlanID
Required
9
67
Identification Code
O 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
INDUSTRY NAME: Other Payer Primary Identifier
When sending Line Adjudication Information for this payer, the identifier sent in SVD01 (Payer Identifier) of Loop ID-2430 (Line Adjudication Information) must match this value.
Not Used
10
706
Entity Relationship Code
O 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/60

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✱20120503~
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:
4
Situational Rule:
Required when available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Example:
REF✱2U✱98765~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
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
O 1
AN
1/50
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
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*T4 - OTHER PAYER CLAIM ADJUSTMENT 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:
Situational
Segment Repeat:
1
Situational Rule:
Required when SBR06 = 6; and this claim is a void or adjustment of a previously adjudicated claim.

If not required by this implementation guide, do not send.
TR3 Example:
REF✱T4✱Y~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
T4
Signal Code
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Other Payer Claim Adjustment Indicator
The only valid value for this element is `Y'.
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*F8 - OTHER PAYER CLAIM CONTROL NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when SBR06 = 6.
OR
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✱F8✱R555588~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
F8
Original Reference Number
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Other Payer's Claim Control Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*BP - OTHER PAYER ADJUSTED 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 SBR06 = 6 and the submitting payer has adjusted this claim.
OR
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✱BP✱R5555589~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
BP
Adjustment Control Number
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Other Payer's Adjusted Claim Control Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

NM1*QC - OTHER 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 2330A (Other Payer Subscriber) is not the patient.
TR3 Notes:
  1. NM1*QC*1*DOE*JOHN*T**JR*MI*123456~
  2. When SBR06 = 1, the information in this segment represents the Patient as submitted by the provider for the payer identified in Loop ID 2330B.

    When SBR06 = 6, the information in this segment represents the Patient as known by the submitting payer.
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 qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Required
3
1035
Name Last or Organization Name
O 1
AN
1/60
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Other Insured 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 Insured 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 Insured 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 Insured Name Suffix
Situational
8
66
Identification Code Qualifier
O 1
ID
1/2
Code designating 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 2330A 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
O 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 2330A NM109.If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Insured Identifier
Not Used
10
706
Entity Relationship Code
O 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/60

N3 - OTHER 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 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
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 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 Patient Address Line
If, for whatever reason, the data is not stored within the payer's system, do not use.

N4 - OTHER 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. C0605
    If N406 is present, then N405 is required.
  3. 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 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
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 Patient City Name
Situational
2
156
State or Province Code
O 1
ID
2
Code (Standard State/Province) as defined by appropriate government agency
COMMENT: N402 is required only if city name (N401) is in the U.S. or Canada.
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 Patient State or Province Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
O 1
ID
3/15
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
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 Patient Postal Zone or ZIP Code
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
O 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
O 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
O 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

REF*SY - OTHER 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:
Situational
Segment Usage:
Situational
Segment Repeat:
3
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 qualifying 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
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Other Insured Additional Identifier
Not Used
3
352
Description
O 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/6
Number assigned for differentiation within a transaction set

SV1 - PROFESSIONAL SERVICE

X12 Name:
Professional Service
X12 Purpose:
To specify the service line item detail for a health care professional
X12 Syntax:
P0304
If either SV103 or SV104 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
SV1✱HC:99211:25✱12.25✱UN✱1✱11✱✱1:2:3✱✱Y~
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.
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
The intent is to capture the data as provided on the original claim from the submitter.
CODE
DEFINITION
ER
Jurisdiction Specific Procedure and Supply Codes
CODE SOURCE: 576: Workers Compensation Specific Procedure and Supply Codes
HC
Health Care Financing Administration Common Procedural Coding System (HCPCS) Codes
Because the AMA's CPT codes are also level 1 HCPCS codes, they are reported under HC.
CODE SOURCE: 130: Healthcare Common Procedure Coding System
WK
Advanced Billing Concepts (ABC) Codes
CODE SOURCE: 843: Advanced Billing Concepts (ABC) Codes
Required
1-2
234
Product/Service ID
M 1
AN
1/48
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.
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.
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.
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.
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.
Not Used
1-8
234
Product/Service ID
O 1
AN
1/48
Required
2
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: SV102 is the submitted service line item amount.
INDUSTRY NAME: Line Item Charge Amount
  1. Zero "0" is an acceptable value for this element.
  2. This is the total charge amount for this service line. The amount is inclusive of the provider's base charge and any applicable tax and/or postage claimed amounts reported within this line's AMT segments.
Required
3
355
Unit or Basis for Measurement Code
O 1
ID
2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
SEGMENT SYNTAX: P0304
The intent is to capture the data as provided on the original claim from the submitter.
CODE
DEFINITION
MJ
Minutes
Required for Anesthesia claims.

Anesthesia time is counted from the moment that the practitioner, having completed the preoperative evaluation, starts an intravenous line, places monitors, administers pre-anesthesia sedation, or otherwise physically begins to prepare the patient for anesthesia. Time continues throughout the case and while the practitioner accompanies the patient to the post-anesthesia recovery unit (PACU). Time stops when the practitioner releases the patient to the care of PACU personnel.
UN
Unit
Required
4
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEGMENT SYNTAX: P0304
INDUSTRY NAME: Service Unit Count
  1. Note: When a decimal is needed to report units, include it in this element, for example, "15.6".
  2. The maximum length for this field is 8 digits excluding the decimal. When a decimal is used, the maximum number of digits allowed to the right of the decimal is three.
  3. The intent is to capture the data as provided on the original claim from the submitter.
Situational
5
1331
Facility Code Value
O 1
AN
1/2
Code identifying where services were, or may be, performed; the first and second positions of the Uniform Bill Type Code for Institutional Services or the Place of Service Codes for Professional or Dental Services.
SEMANTIC: SV105 is the place of service.
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
Not Used
6
1365
Service Type Code
O 1
ID
1/2
Required
7
C004
Composite Diagnosis Code Pointer
O 1
To identify one or more diagnosis code pointers
X12 COMPOSITE SEMANTIC NOTES:
  1. C004-01 identifies the primary diagnosis code for this service line.
  2. C004-02 identifies the second diagnosis code for this service line.
  3. C004-03 identifies the third diagnosis code for this service line.
  4. C004-04 identifies the fourth diagnosis code for this service line.
The intent is to capture the data as provided on the original claim from the submitter.
Required
7-1
1328
Diagnosis Code Pointer
M 1
N
1/2
A pointer to the diagnosis code in the order of importance to this service
This first pointer designates the primary diagnosis for this service line. Remaining diagnosis pointers indicate declining level of importance to service line. Acceptable values are 1 through 12, and correspond to Composite Data Elements 01 through 12 in the Health Care Diagnosis Code HI segment in the Claim Loop ID-2300.
Situational
7-2
1328
Diagnosis Code Pointer
O 1
N
1/2
A pointer to the diagnosis code in the order of importance to this service
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
Situational
7-3
1328
Diagnosis Code Pointer
O 1
N
1/2
A pointer to the diagnosis code in the order of importance to this service
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
Situational
7-4
1328
Diagnosis Code Pointer
O 1
N
1/2
A pointer to the diagnosis code in the order of importance to this service
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
Not Used
8
782
Monetary Amount
O 1
R
1/18
Situational
9
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: SV109 is the emergency-related indicator; a "Y" value indicates service provided was emergency related; an "N" value indicates service provided was not emergency related.
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Emergency Indicator
  1. For this implementation, the listed value takes precedence over the semantic note.

    Emergency definition: The patient requires immediate medical intervention as a result of severe, life threatening, or potentially disabling conditions.
  2. The intent is to capture the data as provided on the original claim from the submitter.
CODE
DEFINITION
Y
Yes
Not Used
10
1340
Multiple Procedure Code
O 1
ID
1/2
Situational
11
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: SV111 is early and periodic screen for diagnosis and treatment of children (EPSDT) involvement; a "Y" value indicates EPSDT involvement; an "N" value indicates no EPSDT involvement.
SITUATIONAL RULE: Required when this transaction is being submitted to a Medicaid Agency and the data was submitted in the provider's original claim.If not required by this implementation guide, do not send.
INDUSTRY NAME: EPSDT Indicator
  1. For this implementation, the listed value takes precedence over the semantic note.
  2. When this element is used, this service is not the screening service.
CODE
DEFINITION
Y
Yes
Situational
12
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: SV112 is the family planning involvement indicator. A "Y" value indicates family planning services involvement; an "N" value indicates no family planning services involvement.
SITUATIONAL RULE: Required when this transaction is being submitted to a Medicaid Agency and the data was submitted in the provider's original claim.If not required by this implementation guide, do not send.
INDUSTRY NAME: Family Planning Indicator
For this implementation, the listed value takes precedence over the semantic note.
CODE
DEFINITION
Y
Yes
Not Used
13
1364
Review Code
O 1
ID
1/2
Not Used
14
1341
National or Local Assigned Review Value
O 1
AN
1/2
Situational
15
1327
Copay Status Code
O 1
ID
1
Code indicating whether or not co-payment requirements were met on a line by line basis
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
When this field is populated, the related service was exempt from copay.
CODE
DEFINITION
0
Copay exempt
Not Used
16
1334
Health Care Professional Shortage Area Code
O 1
ID
1
Not Used
17
127
Reference Identification
O 1
AN
1/50
Not Used
18
116
Postal Code
O 1
ID
3/15
Not Used
19
782
Monetary Amount
O 1
R
1/18
Not Used
20
1337
Level of Care Code
O 1
ID
1
Not Used
21
1360
Provider Agreement Code
O 1
ID
1

PWK - LINE SUPPLEMENTAL INFORMATION

X12 Name:
Paperwork
X12 Purpose:
To identify the type or transmission or both of paperwork or supporting information
X12 Syntax:
P0506
If either PWK05 or PWK06 is present, then the other is required.
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:
If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
PWK✱OZ✱BM✱✱✱AC✱DMN0012~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
755
Report Type Code
M 1
ID
2
Code indicating the title or contents of a document, report or supporting item
INDUSTRY NAME: Attachment Report Type Code
CODE
DEFINITION
03
Report Justifying Treatment Beyond Utilization Guidelines
04
Drugs Administered
05
Treatment Diagnosis
06
Initial Assessment
07
Functional Goals
08
Plan of Treatment
09
Progress Report
10
Continued Treatment
11
Chemical Analysis
13
Certified Test Report
15
Justification for Admission
21
Recovery Plan
A3
Allergies/Sensitivities Document
A4
Autopsy Report
AM
Ambulance Certification
AS
Admission Summary
B2
Prescription
B3
Physician Order
B4
Referral Form
BR
Benchmark Testing Results
BS
Baseline
BT
Blanket Test Results
CB
Chiropractic Justification
CK
Consent Form(s)
CT
Certification
D2
Drug Profile Document
DA
Dental Models
DB
Durable Medical Equipment Prescription
DG
Diagnostic Report
DJ
Discharge Monitoring Report
DS
Discharge Summary
EB
Explanation of Benefits (Coordination of Benefits or Medicare Secondary Payor)
HC
Health Certificate
HR
Health Clinic Records
I5
Immunization Record
IR
State School Immunization Records
LA
Laboratory Results
M1
Medical Record Attachment
MT
Models
NN
Nursing Notes
OB
Operative Note
OC
Oxygen Content Averaging Report
OD
Orders and Treatments Document
OE
Objective Physical Examination (including vital signs) Document
OX
Oxygen Therapy Certification
OZ
Support Data for Claim
P4
Pathology Report
P5
Patient Medical History Document
PE
Parenteral or Enteral Certification
PN
Physical Therapy Notes
PO
Prosthetics or Orthotic Certification
PQ
Paramedical Results
PY
Physician's Report
PZ
Physical Therapy Certification
RB
Radiology Films
RR
Radiology Reports
RT
Report of Tests and Analysis Report
RX
Renewable Oxygen Content Averaging Report
SG
Symptoms Document
V5
Death Notification
XP
Photographs
Required
2
756
Report Transmission Code
O 1
ID
1/2
Code defining timing, transmission method or format by which reports are to be sent
INDUSTRY NAME: Attachment Transmission Code
CODE
DEFINITION
AA
Available on Request at Provider Site
This means that the additional information is not being sent with the claim at this time. Instead, it is available to the payer (or appropriate entity) at their request.
BM
By Mail
EL
Electronically Only
Indicates that the attachment is being transmitted in a separate X12 functional group.
EM
E-Mail
FT
File Transfer
Required when the actual attachment is maintained by an attachment warehouse or similar vendor.
FX
By Fax
Not Used
3
757
Report Copies Needed
O 1
N
1/2
Not Used
4
98
Entity Identifier Code
O 1
ID
2/3
Situational
5
66
Identification Code Qualifier
O 1
ID
1/2
Code designating the system/method of code structure used for Identification Code (67)
COMMENT: PWK05 and PWK06 may be used to identify the addressee by a code number.
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
CODE
DEFINITION
AC
Attachment Control Number
Situational
6
67
Identification Code
O 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Attachment Control Number
  1. PWK06 is used to identify the attached electronic documentation. The number in PWK06 is carried in the TRN of the electronic attachment.
  2. For the purpose of this implementation, the maximum field length is 50.
Not Used
7
352
Description
O 1
AN
1/80
Not Used
8
C002
Actions Indicated
O 1
Not Used
9
1525
Request Category Code
O 1
ID
1/2

PWK*CT - DURABLE MEDICAL EQUIPMENT CERTIFICATE OF MEDICAL NECESSITY INDICATOR

X12 Name:
Paperwork
X12 Purpose:
To identify the type or transmission or both of paperwork or supporting information
X12 Syntax:
P0506
If either PWK05 or PWK06 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:
PWK✱CT✱AB~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
755
Report Type Code
M 1
ID
2
Code indicating the title or contents of a document, report or supporting item
INDUSTRY NAME: Attachment Report Type Code
CODE
DEFINITION
CT
Certification
Required
2
756
Report Transmission Code
O 1
ID
1/2
Code defining timing, transmission method or format by which reports are to be sent
INDUSTRY NAME: Attachment Transmission Code
CODE
DEFINITION
AB
Previously Submitted to Payer
AD
Certification Included in this Claim
AF
Narrative Segment Included in this Claim
AG
No Documentation is Required
NS
Not Specified
NS = Paperwork is available on request at the provider's site. This means that the paperwork is not being sent with the claim at this time. Instead, it is available to the payer (or appropriate entity) at their request.
Not Used
3
757
Report Copies Needed
O 1
N
1/2
Not Used
4
98
Entity Identifier Code
O 1
ID
2/3
Not Used
5
66
Identification Code Qualifier
O 1
ID
1/2
Not Used
6
67
Identification Code
O 1
AN
2/80
Not Used
7
352
Description
O 1
AN
1/80
Not Used
8
C002
Actions Indicated
O 1
Not Used
9
1525
Request Category Code
O 1
ID
1/2

CR1*LB - AMBULANCE TRANSPORT INFORMATION

X12 Name:
Ambulance Certification
X12 Purpose:
To supply information related to the ambulance service rendered to a patient
X12 Syntax:
  1. P0102
    If either CR101 or CR102 is present, then the other is required.
  2. P0506
    If either CR105 or CR106 is present, then the other is required.
X12 Set Notes:
NOTE: The CR1 through CR5 and CRC certification segments appear on both the claim level and the service line level because certifications can be submitted for all services on a claim or for individual services. Certification information at the claim level applies to all service lines of the claim, unless overridden by certification information at the service line level.
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:
CR1✱LB✱140✱✱A✱DH✱12✱✱✱✱UNCONSCIOUS~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Situational
1
355
Unit or Basis for Measurement Code
O 1
ID
2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
SEGMENT SYNTAX: P0102
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
CODE
DEFINITION
LB
Pound
Situational
2
81
Weight
O 1
R
1/10
Numeric value of weight
SEMANTIC: CR102 is the weight of the patient at time of transport.
SEGMENT SYNTAX: P0102
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Weight
Not Used
3
1316
Ambulance Transport Code
O 1
ID
1
Required
4
1317
Ambulance Transport Reason Code
O 1
ID
1
Code indicating the reason for ambulance transport
CODE
DEFINITION
A
Patient was transported to nearest facility for care of symptoms, complaints, or both
B
Patient was transported for the benefit of a preferred physician
C
Patient was transported for the nearness of family members
D
Patient was transported for the care of a specialist or for availability of specialized equipment
E
Patient Transferred to Rehabilitation Facility
Required
5
355
Unit or Basis for Measurement Code
O 1
ID
2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
SEGMENT SYNTAX: P0506
CODE
DEFINITION
DH
Miles
Required
6
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: CR106 is the distance traveled during transport.
SEGMENT SYNTAX: P0506
INDUSTRY NAME: Transport Distance
0 (zero) is a valid value when ambulance services do not include a charge for mileage.
Not Used
7
166
Address Information
O 1
AN
1/55
Not Used
8
166
Address Information
O 1
AN
1/55
Situational
9
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
SEMANTIC: CR109 is the purpose for the round trip ambulance service.
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Round Trip Purpose Description
Situational
10
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
SEMANTIC: CR110 is the purpose for the usage of a stretcher during ambulance service.
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Stretcher Purpose Description

CR3 - DURABLE MEDICAL EQUIPMENT CERTIFICATION

X12 Name:
Durable Medical Equipment Certification
X12 Purpose:
To supply information regarding a physician's certification for durable medical equipment
X12 Syntax:
P0203
If either CR302 or CR303 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:
CR3✱I✱MO✱6~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1322
Certification Type Code
O 1
ID
1
Code indicating the type of certification
CODE
DEFINITION
I
Initial
R
Renewal
S
Revised
Required
2
355
Unit or Basis for Measurement Code
O 1
ID
2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
SEMANTIC: CR302 and CR303 specify the time period covered by this certification.
SEGMENT SYNTAX: P0203
CODE
DEFINITION
MO
Months
Required
3
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEGMENT SYNTAX: P0203
INDUSTRY NAME: Durable Medical Equipment Duration
Length of time DME equipment is needed.
Not Used
4
1335
Insulin Dependent Code
O 1
ID
1
Not Used
5
352
Description
O 1
AN
1/80

CRC*07 - AMBULANCE CERTIFICATION

X12 Name:
Conditions Indicator
X12 Purpose:
To supply information on conditions
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:
  1. The maximum number of CRC segments which can occur per Loop ID-2400 is 3. Submitters are free to mix and match the three types of service line level CRC segments shown in this implementation guide to meet their billing or reporting needs but no more than a total of 3 CRC segments per Loop ID-2400 are allowed.
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
CRC✱07✱Y✱01~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1136
Code Category
M 1
ID
2
Specifies the situation or category to which the code applies
SEMANTIC: CRC01 qualifies CRC03 through CRC07.
CODE
DEFINITION
07
Ambulance Certification
Required
2
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: CRC02 is a Certification Condition Code applies indicator. A "Y" value indicates the condition codes in CRC03 through CRC07 apply; an "N" value indicates the condition codes in CRC03 through CRC07 do not apply.
INDUSTRY NAME: Certification Condition Indicator
CODE
DEFINITION
N
No
Y
Yes
Required
3
1321
Condition Indicator
M 1
ID
2/3
Code indicating a condition
INDUSTRY NAME: Condition Code
The codes for CRC03 also can be used for CRC04 through CRC07.
CODE
DEFINITION
01
Patient was admitted to a hospital
04
Patient was moved by stretcher
05
Patient was unconscious or in shock
06
Patient was transported in an emergency situation
07
Patient had to be physically restrained
08
Patient had visible hemorrhaging
09
Ambulance service was medically necessary
12
Patient is confined to a bed or chair
Use code 12 to indicate patient was bedridden during transport.
Situational
4
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use the codes listed in CRC03.
CODE
DEFINITION
01
Patient was admitted to a hospital
04
Patient was moved by stretcher
05
Patient was unconscious or in shock
06
Patient was transported in an emergency situation
07
Patient had to be physically restrained
08
Patient had visible hemorrhaging
09
Ambulance service was medically necessary
12
Patient is confined to a bed or chair
Use code 12 to indicate patient was bedridden during transport.
Situational
5
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use the codes listed in CRC03.
CODE
DEFINITION
01
Patient was admitted to a hospital
04
Patient was moved by stretcher
05
Patient was unconscious or in shock
06
Patient was transported in an emergency situation
07
Patient had to be physically restrained
08
Patient had visible hemorrhaging
09
Ambulance service was medically necessary
12
Patient is confined to a bed or chair
Use code 12 to indicate patient was bedridden during transport.
Situational
6
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use the codes listed in CRC03.
CODE
DEFINITION
01
Patient was admitted to a hospital
04
Patient was moved by stretcher
05
Patient was unconscious or in shock
06
Patient was transported in an emergency situation
07
Patient had to be physically restrained
08
Patient had visible hemorrhaging
09
Ambulance service was medically necessary
12
Patient is confined to a bed or chair
Use code 12 to indicate patient was bedridden during transport.
Situational
7
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use the codes listed in CRC03.
CODE
DEFINITION
01
Patient was admitted to a hospital
04
Patient was moved by stretcher
05
Patient was unconscious or in shock
06
Patient was transported in an emergency situation
07
Patient had to be physically restrained
08
Patient had visible hemorrhaging
09
Ambulance service was medically necessary
12
Patient is confined to a bed or chair
Use code 12 to indicate patient was bedridden during transport.

CRC*70 - HOSPICE EMPLOYEE INDICATOR

X12 Name:
Conditions Indicator
X12 Purpose:
To supply information on conditions
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. The maximum number of CRC segments which can occur per Loop ID-2400 is 3. Submitters are free to mix and match the three types of service line level CRC segments shown in this implementation guide to meet their billing or reporting needs but no more than a total of 3 CRC segments per Loop ID-2400 are allowed.
  2. The example shows the method used to indicate whether the rendering provider is an employee of the hospice.
  3. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
CRC✱70✱Y✱65~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1136
Code Category
M 1
ID
2
Specifies the situation or category to which the code applies
SEMANTIC: CRC01 qualifies CRC03 through CRC07.
CODE
DEFINITION
70
Hospice
Required
2
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: CRC02 is a Certification Condition Code applies indicator. A "Y" value indicates the condition codes in CRC03 through CRC07 apply; an "N" value indicates the condition codes in CRC03 through CRC07 do not apply.
INDUSTRY NAME: Hospice Employed Provider Indicator
A "Y" value indicates the provider is employed by the hospice. A "N" value indicates the provider is not employed by the hospice.
CODE
DEFINITION
N
No
Y
Yes
Required
3
1321
Condition Indicator
M 1
ID
2/3
Code indicating a condition
CODE
DEFINITION
65
Open
This code value is a placeholder to satisfy the Mandatory Data Element syntax requirement.
Not Used
4
1321
Condition Indicator
O 1
ID
2/3
Not Used
5
1321
Condition Indicator
O 1
ID
2/3
Not Used
6
1321
Condition Indicator
O 1
ID
2/3
Not Used
7
1321
Condition Indicator
O 1
ID
2/3

CRC*09 - CONDITION INDICATOR/DURABLE MEDICAL EQUIPMENT

X12 Name:
Conditions Indicator
X12 Purpose:
To supply information on conditions
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. The maximum number of CRC segments which can occur per Loop ID-2400 is 3. Submitters are free to mix and match the three types of service line level CRC segments shown in this implementation guide to meet their billing or reporting needs but no more than a total of 3 CRC segments per Loop ID-2400 are allowed.
  2. The first example shows a case where an item billed was not a replacement item.
  3. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
  1. CRC✱09✱N✱ZV~
  2. CRC✱09✱Y✱38~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1136
Code Category
M 1
ID
2
Specifies the situation or category to which the code applies
SEMANTIC: CRC01 qualifies CRC03 through CRC07.
CODE
DEFINITION
09
Durable Medical Equipment Certification
Required
2
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: CRC02 is a Certification Condition Code applies indicator. A "Y" value indicates the condition codes in CRC03 through CRC07 apply; an "N" value indicates the condition codes in CRC03 through CRC07 do not apply.
INDUSTRY NAME: Certification Condition Indicator
CODE
DEFINITION
N
No
Y
Yes
Required
3
1321
Condition Indicator
M 1
ID
2/3
Code indicating a condition
CODE
DEFINITION
38
Certification signed by the physician is on file at the supplier's office
ZV
Replacement Item
Situational
4
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
Use the codes listed in CRC03.
CODE
DEFINITION
38
Certification signed by the physician is on file at the supplier's office
ZV
Replacement Item
Not Used
5
1321
Condition Indicator
O 1
ID
2/3
Not Used
6
1321
Condition Indicator
O 1
ID
2/3
Not Used
7
1321
Condition Indicator
O 1
ID
2/3

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:
Required
Segment Repeat:
1
TR3 Notes:
The intent is to capture the data as provided on the original claim from the submitter.
TR3 Example:
DTP✱472✱RD8✱20120314-20120325~
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.
RD8 is required only when the "To and From" dates are different. However, at the discretion of the submitter, RD8 can also be used when the "To and From" dates are the same.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
RD8
Range of Dates Expressed in Format CCYYMMDD-CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Service Date

DTP*471 - PRESCRIPTION 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✱471✱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
471
Prescription
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: Prescription Date

DTP*607 - CERTIFICATION REVISION/RECERTIFICATION 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✱607✱D8✱20050112~
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
607
Certification Revision
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: Certification Revision or Recertification Date

DTP*463 - BEGIN THERAPY 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✱463✱D8✱20120112~
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
463
Begin Therapy
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: Begin Therapy Date

DTP*461 - LAST CERTIFICATION 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. This is the date the ordering physician signed the CMN or Oxygen Therapy Certification, or the date the supplier signed the DMERC Information Form (DIF).
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
DTP✱461✱D8✱20050112~
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
461
Last Certification
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: Last Certification Date

DTP*304 - LAST SEEN 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✱304✱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
304
Latest Visit or Consultation
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 or Therapy Date

DTP - TEST 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:
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:
DTP✱738✱D8✱20120112~
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
738
Most Recent Hemoglobin or Hematocrit or Both
739
Most Recent Serum Creatine
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: Test Performed Date

DTP*011 - SHIPPED 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✱011✱D8✱20120112~
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
011
Shipped
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: Shipped Date

DTP*455 - LAST X-RAY 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✱455✱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
455
Last X-Ray
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: Last X-Ray Date

DTP*454 - INITIAL TREATMENT 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✱454✱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
454
Initial Treatment
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: Initial Treatment Date

QTY*PT - AMBULANCE PATIENT COUNT

X12 Name:
Quantity Information
X12 Purpose:
To specify quantity information
X12 Syntax:
  1. R0204
    At least one of QTY02 or QTY04 is required.
  2. E0204
    Only one of QTY02 or QTY04 may be present.
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. The QTY02 is the only place to report the number of patients when there are multiple patients transported.
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
QTY✱PT✱2~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
673
Quantity Qualifier
M 1
ID
2
Code specifying the type of quantity
CODE
DEFINITION
PT
Patients
Required
2
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEGMENT SYNTAX: R0204, E0204
INDUSTRY NAME: Ambulance Patient Count
Not Used
3
C001
Composite Unit of Measure
O 1
Not Used
4
61
Free-form Information
O 1
AN
1/30

QTY*FL - OBSTETRIC ANESTHESIA ADDITIONAL UNITS

X12 Name:
Quantity Information
X12 Purpose:
To specify quantity information
X12 Syntax:
  1. R0204
    At least one of QTY02 or QTY04 is required.
  2. E0204
    Only one of QTY02 or QTY04 may be present.
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:
QTY✱FL✱3~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
673
Quantity Qualifier
M 1
ID
2
Code specifying the type of quantity
CODE
DEFINITION
FL
Units
Required
2
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEGMENT SYNTAX: R0204, E0204
INDUSTRY NAME: Obstetric Additional Units
The number of additional units reported by an anesthesia provider to reflect additional complexity of services.
Not Used
3
C001
Composite Unit of Measure
O 1
Not Used
4
61
Free-form Information
O 1
AN
1/30

MEA - TEST RESULT

X12 Name:
Measurements
X12 Purpose:
To specify physical measurements or counts, including dimensions, tolerances, variances, and weights

(See Figures Appendix for example of use of C001)
X12 Syntax:
  1. R03050608
    At least one of MEA03, MEA05, MEA06 or MEA08 is required.
  2. E0412
    Only one of MEA04 or MEA12 may be present.
  3. L050412
    If MEA05 is present, then at least one of MEA04 or MEA12 are required.
  4. L060412
    If MEA06 is present, then at least one of MEA04 or MEA12 are required.
  5. L07030506
    If MEA07 is present, then at least one of MEA03, MEA05 or MEA06 are required.
  6. E0803
    Only one of MEA08 or MEA03 may be present.
  7. P1112
    If either MEA11 or MEA12 is present, then the other 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:
MEA✱TR✱R1✱113.4~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
737
Measurement Reference ID Code
O 1
ID
2
Code identifying the broad category to which a measurement applies
INDUSTRY NAME: Measurement Reference Identification Code
CODE
DEFINITION
OG
Original
Use OG to report Starting Dosage.
TR
Test Results
Required
2
738
Measurement Qualifier
O 1
ID
1/3
Code identifying a specific product or process characteristic to which a measurement applies
CODE
DEFINITION
HT
Height
R1
Hemoglobin
R2
Hematocrit
R3
Epoetin Starting Dosage
R4
Creatinine
Required
3
739
Measurement Value
O 1
R
1/20
The value of the measurement
SEGMENT SYNTAX: R03050608, L07030506, E0803
INDUSTRY NAME: Test Results
Not Used
4
C001
Composite Unit of Measure
O 1
Not Used
5
740
Range Minimum
O 1
R
1/20
Not Used
6
741
Range Maximum
O 1
R
1/20
Not Used
7
935
Measurement Significance Code
O 1
ID
2
Not Used
8
936
Measurement Attribute Code
O 1
ID
2
Not Used
9
752
Surface/Layer/Position Code
O 1
ID
2
Not Used
10
1373
Measurement Method or Device
O 1
ID
2/4
Not Used
11
1270
Code List Qualifier Code
O 1
ID
1/3
Not Used
12
1271
Industry Code
O 1
AN
1/30

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
01
Diagnosis Related Group (DRG)
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
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/50
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
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*9B - REPRICED LINE ITEM REFERENCE NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when 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✱9B✱444444~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
9B
Repriced Line Item Reference Number
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Repriced Line Item Reference Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*9D - ADJUSTED REPRICED LINE ITEM REFERENCE NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when 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✱9D✱444444~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
9D
Adjusted Repriced Line Item Reference Number
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Adjusted Repriced Line Item Reference Number
Not Used
3
352
Description
O 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:
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 qualifying the Reference Identification
CODE
DEFINITION
G1
Prior Authorization Number
Required
2
127
Reference Identification
O 1
AN
1/50
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
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*6R - LINE ITEM CONTROL NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
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✱6R✱54321~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
6R
Provider Control Number
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Line Item Control Number
The maximum number of characters to be supported for this field is `30'. A submitter may submit fewer characters depending upon their needs. However, the HIPAA maximum requirement to be supported by any receiving system is `30'. Characters beyond 30 are not required to be stored nor returned by any 837-receiving system.
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*EW - MAMMOGRAPHY CERTIFICATION 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✱EW✱T554~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
EW
Mammography Certification Number
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Mammography Certification Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*X4 - CLINICAL LABORATORY IMPROVEMENT AMENDMENT (CLIA) 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✱X4✱12D4567890~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
X4
Clinical Laboratory Improvement Amendment Number
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Clinical Laboratory Improvement Amendment Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*F4 - REFERRING CLINICAL LABORATORY IMPROVEMENT AMENDMENT (CLIA) FACILITY 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✱F4✱34D1234567~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
F4
Facility Certification Number
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Referring CLIA Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*BT - IMMUNIZATION BATCH 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✱BT✱DTP22333444~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
BT
Batch Number
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Immunization Batch Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*9F - REFERRAL NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when 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 qualifying the Reference Identification
CODE
DEFINITION
9F
Referral Number
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Referral Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

AMT*T - SALES TAX AMOUNT

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. When reporting the Sales Tax Amount (AMT02), the amount reported in the Line Item Charge Amount (SV102) for this service line must include the amount reported in the Sales Tax Amount.
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
AMT✱T✱45~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
522
Amount Qualifier Code
M 1
ID
1/3
Code to qualify amount
CODE
DEFINITION
T
Tax
Required
2
782
Monetary Amount
M 1
R
1/18
Monetary amount
INDUSTRY NAME: Sales Tax Amount
Not Used
3
478
Credit/Debit Flag Code
O 1
ID
1

AMT*F4 - POSTAGE CLAIMED AMOUNT

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. When reporting the Postage Claimed Amount (AMT02), the amount reported in the Line Item Charge Amount (SV102) for this service line must include the amount reported in the Postage Claimed Amount.
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
AMT✱F4✱56.78~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
522
Amount Qualifier Code
M 1
ID
1/3
Code to qualify amount
CODE
DEFINITION
F4
Postage Claimed
Required
2
782
Monetary Amount
M 1
R
1/18
Monetary amount
INDUSTRY NAME: Postage Claimed Amount
Not Used
3
478
Credit/Debit Flag Code
O 1
ID
1

K3 - FILE INFORMATION

X12 Name:
File Information
X12 Purpose:
To transmit a fixed-format record or matrix contents
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
10
Situational Rule:
Required when 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

NTE - LINE NOTE

X12 Name:
Note/Special Instruction
X12 Purpose:
To transmit information in a free-form format, if necessary, for comment or special instruction
X12 Comments:
The NTE segment permits free-form information/data which, under ANSI X12 standard implementations, is not machine processible. The use of the NTE segment should therefore be avoided, if at all possible, in an automated environment.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
  1. Use SV101-7 to describe non-specific procedure codes. Do not use this NTE Segment to describe a non-specific procedure code. If an NDC code is reported in Loop 2410, do not use this segment for a description of the procedure code. The NDC in loop 2410 will provide the description.
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
NTE✱DCP✱PATIENT GOAL TO BE OFF OXYGEN BY END OF MONTH~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
363
Note Reference Code
O 1
ID
3
Code identifying the functional area or purpose for which the note applies
CODE
DEFINITION
ADD
Additional Information
DCP
Goals, Rehabilitation Potential, or Discharge Plans
Required
2
352
Description
M 1
AN
1/80
A free-form description to clarify the related data elements and their content
INDUSTRY NAME: Line Note Text

NTE*TPO - THIRD PARTY ORGANIZATION NOTES

X12 Name:
Note/Special Instruction
X12 Purpose:
To transmit information in a free-form format, if necessary, for comment or special instruction
X12 Comments:
The NTE segment permits free-form information/data which, under ANSI X12 standard implementations, is not machine processible. The use of the NTE segment should therefore be avoided, if at all possible, in an automated environment.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
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:
NTE✱TPO✱STATE REGULATION 123 WAS APPLIED DURING THE PRICING OF THIS CLAIM~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
363
Note Reference Code
O 1
ID
3
Code identifying the functional area or purpose for which the note applies
CODE
DEFINITION
TPO
Third Party Organization Notes
Required
2
352
Description
M 1
AN
1/80
A free-form description to clarify the related data elements and their content
INDUSTRY NAME: Line Note Text

PS1 - PURCHASED SERVICE INFORMATION

X12 Name:
Purchase Service
X12 Purpose:
To specify the information about services that are purchased
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:
PS1✱PN222222✱110~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
127
Reference Identification
M 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: PS101 is provider identification number.
INDUSTRY NAME: Purchased Service Provider Identifier
This must be the identifier from the Purchased Service Provider Loop (Loop ID-2420B). When the Secondary Identifier REF is used, that is the identifier to be reported. If not present, use the identifier in NM109.
Required
2
782
Monetary Amount
M 1
R
1/18
Monetary amount
SEMANTIC: PS102 is cost of the purchased service.
INDUSTRY NAME: Purchased Service Charge Amount
Not Used
3
156
State or Province Code
O 1
ID
2

HCP - LINE PRICING/REPRICING INFORMATION

X12 Name:
Health Care Pricing
X12 Purpose:
To specify pricing or repricing information about a health care claim or line item
X12 Syntax:
  1. R0113
    At least one of HCP01 or HCP13 is required.
  2. P0910
    If either HCP09 or HCP10 is present, then the other is required.
  3. P1112
    If either HCP11 or HCP12 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when 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:
HCP✱03✱100✱10✱RPO12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1473
Pricing Methodology
O 1
ID
2
Code specifying pricing methodology at which the claim or line item has been priced or repriced
SEGMENT SYNTAX: R0113
Specific code use is determined by Trading Partner Agreement due to the variances in contracting policies in the industry.
CODE
DEFINITION
00
Zero Pricing (Not Covered Under Contract)
01
Priced as Billed at 100%
02
Priced at the Standard Fee Schedule
03
Priced at a Contractual Percentage
04
Bundled Pricing
05
Peer Review Pricing
06
Per Diem Pricing
07
Flat Rate Pricing
08
Combination Pricing
09
Maternity Pricing
10
Other Pricing
11
Lower of Cost
12
Ratio of Cost
13
Cost Reimbursed
14
Adjustment Pricing
Required
2
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: HCP02 is the allowed amount.
INDUSTRY NAME: Repriced Allowed Amount
Situational
3
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: HCP03 is the savings amount.
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Repriced Saving Amount
Situational
4
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: HCP04 is the repricing organization identification number.
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Repricing Organization Identifier
Situational
5
118
Rate
O 1
R
1/9
Rate expressed in the standard monetary denomination for the currency specified
SEMANTIC: HCP05 is the pricing rate associated with per diem or flat rate repricing.
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Repricing Per Diem or Flat Rate Amount
Situational
6
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: HCP06 is the approved DRG code.
COMMENT: HCP06, HCP07, HCP08, HCP10, and HCP12 are fields that will contain different values from the original submitted values.
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Repriced Approved Ambulatory Patient Group (APG) Code
Situational
7
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: HCP07 is the approved DRG amount.
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Repriced Approved Ambulatory Patient Group (APG) Amount
Not Used
8
234
Product/Service ID
O 1
AN
1/48
Situational
9
235
Product/Service ID Qualifier
O 1
ID
2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
SEGMENT SYNTAX: P0910
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Product or Service ID Qualifier
CODE
DEFINITION
ER
Jurisdiction Specific Procedure and Supply Codes
CODE SOURCE: 576: Workers Compensation Specific Procedure and Supply Codes
HC
Health Care Financing Administration Common Procedural Coding System (HCPCS) Codes
Because the AMA's CPT codes are also level 1 HCPCS codes, they are reported under HC.
CODE SOURCE: 130: Healthcare Common Procedure Coding System
IV
Home Infusion EDI Coalition (HIEC) Product/Service Code
CODE SOURCE: 513: Home Infusion EDI Coalition (HIEC) Product/Service Code List
WK
Advanced Billing Concepts (ABC) Codes
CODE SOURCE: 843: Advanced Billing Concepts (ABC) Codes
Situational
10
234
Product/Service ID
O 1
AN
1/48
Identifying number for a product or service
SEMANTIC: HCP10 is the approved procedure code.
SEGMENT SYNTAX: P0910
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Repriced Approved HCPCS Code
Situational
11
355
Unit or Basis for Measurement Code
O 1
ID
2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
SEGMENT SYNTAX: P1112
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
CODE
DEFINITION
MJ
Minutes
UN
Unit
Situational
12
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: HCP12 is the approved service units or inpatient days.
SEGMENT SYNTAX: P1112
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Repriced Approved Service Unit Count
  1. Note: When a decimal is needed to report units, include it in this element, for example, "15.6".
  2. The maximum length for this field is 8 digits excluding the decimal. When a decimal is used, the maximum number of digits allowed to the right of the decimal is three.
Situational
13
901
Reject Reason Code
O 1
ID
2
Code assigned by issuer to identify reason for rejection
SEMANTIC: HCP13 is the rejection message returned from the third party organization.
SEGMENT SYNTAX: R0113
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
CODE
DEFINITION
T1
Cannot Identify Provider as TPO (Third Party Organization) Participant
T2
Cannot Identify Payer as TPO (Third Party Organization) Participant
T3
Cannot Identify Insured as TPO (Third Party Organization) Participant
T4
Payer Name or Identifier Missing
T5
Certification Information Missing
T6
Claim does not contain enough information for re-pricing
Situational
14
1526
Policy Compliance Code
O 1
ID
1/2
Code specifying policy compliance
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Procedure Followed (Compliance)
2
Not Followed - Call Not Made (Non-Compliance Call Not Made)
3
Not Medically Necessary (Non-Compliance Non-Medically Necessary)
4
Not Followed Other (Non-Compliance Other)
5
Emergency Admit to Non-Network Hospital
Situational
15
1527
Exception Code
O 1
ID
1/2
Code specifying the exception reason for consideration of out-of-network health care services
SEMANTIC: HCP15 is the exception reason generated by a third party organization.
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Non-Network Professional Provider in Network Hospital
2
Emergency Care
3
Services or Specialist not in Network
4
Out-of-Service Area
5
State Mandates
6
Other

LIN - DRUG IDENTIFICATION

X12 Name:
Item Identification
X12 Purpose:
To specify basic item identification data
X12 Syntax:
  1. P0405
    If either LIN04 or LIN05 is present, then the other is required.
  2. P0607
    If either LIN06 or LIN07 is present, then the other is required.
  3. P0809
    If either LIN08 or LIN09 is present, then the other is required.
  4. P1011
    If either LIN10 or LIN11 is present, then the other is required.
  5. P1213
    If either LIN12 or LIN13 is present, then the other is required.
  6. P1415
    If either LIN14 or LIN15 is present, then the other is required.
  7. P1617
    If either LIN16 or LIN17 is present, then the other is required.
  8. P1819
    If either LIN18 or LIN19 is present, then the other is required.
  9. P2021
    If either LIN20 or LIN21 is present, then the other is required.
  10. P2223
    If either LIN22 or LIN23 is present, then the other is required.
  11. P2425
    If either LIN24 or LIN25 is present, then the other is required.
  12. P2627
    If either LIN26 or LIN27 is present, then the other is required.
  13. P2829
    If either LIN28 or LIN29 is present, then the other is required.
  14. P3031
    If either LIN30 or LIN31 is present, then the other is required.
X12 Set Notes:
NOTE: Loop 2410 contains compound drug components, quantities and prices.
X12 Comments:
See the Data Dictionary for a complete list of IDs.
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. Drugs and biologics reported in this segment are a further specification of service(s) described in the SV1 segment of this Service Line Loop ID-2400.
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
LIN✱✱N4✱01234567891~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Not Used
1
350
Assigned Identification
O 1
AN
1/20
Required
2
235
Product/Service ID Qualifier
M 1
ID
2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
COMMENT: LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
INDUSTRY NAME: Product or Service ID Qualifier
At the time of this writing, UPN code sets designated by values EN, EO, HI, ON, UK, and UP have been approved by the Secretary of HHS as a pilot project allowed under HIPAA law. During the pilot, these code values may only be used by parties registered in the pilot project and their trading partners. Beyond the pilot, these codes may only be used if mandated by government regulation.
CODE
DEFINITION
EN
EAN/UCC - 13
CODE SOURCE: 41: GS1 US Global Trade Item Number (GTIN)
EO
EAN/UCC - 8
CODE SOURCE: 41: GS1 US Global Trade Item Number (GTIN)
HI
HIBC (Health Care Industry Bar Code) Supplier Labeling Standard Primary Data Message
N4
National Drug Code in 5-4-2 Format
Receivers are advised not to attempt validation using only the FDA code list identified by the code source as there are valid NDC values assigned by other sources that are not included in the FDA listing.
CODE SOURCE: 240: National Drug Code by Format
ON
Customer Order Number
UK
GTIN 14-digit Data Structure
CODE SOURCE: 41: GS1 US Global Trade Item Number (GTIN)
UP
UCC - 12
CODE SOURCE: 41: GS1 US Global Trade Item Number (GTIN)
Required
3
234
Product/Service ID
M 1
AN
1/48
Identifying number for a product or service
INDUSTRY NAME: National Drug Code, Universal Product Number or Device Identifier of the Unique Device Identifier
Not Used
4
235
Product/Service ID Qualifier
O 1
ID
2
Not Used
5
234
Product/Service ID
O 1
AN
1/48
Not Used
6
235
Product/Service ID Qualifier
O 1
ID
2
Not Used
7
234
Product/Service ID
O 1
AN
1/48
Not Used
8
235
Product/Service ID Qualifier
O 1
ID
2
Not Used
9
234
Product/Service ID
O 1
AN
1/48
Not Used
10
235
Product/Service ID Qualifier
O 1
ID
2
Not Used
11
234
Product/Service ID
O 1
AN
1/48
Not Used
12
235
Product/Service ID Qualifier
O 1
ID
2
Not Used
13
234
Product/Service ID
O 1
AN
1/48
Not Used
14
235
Product/Service ID Qualifier
O 1
ID
2
Not Used
15
234
Product/Service ID
O 1
AN
1/48
Not Used
16
235
Product/Service ID Qualifier
O 1
ID
2
Not Used
17
234
Product/Service ID
O 1
AN
1/48
Not Used
18
235
Product/Service ID Qualifier
O 1
ID
2
Not Used
19
234
Product/Service ID
O 1
AN
1/48
Not Used
20
235
Product/Service ID Qualifier
O 1
ID
2
Not Used
21
234
Product/Service ID
O 1
AN
1/48
Not Used
22
235
Product/Service ID Qualifier
O 1
ID
2
Not Used
23
234
Product/Service ID
O 1
AN
1/48
Not Used
24
235
Product/Service ID Qualifier
O 1
ID
2
Not Used
25
234
Product/Service ID
O 1
AN
1/48
Not Used
26
235
Product/Service ID Qualifier
O 1
ID
2
Not Used
27
234
Product/Service ID
O 1
AN
1/48
Not Used
28
235
Product/Service ID Qualifier
O 1
ID
2
Not Used
29
234
Product/Service ID
O 1
AN
1/48
Not Used
30
235
Product/Service ID Qualifier
O 1
ID
2
Not Used
31
234
Product/Service ID
O 1
AN
1/48

CTP - DRUG QUANTITY

X12 Name:
Pricing Information
X12 Purpose:
To specify pricing information
X12 Syntax:
  1. P0405
    If either CTP04 or CTP05 is present, then the other is required.
  2. C0607
    If CTP06 is present, then CTP07 is required.
  3. C0902
    If CTP09 is present, then CTP02 is required.
  4. C1002
    If CTP10 is present, then CTP02 is required.
  5. C1103
    If CTP11 is present, then CTP03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
The intent is to capture the information as stored in the payer's system.
TR3 Example:
CTP✱✱✱✱2✱UN~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Not Used
1
687
Class of Trade Code
O 1
ID
2
Not Used
2
236
Price Identifier Code
O 1
ID
3
Not Used
3
212
Unit Price
O 1
R
1/17
Required
4
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEGMENT SYNTAX: P0405
INDUSTRY NAME: National Drug Unit Count
Required
5
C001
Composite Unit of Measure
O 1
To identify a composite unit of measure

(See Figures Appendix for examples of use)
X12 COMPOSITE COMMENTS:
  1. If C001-02 is not used, its value is to be interpreted as 1.
  2. If C001-03 is not used, its value is to be interpreted as 1.
  3. If C001-05 is not used, its value is to be interpreted as 1.
  4. If C001-06 is not used, its value is to be interpreted as 1.
  5. If C001-08 is not used, its value is to be interpreted as 1.
  6. If C001-09 is not used, its value is to be interpreted as 1.
  7. If C001-11 is not used, its value is to be interpreted as 1.
  8. If C001-12 is not used, its value is to be interpreted as 1.
  9. If C001-14 is not used, its value is to be interpreted as 1.
  10. If C001-15 is not used, its value is to be interpreted as 1.
Required
5-1
355
Unit or Basis for Measurement Code
M 1
ID
2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
INDUSTRY NAME: Code Qualifier
CODE
DEFINITION
F2
International Unit
GR
Gram
ME
Milligram
ML
Milliliter
UN
Unit
Not Used
5-2
1018
Exponent
O 1
R
1/15
Not Used
5-3
649
Multiplier
O 1
R
1/10
Not Used
5-4
355
Unit or Basis for Measurement Code
O 1
ID
2
Not Used
5-5
1018
Exponent
O 1
R
1/15
Not Used
5-6
649
Multiplier
O 1
R
1/10
Not Used
5-7
355
Unit or Basis for Measurement Code
O 1
ID
2
Not Used
5-8
1018
Exponent
O 1
R
1/15
Not Used
5-9
649
Multiplier
O 1
R
1/10
Not Used
5-10
355
Unit or Basis for Measurement Code
O 1
ID
2
Not Used
5-11
1018
Exponent
O 1
R
1/15
Not Used
5-12
649
Multiplier
O 1
R
1/10
Not Used
5-13
355
Unit or Basis for Measurement Code
O 1
ID
2
Not Used
5-14
1018
Exponent
O 1
R
1/15
Not Used
5-15
649
Multiplier
O 1
R
1/10
Not Used
6
648
Price Multiplier Qualifier
O 1
ID
3
Not Used
7
649
Multiplier
O 1
R
1/10
Not Used
8
782
Monetary Amount
O 1
R
1/18
Not Used
9
639
Basis of Unit Price Code
O 1
ID
2
Not Used
10
499
Condition Value
O 1
AN
1/10
Not Used
11
289
Multiple Price Quantity
O 1
N
1/2

REF - PRESCRIPTION OR COMPOUND DRUG ASSOCIATION 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 available in the payer's system.
If not required by this implementation guide, do not send.
TR3 Notes:
  1. In cases where a compound drug is being billed, the components of the compound will all have the same prescription number. Payers receiving the claim can relate all the components by matching the prescription number.
  2. For cases where the drug is provided without a prescription (for example, from a physician's office), the value provided in this segment is a "link sequence number". The link sequence number is a provider assigned number that is unique to this claim. Its purpose is to enable the receiver to piece together the components of the compound.
  3. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
REF✱XZ✱123456~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
VY
Link Sequence Number
XZ
Pharmacy Prescription Number
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Prescription Number
Not Used
3
352
Description
O 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 2420 contains information about the rendering, referring, or attending provider on a service line level. 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 qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
2
Non-Person Entity
Required
3
1035
Name Last or Organization Name
O 1
AN
1/60
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
O 1
ID
1/2
Code designating 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
Centers for Medicare and Medicaid Services National Provider Identifier
CODE SOURCE: 537: Centers for Medicare & Medicaid Services National Provider Identifier
Situational
9
67
Identification Code
O 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
O 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/60

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✱208D00000X~
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
O 1
ID
2/3
Code qualifying 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
O 1
AN
1/50
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
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 qualifying 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-2330B 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
O 1
AN
1/50
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
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

NM1*QB - PURCHASED SERVICE 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 rendering, referring, or attending provider on a service line level. 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:
  1. Purchased services are situations where, for example, a physician purchases a diagnostic exam from an outside entity. Purchased services do not include substitute (locum tenens) provider situations.
  2. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
NM1✱QB✱2✱✱✱✱✱✱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
The entity identifier in NM101 applies to all segments in this iteration of Loop ID-2420.
CODE
DEFINITION
QB
Purchase Service Provider
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
2
Non-Person Entity
Not Used
3
1035
Name Last or Organization Name
O 1
AN
1/60
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
O 1
ID
1/2
Code designating 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
Centers for Medicare and Medicaid Services National Provider Identifier
CODE SOURCE: 537: Centers for Medicare & Medicaid Services National Provider Identifier
Situational
9
67
Identification Code
O 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: Purchased Service 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
O 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/60

REF - PURCHASED SERVICE 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:
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 qualifying 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-2330B where 2320 SBR06 equals 6. This is to be used by all payers including: Medicare, Medicaid, Blue Cross, etc.
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Purchased Service Provider Secondary Identifier
Not Used
3
352
Description
O 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 2420 contains information about the rendering, referring, or attending provider on a service line level. 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 Service Facility Location for this line is different than the Service Facility Location reported in Loop ID-2310C (claim level) and is available in the payer's system.

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. When an organization health care provider's NPI is provided to identify the Service Location, the organization health care provider must be external to the entity identified as the Billing Provider (for example, reference lab). It is not permissible to report an organization health care provider NPI as the Service Location if the entity being identified is a component (for example, subpart) of the Billing Provider. In that case, the subpart must be the Billing Provider.
  2. The purpose of this loop is to identify specifically where the service was rendered. When reporting ambulance services, do not use this loop. Use the pick-up (2420G) and drop-off location (2420H) loops elsewhere in this transaction.
  3. If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
NM1✱77✱2✱ABC CLINIC✱✱✱✱✱XX✱1234567891~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
77
Service Location
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
2
Non-Person Entity
Required
3
1035
Name Last or Organization Name
O 1
AN
1/60
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
O 1
ID
1/2
Code designating 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
Centers for Medicare and Medicaid Services National Provider Identifier
CODE SOURCE: 537: Centers for Medicare & Medicaid Services National Provider Identifier
Situational
9
67
Identification Code
O 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: Laboratory or Facility Primary Identifier
Not Used
10
706
Entity Relationship Code
O 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/60

N3 - SERVICE FACILITY LOCATION ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
If service facility location is in an area where there are no street addresses, enter a description of where the service was rendered (for example, "crossroad of State Road 34 and 45" or "Exit near Mile marker 265 on Interstate 80".)
TR3 Example:
N3✱123 MAIN STREET~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: 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. C0605
    If N406 is present, then N405 is required.
  3. C0704
    If N407 is present, then N404 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
N4✱KANSAS CITY✱MO✱64108~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
INDUSTRY NAME: Laboratory or Facility City Name
Situational
2
156
State or Province Code
O 1
ID
2
Code (Standard State/Province) as defined by appropriate government agency
COMMENT: N402 is required only if city name (N401) is in the U.S. or Canada.
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
O 1
ID
3/15
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
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
O 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
O 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
O 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

REF*G2 - 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:
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 qualifying the Reference Identification
CODE
DEFINITION
G2
Provider Commercial Number
This code designates a proprietary provider number for the submitting payer identified in the Payer Name loop, Loop ID-2330B where 2320 SBR06 equals 6. This is to be used by all payers including: Medicare, Medicaid, Blue Cross, etc.
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Service Facility Location Secondary Identifier
Not Used
3
352
Description
O 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 rendering, referring, or attending provider on a service line level. 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 Supervising Provider for this line is different than the Supervising Provider reported in Loop ID-2310D (claim level) and is available in the payer's system.

If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver.
TR3 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
TR3 Example:
NM1✱DQ✱1✱DOE✱JOHN✱B✱✱✱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
DQ
Supervising Physician
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Required
3
1035
Name Last or Organization Name
O 1
AN
1/60
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
O 1
ID
1/2
Code designating 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
Centers for Medicare and Medicaid Services National Provider Identifier
CODE SOURCE: 537: Centers for Medicare & Medicaid Services National Provider Identifier
Situational
9
67
Identification Code
O 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
O 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/60

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✱G2✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying 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-2330B 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
O 1
AN
1/50
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
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

NM1*DK - ORDERING 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 rendering, referring, or attending provider on a service line level. 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✱DK✱1✱RICHARDSON✱TRENT✱✱✱✱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
The entity identifier in NM101 applies to all segments in this iteration of Loop ID-2420.
CODE
DEFINITION
DK
Ordering Physician
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Required
3
1035
Name Last or Organization Name
O 1
AN
1/60
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Ordering 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: Ordering 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: Ordering 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: Ordering Provider Name Suffix
Situational
8
66
Identification Code Qualifier
O 1
ID
1/2
Code designating 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
Centers for Medicare and Medicaid Services National Provider Identifier
CODE SOURCE: 537: Centers for Medicare & Medicaid Services National Provider Identifier
Situational
9
67
Identification Code
O 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: Ordering 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
O 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/60

N3 - ORDERING PROVIDER 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 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
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: Ordering 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: Ordering Provider Address Line

N4 - ORDERING 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. C0605
    If N406 is present, then N405 is required.
  3. 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 Notes:
If, for whatever reason, the data is not stored within the payer's system, do not use.
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: Ordering Provider City Name
Situational
2
156
State or Province Code
O 1
ID
2
Code (Standard State/Province) as defined by appropriate government agency
COMMENT: N402 is required only if city name (N401) is in the U.S. or Canada.
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: Ordering Provider State or Province Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
O 1
ID
3/15
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
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: Ordering Provider Postal Zone or ZIP Code
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
O 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
O 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
O 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

REF - ORDERING 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:
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 qualifying 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-2330B where 2320 SBR06 equals 6. This is to be used by all payers including: Medicare, Medicaid, Blue Cross, etc.
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Ordering Provider Secondary Identifier
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

PER*IC - ORDERING PROVIDER CONTACT INFORMATION

X12 Name:
Administrative Communications Contact
X12 Purpose:
To identify a person or office to whom administrative communications should be directed
X12 Syntax:
  1. P0304
    If either PER03 or PER04 is present, then the other is required.
  2. P0506
    If either PER05 or PER06 is present, then the other is required.
  3. P0708
    If either PER07 or PER08 is present, then the other is required.
Loop:
Loop Usage:
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. 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. If, for whatever reason, the data is not stored within the payer's system, do not use.
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 available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Ordering Provider Contact Name
Required
3
365
Communication Number Qualifier
O 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
O 1
AN
1/256
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0304
Situational
5
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when available in the payer's system.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
O 1
AN
1/256
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
Situational
7
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when available in the payer's system.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
O 1
AN
1/256
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
Not Used
9
443
Contact Inquiry Reference
O 1
AN
1/20

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 2420 contains information about the rendering, referring, or attending provider on a service line level. 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 Referring Provider for this line is different than the Referring Provider reported in Loop ID-2310A (claim level) and is available in the payer's system.

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. When reporting the provider who ordered services such as diagnostic and lab, use Loop ID-2310A at the claim level. For ordered services such as Durable Medical Equipment, use Loop ID-2420E at the line level.
  2. 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.
  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 qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Required
3
1035
Name Last or Organization Name
O 1
AN
1/60
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
O 1
ID
1/2
Code designating 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
Centers for Medicare and Medicaid Services National Provider Identifier
CODE SOURCE: 537: Centers for Medicare & Medicaid Services National Provider Identifier
Situational
9
67
Identification Code
O 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
O 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/60

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:
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 qualifying 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-2330B where 2320 SBR06 equals 6. This is to be used by all payers including: Medicare, Medicaid, Blue Cross, etc.
Required
2
127
Reference Identification
O 1
AN
1/50
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
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

NM1*PW - AMBULANCE PICK-UP LOCATION

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Loop 2420 contains information about the rendering, referring, or attending provider on a service line level. 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 ambulance pick-up location for this service line is different than the ambulance pick-up location reported in Loop ID-2310E and is available in the payer's system. If not required by this implementation guide, do not send.
TR3 Example:
NM1✱PW✱2~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
PW
Pickup Address
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
2
Non-Person Entity
Not Used
3
1035
Name Last or Organization Name
O 1
AN
1/60
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
O 1
ID
1/2
Not Used
9
67
Identification Code
O 1
AN
2/80
Not Used
10
706
Entity Relationship Code
O 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/60

N3 - AMBULANCE PICK-UP LOCATION ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 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: Ambulance Pick-up 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: Ambulance Pick-up Address Line

N4 - AMBULANCE PICK-UP 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. C0605
    If N406 is present, then N405 is required.
  3. C0704
    If N407 is present, then N404 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
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: Ambulance Pick-up City Name
Situational
2
156
State or Province Code
O 1
ID
2
Code (Standard State/Province) as defined by appropriate government agency
COMMENT: N402 is required only if city name (N401) is in the U.S. or Canada.
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: Ambulance Pick-up State or Province Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
O 1
ID
3/15
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
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: Ambulance Pick-up Postal Zone or ZIP Code
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
O 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: Ambulance Pick-up 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
O 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
O 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: Ambulance Pick-up Country Subdivision Code
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds

NM1*45 - AMBULANCE DROP-OFF LOCATION

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Loop 2420 contains information about the rendering, referring, or attending provider on a service line level. 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 ambulance drop-off location for this service line is different than the ambulance drop-off location reported in Loop ID-2310F and is available in the payer's system. If not required by this implementation guide, do not send.
TR3 Example:
NM1✱45✱2~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
45
Drop-off Location
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
2
Non-Person Entity
Situational
3
1035
Name Last or Organization Name
O 1
AN
1/60
Individual last name or organizational name
SEGMENT SYNTAX: C1203
SITUATIONAL RULE: Required when available in the payer's system.If not required by this implementation guide, do not send.
INDUSTRY NAME: Ambulance Drop-off Location
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
O 1
ID
1/2
Not Used
9
67
Identification Code
O 1
AN
2/80
Not Used
10
706
Entity Relationship Code
O 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/60

N3 - AMBULANCE DROP-OFF LOCATION ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 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: Ambulance Drop-off 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: Ambulance Drop-off Address Line

N4 - AMBULANCE DROP-OFF 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. C0605
    If N406 is present, then N405 is required.
  3. C0704
    If N407 is present, then N404 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
N4✱KANSAS CITY✱MO✱64108~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
INDUSTRY NAME: Ambulance Drop-off City Name
Situational
2
156
State or Province Code
O 1
ID
2
Code (Standard State/Province) as defined by appropriate government agency
COMMENT: N402 is required only if city name (N401) is in the U.S. or Canada.
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: Ambulance Drop-off State or Province Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
O 1
ID
3/15
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
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: Ambulance Drop-off Postal Zone or ZIP Code
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
O 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: Ambulance Drop-off 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
O 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
O 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: Ambulance Drop-off Country Subdivision Code
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds

SVD - LINE ADJUDICATION INFORMATION

X12 Name:
Service Line Adjudication
X12 Purpose:
To convey service line adjudication information for coordination of benefits between the initial payers of a health care claim and all subsequent payers
X12 Set Notes:
NOTE: SVD01 identifies the payer which adjudicated the corresponding service line and must match DE 67 in the NM109 position 325 for the payer.
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:
Loop ID 2430 conveys information demonstrating how this line was adjudicated by both the submitting payer and other payers who have previously adjudicated the line.

Loop 2430 and the related 2320 loop are linked using the value reported in Loop 2320 SBR01 and Loop 2430 SVD01.

Loop 2320 SBR06 identifies to the receiver whether the respective iteration of Loop ID 2320 was adjudicated by the submitting plan or an Other Payer.

When SBR06 = 1, the payer and adjudication information related to this iteration of Loop ID 2320 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 SBR06 = 6, the payer and adjudication information related to this iteration of Loop ID 2320 and 2430 represents the adjudication results of the submitting payer.
TR3 Example:
SVD✱43✱55✱HC:84550✱✱3~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
67
Identification Code
M 1
AN
2/80
Code identifying a party or other code
SEMANTIC: SVD01 is the payer identification code.
INDUSTRY NAME: Other Payer Primary Identifier
This identifier indicates the payer responsible for the reimbursement described in this iteration of the 2430 loop. The identifier indicates the Other Payer by matching the appropriate Other Payer Primary Identifier (Loop ID-2330B, element NM109).
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
Zero "0" is an acceptable value for this element.
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.
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
ER
Jurisdiction Specific Procedure and Supply Codes
CODE SOURCE: 576: Workers Compensation Specific Procedure and Supply Codes
HC
Health Care Financing Administration Common Procedural Coding System (HCPCS) Codes
Because the AMA's CPT codes are also level 1 HCPCS codes, they are reported under HC.
CODE SOURCE: 130: Healthcare Common Procedure Coding System
WK
Advanced Billing Concepts (ABC) Codes
CODE SOURCE: 843: Advanced Billing Concepts (ABC) Codes
Required
3-2
234
Product/Service ID
M 1
AN
1/48
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 a modifier clarifies or improves the reporting accuracy of the associated procedure code. This is the first procedure code modifier. If not required by this implementation guide, do not send.
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 a second modifier clarifies or improves the reporting accuracy of the associated procedure code. If not required by this implementation guide, do not send.
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 a third modifier clarifies or improves the reporting accuracy of the associated procedure code. If not required by this implementation guide, do not send.
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 a fourth modifier clarifies or improves the reporting accuracy of the associated procedure code. If not required by this implementation guide, do not send.
Not Used
3-7
352
Description
O 1
AN
1/80
Not Used
3-8
234
Product/Service ID
O 1
AN
1/48
Not Used
4
234
Product/Service ID
O 1
AN
1/48
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. This is the number of paid units from the remittance advice. When paid units are not present on the remittance advice, use the original billed units.
Situational
6
554
Assigned Number
O 1
N
1/6
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 or Unbundled 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
1033
Claim Adjustment Group Code
M 1
ID
1/2
Code identifying the general category of payment adjustment
CODE
DEFINITION
CO
Contractual Obligations
OA
Other adjustments
PI
Payor Initiated Reductions
PR
Patient Responsibility
Required
2
1034
Claim Adjustment Reason Code
M 1
ID
1/5
Code identifying the detailed reason the adjustment was made
INDUSTRY NAME: Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Required
3
782
Monetary Amount
M 1
R
1/18
Monetary amount
SEMANTIC: CAS03 is the amount of adjustment.
INDUSTRY NAME: Adjustment Amount
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
O 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
See CODE SOURCE 139: Claim Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Situational
6
782
Monetary Amount
O 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
Situational
7
380
Quantity
O 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
O 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
See CODE SOURCE 139: Claim Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Situational
9
782
Monetary Amount
O 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
Situational
10
380
Quantity
O 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
O 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
See CODE SOURCE 139: Claim Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Situational
12
782
Monetary Amount
O 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
Situational
13
380
Quantity
O 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
O 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
See CODE SOURCE 139: Claim Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Situational
15
782
Monetary Amount
O 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
Situational
16
380
Quantity
O 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
O 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
See CODE SOURCE 139: Claim Adjustment Reason Code
CODE SOURCE 139: Claim Adjustment Reason Code
Situational
18
782
Monetary Amount
O 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
Situational
19
380
Quantity
O 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✱20120503~
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:
  1. In the judgment of the provider, this is the remaining amount to be paid after adjudication by the Other Payer referenced in SVD01 of this iteration of Loop ID-2430.
  2. 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 to qualify amount
CODE
DEFINITION
EAF
Amount Owed
Required
2
782
Monetary Amount
M 1
R
1/18
Monetary amount
INDUSTRY NAME: Remaining Patient Liability
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

837 Post-adjudicated Claims Data Reporting: Professional (005010X298, 005010X298A1)

OCTOBER 2016

Copyright © 2008-16, X12 Incorporated, Format © 2008-16 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: Professional Implementation Guide describes the use of the X12 Health Care Claim (837) transaction set for reporting health care professional 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

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

Trading partners define their specific transport requirements separately. Neither ASC X12 standards nor TR3s define transport requirements.


1.1 Implementation Purpose and Scope

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 section 1.5 Business Terminology of this implementation guide.

This technical report defines uniform data requirements and content of the ASC X12N Health Care Claims (837) transaction when it is used to report post adjudicated professional claims data.

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 2003 ASC X12 standards, referred to as Version 5, Release 1, Sub-release 0 (005010).

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

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.


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 if the transaction was not transmitted back to the sender of the original transaction. This implementation guide does not set specific response time parameters for these activities.

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 ASC X12 implementation guide explains how to use ASC X12 transaction sets to meet a single defined business purpose. The following diagrams, current as of version 005010, depict the business functions supported by the ASC X12 health care implementation guide. The intent of these diagrams is to represent the possible exchanges between trading partners using these implementation guides. Trading partners include entities that administer part or all of a health plan, fund the plan and enroll members, and provide the health care services.

  1. Health Care Claim and Encounter plus Additional Support Information
     005010X222 837 Health Care Claim: Professional
     005010X223 837 Health Care Claim: Institutional
     005010X224 837 Health Care Claim: Dental
     005010X214 277 Health Care Claim Acknowledgment
  2. Health Care Claim Payment
     005010X221 835 Health Care Claim Payment/Advice
  3. Post Adjudicated Claim Data Reporting (PACDR)
     005010X298 837 Post Adjudicated Claim Data Reporting: Professional
     005010X299 837 Post Adjudicated Claim Data Reporting: Institutional
     005010X300 837 Post Adjudicated Claim Data Reporting: Dental

This section and the associated diagram does not limit or prohibit other means of payer's receiving claims (for example, provider submitted paper claims or claims received directly from subscribers or patients) from being represented in these transactions. The intent is only to show the data flow when EDI transactions are used starting with the original data source to the final destination. The implementation guide was developed with the understanding a payer will not always have the full 837 data set available to be forwarded in a Post Adjudciation transaction.


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~ 
SV1*HC:A*100*UN*1***1**Y**N*N~
835 to provider:
CLP*1CL*1*100*75**12*2011092600001~ 
SVC*HC:A*100*75**1~ 
CAS*CO*45*25~
Payer Claim:
CLM*1CL*100***11:B:1~ 
REF*F8*2011092600001~ 
SV1*HC:A*100*UN*1***1**Y**N*N~ 
SVD*<Related SBR01 value>*75*HC: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~ 
SV1*HC:A*100**1***1**Y**N*N~
835 to provider:
CLP*2CL*1*100*50**12*2011092600002~ 
SVC*HC:B*100*50**1*HC:A~ 
CAS*CO*45*50~
Payer Claim:
CLM*2CL*100***11:B:1~ 
REF*F8*2011092600002~ 
SV1*HC:A*100*UN*1***1**Y**N*N~ 
SVD*<Related SBR01 value>*50*HC: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~ 
SV1*HC:A*300*UN*3***1**Y**N*N~ 
DTP*472*RD8*20101231-20110102~
835 to provider:

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

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

Payer Claim:
CLM*3CL*300***11:B:1~ 
REF*F8*2011092600003~ 
SV1*HC:A*300*UN*3***1**Y**N*N~ 
DTP*472*RD8*20101231-20110102~ 
SVD*<Related SBR01 value>*75*HC:A**1~ 
CAS*CO*45*25~ 
SVD*<Related SBR01 value>*150*HC: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~ 
SV1*HC:A*100*UN*1***1**Y**N*N~ 
SV1*HC:B*100*UN*1***1**Y**N*N~
835 to provider:

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

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

Payer Claim:

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

SV1*HC:B*100*UN*1*11**1**Y**N*N~ SVD*<Related SBR01 value>*0*HC: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~ SV1*HC:A*100*UN*1*11**1**Y**N*N~ DTP*472*D8*20101231~

SV1*HC:B*120*UN*1*11**1**Y**N*N~ DTP*472*D8*20110101~

835 to provider:

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

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

Payer Claim:

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

CLM*5CL*120***11:B:1~ REF*F8*2011092600015~ SV1*HC:B*120*UN*1*11**1**Y**N*N~ DTP*472*D8*20110101~ SVD*<Related SBR01 value>*60*HC: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*5CL*220***11:B:1~CLM*6CL*200***11:B:1~ 
SV1*HC:A*200*UN*1***1**Y**N*N~ 
DTP*472*D8*20110926~
835 to provider:
CLP*6CL*1*200*120**12*2011092600006~ 
SVC*HC:B*200*60***HC:A~ 
CAS*CO*45*140~ 
SVC*HC:C*0*60***HC:A~ 
CAS*OA*94*-60~
Payer Claim:

CLM*6CL*200***11:B:1~ REF*F8*2011092600006~ SV1*HC:A*200*UN*1***1**Y**N*N~ SVD*<Related SBR01 value>*60*HC:B**1*HC:A~ CAS*CO*45*140~

SVD*<Related SBR01 value>*60*HC:C**1*HC: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.

Other Payer Level Subscriber/Patient Information (Loops 2330A and 2330C)
Subscriber and Patient information reported at this level will need to be viewed in two different ways. The difference is based upon whether this is the information related to the submitting payer, or Coordination of Benefits information extracted from the claim submitted to the payer requesting payment.

Submitting Payer (Identified by SBR06 = 6)
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 (Identified by SBR06 = 1)
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 SV102.

2) Claim Payment Amounts
Balancing of claim payment information is done payer by payer. For a given payer that has service line adjudication data, the sum of all line level payment amounts (Loop ID-2430 SVD02) less any claim level adjustment amounts (Loop ID-2320 CAS adjustments) must balance to the claim level payment amount (Loop ID-2320 AMT02).

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

Expressed as a calculation for given payer that has service line adjudication data: {Loop ID-2320 AMT02 payer payment} = {sum of Loop ID-2430 SVD02 payment amounts} minus {sum of Loop ID-2320 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 SV102 Line Item Charge Amount}

Example:

Line 1 Charge = 80.00 Line 1 Payment = 70.00 Line 1 Adjustment = 10.00
Line 2 Charge = 20.00 Line 2 Payment = 15.00 Line 2 Adjustment = 5.00 Line 1 adjustment ($10) plus Line 1 payment ($70) = Line 1 charge ($80). Line 2 adjustment ($5) plus Line 2 payment ($15) = Line 2 charge ($20)

1.5 Business Terminology

This section defines terms used in this implementation guide that are not included in the Data Dictionary Appendix. See the Data Dictionary Appendix for additional terms and definitions.

All Payer Claims Database
The APCD is a database, typically created by state mandate, generally comprised of medical, pharmacy, and dental claims, and information from the member eligibility, provider, and product files encompassing fully-insured, self-insured, Medicare, and Medicaid data.

Bundling
Bundling occurs when a provider reports two or more procedure codes, but the payer adjudicates them together using a single (possibly different) procedure code.

Claim
For the purposes of this implementation guide, claim is intended to be an all-inclusive term to represent adjudicated claims and encounter reporting. When there are differences, they are specifically noted.

Encounter
For the purposes of this implementation guide, the following definitions apply:

  1. When the word "encounter" is used by itself: pre-adjudicated health care service information submitted by the provider to the payer for the purpose of reporting the service rather than requesting payment.
  2. When an encounter is referred to as a "Medicare Encounter", "Medicaid Encounter" or "Medicare/Medicaid encounter": post adjudicated claim data reported from the payer to the Medicare or Medicaid agency.

Health Insurance Exchange
As defined by the Affordable Care Act a Health Insurance Exchange is an organization that provides a marketplace for health insurance coverage options to affordable quality health care and other related functions.

Payer
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.

Payer's System
Reference to the "payer's system" is referenced throughout this implementation guide. The reference is intended to broadly represent the various databases within a payer environment. It is intended to include any data stored in a normalized, retrievable structure. It is not intended to include storage of raw transaction data that is not parsed and maintained in a normalized, retreivable database.

Provider
A provider is either a person or organizational entity who has either provided or participated in some aspect of the service(s) described in the transaction. Specific types of providers are identified in this implementation guide (for example billing provider, referring provider).

Regulatory Agency
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.

Transmission Intermediary
A transmission intermediary is any entity that handles the transaction between the payer (originator of the transmission) and the reporting destination. The term 'intermediary' is not referring to a Part A Medicare contractor.

Unbundling
Unbundling occurs when a provider submits one procedure code which the payer adjudicates and reports back as two or more different procedure codes.


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 ASC 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.7.2 Health Care Claim: Professional (837)

Information in the Health Care Claim: Professional (837) transaction is generated by the provider's billing system. Some of the information included in the Post Adjudicated Claims Data Reporting 837 must be reported as received in the claim submitted by the provider.


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 HIPAA Role in Implementation Guides

Administrative Simplification provisions of the Health Insurance Portability and Accountability Act of 1996 (PL 104-191 - known as HIPAA) direct the Secretary of Health and Human Services to adopt standards for transactions to enable health information to be exchanged electronically and to adopt specifications for implementing each standard.

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 HIPAA standard. Should the Secretary adopt this implementation guide as a standard, the Secretary will establish compliance dates for its use by HIPAA covered entities.


2. Transaction Set

NOTE
See Appendix B, Nomenclature, to review the transaction set structure, including descriptions of segments, data elements, levels, and loops.


2.1 Presentation Examples

The ASC 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:

2.3 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.

2.4 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.

The first form is "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 or requested by the receiver, transmission of this data is solely at the sender's discretion.

The alternative form is "Required when <explicit condition statement>. If not required by this implementation guide, do not send." The data qualified by such a situational rule cannot be sent except as described in the explicit condition statement.


2.2.1.1 Transaction Compliance Related to Industry Usage

A transmitted transaction complies with an implementation guide when it satisfies the requirements as defined within the implementation guide. 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.

Required

Business condition: N/A

Item is Transaction complies with implementation guide?
Sent Yes
Not Sent No
Not Used

Business condition: N/A

Item is Transaction complies with implementation guide?
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.

Business Condition is Item is Transaction complies with implementation guide?
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.

Business Condition is Item is Transaction complies with implementation guide?
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 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 ASC X12 Examples Web Site at http://examples.x12.org. The ASC X12 Examples Web Site provides convenient access to examples of ASC X12 transaction transmissions, including the data stream and a description of the associated scenario.


Appendix A. External Code Sources

5 Countries, Currencies and Funds

SIMPLE DATA ELEMENT/CODE REFERENCES

26, 100, 1715, 66/38, 235/CH, 955/SP

SOURCE

Codes for Representation of Names of Countries, ISO 3166-(Latest Release)
Codes for Representation of Currencies and Funds, ISO 4217-(Latest Release)

AVAILABLE FROM

American National Standards Institute
25 West 43rd Street, 4th Floor
New York, NY 10036

ABSTRACT

Part 1 (Country codes) of the ISO 3166 international standard establishes codes that represent the current names of countries, dependencies, and other areas of special geopolitical interest, on the basis of lists of country names obtained from the United Nations. Part 2 (Country subdivision codes) establishes a code that represents the names of the principal administrative divisions, or similar areas, of the countries, etc. included in Part 1. Part 3 (Codes for formerly used names of countries) establishes a code that represents non-current country names, i.e., the country names deleted from ISO 3166 since its first publication in 1974. Most currencies are those of the geopolitical entities that are listed in ISO 3166 Part 1, Codes for the Representation of Names of Countries. The code may be a three-character alphabetic or three-digit numeric. The two leftmost characters of the alphabetic code identify the currency authority to which the code is assigned (using the two character alphabetic code from ISO 3166 Part 1, if applicable). The rightmost character is a mnemonic derived from the name of the major currency unit or fund. For currencies not associated with a single geographic entity, a specially-allocated two-character alphabetic code, in the range XA to XZ identifies the currency authority. The rightmost character is derived from the name of the geographic area concerned, and is mnemonic to the extent possible. The numeric codes are identical to those assigned to the geographic entities listed in ISO 3166 Part 1. The range 950-998 is reserved for identification of funds and currencies not associated with a single entity listed in ISO 3166 Part 1.

22 States and Provinces

SIMPLE DATA ELEMENT/CODE REFERENCES

156, 66/SJ, 235/A5, 771/009

SOURCE

U.S. Postal Service or
Canada Post or
Bureau of Transportation Statistics

AVAILABLE FROM

The U.S. state codes may be obtained from:
U.S. Postal Service
National Information Data Center
P.O. Box 2977
Washington, DC 20013
www.usps.gov
The Canadian province codes may be obtained from:
http://www.canadapost.ca
The Mexican state codes may be obtained from:
www.bts.gov/ntda/tbscd/mex-states.html

ABSTRACT

Provides names, abbreviations, and two character codes for the states, provinces and sub-country divisions as defined by the appropriate government agency of the United States, Canada, and Mexico.

41 GS1 US Global Trade Item Number (GTIN)

SIMPLE DATA ELEMENT/CODE REFERENCES

438, 766, 88/UC, 88/UP, 235/AV, 235/EN, 235/EO, 235/UC, 235/UJ, 235/UK, 235/UL, 235/UP, 235/UR, 559/FD

SOURCE

GS1 US Solutions Center

AVAILABLE FROM

GS1 US, Inc.
7887 Washington Village Drive, Suite 300
Dayton, OH 45459

ABSTRACT

The GS1 Global Trade Item Number (GTIN) is a globally unique number for the identification of products and services. The Universal Product Code (U.P.C.) encodes a 12-digit GTIN. The identification number may be 8, 12, 13 or 14 digits in length using the GTIN EAN/UCC-8, GTIN UCC-12, GTIN EAN/UCC-13, and GTIN EAN/UCC-14 data structures respectively. The GTIN EAN/UCC-8 comprises (from left to right) a GTIN EAN/UCC-8 Prefix, Company and Item Reference, and a Check Digit. The GTIN UCC-12 comprises (from left to right) a GS1 US Company Prefix, an Item Reference, and a Check Digit. The GTIN EAN/UCC-13 comprises (from left to right) a GS1 Company Prefix, an Item Reference, and a Check Digit. The GTIN EAN/UCC-14 comprises (from left to right) an Indicator Digit, a GS1 Company Prefix, an Item Reference, and a Check Digit. Its Application Identifier (AI) is '01'. Some existing EDI Codes make specific assumptions about the construction of the GTIN, including eliminating certain digits. A specific GTIN may not conform to these construction assumptions. A GTIN must be used in its entirety to ensure uniqueness.There also exist EDI codes related to a GTIN for coupons, product variants and additional product identification.

51 ZIP Code

SIMPLE DATA ELEMENT/CODE REFERENCES

116, 66/16, 309/PQ, 309/PR, 309/PS, 771/010

SOURCE

National ZIP Code and Post Office Directory, Publication 65
The USPS Domestic Mail Manual

AVAILABLE FROM

U.S Postal Service
Washington, DC 20260
New Orders
Superintendent of Documents
P.O. Box 371954
Pittsburgh, PA 15250-7954

ABSTRACT

The ZIP Code is a geographic identifier of areas within the United States and its territories for purposes of expediting mail distribution by the U.S. Postal Service. It is five or nine numeric digits. The ZIP Code structure divides the U.S. into ten large groups of states. The leftmost digit identifies one of these groups. The next two digits identify a smaller geographic area within the large group. The two rightmost digits identify a local delivery area. In the nine-digit ZIP Code, the four digits that follow the hyphen further subdivide the delivery area. The two leftmost digits identify a sector which may consist of several large buildings, blocks or groups of streets. The rightmost digits divide the sector into segments such as a street, a block, a floor of a building, or a cluster of mailboxes. The USPS Domestics Mail Manual includes information on the use of the new 11-digit zip code.

130 Healthcare Common Procedure Coding System

SIMPLE DATA ELEMENT/CODE REFERENCES

235/HC, 1270/BO, 1270/BP

SOURCE

Healthcare Common Procedure Coding System

AVAILABLE FROM

Centers for Medicare & Medicaid Services (CMS)
7500 Security Boulevard
Baltimore, MD 21244

ABSTRACT

HCPCS is Centers for Medicare & Medicaid Services (CMS) coding scheme to group procedures performed for payment to providers.

131 International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)

SIMPLE DATA ELEMENT/CODE REFERENCES

128/ICD, 235/DX, 235/ID, 1270/BF, 1270/BJ, 1270/BK, 1270/BN, 1270/BQ, 1270/BR, 1270/DD, 1270/PR, 1270/SD, 1270/TD, 1270/AAU, 1270/AAV, 1270/AAX

SOURCE

International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM), Volumes I, II and III

AVAILABLE FROM

Superintendent of Documents
U.S. Government Printing Office
P.O. Box 371954
Pittsburgh, PA 15250

ABSTRACT

The International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM), Volumes I, II (diagnoses) and III (procedures) describes the classification of morbidity and mortality information for statistical purposes and for the indexing of healthcare records by diseases and procedures.

132 National Uniform Billing Committee (NUBC) Codes

SIMPLE DATA ELEMENT/CODE REFERENCES

235/NU, 235/RB, 1270/BE, 1270/BG, 1270/BH, 1270/BI, 1270/NUB

SOURCE

National Uniform Billing Data Element Specifications

AVAILABLE FROM

National Uniform Billing Committee
American Hospital Association
One North Franklin
Chicago, IL 60606

ABSTRACT

Revenue codes are a classification of hospital charges in a standard grouping that is controlled by the National Uniform Billing Committee.

139 Claim Adjustment Reason Code

SIMPLE DATA ELEMENT/CODE REFERENCES

1034

SOURCE

National Health Care Claim Payment/Advice Committee Bulletins

AVAILABLE FROM

Blue Cross and Blue Shield Association
Health Information Technology Department
225 N Michigan Avenue
Chicago, IL 60601-7680

ABSTRACT

Bulletins describe standard codes and messages that detail the reason why an adjustment was made to a health care claim payment by the payer.

235 Claim Frequency Type Code

SIMPLE DATA ELEMENT/CODE REFERENCES

1325

SOURCE

National Uniform Billing Data Element Specifications Type of Bill Last Position

AVAILABLE FROM

National Uniform Billing Committee
American Hospital Association
One North Franklin
Chicago, IL 60606

ABSTRACT

A variety of codes explaining the frequency of different Types of Bills (for example, Replacement Claims).

237 Place of Service Codes for Professional Claims

SIMPLE DATA ELEMENT/CODE REFERENCES

1332/B

SOURCE

Place of Service Codes for Professional Claims

AVAILABLE FROM

Centers for Medicare & Medicaid Services
CMSO, Mail Stop S2-01-16
7500 Security Boulevard
Baltimore, MD 21244-1850

ABSTRACT

The Centers for Medicare & Medicaid Services develops place of service codes to identify the location where health care services are performed.

240 National Drug Code by Format

SIMPLE DATA ELEMENT/CODE REFERENCES

235/N1, 235/N2, 235/N3, 235/N4, 235/N5, 235/N6, 1270/NDC

SOURCE

Drug Establishment Registration and Listing Instruction Booklet

AVAILABLE FROM

Federal Drug Listing Branch HFN-315
5600 Fishers Lane
Rockville, MD 20857

ABSTRACT

Publication includes manufacturing and labeling information as well as drug packaging sizes.

245 National Association of Insurance Commissioners (NAIC) Code

SIMPLE DATA ELEMENT/CODE REFERENCES

128/NF

SOURCE

National Association of Insurance Commissioners Company Code List Manual

AVAILABLE FROM

National Association of Insurance Commission Publications Department
12th Street, Suite 1100
Kansas City, MO 64105-1925

ABSTRACT

Codes that uniquely identify each insurance company.

513 Home Infusion EDI Coalition (HIEC) Product/Service Code List

SIMPLE DATA ELEMENT/CODE REFERENCES

235/IV, 1270/HO

SOURCE

Home Infusion EDI Coalition (HIEC) Coding System

AVAILABLE FROM

HIEC Chairperson
HIBCC (Health Industry Business Communications Council)
5110 North 40th Street
Suite 250
Phoenix, AZ 85018

ABSTRACT

This list contains codes identifying home infusion therapy products/services.

537 Centers for Medicare & Medicaid Services National Provider Identifier

SIMPLE DATA ELEMENT/CODE REFERENCES

66/XX, 128/HPI

SOURCE

National Provider System

AVAILABLE FROM

Centers for Medicare & Medicaid Services
Office of Financial Management
Division of Provider/Supplier Enrollment
C4-10-07
7500 Security Boulevard
Baltimore, MD 21244-1850

ABSTRACT

The Centers for Medicare & Medicaid Services is developing the National Provider Identifier (NPI), which has been proposed as the standard unique identifier for each health care provider under the Health Insurance Portability and Accountability Act of 1996.

540 Centers for Medicare and Medicaid Services PlanID

SIMPLE DATA ELEMENT/CODE REFERENCES

66/XV, 128/ABY

SOURCE

PlanID Database

AVAILABLE FROM

Centers for Medicare and Medicaid Services
Center of Beneficiary Services, Membership Operations Group
Division of Benefit Coordination
S1-05-06
7500 Security Boulevard
Baltimore, MD 21244-1850

ABSTRACT

The Centers for Medicare and Medicaid Services has joined with other payers to develop a unique national payer identification number. The Centers for Medicare and Medicaid Services is the authorizing agent for enumerating payers through the services of a PlanID Registrar. It may also be used by other payers on a voluntary basis.

576 Workers Compensation Specific Procedure and Supply Codes

SIMPLE DATA ELEMENT/CODE REFERENCES

235/ER

SOURCE

IAIABC Jurisdiction Medical Bill Report Implementation Guide

AVAILABLE FROM

IAIABC EDI Implementation Manager
International Association of Industrial Accident Boards and Commissions
8643 Hauses - Suite 200
87th Parkway
Shawnee Mission, KS 66215

ABSTRACT

The IAIABC Jurisdiction Medical Bill Report Implementation Guide describes the requirements for submitting and the data contained within a jurisdiction medical report. The Implementation Guide includes: Reporting scenarios, data definitions, trading partner requirements tables, reference to industry codes, and IAIABC maintained code lists.

641 Condition Code List

SIMPLE DATA ELEMENT/CODE REFERENCES

1270/BG

SOURCE

Condition Code List

AVAILABLE FROM

EDI Administrator
Dun & Bradstreet Corp.
100 Locust Avenue
Berkely Heights, NJ 07922

ABSTRACT

Provides condition codes and descriptions relating to business entities or individuals involved in business entities.

682 Health Care Provider Taxonomy

SIMPLE DATA ELEMENT/CODE REFERENCES

128/PXC, 1270/68

SOURCE

The National Uniform Claim Committee

AVAILABLE FROM

The National Uniform Claim Committee
c/o American Medical Association
515 North State Street
Chicago, IL 60610

ABSTRACT

Codes defining the health care service provider type, classification, and area of specialization.

843 Advanced Billing Concepts (ABC) Codes

SIMPLE DATA ELEMENT/CODE REFERENCES

235/WK, 1270/CAH

SOURCE

The CAM and Nursing Coding Manual

AVAILABLE FROM

Alternative Link
6121 Indian School Road NE
Suite 131
Albuquerque, NM 87110

ABSTRACT

The manual contains the Advanced Billing Concepts (ABC) codes, descriptive terms and identifiers for reporting complementary or alternative medicine, nursing, and other integrative health care procedures.

897 International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)

SIMPLE DATA ELEMENT/CODE REFERENCES

128/I10, 235/DC, 1270/ABF, 1270/ABJ, 1270/ABK, 1270/ABN, 1270/ABU, 1270/ABV, 1270/ADD, 1270/APR, 1270/ASD, 1270/ATD

SOURCE

International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)

AVAILABLE FROM

OCD/Classifications and Public Health Data Standards
National Center for Health Statistics
3311 Toledo Road
Hyattsville, MD 20782

ABSTRACT

The International Classicication of Diseases, 10th Revision, Clinical Modification (ICD-10-CM), describes the classification of morbidity and mortality information for statistical purposes and for the indexing of healthcare records by diseases.

932 Universal Postal Codes

SIMPLE DATA ELEMENT/CODE REFERENCES

116

SOURCE

Universal Postal Union website

AVAILABLE FROM

International Bureau of the Universal Postal Union
POST*CODE
Case postale 13
3000 BERNE 15 Switzerland

ABSTRACT

The postcode is the fundamental, essential element of an address. A unique, universal identifier, it unambiguously identifies the addressee's locality and assists in the transmission and sorting of mail items. At present, 105 UPU member countries use postcodes as part of their addressing systems.


B.1.1 Interchange and Application Control Structures

Appendix B is provided as a reference to the X12 syntax, usage, and related information. It is not a full statement of Interchange and Control Structure rules. The full X12 Interchange and Control Structures and other rules (X12.5, X12.6, X12.59, X12 dictionaries, other X12 standards and official documents) apply unless specifically modified in the detailed instructions of this implementation guide (see Section B.1.1.3.1.2 for an example of such a modification).


B.1.1.1 Interchange Control Structure

The transmission of data proceeds according to very strict format rules to ensure the integrity and maintain the efficiency of the interchange. Each business grouping of data is called a transaction set. For instance, a group of benefit enrollments sent from a sponsor to a payer is considered a transaction set.

Each transaction set contains groups of logically related data in units called segments. For instance, the N4 segment used in the transaction set conveys the city, state, ZIP Code, and other geographic information. A transaction set contains multiple segments, so the addresses of the different parties, for example, can be conveyed from one computer to the other. An analogy would be that the transaction set is like a freight train; the segments are like the train's cars; and each segment can contain several data elements the same as a train car can hold multiple crates.

The sequence of the elements within one segment is specified by the ASC X12 standard as well as the sequence of segments in the transaction set. In a more conventional computing environment, the segments would be equivalent to records, and the elements equivalent to fields.

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

The interchange header and trailer segments envelop one or more functional groups or interchange-related control segments and perform the following functions:

  1. Define the data element separators and the data segment terminator.
  2. Identify the sender and receiver.
  3. Provide control information for the interchange.
  4. Allow for authorization and security information.

B.1.1.2.1 Basic Structure

A data element corresponds to a data field in data processing terminology. A data segment corresponds to a record in data processing terminology. The data segment begins with a segment ID and contains related data elements. A control segment has the same structure as a data segment; the distinction is in the use. The data segment is used primarily to convey user information, but the control segment is used primarily to convey control information and to group data segments.


B.1.1.2.2 Basic Character Set

The section that follows is designed to have representation in the common character code schemes of EBCDIC, ASCII, and CCITT International Alphabet 5. The ASC X12 standards are graphic-character-oriented; therefore, common character encoding schemes other than those specified herein may be used as long as a common mapping is available. Because the graphic characters have an implied mapping across character code schemes, those bit patterns are not provided here.

The basic character set of this standard, shown in Figure B.2., Basic Character Set, includes those selected from the uppercase letters, digits, space, and special characters as specified below.

Figure B.2 - Basic Character Set

A...Z 0...9 ! " & ' ( ) * +
, - . / : ; ? = " " (space)

B.1.1.2.3 Extended Character Set

An extended character set may be used by negotiation between the two parties and includes the lowercase letters and other special characters as specified in Figure B.3., Extended Character Set.

Figure B.3 - Extended Character Set

a..z % ~ @ [ ] _ {
} \ | < > & $


Note that the extended characters include several character codes that have multiple graphical representations for a specific bit pattern. The complete list appears in other standards such as CCITT S.5. Use of the USA graphics for these codes presents no problem unless data is exchanged with an international partner. Other problems, such as the translation of item descriptions from English to French, arise when exchanging data with an international partner, but minimizing the use of codes with multiple graphics eliminates one of the more obvious problems.

For implementations compliant with this guide, either the entire extended character set must be acceptable, or the entire extended character set must not be used. In the absence of a specific trading partner agreement to the contrary, trading partners will assume that the extended character set is acceptable. Use of the extended character set allows the use of the "@" character in email addresses within the PER segment. Users should note that characters in the extended character set, as well as the basic character set, may be used as delimiters only when they do not occur in the data as stated in Section B.1.1.2.5.


B.1.1.2.4 Control Characters

Two control character groups are specified; they have restricted usage. The common notation for these groups is also provided, together with the character coding in three common alphabets. In the Matrix B.1., Base Control Set, the column IA5 represents CCITT V.3 International Alphabet 5.


B.1.1.2.4.1 Base Control Set

The base control set includes those characters that will not have a disruptive effect on most communication protocols. These are represented by:

Matrix B.1. Base Control Set

NOTATION NAME EBCDIC ASCII IA5
BEL bell 2F 07 07
HT horizontal tab 05 09 09
LF line feed 25 0A 0A
VT vertical tab 0B 0B 0B
FF form feed 0C 0C 0C
CR carriage return 0D 0D 0D
FS file separator 1C 1C 1C
GS group separator 1D 1D 1D
RS record separator 1E 1E 1E
US unit separator 1F 1F 1F
NL new line 15


The Group Separator (GS) may be an exception in this set because it is used in the 3780 communications protocol to indicate blank space compression.


B.1.1.2.4.2 Extended Control Set

The extended control set includes those that may have an effect on a transmission system. These are shown in Matrix B.2., Extended Control Set.

Matrix B.2. Extended Control Set

NOTATION NAME EBCDIC ASCII IA5
SOH start of header 01 01 01
STX start of text 02 02 02
ETX end of text 03 03 03
EOT end of transmission 37 04 04
ENQ enquiry 2D 05 05
ACK acknowledge 2E 06 06
DC1 device control 1 11 11 11
DC2 device control 2 12 12 12
DC3 device control 3 13 13 13
DC4 device control 4 3C 14 14
NAK negative acknowledge 3D 15 15
SYN synchronous idle 32 16 16
ETB end of block 26 17 17


The Group Separator (GS) may be an exception in this set because it is used in the 3780 communications protocol to indicate blank space compression.


B.1.1.2.4.5 Delimiters

A delimiter is a character used to separate two data elements or component elements or to terminate a segment. The delimiters are an integral part of the data.

Delimiters are specified in the interchange header segment, ISA. The ISA segment can be considered in implementations compliant with this guide (see Appendix C, ISA Segment Note 1) to be a 105 byte fixed length record, followed by a segment terminator. The data element separator is byte number 4; the repetition separator is byte number 83; the component element separator is byte number 105; and the segment terminator is the byte that immediately follows the component element separator.

Once specified in the interchange header, the delimiters are not to be used in a data element value elsewhere in the interchange. For consistency, this implementation guide uses the delimiters shown in Matrix B.3., Delimiters, in all examples of EDI transmissions.

Matrix B.3. Delimiters

CHARACTER NAME DELIMITER
* Asterisk Data Element Separator
^ Caret Repetition Separator
: Colon Component Element Separator
~ Tilde Segment Terminator


The delimiters above are for illustration purposes only and are not specific recommendations or requirements. Users of this implementation guide should be aware that an application system may use some valid delimiter characters within the application data. Occurrences of delimiter characters in transmitted data within a data element will result in errors in translation. The existence of asterisks (*) within transmitted application data is a known issue that can affect translation software.


B.1.1.3 Business Transaction Structure Definitions and Concepts

The ASC X12 standards define commonly used business transactions (such as a health care claim) in a formal structure called "transaction sets." A transaction set is composed of a transaction set header control segment, one or more data segments, and a transaction set trailer control segment. Each segment is composed of the following:

  • A unique segment ID
  • One or more logically related data elements each preceded by a data element separator
  • A segment terminator

B.1.1.3.1 Data Element

The data element is the smallest named unit of information in the ASC X12 standard. Data elements are identified as either simple or component. A data element that occurs as an ordinally positioned member of a composite data structure is identified as a component data element. A data element that occurs in a segment outside the defined boundaries of a composite data structure is identified as a simple data element. The distinction between simple and component data elements is strictly a matter of context because a data element can be used in either capacity.

Data elements are assigned a unique reference number. Each data element has a name, description, type, minimum length, and maximum length. For ID type data elements, this guide provides the applicable ASC X12 code values and their descriptions or references where the valid code list can be obtained.

A simple data element within a segment may have an attribute indicating that it may occur once or a specific number of times more than once. The number of permitted repeats are defined as an attribute in the individual segment where the repeated data element occurs.

Each data element is assigned a minimum and maximum length. The length of the data element value is the number of character positions used except as noted for numeric, decimal, and binary elements.

The data element types shown in Matrix B.4., Data Element Types, appear in this implementation guide.

Matrix B.4. Data Element Types

SYMBOL TYPE
Nn Numeric
R Decimal
ID Identifier
AN String
DT Date
TM Time
B Binary


The data element minimum and maximum lengths may be restricted in this implementation guide for a compliant implementation. Such restrictions may occur by virtue of the allowed qualifier for the data element or by specific instructions regarding length or format as stated in this implementation guide.


B.1.1.3.1.1 Numeric

A numeric data element is represented by one or more digits with an optional leading sign representing a value in the normal base of 10. The value of a numeric data element includes an implied decimal point. It is used when the position of the decimal point within the data is permanently fixed and is not to be transmitted with the data.

This set of guides denotes the number of implied decimal positions. The representation for this data element type is "Nn" where N indicates that it is numeric and n indicates the number of decimal positions to the right of the implied decimal point.

If n is 0, it need not appear in the specification; N is equivalent to N0. For negative values, the leading minus sign (-) is used. Absence of a sign indicates a positive value. The plus sign (+) must not be transmitted.

EXAMPLE
A transmitted value of 1234, when specified as numeric type N2, represents a value of 12.34.

Leading zeros must be suppressed unless necessary to satisfy a minimum length requirement. The length of a numeric type data element does not include the optional sign.


B.1.1.3.1.2 Decimal

A decimal data element may contain an explicit decimal point and is used for numeric values that have a varying number of decimal positions. This data element type is represented as "R."

The decimal point always appears in the character stream if the decimal point is at any place other than the right end. If the value is an integer (decimal point at the right end) the decimal point must be omitted. For negative values, the leading minus sign (-) is used. Absence of a sign indicates a positive value. The plus sign (+) must not be transmitted.

Leading zeros must be suppressed unless necessary to satisfy a minimum length requirement. Trailing zeros following the decimal point must be suppressed unless necessary to indicate precision. The use of triad separators (for example, the commas in 1,000,000) is expressly prohibited. The length of a decimal type data element does not include the optional leading sign or decimal point.

EXAMPLE
A transmitted value of 12.34 represents a decimal value of 12.34.

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

For implementation of this guide under the rules promulgated under the Health Insurance Portability and Accountability Act (HIPAA), decimal data elements in 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 the statement in the preceding paragraph that the decimal point and leading sign, if sent, are not part of the character count.

EXAMPLE
For implementations mandated under HIPAA rules:

  • 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.1.3 Identifier

An identifier data element always contains a value from a predefined list of codes that is maintained by the ASC X12 Committee or some other body recognized by the Committee. Trailing spaces must be suppressed unless they are necessary to satisfy a minimum length. An identifier is always left justified. The representation for this data element type is "ID."


B.1.1.3.1.4 String

A string data element is a sequence of any characters from the basic or extended character sets. The string data element must contain at least one non-space character. The significant characters shall be left justified. Leading spaces, when they occur, are presumed to be significant characters. Trailing spaces must be suppressed unless they are necessary to satisfy a minimum length. The representation for this data element type is "AN."


B.1.1.3.1.5 Date

A date data element is used to express the standard date in either YYMMDD or CCYYMMDD format in which CC is the first two digits of the calendar year, YY is the last two digits of the calendar year, MM is the month (01 to 12), and DD is the day in the month (01 to 31). The representation for this data element type is "DT." Users of this guide should note that all dates within transactions are 8-character dates (millennium compliant) in the format CCYYMMDD. The only date data element that is in format YYMMDD is the Interchange Date data element in the ISA segment and the TA1 segment where the century is easily determined because of the nature of an interchange header.


B.1.1.3.1.6 Time

A time data element is used to express the ISO standard time HHMMSSd..d format in which HH is the hour for a 24 hour clock (00 to 23), MM is the minute (00 to 59), SS is the second (00 to 59) and d..d is decimal seconds. The representation for this data element type is "TM." The length of the data element determines the format of the transmitted time.

EXAMPLE
Transmitted data elements of four characters denote HHMM. Transmitted data elements of six characters denote HHMMSS.


B.1.1.3.1.7 Binary

The binary data element is any sequence of octets ranging in value from binary 00000000 to binary 11111111. This data element type has no defined maximum length. Actual length is specified by the immediately preceding data element. Within the body of a transaction set (from ST to SE) implemented according to this technical report, the binary data element type is only used in the segments Binary Data Segment BIN, and Binary Data Structure BDS. Within those segments, Data Element 785 Binary Data is a string of octets which can assume any binary pattern from hexadecimal 00 to FF, and can be used to send text as well as coded data, including data from another application in its native format. The binary data type is also used in some control and security structures.

Not all transaction sets use the Binary Data Segment BIN or Binary Data Structure BDS.


B.1.1.3.2 Repeating Data Elements

Simple or composite data elements within a segment can be designated as repeating data elements. Repeating data elements are adjacent data elements that occur up to a number of times specified in the standard as number of repeats. The implementation guide may also specify the number of repeats of a repeating data element in a specific location in the transaction that are permitted in a compliant implementation. Adjacent occurrences of the same repeating simple data element or composite data structure in a segment shall be separated by a repetition separator.


B.1.1.3.3 Composite Data Structure

The composite data structure is an intermediate unit of information in a segment. Composite data structures are composed of one or more logically related simple data elements, each, except the last, followed by a sub-element separator. The final data element is followed by the next data element separator or the segment terminator. Each simple data element within a composite is called a component.

Each composite data structure has a unique four-character identifier, a name, and a purpose. The identifier serves as a label for the composite. A composite data structure can be further defined through the use of syntax notes, semantic notes, and comments. Each component within the composite is further characterized by a reference designator and a condition designator. The reference designators and the condition designators are described in Sections B.1.1.3.8 and B.1.1.3.9.

A composite data structure within a segment may have an attribute indicating that it may occur once or a specific number of times more than once. The number of permitted repeats are defined as an attribute in the individual segment where the repeated composite data structure occurs.


B.1.1.3.4 Data Segment

The data segment is an intermediate unit of information in a transaction set. In the data stream, a data segment consists of a segment identifier, one or more composite data structures or simple data elements each preceded by a data element separator and succeeded by a segment terminator.

Each data segment has a unique two- or three-character identifier, a name, and a purpose. The identifier serves as a label for the data segment. A segment can be further defined through the use of syntax notes, semantic notes, and comments. Each simple data element or composite data structure within the segment is further characterized by a reference designator and a condition designator.


B.1.1.3.5 Syntax Notes

Syntax notes describe relational conditions among two or more data segment units within the same segment, or among two or more component data elements within the same composite data structure. For a complete description of the relational conditions, See B.1.1.3.9, Condition Designator.


B.1.1.3.6 Semantic Notes

Simple data elements or composite data structures may be referenced by a semantic note within a particular segment. A semantic note provides important additional information regarding the intended meaning of a designated data element, particularly a generic type, in the context of its use within a specific data segment. Semantic notes may also define a relational condition among data elements in a segment based on the presence of a specific value (or one of a set of values) in one of the data elements.


B.1.1.3.7 Comments

A segment comment provides additional information regarding the intended use of the segment.


B.1.1.3.8 Reference Designator

Each simple data element or composite data structure in a segment is provided a structured code that indicates the segment in which it is used and the sequential position within the segment. The code is composed of the segment identifier followed by a two-digit number that defines the position of the simple data element or composite data structure in that segment.

For purposes of creating reference designators, the composite data structure is viewed as the hierarchical equal of the simple data element. Each component data element in a composite data structure is identified by a suffix appended to the reference designator for the composite data structure of which it is a member. This suffix is prefixed with a hyphen and defines the position of the component data element in the composite data structure.

EXAMPLE

  • The first simple element of the CLP segment would be identified as CLP01.
  • The first position in the SVC segment is occupied by a composite data structure that contains seven component data elements, the reference designator for the second component data element would be SVC01-02.

B.1.1.3.9 Condition Designator

This section provides information about X12 standard conditions designators. It is provided so that users will have information about the general standard. Implementation guides may impose other conditions designators. See implementation guide section 2.1 Presentation Examples for detailed information about the implementation guide Industry Usage requirements for compliant implementation.

Data element conditions are of three types: mandatory, optional, and relational. They define the circumstances under which a data element may be required to be present or not present in a particular segment.

Table B.5. Condition Designator

DESIGNATOR DESCRIPTION
M- Mandatory The designation of mandatory is absolute in the sense that there is no dependency on other data elements. This designation may apply to either simple data elements or composite data structures. If the designation applies to a composite data structure, then at least one value of a component data element in that composite data structure shall be included in the data segment.
O- Optional The designation of optional means that there is no requirement for a simple data element or composite data structure to be present in the segment. The presence of a value for a simple data element or the presence of value for any of the component data elements of a composite data structure is at the option of the sender.
X- Relational Relational conditions may exist among two or more simple data elements within the same data segment based on the presence or absence of one of those data elements (presence means a data element must not be empty). Relational conditions are specified by a condition code (see table below) and the reference designators of the affected data elements. A data element may be subject to more than one relational condition. The definitions for each of the condition codes used within syntax notes are detailed below:
CONDITION CODE DEFINITION
P- Paired or Multiple If any element specified in the relational condition is present, then all of the elements specified must be present.
R- Required At least one of the elements specified in the condition must be present.
E- Exclusion Not more than one of the elements specified in the condition may be present.
C- Conditional If the first element specified in the condition is present, then all other elements must be present. However, any or all of the elements not specified as the first element in the condition may appear without requiring that the first element be present. The order of the elements in the condition does not have to be the same as the order of the data elements in the data segment.
L- List Conditional If the first element specified in the condition is present, then at least one of the remaining elements must be present. However, any or all of the elements not specified as the first element in the condition may appear without requiring that the first element be present. The order of the elements in the condition does not have to be the same as the order of the data elements in the data segment.

B.1.1.3.10 Absence of Data

Any simple data element that is indicated as mandatory must not be empty if the segment is used. At least one component data element of a composite data structure that is indicated as mandatory must not be empty if the segment is used. Optional simple data elements and/or composite data structures and their preceding data element separators that are not needed must be omitted if they occur at the end of a segment. If they do not occur at the end of the segment, the simple data element values and/or composite data structure values may be omitted. Their absence is indicated by the occurrence of their preceding data element separators, in order to maintain the element's or structure's position as defined in the data segment.

Likewise, when additional information is not necessary within a composite, the composite may be terminated by providing the appropriate data element separator or segment terminator.

If a segment has no data in any data element within the segment (an "empty" segment), that segment must not be sent.


B.1.1.3.11 Control Segments

A control segment has the same structure as a data segment, but it is used for transferring control information rather than application information.


B.1.1.3.11.1 Loop Control Segments

Loop control segments are used only to delineate bounded loops. Delineation of the loop shall consist of the loop header (LS segment) and the loop trailer (LE segment). The loop header defines the start of a structure that must contain one or more iterations of a loop of data segments and provides the loop identifier for this loop. The loop trailer defines the end of the structure. The LS segment appears only before the first occurrence of the loop, and the LE segment appears only after the last occurrence of the loop. Unbounded looping structures do not use loop control segments.


B.1.1.3.11.2 Transaction Set Control Segments

The transaction set is delineated by the transaction set header (ST segment) and the transaction set trailer (SE segment). The transaction set header identifies the start and identifier of the transaction set. The transaction set trailer identifies the end of the transaction set and provides a count of the data segments, which includes the ST and SE segments.


B.1.1.3.11.3 Functional Group Control Segments

The functional group is delineated by the functional group header (GS segment) and the functional group trailer (GE segment). The functional group header starts and identifies one or more related transaction sets and provides a control number and application identification information. The functional group trailer defines the end of the functional group of related transaction sets and provides a count of contained transaction sets.


B.1.1.3.11.4 Relations among Control Segments

The control segment of this standard must have a nested relationship as is shown and annotated in this subsection. The letters preceding the control segment name are the segment identifier for that control segment. The indentation of segment identifiers shown below indicates the subordination among control segments.

GS Functional Group Header, starts a group of related transaction sets.

ST Transaction Set Header, starts a transaction set.

LS Loop Header, starts a bounded loop of data segments but is not part of the loop.

LS Loop Header, starts an inner, nested, bounded loop.

LE Loop Trailer, ends an inner, nested bounded loop.

LE Loop Trailer, ends a bounded loop of data segments but is not part of the loop.

SE Transaction Set Trailer, ends a transaction set.

GE Functional Group Trailer, ends a group of related transaction sets.

More than one ST/SE pair, each representing a transaction set, may be used within one functional group. Also more than one LS/LE pair, each representing a bounded loop, may be used within one transaction set.


B.1.1.3.12 Transaction Set

The transaction set is the smallest meaningful set of information exchanged between trading partners. The transaction set consists of a transaction set header segment, one or more data segments in a specified order, and a transaction set trailer segment. See Figure B.1., Transmission Control Schematic.


B.1.1.3.12.1 Transaction Set Header and Trailer

A transaction set identifier uniquely identifies a transaction set. This identifier is the first data element of the Transaction Set Header Segment (ST). A user assigned transaction set control number in the header must match the control number in the Trailer Segment (SE) for any given transaction set. The value for the number of included segments in the SE segment is the total number of segments in the transaction set, including the ST and SE segments.


B.1.1.3.12.2 Data Segment Groups

The data segments in a transaction set may be repeated as individual data segments or as unbounded or bounded loops.


B.1.1.3.12.3 Repeated Occurrences of Single Data Segments

When a single data segment is allowed to be repeated, it may have a specified maximum number of occurrences defined at each specified position within a given transaction set standard. Alternatively, a segment may be allowed to repeat an unlimited number of times. The notation for an unlimited number of repetitions is ">1."


B.1.1.3.12.4 Loops of Data Segments

Loops are groups of semantically related segments. Data segment loops may be unbounded or bounded.


B.1.1.3.12.4.1 Unbounded Loops

To establish the iteration of a loop, the first data segment in the loop must appear once and only once in each iteration. Loops may have a specified maximum number of repetitions. Alternatively, the loop may be specified as having an unlimited number of iterations. The notation for an unlimited number of repetitions is ">1."

A specified sequence of segments is in the loop. Loops themselves are optional or mandatory. The requirement designator of the beginning segment of a loop indicates whether at least one occurrence of the loop is required. Each appearance of the beginning segment defines an occurrence of the loop.

The requirement designator of any segment within the loop after the beginning segment applies to that segment for each occurrence of the loop. If there is a mandatory requirement designator for any data segment within the loop after the beginning segment, that data segment is mandatory for each occurrence of the loop. If the loop is optional, the mandatory segment only occurs if the loop occurs.


B.1.1.3.12.4.2 Bounded Loops

The characteristics of unbounded loops described previously also apply to bounded loops. In addition, bounded loops require a Loop Start Segment (LS) to appear before the first occurrence and a Loop End Segment (LE) to appear after the last consecutive occurrence of the loop. If the loop does not occur, the LS and LE segments are suppressed.


B.1.1.3.12.5 Data Segments in a Transaction Set

When data segments are combined to form a transaction set, three characteristics are applied to each data segment: a requirement designator, a position in the transaction set, and a maximum occurrence.


B.1.1.3.12.6 Data Segment Requirement Designators

A data segment, or loop, has one of the following requirement designators for health care and insurance transaction sets, indicating its appearance in the data stream of a transmission. These requirement designators are represented by a single character code.

DESIGNATOR DESCRIPTION
M- Mandatory This data segment must be included in the transaction set. (Note that a data segment may be mandatory in a loop of data segments, but the loop itself is optional if the beginning segment of the loop is designated as optional.)
O- Optional The presence of this data segment is the option of the sending party.

B.1.1.3.12.7 Data Segment Position

The ordinal positions of the segments in a transaction set are explicitly specified for that transaction. Subject to the flexibility provided by the optional requirement designators of the segments, this positioning must be maintained.


B.1.1.3.12.8 Data Segment Occurrence

A data segment may have a maximum occurrence of one, a finite number greater than one, or an unlimited number indicated by ">1."


B.1.1.3.13 Functional Group

A functional group is a group of similar transaction sets that is bounded by a functional group header segment and a functional group trailer segment. The functional identifier defines the group of transactions that may be included within the functional group. The value for the functional group control number in the header and trailer control segments must be identical for any given group. The value for the number of included transaction sets is the total number of transaction sets in the group. See Figure B.1., Transmission Control Schematic.


B.1.1.4.1 Interchange Control Structures

Typically, the term "interchange" connotes the ISA/IEA envelope that is transmitted between trading/business partners. Interchange control is achieved through several "control" components. The interchange control number is contained in data element ISA13 of the ISA segment. The identical control number must also occur in data element 02 of the IEA segment. Most commercial translation software products will verify that these two elements are identical. In most translation software products, if these elements are different the interchange will be "suspended" in error.

There are many other features of the ISA segment that are used for control measures. For instance, the ISA segment contains data elements such as authorization information, security information, sender identification, and receiver identification that can be used for control purposes. These data elements are agreed upon by the trading partners prior to transmission. The interchange date and time data elements as well as the interchange control number within the ISA segment are used for debugging purposes when there is a problem with the transmission or the interchange.

Data Element ISA12, Interchange Control Version Number, indicates the version of the ISA/IEA envelope. GS08 indicates the version of the transaction sets contained within the ISA/IEA envelope. The versions are not required to be the same. An Interchange Acknowledgment can be requested through data element ISA14. The interchange acknowlegement is the TA1 segment. Data element ISA15, Test Indicator, is used between trading partners to indicate that the transmission is in a "test" or "production" mode. Data element ISA16, Subelement Separator, is used by the translator for interpretation of composite data elements.

The ending component of the interchange or ISA/IEA envelope is the IEA segment. Data element IEA01 indicates the number of functional groups that are included within the interchange. In most commercial translation software products, an aggregate count of functional groups is kept while interpreting the interchange. This count is then verified with data element IEA01. If there is a discrepancy, in most commercial products, the interchange is suspended. The other data element in the IEA segment is IEA02 which is referenced above.

See the Appendix C, EDI Control Directory, for a complete detailing of the interchange control header and trailer. The authors recommend that when two transactions with different X12 versions numbers are sent in one interchange control structure (multiple functional groups within one ISA/IEA envelope), the Interchange Control version used should be that of the most recent transaction version included in the envelope. For the transmission of HIPAA transactions with mixed versions, this would be a compliant enveloping structure.


B.1.1.4.2 Functional Groups

Control structures within the functional group envelope include the functional identifier code in GS01. The Functional Identifier Code is used by the commercial translation software during interpretation of the interchange to determine the different transaction sets that may be included within the functional group. If an inappropriate transaction set is contained within the functional group, most commercial translation software will suspend the functional group within the interchange. The Application Sender's Code in GS02 can be used to identify the sending unit of the transmission. The Application Receiver's Code in GS03 can be used to identify the receiving unit of the transmission. The functional group contains a creation date (GS04) and creation time (GS05) for the functional group. The Group Control Number is contained in GS06. These data elements (GS04, GS05, and GS06) can be used for debugging purposes. GS08,Version/Release/ Industry Identifier Code is the version/release/sub-release of the transaction sets being transmitted in this functional group.

The Functional Group Control Number in GS06 must be identical to data element 02 of the GE segment. Data element GE01 indicates the number of transaction sets within the functional group. In most commercial translation software products, an aggregate count of the transaction sets is kept while interpreting the functional group. This count is then verified with data element GE01.

See the Appendix C, EDI Control Directory, for a complete detailing of the functional group header and trailer.


B.1.1.4.3 HL Structures

The HL segment is used in several X12 transaction sets to identify levels of detail information using a hierarchical structure, such as relating dependents to a subscriber. Hierarchical levels may differ from guide to guide.

For example, each provider can bill for one or more subscribers, each subscriber can have one or more dependents and the subscriber and the dependents can make one or more claims.

Each guide states what levels are available, the level's usage, number of repeats, and whether that level has subordinate levels within a transaction set.

For implementations compliant with this guide, the repeats of the loops identified by the HL structure shall appear in the hierarchical order specified in BHT01, when those particular hierarchical levels exist. That is, an HL parent loop must be followed by the subordinate child loops, if any, prior to commencing a new HL parent loop at the same hierarchical level.

The following diagram, from transaction set 837, illustrates a typical hierarchy.

The two examples below illustrate this requirement:

Example 1 based on Implementation Guide 811X201:

INSURER

First STATE in transaction (child of INSURER)

First POLICY in transaction (child of first STATE)

First VEHICLE in transaction (child of first POLICY)

Second POLICY in transaction (child of first STATE)

Second VEHICLE in transaction (child of second POLICY)

Third VEHICLE in transaction (child of second POLICY)

Second STATE in transaction (child of INSURER)

Third POLICY in transaction (child of second STATE)

Fourth VEHICLE in transaction (child of third POLICY)


Example 2 based on Implementation Guide 837X141

First PROVIDER in transaction

First SUBSCRIBER in transaction (child of first PROVIDER)

Second PROVIDER in transaction

Second SUBSCRIBER in transaction (child of second PROVIDER)

First DEPENDENT in transaction (child of second SUBSCRIBER)

Second DEPENDENT in transaction (child of second SUBSCRIBER)

Third SUBSCRIBER in transaction (child of second PROVIDER)

Third PROVIDER in transaction

Fourth SUBSCRIBER in transaction (child of third PROVIDER)

Fifth SUBSCRIBER in transaction (child of third PROVIDER

Third DEPENDENT in transaction (child of fifth SUBSCRIBER)


B.1.1.5.1 Interchange Acknowledgment, TA1

The TA1 segment provides the capability for the interchange receiver to notify the sender that a valid envelope was received or that problems were encountered with the interchange control structure. The TA1 verifies the envelopes only. Transaction set-specific verification is accomplished through use of the Functional Acknowledgment Transaction Set, 997. See B.1.1.5.2, Functional Acknowledgment, 997, for more details. The TA1 is unique in that it is a single segment transmitted without the GS/GE envelope structure. A TA1 can be included in an interchange with other functional groups and transactions.

Encompassed in the TA1 are the interchange control number, interchange date and time, interchange acknowledgment code, and the interchange note code. The interchange control number, interchange date and time are identical to those that were present in the transmitted interchange from the trading partner. This provides the capability to associate the TA1 with the transmitted interchange. TA104, Interchange Acknowledgment Code, indicates the status of the interchange control structure. This data element stipulates whether the transmitted interchange was accepted with no errors, accepted with errors, or rejected because of errors. TA105, Interchange Note Code, is a numerical code that indicates the error found while processing the interchange control structure. Values for this data element indicate whether the error occurred at the interchange or functional group envelope.


B.1.1.5.2 Functional Acknowledgment, 997

The Functional Acknowledgment Transaction Set, 997, has been designed to allow trading partners to establish a comprehensive control function as a part of their business exchange process. This acknowledgment process facilitates control of EDI. There is a one-to-one correspondence between a 997 and a functional group. Segments within the 997 can identify the acceptance or rejection of the functional group, transaction sets or segments. Data elements in error can also be identified. There are many EDI implementations that have incorporated the acknowledgment process in all of their electronic communications. The 997 is used as a functional acknowledgment to a previously transmitted functional group.

The 997 is a transaction set and thus is encapsulated within the interchange control structure (envelopes) for transmission.


B.2 Object Descriptors

Object Descriptors (OD) provide a method to uniquely identify specific locations within an implementation guide. There is an OD assigned at every level of the X12N implementation:

  1. Transaction Set
  2. Loop
  3. Segment
  4. Composite Data Element
  5. Component Data Element
  6. Simple Data Element

ODs at the first four levels are coded using X12 identifiers separated by underbars:

Entity Example
1. Transaction Set Identifier plus a unique 2 character value 837Q1
2. Above plus under bar plus Loop Identifier as assigned within an implementation guide 837Q1_2330C
3. Above plus under bar plus Segment Identifier 837Q1_2330C_NM1
4. Above plus Reference Designator plus under bar plus Composite Identifier 837Q1_2400_SV101_C003

The fifth and sixth levels add a name derived from the "Industry Term" defined in the X12N Data Dictionary. The name is derived by removing the spaces.

Entity Example
5. Number 4 above plus composite sequence plus under bar plus name 837Q1_2400_SV101_C00302_ProcedureCode
6. Number 3 above plus Reference Designator plus two under bars plusname 837Q1_2330C_NM109__OtherPayerPatientPrimaryIdentifier

Said in another way, ODs contain a coded component specifying a location in an implementation guide, a separator, and a name portion. For example:

Since ODs are unique across all X12N implementation guides, they can be used for a variety of purposes. For example, as a cross reference to older data transmission systems, like the National Standard Format for health care claims, or to form XML tags for newer data transmission systems.


Appendix D. Change Summary

This is the first ASC X12N Post Adjudicated Claims Data Reporting implementation guide for the 837. In future guides, this section will contain a summary of all changes since the previous guide.


Appendix E - Industry Names

This section contains an alphabetic listing of data elements used in this implementation guide. Consult the X12N Data Element Dictionary for a complete list of all X12N Data Elements. Data element names in normal type are generic ASC X12 names. Italic type indicates a health care industry defined name.

Legend

Industry Name
Industry name definition.
800 - Transaction Set ID and Name
H=Header, D=Detail, S=Summary | Loop ID | Reference Designator | Composite ID-Position in Composite | X12 Data Element Number

Accident Date
Date of the accident related to charges or to the patient's current condition, diagnosis, or treatment referenced in the transaction.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | DTP03 | - | 1251

Acute Manifestation Date
Date of acute manifestation of patient's condition.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | DTP03 | - | 1251

Adjudication or Payment Date
Date of payment or denial determination by previous payer.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2330B | DTP03 | - | 1251
D | 2430 | DTP03 | - | 1251

Adjusted Repriced Claim Reference Number
Identification number, assigned by a repricing organization, to identify an adjusted claim.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | REF02 | - | 127

Adjusted Repriced Line Item Reference Number
Identification number of an adjusted repriced line item adjusted from an original amount.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | REF02 | - | 127

Adjustment Amount
Adjustment amount for the associated reason code.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2320 | CAS03 | - | 782
D | 2320 | CAS06 | - | 782
D | 2320 | CAS09 | - | 782
D | 2320 | CAS12 | - | 782
D | 2320 | CAS15 | - | 782
D | 2320 | CAS18 | - | 782
D | 2430 | CAS03 | - | 782
D | 2430 | CAS06 | - | 782
D | 2430 | CAS09 | - | 782
D | 2430 | CAS12 | - | 782
D | 2430 | CAS15 | - | 782
D | 2430 | CAS18 | - | 782

Adjustment Quantity
Numeric quantity associated with the related reason code for coordination of benefits.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2320 | CAS04 | - | 380
D | 2320 | CAS07 | - | 380
D | 2320 | CAS10 | - | 380
D | 2320 | CAS13 | - | 380
D | 2320 | CAS16 | - | 380
D | 2320 | CAS19 | - | 380
D | 2430 | CAS04 | - | 380
D | 2430 | CAS07 | - | 380
D | 2430 | CAS10 | - | 380
D | 2430 | CAS13 | - | 380
D | 2430 | CAS16 | - | 380
D | 2430 | CAS19 | - | 380

Adjustment Reason Code
Code that indicates the reason for the adjustment.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2320 | CAS02 | - | 1034
D | 2320 | CAS05 | - | 1034
D | 2320 | CAS08 | - | 1034
D | 2320 | CAS11 | - | 1034
D | 2320 | CAS14 | - | 1034
D | 2320 | CAS17 | - | 1034
D | 2430 | CAS02 | - | 1034
D | 2430 | CAS05 | - | 1034
D | 2430 | CAS08 | - | 1034
D | 2430 | CAS11 | - | 1034
D | 2430 | CAS14 | - | 1034
D | 2430 | CAS17 | - | 1034

Ambulance Drop-off Address Line
Address line of the ambulance transport drop-off location.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310F | N301 | - | 166
D | 2310F | N302 | - | 166
D | 2420H | N301 | - | 166
D | 2420H | N302 | - | 166

Ambulance Drop-off City Name
City name of the ambulance transport drop-off location.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310F | N401 | - | 19
D | 2420H | N401 | - | 19

Ambulance Drop-off Country Code
Country code of the ambulance transport drop-off location.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310F | N404 | - | 26
D | 2420H | N404 | - | 26

Ambulance Drop-off Country Subdivision Code
Country subdivision code of the ambulance transport drop-off location.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310F | N407 | - | 1715
D | 2420H | N407 | - | 1715

Ambulance Drop-off Location
Name of the ambulance transport drop-off location.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310F | NM103 | - | 1035
D | 2420H | NM103 | - | 1035

Ambulance Drop-off Postal Zone or ZIP Code
Postal zone code or ZIP code of the ambulance transport drop-off location.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310F | N403 | - | 116
D | 2420H | N403 | - | 116

Ambulance Drop-off State or Province Code
State or province of the ambulance transport drop-off location.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310F | N402 | - | 156
D | 2420H | N402 | - | 156

Ambulance Patient Count
Number of patients in ambulance transport.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | QTY02 | - | 380

Ambulance Pick-up Address Line
Address line of the ambulance transport pick-up location.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310E | N301 | - | 166
D | 2310E | N302 | - | 166
D | 2420G | N301 | - | 166
D | 2420G | N302 | - | 166

Ambulance Pick-up City Name
City name of the ambulance transport pick-up location.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310E | N401 | - | 19
D | 2420G | N401 | - | 19

Ambulance Pick-up Country Code
Country code of the ambulance transport pick-up location.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2420G | N404 | - | 26

Ambulance Pick-up Country Subdivision Code
Country subdivision code of the ambulance transport pick-up location.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2420G | N407 | - | 1715

Ambulance Pick-up Postal Zone or ZIP Code
Postal zone code or ZIP code of the ambulance transport pick-up location.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310E | N403 | - | 116
D | 2420G | N403 | - | 116

Ambulance Pick-up State or Province Code
State or province of the ambulance transport pick-up location.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310E | N402 | - | 156
D | 2420G | N402 | - | 156

Ambulance Transport Reason Code
Code indicating the reason for ambulance transport.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CR104 | - | 1317
D | 2400 | CR104 | - | 1317

Amount Qualifier Code
Code to qualify amount.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | AMT01 | - | 522
D | 2320 | AMT01 | - | 522
D | 2320 | AMT01 | - | 522
D | 2400 | AMT01 | - | 522
D | 2400 | AMT01 | - | 522
D | 2430 | AMT01 | - | 522

Anesthesia Related Surgical Procedure
Code identifying the surgical procedure performed during this anesthesia session.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | HI01 | C022-02 | 1271

Assigned Number
Number assigned for differentiation within a transaction set.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | LX01 | - | 554

Assumed or Relinquished Care Date
Date post-operative care was assumed by another provider, or date provider ceased post-operative care.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | DTP03 | - | 1251

Attachment Control Number
Identification number of attachment related to the claim.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | PWK06 | - | 67
D | 2400 | PWK06 | - | 67

Attachment Report Type Code
Code to specify the type of attachment that is related to the claim.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | PWK01 | - | 755
D | 2400 | PWK01 | - | 755
D | 2400 | PWK01 | - | 755

Attachment Transmission Code
Code defining timing, transmission method or format by which an attachment report is to be sent or has been sent.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | PWK02 | - | 756
D | 2400 | PWK02 | - | 756
D | 2400 | PWK02 | - | 756

Auto Accident State or Province Code
State or Province where auto accident occurred.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CLM11 | C024-04 | 156

Begin Therapy Date
Date therapy begins.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | DTP03 | - | 1251

Billing Provider Address Line
Address line of the billing provider or billing entity address.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010AA | N301 | - | 166
D | 2010AA | N302 | - | 166

Billing Provider City Name
City of the billing provider or billing entity
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010AA | N401 | - | 19

Billing Provider First Name
First name of the billing provider or billing entity
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010AA | NM104 | - | 1036

Billing Provider Identifier
Identification number for the provider or organization in whose name the bill is submitted and to whom payment should be made.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010AA | NM109 | - | 67

Billing Provider Last or Organizational Name
Last name or organization name of the provider billing or billing entity for services.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010AA | NM103 | - | 1035

Billing Provider License Information
License identification assigned to the Billing Provider.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010AA | REF02 | - | 127

Billing Provider Middle Name or Initial
The middle name or initial of the provider billing for services.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010AA | NM105 | - | 1037

Billing Provider Name Suffix
Suffix, including generation, for the name of the provider or billing entity submitting the claim.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010AA | NM107 | - | 1039

Billing Provider Postal Zone or ZIP Code
Postal zone code or ZIP code for the provider or billing entity billing for services.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010AA | N403 | - | 116

Billing Provider Secondary Identifier
Secondary identification number for the provider or organization in whose name the bill is submitted and to whom payment should be made.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010AA | REF02 | - | 127

Billing Provider State or Province Code
State or province for provider or billing entity billing for services.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010AA | N402 | - | 156

Billing Provider Tax Identification Number
Tax identification number for the provider or organization in whose name the bill is submitted and to whom payment should be made.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010AA | REF02 | - | 127

Bundled or Unbundled Line Number
Identification of line item bundled or unbundled by payer in coordination of benefits.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2430 | SVD06 | - | 554

Certification Condition Code Applies Indicator
Code indicating whether or not the condition codes apply to the patient or another entity.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CRC02 | - | 1073

Certification Condition Indicator
Code indicating whether or not the condition codes apply to the patient or another entity.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CRC02 | - | 1073
D | 2300 | CRC02 | - | 1073
D | 2300 | CRC02 | - | 1073
D | 2400 | CRC02 | - | 1073
D | 2400 | CRC02 | - | 1073

Certification Revision or Recertification Date
Date the certification was revised or recertified.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | DTP03 | - | 1251

Certification Type Code
Code indicating the type of certification.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | CR301 | - | 1322

Claim Adjustment Group Code
Code identifying the general category of payment adjustment.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2320 | CAS01 | - | 1033
D | 2430 | CAS01 | - | 1033

Claim Filing Indicator Code
Code identifying type of claim or expected adjudication process.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2320 | SBR09 | - | 1032

Claim Frequency Code
Code specifying the frequency of the claim. This is the third position of the Uniform Billing Claim Form Bill Type.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CLM05 | C023-03 | 1325

Claim Identifier for Transmission Intermediaries
Unique Identification number for a transaction assigned by a Value Added Network, Clearinghouse, or other transmission entity.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | REF02 | - | 127

Claim Note Text
Narrative text providing additional information related to the claim.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | NTE02 | - | 352

Claim Payment Remark Code
Code identifying the remark associated with the payment.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2320 | MOA03 | - | 127
D | 2320 | MOA04 | - | 127
D | 2320 | MOA05 | - | 127
D | 2320 | MOA06 | - | 127
D | 2320 | MOA07 | - | 127

Claim or Encounter Identifier
Code indicating whether the transaction is a claim or reporting encounter information.
837 - Post-adjudicated Claims Data Reporting: Professional
H | | BHT06 | - | 640

Clinical Laboratory Improvement Amendment Number
The CLIA Certificate of Waiver or the CLIA Certificate of Registration Identification Number assigned to the laboratory testing site that rendered the services on this claim.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | REF02 | - | 127
D | 2400 | REF02 | - | 127

Code Category
Specifies the situation or category to which the code applies.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CRC01 | - | 1136
D | 2300 | CRC01 | - | 1136
D | 2400 | CRC01 | - | 1136
D | 2400 | CRC01 | - | 1136
D | 2400 | CRC01 | - | 1136

Code List Qualifier Code
Code identifying a specific industry code list.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | HI01 | C022-01 | 1270
D | 2300 | HI02 | C022-01 | 1270
D | 2300 | HI01 | C022-01 | 1270
D | 2300 | HI02 | C022-01 | 1270
D | 2300 | HI03 | C022-01 | 1270
D | 2300 | HI04 | C022-01 | 1270
D | 2300 | HI05 | C022-01 | 1270
D | 2300 | HI06 | C022-01 | 1270
D | 2300 | HI07 | C022-01 | 1270
D | 2300 | HI08 | C022-01 | 1270
D | 2300 | HI09 | C022-01 | 1270
D | 2300 | HI10 | C022-01 | 1270
D | 2300 | HI11 | C022-01 | 1270
D | 2300 | HI12 | C022-01 | 1270

Code Qualifier
Code identifying the type of unit or measurement.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CRC01 | - | 1136
D | 2410 | CTP05 | C001-01 | 355

Communication Number
Complete communications number including country or area code when applicable
837 - Post-adjudicated Claims Data Reporting: Professional
H | 1000A | PER04 | - | 364
H | 1000A | PER06 | - | 364
H | 1000A | PER08 | - | 364
D | 2420E | PER04 | - | 364
D | 2420E | PER06 | - | 364
D | 2420E | PER08 | - | 364

Communication Number Qualifier
Code identifying the type of communication number.
837 - Post-adjudicated Claims Data Reporting: Professional
H | 1000A | PER03 | - | 365
H | 1000A | PER05 | - | 365
H | 1000A | PER07 | - | 365
D | 2420E | PER03 | - | 365
D | 2420E | PER05 | - | 365
D | 2420E | PER07 | - | 365

Condition Code
Code(s) used to identify condition(s) relating to this bill or relating to the patient.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CRC03 | - | 1321
D | 2300 | CRC04 | - | 1321
D | 2300 | CRC05 | - | 1321
D | 2300 | CRC06 | - | 1321
D | 2300 | CRC07 | - | 1321
D | 2300 | CRC03 | - | 1321
D | 2300 | CRC04 | - | 1321
D | 2300 | CRC05 | - | 1321
D | 2300 | CRC06 | - | 1321
D | 2300 | CRC07 | - | 1321
D | 2300 | CRC01 | - | 1136
D | 2300 | HI01 | C022-02 | 1271
D | 2300 | HI02 | C022-02 | 1271
D | 2300 | HI03 | C022-02 | 1271
D | 2300 | HI04 | C022-02 | 1271
D | 2300 | HI05 | C022-02 | 1271
D | 2300 | HI06 | C022-02 | 1271
D | 2300 | HI07 | C022-02 | 1271
D | 2300 | HI08 | C022-02 | 1271
D | 2300 | HI09 | C022-02 | 1271
D | 2300 | HI10 | C022-02 | 1271
D | 2300 | HI11 | C022-02 | 1271
D | 2300 | HI12 | C022-02 | 1271
D | 2400 | CRC03 | - | 1321
D | 2400 | CRC04 | - | 1321
D | 2400 | CRC05 | - | 1321
D | 2400 | CRC06 | - | 1321
D | 2400 | CRC07 | - | 1321

Condition Indicator
Code indicating a condition
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CRC03 | - | 1321
D | 2300 | CRC04 | - | 1321
D | 2300 | CRC05 | - | 1321
D | 2400 | CRC03 | - | 1321
D | 2400 | CRC03 | - | 1321
D | 2400 | CRC04 | - | 1321

Contact Function Code
Code identifying the major duty or responsibility of the person or group named.
837 - Post-adjudicated Claims Data Reporting: Professional
H | 1000A | PER01 | - | 366
D | 2420E | PER01 | - | 366

Contract Amount
Fixed monetary amount pertaining to the contract
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CN102 | - | 782
D | 2400 | CN102 | - | 782

Contract Code
Code identifying the specific contract, established by the payer.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CN104 | - | 127
D | 2400 | CN104 | - | 127

Contract Percentage
Percent of charges payable under the contract
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CN103 | - | 332
D | 2400 | CN103 | - | 332

Contract Type Code
Code identifying a contract type
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CN101 | - | 1166
D | 2400 | CN101 | - | 1166

Contract Version Identifier
Identification of additional or supplemental contract provisions, or identification of a particular version or modification of contract.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CN106 | - | 799
D | 2400 | CN106 | - | 799

Coordination of Benefits Code
Code identifying whether there is a coordination of benefits
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2320 | SBR06 | - | 1143

Copay Status Code
Code indicating whether or not co-payment requirements were met on a line by line basis.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | SV115 | - | 1327

Country Code
Code indicating the geographic location.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010AA | N404 | - | 26
D | 2010BA | N404 | - | 26
D | 2010CA | N404 | - | 26
D | 2300 | CLM11 | C024-05 | 26
D | 2310C | N404 | - | 26
D | 2310E | N404 | - | 26
D | 2330A | N404 | - | 26
D | 2330C | N404 | - | 26
D | 2420C | N404 | - | 26
D | 2420E | N404 | - | 26

Country Subdivision Code
Code identifying the country subdivision.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010AA | N407 | - | 1715
D | 2010BA | N407 | - | 1715
D | 2010CA | N407 | - | 1715
D | 2310C | N407 | - | 1715
D | 2310E | N407 | - | 1715
D | 2330A | N407 | - | 1715
D | 2330C | N407 | - | 1715
D | 2420C | N407 | - | 1715
D | 2420E | N407 | - | 1715

Currency Code
Code for country in whose currency the charges are specified.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2000A | CUR02 | - | 100

Data Receiver Name
Final destination receiver of adjudicated claims data.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010BB | NM103 | - | 1035

Date Time Period
Expression of a date, a time, or a range of dates, times, or dates and times.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | DTP03 | - | 1251

Date Time Period Format Qualifier
Code indicating the date format, time format, or date and time format.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010BA | DMG01 | - | 1250
D | 2010CA | DMG01 | - | 1250
D | 2300 | DTP02 | - | 1250
D | 2300 | DTP02 | - | 1250
D | 2300 | DTP02 | - | 1250
D | 2300 | DTP02 | - | 1250
D | 2300 | DTP02 | - | 1250
D | 2300 | DTP02 | - | 1250
D | 2300 | DTP02 | - | 1250
D | 2300 | DTP02 | - | 1250
D | 2300 | DTP02 | - | 1250
D | 2300 | DTP02 | - | 1250
D | 2300 | DTP02 | - | 1250
D | 2300 | DTP02 | - | 1250
D | 2300 | DTP02 | - | 1250
D | 2300 | DTP02 | - | 1250
D | 2300 | DTP02 | - | 1250
D | 2300 | DTP02 | - | 1250
D | 2330B | DTP02 | - | 1250
D | 2400 | DTP02 | - | 1250
D | 2400 | DTP02 | - | 1250
D | 2400 | DTP02 | - | 1250
D | 2400 | DTP02 | - | 1250
D | 2400 | DTP02 | - | 1250
D | 2400 | DTP02 | - | 1250
D | 2400 | DTP02 | - | 1250
D | 2400 | DTP02 | - | 1250
D | 2400 | DTP02 | - | 1250
D | 2400 | DTP02 | - | 1250
D | 2430 | DTP02 | - | 1250

Date Time Qualifier
Code specifying the type of date or time or both date and time.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | DTP01 | - | 374
D | 2300 | DTP01 | - | 374
D | 2300 | DTP01 | - | 374
D | 2300 | DTP01 | - | 374
D | 2300 | DTP01 | - | 374
D | 2300 | DTP01 | - | 374
D | 2300 | DTP01 | - | 374
D | 2300 | DTP01 | - | 374
D | 2300 | DTP01 | - | 374
D | 2300 | DTP01 | - | 374
D | 2300 | DTP01 | - | 374
D | 2300 | DTP01 | - | 374
D | 2300 | DTP01 | - | 374
D | 2300 | DTP01 | - | 374
D | 2300 | DTP01 | - | 374
D | 2300 | DTP01 | - | 374
D | 2330B | DTP01 | - | 374
D | 2400 | DTP01 | - | 374
D | 2400 | DTP01 | - | 374
D | 2400 | DTP01 | - | 374
D | 2400 | DTP01 | - | 374
D | 2400 | DTP01 | - | 374
D | 2400 | DTP01 | - | 374
D | 2400 | DTP01 | - | 374
D | 2400 | DTP01 | - | 374
D | 2400 | DTP01 | - | 374
D | 2400 | DTP01 | - | 374
D | 2430 | DTP01 | - | 374

Delay Reason Code
Code indicating the reason why a request was delayed.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CLM20 | - | 1514

Description
A free-form description to clarify the related data elements and their content.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | SV101 | C003-07 | 352

Diagnosis Code
An ICD-9-CM Diagnosis Code identifying a diagnosed medical condition.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | HI01 | C022-02 | 1271
D | 2300 | HI02 | C022-02 | 1271
D | 2300 | HI03 | C022-02 | 1271
D | 2300 | HI04 | C022-02 | 1271
D | 2300 | HI05 | C022-02 | 1271
D | 2300 | HI06 | C022-02 | 1271
D | 2300 | HI07 | C022-02 | 1271
D | 2300 | HI08 | C022-02 | 1271
D | 2300 | HI09 | C022-02 | 1271
D | 2300 | HI10 | C022-02 | 1271
D | 2300 | HI11 | C022-02 | 1271
D | 2300 | HI12 | C022-02 | 1271

Diagnosis Code Pointer
A pointer to the claim diagnosis code in the order of importance to this service.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | SV107 | C004-01 | 1328
D | 2400 | SV107 | C004-02 | 1328
D | 2400 | SV107 | C004-03 | 1328
D | 2400 | SV107 | C004-04 | 1328

Diagnosis Type Code
Code identifying the type of diagnosis.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | HI01 | C022-01 | 1270
D | 2300 | HI02 | C022-01 | 1270
D | 2300 | HI03 | C022-01 | 1270
D | 2300 | HI04 | C022-01 | 1270
D | 2300 | HI05 | C022-01 | 1270
D | 2300 | HI06 | C022-01 | 1270
D | 2300 | HI07 | C022-01 | 1270
D | 2300 | HI08 | C022-01 | 1270
D | 2300 | HI09 | C022-01 | 1270
D | 2300 | HI10 | C022-01 | 1270
D | 2300 | HI11 | C022-01 | 1270
D | 2300 | HI12 | C022-01 | 1270

Disability Dates
The date(s), in the provider's opinion, that the patient was or will be unable to perform the duties normally associated with his/her work.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | DTP03 | - | 1251

Durable Medical Equipment Duration
Length of time durable medical equipment (DME) is needed.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | CR303 | - | 380

EPSDT Indicator
An indicator of whether or not Early and Periodic Screening for Diagnosis and Treatment of children services are involved with this detail line.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | SV111 | - | 1073

Emergency Indicator
An indicator of whether or not emergency care was rendered in response to the sudden and unexpected onset of a medical condition, a severe injury, or an acute exacerbation of a chronic condition which was threatening to life, limb or sight, and which requires immediate medical intervention.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | SV109 | - | 1073

End Stage Renal Disease Payment Amount
Amount of payment under End Stage Renal Disease benefit.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2320 | MOA08 | - | 782

Entity Identifier Code
Code identifying an organizational entity, a physical location, property or an individual.
837 - Post-adjudicated Claims Data Reporting: Professional
H | 1000A | NM101 | - | 98
H | 1000B | NM101 | - | 98
D | 2000A | CUR01 | - | 98
D | 2010AA | NM101 | - | 98
D | 2010BA | NM101 | - | 98
D | 2010BB | NM101 | - | 98
D | 2010CA | NM101 | - | 98
D | 2310A | NM101 | - | 98
D | 2310B | NM101 | - | 98
D | 2310C | NM101 | - | 98
D | 2310D | NM101 | - | 98
D | 2310E | NM101 | - | 98
D | 2310F | NM101 | - | 98
D | 2330A | NM101 | - | 98
D | 2330B | NM101 | - | 98
D | 2330C | NM101 | - | 98
D | 2420A | NM101 | - | 98
D | 2420B | NM101 | - | 98
D | 2420C | NM101 | - | 98
D | 2420D | NM101 | - | 98
D | 2420E | NM101 | - | 98
D | 2420F | NM101 | - | 98
D | 2420G | NM101 | - | 98
D | 2420H | NM101 | - | 98

Entity Type Qualifier
Code qualifying the type of entity.
837 - Post-adjudicated Claims Data Reporting: Professional
H | 1000A | NM102 | - | 1065
H | 1000B | NM102 | - | 1065
D | 2010AA | NM102 | - | 1065
D | 2010BA | NM102 | - | 1065
D | 2010BB | NM102 | - | 1065
D | 2010CA | NM102 | - | 1065
D | 2310A | NM102 | - | 1065
D | 2310B | NM102 | - | 1065
D | 2310C | NM102 | - | 1065
D | 2310D | NM102 | - | 1065
D | 2310E | NM102 | - | 1065
D | 2310F | NM102 | - | 1065
D | 2330A | NM102 | - | 1065
D | 2330B | NM102 | - | 1065
D | 2330C | NM102 | - | 1065
D | 2420A | NM102 | - | 1065
D | 2420B | NM102 | - | 1065
D | 2420C | NM102 | - | 1065
D | 2420D | NM102 | - | 1065
D | 2420E | NM102 | - | 1065
D | 2420F | NM102 | - | 1065
D | 2420G | NM102 | - | 1065
D | 2420H | NM102 | - | 1065

Exception Code
Exception code generated by the Third Party Organization.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | HCP15 | - | 1527
D | 2400 | HCP15 | - | 1527

Facility Code Qualifier
Code identifying the type of facility referenced.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CLM05 | C023-02 | 1332

Family Planning Indicator
An indicator of whether or not Family Planning Services are involved with this detail line.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | SV112 | - | 1073

Fixed Format Information
Data in fixed format agreed upon by sender and receiver
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | K301 | - | 449
D | 2400 | K301 | - | 449

HCPCS Payable Amount
Amount due under Medicare HCPCS system.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2320 | MOA02 | - | 782

Hierarchical Child Code
Code indicating if there are hierarchical child data segments subordinate to the level being described.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2000A | HL04 | - | 736
D | 2000B | HL04 | - | 736
D | 2000C | HL04 | - | 736

Hierarchical ID Number
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2000A | HL01 | - | 628
D | 2000B | HL01 | - | 628
D | 2000C | HL01 | - | 628

Hierarchical Level Code
Code defining the characteristic of a level in a hierarchical structure.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2000A | HL03 | - | 735
D | 2000B | HL03 | - | 735
D | 2000C | HL03 | - | 735

Hierarchical Parent ID Number
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2000B | HL02 | - | 734
D | 2000C | HL02 | - | 734

Hierarchical Structure Code
Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set
837 - Post-adjudicated Claims Data Reporting: Professional
H | | BHT01 | - | 1005

Homebound Indicator
A code indicating whether a patient is homebound.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CRC03 | - | 1321

Hospice Employed Provider Indicator
An indicator of whether or not the treatment in the Hospice was rendered by a Hospice employed provider.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | CRC02 | - | 1073

Identification Code Qualifier
Code designating the system/method of code structure used for Identification Code (67).
837 - Post-adjudicated Claims Data Reporting: Professional
H | 1000A | NM108 | - | 66
H | 1000B | NM108 | - | 66
D | 2010AA | NM108 | - | 66
D | 2010BA | NM108 | - | 66
D | 2010CA | NM108 | - | 66
D | 2300 | PWK05 | - | 66
D | 2310A | NM108 | - | 66
D | 2310B | NM108 | - | 66
D | 2310C | NM108 | - | 66
D | 2310D | NM108 | - | 66
D | 2330A | NM108 | - | 66
D | 2330B | NM108 | - | 66
D | 2330C | NM108 | - | 66
D | 2400 | PWK05 | - | 66
D | 2420A | NM108 | - | 66
D | 2420B | NM108 | - | 66
D | 2420C | NM108 | - | 66
D | 2420D | NM108 | - | 66
D | 2420E | NM108 | - | 66
D | 2420F | NM108 | - | 66

Immunization Batch Number
The manufacturer's lot number for vaccine used in immunization.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | REF02 | - | 127

Implementation Guide Version Name
Name of the referenced implementation guide version.
837 - Post-adjudicated Claims Data Reporting: Professional
H | | ST03 | - | 1705

Individual Relationship Code
Code indicating the relationship between two individuals or entities.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2000B | SBR02 | - | 1069
D | 2000C | PAT01 | - | 1069
D | 2320 | SBR02 | - | 1069

Industry Code
Code indicating a code from a specific industry code list.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | HI02 | C022-02 | 1271

Initial Treatment Date
Date that the patient initially sought treatment for this condition.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | DTP03 | - | 1251
D | 2400 | DTP03 | - | 1251

Insured Group or Policy Number
The identification number, control number, or code assigned by the carrier or administrator to identify the group under which the individual is covered.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2320 | SBR03 | - | 127

Investigational Device Exemption Identifier
Number or reference identifying exemption assigned to an investigational device referenced in the claim.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | REF02 | - | 127

Laboratory or Facility Address Line
Address line of the laboratory or facility performing tests billed on the claim where the health care service was performed/rendered.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310C | N301 | - | 166
D | 2310C | N302 | - | 166
D | 2420C | N301 | - | 166
D | 2420C | N302 | - | 166

Laboratory or Facility City Name
City of the laboratory or facility performing tests billed on the claim where the health care service was performed/rendered.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310C | N401 | - | 19
D | 2420C | N401 | - | 19

Laboratory or Facility Name
Name of laboratory or other facility performing Laboratory testing on the claim where the health care service was performed/rendered.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310C | NM103 | - | 1035
D | 2420C | NM103 | - | 1035

Laboratory or Facility Postal Zone or ZIP Code
Postal ZIP or zonal code of the laboratory or facility performing tests billed on the claim where the health care service was performed/rendered.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310C | N403 | - | 116
D | 2420C | N403 | - | 116

Laboratory or Facility Primary Identifier
Identification number of laboratory or other facility performing laboratory testing on the claim where the health care service was performed/rendered.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310C | NM109 | - | 67
D | 2420C | NM109 | - | 67

Laboratory or Facility Secondary Identifier
Additional identifier for the laboratory or facility performing tests billed on the claim where the health care service was performed/rendered.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310C | REF02 | - | 127

Laboratory or Facility State or Province Code
State or province of the laboratory or facility performing tests billed on the claim where the health care service was performed/rendered.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310C | N402 | - | 156
D | 2420C | N402 | - | 156

Last Certification Date
The date of the last certification.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | DTP03 | - | 1251

Last Menstrual Period Date
The date of the last menstrual period (LMP).
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | DTP03 | - | 1251

Last Seen Date
Date the patient was last seen by the referring or ordering physician for a claim billed by a provider whose services require physician certification.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | DTP03 | - | 1251

Last Worked Date
Date patient last worked at the patient's current occupation
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | DTP03 | - | 1251

Last X-Ray Date
Date patient received last X-Ray.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | DTP03 | - | 1251
D | 2400 | DTP03 | - | 1251

Line Item Charge Amount
Charges related to this service.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | SV102 | - | 782

Line Item Control Number
Identifier assigned by the submitter/provider to this line item.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | REF02 | - | 127

Line Note Text
Narrative text providing additional information related to the service line.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | NTE02 | - | 352
D | 2400 | NTE02 | - | 352

Mammography Certification Number
CMS assigned Certification Number of the certified mammography screening center
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | REF02 | - | 127
D | 2400 | REF02 | - | 127

Measurement Qualifier
Code identifying a specific product or process characteristic to which a measurement applies
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | MEA02 | - | 738

Measurement Reference Identification Code
Code identifying the broad category to which a measurement applies
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | MEA01 | - | 737

Medical Record Number
A unique number assigned to patient by the provider to assist in retrieval of medical records.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | REF02 | - | 127

National Drug Code, Universal Product Number or Device Identifier of the Unique Device Identifier
The national drug identification number assigned by the Food and Drug Administration (FDA), or the unique product identification number or Device Identifier of the Unique Device Identifier that unambiguously identifies a medical/surgical device.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2410 | LIN03 | - | 234

National Drug Unit Count
The dispensing quantity, based upon the unit of measure as defined by the National Drug Code.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2410 | CTP04 | - | 380

Non-Payable Professional Component Billed Amount
Amount of non-payable charges included in the bill related to professional services.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2320 | MOA09 | - | 782

Note Reference Code
Code identifying the functional area or purpose for which the note applies.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | NTE01 | - | 363
D | 2400 | NTE01 | - | 363
D | 2400 | NTE01 | - | 363

Obstetric Additional Units
Additional anesthesia units reported by anesthesiologist to report additional complexity beyond the normal services reflected by the base units for the reported procedure and anesthesia time.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | QTY02 | - | 380

Onset of Current Illness or Injury Date
Date of onset of indicated patient condition.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | DTP03 | - | 1251

Ordering Provider Address Line
Address line of the provider ordering services for the patient.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2420E | N301 | - | 166
D | 2420E | N302 | - | 166

Ordering Provider City Name
City of provider ordering services for the patient
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2420E | N401 | - | 19

Ordering Provider Contact Name
Contact person to whom inquiries should be directed at the provider ordering services for the patient.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2420E | PER02 | - | 93

Ordering Provider First Name
The first name of the provider who ordered or prescribed this service.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2420E | NM104 | - | 1036

Ordering Provider Identifier
The identifier assigned by the Payer to the provider who ordered or prescribed this service.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2420E | NM109 | - | 67

Ordering Provider Last Name
The last name of the provider who ordered or prescribed this service.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2420E | NM103 | - | 1035

Ordering Provider Middle Name or Initial
Middle name or initial of the provider ordering services for the patient.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2420E | NM105 | - | 1037

Ordering Provider Name Suffix
Suffix to the name of the provider ordering services for the patient.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2420E | NM107 | - | 1039

Ordering Provider Postal Zone or ZIP Code
Postal ZIP code of the provider ordering services for the patient.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2420E | N403 | - | 116

Ordering Provider Secondary Identifier
Additional identifier for the provider ordering services for the patient.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2420E | REF02 | - | 127

Ordering Provider State or Province Code
The State Postal Code of the provider who ordered/prescribed this service.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2420E | N402 | - | 156

Originator Application Transaction Identifier
An identification number that identifies a transaction within the originator's applications system.
837 - Post-adjudicated Claims Data Reporting: Professional
H | | BHT03 | - | 127

Other Insured Additional Identifier
Number providing additional identification of the other insured.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2330A | REF02 | - | 127
D | 2330C | REF02 | - | 127

Other Insured Address Line
Address line of the additional insured individual's mailing address.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2330A | N302 | - | 166

Other Insured First Name
The first name of the additional insured individual.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2330A | NM104 | - | 1036
D | 2330C | NM104 | - | 1036

Other Insured Group Name
Name of the group or plan through which the insurance is provided to the other insured.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2320 | SBR04 | - | 93

Other Insured Identifier
An identification number, assigned by the third party payer, to identify the additional insured individual.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2330A | NM109 | - | 67
D | 2330C | NM109 | - | 67

Other Insured Last Name
The last name of the additional insured individual.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2330A | NM103 | - | 1035
D | 2330C | NM103 | - | 1035

Other Insured Middle Name
The middle name of the additional insured individual.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2330A | NM105 | - | 1037
D | 2330C | NM105 | - | 1037

Other Insured Name Suffix
The suffix to the name of the additional insured individual.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2330A | NM107 | - | 1039
D | 2330C | NM107 | - | 1039

Other Patient Address Line
Address line of the street mailing address of the patient.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2330C | N301 | - | 166
D | 2330C | N302 | - | 166

Other Patient City Name
The city name of the patient.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2330C | N401 | - | 19

Other Patient Postal Zone or ZIP Code
The ZIP Code of the patient.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2330C | N403 | - | 116

Other Patient State or Province Code
The State Postal Code or Province of the patient.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2330C | N402 | - | 156

Other Payer Claim Adjustment Indicator
Indicates this claim has been adjusted.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2330B | REF02 | - | 127

Other Payer Organization Name
Organization name of this non-destination (COB) payer.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2330B | NM103 | - | 1035

Other Payer Primary Identifier
An identification number for the other payer.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2330B | NM109 | - | 67
D | 2430 | SVD01 | - | 67

Other Payer Secondary Identifier
Additional identifier for the other payer organization
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2330B | REF02 | - | 127

Other Payer's Adjusted Claim Control Number
This is the payer's claim control number of the claim adjusted as the result of this adjudication.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2330B | REF02 | - | 127

Other Payer's Claim Control Number
A number assigned by the other payer to identify a claim. The number is usually referred to as an Internal Control Number (ICN), Claim Control Number (CCN) or a Document Control Number (DCN).
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2330B | REF02 | - | 127

Other Subscriber Address Line
Address line of the Other Subscriber's mailing address.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2330A | N301 | - | 166

Other Subscriber City Name
The city name of the Other Subscriber.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2330A | N401 | - | 19

Other Subscriber Postal Zone or ZIP Code
The Postal ZIP code of the Other Subscriber's mailing address.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2330A | N403 | - | 116

Other Subscriber State or Province Code
The state code of the Other Subscriber's mailing address.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2330A | N402 | - | 156

Paid Service Unit Count
Units of service paid by the payer for coordination of benefits.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2430 | SVD05 | - | 380

Patient Address Line
Address line of the street mailing address of the patient.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010CA | N301 | - | 166
D | 2010CA | N302 | - | 166

Patient Amount Paid
The amount the provider has received from the patient (or insured) toward payment of this claim.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | AMT02 | - | 782

Patient Birth Date
Date of birth of the patient.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010CA | DMG02 | - | 1251

Patient City Name
The city name of the patient.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010CA | N401 | - | 19

Patient Condition Code
Code indicating the condition of the patient.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CR208 | - | 1342

Patient Condition Description
Free-form description of the patient's condition.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CR210 | - | 352
D | 2300 | CR211 | - | 352

Patient Control Number
Patient's unique alpha-numeric identification number for this claim assigned by the provider to facilitate retrieval of individual case records and posting of payment.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CLM01 | - | 1028

Patient First Name
The first name of the individual to whom the services were provided.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010CA | NM104 | - | 1036

Patient Gender Code
A code indicating the sex of the patient.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010CA | DMG03 | - | 1068

Patient Last Name
The last name of the individual to whom the services were provided.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010CA | NM103 | - | 1035

Patient Middle Name or Initial
The middle name or initial of the individual to whom the services were provided.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010CA | NM105 | - | 1037

Patient Name Suffix
Suffix to the name of the individual to whom the services were provided.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010CA | NM107 | - | 1039

Patient Postal Zone or ZIP Code
The ZIP Code of the patient.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010CA | N403 | - | 116

Patient Primary Identifier
Identifier assigned by the payer to identify the patient
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010CA | NM109 | - | 67

Patient Signature Source Code
Code indication how the patient/subscriber authorization signatures were obtained and how they are being retained by the provider.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CLM10 | - | 1351

Patient Social Security Number
This is the number assigned to the patient by the Social Security Administration.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010CA | REF02 | - | 127

Patient State Code
The State Postal Code of the patient.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010CA | N402 | - | 156

Patient Weight
Weight of the patient at time of treatment or transport.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CR102 | - | 81
D | 2400 | CR102 | - | 81

Payer Claim Control Number
A number assigned by the payer to identify a claim. The number is usually referred to as an Internal Control Number (ICN), Claim Control Number (CCN) or a Document Control Number (DCN).
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | REF02 | - | 127

Payer Paid Amount
The amount paid by the payer on this claim.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2320 | AMT02 | - | 782

Payer Responsibility Sequence Number Code
Code identifying the insurance carrier's level of responsibility for a payment of a claim
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2000B | SBR01 | - | 1138
D | 2320 | SBR01 | - | 1138

Place of Service Code
The code that identifies where the service was performed.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CLM05 | C023-01 | 1331
D | 2400 | SV105 | - | 1331

Policy Compliance Code
The code that specifies policy compliance.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | HCP14 | - | 1526
D | 2400 | HCP14 | - | 1526

Postage Claimed Amount
Cost of postage used to provide service or to process associated paperwork.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | AMT02 | - | 782

Prescription Date
The date the prescription was issued by the referring physician.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | DTP03 | - | 1251
D | 2400 | DTP03 | - | 1251

Prescription Number
The unique identification number assigned by the pharmacy or supplier to the prescription.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2410 | REF02 | - | 127

Pricing Methodology
Pricing methodology at which the claim or line item has been priced or repriced.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | HCP01 | - | 1473
D | 2400 | HCP01 | - | 1473

Prior Authorization Number
A number, code or other value that indicates the services provided on this claim have been authorized by the payee or other service organization.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | REF02 | - | 127

Prior Authorization or Referral Number
A number, code or other value that indicates the services provided on this claim have been authorized by the payee or other service organization, or that a referral for services has been approved.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | REF02 | - | 127

Procedure Code
Code identifying the procedure, product or service.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | SV101 | C003-02 | 234
D | 2430 | SVD03 | C003-02 | 234

Procedure Modifier
This identifies special circumstances related to the performance of the service.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | SV101 | C003-03 | 1339
D | 2400 | SV101 | C003-04 | 1339
D | 2400 | SV101 | C003-05 | 1339
D | 2400 | SV101 | C003-06 | 1339
D | 2430 | SVD03 | C003-03 | 1339
D | 2430 | SVD03 | C003-04 | 1339
D | 2430 | SVD03 | C003-05 | 1339
D | 2430 | SVD03 | C003-06 | 1339

Product or Service ID Qualifier
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | SV101 | C003-01 | 235
D | 2400 | HCP09 | - | 235
D | 2410 | LIN02 | - | 235
D | 2430 | SVD03 | C003-01 | 235

Property Casualty Claim Number
Identification number for property casualty claim associated with the services identified on the bill.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010BA | REF02 | - | 127
D | 2010CA | REF02 | - | 127

Provider Accept Assignment Code
Code indicating whether the provider accepts assignment.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CLM07 | - | 1359

Provider Code
Code identifying the type of provider.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2000A | PRV01 | - | 1221
D | 2310B | PRV01 | - | 1221
D | 2420A | PRV01 | - | 1221

Provider Taxonomy Code
Code designating the provider type, classification, and specialization.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2000A | PRV03 | - | 127
D | 2310B | PRV03 | - | 127
D | 2420A | PRV03 | - | 127

Purchased Service Charge Amount
The charge for the purchased service.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | PS102 | - | 782

Purchased Service Provider Identifier
The provider number of the entity from which service was purchased.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | PS101 | - | 127
D | 2420B | NM109 | - | 67

Purchased Service Provider Secondary Identifier
Additional identifier for the provider of purchased services.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2420B | REF02 | - | 127

Quantity Qualifier
Code specifying the type of quantity.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | QTY01 | - | 673
D | 2400 | QTY01 | - | 673

Receiver Name
Name of organization receiving the transaction.
837 - Post-adjudicated Claims Data Reporting: Professional
H | 1000B | NM103 | - | 1035

Receiver Primary Identifier
Primary identification number for the receiver of the transaction.
837 - Post-adjudicated Claims Data Reporting: Professional
H | 1000B | NM109 | - | 67

Reference Identification Qualifier
Code qualifying the reference identification.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2000A | PRV02 | - | 128
D | 2010AA | REF01 | - | 128
D | 2010AA | REF01 | - | 128
D | 2010AA | REF01 | - | 128
D | 2010BA | REF01 | - | 128
D | 2010BA | REF01 | - | 128
D | 2010CA | REF01 | - | 128
D | 2010CA | REF01 | - | 128
D | 2300 | REF01 | - | 128
D | 2300 | REF01 | - | 128
D | 2300 | REF01 | - | 128
D | 2300 | REF01 | - | 128
D | 2300 | REF01 | - | 128
D | 2300 | REF01 | - | 128
D | 2300 | REF01 | - | 128
D | 2300 | REF01 | - | 128
D | 2300 | REF01 | - | 128
D | 2300 | REF01 | - | 128
D | 2300 | REF01 | - | 128
D | 2310A | REF01 | - | 128
D | 2310B | PRV02 | - | 128
D | 2310B | REF01 | - | 128
D | 2310C | REF01 | - | 128
D | 2310D | REF01 | - | 128
D | 2330A | REF01 | - | 128
D | 2330B | REF01 | - | 128
D | 2330B | REF01 | - | 128
D | 2330B | REF01 | - | 128
D | 2330B | REF01 | - | 128
D | 2330C | REF01 | - | 128
D | 2400 | REF01 | - | 128
D | 2400 | REF01 | - | 128
D | 2400 | REF01 | - | 128
D | 2400 | REF01 | - | 128
D | 2400 | REF01 | - | 128
D | 2400 | REF01 | - | 128
D | 2400 | REF01 | - | 128
D | 2400 | REF01 | - | 128
D | 2400 | REF01 | - | 128
D | 2410 | REF01 | - | 128
D | 2420A | PRV02 | - | 128
D | 2420A | REF01 | - | 128
D | 2420B | REF01 | - | 128
D | 2420C | REF01 | - | 128
D | 2420D | REF01 | - | 128
D | 2420E | REF01 | - | 128
D | 2420F | REF01 | - | 128

Referral Number
Referral authorization number.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | REF02 | - | 127
D | 2400 | REF02 | - | 127

Referring CLIA Number
Referring Clinical Laboratory Improvement Amendment (CLIA) facility identification.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | REF02 | - | 127

Referring Provider First Name
The first name of provider who referred the patient to the provider of service on this claim.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310A | NM104 | - | 1036
D | 2420F | NM104 | - | 1036

Referring Provider Identifier
The identification number for the referring physician.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310A | NM109 | - | 67
D | 2420F | NM109 | - | 67

Referring Provider Last Name
The Last Name of Provider who referred the patient to the provider of service on this claim.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310A | NM103 | - | 1035
D | 2420F | NM103 | - | 1035

Referring Provider Middle Name or Initial
Middle name or initial of the provider who is referring patient for care.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310A | NM105 | - | 1037
D | 2420F | NM105 | - | 1037

Referring Provider Name Suffix
Suffix to the name of the provider referring the patient for care.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310A | NM107 | - | 1039
D | 2420F | NM107 | - | 1039

Referring Provider Secondary Identifier
Additional identification number for the provider referring the patient for service.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310A | REF02 | - | 127
D | 2420F | REF02 | - | 127

Reimbursement Rate
Rate used when payment is based upon a percentage of applicable charges.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2320 | MOA01 | - | 954

Reject Reason Code
Code assigned by issuer to identify reason for rejection.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | HCP13 | - | 901
D | 2400 | HCP13 | - | 901

Related Causes Code
Code identifying an accompanying cause of an illness, injury, or an accident.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CLM11 | C024-01 | 1362
D | 2300 | CLM11 | C024-02 | 1362

Related Hospitalization Admission Date
The date the patient was admitted for inpatient care related to current service.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | DTP03 | - | 1251

Related Hospitalization Discharge Date
The date the patient was discharged from the inpatient care referenced in the applicable hospitalization or hospice date.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | DTP03 | - | 1251

Release of Information Code
Code indicating whether the provider has on file a signed statement permitting the release of medical data to other organizations.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CLM09 | - | 1363

Remaining Patient Liability
In the judgement of the provider, the amount that remained to be paid after adjudication by this Other Payer.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2320 | AMT02 | - | 782
D | 2430 | AMT02 | - | 782

Rendering Provider First Name
The first name of the provider who performed the service.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310B | NM104 | - | 1036
D | 2420A | NM104 | - | 1036

Rendering Provider Identifier
The identifier assigned by the Payer to the provider who performed the service.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310B | NM109 | - | 67
D | 2420A | NM109 | - | 67

Rendering Provider Last or Organization Name
The last name or organization of the provider who performed the service
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310B | NM103 | - | 1035
D | 2420A | NM103 | - | 1035

Rendering Provider Middle Name or Initial
Middle name or initial of the provider who has provided the services to the patient.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310B | NM105 | - | 1037
D | 2420A | NM105 | - | 1037

Rendering Provider Name Suffix
Name suffix of the provider who has provided the services to the patient.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310B | NM107 | - | 1039
D | 2420A | NM107 | - | 1039

Rendering Provider Secondary Identifier
Additional identifier for the provider providing care to the patient.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310B | REF02 | - | 127
D | 2420A | REF02 | - | 127

Repriced Allowed Amount
The maximum amount determined by the repricer as being allowable under the provisions of the contract prior to the determination of the actual payment.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | HCP02 | - | 782
D | 2400 | HCP02 | - | 782

Repriced Approved Ambulatory Patient Group (APG) Amount
Amount of payment by the repricer for the referenced Ambulatory Patient Group.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | HCP07 | - | 782
D | 2400 | HCP07 | - | 782

Repriced Approved Ambulatory Patient Group (APG) Code
Identifier for Ambulatory Patient Group assigned to the claim by the repricer.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | HCP06 | - | 127
D | 2400 | HCP06 | - | 127

Repriced Approved HCPCS Code
The HCPCS code that describes the services as approved by the repricer.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | HCP10 | - | 234

Repriced Approved Service Unit Count
Number of service units approved by pricing or repricing entity.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | HCP12 | - | 380

Repriced Claim Reference Number
Identification number, assigned by a repricing organization, to identify the claim.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | REF02 | - | 127

Repriced Line Item Reference Number
Identification number of a line item repriced by a third party or prior payer.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | REF02 | - | 127

Repriced Saving Amount
The amount of savings related to Third Party Organization claims.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | HCP03 | - | 782
D | 2400 | HCP03 | - | 782

Repricer Received Date
Date the claim was received by the repricer organization.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | DTP03 | - | 1251

Repricing Organization Identifier
Reference or identification number of the repricing organization.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | HCP04 | - | 127
D | 2400 | HCP04 | - | 127

Repricing Per Diem or Flat Rate Amount
Amount used to determine the flat rate or per diem price by the repricing organization.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | HCP05 | - | 118
D | 2400 | HCP05 | - | 118

Round Trip Purpose Description
Free-form description of the purpose of the ambulance transport round trip.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CR109 | - | 352
D | 2400 | CR109 | - | 352

Sales Tax Amount
Amount of sales tax attributable to the referenced Service.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | AMT02 | - | 782

Service Authorization Exception Code
Code identifying the service authorization exception.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | REF02 | - | 127

Service Date
Date of service, such as the start date of the service, the end date of the service, or the single day date of the service.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | DTP03 | - | 1251

Service Facility Location Secondary Identifier
Secondary identifier for service facility location.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2420C | REF02 | - | 127

Service Line Paid Amount
Amount paid by the indicated payer for a service line
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2430 | SVD02 | - | 782

Service Unit Count
The quantity of units, times, days, visits, services, or treatments for the service described by the HCPCS codes, revenue code or procedure code.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | SV104 | - | 380

Shipped Date
Date product shipped.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | DTP03 | - | 1251

Special Program Indicator
A code indicating the Special Program under which the services rendered to the patient were performed.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CLM12 | - | 1366

Stretcher Purpose Description
Free-form description of the purpose of the use of a stretcher during ambulance service.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CR110 | - | 352
D | 2400 | CR110 | - | 352

Submitter Contact Name
Name of the person at the submitter organization to whom inquiries about the transaction should be directed.
837 - Post-adjudicated Claims Data Reporting: Professional
H | 1000A | PER02 | - | 93

Submitter Identifier
Code or number identifying the entity submitting the claim.
837 - Post-adjudicated Claims Data Reporting: Professional
H | 1000A | NM109 | - | 67

Submitter Last or Organization Name
The last name or the organizational name of the entity submitting the transaction
837 - Post-adjudicated Claims Data Reporting: Professional
H | 1000A | NM103 | - | 1035

Subscriber Address Line
Address line of the current mailing address of the insured individual or subscriber to the coverage.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010BA | N301 | - | 166
D | 2010BA | N302 | - | 166

Subscriber Birth Date
The date of birth of the subscriber to the indicated coverage or policy.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010BA | DMG02 | - | 1251

Subscriber City Name
The City Name of the insured individual or subscriber to the coverage.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010BA | N401 | - | 19

Subscriber First Name
The first name of the insured individual or subscriber to the coverage.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010BA | NM104 | - | 1036

Subscriber Gender Code
Code indicating the sex of the subscriber to the indicated coverage or policy.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010BA | DMG03 | - | 1068

Subscriber Last Name
The surname of the insured individual or subscriber to the coverage.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010BA | NM103 | - | 1035

Subscriber Middle Name or Initial
The middle name or initial of the subscriber to the indicated coverage or policy.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010BA | NM105 | - | 1037

Subscriber Name Suffix
Suffix of the insured individual or subscriber to the coverage.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010BA | NM107 | - | 1039

Subscriber Postal Zone or ZIP Code
The ZIP Code of the insured individual or subscriber to the coverage.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010BA | N403 | - | 116

Subscriber Primary Identifier
Primary identification number of the subscriber to the coverage.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010BA | NM109 | - | 67

Subscriber Social Security Number
This is the number assigned to the subscriber by the Social Security Administration.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010BA | REF02 | - | 127

Subscriber State Code
The State Postal Code of the insured individual or subscriber to the coverage.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2010BA | N402 | - | 156

Supervising Provider First Name
The First Name of the Provider who supervised the rendering of a service on this claim.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310D | NM104 | - | 1036
D | 2420D | NM104 | - | 1036

Supervising Provider Identifier
The Identification Number for the Supervising Provider.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310D | NM109 | - | 67
D | 2420D | NM109 | - | 67

Supervising Provider Last Name
The Last Name of the Provider who supervised the rendering of a service on this claim.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310D | NM103 | - | 1035
D | 2420D | NM103 | - | 1035

Supervising Provider Middle Name or Initial
Middle name or initial of the provider supervising care rendered to the patient.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310D | NM105 | - | 1037
D | 2420D | NM105 | - | 1037

Supervising Provider Name Suffix
Suffix to the name of the provider supervising care rendered to the patient.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310D | NM107 | - | 1039
D | 2420D | NM107 | - | 1039

Supervising Provider Secondary Identifier
Additional identifier for the provider supervising care rendered to the patient.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2310D | REF02 | - | 127
D | 2420D | REF02 | - | 127

Terms Discount Percentage
Discount percentage available to the payer for payment within a specific time period.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CN105 | - | 338
D | 2400 | CN105 | - | 338

Test Performed Date
The date the patient was tested for Hemoglobin, Hematocrit or Serum Creatinine.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | DTP03 | - | 1251

Test Results
The results of Hemoglobin, Hematocrit or Creatinine tests, Epoetin Starting Dosage, or the Patient's Height.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | MEA03 | - | 739

Total Claim Charge Amount
The sum of all charges included within this claim.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CLM02 | - | 782

Transaction Segment Count
A tally of all segments between the ST and the SE segments including the ST and SE segments.
837 - Post-adjudicated Claims Data Reporting: Professional
D | | SE01 | - | 96

Transaction Set Control Number
The unique identification number within a transaction set.
837 - Post-adjudicated Claims Data Reporting: Professional
H | | ST02 | - | 329
D | | SE02 | - | 329

Transaction Set Creation Date
Identifies the date the submitter created the transaction.
837 - Post-adjudicated Claims Data Reporting: Professional
H | | BHT04 | - | 373

Transaction Set Creation Time
Time file is created for transmission.
837 - Post-adjudicated Claims Data Reporting: Professional
H | | BHT05 | - | 337

Transaction Set Identifier Code
Code uniquely identifying a Transaction Set.
837 - Post-adjudicated Claims Data Reporting: Professional
H | | ST01 | - | 143

Transaction Set Purpose Code
Code identifying purpose of transaction set.
837 - Post-adjudicated Claims Data Reporting: Professional
H | | BHT02 | - | 353

Transport Distance
Distance traveled during the ambulance transport.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CR106 | - | 380
D | 2400 | CR106 | - | 380

Treatment or Therapy Date
Date when treatment or therapy was rendered or began.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2400 | DTP03 | - | 1251

Unit or Basis for Measurement Code
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CR101 | - | 355
D | 2300 | CR105 | - | 355
D | 2400 | SV103 | - | 355
D | 2400 | CR101 | - | 355
D | 2400 | CR105 | - | 355
D | 2400 | CR302 | - | 355
D | 2400 | HCP11 | - | 355

Work Return Date
Date patient was or is able to return to the patient's normal occupation or to a similar or substitute occupation.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | DTP03 | - | 1251

Yes No Condition or Response Code
Code indicating a Yes or No condition or response.
837 - Post-adjudicated Claims Data Reporting: Professional
D | 2300 | CLM06 | - | 1073
D | 2300 | CLM08 | - | 1073