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✱1✱T✱:~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
I01
Authorization Information Qualifier
M 1
ID
2
Code identifying the type of information in the Authorization Information
CODE
DEFINITION
00
No Authorization Information Present (No Meaningful Information in I02)
03
Additional Data Identification
Required
2
I02
Authorization Information
M 1
AN
10
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
This element is fixed in length with identical minimum and maximum lengths. Spaces are inserted to meet the minimum length in an AN data element. With the associated code 00 in ISA01 or ISA03, an all space value indicates no information.
Required
3
I03
Security Information Qualifier
M 1
ID
2
Code identifying the type of information in the Security Information
CODE
DEFINITION
00
No Security Information Present (No Meaningful Information in I04)
01
Password
Required
4
I04
Security Information
M 1
AN
10
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
This element is fixed in length with identical minimum and maximum lengths. Spaces are inserted to meet the minimum length in an AN data element. With the associated code 00 in ISA01 or ISA03, an all space value indicates no information.
Required
5
I05
Interchange ID Qualifier
M 1
ID
2
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
This ID qualifies the Sender in ISA06.
CODE
DEFINITION
01
Duns (Dun & Bradstreet)
14
Duns Plus Suffix
20
Health Industry Number (HIN)
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✱RECEIVERCODE✱19991231✱0802✱1✱X✱005010X222A2~
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
005010X222A2
Health Care Claim: 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✱005010X222A2~
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
005010X222A2
Health Care Claim: 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 Notes:
The second example denotes the case where the entire transaction set contains ENCOUNTERS.
TR3 Example:
  1. BHT✱0019✱00✱0123✱20040618✱0932✱CH~
  2. BHT✱0019✱00✱44445✱20040213✱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
  1. The inventory file number of the transmission assigned by the submitter's system. This number operates as a batch control number.
  2. This field is limited to 30 characters.
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
This is the date that the original submitter created the claim file from their business application system.
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
This is the time that the original submitter created the claim file from their business application system.
Required
6
640
Transaction Type Code
O 1
ID
2
Code specifying the type of transaction
INDUSTRY NAME: Claim or Encounter Identifier
CODE
DEFINITION
31
Subrogation Demand
The subrogation demand code is only for use by state Medicaid agencies performing post payment recovery claiming with willing trading partners.
CH
Chargeable
Use CH when the transaction contains only fee for service claims or claims with at least one chargeable line item. If it is not clear whether a transaction contains claims or capitated encounters, or if the transaction contains a mix of claims and capitated encounters, use CH.
RP
Reporting
Use RP when the entire ST-SE envelope contains only capitated encounters.
Use RP when the transaction is being sent to an entity (usually not a payer or a normal provider payer transmission intermediary) for purposes other than adjudication of a claim. Such an entity could be a state health data agency which is using the 837 for health data reporting purposes.

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
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: Submitter Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when NM102 = 1 (person) and the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Submitter First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when NM102 = 1 (person) and the middle name or initial of the person is needed to identify the individual. If not required by this implementation guide, do not send.
INDUSTRY NAME: Submitter Middle Name or Initial
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Not Used
7
1039
Name Suffix
O 1
AN
1/10
Required
8
66
Identification Code Qualifier
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)
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 the payer's adjudication is known to be impacted by the provider taxonomy code.
If not required by this implementation guide, do not send.
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. Beginning on the NPI compliance date: When the Billing Provider is an organization health care provider, the organization health care provider's NPI or its subpart's NPI is reported in NM109. When a health care provider organization has determined that it needs to enumerate its subparts, it will report the NPI of a subpart as the Billing Provider. The subpart reported as the Billing Provider MUST always represent the most detailed level of enumeration as determined by the organization health care provider and MUST be the same identifier sent to any trading partner. For additional explanation, see section 1.10.3 Organization Health Care Provider Subpart Presentation.
  2. Prior to the NPI compliance date, proprietary identifiers necessary for the receiver to identify the Billing Provider entity are to be reported in the REF segment of Loop ID-2010BB.
  3. The Taxpayer Identifying Number (TIN) of the Billing Provider to be used for 1099 purposes must be reported in the REF segment of this loop.
  4. 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. See section 1.10.1 (Providers who are Not Eligible for Enumeration).
  5. 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. The TIN to be used for 1099 purposes must be reported in the REF (Tax Identification Number) segment of this loop.
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 NM102 = 1 (person) and the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Billing Provider First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when NM102 = 1 (person) and the middle name or initial of the person is needed to identify the individual. If not required by this implementation guide, do not send.
INDUSTRY NAME: Billing Provider Middle Name or Initial
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when NM102 = 1 (person) and the name suffix of the person is needed to identify the individual. 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 for providers in the United States or its territories on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider is eligible to receive an NPI.ORRequired for providers not in the United States or its territories on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider has received an NPI.ORRequired for providers prior to the mandated NPI implementation date when the provider has received an NPI and the submitter has the capability to send it.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 and 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 for providers in the United States or its territories on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider is eligible to receive an NPI.ORRequired for providers not in the United States or its territories on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider has received an NPI.ORRequired for providers prior to the mandated NPI implementation date when the provider has received an NPI and the submitter has the capability to send it.If not required by this implementation guide, do not send.
INDUSTRY NAME: Billing Provider 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 - 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 must be a street address. Post Office Box or Lock Box addresses are to be sent in the Pay-To Address Loop (Loop ID-2010AB), if necessary.
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 there is a second address line. 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 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 to be 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 - BILLING PROVIDER UPIN/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 prior to the mandated HIPAA National Provider Identifier (NPI) implementation date when a UPIN and/or license number is necessary for the receiver to identify the provider.
OR
Required on or after the mandated NPI implementation date when NM109 of this loop is not used and a UPIN or license number is necessary for the receiver to identify the provider.
If not required by this implementation guide, do not send.
TR3 Notes:
Payer specific secondary identifiers are reported in the Loop ID-2010BB REF, Billing Provider Secondary Identification.
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
INDUSTRY NAME: Identification Code Qualifier
CODE
DEFINITION
0B
State License Number
1G
Provider UPIN Number
UPINs must be formatted as either X99999 or XXX999.
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 and/or UPIN Information
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

PER*IC - BILLING PROVIDER CONTACT INFORMATION

X12 Name:
Administrative Communications Contact
X12 Purpose:
To identify a person or office to whom administrative communications should be directed
X12 Syntax:
  1. P0304
    If either PER03 or PER04 is present, then the other is required.
  2. P0506
    If either PER05 or PER06 is present, then the other is required.
  3. P0708
    If either PER07 or PER08 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
2
Situational Rule:
Required when this information is different than that contained in the Loop ID-1000A - Submitter PER segment. If not required by this implementation guide, do not send.
TR3 Notes:
  1. When the communication number represents a telephone number in the United States and other countries using the North American Dialing Plan (for voice, data, fax, etc.), the communication number must always include the area code and phone number using the format AAABBBCCCC where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number. Therefore, the following telephone number (555) 555-1234 would be represented as 5555551234. Do not submit long distance access numbers, such as "1", in the telephone number. Telephone extensions, when applicable, must be submitted in the next element immediately following the telephone number. When submitting telephone extensions, only submit the numeric extension. Do not include data that indicates an extension, such as "ext" or "x-".
  2. There are 2 repetitions of the PER segment to allow for six possible 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 in the first iteration of the Billing Provider Contact Information segment. If not required by this implementation guide, do not send.
INDUSTRY NAME: Billing Provider Contact Name
Required
3
365
Communication Number Qualifier
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*87 - PAY-TO ADDRESS 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:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when the address for payment is different than that of the Billing Provider. If not required by this implementation guide, do not send.
TR3 Notes:
The purpose of Loop ID-2010AB has changed from previous versions. Loop ID-2010AB only contains address information when different from the Billing Provider Address. There are no applicable identifiers for Pay-To Address information.
TR3 Example:
NM1✱87✱2~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
87
Pay-to Provider
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code 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
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 - PAY-TO ADDRESS - ADDRESS

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

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

X12 Name:
Geographic Location
X12 Purpose:
To specify the geographic place of the named party
X12 Syntax:
  1. E0207
    Only one of N402 or N407 may be present.
  2. 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: Pay-to Address 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: Pay-to Address 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: Pay-to Address 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*PE - PAY-TO PLAN NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Loop 2010 contains information about entities that apply to all claims in loop 2300. For example, these entities may include billing provider, pay-to provider, insurer, primary administrator, contract holder, or claimant.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when willing trading partners agree to use this implementation for their subrogation payment requests.
TR3 Notes:
This loop may only be used when BHT06 = 31.
TR3 Example:
NM1✱PE✱2✱ANY STATE MEDICAID✱✱✱✱✱PI✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
PE
Payee
PE is used to indicate the subrogated payee.
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: Pay-To Plan Organizational Name
Not Used
4
1036
Name First
O 1
AN
1/35
Not Used
5
1037
Name Middle
O 1
AN
1/25
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Not Used
7
1039
Name Suffix
O 1
AN
1/10
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
Use code value "PI" when reporting Payor Identification.
Use code value "XV" when reporting Health Plan ID (HPID) or Other Entity Identifier (OEID).

Prior to the mandated implementation date for Health Plan Identifier, willing trading partners may agree to:
1. Follow a dual use approach in which both the HPID or OEID and the Payor Identification are sent. Send XV qualifier in NM108 with HPID or OEID in NM109 and the Payor Identification, that would have been sent using qualifier PI, in the corresponding REF segment using qualifier 2U (Payer Identification Number).
OR
2. Follow an early implementation approach in which the HPID or OEID is sent in NM109.
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: Pay-To Plan 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 - PAY-TO PLAN ADDRESS

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

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

X12 Name:
Geographic Location
X12 Purpose:
To specify the geographic place of the named party
X12 Syntax:
  1. E0207
    Only one of N402 or N407 may be present.
  2. 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: Pay-To Plan 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: Pay-To Plan 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: Pay-To Plan 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 - PAY-TO PLAN SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when an additional identification number to that provided in the NM109 of this loop is necessary to identify the entity. If not required by this implementation guide, do not send.
TR3 Example:
REF✱2U✱98765~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
2U
Payer Identification Number
This code is only allowed when the qualifier XV is reported in NM108 of this loop.
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: Pay-to Plan Secondary Identifier
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*EI - PAY-TO PLAN TAX IDENTIFICATION NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
REF✱EI✱123456789~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code 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.
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: Pay-To Plan Tax Identification Number
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:
  1. If a patient can be uniquely identified to the destination payer in Loop ID-2010BB by a unique Member Identification Number, then the patient is the subscriber or is considered to be the subscriber and is identified at this level, and the patient HL in Loop ID-2000C is not used.
  2. If the patient is not the subscriber and cannot be identified to the destination payer by a unique Member Identification Number or it is not known to the sender if the Member Identification number is unique, both this HL and the patient HL in Loop ID- 2000C are required.
TR3 Example:
HL✱2✱1✱22✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
628
Hierarchical ID Number
M 1
AN
1/12
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
COMMENT: HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
The first HL01 within each ST-SE envelope must begin with "1", and be incremented by one each time an HL is used in the transaction. Only numeric values are allowed in HL01.
Required
2
734
Hierarchical Parent ID Number
O 1
AN
1/12
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
COMMENT: HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Required
3
735
Hierarchical Level Code
M 1
ID
1/2
Code 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 - SUBSCRIBER INFORMATION

X12 Name:
Subscriber Information
X12 Purpose:
To record information specific to the primary insured and the insurance carrier for that insured
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
SBR✱P✱✱GRP01020102✱✱✱✱✱✱CI~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1138
Payer Responsibility Sequence Number Code
M 1
ID
1
Code identifying the insurance carrier's level of responsibility for a payment of a claim
Within a given claim, the various values for the Payer Responsibility Sequence Number Code (other than value "U") may occur no more than once.
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
This code may only be used in payer to payer COB claims when the original payer determined the presence of this coverage from eligibility files received from this payer or when the original claim did not provide the responsibility sequence for this payer.
Situational
2
1069
Individual Relationship Code
O 1
ID
2
Code indicating the relationship between two individuals or entities
SEMANTIC: SBR02 specifies the relationship to the person insured.
SITUATIONAL RULE: Required when the patient is the subscriber or is considered to be the subscriber. If not required by this implementation guide, do not send.
CODE
DEFINITION
18
Self
Situational
3
127
Reference Identification
O 1
AN
1/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 the subscriber's identification card for the destination payer (Loop ID-2010BB) shows a group number. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Group or Policy Number
This is not the number uniquely identifying the subscriber. The unique subscriber number is submitted in Loop ID-2010BA-NM109.
Situational
4
93
Name
O 1
AN
1/60
Free-form name
SEMANTIC: SBR04 is plan name.
SITUATIONAL RULE: Required when SBR03 is not used and the group name is available. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Group Name
Situational
5
1336
Insurance Type Code
O 1
ID
1/3
Code identifying the type of insurance policy within a specific insurance program
SITUATIONAL RULE: Required when the destination payer (Loop ID-2010BB) is Medicare and Medicare is not the primary payer (SBR01 does not equal "P"). If not required by this implementation guide, do not send.
CODE
DEFINITION
12
Medicare Secondary Working Aged Beneficiary or Spouse with Employer Group Health Plan
13
Medicare Secondary End-Stage Renal Disease Beneficiary in the Mandated Coordination Period with an Employer's Group Health Plan
14
Medicare Secondary, No-fault Insurance including Auto is Primary
15
Medicare Secondary Worker's Compensation
16
Medicare Secondary Public Health Service (PHS)or Other Federal Agency
41
Medicare Secondary Black Lung
42
Medicare Secondary Veteran's Administration
43
Medicare Secondary Disabled Beneficiary Under Age 65 with Large Group Health Plan (LGHP)
47
Medicare Secondary, Other Liability Insurance is Primary
Not Used
6
1143
Coordination of Benefits Code
O 1
ID
1
Not Used
7
1073
Yes/No Condition or Response Code
O 1
ID
1
Not Used
8
584
Employment Status Code
O 1
ID
2
Required
9
1032
Claim Filing Indicator Code
O 1
ID
1/2
Code identifying type of claim
CODE
DEFINITION
11
Other Non-Federal Programs
12
Preferred Provider Organization (PPO)
13
Point of Service (POS)
14
Exclusive Provider Organization (EPO)
15
Indemnity Insurance
16
Health Maintenance Organization (HMO) Medicare Risk
17
Dental Maintenance Organization
AM
Automobile Medical
BL
Blue Cross/Blue Shield
CH
Champus
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.

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:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the patient is the subscriber or considered to be the subscriber and at least one of the element requirements are met. If not required by this implementation guide, do not send.
TR3 Example:
PAT✱✱✱✱✱D8✱19970314~PAT✱✱✱✱✱✱✱01✱146~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Not Used
1
1069
Individual Relationship Code
O 1
ID
2
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
Situational
5
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: P0506
SITUATIONAL RULE: Required when patient is known to be deceased and the date of death is available to the provider billing system. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
6
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: PAT06 is the date of death.
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when patient is known to be deceased and the date of death is available to the provider billing system. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Death Date
Situational
7
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: P0708
SITUATIONAL RULE: Required when claims involve Medicare Durable Medical Equipment Regional Carriers Certificate of Medical Necessity (DMERC CMN) 02.03, 10.02, or DME MAC 10.03.If not required by this implementation guide, do not send.
CODE
DEFINITION
01
Actual Pounds
Situational
8
81
Weight
O 1
R
1/10
Numeric value of weight
SEMANTIC: PAT08 is the patient's weight.
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when claims involve Medicare Durable Medical Equipment Regional Carriers Certificate of Medical Necessity (DMERC CMN) 02.03, 10.02, or DME MAC 10.03.If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Weight
Situational
9
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: PAT09 indicates whether the patient is pregnant or not pregnant. Code "Y" indicates the patient is pregnant; code "N" indicates the patient is not pregnant.
SITUATIONAL RULE: Required when mandated by law. The determination of pregnancy shall be completed in compliance with applicable law. The "Y" code indicates that the patient is pregnant. If PAT09 is not used, it means that the patient is not pregnant or that the pregnancy indicator is not mandated by law.If not required by this implementation guide, do not send.
INDUSTRY NAME: Pregnancy Indicator
For this implementation, the listed value takes precedence over the semantic note.
CODE
DEFINITION
Y
Yes

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:
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.
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 NM102 = 1 (person) and the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when NM102 = 1 (person) and the middle name or initial of the person is needed to identify the individual. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Middle Name or Initial
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when NM102 = 1 (person) and the name suffix of the person is needed to identify the individual. 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 NM102 = 1 (person). 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
The code MI is intended to be the subscriber's identification number as assigned by the payer. (For example, Insured's ID, Subscriber's ID, Health Insurance Claim Number (HIC), etc.)

MI is also intended to be used in claims submitted to the Indian Health Service/Contract Health Services (IHS/CHS) Fiscal Intermediary for the purpose of reporting the Tribe Residency Code (Tribe County State). In the event that a Social Security Number (SSN) is also available on an IHS/CHS claim, put the SSN in REF02.

When sending the Social Security Number as the Member ID, it 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.
Situational
9
67
Identification Code
O 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when NM102 = 1 (person). If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Primary Identifier
Not Used
10
706
Entity Relationship Code
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:
Situational
Segment Repeat:
1
Situational Rule:
Required when the patient is the subscriber or considered to be the subscriber. If not required by this implementation guide, do not send.
TR3 Example:
N3✱123 MAIN STREET~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Subscriber Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when there is a second address line. 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:
Situational
Segment Repeat:
1
Situational Rule:
Required when the patient is the subscriber or considered to be the subscriber. If not required by this implementation guide, do not send.
TR3 Example:
N4✱KANSAS CITY✱MO✱64108~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
INDUSTRY NAME: Subscriber City Name
Situational
2
156
State or Province Code
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:
Situational
Segment Repeat:
1
Situational Rule:
Required when the patient is the subscriber or considered to be the subscriber. If not required by this implementation guide, do not send.
TR3 Example:
DMG✱D8✱19690815✱M~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1250
Date Time Period Format Qualifier
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 SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when an additional identification number to that provided in NM109 of this loop is necessary for the claim processor to identify the entity. If not required by this implementation guide, do not send.
TR3 Example:
REF✱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 Supplemental Identifier
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 the services included in this claim are to be considered as part of a property and casualty claim. If not required by this implementation guide, do not send.
TR3 Notes:
  1. This is a property and casualty payer-assigned claim number. Providers receive this number from the property and casualty payer during eligibility determinations or some other communication with that payer. See Section 1.4.2, Property and Casualty, for additional information about property and casualty claims.
  2. This segment is not a HIPAA requirement as of this writing.
TR3 Example:
REF✱Y4✱4445555~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code 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

PER*IC - PROPERTY AND CASUALTY SUBSCRIBER CONTACT INFORMATION

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

NM1*PR - PAYER NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Loop 2010 contains information about entities that apply to all claims in loop 2300. For example, these entities may include billing provider, pay-to provider, insurer, primary administrator, contract holder, or claimant.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
  1. This is the destination payer.
  2. For the purposes of this implementation the term payer is synonymous with several other terms, such as, repricer and third party administrator.
TR3 Example:
NM1✱PR✱2✱ABC INSURANCE CO✱✱✱✱✱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: Payer Name
Not Used
4
1036
Name First
O 1
AN
1/35
Not Used
5
1037
Name Middle
O 1
AN
1/25
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Not Used
7
1039
Name Suffix
O 1
AN
1/10
Required
8
66
Identification Code Qualifier
O 1
ID
1/2
Code designating the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
Use code value "PI" when reporting Payor Identification.
Use code value "XV" when reporting Health Plan ID (HPID) or Other Entity Identifier (OEID).

Prior to the mandated implementation date for Health Plan Identifier, willing trading partners may agree to:
1. Follow a dual use approach in which both the HPID or OEID and the Payor Identification are sent. Send XV qualifier in NM108 with HPID or OEID in NM109 and the Payor Identification, that would have been sent using qualifier PI, in the corresponding REF segment using qualifier 2U (Payer Identification Number).
OR
2. Follow an early implementation approach in which the HPID or OEID is sent in NM109.
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: Payer 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 - PAYER ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the payer address is available and the submitter intends for the claim to be printed on paper at the next EDI location (for example, a clearinghouse). If not required by this implementation guide, do not send.
TR3 Example:
N3✱123 MAIN STREET~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Payer Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when there is a second address line. If not required by this implementation guide, do not send.
INDUSTRY NAME: Payer Address Line

N4 - PAYER CITY, STATE, ZIP CODE

X12 Name:
Geographic Location
X12 Purpose:
To specify the geographic place of the named party
X12 Syntax:
  1. E0207
    Only one of N402 or N407 may be present.
  2. 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 the payer address is available and the submitter intends for the claim to be printed on paper at the next EDI location (for example, a clearinghouse). If not required by this implementation guide, do not send.
TR3 Example:
N4✱KANSAS CITY✱MO✱64108~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
INDUSTRY NAME: Payer City Name
Situational
2
156
State or Province Code
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: Payer 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: Payer 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 - PAYER SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
3
Situational Rule:
Required when an additional identification number to that provided in the NM109 of this loop is necessary to identify the entity. If not required by this implementation guide, do not send.
TR3 Example:
REF✱FY✱435261708~
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
This code is only allowed when the qualifier XV is reported in NM108 of this loop.
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: Payer Secondary Identifier
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 prior to the mandated NPI Implementation Date when an additional identification number is necessary for the receiver to identify the provider.
OR
Required on or after the mandated NPI Implementation Date when NM109 in Loop 2010AA is not used and an identification number other than the NPI is necessary for the receiver to identify the provider.
If not required by this implementation guide, do not send.
TR3 Example:
REF✱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 destination payer identified in the Payer Name loop, Loop ID-2010BB, associated with this claim. 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: Billing Provider Secondary Identifier
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

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 patient is a dependent of the subscriber identified in Loop ID-2000B and cannot be uniquely identified to the payer using the subscriber's identifier in the Subscriber Level. If not required by this implementation guide, do not send.
TR3 Notes:
  1. There are no HLs subordinate to the Patient HL.
  2. If a patient is a dependent of a subscriber and can be uniquely identified to the payer by a unique Identification Number, then the patient is considered the subscriber and is to be identified in the Subscriber Level.
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 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
Situational
5
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: P0506
SITUATIONAL RULE: Required when patient is known to be deceased and the date of death is available to the provider billing system. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
6
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: PAT06 is the date of death.
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when patient is known to be deceased and the date of death is available to the provider billing system. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Death Date
Situational
7
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: P0708
SITUATIONAL RULE: Required when claims involve Medicare Durable Medical Equipment Regional Carriers Certificate of Medical Necessity (DMERC CMN) 02.03, 10.02, or DME MAC 10.03.If not required by this implementation guide, do not send.
CODE
DEFINITION
01
Actual Pounds
Situational
8
81
Weight
O 1
R
1/10
Numeric value of weight
SEMANTIC: PAT08 is the patient's weight.
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when claims involve Medicare Durable Medical Equipment Regional Carriers Certificate of Medical Necessity (DMERC CMN) 02.03, 10.02, or DME MAC 10.03.If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Weight
Situational
9
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: PAT09 indicates whether the patient is pregnant or not pregnant. Code "Y" indicates the patient is pregnant; code "N" indicates the patient is not pregnant.
SITUATIONAL RULE: Required when mandated by law. The determination of pregnancy shall be completed in compliance with applicable law. The "Y" code indicates that the patient is pregnant. If PAT09 is not used, it means that the patient is not pregnant or that the pregnancy indicator is not mandated by law.If not required by this implementation guide, do not send.
INDUSTRY NAME: Pregnancy Indicator
For this implementation, the listed value takes precedence over the semantic note.
CODE
DEFINITION
Y
Yes

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 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 the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when the middle name or initial of the person is needed to identify the individual. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Middle Name or Initial
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when the name suffix is needed to identify the individual. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Name Suffix
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 - PATIENT ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
N3✱123 MAIN STREET~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Patient Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when there is a second address line. 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 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 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*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 the services included in this claim are to be considered as part of a property and casualty claim. If not required by this implementation guide, do not send.
TR3 Notes:
  1. This is a property and casualty payer-assigned claim number. Providers receive this number from the property and casualty payer during eligibility determinations or some other communication with that payer. See Section 1.4.2, Property and Casualty, for additional information about property and casualty claims.
  2. This segment is not a HIPAA requirement as of this writing.
TR3 Example:
REF✱Y4✱4445555~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code 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

REF - PROPERTY AND CASUALTY PATIENT IDENTIFIER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when an identification number is needed by the receiver to identify the patient for Property and Casualty claims. If not required by this implementation guide, do not send.
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
1W
Member Identification Number
This code designates a patient identification number used by the destination payer identified in the Payer Name loop, Loop ID 2010BB, associated with this claim.
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: Property and Casualty Patient Identifier
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

PER*IC - PROPERTY AND CASUALTY PATIENT CONTACT INFORMATION

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

CLM - CLAIM INFORMATION

X12 Name:
Health Claim
X12 Purpose:
To specify basic data about the claim
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
  1. The developers of this implementation guide recommend that trading partners limit the size of the transaction (ST-SE envelope) to a maximum of 5000 CLM segments. There is no recommended limit to the number of ST-SE transactions within a GS-GE or ISA-IEA. Willing trading partners can agree to set limits higher.
  2. For purposes of this documentation, the claim detail information is presented only in the dependent level. Specific claim detail information can be given in either the subscriber or the dependent hierarchical level. Because of this, the claim information is said to "float." Claim information is positioned in the same hierarchical level that describes its owner-participant, either the subscriber or the dependent. In other words, the claim information, Loop ID-2300, is placed following Loop ID-2010BB in the Subscriber Hierarchical Level (HL) when patient information is sent in Loop ID-2010BA of the Subscriber HL. Claim information is placed in the Patient HL when the patient information is sent in Loop ID-2010CA of the Patient HL. When the patient is the subscriber or is considered to be the subscriber, Loop ID-2000C and Loop ID-2010CA are not sent. See Subscriber/Patient HL Segment explanation in section 1.4.3.2.2.1 for details.
TR3 Example:
CLM✱A37YH556✱500✱✱✱11:B:1✱Y✱A✱Y✱I✱P~
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
  1. The number that the submitter transmits in this position is echoed back to the submitter in the 835 and other transactions. This permits the submitter to use the value in this field as a key in the submitter's system to match the claim to the payment information returned in the 835 transaction. The two recommended identifiers are either the Patient Account Number or the Claim Number in the billing submitter's patient management system. The developers of this implementation guide strongly recommend that submitters use unique numbers for this field for each individual claim.
  2. When Loop ID-2010AC is present, CLM01 represents the subrogated Medicaid agency's claim number (ICN/DCN) from their original 835 CLP07 - Payer Claim Control Number. See Section 1.4.1.4 of the front matter for a description of post payment recovery claims for subrogated Medicaid agencies.
  3. 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.
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
Required
6
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: CLM06 is provider signature on file indicator. A "Y" value indicates the provider signature is on file; an "N" value indicates the provider signature is not on file.
INDUSTRY NAME: Provider or Supplier Signature Indicator
CODE
DEFINITION
N
No
Y
Yes
Required
7
1359
Provider Accept Assignment Code
O 1
ID
1
Code indicating whether the provider accepts assignment
INDUSTRY NAME: Assignment or Plan Participation Code
Within this element the context of the word assignment is related to the relationship between the provider and the payer. 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
Required when the provider accepts assignment and/or has a participation agreement with the destination payer.
OR
Required when the provider does not accept assignment and/or have a participation agreement, but is advising the payer to adjudicate this specific claim under participating provider benefits as allowed under certain plans.
B
Assignment Accepted on Clinical Lab Services Only
Required when the provider accepts assignment for Clinical Lab Services only.
C
Not Assigned
Required when neither codes `A' nor `B' apply.
Required
8
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: CLM08 is assignment of benefits indicator. A "Y" value indicates insured or authorized person authorizes benefits to be assigned to the provider; an "N" value indicates benefits have not been assigned to the provider.
INDUSTRY NAME: Benefits Assignment Certification Indicator
This element 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
Required
9
1363
Release of Information Code
O 1
ID
1
Code indicating whether the provider has on file a signed statement by the patient authorizing the release of medical data to other organizations
The Release of Information response is limited to the information carried in this claim.
CODE
DEFINITION
I
Informed Consent to Release Medical Information for Conditions or Diagnoses Regulated by Federal Statutes
Required when the provider has not collected a signature AND state or federal laws do not require a signature be collected.
Y
Yes, Provider has a Signed Statement Permitting Release of Medical Billing Data Related to a Claim
Required when the provider has collected a signature.
OR
Required when state or federal laws require a signature be collected.
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 a signature was executed on the patient's behalf under state or federal law. 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 the services provided are employment related or the result of an accident. If not required by this implementation guide, do not send.
If DTP - Date of Accident (DTP01=439) is used, then CLM11 is required.
Required
11-1
1362
Related-Causes Code
M 1
ID
2/3
Code identifying an accompanying cause of an illness, injury or an accident
INDUSTRY NAME: Related Causes Code
CODE
DEFINITION
AA
Auto Accident
EM
Employment
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 more than one related cause code applies. See CLM11-1 for valid values. 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 CLM11-1 or CLM11-2 has a value of `AA' to identify the state, province or sub-country code in which the automobile accident occurred. If accident occurred in a country or location that does not have states, provinces or sub-country codes named in Code Source 22, do not use.If not required by this implementation guide, do not send.
INDUSTRY NAME: Auto Accident State or Province Code
CODE SOURCE 22:States and Provinces
Situational
11-5
26
Country Code
O 1
ID
2/3
Code identifying the country
SITUATIONAL RULE: Required when CLM11-1 or CLM11-2 = AA and the accident occurred in a country other than US or Canada. 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 the services were rendered under one of the following circumstances, programs, or projects. If not required by this implementation guide, do not send.
INDUSTRY NAME: Special Program Indicator
CODE
DEFINITION
02
Physically Handicapped Children's Program
This code is used for Medicaid claims only.
03
Special Federal Funding
This code is used for Medicaid claims only.
05
Disability
This code is used for Medicaid claims only.
09
Second Opinion or Surgery
This code is used for Medicaid claims only.
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 the claim is submitted late (past contracted date of filing limitations). If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Proof of Eligibility Unknown or Unavailable
2
Litigation
3
Authorization Delays
4
Delay in Certifying Provider
5
Delay in Supplying Billing Forms
6
Delay in Delivery of Custom-made Appliances
7
Third Party Processing Delay
8
Delay in Eligibility Determination
9
Original Claim Rejected or Denied Due to a Reason Unrelated to the Billing Limitation Rules
10
Administration Delay in the Prior Approval Process
11
Other
15
Natural Disaster

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 for the initial medical service or visit performed in response to a medical emergency when the date is available and is different than the date of service. If not required by this implementation guide, do not send.
TR3 Notes:
This date is the onset of acute symptoms for the current illness or condition.
TR3 Example:
DTP✱431✱D8✱20050108~
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 the Initial Treatment Date is known to impact adjudication for claims involving spinal manipulation, physical therapy, occupational therapy, speech language pathology, dialysis, optical refractions, or pregnancy. If not required by this implementation guide, do not send.
TR3 Notes:
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.
TR3 Example:
DTP✱454✱D8✱20050108~
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 claims involve services for routine foot care and it is known to impact the payer's adjudication process. If not required by this implementation guide, do not send.
TR3 Notes:
  1. 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.
  2. 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.
TR3 Example:
DTP✱304✱D8✱20050108~
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 Loop ID-2300 CR208 = "A" or "M", the claim involves spinal manipulation, and the payer is Medicare. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱453✱D8✱20050108~
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 CLM11-1 or CLM11-2 has a value of `AA' or `OA'.
OR
Required when CLM11-1 or CLM11-2 has a value of `EM' and this claim is the result of an accident.
If not required by this implementation guide, do not send.
TR3 Example:
DTP✱439✱D8✱20060108~
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, in the judgment of the provider, the services on this claim are related to the patient's pregnancy. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱484✱D8✱20050108~
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 claim involves spinal manipulation and an x-ray was taken. If not required by this implementation guide, do not send.
TR3 Notes:
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.
TR3 Example:
DTP✱455✱D8✱20050108~
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 on claims where a prescription has been written for hearing devices or vision frames and lenses and it is being billed on this claim. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱471✱D8✱20050108~
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 on claims involving disability where, in the judgment of the provider, the patient was or will be unable to perform the duties normally associated with his/her work.
OR
Required on non-HIPAA claims (for example workers compensation or property and casualty) when required by the claims processor.
If not required by this implementation guide, do not send.
TR3 Example:
DTP✱360✱D8✱20050108~
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: Certification Expiration Date
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: Level of Service Code

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 on claims where this information is necessary for adjudication of the claim (for example, workers compensation claims involving absence from work). If not required by this implementation guide, do not send.
TR3 Example:
DTP✱297✱D8✱20050108~
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 on claims where this information is necessary for adjudication of the claim (for example, workers compensation claims involving absence from work). If not required by this implementation guide, do not send.
TR3 Example:
DTP✱296✱D8✱20050108~
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 on all ambulance claims when the patient was known to be admitted to the hospital.
OR
Required on all claims involving inpatient medical visits.
If not required by this implementation guide, do not send.
TR3 Example:
DTP✱435✱D8✱20030108~
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 for inpatient claims when the patient was discharged from the facility and the discharge date is known. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱096✱D8✱20050108~
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 to indicate "assumed care date" or "relinquished care date" when providers share post-operative care (global surgery claims). If not required by this implementation guide, do not send.
TR3 Notes:
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".
TR3 Example:
DTP✱090✱D8✱20050108~
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 for Property and Casualty claims when state mandated. If not required by this implementation guide, do not send.
TR3 Notes:
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.
TR3 Example:
DTP✱444✱D8✱20041013~
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 a repricer is passing the claim onto the payer. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱050✱D8✱20051030~
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 there is a paper attachment following this claim.
OR
Required when attachments are sent electronically (PWK02 = EL) but are transmitted in another functional group (for example, 275) rather than by paper. PWK06 is then used to identify the attached electronic documentation. The number in PWK06 is carried in the TRN of the electronic attachment.
OR
Required when the provider deems it necessary to identify additional information that is being held at the provider's office and is available upon request by the payer (or appropriate entity), but the information is not being submitted with the claim. Use the value of "AA" in PWK02 to convey this specific use of the PWK segment.
If not required by this implementation guide, do not send.
TR3 Example:
PWK✱OZ✱BM✱✱✱AC✱DMN0012~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
755
Report Type Code
M 1
ID
2
Code indicating the title or contents of a document, report or supporting item
INDUSTRY NAME: Attachment Report Type Code
CODE
DEFINITION
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 PWK02 = "BM", "EL", "EM", "FX" or "FT". If not required by this implementation guide, do not send.
CODE
DEFINITION
AC
Attachment Control Number
Situational
6
67
Identification Code
O 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when PWK02 = "BM", "EL", "EM", "FX" or "FT". If not required by this implementation guide, do not send.
INDUSTRY NAME: Attachment Control Number
  1. PWK06 is 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 the submitter is contractually obligated to supply this information on post-adjudicated claims. If not required by this implementation guide, do not send.
TR3 Notes:
The developers of this implementation guide note that the CN1 segment is for use only for post-adjudicated claims, which do not meet the definition of a health care claim under HIPAA. Consequently, at the time of this writing, the CN1 segment is for non-HIPAA use only.
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 the provider is required by contract to supply this information on the claim. 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 the provider is required by contract to supply this information on the claim. 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 the provider is required by contract to supply this information on the claim. 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 the provider is required by contract to supply this information on the claim. 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 the provider is required by contract to supply this information on the claim. 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 patient has made payment specifically toward this claim. If not required by this implementation guide, do not send.
TR3 Notes:
Patient Amount Paid refers to the sum of all amounts paid on the claim by the patient or his or her representative(s).
TR3 Example:
AMT✱F5✱152.45~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
522
Amount Qualifier Code
M 1
ID
1/3
Code 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 mandated by government law or regulation to obtain authorization for specific service(s) but, for the reasons listed in REF02, the service was performed without obtaining the authorization. If not required by this implementation guide, do not send.
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*F5 - MANDATORY MEDICARE (SECTION 4081) CROSSOVER 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 the submitter is Medicare and the claim is a Medigap or COB crossover claim. If not required by this implementation guide, do not send.
TR3 Example:
REF✱F5✱N~
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
F5
Medicare Version 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: Medicare Section 4081 Indicator
The allowed values for this element are:
Y 4081
N Regular crossover
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 mammography services are rendered by a certified mammography provider. If not required by this implementation guide, do not send.
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 a referral number is assigned by the payer or Utilization Management Organization (UMO)
AND
a referral is involved.
If not required by this implementation guide, do not send.
TR3 Notes:
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.
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 an authorization number is assigned by the payer or UMO
AND
the services on this claim were preauthorized.
If not required by this implementation guide, do not send.
TR3 Notes:
  1. Generally, preauthorization numbers are assigned by the payer or UMO to authorize a service prior to its being performed. The UMO (Utilization Management Organization) is generally the entity empowered to make a decision regarding the outcome of a health services review or the owner of information. The prior authorization number carried in this REF is specific to the destination payer reported in the Loop ID-2010BB. If other payers have similar numbers for this claim, report that information in the Loop ID-2330 loop REF which holds that payer's information.
  2. 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.
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 CLM05-3 (Claim Frequency Code) indicates this claim is a replacement or void to a previously adjudicated claim. If not required by this implementation guide, do not send.
TR3 Notes:
This information is specific to the destination payer reported in Loop ID-2010BB.
TR3 Example:
REF✱F8✱R555588~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code 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 for all CLIA certified facilities performing CLIA covered laboratory services. 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.
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 this information is deemed necessary by the repricer. The segment is not completed by providers. The information is completed by repricers only. If not required by this implementation guide, do not send.
TR3 Notes:
This information is specific to the destination payer reported in Loop ID-2010BB.
TR3 Example:
REF✱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 this information is deemed necessary by the repricer. The segment is not completed by providers. The information is completed by repricers only. If not required by this implementation guide, do not send.
TR3 Notes:
This information is specific to the destination payer reported in Loop ID-2010BB.
TR3 Example:
REF✱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 claim involves a Food and Drug Administration (FDA) assigned investigational device exemption (IDE) number. When more than one IDE applies, they must be split into separate claims. If not required by this implementation guide, do not send.
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:
Although this REF is supplied for transmission intermediaries to attach their own unique claim number to a claim, 837-recipients are not required under HIPAA to return this number in any HIPAA transaction. Trading partners may voluntarily agree to this interaction if they wish.
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: Value Added Network Trace Number
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 the provider needs to identify for future inquiries, the actual medical record of the patient identified in either Loop ID-2010BA or Loop ID-2010CA for this episode of care. If not required by this implementation guide, do not send.
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

REF*P4 - DEMONSTRATION PROJECT IDENTIFIER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when it is necessary to identify claims which are atypical in ways such as content, purpose, and/or payment, as could be the case for a demonstration or other special project, or a clinical trial. If not required by this implementation guide, do not send.
TR3 Example:
REF✱P4✱THJ1222~
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
P4
Project 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: Demonstration Project Identifier
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*1J - CARE PLAN OVERSIGHT

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 physician is billing Medicare for Care Plan Oversight (CPO). If not required by this implementation guide, do not send.
TR3 Notes:
This is the number of the home health agency or hospice providing Medicare covered services to the patient for the period during which CPO services were furnished.
Prior to the mandated HIPAA National Provider Identifier (NPI) implementation date this number is the Medicare Number.
On or after the mandated HIPAA National Provider Identifier (NPI) implementation date this is the NPI.
TR3 Example:
REF✱1J✱12345678~
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
1J
Facility ID 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: Care Plan Oversight 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 ALL of the following conditions are met:
• A regulatory agency concludes it must use the K3 to meet an emergency
legislative requirement;
• The administering regulatory agency or other state organization has
completed each one of the following steps:
contacted the X12N workgroup,
requested a review of the K3 data requirement to ensure there is not
an existing method within the implementation guide to meet this
requirement
• X12N determines that there is no method to meet the requirement.
If not required by this implementation guide, do not send.
TR3 Notes:
  1. At the time of publication of this implementation, K3 segments have no specific use. 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).
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 in the judgment of the provider, the information is needed to substantiate the medical treatment and is not supported elsewhere within the claim data set.
If not required by this implementation guide, do not send.
TR3 Notes:
  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.
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
ADD
Additional Information
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 on all claims involving ambulance transport services. If not required by this implementation guide, do not send.
TR3 Notes:
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.
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 it is necessary to justify the medical necessity of the level of ambulance services. 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 it is necessary to justify the medical necessity of the level of ambulance services. 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 the ambulance service is for a round trip. 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 needed to justify usage of stretcher. 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 on chiropractic claims involving spinal manipulation when the information is known to impact the payer's adjudication process. If not required by this implementation guide, do not send.
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 this information is deemed necessary by the submitter. 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 this information is deemed necessary by the submitter. 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 the claim involves ambulance transport services
AND
when reporting condition codes in any of CRC03 through CRC07. 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.
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 a second condition code is necessary. 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 a third condition code is necessary. 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 a fourth condition code is necessary. 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 a fifth condition code is necessary. 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 on vision claims involving replacement lenses or frames when this information is known to impact reimbursement. If not required by this implementation guide, do not send.
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 a second condition code is necessary. 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 a third condition code is necessary. 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 a fourth condition code is necessary. 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 a fifth condition code is necessary. 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 for Medicare claims when an independent laboratory renders an EKG tracing or obtains a specimen from a homebound or institutionalized patient. If not required by this implementation guide, do not send.
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.
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 on Early & Periodic Screening, Diagnosis, and Treatment (EPSDT) claims when the screening service is being billed in this claim. If not required by this implementation guide, do not send.
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 conditioner 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 a second condition code is necessary. 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 conditioner 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 a third condition code is necessary. 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 conditioner 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
This code set is not allowed for use under HIPAA at the time of this writing. The qualifier can only be used:
If a new rule names the ICD-10-CM as an allowable code set under HIPAA,
OR
The Secretary grants an exception to use the code set as a pilot project as allowed under the law,
OR
For claims which are not covered under HIPAA.
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 it is necessary to report an additional diagnosis and the preceding HI data elements have been used to report other diagnoses. If not required by this implementation guide, do not send.
Required
2-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
INDUSTRY NAME: Diagnosis Type Code
CODE
DEFINITION
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
This code set is not allowed for use under HIPAA at the time of this writing. The qualifier can only be used:
If a new rule names the ICD-10-CM as an allowable code set under HIPAA,
OR
The Secretary grants an exception to use the code set as a pilot project as allowed under the law,
OR
For claims which are not covered under HIPAA.
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 it is necessary to report an additional diagnosis and the preceding HI data elements have been used to report other diagnoses. If not required by this implementation guide, do not send.
Required
3-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
INDUSTRY NAME: Diagnosis Type Code
CODE
DEFINITION
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
This code set is not allowed for use under HIPAA at the time of this writing. The qualifier can only be used:
If a new rule names the ICD-10-CM as an allowable code set under HIPAA,
OR
The Secretary grants an exception to use the code set as a pilot project as allowed under the law,
OR
For claims which are not covered under HIPAA.
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 it is necessary to report an additional diagnosis and the preceding HI data elements have been used to report other diagnoses. If not required by this implementation guide, do not send.
Required
4-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
INDUSTRY NAME: Diagnosis Type Code
CODE
DEFINITION
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
This code set is not allowed for use under HIPAA at the time of this writing. The qualifier can only be used:
If a new rule names the ICD-10-CM as an allowable code set under HIPAA,
OR
The Secretary grants an exception to use the code set as a pilot project as allowed under the law,
OR
For claims which are not covered under HIPAA.
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 it is necessary to report an additional diagnosis and the preceding HI data elements have been used to report other diagnoses. If not required by this implementation guide, do not send.
Required
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
This code set is not allowed for use under HIPAA at the time of this writing. The qualifier can only be used:
If a new rule names the ICD-10-CM as an allowable code set under HIPAA,
OR
The Secretary grants an exception to use the code set as a pilot project as allowed under the law,
OR
For claims which are not covered under HIPAA.
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 it is necessary to report an additional diagnosis and the preceding HI data elements have been used to report other diagnoses. If not required by this implementation guide, do not send.
Required
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
This code set is not allowed for use under HIPAA at the time of this writing. The qualifier can only be used:
If a new rule names the ICD-10-CM as an allowable code set under HIPAA,
OR
The Secretary grants an exception to use the code set as a pilot project as allowed under the law,
OR
For claims which are not covered under HIPAA.
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 it is necessary to report an additional diagnosis and the preceding HI data elements have been used to report other diagnoses. If not required by this implementation guide, do not send.
Required
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
This code set is not allowed for use under HIPAA at the time of this writing. The qualifier can only be used:
If a new rule names the ICD-10-CM as an allowable code set under HIPAA,
OR
The Secretary grants an exception to use the code set as a pilot project as allowed under the law,
OR
For claims which are not covered under HIPAA.
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 it is necessary to report an additional diagnosis and the preceding HI data elements have been used to report other diagnoses. If not required by this implementation guide, do not send.
Required
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
This code set is not allowed for use under HIPAA at the time of this writing. The qualifier can only be used:
If a new rule names the ICD-10-CM as an allowable code set under HIPAA,
OR
The Secretary grants an exception to use the code set as a pilot project as allowed under the law,
OR
For claims which are not covered under HIPAA.
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 it is necessary to report an additional diagnosis and the preceding HI data elements have been used to report other diagnoses. If not required by this implementation guide, do not send.
Required
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
This code set is not allowed for use under HIPAA at the time of this writing. The qualifier can only be used:
If a new rule names the ICD-10-CM as an allowable code set under HIPAA,
OR
The Secretary grants an exception to use the code set as a pilot project as allowed under the law,
OR
For claims which are not covered under HIPAA.
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 it is necessary to report an additional diagnosis and the preceding HI data elements have been used to report other diagnoses. If not required by this implementation guide, do not send.
Required
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
This code set is not allowed for use under HIPAA at the time of this writing. The qualifier can only be used:
If a new rule names the ICD-10-CM as an allowable code set under HIPAA,
OR
The Secretary grants an exception to use the code set as a pilot project as allowed under the law,
OR
For claims which are not covered under HIPAA.
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 it is necessary to report an additional diagnosis and the preceding HI data elements have been used to report other diagnoses. If not required by this implementation guide, do not send.
Required
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
This code set is not allowed for use under HIPAA at the time of this writing. The qualifier can only be used:
If a new rule names the ICD-10-CM as an allowable code set under HIPAA,
OR
The Secretary grants an exception to use the code set as a pilot project as allowed under the law,
OR
For claims which are not covered under HIPAA.
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 it is necessary to report an additional diagnosis and the preceding HI data elements have been used to report other diagnoses. If not required by this implementation guide, do not send.
Required
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
This code set is not allowed for use under HIPAA at the time of this writing. The qualifier can only be used:
If a new rule names the ICD-10-CM as an allowable code set under HIPAA,
OR
The Secretary grants an exception to use the code set as a pilot project as allowed under the law,
OR
For claims which are not covered under HIPAA.
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 on claims where anesthesiology services are being billed or reported when the provider knows the surgical code and knows the adjudication of the claim will depend on provision of the surgical code. If not required by this implementation guide, do not send.
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 Procedural 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 it is necessary to report an additional procedure and the preceding HI data elements have been used to report other procedures. 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 Procedural 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 condition information applies to the claim.
If not required by this implementation guide, do not send.
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 132: National Uniform Billing Committee (NUBC) Codes
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 it is necessary to report an additional condition code and the preceding HI data elements have been used to report other condition codes. If not required by this implementation guide, do not send.
Required
2-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
CODE
DEFINITION
BG
Condition
CODE SOURCE 132: National Uniform Billing Committee (NUBC) Codes
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 it is necessary to report an additional condition code and the preceding HI data elements have been used to report other condition codes. If not required by this implementation guide, do not send.
Required
3-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
CODE
DEFINITION
BG
Condition
CODE SOURCE 132: National Uniform Billing Committee (NUBC) Codes
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 it is necessary to report an additional condition code and the preceding HI data elements have been used to report other condition codes. If not required by this implementation guide, do not send.
Required
4-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
CODE
DEFINITION
BG
Condition
CODE SOURCE 132: National Uniform Billing Committee (NUBC) Codes
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 it is necessary to report an additional condition code and the preceding HI data elements have been used to report other condition codes. If not required by this implementation guide, do not send.
Required
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 132: National Uniform Billing Committee (NUBC) Codes
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 it is necessary to report an additional condition code and the preceding HI data elements have been used to report other condition codes. If not required by this implementation guide, do not send.
Required
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 132: National Uniform Billing Committee (NUBC) Codes
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 it is necessary to report an additional condition code and the preceding HI data elements have been used to report other condition codes. If not required by this implementation guide, do not send.
Required
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 132: National Uniform Billing Committee (NUBC) Codes
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 it is necessary to report an additional condition code and the preceding HI data elements have been used to report other condition codes. If not required by this implementation guide, do not send.
Required
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 132: National Uniform Billing Committee (NUBC) Codes
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 it is necessary to report an additional condition code and the preceding HI data elements have been used to report other condition codes. If not required by this implementation guide, do not send.
Required
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 132: National Uniform Billing Committee (NUBC) Codes
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 it is necessary to report an additional condition code and the preceding HI data elements have been used to report other condition codes. If not required by this implementation guide, do not send.
Required
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 132: National Uniform Billing Committee (NUBC) Codes
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 it is necessary to report an additional condition code and the preceding HI data elements have been used to report other condition codes. If not required by this implementation guide, do not send.
Required
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 132: National Uniform Billing Committee (NUBC) Codes
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 it is necessary to report an additional condition code and the preceding HI data elements have been used to report other condition codes. If not required by this implementation guide, do not send.
Required
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 132: National Uniform Billing Committee (NUBC) Codes
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 this information is deemed necessary by the repricer. The segment is not completed by providers. The information is completed by repricers only. If not required by this implementation guide, do not send.
TR3 Notes:
  1. This information is specific to the destination payer reported in Loop ID-2010BB.
  2. For capitated encounters, pricing or repricing information usually is not applicable and is provided to qualify other information within the claim.
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
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 this information is deemed necessary by the repricer. The segment is not completed by providers. The information is completed by repricers only. If not required by this implementation guide, do not send.
INDUSTRY NAME: Repriced Saving Amount
This information is specific to the destination payer reported in Loop ID-2010BB.
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 this information is deemed necessary by the repricer. The segment is not completed by providers. The information is completed by repricers only. If not required by this implementation guide, do not send.
INDUSTRY NAME: Repricing Organization Identifier
This information is specific to the destination payer reported in Loop ID-2010BB.
Situational
5
118
Rate
O 1
R
1/9
Rate expressed in the standard monetary denomination for the currency specified
SEMANTIC: HCP05 is the pricing rate associated with per diem or flat rate repricing.
SITUATIONAL RULE: Required when this information is deemed necessary by the repricer. The segment is not completed by providers. The information is completed by repricers only. If not required by this implementation guide, do not send.
INDUSTRY NAME: Repricing Per Diem or Flat Rate Amount
This information is specific to the destination payer reported in Loop ID-2010BB.
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 this information is deemed necessary by the repricer. The segment is not completed by providers. The information is completed by repricers only. If not required by this implementation guide, do not send.
INDUSTRY NAME: Repriced Approved Ambulatory Patient Group Code
This information is specific to the destination payer reported in Loop ID-2010BB.
Situational
7
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: HCP07 is the approved DRG amount.
SITUATIONAL RULE: Required when this information is deemed necessary by the repricer. The segment is not completed by providers. The information is completed by repricers only. If not required by this implementation guide, do not send.
INDUSTRY NAME: Repriced Approved Ambulatory Patient Group Amount
This information is specific to the destination payer reported in Loop ID-2010BB.
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 this information is deemed necessary by the repricer. The segment is not completed by providers. The information is completed by repricers only. If not required by this implementation guide, do not send.
This information is specific to the destination payer reported in Loop ID-2010BB.
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 this information is deemed necessary by the repricer. The segment is not completed by providers. The information is completed by repricers only. If not required by this implementation guide, do not send.
This information is specific to the destination payer reported in Loop ID-2010BB.
CODE
DEFINITION
1
Procedure Followed (Compliance)
2
Not Followed - Call Not Made (Non-Compliance Call Not Made)
3
Not Medically Necessary (Non-Compliance Non-Medically Necessary)
4
Not Followed Other (Non-Compliance Other)
5
Emergency Admit to Non-Network Hospital
Situational
15
1527
Exception Code
O 1
ID
1/2
Code specifying the exception reason for consideration of out-of-network health care services
SEMANTIC: HCP15 is the exception reason generated by a third party organization.
SITUATIONAL RULE: Required when this information is deemed necessary by the repricer. The segment is not completed by providers. The information is completed by repricers only. If not required by this implementation guide, do not send.
This information is specific to the destination payer reported in Loop ID-2010BB.
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 this claim involves a referral. If not required by this implementation guide, do not send.
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. 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✱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 the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Referring Provider First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when the middle name or initial of the person is needed to identify the individual. If not required by this implementation guide, do not send.
INDUSTRY NAME: Referring Provider Middle Name or Initial
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when the name suffix is needed to identify the individual. 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 for providers on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider has received an NPI and the NPI is available to the submitter.ORRequired for providers prior to the mandated HIPAA NPI implementation date when the provider has received an NPI and the submitter has the capability to send it.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 and 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 for providers on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider has received an NPI and the NPI is available to the submitter.ORRequired for providers prior to the mandated HIPAA NPI implementation date when the provider has received an NPI and the submitter has the capability to send it.If not required by this implementation guide, do not send.
INDUSTRY NAME: Referring Provider 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

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:
3
Situational Rule:
Required prior to the mandated HIPAA National Provider Identifier (NPI) implementation date when an identification number other than the NPI is necessary for the receiver to identify the provider.
OR
Required on or after the mandated NPI Implementation Date when NM109 in this loop is not used and an identification number other than the NPI is necessary for the receiver to identify the provider.
If not required by this implementation guide, do not send.
TR3 Notes:
The REF segment in Loop ID-2310 applies to the entire claim unless overridden on the service line level by the presence of a REF segment with the same value in REF01.
TR3 Example:
REF✱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
1G
Provider UPIN Number
UPINs must be formatted as either X99999 or XXX999.
G2
Provider Commercial Number
This code designates a proprietary provider number for the destination payer identified in the Payer Name loop, Loop ID-2010BB, associated with this claim. 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, do not send.
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. 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✱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 NM102 = 1 (person) and the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Rendering Provider First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when NM102 = 1 (person) and the middle name or initial of the person is needed to identify the individual. 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 NM102 = 1 (person) and the name suffix of the person is needed to identify the individual. If not required by this implementation guide, do not send.
INDUSTRY NAME: 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 for providers in the United States or its territories on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider is eligible to receive an NPI.ORRequired for providers not in the United States or its territories on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider has received an NPI.ORRequired for providers prior to the mandated NPI implementation date when the provider has received an NPI and the submitter has the capability to send it.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 and 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 for providers in the United States or its territories on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider is eligible to receive an NPI.ORRequired for providers not in the United States or its territories on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider has received an NPI.ORRequired for providers prior to the mandated NPI implementation date when the provider has received an NPI and the submitter has the capability to send it.If not required by this implementation guide, do not send.
INDUSTRY NAME: Rendering Provider 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

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 adjudication is known to be impacted by the provider taxonomy code. If not required by this implementation guide, do not send.
TR3 Notes:
The PRV segment in Loop ID-2310 applies to the entire claim unless overridden on the service line level by the presence of a PRV segment with the same value in PRV01.
TR3 Example:
PRV✱PE✱PXC✱1223G0001X~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1221
Provider Code
M 1
ID
1/3
Code identifying the type of provider
CODE
DEFINITION
PE
Performing
Required
2
128
Reference Identification Qualifier
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:
4
Situational Rule:
Required prior to the mandated HIPAA National Provider Identifier (NPI) implementation date when an identification number other than the NPI is necessary for the receiver to identify the provider.
OR
Required on or after the mandated NPI Implementation Date when NM109 in this loop is not used and an identification number other than the NPI is necessary for the receiver to identify the provider.
If not required by this implementation guide, do not send.
TR3 Notes:
The REF segment in Loop ID-2310 applies to the entire claim unless overridden on the service line level by the presence of a REF segment with the same value in REF01.
TR3 Example:
REF✱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
1G
Provider UPIN Number
UPINs must be formatted as either X99999 or XXX999.
G2
Provider Commercial Number
This code designates a proprietary provider number for the destination payer identified in the Payer Name loop, Loop ID-2010BB, associated with this claim. 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:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when the location of health care service is different than that carried in Loop ID-2010AA (Billing Provider).
If not required by this implementation guide, do not send.
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 Loop ID-2310E - Ambulance Pick-up Location and Loop ID-2310F - Ambulance Drop-off Location.
  3. 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✱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 the service location to be identified has an NPI and is not a component or subpart of the Billing Provider entity.If not required by this implementation guide, do not send.
CODE
DEFINITION
XX
Centers for Medicare and Medicaid Services National Provider Identifier
CODE SOURCE 537: Centers for Medicare and 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 the service location to be identified has an NPI and is not a component or subpart of the Billing Provider entity.If not required by this implementation guide, do not send.
INDUSTRY NAME: Laboratory or Facility Primary Identifier
Not Used
10
706
Entity Relationship Code
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 there is a second address line. 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 - 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 prior to the mandated HIPAA National Provider Identifier (NPI) implementation date when an identification number other than the NPI is necessary for the receiver to identify the provider.
OR
Required on or after the mandated NPI Implementation Date when NM109 in this loop is not used and an identification number other than the NPI is necessary for the receiver to identify the provider.
If not required by this implementation guide, do not send.
TR3 Example:
REF✱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 destination payer identified in the Payer Name loop, Loop ID-2010BB, associated with this claim. 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

PER*IC - SERVICE FACILITY 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 for Property and Casualty claims when this information is different than the information provided in Loop ID-1000A Submitter EDI Contact Information PER Segment, and Loop ID-2010AA Billing Provider Contact Information PER segment and when deemed necessary by the submitter.
If not required by this implementation guide, do not send.
TR3 Notes:
When the communication number represents a telephone number in the United States and other countries using the North American Dialing Plan (for voice, data, fax, etc.), the communication number must always include the area code and phone number using the format AAABBBCCCC where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number. Therefore, the following telephone number (555) 555-1234 would be represented as 5555551234. Do not submit long distance access numbers, such as "1", in the telephone number. Telephone extensions, when applicable, must be submitted in the next element immediately following the telephone number. When submitting telephone extensions, only submit the numeric extension. Do not include data that indicates an extension, such as "ext" or "x-".
TR3 Example:
PER✱IC✱JOHN SMITH✱TE✱5555551234✱EX✱123~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
366
Contact Function Code
M 1
ID
2
Code identifying the major duty or responsibility of the person or group named
CODE
DEFINITION
IC
Information Contact
Situational
2
93
Name
O 1
AN
1/60
Free-form name
SITUATIONAL RULE: Required when the name is different than the name in the Loop ID-1000A Submitter EDI Contact Information PER segment and in the Loop ID-2010AA Billing Provider Contact Information PER. If not required by this implementation guide, do not send.
Required
3
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0304
CODE
DEFINITION
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
EX
Telephone Extension
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.
Not Used
7
365
Communication Number Qualifier
O 1
ID
2
Not Used
8
364
Communication Number
O 1
AN
1/256
Not Used
9
443
Contact Inquiry Reference
O 1
AN
1/20

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 the rendering provider is supervised by a physician. 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✱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 the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Supervising Provider First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when the middle name or initial of the person is needed to identify the individual. If not required by this implementation guide, do not send.
INDUSTRY NAME: Supervising Provider Middle Name or Initial
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when the name suffix is needed to identify the individual. 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 for providers in the United States or its territories on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider is eligible to receive an NPI.ORRequired for providers not in the United States or its territories on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider has received an NPI.ORRequired for providers prior to the mandated NPI implementation date when the provider has received an NPI and the submitter has the capability to send it.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 and 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 for providers in the United States or its territories on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider is eligible to receive an NPI.ORRequired for providers not in the United States or its territories on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider has received an NPI.ORRequired for providers prior to the mandated NPI implementation date when the provider has received an NPI and the submitter has the capability to send it.If not required by this implementation guide, do not send.
INDUSTRY NAME: Supervising Provider 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

REF - SUPERVISING PROVIDER SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
4
Situational Rule:
Required prior to the mandated HIPAA National Provider Identifier (NPI) implementation date when an identification number other than the NPI is necessary for the receiver to identify the provider.
OR
Required on or after the mandated NPI implementation date when the entity is not a Health Care provider (a.k.a. an atypical provider), and an identifier is necessary for the claims processor to identify the entity.
If not required by this implementation guide, do not send.
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
1G
Provider UPIN Number
UPINs must be formatted as either X99999 or XXX999.
G2
Provider Commercial Number
This code designates a proprietary provider number for the destination payer identified in the Payer Name loop, Loop ID-2010BB, associated with this claim. 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 billing for ambulance or non-emergency transportation services. 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✱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:
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".)
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 there is a second address line. 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 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 billing for ambulance or non-emergency transportation services. 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~
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 drop-off location name is known. 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 there is a second address line. 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.
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

SBR - OTHER SUBSCRIBER INFORMATION

X12 Name:
Subscriber Information
X12 Purpose:
To record information specific to the primary insured and the insurance carrier for that insured
X12 Set Notes:
NOTE: Loop 2320 contains insurance information about: paying and other Insurance Carriers for that Subscriber, Subscriber of the Other Insurance Carriers, School or Employer Information for that Subscriber.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when other payers are known to potentially be involved in paying on this claim. If not required by this implementation guide, do not send.
TR3 Notes:
  1. All information contained in Loop ID-2320 applies only to the payer identified in Loop ID-2330B of this iteration of Loop ID-2320. 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. See Crosswalking COB Data Elements section for more information on handling COB in the 837.
TR3 Example:
SBR✱S✱01✱GR00786✱✱✱✱✱✱13~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1138
Payer Responsibility Sequence Number Code
M 1
ID
1
Code identifying the insurance carrier's level of responsibility for a payment of a claim
Within a given claim, the various values for the Payer Responsibility Sequence Number Code (other than value "U") may occur no more than once.
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
This code may only be used in payer to payer COB claims when the original payer determined the presence of this coverage from eligibility files received from this payer or when the original claim did not provide the responsibility sequence for this payer.
Required
2
1069
Individual Relationship Code
O 1
ID
2
Code indicating the relationship between two individuals or entities
SEMANTIC: SBR02 specifies the relationship to the person insured.
CODE
DEFINITION
01
Spouse
18
Self
19
Child
20
Employee
21
Unknown
39
Organ Donor
40
Cadaver Donor
53
Life Partner
G8
Other Relationship
Situational
3
127
Reference Identification
O 1
AN
1/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 the subscriber's identification card for the non-destination payer identified in Loop ID-2330B of this iteration of Loop ID-2320 shows a group number. If not required by this implemetation 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 SBR03 is not used and the group name is available. If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Insured Group Name
Situational
5
1336
Insurance Type Code
O 1
ID
1/3
Code identifying the type of insurance policy within a specific insurance program
SITUATIONAL RULE: Required when the payer identified in Loop ID-2330B for this iteration of Loop ID-2320 is Medicare and Medicare is not the primary payer (Loop ID-2320 SBR01 is not P). If not required by this implementation guide, do not send.
CODE
DEFINITION
12
Medicare Secondary Working Aged Beneficiary or Spouse with Employer Group Health Plan
13
Medicare Secondary End-Stage Renal Disease Beneficiary in the Mandated Coordination Period with an Employer's Group Health Plan
14
Medicare Secondary, No-fault Insurance including Auto is Primary
15
Medicare Secondary Worker's Compensation
16
Medicare Secondary Public Health Service (PHS)or Other Federal Agency
41
Medicare Secondary Black Lung
42
Medicare Secondary Veteran's Administration
43
Medicare Secondary Disabled Beneficiary Under Age 65 with Large Group Health Plan (LGHP)
47
Medicare Secondary, Other Liability Insurance is Primary
Not Used
6
1143
Coordination of Benefits Code
O 1
ID
1
Not Used
7
1073
Yes/No Condition or Response Code
O 1
ID
1
Not Used
8
584
Employment Status Code
O 1
ID
2
Required
9
1032
Claim Filing Indicator Code
O 1
ID
1/2
Code identifying type of claim
CODE
DEFINITION
11
Other Non-Federal Programs
12
Preferred Provider Organization (PPO)
13
Point of Service (POS)
14
Exclusive Provider Organization (EPO)
15
Indemnity Insurance
16
Health Maintenance Organization (HMO) Medicare Risk
17
Dental Maintenance Organization
AM
Automobile Medical
BL
Blue Cross/Blue Shield
CH
Champus
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:
Situational
Segment Usage:
Situational
Segment Repeat:
5
Situational Rule:
Required when the claim has been adjudicated by the payer identified in this loop, and 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. Codes and associated amounts must come from either paper remittance advice or 835s (Electronic Remittance Advice) received on the claim. When the information originates from a paper remittance advice that does not use the standard Claim Adjustment Reason Codes, the paper values must be converted to standard Claim Adjustment Reason Codes.
  4. 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
CR
Correction and Reversals
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:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the claim has been adjudicated by the payer identified in Loop ID-2330B of this loop.
OR
Required when Loop ID-2010AC is present. In this case, the claim is a post payment recovery claim submitted by a subrogated Medicaid agency.
If not required by this implementation guide, do not send.
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
  1. It is acceptable to show "0" as the amount paid.
  2. When Loop ID-2010AC is present, this is the amount the Medicaid agency actually paid.
Not Used
3
478
Credit/Debit Flag Code
O 1
ID
1

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

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

AMT*EAF - REMAINING PATIENT LIABILITY

X12 Name:
Monetary Amount Information
X12 Purpose:
To indicate the total monetary amount
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the Other Payer identified in Loop ID-2330B (of this iteration of Loop ID-2320) has adjudicated this claim and provided claim level information only.
OR
Required when the Other Payer identified in Loop ID-2330B (of this iteration of Loop ID-2320) has adjudicated this claim and the provider received a paper remittance advice and the provider does not have the ability to report line item information.
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. This segment is only used in provider submitted claims. It is not used in Payer-to-Payer Coordination of Benefits (COB).
  3. This segment is not used if the line level (Loop ID-2430) Remaining Patient Liability AMT segment is used for this Other Payer.
TR3 Example:
AMT✱EAF✱75~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
522
Amount Qualifier Code
M 1
ID
1/3
Code 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

OI - OTHER INSURANCE COVERAGE INFORMATION

X12 Name:
Other Health Insurance Information
X12 Purpose:
To specify information associated with other health insurance coverage
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
All information contained in the OI segment applies only to the payer identified in Loop ID-2330B in this iteration of Loop ID-2320.
TR3 Example:
OI✱✱✱Y✱B✱✱Y~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Not Used
1
1032
Claim Filing Indicator Code
O 1
ID
1/2
Not Used
2
1383
Claim Submission Reason Code
O 1
ID
2
Required
3
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: OI03 is the assignment of benefits indicator. A "Y" value indicates insured or authorized person authorizes benefits to be assigned to the provider; an "N" value indicates benefits have not been assigned to the provider.
INDUSTRY NAME: Benefits Assignment Certification Indicator
  1. This is a crosswalk from CLM08 when doing COB.
  2. 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
4
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 a signature was executed on the patient's behalf under state or federal law. If not required by this implementation guide, do not send.
This is a crosswalk from CLM10 when doing COB.
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.
Not Used
5
1360
Provider Agreement Code
O 1
ID
1
Required
6
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
  1. This is a crosswalk from CLM09 when doing COB.
  2. The Release of Information response is limited to the information carried in this claim.
CODE
DEFINITION
I
Informed Consent to Release Medical Information for Conditions or Diagnoses Regulated by Federal Statutes
Required when the provider has not collected a signature AND state or federal laws do not require a signature be collected.
Y
Yes, Provider has a Signed Statement Permitting Release of Medical Billing Data Related to a Claim
Required when the provider has collected a signature.
OR
Required when state or federal laws require a signature be collected.

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:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when outpatient adjudication information is reported in the remittance advice
OR
Required when it is necessary to report remark codes.
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 returned in the remittance advice. If not required by this implementation guide, do not send.
INDUSTRY NAME: Reimbursement Rate
Situational
2
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: MOA02 is the claim Health Care Financing Administration Common Procedural Coding System (HCPCS) payable amount.
SITUATIONAL RULE: Required when returned in the remittance advice. If not required by this implementation guide, do not send.
INDUSTRY NAME: HCPCS Payable Amount
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 returned in the remittance advice. 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 returned in the remittance advice. 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 returned in the remittance advice. 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 returned in the remittance advice. 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 returned in the remittance advice. 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 returned in the remittance advice. 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 returned in the remittance advice. 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:
  1. If the patient can be uniquely identified to the Other Payer indicated in this iteration of Loop ID-2320 by a unique Member Identification Number, then the patient is the subscriber or is considered to be the subscriber and is identified in this Other Subscriber's Name Loop ID-2330A.
  2. If the patient is a dependent of the subscriber for this other coverage and cannot be uniquely identified to the Other Payer indicated in this iteration of Loop ID-2320 by a unique Member Identification Number, then the subscriber for this other coverage is identified in this Other Subscriber's Name Loop ID-2330A.
  3. See Crosswalking COB Data Elements section for more information on handling COB in the 837.
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 NM102 = 1 (person) and the person has a first name. 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 NM102 = 1 (person) and the middle name or initial of the person is needed to identify the individual. If not required by this implementation guide, do not send.
INDUSTRY NAME: 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 NM102 = 1 (person) and the name suffix of the person is needed to identify the individual. If not required by this implementation guide, do not send.
INDUSTRY NAME: 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
The code MI is intended to be the subscriber's identification number as assigned by the payer. (For example, Insured's ID, Subscriber's ID, Health Insurance Claim Number (HIC), etc.)

MI is also intended to be used in claims submitted to the Indian Health Service/Contract Health Services (IHS/CHS) Fiscal Intermediary for the purpose of reporting the Tribe Residency Code (Tribe County State). In the event that a Social Security Number (SSN) is also available on an IHS/CHS claim, put the SSN in REF02.

When sending the Social Security Number as the Member ID, it 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
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 the information is available. If not required by this implementation guide, do not send.
TR3 Example:
N3✱123 MAIN STREET~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Other Subscriber Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when there is a second address line. If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Insured Address Line

N4 - OTHER SUBSCRIBER CITY, STATE, ZIP CODE

X12 Name:
Geographic Location
X12 Purpose:
To specify the geographic place of the named party
X12 Syntax:
  1. E0207
    Only one of N402 or N407 may be present.
  2. 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 the information is available. If not required by this implementation guide, do not send.
TR3 Example:
N4✱KANSAS CITY✱MO✱64108~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
INDUSTRY NAME: Other 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 SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when an additional identification number to that provided in NM109 of this loop is necessary for the claim processor to identify the entity. If not required by this implementation guide, do not send.
TR3 Example:
REF✱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 Notes:
See Crosswalking COB Data Elements section for more information on handling COB in the 837.
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
Use code value "PI" when reporting Payor Identification.
Use code value "XV" when reporting Health Plan ID (HPID) or Other Entity Identifier (OEID).

Prior to the mandated implementation date for Health Plan Identifier, willing trading partners may agree to:
1. Follow a dual use approach in which both the HPID or OEID and the Payor Identification are sent. Send XV qualifier in NM108 with HPID or OEID in NM109 and the Payor Identification, that would have been sent using qualifier PI, in the corresponding REF segment using qualifier 2U (Payer Identification Number).
OR
2. Follow an early implementation approach in which the HPID or OEID is sent in NM109.
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

N3 - OTHER PAYER ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the payer address is available and the submitter intends for the claim to be printed on paper at the next EDI location (for example, a clearinghouse). If not required by this implementation guide, do not send.
TR3 Example:
N3✱123 MAIN STREET~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Other Payer Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when there is a second address line. If not required by this implementation guide, do not send.
INDUSTRY NAME: Other Payer Address Line

N4 - OTHER PAYER CITY, STATE, ZIP CODE

X12 Name:
Geographic Location
X12 Purpose:
To specify the geographic place of the named party
X12 Syntax:
  1. E0207
    Only one of N402 or N407 may be present.
  2. 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 the payer address is available and the submitter intends for the claim to be printed on paper at the next EDI location (for example, a clearinghouse). If not required by this implementation guide, do not send.
TR3 Example:
N4✱KANSAS CITY✱MO✱64108~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
INDUSTRY NAME: Other Payer City Name
Situational
2
156
State or Province Code
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 Payer 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 Payer 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

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:
Situational
Segment Repeat:
1
Situational Rule:
Required when the payer identified in this loop has previously adjudicated the claim and Loop ID-2430, Line Check or Remittance Date, is not used. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱573✱D8✱20040203~
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:
2
Situational Rule:
Required when an additional identification number to that provided in the NM109 of this loop is necessary to identify the entity. If not required by this implementation guide, do not send.
TR3 Example:
REF✱2U✱98765~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
2U
Payer Identification Number
This code is only allowed when the qualifier XV is reported in NM108 of this loop.
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*G1 - OTHER PAYER PRIOR AUTHORIZATION NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the payer identified in this loop has assigned a prior authorization number to this claim.
If not required by this implementation guide, do not send.
TR3 Example:
REF✱G1✱AB333-Y5~
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: Other Payer Prior Authorization Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*9F - OTHER PAYER REFERRAL NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the payer identified in this loop has assigned a referral number to this claim.
If not required by this implementation guide, do not send.
TR3 Example:
REF✱9F✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code 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: Other Payer Prior Authorization or Referral Number
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 the claim is being sent in the payer-to-payer COB model,
AND
the destination payer is secondary to the payer identified in this Loop ID-2330B,
AND
the payer identified in this Loop ID-2330B has re-adjudicated the 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 it is necessary to identify the Other Payer's Claim Control Number in a payer-to-payer COB situation.
OR
Required when the Other Payer's Claim Control Number is available.
If not required by this implementation guide, do not send.
TR3 Example:
REF✱F8✱R555588~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
INDUSTRY NAME: Hierarchical Level Code
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: Hierarchical Child Code
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

NM1 - OTHER PAYER REFERRING PROVIDER

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Segments NM1-N4 contain name and address information of the insurance carriers referenced in loop 2320.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required prior to the mandated implementation of the HIPAA National Provider Identifier (NPI) rule when the provider in the corresponding Loop ID-2310 is sent and one or more additional payer-specific provider identification numbers are required by this non-destination payer (Loop ID-2330B) to identify the provider.
OR
Required after the mandated implementation of the NPI rule for providers who are not Health Care Providers when the provider is sent in the corresponding Loop ID-2310 and one or more additional payer-specific provider identification numbers are required by this non-destination payer (Loop ID-2330B) to identify the provider.
If not required by this implementation guide, do not send.
TR3 Notes:
See Crosswalking COB Data Elements section for more information on handling COB in the 837.
TR3 Example:
NM1✱DN✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
DN
Referring Provider
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
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

REF - OTHER PAYER REFERRING PROVIDER SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
3
TR3 Notes:
  1. Non-destination (COB) payer's provider identification number(s).
  2. See Crosswalking COB Data Elements section for more information on handling COB in the 837.
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
1G
Provider UPIN Number
UPINs must be formatted as either X99999 or XXX999.
G2
Provider Commercial Number
This code designates a proprietary provider number for the non-destination payer identified in the Other Payer Name Loop ID-2330B for this iteration of Loop ID-2320. This is true regardless of whether that payer is Medicare, Medicaid, a Blue Cross Blue Shield plan, a commercial plan, or any other health plan.
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 Referring Provider Identifier
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

NM1*82 - OTHER PAYER RENDERING PROVIDER

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Segments NM1-N4 contain name and address information of the insurance carriers referenced in loop 2320.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required prior to the mandated implementation of the HIPAA National Provider Identifier (NPI) rule when the provider in the corresponding Loop ID-2310 is sent and one or more additional payer-specific provider identification numbers are required by this non-destination payer (Loop ID-2330B) to identify the provider.
OR
Required after the mandated implementation of the NPI rule for providers who are not Health Care Providers when the provider is sent in the corresponding Loop ID-2310 and one or more additional payer-specific provider identification numbers are required by this non-destination payer (Loop ID-2330B) to identify the provider.
If not required by this implementation guide, do not send.
TR3 Notes:
See Crosswalking COB Data Elements section for more information on handling COB in the 837.
TR3 Example:
NM1✱82✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
82
Rendering Provider
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code 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
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

REF - OTHER PAYER RENDERING PROVIDER SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
3
TR3 Notes:
See Crosswalking COB Data Elements section for more information on handling COB in the 837.
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
1G
Provider UPIN Number
UPINs must be formatted as either X99999 or XXX999.
G2
Provider Commercial Number
This code designates a proprietary provider number for the non-destination payer identified in the Other Payer Name Loop ID-2330B for this iteration of Loop ID-2320. This is true regardless of whether that payer is Medicare, Medicaid, a Blue Cross Blue Shield plan, a commercial plan, or any other health plan.
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: Other Payer Rendering Provider Secondary Identifier
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

NM1*77 - OTHER PAYER SERVICE FACILITY LOCATION

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Segments NM1-N4 contain name and address information of the insurance carriers referenced in loop 2320.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required prior to the mandated implementation of the HIPAA National Provider Identifier (NPI) rule when the provider in the corresponding Loop ID-2310 is sent and one or more additional payer-specific provider identification numbers are required by this non-destination payer (Loop ID-2330B) to identify the provider.
OR
Required after the mandated implementation of the NPI rule for providers who are not Health Care Providers when the provider is sent in the corresponding Loop ID-2310 and one or more additional payer-specific provider identification numbers are required by this non-destination payer (Loop ID-2330B) to identify the provider.
If not required by this implementation guide, do not send.
TR3 Notes:
See Crosswalking COB Data Elements section for more information on handling COB in the 837.
TR3 Example:
NM1✱77✱2~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
77
Service Location
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code 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

REF - OTHER PAYER 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:
Required
Segment Repeat:
3
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 non-destination payer identified in the Other Payer Name Loop ID-2330B for this iteration of Loop ID-2320. This is true regardless of whether that payer is Medicare, Medicaid, a Blue Cross Blue Shield plan, a commercial plan, or any other health plan.
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: Other Payer 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 - OTHER PAYER SUPERVISING PROVIDER

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Segments NM1-N4 contain name and address information of the insurance carriers referenced in loop 2320.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required prior to the mandated implementation of the HIPAA National Provider Identifier (NPI) rule when the provider in the corresponding Loop ID-2310 is sent and one or more additional payer-specific provider identification numbers are required by this non-destination payer (Loop ID-2330B) to identify the provider.
OR
Required after the mandated implementation of the NPI rule for providers who are not Health Care Providers when the provider is sent in the corresponding Loop ID-2310 and one or more additional payer-specific provider identification numbers are required by this non-destination payer (Loop ID-2330B) to identify the provider.
If not required by this implementation guide, do not send.
TR3 Notes:
See Crosswalking COB Data Elements section for more information on handling COB in the 837.
TR3 Example:
NM1✱DQ✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
DQ
Supervising Physician
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
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

REF - OTHER PAYER SUPERVISING PROVIDER SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
3
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
1G
Provider UPIN Number
UPINs must be formatted as either X99999 or XXX999.
G2
Provider Commercial Number
This code designates a proprietary provider number for the non-destination payer identified in the Other Payer Name Loop ID-2330B for this iteration of Loop ID-2320. This is true regardless of whether that payer is Medicare, Medicaid, a Blue Cross Blue Shield plan, a commercial plan, or any other health plan.
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: Other Payer Supervising Provider Identifier
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

NM1*85 - OTHER PAYER BILLING PROVIDER

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Segments NM1-N4 contain name and address information of the insurance carriers referenced in loop 2320.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required prior to the mandated implementation of the HIPAA National Provider Identifier (NPI) rule when the provider in the corresponding Loop ID-2310 is sent and one or more additional payer-specific provider identification numbers are required by this non-destination payer (Loop ID-2330B) to identify the provider.
OR
Required after the mandated implementation of the NPI rule for providers who are not Health Care Providers when the provider is sent in the corresponding Loop ID-2310 and one or more additional payer-specific provider identification numbers are required by this non-destination payer (Loop ID-2330B) to identify the provider.
If not required by this implementation guide, do not send.
TR3 Notes:
See Crosswalking COB Data Elements section for more information on handling COB in the 837.
TR3 Example:
NM1✱85✱2~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
85
Billing Provider
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code 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
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

REF - OTHER PAYER BILLING PROVIDER SECONDARY IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
2
TR3 Notes:
See Crosswalking COB Data Elements section for more information on handling COB in the 837.
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 non-destination payer identified in the Other Payer Name Loop ID-2330B for this iteration of Loop ID-2320. This is true regardless of whether that payer is Medicare, Medicaid, a Blue Cross Blue Shield plan, a commercial plan, or any other health plan.
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: Other Payer Billing Provider 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.1.2 for more information on bundling and unbundling.
TR3 Example:
LX✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
554
Assigned Number
M 1
N
1/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 NDC number is used for reporting prescribed drugs and biologics when required by government regulation, or as deemed by the provider to enhance claim reporting or adjudication processes. The NDC number is reported in the LIN segment of Loop ID-2410 only.
CODE
DEFINITION
ER
Jurisdiction Specific Procedure and Supply Codes
This code set is not allowed for use under HIPAA at the time of this writing. The qualifier can only be used:
If a new rule names the Jurisdiction Specific Procedure and Supply Codes as an allowable code set under HIPAA,
OR
The Secretary grants an exception to use the code set as a pilot project as allowed under the law,
OR
For claims which are not covered under HIPAA.
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 Procedural Coding System
IV
Home Infusion EDI Coalition (HIEC) Product/Service Code
This code set is not allowed for use under HIPAA at the time of this writing. The qualifier can only be used:
If a new rule names the Home Infusion EDI Coalition (HIEC) Product/Service Codes as an allowable code set under HIPAA,
OR
The Secretary grants an exception to use the code set as a pilot project as allowed under the law,
OR
For claims which are not covered under HIPAA.
CODE SOURCE 513: Home Infusion EDI Coalition (HIEC) Product/Service Code List
WK
Advanced Billing Concepts (ABC) Codes
At the time of this writing, this code set has been approved by the Secretary of HHS as a pilot project allowed under HIPAA law.
The qualifier may only be used in transactions covered under HIPAA;
By parties registered in the pilot project and their trading partners,
OR
If a new rule names the Complementary, Alternative, or Holistic Procedure Codes as an allowable code set under HIPAA,
OR
For claims which are not covered under HIPAA.
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 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
1-4
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when a second modifier clarifies or improves the reporting accuracy of the associated procedure code. If not required by this implementation guide, do not send.
Situational
1-5
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when a third modifier clarifies or improves the reporting accuracy of the associated procedure code. If not required by this implementation guide, do not send.
Situational
1-6
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when a fourth modifier clarifies or improves the reporting accuracy of the associated procedure code. If not required by this implementation guide, do not send.
Situational
1-7
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
SITUATIONAL RULE: Required when, in the judgment of the submitter, the Procedure Code does not definitively describe the service/product/supply and loop 2410 is not used.ORRequired when SV101-2 is a non-specific Procedure Code. Non-specific codes may include in their descriptors terms such as: Not Otherwise Classified (NOC); Unlisted; Unspecified; Unclassified; Other; Miscellaneous; Prescription Drug, Generic; or Prescription Drug, Brand Name.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. 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.
  2. Zero "0" is an acceptable value for this element.
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
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.
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 value is different than value carried in CLM05-1 in Loop ID-2300. If not required by this implementation guide, do not send.
INDUSTRY NAME: Place of Service Code
See CODE SOURCE 237: Place of Service Codes for Professional Claims
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.
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 it is necessary to point to a second diagnosis related to this service line. Acceptable values are the same as SV107-1. 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 it is necessary to point to a third diagnosis related to this service line. Acceptable values are the same as SV107-1. 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 it is necessary to point to a fourth diagnosis related to this service line. Acceptable values are the same as SV107-1. 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 the service is known to be an emergency by the provider. If not required by this implementation guide, do not send.
INDUSTRY NAME: Emergency Indicator
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.
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 Medicaid services are the result of a screening referral.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 applicable for Medicaid claims. 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 patient is exempt from co-pay. If not required by this implementation guide, do not send.
INDUSTRY NAME: Co-Pay Status Code
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

SV5 - DURABLE MEDICAL EQUIPMENT SERVICE

X12 Name:
Durable Medical Equipment Service
X12 Purpose:
To specify the claim service detail for durable medical equipment
X12 Syntax:
  1. R0405
    At least one of SV504 or SV505 is required.
  2. C0604
    If SV506 is present, then SV504 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when necessary to report both the rental and purchase price information for durable medical equipment. This is not used for claims where the provider is reporting only the rental price or only the purchase price. If not required by this implementation guide, do not send.
TR3 Example:
SV5✱HC:A4631✱DA✱30✱50✱5000✱4~
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: Procedure Identifier
CODE
DEFINITION
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 Procedural Coding System
Required
1-2
234
Product/Service ID
M 1
AN
1/48
Identifying number for a product or service
INDUSTRY NAME: Procedure Code
This value must be the same as that reported in SV101-2.
Not Used
1-3
1339
Procedure Modifier
O 1
AN
2
Not Used
1-4
1339
Procedure Modifier
O 1
AN
2
Not Used
1-5
1339
Procedure Modifier
O 1
AN
2
Not Used
1-6
1339
Procedure Modifier
O 1
AN
2
Not Used
1-7
352
Description
O 1
AN
1/80
Not Used
1-8
234
Product/Service ID
O 1
AN
1/48
Required
2
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
CODE
DEFINITION
DA
Days
Required
3
380
Quantity
M 1
R
1/15
Numeric value of quantity
SEMANTIC: SV503 is the length of medical treatment required.
INDUSTRY NAME: Length of Medical Necessity
Required
4
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: SV504 is the rental price.
SEGMENT SYNTAX: R0405, C0604
INDUSTRY NAME: DME Rental Price
Required
5
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: SV505 is the purchase price.
SEGMENT SYNTAX: R0405
INDUSTRY NAME: DME Purchase Price
Required
6
594
Frequency Code
O 1
ID
1
Code indicating frequency or type of activities or actions being reported
SEMANTIC: SV506 is the frequency at which the rental equipment is billed.
SEGMENT SYNTAX: C0604
INDUSTRY NAME: Rental Unit Price Indicator
CODE
DEFINITION
1
Weekly
4
Monthly
6
Daily
Not Used
7
923
Prognosis 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 there is a paper attachment following this claim.
OR
Required when attachments are sent electronically (PWK02 = EL) but are transmitted in another functional group (for example, 275) rather than by paper. PWK06 is then used to identify the attached electronic documentation. The number in PWK06 is carried in the TRN of the electronic attachment.
OR
Required when the provider deems it necessary to identify additional information that is being held at the provider's office and is available upon request by the payer (or appropriate entity), but the information is not being submitted with the claim. Use the value of "AA" in PWK02 to convey this specific use of the PWK segment.
If not required by this implementation guide, do not send.
TR3 Example:
PWK✱OZ✱BM✱✱✱AC✱DMN0012~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
755
Report Type Code
M 1
ID
2
Code indicating the title or contents of a document, report or supporting item
INDUSTRY NAME: Attachment Report Type Code
CODE
DEFINITION
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
Required when the actual attachment is maintained by an attachment warehouse or similar vendor.
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
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 PWK02 = "BM", "EL", "EM", "FX" or "FT". If not required by this implementation guide, do not send.
CODE
DEFINITION
AC
Attachment Control Number
Situational
6
67
Identification Code
O 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when PWK02 = "BM", "EL", "EM", "FX" or "FT". If not required by this implementation guide, do not send.
INDUSTRY NAME: Attachment Control Number
  1. PWK06 is 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 on claims that include a Durable Medical Equipment Regional Carrier (DMERC) Certificate of Medical Necessity (CMN). If not required by this implementation guide, do not send.
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
Required when the actual attachment is maintained by an attachment warehouse or similar vendor.
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 on ambulance transport services when the information applicable to any one of the segment's elements is different than the information reported in the CR1 at the claim level (Loop ID-2300). If not required by this implementation guide, do not send.
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 CR102 is used. 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 it is necessary to justify the medical necessity of the level of ambulance services. 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 the ambulance service is for a round trip. 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 needed to justify usage of stretcher. 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 a Durable Medical Equipment Regional Carrier Certificate of Medical Necessity (DMERC CMN) or a DMERC Information Form (DIF) or Oxygen Therapy Certification is included on this service line.
If not required by this implementation guide, do not send.
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 on ambulance transport services when the information applicable to any one of the segment's elements is different than the information reported in the Ambulance Certification CRC at the claim level (Loop ID-2300). If not required by this implementation guide, do not send.
TR3 Notes:
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.
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 a second condition code is necessary. 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 a third condition code is necessary. 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 a fourth condition code is necessary. 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 a fifth condition code is necessary. 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 on all Medicare claims involving physician services to hospice patients. 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.
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 a Durable Medical Equipment Regional Carrier Certificate of Medical Necessity (DMERC CMN) or a DMERC Information Form (DIF), or Oxygen Therapy Certification is included on this service line and the information is necessary for adjudication.
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.
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 a second condition code is necessary. 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:
In cases where a drug is being billed on a service line, date range may be used to indicate drug duration for which the drug supply will be used by the patient. The difference in dates, including both the begin and end dates, are the days supply of the drug. Example: 20000101 - 20000107 (1/1/00 to 1/7/00) is used for a 7 day supply where the first day of the drug used by the patient is 1/1/00. In the event a drug is administered on less than a daily basis (for example, every other day) the date range would include the entire period during which the drug was supplied, including the last day the drug was used. Example: 20000101 - 20000108 (1/1/00 to 1/8/00) is used for an 8 days supply where the prescription is written for Q48 (every 48 hours), four doses of the drug are dispensed and the first dose is used on 1/1/00.
TR3 Example:
DTP✱472✱RD8✱20050314-20050325~
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 a drug is billed for this line and a prescription was written (or otherwise communicated by the prescriber if not written). If not required by this implementation guide, do not send.
TR3 Example:
DTP✱471✱D8✱20050108~
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 CR301 (DMERC Certification) = "R" or "S". If not required by this implementation guide, do not send.
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 a Durable Medical Equipment Regional Carrier Certificate of Medical Necessity (DMERC CMN) or DMERC Information Form (DIF), or Oxygen Therapy Certification is included on this service line. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱463✱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
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 a Durable Medical Equipment Regional Carrier Certificate of Medical Necessity (DMERC CMN), DMERC Information Form (DIF), or Oxygen Therapy Certification is included on this service line. If not required by this implementation guide, do not send.
TR3 Notes:
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).
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 a claim involves physician services for routine foot care; and is different than the date listed at the claim level and is known to impact the payer's adjudication process. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱304✱D8✱20050108~
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 on initial EPO claims service lines for dialysis patients when test results are being billed or reported. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱738✱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
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 billing or reporting shipped products. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱011✱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
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 claim involves spinal manipulation and an x-ray was taken and is different than information at the claim level (Loop ID-2300). If not required by this implementation guide, do not send.
TR3 Example:
DTP✱455✱D8✱20050108~
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 the Initial Treatment Date is known to impact adjudication for claims involving spinal manipulation, physical therapy, occupational therapy, or speech language pathology and when different from what is reported at the claim level. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱454✱D8✱20050108~
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 more than one patient is transported in the same vehicle for Ambulance or non-emergency transportation services. If not required by this implementation guide, do not send.
TR3 Notes:
The QTY02 is the only place to report the number of patients when there are multiple patients transported.
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 in conjunction with anesthesia for obstetric services when the anesthesia provider chooses to report additional complexity beyond the normal services reflected by the procedure base units and anesthesia time.
If not required by this implementation guide, do not send.
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 on Dialysis related service lines for ESRD. Use R1, R2, R3, or R4 to qualify the Hemoglobin, Hematocrit, Epoetin Starting Dosage, and Creatinine test results.
OR
Required on DMERC service lines to report the Patient's Height from the Certificate of Medical Necessity (CMN). Use HT qualifier.
If not required by this implementation guide, do not send.
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 the submitter is contractually obligated to supply this information on post-adjudicated claims. If not required by this implementation guide, do not send.
TR3 Notes:
The developers of this implementation guide note that the CN1 segment is for use only for post-adjudicated claims, which do not meet the definition of a health care claim under HIPAA. Consequently, at the time of this writing, the CN1 segment is for non-HIPAA use only.
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 information is different than that given at claim level (Loop ID-2300). 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 information is different than that given at claim level (Loop ID-2300). 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 information is different than that given at claim level (Loop ID-2300). 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 information is different than that given at claim level (Loop ID-2300). 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 information is different than that given at claim level (Loop ID-2300). 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 a repricing (pricing) organization needs to have an identifying number on the service line in their submission to their payer organization. This segment is not completed by providers. If not required by this implementation guide, do not send.
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 a repricing (pricing) organization needs to have an identifying number on an adjusted service line in their submission to their payer organization. This segment is not completed by providers. If not required by this implementation guide, do not send.
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:
5
Situational Rule:
Required when service line involved a prior authorization number that is different than the number reported at the claim level (Loop ID-2300).
If not required by this implementation guide, do not send.
TR3 Notes:
When it is necessary to report one or more non-destination payer Prior Authorization Numbers, the composite data element in REF04 is used to identify the payer which assigned this number.
TR3 Example:
REF✱G1✱13579~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code 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
Situational
4
C040
Reference Identifier
O 1
To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier
SEMANTIC: REF04 contains data relating to the value cited in REF02.
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C04003 or C04004 is present, then the other is required.
  2. P0506
    If either C04005 or C04006 is present, then the other is required.
SITUATIONAL RULE: Required when the Prior Authorization Number reported in REF02 of this segment is for a non-destination payer.
Required
4-1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
2U
Payer Identification Number
Required
4-2
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
INDUSTRY NAME: Other Payer Primary Identifier
The payer identifier reported in this field must match the cooresponding payer identifier reported in Loop ID-2330B NM109.
Not Used
4-3
128
Reference Identification Qualifier
O 1
ID
2/3
Not Used
4-4
127
Reference Identification
O 1
AN
1/50
Not Used
4-5
128
Reference Identification Qualifier
O 1
ID
2/3
Not Used
4-6
127
Reference Identification
O 1
AN
1/50

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 the submitter needs a line item control number for subsequent communications to or from the payer. If not required by this implementation guide, do not send.
TR3 Notes:
  1. The line item control number must be unique within a patient control number (CLM01). Payers are required to return this number in the remittance advice transaction (835) if the provider sends it to them in the 837 and adjudication is based upon line item detail regardless of whether bundling or unbundling has occurred.
  2. Submitters are STRONGLY encouraged to routinely send a unique line item control number on all service lines, particularly if the submitter automatically posts their remittance advice. Submitting a unique line item control number allows the capability to automatically post by service line.
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 mammography services are rendered by a certified mammography provider and the mammography certification number is different than that sent in Loop ID-2300. If not required by this implementation guide, do not send.
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 for all CLIA certified facilities performing CLIA covered laboratory services and the number is different than the CLIA number reported at the claim level (Loop ID-2300). If not required by this implementation guide, do not send.
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 for claims for any laboratory that referred tests to another laboratory covered by the CLIA Act that is billed on this line. If not required by this implementation guide, do not send.
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 mandated by state or federal law or regulations to report an Immunization Batch Number. If not required by this implementation guide, do not send.
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:
5
Situational Rule:
Required when this service line involved a referral number that is different than the number reported at the claim level (Loop-ID 2300).
If not required by this implementation guide, do not send.
TR3 Notes:
When it is necessary to report one or more non-destination payer Referral Numbers, the composite data element in REF04 is used to identify the payer which assigned this referral number.
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
Situational
4
C040
Reference Identifier
O 1
To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier
SEMANTIC: REF04 contains data relating to the value cited in REF02.
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C04003 or C04004 is present, then the other is required.
  2. P0506
    If either C04005 or C04006 is present, then the other is required.
SITUATIONAL RULE: Required when the Referral Number reported in REF02 of this segment is for a non-destination payer.
Required
4-1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
2U
Payer Identification Number
Required
4-2
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
INDUSTRY NAME: Other Payer Primary Identifier
The payer identifier reported in this field must match the cooresponding payer identifier reported in Loop ID-2330B NM109.
Not Used
4-3
128
Reference Identification Qualifier
O 1
ID
2/3
Not Used
4-4
127
Reference Identification
O 1
AN
1/50
Not Used
4-5
128
Reference Identification Qualifier
O 1
ID
2/3
Not Used
4-6
127
Reference Identification
O 1
AN
1/50

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 sales tax applies to the service line and the submitter is required to report that information to the receiver. If not required by this implementation guide, do not send.
TR3 Notes:
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.
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 service line charge (SV102) includes postage amount claimed in this service line. If not required by this implementation guide, do not send.
TR3 Notes:
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.
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 ALL of the following conditions are met:
• A regulatory agency concludes it must use the K3 to meet an emergency
legislative requirement;
• The administering regulatory agency or other state organization has
completed each one of the following steps:
contacted the X12N workgroup,
requested a review of the K3 data requirement to ensure there is not
an existing method within the implementation guide to meet this
requirement
• X12N determines that there is no method to meet the requirement.
If not required by this implementation guide, do not send.
TR3 Notes:
  1. At the time of publication of this implementation, K3 segments have no specific use. 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).
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 in the judgment of the provider, the information is needed to substantiate the medical treatment and is not supported elsewhere within the claim data set.
If not required by this implementation guide, do not send.
TR3 Notes:
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.
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 the TPO/repricer needs to forward additional information to the payer. This segment is not completed by providers. If not required by this implementation guide, do not send.
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 on non-vision service lines when adjudication is known to be impacted by the charge amount for services purchased from another source.
OR
Required on vision service lines when adjudication is known to be impacted by the acquisition cost of lenses.
If not required by this implementation guide, do not send.
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 this information is deemed necessary by the repricer. The segment is not completed by providers. The information is completed by repricers only. If not required by this implementation guide, do not send.
TR3 Notes:
  1. This information is specific to the destination payer reported in Loop ID-2010BB.
  2. For capitated encounters, pricing or repricing information usually is not applicable and is provided to qualify other information within the claim.
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 this information is deemed necessary by the repricer. The segment is not completed by providers. The information is completed by repricers only. 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 this information is deemed necessary by the repricer. The segment is not completed by providers. The information is completed by repricers only. 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 this information is deemed necessary by the repricer. The segment is not completed by providers. The information is completed by repricers only. 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 this information is deemed necessary by the repricer. The segment is not completed by providers. The information is completed by repricers only. If not required by this implementation guide, do not send.
INDUSTRY NAME: Repriced Approved Ambulatory Patient Group Code
Situational
7
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: HCP07 is the approved DRG amount.
SITUATIONAL RULE: Required when this information is deemed necessary by the repricer. The segment is not completed by providers. The information is completed by repricers only. If not required by this implementation guide, do not send.
INDUSTRY NAME: Repriced Approved Ambulatory Patient Group 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 this information is deemed necessary by the repricer. The segment is not completed by providers. The information is completed by repricers only. 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
This code set is not allowed for use under HIPAA at the time of this writing. The qualifier can only be used:
If a new rule names the Jurisdiction Specific Procedure and Supply Codes as an allowable code set under HIPAA,
OR
The Secretary grants an exception to use the code set as a pilot project as allowed under the law,
OR
For claims which are not covered under HIPAA.
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 Procedural Coding System
IV
Home Infusion EDI Coalition (HIEC) Product/Service Code
This code set is not allowed for use under HIPAA at the time of this writing. The qualifier can only be used:
If a new rule names the Home Infusion EDI Coalition (HIEC) Product/Service Codes as an allowable code set under HIPAA,
OR
The Secretary grants an exception to use the code set as a pilot project as allowed under the law,
OR
For claims which are not covered under HIPAA.
CODE SOURCE 513: Home Infusion EDI Coalition (HIEC) Product/Service Code List
WK
Advanced Billing Concepts (ABC) Codes
At the time of this writing, this code set has been approved by the Secretary of HHS as a pilot project allowed under HIPAA law.
The qualifier may only be used in transactions covered under HIPAA;
By parties registered in the pilot project and their trading partners,
OR
If a new rule names the Complementary, Alternative, or Holistic Procedure Codes as an allowable code set under HIPAA,
OR
For claims which are not covered under HIPAA.
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 this information is deemed necessary by the repricer. The segment is not completed by providers. The information is completed by repricers only. 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 this information is deemed necessary by the repricer. The segment is not completed by providers. The information is completed by repricers only. 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 this information is deemed necessary by the repricer. The segment is not completed by providers. The information is completed by repricers only. 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 this information is deemed necessary by the repricer. The segment is not completed by providers. The information is completed by repricers only. 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 this information is deemed necessary by the repricer. The segment is not completed by providers. The information is completed by repricers only. If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Procedure Followed (Compliance)
2
Not Followed - Call Not Made (Non-Compliance Call Not Made)
3
Not Medically Necessary (Non-Compliance Non-Medically Necessary)
4
Not Followed Other (Non-Compliance Other)
5
Emergency Admit to Non-Network Hospital
Situational
15
1527
Exception Code
O 1
ID
1/2
Code specifying the exception reason for consideration of out-of-network health care services
SEMANTIC: HCP15 is the exception reason generated by a third party organization.
SITUATIONAL RULE: Required when this information is deemed necessary by the repricer. The segment is not completed by providers. The information is completed by repricers only. 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 government regulation mandates that prescribed drugs and biologics are reported with NDC numbers.
OR
Required when the provider or submitter chooses to report NDC numbers to enhance the claim reporting or adjudication processes.
OR
Required when an HHS approved pilot project specifies reporting of Universal Product Number (UPN) by parties registered in the pilot and their trading partners.
OR
Required when government regulation mandates that medical and surgical supplies are reported with UPN's.

If not required by this implementation guide, do not send.
TR3 Notes:
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.
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: EAN.UCC Global Trade Item Number (GTIN), includes Universal Product Code
EO
EAN/UCC - 8
CODE SOURCE 41: EAN.UCC Global Trade Item Number (GTIN), includes Universal Product Code
HI
HIBC (Health Care Industry Bar Code) Supplier Labeling Standard Primary Data Message
N4
National Drug Code in 5-4-2 Format
CODE SOURCE 240: National Drug Code by Format
ON
Customer Order Number
UK
GTIN 14-digit Data Structure
CODE SOURCE 41: EAN.UCC Global Trade Item Number (GTIN), includes Universal Product Code
UP
UCC - 12
CODE SOURCE 41: EAN.UCC Global Trade Item Number (GTIN), includes Universal Product Code
Required
3
234
Product/Service ID
M 1
AN
1/48
Identifying number for a product or service
INDUSTRY NAME: National Drug Code or Universal Product Number
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 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 dispensing of the drug has been done with an assigned prescription number.
OR
Required when the provided medication involves the compounding of two or more drugs being reported and there is no prescription number.
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.
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, do not send.
TR3 Notes:
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.
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 NM102 = 1 (person) and the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Rendering Provider First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when NM102 = 1 (person) and the middle name or initial of the person is needed to identify the individual. 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 NM102 = 1 (person) and the name suffix of the person is needed to identify the individual. If not required by this implementation guide, do not send.
INDUSTRY NAME: 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 for providers in the United States or its territories on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider is eligible to receive an NPI.ORRequired for providers not in the United States or its territories on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider has received an NPI.ORRequired for providers prior to the mandated NPI implementation date when the provider has received an NPI and the submitter has the capability to send it.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 and 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 for providers in the United States or its territories on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider is eligible to receive an NPI.ORRequired for providers not in the United States or its territories on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider has received an NPI.ORRequired for providers prior to the mandated NPI implementation date when the provider has received an NPI and the submitter has the capability to send it.If not required by this implementation guide, do not send.
INDUSTRY NAME: Rendering Provider 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

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 adjudication is known to be impacted by the provider taxonomy code. If not required by this implementation guide, do not send.
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:
20
Situational Rule:
Required prior to the mandated HIPAA National Provider Identifier (NPI) implementation date when an identification number other than the NPI is necessary for the receiver to identify the provider.
OR
Required on or after the mandated NPI Implementation Date when NM109 in this loop is not used and an identification number other than the NPI is necessary for the receiver to identify the provider.
If not required by this implementation guide, do not send.
TR3 Notes:
When it is necessary to report one or more non-destination payer Secondary Identifiers, the composite data element in REF04 is used to identify the payer who assigned this identifier.
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
1G
Provider UPIN Number
UPINs must be formatted as either X99999 or XXX999.
G2
Provider Commercial Number
This code designates a proprietary provider number for the destination payer identified in the Payer Name loop, Loop ID-2010BB, associated with this claim. 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
Situational
4
C040
Reference Identifier
O 1
To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier
SEMANTIC: REF04 contains data relating to the value cited in REF02.
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C04003 or C04004 is present, then the other is required.
  2. P0506
    If either C04005 or C04006 is present, then the other is required.
SITUATIONAL RULE: Required when the identifier reported in REF02 of this segment is for a non-destination payer.
Do not use this composite when the value reported in REF01 is either 0B or 1G.
Required
4-1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
2U
Payer Identification Number
Required
4-2
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
INDUSTRY NAME: Other Payer Primary Identifier
The payer identifier reported in this field must match the cooresponding payer identifier reported in Loop ID-2330B NM109.
Not Used
4-3
128
Reference Identification Qualifier
O 1
ID
2/3
Not Used
4-4
127
Reference Identification
O 1
AN
1/50
Not Used
4-5
128
Reference Identification Qualifier
O 1
ID
2/3
Not Used
4-6
127
Reference Identification
O 1
AN
1/50

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 the service reported in this line item is a purchased service. If not required by this implementation guide, do not send.
TR3 Notes:
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.
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 for providers on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider has received an NPI and the NPI is available to the submitter.ORRequired for providers prior to the mandated HIPAA NPI implementation date when the provider has received an NPI and the submitter has the capability to send it.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 and 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 for providers on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider has received an NPI and the NPI is available to the submitter.ORRequired for providers prior to the mandated HIPAA NPI implementation date when the provider has received an NPI and the submitter has the capability to send it.If not required by this implementation guide, do not send.
INDUSTRY NAME: Purchased Service Provider 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

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:
20
Situational Rule:
Required prior to the mandated HIPAA National Provider Identifier (NPI) implementation date when an identification number other than the NPI is necessary for the receiver to identify the provider.
OR
Required on or after the mandated NPI Implementation Date when NM109 in this loop is not used and an identification number other than the NPI is necessary for the receiver to identify the provider.
If not required by this implementation guide, do not send.
TR3 Notes:
When it is necessary to report one or more non-destination payer Secondary Identifiers, the composite data element in REF04 is used to identify the payer who assigned this identifier.
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
1G
Provider UPIN Number
UPINs must be formatted as either X99999 or XXX999.
G2
Provider Commercial Number
This code designates a proprietary provider number for the destination payer identified in the Payer Name loop, Loop ID-2010BB, associated with this claim. 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
Situational
4
C040
Reference Identifier
O 1
To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier
SEMANTIC: REF04 contains data relating to the value cited in REF02.
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C04003 or C04004 is present, then the other is required.
  2. P0506
    If either C04005 or C04006 is present, then the other is required.
SITUATIONAL RULE: Required when the identifier reported in REF02 of this segment is for a non-destination payer.
Do not use this composite when the value reported in REF01 is either 0B or 1G.
Required
4-1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
2U
Payer Identification Number
Required
4-2
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
INDUSTRY NAME: Other Payer Primary Identifier
The payer identifier reported in this field must match the cooresponding payer identifier reported in Loop ID-2330B NM109.
Not Used
4-3
128
Reference Identification Qualifier
O 1
ID
2/3
Not Used
4-4
127
Reference Identification
O 1
AN
1/50
Not Used
4-5
128
Reference Identification Qualifier
O 1
ID
2/3
Not Used
4-6
127
Reference Identification
O 1
AN
1/50

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 location of health care service for this service line is different than that carried in Loop ID-2010AA Billing Provider or Loop ID-2310C Service Facility Location. If not required by this implementation guide, do not send.
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.
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 the service location to be identified has an NPI and is not a component or subpart of the Billing Provider entity.If not required by this implementation guide, do not send.
CODE
DEFINITION
XX
Centers for Medicare and Medicaid Services National Provider Identifier
CODE SOURCE 537: Centers for Medicare and 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 the service location to be identified has an NPI and is not a component or subpart of the Billing Provider entity.If not required by this implementation guide, do not send.
INDUSTRY NAME: Laboratory or Facility Primary Identifier
Not Used
10
706
Entity Relationship Code
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 there is a second address line. 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 - 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 prior to the mandated HIPAA National Provider Identifier (NPI) implementation date when an identification number other than the NPI is necessary for the receiver to identify the provider.
OR
Required on or after the mandated NPI implementation date when the entity is not a Health Care provider (a.k.a. an atypical provider), and an identifier is necessary for the claims processor to identify the entity.
If not required by this implementation guide, do not send.
TR3 Notes:
When it is necessary to report one or more non-destination payer Secondary Identifiers, the composite data element in REF04 is used to identify the payer who assigned this identifier.
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 destination payer identified in the Payer Name loop, Loop ID-2010BB, associated with this claim. 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: Service Facility Location Secondary Identifier
Not Used
3
352
Description
O 1
AN
1/80
Situational
4
C040
Reference Identifier
O 1
To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier
SEMANTIC: REF04 contains data relating to the value cited in REF02.
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C04003 or C04004 is present, then the other is required.
  2. P0506
    If either C04005 or C04006 is present, then the other is required.
SITUATIONAL RULE: Required when the identifier reported in REF02 of this segment is for a non-destination payer.
Required
4-1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
2U
Payer Identification Number
Required
4-2
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
INDUSTRY NAME: Other Payer Primary Identifier
The payer identifier reported in this field must match the cooresponding payer identifier reported in Loop ID-2330B NM109.
Not Used
4-3
128
Reference Identification Qualifier
O 1
ID
2/3
Not Used
4-4
127
Reference Identification
O 1
AN
1/50
Not Used
4-5
128
Reference Identification Qualifier
O 1
ID
2/3
Not Used
4-6
127
Reference Identification
O 1
AN
1/50

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 rendering provider is supervised by a physician and the supervising physician is different than that listed at the claim level for this service line. If not required by this implementation guide, do not send.
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 the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Supervising Provider First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when the middle name or initial of the person is needed to identify the individual. If not required by this implementation guide, do not send.
INDUSTRY NAME: Supervising Provider Middle Name or Initial
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when the name suffix is needed to identify the individual. 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 for providers in the United States or its territories on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider is eligible to receive an NPI.ORRequired for providers not in the United States or its territories on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider has received an NPI.ORRequired for providers prior to the mandated NPI implementation date when the provider has received an NPI and the submitter has the capability to send it.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 and 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 for providers in the United States or its territories on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider is eligible to receive an NPI.ORRequired for providers not in the United States or its territories on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider has received an NPI.ORRequired for providers prior to the mandated NPI implementation date when the provider has received an NPI and the submitter has the capability to send it.If not required by this implementation guide, do not send.
INDUSTRY NAME: Supervising Provider 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

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:
20
Situational Rule:
Required prior to the mandated HIPAA National Provider Identifier (NPI) implementation date when an identification number other than the NPI is necessary for the receiver to identify the provider.
OR
Required on or after the mandated NPI Implementation Date when NM109 in this loop is not used and an identification number other than the NPI is necessary for the receiver to identify the provider.
If not required by this implementation guide, do not send.
TR3 Notes:
When it is necessary to report one or more non-destination payer Secondary Identifiers, the composite data element in REF04 is used to identify the payer who assigned this identifier.
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
1G
Provider UPIN Number
UPINs must be formatted as either X99999 or XXX999.
G2
Provider Commercial Number
This code designates a proprietary provider number for the destination payer identified in the Payer Name loop, Loop ID-2010BB, associated with this claim. 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
Situational
4
C040
Reference Identifier
O 1
To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier
SEMANTIC: REF04 contains data relating to the value cited in REF02.
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C04003 or C04004 is present, then the other is required.
  2. P0506
    If either C04005 or C04006 is present, then the other is required.
SITUATIONAL RULE: Required when the identifier reported in REF02 of this segment is for a non-destination payer.
Do not use this composite when the value reported in REF01 is either 0B or 1G.
Required
4-1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
2U
Payer Identification Number
Required
4-2
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
INDUSTRY NAME: Other Payer Primary Identifier
The payer identifier reported in this field must match the cooresponding payer identifier reported in Loop ID-2330B NM109.
Not Used
4-3
128
Reference Identification Qualifier
O 1
ID
2/3
Not Used
4-4
127
Reference Identification
O 1
AN
1/50
Not Used
4-5
128
Reference Identification Qualifier
O 1
ID
2/3
Not Used
4-6
127
Reference Identification
O 1
AN
1/50

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 the service or supply was ordered by a provider who is different than the rendering provider for this service line.
If not required by this implementation guide, do not send.
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 the person has a first name. 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 the middle name or initial of the person is needed to identify the individual. If not required by this implementation guide, do not send.
INDUSTRY NAME: 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 the name suffix is needed to identify the individual. 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 for providers on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider has received an NPI and the NPI is available to the submitter.ORRequired for providers prior to the mandated HIPAA NPI implementation date when the provider has received an NPI and the submitter has the capability to send it.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 and 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 for providers on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider has received an NPI and the NPI is available to the submitter.ORRequired for providers prior to the mandated HIPAA NPI implementation date when the provider has received an NPI and the submitter has the capability to send it.If not required by this implementation guide, do not send.
INDUSTRY NAME: Ordering Provider 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 - 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 a Durable Medical Equipment Regional Carrier Certificate of Medical Necessity (DMERC CMN) or DMERC Information Form (DIF), or Oxygen Therapy Certification is included on this service line. If not required by this implementation guide, do not send.
TR3 Example:
N3✱123 MAIN STREET~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Ordering Provider Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when there is a second address line. 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 a Durable Medical Equipment Regional Carrier Certificate of Medical Necessity (DMERC CMN) or DMERC Information Form (DIF), or Oxygen Therapy Certification is included on this service line. If not required by this implementation guide, do not send.
TR3 Example:
N4✱KANSAS CITY✱MO✱64108~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
INDUSTRY NAME: 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:
20
Situational Rule:
Required prior to the mandated HIPAA National Provider Identifier (NPI) implementation date when an identification number other than the NPI is necessary for the receiver to identify the provider.
OR
Required on or after the mandated NPI Implementation Date when NM109 in this loop is not used and an identification number other than the NPI is necessary for the receiver to identify the provider.
If not required by this implementation guide, do not send.
TR3 Notes:
When it is necessary to report one or more non-destination payer Secondary Identifiers, the composite data element in REF04 is used to identify the payer who assigned this identifier.
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
1G
Provider UPIN Number
UPINs must be formatted as either X99999 or XXX999.
G2
Provider Commercial Number
This code designates a proprietary provider number for the destination payer identified in the Payer Name loop, Loop ID-2010BB, associated with this claim. 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
Situational
4
C040
Reference Identifier
O 1
To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier
SEMANTIC: REF04 contains data relating to the value cited in REF02.
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C04003 or C04004 is present, then the other is required.
  2. P0506
    If either C04005 or C04006 is present, then the other is required.
SITUATIONAL RULE: Required when the identifier reported in REF02 of this segment is for a non-destination payer.
Do not use this composite when the value reported in REF01 is either 0B or 1G.
Required
4-1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
2U
Payer Identification Number
Required
4-2
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
INDUSTRY NAME: Other Payer Primary Identifier
The payer identifier reported in this field must match the cooresponding payer identifier reported in Loop ID-2330B NM109.
Not Used
4-3
128
Reference Identification Qualifier
O 1
ID
2/3
Not Used
4-4
127
Reference Identification
O 1
AN
1/50
Not Used
4-5
128
Reference Identification Qualifier
O 1
ID
2/3
Not Used
4-6
127
Reference Identification
O 1
AN
1/50

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 a Durable Medical Equipment Regional Carrier Certificate of Medical Necessity (DMERC CMN) or DMERC Information Form (DIF), or Oxygen Therapy Certification is included on this service line. If not required by this implementation guide, do not send.
TR3 Notes:
When the communication number represents a telephone number in the United States and other countries using the North American Dialing Plan (for voice, data, fax, etc.), the communication number must always include the area code and phone number using the format AAABBBCCCC where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number. Therefore, the following telephone number (555) 555-1234 would be represented as 5555551234. Do not submit long distance access numbers, such as "1", in the telephone number. Telephone extensions, when applicable, must be submitted in the next element immediately following the telephone number. When submitting telephone extensions, only submit the numeric extension. Do not include data that indicates an extension, such as "ext" or "x-".
TR3 Example:
PER✱IC✱JOHN SMITH✱TE✱5555551234✱EX✱123~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
366
Contact Function Code
M 1
ID
2
Code identifying the major duty or responsibility of the person or group named
CODE
DEFINITION
IC
Information Contact
Situational
2
93
Name
O 1
AN
1/60
Free-form name
SITUATIONAL RULE: Required in the first iteration of the Ordering Provider Contact Information segment. If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver.
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 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 - 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 this service line involves a referral and the referring provider differs from that reported at the claim level (loop 2310A). 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.
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 the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Referring Provider First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when the middle name or initial of the person is needed to identify the individual. If not required by this implementation guide, do not send.
INDUSTRY NAME: Referring Provider Middle Name or Initial
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when the name suffix is needed to identify the individual. 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 for providers on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider has received an NPI and the NPI is available to the submitter.ORRequired for providers prior to the mandated HIPAA NPI implementation date when the provider has received an NPI and the submitter has the capability to send it.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 and 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 for providers on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider has received an NPI and the NPI is available to the submitter.ORRequired for providers prior to the mandated HIPAA NPI implementation date when the provider has received an NPI and the submitter has the capability to send it.If not required by this implementation guide, do not send.
INDUSTRY NAME: Referring Provider 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

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:
20
Situational Rule:
Required prior to the mandated HIPAA National Provider Identifier (NPI) implementation date when an identification number other than the NPI is necessary for the receiver to identify the provider.
OR
Required on or after the mandated NPI Implementation Date when NM109 in this loop is not used and an identification number other than the NPI is necessary for the receiver to identify the provider.
If not required by this implementation guide, do not send.
TR3 Notes:
When it is necessary to report one or more non-destination payer Secondary Identifiers, the composite data element in REF04 is used to identify the payer who assigned this identifier.
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
1G
Provider UPIN Number
UPINs must be formatted as either X99999 or XXX999.
G2
Provider Commercial Number
This code designates a proprietary provider number for the destination payer identified in the Payer Name loop, Loop ID-2010BB, associated with this claim. 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
Situational
4
C040
Reference Identifier
O 1
To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier
SEMANTIC: REF04 contains data relating to the value cited in REF02.
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C04003 or C04004 is present, then the other is required.
  2. P0506
    If either C04005 or C04006 is present, then the other is required.
SITUATIONAL RULE: Required when the identifier reported in REF02 of this segment is for a non-destination payer.
Do not use this composite when the value reported in REF01 is either 0B or 1G.
Required
4-1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
2U
Payer Identification Number
Required
4-2
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
INDUSTRY NAME: Other Payer Primary Identifier
The payer identifier reported in this field must match the cooresponding payer identifier reported in Loop ID-2330B NM109.
Not Used
4-3
128
Reference Identification Qualifier
O 1
ID
2/3
Not Used
4-4
127
Reference Identification
O 1
AN
1/50
Not Used
4-5
128
Reference Identification Qualifier
O 1
ID
2/3
Not Used
4-6
127
Reference Identification
O 1
AN
1/50

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 provided in Loop ID-2310E. 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 Notes:
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".)
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 there is a second address line. 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 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 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 provided in Loop ID-2310F. 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 drop-off location name is known. 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 Notes:
If the ambulance drop-off 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: Ambulance Drop-off Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when there is a second address line. 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.
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

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 the claim has been previously adjudicated by payer identified in Loop ID-2330B and this service line has payments and/or adjustments applied to it. If not required by this implementation guide, do not send.
TR3 Notes:
To show unbundled lines: If, in the original claim, line 3 is unbundled into (for example) 2 additional lines, then the SVD for line 3 is used 3 times: once for the original adjustment to line 3 and then two more times for the additional unbundled lines.
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
This code set is not allowed for use under HIPAA at the time of this writing. The qualifier can only be used:
If a new rule names the Jurisdiction Specific Procedure and Supply Codes as an allowable code set under HIPAA,
OR
The Secretary grants an exception to use the code set as a pilot project as allowed under the law,
OR
For claims which are not covered under HIPAA.
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 Procedural Coding System
IV
Home Infusion EDI Coalition (HIEC) Product/Service Code
This code set is not allowed for use under HIPAA at the time of this writing. The qualifier can only be used:
If a new rule names the Home Infusion EDI Coalition (HIEC) Product/Service Codes as an allowable code set under HIPAA,
OR
The Secretary grants an exception to use the code set as a pilot project as allowed under the law,
OR
For claims which are not covered under HIPAA.
CODE SOURCE 513: Home Infusion EDI Coalition (HIEC) Product/Service Code List
WK
Advanced Billing Concepts (ABC) Codes
At the time of this writing, this code set has been approved by the Secretary of HHS as a pilot project allowed under HIPAA law.
The qualifier may only be used in transactions covered under HIPAA;
By parties registered in the pilot project and their trading partners,
OR
If a new rule names the Complementary, Alternative, or Holistic Procedure Codes as an allowable code set under HIPAA,
OR
For claims which are not covered under HIPAA.
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.
Situational
3-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 SVC01-7 was returned in the 835 transaction. If not required by this implementation guide, do not send.
INDUSTRY NAME: Procedure Code Description
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. 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.
  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
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 Loop 2330B made line level adjustments which caused the amount paid to differ from the amount originally charged. 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
CR
Correction and Reversals
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✱20040203~
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 the Other Payer referenced in SVD01 of this iteration of Loop ID-2430 has adjudicated this claim, provided line level information, and the provider has the ability to report line item information. 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. This segment is only used in provider submitted claims. It is not used in Payer-to-Payer Coordination of Benefits (COB).
  3. This segment is not used if the claim level (Loop ID-2320) Remaining Patient Liability AMT segment is used for this Other Payer.
TR3 Example:
AMT✱EAF✱75~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
522
Amount Qualifier Code
M 1
ID
1/3
Code 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

LQ - FORM IDENTIFICATION CODE

X12 Name:
Industry Code Identification
X12 Purpose:
To identify standard industry codes
X12 Syntax:
C0102
If LQ01 is present, then LQ02 is required.
X12 Set Notes:
NOTE: Loop 2440 provides certificate of medical necessity information for the procedure identified in SV101 in position 2/3700.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when adjudication is known to be impacted by one of the types of supporting documentation (standardized paper forms) listed in LQ01. If not required by this implementation guide, do not send.
TR3 Notes:
  1. Loop ID-2440 is designed to allow providers to attach standardized supplemental information to the claim when required to do so by the payer. The LQ segment contains information to identify the form (LQ01) and the specific form number (LQ02). In the example given below, LQ01=UT which identifies the form as a Medicare DMERC CMN form. LQ02=01.02 identifies which DMERC CMN form is being used.
  2. An example application of this Form Identification Code Loop is for Medicare DMERC claims for which the DME provider is required to obtain a Certificate of Medical Necessity (DMERC CMN) or DMERC Information Form (DIF), or Oxygen Therapy Certification from the referring physician. Another example is payer documentation requirements for Home Health services.
TR3 Example:
LQ✱UT✱01.02~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1270
Code List Qualifier Code
O 1
ID
1/3
Code identifying a specific industry code list
SEGMENT SYNTAX: C0102
CODE
DEFINITION
AS
Form Type Code
Code value AS indicates that a Home Health form from External Code Source 656 is being identified in LQ02.
CODE SOURCE 656: Form Type Codes
UT
Centers for Medicare and Medicaid Services (CMS) Durable Medical Equipment Regional Carrier (DMERC) Certificate of Medical Necessity (CMN) Forms
CODE SOURCE 582: Centers for Medicare and Medicaid Services (CMS) Durable Medical Equipment Regional Carrier (DMERC) Certificate of Medical Necessity (CMN) Forms
Required
2
1271
Industry Code
O 1
AN
1/30
Code indicating a code from a specific industry code list
SEGMENT SYNTAX: C0102
INDUSTRY NAME: Form Identifier

FRM - SUPPORTING DOCUMENTATION

X12 Name:
Supporting Documentation
X12 Purpose:
To specify information in response to a codified questionnaire document
X12 Syntax:
R02030405
At least one of FRM02, FRM03, FRM04 or FRM05 is required.
X12 Set Notes:
NOTE: FRM segment provides question numbers and responses for the questions on the medical necessity information form identified in LQ position 551.
X12 Comments:
The FRM segment can only be used in the context of an identified questionnaire or list of questions. The source of the questions can be identified by an associated segment or by transaction set notes in a particular transaction.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
99
TR3 Notes:
The LQ segment is used to identify the general (LQ01) and specific type (LQ02) for the form being reported in Loop ID-2440. The FRM segment is used to answer specific questions on the form identified in the LQ segment. FRM01 is used to indicate the question being answered. Answers can take one of 4 forms: FRM02 for Yes/No questions, FRM03 for text/uncodified answers, FRM04 for answers which use dates, and FRM05 for answers which are percents. For each FRM01 (question) use a remaining FRM element, choosing the element which has the most appropriate format. One FRM segment is used for each question/answer pair.

The example below shows how the FRM can be used to answer all the pertinent questions on DMERC form 0802 (LQ*UT*08.02~).
TR3 Example:
FRM✱1A✱✱J0234~FRM✱1B✱✱500~FRM✱1C✱✱4~FRM✱4✱Y~FRM✱5A✱✱5~FRM✱5B✱✱3~FRM✱8✱✱Methodist Hospital~FRM✱9✱✱Indianapolis~FRM✱10✱✱IN~FRM✱11✱✱✱19971101~FRM✱12✱N~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
350
Assigned Identification
M 1
AN
1/20
Alphanumeric characters assigned for differentiation within a transaction set
SEMANTIC: FRM01 is the question number on a questionnaire or codified form.
INDUSTRY NAME: Question Number/Letter
Situational
2
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: FRM02, FRM03, FRM04 and FRM05 are responses which only have meaning in reference to the question identified in FRM01.
SEGMENT SYNTAX: R02030405
SITUATIONAL RULE: Required when the question identified in FRM01 uses a Yes or No response format. If not required by this implementation guide, do not send.
INDUSTRY NAME: Question Response
CODE
DEFINITION
N
No
W
Not Applicable
Y
Yes
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
SEGMENT SYNTAX: R02030405
SITUATIONAL RULE: Required when question identified in FRM01 uses a text or uncodified response format. If not required by this implementation guide, do not send.
INDUSTRY NAME: Question Response
Situational
4
373
Date
O 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEGMENT SYNTAX: R02030405
SITUATIONAL RULE: Required when question identified in FRM01 uses a date response format. If not required by this implementation guide, do not send.
INDUSTRY NAME: Question Response
Situational
5
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%)
SEGMENT SYNTAX: R02030405
SITUATIONAL RULE: Required when question identified in FRM01 uses a percent response format. If not required by this implementation guide, do not send.
INDUSTRY NAME: Question Response

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 Health Care Claim: Professional (005010X222, 005010X222E1, 005010X222A1, 005010X222A2)

1. Purpose and Business Information

1.1 Implementation Purpose and Scope

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

This is the technical report document for the ANSI ASC X12N 837 Health Care Claims (837) transaction for professional claims and/or encounters. This document provides a definitive statement of what trading partners must be able to support in this version of the 837. This document is intended to be compliant with the data standards set out by the Health Insurance Portability and Accountability Act of 1996 (HIPAA) and its associated rules.

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 005010X222A2.

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

  • HC Health Care Claim (837)

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

1.3 Implementation Limitations

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. The sender of the original transmission reconnects at a later time and picks up the response 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 is intended to support use in batch mode. This implementation guide is not intended to support use in real-time mode. A statement that the transaction is not intended to support a specific mode does not preclude its use in that mode between willing trading partners.

1.3.2 Other Usage Limitations

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

1.4 Business Usage

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

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

The transaction defined by this implementation guide is intended to originate with the health care provider or the health care provider's designated agent. In some instances, a health care payer may originate an 837 to report a health care encounter to another payer or sponsoring organization. The 837 Transaction provides all necessary information to allow the destination payer to at least begin to adjudicate the claim. The 837 coordinates with a variety of other transactions including, but not limited to, the following: Health Care Information Status Notification (277), Health Care Claim Payment/Advice (835) and the Functional Acknowledgment (997). See Section 1.6 - Transaction Acknowledgments, and Section 1.7 - Related Transactions, for a summary description of these interactions.

1.4.1 Coordination of Benefits

A primary enhancement for this version is upgrading COB functionality to minimize manual intervention and/or the necessity for paper supporting document. Electronic COB is predicated upon using two transactions – the 837 and the 835 Health Care Claim Payment/Advice. See Section 1.4.1.1 - Coordination of Benefits Data Models -- Detail for details about the two models for using these transactions to achieve a totally electronic interchange of COB information. Section 3, EDI Transmission Examples for Different Business Uses, contains detailed examples of how these transactions are completed for several business situations. Section 1.4.1.3 - Coordination of Benefits Claims from Paper or Proprietary Remittance Advices provides guidance on creating electronic COB claims when the payer's remittance was a paper or proprietary remittance advice.

1.4.1.1 Coordination of Benefits Data Models -- Detail

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

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

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

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

Provider-to-Payer-to-Provider COB Model

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

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

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

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

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

Provider-to-Payer-to-Payer COB Model

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

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

1.4.1.1.1 Coordination of Benefits -- Claim Level

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

Loop ID-2320 contains the following:

  • claim level adjustments

  • other subscriber demographics

  • various amounts

  • other payer information

  • assignment of benefits indicator

  • patient signature indicator

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

1.4.1.1.2 Coordination of Benefits -- Service Line Level

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

Loop ID-2430 contains the following:

  • ID of the payer who adjudicated the service line

  • amount paid for the service line

  • procedure code upon which adjudication of the service line was based. This code may be different than the submitted procedure code. (This procedure code also can be used for unbundling or bundling service lines.)

  • paid units of service

  • service line level adjustments

  • adjudication date

To enable accurate matching of billed service lines with paid service lines, the payer must return the original billed procedure code(s) and/or modifiers in the SVC06 and SVC07 data element of the 835 if they are different from those used to pay the line. In addition, if a provider includes a line item control number at the 2400 level (REF01 = 6R), then payers are required to return this in any corresponding 835 regardless of whether bundling or unbundling has occurred.

1.4.1.2 Crosswalking COB Data Elements

This section provides additional guidance for automation of the COB process. The purpose of the discussion below is to clarify how multiple payer and related COB data is structured and interrelated to facilitate an automated COB process. These strategies apply to both payer and provider submitted COB claims.

For the purposes of this discussion, there are two types of payers in the 837; (1) the destination payer, the payer receiving the claim and defined in the 2010BB loop, and (2) any 'other' payers, those defined in the 2330B loop(s). The destination payer or the 'other' payers may be the primary, secondary or another position payer in terms of their sequence of paying on the claim. The payment position is not particularly important in discussing how to manage COB data elements in the 837. For this discussion, it is only important to distinguish between the destination payer and any other payer contained in the claim. In a COB situation each payer in the claim takes a turn at being the destination payer. As the destination payer changes, payer information must change position along with the payer to stay associated with that payer. The same is true of all the 'other' payers, who will each, in turn, become the destination payer as the claim is forwarded to them. It is the purpose of the example detailed below to demonstrate exactly how payer specific information stays associated with the correct payer as the destination payer rotates through the various COB payers.

Business Model:

The destination payer is defined as the payer that is described in the 2010BB loop. All of the information contained in the 2300 and 2310 loops is specific to the destination payer. Information specific to other payers is contained in the 2320, 2330, and 2430 loops. Referral, predetermination, and prior authorization numbers in the 2400 loop; and provider numbers in the 2420 loop are associated with either the destination or a non-destination payer.

837 Professional Claim

(In this crosswalk, the Subscriber is NOT the Patient, and the Original Claim is NOT a resubmission)

Primary Subscriber is JOHN DOE who has coverage with ABC INS; Secondary Subscriber is JANE DOE who has coverage with XYZ INS GROUP; Patient is daughter SALLY DOE.

COLOR KEY

D -- Destination Payer Loops and Data - Once the primary payer has adjudicated the claim, whoever submits the claim to the secondary payer needs to place the information specific to the secondary payer (columns 4 and 5) into the "destination payer" location (column 1) in the secondary claim.

N -- Other (non-destination) Payer Loops and Data - Once the primary payer has adjudicated the claim, whoever submits the claim to the secondary payer needs to place the information specific to the primary payer (columns 4 and 5) into the other (non-destination) payer location (column 1) in the secondary claim.

M -- Medicare COB - This information is entered by Medicare on the secondary (crossover) claim in Payer-to-Payer COB elements (column 4).

P -- Provider Submitted COB Data - This information is entered by the provider into the secondary claim elements (column 4) prior to forwarding to the next payer.

E -- Prior Payer 835 Data - This information is cross-walked from the 835 Remittance Advice (column 3) to elements in the secondary claim (column 4).

1

Primary Payer

837 Claim

2

Primary Payer

Claim Example

3

835 ERA

4

Crosswalk Secondary 837

Claim From Primary[1]

5

Secondary Payer

Claim Example

D

2000B | SBR

Subscriber Information

FOR JOHN DOE 2320 | SBR (except SBR02) FOR JANE DOE

D

2010BA | NM1 | REF

Subscriber Name

Secondary Identification

JOHN DOE

JD03398777

033987777

2330A | NM1 | REF

JANE DOE

JA7654321

765432111

D

Not Used[2]

Subscriber Address

Not Used[2]

Not Used

Not Used[2]

D

2010BB

Payer Information

ABC INS

2330B

XYZ INS GROUP

D

2010BB | REF (G2)

Billing Provider

Secondary ID

FOR ABC INS

12345678

2330I | REF (2U with G2)

FOR XYZ INS GROUP

(G2) XYZ3434343

D

2010BB | REF (LU)

Billing Provider

Location Code

FOR ABC INS

678

2330I | REF (2U with LU)

FOR XYZ INS GROUP

(LU) 455

D

2000C | PAT01

Patient Information

SALLY'S

RELATIONSHIP TO

JOHN – 19 CHILD

2320 | SBR02

SALLY'S

RELATIONSHIP

TO JANE –

19 CHILD

D

2010CA | NM1

Patient Name

Information

SALLY DOE

2010CA | NM1

SALLY DOE

D

2300 | CLM07

Accept Assignment

Indicator

FOR JOHN DOE

2320 | OI05

FOR JANE DOE

D

2300 | CLM08

Assignment of

Benefits Indicator

FOR JOHN DOE

2320 | OI03

FOR JANE DOE

D

2300 | CLM09

Release of

Information

FOR JOHN DOE

2320 | OI06

FOR JANE DOE

D

2300 | CLM10

Patient's Signature

Source Code

FOR JOHN DOE

2320 | OI04

FOR JANE DOE

M

N/A

Medicare (Section 4081)

Crossover Indicator

Not Used

2300 | REF01/02

Set by Medicare in

Crossover Claims

D

2300 | REF (G1)

Prior Authorization

FOR ABC INS

(G1) ABC456

2330B | REF (G1)

FOR XYZ INS GROUP

(G1) XYZ345200

D

2300 | REF (9F)

Referral Number

FOR ABC INS

(9F) ABC670000

2330B | REF (9F)

FOR XYZ INS GROUP

(9F) XYZ6798777

D

2310A | REF (G2)

Referring Provider

Secondary ID

FOR ABC INS

(G2) ABC670001

2330C | REF (G2)

FOR XYZ INS GROUP

(G2) XYZ6798666

D

2310A | REF (LU)

Referring Provider

Secondary ID

FOR ABC INS

(LU) 671

2330C | REF (LU)

FOR XYZ INS GROUP

(LU) 986

D

2310B | REF (G2)

Rendering Provider

Secondary ID

FOR ABC INS

(G2) ABC670002

2330D | REF (G2)

FOR XYZ INS GROUP

(G2) XYZ6798444

D

2310B | REF (LU)

Rendering Provider

Secondary ID

FOR ABC INS

(LU) 672

2330D | REF (LU)

FOR XYZ INS GROUP

(LU) 984

D

2310C | REF (G2)

Service Facility

Location Secondary ID

FOR ABC INS

(G2) ABC670004

2330E | REF (G2)

FOR XYZ INS GROUP

(G2) XYZ6798222

D

2310C | REF (LU)

Service Facility

Location Secondary ID

FOR ABC INS

(LU) 674

2330E | REF (LU)

FOR XYZ INS GROUP

(LU) 982

D

2310D | REF (G2)

Supervising Provider ID

FOR ABC INS

(G2) ABC670005

2330F | REF (G2)

FOR XYZ INS GROUP

(G2) XYZ6798111

D

2310D | REF (LU)

Supervising Provider ID

FOR ABC INS

(LU) 675

2330F | REF (LU)

FOR XYZ INS GROUP

(LU) 981

N

2320 | SBR

(except SBR02)

Subscriber Information

FOR JANE DOE

2000B | SBR (except SBR02)

FOR JOHN DOE

N

2320 | SBR02

Subscriber Relationship

to Patient

SALLY'S

RELATIONSHIP

TO JANE – 17

STEPCHILD

2000C | PAT01

SALLY'S

RELATIONSHIP

TO JOHN – 19

CHILD

E

Claim Adjustment

Group Code

Not Used

2100 | CAS

2320 | CAS

FROM ABC INS

E

Payer Paid Amount

Not Used

2100 | CLP04

2320 | AMT01/02 (D)

FROM ABC INS

E

Total Non-Covered

Amount

Not Used

2100 | AMT (A8)

2320 | AMT01/02 (A8)

FROM ABC INS

P

Remaining Patient

Liability

Not Used

2320 | AMT01 (EAF)

Calculated by

Provider

N

2320 | DMG

Subscriber Demographic

Information

FOR JANE DOE

Not Used

Not Used

N

2320 | OI05

Accept Assignment

Indicator

FOR JANE DOE

2300 | CLM07

FOR JOHN DOE

N

2320 | OI03

Assignment of

Benefit Indicator

FOR JANE DOE

2300 | CLM08

FOR JOHN DOE

N

2320 | OI06

Release of Information

FOR JANE DOE

2300 | CLM09

FOR JOHN DOE

N

2320 | OI04

Patient's Signature

Source Code

FOR JANE DOE

2300 | CLM10

FOR JOHN DOE

E

Medicare Outpatient

Adjudication Information

Not Used

2100 | MOA

2320 | MOA

FROM ABC INS

N

2330A | NM1 | REF

Subscriber Name

Secondary ID

JANE DOE

JA7654321

765432111

2010BA | NM1 | REF

JOHN DOE

JD03398777

033987777

N

2330A | N3/N4

Subscriber Address

FOR JANE DOE

2010BA | N3/N4

FOR JOHN DOE

N

2330B

Payer Information

FOR XYZ INS GROUP

2010BB

FOR JOHN DOE

N

2330B | PER

Payer Contact

Information

FOR XYZ INS GROUP

Not Used

FOR ABC INS

E

Claim Adjudication

Date

Not Used

Table 1 | BPR16

2330B | DTP (573)

FROM ABC INS

N

Payer Claim Control

Secondary Number

Not Used

2100 | CLP07[3]

2330B | REF (F8)

FROM ABC INS

XYZCLM0005

N

2330B | REF (G1)

Prior Authorization

FOR XYZ INS GROUP

XYZ345200

2300 | REF (G1)

FOR ABC INS

ABC456

N

2330B | REF (9F)

Referral Number

FOR XYZ INS GROUP

XYZ6798777

2300 | REF (9F)

FOR ABC INS

ABC670000

N

2330C | REF (G2)

Referring Provider

Secondary ID

FOR XYZ INS GROUP

(G2) XYZ6798666

2310A | REF (G2)

FOR ABC INS

(G2) ABC670001

N

2330C | REF (LU)

Referring Provider

Secondary ID

FOR XYZ INS GROUP

(LU) 986

2310A | REF (LU)

FOR ABC INS

(LU) 671

N

2330D | REF (G2)

Rendering Provider

Secondary ID

FOR XYZ INS GROUP

(G2) XYZ6798444

2310B | REF (G2)

FOR ABC INS

(G2) ABC670002

N

2330D | REF (LU)

Rendering Provider

Secondary ID

FOR XYZ INS GROUP

(LU) 984

2310B | REF (LU)

FOR ABC INS

(LU) 672

N

2330E | REF (G2)

Service Facility Location

Secondary ID

FOR XYZ INS GROUP

(G2) XYZ6798222

2310C | REF (G2)

FOR ABC INS

(G2) ABC670004

N

2330E | REF (LU)

Service Facility Location

Secondary ID

FOR XYZ INS GROUP

(LU) 982

2310C | REF (LU)

FOR ABC INS

(LU) 674

N

2330F | REF (G2)

Supervising Provider ID

FOR XYZ INS GROUP

(G2) XYZ6798111

2310D | REF (G2)

FOR ABC INS

(G2) ABC670005

N

2330F | REF (LU)

Supervising Provider ID

FOR XYZ INS GROUP

(LU) 981

2310D | REF (LU)

FOR ABC INS

(LU) 675

N

2330G | REF (G2)

Billing Provider ID

FOR XYZ INS GROUP

(G2) XYZ3434343

2010BB | REF (G2)

FOR ABC INS

(G2) 12345678

N

2330G | REF (LU)

Billing Provider ID

FOR XYZ INS GROUP

(LU) 455

2010BB | REF (LU)

FOR ABC INS

(LU) 678

D

2400 | REF (G1)

Prior Authorization

Number

FOR ABC INS

(G1) ABC222222

2400 | REF (G1/2U)

FOR XYZ INS GROUP

(G1) XYZ888888

N

2400 | REF (G1/2U)

Prior Authorization

Number

FOR XYZ INS GROUP

(G1) XYZ888888

(2U) 54698

2400 | REF (G1)

FOR ABC INS

(G1) ABC222222

(2U) 12345

D

2400 | REF (9F)

Referral Number

FOR ABC INS

(9F) ABC111111

2400 | REF (9F/2U)

FOR XYZ INS GROUP

(9F) XYZ777777

N

2400 | REF (9F/2U)

Referral Number

FOR XYZ INS GROUP

(9F) XYZ777777

(2U) 54698

2400 | REF (9F)

FOR ABC INS

(9F) ABC111111

(2U) 12345

D

2420A | REF (G2)[4]

Rendering Provider

Secondary ID

FOR ABC INS

(G2) ABC888888

2420A | REF (G2/2U)[4]

FOR XYZ INS GROUP

(G2) XYZ111111

D

2420A | REF (LU)[4]

Rendering Provider

Secondary ID

FOR ABC INS

(LU) C333

2420A | REF (LU/2U)[4]

FOR XYZ INS GROUP

(LU) Z666

N

2420A | REF (G2/2U)[4]

Rendering Provider

Secondary ID

FOR XYZ INS GROUP

(G2) XYZ666666

(2U)54698

2420A | REF (G2)[4]

FOR ABC INS

(G2) ABC333333

(2U) 12345

N

2420A | REF (LU/2U)[4]

Rendering Provider

Secondary ID

FOR XYZ INS GROUP

(LU) Z666

(2U) 54698

2420A | REF (LU)[4]

FOR ABC INS

(LU) C333

(2U) 12345

D

2420B | REF (G2)[4]

Purchased Service

Secondary ID

FOR ABC INS

(G2) ABC444444

2420B | REF (G2/2U)[4]

FOR XYZ INS GROUP

(G2) XYZ555555

D

2420B | REF (LU)[4]

Purchased Service

Secondary ID

FOR ABC INS

(LU) C444

2420B | REF (LU/2U)[4]

FOR XYZ INS GROUP

(LU) Z555

N

2420B | REF (G2/2U)[4]

Purchased Service

Secondary ID

FOR XYZ INS GROUP

(G2) XYZ555555

(2U) 54698

2420B | REF (G2)[4]

FOR ABC INS

(G2) ABC444444

(2U) 12345

N

2420B | REF (LU/2U)[4]

Purchased Service

Secondary ID

FOR XYZ INS GROUP

(LU) Z555

(2U) 54698

2420B | REF (LU)[4]

FOR ABC INS

(LU) C444

(2U) 12345

D

2420C | REF (G2)[4]

Service Facility

Location Secondary ID

FOR ABC INS

(G2) ABC555555

2420C | REF (G2/2U)[4]

FOR XYZ INS GROUP

(G2) XYZ444444

D

2420C | REF (LU)[4]

Service Facility

Location Secondary ID

FOR ABC INS

(LU) C555

2420C | REF (LU/2U)[4]

FOR XYZ INS GROUP

(LU) Z444

N

2420C | REF (G2/2U)[4]

Service Facility

Location Secondary ID

FOR XYZ INS GROUP

(G2) XYZ444444

(2U) 54698

2420C | REF (G2)[4]

FOR ABC INS

(G2) ABC555555

(2U) 12345

N

2420C | REF (LU/2U)[4]

Service Facility

Location Secondary ID

FOR XYZ INS GROUP

(LU) Z444

(2U) 54698

2420C | REF (LU)[4]

FOR ABC INS

(LU) C555

(2U) 12345

D

2420D | REF (G2)[4]

Supervising Provider

Secondary ID

FOR ABC INS

(G2) ABC666666

2420D | REF (G2/2U)[4]

FOR XYZ INS GROUP

(G2) XYZ333333

D

2420D | REF (LU)[4]

Supervising Provider

Secondary ID

FOR ABC INS

(LU) C666

2420D | REF (LU/2U)[4]

FOR XYZ INS GROUP

(LU) Z333

N

2420D | REF (G2/2U)[4]

Supervising Provider

Secondary ID

FOR XYZ INS GROUP

(G2) XYZ333333

(2U) 54698

2420D | REF (G2)[4]

FOR ABC INS

(G2) ABC666666

(2U) 12345

N

2420D | REF (LU/2U)[4]

Supervising Provider

Secondary ID

FOR XYZ INS GROUP

(LU) Z333

(2U) 54698

2420D | REF (LU)[4]

FOR ABC INS

(LU) C666

(2U) 12345

D

2420E | REF (G2)[4]

Ordering Provider

Secondary ID

FOR ABC INS

(G2) ABC777777

2420E | REF (G2/2U)[4]

FOR XYZ INS GROUP

(G2) XYZ222222

D

2420E | REF (LU)[4]

Ordering Provider

Secondary ID

FOR ABC INS

(LU) C777

2420E | REF (LU/2U)[4]

FOR XYZ INS GROUP

(LU) Z222

N

2420E | REF (G2/2U)[4]

Ordering Provider

Secondary ID

FOR XYZ INS GROUP

(G2) XYZ222222

(2U) 54698

2420E | REF (G2)[4]

FOR ABC INS

(G2) ABC777777

(2U) 12345

N

2420E | REF (LU/2U)[4]

Ordering Provider

Secondary ID

FOR XYZ INS GROUP

(LU) Z222

(2U) 54698

2420E | REF (LU)[4]

FOR ABC INS

(LU) C777

(2U) 12345

D

2420F | REF (G2)[4]

Referring Provider

Secondary ID

FOR ABC INS

(G2) ABC888888

2420F | REF (G2/2U)[4]

FOR XYZ INS GROUP

(G2) XYZ111111

D

2420F | REF (LU)[4]

Referring Provider

Secondary ID

FOR ABC INS

(LU) C888

2420F | REF (LU/2U)[4]

FOR XYZ INS GROUP

(LU) Z111

N

2420F | REF (G2/2U)[4]

Referring Provider

Secondary ID

FOR XYZ INS GROUP

(G2) XYZ111111

(2U) 54698

2420F | REF (G2)[4]

FOR ABC INS

(G2) ABC888888

(2U) 12345

N

2420F | REF (LU/2U)[4]

Referring Provider

Secondary ID

FOR XYZ INS GROUP

(LU) Z111

(2U) 54698

2420F | REF (LU)[4]

FOR ABC INS

(LU) C888

(2U) 12345

E

Service Line

Paid Amount

Not Used

2200 | SVD

2430 | SVD

FROM ABC INS

E

Claim Adjustment

Information

Not Used

2200 | CAS

2430 | CAS

FROM ABC INS

E

Line Adjudication

Date

Not Used

Table 1 | BPR16

2430 | DTP (573)

FROM ABC INS

P

Remaining Patient

Liability Amount

Not Used

2430 | AMT01 (EAF)

Calculated by

Provider

[1] 1 The secondary claim information shows where the original claim information would be mapped to when creating the secondary claim. This information must be in the correct order of the implementation guide and not in the order shown above.

[2] 2 The Subscriber Address in the 2010BB Loop is only used when the Patient is the Subscriber.

[3] 32300REF Original Payer Claim Number

The Original Payer Claim Number is used to submit the Claim Number returned on the 835 whenever a claim is resubmitted to the same payer. When submitting a secondary claim that was resubmitted to the first payer, this number is carried in the 2330B REF. It is important to keep a Payer Original Claim Number in the loop associated with that payer. In the example below, the number returned by the first payer is used in the destination claim loop when resubmitting to that payer. Then when the secondary claim is created, the first payer's Original Claim Number is moved down into the Loop ID-2330B REF for the first payer.

Original Claim Remittance Advice Resubmitted Claim Secondary Claim
2300 REF (F8) Not Used 2100 | CLP07 2300 | REF (F8) Not Used
2330B REF (F8) Not Used Not Used 2300 REF (F8)

[4] 4 2420A-F Provider Secondary Identifiers

The G2 and LU Qualifiers and the Secondary Identifiers in these Loops are for both the Destination Payer and the Non-Destination Payer. The 2U Qualifier is specific to the Non-Destination Payer. When creating the secondary claim, the numbers are swapped as follows:

Original Claim Secondary Claim
2010BB NM108/09 Payer ID 12345 54698
2330B NM108-09 Payer ID 54698 12345
2420A REF01 Rendering Provider ID FOR Payer G2 G2
2420A REF02 ABC333333 XYZ666666
2420A REF01 Rendering Provider Location Code LU LU
2420A REF02 C333 Z666
2420A REF01 Rendering Provider Secondary ID G2 G2
2420A REF02 (For Non-destination Payer identified below) XYZ666666 ABC333333
2420A REF03 Not Used
2420A REF04-1 Other Payer ID (linked to 2330B Payer) 2U 2U
2420A REF04-2 54698 12345
2420A REF01 Rendering Provider Location Code LU LU
2420A REF02 (For Non-destination Payer identified below) Z666 C333
2420A REF03 Not Used
2420A REF04-1 Other Payer ID (linked to 2330B Payer) 2U 2U
2420A REF04-2 54698 12345

Example

In the following example, the first column is a claim as submitted to the primary payer. The second column is the corresponding claim with the same business data as it would be submitted to the secondary payer. For the COB claim to the secondary payer, this example shows information related to the primary payer being placed in the other (non-destination) payer locations, and it also shows information related to the secondary payer being placed in the destination payer locations. Segments in red, italicized text are related to the secondary payer.

HEADER

ST*837*0002*005010X222A2~

BHT*0019*00*0123*20050730*1023*CH~

HEADER

ST*837*0002*005010X222A2~

BHT*0019*00*0123*20050730*1023*CH~

1000A SUBMITTER

NM1*41*2*GET WELL CLINIC*****46*567890~

PER*IC*MARY*TE*6155552222~

1000A SUBMITTER

NM1*41*2*GET WELL CLINIC*****46*567890~

PER*IC*MARY*TE*6155552222~

1000B RECEIVER

NM1*40*2*MY CLEARINGHOUSE*****46*988888888~

1000B RECEIVER

NM1*40*2*MY CLEARINGHOUSE*****46*988888888~

2000A BILLING/PAY-TO PROVIDER HL LOOP

HL*1**20*1~

2000A BILLING/PAY-TO PROVIDER HL LOOP

HL*1**20*1~

2010AA BILLING PROVIDER

NM1*85*2*GET WELL CLINIC*****XX*5876543216~

N3*1234 MAIN ST~

N4*ANYWHERE*TN*37214~

REF*EI*111222333~

2010AA BILLING PROVIDER

NM1*85*2*GET WELL CLINIC*****XX*5876543216~

N3*1234 MAIN ST~

N4*ANYWHERE*TN*37214~

REF*EI*111222333~

2000B SUBSCRIBER HL LOOP

HL*2*1*22*1~

SBR*P********BL~

2000B SUBSCRIBER HL LOOP

HL*2*1*22*1~

SBR*S********CI~

2010BA SUBSCRIBER

NM1*IL*1*DOE*JOHN****MI*JD03398777~

REF*SY*033987777~

2010BA SUBSCRIBER

NM1*IL*1*DOE*JANE****MI*JA7654321~

REF*SY*765432111~

2010BB PAYER

NM1*PR*2*ABC INS*****PI*12345~

REF*G2*12345678~

REF*LU*678~

2010BB PAYER

NM1*PR*2*XYZ INS GROUP*****PI*54698~

REF*G2*XYZ3434343~

REF*LU*455~

2000C PATIENT HL LOOP

HL*3*2*23*0~

PAT*19~

2000C PATIENT HL LOOP

HL*3*2*23*0~

PAT*19~

2010CA PATIENT

NM1*QC*1*DOE*SALLY~

N3*234 SOUTH ST~

N4*ANYWHERE*TN*37214~

DMG*D8*19930501*F~

2010CA PATIENT

NM1*QC*1*DOE*SALLY~

N3*234 SOUTH ST~

N4*ANYWHERE*TN*37214~

DMG*D8*19930501*F~

2300 CLAIM

CLM*26407789*115***11:B:1*Y*A*Y*Y*B~

REF*G1*ABC456~

REF*9F*ABC670000~

HI*BK:4779*BF:2724*BF:2780*BF:53081~

2300 CLAIM

CLM*26407789*115***11:B:1*Y*A*N*Y*B~

REF*G1*XYZ345200~

REF*9F*XYZ6798777~

HI*BK:4779*BF:2724*BF:2780*BF:53081~

2310A REFERRING PROVIDER

NM1*DN*1*KILDARE*RICHARD****XX*9999977777~

REF*G2*ABC670001~

REF*LU*671~

2310A REFERRING PROVIDER

NM1*DN*1*KILDARE*RICHARD****XX*9999977777~

REF*G2*XYZ6798666~

REF*LU*986~

2310B RENDERING PROVIDER

NM1*82*1*CASEY*BEN****XX*9999966666~

REF*G2*ABC670002~

REF*LU*672~

2310B RENDERING PROVIDER

NM1*82*1*CASEY*BEN****XX*9999966666~

REF*G2*XYZ6798444~

REF*LU*984~

2310C SERVICE FACILITY LOCATION

NM1*77*2*ANYWHERE CLINIC*****XX*9999955555~

N3*2345 STATE ST~

N4*NASHVILLE*TN*37212~

REF*G2*ABC670004~

REF*LU*674~

2310C SERVICE FACILITY LOCATION

NM1*77*2*ANYWHERE CLINIC*****XX*9999955555~

N3*2345 STATE ST~

N4*NASHVILLE*TN*37212~

REF*G2*XYZ6798222~

REF*LU*982~

2320 OTHER SUBSCRIBER INFORMATION

SBR*S*19*******CI~

DMG*D8*19500501*F~

OI***N*B**Y~

2320 OTHER SUBSCRIBER INFORMATION

SBR*P*19*******BL~

AMT*D*65~

DMG*D8*19481013*M~

OI***Y*B**Y~

2330A OTHER SUBSCRIBER NAME

NM1*IL*1*DOE*JANE****MI*JA7654321~

N3*234 SOUTH ST~

N4*ANYWHERE*TN*37214~

REF*SY*765432111~

2330A OTHER SUBSCRIBER NAME

NM1*IL*1*DOE*JOHN****MI*JD03398777~

N3*234 SOUTH ST~

N4*ANYWHERE*TN*37214~

REF*SY*033987777~

2330B OTHER PAYER

NM1*PR*2*XYZ INS GROUP*****PI*54698~

REF*G1*XYZ345200~

REF*9F*XYZ6798777~

2330B OTHER PAYER

NM1*PR*2*ABC INS*****PI*12345~

REF*F8*ABCCLM0005~

REF*G1*ABC456~

REF*9F*ABC670000~

2330C OTHER PAYER REFERRING PROVIDER

NM1*DN*1~

REF*G2*XYZ6798666~

REF*LU*986~

2330C OTHER PAYER REFERRING PROVIDER

NM1*DN*1~

REF*G2*ABC670001~

REF*LU*671~

2330D OTHER PAYER RENDERING PROVIDER

NM1*82*1~

REF*G2*XYZ6798444~

REF*LU*984~

2330D OTHER PAYER RENDERING PROVIDER

NM1*82*1~

REF*G2*ABC670002~

REF*LU*672~

2330E OTHER PAYER SERVICE FACILITY LOCATION

NM1*77*2~

REF*G2*XYZ6798222~

REF*LU*982~

2330E OTHER PAYER SERVICE FACILITY LOCATION

NM1*77*2~

REF*G2*ABC670004~

REF*LU*674~

2400 SERVICE LINE

LX*1~

SV1*HC:99213*100*UN*1***1:2~

DTP*472*D8*20050705~

REF*G1*ABC222222~

REF*G1*XYZ888888**2U:54698~

REF*9F*ABC111111~

REF*9F*XYZ777777**2U:54698~

SERVICE LINE

LX*1~

SV1*HC:99213*100*UN*1***1:2~

DTP*472*D8*20050705~

REF*G1*XYZ888888~

REF*G1*ABC222222**2U:12345~

REF*9F*XYZ777777~

REF*9F*ABC111111**2U:12345~

2420A RENDERING PROVIDER

NM1*82*1*WELBY*MARCUS****XX*1545454541~

REF*G2*ABC333333~

REF*LU*C333~

REF*G2*XYZ666666**2U:54698~

REF*LU*Z666**2U:54698~

2420A RENDERING PROVIDER

NM1*82*1*WELBY*MARCUS****XX*1545454541~

REF*G2*XYZ666666~

LU*Z666~

REF*G2*ABC333333**2U:12345~

REF*LU*C333**2U:12345~

2420F REFERRING PROVIDER

NM1*DN*1*BROWN*JOE****XX*1323232321~

REF*G2*ABC888888~

REF*LU*C888~

REF*G2*XYZ111111**2U:54698~

REF*LU*Z111**2U:54698~

2420F REFERRING PROVIDER

NM1*DN*1*BROWN*JOE****XX*1323232321~

REF*G2*XYZ111111~

REF*LU*Z111~

REF*G2*ABC88888888**2U:12345~

REF*LU*C888**2U:12345~

2430 LINE ADJUDICATION INFORMATION

SVD*12345*50*HC:99213**1~

CAS*PR*1*50~

DTP*573*D8*20050726~

AMT*EAF*50~

2400 SERVICE LINE

LX*2~

SV1*HC:90782*15*UN*1***3:4~

DTP*472*D8*20050705~

2400 SERVICE LINE

LX*2~

SV1*HC:90782*15*UN*1***3:4~

DTP*472*D8*20050705~

2430 LINE ADJUDICATION INFORMATION

SVD*12345*15*HC:90782**1~

CAS*PR*92*0~

DTP*573*D8*20050726~

TRANSACTION SET TRAILER

SE*78*0002~

TRANSACTION SET TRAILER

SE*88*0002~

1.4.1.3 Coordination of Benefits Claims from Paper or Proprietary Remittance Advices

Claim submitters may at times need or choose to create electronic secondary/tertiary coordination of benefit (COB) claims to subsequent payers due to regulatory or business relationships when the prior payer's remittance was a paper or proprietary remittance advice. This situation may occur when the prior payer(s) is not a regular trading partner of the claim submitter or the prior payer(s) produces electronic remittances but has not converted to the standard transaction.

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

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

Generally, a subsequent COB payer(s) determines payment on a combination of "Group Code" and "Claim Adjustment Reason Code" provided in the CAS segment at either the claim or service line. The primary considerations of Group Code of subsequent COB payers are:

Description837 Standard Value
Patient ResponsibilityPR
Contractual ObligationCO
Payer InitiatedPI
Other AdjustmentsOA

The Claim Adjustment Reason Code is equally important in subsequent payers' determination of payment responsibility. In most instances paper or proprietary monetary adjustments may easily be cross-walked to the standard Claim Adjustment Reason Codes as follows:

Description837 Standard Value
Patient Responsibility
Deductible Amount1
Coinsurance Amount2
Co-payment Amount3
Blood Deductible66
Psychiatric Reduction122
Contractual Obligations
Charges exceed our fee schedule or maximum allowable amount42
Charges exceed your contracted / legislated fee arrangement45
Non-covered charges96

Payment adjustments by the prior payer(s) that are not readily defined by the above cross-walk values may be reported using default Claim Adjustment Reason Code 192 (Non-standard adjustment code from paper remittance advice) or with other codes the claim submitter determines to be appropriate. Submitters must not use default code 192 when a more specific code is available.

1.4.1.4 Coordination of Benefits - Service Line Procedure Code Bundling and Unbundling

This explanation of bundling and unbundling is applicable to secondary claims that must contain the results of the primary payer's processing. It is not applicable to initial claims sent to the primary payer.

Procedure code bundling or unbundling occurs when a payer's business policy requires that the services reported for payment in a claim be either combined or split apart and represented by a different group of procedure codes. Bundling occurs when two or more reported procedure codes are paid under only one procedure code. Unbundling occurs when one submitted procedure code is paid and reported back as two or more procedure codes.

See the latest version of the 835 Remittance Advice transaction implementation guide for an explanation on how bundling and unbundling are handled in that transaction.

Bundling:

In a COB situation, it may be necessary to show payment on bundled lines. When showing bundled service lines, the health care claim must report all of the originally submitted service lines. The first bundled procedure includes the new bundled procedure code in the SVD (Service Line Adjudication) segment (SVD03). The other procedure or procedures that are bundled into the same line are reported as originally submitted with the following:

  • An SVD segment with zero payment (SVD02),

  • A pointer to the new bundled procedure code (SVD06, data element 554 (Assigned Number) is the bundled service line number that refers to the LX assigned number of the service line into which this service line was bundled),

  • A CAS segment with a claim adjustment reason code of 97 (payment is included in the allowance for the basic service), and

  • An adjustment amount equal to the submitted charge.

  • The Adjustment Group in the CAS01 will be either CO (Contractual Obligation) or PI (Payer Initiated), depending upon the provider/payer relationship.

Bundling with COB Example

The following example shows how to report bundled lines on a subsequent COB claim. Dr. Smith submits procedure code A and B for $100.00 each to his PPO as primary coverage. Each procedure was performed on the same date of service. The original 837 submitted by Dr. Smith contains this information. Only segments specific to bundling are included in the example.

Original 837

LX*1~
1   
SV1*HC:A*100*UN*1***1~
HC  
A   
100 
UN  
1   
1   
LX*2~
2   
SV1*HC:B*100*UN*1***1~
HC  
B   
100 
UN  
1   
1   

The PPO's adjudication system screens the submitted procedures and notes that procedure C covers the services rendered by Dr. Smith on that single date of service. The PPO's maximum allowed amount for procedure C is $120.00. The patient's co-insurance amount for procedure C is $20.00. The patient has not met the $50.00 deductible. The PPO's total payment on this claim was $50.00. The following example includes only segments specific to bundling. The key number to automate tracking of bundled lines is the service line number assigned to each service line in LX01.

COB 837

Claim Level

CAS*PR*1*50~
PR  
1   
50  
AMT*D*50~
D   
50  

Service Line Level

LX*1~
1   
SV1*HC:A*100*UN*1***1~
HC  
A   
100 
UN  
1   
1   
SVD*PAYER ID*100*HC:C**1~
Payer ID
    
100 
HC  
C   
1   
CAS*PR*2*20~
PR  
2   
20  
LX*2~
2   
SV1*HC:B*100*UN*1***1~
HC  
B   
100 
UN  
1   
1   
SVD*PAYER ID*0*HC:C**1*1~
Payer ID
    
0   
HC  
C   
1   
1   
CAS*CO*97*100~
CO  
97  
100 

Bundling with COB -– More Than 2 Payers Example

Bundling with more than two payers in a COB situation where there is both bundling and line level adjustments. The COB related loops would appear as follows:

Claim Level 2320 and 2330 Loops

2320 Loop (for payer A)

SBR* identifies the other subscriber for payer A identified in 2330B

2330A Loop

NM1* identifies other subscriber for payer A

2330B Loop

NM1* identifies payer A

2320 Loop (for payer B)

SBR* identifies the other subscriber for payer B identified in 2330B loop

2330A Loop

NM1* identifies other subscriber for payer B

2330B Loop

NM1* identifies payer B

2320 Loop (for payer C)

SBR* identifies the other subscriber for payer C identified in 2330B loop

2330A Loop

NM1* identifies other subscriber for payer C

2330B Loop

NM1* identifies payer C

Repeat as necessary up to a maximum of ten times. Any one claim can carry up to a total of 11 payers (ten carried in Loop ID-2320, and one carried in Loop ID-2010BB). Once all the claim level payers have been identified, use the 2400 loop once for each original billed service line. Use 2430 loops to show line level adjustment by each payer.

Service Line

2400 Loop

LX*1~

SV1* original data from provider for line 1

2430 Loop (for payer A)

SVD*A* their data for this line (the procedure code A paid on)

CAS* payer A's data for this line (repeat CAS as necessary)

DTP* payer A's adjudication date for this line

2430 Loop (for payer B)

SVD*B* their data for this line (the procedure code B paid on)

CAS* payer B's data for this line (repeat CAS as necessary)

DTP* payer B's adjudication date for this line

2430 Loop (for payer C, only used if 837 is being sent to payer D)

SVD*C* their data for this line (the procedure code C paid on)

CAS* payer C's data for this line (repeat CAS as necessary)

DTP* payer C's adjudication date for this line

2400 Loop

LX*2~

SV1* original data from provider for line 2

2430 Loop (for payer A)

SVD*A* their data for this line (the procedure code A paid on)

CAS* payer A's data for this line (repeat CAS as necessary)

DTP* payer A's adjudication date for this line

2430 Loop (for payer B)

SVD*B* their data for this line (the procedure code B paid on)

CAS* payer B's data for this line (repeat CAS as necessary)

DTP* payer B's adjudication date for this line

2430 Loop (for payer C, only used if 837 is being sent to payer D)

SVD*C* their data for this line (the procedure code C paid on)

CAS* payer C's data for this line (repeat CAS as necessary)

DTP* payer C's adjudication date for this line

etc.

Unbundling with COB

When unbundling, the original service line detail will be followed by one or more occurrences of the Line Adjudication Information (Loop ID-2430) loop. This loop is repeated once for each unbundled procedure code.

Unbundling Example

The same provider submits a claim for one service line. The billed service procedure code is A, with a submitted charge of $200.00. The payer unbundled this into two services -- B and C -- each with an allowed amount of $60.00. There is no deductible or co-insurance amount. Only segments specific to unbundling are included in the following example.

LX*1~
1   
SV1*HC:A*200*UN*1***1~
HC  
A   
200 
UN  
1   
1   
SVD*PAYER ID*60*HC:B**1~
Payer ID
    
60  
HC  
B   
1   
CAS*CO*45*35~
CO  
45  
35  
SVD*PAYER ID*60*HC:C**1~
Payer ID
    
60  
HC  
C   
1   
CAS*CO*45*45~
CO  
45  
45  
(Loop 2400)= Service line 1= HCPCS qualifier= HCPCS code= Submitted charge= Units code= Units billed= Diagnosis code pointer (Loop 2400)= Service line 2= HCPCS qualifier= HCPCS code= Submitted charge= Units code= Units billed= Diagnosis code pointer (Loop ID-2320)= Patient's Responsibility= Adjustment reason - Deductible amount= Amount of adjustment= Payer amount paid qualifier= Amount paid on this claim by this payer (Loop ID-2400)= Service line 1 (Loop ID-2400)= HCPCS qualifier= HCPCS code= Submitted charge= Units code= Units billed= Diagnosis code pointer (Loop ID-2430)= ID of the payer who adjudicated this service line= Payer amount approved for payment for the line= HCPCS qualifier= HCPCS code for bundled procedure= Service Units= Patient Responsibility= Adjustment reason -- Co-insurance amount= Amount of adjustment (Loop 2400)= Service line 2= HCPCS qualifier= HCPCS code= Submitted charge= Units code= Units billed= Diagnosis code pointer (Loop ID-2430)= ID of the payer who adjudicated this service line= Payer amount paid= HCPCS qualifier= HCPCS code for bundled procedure= Service Units= Service line number into which this service line was bundled= Contractual obligations qualifier= Adjustment reason - Payment is included in the allowance for the basic service/procedure= Amount of adjustment (Loop-2400)= Service line 1= HCPCS qualifier= HCPCS code= Submitted charge= Units code= Units billed= Diagnosis code pointer (Loop ID-2430)= ID of the payer who adjudicated this service line= Payer amount paid= HCPCS qualifier= Unbundled HCPCS code= Service Units= Contractual obligations qualifier= Adjustment reason -- Charges exceed your contracted/legislated fee arrangement= Amount of adjustment= ID of the payer who adjudicated this service line= Payer amount paid= HCPCS qualifier= Unbundled HCPCS code= Service Units= Contractual obligations qualifier= Adjustment reason -- Charges exceed your contracted/legislated fee arrangement= Amount of adjustment

1.4.1.5 Coordination of Benefits - Medicaid Subrogation

Federal law requires Medicaid agencies to pursue recovery of medical expenditures made on behalf of Medicaid recipients when third party liability is determined to exist. Since Medicaid recipients are required to assign any rights of third party liability to the Medicaid agency, this Implementation Guide provides the ability for willing trading partners to allow direct billing by a Medicaid agency to other health plans. These pay-to-plan claims are identified by the inclusion of Loop ID-2010AC Pay-to Plan Name Loop. Medicaid subrogation claims include the Medicaid agency's own payer claim control number in Loop ID-2300 data element CLM01 rather than the provider's patient control number. The Medicaid paid amount, indicated in Loop ID-2320 data element AMT01, represents the maximum amount of liability the Medicaid agency is requesting to recover by submitting the claim.

The Medicaid agency is identified in Loop ID-2330B (Other Payer Name). Loop ID-2320 and Loop ID-2430 include all required segments to indicate the Medicaid agency's adjudication of the original claim submitted to that agency. Receiving payers are to direct information requests about the claim to the Medicaid agency rather than to the original service provider.

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

1.4.2 Property and Casualty

To ensure timely processing, specific information needs to be included when submitting bills to Property and Casualty payers (for example, Automobile, Homeowner's, or Workers' Compensation insurers and related entities). Section 3.2 of this Implementation Guide explains these requirements and presents a number of examples.

1.4.3 Data Overview

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

1.4.3.1 Loop Labeling, Sequence, and Use

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

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

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

1.4.3.2 Data Use by Business Use

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

1.4.3.2.1 Table 1 -- Transaction Control Information

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

Figure 1.3 - Header Level

Header Level
1.4.3.2.1.1 Transaction Set Header (ST) Segment

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

Because the 837 is multi-functional, it is important for the receiver to know which business purpose is served. ST03 contains a reference to the specific implementation guide used to create this 837 transaction. This data element differentiates among the Health Care Claim: Professional (005010X222A2), the Health Care Claim: Institutional (005010X223A3), the Health Care Claim: Dental (005010X224A3), and the Health Care Service: Data Reporting (005010X225A2).

1.4.3.2.1.2 Beginning of Hierarchical Transaction (BHT) Segment

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

  • BHT01 - The Hierarchical Structure Code designates the type of business data within each hierarchical level. The 0019 value used in the claim BHT01 specifies the order of subsequent hierarchical levels to be:

    • Information source (Billing Provider)

    • Subscriber (can be the patient when the patient is the subscriber or is considered to be the subscriber)

    • Dependent (Patient, when the patient is not considered to be the subscriber)

  • BHT02 - The transaction purpose code indicates "original" by using data value 00 or "reissue" by using data value 18.

  • BHT03 - originator's reference number; generated by the business application system of the entity building the original transaction.

  • BHT04 - date of transaction creation; generated by the business application system of the entity building the original transaction.

  • BHT05 - time of transaction creation; generated by the business application system of the entity building the original transaction.

  • BHT06 - designates transaction as Subrogation, fee-for-service, or capitated services.

1.4.3.2.2 Table 2 -- Detail Information

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

1.4.3.2.2.1 Hierarchical Level (HL) Segments

Section B.1.1.4.3 in Appendix B contains a general description of HL structures. The following describes the HL structure within the claim transaction.

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

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

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

1.4.3.2.2.2 Subscriber / Patient Hierarchical Level (HL) Segments

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

NOTE

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

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

Billing provider (HL03=20)

Subscriber (HL03=22)

Claim level information

Line level information, as needed

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

Billing provider (HL03=20)

Subscriber (HL03=22)

Patient (HL03=23)

Claim level information

Line level information, as needed

1.4.3.2.2.3 Hierarchical Level (HL) Structural Example

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

BILLING PROVIDER

SUBSCRIBER #1 (Patient #1)

Claim level information

Line level information, as needed

SUBSCRIBER #2

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

Claim level information

Line level information, as needed

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

Claim level information

Line level information, as needed

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

Claim level information

Line level information, as needed

SUBSCRIBER #3 (Patient #3)

Claim level information

Line level information, as needed

SUBSCRIBER #4 (Patient #4)

Claim level information

Line level information, as needed

SUBSCRIBER #4 (repeated)

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

Claim level information

Line level information, as needed

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

HL*1**20*1~
1   
**(blank)
    
20  
1   
HL*2*1*22*0~
2   
1   
22  
0   
HL*3*1*22*1~
3   
1   
22  
1   
HL*4*3*23*0~
4   
3   
23  
0   
HL*5*3*23*0~
5   
3   
23  
0   
HL*6*3*23*0~
6   
3   
23  
0   
HL*7*1*22*0~
7   
1   
22  
0   
HL*8*1*22*0~
8   
1   
22  
0   
HL*9*1*22*1~
9   
1   
22  
1   
HL*10*9*23*0~
10  
9   
23  
0   

If another billing provider is listed in the same ST-SE functional group, it could be listed as follows:

HL*100**20*1~
(BILLING PROVIDER)= HL sequence number= there is no parent HL (characteristic of the billing provider HL)= information source= there is at least one child HL to this HL (SUBSCRIBER #1)= HL sequence number= parent HL= subscriber= no subordinate HLs to this HL (there is no child HL to this HL - claim level data follows) (SUBSCRIBER #2)= HL sequence number= parent HL= subscriber= there is at least one child HL to this HL (PATIENT #P2.1)= HL sequence number= parent HL= dependent= no subordinate HLs in this HL (there is no child HL to this HL - data follows) (PATIENT #P2.2)= HL sequence number= parent HL= dependent= no subordinate HLs in this HL (there is no child HL to this HL - claim level data follows) (PATIENT #P2.3)= HL sequence number= parent HL= dependent= no subordinate HLs in this HL (there is no child HL to this HL - claim level data follows) (SUBSCRIBER AND PATIENT #3)= HL sequence number= parent HL= subscriber= no subordinate HLs in this HL (there is no child HL to this HL - claim level data follows) (SUBSCRIBER AND PATIENT #4)= HL sequence number= parent HL= subscriber= no subordinate HLs (SUBSCRIBER #4)= HL sequence number= parent HL= subscriber= there is at least one child HL to this HL (PATIENT #P4.1)= HL sequence number= parent HL= dependent= no subordinate HLs. The HL sequence number of 100 indicates that there are 99 previous HL segments and it is the billing provider level HL (HL03 = 20).
1.4.3.2.2.4 Hierarchical Level (HL) Structural Summary

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

  • HL segments are numbered sequentially within a transaction (ST to SE), beginning with 1. The sequential number is found in HL01, which is the first data element in the HL segment. Sequence number must be numeric.

  • The second element, HL02, indicates the sequential number of the parent hierarchical level. The billing provider/information source is the highest hierarchical level and therefore has no parent.

  • The data value in data element HL03 describes the hierarchical level entity. For example, when HL03 equals 20, the hierarchical level is the billing provider; when HL03 equals 23, the hierarchical level is the dependent (patient).

  • Data element HL04 indicates whether or not subordinate hierarchical levels exist. A value of "1" indicates subsequent hierarchical levels. A value of "0" indicates no subordinate hierarchical levels exist for this HL.

1.4.3.2.2.5 Claim Structure

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

  • Loop ID-2300 contains claim level information.

  • Loop ID-2310 identifies various claim specific providers who may have been involved in the health care services being reported in the transaction.

  • Loop ID-2320 identifies claim level adjudication information associated with non-destination, other payer information for the purpose of coordination of benefits.

  • Loop ID-2330 identifies the subscriber, payer, and provider identifiers associated with the non-destination, other payer.

  • Loop ID-2400 is required for all claims and identifies service line information.

  • Loop ID-2410 identifies drug and biologics information.

  • Loop ID-2420 identifies any service line providers who are different than claim level providers.

  • Loop ID-2430 identifies any service line adjudication information from another payer.

1.4.3.2.2.6 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 an 837 claim, the provider determines the code value from the code set (external Code Source 682) that most accurately describes the type and specialty classification under which the provider performed the services reported on the claim. The payer may not dictate the code value to be reported.

1.4.4 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.4.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, 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).

Expressed as a calculation for given payer: {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-2330B NM109.

Adjustment Calculations

Adjustments are reported in the CAS segments of Loop ID-2320 (claim level) and Loop ID-2430 (line level). In this context, Adjustment Amounts are the sum of CAS03, CAS06, CAS09, CAS12, CAS15, and CAS18. Adjustment amounts within the CAS segment DECREASE the payment amount when the adjustment amount is POSITIVE, and INCREASE the payment amount when the adjustment amount is NEGATIVE.

Claim Level Payment Amount

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

Example:

Claim Charge - 100.00

Claim Payment - 80.00

Claim Adjustment - 5.00

Line 1 Charge - 80.00

Line 1 Payment - 70.00

Line 1 Adjustment - 10.00

Line 2 Charge - 20.00

Line 2 Payment - 15.00

Line 2 Adjustment - 5.00

Claim Payment = (Line 1 Payment + Line 2 Payment) - Claim Adjustment

80.00 = (70.00 + 15.00) - 5.00

1.4.4.2 Service Line

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

Line level balancing occurs independently for each individual Line Adjudication Information loop. In order to balance, the sum of the line level adjustment amounts and line level payments in each Line Adjudication Information loop must balance to the provider's charge for that line (Loop ID-2400 SV102). The Line Adjudication Information loop can repeat up to 25 times for each line item.

The calculation for each 2430 loop is as follows: {sum of Loop ID-2430 CAS Service Line Adjustments} 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 Adjustments) + (Line 1 Payment) = Line Item 1 Charge

10.00 + 70.00 = 80.00

(Line 2 Adjustments) + (Line 2 Payment) = Line Item 2 Charge

5.00 + 15.00 = 20.00

1.4.5 Allowed/Approved Amount Calculation

During the development cycle of this version, one of the guiding principles was to remove all amount fields that can be calculated with other information already present in the claim. This resulted in the elimination of several AMT segments. Included in these, are the Approved and Allowed Amount segments. The workgroup has found these amounts vary in definition depending upon perspective. Although rare, there are times the provider's determination of what the allowed amount is different from the payers. This occurs for many various reasons. However, there has never been a way to recognize when these differences occur. As a result, the authors offer the following guidance as to how these amounts are calculated.

The Allowed amount as determined by the payer is calculated using the prior payer's payment information coupled with adjustment information in the CAS segments. The prior payer payment + the sum total of all patient responsible adjustment amounts = the Allowed amount. The Patient Responsible adjustments are identified by use of the Category Code PR in CAS01.

The Allowed amount as determined by the provider is calculated using the prior payer's payment information coupled with the Remaining Patient Liability AMT segments. The prior payer payment + the Remaining Patient Liability AMT amount = the Allowed amount.

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.

Bundling

Bundling occurs when a provider submits two or more reported procedure codes and the payer believes that the actual services performed and reported must be paid under only one (possibly different) procedure code.

Claim

For the purposes of this implementation guide, claim is intended to be an all inclusive term to represent both reimbursable claims and encounter reporting.

Dependent

In the hierarchical loop coding, the dependent code 23 indicates the use of the Patient Hierarchical loop (Loop ID-2000C).

Destination Payer

The destination payer is the payer who is specified in the Subscriber/Payer loop (Loop ID-2010BB).

Encounter

Non-reimbursable claim for which the health care encounter information is gathered for reporting. Also thought of as the reporting of a face-to-face encounter between a patient and a provider for which no reimbursement will be made. Often seen in pre-paid capitated financial arrangements in which the provider of services is paid in advance for the patient's health care needs. In some areas called a capitated or zero pay claim.

Inpatient

The determination of what constitutes an Inpatient Claim is defined by the National Uniform Billing Committee code set and documentation. See Section 1.12.6 - Inpatient and Outpatient Designation for more information about Inpatient and Outpatient designation.

Outpatient

The determination of what constitutes an Outpatient Claim is defined by the National Uniform Billing Committee code set and documentation. See Section 1.12.6 - Inpatient and Outpatient Designation for more information about Inpatient and Outpatient designation.

Pay-To Plan Claims

Pay-to plan claims are payment requests billed by one health plan directly to other health plans. These claims were originally submitted to and paid by the first health plan. An example of a pay-to plan claim is a payment request from a Medicaid agency direct to another health plan that may have liability for the member and services on the claim originally paid by the Medicaid agency.

Patient

The term patient is used in this implementation guide when the Patient loop (Loop ID-2000C) is used. In Loop ID-2000C, the patient is not the same person as the subscriber, and the patient is a person (for example, spouse, children, others) who is covered by the subscriber's insurance plan and does not have a unique member identification number. The person receiving services (in clinical terms, the patient) can be the same person as the subscriber. In that case, all information about that person is carried in the Subscriber loop (Loop ID-2000B).

See Section 1.4.3.2.2.2 - Subscriber / Patient Hierarchical Level (HL) Segments, and the notes for the SBR and PAT segments for further details. Every effort has been made to ensure that the meaning of the word patient is clear in its specific context.

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). Beginning with the 5010 version, the Billing Provider must be a health care or atypical provider (as described in Section 1.10.1 - Providers who are Not Eligible for Enumeration).

Secondary Payer

The term secondary payer indicates any payer who is not the primary payer. The secondary payer may be the secondary, tertiary, or even quaternary payer.

Subscriber

The subscriber is the person whose name is listed in the health insurance policy, or who has a unique member identification number. Other synonymous terms include member and/or insured. In some cases the subscriber is the person receiving services. See the definition of patient, and see Section 1.4.3.2.2.2 - Subscriber / Patient Hierarchical Level (HL) Segments, and the notes for the SBR and PAT segments for further details.

Transmission Intermediary

A transmission intermediary is any entity that handles the transaction between the provider (originator of the claim transmission) and the destination payer. The term intermediary is not used to convey a specific Medicare contractor type.

Unbundling

Unbundling occurs when a provider is billing multiple procedure codes for a group of procedures that are covered by a single comprehensive code. In other words, the provider submits one reported procedure code and the payer believes that the actual services performed and reported must be paid under two or more separate (possibly different) procedure codes. Unbundling also occurs when the units of service reported on one service line are broken out to two or more service lines for different reimbursement rates.

1.6 Transaction Acknowledgments

There are several acknowledgment implementation transactions available for use. The IG developers have noted acknowledgment requirements in this section. Other recommendations of acknowledgment transactions may be used at the discretion of the trading partners. A statement that the acknowledgment is not required does not preclude its use between willing trading partners.

1.6.1 997 Functional Acknowledgment

The 997 informs the submitter that the functional group arrived at the destination. It may include information about the syntactical quality of the functional group.

The Functional Acknowledgment (997) transaction is not required as a response to receipt of a batch transaction compliant with this implementation guide.

The Functional Acknowledgment (997) transaction is not required as a response to receipt of a real-time transaction compliant with this implementation guide.

A 997 Implementation Guide is being developed for use by the insurance industry and is expected to be available for use with this version of this Implementation Guide.

1.6.2 999 Implementation Acknowledgment

The 999 informs the submitter that the functional group arrived at the destination. It may include information about the syntactical quality of the functional group and the implementation guide compliance.

The Implementation Acknowledgment (999) transaction is not required as a response to receipt of a batch transaction compliant with this implementation guide.

The Implementation Acknowledgment (999) transaction is not required as a response to receipt of a real-time transaction compliant with this implementation guide.

A 999 Implementation Guide is being developed for use by the insurance industry and is expected to be available for use with this version of this Implementation Guide.

1.6.3 824 Application Advice

The 824 informs the submitter of the results of the receiving application system's data content edits of transaction sets.

The Application Advice (824) transaction is not required as a response to receipt of a batch transaction compliant with this implementation guide.

The Application Advice (824) transaction is not required as a response to receipt of a real-time transaction compliant with this implementation guide.

An 824 Implementation Guide is being developed for use by the insurance industry and is expected to be available for use with this version of this Implementation Guide.

1.6.4 277 Health Care Claim Acknowledgment

The 277 provides an application level acknowledgment of electronic claims. It may include information about the business validity and acceptability of the claims.

The Health Care Claim Acknowledgment (277) transaction is not required as a response to receipt of a batch transaction compliant with this implementation guide.

The Health Care Claim Acknowledgment (277) transaction is not required as a response to receipt of a real-time transaction compliant with this implementation guide.

1.7 Related Transactions

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

1.7.1 Health Care Claim Payment/Advice (835)

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

1.8 Trading Partner Agreements

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

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

1.10 National Provider Identifier Usage within the HIPAA 837 Transaction

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

  • Providers who are not eligible for enumeration

  • Implementation migration strategy

  • Organization health care provider subpart representation

  • Subparts and the billing provider

1.10.1 Providers who are Not Eligible for Enumeration

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

1.10.2 Implementation Migration Strategy

The ANSI ASC X12N Health Care Claims workgroup (TG2WG2) anticipates that during the transition period (i.e., the period from May 23, 2005 until the NPI compliance dates), the need to use both the NPI and proprietary identifiers to identify health care providers in the same standard claims transaction will be necessary. The implementation guides for the 837 transaction set have been modified to meet this need.

1.10.3 Organization Health Care Provider Subpart Representation

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

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

NOTE
In published versions prior to 5010, the Billing Provider may have been a variety of entities, including billing services and healthcare clearinghouses. Beginning with version 5010, the Billing Provider must be a health care or atypical service provider (as described in the section entitled Providers who are Not Eligible for Enumeration).

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

1.10.4 Subparts and the 2010 AA - Billing Provider Name Loop

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

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

Prior to the NPI compliance date, proprietary identifiers necessary for the receiver to identify the Billing Provider entity are to be reported in the REF segment of Loop ID-2010BB Payer Name. The TIN of the Billing Provider, used for IRS Form 1099 purposes, must be reported in the REF segment of Loop ID-2010AA Billing Provider.

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

1.11 Coding of Drugs in the 837 Claim

This section provides guidance on the coding of drug claims under HIPAA as accomplished in the 2400 and 2410 loops. For home infusion therapy care claims that include the drugs, biologics, and nutrition components of the total home infusion therapy encounters, refer to the 837 Health Care Claim: Professional implementation guide.

Regarding format, although National Drug Code (NDC) numbers may have different formats, all may be mapped to the 5-4-2 format used in this implementation guide, for example 12345-6789-01. NDC numbers are to be reported as an 11 character data stream with no separators. In other words, the hyphens are to be suppressed. HCPCS codes are always five characters in length.

1.11.1 Single Drug Billing

An 837 for a single drug will have one 2400 loop with the HCPCS code in SV101-2 and the associated units in SV104. When required by situational rules, the 2410 loop is sent with the NDC number in LIN03 and the associated quantity in CTP04. Loop ID-2410 REF02 contains a prescription number when the drug is provided under prescription.

1.11.2 Compound Drug Billing

An 837 for a multiple ingredient compound will have one 2400 loop for each ingredient with the HCPCS code in SV101-2, the provider's charge for that ingredient in SV102, and the associated units in SV104. When required by situational rules, the 2410 loop is sent with the NDC number in LIN03 with the associated quantity in CTP04. Loop ID-2410 REF02 must have the same prescription number, or the same linkage number if provided without a prescription, for each ingredient of the compound to enable the payer to differentiate and link the ingredients to a single compound.

1.12 Additional Instructions and Considerations

1.12.1 Individuals with one Legal Name

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

1.12.2 Rejecting Claims Based on the Inclusion of Situational Data

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

The purpose is to enable proper adjudication for any potential downstream payers as well as allow affected providers to collect and report information consistently for all trading partners when desired. As a result, the submitter is not restricted from sending the information to other payers in addition to the specific payer that has a known adjudication impact.

1.12.3 Multiple REF Segments with the same Qualifier

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

1.12.4 Provider Tax IDs

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

1.12.5 Claim and Line Redundant Information

This implementation guide supports the reporting of some information at the claim and the service levels to enable the reporting of individual line specific information. The line level usage notes for these pieces of information state "Required when different than that reported at the claim level. If not required by this implementation guide, do not send." This wording results in the potential for misinterpretation resulting in unintended rigidity. These usage notes, as written with the "do not send" statement, should be applied as establishing the conditions when a submitter must send, and when a submitter is not required to send, the line level information. This "do not send" statement does not establish situations where a receiver is allowed, or is required, to reject a claim. That would be placing an unnecessary burden on the sender. The appropriate action by a receiver is to "ignore, but don't reject" this redundant claim/line information. If redundant data segments or elements are reported but are not necessary for the receiver within their application, the receiver ignores the information that is not needed. The presence of the unneeded information must not cause the transaction to be rejected.

These usage notes do not permit a receiver to request or require the redundant line level data. Sending the redundant data is strictly at the submitter's discretion.

An example of this would be Rendering Provider information that is supported in the 2310 and 2420 loops of the Institutional, Professional, and Dental implementation guides. The same Rendering Provider information might be reported at both the claim and line levels. This situation would not alter the payment of that claim nor complicate the adjudication algorithms. Consequently, rejecting any claims because of the presence of this redundant data would unnecessarily burden the provider community and further complicate the claim process.

Other examples exist in the claim implementation guides where the business cases open up the possibility for redundant data to be reported. For all such situations, the principle is to "ignore, but don't reject".

1.12.6 Inpatient and Outpatient Designation

The determination of what constitutes an Inpatient or Outpatient claim is defined in the external code set developed by the National Uniform Billing Committee in its Data Specifications Manual (UB Manual) beginning with UB-04. General guidelines are contained in the Type of Bill section of the UB Manual. Inpatient and Outpatient claims are distinguished by Type of Bill and other factors. Certain bill types are designated for inpatient use while others are designated for outpatient reporting. Exceptions to the general rules are documented with reference to the specific data elements affected.

1.12.7 Trading Partner Acknowledgments

The authors of this implementation guide strongly encourage submitters of this transaction to expect and require standard electronic acknowledgments from receivers. The authors encourage receivers to expect and require submitters to have an operational capability to accept and take action on standard electronic acknowledgments.

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 Implementation Usage

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 segment is used.

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

3. Examples

  • Please visit http://www.wpc-edi.com/837 for additional or corrected examples.

3.1 Professional

3.1.1 Example 1 - Commercial Health Insurance

Patient is a different person than the Subscriber. Payer is commercial health insurance company.

SUBSCRIBER: Jane Smith

PATIENT ADDRESS:236 N. Main St., Miami, Fl, 33413

TELEPHONE NUMBER: 305-555-1111

SEX: F

DOB: 05/01/43

EMPLOYER: ACME Inc.

GROUP #: 2222-SJ

KEY INSURANCE COMPANY ID #: JS00111223333

PATIENT: Ted Smith

PATIENT ADDRESS:236 N. Main St., Miami, Fl, 33413

TELEPHONE NUMBER: 305-555-1111

SEX: M

DOB: 05/01/73

KEY INSURANCE COMPANY ID #: JS01111223333

DESTINATION PAYER: Key Insurance Company

PAYER ADDRESS: 3333 Ocean St. South Miami, FL 33000

PAYER ID: 999996666

SUBMITTER: Premier Billing Service

EDI#: TGJ23

CONTACT PERSON AND PHONE NUMBER: JERRY, 305-555-2222 ext. 231

RECEIVER: Key Insurance Company

EDI #:66783JJT

BILLING PROVIDER: Dr. Ben Kildare,

ADDRESS: 234 Seaway St, Miami, FL, 33111

NPI: 9876543210

TIN: 587654321

KEY INSURANCE COMPANY PROVIDER ID #: KA6663

Taxonomy Code: 203BF0100Y

PAY-TO PROVIDER: Kildare Associates,

PROVIDER ADDRESS: 2345 Ocean Blvd, Miami, Fl 33111

RENDERING PROVIDER: Dr. Ben Kildare

PATIENT ACCOUNT NUMBER: 2-646-3774

CASE: Patient has sore throat.

INITIAL VISIT: DOS=10/03/06. POS=Office

SERVICES: Office visit, intermediate service, established patient, throat culture.

CHARGES: Office first visit = $40.00, Lab test for strep = $15.00

FOLLOW-UP VISIT: DOS=10/10/06 POS=Office

Antibiotics didn't work (pain continues).

SERVICES: Office visit, intermediate service, established patient, mono screening.

CHARGES: Follow-up visit = $35.00, lab test for mono = $10.00.

TOTAL CHARGES: $100.00.

ELECTRONIC ROUTE: Billing provider (sender), to VAN to Key Insurance Company (receiver). VAN claim identification number = 17312345600006351.

SEG #

LOOP SEGMENT/ELEMENT STRING

1

HEADER

ST TRANSACTION SET HEADER

ST*837*0021*005010X222A2~

2

BHT BEGINNING OF HIERARCHICAL TRANSACTION

BHT*0019*00*244579*20061015*1023*CH~

3

1000A SUBMITTER

NM1 SUBMITTER NAME

NM1*41*2*PREMIER BILLING                        SERVICE*****46*TGJ23~

4

PER SUBMITTER EDI CONTACT INFORMATION

PER*IC*JERRY*TE*3055552222*EX*231~

5

1000B RECEIVER

NM1 RECEIVER NAME

NM1*40*2*KEY INSURANCE                        COMPANY*****46*66783JJT~

6

2000A BILLING PROVIDER HL LOOP

HL - BILLING PROVIDER

HL*1**20*1~

7

PRV BILLING PROVIDER SPECIALTY INFORMATION

PRV*BI*PXC*203BF0100Y~

8

2010AA BILLING PROVIDER

NM1 BILLING PROVIDER NAME

NM1*85*2*BEN KILDARE                        SERVICE*****XX*9876543210~

9

N3 BILLING PROVIDER ADDRESS

N3*234 SEAWAY ST~

10

N4 BILLING PROVIDER LOCATION

N4*MIAMI*FL*33111~

11

REF - BILLING PROVIDER TAX IDENTIFICATION

REF*EI*587654321~

12

2010AB PAY-TO PROVIDER

NM1 PAY-TO PROVIDER NAME

NM1*87*2~

13

N3 PAY-TO PROVIDER ADDRESS

N3*2345 OCEAN BLVD~

14

N4 PAY-TO PROVIDER CITY

N4*MAIMI*FL*33111~

15

2000B SUBSCRIBER HL LOOP

HL - SUBSCRIBER

HL*2*1*22*1~

16

SBR SUBSCRIBER INFORMATION

SBR*P**2222-SJ******CI~

17

2010BA SUBSCRIBER

NM1 SUBSCRIBER NAME

NM1*IL*1*SMITH*JANE****MI*JS00111223333~

18

DMG SUBSCRIBER DEMOGRAPHIC INFORMATION

DMG*D8*19430501*F~

19

2010BB PAYER

NM1 PAYER NAME

NM1*PR*2*KEY INSURANCE COMPANY*****PI*999996666~

20

REF BILLING PROVIDER SECONDARY IDENTIFICATION

REF*G2*KA6663~

21

2000C PATIENT HL LOOP

HL - PATIENT

HL*3*2*23*0~

22

PAT PATIENT INFORMATION

PAT*19~

23

2010CA PATIENT

NM1 PATIENT NAME

NM1*QC*1*SMITH*TED~

24

N3 PATIENT ADDRESS

N3*236 N MAIN ST~

25

N4 PATIENT CITY/STATE/ZIP

N4*MIAMI*FL*33413~

26

DMG PATIENT DEMOGRAPHIC INFORMATION

DMG*D8*19730501*M~

27

2300 CLAIM

CLM CLAIM LEVEL INFORMATION

CLM*26463774*100***11:B:1*Y*A*Y*I~

28

REF CLAIM IDENTIFICATION NUMBER FOR CLEARING HOUSES (Added by C.H.)

REF*D9*17312345600006351~

29

HI HEALTH CARE DIAGNOSIS CODES

HI*BK:0340*BF:V7389~

30

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*1~

31

SV1 PROFESSIONAL SERVICE

SV1*HC:99213*40*UN*1***1~

32

DTP DATE - SERVICE DATE(S)

DTP*472*D8*20061003~

33

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*2~

34

SV1 PROFESSIONAL SERVICE

SV1*HC:87070*15*UN*1***1~

35

DTP DATE - SERVICE DATE(S)

DTP*472*D8*20061003~

36

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*3~

37

SV1 PROFESSIONAL SERVICE

SV1*HC:99214*35*UN*1***2~

38

DTP DATE - SERVICE DATE(S)

DTP*472*D8*20061010~

39

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*4~

40

SV1 PROFESSIONAL SERVICE

SV1*HC:86663*10*UN*1***2~

41

DTP DATE - SERVICE DATE(S)

DTP*472*D8*20061010~

42

TRAILER

SE TRANSACTION SET TRAILER

SE*42*0021~

Complete Data String:

ST*837*0021*005010X222A2~BHT*0019*00*244579*20061015*1023*CH

~NM1*41*2*PREMIER BILLING SERVICE*****46*TGJ23~PER*IC*JERRY*

TE*3055552222*EX*231~NM1*40*2*KEY INSURANCE COMPANY*****46*6

6783JJT~HL*1**20*1~PRV*BI*PXC*203BF0100Y~NM1*85*2*BEN KILDAR

E SERVICE*****XX*9876543210~N3*234 SEAWAY ST~N4*MIAMI*FL*331

11~REF*EI*587654321~NM1*87*2~N3*2345 OCEAN BLVD~N4*MAIMI*FL*

33111~HL*2*1*22*1~SBR*P**2222-SJ******CI~NM1*IL*1*SMITH*JANE

****MI*JS00111223333~DMG*D8*19430501*F~NM1*PR*2*KEY INSURANC

E COMPANY*****PI*999996666~REF*G2*KA6663~HL*3*2*23*0~PAT*19~

NM1*QC*1*SMITH*TED~N3*236 N MAIN ST~N4*MIAMI*FL*33413~DMG*D8

*19730501*M~CLM*26463774*100***11:B:1*Y*A*Y*I~REF*D9*1731234

5600006351~HI*BK:0340*BF:V7389~LX*1~SV1*HC:99213*40*UN*1***1

~DTP*472*D8*20061003~LX*2~SV1*HC:87070*15*UN*1***1~DTP*472*D

8*20061003~LX*3~SV1*HC:99214*35*UN*1***2~DTP*472*D8*20061010

~LX*4~SV1*HC:86663*10*UN*1***2~DTP*472*D8*20061010~SE*42*002

1~

3.1.2 Example 2 - Encounter

Patient is the same person as the Subscriber. Payer is an HMO. Encounter is transmitted through a clearinghouse. Submitter is the billing provider, receiver is a payer.

SUBSCRIBER/PATIENT: Ted Smith

ADDRESS: 236 N. Main St., Miami, Fl, 33413,

TELEPHONE NUMBER: 305-555-1111

SEX: M

DOB: 05/01/43

EMPLOYER: ACME Inc.

GROUP #: 12312-A

PAYER ID NUMBER: SSN

SSN: 000-22-1111

DESTINATION PAYER: Alliance Health and Life Insurance Company (AHLIC),

PAYER ADDRESS: 2345 West Grand Blvd, Detroit, MI 48202. ,

AHLIC #: 741234

SUBMITTER: Premier Billing Service

EDI#: TGJ23

CONTACT PERSON AND PHONE NUMBER: JERRY, 305-555-2222 ext. 231

RECEIVER: Alliance Health and Life Insurance Company (AHLIC),

EDI #: 66783JJT

BILLING PROVIDER: Dr. Ben Kildare,

ADDRESS: 234 Seaway St, Miami, FL, 33111

NPI: 9876543210

TIN: 587654321

Taxonomy Code: 203BF0100Y

PAY-TO PROVIDER: Kildare Associates,

PROVIDER ADDRESS: 2345 Ocean Blvd, Miami, Fl 33111

RENDERING PROVIDER: Dr. Ben Kildare/Family Practitioner

PATIENT ACCOUNT NUMBER: 2-646-2967

CASE: Patient has sore throat.

INITIAL VISIT: DOS=10/03/06. POS=Office

SERVICES: Office visit, intermediate service, established patient, throat culture.

CHARGES: Office first visit = $40.00, Lab test for strep = $15.00

FOLLOW-UP VISIT: DOS=10/10/06 POS=Office

Antibiotics didn't work (pain continues).

SERVICES: Office visit, intermediate service, established patient, mono screening.

CHARGES: Follow-up visit = $35.00, lab test for mono = $10.00.

TOTAL CHARGES: $100.00.

ELECTRONIC ROUTE: Billing provider (sender) to Clearinghouse to Alliance Health and Life Insurance Company (AHLIC);

Clearinghouse claim identification number = 17312345600006351.

SEG #

LOOP SEGMENT/ELEMENT STRING

1

HEADER

ST TRANSACTION SET HEADER

ST*837*0021*005010X222A2~

2

BHT BEGINNING OF HIERARCHICAL TRANSACTION

BHT*0019*00*0123*20061015*1023*RP~

3

1000A SUBMITTER

NM1 SUBMITTER NAME

NM1*41*2*PREMIER BILLING SERVICE*****46*TGJ23~

4

PER SUBMITTER EDI CONTACT INFORMATION

PER*IC*JERRY*TE*3055552222*EX*231~

5

1000B RECEIVER

NM1 RECEIVER NAME

NM1*40*2* AHLIC*****46*66783JJT~

6

2000A BILLING PROVIDER HL LOOP

HL - BILLING PROVIDER

HL*1**20*1~

7

PRV BILLING PROVIDER SPECIALTY INFORMATION

PRV*BI*PXC*203BF0100Y~

8

2010AA BILLING PROVIDER

NM1 BILLING PROVIDER NAME

NM1*85*2*BEN KILDARE SERVICE*****XX*9876543210~

9

N3 BILLING PROVIDER ADDRESS

N3*234 SEAWAY ST~

10

N4 BILLING PROVIDER LOCATION

N4*MIAMI*FL*33111~

11

REF - BILLING PROVIDER TAX IDENTIFICATION

REF*EI*587654321~

12

2010AB PAY-TO PROVIDER

NM1 PAY-TO PROVIDER NAME

NM1*87*2~

13

N3 PAY-TO PROVIDER ADDRESS

N3*2345 OCEAN BLVD~

14

N4 PAY-TO PROVIDER CITY

N4*MIAMI*FL*33111~

15

2000B SUBSCRIBER HL LOOP

HL - SUBSCRIBER

HL*2*1*22*0~

16

SBR SUBSCRIBER INFORMATION

SBR*P*18*12312-A******HM~

17

2010BA SUBSCRIBER

NM1 SUBSCRIBER NAME

NM1*IL*1*SMITH*TED****MI*000221111~

18

N3 SUBSCRIBER ADDRESS

N3*236 N MAIN ST~

19

N4 SUBSCRIBER CITY

N4*MIAMI*FL*33413~

20

DMG SUBSCRIBER DEMOGRAPHIC INFORMATION

DMG*D8*19430501*M~

21

2010BB SUBSCRIBER/PAYER

NM1 PAYER NAME

NM1*PR*2*ALLIANCE HEALTH AND LIFE INSURANCE*****PI*741234~

22

2300 CLAIM

CLM CLAIM LEVEL INFORMATION

CLM*26462967*100***11:B:1*Y*A*Y*I~

23

DTP DATE OF ONSET

DTP*431*D8*19981003~

24

REF CLEARING HOUSE CLAIM NUMBER (Added by CH)

REF*D9*17312345600006351~

25

HI HEALTH CARE DIAGNOSIS CODES

HI*BK:0340*BF:V7389~

26

2310D SERVICE LOCATION

NM1 SERVICE FACILITY LOCATION

NM1*77*2*KILDARE ASSOCIATES*****XX*5812345679~

27

N3 SERVICE FACILITY ADDRESS

N3*2345 OCEAN BLVD~

28

N4 SERVICE FACILITY CITY/STATE/ZIP

N4*MIAMI*FL*33111~

29

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*1~

30

SV1 PROFESSIONAL SERVICE

SV1*HC:99213*40*UN*1***1~

31

DTP DATE - SERVICE DATE(S)

DTP*472*D8*20061003~

32

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*2~

33

SV1 PROFESSIONAL SERVICE

SV1*HC:87072*15*UN*1***1~

34

DTP DATE - SERVICE DATE(S)

DTP*472*D8*20061003~

35

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*3~

36

SV1 PROFESSIONAL SERVICE

SV1*HC:99214*35*UN*1***2~

37

DTP DATE - SERVICE DATE(S)

DTP*472*D8*20061010~

38

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*4~

39

SV1 PROFESSIONAL SERVICE

SV1*HC:86663*10*UN*1***2~

40

DTP DATE - SERVICE DATE(S)

DTP*472*D8*20061010~

41

TRAILER

SE TRANSACTION SET TRAILER

SE*41*0021~

Complete Data String:

ST*837*0021*005010X222A2~BHT*0019*00*0123*20061015*1023*RP~N

M1*41*2*PREMIER BILLING SERVICE*****46*TGJ23~PER*IC*JERRY*TE

*3055552222*EX*231~NM1*40*2*AHLIC*****46*66783JJT~HL*1**20*1

~PRV*BI*PXC*203BF0100Y~NM1*85*2*BEN KILDARE SERVICE*****XX*9

876543210~N3*234 SEAWAY ST~N4*MIAMI*FL*33111~REF*EI*58765432

1~NM1*87*2~N3*2345 OCEAN BLVD~N4*MIAMI*FL*33111~HL*2*1*22*0~

SBR*P*18*12312-A******HM~NM1*IL*1*SMITH*TED****MI*00221111~N

3*236 N MAIN ST~N4*MIAMI*FL*33413~DMG*D8*19430501*M~NM1*PR*2

*ALLIANCE HEALTH AND LIFE INSURANCE*****PI*741234~CLM*264629

67*100***11:B:1*Y*A*Y*I~DTP*431*D8*19981003~REF*D9*173123456

00006351~HI*BK:0340*BF:V7389~NM1*77*2*KILDARE ASSOCIATES****

*XX*5812345679~N3*2345 OCEAN BLVD~N4*MIAMI*FL*33111~LX*1~SV1

*HC:99213*40*UN*1***1~DTP*472*D8*20061003~LX*2~SV1*HC:87072*

15*UN*1***1~DTP*472*D8*20061003~LX*3~SV1*HC:99214*35*UN*1***

2~DTP*472*D8*20061010~LX*4~SV1*HC:86663*10*UN*1***2~DTP*472*

D8*20061010~SE*41*0021~

3.1.3 Example 3 - Coordination of benefits (COB)

Coordination of benefits; patient is not the subscriber; payers are commercial health insurance companies. Patient and subscriber have same primary policy number. Claim submitted to primary insurer with information pertaining to the secondary payer.

SUBSCRIBER FOR PAYER A: Jane Smith

ADDRESS: 236 N. Main St., Miami, Fl 33413

TELEPHONE NUMBER: 305-555-1111

SEX: F

DOB: 05/01/43

EMPLOYER: Acme, Inc.

PAYER A ID NUMBER: JS00111223333

SSN: 111-22-3333

SUBSCRIBER FOR PAYER B: Jack Smith

ADDRESS: 236 N. Main St., Miami, Fl 33413

TELEPHONE NUMBER: 305-555-1111

SEX: M

DOB: 10/22/43

EMPLOYER: Telecom of Florida

PAYER B ID NUMBER: T55TY666

SSN: 222-33-4444

PATIENT: Ted Smith

ADDRESS: 236 N. Main St., Miami, Fl 33413

TELEPHONE NUMBER: 305-555-1111

SEX: M

DOB: 05/01/73

PAYER A ID NUMBER: JS01111223333

PAYER B ID NUMBER: T55TY666-01

SSN: 000-22-1111

DESTINATION PAYER A: Key Insurance Company

PAYER A ADDRESS: 3333 Ocean St., South Miami, FL, 33000

PAYER A ID NUMBER: (TIN) 999996666

RECEIVER FOR PAYER A: XYZ REPRICER

EDI #: 66783JJT

RECEIVER: Alliance Health and Life Insurance Company (AHLIC),

EDI #: 66783JJT

DESTINATION PAYER B (RECEIVER): Great Prairies Health

PAYER B ADDRESS: 4456 South Shore Blvd., Chicago, IL 44444

PAYER B ID NUMBER: 567890

EDI #: 567890

BILLING PROVIDER/SENDER: Dr. Ben Kildare

ADDRESS: 234 Seaway St, Miami, FL, 33111

PAYER A ID NUMBER: KA6663

PAYER B ID NUMBER: 88877

TIN: 999996666

EDI # FOR RECEIVER A: TGJ23

EDI # FOR PAYER B: 12EEER000TY

PAY-TO PROVIDER: Kildare Associates,

ADDRESS: 2345 Ocean Blvd, Miami, Fl 33111

PAYER A ID NUMBER: 99878ABA

PAYER B ID NUMBER: EX7777

TIN: 581234567

RENDERING PROVIDER: Dr. Ben Kildare

PAYER A ID NUMBER: KA6663

PAYER B ID NUMBER: 88877

TIN: 999996666

PATIENT ACCOUNT NUMBER: 26407789

CASE: Patient came to office for routine hyperlipidemia check. DOS=10/03/05,

POS=Office; Patient also complained of hay fever and heart burn.

SERVICES RENDERED: Patient received injection for hyperlipidemia and hay fever.

CHARGES: Patient was charged for office visit ($43.00), and two injections ($15.00 and $21.04).

ELECTRONIC PATH: The billing provider (sender) transmits the claim to Payer A (receiver) (Example 3.A) who adjudicates the claim. Payer A transmits back an 835 to the billing provider. The billing provider then submits a second claim to Payer B (receiver) (Example 3.B).

3.1.3.1 Example 3.A -- Claim from Billing Provider to Payer A

SEG #

LOOP SEGMENT/ELEMENT STRING

1

HEADER

ST TRANSACTION SET HEADER

ST*837*0021*005010X222A2~

2

BHT BEGINNING OF HIERARCHICAL TRANSACTION

BHT*0019*00*0123*20051015*1023*CH~

3

1000A SUBMITTER

NM1 SUBMITTER NAME

NM1*41*2*PREMIER BILLING                                SERVICE*****46*TGJ23~

4

PER SUBMITTER EDI CONTACT INFORMATION

PER*IC*JERRY*TE*3055552222~

5

1000B RECEIVER

NM1 RECEIVER NAME

NM1*40*2*XYZ                            REPRICER*****46*66783JJT~

6

2000A BILLING PROVIDER HL LOOP

HL - BILLING PROVIDER

HL*1**20*1~

7

2010AA BILLING PROVIDER

NM1 BILLING PROVIDER NAME

NM1*85*1*KILDARE*BEN****XX*1999996666~

8

N3 BILLING PROVIDER ADDRESS

N3*1234 SEAWAY ST~

9

N4 BILLING PROVIDER CITY/STATE/ZIP

N4*MIAMI*FL*33111~

10

REF - BILLING PROVIDER TAX IDENTIFICATION

REF*EI*123456789~

11

PER BILLING PROVIDER CONTACT INFORMATION

PER*IC*CONNIE*TE*3055551234~

12

2010AB PAY-TO PROVIDER

NM1 PAY-TO PROVIDER NAME

NM1*87*2~

13

N3 PAY-TO PROVIDER ADDRESS

N3*2345 OCEAN BLVD~

14

N4 PAY-TO PROVIDER CITY/STATE/ZIP

N4*MIAMI*FL*33111~

15

2000B SUBSCRIBER HL LOOP

HL - SUBSCRIBER

HL*2*1*22*1~

16

SBR SUBSCRIBER INFORMATION

SBR*P*******CI~

17

2010BA SUBSCRIBER

NM1 SUBSCRIBER NAME

NM1*IL*1*SMITH*JANE****MI*111223333~

18

DMG SUBSCRIBER DEMOGRAPHIC INFORMATION

DMG*D8*19430501*F~

19

2010BB PAYER

NM1 PAYER NAME

NM1*PR*2*KEY INSURANCE                                COMPANY*****PI*999996666~

20

N3 PAYER ADDRESS

N3*3333 OCEAN ST~

21

N4 PAYER CITY/STATE/ZIP

N4*SOUTH MIAMI*FL*33000~

22

REF BILLING PROVIDER SECONDARY IDENTIFICATION

REF*G2*PBS3334~

23

2000C PATIENT HL LOOP

HL - PATIENT

HL*3*2*23*0~

24

PAT PATIENT INFORMATION

PAT*19~

25

2010CA PATIENT

NM1 PATIENT NAME

NM1*QC*1*SMITH*TED~

26

N3 PATIENT ADDRESS

N3*236 N MAIN ST~

27

N4 PATIENT CITY/STATE/ZIP

N4*MIAMI*FL*33413~

28

DMG PATIENT DEMOGRAPHIC INFORMATION

DMG*D8*19730501*M~

29

2300 CLAIM

CLM CLAIM LEVEL INFORMATION

CLM*26407789*79.04***11:B:1*Y*A*Y*I*P~

30

HI HEALTH CARE DIAGNOSIS CODES

HI*BK:4779*BF:2724*BF:2780*BF:53081~

31

2310B RENDERING PROVIDER

NM1 RENDERING PROVIDER NAME

NM1*82*1*KILDARE*BEN****XX*1999996666~

32

PRV RENDERING PROVIDER INFORMATION

PRV*PE*PXC*204C00000X~

33

REF RENDERING PROVIDER SECONDARY IDENTIFICATION

REF*G2*KA6663~

34

2310D SERVICE FACILITY LOCATION

NM1 SERVICE FACILITY LOCATION

NM1*77*2*KILDARE                                ASSOCIATES*****XX*1581234567~

35

N3 SERVICE FACILITY ADDRESS

N3*2345 OCEAN BLVD~

36

N4 SERVICE FACILITY CITY/STATE/ZIP

N4*MIAMI*FL*33111~

37

2320 OTHER SUBSCRIBER INFORMATION

SBR OTHER SUBSCRIBER INFORMATION

SBR*S*01*******CI~

38

DMG SUBSCRIBER DEMOGRAPHIC INFORMATION

DMG*D8*19430501*F~

39

OI OTHER INSURANCE COVERAGE INFORMATION

OI***Y*P**Y~

40

2330A OTHER SUBSCRIBER NAME

NM1 OTHER SUBSCRIBER NAME

NM1*IL*1*SMITH*JACK****MI*T55TY666~

41

N3 OTHER SUBSCIBER ADDRESS

N3*236 N MAIN ST~

42

N4 OTHER SUBSCIBER CITY

N4*MIAMI*FL*33111~

43

2330B OTHER SUBSCRIBER/PAYER

NM1 OTHER PAYER NAME

NM1*PR*2*KEY INSURANCE                                COMPANY*****PI*999996666~

44

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*1~

45

SV1 PROFESSIONAL SERVICE

SV1*HC:99213*43*UN*1***1:2:3:4~

46

DTP DATE - SERVICE DATE(S)

DTP*472*D8*20051003~

47

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*2~

48

SV1 PROFESSIONAL SERVICE

SV1*HC:90782*15*UN*1***1:2~

49

DTP DATE - SERVICE DATE(S)

DTP*472*D8*20051003~

50

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*3~

51

SV1 PROFESSIONAL SERVICE

SV1*HC:J3301*21.04*UN*1***1:2~

52

DTP DATE - SERVICE DATE(S)

DTP*472*D8*20051003~

53

TRAILER

SE TRANSACTION SET TRAILER

SE*53*0021~

Complete Data String For Example 3.A:

ST*837*0021*005010X222A2~BHT*0019*00*0123*20051015*1023*CH~N

M1*41*2*PREMIER BILLING SERVICE*****46*TGJ23~PER*IC*JERRY*TE

*3055552222~NM1*40*2*XYZ REPRICER*****46*66783JJT~HL*1**20*1

~NM1*85*1*KILDARE*BEN****XX*1999996666~N3*1234 SEAWAY ST~N4*

MIAMI*FL*33111~REF*EI*123456789~PER*IC*CONNIE*TE*3055551234~

NM1*87*2~N3*2345 OCEAN BLVD~N4*MIAMI*FL*33111~HL*2*1*22*1~SB

R*P*******CI~NM1*IL*1*SMITH*JANE****MI*111223333~DMG*D8*1943

0501*F~NM1*PR*2*KEY INSURANCE COMPANY*****PI*999996666~N3*33

33 OCEAN ST~N4*SOUTH MIAMI*FL*33000~REF*G2*PBS3334~HL*3*2*23

*0~PAT*19~NM1*QC*1*SMITH*TED~N3*236 N MAIN ST~N4*MIAMI*FL*33

413~DMG*D8*19730501*M~CLM*26407789*79.04***11:B:1*Y*A*Y*I*P~

HI*BK:4779*BF:2724*BF:2780*BF:53081~NM1*82*1*KILDARE*BEN****

XX*1999996666~PRV*PE*PXC*204C00000X~REF*G2*KA6663~NM1*77*2*K

ILDARE ASSOCIATES*****XX*1581234567~N3*2345 OCEAN BLVD~N4*MI

AMI*FL*33111~SBR*S*01*******CI~DMG*D8*19430501*F~OI***Y*P**Y

~NM1*IL*1*SMITH*JACK****MI*T55TY666~N3*236 N MAIN ST~N4*MIAM

I*FL*33111~NM1*PR*2*KEY INSURANCE COMPANY*****PI*999996666~L

X*1~SV1*HC:99213*43*UN*1***1:2:3:4~DTP*472*D8*20051003~LX*2~

SV1*HC:90782*15*UN*1***1:2~DTP*472*D8*20051003~LX*3~SV1*HC:J

3301*21.04*UN*1***1:2~DTP*472*D8*20051003~SE*53*0021~

Payer A returned an electronic remittance advice (835) to the Billing Provider with the following amounts and Claim Adjustment Reason Codes:

SUBMITTED CHARGES (CLP03): 79.04

AMOUNT PAID (CLP04): 39.15

PATIENT RESPONSIBILITY (CLP05): 36.89

The CAS at the Claim level was:

CAS*PR*1*21.89**2*15~ (INDICATES A $15.00 CO-INSURANCE PAYMENT AND $21.89 DEDUCTIBLE PAYMENT IS DUE FROM PATIENT).

In addition, Payer A adjusted the office visit charges to $40.00 by Contractual Agreement. The CAS on line 1 was: CAS*CO*42*3~. Because the other lines did not have adjustments, there are no CAS segments for those lines.

See the Introduction for a discussion on cross walking 835s to 837s.

3.1.3.2 Example 3.B -- Claim from Billing Provider to Payer B

SEG #

LOOP SEGMENT/ELEMENT STRING

1

HEADER

ST TRANSACTION SET HEADER

ST*837*1234*005010X222A2~

2

BHT BEGINNING OF HIERARCHICAL TRANSACTION

BHT*0019*00*0123*20051015*1023*CH~

3

1000A SUBMITTER

NM1 SUBMITTER

NM1*41*2*PREMIER BILLING                                SERVICE*****46*12EEER000TY~

4

PER SUBMITTER EDI CONTACT INFORMATION

PER*IC*JERRY*TE*3055552222~

5

1000B RECEIVER

NM1 RECEIVER

NM1*40*2*GREAT PRARIES                            HEALTH*****46*567890~

6

2000A BILLING PROVIDER HL LOOP

HL - BILLING PROVIDER

HL*1**20*1~

7

2010AA BILLING PROVIDER

NM1 BILLING PROVIDER

NM1*85*1*KILDARE*BEN****XX*1999996666~

8

N3 BILLING PROVIDER ADDRESS

N3*1234 SEAWAY ST~

9

N4 BILLING PROVIDER CITY

N4*MIAMI*FL*33111~

10

REF - BILLING PROVIDER TAX ID

REF*EI*123456789~

11

PER BILLING CONTACT INFORMATION

PER*IC*CONNIE*TE*3055551234~

12

2010AB PAY-TO PROVIDER

NM1 PAY-TO PROVIDER NAME

NM1*87*2~

13

N3 PAY-TO PROVIDER ADDRESS

N3*2345 OCEAN BLVD~

14

N4 PAY-TO PROVIDER CITY

N4*MIAMI*FL*33111~

15

2000B SUBSCRIBER HL LOOP

HL - SUBSCRIBER

HL*2*1*22*1~

16

SBR SUBSCRIBER INFORMATION

SBR*S*******CI~

17

2010BA SUBSCRIBER

NM1 SUBSCRIBER NAME

NM1*IL*1*SMITH*JACK****MI*222334444~

18

DMG SUBSCRIBER DEMOGRAPHIC INFORMATION

DMG*D8*19431022*M~

19

2010BB PAYER

NM1 PAYER NAME

NM1*PR*2*GREAT PRAIRIES                            HEALTH*****PI*567890~

20

N3 PAYER ADDRESS

N3*4456 SOUTH SHORE BLVD~

21

N4 PAYER CITY/STATE/ZIP CODE

N4*CHICAGO*IL*44444~

22

REF BILLING PROVIDER SECONDARY IDENTIFICATION

REF*G2*567890~

23

2000C PATIENT HL LOOP

HL - PATIENT

HL*3*2*23*0~

24

PAT PATIENT INFORMATION

PAT*19~

25

2010CA PATIENT

NM1 PATIENT NAME

NM1*QC*1*SMITH*TED~

26

N3 PATIENT ADDRESS

N3*236 N MAIN ST~

27

N4 PATIENT CITY

N4*MIAMI*FL*33413~

28

DMG PATIENT DEMOGRAPHIC INFORMATION

DMG*D8*19730501*M~

29

2300 CLAIM

CLM CLAIM LEVEL INFORMATION

CLM*26407789*79.04***11:B:1*Y*A*Y*I~

30

HI HEALTH CARE DIAGNOSIS CODES

HI*BK:4779*BF:2724*BF:2780*BF:53081~

31

2310B RENDERING PROVIDER

NM1 RENDERING PROVIDER NAME

NM1*82*1*KILDARE*BEN****XX*1999996666~

32

PRV RENDERING PROVIDER INFORMATION

PRV*PE*PXC*204C00000X~

33

REF RENDERING PROVIDER SECONDARY IDENTIFICATION

REF*G2*88877~

34

2310D SERVICE FACILITY LOCATION

NM1 SERVICE FACILITY LOCATION

NM1*77*2*KILDARE                            ASSOCIATES*****XX*1581234567~

35

N3 SERVICE FACILITY ADDRESS

N3*2345 OCEAN BLVD~

36

N4 SERVICE FACILITY CITY/STATE/ZIP

N4*MIAMI*FL*33111~

37

2320 OTHER SUBSCRIBER INFORMATION

SBR OTHER SUBSCRIBER INFORMATION

SBR*P*01*******CI~

38

CAS CLAIM LEVEL ADJUSTMENTS AND AMOUNTS

CAS*PR*1*21.89**2*15~

39

AMT COORDINATION OF BENEFITS - PAYOR PAID AMOUNT

AMT*D*39.15~

40

AMT COORDINATION OF BENEFITS – PATIENT RESPONSBILITY

AMT*EAF*36.89~

41

DMG SUBSCRIBER DEMOGRAPHIC INFORMATION

DMG*D8*19430501*F~

42

OI OTHER INSURANCE COVERAGE INFORMATION

OI***Y*P**Y~

43

2330A OTHER SUBSCRIBER NAME

NM1 OTHER SUBSCRIBER NAME

NM1*IL*1*SMITH*JANE****MI*JS00111223333~

44

N3 OTHER SUBSCIBER ADDRESS

N3*236 N MAIN ST~

45

N4 OTHER SUBSCIBER CITY

N4*MIAMI*FL*33111~

46

2330B OTHER SUBSCRIBER/PAYER

NM1 OTHER PAYER NAME

NM1*PR*2*KEY INSURANCE                                COMPANY*****PI*999996666~

47

2400 SERVICE LINE

LX*1~

48

SV1 PROFESSIONAL SERVICE

SV1*HC:99213*43*UN*1***1:2:3:4~

49

DTP DATE - SERVICE DATE(S)

DTP*472*D8*20051003~

50

2430 LINE ADJUDICATION INFORMATION

SVD*999996666*40*HC:99213**1~

51

CAS LINE ADJUSTMENT

CAS*CO*42*3~

52

DTP LINE ADJUDICATION DATE

DTP*573*D8*20051015~

53

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*2~

54

SV1 PROFESSIONAL SERVICE

SV1*HC:90782*15*UN*1***1:2~

55

DTP DATE - SERVICE DATE(S)

DTP*472*D8*20051003~

56

2430 LINE ADJUDICATION INFORMATION

SVD*999996666*15*HC:90782**1~

57

DTP LINE ADJUDICATION DATE

DTP*573*D8*20051015~

58

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*3~

59

SV1 PROFESSIONAL SERVICE

SSV1*HC:J3301*21.04*UN*1***1:2~

60

DTP DATE - SERVICE DATE(S)

DTP*472*D8*20051003~

61

2430 LINE ADJUDICATION INFORMATION

SVD*999996666*21.04*HC:J3301**1~

62

DTP LINE ADJUDICATION DATE

DTP*573*D8*20051015~

63

TRAILER

SE TRANSACTION SET TRAILER

SE*63*1234~

Complete Data String For Example 3.B:

ST*837*1234*005010X222A2~BHT*0019*00*0123*20051015*1023*CH~N

M1*41*2*PREMIER BILLING SERVICE*****46*12EEER 000TY~PER*IC*J

ERRY*TE*3055552222~NM1*40*2*GREAT PRAIRIES HEALTH*****46*567

890~HL*1**20*1~NM1*85*1*KILDARE*BEN****XX*1999996666~N3*1234

SEAWAY ST~N4*MIAMI*FL*33111~REF*EI*123456789~ PER*IC*CONNIE

*TE*3055551234~NM1*87*2~N3*2345*OCEAN BLVD~N4*MIAMI*FL*3111~

REF*G2*EX7777~HL*2*1*22*1~ SBR*S********CI~NM1*IL*1*SMITH*JA

CK****MI*222334444~DMG*D8*19431022*M~NM1*PR*2*GREAT PRAIRIES

HEALTH*****PI*567890~N3*4456 SOUTH SHORE BLVD~N4*CHICAGO*IL

*44444~REF*G2*567890~HL*3*2*23*0~PAT*19~NM1*QC*1*SMITH*TED~N

3*236 N MAIN ST~N4*MIAMI*FL*33413~DMG*D8*19730501*M~CLM*2640

7789*79.04***11:B:1*Y*A*Y*I~HI*BK:4779*BF:2724*BF:2780*BF:53

081~NM1*82*1*KILDARE*BEN****XX*1999996666~PRV*PE*PXC*204C000

00X~REF*G2*88877~NM1*77*2*KILDARE ASSOCIATES*****XX*15812345

67~N3*2345 OCEAN BLVD~N4*MIAMI*FL*33111~SBR*P*01*******CI~CA

S*PR*1*21.89**2*15~AMT*D*39.15~AMT*EAF*36.89~DMG*D8*19430501

*F~OI***Y*P**Y~NM1*IL*1*SMITH*JANE****MI*JS00111223333~N3*23

6 N MAIN ST~N4*MIAMI*FL*33111~NM1*PR*2*KEY INSURANCE COMPANY

*****PI*999996666~LX*1~SV1*HC:99213*43*UN*1***1:2:3:4~DTP*47

2*D8*20051003~SVD*999996666*40*HC:99213**1~CAS*CO*42*3~DPT*5

73*D8*20051015~LX*2~SV1*HC:90782*15*UN*1***1:2~DTP*472*D8*20

051003~SVD*999996666*15*HC:90782**1~DTP*573*D8*20051015~LX*3

~SV1*HC:J3301*21.04*UN*1***1:2~DTP*472*D8*20051003~SVD*99999

6666*21.04*HC:J3301**1~DPT*573*D8*20051015~SE*63*1234~

3.1.3.3 Example 3.C -- Claim from Payer A to Payer B in Payer-to-Payer

COB Situation. Payer A will pass the claim directly to Payer B without intervention from provider.

If this claim were to go from the Billing Provider to Payer A and then Payer A were to send it claim directly to Payer B, the transaction would look like this as it comes out of Payer A's processing system. In this situation, the Billing Provider must send Payer A all the COB information on Payer B.

SEG #

LOOP SEGMENT/ELEMENT STRING

1

HEADER

ST TRANSACTION SET HEADER

ST*837*0024*005010X222A2~

2

BHT BEGINNING OF HIERARCHICAL TRANSACTION

BHT*0019*00*0123*20051015*1023*CH~

3

1000A SUBMITTER

NM1 SUBMITTER NAME

NM1*41*2*KEY INSURANCE*****46*999996666~

4

PER SUBMITTER EDI CONTACT INFORMATION

PER**IC*JERRY*TE*3055552222~

5

1000B RECEIVER

NM1 RECEIVER NAME

NM1*40*2*GREAT PRARIES*****46*567890~

6

2000A BILLING PROVIDER HL LOOP

HL - BILLING PROVIDER

HL*1**20*1~

7

2010AA BILLING PROVIDER

NM1 BILLING PROVIDER

NM1*85*1*KILDARE*BEN****XX*1999996666~

8

N3 BILLING PROVIDER ADDRESS

N3*1234 SEAWAY ST~

9

N4 BILLING PROVIDER CITY/STATE/ZIP

N4*MIAMI*FL*33111~

10

REF - BILLING PROVIDER TAX ID

REF*EI*123456789~

11

PER BILLING PROVIDER CONTACT INFORMATION

PER*IC*CONNIE*TE*3055551234~

12

2010AB PAY-TO PROVIDER

NM1 PAY-TO PROVIDER NAME

NM1*87*2~

13

N3 PAY-TO PROVIDER ADDRESS

N3*2345 OCEAN BLVD~

14

N4 PAY-TO PROVIDER CITY/STATE/ZIP

N4*MIAMI*FL*33111~

15

2000B SUBSCRIBER HL LOOP

HL SUBSCRIBER

HL*2*1*22*1~

16

SBR SUBSCRIBER INFORMATION

SBR*S*******CI~

17

2010BA SUBSCRIBER

NM1 SUBSCRIBER NAME

NM1*IL*1*SMITH*JACK****MI*222334444~

18

DMG SUBSCRIBER DEMOGRAPHIC INFORMATION

DMG*D8*19431022*M~

19

2010BB PAYER

NM1 PAYER NAME

NM1*PR*2*GREAT PRAIRIES HEALTH*****PI*567890~

20

N3 PAYER ADDRESS

N3*4456 SOUTH SHORE BLVD~

21

N4 PAYER CITY/STATE/ZIP CODE

N4*CHICAGO*IL*44444~

22

REF BILLING PROVIDER SECONDARY IDENTIFICATION

REF*G2*EJ6666~

23

2000C PATIENT HL LOOP

HL - PATIENT

HL*3*2*23*0~

24

PAT PATIENT INFORMATION

PAT*19~

25

2010CA PATIENT

NM1 PATIENT NAME

NM1*QC*1*SMITH*TED~

26

N3 PATIENT ADDRESS

N3*236 N MAIN ST~

27

N4 PATIENT CITY/STATE/ZIP

N4*MIAMI*FL*33413~

28

DMG PATIENT DEMOGRAPHIC INFORMATION

DMG*D8*19730501*M~

29

2300 CLAIM

CLM CLAIM LEVEL INFORMATION

CLM*26407789*79.04***11:B:1*Y*A*Y*I*P~

30

HI HEALTH CARE DIAGNOSIS CODES

HI*BK:4779*BF:2724*BF:2780*BF:53081~

31

2310B RENDERING PROVIDER

NM1 RENDERING PROVIDER NAME

NM1*82*1*KILDARE*BEN****XX*1999996666~

32

PRV RENDERING PROVIDER INFORMATION

PRV*PE*PXC*204C00000X~

33

REF RENDERING PROVIDER SECONDARY IDENTIFICATION

REF*G2*PBS3334~

34

2310D SERVICE FACILITY LOCATION

NM1 SERVICE FACILITY LOCATION

NM1*77*2*KILDARE ASSOCIATES*****XX*1581234567~

35

N3 SERVICE FACILITY ADDRESS

N3*2345 OCEAN BLVD~

36

N4 SERVICE FACILITY CITY/STATE/ZIP

N4*MIAMI*FL*33111~

37

2320 OTHER SUBSCRIBER INFORMATION

SBR OTHER SUBSCRIBER INFORMATION

SBR*P*01*******CI~

38

CAS CLAIM LEVEL ADJUSTMENTS AND AMOUNTS

CAS*PR*1*21.89**2*15~

39

AMT COORDINATION OF BENEFITS - PAYOR PAID AMOUNT

AMT*D*39.15~

40

AMT COORDINATION OF BENEFITS – PATIENT RESPONSBILITY

AMT*EAF*36.89~

41

DMG SUBSCRIBER DEMOGRAPHIC INFORMATION

DMG*D8*19430501*F~

42

OI OTHER INSURANCE COVERAGE INFORMATION

OI***Y*P**Y~

43

2330A OTHER SUBSCRIBER NAME

NM1 OTHER SUBSCRIBER NAME

NM1*IL*1*SMITH*JANE****MI*JS00111223333~

44

N3 OTHER SUBSCIBER ADDRESS

N3*236 N MAIN ST~

45

N4 OTHER SUBSCIBER CITY/STATE/ZIP

N4*MIAMI*FL*33111~

46

2330B OTHER PAYER NAME

NM1 OTHER PAYER NAME

NM1*PR*2*KEY INSURANCE COMPANY*****PI*999996666~

47

2330E OTHER PAYER RENDERING PROVIDER

NM1 OTHER PAYER RENDERING PROVIDER

NM1*82*1~

48

REF OTHER PAYER RENDERING PROVIDER IDENTIFICATION

REF*G2*PBS3334~

49

2400 SERVICE LINE

LX*1~

50

SV1 PROFESSIONAL SERVICE

SV1*HC:99213*43*UN*1***1:2:3:4~

51

DTP DATE - SERVICE DATE(S)

DTP*472*D8*20051003~

52

2430 LINE ADJUDICATION INFORMATION

SVD*999996666*40*HC:99213**1~

53

CAS LINE ADJUSTMENT

CAS*CO*42*3~

54

DTP LINE ADJUDICATION DATE

DTP*573*D8*20051015~

55

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*2~

56

SV1 PROFESSIONAL SERVICE

SV1*HC:90782*15*UN*1***1:2~

57

DTP DATE - SERVICE DATE(S)

DTP*472*D8*20051003~

58

2430 LINE ADJUDICATION INFORMATION

SVD*999996666*15*HC:90782**1~

59

DTP LINE ADJUDICATION DATE

DTP*573*D8*20051015~

60

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*3~

61

SV1 PROFESSIONAL SERVICE

SV1*HC:J3301*21.04*UN*1***1:2~

62

DTP DATE - SERVICE DATE(S)

DTP*472*D8*20051003~

63

2430 LINE ADJUDICATION INFORMATION

SVD*999996666*21.04*HC:J3301**1~

64

DTP LINE ADJUDICATION DATE

DTP*573*D8*20051015~

65

TRAILER

SE TRANSACTION SET TRAILER

SE*65*0024~

Complete Data String For Example 3.C:

ST*837*0024*005010X222A2~BHT*0019*00*0123*20051015*1023*CH~N

M1*41*2*KEY INSURANCE*****46*999996666~PER*IC*JERRY*TE*30555

52222~NM1*40*2*GREAT PRAIRIES*****46*567890~HL*1**20*1~NM1*8

5*1*KILDARE*BEN****XX*1999996666~N3*1234*SEAWAY ST~N4*MIAMI*

FL*33111~REF*EI*123456789~PER*IC*CONNIE*TE*3055551234~NM1*87

*2~N3*2345*OCEAN BLVD~N4*MAIMI*FL*33111~HL*2*1*22*1~SBR*S***

****CI~NM1*IL*1*SmITH*JACK****MI*22233444~DMG*D8*19431022*M~

NM1*PR*2*GREAT PRAIRIES HEALTH*****PI*567890~N3*4456 SOUTH S

HORE BLVD~N4*CHICAGO*IL*44444~REF*G2*EJ6666~HL*3*2*23*0~PAT*

19~NM1*QC*1*SMITH*TED~N3*236 N MAIN ST~N4*MIAMI*FL*33413~DMG

*D8*19730501*M~CLM*26407789*79.04***11:B:1*Y*A*Y*I*P~HI*BK:4

779*BF:2724*BF:2780*BF:53081~NM1*82*1*KILDARE*BEN****XX*1999

996666~PRV*PE*PXC*204C00000X~REF*G2*PBS3334~NM1*77*2*KILDARE

ASSOCIATES*****XX*1581234567~N3*2345 OCEAN BLVD~N4*MIAMI*FL

*33111~SBR*P*01*******CI~CAS*PR*1*21.89**2*15~AMT*D*39.15~AM

T*EAF*36.89~DMG*D8*19430501*F~OI***Y*P**Y~NM1*IL*1*SMITH*JAN

E****MI*JS00111223333~N3*236 N MAIN ST~N4*MIAMI*FL*33111~NM1

*PR*2*KEY INSURANCE COMPANY*****PI*999996666~NM1*82*1~REF*G2

*PBS3334~LX*1~SV1*HC:99213*43*UN*1***1:2:3:4~DPT*472*D8*2005

1003~SVD*999996666*40*HC:99213**1~CAS*CO*42*3~DTP*573*D8*200

51015~LX*2~SV1*HC:90782*15*UN*1***1:2~DTP*472*D8*20051003~SV

D*999996666*15*HC:90782**1~DTP*573*D8*20051015~LX*3~SV1*HC:J

3301*21.04*UN*1***1:2~DTP*472*D8*20051003~SVD*999996666*21.0

4*HC:J3301**1~DTP*573*D8*20051015~SE*65*0024~

3.1.4 Example 4 - Medicare Secondary Payer Example (COB)

Patient and the Subscriber are the same person. The submitter is the provider. The provider previously sent the claim to the primary payer — Commerce. Payment received and the provider submitted the claim to the secondary payer, which is Medicare Part B. The claim was transmitted directly to Medicare by the submitter. Model used is provider to payer.

SUBSCRIBER/PATIENT: Wayne Medyum

ADDRESS: 1010 Thousand Oak Lane, Mayne, PA 17089

SEX: M

DOB: 1/10/1956

HEALTH INSURANCE CLAIM NUMBER: 102200221B1

DESTINATION PAYER: Medicare Part B Pennsylvania

PAYER ADDRESS: 5232 Mayne Avenue, Lyght, PA 17009

RECEIVER: Medicare Part B Pennsylvania

EDI #: 10234

BILLING PROVIDER/SENDER: Specialists

ADDRESS: 5 Map Court, Mayne, PA 17089

EDI # 110101

CONTACT PERSON AND PHONE NUMBER: Sue 8005558888

PATIENT ACCOUNT NUMBER: 101KEN6055

CASE: Lower leg pain

SERVICES: Office Visit – POS=Office

DATE OF SERVICE: 1/19/2005

CHARGE: $120

TOTAL CHARGES: $120

ELECTRONIC ROUTE: Billing provider (submitter) direct to Medicare Part B Pennsylvania

SEG #

LOOP SEGMENT/ELEMENT STRING

1

HEADER

ST TRANSACTION SET HEADER

ST*837*0002*005010X222A2~

2

BHT BEGINNING OF HIERARCHICAL TRANSACTION

BHT*0019*00*000001142*20050214*115101*CH~

3

1000A SUBMITTER

NM1 SUBMITTER

NM1*41*2*SPECIALISTS*****46*1111111~

4

PER SUBMITTER EDI CONTACT INFORMATION

PER*IC*SUE*TE*8005558888~

5

1000B RECEIVER

NM1 RECEIVER NAME

NM1*40*2*MEDICARE                        PENNSYLVANIA*****46*10234~

6

2000A BILLING PROVIDER HL LOOP

HL BILLING PROVIDER

HL*1**20*1~

7

2010AA BILLING PROVIDER

NM1 BILLING PROVIDER NAME

M1*85*2*SPECIALISTS*****XX*0100000090~

8

N3 BILLING PROVIDER ADDRESS

N3*5 MAP COURT~

9

N4 BILLING PROVIDER CITY/STATE/ZIP

N4*MAYNE*PA*17111~

10

REF - BILLING PROVIDER TAX IDENTIFICATION

REF*EI*890123456~

11

REF BILLING PROVIDER SECONDARY ID

REF*G2*110101~

12

2000B SUBSCRIBER HL LOOP

HL*2*1*22*0~

13

SBR SUBSCRIBER INFORMATION

SBR*S*18*MEDICARE*12****MB~

14

2010BA SUBSCRIBER

NM1 SUBSCRIBER NAME

NM1*IL*1*MEDYUM*WAYNE*M***MI*102200221B1~

15

N3 SUBSCRIBER ADDRESS

N3*1010 THOUSAND OAK LANE~

16

N4 SUBSCRIBER CITY/STATE/ZIP

N4*MAYN*PA*17089~

17

DMG SUBSCRIBER DEMOGRAPHIC INFORMATION

DMG*D8*19560110*M~

18

2010BB PAYER

NM1 PAYER NAME

NM1*PR*2*MEDICARE                        PENNSYLVANIA*****PI*10234~

19

N3 PAYER ADDRESS

N3*5232 MAYNE AVENUE~

20

N4 PAYER CITY/STATE/ZIP

N4*LYGHT*PA*17009~

21

2300 CLAIM

CLM CLAIM LEVEL INFORMATION

CLM*101KEN6055*120***11:B:1*Y*A*Y*Y*B~

22

HI HEALTH CARE DIAGNOSIS CODE(S)

HI*BK:71516*BF:71906~

23

2310A REFERRING PROVIDER

NM1*DN*1*BRYHT*LEE*T~

24

REF REFERRING PROVIDER SECONDARY IDENTIFICATION

REF*1G*B01010~

25

2310B RENDERING PROVIDER

NM1*82*1*HENZES*JACK****XX*9090909090~

26

PRV RENDERING PROVIDER INFORMATION

PRV*PE*PXC*207X00000X~

27

REF RENDERING PROVIDER SECONDARY IDENTIFICATION

REF*G2*110102CCC~

28

2320 OTHER SUBSCRIBER INFORMATION

SBR OTHER SUBSCRIBER INFORMATION

SBR*P*01**COMMERCE*****CI~

29

AMT CORRDINATION OF BENEFITS – PAYOR PAID AMOUNT

AMT*D*80~

30

AMT CORRDINATION OF BENEFITS – PATIENT RESPONSBILITY

AMT*F2*15~

31

DMG SUBSCRIBER DEMOGRAPHIC INFORMATION

DMG*D8*19601222*F~

32

OI OTHER INSURANCE COVERAGE INFORMATION

OI***Y*B**Y~

33

2330A OTHER SUBSCRIBER NAME

NM1 OTHER SUBSCRIBER NAME

NM1*IL*1*MEDYUM*CAROL****MI*COM188-404777~

34

N3 OTHER SUBSCIBER ADDRESS

N3*PO BOX 45~

35

N4 OTHER SUBSCIBER CITY/STATE/ZIP CODE

N4*MAYN*PA*17089~

36

2330B OTHER SUBSCRIBER/PAYER

NM1 OTHER PAYER NAME

NM1*PR*2*COMMERCE*****PI*59999~

37

2400 SERVICE LINE

LX*1~

38

SV1 PROFESSIONAL SERVICE

SV1*HC:99203:25*120*UN*1***1:2~

39

DTP DATE - SERVICE DATE

DTP*472*D8*20050119~

40

2420 LINE ADJUDICATION INFORMATION

SVD LINE ADJUDICATION INFORMATION

SVD*59999*80*HC:99203:25**1~

41

CAS LINE ADJUSTMENT

CAS*CO*42*25~

42

CAS LINE ADJUSTMENT

CAS*PR*2*15

43

DTP LINE ADJUDICATION DATE

DTP*573*D8*20050128~

44

TRAILER

SE TRANSACTION SET TRAILER

SE*44*000000002~

Complete Data String:

ST*837*0002*005010X222A2~BHT*0019*00*000001142*20050214*1151

01*CH~NM1*41*2*SPECIALISTS*****46*1111111~PER*IC*SUE*TE*8005

558888~NM1*40*2*MEDICARE PENNSYLVANIA*****46*10234~HL*1**20*

1~NM1*85*2*SPECIALISTS*****XX*0100000009~N3*5 MAP COURT~N4*M

AYNE*PA*21236~ REF*EI*890123456~REF*G2*110101~HL*2*1*22*0~SB

R*S*18**MEDICARE*12****MB~NM1*IL*1*MEDYUM*WAYNE*M***MI*10220

0221B1~N3*1010 THOUSAND OAK LANE~N4*MAYN*PA*17089~DMG*D8*195

60110*M~NM1*PR*2*MEDICARE*****PI*10234~N3*5232 MAYNE~N4*LYGH

T*PA*17009~CLM*101KEN6055*120***11:B:1*Y*A*Y*Y*B~HI*BK:71516

*BF:71906~NM1*DN*1*BRYHT*LEE*T~REF*1G*B01010~NM1*82*1*HENZES

*JACK****XX*9090909090~PRV*PE*PXC*207X00000X~REF*G2*110102XX

X~SBR*P*01**COMMERCE*****CI~AMT*D*80~AMT*F2*15~DMG*D8*196012

22*F~OI***Y*B**Y~NM1*IL*1*MEDYUM*CAROL****MI*COM188-404777~N

3*PO BOX 45~N4*MAYN*PA*17089~NM1*PR*2*COMMERCE*****PI*59999~

LX*1~SV1*HC:99203:25*120*UN*1***1:2~DTP*472*D8*20050119~SVD*

59999*80*HC:99203:25**1~CAS*CO*42*25~CAS*PR*2*15~DTP*573*D8*

20050128~SE*44*0002~

3.1.5 Example 5 - Ambulance

Patient is the same person as the subscriber. The provider type is ambulance. The payer is medicare. The submitter is the same as the provider. The receiver is medicare.

SUBSCRIBER/PATIENT: Sarah Jones

ADDRESS: 1129 Reindeer Road, Carr, CO 80612

TELEPHONE NUMBER: 305-555-1111

SEX: F

DOB: 07/29/1963

SUBSCRIBER ID: 012345678A

DESTINATION PAYER: Medicare Part B

PAYER ADDRESS: P. O. Box 3543, Baltimore, MD. 666013543

RECEIVER: Medicare

EDI #: 123245

BILLING PROVIDER/SENDER: AAA Ambulance Service

ADDRESS: 12202 Airport Way, Broomfield, CO 80221-0021

TIN: 376985369

NPI: 2366554859

CONTACT PERSON AND PHONE NUMBER: Lisa Smith, 303-775-2536

PATIENT ACCOUNT NUMBER: 05-1068

DIAGNOSIS: 8628, E8888, 9592, 8540

SERVICES: A0427 - Ambulance Transport $700.00

A0425 - Mileage $8.20

A0422 - Oxygen $46.00

A0382 - BLS Disposable Supplies $12.30

TOTAL CHARGES: $766.50

MISCELLANEOUS: Two patients were transported.

ELECTRONIC ROUTE: Billing Provider (Sender) to Medicare

SEG #

LOOP SEGMENT/ELEMENT STRING

1

HEADER

ST TRANSACTION SET HEADER

ST*837*000017712*005010X222A2~

2

BHT BEGINNING OF HIERARCHICAL TRANSACTION

BHT*0019*00*000017712*20050208*1112*CH~

3

1000A SUBMITTER

NM1 SUBMITTER NAME

NM1*41*2*AAA AMBULANCE SERVICE*****46*376985369~

4

PER SUBMITTER EDI CONTACT INFORMATION

PER*IC*LISA SMITH*TE*3037752536~

5

1000B RECEIVER

NM1 RECEIVER NAME

NM1*40*2*MEDICARE B*****46*123245~

6

2000A BILLING PROVIDER HL LOOP

HL - BILLING PROVIDER

HL*1**20*1~

7

2010AA BILLING PROVIDER

PRV BILLING PROVIDER SPECIALTY

PRV*BI*PXC*3416L0300X~

8

NM1 BILLING PROVIDER NAME

NM1*85*2*AAA AMBULANCE SERVICE*****XX*2366554859~

9

N3 BILLING PROVIDER ADDRESS

N3*12202 AIRPORT WAY~

10

N4 BILLING PROVIDER LOCATION

N4*BROOMFIELD*CO*800210021~

11

REF - BILLING PROVIDER TAX IDENTIFICATION

REF*EI*376985369~

12

2000B SUBSCRIBER HL LOOP

HL - SUBSCRIBER

HL*2*1*22*0~

13

SBR SUBSCRIBER INFORMATION

SBR*P*18*******MB~

14

2010BA SUBSCRIBER

NM1 SUBSCRIBER NAME

NM1*IL*1*JONES*SARAH*A***MI*012345678A~

15

N3 SUBSCRIBER ADDRESS

N3*1129 REINDEER ROAD~

16

N4 SUBSCRIBER CITY, STATE, ZIP CODE

N4*CARR*CO*80612~

17

DMG SUBSCRIBER DEMOGRAPHIC INFORMATION

DMG*D8*19630729*F~

18

2010BB PAYER

NM1 PAYER NAME

NM1*PR*2*MEDICARE PART B*****PI*123245~

19

N3 PAYER ADDRESS

N3*PO BOX 3543~

20

N4 LOCATION

N4*BALTIMORE*MD*666013543~

21

2300 CLAIM

CLM CLAIM LEVEL INFORMATION

CLM*051068*766.50***41::1*Y*A*Y*Y*P*OA~

22

DTP DATE ACCIDENT

DTP*439*D8*20050208~

23

CR1 AMBULANCE TRANSPORT INFORMATION

CR1*LB*275**A*DH*21****PATIENT IMOBILIZED~

24

CRC AMBULANCE CERTIFICATION

CRC*07*Y*04*06*09~

25

CRC AMBULANCE CERTIFICATION

CRC*07*N*05*07*08~

26

HI - HEALTH CARE DIAGNOSIS

HI*BK:8628*BF:E8888*BF:9592*BF:8540~

27

2310E AMBULANCES PICK-UP LOCATION

NM1 PICK UP LOCATION

NM1*PW*2*~

28

N3 PICK UP ADDRESS

N3*1129 REINDEER ROAD~

29

N4 PICK UP LOCATION

N4*CARR*CO*80612~

30

2310F AMBULANCE DROP-OFF LOCATION

NM1 DROP OFF LOCATION

NM1*45*2~

31

N3 - DROP OFF ADDRESS

N3*10005 BANNOCK ST~

32

N4 - DROP OFF LOCATION

N4*CHEYENNE*WY*82009~

33

2400 SERVICE LINE

LX SERVICE LINE NUMBER

LX*1~

34

SV1 - PROFESSIONAL SERVICE

SV1*HC:A0427:RH*700*UN*1***1:2:3:4**Y~

35

DTP DATE - SERVICE DATE

DTP*472*D8*20050208~

36

QTY - AMBULANCE PATIENT COUNT

QTY*PT*2~

37

REF - LINE ITEM CONTROL NUMBER

REF*6R*1001~

38

NTE - LINE NOTE

NTE*ADD*CARDIAC EMERGENCY~

39

LX SERVICE LINE NUMBER

LX*2~

40

SV1 - PROFESSIONAL SERVICE

SV1*HC:A0425:RH*8.20*UN*21***1:2:3:4**Y~

41

DTP - SERVICE DATE

DTP*472*D8*20050208~

42

QTY - AMBULANCE PATIENT COUNT

QTY*PT*2~

43

REF - LINE CONTROL NUMBER

REF*6R*1002~

44

LX - SERVICE LINE NUMBER

LX*3~

45

SV1 - PROFESSIONAL SERVICE

SV1*HC:A0422:RH*46*UN*1***1:2:3:4**Y~

46

DTP - SERVICE DATE

DTP*472*D8*20050208~

47

REF - LINE CONTROL NUMBER

REF*6R*1003~

48

LX - SERVICE LINE NUMBER

LX*4~

49

SV1 - PROFESSIONAL SERVICE

SV1*HC:A0382:RH*12.30*UN*1***1:2:3:4**Y~

50

DTP - SERVICE DATE

DTP*472*D8*20050208~

51

REF - LINE CONTROL NUMBER

REF*6R*1004~

52

TRAILER

SE TRANSACTION SET TRAILER

SE*52*000017712~

Complete Data String:

ST*837*000017712*005010X222A2~BHT*0019*00*000017712*20050208

*1112*CH~NM1*41*2*AAA AMBULANCE SERVICE*****46*376985369~PER

*IC*LISA SMITH*TE*3037752536~NM1*40*2*MEDICARE B*****46*1232

45~HL*1**20*1~PRV*BI*PXC*3416L0300X~NM1*85*2*AAA AMBULANCE S

ERVICE*****XX*2366554859~N3*12202 AIRPORT WAY~N4*BROOMFIELD*

CO*800210021~REF*EI*376985369~HL*2*1*22*0~SBR*P*18*******MB~

NM1*IL*1*JONES*SARAH*A***MI*012345678A~N3*1129 REINDEER ROAD

~N4*CARR*CO*80612~DMG*D8*19630729*F~NM1*PR*2*MEDICARE PART B

*****PI*123245~N3*PO BOX 3543~N4*BALTIMORE*MD*666013543~CLM*

051068*766.50***41::1*Y*A*Y*Y*P*OA~DTP*439*D8*20050208~CR1*L

B*275**A*DH*21****PATIENT IMOBILIZED~CRC*07*Y*04*06*09~CRC*0

7*N*05*07*08~HI*BK:8628*BF:E8888*BF:9592*BF:8540~NM1*PW*2*~N

3*1129 REINDEER ROAD~N4*CARR*CO*80612~NM1*45*2~N3*10005 BANN

OCK ST~N4*CHEYENNE*WY*82009~LX*1~SV1*HC:A0427:RH*700*UN*1***

1:2:3:4**Y~DTP*472*D8*20050208~QTY*PT*2~REF*6R*1001~NTE*ADD*

CARDIAC EMERGENCY~LX*2~SV1*HC:A0425:RH*8.20*UN*21***1:2:3:4*

*Y~DTP*472*D8*20050208~QTY*PT*2~REF*6R*1002~LX*3~SV1*HC:A042

2:RH*46*UN*1***1:2:3:4**Y~DTP*472*D8*20050208~REF*6R*1003~LX

*4~SV1*HC:A0382:RH*12.30*UN*1***1:2:3:4**Y~DTP*472*D8*200502

08~REF*6R*1004~SE*52*000017712~

3.1.6 Example 6 - Chiropractic Example

Patient is the same person as the Subscriber. Payer is Medicare Part B. The claim is submitter directly to Medicare, the submitter being the provider.

SUBSCRIBER/PATIENT: Matthew J Williamson

ADDRESS: 128 Broadcreek, Baltimore, MD 21234

SEX: M

DOB: 1/10/1925

PAYER ID NUMBER: SSN

SSN: 123456789A

DESTINATION PAYER: Medicare Part B Maryland

PAYER ADDRESS: 1946 Greenspring Drive, Timonium, MD 21093

RECEIVER: Medicare Part B Maryland

EDI #: 12345

BILLING PROVIDER/SENDER: David M Greene, DC

ADDRESS: 1264 Oakwood Ave, Baltimore, MD 21236

EDI#: S01057

CONTACT PERSON AND PHONE NUMBER: Kathi Wilmoth 4105558888

PATIENT ACCOUNT NUMBER: 125WILL

CASE: Acute Back Pain

SERVICES: Chiropractic Manipulative Treatment - POS=Office

DATE OF SERVICE: 2/15/2005

CHARGE: $145.50

Initial Treatment Date: 01/15/20050

Acute Manifestation Date: 01/10/2005

Last X-Ray Date: 01/13/2005

TOTAL CHARGES: $145.50

ELECTRONIC ROUTE: Billing provider (sender) direct to Maryland Medicare Part B

SEG #

LOOP SEGMENT/ELEMENT STRING

1

HEADER

ST TRANSACTION SET HEADER

ST*837*3701*005010X222A2~

2

BHT BEGINNING OF HIERARCHICAL TRANSACTION

BHT*0019*00*007227*20050215*075420*CH~

3

1000A SUBMITTER

NM1 SUBMITTER

NM1*41*2*DAVID GREEN*****46*S01057~

4

PER SUBMITTER EDI CONTACT INFORMATION

PER*IC*KATHY SMITH*TE*4105558888~

5

1000B RECEIVER

NM1 RECEIVER NAME

NM1*40*2*MEDICARE PART B                        MARYLAND*****46*12345~

6

2000A BILLING PROVIDER HL LOOP

HL - BILLING PROVIDER

HL*1**20*1~

7

2010AA BILLING PROVIDER

NM1 BILLING PROVIDER NAME

NM1*85*1*GREENE*DAVID*M***XX*1234567890~

8

N3 BILLING PROVIDER ADDRESS

N3*1264 OAKWOOD AVE~

9

N4 BILLING PROVIDER LOCATION

N4*BALTIMORE*MD*21236~

10

REF BILLING PROVIDER SECONDARY ID

REF*EI*987654321~

11

PER BILLING PROVIDER CONTACT INFORMATION

PER*IC*DR*TE*4105551212~

12

2000B SUBSCRIBER HL LOOP

HL*2*1*22*0~

13

SBR SUBSCRIBER INFORMATION

SBR*P*18*******MB~

14

2010BA SUBSCRIBER

NM1 SUBSCRIBER NAME

NM1*IL*1*WILLIAMSON*MATTHEW*J***MI*123456789A~

15

N3 SUBSCRIBER ADDRESS

N3*128 BROADCREEK~

16

N4 SUBSCRIBER CITY

N4*BALTIMORE*MD*21234~

17

DMG SUBSCRIBER DEMOGRAPHIC INFORMATION

DMG*D8*19250110*M~

18

2010BB SUBSCRIBER / PAYER

NM1 PAYER NAME

NM1*PR*2*MEDICARE PART B                        MARYLAND*****PI*C12345~

19

2300 CLAIM

CLM CLAIM LEVEL INFORMATION

CLM*125WILL*145.5***11>B>1*Y*A*Y*Y~

20

DTP - INITIAL TREATMENT DATE

DTP*454*D8*20050115~

21

DTP - ACUTE MANIFESTATION DATE

DTP*453*D8*20050110~

22

DTP - LAST X-RAY DATE

DTP*455*D8*20050113~

23

CR2 SPINAL MANIPULATION SERVICE INFORMATION

CR2********A**CHRONIC PAIN AND                        DISCOMFORT~

24

HI HEALTH CARE DIAGNOSIS CODE(S)

HI*BK>7215~

25

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*1~

26

SV1 PROFESSIONAL SERVICE

SV1*HC>98940*145.5*UN*1***1~

27

DTP - SERVICE DATE(S)

DTP*472*D8*20050215~

28

LINE ITEM CONTROL NUMBER

REF*6R*01~

29

TRAILER

SE TRANSACTION SET TRAILER

SE*29*3701~

Complete Data String:

ST*837*3701*005010X222A2~BHT*0019*00*007227*20050215*075420*

CH~NM1*41*2*DAVID GREEN*****46*S01057~PER*IC*KATHY SMITH*TE*

4105558888~NM1*40*2*MEDICARE PART B MARYLAND*****46*12345~HL

*1**20*1~NM1*85*1*GREENE*DAVID*M***XX*1234567890~N3*1264 OAK

WOOD AVE~N4*BALTIMORE*MD*21236~REF*EI*987654321~PER*IC*DR*TE

*4105551212~HL*2*1*22*0~SBR*P*18*******MB~NM1*IL*1*WILLIAMSO

N*MATTHEW*J***MI*123456789A~N3*128 BROADCREEK~N4*BALTIMORE*M

D*21234~DMG*D8*19250110*M~NM1*PR*2*MEDICARE PART B MARYLAND*

****PI*C12345~CLM*125WILL*145.5***11>B>1*Y*A*Y*Y~DTP*454*D8*

20050115~DTP*453*D8*20050110~DTP*455*D8*20050113~CR2********

A**CHRONIC PAIN AND DISCOMFORT~HI*BK>7215~LX*1~SV1*HC>98940*

145.5*UN*1***1~DTP*472*D8*20050215~REF*6R*01~SE*31*3701~

3.1.7 Example 7 - Oxygen

Patient is the same person as the Subscriber. Claim is submitted by provider directly and the Payer is Medicare DMERC.

SUBSCRIBER/PATIENT: Terry Smith

ADDRESS: 121 South Street, Richmond, IN 46236

SEX: F

DOB: 01/05/38

HIC#: 111-22-2333A

DESTINATION PAYER: DMERC Carrier

PAYOR ADDRESS: 926 W Angel Rd, Richmond, IN 46236

EDI #: 99999

BILLING PROVIDER/SENDER: Oxygen Supply Company

ADDRESS: 1800 East Ridge Drive, Richmond, IN 46224

TIN: 389999999

EDI #: ABC11111

NPI#: 9992233334

DMERC Provider #: 099999999

CONTACT PERSON AND PHONE NUMBER: Bonnie, 812-555-1111

EMAIL: HELPDESK@OXYGEN.COM

ORDERING PROVIDER: Dr. Larry Wilson

ADDRESS: 1212 North Meridian, Richmond, IN 46223

NPI#: 5555511111

UPIN#: X99999

PHONE NUMBER: 555-444-6666

PATIENT ACCOUNT NUMBER: R03996273 #01

CASE: Chronic Airway Obstruction

SERVICE: DOS=03/21/05 POS=Home

SERVICES: Oxygen concentrator and Portable gaseous O2

CHARGES: Oxygen concentrator = $461.10, Portable gaseous oxygen = $59.14

TOTAL CHARGES: $520.24

SEG #

LOOP SEGMENT/ELEMENT STRING

1

HEADER

ST TRANSACTION SET HEADER

ST*837*0001*005010X222A2~

2

BHT BEGINNING OF HIERARCHICAL TRANSACTION

BHT*0019*00*16*20050326*1036*CH~

3

1000A SUBMITTER

NM1 SUBMITTER

NM1*41*2*OXYGEN SUPPLY COMPANY*****46*ABC11111~

4

PER SUBMITTER EDI CONTACT INFORMATION

PER*IC*BONNIE*TE*8125551111*EM*HELPDESK@OXYGEN.COM~

5

1000B RECEIVER

NM1 RECEIVER NAME

NM1*40*2*DMERC CARRIER*****46*99999~

6

2000A BILLING PROVIDER HL LOOP

HL BILLING PROVIDER

HL*1**20*1~

7

2010AA BILLING PROVIDER

NM1 BILLING PROVIDER NAME

NM1*85*2*OXYGEN SUPPLY COMPANY*****XX*9992233334~

8

N3 BILLING PROVIDER ADDRESS

N3*1800 EAST RIDGE DRIVE~

9

N4 BILLING PROVIDER LOCATION

N4*RICHMOND*IN*46224~

10

REF BILLING PROIVDER TAX IDENTIFIER

REF*EI*389999999~

11

2000B SUBSCRIBER HL LOOP

HL SUBSCRIBER

HL*2*1*22*0~

12

SBR SUBSCRIBER INFORMATION

SBR*P*18*******MB~

13

2010BA SUBSCRIBER

NM1 SUBSCRIBER NAME

NM1*IL*1*SMITH*TERRY****MI*111222333A~

14

N3 SUBSCRIBER ADDRESS

N3*121 SOUTH ST~

15

N4 SUBSCRIBER CITY

N4*RICHMOND*IN*46236~

16

DMG SUBSCRIBER DEMOGRAPHIC INFORMATION

DMG*D8*19380105*F~

17

2010BB SUBSCRIBER / PAYER

NM1 PAYER NAME

NM1*PR*2*DMERC CARRIER*****PI*99999~

18

2300 CLAIM

CLM CLAIM LEVEL INFORMATION

CLM*R03996273 #01*520.24***11:B:1*Y*A*Y*Y~

19

HI HEALTH CARE DIAGNOSIS CODES

HI*BK:496*BF:51881*BF:2859~

20

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*1~

21

SV1 PROFESSIONAL SERVICE

SV1*HC:E1390:RR*461.1*UN*1***1:2~

22

PWK DURABLE MEDICAL EQUIPMENT CERTIFICATE OF MEDICAL NECESSITY INDICATOR

PWK*CT*AD~

23

CR3 DURABLE MEDICAL EQUIPMENT CERTIFICATION

CR3*R*MO*99~

24

DTP SERVICE DATE

DTP*472*RD8*20050321-20050321~

25

DTP CERTIFICATION REVISION/RECERTIFICATION DATE

DTP*607*D8*20050321~

26

DTP BEGIN THERAPY DATE

DTP*463*D8*20040321~

27

DTP LAST CERTIFICATION DATE

DTP*461*D8*20050321~

28

2420E ORDERING PROVIDER

NM1 ORDERING PROVIDER NAME

NM1*DK*1*WILSON*LARRY****XX*5555511111~

29

N3 ORDERING PROVIDER ADDRESS

N3*1212 NORTH MERIDIAN~

30

N4 ORDERING PROVIDER CITY/STATE/ZIP CODE

N4*RICHMOND*IN*46223~

31

REF ORDERING PROVIDER INFORMATION

REF*1G*X99999~

32

PER ORDERING PROVIDER CONTACT INFORMATION

PER*IC*LEE*TE*5554446666~

33

2440 FORM IDENTIFICATION CODE

LQ FORM IDENTIFICATION CODE

LQ*UT*04.03~

34

FRM SUPPORTING DOCUMENTATION

FRM*1A**056~

35

FRM SUPPORTING DOCUMENTATION

FRM*1C**20050228~

36

FRM SUPPORTING DOCUMENTATION

FRM*2**1~

37

FRM SUPPORTING DOCUMENTATION

FRM*3**1~

38

FRM SUPPORTING DOCUMENTATION

FRM*4*Y~

39

FRM SUPPORTING DOCUMENTATION

FRM*5**2~

40

FRM SUPPORTING DOCUMENTATION

FRM*7*Y~

41

FRM SUPPORTING DOCUMENTATION

FRM*8*N~

42

FRM SUPPORTING DOCUMENTATION

FRM*9*Y~

43

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*2~

44

SV1 PROFESSIONAL SERVICE

SV1*HC:E0431:RR*59.14*UN*1***1:2~

45

PWK DURABLE MEDICAL EQUIPMENT CERTIFICATE OF MEDICAL NECESSITY INDICATOR

PWK*CT*AD~

46

DTP SERVICE DATE

DTP*472*RD8*20050321-20050321~

47

CR3 DURABLE MEDICAL EQUIPMENT CERTIFICATION

CR3*R*MO*99~

48

DTP CERTIFICATION REVISION/RECERTIFICATION DATE

DTP*607*D8*20050321~

49

DTP BEGIN THERAPY DATE

DTP*463*D8*20040321~

50

DTP LAST CERTIFICATION DATE

DTP*461*D8*20050321~

51

2420E ORDERING PROVIDER

NM1 ORDERING PROVIDER NAME

NM1*DK*1*WILSON*LARRY****XX*5555511111~

52

N3 ORDERING PROVIDER ADDRESS

N3*1212 NORTH MERIDIAN~

53

N4 ORDERING PROVIDER CITY/STATE/ZIP CODE

N4*RICHMOND*IN*46223~

54

REF ORDERING PROVIDER INFORMATION

REF*1G*X99999~

55

PER ORDERING PROVIDER CONTACT INFORMATION

PER*IC*LEE*TE*5554446666~

56

2440 FORM IDENTIFICATION CODE

LQ FORM IDENTIFICATION CODE

LQ*UT*04.03~

57

FRM SUPPORTING DOCUMENTATION

FRM*1A**056~

58

FRM SUPPORTING DOCUMENTATION

FRM*1C**20050228~

59

FRM SUPPORTING DOCUMENTATION

FRM*2**1~

60

FRM SUPPORTING DOCUMENTATION

FRM*3**1~

61

FRM SUPPORTING DOCUMENTATION

FRM*4*Y~

62

FRM SUPPORTING DOCUMENTATION

FRM*5**2~

63

FRM SUPPORTING DOCUMENTATION

FRM*7*Y~

64

FRM SUPPORTING DOCUMENTATION

FRM*8*N~

65

FRM SUPPORTING DOCUMENTATION

FRM*9*Y~

66

TRAILER

SE TRANSACTION SET TRAILER

SE*66*0001~

Complete Data String:

ST*837*0001*005010X222A2~BHT*0019*00*16*20050326*1036*CH~NM1

*41*2*OXYGEN SUPPLY COMPANY*****46*ABC11111~PER*IC*BONNIE*TE

*8125551111*EM*HELPDESK@OXYGEN.COM~NM1*40*2*DMERC CARRIER***

**46*99999~HL*1**20*1~NM1*85*2*OXYGEN SUPPLY COMPANY*****XX*

9992233334~N3*1800 EAST RIDGE DRIVE~N4*RICHMOND*IN*46224~REF

*EI*389999999~HL*2*1*22*0~SBR*P*18*******MB~NM1*IL*1*SMITH*T

ERRY****MI*111222333A~N3*121 SOUTH ST~N4*RICHMOND*IN*46236~D

MG*D8*19380105*F~NM1*PR*2*DMERC CARRIER*****PI*99999~CLM*R03

996273 #01*520.24***11:B:1*Y*A*Y*Y~HI*BK:496*BF:51881*BF:285

9~LX*1~SV1*HC:E1390:RR*461.1*UN*1***1:2~PWK*CT*AD~CR3*R*MO*9

9~DTP*472*RD8*20050321-20050321~DTP*607*D8*20050321~DTP*463*

D8*20040321~DTP*461*D8*20050301~NM1*DK*1*WILSON*LARRY****XX*

5555511111~N3*1212 NORTH MERIDIAN~N4*RICHMOND*IN*46223~REF*1

G*X99999~PER*IC*LEE*TE*5554446666~LQ*UT*04.03~FRM*1A**056~FR

M*1C**20050228~FRM*2**1~FRM*3**1~FRM*4*Y~FRM*5**2~FRM*7*Y~FR

M*8*N~FRM*9*Y~LX*2~SV1*HC:E0431:RR*59.14*UN*1***1:2~PWK*CT*A

D~CR3*R*MO*99~DTP*472*RD8*20050321-20050321~DTP*607*D8*20050

321~DTP*463*D8*20040321~DTP*461*D8*20050301~NM1*DK*1*WILSON*

LARRY****XX*5555511111~N3*1212 NORTH MERIDIAN~N4*RICHMOND*IN

*46223~REF*1G*X99999~PER*IC*LEE*TE*5554446666~LQ*UT*04.03~FR

M*1A**056~FRM*1C**20050228~FRM*2**1~FRM*3**1~FRM*4*Y~FRM*5**

2~FRM*7*Y~FRM*8*N~FRM*9*Y~SE*66*0001~

3.1.8 Example 8 - Wheelchair

Patient is the same person as the Subscriber. Claim is submitted by provider directly and the Payer is Medicare DMERC.

SUBSCRIBER/PATIENT: James Smith

ADDRESS: 12 Main Street, Frankfort, IN 46209

SEX: M

DOB: 10/23/1920

HIC#: 987-65-4321A

DESTINATION PAYER: DMERC Carrier

PAYOR ADDRESS: 926 W Angel Rd, Richmond, IN 46236

EDI #: 99999

BILLING PROVIDER/SENDER: XYZ Wheelchairs Inc

ADDRESS: 1440 North Street, Lafayette, IN 47904

TIN: 123567989

EDI #: ABC55

NPI#: 7778889999

DMERC Provider #: 0426960001

CONTACT PERSON AND PHONE NUMBER: Jane Doe, 222-555-1111

EMAIL: HELPDESK@WHEELCHAIR.COM

ORDERING PROVIDER: Dr. Randall Wilson

ADDRESS: 1226 West Railroad St, Lafayette, IN 47905

NPI#: 1111155555

UPIN#: M12345

CONTACT PERSON AND PHONE NUMBER: Lee, 765-297-7999

PATIENT ACCOUNT NUMBER: SMI123

CASE: Paralysis & CVA

SERVICE: DOS=03/21/05 POS=Home

SERVICES: Standard wheelchair rental for $75.00

SEG #

LOOP SEGMENT/ELEMENT STRING

1

HEADER

ST TRANSACTION SET HEADER

ST*837*112233*005010X222A2~

2

BHT BEGINNING OF HIERARCHICAL TRANSACTION

BHT*0019*00*16*20050326*1036*CH~

3

1000A SUBMITTER

NM1 SUBMITTER

NM1*41*2*XYZ WHEELCHAIRS INC*****46*ABC55~

4

PER SUBMITTER EDI CONTACT INFORMATION

PER*IC*JANE*TE*2225551111~

5

1000B RECEIVER

NM1 RECEIVER NAME

NM1*40*2*DMERC CARRIER*****46*99999~

6

2000A BILLING PROVIDER HL LOOP

HL - BILLING PROVIDER

HL*1**20*1~

7

2010AA BILLING PROVIDER

NM1 BILLING PROVIDER NAME

NM1*85*2*XYZ WHEELCHAIR INC*****XX*7778889999~

8

N3 BILLING PROVIDER ADDRESS

N3*1440 NORTH STREET~

9

N4 BILLING PROVIDER LOCATION

N4*LAFAYETTE*IN*47904~

10

REF BILLING PROVIDER TAX IDENTIFIER

REF*EI*123567989~

11

REF BILLING PROIVDER SECONDARY IDENTIFIER

REF*G2*0426960001~

12

2000B SUBSCRIBER HL LOOP

HL - SUBSCRIBER

HL*2*1*22*0~

13

SBR SUBSCRIBER INFORMATION

SBR*P*18*******MB~

14

PAT PATIENT INFORMATION

PAT*******01*155~

15

2010BA SUBSCRIBER

NM1 SUBSCRIBER NAME

NM1*IL*1*SMITH*JAMES****MI*987654321A~

16

N3 SUBSCRIBER ADDRESS

N3*12 MAIN ST~

17

N4 SUBSCRIBER CITY

N4*FRANKFORT*IN*46209~

18

DMG SUBSCRIBER DEMOGRAPHIC INFORMATION

DMG*D8*19201023*M~

19

2010BB SUBSCRIBER / PAYER

NM1 PAYER NAME

NM1*PR*2*DMERC CARRIER*****PI*99999~

20

2300 CLAIM

CLM CLAIM LEVEL INFORMATION

CLM*SMI123*75***12:B:1*Y*A*Y*Y~

21

HI HEALTH CARE DIAGNOSIS CODES

HI*BK:436*BF:3449~

22

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*1~

23

SV1 PROFESSIONAL SERVICE

SV1*HC:K0001:RR:KH:BR*75*UN*1***1:2~

24

PWK CLAIM SUPPLEMENTAL INFORMATION

PWK*CT*AD~

25

CR3 DURABLE MEDICAL EQUIPMENT CERTIFICATION

CR3*I*MO*99~

26

DTP SERVICE DATE

DTP*472*RD8*20050321-20050321~

27

DTP BEGIN THERAPY DATE

DTP*463*D8*20040321~

28

DTP LAST CERTIFICATION DATE

DTP*461*D8*20050321~

29

MEA TEST RESULT

MEA*TR*HT*70~

30

2420E ORDERING PROVIDER

NM1 ORDERING PROVIDER NAME

NM1*DK*1*WILSON*RANDALL****XX*1111155555~

31

N3 ORDERING PROVIDER ADDRESS

N3*1226 WEST RAILROAD STREET~

32

N4 ORDERING PROVIDER CITY/STATE/ZIP CODE

N4*LAFAYETTE*IN*47905~

33

REF ORDERING PROVIDER INFORMATION

REF*1G*M12345~

34

PER ORDERING PROVIDER CONTACT INFORMATION

PER*IC*LEE*TE*7659259999~

35

2440 FORM IDENTIFICATION CODE

LQ FORM IDENTIFICATION CODE

LQ*UT*02.03B~

36

FRM SUPPORTING DOCUMENTATION

FRM*1*Y~

37

FRM SUPPORTING DOCUMENTATION

FRM*2*N~

38

FRM SUPPORTING DOCUMENTATION

FRM*3*N~

39

FRM SUPPORTING DOCUMENTATION

FRM*4*N~

40

FRM SUPPORTING DOCUMENTATION

FRM*5**8~

41

FRM SUPPORTING DOCUMENTATION

FRM*8*N~

42

FRM SUPPORTING DOCUMENTATION

FRM*9*Y~

43

TRAILER

SE TRANSACTION SET TRAILER

SE*43*112233~

Complete Data String:

ST*837*112233*005010X222A2~BHT*0019*00*16*20050326*1036*CH~N

M1*41*2*XYZ WHEELCHAIRS INC*****46*ABC55~PER*IC*JANE*TE*2225

551111~NM1*40*2*DMERC CARRIER*****46*99999~HL*1**20*1~NM1*85

*2*XYZ WHEELCHAIR INC*****XX*7778889999~N3*1440 NORTH STREET

~N4*LAFAYETTE*IN*47904~REF*EI*123567989~REF*G2*0426960001~HL

*2*1*22*0~SBR*P*18*******MB~PAT*******01*155~NM1*IL*1*SMITH*

JAMES****MI*987654321A~N3*12 MAIN ST~N4*FRANKFORT*IN*46209~D

MG*D8*19201023*M~NM1*PR*2*DMERC CARRIER*****PI*99999~CLM*SMI

123*75***12:B:1*Y*A*Y*Y~HI*BK:436*BF:3449~LX*1~SV1*HC:K0001:

RR:KH:BR*75*UN*1***1:2~PWK*CT*AD~CR3*I*MO*99~DTP*472*RD8*200

50321-20050321~DTP*463*D8*20040321~DTP*461*D8*20050321~MEA*T

R*HT*70~NM1*DK*1*WILSON*RANDALL****XX*1111155555~N3*1226 WES

T RAILROAD STREET~N4*LAFAYETTE*IN*47905~REF*1G*M12345~PER*IC

*LEE*TE*7659259999~LQ*UT*02.03B~FRM*1*Y~FRM*2*N~FRM*3*N~FRM*

4*N~FRM*5**8~FRM*8*N~FRM*9*Y~SE*43*112233~

3.1.9 Example 9 - Anesthesia

Patient is the same as the subscriber. Payer is Medicare. Encounter is billed directly to Medicare.

SUBSCRIBER/PATIENT: Margaret Jones

ADDRESS: 123 Rainbow Road, Nashville, TN 37232

TELEPHONE: 615-555-1212

SEX: F

DOB: 03/03/1974

EMPLOYER: ACME Inc.

SUBSCRIBER #: 123456789A

SECONDARY COVERAGE

DESTINATION PAYER: ABC Payer

PAYER ADDRESS: P.O. Box 1465, Nashville, TN, 37232

PAYER ORGANIZATION ID: 05440

RECEIVER: ABC Payer

EDI #: 05440

BILLING PROVIDER/SENDER: Provider Medical Group

ADDRESS: 1234 West End Ave, Nashville, TN, 37232

NPI#: 2366554859

TIN: 756473826

EDI #: N305

CONTACT PERSON AND PHONE NUMBER: Nina, 615-555-1212 ext.911

RENDERING PROVIDER: Dr. Jacob E. Townsend/Anesthesiologist

NPI: 5678912345

MEDICARE PROVIDER ID#: 9741234

PLACE OF SERVICE: Provider OP Hospital

PLACE OF SERVICE ADDRESS: 345 Main Drive, Nashville, TN,37232

PLACE OF SERVICE ID#: 43294867

PATIENT ACCOUNT NUMBER: 543211230

CASE: Laser Eye Surgery.

VISIT: DOS=1/12/2005 POS=Outpatient Hospital

SERVICES: Anesthesia for the Laser Eye Surgery

CHARGES: Anesthesia, 61 minutes = $827.00

CONCURRENCY: 2 cases

PHYSICAL STATUS: Normal

PATIENT CONTROL #: 153829140

MEDICAL RECORD ID #: 006653794

TOTAL CHARGES: $827.00

ELECTRONIC ROUTE: Billing Provider (sender) to ABC PAYER direct

SEG #

LOOP SEGMENT/ELEMENT STRING

1

HEADER

ST TRANSACTION SET HEADER

ST*837*0001*005010X222A2~

2

BHT BEGINNING OF HIERARCHICAL

BHT*0019*00*0123*20050117*1023*CH~

3

1000A SUBMITTER

NM1 SUBMITTER

NM1*41*2*PROVIDER MEDICAL                        GROUP*****46*N305~

4

PER SUBMITTER EDI CONTACT INFORMATION

PER*IC*NINA*TE*6155551212*EX*911~

5

1000B RECEIVER

NM1 RECEIVER NAME

NM1*40*2*ABC PAYER*****46*05440~

6

2000A BILLING PROVIDER HL LOOP

HL - BILLING PROVIDER

HL*1**20*1~

7

2010AA BILLING PROVIDER

NM1 BILLING PROVIDER NAME

NM1*85*2*PROVIDER MEDICAL                        GROUP*****XX*2366554859~

8

N3 BILLING PROVIDER ADDRESS

N3*1234 WEST END AVE~

9

N4 BILLING PROVIDER CITY/STATE/ZIP

N4*NASHVILLE*TN*37232~

10

REF BILLING PROVIDER TAX IDENTIFICATION

REF*EI*756473826~

11

2000B SUBSCRIBER HL LOOP

HL - SUBSCRIBER

HL*2*1*22*0~

12

SBR SUBSCRIBER INFORMATION

SBR*P*18*******MB~

13

2010BA SUBSCRIBER

NM1 SUBSCRIBER NAME

NM1*IL*1*JONES*MARGARET****MI*123456789A~

14

N3 SUBSCRIBER STREET ADDRESS

N3*123 RAINBOW ROAD~

15

N4 SUBSCRIBER CITY/STATE/ZIP

N4*NASHVILLE*TN*37232~

16

DMG SUBSCRIBER DEMOGRAPHIC INFORMATION

DMG*D8*19740303*F~

17

2010BB SUBSCRIBER / PAYER

NM1 PAYER NAME

NM1*PR*2*ABC PAYER*****PI*05440~

18

2300 CLAIM

CLM CLAIM LEVEL INFORMATION

CLM*153829140*827***22>B>1*Y*A*Y*Y~

19

HI HEALTH CARE DIAGNOSIS CODES

HI*BK>36616~

20

2310B RENDERING PROVIDER

NM1 RENDERING PROVIDER NAME

NM1*82*1*TOWNSEND*JACOB*E***XX*5678912345~

21

PRV RENDERING PROVIDER TAXONOMY INFORMATION

PRV*PE*ZZ*207L00000X~

22

REF RENDERING PROVIDER SECONDARY IDENTIFICATION

REF*G2*9741234~

23

2310C SERVICE FACILITY LOCATION

NM1 SERVICE FACILITY LOCATION

NM1*77*2*PROVIDER OP                        HOSP*****XX*432198765~

24

N3 SERVICE FACILITY LOCATION

N3*345 MAIN DRIVE~

25

N4 SERVICE FACILITY LOCATION CITY/STATE/ZIP

N4*NASHVILLE*TN*37232~

26

2400 SERVICE LINE

LX SERVICE LINE COUNT

LX*1~

27

SV1 PROFESSIONAL SERVICE

SV1*HC>00142>QK>QS>P1*827*MJ*61***1~

28

DTP DATE - SERVICE DATE

DTP*472*D8*20050112~

29

TRAILER

SE TRANSACTION SET TRAILER

SE*29*0001~

Complete Data String:

ST*837*0001*005010X222A2~BHT*0019*00*0123*20050117*1023*CH~N

M1*41*2*PROVIDER MEDICAL GROUP*****46*N305~PER*IC*NINA*TE*61

55551212*EX*911~NM1*40*2*ABC PAYER*****46*05440~HL*1**20*1~N

M1*85*2*PROVIDER MEDICAL GROUP*****XX*2366554859~N3*1234 WES

T END AVE~N4*NASHVILLE*TN*37232~REF*EI*756473826~HL*2*1*22*0

~SBR*P*18*******MB~NM1*IL*1*JONES*MARGARET****MI*123456789A~

N3*123 RAINBOW ROAD~N4*NASHVILLE*TN*37232~DMG*D8*19740303*F~

NM1*PR*2*ABC PAYER*****PI*05440~CLM*153829140*827***22>B>1*Y

*A*Y*Y~HI*BK>36616~NM1*82*1*TOWNSEND*JACOB*E***XX*5678912345

~PRV*PE*ZZ*207L00000X~REF*1G*A41234~NM1*77*2*PROVIDER OP HOS

P*****XX*432198765~N3*345 MAIN DRIVE~N4*NASHVILLE*TN*37232~L

X*1~SV1*HC>00142>QK>QS>P1*827*MJ*61***1~DTP*472*D8*20050112~

SE*29*0001~

3.1.10 Example 10 - Drug examples

The examples in this section have been created with a mixture of uppercase and lowercase letters. This demonstrates that this is an acceptable representation.

3.1.10.1 Drug Example 1 - Drug administered in the Physician Office

Example of service in a physician office, which includes the billing for a drug administered in the office.

SUBSCRIBER/PATIENT: Steve R. Vaughn

ADDRESS: 236 Diamond St., Las Vegas, NV 89109

SEX: M

DOB: 5/1/1943

SUBSCRIBER IDENTIFICATION #: MBRID12345

GROUP #: GRP01020102

DESTINATION RECEIVER: XYZ Receiver

ETIN: 369852758

DESTINATION PAYER: R&R Health Plan

NATIONAL PLAN IDENTIFIER: PLANID12345

BILLING PROVIDER/SENDER: Associates in Medicine

ADDRESS: 1313 Las Vegas Blvd., Las Vegas, NV 89109

TIN: 587654321

NATIONAL PROVIDER IDENTIFIER: 1234567893

CONTACT PERSON AND PHONE NUMBER: Bud Holly, (801)726-8899

PAY-TO PROVIDER: Associates in Medicine

RENDERING PROVIDER: Jim Hendrix

NATIONAL PROVIDER IDENTIFIER: 1122333341

TAXONOMY IDENTIFIER: 208D00000X

PATIENT ACCOUNT NUMBER: CLMNO12345

DIAGNOSIS: 0359.1

CASE: The service provided on 7/11/2004 is that the patient received an injection of immune globulin during an office visit. The service is billed with procedure code 90782.

Coding for the drug is accomplished with a HCPCS procedure code of J1550 (injection, gammablobulin, intramuscular, 10 cc). And, the drug is also coded with NDC of 00026-0635-12 (BayGam® SDV, PF 10 ML).

Place of service is an office. Total billed charges are $103.37. Sales tax is $3.37.

The primary purpose of this example is to demonstrate how drugs are billed along with services when provided by a physician office. Billing for the drug is found in segments #25-30 below.

SEG #

LOOP SEGMENT/ELEMENT STRING

1

HEADER

ST TRANSACTION SET HEADER

ST*837*0711*005010X222A2~

2

BHT BEGINNING OF HIERARCHICAL TRANSACTION

BHT*0019*00*0013*20040801*1200*CH~

3

1000A SUBMITTER

NM1 SUBMITTER

NM1*41*2*Associates in                        Medicine*****46*587654321~

4

PER SUBMITTER EDI CONTACT INFORMATION

PER*IC*Bud Holly*TE*8017268899~

5

1000B RECEIVER

NM1 RECEIVER NAME

NM1*40*2*XYZ Receiver*****46*369852758~

6

2000A BILLING PROVIDER HL LOOP

HL - BILLING PROVIDER

HL*1**20*1~

7

2010AA BILLING PROVIDER

NM1 BILLING PROVIDER NAME

NM1*85*2*Associates in                        Medicine*****XX*587654321~

8

N3 BILLING PROVIDER ADDRESS

N3*1313 Las Vegas Boulevard~

9

N4 BILLING PROVIDER CITY/STATE/ZIP

N4*Las Vegas*NV*89109~

10

REF BILLING PROVIDER SECONDARY IDENTIFICATION

REF*EI*587654321~

11

2000B SUBSCRIBER HL LOOP

HL - SUBSCRIBER

HL*2*1*22*0~

12

SBR SUBSCRIBER INFORMATION

SBR*P*18*GRP01020102******CI~

13

2010BA SUBSCRIBER

NM1 SUBSCRIBER NAME

NM1*IL*1*Vaughn*Steve*R***MI*MBRID12345~

14

N3 SUBSCRIBER ADDRESS

N3*236 Diamond ST~

15

N4 SUBSCRIBER CITY

N4*Las Vegas*NV*89109~

16

DMG SUBSCRIBER DEMOGRAPHIC INFORMATION

DMG*D8*19430501*M~

17

2010BB SUBSCRIBER / PAYER

NM1 PAYER NAME

NM1*PR*2*R&R Health                            Plan*****XY*PLANID12345~

18

2300 CLAIM

CLM CLAIM LEVEL INFORMATION

CLM*CLMNO12345*103.37***11:B:1*Y*A*Y*Y~

19

HI HEALTH CARE DIAGNOSIS CODE

HI*BK:03591~

20

2310B RENDERING PROVIDER

NM1 RENDERING PROVIDER NAME

NM1*82*1*Hendrix*Jim****XX*1122333341~

21

PRV RENDERING PROVIDER INFORMATION

PRV*PE*PXC*208D00000X~

22

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*1~

23

SV1 PROFESSIONAL SERVICE

SV1*HC:90782*50*UN*1*11**1~

24

DTP DATE - SERVICE DATE(S)

DTP*472*D8*20040711~

25

2400 SERVICE LINE

LX*2~

26

SV1 PROFESSIONAL SERVICE

SV1*HC:J1550*53.37*UN*1*11**1~

27

DTP DATE - SERVICE DATE(S)

DTP*472*D8*20040711~

28

AMT SALE TAX AMOUNT

AMT*T*3.37~

29

2410 DRUG IDENTIFICATION

LIN DRUG IDENTIFICATION

LIN**N4*00026063512~

30

CTP DRUG QUANTITY

CTP****10*ML~

31

TRAILER

SE TRANSACTION SET TRAILER

SE*31*0711~

Complete Data String:

ST*837*0711*005010X222A2~BHT*0019*00*0013*20040801*1200*CH~N

M1*41*2*Associates in Medicine*****46*587654321~PER*IC*Bud H

olly*TE*8017268899~NM1*40*2*XYZ Receiver*****46*369852758~HL

*1**20*1~NM1*85*2*Associates in Medicine*****XX*1234567893~N

3*1313 Las Vegas Boulevard~N4*Las Vegas*NV*89109~REF*EI*5876

54321~HL*2*1*22*0~SBR*P*18*GRP01020102******CI~NM1*IL*1*Vaug

hn*Steve*R***MI*MBRID12345~N3*236 Diamond ST~N4*Las Vegas*NV

*89109~DMG*D8*19430501*M~NM1*PR*2*R&R Health Plan*****XY*PLA

NID12345~CLM*CLMNO12345*103.37***11:B:1*Y*A*Y*Y~HI*BK:03591~

NM1*82*1*Hendrix*Jim****XX*1122333341~PRV*PE*PXC*208D00000X~

LX*1~SV1*HC:90782*50*UN*1*11**1~DTP*472*D8*20040711~LX*2~SV1

*HC:J1550*53.37*UN*1*11**1~DTP*472*D8*20040711~AMT*T*3.37~LI

N**N4*00026063512~CTP****10*ML~SE*31*0711~

3.1.10.2 Drug Example 2 - Home Infusion Therapy Pharmacy (Adjudicated with NDC in Loop 2410)

Example of services from a home infusion therapy pharmacy, which includes the billing for the drugs delivered for administration in the home and where adjudication will be from NDC number provided in Loop 2410.

SUBSCRIBER/PATIENT: Steve A. Smith

ADDRESS: 15210 Juliet Lane, Libertyville, IL 60048

SEX: M

DOB: 5/1/1943

SUBSCRIBER IDENTIFICATION #: MBRID12345

GROUP #: GRP01020102

DESTINATION RECEIVER: XYZ Receiver

ETIN: 369852758

DESTINATION PAYER: R&R Health Plan

NATIONAL PLAN IDENTIFIER: PLANID1234

SUBMITTER: Quality Billing Service Corporation

ETIN: 587654321

CONTACT PERSON AND PHONE NUMBER: Bud Holly, (801)726-8899

BILLING PROVIDER/SENDER: Professional Home IV, LLC

ADDRESS: 1500 Industrial Drive, Libertyville, IL 60048

TIN: 10-1234567

NATIONAL PROVIDER IDENTIFIER: 1234567893

CONTACT PERSON AND PHONE NUMBER: Brenda Holly, (801)999-9999

PAY-TO PROVIDER: Professional Home IV, LLC

ORDERING PROVIDER: Marcus Welby

NATIONAL PROVIDER IDENTIFIER: 1112223338

PATIENT ACCOUNT NUMBER: CLMNO12345

DIAGNOSIS: 465.9

CASE: The service is provided over a date span from 2/1/2004 to 2/7/2004 for prescriptions that the physician prescribed on 1/30/2004.

Provided is ceftriaxone, 2 gm IV, q24h over 7 days for gravity infusion through PICC line to treat an acute upper respiratory infection. 20mls sterile water is the diluent for reconstitution of the ceftriaxone which is compounded into 100ml saline IV mini-bags. Also provided are all administration supplies and the pole necessary for the ceftriaxone infusion. Additionally, provided are all administration supplies, and flushing solutions (sodium chloride and heparin) prepackaged by the manufacturer in pre-filled syringes.

Drug service lines in this example begin after submission of a daily per diem charge of $200 per day of therapy, coded with HCPCS S9500 in the LX*1 service line. Drugs are precisely coded with NDC numbers, and the HCPCS provided are S5000 and S5001 for a generic drug and brand drug, respectively. The quantity and unit of measure sent for each pair of NDC and HCPCS is the same, and the practice used for infusion therapy claims is to provide a count of containers used, e.g. number of vials, number of bags, etc.

The health plan adjudicates the drug claim using the NDC in the 2410 LIN segment, quantity and unit of measure in the 2410 CTP segment, and charges in the 2400 SV1 segment. For example, in the LX*2 service line, 7 units of ceftriaxone (NDC of 00004-1965-01 which is for Rocephin®) is billed by the provider for total charge amount of $682.50. We note that as 00004-1965-01 Rocephin comes in a physical container of 2gm vials, this means that the provider's charge per vial of Rocephin is $97.50.

As S5000 and S5001 are used to map claim translation directly to the NDC coding for adjudication, payers should not reject occurrences of S5000 or S5001 because of overlapping dates.

Service lines LX*2, LX*3 and LX*4 contain the drugs that are elements of the compound. Service lines LX*5 and LX*6 are for non-compounded prescription drugs.

The primary purpose of this example is to demonstrate how drugs are billed along with services when provided by a home infusion therapy pharmacy. Billing for the drugs is found in segments #25-64 below.

SEG #

LOOP SEGMENT/ELEMENT STRING

1

HEADER

ST TRANSACTION SET HEADER

ST*837*0711*005010X222A2~

2

BHT BEGINNING OF HIERARCHICAL TRANSACTION

BHT*0019*00*0013*20040301*1200*CH~

3

1000A SUBMITTER

NM1 SUBMITTER

NM1*41*2*Quality Billing Service Corporation*****46*587654321~

4

PER SUBMITTER EDI CONTACT INFORMATION

PER*IC*Bud Holly*TE*8017268899~

5

1000B RECEIVER

NM1 RECEIVER NAME

NM1*40*2*XYZ Receiver*****46*369852758~

6

2000A BILLING PROVIDER HL LOOP

HL - BILLING PROVIDER

HL*1**20*1~

7

2010AA BILLING PROVIDER

NM1 BILLING PROVIDER NAME

NM1*85*2*Professional Home IV, LLC*****XX*1234567893~

8

N3 BILLING PROVIDER ADDRESS

N3*1500 Industrial Drive~

9

N4 BILLING PROVIDER CITY

N4*Libertyville*IL*60048~

10

REF BILLING PROVIDER SECONDARY IDENTIFICATION

REF*EI*10-1234567~

11

PER BILLING PROVIDER CONTACT INFORMATION

PER*IC*Brenda Holly*TE*8019999999~

12

2000B SUBSCRIBER HL LOOP

HL - SUBSCRIBER

HL*2*1*22*0~

13

SBR SUBSCRIBER INFORMATION

SBR*P*18*GRP01020102******CI~

14

2010BA SUBSCRIBER

NM1*IL*1*Smith*Steve*A***MI*MBRID01234~

15

N3 SUBSCRIBER ADDRESS

N3*15210 Juliet Lane~

16

N4 SUBSCRIBER CITY

N4*Libertyville*IL*60048~

17

DMG SUBSCRIBER DEMOGRAPHIC INFORMATION

DMG*D8*19430501*M~

18

2010BB SUBSCRIBER / PAYER

NM1 PAYER NAME

NM1*PR*2*R&R Health Plan*****XY*PLANID12345~

19

2300 CLAIM

CLM CLAIM LEVEL INFORMATION

CLM*CLMNO12345*2232.93***12:B:1*Y*A*Y*Y~

20

HI HEALTH CARE DIAGNOSIS CODE

HI*BK:4659~

21

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*1~

22

SV1 PROFESSIONAL SERVICE

SV1*HC:S9500*1400.00*UN*7*12**1~

23

DTP DATE - SERVICE DATE(S)

DTP*472*RD8*20040201-20040207~

24

2420E ORDERING PROVIDER NAME

NM1 ORDERING PROVIDER NAME

NM1*DK*1*Welby*Marcus****XX*1112223338~

25

2400 SERVICE LINE

LX*2~

26

SV1 PROFESSIONAL SERVICE

SV1*HC:S5001*682.50*UN*7*12**1~

27

DTP DATE - SERVICE DATE(S)

DTP*472*RD8*20040201-20040207~

28

DTP DATE – PRESCRIPTION DATE

DTP*471*D8*20040130~

29

2410 DRUG IDENTIFICATION

LIN DRUG IDENTIFICATION

LIN**N4*00004196501~

30

CTP DRUG QUANTITY

CTP****7*UN~

31

REF PRESCRIPTION NUMBER

REF*XZ*2530001~

32

2420E ORDERING PROVIDER NAME

NM1 ORDERING PROVIDER NAME

NM1*DK*1*Welby*Marcus****XX*1112223338~

33

2400 SERVICE LINE COUNTER

LX*3~

34

SV1 PROFESSIONAL SERVICE

SV1*HC:S5000*15.12*UN*14*12**1~

35

DTP DATE - SERVICE DATE(S)

DTP*472*RD8*20040201-20040207~

36

DTP DATE – PRESCRIPTION DATE

DTP*471*D8*20040130~

37

2410 DRUG IDENTIFICATION

LIN DRUG IDENTIFICATION

LIN**N4*63323024910~

38

CTP DRUG QUANTITY

CTP****14*UN~

39

REF PRESCRIPTION NUMBER

REF*XZ*2530001~

40

2420E ORDERING PROVIDER NAME

NM1 ORDERING PROVIDER NAME

NM1*DK*1*Welby*Marcus****XX*1112223338~

41

2400 SERVICE LINE COUNTER

LX*4~

42

SV1 PROFESSIONAL SERVICE

SV1*HC:S5000*67.69*UN*7*12**1~

43

DTP DATE - SERVICE DATE(S)

DTP*472*RD8*20040201-20040207~

44

DTP DATE – PRESCRIPTION DATE

DTP*471*D8*20040130~

45

2410 DRUG IDENTIFICATION

LIN DRUG IDENTIFICATION

LIN**N4*00338004938~

46

CTP DRUG QUANTITY

CTP****7*UN~

47

REF PRESCRIPTION NUMBER

REF*XZ*2530001~

48

2420E ORDERING PROVIDER NAME

NM1 ORDERING PROVIDER NAME

NM1*DK*1*Welby*Marcus****XX*1112223338~

49

2400 SERVICE LINE COUNTER

LX*5~

50

SV1 PROFESSIONAL SERVICE

SV1*HC:S5000*57.12*UN*14*12**1~

51

DTP DATE - SERVICE DATE(S)

DTP*472*RD8*20040201-20040207~

52

DTP DATE – PRESCRIPTION DATE

DTP*471*D8*20040130~

53

2410 DRUG IDENTIFICATION

LIN DRUG IDENTIFICATION

LIN**N4*08290033010~

54

CTP DRUG QUANTITY

CTP****14*UN~

55

REF PRESCRIPTION NUMBER

REF*XZ*2530002~

56

2420E ORDERING PROVIDER NAME

NM1 ORDERING PROVIDER NAME

NM1*DK*1*Welby*Marcus****XX*1112223338~

57

2400 SERVICE LINE COUNTER

LX*6~

58

SV1 PROFESSIONAL SERVICE

SV1*HC:S5000*10.50*UN*7*12**1~

59

DTP DATE - SERVICE DATE(S)

DTP*472*RD8*20040201-20040207~

60

DTP DATE – PRESCRIPTION DATE

DTP*471*D8*20040130~

61

2410 DRUG IDENTIFICATION

LIN DRUG IDENTIFICATION

LIN**N4*08290038005~

62

CTP DRUG QUANTITY

CTP****7*UN~

63

REF PRESCRIPTION NUMBER

REF*XZ*2530003~

64

2420E ORDERING PROVIDER NAME

NM1 ORDERING PROVIDER NAME

NM1*DK*1*Welby*Marcus****XX*1112223338~

65

TRAILER

SE TRANSACTION SET TRAILER

SE*65*0711~

Complete Data String:

ST*837*0711*005010X222A2~BHT*0019*00*0013*20040301*1200*CH~N

M1*41*2*Quality Billing Service Corporation*****46*587654321

~PER*IC*Bud Holly*TE*8017268899~NM1*40*2*XYZ Receiver*****46

*369852758~HL*1**20*1~NM1*85*2*Professional Home IV, LLC****

*XX*1234567893~N3*1500 Industrial Drive~N4*Libertyville*IL*6

0048~REF*EI*10-1234567~PER*IC*Brenda Holly*TE*8019999999~HL*

2*1*22*0~SBR*P*18*GRP01020102******CI~NM1*IL*1*Smith*Steve*A

***MI*MBRID01234~N3*15210 Juliet Lane~N4*Libertyville*IL*600

48~DMG*D8*19430501*M~NM1*PR*2*R&R Health Plan*****XY*PLANID1

2345~CLM*CLMNO12345*2232.93***12:B:1*Y*A*Y*Y~HI*BK:4659~LX*1

~SV1*HC:S9500*1400.00*UN*7*12**1~DTP*472*RD8*20040201-200402

07~NM1*DK*1*Welby*Marcus****XX*1112223338~LX*2~SV1*HC:S5001*

682.50*UN*7*12**1~DTP*472*RD8*20040201-20040207~DTP*471*D8*2

0040130~LIN**N4*00004196501~CTP****7*UN~REF*XZ*2530001~NM1*D

K*1*Welby*Marcus****XX*1112223338~LX*3~SV1*HC:S5000*15.12*UN

*14*12**1~DTP*472*RD8*20040201-20040207~DTP*471*D8*20040130~

LIN**N4*63323024910~CTP****14*UN~REF*XZ*2530001~NM1*DK*1*Wel

by*Marcus****XX*1112223338~LX*4~SV1*HC:S5000*67.69*UN*7*12**

1~DTP*472*RD8*20040201-20040207~DTP*471*D8*20040130~LIN**N4*

00338004938~CTP****7*UN~REF*XZ*2530001~NM1*DK*1*Welby*Marcus

2*RD8*20040201-20040207~DTP*471*D8*20040130~LIN**N4*08290033

010~CTP****14*UN~REF*XZ*2530002~NM1*DK*1*Welby*Marcus****XX*

1112223338~LX*6~SV1*HC:S5000*10.50*UN*7*12**1~DTP*472*RD8*20

040201-20040207~DTP*471*D8*20040130~LIN**N4*08290038005~CTP*

***7*UN~REF*XZ*2530003~NM1*DK*1*Welby*Marcus****XX*111222333

8~SE*65*0711~

3.1.10.3 Drug Example 3 - Home Infusion Therapy Pharmacy (Adjudicated with HCPCS in Loop 2400 or NDC in Loop 2410)

Example of services from a home infusion therapy pharmacy, which includes the billing for the drugs delivered for administration in the home and where adjudication may be from either HCPCS code found in SV1 or NDC number provided in Loop 2410.

SUBSCRIBER/PATIENT: Steve A. Smith

ADDRESS: 15210 Juliet Lane, Libertyville, IL 60048

SEX: M

DOB: 5/1/1943

SUBSCRIBER IDENTIFICATION #: MBRID12345

GROUP #: GRP01020102

DESTINATION RECEIVER: XYZ Receiver

ETIN: 369852758

DESTINATION PAYER: R&R Health Plan

NATIONAL PLAN IDENTIFIER: PLANID12345

SUBMITTER: Quality Billing Service Corporation

ETIN: 587654321

CONTACT PERSON AND PHONE NUMBER: Bud Holly, (801) 726-8899

BILLING PROVIDER/SENDER: Professional Home IV, LLC

ADDRESS: 1500 Industrial Drive, Libertyville, IL 60048

TIN: 10-1234567

NATIONAL PROVIDER IDENTIFIER: 1234567893

CONTACT PERSON AND PHONE NUMBER: Brenda Holly, (801) 999-9999

PAY-TO PROVIDER: Professional Home IV, LLC

ORDERING PROVIDER: Marcus Welby

NATIONAL PROVIDER IDENTIFIER: 1112223338

PATIENT ACCOUNT NUMBER: CLM012345

DIAGNOSIS: 465.9

CASE: The service is provided over a date span from 2/1/2004 to 2/7/2004 for prescriptions that the physician prescribed on 1/30/2004.

Provided is ceftriaxone, 2 gm IV, q24h over 7 days for gravity infusion through PICC line to treat an acute upper respiratory infection. 20mls sterile water is the diluent for reconstitution of the ceftriaxone which is compounded into 100ml saline IV mini-bags. Also provided are all administration supplies and the pole necessary for the ceftriaxone infusion. Additionally, provided are all administration supplies, and flushing solutions (sodium chloride and heparin) prepackaged by the manufacturer in pre-filled syringes.

Drug service lines in this example begin after submission of a daily per diem charge of $200 per day of therapy, coded with HCPCS S9500 in the LX*1 service line.

The drugs are coded with HCPCS j-codes and with NDC numbers. The quantity of units for each pair of HCPCS j-code and NDC is not always the same. In HCPCS drug coding, the billed units of measure is described in the specific code description. For NDC coding in home infusion therapy claims, the billed units equal the containers used, e.g. number of vials, number of bags, etc.:

  • If the health plan is to adjudicate the drug claim using the provided HCPCS drug code (such as J0696 in LX*2), the plan obtains the charges, unit of measure and quantity billed for the HCPCS drug code from the SV1 segment. While the provider has sent the information of loop 2410, the plan may or may not use it for other purposes.

  • However, if the health plan adjudicates the drug claim using loop 2410 information, this means the plan uses charges submitted in SV102 while quantity and unit of measure are obtained from CTP04 and CTP05. While the unit of measure and quantity in SV103 and SV104 are to reflect the units appropriate for the HCPCS drug code description, the plan is not using them for adjudication.

  • For example, in the LX*2 service line, 56 HCPCS units of ceftriaxone (HCPCS code of J0696) is billed by the provider for total charge amount of $682.50. Equivalently, the provider is billing 7 units of ceftriaxone (NDC number 00004-1965-01 for Rocephin®). As 00004-1965-01 Rocephin comes in a physical container of 2gm vials, this means that the provider's charge per vial of Rocephin is $97.50. As the HCPCS description for J0696 is "injection, ceftriaxone sodium, per 250 mg", 8 units if J0696 is equivalent to 1 unit of 00004-1965-01 ceftriaxone 2gm vial.

  • As another example, in LX*3 we state much more briefly that billed are 14 vials of sterile water, NDC 63323-0249-10. As each vial contains 10mls of sterile water, 28 units of HCPCS J7051 are billed since the HCPCS description is "sterile saline or water, up to 5 cc". Note: If there had existed a HCPCS drug code for 10mls of sterile water, say code JXXXX for "sterile water, 10 cc", then the solution for LX*3 in the complete example that follows would have instead been:

    LX*3~
    SV1*HC:JXXXX*15.12*UN*14*12**1~
    DTP*472*RD8*20040201-20040207~
    DTP*471*D8*20040130~
    LIN**N4*63323024910~
    CTP****14*UN~
    REF*XZ*2530001~
    NM1*DK*1*Welby*Marcus****XX*1112223338~
  • For certain service lines, the HCPCS code submitted is J3490 "unclassified drugs" because there is a lack of clarity as to which of multiple available HCPCS j-codes are to be selected from. As therefore there are multiple occurrences of J3490, payers should not reject occurrences of J3490 because of overlapping dates.

  • When J3490 is used (see service lines LX*4, LX*5, and LX*6), specification of amount charged, quantity billed, unit of measure, NDC number and prescription number is similar to the solution provided in the previous example where HCPCS S5000 and S5001 were used in service lines LX*2 through LX*6.

  • Service lines LX*2, LX*3 and LX*4 contain the prescription drugs that are elements of the compound. Service lines LX*5 and LX*6 are for non-compounded prescription drugs.

Service lines LX*2, LX*3 and LX*4 contain the drugs that are elements of the compound. Service lines LX*5 and LX*6 are for non-compounded prescription drugs.

The primary purpose of this example is to demonstrate how drugs are billed along with services when provided by a home infusion therapy pharmacy. Billing for the drugs is found in segments #25-64 below.

SEG #

LOOP SEGMENT/ELEMENT STRING

1

HEADER

ST TRANSACTION SET HEADER

ST*837*0711*005010X222A2~

2

BHT BEGINNING OF HIERARCHICAL TRANSACTION

BHT*0019*00*0013*20040301*1200*CH~

3

1000A SUBMITTER

NM1 SUBMITTER

NM1*41*2*Quality Billing Service Corporation*****46*587654321~

4

PER SUBMITTER EDI CONTACT INFORMATION

PER*IC*Bud Holly*TE*8017268899~

5

1000B RECEIVER

NM1 RECEIVER NAME

NM1*40*2*XYZ Receiver*****46*369852758~

6

2000A BILLING PROVIDER HL LOOP

HL - BILLING PROVIDER

HL*1**20*1~

7

2010AA BILLING PROVIDER

NM1 BILLING PROVIDER NAME

NM1*85*2*Professional Home IV, LLC*****XX*1234567893~

8

N3 BILLING PROVIDER ADDRESS

N3*1500 Industrial Drive~

9

N4 BILLING PROVIDER CITY

N4*Libertyville*IL*60048~

10

REF BILLING PROVIDER SECONDARY IDENTIFICATION

REF*EI*10-1234567~

11

PER BILLING PROVIDER CONTACT INFORMATION

PER*IC*Brenda Holly*TE*8019999999~

12

2000B SUBSCRIBER HL LOOP

HL - SUBSCRIBER

HL*2*1*22*0~

13

SBR SUBSCRIBER INFORMATION

SBR*P*18*GRP01020102******CI~

14

2010BA SUBSCRIBER

NM1*IL*1*Smith*Steve*A***MI*MBRID01234~

15

N3 SUBSCRIBER ADDRESS

N3*15210 Juliet Lane~

16

N4 SUBSCRIBER CITY

N4*Libertyville*IL*60048~

17

DMG SUBSCRIBER DEMOGRAPHIC INFORMATION

DMG*D8*19430501*M~

18

2010BB SUBSCRIBER / PAYER

NM1 PAYER NAME

NM1*PR*2*R&R Health Plan*****XY*PLANID12345~

19

2300 CLAIM

CLM CLAIM LEVEL INFORMATION

CLM*CLMNO12345*2232.93***12:B:1*Y*A*Y*Y~

20

HI HEALTH CARE DIAGNOSIS CODE

HI*BK:4659~

21

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*1~

22

SV1 PROFESSIONAL SERVICE

SV1*HC:S9500*1400.00*UN*7*12**1~

23

DTP DATE - SERVICE DATE(S)

DTP*472*RD8*20040201-20040207~

24

2420E ORDERING PROVIDER NAME

NM1 ORDERING PROVIDER NAME

NM1*DK*1*Welby*Marcus****XX*1112223338~

25

2400 SERVICE LINE

LX*2~

26

SV1 PROFESSIONAL SERVICE

SV1*HC:J0696*682.50*UN*56*12**1~

27

DTP DATE - SERVICE DATE(S)

DTP*472*RD8*20040201-20040207~

28

DTP DATE – PRESCRIPTION DATE

DTP*471*D8*20040130~

29

2410 DRUG IDENTIFICATION

LIN DRUG IDENTIFICATION

LIN**N4*00004196501~

30

CTP DRUG QUANTITY

CTP****7*UN~

31

REF PRESCRIPTION NUMBER

REF*XZ*2530001~

32

2420E ORDERING PROVIDER NAME

NM1 ORDERING PROVIDER NAME

NM1*DK*1*Welby*Marcus****XX*1112223338~

33

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*3~

34

SV1 PROFESSIONAL SERVICE

SV1*HC:J7051*15.12*UN*28*12**1~

35

DTP DATE - SERVICE DATE(S)

DTP*472*RD8*20040201-20040207~

36

DTP DATE – PRESCRIPTION DATE

DTP*471*D8*20040130~

37

2410 DRUG IDENTIFICATION

LIN DRUG IDENTIFICATION

LIN**N4*63323024910~

38

CTP DRUG QUANTITY

CTP****14*UN~

39

REF PRESCRIPTION NUMBER

REF*XZ*2530001~

40

2420E ORDERING PROVIDER NAME

NM1 ORDERING PROVIDER NAME

NM1*DK*1*Welby*Marcus****XX*1112223338~

41

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*4~

42

SV1 PROFESSIONAL SERVICE

SV1*HC:J3490:::::Sod Chl 0.9% see NDC#*67.69*UN*7*12**1~

43

DTP DATE - SERVICE DATE(S)

DTP*472*RD8*20040201-20040207~

44

DTP DATE – PRESCRIPTION DATE

DTP*471*D8*20040130~

45

2410 DRUG IDENTIFICATION

LIN DRUG IDENTIFICATION

LIN**N4*00338004938~

46

CTP DRUG QUANTITY

CTP****7*UN~

47

REF PRESCRIPTION NUMBER

REF*XZ*2530001~

48

2420E ORDERING PROVIDER NAME

NM1 ORDERING PROVIDER NAME

NM1*DK*1*Welby*Marcus****XX*1112223338~

49

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*5~

50

SV1 PROFESSIONAL SERVICE

SV1*HC:J3490:::::Sod Chl 0.9% see NDC#*57.12*UN*14*12**1~

51

DTP DATE - SERVICE DATE(S)

DTP*472*RD8*20040201-20040207~

52

DTP DATE – PRESCRIPTION DATE

DTP*471*D8*20040130~

53

2410 DRUG IDENTIFICATION

LIN DRUG IDENTIFICATION

LIN**N4*08290033010~

54

CTP DRUG QUANTITY

CTP****14*UN~

55

REF PRESCRIPTION NUMBER

REF*XZ*2530002~

56

2420E ORDERING PROVIDER NAME

NM1 ORDERING PROVIDER NAME

NM1*DK*1*Welby*Marcus****XX*1112223338~

57

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*6~

58

SV1 PROFESSIONAL SERVICE

SV1*HC:J3490:::::Hep Lock see NDC#*10.50*UN*7*12**1~

59

DTP DATE - SERVICE DATE(S)

DTP*472*RD8*20040201-20040207~

60

DTP DATE – PRESCRIPTION DATE

DTP*471*D8*20040130~

61

2410 DRUG IDENTIFICATION

LIN DRUG IDENTIFICATION

LIN**N4*08290038005~

62

CTP DRUG QUANTITY

CTP****7*UN~

63

REF PRESCRIPTION NUMBER

REF*XZ*2530003~

64

2420E ORDERING PROVIDER NAME

NM1 ORDERING PROVIDER NAME

NM1*DK*1*Welby*Marcus****XX*1112223338~

65

TRAILER

SE TRANSACTION SET TRAILER

SE*65*0711~

Complete Data String:

ST*837*0711*005010X222A2~BHT*0019*00*0013*20040301*1200*CH~N

M1*41*2*Quality Billing Service Corporation*****46*587654321

~PER*IC*Bud Holly*TE*8017268899~NM1*40*2*XYZ Receiver*****46

*369852758~HL*1**20*1~NM1*85*2*Professional Home IV, LLC****

*XX*1234567893~N3*1500 Industrial Drive~N4*Libertyville*IL*6

0048~REF*EI*10-1234567~PER*IC*Brenda Holly*TE*8019999999~HL*

2*1*22*0~SBR*P*18*GRP01020102******CI~NM1*IL*1*Smith*Steve*A

***MI*MBRID01234~N3*15210 Juliet Lane~N4*Libertyville*IL*600

48~DMG*D8*19430501*M~NM1*PR*2*R&R Health Plan*****XY*PLANID1

2345~CLM*CLMNO12345*2232.93***12:B:1*Y*A*Y*Y~HI*BK:4659~LX*1

~SV1*HC:S9500*1400.00*UN*7*12**1~DTP*472*RD8*20040201-200402

07~NM1*DK*1*Welby*Marcus****XX*1112223338~LX*2~SV1*HC:J0696*

682.50*UN*56*12**1~DTP*472*RD8*20040201-20040207~DTP*471*D8*

20040130~LIN**N4*00004196501~CTP****7*UN~REF*XZ*2530001~NM1*

DK*1*Welby*Marcus****XX*1112223338~LX*3~SV1*HC:J7051*15.12*U

N*28*12**1~DTP*472*RD8*20040201-20040207~DTP*471*D8*20040130

~LIN**N4*63323024910~CTP****14*UN~REF*XZ*2530001~NM1*DK*1*We

lby*Marcus****XX*1112223338~LX*4~SV1*HC:J3490:::::Sod Chl 0.

9%see NDC#*67.69*UN*7*12**1~DTP*472*RD8*20040201-20040207~DT

P*471*D8*20040130~LIN**N4*00338004938~CTP****7*UN~REF*XZ*253

0001~NM1*DK*1*Welby*Marcus****XX*1112223338~LX*5~SV1*HC:J349

0:::::Sod Chl 0.9% see NDC#*57.12*UN*14*12**1~DTP*472*RD8*20

040201-20040207~DTP*471*D8*20040130~LIN**N4*08290033010~CTP*

***14*UN~REF*XZ*2530002~NM1*DK*1*Welby*Marcus****XX*11122233

38~LX*6~SV1*HC:J3490:::::Hep Lock see NDC#*10.50*UN*7*12**1~

DTP*472*RD8*20040201-20040207~DTP*471*D8*20040130~LIN**N4*08

290038005~CTP****7*UN~REF*XZ*2530003~NM1*DK*1*Welby*Marcus**

**XX*1112223338~SE*65*0711~

3.1.11 Example 11 - PPO Repriced Claim

Repriced claim being transmitted from a Regional PPO (Preferred Provider Organization) to a commercial health insurance company. The patient is the same person as the subscriber. In this situation, the provider has sent the claim to a clearinghouse, which then forwarded the claim to the repricer; the claim has been repriced and is now being forwarded to the appropriate payer for payment.

SUBSCRIBER/PATIENT: Diamond D. Ring,

ADDRESS: 123 Example Drive, Indianapolis, IN 462290000

SEX: F

DATE OF BIRTH: 12/29/1940

EMPLOYER: COMPANY, INC.

GROUP NUMBER: 123XYZ

MEMBER ID: 00124A089

PATIENT ACCOUNT NUMBER: ABC123-RI

SUBMITTER: Regional PPO Network

SUBMITTER ID: 123456789

RECEIVER: Extra Healthy Insurance

RECEIVER ID: 112244

DESTINATION PAYER: Extra Healthy Insurance

PAYER ID NUMBER: 12345

BILLING PROVIDER: HAPPY DOCTORS GROUP PRACTICE

ADDRESS: P O BOX 123, Fort Wayne, IN 462540000

NATIONAL PROVIDER ID (NPI): 1234567890

TAX IDENTIFICATION NUMBER (TIN): 555-51-2345

REFERRING PROVIDER: John Doe

NATIONAL PROVIDER ID (NPI): 9988776655

RENDERING PROVIDER: Susan B. Anthony

NATIONAL PROVIDER ID (NPI): 1122334455

TOTAL CLAIM CHARGES: $28.75

TOTAL CLAIM REPRICED AMOUNT: $26.75

TOTAL CLAIM SAVINGS AMOUNT: $2.00

SERVICE LINE 1 REPRICING INFORMATION:

TOTAL SERVICE LINE CHARGES: $25.00

TOTAL REPRICED AMOUNT: $23.75

SAVINGS AMOUNT: $1.25

TIN FOR THE REPRICING ORGANIZATION: 908231234

DATE OF SERVICE: 05/14/05

SERVICE LINE 2 REPRICING INFORMATION:

TOTAL SERVICE LINE CHARGES: $3.75

TOTAL REPRICED AMOUNT: $3

SAVINGS AMOUNT: $.75

TIN FOR THE REPRICING ORGANIZATION: 908231234

DATE OF SERVICE: 05/14/05

SEG #

LOOP SEGMENT/ELEMENT STRING

1

TRANSACTION SET HEADER

ST*837*1002*005010X222A2~

2

BHT BEGINNING OF HIERARCHICAL TRANSACTION

BHT*0019*00*1002*20050620*09460000*CH~

3

1000A SUBMITTER NAME

NM1 SUBMITTER NAME

NM1*41*2*REGIONAL PPO                        NETWORK*****46*123456789~

4

PER SUBMITTER EDI CONTACT INFORMATION

PER*IC*SUBMITTER CONTACT                        INFO*TE*8001231234~

5

1000B RECEIVER NAME

NM1 RECEIVER NAME

NM1*40*2*EXTRA HEALTHY                        INSURANCE*****46*112244~

6

2000A BILLING PROVIDER

HL BILLING PROVIDER HIERARCHICAL LEVEL

HL*1**20*1~

7

2010AA BILLING PROVIDER NAME

NM1 BILLING PROVIDER NAME INCLUDING NATIONAL PROVIDER ID

NM1*85*2*HAPPY DOCTORS GROUP                            PRACTICE*****XX*1234567890~

8

N3 BILLING PROVIDER ADDRESS

N3*P O BOX 123~

9

N4 BILLING PROVIDER LOCATION

N4*FORT WAYNE*IN*462540000~

10

REF BILLING PROVIDER TAX IDENTIFICATION NUMBER

REF*EI*555512345~

11

PER BILLING PROVIDER CONTACT INFORMATION

PER*IC*SUE BILLINGSWORTH*TE*8881231234~

12

2000B SUBSCRIBER HL LOOP

HL SUBSCRIBER HIERARCHICAL LEVEL

HL*2*1*22*0~

13

SBR SUBSCRIBER INFORMATION

SBR*P*18*123XYZ******CI~

14

2010BA SUBSCRIBER NAME LOOP

NM1 SUBSCRIBER NAME

NM1*IL*1*RING*DIAMOND*D***MI*00124A089~

15

N3 SUBSCRIBER ADDRESS

N3*123 EXAMPLE DRIVE~

16

N4 SUBSCRIBER LOCATION

N4*INDIANAPOLIS*IN*462290000~

17

DMG SUBSCRIBER DEMOGRAPHIC INFORMATION

DMG*D8*19401229*F~

18

2010BB - PAYER NAME LOOP

NM1 PAYER NAME

NM1*PR*2*EXTRA HEALTHY                        INSURANCE*****PI*12345~

19

2300 CLAIM INFORMATION

CLM CLAIM LEVEL INFORMATION

CLM*ABC123-RI*28.75***11>B>1*Y*A*Y*Y*P~

20

REF REPRICED CLAIM NUMBER

REF*9A*0902352342~

21

REF CLEARING HOUSE CLAIM NUMBER (ASSIGNED BY THE CLEARING HOUSE WHEN TRANSMITTING TO THE REPRICER)

REF*D9*061505501749388~

22

HI HEALTH CARE DIAGNOSIS CODES

HI*BK>496*BF>25000~

23

HCP HEALTH CARE PRICING - REPRICING INFORMATION

HCP*03*26.75*2*908231234~

24

2310A REFERRING PROVIDER

NM1 REFERRING PROVIDER

NM1*DN*1*DOE*JOHN****XX*9988776655~

25

2310B RENDERING PROVIDER

NM1 RENDERING PROVIDER

NM1*82*1*ANTHONY*SUSAN*B***XX*1122334455~

26

2310D SERVICE FACILITY LOCATION

NM1 SERVICE FACILITY LOCATION

NM1*77*2*HAPPY DOCTORS GROUP~

27

N3 FACILITY ADDRESS

N3*123 FEEL GOOD ROAD~

28

N4 FACILITY LOCATION

N4*WASHINGTON*IN*475010000~

29

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*1~

30

SV1 PROFESSIONAL SERVICE

SV1*HC>E0570>RR*25*UN*1***1>2~

31

DTP DATE - SERVICE DATES

DTP*472*D8*20050514~

32

HCP HEALTH CARE PRICING - REPRICING INFORMATION

HCP*03*23.75*1.25*908231234~

33

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*2~

34

SV1 PROFESSIONAL SERVICE

SV1*HC>A7003>NU*3.75*UN*1***1~

35

DTP DATE - SERVICE DATES

DTP*472*D8*20050514~

36

HCP HEALTH CARE PRICING - REPRICING INFORMATION

HCP*03*3*.75*908231234~

37

TRAILER

SE TRANSACTION SET TRAILER

SE*37*1002~

Complete Data String:

ST*837*1002*005010X222A2~BHT*0019*00*1002*20050620*09460000*

CH~NM1*41*2*REGIONAL PPO NETWORK*****46*123456789~PER*IC*SUB

MITTER CONTACT INFO*TE*8001231234~NM1*40*2*EXTRA HEALTHY INS

URANCE*****46*112244~HL*1**20*1~NM1*85*2*HAPPY DOCTORS GROUP

PRACTICE*****XX*1234567890~N3*P O BOX 123~N4*FORT WAYNE*IN*

462540000~REF*EI*555512345~PER*IC*SUE BILLINGSWORTH*TE*88812

31234~HL*2*1*22*0~SBR*P*18*123XYZ******CI~NM1*IL*1*RING*DIAM

OND*D***MI*00124A089~N3*123 EXAMPLE DRIVE~N4*INDIANAPOLIS*IN

*462290000~DMG*D8*19401229*F~NM1*PR*2*EXTRA HEALTHY INSURANC

E*****PI*12345~CLM*ABC123-RI*28.75***11>B>1*Y*A*Y*Y*P~REF*9A

*0902352342~REF*D9*061505501749388~HI*BK>496*BF>25000~HCP*03

*26.75*2*908231234~NM1*DN*1*DOE*JOHN****XX*9988776655~NM1*82

*1*ANTHONY*SUSAN*B***XX*1122334455~NM1*77*2*HAPPY DOCTORS GR

OUP~N3*123 FEEL GOOD ROAD~N4*WASHINGTON*IN*475010000~LX*1~SV

1*HC>E0570>RR*25*UN*1***1>2~DTP*472*D8*20050514~HCP*03*23.75

*1.25*908231234~LX*2~SV1*HC>A7003>NU*3.75*UN*1***1~DTP*472*D

8*20050514~HCP*03*3*.75*908231234~SE*37*1002~

3.1.12 Example 12 - Out of Network Repriced Claim

An out of network claim is being transmitted from a Regional PPO (Preferred Provider Organization) to a commercial health insurance company. The patient is a child of the subscriber. In this situation, the provider has sent the claim to a clearinghouse, which then forwarded the claim to the repricer; the claim has been determined to be out of network and is now being forwarded to the appropriate payer for payment.

SUBSCRIBER: Matthew R. Smith

ADDRESS: 5698 South Street, Billings, MO 919910000

SEX: M

DATE OF BIRTH: 10/15/1956

EMPLOYER: Lumber Company.

GROUP NUMBER: 232AA

MEMBER ID: 57976235C

PATIENT: Tom E. Smith

ADDRESS: 5698 South Street, Billings, MO 919910000

SEX: M

DATE OF BIRTH: 08/07/1996

PATIENT ACCOUNT NUMBER: TS234H3

OTHER INSURANCE: Secondary Insurance Company

PAYER ID: 95645

GROUP NUMBER: 56567

OTHER INSURED MEMBER ID: 23424570

SUBMITTER: Regional PPO Network

SUBMITTER ID: 123456789

RECEIVER: Conservative Insurance

RECEIVER ID: 000110002

DESTINATION PAYER: Conservative Insurance

PAYER ID NUMBER: 00123

BILLING PROVIDER: Emergency Physicians Group

ADDRESS: 7423 Super Street, Billings, MO 919910000

NATIONAL PROVIDER ID (NPI): 1122334455

TAX IDENTIFICATION NUMBER (TIN): 111-00-2222

RENDERING PROVIDER: Jackie D. Blue

NATIONAL PROVIDER ID (NPI): 1112223336

REPRICING INFORMATION:

TOTAL CHARGES: $252.71

TOTAL REPRICED AMOUNT: $0

SAVINGS AMOUNT: $0

TIN FOR THE REPRICING ORGANIZATION: 333001234

DATE OF SERVICE: 05/06/05

SEG #

LOOP SEGMENT/ELEMENT STRING

1

TRANSACTION SET HEADER

ST*837*1024*005010X222A2~

2

BHT BEGINNING OF HIERARCHICAL TRANSACTION

BHT*0019*00*1024*20050711*1335*CH~

3

1000A SUBMITTER NAME

NM1 SUBMITTER NAME

NM1*41*2*REGIONAL PPO                        NETWORK*****46*123456789~

4

PER SUBMITTER EDI CONTACT INFORMATION

PER*IC*SUBMITTER CONTACT                        INFO*TE*8001231234~

5

1000B RECEIVER NAME

NM1 RECEIVER NAME

NM1*40*2*CONSERVATIVE                        INSURANCE*****46*000110002~

6

2000A BILLING PROVIDER

HL BILLING PROVIDER HIERARCHICAL LEVEL

HL*1**20*1~

7

2010AA BILLING PROVIDER NAME

NM1 BILLING PROVIDER NAME INCLUDING NATIONAL PROVIDER ID

NM1*85*2*EMERGENCY PHYSICIANS                            GROUP*****XX*1122334455~

8

N3 BILLING PROVIDER ADDRESS

N3*7423 SUPER STREET~

9

N4 BILLING PROVIDER LOCATION

N4*BILLINGS*MO*919910000~

10

REF BILLING PROVIDER TAX IDENTIFICATION NUMBER

REF*EI*111002222~

11

2000B SUBSCRIBER HL LOOP

HL SUBSCRIBER HIERARCHICAL LEVEL

HL*2*1*22*1~

12

SBR SUBSCRIBER INFORMATION

SBR*P**232AA******CI~

13

2010BA SUBSCRIBER NAME LOOP

NM1 SUBSCRIBER NAME

NM1*IL*1*SMITH*MATTHEW*R***MI*57976235C~

14

N3 SUBSCRIBER ADDRESS

N3*5698 SOUTH STREET~

15

N4 SUBSCRIBER LOCATION

N4*BILLINGS*MO*919910000~

16

DMG SUBSCRIBER DEMOGRAPHIC INFORMATION

DMG*D8*19561015*M~

17

2010BB - PAYER NAME LOOP

NM1 PAYER NAME

NM1*PR*2*CONSERVATIVE                        INSURANCE*****PI*00123~

18

2000C - PATIENT HL LOOP

HL PATIENT HIERARCHICAL LEVEL

HL*3*2*23*0~

19

PAT PATIENT INFORMATION

PAT*19~

20

2010CA PATIENT NAME

NM1 PATIENT NAME

NM1*QC*1*SMITH*TOM*E~

21

N3 PATIENT STREET ADDRESS

N3*5698 SOUTH STREET~

22

N4 PATIENT LOCATION

N4*BILLINGS*MO*919910000~

23

DMG PATIENT DEMOGRAPHIC INFORMATION

DMG*D8*19960807*M~

24

2300 CLAIM INFORMATION

CLM CLAIM LEVEL INFORMATION

CLM*TS234H3*252.71***23>B>1*Y*A*Y*Y*P~

25

REF REPRICED CLAIM NUMBER

REF*9A*0902345406~

26

REF CLEARING HOUSE CLAIM NUMBER (ASSIGNED BY THE CLEARING HOUSE WHEN TRANSMITTING TO THE REPRICER)

REF*D9*687534234346~

27

HI HEALTH CARE DIAGNOSIS CODES

HI*BK>9951~

28

HCP HEALTH CARE PRICING - OUT OF NETWORK INFORMATION

HCP*00*0**333001234*********T1~

29

2310B RENDERING PROVIDER

NM1 RENDERING PROVIDER

NM1*82*1*BLUE*JACKIE*D***XX*1112223336~

30

2320 OTHER SUBSCRIBER INFORMATION

SBR OTHER SUBSCRIBER INFORMATION

SBR*S*18*56567******CI~

31

DMG OTHER SUBSCRIBER DEMOGRAPHIC INFORMATION

DMG*D8*19960807*M~

32

OI OTHER INSURANCE COVERAGE INFORMATION

OI***Y***Y~

33

2330A OTHER SUBSCRIBER NAME

NM1 OTHER SUBSCRIBER NAME

NM1*IL*1*SMITH*TOM*E***MI*23424570~

34

N3 OTHER SUBSCRIBER ADDRESS

N3*5698 SOUTH STREET~

35

N4 OTHER SUBSCRIBER LOCATION

N4*BILLINGS*MO*919910000~

36

2330B OTHER PAYER NAME

NM1 OTHER PAYER NAME

NM1*PR*2*SECONDARY INSURANCE                        COMPANY*****PI*95645~

37

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*1~

38

SV1 PROFESSIONAL SERVICE

SV1*HC>99284*252.71*UN*1***1~

39

DTP DATE - SERVICE DATES

DTP*472*D8*20050506~

40

TRAILER

SE TRANSACTION SET TRAILER

SE*40*1024~

Complete Data String:

ST*837*1024*005010X222A2~BHT*0019*00*1024*20050711*1335*CH~N

M1*41*2*REGIONAL PPO NETWORK*****46*123456789~PER*IC*SUBMITT

ER CONTACT INFO*TE*8001231234~NM1*40*2*CONSERVATIVE INSURANC

E*****46*000110002~HL*1**20*1~NM1*85*2*EMERGENCY PHYSICIANS

GROUP*****XX*1122334455~N3*7423 SUPER STREET~N4*BILLINGS*MO*

919910000~REF*EI*111002222~HL*2*1*22*1~SBR*P**232AA******CI~

NM1*IL*1*SMITH*MATTHEW*R***MI*57976235C~N3*5698 SOUTH STREET

~N4*BILLINGS*MO*919910000~DMG*D8*19561015*M~NM1*PR*2*CONSERV

ATIVE INSURANCE*****PI*00123~HL*3*2*23*0~PAT*19~NM1*QC*1*SMI

TH*TOM*E~N3*5698 SOUTH STREET~N4*BILLINGS*MO*919910000~DMG*D

8*19960807*M~CLM*TS234H3*252.71***23>B>1*Y*A*Y*Y*P~REF*9A*09

02345406~REF*D9*687534234346~HI*BK>9951~HCP*00*0**333001234*

********T1~NM1*82*1*BLUE*JACKIE*D***XX*1112223336~SBR*S*18*5

6567******CI~DMG*D8*19960807*M~OI***Y***Y~NM1*IL*1*SMITH*TOM

*E***MI*23424570~N3*5698 SOUTH STREET~N4*BILLINGS*MO*9199100

00~NM1*PR*2*SECONDARY INSURANCE COMPANY*****PI*95645~LX*1~SV

1*HC>99284*252.71*UN*1***1~DTP*472*D8*20050506~SE*40*1024~

3.2 Property and Casualty

Healthcare Bill to Property & Casualty Payer

The requirements for submitting of Healthcare bills to Property & Casualty payers are presented here.

837 Transaction Set

Healthcare bills can be submitted to a Property & Casualty (P&C) payer. Because coverage is triggered by a specific event, certain information is critical to the billing process.

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

P&C insurance is governed by State Insurance Regulations, Departments of Labor, Worker's Compensation Boards, or other jurisdictionally defined entities, which often mandates compliance with Jurisdiction-specific procedures.

The Business Need: Provider to P&C Payer Bill Transmission

  • The date of accident/occurrence/onset of symptoms (Date of Loss) is a critical piece of information and must always be transmitted in the "Date - Accident" DTP segment within Loop ID-2300 (Claim loop).

    The Date of Loss is used to determine the eligibility of coverage.

  • The unique identification number, referred to in P&C as a claim number, must be provided. The claim number is transmitted in the REF segment of Loop ID-2010BA if the patient is the subscriber or in the REF segment of Loop ID-2010CA if the patient is not the subscriber.

    Without a date of loss on the bill and claim number, the bill will incomplete and may be rejected.

3.2.1 Example 1 - Automobile Accident

BUSINESS SCENARIO: Automobile Accident

CLAIM TYPE: Automobile Accident

TYPE OF BILL: Emergency Care

PRIMARY PAYER: Property & Casualty Insurer

The patient is a different person than the subscriber. The payer is a commercial Property & Casualty Insurance Company.

DATE OF ACCIDENT: 10/31/2005

SUBSCRIBER: Hal Howling

SUBSCRIBER ADDRESS: 327 Bronco Drive, Getaway, CA, 99999

POLICY NUMBER: B999-777-91G

INSURANCE COMPANY: Heisman Insurance Company

CLAIM NUMBER: 32-3232-32

PATIENT: D.J. Dimpson

PATIENT ADDRESS: 32 Buffalo Run, Rocking Horse, CA, 99666

SEX: M

DOB: 06/01/48

CONTACT NUMBER: (815) 766-5902

DESTINATION PAYER/RECEIVER: Heisman Insurance Company

PAYER ADDRESS: 1 Trophy Lane, NYAC, NY, 10032

PAYER ID: 999888777

BILLING PROVIDER/SENDER: Associated Medical Group

PROVIDER SPECIALTY: General Practice

TIN: 579999999

NATIONAL PROVIDER IDENTIFIER: 1253695747

ADDRESS: 10 1/2 Shoemaker Street, Cobbler, CA, 99997

TELEPHONE: 212-555-7987

PAY-TO-PROVIDER: Associated Medical Group

RENDERING PROVIDER: Bruno Moglie, MD

NATIONAL PROVIDER IDENTIFIER: 2366552595

SERVICE FACILITY LOCATION: Associated Medical Group

PROVIDER SPECIALTY: General Practice

TIN: 579999999

NATIONAL PROVIDER IDENTIFIER: 1253695747

ADDRESS: 101 East Pryor Street, Loma Linda, CA. 99622

TELEPHONE: 342-555-7987

PATIENT ACCOUNT NUMBER: 900-00-0032

CASE: The patient was a passenger in the subscriber's automobile. The patient suffered a head and neck injury.

DIAGNOSIS: 854.0

SERVICES RENDERED: Office visit, Drain Abscess.

DOS = 10/31/2005, POS = Office, TOS = Medical Care

CHARGES: Office visit = $150.00, Suture wound = $35.00. Total charges = $185.00.

SEG #

LOOP SEGMENT/ELEMENT STRING

1

HEADER

ST TRANSACTION SET HEADER

ST*837*0021*005010X222A2~

2

BHT BEGINNING OF HIERARCHICAL TRANSACTION

BHT*0019*00*0125*20051111*1524*CH~

3

1000A SUBMITTER

NM1 SUBMITTER

NM1*41*2*ASSOCIATED MEDICAL                            GROUP*****46*1253695747~

4

PER SUBMITTER EDI CONTACT INFORMATION

PER*IC*JANICE HENDRIX*TE*2125557987~

5

1000B RECEIVER

NM1 RECEIVER NAME

NM1*40*2*HEISMAN INSURANCE                            COMPANY*****46*999888777~

6

2000A BILLING/PAY-TO PROVIDER HL LOOP

HL BILLING PROVIDER

HL*1**20*1~

7

2010AA BILLING PROVIDER

NM1 BILLING PROVIDER NAME

NM1*85*2*ASSOCIATED MEDICAL                            GROUP*****XX*1253695747~

8

N3 BILLING PROVIDER ADDRESS

N3*10 1/2 SHOEMAKER STREET~

9

N4 BILLING PROVIDER CITY/STATE/ZIP CODE

N4*COBBLER*CA*99997~

10

REF BILLING PROVIDER SECONDARY IDENTIFICATION

REF*EI*579999999~

11

2000B SUBSCRIBER HL LOOP

HL - SUBSCRIBER

HL*2*1*22*1~

12

SBR SUBSCRIBER INFORMATION

SBR*P********AM~

13

2010BA SUBSCRIBER

NM1 SUBSCRIBER NAME

NM1*IL*1*HOWLING*HAL****MI*B99977791G~

14

2010BB SUBSCRIBER/PAYER

NM1 PAYER NAME

NM1*PR*2*HEISMAN INSURANCE                            COMPANY*****PI*999888777~

15

2000C PATIENT HL LOOP

HL - PATIENT

HL*3*2*23*0~

16

PAT PATIENT INFORMATION

PAT*21~

17

2010CA PATIENT NAME

NM1 PATIENT NAME

NM1*QC*1*DIMPSON*DJ~

18

N3 PATIENT STREET ADDRESS

N3*32 BUFFALO RUN~

19

N4 PATIENT CITY/STATE/ZIP

N4*ROCKING HORSE*CA*99666~

20

DMG PATIENT DEMOGRAPHIC INFORMATION

DMG*D8*19480601*M~

21

REF PROPERTY AND CASUALTY CLAIM NUMBER

REF*Y4*32323232~

22

PER PROPERTY AND CASUALTY PATIENT CONTACT INFORMATION

PER*IC*DJ DIMPSON*TE*8157665902~

23

2300 CLAIM

CLM CLAIM LEVEL INFORMATION

CLM*900000032*185***11:B:1*Y*A*Y*Y**AA:::CA~

24

DTP DATE - ACCIDENT

DTP*439*D8*20051031~

25

DTP DATE - PROPERTY AND CASUALTY DATE OF FIRST CONTACT

DTP*444*D8*20051031~

26

HEALTH CARE DIAGNOSIS CODES

HI*BK:8540~

27

2310B RENDERING PROVIDER

NM1 RENDERING PROVIDER NAME

NM1*82*1*MOGLIE*BRUNO****XX*2366552595~

28

PRV RENDERING PROVIDER SPECIALTY INFORMATION

PRV*PE*PXC*208D00000X~

29

2310C SERVICE FACILITY LOCATION

NM1 SERVICE FACILITY LOCATION

NM1*77*2*ASSOCIATED MEDICAL                            GROUP*****XX*1235767887~

30

N3 SERVICE FACILITY LOCATION ADDRESS

N3*101 EAST PRYOR STREET~

31

N4 SERVICE FACILITY LOCATION CITY/STATE/ZIP

N4*LOMA LINDA*CA*99622~

32

PER PROPERTY AND CASUALTY SERVICE FACILITY CONTACT INFORMATION

PER*IC*KAREN SPARKLE*TE*3425557987~

33

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*1~

34

SV1 PROFESSIONAL SERVICE

SV1*HC:99201*150*UN*1***1**Y~

35

DTP DATE - SERVICE DATE(S)

DTP*472*D8*20051031~

36

2400 SERVICE LINE

LX SERVICE LINE COUNTER

LX*2~

37

SV1 PROFESSIONAL SERVICE

SV1*HC:26010*35*UN*1***1**Y~

38

DTP DATE - SERVICE DATE(S)

DTP*472*D8*20051031~

39

TRAILER

SE TRANSACTION SET TRAILER

SE*39*0021~

Complete Data String:

ST*837*0021*005010X222A2~BHT*0019*00*0125*20051111*1524*CH~N

M1*41*2*ASSOCIATED MEDICAL GROUP*****46*1253695747~PER*IC*JA

NICE HENDRIX*TE*2125557987~NM1*40*2*HEISMAN INSURANCE COMPAN

Y*****46*999888777~HL*1**20*1~NM1*85*2*ASSOCIATED MEDICAL GR

OUP*****XX*1253695747~N3*10 1/2 SHOEMAKER STREET~N4*COBBLER*

CA*99997~REF*EI*579999999~HL*2*1*22*1~SBR*P********AM~NM1*IL

*1*HOWLING*HAL****MI*B99977791G~NM1*PR*2*HEISMAN INSURANCE C

OMPANY*****PI*999888777~HL*3*2*23*0~PAT*21~NM1*QC*1*DIMPSON*

DJ~N3*32 BUFFALO RUN~N4*ROCKING HORSE*CA*99666~DMG*D8*194806

01*M~REF*Y4*32323232~PER*IC*DJ DIMPSON*TE*8157665902~CLM*900

000032*185***11:B:1*Y*A*Y*Y**AA:::CA~DTP*439*D8*20051031~DTP

*444*D8*20051031~HI*BK:8540~NM1*82*1*MOGLIE*BRUNO****XX*2366

552595~PRV*PE*PXC*208D00000X~NM1*77*2*ASSOCIATED MEDICAL GRO

UP*****XX*1235767887~N3*101 EAST PRYOR STREET~N4*LOMA LINDA*

CA*99622~PER*IC*KAREN SPARKLE*TE*3425557987~LX*1~SV1*HC:9920

1*150*UN*1***1**Y~DTP*472*D8*20051031~LX*2~SV1*HC:26010*35*U

N*1***1**Y~DTP*472*D8*20051031~SE*39*0021~

Appendix A. External Code Sources

A.1 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.

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 Procedural Coding System

SIMPLE DATA ELEMENT/CODE REFERENCES

235/HC, 1270/BO, 1270/BP

SOURCE

Healthcare Common Procedural Coding System

AVAILABLE FROM

Centers for Medicare & Medicaid Services

7500 Security Boulevard

Baltimore, MD 21244

ABSTRACT

HCPCS is Centers for Medicare & Medicaid Service's (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/Blue Shield Association

Interplan Teleprocessing Services Division

676 N. St. Clair Street

Chicago, IL 60611

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 Position 3

AVAILABLE FROM

National Uniform Billing Committee

American Hospital Association

One North Franklin

Chicago, IL 60606

ABSTRACT

A variety of codes explaining the frequency of the bill submission.

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 and Medicaid Services

CMSO, Mail Stop S2-01-16

7500 Security Blvd

Baltimore, MD 21244-1850

ABSTRACT

The Centers for Medicare and 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.

411 Remittance Advice Remark Codes

SIMPLE DATA ELEMENT/CODE REFERENCES

1270/HE

SOURCE

Centers for Medicare and Medicaid Services

OIS/BSOG/DDIS,

Mail stop N2-13-16

7500 Security Boulevard

Baltimore, MD 21244

AVAILABLE FROM

Washington Publishing Company

http://www.wpc-edi.com/

ABSTRACT

Remittance Advice Remark Codes (RARC) are used to convey information about claim adjudication. It could provide general information or supplemental explanations to an adjustment already reported by a Claim Adjustment Reason Code.

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 and Medicaid Services National Provider Identifier

SIMPLE DATA ELEMENT/CODE REFERENCES

66/XX, 128/HPI

SOURCE

National Provider System

AVAILABLE FROM

Centers for Medicare and 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 and 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.

582 Centers for Medicare and Medicaid Services (CMS) Durable Medical Equipment Regional Carrier (DMERC) Certificate of Medical Necessity (CMN) Forms

SIMPLE DATA ELEMENT/CODE REFERENCES

1270/UT

SOURCE

Durable Medical Equipment Regional Carrier (DMERC) Certificate of Medical Necessity (CMN) Forms

AVAILABLE FROM

Centers for Medicare and Medicaid Services

Attention: Supplier Claims Processing Unit

Mail Stop S1-03-06

7500 Security Boulevard

Baltimore, MD 21244

ABSTRACT

A listing of the Durable Medical Equipment Regional Carrier (DMERC) Certificate of Medical Necessity (CMN) Forms and a listing of the questions from each form.

656 Form Type Codes

SIMPLE DATA ELEMENT/CODE REFERENCES

1270/AS

SOURCE

Form Type Codes

AVAILABLE FROM

Standards Department

Agency Company Organization for Research and Development (ACORD)

One Blue Hill Plaza - 15th Floor

P.O. Box 1529

Pearl River, NY 10965-8529

ABSTRACT

Form Type Codes is a list of codes indicating the level of coverage provided by a policy contract.

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

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

Appendix B. Nomenclature

B.1 ASC X12 Nomenclature

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 - Decimal 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 Application Control Structure Definitions and Concepts

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 Table B.1 - Basic Character Set, includes those selected from the uppercase letters, digits, space, and special characters as specified below.

Table B.1 - 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 Table B.2 - Extended Character Set.

Table B.2 - 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.4.1 - Base Control Set.

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 Table B.3 - 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:

Table B.3 - Base Control Set

NOTATIONNAMEEBCDICASCIIIA5
BELbell2F0707
HThorizontal tab050909
LFline feed250A0A
VTvertical tab0B0B0B
FFform feed0C0C0C
CRcarriage return0D0D0D
FSfile separator1C1C1C
GSgroup separator1D1D1D
RSrecord separator1E1E1E
USunit separator1F1F1F
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 Table B.4 - Extended Control Set.

Table B.4 - Extended Control Set

NOTATIONNAMEEBCDICASCIIIA5
SOHstart of header010101
STXstart of text020202
ETXend of text030303
EOTend of transmission370404
ENQenquiry2D0505
ACKacknowledge2E0606
DC1device control 1111111
DC2device control 2121212
DC3device control 3131313
DC4device control 43C1414
NAKnegative acknowledge3D1515
SYNsynchronous idle321616
ETBend of block261717
B.1.1.2.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 Table B.5 - Delimiters, in all examples of EDI transmissions.

Table B.5 - Delimiters

CHARACTER NAME DELIMITER
* Asterisk Data Element Separator
^ Carat 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 X12standard. 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 Table B.6 - Data Element Types, appear in this implementation guide.

Table B.6 - Data Element Types

SYMBOL TYPE
NnNumeric
RDecimal
IDIdentifier
ANString
DTDate
TMTime
BBinary

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 asrepeating 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 Section B.1.1.3.8 - Reference Designator and Section B.1.1.3.9 - Condition Designator.

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 Section 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 provideda structured code that indicates the segment in which it is used and thesequential position within the segment. The code is composed of the segmentidentifier followed by a two-digit number that defines the position of thesimple data element or composite data structure in that segment.

For purposes of creating reference designators, the composite data structureis viewed as the hierarchical equal of the simple data element. Each componentdata element in a composite data structure is identified by a suffix appended tothe reference designator for the composite data structure of which it is amember. This suffix is prefixed with a hyphen and definesthe 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.7 - 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- OptionalThe 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- RelationalRelational 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 CODEDEFINITION
P- Paired or Multiple If any element specified in the relational condition is present, then all of the elements specified must be present.
R- RequiredAt 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- ConditionalIf 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 fortransferring 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.

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.

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

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.

Table B.8 - Data Segment Requirement Designators

DESIGNATORDESCRIPTION
M- MandatoryThis 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- OptionalThe 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 Envelopes and Control Structures

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 controlmeasures. For instance, the ISA segment contains data elements such asauthorization information, security information, sender identification, andreceiver identification that can be used for control purposes. These dataelements are agreed upon by the trading partners prior to transmission. Theinterchange date and time data elements as well as the interchange controlnumber within the ISA segment are used for debugging purposes when there is aproblem with the transmission or the interchange.

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

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

See Appendix C, EDI Control Directory, for a complete detailing of theinter-change control header and trailer. The authors recommend that when twotransactions with different X12 versions numbers are sent in one interchangecontrol structure (multiple functional groups within one ISA/IEA envelope), theInterchange Control version used should be that of the most recent transactionversion included in the envelope. For the transmission of HIPAA transactionswith 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 functionalidentifier code in GS01. The Functional Identifier Code is used by thecommercial translation software during interpretation of the interchange todetermine the different transaction sets that may be included within thefunctional group. If an inappropriate transaction set is contained within thefunctional group, most commercial translation software will suspend thefunctional group within the interchange. The Application Sender's Code in GS02can be used to identify the sending unit of the transmission. The ApplicationReceiver's Code in GS03 can be used to identify the receiving unit of thetransmission. The functional group contains a creation date (GS04) and creationtime (GS05) for the functional group. The Group Control Number is contained inGS06. These data elements (GS04, GS05, and GS06) can be used for debuggingpurposes. GS08,Version/Release/Industry Identifier Code is theversion/release/sub-release of the transaction sets being transmitted in thisfunctional group.

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

See Appendix C, EDI Control Directory, for a complete detailing of thefunctional 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 loopsidentified by the HL structure shall appear in the hierarchical order specifiedin BHT01, when those particular hierarchical levels exist. That is, an HL parentloop must be followed by the subordinate child loops, if any, prior tocommencing a new HL parent loop at the same hierarchical level.

The following diagram, from transaction set 837, illustrates a typicalhierarchy.

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 Acknowledgments

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 Section 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:

EntityExample
1. Transaction Set Identifier plus a unique 2 character value837Q1
2. Above plus under bar plus Loop Identifier as assigned within an implementation guide837Q1_2330C
3. Above plus under bar plus Segment Identifier837Q1_2330C_NM1
4. Above plus Reference Designator plus under bar plus Composite Identifier837Q1_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.

EntityExample
5. Number 4 above plus composite sequence plus under bar plus name837Q1_2400_SV101_C00302_ProcedureCode
6. Number 3 above plus Reference Designator plus two under bars plus name837Q1_2330C_NM109__OtherPayerPatientPrimaryIdentifier

Said in another way, ODs contain a coded component specifying a location in animplementation 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 Implementation Guide defines X12N implementation 005010X222 of the Health Care Claim: Professional. It is based on version/release/subrelease 005010 of the ASC X12 standards. The previous X12N implementation of the Health Care Claim: Professional was 004050X143, based on version/release/subrelease 004050 of the ASC X12 standards.

Implementation of 005010X222 contains significant changes and clarifications. It can only be used with other trading partners who have also implemented 005010X222. Below is a high-level description of the substantive changes from the previous version.

D.1. Global Changes

  1. All Situational notes throughout this implementation guide have changed to comply with ASC X12N implementation guide standards.

  2. The guide contains many revisions to informational notes within the various loops, segments and data elements. The revisions add explanatory text.

  3. Billing Provider as well as all 2310x and 2420x provider loops contain instruction on the use of the HIPAA National Provider Identifier (NPI) both prior to, and after, the nationally mandated implementation date for that identifier. In instances where a provider identifier is reported, the National Provider Identifier is reported in NM109 data element with a NM108 qualifier of XX. The EIN and SSN qualifiers have been removed from all provider related NM108 elements. Any secondary or proprietary identifiers are reported in the secondary identifier REF segments. For a more detailed explanation of NPI usage, see Section 1.10 National Provider Identifier Usage within the HIPAA 837 Transaction.

  4. The G2 qualifier replaces program-specific codes such as 1A, Blue Cross; 1B, Blue Shield; 1C, Medicare, 1D, Medicaid; 1H, Champus; etc. to designate a proprietary identifier in all Secondary Identification provider segments.

  5. The following qualifiers have been revised to assign specific values in place of generic values:

    • The Provider Taxonomy Code has replaced the generic value of ZZ (Mutually Defined) with the specific value of PXC (Health Care Provider Taxonomy Code).

    • The qualifier for the HIPAA Individual Patient Identifier has replaced the generic value of ZZ (Mutually Defined) with the specific value of II (Standard Unique Health Identifier for each individual in the United States).

  6. In order to report payer-specific provider identifiers, prior authorization, and referral, numbers for non-destination payers at the service line level, data element REF04 is used to indicate the payer associated with the identifier in REF01 and REF02.

  7. Requirements for address segments (N3 and N4) have changed. The underlying code sets for country codes and sub-country codes, as well as for postal zones (ZIP Codes in the US) have been enhanced for greater international mailing uniformity.

  8. References to "Insured" in notes and implementation names have changed to the more descriptive term "Subscriber". See Section 1.5 Business Terminology and Section 1.4.3.2.2.2, Subscriber / Patient Hierarchical Level (HL) Segment for more information.

  9. Changes have been made to support the National Plan Identifier, if mandated for use. This identifier is accommodated in the following loops:

    • Pay-to Plan Name, Loop ID-2010AC

    • Payer Name, Loop ID-2010BB

    • Other Payer Name, Loop ID-2330B

  10. All aliases have been removed from the guide.

  11. Line level segments and elements related to the Oxygen Therapy Certificate of Medical Necessity have been deleted or changed to Not Used. The information will be reported in Loop ID-2440 Supporting Information (FRM) segment. The individual segments, elements, and code deletions are included in the Detailed Changes.

  12. The guide ID has changed to 005010X222A2 (this guide) in several places in the Front Matter and in Section 3 Examples.

D.2. Detailed Changes

ASC X12N implementation guide standards for the content and organization of Front Matter sections have changed for this version. The items listed below are those where significant changes have occurred. This list does not include section numbering changes.

Front Matter

  1. The explanation of COB reporting (Section 1.4.1) is enhanced and a crosswalk chart and examples are added to show how destination and non-destination payer related information is reported on primary and secondary claims. The COB section includes several new supplemental explanations:

  2. A section is added to specify the balancing requirements for the 837 transaction (Section 1.4.4).

  3. A section is added to explain allowed and approved amount reporting and calculations (Section 1.4.5).

  4. Business Terminology (Section 1.5) is expanded to include new definitions of Bundling, Claim, Encounter, Inpatient, Outpatient, Pay-to-Plan Claims, and Unbundling. Other definitions were updated.

  5. A section is added (Section 1.10) to describe the use of the National Provider Identifier (NPI) with the 837 transaction.

  6. A section is added (Section 1.11) to explain the reporting of drug claims with the 837 transaction.

  7. A section is added (Section 1.12) to address a number of additional 837 reporting instructions, including:

    • Individuals with one legal name,

    • Rejecting claims based on the inclusion of situational data,

    • Multiple REF segments with the same qualifier,

    • Provider Tax ID's,

    • Claim and line redundant information,

    • Inpatient and outpatient designation, and

    • Trading partner acknowledgments.

Transaction Header

  1. The value of the Implementation Reference Number (ST03) has changed to 005010X222A2, which represents the guide ID for this implementation guide.

  2. The Beginning of Hierarchical Transaction (BHT) segment includes examples for a claim and an encounter.

Loop ID-2000A

  1. Beginning with the 5010 version, the Billing Provider must be a health care or atypical service provider (as described in Section 1.10.1 Providers Who Are Not Eligible for Enumeration).

  2. The Pay-to Provider loop has been renamed and is now called the Pay-to Address Name loop (Loop ID-2010AB). Its one and only purpose is to supply an alternate location to send reimbursement.

  3. Due to the change in function of the Pay-to Address Name loop, the only permitted value for the Provider Code (PRV01) in the Billing Provider Specialty Information (PRV) segment is BI (Billing). The guide no longer supports value PT (Pay-To).

  4. The Situational Rule for the Billing Provider Taxonomy (PRV) segment has been expanded to enable non-individual taxonomies to be used.

  5. The segment notes for the Foreign Currency Information (CUR) segment now include the instruction that all amounts reported in the transaction be of the currency named in the CUR segment. If there is no CUR segment, then all amounts will be in US dollars.

Loop ID-2010AA

  1. The Billing Provider loop contains no payer-specific provider identifiers. When it is necessary to send a payer-specific provider identifier, it must be sent in either the Payer Name loop (Loop ID-2010BB) or the Other Payer Name loop (Loop ID-2330B).

  2. The only provider identifiers allowed in the Billing Provider loop are:

    • the NPI

    • the provider's taxpayer id

    • the provider's state license number

    • the provider's UPIN

  3. The Billing Provider Name segment contains the NPI, which is Situational.

  4. The Billing Provider Address must be a street address. Other types of mailing addresses for the Billing Provider (such as a Post Office Box or a Lock Box) must be sent in the Pay-To Address Name loop.

  5. The Billing Provider Secondary Identification Number segment has split into two named REF segments: the Billing Provider Tax Identification segment and the Billing Provider UPIN/License Information segment.

  6. The Billing Provider Tax Identification (REF) segment is required and contains the provider's taxpayer identifier to be used for 1099 reporting purposes.

  7. The Billing Provider UPIN / License Information segment is situational and can contain the license number, the UPIN or both identifiers. If the provider has an NPI and is required by HIPAA to send the NPI, then this segment is not used.

  8. The Claim Submitter Credit/Debit Card Information (REF) segment has been deleted.

  9. The Billing Provider Contact Name (PER02) is Required in the first iteration of the Billing Provider Contact Information segment. If a second iteration of the segment is sent, PER02 is Not Used.

Loop ID-2010AB

  1. The Pay-To Address Name loop replaces the Pay-To Provider Name loop. Its sole purpose is to supply an alternate location to send reimbursement. There are no names and no identifiers in the Pay-To Address Name loop.

  2. The Pay-To Provider Secondary Identification Number (REF) segment has been removed.

Loop ID-2010AC

  1. The usage of the Pay-to Plan Name loop has expanded and is no longer limited to Medicaid subrogation.

  2. The qualifier in NM101 has been changed to no longer use the generic value ZZ Mutually Defined) in favor of the more specific value PE (Payee).

  3. The Pay-to Plan secondary REF segments have been "flattened". There are now two distinct segments, each with a repeat count of one. The segments are the Pay-to Plan Secondary Identification segment and the Pay-to Plan Tax Identification segment.

Loop ID-2000B

  1. The Subscriber / Patient hierarchy has changed to follow the same principles used in other HIPAA transactions, such as Eligibility Request/Response and Claim Status Inquiry/Response. The basic principles are as follows:

    • If the patient has a unique identifier assigned by the destination payer in Loop ID-2010BB, then the patient is considered to be the subscriber and is sent in the Subscriber loop (Loop ID-2000B) and the Patient Hierarchical Level (Loop ID-2000C) is not used.

    • If the patient is different than the subscriber and the patient does not have a unique identifier, then the subscriber information is sent in Loop ID- 2000B and the patient information is sent in Loop ID-2000C.

  2. There are new values for the Payer Responsibility Sequence Number Code (SBR01). The new values support sequencing of up to 11 payers. The new values also include a value of U (Unknown) to be used in certain payer-to-payer COB situations.

  3. The Situational Rule for the Subscriber Group Name (SBR04) has changed.

  4. The list of valid values for the Claim Filing Indicator Code (SBR09) has changed.

Loop ID-2010BA

  1. The Subscriber Primary Identifier and its qualifier (NM108 and NM109) remain Situational (NM108 and NM109 were Required in 005010X222). The elements are still required when NM102 of the Subscriber Name segment has a value of '1' (Person) but are not used when NM102 has a value of '2' (Non-Person). NM102 could indicate a Non-Person for Worker's Compensation claims.

  2. The Situational Rule for the Subscriber Address segments (N3 and N4) has changed.

  3. The usage for the Subscriber City, State and ZIP Code (N4) segment remains Situational. (This N4 segment had been Required in 005010X222.)

  4. The Situational Rule for the Subscriber Demographic Information segment (DMG) has changed.

  5. The Repeat Count for the Subscriber Secondary Identification (REF) segment has decreased to one. The only permitted value for the Subscriber Secondary Identification (REF) segment is the subscriber's Social Security Number (qualifier SY).

  6. Added Property and Casualty Subscriber Contact Information (PER) segment.

Loop ID-2010BB

  1. By adding an informational note to the Payer Name segment, the usage of this segment and loop now explicitly supports designating a repricer as the destination payer.

  2. The element notes for the qualifier for the Payer Identifier (NM108/NM109) now contain specific instructions on when to use the HIPAA National Plan ID (value XV) vs. when to use the generic Payer Identifier (value PI).

  3. The usage for the Payer City, State and ZIP Code (N4) segment remains Situational. (This N4 segment had been Required in 005010X222.)

  4. Loop ID-2010BB (Payer Name) now contains the Billing Provider Secondary Information (REF) segment. This new segment contains provider identifiers that were formerly sent in the Billing Provider loop.

  5. Loop ID-2010BC (Credit/Debit Card Holder Name) has been deleted.

Loop ID-2000C

  1. The Situational Rule for the Patient Hierarchical Level has changed in support of the revised Subscriber / Patient hierarchy. The loop is required only when the patient is not the subscriber and the patient does not have a unique identifier assigned by the destination payer. In this case, the patient can only be identified when associated with the subscriber.

Loop ID-2010CA

  1. The Patient Primary Identifier and associated qualifier (NM108/NM109) are now Not Used.

  2. The Patient Secondary Identification (REF) segment has been deleted.

  3. A new REF segment (Property and Casualty Patient Identifier) was added to the 2010CA (Patient Name) loop. The Property and Casualty Patient Identifier segment has a usage of Situational.

  4. Added Property and Casualty Patient Contact Information (PER) segment.

Loop ID-2300

  1. The Total Claim Charge Amount (CLM02) now explicitly states that it must be the sum of the service line charge amounts (sum of the SV102's.)

  2. The usage for the Facility Code Qualifier (CLM05-2) has changed from Not Used to Required.

  3. CLM07 has changed from Situational to Required.

  4. The element note for the Provider Accept Assignment Code (CLM07) has changed to be more specific in its usage for Medicare claims and non-Medicare claims. Value P (Patient Refuses to Assign Benefits) has been removed.

  5. A new value has been added to CLM08, the Benefits Assignment Certification Indicator. The new value is W (Not Applicable), which means that the patient has refused to assign benefits to the provider. In the previous version, CLM07 = P carried this message.

  6. The Situational Rule for the Related Causes Information composite (CLM11) has been clarified. Value AP (Another Party Responsible) has been deleted from CLM11-1. Component CLM11-3 of element CLM11 has changed to Not Used.

  7. The Situational Rule for CLM11-4 (Auto Accident State or Province Code) has changed to be more specific.

  8. Combined the Loop ID-2300 Date-Disability Begin and Date-Disability End segments into one segment entitled Date-Disability Dates. This was accomplished by adding qualifiers 314 and 361 to DTP01 along with notes instructing when each of the three qualifiers is to be used. Added notes to DTP02 qualifiers instructing when each of the qualifiers are to be used with respect to the value in DTP01.

  9. Date - Assumed and Relinquished Care Dates (DTP) notes have been expanded to include usage beyond Medicare.

  10. Added Date - Property and Casualty Date of First Contact (DTP) segment.

  11. Added Date - Repricer Received Date (DTP) segment.

  12. Available values in the Attachment Report Type Code (PWK01) have been expanded.

  13. The Attachment Transmission Code (PWK02) has added new value FT (File Transfer) to designate that the attachment is available from an attachment warehouse (vendor).

  14. The Situational Rule for both PWK05 and PWK06 has changed to support PWK02 = FT.

  15. The maximum field length for the Attachment Control Number (PWK06) is now 50 characters.

  16. The Credit / Debit Card - Maximum Amount (AMT) segment has been removed.

  17. The Total Purchased Service Amount (AMT) segment has been deleted.

  18. The Situational Rule for the Service Authorization Exception Code (REF) segment has been clarified.

  19. The Prior Authorization or Referral Number (REF) segment is now two distinct segments: the Referral Number segment; and the Prior Authorization segment. The qualifiers did not change.

  20. The segment notes for the Payer Claim Control Number (REF) segment have been clarified.

  21. The repeat count for the Clinical Laboratory Improvement (CLIA) Number (REF) segment has been reduced to 1.

  22. Claim Identifier for Transmission Intermediaries is the new name for the Claim Identification Number for Clearinghouses and Other Transmission Intermediaries segment. The qualifier (REF01 = D9) did not change.

  23. The situational rule and usage notes for the Care Plan Oversight (REF) segment have been clarified.

  24. The Repriced Claim Number (REF) and the Adjusted Repriced Claim Number (REF) segments have been added to the 2300 loop.

  25. The Situational Rule has been clarified for the File Information (K3) segment. Segment notes explain the process for applying for an exception to be allowed to use the segment.

  26. The qualifier PMT has been deleted from NTE01 of the Claim Note (NTE) segment.

  27. Usage of CR103 of the Ambulance Transport Information (CR1) segment changed from Required to Not Used.

  28. Situational Rule for Ambulance Certification (CRC) segment has been clarified.

  29. Qualifiers 02 and 03 were deleted from CRC03 of the Ambulance Certification (CRC) segment.

  30. The Situational Rule for the EPSDT Referral (CRC) segment was clarified.

  31. Deleted data element note from HI01 of the Health Care Diagnosis Code (HI) segment which states "E codes are Not Used in HI01 except when defined by the claims processor but they may be put in any other HI element using BF qualifier."

  32. The Health Care Diagnosis Code (HI) segment has added an additional qualifier (ABK) to HI01-1 and qualifier ABF to HI02-1 through HI08-1 with extensive usage notes to support ICD-10-CM Diagnosis Codes (if allowed under HIPAA).

  33. Changed HI09, HI10, HI11, and HI12 of the Health Care Diagnosis Code (HI) segment from Not Used to Situational in order to enable reporting up to 12 diagnoses.

  34. Added Anesthesia Related Procedure (HI) segment.

  35. The Situational Rule for the claim-level Claim Pricing / Repricing Information (HCP) segment has been clarified. The Situational Rules for the data elements within the segment have also been clarified.

  36. The Home Health Care Plan Information Loop (Loop ID-2305) has been deleted. This loop included the CR7 and HSD segments.

Loop ID-2310A

  1. The Situational Rule for the claim-level Referring Provider loop has been clarified.

  2. The Referring Provider must be a person. (Loop ID-2310A|NM102 must be a '1'.)

  3. The only identifier allowed in the Referring Provider Name segment (NM108 and NM109) is the National Provider Identifier (NPI). The identifier has a usage of Situational.

  4. The Referring Provider Specialty Information (PRV) segment has been deleted.

  5. The segment repeat for the Referring Provider Secondary Identifier (REF) segment has been reduced to 3.

  6. The list of valid qualifiers for the Referring Provider Secondary Identifier (REF01) now contains only 0B (State License Number), 1G (Provider UPIN Number) and G2 (Provider Commercial Number). The specific values such as 1B (Blue Shield Provider Number), 1D (Medicaid Provider Number) etc. have been removed. In their place, use G2.

Loop ID-2310B

  1. The Situational Rule for the claim-level Rendering Provider loop has been clarified.

  2. The only identifier allowed in the Rendering Provider Name segment (NM108 and NM109) is the National Provider Identifier (NPI). The identifier has a usage of Situational.

  3. The segment repeat for the Referring Provider Secondary Identifier (REF) segment has been reduced to 4.

  4. The list of valid qualifiers for the Rendering Provider Secondary Identifier (Loop ID-2310A | REF01) now contains only 0B (State License Number), 1G (Provider UPIN Number), G2 (Provider Commercial Number) and LU (Location Number). The specific values such as 1B (Blue Shield Provider Number), 1D (Medicaid Provider Number) etc. have been removed. In their place, use G2.

Loop ID-2310C through Loop ID-2310G

  1. Purchased Service Provider Name Loop (Loop ID-2310C in X143) has been deleted. This resulted in the following loop name changes. These changes are listed showing the X143 Loop ID first followed by the Loop ID as named within this implementation.

    • Purchased Service Provider - Loop ID-2310C to Not Used.

    • Service Facility Location Name - Loop ID-2310D moved to Loop ID-2310C

    • Supervising Provider Name - Loop ID-2310E moved to Loop ID-2310D

    • Ambulance Pick-up Location - Loop ID-2310F moved to Loop ID-2310E

    • Ambulance Drop-off Location - Loop ID-2310G moved to Loop ID-2310F

Loop ID-2310C

  1. The segment name for the Service Facility Location is now the Service Facility Location Name.

  2. The Situational Rule for the claim-level Service Facility Location Name loop has been clarified.

  3. The Entity Identifier Code (NM101) in the Service Facility Location Name segment must be '77'. The qualifiers FA (Facility), LI (Independent Lab), and TL (Testing Laboratory) have been deleted.

  4. The only identifier allowed in the Service Facility Location Name segment (NM108 and NM109) is the National Provider Identifier (NPI).

  5. The usage for the Laboratory or Facility Primary Identifier (NM108 and NM109) has changed from Required to Situational.

  6. The Repeat Count for the Service Facility Location Secondary Identification segment is now three.

  7. The list of valid qualifiers for the Service Facility Location Name Secondary Identifier (Loop ID-2310A | REF01) now contains only 0B (State License Number), G2 (Provider Commercial Number) and LU (Location Number). The specific values such as 1B (Blue Shield Provider Number), 1D (Medicaid Provider Number) etc. have been removed. In their place, use G2.

  8. Added Service Facility Contact Information (PER) segment.

Loop ID-2310D

  1. The only identifier allowed in the Supervising Provider Name segment (NM108 and NM109) is the National Provider Identifier (NPI). The identifier has a usage of Situational.

  2. The Repeat Count for the Service Facility Location Secondary Identification segment is now three.

  3. The list of valid qualifiers for the Supervising Provider Secondary Identifier (Loop ID-2310A | REF01) now contains only 0B (State License Number), 1G (Provider UPIN Number), G2 (Provider Commercial Number) and LU (Location Number). The specific values such as 1B (Blue Shield Provider Number), 1D (Medicaid Provider Number) etc. have been removed. In their place, use G2.

Loop ID-2310E

  1. The Ambulance Pick-up Location Name (NM103) element has been changed to Not Used.

Loop ID-2310F

  1. Segment notes for Ambulance Drop-off Location Address (N3) segment (Loop 2310F) were deleted.

  2. Segment notes for Ambulance Drop-off Location City, State, Zip Code (N4) segment (Loop 2310F) were deleted.

Loop ID-2320

  1. There are new values for the Payer Responsibility Sequence Number Code (SBR01). The new values support sequencing of up to 11 payers.

  2. The Situational Rule for the Subscriber Group Name (SBR04) has changed.

  3. The usage of The Insurance Type Code (SBR05) has changed from Required to Situational.

  4. The Insurance Type Code (SBR05) values have been modified to match the Loop ID-2000B SBR05 list.

  5. The list of valid values for the Claim Filing Indicator Code (SBR09) has changed.

  6. The segment notes and Situational Rule for the Claim Adjustment (CAS) segment have been clarified.

  7. The Situational Rules for the various elements in the CAS segment have been clarified.

  8. The COB Allowed Amount (AMT) segment in has been removed.

  9. The COB Patient Responsibility Amount (AMT) segment has been removed.

  10. The COB Discount Amount (AMT) segment has been removed.

  11. The COB Per Day Limit Amount (AMT) segment has been removed.

  12. The COB Patient Paid Amount (AMT) segment has been removed.

  13. The COB Tax Amount (AMT) segment has been removed.

  14. The COB Total Claim Before Taxes Amount (AMT) segment has been removed.

  15. The COB Total Non-Covered Amount (AMT) segment has been added.

  16. 2The Remaining Patient Liability (AMT) segment has been added.

  17. The Subscriber Demographic Information (DMG) segment has been removed.

  18. A new value has been added to OI03 (Benefits Assignment Certification Indicator). The new value is W (Not Applicable), which means that the patient has refused to assign benefits to the provider.

  19. The Situational Rule for the Outpatient Adjudication Information (MOA) segment has been clarified.

Loop ID-2330A

  1. The Segment Notes for the Other Subscriber have been clarified.

  2. The Other Subscriber Primary Identifier and its qualifier (NM108 and NM109) are now required.

  3. The usage for the Other Subscriber City, State and ZIP Code (N4) segment remains Situational. (This N4 segment had been Required in 005010X222.)

  4. The Repeat Count for the Subscriber Secondary Identification (REF) segment has reduced to one.

  5. The only permitted value for the Subscriber Secondary Identification (REF) segment is the subscriber's Social Security Number (qualifier SY).

Loop ID-2330B

  1. The element notes for the Other Payer Primary Identifier (Loop ID-2330B | NM108-NM109) contain instructions for using the HIPAA National Plan ID, when issued.

  2. The usage for the Other Payer City, State and ZIP Code (N4) segment remains Situational. (This N4 segment had been Required in 005010X222.)

  3. The Other Payer Contact Information (PER) segment has been removed.

  4. The Claim Adjudication Date (DTP) segment has been renamed to Claim Check or Remittance Date.

  5. Several qualifiers have been removed from the Other Payer Secondary Identifier (REF) segment and one new qualifier has been added.

  6. The Other Payer Prior Authorization or Referral Number (REF) segment is now two distinct segments: the Other Payer Referral Number segment; and the Other Payer Prior Authorization segment. The qualifiers did not change.

  7. The segment and element notes in the Other Payer Claim Adjustment Indicator (REF) segment have been clarified.

  8. The Other Payer Claim Control Number (REF) segment has been added.

Loop ID-2330C through Loop ID-2330H

  1. The Other Payer Patient Information loop (formerly Loop ID-2330C) has been removed. If the payer in Loop ID-2330B has assigned a unique identifier to the patient, then the patient must be sent in the Other Subscriber loop. The deletion of the Other Payer Patient Information Loop resulted in the following loop name changes. These changes are listed showing the X143 Loop ID first followed by the Loop ID as named within this implementation.

    • Other Payer Patient Information - Loop ID-2330C to Not Used.

    • Other Payer Referring Provider - Loop ID-2330D to Loop ID-2330C

    • Other Payer Rendering Provider - Loop ID-2330E to Loop ID-2330D

    • Other Payer Purchased Service Provider - Loop ID-2330F to Not Used

    • Other Payer Service Facility Location - Loop ID-2330G to Loop ID-2330E

    • Other Payer Supervising Provider - Loop ID-2330H to Loop ID-2330F

Loop ID-2330C

  1. The list of valid qualifiers for the Other Payer Referring Provider Secondary Identifier (REF01) now contains only 0B (State License Number), 1G (Provider UPIN Number) and G2 (Provider Commercial Number). The specific values such as 1B (Blue Shield Provider Number), 1D (Medicaid Provider Number) etc. have been removed. In their place, use G2.

Loop ID-2330D

  1. The list of valid qualifiers for the Other Payer Rendering Provider Secondary Identifier (REF01) now contains only 0B (State License Number), 1G (Provider UPIN Number), G2 (Provider Commercial Number) and LU (Location Number). The specific values such as 1B (Blue Shield Provider Number), 1D (Medicaid Provider Number) etc. have been removed. In their place, use G2.

Loop ID-2330E

  1. The Entity Identifier Code (NM101) in the Other Payer Service Facility Location Name segment must be '77'. The qualifiers FA (Facility), LI (Independent Lab), and TL (Testing Laboratory) have been deleted.

  2. The list of valid qualifiers for the Other Payer Service Facility Location Secondary Identification (REF01) now contains only 0B (State License Number), G2 (Provider Commercial Number) and LU (Location Number). The specific values such as 1B (Blue Shield Provider Number), 1D (Medicaid Provider Number) etc. have been removed. In their place, use G2.

Loop ID-2330F

  1. Deleted Other Payer Purchased Service Provider Loop. See Loop ID-2330C through Loop ID-2330H section of the change log for Loop renaming detail.

  2. The list of valid qualifiers for the Other Payer Supervising Provider Secondary Identification (REF01) now contains only 0B (State License Number), 1G (Provider UPIN Number), G2 (Provider Commercial Number) and LU (Location Number). The specific values such as 1B (Blue Shield Provider Number), 1D (Medicaid Provider Number) etc. have been removed. In their place, use G2.

Loop ID-2330G

  1. Added Other Payer Billing Provider Loop

Loop ID-2400

  1. The Service Line (LX) segment has been renamed to Service Line Number.

  2. Notes added to SV101-1 qualifiers ER and WK of the Professional Service (SV1) segment to clarify usage.

  3. The usage of the Procedure Description (SV101-7) has been clarified.

  4. The usage of the Line Item Charge Amount (SV102) has been clarified. The amount is inclusive of the provider's base charge and any applicable tax and/or postage claimed amounts reported in the service line's relative (AMT) segments.

  5. The usage of the Composite Diagnosis Pointer (SV107) has been changed from Situational to Required.

  6. Component note changed in SV107-1 to indicate the valid values have changed from 1 through 8 to 1 through 12.

  7. The usage of the EPSDT Indicator (SV111) has been clarified.

  8. Added the Line Supplemental Information (PWK) segment.

  9. Usage of the Ambulance Transport Code (CR103) has been changed from Required to Not Used.

  10. The Spinal Manipulation Service Information (CR2) segment was removed.

  11. The Home Oxygen Therapy Information (CR5) segment was removed.

  12. Situational Rule of the Ambulance Certification (CRC) segment was clarified.

  13. CRC03 Condition Codes 02 (Patient was bed confined before the ambulance service), 03 (Patient was bed confined after the ambulance service), and 60 (Transportation was to the nearest facility) have been removed from the Ambulance Certification (CRC) segment.

  14. The usage of the Date Last Seen (DTP) segment has been clarified.

  15. The Date - Test (DTP) segment has been renamed to Date - Test Date.

  16. The Date - Oxygen Saturation/Arterial Blood Gas Test (DTP) segment has been removed.

  17. The usage of the Date-Last X-Ray Date (DTP) segment has been clarified.

  18. The Date - Acute Manifestation (DTP) segment has been removed.

  19. The usage of the Date - Initial Treatment Date (DTP) segment has been clarified.

  20. Added the Obstetric Anesthesia Additional Units (QTY) segment.

  21. The codes for Gas Test Rate (GRA) and Oxygen (ZO) have been removed from the Test Result Measurement Qualifiers (MEA02).

  22. Segment usage notes pertaining to qualifiers "GRA" and "ZO" of the Test Result (MEA) segment have been removed.

  23. The Situational Rule for the Contract Information (CN1) segment has been clarified.

  24. The Situational Rules for the Contract Information (CN1) situational data elements have been clarified.

  25. The usage of the Repriced Line Item Reference Number (REF) segment has been clarified.

  26. The usage of the Adjusted Repriced Line Item Reference Number (REF) segment has been clarified.

  27. The (line level) Prior Authorization or Referral Number (REF) segment is now two distinct segments: the Referral Number segment; and the Prior Authorization segment. The qualifiers did not change. Segment repeats changed from 2 to 5.

  28. TR3 note added to the Prior Authorization and Referral Number (REF) segments to indicate that composite REF04 is used when it is necessary to report one or more non-destination payer Prior Authorization Numbers.

  29. The usage of REF04 in the Prior Authorization and Referral Number (REF) segments has been changed from Not Used to Situational. This composite data element is used to identify a non-destination payer. In prior versions, Loop ID-2420G was used for this purpose with limited capacity.

  30. The usage notes for the Line Item Control Number (REF) segment have been clarified.

  31. The reference to "Medicare" has been deleted from the Situational Rule of the Referring Clinical Laboratory Improvement Amendment (CLIA) Facility Identification (REF) segment.

  32. A reference to "federal law or regulations" has been added to the Situational Rule for the Immunization batch Number (REF) segment.

  33. The Universal Product Number (UPN) (REF) segment has been removed.

  34. The usage of the Sales Tax Amount (AMT) segment has been clarified.

  35. The Allowed Amount (AMT) segment has been removed.

  36. The usage of the Postage Claimed Amount (AMT) segment has been clarified.

  37. The Situational Rule has been clarified for the line-item File Information (K3) segment. Segment notes explain the process for applying for an exception to be allowed to use the segment.

  38. The usage of the Line Item Note (NTE) segment has been clarified.

  39. The qualifier PMT (Payment) has been removed from NTE01 of the Line Note (NTE) segment.

  40. The Health care Services Delivery (HSD) segment has been removed.

  41. The usage of the Line Pricing/Repricing Information (HCP) segment has been clarified.

  42. The listed values in Product or Service ID Qualifier (HCP09) have been modified to be in sync with the qualifiers listed in SV101-1.

  43. The value F2 (International Unit) has been removed from the Unit or Basis for Measurement Code (HCP11) element to be in sync with the qualifiers listed in SV103.

Loop ID-2410

  1. The Situational rule for the Drug Identification (LIN) segment has changed. The new rule is as follows:

    "Required when government regulation mandates that prescribed drugs and biologics are reported with NDC numbers.
    OR
    Required when the provider or submitter chooses to report NDC numbers to enhance the claim reporting or adjudication processes.
    OR
    Required when an HHS approved pilot project specifies reporting of Universal Product Number (UPN) by parties registered in the pilot and their trading partners.
    OR
    Required when government regulation mandates that medical and surgical supplies are reported with UPN's.
    If not required by this implementation guide, do not send."

  2. Additional qualifiers EN (EAN/UCC - 13), EO (EAN/UCC - 8), HI (HIBC (Health Care Industry Bar Code) Supplier Labeling Standard Primary Data Message), ON - Customer Order Number, UK (GTIN 14 - digit Data Structure) and UP (UCC -12) were added to Product or Service ID Qualifier (LIN02), as well as a new element note limiting the use of these qualifiers to pilots approved by HHS or when mandated by government regulation.

  3. The name of the National Drug Code (LIN03) data element was changed to National Drug Code or Universal Product Number.

  4. The usage of the Drug Quantity (CTP) segment has been changed from Situational to Required. Notes were deleted.

  5. The name of the Prescription Number (REF) segment has been changed to Prescription or Compound Drug Association Number.

  6. The Situational Rule and TR3 Notes of the Prescription or Compound Drug Association Number (REF) segment have been clarified.

  7. Added the qualifier VY (Link Sequence Number) to the Prescription or Compound Drug Association Number (REF) segment.

Loop ID-2420A

  1. The Situational Rule and usage notes for the Rendering Provider loop have been clarified.

  2. The usage for the Rendering Provider Identifier and its associated qualifier (NM108/NM109) has changed from Required to Situational. The only valid qualifier is XX, which signifies the CMS National Provider Identifier (NPI).

  3. The usage notes for the Rendering Provider Secondary Identification (REF) segment have been clarified.

  4. The list of valid qualifiers for the Rendering Provider Secondary Identifier (REF01) now contains only 0B (State License Number), 1G (Provider UPIN Number), G2 (Provider Commercial Number) and LU (Location Number). The specific values such as 1B (Blue Shield Provider Number), 1D (Medicaid Provider Number) etc. have been removed. In their place, use G2.

  5. The Rendering Provider Secondary Identifier (REF) segment now allows identification of a specific payer (the destination payer named in Loop ID- 2010BB or a specified payer from the Other Payer loop (Loop ID-2330B). If the identifier belongs to the destination payer, then composite REF04 is not used. If the identifier belongs to a specific non-destination payer, then REF04 indicates the specific non-destination payer.

  6. The repeat count for the Rendering Provider Secondary Identifier (REF) segment increased from five to 20.

Loop ID-2420B

  1. The Situational Rule and usage notes for the Purchased Service Provider loop have been clarified.

  2. The usage notes for the Purchased Service Provider Identifier and its associated qualifier (NM108/NM109) have been clarified. The only valid qualifier is XX, which signifies the CMS National Provider Identifier (NPI).

  3. The usage notes for the Purchased Service Provider Secondary Identification (REF) segment have been clarified.

  4. The list of valid qualifiers for the Purchased Service Provider Secondary Identifier (REF01) now contains only 0B (State License Number), 1G (Provider UPIN Number), G2 (Provider Commercial Number) and LU (Location Number). The specific values such as 1B (Blue Shield Provider Number), 1D (Medicaid Provider Number) etc. have been removed. In their place, use G2.

  5. The Purchased Service Provider Secondary Identifier (REF) segment now allows identification of a specific payer (the destination payer named in Loop ID-2010BB or a specified payer from the Other Payer loop (Loop ID- 2330B). If the identifier belongs to the destination payer, then composite REF04 is not used. If the identifier belongs to a specific non-destination payer, then REF04 indicates the specific non-destination payer.

  6. The repeat count for the Purchased Service Provider Secondary Identifier (REF) segment increased from five to 20.

Loop ID-2420C

  1. The segment name for the Service Facility Location is now the Service Facility Location Name.

  2. The Situational Rule for the line-level Service Facility Location Name loop has been clarified.

  3. The Entity Identifier Code (NM101) in the Service Facility Location Name segment must be '77'. The qualifiers FA (Facility), LI (Independent Lab), and TL (Testing Laboratory) have been deleted.

  4. The only identifier allowed in the Service Facility Location Name segment (NM108 and NM109) is the National Provider Identifier (NPI).

  5. The usage for the Laboratory or Facility Primary Identifier (NM108 and NM109) has changed from Required to Situational.

  6. The usage notes for the Service Facility Location Name Provider Secondary Identification (REF) segment have been clarified.

  7. The list of valid qualifiers for the Service Facility Location Name Provider Secondary Identifier (REF01) now contains only 0B (State License Number), 1G (Provider UPIN Number), G2 (Provider Commercial Number) and LU (Location Number). The specific values such as 1B (Blue Shield Provider Number), 1D (Medicaid Provider Number) etc. have been removed. In their place, use G2.

  8. The Service Facility Location Name Provider Secondary Identifier (REF) segment now allows identification of a specific payer (the destination payer named in Loop ID-2010BB or a specified payer from the Other Payer loop (Loop ID-2330B). If the identifier belongs to the destination payer, then composite REF04 is not used. If the identifier belongs to a specific non-destination payer, then REF04 indicates the specific non-destination payer.

  9. The repeat count for the Service Facility Location Name Provider Secondary Identifier (REF) segment increased from five to 20.

Loop ID-2420D

  1. The Situational Rule and usage notes for the Supervising Provider loop have been clarified.

  2. The usage notes for the Supervising Provider Identifier and its associated qualifier (NM108/NM109) have been clarified. The only valid qualifier is XX, which signifies the CMS National Provider Identifier (NPI).

  3. The usage notes for the Supervising Provider Secondary Identification (REF) segment have been clarified.

  4. The list of valid qualifiers for the Supervising Provider Secondary Identifier (REF01) now contains only 0B (State License Number), 1G (Provider UPIN Number), G2 (Provider Commercial Number) and LU (Location Number). The specific values such as 1B (Blue Shield Provider Number), 1D (Medicaid Provider Number) etc. have been removed. In their place, use G2.

  5. The Supervising Provider Secondary Identifier (REF) segment now allows identification of a specific payer (the destination payer named in Loop ID-2010BB or a specified payer from the Other Payer loop (Loop ID-2330B). If the identifier belongs to the destination payer, then composite REF04 is not used. If the identifier belongs to a specific non-destination payer, then REF04 indicates the specific non-destination payer.

  6. The repeat count for the Supervising Provider Secondary Identifier (REF) segment increased from five to 20.

Loop ID-2420E

  1. The Situational Rule and usage notes for the Ordering Provider loop have been clarified.

  2. The usage notes for the Ordering Provider Identifier and its associated qualifier (NM108/NM109) have been clarified. The only valid qualifier is XX, which signifies the CMS National Provider Identifier (NPI).

  3. The usage for the Ordering Provider City, State and ZIP Code (N4) segment remains Situational. (This N4 segment had been Required in 005010X222.)

  4. The usage notes for the Ordering Provider Secondary Identification (REF) segment have been clarified.

  5. The list of valid qualifiers for the Ordering Provider Secondary Identifier (REF01) now contains only 0B (State License Number), 1G (Provider UPIN Number), G2 (Provider Commercial Number) and LU (Location Number). The specific values such as 1B (Blue Shield Provider Number), 1D (Medicaid Provider Number) etc. have been removed. In their place, use G2.

  6. The Ordering Provider Secondary Identifier (REF) segment now allows identification of a specific payer (the destination payer named in Loop ID-2010BB or a specified payer from the Other Payer loop (Loop ID-2330B). If the identifier belongs to the destination payer, then composite REF04 is not used. If the identifier belongs to a specific non-destination payer, then REF04 indicates the specific non-destination payer.

  7. The repeat count for the Ordering Provider Secondary Identifier (REF) segment increased from five to 20.

Loop ID-2420F

  1. The Situational Rule and usage notes for the Referring Provider loop have been clarified.

  2. The usage notes for the Referring Provider Identifier and its associated qualifier (NM108/NM109) have been clarified. The only valid qualifier is XX, which signifies the CMS National Provider Identifier (NPI).

  3. The Referring Provider Specialty Information (PRV) segment has been removed.

  4. The usage notes for the Referring Provider Secondary Identification (REF) segment have been clarified.

  5. The list of valid qualifiers for the Referring Provider Secondary Identifier (REF01) now contains only 0B (State License Number), 1G (Provider UPIN Number), G2 (Provider Commercial Number) and LU (Location Number). The specific values such as 1B (Blue Shield Provider Number), 1D (Medicaid Provider Number) etc. have been removed. In their place, use G2.

  6. The Referring Provider Secondary Identifier (REF) segment now allows identification of a specific payer (the destination payer named in Loop ID- 2010BB or a specified payer from the Other Payer loop (Loop ID-2330B). If the identifier belongs to the destination payer, then composite REF04 is not used. If the identifier belongs to a specific non-destination payer, then REF04 indicates the specific non-destination payer.

  7. The repeat count for the Referring Provider Secondary Identifier (REF) segment increased from five to 20.

Loop ID-2420G through Loop ID-2420I

  1. The Other Payer Prior Authorization or Referral Number (Loop ID-2420G) loop has been removed. This resulted in the following loop name changes. These changes are listed showing the X143 Loop ID first followed by the Loop ID as named within this implementation.

    • Other Payer Prior Authorization or Referral Number - Loop ID-2420G to Not Used.
    • Ambulance Pick-up Location - Loop ID-2420H moved to Loop ID-2420G
    • Ambulance Drop-off Location - Loop ID-2420I moved to Loop ID-2420H

Loop ID-2420H

  1. The Loop Repeat Ambulance Drop-off Location (NM1) segment has been changed from 5 to 1.

Loop ID-2430

  1. The Loop Repeat of the Line Adjudication Information (SVD) segment has been changed from 25 to 15.

  2. The Situational Rule and the usage notes for the Line Item Adjudication loop have been clarified.

  3. Crosswalk references to specific elements in the ASC X12 835 Payment / Remittance Advice transaction have been removed.

  4. SVD01 element note of the Line Adjudication Information (SVD) segment was clarified.

  5. The usage of SVD03-1 codes IV (Home Infusion EDI Coalition (HIEC) Product/ Service Code) and WK (Advanced Billing Concepts (ABC) Codes) have been clarified.

  6. Added SVD03-8 to the Line Adjudication Information (SVD) segment (Loop 2430). The component is Not Used.

  7. Added element note to SVD05 of the Line Adjudication Information (SVD) segment to indicate a maximum length of 8 digits excluding the decimal. When decimal used, maximum digits allowed to the right of decimal is three.

  8. The usage notes for SVD06 Bundled or Unbundled Line Number have been clarified.

  9. The Segment Repeat of the Line Adjustment (CAS) segment has been changed from 99 to 5.

  10. The usage of the Line Adjustment (CAS) segment and some if its elements have been clarified.

  11. The segment name for the DTP segment changed from Line Adjudication Date to the more descriptive Line Check or Remittance Date.

  12. The Remaining Patient Liability (AMT) segment has been added.

Loop ID-2440

  1. The Loop Repeat of the Form Identification Code loop has been changed from 5 to 1.

Section 3 Examples

  1. All examples were revised to contain the new Guide ID (005010X222A2).

Appendix B Nomenclature

  1. In section B.1.1.2.2., blank spaces in the Basic Character Set were replaced with a quote mark (") and apostrophe (').

  2. In section B.1.1.2.3., two additional characters were added: a carat (^) and open single quote mark (').

Appendix C Control Segments

  1. The listed value for element GS08 was changed to contain the new Guide ID (005010X222A2).

  2. The segment example for the Functional Group Header (GS) was changed to contain the new Guide ID (005010X222A2).

D.3. Errata Changes in X222A1

Errata changes appear in yellow highlight. Listed below are the specific changes, their page number location in the original guide, and a link to the change in this document. These changes appear in the X222A1 document.

Section 1.2 - Version Information

Original page 1, paragraph 2

1.4.1.2 Crosswalking COB Data Elements

Original page 7, paragraph subtitle under Business Model

1.4.1.2 Crosswalking COB Data Elements

Original page 15, Example table, Header Strings (both columns)

1.4.3.2.1.1 Transaction Set Header (ST) Segment

Original page 28, paragraph 2, last sentence

Table 2 - Subscriber Detail

Original page 59, Segment Usage, Loops 2010BA & 2010BB, N4 Segment changes to Situational ("S")

Table 2 - Patient Detail

Original page 59, Loop 2010CA, New REF Segment "Property and Casualty Patient Identifier"

Table 2 - Patient Detail

Original page 61, Segment Usage, Loops 2330A & 2330B, N4 Segment changes to Situational ("S")

Table 2 - Patient Detail

Original page 63, Segment Usage, Loop 2420E, N4 Segment changes to Situational ("S")

ST - TRANSACTION SET HEADER

Original page 70, Header Section, ST Segment example

NM1 - SUBSCRIBER NAME

Original pages 122 & 123, Table 2 - Subscriber Detail, Loop 2010B, NM108 & NM109 Data Elements, Change Requirement and add Situational Rule

N4 - SUBSCRIBER CITY, STATE, ZIP CODE

Original page 125, Table 2 - Subscriber Detail, Loop 2010BA, N4 Segment, Change Requirement and add Situational Rule

N4 - PAYER CITY, STATE, ZIP CODE

Original page 136, Table 2 - Subscriber Detail, Loop 2010BB, N4 Segment, Change Requirement and add Situational Rule

REF - PROPERTY AND CASUALTY PATIENT IDENTIFIER

New REF Segment, Table 2 - Patient Detail, Loop 2010CA

N4 - OTHER SUBSCRIBER CITY, STATE, ZIP CODE

Original page 317, Table 2 - Patient Detail, Loop 2330A, N4 Segment, Change Requirement and add Situational Rule

N4 - OTHER PAYER CITY, STATE, ZIP CODE

Original page 323, Table 2 - Patient Detail, Loop 2330B, N4 Segment, Change Requirement and add Situational Rule

LIN - DRUG IDENTIFICATION

Original page 424, Table 2 - Patient Detail, Loop 2410, LIN Segment, Situational Rule

LIN - DRUG IDENTIFICATION

Original page 425, Table 2 - Patient Detail, Loop 2410, LIN02 Data Element, new Codes and note

LIN - DRUG IDENTIFICATION

Original page 425, Table 2 - Patient Detail, Loop 2410, LIN03 Data Element, Implementation Name

N4 - ORDERING PROVIDER CITY, STATE, ZIP CODE

Original page 458, Table 2 - Patient Detail, Loop 2420E, N4 Segment, Change Requirement and add Situational Rule

3.1.1 Example 1 - Commercial Health Insurance

Original page 498, Segment 1 String, ST Example

3.1.1 Example 1 - Commercial Health Insurance

Original page 502, Complete Data String, ST Example

3.1.2 Example 2 - Encounter

Original page 504, Segment 1 String, ST Example

3.1.2 Example 2 - Encounter

Original page 507, Complete Data String, ST Example

3.1.3.1 Example 3.A - Claim from Billing Provider to Payer A

Original page 510, Segment 1 String, ST Example

3.1.3.1 Example 3.A - Claim from Billing Provider to Payer A

Original page 514, Complete Data String, ST Example

3.1.3.2 Example 3.B - Claim from Billing Provider to Payer B

Original page 515, Segment 1 String, ST Example

3.1.3.2 Example 3.B - Claim from Billing Provider to Payer B

Original page 520, Complete Data String, ST Example

3.1.3.3 Example 3.C - Claim from Payer A to Payer B in Payer-to-Payer

Original page 521, Segment 1 String, ST Example

3.1.3.3 Example 3.C - Claim from Payer A to Payer B in Payer-to-Payer

Original page 526, Complete Data String, ST Example

3.1.4 Example 4 - Medicare Secondary Payer Example (COB)

Original page 528, Segment 1 String, ST Example

3.1.4 Example 4 - Medicare Secondary Payer Example (COB)

Original page 532, Complete Data String, ST Example

3.1.5 Example 5 - Ambulance

Original page 533, Segment 1 String, ST Example

3.1.5 Example 5 - Ambulance

Original page 537, Complete Data String, ST Example

3.1.6 Example 6 - Chiropractic Example

Original page 539, Segment 1 String, ST Example

3.1.6 Example 6 - Chiropractic Example

Original page 541, Complete Data String, ST Example

3.1.7 Example 7 - Oxygen

Original page 542, Segment 1 String, ST Example

3.1.7 Example 7 - Oxygen

Original page 548, Complete Data String, ST Example

3.1.8 Example 8 - Wheelchair

Original page 550, Segment 1 String, ST Example

3.1.8 Example 8 - Wheelchair

Original page 554, Complete Data String, ST Example

3.1.9 Example 9 - Anesthesia

Original page 557, Segment 1 String, ST Example

3.1.9 Example 9 - Anesthesia

Original page 559, Complete Data String, ST Example

3.1.10.1 Drug Example 1 - Drug administered in the Physician Office

Original page 561, Segment 1 String, ST Example

3.1.10.1 Drug Example 1 - Drug administered in the Physician Office

Original page 563, Complete Data String, ST Example

3.1.10.2 Drug Example 2 - Home Infusion Therapy Pharmacy (Adjudicated with NDC in Loop 2410)

Original page 566, Segment 1 String, ST Example

3.1.10.2 Drug Example 2 - Home Infusion Therapy Pharmacy (Adjudicated with NDC in Loop 2410)

Original page 571, Complete Data String, ST Example

3.1.10.3 Drug Example 3 - Home Infusion Therapy Pharmacy (Adjudicated with HCPCS in Loop 2400 or NDC in Loop 2410)

Original page 574, Segment 1 String, ST Example

3.1.10.3 Drug Example 3 - Home Infusion Therapy Pharmacy (Adjudicated with HCPCS in Loop 2400 or NDC in Loop 2410)

Original page 580, Complete Data String, ST Example

3.1.11 Example 11 - PPO Repriced Claim

Original page 582, Segment 1 String, ST Example

3.1.11 Example 11 - PPO Repriced Claim

Original page 585, Complete Data String, ST Example

3.1.12 Example 12 - Out of Network Repriced Claim

Original page 587, Segment 1 String, ST Example

3.1.12 Example 12 - Out of Network Repriced Claim

Original page 590, Complete Data String, ST Example

3.2.1 Example 1 - Automobile Accident

Original page 593, Segment 1 String, ST Example

3.2.1 Example 1 - Automobile Accident

Original page 596, Complete Data String, ST Example

GS - FUNCTIONAL GROUP HEADER

Original page C.7, GS Segment example

GS08 - Version / Release / Industry Identifier Code

Original page C.8, GS08 Data Element, Code 005010X222

D.4. Errata Changes in X222A2

Errata changes appear in yellow highlight. Listed below are the specific changes, their page number location in the original guide, and a link to the change in this document. These changes appear in the X222A2 document.

Section 1.2 - Version Information

Original page 1, paragraph 2

1.4.1.2 Crosswalking COB Data Elements

Original page 15, Example table, Header Strings (both columns)

1.4.3.2.1.1 Transaction Set Header (ST) Segment

Original page 28, paragraph 2, last sentence

ST - TRANSACTION SET HEADER

Original page 70, Header Section, ST Segment example

NM1 - PAY-TO PLAN NAME

Original page 107, Table 2 - Billing Provider Detail, Loop 2010AC, NM108 Data Element, Change Note

REF - PAY-TO PLAN SECONDARY IDENTIFICATION

Original page 111, Table 2 - Billing Provider Detail, Loop 2010AC, REF Segment, Change Situational Rule, REF01 - Code 2U, Change Note

SBR - SUBSCRIBER INFORMATION

Original pages 116 & 118, Table 2 - Subscriber Detail, Loop 2000B, SBR09 Data Element, Change Requirement and Remove Situational Rule

NM1 - PAYER NAME

Original page 134, Table 2 - Subscriber Detail, Loop 2010BB, NM108 Data Element, Change Note

REF - PAYER SECONDARY IDENTIFICATION

Original page 138, Table 2 - Subscriber Detail, Loop 2010BB, REF Segment, Change Situational Rule, REF01 - Code 2U, Change Note

SBR - OTHER SUBSCRIBER INFORMATION

Original pages 295 & 298, Table 2 - Patient Detail, Loop 2320, SBR09 Data Element, Change Requirement and Remove Situational Rule

NM1 - OTHER PAYER NAME

Original page 321, Table 2 - Patient Detail, Loop 2330B, NM108 Data Element, Change Note

REF - OTHER PAYER SECONDARY IDENTIFIER

Original page 326, Table 2 - Patient Detail, Loop 2330B, REF Segment, Change Situational Rule, REF01 - Code 2U, Add Note

3.1.1 Example 1 - Commercial Health Insurance

Original page 498, Segment 1 String, ST Example

3.1.1 Example 1 - Commercial Health Insurance

Original page 502, Complete Data String, ST Example

3.1.2 Example 2 - Encounter

Original page 504, Segment 1 String, ST Example

3.1.2 Example 2 - Encounter

Original page 507, Complete Data String, ST Example

3.1.3.1 Example 3.A - Claim from Billing Provider to Payer A

Original page 510, Segment 1 String, ST Example

3.1.3.1 Example 3.A - Claim from Billing Provider to Payer A

Original page 514, Complete Data String, ST Example

3.1.3.2 Example 3.B - Claim from Billing Provider to Payer B

Original page 515, Segment 1 String, ST Example

3.1.3.2 Example 3.B - Claim from Billing Provider to Payer B

Original page 520, Complete Data String, ST Example

3.1.3.3 Example 3.C - Claim from Payer A to Payer B in Payer-to-Payer

Original page 521, Segment 1 String, ST Example

3.1.3.3 Example 3.C - Claim from Payer A to Payer B in Payer-to-Payer

Original page 526, Complete Data String, ST Example

3.1.4 Example 4 - Medicare Secondary Payer Example (COB)

Original page 528, Segment 1 String, ST Example

3.1.4 Example 4 - Medicare Secondary Payer Example (COB)

Original page 532, Complete Data String, ST Example

3.1.5 Example 5 - Ambulance

Original page 533, Segment 1 String, ST Example

3.1.5 Example 5 - Ambulance

Original page 537, Complete Data String, ST Example

3.1.6 Example 6 - Chiropractic Example

Original page 539, Segment 1 String, ST Example

3.1.6 Example 6 - Chiropractic Example

Original page 541, Complete Data String, ST Example

3.1.7 Example 7 - Oxygen

Original page 542, Segment 1 String, ST Example

3.1.7 Example 7 - Oxygen

Original page 548, Complete Data String, ST Example

3.1.8 Example 8 - Wheelchair

Original page 550, Segment 1 String, ST Example

3.1.8 Example 8 - Wheelchair

Original page 554, Complete Data String, ST Example

3.1.9 Example 9 - Anesthesia

Original page 557, Segment 1 String, ST Example

3.1.9 Example 9 - Anesthesia

Original page 559, Complete Data String, ST Example

3.1.10.1 Drug Example 1 - Drug administered in the Physician Office

Original page 561, Segment 1 String, ST Example

3.1.10.1 Drug Example 1 - Drug administered in the Physician Office

Original page 563, Complete Data String, ST Example

3.1.10.2 Drug Example 2 - Home Infusion Therapy Pharmacy (Adjudicated with NDC in Loop 2410)

Original page 566, Segment 1 String, ST Example

3.1.10.2 Drug Example 2 - Home Infusion Therapy Pharmacy (Adjudicated with NDC in Loop 2410)

Original page 571, Complete Data String, ST Example

3.1.10.3 Drug Example 3 - Home Infusion Therapy Pharmacy (Adjudicated with HCPCS in Loop 2400 or NDC in Loop 2410)

Original page 574, Segment 1 String, ST Example

3.1.10.3 Drug Example 3 - Home Infusion Therapy Pharmacy (Adjudicated with HCPCS in Loop 2400 or NDC in Loop 2410)

Original page 580, Complete Data String, ST Example

3.1.11 Example 11 - PPO Repriced Claim

Original page 582, Segment 1 String, ST Example

3.1.11 Example 11 - PPO Repriced Claim

Original page 585, Complete Data String, ST Example

3.1.12 Example 12 - Out of Network Repriced Claim

Original page 587, Segment 1 String, ST Example

3.1.12 Example 12 - Out of Network Repriced Claim

Original page 590, Complete Data String, ST Example

3.2.1 Example 1 - Automobile Accident

Original page 593, Segment 1 String, ST Example

3.2.1 Example 1 - Automobile Accident

Original page 596, Complete Data String, ST Example

GS - FUNCTIONAL GROUP HEADER

Original page C.7, GS Segment example

GS08 - Version / Release / Industry Identifier Code

Original page C.8, GS08 Data Element, Code 005010X222