276 Request 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*HR - 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✱HI✱SENDER CODE✱RECEIVERCODE✱19991231✱0802✱1✱X✱005010X217~
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
HR
Health Care Claim Status Request (276)
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
005010X212
Health Care Claim Status Request and Response

ST*276 - 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✱276✱0001✱005010X212~
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
276
Health Care Claim Status Request
Required
2
329
Transaction Set Control Number
M 1
AN
4/9
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
The Transaction Set Control Numbers in ST02 and SE02 must be identical. The number is assigned by the originator and must be unique within a functional group (GS-GE). For example, start with the number 0001 and increment from there.
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: Version, Release, or Industry Identifier
  1. This element must be populated with the implementation guide Version/Release/Industry Identifier Code 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 utilized at translation time.
CODE
DEFINITION
005010X212
Health Care Claim Status Request and Response

BHT*0010 - BEGINNING OF HIERARCHICAL TRANSACTION

X12 Name:
Beginning of Hierarchical Transaction
X12 Purpose:
To define the business hierarchical structure of the transaction set and identify the business application purpose and reference data, i.e., number, date, and time
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
BHT✱0010✱13✱ABC276XXX✱20050920✱1425~
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
0010
Information Source, Information Receiver, Provider of Service, Subscriber, Dependent
Required
2
353
Transaction Set Purpose Code
M 1
ID
2
Code identifying purpose of transaction set
CODE
DEFINITION
13
Request
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.
Required
4
373
Date
O 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: BHT04 is the date the transaction was created within the business application system.
INDUSTRY NAME: Transaction Set Creation Date
Required
5
337
Time
O 1
TM
4/8
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
SEMANTIC: BHT05 is the time the transaction was created within the business application system.
INDUSTRY NAME: Transaction Set Creation Time
Not Used
6
640
Transaction Type Code
O 1
ID
2

HL - INFORMATION SOURCE 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:
This entity is the payer who has the current status information for the specified claims.
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.
HL01 must begin with "1" within each ST/SE envelope 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.

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.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
NM1✱PR✱2✱ABC INSURANCE✱✱✱✱✱PI✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
PR
Payer
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code 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
CODE
DEFINITION
PI
Payor Identification
Payer identification number established through trading partner agreement.
XV
Centers for Medicare and Medicaid Services PlanID
Use when reporting Health Plan ID (HPID) or Other Entity Identifier (OEID).
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

HL - INFORMATION RECEIVER 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:
This entity expects a response from the Information Source. See Section 1.4.1 Transaction Participants for more information on the Information Receiver.
TR3 Example:
HL✱2✱1✱21✱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.
HL01 must be incremented by one each time an HL is used within each ST/SE envelope. 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
21
Information Receiver
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.

NM1*41 - INFORMATION 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.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
NM1✱41✱2✱XYZ SERVICE✱✱✱✱✱46✱A222222221~
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
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 the identifier in NM109 is not sufficient to identify the Information Receiver. If not required by this implementation guide, may be provided at sender's discretion, but cannot be required by the receiver.
INDUSTRY NAME: Information Receiver Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when the value in NM102 = "1" and the person has a first name that is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Information Receiver First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when NM102 = 1 and the person has a middle name that is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Information Receiver Middle Name
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: Information Receiver Identification Number
The ETIN is established through Trading Partner agreement.
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 - SERVICE PROVIDER LEVEL

X12 Name:
Hierarchical Level
X12 Purpose:
To identify dependencies among and the content of hierarchically related groups of data segments
X12 Comments:
  1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
  2. The HL segment defines a top-down/left-right ordered structure.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
This entity delivered the health care service. See Section 1.4.1 Transaction Participants for more information on the Provider.
TR3 Example:
HL✱3✱2✱19✱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.
HL01 must be incremented by one each time an HL is used within each ST/SE envelope. 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
19
Provider of Service
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.

NM1*1P - 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.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
  1. Provider of Service is generic in that this could be the entity that originally submitted the claim (Billing Provider) or may be the entity that provided or participated in some aspect of the health care (Rendering Provider). The provider identified facilitates identification of the claim within a payer's system.
  2. During the transition to NPI, for those health care providers covered under the NPI mandate, two iterations of the 2100C Loop may be sent to accommodate reporting dual provider identification numbers (NPI and Legacy). When two iterations are reported, the NPI number will be in the iteration where the NM108 qualifier will be 'XX' and the legacy number will be in the iteration where the NM108 qualifier will be either 'SV' or 'FI'.
  3. After the transition to NPI, for those health care providers covered under the NPI mandate, only one iteration of the 2100C loop must be sent with the NPI reported in the NM109 and NM108=XX.
TR3 Example:
NM1✱1P✱2✱HOME MEDICAL✱✱✱✱✱XX✱1666666666~
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
1P
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
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 the identifier in NM109 is not sufficient to identify the Provider. If not required by this implementation guide, may be provided at sender's discretion, but cannot be required by the receiver.
INDUSTRY NAME: Provider Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when the value in NM102 = "1" and the person has a first name that is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Provider First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when NM102 = 1 and the person has a middle name that is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Provider 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 and the person has a name suffix that is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Provider 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
FI
Federal Taxpayer's Identification Number
SV
Service Provider Number
XX
Centers for Medicare and Medicaid Services National Provider Identifier
Required value when the National Provider ID is mandated for use and the provider is a covered health care provider under the mandate. Otherwise, one of the other listed codes must be used.
CODE SOURCE 537: Centers for Medicare and Medicaid Services National Provider Identifier
Required
9
67
Identification Code
O 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
INDUSTRY NAME: 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

HL - SUBSCRIBER LEVEL

X12 Name:
Hierarchical Level
X12 Purpose:
To identify dependencies among and the content of hierarchically related groups of data segments
X12 Comments:
  1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
  2. The HL segment defines a top-down/left-right ordered structure.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
  1. When the patient is the subscriber or a dependent with a unique identification number, the claim status request information is reflected in the 2200D Loop under the Subscriber HL, 2000D Loop (HL03 = 22). The Dependent HL, 2000E Loop is not used. See Section 1.4.1.1 for more information on defining the patient.
  2. When requesting and responding to claim status for both a subscriber and a dependent of that subscriber, the Subscriber HL Loop 2000D must be followed by the subscriber's claim status data, Loop 2200D. In this instance, HL04=0 would be used. Then the Subscriber HL Loop 2000D must be repeated prior to the dependent HL Loop 2000E and their corresponding claim status data, Loop 2200E. In this instance, HL04=1 would be used. See Section 1.4.2.3 for an example of this structure.
TR3 Example:
HL✱4✱3✱22✱0~ or HL✱4✱3✱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.
HL01 must be incremented by one each time an HL is used within each ST/SE envelope. 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.
CODE
DEFINITION
0
No Subordinate HL Segment in This Hierarchical Structure.
Required when there are no dependent claim status requests for this subscriber.
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.
Required when there are dependent claim status requests for this subscriber.

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.
X12 Set Notes:
NOTE: The DMG segment may only appear at the Subscriber (HL03=22) or Dependent (HL03=23) level.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the patient is the subscriber or a dependent with a unique identification number. If not required by this implementation guide, do not send.
TR3 Example:
DMG✱D8✱19330706✱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
Situational
3
1068
Gender Code
O 1
ID
1
Code indicating the sex of the individual
SITUATIONAL RULE: Required when available from the Information Receiver. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Gender Code
CODE
DEFINITION
F
Female
M
Male
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

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.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
NM1✱IL✱1✱SMITH✱ROBERT✱✱✱✱MI✱9876543210~
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
Use the value "2" in an employer-subscriber situation, such as Worker's Compensation.
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 the value in NM102 = "1" and the person has a first name that is known. 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 and the person has a middle name that is known. 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 and the person has a name suffix that is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber 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
24
Employer's Identification Number
This code may be used in conjunction with a workers compensation claim.
II
Standard Unique Health Identifier for each Individual in the United States
Required if the HIPAA Individual Patient Identifier is mandated for use. If not required, use one of the other values.
MI
Member Identification Number
Required
9
67
Identification Code
O 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
INDUSTRY NAME: Subscriber 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

TRN*1 - CLAIM STATUS TRACKING NUMBER

X12 Name:
Trace
X12 Purpose:
To uniquely identify a transaction to an application
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when the patient is the subscriber or a dependent with a unique identification number. If not required by this implementation guide, do not send.
TR3 Notes:
  1. This segment conveys a unique trace or reference number for each 2200D loop. This number will be returned in the 277 response.
  2. When the patient is not the subscriber or a dependent with a unique identification number, the Loop 2200E TRN and subsequent segments will be used to reflect the claim status information.
TR3 Example:
TRN✱1✱1722634842~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
481
Trace Type Code
M 1
ID
1/2
Code identifying which transaction is being referenced
CODE
DEFINITION
1
Current Transaction Trace Numbers
Required
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
SEMANTIC: TRN02 provides unique identification for the transaction.
INDUSTRY NAME: Current Transaction Trace Number
Not Used
3
509
Originating Company Identifier
O 1
AN
10
Not Used
4
127
Reference Identification
O 1
AN
1/50

REF*1K - 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:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the Information Receiver knows the payer assigned number and intends the search criteria be narrowed to a specific claim. If not required by this implementation guide, do not send.
TR3 Notes:
This is the payer's assigned control number, also known as, Internal Control Number (ICN), Document Control Number (DCN), or Claim Control Number (CCN).
TR3 Example:
REF✱1K✱9918046987~
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
1K
Payor's 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: Payer Claim Control Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*BLT - INSTITUTIONAL BILL TYPE 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 needed to refine the search criteria on Institutional claims. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
TR3 Example:
REF✱BLT✱111~
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
BLT
Billing Type
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: Bill Type Identifier
Concatenate the 837I CLM05-1 (Facility Type Code) and CLM05-3 (Claim Frequency Code) values.
Code Source 236: Uniform Billing Claim Form Bill Type
Code Source 235: Claim Frequency Type Code
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*LU - APPLICATION OR LOCATION SYSTEM IDENTIFIER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the application or location system identifier is known. If not required by this implementation guide, do not send.
TR3 Notes:
This identifier will be provided to the Information Receiver by the Information Source through a companion document or other trading partner document. If a payer has multiple adjudication systems processing the same type of claim (e.g. professional or institutional), this identifier can be used to improve status routing and response time.
TR3 Example:
REF✱LU✱SYS5963~
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
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: Application or Location System Identifier
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*6P - GROUP NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the patient has a group number and the number is known by the Information Receiver. If not required by this implementation guide, do not send.
TR3 Example:
REF✱6P✱GRP123~
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
6P
Group 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: Group Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*EJ - PATIENT 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:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the Patient Control Number has been assigned by the service provider. If not required by this implementation guide, do not send.
TR3 Notes:
The maximum number of characters supported for the Patient Control Number is '20'.
TR3 Example:
REF✱EJ✱PT12345~
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
EJ
Patient Account 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: Patient Control Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*XZ - PHARMACY PRESCRIPTION NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the Pharmacy Prescription Number is needed to refine the search criteria for pharmacy claims. If not required by this implementation guide, do not send.
TR3 Example:
REF✱XZ✱1234567~
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
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: Pharmacy Prescription Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*D9 - CLAIM IDENTIFICATION NUMBER FOR CLEARINGHOUSES AND OTHER 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:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when a Clearinghouse or other transmission intermediary needs to attach their own unique claim number. If not required by this implementation guide, do not send.
TR3 Example:
REF✱D9✱20041513010001~
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
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: Clearinghouse Trace Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

AMT*T3 - CLAIM SUBMITTED CHARGES

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 needed to refine the search criteria for a specific claim. If not required by this implementation guide, do not send.
TR3 Notes:
Not all payer systems retain the original submitted charges. Charges are sometimes changed during processing.
TR3 Example:
AMT✱T3✱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
T3
Total Submitted Charges
Required
2
782
Monetary Amount
M 1
R
1/18
Monetary amount
INDUSTRY NAME: Total Claim Charge Amount
Not Used
3
478
Credit/Debit Flag Code
O 1
ID
1

DTP*472 - CLAIM 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:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required for institutional claims or for professional and dental claims when the service date (Loop 2210) is not used. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
TR3 Notes:
For professional claims, this date is derived from the service level dates.
TR3 Example:
DTP✱472✱RD8✱20050401-20050402~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
472
Service
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
RD8
Range of Dates Expressed in Format CCYYMMDD-CCYYMMDD
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.
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: Claim Service Period

SVC - SERVICE LINE INFORMATION

X12 Name:
Service Information
X12 Purpose:
To supply payment and control information to a provider for a particular service
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when requesting status for Service Lines. If not required by this implementation guide, do not send.
TR3 Notes:
For Institutional claims, when both an NUBC revenue code and a HCPCS or HIPPS code are reported, the HCPCS or HIPPS code is reported in SVC01-2 and the revenue code is reported in SVC04. When only a revenue code is used, it is reported in SVC01-2.
TR3 Example:
SVC✱HC:C8900:AA✱800✱✱0111✱✱✱12~orSVC✱NU:0710✱50✱✱✱✱✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
C003
Composite Medical Procedure Identifier
M 1
To identify a medical procedure by its standardized codes and applicable modifiers
SEMANTIC: SVC01 is the medical procedure upon which adjudication is based.
COMMENT: For Medicare Part A claims, SVC01 would be the Health Care Financing Administration (HCFA) Common Procedural Coding System (HCPCS) Code (see code source 130) and SVC04 would be the Revenue Code (see code source 132).
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.
SVC01-2 will contain the procedure code of the adjudicated claim. If the adjudicated code is not known then SVC01-2 will contain the original submitted procedure code.
Required
1-1
235
Product/Service ID Qualifier
M 1
ID
2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
INDUSTRY NAME: Product or Service ID Qualifier
CODE
DEFINITION
AD
American Dental Association Codes
CODE SOURCE 135: American Dental Association
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 CPT codes of the American Medical Association are also level 1 HCPCS codes, the CPT codes are reported under the code HC.
CODE SOURCE 130: Healthcare Common Procedural Coding System
HP
Health Insurance Prospective Payment System (HIPPS) Skilled Nursing Facility Rate Code
CODE SOURCE 716: Health Insurance Prospective Payment System (HIPPS) Rate Code for Skilled Nursing Facilities
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 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
N4
National Drug Code in 5-4-2 Format
CODE SOURCE 240: National Drug Code by Format
NU
National Uniform Billing Committee (NUBC) UB92 Codes
This code is the NUBC Revenue Code.
CODE SOURCE 132: National Uniform Billing Committee (NUBC) Codes
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
If the value in SVC01-1 is "NU", then this is an NUBC Revenue Code. If the revenue code is present here, then SVC04 is not used.
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 modifiers have been applied to the adjudicated or submitted procedure code reported in SVC01-2. 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 modifiers have been applied to the adjudicated or submitted procedure code reported in SVC01-2. 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 modifiers have been applied to the adjudicated or submitted procedure code reported in SVC01-2. 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 modifiers have been applied to the adjudicated or submitted procedure code reported in SVC01-2. If not required by this implementation guide, do not send.
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
782
Monetary Amount
M 1
R
1/18
Monetary amount
SEMANTIC: SVC02 is the submitted service charge.
INDUSTRY NAME: Line Item Charge Amount
This amount is the original submitted charge.
Not Used
3
782
Monetary Amount
O 1
R
1/18
Situational
4
234
Product/Service ID
O 1
AN
1/48
Identifying number for a product or service
SEMANTIC: SVC04 is the National Uniform Billing Committee Revenue Code.
SITUATIONAL RULE: Required on institutional claims when an NUBC revenue code needs to be reported in addition to a HCPCS or HIPPS code reported in SVC01-2. If not required by this implementation guide, do not send.
INDUSTRY NAME: Revenue Code
Not Used
5
380
Quantity
O 1
R
1/15
Not Used
6
C003
Composite Medical Procedure Identifier
O 1
Required
7
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: SVC07 is the original submitted units of service.
INDUSTRY NAME: Units of Service Count

REF*FJ - SERVICE LINE ITEM 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 needed to refine the search criteria for a specific service line. If not required by this implementation guide, do not send.
TR3 Example:
REF✱FJ✱6042201~
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
FJ
Line Item 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
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

DTP*472 - SERVICE LINE 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✱472✱RD8✱20050401-20050402~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
472
Service
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
RD8
Range of Dates Expressed in Format CCYYMMDD-CCYYMMDD
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.
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 Line Date

HL - DEPENDENT 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 who does not have a unique identification number. If not required by this implementation guide, do not send.
TR3 Notes:
When the patient is the dependent, the claim status request information is reflected in the 2200E Loop under the Dependent HL, 2000E Loop (HL03 = 23). See Section 1.4.1.1 for more information on defining the patient.
TR3 Example:
HL✱5✱4✱23~
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.
HL01 must be incremented by one each time an HL is used within each ST/SE envelope. 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
23
Dependent
Not Used
4
736
Hierarchical Child Code
O 1
ID
1

DMG*D8 - DEPENDENT 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.
X12 Set Notes:
NOTE: The DMG segment may only appear at the Subscriber (HL03=22) or Dependent (HL03=23) level.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
DMG✱D8✱20010706✱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
Situational
3
1068
Gender Code
O 1
ID
1
Code indicating the sex of the individual
SITUATIONAL RULE: Required when available from the Information Receiver. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Gender Code
CODE
DEFINITION
F
Female
M
Male
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

NM1*QC - DEPENDENT 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.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
NM1✱QC✱1✱SMITH✱JOSEPH~
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 that is known. 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 person has a middle name that is known. 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 person has a name suffix that is known. 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

TRN*1 - CLAIM STATUS TRACKING NUMBER

X12 Name:
Trace
X12 Purpose:
To uniquely identify a transaction to an application
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
This segment conveys a unique trace or reference for each 2200E Loop. This number will be returned in the 277 response.
TR3 Example:
TRN✱1✱1722634842~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
481
Trace Type Code
M 1
ID
1/2
Code identifying which transaction is being referenced
CODE
DEFINITION
1
Current Transaction Trace Numbers
Required
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
SEMANTIC: TRN02 provides unique identification for the transaction.
INDUSTRY NAME: Current Transaction Trace Number
Not Used
3
509
Originating Company Identifier
O 1
AN
10
Not Used
4
127
Reference Identification
O 1
AN
1/50

REF*1K - 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 the Information Receiver knows the payer assigned number and intends the search criteria be narrowed to a specific claim. If not required by this implementation guide, do not send.
TR3 Notes:
This is the payer's assigned control number, also known as, Internal Control Number (ICN), Document Control Number (DCN), or Claim Control Number (CCN).
TR3 Example:
REF✱1K✱9918046987~
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
1K
Payor's 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: Payer Claim Control Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*BLT - INSTITUTIONAL BILL TYPE 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 needed to refine the search criteria on Institutional claims. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
TR3 Example:
REF✱BLT✱111~
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
BLT
Billing Type
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: Bill Type Identifier
Concatenate the 837I CLM05-1 (Facility Type Code) and CLM05-3 (Claim Frequency Code) values.
Code Source 236: Uniform Billing Claim Form Bill Type
Code Source 235: Claim Frequency Type Code
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*LU - APPLICATION OR LOCATION SYSTEM 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 the application or location system identifier is known. If not required by this implementation guide, do not send.
TR3 Notes:
This identifier will be provided to the Information Receiver by the Information Source through a companion document or other trading partner document. If a payer has multiple adjudication systems processing the same type of claim (e.g. professional or institutional), this identifier can be used to improve status routing and response time.
TR3 Example:
REF✱LU✱SYS5963~
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
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: Application or Location System Identifier
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*6P - GROUP 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 patient has a group number and the number is known by the Information Receiver. If not required by this implementation guide, do not send.
TR3 Example:
REF✱6P✱GRP123~
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
6P
Group 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: Group Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*EJ - PATIENT 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 Patient Control Number has been assigned by the service provider. If not required by this implementation guide, do not send.
TR3 Notes:
The maximum number of characters supported for the Patient Control Number is `20'.
TR3 Example:
REF✱EJ✱PT12345~
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
EJ
Patient Account 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: Patient Control Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*XZ - PHARMACY PRESCRIPTION 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 Pharmacy Prescription Number is needed to refine the search criteria for pharmacy claims. If not required by this implementation guide, do not send.
TR3 Example:
REF✱XZ✱1234567~
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
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: Pharmacy Prescription Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*D9 - CLAIM IDENTIFICATION NUMBER FOR CLEARINGHOUSES AND OTHER 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 a Clearinghouse or other transmission intermediary needs to attach their own unique claim number. If not required by this implementation guide, do not send.
TR3 Example:
REF✱D9✱20041513010001~
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
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: Clearinghouse Trace Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

AMT*T3 - CLAIM SUBMITTED CHARGES

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 needed to refine the search criteria for a specific claim. If not required by this implementation guide, do not send.
TR3 Notes:
Not all payer systems retain the original submitted charges. Charges are sometimes changed during processing.
TR3 Example:
AMT✱T3✱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
T3
Total Submitted Charges
Required
2
782
Monetary Amount
M 1
R
1/18
Monetary amount
INDUSTRY NAME: Total Claim Charge Amount
Not Used
3
478
Credit/Debit Flag Code
O 1
ID
1

DTP*472 - CLAIM SERVICE DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required for institutional claims or for professional and dental claims when the service date (Loop 2210) is not used. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
TR3 Notes:
For professional claims, this date is derived from the service level dates.
TR3 Example:
DTP✱472✱RD8✱20050401-20050402~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
472
Service
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
RD8
Range of Dates Expressed in Format CCYYMMDD-CCYYMMDD
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.
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: Claim Service Period

SVC - SERVICE LINE INFORMATION

X12 Name:
Service Information
X12 Purpose:
To supply payment and control information to a provider for a particular service
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when requesting status for Service Lines. If not required by this implementation guide, do not send.
TR3 Notes:
For Institutional claims, when both an NUBC revenue code and a HCPCS or HIPPS code are reported, the HCPCS or HIPPS code is reported in SVC01-2 and the revenue code is reported in SVC04. When only a revenue code is used, it is reported in SVC01-2.
TR3 Example:
SVC✱HC:C8900:AA✱800✱✱0111✱✱✱12~orSVC✱NU:0710✱50✱✱✱✱✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
C003
Composite Medical Procedure Identifier
M 1
To identify a medical procedure by its standardized codes and applicable modifiers
SEMANTIC: SVC01 is the medical procedure upon which adjudication is based.
COMMENT: For Medicare Part A claims, SVC01 would be the Health Care Financing Administration (HCFA) Common Procedural Coding System (HCPCS) Code (see code source 130) and SVC04 would be the Revenue Code (see code source 132).
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.
SVC01-2 will contain the procedure code of the adjudicated claim. If the adjudicated code is not known then SVC01-2 will contain the original submitted procedure code.
Required
1-1
235
Product/Service ID Qualifier
M 1
ID
2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
INDUSTRY NAME: Product or Service ID Qualifier
CODE
DEFINITION
AD
American Dental Association Codes
CODE SOURCE 135: American Dental Association
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 CPT codes of the American Medical Association are also level 1 HCPCS codes, the CPT codes are reported under the code HC.
CODE SOURCE 130: Healthcare Common Procedural Coding System
HP
Health Insurance Prospective Payment System (HIPPS) Skilled Nursing Facility Rate Code
CODE SOURCE 716: Health Insurance Prospective Payment System (HIPPS) Rate Code for Skilled Nursing Facilities
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 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
N4
National Drug Code in 5-4-2 Format
CODE SOURCE 240: National Drug Code by Format
NU
National Uniform Billing Committee (NUBC) UB92 Codes
This code is the NUBC Revenue Code.
CODE SOURCE 132: National Uniform Billing Committee (NUBC) Codes
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
If the value in SVC01-1 is "NU", then this is an NUBC Revenue Code. If the revenue code is present here, then SVC04 is not used.
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 modifiers have been applied to the adjudicated or submitted procedure code reported in SVC01-2. 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 modifiers have been applied to the adjudicated or submitted procedure code reported in SVC01-2. 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 modifiers have been applied to the adjudicated or submitted procedure code reported in SVC01-2. 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 modifiers have been applied to the adjudicated or submitted procedure code reported in SVC01-2. If not required by this implementation guide, do not send.
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
782
Monetary Amount
M 1
R
1/18
Monetary amount
SEMANTIC: SVC02 is the submitted service charge.
INDUSTRY NAME: Line Item Charge Amount
This amount is the original submitted charge.
Not Used
3
782
Monetary Amount
O 1
R
1/18
Situational
4
234
Product/Service ID
O 1
AN
1/48
Identifying number for a product or service
SEMANTIC: SVC04 is the National Uniform Billing Committee Revenue Code.
SITUATIONAL RULE: Required on institutional claims when an NUBC revenue code needs to be reported in addition to a HCPCS or HIPPS code reported in SVC01-2. If not required by this implementation guide, do not send.
INDUSTRY NAME: Revenue Code
Not Used
5
380
Quantity
O 1
R
1/15
Not Used
6
C003
Composite Medical Procedure Identifier
O 1
Required
7
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: SVC07 is the original submitted units of service.
INDUSTRY NAME: Units of Service Count

REF*FJ - SERVICE LINE ITEM 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 needed to refine the search criteria for a specific service line. If not required by this implementation guide, do not send.
TR3 Example:
REF✱FJ✱6042201~
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
FJ
Line Item 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
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

DTP*472 - SERVICE LINE 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✱472✱RD8✱20050401-20050402~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
472
Service
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
RD8
Range of Dates Expressed in Format CCYYMMDD-CCYYMMDD
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.
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 Line Date

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✱34✱0001~
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
Data value in SE02 must be identical to ST02.

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

277 Response 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*HN - 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✱HI✱SENDER CODE✱RECEIVERCODE✱19991231✱0802✱1✱X✱005010X217~
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
HN
Health Care Information Status Notification (277)
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
005010X212
Health Care Claim Status Request and Response

ST*277 - 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✱277✱0001✱005010X212~
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
277
Health Care Information Status Notification
Required
2
329
Transaction Set Control Number
M 1
AN
4/9
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
The Transaction Set Control Numbers in ST02 and SE02 must be identical. The number is assigned by the originator and must be unique within a functional group (GS-GE). For example, start with the number 0001 and increment from there.
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: Version, Release, or Industry Identifier
  1. This element must be populated with the implementation guide Version/Release/Industry Identifier Code 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 utilized at translation time.
CODE
DEFINITION
005010X212
Health Care Claim Status Request and Response

BHT*0010 - BEGINNING OF HIERARCHICAL TRANSACTION

X12 Name:
Beginning of Hierarchical Transaction
X12 Purpose:
To define the business hierarchical structure of the transaction set and identify the business application purpose and reference data, i.e., number, date, and time
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
BHT✱0010✱08✱277XXXX✱20050921✱0430✱DG~
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
0010
Information Source, Information Receiver, Provider of Service, Subscriber, Dependent
Required
2
353
Transaction Set Purpose Code
M 1
ID
2
Code identifying purpose of transaction set
CODE
DEFINITION
08
Status
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
Required
4
373
Date
O 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: BHT04 is the date the transaction was created within the business application system.
INDUSTRY NAME: Transaction Set Creation Date
Required
5
337
Time
O 1
TM
4/8
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
SEMANTIC: BHT05 is the time the transaction was created within the business application system.
INDUSTRY NAME: Transaction Set Creation Time
Required
6
640
Transaction Type Code
O 1
ID
2
Code specifying the type of transaction
CODE
DEFINITION
DG
Response

HL - INFORMATION SOURCE 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:
This entity is the payer who has the current status information for the specified claims.
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.
HL01 must begin with "1" within each ST/SE envelope 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.

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.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
NM1✱PR✱2✱ABC INSURANCE✱✱✱✱✱PI✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
PR
Payer
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code 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
CODE
DEFINITION
PI
Payor Identification
Payer identification number established through trading partner agreement.
XV
Centers for Medicare and Medicaid Services PlanID
Use when reporting Health Plan ID (HPID) or Other Entity Identifier (OEID).
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

PER*IC - PAYER 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 when the payer's contact information is not otherwise specified in a Trading Partner Agreement and the Information Receiver does not know how to contact the payer. If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver.
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 should always include the area code and phone number using the format AAABBBCCCC. A telephone extension, when applicable is reported in the communication number immediately after the telephone number.
TR3 Example:
PER✱IC✱MEDICAL REVIEW DEPARTMENT✱TE✱3135551234✱EX✱6593✱FX✱3135554321~ORPER✱IC✱✱TE✱3135551234✱FX✱3135554321~
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 a specific person or department is the contact for the response. If not required by this implementation guide, do not send.
INDUSTRY NAME: Payer Contact Name
Required
3
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0304
CODE
DEFINITION
ED
Electronic Data Interchange Access Number
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
INDUSTRY NAME: Payer Contact Communication Number
When an extension or additional contact number is required, use PER06.
Situational
5
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
CODE
DEFINITION
ED
Electronic Data Interchange Access Number
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 a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
INDUSTRY NAME: Payer Contact Communication Number
Situational
7
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
CODE
DEFINITION
ED
Electronic Data Interchange Access Number
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 a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
INDUSTRY NAME: Payer Contact Communication Number
Not Used
9
443
Contact Inquiry Reference
O 1
AN
1/20

HL - INFORMATION RECEIVER 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:
This entity expects a response from the Information Source. See Section 1.4.1 Transaction Participants for more information on the Information Receiver.
TR3 Example:
HL✱2✱1✱21✱1~ or HL✱2✱1✱21✱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.
HL01 must be incremented by one each time an HL is used within each ST/SE envelope. 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
21
Information Receiver
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.
Required when rejecting the status request for errors at the Information Source or Information Receiver levels.
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.
Required when reporting status responses at the lower hierarchial levels (i.e. Provider, Subscriber or Dependent).

NM1*41 - INFORMATION 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.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
This is the individual or organization requesting to receive the status information.
TR3 Example:
NM1✱41✱2✱XYZ SERVICE✱✱✱✱✱46✱A222222221~
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
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 the identifier in NM109 is not sufficient to identify the Information Receiver. If not required by this implementation guide, may be provided at sender's discretion, but cannot be required by the receiver.
INDUSTRY NAME: Information Receiver Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when the value in NM102 = "1" and the person has a first name that is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Information Receiver First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when NM102 = 1 and the person has a middle name that is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Information Receiver Middle Name
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: Information Receiver Identification Number
The ETIN is established through Trading Partner agreement.
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

TRN*2 - INFORMATION RECEIVER TRACE IDENTIFIER

X12 Name:
Trace
X12 Purpose:
To uniquely identify a transaction to an application
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when rejecting claim status requests for errors at Information Source or Information Receiver levels. If not required by this implementation guide, do not send.
TR3 Notes:
If reporting error status at this level, 2000C, 2000D and 2000E Loops are not used.
TR3 Example:
TRN✱2✱ABC276XXX~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
481
Trace Type Code
M 1
ID
1/2
Code identifying which transaction is being referenced
CODE
DEFINITION
2
Referenced Transaction Trace Numbers
Required
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
SEMANTIC: TRN02 provides unique identification for the transaction.
INDUSTRY NAME: Claim Transaction Batch Number
This value must be the BHT03 data element value from the 276 Claim Status Request being rejected.
Not Used
3
509
Originating Company Identifier
O 1
AN
10
Not Used
4
127
Reference Identification
O 1
AN
1/50

STC - INFORMATION RECEIVER STATUS INFORMATION

X12 Name:
Status Information
X12 Purpose:
To report the status, required action, and paid information of a claim or service line
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
>1
TR3 Notes:
See Section 1.4.3 - Status Information (STC) Segment Usage for specific STC segment information related to the hierarchical level, composites and code use.
TR3 Example:
STC✱E0:24:41✱20050830~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
C043
Health Care Claim Status
M 1
Used to convey status of the entire claim or a specific service line
X12 COMPOSITE SEMANTIC NOTES:
  1. C043-01 is used to specify the logical groupings of Health Care Claim Status Codes (See Code Source 507).
  2. C043-02 is used to identify the status of an entire claim or a serviceline. Code Source 508 is referenced unless qualified by C043-04.
  3. C043-03 identifies the entity associated with the Health Care Claim Status Code.
  4. C043-04 is used to identify the Code Source referenced in C043-02.
Required
1-1
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Health Care Claim Status Category Code
Only the `D0' Category Code and `E' Category Codes are allowable at this level.
Required
1-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Status Code
Situational
1-3
98
Entity Identifier Code
O 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
SITUATIONAL RULE: Required when an entity must be identified to further clarify the code message in STC01-2. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
CODE
DEFINITION
41
Submitter
AY
Clearinghouse
PR
Payer
Not Used
1-4
1270
Code List Qualifier Code
O 1
ID
1/3
Required
2
373
Date
O 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: STC02 is the effective date of the status information.
INDUSTRY NAME: Status Information Effective Date
Not Used
3
306
Action Code
O 1
ID
1/2
Not Used
4
782
Monetary Amount
O 1
R
1/18
Not Used
5
782
Monetary Amount
O 1
R
1/18
Not Used
6
373
Date
O 1
DT
8
Not Used
7
591
Payment Method Code
O 1
ID
3
Not Used
8
373
Date
O 1
DT
8
Not Used
9
429
Check Number
O 1
AN
1/16
Situational
10
C043
Health Care Claim Status
O 1
Used to convey status of the entire claim or a specific service line
X12 COMPOSITE SEMANTIC NOTES:
  1. C043-01 is used to specify the logical groupings of Health Care Claim Status Codes (See Code Source 507).
  2. C043-02 is used to identify the status of an entire claim or a serviceline. Code Source 508 is referenced unless qualified by C043-04.
  3. C043-03 identifies the entity associated with the Health Care Claim Status Code.
  4. C043-04 is used to identify the Code Source referenced in C043-02.
SITUATIONAL RULE: Required when a second status is needed. If not required by this implementation guide, do not send.
Required
10-1
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Health Care Claim Status Category Code
See STC01-1 for valid values.
Required
10-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Status Code
Situational
10-3
98
Entity Identifier Code
O 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
SITUATIONAL RULE: Required when an entity must be identified to further clarify the code message in STC10-2. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
See STC01-3 for valid values.
CODE
DEFINITION
41
Submitter
AY
Clearinghouse
PR
Payer
Not Used
10-4
1270
Code List Qualifier Code
O 1
ID
1/3
Situational
11
C043
Health Care Claim Status
O 1
Used to convey status of the entire claim or a specific service line
X12 COMPOSITE SEMANTIC NOTES:
  1. C043-01 is used to specify the logical groupings of Health Care Claim Status Codes (See Code Source 507).
  2. C043-02 is used to identify the status of an entire claim or a serviceline. Code Source 508 is referenced unless qualified by C043-04.
  3. C043-03 identifies the entity associated with the Health Care Claim Status Code.
  4. C043-04 is used to identify the Code Source referenced in C043-02.
SITUATIONAL RULE: Required when a third status is needed. If not required by this implementation guide, do not send.
Required
11-1
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Health Care Claim Status Category Code
See STC01-1 for valid values.
Required
11-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Status Code
Situational
11-3
98
Entity Identifier Code
O 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
SITUATIONAL RULE: Required when an entity must be identified to further clarify the code message in STC11-2. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
See STC01-3 for valid values.
CODE
DEFINITION
41
Submitter
AY
Clearinghouse
PR
Payer
Not Used
11-4
1270
Code List Qualifier Code
O 1
ID
1/3
Not Used
12
933
Free-form Message Text
O 1
AN
1/264

HL - SERVICE PROVIDER LEVEL

X12 Name:
Hierarchical Level
X12 Purpose:
To identify dependencies among and the content of hierarchically related groups of data segments
X12 Comments:
  1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
  2. The HL segment defines a top-down/left-right ordered structure.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when status was not reported at the Information Receiver level. If not required by this implementation guide, do not send.
TR3 Notes:
This entity delivered the health care service. See Section 1.4.1 Transaction Participants for more information on the Provider.
TR3 Example:
HL✱3✱2✱19✱0~ or HL✱3✱2✱19✱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.
HL01 must be incremented by one each time an HL is used within each ST/SE envelope. 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
19
Provider of Service
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.
Required when rejecting the claim status requests for errors at the provider level. The 2000D and 2000E hierarchical levels (children) associated with this provider are not used.
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.
Required when reporting status responses at lower hierarchical levels (Subscriber or Dependent).

NM1*1P - 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.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
  1. During the transition to NPI, for those health care providers covered under the NPI mandate, two iterations of the 2100C Loop may be sent to accommodate reporting dual provider identification numbers (NPI and Legacy). When two iterations are reported, the NPI number will be in the iteration where the NM108 qualifier will be 'XX' and the legacy number will be in the iteration where the NM108 qualifier will be either 'SV' or 'FI'.
  2. After the transition to NPI, for those health care providers covered under the NPI mandate, only one iteration of the 2100C loop must be sent with the NPI reported in the NM109 and NM108=XX.
TR3 Example:
NM1✱1P✱2✱HOME MEDICAL✱✱✱✱✱XX✱1666666666~
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
1P
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
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 the identifier in NM109 is not sufficient to identify the Provider. If not required by this implementation guide, may be provided at sender's discretion, but cannot be required by the receiver.
INDUSTRY NAME: Provider Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when the value in NM102 = "1" and the person has a first name that is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Provider First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when NM102 = 1 and the person has a middle name that is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Provider 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 and the person has a name suffix that is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Provider 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
FI
Federal Taxpayer's Identification Number
SV
Service Provider Number
XX
Centers for Medicare and Medicaid Services National Provider Identifier
Required value when the National Provider ID is mandated for use and the provider is a covered health care provider under the mandate. Otherwise, one of the other listed codes must be used.
CODE SOURCE 537: Centers for Medicare and Medicaid Services National Provider Identifier
Required
9
67
Identification Code
O 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
INDUSTRY NAME: 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

TRN*1 - PROVIDER OF SERVICE TRACE IDENTIFIER

X12 Name:
Trace
X12 Purpose:
To uniquely identify a transaction to an application
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when rejecting the claim status request(s) for errors at the provider level. If not required by this implementation guide, do not send.
TR3 Notes:
  1. If reporting error status at this level, the 2000D and 2000E Loops related to this provider are not used.
  2. The TRN Segment is syntactically required in order to use the Loop 2200C STC. TRN02 can be either a default value of zero (0) or any value the Information Source chooses to assign.
TR3 Example:
TRN✱1✱0~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
481
Trace Type Code
M 1
ID
1/2
Code identifying which transaction is being referenced
CODE
DEFINITION
1
Current Transaction Trace Numbers
Required
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
SEMANTIC: TRN02 provides unique identification for the transaction.
INDUSTRY NAME: Provider of Service Information Trace Identifier
Not Used
3
509
Originating Company Identifier
O 1
AN
10
Not Used
4
127
Reference Identification
O 1
AN
1/50

STC - PROVIDER STATUS INFORMATION

X12 Name:
Status Information
X12 Purpose:
To report the status, required action, and paid information of a claim or service line
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
>1
TR3 Notes:
See Section 1.4.3 - Status Information (STC) Segment Usage for specific STC segment information related to the hierarchical level, composites and code use.
TR3 Example:
STC✱E0:24:85✱20050830~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
C043
Health Care Claim Status
M 1
Used to convey status of the entire claim or a specific service line
X12 COMPOSITE SEMANTIC NOTES:
  1. C043-01 is used to specify the logical groupings of Health Care Claim Status Codes (See Code Source 507).
  2. C043-02 is used to identify the status of an entire claim or a serviceline. Code Source 508 is referenced unless qualified by C043-04.
  3. C043-03 identifies the entity associated with the Health Care Claim Status Code.
  4. C043-04 is used to identify the Code Source referenced in C043-02.
Required
1-1
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Health Care Claim Status Category Code
Only the `D0' Category Code and `E' Category Codes are allowable at this level.
Required
1-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Status Code
Situational
1-3
98
Entity Identifier Code
O 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
SITUATIONAL RULE: Required when an entity must be identified to further clarify the code message in STC01-2. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
CODE
DEFINITION
1P
Provider
Not Used
1-4
1270
Code List Qualifier Code
O 1
ID
1/3
Required
2
373
Date
O 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: STC02 is the effective date of the status information.
INDUSTRY NAME: Status Information Effective Date
Not Used
3
306
Action Code
O 1
ID
1/2
Not Used
4
782
Monetary Amount
O 1
R
1/18
Not Used
5
782
Monetary Amount
O 1
R
1/18
Not Used
6
373
Date
O 1
DT
8
Not Used
7
591
Payment Method Code
O 1
ID
3
Not Used
8
373
Date
O 1
DT
8
Not Used
9
429
Check Number
O 1
AN
1/16
Situational
10
C043
Health Care Claim Status
O 1
Used to convey status of the entire claim or a specific service line
X12 COMPOSITE SEMANTIC NOTES:
  1. C043-01 is used to specify the logical groupings of Health Care Claim Status Codes (See Code Source 507).
  2. C043-02 is used to identify the status of an entire claim or a serviceline. Code Source 508 is referenced unless qualified by C043-04.
  3. C043-03 identifies the entity associated with the Health Care Claim Status Code.
  4. C043-04 is used to identify the Code Source referenced in C043-02.
SITUATIONAL RULE: Required when a second status is needed. If not required by this implementation guide, do not send.
Required
10-1
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Health Care Claim Status Category Code
See STC01-1 for valid values.
Required
10-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Status Code
Situational
10-3
98
Entity Identifier Code
O 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
SITUATIONAL RULE: Required when an entity must be identified to further clarify the code message in STC10-2. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
See STC01-3 for valid value.
CODE
DEFINITION
1P
Provider
Not Used
10-4
1270
Code List Qualifier Code
O 1
ID
1/3
Situational
11
C043
Health Care Claim Status
O 1
Used to convey status of the entire claim or a specific service line
X12 COMPOSITE SEMANTIC NOTES:
  1. C043-01 is used to specify the logical groupings of Health Care Claim Status Codes (See Code Source 507).
  2. C043-02 is used to identify the status of an entire claim or a serviceline. Code Source 508 is referenced unless qualified by C043-04.
  3. C043-03 identifies the entity associated with the Health Care Claim Status Code.
  4. C043-04 is used to identify the Code Source referenced in C043-02.
SITUATIONAL RULE: Required when a third status is needed. If not required by this implementation guide, do not send.
Required
11-1
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Health Care Claim Status Category Code
See STC01-1 for valid values.
Required
11-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Status Code
Situational
11-3
98
Entity Identifier Code
O 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
SITUATIONAL RULE: Required when an entity must be identified to further clarify the code message in STC11-2. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
See STC01-3 for valid value.
CODE
DEFINITION
1P
Provider
Not Used
11-4
1270
Code List Qualifier Code
O 1
ID
1/3
Not Used
12
933
Free-form Message Text
O 1
AN
1/264

HL - SUBSCRIBER LEVEL

X12 Name:
Hierarchical Level
X12 Purpose:
To identify dependencies among and the content of hierarchically related groups of data segments
X12 Comments:
  1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
  2. The HL segment defines a top-down/left-right ordered structure.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when the patient is the subscriber or a dependent with a unique identification number and status was not reported at the Provider level. If not required by this implementation guide, do not send.
TR3 Notes:
  1. When the patient is the subscriber or a dependent with a unique identification number, the claim status response information is reflected in the 2200D Loop under the Subscriber HL, 2000D Loop (HL03 = 22). The Dependent HL, 2000E Loop is not used. See Section 1.4.1.1 for more information on defining the patient.
  2. When requesting and responding to claim status for both a subscriber and a dependent of that subscriber, the Subscriber HL Loop 2000D must be followed by the subscriber's claim status data, Loop 2200D. In this instance, HL04=0 would be used. Then the Subscriber HL Loop 2000D must be repeated prior to the dependent HL Loop 2000E and their corresponding claim status data, Loop 2200E. In this instance, HL04=1 would be used. See Section 1.4.2.3 for an example of this structure.
TR3 Example:
HL✱4✱3✱22✱0~ or HL✱4✱3✱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.
HL01 must be incremented by one each time an HL is used within each ST/SE envelope. 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.
CODE
DEFINITION
0
No Subordinate HL Segment in This Hierarchical Structure.
Required when there are no dependent claim status responses for this subscriber.
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.
Required when there are dependent claim status responses for this subscriber.

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.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
NM1✱IL✱1✱SMITH✱ROBERT✱✱✱✱MI✱9876543210~
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
Use the value "2" in an employer-subscriber situation, such as Worker's Compensation.
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 the value in NM102 = "1" and the person has a first name that is known. 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 and the person has a middle name that is known. 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 and the person has a name suffix that is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber 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
24
Employer's Identification Number
This code may be used in conjunction with a workers compensation claim.
II
Standard Unique Health Identifier for each Individual in the United States
Required if the HIPAA Individual Patient Identifier is mandated for use. If not required, use one of the other values.
MI
Member Identification Number
Required
9
67
Identification Code
O 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
INDUSTRY NAME: Subscriber 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

TRN*2 - CLAIM STATUS TRACKING NUMBER

X12 Name:
Trace
X12 Purpose:
To uniquely identify a transaction to an application
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when the patient is the subscriber or a dependent with a unique identification number. If not required by this implementation guide, do not send.
TR3 Notes:
  1. This is the trace or reference number from the originator of the transaction that was provided for this patient's 276 request.
  2. When the patient is not the subscriber or a dependent with a unique identification number, the Loop 2200E TRN and subsequent segments will be used to reflect the claim status information.
TR3 Example:
TRN✱2✱1722634842~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
481
Trace Type Code
M 1
ID
1/2
Code identifying which transaction is being referenced
CODE
DEFINITION
2
Referenced Transaction Trace Numbers
Required
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
SEMANTIC: TRN02 provides unique identification for the transaction.
INDUSTRY NAME: Referenced Transaction Trace Number
Not Used
3
509
Originating Company Identifier
O 1
AN
10
Not Used
4
127
Reference Identification
O 1
AN
1/50

STC - CLAIM LEVEL STATUS INFORMATION

X12 Name:
Status Information
X12 Purpose:
To report the status, required action, and paid information of a claim or service line
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
>1
TR3 Notes:
See Section 1.4.3 - Status Information (STC) Segment Usage for specific STC segment information related to the hierarchical level, composites and code use.
TR3 Example:
STC✱A1:21✱20050501✱✱50✱0~ or STC✱F1:65✱20050511✱✱50✱40✱20050510✱✱20050510✱50321~ or STC✱F2:79::RX✱20050501✱✱50✱0~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
C043
Health Care Claim Status
M 1
Used to convey status of the entire claim or a specific service line
X12 COMPOSITE SEMANTIC NOTES:
  1. C043-01 is used to specify the logical groupings of Health Care Claim Status Codes (See Code Source 507).
  2. C043-02 is used to identify the status of an entire claim or a serviceline. Code Source 508 is referenced unless qualified by C043-04.
  3. C043-03 identifies the entity associated with the Health Care Claim Status Code.
  4. C043-04 is used to identify the Code Source referenced in C043-02.
Required
1-1
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Health Care Claim Status Category Code
All Category Codes except `Request for Additional Information' (R Category Codes) are allowable at this level.
Required
1-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Status Code
  1. The Status Code is either a Health Care Claim Status Code (Code Source 508) or a National Council for Prescription Drug Programs Reject/Payment Code (Code Source 530).
  2. The National Council for Prescription Drug Programs Reject/Payment Codes may be used for status related to pharmacy claims. When these codes are used, STC01-4 must have the value `RX'.
Situational
1-3
98
Entity Identifier Code
O 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
SITUATIONAL RULE: Required when an entity must be identified to further clarify the code message in STC01-2. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
CODE
DEFINITION
03
Dependent
13
Contracted Service Provider
17
Consultant's Office
1E
Health Maintenance Organization (HMO)
1G
Oncology Center
1H
Kidney Dialysis Unit
1I
Preferred Provider Organization (PPO)
1O
Acute Care Hospital
1P
Provider
1Q
Military Facility
1R
University, College or School
1S
Outpatient Surgicenter
1T
Physician, Clinic or Group Practice
1U
Long Term Care Facility
1V
Extended Care Facility
1W
Psychiatric Health Facility
1X
Laboratory
1Y
Retail Pharmacy
1Z
Home Health Care
28
Subcontractor
2A
Federal, State, County or City Facility
2B
Third-Party Administrator
2D
Miscellaneous Health Care Facility
2E
Non-Health Care Miscellaneous Facility
2I
Church Operated Facility
2K
Partnership
2P
Public Health Service Facility
2Q
Veterans Administration Facility
2S
Public Health Service Indian Service Facility
2Z
Hospital Unit of an Institution (prison hospital, college infirmary, etc.)
30
Service Supplier
36
Employer
3A
Hospital Unit Within an Institution for the Mentally Retarded
3C
Tuberculosis and Other Respiratory Diseases Facility
3D
Obstetrics and Gynecology Facility
3E
Eye, Ear, Nose and Throat Facility
3F
Rehabilitation Facility
3G
Orthopedic Facility
3H
Chronic Disease Facility
3I
Other Specialty Facility
3J
Children's General Facility
3K
Children's Hospital Unit of an Institution
3L
Children's Psychiatric Facility
3M
Children's Tuberculosis and Other Respiratory Diseases Facility
3N
Children's Eye, Ear, Nose and Throat Facility
3O
Children's Rehabilitation Facility
3P
Children's Orthopedic Facility
3Q
Children's Chronic Disease Facility
3R
Children's Other Specialty Facility
3S
Institution for Mental Retardation
3T
Alcoholism and Other Chemical Dependency Facility
3U
General Inpatient Care for AIDS/ARC Facility
3V
AIDS/ARC Unit
3W
Specialized Outpatient Program for AIDS/ARC
3X
Alcohol/Drug Abuse or Dependency Inpatient Unit
3Y
Alcohol/Drug Abuse or Dependency Outpatient Services
3Z
Arthritis Treatment Center
40
Receiver
43
Claimant Authorized Representative
44
Data Processing Service Bureau
4A
Birthing Room/LDRP Room
4B
Burn Care Unit
4C
Cardiac Catherization Laboratory
4D
Open-Heart Surgery Facility
4E
Cardiac Intensive Care Unit
4F
Angioplasty Facility
4G
Chronic Obstructive Pulmonary Disease Service Facility
4H
Emergency Department
4I
Trauma Center (Certified)
4J
Extracorporeal Shock-Wave Lithotripter (ESWL) Unit
4L
Genetic Counseling/Screening Services
4M
Adult Day Care Program Facility
4N
Alzheimer's Diagnostic/Assessment Services
4O
Comprehensive Geriatric Assessment Facility
4P
Emergency Response (Geriatric) Unit
4Q
Geriatric Acute Care Unit
4R
Geriatric Clinics
4S
Respite Care Facility
4U
Patient Education Unit
4V
Community Health Promotion Facility
4W
Worksite Health Promotion Facility
4X
Hemodialysis Facility
4Y
Home Health Services
4Z
Hospice
5A
Medical Surgical or Other Intensive Care Unit
5B
Hisopathology Laboratory
5C
Blood Bank
5D
Neonatal Intensive Care Unit
5E
Obstetrics Unit
5F
Occupational Health Services
5G
Organized Outpatient Services
5H
Pediatric Acute Inpatient Unit
5I
Psychiatric Child/Adolescent Services
5J
Psychiatric Consultation-Liaison Services
5K
Psychiatric Education Services
5L
Psychiatric Emergency Services
5M
Psychiatric Geriatric Services
5N
Psychiatric Inpatient Unit
5O
Psychiatric Outpatient Services
5P
Psychiatric Partial Hospitalization Program
5Q
Megavoltage Radiation Therapy Unit
5R
Radioactive Implants Unit
5S
Therapeutic Radioisotope Facility
5T
X-Ray Radiation Therapy Unit
5U
CT Scanner Unit
5V
Diagnostic Radioisotope Facility
5W
Magnetic Resonance Imaging (MRI) Facility
5X
Ultrasound Unit
5Y
Rehabilitation Inpatient Unit
5Z
Rehabilitation Outpatient Services
61
Performed At
6A
Reproductive Health Services
6B
Skilled Nursing or Other Long-Term Care Unit
6C
Single Photon Emission Computerized Tomography (SPECT) Unit
6D
Organized Social Work Service Facility
6E
Outpatient Social Work Services
6F
Emergency Department Social Work Services
6G
Sports Medicine Clinic/Services
6H
Hospital Auxiliary Unit
6I
Patient Representative Services
6J
Volunteer Services Department
6K
Outpatient Surgery Services
6L
Organ/Tissue Transplant Unit
6M
Orthopedic Surgery Facility
6N
Occupational Therapy Services
6O
Physical Therapy Services
6P
Recreational Therapy Services
6Q
Respiratory Therapy Services
6R
Speech Therapy Services
6S
Women's Health Center/Services
6U
Cardiac Rehabilitation Program Facility
6V
Non-Invasive Cardiac Assessment Services
6W
Emergency Medical Technician
6X
Disciplinary Contact
6Y
Case Manager
71
Attending Physician
72
Operating Physician
73
Other Physician
74
Corrected Insured
77
Service Location
7C
Place of Occurrence
80
Hospital
82
Rendering Provider
84
Subscriber's Employer
85
Billing Provider
87
Pay-to Provider
95
Research Institute
CK
Pharmacist
CZ
Admitting Surgeon
D2
Commercial Insurer
DD
Assistant Surgeon
DJ
Consulting Physician
DK
Ordering Physician
DN
Referring Provider
DO
Dependent Name
DQ
Supervising Physician
E1
Person or Other Entity Legally Responsible for a Child
E2
Person or Other Entity With Whom a Child Resides
E7
Previous Employer
E9
Participating Laboratory
FA
Facility
FD
Physical Address
FE
Mail Address
G0
Dependent Insured
G3
Clinic
GB
Other Insured
GD
Guardian
GI
Paramedic
GJ
Paramedical Company
GK
Previous Insured
GM
Spouse Insured
GY
Treatment Facility
HF
Healthcare Professional Shortage Area (HPSA) Facility
HH
Home Health Agency
I3
Independent Physicians Association (IPA)
IJ
Injection Point
IL
Insured or Subscriber
IN
Insurer
LI
Independent Lab
LR
Legal Representative
MR
Medical Insurance Carrier
MSC
Mammography Screening Center
OB
Ordered By
OD
Doctor of Optometry
OX
Oxygen Therapy Facility
P0
Patient Facility
P2
Primary Insured or Subscriber
P3
Primary Care Provider
P4
Prior Insurance Carrier
P6
Third Party Reviewing Preferred Provider Organization (PPO)
P7
Third Party Repricing Preferred Provider Organization (PPO)
PRP
Primary Payer
PT
Party to Receive Test Report
PV
Party performing certification
PW
Pickup Address
QA
Pharmacy
QB
Purchase Service Provider
QC
Patient
QD
Responsible Party
QE
Policyholder
QH
Physician
QK
Managed Care
QL
Chiropractor
QN
Dentist
QO
Doctor of Osteopathy
QS
Podiatrist
QV
Group Practice
QY
Medical Doctor
RC
Receiving Location
RW
Rural Health Clinic
S4
Skilled Nursing Facility
SEP
Secondary Payer
SJ
Service Provider
SU
Supplier/Manufacturer
T4
Transfer Point
Used to identify the geographic location where a patient is transferred or diverted.
TL
Testing Laboratory
TQ
Third Party Reviewing Organization (TPO)
TT
Transfer To
TTP
Tertiary Payer
TU
Third Party Repricing Organization (TPO)
UH
Nursing Home
X3
Utilization Management Organization
X4
Spouse
X5
Durable Medical Equipment Supplier
ZZ
Mutually Defined
Situational
1-4
1270
Code List Qualifier Code
O 1
ID
1/3
Code identifying a specific industry code list
SITUATIONAL RULE: Required when using a National Council for Prescription Drug Programs Reject/Payment Code in STC01-2 for status related to a pharmacy claim. If not required by this implementation guide, do not send.
CODE
DEFINITION
RX
National Council for Prescription Drug Programs Reject/Payment Codes
CODE SOURCE 530: National Council for Prescription Drug Programs Reject/Payment Codes
Required
2
373
Date
O 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: STC02 is the effective date of the status information.
INDUSTRY NAME: Status Information Effective Date
This is the date the claim was placed in this status by the Information Source's adjudication process.
Not Used
3
306
Action Code
O 1
ID
1/2
Situational
4
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: STC04 is the amount of original submitted charges.
SITUATIONAL RULE: Required when the response provides status on a claim found in the Information Source's system. If not required by this implementation guide, do not send.
INDUSTRY NAME: Total Claim Charge Amount
The total claim charge may change from the submitted claim total charge based on claims processing instructions, i.e. claim splitting. Some payers may not store the original submitted charge. Some HMO encounters supply zero as the amount of original charges.
Situational
5
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: STC05 is the amount paid.
SITUATIONAL RULE: Required when the remittance cycle is complete and a remittance advice has been issued. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
INDUSTRY NAME: Claim Payment Amount
  1. Zero is an acceptable amount when no payment is being made.
  2. Some payers are able to provide the adjudicated payment amount prior to the remittance being issued.
Situational
6
373
Date
O 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: STC06 is the paid date.
SITUATIONAL RULE: Required when the remittance cycle is complete and a remittance advice has been issued. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
INDUSTRY NAME: Adjudication Finalized Date
  1. This is the date of denial or approval for the claim. This date may or may not be the same as the issue date of the check, EFT or non-payment remittance (STC08).
  2. Some payers are able to provide the final claim adjudicated date prior to the remittance being issued.
Not Used
7
591
Payment Method Code
O 1
ID
3
Situational
8
373
Date
O 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: STC08 is the check issue date.
SITUATIONAL RULE: Required when the remittance cycle is complete and this claim is included on a check or EFT that is reported in an 835 or paper remittance to the provider. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
INDUSTRY NAME: Remittance Date
  1. This is the check issue or EFT funds available date.
  2. This could include a non-payment remittance advice date if available from the Information Source's system.
Situational
9
429
Check Number
O 1
AN
1/16
Check identification number
SITUATIONAL RULE: Required when the remittance cycle is complete and this claim is included on a check or EFT that is reported in an 835 or paper remittance to the provider. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
INDUSTRY NAME: Remittance Trace Number
  1. This is the check or EFT Trace Number.
  2. This could include a non-payment remittance advice Trace Number (835 or paper) if available from the Information Source's system.
Situational
10
C043
Health Care Claim Status
O 1
Used to convey status of the entire claim or a specific service line
X12 COMPOSITE SEMANTIC NOTES:
  1. C043-01 is used to specify the logical groupings of Health Care Claim Status Codes (See Code Source 507).
  2. C043-02 is used to identify the status of an entire claim or a serviceline. Code Source 508 is referenced unless qualified by C043-04.
  3. C043-03 identifies the entity associated with the Health Care Claim Status Code.
  4. C043-04 is used to identify the Code Source referenced in C043-02.
SITUATIONAL RULE: Required when a second claim status is needed. If not required by this implementation guide, do not send.
Required
10-1
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Health Care Claim Status Category Code
See STC01-1 for valid values.
Required
10-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Status Code
  1. The Status Code is either a Health Care Claim Status Code (Code Source 508) or a National Council for Prescription Drug Programs Reject/Payment Code (Code Source 530).
  2. The National Council for Prescription Drug Programs Reject/Payment Codes may be used for status related to pharmacy claims. When these codes are used, STC10-4 must have the value `RX'.
Situational
10-3
98
Entity Identifier Code
O 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
SITUATIONAL RULE: Required when an entity must be identified to further clarify the code message in STC10-2. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
See STC01-3 for valid values.
CODE
DEFINITION
03
Dependent
13
Contracted Service Provider
17
Consultant's Office
1E
Health Maintenance Organization (HMO)
1G
Oncology Center
1H
Kidney Dialysis Unit
1I
Preferred Provider Organization (PPO)
1O
Acute Care Hospital
1P
Provider
1Q
Military Facility
1R
University, College or School
1S
Outpatient Surgicenter
1T
Physician, Clinic or Group Practice
1U
Long Term Care Facility
1V
Extended Care Facility
1W
Psychiatric Health Facility
1X
Laboratory
1Y
Retail Pharmacy
1Z
Home Health Care
28
Subcontractor
2A
Federal, State, County or City Facility
2B
Third-Party Administrator
2D
Miscellaneous Health Care Facility
2E
Non-Health Care Miscellaneous Facility
2I
Church Operated Facility
2K
Partnership
2P
Public Health Service Facility
2Q
Veterans Administration Facility
2S
Public Health Service Indian Service Facility
2Z
Hospital Unit of an Institution (prison hospital, college infirmary, etc.)
30
Service Supplier
36
Employer
3A
Hospital Unit Within an Institution for the Mentally Retarded
3C
Tuberculosis and Other Respiratory Diseases Facility
3D
Obstetrics and Gynecology Facility
3E
Eye, Ear, Nose and Throat Facility
3F
Rehabilitation Facility
3G
Orthopedic Facility
3H
Chronic Disease Facility
3I
Other Specialty Facility
3J
Children's General Facility
3K
Children's Hospital Unit of an Institution
3L
Children's Psychiatric Facility
3M
Children's Tuberculosis and Other Respiratory Diseases Facility
3N
Children's Eye, Ear, Nose and Throat Facility
3O
Children's Rehabilitation Facility
3P
Children's Orthopedic Facility
3Q
Children's Chronic Disease Facility
3R
Children's Other Specialty Facility
3S
Institution for Mental Retardation
3T
Alcoholism and Other Chemical Dependency Facility
3U
General Inpatient Care for AIDS/ARC Facility
3V
AIDS/ARC Unit
3W
Specialized Outpatient Program for AIDS/ARC
3X
Alcohol/Drug Abuse or Dependency Inpatient Unit
3Y
Alcohol/Drug Abuse or Dependency Outpatient Services
3Z
Arthritis Treatment Center
40
Receiver
43
Claimant Authorized Representative
44
Data Processing Service Bureau
4A
Birthing Room/LDRP Room
4B
Burn Care Unit
4C
Cardiac Catherization Laboratory
4D
Open-Heart Surgery Facility
4E
Cardiac Intensive Care Unit
4F
Angioplasty Facility
4G
Chronic Obstructive Pulmonary Disease Service Facility
4H
Emergency Department
4I
Trauma Center (Certified)
4J
Extracorporeal Shock-Wave Lithotripter (ESWL) Unit
4L
Genetic Counseling/Screening Services
4M
Adult Day Care Program Facility
4N
Alzheimer's Diagnostic/Assessment Services
4O
Comprehensive Geriatric Assessment Facility
4P
Emergency Response (Geriatric) Unit
4Q
Geriatric Acute Care Unit
4R
Geriatric Clinics
4S
Respite Care Facility
4U
Patient Education Unit
4V
Community Health Promotion Facility
4W
Worksite Health Promotion Facility
4X
Hemodialysis Facility
4Y
Home Health Services
4Z
Hospice
5A
Medical Surgical or Other Intensive Care Unit
5B
Hisopathology Laboratory
5C
Blood Bank
5D
Neonatal Intensive Care Unit
5E
Obstetrics Unit
5F
Occupational Health Services
5G
Organized Outpatient Services
5H
Pediatric Acute Inpatient Unit
5I
Psychiatric Child/Adolescent Services
5J
Psychiatric Consultation-Liaison Services
5K
Psychiatric Education Services
5L
Psychiatric Emergency Services
5M
Psychiatric Geriatric Services
5N
Psychiatric Inpatient Unit
5O
Psychiatric Outpatient Services
5P
Psychiatric Partial Hospitalization Program
5Q
Megavoltage Radiation Therapy Unit
5R
Radioactive Implants Unit
5S
Therapeutic Radioisotope Facility
5T
X-Ray Radiation Therapy Unit
5U
CT Scanner Unit
5V
Diagnostic Radioisotope Facility
5W
Magnetic Resonance Imaging (MRI) Facility
5X
Ultrasound Unit
5Y
Rehabilitation Inpatient Unit
5Z
Rehabilitation Outpatient Services
61
Performed At
6A
Reproductive Health Services
6B
Skilled Nursing or Other Long-Term Care Unit
6C
Single Photon Emission Computerized Tomography (SPECT) Unit
6D
Organized Social Work Service Facility
6E
Outpatient Social Work Services
6F
Emergency Department Social Work Services
6G
Sports Medicine Clinic/Services
6H
Hospital Auxiliary Unit
6I
Patient Representative Services
6J
Volunteer Services Department
6K
Outpatient Surgery Services
6L
Organ/Tissue Transplant Unit
6M
Orthopedic Surgery Facility
6N
Occupational Therapy Services
6O
Physical Therapy Services
6P
Recreational Therapy Services
6Q
Respiratory Therapy Services
6R
Speech Therapy Services
6S
Women's Health Center/Services
6U
Cardiac Rehabilitation Program Facility
6V
Non-Invasive Cardiac Assessment Services
6W
Emergency Medical Technician
6X
Disciplinary Contact
6Y
Case Manager
71
Attending Physician
72
Operating Physician
73
Other Physician
74
Corrected Insured
77
Service Location
7C
Place of Occurrence
80
Hospital
82
Rendering Provider
84
Subscriber's Employer
85
Billing Provider
87
Pay-to Provider
95
Research Institute
CK
Pharmacist
CZ
Admitting Surgeon
D2
Commercial Insurer
DD
Assistant Surgeon
DJ
Consulting Physician
DK
Ordering Physician
DN
Referring Provider
DO
Dependent Name
DQ
Supervising Physician
E1
Person or Other Entity Legally Responsible for a Child
E2
Person or Other Entity With Whom a Child Resides
E7
Previous Employer
E9
Participating Laboratory
FA
Facility
FD
Physical Address
FE
Mail Address
G0
Dependent Insured
G3
Clinic
GB
Other Insured
GD
Guardian
GI
Paramedic
GJ
Paramedical Company
GK
Previous Insured
GM
Spouse Insured
GY
Treatment Facility
HF
Healthcare Professional Shortage Area (HPSA) Facility
HH
Home Health Agency
I3
Independent Physicians Association (IPA)
IJ
Injection Point
IL
Insured or Subscriber
IN
Insurer
LI
Independent Lab
LR
Legal Representative
MR
Medical Insurance Carrier
MSC
Mammography Screening Center
OB
Ordered By
OD
Doctor of Optometry
OX
Oxygen Therapy Facility
P0
Patient Facility
P2
Primary Insured or Subscriber
P3
Primary Care Provider
P4
Prior Insurance Carrier
P6
Third Party Reviewing Preferred Provider Organization (PPO)
P7
Third Party Repricing Preferred Provider Organization (PPO)
PRP
Primary Payer
PT
Party to Receive Test Report
PV
Party performing certification
PW
Pickup Address
QA
Pharmacy
QB
Purchase Service Provider
QC
Patient
QD
Responsible Party
QE
Policyholder
QH
Physician
QK
Managed Care
QL
Chiropractor
QN
Dentist
QO
Doctor of Osteopathy
QS
Podiatrist
QV
Group Practice
QY
Medical Doctor
RC
Receiving Location
RW
Rural Health Clinic
S4
Skilled Nursing Facility
SEP
Secondary Payer
SJ
Service Provider
SU
Supplier/Manufacturer
T4
Transfer Point
Used to identify the geographic location where a patient is transferred or diverted.
TL
Testing Laboratory
TQ
Third Party Reviewing Organization (TPO)
TT
Transfer To
TTP
Tertiary Payer
TU
Third Party Repricing Organization (TPO)
UH
Nursing Home
X3
Utilization Management Organization
X4
Spouse
X5
Durable Medical Equipment Supplier
ZZ
Mutually Defined
Situational
10-4
1270
Code List Qualifier Code
O 1
ID
1/3
Code identifying a specific industry code list
SITUATIONAL RULE: Required when using a National Council for Prescription Drug Programs Reject/Payment Code in STC10-2 for status related to a pharmacy claim. If not required by this implementation guide, do not send.
CODE
DEFINITION
RX
National Council for Prescription Drug Programs Reject/Payment Codes
CODE SOURCE 530: National Council for Prescription Drug Programs Reject/Payment Codes
Situational
11
C043
Health Care Claim Status
O 1
Used to convey status of the entire claim or a specific service line
X12 COMPOSITE SEMANTIC NOTES:
  1. C043-01 is used to specify the logical groupings of Health Care Claim Status Codes (See Code Source 507).
  2. C043-02 is used to identify the status of an entire claim or a serviceline. Code Source 508 is referenced unless qualified by C043-04.
  3. C043-03 identifies the entity associated with the Health Care Claim Status Code.
  4. C043-04 is used to identify the Code Source referenced in C043-02.
SITUATIONAL RULE: Required when a third claim status is needed. If not required by this implementation guide, do not send.
Required
11-1
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Health Care Claim Status Category Code
See STC01-1 for valid values.
Required
11-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Status Code
  1. The Status Code is either a Health Care Claim Status Code (Code Source 508) or a National Council for Prescription Drug Programs Reject/Payment Code (Code Source 530).
  2. The National Council for Prescription Drug Programs Reject/Payment Codes may be used for status related to pharmacy claims. When these codes are used, STC11-4 must have the value `RX'.
Situational
11-3
98
Entity Identifier Code
O 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
SITUATIONAL RULE: Required when an entity must be identified to further clarify the code message in STC11-2. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
See STC01-3 for valid values.
CODE
DEFINITION
03
Dependent
13
Contracted Service Provider
17
Consultant's Office
1E
Health Maintenance Organization (HMO)
1G
Oncology Center
1H
Kidney Dialysis Unit
1I
Preferred Provider Organization (PPO)
1O
Acute Care Hospital
1P
Provider
1Q
Military Facility
1R
University, College or School
1S
Outpatient Surgicenter
1T
Physician, Clinic or Group Practice
1U
Long Term Care Facility
1V
Extended Care Facility
1W
Psychiatric Health Facility
1X
Laboratory
1Y
Retail Pharmacy
1Z
Home Health Care
28
Subcontractor
2A
Federal, State, County or City Facility
2B
Third-Party Administrator
2D
Miscellaneous Health Care Facility
2E
Non-Health Care Miscellaneous Facility
2I
Church Operated Facility
2K
Partnership
2P
Public Health Service Facility
2Q
Veterans Administration Facility
2S
Public Health Service Indian Service Facility
2Z
Hospital Unit of an Institution (prison hospital, college infirmary, etc.)
30
Service Supplier
36
Employer
3A
Hospital Unit Within an Institution for the Mentally Retarded
3C
Tuberculosis and Other Respiratory Diseases Facility
3D
Obstetrics and Gynecology Facility
3E
Eye, Ear, Nose and Throat Facility
3F
Rehabilitation Facility
3G
Orthopedic Facility
3H
Chronic Disease Facility
3I
Other Specialty Facility
3J
Children's General Facility
3K
Children's Hospital Unit of an Institution
3L
Children's Psychiatric Facility
3M
Children's Tuberculosis and Other Respiratory Diseases Facility
3N
Children's Eye, Ear, Nose and Throat Facility
3O
Children's Rehabilitation Facility
3P
Children's Orthopedic Facility
3Q
Children's Chronic Disease Facility
3R
Children's Other Specialty Facility
3S
Institution for Mental Retardation
3T
Alcoholism and Other Chemical Dependency Facility
3U
General Inpatient Care for AIDS/ARC Facility
3V
AIDS/ARC Unit
3W
Specialized Outpatient Program for AIDS/ARC
3X
Alcohol/Drug Abuse or Dependency Inpatient Unit
3Y
Alcohol/Drug Abuse or Dependency Outpatient Services
3Z
Arthritis Treatment Center
40
Receiver
43
Claimant Authorized Representative
44
Data Processing Service Bureau
4A
Birthing Room/LDRP Room
4B
Burn Care Unit
4C
Cardiac Catherization Laboratory
4D
Open-Heart Surgery Facility
4E
Cardiac Intensive Care Unit
4F
Angioplasty Facility
4G
Chronic Obstructive Pulmonary Disease Service Facility
4H
Emergency Department
4I
Trauma Center (Certified)
4J
Extracorporeal Shock-Wave Lithotripter (ESWL) Unit
4L
Genetic Counseling/Screening Services
4M
Adult Day Care Program Facility
4N
Alzheimer's Diagnostic/Assessment Services
4O
Comprehensive Geriatric Assessment Facility
4P
Emergency Response (Geriatric) Unit
4Q
Geriatric Acute Care Unit
4R
Geriatric Clinics
4S
Respite Care Facility
4U
Patient Education Unit
4V
Community Health Promotion Facility
4W
Worksite Health Promotion Facility
4X
Hemodialysis Facility
4Y
Home Health Services
4Z
Hospice
5A
Medical Surgical or Other Intensive Care Unit
5B
Hisopathology Laboratory
5C
Blood Bank
5D
Neonatal Intensive Care Unit
5E
Obstetrics Unit
5F
Occupational Health Services
5G
Organized Outpatient Services
5H
Pediatric Acute Inpatient Unit
5I
Psychiatric Child/Adolescent Services
5J
Psychiatric Consultation-Liaison Services
5K
Psychiatric Education Services
5L
Psychiatric Emergency Services
5M
Psychiatric Geriatric Services
5N
Psychiatric Inpatient Unit
5O
Psychiatric Outpatient Services
5P
Psychiatric Partial Hospitalization Program
5Q
Megavoltage Radiation Therapy Unit
5R
Radioactive Implants Unit
5S
Therapeutic Radioisotope Facility
5T
X-Ray Radiation Therapy Unit
5U
CT Scanner Unit
5V
Diagnostic Radioisotope Facility
5W
Magnetic Resonance Imaging (MRI) Facility
5X
Ultrasound Unit
5Y
Rehabilitation Inpatient Unit
5Z
Rehabilitation Outpatient Services
61
Performed At
6A
Reproductive Health Services
6B
Skilled Nursing or Other Long-Term Care Unit
6C
Single Photon Emission Computerized Tomography (SPECT) Unit
6D
Organized Social Work Service Facility
6E
Outpatient Social Work Services
6F
Emergency Department Social Work Services
6G
Sports Medicine Clinic/Services
6H
Hospital Auxiliary Unit
6I
Patient Representative Services
6J
Volunteer Services Department
6K
Outpatient Surgery Services
6L
Organ/Tissue Transplant Unit
6M
Orthopedic Surgery Facility
6N
Occupational Therapy Services
6O
Physical Therapy Services
6P
Recreational Therapy Services
6Q
Respiratory Therapy Services
6R
Speech Therapy Services
6S
Women's Health Center/Services
6U
Cardiac Rehabilitation Program Facility
6V
Non-Invasive Cardiac Assessment Services
6W
Emergency Medical Technician
6X
Disciplinary Contact
6Y
Case Manager
71
Attending Physician
72
Operating Physician
73
Other Physician
74
Corrected Insured
77
Service Location
7C
Place of Occurrence
80
Hospital
82
Rendering Provider
84
Subscriber's Employer
85
Billing Provider
87
Pay-to Provider
95
Research Institute
CK
Pharmacist
CZ
Admitting Surgeon
D2
Commercial Insurer
DD
Assistant Surgeon
DJ
Consulting Physician
DK
Ordering Physician
DN
Referring Provider
DO
Dependent Name
DQ
Supervising Physician
E1
Person or Other Entity Legally Responsible for a Child
E2
Person or Other Entity With Whom a Child Resides
E7
Previous Employer
E9
Participating Laboratory
FA
Facility
FD
Physical Address
FE
Mail Address
G0
Dependent Insured
G3
Clinic
GB
Other Insured
GD
Guardian
GI
Paramedic
GJ
Paramedical Company
GK
Previous Insured
GM
Spouse Insured
GY
Treatment Facility
HF
Healthcare Professional Shortage Area (HPSA) Facility
HH
Home Health Agency
I3
Independent Physicians Association (IPA)
IJ
Injection Point
IL
Insured or Subscriber
IN
Insurer
LI
Independent Lab
LR
Legal Representative
MR
Medical Insurance Carrier
MSC
Mammography Screening Center
OB
Ordered By
OD
Doctor of Optometry
OX
Oxygen Therapy Facility
P0
Patient Facility
P2
Primary Insured or Subscriber
P3
Primary Care Provider
P4
Prior Insurance Carrier
P6
Third Party Reviewing Preferred Provider Organization (PPO)
P7
Third Party Repricing Preferred Provider Organization (PPO)
PRP
Primary Payer
PT
Party to Receive Test Report
PV
Party performing certification
PW
Pickup Address
QA
Pharmacy
QB
Purchase Service Provider
QC
Patient
QD
Responsible Party
QE
Policyholder
QH
Physician
QK
Managed Care
QL
Chiropractor
QN
Dentist
QO
Doctor of Osteopathy
QS
Podiatrist
QV
Group Practice
QY
Medical Doctor
RC
Receiving Location
RW
Rural Health Clinic
S4
Skilled Nursing Facility
SEP
Secondary Payer
SJ
Service Provider
SU
Supplier/Manufacturer
T4
Transfer Point
Used to identify the geographic location where a patient is transferred or diverted.
TL
Testing Laboratory
TQ
Third Party Reviewing Organization (TPO)
TT
Transfer To
TTP
Tertiary Payer
TU
Third Party Repricing Organization (TPO)
UH
Nursing Home
X3
Utilization Management Organization
X4
Spouse
X5
Durable Medical Equipment Supplier
ZZ
Mutually Defined
Situational
11-4
1270
Code List Qualifier Code
O 1
ID
1/3
Code identifying a specific industry code list
SITUATIONAL RULE: Required when using a National Council for Prescription Drug Programs Reject/Payment Code in STC11-2 for status related to a pharmacy claim. If not required by this implementation guide, do not send.
CODE
DEFINITION
RX
National Council for Prescription Drug Programs Reject/Payment Codes
CODE SOURCE 530: National Council for Prescription Drug Programs Reject/Payment Codes
Not Used
12
933
Free-form Message Text
O 1
AN
1/264

REF*1K - 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:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when a claim is located in the Information Source's system. If not required by this implementation guide, do not send.
TR3 Notes:
This is the payer's assigned control number, also known as, Internal Control Number (ICN), Document Control Number (DCN), or Claim Control Number (CCN).
TR3 Example:
REF✱1K✱9918046987~
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
1K
Payor's 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: Payer Claim Control Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*BLT - INSTITUTIONAL BILL TYPE 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 on institutional claims when different than the value submitted on the 276 request. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
TR3 Example:
REF✱BLT✱111~
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
BLT
Billing Type
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: Bill Type Identifier
Concatenate the 837I CLM05-1 (Facility Type Code) and CLM05-3 (Claim Frequency Code) values.
Code Source 236: Uniform Billing Claim Form Bill Type
Code Source 235: Claim Frequency Type Code
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*EJ - PATIENT 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:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the Patient Control Number was submitted on the 276 request or when available on claims located in the Information Source's system. If not required by this implementation guide, do not send.
TR3 Notes:
The maximum number of characters supported for the Patient Control Number is `20'.
TR3 Example:
REF✱EJ✱PT12345~
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
EJ
Patient Account 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: Patient Control Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*XZ - PHARMACY PRESCRIPTION NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the Pharmacy Prescription Number was submitted on the 276 request or when available on claims located in the Information Source's system. If not required by this implementation guide, do not send.
TR3 Example:
REF✱XZ✱1234567~
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
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: Pharmacy Prescription Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*VV - VOUCHER IDENTIFIER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when a voucher identifier is associated with the response claim. If not required by this implementation guide, do not send.
TR3 Notes:
Some payers assign voucher identifiers to a group of claims as part of the payment process prior to payment being issued.
TR3 Example:
REF✱VV✱V123~
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
VV
Voucher
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: Voucher Identifier
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*D9 - CLAIM IDENTIFICATION NUMBER FOR CLEARINGHOUSES AND OTHER 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:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when received on the 276 status request. If not required by this implementation guide, do not send.
TR3 Example:
REF✱D9✱20041513010001~
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
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: Clearinghouse Trace Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

DTP*472 - CLAIM 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:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required for institutional claims or for professional and dental claims when the service line date is not used. 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. For professional claims, this date is derived from the service level dates.
  2. When reporting a claim level date, use the date from the Information Source's system for claim matches, otherwise return the date from the 276 status request.
TR3 Example:
DTP✱472✱RD8✱20050401-20050402~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
472
Service
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
RD8
Range of Dates Expressed in Format CCYYMMDD-CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Claim Service Period

SVC - SERVICE LINE INFORMATION

X12 Name:
Service Information
X12 Purpose:
To supply payment and control information to a provider for a particular service
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when reporting status for Service Lines. If not required by this implementation guide, do not send.
TR3 Notes:
For Institutional claims, when both an NUBC revenue code and a HCPCS or HIPPS code are reported, the HCPCS or HIPPS code is reported in SVC01-2 and the revenue code is reported in SVC04. When only a revenue code is used, it is reported in SVC01-2.
TR3 Example:
SVC✱HC:99214✱75✱50✱✱✱✱1~ orSVC✱NU:0710✱50✱0✱✱✱✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
C003
Composite Medical Procedure Identifier
M 1
To identify a medical procedure by its standardized codes and applicable modifiers
SEMANTIC: SVC01 is the medical procedure upon which adjudication is based.
COMMENT: For Medicare Part A claims, SVC01 would be the Health Care Financing Administration (HCFA) Common Procedural Coding System (HCPCS) Code (see code source 130) and SVC04 would be the Revenue Code (see code source 132).
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.
SVC01-2 contains the adjudicated procedure code. This code may be different than the original submitted procedure code based on the payer's claim processing.
Required
1-1
235
Product/Service ID Qualifier
M 1
ID
2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
INDUSTRY NAME: Product or Service ID Qualifier
CODE
DEFINITION
AD
American Dental Association Codes
CODE SOURCE 135: American Dental Association
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 CPT codes of the American Medical Association are also level 1 HCPCS codes, the CPT codes are reported under the code HC.
CODE SOURCE 130: Healthcare Common Procedural Coding System
HP
Health Insurance Prospective Payment System (HIPPS) Skilled Nursing Facility Rate Code
CODE SOURCE 716: Health Insurance Prospective Payment System (HIPPS) Rate Code for Skilled Nursing Facilities
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 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
N4
National Drug Code in 5-4-2 Format
CODE SOURCE 240: National Drug Code by Format
NU
National Uniform Billing Committee (NUBC) UB92 Codes
This code is the NUBC Revenue Code.
CODE SOURCE 132: National Uniform Billing Committee (NUBC) Codes
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
If the value in SVC01-1 is "NU", then this is an NUBC Revenue Code. If the revenue code is present here, then SVC04 is not used.
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 modifiers have been applied to the adjudicated procedure code reported in SVC01-2. 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 modifiers have been applied to the adjudicated procedure code reported in SVC01-2. 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 modifiers have been applied to the adjudicated procedure code reported in SVC01-2. 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 modifiers have been applied to the adjudicated procedure code reported in SVC01-2. If not required by this implementation guide, do not send.
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
782
Monetary Amount
M 1
R
1/18
Monetary amount
SEMANTIC: SVC02 is the submitted service charge.
INDUSTRY NAME: Line Item Charge Amount
This is the line item total on the current claim service status.
Required
3
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: SVC03 is the amount paid this service.
INDUSTRY NAME: Line Item Payment Amount
Situational
4
234
Product/Service ID
O 1
AN
1/48
Identifying number for a product or service
SEMANTIC: SVC04 is the National Uniform Billing Committee Revenue Code.
SITUATIONAL RULE: Required on institutional claims when an NUBC revenue code needs to be reported in addition to a HCPCS or HIPPS code reported in SVC01-2. If not required by this implementation guide, do not send.
INDUSTRY NAME: Revenue Code
Not Used
5
380
Quantity
O 1
R
1/15
Not Used
6
C003
Composite Medical Procedure Identifier
O 1
Required
7
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: SVC07 is the original submitted units of service.
INDUSTRY NAME: Units of Service Count

STC - SERVICE LINE STATUS INFORMATION

X12 Name:
Status Information
X12 Purpose:
To report the status, required action, and paid information of a claim or service line
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
>1
TR3 Notes:
See Section 1.4.3 - Status Information (STC) Segment Usage for specific STC segment information related to the hierarchical level, composites and code use.
TR3 Example:
STC✱F1:65✱20050501~ orSTC✱A3:110✱20050501✱✱✱✱✱✱✱✱A3:400~ or STC✱F2:79::RX✱20050501~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
C043
Health Care Claim Status
M 1
Used to convey status of the entire claim or a specific service line
X12 COMPOSITE SEMANTIC NOTES:
  1. C043-01 is used to specify the logical groupings of Health Care Claim Status Codes (See Code Source 507).
  2. C043-02 is used to identify the status of an entire claim or a serviceline. Code Source 508 is referenced unless qualified by C043-04.
  3. C043-03 identifies the entity associated with the Health Care Claim Status Code.
  4. C043-04 is used to identify the Code Source referenced in C043-02.
Required
1-1
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Health Care Claim Status Category Code
All Category Codes except `Request for Additional Information' (R Category Codes) are allowable at this level.
Required
1-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Status Code
  1. The Status Code is either a Health Care Claim Status Code (Code Source 508) or a National Council for Prescription Drug Programs Reject/Payment Code (Code Source 530).
  2. The National Council for Prescription Drug Programs Reject/Payment Codes may be used for status related to pharmacy claims. When these codes are used, STC01-4 must have the value `RX'.
Situational
1-3
98
Entity Identifier Code
O 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
SITUATIONAL RULE: Required when an entity must be identified to further clarify the code message in STC01-2. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
CODE
DEFINITION
03
Dependent
13
Contracted Service Provider
17
Consultant's Office
1E
Health Maintenance Organization (HMO)
1G
Oncology Center
1H
Kidney Dialysis Unit
1I
Preferred Provider Organization (PPO)
1O
Acute Care Hospital
1P
Provider
1Q
Military Facility
1R
University, College or School
1S
Outpatient Surgicenter
1T
Physician, Clinic or Group Practice
1U
Long Term Care Facility
1V
Extended Care Facility
1W
Psychiatric Health Facility
1X
Laboratory
1Y
Retail Pharmacy
1Z
Home Health Care
28
Subcontractor
2A
Federal, State, County or City Facility
2B
Third-Party Administrator
2D
Miscellaneous Health Care Facility
2E
Non-Health Care Miscellaneous Facility
2I
Church Operated Facility
2K
Partnership
2P
Public Health Service Facility
2Q
Veterans Administration Facility
2S
Public Health Service Indian Service Facility
2Z
Hospital Unit of an Institution (prison hospital, college infirmary, etc.)
30
Service Supplier
36
Employer
3A
Hospital Unit Within an Institution for the Mentally Retarded
3C
Tuberculosis and Other Respiratory Diseases Facility
3D
Obstetrics and Gynecology Facility
3E
Eye, Ear, Nose and Throat Facility
3F
Rehabilitation Facility
3G
Orthopedic Facility
3H
Chronic Disease Facility
3I
Other Specialty Facility
3J
Children's General Facility
3K
Children's Hospital Unit of an Institution
3L
Children's Psychiatric Facility
3M
Children's Tuberculosis and Other Respiratory Diseases Facility
3N
Children's Eye, Ear, Nose and Throat Facility
3O
Children's Rehabilitation Facility
3P
Children's Orthopedic Facility
3Q
Children's Chronic Disease Facility
3R
Children's Other Specialty Facility
3S
Institution for Mental Retardation
3T
Alcoholism and Other Chemical Dependency Facility
3U
General Inpatient Care for AIDS/ARC Facility
3V
AIDS/ARC Unit
3W
Specialized Outpatient Program for AIDS/ARC
3X
Alcohol/Drug Abuse or Dependency Inpatient Unit
3Y
Alcohol/Drug Abuse or Dependency Outpatient Services
3Z
Arthritis Treatment Center
40
Receiver
43
Claimant Authorized Representative
44
Data Processing Service Bureau
4A
Birthing Room/LDRP Room
4B
Burn Care Unit
4C
Cardiac Catherization Laboratory
4D
Open-Heart Surgery Facility
4E
Cardiac Intensive Care Unit
4F
Angioplasty Facility
4G
Chronic Obstructive Pulmonary Disease Service Facility
4H
Emergency Department
4I
Trauma Center (Certified)
4J
Extracorporeal Shock-Wave Lithotripter (ESWL) Unit
4L
Genetic Counseling/Screening Services
4M
Adult Day Care Program Facility
4N
Alzheimer's Diagnostic/Assessment Services
4O
Comprehensive Geriatric Assessment Facility
4P
Emergency Response (Geriatric) Unit
4Q
Geriatric Acute Care Unit
4R
Geriatric Clinics
4S
Respite Care Facility
4U
Patient Education Unit
4V
Community Health Promotion Facility
4W
Worksite Health Promotion Facility
4X
Hemodialysis Facility
4Y
Home Health Services
4Z
Hospice
5A
Medical Surgical or Other Intensive Care Unit
5B
Hisopathology Laboratory
5C
Blood Bank
5D
Neonatal Intensive Care Unit
5E
Obstetrics Unit
5F
Occupational Health Services
5G
Organized Outpatient Services
5H
Pediatric Acute Inpatient Unit
5I
Psychiatric Child/Adolescent Services
5J
Psychiatric Consultation-Liaison Services
5K
Psychiatric Education Services
5L
Psychiatric Emergency Services
5M
Psychiatric Geriatric Services
5N
Psychiatric Inpatient Unit
5O
Psychiatric Outpatient Services
5P
Psychiatric Partial Hospitalization Program
5Q
Megavoltage Radiation Therapy Unit
5R
Radioactive Implants Unit
5S
Therapeutic Radioisotope Facility
5T
X-Ray Radiation Therapy Unit
5U
CT Scanner Unit
5V
Diagnostic Radioisotope Facility
5W
Magnetic Resonance Imaging (MRI) Facility
5X
Ultrasound Unit
5Y
Rehabilitation Inpatient Unit
5Z
Rehabilitation Outpatient Services
61
Performed At
6A
Reproductive Health Services
6B
Skilled Nursing or Other Long-Term Care Unit
6C
Single Photon Emission Computerized Tomography (SPECT) Unit
6D
Organized Social Work Service Facility
6E
Outpatient Social Work Services
6F
Emergency Department Social Work Services
6G
Sports Medicine Clinic/Services
6H
Hospital Auxiliary Unit
6I
Patient Representative Services
6J
Volunteer Services Department
6K
Outpatient Surgery Services
6L
Organ/Tissue Transplant Unit
6M
Orthopedic Surgery Facility
6N
Occupational Therapy Services
6O
Physical Therapy Services
6P
Recreational Therapy Services
6Q
Respiratory Therapy Services
6R
Speech Therapy Services
6S
Women's Health Center/Services
6U
Cardiac Rehabilitation Program Facility
6V
Non-Invasive Cardiac Assessment Services
6W
Emergency Medical Technician
6X
Disciplinary Contact
6Y
Case Manager
71
Attending Physician
72
Operating Physician
73
Other Physician
74
Corrected Insured
77
Service Location
7C
Place of Occurrence
80
Hospital
82
Rendering Provider
84
Subscriber's Employer
85
Billing Provider
87
Pay-to Provider
95
Research Institute
CK
Pharmacist
CZ
Admitting Surgeon
D2
Commercial Insurer
DD
Assistant Surgeon
DJ
Consulting Physician
DK
Ordering Physician
DN
Referring Provider
DO
Dependent Name
DQ
Supervising Physician
E1
Person or Other Entity Legally Responsible for a Child
E2
Person or Other Entity With Whom a Child Resides
E7
Previous Employer
E9
Participating Laboratory
FA
Facility
FD
Physical Address
FE
Mail Address
G0
Dependent Insured
G3
Clinic
GB
Other Insured
GD
Guardian
GI
Paramedic
GJ
Paramedical Company
GK
Previous Insured
GM
Spouse Insured
GY
Treatment Facility
HF
Healthcare Professional Shortage Area (HPSA) Facility
HH
Home Health Agency
I3
Independent Physicians Association (IPA)
IJ
Injection Point
IL
Insured or Subscriber
IN
Insurer
LI
Independent Lab
LR
Legal Representative
MR
Medical Insurance Carrier
MSC
Mammography Screening Center
OB
Ordered By
OD
Doctor of Optometry
OX
Oxygen Therapy Facility
P0
Patient Facility
P2
Primary Insured or Subscriber
P3
Primary Care Provider
P4
Prior Insurance Carrier
P6
Third Party Reviewing Preferred Provider Organization (PPO)
P7
Third Party Repricing Preferred Provider Organization (PPO)
PRP
Primary Payer
PT
Party to Receive Test Report
PV
Party performing certification
PW
Pickup Address
QA
Pharmacy
QB
Purchase Service Provider
QC
Patient
QD
Responsible Party
QE
Policyholder
QH
Physician
QK
Managed Care
QL
Chiropractor
QN
Dentist
QO
Doctor of Osteopathy
QS
Podiatrist
QV
Group Practice
QY
Medical Doctor
RC
Receiving Location
RW
Rural Health Clinic
S4
Skilled Nursing Facility
SEP
Secondary Payer
SJ
Service Provider
SU
Supplier/Manufacturer
T4
Transfer Point
Used to identify the geographic location where a patient is transferred or diverted.
TL
Testing Laboratory
TQ
Third Party Reviewing Organization (TPO)
TT
Transfer To
TTP
Tertiary Payer
TU
Third Party Repricing Organization (TPO)
UH
Nursing Home
X3
Utilization Management Organization
X4
Spouse
X5
Durable Medical Equipment Supplier
ZZ
Mutually Defined
Situational
1-4
1270
Code List Qualifier Code
O 1
ID
1/3
Code identifying a specific industry code list
SITUATIONAL RULE: Required when using a National Council for Prescription Drug Programs Reject/Payment Code in STC01-2 for status related to a pharmacy claim. If not required by this implementation guide, do not send.
CODE
DEFINITION
RX
National Council for Prescription Drug Programs Reject/Payment Codes
CODE SOURCE 530: National Council for Prescription Drug Programs Reject/Payment Codes
Required
2
373
Date
O 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: STC02 is the effective date of the status information.
INDUSTRY NAME: Status Information Effective Date
This is the date the service was placed in this status by the Information Source's adjudication process.
Not Used
3
306
Action Code
O 1
ID
1/2
Not Used
4
782
Monetary Amount
O 1
R
1/18
Not Used
5
782
Monetary Amount
O 1
R
1/18
Not Used
6
373
Date
O 1
DT
8
Not Used
7
591
Payment Method Code
O 1
ID
3
Not Used
8
373
Date
O 1
DT
8
Not Used
9
429
Check Number
O 1
AN
1/16
Situational
10
C043
Health Care Claim Status
O 1
Used to convey status of the entire claim or a specific service line
X12 COMPOSITE SEMANTIC NOTES:
  1. C043-01 is used to specify the logical groupings of Health Care Claim Status Codes (See Code Source 507).
  2. C043-02 is used to identify the status of an entire claim or a serviceline. Code Source 508 is referenced unless qualified by C043-04.
  3. C043-03 identifies the entity associated with the Health Care Claim Status Code.
  4. C043-04 is used to identify the Code Source referenced in C043-02.
SITUATIONAL RULE: Required when a second claim status is needed. If not required by this implementation guide, do not send.
Required
10-1
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Health Care Claim Status Category Code
See STC01-1 for valid values.
Required
10-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Status Code
  1. The Status Code is either a Health Care Claim Status Code (Code Source 508) or a National Council for Prescription Drug Programs Reject/Payment Code (Code Source 530).
  2. The National Council for Prescription Drug Programs Reject/Payment Codes may be used for status related to pharmacy claims. When these codes are used, STC10-4 must have the value `RX'.
Situational
10-3
98
Entity Identifier Code
O 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
SITUATIONAL RULE: Required when an entity must be identified to further clarify the code message in STC10-2. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
See STC01-3 for valid values.
CODE
DEFINITION
03
Dependent
13
Contracted Service Provider
17
Consultant's Office
1E
Health Maintenance Organization (HMO)
1G
Oncology Center
1H
Kidney Dialysis Unit
1I
Preferred Provider Organization (PPO)
1O
Acute Care Hospital
1P
Provider
1Q
Military Facility
1R
University, College or School
1S
Outpatient Surgicenter
1T
Physician, Clinic or Group Practice
1U
Long Term Care Facility
1V
Extended Care Facility
1W
Psychiatric Health Facility
1X
Laboratory
1Y
Retail Pharmacy
1Z
Home Health Care
28
Subcontractor
2A
Federal, State, County or City Facility
2B
Third-Party Administrator
2D
Miscellaneous Health Care Facility
2E
Non-Health Care Miscellaneous Facility
2I
Church Operated Facility
2K
Partnership
2P
Public Health Service Facility
2Q
Veterans Administration Facility
2S
Public Health Service Indian Service Facility
2Z
Hospital Unit of an Institution (prison hospital, college infirmary, etc.)
30
Service Supplier
36
Employer
3A
Hospital Unit Within an Institution for the Mentally Retarded
3C
Tuberculosis and Other Respiratory Diseases Facility
3D
Obstetrics and Gynecology Facility
3E
Eye, Ear, Nose and Throat Facility
3F
Rehabilitation Facility
3G
Orthopedic Facility
3H
Chronic Disease Facility
3I
Other Specialty Facility
3J
Children's General Facility
3K
Children's Hospital Unit of an Institution
3L
Children's Psychiatric Facility
3M
Children's Tuberculosis and Other Respiratory Diseases Facility
3N
Children's Eye, Ear, Nose and Throat Facility
3O
Children's Rehabilitation Facility
3P
Children's Orthopedic Facility
3Q
Children's Chronic Disease Facility
3R
Children's Other Specialty Facility
3S
Institution for Mental Retardation
3T
Alcoholism and Other Chemical Dependency Facility
3U
General Inpatient Care for AIDS/ARC Facility
3V
AIDS/ARC Unit
3W
Specialized Outpatient Program for AIDS/ARC
3X
Alcohol/Drug Abuse or Dependency Inpatient Unit
3Y
Alcohol/Drug Abuse or Dependency Outpatient Services
3Z
Arthritis Treatment Center
40
Receiver
43
Claimant Authorized Representative
44
Data Processing Service Bureau
4A
Birthing Room/LDRP Room
4B
Burn Care Unit
4C
Cardiac Catherization Laboratory
4D
Open-Heart Surgery Facility
4E
Cardiac Intensive Care Unit
4F
Angioplasty Facility
4G
Chronic Obstructive Pulmonary Disease Service Facility
4H
Emergency Department
4I
Trauma Center (Certified)
4J
Extracorporeal Shock-Wave Lithotripter (ESWL) Unit
4L
Genetic Counseling/Screening Services
4M
Adult Day Care Program Facility
4N
Alzheimer's Diagnostic/Assessment Services
4O
Comprehensive Geriatric Assessment Facility
4P
Emergency Response (Geriatric) Unit
4Q
Geriatric Acute Care Unit
4R
Geriatric Clinics
4S
Respite Care Facility
4U
Patient Education Unit
4V
Community Health Promotion Facility
4W
Worksite Health Promotion Facility
4X
Hemodialysis Facility
4Y
Home Health Services
4Z
Hospice
5A
Medical Surgical or Other Intensive Care Unit
5B
Hisopathology Laboratory
5C
Blood Bank
5D
Neonatal Intensive Care Unit
5E
Obstetrics Unit
5F
Occupational Health Services
5G
Organized Outpatient Services
5H
Pediatric Acute Inpatient Unit
5I
Psychiatric Child/Adolescent Services
5J
Psychiatric Consultation-Liaison Services
5K
Psychiatric Education Services
5L
Psychiatric Emergency Services
5M
Psychiatric Geriatric Services
5N
Psychiatric Inpatient Unit
5O
Psychiatric Outpatient Services
5P
Psychiatric Partial Hospitalization Program
5Q
Megavoltage Radiation Therapy Unit
5R
Radioactive Implants Unit
5S
Therapeutic Radioisotope Facility
5T
X-Ray Radiation Therapy Unit
5U
CT Scanner Unit
5V
Diagnostic Radioisotope Facility
5W
Magnetic Resonance Imaging (MRI) Facility
5X
Ultrasound Unit
5Y
Rehabilitation Inpatient Unit
5Z
Rehabilitation Outpatient Services
61
Performed At
6A
Reproductive Health Services
6B
Skilled Nursing or Other Long-Term Care Unit
6C
Single Photon Emission Computerized Tomography (SPECT) Unit
6D
Organized Social Work Service Facility
6E
Outpatient Social Work Services
6F
Emergency Department Social Work Services
6G
Sports Medicine Clinic/Services
6H
Hospital Auxiliary Unit
6I
Patient Representative Services
6J
Volunteer Services Department
6K
Outpatient Surgery Services
6L
Organ/Tissue Transplant Unit
6M
Orthopedic Surgery Facility
6N
Occupational Therapy Services
6O
Physical Therapy Services
6P
Recreational Therapy Services
6Q
Respiratory Therapy Services
6R
Speech Therapy Services
6S
Women's Health Center/Services
6U
Cardiac Rehabilitation Program Facility
6V
Non-Invasive Cardiac Assessment Services
6W
Emergency Medical Technician
6X
Disciplinary Contact
6Y
Case Manager
71
Attending Physician
72
Operating Physician
73
Other Physician
74
Corrected Insured
77
Service Location
7C
Place of Occurrence
80
Hospital
82
Rendering Provider
84
Subscriber's Employer
85
Billing Provider
87
Pay-to Provider
95
Research Institute
CK
Pharmacist
CZ
Admitting Surgeon
D2
Commercial Insurer
DD
Assistant Surgeon
DJ
Consulting Physician
DK
Ordering Physician
DN
Referring Provider
DO
Dependent Name
DQ
Supervising Physician
E1
Person or Other Entity Legally Responsible for a Child
E2
Person or Other Entity With Whom a Child Resides
E7
Previous Employer
E9
Participating Laboratory
FA
Facility
FD
Physical Address
FE
Mail Address
G0
Dependent Insured
G3
Clinic
GB
Other Insured
GD
Guardian
GI
Paramedic
GJ
Paramedical Company
GK
Previous Insured
GM
Spouse Insured
GY
Treatment Facility
HF
Healthcare Professional Shortage Area (HPSA) Facility
HH
Home Health Agency
I3
Independent Physicians Association (IPA)
IJ
Injection Point
IL
Insured or Subscriber
IN
Insurer
LI
Independent Lab
LR
Legal Representative
MR
Medical Insurance Carrier
MSC
Mammography Screening Center
OB
Ordered By
OD
Doctor of Optometry
OX
Oxygen Therapy Facility
P0
Patient Facility
P2
Primary Insured or Subscriber
P3
Primary Care Provider
P4
Prior Insurance Carrier
P6
Third Party Reviewing Preferred Provider Organization (PPO)
P7
Third Party Repricing Preferred Provider Organization (PPO)
PRP
Primary Payer
PT
Party to Receive Test Report
PV
Party performing certification
PW
Pickup Address
QA
Pharmacy
QB
Purchase Service Provider
QC
Patient
QD
Responsible Party
QE
Policyholder
QH
Physician
QK
Managed Care
QL
Chiropractor
QN
Dentist
QO
Doctor of Osteopathy
QS
Podiatrist
QV
Group Practice
QY
Medical Doctor
RC
Receiving Location
RW
Rural Health Clinic
S4
Skilled Nursing Facility
SEP
Secondary Payer
SJ
Service Provider
SU
Supplier/Manufacturer
T4
Transfer Point
Used to identify the geographic location where a patient is transferred or diverted.
TL
Testing Laboratory
TQ
Third Party Reviewing Organization (TPO)
TT
Transfer To
TTP
Tertiary Payer
TU
Third Party Repricing Organization (TPO)
UH
Nursing Home
X3
Utilization Management Organization
X4
Spouse
X5
Durable Medical Equipment Supplier
ZZ
Mutually Defined
Situational
10-4
1270
Code List Qualifier Code
O 1
ID
1/3
Code identifying a specific industry code list
SITUATIONAL RULE: Required when using a National Council for Prescription Drug Programs Reject/Payment Code in STC10-2 for status related to a pharmacy claim. If not required by this implementation guide, do not send.
CODE
DEFINITION
RX
National Council for Prescription Drug Programs Reject/Payment Codes
CODE SOURCE 530: National Council for Prescription Drug Programs Reject/Payment Codes
Situational
11
C043
Health Care Claim Status
O 1
Used to convey status of the entire claim or a specific service line
X12 COMPOSITE SEMANTIC NOTES:
  1. C043-01 is used to specify the logical groupings of Health Care Claim Status Codes (See Code Source 507).
  2. C043-02 is used to identify the status of an entire claim or a serviceline. Code Source 508 is referenced unless qualified by C043-04.
  3. C043-03 identifies the entity associated with the Health Care Claim Status Code.
  4. C043-04 is used to identify the Code Source referenced in C043-02.
SITUATIONAL RULE: Required when a third claim status is needed. If not required by this implementation guide, do not send.
Required
11-1
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Health Care Claim Status Category Code
See STC01-1 for valid values.
Required
11-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Status Code
  1. The Status Code is either a Health Care Claim Status Code (Code Source 508) or a National Council for Prescription Drug Programs Reject/Payment Code (Code Source 530).
  2. The National Council for Prescription Drug Programs Reject/Payment Codes may be used for status related to pharmacy claims. When these codes are used, STC11-4 must have the value `RX'.
Situational
11-3
98
Entity Identifier Code
O 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
SITUATIONAL RULE: Required when an entity must be identified to further clarify the code message in STC11-2. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
See STC01-3 for valid values.
CODE
DEFINITION
03
Dependent
13
Contracted Service Provider
17
Consultant's Office
1E
Health Maintenance Organization (HMO)
1G
Oncology Center
1H
Kidney Dialysis Unit
1I
Preferred Provider Organization (PPO)
1O
Acute Care Hospital
1P
Provider
1Q
Military Facility
1R
University, College or School
1S
Outpatient Surgicenter
1T
Physician, Clinic or Group Practice
1U
Long Term Care Facility
1V
Extended Care Facility
1W
Psychiatric Health Facility
1X
Laboratory
1Y
Retail Pharmacy
1Z
Home Health Care
28
Subcontractor
2A
Federal, State, County or City Facility
2B
Third-Party Administrator
2D
Miscellaneous Health Care Facility
2E
Non-Health Care Miscellaneous Facility
2I
Church Operated Facility
2K
Partnership
2P
Public Health Service Facility
2Q
Veterans Administration Facility
2S
Public Health Service Indian Service Facility
2Z
Hospital Unit of an Institution (prison hospital, college infirmary, etc.)
30
Service Supplier
36
Employer
3A
Hospital Unit Within an Institution for the Mentally Retarded
3C
Tuberculosis and Other Respiratory Diseases Facility
3D
Obstetrics and Gynecology Facility
3E
Eye, Ear, Nose and Throat Facility
3F
Rehabilitation Facility
3G
Orthopedic Facility
3H
Chronic Disease Facility
3I
Other Specialty Facility
3J
Children's General Facility
3K
Children's Hospital Unit of an Institution
3L
Children's Psychiatric Facility
3M
Children's Tuberculosis and Other Respiratory Diseases Facility
3N
Children's Eye, Ear, Nose and Throat Facility
3O
Children's Rehabilitation Facility
3P
Children's Orthopedic Facility
3Q
Children's Chronic Disease Facility
3R
Children's Other Specialty Facility
3S
Institution for Mental Retardation
3T
Alcoholism and Other Chemical Dependency Facility
3U
General Inpatient Care for AIDS/ARC Facility
3V
AIDS/ARC Unit
3W
Specialized Outpatient Program for AIDS/ARC
3X
Alcohol/Drug Abuse or Dependency Inpatient Unit
3Y
Alcohol/Drug Abuse or Dependency Outpatient Services
3Z
Arthritis Treatment Center
40
Receiver
43
Claimant Authorized Representative
44
Data Processing Service Bureau
4A
Birthing Room/LDRP Room
4B
Burn Care Unit
4C
Cardiac Catherization Laboratory
4D
Open-Heart Surgery Facility
4E
Cardiac Intensive Care Unit
4F
Angioplasty Facility
4G
Chronic Obstructive Pulmonary Disease Service Facility
4H
Emergency Department
4I
Trauma Center (Certified)
4J
Extracorporeal Shock-Wave Lithotripter (ESWL) Unit
4L
Genetic Counseling/Screening Services
4M
Adult Day Care Program Facility
4N
Alzheimer's Diagnostic/Assessment Services
4O
Comprehensive Geriatric Assessment Facility
4P
Emergency Response (Geriatric) Unit
4Q
Geriatric Acute Care Unit
4R
Geriatric Clinics
4S
Respite Care Facility
4U
Patient Education Unit
4V
Community Health Promotion Facility
4W
Worksite Health Promotion Facility
4X
Hemodialysis Facility
4Y
Home Health Services
4Z
Hospice
5A
Medical Surgical or Other Intensive Care Unit
5B
Hisopathology Laboratory
5C
Blood Bank
5D
Neonatal Intensive Care Unit
5E
Obstetrics Unit
5F
Occupational Health Services
5G
Organized Outpatient Services
5H
Pediatric Acute Inpatient Unit
5I
Psychiatric Child/Adolescent Services
5J
Psychiatric Consultation-Liaison Services
5K
Psychiatric Education Services
5L
Psychiatric Emergency Services
5M
Psychiatric Geriatric Services
5N
Psychiatric Inpatient Unit
5O
Psychiatric Outpatient Services
5P
Psychiatric Partial Hospitalization Program
5Q
Megavoltage Radiation Therapy Unit
5R
Radioactive Implants Unit
5S
Therapeutic Radioisotope Facility
5T
X-Ray Radiation Therapy Unit
5U
CT Scanner Unit
5V
Diagnostic Radioisotope Facility
5W
Magnetic Resonance Imaging (MRI) Facility
5X
Ultrasound Unit
5Y
Rehabilitation Inpatient Unit
5Z
Rehabilitation Outpatient Services
61
Performed At
6A
Reproductive Health Services
6B
Skilled Nursing or Other Long-Term Care Unit
6C
Single Photon Emission Computerized Tomography (SPECT) Unit
6D
Organized Social Work Service Facility
6E
Outpatient Social Work Services
6F
Emergency Department Social Work Services
6G
Sports Medicine Clinic/Services
6H
Hospital Auxiliary Unit
6I
Patient Representative Services
6J
Volunteer Services Department
6K
Outpatient Surgery Services
6L
Organ/Tissue Transplant Unit
6M
Orthopedic Surgery Facility
6N
Occupational Therapy Services
6O
Physical Therapy Services
6P
Recreational Therapy Services
6Q
Respiratory Therapy Services
6R
Speech Therapy Services
6S
Women's Health Center/Services
6U
Cardiac Rehabilitation Program Facility
6V
Non-Invasive Cardiac Assessment Services
6W
Emergency Medical Technician
6X
Disciplinary Contact
6Y
Case Manager
71
Attending Physician
72
Operating Physician
73
Other Physician
74
Corrected Insured
77
Service Location
7C
Place of Occurrence
80
Hospital
82
Rendering Provider
84
Subscriber's Employer
85
Billing Provider
87
Pay-to Provider
95
Research Institute
CK
Pharmacist
CZ
Admitting Surgeon
D2
Commercial Insurer
DD
Assistant Surgeon
DJ
Consulting Physician
DK
Ordering Physician
DN
Referring Provider
DO
Dependent Name
DQ
Supervising Physician
E1
Person or Other Entity Legally Responsible for a Child
E2
Person or Other Entity With Whom a Child Resides
E7
Previous Employer
E9
Participating Laboratory
FA
Facility
FD
Physical Address
FE
Mail Address
G0
Dependent Insured
G3
Clinic
GB
Other Insured
GD
Guardian
GI
Paramedic
GJ
Paramedical Company
GK
Previous Insured
GM
Spouse Insured
GY
Treatment Facility
HF
Healthcare Professional Shortage Area (HPSA) Facility
HH
Home Health Agency
I3
Independent Physicians Association (IPA)
IJ
Injection Point
IL
Insured or Subscriber
IN
Insurer
LI
Independent Lab
LR
Legal Representative
MR
Medical Insurance Carrier
MSC
Mammography Screening Center
OB
Ordered By
OD
Doctor of Optometry
OX
Oxygen Therapy Facility
P0
Patient Facility
P2
Primary Insured or Subscriber
P3
Primary Care Provider
P4
Prior Insurance Carrier
P6
Third Party Reviewing Preferred Provider Organization (PPO)
P7
Third Party Repricing Preferred Provider Organization (PPO)
PRP
Primary Payer
PT
Party to Receive Test Report
PV
Party performing certification
PW
Pickup Address
QA
Pharmacy
QB
Purchase Service Provider
QC
Patient
QD
Responsible Party
QE
Policyholder
QH
Physician
QK
Managed Care
QL
Chiropractor
QN
Dentist
QO
Doctor of Osteopathy
QS
Podiatrist
QV
Group Practice
QY
Medical Doctor
RC
Receiving Location
RW
Rural Health Clinic
S4
Skilled Nursing Facility
SEP
Secondary Payer
SJ
Service Provider
SU
Supplier/Manufacturer
T4
Transfer Point
Used to identify the geographic location where a patient is transferred or diverted.
TL
Testing Laboratory
TQ
Third Party Reviewing Organization (TPO)
TT
Transfer To
TTP
Tertiary Payer
TU
Third Party Repricing Organization (TPO)
UH
Nursing Home
X3
Utilization Management Organization
X4
Spouse
X5
Durable Medical Equipment Supplier
ZZ
Mutually Defined
Situational
11-4
1270
Code List Qualifier Code
O 1
ID
1/3
Code identifying a specific industry code list
SITUATIONAL RULE: Required when using a National Council for Prescription Drug Programs Reject/Payment Code in STC11-2 for status related to a pharmacy claim. If not required by this implementation guide, do not send.
CODE
DEFINITION
RX
National Council for Prescription Drug Programs Reject/Payment Codes
CODE SOURCE 530: National Council for Prescription Drug Programs Reject/Payment Codes
Not Used
12
933
Free-form Message Text
O 1
AN
1/264

REF*FJ - SERVICE LINE ITEM 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 the Service Line Item Identification was submitted on the 276 request and service level status is reported. If not required by this implementation guide, do not send.
TR3 Example:
REF✱FJ✱6042201~
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
FJ
Line Item 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
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

DTP*472 - SERVICE LINE 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✱472✱RD8✱20050401-20050402~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
472
Service
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
RD8
Range of Dates Expressed in Format CCYYMMDD-CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Service Line Date

HL - DEPENDENT 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 who does not have a unique identification number. If not required by this implementation guide, do not send.
TR3 Notes:
When the patient is a dependent, the claim status response information is reflected in the 2200E Loop under the Dependent HL, 2000E Loop (HL03 = 23). See Section 1.4.1.1 for more information on defining the patient.
TR3 Example:
HL✱5✱4✱23~
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.
HL01 must be incremented by one each time an HL is used within each ST/SE envelope. 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
23
Dependent
Not Used
4
736
Hierarchical Child Code
O 1
ID
1

NM1*QC - DEPENDENT 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.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
NM1✱QC✱1✱SMITH✱JOSEPH~
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 that is known. 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 person has a middle name that is known. 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 person has a name suffix that is known. 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

TRN*2 - CLAIM STATUS TRACKING NUMBER

X12 Name:
Trace
X12 Purpose:
To uniquely identify a transaction to an application
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
This is the trace or reference number from the originator of the transaction that was provided for this patient's 276 request.
TR3 Example:
TRN✱2✱1722634842~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
481
Trace Type Code
M 1
ID
1/2
Code identifying which transaction is being referenced
CODE
DEFINITION
2
Referenced Transaction Trace Numbers
Required
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
SEMANTIC: TRN02 provides unique identification for the transaction.
INDUSTRY NAME: Referenced Transaction Trace Number
Not Used
3
509
Originating Company Identifier
O 1
AN
10
Not Used
4
127
Reference Identification
O 1
AN
1/50

STC - CLAIM LEVEL STATUS INFORMATION

X12 Name:
Status Information
X12 Purpose:
To report the status, required action, and paid information of a claim or service line
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
>1
TR3 Notes:
See Section 1.4.3 - Status Information (STC) Segment Usage for specific STC segment information related to the hierarchical level, composites and code use.
TR3 Example:
STC✱A1:21✱20050501✱✱50✱0~ or STC✱F1:65✱20050511✱✱50✱40✱20050510✱✱20050510✱50321~ or STC✱F2:79::RX✱20050501✱✱50✱0~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
C043
Health Care Claim Status
M 1
Used to convey status of the entire claim or a specific service line
X12 COMPOSITE SEMANTIC NOTES:
  1. C043-01 is used to specify the logical groupings of Health Care Claim Status Codes (See Code Source 507).
  2. C043-02 is used to identify the status of an entire claim or a serviceline. Code Source 508 is referenced unless qualified by C043-04.
  3. C043-03 identifies the entity associated with the Health Care Claim Status Code.
  4. C043-04 is used to identify the Code Source referenced in C043-02.
Required
1-1
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Health Care Claim Status Category Code
All Category Codes except `Request for Additional Information' (R Category Codes) are allowable at this level.
Required
1-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Status Code
  1. The Status Code is either a Health Care Claim Status Code (Code Source 508) or a National Council for Prescription Drug Programs Reject/Payment Code (Code Source 530).
  2. The National Council for Prescription Drug Programs Reject/Payment Codes may be used for status related to pharmacy claims. When these codes are used, STC01-4 must have the value `RX'.
Situational
1-3
98
Entity Identifier Code
O 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
SITUATIONAL RULE: Required when an entity must be identified to further clarify the code message in STC01-2. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
CODE
DEFINITION
03
Dependent
13
Contracted Service Provider
17
Consultant's Office
1E
Health Maintenance Organization (HMO)
1G
Oncology Center
1H
Kidney Dialysis Unit
1I
Preferred Provider Organization (PPO)
1O
Acute Care Hospital
1P
Provider
1Q
Military Facility
1R
University, College or School
1S
Outpatient Surgicenter
1T
Physician, Clinic or Group Practice
1U
Long Term Care Facility
1V
Extended Care Facility
1W
Psychiatric Health Facility
1X
Laboratory
1Y
Retail Pharmacy
1Z
Home Health Care
28
Subcontractor
2A
Federal, State, County or City Facility
2B
Third-Party Administrator
2D
Miscellaneous Health Care Facility
2E
Non-Health Care Miscellaneous Facility
2I
Church Operated Facility
2K
Partnership
2P
Public Health Service Facility
2Q
Veterans Administration Facility
2S
Public Health Service Indian Service Facility
2Z
Hospital Unit of an Institution (prison hospital, college infirmary, etc.)
30
Service Supplier
36
Employer
3A
Hospital Unit Within an Institution for the Mentally Retarded
3C
Tuberculosis and Other Respiratory Diseases Facility
3D
Obstetrics and Gynecology Facility
3E
Eye, Ear, Nose and Throat Facility
3F
Rehabilitation Facility
3G
Orthopedic Facility
3H
Chronic Disease Facility
3I
Other Specialty Facility
3J
Children's General Facility
3K
Children's Hospital Unit of an Institution
3L
Children's Psychiatric Facility
3M
Children's Tuberculosis and Other Respiratory Diseases Facility
3N
Children's Eye, Ear, Nose and Throat Facility
3O
Children's Rehabilitation Facility
3P
Children's Orthopedic Facility
3Q
Children's Chronic Disease Facility
3R
Children's Other Specialty Facility
3S
Institution for Mental Retardation
3T
Alcoholism and Other Chemical Dependency Facility
3U
General Inpatient Care for AIDS/ARC Facility
3V
AIDS/ARC Unit
3W
Specialized Outpatient Program for AIDS/ARC
3X
Alcohol/Drug Abuse or Dependency Inpatient Unit
3Y
Alcohol/Drug Abuse or Dependency Outpatient Services
3Z
Arthritis Treatment Center
40
Receiver
43
Claimant Authorized Representative
44
Data Processing Service Bureau
4A
Birthing Room/LDRP Room
4B
Burn Care Unit
4C
Cardiac Catherization Laboratory
4D
Open-Heart Surgery Facility
4E
Cardiac Intensive Care Unit
4F
Angioplasty Facility
4G
Chronic Obstructive Pulmonary Disease Service Facility
4H
Emergency Department
4I
Trauma Center (Certified)
4J
Extracorporeal Shock-Wave Lithotripter (ESWL) Unit
4L
Genetic Counseling/Screening Services
4M
Adult Day Care Program Facility
4N
Alzheimer's Diagnostic/Assessment Services
4O
Comprehensive Geriatric Assessment Facility
4P
Emergency Response (Geriatric) Unit
4Q
Geriatric Acute Care Unit
4R
Geriatric Clinics
4S
Respite Care Facility
4U
Patient Education Unit
4V
Community Health Promotion Facility
4W
Worksite Health Promotion Facility
4X
Hemodialysis Facility
4Y
Home Health Services
4Z
Hospice
5A
Medical Surgical or Other Intensive Care Unit
5B
Hisopathology Laboratory
5C
Blood Bank
5D
Neonatal Intensive Care Unit
5E
Obstetrics Unit
5F
Occupational Health Services
5G
Organized Outpatient Services
5H
Pediatric Acute Inpatient Unit
5I
Psychiatric Child/Adolescent Services
5J
Psychiatric Consultation-Liaison Services
5K
Psychiatric Education Services
5L
Psychiatric Emergency Services
5M
Psychiatric Geriatric Services
5N
Psychiatric Inpatient Unit
5O
Psychiatric Outpatient Services
5P
Psychiatric Partial Hospitalization Program
5Q
Megavoltage Radiation Therapy Unit
5R
Radioactive Implants Unit
5S
Therapeutic Radioisotope Facility
5T
X-Ray Radiation Therapy Unit
5U
CT Scanner Unit
5V
Diagnostic Radioisotope Facility
5W
Magnetic Resonance Imaging (MRI) Facility
5X
Ultrasound Unit
5Y
Rehabilitation Inpatient Unit
5Z
Rehabilitation Outpatient Services
61
Performed At
6A
Reproductive Health Services
6B
Skilled Nursing or Other Long-Term Care Unit
6C
Single Photon Emission Computerized Tomography (SPECT) Unit
6D
Organized Social Work Service Facility
6E
Outpatient Social Work Services
6F
Emergency Department Social Work Services
6G
Sports Medicine Clinic/Services
6H
Hospital Auxiliary Unit
6I
Patient Representative Services
6J
Volunteer Services Department
6K
Outpatient Surgery Services
6L
Organ/Tissue Transplant Unit
6M
Orthopedic Surgery Facility
6N
Occupational Therapy Services
6O
Physical Therapy Services
6P
Recreational Therapy Services
6Q
Respiratory Therapy Services
6R
Speech Therapy Services
6S
Women's Health Center/Services
6U
Cardiac Rehabilitation Program Facility
6V
Non-Invasive Cardiac Assessment Services
6W
Emergency Medical Technician
6X
Disciplinary Contact
6Y
Case Manager
71
Attending Physician
72
Operating Physician
73
Other Physician
74
Corrected Insured
77
Service Location
7C
Place of Occurrence
80
Hospital
82
Rendering Provider
84
Subscriber's Employer
85
Billing Provider
87
Pay-to Provider
95
Research Institute
CK
Pharmacist
CZ
Admitting Surgeon
D2
Commercial Insurer
DD
Assistant Surgeon
DJ
Consulting Physician
DK
Ordering Physician
DN
Referring Provider
DO
Dependent Name
DQ
Supervising Physician
E1
Person or Other Entity Legally Responsible for a Child
E2
Person or Other Entity With Whom a Child Resides
E7
Previous Employer
E9
Participating Laboratory
FA
Facility
FD
Physical Address
FE
Mail Address
G0
Dependent Insured
G3
Clinic
GB
Other Insured
GD
Guardian
GI
Paramedic
GJ
Paramedical Company
GK
Previous Insured
GM
Spouse Insured
GY
Treatment Facility
HF
Healthcare Professional Shortage Area (HPSA) Facility
HH
Home Health Agency
I3
Independent Physicians Association (IPA)
IJ
Injection Point
IL
Insured or Subscriber
IN
Insurer
LI
Independent Lab
LR
Legal Representative
MR
Medical Insurance Carrier
MSC
Mammography Screening Center
OB
Ordered By
OD
Doctor of Optometry
OX
Oxygen Therapy Facility
P0
Patient Facility
P2
Primary Insured or Subscriber
P3
Primary Care Provider
P4
Prior Insurance Carrier
P6
Third Party Reviewing Preferred Provider Organization (PPO)
P7
Third Party Repricing Preferred Provider Organization (PPO)
PRP
Primary Payer
PT
Party to Receive Test Report
PV
Party performing certification
PW
Pickup Address
QA
Pharmacy
QB
Purchase Service Provider
QC
Patient
QD
Responsible Party
QE
Policyholder
QH
Physician
QK
Managed Care
QL
Chiropractor
QN
Dentist
QO
Doctor of Osteopathy
QS
Podiatrist
QV
Group Practice
QY
Medical Doctor
RC
Receiving Location
RW
Rural Health Clinic
S4
Skilled Nursing Facility
SEP
Secondary Payer
SJ
Service Provider
SU
Supplier/Manufacturer
T4
Transfer Point
Used to identify the geographic location where a patient is transferred or diverted.
TL
Testing Laboratory
TQ
Third Party Reviewing Organization (TPO)
TT
Transfer To
TTP
Tertiary Payer
TU
Third Party Repricing Organization (TPO)
UH
Nursing Home
X3
Utilization Management Organization
X4
Spouse
X5
Durable Medical Equipment Supplier
ZZ
Mutually Defined
Situational
1-4
1270
Code List Qualifier Code
O 1
ID
1/3
Code identifying a specific industry code list
SITUATIONAL RULE: Required when using a National Council for Prescription Drug Programs Reject/Payment Code in STC01-2 for status related to a pharmacy claim. If not required by this implementation guide, do not send.
CODE
DEFINITION
RX
National Council for Prescription Drug Programs Reject/Payment Codes
CODE SOURCE 530: National Council for Prescription Drug Programs Reject/Payment Codes
Required
2
373
Date
O 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: STC02 is the effective date of the status information.
INDUSTRY NAME: Status Information Effective Date
This is the date the claim was placed in this status by the Information Source's adjudication process.
Not Used
3
306
Action Code
O 1
ID
1/2
Situational
4
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: STC04 is the amount of original submitted charges.
SITUATIONAL RULE: Required when the response provides status on a claim found in the Information Source's system. If not required by this implementation guide, do not send.
INDUSTRY NAME: Total Claim Charge Amount
The total claim charge may change from the submitted claim total charge based on claims processing instructions, i.e. claim splitting. Some payers may not store the original submitted charge. Some HMO encounters supply zero as the amount of original charges.
Situational
5
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: STC05 is the amount paid.
SITUATIONAL RULE: Required when the remittance cycle is complete and a remittance advice has been issued. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
INDUSTRY NAME: Claim Payment Amount
  1. Zero is an acceptable amount when no payment is being made.
  2. Some payers are able to provide the adjudicated payment amount prior to the remittance being issued.
Situational
6
373
Date
O 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: STC06 is the paid date.
SITUATIONAL RULE: Required when the remittance cycle is complete and a remittance advice has been issued. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
INDUSTRY NAME: Adjudication Finalized Date
  1. This is the date of denial or approval for the claim. This date may or may not be the same as the issue date of the check, EFT or non-payment remittance (STC08).
  2. Some payers are able to provide the final claim adjudicated date prior to the remittance being issued.
Not Used
7
591
Payment Method Code
O 1
ID
3
Situational
8
373
Date
O 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: STC08 is the check issue date.
SITUATIONAL RULE: Required when the remittance cycle is complete and this claim is included on a check or EFT that is reported in an 835 or paper remittance to the provider. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
INDUSTRY NAME: Remittance Date
  1. This is the check issue or EFT funds available date.
  2. This could include a non-payment remittance advice date if available from the Information Source's system.
Situational
9
429
Check Number
O 1
AN
1/16
Check identification number
SITUATIONAL RULE: Required when the remittance cycle is complete and this claim is included on a check or EFT that is reported in an 835 or paper remittance to the provider. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
INDUSTRY NAME: Remittance Trace Number
  1. This is the check or EFT Trace Number.
  2. This could include a non-payment remittance advice Trace Number (835 or paper) if available from the Information Source's system.
Situational
10
C043
Health Care Claim Status
O 1
Used to convey status of the entire claim or a specific service line
X12 COMPOSITE SEMANTIC NOTES:
  1. C043-01 is used to specify the logical groupings of Health Care Claim Status Codes (See Code Source 507).
  2. C043-02 is used to identify the status of an entire claim or a serviceline. Code Source 508 is referenced unless qualified by C043-04.
  3. C043-03 identifies the entity associated with the Health Care Claim Status Code.
  4. C043-04 is used to identify the Code Source referenced in C043-02.
SITUATIONAL RULE: Required when a second claim status is needed. If not required by this implementation guide, do not send.
Required
10-1
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Health Care Claim Status Category Code
See STC01-1 for valid values.
Required
10-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Status Code
  1. The Status Code is either a Health Care Claim Status Code (Code Source 508) or a National Council for Prescription Drug Programs Reject/Payment Code (Code Source 530).
  2. The National Council for Prescription Drug Programs Reject/Payment Codes may be used for status related to pharmacy claims. When these codes are used, STC10-4 must have the value `RX'.
Situational
10-3
98
Entity Identifier Code
O 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
SITUATIONAL RULE: Required when an entity must be identified to further clarify the code message in STC10-2. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
See STC01-3 for valid values.
CODE
DEFINITION
03
Dependent
13
Contracted Service Provider
17
Consultant's Office
1E
Health Maintenance Organization (HMO)
1G
Oncology Center
1H
Kidney Dialysis Unit
1I
Preferred Provider Organization (PPO)
1O
Acute Care Hospital
1P
Provider
1Q
Military Facility
1R
University, College or School
1S
Outpatient Surgicenter
1T
Physician, Clinic or Group Practice
1U
Long Term Care Facility
1V
Extended Care Facility
1W
Psychiatric Health Facility
1X
Laboratory
1Y
Retail Pharmacy
1Z
Home Health Care
28
Subcontractor
2A
Federal, State, County or City Facility
2B
Third-Party Administrator
2D
Miscellaneous Health Care Facility
2E
Non-Health Care Miscellaneous Facility
2I
Church Operated Facility
2K
Partnership
2P
Public Health Service Facility
2Q
Veterans Administration Facility
2S
Public Health Service Indian Service Facility
2Z
Hospital Unit of an Institution (prison hospital, college infirmary, etc.)
30
Service Supplier
36
Employer
3A
Hospital Unit Within an Institution for the Mentally Retarded
3C
Tuberculosis and Other Respiratory Diseases Facility
3D
Obstetrics and Gynecology Facility
3E
Eye, Ear, Nose and Throat Facility
3F
Rehabilitation Facility
3G
Orthopedic Facility
3H
Chronic Disease Facility
3I
Other Specialty Facility
3J
Children's General Facility
3K
Children's Hospital Unit of an Institution
3L
Children's Psychiatric Facility
3M
Children's Tuberculosis and Other Respiratory Diseases Facility
3N
Children's Eye, Ear, Nose and Throat Facility
3O
Children's Rehabilitation Facility
3P
Children's Orthopedic Facility
3Q
Children's Chronic Disease Facility
3R
Children's Other Specialty Facility
3S
Institution for Mental Retardation
3T
Alcoholism and Other Chemical Dependency Facility
3U
General Inpatient Care for AIDS/ARC Facility
3V
AIDS/ARC Unit
3W
Specialized Outpatient Program for AIDS/ARC
3X
Alcohol/Drug Abuse or Dependency Inpatient Unit
3Y
Alcohol/Drug Abuse or Dependency Outpatient Services
3Z
Arthritis Treatment Center
40
Receiver
43
Claimant Authorized Representative
44
Data Processing Service Bureau
4A
Birthing Room/LDRP Room
4B
Burn Care Unit
4C
Cardiac Catherization Laboratory
4D
Open-Heart Surgery Facility
4E
Cardiac Intensive Care Unit
4F
Angioplasty Facility
4G
Chronic Obstructive Pulmonary Disease Service Facility
4H
Emergency Department
4I
Trauma Center (Certified)
4J
Extracorporeal Shock-Wave Lithotripter (ESWL) Unit
4L
Genetic Counseling/Screening Services
4M
Adult Day Care Program Facility
4N
Alzheimer's Diagnostic/Assessment Services
4O
Comprehensive Geriatric Assessment Facility
4P
Emergency Response (Geriatric) Unit
4Q
Geriatric Acute Care Unit
4R
Geriatric Clinics
4S
Respite Care Facility
4U
Patient Education Unit
4V
Community Health Promotion Facility
4W
Worksite Health Promotion Facility
4X
Hemodialysis Facility
4Y
Home Health Services
4Z
Hospice
5A
Medical Surgical or Other Intensive Care Unit
5B
Hisopathology Laboratory
5C
Blood Bank
5D
Neonatal Intensive Care Unit
5E
Obstetrics Unit
5F
Occupational Health Services
5G
Organized Outpatient Services
5H
Pediatric Acute Inpatient Unit
5I
Psychiatric Child/Adolescent Services
5J
Psychiatric Consultation-Liaison Services
5K
Psychiatric Education Services
5L
Psychiatric Emergency Services
5M
Psychiatric Geriatric Services
5N
Psychiatric Inpatient Unit
5O
Psychiatric Outpatient Services
5P
Psychiatric Partial Hospitalization Program
5Q
Megavoltage Radiation Therapy Unit
5R
Radioactive Implants Unit
5S
Therapeutic Radioisotope Facility
5T
X-Ray Radiation Therapy Unit
5U
CT Scanner Unit
5V
Diagnostic Radioisotope Facility
5W
Magnetic Resonance Imaging (MRI) Facility
5X
Ultrasound Unit
5Y
Rehabilitation Inpatient Unit
5Z
Rehabilitation Outpatient Services
61
Performed At
6A
Reproductive Health Services
6B
Skilled Nursing or Other Long-Term Care Unit
6C
Single Photon Emission Computerized Tomography (SPECT) Unit
6D
Organized Social Work Service Facility
6E
Outpatient Social Work Services
6F
Emergency Department Social Work Services
6G
Sports Medicine Clinic/Services
6H
Hospital Auxiliary Unit
6I
Patient Representative Services
6J
Volunteer Services Department
6K
Outpatient Surgery Services
6L
Organ/Tissue Transplant Unit
6M
Orthopedic Surgery Facility
6N
Occupational Therapy Services
6O
Physical Therapy Services
6P
Recreational Therapy Services
6Q
Respiratory Therapy Services
6R
Speech Therapy Services
6S
Women's Health Center/Services
6U
Cardiac Rehabilitation Program Facility
6V
Non-Invasive Cardiac Assessment Services
6W
Emergency Medical Technician
6X
Disciplinary Contact
6Y
Case Manager
71
Attending Physician
72
Operating Physician
73
Other Physician
74
Corrected Insured
77
Service Location
7C
Place of Occurrence
80
Hospital
82
Rendering Provider
84
Subscriber's Employer
85
Billing Provider
87
Pay-to Provider
95
Research Institute
CK
Pharmacist
CZ
Admitting Surgeon
D2
Commercial Insurer
DD
Assistant Surgeon
DJ
Consulting Physician
DK
Ordering Physician
DN
Referring Provider
DO
Dependent Name
DQ
Supervising Physician
E1
Person or Other Entity Legally Responsible for a Child
E2
Person or Other Entity With Whom a Child Resides
E7
Previous Employer
E9
Participating Laboratory
FA
Facility
FD
Physical Address
FE
Mail Address
G0
Dependent Insured
G3
Clinic
GB
Other Insured
GD
Guardian
GI
Paramedic
GJ
Paramedical Company
GK
Previous Insured
GM
Spouse Insured
GY
Treatment Facility
HF
Healthcare Professional Shortage Area (HPSA) Facility
HH
Home Health Agency
I3
Independent Physicians Association (IPA)
IJ
Injection Point
IL
Insured or Subscriber
IN
Insurer
LI
Independent Lab
LR
Legal Representative
MR
Medical Insurance Carrier
MSC
Mammography Screening Center
OB
Ordered By
OD
Doctor of Optometry
OX
Oxygen Therapy Facility
P0
Patient Facility
P2
Primary Insured or Subscriber
P3
Primary Care Provider
P4
Prior Insurance Carrier
P6
Third Party Reviewing Preferred Provider Organization (PPO)
P7
Third Party Repricing Preferred Provider Organization (PPO)
PRP
Primary Payer
PT
Party to Receive Test Report
PV
Party performing certification
PW
Pickup Address
QA
Pharmacy
QB
Purchase Service Provider
QC
Patient
QD
Responsible Party
QE
Policyholder
QH
Physician
QK
Managed Care
QL
Chiropractor
QN
Dentist
QO
Doctor of Osteopathy
QS
Podiatrist
QV
Group Practice
QY
Medical Doctor
RC
Receiving Location
RW
Rural Health Clinic
S4
Skilled Nursing Facility
SEP
Secondary Payer
SJ
Service Provider
SU
Supplier/Manufacturer
T4
Transfer Point
Used to identify the geographic location where a patient is transferred or diverted.
TL
Testing Laboratory
TQ
Third Party Reviewing Organization (TPO)
TT
Transfer To
TTP
Tertiary Payer
TU
Third Party Repricing Organization (TPO)
UH
Nursing Home
X3
Utilization Management Organization
X4
Spouse
X5
Durable Medical Equipment Supplier
ZZ
Mutually Defined
Situational
10-4
1270
Code List Qualifier Code
O 1
ID
1/3
Code identifying a specific industry code list
SITUATIONAL RULE: Required when using a National Council for Prescription Drug Programs Reject/Payment Code in STC10-2 for status related to a pharmacy claim. If not required by this implementation guide, do not send.
CODE
DEFINITION
RX
National Council for Prescription Drug Programs Reject/Payment Codes
CODE SOURCE 530: National Council for Prescription Drug Programs Reject/Payment Codes
Situational
11
C043
Health Care Claim Status
O 1
Used to convey status of the entire claim or a specific service line
X12 COMPOSITE SEMANTIC NOTES:
  1. C043-01 is used to specify the logical groupings of Health Care Claim Status Codes (See Code Source 507).
  2. C043-02 is used to identify the status of an entire claim or a serviceline. Code Source 508 is referenced unless qualified by C043-04.
  3. C043-03 identifies the entity associated with the Health Care Claim Status Code.
  4. C043-04 is used to identify the Code Source referenced in C043-02.
SITUATIONAL RULE: Required when a third claim status is needed. If not required by this implementation guide, do not send.
Required
11-1
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Health Care Claim Status Category Code
See STC01-1 for valid values.
Required
11-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Status Code
  1. The Status Code is either a Health Care Claim Status Code (Code Source 508) or a National Council for Prescription Drug Programs Reject/Payment Code (Code Source 530).
  2. The National Council for Prescription Drug Programs Reject/Payment Codes may be used for status related to pharmacy claims. When these codes are used, STC11-4 must have the value `RX'.
Situational
11-3
98
Entity Identifier Code
O 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
SITUATIONAL RULE: Required when an entity must be identified to further clarify the code message in STC11-2. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
See STC01-3 for valid values.
CODE
DEFINITION
03
Dependent
13
Contracted Service Provider
17
Consultant's Office
1E
Health Maintenance Organization (HMO)
1G
Oncology Center
1H
Kidney Dialysis Unit
1I
Preferred Provider Organization (PPO)
1O
Acute Care Hospital
1P
Provider
1Q
Military Facility
1R
University, College or School
1S
Outpatient Surgicenter
1T
Physician, Clinic or Group Practice
1U
Long Term Care Facility
1V
Extended Care Facility
1W
Psychiatric Health Facility
1X
Laboratory
1Y
Retail Pharmacy
1Z
Home Health Care
28
Subcontractor
2A
Federal, State, County or City Facility
2B
Third-Party Administrator
2D
Miscellaneous Health Care Facility
2E
Non-Health Care Miscellaneous Facility
2I
Church Operated Facility
2K
Partnership
2P
Public Health Service Facility
2Q
Veterans Administration Facility
2S
Public Health Service Indian Service Facility
2Z
Hospital Unit of an Institution (prison hospital, college infirmary, etc.)
30
Service Supplier
36
Employer
3A
Hospital Unit Within an Institution for the Mentally Retarded
3C
Tuberculosis and Other Respiratory Diseases Facility
3D
Obstetrics and Gynecology Facility
3E
Eye, Ear, Nose and Throat Facility
3F
Rehabilitation Facility
3G
Orthopedic Facility
3H
Chronic Disease Facility
3I
Other Specialty Facility
3J
Children's General Facility
3K
Children's Hospital Unit of an Institution
3L
Children's Psychiatric Facility
3M
Children's Tuberculosis and Other Respiratory Diseases Facility
3N
Children's Eye, Ear, Nose and Throat Facility
3O
Children's Rehabilitation Facility
3P
Children's Orthopedic Facility
3Q
Children's Chronic Disease Facility
3R
Children's Other Specialty Facility
3S
Institution for Mental Retardation
3T
Alcoholism and Other Chemical Dependency Facility
3U
General Inpatient Care for AIDS/ARC Facility
3V
AIDS/ARC Unit
3W
Specialized Outpatient Program for AIDS/ARC
3X
Alcohol/Drug Abuse or Dependency Inpatient Unit
3Y
Alcohol/Drug Abuse or Dependency Outpatient Services
3Z
Arthritis Treatment Center
40
Receiver
43
Claimant Authorized Representative
44
Data Processing Service Bureau
4A
Birthing Room/LDRP Room
4B
Burn Care Unit
4C
Cardiac Catherization Laboratory
4D
Open-Heart Surgery Facility
4E
Cardiac Intensive Care Unit
4F
Angioplasty Facility
4G
Chronic Obstructive Pulmonary Disease Service Facility
4H
Emergency Department
4I
Trauma Center (Certified)
4J
Extracorporeal Shock-Wave Lithotripter (ESWL) Unit
4L
Genetic Counseling/Screening Services
4M
Adult Day Care Program Facility
4N
Alzheimer's Diagnostic/Assessment Services
4O
Comprehensive Geriatric Assessment Facility
4P
Emergency Response (Geriatric) Unit
4Q
Geriatric Acute Care Unit
4R
Geriatric Clinics
4S
Respite Care Facility
4U
Patient Education Unit
4V
Community Health Promotion Facility
4W
Worksite Health Promotion Facility
4X
Hemodialysis Facility
4Y
Home Health Services
4Z
Hospice
5A
Medical Surgical or Other Intensive Care Unit
5B
Hisopathology Laboratory
5C
Blood Bank
5D
Neonatal Intensive Care Unit
5E
Obstetrics Unit
5F
Occupational Health Services
5G
Organized Outpatient Services
5H
Pediatric Acute Inpatient Unit
5I
Psychiatric Child/Adolescent Services
5J
Psychiatric Consultation-Liaison Services
5K
Psychiatric Education Services
5L
Psychiatric Emergency Services
5M
Psychiatric Geriatric Services
5N
Psychiatric Inpatient Unit
5O
Psychiatric Outpatient Services
5P
Psychiatric Partial Hospitalization Program
5Q
Megavoltage Radiation Therapy Unit
5R
Radioactive Implants Unit
5S
Therapeutic Radioisotope Facility
5T
X-Ray Radiation Therapy Unit
5U
CT Scanner Unit
5V
Diagnostic Radioisotope Facility
5W
Magnetic Resonance Imaging (MRI) Facility
5X
Ultrasound Unit
5Y
Rehabilitation Inpatient Unit
5Z
Rehabilitation Outpatient Services
61
Performed At
6A
Reproductive Health Services
6B
Skilled Nursing or Other Long-Term Care Unit
6C
Single Photon Emission Computerized Tomography (SPECT) Unit
6D
Organized Social Work Service Facility
6E
Outpatient Social Work Services
6F
Emergency Department Social Work Services
6G
Sports Medicine Clinic/Services
6H
Hospital Auxiliary Unit
6I
Patient Representative Services
6J
Volunteer Services Department
6K
Outpatient Surgery Services
6L
Organ/Tissue Transplant Unit
6M
Orthopedic Surgery Facility
6N
Occupational Therapy Services
6O
Physical Therapy Services
6P
Recreational Therapy Services
6Q
Respiratory Therapy Services
6R
Speech Therapy Services
6S
Women's Health Center/Services
6U
Cardiac Rehabilitation Program Facility
6V
Non-Invasive Cardiac Assessment Services
6W
Emergency Medical Technician
6X
Disciplinary Contact
6Y
Case Manager
71
Attending Physician
72
Operating Physician
73
Other Physician
74
Corrected Insured
77
Service Location
7C
Place of Occurrence
80
Hospital
82
Rendering Provider
84
Subscriber's Employer
85
Billing Provider
87
Pay-to Provider
95
Research Institute
CK
Pharmacist
CZ
Admitting Surgeon
D2
Commercial Insurer
DD
Assistant Surgeon
DJ
Consulting Physician
DK
Ordering Physician
DN
Referring Provider
DO
Dependent Name
DQ
Supervising Physician
E1
Person or Other Entity Legally Responsible for a Child
E2
Person or Other Entity With Whom a Child Resides
E7
Previous Employer
E9
Participating Laboratory
FA
Facility
FD
Physical Address
FE
Mail Address
G0
Dependent Insured
G3
Clinic
GB
Other Insured
GD
Guardian
GI
Paramedic
GJ
Paramedical Company
GK
Previous Insured
GM
Spouse Insured
GY
Treatment Facility
HF
Healthcare Professional Shortage Area (HPSA) Facility
HH
Home Health Agency
I3
Independent Physicians Association (IPA)
IJ
Injection Point
IL
Insured or Subscriber
IN
Insurer
LI
Independent Lab
LR
Legal Representative
MR
Medical Insurance Carrier
MSC
Mammography Screening Center
OB
Ordered By
OD
Doctor of Optometry
OX
Oxygen Therapy Facility
P0
Patient Facility
P2
Primary Insured or Subscriber
P3
Primary Care Provider
P4
Prior Insurance Carrier
P6
Third Party Reviewing Preferred Provider Organization (PPO)
P7
Third Party Repricing Preferred Provider Organization (PPO)
PRP
Primary Payer
PT
Party to Receive Test Report
PV
Party performing certification
PW
Pickup Address
QA
Pharmacy
QB
Purchase Service Provider
QC
Patient
QD
Responsible Party
QE
Policyholder
QH
Physician
QK
Managed Care
QL
Chiropractor
QN
Dentist
QO
Doctor of Osteopathy
QS
Podiatrist
QV
Group Practice
QY
Medical Doctor
RC
Receiving Location
RW
Rural Health Clinic
S4
Skilled Nursing Facility
SEP
Secondary Payer
SJ
Service Provider
SU
Supplier/Manufacturer
T4
Transfer Point
Used to identify the geographic location where a patient is transferred or diverted.
TL
Testing Laboratory
TQ
Third Party Reviewing Organization (TPO)
TT
Transfer To
TTP
Tertiary Payer
TU
Third Party Repricing Organization (TPO)
UH
Nursing Home
X3
Utilization Management Organization
X4
Spouse
X5
Durable Medical Equipment Supplier
ZZ
Mutually Defined
Situational
11-4
1270
Code List Qualifier Code
O 1
ID
1/3
Code identifying a specific industry code list
SITUATIONAL RULE: Required when using a National Council for Prescription Drug Programs Reject/Payment Code in STC11-2 for status related to a pharmacy claim. If not required by this implementation guide, do not send.
CODE
DEFINITION
RX
National Council for Prescription Drug Programs Reject/Payment Codes
CODE SOURCE 530: National Council for Prescription Drug Programs Reject/Payment Codes
Not Used
12
933
Free-form Message Text
O 1
AN
1/264

REF*1K - 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 a claim is located in the Information Source's system. If not required by this implementation guide, do not send.
TR3 Notes:
This is the payer's assigned control number, also known as, Internal Control Number (ICN), Document Control Number (DCN), or Claim Control Number (CCN).
TR3 Example:
REF✱1K✱9918046987~
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
1K
Payor's 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: Payer Claim Control Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*BLT - INSTITUTIONAL BILL TYPE 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 on institutional claims when different than the value submitted on the 276 request. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
TR3 Example:
REF✱BLT✱111~
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
BLT
Billing Type
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: Bill Type Identifier
Concatenate the 837I CLM05-1 (Facility Type Code) and CLM05-3 (Claim Frequency Code) values.
Code Source 236: Uniform Billing Claim Form Bill Type
Code Source 235: Claim Frequency Type Code
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*EJ - PATIENT 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 Patient Control Number was submitted on the 276 request or when available on claims located in the Information Source's system. If not required by this implementation guide, do not send.
TR3 Notes:
The maximum number of characters supported for the Patient Control Number is `20'.
TR3 Example:
REF✱EJ✱PT12345~
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
EJ
Patient Account 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: Patient Control Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*XZ - PHARMACY PRESCRIPTION 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 Pharmacy Prescription Number was submitted on the 276 request or when available on claims located in the Information Source's system. If not required by this implementation guide, do not send.
TR3 Example:
REF✱XZ✱1234567~
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
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: Pharmacy Prescription Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*VV - VOUCHER 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 a voucher identifier is associated with the response claim. If not required by this implementation guide, do not send.
TR3 Notes:
Some payers assign voucher identifiers to a group of claims as part of the payment process prior to payment being issued.
TR3 Example:
REF✱VV✱V123~
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
VV
Voucher
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: Voucher Identifier
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*D9 - CLAIM IDENTIFICATION NUMBER FOR CLEARINGHOUSES AND OTHER 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 received on the 276 status request. If not required by this implementation guide, do not send.
TR3 Example:
REF✱D9✱20041513010001~
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
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: Clearinghouse Trace Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

DTP*472 - CLAIM SERVICE DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required for institutional claims or for professional and dental claims when the service line date is not used. 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. For professional claims, this date is derived from the service level dates.
  2. When reporting a claim level date, use the date from the Information Source's system for claim matches, otherwise return the date from the 276 status request.
TR3 Example:
DTP✱472✱RD8✱20050401-20050402~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
472
Service
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
RD8
Range of Dates Expressed in Format CCYYMMDD-CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Claim Service Period

SVC - SERVICE LINE INFORMATION

X12 Name:
Service Information
X12 Purpose:
To supply payment and control information to a provider for a particular service
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when reporting status for Service Lines. If not required by this implementation guide, do not send.
TR3 Notes:
For Institutional claims, when both an NUBC revenue code and a HCPCS or HIPPS code are reported, the HCPCS or HIPPS code is reported in SVC01-2 and the revenue code is reported in SVC04. When only a revenue code is used, it is reported in SVC01-2.
TR3 Example:
SVC✱HC:99214✱75✱50✱✱✱✱1~ orSVC✱NU:0710✱50✱0✱✱✱✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
C003
Composite Medical Procedure Identifier
M 1
To identify a medical procedure by its standardized codes and applicable modifiers
SEMANTIC: SVC01 is the medical procedure upon which adjudication is based.
COMMENT: For Medicare Part A claims, SVC01 would be the Health Care Financing Administration (HCFA) Common Procedural Coding System (HCPCS) Code (see code source 130) and SVC04 would be the Revenue Code (see code source 132).
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.
SVC01-2 contains the adjudicated procedure code. This code may be different than the original submitted procedure code based on the payer's claim processing.
Required
1-1
235
Product/Service ID Qualifier
M 1
ID
2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
INDUSTRY NAME: Product or Service ID Qualifier
CODE
DEFINITION
AD
American Dental Association Codes
CODE SOURCE 135: American Dental Association
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 CPT codes of the American Medical Association are also level 1 HCPCS codes, the CPT codes are reported under the code HC.
CODE SOURCE 130: Healthcare Common Procedural Coding System
HP
Health Insurance Prospective Payment System (HIPPS) Skilled Nursing Facility Rate Code
CODE SOURCE 716: Health Insurance Prospective Payment System (HIPPS) Rate Code for Skilled Nursing Facilities
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 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
N4
National Drug Code in 5-4-2 Format
CODE SOURCE 240: National Drug Code by Format
NU
National Uniform Billing Committee (NUBC) UB92 Codes
This code is the NUBC Revenue Code.
CODE SOURCE 132: National Uniform Billing Committee (NUBC) Codes
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
If the value in SVC01-1 is "NU", then this is an NUBC Revenue Code. If the revenue code is present here, then SVC04 is not used.
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 modifiers have been applied to the adjudicated procedure code reported in SVC01-2. 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 modifiers have been applied to the adjudicated procedure code reported in SVC01-2. 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 modifiers have been applied to the adjudicated procedure code reported in SVC01-2. 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 modifiers have been applied to the adjudicated procedure code reported in SVC01-2. If not required by this implementation guide, do not send.
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
782
Monetary Amount
M 1
R
1/18
Monetary amount
SEMANTIC: SVC02 is the submitted service charge.
INDUSTRY NAME: Line Item Charge Amount
This is the line item total on the current claim service status.
Required
3
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: SVC03 is the amount paid this service.
INDUSTRY NAME: Line Item Payment Amount
Situational
4
234
Product/Service ID
O 1
AN
1/48
Identifying number for a product or service
SEMANTIC: SVC04 is the National Uniform Billing Committee Revenue Code.
SITUATIONAL RULE: Required on institutional claims when an NUBC revenue code needs to be reported in addition to a HCPCS or HIPPS code reported in SVC01-2. If not required by this implementation guide, do not send.
INDUSTRY NAME: Revenue Code
Not Used
5
380
Quantity
O 1
R
1/15
Not Used
6
C003
Composite Medical Procedure Identifier
O 1
Required
7
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: SVC07 is the original submitted units of service.
INDUSTRY NAME: Units of Service Count

STC - SERVICE LINE STATUS INFORMATION

X12 Name:
Status Information
X12 Purpose:
To report the status, required action, and paid information of a claim or service line
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
>1
TR3 Notes:
See Section 1.4.3 - Status Information (STC) Segment Usage for specific STC segment information related to the hierarchical level, composites and code use.
TR3 Example:
STC✱F1:65✱20050501~ orSTC✱A3:110✱20050501✱✱✱✱✱✱✱✱A3:400~ or STC✱F2:79::RX✱20050501~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
C043
Health Care Claim Status
M 1
Used to convey status of the entire claim or a specific service line
X12 COMPOSITE SEMANTIC NOTES:
  1. C043-01 is used to specify the logical groupings of Health Care Claim Status Codes (See Code Source 507).
  2. C043-02 is used to identify the status of an entire claim or a serviceline. Code Source 508 is referenced unless qualified by C043-04.
  3. C043-03 identifies the entity associated with the Health Care Claim Status Code.
  4. C043-04 is used to identify the Code Source referenced in C043-02.
Required
1-1
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Health Care Claim Status Category Code
All Category Codes except `Request for Additional Information' (R Category Codes) are allowable at this level.
Required
1-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Status Code
  1. The Status Code is either a Health Care Claim Status Code (Code Source 508) or a National Council for Prescription Drug Programs Reject/Payment Code (Code Source 530).
  2. The National Council for Prescription Drug Programs Reject/Payment Codes may be used for status related to pharmacy claims. When these codes are used, STC01-4 must have the value `RX'.
Situational
1-3
98
Entity Identifier Code
O 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
SITUATIONAL RULE: Required when an entity must be identified to further clarify the code message in STC01-2. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
CODE
DEFINITION
03
Dependent
13
Contracted Service Provider
17
Consultant's Office
1E
Health Maintenance Organization (HMO)
1G
Oncology Center
1H
Kidney Dialysis Unit
1I
Preferred Provider Organization (PPO)
1O
Acute Care Hospital
1P
Provider
1Q
Military Facility
1R
University, College or School
1S
Outpatient Surgicenter
1T
Physician, Clinic or Group Practice
1U
Long Term Care Facility
1V
Extended Care Facility
1W
Psychiatric Health Facility
1X
Laboratory
1Y
Retail Pharmacy
1Z
Home Health Care
28
Subcontractor
2A
Federal, State, County or City Facility
2B
Third-Party Administrator
2D
Miscellaneous Health Care Facility
2E
Non-Health Care Miscellaneous Facility
2I
Church Operated Facility
2K
Partnership
2P
Public Health Service Facility
2Q
Veterans Administration Facility
2S
Public Health Service Indian Service Facility
2Z
Hospital Unit of an Institution (prison hospital, college infirmary, etc.)
30
Service Supplier
36
Employer
3A
Hospital Unit Within an Institution for the Mentally Retarded
3C
Tuberculosis and Other Respiratory Diseases Facility
3D
Obstetrics and Gynecology Facility
3E
Eye, Ear, Nose and Throat Facility
3F
Rehabilitation Facility
3G
Orthopedic Facility
3H
Chronic Disease Facility
3I
Other Specialty Facility
3J
Children's General Facility
3K
Children's Hospital Unit of an Institution
3L
Children's Psychiatric Facility
3M
Children's Tuberculosis and Other Respiratory Diseases Facility
3N
Children's Eye, Ear, Nose and Throat Facility
3O
Children's Rehabilitation Facility
3P
Children's Orthopedic Facility
3Q
Children's Chronic Disease Facility
3R
Children's Other Specialty Facility
3S
Institution for Mental Retardation
3T
Alcoholism and Other Chemical Dependency Facility
3U
General Inpatient Care for AIDS/ARC Facility
3V
AIDS/ARC Unit
3W
Specialized Outpatient Program for AIDS/ARC
3X
Alcohol/Drug Abuse or Dependency Inpatient Unit
3Y
Alcohol/Drug Abuse or Dependency Outpatient Services
3Z
Arthritis Treatment Center
40
Receiver
43
Claimant Authorized Representative
44
Data Processing Service Bureau
4A
Birthing Room/LDRP Room
4B
Burn Care Unit
4C
Cardiac Catherization Laboratory
4D
Open-Heart Surgery Facility
4E
Cardiac Intensive Care Unit
4F
Angioplasty Facility
4G
Chronic Obstructive Pulmonary Disease Service Facility
4H
Emergency Department
4I
Trauma Center (Certified)
4J
Extracorporeal Shock-Wave Lithotripter (ESWL) Unit
4L
Genetic Counseling/Screening Services
4M
Adult Day Care Program Facility
4N
Alzheimer's Diagnostic/Assessment Services
4O
Comprehensive Geriatric Assessment Facility
4P
Emergency Response (Geriatric) Unit
4Q
Geriatric Acute Care Unit
4R
Geriatric Clinics
4S
Respite Care Facility
4U
Patient Education Unit
4V
Community Health Promotion Facility
4W
Worksite Health Promotion Facility
4X
Hemodialysis Facility
4Y
Home Health Services
4Z
Hospice
5A
Medical Surgical or Other Intensive Care Unit
5B
Hisopathology Laboratory
5C
Blood Bank
5D
Neonatal Intensive Care Unit
5E
Obstetrics Unit
5F
Occupational Health Services
5G
Organized Outpatient Services
5H
Pediatric Acute Inpatient Unit
5I
Psychiatric Child/Adolescent Services
5J
Psychiatric Consultation-Liaison Services
5K
Psychiatric Education Services
5L
Psychiatric Emergency Services
5M
Psychiatric Geriatric Services
5N
Psychiatric Inpatient Unit
5O
Psychiatric Outpatient Services
5P
Psychiatric Partial Hospitalization Program
5Q
Megavoltage Radiation Therapy Unit
5R
Radioactive Implants Unit
5S
Therapeutic Radioisotope Facility
5T
X-Ray Radiation Therapy Unit
5U
CT Scanner Unit
5V
Diagnostic Radioisotope Facility
5W
Magnetic Resonance Imaging (MRI) Facility
5X
Ultrasound Unit
5Y
Rehabilitation Inpatient Unit
5Z
Rehabilitation Outpatient Services
61
Performed At
6A
Reproductive Health Services
6B
Skilled Nursing or Other Long-Term Care Unit
6C
Single Photon Emission Computerized Tomography (SPECT) Unit
6D
Organized Social Work Service Facility
6E
Outpatient Social Work Services
6F
Emergency Department Social Work Services
6G
Sports Medicine Clinic/Services
6H
Hospital Auxiliary Unit
6I
Patient Representative Services
6J
Volunteer Services Department
6K
Outpatient Surgery Services
6L
Organ/Tissue Transplant Unit
6M
Orthopedic Surgery Facility
6N
Occupational Therapy Services
6O
Physical Therapy Services
6P
Recreational Therapy Services
6Q
Respiratory Therapy Services
6R
Speech Therapy Services
6S
Women's Health Center/Services
6U
Cardiac Rehabilitation Program Facility
6V
Non-Invasive Cardiac Assessment Services
6W
Emergency Medical Technician
6X
Disciplinary Contact
6Y
Case Manager
71
Attending Physician
72
Operating Physician
73
Other Physician
74
Corrected Insured
77
Service Location
7C
Place of Occurrence
80
Hospital
82
Rendering Provider
84
Subscriber's Employer
85
Billing Provider
87
Pay-to Provider
95
Research Institute
CK
Pharmacist
CZ
Admitting Surgeon
D2
Commercial Insurer
DD
Assistant Surgeon
DJ
Consulting Physician
DK
Ordering Physician
DN
Referring Provider
DO
Dependent Name
DQ
Supervising Physician
E1
Person or Other Entity Legally Responsible for a Child
E2
Person or Other Entity With Whom a Child Resides
E7
Previous Employer
E9
Participating Laboratory
FA
Facility
FD
Physical Address
FE
Mail Address
G0
Dependent Insured
G3
Clinic
GB
Other Insured
GD
Guardian
GI
Paramedic
GJ
Paramedical Company
GK
Previous Insured
GM
Spouse Insured
GY
Treatment Facility
HF
Healthcare Professional Shortage Area (HPSA) Facility
HH
Home Health Agency
I3
Independent Physicians Association (IPA)
IJ
Injection Point
IL
Insured or Subscriber
IN
Insurer
LI
Independent Lab
LR
Legal Representative
MR
Medical Insurance Carrier
MSC
Mammography Screening Center
OB
Ordered By
OD
Doctor of Optometry
OX
Oxygen Therapy Facility
P0
Patient Facility
P2
Primary Insured or Subscriber
P3
Primary Care Provider
P4
Prior Insurance Carrier
P6
Third Party Reviewing Preferred Provider Organization (PPO)
P7
Third Party Repricing Preferred Provider Organization (PPO)
PRP
Primary Payer
PT
Party to Receive Test Report
PV
Party performing certification
PW
Pickup Address
QA
Pharmacy
QB
Purchase Service Provider
QC
Patient
QD
Responsible Party
QE
Policyholder
QH
Physician
QK
Managed Care
QL
Chiropractor
QN
Dentist
QO
Doctor of Osteopathy
QS
Podiatrist
QV
Group Practice
QY
Medical Doctor
RC
Receiving Location
RW
Rural Health Clinic
S4
Skilled Nursing Facility
SEP
Secondary Payer
SJ
Service Provider
SU
Supplier/Manufacturer
T4
Transfer Point
Used to identify the geographic location where a patient is transferred or diverted.
TL
Testing Laboratory
TQ
Third Party Reviewing Organization (TPO)
TT
Transfer To
TTP
Tertiary Payer
TU
Third Party Repricing Organization (TPO)
UH
Nursing Home
X3
Utilization Management Organization
X4
Spouse
X5
Durable Medical Equipment Supplier
ZZ
Mutually Defined
Situational
1-4
1270
Code List Qualifier Code
O 1
ID
1/3
Code identifying a specific industry code list
SITUATIONAL RULE: Required when using a National Council for Prescription Drug Programs Reject/Payment Code in STC01-2 for status related to a pharmacy claim. If not required by this implementation guide, do not send.
CODE
DEFINITION
RX
National Council for Prescription Drug Programs Reject/Payment Codes
CODE SOURCE 530: National Council for Prescription Drug Programs Reject/Payment Codes
Required
2
373
Date
O 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: STC02 is the effective date of the status information.
INDUSTRY NAME: Status Information Effective Date
This is the date the service was placed in this status by the Information Source's adjudication process.
Not Used
3
306
Action Code
O 1
ID
1/2
Not Used
4
782
Monetary Amount
O 1
R
1/18
Not Used
5
782
Monetary Amount
O 1
R
1/18
Not Used
6
373
Date
O 1
DT
8
Not Used
7
591
Payment Method Code
O 1
ID
3
Not Used
8
373
Date
O 1
DT
8
Not Used
9
429
Check Number
O 1
AN
1/16
Situational
10
C043
Health Care Claim Status
O 1
Used to convey status of the entire claim or a specific service line
X12 COMPOSITE SEMANTIC NOTES:
  1. C043-01 is used to specify the logical groupings of Health Care Claim Status Codes (See Code Source 507).
  2. C043-02 is used to identify the status of an entire claim or a serviceline. Code Source 508 is referenced unless qualified by C043-04.
  3. C043-03 identifies the entity associated with the Health Care Claim Status Code.
  4. C043-04 is used to identify the Code Source referenced in C043-02.
SITUATIONAL RULE: Required when a second claim status is needed. If not required by this implementation guide, do not send.
Required
10-1
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Health Care Claim Status Category Code
See STC01-1 for valid values.
Required
10-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Status Code
  1. The Status Code is either a Health Care Claim Status Code (Code Source 508) or a National Council for Prescription Drug Programs Reject/Payment Code (Code Source 530).
  2. The National Council for Prescription Drug Programs Reject/Payment Codes may be used for status related to pharmacy claims. When these codes are used, STC10-4 must have the value `RX'.
Situational
10-3
98
Entity Identifier Code
O 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
SITUATIONAL RULE: Required when an entity must be identified to further clarify the code message in STC10-2. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
See STC01-3 for valid values.
CODE
DEFINITION
03
Dependent
13
Contracted Service Provider
17
Consultant's Office
1E
Health Maintenance Organization (HMO)
1G
Oncology Center
1H
Kidney Dialysis Unit
1I
Preferred Provider Organization (PPO)
1O
Acute Care Hospital
1P
Provider
1Q
Military Facility
1R
University, College or School
1S
Outpatient Surgicenter
1T
Physician, Clinic or Group Practice
1U
Long Term Care Facility
1V
Extended Care Facility
1W
Psychiatric Health Facility
1X
Laboratory
1Y
Retail Pharmacy
1Z
Home Health Care
28
Subcontractor
2A
Federal, State, County or City Facility
2B
Third-Party Administrator
2D
Miscellaneous Health Care Facility
2E
Non-Health Care Miscellaneous Facility
2I
Church Operated Facility
2K
Partnership
2P
Public Health Service Facility
2Q
Veterans Administration Facility
2S
Public Health Service Indian Service Facility
2Z
Hospital Unit of an Institution (prison hospital, college infirmary, etc.)
30
Service Supplier
36
Employer
3A
Hospital Unit Within an Institution for the Mentally Retarded
3C
Tuberculosis and Other Respiratory Diseases Facility
3D
Obstetrics and Gynecology Facility
3E
Eye, Ear, Nose and Throat Facility
3F
Rehabilitation Facility
3G
Orthopedic Facility
3H
Chronic Disease Facility
3I
Other Specialty Facility
3J
Children's General Facility
3K
Children's Hospital Unit of an Institution
3L
Children's Psychiatric Facility
3M
Children's Tuberculosis and Other Respiratory Diseases Facility
3N
Children's Eye, Ear, Nose and Throat Facility
3O
Children's Rehabilitation Facility
3P
Children's Orthopedic Facility
3Q
Children's Chronic Disease Facility
3R
Children's Other Specialty Facility
3S
Institution for Mental Retardation
3T
Alcoholism and Other Chemical Dependency Facility
3U
General Inpatient Care for AIDS/ARC Facility
3V
AIDS/ARC Unit
3W
Specialized Outpatient Program for AIDS/ARC
3X
Alcohol/Drug Abuse or Dependency Inpatient Unit
3Y
Alcohol/Drug Abuse or Dependency Outpatient Services
3Z
Arthritis Treatment Center
40
Receiver
43
Claimant Authorized Representative
44
Data Processing Service Bureau
4A
Birthing Room/LDRP Room
4B
Burn Care Unit
4C
Cardiac Catherization Laboratory
4D
Open-Heart Surgery Facility
4E
Cardiac Intensive Care Unit
4F
Angioplasty Facility
4G
Chronic Obstructive Pulmonary Disease Service Facility
4H
Emergency Department
4I
Trauma Center (Certified)
4J
Extracorporeal Shock-Wave Lithotripter (ESWL) Unit
4L
Genetic Counseling/Screening Services
4M
Adult Day Care Program Facility
4N
Alzheimer's Diagnostic/Assessment Services
4O
Comprehensive Geriatric Assessment Facility
4P
Emergency Response (Geriatric) Unit
4Q
Geriatric Acute Care Unit
4R
Geriatric Clinics
4S
Respite Care Facility
4U
Patient Education Unit
4V
Community Health Promotion Facility
4W
Worksite Health Promotion Facility
4X
Hemodialysis Facility
4Y
Home Health Services
4Z
Hospice
5A
Medical Surgical or Other Intensive Care Unit
5B
Hisopathology Laboratory
5C
Blood Bank
5D
Neonatal Intensive Care Unit
5E
Obstetrics Unit
5F
Occupational Health Services
5G
Organized Outpatient Services
5H
Pediatric Acute Inpatient Unit
5I
Psychiatric Child/Adolescent Services
5J
Psychiatric Consultation-Liaison Services
5K
Psychiatric Education Services
5L
Psychiatric Emergency Services
5M
Psychiatric Geriatric Services
5N
Psychiatric Inpatient Unit
5O
Psychiatric Outpatient Services
5P
Psychiatric Partial Hospitalization Program
5Q
Megavoltage Radiation Therapy Unit
5R
Radioactive Implants Unit
5S
Therapeutic Radioisotope Facility
5T
X-Ray Radiation Therapy Unit
5U
CT Scanner Unit
5V
Diagnostic Radioisotope Facility
5W
Magnetic Resonance Imaging (MRI) Facility
5X
Ultrasound Unit
5Y
Rehabilitation Inpatient Unit
5Z
Rehabilitation Outpatient Services
61
Performed At
6A
Reproductive Health Services
6B
Skilled Nursing or Other Long-Term Care Unit
6C
Single Photon Emission Computerized Tomography (SPECT) Unit
6D
Organized Social Work Service Facility
6E
Outpatient Social Work Services
6F
Emergency Department Social Work Services
6G
Sports Medicine Clinic/Services
6H
Hospital Auxiliary Unit
6I
Patient Representative Services
6J
Volunteer Services Department
6K
Outpatient Surgery Services
6L
Organ/Tissue Transplant Unit
6M
Orthopedic Surgery Facility
6N
Occupational Therapy Services
6O
Physical Therapy Services
6P
Recreational Therapy Services
6Q
Respiratory Therapy Services
6R
Speech Therapy Services
6S
Women's Health Center/Services
6U
Cardiac Rehabilitation Program Facility
6V
Non-Invasive Cardiac Assessment Services
6W
Emergency Medical Technician
6X
Disciplinary Contact
6Y
Case Manager
71
Attending Physician
72
Operating Physician
73
Other Physician
74
Corrected Insured
77
Service Location
7C
Place of Occurrence
80
Hospital
82
Rendering Provider
84
Subscriber's Employer
85
Billing Provider
87
Pay-to Provider
95
Research Institute
CK
Pharmacist
CZ
Admitting Surgeon
D2
Commercial Insurer
DD
Assistant Surgeon
DJ
Consulting Physician
DK
Ordering Physician
DN
Referring Provider
DO
Dependent Name
DQ
Supervising Physician
E1
Person or Other Entity Legally Responsible for a Child
E2
Person or Other Entity With Whom a Child Resides
E7
Previous Employer
E9
Participating Laboratory
FA
Facility
FD
Physical Address
FE
Mail Address
G0
Dependent Insured
G3
Clinic
GB
Other Insured
GD
Guardian
GI
Paramedic
GJ
Paramedical Company
GK
Previous Insured
GM
Spouse Insured
GY
Treatment Facility
HF
Healthcare Professional Shortage Area (HPSA) Facility
HH
Home Health Agency
I3
Independent Physicians Association (IPA)
IJ
Injection Point
IL
Insured or Subscriber
IN
Insurer
LI
Independent Lab
LR
Legal Representative
MR
Medical Insurance Carrier
MSC
Mammography Screening Center
OB
Ordered By
OD
Doctor of Optometry
OX
Oxygen Therapy Facility
P0
Patient Facility
P2
Primary Insured or Subscriber
P3
Primary Care Provider
P4
Prior Insurance Carrier
P6
Third Party Reviewing Preferred Provider Organization (PPO)
P7
Third Party Repricing Preferred Provider Organization (PPO)
PRP
Primary Payer
PT
Party to Receive Test Report
PV
Party performing certification
PW
Pickup Address
QA
Pharmacy
QB
Purchase Service Provider
QC
Patient
QD
Responsible Party
QE
Policyholder
QH
Physician
QK
Managed Care
QL
Chiropractor
QN
Dentist
QO
Doctor of Osteopathy
QS
Podiatrist
QV
Group Practice
QY
Medical Doctor
RC
Receiving Location
RW
Rural Health Clinic
S4
Skilled Nursing Facility
SEP
Secondary Payer
SJ
Service Provider
SU
Supplier/Manufacturer
T4
Transfer Point
Used to identify the geographic location where a patient is transferred or diverted.
TL
Testing Laboratory
TQ
Third Party Reviewing Organization (TPO)
TT
Transfer To
TTP
Tertiary Payer
TU
Third Party Repricing Organization (TPO)
UH
Nursing Home
X3
Utilization Management Organization
X4
Spouse
X5
Durable Medical Equipment Supplier
ZZ
Mutually Defined
Situational
10-4
1270
Code List Qualifier Code
O 1
ID
1/3
Code identifying a specific industry code list
SITUATIONAL RULE: Required when using a National Council for Prescription Drug Programs Reject/Payment Code in STC10-2 for status related to a pharmacy claim. If not required by this implementation guide, do not send.
CODE
DEFINITION
RX
National Council for Prescription Drug Programs Reject/Payment Codes
CODE SOURCE 530: National Council for Prescription Drug Programs Reject/Payment Codes
Situational
11
C043
Health Care Claim Status
O 1
Used to convey status of the entire claim or a specific service line
X12 COMPOSITE SEMANTIC NOTES:
  1. C043-01 is used to specify the logical groupings of Health Care Claim Status Codes (See Code Source 507).
  2. C043-02 is used to identify the status of an entire claim or a serviceline. Code Source 508 is referenced unless qualified by C043-04.
  3. C043-03 identifies the entity associated with the Health Care Claim Status Code.
  4. C043-04 is used to identify the Code Source referenced in C043-02.
SITUATIONAL RULE: Required when a third claim status is needed. If not required by this implementation guide, do not send.
Required
11-1
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Health Care Claim Status Category Code
See STC01-1 for valid values.
Required
11-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Status Code
  1. The Status Code is either a Health Care Claim Status Code (Code Source 508) or a National Council for Prescription Drug Programs Reject/Payment Code (Code Source 530).
  2. The National Council for Prescription Drug Programs Reject/Payment Codes may be used for status related to pharmacy claims. When these codes are used, STC11-4 must have the value `RX'.
Situational
11-3
98
Entity Identifier Code
O 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
SITUATIONAL RULE: Required when an entity must be identified to further clarify the code message in STC11-2. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
See STC01-3 for valid values.
CODE
DEFINITION
03
Dependent
13
Contracted Service Provider
17
Consultant's Office
1E
Health Maintenance Organization (HMO)
1G
Oncology Center
1H
Kidney Dialysis Unit
1I
Preferred Provider Organization (PPO)
1O
Acute Care Hospital
1P
Provider
1Q
Military Facility
1R
University, College or School
1S
Outpatient Surgicenter
1T
Physician, Clinic or Group Practice
1U
Long Term Care Facility
1V
Extended Care Facility
1W
Psychiatric Health Facility
1X
Laboratory
1Y
Retail Pharmacy
1Z
Home Health Care
28
Subcontractor
2A
Federal, State, County or City Facility
2B
Third-Party Administrator
2D
Miscellaneous Health Care Facility
2E
Non-Health Care Miscellaneous Facility
2I
Church Operated Facility
2K
Partnership
2P
Public Health Service Facility
2Q
Veterans Administration Facility
2S
Public Health Service Indian Service Facility
2Z
Hospital Unit of an Institution (prison hospital, college infirmary, etc.)
30
Service Supplier
36
Employer
3A
Hospital Unit Within an Institution for the Mentally Retarded
3C
Tuberculosis and Other Respiratory Diseases Facility
3D
Obstetrics and Gynecology Facility
3E
Eye, Ear, Nose and Throat Facility
3F
Rehabilitation Facility
3G
Orthopedic Facility
3H
Chronic Disease Facility
3I
Other Specialty Facility
3J
Children's General Facility
3K
Children's Hospital Unit of an Institution
3L
Children's Psychiatric Facility
3M
Children's Tuberculosis and Other Respiratory Diseases Facility
3N
Children's Eye, Ear, Nose and Throat Facility
3O
Children's Rehabilitation Facility
3P
Children's Orthopedic Facility
3Q
Children's Chronic Disease Facility
3R
Children's Other Specialty Facility
3S
Institution for Mental Retardation
3T
Alcoholism and Other Chemical Dependency Facility
3U
General Inpatient Care for AIDS/ARC Facility
3V
AIDS/ARC Unit
3W
Specialized Outpatient Program for AIDS/ARC
3X
Alcohol/Drug Abuse or Dependency Inpatient Unit
3Y
Alcohol/Drug Abuse or Dependency Outpatient Services
3Z
Arthritis Treatment Center
40
Receiver
43
Claimant Authorized Representative
44
Data Processing Service Bureau
4A
Birthing Room/LDRP Room
4B
Burn Care Unit
4C
Cardiac Catherization Laboratory
4D
Open-Heart Surgery Facility
4E
Cardiac Intensive Care Unit
4F
Angioplasty Facility
4G
Chronic Obstructive Pulmonary Disease Service Facility
4H
Emergency Department
4I
Trauma Center (Certified)
4J
Extracorporeal Shock-Wave Lithotripter (ESWL) Unit
4L
Genetic Counseling/Screening Services
4M
Adult Day Care Program Facility
4N
Alzheimer's Diagnostic/Assessment Services
4O
Comprehensive Geriatric Assessment Facility
4P
Emergency Response (Geriatric) Unit
4Q
Geriatric Acute Care Unit
4R
Geriatric Clinics
4S
Respite Care Facility
4U
Patient Education Unit
4V
Community Health Promotion Facility
4W
Worksite Health Promotion Facility
4X
Hemodialysis Facility
4Y
Home Health Services
4Z
Hospice
5A
Medical Surgical or Other Intensive Care Unit
5B
Hisopathology Laboratory
5C
Blood Bank
5D
Neonatal Intensive Care Unit
5E
Obstetrics Unit
5F
Occupational Health Services
5G
Organized Outpatient Services
5H
Pediatric Acute Inpatient Unit
5I
Psychiatric Child/Adolescent Services
5J
Psychiatric Consultation-Liaison Services
5K
Psychiatric Education Services
5L
Psychiatric Emergency Services
5M
Psychiatric Geriatric Services
5N
Psychiatric Inpatient Unit
5O
Psychiatric Outpatient Services
5P
Psychiatric Partial Hospitalization Program
5Q
Megavoltage Radiation Therapy Unit
5R
Radioactive Implants Unit
5S
Therapeutic Radioisotope Facility
5T
X-Ray Radiation Therapy Unit
5U
CT Scanner Unit
5V
Diagnostic Radioisotope Facility
5W
Magnetic Resonance Imaging (MRI) Facility
5X
Ultrasound Unit
5Y
Rehabilitation Inpatient Unit
5Z
Rehabilitation Outpatient Services
61
Performed At
6A
Reproductive Health Services
6B
Skilled Nursing or Other Long-Term Care Unit
6C
Single Photon Emission Computerized Tomography (SPECT) Unit
6D
Organized Social Work Service Facility
6E
Outpatient Social Work Services
6F
Emergency Department Social Work Services
6G
Sports Medicine Clinic/Services
6H
Hospital Auxiliary Unit
6I
Patient Representative Services
6J
Volunteer Services Department
6K
Outpatient Surgery Services
6L
Organ/Tissue Transplant Unit
6M
Orthopedic Surgery Facility
6N
Occupational Therapy Services
6O
Physical Therapy Services
6P
Recreational Therapy Services
6Q
Respiratory Therapy Services
6R
Speech Therapy Services
6S
Women's Health Center/Services
6U
Cardiac Rehabilitation Program Facility
6V
Non-Invasive Cardiac Assessment Services
6W
Emergency Medical Technician
6X
Disciplinary Contact
6Y
Case Manager
71
Attending Physician
72
Operating Physician
73
Other Physician
74
Corrected Insured
77
Service Location
7C
Place of Occurrence
80
Hospital
82
Rendering Provider
84
Subscriber's Employer
85
Billing Provider
87
Pay-to Provider
95
Research Institute
CK
Pharmacist
CZ
Admitting Surgeon
D2
Commercial Insurer
DD
Assistant Surgeon
DJ
Consulting Physician
DK
Ordering Physician
DN
Referring Provider
DO
Dependent Name
DQ
Supervising Physician
E1
Person or Other Entity Legally Responsible for a Child
E2
Person or Other Entity With Whom a Child Resides
E7
Previous Employer
E9
Participating Laboratory
FA
Facility
FD
Physical Address
FE
Mail Address
G0
Dependent Insured
G3
Clinic
GB
Other Insured
GD
Guardian
GI
Paramedic
GJ
Paramedical Company
GK
Previous Insured
GM
Spouse Insured
GY
Treatment Facility
HF
Healthcare Professional Shortage Area (HPSA) Facility
HH
Home Health Agency
I3
Independent Physicians Association (IPA)
IJ
Injection Point
IL
Insured or Subscriber
IN
Insurer
LI
Independent Lab
LR
Legal Representative
MR
Medical Insurance Carrier
MSC
Mammography Screening Center
OB
Ordered By
OD
Doctor of Optometry
OX
Oxygen Therapy Facility
P0
Patient Facility
P2
Primary Insured or Subscriber
P3
Primary Care Provider
P4
Prior Insurance Carrier
P6
Third Party Reviewing Preferred Provider Organization (PPO)
P7
Third Party Repricing Preferred Provider Organization (PPO)
PRP
Primary Payer
PT
Party to Receive Test Report
PV
Party performing certification
PW
Pickup Address
QA
Pharmacy
QB
Purchase Service Provider
QC
Patient
QD
Responsible Party
QE
Policyholder
QH
Physician
QK
Managed Care
QL
Chiropractor
QN
Dentist
QO
Doctor of Osteopathy
QS
Podiatrist
QV
Group Practice
QY
Medical Doctor
RC
Receiving Location
RW
Rural Health Clinic
S4
Skilled Nursing Facility
SEP
Secondary Payer
SJ
Service Provider
SU
Supplier/Manufacturer
T4
Transfer Point
Used to identify the geographic location where a patient is transferred or diverted.
TL
Testing Laboratory
TQ
Third Party Reviewing Organization (TPO)
TT
Transfer To
TTP
Tertiary Payer
TU
Third Party Repricing Organization (TPO)
UH
Nursing Home
X3
Utilization Management Organization
X4
Spouse
X5
Durable Medical Equipment Supplier
ZZ
Mutually Defined
Situational
11-4
1270
Code List Qualifier Code
O 1
ID
1/3
Code identifying a specific industry code list
SITUATIONAL RULE: Required when using a National Council for Prescription Drug Programs Reject/Payment Code in STC11-2 for status related to a pharmacy claim. If not required by this implementation guide, do not send.
CODE
DEFINITION
RX
National Council for Prescription Drug Programs Reject/Payment Codes
CODE SOURCE 530: National Council for Prescription Drug Programs Reject/Payment Codes
Not Used
12
933
Free-form Message Text
O 1
AN
1/264

REF*FJ - SERVICE LINE ITEM 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 the Service Line Item Identification was submitted on the 276 request and service level status is reported. If not required by this implementation guide, do not send.
TR3 Example:
REF✱FJ✱6042201~
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
FJ
Line Item 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
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

DTP*472 - SERVICE LINE 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✱472✱RD8✱20050401-20050402~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
472
Service
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
RD8
Range of Dates Expressed in Format CCYYMMDD-CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Service Line Date

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✱34✱0001~
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
Data value in SE02 must be identical to ST02.

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

276/277 Health Care Claim Status Request and Response
(005010X212, 005010X212E1, 005010X212E2, 005010X212E3)

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.

The purpose of this implementation guide is to provide standardized data requirements and content for all users of the ASC X12 Health Care Claim Status Request (276) and the ASC X12 Health Care Information Status Notification (277). This implementation guide focuses on the use of the 276 to request the status of a health care claim(s) and the 277 to respond with the information regarding the specified claim(s). This implementation guide provides detailed explanations of the transaction sets by defining uniform data content, identifying valid code tables, and specifying values applicable for the business focus of the 276 Health Care Claim Status Request and the 277 Health Care Claim Status Response. The intention of the developers of the 276 and 277 is represented in the guide.

Entities using the 276 to request health care claim status include, but are not limited to, hospitals, nursing homes, laboratories, physicians, dentists, allied professional groups, employers, and supplemental (i.e., other than primary payer) health care claims adjudication processors.

Organizations sending the 277 response include payers, who may be insurance companies; third party administrators; service corporations; state and federal agencies and their contractors; and any other entity that processes health care claims.

Other business partners affiliated with the 276 and/or the 277 include billing services; consulting services; vendors of systems; software and EDI translators; and EDI network intermediaries such as Automated Clearing Houses (ACHs), Value-Added Networks (VANs), and telecommunications services.

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

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

  • HR Health Care Claim Status Request (276)

  • HN Health Care Information Status Notification (277)

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

There are other usage limitations.

1.3.2.1 Real Time and Batch Transmissions

The Claim Status Request and Response transaction may be sent in batch or real time. If trading partners are going to engage in both transmission options, it is recommended they establish a method for identifying the difference.

Real Time Limitations

  • The 276 must only contain one status request. The 277 may return multiple responses depending on the specificity of the request criteria and the payer's system capabilities.

  • Date search criteria may vary by payer. This includes date ranges or available history.

Batch Limitations

  • This implementation supports the sending and receiving of multiple claim status requests and responses within the Transaction.

  • When requesting and responding to claim status for both a subscriber and a dependent of that subscriber, the Subscriber HL Loop 2000D must be followed by the subscriber's claim status data, Loop 2200D. Then the Subscriber HL Loop 2000D must be repeated prior to the dependent HL Loop 2000E and their corresponding claim status data, Loop 2200E. See Section 1.4.2.3 - Claim and Service loop placement for an example of this structure.

  • Date search criteria may vary by payer. This includes date ranges or available history.

1.3.2.2 Claim Status Category Codes

  • The 'Request for Additional Information' Claims Status Category Codes (R codes) are excluded from use in this implementation.

  • The usage of the other allowable Category Codes vary by Hierarchical levels. See Section 1.4.3.2 - Status Response Levels for those variations.

1.3.2.3 277 Business Functions

Additional 277 business functions that are not in direct response to a Claim Status Request (276) are not supported in this implementation. See Section 1.4.5 - 277 Transaction Uses, for additional information on the varied 277 business functions.

1.4 Business Usage

The ASC X12 Health Care Claim Status Request and Response (276/277) implementation guide addresses the paired usage of the 276 as a request for claim status and the 277 as a response to that request. The 276 is used to transmit request(s) to obtain the status of specific health care claim(s) within a payer's adjudication process. The payer uses the 277 to transmit the current system status of those requested claims. Claim history parameters may vary by payers and systems.

Status information can be requested and responded to at the claim and/or service level. The 276 provides information that is necessary for the payer to identify the specific claim(s) in question. Some primary or unique identifying element(s) may be supplied to obtain an exact match for that request. However, when the 276 does not uniquely identify the claim within the payer's system, the response may include multiple claims that meet the parameters supplied by the requester.

Figure 1.1 - Information Flow for Claim Status Request/Response, illustrates the flow of information for the 276 Health Care Claim Status Request and the 277 Health Care Claim Status Response.

Figure 1.1 - Information Flow for Claim Status Request/Response

Information Flow for Claim Status Request/Response

1.4.1 Transaction Participants

The hierarchical level structure is used to identify and relate the participants involved in the transaction. The relationships between the hierarchical levels are described by the hierarchical level code data elements, also known as HL01 and HL02. The data element, HL03, identifies the participants within the transaction. The hierarchical structure and participants are the same for both the 276 and 277. The participants described are as follows:

When HL03 = 20, the hierarchical level contains the Information Source. This entity is the decision maker in the business transaction. For this business use, this entity is the payer who has the current status information for the specified claims.

When HL03 = 21, the hierarchical level contains the Information Receiver. This entity expects the response from the Information Source. For this business use, this entity can be a provider, a provider group, a claims clearinghouse, a service bureau, an agency, an employer, etc. This entity will be identified via their electronic ID as the sender of the 276 Request and receiver of the 277 Response.

When HL03 = 19, the hierarchical level contains the Provider of Service. This entity delivered the health care service. Provider of Service is generic in that this could be the entity that originally submitted the claim (Billing Provider) or may be the entity that provided or participated in some aspect of the health care (Rendering Provider).

When HL03 = 22, the hierarchical level contains the Insured or Subscriber information. This entity is the contract holder of the health care benefits. This entity may or may not be the recipient of the health care service rendered. See Section 1.4.1.1 - Defining the "Patient" Participant, for more information on this entity.

When HL03 = 23, the hierarchical level contains the Dependent information. This entity is eligible for health care benefits due to their relationship to the subscriber. When this HL is reported, this entity is the recipient of the health care service rendered. See Section 1.4.1.1 - Defining the "Patient" Participant, for more information on this entity.

The Information Receiver and the Service Provider hierarchical levels have a unique relationship. Information Receiver refers to the entity that processes the detailed information contained within the transaction set. In some cases, the Information Receiver is an entity acting on behalf of the Service Provider. When this occurs, the entity is described when HL03 = 21, and the Provider of Service is described when HL03 = 19. In other instances, the Information Receiver is also the Service Provider. When this occurs, the same entity is described at two hierarchical levels - when HL03 = 21 and when HL03 = 19.

The coding examples are presented sequentially as found within an actual transaction set. However, for reading ease each segment begins on a new line.

The following example demonstrates the coding of the segments and data elements within the Information Source hierarchical level:

HL*1**20*1~
NM1*PR*2*ABC INSURANCE*****PI*12345~

The following is a coding example of the Information Receiver hierarchical level:

HL*2*1*21*1~
NM1*41*2*XYZ SERVICE*****46*X67E~

The following is a coding example of the Service Provider hierarchical level:

HL*3*2*19*1~
NM1*1P*2*HOME MEDICAL*****SV*987666666~

The following is a coding example of the Subscriber Hierarchical level:

HL*4*3*22*1~
NM1*IL*1*MANN*JOHN****MI*345678901~

The following is a coding example of the Dependent Hierarchical level:

HL*5*4*23~
NM1*QC*1*MANN*JOSEPH~

1.4.1.1 Defining the "Patient" Participant

Subscriber Loop 2000D and Dependent Loop 2000E identify the patient for whom a claim status inquiry is being generated. When reporting status at the patient level (see Section 1.4.3.2 - Status Response Levels), Loop 2000D is always used. Loop 2000E is used only when necessary to identify a patient who is a dependent that does not have a unique identification number.

  • When the patient is the subscriber, only Loop 2000D is used. Loop 2000E is not used.

  • When the patient is a dependent and their identification number is the same as the subscriber's, Loop 2000D is used to identify the subscriber and Loop 2000E is used to identify the subscriber's dependent. This structure is more common in traditional group insurance where a patient is identified within the primary subscriber identifier.

  • When the patient is a dependent and they have a unique identification number (different from the subscriber), the patient is considered to be the subscriber and must be reported in Loop 2000D. Loop 2000E is not used. This situation is common when an insurance company issues a unique insurance identification number to each individual insured.

1.4.2 Claim and Service Information

Unlike the Transaction Participants, specific claim and service details are not given a hierarchical level. Claim and Service details are positioned in the same hierarchical level that describes its owner-participant, either the Subscriber or the Dependent. The claim(s) details are said to "float". That means the claim(s) details are placed at the Subscriber hierarchical level (2200D) when the patient is the subscriber or a uniquely identified dependent. The claim(s) details are placed at the Dependent hierarchical level (2200E) when the patient is the dependent of the subscriber and not uniquely identified. The specific claim(s) in question are described in Loop 2200 in both the 276 and 277 transactions, while the service information follows the claim data in Loop 2210 of the 276 and Loop 2220 of the 277.

1.4.2.1 The Claim

The 276 and 277 Loop 2200 may contain different segments, with the exception of the TRN Segment. However, the intent of the loop is similar in both transactions. The provider and payer may identify the claim within their respective system using different data. As a result, the segments used for the request (276) may differ from the segments returned in the response (277).

When claim status is requested, the provider supplies data that helps the payer locate the claim(s). This data may include the payer's claim number, dates of service, claim amount, type of bill, patient control number, etc. Similarly, when the claim status is returned, the payer supplies data that helps the provider locate the claim within their system. This data may include patient control number, type of bill, dates and amounts of the service, etc.

Reassociation of the response to the original request is a necessity of the 276/277 paired transaction. The reassociation is accomplished with a unique trace or reference number identified in the TRN Segment (TRN02). This number is determined by the originator (Information Receiver) of the 276 and must be returned in the 277 by the sender (Information Source). The 277 response TRN02 must contain the same value that was submitted in the 276 request. The only exceptions for not returning the 2200D or 2200E TRN segment in the 277 are when rejection statuses are reported at either the Information Receiver or Provider of Service levels. In both of those instances, lower level (child) HL's are not used. With respect to the Provider of Service Level status, only those lower HL's directly tied to the rejected Provider would be impacted. See Section 1.4.3.2 - Status Response Levels, for details on Information Receiver and Provider of Service level rejections.

1.4.2.2 The Service

The service information follows the claim data in Loop 2210 of the 276 and Loop 2220 of the 277. Some payers' adjudication systems support service line information. When the requester is inquiring on the status of a specific service, Loop 2210 must be populated in the 276. When the payer is reporting the status of a specific service, Loop 2220 must be populated in the 277.

For Service line status requests and responses, the SVC segment is used to report the actual service (procedure) data. When capable of providing this level of detail, the SVC Segment is returned by the payer indicating the adjudicated procedure code. Due to the payer's adjudication processes and policies, service line data may be changed as a result of bundling or unbundling. In this case, the service line(s) returned in the 277 may be different than those submitted in the 276. Procedure code bundling or unbundling occurs when a payer believes the actual services performed and reported for claim payment can be represented by a different group of procedure codes. Bundling occurs when two or more submitted procedures are processed using one procedure code. Unbundling occurs when one submitted procedure code is processed and reported back as two or more procedure codes.

1.4.2.3 Claim and Service loop placement

The following reflects the transaction participant structure, along with the claim and service loops placement for the identified patient. See Section 1.4.1.1 - Defining the "Patient" Participant, for the definition of the patient.

Claim and Service loop placement when the patient is the subscriber or a dependent with a unique identification number.

276 Request

Information Source (2000A)

Information Receiver (2000B)

Service Provider (2000C)

Subscriber (2000D)

Claim Status Request (2200D)

Service Status Request (2210D)

277 Response (multiple claim response)

Information Source (2000A)

Information Receiver (2000B)

Service Provider (2000C)

Subscriber (2000D)

Claim Status Response (2200D)

Service Status Response (2220D)

Claim Status Response (2200D)

Service Status Response (2220D)

Claim and Service loop placement when the patient is a dependent of the subscriber. The dependent has the same identification number as the subscriber.

276 Request (multiple service requests)

Information Source (2000A)

Information Receiver (2000B)

Service Provider (2000C)

Subscriber (2000D)

Dependent (2000E)

Claim Status Request (2200E)

Service Status Request (2210E)

Service Status Request (2210E)

277 Response (multiple service responses)

Information Source (2000A)

Information Receiver (2000B)

Service Provider (2000C)

Subscriber (2000D)

Dependent (2000E)

Claim Status Response (2200E)

Service Status Response (2220E)

Service Status Response (2220E)

Claim and Service loop placement for multiple patient requests (batch mode) where one patient is the subscriber (A) and one or more other patients (A.1, A.2) are dependents of that subscriber (A). The dependent(s) has the same identification number as the subscriber.

276 Request

Information Source (2000A)

Information Receiver (2000B)

Service Provider (2000C)

Subscriber (2000D) - A

Requested Claim(s) Identification (2200D)

Subscriber (2000D) - A

Dependent (2000E) – A.1

Claim Status Request (2200E)

Service Status Request (2210E)

Dependent (2000E) – A.2

Claim Status Request (2200E)

Service Status Request (2210E)

277 Response

Information Source (2000A)

Information Receiver (2000B)

Service Provider (2000C)

Subscriber (2000D) - A

Claim Status Response (2200D)

Subscriber (2000D) - A

Dependent (2000E) – A.1

Claim Status Response (2200E)

Service Status Response (2220E)

Dependent (2000E) – A.2

Claim Status Response (2200E)

Service Status Response (2220E)

1.4.3 277 Status Information (STC) Segment Usage

The primary vehicle for the claim status information in the 277 Transaction is the Status Information (STC) Segment. The level of information returned in the STC Segment may vary from payer to payer. Payers are urged to provide the greatest level of response detail to the Information Receiver so that the data exchange is beneficial to both entities. Payers who meet the minimum required basics, defined in Section 1.4.3.1 - STC Composite and Code Use Rules, may not satisfy the receiver's need for complete and detailed status which could result in the generation of subsequent inquiries to the payer.

The STC segment contains three iterations of the C043 (Health Care Claim Status) composite within STC01, STC10 and STC11.

The Health Care Claim Status composite (C043) consists of four elements:

The first element in the C043 composite (C043-01) is the Health Care Claim Status Category Code (Code Source 507). The Category Code indicates the payer's current system status of the claim. This implementation guide allows the use of all Category Codes in the list, except the 'Request for Additional Information Codes' (R). The 'Request' codes apply only to the 277 Request for Additional Information Implementation Guide (see Section 1.4.5 - 277 Transaction Uses).

The second element in the C043 composite (C043-02) is either the Health Care Claim Status Code (Code Source 508) or the National Council for Prescription Drug Programs Reject/Payment Codes (Code Source 530). These codes provide more specific information about the claim or line item.

The third element in the C043 composite (C043-03) is the Entity Identifier Code (ASC X12 data element 98). The Entity Identifier code is used to clarify the entity when referred to in the status message (C043-02). The code list identifies an organizational entity, a physical location, property, or an individual. A list of appropriate code values for data element 98 appears within the STC segments in Section 2.6.

The fourth element in the C043 composite (C043-04) is the Code List Qualifier Code (ASC X12 data element 1270). This element is Situational and only used when identifying the second element of the composite (C043-02) as a National Council for Prescription Drug Programs Reject/Payment Code. When this element is used, it will contain code value 'RX' - National Council for Prescription Drug Programs Reject/Payment Codes.

A committee of healthcare industry representatives from payer, provider and vendor organizations maintain the Health Care Claim Status Category Codes and Health Care Claim Status Codes (Code Sources 507 and 508). They are updated after each ASC X12 trimester meeting. Version specific code additions or deactivations are noted on the code lists.

The Blue Cross Blue Shield Association (BCBSA) is the owner of these code lists. The primary distribution source is the Washington Publishing Company web site (www.wpc-edi.com). This web site offers an online conferencing facility that allows interested parties to submit requests for new codes, changes to existing codes, or simply view comments on pending requests. Individuals who are unable to access the Internet may contact BCBSA directly.

The National Council for Prescription Drug Programs (NCPDP) Reject/Payment Codes are maintained by the National Council for Prescription Drug Programs. For information on the NCPDP Reject/Payment Codes (Code Source 530) refer to Appendix A, External Code Sources.

1.4.3.1 STC Composite and Code Use Rules

The following rules apply to use of the composites and codes within the STC segment:

  • STC01 is required.

  • STC10 and STC11 are situational and provide additional status information (second and third, respectively) when needed.

  • The Status Category Code for STC10 and STC11 must be within the same Status Category Code (i.e., Acknowledgments, Pending, Finalized) as that used in STC01, but not necessarily the same Status Category Code. (For example, if STC01 uses the Category Code 'P0 - Pending: Adjudication/Details', STC10 and STC11 must use Category Codes from the 'Pending' Category Code List but not necessarily the 'P0' value.)

  • An Entity Code must be identified when the Health Care Claim Status Code or the National Council for Prescription Drug Programs Reject/Payment Code message refers to an Entity. For example the Entity Code '85 - Billing Provider' could be used when Status Code '24 - Entity not approved as an electronic submitter' is used.

  • When reporting multiple statuses, payers must use discretion in choosing the appropriate Category and Status Codes to ensure business compatibility between the status messages reflected.

  • Allowable Category Codes vary per Hierarchical Levels. See Section 1.4.3.2 - Status Response Levels, for those variations.

  • The Information Source must discriminate between all of the Status Category Codes applicable to their business process. (Example - Code 'P0 - Pending: Adjudication/Details' should not be used when a claim is really in a category of 'P3 - Pending/Requested Information'.)

  • The Information Source must strive to provide full status information by making use of the entire Claim Status Code list. However, the minimum requirement is to support the following basic codes:

    Code Description
    0 Cannot provide further status electronically.
    1 For more detailed information, see remittance advice.
    2 More detailed information in letter.

    Minimum Reporting Requirement Example - Claim is pended awaiting additional information to identify the medical necessity for the service. At a bare minimum, the Information Source must report a Category code of P3 and a Status code of 0. However, the Information Source is encouraged to support more detail by identifying a Status code of 287 (Medical necessity for service).

1.4.3.2 Status Response Levels

The STC segment is used in the 277 at various participant levels and within the claim and service loops for the patient level (subscriber or dependent). When the 277 transaction is sent, a status response is not required at all levels within the transaction.

In most instances, the Information Source must respond with status at the appropriate patient level (Subscriber or Dependent loop) of the claim, and when applicable the service level. Responses at these patient levels meet the intended business purpose of this paired transaction.

The Information Receiver and Provider of Service status response levels are Situational and provide the flexibility for an Information Source to reject an entire 276 transaction or a specific provider's portion of the 276 transaction without having to repeat the status error at each patient level. The Information Receiver and Provider of Service status response levels have limited defined functionality and are not to be used in place of providing valid claim status at a patient level. The patient (Subscriber or Dependent loop) claim level status can also accommodate the error statuses allowable at the Information Receiver and Provider of Service level, if an Information Source chooses to respond by repeating those types of error statuses for each patient claim status request received in the 276 transaction.

The following describes use of the various status levels.

Loop 2200B - Information Receiver

The Loop 2200B STC segment allows the capability to report a rejected status for the entire 276 Transaction for errors at the Information Source or Information Receiver levels. Status at this level is the result of system or application availability, transaction size limitations for real time capability or Trading Partner authorization/verification issues. When status is reported at this level, the 2000C, 2000D and 2000E hierarchical levels (children) are not used.

Only the 'D0' Category Code and 'E' Category Code types are allowed at the Information Receiver status level.

Loop 2200C - Provider of Service

The Loop 2200C STC segment allows the capability to report rejected claim status requests for errors at the provider level. Typically a rejection at this level is the result of provider authorization/verification issues. When status is reported at this level, the 2000D and 2000E hierarchical levels (children) associated to that specific provider are not used.

Only the 'D0' Category Code and 'E' Category Code types are allowed at the Provider of Service status level.

Loop 2200D or 2200E - The Claim Level

The Loop 2200D (Subscriber) or 2200E (Dependent) STC segments are used to report the payer's adjudication status that applies to the entire claim.

This implementation guide allows the use of all Category Codes in the list, except the 'Request for Additional Information Codes' (R Category Codes) at the claim level.

Loop 2220D or 2220E - The Service Level

The Loop 2220D (Subscriber) or 2220E (Dependent) STC segments are used to report the payer's adjudication status that applies to the service line.

This implementation guide allows the use of all Category Codes in the list, except the 'Request for Additional Information Codes' (R Category Codes) at the service level.

When service lines within a claim have various statuses (example both pending and finalized), a single status must be reflected at the claim level and the service specific statuses must be reported at the service level (2220D or 2220E).

1.4.4 Payer's System Status Locations

In response to a 276 request, the 277 can support responding with status for claims in the payer system locations identified in sections 1.4.4.1 through 1.4.4.3 (Pre-Adjudication, Pended and Finalized). However, a payer's response capability for claim status in those locations will vary from payer to payer, as well as their determination of when a claim is in a pended versus finalized status.

1.4.4.1 Pre-Adjudication

Payers may pre-process claims to determine whether or not to introduce them to their adjudication system. This process is performed so that incorrectly formatted claims or those that are missing information can be returned to the provider for correction. Returned claims may not have a claim number assigned by the payer.

Status for claims in this location generally use the 'Acknowledgments' (A) Category Codes.

1.4.4.2 Pended

Payers may perform various functions, such as validation editing, medical reviews, contractual requirements, request additional information, etc. within their adjudication system that may cause claims to be placed in a 'pended' or 'suspended' status. Payers usually assign a claim number to a pended claim. Claims generally remain in a 'pending' state until the payer resolves or completes validation editing, medical reviews, etc. and the claims are finalized.

Status for claims in this location generally use the 'Pending' (P) Category Codes.

1.4.4.3 Finalized

Claims that complete the adjudication process and/or remittance cycle are referred to as 'finalized' claims. The adjudication determination on finalized claims has concluded. Claims in a finalized status may include rejected, denied, approved for payment and paid.

Status for claims in this location generally use the 'Finalized' (F) Category Codes.

1.4.5 277 Transaction Uses

The Health Care Information Status Notification (277) transaction set has multiple implementation conventions to meet various business needs of the health care industry. The transaction set can be used to provide healthcare claim information in the following business scenarios:

  • ASC X12 Health Care Claim Status Request and Response (276/277), where the 277 is a response to a request for claim status information. This function is supported in this implementation guide.

  • ASC X12 Health Care Claim Acknowledgment (277), which is a business application response to the ASC X12 837 claim/encounter transactions. This function is not supported in this implementation guide.

  • ASC X12 Health Care Claim Request for Additional information (277), which is a payer's request for additional information to support a health care claim. This function is not supported in this implementation guide.

  • ASC X12 Health Care Claim Pending Status Information (277), which is used as a listing of pended claims in a payer's system. This function is not supported in this implementation guide.

Figure 1.2 - General ASC X12 Health Care Claim Information Flow illustrates the flow of information related to several usages of the 277. The multiple uses of the 277 claim status are differentiated by values in the ST and BHT Segments of Table 1 data. Element BHT06, in addition to the ST03 and GS08 values, is used to distinguish between these varied business functions. The various 277 - BHT06 code values are:

  • DG - Response (Health Care Claim Status Request and Response)

  • NO - Notice (Health Care Claim Pending Status Information)

  • RQ - Request (Health Care Claim Request for Additional Information)

  • TH - Receipt Acknowledgment Advice (Health Care Claim Acknowledgment)

Figure 1.2 - General ASC X12 Health Care Claim Information Flow

General ASC X12 Health Care Claim Information Flow

1.5 Business Terminology

Remittance cycle

The point in a payer's claim adjudication process where a remittance advice notice (835, paper remittance or Explanation of Benefits) has been issued providing the final claim payment or denial details.

Claim

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

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.7 Related Transactions

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

1.7.1 The Claim (837)

Submitting a claim, whether by using the 837 or another format, is the first step in the claim status request/response process. Certain data elements (e.g., the patient control number, type of bill, dates of service, insured identifier, service provider identifier, and payer's claim number when available) found on the claim help locate a claim within a payer's adjudication system. When the provider initiates a claim status request, as many of these data elements as possible should be forwarded to the payer. With the exception of the payer's claim number, the source of this information is the provider's billing system.

1.7.2 The Remittance Advice

The Remittance Advice, whether using an electronic transaction (835) or paper, provides the final adjudication details related to the payment or denial of a claim. The 277 Claim Status Response is not intended to provide the final claim adjudication details. Some remittance advice data is reflected in the 2200 STC to provide the link between the finalized claim and the remittance advice on which it was reported.

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 Data Overview

This section introduces the structures of the 276 and 277. Familiarity with ASC X12 nomenclature, segments, data elements, hierarchical levels, and looping structure is recommended. For a review, see Appendix B, Nomenclature and Appendix C, EDI Control Directory.

1.10.1 Overall Data Architecture

Two formats, or views, are used to present the transaction set: the implementation view and the standard view. The intent of the implementation view is to clarify the purpose and use of the segments by restricting the view to display only those segments used with their assigned health care names. The implementation views for both the 276 and 277 are presented in the Implementation Sections 2.3.1 and 2.5.1, respectively. The standard views for both the 276 and 277 display all segments available within the transaction sets with their assigned ASC X12 names. These views are presented in the X12 Standard Sections 2.3.2 and 2.5.2, respectively.

The 276 and 277 transaction sets are similar in structure but are not duplicates. Both transaction sets are divided into two levels, or tables, Table 1 and Table 2.

Table 1

Table 1 is named the Header Level and contains the transaction control information. This table contains the same segments, ST and BHT for both of the 276 and 277 transaction sets. The ST segment identifies the start of a transaction and the specific transaction set. The BHT identifies the transactions business purpose and the hierarchical structure used in Table 2.

Table 2

Table 2 is named the Detail Level because it contains the detail information for the business function of the transactions. This table uses the hierarchical level structure. Each hierarchical level (HL) is a series of loops, which are identified by numbers. The hierarchical level that identifies the participant and the relationship to other participants is Loop ID- 2000. The individual or entity name is contained in Loop ID-2100. Specific claim details begin with Loop ID-2200. It is at this point that the 276 and 277 transactions begin to differ in segment usage.

The following are HL segment coding examples and the data element significance within the HL segments:

HL*1**20*1~
Information Source level
HL*2*1*21*1~
Information Receiver level
HL*3*2*19*1~
Service Provider level
HL*4*3*22*1~
Subscriber level
HL*5*4*23~
Dependent level
  • HLs are sequentially numbered. The sequential number is found in HL01, which is the first data element in the HL segment.

  • The second element, HL02, indicates the sequential number of the parent hierarchical level to which this hierarchical level is subordinate. The absence of a data value in HL02, indicates it is the highest hierarchical level. In this example, the Information Source is the highest parent. The Information Receiver level is subordinate to the Information Source hierarchical level numbered 1 (HL01 =1). The provider of service level is subordinate to the Information Receiver hierarchical level numbered 2 (HL01=2), etc.

  • The data value in data element HL03 describes the hierarchical level entity. For example, when HL03 = 20, the hierarchical level is the Information Source. When HL03 = 23, the hierarchical level is the Dependent.

  • Data element HL04 indicates whether or not child (subordinate) hierarchical levels exist. A value of "1" indicates subordinate hierarchical levels exist. A value of "0" or the absence of a data value indicates that no subordinate hierarchical levels exist.

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.

2.3 Transaction Set Listing

2.3.1 Implementation

This section lists the levels, loops, and segments contained in this implementation. It also serves as an index to the segment detail. Refer to Section 2.1 - Presentation Examples for detailed information on the components of the Implementation section.

Table 1 - Header

POSIDNAMEUSGRPTLOOP RPT
0100 ST Transaction Set HeaderR1
0200 BHT Beginning of Hierarchical TransactionR1
Table 2 - Information Source Detail
POSIDNAMEUSGRPTLOOP RPT
--
LOOP ID - 2000A INFORMATION SOURCE LEVEL>1
0100 HL Information Source LevelR1 -
---
LOOP ID - 2100A PAYER NAME1-
0500 NM1 Payer NameR1 --
---
Table 2 - Information Receiver Detail
POSIDNAMEUSGRPTLOOP RPT
--
LOOP ID - 2000B INFORMATION RECEIVER LEVEL>1
0100 HL Information Receiver LevelR1 -
---
LOOP ID - 2100B INFORMATION RECEIVER NAME1-
0500 NM1 Information Receiver NameR1 --
---
Table 2 - Service Provider Detail
POSIDNAMEUSGRPTLOOP RPT
--
LOOP ID - 2000C SERVICE PROVIDER LEVEL>1
0100 HL Service Provider LevelR1 -
---
LOOP ID - 2100C PROVIDER NAME2-
0500 NM1 Provider NameR1 --
---
Table 2 - Subscriber Detail
POSIDNAMEUSGRPTLOOP RPT
--
LOOP ID - 2000D SUBSCRIBER LEVEL>1
0100 HL Subscriber LevelR1 -
0400 DMG Subscriber Demographic InformationS1 -
---
LOOP ID - 2100D SUBSCRIBER NAME1-
0500 NM1 Subscriber NameR1 --
---
---
LOOP ID - 2200D CLAIM STATUS TRACKING NUMBER>1-
0900 TRN Claim Status Tracking NumberS1 --
1000 REF Payer Claim Control NumberS1 --
1000 REF Institutional Bill Type IdentificationS1 --
1000 REF Application or Location System IdentifierS1 --
1000 REF Group NumberS1 --
1000 REF Patient Control NumberS1 --
1000 REF Pharmacy Prescription NumberS1 --
1000 REF Claim Identification Number For Clearinghouses and Other Transmission IntermediariesS1 --
1100 AMT Claim Submitted ChargesS1 --
1200 DTP Claim Service DateS1 --
----
LOOP ID - 2210D SERVICE LINE INFORMATION>1--
1300 SVC Service Line InformationS1 ---
1400 REF Service Line Item IdentificationS1 ---
1500 DTP Service Line DateR1 ---
----
Table 2 - Dependent Detail
POSIDNAMEUSGRPTLOOP RPT
--
LOOP ID - 2000E DEPENDENT LEVEL>1
0100 HL Dependent LevelS1 -
0400 DMG Dependent Demographic InformationR1 -
---
LOOP ID - 2100E DEPENDENT NAME1-
0500 NM1 Dependent NameR1 --
---
---
LOOP ID - 2200E CLAIM STATUS TRACKING NUMBER>1-
0900 TRN Claim Status Tracking NumberR1 --
1000 REF Payer Claim Control NumberS1 --
1000 REF Institutional Bill Type IdentificationS1 --
1000 REF Application or Location System IdentifierS1 --
1000 REF Group NumberS1 --
1000 REF Patient Control NumberS1 --
1000 REF Pharmacy Prescription NumberS1 --
1000 REF Claim Identification Number For Clearinghouses and Other Transmission IntermediariesS1 --
1100 AMT Claim Submitted ChargesS1 --
1200 DTP Claim Service DateS1 --
----
LOOP ID - 2210E SERVICE LINE INFORMATION>1--
1300 SVC Service Line InformationS1 ---
1400 REF Service Line Item IdentificationS1 ---
1500 DTP Service Line DateR1 ---
----
1600 SE Transaction Set TrailerR1

2.5 Transaction Set Listing

2.5.1 Implementation

This section lists the levels, loops, and segments contained in this implementation. It also serves as an index to the segment detail. Refer to Section 2.1 - Presentation Examples for detailed information on the components of the Implementation section.

Table 1 - Header

POSIDNAMEUSGRPTLOOP RPT
0100 ST Transaction Set HeaderR1
0200 BHT Beginning of Hierarchical TransactionR1
Table 2 - Information Source Detail
POSIDNAMEUSGRPTLOOP RPT
--
LOOP ID - 2000A INFORMATION SOURCE LEVEL>1
0100 HL Information Source LevelR1 -
---
LOOP ID - 2100A PAYER NAME1-
0500 NM1 Payer NameR1 --
0800 PER Payer Contact InformationS1 --
---
Table 2 - Information Receiver Detail
POSIDNAMEUSGRPTLOOP RPT
--
LOOP ID - 2000B INFORMATION RECEIVER LEVEL>1
0100 HL Information Receiver LevelR1 -
---
LOOP ID - 2100B INFORMATION RECEIVER NAME1-
0500 NM1 Information Receiver NameR1 --
---
---
LOOP ID - 2200B INFORMATION RECEIVER TRACE IDENTIFIER1-
0900 TRN Information Receiver Trace IdentifierS1 --
1000 STC Information Receiver Status InformationR>1 --
---
Table 2 - Service Provider Detail
POSIDNAMEUSGRPTLOOP RPT
--
LOOP ID - 2000C SERVICE PROVIDER LEVEL>1
0100 HL Service Provider LevelS1 -
---
LOOP ID - 2100C PROVIDER NAME2-
0500 NM1 Provider NameR1 --
---
---
LOOP ID - 2200C PROVIDER OF SERVICE TRACE IDENTIFIER1-
0900 TRN Provider of Service Trace IdentifierS1 --
1000 STC Provider Status InformationR>1 --
---
Table 2 - Subscriber Detail
POSIDNAMEUSGRPTLOOP RPT
--
LOOP ID - 2000D SUBSCRIBER LEVEL>1
0100 HL Subscriber LevelS1 -
---
LOOP ID - 2100D SUBSCRIBER NAME1-
0500 NM1 Subscriber NameR1 --
---
---
LOOP ID - 2200D CLAIM STATUS TRACKING NUMBER>1-
0900 TRN Claim Status Tracking NumberS1 --
1000 STC Claim Level Status InformationR>1 --
1100 REF Payer Claim Control NumberS1 --
1100 REF Institutional Bill Type IdentificationS1 --
1100 REF Patient Control NumberS1 --
1100 REF Pharmacy Prescription NumberS1 --
1100 REF Voucher IdentifierS1 --
1100 REF Claim Identification Number For Clearinghouses and Other Transmission IntermediariesS1 --
1200 DTP Claim Service DateS1 --
----
LOOP ID - 2220D SERVICE LINE INFORMATION>1--
1800 SVC Service Line InformationS1 ---
1900 STC Service Line Status InformationR>1 ---
2000 REF Service Line Item IdentificationS1 ---
2100 DTP Service Line DateR1 ---
----
Table 2 - Dependent Detail
POSIDNAMEUSGRPTLOOP RPT
--
LOOP ID - 2000E DEPENDENT LEVEL>1
0100 HL Dependent LevelS1 -
---
LOOP ID - 2100E DEPENDENT NAME1-
0500 NM1 Dependent NameR1 --
---
---
LOOP ID - 2200E CLAIM STATUS TRACKING NUMBER>1-
0900 TRN Claim Status Tracking NumberR1 --
1000 STC Claim Level Status InformationR>1 --
1100 REF Payer Claim Control NumberS1 --
1100 REF Institutional Bill Type IdentificationS1 --
1100 REF Patient Control NumberS1 --
1100 REF Pharmacy Prescription NumberS1 --
1100 REF Voucher IdentifierS1 --
1100 REF Claim Identification Number For Clearinghouses and Other Transmission IntermediariesS1 --
1200 DTP Claim Service DateS1 --
----
LOOP ID - 2220E SERVICE LINE INFORMATION>1--
1800 SVC Service Line InformationS1 ---
1900 STC Service Line Status InformationR>1 ---
2000 REF Service Line Item IdentificationS1 ---
2100 DTP Service Line DateR1 ---
----
2700 SE Transaction Set TrailerR1

3. Examples

3.1 Business Scenario 1 - Claim Level Status

ABC Insurance is both the Medicare Part A Fiscal Intermediary and a PPO. ABC insurance has a payer identification of 12345.

XYZ Service, which is a Clearinghouse, has an electronic transmitter identification number of X67E that it uses to conduct electronic business transactions with ABC Insurance.

Home Hospital and Home Hospital Physicians use XYZ Service to submit electronic claims and claim status requests to ABC Insurance. Home Hospital's National Provider Identifier (NPI) is 1666666661. Home Hospital Physicians' National Provider Identifier (NPI) is 1666666666.

The following details are for 3 claims that XYZ Service requested status and ABC Insurance responded:

Claim 1

Request - Fred Smith is a Medicare enrollee with a health insurance claim number of 123456789A. Mr. Smith's birth date is 12/10/1930. A claim status tracking number of ABCXYZ1 was assigned to the status inquiry for Mr. Smith's claim. Home Hospital requested the status of a claim for inpatient services (bill type 111) for services August 31, 2005 through September 6, 2005 in the amount of $8,513.88. Home Hospital provided a patient control number of SM123456.

Response - ABC Insurance assigned a payer claim control number of 05347006051 to Mr. Smith's claim. The claim was pending waiting on additional information that had already been requested.

Claim 2

Request - Mary Jones is a Medicare enrollee with a health insurance claim number of 234567890A. Mrs. Jones' birth date is 11/15/1930. A claim status tracking number of ABCXYZ2 was assigned to the status inquiry for Mrs. Jones' claim. Home Hospital requested the status of a claim for inpatient services (bill type 111) from July 31, 2005 through August 9, 2005 in the amount of $7,599.00. Home Hospital provided a patient control number of JO234567.

Response - ABC Insurance assigned a payer claim control number of 0529675341 to Mrs. Jones' claim. The claim completed adjudication and is awaiting the payment cycle.

Claim 3

Request - Joseph Mann is a dependent under John Mann's PPO plan. John Mann is the insured, or subscriber, and his member identification is 345678901. Joseph Mann's birth date is 11/01/1995. A claim status tracking number of ABCXYZ3 was assigned to the status inquiry for Joseph Mann's claim. Home Hospital Physicians requested the status of a service (99203) on May 1, 2005 in the amount of $150.00. Home Hospital Physicians provided a patient control number of MA345678.

Response - ABC Insurance assigned a payer internal control number of 051681010827 to Joseph Mann's claim. The service was denied because the dependent was not eligible for benefits at the time of service.

3.1.1 276 Request Transmission

The following is the 276 transmission XYZ Services sent to ABC Insurance requesting the status of the claims described in Section 3.1 - Business Scenario 1 - Claim Level Status.

ST*276*0001*005010X212~
BHT*0010*13*ABC276XXX*20050915*1425~
HL*1**20*1~
NM1*PR*2*ABC INSURANCE*****PI*12345~
HL*2*1*21*1~
NM1*41*2*XYZ SERVICE*****46*X67E~
HL*3*2*19*1~
NM1*1P*2*HOME HOSPITAL*****XX*1666666661~
HL*4*3*22*0~
DMG*D8*19301210*M~
NM1*IL*1*SMITH*FRED****MI*123456789A~
TRN*1*ABCXYZ1~
REF*BLT*111~
REF*EJ*SM123456~
AMT*T3*8513.88~
DTP*472*RD8*20050831-20050906~
HL*5*3*22*0~
DMG*D8*19301115*F~
NM1*IL*1*JONES*MARY****MI*234567890A~
TRN*1*ABCXYZ2~
REF*BLT*111~
REF*EJ*JO234567~
AMT*T3*7599~
DTP*472*RD8*20050731-20050809~
HL*6*2*19*1~
NM1*1P*2*HOME HOSPITAL PHYSICIANS*****XX*1666666666~
HL*7*6*22*1~
NM1*IL*1*MANN*JOHN****MI*345678901~
HL*8*7*23~
DMG*D8*19951101*M~
NM1*QC*1*MANN*JOSEPH~
TRN*1*ABCXYZ3~
REF*EJ*MA345678~
SVC*HC:99203*150*****1~
DTP*472*D8*20050501~
SE*36*0001~

3.1.2 277 Response Transmission

The following is the 277 transmission ABC Insurance sent in response to the 276 transmission from XYZ Service regarding the claims described in Section 3.1 - Business Scenario 1 - Claim Level Status.

ST*277*0001*005010X212~
BHT*0010*08*277X212*20050916*0810*DG~
HL*1**20*1~
NM1*PR*2*ABC INSURANCE*****PI*12345~
HL*2*1*21*1~
NM1*41*2*XYZ SERVICE*****46*X67E~
HL*3*2*19*1~
NM1*1P*2*HOME HOSPITAL*****XX*1666666661~
HL*4*3*22*0~
NM1*IL*1*SMITH*FRED****MI*123456789A~
TRN*2*ABCXYZ1~
STC*P3:317*20050913**8513.88~
REF*1K*05347006051~
REF*BLT*111~
REF*EJ*SM123456~
DTP*472*RD8*20050831-20050906~
HL*5*3*22*0~
NM1*IL*1*JONES*MARY****MI*234567890A~
TRN*2*ABCXYZ2~
STC*F0:3*20050915**7599*7599~
REF*1K*0529675341~
REF*BLT*111~
REF*EJ*JO234567~
DTP*472*RD8*20050731-20050809~
HL*6*2*19*1~
NM1*1P*2*HOME HOSPITAL PHYSICIANS*****XX*1666666666~
HL*7*6*22*1~
NM1*IL*1*MANN*JOHN****MI*345678901~
HL*8*7*23~
NM1*QC*1*MANN*JOSEPH~
TRN*2*ABCXYC3~
STC*F2:88:QC*20050612**150*0~
REF*1K*051681010827~
REF*EJ*MA345678~
SVC*HC:99203*150*0****1~
STC*F2:88:QC*20050612~
DTP*472*D8*20050501~
SE*38*0001~

3.2 Business Scenario 2 - Provider Level Status

ABC Insurance is both the Medicare Part A Fiscal Intermediary and a PPO. ABC insurance has a payer identification of 12345.

XYZ Service, which is a Clearinghouse, has an electronic transmitter identification number of X67E that it uses to conduct electronic business transactions with ABC Insurance.

Home Hospital and Home Hospital Physicians use XYZ Service to submit electronic claims and claim status requests to ABC Insurance. Home Hospital's National Provider Identifier (NPI) is 1666666661. Home Hospital Physicians' National Provider Identifier (NPI) is 1666666666.

The following details are for 2 claims that XYZ Service requested status and ABC Insurance responded:

Claim 1

Request - Fred Smith is a Medicare enrollee with a health insurance claim number of 123456789A. Mr. Smith's birth date is 12/10/1930. A claim status tracking number of ABCXYZ1 was assigned to the status inquiry for Mr. Smith's claim. Home Hospital requested the status of a claim for inpatient services (bill type 111) for services August 31, 2005 through September 6, 2005 in the amount of $8,513.88. Home Hospital provided a patient control number of SM123456.

Response - ABC Insurance assigned a payer claim control number of 05347006051 to Mr. Smith's claim. The claim was pending waiting on additional information that had already been requested.

Claim 2

Request - Joseph Mann is a dependent under John Mann's PPO plan. John Mann is the insured, or subscriber, and his member identification is 345678901. Joseph Mann's birth date is 11/01/1995. A claim status tracking number of ABCXYZ3 was assigned to the status inquiry for Joseph Mann's claim. Home Hospital Physicians requested the status of a service (99203) on May 1, 2005 in the amount of $150.00. Home Hospital Physicians provided a patient control number of MA345678.

Response - ABC Insurance did not recognize the electronic business relationship between Home Hospital Physicians and XYZ Service because Home Hospital Physicians' provider number was erroneously transposed in their transmission set-up. Consequently, ABC Insurance responded at this specific Provider Level indicating the provider was not eligible for EDI status.

3.2.1 276 Request Transmission

The following is the 276 transmission XYZ Services sent to ABC Insurance requesting the status of the claims described in Section 3.2 - Business Scenario 2 - Provider Level Status:

ST*276*0001*005010X212~
BHT*0010*13*ABC276XXX*20050915*1425~
HL*1**20*1~
NM1*PR*2*ABC INSURANCE*****PI*12345~
HL*2*1*21*1~
NM1*41*2*XYZ SERVICE*****46*X67E~
HL*3*2*19*1~
NM1*1P*2*HOME HOSPITAL*****XX*1666666661~
HL*4*3*22*0~
DMG*D8*19301210*M~
NM1*IL*1*SMITH*FRED****MI*123456789A~
TRN*1*ABCXYZ1~
REF*BLT*111~
REF*EJ*SM123456~
AMT*T3*8513.88~
DTP*472*RD8*20050831-20050906~
HL*5*2*19*1~
NM1*1P*2*HOME HOSPITAL PHYSICIANS*****XX*6166666666~
HL*6*5*22*1~
NM1*IL*1*MANN*JOHN****MI*345678901~
HL*7*6*23~
DMG*D8*19951101*M~
NM1*QC*1*MANN*JOSEPH~
TRN*1*ABCXYZ3~
REF*EJ*MA345678~
SVC*HC:99203*150*****1~
DTP*472*D8*20050501~
SE*28*0001~

3.2.2 277 Response Transmission

The following is the 277 transmission ABC Insurance sent in response to the 276 transmission from XYZ Service regarding the claims described in Section 3.2 - Business Scenario 2 - Provider Level Status:

ST*277*0001*005010X212~
BHT*0010*08*277X212*20050916*0810*DG~
HL*1**20*1~
NM1*PR*2*ABC INSURANCE*****PI*12345~
HL*2*1*21*1~
NM1*41*2*XYZ SERVICE*****46*X67E~
HL*3*2*19*1~
NM1*1P*2*HOME HOSPITAL*****XX*1666666661~
HL*4*3*22*0~
NM1*IL*1*SMITH*FRED****MI*123456789A~
TRN*2*ABCXYZ1~
STC*P3:317*20050913**8513.88~
REF*1K*05347006051~
REF*BLT*111~
REF*EJ*SM123456~
DTP*472*RD8*20050831-20050906~
HL*5*2*19*0~
NM1*1P*2*HOME HOSPITAL PHYSICIANS*****XX*6166666666~
TRN*1*0~
STC*E0:24:85*20050916~
SE*21*0001~

3.3 Business Scenario 3 - Information Receiver Level Status

ABC Insurance is a Medicare Part A Fiscal Intermediary. ABC insurance has a payer identification of 12345.

XYZ Service, which is a Clearinghouse, has an electronic transmitter identification number of X67E which it uses to conduct electronic business transactions with ABC Insurance.

Home Hospital uses XYZ Service to submit electronic claims and claim status requests to ABC Insurance. Home Hospital's National Provider Identifier (NPI) is 1666666661.

The following details are for 1 claim that XYZ Service requested status and ABC Insurance responded:

Claim 1

Request - Fred Smith is a Medicare enrollee with a health insurance claim number of 123456789A. Mr. Smith's birth date is 12/10/1930. A claim status tracking number of ABCXYZ1 was assigned to the status inquiry for Mr. Smith's claim. Home Hospital requested the status of a claim for inpatient services (bill type 111) for services August 31, 2005 through September 6, 2005 in the amount of $8,513.88. Home Hospital provided a patient control number of SM123456.

Response - ABC Insurance's system was down and they were unable to respond to the claim status request. ABC Insurance responded at the Information Receiver level with a system unavailable status.

3.3.1 276 Request Transmission

The following is the 276 transmission XYZ Services sent to ABC Insurance requesting the status of the claims described in Section 3.3 - Business Scenario 3 - Information Receiver Level Status:

ST*276*0001*005010X212~
BHT*0010*13*ABC276XXX*20050915*1425~
HL*1**20*1~
NM1*PR*2*ABC INSURANCE*****PI*12345~
HL*2*1*21*1~
NM1*41*2*XYZ SERVICE*****46*X67E~
HL*3*2*19*1~
NM1*1P*2*HOME HOSPITAL*****XX*1666666661~
HL*4*3*22*0~
DMG*D8*19301210*M~
NM1*IL*1*SMITH*FRED****MI*123456789A~
TRN*1*ABCXYZ1~
REF*BLT*111~
REF*EJ*SM123456~
AMT*T3*8513.88~
DTP*472*RD8*20050831-20050906~
SE*17*0001~

3.3.2 277 Response Transmission

The following is the 277 transmission ABC Insurance sent in response to the 276 transmission from XYZ Service regarding the claims described in Section 3.3 - Business Scenario 3 - Information Receiver Level Status:

ST*277*0001*005010X212~
BHT*0010*08*277X212*20050916*0810*DG~
HL*1**20*1~
NM1*PR*2*ABC INSURANCE*****PI*12345~
HL*2*1*21*0~
NM1*41*2*XYZ SERVICE*****46*X67E~
TRN*2*ABC276XXX~
STC*E0:0*20050916~
SE*9*0001~

3.4 Business Scenario 4 - Claim Level Status with NCPDP Reject/Payment Code

ABC Insurance is a Medicaid Fiscal Agent. ABC Insurance has a payer identification of 12345.

XYZ Service, which is a Clearinghouse, has an electronic transmitter identification number of X67E which it uses to conduct electronic business transactions with ABC Insurance.

Home Hospital Pharmacy uses XYZ Service to submit electronic claims and claim status requests to ABC Insurance. Home Hospital Pharmacy’s National Provider Identifier (NPI) is 1666666662.

The following details are for 1 claim that XYZ Service requested status and ABC Insurance responded:

Claim 1

Request - Fred Smith is a Medicaid enrollee with a Medicaid subscriber identification of 123456789012. Mr. Smith’s birth date is 12/10/1930. A claim status tracking number of ABCXYZ1 was assigned to the status inquiry for Mr. Smith’s claim. Home Hospital Pharmacy requested the status of a claim for a pharmacy service on March 1, 2006 in the amount of $85. Home Hospital Pharmacy provided a pharmacy prescription number of 7654321.

Response - ABC Insurance assigned a payer claim control number of 05347006051. ABC Insurance provided status using a Claim Status Category of F2 (Finalized/Denied) and a National Council for Prescription Drug Programs (NCPDP) Reject/Payment Code of 80 (Drug- diagnosis mismatch) to indicated the denial reason. The NCPDP Status Code Source was identified by use of the RX Code Source Qualifier in STC01-4.

3.4.1 276 Request Transmission

The following is a 276 transmission XYZ Services sent to ABC Insurance requesting the status of a pharmacy claim.

ST*276*0001*005010X212~
BHT*0010*13*ABC276XXX*20060415*1425~
HL*1**20*1~
NM1*PR*2*ABC INSURANCE*****PI*12345~
HL*2*1*21*1~
NM1*41*2*XYZ SERVICE*****46*X67E~
HL*3*2*19*1~
NM1*1P*2*HOME HOSPITAL PHARMACY*****XX*1666666662~
HL*4*3*22*0~
DMG*D8*19301210*M~
NM1*IL*1*SMITH*FRED****MI*123456789012~
TRN*1*ABCXYZ1~
REF*XZ*7654321~
AMT*T3*85~
DTP*472*D8*20060301~
SE*16*0001~

3.4.2 277 Response Transmission

The following is the 277 transmission ABC Insurance sent in response to the 276 transmission from XYZ Service regarding the pharmacy claim status.

ST*277*0001*005010X212~
BHT*0010*08*277X212*20060415*0810*DG~
HL*1**20*1~
NM1*PR*2*ABC INSURANCE*****PI*12345~
HL*2*1*21*1~
NM1*41*2*XYZ SERVICE*****46*X67E~
HL*3*2*19*1~
NM1*1P*2*HOME HOSPITAL PHARMACY*****XX*1666666662~
HL*4*3*22*0~
NM1*IL*1*SMITH*FRED****MI*123456789012~
TRN*2*ABCXYZ1~
STC*F2:80::RX*20060301**85*0~
REF*1K*05347006051~
REF*XZ*7654321~
DTP*472*D8*20060301~
SE*16*0001~

Appendix A. External Code Sources

A.1 External Code Sources

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.

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.

135 American Dental Association

SIMPLE DATA ELEMENT/CODE REFERENCES

1361, 235/AD, 1270/JO, 1270/JP, 1270/TQ, 1270/AAY

SOURCE

Current Dental Terminology (CDT) Manual

AVAILABLE FROM

Salable Materials

American Dental Association

211 East Chicago Avenue

Chicago, IL 60611-2678

ABSTRACT

The CDT manual contains the American Dental Association's codes for dental procedures and nomenclature and is the accepted set of numeric codes and descriptive terms for reporting dental treatments and descriptors.

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.

507 Health Care Claim Status Category Code

SIMPLE DATA ELEMENT/CODE REFERENCES

1271

SOURCE

Health Care Claim Status Category Code

AVAILABLE FROM

Washington Publishing Company

http://www.wpc-edi.com

ABSTRACT

Code used to organize the Health Care Claim Status Codes into logical groupings.

508 Health Care Claim Status Code

SIMPLE DATA ELEMENT/CODE REFERENCES

1271, 1270/65

SOURCE

Health Care Claim Status Code

AVAILABLE FROM

Washington Publishing Company

http://www.wpc-edi.com

ABSTRACT

Code identifying the status of an entire claim or service line

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.

530 National Council for Prescription Drug Programs Reject/Payment Codes

SIMPLE DATA ELEMENT/CODE REFERENCES

1270/RX

SOURCE

National Council for Prescription Drug Programs Data Dictionary

AVAILABLE FROM

NCPDP

9240 East Raintree Drive

Scottsdale, AZ 85260

ABSTRACT

A listing of NCPDPs payment and reject reason codes, the explanation of the code, and the field number in error (if rejected).

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.

716 Health Insurance Prospective Payment System (HIPPS) Rate Code for Skilled Nursing Facilities

SIMPLE DATA ELEMENT/CODE REFERENCES

235/HP

SOURCE

Health Insurance Prospective Payment System (HIPPS) Rate Code for Skilled Nursing Facilities

AVAILABLE FROM

Division of Institutional Claims Processing

Centers for Medicare and Medicaid Services

C4-10-07

7500 Security Boulevard

Baltimore, MD 21244-1850

ABSTRACT

The Centers for Medicare and Medicaid services develops and publishes the HIPPS codes to establish a coding system for claims submission and claims payment under prospective payment systems. These codes represent the case mix classification groups that are used to determine payment rates under prospective payment systems. Case mix classification groups include, but may not be limited to, resource utilization groups (RUGs) for skilled nursing facilities, home health resource groups (HHRGs) for home health agencies, and case mix groups (CMGs) for inpatient rehabilitation facilities.

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.

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 relatedinformation. It is not a full statement of Interchange and Control Structure rules. Thefull X12 Interchange and Control Structures and other rules (X12.5, X12.6, X12.59, X12dictionaries, other X12 standards and official documents) apply unless specificallymodified 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 calledsegments. For instance, the N4 segment used in the transaction set conveys the city,state, ZIP Code, and other geographic information. A transaction set containsmultiple segments, so the addresses of the different parties, for example, can beconveyed from one computer to the other. An analogy would be that the transactionset is like a freight train; the segments are like the train's cars; and eachsegment can contain several data elements the same as a train car can hold multiplecrates.

The sequence of the elements within one segment is specified by the ASC X12standard as well as the sequence of segments in the transaction set. In a moreconventional computing environment, the segments would be equivalent to records, andthe elements equivalent to fields.

Similar transaction sets, called "functional groups," can be sent together withina transmission. Each functional group is prefaced by a group start segment; and afunctional group is terminated by a group end segment. One or more functional groupsare 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

CHARACTERNAMEDELIMITER
*AsteriskData Element Separator
^CaratRepetition Separator
:ColonComponent Element Separator
~TildeSegment 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

SYMBOLTYPE
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 exchangedbetween trading partners. The transaction set consists of a transaction setheader segment, one or more data segments in a specified order, and atransaction 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 istransmitted between trading/business partners. Interchange control is achievedthrough several "control" components. The interchange control number iscontained in data element ISA13 of the ISA segment. The identical control numbermust also occur in data element 02 of the IEA segment. Most commercialtranslation software products will verify that these two elements are identical.In most translation software products, if these elements are different theinterchange 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 ofdetail information using a hierarchical structure, such as relating dependentsto a subscriber. Hierarchical levels may differ from guide to guide.

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

Each guide states what levels are available, the level's usage, number ofrepeats, 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 X12NData 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 005010X212 of the Health Care Claim.

Status Request and Response (276/277). It is based on version/release/sub-release 005010 of the ASC X12 standards.

The previous X12N implementation Guide of the Health Care Claim Status Request and Response (276/277) was 004050X139. It was based on version/release/sub-release 004050 of the ASC X12 standards.

The 005010X212 Implementation Guide contains significant changes and clarifications. This appendix provides a high level description of changes between 004050X139 and 005010X212.

D.1 Change Descriptions

Overall Changes

  1. Sections one and two were revised in accordance with version 5010 of the ASC X12N Implementation Guide Handbook.
  2. All Situational loops, segments and data elements notes were modified in accordance with the ASC X12N Implementation Guide Handbook. See Section 2.2.1 Industry Usage and Section 2.2.1.1 Transaction Compliance Related to Industry Usage for further information about the Situational Rule format.
  3. Appendix A and Appendix B have been revised in accordance with version 5010 of the X12N Implementation Guide Handbook.
  4. The guide number (005010X212) is now documented in Section 1.2 Version Information. This identifier must be inserted as elements GS08 and ST03 in all Claim Status Requests and Responses created according to this implementation guide.
  5. The Functional Identifier Codes, HR (276) and HN (277) are now documented in Section 1.2 Version Information. These identifiers must be inserted as the applicable element GS01 in all Claim Status Requests and Responses created according to this implementation guide.
  6. All segment examples have been reviewed and brought up to date.
  7. All Alias names have been deleted.

Front Matter Changes

  1. The Front Matter sections pertaining to the transaction business use were rewritten and condensed into Section 1.4 Business Use for the purpose of clarity and consistency.
  2. Previous Table 1 and Table 2 segment by segment details, views and matrixes were eliminated for the purpose of reducing redundancy and gaining consistency with the actual Section 2 Transaction Set Views and Segment descriptions and usages.
  3. Section 1.4.3 277 Status Information (STC) Segment Usage and subsections were added to provide guidance on reporting consistency within the STC segment and the various status levels.
  4. Section 1.3.2.1 - Real Time and Batch Transmissions, was added to provide guidance and limitations between real-time and batch transaction reporting.
  5. Business terms were added to Section 1.5 Business Terminology.

276 Request - Loop, Segment, Element Changes

Table 1

  1. ST Segment - ST03 changed from Not Used to Required.

Table 2 - Information Source Detail

  1. Loop 2000A Information Source Level HL - Segment note was added.
  2. Loop 2100A Payer Name NM1 - NM108 qualifiers limited to PI and XV, NM108 qualifier note added to PI and NM109 element note eliminated.

Table 2 - Information Receiver Detail

  1. Loop 2000B Information Receiver Level HL - Segment note was changed.
  2. Loop 2100B Information Receiver Name NM1 - NM103 changed from Required to Situational, NM107 changed from Situational to Not Used, NM108 limited to qualifier 46 and a note was added to NM109.

Table 2 - Service Provider Detail

  1. Loop 2000C Service Provider Level HL - Segment note was added.
  2. Loop 2100C Provider Name NM1 - Loop repeat changed to 2, segment notes were added, NM103 changed from Required to Situational and NM108 qualifier SV note deleted.

Table 2 - Subscriber Detail

  1. Loop 2000D Subscriber Level HL - Segment note was changed and HL04=1 element note changed.
  2. Loop 2000D Subscriber Demographic Information DMG - DMG03 usage note changed and code 'U - Unknown' removed.
  3. Loop 2100D Subscriber Name NM1 - NM101 qualifier QC removed, NM102=2 note changed and NM108 qualifier ZZ replaced with II.

Table 2 - Dependent Detail

  1. Loop 2000E Dependent Level HL - Segment note was changed.
  2. Loop 2000E Dependent Demographic Information DMG - DMG03 usage note changed and code 'U - Unknown' removed.
  3. Loop 2100E Dependent Name NM1 - Changed NM106, NM108 and NM109 from Situational to Not Used.

Table 2 - Loop 2200D and Loop 2200E

  1. Loop 2200D/E Claim Status Tracking Number TRN - Loop and Segment name changed from Claim Submitter Trace Number to Claim Status Tracking Number. Segment rule, notes and data content of TRN02 value changed.
  2. Loop 2200D/E Payer Claim Control Number REF - Segment name changed from Payer Claim Identification Number to Payer Claim Control Number. Segment notes changed, usage changed and REF02 element note eliminated.
  3. Loop 2200D/E Institutional Bill Type Identification REF - Segment notes deleted and REF02 element note changed.
  4. Loop 2200D/E Medical Record Number REF - deleted.
  5. Loop 2200D/E Application or Location System Identifier REF - New segment added.
  6. Loop 2200D/E Group Number REF - Segment notes, data content and usage changed.
  7. Loop 2200D/E Patient Control Number REF - New segment added.
  8. Loop 2200D/E Pharmacy Prescription Number REF - New segment added.
  9. Loop 2200D/E Claim Identification Number for Clearinghouses and Other Transmission Intermediaries REF - New segment added.
  10. Loop 2200D/E Claim Submitted Charges AMT - Segment usage changed, segment note changed and AMT02 element note eliminated.
  11. Loop 2200D/E Claim Service Date DTP - Segment notes changed, example changed, DTP01 qualifier changed from '232' to '472', DTP02 element note changed and qualifier D8 added.

Table 2 - Loop 2210D and Loop 2210E

  1. Loop 2210D/E Service Line Information SVC - For SVC01-1: qualifiers ER and HP were added, qualifiers ID and NH were deleted and notes were added to qualifiers IV, ER and WK, usage notes changed for SVC01-3 through SVC01-6, SVC04 usage note changed and SVC07 changed from Situational to Required.
  2. Loop 2210D/E Service Line Item Identification REF - Segment usage note and example changed.
  3. Loop 2210D/E Service Line Date DTP - Segment note deleted, DTP02 element note changed and qualifier D8 added to DTP02.

277 Response - Loop, Segment, Element Changes

Table 1

  1. ST Segment - ST03 changed from Not Used to Required.

Table 2 - Information Source Detail

  1. Loop 2000A Information Source Level HL - Segment note was added.
  2. Loop 2100A Payer Name NM1 - NM108 qualifiers limited to PI and XV, NM108 qualifier note added to PI and NM109 element note eliminated.
  3. Loop 2100A Payer Contact Information PER - Segment usage rule changed, PER02 notes changed, qualifier ED was added to PER05 and PER07.

Table 2 - Information Receiver Detail

  1. Loop 2000B Information Receiver Level HL - Segment note changed and the notes for HL04 values were changed.
  2. Loop 2100B Information Receiver Name NM1 - NM103 changed from Required to Situational, NM107 changed from Situational to Not Used, NM108 limited to qualifier 46 and an element note added to NM109.
  3. Loop 2200B Information Receiver Trace Identifier TRN - Removed 'Application' from Segment Name, segment rule and note were changed and TRN02 note changed.
  4. Loop 2200B Information Receiver Status Information STC - Segment note changed, usage for composites STC10 and STC11 were changed, all sub-element notes for STC01, STC10 and STC11 composites changed, usage rules for STC01-3, STC10-3 and STC11-3 changed, code values 40 and 85 were eliminated from STC01-3, STC10-3 and STC11-3 and STC01-4, STC10-4 and STC11-4 were changed from Required to Not Used.

Table 2 - Service Provider Detail

  1. Loop 2000C Service Provider Level HL - Segment rule changed, segment note changed and usage notes were added to the HL04 values.
  2. Loop 2100C Provider Name NM1 - Loop repeat changed to 2, segment notes added, NM103 changed from Required to Situational, NM106 changed from Situational to Not Used and NM108 qualifier SV note deleted.
  3. Loop 2200C Provider of Service Trace Identifier TRN - Removed 'Information' from Segment Name, segment rule changed and segment note on data content added for clarification.
  4. Loop 2200C Provider Status Information STC - Removed 'Billing' from segment name, segment note added, usage for composites STC10 and STC11 were changed, all sub-element notes for STC01, STC10 and STC11 composites changed, usage rules for STC01-3, STC10-3 and STC11-3 changed, code value for STC01-3, STC10-3 and STC11-3 changed from 82 and 85 to 1P and STC01-4, STC10-4 and STC11-4 were changed from Required to Not Used.

Table 2 - Subscriber Detail

  1. Loop 2000D Subscriber Level HL - Segment rule changed, segment note changed and the notes were changed for the HL04 values.
  2. Loop 2000D Subscriber Demographic Information DMG - Segment deleted.
  3. Loop 2100D Subscriber Name NM1 - NM101 qualifier QC removed, NM102=2 note changed, NM106 changed from Situational to Not Used and NM108 qualifier ZZ replaced with II.

Table 2 - Dependent Detail

  1. Loop 2000E Dependent Level HL - Segment rule and notes changed.
  2. Loop 2000E Dependent Demographic Information DMG - Segment deleted.
  3. Loop 2100E Dependent Name NM1 - Element note removed from NM104 and changed NM106, NM108 and NM109 from Situational to Not Used.

Table 2 - Loop 2200D and Loop 2200E

  1. Loop 2200D/E Claim Status Tracking Number TRN - Loop and Segment name changed from Claim Submitter Trace Number to Claim Status Tracking Number. Segment rule, notes and data content of TRN02 value changed.
  2. Loop 2200D/E Claim Level Status Information STC - Segment repeat changed to >1, segment note added, additional TR3 example added, all sub-element notes for STC01, STC10 and STC11 composites changed, data content note added for STC01-1, STC10-1 and STC11-1, usage rule for STC01-3, STC10-3 and STC11-3 changed, code values 03, MSC, TL, PRP, SEP and TTP were added to STC01-3, STC10-3 and STC11-3, usage changed from Not Used to Situational for STC01-4, STC10-4 and STC11-4, usage rule and code value RX added for STC01-4, STC10-4 and STC11-4, STC02 note changed, STC04 usage rule changed, STC05 usage rule changed, STC06 usage and notes changed, STC07 changed from Situational to Not Used, STC08 usage and notes changed and STC09 usage and notes changed.
  3. Loop 2200D/E Payer Claim Control Number REF - Segment name changed from Payer Claim Identification Number to Payer Claim Control Number. Segment notes and usage changed.
  4. Loop 2200D/E Institutional Bill Type Identification REF - Segment notes deleted and REF02 element note changed.
  5. Loop 2200D/E Medical Record Number REF - deleted.
  6. Loop 2200D/E Patient Control Number REF - New segment added.
  7. Loop 2200D/E Pharmacy Prescription Number REF - New segment added.
  8. Loop 2200D/E Voucher Identifier REF - New segment added.
  9. Loop 2200D/E Claim Identification Number for Clearinghouses and Other Transmission Intermediaries REF - New segment added.
  10. Loop 2200D/E Claim Service Date DTP - Segment usage and notes changed, example changed, DTP01 qualifier changed from '232' to '472', DTP02 element note changed and qualifier D8 was added to DTP02.

Table 2 - Loop 2220D and Loop 2220E

  1. Loop 2220D/E Service Line Information SVC - SVC01 element note changed, for SVC01-1: qualifiers ER and HP were added, qualifiers ID and NH were deleted and notes were added to qualifiers IV, ER and WK, usage notes changed for SVC01-3 through SVC01-6, SVC02 notes changed, SVC04 usage note changed and SVC07 changed from Situational to Required.
  2. Loop 2220D/E Service Line Status Information STC - Segment repeat changed to >1, segment note changed, additional TR3 example added, all sub-element notes for STC01, STC10 and STC11 composites changed, data content note added for STC01-1, STC10-1 and STC11-1, usage rules for STC01-3, STC10-3 and STC11-3 changed, code values 03, MSC, TL, PRP, SEP and TTP were added to STC01-3, STC10-3 and STC11-3, usage changed from Not Used to Situational for STC01-4, STC10-4 and STC11-4, usage rule and code value RX added for STC01-4, STC10-4 and STC11-4, and STC02 note changed.
  3. Loop 2220D/E Service Line Item Identification REF - Segment usage note and example changed.
  4. Loop 2220D/E Service Line Date DTP - Segment changed from Situational to Required, segment note deleted, DTP02 element note changed and qualifier D8 was added to DTP02.

Section 3 Examples

  1. The existing scenario was rewritten and updated.
  2. A new business scenario was added for a Provider Level Status Response.
  3. A new business scenario was added for an Information Receiver Level Status Response.
  4. A new business scenario was added for a Claim Level Status Response with NCPDP Reject/Payment Code.

Appendix A External Code Sources

  1. The following Code Sources were added: 507 - Health Care Claim Category Codes, 508 - Health Care Claim Status Codes, 530 - National Council for Prescription Drug Programs Reject/Payment Codes, 576 - Workers Compensation Specific Procedure and Supply Codes and 716 - Health Insurance Prospective Payment System (HIPPS) Rate Code for Skilled Nursing.

Appendix D Change Summary

  1. Updated with changes from 004050X139 to 005010X212.