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)
27
Carrier Identification Number as assigned by Health Care Financing Administration (HCFA)
28
Fiscal Intermediary Identification Number as assigned by Health Care Financing Administration (HCFA)
29
Medicare Provider and Supplier Identification Number as assigned by Health Care Financing Administration (HCFA)
30
U.S. Federal Tax Identification Number
33
National Association of Insurance Commissioners Company Code (NAIC)
ZZ
Mutually Defined
Required
6
I06
Interchange Sender ID
M 1
AN
15
Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Required
7
I05
Interchange ID Qualifier
M 1
ID
2
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
This ID qualifies the Receiver in ISA08.
CODE
DEFINITION
01
Duns (Dun & Bradstreet)
14
Duns Plus Suffix
20
Health Industry Number (HIN)
27
Carrier Identification Number as assigned by Health Care Financing Administration (HCFA)
28
Fiscal Intermediary Identification Number as assigned by Health Care Financing Administration (HCFA)
29
Medicare Provider and Supplier Identification Number as assigned by Health Care Financing Administration (HCFA)
30
U.S. Federal Tax Identification Number
33
National Association of Insurance Commissioners Company Code (NAIC)
ZZ
Mutually Defined
Required
8
I07
Interchange Receiver ID
M 1
AN
15
Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them
Required
9
I08
Interchange Date
M 1
DT
6
Date of the interchange
The date format is YYMMDD.
Required
10
I09
Interchange Time
M 1
TM
4
Time of the interchange
The time format is HHMM.
Required
11
I65
Repetition Separator
M 1
Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator
Required
12
I11
Interchange Control Version Number
M 1
ID
5
Code specifying the version number of the interchange control segments
CODE
DEFINITION
00501
Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
Required
13
I12
Interchange Control Number
M 1
N
9
A control number assigned by the interchange sender
  1. The Interchange Control Number, ISA13, must be identical to the associated Interchange Trailer IEA02.
  2. Must be a positive unsigned number and must be identical to the value in IEA02.
Required
14
I13
Acknowledgment Requested
M 1
ID
1
Code indicating sender's request for an interchange acknowledgment
See Section B.1.1.5.1 for interchange acknowledgment information.
CODE
DEFINITION
0
No Interchange Acknowledgment Requested
1
Interchange Acknowledgment Requested (TA1)
Required
15
I14
Interchange Usage Indicator
M 1
ID
1
Code indicating whether data enclosed by this interchange envelope is test, production or information
CODE
DEFINITION
P
Production Data
T
Test Data
Required
16
I15
Component Element Separator
M 1
Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

GS*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✱005010X000~
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
005010X217
Health Care Services Review - Request for Review and Response

ST*278 - TRANSACTION SET HEADER

X12 Name:
Transaction Set Header
X12 Purpose:
To indicate the start of a transaction set and to assign a control number
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
Use this segment to indicate the start of a health care services review request transaction set with all of the supporting detail information. This transaction set is the electronic equivalent of a phone, fax, or paper-based utilization management request.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile because the values are hardcoded or derived.
Implement with version: STU 1.0.0
TR3 Example:
ST✱278✱0001✱005010X217~
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).
FHIR Mapping: '278'
Implement with version: STU 1.0.0
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
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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.
FHIR Mapping: '005010X217'
Implement with version: STU 1.0.0
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
005010X217
Health Care Services Review - Request for Review and Response

BHT*0007 - BEGINNING OF HIERARCHICAL TRANSACTION

X12 Name:
Beginning of Hierarchical Transaction
X12 Purpose:
To define the business hierarchical structure of the transaction set and identify the business application purpose and reference data, i.e., number, date, and time
Segment Usage:
Required
Segment Repeat:
1
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
BHT✱0007✱13✱200300114000001✱20030101✱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
FHIR Mapping: '0007'
Implement with version: STU 1.0.0
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
FHIR Mapping: '13'
Implement with version: STU 1.0.0
CODE
DEFINITION
01
Cancellation
Use this code to cancel a previously submitted 278 transaction. Only 278 transactions that used a BHT06 code of "RU" can be canceled. The cancellation 278 transaction must contain the same BHT06 code as the previously submitted 278 transaction.
13
Request
36
Authority to Deduct (Reply)
Use this code for medical services reservations to reserve or deduct a service with the health plan. BHT06 must be equal to "RU".
Required
3
127
Reference Identification
O 1
AN
1/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.
FHIR Mapping: Bundle.identifier.value
Implement with version: STU 1.0.0
INDUSTRY NAME: Submitter Transaction Identifier
Use this element to trace the transaction from one point to the next point, such as when the transaction is passed from one clearinghouse to another clearinghouse. This identifier must be returned in the corresponding 278 response transaction's BHT03. This identifier will only be returned by the last entity to handle the 278. This identifier will not be passed through the complete life of the transaction. All recipients of 278 request transactions are required to return the Submitter Transaction Identifier in their 278 response if one is submitted.
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.
FHIR Mapping: Bundle.timestamp
Extract the date portion of the Bundle.timestamp to populate BHT04
Implement with version: STU 1.0.0
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.
FHIR Mapping: Bundle.timestamp
Extract the time portion of the Bundle.timestamp to populate BHT05
Implement with version: STU 1.0.0
INDUSTRY NAME: Transaction Set Creation Time
Situational
6
640
Transaction Type Code
O 1
ID
2
Code specifying the type of transaction
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when requesting Medical Services Reservation. If not required by this implementation guide, do not send.
CODE
DEFINITION
RU
Medical Services Reservation

HL - UTILIZATION MANAGEMENT ORGANIZATION (UMO) LEVEL

X12 Name:
Hierarchical Level
X12 Purpose:
To identify dependencies among and the content of hierarchically related groups of data segments
X12 Comments:
  1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
  2. The HL segment defines a top-down/left-right ordered structure.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
This segment indicates the information source hierarchical level. For a request transaction, this segment corresponds to the identification of the payer, HMO, or other utilization management organization who will be the source of the decision/response.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile because the values are hardcoded or derived.
Implement with version: STU 1.0.0
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.
FHIR Mapping: '1'
Implement with version: STU 1.0.0
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.
FHIR Mapping: '20'
Implement with version: STU 1.0.0
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.
FHIR Mapping: '1'
Implement with version: STU 1.0.0
CODE
DEFINITION
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.

NM1 - UTILIZATION MANAGEMENT ORGANIZATION (UMO) NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
This segment identifies the source of information. In the case of a request transaction, the source of information would normally be the payer or utilization review organization making the decision on the request.
FHIR Mapping:
Claim.insurer => Organization
The Claim.insurer will point to a Organization in the Bundle. Locate the Organization pointed at in the Claim and use that Organization for all of the fields in the 2010A Loop
Implement with version: STU 1.0.0
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
FHIR Mapping: Organization.type[0].coding[0].code
Implement with version: STU 1.0.0
CODE
DEFINITION
2B
Third-Party Administrator
36
Employer
PR
Payer
Use only when the organization receiving the request is a health plan but is not the entity rendering the medical decision, as in plan to plan communication or communication from the health plan to the medical review organization.
X3
Utilization Management Organization
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
FHIR Mapping: '2'
Implement with version: STU 1.0.0
CODE
DEFINITION
1
Person
Use this code only if the reviewing entity is an individual, such as an individual primary care physician.
2
Non-Person Entity
Situational
3
1035
Name Last or Organization Name
O 1
AN
1/60
Individual last name or organizational name
FHIR Mapping: Organization.name
Implement with version: STU 1.0.0
SEGMENT SYNTAX: C1203
SITUATIONAL RULE: Required when name information is needed to identify the UMO. If not required by this implementation guide, do not send.
INDUSTRY NAME: Utilization Management Organization (UMO) Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when NM103 is valued and the reviewing entity is an individual (NM102 = 1), such as a primary care provider. If not required by this implementation guide, do not send.
INDUSTRY NAME: Utilization Management Organization (UMO) First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when NM104 is present and the middle name/initial of the person is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Utilization Management Organization (UMO) Middle Name or Initial
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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: Utilization Management Organization (UMO) 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)
FHIR Mapping: Organization.identifier[0].type.coding[0].code
The value from the system attribute is translated as follows:
'46' -> '46'
'U' -> 'PI'
Implement with version: STU 1.1.0
SEGMENT SYNTAX: P0809
CODE
DEFINITION
24
Employer's Identification Number
34
Social Security Number
46
Electronic Transmitter Identification Number (ETIN)
PI
Payor Identification
Use when UMO is a payer and XV is not used.
XV
Centers for Medicare and Medicaid Services PlanID
Use when reporting Health Plan ID (HPID) or Other Entity Identifier (OEID).
CODE SOURCE: 540: Centers for Medicare and Medicaid Services PlanID
Required
9
67
Identification Code
O 1
AN
2/80
Code identifying a party or other code
FHIR Mapping: Organization.identifier[0].value
Implement with version: STU 1.0.0
SEGMENT SYNTAX: P0809
INDUSTRY NAME: Utilization Management Organization (UMO) 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 - REQUESTER LEVEL

X12 Name:
Hierarchical Level
X12 Purpose:
To identify dependencies among and the content of hierarchically related groups of data segments
X12 Comments:
  1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
  2. The HL segment defines a top-down/left-right ordered structure.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
This segment indicates the health care services review information receiver. For request transactions, this segment corresponds to the identification of the entity initiating the request for review.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile because the values are hardcoded or derived.
Implement with version: STU 1.0.0
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.
FHIR Mapping: '2'
Implement with version: STU 1.0.0
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.
FHIR Mapping: '1'
Implement with version: STU 1.0.0
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.
FHIR Mapping: '21'
Implement with version: STU 1.0.0
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.
FHIR Mapping: '1'
Implement with version: STU 1.0.0
CODE
DEFINITION
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.

NM1 - REQUESTER NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
This segment identifies the receiver of information. In the case of a request transaction, the receiver would normally be the entity who will ultimately be receiving the decision.
FHIR Mapping:
Claim.provider => Organization
The Claim.provider will point to a Organization in the Bundle. Locate the Organization pointed at in the Claim and use that Organization for all of the fields in the 2010B Loop.
Implement with version: STU 1.0.0
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
FHIR Mapping: Organization.type[0].coding[0].code
Implement with version: STU 1.0.0
CODE
DEFINITION
1P
Provider
Use when the requester is an individual provider.
2B
Third-Party Administrator
36
Employer
FA
Facility
Use when the requester is a facility, such as a clinic or hospital.
PR
Payer
Use only when the organization sending the request is a health plan, as in plan to plan communication or communication from the health plan to the medical review organization.
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
FHIR Mapping: '2'
Implement with version: STU 1.0.0
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
FHIR Mapping: Organization.name
Implement with version: STU 1.0.0
SEGMENT SYNTAX: C1203
SITUATIONAL RULE: Required when name information is needed by the UMO to identify the requester. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
INDUSTRY NAME: Requester Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when NM103 is present and NM102=1. If not required by this implementation guide, do not send.
INDUSTRY NAME: Requester First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when NM104 is present and the middle name/initial of the person is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Requester Middle Name or Initial
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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: Requester 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)
FHIR Mapping: 'XX'
Implement with version: STU 1.0.0
SEGMENT SYNTAX: P0809
CODE
DEFINITION
24
Employer's Identification Number
34
Social Security Number
46
Electronic Transmitter Identification Number (ETIN)
XV
Centers for Medicare and Medicaid Services PlanID
Use when reporting Health Plan ID (HPID) or Other Entity Identifier (OEID).
CODE SOURCE: 540: Centers for Medicare and Medicaid Services PlanID
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
FHIR Mapping: Organization.identifier[0].value
Implement with version: STU 1.0.0
SEGMENT SYNTAX: P0809
INDUSTRY NAME: Requester 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 - REQUESTER SUPPLEMENTAL IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
8
Situational Rule:
Required 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.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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
Required when needed to identify the physician, clinic, or group practice associated with the requester identified in this NM1 loop. If not required, do not send.
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
Required when necessary to provide the requester/provider ID as assigned by the UMO identified in Loop 2000A. If not required, do not send.
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: Requester Supplemental Identifier
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

N3 - REQUESTER ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when necessary to identify the requester by location. If not required by this implementation guide, do not send.
TR3 Notes:
Use to identify a specific location when the requester has multiple locations and authority varies based on location.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
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
FHIR Mapping: Organization.address[0].line[0]
Implement with version: STU 1.0.0
INDUSTRY NAME: Requester Address Line
Use this element for the first line of the requester's address.
Situational
2
166
Address Information
O 1
AN
1/55
Address information
FHIR Mapping: Organization.address[0].line[1]
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when a second address line exists. If not required by this implementation guide, do not send.
INDUSTRY NAME: Requester Address Line

N4 - REQUESTER CITY, STATE, ZIP CODE

X12 Name:
Geographic Location
X12 Purpose:
To specify the geographic place of the named party
X12 Syntax:
  1. E0207
    Only one of N402 or N407 may be present.
  2. C0605
    If N406 is present, then N405 is required.
  3. C0704
    If N407 is present, then N404 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when necessary to identify the requester by location. If not required by this implementation guide, do not send.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
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.
FHIR Mapping: Organization.address[0].city
Implement with version: STU 1.0.0
INDUSTRY NAME: Requester 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.
FHIR Mapping: Organization.address[0].state
Implement with version: STU 1.0.0
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: Requester State or Province Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
O 1
ID
3/15
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
FHIR Mapping: Organization.address[0].postalCode
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada, or when a postal code exists for the country in N404. If not required by this implementation guide, do not send.
INDUSTRY NAME: Requester Postal Zone or ZIP Code
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
O 1
ID
2/3
Code identifying the country
FHIR Mapping: Organization.address[0].country
Implement with version: STU 1.0.0
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
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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 - REQUESTER CONTACT INFORMATION

X12 Name:
Administrative Communications Contact
X12 Purpose:
To identify a person or office to whom administrative communications should be directed
X12 Syntax:
  1. P0304
    If either PER03 or PER04 is present, then the other is required.
  2. P0506
    If either PER05 or PER06 is present, then the other is required.
  3. P0708
    If either PER07 or PER08 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the UMO must direct requests for additional information to a specific requester contact, electronic mail, facsimile, or telephone number. If not required by this implementation guide, do not send.
TR3 Notes:
When the communication number represents a telephone number in the United States and other countries using the North American Dialing Plan (for voice, data, fax, etc.), the communication number 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.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
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
FHIR Mapping: 'IC'
Implement with version: STU 1.0.0
CODE
DEFINITION
IC
Information Contact
Situational
2
93
Name
O 1
AN
1/60
Free-form name
FHIR Mapping: Organization.contact[0].name
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the response must be directed to a particular contact and the name of the entity to contact is not already defined or is different than the name supplied in the NM1 segment of this loop. If not required by this implementation guide, do not send.
INDUSTRY NAME: Requester Contact Name
Situational
3
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
FHIR Mapping: Organization.contact[0].telecom[0].system
The value from the system attribute is translated as follows:
'phone' -> 'TE'
'fax' -> 'FX'
'email' -> 'EM'
'pager' -> 'TE'
'url' -> 'UR'
'sms' -> 'TE'
'other' -> cannot be translated
Implement with version: STU 1.0.0
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
FHIR Mapping: Organization.contact[0].telecom[0].value
If the value of system is 'phone', this value must be parsed to determine if an extension is present (see ITU-T E.123 for format of telephone values). If an extension is present, the remove the extension part of the phone number and place in PER06 and set PER05 to 'EX'
Implement with version: STU 1.0.0
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: Requester Contact Communication Number
Situational
5
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
FHIR Mapping: Organization.contact[0].telecom[1].system | 'EX'
See PER04 if PER03 is 'TE' otherwise select the next telecom in contact[0] and translate the system as follows:
'phone' -> 'TE'
'fax' -> 'FX'
'email' -> 'EM'
'pager' -> 'TE'
'url' -> 'UR'
'sms' -> 'TE'
'other' -> cannot be translated
Implement with version: STU 1.0.0
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
FHIR Mapping: Organization.contact[0].telecom[1].value | extracted extension
If PER05 is set to 'EX' this will be the extract value for the extension from PER04
Otherwise this is refer to PER04 for rules on formatting
Implement with version: STU 1.0.0
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: Requester Contact Communication Number
Situational
7
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
FHIR Mapping: Organization.contact[0].telecom[n].system | 'EX'
See PER06 if PER05 is 'TE' otherwise select the next telecom in contact[0] and translate the system as follows:
'phone' -> 'TE'
'fax' -> 'FX'
'email' -> 'EM'
'pager' -> 'TE'
'url' -> 'UR'
'sms' -> 'TE'
'other' -> cannot be translated
Implement with version: STU 1.0.0
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
FHIR Mapping: Organization.contact[0].telecom[n].value | extracted extension
If PER07 is set to 'EX' this will be the extract value for the extension from PER06
Otherwise this is refer to PER04 for rules on formatting
Implement with version: STU 1.0.0
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: Requester Contact Communication Number
Not Used
9
443
Contact Inquiry Reference
O 1
AN
1/20

PRV - REQUESTER PROVIDER INFORMATION

X12 Name:
Provider Information
X12 Purpose:
To specify the identifying characteristics of a provider
X12 Syntax:
P0203
If either PRV02 or PRV03 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when needed to indicate the requester's role in the care of the patient and the requesting provider's specialty. If not required by this implementation guide, do not send.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
TR3 Example:
PRV✱CO✱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
Situational
2
128
Reference Identification Qualifier
O 1
ID
2/3
Code qualifying the Reference Identification
SEGMENT SYNTAX: P0203
SITUATIONAL RULE: Required when necessary to identify the requesting provider's specialty. If not required by this implementation guide, do not send.
CODE
DEFINITION
PXC
Health Care Provider Taxonomy Code
CODE SOURCE: 682: Health Care Provider Taxonomy
Situational
3
127
Reference Identification
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
SITUATIONAL RULE: Required when necessary to identify the requesting provider's specialty. If not required by this implementation guide, do not send.
INDUSTRY NAME: Provider Taxonomy Code
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 - 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.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile because the values are hardcoded or derived.
Implement with version: STU 1.0.0
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.
FHIR Mapping: '3'
Implement with version: STU 1.0.0
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.
FHIR Mapping: '2'
Implement with version: STU 1.0.0
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.
FHIR Mapping: '22'
Implement with version: STU 1.0.0
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.
FHIR Mapping: '1'
Implement with version: STU 1.0.0
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 2.2.2.1 Identifying the Patient for specific information on how to identify an individual to a UMO.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Claim.insurance[0].coverage => Coverage.subscriber => Patient
Locate the Coverage Resource in the Bundle that is referenced from the Claim.insurance[0].coverage. Then locate the Patient Resource in the Bundle referenced in the Coverage.subscriber attribute. Use the Patient Resource for all of the segments of the 2010C Loop
Implement with version: STU 1.0.0
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
FHIR Mapping: 'IL'
Implement with version: STU 1.0.0
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.
FHIR Mapping: '1'
Implement with version: STU 1.0.0
CODE
DEFINITION
1
Person
Situational
3
1035
Name Last or Organization Name
O 1
AN
1/60
Individual last name or organizational name
FHIR Mapping: Patient.name[0].family
Implement with version: STU 1.0.0
SEGMENT SYNTAX: C1203
SITUATIONAL RULE: Required when name information is needed by the UMO to identify the Subscriber. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Last Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
FHIR Mapping: Patient.name[0].given[0]
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when name information is needed by the UMO to identify the Subscriber. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
FHIR Mapping: Patient.name[0].given[1]
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when name information is needed by the UMO 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
Situational
6
1038
Name Prefix
O 1
AN
1/10
Prefix to individual name
FHIR Mapping: Patient.name[0].prefix[0]
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when military title or rank is needed by the UMO to determine the approriate benefit/level of care. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Name Prefix
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
FHIR Mapping: Patient.name[0].suffix[0]
Implement with version: STU 1.0.0
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)
FHIR Mapping: 'MI'
Implement with version: STU 1.1.0
SEGMENT SYNTAX: P0809
CODE
DEFINITION
II
Standard Unique Health Identifier for each Individual in the United States
The value "II" when used in this data element, shall be defined as "HIPAA Individual Identifier" if this identifier has been adopted. Under the Health Insurance Portability and Accountability Act of 1996, the Secretary of Health and Human Services must adopt a standard individual identifier for use in this transaction.
MI
Member Identification Number
The code MI is intended to be the subscriber's identification number as assigned by the payer. Payers use different terminology to convey the same number. Use MI - Member Identification Number to convey the following terms:
Insured's ID, Subscriber's ID, Health Insurance Claim Number (HIC), etc.
Required
9
67
Identification Code
O 1
AN
2/80
Code identifying a party or other code
FHIR Mapping: Patient.identifier[0].value
Implement with version: STU 1.0.0
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.
TR3 Notes:
  1. The primary identifier is the Member Identification Number in the NM1 segment.
  2. Health Insurance Claim (HIC) Number or Medicaid Recipient Identification Number are 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.
  3. If the requester values this segment with the Patient Account Number (REF01="EJ") on the request, the UMO is required to return the same value in this segment on the response.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.1.0
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
FHIR Mapping: Patient.identifier[1].type.coding[0].code
Translate as follows:
'1L' -> '1L'
'3L' -> '3L'
'6P' -> '6P'
'DP' -> 'DP'
'EJ' -> 'EJ'
'MC' -> 'F6'
'HJ' -> 'HJ'
'IG' -> 'IG'
'N6' -> 'N6'
'MA' -> 'NQ'
'SS' -> 'SY'
Implement with version: STU 1.1.0
CODE
DEFINITION
1L
Group or Policy Number
Use this code only if you cannot determine if the number is a Group Number (6P) or a Policy Number (IG).
3L
Branch Identifier
6P
Group Number
DP
Department Number
EJ
Patient Account Number
The maximum number of characters to be supported for this qualifier is `20'. Characters beyond the maximum are not required to be stored nor returned by any receiving system. Use this code only if the subscriber is the patient.
F6
Health Insurance Claim (HIC) Number
Use the NM1 (Subscriber Name) segment if the subscriber's HIC number is the primary identifier for his or her coverage. Use this code only in a REF segment when the payer has a different member number, and there is also a need to pass the subscriber's HIC number. This might occur in a Medicare HMO situation.
HJ
Identity Card Number
Use this code when the Identity Card Number differs from the Member Identification Number. This is particularly prevalent in the Medicaid environment.
IG
Insurance Policy Number
N6
Plan Network Identification Number
NQ
Medicaid Recipient Identification Number
SY
Social Security Number
Use this code only if the Social Security Number 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
FHIR Mapping: Patient.identifier[1].value
Implement with version: STU 1.1.0
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.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
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
FHIR Mapping: Patient.address[0].line[0]
Implement with version: STU 1.0.0
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
FHIR Mapping: Patient.address[0].line[1]
Implement with version: STU 1.0.0
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.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
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.
FHIR Mapping: Patient.address[0].city
Implement with version: STU 1.0.0
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.
FHIR Mapping: Patient.address[0].state
Implement with version: STU 1.0.0
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)
FHIR Mapping: Patient.address[0].postalCode
Implement with version: STU 1.0.0
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
FHIR Mapping: Patient.address[0].country
Implement with version: STU 1.0.0
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
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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 is required to determine medical necessity. If not required by this implementation guide, do not send.
TR3 Notes:
Refer to Section 1.12.2 Identifying the Patient for specific information on how to identify an individual to a UMO.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
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
FHIR Mapping: 'D8'
Implement with version: STU 1.0.0
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.
FHIR Mapping: Patient.birthDate
The Patient.birthDate format is YYYY-MM-DD and will need to be converted.
Implement with version: STU 1.1.0
SEGMENT SYNTAX: P0102
INDUSTRY NAME: Subscriber Birth Date
Situational
3
1068
Gender Code
O 1
ID
1
Code indicating the sex of the individual
FHIR Mapping: Patient.gender
The value from gender must be translated to an X12 specific value as follows:
'female' -> 'F'
'male' -> 'M'
'unknown' -> 'U'
'other' -> 'U'
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when gender code (DMG03) is needed 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 is necessary to determine the appropriate benefit/level of care. If not required by this implementation guide, do not send.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
This segment will only be populated when Patient.extension[n] has an occurrence of an extension where the uri atttribute is 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- militaryStatus'
Implement with version: STU 1.1.0
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.
FHIR Mapping: 'Y'
Implement with version: STU 1.0.0
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
FHIR Mapping: '18'
Implement with version: STU 1.0.0
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
FHIR Mapping: Patient.extension(militaryStatus).valueCodeableConcept.coding[0].codeThe militaryStatus extension has a url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-militaryStatus'
Implement with version: STU 1.0.0
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:
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.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile because the values are hardcoded or derived.
The 2000D is only created when the patient is other than the covered subscriber. Formally, create a 2000D when Coverage referenced by Claim.insurance[0].coverage has Coverage.relationship.coding[0].code NOT equal 'self'
Implement with version: STU 1.0.0
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.
FHIR Mapping: Create this element following HL segment and element rules.
Implement with version: STU 1.0.0
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.
FHIR Mapping: Create this element following HL segment and element rules.
Implement with version: STU 1.0.0
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.
FHIR Mapping: '23'
Implement with version: STU 1.0.0
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.
FHIR Mapping: '1'
Implement with version: STU 1.0.0
CODE
DEFINITION
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.

NM1*QC - DEPENDENT NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
  1. This segment conveys the name of the dependent who is the patient.
  2. The maximum data elements in Loop 2010D that can be required by a UMO to identify a dependent are as follows:
    Dependent Last Name (NM103)
    Dependent First Name (NM104)
    Dependent Birth Date (DMG01 and DMG02)
  3. Refer to Section 1.12.2 Identifying the Patient for specific information on how to identify an individual to a UMO.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
The 2000D is only created when the patient is not the covered subscriber.
Create a 2000D when Coverage referenced by Claim.insurance[0].coverage has Coverage.relationship.coding[0].code NOT equal 'self'
Implement with version: STU 1.0.0
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
FHIR Mapping: 'QC'
Implement with version: STU 1.0.0
CODE
DEFINITION
QC
Patient
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
FHIR Mapping: '1'
Implement with version: STU 1.0.0
CODE
DEFINITION
1
Person
Situational
3
1035
Name Last or Organization Name
O 1
AN
1/60
Individual last name or organizational name
FHIR Mapping: Patient.name[0].family
Implement with version: STU 1.0.0
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
FHIR Mapping: Patient.name[0].given[0]
Implement with version: STU 1.0.0
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
FHIR Mapping: Patient.name[0].given[1]
Implement with version: STU 1.0.0
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
FHIR Mapping: Patient.name[0].suffix[0]
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when name information is needed 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 requester values this segment with the Patient Account Number (REF01 = "EJ") on the request, the UMO is required to return the same value in this segment on the response.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.1.0
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
FHIR Mapping: Patient.identifier[0].type.coding[0].code
Translated as follows:
'EJ' -> 'EJ'
'SB' -> 'SY'
Implement with version: STU 1.1.0
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
FHIR Mapping: Patient.identifier[0].value
Implement with version: STU 1.1.0
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.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
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
FHIR Mapping: Patient.address[0].line[0]
Implement with version: STU 1.0.0
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
FHIR Mapping: Patient.address[0].line[1]
Implement with version: STU 1.0.0
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.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
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.
FHIR Mapping: Patient.address[0].city
Implement with version: STU 1.0.0
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.
FHIR Mapping: Patient.address[0].state
Implement with version: STU 1.0.0
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)
FHIR Mapping: Patient.address[0].postalCode
Implement with version: STU 1.0.0
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
FHIR Mapping: Patient.address[0].country
Implement with version: STU 1.0.0
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
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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 is required to determine medical necessity. If not required by this implementation guide, do not send.
TR3 Notes:
Refer to Section 1.12.2 Identifying the Patient for specific information on how to identify an individual to a UMO.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
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
FHIR Mapping: 'D8'
Implement with version: STU 1.0.0
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.
FHIR Mapping: Patient.birthDate
The Patient.birthDate format is YYYY-MM-DD and will need to be converted.
Implement with version: STU 1.1.0
SEGMENT SYNTAX: P0102
INDUSTRY NAME: Dependent Birth Date
Situational
3
1068
Gender Code
O 1
ID
1
Code indicating the sex of the individual
FHIR Mapping: Patient.gender
The value from gender must be translated to an X12 specific value as follows:
'female' -> 'F'
'male' -> 'M'
'unknown' -> 'U'
'other' -> 'U'
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when gender code (DMG03) is needed 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 is needed by the UMO to determine the appropriate benefit/level of care. If not required by this implementation guide, do not send.
TR3 Notes:
This segment may be used to further identify the patient. Examples include identifying a patient in a multiple birth or differentiating dependents with the same name.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
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.
FHIR Mapping: 'N'
Implement with version: STU 1.0.0
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
FHIR Mapping: Coverage.relationship
The value from Coverage.relationship.coding[0].code will be translated as follows:
'child' -> '19'
'parent' -> 'G8'
'spouse' -> '01'
'common' -> 'G8'
'other' -> 'G8'
'self' -> should not occur, see note on 2000D
'injured' -> 'G8'
Implement with version: STU 1.0.0
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.).
FHIR Mapping: Patient.multipleBirthInteger
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the dependent is a child from a multiple birth. If not required, do not send.
INDUSTRY NAME: Birth Sequence Number

HL - PATIENT EVENT LEVEL

X12 Name:
Hierarchical Level
X12 Purpose:
To identify dependencies among and the content of hierarchically related groups of data segments
X12 Comments:
  1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
  2. The HL segment defines a top-down/left-right ordered structure.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
Loop 2000E to provide information on the patient event associated with this health care services review.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile because the values are hardcoded or derived.
Implement with version: STU 1.0.0
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.
FHIR Mapping: Create this element following HL segment and element rules.
Implement with version: STU 1.0.0
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.
FHIR Mapping: Create this element following HL segment and element rules.
Implement with version: STU 1.0.0
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.
FHIR Mapping: 'EV'
Implement with version: STU 1.0.0
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.
FHIR Mapping: '1'
Implement with version: STU 1.0.0
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:
2
Situational Rule:
Required when the requester needs to assign a unique trace number to the patient event request. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
TR3 Notes:
  1. This enables the requester to
    • uniquely identify this patient event request
    • trace the request
    • match the response to the request
    • reference this request in any associated attachments containing additional patient information related to this patient event request.
  2. If the transaction is routed through a clearinghouse, the clearinghouse may add their own TRN segment. If the transaction passes through multiple clearinghouses, and the second clearinghouse needs to assign their own TRN segment, they must replace the TRN from the first clearinghouse and retain it to be returned in the 278 response. If the second clearinghouse does not need to assign a TRN segment, they should pass all received TRN segments.
  3. Each trace number provided in the TRN segment at this level on the request must be returned by the UMO in the TRN segment at the corresponding level of the response.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
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
FHIR Mapping: '1'
Implement with version: STU 1.0.0
CODE
DEFINITION
1
Current Transaction Trace Numbers
Required
2
127
Reference Identification
M 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: TRN02 provides unique identification for the transaction.
FHIR Mapping: Claim.identifier[0].value
Implement with version: STU 1.0.0
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.
FHIR Mapping: Claim.identifier[0].assigner.identifier.value
Implement with version: STU 1.0.0
INDUSTRY NAME: Trace Assigning Entity Identifier
  1. Use this element to identify the organization that assigned this trace number. TRN03 must be completed to aid requesters and clearinghouses in identifying their TRN in the 278 response.
  2. The first position must be either a "1" if an EIN is used, a "3" if a DUNS is used or a "9" if a user assigned identifier is used.
Situational
4
127
Reference Identification
O 1
AN
1/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.
FHIR Mapping: Claim.identifier[0].extension(identifierSubDepartment).valueString
The subDepartment extension has a url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- identifierSubDepartment'

Implement with version: STU 1.1.0
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

UM - HEALTH CARE SERVICES REVIEW INFORMATION

X12 Name:
Health Care Services Review Information
X12 Purpose:
To specify health care services review information
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
This segment identifies the type of health care services review request.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
UM✱SC✱I✱3✱✱✱✱✱✱Y~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1525
Request Category Code
M 1
ID
1/2
Code indicating a type of request
FHIR Mapping: Claim.item[0].extension(serviceItemRequestType).valueCodeableConcept.coding[0].code
The serviceItemRequestType extension has a url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-serviceItemRequestType'
Implement with version: STU 1.0.0
CODE
DEFINITION
AR
Admission Review
Required if requesting an admission to a facility.
HS
Health Services Review
Required if requesting a review of services related to an episode of care.
IN
Individual
Required when BHT06 is equal to "RU".
SC
Specialty Care Review
Required if requesting a referral to a specialty provider.
Required
2
1322
Certification Type Code
O 1
ID
1
Code indicating the type of certification
FHIR Mapping: Claim.item[0].extension(certificationType).valueCodeableConcept.coding[0].code
The certificationType extension has a url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-certificationType'
Implement with version: STU 1.0.0
CODE
DEFINITION
1
Appeal - Immediate
Use this value only for appeals of review decisions where the level of service required is emergency or urgent. If UM02 = 1 then UM06 must be valued.
2
Appeal - Standard
Use this value for appeals of review decisions where the level of service required is not emergency or urgent.
3
Cancel
4
Extension
Indicates that this is an extension request to a prior approved service.
I
Initial
N
Reconsideration
R
Renewal
Various services, such as physical therapy, spinal manipulation, and allergy treatment, have both a delivery pattern and a time span of authorization. Many UMOs place time limits - as in will not authorize anything for more than 30 days at a time. For example, blanket authorization for allergy treatments as required for 30 days. At the end of the 30 days, the provider must request to renew the certification - not extend it - because the UMO authorizes for 30 day intervals, one interval at a time.
S
Revised
Use if the requester is revising the specifics of a certification for which services have not been rendered. For example, the requester may be requesting 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
FHIR Mapping: Claim.item[0].category.coding[0].code
Implement with version: STU 1.0.0
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
87
Cancer
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.
Value at 2000F, Service Level, overrides the patient event for that service only.
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.
FHIR Mapping: Claim.item[0].locationCodeableConcept.coding[0].code
Implement with version: STU 1.0.0
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
FHIR Mapping: Claim.item[0].locationCodeableConcept.coding[0].system
Populate UM04-02 with the value in coding[0].system translated as follows:
'https://www.nubc.org/CodeSystem/TypeOfBill' -> 'A'
'https://www.cms.gov/Medicare/Coding/place-of-service-codes/Place_of_Service_Code_Set' -> 'B'
Implement with version: STU 1.0.0
CODE
DEFINITION
A
Uniform Billing Claim Form Bill Type
CODE SOURCE: 236: Uniform Billing Claim Form Bill Type
B
Place of Service Codes for Professional or Dental Services
CODE SOURCE: 237: Place of Service Codes for Professional Claims
Not Used
4-3
1325
Claim Frequency Type Code
O 1
ID
1
Situational
5
C024
Related Causes Information
O 1
To identify one or more related causes and associated state or country information
X12 COMPOSITE COMMENTS: C024-04 and C024-05 apply only to auto accidents when C024-01, C024-02, or C024-03 is equal to "AA".
SITUATIONAL RULE: Required when the patient's condition is accident or employment related. If not required by this implementation guide, do not send.
Required
5-1
1362
Related-Causes Code
M 1
ID
2/3
Code identifying an accompanying cause of an illness, injury or an accident
FHIR Mapping: Claim.accident.type.coding[0].code
Implement with version: STU 1.0.0
INDUSTRY NAME: Related Causes Code
Always use this data element if the related cause is an auto accident.
CODE
DEFINITION
AA
Auto Accident
AP
Another Party Responsible
EM
Employment
Situational
5-2
1362
Related-Causes Code
O 1
ID
2/3
Code identifying an accompanying cause of an illness, injury or an accident
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when there is greater than 1 related cause for this certification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Related Causes Code
CODE
DEFINITION
AP
Another Party Responsible
EM
Employment
Situational
5-3
1362
Related-Causes Code
O 1
ID
2/3
Code identifying an accompanying cause of an illness, injury or an accident
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when UM05 -1 and UM05-2 are not equal "AP" and "AP" applies to this patient event. If not required by this implementation guide, do not send.
INDUSTRY NAME: Related Causes Code
CODE
DEFINITION
AP
Another Party Responsible
Situational
5-4
156
State or Province Code
O 1
ID
2
Code (Standard State/Province) as defined by appropriate government agency
FHIR Mapping: Claim.accident.locationAddress.state
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when UM05-1 = "AA" and the accident occurred out of the services provider's state. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
CODE SOURCE 22: States and Provinces
Situational
5-5
26
Country Code
O 1
ID
2/3
Code identifying the country
FHIR Mapping: Claim.accident.locationAddress.country
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the automobile accident occurred out of the United States to identify the country in which the accident occurred. If not required by this implementation guide, do not send.
CODE SOURCE 5: Countries, Currencies and Funds
Situational
6
1338
Level of Service Code
O 1
ID
1/3
Code specifying the level of service rendered
FHIR Mapping: Claim.extension(levelOfServiceCode).valueCodeableConcept.coding[0].code
The levelOfServiceCode extension has a url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-levelOfServiceCode'
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when UM02=1 or if the patient event requires a level of service for care other than routine. If not required by this implementation guide do not send.
CODE
DEFINITION
03
Emergency
E
Elective
U
Urgent
Situational
7
1213
Current Health Condition Code
O 1
ID
1
Code indicating current health condition of the individual
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the patient's condition, as expressed by the codes in this data element, is a factor in the provider's determination of services to be performed that are not typically requested for the patient's diagnosis and proposed treatment. If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Acute
2
Stable
3
Chronic
4
Systemic
5
Localized
6
Mild Disease
7
Normal, Healthy
8
Severe Systemic disease
9
Severe Systemic Disease that is a Constant Threat to Life
E
Excellent
F
Fair
G
Good
P
Poor
Situational
8
923
Prognosis Code
O 1
ID
1
Code indicating physician's prognosis for the patient
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the patient's prognosis, as expressed by the codes in this data element, is a factor in the provider's determination of services to be performed that are not typically requested for the patient's diagnosis and proposed treatment. If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Poor
2
Guarded
3
Fair
4
Good
5
Very Good
6
Excellent
7
Less than 6 Months to Live
8
Terminal
Situational
9
1363
Release of Information Code
O 1
ID
1
Code indicating whether the provider has on file a signed statement by the patient authorizing the release of medical data to other organizations
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when applicable legislation requires that a signature be collected and reported on this Health Care Services Review. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
The Release of Information response is limited to the information carried in this service review.
CODE
DEFINITION
M
The Provider has Limited or Restricted Ability to Release Data Related to a Claim
For professional service, this value is only used when state or federal laws supersede the HIPAA privacy rule by requiring that the provider collect a signature and the patient is either not present or physically unable to sign at the time the provider submits the request.
Y
Yes, Provider has a Signed Statement Permitting Release of Medical Billing Data Related to a Claim
Situational
10
1514
Delay Reason Code
O 1
ID
1/2
Code indicating the reason why a request was delayed
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the request is not submitted within the normal timeframe of the UMO. If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Proof of Eligibility Unknown or Unavailable
2
Litigation
3
Authorization Delays
4
Delay in Certifying Provider
7
Third Party Processing Delay
8
Delay in Eligibility Determination
10
Administration Delay in the Prior Approval Process
11
Other
15
Natural Disaster
16
Lack of Information
17
No response to initial request

REF*BB - PREVIOUS REVIEW AUTHORIZATION NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when submitting an additional health care services review request associated with a request already processed by the UMO. If not required by this implementation guide, do not send.
TR3 Notes:
This is the authorization number assigned by the UMO to the original service review outcome associated with this service review. This is not the trace number assigned by the requester.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
TR3 Example:
REF✱BB✱A123~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
CODE
DEFINITION
BB
Authorization Number
Required
2
127
Reference Identification
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 - PREVIOUS REVIEW ADMINISTRATIVE REFERENCE NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when submitting a follow-up to a previous health care services review request for which the UMO has returned a response that contained an administrative reference number in the REF segment where REF01 = NT and did not return a certification number in HCR02. If not required by this implementation guide, do not send.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
TR3 Example:
REF✱NT✱Z123~
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: Previous 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.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
DTP✱439✱D8✱20050430~
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
FHIR Mapping: '439'
Implement with version: STU 1.0.0
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.
FHIR Mapping: 'D8'
Implement with version: STU 1.0.0
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
FHIR Mapping: Claim.accident.date
The Claim.accident.date may be in the format of CCYY or CCYYMM or CCYYMMDD
Implement with version: STU 1.0.0
INDUSTRY NAME: Accident Date

DTP*484 - LAST MENSTRUAL PERIOD DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the certification is pregnancy related. If not required by this implementation guide, do not send.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
TR3 Example:
DTP✱484✱D8✱20050312~
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 certification is related to the estimated date of delivery. If not required by this implementation guide, do not send.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
TR3 Example:
DTP✱ABC✱D8✱20051130~
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.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
TR3 Example:
DTP✱431✱D8✱20050415~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
431
Onset of Current Symptoms or Illness
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Onset Date

DTP*AAH - EVENT DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the proposed or actual date or range of dates of this patient event are known and UM01 does not equal AR. If not required by this implementation guide, do not send.
TR3 Notes:
If UM01 = AR use Admit Date.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
An Event Date DTP segment is created when the Claim has a supportingInfo attribute for a PatientEvent determined by:
supportingInfo[n].category.coding[0].system set to 'http://hl7.org/fhir/us/davinci-pas/CodeSystem-PASSupportingInfoType'
and
supportingInfo[n].category.coding[0].code set to 'patientEvent'
Implement with version: STU 1.1.0
TR3 Example:
DTP✱AAH✱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
FHIR Mapping: 'AAH'
Implement with version: STU 1.0.0
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.
FHIR Mapping: 'D8' or 'RD8'
If the supportingInfo[n] has an attribute named 'timingDate' set DTP02 to 'D8'
Otherwise set DTP02 to 'RD8'
Implement with version: STU 1.0.0
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
FHIR Mapping: Claim.supportingInfo(PatientEvent).timingDate | Claim.supportingInfo(PatientEvent).timingPeriod
If the supportingInfo[n] has the attribute timingDate set DTP03 to the value of timingDate
Otherwise set DTP03 to '-'
The date format is YYYY-MM-DD and will need to be converted.
Implement with version: STU 1.1.0
INDUSTRY NAME: Proposed or Actual Event Date

DTP*435 - ADMISSION DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when requesting an admission review (UM01 = "AR") to identify the proposed or actual date of admission. If not required by this implementation guide, do not send.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
An Admission Date DTP segment is created when the Claim has a supportingInfo attribute for AdmissionDates determined by:
supportingInfo[n].category.coding[0].system set to 'http://hl7.org/fhir/us/davinci-pas/CodeSystem-PASSupportingInfoType'
and
supportingInfo[n].category.coding[0].code set to 'admissionDates'
Implement with version: STU 1.1.0
TR3 Example:
DTP✱435✱D8✱20050505~
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
FHIR Mapping: '435'
Implement with version: STU 1.0.0
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.
FHIR Mapping: 'D8' or 'RD8'
If the supportingInfo[n] has an attribute named 'timingDate' set DTP02 to 'D8'
Otherwise set DTP02 to 'RD8'
Implement with version: STU 1.1.0
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
FHIR Mapping: Claim.supportingInfo(AdmissionDates).timingPeriod.start
The date format is YYYY-MM-DD and will need to be converted.
Implement with version: STU 1.1.0
INDUSTRY NAME: Proposed or Actual Admission Date

DTP*096 - DISCHARGE DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when requesting an admission review (UM01 = "AR") and the proposed or actual date of discharge from a facility is known. If not required by this implementation guide, do not send.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
A Discharge Date DTP segment is created when the Claim has a supportingInfo attribute for a DischargeDates determined by:
supportingInfo[n].category.coding[0].system set to 'http://hl7.org/fhir/us/davinci-pas/CodeSystem-PASSupportingInfoType'
and
supportingInfo[n].category.coding[0].code set to 'dischargeDates'
Implement with version: STU 1.1.0
TR3 Example:
DTP✱096✱D8✱20050509~
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
FHIR Mapping: '096'
Implement with version: STU 1.0.0
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.
FHIR Mapping: 'D8'
Implement with version: STU 1.0.0
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
FHIR Mapping: Claim.supportingInfo(DischargeDates).timingDate
The date format is YYYY-MM-DD and will need to be converted.
Implement with version: STU 1.1.0
INDUSTRY NAME: Proposed or Actual Discharge Date

HI - PATIENT DIAGNOSIS

X12 Name:
Health Care Information Codes
X12 Purpose:
To supply information related to the delivery of health care
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when known by the requester to convey diagnosis information. If not required by this implementation guide, do not send.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
HI✱BF:41090:D8:20050415~
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
FHIR Mapping: Use the values from Claim.diagnosis[0] in the mapping table DiagnosisTypeCodeMapping to determine this value.
Implement with version: STU 1.0.0
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
FHIR Mapping: Claim.diagnosis[0].diagnosisCodeableConcept.coding[0].code
Implement with version: STU 1.0.0
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
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
1-4
1251
Date Time Period
O 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
COMPOSITE SYNTAX: P0304
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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
FHIR Mapping: Use the values from Claim.diagnosis[1] in the mapping table DiagnosisTypeCodeMapping to determine this value.
Implement with version: STU 1.1.0
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
FHIR Mapping: Claim.diagnosis[1].diagnosisCodeableConcept.coding[0].code
Implement with version: STU 1.0.0
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
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
2-4
1251
Date Time Period
O 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
COMPOSITE SYNTAX: P0304
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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
FHIR Mapping: Use the values from Claim.diagnosis[2] in the mapping table DiagnosisTypeCodeMapping to determine this value.
Implement with version: STU 1.1.0
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
FHIR Mapping: Claim.diagnosis[2].diagnosisCodeableConcept.coding[0].code
Implement with version: STU 1.0.0
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
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
3-4
1251
Date Time Period
O 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
COMPOSITE SYNTAX: P0304
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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
FHIR Mapping: Use the values from Claim.diagnosis[3] in the mapping table DiagnosisTypeCodeMapping to determine this value.
Implement with version: STU 1.1.0
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
FHIR Mapping: Claim.diagnosis[3].diagnosisCodeableConcept.coding[0].code
Implement with version: STU 1.0.0
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
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
4-4
1251
Date Time Period
O 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
COMPOSITE SYNTAX: P0304
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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
FHIR Mapping: Use the values from Claim.diagnosis[4] in the mapping table DiagnosisTypeCodeMapping to determine this value.
Implement with version: STU 1.1.0
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
FHIR Mapping: Claim.diagnosis[4].diagnosisCodeableConcept.coding[0].code
Implement with version: STU 1.0.0
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
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
5-4
1251
Date Time Period
O 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
COMPOSITE SYNTAX: P0304
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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
FHIR Mapping: Use the values from Claim.diagnosis[5] in the mapping table DiagnosisTypeCodeMapping to determine this value.
Implement with version: STU 1.1.0
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
FHIR Mapping: Claim.diagnosis[5].diagnosisCodeableConcept.coding[0].code
Implement with version: STU 1.0.0
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
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
6-4
1251
Date Time Period
O 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
COMPOSITE SYNTAX: P0304
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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
FHIR Mapping: Use the values from Claim.diagnosis[6] in the mapping table DiagnosisTypeCodeMapping to determine this value.
Implement with version: STU 1.1.0
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
FHIR Mapping: Claim.diagnosis[6].diagnosisCodeableConcept.coding[0].code
Implement with version: STU 1.0.0
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
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
7-4
1251
Date Time Period
O 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
COMPOSITE SYNTAX: P0304
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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
FHIR Mapping: Use the values from Claim.diagnosis[7] in the mapping table DiagnosisTypeCodeMapping to determine this value.
Implement with version: STU 1.1.0
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
FHIR Mapping: Claim.diagnosis[7].diagnosisCodeableConcept.coding[0].code
Implement with version: STU 1.0.0
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
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
8-4
1251
Date Time Period
O 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
COMPOSITE SYNTAX: P0304
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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
FHIR Mapping: Use the values from Claim.diagnosis[8] in the mapping table DiagnosisTypeCodeMapping to determine this value.
Implement with version: STU 1.1.0
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
FHIR Mapping: Claim.diagnosis[8].diagnosisCodeableConcept.coding[0].code
Implement with version: STU 1.0.0
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
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
9-4
1251
Date Time Period
O 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
COMPOSITE SYNTAX: P0304
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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
FHIR Mapping: Use the values from Claim.diagnosis[9] in the mapping table DiagnosisTypeCodeMapping to determine this value.
Implement with version: STU 1.1.0
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
FHIR Mapping: Claim.diagnosis[9].diagnosisCodeableConcept.coding[0].code
Implement with version: STU 1.0.0
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
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
10-4
1251
Date Time Period
O 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
COMPOSITE SYNTAX: P0304
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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
FHIR Mapping: Use the values from Claim.diagnosis[10] in the mapping table DiagnosisTypeCodeMapping to determine this value.
Implement with version: STU 1.1.0
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
FHIR Mapping: Claim.diagnosis[10].diagnosisCodeableConcept.coding[0].code
Implement with version: STU 1.0.0
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
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
11-4
1251
Date Time Period
O 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
COMPOSITE SYNTAX: P0304
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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
FHIR Mapping: Use the values from Claim.diagnosis[11] in the mapping table DiagnosisTypeCodeMapping to determine this value.
Implement with version: STU 1.1.0
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
FHIR Mapping: Claim.diagnosis[11].diagnosisCodeableConcept.coding[0].code
Implement with version: STU 1.0.0
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
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the date diagnosed is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
12-4
1251
Date Time Period
O 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
COMPOSITE SYNTAX: P0304
FHIR Mapping: This data element is not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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 requesting services that have a specific pattern of delivery or usage. If not required by this implementation guide, do not send.
TR3 Notes:
An explanation of the uses of this segment follows.

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

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

An alternate way to use HSD is to employ HSD07 and/or HSD08. A data string of HSD*VS*1*****SX*D~ means "1 visit on Wednesday and Thursday morning".
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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
  1. Service Quantity
  2. If this is a request for an extension to an existing certification (UM02 = 4), then HSD02 represents the number of visits by which the certification is extended. If this is a request to revise an existing certification (UM02 = S), then HSD02 represents the new total.
Situational
3
355
Unit or Basis for Measurement Code
O 1
ID
2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
SITUATIONAL RULE: Required when 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 needed to indicate the frequency for the 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 patient events must be rendered within a specific timeframe. If not required by this implementation guide, do not send.
CODE
DEFINITION
6
Hour
7
Day
21
Years
26
Episode
27
Visit
34
Month
35
Week
Situational
6
616
Number of Periods
O 1
N
1/3
Total number of periods
SEGMENT SYNTAX: C0605
SITUATIONAL RULE: Required when patient events must be rendered within a specific timeframe. If not required by this implementation guide, do not send.
INDUSTRY NAME: Period Count
Situational
7
678
Ship/Delivery or Calendar Pattern Code
O 1
ID
1/2
Code which specifies the routine shipments, deliveries, or calendar pattern
SITUATIONAL RULE: Required when the patient event must be rendered within a specific calendar delivery pattern. If not required by this implementation guide, do not send.
INDUSTRY NAME: Delivery Frequency Code
CODE
DEFINITION
1
1st Week of the Month
2
2nd Week of the Month
3
3rd Week of the Month
4
4th Week of the Month
5
5th Week of the Month
6
1st & 3rd Weeks of the Month
7
2nd & 4th Weeks of the Month
8
1st Working Day of Period
9
Last Working Day of Period
A
Monday through Friday
B
Monday through Saturday
C
Monday through Sunday
D
Monday
E
Tuesday
F
Wednesday
G
Thursday
H
Friday
J
Saturday
K
Sunday
L
Monday through Thursday
M
Immediately
N
As Directed
O
Daily Mon. through Fri.
P
1/2 Mon. & 1/2 Thurs.
Q
1/2 Tues. & 1/2 Thurs.
R
1/2 Wed. & 1/2 Fri.
S
Once Anytime Mon. through Fri.
SA
Sunday, Monday, Thursday, Friday, Saturday
SB
Tuesday through Saturday
SC
Sunday, Wednesday, Thursday, Friday, Saturday
SD
Monday, Wednesday, Thursday, Friday, Saturday
SG
Tuesday through Friday
SL
Monday, Tuesday and Thursday
SP
Monday, Tuesday and Friday
SX
Wednesday and Thursday
SY
Monday, Wednesday and Thursday
SZ
Tuesday, Thursday and Friday
T
1/2 Tue. & 1/2 Fri.
U
1/2 Mon. & 1/2 Wed.
V
1/3 Mon., 1/3 Wed., 1/3 Fri.
W
Whenever Necessary
X
1/2 By Wed., Bal. By Fri.
Y
None (Also Used to Cancel or Override a Previous Pattern)
Situational
8
679
Ship/Delivery Pattern Time Code
O 1
ID
1
Code which specifies the time for routine shipments or deliveries
SITUATIONAL RULE: Required when a specific time delivery pattern for the services in this patient event must be identified. If not required by this implementation guide, do not send.
INDUSTRY NAME: Delivery Pattern Time Code
CODE
DEFINITION
A
1st Shift (Normal Working Hours)
B
2nd Shift
C
3rd Shift
D
A.M.
E
P.M.
F
As Directed
G
Any Shift
Y
None (Also Used to Cancel or Override a Previous Pattern)

CRC*07 - AMBULANCE CERTIFICATION INFORMATION

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

CRC*08 - CHIROPRACTIC CERTIFICATION INFORMATION

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

CRC*09 - DURABLE MEDICAL EQUIPMENT INFORMATION

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

CRC*11 - OXYGEN THERAPY CERTIFICATION INFORMATION

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

CRC*75 - FUNCTIONAL LIMITATIONS INFORMATION

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

CRC*76 - ACTIVITIES PERMITTED INFORMATION

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

CRC*77 - MENTAL STATUS INFORMATION

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

CL1 - 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 requesting certification for admission (UM01 = AR) to a facility. If not required by this implementation guide, do not send.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Claim.supportingInfo(InstitutionalEncounter).valueReference.reference => Encounter
The Claim has a supportingInfo attribute for a InstitutionalEncounter determined by:
supportingInfo[n].category.coding[0].system set to 'http://hl7.org/fhir/us/davinci-pas/CodeSystem-PASSupportingInfoType'
and
supportingInfo[n].category.coding[0].code set to 'institutionalEncounter'
Implement with version: STU 1.1.0
TR3 Example:
CL1✱3✱✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Situational
1
1315
Admission Type Code
O 1
ID
1
Code indicating the priority of this admission
FHIR Mapping: Encounter.type[0].coding[0].code
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when requesting admission to a hospital for inpatient services. 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
FHIR Mapping: Encounter.hospitalization.admitSource.coding[0].code
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when certification requires information on the admission source that is not provided in the Requester Loop 2000B. 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"
FHIR Mapping: Encounter.extension(patientStatus).valueCodeableConcept.coding[0].code
The patientStatus extension has a url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- patientStatus'
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when health care services review is for inpatient services. If not required by this implementation guide, do not send.
CODE SOURCE 239: Patient Status Code
Situational
4
1345
Nursing Home Residential Status Code
O 1
ID
1
Code specifying the status of a nursing home resident at the time of service
FHIR Mapping: Encounter.extension(nursingHomeResidentialStatus).valueCodeableConcept.coding[0].code
The nursingHomeResidentialStatus extension has a url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- nursingHomeResidentialStatus'
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when certification involves a nursing home resident. If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Transferred to Intermediate Care Facility - Mentally Retarded (ICF-MR)
2
Newly Admitted
3
Newly Eligible
4
No Longer Eligible
5
Still a Resident
6
Temporary Absence - Hospital
7
Temporary Absence - Other
8
Transferred to Intermediate Care Facility - Level II (ICF II)
9
Other

CR1 - AMBULANCE TRANSPORT INFORMATION

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

CR2 - SPINAL MANIPULATION SERVICE INFORMATION

X12 Name:
Chiropractic Certification
X12 Purpose:
To supply information related to the chiropractic service rendered to a patient
X12 Syntax:
  1. P0102
    If either CR201 or CR202 is present, then the other is required.
  2. C0403
    If CR204 is present, then CR203 is required.
  3. P0506
    If either CR205 or CR206 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when requesting certification for spinal manipulation services (UM01=HS) when the patient's condition or treatment involves subluxation. If not required by this implementation guide, do not send.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
TR3 Example:
CR2✱1✱5✱✱✱✱✱✱✱✱✱✱Y~
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 requesting certification for a specific treatment number in a series of treatments. If not required by this implementation guide, do not send.
INDUSTRY NAME: Treatment Series Number
Situational
2
380
Quantity
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 requesting certification for a specific treatment number in a series of treatments. If not required by this implementation guide, do not send.
INDUSTRY NAME: Treatment Count
Situational
3
1367
Subluxation Level Code
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
Required
8
1342
Nature of Condition Code
O 1
ID
1
Code indicating the nature of a patient's condition
INDUSTRY NAME: Patient Condition Code
CODE
DEFINITION
A
Acute Condition
C
Chronic Condition
D
Non-acute
E
Non-Life Threatening
F
Routine
G
Symptomatic
M
Acute Manifestation of a Chronic Condition
Required
9
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: CR209 is complication indicator. A "Y" value indicates a complicated condition; an "N" value indicates an uncomplicated condition.
INDUSTRY NAME: Complication Indicator
CODE
DEFINITION
N
No
Y
Yes
Situational
10
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
SEMANTIC: CR210 is a description of the patient's condition.
SITUATIONAL RULE: Required when necessary to clarify patient condition. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Condition Description
Situational
11
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
SEMANTIC: CR211 is an additional description of the patient's condition.
SITUATIONAL RULE: Required when necessary to clarify patient condition. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Condition Description
Situational
12
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: CR212 is X-rays availability indicator. A "Y" value indicates X-rays are maintained and available for carrier review; an "N" value indicates X-rays are not maintained and available for carrier review.
SITUATIONAL RULE: Required when X-rays are available. If not required by this implementation guide, do not send.
INDUSTRY NAME: X-ray Availability Indicator
CODE
DEFINITION
N
No
Y
Yes

CR5 - HOME OXYGEN THERAPY INFORMATION

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

CR6 - HOME HEALTH CARE INFORMATION

X12 Name:
Home Health Care Certification
X12 Purpose:
To supply information related to the certification of a home health care patient
X12 Syntax:
  1. P0304
    If either CR603 or CR604 is present, then the other is required.
  2. P091011
    If either CR609, CR610 or CR611 are present, then the others are required.
  3. P151617
    If either CR615, CR616 or CR617 are present, then the others are required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when requesting for certification of home health care, private duty nursing, or services by a nurses' agency. If not required by this implementation guide, do not send.
TR3 Notes:
Requests for home health care must include a principal diagnosis (HI01=BK) and principal diagnosis date in the HI segment in Loop 2000E, Patient Event.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
TR3 Example:
CR6✱7✱20050429✱✱✱✱N✱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 required is not emergency or urgent.
3
Cancel
4
Extension
Indicates that this is an extension request to a prior approved service.
6
Verification
This code is used to request the UMO to reconsider a previously denied referral or certification request.
I
Initial
R
Renewal
Indicates that this is a request to renew a prior approved service.
S
Revised
Use if the requester is revising the specifics of a certification for which services have not been rendered.
Situational
9
373
Date
O 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: CR609 is the date that the surgery identified in CR611 was performed.
SEGMENT SYNTAX: P091011
SITUATIONAL RULE: Required when home health care is related to a specific surgical procedure, the surgery date is known, and the surgical procedure code is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Surgery Date
Situational
10
235
Product/Service ID Qualifier
O 1
ID
2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
SEMANTIC: CR610 qualifies CR611.
SEGMENT SYNTAX: P091011
SITUATIONAL RULE: Required when home health care is related to a specific surgical procedure, the surgery date is known, and the surgical procedure code is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Product or Service ID Qualifier
CODE
DEFINITION
HC
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)
Situational
11
1137
Medical Code Value
O 1
AN
1/15
Code value for describing a medical condition or procedure
SEMANTIC: CR611 is the surgical procedure most relevant to the care being rendered.
SEGMENT SYNTAX: P091011
SITUATIONAL RULE: Required when home health care is related to a specific surgical procedure, the surgery date is known, and the surgical procedure code is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Surgical Procedure Code
Situational
12
373
Date
O 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: CR612 is the date the agency received the verbal orders from the physician for start of care.
SITUATIONAL RULE: Required when the requester received verbal orders from the physician for the start of home health care and the date when the order was received is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Physician Order Date
Situational
13
373
Date
O 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: CR613 is the date that the patient was last seen by the physician.
SITUATIONAL RULE: Required when the date the patient was last seen by the physician is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Last Visit Date
Situational
14
373
Date
O 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: CR614 is the date of the home health agency's most recent contact with the physician.
SITUATIONAL RULE: Required when the physician has been contacted by the home health service provider. If not required by this implementation guide, do not send.
INDUSTRY NAME: Physician Contact Date
Situational
15
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEGMENT SYNTAX: P151617
SITUATIONAL RULE: Required when home health care is associated with a recent inpatient stay, the admission stay date is known, and the facility type is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
RD8
Range of Dates Expressed in Format CCYYMMDD-CCYYMMDD
Situational
16
1251
Date Time Period
O 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
SEMANTIC: CR616 is the date range of the most recent inpatient stay.
SEGMENT SYNTAX: P151617
SITUATIONAL RULE: Required when home health care is associated with a recent inpatient stay, the admission stay date is known, and the facility type is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Last Admission Period
Situational
17
1384
Patient Location Code
O 1
ID
1
Code identifying the location where patient is receiving medical treatment
SEMANTIC: CR617 indicates the type of facility from which the patient was most recently discharged.
SEGMENT SYNTAX: P151617
SITUATIONAL RULE: Required when home health care is associated with a recent inpatient stay, the admission stay date is known, and the facility type is known. If not required by this implementation guide, do not send.
CODE
DEFINITION
A
Acute Care Facility
B
Boarding Home
C
Hospice
D
Intermediate Care Facility
E
Long-term or Extended Care Facility
F
Not Specified
G
Nursing Home
H
Sub-acute Care Facility
L
Other Location
M
Rehabilitation Facility
O
Outpatient Facility
P
Private Home
R
Residential Treatment Facility
S
Skilled Nursing Home
T
Rest Home
Not Used
18
373
Date
O 1
DT
8
Not Used
19
373
Date
O 1
DT
8
Not Used
20
373
Date
O 1
DT
8
Not Used
21
373
Date
O 1
DT
8

PWK - ADDITIONAL PATIENT INFORMATION

X12 Name:
Paperwork
X12 Purpose:
To identify the type or transmission or both of paperwork or supporting information
X12 Syntax:
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 report missing teeth on requests for dental services, or if the requester has additional documentation (electronic, paper, or other medium) associated with this health care services review that applies to the patient event and/or 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:
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.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Claim.supportingInfo(AdditionalInformation).valueReference.reference => DocumentReference
If a Claim.supportingInfo(AdditionalInformation) item exists create an initial PWK which will provide a link to the 275 Unsolicited message containing the Bundle content (mapping to the X316-275 described elsewhere). Create additional PWK segments as follows:
Create a Patient Event Level PWK segment for the first nine supportingInfo(AdditionalInformation) structure that are NOT referenced by a Service level PWK Claim.item[n],informationSequence[n].
The Claim will have a supportingInfo attribute for a AdditionalInformation determined by:
supportingInfo[n].category.coding[0].system set to 'http://hl7.org/fhir/us/davinci-pas/CodeSystem-PASSupportingInfoType'
and
supportingInfo[n].category.coding[0].code set to 'additionalInformation'
Implement with version: STU 1.0.0
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
FHIR Mapping: The first PWK segment will contain '77' |Additional PWK segments will use the DocumentReference.type.coding[0].code
Preferred value set is LOINC (not X12)
Implement with version: STU 1.0.0
INDUSTRY NAME: Attachment Report Type Code
CODE
DEFINITION
03
Report Justifying Treatment Beyond Utilization Guidelines
04
Drugs Administered
05
Treatment Diagnosis
06
Initial Assessment
07
Functional Goals
Expected outcomes of rehabilitative services.
08
Plan of Treatment
09
Progress Report
10
Continued Treatment
11
Chemical Analysis
13
Certified Test Report
15
Justification for Admission
21
Recovery Plan
48
Social Security Benefit Letter
55
Rental Agreement
Use for medical or dental equipment rental.
59
Benefit Letter
77
Support Data for Verification
A3
Allergies/Sensitivities Document
A4
Autopsy Report
AM
Ambulance Certification
Information to support necessity of ambulance trip.
AS
Admission Summary
A brief patient summary; it lists the patient's chief complaints and the reasons for admitting the patient to the hospital.
AT
Purchase Order Attachment
Use for purchase of medical or dental equipment.
B2
Prescription
B3
Physician Order
BR
Benchmark Testing Results
BS
Baseline
BT
Blanket Test Results
CB
Chiropractic Justification
Lists the reasons chiropractic is just and appropriate treatment.
CK
Consent Form(s)
D2
Drug Profile Document
DA
Dental Models
DB
Durable Medical Equipment Prescription
DG
Diagnostic Report
DJ
Discharge Monitoring Report
DS
Discharge Summary
FM
Family Medical History Document
HC
Health Certificate
HR
Health Clinic Records
I5
Immunization Record
IR
State School Immunization Records
LA
Laboratory Results
M1
Medical Record Attachment
NN
Nursing Notes
OB
Operative Note
OC
Oxygen Content Averaging Report
OD
Orders and Treatments Document
OE
Objective Physical Examination (including vital signs) Document
OX
Oxygen Therapy Certification
P4
Pathology Report
P5
Patient Medical History Document
P6
Periodontal Charts
Required when using the PWK segment to provide missing teeth information.
P7
Periodontal Reports
PE
Parenteral or Enteral Certification
PN
Physical Therapy Notes
PO
Prosthetics or Orthotic Certification
PQ
Paramedical Results
PY
Physician's Report
PZ
Physical Therapy Certification
QC
Cause and Corrective Action Report
QR
Quality Report
RB
Radiology Films
RR
Radiology Reports
RT
Report of Tests and Analysis Report
RX
Renewable Oxygen Content Averaging Report
SG
Symptoms Document
V5
Death Notification
XP
Photographs
Required
2
756
Report Transmission Code
O 1
ID
1/2
Code defining timing, transmission method or format by which reports are to be sent
FHIR Mapping: 'EL'
Implement with version: STU 1.0.0
CODE
DEFINITION
AA
Available on Request at Provider Site
Required when using the PWK segment to provide missing teeth information.

This means that the paperwork is not being sent with the request at this time. Instead, it is available to the UMO (or appropriate entity) on request.
BM
By Mail
EL
Electronically Only
Use to indicate that the attachment is being transmitted in a separate X12 functional group.
EM
E-Mail
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.
FHIR Mapping: 'AC'
Implement with version: STU 1.0.0
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
FHIR Mapping: The first PWK segment will contain the Claim.identifier[0].value | Additional PWK segments will use the DocumentReference.masterIdentifier.value
Implement with version: STU 1.0.0
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 requester can use it when PWK02 equals "AA" if the requester wants to send a document control number for an attachment remaining at the Provider's office.
Situational
7
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
COMMENT: PWK07 may be used to indicate special information to be shown on the specified report.
FHIR Mapping: The first PWK segment will contain no value | Additional PWK segments will use the DocumentReference.description
Implement with version: STU 1.0.0
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 needed to transmit a text message to the UMO about the patient event. If not required by this implementation guide, do not send.
TR3 Notes:
Do not use the MSG segment to relay information that you can send using codified information in existing data elements. If you need to use the MSG segment, you should approach X12N with data maintenance to solve the business need without the use of the MSG segment.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Creation of a MSG segment at the Patient Event level is done for the first supportingInfo(MessageText) that is NOT referenced from any Claim.item[n].informationSequence[n]
Implement with version: STU 1.0.0
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
FHIR Mapping: Claim.supportingInfo(MessageText).valueString
The Claim has a supportingInfo attribute for a MessageText determined by:
supportingInfo[n].category.coding[0].system set to 'http://hl7.org/fhir/us/davinci-pas/CodeSystem-PASSupportingInfoType'
and
supportingInfo[n].category.coding[0].code set to 'freeFormMessage'
Implement with version: STU 1.0.0
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 or when loop 2000F is valued and at least one occurrence of loop 2000F does not contain a 2010F loop. If not required by this implementation guide, do not send.
TR3 Notes:
  1. If Loop 2000F is not valued, this segment conveys the name and identification number of the service provider (person, group, or facility) specialist, or specialty entity to provide services to the patient for this patient event.
  2. If Loop 2000F is valued, the providers identified in this Loop 2010EA apply to all the services identified in Loop 2000F unless Loop 2010F is valued. Providers identified in Loop 2010F override the providers identified in Loop 2010EA for that service only.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Claim.careTeam[n].provider can point to either an Organization or Practitioner Resource.
For each Claim.careTeam[n].extension(careTeamClaimScope).valueBoolean = true (maximum of 14).
Implement with version: STU 1.1.0
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
FHIR Mapping: Claim.careTeam[n].role.coding[0].code
Implement with version: STU 1.0.0
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
Do not use if the entity identified in 2010B is the referring provider.
FA
Facility
G3
Clinic
P3
Primary Care Provider
QB
Purchase Service Provider
QV
Group Practice
SJ
Service Provider
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
FHIR Mapping: If the provider is a Practitioner Resource this value is '1'
If the provider is a Organization Resource this value is '2'
Implement with version: STU 1.0.0
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
FHIR Mapping: Practitioner.name[0].family | Organization.name
Implement with version: STU 1.0.0
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: Patient Event Provider Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
FHIR Mapping: Practitioner.name[0].given[0] | not used on Organization
Implement with version: STU 1.0.0
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
FHIR Mapping: Practitioner.name[0].given[1] | not used on Organization
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when NM104 is present and the middle name/initial of the person is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider Middle Name
Situational
6
1038
Name Prefix
O 1
AN
1/10
Prefix to individual name
FHIR Mapping: Practitioner.name[0].prefix[0] | not used on Organization
Implement with version: STU 1.0.0
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: Patient Event Provider Name Prefix
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
FHIR Mapping: Practitioner.name[0].suffix[0] | not used on Organization
Implement with version: STU 1.0.0
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)
FHIR Mapping: Practitioner.identifier[0].type.coding[0].code | Organization.identifier[0].type.coding[0].code
The value from the code attribute is translated as follows:
'EN' -> '24'
'SB' -> '34'
'46' -> '46'
'NPI' -> 'XX'
Implement with version: STU 1.1.0
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
FHIR Mapping: Practitioner.identifier[0].value | Organization.identifier[0].value
Implement with version: STU 1.0.0
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when requesting the services of a specific person, facility, group practice, or clinic and the provider ID is known by the requester. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider Identifier
Not Used
10
706
Entity Relationship Code
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 INFORMATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
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.
OR
Required prior to the mandated NPI implementation date when necessary for the UMO to identify the patient event provider.
If not required by this implementation guide, do not send.
TR3 Notes:
Use the NM1 Segment for the primary identifier.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim Inquiry profile, see the FHIR Mapping instructions for each data element below.
If Organization.identifier[n].type.coding[0].code is equal to 'SL' (State License Number), do not create this REF Segment.

Implement with version: STU 1.1.0
TR3 Example:
REF✱1G✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
FHIR Mapping: Practitioner.identifier[1].type.coding[0].code | Organization.identifier[1].type.coding[0].code
The value from the code attribute is translated as follows:
'SL' -> '0B'
'FI' -> '1J'
'EN' -> 'EI'
'N5' -> 'N5'
'N7' -> 'N7'
'SB' -> 'SY'
'ZH' -> 'ZH'
Implement with version: STU 1.1.0
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
FHIR Mapping: Practitioner.identifier[1].value | Organization.identifier[1].value
Implement with version: STU 1.0.0
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
FHIR Mapping: Practitioner.identifier[1].extension(jurisdiction).coding[0].code
Implement with version: STU 1.1.0
SEGMENT SYNTAX: R0203
SITUATIONAL RULE: Required when REF01 = 0B to report the two character state ID of the state assigning the State License Number. If not required by this implementation guide, do not send.
INDUSTRY NAME: License Number State Code
Not Used
4
C040
Reference Identifier
O 1

N3 - PATIENT EVENT PROVIDER ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the provider has multiple locations to identify the specific location for this patient event. If not required by this implementation guide, do not send.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
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
FHIR Mapping: Practitioner.address[0].line[1] | Organization.address[0].line[1]
Implement with version: STU 1.0.0
INDUSTRY NAME: Patient Event Provider Address Line
Use this element for the first line of the provider's address.
Situational
2
166
Address Information
O 1
AN
1/55
Address information
FHIR Mapping: Practitioner.address[0].line[2] | Organization.address[0].line[2]
Implement with version: STU 1.0.0
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 the provider has multiple locations to identify the specific location for this patient event. If not required by this implementation guide, do not send.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
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.
FHIR Mapping: Practitioner.address[0].city | Organization.address[0].city
Implement with version: STU 1.0.0
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.
FHIR Mapping: Practitioner.address[0].state | Organization.address[0].state
Implement with version: STU 1.0.0
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider State Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
O 1
ID
3/15
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
FHIR Mapping: Practitioner.address[0].postalCode | Organization.address[0].postalCode
Implement with version: STU 1.0.0
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
FHIR Mapping: Practitioner.address[0].country | Organization.address[0].country
Implement with version: STU 1.0.0
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
FHIR Mapping: Practitioner.address[0].district | Organization.address[0].district
Implement with version: STU 1.0.0
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.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
PER✱IC✱M TUCKER✱TE✱8189993456✱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
FHIR Mapping: 'IC'
Implement with version: STU 1.0.0
CODE
DEFINITION
IC
Information Contact
Situational
2
93
Name
O 1
AN
1/60
Free-form name
FHIR Mapping: no value when Practitioner | Organization.contact[0].name.text
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the requester needs to indicate a particular contact. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider Contact Name
Use this data element when the name of the individual to contact is not already defined or is different than the name within the prior name segment (e.g. N1 or NM1). If not required, do not send.
Situational
3
365
Communication Number Qualifier
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 provider needs to transmit a contact communication number. If not required by this implementation guide, do not send.
Practitioner.telecom[0].system | Organization.contact[0].telecom[0].system
The value from the system attribute is translated as follows:
'phone' -> 'TE'
'fax' -> 'FX'
'email' -> 'EM'
'pager' -> 'TE'
'url' -> 'UR'
'sms' -> 'TE'
'other' -> cannot be translated
Implement with version: STU 1.0.0
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
FHIR Mapping: Practitioner.telecom[0].value | Organization.contact[0].telecom[0].valueIf the value of system is 'phone', this value must be parsed to determine if an extension is present (see ITU-T E.123 for format of telephone values). If an extension is present, the remove the extension part of the phone number and place in PER06 and set PER05 to 'EX'
Implement with version: STU 1.0.0
SEGMENT SYNTAX: P0304
SITUATIONAL RULE: Required when PER02 is not valued or when the provider 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
FHIR Mapping: Practitioner.telecom[1].system | Organization.contact[0].telecom[1].system | 'EX'
See PER04 if PER03 is 'TE' otherwise select the next telecom in contact[0] and translate the system as follows:
'phone' -> 'TE'
'fax' -> 'FX'
'email' -> 'EM'
'pager' -> 'TE'
'url' -> 'UR'
'sms' -> 'TE'
'other' -> cannot be translated
Implement with version: STU 1.0.0
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when the 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
FHIR Mapping: Practitioner.telecom[1].value | Organization.contact[0].telecom[1].value | extracted extension
If PER05 is set to 'EX' this will be the extract value for the extension from PER04
Otherwise this is refer to PER04 for rules on formatting
Implement with version: STU 1.0.0
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when the 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
FHIR Mapping: Practitioner.telecom[n].system | Organization.contact[0].telecom[n].system | 'EX'
See PER06 if PER05 is 'TE' otherwise select the next telecom in contact[0] and translate the system as follows:
'phone' -> 'TE'
'fax' -> 'FX'
'email' -> 'EM'
'pager' -> 'TE'
'url' -> 'UR'
'sms' -> 'TE'
'other' -> cannot be translated
Implement with version: STU 1.0.0
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when the 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
FHIR Mapping: Practitioner.telecom[n].value | Organization.contact[0].telecom[n].value | extracted extension
If PER07 is set to 'EX' this will be the extract value for the extension from PER06
Otherwise this is refer to PER04 for rules on formatting
Implement with version: STU 1.0.0
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when the telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider Contact Communication Number
Not Used
9
443
Contact Inquiry Reference
O 1
AN
1/20

PRV - PATIENT EVENT PROVIDER INFORMATION

X12 Name:
Provider Information
X12 Purpose:
To specify the identifying characteristics of a provider
X12 Syntax:
P0203
If either PRV02 or PRV03 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when request is for services of a specialist or specialty entity to indicate the provider's specialty. If not required by this implementation guide, may be provided a the sender's discretion but cannot be required by the receiver.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Only populated when the careTeam[n].provider is a Practitioner
Implement with version: STU 1.0.0
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
FHIR Mapping: The qualifier code used in this qualifier element is mapped from the qualifier codes used in NM101, Claim.careTeam[n].role.coding[0].code.
Implement with version: STU 1.0.0
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
FHIR Mapping: 'PXC'
Implement with version: STU 1.0.0
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
FHIR Mapping: Claim.careTeam[n].qualification.coding[0].code
Implement with version: STU 1.0.0
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 - 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
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
TR3 Example:
  1. NM1✱PW✱2✱PATIENT DIALYSIS CENT~
  2. NM1✱FS✱2~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
45
Drop-off Location
FS
Final Scheduled Destination
ND
Next Destination
PW
Pickup Address
R3
Next Scheduled Destination
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
2
Non-Person Entity
Situational
3
1035
Name Last or Organization Name
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 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
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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 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 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
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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

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.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
TR3 Example:
NM1✱CA~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
00
Alternate Insurer
Use this code to indicate that the other UMO is commercial insurance.
CA
Carrier
Use this code to indicate that the other UMO is Medicare Part B.
GG
Intermediary
Use this code to indicate that the other UMO is Medicare Part A.
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
2
Non-Person Entity
Situational
3
1035
Name Last or Organization Name
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 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
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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 specific services are associated with this patient event. If not required by this implementation guide, do not send.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile because the values are hardcoded or derived.
Each occurrence of Claim.item[n] will have a corresponding 2000F occurrence
Implement with version: STU 1.0.0
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.
FHIR Mapping: Create this element following HL segment and element rules.
Implement with version: STU 1.0.0
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.
FHIR Mapping: Create this element following HL segment and element rules.
Implement with version: STU 1.0.0
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.
FHIR Mapping: 'SS'
Implement with version: STU 1.0.0
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.
FHIR Mapping: Create this element following HL segment and element rules.
Implement with version: STU 1.0.0
CODE
DEFINITION
0
No Subordinate HL Segment in This Hierarchical Structure.

TRN*1 - SERVICE TRACE NUMBER

X12 Name:
Trace
X12 Purpose:
To uniquely identify a transaction to an application
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
2
Situational Rule:
Required when the requester needs to assign a unique trace number to the service line request. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
TR3 Notes:
  1. This enables the requester to
    • uniquely identify this service line request
    • trace the request
    • match the response to the request
    • reference this request in any associated attachments containing additional service information related to this service line request.
  2. If the transaction is routed through a clearinghouse, the clearinghouse may add their own TRN segment. If the transaction passes through multiple clearinghouses, and the second clearinghouse needs to assign their own TRN segment, they must replace the TRN from the first clearinghouse and retain it to be returned in the 278 response. If the second clearinghouse does not need to assign a TRN segment, they should pass all received TRN segments.
  3. Each trace number provided in the TRN segment at this level on the request must be returned by the UMO in the TRN segment at the corresponding level of the response.
  4. If the request contains more than one occurrence of Loop 2000F and the requester needs to uniquely identify each service level request this TRN segment is required in each Service loop.
FHIR Mapping:
Create one TRN segment for each itemTraceNumber extension up to three (3) in the PAS Claim Inquiry.

Implement with version: STU 1.1.0
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
FHIR Mapping: '1'
Implement with version: STU 1.0.0
CODE
DEFINITION
1
Current Transaction Trace Numbers
Required
2
127
Reference Identification
M 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: TRN02 provides unique identification for the transaction.
FHIR Mapping: Claim.item[n].extension(itemTraceNumber).valueIdentifier.value
The itemTraceNumber extension has:
extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-itemTraceNumber'
Implement with version: STU 1.0.0
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.
FHIR Mapping: Claim.item[n].extension(itemTraceNumber).valueIdentifier.assigner.value
The itemTraceNumber extension has:
extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- itemTraceNumber'
Implement with version: STU 1.0.0
INDUSTRY NAME: Trace Assigning Entity Identifier
  1. Use this element to identify the organization that assigned this trace number. TRN03 must be completed to aid requesters and clearinghouses in identifying their TRN in the 278 response.
  2. The first position must be either a "1" if an EIN is used, a "3" if a DUNS is used or a "9" if a user assigned identifier is used.
Situational
4
127
Reference Identification
O 1
AN
1/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.
FHIR Mapping: Claim.item[n].extension(itemTraceNumber).extension (identifierSubDepartment).valueString
The subDepartment extension has a url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-
identifierSubDepartment'

Implement with version: STU 1.1.0
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

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.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
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
FHIR Mapping: Claim.item[n].extension(serviceItemRequestType).valueCodeableConcept.coding[0].code
The serviceItemRequestType extension has:
extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-serviceItemRequestType'
Implement with version: STU 1.0.0
CODE
DEFINITION
HS
Health Services Review
Required if requesting a review of services related to an episode of care.
SC
Specialty Care Review
Required if requesting a referral to a specialty provider.
Situational
2
1322
Certification Type Code
O 1
ID
1
Code indicating the type of certification
FHIR Mapping: Claim.item[n].extension(certificationType).valueCodeableConcept.coding[0].code
The certificationType extension has:
extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-certificationType'
Implement with version: STU 1.0.0
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
A "UM02 = 4" indicates that this is an extension request to a prior approved service.
I
Initial
N
Reconsideration
R
Renewal
Various services, such as physical therapy, spinal manipulation, and allergy treatment, have both a delivery pattern and a time span of authorization. Many UMOs place time limits - as in will not authorize anything for more than 30 days at a time. For example, blanket authorization for allergy treatments as required for 30 days. At the end of the 30 days, the provider must request to renew the certification - not extend it - because the UMO authorizes for 30 day intervals, one interval at a time.
S
Revised
Use if the requester is revising the specifics of a certification for which services have not been rendered. For example, the requester may be requesting 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
FHIR Mapping: Claim.item[n].category.coding[0].code
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when different from the UM03 value at the Patient Event level (Loop 2000E) or when SV1, SV2, or SV3 is not valued in this Service loop. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
Values at the Service Level override the values entered at the Patient Event Level for this service.
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
87
Cancer
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 entered at the Service Level overrides the value 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.
FHIR Mapping: Claim.item[n].locationCodeableConcept.coding[0].code
Implement with version: STU 1.0.0
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
FHIR Mapping: Claim.item[n].locationCodeableConcept.coding[0].system
Populate UM04-02 with the value in coding[n].system translated as follows:
'https://www.nubc.org/CodeSystem/TypeOfBill' -> 'A'
'https://www.cms.gov/Medicare/Coding/place-of-service-codes/Place_of_Service_Code_Set' -> 'B'
Implement with version: STU 1.0.0
CODE
DEFINITION
A
Uniform Billing Claim Form Bill Type
CODE SOURCE: 236: Uniform Billing Claim Form Bill Type
B
Place of Service Codes for Professional or Dental Services
CODE SOURCE: 237: Place of Service Codes for Professional Claims
Not Used
4-3
1325
Claim Frequency Type Code
O 1
ID
1
Not Used
5
C024
Related Causes Information
O 1
Not Used
6
1338
Level of Service Code
O 1
ID
1/3
Not Used
7
1213
Current Health Condition Code
O 1
ID
1
Not Used
8
923
Prognosis Code
O 1
ID
1
Not Used
9
1363
Release of Information Code
O 1
ID
1
Not Used
10
1514
Delay Reason Code
O 1
ID
1/2

REF*BB - PREVIOUS REVIEW AUTHORIZATION NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when different from the Previous Review Authorization Number specified at the Patient Event Level (Loop 2000E). If not required by this implementation guide, do not send.
TR3 Notes:
This is the authorization number assigned by the UMO to the original review outcome associated with this service. This is not the trace number assigned by the requester.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
REF✱BB✱A123~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
FHIR Mapping: 'BB'
Implement with version: STU 1.0.0
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
FHIR Mapping: Claim.item[n].extension(authorizationNumber).valueString
The authorizationNumber extension has:
extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-authorizationNumber'
Implement with version: STU 1.0.0
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 - PREVIOUS REVIEW ADMINISTRATIVE REFERENCE NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when different from the Previous Review Administrative Reference Number specified at the Patient Event Level (Loop 2000E). If not required by this implementation guide, do not send.
TR3 Notes:
This is the administrative number assigned by the UMO to the original service review outcome associated with this service review. This is not the trace number assigned by the requester.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
REF✱NT✱123Z~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
FHIR Mapping: 'NT'
Implement with version: STU 1.0.0
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
FHIR Mapping: Claim.item[n].extension(administrationReferenceNumber).valueString
The administrationReferenceNumber extension has:
extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-administrationReferenceNumber'
Implement with version: STU 1.0.0
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Previous 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.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
DTP✱472✱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
FHIR Mapping: '472'
Implement with version: STU 1.0.0
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.
FHIR Mapping: 'D8' or 'RD8'
If the item[n] has an attribute named 'servicedDate' set DTP02 to 'D8'
Otherwise set DTP02 to 'RD8'
Implement with version: STU 1.0.0
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
FHIR Mapping: Claim.item[n].servicedDate
Claim.item[n].servicedPeriod
If the item[n] has the attribute servicedDate set DTP03 to the value of servicedDate
Otherwise set DTP03 to '-'
Implement with version: STU 1.0.0
INDUSTRY NAME: Proposed or Actual Service Date

SV1 - PROFESSIONAL SERVICE

X12 Name:
Professional Service
X12 Purpose:
To specify the service line item detail for a health care professional
X12 Syntax:
P0304
If either SV103 or SV104 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when requesting a specific Professional Service. If not required by this implementation guide, do not send.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim Inquiry profile, see the FHIR Mapping instructions for each data element below.
If Claim.type.coding[0].code = 'professional' then populate the SV1 segment otherwise do not populate the elements.
Implement with version: STU 1.0.0
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)
FHIR Mapping: The value of Claim.item[n].productOrServiceCode.coding[0].system is translated as follows:
'http://codesystem.x12.org/005010/1365' -> no value
'http://www.ama-assn.org/go/cpt' -> 'HC'
'http://www.cms.gov/Medicare/Coding/HCPCSReleaseCodeSets' -> 'HC'
'http://hl7.org/fhir/sid/ndc' -> 'N4'
'http://terminology.hl7.org/CodeSystem/icd9cm' -> no value
'http://www.cms.gov/Medicare/Coding/ICD10' -> no value
Implement with version: STU 1.1.0
INDUSTRY NAME: Product or Service ID Qualifier
CODE
DEFINITION
HC
Health Care Financing Administration Common Procedural Coding System (HCPCS) Codes
This code is required when reporting CPT codes and Level 1 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
WK
Advanced Billing Concepts (ABC) Codes
This code set is not allowed for use under HIPAA at the time of this writing. The qualifier can only be used:
If a new rule names the Complimentary, Alternative, or Holistic Procedure Codes as an allowable code set under HIPAA,
OR
The Secretary grants an exception to use the code set as a pilot project as allowed under the law,
OR
For service reviews which are not covered under HIPAA.
CODE SOURCE: 843: Advanced Billing Concepts (ABC) Codes
Required
1-2
234
Product/Service ID
M 1
AN
1/48
Identifying number for a product or service
FHIR Mapping: Claim.item[n].productOrServiceCode.coding[0].code
Implement with version: STU 1.0.0
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
FHIR Mapping: Claim.item[n].modifier[0].coding[0].code
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
Use this modifier for the first procedure code modifier.
Situational
1-4
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
FHIR Mapping: Claim.item[n].modifier[1].coding[0].code
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
Use this modifier for the second procedure code modifier.
Situational
1-5
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
FHIR Mapping: Claim.item[n].modifier[2].coding[0].code
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
Use this modifier for the third procedure code modifier.
Situational
1-6
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
FHIR Mapping: Claim.item[n].modifier[3].coding[0].code
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
Use this modifier for the fourth procedure code modifier.
Situational
1-7
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
FHIR Mapping: Claim.item[n].productOrServiceCode.text
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the provider needs to convey additional clarification to miscellaneous, unspecified, or non descriptive procedures or modifiers. If not required by this implementation guide, may be provider at the sender's discretion but cannot be required by the receiver.
INDUSTRY NAME: Procedure Code Description
Situational
1-8
234
Product/Service ID
O 1
AN
1/48
Identifying number for a product or service
FHIR Mapping: Claim.item[n].extension(productOrServiceCodeEnd).valueCodeableConcept.coding[0].code
The productOrServiceCodeEnd extension has:
extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-productOrServiceCodeEnd'
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the requester cannot determine the intensity or complexity of the service to be performed and therefore requires authorization for a range of procedures. If not required by this implementation guide, do not send.
INDUSTRY NAME: Procedure Code
Use SV101-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.
FHIR Mapping: Claim.item[n].unitPrice.value
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the procedure charge amount is necessary to approve a monetary limitation for the health care services requests. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Line Amount
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
FHIR Mapping: Claim.item[n].quantity.unit
Implement with version: STU 1.0.0
SEGMENT SYNTAX: P0304
SITUATIONAL RULE: Required when service units were not provided in the HSD segment and a specific number of services are being requested for this procedure. If not required by this implementation guide, do not send.
CODE
DEFINITION
F2
International Unit
International Unit is used to indicate dosage amount. Dosage amount is only used for drug claims when the dosage of the drug is variable within a single NDC number (e.g., blood factors).
MJ
Minutes
UN
Unit
Situational
4
380
Quantity
O 1
R
1/15
Numeric value of quantity
FHIR Mapping: Claim.item[n].quantity.value
Implement with version: STU 1.0.0
SEGMENT SYNTAX: P0304
SITUATIONAL RULE: Required when service units were not provided in the HSD segment and a specific number of services are being requested for this procedure. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Unit Count
Not Used
5
1331
Facility Code Value
O 1
AN
1/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 the implementation, do not send.
  1. Acceptable values are 1 through 12.
  2. If no diagnosis pointer is provided, then this procedure applies to all diagnosis.
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
FHIR Mapping: Claim.item[n].diagnosisSequence[0]
Translate the value from diagnosisSequence[0] by locating the HI segment create for the referenced Claim.diagnosis[n] (where Claim.diagnosis[n].sequence = diagnosisSequence[0]) and use the HI number (1 to 12) for the value of SV101-01
Implement with version: STU 1.0.0
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
FHIR Mapping: Claim.item[n].diagnosisSequence[1]
Translate the value from diagnosisSequence[1] by locating the HI segment create for the referenced Claim.diagnosis[n] (where Claim.diagnosis[n].sequence = diagnosisSequence[1]) and use the HI number (1 to 12) for the value of SV101-02
Implement with version: STU 1.0.0
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
FHIR Mapping: Claim.item[n].diagnosisSequence[2]
Translate the value from diagnosisSequence[2] by locating the HI segment create for the referenced Claim.diagnosis[n] (where Claim.diagnosis[n].sequence = diagnosisSequence[2]) and use the HI number (1 to 12) for the value of SV101-03
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when procedure is related to more than two diagnoses. 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
FHIR Mapping: Claim.item[n].diagnosisSequence[3]
Translate the value from diagnosisSequence[3] by locating the HI segment create for the referenced Claim.diagnosis[n] (where Claim.diagnosis[n].sequence = diagnosisSequence[3]) and use the HI number (1 to 12) for the value of SV101-04
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when procedure is related to more than three diagnoses. 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.
FHIR Mapping: Claim.item[n].extension(epsdtIndicator).valueBoolean
The epsdtIndicator extension has:
extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-epsdtIndicator'
The valueBoolean is translated as follows:
true -> 'Y'
false -> 'N'
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the requested service is based on EPSDT. If not required by this implementation guide, do not send.
INDUSTRY NAME: EPSDT Indicator
CODE
DEFINITION
N
No
Y
Yes
Not Used
12
1073
Yes/No Condition or Response Code
O 1
ID
1
Not Used
13
1364
Review Code
O 1
ID
1/2
Not Used
14
1341
National or Local Assigned Review Value
O 1
AN
1/2
Not Used
15
1327
Copay Status Code
O 1
ID
1
Not Used
16
1334
Health Care Professional Shortage Area Code
O 1
ID
1
Not Used
17
127
Reference Identification
O 1
AN
1/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
FHIR Mapping: Claim.item[n].extension(nursingHomeLevelOfCare).valueCodeableConcept.coding[0].code
The nursingHomeLevelOfCare extension has:
extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-nursingHomeLevelOfCare'
Implement with version: STU 1.0.0
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 requesting a specific Institutional Service or requesting a specific Revenue Code for the Institutional Service. If not required by this implementation guide, do not send.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
If Claim.type.coding[0].code = 'institutional' then populate the SV1 segment otherwise do not populate the elements.
Implement with version: STU 1.0.0
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.
FHIR Mapping: Claim.item[n].revenue.coding[0].code
Implement with version: STU 1.0.0
SEGMENT SYNTAX: R0102
SITUATIONAL RULE: Required when requesting approval on a revenue code. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Line Revenue Code
See Code Source 132: National Uniform Billing Committee (NUBC) Codes.
Situational
2
C003
Composite Medical Procedure Identifier
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 requesting approval for a specific procedure code. If not required by this implementation guide, do not send.
Required
2-1
235
Product/Service ID Qualifier
M 1
ID
2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
FHIR Mapping: item.productOrServiceCode.coding.system
Implement with version: STU 1.0.0
INDUSTRY NAME: Product or Service ID Qualifier
CODE
DEFINITION
HC
Health Care Financing Administration Common Procedural Coding System (HCPCS) Codes
This code is required when reporting CPT codes and Level 1 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 (ICD-10-PCS)
Required
2-2
234
Product/Service ID
M 1
AN
1/48
Identifying number for a product or service
FHIR Mapping: Claim.item[n].productOrServiceCode.coding[0].code
Implement with version: STU 1.0.0
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
FHIR Mapping: Claim.item[n].modifier[0].coding[0].code
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
Use this data element for the first procedure code modifier.
Situational
2-4
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
FHIR Mapping: Claim.item[n].modifier[1].coding[0].code
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
Use this data element for the second procedure code modifier.
Situational
2-5
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
FHIR Mapping: Claim.item[n].modifier[2].coding[0].code
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
Use this data element for the third procedure code modifier.
Situational
2-6
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
FHIR Mapping: Claim.item[n].modifier[3].coding[0].code
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
Use this data element for the fourth procedure code modifier.
Situational
2-7
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
FHIR Mapping: Claim.item[n].productOrServiceCode.text
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the provider needs to convey additional clarification to miscellaneous, unspecified, or non descriptive procedures or modifiers. If not required by this implementation guide, may be provider at the sender's discretion but cannot be required by the receiver.
INDUSTRY NAME: Procedure Code Description
Situational
2-8
234
Product/Service ID
O 1
AN
1/48
Identifying number for a product or service
FHIR Mapping: Claim.item[n].extension(productOrServiceCodeEnd).valueCodeableConcept.coding[0].code
The productOrServiceCodeEnd extension has:
extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-productOrServiceCodeEnd'
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the requester cannot determine the intensity or complexity of the service to be performed and therefore requires authorization for a range of procedures. If not required by this implementation guide, do not send.
INDUSTRY NAME: Procedure Code
Use SV202-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.
FHIR Mapping: Claim.item[n].unitPrice.value
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the procedure charge amount is necessary to approve a monetary limitation for the health care services requests. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Line Amount
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
FHIR Mapping: Claim.item[n].quantity.unit
Implement with version: STU 1.0.0
SEGMENT SYNTAX: P0405
SITUATIONAL RULE: Required when service units were not provided in the HSD segment and a specific number of services are being requested for this procedure. If not required by this implementation guide, do not send.
CODE
DEFINITION
DA
Days
F2
International Unit
Dosage amount is only used for drug claims when the dosage of the drug is variable within a single NDC number (e.g. blood factors).
UN
Unit
Situational
5
380
Quantity
O 1
R
1/15
Numeric value of quantity
FHIR Mapping: Claim.item[n].quantity.value
Implement with version: STU 1.0.0
SEGMENT SYNTAX: P0405
SITUATIONAL RULE: Required when service units were not provided in the HSD segment and a specific number of services are being requested for this procedure. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Unit Count
Situational
6
1371
Unit Rate
O 1
R
1/10
The rate per unit of associate revenue for hospital accommodation
FHIR Mapping: Claim.item[n].extension(revenueUnitRateLimit).valueDecimal
The revenueUnitRateLimit extension has:
extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-revenueUnitRateLimit'
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when SV201 is valued and accommodation rate is necessary to approve a monetary limitation for the health care services requests. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Line Rate
Not Used
7
782
Monetary Amount
O 1
R
1/18
Not Used
8
1073
Yes/No Condition or Response Code
O 1
ID
1
Situational
9
1345
Nursing Home Residential Status Code
O 1
ID
1
Code specifying the status of a nursing home resident at the time of service
FHIR Mapping: Claim.item[n].extension(nursingHomeResidentialStatus).valueCodeableConcept.coding[0].code
The nursingHomeResidentialStatus extension has:
extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-nursingHomeResidentialStatus'
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the Health Care Services Review Request is for Long Term Care. If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Transferred to Intermediate Care Facility - Mentally Retarded (ICF-MR)
2
Newly Admitted
3
Newly Eligible
4
No Longer Eligible
5
Still a Resident
6
Temporary Absence - Hospital
7
Temporary Absence - Other
8
Transferred to Intermediate Care Facility - Level II (ICF II)
Situational
10
1337
Level of Care Code
O 1
ID
1
Code specifying the level of care provided by a nursing home facility
FHIR Mapping: Claim.item[n].extension(nursingHomeLevelOfCare).valueCodeableConcept.coding[0].code
The nursingHomeLevelOfCare extension has:
extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-nursingHomeLevelOfCare'
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when needed to further clarify the level of care being requested for admission to a nursing facility, or when the request is for non-nursing facility and the level of care in which the patient resides is needed. If not required by this implementation guide, do not send.
INDUSTRY NAME: Nursing Home Level of Care
CODE
DEFINITION
1
Skilled Nursing Facility (SNF)
2
Intermediate Care Facility (ICF)
3
Intermediate Care Facility - Mentally Retarded (ICF-MR)
4
Chronic Disease Hospital (CD)
5
Intermediate Care Facility (ICF) Level II
6
Special Skilled Nursing Facility (SNF)
7
Nursing Facility (NF)
8
Hospice

SV3 - DENTAL SERVICE

X12 Name:
Dental Service
X12 Purpose:
To specify the service line item detail for dental work
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when requesting a specific Dental Service. If not required by this implementation guide, do not send.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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
CDT = Current Dental Terminology
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 additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
  1. Use this data element for the first procedure code modifier.
  2. 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.
Situational
1-4
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
  1. Use this data element for the second procedure code modifier.
  2. 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.
Situational
1-5
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
  1. Use this data element for the third procedure code modifier.
  2. 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.
Situational
1-6
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when additional clarification to the associated procedure code for which authorization is being requested. If not required by this implementation guide, do not send.
  1. Use this data element for the fourth procedure code modifier.
  2. 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.
Situational
1-7
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
SITUATIONAL RULE: Required when the service request is for a "Not Otherwise Classified" (NOC) or "By Report" procedure code or to report the following information on this service line: Date of Initial Impression, Date of Initial Preparation Crown, Initial Preparation Crown Tooth Number, or Initial Endodontic Treatment. If not required by this implementation guide, do not send.
INDUSTRY NAME: Procedure Code Description
Situational
1-8
234
Product/Service ID
O 1
AN
1/48
Identifying number for a product or service
SITUATIONAL RULE: Required when the requester cannot determine the intensity or complexity of the service to be performed and therefore requires authorization for a range of procedures. If not required by this implementation guide, do not send.
INDUSTRY NAME: Procedure Code
Use SV301-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 usual and customary cost is necessary to approve a monetary limitation for the health care services requests. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Line Amount
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 Codes
CODE SOURCE 135: American Dental Association
Situational
4-2
1361
Oral Cavity Designation Code
O 1
ID
1/3
Code Identifying the area of the oral cavity in which service is rendered
SITUATIONAL RULE: Required when needed to identify additional oral cavity designation codes. If not required by this implementation guide, do not send.
Code source 135: American Dental Association Codes
CODE SOURCE 135: American Dental Association
Situational
4-3
1361
Oral Cavity Designation Code
O 1
ID
1/3
Code Identifying the area of the oral cavity in which service is rendered
SITUATIONAL RULE: Required when needed to identify additional oral cavity designation codes. If not required by this implementation guide, do not send.
Code source 135: American Dental Association Codes
CODE SOURCE 135: American Dental Association
Situational
4-4
1361
Oral Cavity Designation Code
O 1
ID
1/3
Code Identifying the area of the oral cavity in which service is rendered
SITUATIONAL RULE: Required when needed to identify additional oral cavity designation codes. If not required by this implementation guide, do not send.
Code source 135: American Dental Association Codes
CODE SOURCE 135: American Dental Association
Situational
4-5
1361
Oral Cavity Designation Code
O 1
ID
1/3
Code Identifying the area of the oral cavity in which service is rendered
SITUATIONAL RULE: Required when needed to identify additional oral cavity designation codes. If not required by this implementation guide, do not send.
Code source 135: American Dental Association Codes
CODE SOURCE 135: American Dental Association
Situational
5
1358
Prosthesis, Crown or Inlay Code
O 1
ID
1
Code specifying the placement status for the dental work
SITUATIONAL RULE: Required when needed to indicate the placement status of the prosthetic for this service. If not required by this implementation guide, do not send.
INDUSTRY NAME: Prosthesis, Crown, or Inlay Code
CODE
DEFINITION
I
Initial Placement
R
Replacement
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 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.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile.
Implement with version: STU 1.0.0
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
Code source 135: American Dental Association Codes
Situational
3
C005
Tooth Surface
O 1
To identify one or more tooth surface codes
SITUATIONAL RULE: Required when reporting tooth surface as defined by the procedure code. If not required by this implementation guide, do not send.
Required
3-1
1369
Tooth Surface Code
M 1
ID
1/2
Code identifying the area of the tooth that was treated
CODE
DEFINITION
B
Buccal
D
Distal
F
Facial
I
Incisal
L
Lingual
M
Mesial
O
Occlusal
Situational
3-2
1369
Tooth Surface Code
O 1
ID
1/2
Code identifying the area of the tooth that was treated
SITUATIONAL RULE: Required when necessary to report a second tooth surface. If not required by this implementation guide, do not send.
Use code values from TOO03-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 requesting services that have a specific pattern of delivery and the pattern of delivery or usage for this service is different from the pattern of delivery or usage (HSD) in the Patient Event (Loop 2000E). If not required by this implementation guide, do not send.
TR3 Notes:
An explanation of the uses of this segment follows.

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

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

An alternate way to use HSD is to employ HSD07 and/or HSD08. A data string of HSD*VS*1*****SX*D~ means "1 visit on Wednesday and Thursday morning".
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Claim.item[n].extension(requestedService).valueReference.reference => MedicationRequest | ServiceRequest | DeviceRequest
The requestedService extension has:
extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- requestedService'
Locate the MedicationRequest or Servicerequest or DeviceRequest within the Bundle referenced from the extension and use that resource in populating the HSD segment.
Implement with version: STU 1.0.0
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
FHIR Mapping: Claim.item[n].quantity.unit
Implement with version: STU 1.0.0
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
FHIR Mapping: Claim.item[n].quantity.value
Implement with version: STU 1.0.0
SEGMENT SYNTAX: P0102
SITUATIONAL RULE: Required when HSD01 is valued to indicate the service quantity. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Unit Count
  1. Service Quantity
  2. If this is a request for an extension to an existing certification (UM02 = 4), then HSD02 represents the number of visits by which the certification is extended. If this is a request to revise an existing certification (UM02 = S), then HSD02 represents the new total.
Situational
3
355
Unit or Basis for Measurement Code
O 1
ID
2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
FHIR Mapping: MedicationRequest.dosageInstruction[0].timing.repeat.periodUnit | ServiceRequest.occurrenceTiming.repeat.periodUnit | DeviceRequest.occurrenceTiming.repeat.periodUnit
Translate the value from periodUnit as follows:
'da' -> 'DA'
'wk' -> 'WK'
'mo' -> 'MO'
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when needed to indicate the timeframe in which the quantity of services in HSD02 will be rendered. If not required by this implementation guide, do not send.
CODE
DEFINITION
DA
Days
MO
Months
WK
Week
Situational
4
1167
Sample Selection Modulus
O 1
R
1/6
To specify the sampling frequency in terms of a modulus of the Unit of Measure, e.g., every fifth bag, every 1.5 minutes
FHIR Mapping: MedicationRequest.dosageInstruction[0].timing.repeat.period | ServiceRequest.occurrenceTiming.repeat.period | DeviceRequest.occurrenceTiming.repeat.period
Implement with version: STU 1.0.0
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
FHIR Mapping: MedicationRequest.dosageInstruction[0].timing.repeat.boundsDuration.unit | ServiceRequest.occurrenceTiming.repeat.boundsDuration.unit | DeviceRequest.occurrenceTiming.repeat.boundsDuration.unit
Implement with version: STU 1.0.0
SEGMENT SYNTAX: C0605
SITUATIONAL RULE: Required when needed to indicate the time period for which the services will be continued. If not required by this implementation guide, do not send.
CODE
DEFINITION
6
Hour
7
Day
21
Years
26
Episode
27
Visit
34
Month
35
Week
Situational
6
616
Number of Periods
O 1
N
1/3
Total number of periods
FHIR Mapping: MedicationRequest.dosageInstruction[0].timing.repeat.boundsDuration.value | ServiceRequest.occurrenceTiming.repeat.boundsDuration.value | DeviceRequest.occurrenceTiming.repeat.boundsDuration.value
Implement with version: STU 1.0.0
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
FHIR Mapping: MedicationRequest.dosageInstruction[0].timing.extension(timingCalendarPattern).valueCodeableConcept.coding[0].code | ServiceRequest.occurrenceTiming.extension(timingCalendarPattern).valueCodeableConcept.coding[0].code | DeviceRequest.occurrenceTiming.extension(timingCalendarPattern).valueCodeableConcept.coding[0].code
The timingCalendarPattern extension has:
extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-timingcalendarpattern'
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the patient event must be rendered within a specific calendar delivery pattern. If not required by this implementation guide, do not send.
INDUSTRY NAME: Delivery Frequency Code
CODE
DEFINITION
1
1st Week of the Month
2
2nd Week of the Month
3
3rd Week of the Month
4
4th Week of the Month
5
5th Week of the Month
6
1st & 3rd Weeks of the Month
7
2nd & 4th Weeks of the Month
8
1st Working Day of Period
9
Last Working Day of Period
A
Monday through Friday
B
Monday through Saturday
C
Monday through Sunday
D
Monday
E
Tuesday
F
Wednesday
G
Thursday
H
Friday
J
Saturday
K
Sunday
L
Monday through Thursday
M
Immediately
N
As Directed
O
Daily Mon. through Fri.
P
1/2 Mon. & 1/2 Thurs.
Q
1/2 Tues. & 1/2 Thurs.
R
1/2 Wed. & 1/2 Fri.
S
Once Anytime Mon. through Fri.
SA
Sunday, Monday, Thursday, Friday, Saturday
SB
Tuesday through Saturday
SC
Sunday, Wednesday, Thursday, Friday, Saturday
SD
Monday, Wednesday, Thursday, Friday, Saturday
SG
Tuesday through Friday
SL
Monday, Tuesday and Thursday
SP
Monday, Tuesday and Friday
SX
Wednesday and Thursday
SY
Monday, Wednesday and Thursday
SZ
Tuesday, Thursday and Friday
T
1/2 Tue. & 1/2 Fri.
U
1/2 Mon. & 1/2 Wed.
V
1/3 Mon., 1/3 Wed., 1/3 Fri.
W
Whenever Necessary
X
1/2 By Wed., Bal. By Fri.
Y
None (Also Used to Cancel or Override a Previous Pattern)
Situational
8
679
Ship/Delivery Pattern Time Code
O 1
ID
1
Code which specifies the time for routine shipments or deliveries
FHIR Mapping: MedicationRequest.dosageInstruction[0].timing.extension(timingDeliveryPattern).valueCodeableConcept.coding[0].code | ServiceRequest.occurrenceTiming.extension(timingDeliveryPattern).valueCodeableConcept.coding[0].code | DeviceRequest.occurrenceTiming.extension(timingDeliveryPattern).valueCodeableConcept.coding[0].code
The timingDeliveryPattern extension has:
extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-timingdeliverypattern'
Implement with version: STU 1.0.0
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 requester has additional documentation (electronic, paper, or other medium) associated with this health care services review that applies to the service(s) requested in this Service loop, and the 278 request (ST-SE) does not support this information in its segments and data elements. If not required by this implementation guide, do not send.
TR3 Notes:
  1. Additional documentation at the service level should apply to a specific service and/or all the services requested in this service loop.
  2. This PWK segment is required to identify attachments that are sent electronically (PWK02 = EL) but are transmitted in another X12 functional group rather than by paper or other medium. PWK06 is used to identify the attached electronic documentation. The number in PWK06 would be referenced in the electronic attachment.
  3. The requester can also use this PWK segment to identify paperwork that is held at the provider's office and is available upon request by the UMO (or appropriate entity). Use code AA in PWK02 to convey this specific use of the PWK segment. See code note under PWK02, code AA.

    Refer to Section 2.5 for more information on using this PWK segment.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Claim.item[n].informationSequence => Claim.supportingInfo[n].valueReference => DocumentReference
Locate the Claim.supportingInfo where supportingInfo[n].sequence = to Claim.item[n].informationSequence.
If the supportingInfo is AdditionalInformation where
supportingInfo[n].category.coding[0].system set to 'http://hl7.org/fhir/us/davinci-pas/CodeSystem-PASSupportingInfoType'
and
supportingInfo[n].category.coding[0].code set to 'additionalInformation'
Then a PWK segment is created.
Locate the DocumentReference using the valueReference.reference in the supportingInfo.
Implement with version: STU 1.0.0
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
FHIR Mapping: DocumentReference.type.coding[0].code
Preferred value set is LOINC (not X12)
Implement with version: STU 1.0.0
INDUSTRY NAME: Attachment Report Type Code
CODE
DEFINITION
03
Report Justifying Treatment Beyond Utilization Guidelines
04
Drugs Administered
05
Treatment Diagnosis
06
Initial Assessment
07
Functional Goals
Expected outcomes of rehabilitative services.
08
Plan of Treatment
09
Progress Report
10
Continued Treatment
11
Chemical Analysis
13
Certified Test Report
15
Justification for Admission
21
Recovery Plan
48
Social Security Benefit Letter
55
Rental Agreement
Use for medical or dental equipment rental.
59
Benefit Letter
77
Support Data for Verification
A3
Allergies/Sensitivities Document
A4
Autopsy Report
AM
Ambulance Certification
Information to support necessity of ambulance trip.
AS
Admission Summary
A brief patient summary; it lists the patient's chief complaints and the reasons for admitting the patient to the hospital.
AT
Purchase Order Attachment
Use for purchase of medical or dental equipment.
B2
Prescription
B3
Physician Order
BR
Benchmark Testing Results
BS
Baseline
BT
Blanket Test Results
CB
Chiropractic Justification
Lists the reasons chiropractic is just and appropriate treatment.
CK
Consent Form(s)
D2
Drug Profile Document
DA
Dental Models
DB
Durable Medical Equipment Prescription
DG
Diagnostic Report
DJ
Discharge Monitoring Report
DS
Discharge Summary
FM
Family Medical History Document
HC
Health Certificate
HR
Health Clinic Records
I5
Immunization Record
IR
State School Immunization Records
LA
Laboratory Results
M1
Medical Record Attachment
NN
Nursing Notes
OB
Operative Note
OC
Oxygen Content Averaging Report
OD
Orders and Treatments Document
OE
Objective Physical Examination (including vital signs) Document
OX
Oxygen Therapy Certification
P4
Pathology Report
P5
Patient Medical History Document
P6
Periodontal Charts
P7
Periodontal Reports
PE
Parenteral or Enteral Certification
PN
Physical Therapy Notes
PO
Prosthetics or Orthotic Certification
PQ
Paramedical Results
PY
Physician's Report
PZ
Physical Therapy Certification
QC
Cause and Corrective Action Report
QR
Quality Report
RB
Radiology Films
RR
Radiology Reports
RT
Report of Tests and Analysis Report
RX
Renewable Oxygen Content Averaging Report
SG
Symptoms Document
V5
Death Notification
XP
Photographs
Required
2
756
Report Transmission Code
O 1
ID
1/2
Code defining timing, transmission method or format by which reports are to be sent
FHIR Mapping: 'EL'
Implement with version: STU 1.0.0
CODE
DEFINITION
AA
Available on Request at Provider Site
This means that the paperwork is not being sent with the request at this time. Instead, it is available to the UMO (or appropriate entity) on request.
BM
By Mail
EL
Electronically Only
Use to indicate that the attachment is being transmitted in a separate X12 functional group.
EM
E-Mail
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.
FHIR Mapping: 'AC'
Implement with version: STU 1.0.0
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
FHIR Mapping: DocumentReference.identifier.value
Implement with version: STU 1.0.0
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 requester can use it when PWK02 equals "AA" if the requester wants to send a document control number for an attachment remaining at the Provider's office.
Situational
7
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
COMMENT: PWK07 may be used to indicate special information to be shown on the specified report.
FHIR Mapping: DocumentReference.description
Implement with version: STU 1.0.0
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 UMO about the service. If not required by this implementation guide, do not send.
TR3 Notes:
Do not use the MSG segment to relay information that you can send using codified information in existing data elements. If you need to use the MSG segment, you should approach X12N with data maintenance to solve the business need without the use of the MSG segment.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
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
FHIR Mapping: Claim.item[n].informationSequence => Claim.supportingInfo[n].valueString
Locate the Claim.supportingInfo where supportingInfo[n].sequence = to Claim.item[n].informationSequence.
If the supportingInfo is MessageText where
supportingInfo[n].category.coding[0].system set to 'http://hl7.org/fhir/us/davinci-pas/CodeSystem-PASSupportingInfoType'
and
supportingInfo[n].category.coding[0].code set to 'freeFormMessage'
Then a MSG segment is created.
Use the valueString in the supportingInfo for MSG01
Implement with version: STU 1.0.0
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 requesting a service provider, specialist, or specialty entity for this service that is different from the provider, specialist, or specialty entity identified in Loop 2010EA (Patient Event Provider Name). If Loop 2010EA is not valued, Loop 2010F must be valued for each service associated with this patient event. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
TR3 Notes:
  1. Use this segment to convey the name and identification number of the service provider (person, group, or facility) specialist, or specialty entity to provide services to the patient.
  2. If this loop is not valued, loop 2010E is required to identify the service provider, specialist, or speciality entity to provide services.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Claim.careTeam[n].provider => Practitioner | Organization
Where Claim.careTeam[n].sequence = Claim.item[n].careTeamSequence[0..9] (create for the 1st 10 occurrences only)
Implement with version: STU 1.1.0
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
FHIR Mapping: Claim.careTeam[n].role.coding[0].code
Implement with version: STU 1.0.0
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.
FHIR Mapping: If the provider is a Practitioner Resource this value is '1'
If the provider is a Organization Resource this value is '2'
Implement with version: STU 1.0.0
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
FHIR Mapping: Practitioner.name[0].family | Organization.name
Implement with version: STU 1.0.0
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
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
FHIR Mapping: Practitioner.name[0].given[0] | not used on Organization
Implement with version: STU 1.0.0
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
FHIR Mapping: Practitioner.name[0].given[1] | not used on Organization
Implement with version: STU 1.0.0
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
FHIR Mapping: Practitioner.name[0].prefix[0] | not used on Organization
Implement with version: STU 1.0.0
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
FHIR Mapping: Practitioner.name[0].suffix[0] | not used on Organization
Implement with version: STU 1.0.0
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: 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)
FHIR Mapping: Practitioner.identifier[0].type.coding[0].code | Organization.identifier[0].type.coding[0].code
The value from the code attribute is translated as follows:
'EN' -> '24'
'SB' -> '34'
'46' -> '46'
'NPI' -> 'XX'
Implement with version: STU 1.1.0
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
FHIR Mapping: Practitioner.identifier[0].value | Organization.identifier[0].value
Implement with version: STU 1.0.0
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 service provider.
OR
Required prior to the mandated NPI implementation date when necessary for the UMO to identify the service provider.
If not required by this implementation guide, do not send.
TR3 Notes:
Use the NM1 Segment for the primary identifier.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
If Organization.identifier[n].type.coding[0].code is equal to 'SL' (State License Number), do not create this REF Segment.
Implement with version: STU 1.1.0
TR3 Example:
REF✱1G✱12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code qualifying the Reference Identification
FHIR Mapping: Practitioner.identifier[1].type.coding[0].code | Organization.identifier[1].type.coding[0].code
The value from the code attribute is translated as follows:
'SL' -> '0B'
'FI' -> '1J'
'EN' -> 'EI'
'N5' -> 'N5'
'N7' -> 'N7'
'SB' -> 'SY'
'ZH' -> 'ZH'
Implement with version: STU 1.1.0
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
Required when necessary to provide 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
FHIR Mapping: Practitioner.identifier[1].value | Organization.identifier[1].value
Implement with version: STU 1.0.0
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
FHIR Mapping: Practitioner.identifier[1].extension(jurisdiction).coding[0].code
Implement with version: STU 1.1.0
SEGMENT SYNTAX: R0203
SITUATIONAL RULE: Required when REF01 = 0B to report the two character state ID of the state assigning the State License Number. If not required by this implementation guide, do not send.
INDUSTRY NAME: License Number State Code
See code source 22: State and Outlying Areas of the US.
Not Used
4
C040
Reference Identifier
O 1

N3 - SERVICE PROVIDER ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the provider has multiple locations to identify the specific location for this patient event. If not required by this implementation guide, do not send.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
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
FHIR Mapping: Practitioner.address[0].line[1] | Organization.address[0].line[1]
Implement with version: STU 1.0.0
INDUSTRY NAME: Service Provider Address Line
Use this element for the first line of the provider's address.
Situational
2
166
Address Information
O 1
AN
1/55
Address information
FHIR Mapping: Practitioner.address[0].line[2] | Organization.address[0].line[2]
Implement with version: STU 1.0.0
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 the provider has multiple locations to identify the specific location for this patient event. If not required by this implementation guide, do not send.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
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.
FHIR Mapping: Practitioner.address[0].city | Organization.address[0].city
Implement with version: STU 1.0.0
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.
FHIR Mapping: Practitioner.address[0].state | Organization.address[0].state
Implement with version: STU 1.0.0
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)
FHIR Mapping: Practitioner.address[0].postalCode | Organization.address[0].postalCode
Implement with version: STU 1.0.0
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
FHIR Mapping: Practitioner.address[0].country | Organization.address[0].country
Implement with version: STU 1.0.0
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
FHIR Mapping: Practitioner.address[0].district | Organization.address[0].district
Implement with version: STU 1.0.0
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.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
PER✱IC✱M TUCKER✱TE✱8185551212✱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
FHIR Mapping: 'IC'
Implement with version: STU 1.0.0
CODE
DEFINITION
IC
Information Contact
Situational
2
93
Name
O 1
AN
1/60
Free-form name
FHIR Mapping: no value when Practitioner | Organization.contact[0].name.text
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the Information Source needs to indicate a particular contact and the name of the entity to contact is not already defined or is different than the name within the prior name segment (NM1). If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Provider Contact Name
Situational
3
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
FHIR Mapping: Practitioner.telecom[0].system | Organization.contact[0].telecom[0].system
The value from the system attribute is translated as follows:
'phone' -> 'TE'
'fax' -> 'FX'
'email' -> 'EM'
'pager' -> 'TE'
'url' -> 'UR'
'sms' -> 'TE'
'other' -> cannot be translated
Implement with version: STU 1.0.0
SEGMENT SYNTAX: P0304
SITUATIONAL RULE: Required when PER02 is not valued or when the provider 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
FHIR Mapping: Practitioner.telecom[0].value | Organization.contact[0].telecom[0].valueIf the value of system is 'phone', this value must be parsed to determine if an extension is present (see ITU-T E.123 for format of telephone values). If an extension is present, the remove the extension part of the phone number and place in PER06 and set PER05 to 'EX'
Implement with version: STU 1.0.0
SEGMENT SYNTAX: P0304
SITUATIONAL RULE: Required when PER02 is not valued or when the provider 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
FHIR Mapping: Practitioner.telecom[1].system | Organization.contact[0].telecom[1].system | 'EX'
See PER04 if PER03 is 'TE' otherwise select the next telecom in contact[0] and translate the system as follows:
'phone' -> 'TE'
'fax' -> 'FX'
'email' -> 'EM'
'pager' -> 'TE'
'url' -> 'UR'
'sms' -> 'TE'
'other' -> cannot be translated
Implement with version: STU 1.0.0
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when the 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
FHIR Mapping: Practitioner.telecom[1].value | Organization.contact[0].telecom[1].value | extracted extension
If PER05 is set to 'EX' this will be the extract value for the extension from PER04
Otherwise this is refer to PER04 for rules on formatting
Implement with version: STU 1.0.0
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when the 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
FHIR Mapping: Practitioner.telecom[n].system | Organization.contact[0].telecom[n].system | 'EX'
See PER06 if PER05 is 'TE' otherwise select the next telecom in contact[0] and translate the system as follows:
'phone' -> 'TE'
'fax' -> 'FX'
'email' -> 'EM'
'pager' -> 'TE'
'url' -> 'UR'
'sms' -> 'TE'
'other' -> cannot be translated
Implement with version: STU 1.0.0
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when the 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
FHIR Mapping: Practitioner.telecom[n].value | Organization.contact[0].telecom[n].value | extracted extension
If PER07 is set to 'EX' this will be the extract value for the extension from PER06
Otherwise this is refer to PER04 for rules on formatting
Implement with version: STU 1.0.0
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when the telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Provider Contact Communication Number
Not Used
9
443
Contact Inquiry Reference
O 1
AN
1/20

PRV - SERVICE PROVIDER INFORMATION

X12 Name:
Provider Information
X12 Purpose:
To specify the identifying characteristics of a provider
X12 Syntax:
P0203
If either PRV02 or PRV03 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when request is for services of a specialist or specialty entity to indicate the provider's specialty. If not required by this implementation guide, may be provided a the sender's discretion but cannot be required by the receiver.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
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
FHIR Mapping: Claim.careTeam[n].role.coding[1].code
Implement with version: STU 1.0.0
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
FHIR Mapping: 'PXC'
Implement with version: STU 1.0.0
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
FHIR Mapping: Claim.careTeam[n].qualification.coding[0].code
Implement with version: STU 1.0.0
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

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
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile because the values are hardcoded or derived.
Implement with version: STU 1.0.0
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 - Request for Review and Response (005010X217)

AUGUST 2021

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

All rights reserved.

Abstract

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

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

1.1 Implementation Purpose and Scope

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

The purpose of this implementation guide is to provide standardized data requirements and content for all users who request authorizations or certifications or who respond to such requests using the 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 requests and responses. The intention of the developers of the 278 is represented in this guide.

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


1.2 Version Information

This implementation guide is based on the October 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 005010X217.

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 not intended to support use in real-time mode. A statement that the transaction is not intended to support a specific mode does not preclude its use in that mode between willing trading partners.


1.3.2 Other Usage Limitations

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

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

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

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

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

This subscriber/patient information is followed by at least one occurrence each of Loop 2000E and Loop 2000F representing one patient event and the associated services for this patient.


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 - Request and Response

This implementation guide covers the following business events:

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

Figure 1.1. Review Request and Response

Review Request and Response<

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

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

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

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

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

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

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

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

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


1.4.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. At the time of publication, these guides, and the business events they represent, are not covered under HIPAA.

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

This implementation guide supports the following categories of notifications.

Advance Notification for:

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

Completion Notification for:

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

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

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

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

Figure 1.2 - Notifications

Notifications

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

Figure 1.3 - Inquiry and Response

Inquiry and Response

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

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

1.5 Business Terminology

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

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:

  • Admission to a facility for treatment related to a specific patient condition or diagnosis or related group of diagnoses
  • Referral to a specialty provider for consultation or testing to determine a specific diagnosis and appropriate treatment
  • Services administered during a patient visit such as chiropractic treatment delivered in a single patient visit. The same treatment can be approved for a series of visits.

This implementation guide requires limiting each request to a single patient event.

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.

Medical Service Reservation
A health care service that is limited to a certain number of occurrences within a defined timeframe as specified by the Health Plan without authorization that is reserved by a specific provider.

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 recommendations of acknowledgment transactions may be used at the discretion of the trading partners. A statement that the acknowledgment is not required does not preclude its use between willing trading partners.


1.6.1 997 Functional Acknowledgment

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

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

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

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


1.6.2 999 Implementation Acknowledgment

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

The Implementation Acknowledgment (999) transaction is 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/nonhealth 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 Plan and Provider Enumeration System (NPPES) 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. In addition, some provider organizations may not have subparts.

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 request/response mode of operation. In this mode, a participant requests a certification and a review entity responds to that request. This implementation guide addresses that use. This section provides general information on the structure of the transaction set as represented in this implementation guide.

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


1.10.1 Overall Data Architecture

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

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

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

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

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 UMO (reviewer) and requesting provider respectively. Loop 2000C and Loop 2000D represent the subscriber and dependent. If the subscriber is the patient or if the patient has a unique identification number, only Loop 2000C is required. Loop 2000E carries information about the patient event and the provider(s) (referred-to providers) associated with this patient event. Loop 2000F carries information about specific services and the service provider(s) for those individual services.

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

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


1.11.2 Sample Table 2 Configurations

The following are sample Table 2 configurations.

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

UMO (Loop 2000A)

Requester (Loop 2000B)

Subscriber (Loop 2000C)

Dependent (Loop 2000D)

Patient Event (Loop 2000E)

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

UMO (Loop 2000A)

Requester (Loop 2000B)

Subscriber (Loop 2000C)

Dependent (Loop 2000D)

Patient Event (Loop 2000E)

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

UMO (Loop 2000A)

Requester (Loop 2000B)

Subscriber (Loop 2000C)

Patient Event (Loop 2000E)

Service (Loop 2000F)

Service (Loop 2000F)

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

UMO (Loop 2000A)

Requester (Loop 2000B)

Subscriber (Loop 2000C)

Patient Event (with Review Outcome Data) (Loop 2000E)

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

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

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


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

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

Table 1.1 - Intended Segment Use for a Request Transaction

Segment

Position

Segment

ID

UMO HL

Requester

HL

Subscriber

HL

Dependent

HL

Patient

Event HL

Service

HL

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

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

Table 1.2 - Intended Segment Use for a Response Transaction

Segment

Position

Segment

ID

UMO HL

Requester

HL

Subscriber

HL

Dependent

HL

Patient

Event HL

Service

HL

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

1.11.4 Matching the Request with Its Response

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

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

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

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

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

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

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

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

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

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

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


1.11.5 Transaction Responses

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

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


1.12 Data Use By Business Use

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

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

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


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

Figure 1.4 - Information Source and Receiver Levels

Information Source and Receiver Levels

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

Table 1.3 - HL Information Sources and Receivers

Transaction Use

HL

UMO

HL

Requester

Physical

Transmitter

Physical

Receiver

PCP Request for a Specialty Care Referral HMO PCP PCP HMO
Response to a Specialty Care Referral Request HMO PCP HMO PCP
Specialist Request for Admission Review HMO SCP SCP HMO
Response to a Specialist Request for Admission Review HMO SCP HMO SCP
Specialist Request for Admission Review PCP SCP SCP PCP
Response to a Specialist Request for Admission Review PCP SCP PCP SCP

* HMO - Health Maintenance Organization

* UMO - Utilization Management Organization

* PCP - Primary Care Provider

* SCP - Specialty Care Provider

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

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

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

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

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

HL*2*1*21*1~
NM1*1P*1******24*000012345~

1.12.2 Patient (Loop 2000C and Loop 2000D)

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

Figure 1.5 - Subscriber and Dependent Levels

Subscriber and Dependent Levels

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

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

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

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

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

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

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

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

Loop 2010C
Subscriber's Member ID

Loop 2010D
Dependent First Name
Dependent Last Name
Dependent Date of Birth

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

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

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

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

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


1.12.3 Patient Event (Loop 2000E)

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

Figure 1.6 - Patient Event Level

Patient Event Level

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

Loop 2000E (Patient Event)

Loop 2010EA (Patient Event Provider 1)

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

Loop 2000E (Patient Event)

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

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


1.12.3.1 Specialty Care Referrals

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

Initial Request

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Request for Extension
After a certification has been approved, a requester may need to extend the number of services originally requested based upon the patient's health status. The 278 supports a request to extend a service.

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

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

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

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

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

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

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

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

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

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

Request for Revision
In a request to revise a certification (UM02 = S), the requester is revising the specifics of a certification for services that have not been rendered. For example, the requester may be requesting additional procedures or other procedures for the same patient event. In a request to revise an existing certification (UM02 = S), if HSD is used, the value in HSD02 represents the new total.

HL*4*3*EV*0~
UM*SC*S~
REF*BB*0081096G~
HSD*VS*2~

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.3.2 Health Services Reviews

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

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

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

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

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

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

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

Example — Request for Spinal Manipulation Treatment
This is an example of a request for spinal manipulation services of the thoracic and lumbar section of the spine. It provides an example of the use of the CR2 segment. In this scenario, the chiropractor diagnosed the patient with a primary diagnosis of 847.2 (Lumbar sprain and strain) and two secondary diagnoses 728.85 (Muscle spasm) and 847.1 (Thoracic sprain and strain). The chiropractor is requesting 2 visits per week over a 3 month period. In addition, the chiropractor specifies that subluxation is necessary for Thoracic Eleven and Lumbar Five, of the spine. The chiropractor requests authorization for the following procedures: 98941 (Chiropractic manipulative treatment, spinal, 3-4 areas), 98943 (Chiropractic manipulative treatment, extraspinal, 1-2 regions) and 97124 (Therapeutic massage to one or more areas).

HI*BF:8472:D8:20020901*BF:72885:D8:20020901*BF:8471:D8:20020901~
HSD*VS*2*WK**34*3~
CR2***T11*L5****A*N***Y~

The HI segment provides the associated diagnosis information.

HI01-1 = BF (Diagnosis)
HI01-2 = 8472 (Lumbar sprain and strain)
HI01-3 = D8 (Date expressed as CCYYMMDD)
HI01-4 = 20020901 (Date diagnosed)
HI02-1 = BF (Diagnosis)
HI02-2 = 72885 (Muscle spasm)
HI02-3 = D8 (Date expressed as CCYYMMDD)
HI02-4 = 20020901 (Date diagnosed)
HI03-1 = BF (Diagnosis)
HI03-2 = 8471 (Thoracic sprain and strain)
HI03-3 = D8 (Date expressed as CCYYMMDD)
HI03-4 = 20020901 (Date diagnosed)

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

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

The CR2 Segment is used to express the subluxation levels.

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

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


1.12.3.3 Admission Review

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

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

HL*4*3*EV*0~
TRN*1*211099*9012345678~
UM*AR*I*2*21:B*****Y~
DTP*435*RD8:20020820-20020826~
HI*BJ:41090~
CL1*2~
NM1*FA*2*ABC MEMORIAL HOSPITAL*****24*765432100~

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

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

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

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

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

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


1.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 is required. If the 278 request does not include this loop, it must specify all the information pertaining to the category of services requested at the Patient Event level (Loop 2000E). As illustrated in Table 1.1 - Intended Segment Use for a Request Transaction and Table 1.2 - Intended Segment Use for a Response Transaction, many of the segments used in Loop 2000F are the same as those available in Loop 2000E. For a detailed explanation of their use, refer to Section 1.12.3 - Patient Event (Loop 2000E).

Figure 1.7 - Services Level

Figure 1.7 - Services Level

Guidelines for Using the Service Level

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

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

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

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

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

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

HL*4*3*EV*1~
UM*HS*I**11:B*****A~
HI*BK:7220*BF:7232~
HSD*VS*2*WK**34*3~
CR2***C1*C7****A*N***Y~
PWK*09*FX***AC*20020901001*Cervical x-ray demonstrates subluxation of cervical disc~
NM1*SJ*1******24*123456789~

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

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

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

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

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

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

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

HL*5*4*SS*0~
SV1*HC:98941~
HL*6*4*SS*0~
SV1*HC:98943~
HL*7*4*SS*0~
SV1*HC:97124~

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


(HCPCS/CPT for Chiropractic manipulative treatment, spinal, 3-4 areas) (HCPCS/CPT for Chiropractic manipulative treatment, extraspinal, 1-2 regions) (HCPCS/CPT for Therapeutic massage to one or more areas)

1.12.5 Additional Service Review Information (Loops 2000E and 2000F)

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


1.12.5.1 Referencing Additional Information on the 278 Request

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

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

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

Guidelines for Using the PWK Segment on the Request

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

1.12.5.2 Referencing Additional Information on the 278 Response

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

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

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

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

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

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

HCR*A4**0U~

Where:

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

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

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

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

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

Guidelines for Using the PWK Segments on the Response

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

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

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

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

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

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

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

Guidelines for Using HI Segments to Request Additional Information

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

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

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

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

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

Loop 2000F - First Service Loop

HI segment

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

SV1 segment

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

Loop 2000F - Second Service Loop

HI segment

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

SV1 segment

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

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

HI segment

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

SV1 segment

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

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

Loop 2000F - First Service Loop

HI segment

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

SV1 segment

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

Loop 2000F - Second Service Loop

HI segment

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

SV1 segment

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

Loop 2000F - Third Service Loop

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

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

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

Guidelines for Use of NM1 Loops

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

1.13 External References in this Guide

This implementation guide describes the intersection of X12 and Da Vinci data elements, so the information can be used consistently across implementations, regardless of syntax. Section 1.13, the FHIR mapping information provided in Section 2, and Appendices F and G are not part of the X12 EDI Standard or TR3 but are provided as a courtesy for organizations who are implementing multiple syntaxes.


1.13.1 The Da Vinci Project

Da Vinci is a private sector initiative, that addresses the needs of the Value Based Care Community by leveraging the Health Level 7 (HL7) Fast Healthcare Interoperability Resources (FHIR) platform. FHIR is an HL7 standard for exchanging healthcare information electronically. Da Vinci, an HL7 accelerator, and X12, an accredited Standards Developing Organization (SDO) have collaborated to produce materials to assist implementers in producing consistent electronic messaging.

Within this implementation guide are mapping instructions intended to inform implementers of the data relationships between the Da Vinci implementation guide and the X12 EDI Standard. These instructions delineate how the content maps between the FHIR exchange and the associated X12 segments and elements. The mapping appears in context in Section 2 of this implementation guide and as a standalone appendix.


1.13.1.1 The Da Vinci Prior Authorization Support Implementation Guide

The Da Vinci Project has developed a FHIR Implementation Guide titled Da Vinci Prior Authorization Support Implementation Guide (PAS). PAS provides a format to be used for creating a FHIR based message that contains the data necessary to create two X12 005010278 transactions and the X12 006020275. They are:

  • The 278 Health Care Services Review – Inquiry and Response
  • The 278 Health Care Services Review – Request and Response
  • The 275 Additional Information to Support a Health Care Services Review

X12 publishes detailed mappings specifically for use with the FHIR resource profiles contained within the Da Vinci PAS Implementation Guide for use by the industry. If subsequent changes are made to the Da Vinci PAS associated revisions may be applied to these mappings.


1.13.1.2 FHIR Resource Naming

FHIR naming methodology differs from the naming methodology of X12. To understand the mapping instructions provided an implementer must understand the following. A Bundle is the item exchanged between trading partners. The bundle contains a collection of resources that are composed of a set of structured data items as described by the name. One resource can be used for a variety of business purposes. The resource that includes the information needed for prior authorization and referrals (inquiry and request) is called Claim. ClaimResponse is the name of the resource used for a response to a prior authorization or referral inquiry or request.


1.13.1.3 FHIR Mapping Legend

The following conventions consistently describe the process of converting X12 messages from and to PAS compliant FHIR Resources.

  • The symbol '->' is used to show the translation of one value into another (code translation). This symbol should be read as 'becomes' or 'translates to'.
  • The symbol '=>' is used to follow the linkage from one FHIR resource to a related resource. This linkage traversal mechanism within a FHIR Bundle is described in the core FHIR Specification (v4.0.1) Section 2.36.4.1 Resolving References in Bundles. This symbol should be read as 'following reference to' or 'traversing reference'.
  • The symbol '|' is used when there are either multiple sources for the mapping or multiple destinations for the mapping. Mapping rules describe how to choose between the multiple sources or destinations. For example, a provider referenced on the Claim resource may be either a Practitioner resource or an Organization resource.
  • Single quotes "'" surround values that appear in codes and strings. These are fixed values (hard coded).
  • The values of true and false are not surrounded by single quotes as these are symbolic and the actual value used in implementations is dependent on technology (true may be 'T' or 't' or 'Y' or true).
  • Square brackets: '[' and ']'. Many of the elements in FHIR resources are arrays. An individual item from an array is indicated by a value enclosed in square brackets. For consistency, all array access is defined with a '0' base. So '[0]' is the first item in the array, '[1]' is the second item and '[n]' is an undetermined item within the array.
  • "out of scope": based on feedback to the Da Vinci Project PAS implementations will not include this information.
  • "no value - not populated from FHIR <resource-name>: there is no value in an attribute of the incoming FHIR Resource that can be used to populate the associated X12 attribute.
  • "no value - not populated for this use case": based on the use cases supported by PAS, this attribute is not expected to contain a value because the situation rule does not apply.
  • "not used on FHIR ClaimResponse": the outgoing FHIR ClaimResponse does not have an associated X12 element.
  • "cannot be populated into ClaimResponse at this time": there is a pending change request on the Da Vinci PAS FHIR profiles that will allow this attribute to be provided later.

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

This is an example of a standard Referral Request/Response sequence between a Primary Care Provider and a Utilization Management Organization. The example will show how a PCP can request a referral to a specialist for a patient from a UMO. The example will also show the response.

Joe Smith is a subscriber to Maryland Capital Insurance Company. During a regular physical, Dr. James Gardener, Joe's primary care physician, diagnoses a potential heart problem. Dr. Gardener determines that it would be best to refer Joe to Dr. Susan Watson, a cardiologist, for a consultation.

Dr. Gardener is required by Maryland Capital Insurance to submit a request for review seeking approval to refer Joe to Dr. Watson.

After review, Maryland Capital approves the referral and responds.


3.1.1 Request for Review

The following example represents the Request for Review (Specialty Care Referral) from Dr. Gardener to Maryland Capital Insurance.

Table 1

ST*278*0001*005010X217~

Begin transaction set 278, control #0001, and implementation convention reference is 005010X217.

BHT*0007*13*A12345*20050502*1101~

This transaction is a request using hierarchical structure 0007 (information source, information receiver, subscriber, dependent, event, services). The originating system has assigned the Submitter Transaction Identifier "A12345" along with the transaction set creation date and time.

Loop 2000A hierarchical level identifies the Insurance Company.

HL*1**20*1~

HL count is 1. There is no higher, or parent, HL. This HL code is 20, identifying the information source or the insurance company. This HL has subordinate levels, or children.

NM1*X3*2*MARYLAND CAPITAL INSURANCE COMPANY*****46*789312~

The request for a referral is being made to Maryland Capital Insurance Company. Their electronic transmitter identification number is 789312.

Loop 2000B hierarchical level identifies the submitting provider.

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*1P*1*GARDENER*JAMES****46*8189991234~

The request is being made by James Gardener whose Electronic Transmitter Identification Number is 8189991234.

Loop 2000C hierarchical level identifies the subscriber, who in this case is also the patient.

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 patient's name is Joe Smith; his Member Identification Number is 12345678901.

Loop 2000D hierarchical level identifies the dependent as a patient. Because there is no dependent in this example, there is no Loop 2000D.

Loop 2000E hierarchical level identifies the patient event.

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 patient event. This HL has no subordinate levels, or children.

TRN*1*111099*9012345678~

The provider assigned the trace number 111099 to this service request. The requester has included the user-assigned identifier of 012345678 to this trace number.

UM*SC*I*3*11:B*****Y~

Dr. Gardener is requesting an initial consultation for the patient.

HI*BF:41090:D8:20050430~

The patient has been diagnosed with acute myocardial infarction; unspecified site.

HSD*VS*1~

Dr. Gardener is requesting a single visit.

NM1*SJ*1*WATSON*SUSAN****34*987654321~

The patient event provider is identified as Susan Watson. Her Social Security Number is 987654321.

PER*IC**TE*4029993456~

Dr. Watson can be contacted by telephone at (402)999-3456.

SE*16*0001~

Number of segments, control number.


3.1.2 Response to the Request for Review

The following example represents the response to a request for review from Maryland Capital Insurance to Dr. Gardener.

In this case Maryland Capital Insurance has approved the referral request with no modifications.

Notice that the response transaction includes the detail of the request transaction to ensure for all parties exactly what is being approved. Notice that the insurance company has included a certification number for reference, AUTH0001. Also note the use of the DTP segment to specify the time period during which the referral is valid and the service is to be performed.

Table 1

ST*278*0001*005010X217~

Begin transaction set 278, control #0001, and implementation convention reference is 005010X217.

BHT*0007*11*A12345*20050502*1102*18~

This transaction is a response using hierarchical structure 0007 (information source, information receiver, subscriber, dependent, event, services). The UMO's system returns the Submitter Transaction Identifier "A12345". The BHT06 value of "18" indicates that this is a response with no further updates to follow.

Loop 2000A hierarchical level identifies the Insurance Company.

HL*1**20*1~

HL count is 1. There is no higher, or parent, HL. This HL code is 20, identifying the information source or the insurance company. This HL has subordinate levels, or children.

NM1*X3*2*MARYLAND CAPITAL INSURANCE COMPANY*****46*789312~

The response to the request for a referral is being made by Maryland Capital Insurance Company. Their electronic transmitter identification number is 789312.

Loop 2000B hierarchical level identifies the submitting provider.

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*1P*1*GARDENER*JAMES****46*8189991234~

The request is made by James Gardener whose Electronic Transmitter Identification Number is 8189991234.

Loop 2000C hierarchical level identifies the subscriber, who in this case is also the patient.

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 patient's name is Joe Smith; his Member Identification Number is 12345678901.

Loop 2000D hierarchical level identifies the dependent as a patient. Because there is no dependent in this example, there is no Loop 2000D.

Loop 2000E hierarchical level identifies the patient event.

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 patient event. This HL has no subordinate levels, or children.

TRN*2*111099*9012345678~

The UMO must return the trace number assigned by the provider to aid the provider in linking this response to the original request.

UM*SC*I*3*11:B~

Dr. Gardener requested an initial consultation for the patient with Dr. Watson at Dr. Watson's office.

HCR*A1*AUTH0001~

Maryland Capital approves the referral and provides a certification number.

DTP*AAH*RD8*20050502-20050602~

The insurance company indicates a date range during which the consultation or service can occur.

HI*BF:41090:D8:20050430~

The patient has been diagnosed with acute myocardial infarction; unspecified site.

HSD*VS*1~

Dr. Gardener is requesting a single visit.

NM1*SJ*1*WATSON*SUSAN****34*987654321~

The patient event provider is identified as Susan Watson. Her Social Security Number is 987654321.

PER*IC**TE*4029993456~

Dr. Watson can be contacted by telephone at (402)999-3456.

SE*18*0001~

Number of segments, control number.


3.2 Business Scenario 2 - Admission for Surgery

This is an example of a health services review request/response sequence between a specialist provider and a utilization management organization. The example shows how a specialist can request hospitalization for a patient from a UMO. The example also shows the UMO's response.

Joe Smith is a subscriber to Maryland Capital Insurance Company. During a regular physical, Dr. James Gardener, Joe's primary care physician, diagnosed a potential heart problem, acute myocardial infarction; unspecified site. Dr. Gardener had referred Joe to Dr. Susan Watson, a cardiologist for a consultation (see Business Scenario 1).

During the consultation examination, Dr. Watson determines that Joe's diagnosis requires hospitalization and a surgical procedure, a triple bypass venous graft. The operation and recovery is to be at Montgomery Hospital.

Dr. Watson is required by Maryland Capital Insurance to submit a request for review seeking approval to perform the surgery at the hospital.

After review, Maryland Capital approves the request and responds.


3.2.1 Request for Review

The following example represents the request for review (Health Services Review) from Dr. Watson to Maryland Capital Insurance.

Table 1

ST*278*0001*005010X217~

Begin transaction set 278, control #0001, and implementation convention reference is 005010X217.

BHT*0007*13*B56789*20050502*1430~

This transaction is a request using hierarchical structure 0007 (information source, information receiver, subscriber, dependent, event, services). The originating system has assigned the Submitter Transaction Identifier "B56789" along with the transaction set creation date and time.

Loop 2000A hierarchical level identifies the insurance company.

HL*1**20*1~

HL count is 1. There is no higher, or parent, HL. This HL code is 20, identifying the information source or the insurance company. This HL has subordinate levels, or children.

NM1*X3*2*MARYLAND CAPITAL INSURANCE COMPANY*****46*789312~

The request for a health service review and an admission review is being made to Maryland Capital Insurance Company. Their electronic transmitter identification number is 789312.

Loop 2000B hierarchical level identifies the submitting provider.

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*1P*1*WATSON*SUSAN****34*98765432~

The request is being made by Susan Watson whose Social Security Number is 98765432.

PER*IC**TE*4029993456~

Dr. Watson can be contacted by telephone at (402)999-3456.

Loop 2000C hierarchical level identifies the subscriber, who in this case is also the patient.

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 patient's name is Joe Smith; his Member Identification Number is 12345678901.

Loop 2000D hierarchical level identifies the dependent as a patient. Because there is no dependent in this example, there is no Loop 2000D.

Loop 2000E hierarchical level identifies the patient event.

HL*4*3*EV*1~

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

TRN*1*97021001*9012345678~

The provider assigned the trace number of 97021001 to this patient event request. The requester has included the user-assigned identifier of 012345678 to this trace number.

UM*AR*I*2*21:B*****Y~

Dr. Watson is requesting an admission review for the patient at an inpatient hospital setting.

DTP*435*D8*20050516~

Dr. Watson requests an admission date of May 16, 2005.

HI*BF:41090:D8:20050125~

The patient has been diagnosed with acute myocardial infarction; unspecified site.

HSD*DY*7~

Dr. Watson has requested certification for a length of stay of seven days.

CL1*2~

Dr. Watson indicates that the inpatient admission type is "urgent".

NM1*FA*2*MONTGOMERY HOSPITAL*****24*000012121~

The admitting facility is identified as Montgomery Hospital. The Employer's Identification Number is 000012121.

N3*475 MAIN STREET~

Montgomery Hospital street address.

N4*ANYTOWN*PA*19087~

Montgomery Hospital city, state, ZIP Code.

Loop 2000F hierarchical level identifies the services. Loop 2000F repeats for each service to be performed at Montgomery Hospital for which authorization is requested.

HL*5*4*SS*0~

HL count is 5. This HL is subordinate to HL*4, the parent HL. This HL code is SS, identifying the service. This HL has no subordinate levels, or children.

UM*HS*I*2~

Dr. Watson is requesting an initial health service review for surgery for the patient.

DTP*472*D8*20050516~

Dr. Watson is requesting permission to perform a triple bypass venous graft (CPT) on May 16, 2005.

SV2**HC:33510~

Dr. Watson is requesting permission to perform a triple bypass venous graft (CPT).

NM1*SJ*1*WATSON*SUSAN****34*987654321~

The service provider, the surgeon, is identified as Susan Watson. Her Social Security Number is 987654321.

PRV*PE*PXC*203BS0133X~

This segment identifies Dr. Watson's specialty, thoracic cardiovascular surgery.

SE*26*0001~

Number of segments, control number.


3.2.2 Response to the Request for Review

The following example represents the response to a request for review (health services review and hospital admission) from Maryland Capital Insurance to Dr. Watson.

In this case Maryland Capital Insurance is approving the request for surgery but partially approving the request for inpatient confinement.

Notice that the response transaction includes the detail of the request transaction to insure for all parties exactly what is being approved. Notice that the insurance company has included a certification number for reference, AUTH0002, for both services. The insurance company has the option of treating this as either one or two certifications.

Table 1

ST*278*0001*005010X217~

Begin transaction set 278, control #0001, and implementation convention reference is 005010X217.

BHT*0007*11*B56789*20050502*1431*18~

This transaction is a response using hierarchical structure 0007 (information source, information receiver, subscriber, dependent, event, services). The UMO's system returns the Submitter Transaction Identifier "B56789". The BHT06 value of "18" indicates that this is a response with no further updates to follow.

Loop 2000A hierarchical level identifies the insurance company.

HL*1**20*1~

HL count is 1. There is no higher, or parent, HL. This HL code is 20, identifying the information source or the insurance company. This HL has subordinate levels, or children.

NM1*X3*2*MARYLAND CAPITAL INSURANCE COMPANY*****46*789312~

The response to the request for admission review and health services review is being made by Maryland Capital Insurance Company. Their electronic transmitter identification number is 789312.

Loop 2000B hierarchical level identifies the submitting provider.

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*1P*1*WATSON*SUSAN****34*987654321~

The request is being made by Susan Watson whose Social Security Number is 987654321.

Loop 2000C hierarchical level identifies the subscriber, who in this case is also the patient.

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 patient's name is Joe Smith; his Member Identification Number is 12345678901.

Loop 2000D hierarchical level identifies the dependent as a patient. Because there is no dependent in this example, there is no Loop 2000D.

Loop 2000E hierarchical level identifies the patient event.

HL*4*3*EV*1~

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

TRN*2*97021001*9012345678~

The UMO must return the trace number assigned by the provider to aid the provider in linking this service response to the original service request.

UM*AR*I*2*21:B~

Dr. Watson requested an admission review for the patient at an inpatient hospital setting.

HCR*A6*AUTH0002~

Maryland Capital has approved the inpatient stay but has approved a modification from the initial request.

DTP*435*D8*20050516~

Maryland Capital has approved the admission date of May 16, 2005.

HI*BF:41090:D8:20050125~

The patient has been diagnosed with acute myocardial infarction; unspecified site.

HSD*DY*5~

Dr. Watson requested certification for a length of stay of seven days. The UMO has certified a length of stay of five days.

NM1*FA*2*MONTGOMERY HOSPITAL*****24*000012121~

The admitting facility is identified as Montgomery Hospital. The Employer's Identification Number is 000012121.

N3*475 MAIN STREET~

Montgomery Hospital street address.

N4*ANYTOWN*PA*19087~

Montgomery Hospital city, state, ZIP Code.

Loop 2000F hierarchical level identifies the services. Loop 2000F repeats for each service to be performed at Montgomery Hospital for which authorization is requested.

HL*5*4*SS*0~

HL count is 5. This HL is subordinate to HL*4, the parent HL. This HL code is SS, identifying the service. This HL has no subordinate levels, or children.

UM*HS*I*2~

Dr. Watson is requesting an initial health service review for surgery for the patient.

HCR*A1*AUTH0002~

Maryland Capital Insurance Company has approved the surgery in full and assigned the same certification number AUTH0002.

DTP*472*D8*20050516~

Dr. Watson requested permission to perform the procedure on May 16, 20.

SV2**HC:33510~

Dr. Watson is requesting permission to perform a triple bypass venous graft (CPT).

NM1*SJ*1*WATSON*SUSAN****34*987654321~

The service provider, the surgeon, is identified as Susan Watson. Her Social Security Number is 987654321.

PRV*PE*PXC*203BS0133X~

This segment identifies Dr. Watson's specialty, thoracic cardiovascular surgery.

SE*26*0001~

Number of segments, control number.

NOTE
The CL1 segment is returned on the response only if it was valued on the request and used by the UMO when rendering a decision.


3.3 Business Scenario 3 - Request for Behavioral Health Emergency Admission

This is an example of admission for behavioral health care. Mary Smith is a subscriber to the Capital Insurance Company and presents at the General Hospital emergency room. Dr. Marcus Jones, the attending physician, evaluates Mary and decides to admit Mary to the Inpatient Psychiatric unit at General Hospital. The preliminary diagnosis is 296.03, Bipolar I Disorder, Single Manic Episode, Severe without Psychotic Features. Dr. Jones recommends 3 days of inpatient treatment, under the care of Dr. Jacob Brown. The registration clerk determines that Capital Insurance requires pre-certification of care and submits a request for an admission to the hospital.


3.3.1 Request for Review

The following example represents the Request for Review (Admission Review).

Table 1

ST*278*0001*005010X217~

Begin transaction set 278, control #0001, and implementation convention reference is 005010X217.

BHT*0007*13*YZZ345*20050502*1101~

This transaction is a request using hierarchical structure 0007 (information source, information receiver, subscriber, dependent, event, services). The originating system has assigned the Submitter Transaction Identifier "YZZ345" along with the transaction set creation date and time.

Loop 2000A hierarchical level identifies the Utilization Management Company.

HL*1**20*1~

HL count is 1. There is no higher, or parent, HL. This HL code is 20, identifying the information source or the insurance company. This HL has subordinate levels, or children.

NM1*X3*2*MARYLAND CAPITAL INSURANCE COMPANY*****46*789312~

The request for a referral is being made to Capital Insurance Company. Their electronic transmitter identification number is 789312.

Loop 2000B hierarchical level identifies the Information Requester.

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 requesting provider. This HL has subordinate levels, or children.

NM1*FA*2*GENERAL HOSPITAL*****46*8189991234~

The request is being made by General Hospital whose Electronic Transmitter Identification Number is 8189991234.

Loop 2000C hierarchical level identifies the subscriber, who in this case is also the patient.

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*MARY****MI*12345678901~

The patient's name is Mary Smith; her Member Identification Number is 12345678901.

Loop 2000D hierarchical level identifies the dependent as a patient. Because there is no dependent in this example, there is no Loop 2000D.

Loop 2000E hierarchical level identifies the patient event level.

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 patient event. This HL has no subordinate levels, or children.

TRN*1*YZZ099*987654321~

The requester's system assigned the trace number YZZ099 to this service request.

UM*AR*I*A4*21:B**03***Y~

Dr. Jones is requesting an initial emergency psychiatric admission for the patient.

DTP*435*D8*20050505~

Admit Date

HI*BF:29603:D8:20050430~

The patient has been diagnosed with Bipolar I Disorder, Single Manic Episode, Severe Without Psychotic Features (296.03).

HSD*DY*3~

Dr. Jones has requested a stay of 3 days.

CL1*1~

Admission type is New.

Loop 2010E identifies the providers associated with this the patient event.

NM1*FA*2*GENERAL HOSPITAL*****46*987654321~

The admitting facility is identified as General Hospital. The ETIN Number is 987654321.

PER*IC**TE*4029993456~

The hospital can be contacted by telephone at (402)999-3456.

NM1*71*1*JONES*MARCUS****24*453667654~

Dr Marcus Jones is the attending physician.

NM1*SJ*1*BROWN*JACOB****24*123454545~

Dr. Jacob Brown will be responsible for Mary's care for this inpatient stay.

NM1*SJ*1*WATSON*SUSAN****34*987654321~

The service provider, the surgeon, is identified as Susan Watson. Her Social Security Number is 987654321.

SE*20*0001~

Number of segments. Control number.


3.3.2 Response to the Request for Review

The following example represents the response to a request for review from Capital Insurance to General Hospital. In this case, Capital Insurance has pended the admission request for an admission summary to be delivered by telephone. Notice that the response transaction includes the detail of the request transaction to ensure for all parties exactly what is pended.

Table 1

ST*278*0001*005010X217~

Begin transaction set 278, control #0001, and implementation convention reference is 005010X217.

BHT*0007*11*YZZ345*20050502*1102*19~

This transaction is a response using hierarchical structure 0007 (information source, information receiver, subscriber, dependent, event, services). The UMO's system returns the Submitter Transaction Identifier "YZZ345". The BHT06 value of "19" indicates that this is a response with further updates to follow.

Loop 2000A hierarchical level identifies the Utilization Management Organization.

HL*1**20*1~

HL count is 1. There is no higher, or parent, HL. This HL code is 20, identifying the information source or the insurance company. This HL has subordinate levels, or children.

NM1*X3*2*CAPITAL INSURANCE COMPANY*****46*789312~

The response to the request for an admission is being made by Capital Insurance Company. Their electronic transmitter identification number is 789312.

PER*IC**TE*3936533000~

The payer can be contacted by telephone at (393) 653-3000.

Loop 2000B hierarchical level identifies 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 requesting provider. This HL has subordinate levels, or children.

NM1*FA*2*GENERAL HOSPITAL****46*8189991234~

The request is made by General Hospital whose Electronic Transmitter Identification Number is 8189991234.

Loop 2000C hierarchical level identifies the subscriber, who in this case is also the patient.

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*MARY****MI*12345678901~

The patient's name is Joe Smith; his Member Identification Number is 12345678901.

Loop 2000D hierarchical level identifies the dependent as a patient. Because there is no dependent in this example, there is no Loop 2000D.

Loop 2000E hierarchical level is the patient event level.

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 patient event. This HL has no subordinate levels, or children.

TRN*2*YZZ099*987654321~

The UMO must return the trace number sent on the request to aid the provider in linking this response to the original request.

UM*AR*I*A4*21:B**03~

Dr. Jones submitted an initial request emergency psychiatric admission for the patient.

HCR*A4**0U~

Disposition is pending review.

REF*NT*P20030216001~

The UMO has assigned an administrative reference number to the review. The provider can use this number to reference this UMO response on subsequent inquiries associated with this pended health care services review.

HI*BF:29603:D8:20050429~

The patient has been diagnosed with Bipolar I Disorder, Single Manic Episode, Severe Without Psychotic Features (296.03).

PWK*AS*VO~

Capital Insurance Company has requested an admission summary by voice.

NM1*FA*2*GENERAL HOSPITAL*****46*987654321~

The admitting facility is General Hospital. Its ETIN Number is 987654321.

NM1*71*1*JONES*MARCUS****24*453667654~

Dr. Marcus Jones is the attending physician.

NM1*SJ*1*BROWN*JACOB****24*123454545~

Dr. Jacob Brown will be responsible for Mary's care for this inpatient stay.

SE*20*0001~

Number of segments, control number.


3.4 Business Scenario 4 - Request for Home Health Care

This is an example of a home health care provider's request to provide home health care services. In this example, the patient's diagnoses are: 183.1 (Ovarian Cancer - Malignant neoplasm of ovary) and 263.0 (Malnutrition of moderate degree). The procedures requested include: G0154 (Services of skilled nurse in home care setting) and B4184 (Parenteral nutrition - 10% lipids). The patient will receive the parenteral nutrition services over a 2 month period delivered 3 times per week. This section describes the composition of the Patient Event level Loop 2000E and the Service level Loop 2000F of the request. Refer to the previous business scenarios for examples of valuing Loops 2000A, B, and C and the 278 response.


3.4.1 Patient Event Level - Loop 2000E

Loop 2000E hierarchical level identifies the patient event level.

HL*4*3*EV*1~

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

UM*HS*I**12:B*****Y~

This is an initial request for home care. Appropriate release of information is on file at the health service provider or at the utilization review organization.

HI*BF:1831*BF:2630~

The patient has been diagnosed with ovarian cancer - malignant neoplasm of ovary and malnutrition of moderate degree.

HSD*VS*3*WK**34*2~

The patient will receive services over a 2 month period delivered 3 times per week.

CR6*1*20050502*RD8*20050502-20050801***W*I~

The patient's prognosis is poor. The requested home health care is scheduled to begin on May, 2005 and extend to August 1, 2005. The patient is not in a skilled nursing facility and not on Medicare.

NM1*SJ*2*CARING HANDS HOME HEALTH AGENCY*****24*345678912~

Caring Hands Home Health Agency will provide the care.


3.4.2 Service Level - Loop 2000F

This loop allows the provider to request authorization for specific procedure codes. In this example, the request includes 2 procedure codes identified below. Therefore, the request includes 2 occurrences of Service level Loop 2000F.

Loop 2000F hierarchical level identifies the service level. Loop 2000F repeats for each service.

HL*5*4*SS*0~

HL count is 5. This HL is subordinate to HL*4, the parent HL. This HL code is SS, identifying the service. This HL has no subordinate levels, or children.

SV1*HC:G0154~

HCPCS/CPT for Services of skilled nurse in home care setting.

HL*6*4*SS*0~

HL count is 6. This HL is subordinate to HL*4, the parent HL. This HL code is SS, identifying the service. This HL has no subordinate levels, or children.

SV1*HC:B4184~

HCPCS/CPT for Parenteral nutrition - 10% lipids.


3.5 Business Scenario 5 - Request for Non-emergency Transportation Service (Multi-destination Trip)

This is an example of a Health Care Services Review Request and Response between an ambulance service provider and a payer or Utilization Management Organization. The example will show how a provider can request a multi-destination non-emergency transportation service. The example will also show the response.

Joe Smith is a subscriber to ABC Payer. ABC Ambulance Service has been notified that they will be providing a multi-destination non-emergency transportation service to Mr. Smith, where the patient will be transported from home, to his physician's office, to a dialysis center for treatment, then back home again.

ABC Ambulance Service is required to submit a request for approval of these non-emergency services showing each leg of the multi-destination trip and their association pick-up and drop-off locations prior to the service being provided to the patient.

After review, ABC Payer has approved this multi-destination non-emergency transportation trip and responds.


3.5.1 Request for Non-emergency Transportation

The following example represents a request for a non-emergency transportation service from Dr. Gardner to ABC Payer.

Table 1

ST*278*0001*005010X217~

Begin transaction set 278, control #0001, and implementation convention reference is 005010X217.

BHT*0007*13*165932*20050502*1525~

This transaction is a Health Care Services Review request for non-emergency transportation services using hierarchical structure 0007 (information source, information receiver, subscriber, dependent, event, services). The originating system has assigned the Submitter Transaction Identifier 165932 along with the transaction creation date and time.

Loop 2000A hierarchical level identifies the Insurance Company, UMO or Health Plan.

HL*1**20*1~

HL count is 1. There is no higher or parent HL. This HL code is 20, identifying the information source or the insurance company. This HL has subordinate levels, or children.

NM1*X3*2*ABC PAYER*****PI*1234560010~

The request for review for the non-emergency transportation services is made to ABC Payer. Their Electronic Transmitter Identification Number is 1234560010.

Loop 2000B hierarchical level identifies the submitting provider.

HL*2*1*21*1~

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

NM1*1P*1*XYZ AMBULANCE SVC*****24*7759621873~

The request is being made by XYZ Ambulance Svc whose Employer's Identification Number is 7759621873.

Loop 2000C hierarchical level identifies the subscriber, who in this case is also the patient.

HL*3*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*12345689001~

The patient's name is Joe Smith; his Member Identification Number is 12345689001.

REF*EJ*6532214A76~

The Patient Account Number for Joe Smith is 6532214A76.

DMG*D8*19580322*M~

The patient's date of birth is March 22, 1958.

Loop 2000D hierarchical level identifies the dependent as a patient. Because there is no dependent in this example, there is no Loop 2000D.

Loop 2000E hierarchical level identifies the patient event.

HL*4*3*EV*1~

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

UM*HS*I*56*41:B~

Dr. Gardner is requesting review and approval a multi-destination non-emergency transportation service for the patient. The Place of Service is 41 (Ambulance).

DTP*AAH*D8*20050510~

The date of this event is May 10, 2005.

CRC*07*Y*09~

The transportation conditions identified that the Ambulance was medically necessary (09).

CR1***X*D*DH*27***TRIP FROM HOME TO OFFICE VISIT TO DIALYSIS TREATMENT AND BACK HOME~

This multi-destination round trip is for a total of 27 miles. The trip is from the patient's home, to an office visit, to a dialysis center for treatment, then back home again.

NM1*PW*2*HOME~

This identifies the pick-up destination is the patient's home.

N3*8652 Starwood Lane~

The patient's home address is 8652 Starwood Lane.

N4*SACRAMENTO*CA*95826~

The patient's city, state and zip code are Sacramento, CA 95826.

NM1*ND*2*DR. GARDNER OFFICE~

This identifies the first stop in the multi-destination trip, Dr. Gardner's office.

N3*1921 FULTON AVENUE~

The address of the patient's physician office is 1921 Fulton Avenue.

N4*SACRAMENTO*CA*95624~

The city, state and zip code of the patient's physician office are Sacramento, CA 95624.

NM1*R3*2*XYZ DIALYSIS CENTER~

This is the second stop in the multi-destination trip, the XYZ Dialysis Center.

N3*7622 MORSETOWN ROAD~

The address of the dialysis center is 7622 Morsetown Road.

N4*SACRAMENTO*CA*95826~

The city, state and zip code of the dialysis center are Sacramento, CA 95826.

NM1*FS*2*HOME~

This is the final destination in the multi-destination trip, back to the patient's home.

N3*8652 STARWOOD LANE~

The patient's address is 8652 Starwood Lane.

N4*SACRAMENTO*CA*95826~

The patient's city, state and zip code are Sacramento, CA 95826.

Loop 2000F hierarchical level identifies the services associated with this event.

HL*5*4*SS*0~

HL count is 5. This HL is subordinate to HL *4, the parent HL. This HL code is SS, identifying the specific services associated to this request. This HL has no subordinate levels, or children.

SV1*HC:A0428:RX**UN*5~

The ambulance company is requesting review and approval of procedure code A0428 for the first leg of the trip (home to physician office) for a total of 5 miles.

Repeat of Loop 2000F hierarchical level identifies the services associated with this event.

HL*6*5*SS*0~

HL count is 6. This HL is subordinate to HL *5, the parent HL. This HL code is SS, identifying the specific services associated to this request. This HL has no subordinate levels, or children.

SV1*HC:A0428:PD**UN*8~

The ambulance company is requesting review and approval of procedure code A0428 for the second leg (physician office to dialysis center) of the trip for a total of 8 miles.

Repeat of Loop 2000F hierarchical level identifies the services associated with this event.

HL*7*6*SS*0~

HL count is 7. This HL is subordinate to HL *6, the parent HL. This HL code is SS, identifying the specific services associated to this request. This HL has no subordinate levels, or children.

SV1*HC:A0428:DR**UN*14~

The ambulance company is requesting review and approval of procedure code A0428 for the final leg of the trip (dialysis center to home) for a total of 14 miles. The total trip equals 27 miles.

SE*34*0001~

Number of segments, control number.


3.5.2 Response to Non-emergency Transportation

The following example represents the response non-emergency transportation service from ABC Payer to Dr. Gardner.

Table 1

ST*278*0001*005010X217~

Begin transaction set 278, control #0001, and implementation convention reference is 005010X217.

BHT*0007*11*165932*20055002*0815*18~

This transaction is a Health Care Services Review request for non-emergency transportation services using hierarchical structure 0007 (information source, information receiver, subscriber, dependent, event, services). The originating system has assigned the Submitter Transaction Identifier 165932 along with the transaction creation date and time. The BHT06 value of "18" indicates that this is the final EDI reponse.

Loop 2000A hierarchical level identifies the Insurance Company, UMO or Health Plan.

HL*1**20*1~

HL count is 1. There is no higher or parent HL. This HL code is 20, identifying the information source or the insurance company. This HL has subordinate levels, or children.

NM1*X3*2*ABC PAYER*****PI*1234560010~

The response for review for the non-emergency transportation services is made by ABC Payer. Their Electronic Transmitter Identification Number is 1234560010.

Loop 2000B hierarchical level identifies the submitting provider.

HL*2*1*21*1~

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

NM1*1P*1*XYZ AMBULANCE SVC*****24*7759621873~

The response is being sent to XYZ Ambulance Service whose Employer's Identification Number is 7759621873.

Loop 2000C hierarchical level identifies the subscriber, who in this case is also the patient.

HL*3*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*12345689001~

The patient's name is Joe Smith; his Member Identification Number is 12345689001.

REF*EJ*6532214A76~

The Patient Account Number for Joe Smith is 6532214A76.

DMG*D8*19580322*M~

The patient's date of birth is March 22, 1958.

Loop 2000D hierarchical level identifies the dependent as a patient. Because there is no dependent in this example, there is no Loop 2000D.

Loop 2000E hierarchical level identifies the patient event.

HL*4*3*EV*1~

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

UM*HS*I*56*41:B~

The response is for approval of the multi-destination non-emergency transportation service submitted by XYZ Ambulance Services for the patient. The Place of Service is 41 (ambulance).

HCR*A1*2005010796321~

The health plan/UMO is giving total certification of these services with a certification/approval number of 2005010796321.

DTP*AAH*D8*20050510~

The date of this even is May 10, 2005.

CR1***X**DH*27~

This multi-destination round trip was for a total of 27 miles.

NM1*PW*2*HOME~

This identifies the pick-up destination is the patient's home.

N3*8652 STARWOOD LANE~

The patient's home address is 8652 Starwood Lane.

N4*SACRAMENTO*CA*95826~

The patient's city, state and zip code are Sacramento, CA 95826.

NM1*ND*2*DR. GARDNER OFFICE~

This identifies the first stop in the multi-destination trip, Dr. Gardner's office.

N3*1921 FULTON AVENUE~

The address of the patient's physician office is 1921 Fulton Avenue.

N4*SACRAMENTO*CA*95624~

The city, state and zip code of the patient's physician office are Sacramento, CA 95624.

NM1*R3*2*XYZ DIALYSIS CENTER~

This is the second stop in the multi-destination trip, the XYZ Dialysis Center.

N3*7622 MORSETOWN ROAD~

The address of the dialysis center is 7622 Morsetown Road.

N4*SACRAMENTO*CA*95826~

The city, state and zip code of the dialysis center are Sacramento, CA 95826.

NM1*FS*2*HOME~

This is the final destination in the multi-destination trip, back to the patient's home.

N3*8652 STARWOOD LANE~

The patient's address is 8652 Starwood Lane.

N4*SACRAMENTO*CA*95826~

The patient's city, state and zip code are Sacramento, CA 95826.

Loop 2000F hierarchical level identifies the services associated with this event.

HL*5*4*SS*0~

HL count is 5. This HL is subordinate to HL *4, the parent HL. This HL code is SS, identifying the specific services associated to this request. This HL has no subordinate levels, or children.

SV1*HC:A0428:RX**UN*5~

The payer is approving procedure code A0428 with modifier RX for a total of 5 units.

Loop 2000F hierarchical level identifies the services associated with this event.

HL*6*4*SS*0~

HL count is 6. This HL is subordinate to HL *4, the parent HL. This HL code is SS, identifying the specific services associated to this request. This HL has no subordinate levels, or children.

SV1*HC:A0428:PD**UN*8~

The payer is approving procedure code A0428 with modifier PD for a total of 8 units.

Loop 2000F hierarchical level identifies the services associated with this event.

HL*7*4*SS*0~

HL count is 7. This HL is subordinate to HL *4, the parent HL. This HL code is SS, identifying the specific services associated to this request. This HL has no subordinate levels, or children.

SV1*HC:A0428:DR**UN*14~

The payer is approving procedure code A0428 with modifier DR for a total of 14 units.

SE*34*0001~

Number of segments, control number.


3.6 Business Scenario 6 - Medical Services Reservation

This is an example of a Medical Services Reservation request and response between a payer and a primary care physician. The example will show how a physician can reserve a medical service for a patient from a payer and the example will also show the response from the payer.

Joe Smith is a subscriber to ABC Payer. Dr. James Gardner is expecting to perform a service on Joe Smith in the near future and is required to reserve this service with the payer. The procedure code is 99212 and the unit count being reserved is 1.

ABC Payer accepts the medical reservation request and responds.


3.6.1 Request for Medical Services Reservation

The following example represents a request for a Medical Services Reservation from Dr. Gardner to ABC Payer.

Table 1

ST*278*0001*005010X217~

Begin transaction set 278, control #0001, and implementation convention reference is 005010X217.

BHT*0007*36*5269367*20050502*2243*RU~

This transaction is a Medical Services Reservation request using hierarchical structure 0007 (information source, information receiver, subscriber, dependent, event, services). The originating system has assigned the Submitter Transaction Identifier 5269367 along with the transaction creation date and time.

Loop 2000A hierarchical level identifies the Insurance Company, UMO or Health Plan.

HL*1**20*1~

HL count is 1. There is no higher or parent HL. This HL code is 20, identifying the information source or the insurance company. This HL has subordinate levels, or children.

NM1*X3*2*ABC PAYER*****PI*1234560010~

The request for the Medical Services Reservation is being made to ABC Payer. Their Electronic Transmitter Identification Number is 1234560010.

Loop 2000B hierarchical level identifies the submitting provider.

HL*2*1*21*1~

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

NM1*1P*1*GARDNER*JAMES****24*0010102364~

The request is being made by James Gardner whose Employer's Identification Number is 0010102364.

Loop 2000C hierarchical level identifies the subscriber, who in this case is also the patient.

HL*3*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*12345689001~

The patient's name is Joe Smith; his Member Identification Number is 12345689001.

DMG*D8*19580322*M~

The patient's date of birth is March 22, 1958.

Loop 2000D hierarchical level identifies the dependent as a patient. Because there is no dependent in this example, there is no Loop 2000D.

Loop 2000E hierarchical level identifies the patient event.

HL*4*3*EV*1~

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

UM*IN*I*1*11:B~

Dr. Gardner is requesting an Initial Medical Services Reservation for a Medical Care service with a Place of Service of 11 (Office) for the patient.

Loop 2000F hierarchical level identifies the services associated with this event.

HL*5*4*SS*0~

HL count is 5. This HL is subordinate to HL *4, the parent HL. This HL code is SS, identifying the specific services associated to this request. This HL has no subordinate levels, or children.

DTP*472*D8*20050510~

The proposed date for the service reservation is May 10, 2005.

SV1*HC:99212**UN*1~

Dr. Gardner is requesting a Medical Services Reservation for procedure code 99212, unit count 1.

SE*15*0001~

Number of segments, control number.


3.6.2 Response to Medical Services Reservation

The following example represents the response to the Medical Service Reservation from ABC Payer to Dr. Gardner.

In this case ABC Payer has accepted a reservation for patient Joe Smith for procedure code 99212. The unit count requested and accepted is 1. The remaining medical services on file with ABC Payer is 2.

Table 1

ST*278*0001*005010X217~

Begin transaction set 278, control #0001, and implementation convention reference is 005010X217.

BHT*0007*11*5269367*20050502*0859*RU~

This transaction is a Medical Services Reservation response using hierarchical structure 0007 (information source, information receiver, subscriber, dependent, event, services). The originating system has assigned the Submitter Transaction Identifier 5269367 along with the transaction creation date and time.

Loop 2000A hierarchical level identifies the Insurance Company.

HL*1**20*1~

HL count is 1. There is no higher or parent HL. This HL code is 20, identifying the information source or the insurance company. This HL has subordinate levels, or children.

NM1*X3*2*ABC PAYER*****PI*1234560010~

The response for the Medical Services Reservation is being made by ABC Payer. Their Electronic Transmitter Identification Number is 1234560010.

Loop 2000B hierarchical level identifies the submitting provider.

HL*2*1*21*1~

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

NM1*1P*1*GARDNER*JAMES****24*0010102364~

The response is being sent to James Gardner whose Employer's Identification Number is 0010102364.

Loop 2000C hierarchical level identifies the subscriber, who in this case is also the patient.

HL*3*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*12345689001~

The patient's name is Joe Smith; his Member Identification Number is 12345689001.

DMG*D8*19580322*M~

The patient's date of birth is March 22, 1958.

Loop 2000D hierarchical level identifies the dependent as a patient. Because there is no dependent in this example, there is no Loop 2000D.

Loop 2000E hierarchical level identifies the patient event.

HL*4*3*EV*1~

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

UM*IN*I*1*11:B~

This identifies that this is a Medical Services Reservation for a Medical Care service with a Place of Service of 11 (office).

HCR*A1*6735172961~

This service was certified in total with a confirmation or certification number of 6735172961.

Loop 2000F hierarchical level identifies the services associated with this event.

HL*5*4*SS*0~

HL count is 5. This HL is subordinate to HL *4, the parent HL. This HL code is SS, identifying the specific services associated to this request. This HL has no subordinate levels, or children.

DTP*472*D8*20050110~

The proposed date for the service reservation is January 10, 2005.

SV1*HC:99212**UN*1~

The Medical Service Reservation response identifies that procedure code 99212 for a unit count of 1 has been reserved for this patient.

HSD*****29*2~

The remaining number of services on file for this patient is 2.

SE*17*0001~

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 threecharacter 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 speciallyallocated two-character alphabetic code, in the range XA to XZ identifies the currency authority. The rightmost character is derived from the name of the geographic area concerned, and is mnemonic to the extent possible. The numeric codes are identical to those assigned to the geographic entities listed in ISO 3166 Part 1. The range 950-998 is reserved for identification of funds and currencies not associated with a single entity listed in ISO 3166 Part 1.

22 States and Provinces

SIMPLE DATA ELEMENT/CODE REFERENCES

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

SOURCE

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

AVAILABLE FROM

The U.S. state codes may be obtained from:
U.S. Postal Service
National Information Data Center
P.O. Box 2977
Washington, DC 20013
www.usps.gov

The Canadian province codes may be obtained from:
http://www.canadapost.ca

The Mexican state codes may be obtained from:
www.bts.gov/ntda/tbscd/mex-states.html

ABSTRACT

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

51 ZIP Code

SIMPLE DATA ELEMENT/CODE REFERENCES

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

SOURCE

National ZIP Code and Post Office Directory, Publication 65

The USPS Domestic Mail Manual

AVAILABLE FROM

U.S. Postal Service
Washington, DC 20260

New Orders
Superintendent of Documents
P.O. Box 371954
Pittsburgh, PA 15250-7954

ABSTRACT

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

130 Healthcare Common Procedural Coding System

SIMPLE DATA ELEMENT/CODE REFERENCES

235/HC, 1270/BO, 1270/BP

SOURCE

Healthcare Common Procedural Coding System

AVAILABLE FROM

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

ABSTRACT

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

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

SIMPLE DATA ELEMENT/CODE REFERENCES

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

SOURCE

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

AVAILABLE FROM

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

ABSTRACT

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

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

AVAILABLE FROM

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

ABSTRACT

A variety of codes explaining the frequency of the bill submission.

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 and Medicaid Services
CMSO, Mail Stop S2-01-16
7500 Security Blvd
Baltimore, MD 21244-1850

ABSTRACT

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

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

TList 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

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 005010X217 of the Health Care Services Review - Request for Review and Response (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 - Request for Review and Response was 004050X140. It was based on version/release/sub-release 004050 of the ASC X12 standards.

This appendix provides a change summary of changes between 004050X140 and 005010X217.


Appendix D.1 Change Descriptions

Front Matter

  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. Medical Services Reservations and Cancellations were added to Section 1.4.1.
  10. Administrative notifications were deleted from business events support by this guide.
  11. Section 1.3.3 was changed to Section 1.4.2.
  12. Section 1.3.4 was renamed to Implementation Limitations and moved to Section 1.3.
  13. Section 1.4 has been changed to Section 1.11.
  14. Section 1.4.1 has been changed to Section 1.11.1.
  15. Section 1.4.2 has been changed to Section 1.11.2.
  16. Section 1.4.3 has been changed to Section 1.11.3.
  17. Section 1.4.4 has been changed to Section 1.11.4.
  18. Section 1.4.5 has been changed to Section 1.11.5.
  19. Section 1.6 has been added to explain the use of acknowledgments with this implementation guide.
  20. Sections 1.7, 1.8, 1.9 and 1.10 have been added.
  21. Section 2 has been changed to Section 1.12 and contains minor content changes.
  22. Section 2.1 has been changed to Section 1.12.1
  23. Section 2.2 has been changed to Section 1.12.2 and contains minor content changes.
  24. Section 2.3 has been changed to Section 1.12.3 and contains minor content changes.
  25. Figure 1.6 has been updated.
  26. Section 2.4 has been changed to Section 1.12.4, contains minor content changes and changes to Request for a Range of Procedure Codes.
  27. Section 2.5 has been changed to Section 1.12.5 and contains changes to Use of LOINC codes for requesting additional documentation for a procedure code range.
  28. Section 3 and all sub-sections changed to Section 2.
  29. Situational notes have been revised in accordance with version 5010 of the X12N Implementation Guide Handbook.

Health Care Services Review Request:

  1. Updated segment examples to reflect changes and bring them up to date.
  2. Changed ST03 from not used to required.
  3. Changed BHT01 qualifier to 0007 Information Source, Information Receiver, Subscriber, Dependent, Event, Services.
  4. Added codes 36 and 01 to BHT02.
  5. Changed BHT06 usage to situational.
  6. Deleted AGB qualifier from NM101 in Loop 2010A.
  7. Added usage note for PI qualifier in NM108 in Loop 2010A.
  8. Deleted XX qualifier from NM108 in Loop 2010A.
  9. Changed REF situational rule in Loop 2010B.
  10. Changed N3 situational rule and added TR3 note in Loop 2010B.
  11. Changed to N4 segment usage to required in Loops 2010B, 2010C and 2010D.
  12. Changed N401 usage to required in Loops 2010B, 2010C, and 2010D.
  13. Changed N402 situational rule in Loops 2010B, 2010C, and 2010D.
  14. Changed N403 situational rule in Loops 2010B, 2010C, and 2010D.
  15. Changed N407 usage to situational in Loops 2010B, 2010C, and 2010D.
  16. Changed PRV02 qualifier to PXC in Loop 2010B.
  17. Changed Loop 2000E repeat to 1 and deleted second segment note.
  18. Changed TRN situational note and added TR3 note in Loop 2000E.
  19. Changed TRN04 situational rule in Loop 2000E.
  20. Added code IN with usage note to UM01 in Loop 2000E.
  21. Deleted codes 5 and 6 and added code N to UM02 in Loop 2000E.
  22. Added codes B1, C1, CQ, IC, NI, ON, PT, PU, RN, RT, TC, and TN to UM03 in Loop 2000E.
  23. Changed UM06 situational rule, deleted code R, and added code E in Loop 2000E.
  24. Changed UM04 situational rule in Loop 2000E.
  25. Changed UM05-4 situational rule in Loop 2000E.
  26. Changed DTP, Last Menstrual Period Date, situational rule in Loop 2000E.
  27. Changed DTP, Estimated Date of Birth, situational rule in Loop 2000E.
  28. Changed DTP, Event Date, situational rule and added TR3 note in Loop 2000E.
  29. Deleted HI segment note and added ICD-10 qualifier codes to HIXX-1 in Loop 2000E.
  30. Changed HSD01, HSD02, and HSD04 situational rules in Loop 2000E.
  31. Deleted CRC, Patient Condition Information, from Loop 2000E.
  32. Added CRC, Ambulance Certification Information, to Loop 2000E.
  33. Added CRC, Chiropractic Certification, to Loop 2000E.
  34. Added CRC, Durable Medical Equipment Information, to Loop 2000E.
  35. Added CRC, Oxygen Therapy Certification Information, to Loop 2000E.
  36. Added CRC, Functional Limitations Information, to Loop 2000E.
  37. Added CRC, Activities Permitted Information, to Loop 2000E.
  38. Added CRC, Mental Status Information, to Loop 2000E.
  39. Changed CR1 situational rule and added TR3 note in Loop 2000E.
  40. Deleted usage note for code A in CR104 in Loop 2000E.
  41. Changed CR106, CR109, and CR110 situational rules in Loop 2000E.
  42. Changed CR107 and CR108 to not used in Loop 2000E.
  43. Changed CR212 situational rule and moved code value on N in Loop 2000E.
  44. Changed CR507, CR508, CR510, CR511, CR513, CR514 and CR515 situational rules in Loop 2000E.
  45. Changed CR6 situational rule and segment note in Loop 2000E.
  46. Changed CR606 usage to not used in Loop 2000E.
  47. Deleted previously used codes and added W to CR607 in Loop 2000E.
  48. Changed CR613 and CR614 situational rules in Loop 2000E.
  49. Changed Loop 2010E to 2010EA, loop situational rule, and loop repeat.
  50. Deleted NM101 1T qualifier and added qualifiers 77, G3 and QV in Loop 2010EA.
  51. Changed NM106 situational rule in Loop 2010EA.
  52. Changed REF situational rule and added TR3 Note in Loop 2010EA.
  53. Changed N3 situational rule in Loop 2010EA.
  54. Changed to N4 segment usage to required in Loops 2010EA.
  55. Changed N401 usage to required in Loops 2010EA.
  56. Changed N402 situational rule in Loops 2010EA.
  57. Changed N403 situational rule in Loops 2010EA.
  58. Changed N407 usage to situational in Loops 2010EA.
  59. Changed PER situational rule in Loop 2010EA.
  60. Changed PER04 situational rule in Loop 2010EA.
  61. Change PRV situational rule and deleted segment note in Loop 2010EA.
  62. Changed PRV02 and PRV3 usage to required in Loop 2010EA.
  63. Changed PRV02 qualifier to PXC in Loop 2010EA.
  64. Added Loop 2010EB, Patient Event Transport Location with NM1, N3 and N4 segments.
  65. Added Loop 2010EC, Patient Event Other UMO Name with NM1, REF, DTP segments.
  66. Changed HL situational rule in Loop 2000F.
  67. Changed TRN situational rule and added TR3 note in Loop 2000F.
  68. Changed TRN04 situational rule in Loop 2000F.
  69. Changed UM03 situational rule and added codes B1, C1, CQ, IC, NI, ON, PT, PU, RN, RT, TC, and TN to UM03 in Loop 2000F.
  70. Deleted HI, Procedure Range, in Loop 2000F.
  71. Changed SV1 situational rule in Loop 2000F.
  72. Changed SV101-3, SV101-4, SV101-5, SV101-6 and SV101-7 situational rules in Loop 2000F.
  73. Added SV101-8 for procedure code range in Loop 2000F.
  74. Changed SV102 situational rule in Loop 2000F.
  75. Changed SV107 situational rule and added data element notes in Loop 2000F.
  76. Changed SV107-2, SV107-3 and SV107-3 situational rules in Loop 2000F.
  77. Changed SV2 situational rule in Loop 2000F.
  78. Added qualifier codes for ICD-9 and ICD-10 procedure codes to SV202-1.
  79. Changed SV202-3, SV202-4, SV202-5, SV202-6 and SV202-7 situational rules in Loop 2000F.
  80. Added SV202-8 for procedure code range in Loop 2000F.
  81. Changed SV203, SV206 and SV210 situational rules in Loop 2000F.
  82. Changed SV3 situational rule in Loop 2000F.
  83. Changed SV301-3, SV301-4, SV301-5 and SV301-6 situational rules in Loop 2000F.
  84. Added SV301-8 for procedure code range in Loop 2000F.
  85. Changed SV302 situational rule in Loop 2000F.
  86. Added code source reference to SV304-1, SV304-2, SV304-3, SV304-4 and SV304-5 in Loop 2000F.
  87. Changed NM1 situational rule in Loop 2010F.
  88. Deleted NM101 1T qualifier and added qualifiers 77, G3 and QV in Loop 2010F.
  89. Changed NM106 situational rule in Loop 2010F.
  90. Changed REF situational rule and added TR3 Note in Loop 2010F.
  91. Changed N3 situational rule in Loop 2010F.
  92. Changed to N4 segment usage to required in Loop 2010F.
  93. Changed N401 usage to required in Loop 2010F.
  94. Changed N402 situational rule in Loop 2010F.
  95. Changed N403 situational rule in Loop 2010F
  96. Changed N407 usage to situational in Loop 2010F.
  97. Changed PER situational rule in Loop 2010F.
  98. Changed PER04 situational rule in Loop 2010F.
  99. Change PRV situational rule and deleted segment note in Loop 2010F.
  100. Changed PRV02 and PRV3 usage to required in Loop 2010F.
  101. Changed PRV02 qualifier to PXC in Loop 2010F.

Health Care Services Review Response:

  1. Updated segment examples to reflect changes and bring them up to date.
  2. Changed ST03 from not used to required.
  3. Changed BHT01 qualifier to 0007 Information Source, Information Receiver, Subscriber, Dependent, Event, Services.
  4. Changed BHT06 usage to situational.
  5. Deleted AGB qualifier from NM101 in Loop 2010A.
  6. Deleted XX qualifier from NM108 in Loop 2010A.
  7. Deleted Y response code from AAA01 in Loop 2010A.
  8. Changed AAA03 and AAA04 usage to required in Loop 2010A.
  9. Deleted reason codes 04 and 41 from AAA03 in Loop 2010A.
  10. Changed HL situational rule and added TR3 note in Loop 2000B.
  11. Deleted Y response code from AAA01 in Loop 2010B.
  12. Changed AAA03 and AAA04 usage to required in Loop 2010B.
  13. Changed PRV02 qualifier to PXC in Loop 2010B.
  14. Changed HL situational rule and added TR3 note in Loops 2000C and 2000D.
  15. Deleted code 15 from AAA03 in Loop 2010C.
  16. Changed to N4 segment usage to required in Loops 2010C and 2010D
  17. Changed N401 usage to required in Loops 2010C and 2010D.
  18. Changed N402 situational rule in Loops 2010C and 2010D.
  19. Changed N403 situational rule in Loops 2010C and 2010D.
  20. Changed N407 usage to situational in Loops 2010C and 2010D.
  21. Deleted Y response code from AAA01 in Loops 2010C and 2010D.
  22. Changed AAA03 and AAA04 usage to required in Loops 2010C and 2010D.
  23. Changed DMG situational rule in Loops 2010C and 2010D.
  24. Changed DMG03 situational rule in Loops 2010C and 2010D.
  25. Changed INS situation rule in Loops 2010C and 2010D.
  26. Changed Loop 2000E repeat to 1.
  27. Changed HL situational rule and added TR3 note in Loop 2000E.
  28. Changed TRN04 situational rule in Loop 2000E.
  29. Deleted Y response code from AAA01 in Loop 2000E.
  30. Changed AAA03 and AAA04 usage to required in Loop 2000E.
  31. Added response code AA to AAA03 in Loop 2000E.
  32. Added code IN Individual with usage note to UM01 in Loop 2000E.
  33. Deleted codes 5 and 6 and added code N to UM02 in Loop 2000E.
  34. Added codes B1, C1, CQ, IC, NI, ON, PT, PU, RN, RT, TC, and TN to UM03 in Loop 2000E.
  35. Deleted code R and added code E to UM06 in Loop 2000E.
  36. Added note to HCR03 in Loop 2000E.
  37. Changed REF, Administrative Reference Number, situational note in Loop 2000E.
  38. Changed REF, Previous Review Authorization Number, situational note and added TR3 note in Loop 2000E.
  39. Deleted DTP, Event Date, segment note in Loop 2000E.
  40. Deleted DTP, Admission Date, segment note in Loop 2000E.
  41. Changed DTP, Certification Issue Date, situational rule and segment note in Loop 2000E.
  42. Changed DTP, Certification Expiration Date, situational rule in Loop 2000E.
  43. Changed DTP, Certification Effective Date, situational rule in Loop 2000E.
  44. Change HI situational rule and segment note and added ICD-10 qualifier codes to HIXX-1 in Loop 2000E.
  45. Changed HSD situational rule in Loop 2000E.
  46. Changed HSD01 and HSD02 situational rules in Loop 2000E.
  47. Changed CL101, CL102 and CL103 situational rules in Loop 2000E.
  48. Changed CR1 situational rule in Loop 2000E.
  49. Changed CR106 situational rule in Loop 2000E.
  50. Changed CR107 and CR108 to not used in Loop 2000E.
  51. Changed CR2 situational rule and deleted segment note in Loop 2000E.
  52. Changed CR505 to not used in Loop 2000E.
  53. Changed CR507 and CR508 situational rules in Loop 2000E.
  54. Changed CR6 situational rule in Loop 2000E.
  55. Changed CR604 situational rule in Loop 2000E.
  56. Deleted previously used codes and added W to CR607 in Loop 2000E.
  57. Changed PWK07 situational rule in Loop 2000E.
  58. Changed Loop 2010EA loop repeat.
  59. Changed NM1 situational rule in Loop 2010EA.
  60. Deleted NM101 1T qualifier and added qualifiers 77, G3 and QV in Loop 2010EA.
  61. Changed NM103, NM104, NM106, NM107, NM108 and NM109 situational rules in Loop 2010EA.
  62. Changed to N4 segment usage to required in Loop 2010EA.
  63. Changed N401 usage to required in Loop 2010EA.
  64. Changed N402 situational rule in Loop 2010EA.
  65. Changed N403 situational rule in Loop 2010EA.
  66. Changed N407 usage to situational in Loop 2010EA.
  67. Deleted Y response code from AAA01 in Loop 2010EA.
  68. Changed AAA03 and AAA04 usage to required in Loop 2010EA.
  69. Added response code IP to AAA03 in Loop 2010EA.
  70. Change PRV situational rule in Loop 2010EA.
  71. Changed PRV02 and PRV3 usage to required in Loop 2010EA.
  72. Changed PRV02 qualifier to PXC in Loop 2010EA.
  73. Deleted NM1 segment note in Loop 2010EB.
  74. Changed NM108 and NM109 situational rules in Loop 2010EB.
  75. Changed to N4 segment usage to required in Loop 2010EB.
  76. Changed N401 usage to required in Loop 2010EB.
  77. Changed N402 situational rule in Loop 2010EB.
  78. Changed N403 situational rule in Loop 2010EB.
  79. Changed N407 usage to situational in Loop 2010EB.
  80. Added Loop 2010EC, Patient Event Transport Location with NM1, N3, N4, and AAA segments.
  81. Changed HL situational rule and added TR3 note in Loop 2000F.
  82. Changed TRN04 situational rule in Loop 2000F.
  83. Changed AAA situational rule in Loop 2000F.
  84. Deleted Y response code from AAA01 in Loop 2000F.
  85. Changed AAA03 and AAA04 usage to required in Loop 2000F.
  86. Added response code AA to AAA03 in Loop 2000F.
  87. Changed UM situational rule in Loop 2000F.
  88. Added codes B1, C1, CQ, IC, NI, ON, PT, PU, RN, RT, TC, and TN to UM03 in Loop 2000F.
  89. Changed UM04 situational rule in Loop 2000F.
  90. Added note to HCR03 in Loop 2000F.
  91. Changed DTP, Certification Issue Date, situational rule and segment note in Loop 2000F.
  92. Changed DTP, Certification Expiration Date, situational rule in Loop 2000F.
  93. Changed DTP, Certification Effective Date, situational rule in Loop 2000F.
  94. Deleted HI, Procedure Range, in Loop 2000F.
  95. Added HI, Request for Additional Information, in Loop 2000F.
  96. Changed SV1 situational rule in Loop 2000F.
  97. Changed SV101-7 situational rule in Loop 2000F.
  98. Added SV101-8 for procedure code range in Loop 2000F.
  99. Changed SV102 situational rule in Loop 2000F.
  100. Changed SV107 situational rule and added data element notes in Loop 2000F.
  101. Changed SV107 to not used in Loop 2000F.
  102. Changed SV2 situational rule in Loop 2000F.
  103. Changed SV201, SV202-7 and SV203 situational rules in Loop 2000F.
  104. Added qualifier codes for ICD-9 and ICD-10 procedure codes to SV202-1.
  105. Added SV202-8 for procedure code range in Loop 2000F.
  106. Deleted SV3 segment note in Loop 2000F.
  107. Changed SV301-7 situational rules in Loop 2000F.
  108. Added SV301-8 for procedure code range in Loop 2000F.
  109. Changed SV302 situational rule in Loop 2000F.
  110. Added code source reference to SV304-1, SV304-2, SV304-3, SV304-4 and SV304-5 in Loop 2000F.
  111. Changed TOO situational rule in Loop 2000F.
  112. Changed TOO01 to required in Loop 2000F.
  113. Changed TOO03-2, TOO03-3, TOO03-4 and TOO03-5 situational rule and added code source reference in Loop 2000F.
  114. Changed HSD situational rule and added TR3 note and segment example in Loop 2000F.
  115. Changed HSD01, HSD02, HSD05, HSD06, HSD07, and HSD08 situational rules in Loop 2000F.
  116. Added qualifier code 29 to HSD05 in Loop 2000F.
  117. Changed PWK07 situational rule in Loop 2000F.
  118. Changed NM1 situational rule in Loop 2010FA.
  119. Deleted NM101 1T qualifier and added qualifiers 77, G3 and QV in Loop 2010FA.
  120. Changed NM103, NM104, NM106, NM107, NM108 and NM109 situational rules in Loop 2010FA.
  121. Changed REF situational rule and added TR3 Note in Loop 2010FA.
  122. Changed N3 situational rule in Loop 2010FA.
  123. Changed to N4 segment usage to required in Loop 2010FA.
  124. Changed N401 usage to required in Loop 2010FA.
  125. Changed N402 situational rule in Loop 2010FA.
  126. Changed N403 situational rule in Loop 2010FA.
  127. Changed N407 usage to situational in Loop 2010FA.
  128. Changed PER situational rule in Loop 2010FA.
  129. Changed PER04 situational rule in Loop 2010FA.
  130. Deleted Y response code from AAA01 in Loop 2010FA.
  131. Changed AAA03 and AAA04 usage to required in Loop 2010FA.
  132. Added response code IP to AAA03 in Loop 2010FA.
  133. Change PRV situational rule in Loop 2010FA.
  134. Changed PRV02 and PRV3 usage to required in Loop 2010F.
  135. Changed PRV02 qualifier to PXC in Loop 2010FA.
  136. Deleted NM1 segment note in Loop 2010FB.
  137. Changed NM103 and NM109 situational rules in Loop 2010FB.
  138. Deleted N3 segment note in Loop 2010FB.
  139. Changed to N4 segment usage to required in Loop 2010FB.
  140. Changed N401 usage to required in Loop 2010FB.
  141. Changed N402 situational rule in Loop 2010FB.
  142. Changed N403 situational rule in Loop 2010FB.
  143. Changed N407 usage to situational in Loop 2010FB.
  144. Changed PER04 situational rule in Loop 2010FB.

Examples:

  1. Updated examples to reflect changes and bring them up to date.
  2. Added Non-Emergency Transportation Services example.
  3. Added Medical Services Reservation example.

Appendixes:

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

Appendix E - Industry Names

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

Legend

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

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

Action Code
Code indicating type of action
278 - Health Care Services Review - Request For Review Response
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 - Request For Review Response
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 - Request For Review Response
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 - Request For Review Response
D | 2010EB | N402 | - | 156

Additional Service Information Contact City Name
The city name of the Additional Service Information Contact.
278 - Health Care Services Review - Request For Review Response
D | 2010FB | N401 | - | 19

Additional Service Information Contact Postal Zone or ZIP Code
The postal code in the address of the Additional Service Information Contact.
278 - Health Care Services Review - Request For Review Response
D | 2010FB | N403 | - | 116

Additional Service Information Contact State Code
Code identifying the state or province in the address of the Additional Service Information Contact.
278 - Health Care Services Review - Request For Review Response
D | 2010FB | N402 | - | 156

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

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

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

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

Ambulance Transport Reason Code
Code indicating the reason for ambulance transport.
278 - Health Care Services Review - Request For Review
D | 2000E | CR104 | - | 1317

Arterial Blood Gas Quantity
The Arterial Blood Gas test results breathing room air (furnish results of recent hospital tests).
278 - Health Care Services Review - Request For Review
D | 2000E | CR510 | - | 380

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

Attachment Description
Free-form text describing attachments related to the claim.
278 - Health Care Services Review - Request For Review
D | 2000E | PWK07 | - | 352
D | 2000F | PWK07 | - | 352
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2000E | PWK01 | - | 755
D | 2000F | PWK01 | - | 755
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2010D | INS17 | - | 1470
278 - Health Care Services Review - Request For Review Response
D | 2010D | INS17 | - | 1470

Certification Condition Indicator
Code indicating whether or not the condition codes apply to the patient or another entity.
278 - Health Care Services Review - Request For Review
D | 2000E | CRC02 | - | 1073
D | 2000E | CRC02 | - | 1073
D | 2000E | CRC02 | - | 1073
D | 2000E | CRC02 | - | 1073
D | 2000E | CRC02 | - | 1073
D | 2000E | CRC02 | - | 1073
D | 2000E | CRC02 | - | 1073

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 - Request For Review Response
D | 2000E | DTP03 | - | 1251
D | 2000F | DTP03 | - | 1251

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

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

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

Code Category
Specifies the situation or category to which the code applies.
278 - Health Care Services Review - Request For Review
D | 2000E | CRC01 | - | 1136
D | 2000E | CRC01 | - | 1136
D | 2000E | CRC01 | - | 1136
D | 2000E | CRC01 | - | 1136
D | 2000E | CRC01 | - | 1136
D | 2000E | CRC01 | - | 1136
D | 2000E | CRC01 | - | 1136

Code List Qualifier Code
Code identifying a specific industry code list.
278 - Health Care Services Review - Request For Review
D | 2000F | TOO01 | - | 1270
278 - Health Care Services Review - Request For Review Response
D | 2000F | HI01 | C022-01 | 1270
D | 2000F | HI02 | C022-01 | 1270
D | 2000F | HI03 | C022-01 | 1270
D | 2000F | HI04 | C022-01 | 1270
D | 2000F | HI05 | C022-01 | 1270
D | 2000F | HI06 | C022-01 | 1270
D | 2000F | HI07 | C022-01 | 1270
D | 2000F | HI08 | C022-01 | 1270
D | 2000F | HI09 | C022-01 | 1270
D | 2000F | HI10 | C022-01 | 1270
D | 2000F | HI11 | C022-01 | 1270
D | 2000F | HI12 | C022-01 | 1270
D | 2000F | TOO01 | - | 1270

Communication Number Qualifier
Code identifying the type of communication number.
278 - Health Care Services Review - Request For Review
D | 2010B | PER03 | - | 365
D | 2010B | PER05 | - | 365
D | 2010B | PER07 | - | 365
D | 2010EA | PER03 | - | 365
D | 2010EA | PER05 | - | 365
D | 2010EA | PER07 | - | 365
D | 2010F | PER03 | - | 365
D | 2010F | PER05 | - | 365
D | 2010F | PER07 | - | 365
278 - Health Care Services Review - Request For Review Response
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 | 2010FA | PER03 | - | 365
D | 2010FA | PER05 | - | 365
D | 2010FA | PER07 | - | 365
D | 2010FB | PER03 | - | 365
D | 2010FB | PER05 | - | 365
D | 2010FB | PER07 | - | 365

Complication Indicator
A code to indicate whether the Patient's condition is Complicated or Uncomplicated.
278 - Health Care Services Review - Request For Review
D | 2000E | CR209 | - | 1073

Condition Code
Code(s) used to identify condition(s) relating to this bill or relating to the patient.
278 - Health Care Services Review - Request For Review
D | 2000E | CRC03 | - | 1321
D | 2000E | CRC04 | - | 1321
D | 2000E | CRC05 | - | 1321
D | 2000E | CRC06 | - | 1321
D | 2000E | CRC07 | - | 1321
D | 2000E | CRC03 | - | 1321
D | 2000E | CRC04 | - | 1321
D | 2000E | CRC05 | - | 1321
D | 2000E | CRC06 | - | 1321
D | 2000E | CRC07 | - | 1321
D | 2000E | CRC03 | - | 1321
D | 2000E | CRC04 | - | 1321
D | 2000E | CRC05 | - | 1321
D | 2000E | CRC06 | - | 1321
D | 2000E | CRC07 | - | 1321
D | 2000E | CRC03 | - | 1321
D | 2000E | CRC04 | - | 1321
D | 2000E | CRC05 | - | 1321
D | 2000E | CRC06 | - | 1321
D | 2000E | CRC07 | - | 1321
D | 2000E | CRC03 | - | 1321
D | 2000E | CRC04 | - | 1321
D | 2000E | CRC05 | - | 1321
D | 2000E | CRC06 | - | 1321
D | 2000E | CRC07 | - | 1321
D | 2000E | CRC03 | - | 1321
D | 2000E | CRC04 | - | 1321
D | 2000E | CRC05 | - | 1321
D | 2000E | CRC06 | - | 1321
D | 2000E | CRC07 | - | 1321
D | 2000E | CRC03 | - | 1321
D | 2000E | CRC04 | - | 1321
D | 2000E | CRC05 | - | 1321
D | 2000E | CRC06 | - | 1321
D | 2000E | CRC07 | - | 1321

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

Country Code
Code indicating the geographic location.
278 - Health Care Services Review - Request For Review
D | 2010B | N404 | - | 26
D | 2010C | N404 | - | 26
D | 2010D | N404 | - | 26
D | 2000E | UM05 | C024-05 | 26
D | 2010EA | N404 | - | 26
D | 2010F | N404 | - | 26
278 - Health Care Services Review - Request For Review Response
D | 2010C | N404 | - | 26
D | 2010D | N404 | - | 26
D | 2010EA | N404 | - | 26
D | 2010EB | N404 | - | 26
D | 2010FA | N404 | - | 26
D | 2010FB | N404 | - | 26

Country Subdivision Code
Code identifying the country subdivision.
278 - Health Care Services Review - Request For Review
D | 2010B | N407 | - | 1715
D | 2010C | N407 | - | 1715
D | 2010D | N407 | - | 1715
D | 2010EA | N407 | - | 1715
D | 2010F | N407 | - | 1715
278 - Health Care Services Review - Request For Review Response
D | 2010C | N407 | - | 1715
D | 2010D | N407 | - | 1715
D | 2010EA | N407 | - | 1715
D | 2010EB | N407 | - | 1715
D | 2010FA | N407 | - | 1715
D | 2010FB | N407 | - | 1715

Current Health Condition Code
Code indicating current condition of the individual.
278 - Health Care Services Review - Request For Review
D | 2000E | UM07 | - | 1213

Daily Oxygen Use Count
Number of times per day that the patient must use oxygen.
278 - Health Care Services Review - Request For Review
D | 2000E | CR507 | - | 380
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
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 | 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 | 2000E | CR615 | - | 1250
D | 2010EC | DTP02 | - | 1250
D | 2000F | DTP02 | - | 1250
278 - Health Care Services Review - Request For Review Response
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 | 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 - Request For Review
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 | 2010EC | DTP01 | - | 374
D | 2000F | DTP01 | - | 374
278 - Health Care Services Review - Request For Review Response
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 | 2000F | DTP01 | - | 374
D | 2000F | DTP01 | - | 374
D | 2000F | DTP01 | - | 374
D | 2000F | DTP01 | - | 374

Delay Reason Code
Code indicating the reason why a request was delayed.
278 - Health Care Services Review - Request For Review
D | 2000E | UM10 | - | 1514

Delivery Frequency Code
Code which specifies frequency by which services can be performed.
278 - Health Care Services Review - Request For Review
D | 2000E | HSD07 | - | 678
D | 2000F | HSD07 | - | 678
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2000E | HSD08 | - | 679
D | 2000F | HSD08 | - | 679
278 - Health Care Services Review - Request For Review Response
D | 2000E | HSD08 | - | 679
D | 2000F | HSD08 | - | 679

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

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

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

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

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

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

Dependent Middle Name or Initial
The middle name of the dependent.
278 - Health Care Services Review - Request For Review
D | 2010D | NM105 | - | 1037
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2010D | NM107 | - | 1039
278 - Health Care Services Review - Request For Review Response
D | 2010D | NM107 | - | 1039

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

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

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

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

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

Diagnosis Code
An ICD-9-CM Diagnosis Code identifying a diagnosed medical condition.
278 - Health Care Services Review - Request For Review
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 - Request For Review Response
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 - Request For Review
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 - Request For Review
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 - Request For Review Response
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 - Request For Review
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 - Request For Review Response
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 - Request For Review
D | 2000F | SV111 | - | 1073
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2010C | INS08 | - | 584
278 - Health Care Services Review - Request For Review Response
D | 2010C | INS08 | - | 584

Entity Identifier Code
Code identifying an organizational entity, a physical location, property or an individual.
278 - Health Care Services Review - Request For Review
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 | 2010F | NM101 | - | 98
278 - Health Care Services Review - Request For Review Response
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 | 2010FA | NM101 | - | 98
D | 2010FB | NM101 | - | 98

Entity Type Qualifier
Code qualifying the type of entity.
278 - Health Care Services Review - Request For Review
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 | 2010F | NM102 | - | 1065
278 - Health Care Services Review - Request For Review Response
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 | 2010FA | NM102 | - | 1065
D | 2010FB | NM102 | - | 1065

Equipment Reason Description
Free-form description of the reason for the equipment.
278 - Health Care Services Review - Request For Review
D | 2000E | CR505 | - | 352

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

Facility Code Qualifier
Code identifying the type of facility referenced.
278 - Health Care Services Review - Request For Review
D | 2000E | UM04 | C023-02 | 1332
D | 2000F | UM04 | C023-02 | 1332
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2000E | UM04 | C023-01 | 1331
D | 2000F | UM04 | C023-01 | 1331
278 - Health Care Services Review - Request For Review Response
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 - Request For Review Response
D | 2000A | AAA04 | - | 889
D | 2010A | AAA04 | - | 889
D | 2010B | AAA04 | - | 889
D | 2010C | AAA04 | - | 889
D | 2010D | AAA04 | - | 889
D | 2000E | AAA04 | - | 889
D | 2010EA | AAA04 | - | 889
D | 2010EC | AAA04 | - | 889
D | 2000F | AAA04 | - | 889
D | 2010FA | AAA04 | - | 889

Free Form Message Text
Text used to convey information related to the transaction.
278 - Health Care Services Review - Request For Review
D | 2000E | MSG01 | - | 933
D | 2000F | MSG01 | - | 933
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
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 - Request For Review Response
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 - Request For Review
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 - Request For Review Response
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 - Request For Review
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 - Request For Review Response
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 - Request For Review
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 - Request For Review Response
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 - Request For Review
H | | BHT01 | - | 1005
278 - Health Care Services Review - Request For Review Response
H | | BHT01 | - | 1005

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

Home Health Start Date
Date Home Health services are scheduled or are anticipated to start.
278 - Health Care Services Review - Request For Review
D | 2000E | CR602 | - | 373
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2010A | NM108 | - | 66
D | 2010B | NM108 | - | 66
D | 2010C | NM108 | - | 66
D | 2000E | PWK05 | - | 66
D | 2010EA | NM108 | - | 66
D | 2000F | PWK05 | - | 66
D | 2010F | NM108 | - | 66
278 - Health Care Services Review - Request For Review Response
D | 2010A | NM108 | - | 66
D | 2010B | NM108 | - | 66
D | 2010C | NM108 | - | 66
D | 2010D | NM108 | - | 66
D | 2000E | PWK05 | - | 66
D | 2010EA | NM108 | - | 66
D | 2010EB | NM108 | - | 66
D | 2000F | PWK05 | - | 66
D | 2010FA | NM108 | - | 66
D | 2010FB | NM108 | - | 66

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

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

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

LOINC Code
Logical Observation Identifier Names and Codes (LOINC) codes.
278 - Health Care Services Review - Request For Review Response
D | 2000F | HI01 | C022-02 | 1271
D | 2000F | HI02 | C022-02 | 1271
D | 2000F | HI03 | C022-02 | 1271
D | 2000F | HI04 | C022-02 | 1271
D | 2000F | HI05 | C022-02 | 1271
D | 2000F | HI06 | C022-02 | 1271
D | 2000F | HI07 | C022-02 | 1271
D | 2000F | HI08 | C022-02 | 1271
D | 2000F | HI09 | C022-02 | 1271
D | 2000F | HI10 | C022-02 | 1271
D | 2000F | HI11 | C022-02 | 1271
D | 2000F | HI12 | C022-02 | 1271

Last Admission Period
Admission date of the most recent inpatient stay.
278 - Health Care Services Review - Request For Review
D | 2000E | CR616 | - | 1251

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

Last Visit Date
Date the patient was last seen by the physician.
278 - Health Care Services Review - Request For Review
D | 2000E | CR613 | - | 373

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

License Number State Code
The State Postal Code of a jurisdiction-assigned license number.
278 - Health Care Services Review - Request For Review
D | 2010EA | REF03 | - | 352
D | 2010F | REF03 | - | 352
278 - Health Care Services Review - Request For Review Response
D | 2010EA | REF03 | - | 352
D | 2010FA | REF03 | - | 352

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

Nursing Home Level of Care
Code specifying the level of care provided by a nursing home facility.
278 - Health Care Services Review - Request For Review
D | 2000F | SV120 | - | 1337
D | 2000F | SV210 | - | 1337
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2000E | CL104 | - | 1345
D | 2000F | SV209 | - | 1345

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

Oral Cavity Designation Code
Code identifying an oral cavity involved in the service.
278 - Health Care Services Review - Request For Review
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 - Request For Review Response
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 - Request For Review
D | 2010EC | DTP03 | - | 1251

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

Other UMO Name
Name of other UMO.
278 - Health Care Services Review - Request For Review
D | 2010EC | NM103 | - | 1035

Oxygen Delivery System Code
Code to indicate if a particular form of delivery was prescribed.
278 - Health Care Services Review - Request For Review
D | 2000E | CR517 | - | 1382
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2000E | CR503 | - | 1348
D | 2000E | CR504 | - | 1348
D | 2000E | CR518 | - | 1348
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2000E | CR506 | - | 380
278 - Health Care Services Review - Request For Review Response
D | 2000E | CR506 | - | 380

Oxygen Saturation Quantity
The oxygen saturation (oximetry) test results.
278 - Health Care Services Review - Request For Review
D | 2000E | CR511 | - | 380

Oxygen Test Condition Code
Code indicating the conditions under which a patient was tested.
278 - Health Care Services Review - Request For Review
D | 2000E | CR512 | - | 1349

Oxygen Test Findings Code
Code indicating the findings of oxygen tests performed on a patient.
278 - Health Care Services Review - Request For Review
D | 2000E | CR513 | - | 1350
D | 2000E | CR514 | - | 1350
D | 2000E | CR515 | - | 1350

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

Patient Condition Code
Code indicating the condition of the patient.
278 - Health Care Services Review - Request For Review
D | 2000E | CR208 | - | 1342

Patient Condition Description
Free-form description of the patient's condition.
278 - Health Care Services Review - Request For Review
D | 2000E | CR210 | - | 352
D | 2000E | CR211 | - | 352

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 - Request For Review
D | 2010EA | N301 | - | 166
D | 2010EA | N302 | - | 166
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2010EA | N401 | - | 19
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2010EA | PER04 | - | 364
D | 2010EA | PER06 | - | 364
D | 2010EA | PER08 | - | 364
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2010EA | PER02 | - | 93
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2010EA | NM104 | - | 1036
278 - Health Care Services Review - Request For Review Response
D | 2010EA | 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 - Request For Review
D | 2010EA | NM109 | - | 67
278 - Health Care Services Review - Request For Review Response
D | 2010EA | 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 - Request For Review
D | 2010EA | NM103 | - | 1035
278 - Health Care Services Review - Request For Review Response
D | 2010EA | 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 - Request For Review
D | 2010EA | NM105 | - | 1037
278 - Health Care Services Review - Request For Review Response
D | 2010EA | 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 - Request For Review
D | 2010EA | NM106 | - | 1038
278 - Health Care Services Review - Request For Review Response
D | 2010EA | 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 - Request For Review
D | 2010EA | NM107 | - | 1039
278 - Health Care Services Review - Request For Review Response
D | 2010EA | 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 - Request For Review
D | 2010EA | N403 | - | 116
278 - Health Care Services Review - Request For Review Response
D | 2010EA | N403 | - | 116

Patient Event Provider State 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 - Request For Review
D | 2010EA | N402 | - | 156
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2010EA | REF02 | - | 127
278 - Health Care Services Review - Request For Review Response
D | 2010EA | REF02 | - | 127

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 - Request For Review
D | 2000E | TRN02 | - | 127
278 - Health Care Services Review - Request For Review Response
D | 2000E | TRN02 | - | 127

Patient Event 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 - Request For Review
D | 2010EB | N301 | - | 166
D | 2010EB | N302 | - | 166
278 - Health Care Services Review - Request For Review Response
D | 2010EC | N301 | - | 166
D | 2010EC | N302 | - | 166

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 - Request For Review
D | 2010EB | N401 | - | 19
278 - Health Care Services Review - Request For Review Response
D | 2010EC | N401 | - | 19

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

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 - Request For Review
D | 2010EB | N403 | - | 116
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2010EB | N402 | - | 156
278 - Health Care Services Review - Request For Review Response
D | 2010EC | N402 | - | 156

Patient Location Code
Code identifying the location where the patient receives medical treatment.
278 - Health Care Services Review - Request For Review
D | 2000E | CR617 | - | 1384

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 - Request For Review
D | 2000E | CL103 | - | 1352
278 - Health Care Services Review - Request For Review Response
D | 2000E | CL103 | - | 1352

Patient Weight
Weight of the patient at time of treatment or transport.
278 - Health Care Services Review - Request For Review
D | 2000E | CR102 | - | 81

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

Physician Contact Date
Date of the home health agency's most recent contact with the physician.
278 - Health Care Services Review - Request For Review
D | 2000E | CR614 | - | 373

Physician Order Date
Date the agency received the verbal orders from the physician for start of care.
278 - Health Care Services Review - Request For Review
D | 2000E | CR612 | - | 373

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

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

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

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

Procedure Code Description
Description clarifying the Product/Service Procedure Code and related data elements.
278 - Health Care Services Review - Request For Review
D | 2000F | SV101 | C003-07 | 352
D | 2000F | SV202 | C003-07 | 352
D | 2000F | SV301 | C003-07 | 352
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
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 - Request For Review Response
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 Qualifier
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
278 - Health Care Services Review - Request For Review
D | 2000E | CR610 | - | 235
D | 2000F | SV101 | C003-01 | 235
D | 2000F | SV202 | C003-01 | 235
D | 2000F | SV301 | C003-01 | 235
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2000E | UM08 | - | 923
D | 2000E | CR601 | - | 923
278 - Health Care Services Review - Request For Review Response
D | 2000E | CR601 | - | 923

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

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

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

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

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

Provider Code
Code identifying the type of provider.
278 - Health Care Services Review - Request For Review
D | 2010B | PRV01 | - | 1221
D | 2010EA | PRV01 | - | 1221
D | 2010F | PRV01 | - | 1221
278 - Health Care Services Review - Request For Review Response
D | 2010B | PRV01 | - | 1221
D | 2010EA | PRV01 | - | 1221
D | 2010FA | PRV01 | - | 1221

Provider Taxonomy Code
Code designating the provider type, classification, and specialization.
278 - Health Care Services Review - Request For Review
D | 2010B | PRV03 | - | 127
D | 2010EA | PRV03 | - | 127
D | 2010F | PRV03 | - | 127
278 - Health Care Services Review - Request For Review Response
D | 2010B | PRV03 | - | 127
D | 2010EA | PRV03 | - | 127
D | 2010FA | PRV03 | - | 127

Quantity Qualifier
Code specifying the type of quantity.
278 - Health Care Services Review - Request For Review
D | 2000E | HSD01 | - | 673
D | 2000F | HSD01 | - | 673
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2010EC | REF04 | C040-06 | 127

Reference Identification Qualifier
Code qualifying the reference identification.
278 - Health Care Services Review - Request For Review
D | 2010B | REF01 | - | 128
D | 2010B | 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 | 2010EC | REF01 | - | 128
D | 2010EC | REF04 | C040-01 | 128
D | 2010EC | REF04 | C040-03 | 128
D | 2010EC | 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 - Request For Review Response
D | 2010B | REF01 | - | 128
D | 2010B | 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 | 2000F | REF01 | - | 128
D | 2000F | REF01 | - | 128
D | 2010FA | REF01 | - | 128
D | 2010FA | PRV02 | - | 128

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

Related Causes Code
Code identifying an accompanying cause of an illness, injury, or an accident.
278 - Health Care Services Review - Request For Review
D | 2000E | UM05 | C024-01 | 1362
D | 2000E | UM05 | C024-02 | 1362
D | 2000E | UM05 | C024-03 | 1362

Release of Information Code
Code indicating whether the provider has on file a signed statement permitting the release of medical data to other organizations.
278 - Health Care Services Review - Request For Review
D | 2000E | UM09 | - | 1363

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

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

Requester Address Line
Address line in the address of the requester.
278 - Health Care Services Review - Request For Review
D | 2010B | N301 | - | 166
D | 2010B | N302 | - | 166

Requester City Name
Name of the city in the address of the requester.
278 - Health Care Services Review - Request For Review
D | 2010B | N401 | - | 19

Requester Contact Communication Number
Complete requester contact communications number, including country or area code when applicable.
278 - Health Care Services Review - Request For Review
D | 2010B | PER04 | - | 364
D | 2010B | PER06 | - | 364
D | 2010B | PER08 | - | 364

Requester Contact Name
Name identifying the requester's contact person.
278 - Health Care Services Review - Request For Review
D | 2010B | PER02 | - | 93

Requester First Name
First name of the requester of a health care services review.
278 - Health Care Services Review - Request For Review
D | 2010B | NM104 | - | 1036
278 - Health Care Services Review - Request For Review Response
D | 2010B | NM104 | - | 1036

Requester Identifier
Code uniquely identifying the provider requesting the services review to the payer, regulatory authority, or other authorized body or agency.
278 - Health Care Services Review - Request For Review
D | 2010B | NM109 | - | 67
278 - Health Care Services Review - Request For Review Response
D | 2010B | NM109 | - | 67

Requester Last or Organization Name
Last name or organization name of the requester of a health care services review.
278 - Health Care Services Review - Request For Review
D | 2010B | NM103 | - | 1035
278 - Health Care Services Review - Request For Review Response
D | 2010B | NM103 | - | 1035

Requester Middle Name or Initial
Middle name or middle initial of the requester of a health care services review.
278 - Health Care Services Review - Request For Review
D | 2010B | NM105 | - | 1037
278 - Health Care Services Review - Request For Review Response
D | 2010B | NM105 | - | 1037

Requester Name Suffix
Suffix to the name of the requester of a health care services review.
278 - Health Care Services Review - Request For Review
D | 2010B | NM107 | - | 1039
278 - Health Care Services Review - Request For Review Response
D | 2010B | NM107 | - | 1039

Requester Postal Zone or ZIP Code
Postal code in the address of the requester.
278 - Health Care Services Review - Request For Review
D | 2010B | N403 | - | 116

Requester State or Province Code
Code identifying the state or province in the address of the requester.
278 - Health Care Services Review - Request For Review
D | 2010B | N402 | - | 156

Requester Supplemental Identifier
Supplemental identification information about the requester.
278 - Health Care Services Review - Request For Review
D | 2010B | REF02 | - | 127
278 - Health Care Services Review - Request For Review Response
D | 2010B | REF02 | - | 127

Respiratory Therapist Order Text
Free-form description of the respiratory therapist's orders.
278 - Health Care Services Review - Request For Review
D | 2000E | CR509 | - | 352
278 - Health Care Services Review - Request For Review Response
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 - Request For Review Response
D | 2010EB | N301 | - | 166
D | 2010EB | N302 | - | 166
D | 2010FB | N301 | - | 166
D | 2010FB | 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 - Request For Review Response
D | 2010EB | PER04 | - | 364
D | 2010EB | PER06 | - | 364
D | 2010EB | PER08 | - | 364
D | 2010FB | PER04 | - | 364
D | 2010FB | PER06 | - | 364
D | 2010FB | 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 - Request For Review Response
D | 2010EB | NM104 | - | 1036
D | 2010FB | NM104 | - | 1036

Response Contact Identifier
Code uniquely identifying the entity that is the designated recipient of requested additional information.
278 - Health Care Services Review - Request For Review Response
D | 2010EB | NM109 | - | 67
D | 2010FB | 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 - Request For Review Response
D | 2010EB | NM103 | - | 1035
D | 2010FB | 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 - Request For Review Response
D | 2010EB | NM105 | - | 1037
D | 2010FB | NM105 | - | 1037

Response Contact Name
The name of the person or organization designated to receive the requested information.
278 - Health Care Services Review - Request For Review Response
D | 2010EB | PER02 | - | 93
D | 2010FB | 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 - Request For Review Response
D | 2010EB | NM107 | - | 1039
D | 2010FB | NM107 | - | 1039

Review Decision Reason Code
Code identifying the reason for this review outcome.
278 - Health Care Services Review - Request For Review Response
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 - Request For Review Response
D | 2000E | HCR02 | - | 127
D | 2000F | HCR02 | - | 127

Round Trip Purpose Description
Free-form description of the purpose of the ambulance transport round trip.
278 - Health Care Services Review - Request For Review
D | 2000E | CR109 | - | 352

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 - Request For Review
D | 2000E | HSD04 | - | 1167
D | 2000F | HSD04 | - | 1167
278 - Health Care Services Review - Request For Review Response
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 - Request For Review Response
D | 2000E | HCR04 | - | 1073
D | 2000F | HCR04 | - | 1073

Service Line Amount
Charges related to this service.
278 - Health Care Services Review - Request For Review
D | 2000F | SV102 | - | 782
D | 2000F | SV203 | - | 782
D | 2000F | SV302 | - | 782
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2000F | SV206 | - | 1371
278 - Health Care Services Review - Request For Review Response
D | 2000F | SV206 | - | 1371

Service Line Revenue Code
UB92 Revenue Code pertaining to the service line.
278 - Health Care Services Review - Request For Review
D | 2000F | SV201 | - | 234
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2010F | N301 | - | 166
D | 2010F | N302 | - | 166
278 - Health Care Services Review - Request For Review Response
D | 2010FA | N301 | - | 166
D | 2010FA | 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 - Request For Review
D | 2010F | N401 | - | 19
278 - Health Care Services Review - Request For Review Response
D | 2010FA | 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 - Request For Review
D | 2010F | PER04 | - | 364
D | 2010F | PER06 | - | 364
D | 2010F | PER08 | - | 364
278 - Health Care Services Review - Request For Review Response
D | 2010FA | PER04 | - | 364
D | 2010FA | PER06 | - | 364
D | 2010FA | 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 - Request For Review
D | 2010F | PER02 | - | 93
278 - Health Care Services Review - Request For Review Response
D | 2010FA | 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 - Request For Review
D | 2010F | NM104 | - | 1036
278 - Health Care Services Review - Request For Review Response
D | 2010FA | 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 - Request For Review
D | 2010F | NM109 | - | 67
278 - Health Care Services Review - Request For Review Response
D | 2010FA | 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 - Request For Review
D | 2010F | NM103 | - | 1035
278 - Health Care Services Review - Request For Review Response
D | 2010FA | 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 - Request For Review
D | 2010F | NM105 | - | 1037
278 - Health Care Services Review - Request For Review Response
D | 2010FA | 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 - Request For Review
D | 2010F | NM106 | - | 1038
278 - Health Care Services Review - Request For Review Response
D | 2010FA | 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 - Request For Review
D | 2010F | NM107 | - | 1039
278 - Health Care Services Review - Request For Review Response
D | 2010FA | 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 - Request For Review
D | 2010F | N403 | - | 116
278 - Health Care Services Review - Request For Review Response
D | 2010FA | 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 - Request For Review
D | 2010F | N402 | - | 156
278 - Health Care Services Review - Request For Review Response
D | 2010FA | 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 - Request For Review
D | 2010F | REF02 | - | 127
278 - Health Care Services Review - Request For Review Response
D | 2010FA | 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 - Request For Review
D | 2000F | TRN02 | - | 127
278 - Health Care Services Review - Request For Review Response
D | 2000F | TRN02 | - | 127

Service Type Code
Code identifying the classification of service.
278 - Health Care Services Review - Request For Review
D | 2000E | UM03 | - | 1365
D | 2000F | UM03 | - | 1365
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
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 - Request For Review Response
D | 2000E | HSD02 | - | 380
D | 2000F | SV104 | - | 380
D | 2000F | SV205 | - | 380
D | 2000F | SV306 | - | 380
D | 2000F | HSD02 | - | 380

State or Province Code
Code (Standard State/Province) as defined by appropriate government agency.
278 - Health Care Services Review - Request For Review
D | 2000E | UM05 | C024-04 | 156

Stretcher Purpose Description
Free-form description of the purpose of the use of a stretcher during ambulance service.
278 - Health Care Services Review - Request For Review
D | 2000E | CR110 | - | 352

Subluxation Level Code
Code identifying the specific level of subluxation.
278 - Health Care Services Review - Request For Review
D | 2000E | CR203 | - | 1367
D | 2000E | CR204 | - | 1367
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
H | | BHT03 | - | 127
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2010C | N301 | - | 166
D | 2010C | N302 | - | 166
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2010C | DMG02 | - | 1251
278 - Health Care Services Review - Request For Review Response
D | 2010C | DMG02 | - | 1251

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

Subscriber First Name
The first name of the insured individual or subscriber to the coverage.
278 - Health Care Services Review - Request For Review
D | 2010C | NM104 | - | 1036
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2010C | DMG03 | - | 1068
278 - Health Care Services Review - Request For Review Response
D | 2010C | DMG03 | - | 1068

Subscriber Last Name
The surname of the insured individual or subscriber to the coverage.
278 - Health Care Services Review - Request For Review
D | 2010C | NM103 | - | 1035
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2010C | NM105 | - | 1037
278 - Health Care Services Review - Request For Review Response
D | 2010C | NM105 | - | 1037

Subscriber Name Prefix
The name prefix of the subscriber to the indicated coverage or policy.
278 - Health Care Services Review - Request For Review
D | 2010C | NM106 | - | 1038
278 - Health Care Services Review - Request For Review Response
D | 2010C | NM106 | - | 1038

Subscriber Name Suffix
Suffix of the insured individual or subscriber to the coverage.
278 - Health Care Services Review - Request For Review
D | 2010C | NM107 | - | 1039
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2010C | N403 | - | 116
278 - Health Care Services Review - Request For Review Response
D | 2010C | N403 | - | 116

Subscriber Primary Identifier
Primary identification number of the subscriber to the coverage.
278 - Health Care Services Review - Request For Review
D | 2010C | NM109 | - | 67
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2010C | N402 | - | 156
278 - Health Care Services Review - Request For Review Response
D | 2010C | N402 | - | 156

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

Surgery Date
Requested, anticipated, or actual date of surgery.
278 - Health Care Services Review - Request For Review
D | 2000E | CR609 | - | 373

Surgical Procedure Code
Code describing the surgical procedure most relevant to the care being rendered.
278 - Health Care Services Review - Request For Review
D | 2000E | CR611 | - | 1137

Time Period Qualifier
Code defining the type of time period.
278 - Health Care Services Review - Request For Review
D | 2000E | HSD05 | - | 615
D | 2000F | HSD05 | - | 615
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2000F | TOO02 | - | 1271
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
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 - Request For Review Response
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 - Request For Review
D | 2000E | TRN04 | - | 127
D | 2000F | TRN04 | - | 127
278 - Health Care Services Review - Request For Review Response
D | 2000E | TRN04 | - | 127
D | 2000F | TRN04 | - | 127

Trace Assigning Entity Identifier
Identifies the organization assigning the trace number.
278 - Health Care Services Review - Request For Review
D | 2000E | TRN03 | - | 509
D | 2000F | TRN03 | - | 509
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2000E | TRN01 | - | 481
D | 2000F | TRN01 | - | 481
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | | SE01 | - | 96
278 - Health Care Services Review - Request For Review Response
D | | SE01 | - | 96

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

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

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

Transaction Set Identifier Code
Code uniquely identifying a Transaction Set.
278 - Health Care Services Review - Request For Review
H | | ST01 | - | 143
278 - Health Care Services Review - Request For Review Response
H | | ST01 | - | 143

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

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

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

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

Treatment Series Number
Number this treatment is in the series of services.
278 - Health Care Services Review - Request For Review
D | 2000E | CR201 | - | 609
278 - Health Care Services Review - Request For Review Response
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 - Request For Review
D | 2000E | HSD03 | - | 355
D | 2000E | CR101 | - | 355
D | 2000E | CR105 | - | 355
D | 2000F | SV103 | - | 355
D | 2000F | SV204 | - | 355
D | 2000F | HSD03 | - | 355
278 - Health Care Services Review - Request For Review Response
D | 2000E | HSD03 | - | 355
D | 2000E | CR105 | - | 355
D | 2000F | SV103 | - | 355
D | 2000F | SV204 | - | 355
D | 2000F | HSD03 | - | 355

Utilization Management Organization (UMO) Contact Communication Number
Complete UMO contact communications number, including country or area code when applicable.
278 - Health Care Services Review - Request For Review Response
D | 2010A | PER04 | - | 364
D | 2010A | PER06 | - | 364
D | 2010A | PER08 | - | 364

Utilization Management Organization (UMO) Contact Name
Name identifying the UMO's contact person.
278 - Health Care Services Review - Request For Review Response
D | 2010A | PER02 | - | 93

Utilization Management Organization (UMO) First Name
First name of the individual, such as the primary care provider, associated with the request for a health care services review.
278 - Health Care Services Review - Request For Review
D | 2010A | NM104 | - | 1036
278 - Health Care Services Review - Request For Review Response
D | 2010A | NM104 | - | 1036

Utilization Management Organization (UMO) Identifier
Code uniquely identifying the Utilization Management Organization (UMO).
278 - Health Care Services Review - Request For Review
D | 2010A | NM109 | - | 67
278 - Health Care Services Review - Request For Review Response
D | 2010A | NM109 | - | 67

Utilization Management Organization (UMO) Last or Organization Name
Name of the Utilization Management Organization (UMO) or last name of the party associated with the request for a health care services review.
278 - Health Care Services Review - Request For Review
D | 2010A | NM103 | - | 1035
278 - Health Care Services Review - Request For Review Response
D | 2010A | NM103 | - | 1035

Utilization Management Organization (UMO) Middle Name or Initial
Middle name or middle initial of the individual, such as the primary care provider, associated with the request for a health care services review.
278 - Health Care Services Review - Request For Review
D | 2010A | NM105 | - | 1037
278 - Health Care Services Review - Request For Review Response
D | 2010A | NM105 | - | 1037

Utilization Management Organization (UMO) Name Suffix
Suffix to the name of the individual, such as the primary care provider, associated with the request for a health care services review.
278 - Health Care Services Review - Request For Review
D | 2010A | NM107 | - | 1039
278 - Health Care Services Review - Request For Review Response
D | 2010A | NM107 | - | 1039

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

X-ray Availability Indicator
Indicates if X-Rays are on file for chiropractor spinal manipulation.
278 - Health Care Services Review - Request For Review
D | 2000E | CR212 | - | 1073

Appendix F. FHIR PAS Claim to X12 278 Request

This implementation guide describes the intersection of X12 and Da Vinci data elements, so the information can be used consistently across implementations, regardless of syntax. Section 1.13, the FHIR mapping information provided in Section 2, and Appendices F and G are not part of the X12 EDI Standard or TR3 but are provided as a courtesy for organizations who are implementing multiple syntaxes.

These instructions delineate how the data maps between the FHIR Claim elements and the associated X12 278 Request segments and elements.

Please review the information in Section 1.13 of this Implementation Guide for background and details on the mapping legend.

Segment - Loop Field Mapping/Notes Usage
STThe data elements in this segment are not defined in the PAS Claim profile because the values are hardcoded or derived. Implement with version: STU 1.0.0R
ST01'278' Implement with version: STU 1.0.0R
ST02This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0R
ST03'005010X217' Implement with version: STU 1.0.0R
BHTThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0R
BHT01'0007' Implement with version: STU 1.0.0R
BHT02'13' Implement with version: STU 1.0.0R
BHT03Bundle.identifier.value Implement with version: STU 1.0.0R
BHT04Bundle.timestamp Extract the date portion of the Bundle.timestamp to populate BHT04 Implement with version: STU 1.0.0R
BHT05Bundle.timestamp Extract the time portion of the Bundle.timestamp to populate BHT05 Implement with version: STU 1.0.0R
BHT06This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HL - 2000AThe data elements in this segment are not defined in the PAS Claim profile because the values are hardcoded or derived. Implement with version: STU 1.0.0R
HL01'1' Implement with version: STU 1.0.0R
HL03'20' Implement with version: STU 1.0.0R
HL04'1' Implement with version: STU 1.0.0R
NM1 - 2010AClaim.insurer => Organization The Claim.insurer will point to a Organization in the Bundle. Locate the Organization pointed at in the Claim and use that Organization for all of the fields in the 2010A Loop Implement with version: STU 1.0.0R
NM101Organization.type[0].coding[0].code Implement with version: STU 1.0.0R
NM102'2' Implement with version: STU 1.0.0R
NM103Organization.name Implement with version: STU 1.0.0S
NM104This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
NM105This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
NM107This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
NM108Organization.identifier[0].type.coding[0].code The value from the system attribute is translated as follows: '46' -> '46' 'U' -> 'PI' Implement with version: STU 1.1.0R
NM109Organization.identifier[0].value Implement with version: STU 1.0.0R
HL - 2000BThe data elements in this segment are not defined in the PAS Claim profile because the values are hardcoded or derived. Implement with version: STU 1.0.0R
HL01'2' Implement with version: STU 1.0.0R
HL02'1' Implement with version: STU 1.0.0R
HL03'21' Implement with version: STU 1.0.0R
HL04'1' Implement with version: STU 1.0.0R
NM1 - 2010BClaim.provider => Organization The Claim.provider will point to a Organization in the Bundle. Locate the Organization pointed at in the Claim and use that Organization for all of the fields in the 2010B Loop. Implement with version: STU 1.0.0R
NM101Organization.type[0].coding[0].code Implement with version: STU 1.0.0R
NM102'2' Implement with version: STU 1.0.0R
NM103Organization.name Implement with version: STU 1.0.0S
NM104This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
NM105This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
NM107This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
NM108'XX' Implement with version: STU 1.0.0R
NM109Organization.identifier[0].value Implement with version: STU 1.0.0R
REF - 2010BThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
N3 - 2010BThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
N301Organization.address[0].line[0] Implement with version: STU 1.0.0R
N302Organization.address[0].line[1] Implement with version: STU 1.0.0S
N4 - 2010BThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
N401Organization.address[0].city Implement with version: STU 1.0.0R
N402Organization.address[0].state Implement with version: STU 1.0.0S
N403Organization.address[0].postalCode Implement with version: STU 1.0.0S
N404Organization.address[0].country Implement with version: STU 1.0.0S
N407This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
PER - 2010BThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
PER01'IC' Implement with version: STU 1.0.0R
PER02Organization.contact[0].name Implement with version: STU 1.0.0S
PER03Organization.contact[0].telecom[0].system The value from the system attribute is translated as follows: 'phone' -> 'TE' 'fax' -> 'FX' 'email' -> 'EM' 'pager' -> 'TE' 'url' -> 'UR' 'sms' -> 'TE' 'other' -> cannot be translated Implement with version: STU 1.0.0S
PER04Organization.contact[0].telecom[0].value If the value of system is 'phone', this value must be parsed to determine if an extension is present (see ITU-T E.123 for format of telephone values). If an extension is present, the remove the extension part of the phone number and place in PER06 and set PER05 to 'EX' Implement with version: STU 1.0.0S
PER05Organization.contact[0].telecom[1].system | 'EX' See PER04 if PER03 is 'TE' otherwise select the next telecom in contact[0] and translate the system as follows: 'phone' -> 'TE' 'fax' -> 'FX' 'email' -> 'EM' 'pager' -> 'TE' 'url' -> 'UR' 'sms' -> 'TE' 'other' -> cannot be translated Implement with version: STU 1.0.0S
PER06Organization.contact[0].telecom[1].value | extracted extension If PER05 is set to 'EX' this will be the extract value for the extension from PER04 Otherwise this is refer to PER04 for rules on formatting Implement with version: STU 1.0.0S
PER07Organization.contact[0].telecom[n].system | 'EX' See PER06 if PER05 is 'TE' otherwise select the next telecom in contact[0] and translate the system as follows: 'phone' -> 'TE' 'fax' -> 'FX' 'email' -> 'EM' 'pager' -> 'TE' 'url' -> 'UR' 'sms' -> 'TE' 'other' -> cannot be translated Implement with version: STU 1.0.0S
PER08Organization.contact[0].telecom[n].value | extracted extension If PER07 is set to 'EX' this will be the extract value for the extension from PER06 Otherwise this is refer to PER04 for rules on formatting Implement with version: STU 1.0.0S
PRV - 2010BThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HL - 2000CThe data elements in this segment are not defined in the PAS Claim profile because the values are hardcoded or derived. Implement with version: STU 1.0.0R
HL01'3' Implement with version: STU 1.0.0R
HL02'2' Implement with version: STU 1.0.0R
HL03'22' Implement with version: STU 1.0.0R
HL04'1' Implement with version: STU 1.0.0R
NM1 - 2010CThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Claim.insurance[0].coverage => Coverage.subscriber => Patient Locate the Coverage Resource in the Bundle that is referenced from the Claim.insurance[0].coverage. Then locate the Patient Resource in the Bundle referenced in the Coverage.subscriber attribute. Use the Patient Resource for all of the segments of the 2010C Loop Implement with version: STU 1.0.0R
NM101'IL' Implement with version: STU 1.0.0R
NM102'1' Implement with version: STU 1.0.0R
NM103Patient.name[0].family Implement with version: STU 1.0.0S
NM104Patient.name[0].given[0] Implement with version: STU 1.0.0S
NM105Patient.name[0].given[1] Implement with version: STU 1.0.0S
NM106Patient.name[0].prefix[0] Implement with version: STU 1.0.0S
NM107Patient.name[0].suffix[0] Implement with version: STU 1.0.0S
NM108'MI' Implement with version: STU 1.1.0R
NM109Patient.identifier[0].value Implement with version: STU 1.0.0R
REF - 2010CThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.1.0S
REF01Patient.identifier[1].type.coding[0].code Translate as follows: '1L' -> '1L' '3L' -> '3L' '6P' -> '6P' 'DP' -> 'DP' 'EJ' -> 'EJ' 'MC' -> 'F6' 'HJ' -> 'HJ' 'IG' -> 'IG' 'N6' -> 'N6' 'MA' -> 'NQ' 'SS' -> 'SY' Implement with version: STU 1.1.0R
REF02Patient.identifier[1].value Implement with version: STU 1.1.0R
N3 - 2010CThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
N301Patient.address[0].line[0] Implement with version: STU 1.0.0R
N302Patient.address[0].line[1] Implement with version: STU 1.0.0S
N4 - 2010CThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
N401Patient.address[0].city Implement with version: STU 1.0.0R
N402Patient.address[0].state Implement with version: STU 1.0.0S
N403Patient.address[0].postalCode Implement with version: STU 1.0.0S
N404Patient.address[0].country Implement with version: STU 1.0.0S
N407This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
DMG - 2010CThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
DMG01'D8' Implement with version: STU 1.0.0R
DMG02Patient.birthDate The Patient.birthDate format is YYYY-MM-DD and will need to be converted. Implement with version: STU 1.1.0R
DMG03Patient.gender The value from gender must be translated to an X12 specific value as follows: 'female' -> 'F' 'male' -> 'M' 'unknown' -> 'U' 'other' -> 'U' Implement with version: STU 1.0.0S
INS - 2010CThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. This segment will only be populated when Patient.extension[n] has an occurrence of an extension where the uri atttribute is 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- militaryStatus' Implement with version: STU 1.1.0S
INS01'Y' Implement with version: STU 1.0.0R
INS02'18' Implement with version: STU 1.0.0R
INS08Patient.extension(militaryStatus).valueCodeableConcept.coding[0].code The militaryStatus extension has a url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-milita ryStatus' Implement with version: STU 1.0.0R
HL - 2000DThe data elements in this segment are not defined in the PAS Claim profile because the values are hardcoded or derived. The 2000D is only created when the patient is other than the covered subscriber. Formally, create a 2000D when Coverage referenced by Claim.insurance[0].coverage has Coverage.relationship.coding[0].code NOT equal 'self' Implement with version: STU 1.0.0S
HL01Create this element following HL segment and element rules. Implement with version: STU 1.0.0R
HL02Create this element following HL segment and element rules. Implement with version: STU 1.0.0R
HL03'23' Implement with version: STU 1.0.0R
HL04'1' Implement with version: STU 1.0.0R
NM1 - 2010DThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. The 2000D is only created when the patient is not the covered subscriber. Create a 2000D when Coverage referenced by Claim.insurance[0].coverage has Coverage.relationship.coding[0].code NOT equal 'self' Implement with version: STU 1.0.0R
NM101'QC' Implement with version: STU 1.0.0R
NM102'1' Implement with version: STU 1.0.0R
NM103Patient.name[0].family Implement with version: STU 1.0.0S
NM104Patient.name[0].given[0] Implement with version: STU 1.0.0S
NM105Patient.name[0].given[1] Implement with version: STU 1.0.0S
NM107Patient.name[0].suffix[0] Implement with version: STU 1.0.0S
REF - 2010DThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.1.0S
REF01Patient.identifier[0].type.coding[0].code Translated as follows: 'EJ' -> 'EJ' 'SB' -> 'SY' Implement with version: STU 1.1.0R
REF02Patient.identifier[0].value Implement with version: STU 1.1.0R
N3 - 2010DThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
N301Patient.address[0].line[0] Implement with version: STU 1.0.0R
N302Patient.address[0].line[1] Implement with version: STU 1.0.0S
N4 - 2010DThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
N401Patient.address[0].city Implement with version: STU 1.0.0R
N402Patient.address[0].state Implement with version: STU 1.0.0S
N403Patient.address[0].postalCode Implement with version: STU 1.0.0S
N404Patient.address[0].country Implement with version: STU 1.0.0S
N407This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
DMG - 2010DThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
DMG01'D8' Implement with version: STU 1.0.0R
DMG02Patient.birthDate The Patient.birthDate format is YYYY-MM-DD and will need to be converted. Implement with version: STU 1.1.0R
DMG03Patient.gender The value from gender must be translated to an X12 specific value as follows: 'female' -> 'F' 'male' -> 'M' 'unknown' -> 'U' 'other' -> 'U' Implement with version: STU 1.0.0S
INS - 2010DThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
INS01'N' Implement with version: STU 1.0.0R
INS02Coverage.relationship The value from Coverage.relationship.coding[0].code will be translated as follows: 'child' -> '19' 'parent' -> 'G8' 'spouse' -> '01' 'common' -> 'G8' 'other' -> 'G8' 'self' -> should not occur, see note on 2000D 'injured' -> 'G8' Implement with version: STU 1.0.0R
INS17Patient.multipleBirthInteger Implement with version: STU 1.0.0S
HL - 2000EThe data elements in this segment are not defined in the PAS Claim profile because the values are hardcoded or derived. Implement with version: STU 1.0.0R
HL01Create this element following HL segment and element rules. Implement with version: STU 1.0.0R
HL02Create this element following HL segment and element rules. Implement with version: STU 1.0.0R
HL03'EV' Implement with version: STU 1.0.0R
HL04'1' Implement with version: STU 1.0.0R
TRN - 2000EThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
TRN01'1' Implement with version: STU 1.0.0R
TRN02Claim.identifier[0].value Implement with version: STU 1.0.0R
TRN03Claim.identifier[0].assigner.identifier.value Implement with version: STU 1.0.0R
TRN04Claim.identifier[0].extension(identifierSubDepartment).valueString The subDepartment extension has a url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- identifierSubDepartment' Implement with version: STU 1.1.0S
UM - 2000EThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0R
UM01Claim.item[0].extension(serviceItemRequestType).valueCodeableConcept.cod ing[0].code The serviceItemRequestType extension has a url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-servic eItemRequestType' Implement with version: STU 1.0.0R
UM02Claim.item[0].extension(certificationType).valueCodeableConcept.coding[0 ].code The certificationType extension has a url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-certif icationType' Implement with version: STU 1.0.0R
UM03Claim.item[0].category.coding[0].code Implement with version: STU 1.0.0S
UM04-01Claim.item[0].locationCodeableConcept.coding[0].code Implement with version: STU 1.0.0R
UM04-02Claim.item[0].locationCodeableConcept.coding[0].system Populate UM04-02 with the value in coding[0].system translated as follows: 'https://www.nubc.org/CodeSystem/TypeOfBill' -> 'A' 'https://www.cms.gov/Medicare/Coding/place-of-service-codes/Plac e_of_Service_Code_Set' -> 'B' Implement with version: STU 1.0.0R
UM05-01Claim.accident.type.coding[0].code Implement with version: STU 1.0.0R
UM05-02This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
UM05-03This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
UM05-04Claim.accident.locationAddress.state Implement with version: STU 1.0.0S
UM05-05Claim.accident.locationAddress.country Implement with version: STU 1.0.0S
UM06Claim.extension(levelOfServiceCode).valueCodeableConcept.coding[0].code< br/>The levelOfServiceCode extension has a url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-levelO fServiceCode' Implement with version: STU 1.0.0S
UM07This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
UM08This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
UM09This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
UM10This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
REF - 2000EThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
REF - 2000EThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
DTP - 2000EThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
DTP01'439' Implement with version: STU 1.0.0R
DTP02'D8' Implement with version: STU 1.0.0R
DTP03Claim.accident.date The Claim.accident.date may be in the format of CCYY or CCYYMM or CCYYMMDD Implement with version: STU 1.0.0R
DTP - 2000EThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
DTP - 2000EThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
DTP - 2000EThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
DTP - 2000EThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. An Event Date DTP segment is created when the Claim has a supportingInfo attribute for a PatientEvent determined by: supportingInfo[n].category.coding[0].system set to 'http://hl7.org/fhir/us/davinci-pas/CodeSystem-PASSupportingInfoType' and supportingInfo[n].category.coding[0].code set to 'patientEvent' Implement with version: STU 1.1.0S
DTP01'AAH' Implement with version: STU 1.0.0R
DTP02'D8' or 'RD8' If the supportingInfo[n] has an attribute named 'timingDate' set DTP02 to 'D8' Otherwise set DTP02 to 'RD8' Implement with version: STU 1.0.0R
DTP03Claim.supportingInfo(PatientEvent).timingDate | Claim.supportingInfo(PatientEvent).timingPeriod If the supportingInfo[n] has the attribute timingDate set DTP03 to the value of timingDate Otherwise set DTP03 to '-' The date format is YYYY-MM-DD and will need to be converted. Implement with version: STU 1.1.0R
DTP - 2000EThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. An Admission Date DTP segment is created when the Claim has a supportingInfo attribute for AdmissionDates determined by: supportingInfo[n].category.coding[0].system set to 'http://hl7.org/fhir/us/davinci-pas/CodeSystem-PASSupportingInfoType' and supportingInfo[n].category.coding[0].code set to 'admissionDates' Implement with version: STU 1.1.0S
DTP01'435' Implement with version: STU 1.0.0R
DTP02'D8' or 'RD8' If the supportingInfo[n] has an attribute named 'timingDate' set DTP02 to 'D8' Otherwise set DTP02 to 'RD8' Implement with version: STU 1.1.0R
DTP03Claim.supportingInfo(AdmissionDates).timingPeriod.start The date format is YYYY-MM-DD and will need to be converted. Implement with version: STU 1.1.0R
DTP - 2000EThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. A Discharge Date DTP segment is created when the Claim has a supportingInfo attribute for a DischargeDates determined by: supportingInfo[n].category.coding[0].system set to 'http://hl7.org/fhir/us/davinci-pas/CodeSystem-PASSupportingInfoType' and supportingInfo[n].category.coding[0].code set to 'dischargeDates' Implement with version: STU 1.1.0S
DTP01'096' Implement with version: STU 1.0.0R
DTP02'D8' Implement with version: STU 1.0.0R
DTP03Claim.supportingInfo(DischargeDates).timingDate The date format is YYYY-MM-DD and will need to be converted. Implement with version: STU 1.1.0R
HI - 2000EThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
HI01-01Use the values from Claim.diagnosis[0] in the mapping table DiagnosisTypeCodeMapping to determine this value. Implement with version: STU 1.0.0R
HI01-02Claim.diagnosis[0].diagnosisCodeableConcept.coding[0].code Implement with version: STU 1.0.0R
HI01-03This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HI01-04This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HI02-01Use the values from Claim.diagnosis[1] in the mapping table DiagnosisTypeCodeMapping to determine this value. Implement with version: STU 1.1.0R
HI02-02Claim.diagnosis[1].diagnosisCodeableConcept.coding[0].code Implement with version: STU 1.0.0R
HI02-03This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HI02-04This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HI03-01Use the values from Claim.diagnosis[2] in the mapping table DiagnosisTypeCodeMapping to determine this value. Implement with version: STU 1.1.0R
HI03-02Claim.diagnosis[2].diagnosisCodeableConcept.coding[0].code Implement with version: STU 1.0.0R
HI03-03This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HI03-04This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HI04-01Use the values from Claim.diagnosis[3] in the mapping table DiagnosisTypeCodeMapping to determine this value. Implement with version: STU 1.1.0R
HI04-02Claim.diagnosis[3].diagnosisCodeableConcept.coding[0].code Implement with version: STU 1.0.0R
HI04-03This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HI04-04This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HI05-01Use the values from Claim.diagnosis[4] in the mapping table DiagnosisTypeCodeMapping to determine this value. Implement with version: STU 1.1.0R
HI05-02Claim.diagnosis[4].diagnosisCodeableConcept.coding[0].code Implement with version: STU 1.0.0R
HI05-03This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HI05-04This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HI06-01Use the values from Claim.diagnosis[5] in the mapping table DiagnosisTypeCodeMapping to determine this value. Implement with version: STU 1.1.0R
HI06-02Claim.diagnosis[5].diagnosisCodeableConcept.coding[0].code Implement with version: STU 1.0.0R
HI06-03This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HI06-04This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HI07-01Use the values from Claim.diagnosis[6] in the mapping table DiagnosisTypeCodeMapping to determine this value. Implement with version: STU 1.1.0R
HI07-02Claim.diagnosis[6].diagnosisCodeableConcept.coding[0].code Implement with version: STU 1.0.0R
HI07-03This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HI07-04This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HI08-01Use the values from Claim.diagnosis[7] in the mapping table DiagnosisTypeCodeMapping to determine this value. Implement with version: STU 1.1.0R
HI08-02Claim.diagnosis[7].diagnosisCodeableConcept.coding[0].code Implement with version: STU 1.0.0R
HI08-03This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HI08-04This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HI09-01Use the values from Claim.diagnosis[8] in the mapping table DiagnosisTypeCodeMapping to determine this value. Implement with version: STU 1.1.0R
HI09-02Claim.diagnosis[8].diagnosisCodeableConcept.coding[0].code Implement with version: STU 1.0.0R
HI09-03This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HI09-04This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HI10-01Use the values from Claim.diagnosis[9] in the mapping table DiagnosisTypeCodeMapping to determine this value. Implement with version: STU 1.1.0R
HI10-02Claim.diagnosis[9].diagnosisCodeableConcept.coding[0].code Implement with version: STU 1.0.0R
HI10-03This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HI10-04This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HI11-01Use the values from Claim.diagnosis[10] in the mapping table DiagnosisTypeCodeMapping to determine this value. Implement with version: STU 1.1.0R
HI11-02Claim.diagnosis[10].diagnosisCodeableConcept.coding[0].code Implement with version: STU 1.0.0R
HI11-03This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HI11-04This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HI12-01Use the values from Claim.diagnosis[11] in the mapping table DiagnosisTypeCodeMapping to determine this value. Implement with version: STU 1.1.0R
HI12-02Claim.diagnosis[11].diagnosisCodeableConcept.coding[0].code Implement with version: STU 1.0.0R
HI12-03This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HI12-04This data element is not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HSD - 2000EThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
CRC - 2000EThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
CRC - 2000EThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
CRC - 2000EThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
CRC - 2000EThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
CRC - 2000EThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
CRC - 2000EThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
CRC - 2000EThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
CL1 - 2000EThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Claim.supportingInfo(InstitutionalEncounter).valueReference.referen ce => Encounter The Claim has a supportingInfo attribute for a InstitutionalEncounter determined by: supportingInfo[n].category.coding[0].system set to 'http://hl7.org/fhir/us/davinci-pas/CodeSystem-PASSupportingInfoType' and supportingInfo[n].category.coding[0].code set to 'institutionalEncounter' Implement with version: STU 1.1.0S
CL101Encounter.type[0].coding[0].code Implement with version: STU 1.0.0S
CL102Encounter.hospitalization.admitSource.coding[0].code Implement with version: STU 1.0.0S
CL103Encounter.extension(patientStatus).valueCodeableConcept.coding[0].code The patientStatus extension has a url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- patientStatus' Implement with version: STU 1.0.0S
CL104Encounter.extension(nursingHomeResidentialStatus).valueCodeableConcept.c oding[0].code The nursingHomeResidentialStatus extension has a url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- nursingHomeResidentialStatus' Implement with version: STU 1.0.0S
CR1 - 2000EThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
CR2 - 2000EThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
CR5 - 2000EThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
CR6 - 2000EThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
PWK - 2000EThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Claim.supportingInfo(AdditionalInformation).valueReference.re ference => DocumentReference If a Claim.supportingInfo(AdditionalInformation) item exists create an initial PWK which will provide a link to the 275 Unsolicited message containing the Bundle content (mapping to the X316-275 described elsewhere). Create additional PWK segments as follows: Create a Patient Event Level PWK segment for the first nine supportingInfo(AdditionalInformation) structure that are NOT referenced by a Service level PWK Claim.item[n],informationSequence[n]. The Claim will have a supportingInfo attribute for a AdditionalInformation determined by: supportingInfo[n].category.coding[0].system set to 'http://hl7.org/fhir/us/davinci-pas/CodeSystem-PASSupportingInfoType' and supportingInfo[n].category.coding[0].code set to 'additionalInformation' Implement with version: STU 1.0.0S
PWK01The first PWK segment will contain '77' |Additional PWK segments will use the DocumentReference.type.coding[0].code Preferred value set is LOINC (not X12) Implement with version: STU 1.0.0R
PWK02'EL' Implement with version: STU 1.0.0R
PWK05'AC' Implement with version: STU 1.0.0S
PWK06The first PWK segment will contain the Claim.identifier[0].value | Additional PWK segments will use the DocumentReference.masterIdentifier.value Implement with version: STU 1.0.0S
PWK07The first PWK segment will contain no value | Additional PWK segments will use the DocumentReference.description Implement with version: STU 1.0.0S
MSG - 2000EThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Creation of a MSG segment at the Patient Event level is done for the first supportingInfo(MessageText) that is NOT referenced from any Claim.item[n].informationSequence[n] Implement with version: STU 1.0.0S
MSG01Claim.supportingInfo(MessageText).valueString The Claim has a supportingInfo attribute for a MessageText determined by: supportingInfo[n].category.coding[0].system set to 'http://hl7.org/fhir/us/davinci-pas/CodeSystem-PASSupportingInfoType' and supportingInfo[n].category.coding[0].code set to 'freeFormMessage' Implement with version: STU 1.0.0R
NM1 - 2010EAThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Claim.careTeam[n].provider can point to either an Organization or Practitioner Resource. For each Claim.careTeam[n].extension(careTeamClaimScope).valueBoolean = true (maximum of 14). Implement with version: STU 1.1.0S
NM101Claim.careTeam[n].role.coding[0].code Implement with version: STU 1.0.0R
NM102If the provider is a Practitioner Resource this value is '1' If the provider is a Organization Resource this value is '2' Implement with version: STU 1.0.0R
NM103Practitioner.name[0].family | Organization.name Implement with version: STU 1.0.0S
NM104Practitioner.name[0].given[0] | not used on Organization Implement with version: STU 1.0.0S
NM105Practitioner.name[0].given[1] | not used on Organization Implement with version: STU 1.0.0S
NM106Practitioner.name[0].prefix[0] | not used on Organization Implement with version: STU 1.0.0S
NM107Practitioner.name[0].suffix[0] | not used on Organization Implement with version: STU 1.0.0S
NM108Practitioner.identifier[0].type.coding[0].code | Organization.identifier[0].type.coding[0].code The value from the code attribute is translated as follows: 'EN' -> '24' 'SB' -> '34' '46' -> '46' 'NPI' -> 'XX' Implement with version: STU 1.1.0S
NM109Practitioner.identifier[0].value | Organization.identifier[0].value Implement with version: STU 1.0.0S
REF - 2010EAThe data elements in this segment are defined in the PAS Claim Inquiry profile, see the FHIR Mapping instructions for each data element below. If Organization.identifier[n].type.coding[0].code is equal to 'SL' (State License Number), do not create this REF Segment. Implement with version: STU 1.1.0S
REF01Practitioner.identifier[1].type.coding[0].code | Organization.identifier[1].type.coding[0].code The value from the code attribute is translated as follows: 'SL' -> '0B' 'FI' -> '1J' 'EN' -> 'EI' 'N5' -> 'N5' 'N7' -> 'N7' 'SB' -> 'SY' 'ZH' -> 'ZH' Implement with version: STU 1.1.0R
REF02Practitioner.identifier[1].value | Organization.identifier[1].value Implement with version: STU 1.0.0R
REF03Practitioner.identifier[1].extension(jurisdiction).coding[0].code Implement with version: STU 1.1.0S
N3 - 2010EAThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
N301Practitioner.address[0].line[1] | Organization.address[0].line[1] Implement with version: STU 1.0.0R
N302Practitioner.address[0].line[2] | Organization.address[0].line[2] Implement with version: STU 1.0.0S
N4 - 2010EAThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
N401Practitioner.address[0].city | Organization.address[0].city Implement with version: STU 1.0.0R
N402Practitioner.address[0].state | Organization.address[0].state Implement with version: STU 1.0.0S
N403Practitioner.address[0].postalCode | Organization.address[0].postalCode Implement with version: STU 1.0.0S
N404Practitioner.address[0].country | Organization.address[0].country Implement with version: STU 1.0.0S
N407Practitioner.address[0].district | Organization.address[0].district Implement with version: STU 1.0.0S
PER - 2010EAThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
PER01'IC' Implement with version: STU 1.0.0R
PER02no value when Practitioner | Organization.contact[0].name.text Implement with version: STU 1.0.0S
PER04Practitioner.telecom[0].value | Organization.contact[0].telecom[0].value If the value of system is 'phone', this value must be parsed to determine if an extension is present (see ITU-T E.123 for format of telephone values). If an extension is present, the remove the extension part of the phone number and place in PER06 and set PER05 to 'EX' Implement with version: STU 1.0.0S
PER05Practitioner.telecom[1].system | Organization.contact[0].telecom[1].system | 'EX' See PER04 if PER03 is 'TE' otherwise select the next telecom in contact[0] and translate the system as follows: 'phone' -> 'TE' 'fax' -> 'FX' 'email' -> 'EM' 'pager' -> 'TE' 'url' -> 'UR' 'sms' -> 'TE' 'other' -> cannot be translated Implement with version: STU 1.0.0S
PER06Practitioner.telecom[1].value | Organization.contact[0].telecom[1].value | extracted extension If PER05 is set to 'EX' this will be the extract value for the extension from PER04 Otherwise this is refer to PER04 for rules on formatting Implement with version: STU 1.0.0S
PER07Practitioner.telecom[n].system | Organization.contact[0].telecom[n].system | 'EX' See PER06 if PER05 is 'TE' otherwise select the next telecom in contact[0] and translate the system as follows: 'phone' -> 'TE' 'fax' -> 'FX' 'email' -> 'EM' 'pager' -> 'TE' 'url' -> 'UR' 'sms' -> 'TE' 'other' -> cannot be translated Implement with version: STU 1.0.0S
PER08Practitioner.telecom[n].value | Organization.contact[0].telecom[n].value | extracted extension If PER07 is set to 'EX' this will be the extract value for the extension from PER06 Otherwise this is refer to PER04 for rules on formatting Implement with version: STU 1.0.0S
PRV - 2010EAThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Only populated when the careTeam[n].provider is a Practitioner Implement with version: STU 1.0.0S
PRV01The qualifier code used in this qualifier element is mapped from the qualifier codes used in NM101, Claim.careTeam[n].role.coding[0].code. Implement with version: STU 1.0.0R
PRV02'PXC' Implement with version: STU 1.0.0R
PRV03Claim.careTeam[n].qualification.coding[0].code Implement with version: STU 1.0.0R
NM1 - 2010EBThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
N3 - 2010EBThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0R
N4 - 2010EBThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0R
NM1 - 2010ECThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
REF - 2010ECThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0R
DTP - 2010ECThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0R
HL - 2000FThe data elements in this segment are not defined in the PAS Claim profile because the values are hardcoded or derived. Each occurrence of Claim.item[n] will have a corresponding 2000F occurrence Implement with version: STU 1.0.0S
HL01Create this element following HL segment and element rules. Implement with version: STU 1.0.0R
HL02Create this element following HL segment and element rules. Implement with version: STU 1.0.0R
HL03'SS' Implement with version: STU 1.0.0R
HL04Create this element following HL segment and element rules. Implement with version: STU 1.0.0R
TRN - 2000FCreate one TRN segment for each itemTraceNumber extension up to three (3) in the PAS Claim Inquiry. Implement with version: STU 1.1.0S
TRN01'1' Implement with version: STU 1.0.0R
TRN02Claim.item[n].extension(itemTraceNumber).valueIdentifier.value The itemTraceNumber extension has: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-itemTr aceNumber' Implement with version: STU 1.0.0R
TRN03Claim.item[n].extension(itemTraceNumber).valueIdentifier.assigner.value The itemTraceNumber extension has: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- itemTraceNumber' Implement with version: STU 1.0.0R
TRN04Claim.item[n].extension(itemTraceNumber).extension (identifierSubDepartment).valueString The subDepartment extension has a url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- identifierSubDepartment' Implement with version: STU 1.1.0S
UM - 2000FThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
UM01Claim.item[n].extension(serviceItemRequestType).valueCodeableConcept.cod ing[0].code The serviceItemRequestType extension has: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-servic eItemRequestType' Implement with version: STU 1.0.0R
UM02Claim.item[n].extension(certificationType).valueCodeableConcept.coding[0 ].code The certificationType extension has: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-certif icationType' Implement with version: STU 1.0.0S
UM03Claim.item[n].category.coding[0].code Implement with version: STU 1.0.0S
UM04-01Claim.item[n].locationCodeableConcept.coding[0].code Implement with version: STU 1.0.0R
UM04-02Claim.item[n].locationCodeableConcept.coding[0].system Populate UM04-02 with the value in coding[n].system translated as follows: 'https://www.nubc.org/CodeSystem/TypeOfBill' -> 'A' 'https://www.cms.gov/Medicare/Coding/place-of-service-codes/Plac e_of_Service_Code_Set' -> 'B' Implement with version: STU 1.0.0R
REF - 2000FThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
REF01'BB' Implement with version: STU 1.0.0R
REF02Claim.item[n].extension(authorizationNumber).valueString The authorizationNumber extension has: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-author izationNumber' Implement with version: STU 1.0.0R
REF - 2000FThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
REF01'NT' Implement with version: STU 1.0.0R
REF02Claim.item[n].extension(administrationReferenceNumber).valueString T he administrationReferenceNumber extension has: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-admini strationReferenceNumber' Implement with version: STU 1.0.0R
DTP - 2000FThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
DTP01'472' Implement with version: STU 1.0.0R
DTP02'D8' or 'RD8' If the item[n] has an attribute named 'servicedDate' set DTP02 to 'D8' Otherwise set DTP02 to 'RD8' Implement with version: STU 1.0.0R
DTP03Claim.item[n].servicedDate Claim.item[n].servicedPeriod If the item[n] has the attribute servicedDate set DTP03 to the value of servicedDate Otherwise set DTP03 to '-' Implement with version: STU 1.0.0R
SV1 - 2000FThe data elements in this segment are defined in the PAS Claim Inquiry profile, see the FHIR Mapping instructions for each data element below. If Claim.type.coding[0].code = 'professional' then populate the SV1 segment otherwise do not populate the elements. Implement with version: STU 1.0.0S
SV101-01The value of Claim.item[n].productOrServiceCode.coding[0].system is translated as follows: 'http://codesystem.x12.org/005010/1365' -> no value 'http://www.ama-assn.org/go/cpt' -> 'HC' 'http://www.cms.gov/Medicare/Coding/HCPCSReleaseCodeSets' -> 'HC' 'http://hl7.org/fhir/sid/ndc' -> 'N4' 'http://terminology.hl7.org/CodeSystem/icd9cm' -> no value 'http://www.cms.gov/Medicare/Coding/ICD10' -> no value Implement with version: STU 1.1.0R
SV101-02Claim.item[n].productOrServiceCode.coding[0].code Implement with version: STU 1.0.0R
SV101-03Claim.item[n].modifier[0].coding[0].code Implement with version: STU 1.0.0S
SV101-04Claim.item[n].modifier[1].coding[0].code Implement with version: STU 1.0.0S
SV101-05Claim.item[n].modifier[2].coding[0].code Implement with version: STU 1.0.0S
SV101-06Claim.item[n].modifier[3].coding[0].code Implement with version: STU 1.0.0S
SV101-07Claim.item[n].productOrServiceCode.text Implement with version: STU 1.0.0S
SV101-08Claim.item[n].extension(productOrServiceCodeEnd).valueCodeableConcept.co ding[0].code The productOrServiceCodeEnd extension has: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-produc tOrServiceCodeEnd' Implement with version: STU 1.0.0S
SV102Claim.item[n].unitPrice.value Implement with version: STU 1.0.0S
SV103Claim.item[n].quantity.unit Implement with version: STU 1.0.0S
SV104Claim.item[n].quantity.value Implement with version: STU 1.0.0S
SV107-01Claim.item[n].diagnosisSequence[0] Translate the value from diagnosisSequence[0] by locating the HI segment create for the referenced Claim.diagnosis[n] (where Claim.diagnosis[n].sequence = diagnosisSequence[0]) and use the HI number (1 to 12) for the value of SV101-01 Implement with version: STU 1.0.0R
SV107-02Claim.item[n].diagnosisSequence[1] Translate the value from diagnosisSequence[1] by locating the HI segment create for the referenced Claim.diagnosis[n] (where Claim.diagnosis[n].sequence = diagnosisSequence[1]) and use the HI number (1 to 12) for the value of SV101-02 Implement with version: STU 1.0.0S
SV107-03Claim.item[n].diagnosisSequence[2] Translate the value from diagnosisSequence[2] by locating the HI segment create for the referenced Claim.diagnosis[n] (where Claim.diagnosis[n].sequence = diagnosisSequence[2]) and use the HI number (1 to 12) for the value of SV101-03 Implement with version: STU 1.0.0S
SV107-04Claim.item[n].diagnosisSequence[3] Translate the value from diagnosisSequence[3] by locating the HI segment create for the referenced Claim.diagnosis[n] (where Claim.diagnosis[n].sequence = diagnosisSequence[3]) and use the HI number (1 to 12) for the value of SV101-04 Implement with version: STU 1.0.0S
SV111Claim.item[n].extension(epsdtIndicator).valueBoolean The epsdtIndicator extension has: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-epsdtI ndicator' The valueBoolean is translated as follows: true -> 'Y' false -> 'N' Implement with version: STU 1.0.0S
SV120Claim.item[n].extension(nursingHomeLevelOfCare).valueCodeableConcept.cod ing[0].code The nursingHomeLevelOfCare extension has: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-nursin gHomeLevelOfCare' Implement with version: STU 1.0.0S
SV2 - 2000FThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. If Claim.type.coding[0].code = 'institutional' then populate the SV1 segment otherwise do not populate the elements. Implement with version: STU 1.0.0S
SV201Claim.item[n].revenue.coding[0].code Implement with version: STU 1.0.0S
SV202-01item.productOrServiceCode.coding.system Implement with version: STU 1.0.0R
SV202-02Claim.item[n].productOrServiceCode.coding[0].code Implement with version: STU 1.0.0R
SV202-03Claim.item[n].modifier[0].coding[0].code Implement with version: STU 1.0.0S
SV202-04Claim.item[n].modifier[1].coding[0].code Implement with version: STU 1.0.0S
SV202-05Claim.item[n].modifier[2].coding[0].code Implement with version: STU 1.0.0S
SV202-06Claim.item[n].modifier[3].coding[0].code Implement with version: STU 1.0.0S
SV202-07Claim.item[n].productOrServiceCode.text Implement with version: STU 1.0.0S
SV202-08Claim.item[n].extension(productOrServiceCodeEnd).valueCodeableConcept.co ding[0].code The productOrServiceCodeEnd extension has: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-produc tOrServiceCodeEnd' Implement with version: STU 1.0.0S
SV203Claim.item[n].unitPrice.value Implement with version: STU 1.0.0S
SV204Claim.item[n].quantity.unit Implement with version: STU 1.0.0S
SV205Claim.item[n].quantity.value Implement with version: STU 1.0.0S
SV206Claim.item[n].extension(revenueUnitRateLimit).valueDecimal The revenueUnitRateLimit extension has: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-revenu eUnitRateLimit' Implement with version: STU 1.0.0S
SV209Claim.item[n].extension(nursingHomeResidentialStatus).valueCodeableConce pt.coding[0].code The nursingHomeResidentialStatus extension has: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-nursin gHomeResidentialStatus' Implement with version: STU 1.0.0S
SV210Claim.item[n].extension(nursingHomeLevelOfCare).valueCodeableConcept.cod ing[0].code The nursingHomeLevelOfCare extension has: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-nursin gHomeLevelOfCare' Implement with version: STU 1.0.0S
SV3 - 2000FThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
TOO - 2000FThe data elements in this segment are not defined in the PAS Claim profile. Implement with version: STU 1.0.0S
HSD - 2000FThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Claim.item[n].extension(requestedService).valueReference.reference => MedicationRequest | ServiceRequest | DeviceRequest The requestedService extension has: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- requestedService' Locate the MedicationRequest or Servicerequest or DeviceRequest within the Bundle referenced from the extension and use that resource in populating the HSD segment. Implement with version: STU 1.0.0S
HSD01Claim.item[n].quantity.unit Implement with version: STU 1.0.0S
HSD02Claim.item[n].quantity.value Implement with version: STU 1.0.0S
HSD03MedicationRequest.dosageInstruction[0].timing.repeat.periodUnit | ServiceRequest.occurrenceTiming.repeat.periodUnit | DeviceRequest.occurrenceTiming.repeat.periodUnit Translate the value from periodUnit as follows: 'da' -> 'DA' 'wk' -> 'WK' 'mo' -> 'MO' Implement with version: STU 1.0.0S
HSD04MedicationRequest.dosageInstruction[0].timing.repeat.period | ServiceRequest.occurrenceTiming.repeat.period | DeviceRequest.occurrenceTiming.repeat.period Implement with version: STU 1.0.0S
HSD05MedicationRequest.dosageInstruction[0].timing.repeat.boundsDuration.unit | ServiceRequest.occurrenceTiming.repeat.boundsDuration.unit | DeviceRequest.occurrenceTiming.repeat.boundsDuration.unit Implement with version: STU 1.0.0S
HSD06MedicationRequest.dosageInstruction[0].timing.repeat.boundsDuration.valu e | ServiceRequest.occurrenceTiming.repeat.boundsDuration.value | DeviceRequest.occurrenceTiming.repeat.boundsDuration.value Implement with version: STU 1.0.0S
HSD07MedicationRequest.dosageInstruction[0].timing.extension(timingCalendarPa ttern).valueCodeableConcept.coding[0].code | ServiceRequest.occurrenceTiming.extension(timingCalendarPattern).valueCo deableConcept.coding[0].code | DeviceRequest.occurrenceTiming.extension(timingCalendarPattern).valueCod eableConcept.coding[0].code The timingCalendarPattern extension has: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-timing calendarpattern' Implement with version: STU 1.0.0S
HSD08MedicationRequest.dosageInstruction[0].timing.extension(timingDeliveryPa ttern).valueCodeableConcept.coding[0].code | ServiceRequest.occurrenceTiming.extension(timingDeliveryPattern).valueCo deableConcept.coding[0].code | DeviceRequest.occurrenceTiming.extension(timingDeliveryPattern).valueCod eableConcept.coding[0].code The timingDeliveryPattern extension has: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-timing deliverypattern' Implement with version: STU 1.0.0S
PWK - 2000FThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Claim.item[n].informationSequence => Claim.supportingInfo[n].valueReference => DocumentReference Locate the Claim.supportingInfo where supportingInfo[n].sequence = to Claim.item[n].informationSequence. If the supportingInfo is AdditionalInformation where supportingInfo[n].category.coding[0].system set to 'http://hl7.org/fhir/us/davinci-pas/CodeSystem-PASSupportingInfoType' and supportingInfo[n].category.coding[0].code set to 'additionalInformation' Then a PWK segment is created. Locate the DocumentReference using the valueReference.reference in the supportingInfo. Implement with version: STU 1.0.0S
PWK01DocumentReference.type.coding[0].code Preferred value set is LOINC (not X12) Implement with version: STU 1.0.0R
PWK02'EL' Implement with version: STU 1.0.0R
PWK05'AC' Implement with version: STU 1.0.0S
PWK06DocumentReference.identifier.value Implement with version: STU 1.0.0S
PWK07DocumentReference.description Implement with version: STU 1.0.0S
MSG - 2000FThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
MSG01Claim.item[n].informationSequence => Claim.supportingInfo[n].valueString Locate the Claim.supportingInfo where supportingInfo[n].sequence = to Claim.item[n].informationSequence. If the supportingInfo is MessageText where supportingInfo[n].category.coding[0].system set to 'http://hl7.org/fhir/us/davinci-pas/CodeSystem-PASSupportingInfoType' and supportingInfo[n].category.coding[0].code set to 'freeFormMessage' Then a MSG segment is created. Use the valueString in the supportingInfo for MSG01 Implement with version: STU 1.0.0R
NM1 - 2010FThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Claim.careTeam[n].provider => Practitioner | Organization Where Claim.careTeam[n].sequence = Claim.item[n].careTeamSequence[0..9] (create for the 1st 10 occurrences only) Implement with version: STU 1.1.0S
NM101Claim.careTeam[n].role.coding[0].code Implement with version: STU 1.0.0R
NM102If the provider is a Practitioner Resource this value is '1' If the provider is a Organization Resource this value is '2' Implement with version: STU 1.0.0R
NM103Practitioner.name[0].family | Organization.name Implement with version: STU 1.0.0S
NM104Practitioner.name[0].given[0] | not used on Organization Implement with version: STU 1.0.0S
NM105Practitioner.name[0].given[1] | not used on Organization Implement with version: STU 1.0.0S
NM106Practitioner.name[0].prefix[0] | not used on Organization Implement with version: STU 1.0.0S
NM107Practitioner.name[0].suffix[0] | not used on Organization Implement with version: STU 1.0.0S
NM108Practitioner.identifier[0].type.coding[0].code | Organization.identifier[0].type.coding[0].code The value from the code attribute is translated as follows: 'EN' -> '24' 'SB' -> '34' '46' -> '46' 'NPI' -> 'XX' Implement with version: STU 1.1.0S
NM109Practitioner.identifier[0].value | Organization.identifier[0].value Implement with version: STU 1.0.0S
REF - 2010FThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. If Organization.identifier[n].type.coding[0].code is equal to 'SL' (State License Number), do not create this REF Segment. Implement with version: STU 1.1.0S
REF01Practitioner.identifier[1].type.coding[0].code | Organization.identifier[1].type.coding[0].code The value from the code attribute is translated as follows: 'SL' -> '0B' 'FI' -> '1J' 'EN' -> 'EI' 'N5' -> 'N5' 'N7' -> 'N7' 'SB' -> 'SY' 'ZH' -> 'ZH' Implement with version: STU 1.1.0R
REF02Practitioner.identifier[1].value | Organization.identifier[1].value Implement with version: STU 1.0.0R
REF03Practitioner.identifier[1].extension(jurisdiction).coding[0].code Implement with version: STU 1.1.0S
N3 - 2010FThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
N301Practitioner.address[0].line[1] | Organization.address[0].line[1] Implement with version: STU 1.0.0R
N302Practitioner.address[0].line[2] | Organization.address[0].line[2] Implement with version: STU 1.0.0S
N4 - 2010FThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
N401Practitioner.address[0].city | Organization.address[0].city Implement with version: STU 1.0.0R
N402Practitioner.address[0].state | Organization.address[0].state Implement with version: STU 1.0.0S
N403Practitioner.address[0].postalCode | Organization.address[0].postalCode Implement with version: STU 1.0.0S
N404Practitioner.address[0].country | Organization.address[0].country Implement with version: STU 1.0.0S
N407Practitioner.address[0].district | Organization.address[0].district Implement with version: STU 1.0.0S
PER - 2010FThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
PER01'IC' Implement with version: STU 1.0.0R
PER02no value when Practitioner | Organization.contact[0].name.text Implement with version: STU 1.0.0S
PER03Practitioner.telecom[0].system | Organization.contact[0].telecom[0].system The value from the system attribute is translated as follows: 'phone' -> 'TE' 'fax' -> 'FX' 'email' -> 'EM' 'pager' -> 'TE' 'url' -> 'UR' 'sms' -> 'TE' 'other' -> cannot be translated Implement with version: STU 1.0.0S
PER04Practitioner.telecom[0].value | Organization.contact[0].telecom[0].value If the value of system is 'phone', this value must be parsed to determine if an extension is present (see ITU-T E.123 for format of telephone values). If an extension is present, the remove the extension part of the phone number and place in PER06 and set PER05 to 'EX' Implement with version: STU 1.0.0S
PER05Practitioner.telecom[1].system | Organization.contact[0].telecom[1].system | 'EX' See PER04 if PER03 is 'TE' otherwise select the next telecom in contact[0] and translate the system as follows: 'phone' -> 'TE' 'fax' -> 'FX' 'email' -> 'EM' 'pager' -> 'TE' 'url' -> 'UR' 'sms' -> 'TE' 'other' -> cannot be translated Implement with version: STU 1.0.0S
PER06Practitioner.telecom[1].value | Organization.contact[0].telecom[1].value | extracted extension If PER05 is set to 'EX' this will be the extract value for the extension from PER04 Otherwise this is refer to PER04 for rules on formatting Implement with version: STU 1.0.0S
PER07Practitioner.telecom[n].system | Organization.contact[0].telecom[n].system | 'EX' See PER06 if PER05 is 'TE' otherwise select the next telecom in contact[0] and translate the system as follows: 'phone' -> 'TE' 'fax' -> 'FX' 'email' -> 'EM' 'pager' -> 'TE' 'url' -> 'UR' 'sms' -> 'TE' 'other' -> cannot be translated Implement with version: STU 1.0.0S
PER08Practitioner.telecom[n].value | Organization.contact[0].telecom[n].value | extracted extension If PER07 is set to 'EX' this will be the extract value for the extension from PER06 Otherwise this is refer to PER04 for rules on formatting Implement with version: STU 1.0.0S
PRV - 2010FThe data elements in this segment are defined in the PAS Claim profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
PRV01Claim.careTeam[n].role.coding[1].code Implement with version: STU 1.0.0R
PRV02'PXC' Implement with version: STU 1.0.0R
PRV03Claim.careTeam[n].qualification.coding[0].code Implement with version: STU 1.0.0R
SEThe data elements in this segment are not defined in the PAS Claim profile because the values are hardcoded or derived. Implement with version: STU 1.0.0R

Appendix G. X12 278 Response to the FHIR PAS Claim Response

This implementation guide describes the intersection of X12 and Da Vinci data elements, so the information can be used consistently across implementations, regardless of syntax. Section 1.13, the FHIR mapping information provided in Section 2, and Appendices F and G are not part of the X12 EDI Standard or TR3 but are provided as a courtesy for organizations who are implementing multiple syntaxes.

These instructions delineate how the data maps between the X12 278 Response segments and elements and associated FHIR PAS Claim Response elements.

Please review the information in Section 1.13 of this Implementation Guide for background and details on the mapping legend.

Segment - Loop Field Mapping/Notes Usage
STThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
BHTThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0R
BHT01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
BHT02This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
BHT03Bundle.identifier Implement with version: STU 1.0.0R
BHT04Bundle.timestamp and ClaimResponse.created Combine with BHT05 to create a datetime and populate both fields with the same value Implement with version: STU 1.0.0R
BHT05Bundle.timestamp and ClaimResponse.created Combine with BHT04 to create a datetime and populate both fields with the same value Implement with version: STU 1.0.0R
BHT06ClaimResponse.outcome The value from BHT06 is translated as follows: '18' -> 'complete' '19' -> 'partial' 'AT' -> 'partial' 'RU' -> 'partial' ?Recognize the concept may not easily fit when mapping between BHT06 and outcome Implement with version: STU 1.0.0R
HL - 2000AThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
AAA - 2000AThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
AAA01ClaimResponse.error[n].extension(errorPlace) The value of AAA01 is NOT used but the location of this AAA segment is recorded in the error to provide additional information as follows: extension[0].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- errorElement' extension[0].valueString = '2000A' Implement with version: STU 1.0.0R
AAA03ClaimResponse.error[n].code Populate the components of the code (datatype CodeableConcept) as follows: code.coding[0].system = 'https://codesystem.x12.org/005010/901' code.coding[0].c ode = value of AAA03 Implement with version: STU 1.0.0R
AAA04ClaimResponse.error[n].extension(followupActionCode) The followupActionCode extension type is a CodeableConcept and is populated as follows: extension[1].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- errorFollowupAction' extension[1].valueCodeableConcept.coding[0].system = 'https://codesystem.x12.org/005010/889' extension[1].valueCodeableConcept.coding[0].code = value of AAA04 Implement with version: STU 1.0.0R
NM1 - 2010AClaimResponse.insurer => Organization Create an Organization in the response Bundle and set ClaimResponse.insurer to point to this Organization. Note that this Organization must adhere to the PAS Insurer Organization profile Implement with version: STU 1.0.0R
NM101Organization.type Populate the components of the type (datatype CodeableConcept) as follows: type.coding[0].system = 'https://codesystem.x12.org/005010/98' type.coding[0].code = value of NM101 Implement with version: STU 1.0.0R
NM102This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
NM103Organization.name Implement with version: STU 1.0.0S
NM104This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
NM105This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
NM107This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
NM108Organization.identifier[0].type Populate the components of the type (datatype CodeableConcept) as follows: type.coding[0].system = 'https://terminology.hl7.org/CodeSystem/v2-0203' type.coding[0].code = value of NM108 translated as follows: '46' -> '46' 'PI' -> 'U' Implement with version: STU 1.1.0R
NM109Organization.identifier[0].value Implement with version: STU 1.0.0R
PER - 2010AThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
PER01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
PER02Organization.contact.name Populate the 'text' attribute of the name Implement with version: STU 1.0.0S
PER03Organization.contact.telecom[0].system Translate the PER03 value as follows: 'EM' -> 'email' 'FX' -> 'fax' 'TE' -> 'phone' 'UR' -> 'url' Implement with version: STU 1.0.0S
PER04Organization.contact.telecom[0].value Implement with version: STU 1.0.0S
PER05Organization.contact.telecom[1].system When PER05 is NOT equal to 'EX' create a new telecom element and translate PER05 as per the note for PER03. Implement with version: STU 1.0.0S
PER06Organization.contact.telecom[1].value If PER05 is NOT 'EX' store this value in the telecom[1].value If PER05 is 'EX' append the value formatted: ' ext. ' to telecom[0].value See ITU-T E.123 for format of telephone values Implement with version: STU 1.0.0S
PER07Organization.contact.telecom[n].system When PER07 is NOT equal to 'EX' create a new telecom element and translate PER07 as per the note for PER03. If PER05 was not 'EX' this will be telecom[2] otherwise this will be the 2nd telecom element. Implement with version: STU 1.0.0S
PER08Organization.contact.telecom[n].value If PER07 is NOT 'EX' store this value in the telecom[n].value If PER07 is 'EX' append the value formatted: ' ext. ' to telecom[1].value See ITU-T E.123 for format of telephone values Implement with version: STU 1.0.0S
AAA - 2010AThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
AAA01ClaimResponse.error[n].extension(errorPlace) The value of AAA01 is NOT used but the location of this AAA segment is recorded in the error to provide additional information as follows: extension[0].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-errorE lement' extension[0].valueString = '2010A' Implement with version: STU 1.0.0R
AAA03ClaimResponse.error[n].code Populate the components of the code (datatype CodeableConcept) as follows: code.coding[0].system = 'https://codesystem.x12.org/005010/901' code.coding[0].code = value of AAA03 Implement with version: STU 1.0.0R
AAA04ClaimResponse.error[n].extension(followupActionCode) The followupActionCode extension type is a CodeableConcept and is populated as follows: extension[1].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- errorFollowupAction' extension[1].valueCodeableConcept.coding[0].system = 'https://codesystem.x12.org/005010/889' extension[1].valueCodeableConcept.coding[0].code = value of AAA04 Implement with version: STU 1.0.0R
HL - 2000BThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
NM1 - 2010BClaimResponse.requestor => Organization Create an Organization in the response Bundle and set ClaimResponse.requestor to point to this Organization. Note that this Organization must adhere to the PAS Requestor Organization profile. Note also The PAS Requestor Organization requires an address attribute (which is not provided in the REQUESTER LEVEL) which will require creating an address with a Data Absent Reason extension. Implement with version: STU 1.0.0R
NM101Organization.type Populate the components of the type (datatype CodeableConcept) as follows: type.coding[0].system = 'https://codesystem.x12.org/005010/98' type.coding[0].code = value of NM101 Implement with version: STU 1.0.0R
NM102This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
NM103Organization.name Implement with version: STU 1.0.0S
NM104This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
NM105This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
NM107This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
NM108Organization.identifier[0].type Populate the CodeableConcept components of the type as follows: Organization.identifier[0].type.coding[0].system = 'http://terminology.hl7.org/CodeSystem/v2-0203' Organization.identifier[0].type.coding[0].code = 'NPI' Organization.identifier[0].system = 'http://hl7.org/fhir/sid/us-npi' Implement with version: STU 1.1.0R
NM109Organization.identifier[0].value Implement with version: STU 1.0.0R
REF - 2010BThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.1.0S
AAA - 2010BThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
AAA01ClaimResponse.error[n].extension(errorPlace) The value of AAA01 is NOT used but the location of this AAA segment is recorded in the error to provide additional information as follows: extension[0].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-errorE lement' extension[0].valueString = '2010B' Implement with version: STU 1.0.0R
AAA03ClaimResponse.error[n].code Populate the components of the code (datatype CodeableConcept) as follows: code.coding[0].system = 'https://codesystem.x12.org/005010/901' code.coding[0].code = value of AAA03 Implement with version: STU 1.0.0R
AAA04ClaimResponse.error[n].extension(followupActionCode) The followupActionCode extension type is a CodeableConcept and is populated as follows: extension[1].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- errorFollowupAction' extension[1].valueCodeableConcept.coding[0].system = 'https://codesystem.x12.org/005010/889' extension[1].valueCodeableConcept.coding[0].code = value of AAA04 Implement with version: STU 1.0.0R
PRV - 2010BThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HL - 2000CThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
NM1 - 2010CClaimResponse.patient => Patient (if 2000D Loop is NOT present) Create an Patient in the response Bundle and set ClaimResponse.patient to point to this Patient. Note that the Patient resource created must conform to the PAS Beneficiary Patient profile. Implement with version: STU 1.1.0R
NM101This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
NM102This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
NM103Patient.name[0].family Implement with version: STU 1.0.0S
NM104Patient.name[0].given[1] Implement with version: STU 1.0.0S
NM105Patient.name[0].given[2] Implement with version: STU 1.0.0S
NM106Patient.name[0].prefix[0] Implement with version: STU 1.0.0S
NM107Patient.name[0].suffix[0] Implement with version: STU 1.0.0S
NM108Patient.identifier[0].type Populate the components of the type (datatype CodeableConcept) as follows: type.coding[0].system = 'http://terminology.hl7.org/CodeSystem/v2-0203' type.coding[0].code = 'MB' Implement with version: STU 1.1.0R
NM109Patient.identifier[0].value Implement with version: STU 1.0.0R
REF - 2010CThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
REF01Patient.identifier[1].type The type attribute is a CodeableConcept and is populated as follows: type.coding[0].system = 'http://terminology.hl7.org/CodeSystem/v2-0203' type.coding[0].code = value of REF01 translated as follows: '1L' -> '1L' '3L' -> '3L' '6P' -> '6P' 'DP' -> 'DP' 'EJ' -> 'EJ' 'F6' -> 'MC' 'HJ' -> 'HJ' 'IG' -> 'IG' 'N6' -> 'N6' 'NQ' -> 'MA' 'SY' -> 'SB' Implement with version: STU 1.1.0R
REF02Patient.identifier[1].value Implement with version: STU 1.0.0R
N3 - 2010CThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
N301Patient.address[0].line[1] Implement with version: STU 1.0.0R
N302Patient.address[0].line[2] Implement with version: STU 1.0.0S
N4 - 2010CThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
N401Patient.address[0].city Implement with version: STU 1.0.0R
N402Patient.address[0].state Implement with version: STU 1.0.0S
N403Patient.address[0].postalCode Implement with version: STU 1.0.0S
N404Patient.address[0].country Implement with version: STU 1.0.0S
N407This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
AAA - 2010CThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
AAA01ClaimResponse.error[n].extension(errorPlace) The value of AAA01 is NOT used but the location of this AAA segment is recorded in the error to provide additional information as follows: extension[0].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-errorE lement' extension[0].valueString = '2010C' Implement with version: STU 1.0.0R
AAA03ClaimResponse.error[n].code Populate the components of the code (datatype CodeableConcept) as follows: code.coding[0].system = 'https://codesystem.x12.org/005010/901' code.coding[0].code = value of AAA03 Implement with version: STU 1.0.0R
AAA04ClaimResponse.error[n].extension(followupActionCode) The followupActionCode extension type is a CodeableConcept and is populated as follows: extension[1].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- errorFollowupAction' extension[1].valueCodeableConcept.coding[0].system = 'https://codesystem.x12.org/005010/889' extension[1].valueCodeableConcept.coding[0].code = value of AAA04 Implement with version: STU 1.0.0R
DMG - 2010CThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
DMG01The data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
DMG02Patient.birthDate The Patient.birthDate format is YYYY-MM-DD and will need to be converted. Implement with version: STU 1.1.0R
DMG03Patient.gender The value from DMG03 must be translated to a FHIR specific value as follows: 'F' -> 'female' 'M' -> 'male' 'U' -> 'unknown' Implement with version: STU 1.0.0S
INS - 2010CThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HL - 2000DThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
NM1 - 2010DClaimResponse.patient => Patient (if 2000D Loop is present) Create a Patient in the response Bundle and set ClaimResponse.patient to point to this Patient. Note that the Patient resource created must conform to the PAS Beneficiary Patient profile. Implement with version: STU 1.1.0R
NM101This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
NM102This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
NM103Patient.name[0].family Implement with version: STU 1.0.0S
NM104Patient.name[0].given[1] Implement with version: STU 1.0.0S
NM105Patient.name[0].given[2] Implement with version: STU 1.0.0S
NM107Patient.name[0].suffix[0] Implement with version: STU 1.0.0S
NM108Patient.identifier[0].type Populate the components of the type (datatype CodeableConcept) as follows: type.coding[0].system = 'http://terminology.hl7.org/CodeSystem/v2-0203' type.coding[0].code = 'MB' Implement with version: STU 1.1.0S
NM109Patient.identifier[0].value Implement with version: STU 1.0.0S
REF - 2010DThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
REF01Patient.identifier[1].type The type attribute is a CodeableConcept and is populated as follows: type.coding[0].system = 'http://terminology.hl7.org/CodeSystem/v2-0203' type.coding[0].code = value of REF01 translated as follows: 'EJ' -> 'EJ' 'SY' -> 'SB' Implement with version: STU 1.1.0R
REF02Patient.identifier[1].value Implement with version: STU 1.0.0R
N3 - 2010DThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
N301Patient.address[0].line[1] Implement with version: STU 1.0.0R
N302Patient.address[0].line[2] Implement with version: STU 1.0.0S
N4 - 2010DThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
N401Patient.address[0].city Implement with version: STU 1.0.0R
N402Patient.address[0].state Implement with version: STU 1.0.0S
N403Patient.address[0].postalCode Implement with version: STU 1.0.0S
N404Patient.address[0].country Implement with version: STU 1.0.0S
N407This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
AAA - 2010DThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
AAA01ClaimResponse.error[n].extension(errorPlace) The value of AAA01 is NOT used but the location of this AAA segment is recorded in the error to provide additional information as follows: extension[0].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- errorElement' extension[0].valueString = '2010D' Implement with version: STU 1.0.0R
AAA03ClaimResponse.error[n].code Populate the components of the code (datatype CodeableConcept) as follows: code.coding[0].system = 'https://codesystem.x12.org/005010/901' code.coding[0].code = value of AAA03 Implement with version: STU 1.0.0R
AAA04ClaimResponse.error[n].extension(followupActionCode) The followupActionCode extension type is a CodeableConcept and is populated as follows: extension[1].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- errorFollowupAction' extension[1].valueCodeableConcept.coding[0].system = 'https://codesystem.x12.org/005010/889' extension[1].valueCodeableConcept.coding[0].code = value of AAA04 Implement with version: STU 1.0.0R
DMG - 2010DThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
DMG01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
DMG02Patient.birthDate The Patient.birthDate format is YYYY-MM-DD and will need to be converted. Implement with version: STU 1.1.0R
DMG03Patient.gender The value from DMG03 must be translated to a FHIR specific value as follows: 'F' -> 'female' 'M' -> 'male' 'U' -> 'unknown' Implement with version: STU 1.0.0S
INS - 2010DThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
INS01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
INS02This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
INS17Patient.multipleBirthInteger Implement with version: STU 1.0.0S
HL - 2000EThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
TRN - 2000EThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
TRN01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
TRN02ClaimResponse.identifier[0].value Implement with version: STU 1.0.0R
TRN03ClaimResponse.identifier[0].system Implement with version: STU 1.0.0R
TRN04ClaimResponse.identifier[0].assigner Implement with version: STU 1.0.0S
AAA - 2000EThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
AAA01ClaimResponse.error[n].extension(errorPlace) The value of AAA01 is NOT used but the location of this AAA segment is recorded in the error to provide additional information as follows: extension[0].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-errorE lement' extension[0].valueString = '2000E' Implement with version: STU 1.0.0R
AAA03ClaimResponse.error[n].code Populate the components of the code (datatype CodeableConcept) as follows: code.coding[0].system = 'https://codesystem.x12.org/005010/901' code.coding[0].code = value of AAA03 Implement with version: STU 1.0.0R
AAA04ClaimResponse.error[n].extension(followupActionCode) The followupActionCode extension type is a CodeableConcept and is populated as follows: extension[1].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- errorFollowupAction' extension[1].valueCodeableConcept.coding[0].system = 'https://codesystem.x12.org/005010/889' extension[1].valueCodeableConcept.coding[0].code = value of AAA04 Implement with version: STU 1.0.0R
UM - 2000EThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
HCR - 2000EClaimResponse.adjudication[0].extension(reviewAction) The HCR segment in the 2000E is used when present and there is no HCR segment in the 2000F. The components of the HCR segment are used to populate the complex extensions within the reviewAction extension. The base reviewAction extension is populate as follows: adjudication[0].extension[n].extension[] -> see HCR attributes below adjudication[0].extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- review Action' adjudication[0].category.coding[0].system = 'http://terminology.hl7.org/CodeSystem/adjudication' adjudication[0].category.coding[0].value = 'submitted' Implement with version: STU 1.1.0S
HCR01.extension(reviewActionCode) The reviewActionCode extension is a CodeableConcept and populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- review ActionCode' extension[n].valueCodeableConcept.coding[0].system = 'https://codesystem.x12.org/005010/306' extension[n].valueCodeableCo ncept.coding[0].code = value of HCR01 Implement with version: STU 1.1.0R
HCR02ClaimResponse.preAuthRef AND .extension(number) The number extension is a string and populated as follows: extension[n].url = 'number' extension[n].valueString = value of HCR02 Implement with version: STU 1.1.0S
HCR03.extension(reasonCode) Create one of the following for each repetition of the reasonCode sent. The reasonCode extension is of type CodeableConcept and populated as follows: extension[n].url = 'reasonCode' extension[n].valueCodeableConcept.coding[0].system = 'https://codesystem.x12.org/005010/886' extension[n].valueCodeableConcept.coding[0].code = value of HCR03 Implement with version: STU 1.1.0S
HCR04.extension(secondSurgicalOpinionFlag) The number extension is a boolean and populated as follows: extension[n].url = 'secondSurgicalOpinionFlag' extension[n].valueString = true if HCR04 = 'Y', false if HCR04 = 'N' Implement with version: STU 1.0.0S
REF - 2000EThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
REF01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
REF02ClaimResponse.item[n].extension(administrationReferenceNumber) Used for each iteration of 2000F where REF (Previous Review Authorization Number) is NOT present in the 2000F The administrationReferenceNumber extension type is a string and is populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- administrationReferenceNumber' extension[n].valueString = value of REF02 Implement with version: STU 1.0.0R
REF - 2000EThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
REF01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
REF02ClaimResponse.item[n].extension(authorizationNumber) Used for each iteration of 2000F where REF (Previous Review Authorization Number) is NOT present in the 2000F The authorizationNumber extension type is a string and is populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- authorizationNumber' extension[n].valueString = value of REF02 Implement with version: STU 1.0.0R
DTP - 2000EThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
DTP - 2000EThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
DTP - 2000EThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
DTP - 2000EThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
DTP - 2000EThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
DTP01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
DTP02See note on DTP03 Implement with version: STU 1.0.0R
DTP03ClaimResponse.item[n].extension(authorizedDate) Used for each iteration of 2000F where DTP (Service Date) is NOT present If DTP02 = 'D8' extension type is dateTime and is populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- itemAuthorizedDate' extension[n].valueDateTime = value of DTP03 If DTP02 = 'RD8' extension type is Period and is populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- itemAuthorizedDate' extension[n].valuePeriod.start = value of DTP03 before '-' extension[n].valuePeriod.end = value of DTP03 after '-' Implement with version: STU 1.0.0R
DTP - 2000EThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
DTP - 2000EThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
DTP - 2000EThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
DTP01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
DTP02This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
DTP03ClaimResponse.item[n].extension(preAuthIssueDate) Used for each iteration of 2000F where DTP (Certification Issue Date) is NOT present in the 2000F See DTP (Certification Issue Date) in 2000F below for formatting instructions Implement with version: STU 1.0.0R
DTP - 2000EThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
DTP01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
DTP02This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
DTP03ClaimResponse.preAuthPeriod.end Also used for each iteration of 2000F where DTP (Certification Expiration Date) is NOT present in the 2000F See DTP (Certification Expiration Date) in 2000F below for formatting instructions Implement with version: STU 1.0.0R
DTP - 2000EThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
DTP01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
DTP02This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
DTP03ClaimResponse.preAuthPeriod.start Also used for each iteration of 2000F where DTP (Certification Effective Date) is NOT present in the 2000F See DTP (Certification Effective Date) in 2000F below for formatting instructions Implement with version: STU 1.0.0R
HI - 2000EClaimResponse.communicationRequest[n].reference => CommunicationRequest If there is no LOINC (HI0x-02 with 'LOI') in the HI segment, no CommunicationRequest is created. Only when there is a HI0x-02 with 'LOI', create a CommunicationRequest that conforms to the PAS CommunicationRequest and then set the reference to the new resource in the Bundle. Also set the following attributes on the CommunicationRequest: CommunicationRequest.status = 'active' CommunicationRequest.requestor.reference => Organization created in 2000B CommunicationRequest.sender.reference => Organization created in 2010A Note there is no unique qualifier that defines a LOINC Modifier. Allowed patterns are: DX/LOINC/LOINC Modifier which would result in one ClaimResponse.communicationRequest with one payload. LOINC/LOINC Modifier which would result in one ClaimResponse.communicationRequest with one payload. DX/DX/DX/DX/LOINC/LOINC Modifier/DX/LOINC/DX/LOINC/LOINC Modifier which would result in one ClaimResponse.communicationRequest with three payload structures. Implement with version: STU 1.1.0S
HI01-01see HI01-02 Translate the HI01-01 as follows: 'ABF' -> 'http://hl7.org/fhir/sid/icd-10-cm' 'ABJ' -> 'http://hl7.org/fhir/sid/icd-10-cm' 'APR' -> 'http://hl7.org/fhir/sid/icd-10-cm' 'BF' -> 'http://terminology.hl7.org/CodeSystem/icd9cm' 'BJ' -> 'http://terminology.hl7.org/CodeSystem/icd9cm' 'BK' -> 'http://terminology.hl7.org/CodeSystem/icd9cm' 'DR' -> cannot be translated at this time 'PR' -> 'http://terminology.hl7.org/CodeSystem/icd9cm' Implement with version: STU 1.0.0R
HI01-02CommunicationRequest.payload[0].extension(communicatedDiagnosis) The communicatedDiagnosis extension is a CodeableConcept and populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- communicatedDiagnosis' extension[n].valueCodeableConcept.coding[0].system = translated value from HI01-01 extension[n].valueCodeableConcept.coding[0].code = value of HI01-02 Note also that communicatedDiagnosis does not indicate if the returned diagnosis code is for admitting, patient reason for visit or any other qualifier for the diagnosis code. Implement with version: STU 1.1.0R
HI01-03This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HI01-04This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HI02-01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
HI02-02CommunicationRequest.payload[0].contentString Implement with version: STU 1.1.0R
HI02-03This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HI02-04This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HI03-01If HI03-01 = 'LOI' this is a modifier of HI02 Otherwise a new CommunicationRequest should be created and see HI01 for how to populate. Implement with version: STU 1.1.0R
HI03-02CommunicationRequest.payload[0].extension(contentModifier) if HI103-01 = 'LOI' The contentModifier is a CodeableConcept and populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- contentModifier' extension[n].valueCodeableConcept.coding[0].system = 'http://loinc.org' extension[n].valueCodeableConcept.coding[0].code = value of HI02-02 Implement with version: STU 1.1.0R
HI03-03This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HI03-04This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HI04-01If HI04-01 is not 'LOI' then create a new CommunicationRequest and populate as per HI01 If HI04-01 is 'LOI' and the previous HI is not 'LOI' this is the report/document code, populate as per HI02 If HI04-01 is 'LOI' and the previous HI is 'LOI' this is the modifier, populate as per HI03 Implement with version: STU 1.0.0R
HI04-02see note on HI04-01 for details Implement with version: STU 1.0.0R
HI04-03This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HI04-04This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HI05-01If HI05-01 is not 'LOI' then create a new CommunicationRequest and populate as per HI01 If HI05-01 is 'LOI' and the previous HI is not 'LOI' this is the report/document code, populate as per HI02 If HI05-01 is 'LOI' and the previous HI is 'LOI' this is the modifier, populate as per HI03 Implement with version: STU 1.0.0R
HI05-02see note on HI05-01 for details Implement with version: STU 1.0.0R
HI05-03This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HI05-04This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HI06-01If HI06-01 is not 'LOI' then create a new CommunicationRequest and populate as per HI01 If HI06-01 is 'LOI' and the previous HI is not 'LOI' this is the report/document code, populate as per HI02 If HI06-01 is 'LOI' and the previous HI is 'LOI' this is the modifier, populate as per HI03 Implement with version: STU 1.0.0R
HI06-02see note on HI06-01 for details Implement with version: STU 1.0.0R
HI06-03This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HI06-04This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HI07-01If HI07-01 is not 'LOI' then create a new CommunicationRequest and populate as per HI01 If HI07-01 is 'LOI' and the previous HI is not 'LOI' this is the report/document code, populate as per HI02 If HI07-01 is 'LOI' and the previous HI is 'LOI' this is the modifier, populate as per HI03 Implement with version: STU 1.0.0R
HI07-02see note on HI07-01 for details Implement with version: STU 1.0.0R
HI07-03This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HI07-04This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HI08-01If HI08-01 is not 'LOI' then create a new CommunicationRequest and populate as per HI01 If HI08-01 is 'LOI' and the previous HI is not 'LOI' this is the report/document code, populate as per HI02 If HI08-01 is 'LOI' and the previous HI is 'LOI' this is the modifier, populate as per HI03 Implement with version: STU 1.0.0R
HI08-02see note on HI08-01 for details Implement with version: STU 1.0.0R
HI08-03This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HI08-04This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HI09-01If HI09-01 is not 'LOI' then create a new CommunicationRequest and populate as per HI01 If HI09-01 is 'LOI' and the previous HI is not 'LOI' this is the report/document code, populate as per HI02 If HI09-01 is 'LOI' and the previous HI is 'LOI' this is the modifier, populate as per HI03 Implement with version: STU 1.0.0R
HI09-02see note on HI09-01 for details Implement with version: STU 1.0.0R
HI09-03This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HI09-04This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HI10-01If HI10-01 is not 'LOI' then create a new CommunicationRequest and populate as per HI01 If HI10-01 is 'LOI' and the previous HI is not 'LOI' this is the report/document code, populate as per HI02 If HI10-01 is 'LOI' and the previous HI is 'LOI' this is the modifier, populate as per HI03 Implement with version: STU 1.0.0R
HI10-02see note on HI10-01 for details Implement with version: STU 1.0.0R
HI10-03This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HI10-04This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HI11-01If HI11-01 is not 'LOI' then create a new CommunicationRequest and populate as per HI01 If HI11-01 is 'LOI' and the previous HI is not 'LOI' this is the report/document code, populate as per HI02 If HI11-01 is 'LOI' and the previous HI is 'LOI' this is the modifier, populate as per HI03 Implement with version: STU 1.0.0R
HI11-02see note on HI11-01 for details Implement with version: STU 1.0.0R
HI11-03This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HI11-04This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HI12-01If HI12-01 is 'LOI' and the previous HI is not 'LOI' this is the report/document code, populate as per HI02 If HI12-01 is 'LOI' and the previous HI is 'LOI' this is the modifier, populate as per HI03 Implement with version: STU 1.0.0R
HI12-02see note on HI12-01 for details Implement with version: STU 1.0.0R
HI12-03This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HI12-04This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HSD - 2000E.extension(requestedService) => ServiceRequest The HSD segment in the 2000E is used when present and there is no HSD segment in the 2000F. Create a ServiceRequest that adheres to the PAS Service Request profile and the set a reference to the Resource in the extension as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- requestedService' extension[n].valueReference.reference = Set the ServiceRequest.subject to the value of ClaimResponse.patient Note: Though a MedicationRequest would be preferable if the value of SV101-1 or SV202-1 is N4, the PAS Medication Request profile requires that the medication be specified using RxNorm which is not avaiailable on the 278 response. Implement with version: STU 1.0.0S
HSD01ServiceRequest.quantityQuantity.unit Implement with version: STU 1.0.0S
HSD02ServiceRequest.quantityQuantity.value Implement with version: STU 1.0.0S
HSD03ServiceRequest.occurrenceTiming.repeat.periodUnit Translate the HSD03 value as follows: 'DA' -> 'd' 'WK' -> 'wk' 'MO' -> 'mo' Implement with version: STU 1.0.0S
HSD04ServiceRequest.occurrenceTiming.repeat.period Implement with version: STU 1.0.0S
HSD05ServiceRequest.occurrenceTiming.repeat.boundsDuration.unit Implement with version: STU 1.0.0S
HSD06ServiceRequest.occurrenceTiming.repeat.boundsDuration.value Implement with version: STU 1.0.0S
HSD07ServiceRequest.occurrenceTiming.extension(calendarPattern) The calendarPattern extension type is a CodeableConcept and is populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- timingcalendarpattern' extension[n].valueCodeableConcept.coding[0].system = 'https://codesystem.x12.org/005010/678' extension[n].valueCodeableConcept.coding[0].code = value of HSD07 Implement with version: STU 1.0.0S
HSD08ServiceRequest.occurrenceTiming.extension(deliveryPattern) The deliveryPattern extension type is a CodeableConcept and is populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- timingdeliverypattern' extension[n].valueCodeableConcept.coding[0].system = 'https://codesystem.x12.org/005010/679' extension[n].valueCodeableConcept.coding[0].code = value of HSD08 Implement with version: STU 1.0.0S
CL1 - 2000EThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
CR1 - 2000EThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
CR2 - 2000EThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
CR5 - 2000EThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
CR6 - 2000EThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
PWK - 2000EClaimResponse.communicationRequest[n].reference => CommunicationRequest Create a CommunicationRequest that conforms to the PAS CommunicationRequest and then set the reference to the new resource in the Bundle. Also set the following attributes on the CommunicationRequest: CommunicationRequest.status = 'active' CommunicationRequest.requestor.reference => Organization created in 2000B CommunicationRequest.sender.reference => Organization created in 2010A Implement with version: STU 1.0.0S
PWK01CommunicationRequest.category[0] Populate the components of the category (datatype CodeableConcept) as follows: category[0].coding[0].system = 'https://codesystem.x12.org/005010/755' category[0].coding[0].code = value of PWK01 Implement with version: STU 1.0.0R
PWK02CommunicationRequest.medium[0] Populate the components of the medium (datatype CodeableConcept) as follows: medium[0].coding[0].system = 'https://codesystem.x12.org/005010/756' medium[0].coding[0].code = value of PWK02 Implement with version: STU 1.0.0R
PWK05The data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.1.0S
PWK06CommunicationRequest.identifier[0].value Implement with version: STU 1.0.0S
PWK07CommunicationRequest.category.text Implement with version: STU 1.0.0S
MSG - 2000EThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
MSG01ClaimResponse.processNote[n].text When a MSG segment is encountered, a new processNote entry is created. The number attribute of the processNote would be set to the value of '1'. For MSG in the 2000E, the note is referenced in the first ClaimResponse.item created for the first 2000F service as follows: ClaimResponse.item[0].noteNumber[0] = processNote[0].number (from above) Implement with version: STU 1.0.0R
NM1 - 2010EAThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
REF - 2010EAThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
N3 - 2010EAThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
N4 - 2010EAThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
PER - 2010EAThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
AAA - 2010EAThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
PRV - 2010EAThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
NM1 - 2010EBThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
N3 - 2010EBThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
N4 - 2010EBThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
PER - 2010EBThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
NM1 - 2010ECThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
N3 - 2010ECThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
N4 - 2010ECThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
AAA - 2010ECThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HL - 2000FClaimResponse.item[n] For each iteration of the 2000F create a new ClaimResponse.item Implement with version: STU 1.0.0S
HL01ClaimResponse.item[n].itemSequence Implement with version: STU 1.0.0R
HL02This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
HL03This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
HL04This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
TRN - 2000FFor each TRN segment create an itemTraceNumber extension. Implement with version: STU 1.1.0S
TRN01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.1.0R
TRN02ClaimResponse.item[n].extension(itemTraceNumber) Populate the components of the extension as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- itemTraceNumber' extension[n].valueIdentifier.value = value of TRN02 Implement with version: STU 1.1.0R
TRN03extension[n].valueIdentifier.assigner.identifier.value = value of TRN03 Implement with version: STU 1.1.0R
TRN04extension[n].valueIdentifier.extension[0].valueString = value of TRN04 extension[n].valueIdentifier.extension[0].url= 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- identifierSubDepartment' Implement with version: STU 1.1.0S
AAA - 2000FThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
AAA01ClaimResponse.error[n].extension(errorPlace) The value of AAA01 is NOT used but the location of this AAA segment is recorded in the error to provide additional information as follows: extension[0].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- errorElement' extension[0].valueString = '2000F' Implement with version: STU 1.0.0R
AAA03ClaimResponse.error[n].code Populate the components of the code (datatype CodeableConcept) as follows: code.coding[0].system = 'https://codesystem.x12.org/005010/901' code.coding[0].code = value of AAA03 Implement with version: STU 1.0.0R
AAA04ClaimResponse.error[n].extension(followupActionCode) The followupActionCode extension type is a CodeableConcept and is populated as follows: extension[1].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- errorFollowupAction' extension[1].valueCodeableConcept.coding[0].system = 'https://codesystem.x12.org/005010/889' extension[1].valueCodeableConcept.coding[0].code = value of AAA04 Implement with version: STU 1.0.0R
UM - 2000FThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HCR - 2000FClaimResponse.item[n].adjudication[0].extension(reviewAction) The components of the HCR segment are used to populate the complex extensions within the reviewAction extension. The base reviewAction extension is populate as follows: item[n].extension[n].extension[] -> see HCR attributes below item[n].extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- reviewAction' item[n].adjudication[0].category.coding[0].system = 'http://terminology.hl7.org/CodeSystem/adjudication' item[n].adjudication[0].category.coding[0].value = 'submitted' Implement with version: STU 1.1.0S
HCR01.extension(reviewActionCode) The reviewActionCode extension is a CodeableConcept and populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- review ActionCode' extension[n].valueCodeableConcept.coding[0].system = 'https://codesystem.x12.org/005010/306' extension[n].valueCodeableConcept.coding[0].code = HCR01 Implement with version: STU 1.0.0R
HCR02.extension(number) The number extension is a string and is populated as follows: extension[n].url = 'number' extension[n].valueString = HCR02 Implement with version: STU 1.0.0S
HCR03.extension(reasonCode) Create one of the following for each repetition of the reasonCode sent. The reasonCode extension is a CodeableConcept and is populated as follows: extension[n].url = 'reasonCode' extension[n].valueCodeableConcept.coding[0].system = 'https://codesystem.x12.org/005010/886' extension[n].valueCodeableConcept.coding[0].code = value of HCR03 Implement with version: STU 1.1.0S
HCR04.extension(secondSurgicalOpinionFlag) The number extension is a boolean and populated as follows: extension[n].url = 'secondSurgicalOpinionFlag' extension[n].valueString = true if HCR04 = 'Y', false if HCR04 = 'N' Implement with version: STU 1.0.0S
REF - 2000FThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
REF01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
REF02ClaimResponse.item[n].extension(administrationReferenceNumber) The administrationReferenceNumber extension type is a string and is populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- administrationReferenceNumber' extension[n].valueString = value of REF02 Implement with version: STU 1.0.0R
REF - 2000FThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
REF01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
REF02ClaimResponse.item[n].extension(authorizationNumber) The authorizationNumber extension type is a string and is populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- authorizationNumber' extension[n].valueString = value of REF02 Implement with version: STU 1.0.0R
DTP - 2000FThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
DTP01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
DTP02See note on DTP03 Implement with version: STU 1.0.0R
DTP03ClaimResponse.item[n].extension(authorizedDate) If DTP02 = 'D8' extension type is dateTime and is populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- itemAuthorizedDate' extension[n].valueDateTime = value of DTP03 If DTP02 = 'RD8' extension type is Period and is populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- itemAuthorizedDate' extension[n].valuePeriod.start = value of DTP03 before '-' extension[n].valuePeriod.end = value of DTP03 after '-' Implement with version: STU 1.0.0R
DTP - 2000FThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
DTP01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
DTP02This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
DTP03ClaimResponse.item[n].extension(preAuthIssueDate) The extension type is dateTime and is populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- itemPreAuthIssueDate' extension[n].valueDateTime = value of DTP03 Implement with version: STU 1.0.0R
DTP - 2000FThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
DTP01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
DTP02This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
DTP03ClaimResponse.item[n].extension(preAuthPeriod) If DTP02 = 'D8' extension type is dateTime and is populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- itemPreAuthPeriod' extension[n].valuePeriod.end = value of DTP03 Implement with version: STU 1.0.0R
DTP - 2000FThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
DTP01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
DTP02See note on DTP03 Implement with version: STU 1.0.0R
DTP03ClaimResponse.item[n].extension(preAuthPeriod) If DTP02 = 'D8' extension type is dateTime and is populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- itemPreAuthPeriod' extension[n].valuePeriod.start = value of DTP03 If DTP02 = 'RD8' extension type is Period and is populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- itemPreAuthPeriod' extension[n].valuePeriod.start = value of DTP03 before '-' extension[n].valuePeriod.end = value of DTP03 after '-' Implement with version: STU 1.0.0R
HI - 2000FCheck for an existing PAS Communication Request: ClaimResponse.communicationRequest[n].reference => CommunicationRequest If one is not found create a CommunicationRequest that conforms to the PAS CommunicationRequest and then set the reference to the new resource in the Bundle. Also set the following attributes on the CommunicationRequest: CommunicationRequest.status = 'active' CommunicationRequest.requestor.reference => Organization created in 2000B Then for each HIXX-02, create a communication payload, within the CommunicationRequest. If an exisiting PAS Communication Request is found: For each HIXX-02, create a communication payload, within the existing CommunicationRequest. The end result should be one communication request with a payload loop for each HIXX-02. Implement with version: STU 1.1.0S
HI01-01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
HI01-02CommunicationRequest.payload[n].extension(extension-serviceLineNumber) as follows: payload[n].extension[0].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- serviceLineNumber' payload[n].extension[0].valuePositiveInt = value of HL01 Populate the content as follows: payload[n].contentString = value of HI01-02 Implement with version: STU 1.1.0R
HI02-01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
HI02-02CommunicationRequest.payload[n].extension(extension-serviceLineNumber) as follows: payload[n].extension[0].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- serviceLineNumber' payload[n].extension[0].valuePositiveInt = value of HL01 Populate the content as follows: payload[n].contentString = value of HI02-02 Implement with version: STU 1.1.0R
HI03-01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
HI03-02CommunicationRequest.payload[n].extension(extension-serviceLineNumber) as follows: payload[n].extension[0].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- serviceLineNumber' payload[n].extension[0].valuePositiveInt = value of HL01 Populate the content as follows: payload[n].contentString = value of HI03-02 Implement with version: STU 1.1.0R
HI04-01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
HI04-02CommunicationRequest.payload[n].extension(extension-serviceLineNumber) as follows: payload[n].extension[0].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- serviceLineNumber' payload[n].extension[0].valuePositiveInt = value of HL01 Populate the content as follows: payload[n].contentString = value of HI04-02 Implement with version: STU 1.1.0R
HI05-01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
HI05-02CommunicationRequest.payload[n].extension(extension-serviceLineNumber) as follows: payload[n].extension[0].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- serviceLineNumber' payload[n].extension[0].valuePositiveInt = value of HL01 Populate the content as follows: payload[n].contentString = value of HI05-02 Implement with version: STU 1.1.0R
HI06-01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
HI06-02CommunicationRequest.payload[n].extension(extension-serviceLineNumber) as follows: payload[n].extension[0].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- serviceLineNumber' payload[n].extension[0].valuePositiveInt = value of HL01 Populate the content as follows: payload[n].contentString = value of HI06-02 Implement with version: STU 1.1.0R
HI07-01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
HI07-02CommunicationRequest.payload[n].extension(extension-serviceLineNumber) as follows: payload[n].extension[0].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- serviceLineNumber' payload[n].extension[0].valuePositiveInt = value of HL01 Populate the content as follows: payload[n].contentString = value of HI07-02 Implement with version: STU 1.1.0R
HI08-01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
HI08-02CommunicationRequest.payload[n].extension(extension-serviceLineNumber) as follows: payload[n].extension[0].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- serviceLineNumber' payload[n].extension[0].valuePositiveInt = value of HL01 Populate the content as follows: payload[n].contentString = value of HI08-02 Implement with version: STU 1.1.0R
HI09-01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
HI09-02CommunicationRequest.payload[n].extension(extension-serviceLineNumber) as follows: payload[n].extension[0].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- serviceLineNumber' payload[n].extension[0].valuePositiveInt = value of HL01 Populate the content as follows: payload[n].contentString = value of HI09-02 Implement with version: STU 1.1.0R
HI10-01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
HI10-02CommunicationRequest.payload[n].extension(extension-serviceLineNumber) as follows: payload[n].extension[0].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- serviceLineNumber' payload[n].extension[0].valuePositiveInt = value of HL01 Populate the content as follows: payload[n].contentString = value of HI10-02 Implement with version: STU 1.1.0R
HI11-01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
HI11-02CommunicationRequest.payload[n].extension(extension-serviceLineNumber) as follows: payload[n].extension[0].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- serviceLineNumber' payload[n].extension[0].valuePositiveInt = value of HL01 Populate the content as follows: payload[n].contentString = value of HI11-02 Implement with version: STU 1.1.0R
HI12-01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
HI12-02CommunicationRequest.payload[n].extension(extension-serviceLineNumber) as follows: payload[n].extension[0].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- serviceLineNumber' payload[n].extension[0].valuePositiveInt = value of HL01 Populate the content as follows: payload[n].contentString = value of HI12-02 Implement with version: STU 1.1.0R
SV1 - 2000FClaimResponse.item[n].extension(authorizedItemDetail) The components of the SV1 segment are used to create the authorizedItemDetail extension in an item (created for the 2000F loop as noted above in the 2000F HL). The authorizedItemDetail is a complex extension, and does not contain a value but rather contains its own extensions for each of the SV1 attributes. The base format of the authorizedItemDetail is: item[n].extension[n].extension[] -- see SV1 attributes below item[n]extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- itemAuthorizedDetail' Implement with version: STU 1.0.0S
SV101-01Convert for use in SV101-02, SV101-03, SV101-07, SV101-08 The converted value is in populating the values for the other attributes of SV1. The value is converted as follows: HC Shall be translated into either the URL for HCPCS or CPT as follows: If the 1st position of the code an Alpha Character (A-Z) HC = 'http://www.cms.gov/Medicare/Coding/HCPCSReleaseCodeSets' If the 1st position of the code is a Numberic (0-9) HC = 'http://www.ama-assn.org/go/cpt' N4 = 'http://hl7.org/fhir/sid/ndc' Implement with version: STU 1.1.0R
SV101-02.extension(productOrServiceCode) The productOrServiceCode extension is comprised of multiple attributes from the SV1 as follows: extension[n].url = 'productOrServiceCode' extension[n].valueCodeableConcept.coding[0].s ystem = no value extension[n].valueCodeableConcept.coding[0].code = value of SV101-02 extension[n].valueCodeableConcept.text = value of SV101-07 Implement with version: STU 1.0.0R
SV101-03.extension(modifier) The modifier extension is comprised as follows: extension[n].url = 'modifier' extension[n].valueCodeableConcept.coding[0].system = no value extension[n].valueCodeableConcept.coding[0].code = value of SV101-03 Implement with version: STU 1.0.0S
SV101-04.extension(modifier) The modifier extension is comprised as follows: extension[n].url = 'modifier' extension[n].valueCodeableConcept.coding[0].system = no value extension[n].valueCodeableConcept.coding[0].code = value of SV101-04 Implement with version: STU 1.0.0S
SV101-05.extension(modifier) The modifier extension is comprised as follows: extension[n].url = 'modifier' extension[n].valueCodeableConcept.coding[0].system = no value extension[n].valueCodeableConcept.coding[0].code = value of SV101-05 Implement with version: STU 1.0.0S
SV101-06.extension(modifier) The modifier extension is comprised as follows: extension[n].url = 'modifier' extension[n].valueCodeableConcept.coding[0].system = no value extension[n].valueCodeableConcept.coding[0].code = value of SV101-06 Implement with version: STU 1.0.0S
SV101-07.extension(productOrServiceCode) See SV101-02 for using this attribute in the productOrServiceCode Implement with version: STU 1.0.0S
SV101-08.extension(productOrServiceCodeEnd) The productOrServiceCodeEnd extension is comprised as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- productOrServiceCodeEnd' extension[n].valueCodeableConcept.coding[0].system = no value extension[n].valueCodeableConcept.coding[0].code = value of SV101-08 Implement with version: STU 1.0.0S
SV102.extension(unitPrice) The unitPrice extension is comprised as follows: extension[n].url = 'unitPrice' extension[n].valueMoney.value = value of SV102 extension[n].valueMoney.currency = 'USD' Note it is assumed that all money values are in US dollars Implement with version: STU 1.0.0S
SV103.extension(quantity) The quantity extension is comprised as follows: extension[n].url = 'quantity' extension[n].valueSimpleQuantity.value = value of SV104 extension[n].valueSimpleQuantity.unit = value of SV103 Implement with version: STU 1.0.0S
SV104See SV103 above Implement with version: STU 1.0.0S
SV111.extension(epsdtIndicator) The epsdtIndicator is a boolean and is populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- epsdtIndicator' extension[n].valueBoolean = value of SV111 Implement with version: STU 1.0.0S
SV120.extension(nursingHomeLevelOfCare) The nursingHomeLevelOfCare extension is a CodeableConcept and is populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- nursingHomeLevelOfCare' extension[n].valueCodeableConcept.coding[0].system = 'https://codesystem.x12.org/005010/1337' extension[n].valueCodeableC oncept.coding[0].code = value of SV120 Implement with version: STU 1.0.0S
SV2 - 2000FClaimResponse.item[n].extension(authorizedItemDetail) The components of the SV2 segment are used to create the authorizedItemDetail extension in an item (created for the 2000F loop as noted above). The authorizedItemDetail is a complex extension, and does not contain a value but rather contains its own extensions for each of the SV2 attributes. The base format of the authorizedItemDetail is: item[n].extension[n].extension[] -- see SV2 attributes below item[n]extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- itemAuthorizedDetail' Implement with version: STU 1.0.0S
SV201.extension(revenue) The revenue extension is a CodeableConcept and is populated as follows: extension[n].url = 'revenue' extension[n].valueCodeableConcept.coding[0].system = 'http://www.nubc.org/revenue-code' extension[n].valueCodeableConcept .coding[0].code = value of SV201 Implement with version: STU 1.0.0S
SV202-01Convert for use in SV202-02, SV202-03, SV202-07, SV202-08 The converted value is in populating the values for the other attributes of SV2. The value is converted as follows: HC Shall be translated into either the URL for HCPCS or CPT as follows: If the 1st position of the code an Alpha Character (A-Z) HC = 'http://www.cms.gov/Medicare/Coding/HCPCSReleaseCodeSets' If the 1st position of the code is a Numberic (0-9) HC = 'http://www.ama-assn.org/go/cpt' N4 = 'http://hl7.org/fhir/sid/ndc' Implement with version: STU 1.1.0R
SV202-02.extension(productOrServiceCode) The productOrServiceCode extension is comprised of multiple attributes from the SV2 as follows: extension[n].url = 'productOrServiceCode' extension[n].valueCodeableConcept.coding[0].s ystem = no value extension[n].valueCodeableConcept.coding[0].code = value of SV202-02 extension[n].valueCodeableConcept.text = value of SV202-07 Implement with version: STU 1.0.0R
SV202-03.extension(modifier) The modifier extension is comprised as follows: extension[n].url = 'modifier' extension[n].valueCodeableConcept.coding[0].system = no value extension[n].valueCodeableConcept.coding[0].code = value of SV202-03 Implement with version: STU 1.0.0S
SV202-04.extension(modifier) The modifier extension is comprised as follows: extension[n].url = 'modifier' extension[n].valueCodeableConcept.coding[0].system = no value extension[n].valueCodeableConcept.coding[0].code = value of SV202-04 Implement with version: STU 1.0.0S
SV202-05.extension(modifier) The modifier extension is comprised as follows: extension[n].url = 'modifier' extension[n].valueCodeableConcept.coding[0].system = no value extension[n].valueCodeableConcept.coding[0].code = value of SV202-05 Implement with version: STU 1.0.0S
SV202-06.extension(modifier) The modifier extension is comprised as follows: extension[n].url = 'modifier' extension[n].valueCodeableConcept.coding[0].system = no value extension[n].valueCodeableConcept.coding[0].code = value of SV202-06 Implement with version: STU 1.0.0S
SV202-07.extension(productOrServiceCode) See SV202-02 for using this attribute in the productOrServiceCode Implement with version: STU 1.0.0S
SV202-08.extension(productOrServiceCodeEnd) The productOrServiceCodeEnd extension is comprised as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- productOrServiceCodeEnd' extension[n].valueCodeableConcept.coding[0].system = no value extension[n].valueCodeableConcept.coding[0].code = value of SV202-08 Implement with version: STU 1.0.0S
SV203.extension(unitPrice) The unitPrice extension is comprised as follows: extension[n].url = 'unitPrice' extension[n].valueMoney.value = value of SV203 extension[n].valueMoney.currency = 'USD' Note it is assumed that all money values are in US dollars Implement with version: STU 1.0.0S
SV204.extension(quantity) The quantity extension is comprised as follows: extension[n].url = 'quantity' extension[n].valueSimpleQuantity.value = value of SV205 extension[n].valueSimpleQuantity.unit = value of SV204 Implement with version: STU 1.0.0S
SV205See SV204 above Implement with version: STU 1.0.0S
SV206.extension(revenueUnitRateLimit) The revenueUnitRateLimit extension is a decimal and is populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- revenueUnitRateLimit' extension[n].valueDecimal = value of SV206 Implement with version: STU 1.0.0S
SV210.extension(nursingHomeLevelOfCare) The nursingHomeLevelOfCare extension is a CodeableConcept and is populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- nursingHomeLevelOfCare' extension[n].valueCodeableConcept.coding[0].system = 'https://codesystem.x12.org/005010/1337' extension[n].valueCodeableConcept.coding[0].code = value of SV210 Implement with version: STU 1.0.0S
SV3 - 2000FThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
TOO - 2000FThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0S
HSD - 2000F.extension(requestedService) => ServiceRequest Create a ServiceRequest that adheres to the PAS Service Request profile and then set a reference to the Resource in the extension as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- requestedService' extension[n].valueReference.reference = Set the ServiceRequest.subject to the value of ClaimResponse.patient Note: Though a MedicationRequest would be preferable if the value of SV101-1 or SV202-1 is N4, the PAS Medication Request profile requires that the medication be specified using RxNorm which is not available on the 278 response Implement with version: STU 1.0.0S
HSD01ServiceRequest.quantityQuantity.unit Implement with version: STU 1.0.0S
HSD02ServiceRequest.quantityQuantity.value Implement with version: STU 1.0.0S
HSD03ServiceRequest.occurrenceTiming.repeat.periodUnit Translate the HSD03 value as follows: 'DA' -> 'd' 'WK' -> 'wk' 'MO' -> 'mo' Implement with version: STU 1.0.0S
HSD04ServiceRequest.occurrenceTiming.repeat.period Implement with version: STU 1.0.0S
HSD05ServiceRequest.occurrenceTiming.repeat.boundsDuration.unit Implement with version: STU 1.0.0S
HSD06ServiceRequest.occurrenceTiming.repeat.boundsDuration.value Implement with version: STU 1.0.0S
HSD07ServiceRequest.occurrenceTiming.extension(calendarPattern) The calendarPattern extension type is a CodeableConcept and is populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- timingcalendarpattern' extension[n].valueCodeableConcept.coding[0].system = 'https://codesystem.x12.org/005010/678' extension[n].valueCodeableConcept.coding[0].code = value of HSD07 Implement with version: STU 1.0.0S
HSD08ServiceRequest.occurrenceTiming.extension(deliveryPattern) The deliveryPattern extension type is a CodeableConcept and is populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- timingdeliverypattern' extension[n].valueCodeableConcept.coding[0].system = 'https://codesystem.x12.org/005010/679' extension[n].valueCodeableConcept.coding[0].code = value of HSD08 Implement with version: STU 1.0.0S
PWK - 2000FClaimResponse.communicationRequest[n].reference => CommunicationRequest Create a CommunicationRequest that conforms to the PAS CommunicationRequest and then set the reference to the new resource in the Bundle. Also set the following attributes on the CommunicationRequest: CommunicationRequest.status = 'active' CommunicationRequest.requestor.reference => Organization created in 2000B CommunicationRequest.sender.reference => Organization created in 2010A Implement with version: STU 1.0.0S
PWK01CommunicationRequest.category[0] Populate the components of the category (datatype CodeableConcept) as follows: category[0].coding[0].system = 'https://codesystem.x12.org/005010/755' category[0].coding[0].code = value of PWK01 Implement with version: STU 1.0.0R
PWK02CommunicationRequest.medium[0] Populate the components of the medium (datatype CodeableConcept) as follows: medium[0].coding[0].system = 'https://codesystem.x12.org/005010/756' medium[0].coding[0].code = value of PWK02 Implement with version: STU 1.0.0R
PWK05This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.1.0S
PWK06CommunicationRequest.identifier[0].value Implement with version: STU 1.0.0S
PWK07CommunicationRequest.category.text Implement with version: STU 1.0.0S
MSG - 2000FThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
MSG01ClaimResponse.processNote[n].text For each MSG segment encountered, a new processNote entry is created. The number attribute of the processNote would be set to the next ordinal value. Then the note is referenced in the ClaimResponse.item created for this 2000F service as follows: ClaimResponse.item[n].noteNumber[n] = processNote[n].number (from above) Implement with version: STU 1.0.0R
NM1 - 2010FAClaimResponse.item[n].extension(itemAuthorizedProvider) => Practitioner | Organization Create either a Practitioner or Organization (see NM102 note below) and the set a reference to the Resource in the extension as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- itemAuthorizedProvider' extension[n].extension[0].url = 'provider' extension[n].extension[0].valueReference.reference = Implement with version: STU 1.1.0S
NM101extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- itemAuthorizedProvider' extension[n].extension[1].url = 'providerType' extension[n].extension[1].valueCodeableConcept.coding[0].code = value of NM101 Implement with version: STU 1.1.0R
NM102if NM102 = '1' the created Resource will be a Practitioner that follows the PAS Practitioner profile if NM102 = '2' the created Resource will be an Organization that follows the US Core Organization Profile Implement with version: STU 1.0.0R
NM103Practitioner.name.family | Organization.name Implement with version: STU 1.0.0S
NM104Practitioner.name.given[0] | not used on Organzation Implement with version: STU 1.0.0S
NM105Practitioner.name.given[1] | not used on Organzation Implement with version: STU 1.0.0S
NM106Practitioner.name.prefix[0] | not used on Organzation Implement with version: STU 1.0.0S
NM107Practitioner.name.suffix[0] | not used on Organzation Implement with version: STU 1.0.0S
NM108Practitioner.identifier[0].type | Organization.identifier[0].type Populate the components of the type (datatype CodeableConcept) as follows: type.coding[0].system = 'http://terminology.hl7.org/CodeSystem/v2-0203' type.coding[0].code = value of NM108 translated as follows: '24' -> 'EN' '34' -> 'SB' '46' -> '46' 'XX' -> 'NPI' Implement with version: STU 1.1.0S
NM109Practitioner.identifier[0].value | Organization.identifier[0].value Implement with version: STU 1.0.0S
REF - 2010FAThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
REF01Practitioner.identifier[1].type | Organization.identifier[0].type Populate the components of the type (datatype CodeableConcept) as follows: type.coding[0].system = 'http://terminology.hl7.org/CodeSystem/v2-0203' type.coding[0].code = value of NM108 translated as follows: '0B' -> 'SL' '1G' -> 'UPIN' '1J' -> 'FI' 'EI' -> 'EN' 'N5' -> 'N5' 'N7' -> 'N7' 'SY' -> 'SB' 'ZH' -> 'ZH' Implement with version: STU 1.1.0R
REF02Practitioner.identifier[1].value | Organization.identifier[0].value Implement with version: STU 1.0.0R
REF03Practitioner.identifier[1].extension(identifierJurisdiction).coding[0]. code | Not populated for Organization Implement with version: STU 1.1.0S
N3 - 2010FAThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
N301Practitioner.address[0].line[0] | Organization.address[0].line[0] Implement with version: STU 1.0.0R
N302Practitioner.address[0].line[1] | Organization.address[0].line[1] Implement with version: STU 1.0.0S
N4 - 2010FAThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
N401Practitioner.address[0].city | Organization.address[0].city Implement with version: STU 1.0.0R
N402Practitioner.address[0].state | Organization.address[0].state Implement with version: STU 1.0.0S
N403Practitioner.address[0].postalCode | Organization.address[0].postalCode Implement with version: STU 1.0.0S
N404Practitioner.address[0].country | Organization.address[0].country Implement with version: STU 1.0.0S
N407Practitioner.address[0].district | Organization.address[0].district Implement with version: STU 1.0.0S
PER - 2010FAThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
PER01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
PER02not used on Practitioner | 'Organization.contact.name Populate the 'text' attribute of the name Implement with version: STU 1.0.0S
PER03Practitioner.telecom[0].system | Organization.contact.telecom[0].system Translate the PER03 value as follows: EM -> email FX -> fax TE -> phone UR -> url Implement with version: STU 1.0.0S
PER04Practitioner.telecom[0].value | Organization.contact.telecom[0].value Implement with version: STU 1.0.0S
PER05Practitioner.telecom[1].system | Organization.contact.telecom[1].system When PER05 is NOT equal to 'EX' create a new telecom element and translate PER05 as per the note for PER03. Implement with version: STU 1.0.0S
PER06Practitioner.telecom[1].value | Organization.contact.telecom[1].value If PER05 is NOT 'EX' store this value in the telecom[1].value If PER05 is 'EX' append the value formatted: ' ext. ' to telecom[0].value See ITU-T E.123 for format of telephone values Implement with version: STU 1.0.0S
PER07Practitioner.telecom[n].system | Organization.contact.telecom[n].system When PER07 is NOT equal to 'EX' create a new telecom element and translate PER07 as per the note for PER03. If PER05 was not 'EX' this will be telecom[2] otherwise this will be the 2nd telecom element. Implement with version: STU 1.0.0S
PER08Practitioner.telecom[n].value | Organization.contact.telecom[n].value If PER07 is NOT 'EX' store this value in the telecom[x].value If PER07 is 'EX' append the value formatted: ' ext. ' to telecom[1].value See ITU-T E.123 for format of telephone values Implement with version: STU 1.0.0S
AAA - 2010FAThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
AAA01ClaimResponse.error[n].extension(errorPlace) The value of AAA01 is NOT used but the location of this AAA segment is recorded in the error to provide additional information as follows: extension[0].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- errorElement' extension[0].valueString = '2010FA' Implement with version: STU 1.0.0R
AAA03ClaimResponse.error[n].code Populate the components of the code (datatype CodeableConcept) as follows: code.coding[0].system = 'https://codesystem.x12.org/005010/901' code.coding[0].code = value of AAA03 Implement with version: STU 1.0.0R
AAA04ClaimResponse.error[n].extension(followupActionCode) The followupActionCode extension type is a CodeableConcept and is populated as follows: extension[1].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension- errorFollowupAction' extension[1].valueCodeableConcept.coding[0].system = 'https://codesystem.x12.org/005010/889' extension[1].valueCodeableConcept.coding[0].code = value of AAA04 Implement with version: STU 1.0.0R
PRV - 2010FAThe data elements in this segment are defined in the PAS Claim Inquiry Response profile, see the FHIR Mapping instructions for each data element below. Not used for Organzation Implement with version: STU 1.1.0S
PRV01This data element is not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.1.0R
PRV02This data element is not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.1.0R
PRV03Practitioner.qualification[0].code.coding[0].system = 'https://codesystem.x12.org/005010/127' Practitioner.qualification[0].code.coding[0].code = value of PRV03 Implement with version: STU 1.1.0R
NM1 - 2010FBThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. When the current 2000F has a PWK segment: CommunicationRequest.recipient.reference => Practitioner | Organization Create either a Practitioner or Organization (see NM102 below) and the set a reference to the Resource. Implement with version: STU 1.0.0S
NM101This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
NM102if NM102 = '1' the created Resource will be a Practitioner that follows the PAS Practitioner profile if NM102 = '2' the created Resource will be an Organization that follows the US Core Organization Profile Implement with version: STU 1.0.0R
NM103Practitioner.name.family | Organization.name Implement with version: STU 1.0.0S
NM104Practitioner.name.given[0] | not used on Organzation Implement with version: STU 1.0.0S
NM105Practitioner.name.given[1] | not used on Organzation Implement with version: STU 1.0.0S
NM107Practitioner.name.suffix[0] | not used on Organzation Implement with version: STU 1.0.0S
NM108Practitioner.identifier[0].type | Organization.identifier[0].type Populate the components of the type (datatype CodeableConcept) as follows: type.coding[0].system = 'http://terminology.hl7.org/CodeSystem/v2-0203' type.coding[0].code = value of NM108 translated as follows: '24' -> 'EN' '34' -> 'SB' '46' -> '46' 'PI' -> 'U' 'XX' -> 'NPI' Implement with version: STU 1.1.0S
NM109Practitioner.identifier[0].value | Organization.identifier[0].value Implement with version: STU 1.0.0S
N3 - 2010FBThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
N301Practitioner.address[0].line[0] | Organization.address[0].line[0] Implement with version: STU 1.0.0R
N302Practitioner.address[0].line[1] | Organization.address[0].line[1] Implement with version: STU 1.0.0S
N4 - 2010FBThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
N401Practitioner.address[0].city | Organization.address[0].city Implement with version: STU 1.0.0R
N402Practitioner.address[0].state | Organization.address[0].state Implement with version: STU 1.0.0S
N403Practitioner.address[0].postalCode | Organization.address[0].postalCode Implement with version: STU 1.0.0S
N404Practitioner.address[0].country | Organization.address[0].country Implement with version: STU 1.0.0S
N407Practitioner.address[0].district | Organization.address[0].district Implement with version: STU 1.0.0S
PER - 2010FBThe data elements in this segment are defined in the PAS Claim Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
PER01This data element is not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R
PER02not used on Practitioner | 'Organization.contact.name Populate the 'text' attribute of the name Implement with version: STU 1.0.0S
PER03Practitioner.telecom[0].system | Organization.contact.telecom[0].system Translate the PER03 value as follows: EM -> email FX -> fax TE -> phone UR -> url Implement with version: STU 1.0.0S
PER04Practitioner.telecom[0].value | Organization.contact.telecom[0].value Implement with version: STU 1.0.0S
PER05Practitioner.telecom[1].system | Organization.contact.telecom[1].system When PER05 is NOT equal to 'EX' create a new telecom element and translate PER05 as per the note for PER03. Implement with version: STU 1.0.0S
PER06Practitioner.telecom[1].value | Organization.contact.telecom[1].value If PER05 is NOT 'EX' store this value in the telecom[1].value If PER05 is 'EX' append the value formatted: ' ext. ' to telecom[0].value See ITU-T E.123 for format of telephone values Implement with version: STU 1.0.0S
PER07Practitioner.telecom[n].system | Organization.contact.telecom[n].system When PER07 is NOT equal to 'EX' create a new telecom element and translate PER07 as per the note for PER03. If PER05 was not 'EX' this will be telecom[2] otherwise this will be the 2nd telecom element. Implement with version: STU 1.0.0S
PER08Practitioner.telecom[n].value | Organization.contact.telecom[n].value If PER07 is NOT 'EX' store this value in the telecom[x].value If PER07 is 'EX' append the value formatted: ' ext. ' to telecom[1].value See ITU-T E.123 for format of telephone values Implement with version: STU 1.0.0S
SEThe data elements in this segment are not defined in the PAS Claim Response profile. Implement with version: STU 1.0.0R