278 Transaction Set Listing

Usage
Repeats

ISA - INTERCHANGE CONTROL HEADER

X12 Name:
Interchange Control Header
X12 Purpose:
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
  1. All positions within each of the data elements must be filled.
  2. For compliant implementations under this implementation guide, ISA13, the interchange Control Number, must be a positive unsigned number. Therefore, the ISA segment can be considered a fixed record length segment.
  3. The first element separator defines the element separator to be used through the entire interchange.
  4. The ISA segment terminator defines the segment terminator used throughout the entire interchange.
  5. Spaces in the example interchanges are represented by "." for clarity.
TR3 Example:
ISA✱00✱..........✱01✱SECRET....✱ZZ✱SUBMITTERS.ID..✱ZZ✱RECEIVERS.ID...✱030101✱1253✱^✱00501✱000000905✱0✱T✱:~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
I01
Authorization Information Qualifier
M 1
ID
2
Code identifying the type of information in the Authorization Information
CODE
DEFINITION
00
No Authorization Information Present (No Meaningful Information in I02)
03
Additional Data Identification
Required
2
I02
Authorization Information
M 1
AN
10
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
Required
3
I03
Security Information Qualifier
M 1
ID
2
Code identifying the type of information in the Security Information
CODE
DEFINITION
00
No Security Information Present (No Meaningful Information in I04)
01
Password
Required
4
I04
Security Information
M 1
AN
10
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
Required
5
I05
Interchange ID Qualifier
M 1
ID
2
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
This ID qualifies the Sender in ISA06.
CODE
DEFINITION
01
Duns (Dun & Bradstreet)
14
Duns Plus Suffix
20
Health Industry Number (HIN)
CODE SOURCE 121: Health Industry Number
27
Carrier Identification Number as assigned by Health Care Financing Administration (HCFA)
28
Fiscal Intermediary Identification Number as assigned by Health Care Financing Administration (HCFA)
29
Medicare Provider and Supplier Identification Number as assigned by Health Care Financing Administration (HCFA)
30
U.S. Federal Tax Identification Number
33
National Association of Insurance Commissioners Company Code (NAIC)
ZZ
Mutually Defined
Required
6
I06
Interchange Sender ID
M 1
AN
15
Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Required
7
I05
Interchange ID Qualifier
M 1
ID
2
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
This ID qualifies the Receiver in ISA08.
CODE
DEFINITION
01
Duns (Dun & Bradstreet)
14
Duns Plus Suffix
20
Health Industry Number (HIN)
CODE SOURCE 121: Health Industry Number
27
Carrier Identification Number as assigned by Health Care Financing Administration (HCFA)
28
Fiscal Intermediary Identification Number as assigned by Health Care Financing Administration (HCFA)
29
Medicare Provider and Supplier Identification Number as assigned by Health Care Financing Administration (HCFA)
30
U.S. Federal Tax Identification Number
33
National Association of Insurance Commissioners Company Code (NAIC)
ZZ
Mutually Defined
Required
8
I07
Interchange Receiver ID
M 1
AN
15
Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them
Required
9
I08
Interchange Date
M 1
DT
6
Date of the interchange
The date format is YYMMDD.
Required
10
I09
Interchange Time
M 1
TM
4
Time of the interchange
The time format is HHMM.
Required
11
I65
Repetition Separator
M 1
Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator
Required
12
I11
Interchange Control Version Number
M 1
ID
5
Code specifying the version number of the interchange control segments
CODE
DEFINITION
00501
Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
Required
13
I12
Interchange Control Number
M 1
N
9
A control number assigned by the interchange sender
  1. The Interchange Control Number, ISA13, must be identical to the associated Interchange Trailer IEA02.
  2. Must be a positive unsigned number and must be identical to the value in IEA02.
Required
14
I13
Acknowledgment Requested
M 1
ID
1
Code indicating sender's request for an interchange acknowledgment
See Section B.1.1.5.1 for interchange acknowledgment information.
CODE
DEFINITION
0
No Interchange Acknowledgment Requested
1
Interchange Acknowledgment Requested (TA1)
Required
15
I14
Interchange Usage Indicator
M 1
ID
1
Code indicating whether data enclosed by this interchange envelope is test, production or information
CODE
DEFINITION
P
Production Data
T
Test Data
Required
16
I15
Component Element Separator
M 1
Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

GS*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✱20071231✱0802✱1✱X✱005010X216~
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
005010X216
Health Care Services Review Notification and Acknowledgment

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 notification or information copy transaction set with all of the supporting detail information. This transaction set is the electronic equivalent of a phone, fax, or paper-based notification or information copy.
TR3 Example:
ST✱278✱0001✱005010X216~
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. The number is assigned by the originator and must be unique within a functional group (GS-GE). For example, start with the number 0001 and increment from there. The number also aids in error resolution research. Use the corresponding value in SE02 for this transaction set.
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 (STSE) processing. Providing the information from the GS08 at this level will ensure that the appropriate application mapping is utilized at translation time.
CODE
DEFINITION
005010X216
Health Care Services Review Notification and Acknowledgment

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✱14✱199800114000001✱20050101✱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
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
14
Advance Notification
Use for administrative notification (provider to payer) of admissions, referrals, pre-certifications of future events. For example, use for notification of authorization to admit a patient, notification of authorization to refer a patient, notification of authorization for pre-certification of services.
22
Information Copy
Use for courtesy copy of notification. For example, use to send copies of health care service review decision outcomes from a delegated entity, PCP, or UMO to the service provider.
CN
Completion Notification
Use CN for administrative notification (provider to payer) of admissions, referrals, pre-certifications associated with completed events. For example, use for Notice of Admission and Notice of Discharge.
Required
3
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: BHT03 is the number assigned by the originator to identify the transaction within the originator's business application system.
INDUSTRY NAME: Submitter Transaction Identifier
If the receiver returns a 278 acknowledgment response, this identifier must be returned in the 278 acknowledgment transaction's BHT03.
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 a 278 acknowledgment response to this notification is required. If not required by this implementation guide, do not send.
If BHT06 is not valued, the information receiver shall assume that a 278 acknowledgment response is not required or desired.
CODE
DEFINITION
NO
Notice

HL - INFORMATION SOURCE LEVEL

X12 Name:
Hierarchical Level
X12 Purpose:
To identify dependencies among and the content of hierarchically related groups of data segments
X12 Comments:
  1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
  2. The HL segment defines a top-down/left-right ordered structure.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
This segment identifies the information source hierarchical level. For a notification transaction, this segment corresponds to the identification of the provider, payer, HMO, delegated entity, or other utilization management organization sending this information.
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 - INFORMATION SOURCE 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. The first occurrence of the NM1 loop is required and identifies the notification sender. In most cases, the sender is the same entity as the information source. The information source is the entity that determined the outcome of a health services review or the owner of the information.
  2. The second NM1 loop may be used when the sender is not the same entity as the information source, or if there is a need to identify another requesting entity that was neither the sender or the information source.
TR3 Example:
NM1✱1P✱1✱GARDENER✱JAMES✱✱✱✱24✱000012345~
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
2B
Third-Party Administrator
FA
Facility
PR
Payer
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
2
Non-Person Entity
Situational
3
1035
Name Last or Organization Name
O 1
AN
1/60
Individual last name or organizational name
SEGMENT SYNTAX: C1203
SITUATIONAL RULE: Required when name information is needed to identify the information source. If not required by this implementation guide, do not send.
INDUSTRY NAME: Information Source 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 information source is an individual (NM102 = 1), such as a primary care provider. If not required by this implementation guide, do not send.
INDUSTRY NAME: Information Source 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: Information Source Middle Name
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when NM104 is present 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: Information Source Name Suffix
Required
8
66
Identification Code Qualifier
O 1
ID
1/2
Code designating the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
CODE
DEFINITION
24
Employer's Identification Number
34
Social Security Number
46
Electronic Transmitter Identification Number (ETIN)
PI
Payor Identification
Use until the National PlanID is mandated if the UMO is a payer.
XV
Centers for Medicare and Medicaid Services PlanID
CODE SOURCE: 540: Centers for Medicare and Medicaid Services PlanID
XX
Centers for Medicare and Medicaid Services National Provider Identifier
Required for providers in the United States or its territories on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider is eligible to receive an NPI;
OR
Required for providers not in the United States or its territories on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider has received an NPI;
OR
Required for providers prior to the mandated NPI implementation date when the provider has received an NPI and the submitter has the capability to send it;

If not required by this implementation guide, do not send.
CODE SOURCE: 537: Centers for Medicare & Medicaid Services National Provider Identifier
Required
9
67
Identification Code
O 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
INDUSTRY NAME: Information Source Identifier
Not Used
10
706
Entity Relationship Code
O 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/60

REF - INFORMATION SOURCE 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 prior to the mandated HIPAA National Provider Identifier (NPI) implementation date when an identification number other than the NPI is necessary for the UMO to identify the provider;
OR
Required after the mandated NPI implementation date, when the entity is a non-health care provider, and an identifier is necessary for the UMO to identify the entity.
If not required by this implementation guide, do not send.
TR3 Notes:
Use the NM1 segment for the primary identifier.
TR3 Example:
REF✱1G✱123456~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
1G
Provider UPIN Number
1J
Facility ID Number
EI
Employer's Identification Number
Not used if NM108 = 24.
G5
Provider Site Number
N5
Provider Plan Network Identification Number
N7
Facility Network Identification Number
SY
Social Security Number
Not used if NM108 = 34.
ZH
Carrier Assigned Reference Number
Use if the sender or information source is a provider to indicate the identifier assigned to the provider by the receiver identified in Loop 2000B.
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Information Source Supplemental Identifier
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

N3 - INFORMATION SOURCE 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 information source by location. If not required, by this implementation guide, do not send.
TR3 Notes:
Used to identify a specific location when the information source has multiple locations and his authority varies based on location.
TR3 Example:
N3✱43 SUNRISE BLVD✱SUITE 234~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Information Source Address Line
Use this element for the first line of the information source address.
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when a second address line exists. If not required by this implementation guide, do not send.
INDUSTRY NAME: Information Source Address Line

N4 - INFORMATION SOURCE 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 information source 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: Information Source City Name
Situational
2
156
State or Province Code
O 1
ID
2
Code (Standard State/Province) as defined by appropriate government agency
COMMENT: N402 is required only if city name (N401) is in the U.S. or Canada.
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: Information Source 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: Information Source Postal Zone or ZIP Code
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
O 1
ID
2/3
Code identifying the country
SEGMENT SYNTAX: C0704
SITUATIONAL RULE: Required when the address is outside the United States of America. If not required by this implementation guide, do not send.
Use the alpha-2 country codes from Part 1 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
5
309
Location Qualifier
O 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
O 1
ID
1/3
Code identifying the country subdivision
SEGMENT SYNTAX: E0207, C0704
SITUATIONAL RULE: Required when the address is not in the United States of America, including its territories, or Canada, and the country in N404 has administrative subdivisions such as but not limited to states, provinces, cantons, etc. If not required by this implementation guide, do not send.
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds

PER*IC - INFORMATION SOURCE CONTACT INFORMATION

X12 Name:
Administrative Communications Contact
X12 Purpose:
To identify a person or office to whom administrative communications should be directed
X12 Syntax:
  1. P0304
    If either PER03 or PER04 is present, then the other is required.
  2. P0506
    If either PER05 or PER06 is present, then the other is required.
  3. P0708
    If either PER07 or PER08 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the information receiver must direct requests for follow up to a specific contact, electronic mail, facsimile, or phone 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 should always include the area code and telephone number using the format AAABBBCCCC. Where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number (e.g. (534)224-2525 would be represented as 5342242525). The extension, when applicable, should be included in the communication number immediately after the telephone number.
TR3 Example:
PER✱IC✱WILBER✱TE✱8189991234✱FX✱8188769304~
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 within the prior name segment (e.g. N1 or NM1). If not required by this implementation guide, do not send.
INDUSTRY NAME: Information Source Contact Name
Situational
3
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0304
SITUATIONAL RULE: Required when PER02 is not valued 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
O 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 to transmit a contact communication number. If not required by this implementation guide, do not send.
INDUSTRY NAME: Information Source Contact Communication Number
Situational
5
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when the telephone extension or multiple communication numbers 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
O 1
AN
1/256
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when the telephone extension or multiple communication numbers are available. If not required by this implementation guide, do not send.
INDUSTRY NAME: Information Source Contact Communication Number
Situational
7
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when the telephone extension or multiple communication numbers 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
O 1
AN
1/256
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when the telephone extension or multiple communication numbers are available. If not required by this implementation guide, do not send.
INDUSTRY NAME: Information Source Contact Communication Number
Not Used
9
443
Contact Inquiry Reference
O 1
AN
1/20

PRV - INFORMATION SOURCE 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 the information source is a provider and the provider's role in the care of the patient or the provider's specialty is needed to further identify 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:
PRV02 qualifies PRV03.
TR3 Example:
PRV✱PC✱PXC✱203BS0133X~
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
Required
2
128
Reference Identification Qualifier
O 1
ID
2/3
Code qualifying the Reference Identification
SEGMENT SYNTAX: P0203
CODE
DEFINITION
PXC
Health Care Provider Taxonomy Code
CODE SOURCE: 682: Health Care Provider Taxonomy
Required
3
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: P0203
INDUSTRY NAME: Provider Taxonomy Code
Provider Specialty Code
Not Used
4
156
State or Province Code
O 1
ID
2
Not Used
5
C035
Provider Specialty Information
O 1
Not Used
6
1223
Provider Organization Code
O 1
ID
3

HL - INFORMATION RECEIVER LEVEL

X12 Name:
Hierarchical Level
X12 Purpose:
To identify dependencies among and the content of hierarchically related groups of data segments
X12 Comments:
  1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
  2. The HL segment defines a top-down/left-right ordered structure.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
This segment indicates the health care services review notification information receiver.
TR3 Example:
HL✱2✱1✱21✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
628
Hierarchical ID Number
M 1
AN
1/12
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
COMMENT: HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
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 - INFORMATION RECEIVER NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
This segment identifies the receiver of information.
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
1P
Provider
2B
Third-Party Administrator
FA
Facility
PR
Payer
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
2
Non-Person Entity
Situational
3
1035
Name Last or Organization Name
O 1
AN
1/60
Individual last name or organizational name
SEGMENT SYNTAX: C1203
SITUATIONAL RULE: Required when name information is needed to identify the receiver. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
INDUSTRY NAME: Information Receiver Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when NM103 is present and NM102 = 1. If not required by this implementation guide, do not send.
INDUSTRY NAME: Information Receiver First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when 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: Information Receiver Middle Name
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when NM104 is present 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: Information Receiver Name Suffix
Required
8
66
Identification Code Qualifier
O 1
ID
1/2
Code designating the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
CODE
DEFINITION
24
Employer's Identification Number
34
Social Security Number
46
Electronic Transmitter Identification Number (ETIN)
PI
Payor Identification
Use until the National PlanID is mandated if the information receiver is a payer.
XV
Centers for Medicare and Medicaid Services PlanID
CODE SOURCE: 540: Centers for Medicare and Medicaid Services PlanID
XX
Centers for Medicare and Medicaid Services National Provider Identifier
Required for providers on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider has an NPI and it is available to the submitter.
OR
Required for providers before the mandated HIPAA NPI implementation date when the provider has an NPI and the submitter has the capability to send it.

If not required by this implementation guide, do not send.
CODE SOURCE: 537: Centers for Medicare & Medicaid Services National Provider Identifier
Required
9
67
Identification Code
O 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
INDUSTRY NAME: Information Receiver Identifier
Not Used
10
706
Entity Relationship Code
O 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/60

HL - SUBSCRIBER LEVEL

X12 Name:
Hierarchical Level
X12 Purpose:
To identify dependencies among and the content of hierarchically related groups of data segments
X12 Comments:
  1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
  2. The HL segment defines a top-down/left-right ordered structure.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
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.1, Identifying the Subscriber/Patient.
TR3 Example:
NM1✱IL✱1✱SMITH✱JOE✱✱✱✱MI✱12345678901~
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
O 1
AN
1/60
Individual last name or organizational name
SEGMENT SYNTAX: C1203
SITUATIONAL RULE: Required when name information is needed by the receiver 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 receiver 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 receiver to identify the Subscriber and the middle name/initial of the person is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Middle Name or Initial
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when the suffix is needed to further identify the patient; 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
O 1
ID
1/2
Code designating the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
CODE
DEFINITION
II
Standard Unique Health Identifier for each Individual in the United States
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
O 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
O 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/60

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

The primary identifier is the Member Identification Number in the NM1 segment.
TR3 Notes:
  1. Health Insurance Claim (HIC) Number or Medicaid Recipient Identification Number is to be provided in the NM1 segment as a Member Identification Number when it is the primary number a UMO knows a member by (such as for Medicare or Medicaid). Do not use this segment for the Health Insurance Claim (HIC) Number or Medicaid Recipient Identification Number unless they are different from the Member Identification Number provided in the NM1 segment.
  2. If the information source values this segment with the Patient Account Number (REF01="EJ") on the notification, the notification receiver must return the same value in this segment on the acknowledgment response if one is returned.
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).
6P
Group Number
EJ
Patient Account Number
Use this code only if the subscriber is the patient.

The maximum number of characters to be supported for this qualifier is `20'. Characters beyond the maximum are not required to be stored nor returned by any receiving system.
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 was not used by the payer as its primary method of identifying the subscriber. The social security number may not be used for Medicare.
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Subscriber Supplemental Identifier
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

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✱PO Box 171021~
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 mailing address.
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when a second address line exists. 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
O 1
ID
2
Code (Standard State/Province) as defined by appropriate government agency
COMMENT: N402 is required only if city name (N401) is in the U.S. or Canada.
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber State Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
O 1
ID
3/15
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada, or when a postal code exists for the country in N404. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Postal Zone or ZIP Code
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
O 1
ID
2/3
Code identifying the country
SEGMENT SYNTAX: C0704
SITUATIONAL RULE: Required when the address is outside the United States of America. If not required by this implementation guide, do not send.
Use the alpha-2 country codes from Part 1 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
5
309
Location Qualifier
O 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
O 1
ID
1/3
Code identifying the country subdivision
SEGMENT SYNTAX: E0207, C0704
SITUATIONAL RULE: Required when the address is not in the United States of America, including its territories, or Canada, and the country in N404 has administrative subdivisions such as but not limited to states, provinces, cantons, etc. If not required by this implementation guide, do not send.
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds

DMG*D8 - SUBSCRIBER DEMOGRAPHIC INFORMATION

X12 Name:
Demographic Information
X12 Purpose:
To supply demographic information
X12 Syntax:
  1. P0102
    If either DMG01 or DMG02 is present, then the other is required.
  2. P1011
    If either DMG10 or DMG11 is present, then the other is required.
  3. C1105
    If DMG11 is present, then DMG05 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when birth date is needed to identify the patient or when gender information was used to render a medical decision. If not required by this implementation guide, do not send.
TR3 Example:
DMG✱D8✱19580322✱M~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEGMENT SYNTAX: P0102
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
2
1251
Date Time Period
O 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
SEMANTIC: DMG02 is the date of birth.
SEGMENT SYNTAX: P0102
INDUSTRY NAME: Subscriber Birth Date
Situational
3
1068
Gender Code
O 1
ID
1
Code indicating the sex of the individual
SITUATIONAL RULE: Required when 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
O 10
Not Used
6
1066
Citizenship Status Code
O 1
ID
1/2
Not Used
7
26
Country Code
O 1
ID
2/3
Not Used
8
659
Basis of Verification Code
O 1
ID
1/2
Not Used
9
380
Quantity
O 1
R
1/15
Not Used
10
1270
Code List Qualifier Code
O 1
ID
1/3
Not Used
11
1271
Industry Code
O 1
AN
1/30

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 the subscriber's role in the military was used to determine the appropriate benefit/level of care. 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
O 1
ID
2/3
Not Used
12
1251
Date Time Period
O 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:
This hierarchical loop is 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)
TR3 Example:
NM1✱QC✱1✱SMITH✱MARY~
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
O 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
O 1
ID
1/2
Not Used
9
67
Identification Code
O 1
AN
2/80
Not Used
10
706
Entity Relationship Code
O 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/60

REF - 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:
3
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 information source values this segment with the Patient Account Number (REF01="EJ") on the notification, the notification receiver must return the same value in this segment on the acknowledgment response if one is returned.
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 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 Medicare.
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Dependent Supplemental Identifier
Not Used
3
352
Description
O 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✱PO Box 171021~
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 exists. 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
O 1
ID
2
Code (Standard State/Province) as defined by appropriate government agency
COMMENT: N402 is required only if city name (N401) is in the U.S. or Canada.
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: 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
O 1
ID
2/3
Code identifying the country
SEGMENT SYNTAX: C0704
SITUATIONAL RULE: Required when the address is outside the United States of America. If not required by this implementation guide, do not send.
Use the alpha-2 country codes from Part 1 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
5
309
Location Qualifier
O 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
O 1
ID
1/3
Code identifying the country subdivision
SEGMENT SYNTAX: E0207, C0704
SITUATIONAL RULE: Required when the address is not in the United States of America, including its territories, or Canada, and the country in N404 has administrative subdivisions such as but not limited to states, provinces, cantons, etc. If not required by this implementation guide, do not send.
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds

DMG*D8 - 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 was used to render a medical decision. If not required by this implementation guide, do not send.
TR3 Example:
DMG✱D8✱19580322✱M~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEGMENT SYNTAX: P0102
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
2
1251
Date Time Period
O 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
SEMANTIC: DMG02 is the date of birth.
SEGMENT SYNTAX: P0102
INDUSTRY NAME: 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
O 10
Not Used
6
1066
Citizenship Status Code
O 1
ID
1/2
Not Used
7
26
Country Code
O 1
ID
2/3
Not Used
8
659
Basis of Verification Code
O 1
ID
1/2
Not Used
9
380
Quantity
O 1
R
1/15
Not Used
10
1270
Code List Qualifier Code
O 1
ID
1/3
Not Used
11
1271
Industry Code
O 1
AN
1/30

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 was used 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.
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
O 1
ID
2/3
Not Used
12
1251
Date Time Period
O 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:
  1. Loop 2000E identifies information about the patient event and includes specific person, group practice, facility, or specialty entity providing services.
  2. Patient event information identified at the 2000E loop applies to all subsequent 2000F service loops. Values entered at a specific 2000F service loop override 2000E patient event information for that 2000F service loop only.
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 TRACKING NUMBER

X12 Name:
Trace
X12 Purpose:
To uniquely identify a transaction to an application
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
3
Situational Rule:
Required when the information source needs to assign a unique trace number at the patient event level. 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 information receiver 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
The term "Current Transaction Trace Number" refers to the trace number assigned by the creator of the 278 notification transaction (the information source).
Required
2
127
Reference Identification
M 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: TRN02 provides unique identification for the transaction.
INDUSTRY NAME: Patient Event Trace Number
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 the information source and clearinghouses in identifying their TRN in the 278 acknowledgment.
  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/50
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

AAA - PATIENT EVENT REQUEST VALIDATION

X12 Name:
Request Validation
X12 Purpose:
To specify the validity of the request and indicate follow-up action authorized
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
9
Situational Rule:
Required when this is a notification of a health care services review that was rejected due to invalid or missing patient event information. If not required by this implementation guide, do not send.
TR3 Notes:
Use this AAA segment to identify the reasons why a request could not be processed based on the data at this level of the request. If not required, may be provided at the sender's discretion.
TR3 Example:
AAA✱N✱✱15~
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: AAA01 designates whether the request is valid or invalid. Code "Y" indicates that the code is valid; code "N" indicates that the code is invalid.
INDUSTRY NAME: Valid Request Indicator
CODE
DEFINITION
N
No
Y
Yes
Not Used
2
559
Agency Qualifier Code
O 1
ID
2
Situational
3
901
Reject Reason Code
O 1
ID
2
Code assigned by issuer to identify reason for rejection
SITUATIONAL RULE: Required when AAA01 = "N". If not required, may be provided at the sender's discretion.
CODE
DEFINITION
15
Required application data missing
Use when data is missing that is not covered by another Reject Reason Code. For example, use for missing procedure codes and procedure dates.
33
Input Errors
Use for input errors in the service data not covered by the other reject reason codes listed. For example, use for invalid place of service codes and invalid diagnosis codes and diagnosis dates.
52
Service Dates Not Within Provider Plan Enrollment
Use for Event Date(s).
56
Inappropriate Date
Use when the type of date (Accident, Last Menstrual Period, Estimated Date of Birth, Onset of Current Symptoms or Illness) used on the request is inconsistent with the patient condition or services requested.
57
Invalid/Missing Date(s) of Service
Use for invalid/missing event date.
60
Date of Birth Follows Date(s) of Service
Use for Date(s) of Event.
61
Date of Death Precedes Date(s) of Service
Use for Date(s) of Event.
62
Date of Service Not Within Allowable Inquiry Period
Use for Date of Event.
AF
Invalid/Missing Diagnosis Code(s)
AH
Invalid/Missing Onset of Current Condition or Illness Date
AI
Invalid/Missing Accident Date
AJ
Invalid/Missing Last Menstrual Period Date
AK
Invalid/Missing Expected Date of Birth
AM
Invalid/Missing Admission Date
AN
Invalid/Missing Discharge Date
T5
Certification Information Missing
Use to indicate missing previous certification number information.
Not Used
4
889
Follow-up Action Code
O 1
ID
1

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:
Required to identify the type of health care services in this notification.
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
AR
Admission Review
Use this value to identify admission to a facility.
HS
Health Services Review
Use this value to identify services related to an episode of care.
SC
Specialty Care Review
Use this value to identify 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 value to identify an extension request to a prior approved service.
5
Notification
I
Initial
N
Reconsideration
R
Renewal
Use this value to identify the various services, such as physical therapy, spinal manipulation, and allergy treatment, that 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 this value to identify a revision of a certification for which services have not been rendered. For example, the information source may be identifying additional procedures or other procedures for the same patient event.
Situational
3
1365
Service Type Code
O 1
ID
1/2
Code identifying the classification of service
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.
CODE
DEFINITION
1
Medical Care
2
Surgical
3
Consultation
4
Diagnostic X-Ray
5
Diagnostic Lab
6
Radiation Therapy
7
Anesthesia
8
Surgical Assistance
11
Used Durable Medical Equipment
12
Durable Medical Equipment Purchase
14
Renal Supplies in the Home
15
Alternate Method Dialysis
16
Chronic Renal Disease (CRD) Equipment
17
Pre-Admission Testing
18
Durable Medical Equipment Rental
20
Second Surgical Opinion
21
Third Surgical Opinion
23
Diagnostic Dental
24
Periodontics
25
Restorative
Use for restorative dental.
26
Endodontics
27
Maxillofacial Prosthetics
28
Adjunctive Dental Services
33
Chiropractic
35
Dental Care
36
Dental Crowns
37
Dental Accident
38
Orthodontics
39
Prosthodontics
40
Oral Surgery
42
Home Health Care
44
Home Health Visits
45
Hospice
46
Respite Care
54
Long Term Care
56
Medically Related Transportation
61
In-vitro Fertilization
62
MRI/CAT Scan
63
Donor Procedures
64
Acupuncture
65
Newborn Care
66
Pathology
67
Smoking Cessation
68
Well Baby Care
69
Maternity
70
Transplants
71
Audiology Exam
72
Inhalation Therapy
73
Diagnostic Medical
74
Private Duty Nursing
75
Prosthetic Device
76
Dialysis
77
Otological Exam
78
Chemotherapy
79
Allergy Testing
80
Immunizations
82
Family Planning
83
Infertility
84
Abortion
85
AIDS
86
Emergency Services
88
Pharmacy
93
Podiatry
A4
Psychiatric
A6
Psychotherapy
A9
Rehabilitation
AD
Occupational Therapy
AE
Physical Medicine
AF
Speech Therapy
AG
Skilled Nursing Care
AI
Substance Abuse
AJ
Alcoholism
AK
Drug Addiction
AL
Vision (Optometry)
AR
Experimental Drug Therapy
B1
Burn Care
BB
Partial Hospitalization (Psychiatric)
BC
Day Care (Psychiatric)
BD
Cognitive Therapy
BE
Massage Therapy
BF
Pulmonary Rehabilitation
BG
Cardiac Rehabilitation
BL
Cardiac
BN
Gastrointestinal
BP
Endocrine
BQ
Neurology
BS
Invasive Procedures
BY
Physician Visit - Office: Sick
BZ
Physician Visit - Office: Well
C1
Coronary Care
CQ
Case Management
GY
Allergy
IC
Intensive Care
MH
Mental Health
NI
Neonatal Intensive Care
ON
Oncology
PT
Physical Therapy
PU
Pulmonary
RN
Renal
RT
Residential Psychiatric Treatment
TC
Transitional Care
TN
Transitional Nursery Care
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: C023-02 qualifies C023-01 and C023-03.
SITUATIONAL RULE: Required when UM04 is not valued at 2000F. If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver.
Required
4-1
1331
Facility Code Value
M 1
AN
1/2
Code identifying where services were, or may be, performed; the first and second positions of the Uniform Bill Type Code for Institutional Services or the Place of Service Codes for Professional or Dental Services.
INDUSTRY NAME: Facility Type Code
Use to indicate a facility code value from the code source referenced in UM04-2.
Required
4-2
1332
Facility Code Qualifier
O 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
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
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

HCR - HEALTH CARE SERVICES REVIEW

X12 Name:
Health Care Services Review
X12 Purpose:
To specify the outcome of a health care services review
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when health care services review information applies to the event level. If not required by this implementation guide, do not send.
TR3 Notes:
The HCR segment at the 2000E event level contains information relevant to the original decision holder for the event. Certification Action, Review Identification, Review Decision Reason Code and Second Surgical Opinion Indicator data from the original decision maker is made available in the HCR segment to the information receiver.
TR3 Example:
HCR✱A1✱20020713~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
306
Action Code
M 1
ID
1/2
Code indicating type of action
Certification Action Code
CODE
DEFINITION
A1
Certified in total
A2
Certified - partial
Use to identify that the event is only partially certified. Consult HCR01, Loop 2000F for approved, denied or pended services.
A3
Not Certified
A4
Pended
A6
Modified
C
Cancelled
CT
Contact Payer
NA
No Action Required
Use only if certification is not required.
Situational
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: HCR02 is the number assigned by the information source to this review outcome.
SITUATIONAL RULE: Required when HCR01 = A1, A2 or A6. If not required by this implementation guide, do not send.
INDUSTRY NAME: Review Identification Number
Situational
3
1271
Industry Code
O 5
AN
1/30
Code indicating a code from a specific industry code list
SEMANTIC: HCR03 is the code assigned by the information source to identify the reason for the health care service review outcome indicated in HCR01.See Code Source 886
SITUATIONAL RULE: Required when HCR01 = A3, or A4. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
INDUSTRY NAME: Review Decision Reason Code
The HCR03 data element is a repeating data element and can be repeated up to the maximum allowed by the standard in this implementation guide.
Situational
4
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: HCR04 is the second surgical opinion indicator. A "Y" value indicates a second surgical opinion is required; an "N" value indicates a second surgical opinion is not required for this request.
SITUATIONAL RULE: Required when certification pertains to a surgical procedure and the contract under which the patient is covered has provisions regarding a second surgical opinion. If not required required by this implementation guide, do not send.
INDUSTRY NAME: Second Surgical Opinion Indicator
CODE
DEFINITION
N
No
Y
Yes

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 the certification number assigned by the UMO to the original event review outcome was used by the UMO to determine the outcome of this service review. 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 event. This is not the trace number assigned by the requester.
TR3 Example:
REF✱BB✱123A~
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
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Previous Review Authorization Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*NT - 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 this notification is related to an acknowledgment received from the information receiver in a prior acknowledgment transaction. If not required by this implementation guide, do not send.
TR3 Notes:
This is the administrative number assigned by the Information receiver in an acknowledgment from a prior notification. This is not the trace number assigned by the Information receiver.
TR3 Example:
REF✱NT✱Y456~
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
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Administrative Reference Number
Not Used
3
352
Description
O 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 Notes:
The total number of DPT segments in the 2000E Loop cannot exceed 9.
TR3 Example:
DTP✱439✱D8✱20051218~
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 notification is pregnancy related. If not required by this implementation guide, do not send.
TR3 Notes:
The total number of DPT segments in the 2000E Loop cannot exceed 9.
TR3 Example:
DTP✱484✱D8✱20051218~
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 DATE OF BIRTH

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 notification is related to the estimated date of delivery. If not required by this implementation guide, do not send.
TR3 Notes:
The total number of DPT segments in the 2000E Loop cannot exceed 9.
TR3 Example:
DTP✱ABC✱D8✱20050905~
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 Notes:
The total number of DPT segments in the 2000E Loop cannot exceed 9.
TR3 Example:
DTP✱431✱D8✱20051218~
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:
  1. If UM01 = AR use Admit Date.
  2. The total number of DPT segments in the 2000E Loop cannot exceed 9.
TR3 Example:
DTP✱AAH✱D8✱20050723~
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
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 identifying 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 Notes:
The total number of DPT segments in the 2000E Loop cannot exceed 9.
TR3 Example:
DTP✱435✱D8✱20050723~
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. Use the HSD segment for the length of stay.
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 identifying 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 Notes:
The total number of DPT segments in the 2000E Loop cannot exceed 9.
TR3 Example:
DTP✱096✱D8✱20050724~
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

DTP*102 - CERTIFICATION ISSUE 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 certification issue date is different than the certification effective date. If not required by this implementation guide, do not send.
TR3 Notes:
The total number of DPT segments in the 2000E Loop cannot exceed 9.
TR3 Example:
DTP✱102✱D8✱20050701~
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
102
Issue
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Certification Issue Date

DTP*036 - CERTIFICATION EXPIRATION 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 has an expiration date that indicates the date on which the certification will expire. If not required by the implementation guide, do not send.
TR3 Notes:
The total number of DPT segments in the 2000E Loop cannot exceed 9.
TR3 Example:
DTP✱036✱D8✱20050731~
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
036
Expiration
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Certification Expiration Date

DTP*007 - CERTIFICATION EFFECTIVE 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 limited by effective dates to indicate the date or date range when the certification is effective. If not required by the implementation guide, do not send.
TR3 Notes:
The total number of DPT segments in the 2000E Loop cannot exceed 9.
TR3 Example:
DTP✱007✱RD8✱20050701-20050731~
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
007
Effective
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: Certification Effective 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 identifying the diagnosis code at the event level. If not required by this implementation guide, do not send.
TR3 Example:
HI✱BF:41090~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
C022
Health Care Code Information
M 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (Diagnosis Code) and range of diagnosis codes were NOT given in C022-08.
Required
1-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
INDUSTRY NAME: Diagnosis Type Code
CODE
DEFINITION
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
ABJ
International Classification of Diseases Clinical Modification (ICD-10-CM) Admitting Diagnosis
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
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
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
O 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.
Situational
1-4
1251
Date Time Period
O 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
O 1
AN
1/30
Not Used
1-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
2
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (Diagnosis Code) and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when 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
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
ABJ
International Classification of Diseases Clinical Modification (ICD-10-CM) Admitting Diagnosis
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
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
O 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.
Situational
2-4
1251
Date Time Period
O 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
O 1
AN
1/30
Not Used
2-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
3
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (Diagnosis Code) and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when 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
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
APR
International Classification of Diseases Clinical Modification (ICD-10-CM) Patient's Reason for Visit
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
O 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.
Situational
3-4
1251
Date Time Period
O 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
O 1
AN
1/30
Not Used
3-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
4
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (Diagnosis Code) and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when 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
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
APR
International Classification of Diseases Clinical Modification (ICD-10-CM) Patient's Reason for Visit
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
O 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.
Situational
4-4
1251
Date Time Period
O 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
O 1
AN
1/30
Not Used
4-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
5
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (Diagnosis Code) and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when 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
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
APR
International Classification of Diseases Clinical Modification (ICD-10-CM) Patient's Reason for Visit
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
O 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.
Situational
5-4
1251
Date Time Period
O 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
O 1
AN
1/30
Not Used
5-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
6
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (Diagnosis Code) and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when 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
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
APR
International Classification of Diseases Clinical Modification (ICD-10-CM) Patient's Reason for Visit
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
O 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.
Situational
6-4
1251
Date Time Period
O 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
O 1
AN
1/30
Not Used
6-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
7
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (Diagnosis Code) and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when 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
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
APR
International Classification of Diseases Clinical Modification (ICD-10-CM) Patient's Reason for Visit
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
O 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.
Situational
7-4
1251
Date Time Period
O 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
O 1
AN
1/30
Not Used
7-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
8
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (Diagnosis Code) and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when 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
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
APR
International Classification of Diseases Clinical Modification (ICD-10-CM) Patient's Reason for Visit
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
O 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.
Situational
8-4
1251
Date Time Period
O 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
O 1
AN
1/30
Not Used
8-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
9
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (Diagnosis Code) and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when 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
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
APR
International Classification of Diseases Clinical Modification (ICD-10-CM) Patient's Reason for Visit
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
O 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.
Situational
9-4
1251
Date Time Period
O 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
O 1
AN
1/30
Not Used
9-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
10
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (Diagnosis Code) and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when 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
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
APR
International Classification of Diseases Clinical Modification (ICD-10-CM) Patient's Reason for Visit
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
O 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.
Situational
10-4
1251
Date Time Period
O 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
O 1
AN
1/30
Not Used
10-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
11
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (Diagnosis Code) and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when 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
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
APR
International Classification of Diseases Clinical Modification (ICD-10-CM) Patient's Reason for Visit
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
O 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.
Situational
11-4
1251
Date Time Period
O 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
O 1
AN
1/30
Not Used
11-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
12
C022
Health Care Code Information
O 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (Diagnosis Code) and range of diagnosis codes were NOT given in C022-08.
SITUATIONAL RULE: Required when 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
ABF
International Classification of Diseases Clinical Modification (ICD-10-CM) Diagnosis
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
APR
International Classification of Diseases Clinical Modification (ICD-10-CM) Patient's Reason for Visit
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
O 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.
Situational
12-4
1251
Date Time Period
O 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
O 1
AN
1/30
Not Used
12-9
1073
Yes/No Condition or Response Code
O 1
ID
1

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 identifying services that have a specific pattern of delivery or usage. If not required by this implementation guide, do not send.
TR3 Notes:
  1. Report delivery patterns for specific services in the Service Level (Loop 2000F).
  2. 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
O 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
O 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
Service Quantity
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 time frame 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 patient events must be rendered within a specific timeframe. If not required by this implementation guide, do not send.
Situational
5
615
Time Period Qualifier
O 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
WE
Weekend
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)

CL1 - INSTITUTIONAL CLAIM CODE

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 identifying certifications for admissions (UM01 = AR) to a facility. If not required by this implementation guide, do not send.
TR3 Example:
CL1✱3✱✱01~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Situational
1
1315
Admission Type Code
O 1
ID
1
Code indicating the priority of this admission
SITUATIONAL RULE: Required when admission type code information is used between the information sender and information receiver. If not required by this implementation guide, do not send.
CODE SOURCE 231: Priority (Type) of Admission or Visit
Situational
2
1314
Admission Source Code
O 1
ID
1
Code indicating the source of this admission
SITUATIONAL RULE: Required when admission source code information is used between the information sender and information receiver. If not required by this implementation guide, do not send.
CODE SOURCE 230: Point of Origin for Admission or Visit
Situational
3
1352
Patient Status Code
O 1
ID
1/2
Code indicating patient status as of the "statement covers through date"
SITUATIONAL RULE: Required when patient status code information is used between the information sender and information receiver. If not required by this implementation guide, do not send.
CODE SOURCE 239: Patient Status Code
Not Used
4
1345
Nursing Home Residential Status Code
O 1
ID
1

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✱✱✱T✱✱DH✱28~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Not Used
1
355
Unit or Basis for Measurement Code
O 1
ID
2
Not Used
2
81
Weight
O 1
R
1/10
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
Not Used
4
1317
Ambulance Transport Reason Code
O 1
ID
1
Situational
5
355
Unit or Basis for Measurement Code
O 1
ID
2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
SEGMENT SYNTAX: P0506
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
O 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
Not Used
9
352
Description
O 1
AN
1/80
Not Used
10
352
Description
O 1
AN
1/80

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 identifying 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~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Situational
1
609
Count
O 1
N
1/9
Occurrence counter
SEMANTIC: CR201 is the number this treatment is in the series.
SEGMENT SYNTAX: P0102
SITUATIONAL RULE: Required when identifying 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
O 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 identifying 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
O 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
O 1
ID
2
Not Used
6
380
Quantity
O 1
R
1/15
Not Used
7
380
Quantity
O 1
R
1/15
Not Used
8
1342
Nature of Condition Code
O 1
ID
1
Not Used
9
1073
Yes/No Condition or Response Code
O 1
ID
1
Not Used
10
352
Description
O 1
AN
1/80
Not Used
11
352
Description
O 1
AN
1/80
Not Used
12
1073
Yes/No Condition or Response Code
O 1
ID
1

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 identifying 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✱✱✱✱✱✱✱✱✱✱2✱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 was identified 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
Not Used
5
352
Description
O 1
AN
1/80
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
Not Used
10
380
Quantity
O 1
R
1/15
Not Used
11
380
Quantity
O 1
R
1/15
Not Used
12
1349
Oxygen Test Condition Code
O 1
ID
1
Not Used
13
1350
Oxygen Test Findings Code
O 1
ID
1
Not Used
14
1350
Oxygen Test Findings Code
O 1
ID
1
Not Used
15
1350
Oxygen Test Findings Code
O 1
ID
1
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 identifying 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✱19980601✱✱✱✱✱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
O 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
O 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
Use this value only for appeals of review decisions where the level of service required is emergency or urgent.
2
Appeal - Standard
Use this value for appeals of review decisions where the level of service is not emergency or urgent.
3
Cancel
4
Extension
5
Notification
6
Verification
This code is used to request the UMO to reconsider a previously denied referral or certification request.
I
Initial
R
Renewal
S
Revised
Not Used
9
373
Date
O 1
DT
8
Not Used
10
235
Product/Service ID Qualifier
O 1
ID
2
Not Used
11
1137
Medical Code Value
O 1
AN
1/15
Not Used
12
373
Date
O 1
DT
8
Not Used
13
373
Date
O 1
DT
8
Not Used
14
373
Date
O 1
DT
8
Not Used
15
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
16
1251
Date Time Period
O 1
AN
1/35
Not Used
17
1384
Patient Location Code
O 1
ID
1
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:
P0506
If either PWK05 or PWK06 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
10
Situational Rule:
Required when needed to identify missing teeth for dental services, or to identify additional documentation (electronic, paper, or other medium) associated with this health care services review that applies to the patient event and/or all the services requested 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 X12functional group rather than by paper or other medium. PWK06 is used to identify the attached electronic documentation. The number inPWK06 would be referenced in the electronic attachment.
  2. The information source can also use this PWK segment to identify paperwork that is held at the provider's office and is available upon request by the information receiver. Use code AA in PWK02 to convey this specific use of the PWK segment. See code note under PWK02, code AA.
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
HP
History and Physical
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
T7
Therapy Notes
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
BM
By Mail
EL
Electronically Only
Use to indicate that the attachment is being transmitted in a separate X12 functional group.
EM
E-Mail
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
O 1
ID
1/2
Code designating the system/method of code structure used for Identification Code (67)
COMMENT: PWK05 and PWK06 may be used to identify the addressee by a code number.
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when PWK02 equals BM, EL, EM 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
O 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when PWK02 equals BM, EL, EM 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
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 report tooth number(s) of missing teeth or if 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

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 it is necessary to send additional information about the patient event that could not otherwise be codified within the 2000E Loop. If not required by this implementation guide, do not send.
TR3 Notes:
  1. Free form text or description fields are not recommended because they require human interpretation.
  2. 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
O 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 of if 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✱✱✱✱34✱987654321~
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
DD
Assistant Surgeon
DK
Ordering Physician
DN
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
O 1
AN
1/60
Individual last name or organizational name
SEGMENT SYNTAX: C1203
SITUATIONAL RULE: Required when identifying a specialty person, facility, group practice, or clinic and NM108/NM109 are not present. Not used if identifying a specialty 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: 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 if 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 was used to determine the appropriate benefit/level of care. If not required by this implementation, may be provided at the sender's discretion, but cannot be required by the receiver.
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 present 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
O 1
ID
1/2
Code designating the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when identifying the services of a specific person, facility, group practice, or clinic and the provider ID is known by the information source. If not required by this implementation guide, do not send.
CODE
DEFINITION
24
Employer's Identification Number
34
Social Security Number
46
Electronic Transmitter Identification Number (ETIN)
XX
Centers for Medicare and Medicaid Services National Provider Identifier
Required for providers on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider has an NPI and it is available to the submitter.
OR
Required for providers before the mandated HIPAA NPI implementation date when the provider has an NPI and the submitter has the capability to send it.

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
O 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when identifying the services of a specific person, facility, group practice, or clinic and the provider ID is known by the information source. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider Identifier
Not Used
10
706
Entity Relationship Code
O 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/60

REF - 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:
7
Situational Rule:
Required on or after the mandated implementation date for the HIPAA National Provider Identifier (NPI) when the provider is not a specialty entity and the NPI is not reported in NM109 of this loop and another identifier is available to the submitter.
OR
Required prior to the mandated NPI implementation date when an additional identification number to the NPI provided in NM109 of this loop is necessary for the UMO to identify the patient event provider (2010E) service provider (2010F).
OR
Required prior to the mandated NPI implementation date when necessary for the UMO to identify the patient event provider (2010E) service provider (2010F).
If not required by this implementation guide, do not send.
TR3 Notes:
Use the NM1 segment for the primary identifier.
TR3 Example:
REF✱1G✱123456~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
0B
State License Number
1G
Provider UPIN Number
1J
Facility ID Number
EI
Employer's Identification Number
Not used if NM108 = 24.
N5
Provider Plan Network Identification Number
N7
Facility Network Identification Number
SY
Social Security Number
The social security number may not be used for Medicare. Not used if NM108 = 34.
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 2010A has assigned its own identifier for this provider.
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Patient Event Provider Supplemental Identifier
Situational
3
352
Description
O 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 identifying a specific location for a patient event provider that has multiple locations. If not required, may be provided at the sender's discretion.
TR3 Example:
N3✱77 HOLLY BLVD~
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 patient event provider's address.
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when a second address line exists. 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 identifying a specific location for a patient event provider that has multiple locations. If not required, may be provided at the sender's discretion.
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
O 1
ID
2
Code (Standard State/Province) as defined by appropriate government agency
COMMENT: N402 is required only if city name (N401) is in the U.S. or Canada.
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event 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: Patient Event Provider Postal Zone or ZIP Code
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
O 1
ID
2/3
Code identifying the country
SEGMENT SYNTAX: C0704
SITUATIONAL RULE: Required when the address is outside the United States of America. If not required by this implementation guide, do not send.
Use the alpha-2 country codes from Part 1 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
5
309
Location Qualifier
O 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
O 1
ID
1/3
Code identifying the country subdivision
SEGMENT SYNTAX: E0207, C0704
SITUATIONAL RULE: Required when the address is not in the United States of America, including its territories, or Canada, and the country in N404 has administrative subdivisions such as but not limited to states, provinces, cantons, etc. If not required by this implementation guide, do not send.
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds

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:
1
Situational Rule:
Required when needed to identify a contact name and/or communications 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 should always include the area code and telephone number using the format AAABBBCCCC. Where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number (e.g. (534)224-2525 would be represented as 5342242525). The extension, when applicable, should be included in the communication number immediately after the telephone number.
TR3 Example:
PER✱IC✱M TUCKER✱TE✱8189993456✱FX✱8185551212~
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 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 by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider Contact Name
Situational
3
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0304
SITUATIONAL RULE: Required when PER02 is not valued or when the Information Source needs 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
O 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 when the Information Source needs 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
O 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
CODE
DEFINITION
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
O 1
AN
1/256
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider Contact Communication Number
Situational
7
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
CODE
DEFINITION
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
O 1
AN
1/256
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider Contact Communication Number
Not Used
9
443
Contact Inquiry Reference
O 1
AN
1/20

AAA - PATIENT EVENT PROVIDER REQUEST VALIDATION

X12 Name:
Request Validation
X12 Purpose:
To specify the validity of the request and indicate follow-up action authorized
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
9
Situational Rule:
Required when this is a notification of a health care services review that was rejected due to invalid or missing service provider information. If not required by this implementation guide, do not send.
TR3 Example:
AAA✱N✱✱43~
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: AAA01 designates whether the request is valid or invalid. Code "Y" indicates that the code is valid; code "N" indicates that the code is invalid.
INDUSTRY NAME: Valid Request Indicator
CODE
DEFINITION
N
No
Y
Yes
Not Used
2
559
Agency Qualifier Code
O 1
ID
2
Required
3
901
Reject Reason Code
O 1
ID
2
Code assigned by issuer to identify reason for rejection
CODE
DEFINITION
15
Required application data missing
Use when data is missing that is not covered by another reject reason code. Use to indicate when there is not enough information to identify the provider.
33
Input Errors
Use for input errors not covered by another reject reason code.
35
Out of Network
41
Authorization/Access Restrictions
43
Invalid/Missing Provider Identification
44
Invalid/Missing Provider Name
45
Invalid/Missing Provider Specialty
46
Invalid/Missing Provider Phone Number
47
Invalid/Missing Provider State
49
Provider is Not Primary Care Physician
51
Provider Not on File
52
Service Dates Not Within Provider Plan Enrollment
Use for patient event dates.
79
Invalid Participant Identification
Use for invalid/missing service provider supplemental identifier.
97
Invalid or Missing Provider Address
IP
Inappropriate Provider Role
Not Used
4
889
Follow-up Action Code
O 1
ID
1

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 the notification 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 a the sender's discretion but cannot be required by the receiver.
TR3 Example:
PRV✱PE✱PXC✱203BS0133X~
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
O 1
ID
2/3
Code qualifying the Reference Identification
SEGMENT SYNTAX: P0203
CODE
DEFINITION
PXC
Health Care Provider Taxonomy Code
CODE SOURCE: 682: Health Care Provider Taxonomy
Required
3
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: P0203
INDUSTRY NAME: Provider Taxonomy Code
Not Used
4
156
State or Province Code
O 1
ID
2
Not Used
5
C035
Provider Specialty Information
O 1
Not Used
6
1223
Provider Organization Code
O 1
ID
3

NM1*L5 - ADDITIONAL PATIENT INFORMATION CONTACT 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 additional information is sent by an information contact that is different from the information source identified in loop 2010A. If not required by this implementation guide, do not send.
TR3 Example:
NM1✱L5✱2✱ACME THIRD PARTY ADMINISTRATOR~
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
L5
Contact
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 name only if the destination is an individual, such as an individual primary care physician.
2
Non-Person Entity
Situational
3
1035
Name Last or Organization Name
O 1
AN
1/60
Individual last name or organizational name
SEGMENT SYNTAX: C1203
SITUATIONAL RULE: Required when the information source needs to identify the destination by name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Response Contact 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 destination is an individual (NM102 = 1). If not required by this implementation guide, do not send.
INDUSTRY NAME: Response Contact First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when NM104 is valued and the middle name/initial of the individual is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Response Contact Middle Name
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when NM104 is valued and the suffix of the individual's name; e.g. Sr., Jr., or III., is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Response Contact Name Suffix
Situational
8
66
Identification Code Qualifier
O 1
ID
1/2
Code designating the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when the information source needs to identify the destination. If not required by this implementation guide, do not send.
CODE
DEFINITION
24
Employer's Identification Number
34
Social Security Number
46
Electronic Transmitter Identification Number (ETIN)
PI
Payor Identification
Use until the National PlanID is mandated if the destination is a payer.
XV
Centers for Medicare and Medicaid Services PlanID
Use if the destination is a payer.
CODE SOURCE: 540: Centers for Medicare and Medicaid Services PlanID
XX
Centers for Medicare and Medicaid Services National Provider Identifier
Use if the destination is a provider.
CODE SOURCE: 537: Centers for Medicare & Medicaid Services National Provider Identifier
Situational
9
67
Identification Code
O 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when NM108 is used. If not required by this implementation guide, do not send.
INDUSTRY NAME: Response Contact Identifier
Not Used
10
706
Entity Relationship Code
O 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/60

N3 - ADDITIONAL PATIENT INFORMATION CONTACT 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 request for additional patient information must be routed to a specific office location. If not required by this implementation guide, do not send.
TR3 Example:
N3✱43 SUNRISE BLVD✱SUITE 1000~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Response Contact 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 exists. If not required by this implementation guide, do not send.
INDUSTRY NAME: Response Contact Address Line

N4 - ADDITIONAL PATIENT INFORMATION 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 request for additional patient information must be routed to a specific office 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: Additional Patient Information Contact City Name
Situational
2
156
State or Province Code
O 1
ID
2
Code (Standard State/Province) as defined by appropriate government agency
COMMENT: N402 is required only if city name (N401) is in the U.S. or Canada.
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: Additional Patient Information Contact 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: Additional Patient Information Contact Postal Zone or ZIP Code
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
O 1
ID
2/3
Code identifying the country
SEGMENT SYNTAX: C0704
SITUATIONAL RULE: Required when the address is outside the United States of America. If not required by this implementation guide, do not send.
Use the alpha-2 country codes from Part 1 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
5
309
Location Qualifier
O 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
O 1
ID
1/3
Code identifying the country subdivision
SEGMENT SYNTAX: E0207, C0704
SITUATIONAL RULE: Required when the address is not in the United States of America, including its territories, or Canada, and the country in N404 has administrative subdivisions such as but not limited to states, provinces, cantons, etc. If not required by this implementation guide, do not send.
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds

PER*IC - ADDITIONAL PATIENT INFORMATION CONTACT INFORMATION

X12 Name:
Administrative Communications Contact
X12 Purpose:
To identify a person or office to whom administrative communications should be directed
X12 Syntax:
  1. P0304
    If either PER03 or PER04 is present, then the other is required.
  2. P0506
    If either PER05 or PER06 is present, then the other is required.
  3. P0708
    If either PER07 or PER08 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the request for additional patient information must be routed to a specific contact, electronic mail, facsimile, or phone number. If not required by this implementation guide, do not send.
TR3 Notes:
  1. When the communication number represents a telephone number in the United States and other countries using the North American Dialing Plan (for voice, data, fax, etc.), the communication number should always include the area code and telephone number using the format AAABBBCCCC. Where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number (e.g. (534)224-2525 would be represented as 5342242525). The extension, when applicable, should be included in the communication number immediately after the telephone number.
  2. By definition of the standard, if PER03 is used, PER04 is required.
TR3 Example:
PER✱IC✱MARY✱FX✱3135551212~
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 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 by this implementation guide, do not send.
INDUSTRY NAME: Response Contact Name
Situational
3
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0304
SITUATIONAL RULE: Required when the Information Source needs to indicate a particular contact telephone number versus the PER02. 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
O 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 to transmit a contact communication number. If not required by this implementation guide, do not send.
INDUSTRY NAME: Response Contact Communication Number
Situational
5
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
CODE
DEFINITION
EM
Electronic Mail
EX
Telephone Extension
FX
Facsimile
TE
Telephone
Situational
6
364
Communication Number
O 1
AN
1/256
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
INDUSTRY NAME: Response Contact Communication Number
Situational
7
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
CODE
DEFINITION
EM
Electronic Mail
EX
Telephone Extension
FX
Facsimile
TE
Telephone
Situational
8
364
Communication Number
O 1
AN
1/256
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
INDUSTRY NAME: Response Contact Communication Number
Not Used
9
443
Contact Inquiry Reference
O 1
AN
1/20

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 Health Care Service Review is 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:
NM1✱PW✱2✱PATIENT DIALYSIS CENT~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
O 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 Provider 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
O 1
ID
1/2
Not Used
9
67
Identification Code
O 1
AN
2/80
Not Used
10
706
Entity Relationship Code
O 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/60

N3 - PATIENT 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✱77 HOLLY BLVD~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Patient Event Provider 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 exists. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider 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✱HOLLYWOOD✱CA✱90214~
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
O 1
ID
2
Code (Standard State/Province) as defined by appropriate government agency
COMMENT: N402 is required only if city name (N401) is in the U.S. or Canada.
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when 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
O 1
ID
2/3
Not Used
5
309
Location Qualifier
O 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Not Used
7
1715
Country Subdivision Code
O 1
ID
1/3

AAA - PATIENT EVENT TRANSPORT INFORMATION REQUEST VALIDATION

X12 Name:
Request Validation
X12 Purpose:
To specify the validity of the request and indicate follow-up action authorized
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
9
Situational Rule:
Required when this is a notification of a health care services review that was rejected due to invalid or missing service provider information. If not required by this implementation guide, do not send.
TR3 Example:
AAA✱N✱✱47✱C~
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: AAA01 designates whether the request is valid or invalid. Code "Y" indicates that the code is valid; code "N" indicates that the code is invalid.
INDUSTRY NAME: Valid Request Indicator
CODE
DEFINITION
N
No
Y
Yes
Not Used
2
559
Agency Qualifier Code
O 1
ID
2
Situational
3
901
Reject Reason Code
O 1
ID
2
Code assigned by issuer to identify reason for rejection
SITUATIONAL RULE: Required when AAA01 = "N". If not required by this implementation guide, do not send.
CODE
DEFINITION
15
Required application data missing
Use when data is missing that is not covered by another reject reason code. Use to indicate when there is not enough information to identify the transport information.
33
Input Errors
Use for input errors not covered by another reject reason code.
47
Invalid/Missing Provider State
Use to code to indicate that the transport location state is invalid or missing.
97
Invalid or Missing Provider Address
Use this code to indicate that the transport location address is invalid or missing.
Required
4
889
Follow-up Action Code
O 1
ID
1
Code identifying follow-up actions allowed
CODE
DEFINITION
C
Please Correct and Resubmit
N
Resubmission Not Allowed

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 indate that the other UMO is commerical 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
O 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
O 1
ID
1/2
Not Used
9
67
Identification Code
O 1
AN
2/80
Not Used
10
706
Entity Relationship Code
O 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/60

REF*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
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Other UMO Denial Reason
Not Used
3
352
Description
O 1
AN
1/80
Situational
4
C040
Reference Identifier
O 1
To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier
SEMANTIC: REF04 contains data relating to the value cited in REF02.
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C04003 or C04004 is present, then the other is required.
  2. P0506
    If either C04005 or C04006 is present, then the other is required.
SITUATIONAL RULE: Required when the 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/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
INDUSTRY NAME: Other UMO Denial Reason
Situational
4-3
128
Reference Identification Qualifier
O 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
O 1
AN
1/50
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
Situational
4-5
128
Reference Identification Qualifier
O 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
O 1
AN
1/50
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.

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✱20050516~
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 identifying specific services associated with this patient event. If not required by this implementation guide, do not send.
TR3 Notes:
This segment identifies the service(s) and conveys the review outcome related to that service(s).
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 - 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:
3
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
The term "Current Transaction Trace Number" refers to the trace number assigned by the creator of the 278 notification transaction (the information source).
2
Referenced Transaction Trace Numbers
The term "Referenced Transaction Trace Number" refers to the trace number originally sent in the 278 notification transaction.
Required
2
127
Reference Identification
M 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: TRN02 provides unique identification for the transaction.
INDUSTRY NAME: Service Trace Number
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. If TRN01 is "2", this is the value received in the original 278 notification transaction. If TRN01 is "1", use this information to identify the UMO organization that assigned this trace number.
  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/50
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 necessary to further identify a specific component, such as a specific division or group, of the company identified in the previous data element (TRN03). If not required by this implementation guide, do not send.
INDUSTRY NAME: Trace Assigning Entity Additional Identifier

AAA - SERVICE REQUEST VALIDATION

X12 Name:
Request Validation
X12 Purpose:
To specify the validity of the request and indicate follow-up action authorized
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
9
Situational Rule:
Required when this is a notification of a health care services review that was rejected due to invalid or missing service information. If not required by this implementation guide, do not send.
TR3 Notes:
If the non-certification is related to a medical necessity/benefits decision, use the HCR segment.
TR3 Example:
AAA✱N✱✱52~
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: AAA01 designates whether the request is valid or invalid. Code "Y" indicates that the code is valid; code "N" indicates that the code is invalid.
INDUSTRY NAME: Valid Request Indicator
CODE
DEFINITION
N
No
Y
Yes
Not Used
2
559
Agency Qualifier Code
O 1
ID
2
Situational
3
901
Reject Reason Code
O 1
ID
2
Code assigned by issuer to identify reason for rejection
SITUATIONAL RULE: Required when AAA01 = "N". If not required by this implementation guide, do not send.
CODE
DEFINITION
15
Required application data missing
Use when data is missing that is not covered by another Reject Reason Code. For example, use for missing procedure codes and procedure dates.
33
Input Errors
Use for input errors in the service data not covered by the other reject reason codes listed. For example, use for invalid place of service codes and invalid procedure codes and procedure dates.
52
Service Dates Not Within Provider Plan Enrollment
57
Invalid/Missing Date(s) of Service
Use for invalid/missing service, admission, surgery, or discharge dates.
60
Date of Birth Follows Date(s) of Service
61
Date of Death Precedes Date(s) of Service
62
Date of Service Not Within Allowable Inquiry Period
AG
Invalid/Missing Procedure Code(s)
T5
Certification Information Missing
Use to indicate missing previous certification number information.
Not Used
4
889
Follow-up Action Code
O 1
ID
1

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
Use this value to identify services related to an episode of care.
SC
Specialty Care Review
Use this value to identify 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 only for appeals of review decisions where the level of service required is emergency or urgent.
2
Appeal - Standard
Use this value for appeals of review decisions where the level of service is not emergency or urgent.
3
Cancel
4
Extension
Use this value for an extension request to a prior approved service.
5
Notification
I
Initial
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 this value when revising the specifics of a notification for which services have not been rendered. For example, the Information Source may be identifying additional procedures or other procedures for the same patient event.
Situational
3
1365
Service Type Code
O 1
ID
1/2
Code identifying the classification of service
SITUATIONAL RULE: Required when different from the UM03 value at the Patient Event level (Loop 2000E) or when the SV1, or SV2, or SV3 is not valued in this Service loop. If not required by this implementation guide, do not send.
Values at the Service Level override the values entered at the Patient Event Level for this service.
CODE
DEFINITION
1
Medical Care
2
Surgical
3
Consultation
4
Diagnostic X-Ray
5
Diagnostic Lab
6
Radiation Therapy
7
Anesthesia
8
Surgical Assistance
11
Used Durable Medical Equipment
12
Durable Medical Equipment Purchase
14
Renal Supplies in the Home
15
Alternate Method Dialysis
16
Chronic Renal Disease (CRD) Equipment
17
Pre-Admission Testing
18
Durable Medical Equipment Rental
20
Second Surgical Opinion
21
Third Surgical Opinion
23
Diagnostic Dental
24
Periodontics
25
Restorative
Use for restorative dental services.
26
Endodontics
27
Maxillofacial Prosthetics
28
Adjunctive Dental Services
33
Chiropractic
35
Dental Care
36
Dental Crowns
37
Dental Accident
38
Orthodontics
39
Prosthodontics
40
Oral Surgery
42
Home Health Care
44
Home Health Visits
45
Hospice
46
Respite Care
54
Long Term Care
56
Medically Related Transportation
61
In-vitro Fertilization
62
MRI/CAT Scan
63
Donor Procedures
64
Acupuncture
65
Newborn Care
66
Pathology
67
Smoking Cessation
68
Well Baby Care
69
Maternity
70
Transplants
71
Audiology Exam
72
Inhalation Therapy
73
Diagnostic Medical
74
Private Duty Nursing
75
Prosthetic Device
76
Dialysis
77
Otological Exam
78
Chemotherapy
79
Allergy Testing
80
Immunizations
82
Family Planning
83
Infertility
84
Abortion
85
AIDS
86
Emergency Services
88
Pharmacy
93
Podiatry
A4
Psychiatric
A6
Psychotherapy
A9
Rehabilitation
AD
Occupational Therapy
AE
Physical Medicine
AF
Speech Therapy
AG
Skilled Nursing Care
AI
Substance Abuse
AJ
Alcoholism
AK
Drug Addiction
AL
Vision (Optometry)
AR
Experimental Drug Therapy
B1
Burn Care
BB
Partial Hospitalization (Psychiatric)
BC
Day Care (Psychiatric)
BD
Cognitive Therapy
BE
Massage Therapy
BF
Pulmonary Rehabilitation
BG
Cardiac Rehabilitation
BL
Cardiac
BN
Gastrointestinal
BP
Endocrine
BQ
Neurology
BS
Invasive Procedures
BY
Physician Visit - Office: Sick
BZ
Physician Visit - Office: Well
C1
Coronary Care
GY
Allergy
IC
Intensive Care
MH
Mental Health
NI
Neonatal Intensive Care
ON
Oncology
PT
Physical Therapy
PU
Pulmonary
RN
Renal
RT
Residential Psychiatric Treatment
TC
Transitional Care
TN
Transitional Nursery Care
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: C023-02 qualifies C023-01 and C023-03.
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.
Values at the Service Level override the values entered at the Patient Event Level for this service.
Required
4-1
1331
Facility Code Value
M 1
AN
1/2
Code identifying where services were, or may be, performed; the first and second positions of the Uniform Bill Type Code for Institutional Services or the Place of Service Codes for Professional or Dental Services.
INDUSTRY NAME: Facility Type Code
Use to indicate a facility code value from the code source referenced in UM04-2.
Required
4-2
1332
Facility Code Qualifier
O 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

HCR - HEALTH CARE SERVICES REVIEW

X12 Name:
Health Care Services Review
X12 Purpose:
To specify the outcome of a health care services review
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the HCR segment is not used in 2000E, or if HCR01 in 2000E is A2. If not required by this implementation guide, do not send.
TR3 Notes:
If the HCR segment is sent in this 2000F Service level loop, it will override an HCR segment sent in the Patient Event loop (2000E) for this service only.
TR3 Example:
HCR✱A1✱20020713~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
306
Action Code
M 1
ID
1/2
Code indicating type of action
Certification Action Code
CODE
DEFINITION
A1
Certified in total
A3
Not Certified
A4
Pended
A6
Modified
C
Cancelled
CT
Contact Payer
NA
No Action Required
Use only if certification is not required.
Situational
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: HCR02 is the number assigned by the information source to this review outcome.
SITUATIONAL RULE: Required when HCR01 = A1, or A6. If not required by this implementation guide, do not send.
INDUSTRY NAME: Review Identification Number
Situational
3
1271
Industry Code
O 5
AN
1/30
Code indicating a code from a specific industry code list
SEMANTIC: HCR03 is the code assigned by the information source to identify the reason for the health care service review outcome indicated in HCR01.See Code Source 886
SITUATIONAL RULE: Required when HCR01 = A3, or A4. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
INDUSTRY NAME: Review Decision Reason Code
The HCR03 data element is a repeating data element and can be repeated up to the maximum allowed by the standard in this implementation guide.
Situational
4
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: HCR04 is the second surgical opinion indicator. A "Y" value indicates a second surgical opinion is required; an "N" value indicates a second surgical opinion is not required for this request.
SITUATIONAL RULE: Required when certification pertains to a surgical procedure and the contract under which the patient is covered has provisions regarding a second surgical opinion. If not required by this implementation guide, do not send.
INDUSTRY NAME: Second Surgical Opinion Indicator
CODE
DEFINITION
N
No
Y
Yes

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 (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✱123A~
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
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Previous Review Authorization Number
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*NT - 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 Information receiver for the original acknowledgment of the notification associated with this service review. This is not the trace number assigned by the requester.
TR3 Example:
REF✱NT✱Y789~
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
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Administrative Reference Number
Not Used
3
352
Description
O 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 Notes:
Use this segment for the valid date(s) during which the service can be performed.
TR3 Example:
DTP✱472✱D8✱20050723~
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

DTP*102 - CERTIFICATION ISSUE 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 Certification Issue Date is different from the Patient Event Certification Issue Date in Loop 2000E. If not required by this implementation guide, do not send.
TR3 Notes:
Use this segment for the date when the certification was issued.
TR3 Example:
DTP✱102✱D8✱20050701~
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
102
Issue
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Certification Issue Date

DTP*036 - CERTIFICATION EXPIRATION 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 Certification Expiration Date is different from the Patient Event Certification Expiration Date in Loop 2000E. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱036✱D8✱20050731~
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
036
Expiration
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Certification Expiration Date

DTP*007 - CERTIFICATION EFFECTIVE 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 different from the Certification Effective Date in Loop 2000E. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱007✱RD8✱20050701-20050731~
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
007
Effective
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: Certification Effective 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 identifying 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.
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
Health Care Financing Administration Common Procedural Coding System (HCPCS) Codes
Because the AMA's CPT codes are also level 1 HCPCS codes, they are reported under HC.
CODE SOURCE: 130: Healthcare Common Procedure Coding System
IV
Home Infusion EDI Coalition (HIEC) Product/Service Code
This code set is not allowed for use under HIPAA at the time of this writing. Use only in non-HIPAA implementations.
CODE SOURCE: 513: Home Infusion EDI Coalition (HIEC) Product/Service Code List
N4
National Drug Code in 5-4-2 Format
CODE SOURCE: 240: National Drug Code by Format
Required
1-2
234
Product/Service ID
M 1
AN
1/48
Identifying number for a product or service
INDUSTRY NAME: Procedure Code
Situational
1-3
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when the information source needs to convey additional clarification to miscellaneous, unspecified, or non descriptive procedures or modifiers. If not required by this implementation guide, do not send.
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 the information source needs to convey additional clarification to miscellaneous, unspecified, or non descriptive procedures or modifiers. If not required by this implementation guide, do not send.
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 the information source needs to convey additional clarification to miscellaneous, unspecified, or non descriptive procedures or modifiers. If not required by this implementation guide, do not send.
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 the information source needs to convey additional clarification to miscellaneous, unspecified, or non descriptive procedures or modifiers. If not required by this implementation guide, do not send.
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 information source needs to convey additional clarification to miscellaneous, unspecified, or non descriptive procedures or modifiers. 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/48
Identifying number for a product or service
SITUATIONAL RULE: Required when the information source has not determined the intensity or complexity of the services and therefore identifies a range of procedures. If not required by this implementation guide, do not send.
INDUSTRY NAME: Product or Service ID
Use SV101-2 to represent the beginning value in a procedure range and this data element to represent the ending value in a range of codes.
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 Notification or Information Copy had monetary limitations for the service. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Line Amount
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
SEGMENT SYNTAX: P0304
SITUATIONAL RULE: Required when service units were not provided in the HSD segment and a specific number of services are being identified 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
O 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 identified 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/2
Not Used
6
1365
Service Type Code
O 1
ID
1/2
Situational
7
C004
Composite Diagnosis Code Pointer
O 1
To identify one or more diagnosis code pointers
X12 COMPOSITE SEMANTIC NOTES:
  1. C004-01 identifies the primary diagnosis code for this service line.
  2. C004-02 identifies the second diagnosis code for this service line.
  3. C004-03 identifies the third diagnosis code for this service line.
  4. C004-04 identifies the fourth diagnosis code for this service line.
SITUATIONAL RULE: Required when this procedure relates to a specific diagnosis reported in HI Loop 2000E to point to the specific diagnosis. If not required by this implementation guide, do not send.
If no diagnosis pointer is provided, then this procedure applies to all diagnoses.
Required
7-1
1328
Diagnosis Code Pointer
M 1
N
1/2
A pointer to the diagnosis code in the order of importance to this service
Situational
7-2
1328
Diagnosis Code Pointer
O 1
N
1/2
A pointer to the diagnosis code in the order of importance to this service
SITUATIONAL RULE: Required when procedure is related to more than one diagnosis. If not required by this implementation guide, do not send.
Use this pointer for the second diagnosis code pointer.
Situational
7-3
1328
Diagnosis Code Pointer
O 1
N
1/2
A pointer to the diagnosis code in the order of importance to this service
SITUATIONAL RULE: Required when procedure is related to more than two diagnosis. If not required by this implementation guide, do not send.
Use this pointer for the third diagnosis code pointer.
Situational
7-4
1328
Diagnosis Code Pointer
O 1
N
1/2
A pointer to the diagnosis code in the order of importance to this service
SITUATIONAL RULE: Required when procedure is related to more than three diagnosis. If not required by this implementation guide, do not send.
Use this pointer for the fourth diagnosis code pointer.
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 review decision 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/50
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 LINE

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 identifying a specific Institutional Service, or a specific Revenue Code for the Institutional Service. If not required by this implementation guide, do not send.
TR3 Example:
  1. SV2✱300✱HC:80019✱73.42✱UN✱1~
  2. SV2✱120✱✱1500✱DA✱5✱300~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Situational
1
234
Product/Service ID
O 1
AN
1/48
Identifying number for a product or service
SEMANTIC: SV201 is the revenue code.
SEGMENT SYNTAX: R0102
SITUATIONAL RULE: Required when the service review decision was determined using 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
O 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.
SITUATIONAL RULE: Required when identifying 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
Health Care Financing Administration Common Procedural Coding System (HCPCS) Codes
Because the AMA's CPT codes are also level 1 HCPCS codes, they are reported under HC.
CODE SOURCE: 130: Healthcare Common Procedure Coding System
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)
IV
Home Infusion EDI Coalition (HIEC) Product/Service Code
This code set is not allowed for use under HIPAA at the time of this writing. Use only in non-HIPAA implementations.
CODE SOURCE: 513: Home Infusion EDI Coalition (HIEC) Product/Service Code List
N4
National Drug Code in 5-4-2 Format
CODE SOURCE: 240: National Drug Code by Format
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
ZZ
Mutually Defined
Use this code when reporting ICD-10-PCS. This code can only be used if mandated by HIPAA or for services not covered under HIPAA.
CODE SOURCE 896: International Classification of Diseases, 10th Revision, Procedure Coding System
Required
2-2
234
Product/Service ID
M 1
AN
1/48
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 the information source needs to convey additional clarification to miscellaneous, unspecified, or non descriptive procedures or modifiers. 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 the information source needs to convey additional clarification to miscellaneous, unspecified, or non descriptive procedures or modifiers. 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 the information source needs to convey additional clarification to miscellaneous, unspecified, or non descriptive procedures or modifiers. 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 the information source needs to convey additional clarification to miscellaneous, unspecified, or non descriptive procedures or modifiers. 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 information source needs to convey additional clarification to miscellaneous, unspecified, or non descriptive procedures or modifiers. If not required by this implementation guide, do not send.
INDUSTRY NAME: Procedure Code Description
Situational
2-8
234
Product/Service ID
O 1
AN
1/48
Identifying number for a product or service
SITUATIONAL RULE: Required when the information source has not determined the intensity or complexity of the service to be performed and therefore identifies a range of procedures. If not required by this implementation guide, do not send.
INDUSTRY NAME: Product or Service ID
Use SV202-2 to represent the beginning value in the procedure range and this data element to represent the ending value in a range of codes.
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 Notification or Information Copy had monetary limitations for the service. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Line Amount
Situational
4
355
Unit or Basis for Measurement Code
O 1
ID
2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
SEGMENT SYNTAX: P0405
SITUATIONAL RULE: Required when service units were not provided in the HSD segment and a specific number of services are being identified for this procedure. If not required by this implementation guide, do not send.
CODE
DEFINITION
DA
Days
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).
UN
Unit
Situational
5
380
Quantity
O 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 identified 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 used and the Notification or Information Copy had monetary limitations on the accommodation rate. 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 identifying services 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)
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 identified for admissions to a nursing facility, or for identification for a 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 identifying a specific Dental Service. If not required by this implementation guide, do not send.
TR3 Example:
SV3✱AD:D2150✱80✱✱✱✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
C003
Composite Medical Procedure Identifier
M 1
To identify a medical procedure by its standardized codes and applicable modifiers
X12 COMPOSITE SEMANTIC NOTES:
  1. C003-01 qualifies C003-02 and C003-08.
  2. If C003-08 is used, then C003-02 represents the beginning value in the range in which the code occurs.
  3. C003-03 modifies the value in C003-02 and C003-08.
  4. C003-04 modifies the value in C003-02 and C003-08.
  5. C003-05 modifies the value in C003-02 and C003-08.
  6. C003-06 modifies the value in C003-02 and C003-08.
  7. C003-07 is the description of the procedure identified in C003-02.
  8. C003-08 represents the ending value in the range in which the code occurs.
Required
1-1
235
Product/Service ID Qualifier
M 1
ID
2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
INDUSTRY NAME: Product or Service ID Qualifier
CODE
DEFINITION
AD
American Dental Association Codes
CODE SOURCE: 135: American Dental Association
Required
1-2
234
Product/Service ID
M 1
AN
1/48
Identifying number for a product or service
INDUSTRY NAME: Procedure Code
Situational
1-3
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when the information source needs to convey additional clarification to miscellaneous, unspecified, or non descriptive procedures or modifiers. 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', if such modifier is available.
  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 the information source needs to convey additional clarification to miscellaneous, unspecified, or non descriptive procedures or modifiers. 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', if such modifier is available.
  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 the information source needs to convey additional clarification to miscellaneous, unspecified, or non descriptive procedures or modifiers. 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', if such modifier is available.
  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 the information source needs to convey additional clarification to miscellaneous, unspecified, or non descriptive procedures or modifiers. 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', if such modifier is available.
  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 information 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 InitialEndodontic 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/48
Identifying number for a product or service
SITUATIONAL RULE: Required when the information source has not determined the intensity or complexity of the service to be performed and therefore indicates a range of procedures. If not required by this implementation guide, do not send.
INDUSTRY NAME: Product or Service ID
Use SV301-2 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
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: SV302 is the submitted service line item amount.
SITUATIONAL RULE: Required when the Notification or Information Copy had monetary limitations for the service. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Line Amount
Not Used
3
1331
Facility Code Value
O 1
AN
1/2
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
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.
Use this code for the additional oral cavity designation codes. The code values in SV304-1 apply to all occurrences of the oral cavity designation code.
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.
Use this code for the additional oral cavity designation codes. The code values in SV304-1 apply to all occurrences of the oral cavity designation code.
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.
Use this code for the additional oral cavity designation codes. The code values in SV304-1 apply to all occurrences of the oral cavity designation code.
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.
Use this code for the additional oral cavity designation codes. The code values in SV304-1 apply to all occurrences of the oral cavity designation code.
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. If not required by this implementation guide, do not send.
INDUSTRY NAME: Prosthesis, Crown, or Inlay Code
CODE
DEFINITION
I
Initial Placement
R
Replacement
Required
6
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: SV306 is the number of procedures.
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 to 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
Not Used
11
C004
Composite Diagnosis Code Pointer
O 1

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
O 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
O 1
AN
1/30
Code indicating a code from a specific industry code list
SEGMENT SYNTAX: P0102
INDUSTRY NAME: Tooth Code
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-1.
CODE
DEFINITION
B
Buccal
D
Distal
F
Facial
I
Incisal
L
Lingual
M
Mesial
O
Occlusal
Situational
3-3
1369
Tooth Surface Code
O 1
ID
1/2
Code identifying the area of the tooth that was treated
SITUATIONAL RULE: Required when necessary to report a third tooth surface. If not required by this implementation guide, do not send.
Use code values from TOO03-1.
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-1.
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.
Use code values from TOO03-1.
CODE
DEFINITION
B
Buccal
D
Distal
F
Facial
I
Incisal
L
Lingual
M
Mesial
O
Occlusal

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 identifying 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
O 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
O 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
Service Quantity
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.
If HSD02 is not valued, do not use.
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
O 1
ID
1/2
Code defining periods
SEGMENT SYNTAX: C0605
SITUATIONAL RULE: Required when HSD06 is valued to qualify the time period in which the quantity of services (HSD02) 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 needed to indicate the calendar delivery pattern for the services. 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:
P0506
If either PWK05 or PWK06 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
10
Situational Rule:
Required when the information source has additional documentation (electronic, paper, or other medium) associated with this health care services review that applies to the service(s) in this Service loop, and the 278 Notification, or Information Copy (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 information requested 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 information source can also use this PWK segment to identify paperwork that is held at the provider's office and is available upon request by the information receiver. Use code AA in PWK02 to convey this specific use of the PWK segment. See code note under PWK02, code AA.
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
HP
History and Physical
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
T7
Therapy Notes
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
This means that the paperwork is not being sent with the notification at this time. Instead, it is available to the Information Receiver upon 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
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
O 1
ID
1/2
Code designating the system/method of code structure used for Identification Code (67)
COMMENT: PWK05 and PWK06 may be used to identify the addressee by a code number.
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when PWK06 is used. If not required by this implementation guide, do not send.
CODE
DEFINITION
AC
Attachment Control Number
Situational
6
67
Identification Code
O 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when PWK02 equals BM, EL, EM 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 Information Source can use when PWK02 equals "AA" if the Inforamtion Source 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

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 Information Receiver about the service. If not required by this implementation guide, do not send.
TR3 Notes:
  1. Free form text or description fields are not recommended because they require human interpretation.
  2. 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
O 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 identifying a service provider, specialist, or specialty entity for this service and is different from the provider, specialist, or specialty entity identified in Loop 2010EA (Patient Event Provider Name). 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 Loop 2010EA is not valued, Loop 2010F must be valued for each service associated with this patient event.
TR3 Example:
NM1✱SJ✱1✱WATSON✱SUSAN✱✱✱✱34✱987654321~
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
O 1
AN
1/60
Individual last name or organizational name
SEGMENT SYNTAX: C1203
SITUATIONAL RULE: Required when identifying a specialty person, facility, group practice, or clinic and NM108/NM109 are not present. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
INDUSTRY NAME: Service Provider Last or Organization Name
Not Used if identifying a specialty entity.
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, may be provided at the sender's discretion, but cannot be required by the receiver.
INDUSTRY NAME: Service Provider Name Prefix
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when the suffix is needed to further identify the Service Provider: 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
O 1
ID
1/2
Code designating the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when 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
24
Employer's Identification Number
34
Social Security Number
46
Electronic Transmitter Identification Number (ETIN)
XX
Centers for Medicare and Medicaid Services National Provider Identifier
Required for providers on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider has an NPI and it is available to the submitter.
OR
Required for providers before the mandated HIPAA NPI implementation date when the provider has an NPI and the submitter has the capability to send it.

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
O 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
O 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/60

REF - 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 on or after the mandated implementation date for the HIPAA National Provider Identifier (NPI) when the provider is not a specialty entity and the NPI is not reported in NM109 of this loop and another identifier is available to the submitter.
OR
Required prior to the mandated NPI implementation date when an additional identification number to the NPI provided in NM109 of this loop is necessary for the UMO to identify the patient event provider (2010E) service provider (2010F).
OR
Required prior to the mandated NPI implementation date when necessary for the UMO to identify the patient event provider (2010E) service provider (2010F).
If not required by this implementation guide, do not send.
TR3 Notes:
Use the NM1 segment for the primary identifier.
TR3 Example:
REF✱1G✱123456~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
0B
State License Number
1G
Provider UPIN Number
1J
Facility ID Number
EI
Employer's Identification Number
Not used if NM108 = 24.
G5
Provider Site Number
N5
Provider Plan Network Identification Number
N7
Facility Network Identification Number
SY
Social Security Number
The social security number may not be used for any Federally administered programs such as Medicare or CHAMPUS. Not used if NM108 = 34.
ZH
Carrier Assigned Reference Number
Use for the provider ID as assigned by the UMO identified in Loop 2000A.
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Service Provider Supplemental Identifier
Situational
3
352
Description
O 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 needed to identify a specific location for a provider that has multiple locations. If not required by this implementation guide, do not send.
TR3 Example:
N3✱77 HOLLY BLVD~
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 service provider's address.
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when a second address line exists. 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 needed to identify a specific location for a provider that has multiple locations. 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
O 1
ID
2
Code (Standard State/Province) as defined by appropriate government agency
COMMENT: N402 is required only if city name (N401) is in the U.S. or Canada.
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: 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
O 1
ID
2/3
Code identifying the country
SEGMENT SYNTAX: C0704
SITUATIONAL RULE: Required when the address is outside the United States of America. If not required by this implementation guide, do not send.
Use the alpha-2 country codes from Part 1 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
5
309
Location Qualifier
O 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
O 1
ID
1/3
Code identifying the country subdivision
SEGMENT SYNTAX: E0207, C0704
SITUATIONAL RULE: Required when the address is not in the United States of America, including its territories, or Canada, and the country in N404 has administrative subdivisions such as but not limited to states, provinces, cantons, etc. If not required by this implementation guide, do not send.
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds

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:
1
Situational Rule:
Required when needed to identify a contact name and/or communications 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 should always include the area code and telephone number using the format AAABBBCCCC. Where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number (e.g. (534)224-2525 would be represented as 5342242525). The extension, when applicable, should be included in the communication number immediately after the telephone number.
TR3 Example:
PER✱IC✱M TUCKER✱TE✱8189993456✱FX✱8185551212~
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 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 by this implementation guide, do not send.
INDUSTRY NAME: Service Provider Contact Name
Situational
3
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0304
SITUATIONAL RULE: Required when the Information Source needs to indicate a particular contact telephone number versus the PER02. 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
O 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 when the information source needs 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
O 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
CODE
DEFINITION
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
O 1
AN
1/256
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Provider Contact Communication Number
Situational
7
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
CODE
DEFINITION
EM
Electronic Mail
EX
Telephone Extension
When used, the value following this code is the extension for the preceding communications contact number.
TE
Telephone
UR
Uniform Resource Locator (URL)
Situational
8
364
Communication Number
O 1
AN
1/256
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Provider Contact Communication Number
Not Used
9
443
Contact Inquiry Reference
O 1
AN
1/20

AAA - SERVICE PROVIDER REQUEST VALIDATION

X12 Name:
Request Validation
X12 Purpose:
To specify the validity of the request and indicate follow-up action authorized
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
9
Situational Rule:
Required when this is a notification of a health care services review that was rejected due to invalid or missing service provider information. If not required by this implementation guide, do not send.
TR3 Example:
AAA✱N✱✱43~
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: AAA01 designates whether the request is valid or invalid. Code "Y" indicates that the code is valid; code "N" indicates that the code is invalid.
INDUSTRY NAME: Valid Request Indicator
CODE
DEFINITION
N
No
Y
Yes
Not Used
2
559
Agency Qualifier Code
O 1
ID
2
Situational
3
901
Reject Reason Code
O 1
ID
2
Code assigned by issuer to identify reason for rejection
SITUATIONAL RULE: Required when AAA01 = "N". If not required by this implementation guide, do not send.
CODE
DEFINITION
15
Required application data missing
Use when data is missing that is not covered by another reject reason code. Use to indicate when there is not enough information to identify the service provider.
33
Input Errors
Use for input errors not covered by another reject reason code.
35
Out of Network
41
Authorization/Access Restrictions
43
Invalid/Missing Provider Identification
44
Invalid/Missing Provider Name
45
Invalid/Missing Provider Specialty
46
Invalid/Missing Provider Phone Number
47
Invalid/Missing Provider State
49
Provider is Not Primary Care Physician
51
Provider Not on File
52
Service Dates Not Within Provider Plan Enrollment
79
Invalid Participant Identification
97
Invalid or Missing Provider Address
Not Used
4
889
Follow-up Action Code
O 1
ID
1

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 a the sender's discretion but cannot be required by the receiver.
TR3 Example:
PRV✱PE✱PXC✱203BS0133X~
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
O 1
ID
2/3
Code qualifying the Reference Identification
SEGMENT SYNTAX: P0203
CODE
DEFINITION
PXC
Health Care Provider Taxonomy Code
CODE SOURCE: 682: Health Care Provider Taxonomy
Required
3
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: P0203
INDUSTRY NAME: Provider Taxonomy Code
Not Used
4
156
State or Province Code
O 1
ID
2
Not Used
5
C035
Provider Specialty Information
O 1
Not Used
6
1223
Provider Organization Code
O 1
ID
3

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 Numbers in ST02 and SE02 must be identical. The number is assigned by the originator and must be unique within a functional group (GS-GE). For example, start with the number 0001 and increment from there. The number also aids in error resolution research.

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

278 Health Care Services Review Notification and Acknowledgment (005010X216, 005010X216E1, 005010X216E2)

FEBRUARY 2010

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

All rights reserved.

Abstract

The Health Care Services Review Notification and Acknowledgment Implementation Guide describes the use of the ANSI ASC X12 Health Care Services Review Information (278) Version/Release 005010 transaction set for the following business usage:

Notification of interested parties concerning events related to a health care services review such as:

  • Patient arrival notice
  • Patient discharge notice
  • Patient transfer notice
  • Notification of certification to primary care physician (PCP), utilization management organization (UMO), or other service providers
  • Certification notice change

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 send and receive notifications using the ANSI 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 notification. The intention of the developers of the 278 is represented in this guide.

This implementation guide is designed to assist those who send, receive and/or route notifications associated with health care review outcomes that include the following:

  • Advance Notification of authorizations for planned or scheduled admissions, health services, specialty referrals.
  • Completion Notification of admissions and discharges that have occurred or the completion of the delivery of previously authorized health care services.
  • Information Copy or courtesy copy to notify a receiving entity of a health care services review outcome.
  • Acknowledgment of receipt of a health care services review notification or information copy.

Notifications do not necessarily require a response because the decision outcome has already been established. Similarly, an information copy does not require verification, or approval. However this guide does provide the ability to respond to a notification or information copy specifically to acknowledge receipt of the transmission and to address error conditions identified during application layer processing.

Health care entities that use this implementation of the 278 include, but are not limited to the following:

  • Utilization Management Organizations (UMOs) (e.g., insurance companies, health maintenance organizations, preferred provider organizations, health care purchasers, professional review organizations, other providers, and other utilization review entities) that send, or receive notifications regarding Health Care Services review information.
  • Providers (e.g., physicians, medical groups, independent physician associations, facilities) who send notifications regarding Health Care Services review information to UMOs, or to other providers.
  • Providers who receive notifications.

1.2 Version Information

This implementation guide is based on the October 2003 ASC X12 standards, referred to as Version 5, Release 1, Sub-release 0 (005010).

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

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.


1.3.1 Batch and Real-time Usage

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

Batch - In a batch mode the sender does not remain connected while the receiver processes the transactions. Processing is usually completed according to a set schedule. If there is an associated business response transaction (such as a 271 Response to a 270 Request for Eligibility), the receiver creates the response transaction and stores it for future delivery. The sender of the original transmission reconnects at a later time and picks up the response transaction. This implementation guide does not set specific response time parameters for these activities.

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

This implementation guide is intended to support use in batch mode. This implementation guide is intended to support use in real-time mode. A statement that the transaction is not intended to support a specific mode does not preclude its use in that mode between willing trading partners.


1.3.2 Other Usage Limitations

Real Time Delivery of the 278

A 278 real time notification transaction and its associated acknowledgment 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 at least one occurrence each of Loop 2000E and/or Loop 2000F representing one to many service providers and the associated services.

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

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.


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 Business Events Supported in this Guide

This implementation guide supports the following health care service review business events.


1.4.1.1 Notification

The 278 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, 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 provider(s), service provider(s), or other Health Care entities requiring the information for specific purposes. An information copy can also be used for hospital census reporting.

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


1.4.1.2 Acknowledgment

Acknowledgments are sent from a notification receiver to the notification sender to indicate the successful receipt or rejection of a notification or information copy.

Note: This implementation guide does not require that the information receiver return 278 acknowledgment responses for notifications received. Acknowledgments are required only if the information receiver was unable to receive the notification or information copy or if the information source has indicated that a receipt acknowledgment is required. The information receiver's system can return a 997 Functional Acknowledgment to indicate the acceptance or rejection of a transaction based on syntactical checks of the data format and content.

The notification process transfers data from one source to another. In most instances, a simple acknowledgment from the receiver to the sender is sufficient to verify that the receiver has received and processed the data content of the notification. The information receiver has the flexibility to either respond at a high level for successful transaction processing, or at a detail level when the data received produced specific application layer processing errors.

In addition, this implementation guide supports the ability to indicate the acceptance or rejection of the notification based on its application data content. The information receiver can return one of the following types of 278 acknowledgments, as specified in the BHT02.

Completion: BHT02 = 53 (Completion) indicates the successful receipt of a notification. Its content identifies the information source, information receiver and the subscriber/patient. It supports a reference segment (Notification Receipt Number) at the patient level to enable the information receiver to return a receipt number associated with this patient event notification. The receiver can return service provider and service information, along with a service notification receipt number, to indicate successful receipt of the information at the service detail.

Rejection: In many business scenarios, the information receiver verifies the application data before accepting the notification or information copy from the information source. The information receiver can reject the notification based on invalid or missing data content or discrepancies between the patient's coverage and the service detail reported. BHT02 = 44 (Rejection) indicates that the information receiver rejected the notification due to system errors or errors in the application data content. It reports the reasons for rejection at the appropriate hierarchical level.


1.4.2 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. A brief description of these business events follows.

Request for Review and Response

Health Care Services Review - Request and Response includes 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

The exchange of information is between the primary parties, the provider and the UMO.

X12N 278 Health Care Services Review - Request for Review and Response At the time of publication, implementation guides (004010X094A) and (004010X094A1) are the adopted HIPAA standard for the referral certification and authorization transaction.

Review Inquiry and Response

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. The primary participants are providers and UMOs. The entity initiating the inquiry is either the primary provider or the service provider.

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.4.3 Notification Information Flows

Figure 1.1 Information Flows, illustrates various examples of information flow for different business needs requiring the health care services review notification.

Example 1: Advance Notification

A provider notifies the UMO of an inpatient stay to occur in the future. The UMO returns an acknowledgment indicating that the notice has been received.

Figure 1.1. Advance Notification

Example 2: Completion Notification

A delegated entity notifies the UMO of all discharges that have occurred for a given date span. The UMO acknowledges receipt by returning a receipt number for each discharge notification. The receipt number indicates that the UMO has stored data to support the claims payment process.

Figure 1.2. Completion Notification

Example 3: Information Copy

A delegated entity notifies the payer of all authorized services for multiple patients for a particular time span.

Figure 1.3. Information Copy

Example 4: Information Copy

UMO notifying a preferred special review organization on specific patient events to support proactive disease management and/or other preventative care programs.

Figure 1.4. Information Copy


1.5 Business Terminology

This section contains definitions of terms frequently used in Section 2 of this implementation guide. Refer to Appendix E Data Element Name Index for a list of the data element names used in this implementation guide and their associated definitions.

Acknowledgment
A transaction sent from a notification receiver to the notification sender to indicate the receipt of a notification or information copy or its non-receipt due to system or application level errors.

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

Delegated Entity
An entity assigned by another entity to perform services on their behalf. This arrangement is usually contractual in nature. Examples may include the following:

  1. payer assigns an outside professional utilization management entity to complete all health care decisions on their behalf, but the payer retains responsibility for claim payment processing
  2. a UMO makes all medical decisions, but delegates the claim payment process to an outside resource

Information Copy
An unsolicited 278 transaction that provides a courtesy copy of a health care services review or the change of status of a previously authorized health care services review.

Information Receiver
The entity that is the receiver of the notification or information copy. This entity is carried in Loop 2000B in both the Notification and Acknowledgment.

Information Sender
The entity responsible for sending the notification or information copy of the outcome of the health care service review request.

Information Source
The entity that is the originator of the health care services review or the entity that determined the outcome of a health care services review. The information sender and information source may be the same entity. This entity is carried in the Loop 2000A in both the Notification and Acknowledgment.

Notification
An unsolicited 278 transaction that notifies the recipient of the outcome of a health care services review and or the change of status of a previously authorized health care services review.

Patient event
Patient event in this guide refers to the service or group of services associated with a single episode of care. Examples include the following:

  • an admission to a facility for treatment related to a specific patient condition or diagnosis or related group of diagnoses
  • a referral to a specialty provider for a consult or testing to determine a specific diagnosis and appropriate treatment
  • services to be administered at a patient visit such as chiropractic treatment delivered in a single patient visit. The same treatment can be approved for a series of visits.

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 type of authorization initiated by the patient's primary care provider (PCP) that enables the patient to receive consultation and/or services of a specialist or specialty entity. Under some UMO arrangements, the PCP is authorized to refer the patient without seeking the permission of the UMO/review entity.

Requester
Requester refers to providers (e.g., physicians, medical groups, independent physician associations, facilities) who request information on referrals or certifications for a patient to receive health care services.

Service Provider
Service provider is the referred-to provider, specialist, specialty entity, group, or facility where the medical services are to be performed.

Utilization Management Organization (UMO)
UMO refers to insurance companies, health maintenance organizations, preferred provider organizations, health care purchasers, professional review organizations, third-party administrators, other providers, and other utilization review entities that receive and respond to health care service review requests and inquiries. The UMO may or may not be the organization that makes the medical decision. The UMO might have a relationship with a payer that calls for the payer to make a decision or store information on completed referrals and certifications. It is the role of the UMO to forward that request or inquiry to the payer, receive the response from the payer, and then return the response to the requester. From the requester's perspective, the exchange of information is between the requester and the UMO.


1.6 Transaction Acknowledgments

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


1.6.1 997 Functional Acknowledgment

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

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

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

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


1.6.2 999 Implementation Acknowledgment

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

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

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

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


1.6.3 824 Application Advice

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

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

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

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


1.7 Related Transactions

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

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

This implementation guide has been developed for use as an insurance industry implementation guide. At the time of publication it has not been adopted as a HIPAA standard. Should the Secretary adopt this implementation guide as a standard, the Secretary will establish compliance dates for its use by HIPAA covered entities.


1.10 National Provider Identifier Usage within the HIPAA 278 Transaction

Background

The final rule for the National Provider Identifier presents challenges that have a direct impact on Health Care Service Reviews. This section describes how to address the following challenges:

  • Providers who are not eligible for enumeration
  • Implementation migration strategy
  • Organization health care provider subpart representation

1.10.1 Providers who are Not Eligible for Enumeration

Only providers who meet the definition of health care provider at 45 CFR 160.103 are eligible to receive NPIs. There are providers within the industry who do not meet the definition of health care provider, but still use the 278 Health Care Services Review mandated by HIPAA. Examples of these providers include taxi drivers, carpenters, personal care providers, etc. The fact that these professions perform services, which are authorized by some health plans requires this implementation guide to accommodate both the NPI (to identify health care providers) and proprietary identifiers (to identify atypical/non-health care providers).


1.10.2 Implementation Migration Strategy

During the transition period (for example, the period from May 23, 2005 until the NPI compliance dates), it will be necessary to accommodate both the NPI and proprietary identifiers to identify health care providers in the same standard health care services review transaction. This will allow health care providers to demonstrate to their trading partners their NPIs in relation to their proprietary identifier(s). Health plans may attempt a match routine using the National Provider System (NPS) data. This strategy will enable these health plans to validate the results of their match. There are others who may choose to build table crosswalks on their own. Again, this strategy enables validation of any matches or tables using actual data received from the health care providers.


1.10.3 Organization Health Care Provider Subpart Representation

The NPI Final Rule allows an organization health care provider to designate subparts to identify various components of the organization in standard transactions. A subpart cannot be a person (for example, a subpart cannot be a health care provider who is an individual.) The minimum level of subpart creation is discussed in various federal regulations. The organization health care provider will need to determine whether additional subpart enumeration is necessary or not.

If the requesting provider is an organization, the subpart reported MUST always represent the most detailed level of enumeration as determined by the organization health care provider and MUST be the same identifier sent to any trading partner.


1.11 Data Overview

The 278 can be exchanged between interested participants in a bi-directional notification/acknowledgment mode of operation. In this mode, an information source sends a notification or information copy and an information receiver acknowledges receipt of that notification. This implementation guide does not require that the information receiver acknowledge receipt of a notification.

However, it addresses this bi-directional use to support cases when:

  • the information receiver returns rejection information to indicate that it was unable to receive the notification or information copy, or
  • the information source has indicated that a receipt acknowledgment is required.

This section provides general information on the structure of the transaction set as represented in this implementation guide.

Note: See Appendix B, ASC X12 Nomenclature, for a review of transaction set structure, including descriptions of segments, data elements, levels, and loops.


1.11.1 Overall Data Architecture

The 278 is divided into two levels, or tables. See Section 2, Transaction Set, for a description of the format presented in the Transaction Set Listing. The Header level, Table 1, contains the purpose code for the transaction set as well as date and time stamps. For the notification portion of this implementation guide, BHT02 is either an Advance Notification (14), Completion Notification (CN) or an Information Copy (22). In addition, a BHT06 value of NO (Notice) indicates that the notification sender expects an acknowledgment of receipt. For the acknowledgment response, BHT02 indicates that this is either an acknowledgment indicating a successful receipt (BHT02 = 53, Completion) or a rejection (BHT02 = 44, Rejection) of the notification.

The Detail level, Table 2, contains all data relating to the notification, 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. Patient event in this 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, the implementation guide's developers 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.

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

Loop 2000A contains the Information Source

Loop 2000B contains the Information Receiver

Loop 2000C contains the Subscriber

Loop 2000D contains the Dependent

Loop 2000E contains the Patient Event

Loop 2000F contains the Services

Service Review Participants
This implementation uses a separate hierarchical level to identify each participant in the service review. Loop 2000A and Loop 2000B represent the information source and information receiver respectively. In this implementation guide, the terms "source" and "receiver" refer to the entities sending and receiving the notification.

Information Source: The information source may be a delegated utilization management entity that determined the outcome of a health care service review who has the knowledge of an event. Loop 2000A supports the identification of both an information sender and an information source for situations where the notification sender has knowledge of the event but is not the originator or decision maker.

Information Receiver: The information receiver, identified in Loop 2000B, is the partner who needs to know of the decision or result of an event.

Patient: 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.

Patient Event: Loop 2000E identifies information about the patient event and includes specific person, group practice, facility, or specialty entity providing services.

Services
Loop 2000F identifies the category of services and the specific services associated with this patient event. It also includes decision review outcomes and associated reason codes and authorization numbers if applicable.


1.11.2 Sample Table 2 Configurations

The following are sample Table 2 configurations.

The following example represents an advance notification of service, such as ambulance transport, for a dependent of a subscriber.

Information Source (Loop 2000A)

Information Receiver (Loop 2000B)

Subscriber (Loop 2000C)

Dependent (Loop 2000D)

Patient Event (Loop 2000E)

Service (Loop 2000F)

The following example represents an acknowledgment of receipt of a notification of service, such as ambulance transport, for a dependent of a subscriber. The information receiver acknowledges receipt at the patient level.

Information Source (Loop 2000A)

Information Receiver (Loop 2000B)

Subscriber (Loop 2000C)

Dependent (Loop 2000D)

The following example represents an advance notification of authorization for multiple services performed by the same service provider for a subscriber who is the patient.

Information Source (Loop 2000A)

Information Receiver (Loop 2000B)

Subscriber (Loop 2000C)

Patient Event (Loop 2000E)

Service (Loop 2000F)

Service (Loop 2000F)

The following example represents an acknowledgment of receipt of a notification of service for multiple services for a subscriber who is the patient. The information receiver acknowledges receipt of each service.

Information Source (Loop 2000A)

Information Receiver (Loop 2000B)

Subscriber (Loop 2000C)

Patient Event (Loop 2000E)

Service (with Review Outcome Data) (Loop 2000F)

Service (with Review Outcome Data) (Loop 2000F)


1.11.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 service review participants, Patient Event, and services.

Notification/Information Copy
For a Notification or Information Copy transaction, Matrix 1, Intended Segment Use for a 278 Notification Transaction, identifies the intended segment use by hierarchical level.

Matrix 1. Intended Segment Use for a 278 Notification Transaction

Segment

Position

Segment

ID

Info

Source

HL

Info

Receiver

HL

Subscriber

HL

Dependent

HL

Patient

Event

HL

Service

HL

0100 HL YES YES YES YES YES YES
0200 TRN YES YES
0300 AAA YES YES
0400UM YESYES
0500HCR YESYES
0600REF YESYES
0700DTP YESYES
0800HI YES
0810SV1 YES
0820SV2 YES
0830SV3 YES
0840TOO YES
0900HSD YESYES
1000CRC
1100CL1 YES
1200CR1 YES
1300CR2 YES
1350CR4
1400CR5 YES
1500CR6 YES
1520CR7
1530CR8
1550PWK YESYES
1600MSG YESYES
1700NM1YESYESYESYESYESYES
1800REFYES YESYESYESYES
1900N2
2000N3YES YESYESYESYES
2100N4YES YESYESYESYES
2200PERYES YESYES
2300AAA YESYES
2400PRVYES YESYES
2500DMG YESYES
2600INS YESYES
2700DTP

Acknowledgment
For an Acknowledgment transaction, Matrix 2, Intended Segment Use for a 278 Acknowledgment Transaction, identifies the intended segment use by hierarchical level.

Matrix 2. Intended Segment Use for a 278 Acknowledgment Transaction

Segment

Position

Segment

ID

Info

Source

HL

Info

Receiver

HL

Subscriber

HL

Dependent

HL

Patient

Event

HL

Service

HL

0100 HL YES YES YES YES YES YES
0200 TRN YES YES YES YES
0300AAAYES YESYESYESYES
0400UM YESYES
0500HCR YESYES
0600REF YESYESYESYES
0700DTP YESYES
0800HI YES
0810SV1 YES
0820SV2 YES
0830SV3 YES
0840TOO YES
0900HSD
1000CRC
1100CL1
1200CR1
1300CR2
1350CR4
1400CR5
1500CR6
1520CR7
1530CR8
1550PWK
1600MSG YES
1700NM1YESYESYESYESYESYES
1800REFYES YESYESYESYES
1900N2
2000N3
2100N4
2200PER YES
2300AAAYESYESYESYESYESYES
2400PRVYES YESYES
2500DMG YESYES
2600INS YESYES
2700DTP

1.11.4 Matching the Acknowledgment with its Notification

This implementation guide provides several methods to enable sources, receivers, and clearinghouses to trace the transaction or match the 278 acknowledgment, if returned, to the original notification. 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 notification transaction must return this identifier in the 278 acknowledgment BHT03.

TRN Segment
The Patient Event loop (2000E) and the Service loop (Loop 2000F) each contain a TRN segment. This segment enables organizations to uniquely identify the notification. 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 information source and the clearinghouse can add a TRN segment to the notification. The information receiver can assign its own trace number to the Patient Event loop and/or Service loop of the acknowledgment if returned.

The information source can use this TRN segment to meet several needs, including the following:

  • uniquely identify this notification within the information source's environment
  • uniquely identify each service. A single notification transaction can contain multiple services represented by multiple occurrences of Loop 2000F. The information receiver might receive some of these services and/or reject others due to data content errors.
  • match the associated acknowledgment to the notification
  • facilitate routing of this acknowledgment in a large health care environment. For example, it might be necessary for the information source to identify the department within the provider environment that originated the transaction.

Note: The information source cannot use this trace number to report the certification number to the information receiver.

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 notification, the information receiver must return the trace information in the 278 acknowledgment transaction.

Information receivers can add a trace number in their own TRN segment at the Patient Event level (Loop 2000E) and Service level (Loop 2000F) on the acknowledgment.

Note: The information receiver cannot use this trace number to report a receipt number to the information source.

If the 278 notification 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 acknowledgment 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 notification back in the 278 acknowledgment transaction. If the 278 notification passes through a clearinghouse that adds their own TRN in addition to a information source TRN, the clearinghouse will receive an acknowledgment from the information receiver containing two TRN segments that contain the value "2" (Referenced Transaction Trace Number) in TRN01. If the UMO has assigned a TRN, the information receiver TRN will contain the value "1" (Current Transaction Trace Number) in TRN01. If the clearinghouse chooses to pass their own TRN values to the information source, the clearinghouse must change the value in their TRN01 to "1" because, from the information source perspective, this is not a referenced transaction trace number.

1.12 Data Use By Business Use

The segments referenced in Matrix 1 and Matrix 2 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 information source, information receiver, 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 and service level discussions in this section contain multiple examples. In addition, the minimum data necessary for an acknowledgment differs from that required for a notification. The descriptions of each hierarchical level describe these differences.

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

Minimum Data Requirements - Acknowledgments
The information receiver must return a 278 acknowledgment to report any invalid or missing application data that prevented the information receiver from accepting the notification into their system. The minimum data necessary to report a rejection are the loops hierarchically necessary to report the rejection information. For example, if the error is detected in Loop 2000E of the notification, the acknowledgment must contain the minimum information (segments and data elements) necessary to return valid loops 2000A, 2000B, 2000C, 2000D, and the rejection reason in Loop 2000E.

The use of the 278 acknowledgment to report the successful receipt of a notification is optional and must be established by trading partner agreement between the information source and the information receiver. This implementation guide limits the information from the notification that the information receiver must return on the acknowledgment. If the information receiver acknowledges successful receipts of notifications, the minimum data necessary on the acknowledgment are the loops necessary to identify the information source (Loop 2000A), information receiver (Loop 2000B), and the patient (Loop 2000C/2000D).

Note: This section provides examples of types of health care service reviews and the minimum data required. Refer to Section 2 of this guide for detailed information on valuing specific data elements within the segments.


1.12.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.5 Information Source and Receiver Levels, presents the Loop 2000A and Loop 2000B levels.

Figure 1.5. Information Source and Receiver Levels

Information Source and Receiver Levels

Hierarchy Usage Chart for Transaction Participants
The various utilization management entities may appear in either the Loop 2000A or Loop 2000B hierarchical levels depending on the transaction usage. Matrix 3, HL Information Sources and Receivers, identifies some of the possible entities exchanging a health care services review notification. This matrix is by no means exhaustive.

Matrix 3. HL Information Sources and Receivers

Transaction Use

HL

Information Source

Sender NM1

HL

Information Source

Source NM1

HL

Information

Receiver

Physical

Transmitter

Physical

Receiver

Notice of Admission to UMO Hospital PCP UMO Hospital UMO
Notification to UMO regarding transfer or discharge Hospital PCP UMO Hospital UMO
Notification of services from a Provider to a Service Provider PCP UMO SCP PCP SCP
Notification of services from a UMO to a Service Provider UMO PCP SCP UMO SCP
Notification of authorization for services from a Delegated Entity to a Payer Delegated Entity Provider Payer Delegated Entity Payer
Notification of services from a UMO to a Third-party AdministratorUMOProviderTPAUMOTPA

* UMO - Utilization Management Organization

* PCP - Primary Care Provider

* SCP - Specialty Care Provider

The 2000A loop in the Notification and the Acknowledgment transactions always carries the party that initiated the notification. The 2000B loop in both transactions is always the party that received the notification.


1.12.1.1 Information Source (Loop 2000A)

The Loop 2000A hierarchical level is used to identify the information source. The information source is generally the entity empowered to make a decision regarding the outcome of a health services review or the owner of information.

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

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

As indicated in Figure 1.5, Loop 2010A supports two occurrences of the NM1 loop. The first NM1 loop is required. The second NM1 loop enables the notification sender to identify an additional entity as the source of this health care services review information. For example, in a notification of referral from the UMO to the service provider, the UMO may identify itself in the first NM1 loop and the requesting provider in the second NM1 loop. Or, in a notification of authorization to admit the patient sent from the PCP to the hospital, the PCP can use the first NM1 to identify itself as the sender and the second NM1 to identify the UMO as the source of the authorization.

Loop 2010A also supports the following additional segments:

REF Segment: Use this segment to provide supplementary identifiers for the information source when required.

PER Segment: Use this segment to identify a specific individual within the information source who can be contacted concerning the notification.

N3 and N4 Segments: Use the address segments, only when necessary, to further identify the information source or to provide information source address information to the receiver. These segments are supported on the 278 notification but are not supported on the 278 acknowledgment.

AAA Segment: This implementation guide supports the use of the AAA segment to enable the information receiver to report reasons why the notification cannot be processed at a system or application level or to convey rejection information regarding the entity that initiated a notification or information copy transaction.

PRV Segment: If the information source is a provider, use this segment to identify the provider's role in the care of the patient or the provider's specialty.


1.12.1.2 Information Receiver (Loop 2000B)

The Loop 2000B hierarchical level identifies the intended receiver of the notification. The following example demonstrates a minimum way of identifying an information receiver:

HL*2*1*21*1~
NM1*1P*1******46*0000012345~

NM1 Segment: As with the HL20 hierarchical level, the NM1 segment is usually sufficient to identify the information receiver when the trading partners are known. The NM1 segment should always be used to carry the primary identifier of the information receiver (see NM108 and NM109).

The 278 notification supports only the HL and NM1 segments. Loop 2010B of the 278 acknowledgment supports the following additional segments:

PER Segment: The information receiver should value this segment only if the information source must direct requests for additional information to a specific contact, electronic mail, facsimile, or phone number.

AAA Segment: Use this AAA segment to report the reasons why the information receiver cannot receive the notification at a system or application level based on the information source identified in Loop 2010A.


1.12.2 Patient (Loop 2000C and Loop 2000D)

Subscriber Loop 2000C and Dependent Loop 2000D identify the patient. Loop 2000C is always required. Loop 2000D is used only when necessary to identify a patient who is a dependent. Figure 1.6 Subscriber and Dependent Levels shows the structure of these loops.

Figure 1.6 - 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. This structure is more common in traditional group insurance where a patient is uniquely identified within the primary subscriber identifier.

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 information source and information receiver to identify the patient.


1.12.2.1 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 information receiver. However, the information receiver (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~

1.12.2.2 Identifying the Dependent

If the dependent has been issued a unique member ID, the Dependent Loop (2000D) is not used.

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 an information receiver (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

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~

Patient Account Number
The information source (provider) can supply the patient account number as a supplemental identifier for the patient on the notification. 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 information source. However if the information receiver/UMO receives the patient account number, they must return it in the 278 acknowledgment transaction, if returned.


1.12.2.3 Supplying Other Patient Information on the Notification

In addition to the patient identification segments provided in loops 2010C and 2010D, the 278 notification also supports the ability to provide address information, date of birth, gender and relationship in the following segments:

N3 and N4 Segments: Use the address segments, only when necessary, to further identify the subscriber or dependent to the information receiver.

DMG Segment: Use the DMG segment when birth date is needed to identify the patient or when gender information was used to render a medical decision.

INS Segment: Use the INS segment when patient relationship to insured or birth sequence was used to determine the appropriate benefit/level of care.


1.12.2.4 Acknowledging Patient Information Received

With the exception of the TRN segment, the segments referenced in section 2.2.3 are not supported on the acknowledgment. This implementation guide limits the acknowledgment to return the minimum data necessary to indicate the receipt or rejection of the notification. The information receiver can return the following acknowledgment information, in addition to the segments that identify the patient.

AAA Segment: The information receiver must return a 278 acknowledgment response if the information receiver is unable to process the application data at subscriber or dependent level. The response must contain a AAA segment at the level of the failure that reports the error condition that prohibits the receiver system from processing the notification. Two AAA segments are provided. The first AAA identifies error conditions in the data contained in Loop 2000C/2000D. These pertain to invalid or missing diagnosis codes and dates and patient condition dates. The second AAA in Loop 2010C/2010D identifies invalid or missing subscriber or dependent identification information.

Notification Receipt Number REF: This REF is required if the information receiver returns a receipt number to indicate receipt of the notification.


1.12.3 Patient Event (Loop 2000E)

The Loop 2000E hierarchical level identifies the patient event associated with this Notification, or Information Copy. It identifies the category of service and whether the patient event concerns a referral to a specialist, specialty treatment, or an admission to a facility. Inbound patient event information can include Utilization Management decision outcomes, a variety of date indicators, reference/review numbers and even rejection reasons associated with the event. 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 Notification includes information on specific procedures to be performed, it must provide information on these procedures at the Services Level (Loop 2000F).

Figure 1.7. Service Provider Level

Service Provider Level


1.12.3.1 Tracking the Notification and Acknowledgment

Only certified, partial certified (2000E only) and modified events and services have an assigned review identification number reported in HCR02. The TRN and REF segments at the Event and Service loops enable the information source and information receiver to assign identifiers to each event and service for internal tracking purposes.

TRN Segment
The Event level Trace Number (TRN) segment uniquely identifies the notification at its highest logical level, the event. The TRN is also for use at the Service Level, its lowest logical level. Both the information source and the clearinghouse can add a TRN segment to the notification. The information receiver can add its own TRN to each event, or service loop in the acknowledgment. The TRN segment is used to accomplish the following:

  • uniquely identify each patient event, or service.
  • match the associated acknowledgment to the notification, if applicable
  • facilitate routing of this acknowledgment in a large health care environment. For example, it might be necessary for the notification source to identify the department within the provider environment that originated the notification transaction.
  • associate the event to any additional information in an attachment

Refer to Section 1.5.4 for more information on the uses of the TRN segment.

REF Segment
The notification/information copy (BHT02 = 14, CN, or 22) supports multiple REF segments to enable the information source to identify an administrative reference number returned by the information receiver, or the information receiver to recognize a previous review authorization number assigned by the information source when referencing a previous notification, or information copy. For example, in a notice of admission or notice of discharge when REF01=NT, this identifies the administrative reference number that was previously assigned and returned by the information source for a previous acknowledgment.

In addition, when REF01=BB this will allow the information receiver to identify a previous review authorization that was assigned by the information source to a prior notification.


1.12.3.2 Identifying the Category and Status of a Notification

The following segments enable the information source to report on the category and status of a health care services review.

UM Segment
The UM segment identifies the type of health care services review. UM01 indicates if the patient event concerns a referral to a specialist, specialty treatment, or an admission to a facility. UM02 specifies the type of certification and indicates if this is a notification of the outcome of an initial request, appeal or reconsideration of a previous denial, or an extension, cancellation, revision or renewal of a previous authorization. UM03 identifies the type or category of service such as Chiropractic. Additional segments provide related detail including the place of service and indicators of whether the service is accident related, emergency or urgent. This segment is required on all notifications and on all acknowledgments if this loop is used.

HCR Segment
The HCR segment reports the status or outcome of a health care services review. If BHT02 = 14 (Advance Notification) or 22 (Information Copy) and the information copy reports a review decision, this segment is required. HCR02 conveys the certification number assigned to this health care services review. This segment is valued on the acknowledgment (BHT02 = 44 (Rejection) or 53 (Completion)) only if this loop is returned and HCR02 was valued on the notification.

AAA Segment
The AAA segment identifies the reason for rejection of a health care services review. When valued on the notification or information copy (BHT02 = 22), this segment identifies to the information receiver (UMO or payer) the reason why the information source (delegated entity) rejected a request for authorization based on the service information in the original 278 health care services request for review. When valued on the acknowledgment (BHT02 = 44), this segment identifies to the information source the reason why the information receiver was unable to accept the notification based on the data content in the 278 notification.


1.12.3.3 Identifying Event Details on the Notification

The following segments carry detailed information associated with the service.

Segment

Purpose

DTP - Date Date Carries date information associated with the service. The type and category of the of service and the status of the service review determine the dates needed.
HI - Health Care Information Codes Identifies specific diagnosis codes.
CRC - Patient Condition Information Identifies additional patient condition information used to determine the medical necessity of services
CL1 - Institutional Claim Code Provides institutional claim information on notifications of admission
CR1 - Ambulance Transport Information Provides non-emergency patient transport information
CR2 - Spinal Manipulation Service Information Identifies a spinal condition or treatment that involves subluxation
CR5 - Home Oxygen Therapy Information Identifies the equipment and treatment for notifications of initial, extended, or revised certification of home oxygen therapy
CR6 - Home Health Care Information Provides information specific to notifications of certification of home health care, private duty nursing, or services by a nurses’ agency.
PWK Identifies additional documentation (electronic, paper, or other medium) associated with this service. The 278 notification transaction (ST to SE) does not support this information. Refer to Section 2.6 for more information.

MSG Segment: The MSG segment is used in the notification only and carries freeform text about the patient event. This segment must only be used when it is necessary to send additional information about the patient event that could not otherwise be codified within the 2000E Loop.


1.12.3.4 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 providers, for example an admission review and identification of the various provider roles.

Loop 2000E (Patient Event)

Loop 2010EA (Patient Event Provider 1) - Attending Provider
Loop 2010EA (Patient Event Provider 2) - Admitting Provider
Loop 2010EA (Patient Event Provider 3) - Facility

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

The following example represents a single patient event with multiple providers associated with specific services.

Loop 2000E (Patient Event)

Loop 2010EA (Patient Event Provider 1) - Facility

Loop 2000F (Service 1)

Loop 2010F (Service Provider 1) - Assistant Surgeon

Loop 2000F (Service 2)

Loop 2010F (Service Provider 2) - Operating Physician


1.12.3.5 Service Provider Information on the Notification

In addition to the name (NM1), the Patient Event Provider Name also supports address (N3 and N4), supplementary identifiers (REF), communication number (PER) and provider specialty (PRV) details.

AAA Segment: A delegated entity or third-party situation, in the role of information source, may have responsibility for reporting the outcome or providing information copies of all health care service reviews. In these situations, the information source can use the AAA segment at this level of the notification to identify to the information receiver (UMO or payer) the reason why a request for authorization was denied or rejected based on the service provider identified in the original 278 health care services request for review.


1.12.3.6 Service Provider Information on the Acknowledgment

This implementation guide limits the acknowledgment to return the minimum data necessary to indicate the receipt or rejection of the notification. The information receiver must return a 278 acknowledgment response if the information receiver is unable to process the application data at this level or at a subordinate level. If the information receiver returns a receipt acknowledgment for notifications accepted, the acknowledgment must contain this loop only if the information receiver returns the subordinate Loop 2000F.

The acknowledgment supports the use of the NM1, REF, and PRV segments to identify the service provider. The acknowledgment does not return the address information (N3 and N4) or communication information (PER) if provided on the notification.

AAA Segment: If the information receiver is unable to accept the notification, the acknowledgment must contain a AAA segment at the level of the failure that reports the error condition that prohibits the receiver system from processing the notification.

NM1 Loops - Additional Information Contact Name
The 278 response includes NM1 loops to identify the person, office location, or other destination when the Information Source utilized the PWK to forward additional patient event information to the information receiver. NM1 Loop 2010EB identifies additional patient event information contact name, address, and communication number information.


1.12.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 was 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 Matrix 1 and Matrix 2, many of the segments used in Loop 2000F are the same as those available in Loop 2000E.

Figure 1.8. Service Level

Service Level

Guidelines for Using the Service Level

  1. Use only if the services or procedures identified are for the same patient event identified in Loop 2000E.
  2. Use only if at least one of the following situations exists.
    • You are indicating a type of service (UM03) in addition to the category or type of service specified in the patient event, or
    • You are identifying 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 identifying 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 acknowledgment to the notification. Use of trace numbers at this level can facilitate matching these different responses to the original request.

1.12.4.1 Returning Service Details on the Acknowledgment

This implementation does not require the information receiver to return Loop 2000F when acknowledging the successful receipt of a notification.

BHT02 = 44, Rejection
Loop 2000F is required only when necessary to report invalid or missing application data at this level of the notification that prevented the information receiver from accepting the notification into their system. To facilitate the identification of the data in error, the acknowledgment can return service detail information reported in the UM, HCR, REF, DTP, and HI segments of the notification.

BHT02 = 53, Completion
If the information receiver chooses to acknowledge receipt of each service loop on the notification, they must return the segments that carried service level identification information on the notification. This includes the trace number (TRN), category and type of service (UM), certification number (HCR02), and previous certification identification (REF) if valued on the notification. The information receiver can elect to return the values specified in the notification for the DTP and HI segments. The other segments at this level of the notification carried patient condition information and are not supported on the acknowledgment.


1.12.5 Examples of Service Level Notifications

This section provides some examples of Service level segment values for the different types of notifications and information copies.


1.12.5.1 Advance Notification (BHT02 = 14)

Specialty Referral
Specialty care referral notifications encompass those transactions where a provider requests or grants 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. The following example contains a notification of authorization for an initial service consisting of a single office visit for a consultation at the provider's office.

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

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

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 HCR segment provides the results of the review as well as a review identification number. This set of values indicates approval of the request in full. A review identification number of 0081096G is supplied and is critical if the information source wishes to initiate further transactions concerning this service.

The HSD segment identifies the number of visits authorized.

Health Services Review
The term "health services review" identifies a notification of authorization for specific treatments or more extended care. Extended care refers to treatment for a condition requiring prolonged rehabilitation therapy. This transaction set supports a notification for authorization 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 notification transaction for each patient event.

This is an example of a notification indicating a certified in total decision for chiropractic services of the spine. The UMO is notifying the chiropractor that it has authorized 24 visits to occur twice per week over a (3) month period.

HL*5*4*SS*0~ 
UM*HS*I*33******Y~ 
HCR*A1*2003082001~ 
HSD*VS*2*WK**34*3~ 

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

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

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.

Admission Review
The term "admission review" identifies a notification of authorization for admission to a facility for treatment (pre-certification). The transaction set enables the information source to specify both the admission to the facility and the associated inpatient procedures authorized within the same transaction. In this scenario, the specialist requested authorization to admit the patient for a surgical procedure. The UMO has authorized the request and sends a notification of the authorization to the facility. The notification contains two occurrences of Loop 2000E and Loop 2000F as follows:

Loop 2000E (Service Provider - Facility)
Loop 2000F (Admission Review)
Loop 2000E (Service Provider - Operating Surgeon)
Loop 2000F (Health Services Review for surgical procedure)

The following example demonstrates a notification of authorization for the facility portion of an admission review.

HL*5*4*SS*0~ 
TRN*1*211099*9012345678~ 
UM*AR*I*2*21:B*****Y~ 
HCR*A1*IP2003073101~ 
DTP*435*RD8*20030820-20030826~ 
CL1*2~ 

The UM segment identifies the type of health care services.

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)

The DTP segment carries the anticipated date range of the admission and the CL1 value indicates the priority of the admission.

Revisions
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 modified 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*20051109ABCD~ 

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.12.5.2 Completion Notification (BHT02 = 14)

Specialty Referral
A completion notification advises the information receiver that an authorized patient event has occurred. For example, the UMO may require the facility to return a notification of admission when it admits the patient. The UMO may also require notification when the facility discharges the patient, notice of discharge. The following example demonstrates the use of the notice of admission to advise the UMO that the patient, whose admission was pre-authorized, has been admitted.

HL*5*4*SS*0~ 
TRN*1*20030820*123456789~ 
UM*AR**2*21:B~ 
REF*BB*IP2003073101~ 
DTP*435*D8*20030821~ 
CL1*2~ 

The REF segment identifies the previous certification identifier (the value of HCR02) assigned to the admission review previously authorized. The DTP segment identifies the actual date of admission (DTP01 = 435).

When the facility discharges the patient, it sends another completion notification to notify the UMO of the discharge. Loop 2000E of the discharge notification is identical to the notice of admission with the exception of the DTP segment. On a discharge notice, DTP01 has the value "096" to indicate a discharge date.


1.12.5.3 Information Copy (BHT02 = 22)

The Service loop of courtesy copies of advance or completion notifications are identical in content to the notifications. The business event that triggers this transfer of information and the entities sending and receiving the information determine if the requirement is to notify the receiver, or provide information copies. The primary use of the information copy is to forward from a delegated entity to the Payer a copy of the contents of service reviews that were certified, or not certified by the information source/delegated entity. The following example demonstrates an information copy of a service review that was rejected based on the data content of Loop 2000F of the health care services review request.

HL*5*4*SS*0~ 
AAA*N**52*C~ 
UM*HS*I*6~ 

The AAA segment indicates that the information source rejected the service review request for radiation therapy due to an invalid or missing date of service.


1.12.5.4 Acknowledgment of Receipt (BHT02 = 53)

The information receiver can return a 278 acknowledgment to indicate the successful receipt of the notification. The information receiver can assign a receipt number to the acknowledgment at the Patient level and/or at each Service level associated with the notification. The following example demonstrates an acknowledgment of receipt of a notice of admission.

HL*5*4*SS*0~ 
TRN*2*20030820*123456789~ 
UM*AR**2~ 
REF*NT*IP2003073101~ 
REF*BB*000056789123~ 
DTP*435*D8*20030821~ 

The acknowledgment echoes back the source's trace number and other identifying information associated with the service notification. In addition, the information receiver has assigned an administrative reference number (REF01 = NT) to acknowledge receipt of the notice of admission.


1.12.5.5 Negative Acknowledgment (BHT02 = 44)

The information receiver must return a negative acknowledgment if it detects invalid or missing data at the Event, or Service level of the notification. The negative acknowledgment must identify the reasons for rejection in the AAA segment at the appropriate level. The following example demonstrates an acknowledgment indicating that the notification contained errors at the Service level.

HL*5*4*SS*0~ 
AAA*N**52*Y~ 
UM*HS*I*79~ 
HCR*A1*3082001~ 
DTP*472*RD8*20030901-20031130~ 

The negative acknowledgment echoes back event or service level identification information from the notification. It indicates that the service dates on the notification are not within the provider plan enrollment for the service provider assigned in Loop 2000E. It returns the date in question and the certification number provided in the HCR02 field of the notification.


1.12.6 Additional Service Review Information

Under some circumstances, the information receiver (UMO, or Payer) may require copies of any additional information used by the information source to determine the medical necessity of the services. This additional information concerns patient condition and service detail data not supported in the 278 (ST to SE).


1.12.6.1 Referencing Additional Information on the 278 Notification

The 278 notification contains a PWK segment that the information source must 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 (Loop 2000E) level and at the Service (Loop 2000F) level. The Event level TRN segment (Patient Event Tracking Number) enables the information source to assign a unique trace number to the patient event associated with this notification. The Service level TRN Segment (Service Trace Number) enables the information source to assign a unique identifier to a service when multiple services are included.

PWK Segments
The 278 notification supports 10 occurrences of the PWK segment at the Patient level and at each Service level (Loop 2000F). This enables the information source 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 notification.

Guidelines for Using the PWK Segment on the Notification

  1. The PWK segment is required if the information source has additional documentation (electronic, paper, or other medium) associated with this health care services review that applies to the patient and/or the services and the 278 notification transaction (ST to SE) does not support this information.
  2. Use the PWK segment at the Patient level if the attachment pertains to this patient event and/or all the services.
  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.
    Note: 275 refers to the X12N 275 Patient Information Transaction Set. At the time of this writing, HIPAA has not adopted the 275 for use with the 278 Health Care Services Review. A draft 275 Additional Information to Support a Health Care Services Review implementation guide is in progress. If not adopted by HIPAA, use of the 275 must be mutually agreed to by trading partners.
  5. The information source 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).

2. Transaction Set

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


2.1 Presentation Examples

The ASC X12 standards are generic. For example, multiple trading communities use the same PER segment to specify administrative communication contacts. Each community decides which elements to use and which code values in those elements are applicable.

This implementation guide uses a format that depicts both the generalized standard and the insurance industry-specific implementation. In this implementation guide, IMPLEMENTATION specifies the requirements for this implementation. X12 STANDARD is included as a reference only.

The transaction set presentation is comprised of two main sections with subsections within the main sections:

2.3 Transaction Set Listing

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

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

This section is included as a reference.

2.4 Segment Detail

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

This section is included as a reference.

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

This section specifies the implementation details of each data element.

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

Figure 2.1 - Transaction Set Key - Implementation

Transaction Set Key - Implementation

Figure 2.2 - Transaction Set Key - Standard

Transaction Set Key - Standard

Figure 2.3 - Segment Key - Implementation

Segment Key - Implementation

Figure 2.4 - Segment Key - Diagram

Segment Key - Diagram

Figure 2.5 - Segment Key - Element Summary

Segment Key - Element Summary


2.2.1 Industry Usage

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

Required

This loop/segment/element must always be sent.

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

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

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

Not Used

This element must never be sent.

Situational

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

There are two forms of Situational Rules.

The first form is "Required when <explicit condition statement>. If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver." The data qualified by such a situational rule cannot be required or requested by the receiver, transmission of this data is solely at the sender's discretion.

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


2.2.1.1 Transaction Compliance Related to Industry Usage

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

Required

Business condition: N/A

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

Business condition: N/A

Item is Transaction complies with implementation guide?
Sent No
Not Sent Yes
Situational (Required when [explicit condition statement])

If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver.

Business Condition is Item is Transaction complies with implementation guide?
True Sent Yes
Not Sent No
Not True Sent Yes
Not Sent Yes
Situational (Required when [explicit condition statement])

If not required by this implementation guide, do not send.

Business Condition is Item is Transaction complies with implementation guide?
True Sent Yes
Not Sent No
Not True Sent No
Not Sent Yes

2.2.2 Loops

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

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

3.1 Business Scenario 1

This is an example of a standard Notification/Acknowledgment sequence between a Service Provider and a Utilization Management Organization.

Joe Smith, who is a subscriber to Maryland Capital Insurance Company is approved for admission to St. Joseph Hospital for surgery. When Joe is actually admitted to the hospital, May 30, 2004, St. Joseph Hospital sends an Admission Notification to Maryland Capital Insurance informing them that Joe has become a patient.

Upon receipt and processing of the Notification the Maryland Capital Insurance Company responds with an Acknowledgment transaction.


3.1.1 Notification

The following example represents the Notification from St. Joseph Hospital to Maryland Capital Insurance of the hospital admission.

Table
ST*278*0001*005010X216~

Begin transaction set 278, control #001.

BHT*0007*CN*2004000345628*20040601*1410*NO~

This transaction is a notification using hierarchical structure 0007 (Information Source, Information Receiver, Subscriber, Dependent, Event, Services). The transaction purpose is completion notification (CN) and the information source has sent a reference number of 2004000345628. The transaction was created on the information source's system June 1, 2004 at 2:10 PM. The transaction type is a notice (NO), this indicates that an acknowledgment response by the information receiver is required.

Loop 2000A identifies the hospital as the information source.
HL*1**20*1~

The HL Count is 1. There is no higher or parent, HL. This HL contains information about the Information Source as indicated by the value 20. This HL has subordinate, or children, levels of information.

NM1*1P*2*St Joseph Hospital*****XX*1234567890~

The information source is identified as a provider (1P) and as a Non-Person Entity (2) with the name St. Joseph Hospital. The hospital is further identified with an NPI (XX) of 1234567890.

Loop 2000B identifies the insurance company, the information receiver.
HL*2*1*21*1~

HL count is 2. This HL is subordinate to HL*1, the parent HL. This HL code is 21, identifying the information receiver or the referring provider. This HL has subordinate levels, or children.

NM1*X3*2*Maryland Capital Insurance Company*****46*789312~

The information receiver is identified as an UMO (X3) and as a Non-Person Entity (2) with the name Maryland Capital Insurance Company. The UMO is further identified with an ETIN (46) of 789312

Loop 2000C contains subscriber information, who in this case is also the patient (the subscriber is the patient when loop 2000D is not present).
HL*3*2*22*1~

HL count is 3. This HL is subordinate to HL*2, the parent HL. This HL code is 22, identifying the subscriber. This HL has subordinate levels, or children.

NM1*IL*1*Smith*Joe****MI*12345678901~

The name information is for the subscriber (IL) and is identified as a person (2) with the last name Smith and a first name of Joe. The subscriber is further identified with a member identification number (MI) of 12345678901.

DMG*D8*19580322*M~

As a matter of course, St. Joseph's system provides patient demographic information. This segment indicates Joe Smith's birthday as March 22, 1958 and that Joe is a male (M).

Loop 2000D identifies the dependent as a patient. Because there is no dependent in this example, there is no Loop 2000D.
Loop 2000E identifies the Patient Event. The information within the 2000E Patient Event level applies to all subsequent 2000F service loops unless a 2000F service loop contains information unique for the 2000F service. In this situation, the information at the 2000F loop overrides the 2000E event information for that 2000F loop's service(s) only.
HL*4*3*EV*0~

HL count is 4. This HL is subordinate to HL*3, the parent HL. This HL code is EV, identifying the event. This HL has no subordinate levels, or children.

TRN*1*040601002349A*9000012121~

The Patient Event Tracking Number assigned by the information source (1) with the value of 040601002349A using the Trace Assigning Entity Identifier of 9000012121.

UM*AR*I*2*11:A~

The Health Care Service Review Information is for an (I) initial Notification of Admission Review (AR) for surgery (2) at an inpatient facility (11:A).

HCR*A1*A0405295498~

The Health Care Review certification action of certified in total (A1) and the associated reference identification number of A0405295498 were assigned by the UMO on the original response to the request for service.

DTP*435*D8*20040530~

Joe Smith's admission (435) date was May 30, 2004.

HI*BF:410.90~

The patient has been diagnosed with acute myocardial infarction; unspecified site. ICD-9-CM (BF) code 410.90.

CL1*2~

The Institutional Claim Code from the original request for service to the UMO was an urgent admission type (2).

Loop 2010E Identifies providers at the Event Level.
NM1*SJ*2*St Joseph Hospital*****XX*1234567890~

The patient event provider is identified as the service provider (SJ) and as a Non-Person Entity (2) with the name St. Joseph Hospital. The hospital is further identified with an NPI (XX) of 1234567890.

PER*IC**TE*6107771212~

The information contact (IC) information for St Joseph Hospital is telephone (TE) number 6107771212.

Loop F identifies specific service information. This Notification example of a hospital admission contains no additional service detail information at this level.
SE*19*0001~

Number of segments, control number.


3.1.2 Acknowledgment

The following example represents the Acknowledgment from Maryland Capital Insurance to St. Joseph's Hospital for the Notification example in section 3.1.1.

Table
ST*278*0034*005010X216~
BHT*0007*53*2004000345628*20050602*0420~

This transaction is an acknowledgment using hierarchical structure 0007 (Information Source, Information Receiver, Subscriber, Dependent, Event, Services). The transaction purpose is Completion (53) and the information source has returned the reference identification value 2004000345628 that was sent on the notification. The transaction was created on the acknowledger's system on June 2, 2005 at 4:20 AM.

Loop 2000A identifies the UMO as the information source.
HL*1**20*1~

The HL Count is 1. There is no higher or parent, HL. This HL contains information about the Information Source as indicated by the value 20. This HL has subordinate, or children, levels of information.

NM1*1P*2*St Joseph Hospital*****XX*1234567890~

The information sender is identified as a provider (1P) and as a Non-Person Entity (2) with the name St. Joseph Hospital. The hospital is further identified with an NPI (XX) of 1234567890.

Loop 2000B identifies the Hospital as the information receiver.
HL*2*1*21*1~

HL count is 2. This HL is subordinate to HL*1, the parent HL. This HL code is 21, identifying the information receiver. This HL has subordinate levels, or children.

NM1*X3*2*Maryland Capital Insurance Company*****46*789312~

The information receiver is identified as an UMO (X3) and as a Non-Person Entity (2) with the name Maryland Capital Insurance Company. The UMO is further identified with an ETIN (46) of 789312.

Loop 2000C contains subscriber information, who in this case is also the patient (the subscriber is the patient when loop 2000D is not present).
HL*3*2*22*1~

HL count is 3. This HL is subordinate to HL*2, the parent HL. This HL code is 22, identifying the subscriber. This HL has subordinate levels, or children.

NM1*IL*1*Smith*Joe****MI*12345678901~

The name information is for the subscriber (IL) and is identified as a person (2) with the last name Smith and a first name of Joe. The subscriber is further identified with a member identification number (MI) of 12345678901.

DMG*D8*19580322*M~

As a part of the original notification (from the hospital), Maryland Capital Insurance Company, as a matter of policy, is returning the same patient demographic information on the acknowledgment. This segment indicates Joe Smith's birthday as March 22, 1958 and that Joe is a male (M).

Loop 2000D identifies the dependent as a patient. Because the original notification identified the patient as the subscriber no information is present in the acknowledgment at this level.
Loop 2000E identifies the Patient Event. The information within the 2000E Patient Event level applies to all subsequent 2000F service loops unless a 2000F service loop contains information unique for the 2000F service. In this situation, the information at the 2000F loop overrides the 2000E event information for that 2000F loop's service(s) only.
HL*4*3*EV*0~

HL count is 4. This HL is subordinate to HL*3, the parent HL. This HL code is EV, identifying the event. This HL has no subordinate levels, or children.

TRN*2*040601002349A*9000012121~

The Patient Event Tracking Number, originally present on the notification, is returned on the acknowledgment by Maryland Capital Insurance Company. The value of "2" in the TRN01 element identifies the value of 040601002349A with the Trace Assigning Entity Identifier of 9000012121 as tracking values present on the original notification transaction.

UM*AR*I*2*11:A~

The Health Care Service Review Information is for an (I) initial Notification of Admission Review (AR) for surgery (2) at an inpatient facility (11:A). This information was valued on the notification and is being returned on the acknowledgment.

HCR*A1*A0405295498~

The Health Care Review certification action of certified in total (A1) and the associated reference identification number of A0405295498 were assigned by the UMO on the original response to the request for service. The acknowledgment is required to returning this information when it was part of the notification transaction.

DTP*435*D8*20040530~

Joe Smith's admission (435) date was May 30, 2004. The acknowledgment is required to return this information when it was part of the notification transaction.

HI*BF:410.90~

The patient was diagnosed with acute myocardial infarction; unspecified site. ICD-9-CM (BF) code 410.90. The acknowledgment is required to return this information when it was part of the notification transaction.

Loop 2010E Identifies providers at the Event level
NM1*SJ*2*St Joseph Hospital*****XX*1234567890~

The patient event provider is identified as the service provider (SJ) and as a Non-Person Entity (2) with the name St. Joseph Hospital. The hospital is further identified with an NPI (XX) of 1234567890.

Loop F identifies specific service information. This Acknowledge example of a hospital admission contains no additional service detail information at this level.
SE*17*0034~

Number of segments, control number.


Appendix A. External Code Sources

5 Countries, Currencies and Funds

SIMPLE DATA ELEMENT/CODE REFERENCES

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

SOURCE

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

AVAILABLE FROM

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

ABSTRACT

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

22 States and Provinces

SIMPLE DATA ELEMENT/CODE REFERENCES

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

SOURCE

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

AVAILABLE FROM

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

ABSTRACT

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

51 ZIP Code

SIMPLE DATA ELEMENT/CODE REFERENCES

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

SOURCE

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

AVAILABLE FROM

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

ABSTRACT

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

130 Healthcare Common Procedure Coding System

SIMPLE DATA ELEMENT/CODE REFERENCES

235/HC, 1270/BO, 1270/BP

SOURCE

Healthcare Common Procedure Coding System

AVAILABLE FROM

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

ABSTRACT

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

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

SIMPLE DATA ELEMENT/CODE REFERENCES

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

SOURCE

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

AVAILABLE FROM

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

ABSTRACT

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

135 American Dental Association

SIMPLE DATA ELEMENT/CODE REFERENCES

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

SOURCE

Current Dental Terminology (CDT) Manual

AVAILABLE FROM

Salable Materials
American Dental Association
211 East Chicago Avenue
Chicago, IL 60611-2678

ABSTRACT

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

229 Diagnosis Related Group Number (DRG)

SIMPLE DATA ELEMENT/CODE REFERENCES

1354, 1270/DR

SOURCE

Federal Register and Health Insurance Manual 15 (HIM 15)

AVAILABLE FROM

Superintendent of Documents
U.S. Government Printing Office
Washington, DC 20402

ABSTRACT

A patient classification scheme that clusters patients into categories on the basis of patient's illness, diseases, and medical problems.

230 Admission Source Code

SIMPLE DATA ELEMENT/CODE REFERENCES

1314

SOURCE

National Uniform Billing Data Element Specifications

AVAILABLE FROM

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

ABSTRACT

A variety of codes explaining who recommended admission to a medical facility.

231 Admission Type Code

SIMPLE DATA ELEMENT/CODE REFERENCES

1315

SOURCE

National Uniform Billing Data Element Specifications

AVAILABLE FROM

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

ABSTRACT

A variety of codes explaining the priority of the admission to a medical facility.

235 Claim Frequency Type Code

SIMPLE DATA ELEMENT/CODE REFERENCES

1325

SOURCE

National Uniform Billing Data Element Specifications Type of Bill Last Position

AVAILABLE FROM

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

ABSTRACT

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

236 Uniform Billing Claim Form Bill Type

SIMPLE DATA ELEMENT/CODE REFERENCES

1332/A

SOURCE

National Uniform Billing Data Element Specifications Type of Bill Positions 1 and 2

AVAILABLE FROM

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

ABSTRACT

A variety of codes describing the type of medical facility.

237 Place of Service Codes for Professional Claims

SIMPLE DATA ELEMENT/CODE REFERENCES

1332/B

SOURCE

Place of Service Codes for Professional Claims

AVAILABLE FROM

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

ABSTRACT

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

239 Patient Status Code

SIMPLE DATA ELEMENT/CODE REFERENCES

1352

SOURCE

National Uniform Billing Data Element Specifications

AVAILABLE FROM

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

ABSTRACT

A variety of codes indicating patient status as of the statement covers through date.

240 National Drug Code by Format

SIMPLE DATA ELEMENT/CODE REFERENCES

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

SOURCE

Drug Establishment Registration and Listing Instruction Booklet

AVAILABLE FROM

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

ABSTRACT

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

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

SIMPLE DATA ELEMENT/CODE REFERENCES

235/IV, 1270/HO

SOURCE

Home Infusion EDI Coalition (HIEC) Coding System

AVAILABLE FROM

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

ABSTRACT

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

537 Centers for Medicare and Medicaid Services National Provider Identifier

SIMPLE DATA ELEMENT/CODE REFERENCES

66/XX, 128/HPI

SOURCE

National Provider System

AVAILABLE FROM

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

ABSTRACT

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

540 Centers for Medicare and Medicaid Services PlanID

SIMPLE DATA ELEMENT/CODE REFERENCES

66/XV, 128/ABY

SOURCE

PlanID Database

AVAILABLE FROM

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

ABSTRACT

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

663 Logical Observation Identifier Names and Codes (LOINC)

SIMPLE DATA ELEMENT/CODE REFERENCES

128/LOI, 235/LB, 1270/LOI

SOURCE

Logical Observation Identifier Names and Codes (LOINC)

AVAILABLE FROM

Reginstriff Institute
Indiana University School of Medicine
1001 West 10th Street
5th Floor RHC
Indianapolis, IN 46202

ABSTRACT

List of descriptive terms and identifying codes for reporting precise test methods in medicine.

682 Health Care Provider Taxonomy

SIMPLE DATA ELEMENT/CODE REFERENCES

128/PXC, 1270/68

SOURCE

The National Uniform Claim Committee

AVAILABLE FROM

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

ABSTRACT

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

843 Advanced Billing Concepts (ABC) Codes

SIMPLE DATA ELEMENT/CODE REFERENCES

235/WK, 1270/CAH

SOURCE

The CAM and Nursing Coding Manual

AVAILABLE FROM

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

ABSTRACT

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

886 Health Care Service Review Decision Reason Codes

SIMPLE DATA ELEMENT/CODE REFERENCES

1271

SOURCE

Health Care Service Review Decision Reason Code List

AVAILABLE FROM

The Blue Cross Blue Shield Association
Interplan Teleprocessing Services Division
676 North St. Clair Street
Chicago, IL 60611

ABSTRACT

Code identifying the decision of a health care service review as reported by the transaction set sender

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

SIMPLE DATA ELEMENT/CODE REFERENCES

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

SOURCE

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

AVAILABLE FROM

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

ABSTRACT

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

932 Universal Postal Codes

SIMPLE DATA ELEMENT/CODE REFERENCES

116

SOURCE

Universal Postal Union website

AVAILABLE FROM

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

ABSTRACT

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


B.1.1 Interchange and Application Control Structures

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


B.1.1.1 Interchange Control Structure

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

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

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

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

Figure B.1 - Transmission Control Schematic

Transmission Control Schematic

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

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

B.1.1.2.1 Basic Structure

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


B.1.1.2.2 Basic Character Set

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

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

Figure B.2 - Basic Character Set

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

B.1.1.2.3 Extended Character Set

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

Figure B.3 - Extended Character Set

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


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

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


B.1.1.2.4 Control Characters

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


B.1.1.2.4.1 Base Control Set

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

Matrix B.1. Base Control Set

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


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


B.1.1.2.4.2 Extended Control Set

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

Matrix B.2. Extended Control Set

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


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


B.1.1.2.4.5 Delimiters

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

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

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

Matrix B.3. Delimiters

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


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


B.1.1.3 Business Transaction Structure Definitions and Concepts

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

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

B.1.1.3.1 Data Element

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

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

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

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

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

Matrix B.4. Data Element Types

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


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


B.1.1.3.1.1 Numeric

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

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

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

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

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


B.1.1.3.1.2 Decimal

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

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

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

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

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

For implementation of this guide under the rules promulgated under the Health Insurance Portability and Accountability Act (HIPAA), decimal data elements in Data Element 782 (Monetary Amount) will be limited to a maximum length of 10 characters including reported or implied places for cents (implied value of 00 after the decimal point). Note the statement in the preceding paragraph that the decimal point and leading sign, if sent, are not part of the character count.

EXAMPLE
For implementations mandated under HIPAA rules:

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

B.1.1.3.1.3 Identifier

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


B.1.1.3.1.4 String

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


B.1.1.3.1.5 Date

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


B.1.1.3.1.6 Time

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

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


B.1.1.3.1.7 Binary

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

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


B.1.1.3.2 Repeating Data Elements

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


B.1.1.3.3 Composite Data Structure

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

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

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


B.1.1.3.4 Data Segment

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

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


B.1.1.3.5 Syntax Notes

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


B.1.1.3.6 Semantic Notes

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


B.1.1.3.7 Comments

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


B.1.1.3.8 Reference Designator

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

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

EXAMPLE

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

B.1.1.3.9 Condition Designator

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

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

Table B.5. Condition Designator

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

B.1.1.3.10 Absence of Data

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

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

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


B.1.1.3.11 Control Segments

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


B.1.1.3.11.1 Loop Control Segments

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


B.1.1.3.11.2 Transaction Set Control Segments

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


B.1.1.3.11.3 Functional Group Control Segments

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


B.1.1.3.11.4 Relations among Control Segments

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

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

ST Transaction Set Header, starts a transaction set.

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

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

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

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

SE Transaction Set Trailer, ends a transaction set.

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

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


B.1.1.3.12 Transaction Set

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


B.1.1.3.12.1 Transaction Set Header and Trailer

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


B.1.1.3.12.2 Data Segment Groups

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


B.1.1.3.12.3 Repeated Occurrences of Single Data Segments

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


B.1.1.3.12.4 Loops of Data Segments

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


B.1.1.3.12.4.1 Unbounded Loops

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

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

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


B.1.1.3.12.4.2 Bounded Loops

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


B.1.1.3.12.5 Data Segments in a Transaction Set

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


B.1.1.3.12.6 Data Segment Requirement Designators

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

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

B.1.1.3.12.7 Data Segment Position

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


B.1.1.3.12.8 Data Segment Occurrence

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


B.1.1.3.13 Functional Group

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


B.1.1.4.1 Interchange Control Structures

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

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

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

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

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


B.1.1.4.2 Functional Groups

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

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

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


B.1.1.4.3 HL Structures

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

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

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

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

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

The two examples below illustrate this requirement:

Example 1 based on Implementation Guide 811X201:

INSURER

First STATE in transaction (child of INSURER)

First POLICY in transaction (child of first STATE)

First VEHICLE in transaction (child of first POLICY)

Second POLICY in transaction (child of first STATE)

Second VEHICLE in transaction (child of second POLICY)

Third VEHICLE in transaction (child of second POLICY)

Second STATE in transaction (child of INSURER)

Third POLICY in transaction (child of second STATE)

Fourth VEHICLE in transaction (child of third POLICY)


Example 2 based on Implementation Guide 837X141

First PROVIDER in transaction

First SUBSCRIBER in transaction (child of first PROVIDER)

Second PROVIDER in transaction

Second SUBSCRIBER in transaction (child of second PROVIDER)

First DEPENDENT in transaction (child of second SUBSCRIBER)

Second DEPENDENT in transaction (child of second SUBSCRIBER)

Third SUBSCRIBER in transaction (child of second PROVIDER)

Third PROVIDER in transaction

Fourth SUBSCRIBER in transaction (child of third PROVIDER)

Fifth SUBSCRIBER in transaction (child of third PROVIDER

Third DEPENDENT in transaction (child of fifth SUBSCRIBER)


B.1.1.5.1 Interchange Acknowledgment, TA1

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

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


B.1.1.5.2 Functional Acknowledgment, 997

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

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


B.2 Object Descriptors

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

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

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

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

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

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

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

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


Appendix D. Change Summary

This Implementation Guide defines X12N implementation 005010X216 of the Health Care Services Review - Notification (278). It is based on version/release/sub-release 005010 of the ASC X12 standards.

The previous X12N implementation Guide of the Health Care Services Review - Notification was 004010X111. It was based on version/release/sub-release 004010 of the ASC X12 standards.

This appendix provides a change summary of changes between 004010X110 and 005010X216.


D.1 Change Descriptions

  1. Sections one and two have been revised in accordance with version 5010 of the X12N Implementation Guide Handbook.
  2. Section 1.1 section description has changed.
  3. Sections 1.1.1 and 1.1.2 have been deleted.
  4. Section 1.2 has been revised to reflect version and release information for this implementation guide.
  5. Section 1.3 has been replaced with a new section.
  6. Section 1.3 has been changed to section 1.4.
  7. Section 1.3.1 was renamed to Business Terminology and moved to section 1.5.
  8. Section 1.3.2 was changed to section 1.4.1.
  9. Section 1.3.2.2 was changed to section 1.6.
  10. Section 1.3.3 was changed to section 1.4.2.
  11. Section 1.4 was changed to section 1.4.3.
  12. Section 1.4.1 was renamed to Implementation Limitations and moved to section 1.3.
  13. Section 1.5 has been changed to section 1.11.
  14. Section 1.5.1 has been changed to section 1.11.1.
  15. Section 1.5.2 has been changed to section 1.11.2.
  16. Section 1.5.3 has been changed to section 1.11.3.
  17. Section 1.5.4 has been changed to section 1.11.4.
  18. Section 2 has been changed to section 1.12.
  19. Section 1.6 has been added to explain the use of transaction acknowledgments with this implementation guide.
  20. Section 2.2.1 has been changed to section 1.12.2.1.
  21. Section 2.2.2 has been changed to section 1.12.2.2.
  22. Section 2.2.3 has been changed to section 1.12.2.3.
  23. Section 2.2.4 has been changed to section 1.12.2.4.
  24. Section 1.12.3 Patient Event (Loop E) was added and will provide the information on the patient event associated with all health care service review. The patient even level supports the types of information that was previously carried in the subscriber and dependent level (e.g. accident date, Diagnosis information, patient event tracking number etc).

    The patient event level also supports the UM segment which identifies the types of health care services review information. The UM segment is also supported in the services level (2000 F). The service level supports detailed information contained in the patient event level unless other wise specified with condition and usage statements.

    The Service Provider information will be captured in either the Patient Event Provider (Loop 2010EA) or the Service Provider (Loop 2010FA).

  25. Sections 1.7, 1.8, 1.9, 1.10 and 1.11 have been added.
  26. Section 2.3.1 has been changed to 1.12.3.4.
  27. Section 2.3.2 has been changed to 1.12.3.5.
  28. Section 2.3.3 has been changed to 1.12.3.6.
  29. Section 2.4 has been changed to 1.12.4.
  30. Section 2.5 has been changed to 1.12.5.
  31. Added a clarification and example for revisions in section 1.12.5.1.
  32. Section 2.6 has been changed to 1.12.6.
  33. Section 3 and all sub-sections changed to section 2.
  34. Situational notes have been revised in accordance with version 5010 of the X12N Implementation Guide Handbook.
  35. All notes and codes concerning NPI, have been updated for clarification.
  36. Added code values and notes in the HI and SV2 segments to accommodate ICD-10 diagnosis and procedure codes.

Health Care Services Review Request:

  1. Updated segment examples to reflect changes and bring them up to date.
  2. Changed ST03 to required. (Implementation Guide Version Name)
  3. Changed BHT01 qualifier to 0007 Information Source, Information Receiver, Subscriber, Dependent, Event, Services.
  4. Added TR3 note to N3 segment in 2010A.
  5. Added TR3 note to N4 segment in 2010A.
  6. Changed PRV02 qualifier to PXC in Loop 2010A.
  7. Moved Patient Event Tracking Number (Loop 2000C) to Patient Event Loop (Loop E).
  8. Moved all dates from Subscriber Loop to Patient Event Loop (Loop E).
  9. Moved Subscriber Diagnosis to Patient Diagnosis in the Patient Event Loop (Loop E).
  10. Moved Additional Patient Information (Loop 2000C) to Patient Event Loop (Loop E).
  11. Moved Patient Event Tracking Number (Loop 2000D) to Patient Event Loop (Loop E).
  12. Moved all dates from Dependent Loop to Patient Event Loop (Loop E).
  13. Moved Dependent Diagnosis to Patient Diagnosis in the Patient Event Loop (Loop E).
  14. Moved Additional Patient Information (Loop 2000D) to Patient Event Loop (Loop E).
  15. Moved Admission Date, Discharge Date and all Certification Dates from Service Loop (Loop 2000F) to Patient Event Loop (Loop 2000E).
  16. Changed UM06 situational rule, added code E for elective and removed R for routine.
  17. Removed CRC Patient Condition Information.
  18. Moved CL1, CR1, CR2, CR5 and CR6 segments from Service Loop (Loop 2000F) to Patient Event Loop (Loop 2000E).
  19. Removed HI Procedures segment from Service Loop (Loop 2000F) and replaced it with SV1 Professional Service, SV2 Institutional Service Line and SV3 Dental Service segments.
  20. Added TOO Tooth Information segment to the Service Loop (Loop 2000F).
  21. Added REF Administrative Reference Number segment to the Service Loop (Loop 2000F).
  22. Changed CR1 situational rule and added TR3 note in Loop 2000E.
  23. Deleted usage note for code A in CR104 in Loop 2000E.
  24. Changed CR106 situational rule in Loop 2000E.
  25. Changed CR107, CR108, CR109 and CR110 to not used in Loop 2000E.
  26. Changed CR212 to not used in Loop 2000E.
  27. Changed CR507, CR508 and CR509 situational rules in Loop 2000E.
  28. Changed CR510, CR511, CR512, CR513, CR514 and CR515 to not used in Loop 2000E.
  29. Changed CR6 situational rule and segment note in Loop 2000E.
  30. Changed CR606 usage to not used in Loop 2000E.
  31. Deleted previously used codes and added W to CR607 in Loop 2000E.
  32. Changed CR609 through CR621 to not used in Loop 2000E.
  33. Added Patient Event Provider Name (Loop 2010EA).
  34. Added Patient Event Additional Patient Information Contact Name (Loop 2010EB).
  35. Added Patient Event Transportation Information (Loop 2010EC).
  36. Added Patient Event Other UMO Name (Loop 2010ED).
  37. Deleted NM101 1T qualifier and added qualifiers 77, G3 and QV in Loop 2010EA.
  38. Changed NM103 through NM109 situational rules in Loop 2010EA.
  39. Changed REF situational rule and added TR3 Note in Loop 2010EA.
  40. Changed N3 situational rule in Loop 2010EA.
  41. Changed N401 usage to required in Loop 2010EA.
  42. Changed N402 situational rule in Loop 2010EA.
  43. Changed N403 situational rule in Loop 2010EA.
  44. Changed N404 situational rule in Loop 2010EA.
  45. Changed PER03 and PER04 situational rules in Loop 2010EA.
  46. Change PRV situational rule in Loop 2010EA.
  47. Changed PRV02 and PRV3 usage to required in Loop 2010EA.
  48. Changed PRV02 qualifier to PXC in Loop 2010EA.
  49. Changed TRN situational rule and added TR3 note in Loop 2000F.
  50. Changed UM03 situational rule and added codes 11, 66, 88, B1, BL, BN, BP, BQ, BY, BZ, C1, GY, IC, MH, NI, ON, PT, PU, RN, RT, TC, TN.
  51. Removed codes 34, 48, 50, 51, 52, 53, 57, 58, 59, 94, 95, 98, 99, A0, A1, A2, A3, A7, A8, AB and AC from UM03.
  52. Added Service Provider Name Loop (Loop 2010F).
  53. Deleted NM101 1T qualifier and added qualifiers 77, G3 and QV in Loop 2010F.

Health Care Services Review Response:

  1. Updated segment examples to reflect changes and bring them up to date.
  2. Changed ST03 to required. (Implementation Guide Version Name)
  3. Changed BHT01 qualifier to 0007 Information Source, Information Receiver, Subscriber, Dependent, Event, Services.
  4. Changed PRV02 qualifier to PXC in Loop 2010A.
  5. Changed UM situational rule in Loop 2000F.
  6. Added codes 11, 66, 88, B1, BL, BN, BP, BQ, BY, BZ, C1, GY, IC, MH, NI, ON, PT, PU, RN, RT, TC, TN.
  7. Removed codes 34, 48, 50, 51, 52, 53, 57, 58, 59, 94, 95, 98, 99, A0, A1, A2, A3, A7, A8, AB and AC from UM03.
  8. Changed UM04 situational rule in Loop 2000F.
  9. Added note to HCR03 in Loop 2000F.
  10. Removed HI Procedures segment from Service Loop (Loop 2000F) and replaced it with SV1 Professional Service, SV2 Institutional Service Line and SV3 Dental Service segments.
  11. Added TOO Tooth Information segment to the Service Loop (Loop 2000F).
  12. Added Service Provider Name (Loop 2010F).

Examples:

  1. Updated examples to reflect changes and bring them up to date.

Appendixes:
Appendixes have been revised in accordance with version 5010 of the X12N Implementation Guide Handbook.


Appendix E - Data Element Name Index

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

Legend

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

Accident Date
Date of the accident related to charges or to the patient's current condition, diagnosis, or treatment referenced in the transaction.
278 - Health Care Services Review Notification
D | 2000E | DTP03 | - | 1251

Action Code
Code indicating type of action
278 - Health Care Services Review Notification
D | 2000E | HCR01 | - | 306
D | 2000F | HCR01 | - | 306
278 - Health Care Services Review Acknowledgment
D | 2000E | HCR01 | - | 306
D | 2000F | HCR01 | - | 306

Additional Patient Information Contact City Name
The city name of the Additional Patient Information Contact.
278 - Health Care Services Review Notification
D | 2010EB | N401 | - | 19

Additional Patient Information Contact Postal Zone or ZIP Code
The postal code in the address of the Additional Patient Information Contact.
278 - Health Care Services Review Notification
D | 2010EB | N403 | - | 116

Additional Patient Information Contact State Code
Code identifying the state or province in the address of the Additional Patient Information Contact.
278 - Health Care Services Review Notification
D | 2010EB | N402 | - | 156

Administrative Reference Number
Unique reference number assigned by the UMO to this service review.
278 - Health Care Services Review Notification
D | 2000E | REF02 | - | 127
D | 2000F | REF02 | - | 127
278 - Health Care Services Review Acknowledgment
D | 2000E | REF02 | - | 127
D | 2000F | REF02 | - | 127

Admission Source Code
Code indicating the source of this admission.
278 - Health Care Services Review Notification
D | 2000E | CL102 | - | 1314

Admission Type Code
Code indicating the priority of this admission.
278 - Health Care Services Review Notification
D | 2000E | CL101 | - | 1315

Ambulance Transport Code
Code indicating the type of ambulance transport.
278 - Health Care Services Review Notification
D | 2000E | CR103 | - | 1316

Attachment Control Number
Identification number of attachment related to the claim.
278 - Health Care Services Review Notification
D | 2000E | PWK06 | - | 67
D | 2000F | PWK06 | - | 67

Attachment Description
Free-form text describing attachments related to the claim.
278 - Health Care Services Review Notification
D | 2000E | PWK07 | - | 352
D | 2000F | PWK07 | - | 352

Attachment Report Type Code
Code to specify the type of attachment that is related to the claim.
278 - Health Care Services Review Notification
D | 2000E | PWK01 | - | 755
D | 2000F | PWK01 | - | 755

Birth Sequence Number
A number indicating the order of birth for the identified person in relationship to family members with the same date of birth.
278 - Health Care Services Review Notification
D | 2010D | INS17 | - | 1470
278 - Health Care Services Review Acknowledgment
D | 2010D | INS17 | - | 1470

Certification Effective Date
The date when the certification takes effect or the date range within which the certification is effective.
278 - Health Care Services Review Notification
D | 2000E | DTP03 | - | 1251
D | 2000F | DTP03 | - | 1251
278 - Health Care Services Review Acknowledgment
D | 2000E | DTP03 | - | 1251
D | 2000F | DTP03 | - | 1251

Certification Expiration Date
Date on which the certification will expire.
278 - Health Care Services Review Notification
D | 2000E | DTP03 | - | 1251
D | 2000F | DTP03 | - | 1251
278 - Health Care Services Review Acknowledgment
D | 2000E | DTP03 | - | 1251
D | 2000F | DTP03 | - | 1251

Certification Issue Date
The date when the certification was issued.
278 - Health Care Services Review Notification
D | 2000E | DTP03 | - | 1251
D | 2000F | DTP03 | - | 1251
278 - Health Care Services Review Acknowledgment
D | 2000E | DTP03 | - | 1251
D | 2000F | DTP03 | - | 1251

Certification Type Code
Code indicating the type of certification.
278 - Health Care Services Review Notification
D | 2000E | UM02 | - | 1322
D | 2000E | CR608 | - | 1322
D | 2000F | UM02 | - | 1322
278 - Health Care Services Review Acknowledgment
D | 2000E | UM02 | - | 1322
D | 2000F | UM02 | - | 1322

Code List Qualifier Code
Code identifying a specific industry code list.
278 - Health Care Services Review Notification
D | 2000F | TOO01 | - | 1270
278 - Health Care Services Review Acknowledgment
D | 2000F | TOO01 | - | 1270

Communication Number Qualifier
Code identifying the type of communication number.
278 - Health Care Services Review Notification
D | 2010A | PER03 | - | 365
D | 2010A | PER05 | - | 365
D | 2010A | PER07 | - | 365
D | 2010EA | PER03 | - | 365
D | 2010EA | PER05 | - | 365
D | 2010EA | PER07 | - | 365
D | 2010EB | PER03 | - | 365
D | 2010EB | PER05 | - | 365
D | 2010EB | PER07 | - | 365
D | 2010F | PER03 | - | 365
D | 2010F | PER05 | - | 365
D | 2010F | PER07 | - | 365
278 - Health Care Services Review Acknowledgment
D | 2010B | PER03 | - | 365
D | 2010B | PER05 | - | 365
D | 2010B | PER07 | - | 365

Contact Function Code
Code identifying the major duty or responsibility of the person or group named.
278 - Health Care Services Review Notification
D | 2010A | PER01 | - | 366
D | 2010EA | PER01 | - | 366
D | 2010EB | PER01 | - | 366
D | 2010F | PER01 | - | 366
278 - Health Care Services Review Acknowledgment
D | 2010B | PER01 | - | 366

Country Code
Code indicating the geographic location.
278 - Health Care Services Review Notification
D | 2010A | N404 | - | 26
D | 2010C | N404 | - | 26
D | 2010D | N404 | - | 26
D | 2010EA | N404 | - | 26
D | 2010EB | N404 | - | 26
D | 2010F | N404 | - | 26

Country Subdivision Code
Code identifying the country subdivision.
278 - Health Care Services Review Notification
D | 2010A | N407 | - | 1715
D | 2010C | N407 | - | 1715
D | 2010D | N407 | - | 1715
D | 2010EA | N407 | - | 1715
D | 2010EB | N407 | - | 1715
D | 2010F | N407 | - | 1715

Daily Oxygen Use Count
Number of times per day that the patient must use oxygen.
278 - Health Care Services Review Notification
D | 2000E | CR507 | - | 380

Date Time Period Format Qualifier
Code indicating the date format, time format, or date and time format.
278 - Health Care Services Review Notification
D | 2010C | DMG01 | - | 1250
D | 2010D | DMG01 | - | 1250
D | 2000E | DTP02 | - | 1250
D | 2000E | DTP02 | - | 1250
D | 2000E | DTP02 | - | 1250
D | 2000E | DTP02 | - | 1250
D | 2000E | DTP02 | - | 1250
D | 2000E | DTP02 | - | 1250
D | 2000E | DTP02 | - | 1250
D | 2000E | DTP02 | - | 1250
D | 2000E | DTP02 | - | 1250
D | 2000E | DTP02 | - | 1250
D | 2000E | HI01 | C022-03 | 1250
D | 2000E | HI02 | C022-03 | 1250
D | 2000E | HI03 | C022-03 | 1250
D | 2000E | HI04 | C022-03 | 1250
D | 2000E | HI05 | C022-03 | 1250
D | 2000E | HI06 | C022-03 | 1250
D | 2000E | HI07 | C022-03 | 1250
D | 2000E | HI08 | C022-03 | 1250
D | 2000E | HI09 | C022-03 | 1250
D | 2000E | HI10 | C022-03 | 1250
D | 2000E | HI11 | C022-03 | 1250
D | 2000E | HI12 | C022-03 | 1250
D | 2000E | CR603 | - | 1250
D | 2010ED | DTP02 | - | 1250
D | 2000F | DTP02 | - | 1250
D | 2000F | DTP02 | - | 1250
D | 2000F | DTP02 | - | 1250
D | 2000F | DTP02 | - | 1250
278 - Health Care Services Review Acknowledgment
D | 2010C | DMG01 | - | 1250
D | 2010D | DMG01 | - | 1250
D | 2000E | DTP02 | - | 1250
D | 2000E | DTP02 | - | 1250
D | 2000E | DTP02 | - | 1250
D | 2000E | DTP02 | - | 1250
D | 2000E | DTP02 | - | 1250
D | 2000E | DTP02 | - | 1250
D | 2000E | HI01 | C022-03 | 1250
D | 2000E | HI02 | C022-03 | 1250
D | 2000E | HI03 | C022-03 | 1250
D | 2000E | HI04 | C022-03 | 1250
D | 2000E | HI05 | C022-03 | 1250
D | 2000E | HI06 | C022-03 | 1250
D | 2000E | HI07 | C022-03 | 1250
D | 2000E | HI08 | C022-03 | 1250
D | 2000E | HI09 | C022-03 | 1250
D | 2000E | HI10 | C022-03 | 1250
D | 2000E | HI11 | C022-03 | 1250
D | 2000E | HI12 | C022-03 | 1250
D | 2000F | DTP02 | - | 1250
D | 2000F | DTP02 | - | 1250
D | 2000F | DTP02 | - | 1250
D | 2000F | DTP02 | - | 1250

Date Time Qualifier
Code specifying the type of date or time or both date and time.
278 - Health Care Services Review Notification
D | 2000E | DTP01 | - | 374
D | 2000E | DTP01 | - | 374
D | 2000E | DTP01 | - | 374
D | 2000E | DTP01 | - | 374
D | 2000E | DTP01 | - | 374
D | 2000E | DTP01 | - | 374
D | 2000E | DTP01 | - | 374
D | 2000E | DTP01 | - | 374
D | 2000E | DTP01 | - | 374
D | 2000E | DTP01 | - | 374
D | 2010ED | DTP01 | - | 374
D | 2000F | DTP01 | - | 374
D | 2000F | DTP01 | - | 374
D | 2000F | DTP01 | - | 374
D | 2000F | DTP01 | - | 374
278 - Health Care Services Review Acknowledgment
D | 2000E | DTP01 | - | 374
D | 2000E | DTP01 | - | 374
D | 2000E | DTP01 | - | 374
D | 2000E | DTP01 | - | 374
D | 2000E | DTP01 | - | 374
D | 2000E | DTP01 | - | 374
D | 2000F | DTP01 | - | 374
D | 2000F | DTP01 | - | 374
D | 2000F | DTP01 | - | 374
D | 2000F | DTP01 | - | 374

Delivery Frequency Code
Code which specifies frequency by which services can be performed.
278 - Health Care Services Review Notification
D | 2000E | HSD07 | - | 678
D | 2000F | HSD07 | - | 678

Delivery Pattern Time Code
Code which specifies the time delivery pattern of the services.
278 - Health Care Services Review Notification
D | 2000E | HSD08 | - | 679
D | 2000F | HSD08 | - | 679

Dependent Address Line
The street address of the patient.
278 - Health Care Services Review Notification
D | 2010D | N301 | - | 166
D | 2010D | N302 | - | 166

Dependent Birth Date
The date of birth of the dependent.
278 - Health Care Services Review Notification
D | 2010D | DMG02 | - | 1251
278 - Health Care Services Review Acknowledgment
D | 2010D | DMG02 | - | 1251

Dependent City Name
The city name of the patient.
278 - Health Care Services Review Notification
D | 2010D | N401 | - | 19

Dependent First Name
The first name of the dependent.
278 - Health Care Services Review Notification
D | 2010D | NM104 | - | 1036
278 - Health Care Services Review Acknowledgment
D | 2010D | NM104 | - | 1036

Dependent Gender Code
A code indicating the gender of the dependent.
278 - Health Care Services Review Notification
D | 2010D | DMG03 | - | 1068
278 - Health Care Services Review Acknowledgment
D | 2010D | DMG03 | - | 1068

Dependent Last Name
The last name of the dependent.
278 - Health Care Services Review Notification
D | 2010D | NM103 | - | 1035
278 - Health Care Services Review Acknowledgment
D | 2010D | NM103 | - | 1035

Dependent Middle Name or Initial
The middle name of the dependent.
278 - Health Care Services Review Notification
D | 2010D | NM105 | - | 1037
278 - Health Care Services Review Acknowledgment
D | 2010D | NM105 | - | 1037

Dependent Name Suffix
A suffix following the name, including the generation of the patient, such as I, II, III, Jr, Sr.
278 - Health Care Services Review Notification
D | 2010D | NM107 | - | 1039
278 - Health Care Services Review Acknowledgment
D | 2010D | NM107 | - | 1039

Dependent Postal Zone or ZIP Code
The zip code of the dependent.
278 - Health Care Services Review Notification
D | 2010D | N403 | - | 116

Dependent Primary Identifier
Identifies the code number by which the dependent is known.
278 - Health Care Services Review Acknowledgment
D | 2010D | NM109 | - | 67

Dependent State Code
The state postal code of the dependent.
278 - Health Care Services Review Notification
D | 2010D | N402 | - | 156

Dependent Supplemental Identifier
Identifies another or additional distinguishing code number associated with the dependent.
278 - Health Care Services Review Notification
D | 2010D | REF02 | - | 127
278 - Health Care Services Review Acknowledgment
D | 2010D | REF02 | - | 127

Description
A free-form description to clarify the related data elements and their content.
278 - Health Care Services Review Notification
D | 2000F | SV307 | - | 352

Diagnosis Code
An ICD-9-CM Diagnosis Code identifying a diagnosed medical condition.
278 - Health Care Services Review Notification
D | 2000E | HI01 | C022-02 | 1271
D | 2000E | HI02 | C022-02 | 1271
D | 2000E | HI03 | C022-02 | 1271
D | 2000E | HI04 | C022-02 | 1271
D | 2000E | HI05 | C022-02 | 1271
D | 2000E | HI06 | C022-02 | 1271
D | 2000E | HI07 | C022-02 | 1271
D | 2000E | HI08 | C022-02 | 1271
D | 2000E | HI09 | C022-02 | 1271
D | 2000E | HI10 | C022-02 | 1271
D | 2000E | HI11 | C022-02 | 1271
D | 2000E | HI12 | C022-02 | 1271
278 - Health Care Services Review Acknowledgment
D | 2000E | HI01 | C022-02 | 1271
D | 2000E | HI02 | C022-02 | 1271
D | 2000E | HI03 | C022-02 | 1271
D | 2000E | HI04 | C022-02 | 1271
D | 2000E | HI05 | C022-02 | 1271
D | 2000E | HI06 | C022-02 | 1271
D | 2000E | HI07 | C022-02 | 1271
D | 2000E | HI08 | C022-02 | 1271
D | 2000E | HI09 | C022-02 | 1271
D | 2000E | HI10 | C022-02 | 1271
D | 2000E | HI11 | C022-02 | 1271
D | 2000E | HI12 | C022-02 | 1271

Diagnosis Code Pointer
A pointer to the claim diagnosis code in the order of importance to this service.
278 - Health Care Services Review Notification
D | 2000F | SV107 | C004-01 | 1328
D | 2000F | SV107 | C004-02 | 1328
D | 2000F | SV107 | C004-03 | 1328
D | 2000F | SV107 | C004-04 | 1328

Diagnosis Date
Date the diagnosis was established or recorded.
278 - Health Care Services Review Notification
D | 2000E | HI01 | C022-04 | 1251
D | 2000E | HI02 | C022-04 | 1251
D | 2000E | HI03 | C022-04 | 1251
D | 2000E | HI04 | C022-04 | 1251
D | 2000E | HI05 | C022-04 | 1251
D | 2000E | HI06 | C022-04 | 1251
D | 2000E | HI07 | C022-04 | 1251
D | 2000E | HI08 | C022-04 | 1251
D | 2000E | HI09 | C022-04 | 1251
D | 2000E | HI10 | C022-04 | 1251
D | 2000E | HI11 | C022-04 | 1251
D | 2000E | HI12 | C022-04 | 1251
278 - Health Care Services Review Acknowledgment
D | 2000E | HI01 | C022-04 | 1251
D | 2000E | HI02 | C022-04 | 1251
D | 2000E | HI03 | C022-04 | 1251
D | 2000E | HI04 | C022-04 | 1251
D | 2000E | HI05 | C022-04 | 1251
D | 2000E | HI06 | C022-04 | 1251
D | 2000E | HI07 | C022-04 | 1251
D | 2000E | HI08 | C022-04 | 1251
D | 2000E | HI09 | C022-04 | 1251
D | 2000E | HI10 | C022-04 | 1251
D | 2000E | HI11 | C022-04 | 1251
D | 2000E | HI12 | C022-04 | 1251

Diagnosis Type Code
Code identifying the type of diagnosis.
278 - Health Care Services Review Notification
D | 2000E | HI01 | C022-01 | 1270
D | 2000E | HI02 | C022-01 | 1270
D | 2000E | HI03 | C022-01 | 1270
D | 2000E | HI04 | C022-01 | 1270
D | 2000E | HI05 | C022-01 | 1270
D | 2000E | HI06 | C022-01 | 1270
D | 2000E | HI07 | C022-01 | 1270
D | 2000E | HI08 | C022-01 | 1270
D | 2000E | HI09 | C022-01 | 1270
D | 2000E | HI10 | C022-01 | 1270
D | 2000E | HI11 | C022-01 | 1270
D | 2000E | HI12 | C022-01 | 1270
278 - Health Care Services Review Acknowledgment
D | 2000E | HI01 | C022-01 | 1270
D | 2000E | HI02 | C022-01 | 1270
D | 2000E | HI03 | C022-01 | 1270
D | 2000E | HI04 | C022-01 | 1270
D | 2000E | HI05 | C022-01 | 1270
D | 2000E | HI06 | C022-01 | 1270
D | 2000E | HI07 | C022-01 | 1270
D | 2000E | HI08 | C022-01 | 1270
D | 2000E | HI09 | C022-01 | 1270
D | 2000E | HI10 | C022-01 | 1270
D | 2000E | HI11 | C022-01 | 1270
D | 2000E | HI12 | C022-01 | 1270

EPSDT Indicator
An indicator of whether or not Early and Periodic Screening for Diagnosis and Treatment of children services are involved with this detail line.
278 - Health Care Services Review Notification
D | 2000F | SV111 | - | 1073
278 - Health Care Services Review Acknowledgment
D | 2000F | SV111 | - | 1073

Employment Status Code
A code used to define the employment status of the individual covered by this insurance payer.
278 - Health Care Services Review Notification
D | 2010C | INS08 | - | 584
278 - Health Care Services Review Acknowledgment
D | 2010C | INS08 | - | 584

Entity Identifier Code
Code identifying an organizational entity, a physical location, property or an individual.
278 - Health Care Services Review Notification
D | 2010A | NM101 | - | 98
D | 2010B | NM101 | - | 98
D | 2010C | NM101 | - | 98
D | 2010D | NM101 | - | 98
D | 2010EA | NM101 | - | 98
D | 2010EB | NM101 | - | 98
D | 2010EC | NM101 | - | 98
D | 2010ED | NM101 | - | 98
D | 2010F | NM101 | - | 98
278 - Health Care Services Review Acknowledgment
D | 2010A | NM101 | - | 98
D | 2010B | NM101 | - | 98
D | 2010C | NM101 | - | 98
D | 2010D | NM101 | - | 98
D | 2010E | NM101 | - | 98
D | 2010F | NM101 | - | 98

Entity Type Qualifier
Code qualifying the type of entity.
278 - Health Care Services Review Notification
D | 2010A | NM102 | - | 1065
D | 2010B | NM102 | - | 1065
D | 2010C | NM102 | - | 1065
D | 2010D | NM102 | - | 1065
D | 2010EA | NM102 | - | 1065
D | 2010EB | NM102 | - | 1065
D | 2010EC | NM102 | - | 1065
D | 2010ED | NM102 | - | 1065
D | 2010F | NM102 | - | 1065
278 - Health Care Services Review Acknowledgment
D | 2010A | NM102 | - | 1065
D | 2010B | NM102 | - | 1065
D | 2010C | NM102 | - | 1065
D | 2010D | NM102 | - | 1065
D | 2010E | NM102 | - | 1065
D | 2010F | NM102 | - | 1065

Estimated Birth Date
Date delivery is expected.
278 - Health Care Services Review Notification
D | 2000E | DTP03 | - | 1251

Facility Code Qualifier
Code identifying the type of facility referenced.
278 - Health Care Services Review Notification
D | 2000E | UM04 | C023-02 | 1332
D | 2000F | UM04 | C023-02 | 1332
278 - Health Care Services Review Acknowledgment
D | 2000E | UM04 | C023-02 | 1332
D | 2000F | UM04 | C023-02 | 1332

Facility Type Code
Code identifying the type of facility where services were performed; the first and second positions of the Uniform Bill Type code or the Place of Service code from the Electronic Media Claims National Standard Format.
278 - Health Care Services Review Notification
D | 2000E | UM04 | C023-01 | 1331
D | 2000F | UM04 | C023-01 | 1331
278 - Health Care Services Review Acknowledgment
D | 2000E | UM04 | C023-01 | 1331
D | 2000F | UM04 | C023-01 | 1331

Follow-up Action Code
Code identifying follow-up actions allowed.
278 - Health Care Services Review Notification
D | 2010EC | AAA04 | - | 889
278 - Health Care Services Review Acknowledgment
D | 2000A | AAA04 | - | 889
D | 2010A | AAA04 | - | 889
D | 2010B | AAA04 | - | 889
D | 2000C | AAA04 | - | 889
D | 2010C | AAA04 | - | 889
D | 2000D | AAA04 | - | 889
D | 2010D | AAA04 | - | 889
D | 2000E | AAA04 | - | 889
D | 2010E | AAA04 | - | 889
D | 2000F | AAA04 | - | 889
D | 2010F | AAA04 | - | 889

Free Form Message Text
Text used to convey information related to the transaction.
278 - Health Care Services Review Notification
D | 2000E | MSG01 | - | 933
D | 2000F | MSG01 | - | 933

Hierarchical Child Code
Code indicating if there are hierarchical child data segments subordinate to the level being described.
278 - Health Care Services Review Notification
D | 2000A | HL04 | - | 736
D | 2000B | HL04 | - | 736
D | 2000C | HL04 | - | 736
D | 2000D | HL04 | - | 736
D | 2000E | HL04 | - | 736
D | 2000F | HL04 | - | 736
278 - Health Care Services Review Acknowledgment
D | 2000A | HL04 | - | 736
D | 2000B | HL04 | - | 736
D | 2000C | HL04 | - | 736
D | 2000D | HL04 | - | 736
D | 2000E | HL04 | - | 736
D | 2000F | HL04 | - | 736

Hierarchical ID Number
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure.
278 - Health Care Services Review Notification
D | 2000A | HL01 | - | 628
D | 2000B | HL01 | - | 628
D | 2000C | HL01 | - | 628
D | 2000D | HL01 | - | 628
D | 2000E | HL01 | - | 628
D | 2000F | HL01 | - | 628
278 - Health Care Services Review Acknowledgment
D | 2000A | HL01 | - | 628
D | 2000B | HL01 | - | 628
D | 2000C | HL01 | - | 628
D | 2000D | HL01 | - | 628
D | 2000E | HL01 | - | 628
D | 2000F | HL01 | - | 628

Hierarchical Level Code
Code defining the characteristic of a level in a hierarchical structure.
278 - Health Care Services Review Notification
D | 2000A | HL03 | - | 735
D | 2000B | HL03 | - | 735
D | 2000C | HL03 | - | 735
D | 2000D | HL03 | - | 735
D | 2000E | HL03 | - | 735
D | 2000F | HL03 | - | 735
278 - Health Care Services Review Acknowledgment
D | 2000A | HL03 | - | 735
D | 2000B | HL03 | - | 735
D | 2000C | HL03 | - | 735
D | 2000D | HL03 | - | 735
D | 2000E | HL03 | - | 735
D | 2000F | HL03 | - | 735

Hierarchical Parent ID Number
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to.
278 - Health Care Services Review Notification
D | 2000B | HL02 | - | 734
D | 2000C | HL02 | - | 734
D | 2000D | HL02 | - | 734
D | 2000E | HL02 | - | 734
D | 2000F | HL02 | - | 734
278 - Health Care Services Review Acknowledgment
D | 2000B | HL02 | - | 734
D | 2000C | HL02 | - | 734
D | 2000D | HL02 | - | 734
D | 2000E | HL02 | - | 734
D | 2000F | HL02 | - | 734

Hierarchical Structure Code
Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set
278 - Health Care Services Review Notification
H | | BHT01 | - | 1005
278 - Health Care Services Review Acknowledgment
H | | BHT01 | - | 1005

Home Health Certification Period
Certification period for home health care covered by this plan of treatment.
278 - Health Care Services Review Notification
D | 2000E | CR604 | - | 1251

Home Health Start Date
Date Home Health services are scheduled or are anticipated to start.
278 - Health Care Services Review Notification
D | 2000E | CR602 | - | 373

Identification Code Qualifier
Code designating the system/method of code structure used for Identification Code (67).
278 - Health Care Services Review Notification
D | 2010A | NM108 | - | 66
D | 2010B | NM108 | - | 66
D | 2010C | NM108 | - | 66
D | 2000E | PWK05 | - | 66
D | 2010EA | NM108 | - | 66
D | 2010EB | NM108 | - | 66
D | 2000F | PWK05 | - | 66
D | 2010F | NM108 | - | 66
278 - Health Care Services Review Acknowledgment
D | 2010A | NM108 | - | 66
D | 2010B | NM108 | - | 66
D | 2010C | NM108 | - | 66
D | 2010D | NM108 | - | 66
D | 2010E | NM108 | - | 66
D | 2010F | NM108 | - | 66

Implementation Guide Version Name
Name of the referenced implementation guide version.
278 - Health Care Services Review Notification
H | | ST03 | - | 1705
278 - Health Care Services Review Acknowledgment
H | | ST03 | - | 1705

Individual Relationship Code
Code indicating the relationship between two individuals or entities.
278 - Health Care Services Review Notification
D | 2010C | INS02 | - | 1069
D | 2010D | INS02 | - | 1069
278 - Health Care Services Review Acknowledgment
D | 2010C | INS02 | - | 1069
D | 2010D | INS02 | - | 1069

Information Receiver Contact Communication Number
Communication Number for the Individual at information receiver to whom inquiries about this transaction should be directed.
278 - Health Care Services Review Acknowledgment
D | 2010B | PER04 | - | 364
D | 2010B | PER06 | - | 364
D | 2010B | PER08 | - | 364

Information Receiver Contact Name
Individual at information receiver to whom inquiries about this transaction should be directed.
278 - Health Care Services Review Acknowledgment
D | 2010B | PER02 | - | 93

Information Receiver First Name
The first name of the individual or organization who expects to receive information in response to a query.
278 - Health Care Services Review Notification
D | 2010B | NM104 | - | 1036
278 - Health Care Services Review Acknowledgment
D | 2010B | NM104 | - | 1036

Information Receiver Identifier
Unique number identifying the information receiver.
278 - Health Care Services Review Notification
D | 2010B | NM109 | - | 67
278 - Health Care Services Review Acknowledgment
D | 2010B | NM109 | - | 67

Information Receiver Last or Organization Name
The name of the organization or last name of the individual that expects to receive information or is receiving information.
278 - Health Care Services Review Notification
D | 2010B | NM103 | - | 1035
278 - Health Care Services Review Acknowledgment
D | 2010B | NM103 | - | 1035

Information Receiver Middle Name
The middle name of the individual or organization who expects to receive information in response to a query.
278 - Health Care Services Review Notification
D | 2010B | NM105 | - | 1037
278 - Health Care Services Review Acknowledgment
D | 2010B | NM105 | - | 1037

Information Receiver Name Suffix
The suffix to the name of the individual or organization who expects to receive information in response to a query.
278 - Health Care Services Review Notification
D | 2010B | NM107 | - | 1039
278 - Health Care Services Review Acknowledgment
D | 2010B | NM107 | - | 1039

Information Source Address Line
The street address of the information source
278 - Health Care Services Review Notification
D | 2010A | N301 | - | 166
D | 2010A | N302 | - | 166

Information Source City Name
The city name of the source
278 - Health Care Services Review Notification
D | 2010A | N401 | - | 19

Information Source Contact Communication Number
Complete Information Source contact communications number, including country or area code when applicable.
278 - Health Care Services Review Notification
D | 2010A | PER04 | - | 364
D | 2010A | PER06 | - | 364
D | 2010A | PER08 | - | 364

Information Source Contact Name
Information source contact name to whom inquiries about this transaction should be directed.
278 - Health Care Services Review Notification
D | 2010A | PER02 | - | 93

Information Source First Name
First name of an individual who is the source of the information.
278 - Health Care Services Review Notification
D | 2010A | NM104 | - | 1036
278 - Health Care Services Review Acknowledgment
D | 2010A | NM104 | - | 1036

Information Source Identifier
The Identification number of the individual or organization who provides the information in this transaction.
278 - Health Care Services Review Notification
D | 2010A | NM109 | - | 67
278 - Health Care Services Review Acknowledgment
D | 2010A | NM109 | - | 67

Information Source Last or Organization Name
The organization name or the last name of an individual who is the source of the information.
278 - Health Care Services Review Notification
D | 2010A | NM103 | - | 1035
278 - Health Care Services Review Acknowledgment
D | 2010A | NM103 | - | 1035

Information Source Middle Name
Middle name of an individual who is the source of the information.
278 - Health Care Services Review Notification
D | 2010A | NM105 | - | 1037
278 - Health Care Services Review Acknowledgment
D | 2010A | NM105 | - | 1037

Information Source Name Suffix
Suffix to the name of the individual who is the source of the information.
278 - Health Care Services Review Notification
D | 2010A | NM107 | - | 1039
278 - Health Care Services Review Acknowledgment
D | 2010A | NM107 | - | 1039

Information Source Postal Zone or ZIP Code
The zip code of the source.
278 - Health Care Services Review Notification
D | 2010A | N403 | - | 116

Information Source State Code
The state postal code of the source.
278 - Health Care Services Review Notification
D | 2010A | N402 | - | 156

Information Source Supplemental Identifier
Identifies another or additional distinguishing code number associated with the Information Source.
278 - Health Care Services Review Notification
D | 2010A | REF02 | - | 127
278 - Health Care Services Review Acknowledgment
D | 2010A | REF02 | - | 127

Insured Indicator
Indicates whether the insured is the subscriber or a dependent.
278 - Health Care Services Review Notification
D | 2010C | INS01 | - | 1073
D | 2010D | INS01 | - | 1073
278 - Health Care Services Review Acknowledgment
D | 2010C | INS01 | - | 1073
D | 2010D | INS01 | - | 1073

Last Menstrual Period Date
The date of the last menstrual period (LMP).
278 - Health Care Services Review Notification
D | 2000E | DTP03 | - | 1251

Level of Service Code
Code specifying the level of service rendered.
278 - Health Care Services Review Notification
D | 2000E | UM06 | - | 1338
278 - Health Care Services Review Acknowledgment
D | 2000E | UM06 | - | 1338

License Number State Code
The State Postal Code of a jurisdiction-assigned license number.
278 - Health Care Services Review Notification
D | 2010EA | REF03 | - | 352
D | 2010F | REF03 | - | 352
278 - Health Care Services Review Acknowledgment
D | 2010E | REF03 | - | 352
D | 2010F | REF03 | - | 352

Medicare Coverage Indicator
A code indicating the Medicare coverage exists.
278 - Health Care Services Review Notification
D | 2000E | CR607 | - | 1073

Notification Receipt Number
A receipt number to indicate receipt of the notification.
278 - Health Care Services Review Acknowledgment
D | 2000C | REF02 | - | 127
D | 2000D | REF02 | - | 127

Nursing Home Level of Care
Code specifying the level of care provided by a nursing home facility.
278 - Health Care Services Review Notification
D | 2000F | SV120 | - | 1337
D | 2000F | SV210 | - | 1337
278 - Health Care Services Review Acknowledgment
D | 2000F | SV120 | - | 1337
D | 2000F | SV210 | - | 1337

Nursing Home Residential Status Code
Code specifying the status of a nursing home resident at the time of service.
278 - Health Care Services Review Notification
D | 2000F | SV209 | - | 1345

Onset Date
Date of onset of indicated patient condition.
278 - Health Care Services Review Notification
D | 2000E | DTP03 | - | 1251

Oral Cavity Designation Code
Code identifying an oral cavity involved in the service.
278 - Health Care Services Review Notification
D | 2000F | SV304 | C006-01 | 1361
D | 2000F | SV304 | C006-02 | 1361
D | 2000F | SV304 | C006-03 | 1361
D | 2000F | SV304 | C006-04 | 1361
D | 2000F | SV304 | C006-05 | 1361
278 - Health Care Services Review Acknowledgment
D | 2000F | SV304 | C006-01 | 1361
D | 2000F | SV304 | C006-02 | 1361
D | 2000F | SV304 | C006-03 | 1361
D | 2000F | SV304 | C006-04 | 1361
D | 2000F | SV304 | C006-05 | 1361

Other UMO Denial Date
Date the other UMO denied the authorization request.
278 - Health Care Services Review Notification
D | 2010ED | DTP03 | - | 1251

Other UMO Denial Reason
Reason code for why the other UMO denied the authorization request.
278 - Health Care Services Review Notification
D | 2010ED | REF02 | - | 127
D | 2010ED | REF04 | C040-02 | 127
D | 2010ED | REF04 | C040-04 | 127

Other UMO Name
Name of other UMO.
278 - Health Care Services Review Notification
D | 2010ED | NM103 | - | 1035

Oxygen Delivery System Code
Code to indicate if a particular form of delivery was prescribed.
278 - Health Care Services Review Notification
D | 2000E | CR517 | - | 1382

Oxygen Equipment Type Code
Code indicating the specific type of equipment prescribed for the delivery of oxygen.
278 - Health Care Services Review Notification
D | 2000E | CR503 | - | 1348
D | 2000E | CR504 | - | 1348
D | 2000E | CR518 | - | 1348

Oxygen Flow Rate
The oxygen flow rate in liters per minute.
278 - Health Care Services Review Notification
D | 2000E | CR506 | - | 380

Oxygen Use Period Hour Count
Number of hours per period of oxygen use.
278 - Health Care Services Review Notification
D | 2000E | CR508 | - | 380

Patient Event Provider Address Line
Address line in the mailing address of the provider to whom the patient has been or will be referred for this patient event.
278 - Health Care Services Review Notification
D | 2010EA | N301 | - | 166
D | 2010EA | N302 | - | 166

Patient Event Provider City Name
Name of the city in the mailing address of the provider to whom the patient has been or will be referred for this patient event.
278 - Health Care Services Review Notification
D | 2010EA | N401 | - | 19

Patient Event Provider Contact Communication Number
Complete patient event provider contact communications number, including country or area code when applicable.
278 - Health Care Services Review Notification
D | 2010EA | PER04 | - | 364
D | 2010EA | PER06 | - | 364
D | 2010EA | PER08 | - | 364

Patient Event Provider Contact Name
Name of the person, group, or organization to contact at the entity where the patient event has or will occur.
278 - Health Care Services Review Notification
D | 2010EA | PER02 | - | 93

Patient Event Provider First Name
First name of the provider to whom the patient has been or will be referred for the patient event.
278 - Health Care Services Review Notification
D | 2010EA | NM104 | - | 1036
278 - Health Care Services Review Acknowledgment
D | 2010E | NM104 | - | 1036

Patient Event Provider Identifier
Code uniquely identifying the provider to whom the patient has been or will be referred for the patient event.
278 - Health Care Services Review Notification
D | 2010EA | NM109 | - | 67
278 - Health Care Services Review Acknowledgment
D | 2010E | NM109 | - | 67

Patient Event Provider Last or Organization Name
Last name or organization name of the provider to whom the patient has been or will be referred for the patient event.
278 - Health Care Services Review Notification
D | 2010EA | NM103 | - | 1035
278 - Health Care Services Review Acknowledgment
D | 2010E | NM103 | - | 1035

Patient Event Provider Middle Name
Middle name or middle initial name of the provider to whom the patient has been or will be referred for the patient event.
278 - Health Care Services Review Notification
D | 2010EA | NM105 | - | 1037
278 - Health Care Services Review Acknowledgment
D | 2010E | NM105 | - | 1037

Patient Event Provider Name Prefix
Prefix of the name of the individual who is the patient event provider.
278 - Health Care Services Review Notification
D | 2010EA | NM106 | - | 1038
278 - Health Care Services Review Acknowledgment
D | 2010E | NM106 | - | 1038

Patient Event Provider Name Suffix
Suffix to the name of the provider to whom the patient has been or will be referred for the patient event.
278 - Health Care Services Review Notification
D | 2010EA | NM107 | - | 1039
278 - Health Care Services Review Acknowledgment
D | 2010E | NM107 | - | 1039

Patient Event Provider Postal Zone or ZIP Code
Code indicating the postal code in the mailing address of the provider to whom the patient has been or will be referred for the patient event.
278 - Health Care Services Review Notification
D | 2010EA | N403 | - | 116

Patient Event Provider State or Province Code
Code indicating the state or province in the mailing address of the provider to whom the patient has been or will be referred for the patient event.
278 - Health Care Services Review Notification
D | 2010EA | N402 | - | 156

Patient Event Provider Supplemental Identifier
Supplemental identification information about the provider to whom the patient has been or will be referred for the patient event.
278 - Health Care Services Review Notification
D | 2010EA | REF02 | - | 127
278 - Health Care Services Review Acknowledgment
D | 2010E | REF02 | - | 127

Patient Event Provider Transport Location Address Line
Street address from which the patient is being transported or the street address to which the patient is being transported.
278 - Health Care Services Review Notification
D | 2010EC | N301 | - | 166
D | 2010EC | N302 | - | 166

Patient Event Provider Transport Location Name
Name of location for which the patient is being transported.
278 - Health Care Services Review Notification
D | 2010EC | NM103 | - | 1035

Patient Event Trace Number
Unique number assigned by the provider to identify the patient event for reconciliation of the response to an internal system.
278 - Health Care Services Review Notification
D | 2000E | TRN02 | - | 127
278 - Health Care Services Review Acknowledgment
D | 2000E | TRN02 | - | 127

Patient Event Tracking Number
Unique number assigned by the provider to identify the patient event for reconciliation of the response to an internal system.
278 - Health Care Services Review Acknowledgment
D | 2000C | TRN02 | - | 127
D | 2000D | TRN02 | - | 127

Patient Event Transport Location City Name
City from which the patient is being transported or the city to which the patient is being transported.
278 - Health Care Services Review Notification
D | 2010EC | N401 | - | 19

Patient Event Transport Location Postal Zone or ZIP Code
Zip Code from which the patient is being transported or the Zip Code to which the patient is being transported.
278 - Health Care Services Review Notification
D | 2010EC | N403 | - | 116

Patient Event Transport Location State or Province Code
State Postal Code or Province Code from which the patient is being transported or the State Postal Code or Province Code to which the patient is being transported.
278 - Health Care Services Review Notification
D | 2010EC | N402 | - | 156

Patient Status Code
A code indicating the patient's status at the date of admission, outpatient service, or start of care.
278 - Health Care Services Review Notification
D | 2000E | CL103 | - | 1352

Period Count
Total number of periods.
278 - Health Care Services Review Notification
D | 2000E | HSD06 | - | 616
D | 2000F | HSD06 | - | 616

Portable Oxygen System Flow Rate
Oxygen flow rate for a portable oxygen system in liters per minute.
278 - Health Care Services Review Notification
D | 2000E | CR516 | - | 380

Previous Review Authorization Number
Unique authorization number previously assigned by the UMO to this service review.
278 - Health Care Services Review Notification
D | 2000E | REF02 | - | 127
D | 2000F | REF02 | - | 127
278 - Health Care Services Review Acknowledgment
D | 2000E | REF02 | - | 127
D | 2000F | REF02 | - | 127

Procedure Code
Code identifying the procedure, product or service.
278 - Health Care Services Review Notification
D | 2000F | SV101 | C003-02 | 234
D | 2000F | SV202 | C003-02 | 234
D | 2000F | SV301 | C003-02 | 234
278 - Health Care Services Review Acknowledgment
D | 2000F | SV101 | C003-02 | 234
D | 2000F | SV202 | C003-02 | 234
D | 2000F | SV301 | C003-02 | 234

Procedure Code Description
Description clarifying the Product/Service Procedure Code and related data elements.
278 - Health Care Services Review Notification
D | 2000F | SV101 | C003-07 | 352
D | 2000F | SV202 | C003-07 | 352
D | 2000F | SV301 | C003-07 | 352

Procedure Modifier
This identifies special circumstances related to the performance of the service.
278 - Health Care Services Review Notification
D | 2000F | SV101 | C003-03 | 1339
D | 2000F | SV101 | C003-04 | 1339
D | 2000F | SV101 | C003-05 | 1339
D | 2000F | SV101 | C003-06 | 1339
D | 2000F | SV202 | C003-03 | 1339
D | 2000F | SV202 | C003-04 | 1339
D | 2000F | SV202 | C003-05 | 1339
D | 2000F | SV202 | C003-06 | 1339
D | 2000F | SV301 | C003-03 | 1339
D | 2000F | SV301 | C003-04 | 1339
D | 2000F | SV301 | C003-05 | 1339
D | 2000F | SV301 | C003-06 | 1339
278 - Health Care Services Review Acknowledgment
D | 2000F | SV101 | C003-03 | 1339
D | 2000F | SV101 | C003-04 | 1339
D | 2000F | SV101 | C003-05 | 1339
D | 2000F | SV101 | C003-06 | 1339
D | 2000F | SV202 | C003-03 | 1339
D | 2000F | SV202 | C003-04 | 1339
D | 2000F | SV202 | C003-05 | 1339
D | 2000F | SV202 | C003-06 | 1339
D | 2000F | SV301 | C003-03 | 1339
D | 2000F | SV301 | C003-04 | 1339
D | 2000F | SV301 | C003-05 | 1339
D | 2000F | SV301 | C003-06 | 1339

Product or Service ID
Identifying number for a product or service.
278 - Health Care Services Review Notification
D | 2000F | SV101 | C003-08 | 234
D | 2000F | SV202 | C003-08 | 234
D | 2000F | SV301 | C003-08 | 234
278 - Health Care Services Review Acknowledgment
D | 2000F | SV101 | C003-08 | 234
D | 2000F | SV202 | C003-08 | 234
D | 2000F | SV301 | C003-08 | 234

Product or Service ID Qualifier
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
278 - Health Care Services Review Notification
D | 2000F | SV101 | C003-01 | 235
D | 2000F | SV202 | C003-01 | 235
D | 2000F | SV301 | C003-01 | 235
278 - Health Care Services Review Acknowledgment
D | 2000F | SV101 | C003-01 | 235
D | 2000F | SV202 | C003-01 | 235
D | 2000F | SV301 | C003-01 | 235

Prognosis Code
Code indicating physician's prognosis for the patient.
278 - Health Care Services Review Notification
D | 2000E | CR601 | - | 923

Proposed or Actual Admission Date
Requested or actual date of admission to a healthcare facility.
278 - Health Care Services Review Notification
D | 2000E | DTP03 | - | 1251
278 - Health Care Services Review Acknowledgment
D | 2000E | DTP03 | - | 1251

Proposed or Actual Discharge Date
Requested or actual date of discharge from a healthcare facility.
278 - Health Care Services Review Notification
D | 2000E | DTP03 | - | 1251
278 - Health Care Services Review Acknowledgment
D | 2000E | DTP03 | - | 1251

Proposed or Actual Event Date
Requested or actual date of the patient event.
278 - Health Care Services Review Notification
D | 2000E | DTP03 | - | 1251
278 - Health Care Services Review Acknowledgment
D | 2000E | DTP03 | - | 1251

Proposed or Actual Service Date
Requested or actual date of service.
278 - Health Care Services Review Notification
D | 2000F | DTP03 | - | 1251
278 - Health Care Services Review Acknowledgment
D | 2000F | DTP03 | - | 1251

Prosthesis, Crown, or Inlay Code
Code Specifying the Placement Status for the Dental Work.
278 - Health Care Services Review Notification
D | 2000F | SV305 | - | 1358
278 - Health Care Services Review Acknowledgment
D | 2000F | SV305 | - | 1358

Provider Code
Code identifying the type of provider.
278 - Health Care Services Review Notification
D | 2010A | PRV01 | - | 1221
D | 2010EA | PRV01 | - | 1221
D | 2010F | PRV01 | - | 1221
278 - Health Care Services Review Acknowledgment
D | 2010A | PRV01 | - | 1221
D | 2010E | PRV01 | - | 1221
D | 2010F | PRV01 | - | 1221

Provider Taxonomy Code
Code designating the provider type, classification, and specialization.
278 - Health Care Services Review Notification
D | 2010A | PRV03 | - | 127
D | 2010EA | PRV03 | - | 127
D | 2010F | PRV03 | - | 127
278 - Health Care Services Review Acknowledgment
D | 2010A | PRV03 | - | 127
D | 2010E | PRV03 | - | 127
D | 2010F | PRV03 | - | 127

Quantity Qualifier
Code specifying the type of quantity.
278 - Health Care Services Review Notification
D | 2000E | HSD01 | - | 673
D | 2000F | HSD01 | - | 673

Reference Identification
The identification value assigned by the sender for this particular transaction.
278 - Health Care Services Review Notification
D | 2010ED | REF04 | C040-06 | 127

Reference Identification Qualifier
Code qualifying the reference identification.
278 - Health Care Services Review Notification
D | 2010A | REF01 | - | 128
D | 2010A | PRV02 | - | 128
D | 2010C | REF01 | - | 128
D | 2010D | REF01 | - | 128
D | 2000E | REF01 | - | 128
D | 2000E | REF01 | - | 128
D | 2010EA | REF01 | - | 128
D | 2010EA | PRV02 | - | 128
D | 2010ED | REF01 | - | 128
D | 2010ED | REF04 | C040-01 | 128
D | 2010ED | REF04 | C040-03 | 128
D | 2010ED | REF04 | C040-05 | 128
D | 2000F | REF01 | - | 128
D | 2000F | REF01 | - | 128
D | 2010F | REF01 | - | 128
D | 2010F | PRV02 | - | 128
278 - Health Care Services Review Acknowledgment
D | 2010A | REF01 | - | 128
D | 2010A | PRV02 | - | 128
D | 2000C | REF01 | - | 128
D | 2010C | REF01 | - | 128
D | 2000D | REF01 | - | 128
D | 2010D | REF01 | - | 128
D | 2000E | REF01 | - | 128
D | 2000E | REF01 | - | 128
D | 2010E | REF01 | - | 128
D | 2010E | PRV02 | - | 128
D | 2000F | REF01 | - | 128
D | 2000F | REF01 | - | 128
D | 2010F | REF01 | - | 128
D | 2010F | PRV02 | - | 128

Reject Reason Code
Code assigned by issuer to identify reason for rejection.
278 - Health Care Services Review Notification
D | 2000E | AAA03 | - | 901
D | 2010EA | AAA03 | - | 901
D | 2010EC | AAA03 | - | 901
D | 2000F | AAA03 | - | 901
D | 2010F | AAA03 | - | 901
278 - Health Care Services Review Acknowledgment
D | 2000A | AAA03 | - | 901
D | 2010A | AAA03 | - | 901
D | 2010B | AAA03 | - | 901
D | 2000C | AAA03 | - | 901
D | 2010C | AAA03 | - | 901
D | 2000D | AAA03 | - | 901
D | 2010D | AAA03 | - | 901
D | 2000E | AAA03 | - | 901
D | 2010E | AAA03 | - | 901
D | 2000F | AAA03 | - | 901
D | 2010F | AAA03 | - | 901

Report Transmission Code
Code defining timing, transmission method or format by which reports are to be sent.
278 - Health Care Services Review Notification
D | 2000E | PWK02 | - | 756
D | 2000F | PWK02 | - | 756

Request Category Code
Code indicating a type of request.
278 - Health Care Services Review Notification
D | 2000E | UM01 | - | 1525
D | 2000F | UM01 | - | 1525
278 - Health Care Services Review Acknowledgment
D | 2000E | UM01 | - | 1525
D | 2000F | UM01 | - | 1525

Respiratory Therapist Order Text
Free-form description of the respiratory therapist's orders.
278 - Health Care Services Review Notification
D | 2000E | CR509 | - | 352

Response Contact Address Line
The address line of the person or organization designated to receive the requested information.
278 - Health Care Services Review Notification
D | 2010EB | N301 | - | 166
D | 2010EB | N302 | - | 166

Response Contact Communication Number
Complete contact communications number, including country or area code when applicable, for the entity that is the designated recipient of requested additional information.
278 - Health Care Services Review Notification
D | 2010EB | PER04 | - | 364
D | 2010EB | PER06 | - | 364
D | 2010EB | PER08 | - | 364

Response Contact First Name
First name of the individual that is the designated recipient of requested additional information.
278 - Health Care Services Review Notification
D | 2010EB | NM104 | - | 1036

Response Contact Identifier
Code uniquely identifying the entity that is the designated recipient of requested additional information.
278 - Health Care Services Review Notification
D | 2010EB | NM109 | - | 67

Response Contact Last or Organization Name
Last name or organization name of the entity that is the designated recipient of requested additional information.
278 - Health Care Services Review Notification
D | 2010EB | NM103 | - | 1035

Response Contact Middle Name
Middle name or middle initial of the individual that is the designated recipient of requested additional information.
278 - Health Care Services Review Notification
D | 2010EB | NM105 | - | 1037

Response Contact Name
The name of the person or organization designated to receive the requested information.
278 - Health Care Services Review Notification
D | 2010EB | PER02 | - | 93

Response Contact Name Suffix
Suffix to the name of the individual that is the designated recipient of requested additional information.
278 - Health Care Services Review Notification
D | 2010EB | NM107 | - | 1039

Review Decision Reason Code
Code identifying the reason for this review outcome.
278 - Health Care Services Review Notification
D | 2000E | HCR03 | - | 1271
D | 2000F | HCR03 | - | 1271
278 - Health Care Services Review Acknowledgment
D | 2000E | HCR03 | - | 1271
D | 2000F | HCR03 | - | 1271

Review Identification Number
Authorization number assigned by the UMO to the service review.
278 - Health Care Services Review Notification
D | 2000E | HCR02 | - | 127
D | 2000F | HCR02 | - | 127
278 - Health Care Services Review Acknowledgment
D | 2000E | HCR02 | - | 127
D | 2000F | HCR02 | - | 127

Sample Selection Modulus
To specify the sampling frequency in terms of a modulus of the Unit of Measure, e.g., every fifth bag, every 1.5 minutes.
278 - Health Care Services Review Notification
D | 2000E | HSD04 | - | 1167
D | 2000F | HSD04 | - | 1167

Second Surgical Opinion Indicator
Code indicating whether or not a second surgical opinion is required for this health care services review request.
278 - Health Care Services Review Notification
D | 2000E | HCR04 | - | 1073
D | 2000F | HCR04 | - | 1073
278 - Health Care Services Review Acknowledgment
D | 2000E | HCR04 | - | 1073

Service Line Amount
Charges related to this service.
278 - Health Care Services Review Notification
D | 2000F | SV102 | - | 782
D | 2000F | SV203 | - | 782
D | 2000F | SV302 | - | 782
278 - Health Care Services Review Acknowledgment
D | 2000F | SV102 | - | 782
D | 2000F | SV203 | - | 782
D | 2000F | SV302 | - | 782

Service Line Rate
Payment rate that applies to the service line.
278 - Health Care Services Review Notification
D | 2000F | SV206 | - | 1371
278 - Health Care Services Review Acknowledgment
D | 2000F | SV206 | - | 1371

Service Line Revenue Code
UB92 Revenue Code pertaining to the service line.
278 - Health Care Services Review Notification
D | 2000F | SV201 | - | 234
278 - Health Care Services Review Acknowledgment
D | 2000F | SV201 | - | 234

Service Provider Address Line
Address line in the mailing address of the provider to whom the patient has been or will be referred for service.
278 - Health Care Services Review Notification
D | 2010F | N301 | - | 166
D | 2010F | N302 | - | 166

Service Provider City Name
Name of the city in the mailing address of the provider to whom the patient has been or will be referred for service.
278 - Health Care Services Review Notification
D | 2010F | N401 | - | 19

Service Provider Contact Communication Number
Complete service provider contact communications number, including country or area code when applicable.
278 - Health Care Services Review Notification
D | 2010F | PER04 | - | 364
D | 2010F | PER06 | - | 364
D | 2010F | PER08 | - | 364

Service Provider Contact Name
Name of person, group, or organization to contact at the entity providing service or at the entity that may provide service.
278 - Health Care Services Review Notification
D | 2010F | PER02 | - | 93

Service Provider First Name
First name of the provider to whom the patient has been or will be referred for service or the provider that performed the service.
278 - Health Care Services Review Notification
D | 2010F | NM104 | - | 1036
278 - Health Care Services Review Acknowledgment
D | 2010F | NM104 | - | 1036

Service Provider Identifier
Code uniquely identifying the provider to whom the patient has been or will be referred for service or the provider that performed the service or where the service was performed.
278 - Health Care Services Review Notification
D | 2010F | NM109 | - | 67
278 - Health Care Services Review Acknowledgment
D | 2010F | NM109 | - | 67

Service Provider Last or Organization Name
Last name or organization name of the provider to whom the patient has been or will be referred for service or the provider that performed the service or where the service was performed.
278 - Health Care Services Review Notification
D | 2010F | NM103 | - | 1035
278 - Health Care Services Review Acknowledgment
D | 2010F | NM103 | - | 1035

Service Provider Middle Name or Initial
Middle name or middle initial of the provider to whom the patient has been or will be referred for service or the provider that performed the service.
278 - Health Care Services Review Notification
D | 2010F | NM105 | - | 1037
278 - Health Care Services Review Acknowledgment
D | 2010F | NM105 | - | 1037

Service Provider Name Prefix
Prefix to the name of the provider to whom the patient has been or will be referred for service.
278 - Health Care Services Review Notification
D | 2010F | NM106 | - | 1038
278 - Health Care Services Review Acknowledgment
D | 2010F | NM106 | - | 1038

Service Provider Name Suffix
Suffix to the name of the provider to whom the patient has been or will be referred for service or the provider that performed the service.
278 - Health Care Services Review Notification
D | 2010F | NM107 | - | 1039
278 - Health Care Services Review Acknowledgment
D | 2010F | NM107 | - | 1039

Service Provider Postal Zone or ZIP Code
Code indicating the postal code in the mailing address of the provider to whom the patient has been or will be referred for service.
278 - Health Care Services Review Notification
D | 2010F | N403 | - | 116

Service Provider State or Province Code
Code indicating the state or province in the mailing address of the provider to whom the patient has been or will be referred for service.
278 - Health Care Services Review Notification
D | 2010F | N402 | - | 156

Service Provider Supplemental Identifier
Supplemental identification information about the provider to whom the patient has been or will be referred for service.
278 - Health Care Services Review Notification
D | 2010F | REF02 | - | 127
278 - Health Care Services Review Acknowledgment
D | 2010F | REF02 | - | 127

Service Trace Number
Unique number assigned by the provider to identify a request for reconciliation of the response to an internal system.
278 - Health Care Services Review Notification
D | 2000F | TRN02 | - | 127
278 - Health Care Services Review Acknowledgment
D | 2000F | TRN02 | - | 127

Service Type Code
Code identifying the classification of service.
278 - Health Care Services Review Notification
D | 2000E | UM03 | - | 1365
D | 2000F | UM03 | - | 1365
278 - Health Care Services Review Acknowledgment
D | 2000E | UM03 | - | 1365
D | 2000F | UM03 | - | 1365

Service Unit Count
The quantity of units, times, days, visits, services, or treatments for the service described by the HCPCS codes, revenue code or procedure code.
278 - Health Care Services Review Notification
D | 2000E | HSD02 | - | 380
D | 2000F | SV104 | - | 380
D | 2000F | SV205 | - | 380
D | 2000F | SV306 | - | 380
D | 2000F | HSD02 | - | 380
278 - Health Care Services Review Acknowledgment
D | 2000F | SV104 | - | 380
D | 2000F | SV205 | - | 380
D | 2000F | SV306 | - | 380

Subluxation Level Code
Code identifying the specific level of subluxation.
278 - Health Care Services Review Notification
D | 2000E | CR203 | - | 1367
D | 2000E | CR204 | - | 1367

Submitter Transaction Identifier
Trace or control number assigned by the originator of the transaction.
278 - Health Care Services Review Notification
H | | BHT03 | - | 127
278 - Health Care Services Review Acknowledgment
H | | BHT03 | - | 127

Subscriber Address Line
Address line of the current mailing address of the insured individual or subscriber to the coverage.
278 - Health Care Services Review Notification
D | 2010C | N301 | - | 166
D | 2010C | N302 | - | 166

Subscriber Birth Date
The date of birth of the subscriber to the indicated coverage or policy.
278 - Health Care Services Review Notification
D | 2010C | DMG02 | - | 1251
278 - Health Care Services Review Acknowledgment
D | 2010C | DMG02 | - | 1251

Subscriber City Name
The City Name of the insured individual or subscriber to the coverage.
278 - Health Care Services Review Notification
D | 2010C | N401 | - | 19

Subscriber First Name
The first name of the insured individual or subscriber to the coverage.
278 - Health Care Services Review Notification
D | 2010C | NM104 | - | 1036
278 - Health Care Services Review Acknowledgment
D | 2010C | NM104 | - | 1036

Subscriber Gender Code
Code indicating the sex of the subscriber to the indicated coverage or policy.
278 - Health Care Services Review Notification
D | 2010C | DMG03 | - | 1068
278 - Health Care Services Review Acknowledgment
D | 2010C | DMG03 | - | 1068

Subscriber Last Name
The surname of the insured individual or subscriber to the coverage.
278 - Health Care Services Review Notification
D | 2010C | NM103 | - | 1035
278 - Health Care Services Review Acknowledgment
D | 2010C | NM103 | - | 1035

Subscriber Middle Name or Initial
The middle name or initial of the subscriber to the indicated coverage or policy.
278 - Health Care Services Review Notification
D | 2010C | NM105 | - | 1037
278 - Health Care Services Review Acknowledgment
D | 2010C | NM105 | - | 1037

Subscriber Name Suffix
Suffix of the insured individual or subscriber to the coverage.
278 - Health Care Services Review Notification
D | 2010C | NM107 | - | 1039
278 - Health Care Services Review Acknowledgment
D | 2010C | NM107 | - | 1039

Subscriber Postal Zone or ZIP Code
The ZIP Code of the insured individual or subscriber to the coverage.
278 - Health Care Services Review Notification
D | 2010C | N403 | - | 116

Subscriber Primary Identifier
Primary identification number of the subscriber to the coverage.
278 - Health Care Services Review Notification
D | 2010C | NM109 | - | 67
278 - Health Care Services Review Acknowledgment
D | 2010C | NM109 | - | 67

Subscriber State Code
The State Postal Code of the insured individual or subscriber to the coverage.
278 - Health Care Services Review Notification
D | 2010C | N402 | - | 156

Subscriber Supplemental Identifier
Identifies another or additional distinguishing code number associated with the subscriber.
278 - Health Care Services Review Notification
D | 2010C | REF02 | - | 127
278 - Health Care Services Review Acknowledgment
D | 2010C | REF02 | - | 127

Time Period Qualifier
Code defining the type of time period.
278 - Health Care Services Review Notification
D | 2000E | HSD05 | - | 615
D | 2000F | HSD05 | - | 615

Tooth Code
An indication of the tooth on which services were performed or will be performed.
278 - Health Care Services Review Notification
D | 2000F | TOO02 | - | 1271
278 - Health Care Services Review Acknowledgment
D | 2000F | TOO02 | - | 1271

Tooth Surface Code
The surface(s) of the tooth on which services were performed or will be performed.
278 - Health Care Services Review Notification
D | 2000F | TOO03 | C005-01 | 1369
D | 2000F | TOO03 | C005-02 | 1369
D | 2000F | TOO03 | C005-03 | 1369
D | 2000F | TOO03 | C005-04 | 1369
D | 2000F | TOO03 | C005-05 | 1369
278 - Health Care Services Review Acknowledgment
D | 2000F | TOO03 | C005-01 | 1369
D | 2000F | TOO03 | C005-02 | 1369
D | 2000F | TOO03 | C005-03 | 1369
D | 2000F | TOO03 | C005-04 | 1369
D | 2000F | TOO03 | C005-05 | 1369

Trace Assigning Entity Additional Identifier
Additional identifier for the entity assigning the trace number.
278 - Health Care Services Review Notification
D | 2000E | TRN04 | - | 127
D | 2000F | TRN04 | - | 127
278 - Health Care Services Review Acknowledgment
D | 2000C | TRN04 | - | 127
D | 2000D | TRN04 | - | 127
D | 2000E | TRN04 | - | 127
D | 2000F | TRN04 | - | 127

Trace Assigning Entity Identifier
Identifies the organization assigning the trace number.
278 - Health Care Services Review Notification
D | 2000E | TRN03 | - | 509
D | 2000F | TRN03 | - | 509
278 - Health Care Services Review Acknowledgment
D | 2000C | TRN03 | - | 509
D | 2000D | TRN03 | - | 509
D | 2000E | TRN03 | - | 509
D | 2000F | TRN03 | - | 509

Trace Type Code
Code identifying the type of re-association which needs to be performed.
278 - Health Care Services Review Notification
D | 2000E | TRN01 | - | 481
D | 2000F | TRN01 | - | 481
278 - Health Care Services Review Acknowledgment
D | 2000C | TRN01 | - | 481
D | 2000D | TRN01 | - | 481
D | 2000E | TRN01 | - | 481
D | 2000F | TRN01 | - | 481

Transaction Segment Count
A tally of all segments between the ST and the SE segments including the ST and SE segments.
278 - Health Care Services Review Notification
D | | SE01 | - | 96
278 - Health Care Services Review Acknowledgment
D | | SE01 | - | 96

Transaction Set Control Number
The unique identification number within a transaction set.
278 - Health Care Services Review Notification
H | | ST02 | - | 329
D | | SE02 | - | 329
278 - Health Care Services Review Acknowledgment
H | | ST02 | - | 329
D | | SE02 | - | 329

Transaction Set Creation Date
Identifies the date the submitter created the transaction.
278 - Health Care Services Review Notification
H | | BHT04 | - | 373
278 - Health Care Services Review Acknowledgment
H | | BHT04 | - | 373

Transaction Set Creation Time
Time file is created for transmission.
278 - Health Care Services Review Notification
H | | BHT05 | - | 337
278 - Health Care Services Review Acknowledgment
H | | BHT05 | - | 337

Transaction Set Identifier Code
Code uniquely identifying a Transaction Set.
278 - Health Care Services Review Notification
H | | ST01 | - | 143
278 - Health Care Services Review Acknowledgment
H | | ST01 | - | 143

Transaction Set Purpose Code
Code identifying purpose of transaction set.
278 - Health Care Services Review Notification
H | | BHT02 | - | 353
278 - Health Care Services Review Acknowledgment
H | | BHT02 | - | 353

Transaction Type Code
Code specifying the type of transaction.
278 - Health Care Services Review Notification
H | | BHT06 | - | 640

Transport Distance
Distance traveled during the ambulance transport.
278 - Health Care Services Review Notification
D | 2000E | CR106 | - | 380

Treatment Count
Total number of treatments in the series.
278 - Health Care Services Review Notification
D | 2000E | CR202 | - | 380

Treatment Series Number
Number this treatment is in the series of services.
278 - Health Care Services Review Notification
D | 2000E | CR201 | - | 609

Unit or Basis for Measurement Code
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken.
278 - Health Care Services Review Notification
D | 2000E | HSD03 | - | 355
D | 2000E | CR105 | - | 355
D | 2000F | SV103 | - | 355
D | 2000F | SV204 | - | 355
D | 2000F | HSD03 | - | 355
278 - Health Care Services Review Acknowledgment
D | 2000F | SV103 | - | 355
D | 2000F | SV204 | - | 355

Valid Request Indicator
Code indicating if the information request or portion of the request is valid or invalid.
278 - Health Care Services Review Notification
D | 2000E | AAA01 | - | 1073
D | 2010EA | AAA01 | - | 1073
D | 2010EC | AAA01 | - | 1073
D | 2000F | AAA01 | - | 1073
D | 2010F | AAA01 | - | 1073
278 - Health Care Services Review Acknowledgment
D | 2000A | AAA01 | - | 1073
D | 2010A | AAA01 | - | 1073
D | 2010B | AAA01 | - | 1073
D | 2000C | AAA01 | - | 1073
D | 2010C | AAA01 | - | 1073
D | 2000D | AAA01 | - | 1073
D | 2010D | AAA01 | - | 1073
D | 2000E | AAA01 | - | 1073
D | 2010E | AAA01 | - | 1073
D | 2000F | AAA01 | - | 1073
D | 2010F | AAA01 | - | 1073

Yes No Condition or Response Code
Code indicating a Yes or No condition or response.
278 - Health Care Services Review Acknowledgment
D | 2000F | HCR04 | - | 1073