278 Transaction Set Listing

006020X315 Health Care Services Review - Request for Review and Response
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✱^✱00602✱000000905✱0✱T✱:~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
I01
Authorization Information Qualifier
M 1
ID
2
Code identifying the type of information in the Authorization Information
CODE
DEFINITION
00
No Authorization Information Present (No Meaningful Information in I02)
03
Additional Data Identification
Required
2
I02
Authorization Information
M 1
AN
10
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
Required
3
I03
Security Information Qualifier
M 1
ID
2
Code identifying the type of information in the Security Information
CODE
DEFINITION
00
No Security Information Present (No Meaningful Information in I04)
01
Password
Required
4
I04
Security Information
M 1
AN
10
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
Required
5
I05
Interchange ID Qualifier
M 1
ID
2
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
This ID qualifies the Sender in ISA06.
CODE
DEFINITION
01
Duns (Dun & Bradstreet)
14
Duns Plus Suffix
20
Health Industry Number (HIN)
CODE SOURCE: 121: Health Industry Number
27
Carrier Identification Number as assigned by Centers for Medicare & Medicaid Services (CMS)
28
Fiscal Intermediary Identification Number as assigned by Centers for Medicare & Medicaid Services (CMS)
29
Medicare Provider and Supplier Identification Number as assigned by Centers for Medicare & Medicaid Services (CMS)
30
U.S. Federal Tax Identification Number
33
National Association of Insurance Commissioners Company Code (NAIC)
ZZ
Mutually Defined
Required
6
I06
Interchange Sender ID
M 1
AN
15
Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Required
7
I05
Interchange ID Qualifier
M 1
ID
2
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
This ID qualifies the Receiver in ISA08.
CODE
DEFINITION
01
Duns (Dun & Bradstreet)
14
Duns Plus Suffix
20
Health Industry Number (HIN)
CODE SOURCE: 121: Health Industry Number
27
Carrier Identification Number as assigned by Centers for Medicare & Medicaid Services (CMS)
28
Fiscal Intermediary Identification Number as assigned by Centers for Medicare & Medicaid Services (CMS)
29
Medicare Provider and Supplier Identification Number as assigned by Centers for Medicare & Medicaid Services (CMS)
30
U.S. Federal Tax Identification Number
33
National Association of Insurance Commissioners Company Code (NAIC)
ZZ
Mutually Defined
Required
8
I07
Interchange Receiver ID
M 1
AN
15
Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them
Required
9
I08
Interchange Date
M 1
DT
6
Date of the interchange
The date format is YYMMDD.
Required
10
I09
Interchange Time
M 1
TM
4
Time of the interchange
The time format is HHMM.
Required
11
I65
Repetition Separator
M 1
Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator
Required
12
I11
Interchange Control Version Number
M 1
ID
5
Code specifying the version number of the interchange control segments
CODE
DEFINITION
00602
Standards Approved for Publication by ASC X12 Procedures Review Board through October 2009
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
X12.5 - Interchange Control Structure, provides the purpose of the TA1 segment. The X12 Acknowledgment Reference Model provides considerable information about the TA1 segment.
CODE
DEFINITION
0
No Interchange Acknowledgment Requested
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*HI - FUNCTIONAL GROUP HEADER

X12 Name:
Functional Group Header
X12 Purpose:
To indicate the beginning of a functional group and to provide control information
X12 Comments:
A functional group of related transaction sets, within the scope of X12 standards, consists of a collection of similar transaction sets enclosed by a functional group header and a functional group trailer.
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
GS✱XX✱SENDER CODE✱RECEIVER CODE✱19991231✱0802✱1✱X✱006020X315~
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
HI
Health Care Services Review Information (278)
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
006020X315
Health Care Services Review - Request for Review and Response

ST*278 - 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 Notes:
Use this segment to indicate the start of a health care services review request transaction set with all of the supporting detail information. This transaction set is the electronic equivalent of a phone, fax, or paper-based utilization management request.
TR3 Example:
ST✱278✱0001✱006020X315~
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
278
Health Care Services Review Information
Required
2
329
Transaction Set Control Number
M 1
AN
4/9
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
The Transaction Set Control Numbers in ST02 and SE02 must be identical and must be a numeric value. The number (i.e. numeric value) is assigned by the originator and must be unique within a functional group (GS-GE). For example, start with the numeric value 0001 and increment from there. The Transaction Set Control Number also aids in error resolution research.
Required
3
1705
Implementation Convention Reference
O 1
AN
1/35
Reference assigned to identify Implementation Convention
SEMANTIC: The implementation convention reference (ST03) is used by the translation routines of the interchange partners to select the appropriate implementation convention to match the transaction set definition. When used, this implementation convention reference takes precedence over the implementation reference specified in the GS08.
INDUSTRY NAME: Implementation Guide Version Name
  1. This element must be populated with the guide identifier named in Section 1.2.
  2. This field contains the same value as GS08. Some translator products strip off the ISA and GS segments prior to application (ST-SE) processing. Providing the information from the GS08 at this level will ensure that the appropriate application mapping is utilized at translation time.
CODE
DEFINITION
006020X315
Health Care Services Review - Request for Review and Response

BHT*0007 - 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✱0007✱13✱200300114000001✱20111001✱1400~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1005
Hierarchical Structure Code
M 1
ID
4
Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set
Used to specify the sequential order of HL segments. The HL loops in the data stream must comply with this sequential order. An HL parent loop must be followed by any subordinate child loops prior to commencing a new HL parent loop at the same hierarchical level.
CODE
DEFINITION
0007
Information Source, Information Receiver, Subscriber, Dependent, Event, Services
Required
2
353
Transaction Set Purpose Code
M 1
ID
2
Code identifying purpose of transaction set
CODE
DEFINITION
01
Cancellation
Use this code to cancel a previously submitted 278 transaction. Only 278 transactions that used a BHT06 code of "RU" can be canceled. The cancellation 278 transaction must contain the same BHT06 code as the previously submitted 278 transaction.
13
Request
36
Authority to Deduct (Reply)
Use this code for medical services reservations to reserve or deduct a service with the health plan. BHT06 must be equal to "RU".
Required
3
127
Reference Identification
O 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: BHT03 is the number assigned by the originator to identify the transaction within the originator's business application system.
INDUSTRY NAME: Submitter Transaction Identifier
  1. Use this element to trace the transaction from one point to the next point, such as when the transaction is passed from one clearinghouse to another clearinghouse. This identifier must be returned in the corresponding 278 response transaction's BHT03. This identifier will only be returned by the last entity to handle the 278. This identifier will not be passed through the complete life of the transaction. All recipients of 278 request transactions are required to return the Submitter Transaction Identifier in their 278 response if one is submitted.
  2. Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Required
4
373
Date
O 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: BHT04 is the date the transaction was created within the business application system.
INDUSTRY NAME: Transaction Set Creation Date
Required
5
337
Time
O 1
TM
4/8
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
SEMANTIC: BHT05 is the time the transaction was created within the business application system.
INDUSTRY NAME: Transaction Set Creation Time
Situational
6
640
Transaction Type Code
O 1
ID
2
Code specifying the type of transaction
SITUATIONAL RULE: Required when requesting Medical Services Reservation. If not required by this implementation guide, do not send.
CODE
DEFINITION
RU
Medical Services Reservation

HL - UTILIZATION MANAGEMENT ORGANIZATION (UMO) 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 segment indicates the information source hierarchical level. For a request transaction, this segment corresponds to the identification of the payer, HMO, or other utilization management organization who will be the source of the decision/response.
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.
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 - UTILIZATION MANAGEMENT ORGANIZATION (UMO) 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 segment identifies the source of information. In the case of a request transaction, the source of information would normally be the payer or utilization review organization making the decision on the request.
TR3 Example:
NM1✱X3✱2✱ABC PAYER✱✱✱✱✱46✱123450000~
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
2B
Third-Party Administrator
36
Employer
PR
Payer
Use only when the organization receiving the request is a health plan but is not the entity rendering the medical decision, as in plan to plan communication or communication from the health plan to the medical review organization.
X3
Utilization Management Organization
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Use this code only if the reviewing entity is an individual, such as an individual primary care physician.
2
Non-Person Entity
Situational
3
1035
Name Last or Organization Name
X 1
AN
1/60
Individual last name or organizational name
SEGMENT SYNTAX: C1203
SITUATIONAL RULE: Required when name information is needed to identify the UMO. If not required by this implementation guide, do not send.
INDUSTRY NAME: Utilization Management Organization (UMO) Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when NM103 is valued and the reviewing entity is an individual (NM102 = 1), such as a primary care provider. If not required by this implementation guide, do not send.
INDUSTRY NAME: Utilization Management Organization (UMO) First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when NM104 is present and the middle name/initial of the person is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Utilization Management Organization (UMO) 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 NM104 is valued and the suffix of the individual's name is known; e.g. Sr., Jr., or III. If not required by this implementation guide, do not send.
INDUSTRY NAME: Utilization Management Organization (UMO) Name Suffix
Required
8
66
Identification Code Qualifier
X 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
34
Social Security Number
46
Electronic Transmitter Identification Number (ETIN)
PI
Payor Identification
Use when UMO is a payer and XV is not used.
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
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
INDUSTRY NAME: Utilization Management Organization (UMO) Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/60

HL - REQUESTER 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 segment indicates the health care services review information receiver. For request transactions, this segment corresponds to the identification of the entity initiating the request for review.
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.
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 - REQUESTER 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 segment identifies the receiver of information. In the case of a request transaction, the receiver would normally be the entity who will ultimately be receiving the decision.
TR3 Example:
NM1✱1P✱1✱WHITE✱CHRIS✱✱✱✱XX✱1234567890~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
1P
Provider
Use when the requester is an individual provider.
2B
Third-Party Administrator
36
Employer
FA
Facility
Use when the requester is a facility, such as a clinic or hospital.
PR
Payer
Use only when the organization sending the request is a health plan, as in plan to plan communication or communication from the health plan to the medical review organization.
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
X 1
AN
1/60
Individual last name or organizational name
SEGMENT SYNTAX: C1203
SITUATIONAL RULE: Required when name information is needed to identify the requester. If not required by this implementation guide, do not send.
INDUSTRY NAME: Requester Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when NM103 is present and NM102 = 1. If not required by this implementation guide, do not send.
INDUSTRY NAME: Requester First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when NM104 is present and the middle name/initial of the person is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Requester 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 NM104 is valued and the suffix of the individual's name is known; e.g. Sr., Jr., or III. If not required by this implementation guide, do not send.
INDUSTRY NAME: Requester Name Suffix
Situational
8
66
Identification Code Qualifier
X 1
ID
1/2
Code designating the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when requesting the services of a specific person, facility, group practice, or clinic and the provider NPI is known by the requester. If not required by this implementation guide, do not send.
CODE
DEFINITION
XX
Centers for Medicare and Medicaid Services National Provider Identifier
Required for providers in the United States or its territories when the provider is eligible to receive a National Provider Identifier (NPI).

OR

Required for providers not in the United States or its territories when the provider has received an NPI. If not required by this implementation guide, do not send.
CODE SOURCE: 537: Centers for Medicare & Medicaid Services National Provider Identifier
Situational
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when requesting the services of a specific person, facility, group practice, or clinic and the provider NPI is known by the requester. If not required by this implementation guide, do not send.
INDUSTRY NAME: Requester Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/60

REF - REQUESTER SUPPLEMENTAL 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:
8
Situational Rule:
Required when NM109 of this loop is not used and an identifier is necessary for the receiver to identify the provider. If not required by this implementation guide, do not send.
TR3 Example:
REF✱ZH✱A12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
0B
State License Number
1J
Facility ID Number
EI
Employer's Identification Number
G5
Provider Site Number
Required when needed to identify the physician, clinic, or group practice associated with the requester identified in this NM1 loop.
N5
Provider Plan Network Identification Number
N7
Facility Network Identification Number
SY
Social Security Number
The social security number must not be used for any Federally administered programs such as Medicare or CHAMPUS.
ZH
Carrier Assigned Reference Number
Required when necessary to provide the requester/provider ID as assigned by the UMO identified in Loop 2000A.
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Requester Supplemental Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

N3 - REQUESTER ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when necessary to identify the requester by location. If not required, by this implementation guide, do not send.
TR3 Notes:
Use to identify a specific location when the requester has multiple locations and authority varies based on location.
TR3 Example:
N3✱123 MAIN STREET~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Requester Address Line
Use this element for the first line of the requester's address.
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when a second address line is needed. If not required by this implementation guide, do not send.
INDUSTRY NAME: Requester Address Line

N4 - REQUESTER CITY, STATE, ZIP CODE

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

PER*IC - REQUESTER CONTACT INFORMATION

X12 Name:
Administrative Communications Contact
X12 Purpose:
To identify a person or office to whom administrative communications should be directed
X12 Syntax:
  1. P0304
    If either PER03 or PER04 is present, then the other is required.
  2. P0506
    If either PER05 or PER06 is present, then the other is required.
  3. P0708
    If either PER07 or PER08 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
2
Situational Rule:
Required when the UMO must direct requests for additional information to a specific requester contact, electronic mail, facsimile, or telephone number. If not required by this implementation guide, do not send.
TR3 Notes:
When the communication number represents a telephone number in the United States and other countries using the North American Dialing Plan (for voice, data, fax, etc.), the communication number must always include the area code and phone number using the format AAABBBCCCC where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number. Therefore, the following telephone number (555) 555-1234 would be represented as 5555551234. Do not submit long distance access numbers, such as 1, in the telephone number. Telephone extensions, when applicable, must be submitted in the next element immediately following the telephone number. When submitting telephone extensions, only submit the numeric extension, do not include data that indicates an extension, such as "ext" or "x-".
TR3 Example:
PER✱IC✱JOHN SMITH✱TE✱5555551234✱EX✱123~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
366
Contact Function Code
M 1
ID
2
Code identifying the major duty or responsibility of the person or group named
CODE
DEFINITION
IC
Information Contact
Situational
2
93
Name
O 1
AN
1/60
Free-form name
SITUATIONAL RULE: Required when the response must be directed to a particular contact and the name of the entity to contact is not already defined or is different than the name supplied in the NM1 segment of this loop. If not required by this implementation guide, do not send.
INDUSTRY NAME: Requester Contact Name
Situational
3
365
Communication Number Qualifier
X 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0304
SITUATIONAL RULE: Required when PER02 is not valued, or to transmit a contact communication number. If not required by this implementation guide, do not send.
CODE
DEFINITION
EM
Electronic Mail
FX
Facsimile
TE
Telephone
UR
Uniform Resource Locator (URL)
Must not contain any characters used as delimiters in this transaction.
Situational
4
364
Communication Number
X 1
AN
1/256
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0304
SITUATIONAL RULE: Required when PER02 is not valued, or to transmit a contact communication number. If not required by this implementation guide, do not send.
INDUSTRY NAME: Requester Contact Communication Number
Situational
5
365
Communication Number Qualifier
X 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
EM
Electronic Mail
EX
Telephone Extension
FX
Facsimile
TE
Telephone
UR
Uniform Resource Locator (URL)
Must not contain any characters used as delimiters in this transaction.
Situational
6
364
Communication Number
X 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: Requester Contact Communication Number
Situational
7
365
Communication Number Qualifier
X 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
EM
Electronic Mail
EX
Telephone Extension
FX
Facsimile
TE
Telephone
UR
Uniform Resource Locator (URL)
Must not contain any characters used as delimiters in this transaction.
Situational
8
364
Communication Number
X 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: Requester Contact Communication Number
Not Used
9
443
Contact Inquiry Reference
O 1
AN
1/20

PRV - REQUESTER PROVIDER INFORMATION

X12 Name:
Provider Information
X12 Purpose:
To specify the identifying characteristics of a provider
X12 Syntax:
P0203
If either PRV02 or PRV03 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when needed to indicate the requester's role in the care of the patient and the requesting provider's specialty. If not required by this implementation guide, do not send.
TR3 Example:
PRV✱PE✱PXC✱1223G0001X~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1221
Provider Code
M 1
ID
1/3
Code identifying the type of provider
CODE
DEFINITION
AD
Admitting
AS
Assistant Surgeon
AT
Attending
CO
Consulting
CV
Covering
OP
Operating
OR
Ordering
OT
Other Physician
PC
Primary Care Physician
PE
Performing
RF
Referring
Situational
2
128
Reference Identification Qualifier
X 1
ID
2/3
Code qualifying the Reference Identification
SEGMENT SYNTAX: P0203
SITUATIONAL RULE: Required when necessary to identify the requesting provider's specialty. If not required by this implementation guide, do not send.
CODE
DEFINITION
PXC
Health Care Provider Taxonomy Code
CODE SOURCE: 682: Health Care Provider Taxonomy
Situational
3
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: P0203
SITUATIONAL RULE: Required when necessary to identify the requesting provider's specialty. If not required by this implementation guide, do not send.
INDUSTRY NAME: Provider Taxonomy Code
  1. Provider Specialty Code
  2. Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
4
156
State or Province Code
O 1
ID
2
Not Used
5
C035
Provider Specialty Information
O 1
Not Used
6
1223
Provider Organization Code
O 1
ID
3

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:
This segment indicates the subscriber hierarchical level. This segment corresponds to the identification of the subscriber or individual insured member. The subscriber could also be the patient. If the subscriber is the patient or the patient has a unique insurance identifier, the dependent hierarchical level (Loop 2000D) is not used.
TR3 Example:
HL✱3✱2✱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.
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
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.

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 Notes:
  1. This segment conveys the name and identification number of the subscriber (who may also be the patient).
  2. The Member Identification Number (NM108/NM109) is required and may be adequate to identify the subscriber to the UMO. However, the UMO can require additional information. The maximum data elements that the UMO can require to identify the subscriber, in addition to the member ID are as follows:
    Subscriber Last Name (NM103)
    Subscriber First Name (NM104)
    Subscriber Birth Date (DMG01 and DMG02)
  3. Refer to Section 1.11.2 Identifying the Patient for specific information on how to identify an individual to a UMO.
TR3 Example:
NM1✱IL✱1✱DOE✱JOHN✱T✱✱JR✱MI✱123456~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
IL
Insured or Subscriber
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Situational
3
1035
Name Last or Organization Name
X 1
AN
1/60
Individual last name or organizational name
SEGMENT SYNTAX: C1203
SITUATIONAL RULE: Required when name information is needed by the UMO to identify the subscriber. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Last Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when name information is needed by the UMO to identify the subscriber. 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 name information is needed by the UMO to identify the subscriber and the middle name/initial of the subscriber is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Middle Name or Initial
Situational
6
1038
Name Prefix
O 1
AN
1/10
Prefix to individual name
SITUATIONAL RULE: Required when subscriber's military title or rank is needed by the UMO to further identify the subscriber. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Name Prefix
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when the suffix of an individual's name is needed to further identify the subscriber; e.g., Sr., Jr., or III. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Name Suffix
Required
8
66
Identification Code Qualifier
X 1
ID
1/2
Code designating the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
CODE
DEFINITION
II
Standard Unique Health Identifier for each Individual in the United States
The value "II" when used in this data element, shall be defined as "HIPAA Individual Identifier" if this identifier has been adopted. Under the Health Insurance Portability and Accountability Act of 1996, the Secretary of Health and Human Services must adopt a standard individual identifier for use in this transaction.
MI
Member Identification Number
The code MI is intended to be the subscriber's identification number as assigned by the payer. Payers use different terminology to convey the same number. Use MI - Member Identification Number to convey the following terms: Insured's ID, Subscriber's ID, Health Insurance Claim Number (HIC), etc.
Required
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
INDUSTRY NAME: Subscriber Primary Identifier
Subscriber Member Number
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/60

REF - SUBSCRIBER SUPPLEMENTAL 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:
9
Situational Rule:
Required when needed to provide a supplemental identifier for the subscriber. If not required by this implementation guide, do not send.
TR3 Notes:
  1. The primary identifier is the Member Identification Number in the NM1 segment.
  2. Health Insurance Claim (HIC) Number or Medicaid Recipient Identification Number is provided in the NM1 segment as a Member Identification Number when it is the primary number by which the UMO knows the member (such as for Medicare or Medicaid). Do not use this segment for the Health Insurance Claim (HIC) Number or Medicaid Recipient Identification Number unless it is different from the Member Identification Number provided in the NM1 segment.
  3. If the requester values this segment with the Patient Account Number (REF01 = "EJ") on the request, the UMO is required to return the same value in this segment on the response.
TR3 Example:
REF✱SY✱123456789~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
1L
Group or Policy Number
Use this code only if you cannot determine if the number is a Group Number (6P) or a Policy Number (IG).
3L
Branch Identifier
6P
Group Number
DP
Department Number
EJ
Patient Account Number
The maximum number of characters to be supported in REF02 for this qualifier is `20'. Characters beyond the maximum are not required to be stored nor returned by any receiving system. Use this code only if the subscriber is the patient.
F6
Health Insurance Claim (HIC) Number
Use the NM1 (Subscriber Name) segment if the subscriber's HIC number is the primary identifier for his or her coverage. Use this code only in a REF segment when the payer has a different member number, and there is also a need to pass the subscriber's HIC number. This might occur in a Medicare HMO situation.
HJ
Identity Card Number
Use this code when the Identity Card Number differs from the Member Identification Number. This is particularly prevalent in the Medicaid environment.
IG
Insurance Policy Number
N6
Plan Network Identification Number
NQ
Medicaid Recipient Identification Number
SY
Social Security Number
Use this code only if the Social Security Number is not the primary identifier for the subscriber. The social security number must not be used for any Federally administered programs such as Medicare or CHAMPUS.
Y4
Agency Claim Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Subscriber Supplemental Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

N3 - SUBSCRIBER ADDRESS

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

N4 - SUBSCRIBER CITY, STATE, ZIP CODE

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

DMG*D8 - SUBSCRIBER DEMOGRAPHIC INFORMATION

X12 Name:
Demographic Information
X12 Purpose:
To supply demographic information
X12 Syntax:
  1. P0102
    If either DMG01 or DMG02 is present, then the other is required.
  2. P1011
    If either DMG10 or DMG11 is present, then the other is required.
  3. C1105
    If DMG11 is present, then DMG05 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when birth date is needed to identify the patient or when gender information is required to determine medical necessity. If not required by this implementation guide, do not send.
TR3 Notes:
Refer to Section 1.11.2 Identifying the Patient for specific information on how to identify an individual to a UMO.
TR3 Example:
DMG✱D8✱19690815✱M~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEGMENT SYNTAX: P0102
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
2
1251
Date Time Period
X 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
SEMANTIC: DMG02 is the date of birth.
SEGMENT SYNTAX: P0102
INDUSTRY NAME: Subscriber Birth Date
Situational
3
1068
Gender Code
O 1
ID
1
Code indicating the sex of the individual
SITUATIONAL RULE: Required when gender (DMG03) was used to determine medical necessity. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Gender Code
CODE
DEFINITION
F
Female
M
Male
U
Unknown
Not Used
4
1067
Marital Status Code
O 1
ID
1
Not Used
5
C056
Composite Race or Ethnicity Information
X 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
X 1
ID
1/3
Not Used
11
1271
Industry Code
X 1
AN
1/30
Not Used
12
26
Country Code
O 1
ID
2/3

INS*Y - SUBSCRIBER RELATIONSHIP

X12 Name:
Insured Benefit
X12 Purpose:
To provide benefit information on insured entities
X12 Syntax:
P1112
If either INS11 or INS12 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when subscriber's military role is needed by the UMO to further identify the subscriber. If not required by this implementation guide, do not send.
TR3 Example:
INS✱Y✱18✱✱✱✱✱✱AO~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: INS01 indicates status of the insured. A "Y" value indicates the insured is a subscriber: an "N" value indicates the insured is a dependent.
INDUSTRY NAME: Insured Indicator
CODE
DEFINITION
Y
Yes
Required
2
1069
Individual Relationship Code
M 1
ID
2
Code indicating the relationship between two individuals or entities
Relationship to Insured Code
CODE
DEFINITION
18
Self
Not Used
3
875
Maintenance Type Code
O 1
ID
3
Not Used
4
1203
Maintenance Reason Code
O 1
ID
2/3
Not Used
5
1216
Benefit Status Code
O 1
ID
1
Not Used
6
C052
Medicare Status Code
O 1
Not Used
7
1219
Consolidated Omnibus Budget Reconciliation Act (COBRA) Qualifying
O 1
ID
1/2
Required
8
584
Employment Status Code
O 1
ID
2
Code showing the general employment status of an employee/claimant
Use to qualify the patient's relationship to the military.
CODE
DEFINITION
AO
Active Military - Overseas
AU
Active Military - USA
DI
Deceased
PV
Previous
RU
Retired Military - USA
Not Used
9
1220
Student Status Code
O 1
ID
1
Not Used
10
1073
Yes/No Condition or Response Code
O 1
ID
1
Not Used
11
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Not Used
12
1251
Date Time Period
X 1
AN
1/35
Not Used
13
1165
Confidentiality Code
O 1
ID
1
Not Used
14
19
City Name
O 1
AN
2/30
Not Used
15
156
State or Province Code
O 1
ID
2
Not Used
16
26
Country Code
O 1
ID
2/3
Not Used
17
1470
Number
O 1
N
1/9

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 someone other than the subscriber and the patient does not have a unique (different from the subscriber) member ID. If not required by this implementation guide, do not send.
TR3 Notes:
  1. If the patient has a unique member ID, use Loop 2000C to identify the patient.
  2. Required segments in this loop are required only when this loop is used.
TR3 Example:
HL✱4✱3✱23✱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.
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
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*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 Notes:
  1. This segment conveys the name of the dependent who is the patient.
  2. The maximum data elements in Loop 2010D that can be required by a UMO to identify a dependent are as follows:
    Dependent Last Name (NM103)
    Dependent First Name (NM104)
    Dependent Birth Date (DMG01 and DMG02)
  3. Refer to Section 1.11.2 Identifying the Patient for specific information on how to identify an individual to a UMO.
TR3 Example:
NM1✱QC✱1✱DOE✱SALLY✱J~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
QC
Patient
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Situational
3
1035
Name Last or Organization Name
X 1
AN
1/60
Individual last name or organizational name
SEGMENT SYNTAX: C1203
SITUATIONAL RULE: Required when name information is needed by the UMO to identify the dependent. If not required by this implementation guide, do not send.
INDUSTRY NAME: Dependent Last Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when name information is needed by the UMO to identify the dependent. If not required by this implementation guide, do not send.
INDUSTRY NAME: Dependent First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when name information is needed by the UMO to identify the dependent and the middle name/initial of the dependent is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Dependent 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 name information is needed by the UMO to identify the dependent and the suffix of an individual's name; e.g. Sr., Jr., or III of the dependent is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Dependent Name Suffix
Not Used
8
66
Identification Code Qualifier
X 1
ID
1/2
Not Used
9
67
Identification Code
X 1
AN
2/80
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/60

REF - DEPENDENT SUPPLEMENTAL IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
2
Situational Rule:
Required when needed to provide a supplemental identifier for the dependent. If not required by this implementation guide, do not send.
TR3 Notes:
  1. Use the Subscriber Supplemental Identifier (REF) segment in Loop 2010C for supplemental identifiers related to the subscriber's policy or group number.
  2. If the requester values this segment with the Patient Account Number (REF01 = "EJ") on the request, the UMO is required to return the same value in this segment on the response.
TR3 Example:
REF✱SY✱123456789~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
EJ
Patient Account Number
The maximum number of characters to be supported in REF02 for this qualifier is `20'. Characters beyond the maximum are not required to be stored nor returned by any receiving system.
SY
Social Security Number
The social security number may not be used for any Federally administered programs such as Medicare or TRICARE.

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

N3 - DEPENDENT ADDRESS

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

N4 - DEPENDENT CITY, STATE, ZIP CODE

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

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.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when birth date is needed to identify the patient or when gender information is required to determine medical necessity. If not required by this implementation guide, do not send.
TR3 Notes:
Refer to Section 1.11.2 Identifying the Patient for specific information on how to identify an individual to a UMO.
TR3 Example:
DMG✱D8✱19690815✱M~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEGMENT SYNTAX: P0102
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
2
1251
Date Time Period
X 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
SEMANTIC: DMG02 is the date of birth.
SEGMENT SYNTAX: P0102
INDUSTRY NAME: Dependent Birth Date
Situational
3
1068
Gender Code
O 1
ID
1
Code indicating the sex of the individual
SITUATIONAL RULE: Required when gender (DMG03) was used to determine medical necessity. If not required by this implementation guide, do not send.
INDUSTRY NAME: Dependent Gender Code
CODE
DEFINITION
F
Female
M
Male
U
Unknown
Not Used
4
1067
Marital Status Code
O 1
ID
1
Not Used
5
C056
Composite Race or Ethnicity Information
X 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
X 1
ID
1/3
Not Used
11
1271
Industry Code
X 1
AN
1/30
Not Used
12
26
Country Code
O 1
ID
2/3

INS*N - DEPENDENT RELATIONSHIP

X12 Name:
Insured Benefit
X12 Purpose:
To provide benefit information on insured entities
X12 Syntax:
P1112
If either INS11 or INS12 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when patient relationship to insured or birth sequence is needed by the UMO to determine the appropriate benefit/level of care. If not required by this implementation guide, do not send.
TR3 Notes:
This segment may be used to further identify the patient. Examples include identifying a patient in a multiple birth or differentiating dependents with the same name and date of birth.
TR3 Example:
INS✱N✱19~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: INS01 indicates status of the insured. A "Y" value indicates the insured is a subscriber: an "N" value indicates the insured is a dependent.
INDUSTRY NAME: Insured Indicator
CODE
DEFINITION
N
No
Required
2
1069
Individual Relationship Code
M 1
ID
2
Code indicating the relationship between two individuals or entities
Relationship to Insured Code
CODE
DEFINITION
01
Spouse
19
Child
G8
Other Relationship
Not Used
3
875
Maintenance Type Code
O 1
ID
3
Not Used
4
1203
Maintenance Reason Code
O 1
ID
2/3
Not Used
5
1216
Benefit Status Code
O 1
ID
1
Not Used
6
C052
Medicare Status Code
O 1
Not Used
7
1219
Consolidated Omnibus Budget Reconciliation Act (COBRA) Qualifying
O 1
ID
1/2
Not Used
8
584
Employment Status Code
O 1
ID
2
Not Used
9
1220
Student Status Code
O 1
ID
1
Not Used
10
1073
Yes/No Condition or Response Code
O 1
ID
1
Not Used
11
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Not Used
12
1251
Date Time Period
X 1
AN
1/35
Not Used
13
1165
Confidentiality Code
O 1
ID
1
Not Used
14
19
City Name
O 1
AN
2/30
Not Used
15
156
State or Province Code
O 1
ID
2
Not Used
16
26
Country Code
O 1
ID
2/3
Situational
17
1470
Number
O 1
N
1/9
A generic number
SEMANTIC: INS17 is the number assigned to each family member born with the same birth date. This number identifies birth sequence for multiple births allowing proper tracking and response of benefits for each dependent (i.e., twins, triplets, etc.).
SITUATIONAL RULE: Required when the dependent is a child from a multiple birth. If not required by this implementation guide, do not send.
INDUSTRY NAME: Birth Sequence Number

HL - PATIENT EVENT 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:
Loop 2000E to provide information on the patient event associated with this health care services review.
TR3 Example:
HL✱5✱4✱EV✱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.
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
EV
Event
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.
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.

TRN*1 - PATIENT EVENT TRACE NUMBER

X12 Name:
Trace
X12 Purpose:
To uniquely identify a transaction to an application
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
2
Situational Rule:
Required when the requester needs to assign a unique trace number to the patient event request. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
TR3 Notes:
  1. This enables the requester to
    • uniquely identify this patient event request
    • trace the request
    • match the response to the request
    • reference this request in any associated attachments containing additional patient information related to this patient event request.
  2. If the transaction is routed through a clearinghouse, the clearinghouse may add their own TRN segment. If the transaction passes through multiple clearinghouses, and the second clearinghouse needs to assign their own TRN segment, they must replace the TRN from the first clearinghouse and retain it to be returned in the 278 response. If the second clearinghouse does not need to assign a TRN segment, they should pass all received TRN segments.
  3. Each trace number provided in the TRN segment at this level on the request must be returned by the UMO in the TRN segment at the corresponding level of the response.
TR3 Example:
TRN✱1✱2001042801✱9012345678✱CARDIOLOGY~
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/80
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: Patient Event Trace Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Required
3
509
Originating Company Identifier
O 1
AN
10
A unique identifier designating the company initiating the funds transfer instructions, business transaction or assigning tracking reference identification.
SEMANTIC: TRN03 identifies an organization.
INDUSTRY NAME: Trace Assigning Entity Identifier
  1. Use this element to identify the organization that assigned this trace number. TRN03 must be completed to aid requesters and clearinghouses in identifying their TRN in the 278 response.
  2. The first position must be either a "1" if an EIN is used, a "3" if a DUNS is used, or a "9" if a user assigned identifier is used.
Situational
4
127
Reference Identification
O 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: TRN04 identifies a further subdivision within the organization.
SITUATIONAL RULE: Required when a specific division or group of the company identified in the previous data element (TRN03) is needed by the requester to further identify a specific component of the entity. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
INDUSTRY NAME: Trace Assigning Entity Additional Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.

UM - HEALTH CARE SERVICES REVIEW INFORMATION

X12 Name:
Health Care Services Review Information
X12 Purpose:
To specify health care services review information
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
This segment identifies the type of health care services review request.
TR3 Example:
UM✱SC✱I✱3✱✱✱✱✱✱Y~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1525
Request Category Code
M 1
ID
1/2
Code indicating a type of request
CODE
DEFINITION
AR
Admission Review
Required if requesting an admission to a facility.
HS
Health Services Review
Required if requesting a review of services related to an episode of care.
IN
Individual
Required when BHT06 is equal to "RU".
SC
Specialty Care Review
Required if requesting a referral to a specialty provider.
Required
2
1322
Certification Type Code
O 1
ID
1
Code indicating the type of certification
CODE
DEFINITION
1
Appeal - Immediate
Use this value to identify appeals of review decisions where the service required was emergency or urgent.
2
Appeal - Standard
Use this value to identify appeals of review decisions where the service required was not emergency or urgent.
3
Cancel
4
Extension
Use this when requesting additional service units and/or the duration of time for a prior approved service.
I
Initial
N
Reconsideration
R
Renewal
Various services, such as physical therapy, spinal manipulation, and allergy treatment, have both a delivery pattern and a time span of authorization. Many UMOs place time limits - as in will not authorize anything for more than 30 days at a time. For example, blanket authorization for allergy treatments as required for 30 days. At the end of the 30 days, the provider must request to renew the certification - not extend it - because the UMO authorizes for 30 day intervals, one interval at a time.
S
Revised
Use if the requester is changing the specifics of a previously submitted request for which services have not been rendered.
Situational
3
1271
Industry Code
O 1
AN
1/30
Code indicating a code from a specific industry code list
SEMANTIC: UM03 is the Service Type (Code Source 958).
SITUATIONAL RULE: Required when Loop 2000F is not valued. If not required by this implementation guide, may be provided at sender's discretion but cannot be required by the receiver.
INDUSTRY NAME: Service Type Code
Situational
4
C023
Health Care Service Location Information
O 1
To provide information that identifies the place of service or the type of bill related to the location at which a health care service was rendered
X12 COMPOSITE SEMANTIC NOTES:
  1. C023-01 does not contain the last position of the Uniform Bill Type Code (the Claim Frequency Code).
  2. C023-02 qualifies C023-01.
SITUATIONAL RULE: Required when UM04 is not valued at 2000F. If not required by this implementation guide, do not send.
Value at 2000F, Service Level, overrides the patient event for that service only.
Required
4-1
1331
Facility Code Value
M 1
AN
1/3
Code identifying where services were, or may be, performed; the National Uniform Billing Committee (NUBC) Facility Type Code for Institutional Services or the Place of Service Codes for Professional or Dental Services.
INDUSTRY NAME: Facility Type Code
Use to indicate a facility code value from the code source referenced in UM04-02.
Required
4-2
1332
Facility Code Qualifier
M 1
ID
1/2
Code identifying the type of facility referenced
CODE
DEFINITION
A
Uniform Billing Claim Form Bill Type
CODE SOURCE: 236: Uniform Billing Claim Form Bill Type
B
Place of Service Codes for Professional or Dental Services
CODE SOURCE: 237: Place of Service Codes for Professional Claims
Not Used
4-3
1325
Claim Frequency Type Code
O 1
ID
1
Situational
5
C024
Related Causes Information
O 1
To identify one or more related causes and associated state or country information
X12 COMPOSITE COMMENTS: C024-04 and C024-05 apply only to auto accidents when C024-01, C024-02, or C024-03 is equal to "AA".
SITUATIONAL RULE: Required when the patient's condition is accident or employment related. If not required by this implementation guide, do not send.
Required
5-1
1362
Related-Causes Code
M 1
ID
2/3
Code identifying an accompanying cause of an illness, injury or an accident
INDUSTRY NAME: Related Causes Code
CODE
DEFINITION
AA
Auto Accident
EM
Employment
OA
Other Accident
Situational
5-2
1362
Related-Causes Code
O 1
ID
2/3
Code identifying an accompanying cause of an illness, injury or an accident
SITUATIONAL RULE: Required when there is greater than 1 related cause for this certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Related Causes Code
CODE
DEFINITION
EM
Employment
OA
Other Accident
Not Used
5-3
1362
Related-Causes Code
O 1
ID
2/3
Situational
5-4
156
State or Province Code
O 1
ID
2
Code (Standard State/Province) as defined by appropriate government agency
SITUATIONAL RULE: Required when UM05-01 = "AA" and the accident occurred out of the service provider's state. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
CODE SOURCE 22: States and Provinces
Situational
5-5
26
Country Code
O 1
ID
2/3
Code identifying the country
SITUATIONAL RULE: Required when the automobile accident occurred out of the United States to identify the country in which the accident occurred. If not required by this implementation guide, do not send.
CODE SOURCE 5: Countries, Currencies and Funds
Situational
6
1338
Level of Service Code
O 1
ID
1/3
Code specifying the level of service rendered
SITUATIONAL RULE: Required when UM02=1 or if the patient event requires a level of service for care other than routine. If not required by this implementation guide, do not send.
CODE
DEFINITION
03
Emergency
E
Elective
U
Urgent
Situational
7
1213
Current Health Condition Code
O 1
ID
1
Code indicating current health condition of the individual
SITUATIONAL RULE: Required when the patient's condition, as expressed by the codes in this data element, is a factor in the provider's determination of services to be performed that are not typically requested for the patient's diagnosis and proposed treatment. If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Acute
2
Stable
3
Chronic
4
Systemic
5
Localized
6
Mild Disease
7
Normal, Healthy
8
Severe Systemic disease
9
Severe Systemic Disease that is a Constant Threat to Life
E
Excellent
F
Fair
G
Good
P
Poor
Situational
8
923
Prognosis Code
O 1
ID
1
Code indicating physician's prognosis for the patient
SITUATIONAL RULE: Required when the patient's prognosis, as expressed by the codes in this data element, is a factor in the provider's determination of services to be performed that are not typically requested for the patient's diagnosis and proposed treatment. If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Poor
2
Guarded
3
Fair
4
Good
5
Very Good
6
Excellent
7
Less than 6 Months to Live
8
Terminal
Situational
9
1363
Release of Information Code
O 1
ID
1
Code indicating whether the provider has on file a signed statement by the patient authorizing the release of medical data to other organizations
SITUATIONAL RULE: Required when applicable legislation requires that a signature be collected and reported on this Health Care Services Review. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
The Release of Information response is limited to the information carried in this service review.
CODE
DEFINITION
M
The Provider has Limited or Restricted Ability to Release Data Related to a Claim
For professional service, this value is only used when state or federal laws supersede the HIPAA privacy rule by requiring that the provider collect a signature and the patient is either not present or physically unable to sign at the time the provider submits the request.
Y
Yes, Provider has a Signed Statement Permitting Release of Medical Billing Data Related to a Claim
Situational
10
1514
Delay Reason Code
O 1
ID
1/2
Code indicating the reason why a request was delayed
SITUATIONAL RULE: Required when the request is not submitted within the normal timeframe of the UMO. If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Proof of Eligibility Unknown or Unavailable
2
Litigation
3
Authorization Delays
4
Delay in Certifying Provider
7
Third Party Processing Delay
8
Delay in Eligibility Determination
10
Administration Delay in the Prior Approval Process
11
Other
15
Natural Disaster
16
Lack of Information
17
No response to initial request

REF*BB - PREVIOUS REVIEW AUTHORIZATION NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when submitting an additional health care services review request associated with a request already processed by the UMO. If not required by this implementation guide, do not send.
TR3 Notes:
This is the authorization number assigned by the UMO to the original service review outcome associated with this service review. This is not the trace number assigned by the requester.
TR3 Example:
REF✱BB✱A123~
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
BB
Authorization Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Previous Review Authorization Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*NT - PREVIOUS REVIEW ADMINISTRATIVE REFERENCE NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when submitting a follow-up to a previous health care services review request for which the UMO has returned a response that contained an administrative reference number in the REF segment where REF01 = NT and did not return a certification number in HCR02. If not required by this implementation guide, do not send.
TR3 Example:
REF✱NT✱123Z~
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
NT
Administrator's Reference Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Previous Administrative Reference Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

DTP*439 - ACCIDENT DATE

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

DTP*484 - LAST MENSTRUAL PERIOD DATE

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

DTP*ABC - ESTIMATED BIRTH DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the certification is related to the estimated date of delivery. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱ABC✱D8✱20110930~
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
ABC
Estimated Date of Birth
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Estimated Birth Date

DTP*431 - ONSET OF CURRENT SYMPTOMS OR ILLNESS DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the date of onset of the patient's condition is different from the diagnosis date, and not accident or pregnancy related. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱431✱D8✱20110108~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
431
Onset of Current Symptoms or Illness
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Onset Date

DTP*AAH - EVENT DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the proposed or actual date or range of dates of this patient event are known and UM01 does not equal AR. If not required by this implementation guide, do not send.
TR3 Notes:
If UM01 = AR use Admit Date.
TR3 Example:
DTP✱AAH✱D8✱20110930~
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
AAH
Event
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
DT
Date and Time Expressed in Format CCYYMMDDHHMM
DTS
Range of Date and Time Expressed in Format CCYYMMDDHHMMSS-CCYYMMDDHHMMSS
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: Proposed or Actual Event Date

DTP*435 - ADMISSION DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when requesting an admission review (UM01 = "AR") to identify the proposed or actual date of admission. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱435✱D8✱20110930~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
435
Admission
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
RD8
Range of Dates Expressed in Format CCYYMMDD-CCYYMMDD
Use this for the range of dates when admission can occur.
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: Proposed or Actual Admission Date

DTP*096 - DISCHARGE DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when requesting an admission review (UM01 = "AR") and the proposed or actual date of discharge from a facility is known. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱096✱D8✱20110930~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
096
Discharge
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Proposed or Actual Discharge Date

HI - PATIENT DIAGNOSIS

X12 Name:
Health Care Information Codes
X12 Purpose:
To supply information related to the delivery of health care
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when known by the requester to convey diagnosis information. If not required by this implementation guide, do not send.
TR3 Notes:
Do not transmit the decimal points in the diagnosis codes. The decimal point is assumed.
TR3 Example:
HI✱ABF:I213:D8:20131209~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
C022
Health Care Code Information
M 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported when C022-02 is a Diagnosis Code and range of diagnosis codes were NOT given in C022-08.
Required
1-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
INDUSTRY NAME: Diagnosis Type Code
CODE
DEFINITION
AAA
SNOMED, Systematized Nomenclature of Medicine
CODE SOURCE: 662: SNOMED, Systematized Nomenclature of Medicine
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
ABJ
International Classification of Diseases Clinical Modification (ICD-10-CM) Admitting Diagnosis
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
ABK
International Classification of Diseases Clinical Modification (ICD-10-CM) Principal Diagnosis
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
APR
International Classification of Diseases Clinical Modification (ICD-10-CM) Patient's Reason for Visit
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
BF
International Classification of Diseases Clinical Modification (ICD-9-CM) Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
BJ
International Classification of Diseases Clinical Modification (ICD-9-CM) Admitting Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
BK
International Classification of Diseases Clinical Modification (ICD-9-CM) Principal Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
DR
Diagnosis Related Group (DRG)
CODE SOURCE: 229: Diagnosis Related Group Number (DRG)
PR
International Classification of Diseases Clinical Modification (ICD-9-CM) Patient's Reason for Visit
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
Required
1-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Diagnosis Code
Situational
1-3
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Code indicating the date format, time format, or date and time format
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
1-4
1251
Date Time Period
X 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Diagnosis Date
Not Used
1-5
782
Monetary Amount
O 1
R
1/18
Not Used
1-6
380
Quantity
O 1
R
1/15
Not Used
1-7
799
Version Identifier
O 1
AN
1/30
Not Used
1-8
1271
Industry Code
X 1
AN
1/30
Not Used
1-9
1271
Industry Code
X 1
AN
1/30
Situational
2
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported when C022-02 is a Diagnosis Code and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when there are additional diagnoses to communicate. If not required by this implementation guide, do not send.
Required
2-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
INDUSTRY NAME: Diagnosis Type Code
CODE
DEFINITION
AAA
SNOMED, Systematized Nomenclature of Medicine
CODE SOURCE: 662: SNOMED, Systematized Nomenclature of Medicine
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
ABJ
International Classification of Diseases Clinical Modification (ICD-10-CM) Admitting Diagnosis
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
APR
International Classification of Diseases Clinical Modification (ICD-10-CM) Patient's Reason for Visit
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
BF
International Classification of Diseases Clinical Modification (ICD-9-CM) Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
BJ
International Classification of Diseases Clinical Modification (ICD-9-CM) Admitting Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
DR
Diagnosis Related Group (DRG)
CODE SOURCE: 229: Diagnosis Related Group Number (DRG)
PR
International Classification of Diseases Clinical Modification (ICD-9-CM) Patient's Reason for Visit
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
Required
2-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Diagnosis Code
Situational
2-3
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Code indicating the date format, time format, or date and time format
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
2-4
1251
Date Time Period
X 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Diagnosis Date
Not Used
2-5
782
Monetary Amount
O 1
R
1/18
Not Used
2-6
380
Quantity
O 1
R
1/15
Not Used
2-7
799
Version Identifier
O 1
AN
1/30
Not Used
2-8
1271
Industry Code
X 1
AN
1/30
Not Used
2-9
1271
Industry Code
X 1
AN
1/30
Situational
3
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported when C022-02 is a Diagnosis Code and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when there are additional diagnoses to communicate. If not required by this implementation guide, do not send.
Required
3-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
INDUSTRY NAME: Diagnosis Type Code
CODE
DEFINITION
AAA
SNOMED, Systematized Nomenclature of Medicine
CODE SOURCE: 662: SNOMED, Systematized Nomenclature of Medicine
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
APR
International Classification of Diseases Clinical Modification (ICD-10-CM) Patient's Reason for Visit
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
BF
International Classification of Diseases Clinical Modification (ICD-9-CM) Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
DR
Diagnosis Related Group (DRG)
CODE SOURCE: 229: Diagnosis Related Group Number (DRG)
PR
International Classification of Diseases Clinical Modification (ICD-9-CM) Patient's Reason for Visit
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
Required
3-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Diagnosis Code
Situational
3-3
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Code indicating the date format, time format, or date and time format
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
3-4
1251
Date Time Period
X 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Diagnosis Date
Not Used
3-5
782
Monetary Amount
O 1
R
1/18
Not Used
3-6
380
Quantity
O 1
R
1/15
Not Used
3-7
799
Version Identifier
O 1
AN
1/30
Not Used
3-8
1271
Industry Code
X 1
AN
1/30
Not Used
3-9
1271
Industry Code
X 1
AN
1/30
Situational
4
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported when C022-02 is a Diagnosis Code and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when there are additional diagnoses to communicate. If not required by this implementation guide, do not send.
Required
4-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
INDUSTRY NAME: Diagnosis Type Code
CODE
DEFINITION
AAA
SNOMED, Systematized Nomenclature of Medicine
CODE SOURCE: 662: SNOMED, Systematized Nomenclature of Medicine
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
APR
International Classification of Diseases Clinical Modification (ICD-10-CM) Patient's Reason for Visit
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
BF
International Classification of Diseases Clinical Modification (ICD-9-CM) Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
DR
Diagnosis Related Group (DRG)
CODE SOURCE: 229: Diagnosis Related Group Number (DRG)
PR
International Classification of Diseases Clinical Modification (ICD-9-CM) Patient's Reason for Visit
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
Required
4-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Diagnosis Code
Situational
4-3
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Code indicating the date format, time format, or date and time format
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
4-4
1251
Date Time Period
X 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Diagnosis Date
Not Used
4-5
782
Monetary Amount
O 1
R
1/18
Not Used
4-6
380
Quantity
O 1
R
1/15
Not Used
4-7
799
Version Identifier
O 1
AN
1/30
Not Used
4-8
1271
Industry Code
X 1
AN
1/30
Not Used
4-9
1271
Industry Code
X 1
AN
1/30
Situational
5
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported when C022-02 is a Diagnosis Code and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when there are additional diagnoses to communicate. If not required by this implementation guide, do not send.
Required
5-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
INDUSTRY NAME: Diagnosis Type Code
CODE
DEFINITION
AAA
SNOMED, Systematized Nomenclature of Medicine
CODE SOURCE: 662: SNOMED, Systematized Nomenclature of Medicine
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
APR
International Classification of Diseases Clinical Modification (ICD-10-CM) Patient's Reason for Visit
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
BF
International Classification of Diseases Clinical Modification (ICD-9-CM) Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
DR
Diagnosis Related Group (DRG)
CODE SOURCE: 229: Diagnosis Related Group Number (DRG)
PR
International Classification of Diseases Clinical Modification (ICD-9-CM) Patient's Reason for Visit
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
Required
5-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Diagnosis Code
Situational
5-3
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Code indicating the date format, time format, or date and time format
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
5-4
1251
Date Time Period
X 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Diagnosis Date
Not Used
5-5
782
Monetary Amount
O 1
R
1/18
Not Used
5-6
380
Quantity
O 1
R
1/15
Not Used
5-7
799
Version Identifier
O 1
AN
1/30
Not Used
5-8
1271
Industry Code
X 1
AN
1/30
Not Used
5-9
1271
Industry Code
X 1
AN
1/30
Situational
6
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported when C022-02 is a Diagnosis Code and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when there are additional diagnoses to communicate. If not required by this implementation guide, do not send.
Required
6-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
INDUSTRY NAME: Diagnosis Type Code
CODE
DEFINITION
AAA
SNOMED, Systematized Nomenclature of Medicine
CODE SOURCE: 662: SNOMED, Systematized Nomenclature of Medicine
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
APR
International Classification of Diseases Clinical Modification (ICD-10-CM) Patient's Reason for Visit
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
BF
International Classification of Diseases Clinical Modification (ICD-9-CM) Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
DR
Diagnosis Related Group (DRG)
CODE SOURCE: 229: Diagnosis Related Group Number (DRG)
PR
International Classification of Diseases Clinical Modification (ICD-9-CM) Patient's Reason for Visit
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
Required
6-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Diagnosis Code
Situational
6-3
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Code indicating the date format, time format, or date and time format
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
6-4
1251
Date Time Period
X 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Diagnosis Date
Not Used
6-5
782
Monetary Amount
O 1
R
1/18
Not Used
6-6
380
Quantity
O 1
R
1/15
Not Used
6-7
799
Version Identifier
O 1
AN
1/30
Not Used
6-8
1271
Industry Code
X 1
AN
1/30
Not Used
6-9
1271
Industry Code
X 1
AN
1/30
Situational
7
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported when C022-02 is a Diagnosis Code and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when there are additional diagnoses to communicate. If not required by this implementation guide, do not send.
Required
7-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
INDUSTRY NAME: Diagnosis Type Code
CODE
DEFINITION
AAA
SNOMED, Systematized Nomenclature of Medicine
CODE SOURCE: 662: SNOMED, Systematized Nomenclature of Medicine
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
APR
International Classification of Diseases Clinical Modification (ICD-10-CM) Patient's Reason for Visit
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
BF
International Classification of Diseases Clinical Modification (ICD-9-CM) Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
DR
Diagnosis Related Group (DRG)
CODE SOURCE: 229: Diagnosis Related Group Number (DRG)
PR
International Classification of Diseases Clinical Modification (ICD-9-CM) Patient's Reason for Visit
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
Required
7-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Diagnosis Code
Situational
7-3
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Code indicating the date format, time format, or date and time format
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
7-4
1251
Date Time Period
X 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Diagnosis Date
Not Used
7-5
782
Monetary Amount
O 1
R
1/18
Not Used
7-6
380
Quantity
O 1
R
1/15
Not Used
7-7
799
Version Identifier
O 1
AN
1/30
Not Used
7-8
1271
Industry Code
X 1
AN
1/30
Not Used
7-9
1271
Industry Code
X 1
AN
1/30
Situational
8
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported when C022-02 is a Diagnosis Code and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when there are additional diagnoses to communicate. If not required by this implementation guide, do not send.
Required
8-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
INDUSTRY NAME: Diagnosis Type Code
CODE
DEFINITION
AAA
SNOMED, Systematized Nomenclature of Medicine
CODE SOURCE: 662: SNOMED, Systematized Nomenclature of Medicine
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
APR
International Classification of Diseases Clinical Modification (ICD-10-CM) Patient's Reason for Visit
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
BF
International Classification of Diseases Clinical Modification (ICD-9-CM) Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
DR
Diagnosis Related Group (DRG)
CODE SOURCE: 229: Diagnosis Related Group Number (DRG)
PR
International Classification of Diseases Clinical Modification (ICD-9-CM) Patient's Reason for Visit
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
Required
8-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Diagnosis Code
Situational
8-3
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Code indicating the date format, time format, or date and time format
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
8-4
1251
Date Time Period
X 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Diagnosis Date
Not Used
8-5
782
Monetary Amount
O 1
R
1/18
Not Used
8-6
380
Quantity
O 1
R
1/15
Not Used
8-7
799
Version Identifier
O 1
AN
1/30
Not Used
8-8
1271
Industry Code
X 1
AN
1/30
Not Used
8-9
1271
Industry Code
X 1
AN
1/30
Situational
9
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported when C022-02 is a Diagnosis Code and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when there are additional diagnoses to communicate. If not required by this implementation guide, do not send.
Required
9-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
INDUSTRY NAME: Diagnosis Type Code
CODE
DEFINITION
AAA
SNOMED, Systematized Nomenclature of Medicine
CODE SOURCE: 662: SNOMED, Systematized Nomenclature of Medicine
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
APR
International Classification of Diseases Clinical Modification (ICD-10-CM) Patient's Reason for Visit
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
BF
International Classification of Diseases Clinical Modification (ICD-9-CM) Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
DR
Diagnosis Related Group (DRG)
CODE SOURCE: 229: Diagnosis Related Group Number (DRG)
PR
International Classification of Diseases Clinical Modification (ICD-9-CM) Patient's Reason for Visit
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
Required
9-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Diagnosis Code
Situational
9-3
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Code indicating the date format, time format, or date and time format
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
9-4
1251
Date Time Period
X 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Diagnosis Date
Not Used
9-5
782
Monetary Amount
O 1
R
1/18
Not Used
9-6
380
Quantity
O 1
R
1/15
Not Used
9-7
799
Version Identifier
O 1
AN
1/30
Not Used
9-8
1271
Industry Code
X 1
AN
1/30
Not Used
9-9
1271
Industry Code
X 1
AN
1/30
Situational
10
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported when C022-02 is a Diagnosis Code and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when there are additional diagnoses to communicate. If not required by this implementation guide, do not send.
Required
10-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
INDUSTRY NAME: Diagnosis Type Code
CODE
DEFINITION
AAA
SNOMED, Systematized Nomenclature of Medicine
CODE SOURCE: 662: SNOMED, Systematized Nomenclature of Medicine
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
APR
International Classification of Diseases Clinical Modification (ICD-10-CM) Patient's Reason for Visit
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
BF
International Classification of Diseases Clinical Modification (ICD-9-CM) Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
DR
Diagnosis Related Group (DRG)
CODE SOURCE: 229: Diagnosis Related Group Number (DRG)
PR
International Classification of Diseases Clinical Modification (ICD-9-CM) Patient's Reason for Visit
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
Required
10-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Diagnosis Code
Situational
10-3
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Code indicating the date format, time format, or date and time format
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
10-4
1251
Date Time Period
X 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Diagnosis Date
Not Used
10-5
782
Monetary Amount
O 1
R
1/18
Not Used
10-6
380
Quantity
O 1
R
1/15
Not Used
10-7
799
Version Identifier
O 1
AN
1/30
Not Used
10-8
1271
Industry Code
X 1
AN
1/30
Not Used
10-9
1271
Industry Code
X 1
AN
1/30
Situational
11
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported when C022-02 is a Diagnosis Code and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when there are additional diagnoses to communicate. If not required by this implementation guide, do not send.
Required
11-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
INDUSTRY NAME: Diagnosis Type Code
CODE
DEFINITION
AAA
SNOMED, Systematized Nomenclature of Medicine
CODE SOURCE: 662: SNOMED, Systematized Nomenclature of Medicine
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
APR
International Classification of Diseases Clinical Modification (ICD-10-CM) Patient's Reason for Visit
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
BF
International Classification of Diseases Clinical Modification (ICD-9-CM) Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
DR
Diagnosis Related Group (DRG)
CODE SOURCE: 229: Diagnosis Related Group Number (DRG)
PR
International Classification of Diseases Clinical Modification (ICD-9-CM) Patient's Reason for Visit
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
Required
11-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Diagnosis Code
Situational
11-3
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Code indicating the date format, time format, or date and time format
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
11-4
1251
Date Time Period
X 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Diagnosis Date
Not Used
11-5
782
Monetary Amount
O 1
R
1/18
Not Used
11-6
380
Quantity
O 1
R
1/15
Not Used
11-7
799
Version Identifier
O 1
AN
1/30
Not Used
11-8
1271
Industry Code
X 1
AN
1/30
Not Used
11-9
1271
Industry Code
X 1
AN
1/30
Situational
12
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported when C022-02 is a Diagnosis Code and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when there are additional diagnoses to communicate. If not required by this implementation guide, do not send.
Required
12-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
INDUSTRY NAME: Diagnosis Type Code
CODE
DEFINITION
AAA
SNOMED, Systematized Nomenclature of Medicine
CODE SOURCE: 662: SNOMED, Systematized Nomenclature of Medicine
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
APR
International Classification of Diseases Clinical Modification (ICD-10-CM) Patient's Reason for Visit
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
BF
International Classification of Diseases Clinical Modification (ICD-9-CM) Diagnosis
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
DR
Diagnosis Related Group (DRG)
CODE SOURCE: 229: Diagnosis Related Group Number (DRG)
PR
International Classification of Diseases Clinical Modification (ICD-9-CM) Patient's Reason for Visit
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
Required
12-2
1271
Industry Code
M 1
AN
1/30
Code indicating a code from a specific industry code list
INDUSTRY NAME: Diagnosis Code
Situational
12-3
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Code indicating the date format, time format, or date and time format
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
12-4
1251
Date Time Period
X 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Diagnosis Date
Not Used
12-5
782
Monetary Amount
O 1
R
1/18
Not Used
12-6
380
Quantity
O 1
R
1/15
Not Used
12-7
799
Version Identifier
O 1
AN
1/30
Not Used
12-8
1271
Industry Code
X 1
AN
1/30
Not Used
12-9
1271
Industry Code
X 1
AN
1/30

HSD - HEALTH CARE SERVICES DELIVERY

X12 Name:
Health Care Services Delivery
X12 Purpose:
To specify the delivery pattern of health care services
X12 Syntax:
  1. P0102
    If either HSD01 or HSD02 is present, then the other is required.
  2. C0605
    If HSD06 is present, then HSD05 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when requesting services that have a specific pattern of delivery or usage. If not required by this implementation guide, do not send.
TR3 Notes:
An explanation of the uses of this segment follows.

HSD01 qualifies HSD02: If the value in HSD02=1 and the value in HSD01=VS (Visits), this means "one visit".
Between HSD02 and HSD03 verbally insert a "per every".
HSD03 qualifies HSD04: If the value in HSD04=3 and the value in HSD03=DA (Day), this means "three days". Between HSD04 and HSD05 verbally insert a "for". HSD05 qualifies HSD06: If the value in HSD06=21 and the value in HSD05=7 (Days), this means "21 days".
The total message reads:
HSD*VS*1*DA*3*7*21~ = "One visit per every three days for 21 days".

Another similar data string of HSD*VS*2*DA*4*7*20~ = "Two visits per every four days for 20 days".

An alternate way to use HSD is to employ HSD07 and/or HSD08. A data string of HSD*VS*1*****SX*D~ means "1 visit on Wednesday and Thursday morning".
TR3 Example:
  1. HSD✱VS✱1✱DA✱1✱7✱10~ (This indicates "1 visit every (per) 1 day (daily) for 10 days".)
  2. HSD✱VS✱1✱DA✱✱✱✱W~ (This indicates "1 visit per day whenever necessary".)
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Situational
1
673
Quantity Qualifier
X 1
ID
2
Code specifying the type of quantity
SEGMENT SYNTAX: P0102
SITUATIONAL RULE: Required when HSD02 is valued to qualify the type of service count for this patient event. If not required by this implementation guide, do not send.
CODE
DEFINITION
DY
Days
FL
Units
HS
Hours
MN
Month
VS
Visits
Situational
2
380
Quantity
X 1
R
1/15
Numeric value of quantity
SEGMENT SYNTAX: P0102
SITUATIONAL RULE: Required when HSD01 is valued to indicate the service quantity. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Unit Count
If this is a request for an extension to an existing certification (UM02 = 4), then HSD02 represents the number of visits by which the certification is extended. If this is a request to revise an existing certification (UM02 = S), then HSD02 represents the new total.
Situational
3
355
Unit or Basis for Measurement Code
O 1
ID
2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
SITUATIONAL RULE: Required when HSD04 is valued to qualify the timeframe in which the quantity of services (HSD02) will be rendered. If not required by this implementation guide, do not send.
CODE
DEFINITION
DA
Days
MO
Months
WK
Week
Situational
4
1167
Sample Selection Modulus
O 1
R
1/6
To specify the sampling frequency in terms of a modulus of the Unit of Measure, e.g., every fifth bag, every 1.5 minutes
SITUATIONAL RULE: Required when needed to indicate sampling frequency for this service. If not required by this implementation guide, do not send.
Situational
5
615
Time Period Qualifier
X 1
ID
1/2
Code defining periods
SEGMENT SYNTAX: C0605
SITUATIONAL RULE: Required when patient events must be rendered within a specific timeframe. If not required by this implementation guide, do not send.
CODE
DEFINITION
6
Hour
7
Day
21
Years
26
Episode
27
Visit
34
Month
35
Week
Situational
6
616
Number of Periods
O 1
N
1/3
Total number of periods
SEGMENT SYNTAX: C0605
SITUATIONAL RULE: Required when patient events must be rendered within a specific timeframe. If not required by this implementation guide, do not send.
INDUSTRY NAME: Period Count
Situational
7
678
Ship/Delivery or Calendar Pattern Code
O 1
ID
1/2
Code which specifies the routine shipments, deliveries, or calendar pattern
SITUATIONAL RULE: Required when the patient event must be rendered within a specific calendar delivery pattern. If not required by this implementation guide, do not send.
INDUSTRY NAME: Delivery Frequency Code
CODE
DEFINITION
1
1st Week of the Month
2
2nd Week of the Month
3
3rd Week of the Month
4
4th Week of the Month
5
5th Week of the Month
6
1st & 3rd Weeks of the Month
7
2nd & 4th Weeks of the Month
8
1st Working Day of Period
9
Last Working Day of Period
A
Monday through Friday
B
Monday through Saturday
C
Monday through Sunday
D
Monday
E
Tuesday
F
Wednesday
G
Thursday
H
Friday
J
Saturday
K
Sunday
L
Monday through Thursday
M
Immediately
N
As Directed
O
Daily Mon. through Fri.
P
1/2 Mon. & 1/2 Thurs.
Q
1/2 Tues. & 1/2 Thurs.
R
1/2 Wed. & 1/2 Fri.
S
Once Anytime Mon. through Fri.
SA
Sunday, Monday, Thursday, Friday, Saturday
SB
Tuesday through Saturday
SC
Sunday, Wednesday, Thursday, Friday, Saturday
SD
Monday, Wednesday, Thursday, Friday, Saturday
SG
Tuesday through Friday
SL
Monday, Tuesday and Thursday
SP
Monday, Tuesday and Friday
SX
Wednesday and Thursday
SY
Monday, Wednesday and Thursday
SZ
Tuesday, Thursday and Friday
T
1/2 Tue. & 1/2 Fri.
U
1/2 Mon. & 1/2 Wed.
V
1/3 Mon., 1/3 Wed., 1/3 Fri.
W
Whenever Necessary
X
1/2 By Wed., Bal. By Fri.
Y
None (Also Used to Cancel or Override a Previous Pattern)
Situational
8
679
Ship/Delivery Pattern Time Code
O 1
ID
1
Code which specifies the time for routine shipments or deliveries
SITUATIONAL RULE: Required when a specific time delivery pattern for the services in this patient event must be identified. If not required by this implementation guide, do not send.
INDUSTRY NAME: Delivery Pattern Time Code
CODE
DEFINITION
A
1st Shift (Normal Working Hours)
B
2nd Shift
C
3rd Shift
D
A.M.
E
P.M.
F
As Directed
G
Any Shift
Y
None (Also Used to Cancel or Override a Previous Pattern)

CRC*07 - AMBULANCE CERTIFICATION INFORMATION

X12 Name:
Conditions Indicator
X12 Purpose:
To supply information on conditions
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when health care services review is requesting certification and to justify the reason for the request. If not required by this implementation guide, do not send.
TR3 Example:
CRC✱07✱Y✱01~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1136
Code Category
M 1
ID
2
Specifies the situation or category to which the code applies
SEMANTIC: CRC01 qualifies CRC03 through CRC07.
Condition Code Category
CODE
DEFINITION
07
Ambulance Certification
Required
2
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: CRC02 is a Certification Condition Code applies indicator. A "Y" value indicates the condition codes in CRC03 through CRC07 apply; an "N" value indicates the condition codes in CRC03 through CRC07 do not apply.
INDUSTRY NAME: Certification Condition Indicator
CODE
DEFINITION
N
No
Y
Yes
Required
3
1321
Condition Indicator
M 1
ID
2/3
Code indicating a condition
INDUSTRY NAME: Condition Code
CODE
DEFINITION
01
Patient was admitted to a hospital
02
Patient was bed confined before the ambulance service
03
Patient was bed confined after the ambulance service
04
Patient was moved by stretcher
05
Patient was unconscious or in shock
06
Patient was transported in an emergency situation
07
Patient had to be physically restrained
08
Patient had visible hemorrhaging
09
Ambulance service was medically necessary
41
Patient or Caregiver is Unable to Propel or Lift a Standard Weight Wheelchair
43
Patient Weight or Usage Needs Necessitate a Heavy Duty Wheelchair
5A
Treatment is rendered related to the terminal illness
60
Transportation Was To the Nearest Facility
9D
Lack of Appropriate Facility within Reasonable Distance to Treat Patient in the Event of Complications
Situational
4
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
01
Patient was admitted to a hospital
02
Patient was bed confined before the ambulance service
03
Patient was bed confined after the ambulance service
04
Patient was moved by stretcher
05
Patient was unconscious or in shock
06
Patient was transported in an emergency situation
07
Patient had to be physically restrained
08
Patient had visible hemorrhaging
09
Ambulance service was medically necessary
41
Patient or Caregiver is Unable to Propel or Lift a Standard Weight Wheelchair
43
Patient Weight or Usage Needs Necessitate a Heavy Duty Wheelchair
5A
Treatment is rendered related to the terminal illness
60
Transportation Was To the Nearest Facility
9D
Lack of Appropriate Facility within Reasonable Distance to Treat Patient in the Event of Complications
Situational
5
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
01
Patient was admitted to a hospital
02
Patient was bed confined before the ambulance service
03
Patient was bed confined after the ambulance service
04
Patient was moved by stretcher
05
Patient was unconscious or in shock
06
Patient was transported in an emergency situation
07
Patient had to be physically restrained
08
Patient had visible hemorrhaging
09
Ambulance service was medically necessary
41
Patient or Caregiver is Unable to Propel or Lift a Standard Weight Wheelchair
43
Patient Weight or Usage Needs Necessitate a Heavy Duty Wheelchair
5A
Treatment is rendered related to the terminal illness
60
Transportation Was To the Nearest Facility
9D
Lack of Appropriate Facility within Reasonable Distance to Treat Patient in the Event of Complications
Situational
6
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
01
Patient was admitted to a hospital
02
Patient was bed confined before the ambulance service
03
Patient was bed confined after the ambulance service
04
Patient was moved by stretcher
05
Patient was unconscious or in shock
06
Patient was transported in an emergency situation
07
Patient had to be physically restrained
08
Patient had visible hemorrhaging
09
Ambulance service was medically necessary
41
Patient or Caregiver is Unable to Propel or Lift a Standard Weight Wheelchair
43
Patient Weight or Usage Needs Necessitate a Heavy Duty Wheelchair
5A
Treatment is rendered related to the terminal illness
60
Transportation Was To the Nearest Facility
9D
Lack of Appropriate Facility within Reasonable Distance to Treat Patient in the Event of Complications
Situational
7
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
01
Patient was admitted to a hospital
02
Patient was bed confined before the ambulance service
03
Patient was bed confined after the ambulance service
04
Patient was moved by stretcher
05
Patient was unconscious or in shock
06
Patient was transported in an emergency situation
07
Patient had to be physically restrained
08
Patient had visible hemorrhaging
09
Ambulance service was medically necessary
41
Patient or Caregiver is Unable to Propel or Lift a Standard Weight Wheelchair
43
Patient Weight or Usage Needs Necessitate a Heavy Duty Wheelchair
5A
Treatment is rendered related to the terminal illness
60
Transportation Was To the Nearest Facility
9D
Lack of Appropriate Facility within Reasonable Distance to Treat Patient in the Event of Complications

CRC*08 - CHIROPRACTIC CERTIFICATION INFORMATION

X12 Name:
Conditions Indicator
X12 Purpose:
To supply information on conditions
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when health care services review is requesting certification and to justify the reason for the request. If not required by this implementation guide, do not send.
TR3 Example:
CRC✱08✱Y✱14~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1136
Code Category
M 1
ID
2
Specifies the situation or category to which the code applies
SEMANTIC: CRC01 qualifies CRC03 through CRC07.
Condition Code Category
CODE
DEFINITION
08
Chiropractic Certification
Required
2
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: CRC02 is a Certification Condition Code applies indicator. A "Y" value indicates the condition codes in CRC03 through CRC07 apply; an "N" value indicates the condition codes in CRC03 through CRC07 do not apply.
INDUSTRY NAME: Certification Condition Indicator
CODE
DEFINITION
N
No
Y
Yes
Required
3
1321
Condition Indicator
M 1
ID
2/3
Code indicating a condition
INDUSTRY NAME: Condition Code
CODE
DEFINITION
11
Ambulation is Impaired and Walking Aid is Used for Therapy or Mobility
12
Patient is confined to a bed or chair
14
Ambulation is Impaired and Walking Aid is Used for Mobility
24
Patient has an orthopedic impairment requiring traction equipment which prevents ambulation during period of use
25
Item has been prescribed as part of a planned regimen of treatment in patient home
27
Patient or a care-giver has been instructed in use of equipment
30
Without the equipment, the patient would require surgery
Situational
4
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
11
Ambulation is Impaired and Walking Aid is Used for Therapy or Mobility
12
Patient is confined to a bed or chair
14
Ambulation is Impaired and Walking Aid is Used for Mobility
24
Patient has an orthopedic impairment requiring traction equipment which prevents ambulation during period of use
25
Item has been prescribed as part of a planned regimen of treatment in patient home
27
Patient or a care-giver has been instructed in use of equipment
30
Without the equipment, the patient would require surgery
Situational
5
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
11
Ambulation is Impaired and Walking Aid is Used for Therapy or Mobility
12
Patient is confined to a bed or chair
14
Ambulation is Impaired and Walking Aid is Used for Mobility
24
Patient has an orthopedic impairment requiring traction equipment which prevents ambulation during period of use
25
Item has been prescribed as part of a planned regimen of treatment in patient home
27
Patient or a care-giver has been instructed in use of equipment
30
Without the equipment, the patient would require surgery
Situational
6
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
11
Ambulation is Impaired and Walking Aid is Used for Therapy or Mobility
12
Patient is confined to a bed or chair
14
Ambulation is Impaired and Walking Aid is Used for Mobility
24
Patient has an orthopedic impairment requiring traction equipment which prevents ambulation during period of use
25
Item has been prescribed as part of a planned regimen of treatment in patient home
27
Patient or a care-giver has been instructed in use of equipment
30
Without the equipment, the patient would require surgery
Situational
7
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
11
Ambulation is Impaired and Walking Aid is Used for Therapy or Mobility
12
Patient is confined to a bed or chair
14
Ambulation is Impaired and Walking Aid is Used for Mobility
24
Patient has an orthopedic impairment requiring traction equipment which prevents ambulation during period of use
25
Item has been prescribed as part of a planned regimen of treatment in patient home
27
Patient or a care-giver has been instructed in use of equipment
30
Without the equipment, the patient would require surgery

CRC*09 - DURABLE MEDICAL EQUIPMENT INFORMATION

X12 Name:
Conditions Indicator
X12 Purpose:
To supply information on conditions
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when health care services review is requesting certification and to justify the reason for the request. If not required by this implementation guide, do not send.
TR3 Example:
CRC✱09✱Y✱29~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1136
Code Category
M 1
ID
2
Specifies the situation or category to which the code applies
SEMANTIC: CRC01 qualifies CRC03 through CRC07.
Condition Code Category
CODE
DEFINITION
09
Durable Medical Equipment Certification
Required
2
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: CRC02 is a Certification Condition Code applies indicator. A "Y" value indicates the condition codes in CRC03 through CRC07 apply; an "N" value indicates the condition codes in CRC03 through CRC07 do not apply.
INDUSTRY NAME: Certification Condition Indicator
CODE
DEFINITION
N
No
Y
Yes
Required
3
1321
Condition Indicator
M 1
ID
2/3
Code indicating a condition
INDUSTRY NAME: Condition Code
CODE
DEFINITION
01
Patient was admitted to a hospital
02
Patient was bed confined before the ambulance service
03
Patient was bed confined after the ambulance service
04
Patient was moved by stretcher
05
Patient was unconscious or in shock
06
Patient was transported in an emergency situation
07
Patient had to be physically restrained
08
Patient had visible hemorrhaging
09
Ambulance service was medically necessary
10
Patient is ambulatory
11
Ambulation is Impaired and Walking Aid is Used for Therapy or Mobility
12
Patient is confined to a bed or chair
13
Patient is Confined to a Room or an Area Without Bathroom Facilities
14
Ambulation is Impaired and Walking Aid is Used for Mobility
15
Patient Condition Requires Positioning of the Body or Attachments Which Would Not be Feasible With the Use of an Ordinary Bed
16
Patient needs a trapeze bar to sit up due to respiratory condition or change body positions for other medical reasons
17
Patient's Ability to Breathe is Severely Impaired
18
Patient condition requires frequent and/or immediate changes in body positions
19
Patient can operate controls
20
Siderails Are to be Attached to a Hospital Bed Owned by the Beneficiary
21
Patient owns equipment
22
Mattress or Siderails are Being Used with Prescribed Medically Necessary Hospital Bed Owned by the Beneficiary
23
Patient Needs Lift to Get In or Out of Bed or to Assist in Transfer from Bed to Wheelchair
24
Patient has an orthopedic impairment requiring traction equipment which prevents ambulation during period of use
25
Item has been prescribed as part of a planned regimen of treatment in patient home
26
Patient is highly susceptible to decubitus ulcers
27
Patient or a care-giver has been instructed in use of equipment
29
A 6-7 hour nocturnal study documents 30 episodes of apnea each lasting more than 10 seconds
30
Without the equipment, the patient would require surgery
31
Patient has had a total knee replacement
32
Patient has intractable lymphedema of the extremities
33
Patient is in a nursing home
35
This Feeding is the Only Form of Nutritional Intake for This Patient
37
Oxygen delivery equipment is stationary
38
Certification signed by the physician is on file at the supplier's office
40
Patient or Caregiver is Capable of Using the Equipment Without Technical or Professional Supervision
41
Patient or Caregiver is Unable to Propel or Lift a Standard Weight Wheelchair
42
Patient Requires Leg Elevation for Edema or Body Alignment
43
Patient Weight or Usage Needs Necessitate a Heavy Duty Wheelchair
44
Patient Requires Reclining Function of a Wheelchair
45
Patient is Unable to Operate a Wheelchair Manually
46
Patient or Caregiver Requires Side Transfer into Wheelchair, Commode or Other
58
Durable Medical Equipment (DME) Purchased New
59
Durable Medical Equipment (DME) Is Under Warranty
60
Transportation Was To the Nearest Facility
9D
Lack of Appropriate Facility within Reasonable Distance to Treat Patient in the Event of Complications
9H
Patient Requires Intensive IV Therapy
9J
Patient Requires Protective Isolation
9K
Patient Requires Frequent Monitoring
IH
Independent at Home
LB
Legally Blind
SL
Speech Limitations
Situational
4
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
01
Patient was admitted to a hospital
02
Patient was bed confined before the ambulance service
03
Patient was bed confined after the ambulance service
04
Patient was moved by stretcher
05
Patient was unconscious or in shock
06
Patient was transported in an emergency situation
07
Patient had to be physically restrained
08
Patient had visible hemorrhaging
09
Ambulance service was medically necessary
10
Patient is ambulatory
11
Ambulation is Impaired and Walking Aid is Used for Therapy or Mobility
12
Patient is confined to a bed or chair
13
Patient is Confined to a Room or an Area Without Bathroom Facilities
14
Ambulation is Impaired and Walking Aid is Used for Mobility
15
Patient Condition Requires Positioning of the Body or Attachments Which Would Not be Feasible With the Use of an Ordinary Bed
16
Patient needs a trapeze bar to sit up due to respiratory condition or change body positions for other medical reasons
17
Patient's Ability to Breathe is Severely Impaired
18
Patient condition requires frequent and/or immediate changes in body positions
19
Patient can operate controls
20
Siderails Are to be Attached to a Hospital Bed Owned by the Beneficiary
21
Patient owns equipment
22
Mattress or Siderails are Being Used with Prescribed Medically Necessary Hospital Bed Owned by the Beneficiary
23
Patient Needs Lift to Get In or Out of Bed or to Assist in Transfer from Bed to Wheelchair
24
Patient has an orthopedic impairment requiring traction equipment which prevents ambulation during period of use
25
Item has been prescribed as part of a planned regimen of treatment in patient home
26
Patient is highly susceptible to decubitus ulcers
27
Patient or a care-giver has been instructed in use of equipment
29
A 6-7 hour nocturnal study documents 30 episodes of apnea each lasting more than 10 seconds
30
Without the equipment, the patient would require surgery
31
Patient has had a total knee replacement
32
Patient has intractable lymphedema of the extremities
33
Patient is in a nursing home
35
This Feeding is the Only Form of Nutritional Intake for This Patient
37
Oxygen delivery equipment is stationary
38
Certification signed by the physician is on file at the supplier's office
40
Patient or Caregiver is Capable of Using the Equipment Without Technical or Professional Supervision
41
Patient or Caregiver is Unable to Propel or Lift a Standard Weight Wheelchair
42
Patient Requires Leg Elevation for Edema or Body Alignment
43
Patient Weight or Usage Needs Necessitate a Heavy Duty Wheelchair
44
Patient Requires Reclining Function of a Wheelchair
45
Patient is Unable to Operate a Wheelchair Manually
46
Patient or Caregiver Requires Side Transfer into Wheelchair, Commode or Other
58
Durable Medical Equipment (DME) Purchased New
59
Durable Medical Equipment (DME) Is Under Warranty
60
Transportation Was To the Nearest Facility
9D
Lack of Appropriate Facility within Reasonable Distance to Treat Patient in the Event of Complications
9H
Patient Requires Intensive IV Therapy
9J
Patient Requires Protective Isolation
9K
Patient Requires Frequent Monitoring
IH
Independent at Home
LB
Legally Blind
SL
Speech Limitations
Situational
5
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
01
Patient was admitted to a hospital
02
Patient was bed confined before the ambulance service
03
Patient was bed confined after the ambulance service
04
Patient was moved by stretcher
05
Patient was unconscious or in shock
06
Patient was transported in an emergency situation
07
Patient had to be physically restrained
08
Patient had visible hemorrhaging
09
Ambulance service was medically necessary
10
Patient is ambulatory
11
Ambulation is Impaired and Walking Aid is Used for Therapy or Mobility
12
Patient is confined to a bed or chair
13
Patient is Confined to a Room or an Area Without Bathroom Facilities
14
Ambulation is Impaired and Walking Aid is Used for Mobility
15
Patient Condition Requires Positioning of the Body or Attachments Which Would Not be Feasible With the Use of an Ordinary Bed
16
Patient needs a trapeze bar to sit up due to respiratory condition or change body positions for other medical reasons
17
Patient's Ability to Breathe is Severely Impaired
18
Patient condition requires frequent and/or immediate changes in body positions
19
Patient can operate controls
20
Siderails Are to be Attached to a Hospital Bed Owned by the Beneficiary
21
Patient owns equipment
22
Mattress or Siderails are Being Used with Prescribed Medically Necessary Hospital Bed Owned by the Beneficiary
23
Patient Needs Lift to Get In or Out of Bed or to Assist in Transfer from Bed to Wheelchair
24
Patient has an orthopedic impairment requiring traction equipment which prevents ambulation during period of use
25
Item has been prescribed as part of a planned regimen of treatment in patient home
26
Patient is highly susceptible to decubitus ulcers
27
Patient or a care-giver has been instructed in use of equipment
29
A 6-7 hour nocturnal study documents 30 episodes of apnea each lasting more than 10 seconds
30
Without the equipment, the patient would require surgery
31
Patient has had a total knee replacement
32
Patient has intractable lymphedema of the extremities
33
Patient is in a nursing home
35
This Feeding is the Only Form of Nutritional Intake for This Patient
37
Oxygen delivery equipment is stationary
38
Certification signed by the physician is on file at the supplier's office
40
Patient or Caregiver is Capable of Using the Equipment Without Technical or Professional Supervision
41
Patient or Caregiver is Unable to Propel or Lift a Standard Weight Wheelchair
42
Patient Requires Leg Elevation for Edema or Body Alignment
43
Patient Weight or Usage Needs Necessitate a Heavy Duty Wheelchair
44
Patient Requires Reclining Function of a Wheelchair
45
Patient is Unable to Operate a Wheelchair Manually
46
Patient or Caregiver Requires Side Transfer into Wheelchair, Commode or Other
58
Durable Medical Equipment (DME) Purchased New
59
Durable Medical Equipment (DME) Is Under Warranty
60
Transportation Was To the Nearest Facility
9D
Lack of Appropriate Facility within Reasonable Distance to Treat Patient in the Event of Complications
9H
Patient Requires Intensive IV Therapy
9J
Patient Requires Protective Isolation
9K
Patient Requires Frequent Monitoring
IH
Independent at Home
LB
Legally Blind
SL
Speech Limitations
Situational
6
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
01
Patient was admitted to a hospital
02
Patient was bed confined before the ambulance service
03
Patient was bed confined after the ambulance service
04
Patient was moved by stretcher
05
Patient was unconscious or in shock
06
Patient was transported in an emergency situation
07
Patient had to be physically restrained
08
Patient had visible hemorrhaging
09
Ambulance service was medically necessary
10
Patient is ambulatory
11
Ambulation is Impaired and Walking Aid is Used for Therapy or Mobility
12
Patient is confined to a bed or chair
13
Patient is Confined to a Room or an Area Without Bathroom Facilities
14
Ambulation is Impaired and Walking Aid is Used for Mobility
15
Patient Condition Requires Positioning of the Body or Attachments Which Would Not be Feasible With the Use of an Ordinary Bed
16
Patient needs a trapeze bar to sit up due to respiratory condition or change body positions for other medical reasons
17
Patient's Ability to Breathe is Severely Impaired
18
Patient condition requires frequent and/or immediate changes in body positions
19
Patient can operate controls
20
Siderails Are to be Attached to a Hospital Bed Owned by the Beneficiary
21
Patient owns equipment
22
Mattress or Siderails are Being Used with Prescribed Medically Necessary Hospital Bed Owned by the Beneficiary
23
Patient Needs Lift to Get In or Out of Bed or to Assist in Transfer from Bed to Wheelchair
24
Patient has an orthopedic impairment requiring traction equipment which prevents ambulation during period of use
25
Item has been prescribed as part of a planned regimen of treatment in patient home
26
Patient is highly susceptible to decubitus ulcers
27
Patient or a care-giver has been instructed in use of equipment
29
A 6-7 hour nocturnal study documents 30 episodes of apnea each lasting more than 10 seconds
30
Without the equipment, the patient would require surgery
31
Patient has had a total knee replacement
32
Patient has intractable lymphedema of the extremities
33
Patient is in a nursing home
35
This Feeding is the Only Form of Nutritional Intake for This Patient
37
Oxygen delivery equipment is stationary
38
Certification signed by the physician is on file at the supplier's office
40
Patient or Caregiver is Capable of Using the Equipment Without Technical or Professional Supervision
41
Patient or Caregiver is Unable to Propel or Lift a Standard Weight Wheelchair
42
Patient Requires Leg Elevation for Edema or Body Alignment
43
Patient Weight or Usage Needs Necessitate a Heavy Duty Wheelchair
44
Patient Requires Reclining Function of a Wheelchair
45
Patient is Unable to Operate a Wheelchair Manually
46
Patient or Caregiver Requires Side Transfer into Wheelchair, Commode or Other
58
Durable Medical Equipment (DME) Purchased New
59
Durable Medical Equipment (DME) Is Under Warranty
60
Transportation Was To the Nearest Facility
9D
Lack of Appropriate Facility within Reasonable Distance to Treat Patient in the Event of Complications
9H
Patient Requires Intensive IV Therapy
9J
Patient Requires Protective Isolation
9K
Patient Requires Frequent Monitoring
IH
Independent at Home
LB
Legally Blind
SL
Speech Limitations
Situational
7
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
01
Patient was admitted to a hospital
02
Patient was bed confined before the ambulance service
03
Patient was bed confined after the ambulance service
04
Patient was moved by stretcher
05
Patient was unconscious or in shock
06
Patient was transported in an emergency situation
07
Patient had to be physically restrained
08
Patient had visible hemorrhaging
09
Ambulance service was medically necessary
10
Patient is ambulatory
11
Ambulation is Impaired and Walking Aid is Used for Therapy or Mobility
12
Patient is confined to a bed or chair
13
Patient is Confined to a Room or an Area Without Bathroom Facilities
14
Ambulation is Impaired and Walking Aid is Used for Mobility
15
Patient Condition Requires Positioning of the Body or Attachments Which Would Not be Feasible With the Use of an Ordinary Bed
16
Patient needs a trapeze bar to sit up due to respiratory condition or change body positions for other medical reasons
17
Patient's Ability to Breathe is Severely Impaired
18
Patient condition requires frequent and/or immediate changes in body positions
19
Patient can operate controls
20
Siderails Are to be Attached to a Hospital Bed Owned by the Beneficiary
21
Patient owns equipment
22
Mattress or Siderails are Being Used with Prescribed Medically Necessary Hospital Bed Owned by the Beneficiary
23
Patient Needs Lift to Get In or Out of Bed or to Assist in Transfer from Bed to Wheelchair
24
Patient has an orthopedic impairment requiring traction equipment which prevents ambulation during period of use
25
Item has been prescribed as part of a planned regimen of treatment in patient home
26
Patient is highly susceptible to decubitus ulcers
27
Patient or a care-giver has been instructed in use of equipment
29
A 6-7 hour nocturnal study documents 30 episodes of apnea each lasting more than 10 seconds
30
Without the equipment, the patient would require surgery
31
Patient has had a total knee replacement
32
Patient has intractable lymphedema of the extremities
33
Patient is in a nursing home
35
This Feeding is the Only Form of Nutritional Intake for This Patient
37
Oxygen delivery equipment is stationary
38
Certification signed by the physician is on file at the supplier's office
40
Patient or Caregiver is Capable of Using the Equipment Without Technical or Professional Supervision
41
Patient or Caregiver is Unable to Propel or Lift a Standard Weight Wheelchair
42
Patient Requires Leg Elevation for Edema or Body Alignment
43
Patient Weight or Usage Needs Necessitate a Heavy Duty Wheelchair
44
Patient Requires Reclining Function of a Wheelchair
45
Patient is Unable to Operate a Wheelchair Manually
46
Patient or Caregiver Requires Side Transfer into Wheelchair, Commode or Other
58
Durable Medical Equipment (DME) Purchased New
59
Durable Medical Equipment (DME) Is Under Warranty
60
Transportation Was To the Nearest Facility
9D
Lack of Appropriate Facility within Reasonable Distance to Treat Patient in the Event of Complications
9H
Patient Requires Intensive IV Therapy
9J
Patient Requires Protective Isolation
9K
Patient Requires Frequent Monitoring
IH
Independent at Home
LB
Legally Blind
SL
Speech Limitations

CRC*11 - OXYGEN THERAPY CERTIFICATION INFORMATION

X12 Name:
Conditions Indicator
X12 Purpose:
To supply information on conditions
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when health care services review is requesting certification and to justify the reason for the request. If not required by this implementation guide, do not send.
TR3 Example:
CRC✱11✱Y✱25~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1136
Code Category
M 1
ID
2
Specifies the situation or category to which the code applies
SEMANTIC: CRC01 qualifies CRC03 through CRC07.
Condition Code Category
CODE
DEFINITION
11
Oxygen Therapy Certification
Required
2
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: CRC02 is a Certification Condition Code applies indicator. A "Y" value indicates the condition codes in CRC03 through CRC07 apply; an "N" value indicates the condition codes in CRC03 through CRC07 do not apply.
INDUSTRY NAME: Certification Condition Indicator
CODE
DEFINITION
N
No
Y
Yes
Required
3
1321
Condition Indicator
M 1
ID
2/3
Code indicating a condition
INDUSTRY NAME: Condition Code
CODE
DEFINITION
06
Patient was transported in an emergency situation
16
Patient needs a trapeze bar to sit up due to respiratory condition or change body positions for other medical reasons
17
Patient's Ability to Breathe is Severely Impaired
25
Item has been prescribed as part of a planned regimen of treatment in patient home
33
Patient is in a nursing home
37
Oxygen delivery equipment is stationary
39
Patient Has Mobilizing Respiratory Tract Secretions
5A
Treatment is rendered related to the terminal illness
9J
Patient Requires Protective Isolation
9K
Patient Requires Frequent Monitoring
DY
Dyspnea with Minimal Exertion
Situational
4
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
06
Patient was transported in an emergency situation
16
Patient needs a trapeze bar to sit up due to respiratory condition or change body positions for other medical reasons
17
Patient's Ability to Breathe is Severely Impaired
25
Item has been prescribed as part of a planned regimen of treatment in patient home
33
Patient is in a nursing home
37
Oxygen delivery equipment is stationary
39
Patient Has Mobilizing Respiratory Tract Secretions
5A
Treatment is rendered related to the terminal illness
9J
Patient Requires Protective Isolation
9K
Patient Requires Frequent Monitoring
DY
Dyspnea with Minimal Exertion
Situational
5
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
06
Patient was transported in an emergency situation
16
Patient needs a trapeze bar to sit up due to respiratory condition or change body positions for other medical reasons
17
Patient's Ability to Breathe is Severely Impaired
25
Item has been prescribed as part of a planned regimen of treatment in patient home
33
Patient is in a nursing home
37
Oxygen delivery equipment is stationary
39
Patient Has Mobilizing Respiratory Tract Secretions
5A
Treatment is rendered related to the terminal illness
9J
Patient Requires Protective Isolation
9K
Patient Requires Frequent Monitoring
DY
Dyspnea with Minimal Exertion
Situational
6
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
06
Patient was transported in an emergency situation
16
Patient needs a trapeze bar to sit up due to respiratory condition or change body positions for other medical reasons
17
Patient's Ability to Breathe is Severely Impaired
25
Item has been prescribed as part of a planned regimen of treatment in patient home
33
Patient is in a nursing home
37
Oxygen delivery equipment is stationary
39
Patient Has Mobilizing Respiratory Tract Secretions
5A
Treatment is rendered related to the terminal illness
9J
Patient Requires Protective Isolation
9K
Patient Requires Frequent Monitoring
DY
Dyspnea with Minimal Exertion
Situational
7
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
06
Patient was transported in an emergency situation
16
Patient needs a trapeze bar to sit up due to respiratory condition or change body positions for other medical reasons
17
Patient's Ability to Breathe is Severely Impaired
25
Item has been prescribed as part of a planned regimen of treatment in patient home
33
Patient is in a nursing home
37
Oxygen delivery equipment is stationary
39
Patient Has Mobilizing Respiratory Tract Secretions
5A
Treatment is rendered related to the terminal illness
9J
Patient Requires Protective Isolation
9K
Patient Requires Frequent Monitoring
DY
Dyspnea with Minimal Exertion

CRC*75 - FUNCTIONAL LIMITATIONS INFORMATION

X12 Name:
Conditions Indicator
X12 Purpose:
To supply information on conditions
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when health care services review is requesting certification and to justify the reason for the request. If not required by this implementation guide, do not send.
TR3 Example:
CRC✱75✱Y✱02~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1136
Code Category
M 1
ID
2
Specifies the situation or category to which the code applies
SEMANTIC: CRC01 qualifies CRC03 through CRC07.
Condition Code Category
CODE
DEFINITION
75
Functional Limitations
Required
2
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: CRC02 is a Certification Condition Code applies indicator. A "Y" value indicates the condition codes in CRC03 through CRC07 apply; an "N" value indicates the condition codes in CRC03 through CRC07 do not apply.
INDUSTRY NAME: Certification Condition Indicator
CODE
DEFINITION
N
No
Y
Yes
Required
3
1321
Condition Indicator
M 1
ID
2/3
Code indicating a condition
INDUSTRY NAME: Condition Code
CODE
DEFINITION
02
Patient was bed confined before the ambulance service
03
Patient was bed confined after the ambulance service
04
Patient was moved by stretcher
05
Patient was unconscious or in shock
06
Patient was transported in an emergency situation
11
Ambulation is Impaired and Walking Aid is Used for Therapy or Mobility
12
Patient is confined to a bed or chair
14
Ambulation is Impaired and Walking Aid is Used for Mobility
15
Patient Condition Requires Positioning of the Body or Attachments Which Would Not be Feasible With the Use of an Ordinary Bed
16
Patient needs a trapeze bar to sit up due to respiratory condition or change body positions for other medical reasons
17
Patient's Ability to Breathe is Severely Impaired
18
Patient condition requires frequent and/or immediate changes in body positions
19
Patient can operate controls
20
Siderails Are to be Attached to a Hospital Bed Owned by the Beneficiary
21
Patient owns equipment
22
Mattress or Siderails are Being Used with Prescribed Medically Necessary Hospital Bed Owned by the Beneficiary
23
Patient Needs Lift to Get In or Out of Bed or to Assist in Transfer from Bed to Wheelchair
24
Patient has an orthopedic impairment requiring traction equipment which prevents ambulation during period of use
25
Item has been prescribed as part of a planned regimen of treatment in patient home
26
Patient is highly susceptible to decubitus ulcers
27
Patient or a care-giver has been instructed in use of equipment
28
Patient has poor diabetic control
30
Without the equipment, the patient would require surgery
31
Patient has had a total knee replacement
32
Patient has intractable lymphedema of the extremities
35
This Feeding is the Only Form of Nutritional Intake for This Patient
37
Oxygen delivery equipment is stationary
39
Patient Has Mobilizing Respiratory Tract Secretions
40
Patient or Caregiver is Capable of Using the Equipment Without Technical or Professional Supervision
41
Patient or Caregiver is Unable to Propel or Lift a Standard Weight Wheelchair
42
Patient Requires Leg Elevation for Edema or Body Alignment
43
Patient Weight or Usage Needs Necessitate a Heavy Duty Wheelchair
44
Patient Requires Reclining Function of a Wheelchair
45
Patient is Unable to Operate a Wheelchair Manually
46
Patient or Caregiver Requires Side Transfer into Wheelchair, Commode or Other
5A
Treatment is rendered related to the terminal illness
68
Severe
69
Moderate
9E
Sudden Onset of Disorientation
9F
Sudden Onset of Severe, Incapacitating Pain
9H
Patient Requires Intensive IV Therapy
AA
Amputation
AL
Ambulation Limitations
BL
Bowel Limitations, Bladder Limitations, or both (Incontinence)
BPD
Beneficiary is Partially Dependent
BTD
Beneficiary is Totally Dependent
CA
Cane Required
CB
Complete Bedrest
CNJ
Cumulative Injury
CO
Contracture
DY
Dyspnea with Minimal Exertion
EL
Endurance Limitations
EP
Exercises Prescribed
HL
Hearing Limitations
LB
Legally Blind
LE
Lethargic
OL
Other Limitation
PA
Paralysis
PW
Partial Weight Bearing
SL
Speech Limitations
TNJ
Traumatic Injury
WA
Walker Required
WR
Wheelchair Required
Situational
4
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
02
Patient was bed confined before the ambulance service
03
Patient was bed confined after the ambulance service
04
Patient was moved by stretcher
05
Patient was unconscious or in shock
06
Patient was transported in an emergency situation
11
Ambulation is Impaired and Walking Aid is Used for Therapy or Mobility
12
Patient is confined to a bed or chair
14
Ambulation is Impaired and Walking Aid is Used for Mobility
15
Patient Condition Requires Positioning of the Body or Attachments Which Would Not be Feasible With the Use of an Ordinary Bed
16
Patient needs a trapeze bar to sit up due to respiratory condition or change body positions for other medical reasons
17
Patient's Ability to Breathe is Severely Impaired
18
Patient condition requires frequent and/or immediate changes in body positions
19
Patient can operate controls
20
Siderails Are to be Attached to a Hospital Bed Owned by the Beneficiary
21
Patient owns equipment
22
Mattress or Siderails are Being Used with Prescribed Medically Necessary Hospital Bed Owned by the Beneficiary
23
Patient Needs Lift to Get In or Out of Bed or to Assist in Transfer from Bed to Wheelchair
24
Patient has an orthopedic impairment requiring traction equipment which prevents ambulation during period of use
25
Item has been prescribed as part of a planned regimen of treatment in patient home
26
Patient is highly susceptible to decubitus ulcers
27
Patient or a care-giver has been instructed in use of equipment
28
Patient has poor diabetic control
30
Without the equipment, the patient would require surgery
31
Patient has had a total knee replacement
32
Patient has intractable lymphedema of the extremities
35
This Feeding is the Only Form of Nutritional Intake for This Patient
37
Oxygen delivery equipment is stationary
39
Patient Has Mobilizing Respiratory Tract Secretions
40
Patient or Caregiver is Capable of Using the Equipment Without Technical or Professional Supervision
41
Patient or Caregiver is Unable to Propel or Lift a Standard Weight Wheelchair
42
Patient Requires Leg Elevation for Edema or Body Alignment
43
Patient Weight or Usage Needs Necessitate a Heavy Duty Wheelchair
44
Patient Requires Reclining Function of a Wheelchair
45
Patient is Unable to Operate a Wheelchair Manually
46
Patient or Caregiver Requires Side Transfer into Wheelchair, Commode or Other
5A
Treatment is rendered related to the terminal illness
68
Severe
69
Moderate
9E
Sudden Onset of Disorientation
9F
Sudden Onset of Severe, Incapacitating Pain
9H
Patient Requires Intensive IV Therapy
AA
Amputation
AL
Ambulation Limitations
BL
Bowel Limitations, Bladder Limitations, or both (Incontinence)
BPD
Beneficiary is Partially Dependent
BTD
Beneficiary is Totally Dependent
CA
Cane Required
CB
Complete Bedrest
CNJ
Cumulative Injury
CO
Contracture
DY
Dyspnea with Minimal Exertion
EL
Endurance Limitations
EP
Exercises Prescribed
HL
Hearing Limitations
LB
Legally Blind
LE
Lethargic
OL
Other Limitation
PA
Paralysis
PW
Partial Weight Bearing
SL
Speech Limitations
TNJ
Traumatic Injury
WA
Walker Required
WR
Wheelchair Required
Situational
5
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
02
Patient was bed confined before the ambulance service
03
Patient was bed confined after the ambulance service
04
Patient was moved by stretcher
05
Patient was unconscious or in shock
06
Patient was transported in an emergency situation
11
Ambulation is Impaired and Walking Aid is Used for Therapy or Mobility
12
Patient is confined to a bed or chair
14
Ambulation is Impaired and Walking Aid is Used for Mobility
15
Patient Condition Requires Positioning of the Body or Attachments Which Would Not be Feasible With the Use of an Ordinary Bed
16
Patient needs a trapeze bar to sit up due to respiratory condition or change body positions for other medical reasons
17
Patient's Ability to Breathe is Severely Impaired
18
Patient condition requires frequent and/or immediate changes in body positions
19
Patient can operate controls
20
Siderails Are to be Attached to a Hospital Bed Owned by the Beneficiary
21
Patient owns equipment
22
Mattress or Siderails are Being Used with Prescribed Medically Necessary Hospital Bed Owned by the Beneficiary
23
Patient Needs Lift to Get In or Out of Bed or to Assist in Transfer from Bed to Wheelchair
24
Patient has an orthopedic impairment requiring traction equipment which prevents ambulation during period of use
25
Item has been prescribed as part of a planned regimen of treatment in patient home
26
Patient is highly susceptible to decubitus ulcers
27
Patient or a care-giver has been instructed in use of equipment
28
Patient has poor diabetic control
30
Without the equipment, the patient would require surgery
31
Patient has had a total knee replacement
32
Patient has intractable lymphedema of the extremities
35
This Feeding is the Only Form of Nutritional Intake for This Patient
37
Oxygen delivery equipment is stationary
39
Patient Has Mobilizing Respiratory Tract Secretions
40
Patient or Caregiver is Capable of Using the Equipment Without Technical or Professional Supervision
41
Patient or Caregiver is Unable to Propel or Lift a Standard Weight Wheelchair
42
Patient Requires Leg Elevation for Edema or Body Alignment
43
Patient Weight or Usage Needs Necessitate a Heavy Duty Wheelchair
44
Patient Requires Reclining Function of a Wheelchair
45
Patient is Unable to Operate a Wheelchair Manually
46
Patient or Caregiver Requires Side Transfer into Wheelchair, Commode or Other
5A
Treatment is rendered related to the terminal illness
68
Severe
69
Moderate
9E
Sudden Onset of Disorientation
9F
Sudden Onset of Severe, Incapacitating Pain
9H
Patient Requires Intensive IV Therapy
AA
Amputation
AL
Ambulation Limitations
BL
Bowel Limitations, Bladder Limitations, or both (Incontinence)
BPD
Beneficiary is Partially Dependent
BTD
Beneficiary is Totally Dependent
CA
Cane Required
CB
Complete Bedrest
CNJ
Cumulative Injury
CO
Contracture
DY
Dyspnea with Minimal Exertion
EL
Endurance Limitations
EP
Exercises Prescribed
HL
Hearing Limitations
LB
Legally Blind
LE
Lethargic
OL
Other Limitation
PA
Paralysis
PW
Partial Weight Bearing
SL
Speech Limitations
TNJ
Traumatic Injury
WA
Walker Required
WR
Wheelchair Required
Situational
6
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
02
Patient was bed confined before the ambulance service
03
Patient was bed confined after the ambulance service
04
Patient was moved by stretcher
05
Patient was unconscious or in shock
06
Patient was transported in an emergency situation
11
Ambulation is Impaired and Walking Aid is Used for Therapy or Mobility
12
Patient is confined to a bed or chair
14
Ambulation is Impaired and Walking Aid is Used for Mobility
15
Patient Condition Requires Positioning of the Body or Attachments Which Would Not be Feasible With the Use of an Ordinary Bed
16
Patient needs a trapeze bar to sit up due to respiratory condition or change body positions for other medical reasons
17
Patient's Ability to Breathe is Severely Impaired
18
Patient condition requires frequent and/or immediate changes in body positions
19
Patient can operate controls
20
Siderails Are to be Attached to a Hospital Bed Owned by the Beneficiary
21
Patient owns equipment
22
Mattress or Siderails are Being Used with Prescribed Medically Necessary Hospital Bed Owned by the Beneficiary
23
Patient Needs Lift to Get In or Out of Bed or to Assist in Transfer from Bed to Wheelchair
24
Patient has an orthopedic impairment requiring traction equipment which prevents ambulation during period of use
25
Item has been prescribed as part of a planned regimen of treatment in patient home
26
Patient is highly susceptible to decubitus ulcers
27
Patient or a care-giver has been instructed in use of equipment
28
Patient has poor diabetic control
30
Without the equipment, the patient would require surgery
31
Patient has had a total knee replacement
32
Patient has intractable lymphedema of the extremities
35
This Feeding is the Only Form of Nutritional Intake for This Patient
37
Oxygen delivery equipment is stationary
39
Patient Has Mobilizing Respiratory Tract Secretions
40
Patient or Caregiver is Capable of Using the Equipment Without Technical or Professional Supervision
41
Patient or Caregiver is Unable to Propel or Lift a Standard Weight Wheelchair
42
Patient Requires Leg Elevation for Edema or Body Alignment
43
Patient Weight or Usage Needs Necessitate a Heavy Duty Wheelchair
44
Patient Requires Reclining Function of a Wheelchair
45
Patient is Unable to Operate a Wheelchair Manually
46
Patient or Caregiver Requires Side Transfer into Wheelchair, Commode or Other
5A
Treatment is rendered related to the terminal illness
68
Severe
69
Moderate
9E
Sudden Onset of Disorientation
9F
Sudden Onset of Severe, Incapacitating Pain
9H
Patient Requires Intensive IV Therapy
AA
Amputation
AL
Ambulation Limitations
BL
Bowel Limitations, Bladder Limitations, or both (Incontinence)
BPD
Beneficiary is Partially Dependent
BTD
Beneficiary is Totally Dependent
CA
Cane Required
CB
Complete Bedrest
CNJ
Cumulative Injury
CO
Contracture
DY
Dyspnea with Minimal Exertion
EL
Endurance Limitations
EP
Exercises Prescribed
HL
Hearing Limitations
LB
Legally Blind
LE
Lethargic
OL
Other Limitation
PA
Paralysis
PW
Partial Weight Bearing
SL
Speech Limitations
TNJ
Traumatic Injury
WA
Walker Required
WR
Wheelchair Required
Situational
7
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
02
Patient was bed confined before the ambulance service
03
Patient was bed confined after the ambulance service
04
Patient was moved by stretcher
05
Patient was unconscious or in shock
06
Patient was transported in an emergency situation
11
Ambulation is Impaired and Walking Aid is Used for Therapy or Mobility
12
Patient is confined to a bed or chair
14
Ambulation is Impaired and Walking Aid is Used for Mobility
15
Patient Condition Requires Positioning of the Body or Attachments Which Would Not be Feasible With the Use of an Ordinary Bed
16
Patient needs a trapeze bar to sit up due to respiratory condition or change body positions for other medical reasons
17
Patient's Ability to Breathe is Severely Impaired
18
Patient condition requires frequent and/or immediate changes in body positions
19
Patient can operate controls
20
Siderails Are to be Attached to a Hospital Bed Owned by the Beneficiary
21
Patient owns equipment
22
Mattress or Siderails are Being Used with Prescribed Medically Necessary Hospital Bed Owned by the Beneficiary
23
Patient Needs Lift to Get In or Out of Bed or to Assist in Transfer from Bed to Wheelchair
24
Patient has an orthopedic impairment requiring traction equipment which prevents ambulation during period of use
25
Item has been prescribed as part of a planned regimen of treatment in patient home
26
Patient is highly susceptible to decubitus ulcers
27
Patient or a care-giver has been instructed in use of equipment
28
Patient has poor diabetic control
30
Without the equipment, the patient would require surgery
31
Patient has had a total knee replacement
32
Patient has intractable lymphedema of the extremities
35
This Feeding is the Only Form of Nutritional Intake for This Patient
37
Oxygen delivery equipment is stationary
39
Patient Has Mobilizing Respiratory Tract Secretions
40
Patient or Caregiver is Capable of Using the Equipment Without Technical or Professional Supervision
41
Patient or Caregiver is Unable to Propel or Lift a Standard Weight Wheelchair
42
Patient Requires Leg Elevation for Edema or Body Alignment
43
Patient Weight or Usage Needs Necessitate a Heavy Duty Wheelchair
44
Patient Requires Reclining Function of a Wheelchair
45
Patient is Unable to Operate a Wheelchair Manually
46
Patient or Caregiver Requires Side Transfer into Wheelchair, Commode or Other
5A
Treatment is rendered related to the terminal illness
68
Severe
69
Moderate
9E
Sudden Onset of Disorientation
9F
Sudden Onset of Severe, Incapacitating Pain
9H
Patient Requires Intensive IV Therapy
AA
Amputation
AL
Ambulation Limitations
BL
Bowel Limitations, Bladder Limitations, or both (Incontinence)
BPD
Beneficiary is Partially Dependent
BTD
Beneficiary is Totally Dependent
CA
Cane Required
CB
Complete Bedrest
CNJ
Cumulative Injury
CO
Contracture
DY
Dyspnea with Minimal Exertion
EL
Endurance Limitations
EP
Exercises Prescribed
HL
Hearing Limitations
LB
Legally Blind
LE
Lethargic
OL
Other Limitation
PA
Paralysis
PW
Partial Weight Bearing
SL
Speech Limitations
TNJ
Traumatic Injury
WA
Walker Required
WR
Wheelchair Required

CRC*76 - ACTIVITIES PERMITTED INFORMATION

X12 Name:
Conditions Indicator
X12 Purpose:
To supply information on conditions
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when health care services review is requesting certification and to justify the reason for the request. If not required by this implementation guide, do not send.
TR3 Example:
CRC✱76✱Y✱10~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1136
Code Category
M 1
ID
2
Specifies the situation or category to which the code applies
SEMANTIC: CRC01 qualifies CRC03 through CRC07.
Condition Code Category
CODE
DEFINITION
76
Activities Permitted
Required
2
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: CRC02 is a Certification Condition Code applies indicator. A "Y" value indicates the condition codes in CRC03 through CRC07 apply; an "N" value indicates the condition codes in CRC03 through CRC07 do not apply.
INDUSTRY NAME: Certification Condition Indicator
CODE
DEFINITION
N
No
Y
Yes
Required
3
1321
Condition Indicator
M 1
ID
2/3
Code indicating a condition
INDUSTRY NAME: Condition Code
CODE
DEFINITION
10
Patient is ambulatory
13
Patient is Confined to a Room or an Area Without Bathroom Facilities
19
Patient can operate controls
21
Patient owns equipment
22
Mattress or Siderails are Being Used with Prescribed Medically Necessary Hospital Bed Owned by the Beneficiary
27
Patient or a care-giver has been instructed in use of equipment
31
Patient has had a total knee replacement
40
Patient or Caregiver is Capable of Using the Equipment Without Technical or Professional Supervision
BR
Bedrest BRP (Bathroom Privileges)
CA
Cane Required
CB
Complete Bedrest
CR
Crutches Required
EL
Endurance Limitations
EP
Exercises Prescribed
IH
Independent at Home
NR
No Restrictions
PA
Paralysis
PW
Partial Weight Bearing
TR
Transfer to Bed, or Chair, or Both
UT
Up as Tolerated
WA
Walker Required
WR
Wheelchair Required
Situational
4
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
10
Patient is ambulatory
13
Patient is Confined to a Room or an Area Without Bathroom Facilities
19
Patient can operate controls
21
Patient owns equipment
22
Mattress or Siderails are Being Used with Prescribed Medically Necessary Hospital Bed Owned by the Beneficiary
27
Patient or a care-giver has been instructed in use of equipment
31
Patient has had a total knee replacement
40
Patient or Caregiver is Capable of Using the Equipment Without Technical or Professional Supervision
BR
Bedrest BRP (Bathroom Privileges)
CA
Cane Required
CB
Complete Bedrest
CR
Crutches Required
EL
Endurance Limitations
EP
Exercises Prescribed
IH
Independent at Home
NR
No Restrictions
PA
Paralysis
PW
Partial Weight Bearing
TR
Transfer to Bed, or Chair, or Both
UT
Up as Tolerated
WA
Walker Required
WR
Wheelchair Required
Situational
5
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
10
Patient is ambulatory
13
Patient is Confined to a Room or an Area Without Bathroom Facilities
19
Patient can operate controls
21
Patient owns equipment
22
Mattress or Siderails are Being Used with Prescribed Medically Necessary Hospital Bed Owned by the Beneficiary
27
Patient or a care-giver has been instructed in use of equipment
31
Patient has had a total knee replacement
40
Patient or Caregiver is Capable of Using the Equipment Without Technical or Professional Supervision
BR
Bedrest BRP (Bathroom Privileges)
CA
Cane Required
CB
Complete Bedrest
CR
Crutches Required
EL
Endurance Limitations
EP
Exercises Prescribed
IH
Independent at Home
NR
No Restrictions
PA
Paralysis
PW
Partial Weight Bearing
TR
Transfer to Bed, or Chair, or Both
UT
Up as Tolerated
WA
Walker Required
WR
Wheelchair Required
Situational
6
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
10
Patient is ambulatory
13
Patient is Confined to a Room or an Area Without Bathroom Facilities
19
Patient can operate controls
21
Patient owns equipment
22
Mattress or Siderails are Being Used with Prescribed Medically Necessary Hospital Bed Owned by the Beneficiary
27
Patient or a care-giver has been instructed in use of equipment
31
Patient has had a total knee replacement
40
Patient or Caregiver is Capable of Using the Equipment Without Technical or Professional Supervision
BR
Bedrest BRP (Bathroom Privileges)
CA
Cane Required
CB
Complete Bedrest
CR
Crutches Required
EL
Endurance Limitations
EP
Exercises Prescribed
IH
Independent at Home
NR
No Restrictions
PA
Paralysis
PW
Partial Weight Bearing
TR
Transfer to Bed, or Chair, or Both
UT
Up as Tolerated
WA
Walker Required
WR
Wheelchair Required
Situational
7
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
10
Patient is ambulatory
13
Patient is Confined to a Room or an Area Without Bathroom Facilities
19
Patient can operate controls
21
Patient owns equipment
22
Mattress or Siderails are Being Used with Prescribed Medically Necessary Hospital Bed Owned by the Beneficiary
27
Patient or a care-giver has been instructed in use of equipment
31
Patient has had a total knee replacement
40
Patient or Caregiver is Capable of Using the Equipment Without Technical or Professional Supervision
BR
Bedrest BRP (Bathroom Privileges)
CA
Cane Required
CB
Complete Bedrest
CR
Crutches Required
EL
Endurance Limitations
EP
Exercises Prescribed
IH
Independent at Home
NR
No Restrictions
PA
Paralysis
PW
Partial Weight Bearing
TR
Transfer to Bed, or Chair, or Both
UT
Up as Tolerated
WA
Walker Required
WR
Wheelchair Required

CRC*77 - MENTAL STATUS INFORMATION

X12 Name:
Conditions Indicator
X12 Purpose:
To supply information on conditions
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when health care services review is requesting certification and to justify the reason for the request. If not required by this implementation guide, do not send.
TR3 Example:
CRC✱77✱Y✱07~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1136
Code Category
M 1
ID
2
Specifies the situation or category to which the code applies
SEMANTIC: CRC01 qualifies CRC03 through CRC07.
Condition Code Category
CODE
DEFINITION
77
Mental Status
Required
2
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: CRC02 is a Certification Condition Code applies indicator. A "Y" value indicates the condition codes in CRC03 through CRC07 apply; an "N" value indicates the condition codes in CRC03 through CRC07 do not apply.
INDUSTRY NAME: Certification Condition Indicator
CODE
DEFINITION
N
No
Y
Yes
Required
3
1321
Condition Indicator
M 1
ID
2/3
Code indicating a condition
INDUSTRY NAME: Condition Code
CODE
DEFINITION
01
Patient was admitted to a hospital
05
Patient was unconscious or in shock
07
Patient had to be physically restrained
13
Patient is Confined to a Room or an Area Without Bathroom Facilities
20
Siderails Are to be Attached to a Hospital Bed Owned by the Beneficiary
22
Mattress or Siderails are Being Used with Prescribed Medically Necessary Hospital Bed Owned by the Beneficiary
23
Patient Needs Lift to Get In or Out of Bed or to Assist in Transfer from Bed to Wheelchair
26
Patient is highly susceptible to decubitus ulcers
33
Patient is in a nursing home
34
Patient is conscious
5A
Treatment is rendered related to the terminal illness
68
Severe
69
Moderate
9E
Sudden Onset of Disorientation
9F
Sudden Onset of Severe, Incapacitating Pain
9J
Patient Requires Protective Isolation
9K
Patient Requires Frequent Monitoring
AG
Agitated
BPD
Beneficiary is Partially Dependent
BTD
Beneficiary is Totally Dependent
CB
Complete Bedrest
CM
Comatose
DI
Disoriented
DP
Depressed
FO
Forgetful
HO
Hostile
LE
Lethargic
MC
Other Mental Condition
OT
Oriented
UN
Uncooperative
Situational
4
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
01
Patient was admitted to a hospital
05
Patient was unconscious or in shock
07
Patient had to be physically restrained
13
Patient is Confined to a Room or an Area Without Bathroom Facilities
20
Siderails Are to be Attached to a Hospital Bed Owned by the Beneficiary
22
Mattress or Siderails are Being Used with Prescribed Medically Necessary Hospital Bed Owned by the Beneficiary
23
Patient Needs Lift to Get In or Out of Bed or to Assist in Transfer from Bed to Wheelchair
26
Patient is highly susceptible to decubitus ulcers
33
Patient is in a nursing home
34
Patient is conscious
5A
Treatment is rendered related to the terminal illness
68
Severe
69
Moderate
9E
Sudden Onset of Disorientation
9F
Sudden Onset of Severe, Incapacitating Pain
9J
Patient Requires Protective Isolation
9K
Patient Requires Frequent Monitoring
AG
Agitated
BPD
Beneficiary is Partially Dependent
BTD
Beneficiary is Totally Dependent
CB
Complete Bedrest
CM
Comatose
DI
Disoriented
DP
Depressed
FO
Forgetful
HO
Hostile
LE
Lethargic
MC
Other Mental Condition
OT
Oriented
UN
Uncooperative
Situational
5
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
01
Patient was admitted to a hospital
05
Patient was unconscious or in shock
07
Patient had to be physically restrained
13
Patient is Confined to a Room or an Area Without Bathroom Facilities
20
Siderails Are to be Attached to a Hospital Bed Owned by the Beneficiary
22
Mattress or Siderails are Being Used with Prescribed Medically Necessary Hospital Bed Owned by the Beneficiary
23
Patient Needs Lift to Get In or Out of Bed or to Assist in Transfer from Bed to Wheelchair
26
Patient is highly susceptible to decubitus ulcers
33
Patient is in a nursing home
34
Patient is conscious
5A
Treatment is rendered related to the terminal illness
68
Severe
69
Moderate
9E
Sudden Onset of Disorientation
9F
Sudden Onset of Severe, Incapacitating Pain
9J
Patient Requires Protective Isolation
9K
Patient Requires Frequent Monitoring
AG
Agitated
BPD
Beneficiary is Partially Dependent
BTD
Beneficiary is Totally Dependent
CB
Complete Bedrest
CM
Comatose
DI
Disoriented
DP
Depressed
FO
Forgetful
HO
Hostile
LE
Lethargic
MC
Other Mental Condition
OT
Oriented
UN
Uncooperative
Situational
6
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
01
Patient was admitted to a hospital
05
Patient was unconscious or in shock
07
Patient had to be physically restrained
13
Patient is Confined to a Room or an Area Without Bathroom Facilities
20
Siderails Are to be Attached to a Hospital Bed Owned by the Beneficiary
22
Mattress or Siderails are Being Used with Prescribed Medically Necessary Hospital Bed Owned by the Beneficiary
23
Patient Needs Lift to Get In or Out of Bed or to Assist in Transfer from Bed to Wheelchair
26
Patient is highly susceptible to decubitus ulcers
33
Patient is in a nursing home
34
Patient is conscious
5A
Treatment is rendered related to the terminal illness
68
Severe
69
Moderate
9E
Sudden Onset of Disorientation
9F
Sudden Onset of Severe, Incapacitating Pain
9J
Patient Requires Protective Isolation
9K
Patient Requires Frequent Monitoring
AG
Agitated
BPD
Beneficiary is Partially Dependent
BTD
Beneficiary is Totally Dependent
CB
Complete Bedrest
CM
Comatose
DI
Disoriented
DP
Depressed
FO
Forgetful
HO
Hostile
LE
Lethargic
MC
Other Mental Condition
OT
Oriented
UN
Uncooperative
Situational
7
1321
Condition Indicator
O 1
ID
2/3
Code indicating a condition
SITUATIONAL RULE: Required when multiple conditions apply to the certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Condition Code
Use codes listed in CRC03.
CODE
DEFINITION
01
Patient was admitted to a hospital
05
Patient was unconscious or in shock
07
Patient had to be physically restrained
13
Patient is Confined to a Room or an Area Without Bathroom Facilities
20
Siderails Are to be Attached to a Hospital Bed Owned by the Beneficiary
22
Mattress or Siderails are Being Used with Prescribed Medically Necessary Hospital Bed Owned by the Beneficiary
23
Patient Needs Lift to Get In or Out of Bed or to Assist in Transfer from Bed to Wheelchair
26
Patient is highly susceptible to decubitus ulcers
33
Patient is in a nursing home
34
Patient is conscious
5A
Treatment is rendered related to the terminal illness
68
Severe
69
Moderate
9E
Sudden Onset of Disorientation
9F
Sudden Onset of Severe, Incapacitating Pain
9J
Patient Requires Protective Isolation
9K
Patient Requires Frequent Monitoring
AG
Agitated
BPD
Beneficiary is Partially Dependent
BTD
Beneficiary is Totally Dependent
CB
Complete Bedrest
CM
Comatose
DI
Disoriented
DP
Depressed
FO
Forgetful
HO
Hostile
LE
Lethargic
MC
Other Mental Condition
OT
Oriented
UN
Uncooperative

CL1 - NURSING HOME RESIDENTIAL STATUS

X12 Name:
Claim Codes
X12 Purpose:
To supply information specific to hospital claims
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when certification involves a nursing home resident and Loop 2000F is not used. If not required by this implementation guide, do not send.
TR3 Example:
CL1✱3✱✱01~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Not Used
1
1315
Admission Type Code
O 1
ID
1
Not Used
2
1314
Admission Source Code
O 1
ID
1
Not Used
3
1352
Patient Status Code
O 1
ID
1/2
Situational
4
1345
Nursing Home Residential Status Code
O 1
ID
1
Code specifying the status of a nursing home resident at the time of service
SITUATIONAL RULE: Required when certification involves a nursing home resident. If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Transferred to Intermediate Care Facility - Mentally Retarded (ICF-MR)
2
Newly Admitted
3
Newly Eligible
4
No Longer Eligible
5
Still a Resident
6
Temporary Absence - Hospital
7
Temporary Absence - Other
8
Transferred to Intermediate Care Facility - Level II (ICF II)
9
Other

CR1 - AMBULANCE TRANSPORT INFORMATION

X12 Name:
Ambulance Certification
X12 Purpose:
To supply information related to the ambulance service rendered to a patient
X12 Syntax:
  1. P0102
    If either CR101 or CR102 is present, then the other is required.
  2. P0506
    If either CR105 or CR106 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when health care services review is for non-emergency transportation services. If not required by this implementation guide, do not send.
TR3 Notes:
When the CR1 segment is used, then Loop 2010EB is required.
TR3 Example:
CR1✱LB✱155✱T✱A~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Situational
1
355
Unit or Basis for Measurement Code
X 1
ID
2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
SEGMENT SYNTAX: P0102
SITUATIONAL RULE: Required when CR102 is present. If not required by this implementation guide, do not send.
CODE
DEFINITION
KG
Kilogram
LB
Pound
Situational
2
81
Weight
X 1
R
1/10
Numeric value of weight
SEMANTIC: CR102 is the weight of the patient at time of transport.
SEGMENT SYNTAX: P0102
SITUATIONAL RULE: Required when patient weight information is needed to justify the medical necessity of the level of ambulance services. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Weight
Required
3
1316
Ambulance Transport Code
O 1
ID
1
Code indicating the type of ambulance transport
CODE
DEFINITION
I
Initial Trip
R
Return Trip
T
Transfer Trip
X
Round Trip
Situational
4
1317
Ambulance Transport Reason Code
O 1
ID
1
Code indicating the reason for ambulance transport
SITUATIONAL RULE: Required when ambulance transport reason is required to determine medical necessity. If not required by this implementation guide, do not send.
CODE
DEFINITION
A
Patient was transported to nearest facility for care of symptoms, complaints, or both
B
Patient was transported for the benefit of a preferred physician
C
Patient was transported for the nearness of family members
D
Patient was transported for the care of a specialist or for availability of specialized equipment
E
Patient Transferred to Rehabilitation Facility
F
Patient Transferred to Residential Facility
Situational
5
355
Unit or Basis for Measurement Code
X 1
ID
2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when distance of transportation is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
DH
Miles
DK
Kilometers
Situational
6
380
Quantity
X 1
R
1/15
Numeric value of quantity
SEMANTIC: CR106 is the distance traveled during transport.
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when distance of transportation is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Transport Distance
Not Used
7
166
Address Information
O 1
AN
1/55
Not Used
8
166
Address Information
O 1
AN
1/55
Situational
9
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
SEMANTIC: CR109 is the purpose for the round trip ambulance service.
SITUATIONAL RULE: Required when CR103 (Ambulance Transport Code) = "X Round Trip". If not required by this implementation guide, do not send.
INDUSTRY NAME: Round Trip Purpose Description
Situational
10
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
SEMANTIC: CR110 is the purpose for the usage of a stretcher during ambulance service.
SITUATIONAL RULE: Required when needed to justify usage of a stretcher. If not required by this implementation guide, do not send.
INDUSTRY NAME: Stretcher Purpose Description

CR2 - SPINAL MANIPULATION SERVICE INFORMATION

X12 Name:
Chiropractic Certification
X12 Purpose:
To supply information related to the chiropractic service rendered to a patient
X12 Syntax:
  1. P0102
    If either CR201 or CR202 is present, then the other is required.
  2. C0403
    If CR204 is present, then CR203 is required.
  3. P0506
    If either CR205 or CR206 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when requesting certification for spinal manipulation services (UM01=HS) when the patient's condition or treatment involves subluxation. If not required by this implementation guide, do not send.
TR3 Example:
CR2✱1✱5✱✱✱✱✱✱C✱Y✱✱✱Y~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Situational
1
609
Count
X 1
N
1/9
Occurrence counter
SEMANTIC: CR201 is the number this treatment is in the series.
SEGMENT SYNTAX: P0102
SITUATIONAL RULE: Required when requesting certification for a specific treatment number in a series of treatments. If not required by this implementation guide, do not send.
INDUSTRY NAME: Treatment Series Number
Situational
2
380
Quantity
X 1
R
1/15
Numeric value of quantity
SEMANTIC: CR202 is the total number of treatments in the series.
SEGMENT SYNTAX: P0102
SITUATIONAL RULE: Required when requesting certification for a specific treatment number in a series of treatments. If not required by this implementation guide, do not send.
INDUSTRY NAME: Treatment Count
Situational
3
1367
Subluxation Level Code
X 1
ID
2/3
Code identifying the specific level of subluxation
COMMENT: When both CR203 and CR204 are present, CR203 is the beginning level of subluxation and CR204 is the ending level of subluxation.
SEGMENT SYNTAX: C0403
SITUATIONAL RULE: Required when the patient's condition or treatment involves subluxation. If not required by this implementation guide, do not send.
CODE
DEFINITION
C1
Cervical 1
C2
Cervical 2
C3
Cervical 3
C4
Cervical 4
C5
Cervical 5
C6
Cervical 6
C7
Cervical 7
CO
Coccyx
IL
Ilium
L1
Lumbar 1
L2
Lumbar 2
L3
Lumbar 3
L4
Lumbar 4
L5
Lumbar 5
OC
Occiput
SA
Sacrum
T1
Thoracic 1
T10
Thoracic 10
T11
Thoracic 11
T12
Thoracic 12
T2
Thoracic 2
T3
Thoracic 3
T4
Thoracic 4
T5
Thoracic 5
T6
Thoracic 6
T7
Thoracic 7
T8
Thoracic 8
T9
Thoracic 9
Situational
4
1367
Subluxation Level Code
O 1
ID
2/3
Code identifying the specific level of subluxation
SEGMENT SYNTAX: C0403
SITUATIONAL RULE: Required when the patient's condition or treatment involves subluxation to express the ending level of subluxation. If not required by this implementation guide, do not send.
CODE
DEFINITION
C1
Cervical 1
C2
Cervical 2
C3
Cervical 3
C4
Cervical 4
C5
Cervical 5
C6
Cervical 6
C7
Cervical 7
CO
Coccyx
IL
Ilium
L1
Lumbar 1
L2
Lumbar 2
L3
Lumbar 3
L4
Lumbar 4
L5
Lumbar 5
OC
Occiput
SA
Sacrum
T1
Thoracic 1
T10
Thoracic 10
T11
Thoracic 11
T12
Thoracic 12
T2
Thoracic 2
T3
Thoracic 3
T4
Thoracic 4
T5
Thoracic 5
T6
Thoracic 6
T7
Thoracic 7
T8
Thoracic 8
T9
Thoracic 9
Not Used
5
355
Unit or Basis for Measurement Code
X 1
ID
2
Not Used
6
380
Quantity
X 1
R
1/15
Not Used
7
380
Quantity
O 1
R
1/15
Required
8
1342
Nature of Condition Code
O 1
ID
1
Code indicating the nature of a patient's condition
INDUSTRY NAME: Patient Condition Code
CODE
DEFINITION
A
Acute Condition
C
Chronic Condition
D
Non-acute
E
Non-Life Threatening
F
Routine
G
Symptomatic
M
Acute Manifestation of a Chronic Condition
Required
9
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: CR209 is complication indicator. A "Y" value indicates a complicated condition; an "N" value indicates an uncomplicated condition.
INDUSTRY NAME: Complication Indicator
CODE
DEFINITION
N
No
Y
Yes
Situational
10
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
SEMANTIC: CR210 is a description of the patient's condition.
SITUATIONAL RULE: Required when necessary to clarify patient condition. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Condition Description
Situational
11
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
SEMANTIC: CR211 is an additional description of the patient's condition.
SITUATIONAL RULE: Required when necessary to clarify patient condition. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Condition Description
Situational
12
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: CR212 is X-rays availability indicator. A "Y" value indicates X-rays are maintained and available for carrier review; an "N" value indicates X-rays are not maintained and available for carrier review.
SITUATIONAL RULE: Required when X-rays are available. If not required by this implementation guide, do not send.
INDUSTRY NAME: X-ray Availability Indicator
CODE
DEFINITION
N
No
Y
Yes

CR5 - HOME OXYGEN THERAPY INFORMATION

X12 Name:
Oxygen Therapy Certification
X12 Purpose:
To supply information regarding certification of medical necessity for home oxygen therapy
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when requesting initial, extended, or revised certification of home oxygen therapy. If not required by this implementation guide, do not send.
TR3 Notes:
  1. Use the UM segment data element UM02 instead of CR501 to specify the Certification Type Code.
  2. Use the HSD segment instead of CR502 to specify the treatment period.
TR3 Example:
CR5✱✱✱D✱✱✱1✱✱✱✱✱87✱N✱✱✱✱✱A~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Not Used
1
1322
Certification Type Code
O 1
ID
1
Not Used
2
380
Quantity
O 1
R
1/15
Required
3
1348
Oxygen Equipment Type Code
O 1
ID
1
Code indicating the specific type of equipment being prescribed for the delivery of oxygen
CODE
DEFINITION
A
Concentrator
B
Liquid Stationary
C
Gaseous Stationary
D
Liquid Portable
E
Gaseous Portable
O
Other
Situational
4
1348
Oxygen Equipment Type Code
O 1
ID
1
Code indicating the specific type of equipment being prescribed for the delivery of oxygen
SITUATIONAL RULE: Required when CR503 is present and more than one type of equipment is required to administer the oxygen therapy. If not required by this implementation guide, do not send.
CODE
DEFINITION
A
Concentrator
B
Liquid Stationary
C
Gaseous Stationary
D
Liquid Portable
E
Gaseous Portable
O
Other
Situational
5
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
SEMANTIC: CR505 is the reason for equipment.
SITUATIONAL RULE: Required when needed to provide additional information that could impact the medical decision. If not required by this implementation guide, do not send.
INDUSTRY NAME: Equipment Reason Description
Required
6
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: CR506 is the oxygen flow rate in liters per minute.
INDUSTRY NAME: Oxygen Flow Rate
Situational
7
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: CR507 is the number of times per day the patient must use oxygen.
SITUATIONAL RULE: Required when daily oxygen use count is relevant to the type of home oxygen therapy identified. If not required by this implementation guide, do not send.
INDUSTRY NAME: Daily Oxygen Use Count
Situational
8
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: CR508 is the number of hours per period of oxygen use.
SITUATIONAL RULE: Required when daily oxygen use count is relevant to the type of home oxygen therapy identified. If not required by this implementation guide, do not send.
INDUSTRY NAME: Oxygen Use Period Hour Count
Situational
9
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
SEMANTIC: CR509 is the special orders for the respiratory therapist.
SITUATIONAL RULE: Required when necessary to convey special orders for the respiratory therapist. If not required by this implementation guide, do not send.
INDUSTRY NAME: Respiratory Therapist Order Text
Situational
10
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: CR510 is the arterial blood gas.
SITUATIONAL RULE: Required when arterial blood gas quantity is relevant to the type of home oxygen therapy requested. If not required by this implementation guide, do not send.
INDUSTRY NAME: Arterial Blood Gas Quantity
Either CR510 or CR511 is required.
Situational
11
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: CR511 is the oxygen saturation.
SITUATIONAL RULE: Required when arterial blood gas quantity is relevant to the type of home oxygen therapy requested. If not required by this implementation guide, do not send.
INDUSTRY NAME: Oxygen Saturation Quantity
Either CR510 or CR511 is required.
Situational
12
1349
Oxygen Test Condition Code
O 1
ID
1
Code indicating the conditions under which a patient was tested
SITUATIONAL RULE: Required when reporting oxygen test results. If not required by this implementation guide, do not send.
CODE
DEFINITION
E
Exercising
N
No special conditions for test
O
On oxygen
R
At rest on room air
S
Sleeping
W
Walking
X
Other
Situational
13
1350
Oxygen Test Findings Code
O 1
ID
1
Code indicating the findings of oxygen tests performed on a patient
SITUATIONAL RULE: Required when patient's arterial PO2 is greater than 55 mmHg and less than 60 mmHg, or oxygen saturation is greater than 88%. If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Dependent edema suggesting congestive heart failure
2
"P" Pulmonale on Electrocardiogram (EKG)
3
Erythrocythemia with a hematocrit greater than 56 percent
Situational
14
1350
Oxygen Test Findings Code
O 1
ID
1
Code indicating the findings of oxygen tests performed on a patient
SITUATIONAL RULE: Required when patient's arterial PO2 is greater than 55 mmHg and less than 60 mmHg, or oxygen saturation is greater than 88%, and more than one finding is applicable. If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Dependent edema suggesting congestive heart failure
2
"P" Pulmonale on Electrocardiogram (EKG)
3
Erythrocythemia with a hematocrit greater than 56 percent
Situational
15
1350
Oxygen Test Findings Code
O 1
ID
1
Code indicating the findings of oxygen tests performed on a patient
SITUATIONAL RULE: Required when patient's arterial PO2 is greater than 55 mmHg and less than 60 mmHg, or oxygen saturation is greater than 88%, and more than two findings are applicable. If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Dependent edema suggesting congestive heart failure
2
"P" Pulmonale on Electrocardiogram (EKG)
3
Erythrocythemia with a hematocrit greater than 56 percent
Situational
16
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: CR516 is the oxygen flow rate for a portable oxygen system in liters per minute.
SITUATIONAL RULE: Required when either CR503, CR504 or CR518 = "D" (Liquid Portable) or "E" (Gaseous Portable). If not required by this implementation guide, do not send.
INDUSTRY NAME: Portable Oxygen System Flow Rate
Required
17
1382
Oxygen Delivery System Code
O 1
ID
1
Code to indicate if a particular form of delivery was prescribed
CODE
DEFINITION
A
Nasal Cannula
B
Oxygen Conserving Device
C
Oxygen Conserving Device with Oxygen Pulse System
D
Oxygen Conserving Device with Reservoir System
E
Transtracheal Catheter
Situational
18
1348
Oxygen Equipment Type Code
O 1
ID
1
Code indicating the specific type of equipment being prescribed for the delivery of oxygen
SITUATIONAL RULE: Required when CR503 and CR504 are present and more than two types of equipment are required to administer the oxygen therapy. If not required by this implementation guide, do not send.
CODE
DEFINITION
A
Concentrator
B
Liquid Stationary
C
Gaseous Stationary
D
Liquid Portable
E
Gaseous Portable
O
Other

CR6 - HOME HEALTH CARE INFORMATION

X12 Name:
Home Health Care Certification
X12 Purpose:
To supply information related to the certification of a home health care patient
X12 Syntax:
  1. P0304
    If either CR603 or CR604 is present, then the other is required.
  2. P091011
    If either CR609, CR610 or CR611 are present, then the others are required.
  3. P151617
    If either CR615, CR616 or CR617 are present, then the others are required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when requesting for certification of home health care, private duty nursing, or services by a nurses' agency. If not required by this implementation guide, do not send.
TR3 Notes:
Requests for home health care must include a principal diagnosis (HI01 = BK) and principal diagnosis date in the HI segment in Loop 2000E, Patient Event.
TR3 Example:
CR6✱7✱20111004✱✱✱✱✱N✱I~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
923
Prognosis Code
M 1
ID
1
Code indicating physician's prognosis for the patient
CODE
DEFINITION
1
Poor
2
Guarded
3
Fair
4
Good
5
Very Good
6
Excellent
7
Less than 6 Months to Live
8
Terminal
Required
2
373
Date
M 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: CR602 is the date covered home health services began.
INDUSTRY NAME: Home Health Start Date
Situational
3
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEGMENT SYNTAX: P0304
SITUATIONAL RULE: Required when the event date has not been identified in DTP, Event Date in this loop and the duration of this plan of treatment is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
RD8
Range of Dates Expressed in Format CCYYMMDD-CCYYMMDD
Situational
4
1251
Date Time Period
X 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
SEMANTIC: CR604 is the certification period covered by this plan of treatment.
SEGMENT SYNTAX: P0304
SITUATIONAL RULE: Required when the event date has not been identified in DTP, Event Date in this loop and the duration of this plan of treatment is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Home Health Certification Period
Not Used
5
373
Date
O 1
DT
8
Not Used
6
1073
Yes/No Condition or Response Code
O 1
ID
1
Required
7
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: CR607 indicates if the patient is covered by Medicare. A "Y" value indicates the patient is covered by Medicare; an "N" value indicates patient is not covered by Medicare.
INDUSTRY NAME: Medicare Coverage Indicator
CODE
DEFINITION
W
Not Applicable
Required
8
1322
Certification Type Code
M 1
ID
1
Code indicating the type of certification
This element must have the same value as UM02.
CODE
DEFINITION
1
Appeal - Immediate
2
Appeal - Standard
3
Cancel
4
Extension
I
Initial
N
Reconsideration
R
Renewal
S
Revised
Situational
9
373
Date
X 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: CR609 is the date that the surgery identified in CR611 was performed.
SEGMENT SYNTAX: P091011
SITUATIONAL RULE: Required when home health care is related to a specific surgical procedure, the surgery date is known, and the surgical procedure code is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Surgery Date
Situational
10
235
Product/Service ID Qualifier
X 1
ID
2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
SEMANTIC: CR610 qualifies CR611.
SEGMENT SYNTAX: P091011
SITUATIONAL RULE: Required when home health care is related to a specific surgical procedure, the surgery date is known, and the surgical procedure code is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Product or Service ID Qualifier
CODE
DEFINITION
HC
Healthcare Common Procedure Coding System (HCPCS) Codes
Because the AMA's CPT codes are also level 1 HCPCS codes, they are reported under HC. HCPCS consists of codes from multiple sources including AMA's CPT codes and ADA's CDT codes.
CODE SOURCE: 130: Healthcare Common Procedure Coding System
ID
International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM) - Procedure
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
IP
International Classification of Diseases, 10th Revision, Procedure Coding System (ICD-10-PCS)
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 896: International Classification of Diseases, 10th Revision, Procedure Coding System (ICD-10-PCS)
Situational
11
1137
Medical Code Value
X 1
AN
1/15
Code value for describing a medical condition or procedure
SEMANTIC: CR611 is the surgical procedure most relevant to the care being rendered.
SEGMENT SYNTAX: P091011
SITUATIONAL RULE: Required when home health care is related to a specific surgical procedure, the surgery date is known, and the surgical procedure code is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Surgical Procedure Code
Situational
12
373
Date
O 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: CR612 is the date the agency received the verbal orders from the physician for start of care.
SITUATIONAL RULE: Required when the requester received verbal orders from the physician for the start of home health care and the date when the order was received is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Physician Order Date
Situational
13
373
Date
O 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: CR613 is the date that the patient was last seen by the physician.
SITUATIONAL RULE: Required when the date the patient was last seen by the physician is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Last Visit Date
Situational
14
373
Date
O 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: CR614 is the date of the home health agency's most recent contact with the physician.
SITUATIONAL RULE: Required when the physician has been contacted by the home health service provider. If not required by this implementation guide, do not send.
INDUSTRY NAME: Physician Contact Date
Situational
15
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEGMENT SYNTAX: P151617
SITUATIONAL RULE: Required when home health care is associated with a recent inpatient stay, the admission stay date is known, and the facility type is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
RD8
Range of Dates Expressed in Format CCYYMMDD-CCYYMMDD
Situational
16
1251
Date Time Period
X 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
SEMANTIC: CR616 is the date range of the most recent inpatient stay.
SEGMENT SYNTAX: P151617
SITUATIONAL RULE: Required when home health care is associated with a recent inpatient stay, the admission stay date is known, and the facility type is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Last Admission Period
Situational
17
1384
Patient Location Code
X 1
ID
1
Code identifying the location where patient is receiving medical treatment
SEMANTIC: CR617 indicates the type of facility from which the patient was most recently discharged.
SEGMENT SYNTAX: P151617
SITUATIONAL RULE: Required when home health care is associated with a recent inpatient stay, the admission stay date is known, and the facility type is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
A
Acute Care Facility
B
Boarding Home
C
Hospice
D
Intermediate Care Facility
E
Long-term or Extended Care Facility
F
Not Specified
G
Nursing Home
H
Sub-acute Care Facility
L
Other Location
M
Rehabilitation Facility
O
Outpatient Facility
P
Private Home
R
Residential Treatment Facility
S
Skilled Nursing Home
T
Rest Home
Not Used
18
373
Date
O 1
DT
8
Not Used
19
373
Date
O 1
DT
8
Not Used
20
373
Date
O 1
DT
8
Not Used
21
373
Date
O 1
DT
8

PWK - ADDITIONAL PATIENT INFORMATION

X12 Name:
Paperwork
X12 Purpose:
To identify the type or transmission or both of paperwork or supporting information
X12 Syntax:
  1. P0506
    If either PWK05 or PWK06 is present, then the other is required.
  2. P1011
    If either PWK10 or PWK11 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
10
Situational Rule:
Required when the requester has additional documentation (electronic, paper, or other medium) associated with this health care services review that applies to the service(s) requested in this Service loop, and the 278 request (ST-SE) does not support this information in its segments and data elements. If not required by this implementation guide, do not send.
TR3 Notes:
  1. This PWK segment is required to identify attachments that are sent electronically (PWK02 = EL) but are transmitted in another X12 functional group rather than by paper or other medium. PWK06 is used to identify the attached electronic documentation. The number in PWK06 would be referenced in the electronic attachment.
  2. The requester can also use this PWK segment to identify paperwork that is held at the provider's office and is available upon request by the UMO (or appropriate entity). Use code AA in PWK02 to convey this specific use of the PWK segment. See code note under PWK02, code AA.

    Refer to Section 1.11.5.1 for more information on using this PWK segment.
TR3 Example:
PWK✱OB✱BM✱✱✱AC✱DMN0012~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
755
Report Type Code
M 1
ID
2
Code indicating the title or contents of a document, report or supporting item
INDUSTRY NAME: Attachment Report Type Code
CODE
DEFINITION
03
Report Justifying Treatment Beyond Utilization Guidelines
04
Drugs Administered
05
Treatment Diagnosis
06
Initial Assessment
07
Functional Goals
Expected outcomes of rehabilitative services.
08
Plan of Treatment
09
Progress Report
10
Continued Treatment
11
Chemical Analysis
13
Certified Test Report
15
Justification for Admission
21
Recovery Plan
48
Social Security Benefit Letter
55
Rental Agreement
Use for medical or dental equipment rental.
59
Benefit Letter
77
Support Data for Verification
A3
Allergies/Sensitivities Document
A4
Autopsy Report
AM
Ambulance Certification
Information to support necessity of ambulance trip.
AS
Admission Summary
A brief patient summary; it lists the patient's chief complaints and the reasons for admitting the patient to the hospital.
AT
Purchase Order Attachment
Use for purchase of medical or dental equipment.
B2
Prescription
B3
Physician Order
BR
Benchmark Testing Results
BS
Baseline
BT
Blanket Test Results
CB
Chiropractic Justification
Lists the reasons chiropractic is just and appropriate treatment.
CK
Consent Form(s)
D2
Drug Profile Document
DA
Dental Models
DB
Durable Medical Equipment Prescription
DG
Diagnostic Report
DJ
Discharge Monitoring Report
DS
Discharge Summary
FM
Family Medical History Document
HC
Health Certificate
HR
Health Clinic Records
I5
Immunization Record
IR
State School Immunization Records
LA
Laboratory Results
M1
Medical Record Attachment
NN
Nursing Notes
OB
Operative Note
OC
Oxygen Content Averaging Report
OD
Orders and Treatments Document
OE
Objective Physical Examination (including vital signs) Document
OX
Oxygen Therapy Certification
P4
Pathology Report
P5
Patient Medical History Document
P6
Periodontal Charts
Required when using the PWK segment to provide missing teeth information.
P7
Periodontal Reports
PE
Parenteral or Enteral Certification
PN
Physical Therapy Notes
PO
Prosthetics or Orthotic Certification
PQ
Paramedical Results
PY
Physician's Report
PZ
Physical Therapy Certification
QC
Cause and Corrective Action Report
QR
Quality Report
RB
Radiology Films
RR
Radiology Reports
RT
Report of Tests and Analysis Report
RX
Renewable Oxygen Content Averaging Report
SG
Symptoms Document
V5
Death Notification
XP
Photographs
Required
2
756
Report Transmission Code
O 1
ID
1/2
Code defining timing, transmission method or format by which reports are to be sent
CODE
DEFINITION
AA
Available on Request at Provider Site
Required when using the PWK segment to provide missing teeth information.

Use when the paperwork is not being sent with the request at this time. It will be made available to the UMO (or approving entity) on request.
BM
By Mail
EL
Electronically Only
Use to indicate that the attachment is being transmitted in a separate X12 functional group.
EM
E-Mail
FT
File Transfer
FX
By Fax
VO
Voice
Use this for voicemail or phone communication.
Not Used
3
757
Report Copies Needed
O 1
N
1/2
Not Used
4
98
Entity Identifier Code
O 1
ID
2/3
Situational
5
66
Identification Code Qualifier
X 1
ID
1/2
Code designating the system/method of code structure used for Identification Code (67)
COMMENT: PWK05 and PWK06 may be used to identify the addressee by a code number.
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when PWK02 equals BM, EL, EM, FT or FX. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
CODE
DEFINITION
AC
Attachment Control Number
Situational
6
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when PWK02 equals BM, EL, EM, FT or FX. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
INDUSTRY NAME: Attachment Control Number
The requester can use it when PWK02 equals "AA" if the requester wants to send a document control number for an attachment remaining at the Provider's office.
Situational
7
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
COMMENT: PWK07 may be used to indicate special information to be shown on the specified report.
SITUATIONAL RULE: Required when needed to add any additional information about the attachment described in this segment. If not required by this implementation guide, do not send.
INDUSTRY NAME: Attachment Description
To report tooth number(s) for missing teeth, use a variable length format. Allocate two (2) bytes for each missing tooth. When reporting tooth numbers 1 through 9, zero fill the first byte so the field will be 01, 02, etc. When reporting primary dentition (A through P), pad the second byte with a space.
Not Used
8
C002
Actions Indicated
O 1
Not Used
9
1525
Request Category Code
O 1
ID
1/2
Not Used
10
1270
Code List Qualifier Code
X 1
ID
1/3
Not Used
11
1271
Industry Code
X 1
AN
1/30

MSG - MESSAGE TEXT

X12 Name:
Message Text
X12 Purpose:
To provide a free-form format that allows the transmission of text information
X12 Syntax:
C0302
If MSG03 is present, then MSG02 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when needed to transmit a text message to the UMO about the patient event. If not required by this implementation guide, do not send.
TR3 Notes:
Do not use the MSG segment to relay information that you can send using codified information in existing data elements. If you need to use the MSG segment, you should approach X12N with data maintenance to solve the business need without the use of the MSG segment.
TR3 Example:
MSG✱This is a free-form text message~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
933
Free-form Message Text
M 1
AN
1/264
Free-form message text
INDUSTRY NAME: Free Form Message Text
Not Used
2
934
Printer Carriage Control Code
X 1
ID
2
Not Used
3
1470
Number
O 1
N
1/9

NM1 - PATIENT EVENT 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:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when loop 2000E UM01 = AR (Admission Review) or when loop 2000F is not valued or when loop 2000F is valued and at least one occurrence of loop 2000F does not contain a 2010F loop. If not required by this implementation guide, do not send.
TR3 Notes:
  1. If Loop 2000F is not valued, this segment conveys the name and identification number of the service provider (person, group, or facility) specialist, or specialty entity to provide services to the patient for this patient event.
  2. If Loop 2000F is valued, the providers identified in this Loop 2010EA apply to all the services identified in Loop 2000F unless Loop 2010F is valued. Providers identified in Loop 2010F override the providers identified in Loop 2010EA for that service only.
TR3 Example:
NM1✱SJ✱1✱WATSON✱SUSAN✱✱✱✱XX✱1234567890~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
71
Attending Physician
72
Operating Physician
73
Other Physician
77
Service Location
AAJ
Admitting Services
Use this value to identify the admitting provider.
DD
Assistant Surgeon
DK
Ordering Physician
DN
Referring Provider
Do not use if the entity identified in 2010B is the referring provider.
FA
Facility
G3
Clinic
P3
Primary Care Provider
QB
Purchase Service Provider
QV
Group Practice
SJ
Service Provider
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
2
Non-Person Entity
Situational
3
1035
Name Last or Organization Name
X 1
AN
1/60
Individual last name or organizational name
SEGMENT SYNTAX: C1203
SITUATIONAL RULE: Required when identifying a specific person, facility, group practice, or clinic and NM108/NM109 are not present. Not used if identifying a specialty entity utilizing the PRV segment. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when the service provider is a specific person (NM102 = 1) and NM103 is present. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when NM104 is present and the middle name/initial of the person is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider Middle Name
Situational
6
1038
Name Prefix
O 1
AN
1/10
Prefix to individual name
SITUATIONAL RULE: Required when military title or rank further identifies the provider. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider Name Prefix
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when NM104 is valued and the suffix of the individual's name is known; e.g. Sr., Jr., or III. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider Name Suffix
Situational
8
66
Identification Code Qualifier
X 1
ID
1/2
Code designating the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when requesting the services of a specific person, facility, group practice, or clinic and the provider ID is known by the requester. If not required by this implementation guide, do not send.
CODE
DEFINITION
XX
Centers for Medicare and Medicaid Services National Provider Identifier
Required for providers in the United States or its territories when the provider is eligible to receive a National Provider Identifier (NPI).

OR

Required for providers not in the United States or its territories when the provider has received an NPI. If not required by this implementation guide, do not send.
CODE SOURCE: 537: Centers for Medicare & Medicaid Services National Provider Identifier
Situational
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when requesting the services of a specific person, facility, group practice, or clinic and the provider ID is known by the requester. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/60

REF - PATIENT EVENT PROVIDER SUPPLEMENTAL 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:
8
Situational Rule:
Required when NM109 of this loop is not used and an identifier is necessary for the receiver to identify the provider. If not required by this implementation guide, do not send.
TR3 Notes:
Use the NM108 and NM109 in the corresponding NM1 segment for the NPI identifier and number.
TR3 Example:
REF✱ZH✱A12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
0B
State License Number
1J
Facility ID Number
EI
Employer's Identification Number
G5
Provider Site Number
N5
Provider Plan Network Identification Number
N7
Facility Network Identification Number
SY
Social Security Number
The social security number must not be used for any Federally administered programs such as Medicare or CHAMPUS.
ZH
Carrier Assigned Reference Number
Use when the requestor has not been assigned an NPI, or NPI is not mandated for use and the UMO identified in loop 2010AA or 2010AB has assigned its own identifier for this provider.
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Patient Event Provider Supplemental Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Situational
3
352
Description
X 1
AN
1/80
A free-form description to clarify the related data elements and their content
SEGMENT SYNTAX: R0203
SITUATIONAL RULE: Required when REF01 = 0B to report the two character state ID of the state assigning the State License Number. If not required by this implementation guide, do not send.
INDUSTRY NAME: License Number State Code
Not Used
4
C040
Reference Identifier
O 1

N3 - PATIENT EVENT PROVIDER ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the provider has multiple locations and a specific location for this patient event needs to be identified. If not required by this implementation guide, do not send.
TR3 Example:
N3✱123 MAIN STREET~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Patient Event Provider Address Line
Use this element for the first line of the provider's address.
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when a second address line is needed. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider Address Line

N4 - PATIENT EVENT PROVIDER CITY, STATE, ZIP CODE

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

PER*IC - PATIENT EVENT PROVIDER CONTACT INFORMATION

X12 Name:
Administrative Communications Contact
X12 Purpose:
To identify a person or office to whom administrative communications should be directed
X12 Syntax:
  1. P0304
    If either PER03 or PER04 is present, then the other is required.
  2. P0506
    If either PER05 or PER06 is present, then the other is required.
  3. P0708
    If either PER07 or PER08 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
2
Situational Rule:
Required when needed to identify a contact name and/or communication number for the provider. If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver.
TR3 Notes:
When the communication number represents a telephone number in the United States and other countries using the North American Dialing Plan (for voice, data, fax, etc.), the communication number must always include the area code and phone number using the format AAABBBCCCC where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number. Therefore, the following telephone number (555) 555-1234 would be represented as 5555551234. Do not submit long distance access numbers, such as 1, in the telephone number. Telephone extensions, when applicable, must be submitted in the next element immediately following the telephone number. When submitting telephone extensions, only submit the numeric extension, do not include data that indicates an extension, such as "ext" or "x-".
TR3 Example:
PER✱IC✱JOHN SMITH✱TE✱5555551234✱EX✱123~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
366
Contact Function Code
M 1
ID
2
Code identifying the major duty or responsibility of the person or group named
CODE
DEFINITION
IC
Information Contact
Situational
2
93
Name
O 1
AN
1/60
Free-form name
SITUATIONAL RULE: Required when the requester needs to indicate a particular contact. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider Contact Name
Use this data element when the name of the individual to contact is not already defined or is different than the name within the prior name segment (e.g. N1 or NM1). If not required, do not send.
Situational
3
365
Communication Number Qualifier
X 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0304
SITUATIONAL RULE: Required when PER02 is not valued, or to transmit a contact communication number. If not required by this implementation guide, do not send.
CODE
DEFINITION
EM
Electronic Mail
FX
Facsimile
TE
Telephone
UR
Uniform Resource Locator (URL)
Situational
4
364
Communication Number
X 1
AN
1/256
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0304
SITUATIONAL RULE: Required when PER02 is not valued, or to transmit a contact communication number. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider Contact Communication Number
Situational
5
365
Communication Number Qualifier
X 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
EM
Electronic Mail
EX
Telephone Extension
When used, the value following this code is the extension for the preceding communications contact number.
FX
Facsimile
TE
Telephone
UR
Uniform Resource Locator (URL)
Situational
6
364
Communication Number
X 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: Patient Event Provider Contact Communication Number
Situational
7
365
Communication Number Qualifier
X 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
EM
Electronic Mail
EX
Telephone Extension
When used, the value following this code is the extension for the preceding communications contact number.
FX
Facsimile
TE
Telephone
UR
Uniform Resource Locator (URL)
Situational
8
364
Communication Number
X 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: Patient Event Provider Contact Communication Number
Not Used
9
443
Contact Inquiry Reference
O 1
AN
1/20

PRV - PATIENT EVENT PROVIDER INFORMATION

X12 Name:
Provider Information
X12 Purpose:
To specify the identifying characteristics of a provider
X12 Syntax:
P0203
If either PRV02 or PRV03 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when request is for services of a specialist or specialty entity to indicate the provider's specialty. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
TR3 Example:
PRV✱PE✱PXC✱208D00000X~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1221
Provider Code
M 1
ID
1/3
Code identifying the type of provider
CODE
DEFINITION
AD
Admitting
Use only when NM101 = AAJ.
AS
Assistant Surgeon
Use only when NM101 = DD.
AT
Attending
Use only when NM101 = 71.
OP
Operating
Use only when NM101 = 72.
OR
Ordering
Use only when NM101 = DK.
OT
Other Physician
Use only when NM101 = 73.
PC
Primary Care Physician
Use only when NM101 = P3.
PE
Performing
Use only when NM101 = SJ.
RF
Referring
Use only when NM101 = DN.
Required
2
128
Reference Identification Qualifier
X 1
ID
2/3
Code qualifying the Reference Identification
SEGMENT SYNTAX: P0203
CODE
DEFINITION
PXC
Health Care Provider Taxonomy Code
CODE SOURCE: 682: Health Care Provider Taxonomy
Required
3
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: P0203
INDUSTRY NAME: Provider Taxonomy Code
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
4
156
State or Province Code
O 1
ID
2
Not Used
5
C035
Provider Specialty Information
O 1
Not Used
6
1223
Provider Organization Code
O 1
ID
3

NM1 - PATIENT EVENT TRANSPORT INFORMATION

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:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when requesting transport of the patient. If not required by this implementation guide, do not send.
TR3 Notes:
  1. At least two iterations of this loop are necessary to indicate the pick up address, NM101 = PW, and the final scheduled destination, NM101 = FS.
  2. When the transport includes more than one destination, the following NM101 values are used to determine the sequence of stops:
    a. ND is used to indicate the first stop
    b. R3 is used to indicate the second stop
    c. 45 is used to indicate the third stop
TR3 Example:
  1. NM1✱PW✱2✱PATIENT DIALYSIS CENT~
  2. NM1✱FS✱2~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
45
Drop-off Location
FS
Final Scheduled Destination
ND
Next Destination
PW
Pickup Address
R3
Next Scheduled Destination
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
2
Non-Person Entity
Situational
3
1035
Name Last or Organization Name
X 1
AN
1/60
Individual last name or organizational name
SEGMENT SYNTAX: C1203
SITUATIONAL RULE: Required when the name of the location for which the patient is being transported is known. If not required by this implementation, do not send.
INDUSTRY NAME: Patient Event Transport Location Name
Not Used
4
1036
Name First
O 1
AN
1/35
Not Used
5
1037
Name Middle
O 1
AN
1/25
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Not Used
7
1039
Name Suffix
O 1
AN
1/10
Not Used
8
66
Identification Code Qualifier
X 1
ID
1/2
Not Used
9
67
Identification Code
X 1
AN
2/80
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/60

N3 - PATIENT EVENT TRANSPORT LOCATION ADDRESS

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

N4 - PATIENT EVENT TRANSPORT LOCATION CITY/STATE/ZIP CODE

X12 Name:
Geographic Location
X12 Purpose:
To specify the geographic place of the named party
X12 Syntax:
  1. E0207
    Only one of N402 or N407 may be present.
  2. C0605
    If N406 is present, then N405 is required.
  3. C0704
    If N407 is present, then N404 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
N4✱KANSAS CITY✱MO✱64108~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Situational
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
SITUATIONAL RULE: Required when N403 is not valued. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
INDUSTRY NAME: Patient Event Transport Location City Name
Situational
2
156
State or Province Code
X 1
ID
2
Code (Standard State/Province) as defined by appropriate government agency
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when N403 is not valued. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
INDUSTRY NAME: Patient Event Transport Location State or Province Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
O 1
ID
3/15
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
SITUATIONAL RULE: Required when N401 and N402 are not valued. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
INDUSTRY NAME: Patient Event Transport Location Postal Zone or ZIP Code
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Not Used
4
26
Country Code
X 1
ID
2/3
Not Used
5
309
Location Qualifier
X 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Not Used
7
1715
Country Subdivision Code
X 1
ID
1/3

NM1 - PATIENT EVENT OTHER UMO 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:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when Health Care Services Review has been denied by another UMO. If not required by this implementation guide, do not send.
TR3 Example:
NM1✱CA✱2~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
00
Alternate Insurer
Use this code to indicate that the other UMO is commercial insurance.
CA
Carrier
Use this code to indicate that the other UMO is Medicare Part B.
GG
Intermediary
Use this code to indicate that the other UMO is Medicare Part A.
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
2
Non-Person Entity
Situational
3
1035
Name Last or Organization Name
X 1
AN
1/60
Individual last name or organizational name
SEGMENT SYNTAX: C1203
SITUATIONAL RULE: Required when NM101 is equal to "00" to indicate the name of the other UMO. If not required by this implementation guide, do not send.
INDUSTRY NAME: Other UMO Name
Not Used
4
1036
Name First
O 1
AN
1/35
Not Used
5
1037
Name Middle
O 1
AN
1/25
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Not Used
7
1039
Name Suffix
O 1
AN
1/10
Not Used
8
66
Identification Code Qualifier
X 1
ID
1/2
Not Used
9
67
Identification Code
X 1
AN
2/80
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/60

REF*ZZ - OTHER UMO DENIAL REASON

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
REF✱ZZ✱0M~
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
ZZ
Mutually Defined
Use ZZ to indicate Health Care Service Review Decision Reason Code from Code Source 886.
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Other UMO Denial Reason
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Situational
4
C040
Reference Identifier
O 1
To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier
SEMANTIC: REF04 contains data relating to the value cited in REF02.
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C04003 or C04004 is present, then the other is required.
  2. P0506
    If either C04005 or C04006 is present, then the other is required.
SITUATIONAL RULE: Required when the Health Care Services Review was denied by other UMO for more than one reason. If not required by this implementation guide, do not send.
Required
4-1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
ZZ
Mutually Defined
Use ZZ to indicate Health Care Service Review Decision Reason Code from Code Source 886.
Required
4-2
127
Reference Identification
M 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
INDUSTRY NAME: Other UMO Denial Reason
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Situational
4-3
128
Reference Identification Qualifier
X 1
ID
2/3
Code qualifying the Reference Identification
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the other UMO denied the request for more than two reasons. If not required by this implementation guide, do not send.
CODE
DEFINITION
ZZ
Mutually Defined
Use ZZ to indicate Health Care Service Review Decision Reason Code from Code Source 886.
Situational
4-4
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
COMPOSITE SYNTAX: P0304
SITUATIONAL RULE: Required when the other UMO denied the request for more than two reasons. If not required by this implementation guide, do not send.
INDUSTRY NAME: Other UMO Denial Reason
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Situational
4-5
128
Reference Identification Qualifier
X 1
ID
2/3
Code qualifying the Reference Identification
COMPOSITE SYNTAX: P0506
SITUATIONAL RULE: Required when the other UMO denied the request for more than three reasons. If not required by this implementation guide, do not send.
CODE
DEFINITION
ZZ
Mutually Defined
Use ZZ to indicate Health Care Service Review Decision Reason Code from Code Source 886.
Situational
4-6
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
COMPOSITE SYNTAX: P0506
SITUATIONAL RULE: Required when the other UMO denied the request for more than three reasons. If not required by this implementation guide, do not send.
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.

DTP*598 - OTHER UMO DENIAL 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✱598✱D8✱20110930~
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
598
Rejected
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Other UMO Denial Date

HL - SERVICE 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 specific services are associated with this patient event. If not required by this implementation guide, do not send.
TR3 Example:
HL✱6✱5✱SS✱0~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
628
Hierarchical ID Number
M 1
AN
1/12
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
COMMENT: HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Required
2
734
Hierarchical Parent ID Number
O 1
AN
1/12
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
COMMENT: HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Required
3
735
Hierarchical Level Code
M 1
ID
1/2
Code defining the characteristic of a level in a hierarchical structure
COMMENT: HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
CODE
DEFINITION
SS
Services
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.

TRN*1 - SERVICE TRACE NUMBER

X12 Name:
Trace
X12 Purpose:
To uniquely identify a transaction to an application
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
2
Situational Rule:
Required when the requester needs to assign a unique trace number to the service line request. If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver.
TR3 Notes:
  1. This enables the requester to
    • uniquely identify this service line request
    • trace the request
    • match the response to the request
    • reference this request in any associated attachments containing additional service information related to this service line request.
  2. If the transaction is routed through a clearinghouse, the clearinghouse may add their own TRN segment. If the transaction passes through multiple clearinghouses, and the second clearinghouse needs to assign their own TRN segment, they must replace the TRN from the first clearinghouse and retain it to be returned in the 278 response. If the second clearinghouse does not need to assign a TRN segment, they should pass all received TRN segments.
  3. Each trace number provided in the TRN segment at this level on the request must be returned by the UMO in the TRN segment at the corresponding level of the response.
  4. If the request contains more than one occurrence of Loop 2000F and the requester needs to uniquely identify each service level request this TRN segment is required in each Service loop.
TR3 Example:
TRN✱1✱111099✱9012345678✱RADIOLOGY~
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/80
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: Service Trace Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Required
3
509
Originating Company Identifier
O 1
AN
10
A unique identifier designating the company initiating the funds transfer instructions, business transaction or assigning tracking reference identification.
SEMANTIC: TRN03 identifies an organization.
INDUSTRY NAME: Trace Assigning Entity Identifier
  1. Use this element to identify the organization that assigned this trace number. TRN03 must be completed to aid requesters and clearinghouses in identifying their TRN in the 278 response.
  2. The first position must be either a "1" if an EIN is used, a "3" if a DUNS is used, or a "9" if a user assigned identifier is used.
Situational
4
127
Reference Identification
O 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: TRN04 identifies a further subdivision within the organization.
SITUATIONAL RULE: Required when a specific division or group of the company identified in the previous data element (TRN03) is needed by the requester to further identify a specific component of the entity. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
INDUSTRY NAME: Trace Assigning Entity Additional Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.

UM - HEALTH CARE SERVICES REVIEW INFORMATION

X12 Name:
Health Care Services Review Information
X12 Purpose:
To specify health care services review information
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the health care services review information for this service differs from the health care services review information specified in the UM segment at the Patient Event level (Loop 2000E). If not required by this implementation guide, do not send.
TR3 Example:
UM✱SC✱I✱3~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1525
Request Category Code
M 1
ID
1/2
Code indicating a type of request
CODE
DEFINITION
HS
Health Services Review
Required if requesting a review of services related to an episode of care.
SC
Specialty Care Review
Required if requesting a referral to a specialty provider.
Situational
2
1322
Certification Type Code
O 1
ID
1
Code indicating the type of certification
SITUATIONAL RULE: Required when different from the UM02 value at the Patient Event level (Loop 2000E). If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Appeal - Immediate
Use this value to identify appeals of review decisions where the service required was emergency or urgent.
2
Appeal - Standard
Use this value to identify appeals of review decisions where the service required was not emergency or urgent.
3
Cancel
4
Extension
Use this when requesting additional service units and/or the duration of time for a prior approved service.
I
Initial
N
Reconsideration
R
Renewal
Various services, such as physical therapy, spinal manipulation, and allergy treatment, have both a delivery pattern and a time span of authorization. Many UMOs place time limits - as in will not authorize anything for more than 30 days at a time. For example, blanket authorization for allergy treatments as required for 30 days. At the end of the 30 days, the provider must request to renew the certification - not extend it - because the UMO authorizes for 30 day intervals, one interval at a time.
S
Revised
Use if the requester is changing the specifics of a previously submitted request for which services have not been rendered.
Situational
3
1271
Industry Code
O 1
AN
1/30
Code indicating a code from a specific industry code list
SEMANTIC: UM03 is the Service Type (Code Source 958).
SITUATIONAL RULE: Required when different from the UM03 value at the Patient Event level (Loop 2000E) or when SV1, SV2, or SV3 is not valued in this Service loop. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.Values at the Service Level override the values entered at the Patient Event Level for this service.
INDUSTRY NAME: Service Type Code
Situational
4
C023
Health Care Service Location Information
O 1
To provide information that identifies the place of service or the type of bill related to the location at which a health care service was rendered
X12 COMPOSITE SEMANTIC NOTES:
  1. C023-01 does not contain the last position of the Uniform Bill Type Code (the Claim Frequency Code).
  2. C023-02 qualifies C023-01.
SITUATIONAL RULE: Required when different from the UM04 value at the Patient Event level (Loop 2000E). If not required by this implementation guide, do not send.
For this service, values at the Service Level override values at the Patient Event Level.
Required
4-1
1331
Facility Code Value
M 1
AN
1/3
Code identifying where services were, or may be, performed; the National Uniform Billing Committee (NUBC) Facility Type Code for Institutional Services or the Place of Service Codes for Professional or Dental Services.
INDUSTRY NAME: Facility Type Code
Use to indicate a facility code value from the code source referenced in UM04-02.
Required
4-2
1332
Facility Code Qualifier
M 1
ID
1/2
Code identifying the type of facility referenced
CODE
DEFINITION
A
Uniform Billing Claim Form Bill Type
CODE SOURCE: 236: Uniform Billing Claim Form Bill Type
B
Place of Service Codes for Professional or Dental Services
CODE SOURCE: 237: Place of Service Codes for Professional Claims
Not Used
4-3
1325
Claim Frequency Type Code
O 1
ID
1
Not Used
5
C024
Related Causes Information
O 1
Not Used
6
1338
Level of Service Code
O 1
ID
1/3
Not Used
7
1213
Current Health Condition Code
O 1
ID
1
Not Used
8
923
Prognosis Code
O 1
ID
1
Not Used
9
1363
Release of Information Code
O 1
ID
1
Not Used
10
1514
Delay Reason Code
O 1
ID
1/2

REF*BB - PREVIOUS REVIEW AUTHORIZATION NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when different from the Previous Review Authorization Number specified at the Patient Event Level (Loop 2000E). If not required by this implementation guide, do not send.
TR3 Notes:
This is the authorization number assigned by the UMO to the original review outcome associated with this service. This is not the trace number assigned by the requester.
TR3 Example:
REF✱BB✱A123~
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
BB
Authorization Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Previous Review Authorization Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*NT - PREVIOUS REVIEW ADMINISTRATIVE REFERENCE NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when different from the Previous Review Administrative Reference Number specified at the Patient Event Level (Loop 2000E). If not required by this implementation guide, do not send.
TR3 Notes:
This is the administrative number assigned by the UMO to the original service review outcome associated with this service review. This is not the trace number assigned by the requester.
TR3 Example:
REF✱NT✱123Z~
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
NT
Administrator's Reference Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Previous Administrative Reference Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

DTP*472 - SERVICE DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when proposed or actual date or range of dates of service is different from the Patient Event Date in Loop 2000E. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱472✱D8✱20111030~
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: Proposed or Actual Service Date

SV1 - PROFESSIONAL SERVICE

X12 Name:
Professional Service
X12 Purpose:
To specify the service line item detail for a health care professional
X12 Syntax:
P0304
If either SV103 or SV104 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when requesting a specific Professional Service. If not required by this implementation guide, do not send.
TR3 Example:
SV1✱HC:99211:25✱12.25✱UN✱1✱✱✱1:2:3✱✱✱✱N~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
C003
Composite Medical Procedure Identifier
M 1
To identify a medical procedure by its standardized codes and applicable modifiers
X12 COMPOSITE SEMANTIC NOTES:
  1. C003-01 qualifies C003-02 and C003-08.
  2. If C003-08 is used, then C003-02 represents the beginning value in the range in which the code occurs.
  3. C003-03 modifies the value in C003-02 and C003-08.
  4. C003-04 modifies the value in C003-02 and C003-08.
  5. C003-05 modifies the value in C003-02 and C003-08.
  6. C003-06 modifies the value in C003-02 and C003-08.
  7. C003-07 is the description of the procedure identified in C003-02.
  8. C003-08 represents the ending value in the range in which the code occurs.
  9. C003-09 modifies the value in C003-02 and C003-08.
  10. C003-10 modifies the value in C003-02 and C003-08.
  11. C003-11 modifies the value in C003-02 and C003-08.
  12. C003-12 modifies the value in C003-02 and C003-08.
Required
1-1
235
Product/Service ID Qualifier
M 1
ID
2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
INDUSTRY NAME: Product or Service ID Qualifier
CODE
DEFINITION
HC
Healthcare Common Procedure Coding System (HCPCS) Codes
Because the AMA's CPT codes are also level 1 HCPCS codes, they are reported under HC. HCPCS consists of codes from multiple sources including AMA's CPT codes and ADA's CDT codes.
CODE SOURCE: 130: Healthcare Common Procedure Coding System
N4
National Drug Code in 5-4-2 Format
CODE SOURCE: 240: National Drug Code by Format
WK
Advanced Billing Concepts (ABC) 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 Complimentary, Alternative, or Holistic Procedure 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 service reviews 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/80
Identifying number for a product or service
INDUSTRY NAME: Procedure Code
Situational
1-3
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
Use this modifier for the first procedure code modifier.
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 additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
Use this modifier for the second procedure code modifier.
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 additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
Use this modifier for the third procedure code modifier.
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 additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
Use this modifier for the fourth procedure code modifier.
Situational
1-7
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
SITUATIONAL RULE: Required when the provider needs to convey additional clarification to miscellaneous, unspecified, or non descriptive procedures or modifiers. If not required by this implementation guide, may be provider at the sender's discretion but cannot be required by the receiver.
INDUSTRY NAME: Procedure Code Description
Situational
1-8
234
Product/Service ID
O 1
AN
1/80
Identifying number for a product or service
SITUATIONAL RULE: Required when the requester cannot determine the intensity or complexity of the service to be performed and therefore requires authorization for a range of procedures. If not required by this implementation guide, do not send.
INDUSTRY NAME: Procedure Code
Use SV101-02 to represent the beginning value in a procedure range and this data element to represent the ending value in a range of codes.
Situational
1-9
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
Use this modifier for the fifth procedure code modifier.
Situational
1-10
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
Use this modifier for the sixth procedure code modifier.
Situational
1-11
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
Use this modifier for the seventh procedure code modifier.
Situational
1-12
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
Use this modifier for the eighth procedure code modifier.
Situational
2
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: SV102 is the submitted service line item amount.
SITUATIONAL RULE: Required when the procedure charge amount is necessary to approve a monetary limitation for the health care services requests. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Line Amount
Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
Situational
3
355
Unit or Basis for Measurement Code
X 1
ID
2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
SEGMENT SYNTAX: P0304
SITUATIONAL RULE: Required when service units were not provided in the HSD segment and a specific number of services are being requested for this procedure. If not required by this implementation guide, do not send.
CODE
DEFINITION
F2
International Unit
International Unit is used to indicate dosage amount. Dosage amount is only used for drug claims when the dosage of the drug is variable within a single NDC number (e.g., blood factors).
MJ
Minutes
UN
Unit
Situational
4
380
Quantity
X 1
R
1/15
Numeric value of quantity
SEGMENT SYNTAX: P0304
SITUATIONAL RULE: Required when service units were not provided in the HSD segment and a specific number of services are being requested for this procedure. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Unit Count
Not Used
5
1331
Facility Code Value
O 1
AN
1/3
Not Used
6
1271
Industry Code
O 1
AN
1/30
Situational
7
1328
Diagnosis Code Pointer
O 12
N
1/2
A pointer to the diagnosis code in the order of importance to this service
SEMANTIC: The first pointer designates the primary diagnosis and remaining diagnosis pointers indicate declining level of importance.
SITUATIONAL RULE: Required when this procedure relates to a specific diagnosis reported in the Loop 2000E HI - Patient Diagnosis segment to point to the specific diagnosis. If not required by this implementation guide, do not send.
This element is a repeating data element that may be repeated up to 12 times. The first pointer designates the primary diagnosis for this service line. Remaining diagnosis pointers indicate declining level of importance to service line.

Acceptable values are 1 through 12, and correspond to the HI01 through HI12 element number that holds the diagnosis values in the Event Loop (2000E).

If no diagnosis pointer is provided, then this procedure applies to all diagnosis.
Not Used
8
782
Monetary Amount
O 1
R
1/18
Not Used
9
1073
Yes/No Condition or Response Code
O 1
ID
1
Not Used
10
1340
Multiple Procedure Code
O 1
ID
1/2
Situational
11
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: SV111 is early and periodic screen for diagnosis and treatment of children (EPSDT) involvement; a "Y" value indicates EPSDT involvement; an "N" value indicates no EPSDT involvement.
SITUATIONAL RULE: Required when the requested service is based on EPSDT. If not required by this implementation guide, do not send.
INDUSTRY NAME: EPSDT Indicator
CODE
DEFINITION
N
No
Y
Yes
Not Used
12
1073
Yes/No Condition or Response Code
O 1
ID
1
Not Used
13
1364
Review Code
O 1
ID
1/2
Not Used
14
1341
National or Local Assigned Review Value
O 1
AN
1/2
Not Used
15
1327
Copay Status Code
O 1
ID
1
Not Used
16
1334
Health Care Professional Shortage Area Code
O 1
ID
1
Not Used
17
127
Reference Identification
O 1
AN
1/80
Not Used
18
116
Postal Code
O 1
ID
3/15
Not Used
19
782
Monetary Amount
O 1
R
1/18
Situational
20
1337
Level of Care Code
O 1
ID
1
Code specifying the level of care provided by a nursing home facility
SITUATIONAL RULE: Required when needed to further clarify the level of care in which a patient resides. If not required by this implementation guide, do not send.
INDUSTRY NAME: Nursing Home Level of Care
CODE
DEFINITION
1
Skilled Nursing Facility (SNF)
2
Intermediate Care Facility (ICF)
3
Intermediate Care Facility - Mentally Retarded (ICF-MR)
4
Chronic Disease Hospital (CD)
5
Intermediate Care Facility (ICF) Level II
6
Special Skilled Nursing Facility (SNF)
7
Nursing Facility (NF)
8
Hospice
Not Used
21
1360
Provider Agreement Code
O 1
ID
1

SV2 - INSTITUTIONAL SERVICE

X12 Name:
Institutional Service
X12 Purpose:
To specify the service line item detail for a health care institution
X12 Syntax:
  1. R0102
    At least one of SV201 or SV202 is required.
  2. P0405
    If either SV204 or SV205 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when requesting a specific Institutional Service or requesting a specific Revenue Code for the Institutional Service. If not required by this implementation guide, do not send.
TR3 Example:
  1. SV2✱120✱✱1500✱DA✱5✱300~
  2. SV2✱300✱HC:80019✱73.42✱UN✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Situational
1
234
Product/Service ID
X 1
AN
1/80
Identifying number for a product or service
SEMANTIC: SV201 is the revenue code.
SEGMENT SYNTAX: R0102
SITUATIONAL RULE: Required when requesting approval on a revenue code. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Line Revenue Code
See Code Source 132: National Uniform Billing Committee (NUBC) Codes.
Situational
2
C003
Composite Medical Procedure Identifier
X 1
To identify a medical procedure by its standardized codes and applicable modifiers
X12 COMPOSITE SEMANTIC NOTES:
  1. C003-01 qualifies C003-02 and C003-08.
  2. If C003-08 is used, then C003-02 represents the beginning value in the range in which the code occurs.
  3. C003-03 modifies the value in C003-02 and C003-08.
  4. C003-04 modifies the value in C003-02 and C003-08.
  5. C003-05 modifies the value in C003-02 and C003-08.
  6. C003-06 modifies the value in C003-02 and C003-08.
  7. C003-07 is the description of the procedure identified in C003-02.
  8. C003-08 represents the ending value in the range in which the code occurs.
  9. C003-09 modifies the value in C003-02 and C003-08.
  10. C003-10 modifies the value in C003-02 and C003-08.
  11. C003-11 modifies the value in C003-02 and C003-08.
  12. C003-12 modifies the value in C003-02 and C003-08.
SITUATIONAL RULE: Required when requesting approval for a specific procedure code. If not required by this implementation guide, do not send.
Required
2-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
HC
Healthcare Common Procedure Coding System (HCPCS) Codes
Because the AMA's CPT codes are also level 1 HCPCS codes, they are reported under HC. HCPCS consists of codes from multiple sources including AMA's CPT codes and ADA's CDT codes.
CODE SOURCE: 130: Healthcare Common Procedure Coding System
ID
International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM) - Procedure
CODE SOURCE: 131: International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM)
IP
International Classification of Diseases, 10th Revision, Procedure Coding System (ICD-10-PCS)
The ICD-10 code set and corresponding qualifier can only be used: On or after the mandated HIPAA implementation date or, when the Secretary grants an exception to use the code set as a pilot project as allowed under the law.
CODE SOURCE: 896: International Classification of Diseases, 10th Revision, Procedure Coding System (ICD-10-PCS)
N4
National Drug Code in 5-4-2 Format
CODE SOURCE: 240: National Drug Code by Format
WK
Advanced Billing Concepts (ABC) 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 Complimentary, Alternative, or Holistic Procedure 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 service reviews which are not covered under HIPAA.
CODE SOURCE: 843: Advanced Billing Concepts (ABC) Codes
Required
2-2
234
Product/Service ID
M 1
AN
1/80
Identifying number for a product or service
INDUSTRY NAME: Procedure Code
Situational
2-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 additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
Use this data element for the first procedure code modifier.
Situational
2-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 additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
Use this data element for the second procedure code modifier.
Situational
2-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 additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
Use this data element for the third procedure code modifier.
Situational
2-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 additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
Use this data element for the fourth procedure code modifier.
Situational
2-7
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
SITUATIONAL RULE: Required when the provider needs to convey additional clarification to miscellaneous, unspecified, or non descriptive procedures or modifiers. If not required by this implementation guide, may be provider at the sender's discretion but cannot be required by the receiver.
INDUSTRY NAME: Procedure Code Description
Situational
2-8
234
Product/Service ID
O 1
AN
1/80
Identifying number for a product or service
SITUATIONAL RULE: Required when the requester cannot determine the intensity or complexity of the service to be performed and therefore requires authorization for a range of procedures. If not required by this implementation guide, do not send.
INDUSTRY NAME: Procedure Code
Use SV202-02 to represent the beginning value in the procedure range and this data element to represent the ending value in a range of codes.
Situational
2-9
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
Use this modifier for the fifth procedure code modifier.
Situational
2-10
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
Use this modifier for the sixth procedure code modifier.
Situational
2-11
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
Use this modifier for the seventh procedure code modifier.
Situational
2-12
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
Use this modifier for the eighth procedure code modifier.
Situational
3
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: SV203 is the submitted service line item amount.
SITUATIONAL RULE: Required when the procedure charge amount is necessary to approve a monetary limitation for the health care services requests. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Line Amount
Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
Situational
4
355
Unit or Basis for Measurement Code
X 1
ID
2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
SEGMENT SYNTAX: P0405
SITUATIONAL RULE: Required when service units were not provided in the HSD segment and a specific number of services are being requested for this procedure. If not required by this implementation guide, do not send.
CODE
DEFINITION
DA
Days
F2
International Unit
Dosage amount is only used for drug claims when the dosage of the drug is variable within a single NDC number (e.g. blood factors).
UN
Unit
Situational
5
380
Quantity
X 1
R
1/15
Numeric value of quantity
SEGMENT SYNTAX: P0405
SITUATIONAL RULE: Required when service units were not provided in the HSD segment and a specific number of services are being requested for this procedure. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Unit Count
Situational
6
1371
Unit Rate
O 1
R
1/10
The rate per unit of associate revenue for hospital accommodation
SITUATIONAL RULE: Required when SV201 is valued and accommodation rate is necessary to approve a monetary limitation for the health care services requests. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Line Rate
Not Used
7
782
Monetary Amount
O 1
R
1/18
Not Used
8
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
9
1345
Nursing Home Residential Status Code
O 1
ID
1
Code specifying the status of a nursing home resident at the time of service
SITUATIONAL RULE: Required when the Health Care Services Review Request is for Long Term Care. If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Transferred to Intermediate Care Facility - Mentally Retarded (ICF-MR)
2
Newly Admitted
3
Newly Eligible
4
No Longer Eligible
5
Still a Resident
6
Temporary Absence - Hospital
7
Temporary Absence - Other
8
Transferred to Intermediate Care Facility - Level II (ICF II)
9
Other
Situational
10
1337
Level of Care Code
O 1
ID
1
Code specifying the level of care provided by a nursing home facility
SITUATIONAL RULE: Required when needed to further clarify the level of care being requested for admission to a nursing facility, or when the request is for non-nursing facility and the level of care in which the patient resides is needed. If not required by this implementation guide, do not send.
INDUSTRY NAME: Nursing Home Level of Care
CODE
DEFINITION
1
Skilled Nursing Facility (SNF)
2
Intermediate Care Facility (ICF)
3
Intermediate Care Facility - Mentally Retarded (ICF-MR)
4
Chronic Disease Hospital (CD)
5
Intermediate Care Facility (ICF) Level II
6
Special Skilled Nursing Facility (SNF)
7
Nursing Facility (NF)
8
Hospice

SV3 - DENTAL SERVICE

X12 Name:
Dental Service
X12 Purpose:
To specify the service line item detail for dental work
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when requesting a specific Dental Service. If not required by this implementation guide, do not send.
TR3 Example:
SV3✱AD:D2150✱80~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
C003
Composite Medical Procedure Identifier
M 1
To identify a medical procedure by its standardized codes and applicable modifiers
X12 COMPOSITE SEMANTIC NOTES:
  1. C003-01 qualifies C003-02 and C003-08.
  2. If C003-08 is used, then C003-02 represents the beginning value in the range in which the code occurs.
  3. C003-03 modifies the value in C003-02 and C003-08.
  4. C003-04 modifies the value in C003-02 and C003-08.
  5. C003-05 modifies the value in C003-02 and C003-08.
  6. C003-06 modifies the value in C003-02 and C003-08.
  7. C003-07 is the description of the procedure identified in C003-02.
  8. C003-08 represents the ending value in the range in which the code occurs.
  9. C003-09 modifies the value in C003-02 and C003-08.
  10. C003-10 modifies the value in C003-02 and C003-08.
  11. C003-11 modifies the value in C003-02 and C003-08.
  12. C003-12 modifies the value in C003-02 and C003-08.
Required
1-1
235
Product/Service ID Qualifier
M 1
ID
2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
INDUSTRY NAME: Product or Service ID Qualifier
CODE
DEFINITION
AD
American Dental Association Codes
CDT = Current Dental Terminology
CODE SOURCE: 135: American Dental Association
Required
1-2
234
Product/Service ID
M 1
AN
1/80
Identifying number for a product or service
INDUSTRY NAME: Procedure Code
Situational
1-3
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
  1. A modifier must be from code source 135 (American Dental Association) found in the `Code on Dental Procedures and Nomenclature'.
  2. Use this data element for the first procedure code modifier.
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 additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
  1. A modifier must be from code source 135 (American Dental Association) found in the `Code on Dental Procedures and Nomenclature'.
  2. Use this data element for the second procedure code modifier.
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 additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
  1. A modifier must be from code source 135 (American Dental Association) found in the `Code on Dental Procedures and Nomenclature'.
  2. Use this data element for the third procedure code modifier.
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 additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
  1. A modifier must be from code source 135 (American Dental Association) found in the `Code on Dental Procedures and Nomenclature'.
  2. Use this data element for the fourth procedure code modifier.
Situational
1-7
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
SITUATIONAL RULE: Required when the service request is for a "Not Otherwise Classified" (NOC) or "By Report" procedure code or to report the following information on this service line: Date of Initial Impression, Date of Initial Preparation Crown, Initial Preparation Crown Tooth Number, or Initial Endodontic Treatment. If not required by this implementation guide, do not send.
INDUSTRY NAME: Procedure Code Description
Situational
1-8
234
Product/Service ID
O 1
AN
1/80
Identifying number for a product or service
SITUATIONAL RULE: Required when the requester cannot determine the intensity or complexity of the service to be performed and therefore requires authorization for a range of procedures. If not required by this implementation guide, do not send.
INDUSTRY NAME: Procedure Code
Use SV301-02 to represent the beginning value in the procedure range and this data element to represent the ending value in a range of codes.
Situational
1-9
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
A modifier must be from code source 135 (American Dental Association) found in the `Code on Dental Procedures and Nomenclature'.

Use this modifier for the fifth procedure code modifier.
Situational
1-10
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
A modifier must be from code source 135 (American Dental Association) found in the `Code on Dental Procedures and Nomenclature'.

Use this modifier for the sixth procedure code modifier.
Situational
1-11
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
A modifier must be from code source 135 (American Dental Association) found in the `Code on Dental Procedures and Nomenclature'.

Use this modifier for the seventh procedure code modifier.
Situational
1-12
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
A modifier must be from code source 135 (American Dental Association) found in the `Code on Dental Procedures and Nomenclature'.

Use this modifier for the eighth procedure code modifier.
Situational
2
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: SV302 is the submitted service line item amount.
SITUATIONAL RULE: Required when the usual and customary cost is necessary to approve a monetary limitation for the health care services requests. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Line Amount
Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
Not Used
3
1331
Facility Code Value
O 1
AN
1/3
Situational
4
C006
Oral Cavity Designation
O 1
To identify one or more areas of the oral cavity
SITUATIONAL RULE: Required when necessary to report areas of the mouth that are being treated. If not required by this implementation guide, do not send.
Required
4-1
1361
Oral Cavity Designation Code
M 1
ID
1/3
Code Identifying the area of the oral cavity in which service is rendered
Code source 135: American Dental Association Codes
CODE SOURCE 135: American Dental Association
Situational
4-2
1361
Oral Cavity Designation Code
O 1
ID
1/3
Code Identifying the area of the oral cavity in which service is rendered
SITUATIONAL RULE: Required when needed to identify additional oral cavity designation codes. If not required by this implementation guide, do not send.
Code source 135: American Dental Association Codes
CODE SOURCE 135: American Dental Association
Situational
4-3
1361
Oral Cavity Designation Code
O 1
ID
1/3
Code Identifying the area of the oral cavity in which service is rendered
SITUATIONAL RULE: Required when needed to identify additional oral cavity designation codes. If not required by this implementation guide, do not send.
Code source 135: American Dental Association Codes
CODE SOURCE 135: American Dental Association
Situational
4-4
1361
Oral Cavity Designation Code
O 1
ID
1/3
Code Identifying the area of the oral cavity in which service is rendered
SITUATIONAL RULE: Required when needed to identify additional oral cavity designation codes. If not required by this implementation guide, do not send.
Code source 135: American Dental Association Codes
CODE SOURCE 135: American Dental Association
Situational
4-5
1361
Oral Cavity Designation Code
O 1
ID
1/3
Code Identifying the area of the oral cavity in which service is rendered
SITUATIONAL RULE: Required when needed to identify additional oral cavity designation codes. If not required by this implementation guide, do not send.
Code source 135: American Dental Association Codes
CODE SOURCE 135: American Dental Association
Situational
5
1358
Prosthesis, Crown or Inlay Code
O 1
ID
1
Code specifying the placement status for the dental work
SITUATIONAL RULE: Required when needed to indicate the placement status of the prosthetic for this service. If not required by this implementation guide, do not send.
INDUSTRY NAME: Prosthesis, Crown, or Inlay Code
CODE
DEFINITION
I
Initial Placement
R
Replacement
Situational
6
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: SV306 is the number of procedures.
SITUATIONAL RULE: Required when the procedure reported in SV301-02 was performed more than once and it is not required to identify areas of the oral cavity or individual teeth. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Unit Count
Number of procedures
Situational
7
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
SEMANTIC: SV307 is the reason for replacement.
SITUATIONAL RULE: Required when necessary to describe the reason for replacement. If not required by this implementation guide, do not send.
Not Used
8
1327
Copay Status Code
O 1
ID
1
Not Used
9
1360
Provider Agreement Code
O 1
ID
1
Not Used
10
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
11
1328
Diagnosis Code Pointer
O 12
N
1/2
A pointer to the diagnosis code in the order of importance to this service
SEMANTIC: The first pointer designates the primary diagnosis and remaining diagnosis pointers indicate declining level of importance.
SITUATIONAL RULE: Required when this procedure relates to a specific diagnosis reported in the Loop 2000E HI - Patient Diagnosis segment to point to the specific diagnosis. If not required by this implementation guide, do not send.
This element is a repeating data element that may be repeated up to 12 times. The first pointer designates the primary diagnosis for this service line. Remaining diagnosis pointers indicate declining level of importance to service line.

Acceptable values are 1 through 12, and correspond to the HI01 through HI12 element number that holds the diagnosis values in the Event Loop (2000E).

If no diagnosis pointer is provided, then this procedure applies to all diagnosis.

TOO*JP - TOOTH INFORMATION

X12 Name:
Tooth Identification
X12 Purpose:
To identify a tooth by number and, if applicable, one or more tooth surfaces
X12 Syntax:
P0102
If either TOO01 or TOO02 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
32
Situational Rule:
Required when SV3 is valued and it is necessary to report tooth number and/or tooth surface. If not required by this implementation guide, do not send.
TR3 Example:
TOO✱JP✱12✱L:O~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1270
Code List Qualifier Code
X 1
ID
1/3
Code identifying a specific industry code list
SEGMENT SYNTAX: P0102
CODE
DEFINITION
JP
Universal National Tooth Designation System
CODE SOURCE: 135: American Dental Association
Required
2
1271
Industry Code
X 1
AN
1/30
Code indicating a code from a specific industry code list
SEGMENT SYNTAX: P0102
INDUSTRY NAME: Tooth Code
Code source 135: American Dental Association Codes
Situational
3
C005
Tooth Surface
O 1
To identify one or more tooth surface codes
SITUATIONAL RULE: Required when reporting tooth surface as defined by the procedure code. If not required by this implementation guide, do not send.
Required
3-1
1369
Tooth Surface Code
M 1
ID
1/2
Code identifying the area of the tooth that was treated
CODE
DEFINITION
B
Buccal
D
Distal
F
Facial
I
Incisal
L
Lingual
M
Mesial
O
Occlusal
Situational
3-2
1369
Tooth Surface Code
O 1
ID
1/2
Code identifying the area of the tooth that was treated
SITUATIONAL RULE: Required when necessary to report a second tooth surface. If not required by this implementation guide, do not send.
Use code values from TOO03-01.
CODE
DEFINITION
B
Buccal
D
Distal
F
Facial
I
Incisal
L
Lingual
M
Mesial
O
Occlusal
Situational
3-3
1369
Tooth Surface Code
O 1
ID
1/2
Code identifying the area of the tooth that was treated
SITUATIONAL RULE: Required when necessary to report a third tooth surface. If not required by this implementation guide, do not send.
Use code values from TOO03-01.
CODE
DEFINITION
B
Buccal
D
Distal
F
Facial
I
Incisal
L
Lingual
M
Mesial
O
Occlusal
Situational
3-4
1369
Tooth Surface Code
O 1
ID
1/2
Code identifying the area of the tooth that was treated
SITUATIONAL RULE: Required when necessary to report a fourth tooth surface. If not required by this implementation guide, do not send.
Use code values from TOO03-01.
CODE
DEFINITION
B
Buccal
D
Distal
F
Facial
I
Incisal
L
Lingual
M
Mesial
O
Occlusal
Situational
3-5
1369
Tooth Surface Code
O 1
ID
1/2
Code identifying the area of the tooth that was treated
SITUATIONAL RULE: Required when necessary to report a fifth tooth surface. If not required by this implementation guide, do not send.
CODE
DEFINITION
B
Buccal
D
Distal
F
Facial
I
Incisal
L
Lingual
M
Mesial
O
Occlusal

DN2 - TOOTH STATUS

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

DRA - DRUG AUTHORIZATION

X12 Name:
Drug Authorization
X12 Purpose:
To specify a drug for which authorization is being requested
X12 Syntax:
  1. P0405
    If either DRA04 or DRA05 is present, then the other is required.
  2. P080910
    If either DRA08, DRA09 or DRA10 are present, then the others are required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
>1
Situational Rule:
Required when more information is needed than what could be provided in the SV1 or SV2 for specific drug requests. If not required by this implementation guide do not send.
TR3 Notes:
If the request is for a compound drug, repeat the segment for each ingredient in the compound.
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
352
Description
M 2
AN
1/80
A free-form description to clarify the related data elements and their content
SEMANTIC: DRA01 is the drug name. Position of data in the repeating data element conveys no significance.
INDUSTRY NAME: Drug Name
Required
2
1322
Certification Type Code
M 1
ID
1
Code indicating the type of certification
SEMANTIC: DRA02 is the drug therapy type.
INDUSTRY NAME: Drug Therapy Type
CODE
DEFINITION
4
Extension
Use this code if it is the first use of this drug or therapeutic equivalent as a supplemental therapy for treatment of this condition.
I
Initial
Use this code if it is the first use of this drug or its therapeutic equivalent for treatment of this condition.
R
Renewal
Use this code for continuation of the use of this drug or its therapeutic equivalent for treatment of this condition.
S
Revised
Use this code if it the first use of this drug or its therapeutic equivalent to replace a previous unsuccessful or non-optimal therapy for treatment of this condition.
Situational
3
C003
Composite Medical Procedure Identifier
O 2
To identify a medical procedure by its standardized codes and applicable modifiers
SEMANTIC: DRA03 Position of data in the repeating data element conveys no significance.
X12 COMPOSITE SEMANTIC NOTES:
  1. C003-01 qualifies C003-02 and C003-08.
  2. If C003-08 is used, then C003-02 represents the beginning value in the range in which the code occurs.
  3. C003-03 modifies the value in C003-02 and C003-08.
  4. C003-04 modifies the value in C003-02 and C003-08.
  5. C003-05 modifies the value in C003-02 and C003-08.
  6. C003-06 modifies the value in C003-02 and C003-08.
  7. C003-07 is the description of the procedure identified in C003-02.
  8. C003-08 represents the ending value in the range in which the code occurs.
  9. C003-09 modifies the value in C003-02 and C003-08.
  10. C003-10 modifies the value in C003-02 and C003-08.
  11. C003-11 modifies the value in C003-02 and C003-08.
  12. C003-12 modifies the value in C003-02 and C003-08.
SITUATIONAL RULE: Required when a specific packaging of a drug is being requested or when using a representative NDC. If not required by this implementation guide, do not send.
Required
3-1
235
Product/Service ID Qualifier
M 1
ID
2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
INDUSTRY NAME: Product or Service ID Qualifier
CODE
DEFINITION
N4
National Drug Code in 5-4-2 Format
CODE SOURCE: 240: National Drug Code by Format
Required
3-2
234
Product/Service ID
M 1
AN
1/80
Identifying number for a product or service
INDUSTRY NAME: National Drug Code or Device Identifier of the Unique Device Identifier
Not Used
3-3
1339
Procedure Modifier
O 1
AN
2
Not Used
3-4
1339
Procedure Modifier
O 1
AN
2
Not Used
3-5
1339
Procedure Modifier
O 1
AN
2
Not Used
3-6
1339
Procedure Modifier
O 1
AN
2
Not Used
3-7
352
Description
O 1
AN
1/80
Not Used
3-8
234
Product/Service ID
O 1
AN
1/80
Not Used
3-9
1339
Procedure Modifier
O 1
AN
2
Not Used
3-10
1339
Procedure Modifier
O 1
AN
2
Not Used
3-11
1339
Procedure Modifier
O 1
AN
2
Not Used
3-12
1339
Procedure Modifier
O 1
AN
2
Required
4
355
Unit or Basis for Measurement Code
X 1
ID
2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
SEGMENT SYNTAX: P0405
CODE
DEFINITION
F2
International Unit
GR
Gram
ME
Milligram
ML
Milliliter
UN
Unit
Required
5
380
Quantity
X 1
R
1/15
Numeric value of quantity
SEMANTIC: DRA05 is the quantity being requested.
SEGMENT SYNTAX: P0405
INDUSTRY NAME: National Drug Unit Count
Required
6
933
Free-form Message Text
O 1
AN
1/264
Free-form message text
SEMANTIC: DRA06 is the Sig (The Sig is a Latin term used in the pharmacy industry that represents the instructions/directions that are printed on the drug label.)
INDUSTRY NAME: Sig
If the Sig is not known at the the time of the request, send unknown in this data element.
Situational
7
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: DRA07 is the self administer indicator. A "Y" value indicates that the drug can be administered by the patient. An "N" value indicates that the drug can not be administered by the patient.
SITUATIONAL RULE: Required when the drug can not be self administered by the patient. If not required by this implementation guide, do not send.
INDUSTRY NAME: Self Administered Drug Indicator
CODE
DEFINITION
N
No
Situational
8
1073
Yes/No Condition or Response Code
X 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: DRA08 is the end stage renal disease (ESRD) indicator. A "Y" value indicates that the patient has ESRD. An "N" value indicates that the patient does not have ESRD.
SEGMENT SYNTAX: P080910
SITUATIONAL RULE: Required when the patient has ESRD certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: ESRD Indicator
CODE
DEFINITION
Y
Yes
Situational
9
374
Date/Time Qualifier
X 1
ID
3
Code specifying type of date or time, or both date and time
SEGMENT SYNTAX: P080910
SITUATIONAL RULE: Required when the patient has ESRD certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
458
Certification
Situational
10
373
Date
X 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: DRA10 is the ESRD certification date.
SEGMENT SYNTAX: P080910
SITUATIONAL RULE: Required when the patient has ESRD certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: ESRD Certification Date
Situational
11
933
Free-form Message Text
O 999
AN
1/264
Free-form message text
SEMANTIC: DRA11 is for questions that are related to the authorization of the drug. Position of data in the repeating data element conveys no significance.
SITUATIONAL RULE: Required when UMO policy has defined additional information necessary for the completion of the authorization. If not required by this implementation guide, do not send.
INDUSTRY NAME: Drug Authorization Question/Answer
Use this data element to convey the UMO question and the answer.
Situational
12
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: DRA12 is the number of refills requested.
SITUATIONAL RULE: Required when refills are ordered. If not required by this implementation guide, do not send.
Situational
13
C060
Question and Answer
O 999
Used to supply the answers to pre-defined questions
SEMANTIC: DRA13 Position of data in the repeating data element conveys no significance.
X12 COMPOSITE SEMANTIC NOTES:
  1. C060-01 is the question number from a pre-defined questionnaire.
  2. C060-02 is the answer to the pre-defined question. A "Y" value indicates the answer to the question is yes. A "N" value indicates the answer to the question is no.
SITUATIONAL RULE: Required when the UMO has a pre-defined set of a yes/no answer questions that must be answered. If not required by this implementation guide, do not send.
Required
13-1
350
Assigned Identification
M 1
AN
1/20
Alphanumeric characters assigned for differentiation within a transaction set
INDUSTRY NAME: Pre-Defined Question Indicator
Required
13-2
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
INDUSTRY NAME: Pre-Defined Question Response
CODE
DEFINITION
N
No
U
Unknown
W
Not Applicable
Y
Yes
Required
14
1330
Dosage Form Code
O 1
ID
2
Code indicating the form in which the drug is dispensed
CODE
DEFINITION
10
Tablet
20
Capsule
30
Lozenge or Troche
31
Internal Powder
43
Injectable Lyophilized Powder
60
Elixir
61
Suspension
62
Syrup
63
Solution
64
Emulsion
67
Liquid
69
Rectal Cream or Ointment
70
Rectal Suppository
71
Vaginal Suppository
73
Vaginal Cream
75
Urethral Suppository
76
Enema
78
Vaginal Ointment
80
External Ointment
81
External Cream
86
External Powder
Not Used
15
933
Free-form Message Text
O 999
AN
1/264

HSD - HEALTH CARE SERVICES DELIVERY

X12 Name:
Health Care Services Delivery
X12 Purpose:
To specify the delivery pattern of health care services
X12 Syntax:
  1. P0102
    If either HSD01 or HSD02 is present, then the other is required.
  2. C0605
    If HSD06 is present, then HSD05 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when requesting services that have a specific pattern of delivery and the pattern of delivery or usage for this service is different from the pattern of delivery or usage (HSD) in the Patient Event (Loop 2000E). If not required by this implementation guide, do not send.
TR3 Notes:
An explanation of the uses of this segment follows.

HSD01 qualifies HSD02: If the value in HSD02=1 and the value in HSD01=VS (Visits), this means "one visit".
Between HSD02 and HSD03 verbally insert a "per every".
HSD03 qualifies HSD04: If the value in HSD04=3 and the value in HSD03=DA (Day), this means "three days". Between HSD04 and HSD05 verbally insert a "for". HSD05 qualifies HSD06: If the value in HSD06=21 and the value in HSD05=7 (Days), this means "21 days".
The total message reads:
HSD*VS*1*DA*3*7*21~ = "One visit per every three days for 21 days".

Another similar data string of HSD*VS*2*DA*4*7*20~ = "Two visits per every four days for 20 days".

An alternate way to use HSD is to employ HSD07 and/or HSD08. A data string of HSD*VS*1*****SX*D~ means "1 visit on Wednesday and Thursday morning".
TR3 Example:
  1. HSD✱VS✱1✱DA✱1✱7✱10~ (This indicates "1 visit every (per) 1 day (daily) for 10 days".)
  2. HSD✱VS✱1✱DA✱✱✱✱W~ (This indicates "1 visit per day whenever necessary".)
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Situational
1
673
Quantity Qualifier
X 1
ID
2
Code specifying the type of quantity
SEGMENT SYNTAX: P0102
SITUATIONAL RULE: Required when needed to indicate the type of service count quantified in HSD02. If not required by this implementation guide, do not send.
CODE
DEFINITION
DY
Days
FL
Units
HS
Hours
MN
Month
VS
Visits
Situational
2
380
Quantity
X 1
R
1/15
Numeric value of quantity
SEGMENT SYNTAX: P0102
SITUATIONAL RULE: Required when HSD01 is valued to indicate the service quantity. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Unit Count
  1. Service Quantity
  2. If this is a request for an extension to an existing certification (UM02 = 4), then HSD02 represents the number of visits by which the certification is extended. If this is a request to revise an existing certification (UM02 = S), then HSD02 represents the new total.
Situational
3
355
Unit or Basis for Measurement Code
O 1
ID
2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
SITUATIONAL RULE: Required when needed to indicate the timeframe in which the quantity of services in HSD02 will be rendered. If not required by this implementation guide, do not send.
CODE
DEFINITION
DA
Days
MO
Months
WK
Week
Situational
4
1167
Sample Selection Modulus
O 1
R
1/6
To specify the sampling frequency in terms of a modulus of the Unit of Measure, e.g., every fifth bag, every 1.5 minutes
SITUATIONAL RULE: Required when needed to indicate sampling frequency for this service. If not required by this implementation guide, do not send.
Situational
5
615
Time Period Qualifier
X 1
ID
1/2
Code defining periods
SEGMENT SYNTAX: C0605
SITUATIONAL RULE: Required when needed to indicate the time period for which the services will be continued. If not required by this implementation guide, do not send.
CODE
DEFINITION
6
Hour
7
Day
21
Years
26
Episode
27
Visit
34
Month
35
Week
Situational
6
616
Number of Periods
O 1
N
1/3
Total number of periods
SEGMENT SYNTAX: C0605
SITUATIONAL RULE: Required when needed to indicate the number of time periods in HSD05 that are requested. If not required by this implementation guide, do not send.
INDUSTRY NAME: Period Count
Situational
7
678
Ship/Delivery or Calendar Pattern Code
O 1
ID
1/2
Code which specifies the routine shipments, deliveries, or calendar pattern
SITUATIONAL RULE: Required when the service must be rendered within a specific calendar delivery pattern. If not required by this implementation guide, do not send.
INDUSTRY NAME: Delivery Frequency Code
CODE
DEFINITION
1
1st Week of the Month
2
2nd Week of the Month
3
3rd Week of the Month
4
4th Week of the Month
5
5th Week of the Month
6
1st & 3rd Weeks of the Month
7
2nd & 4th Weeks of the Month
8
1st Working Day of Period
9
Last Working Day of Period
A
Monday through Friday
B
Monday through Saturday
C
Monday through Sunday
D
Monday
E
Tuesday
F
Wednesday
G
Thursday
H
Friday
J
Saturday
K
Sunday
L
Monday through Thursday
M
Immediately
N
As Directed
O
Daily Mon. through Fri.
P
1/2 Mon. & 1/2 Thurs.
Q
1/2 Tues. & 1/2 Thurs.
R
1/2 Wed. & 1/2 Fri.
S
Once Anytime Mon. through Fri.
SA
Sunday, Monday, Thursday, Friday, Saturday
SB
Tuesday through Saturday
SC
Sunday, Wednesday, Thursday, Friday, Saturday
SD
Monday, Wednesday, Thursday, Friday, Saturday
SG
Tuesday through Friday
SL
Monday, Tuesday and Thursday
SP
Monday, Tuesday and Friday
SX
Wednesday and Thursday
SY
Monday, Wednesday and Thursday
SZ
Tuesday, Thursday and Friday
T
1/2 Tue. & 1/2 Fri.
U
1/2 Mon. & 1/2 Wed.
V
1/3 Mon., 1/3 Wed., 1/3 Fri.
W
Whenever Necessary
X
1/2 By Wed., Bal. By Fri.
Y
None (Also Used to Cancel or Override a Previous Pattern)
Situational
8
679
Ship/Delivery Pattern Time Code
O 1
ID
1
Code which specifies the time for routine shipments or deliveries
SITUATIONAL RULE: Required when needed to indicate the time delivery pattern for the services. If not required by this implementation guide, do not send.
INDUSTRY NAME: Delivery Pattern Time Code
CODE
DEFINITION
A
1st Shift (Normal Working Hours)
B
2nd Shift
C
3rd Shift
D
A.M.
E
P.M.
F
As Directed
G
Any Shift
Y
None (Also Used to Cancel or Override a Previous Pattern)

PWK - ADDITIONAL SERVICE INFORMATION

X12 Name:
Paperwork
X12 Purpose:
To identify the type or transmission or both of paperwork or supporting information
X12 Syntax:
  1. P0506
    If either PWK05 or PWK06 is present, then the other is required.
  2. P1011
    If either PWK10 or PWK11 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
10
Situational Rule:
Required when the requester has additional documentation (electronic, paper, or other medium) associated with this health care services review that applies to the service(s) requested in this Service loop, and the 278 request (ST-SE) does not support this information in its segments and data elements. If not required by this implementation guide, do not send.
TR3 Notes:
  1. Additional documentation at the service level should apply to a specific service and/or all the services requested in this service loop.
  2. This PWK segment is required to identify attachments that are sent electronically (PWK02 = EL) but are transmitted in another X12 functional group rather than by paper or other medium. PWK06 is used to identify the attached electronic documentation. The number in PWK06 would be referenced in the electronic attachment.
  3. The requester can also use this PWK segment to identify paperwork that is held at the provider's office and is available upon request by the UMO (or appropriate entity). Use code AA in PWK02 to convey this specific use of the PWK segment. See code note under PWK02, code AA.

    Refer to Section 1.11.5.1 for more information on using this PWK segment.
TR3 Example:
PWK✱OB✱BM✱✱✱AC✱DMN0012~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
755
Report Type Code
M 1
ID
2
Code indicating the title or contents of a document, report or supporting item
INDUSTRY NAME: Attachment Report Type Code
CODE
DEFINITION
03
Report Justifying Treatment Beyond Utilization Guidelines
04
Drugs Administered
05
Treatment Diagnosis
06
Initial Assessment
07
Functional Goals
Expected outcomes of rehabilitative services.
08
Plan of Treatment
09
Progress Report
10
Continued Treatment
11
Chemical Analysis
13
Certified Test Report
15
Justification for Admission
21
Recovery Plan
48
Social Security Benefit Letter
55
Rental Agreement
Use for medical or dental equipment rental.
59
Benefit Letter
77
Support Data for Verification
A3
Allergies/Sensitivities Document
A4
Autopsy Report
AM
Ambulance Certification
Information to support necessity of ambulance trip.
AS
Admission Summary
A brief patient summary; it lists the patient's chief complaints and the reasons for admitting the patient to the hospital.
AT
Purchase Order Attachment
Use for purchase of medical or dental equipment.
B2
Prescription
B3
Physician Order
BR
Benchmark Testing Results
BS
Baseline
BT
Blanket Test Results
CB
Chiropractic Justification
Lists the reasons chiropractic is just and appropriate treatment.
CK
Consent Form(s)
D2
Drug Profile Document
DA
Dental Models
DB
Durable Medical Equipment Prescription
DG
Diagnostic Report
DJ
Discharge Monitoring Report
DS
Discharge Summary
FM
Family Medical History Document
HC
Health Certificate
HR
Health Clinic Records
I5
Immunization Record
IR
State School Immunization Records
LA
Laboratory Results
M1
Medical Record Attachment
NN
Nursing Notes
OB
Operative Note
OC
Oxygen Content Averaging Report
OD
Orders and Treatments Document
OE
Objective Physical Examination (including vital signs) Document
OX
Oxygen Therapy Certification
P4
Pathology Report
P5
Patient Medical History Document
P6
Periodontal Charts
P7
Periodontal Reports
PE
Parenteral or Enteral Certification
PN
Physical Therapy Notes
PO
Prosthetics or Orthotic Certification
PQ
Paramedical Results
PY
Physician's Report
PZ
Physical Therapy Certification
QC
Cause and Corrective Action Report
QR
Quality Report
RB
Radiology Films
RR
Radiology Reports
RT
Report of Tests and Analysis Report
RX
Renewable Oxygen Content Averaging Report
SG
Symptoms Document
V5
Death Notification
XP
Photographs
Required
2
756
Report Transmission Code
O 1
ID
1/2
Code defining timing, transmission method or format by which reports are to be sent
CODE
DEFINITION
AA
Available on Request at Provider Site
Use when the paperwork is not being sent with the request at this time. It will be made available to the UMO (or approving entity) on request.
BM
By Mail
EL
Electronically Only
Use to indicate that the attachment is being transmitted in a separate X12 functional group.
EM
E-Mail
FT
File Transfer
FX
By Fax
VO
Voice
Use this for voicemail or phone communication.
Not Used
3
757
Report Copies Needed
O 1
N
1/2
Not Used
4
98
Entity Identifier Code
O 1
ID
2/3
Situational
5
66
Identification Code Qualifier
X 1
ID
1/2
Code designating the system/method of code structure used for Identification Code (67)
COMMENT: PWK05 and PWK06 may be used to identify the addressee by a code number.
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when PWK02 equals BM, EL, EM, FT or FX. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
CODE
DEFINITION
AC
Attachment Control Number
Situational
6
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when PWK02 equals BM, EL, EM, FT or FX. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
INDUSTRY NAME: Attachment Control Number
The requester can use it when PWK02 equals "AA" if the requester wants to send a document control number for an attachment remaining at the Provider's office.
Situational
7
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
COMMENT: PWK07 may be used to indicate special information to be shown on the specified report.
SITUATIONAL RULE: Required when needed to add any additional information about the attachment described in this segment. If not required by this implementation guide, do not send.
INDUSTRY NAME: Attachment Description
Not Used
8
C002
Actions Indicated
O 1
Not Used
9
1525
Request Category Code
O 1
ID
1/2
Not Used
10
1270
Code List Qualifier Code
X 1
ID
1/3
Not Used
11
1271
Industry Code
X 1
AN
1/30

MSG - MESSAGE TEXT

X12 Name:
Message Text
X12 Purpose:
To provide a free-form format that allows the transmission of text information
X12 Syntax:
C0302
If MSG03 is present, then MSG02 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when needed to transmit a message to the UMO about the service. If not required by this implementation guide, do not send.
TR3 Notes:
Do not use the MSG segment to relay information that you can send using codified information in existing data elements. If you need to use the MSG segment, you should approach X12N with data maintenance to solve the business need without the use of the MSG segment.
TR3 Example:
MSG✱This is a free-form text message~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
933
Free-form Message Text
M 1
AN
1/264
Free-form message text
INDUSTRY NAME: Free Form Message Text
Not Used
2
934
Printer Carriage Control Code
X 1
ID
2
Not Used
3
1470
Number
O 1
N
1/9

NM1 - SERVICE PROVIDER NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when requesting a service provider, specialist, or specialty entity for this service that is different from the provider, specialist, or specialty entity identified in Loop 2010EA (Patient Event Provider Name). If Loop 2010EA is not valued, Loop 2010F must be valued for each service associated with this patient event. 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. Use this segment to convey the name and identification number of the service provider (person, group, or facility) specialist, or specialty entity to provide services to the patient.
  2. If this loop is not valued, loop 2010EA is required to identify the service provider, specialist, or speciality entity to provide services.
TR3 Example:
NM1✱SJ✱1✱WATSON✱SUSAN✱✱✱✱XX✱1234567890~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
1T
Physician, Clinic or Group Practice
72
Operating Physician
73
Other Physician
77
Service Location
DD
Assistant Surgeon
DK
Ordering Physician
DQ
Supervising Physician
FA
Facility
G3
Clinic
P3
Primary Care Provider
QB
Purchase Service Provider
QV
Group Practice
SJ
Service Provider
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
2
Non-Person Entity
Situational
3
1035
Name Last or Organization Name
X 1
AN
1/60
Individual last name or organizational name
SEGMENT SYNTAX: C1203
SITUATIONAL RULE: Required when identifying a specific person, facility, group practice, or clinic and NM108/NM109 are not present. Not used if identifying a specialty entity utilizing the PRV segment. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Provider Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when the service provider is a specific person (NM102 = 1) and NM103 is present. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Provider First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when NM104 is present and the middle name/initial of the person is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Provider Middle Name or Initial
Situational
6
1038
Name Prefix
O 1
AN
1/10
Prefix to individual name
SITUATIONAL RULE: Required when military title or rank further identifies the provider. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Provider Name Prefix
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when NM104 is valued and the suffix of the individual's name is known; e.g. Sr., Jr., or III. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Provider Name Suffix
Situational
8
66
Identification Code Qualifier
X 1
ID
1/2
Code designating the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when requesting the services of a specific person, facility, group practice, or clinic and the provider ID is known by the requester. If not required by this implementation guide, do not send.
CODE
DEFINITION
XX
Centers for Medicare and Medicaid Services National Provider Identifier
Required for providers in the United States or its territories when the provider is eligible to receive a National Provider Identifier (NPI).

OR

Required for providers not in the United States or its territories when the provider has received an NPI. If not required by this implementation guide, do not send.
CODE SOURCE: 537: Centers for Medicare & Medicaid Services National Provider Identifier
Situational
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when requesting the services of a specific person, facility, group practice, or clinic and the provider ID is known by the requester. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Provider Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/60

REF - SERVICE PROVIDER SUPPLEMENTAL 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:
8
Situational Rule:
Required when NM1 of this loop is used and the NM109 is not valued and an identifier is necessary for the receiver to identify the provider. If not required by this implementation guide, do not send.
TR3 Example:
REF✱ZH✱A12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
0B
State License Number
1J
Facility ID Number
EI
Employer's Identification Number
G5
Provider Site Number
N5
Provider Plan Network Identification Number
N7
Facility Network Identification Number
SY
Social Security Number
The social security number must not be used for any Federally administered programs such as Medicare or CHAMPUS.
ZH
Carrier Assigned Reference Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Service Provider Supplemental Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Situational
3
352
Description
X 1
AN
1/80
A free-form description to clarify the related data elements and their content
SEGMENT SYNTAX: R0203
SITUATIONAL RULE: Required when REF01 = 0B to report the two character state ID of the state assigning the State License Number. If not required by this implementation guide, do not send.
INDUSTRY NAME: License Number State Code
See Code Source 22: State and Outlying Areas of the US.
Not Used
4
C040
Reference Identifier
O 1

N3 - SERVICE PROVIDER ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the provider has multiple locations and a specific location for this patient event needs to be identified. If not required by this implementation guide, do not send.
TR3 Example:
N3✱123 MAIN STREET~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Service Provider Address Line
Use this element for the first line of the provider's address.
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when a second address line is needed. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Provider Address Line

N4 - SERVICE PROVIDER CITY, STATE, ZIP CODE

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

PER*IC - SERVICE PROVIDER CONTACT INFORMATION

X12 Name:
Administrative Communications Contact
X12 Purpose:
To identify a person or office to whom administrative communications should be directed
X12 Syntax:
  1. P0304
    If either PER03 or PER04 is present, then the other is required.
  2. P0506
    If either PER05 or PER06 is present, then the other is required.
  3. P0708
    If either PER07 or PER08 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
2
Situational Rule:
Required when needed to identify a contact name and/or communication number for the provider. If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver.
TR3 Notes:
When the communication number represents a telephone number in the United States and other countries using the North American Dialing Plan (for voice, data, fax, etc.), the communication number must always include the area code and phone number using the format AAABBBCCCC where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number. Therefore, the following telephone number (555) 555-1234 would be represented as 5555551234. Do not submit long distance access numbers, such as 1, in the telephone number. Telephone extensions, when applicable, must be submitted in the next element immediately following the telephone number. When submitting telephone extensions, only submit the numeric extension, do not include data that indicates an extension, such as "ext" or "x-".
TR3 Example:
PER✱IC✱JOHN SMITH✱TE✱5555551234✱EX✱123~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
366
Contact Function Code
M 1
ID
2
Code identifying the major duty or responsibility of the person or group named
CODE
DEFINITION
IC
Information Contact
Situational
2
93
Name
O 1
AN
1/60
Free-form name
SITUATIONAL RULE: Required when the Information Source needs to indicate a particular contact and the name of the entity to contact is not already defined or is different than the name within the prior name segment (NM1). If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Provider Contact Name
Situational
3
365
Communication Number Qualifier
X 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0304
SITUATIONAL RULE: Required when PER02 is not valued, or to transmit a contact communication number. If not required by this implementation guide, do not send.
CODE
DEFINITION
EM
Electronic Mail
FX
Facsimile
TE
Telephone
UR
Uniform Resource Locator (URL)
Situational
4
364
Communication Number
X 1
AN
1/256
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0304
SITUATIONAL RULE: Required when PER02 is not valued, or to transmit a contact communication number. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Provider Contact Communication Number
Situational
5
365
Communication Number Qualifier
X 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
EM
Electronic Mail
EX
Telephone Extension
When used, the value following this code is the extension for the preceding communications contact number.
FX
Facsimile
TE
Telephone
UR
Uniform Resource Locator (URL)
Situational
6
364
Communication Number
X 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: Service Provider Contact Communication Number
Situational
7
365
Communication Number Qualifier
X 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
EM
Electronic Mail
EX
Telephone Extension
When used, the value following this code is the extension for the preceding communications contact number.
FX
Facsimile
TE
Telephone
UR
Uniform Resource Locator (URL)
Situational
8
364
Communication Number
X 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: Service Provider Contact Communication Number
Not Used
9
443
Contact Inquiry Reference
O 1
AN
1/20

PRV - SERVICE PROVIDER INFORMATION

X12 Name:
Provider Information
X12 Purpose:
To specify the identifying characteristics of a provider
X12 Syntax:
P0203
If either PRV02 or PRV03 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when request is for services of a specialist or specialty entity to indicate the provider's specialty. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
TR3 Example:
PRV✱PE✱PXC✱1223G0001X~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1221
Provider Code
M 1
ID
1/3
Code identifying the type of provider
CODE
DEFINITION
AS
Assistant Surgeon
Use only when NM101 = DD.
OP
Operating
Use only when NM101 = 72.
OR
Ordering
Use only when NM101 = DK.
OT
Other Physician
Use only when NM101 = 73.
PC
Primary Care Physician
Use only when NM101 = P3.
PE
Performing
Use only when NM101 = SJ.
Required
2
128
Reference Identification Qualifier
X 1
ID
2/3
Code qualifying the Reference Identification
SEGMENT SYNTAX: P0203
CODE
DEFINITION
PXC
Health Care Provider Taxonomy Code
CODE SOURCE: 682: Health Care Provider Taxonomy
Required
3
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: P0203
INDUSTRY NAME: Provider Taxonomy Code
  1. Provider Specialty Code
  2. Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
4
156
State or Province Code
O 1
ID
2
Not Used
5
C035
Provider Specialty Information
O 1
Not Used
6
1223
Provider Organization Code
O 1
ID
3

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✱24✱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
The Transaction Set Control Number in ST02 and SE02 must be identical.

GE - FUNCTIONAL GROUP TRAILER

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

IEA - INTERCHANGE CONTROL TRAILER

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

278 Health Care Services Review - Request for Review and Response (006020X315)

SEPTEMBER 2014

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

All rights reserved.

Abstract

The Health Care Services Review Request and Response Implementation Guide describes the use of the ASC X12 Health Care Services Review Information (278) Version/Release 006020 transaction set for the following business usages:

  • Health care admission certificate requests and responses
  • Referral requests and responses
  • Health care services certification requests and responses
  • Extend certification requests and responses
  • Certification appeal requests and responses

Preface

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

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

1.1 Implementation Purpose and Scope

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 who request authorizations or certifications or who respond to such requests using the ASC X12, Health Care Services Review Information (278). This implementation guide provides a detailed explanation of the transaction set by defining data content, identifying valid code tables, and specifying values that are applicable for electronic health care service review requests and responses. The intention of the developers of the 278 is represented in this guide.

This implementation guide is designed to assist those who request reviews (specialty care, treatment, admission) and those who respond to those requests using the 278 format.

1.2 Version Information

This implementation guide is based on the October 2009 ASC X12 standards, referred to as Version 6, Release 2, Sub-release 0 (006020).

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

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

  • HI   Health Care Services Review Information (278)

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

1.3.1 Batch and Real-Time Usage

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

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

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

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

1.3.2 Other Usage Limitations

Batch Delivery of the 278
This implementation guide requires the use of a separate transaction set (ST to SE) for each patient event, as defined in Section 1.5 - Business Terminology.

This implementation supports the sending and receiving of multiple patient events in one transmission, where each patient event represents a single 278 transaction with multiple transactions in a single GS to GE loop.

If the Utilization Management Organization (UMO) system cannot process each 278 request upon receipt, the UMO system must return a 278 response to indicate that the health care services review request has been pended.

Real-Time Delivery of the 278
A 278 real-time request transaction and its associated response must contain only one patient event. A patient event is represented by a single ST to SE loop containing one subscriber loop as follows:

  • One subscriber loop (Loop 2000C) if the subscriber is the patient
  • One subscriber loop (Loop 2000C) if the dependent is the patient and has a unique member ID
  • One subscriber loop and one dependent loop (Loop 2000D) if the dependent is the patient and the dependent does not have a unique (different from the subscriber) member ID

This subscriber/patient information is followed by one occurrence of the 2000E Loop. One or more 2000F Loops may follow containing associated services.

1.4 Business Usage

The 278 has the flexibility to accommodate the exchange of information between providers and review entities. This section introduces the business events and processes associated with the 278.

1.4.1 Health Care Transaction Flow

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

1.4.2 Business Events Supported in this Guide - Request and Response

This implementation guide covers the following business events:

  • Admission certification review request and associated response
  • Referral review request and associated response
  • Health care services certification review request and associated response
  • Extend certification review request and associated response
  • Certification appeal review request and associated response
  • Reservation of medical services request and associated response
  • Cancellations of service reservations request and associated response

Figure 1.1 - Review Request and Response

Review Request and Response

As illustrated in Figure 1.1 - Review Request and Response, the exchange of information is between the primary parties, the provider and the UMO. Health care entities that use this implementation of the 278 include the following:

  • Providers or other requesting entities who request certification for a patient to receive health care services
  • Utilization Management Organizations who receive and respond to requests for authorization or certification
  • Providers who receive responses from the UMO
  • Other trading partners who use the 278 include system vendors, consulting services, and EDI network intermediaries such as clearinghouses, value-added networks, and telecommunication services

NOTE
This 278 is not intended for use in requests to identify service providers that are in network where no services are identified. This implementation guide requires that the requester include information on the service provider or specialty entity and the services requested. The information source or UMO can return a response to indicate that the specific service provider or specialty entity selected is out-of-network.

Dental Referrals and Certifications
You can also use the 278 Health Care Services Review Request and Response for dental referrals and dental certifications.

NOTE
The 278 is not intended for use to determine eligibility and benefits for dental related treatment. This is the function of the 270/271 Health Care Eligibility Inquiry and Response. The 278 is not intended for use in predetermination pricing. Use the 837 Health Care Claim: Dental to submit an inquiry for pricing information. This pricing information is returned on the 835 Health Care Claim: Payment/Advice.

Medical Service Reservations and Cancellations
A Medical Service Reservation is a health care service that is limited to a certain number of occurrences within a defined time frame as specified by the Health Plan without authorization. Some Health Plans require that these services be reserved prior to the service being rendered.

For example, a patient may be limited to two chiropractic services per month. A Medical Service Reservation must be on file and the date of service and procedure code on the claim must match that of the reservation in order for the claim to be paid. If the service is not provided, the Medical Service Reservation must be canceled by the provider who reserved the service to allow the patient to obtain another service.

If the provider determines that a patient needs more than the allotted services, authorization is required.

NOTE
The 278 is not intended for use to determine eligibility and benefits for services. This is the function of the 270/271 Health Care Eligibility Inquiry and Response.

1.4.3 Business Events Supported in Other 278 Implementation Guides

The 278 transaction set accommodates additional health care services review business events that are covered in separate 278 implementation guides. At the time of publication, these guides, and the business events they represent, are not covered under HIPAA.

Notifications
The 278 Health Care Services Review - Notification can be used to send unsolicited information among providers, payers, delegated UMO entities and/or other providers. This information can take the form of copies of health service reviews or notification of scheduled treatment, or the beginning and end of treatment. A participant who is the recipient of the information may acknowledge they received the data, or reject the data due to specific application layer processing, but may not respond with any review decision outcome.

This implementation guide supports the following categories of notifications.

Advance Notification for:

  • scheduled inpatient admissions
  • scheduled health services events
  • scheduled specialty care services

Completion Notification for:

  • patient arrival at a facility
  • patient discharge from facility
  • services completion notice for any specific episode of care

Information Copy for any Health Services Review information sent to primary care provider(s), service provider(s), or other Health Care entities requiring the information for specific purposes.

Change Notification to report changes to the detail of a previously sent notification or information copy.

As illustrated in Figure 1.2 - Notifications, the information is sent unsolicited from the information source. The information source is the entity that knows the outcome of the service review request, and can be either a UMO or a provider. For example, in a situation where the primary care provider can authorize specialty referrals that do not require review for medical necessity, appropriateness, or level of care, the primary care provider is the information source. This provider might have responsibility for notifying both the UMO and the service provider of the specialty referral. In cases where the UMO is the decision maker, the UMO would send a notice of certification to the requesting provider and the service provider.

Figure 1.2 - Notifications

Notifications

Inquiries and Responses
The 278 Health Care Services Review - Inquiry and Response implementation guide handles informational inquiries and their related responses. It enables a participant to inquire about existing certifications and authorizations. As illustrated in Figure 1.3 - Inquiry and Response, the primary participants are providers and UMOs. The entity initiating the inquiry is either the primary provider or the service provider.

Figure 1.3 - Inquiry and Response

Inquiry and Response

Examples of the types of inquiries supported in this implementation include the following:

  • Specialty care referral inquiry
  • Admission certification inquiry
  • Health care service certification inquiry
  • All patient certifications inquiry

1.5 Business Terminology

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

For convenience, the Wordbook definitions for the following business terms, which are used in this implementation guide, are listed below.

Authorization
(1) The process by which the provider obtains permission (authorization) from the review entity/Utilization Management Organization (UMO) to:

  • Refer the patient to a specialist or specialty entity
  • Admit the patient to a facility
  • Administer medical services or treatment to the patient

(2) Permission, as determined by the review entity/UMO and defined by the patient's insurance plan or contract and medical condition, to:

  • Refer the patient (referral authorization)
  • Admit the patient (pre-certification)
  • Treat the patient (service authorization or pre-certification)

Certification
Reference Authorization, which is the preferred term.

Health Care Provider
A provider of medical or health services, and any other person or organization who furnishes, bills, or is paid for health care in the normal course of business.
Synonyms: Provider, Service Provider, Patient Event Provider

Patient event
A service or group of services associated with a single episode of care.

Pre-admission certification
An assessment, prior to elective inpatient hospital care, to determine if the proposed health care services meet the medical necessity criteria for payment under a health benefits plan.

Pre-certification
An assessment, prior to treatment or medical care, to determine if the proposed health care services meet the medical necessity criteria for payment under a health benefits plan.

Referral
A request initiated by a provider that enables a patient to receive consultation and/or services from a specialist or specialty entity, that do not require a prior authorization.

Medical Service Reservation
When a health plan limits the number of occurrences of a service within a defined timeframe, a reservation sets aside a certain number of the available occurrences for a specific provider.

Requester
An entity that initiates the process of a services review.

Utilization Management Organization (UMO)
An entity that receives and responds to health care service review requests and inquiries.

1.6 Transaction Acknowledgments

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

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

1.7 Related Transactions

There are no transactions related to the transactions described in this implementation guide.

1.8 Trading Partner Agreements

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

1.9 Transaction Compliance

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

Compliance with implementation guide requirements

Compliance with state and federal regulation

Compliance with trading partner contractual agreements

1.9.1 Transaction Compliance with Implementation Guide Requirements

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

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

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

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

1.9.2 Transaction Compliance with State and Federal Regulations

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

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

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

1.9.3 Transaction Compliance with State and Federal Regulations

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

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

1.10 Data Overview

The 278 can be exchanged between interested participants in a bi-directional request/response mode of operation. In this mode, a participant requests a certification and a review entity responds to that request. This implementation guide addresses that use. This section provides general information on the structure of the transaction set as represented in this implementation guide.

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

1.10.1 Overall Data Architecture

The 278 is divided into two levels, or tables. See Chapter 2, Transaction Set, for a description of the format presented. The Header level, Table 1, contains the purpose code for the transaction set as well as date and time stamps. For this implementation guide, BHT02 is either Cancellation (01), Request (13) or Authority to Deduct (36) on the request transaction, and Response (11) on the response transaction. In addition, a BHT06 value of AT indicates that the response contains a request for additional information.

The Detail level, Table 2, contains all data relating to the requested transaction, including transaction participants, the patient, all providers, and services detail information. Table 2 uses a hierarchical data structure to identify all the information associated with a health care services review for a patient event.

For the types of business transactions that this implementation guide addresses, the following hierarchical levels (loops) apply:

Loop 2000A contains the UMO
Loop 2000B contains the Requester
Loop 2000C contains the Subscriber
Loop 2000D contains the Dependent
Loop 2000E contains the Patient Event and Patient Event Providers
Loop 2000F contains the Services and Services Providers

Health Service Review Participants
This implementation guide uses a separate hierarchical level to identify each participant in the service review. Loop 2000A and Loop 2000B represent the UMO (reviewer) and requesting provider respectively. Loop 2000C and Loop 2000D represent the subscriber and dependent. If the subscriber is the patient or if the patient has a unique identification number, only Loop 2000C is required. Loop 2000E carries information about the patient event and the provider(s) (referred-to providers) associated with this patient event. Loop 2000F carries information about specific services and the service provider(s) for those individual services.

Patient Event
Patient event in this implementation guide refers to the service or group of services associated with a single episode of care. Refer to Section 1.5 - Business Terminology for examples of patient events. The 278 supports multiple types of service review requests. Due to the multiplicity of uses of the 278, this implementation guide is structured to require that separate transaction sets be used for different patients and events. This can be thought of as a one-to-one style relationship: one transaction set for one patient event. Loop 2000E contains the information associated with the patient event. This includes the diagnosis and condition of the patient, the identification of the category of services associated with this patient event, and the provider (facility or specialist) that will provide the services associated with this patient event.

Services
A health care services review can include a request to authorize a specific service and service provider associated with that service. Loop 2000F identifies the specific services included in this patient event and the providers that will deliver these services.

1.10.2 Sample Table 2 Configurations

The following are sample Table 2 configurations.

The following example represents a request for a category of service, such as ambulance transport, for a dependent of a subscriber.

UMO (Loop 2000A)
 Requester (Loop 2000B)
  Subscriber (Loop 2000C)
   Dependent (Loop 2000D)
    Patient Event (Loop 2000E)

The following example represents a response to a request for a category of service, such as ambulance transport, for a dependent of a subscriber.

UMO (Loop 2000A)
 Requester (Loop 2000B)
  Subscriber (Loop 2000C)
   Dependent (Loop 2000D)
    Patient Event (with Review Outcome Data) (Loop 2000E)

The following example represents a request for multiple services for a subscriber who is the patient.

UMO (Loop 2000A)
 Requester (Loop 2000B)
  Subscriber (Loop 2000C)
   Patient Event (Loop 2000E)
    Service (Loop 2000F)
    Service (Loop 2000F)

The following example represents a response to a request for multiple services for a subscriber who is the patient.

UMO (Loop 2000A)
 Requester (Loop 2000B)
  Subscriber (Loop 2000C)
   Patient Event (with Review Outcome Data) (Loop 2000E)
    Service (with Review Outcome Data) (Loop 2000F)
    Service (with Review Outcome Data) (Loop 2000F)

NOTE
The providers associated with the patient event or specific service are identified within the patient event and service loops respectively.

1.10.3 Intended Segment Use

Each hierarchical level (loop) in this implementation consists of multiple segments and is based on the same standard hierarchical structure of segments. An implementation specifies the maximum segments you can include, per hierarchical level, to describe the health service review participants, patient event, and services.

Request
For a request transaction, Table 1.1 - Intended Segment Use for a Request Transaction, identifies the intended segment use by hierarchical level.

Table 1.1 - Intended Segment Use for a Request Transaction

Segment
Position
Segment
ID
UMO HL Requester
HL
Subscriber
HL
Dependent
HL
Patient Event
HL
Service
HL
0100 HL YES YES YES YES YES YES
0200 TRN         YES YES
0300AAA      
0400UM    YESYES
0500HCR      
0600REF    YESYES
0700DTP    YESYES
0800HI    YES 
0810SV1     YES
0820SV2     YES
0830SV3     YES
0840TOO     YES
0850DN2     YES
0860DRA     YES
0900HSD    YESYES
1000CRC    YES 
1100CL1    YES 
1200CR1    YES 
1300CR2    YES 
1400CR5    YES 
1500CR6    YES 
1520CR7      
1530CR8      
1550PWK    YESYES
1600MSG    YESYES
1700NM1YESYESYESYESYESYES
1800REF YESYESYESYESYES
1900N2      
2000N3 YESYESYESYESYES
2100N4 YESYESYESYESYES
2200PER YES  YESYES
2300AAA      
2400PRV YES  YESYES
2500DMG  YESYES  
2600INS  YESYES  
2700DTP    YES 

Response
Table 1.2 - Intended Segment Use for a Response Transaction, identifies the intended segment use by hierarchical level for a response transaction.

Table 1.2 - Intended Segment Use for a Response Transaction

Segment
Position
Segment
ID
UMO HL Requester
HL
Subscriber
HL
Dependent
HL
Patient Event
HL
Service
HL
0100HLYESYESYESYESYESYES
0200TRN    YESYES
0300AAAYES   YESYES
0400UM    YESYES
0500HCR    YESYES
0600REF    YESYES
0700DTP    YESYES
0800HI    YESYES
0810SV1     YES
0820SV2     YES
0830SV3     YES
0840TOO     YES
0850DN2     YES
0860DRA     YES
0900HSD    YESYES
1000CRC      
1100CL1    YES 
1200CR1    YES 
1300CR2    YES 
1400CR5    YES 
1500CR6    YES 
1520CR7      
1530CR8      
1550PWK    YESYES
1600MSG    YESYES
1700NM1YESYESYESYESYESYES
1800REF YESYESYESYESYES
1900N2      
2000N3  YESYESYESYES
2100N4  YESYESYESYES
2200PERYES   YESYES
2300AAAYESYESYESYESYESYES
2400PRV YES  YESYES
2500DMG  YESYES  
2600INS  YESYES  
2700DTP      

1.10.4 Matching the Request with Its Response

This implementation guide provides several methods to enable requesters, clearinghouses, and UMOs to trace the transaction or match the response to the original request. This section describes the segments and data elements that carry these identifiers.

BHT03 - Submitter Transaction Identifier
BHT03 identifies the transaction at its highest level. This is particularly useful in reconciling 278 rejection transactions that may not contain all of the HL Loops. The receiver of the 278 request transaction (whether it is a clearinghouse or UMO) must return this identifier in the 278 response BHT03.

TRN Segment
The Patient Event loop (Loop 2000E) and the Service loop (Loop 2000F) each contain a TRN segment. This segment enables organizations to uniquely identify the request. The TRN at the Patient Event level uniquely identifies the patient event request. The Service level TRN uniquely identifies the request at its lowest logical level, the service. Both the requester (provider) and the clearinghouse can add a TRN segment to the request.

The requester (provider) can use this TRN segment to meet several needs. This enables the requester to accomplish the following:

  • Uniquely identify this request within the provider's environment
  • Uniquely identify each service requested. A single request transaction can contain requests for multiple services represented by multiple occurrences of Loop 2000F. This can generate more than one 278 response from the UMO. The UMO might certify some of these services immediately and pend others for external review.
  • Match the associated response to the request
  • Facilitate routing of this response in a large health care environment. For example, it might be necessary for the requester to identify the department within the provider environment that originated the transaction.

Clearinghouses can provide their own trace numbers in a separate TRN segment at the Patient Event level and at the Service level on the request to use for transaction tracking and matching purposes.

If the TRN segment is used on the request, the UMO must return the trace information supplied with the request transaction in the response transaction.

UMOs can add a trace number in their own TRN segment at the Patient Event level (Loop 2000E) and Service level (Loop 2000F) on the response. The UMO cannot use this trace number to identify the certification to the requester.

If the 278 request transaction passes through more than one clearinghouse, the second (and subsequent) clearinghouse may choose one of the following options:

  1. If the second or subsequent clearinghouse needs to assign their own TRN segment they may replace the received TRN segment belonging to the sending clearinghouse with their own TRN segment. Upon returning a 278 response to the sending clearinghouse, they must remove their TRN segment and replace it with the sending clearinghouse's TRN segment.
  2. If the second or subsequent clearinghouse does not need to assign their own TRN segment, they should merely pass all TRN segments received in the 278 request back in the 278 response transaction. If the 278 request passes through a clearinghouse that adds their own TRN in addition to a requester TRN, the clearinghouse will receive a response from the UMO containing two TRN segments that contain the value "2" (Referenced Transaction Trace Number) in TRN01. If the UMO has assigned a TRN, the UMO's TRN will contain the value "1" (Current Transaction Trace Number) in TRN01. If the clearinghouse chooses to pass their own TRN values to the requester, the clearinghouse must change the value in their TRN01 to "1" because, from the requester's perspective, this is not a referenced transaction trace number.

A TRN segment at the Patient Event level is required if the requester needs to uniquely identify each patient event. A TRN segment at the service level is required if the request contains more than one service level request and the requester needs to uniquely identify each service request.

1.10.5 Transaction Responses

The UMO must respond to each 278 transaction set received. If the UMO can process the service review request, the UMO must return a 278 response that contains an HCR segment at the Patient Event (Loop 2000E) and/or Service Level (Loop 2000F) in the response to indicate the status of the service review.

Rejected Transactions
Missing or incorrect application data on the 278 request can cause the UMO to reject the transaction. For these requests, the UMO must return a 278 response transaction that contains a AAA Request Validation segment at the appropriate level to indicate why the UMO rejected the transaction. The AAA segments in Loop 2000A (UMO) enable both the clearinghouse and the reviewer to indicate when system availability issues prohibit routing of the request for processing.

1.11 Data Use By Business Use

The segments referenced in Table 1.1 - Intended Segment Use for a Request Transaction and Table 1.2 - Intended Segment Use for a Response Transaction carry the data content of the health care services review. This section provides examples of the segments and data element values used in the hierarchical levels. The use of UMO, requester, subscriber, dependent, patient event, and service is consistent across types of health care services reviews. However, the use of the patient event and service levels differ across types of health care services reviews. Therefore, the patient event level and service level discussions in this section contain multiple examples.

Minimum Data Requirements
Factors such as the type of health care services review requested, the condition of the patient, and the individual UMO's rules for processing certifications make it difficult to identify a single set of data elements that are required for all types of certifications. To meet the divergent needs of the UMOs and requesters, this guide includes many data elements and segments marked "situational".

NOTE
This section provides examples of types of health care service reviews and the minimum data required. Refer to Chapter 2, Transaction Set of this guide for detailed information on valuing specific data elements within the segments.

1.11.1 Transaction Participants (Loop 2000A, Loop 2000B)

The Loop 2000A and Loop 2000B hierarchical levels are used to convey information about the two primary participants in a health care service review transaction. Figure 1.4 - Information Source and Receiver Levels, presents the Loop 2000A and Loop 2000B levels.

Figure 1.4 - Information Source and Receiver Levels

Information Source and Receiver Levels

Hierarchy Usage Chart for Transaction Participants
Because the various utilization management entities may appear in either the Loop 2000A or Loop 2000B hierarchical levels depending on the transaction usage, Table 1.3 - HL Information Sources and Receivers, has been included to better clarify the various possibilities when requesting a health service review. This table contains some examples where the UMO is one form of an HMO. Other examples can be constructed for other UMO environments. This table is by no means exhaustive.

Table 1.3 - HL Information Sources and Receivers

 
Transaction Use
 
HL UMO
HL
Requester
Physical
Transmitter
Physical
Receiver
PCP Request for a Specialty Care ReferralHMOPCPPCPHMO
Response to a Specialty Care Referral RequestHMOPCPHMOPCP
Specialist Request for Admission ReviewHMOSCPSCPHMO
Response to a Specialist Request for Admission ReviewHMOSCPHMOSCP
Specialist Request for Admission ReviewPCPSCPSCPPCP
Response to a Specialist Request for Admission ReviewPCPSCPPCPSCP
* HMO - Health Maintenance Organization
* UMO - Utilization Management Organization
* PCP - Primary Care Provider
* SCP - Specialty Care Provider
 

UMO (Loop 2000A)
The Loop 2000A hierarchical level is used to identify the UMO. The UMO is generally the entity empowered to make a decision regarding the outcome of a health services review or the owner of information.an be constructed for other UMO environments. This table is by no means exhaustive.

The following example demonstrates a minimum way of identifying a UMO.

HL*1**20*1~
NM1*X3*2******46*123450000~

Requester (Loop 2000B)
The Loop 2000B hierarchical level is used to designate the requester. The requester is generally the entity who is making the request for review and for whom the response decision is intended.

The following example demonstrates a minimum way of identifying a requester.

HL*2*1*21*1~
NM1*1P*1******XX*1234567890~

1.11.2 Patient (Loop 2000C and Loop 2000D)

Subscriber Loop 2000C and Dependent Loop 2000D identify the patient. Loop 2000C is always required on the request and on a response that does not report a reject reason in a AAA segment in Loop 2000A or Loop 2000B. Loop 2000D is used only when necessary to identify a patient who is a dependent. Figure 1.5 - Subscriber and Dependent Levels shows the structure of these loops.

Figure 1.5 - Subscriber and Dependent Levels

Subscriber and Dependent Levels

When the subscriber is the patient or when the patient has a unique identification number (different from the subscriber), only Loop 2000C is used. This situation is common when an insurance company issues a unique insurance identification card to each individual insured. In all other cases, Loop 2000C is used to identify the subscriber. Loop 2000D is used to identify the subscriber's dependent, who is the patient.

The Subscriber Name Loop 2010C and Dependent Name Loop 2010D contain the segments and data elements that hold this patient identification information. The NM1 and DMG segments contain all the data needed for the requester and UMO to identify the patient.

Identifying the Subscriber/Patient
In Subscriber Name Loop 2010C, the member ID (NM108/NM109) is required and may be adequate to identify the subscriber to the UMO. However, the UMO can require additional information. The maximum data elements that the UMO can require to identify the subscriber, in addition to the member ID, are as follows:

 Subscriber Last Name (NM103)
 Subscriber First Name (NM104)
 Subscriber Birth Date (DMG01 and DMG02).

The data requirements are the same for a dependent patient who has a unique identification number (different from the subscriber). In those cases where the subscriber is the patient or the patient has a unique identification number (different from the subscriber), only Loop 2000C is used.

The following example demonstrates a sufficient way of identifying a patient who has a unique identification number.

HL*3*2*22*1~
NM1*IL*1*SMITH*JOE****MI*12345678901~

Identifying the Dependent
If the dependent has not been issued a unique member ID, the Dependent Loop (2000D) is required in addition to Loop 2000C. Loop 2000C conveys insurance information and Loop 2000D conveys patient-related information. The maximum data elements that can be required by a UMO in loop 2010C and 2010D to identify a patient are as follows:

Loop 2010C
Subscriber's Member ID
Loop 2010D
Dependent Last Name
Dependent First Name
Dependent Birth Date

If all four of these elements are present the UMO must generate a response if the patient is in the UMO's database. All UMOs are required to support the above search option if their system does not have unique Member Identifiers assigned to dependents.

The following example demonstrates a sufficient way of identifying a patient who is the dependent of a subscriber. The example also illustrates the use of other segments.

HL*3*2*22*1~
NM1*IL*1*SMITH*JOE****MI*12345678901~
HL*4*3*23*1~
NM1*QC*1*SMITH*SEAN~
DMG*D8*19881229*M~
INS*N*19~

The INS segment enables the requester to provide information on the patient's relationship to the insured. The requester can also use this segment to identify a patient in a multiple birth or differentiate dependents with the same name.

Patient Account Number
The requester (provider) can supply the patient account number as a supplemental identifier for the patient on the request. This value is carried in a REF segment where REF01 = "EJ" in Loop 2000C - Subscriber or Loop 2000D - Dependent, whichever is the patient. This information is optional for the requester. However, if the UMO receives the patient account number, they must return it in the 278 response transaction when a AAA reject is not returned at a higher level.

1.11.3 Patient Event (Loop 2000E)

The Loop 2000E hierarchical level identifies the patient event associated with this health care services review request. It identifies the category of service requested and whether the patient event concerns a referral to a specialist, specialty treatment, or an admission to a facility. Patient event information can include a description of the patient's current health condition, prognosis, and other specific diagnosis indicators. It can also reference electronic or non-EDI attachments that provide additional information related to the patient's condition that is not supported within the 278 transaction set. If the health care services review includes information on specific procedures to be performed, it must provide information on these procedures at the Services Level (Loop 2000F).

Figure 1.6 - Patient Event Level

Patient Event Level

Identifying Multiple Providers
Loop 2000E also identifies the health care service provider(s) (facility, specialist or specialty entity) associated with all the services in this patient event. The 278 supports the identification of multiple providers in conjunction with a patient event. The following example represents a single provider associated with a single patient event, for example a referral to a specialist.

Loop 2000E (Patient Event)
 Loop 2010EA (Patient Event Provider 1)

The following example represents a single patient event with multiple associated providers, for example physical rehabilitation services to be administered by a specific provider or group practice at a specific facility location.

Loop 2000E (Patient Event)
 Loop 2010EA (Patient Event Provider 1) - Group Practice
 Loop 2010EA (Patient Event Provider 2) - Facility

If the patient event has multiple services/procedures and requires different providers for these procedures, use the Service Level to associate each provider with the respective service.

1.11.3.1 Specialty Care Referrals

Specialty care referrals encompass those transactions where a provider requests permission to refer or send a patient to another provider, generally a specialist. These types of transactions generally are shared between a primary care physician and a UMO. However, they may just as easily be shared between any two providers or UMOs. In the following example, the initial service requested is for a single office visit for a consultation at the provider's office.

Initial Request
HL*4*3*EV*0~
UM*SC*I*3*11:B*****Y~
HSD*VS*1~

The UM segment is used to identify the type of health care services request.

UM01 = SC (Specialty Care Review)
UM02 = I (Initial Request)
UM03 = 3 (Consultation)
UM04 = 11:B (Physician's Office)
UM09 = Y (Provider has a Signed Statement Permitting Release of Medical Billing Data Related to a Claim)

The HSD segment identifies the number of visits requested where HSD01 = VS (Visits) and HSD02 indicates the number of visits requested.

Response to Initial Request
A response transaction is used to indicate approval, approval with modification, or denial of a previous request. The UMO must respond to each 278 transaction set received. If the UMO can process the health service review request, the UMO must return a 278 response that contains an HCR segment at the Patient Event level (Loop 2000E) to indicate the status of the patient event service review.

Approval
To approve the specialty care referral request as described previously, the following service level would be returned:

HL*4*3*EV*0~
UM*SC*I*3*11:B~
HCR*A1*0081096G~
HSD*VS*1~

The HCR segment provides the results of the review as well as an associated reference number. This set of values indicates approval of the request in full. The response includes the original service level details respecting the services requested to eliminate confusion concerning what the UMO has approved. A reference number 0081096G is supplied and is critical if the provider wishes to initiate further transactions concerning this service.

HCR01 = A1 (Certified in Total
HCR02 = 0081096G (Certification Number)

Approval with Modification of Services
If the review entity wished to approve the specialist visits but decided to increase the number of visits to four, the following would be returned:

HCR*A6*0081096G~
HSD*VS*4~

Denial of Services
To completely deny the patient event request the following would be returned:

HL*4*3*EV*0~
UM*SC*I*3*11:B~
HCR*A3**0Y~
HSD*VS*1~

The A3 value indicates "not certified". Depending on UMO policy, the UMO might not return an authorization or reference number. Some organizations prefer to give no number because a number may imply approval. However, the failure to provide such a number restricts reference to the transaction at a later date. In this case, the UMO has also supplied a Review Decision Reason Code (0Y), "Service Inconsistent with Patient's Age".

Pended Response
Refer to "HCR Segment" in Section 2.6 for information on valuing the HCR segment when the response is pended.

Request for Extension
After a certification has been approved, a requester may need to extend the number of service units and/or the duration of time originally requested based upon the patient's health status.

HL*4*3*EV*0~
UM*SC*4*******Y~
REF*BB*0081096G~
HSD*VS*6~

In a request for an extension to an existing certification (UM02 = 4), HSD02 represents the number of visits by which the certification is extended. In this case, the requester is using the REF segment to refer to a prior certification number. This is the certification number returned by the UMO in HCR02 of the original response. "UM02 = 4" indicates that this is an extension request to a prior approved service. The HSD segment is used to extend the service by six visits.

Request for Reconsideration
The requester can specify a UM02 value of N (Reconsideration) to request the UMO to reconsider a previously denied referral or certification request.

HL*4*3*EV*0~
UM*SC*N*******Y~
REF*NT*REJ00001~

Normally, a request for reconsideration precedes an appeal. As in the "Request for Appeal" example, if the UMO returned an administrative reference number (REF01 = "NT") in the original response, the requester can use the REF segment to reference the UMO's response in this request for reconsideration.

Request for Appeal
The requester can use the 278 request to initiate the appeal of a denied or modified request for review.

HL*4*3*EV*0~
UM*SC*1*******Y~
REF*NT*REJ00001~

In this case, the requester is requesting an immediate appeal of a previously denied request by using the REF segment to refer to an administrative reference number. "UM02 = 1" indicates that this is an immediate appeal request. Although the provider has the ability to initiate an appeal request, this does not change the appeals process already established between the provider and the UMO. Typically, the provider must submit additional documentation that will require review by an appeal review board. The type of information required to return a decision can vary based upon the specific appeal request. In addition, the protocols for responding to an appeal request can vary by state. Therefore, the UMO and provider should establish protocols for communicating required information and ultimately rendering the final appeal decision.

Request for Renewal
Various services, such as physical therapy, spinal manipulation, and allergy treatment, have both a delivery pattern and a time span of authorization. Many UMOs place time limits on the period of treatment authorized and the UMO will authorize treatment for a limited period. For example, blanket authorization for allergy treatments as required for 30 days. At the end of the 30 days, the provider must request to renew the certification, not extend it, because the UMO authorizes for 30 day intervals, one interval at a time. For a renewal, the requester references the previous certification identifier and assigns UM02 the value "R", as follows:

HL*4*3*EV*0~
UM*SC*R~
REF*BB*REJ00001~

Request for Revision
A revision request should only be used to change previously requested services that have not been rendered. A provider may wish to add, delete or change information from a previously submitted request. For example, a revision request can be used to change the diagnosis or to change a servicing provider.

HL*4*3*EV*0~
UM*SC*S~
REF*BB*0081096G~
HI*BF:41090~

To revise a specific procedure code that was previously approved, UM02 in Loop 2000E will equal S (Revised) and the authorization number being revised will appear in the REF Previous Review Authorization Number if the authorization was granted at the Event Level. In the 2000F loop, UM02 will equal 3 (Cancel) in the first iteration of the service loop and the procedure code that is being changed from the original request is reported. If the authorization was granted at the Service Level, the previous review authorization number is reported in the REF Previous Review Authorization Number in this loop. In a second iteration of the 2000F loop, the new procedure code is reported. UM02 will equal S (Revised) to indicate that this loop will contain the revised procedure.

2000E Loop

UM*SC*S*3~
REF*BB*20111109ABCD~

First iteration of 2000F Loop

UM*SC*3~
SV1*HC:99211~

Second iteration of 2000F Loop

UM*SC*S~
SV1*HC:99212~

The response will acknowledge the cancellation of the old procedure and the action on the new procedure.

1.11.3.2 Health Services Reviews

The term "health services review" identifies requests for specific treatments or more extended care. Extended care refers to treatment for a condition requiring prolonged rehabilitation therapy. This transaction set supports a request for certification of services related to specific treatment or extended care associated with a single patient event. Complex treatment plans represent multiple patient events. Use a separate transaction for each patient event requested.

Initial Request
The UM segment is used to identify the type of health care services requested.

UM*HS*I*6******Y~

UM01 = HS (Health Services Review)
UM02 = I (Initial Request)
UM03 = 6 (Radiation Therapy)
UM09 = Y (Provider has a Signed Statement Permitting Release of Medical Billing Data Related to a Claim)

Other data elements in this segment carry additional information about the type of request and the condition of the patient. Value these additional data elements only if they provide information that is relevant to the medical decision on this health service review request.

Response
Health services review response uses are identical to those defined in the specialty care referrals response section of this implementation guide.

Segments Frequently Used in Association with Health Service Review Patient Events
The CRC segments enables the requester to provide additional patient condition information that the UMO can use to determine the medical necessity of the services requested. Because these segments do not contain information on the services or treatment requested, they are not used in the response. The CR1, CR2, CR5, and CR6 segments enable providers and UMOs to exchange more detailed information when requests are made regarding ambulance, spinal manipulation, and oxygen therapy respectively.

Example — Request for Spinal Manipulation Treatment
This is an example of a request for spinal manipulation services of the thoracic and lumbar section of the spine. It provides an example of the use of the CR2 segment. In this scenario, the chiropractor diagnosed the patient with a primary diagnosis of S33.5 (Sprain of ligaments of lumbar spine, initial encounter) and two secondary diagnoses M62.838 (Other muscle spasm) and S23.8 (Sprain of other specified parts of thorax, initial encounter). The chiropractor is requesting 2 visits per week over a 3 month period. In addition, the chiropractor specifies that subluxation is necessary for Thoracic Eleven and Lumbar Five, of the spine. The chiropractor requests authorization for the following procedures: 98941 (Chiropractic manipulative treatment, spinal, 3-4 areas), 98943 (Chiropractic manipulative treatment, extraspinal, 1-2 regions) and 97124 (Therapeutic massage to one or more areas).

HI*ABF:S335:D8:20131209*ABF:M62838:D8:20131209*ABF:S238:D8:20131209~
HSD*VS*2*WK**34*3~
CR2***T11*L5****A*N***Y~

The HI segment provides the associated diagnosis information.

HI01-01 = ABF (Diagnosis)
HI01-02 =S33.5 (Sprain of ligaments of lumbar spine, initial encounter)
HI01-03 = D8 (Date expressed as CCYYMMDD)
HI01-04 = 20131209 (Date diagnosed)
HI02-01 = ABF (Diagnosis)
HI02-02 = M62.838 (Other muscle spasm)
HI02-03 = D8 (Date expressed as CCYYMMDD)
HI02-04 = 20131209 (Date diagnosed)
HI03-01 = ABF (Diagnosis)
HI03-02 = S23.8 (Sprain of other specified parts of thorax, initial encounter)
HI03-03 = D8 (Date expressed as CCYYMMDD)
HI03-04 = 20131209 (Date diagnosed)

The HSD Segment specifies the pattern of delivery for the requested services. The request for spinal manipulation services will include 2 visits per week over a 3 month period.

HSD01 = VS (Visits - Type of service count)
HSD02 = 2 (Number for quantity of services to be rendered in the interval specified in HSD03)
HSD03 = WK (Week - Timeframe for which the quantity of services will be rendered)
HSD05 = 34 (Month - Time period for which services will be continued)
HSD06 = 3 (Number of time periods requested in HSD05)

The CR2 Segment is used to express the subluxation levels.

CR203 = T11 (Subluxation level code)
CR204 = L5 (Subluxation level code)
CR208 = A (Acute condition)
CR209 = No (Uncomplicated condition)
CR212 = Y (X-rays are available and maintained for carrier review)

NOTE
The full request includes three occurrences of the Service level (Loop 2000F), each containing an SV1 segment to request authorization for each of the three procedures. Refer to Section 1.11.4 - Services (Loop 2000F) for examples.

1.11.3.3 Admission Review

The term "admission review" identifies requests for admission to a facility for treatment (pre-certification). The transaction set enables the requester to specify both the facility and associated physicians within the same transaction.

Initial Request
The following example demonstrates a service request for the facility portion of an admission review.

HL*4*3*EV*0~
TRN*1*211099*9012345678~
UM*AR*I*2*21:B*****Y~
DTP*435*RD8:20131209-20131210~
HI*ABJ:I213~
NM1*FA*2*ABC MEMORIAL HOSPITAL*****XX*765432100~

The UM segment identifies the type of health care services request.

UM01 = AR (Admission Review)
UM02 = I (Initial Request)
UM03 = 2 (Surgical)
UM04 = 21:B (Hospital - Inpatient)
UM09 = Y (Provider has a Signed Statement Permitting Release of Medical Billing Data Related to a Claim)

Other segments in this loop carry additional information about the type of request and the condition of the patient. Value these additional data elements only if they provide information that is necessary for processing this request. For example, the request includes an admitting diagnosis of ST elevation (STEMI) myocardial infarction of unspecified site (HI*ABJ:I123~).

In this example, the additional elements clarify that the admission is for surgery that will take place in an inpatient setting. It also specifies a specific facility as the provider of services for this patient event.

NOTE
Use the Service Level (Loop 2000F) to identify specific surgical procedures associated with this admission or use the Service Level (2000F) to identify specific surgical procedures and/or specialty care directly associated with the admission event. If you are requesting a procedure or multiple procedures and are requesting that the same provider or providers perform all of these procedures, identify the providers in Loop 2010EA. If you need to associate different providers with different procedures, use the Loop 2010F associated with the specific service.

Response
Admission review response uses are identical to those defined in the specialty care referrals response section.

1.11.4 Services (Loop 2000F)

The Service level (Loop 2000F) is not required on the 278 request. The requester should value this loop only if the health care services review includes specific services or procedures for which authorization is required. If the 278 request does not include this loop, it must specify all the information pertaining to the category of services requested at the Patient Event level (Loop 2000E). As illustrated in Table 1.1 - Intended Segment Use for a Request Transaction and Table 1.2 - Intended Segment Use for a Response Transaction, many of the segments used in Loop 2000F are the same as those available in Loop 2000E. For a detailed explanation of their use, refer to Section 1.11.3 - Patient Event (Loop 2000E).

Figure 1.7 - Services Level

Services Level

Guidelines for Using the Service Level

  1. Use only if the services or procedures requested are for the same patient event identified in Loop 2000E.
  2. Use only if at least one of the following situations exists.
    • You are requesting a type of service (UM03) in addition to the category or type of service specified in the patient event, or
    • You are requesting a specific service or procedure code or a range of service or procedure codes.
  3. If this loop is valued, one of the following must be valued.
    • UM segment where UM03 is valued
    • SV1 where SV101 is valued
    • SV2 where either SV201 or SV202 is valued
    • SV3 where SV301 is valued
  4. Specify only one procedure or procedure code range in an occurrence of Loop 2000F. If you are requesting multiple procedures or procedure code ranges, use a separate occurrence of Loop 2000F for each procedure code or code range.
  5. Data values at the Service level override data values provided at the Patient Event level for the same data element for this service only.
  6. If this patient event includes requests for multiple services (more than on Loop 2000F), use the TRN segment in each Loop 2000F of the request to assign a unique trace number to each service. This enables you to trace the transaction or match the response to the request. In situations where the request contains multiple service loops, the UMO might return a medical decision on some services immediately and pend others for review. In this case, the final decisions on each service may be returned by the UMO at different times. Use of trace numbers at this level can facilitate matching these different responses to the original request.

Request for a Range of Procedures
Use the SV1 Professional Service, SV2 Institutional Service Line, or SV3 Dental Service segments to request authorization for a range of procedure codes that represent a single service. Typically, procedure ranges are used during the utilization review/management process. For example, the requesting provider knows the service to be provided but cannot be certain of the intensity or complexity of the service. Examples of common procedure ranges include the "Evaluation and Management" codes in the 99xxx range of the CPT-4 code set. A provider who is requesting authorization for specific office consultations might submit the range 99241-99245 in an authorization request. Submitting a range allows the provider to request authorization for visits in cases where the intensity of service cannot be known ahead of time (e.g., a patient undergoing specialist care for a recurring condition).

Response to Request Containing Service Level Information
Both the Patient level (Loop 2000E) and the Service level (Loop 2000F) have an HCR segment. If the UMO was unable to review the request due to missing or invalid application data at this level, the UMO must return a 278 response containing a AAA segment at this level. If the UMO has reviewed the request at this level the UMO may respond in one of the following ways, depending on the UMO's business rules.

  • If the UMO makes determinations at the Patient Event level only, then the decision returned in HCR01 for the HCR segment in Loop 2000E applies to all of the services associated with this patient event. If a certification number is returned (HCR02), this number applies to all the services associated with that patient event. The UMO is not required to render and return separate health care service review decision information in the HCR segment for each Loop 2000F returned.
  • In addition to valuing the HCR segment in Loop 2000E, the UMO may use the HCR segment in Loop 2000F to provide service review decision information specific to the service identified in that Service Loop 2000F. Values provided in the HCR segment in Loop 2000F override the values specified in the HCR segment of Loop 2000E for that service only. This enables the UMO to
    • evaluate and report a determination on each service request separately (HCR01);
    • assign a separate certification number to each service (HCR02); and
    • identify a separate review decision reason to each service (HCR03).

Example — Request for Spinal Manipulation Treatment and Associated Services
This is an example of a request for spinal manipulation services of the cervical section of the spine. In this scenario, the chiropractor diagnosed the patient with a primary diagnosis of M5020 (Displacement of cervical intervertebral disc) and a secondary diagnosis of M530 (Cervicocranial syndrome). The chiropractor is requesting visits to occur twice a week over a 3-month period. In addition, the chiropractor specifies that subluxation is necessary for Cervical One and Cervical Seven of the spine. The chiropractor requests authorization for the following procedures: 98941 (chiropractic manipulative treatment, spinal, 3-4 areas), 98943 (chiropractic manipulative treatment, extraspinal, 1-2 regions) and 97124 (therapeutic massage to one or more areas). The provider also faxes progress notes to substantiate the services requested.

Patient Event - Loop 2000E
Based on this example, the Patient Event Loop 2000E is valued as follows:

HL*4*3*EV*1~
UM*HS*I**11:B*****A~
HI*ABK:M5020*ABF:M530~
HSD*VS*2*WK**34*3~
CR2***C1*C7****A*N***Y~
PWK*09*FX***AC*20110901001*Cervical x-ray demonstrates subluxation of cervical disc~
NM1*SJ*1******XX*123456789~

Loop 2000E provides information on the patient event associated with the health care request. Information provided at this level applies to all the services included in the health care request. The UM segment specifies that this is a health service request for spinal manipulation treatment. Other data elements in this segment carry additional information about the type of request and the condition of the patient. In this example, the provider specified procedures; therefore, there is no need to value UM03 (Type of service). The requested procedures appear in the 2000F Service Loop.

The PWK segment is required if the requester has additional documentation associated with the health services review that applies to the patient event and/or all the services requested. The PWK segment provides the following identification information about the attachment.

PWK01 = 09 (Progress Report)
PWK02 = FX (Fax)
PWK05 = AC (Indicates that the value in PWK06 is the attachment control number assigned to the fax)
PWK06 = 20110901001 (this is the attachment control number)
PWK07 = Cervical x-ray demonstrates subluxation of cervical disc

In this example, the Loop 2010EA NM1 segment identifies the service provider or specialty entity requested.

NM101 = SJ (Service Provider)
NM102 = 1 (Person)
NM108 = 24 (Employer's Identification Number)
NM109 = 123456789

Refer to Section 1.11.3 - Patient Event (Loop 2000E) for a detailed description of the other segments in this loop.

This loop allows the provider to request authorization for specific procedure codes. In this example, the request includes 3 procedure codes. Therefore, the request includes 3 occurrences of Loop 2000F. In each loop, the SV1 segment identifies the service requested with a CPT code.

HL*5*4*SS*0~
SV1*HC:98941~
(HCPCS/CPT for Chiropractic manipulative treatment, spinal, 3-4 areas)
HL*6*4*SS*0~
SV1*HC:98943~
(HCPCS/CPT for Chiropractic manipulative treatment, extraspinal, 1-2 regions)
HL*7*4*SS*0~
SV1*HC:97124~
(HCPCS/CPT for Therapeutic massage to one or more areas)

Refer to Chapter 3, Examples for additional examples of uses of the Patient Event and Service levels.

1.11.5 Additional Health Service Review Information (Loops 2000E and 2000F)

Under some circumstances, UMOs may require additional patient information to determine the medical necessity of the services requested. This additional information concerns patient condition or service detail data not supported in the 278 (ST to SE). Depending on the type of health care services review, the requester might know of additional information required by the UMO at the time the request is initiated. Or, when the UMO receives the health care services review request, the UMO may determine that additional information is required to complete the review. This section provides guidelines for using these segments and data elements.

1.11.5.1 Referencing Additional Information on the 278 Request

The 278 request contains a PWK segment that the requester can use to reference an attachment (paper, electronic, or other medium) associated with the current health care services review. The attachment may be transmitted in a separate X12 functional group (e.g., 275 Attachment).

TRN Segments
The 278 supports a TRN segment at the Patient Event level and at the Service level. The Patient Event level TRN segment (Patient Event Trace Number) enables the requester to assign a unique trace number to the patient event request. The Service level TRN Segment (Service Trace Number) enables the requester to assign a unique identifier to a service when multiple services are requested. The UMO can reference these numbers when requesting additional information pertaining to the patient event or to the services requested.

PWK Segments
The 278 request supports 10 occurrences of the PWK segment at the Patient Event level (Loop 2000E) and at each Service level (Loop 2000F). This enables the requester to attach up to 10 items pertaining to the patient's condition and/or up to 10 items pertaining to each occurrence of Loop 2000F of the request.

Guidelines for Using the PWK Segment on the Request

  1. The PWK segment is required if the requester has additional documentation (electronic, paper, or other medium) associated with this health care services review that applies to the patient event and/or the services requested and the 278 request (ST to SE) does not support this information.
  2. Use the PWK segment at the Patient Event level if the attachment pertains to this patient event and/or all the services requested.
  3. Use the PWK segment at the Service level if the information pertains to a specific service identified in Loop 2000F.
  4. The PWK segment is required to identify attachments that are sent electronically (PWK02 = EL) but are transmitted in another X12 functional group (e.g., 275) rather than by paper. PWK06 is used to identify the attached electronic documentation. The number in PWK06 should be referenced in the electronic attachment.
    Please note that, at the time of publication, the 275 Patient Information Transaction Set has not been adopted as a HIPAA standard transaction and its use must be mutually agreed to by trading partners.
  5. The requester can also use the PWK segment to identify paperwork that is held at the provider's office and is available upon request by the UMO (or appropriate entity).

1.11.5.2 Requesting Additional Information on the 278 Response

When responding to a 278 request, the UMO might determine that additional information is required to complete the health care services review. The 278 response enables the UMO to:

  • indicate that the review outcome is pended for additional medical necessity information;
  • request this additional information by referencing paperwork that the requester must complete or by specifying codified information that the requester must provide; and
  • identify a specific contact or destination for the response to this request for additional information.

BHT Segment
In the BHT segment, BHT02 identifies the purpose of the 278 transaction and BHT06 identifies the type. A 278 response that contains a request for additional information must specify the following values:

BHT02 = 11 (Response)
BHT06 = AT (Administrative Action)

TRN Segment
If the TRN segment is used on the request, the UMO must return the trace information supplied with the request transaction in the response transaction. The UMO must return the Patient Event Trace Number and, if used, the Service Trace Number in the appropriate location on the response. If the UMO has requested additional information at the Patient Event level or at the Service level, the UMO must retain the Patient Event Trace Number or Service Trace Number from the request to reference on the request for additional information. In addition, UMOs can add a trace number in their own TRN segment at the Patient Event level or at the Service level on the response.

HCR Segment
If the UMO system can process the health service review request, the UMO must return a 278 response that contains an HCR segment at the Patient Event level (Loop 2000E) in the response to indicate the status of the health service review. The UMO must value the HCR segment to indicate that the review outcome has been pended for additional medical necessity information. If the UMO uses the 278 response to request this additional information, the UMO system must value the HCR segment as follows:

HCR*A4**0U~

Where:

HCR01 = "A4" (pended)
HCR03 = "0U" (Additional Information Required)

If the Service Level (Loop 2000F) was also valued on the request, the UMO can value the associated HCR segment in Loop 2000F of the response.

If the response contains the outcome of the review for some services but pends others for additional information, the UMO system can value the Loop 2000E HCR with HCR01 = A2 (Certified - partial) to indicate that the event is only partially certified. The HCR segments in Loop 2000F identify why the UMO has partially certified the patient event. For each service with a review outcome, the UMO system can value the Loop 2000F HCR01 to indicate the status of the review outcome. The UMO system can value the HCR segment for each service pended for additional information with HCR01 = "A4" and HCR03 = "0U".

PWK Segment
The UMO can use the PWK segment on a pended response to identify additional documentation required to complete the health care services review. The UMO can request information about the patient using the PWK segment at the Patient Event level (Loop 2000E) and/or about a specific service using the PWK segment at the Service level (Loop 2000F). This implementation supports 10 occurrences of the PWK at the Patient Event level and at each Service level to enable the UMO to request multiple attachments.

The UMO can use this segment to identify the type of documentation needed such as forms that the provider must complete. The UMO can also indicate what medium it has used to send these forms.

Guidelines for Using the PWK Segments on the Response

  1. The PWK segment is required if the UMO is requesting additional documentation (electronic, paper, or other medium) associated with this health care services review that applies to the patient event and/or the services requested and the UMO does not use LOINC® in the HI segments to request this information.
    LOINC is a registered trademark of Regenstrief Institute and the Logical Observation Identifier Names and Codes (LOINC) Committee. The LOINC lists identify high-level health care information groupings, specific data elements, and associated modifiers.
  2. Paperwork requested at the patient level should apply to the patient event and/or all the services requested.
  3. Use the PWK segment in the appropriate Service loop if requesting medical necessity information for a specific service.
  4. This PWK segment is required to identify requests for specific data that are sent electronically (PWK02 = EL) but are transmitted in another X12 functional group rather than by paper or using LOINC in the HI segments of the response. PWK06 is used to identify the attached electronic questionnaire. The number in PWK06 should be referenced in the corresponding electronic attachment.
    NOTE
    At the time of this writing, there is no published standard implementation or draft implementation of another X12 functional group (such as the 275) for use with the 278.
  5. This PWK segment should not be used if the requester should have provided the information within the 278 request (ST-SE) but failed to do so. In this case the UMO should use the AAA segments in the 278 response to indicate the data that is missing or invalid.

HI Segments
In addition to or in place of the PWK segment, the UMO can use the HI Diagnosis segment at the Patient Event level and/or the HI Request for Additional Information segment at the Service level of the pended response to specify codes identifying the specific information that the UMO requires from the provider to complete the medical review. On the response, the HI segment supports the use of codes supplied from the Logical Observation Identifier Names and Codes (LOINC) List. These codes identify high-level health care information groupings, specific data elements, and associated modifiers.

LOINC codes are used to request specific information. LOINC modifier codes are used to qualify the scope of the request for information. For example, LOINC code 18657-7 requests the Rehabilitation treatment plan, plan of treatment (narrative). A LOINC modifier code of 18803-7 would qualify the requested information to include all data of the selected type that represents observations made 30 days or less before the starting date of service.

The LOINC lists are external to ASC X12 standards. See Appendix A, External Code Sources, for instructions about how to obtain these lists.

The following provides an example of how to value the HI segment to request additional information using LOINC.

HI*LOI:18657-7*LOI:18803-7~

"LOI" indicates that the code list used is Logical Observation Identifier Names and Codes and 18657-7 is the high-level grouping and 18803-7 is the modifier.

Guidelines for Using HI Segments to Request Additional Information

  1. The LOINC code set was intended to increase the functionality of the 278 transaction set and it is not mandated by HIPAA and is only used when mutually agreed to by trading partners.
  2. Even if the trading partners can accommodate the use of LOINC on the 278 response request for additional information, the UMO cannot require that the original requester respond to this request using LOINC in the follow-up response.
  3. LOINC specified in the HI Diagnosis segment at the Patient Event level should apply to the patient event and/or all the services requested. Use the HI Request for Additional Information segment in the appropriate Service loop if using LOINC to request medical necessity information for a specific service or procedure.
  4. If the LOINC request pertains to a specific diagnosis code, place the specific diagnosis or procedure code in the HI C022 composite that precedes the HI C022 composite(s) containing the LOINC. For example:
    HI*ABF:I213*LOI:18657-7*LOI:18803-7~
    Where ABF:I213 identifies the diagnosis for which additional information is required.
  5. LOINC should not be used if the requester should have provided the information in the 278 request (ST-SE) but failed to do so. In this case the UMO should use the AAA segments in the 278 response to indicate the data that is missing or invalid.

Use of LOINC codes for requesting additional documentation for Diagnoses
The Patient Event level supports only one occurrence of the HI Diagnosis segment. This segment enables the requester to specify up to 12 diagnosis codes associated with the patient event. If the original request contained more than six diagnosis codes and you are using LOINC to request additional information for each diagnosis code or if you need to specify multiple questions/LOINC codes you cannot exceed the limit of 12 occurrences of the C022 composite. For example, if the provider identified 3 diagnoses and the UMO requires additional documentation regarding diagnosis one utilizing the LOINC code, the UMO can return the following response.

  1. Indicate the code list qualifier in HI01-01. For example, "ABF" - Diagnosis.
  2. Specify the first diagnosis code in HI01-02.
  3. Specify the "LOINC" code list qualifier in HI02-01. For example, "LOI" - LOINC to request additional information on the first diagnosis.
  4. Specify the LOINC code in HI02-02 to identify the specific documentation required.
  5. Specify the code list qualifier in HI03-01 for the second diagnosis requested. For example, "ABF" - Diagnosis.
  6. Specify the second diagnosis code in HI03-02.
  7. Specify the code list qualifier in HI04-01 for the third diagnosis requested. For example, "ABF" - Diagnosis.
  8. Specify the diagnosis code in HI04-02.

This allows the UMO to return the requested diagnoses on the response and provides a suggested format for identifying which diagnosis requires the additional information.

Use of LOINC codes for requesting additional documentation for a Procedure code range
On the 278 request, the requester can use the SV1, SV2 or SV3 segment at the Service Level (Loop 2000F) to request authorization for a range of procedure codes that represent a single service. On the 278 response transaction, the HI segment at the Service Detail (Loop 2000F) provides the facility for the UMO to request additional information regarding a procedure using the LOINC code. This mechanism applies to a provider who has submitted a request for procedure code ranges using the SV1, SV2 or SV3 segment. For example, if the provider submitted a request for a procedure code range using the SV1 segment that included four procedures and the UMO requires additional documentation regarding two the of requested procedures, the UMO can return the following response.

Loop 2000F - First Service Loop

HI segment

  1. Specify the "LOINC" code list qualifier in HI01-01. For example, "LOI" - LOINC to request additional information on the first procedure.
  2. Specify the LOINC code in HI01-02 to request additional information on the first procedure.

SV1 segment

  1. Specify the procedure code list qualifier in SV101-01. For example, "HC" - HCPCS CPT code.
  2. Specify the first specific procedure code for which additional information is being requested from the procedure range in SV101-02.

Loop 2000F - Second Service Loop

HI segment

  1. Specify the "LOINC" code list qualifier in HI01-01. For example, "LOI" - LOINC to request additional information on the second procedure.
  2. Specify the code list qualifier in HI01-02. For example, "LOI" - LOINC to request additional information on the second procedure.

SV1 segment

  1. Specify the procedure code list qualifier in SV101-01. For example, "HC" - HCPCS CPT code.
  2. Specify the second specific procedure code for which additional information is being requested for the procedure range in SV101-02.

When the UMO requests additional information for all procedures in the procedure range, structure the response as follows:

HI segment

  1. Specify the "LOINC" code list qualifier in HI01-01. For example, "LOI" - LOINC to request additional information on the first procedure in the range.
  2. Specify the LOINC code in HI01-02 to request additional information on the first procedure.
  3. Specify the "LOINC" code list qualifier in HI02-01. For example, "LOI" - LOINC to request additional information on the second procedure in the range.
  4. Specify the LOINC code in HI02-02 to request additional information on the second procedure.
  5. Specify the "LOINC" code list qualifier in HI03-01. For example, "LOI" - LOINC to request additional information on the third procedure in the range.
  6. Specify the LOINC code in HI03-02 to request additional information on the third procedure.
  7. Specify the "LOINC" code list qualifier in HI04-01. For example, "LOI" - LOINC to request additional information on the fourth procedure in the range.
  8. Specify the LOINC code in HI04-02 to request additional information on the fourth procedure.

SV1 segment

  1. Specify the procedure code list qualifier in SV101-01. For example, "HC" - HCPCS CPT code.
  2. Specify the beginning procedure code in SV101-02.
  3. Specify the ending procedure code in SV101-08.

Use of LOINC codes for requesting additional documentation for a service (SV1, SV2, or SV3 segment)
On the 278 transaction, the requester can use the Service level (Loop 2000F) to request a specific service or procedure using the SV1, SV2 or SV3 segment. Each occurrence of Loop 2000F represents the information related to a single service or procedure. In the response, the UMO returns an occurrence of Loop 2000F for each occurrence of Loop 2000F on the request. For example, if the provider submitted a request for three specific procedure codes using the SV1 segment, the request would contain three service loops. If the UMO requires additional documentation regarding two of the requested procedures, the UMO can return the following response.

Loop 2000F - First Service Loop

HI segment

  1. Specify the "LOINC" code list qualifier in HI01-01. For example, "LOI" - LOINC to request additional information on the first procedure.
  2. Specify the LOINC code in HI01-02 to request additional information on the first procedure

SV1 segment

  1. Specify the procedure code list qualifier in SV101-01. For example, "HC" - HCPCS CPT code.
  2. Specify the first procedure code in SV101-02.

Loop 2000F - Second Service Loop

HI segment

  1. Specify the "LOINC" code list qualifier in HI01-01. For example, "LOI" - LOINC to request additional information on the second procedure.
  2. Specify the code list qualifier in HI01-02. For example, "LOI" - LOINC to request additional information on the second procedure.

SV1 segment

  1. Specify the procedure code list qualifier in SV101-01. For example, "HC" - HCPCS CPT code.
  2. Specify the second procedure code in SV101-02.

Loop 2000F - Third Service Loop

If the UMO does not require additional information concerning the procedure specified in the third SV1 segment, the UMO may respond as follows:

  • The UMO may render a decision concerning this procedure and return the procedure specified (SV1) along with the health service review decision in the HCR segment of the same loop.
  • The UMO may pend the response on all the services requested until the requested information is returned.

NM1 Loops - Additional Information Contact Name
The 278 response includes NM1 loops to identify the person, office location, or other destination to route the response to the UMO request for additional information. NM1 Loop 2010EB identifies additional patient event information contact name, address, and communication number information for use with requests for additional information contained in the PWK or HI segments at the Patient Event level. NM1 Loop 2010FB identifies additional service information contact name, address, and communication number information for use with requests for additional information contained in the PWK or HI segments at the Service level.

Guidelines for Use of NM1 Loops

  1. Information in this loop overrides information supplied in the UMO Name NM1 loop (Loop 2010A).
  2. Use this NM1 loop only if
    1. the destination for the response to the request for additional patient information differs from the information specified in the UMO Name NM1 loop (Loop 2010A);
    2. either the PWK segment or HI segment in the associated loop contain a request for additional information; and
    3. the request for additional information is not transmitted in another X12 functional group where PWK02 = EL.
  3. This NM1 segment is required if this loop is used.

2. Transaction Set

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

2.1 Presentation Examples

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

Transaction Set Listing

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

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

This section is included as a reference.

Segment Detail

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

This section is included as a reference.

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

This section specifies the implementation details of each data element.

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

Figure 2.1 - Transaction Set Key - Implementation

Transaction Set Key - Implementation

Figure 2.2 - Transaction Set Key - Standard

Transaction Set Key - Standard

Figure 2.3 - Segment Key - Implementation

Segment Key - Implementation

Figure 2.4 - Segment Key - Diagram

Segment Key - Diagram

Figure 2.5 - Segment Key - Element Summary

Segment Key - Element Summary

2.2.1 Industry Usage

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

Required  

This loop/segment/element must always be sent.

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

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

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

Not Used  

This element must never be sent.

Situational  

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

There are two forms of Situational Rules.

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

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

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

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

2.2.1.1 Determining Transaction Compliance with Industry Usage Requirements

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

Industry Usage

Business
Condition
is

Item
is

Transaction
Complies with
Implementation
Guide?

Required

N/A

Sent

Yes

Not Sent

No

Not Used

N/A

Sent

No

Not Sent

Yes

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

True

Sent

Yes

Not Sent

No

Not True

Sent

Yes

Not Sent

Yes

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

True

Sent

Yes

Not Sent

No

Not True

Sent

No

Not Sent

Yes

2.2.2 Loops

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

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

3. Examples

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

Appendix A. External Code Sources

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

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

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

B.1.1 X12 Referenced and Related Standards

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

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

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

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

  • Compliance in X12

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

  • Acknowledgment Reference Model

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

B.1.1.1 Transmission Control Schematic

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

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

Figure B.1 - Transmission Control Schematic

Transmission Control Schematic

B.1.1.2 Constraints applicable to the suite of TR3s

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

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

B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification

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

B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount

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

EXAMPLE

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

B.1.1.3 Decimal

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

Appendix D. Change Summary

This Implementation Guide (006020X315) defines the X12 requirements for the Health Care Services Review - Request for Review and Response. It is based on version/release/subrelease 006020 of the ASC X12 standards.