278 Request Transaction Set Listing

Usage
Repeats

ISA - INTERCHANGE CONTROL HEADER

X12 Name:
Interchange Control Header
X12 Purpose:
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
  1. All positions within each of the data elements must be filled.
  2. For compliant implementations under this implementation guide, ISA13, the interchange Control Number, must be a positive unsigned number. Therefore, the ISA segment can be considered a fixed record length segment.
  3. The first element separator defines the element separator to be used through the entire interchange.
  4. The ISA segment terminator defines the segment terminator used throughout the entire interchange.
  5. Spaces in the example interchanges are represented by "." for clarity.
TR3 Example:
ISA✱00✱..........✱01✱SECRET....✱ZZ✱SUBMITTERS.ID..✱ZZ✱RECEIVERS.ID...✱030101✱1253✱^✱00501✱000000905✱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
005010X215
Health Care Services Review - Inquiry

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:
This segment indicates the start of a Healthcare Services Review Inquiry 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 review inquiry.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim Inquiry profile because the values are hardcoded or derived.
Implement with version: STU 1.0.0
TR3 Example:
ST✱278✱0001✱005010X215~
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 populated during the transformation between the PAS Claim Inquiry profile and X12 278.
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: '005010X215'
Implement with version: STU 1.0.0
  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
005010X215
Health Care Services Review - Inquiry

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 Inquiry profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
BHT✱0007✱28✱199800114000001✱20050101✱1400✱RD~
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: '28'
Because FHIR requires a patient to be present in the inquiry resource, can only query against a single patient.
Implement with version: STU 1.0.0
CODE
DEFINITION
28
Query
Use when inquiring on authorizations associated with a specific patient.
51
Historical Inquiry
Use on global inquiries for the status of authorizations associated with multiple patients.
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. If the inquiry transaction is processed in real time, the respondent must return this value 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 real time 278 inquiry transactions are required to return the Submitter Transaction Identifier in their 278 response.
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 Inquiry profile because BHT02 will always be '28'.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when BHT02 = 51 and the requester has a preference for full detail or summary responses. If not required by this implementation guide, do not send.
This implementation guide does not require the UMO system to support both summary and detail responses. Refer to Section 1.12.5 for a description of the contents of these responses.
CODE
DEFINITION
RD
Returns Detail
Use this code to request full detail for the available records on the UMO system based on the search criteria provided.
ZW
Sort and Segregate Detail
Use this code to request summary information for the available records on the UMO system based on the search criteria provided.

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 an inquiry transaction, this segment identifies the payer, HMO, or other utilization management organization that is the source of service review decision.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim Inquiry 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. For an inquiry transaction this names the payer or utilization review organization responsible for the health care service review decision.
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
1P
Provider
2B
Third-Party Administrator
36
Employer
PR
Payer
X3
Utilization Management Organization
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
FHIR Mapping: '2'
Implement with version: STU 1.0.0
CODE
DEFINITION
1
Person
Use this code only if the information source/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 Inquiry 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 Inquiry 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 Inquiry 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 until the National PlanID is mandated if the UMO is a payer.
XV
Centers for Medicare and Medicaid Services PlanID
CODE SOURCE: 540: Centers for Medicare and Medicaid Services PlanID
XX
Centers for Medicare and Medicaid Services National Provider Identifier
Required for providers on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider has an NPI and it is available to the submitter;
OR
Required for providers before the mandated HIPAA NPI implementation date when the provider has an NPI and the submitter has the capability to send it.
If not required by this implementation guide, do not send.
CODE SOURCE: 537: Centers for Medicare & Medicaid Services National Provider Identifier
Required
9
67
Identification Code
O 1
AN
2/80
Code identifying a party or other code
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 healthcare services review information receiver. For inquiry transactions, this corresponds to the identification of the entity initiating the inquiry.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim Inquiry 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 entity requesting the service review information.
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✱WHITE✱CHRIS✱✱✱✱46✱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
Signifies the provider making the request.
2A
Federal, State, County or City Facility
2B
Third-Party Administrator
36
Employer
FA
Facility
PR
Payer
X3
Utilization Management Organization
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
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 to identify the requester. If not required by this implementation guide, do not send.
INDUSTRY NAME: Requester Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
FHIR Mapping: This data element is not defined in the PAS Claim Inquiry 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 Inquiry 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 Inquiry 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
Cannot be used for Medicare.
46
Electronic Transmitter Identification Number (ETIN)
PI
Payor Identification
Use until the National PlanID is mandated if the requester is a payer.
XV
Centers for Medicare and Medicaid Services PlanID
Use if the requester is a payer.
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: When Organization.identifier[n].system = 'http://hl7.org/fhir/sid/us-npi' move
Organization.identifier[n].value to NM109
Implement with version: STU 1.2.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:
9
Situational Rule:
Required prior to the mandated HIPAA National Provider Identifier (NPI) implementation date when an identification number other than the NPI is necessary for the UMO to identify the provider;
OR
Required after the mandated NPI implementation date, when the entity is a non-health care provider, and an identifier is necessary for the UMO to identify the entity.
If not required by this implementation guide, do not send.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim Inquiry 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
Use to identify the physician, clinic, or group practice.
N5
Provider Plan Network Identification Number
N7
Facility Network Identification Number
SY
Social Security Number
The social security number must not be used for Medicare. Not used if NM108 = 34.
TJ
Federal Taxpayer's Identification Number
ZH
Carrier Assigned Reference Number
Use for the requester/provider ID as assigned by the UMO.
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 the location is used as identification information for the requester. 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 Inquiry profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.2.0
TR3 Example:
N3✱43 SUNSET 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 the location is used as identification information for the requester. 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.
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: Organization.address[0].district
Implement with version: STU 1.2.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 phone number. If not required by this implementation guide, do not send.
TR3 Notes:
  1. When the communication number represents a telephone number in the United States and other countries using the North American Dialing Plan (for voice, data, fax, etc.), the communication number should always include the area code and phone number using the format AAABBBCCCC. Where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number (e.g. (534)224-2525 would be represented as 5342242525). The extension, when applicable, should be included in the communication number immediately after the telephone number.
  2. Use this segment to identify a contact name and/or communication number for the requester.
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.
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.text
Implement with version: STU 1.2.0
SITUATIONAL RULE: Required when the response must be directed to a particular contact that is different than the entity identified in the NM1 segment of this loop. If not required by this implementation guide, do not send.
INDUSTRY NAME: Requester Contact Name
Required
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
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.
Required
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, remove the extension part of the phone number and place in PER06 and set PER05 to 'EX'
Implement with version: STU 1.2.0
SEGMENT SYNTAX: P0304
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 types are available. If not required by this implementation guide, do not send.
CODE
DEFINITION
EM
Electronic Mail
EX
Telephone Extension
FX
Facsimile
TE
Telephone
UR
Uniform Resource Locator (URL)
Must not contain any characters used as delimiters in this transaction.
Situational
6
364
Communication Number
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 extracted value for the extension from PER04
Otherwise refer to PER04 for rules on formatting
Implement with version: STU 1.2.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: 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 types are available. If not required by this implementation guide, do not send.
CODE
DEFINITION
EM
Electronic Mail
EX
Telephone Extension
FX
Facsimile
TE
Telephone
UR
Uniform Resource Locator (URL)
Must not contain any characters used as delimiters in this transaction.
Situational
8
364
Communication Number
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 extracted value for the extension from PER06
Otherwise refer to PER04 for rules on formatting
Implement with version: STU 1.2.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: 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 sending a global inquiry on the status of all health care service reviews for the patient event or service type specified in Loop 2000E and/or 2000F to identify if the requester is the original requesting provider, the patient event/service provider, or primary care provider of record for the patient(s) or when the requester needs to indicate the inquiring provider's role in the care of the patient identified in Loop 2000C or 2000D and the inquiring 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 Inquiry profile.
Implement with version: STU 1.0.0
TR3 Example:
PRV✱PC✱PXC✱203BA0000Y~
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
Identifies the inquiring provider as the original ordering provider.
OT
Other Physician
PC
Primary Care Physician
Identifes the inquiring provider as the primary care provider of record.
PE
Performing
RF
Referring
Identifies the inquiring provider as the original referring provider.
Situational
2
128
Reference Identification Qualifier
O 1
ID
2/3
Code qualifying the Reference Identification
SEGMENT SYNTAX: P0203
SITUATIONAL RULE: Required when the requesting provider's specialty is used to further 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.
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 the requesting provider's specialty is used 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: 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 HIERARCHICAL LEVEL

X12 Name:
Hierarchical Level
X12 Purpose:
To identify dependencies among and the content of hierarchically related groups of data segments
X12 Comments:
  1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
  2. The HL segment defines a top-down/left-right ordered structure.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
This segment is required when inquiring on the status of authorizations for a specific patient. If not required by this implementation guide, do not send.
TR3 Notes:
  1. 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.
  2. A transaction submitted in real time mode can inquire on a maximum of one patient. A transaction submitted in batch mode can contain a maximum of ninety-nine patient requests. Each patient is defined as either one subscriber loop if the member is the patient, or one subscriber loop and one dependent loop if the dependent is the patient.
  3. The Subscriber Hierarchical level (Loop 2000C) is required if the inquiry concerns authorizations for a specific patient. Situational use of this segment enables the requester to create an inquiry that does not specify the name or member information for each patient. If the requester omits this loop on the inquiry, the requester can inquire on the status of all the health care services review requests for which the provider is the original requesting provider, the patient event/service provider, or primary care provider of record for the patient(s).

    For the UMO to respond to this type of inquiry, the UMO must provide other methods of access to authorizations on file in addition to access by member ID. This guide does not require UMOs to support this level of inquiry. Support at this level is at the discretion of the UMO. The UMO must authenticate that the entity initiating the inquiry has a relationship with this patient that authorizes the requester to receive this information.
  4. Patient Event Loop 2000E must be valued if Loop 2000C is not valued.
  5. 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 Inquiry 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
0
No Subordinate HL Segment in This Hierarchical Structure.
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.

TRN*1 - SUBSCRIBER 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 subscriber is the patient and the requester needs to assign a unique trace number to track this inquiry at the patient level. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
TR3 Notes:
  1. 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.
  2. Each trace number provided in the TRN segment at this level on the inquiry 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 not defined in the PAS Claim Inquiry profile.
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
CODE
DEFINITION
1
Current Transaction Trace Numbers
Required
2
127
Reference Identification
M 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: TRN02 provides unique identification for the transaction.
INDUSTRY NAME: Subscriber Trace Number
Required
3
509
Originating Company Identifier
O 1
AN
10
A unique identifier designating the company initiating the funds transfer instructions, business transaction or assigning tracking reference identification.
SEMANTIC: TRN03 identifies an organization.
INDUSTRY NAME: Trace Assigning Entity Identifier
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.

The first position must be either a "1" if an EIN is used, a "3" if a DUNS is used or a "9" if a user assigned identifier is used.
Situational
4
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: TRN04 identifies a further subdivision within the organization.
SITUATIONAL RULE: Required when the requester needs to identify a specific component, such as a specific division or group, of the company identified in the previous data element (TRN03). If not required by this implementation guide, do not send.
INDUSTRY NAME: Trace Assigning Entity Additional Identifier

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 Identifying the Patient in Section 1.12.2 for specific information on how to identify an individual to a UMO.
FHIR Mapping:
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 subscriber is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Middle Name or Initial
Situational
6
1038
Name Prefix
O 1
AN
1/10
Prefix to individual name
FHIR Mapping: Patient.name[0].prefix[0]
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when military rank further identifies the subscriber. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Name Prefix
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
FHIR Mapping: Patient.name[0].suffix[0]
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the suffix of an individual's name is needed to further identify the subscriber; e.g., Sr., Jr., or III. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Name Suffix
Required
8
66
Identification Code Qualifier
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.
The primary identifier is the Member Identification Number in the NM1 segment.
TR3 Notes:
  1. The NM1 segment identifies the member using the Health Insurance Claim (HIC) Number or Medicaid Recipient Identification Number 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 it is different from the Member Identification Number provided in the NM1 segment.
  2. If the requester values this segment with the Patient Account Number (REF01="EJ") on the request, the UMO must return the same value in this segment on the response.
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.
Implement with version: STU 1.0.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.2.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
Use this code only if the subscriber is the patient.
The maximum number of characters to be supported for this qualifier is `20'. Characters beyond the maximum are not required to be stored nor returned by any receiving system.
F6
Health Insurance Claim (HIC) Number
Use the NM1 (Subscriber Name) segment if the subscriber's HIC number is the primary identifier for his or her coverage. Use this code only in a REF segment when the payer has a different member number, and there is also a need to pass the subscriber's HIC number. This might occur in a Medicare HMO situation.
HJ
Identity Card Number
Use this code when the Identity Card Number differs from the Member Identification Number. This is particularly prevalent in the Medicaid environment.
IG
Insurance Policy Number
N6
Plan Network Identification Number
NQ
Medicaid Recipient Identification Number
SY
Social Security Number
Use this code only if the Social Security Number was not used by the payer as its primary method of identifying the subscriber. Do not use the social security number if the information source is 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.0.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

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 subscriber/patient. If not required by this implementation guide, do not send.
TR3 Notes:
Refer to Identifying the Patient in Section 1.12.2 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 Inquiry profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
DMG✱D8✱19580322~
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
Not Used
3
1068
Gender Code
O 1
ID
1
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

HL - DEPENDENT HIERARCHICAL LEVEL

X12 Name:
Hierarchical Level
X12 Purpose:
To identify dependencies among and the content of hierarchically related groups of data segments
X12 Comments:
  1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
  2. The HL segment defines a top-down/left-right ordered structure.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
This loop is required when inquiring on the status of authorizations for a specific patient who 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.
  3. A transaction submitted in real time mode can inquire on a maximum of one patient. A transaction submitted in batch mode can contain a maximum of ninety-nine patient requests. Each patient is defined as either one subscriber loop if the member is the patient, or one subscriber loop and one dependent loop if the dependent is the patient.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim profile because the values are hardcoded or derived. 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.2.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
0
No Subordinate HL Segment in This Hierarchical Structure.
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.

TRN*1 - DEPENDENT 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 this inquiry at the patient level. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
TR3 Notes:
  1. 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.
  2. Each trace number provided in the TRN segment at this level on the inquiry 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 not defined in the PAS Claim Inquiry profile.
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
CODE
DEFINITION
1
Current Transaction Trace Numbers
Required
2
127
Reference Identification
M 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: TRN02 provides unique identification for the transaction.
INDUSTRY NAME: Dependent Trace Number
Required
3
509
Originating Company Identifier
O 1
AN
10
A unique identifier designating the company initiating the funds transfer instructions, business transaction or assigning tracking reference identification.
SEMANTIC: TRN03 identifies an organization.
INDUSTRY NAME: Trace Assigning Entity Identifier
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.

The first position must be either a "1" if an EIN is used, a "3" if a DUNS is used or a "9" if a user assigned identifier is used.
Situational
4
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: TRN04 identifies a further subdivision within the organization.
SITUATIONAL RULE: Required when the requester needs to identify a specific component, such as a specific division or group, of the company identified in the previous data element (TRN03). If not required by this implementation guide, do not send.
INDUSTRY NAME: Trace Assigning Entity Additional Identifier

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:
Claim.patient => Patient
Locate the Patient Resource in the Bundle referenced in the Claim.patient attribute. Use the Patient Resource for all of the segments of the 2010D Loop
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.2.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 used by the requester to identify the dependent to the UMO. 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 must return the same value in this segment on the response.
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.
Implement with version: STU 1.0.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:
'EI' -> '28'
'EJ' -> 'EJ'
'SB' -> 'SY'
Implement with version: STU 1.2.0
CODE
DEFINITION
28
Employee Identification 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.
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.0.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

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 dependent. If not required by this implementation guide, do not send.
TR3 Notes:
Refer to Identifying the Patient in Section 1.12.2 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 Inquiry profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
DMG✱D8✱19580322~
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
Not Used
3
1068
Gender Code
O 1
ID
1
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

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:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
This loop is required when (1) this is a global inquiry and the Patient loop (2000C or 2000D) is not valued, or when (2) the requester wants to limit the inquiry to service reviews for a specific patient event or patient event provider associated with the patient identified, or when (3) this is a patient inquiry and the Service loop (2000F) is not valued. If not required by this implementation guide, do not send.
TR3 Notes:
  1. The Patient Event level enables you to further qualify your inquiry. Use this loop to identify an existing patient event level authorization associated with this inquiry.
  2. When you use this loop on the inquiry, you limit the range of authorizations that meet the specifications entered. Use of this loop also ensures that the response from the UMO contains only those authorizations that meet the criteria you provided.
  3. This segment is required if this loop is used.
  4. A transaction submitted in real time mode can contain a maximum of one global inquiry. A transaction submitted in batch mode can contain a maximum of five global inquiries. Refer to section 1.4.1 for a description of global inquiry.
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.2.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
INDUSTRY NAME: Hierarchical Parent ID Number
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
INDUSTRY NAME: Hierarchical ID Number
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:
Situational
Segment Usage:
Situational
Segment Repeat:
2
Situational Rule:
Required when the requester needs to assign a unique trace number to track this inquiry at the Patient Event level. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
TR3 Notes:
  1. 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.
  2. Each trace number provided in the TRN segment at this level on the inquiry 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 Inquiry 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.2.0
SITUATIONAL RULE: Required when the requester needs to identify a specific component, such as a specific division or group, of the company identified in the previous data element (TRN03). If not required by this implementation guide, do not send.
INDUSTRY NAME: Trace Assigning Entity Additional Identifier

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 requester wants to identify the request category, certification type code, service type, or service location of health care service review of the inquiry. If not required by this implementation guide, do not send.
TR3 Notes:
Value this segment if you want to limit the inquiry to only referrals, or admission certifications, or health care service certifications.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim Inquiry profile.
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
CODE
DEFINITION
AR
Admission Review
Use to limit the inquiry to information on requests for admission to a facility.
HS
Health Services Review
Use to limit the inquiry to information on requests for service reviews related to an episode of care.
IN
Individual
Use to inquire on the status or existence of service reservations.
SC
Specialty Care Review
Use to limit the inquiry to information on requests for referrals.
Situational
2
1322
Certification Type Code
O 1
ID
1
Code indicating the type of certification
SITUATIONAL RULE: Required when the requester needs to limit the inquiry to service review requests that were submitted with a specific certification type code. 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 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
This code is used to request the UMO to reconsider a previously denied referral or certification.
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
SITUATIONAL RULE: Required when the requester needs to limit the inquiry to only those authorizations for the type of service specified. If not required by this implementation guide, do not send.
Use of this element assumes that the original health care services review request specified the same service type. Note that the original health care services review request might have specified a different service type or expressed the service as a specific procedure or set of procedures. Use of this element implies that only those authorizations with an exact match on this value are returned by the UMO.
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
32
Plan Waiting Period
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
AH
Skilled Nursing Care - Room and Board
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 the requester needs to limit the inquiry to only those certifications for the facility type specified. If not required by this implementation guide, do not send.
Use of this element assumes that the original health care services review request specified the same facility type. Note that the original health care services review request might have specified a different facility type or expressed the facility as part of the service type in UM03. Use of this element implies that only those certifications with an exact match on this value are returned by the UMO.
Required
4-1
1331
Facility Code Value
M 1
AN
1/2
Code identifying where services were, or may be, performed; the first and second positions of the Uniform Bill Type Code for Institutional Services or the Place of Service Codes for Professional or Dental Services.
INDUSTRY NAME: Facility Type Code
Use to indicate a facility code value from the code source referenced in UM04-2.
Required
4-2
1332
Facility Code Qualifier
O 1
ID
1/2
Code identifying the type of facility referenced
CODE
DEFINITION
A
Uniform Billing Claim Form Bill Type
CODE SOURCE: 236: Uniform Billing Claim Form Bill Type
B
Place of Service Codes for Professional or Dental Services
CODE SOURCE: 237: Place of Service Codes for Professional Claims
Not Used
4-3
1325
Claim Frequency Type Code
O 1
ID
1
Not Used
5
C024
Related Causes Information
O 1
Not Used
6
1338
Level of Service Code
O 1
ID
1/3
Not Used
7
1213
Current Health Condition Code
O 1
ID
1
Not Used
8
923
Prognosis Code
O 1
ID
1
Not Used
9
1363
Release of Information Code
O 1
ID
1
Not Used
10
1514
Delay Reason Code
O 1
ID
1/2

HCR - HEALTH CARE SERVICES REVIEW

X12 Name:
Health Care Services Review
X12 Purpose:
To specify the outcome of a health care services review
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the requester needs to limit the inquiry to only those health care service reviews on file at the UMO with a specific status. If not required by this implementation guide, do not send.
TR3 Notes:
Use of HCR01 (action code) to limit the responses to only those authorizations that match a specific action/status may omit authorizations for which the status has changed. For example, an inquiry on all health care services reviews with a pended status will not return information on a review that has moved from a pended to a final status.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim Inquiry profile.
Implement with version: STU 1.0.0
TR3 Example:
HCR✱A1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
306
Action Code
M 1
ID
1/2
Code indicating type of action
Certification Action Code
CODE
DEFINITION
51
Complete
Use this code to inquire on authorizations with a status of complete. For the UMO, the authorization is complete at the time the claim is received and recorded.
71
Term Expired
Use this code to inquire on authorizations with a status of expired. For the UMO, this is based on the effective period for which the original certification was authorized.
A1
Certified in total
A2
Certified - partial
Use this code to inquire on authorizations with a status of partially certified. Consult HCR01, Loop 2000F for approved, denied or pended services.
A3
Not Certified
Use this code to inquire on authorizations with a status of denied. Note, however, that the UMO might not retain information on health care services reviews that it has denied.
A4
Pended
A6
Modified
Use this code to inquire on authorizations with a status of certified with modifications.
C
Cancelled
Use this code to inquire on authorizations with a cancelled status. For the UMO, this is an administrative cancellation due to a change in the status of the patient and/or service provider.
CT
Contact Payer
Not Used
2
127
Reference Identification
O 1
AN
1/50
Not Used
3
1271
Industry Code
O 5
AN
1/30
Not Used
4
1073
Yes/No Condition or Response Code
O 1
ID
1

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 inquiring on a previously authorized health care service review or on authorizations associated with a previously authorized health care service review and the authorization number previously assigned by the UMO is known. If not required by this implementation guide, do not send.
TR3 Notes:
  1. This is the certification number previously assigned by the UMO to the original service review outcome associated with this inquiry. This is not the trace number assigned by the requester.
  2. If the UMO locates this certification number and it has not issued a new certification number associated with the same authorization, the UMO must return the same certification identification in HCR02 in the HCR Health Care Services Review segment of the inquiry response. If this certification number is not found or it has been superseded, the UMO must return this number in the REF segment in the corresponding loop of the response.
FHIR Mapping:
Not Used on PAS Claim Inquiry profile on FHIR Claim
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:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when inquiring on 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:
Not Used on PAS Claim Inquiry profile on FHIR Claim
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:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the requester needs to limit the inquiry to authorizations for patient events associated with a specific accident date, or when this is a global inquiry and none of the other DTP segments in this loop are valued. If not required by this implementation guide, do not send.
TR3 Notes:
A global inquiry must value at least one DTP segment in Loop 2000E if the Service Date in Loop 2000F is not valued.
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.
Implement with version: STU 1.0.0
TR3 Example:
DTP✱439✱D8✱20031206~
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*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:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the requester needs to limit the inquiry to service reviews for patient events scheduled for a specific proposed or actual patient event date or date range. If not required by this implementation guide, do not send.
TR3 Notes:
  1. If UM01 = AR use Admit Date.
  2. A global inquiry must value at least one DTP segment in Loop 2000E if the Service Date in Loop 2000F is not valued.
FHIR Mapping:
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.2.0
TR3 Example:
DTP✱AAH✱D8✱20050723~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
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 '«value of timingPeriod.start»-«value of timingPeriod.end»'
Implement with version: STU 1.2.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:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the requester needs to limit the inquiry to health care service reviews for admission to a facility for a specific proposed or actual admission date. If not required by this implementation guide, do not send.
TR3 Notes:
  1. Use in conjunction with UM01 = "AR" (admission review) to limit the inquiry to patient events associated with requests for admission to a facility.
  2. A global inquiry must value at least one DTP segment in Loop 2000E if the Service Date in Loop 2000F is not valued.
FHIR Mapping:
An Admission Date DTP segment is created when the Claim has a supportingInfo attribute for a 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'
The date format in FHIR for this element is YYYY-MM-DD and will need to be converted.
Implement with version: STU 1.2.0
TR3 Example:
DTP✱435✱D8✱20050723~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
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 AdmissionDates has an attribute named 'timingDate' set DTP02 to 'D8'
Otherwise set DTP02 to 'RD8'
Implement with version: STU 1.2.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).timingDate | Claim.supportingInfo(AdmissionDates).timingPeriod
If the supportingInfo[n] has the attribute timingDate set DTP03 to the value of timingDate
Otherwise set DTP03 to '«value of timingPeriod.start»-«value of timingPeriod.end»'
The date format in FHIR for this element is YYYY-MM-DD and will need to be converted.
Implement with version: STU 1.2.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:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the requester needs to limit the inquiry to admission reviews (UM01 = "AR") with an associated proposed or actual date of discharge. If not required by this implementation guide, do not send.
TR3 Notes:
A global inquiry must value at least one DTP segment in Loop 2000E if the Service Date in Loop 2000F is not valued.
FHIR Mapping:
An 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'
The date format in FHIR for this element is CCYY-MM-DD and will need to be converted.
Implement with version: STU 1.2.0
TR3 Example:
DTP✱096✱D8✱20050724~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
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' or 'RD8'
If the DischargeDates has an attribute named 'timingDate' set DTP02 to 'D8'
Otherwise set DTP02 to 'RD8'
Implement with version: STU 1.2.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 | Claim.supportingInfo(DischargeDates).timingPeriod
If the supportingInfo[n] has the attribute timingDate set DTP03 to the value of timingDate
Otherwise set DTP03 to '«value of timingPeriod.start»-«value of timingPeriod.end»'
The date format in FHIR for this element is YYYY-MM-DD and will need to be converted.
Implement with version: STU 1.2.0
INDUSTRY NAME: Proposed or Actual Discharge Date

DTP*102 - CERTIFICATION ISSUE DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the requester needs to limit the inquiry to those authorizations issued on a specific date or within a specific date range. If not required by this implementation guide, do not send.
TR3 Notes:
A global inquiry must value at least one DTP segment in Loop 2000E if the Service Date in Loop 2000F is not valued.
FHIR Mapping:
A DTP (Certification Issue Date) segment is created in the 2000E loop when Claim.item[0].productOrService.coding[0].code is No Value
Implement with version: STU 1.2.0
TR3 Example:
DTP✱102✱D8✱20051218~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
FHIR Mapping: '102'
Implement with version: STU 1.0.0
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
102
Issue
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
FHIR Mapping: 'D8' or 'RD8'
If the itemCertificationIssueDate has an attribute named 'valueDate' set DTP02 to 'D8'
Otherwise set DTP02 to 'RD8'
Implement with version: STU 1.2.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[0].extension(itemCertificationIssueDate).valueDate | Claim.item[0].extension(itemCertificationIssueDate).valuePeriod
If the Claim.item[0] has the attribute valueDate set DTP03 to the value of valueDate
Otherwise set DTP03 to '«value of valuePeriod.start»-«value of valuePeriod.end»'
The date format in FHIR for this element is YYYY-MM-DD and will need to be converted.
Implement with version: STU 1.2.0
INDUSTRY NAME: Certification Issue Date

DTP*036 - CERTIFICATION EXPIRATION DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the requester needs to limit the inquiry to authorizations that expire on or by a specific date or within a specific date range. If not required by this implementation guide, do not send.
TR3 Notes:
A global inquiry must value at least one DTP segment in Loop 2000E if the Service Date in Loop 2000F is not valued.
FHIR Mapping:
A DTP (Certification Expiration Date) segment is created in the 2000E loop when Claim.item[0].productOrService.coding[0].code is No Value
Implement with version: STU 1.2.0
TR3 Example:
DTP✱036✱D8✱20050731~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
FHIR Mapping: '36'
Implement with version: STU 1.0.0
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
036
Expiration
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
FHIR Mapping: 'D8' or 'RD8'
If the itemCertificationExpirationDate has an attribute named 'valueDate' set DTP02 to 'D8'
Otherwise set DTP02 to 'RD8'
Implement with version: STU 1.2.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[0].extension(itemCertificationExpirationDate).valueDate | Claim.item[0].extension(itemCertificationExpirationDate).valuePeriod
If the Claim.item[0] has the attribute valueDate set DTP03 to the value of valueDate
Otherwise set DTP03 to '«value of valuePeriod.start»-«value of valuePeriod.end»'
The date format in FHIR for this element is YYYY-MM-DD and will need to be converted.
Implement with version: STU 1.2.0
INDUSTRY NAME: Certification Expiration Date

DTP*007 - CERTIFICATION EFFECTIVE DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the requester needs to limit the inquiry to authorizations that expire on or by a specific date or within a specific date range. If not required by this implementation guide, do not send.
TR3 Notes:
A global inquiry must value at least one DTP segment in Loop 2000E if the Service Date in Loop 2000F is not valued.
FHIR Mapping:
A DTP (Certification Effective Date) segment is created in the 2000E loop when Claim.item[0].productOrService.coding[0].code is No Value
Implement with version: STU 1.2.0
TR3 Example:
DTP✱007✱RD8✱20050618-20051215~
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: '007'
Implement with version: STU 1.0.0
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
007
Effective
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
FHIR Mapping: 'D8' or 'RD8'
If the itemCertificationEffectiveDate has an attribute named 'valueDate' set DTP02 to 'D8'
Otherwise set DTP02 to 'RD8'
Implement with version: STU 1.2.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[0].extension(itemCertificationEffectiveDate).valueDate | Claim.item[0].extension(itemCertificationEffectiveDate).valuePeriod
If the Claim.item[0] has the attribute valueDate set DTP03 to the value of valueDate
Otherwise set DTP03 to '«value of valuePeriod.start»-«value of valuePeriod.end»'
The date format in FHIR for this element is YYYY-MM-DD and will need to be converted.
Implement with version: STU 1.2.0
INDUSTRY NAME: Certification Effective Date

DTP*881 - HEALTH CARE SERVICES REVIEW REQUEST 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 the requester needs to limit the inquiry to service reviews requested on a specific date or date range, or when this is a global inquiry and none of the other DTP segments in this loop are valued and the Service Date DTP in Loop 2000F is not valued. If not required by this implementation guide, do not send.
TR3 Notes:
  1. A global inquiry must value at least one DTP segment in Loop 2000E if the Service Date in Loop 2000F is not valued.
  2. The date when the requester initiated the health care services review request might not be consistent with the date when the UMO received the health care services review request. Use of this segment implies that only those certifications that match on this value are returned by the UMO.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim Inquiry profile.
Implement with version: STU 1.0.0
TR3 Example:
DTP✱881✱D8✱20051223~
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
881
Request
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
RD8
Range of Dates Expressed in Format CCYYMMDD-CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Health Care Services Review Request 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:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the requester needs to limit the inquiry to authorizations related to a specific diagnosis associated with a single episode 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 Inquiry profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
HI✱BF:41090~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
C022
Health Care Code Information
M 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (Diagnosis Code) and range of diagnosis codes were NOT given in C022-08.
Required
1-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
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
Not Used
1-3
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
1-4
1251
Date Time Period
O 1
AN
1/35
Not Used
1-5
782
Monetary Amount
O 1
R
1/18
Not Used
1-6
380
Quantity
O 1
R
1/15
Not Used
1-7
799
Version Identifier
O 1
AN
1/30
Not Used
1-8
1271
Industry Code
O 1
AN
1/30
Not Used
1-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Not Used
2
C022
Health Care Code Information
O 1
Not Used
3
C022
Health Care Code Information
O 1
Not Used
4
C022
Health Care Code Information
O 1
Not Used
5
C022
Health Care Code Information
O 1
Not Used
6
C022
Health Care Code Information
O 1
Not Used
7
C022
Health Care Code Information
O 1
Not Used
8
C022
Health Care Code Information
O 1
Not Used
9
C022
Health Care Code Information
O 1
Not Used
10
C022
Health Care Code Information
O 1
Not Used
11
C022
Health Care Code Information
O 1
Not Used
12
C022
Health Care Code Information
O 1

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 the requester needs to limit the inquiry to authorizations for patient event providers other than or in addition to the provider identified in the Loop 2010B, or limit the inquiry to authorizations for a specialty entity for this patient event. If not required by this implementation guide, do not send.
TR3 Notes:
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.
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.
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.2.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
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. Not used if identifying a specialty entity. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
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 guide, do not send.
INDUSTRY NAME: Patient Event Provider Name Prefix
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
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:
8
Situational Rule:
Required on or after the mandated implementation date for the HIPAA National Provider Identifier (NPI) when the Patient Event 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.2.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'
'UPIN' -> '1G'
'FI' -> '1J'
'EN' -> 'EI'
'G5' -> 'G5'
'N5' -> 'N5'
'N7' -> 'N7'
'SB' -> 'SY'
'ZH' -> 'ZH'
Implement with version: STU 1.2.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 must not be used for Medicare. Not used if NM108 = 34.
ZH
Carrier Assigned Reference Number
Use when the requester has not been assigned an NPI or the NPI is not mandated for use and the UMO identified in Loop 2010A has assigned its own identifier to 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(identifierJurisdiction).coding[0].code | Organization.identifier[1].extension(identifierJurisdiction).valueCodeableConcept.coding[0].code
Implement with version: STU 1.2.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 - 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 limiting the inquiry to authorizations for a patient event location and the patient event provider has multiple locations to identify the specific 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 Inquiry 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[0] | Organization.address[0].line[0]
Implement with version: STU 1.2.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[1] | Organization.address[0].line[1]
Implement with version: STU 1.2.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 limiting the inquiry to authorizations for a patient event location and the patient event provider has multiple locations to identify the specific 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 Inquiry 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 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: 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

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 inquiring on authorizations for services of a specialty entity to indicate the specialty. 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.
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
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

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 the Patient Event loop is not valued or when inquiring on authorizations for specific services or procedures. If not required, by this implementation guide, do not send.
TR3 Notes:
This segment is required if this loop is used.
FHIR Mapping:
Claim.item[n]
Each occurrence of Claim.item will have a corresponding 2000F occurrence except when the item[0].productOrService.coding[0].code is No Value (there should be only a single Claim.item in this situation and no 2000F Loop will be created)
Implement with version: STU 1.2.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
INDUSTRY NAME: Hierarchical Parent ID Number
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
INDUSTRY NAME: Hierarchical ID Number
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 track this inquiry at the Service level. If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver.
TR3 Notes:
  1. 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.
  2. Each trace number provided in the TRN segment at this level on the inquiry must be returned by the UMO in the TRN segment at the corresponding level of the response.
FHIR Mapping:
Create one TRN segment for each itemTraceNumber extension up to three (3) in the PAS Claim Inquiry.
Implement with version: STU 1.2.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.2.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.2.0
INDUSTRY NAME: Trace Assigning Entity Identifier
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.

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).valueIdentifier.extension(identifierSubDepartment).valueString
The identifierSubDepartment extension has a url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-identifierSubDepartment'
Implement with version: STU 1.2.0
SITUATIONAL RULE: Required when the requester needs to identify a specific component, such as a specific division or group, of the company identified in the previous data element (TRN03). If not required by this implementation guide, do not send.
INDUSTRY NAME: Trace Assigning Entity Additional Identifier

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 requester wants to limit the inquiry to a specific service type or procedure and the associated request category, certification type code, service type, or service location differs from the information specified in the UM segment at the Patient Event level (Loop 2000E). If not required by this implementation guide, do not send.
TR3 Notes:
Value this segment if you want to limit the inquiry to only referrals or only health care service certifications.
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.
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.2.0
CODE
DEFINITION
HS
Health Services Review
Use to limit the inquiry to information on requests for service reviews related to an episode of care.
SC
Specialty Care Review
Use to limit the inquiry to information on requests for referrals.
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.2.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 required 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
This code is used to request the UMO to reconsider a previously denied referral or certification.
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 the requester needs to limit the inquiry to authorizations for a specific service type and that service type is different from the UM03 value at the Patient Event level (Loop 2000E) and is not expressed as a specific code value in the SV1, SV2, or SV3 segment in this Service loop. If not required by this implementation guide, do not send.
  1. Use of this element assumes that the original health care services review request specified the same service type. Note that the original health care services review request might have specified a different service type or expressed the service as a specific procedure or set of procedures. Use of this element implies that only those authorizations with an exact match on this value are returned by the UMO.
  2. Values entered 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
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 the requester needs to limit the inquiry to only those authorizations for services at the facility type specified and that facility type is different from the value specified in the Patient Event loop UM04. If not required by this implementation guide, do not send.
  1. Use of this element assumes that the original health care services review request specified the same facility type. Note that the original health care services review request might have specified a different facility type or expressed the facility as part of the service type in UM03. Use of this element implies that only those authorizations with an exact match on this value are returned by the UMO.
  2. Values entered at the Service Level override the values entered at the Patient Event Level for this service.
Required
4-1
1331
Facility Code Value
M 1
AN
1/2
Code identifying where services were, or may be, performed; the first and second positions of the Uniform Bill Type Code for Institutional Services or the Place of Service Codes for Professional or Dental Services.
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[n].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.2.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

HCR - HEALTH CARE SERVICES REVIEW

X12 Name:
Health Care Services Review
X12 Purpose:
To specify the outcome of a health care services review
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the requester needs to limit the inquiry to only those authorizations for a service with a specific status such as "term expired" and that status is different from the value in HCR01 at the Patient Event Level (Loop 2000E) of this inquiry. If not required by this implementation guide, do not send.
TR3 Notes:
Use of HCR01 (action code) to limit the responses to only those authorizations that match a specific action/status may omit authorizations for which the status has changed. For example, an inquiry on all health care services reviews with a pended status will not return information on a review that has moved from a pended to a final status.
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.
Implement with version: STU 1.0.0
TR3 Example:
HCR✱A1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
306
Action Code
M 1
ID
1/2
Code indicating type of action
FHIR Mapping: Claim.item[n].extension(reviewActionCode).valueCodeableConcept.coding[0].code
The reviewActionCode extension is identified as follows:
extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-reviewActionCode'
Implement with version: STU 1.2.0
Certification Action Code
CODE
DEFINITION
51
Complete
Use this code to inquire on authorizations with a status of complete. For the UMO, the authorization is complete at the time the claim is received and recorded.
71
Term Expired
Use this code to inquire on authorizations with a status of expired. For the UMO, this is based on the effective period for which the original certification was authorized.
A1
Certified in total
A3
Not Certified
Use this code to inquire on authorizations with a status of denied. Note, however, that the UMO might not retain information on health care services reviews that it has denied.
A4
Pended
A6
Modified
Use this code to inquire on authorizations with a status of certified with modifications.
C
Cancelled
Use this code to inquire on authorizations with a cancelled status. For the UMO, this is an administrative cancellation due to a change in the status of the patient and/or service provider.
CT
Contact Payer
Not Used
2
127
Reference Identification
O 1
AN
1/50
Not Used
3
1271
Industry Code
O 5
AN
1/30
Not Used
4
1073
Yes/No Condition or Response Code
O 1
ID
1

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 inquiring on a previously authorized health care service review and the authorization number assigned by the UMO is known and different from the number specified at the Patient Event Level (Loop 2000E). If not required by this implementation guide, do not send.
TR3 Notes:
  1. 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.
  2. If the UMO locates this certification number and it has not issued a new certification number associated with the same authorization, the UMO must return the same certification identification in HCR02 in the HCR Health Care Services Review segment of the inquiry response. If this certification number is not found or it has been superseded, the UMO must return this number in the REF segment in the corresponding loop of the response.
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.
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.2.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 inquiring on a previous health care services review request for which the UMO has returned a response that contained an administrative reference number at the Service level for this service (Loop 2000F REF segment where REF01 = NT) and did not return a certification number in HCR02. If not required by this implementation guide, do not send.
TR3 Notes:
This is the administrative number assigned by the UMO to the original service review outcome. This is not the trace number assigned by the requester.
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.
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.2.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 limiting the inquiry to those authorizations for service for a specific service date or service date range. 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.
Implement with version: STU 1.0.0
TR3 Example:
DTP✱472✱D8✱20050713~
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 Claim.item[n] has the attribute servicedDate set DTP03 to the value of servicedDate
Otherwise set DTP03 to '«value of servicedPeriod.start»-«value of servicedPeriod.end»'
Implement with version: STU 1.2.0
INDUSTRY NAME: Proposed or Actual Service Date

DTP*102 - CERTIFICATION ISSUE DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when limiting the inquiry to authorizations for a service issued on a specific date or within a specific date range that is different from the certification date(s) specified in the Patient Event level (Loop 2000E) of this inquiry. 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.
Implement with version: STU 1.0.0
TR3 Example:
DTP✱102✱D8✱20051218~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
FHIR Mapping: '102'
Implement with version: STU 1.0.0
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
102
Issue
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
FHIR Mapping: 'D8' or 'RD8'
If the itemCertificationIssueDate has an attribute named 'valueDate' set DTP02 to 'D8'
Otherwise set DTP02 to 'RD8'
Implement with version: STU 1.2.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[0].extension(itemCertificationIssueDate).valueDate | Claim.item[0].extension(itemCertificationIssueDate).valuePeriod
If the Claim.item[0] has the attribute valueDate set DTP03 to the value of valueDate
Otherwise set DTP03 to '«value of valuePeriod.start»-«value of valuePeriod.end»'
The date format in FHIR for this element is YYYY-MM-DD and will need to be converted.
Implement with version: STU 1.2.0
INDUSTRY NAME: Certification Issue Date

DTP*036 - CERTIFICATION EXPIRATION DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when limiting the inquiry to authorizations for a service that expire on or by a specific date or within a specific date range and the date(s) differ from the certification expiration date(s) specified at the Patient Event level (Loop 2000E) of this inquiry. 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.
Implement with version: STU 1.0.0
TR3 Example:
DTP✱036✱D8✱20050731~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
FHIR Mapping: '036'
Implement with version: STU 1.0.0
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
036
Expiration
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
FHIR Mapping: 'D8' or 'RD8'
If the itemCertificationExpirationDate extension has an attribute named 'valueDate' set DTP02 to 'D8'
Otherwise set DTP02 to 'RD8'
Implement with version: STU 1.2.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[0].extension(itemCertificationExpirationDate).valueDate | Claim.item[0].extension(itemCertificationExpirationDate).valuePeriod
If the Claim.item[0] has the attribute valueDate set DTP03 to the value of valueDate
Otherwise set DTP03 to '«value of valuePeriod.start»-«value of valuePeriod.end»'
The date format in FHIR for this element is YYYY-MM-DD and will need to be converted.
Implement with version: STU 1.2.0
INDUSTRY NAME: Certification Expiration Date

DTP*007 - CERTIFICATION EFFECTIVE DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when limiting the inquiry to those certifications that are effective for a specific date or date range and the effective date(s) differ from the effective date(s) specified at the Patient Event level (Loop 2000E) of this inquiry. 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.
Implement with version: STU 1.0.0
TR3 Example:
DTP✱007✱RD8✱20050618-20051215~
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: '007'
Implement with version: STU 1.0.0
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
007
Effective
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
FHIR Mapping: 'D8' or 'RD8'
If the itemCertificationEffectiveDate has an attribute named 'valueDate' set DTP02 to 'D8'
Otherwise set DTP02 to 'RD8'
Implement with version: STU 1.2.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[0].extension(itemCertificationEffectiveDate).valueDate | Claim.item[0].extension(itemCertificationEffectiveDate).valuePeriod
If the Claim.item[0] has the attribute valueDate set DTP03 to the value of valueDate
Otherwise set DTP03 to '«value of valuePeriod.start»-«value of valuePeriod.end»'
The date format in FHIR for this element is YYYY-MM-DD and will need to be converted.
Implement with version: STU 1.2.0
INDUSTRY NAME: Certification Effective Date

SV1 - PROFESSIONAL SERVICE

X12 Name:
Professional Service
X12 Purpose:
To specify the service line item detail for a health care professional
X12 Syntax:
P0304
If either SV103 or SV104 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when inquiring on authorizations for a specific professional service. If not required by this implementation guide, do not send.
TR3 Notes:
If the Service level is present on the inquiry, it must specify a service type in UM03 or a service or procedure code in SV1, SV2, or SV3.
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.2.0
TR3 Example:
SV1✱HC:99211:25✱✱UN✱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)
FHIR Mapping: The value of Claim.item[n].productOrService.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.2.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 inquiring on 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
At the time of this writing, this code set has been approved by the Secretary of HHS as a pilot project allowed under the HIPAA law. The qualifier can only be used in transactions covered under HIPAA by parties registered in the pilot project and their trading partners,
OR
If a new rule names the ABC codes as an allowable code set under HIPAA,
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].productOrService.coding[0].code
Implement with version: STU 1.2.0
INDUSTRY NAME: Procedure Code
Not Used
1-3
1339
Procedure Modifier
O 1
AN
2
Not Used
1-4
1339
Procedure Modifier
O 1
AN
2
Not Used
1-5
1339
Procedure Modifier
O 1
AN
2
Not Used
1-6
1339
Procedure Modifier
O 1
AN
2
Not Used
1-7
352
Description
O 1
AN
1/80
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.2.0
SITUATIONAL RULE: Required when limiting the inquiry to authorizations for a specific range of procedures as specified on the original request for authorization. If not required by this implementation guide, do not send.
INDUSTRY NAME: Product or Service ID
Use SV101-2 to represent the beginning value in a procedure range and this data element to represent the ending value in a range of codes.
Not Used
2
782
Monetary Amount
O 1
R
1/18
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 limiting the inquiry to authorizations for a specific number of service units for the service specified. 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 limiting the inquiry to authorizations for a specific number of service units for the service specified. 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
Not Used
7
C004
Composite Diagnosis Code Pointer
O 1
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
Not Used
11
1073
Yes/No Condition or Response Code
O 1
ID
1
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
Not Used
20
1337
Level of Care Code
O 1
ID
1
Not Used
21
1360
Provider Agreement Code
O 1
ID
1

SV2 - INSTITUTIONAL SERVICE

X12 Name:
Institutional Service
X12 Purpose:
To specify the service line item detail for a health care institution
X12 Syntax:
  1. R0102
    At least one of SV201 or SV202 is required.
  2. P0405
    If either SV204 or SV205 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when inquiring on authorizations for a specific Institutional Service or a specific Revenue Code for the Institutional Service. If not required by this implementation guide, do not send.
TR3 Notes:
If the Service level is present on the inquiry, it must specify a service type in UM03 or a service or procedure code in SV1, SV2, or SV3.
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 = 'institutional' then populate the SV2 segment otherwise do not populate the elements.
Implement with version: STU 1.2.0
TR3 Example:
  1. SV2✱300✱HC:80019✱✱UN✱1~
  2. SV2✱120✱✱✱DA✱5~
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 inquiring on authorizations for a specific 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 inquiring on authorizations 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: The value of Claim.item[n].productOrService.coding.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.2.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 inquiring on 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
Use for inpatient services only.
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
At the time of this writing, this code set has been approved by the Secretary of HHS as a pilot project allowed under the HIPAA law. The qualifier can only be used in transactions covered under HIPAA by parties registered in the pilot project and their trading partners,
OR
If a new rule names the ABC codes as an allowable code set under HIPAA,
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].productOrService.coding[0].code
Implement with version: STU 1.2.0
INDUSTRY NAME: Procedure Code
Not Used
2-3
1339
Procedure Modifier
O 1
AN
2
Not Used
2-4
1339
Procedure Modifier
O 1
AN
2
Not Used
2-5
1339
Procedure Modifier
O 1
AN
2
Not Used
2-6
1339
Procedure Modifier
O 1
AN
2
Not Used
2-7
352
Description
O 1
AN
1/80
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.2.0
SITUATIONAL RULE: Required when limiting the inquiry to authorizations for a specific range of procedures as specified on the original request for authorization. If not required by this implementation guide, do not send.
INDUSTRY NAME: Product or Service ID
Use SV202-2 to represent the beginning value in the procedure range and this data element to represent the ending value in a range of codes.
Not Used
3
782
Monetary Amount
O 1
R
1/18
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 limiting the inquiry to authorizations for a specific number of service units for the service specified. 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 limiting the inquiry to authorizations for a specific number of service units for the service specified. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Unit Count
Not Used
6
1371
Unit Rate
O 1
R
1/10
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
Not Used
9
1345
Nursing Home Residential Status Code
O 1
ID
1
Not Used
10
1337
Level of Care Code
O 1
ID
1

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 inquiring on authorizations for a specific Dental Service. If not required by this implementation guide, do not send.
TR3 Notes:
If the Service level is present on the inquiry, it must specify a service type in UM03 or a service or procedure code in SV1, SV2, or SV3.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim Inquiry profile.
Implement with version: STU 1.0.0
TR3 Example:
SV3✱AD:D2150✱✱✱✱✱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
Not Used
1-3
1339
Procedure Modifier
O 1
AN
2
Not Used
1-4
1339
Procedure Modifier
O 1
AN
2
Not Used
1-5
1339
Procedure Modifier
O 1
AN
2
Not Used
1-6
1339
Procedure Modifier
O 1
AN
2
Not Used
1-7
352
Description
O 1
AN
1/80
Situational
1-8
234
Product/Service ID
O 1
AN
1/48
Identifying number for a product or service
SITUATIONAL RULE: Required when limiting the inquiry to authorizations for a specific range of dental procedures as specified on the original request for authorization. If not required by this implementation guide, do not send.
INDUSTRY NAME: Product or Service ID
Use SV301-2 to represent the beginning value in the procedure range and this data element to represent the ending value in a range of codes.
Not Used
2
782
Monetary Amount
O 1
R
1/18
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 limiting the inquiry to authorizations for treatment of an area of the oral cavity. If not required by this implementation guide, do not send.
  1. Do not use this element for inquiring on authorizations for individual teeth. Use the Tooth Information (TOO) segment in this loop to inquire on individual teeth.
  2. The oral cavity area codes are contained in the ISO TC 106 Designation System for Teeth and Areas of the Oral Cavity.
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
Not Used
4-2
1361
Oral Cavity Designation Code
O 1
ID
1/3
Not Used
4-3
1361
Oral Cavity Designation Code
O 1
ID
1/3
Not Used
4-4
1361
Oral Cavity Designation Code
O 1
ID
1/3
Not Used
4-5
1361
Oral Cavity Designation Code
O 1
ID
1/3
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 limiting the inquiry to authorizations for prosthesis, crown, or inlay with the status indicated. If not required by this implementation guide, do not send.
INDUSTRY NAME: Prosthesis, Crown, or Inlay Code
CODE
DEFINITION
I
Initial Placement
R
Replacement
Situational
6
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: SV306 is the number of procedures.
SITUATIONAL RULE: Required when limiting the inquiry to authorizations for a specific number of service units for the procedure specified.
INDUSTRY NAME: Service Unit Count
Number of procedures.
Not Used
7
352
Description
O 1
AN
1/80
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:
1
Situational Rule:
Required when inquiring on authorizations for a specific tooth number and/or tooth surface related to this procedure line. 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 Inquiry 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
See Appendix A for 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 limiting the inquiry to a 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
Not Used
3-2
1369
Tooth Surface Code
O 1
ID
1/2
Not Used
3-3
1369
Tooth Surface Code
O 1
ID
1/2
Not Used
3-4
1369
Tooth Surface Code
O 1
ID
1/2
Not Used
3-5
1369
Tooth Surface Code
O 1
ID
1/2

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 inquiring on authorizations for a specific service provider, specialist, or specialty entity for this service that is different from the provider, specialist, or specialty entity identified in Loop 2010E (Patient Event Provider Name). If not required by this implementation guide, do not send.
TR3 Notes:
This segment is required if Loop 2010F is used.
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
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. Not used if identifying a specialty entity. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Provider Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
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 guide, do not send.
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 the suffix is needed to further identify the provider; e.g. Sr., Jr., or III. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Provider Name Suffix
Situational
8
66
Identification Code Qualifier
O 1
ID
1/2
Code designating the system/method of code structure used for Identification Code (67)
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 Service 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 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.2.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'
'UPIN' -> '1G'
'FI' -> '1J'
'EN' -> 'EI'
'G5' -> 'G5'
'N5' -> 'N5'
'N7' -> 'N7'
'SB' -> 'SY'
'ZH' -> 'ZH'
Implement with version: STU 1.2.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.
G5
Provider Site Number
N5
Provider Plan Network Identification Number
N7
Facility Network Identification Number
SY
Social Security Number
The social security number must not be used for 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(identifierJurisdiction).valueCodeableConcept.coding[0].code | Organization.identifier[1].extension(identifierJurisdiction).valueCodeableConcept.coding[0].code
Implement with version: STU 1.2.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 limiting the inquiry to authorizations for services at a specific provider location and the service provider has multiple locations. 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.
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[0] | Organization.address[0].line[0]
Implement with version: STU 1.2.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[1] | Organization.address[0].line[1]
Implement with version: STU 1.2.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 limiting the inquiry to authorizations for services at a specific provider location and the service provider has multiple locations. 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.
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

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 limiting the inquiry to authorizations for the services of a specialty entity to indicate the specialty. 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.
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
The qualifier code used in this qualifier element is mapped from the qualifier codes used in NM101.
Implement with version: STU 1.2.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
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 Inquiry 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 Response Transaction Set Listing

Usage
Repeats

ISA - INTERCHANGE CONTROL HEADER

X12 Name:
Interchange Control Header
X12 Purpose:
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
  1. All positions within each of the data elements must be filled.
  2. For compliant implementations under this implementation guide, ISA13, the interchange Control Number, must be a positive unsigned number. Therefore, the ISA segment can be considered a fixed record length segment.
  3. The first element separator defines the element separator to be used through the entire interchange.
  4. The ISA segment terminator defines the segment terminator used throughout the entire interchange.
  5. Spaces in the example interchanges are represented by "." for clarity.
TR3 Example:
ISA✱00✱..........✱01✱SECRET....✱ZZ✱SUBMITTERS.ID..✱ZZ✱RECEIVERS.ID...✱030101✱1253✱^✱00501✱000000905✱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
005010X215
Health Care Services Review - 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:
This segment indicates the start of a health care services review inquiry response transaction set with all the supporting detail information. This transaction set is the electronic equivalent of a phone, fax, or paper-based utilization management inquiry response.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim Inquiry Response profile.
Implement with version: STU 1.0.0
TR3 Example:
ST✱278✱0001✱005010X215~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
143
Transaction Set Identifier Code
M 1
ID
3
Code uniquely identifying a Transaction Set
SEMANTIC: The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
CODE
DEFINITION
278
Health Care Services Review Information
Required
2
329
Transaction Set Control Number
M 1
AN
4/9
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
The Transaction Set Control Numbers in ST02 and SE02 must be identical. The number is assigned by the originator and must be unique within a functional group (GS-GE). For example, start with the number 0001 and increment from there. The number also aids in error resolution research. Use the corresponding value in SE02 for this transaction set.
Required
3
1705
Implementation Convention Reference
O 1
AN
1/35
Reference assigned to identify Implementation Convention
SEMANTIC: The implementation convention reference (ST03) is used by the translation routines of the interchange partners to select the appropriate implementation convention to match the transaction set definition. When used, this implementation convention reference takes precedence over the implementation reference specified in the GS08.
  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
005010X215
Health Care Services Review - 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 Inquiry Response profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
BHT✱0007✱49✱199800114000001✱20050101✱1400✱18~
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: This data element is not defined in the PAS Claim Inquiry Response profile.
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: This data element is not defined in the PAS Claim Inquiry Response profile.
Implement with version: STU 1.0.0
CODE
DEFINITION
49
Original - No Response Necessary
Use when responding to an inquiry for authorizations associated with a specific patient.
52
Response to Historical Inquiry
Use when responding to a global inquiry for the status of authorizations associated with multiple patients.
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.2.0
INDUSTRY NAME: Submitter Transaction Identifier
If the transaction is processed in real time, return the transaction identifier entered in BHT03 on the 278 inquiry.
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 and ClaimResponse.created
Combine with BHT05 to create a datetime and populate both fields with the same value
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 and ClaimResponse.created
Combine with BHT04 to create a datetime and populate both fields with the same value
Implement with version: STU 1.0.0
INDUSTRY NAME: Transaction Set Creation Time
Required
6
640
Transaction Type Code
O 1
ID
2
Code specifying the type of transaction
FHIR Mapping: ClaimResponse.outcome
The value from BHT06 is translated as follows:
'18' -> 'complete'
'RD' -> 'complete'
'RS' -> 'partial'
'ZW' -> 'partial'
Recognize the concept may not easily fit when mapping between BHT06 and outcome
Implement with version: STU 1.0.0
CODE
DEFINITION
18
Response - No Further Updates to Follow
Use when this is the final response to the inquiry and the response indicates that (1) the inquiry was rejected or (2) no authorizations were found.
RD
Returns Detail
Use to indicate that the response contains detail information on each authorization found.
RS
Response - Additional Response(s) Available
Use when more records are available on the UMO's system than the system can return in this response. If the response contains a BHT06 = RS, the requester should specify additional inquiry search criteria to narrow the search criteria. The requester can limit a patient inquiry to a single patient event where the request provides qualifying criteria about the patient event, or, if supported by the UMO system, the requester can request to limit the response to summary information by assigning a BHT06 value of ZW on the inquiry.
ZW
Sort and Segregate Detail
Use to indicate that the response contains summary information on the authorizations found.

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. The information source corresponds to the payer, HMO, or other utilization management organization that is the source of the health care services review decision/response.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim Inquiry Response profile.
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.
Not Used
2
734
Hierarchical Parent ID Number
O 1
AN
1/12
Required
3
735
Hierarchical Level Code
M 1
ID
1/2
Code defining the characteristic of a level in a hierarchical structure
COMMENT: HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
CODE
DEFINITION
20
Information Source
Required
4
736
Hierarchical Child Code
O 1
ID
1
Code indicating if there are hierarchical child data segments subordinate to the level being described
COMMENT: HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
CODE
DEFINITION
0
No Subordinate HL Segment in This Hierarchical Structure.
Use this value only if the response contains a AAA segment at this level or in Loop 2010A indicating that the UMO was unable to accept this inquiry due to system failure or invalid application data at this level.
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.

AAA - REQUEST VALIDATION

X12 Name:
Request Validation
X12 Purpose:
To specify the validity of the request and indicate follow-up action authorized
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
9
Situational Rule:
Required when the request cannot be processed at a system or application level based on the trading partner information contained in the Functional Group Header (GS); or when the entity responsible for forwarding the inquiry to the information source (identified in Loop 2010A) is unable to process the transaction at the current time. 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 Response profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
AAA✱Y✱✱42✱Y~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: AAA01 designates whether the request is valid or invalid. Code "Y" indicates that the code is valid; code "N" indicates that the code is invalid.
FHIR Mapping: ClaimResponse.error[n].extension(errorElement)
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.2.0
INDUSTRY NAME: Yes No Condition or Response Code
CODE
DEFINITION
N
No
Use this code to indicate that the inquiry or an element in the inquiry is not valid. The transaction has been rejected as identified by the code in AAA03.
Y
Yes
Use this code to indicate that the inquiry is valid, however the transaction has been rejected as identified by the code in AAA03.
Not Used
2
559
Agency Qualifier Code
O 1
ID
2
Required
3
901
Reject Reason Code
O 1
ID
2
Code assigned by issuer to identify reason for rejection
FHIR Mapping: ClaimResponse.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.0
CODE
DEFINITION
04
Authorized Quantity Exceeded
Use this code to indicate that the functional group exceeds the maximum number of transactions as specified by agreement between the application sender GS02 and application receiver GS03.
41
Authorization/Access Restrictions
Use this code to indicate that the application sender (GS02) and application receiver (GS03) do not have a trading partner agreement for the transaction sets identified in GS01 or transaction sets with the purpose identified in BHT02. The 278 transaction set has three different implementations. The transaction set purpose, as identified in BHT02, specifies the implementation.
42
Unable to Respond at Current Time
Use this code to indicate that the entity responsible for forwarding the inquiry request to the information source (Loop 2010A) is unable to process the transaction at the current time. This indicates a problem in the system forwarding the inquiry request and not in the information source's (UMO) system.
79
Invalid Participant Identification
Use this code to indicate that the identifier used in GS02 or GS03 is invalid or unknown.
Required
4
889
Follow-up Action Code
O 1
ID
1
Code identifying follow-up actions allowed
FHIR Mapping: ClaimResponse.error[n].extension(errorFollowupAction)
The errorFollowupAction 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.2.0
CODE
DEFINITION
C
Please Correct and Resubmit
N
Resubmission Not Allowed
P
Please Resubmit Original Transaction
Y
Do Not Resubmit; We Will Hold Your Request and Respond Again Shortly

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 response to a inquiry transaction, the information source would normally be the payer or utilization review organization that stores the decision regarding the original health care service review request.
FHIR Mapping:
Organization.type
Populate the CodeableConcept components of the type as follows:
type.coding[0].system = 'https://codesystem.x12.org/005010/98'
type.coding[0].code = value of NM101
Implement with version: STU 1.2.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
Populate the components of the type (datatype CodeableConcept) as follows:
type.coding[0].system = 'https://codesystem.x12.org/005010/98'
type.coding[0].code = 'XX'
Implement with version: STU 1.2.0
CODE
DEFINITION
1P
Provider
2B
Third-Party Administrator
36
Employer
PR
Payer
X3
Utilization Management Organization
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
FHIR Mapping: This data element is not defined in the PAS Claim Inquiry Response profile.
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 the responder needs to identify the UMO by name. 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 Inquiry Response profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when NM103 is valued and the responding 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 Inquiry Response 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 Inquiry Response profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when NM104 is valued and the suffix of the individual's name is known; e.g. Sr., Jr., or III. If not required by this implementation guide, do not send.
INDUSTRY NAME: Utilization Management Organization (UMO) Name Suffix
Required
8
66
Identification Code Qualifier
O 1
ID
1/2
Code designating the system/method of code structure used for Identification Code (67)
FHIR Mapping: 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:
'46' -> '46'
'PI' -> 'U'
Implement with version: STU 1.2.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 until the National PlanID is mandated if the UMO is a payer.
XV
Centers for Medicare and Medicaid Services PlanID
CODE SOURCE: 540: Centers for Medicare and Medicaid Services PlanID
XX
Centers for Medicare and Medicaid Services National Provider Identifier
Required for providers in the United States or its territories on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider is eligible to receive an NPI;
OR
Required for providers not in the United States or its territories on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider has received an NPI;
OR
Required for providers prior to the mandated NPI implementation date when the provider has received an NPI and the submitter has the capability to send it;
If not required by this implementation guide, do not send.
CODE SOURCE: 537: Centers for Medicare & Medicaid Services National Provider Identifier
Required
9
67
Identification Code
O 1
AN
2/80
Code identifying a party or other code
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

PER*IC - UTILIZATION MANAGEMENT ORGANIZATION (UMO) 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 requester must direct requests for follow-up to a specific UMO contact, email, facsimile, or telephone. If not required by this implementation guide, do not send.
TR3 Notes:
  1. Use this segment to identify a contact name and/or communication number for the UMO.
  2. When the communication number represents a telephone number in the United States and other countries using the North American Dialing Plan (for voice, data, fax, etc.), the communication number should always include the area code and phone number using the format AAABBBCCCC. 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 immedidately after the telephone number.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim Inquiry Response profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
PER✱IC✱ORCUTT✱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: This data element is not defined in the PAS Claim Inquiry Response profile.
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.name
Populate the 'text' attribute of the name
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when a particular contact is assigned and the name of the contact differs from the entity named in the NM1 segment in this loop (2010A NM1 Segment). If not required by this implementation guide, do not send.
INDUSTRY NAME: Utilization Management Organization (UMO) Contact Name
Required
3
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
FHIR Mapping: 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.0
SEGMENT SYNTAX: P0304
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.
Required
4
364
Communication Number
O 1
AN
1/256
Complete communications number including country or area code when applicable
FHIR Mapping: Organization.contact.telecom[0].value
Implement with version: STU 1.0.0
SEGMENT SYNTAX: P0304
INDUSTRY NAME: Utilization Management Organization (UMO) Contact Communication Number
Situational
5
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
FHIR Mapping: 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.0
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
CODE
DEFINITION
EM
Electronic Mail
EX
Telephone Extension
When used, the value following this code is the extension for the preceding communications contact number.
FX
Facsimile
TE
Telephone
UR
Uniform Resource Locator (URL)
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.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. «value-of-PER06»' to telecom[0].value
See ITU-T E.123 for format of telephone values
Implement with version: STU 1.2.0
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
INDUSTRY NAME: Utilization Management Organization (UMO) Contact Communication Number
Situational
7
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
FHIR Mapping: 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.0
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
CODE
DEFINITION
EM
Electronic Mail
EX
Telephone Extension
When used, the value following this code is the extension for the preceding communications contact number.
FX
Facsimile
TE
Telephone
UR
Uniform Resource Locator (URL)
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.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. «value-of-PER06»' to telecom[1].value
See ITU-T E.123 for format of telephone values
Implement with version: STU 1.2.0
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
INDUSTRY NAME: Utilization Management Organization (UMO) Contact Communication Number
Not Used
9
443
Contact Inquiry Reference
O 1
AN
1/20

AAA - UTILIZATION MANAGEMENT ORGANIZATION (UMO) REQUEST VALIDATION

X12 Name:
Request Validation
X12 Purpose:
To specify the validity of the request and indicate follow-up action authorized
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
9
Situational Rule:
Required when the request cannot be processed at the system or application level based on the Utilization Management Organization (information source) identified in Loop 2010A. 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 Response profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
AAA✱N✱✱42✱Y~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: AAA01 designates whether the request is valid or invalid. Code "Y" indicates that the code is valid; code "N" indicates that the code is invalid.
FHIR Mapping: ClaimResponse.error[n].extension(errorElement)
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 = '2010A'
Implement with version: STU 1.2.0
INDUSTRY NAME: Yes No Condition or Response Code
CODE
DEFINITION
N
No
Y
Yes
Not Used
2
559
Agency Qualifier Code
O 1
ID
2
Required
3
901
Reject Reason Code
O 1
ID
2
Code assigned by issuer to identify reason for rejection
FHIR Mapping: ClaimResponse.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.0
CODE
DEFINITION
04
Authorized Quantity Exceeded
Use this code to indicate that the transaction exceeds the maximum number of patient events for this information source (UMO).
42
Unable to Respond at Current Time
Use this code to indicate that the information source (UMO) identified in Loop 2010A is unable to process the transaction at the current time. This indicates that the UMO's system is not available.
79
Invalid Participant Identification
Use this code to indicate that the code used in Loop 2010A to identify the information source (UMO) is invalid.
80
No Response received - Transaction Terminated
Use this code to indicate that the trading partner/application system responsible for sending the request to the information source (UMO) has not received a response in the expected timeframe and therefore has terminated the request.
T4
Payer Name or Identifier Missing
Use this code to indicate that either the name or identifier for the information source (UMO) identified in Loop 2010A is missing.
ZZ
Mutually Defined
Use to indicate that the UMO system does not support the response type specified in BHT06 of the inquiry or cannot process this inquiry in real-time.
Situational
4
889
Follow-up Action Code
O 1
ID
1
Code identifying follow-up actions allowed
FHIR Mapping: ClaimResponse.error[n].extension(errorFollowupAction)
The errorFollowupAction 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.2.0
SITUATIONAL RULE: Required if AAA03 is present. If not required by this implementation guide, do not send.
CODE
DEFINITION
N
Resubmission Not Allowed
P
Please Resubmit Original Transaction
Y
Do Not Resubmit; We Will Hold Your Request and Respond Again Shortly

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:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when the UMO system processed any of the information contained in Loop 2000B of the inquiry transaction. If not required by this implementation guide, do not send.
TR3 Notes:
  1. If the UMO system was unable to process any data beyond Loop 2000A, Loop 2000B is not used.
  2. This segment indicates the health care services review information receiver. For responses to inquiry transactions, this segment corresponds to the identification of the provider who initiated the inquiry.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim Inquiry Response profile.
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.
Required
2
734
Hierarchical Parent ID Number
O 1
AN
1/12
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
COMMENT: HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Required
3
735
Hierarchical Level Code
M 1
ID
1/2
Code defining the characteristic of a level in a hierarchical structure
COMMENT: HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
CODE
DEFINITION
21
Information Receiver
Required
4
736
Hierarchical Child Code
O 1
ID
1
Code indicating if there are hierarchical child data segments subordinate to the level being described
COMMENT: HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
CODE
DEFINITION
0
No Subordinate HL Segment in This Hierarchical Structure.
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 loop identifies the receiver of information.
FHIR Mapping:
ClaimResponse.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.0
TR3 Example:
NM1✱1P✱1✱WHITE✱CHRIS✱✱✱✱46✱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
Populate the CodeableConcept components of the type as follows:
type.coding[0].system = 'https://codesystem.x12.org/005010/98'
type.coding[0].code = value of NM101
Implement with version: STU 1.2.0
CODE
DEFINITION
1P
Provider
2A
Federal, State, County or City Facility
2B
Third-Party Administrator
36
Employer
FA
Facility
PR
Payer
X3
Utilization Management Organization
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
FHIR Mapping: This data element is not defined in the PAS Claim Inquiry Response profile.
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 used by the UMO to identify the requester. If not required by this implementation guide, do not send.
INDUSTRY NAME: Requester Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
FHIR Mapping: This data element is not defined in the PAS Claim Inquiry Response profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when name information is used by the UMO to identify the requester and the requester is a person. 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 Inquiry Response 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 Inquiry Response profile.
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when NM104 is valued and the suffix of the individual's name is known; e.g. Sr., Jr., or III. If not required by this implementation guide, do not send.
INDUSTRY NAME: Requester Name Suffix
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
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.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 until the National PlanID is mandated if the requester is a payer.
XV
Centers for Medicare and Medicaid Services PlanID
CODE SOURCE: 540: Centers for Medicare and Medicaid Services PlanID
XX
Centers for Medicare and Medicaid Services National Provider Identifier
Required for providers on or after the mandated HIPAA National Provider Identifier (NPI) implementation date when the provider has an NPI and it is available to the submitter;
OR
Required for providers before the mandated HIPAA NPI implementation date when the provider has an NPI and the submitter has the capability to send it.
If not required by this implementation guide, do not send.
CODE SOURCE: 537: Centers for Medicare & Medicaid Services National Provider Identifier
Required
9
67
Identification Code
O 1
AN
2/80
Code identifying a party or other code
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:
9
Situational Rule:
Required prior to the mandated NPI implementation date when the requester is a Health Care Provider and an NPI is reported in NM109 of this loop and an additional identification number is required by the UMO to identify the Health Care Provider.
OR
Required when the requester is not a Health Care Provider and an NPI is reported in NM109 of this loop and an additional identification number is required by the UMO to identify the requester.
OR
Required prior to the mandated NPI implementation date when an identifier other than an NPI is reported in NM109 of this loop and an additional identification number is required by the UMO to identify the requester. 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 Inquiry Response 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
Use to identify the physician, clinic, or group practice associated with the requester identified in this NM1 loop.
N5
Provider Plan Network Identification Number
N7
Facility Network Identification Number
SY
Social Security Number
The social security number must not be used for Medicare. Not used if NM108 = 34.
ZH
Carrier Assigned Reference Number
Use for the requester/provider ID as assigned by the UMO identified in Loop 2000A.
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Requester Supplemental Identifier
Not Used
3
352
Description
O 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

AAA - REQUESTER REQUEST VALIDATION

X12 Name:
Request Validation
X12 Purpose:
To specify the validity of the request and indicate follow-up action authorized
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
9
Situational Rule:
Required when the inquiry is not valid or no authorizations on file match the inquiry criteria specified at this level. If not required by this implementation guide, do not send.
TR3 Notes:
Use this segment to convey rejection information regarding the entity that initiated the inquiry transaction.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim Inquiry Response profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
AAA✱N✱✱46✱C~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: AAA01 designates whether the request is valid or invalid. Code "Y" indicates that the code is valid; code "N" indicates that the code is invalid.
FHIR Mapping: ClaimResponse.error[n].extension(errorElement)
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 = '2010B'
Implement with version: STU 1.2.0
INDUSTRY NAME: Valid Request Indicator
CODE
DEFINITION
N
No
Y
Yes
Not Used
2
559
Agency Qualifier Code
O 1
ID
2
Required
3
901
Reject Reason Code
O 1
ID
2
Code assigned by issuer to identify reason for rejection
FHIR Mapping: ClaimResponse.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.0
CODE
DEFINITION
15
Required application data missing
Use for missing contact information (PER Segment) other than phone number.
35
Out of Network
41
Authorization/Access Restrictions
Use if the provider is not authorized for inquiries.
43
Invalid/Missing Provider Identification
44
Invalid/Missing Provider Name
45
Invalid/Missing Provider Specialty
46
Invalid/Missing Provider Phone Number
47
Invalid/Missing Provider State
49
Provider is Not Primary Care Physician
51
Provider Not on File
79
Invalid Participant Identification
Use for invalid/missing requester supplemental identifier.
97
Invalid or Missing Provider Address
IP
Inappropriate Provider Role
Required
4
889
Follow-up Action Code
O 1
ID
1
Code identifying follow-up actions allowed
FHIR Mapping: ClaimResponse.error[n].extension(errorFollowupAction)
The errorFollowupAction 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.2.0
CODE
DEFINITION
C
Please Correct and Resubmit
N
Resubmission Not Allowed
R
Resubmission Allowed

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 used by the UMO to identify the requester. 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 Inquiry Response 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 used by the UMO to further identify the requester. 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 used by the UMO to further identify the requester. If not required by this implementation guide, do not send.
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

HL - SUBSCRIBER LEVEL

X12 Name:
Hierarchical Level
X12 Purpose:
To identify dependencies among and the content of hierarchically related groups of data segments
X12 Comments:
  1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
  2. The HL segment defines a top-down/left-right ordered structure.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when this is a response to a patient inquiry and the UMO system processed any of the information contained in Loop 2000C of the inquiry, or when this is a response to a global inquiry and authorizations were found in the UMO system that match the inquiry search criteria. If not required by this implementation guide, do not send.
TR3 Notes:
  1. If the UMO system processed any of the information contained in Loop 2000C of the request, the UMO system must return a response or error response containing this HL. If the UMO system was unable to process any data beyond Loop 2000B of the request, then Loop 2000C is not required.
  2. This segment corresponds to the identification of the subscriber or individual insured member.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim Inquiry Response profile.
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.
Required
2
734
Hierarchical Parent ID Number
O 1
AN
1/12
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
COMMENT: HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Required
3
735
Hierarchical Level Code
M 1
ID
1/2
Code defining the characteristic of a level in a hierarchical structure
COMMENT: HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
CODE
DEFINITION
22
Subscriber
Required
4
736
Hierarchical Child Code
O 1
ID
1
Code indicating if there are hierarchical child data segments subordinate to the level being described
COMMENT: HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
CODE
DEFINITION
0
No Subordinate HL Segment in This Hierarchical Structure.
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.

TRN - SUBSCRIBER TRACE NUMBER

X12 Name:
Trace
X12 Purpose:
To uniquely identify a transaction to an application
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
3
Situational Rule:
Required when this loop is returned and the inquiry contained a tracking number at this level or when the UMO or clearinghouse assigns a trace number at the Patient level in the response for tracking purposes. If not required by this implementation guide, do not send.
TR3 Notes:
  1. Any trace numbers provided at this level on the inquiry must be returned by the UMO at this level of the 278 inquiry response.
  2. If the 278 inquiry transaction passes through more than one clearinghouse, the second (and subsequent) clearinghouse may choose one of the following options:

    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 inquiry response to the sending clearinghouse, they must remove their TRN segment and replace it with the sending clearinghouse's TRN segment.

    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 inquiry response transaction.
  3. If the 278 inquiry passes through a clearinghouse that adds their own TRN in addition to a requester TRN, the clearinghouse will receive an inquiry 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.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim Inquiry Response profile.
Implement with version: STU 1.1.0
TR3 Example:
TRN✱2✱111099✱9012345678✱RADIOLOGY~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
481
Trace Type Code
M 1
ID
1/2
Code identifying which transaction is being referenced
CODE
DEFINITION
1
Current Transaction Trace Numbers
The term "Current Transaction Trace Number" refers to the trace number assigned by the creator of the 278 inquiry response transaction (the UMO).
2
Referenced Transaction Trace Numbers
The term "Referenced Transaction Trace Number" refers to the trace number originally sent in the 278 inquiry transaction.
Required
2
127
Reference Identification
M 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: TRN02 provides unique identification for the transaction.
INDUSTRY NAME: Subscriber Trace Number
Required
3
509
Originating Company Identifier
O 1
AN
10
A unique identifier designating the company initiating the funds transfer instructions, business transaction or assigning tracking reference identification.
SEMANTIC: TRN03 identifies an organization.
INDUSTRY NAME: Trace Assigning Entity Identifier
  1. Use this element to identify the organization that assigned this trace number. If TRN01 is "2", this is the value received in the original 278 inquiry request transaction. If TRN01 is "1", use this information to identify the UMO Organization that assigned this trace number.
  2. The first position must be either a "1" if an EIN is used, a "3" if a DUNS is used or a "9" if a user assigned identifier is used.
Situational
4
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: TRN04 identifies a further subdivision within the organization.
SITUATIONAL RULE: Required when TRN01 = 2 and TRN04 was valued on the inquiry or when TRN01 = 1 and the sender needs to identify a specific division or group of the company identified in the previous data element (TRN03). If not required by this implementation guide, do not send.
INDUSTRY NAME: Trace Assigning Entity Additional Identifier

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:
This segment identifies the subscriber.
FHIR Mapping:
ClaimResponse.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.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: This data element is not defined in the PAS Claim Inquiry Response profile.
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: This data element is not defined in the PAS Claim Inquiry Response profile.
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 valued on the request, or when the subscriber is the patient and this is a response to a historical inquiry (inquiry BHT02 = 51) that returns information on authorizations found. 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.2.0
SITUATIONAL RULE: Required when NM103 is valued and the first name of the subscriber is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
FHIR Mapping: Patient.name[0].given[1]
Implement with version: STU 1.2.0
SITUATIONAL RULE: Required when NM104 is valued and the middle name of the subscriber is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Middle Name or Initial
Situational
6
1038
Name Prefix
O 1
AN
1/10
Prefix to individual name
FHIR Mapping: Patient.name[0].prefix[0]
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when NM103 is valued and military rank is needed to further identify the subscriber. If not required by this implementation guide, do not send.
INDUSTRY NAME: Subscriber Name Prefix
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
FHIR Mapping: Patient.name[0].suffix[0]
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when NM104 is valued and the name suffix is needed to identify the subscriber. If not required by this implementation guide, may be provided at the sender's discretion to identify the suffix of the individual's name; e.g., Sr., Jr., or III, but cannot be required by the receiver.
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: Patient.identifier[0].type
Populate the CodeableConcept components of the type as follows:
type.coding[0].system = 'http://terminology.hl7.org/CodeSystem/v2-0203'
type.coding[0].code = 'MB'
Implement with version: STU 1.2.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, 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 a supplementary identifier is used by the UMO to identify the Subscriber or when REF01 = "EJ" (Patient Account Number) is valued on the inquiry. If not required by this implementation guide, do not send.
TR3 Notes:
Health Insurance Claim (HIC) Number or Medicaid Recipient Identification Number is provided in the NM1 segment as a Member Identification Number when it is the primary number by which the UMO knows the member (such as for Medicare or Medicaid). Do not use this segment for the Health Insurance Claim (HIC) Number or Medicaid Recipient Identification Number unless it is different from the Member Identification Number provided in the NM1 segment.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim Inquiry Response profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.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
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' -> 'SS'
Implement with version: STU 1.2.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
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 must 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.0.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 MAILING 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 used by the UMO to determine the appropriate location or network for 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 Response 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.2.0
INDUSTRY NAME: Subscriber Address Line
Use this element for the first line of the Subscriber address.
Situational
2
166
Address Information
O 1
AN
1/55
Address information
FHIR Mapping: Patient.address[0].line[1]
Implement with version: STU 1.2.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 used by the UMO to determine the appropriate location or network for 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 Response 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 Inquiry Response 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

AAA - SUBSCRIBER REQUEST VALIDATION

X12 Name:
Request Validation
X12 Purpose:
To specify the validity of the request and indicate follow-up action authorized
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
9
Situational Rule:
Required when the inquiry is not valid or no authorizations on file match the inquiry criteria specified at this level. 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 Response profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
AAA✱N✱✱67✱C~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: AAA01 designates whether the request is valid or invalid. Code "Y" indicates that the code is valid; code "N" indicates that the code is invalid.
FHIR Mapping: ClaimResponse.error[n].extension(errorElement)
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 = '2010C'
Implement with version: STU 1.2.0
INDUSTRY NAME: Valid Request Indicator
CODE
DEFINITION
N
No
Use to indicate that the inquiry is not valid due to missing or invalid application data at this level of the inquiry.
Y
Yes
Use to indicate that no authorizations on file match the inquiry criteria specified at this level of the inquiry.
Not Used
2
559
Agency Qualifier Code
O 1
ID
2
Required
3
901
Reject Reason Code
O 1
ID
2
Code assigned by issuer to identify reason for rejection
FHIR Mapping: ClaimResponse.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.0
CODE
DEFINITION
58
Invalid/Missing Date-of-Birth
64
Invalid/Missing Patient ID
65
Invalid/Missing Patient Name
67
Patient Not Found
68
Duplicate Patient ID Number
71
Patient Birth Date Does Not Match That for the Patient on the Database
72
Invalid/Missing Subscriber/Insured ID
73
Invalid/Missing Subscriber/Insured Name
75
Subscriber/Insured Not Found
76
Duplicate Subscriber/Insured ID Number
77
Subscriber Found, Patient Not Found
78
Subscriber/Insured Not in Group/Plan Identified
79
Invalid Participant Identification
Use for invalid subscriber supplemental identifier.
95
Patient Not Eligible
Required
4
889
Follow-up Action Code
O 1
ID
1
Code identifying follow-up actions allowed
FHIR Mapping: ClaimResponse.error[n].extension(errorFollowupAction)
The errorFollowupAction 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.2.0
CODE
DEFINITION
C
Please Correct and Resubmit
N
Resubmission Not Allowed

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 used by the UMO to identify the subscriber/patient. 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 Response profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
DMG✱D8✱19580322~
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: This data element is not defined in the PAS Claim Inquiry Response profile.
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
Not Used
3
1068
Gender Code
O 1
ID
1
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

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 this is a response to a patient inquiry and the UMO system processed any of the information contained in Loop 2000D of the inquiry, or when this is a response to a global inquiry and any authorizations that match the inquiry search criteria were found where the patients are dependents and do not have a unique member ID. If not required by this implementation guide, do not send.
TR3 Notes:
Required segments in this loop are required only when this loop is used. If the UMO system was unable to process any data beyond Loop 2000C of the request, Loop 2000D is not required.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim Inquiry Response profile.
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.
Required
2
734
Hierarchical Parent ID Number
O 1
AN
1/12
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
COMMENT: HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Required
3
735
Hierarchical Level Code
M 1
ID
1/2
Code defining the characteristic of a level in a hierarchical structure
COMMENT: HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
CODE
DEFINITION
23
Dependent
Required
4
736
Hierarchical Child Code
O 1
ID
1
Code indicating if there are hierarchical child data segments subordinate to the level being described
COMMENT: HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
CODE
DEFINITION
0
No Subordinate HL Segment in This Hierarchical Structure.
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.

TRN - DEPENDENT TRACE NUMBER

X12 Name:
Trace
X12 Purpose:
To uniquely identify a transaction to an application
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
3
Situational Rule:
Required when this loop is returned and the inquiry contained a tracking number at this level or when the UMO or clearinghouse assigns a trace number at the Patient level in the response for tracking purposes. If not required by this implementation guide, do not send.
TR3 Notes:
  1. Any trace numbers provided at this level on the inquiry must be returned by the UMO at this level of the 278 inquiry response.
  2. If the 278 inquiry transaction passes through more than one clearinghouse, the second (and subsequent) clearinghouse may choose one of the following options:

    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 inquiry response to the sending clearinghouse, they must remove their TRN segment and replace it with the sending clearinghouse's TRN segment.

    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 inquiry response transaction.
  3. If the 278 inquiry passes through a clearinghouse that adds their own TRN in addition to a requester TRN, the clearinghouse will receive an inquiry 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.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim Inquiry Response profile.
Implement with version: STU 1.0.0
TR3 Example:
TRN✱2✱111099✱9012345678✱RADIOLOGY~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
481
Trace Type Code
M 1
ID
1/2
Code identifying which transaction is being referenced
CODE
DEFINITION
1
Current Transaction Trace Numbers
The term "Current Transaction Trace Number" refers to the trace number assigned by the creator of the 278 inquiry response transaction (the UMO).
2
Referenced Transaction Trace Numbers
The term "Referenced Transaction Trace Number" refers to the trace number originally sent in the 278 inquiry transaction.
Required
2
127
Reference Identification
M 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: TRN02 provides unique identification for the transaction.
INDUSTRY NAME: Dependent Trace Number
Required
3
509
Originating Company Identifier
O 1
AN
10
A unique identifier designating the company initiating the funds transfer instructions, business transaction or assigning tracking reference identification.
SEMANTIC: TRN03 identifies an organization.
INDUSTRY NAME: Trace Assigning Entity Identifier
  1. Use this element to identify the organization that assigned this trace number. If TRN01 is "2", this is the value received in the original 278 inquiry request transaction. If TRN01 is "1", use this information to identify the UMO Organization that assigned this trace number.
  2. The first position must be either a "1" if an EIN is used, a "3" if a DUNS is used or a "9" if a user assigned identifier is used.
Situational
4
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: TRN04 identifies a further subdivision within the organization.
SITUATIONAL RULE: Required when TRN01 = 2 and TRN04 was valued on the inquiry or when TRN01 = 1 and the sender needs to identify a specific division or group of the company identified in the previous data element (TRN03). If not required by this implementation guide, do not send.
INDUSTRY NAME: Trace Assigning Entity Additional Identifier

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. NM108 and NM109 are situational on the response but Not Used on the inquiry. This enables the UMO to return a unique member ID for the dependent that was not known to the requester. Normally, if the dependent has a unique member ID, Loop 2000D is not used.
FHIR Mapping:
ClaimResponse.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.2.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: This data element is not defined in the PAS Claim Inquiry Response profile.
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: This data element is not defined in the PAS Claim Inquiry Response profile.
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 valued on the request, or when this is a response to a historical inquiry (inquiry BHT02 = 51) that returns information on authorizations found. 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.2.0
SITUATIONAL RULE: Required when NM103 is valued and the first name of the patient is known. 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.2.0
SITUATIONAL RULE: Required when NM104 is valued and the middle name of the patient 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 NM104 is valued and the name suffix is needed to identify the patient. If not required by this implementation guide, may be provided at the sender's discretion to identify the suffix of the individual's name; e.g., Sr., Jr., or III, but cannot be required by the receiver.
INDUSTRY NAME: Dependent 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: Patient.identifier[0].type
Populate the CodeableConcept components of the type as follows:
type.coding[0].system = 'http://terminology.hl7.org/CodeSystem/v2-0203'
type.coding[0].code = 'MB'
Implement with version: STU 1.2.0
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when the dependent has a unique member ID assigned by the UMO that was not known or provided by the requester. If not required by this implementation guide, do not send.
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, 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.
Situational
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
SITUATIONAL RULE: Required when the dependent has a unique member ID assigned by the UMO that was not known or provided by the requester. If not required by this implementation guide, do not send.
INDUSTRY NAME: Dependent Primary Identifier
Dependent 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 - 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 a supplementary identifier is used by the UMO to identify the Dependent or when REF01 = "EJ" (Patient Account Number) is valued on the inquiry. 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 Response profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.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
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:
'28' -> 'EI'
'EJ' -> 'EJ'
'SY' -> 'SB'
Implement with version: STU 1.1.0
CODE
DEFINITION
28
Employee Identification Number
EJ
Patient Account Number
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[1].value
Implement with version: STU 1.0.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 used by the UMO to determine the appropriate location or network for 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 Response 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.2.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.2.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 used by the UMO to determine the appropriate location or network for 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 Response 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 Inquiry Response 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

AAA - DEPENDENT REQUEST VALIDATION

X12 Name:
Request Validation
X12 Purpose:
To specify the validity of the request and indicate follow-up action authorized
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
9
Situational Rule:
Required when the inquiry is not valid or no authorizations on file match the inquiry criteria specified at this level. 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 Response profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
AAA✱N✱✱67✱N~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: AAA01 designates whether the request is valid or invalid. Code "Y" indicates that the code is valid; code "N" indicates that the code is invalid.
FHIR Mapping: ClaimResponse.error[n].extension(errorElement)
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.2.0
INDUSTRY NAME: Valid Request Indicator
CODE
DEFINITION
N
No
Use to indicate that the inquiry is not valid due to missing or invalid application data at this level of the inquiry.
Y
Yes
Use to indicate that no authorizations on file match the inquiry criteria specified at this level of the inquiry.
Not Used
2
559
Agency Qualifier Code
O 1
ID
2
Required
3
901
Reject Reason Code
O 1
ID
2
Code assigned by issuer to identify reason for rejection
FHIR Mapping: ClaimResponse.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.0
CODE
DEFINITION
58
Invalid/Missing Date-of-Birth
64
Invalid/Missing Patient ID
65
Invalid/Missing Patient Name
67
Patient Not Found
68
Duplicate Patient ID Number
71
Patient Birth Date Does Not Match That for the Patient on the Database
77
Subscriber Found, Patient Not Found
95
Patient Not Eligible
Required
4
889
Follow-up Action Code
O 1
ID
1
Code identifying follow-up actions allowed
FHIR Mapping: ClaimResponse.error[n].extension(errorFollowupAction)
The errorFollowupAction 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.2.0
CODE
DEFINITION
C
Please Correct and Resubmit
N
Resubmission Not Allowed

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 used by the UMO to identify the patient. 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 Response profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
DMG✱D8✱19580322~
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: This data element is not defined in the PAS Claim Inquiry Response profile.
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
Not Used
3
1068
Gender Code
O 1
ID
1
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

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:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when the UMO system processed any of the information contained in Loop 2000E of the inquiry, or when the response returns patient event authorization information. If not required by this implementation guide, do not send.
TR3 Notes:
  1. If the UMO was unable to process any data beyond Loop 2000C or Loop 2000D of the inquiry this loop and any subordinate loops are not required.
  2. This loop is required if certifications are found that match the criteria specified in the inquiry.
  3. Use this segment to identify the patient event(s) and to convey the review outcome related to the patient event(s).
  4. Use multiple occurrences of this loop if more than one patient event certification exists for this patient.
  5. 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 Inquiry Response profile.
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.
Required
2
734
Hierarchical Parent ID Number
O 1
AN
1/12
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
COMMENT: HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Required
3
735
Hierarchical Level Code
M 1
ID
1/2
Code defining the characteristic of a level in a hierarchical structure
COMMENT: HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
CODE
DEFINITION
EV
Event
Required
4
736
Hierarchical Child Code
O 1
ID
1
Code indicating if there are hierarchical child data segments subordinate to the level being described
COMMENT: HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
CODE
DEFINITION
0
No Subordinate HL Segment in This Hierarchical Structure.
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.

TRN - PATIENT EVENT TRACKING NUMBER

X12 Name:
Trace
X12 Purpose:
To uniquely identify a transaction to an application
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
3
Situational Rule:
Required when this loop is returned and the inquiry contained a tracking number at this level, or if the UMO or clearinghouse assigns a trace number to this patient event in the response for tracking purposes. If not required by this implementation guide, do not send.
TR3 Notes:
  1. Any trace numbers provided at this level on the inquiry must be returned by the UMO at this level of the 278 inquiry response.
  2. If the 278 inquiry transaction passes through more than one clearinghouse, the second (and subsequent) clearinghouse may choose one of the following options:

    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.

    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 response transaction.
  3. If the 278 inquiry 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.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim Inquiry Response 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: This data element is not defined in the PAS Claim Inquiry Response profile.
Implement with version: STU 1.0.0
CODE
DEFINITION
1
Current Transaction Trace Numbers
The term "Current Transaction Trace Number" refers to the trace number assigned by the creator of the 278 response transaction (the UMO).
2
Referenced Transaction Trace Numbers
The term "Referenced Transaction Trace Number" refers to the trace number originally sent in the 278 request transaction.
Required
2
127
Reference Identification
M 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: TRN02 provides unique identification for the transaction.
FHIR Mapping: ClaimResponse.identifier[0].value
Implement with version: STU 1.1.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: ClaimResponse.identifier[0].system
Implement with version: STU 1.1.0
INDUSTRY NAME: Trace Assigning Entity Identifier
  1. Use this element to identify the organization that assigned this trace number. If TRN01 is "2", this is the value received in the original 278 request transaction. If TRN01 is "1", use this information to identify the UMO Organization that assigned this trace number.
  2. The first position must be either a "1" if an EIN is used, a "3" if a DUNS is used or a "9" if a user assigned identifier is used.
Situational
4
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: TRN04 identifies a further subdivision within the organization.
FHIR Mapping: ClaimResponse.identifier[0].assigner.reference
Implement with version: STU 1.2.0
SITUATIONAL RULE: Required when TRN01 = 2 and TRN04 was valued on the inquiry or when TRN01 = 1 and the UMO needs to identify a specific component, such as a specific division or group, of the company identified in the previous data element (TRN03). If not required by this implementation guide, do not send.
INDUSTRY NAME: Trace Assigning Entity Additional Identifier

AAA - PATIENT EVENT REQUEST VALIDATION

X12 Name:
Request Validation
X12 Purpose:
To specify the validity of the request and indicate follow-up action authorized
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
9
Situational Rule:
Required when the inquiry is not valid at this level to indicate the data condition that prohibits processing of the inquiry, or when the UMO has no authorizations on file that match the inquiry criteria specified at the Patient Event level of the inquiry. If not required by this implementation guide, do not send.
TR3 Notes:
Use this AAA segment to identify the reasons why the inquiry could not be processed based on the data at this level of the inquiry.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim Inquiry Response profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
AAA✱N✱✱15✱C~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: AAA01 designates whether the request is valid or invalid. Code "Y" indicates that the code is valid; code "N" indicates that the code is invalid.
FHIR Mapping: ClaimResponse.error[n].extension(errorElement)
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 = '2000E'
Implement with version: STU 1.2.0
INDUSTRY NAME: Valid Request Indicator
CODE
DEFINITION
N
No
Use to indicate that the inquiry is not valid due to missing or invalid application data at this level of the inquiry.
Y
Yes
Use to indicate that no authorizations on file match the inquiry criteria specified at this level of the inquiry.
Not Used
2
559
Agency Qualifier Code
O 1
ID
2
Required
3
901
Reject Reason Code
O 1
ID
2
Code assigned by issuer to identify reason for rejection
FHIR Mapping: ClaimResponse.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.0
CODE
DEFINITION
15
Required application data missing
Use when data are missing that are not covered by another Reject Reason Code. For example, use for missing place of service or missing service type codes.
33
Input Errors
Use for input errors in the patient event data not covered by the other reject reason codes listed. For example, use for invalid place of service codes and invalid service type.
52
Service Dates Not Within Provider Plan Enrollment
Use for Event Date(s).
57
Invalid/Missing Date(s) of Service
Use for invalid/missing event date.
60
Date of Birth Follows Date(s) of Service
Use for Date(s) of Event.
61
Date of Death Precedes Date(s) of Service
Use for Date(s) of Event.
62
Date of Service Not Within Allowable Inquiry Period
Use for Date of Event.
AA
Authorization Number Not Found
AF
Invalid/Missing Diagnosis Code(s)
AI
Invalid/Missing Accident Date
AM
Invalid/Missing Admission Date
AN
Invalid/Missing Discharge Date
CI
Certification Information Does Not Match Patient
NC
No Certification Information Found
T5
Certification Information Missing
Use to indicate missing previous certification number information.
Required
4
889
Follow-up Action Code
O 1
ID
1
Code identifying follow-up actions allowed
FHIR Mapping: ClaimResponse.error[n].extension(errorFollowupAction)
The errorFollowupAction 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.2.0
CODE
DEFINITION
C
Please Correct and Resubmit
N
Resubmission Not Allowed

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 response returns information on health care service reviews on file to identify the request category, service type, or service location associated with the health care service 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 Inquiry Response profile.
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
CODE
DEFINITION
AR
Admission Review
Use for admission to a facility.
HS
Health Services Review
Use for review of services related to an episode of care.
IN
Individual
Use for status or existence of service reservations.
SC
Specialty Care Review
Use for a referral to a specialty provider.
Situational
2
1322
Certification Type Code
O 1
ID
1
Code indicating the type of certification
SITUATIONAL RULE: Required when returning status information on authorization requests found and this information is retained by the UMO to indicate the certification type code on the original request. 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
Indicates that this is an extension to a prior approved service.
5
Notification
I
Initial
N
Reconsideration
R
Renewal
Use to indicate a renewal of an existing authorization.
S
Revised
Use to indicate a revision to the specifics of an authorization for which services have not been rendered.
Situational
3
1365
Service Type Code
O 1
ID
1/2
Code identifying the classification of service
SITUATIONAL RULE: Required when the response returns status information on health care service reviews on file that specifiy a service type. If not required by this implementation guide, do not send.
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
AH
Skilled Nursing Care - Room and Board
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 the response returns status information on health care service reviews on file that specifiy a service location or facility type for this patient event. If not required by this implementation guide, do not send.
Values returned at the Service Level for this data element override values at the Patient Event Level 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.
INDUSTRY NAME: Facility Type Code
Use to indicate a facility code value from the code source referenced in UM04-2.
Required
4-2
1332
Facility Code Qualifier
O 1
ID
1/2
Code identifying the type of facility referenced
CODE
DEFINITION
A
Uniform Billing Claim Form Bill Type
CODE SOURCE: 236: Uniform Billing Claim Form Bill Type
B
Place of Service Codes for Professional or Dental Services
CODE SOURCE: 237: Place of Service Codes for Professional Claims
Not Used
4-3
1325
Claim Frequency Type Code
O 1
ID
1
Not Used
5
C024
Related Causes Information
O 1
Not Used
6
1338
Level of Service Code
O 1
ID
1/3
Not Used
7
1213
Current Health Condition Code
O 1
ID
1
Not Used
8
923
Prognosis Code
O 1
ID
1
Not Used
9
1363
Release of Information Code
O 1
ID
1
Not Used
10
1514
Delay Reason Code
O 1
ID
1/2

HCR - HEALTH CARE SERVICES REVIEW

X12 Name:
Health Care Services Review
X12 Purpose:
To specify the outcome of a health care services review
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when returning authorization information that matches the inquiry and the UMO has reviewed the original request at this level, to indicate the status of the review. If not required by this implementation guide, do not send.
TR3 Notes:
  1. If the UMO was unable to locate authorizations due to missing or invalid application data at this level of the inquiry, the UMO must return a 278 response containing a AAA segment at this level.
  2. If Loop 2000E is present in the response, either the AAA segment or the HCR segment must be returned in loop 2000E.
  3. If the response contains Service level information (Loop 2000F) where the HCR segment is valued, the HCR values at the Service level override the HCR values at the Patient Event level for that service only.
FHIR Mapping:
ClaimResponse.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 populated 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-reviewAction'
adjudication[0].category.coding[0].system = 'http://terminology.hl7.org/CodeSystem/adjudication'
adjudication[0].category.coding[0].value = 'submitted'
Implement with version: STU 1.2.0
TR3 Example:
HCR✱A1✱20050713~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
306
Action Code
M 1
ID
1/2
Code indicating type of action
FHIR Mapping: «reviewAction».extension(reviewActionCode)
The reviewActionCode extension is a CodeableConcept and populated as follows:
extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-reviewActionCode'
extension[n].valueCodeableConcept.coding[0].system = 'https://codesystem.x12.org/005010/306'
extension[n].valueCodeableConcept.coding[0].code = value of HCR01
Implement with version: STU 1.2.0
Certification Action Code
CODE
DEFINITION
51
Complete
Use this code to identify authorizations with a status of complete. For the UMO, the authorization is complete at the time the claim is received and recorded.
71
Term Expired
Use this code to identify authorizations with a status of expired. For the UMO, this is based on the effective period for which the original certification was authorized.
A1
Certified in total
A2
Certified - partial
Use to identify that the event is only partially certified. Consult HCR01 in Loop 2000F for approved, denied or pended services.
A3
Not Certified
A4
Pended
A6
Modified
C
Cancelled
CT
Contact Payer
NA
No Action Required
Use this code to identify health care service reviews on file for which an authorization decision was not necessary.
Situational
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: HCR02 is the number assigned by the information source to this review outcome.
FHIR Mapping: ClaimResponse.preAuthRef
AND
«reviewAction».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.2.0
SITUATIONAL RULE: Required when the UMO system has assigned a review identification number to the health care service review reported in this Patient Event loop. If not required by this implementation guide, do not send.
INDUSTRY NAME: Review Identification Number
Situational
3
1271
Industry Code
O 5
AN
1/30
Code indicating a code from a specific industry code list
SEMANTIC: HCR03 is the code assigned by the information source to identify the reason for the health care service review outcome indicated in HCR01.See Code Source 886
FHIR Mapping: «reviewAction».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.2.0
SITUATIONAL RULE: Required when HCR01=A3 or A4. If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver.
INDUSTRY NAME: Review Decision Reason Code
This data element is a repeating data element and can be repeated the maximum number allowed by the standard in this implementation guide.
Situational
4
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: HCR04 is the second surgical opinion indicator. A "Y" value indicates a second surgical opinion is required; an "N" value indicates a second surgical opinion is not required for this request.
FHIR Mapping: «reviewAction».extension(secondSurgicalOpinionFlag)
The number extension is 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.2.0
SITUATIONAL RULE: Required when certification pertains to a surgical procedure and the contract under which the patient is covered has provisions regarding a second surgical opinion. If not required by this implementation guide, do not send.
INDUSTRY NAME: Second Surgical Opinion Indicator
CODE
DEFINITION
N
No
Y
Yes

REF*BB - PREVIOUS REVIEW AUTHORIZATION NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when valued on the inquiry and the UMO does not have certification information on file that matches this previously assigned authorization number or when the authorization number submitted on the inquiry has been superseded. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
TR3 Notes:
If the requester valued this segment on the inquiry and the UMO has certification information on file that matches the previous certification number, the UMO must return that certification identification in HCR02 in the HCR Health Care Services Review segment of the inquiry response.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim Inquiry Response 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: This data element is not defined in the PAS Claim Inquiry Response profile.
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: ClaimResponse.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.2.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 valued on the inquiry and the UMO does not have certification information on file that matches this previously assigned administrative reference number. If not required by this implementation, may be provided at the sender's discretion but cannot be required by the receiver.
TR3 Notes:
If the requester valued this segment on the inquiry and the UMO has health care service review outcome information on file that matches the previous review administrative reference number, the UMO must return that outcome information in the HCR Health Care Service Review segment of the inquiry response. If the event was authorized, the UMO system must return the authorization number in HCR02.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim Inquiry Response profile, see the FHIR Mapping instructions for each data element below.
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
FHIR Mapping: This data element is not defined in the PAS Claim Response profile.
Implement with version: STU 1.2.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: ClaimResponse.item[n].extension(administrationReferenceNumber)
Used for each iteration of 2000F where REF (Previous Administrative Reference 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.2.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*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:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the UMO authorized the patient event for a specific date or date range. 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 Response profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
DTP✱AAH✱D8✱20050723~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
FHIR Mapping: This data element is not defined in the PAS Claim Inquiry Response profile.
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: See note on DTP03
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: ClaimResponse.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.2.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:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the UMO authorized admission for a specific date or date range. 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 Inquiry Response profile.
Implement with version: STU 1.0.0
TR3 Example:
DTP✱435✱D8✱20050723~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
435
Admission
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
RD8
Range of Dates Expressed in Format CCYYMMDD-CCYYMMDD
Use this for the range of dates when admission can occur. Use the HSD segment for length of stay.
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Proposed or Actual Admission Date

DTP*096 - DISCHARGE DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the UMO authorized services or admission based on the proposed or actual discharge date. 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 Inquiry Response profile.
Implement with version: STU 1.0.0
TR3 Example:
DTP✱096✱D8✱20050724~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
096
Discharge
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Proposed or Actual Discharge Date

DTP*102 - CERTIFICATION ISSUE DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the UMO assigned a certification issue date to this authorization. If not required by this implementation guide, do not send.
TR3 Notes:
This is not the effective date of the authorization. This is the date when the UMO issued the authorization.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim Inquiry Response profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
DTP✱102✱D8✱20051218~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
FHIR Mapping: This data element is not defined in the PAS Claim Inquiry Response profile.
Implement with version: STU 1.0.0
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
102
Issue
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
FHIR Mapping: This data element is not defined in the PAS Claim Inquiry Response profile.
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: ClaimResponse.item[n].extension(itemPreAuthIssueDate)
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.2.0
INDUSTRY NAME: Certification Issue Date

DTP*036 - CERTIFICATION EXPIRATION DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the authorization has an expiration date to indicate the date on which the authorization expired or will expire. 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 Response profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
DTP✱036✱D8✱20050731~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
FHIR Mapping: This data element is not defined in the PAS Claim Inquiry Response profile.
Implement with version: STU 1.0.0
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
036
Expiration
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
FHIR Mapping: This data element is not defined in the PAS Claim Inquiry Response profile.
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: ClaimResponse.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.2.0
INDUSTRY NAME: Certification Expiration Date

DTP*007 - CERTIFICATION EFFECTIVE DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the authorization is limited by effective dates to indicate the date or date range when the certification is effective. 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 Response profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
DTP✱007✱RD8✱20050618-20051215~
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: This data element is not defined in the PAS Claim Inquiry Response profile.
Implement with version: STU 1.0.0
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
007
Effective
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
FHIR Mapping: This data element is not defined in the PAS Claim Inquiry Response profile.
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: ClaimResponse.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.2.0
INDUSTRY NAME: Certification Effective Date

DTP*881 - HEALTH CARE SERVICES REVIEW REQUEST 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 the UMO limits the search by request date or request date range, or when valued on the inquiry and used by the UMO to locate authorizations. If not required by this implementation guide, do not send.
FHIR Mapping:
Not Used on PAS Claim Inquiry Response profile on FHIR ClaimResponse
Implement with version: STU 1.0.0
TR3 Example:
DTP✱881✱D8✱20051223~
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
881
Request
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
RD8
Range of Dates Expressed in Format CCYYMMDD-CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Health Care Services Review Request 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:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when valued on the inquiry and used by the UMO to search for authorizations. If not required by this implementation guide, do not send.
TR3 Notes:
Only one diagnosis code is supported on the inquiry. Therefore, only one occurrence of the C022 composite is supported in this HI segment.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim Inquiry Response profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
HI✱BF:41090~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
C022
Health Care Code Information
M 1
To send health care codes and their associated dates, amounts and quantities
X12 COMPOSITE SYNTAX NOTES:
  1. P0304
    If either C02203 or C02204 is present, then the other is required.
  2. E0809
    Only one of C02208 or C02209 may be present.
X12 COMPOSITE SEMANTIC NOTES:
  1. C022-01 qualifies C022-02, C022-04, C022-05, C022-06 and C022-08.
  2. If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
  3. C022-03 is the date format that will appear in C022-04.
  4. C022-07 qualifies C022-01.
  5. C022-08 represents the ending value in a range of codes.
  6. C022-09 is used to identify the diagnosis onset as it relates to the diagnosis reported in C022-02. A "Y" indicates that the onset occurred prior to admission to the hospital; an "N" indicates that the onset did NOT occur prior to admission to the hospital; a "U" indicates that it is unknown whether the onset occurred prior to admission to the hospital or not.
X12 COMPOSITE COMMENTS: C022-09 would only need to be reported to data collectors requiring this information when C022-01 is "BF" (Diagnosis Code) and range of diagnosis codes were NOT given in C022-08.
Required
1-1
1270
Code List Qualifier Code
M 1
ID
1/3
Code identifying a specific industry code list
FHIR Mapping: see 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.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)
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: ClaimResponse.item[n].extension(communicatedDiagnosis)
The communicatedDiagnosis extension is a CodeableConcept and is 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: the communicatedDiagnosis does not indicate if the returned diagnosis code is for admitting, patient reason for visit or any other modifier for the diagnosis code.
Implement with version: STU 1.2.0
INDUSTRY NAME: Diagnosis Code
Not Used
1-3
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
1-4
1251
Date Time Period
O 1
AN
1/35
Not Used
1-5
782
Monetary Amount
O 1
R
1/18
Not Used
1-6
380
Quantity
O 1
R
1/15
Not Used
1-7
799
Version Identifier
O 1
AN
1/30
Not Used
1-8
1271
Industry Code
O 1
AN
1/30
Not Used
1-9
1073
Yes/No Condition or Response Code
O 1
ID
1
Not Used
2
C022
Health Care Code Information
O 1
Not Used
3
C022
Health Care Code Information
O 1
Not Used
4
C022
Health Care Code Information
O 1
Not Used
5
C022
Health Care Code Information
O 1
Not Used
6
C022
Health Care Code Information
O 1
Not Used
7
C022
Health Care Code Information
O 1
Not Used
8
C022
Health Care Code Information
O 1
Not Used
9
C022
Health Care Code Information
O 1
Not Used
10
C022
Health Care Code Information
O 1
Not Used
11
C022
Health Care Code Information
O 1
Not Used
12
C022
Health Care Code Information
O 1

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 the UMO authorized services that have a specific pattern of delivery for the patient event. If not required by this implementation guide, do not send.
TR3 Notes:
  1. Report authorized delivery patterns for specific services in the Service Level (Loop 2000F).
  2. An explanation of the uses of this segment follows.

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

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

    An alternate way to use HSD is to employ HSD07 and/or HSD08. A data string of HSD*VS*1*****SX*D~ means "1 visit on Wednesday and Thursday morning".
FHIR Mapping:
«authorizedItemDetail».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 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 = «ServiceRequest id in Bundle»
Set the ServiceRequest.subject to the value of ClaimResponse.patient
Note: Although 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.2.0
TR3 Example:
HSD✱VS✱1✱DA✱1✱7✱10~ (This indicates "1 visit every (per) 1 day (daily)for 10 days".)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: ServiceRequest.quantityQuantity.unit
Implement with version: STU 1.0.0
SEGMENT SYNTAX: P0102
SITUATIONAL RULE: Required when the pattern of delivery has a quanity of services authorized. 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: ServiceRequest.quantityQuantity.value
Implement with version: STU 1.0.0
SEGMENT SYNTAX: P0102
SITUATIONAL RULE: Required when the pattern of delivery has a quanity of services authorized. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Unit Count
Service Quantity
Situational
3
355
Unit or Basis for Measurement Code
O 1
ID
2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
FHIR Mapping: ServiceRequest.occurrenceTiming.repeat.periodUnit
Translate the HSD03 value as follows:
'DA' -> 'd'
'WK' -> 'wk'
'MO' -> 'mo'
Implement with version: STU 1.0.0
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
FHIR Mapping: ServiceRequest.occurrenceTiming.repeat.period
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the UMO authorized that the patient event must be rendered within a specific timeframe. If not required by this implementation guide, do not send.
Situational
5
615
Time Period Qualifier
O 1
ID
1/2
Code defining periods
FHIR Mapping: ServiceRequest.occurrenceTiming.repeat.boundsDuration.unit
Implement with version: STU 1.0.0
SEGMENT SYNTAX: C0605
SITUATIONAL RULE: Required when the UMO authorized a time period for which this patient event will be continued or to indicate that the value in HSD06 represents the authorized quantity remaining/not used. If not required by this implementation guide, do not send.
CODE
DEFINITION
6
Hour
7
Day
21
Years
26
Episode
27
Visit
29
Remaining
34
Month
35
Week
Situational
6
616
Number of Periods
O 1
N
1/3
Total number of periods
FHIR Mapping: ServiceRequest.occurrenceTiming.repeat.boundsDuration.value
Implement with version: STU 1.0.0
SEGMENT SYNTAX: C0605
SITUATIONAL RULE: Required when the UMO authorized a time period for which this patient event will be continued or to indicate that the value in HSD06 represents the authorized quantity remaining/not used. 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: ServiceRequest.occurrenceTiming.extension(timingCalendarPattern)
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.2.0
SITUATIONAL RULE: Required when the UMO authorized a specific calendar delivery pattern for the patient event. If not required by this implementation guide, do not send.
INDUSTRY NAME: Delivery Frequency Code
CODE
DEFINITION
1
1st Week of the Month
2
2nd Week of the Month
3
3rd Week of the Month
4
4th Week of the Month
5
5th Week of the Month
6
1st & 3rd Weeks of the Month
7
2nd & 4th Weeks of the Month
8
1st Working Day of Period
9
Last Working Day of Period
A
Monday through Friday
B
Monday through Saturday
C
Monday through Sunday
D
Monday
E
Tuesday
F
Wednesday
G
Thursday
H
Friday
J
Saturday
K
Sunday
L
Monday through Thursday
M
Immediately
N
As Directed
O
Daily Mon. through Fri.
P
1/2 Mon. & 1/2 Thurs.
Q
1/2 Tues. & 1/2 Thurs.
R
1/2 Wed. & 1/2 Fri.
S
Once Anytime Mon. through Fri.
SA
Sunday, Monday, Thursday, Friday, Saturday
SB
Tuesday through Saturday
SC
Sunday, Wednesday, Thursday, Friday, Saturday
SD
Monday, Wednesday, Thursday, Friday, Saturday
SG
Tuesday through Friday
SL
Monday, Tuesday and Thursday
SP
Monday, Tuesday and Friday
SX
Wednesday and Thursday
SY
Monday, Wednesday and Thursday
SZ
Tuesday, Thursday and Friday
T
1/2 Tue. & 1/2 Fri.
U
1/2 Mon. & 1/2 Wed.
V
1/3 Mon., 1/3 Wed., 1/3 Fri.
W
Whenever Necessary
WE
Weekend
X
1/2 By Wed., Bal. By Fri.
Y
None (Also Used to Cancel or Override a Previous Pattern)
Situational
8
679
Ship/Delivery Pattern Time Code
O 1
ID
1
Code which specifies the time for routine shipments or deliveries
FHIR Mapping: ServiceRequest.occurrenceTiming.extension(timingDeliveryPattern)
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.2.0
SITUATIONAL RULE: Required when the UMO authorized a specific time delivery pattern for the services in this patient event. If not required by this implementation guide, do not send.
INDUSTRY NAME: Delivery Pattern Time Code
CODE
DEFINITION
A
1st Shift (Normal Working Hours)
B
2nd Shift
C
3rd Shift
D
A.M.
E
P.M.
F
As Directed
G
Any Shift
Y
None (Also Used to Cancel or Override a Previous Pattern)

CL1 - INSTITUTIONAL CLAIM CODE

X12 Name:
Claim Codes
X12 Purpose:
To supply information specific to hospital claims
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the certification is for admission (UM01 = AR) to a facility and the information is known by the 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 Inquiry Response profile.
Implement with version: STU 1.2.0
TR3 Example:
CL1✱3✱✱01~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Situational
1
1315
Admission Type Code
O 1
ID
1
Code indicating the priority of this admission
SITUATIONAL RULE: Required when the certification is for admission (UM01 = AR) to a facility and the information is known by the UMO. If not required by this implementation guide, do not send.
CODE SOURCE 231: Priority (Type) of Admission or Visit
Situational
2
1314
Admission Source Code
O 1
ID
1
Code indicating the source of this admission
SITUATIONAL RULE: Required when the certification is for admission (UM01 = AR) to a facility and the information is known by the UMO. If not required by this implementation guide, do not send.
CODE SOURCE 230: Point of Origin for Admission or Visit
Situational
3
1352
Patient Status Code
O 1
ID
1/2
Code indicating patient status as of the "statement covers through date"
SITUATIONAL RULE: Required when the certification is for admission (UM01 = AR) to a facility and the information is known by the UMO. If not required by this implementation guide, do not send.
CODE SOURCE 239: Patient Status Code
Not Used
4
1345
Nursing Home Residential Status Code
O 1
ID
1

CR1 - AMBULANCE TRANSPORT INFORMATION

X12 Name:
Ambulance Certification
X12 Purpose:
To supply information related to the ambulance service rendered to a patient
X12 Syntax:
  1. P0102
    If either CR101 or CR102 is present, then the other is required.
  2. P0506
    If either CR105 or CR106 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when this is an authorization for specific non-emergency transport services. 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 Inquiry Response profile.
Implement with version: STU 1.0.0
TR3 Example:
CR1✱✱✱T✱✱DH✱28~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Not Used
1
355
Unit or Basis for Measurement Code
O 1
ID
2
Not Used
2
81
Weight
O 1
R
1/10
Required
3
1316
Ambulance Transport Code
O 1
ID
1
Code indicating the type of ambulance transport
CODE
DEFINITION
I
Initial Trip
R
Return Trip
T
Transfer Trip
X
Round Trip
Not Used
4
1317
Ambulance Transport Reason Code
O 1
ID
1
Situational
5
355
Unit or Basis for Measurement Code
O 1
ID
2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when the UMO has authorized ambulance transport for a specific transport distance. 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 the UMO has authorized ambulance transport for a specific transport distance. If not required by this implementation guide, do not send.
INDUSTRY NAME: Transport Distance
Not Used
7
166
Address Information
O 1
AN
1/55
Not Used
8
166
Address Information
O 1
AN
1/55
Not Used
9
352
Description
O 1
AN
1/80
Not Used
10
352
Description
O 1
AN
1/80

CR2 - SPINAL MANIPULATION SERVICE INFORMATION

X12 Name:
Chiropractic Certification
X12 Purpose:
To supply information related to the chiropractic service rendered to a patient
X12 Syntax:
  1. P0102
    If either CR201 or CR202 is present, then the other is required.
  2. C0403
    If CR204 is present, then CR203 is required.
  3. P0506
    If either CR205 or CR206 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the authorization is for spinal manipulation services that have a specific pattern of delivery usage. 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 Inquiry Response profile.
Implement with version: STU 1.0.0
TR3 Example:
CR2✱1✱5~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Situational
1
609
Count
O 1
N
1/9
Occurrence counter
SEMANTIC: CR201 is the number this treatment is in the series.
SEGMENT SYNTAX: P0102
SITUATIONAL RULE: Required when the authorization is for a treatment in a series. 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 the authorization is for a treatment in a series. 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 authorization is for a specific 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
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 authorization is for a specific level of subluxation. If not required by this implementation guide, do not send.
CODE
DEFINITION
C1
Cervical 1
C2
Cervical 2
C3
Cervical 3
C4
Cervical 4
C5
Cervical 5
C6
Cervical 6
C7
Cervical 7
CO
Coccyx
IL
Ilium
L1
Lumbar 1
L2
Lumbar 2
L3
Lumbar 3
L4
Lumbar 4
L5
Lumbar 5
OC
Occiput
SA
Sacrum
T1
Thoracic 1
T10
Thoracic 10
T11
Thoracic 11
T12
Thoracic 12
T2
Thoracic 2
T3
Thoracic 3
T4
Thoracic 4
T5
Thoracic 5
T6
Thoracic 6
T7
Thoracic 7
T8
Thoracic 8
T9
Thoracic 9
Not Used
5
355
Unit or Basis for Measurement Code
O 1
ID
2
Not Used
6
380
Quantity
O 1
R
1/15
Not Used
7
380
Quantity
O 1
R
1/15
Not Used
8
1342
Nature of Condition Code
O 1
ID
1
Not Used
9
1073
Yes/No Condition or Response Code
O 1
ID
1
Not Used
10
352
Description
O 1
AN
1/80
Not Used
11
352
Description
O 1
AN
1/80
Not Used
12
1073
Yes/No Condition or Response Code
O 1
ID
1

CR5 - HOME OXYGEN THERAPY INFORMATION

X12 Name:
Oxygen Therapy Certification
X12 Purpose:
To supply information regarding certification of medical necessity for home oxygen therapy
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the UMO has authorized specific usage of home oxygen therapy. 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 Inquiry Response profile.
Implement with version: STU 1.0.0
TR3 Example:
CR5✱✱✱D✱✱✱1✱✱✱✱✱✱✱✱✱✱2✱A~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Not Used
1
1322
Certification Type Code
O 1
ID
1
Not Used
2
380
Quantity
O 1
R
1/15
Situational
3
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 the UMO has authorized a specific type of equipment to administer the home 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
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 has been authorized. If not required by this implementation guide, do not send.
CODE
DEFINITION
A
Concentrator
B
Liquid Stationary
C
Gaseous Stationary
D
Liquid Portable
E
Gaseous Portable
O
Other
Not Used
5
352
Description
O 1
AN
1/80
Required
6
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: CR506 is the oxygen flow rate in liters per minute.
INDUSTRY NAME: Oxygen Flow Rate
Situational
7
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: CR507 is the number of times per day the patient must use oxygen.
SITUATIONAL RULE: Required when the UMO has authorized a daily oxygen use count. 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 the UMO has authorized an oxygen use period hour count. 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 the UMO must convey special orders to the respiratory therapist that could not otherwise be codified within this transaction. If not required by this implementation guide, do not send.
INDUSTRY NAME: Respiratory Therapist Order Text
Not Used
10
380
Quantity
O 1
R
1/15
Not Used
11
380
Quantity
O 1
R
1/15
Not Used
12
1349
Oxygen Test Condition Code
O 1
ID
1
Not Used
13
1350
Oxygen Test Findings Code
O 1
ID
1
Not Used
14
1350
Oxygen Test Findings Code
O 1
ID
1
Not Used
15
1350
Oxygen Test Findings Code
O 1
ID
1
Situational
16
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: CR516 is the oxygen flow rate for a portable oxygen system in liters per minute.
SITUATIONAL RULE: Required when either CR503, CR505 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 a third type of equipment has been authorized. 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:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the UMO has authorized a home health plan of treatment. 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 Inquiry Response profile.
Implement with version: STU 1.0.0
TR3 Example:
CR6✱7✱20050604✱✱✱✱✱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 UMO has authorized a specific certification period for the home health plan of treatment. 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 UMO has authorized a specific certification period for the home health plan of treatment. 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
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
I
Initial
N
Reconsideration
This code is used to request the UMO to reconsider a previously denied referral or certification request.
R
Renewal
S
Revised
Not Used
9
373
Date
O 1
DT
8
Not Used
10
235
Product/Service ID Qualifier
O 1
ID
2
Not Used
11
1137
Medical Code Value
O 1
AN
1/15
Not Used
12
373
Date
O 1
DT
8
Not Used
13
373
Date
O 1
DT
8
Not Used
14
373
Date
O 1
DT
8
Not Used
15
1250
Date Time Period Format Qualifier
O 1
ID
2/3
Not Used
16
1251
Date Time Period
O 1
AN
1/35
Not Used
17
1384
Patient Location Code
O 1
ID
1
Not Used
18
373
Date
O 1
DT
8
Not Used
19
373
Date
O 1
DT
8
Not Used
20
373
Date
O 1
DT
8
Not Used
21
373
Date
O 1
DT
8

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 it is necessary to send additional information about the patient event that could not otherwise be codified within the 2000E Loop. If not required by this implementation guide, do not send.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim Inquiry Response 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: ClaimResponse.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.2.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 valued on the inquiry and used by the UMO to locate authorizations, or when the UMO has authorized a specific provider or specialty entity for this patient event. If not required by this implementation guide, do not send.
TR3 Notes:
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.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim Inquiry Response profile.
Implement with version: STU 1.0.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
CODE
DEFINITION
71
Attending Physician
72
Operating Physician
73
Other Physician
77
Service Location
AAJ
Admitting Services
DD
Assistant Surgeon
DK
Ordering Physician
DN
Referring Provider
FA
Facility
G3
Clinic
P3
Primary Care Provider
QB
Purchase Service Provider
QV
Group Practice
SJ
Service Provider
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code qualifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
2
Non-Person Entity
Situational
3
1035
Name Last or Organization Name
O 1
AN
1/60
Individual last name or organizational name
SEGMENT SYNTAX: C1203
SITUATIONAL RULE: Required when valued on the inquiry and used by the UMO to locate authorizations, or when the UMO has identified a specific patient event provider by name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when NM103 is valued and NM102 = 1. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when NM104 is present and the middle name/initial of the person is known. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider Middle Name
Situational
6
1038
Name Prefix
O 1
AN
1/10
Prefix to individual name
SITUATIONAL RULE: Required when the UMO uses military title or rank to further identify the patient event provider. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider Name Prefix
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when the UMO uses the name suffix to further identify the patient event provider. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider Name Suffix
Situational
8
66
Identification Code Qualifier
O 1
ID
1/2
Code designating the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when valued on the inquiry and used by the UMO to locate authorizations or when the UMO has authorized a specific provider or specialty entity for this patient event by provider ID.
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 UMO;
OR
Required for providers before the mandated HIPAA NPI implementation date when the provider has an NPI and the UMO has the capability to send it.
If not required by this implementation guide, do not send.
CODE SOURCE: 537: Centers for Medicare & Medicaid Services National Provider Identifier
Situational
9
67
Identification Code
O 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when valued on the inquiry and used by the UMO to locate authorizations or when the UMO has authorized a specific provider or specialty entity for this patient event by provider ID.
INDUSTRY NAME: Patient Event Provider Identifier
Not Used
10
706
Entity Relationship Code
O 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/60

REF - PATIENT EVENT PROVIDER SUPPLEMENTAL IDENTIFICATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
9
Situational Rule:
Required prior to the mandated NPI implementation date when the Patient Event Provider is a Health Care Provider and an NPI is reported in NM109 of this loop and an additional identification number is required by the UMO to identify the Health Care Provider.
OR
Required when the Patient Event Provider is not a Health Care Provider and an NPI is reported in NM109 of this loop and an additional identification number is required by the UMO to identify the provider.
OR
Required prior to the mandated NPI implementation date when an identifier other than an NPI is reported in NM109 of this loop and an additional identification number is required by 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 not defined in the PAS Claim Inquiry Response 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
0B
State License Number
1G
Provider UPIN Number
1J
Facility ID Number
EI
Employer's Identification Number
Not used if NM108 = 24.
G5
Provider Site Number
N5
Provider Plan Network Identification Number
N7
Facility Network Identification Number
SY
Social Security Number
The social security number must not be used for Medicare. Not used if NM108 = 34.
ZH
Carrier Assigned Reference Number
Use for the provider ID as assigned by the UMO identified in Loop 2000A.
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Patient Event Provider Supplemental Identifier
Situational
3
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
SEGMENT SYNTAX: R0203
SITUATIONAL RULE: Required when REF01 = 0B to report the two character state ID of the state assigning the State License Number. If not required by this implementation guide, do not send.
INDUSTRY NAME: License Number State Code
See Code Source 22: State and Outlying Areas of the US.
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 UMO authorized a specific location for a patient event provider that has multiple locations. 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 Inquiry Response 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 Provider Address Line
Use this element for the first line of the service provider's address.
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required when a second address line exists. If not required by this implementation guide, do not send.
INDUSTRY NAME: 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 UMO authorized a specific location for a patient event provider that has multiple locations. 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 Inquiry Response profile.
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.
INDUSTRY NAME: Patient Event Provider City Name
Situational
2
156
State or Province Code
O 1
ID
2
Code (Standard State/Province) as defined by appropriate government agency
COMMENT: N402 is required only if city name (N401) is in the U.S. or Canada.
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider State or Province Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
O 1
ID
3/15
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada, or when a postal code exists for the country in N404. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider Postal Zone or ZIP Code
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
O 1
ID
2/3
Code identifying the country
SEGMENT SYNTAX: C0704
SITUATIONAL RULE: Required when the address is outside the United States of America. If not required by this implementation guide, do not send.
Use the alpha-2 country codes from Part 1 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
5
309
Location Qualifier
O 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
O 1
ID
1/3
Code identifying the country subdivision
SEGMENT SYNTAX: E0207, C0704
SITUATIONAL RULE: Required when the address is not in the United States of America, including its territories, or Canada, and the country in N404 has administrative subdivisions such as but not limited to states, provinces, cantons, etc. If not required by this implementation guide, do not send.
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds

PER*IC - PATIENT EVENT PROVIDER CONTACT INFORMATION

X12 Name:
Administrative Communications Contact
X12 Purpose:
To identify a person or office to whom administrative communications should be directed
X12 Syntax:
  1. P0304
    If either PER03 or PER04 is present, then the other is required.
  2. P0506
    If either PER05 or PER06 is present, then the other is required.
  3. P0708
    If either PER07 or PER08 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when needed to identify a contact name and/or communication number for the provider. If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver.
TR3 Notes:
When the communication number represents a telephone number in the United States and other countries using the North American Dialing Plan (for voice, data, fax, etc.), the communication number should always include the area code and phone number using the format AAABBBCCCC. Where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number (e.g. (534) 224-2525 would be represented as 5342242525). The extension, when applicable, should be included in the communication number immedidately after the telephone number.
FHIR Mapping:
The data elements in this segment are not defined in the PAS Claim Inquiry Response profile.
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
CODE
DEFINITION
IC
Information Contact
Situational
2
93
Name
O 1
AN
1/60
Free-form name
SITUATIONAL RULE: Required when the UMO needs to indicate a particular contact and the name of the individual 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: Patient Event Provider Contact Name
Required
3
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0304
CODE
DEFINITION
EM
Electronic Mail
FX
Facsimile
TE
Telephone
UR
Uniform Resource Locator (URL)
Required
4
364
Communication Number
O 1
AN
1/256
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0304
INDUSTRY NAME: Patient Event Provider Contact Communication Number
Situational
5
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
CODE
DEFINITION
EM
Electronic Mail
EX
Telephone Extension
When used, the value following this code is the extension for the preceding communications contact number.
FX
Facsimile
TE
Telephone
UR
Uniform Resource Locator (URL)
Situational
6
364
Communication Number
O 1
AN
1/256
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider Contact Communication Number
Situational
7
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
CODE
DEFINITION
EM
Electronic Mail
EX
Telephone Extension
When used, the value following this code is the extension for the preceding communications contact number.
FX
Facsimile
TE
Telephone
UR
Uniform Resource Locator (URL)
Situational
8
364
Communication Number
O 1
AN
1/256
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
INDUSTRY NAME: Patient Event Provider Contact Communication Number
Not Used
9
443
Contact Inquiry Reference
O 1
AN
1/20

AAA - PATIENT EVENT PROVIDER REQUEST VALIDATION

X12 Name:
Request Validation
X12 Purpose:
To specify the validity of the request and indicate follow-up action authorized
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
9
Situational Rule:
Required when the inquiry is not valid at this level to indicate the data condition that prohibits processing of the inquiry, or when the UMO has no authorizations on file that match the inquiry criteria specified at this level of the inquiry. 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 Inquiry Response profile.
Implement with version: STU 1.0.0
TR3 Example:
AAA✱N✱✱43✱C~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: AAA01 designates whether the request is valid or invalid. Code "Y" indicates that the code is valid; code "N" indicates that the code is invalid.
INDUSTRY NAME: Valid Request Indicator
CODE
DEFINITION
N
No
Use to indicate that the inquiry is not valid due to missing or invalid application data at this level of the inquiry.
Y
Yes
Use to indicate that no authorizations on file match the inquiry criteria specified at this level of the inquiry.
Not Used
2
559
Agency Qualifier Code
O 1
ID
2
Required
3
901
Reject Reason Code
O 1
ID
2
Code assigned by issuer to identify reason for rejection
CODE
DEFINITION
15
Required application data missing
Use when data are missing that are not covered by another reject reason code. Use to indicate when there is not enough information to identify the provider.
33
Input Errors
Use for input errors not covered by another reject reason code.
35
Out of Network
41
Authorization/Access Restrictions
43
Invalid/Missing Provider Identification
44
Invalid/Missing Provider Name
45
Invalid/Missing Provider Specialty
46
Invalid/Missing Provider Phone Number
47
Invalid/Missing Provider State
49
Provider is Not Primary Care Physician
51
Provider Not on File
52
Service Dates Not Within Provider Plan Enrollment
Use for patient event dates.
79
Invalid Participant Identification
Use for invalid/missing provider supplemental identifier.
97
Invalid or Missing Provider Address
IP
Inappropriate Provider Role
Required
4
889
Follow-up Action Code
O 1
ID
1
Code identifying follow-up actions allowed
CODE
DEFINITION
C
Please Correct and Resubmit
N
Resubmission Not Allowed

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 used by the UMO to identify the provider 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 Inquiry Response profile.
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
CODE
DEFINITION
AD
Admitting
Use only when NM101 = AAJ.
AS
Assistant Surgeon
Use only when NM101 = DD.
AT
Attending
Use only when NM101 = 71.
OP
Operating
Use only when NM101 = 72.
OR
Ordering
Use only when NM101 = DK.
OT
Other Physician
Use only when NM101 = 73.
PC
Primary Care Physician
Use only when NM101 = P3.
PE
Performing
Use only when NM101 = SJ.
RF
Referring
Use only when NM101 = DN.
Required
2
128
Reference Identification Qualifier
O 1
ID
2/3
Code qualifying the Reference Identification
SEGMENT SYNTAX: P0203
CODE
DEFINITION
PXC
Health Care Provider Taxonomy Code
CODE SOURCE: 682: Health Care Provider Taxonomy
Required
3
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: P0203
INDUSTRY NAME: Provider Taxonomy Code
Not Used
4
156
State or Province Code
O 1
ID
2
Not Used
5
C035
Provider Specialty Information
O 1
Not Used
6
1223
Provider Organization Code
O 1
ID
3

NM1 - 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 the UMO has authorized transport services that stipulate a specific origin and destination by address. 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 Inquiry Response profile.
Implement with version: STU 1.0.0
TR3 Example:
NM1✱PW✱2✱PATIENT DIALYSIS CENT~NM1✱FS✱2✱PATIENTS HOME~
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
Required
3
1035
Name Last or Organization Name
O 1
AN
1/60
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Patient 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 Inquiry Response 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 Inquiry Response 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, do not send.
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, do not send.
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, do not send.
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

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 the UMO system processed any of the information contained in Loop 2000F of the inquiry, or when the response returns authorization information about specific services or procedures. If not required by this implementation guide, do not send.
TR3 Notes:
  1. This segment conveys review information related to specific service(s).
  2. Use multiple occurrences of this loop if more than one service has been requested for this patient event.
  3. Required segments in this loop are required only when this loop is used.
FHIR Mapping:
ClaimResponse.item[n]
For each iteration of the 2000F create a new ClaimResponse.item
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: ClaimResponse.item[n].itemSequence
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: This data element is not defined in the PAS Claim Inquiry Response profile.
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: This data element is not defined in the PAS Claim Inquiry Response profile.
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: This data element is not defined in the PAS Claim Inquiry Response profile.
Implement with version: STU 1.0.0
CODE
DEFINITION
0
No Subordinate HL Segment in This Hierarchical Structure.

TRN - SERVICE TRACE NUMBER

X12 Name:
Trace
X12 Purpose:
To uniquely identify a transaction to an application
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
3
Situational Rule:
Required when this loop is returned and the inquiry contained a tracking number at this level, or if the UMO or clearinghouse assigns a trace number to this service in the response for tracking purposes. If not required by this implementation guide, do not send.
TR3 Notes:
  1. Any trace numbers provided at this level on the inquiry must be returned by the UMO at this level of the 278 inquiry response.
  2. If the 278 inquiry transaction passes through more than one clearinghouse, the second (and subsequent) clearinghouse may choose one of the following options:

    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.

    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 response transaction.
  3. If the 278 inquiry 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.
FHIR Mapping:
For each TRN segment create an itemTraceNumber extension.
Implement with version: STU 1.1.0
TR3 Example:
TRN✱2✱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: This data element is not defined in the PAS Claim Inquiry Response profile.
Implement with version: STU 1.1.0
CODE
DEFINITION
1
Current Transaction Trace Numbers
The term "Current Transaction Trace Number" refers to the trace number assigned by the creator of the 278 response transaction (the UMO).
2
Referenced Transaction Trace Numbers
The term "Referenced Transaction Trace Number" refers to the trace number originally sent in the 278 request transaction.
Required
2
127
Reference Identification
M 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: TRN02 provides unique identification for the transaction.
FHIR Mapping: ClaimResponse.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.2.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: extension[n].valueIdentifier.assigner.identifier.value = value of TRN03
Implement with version: STU 1.1.0
INDUSTRY NAME: Trace Assigning Entity Identifier
  1. Use this element to identify the organization that assigned this trace number. If TRN01 is "2", this is the value received in the original 278 request transaction. If TRN01 is "1", use this information to identify the UMO Organization that assigned this trace number.
  2. The first position must be either a "1" if an EIN is used, a "3" if a DUNS is used or a "9" if a user assigned identifier is used.
Situational
4
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: TRN04 identifies a further subdivision within the organization.
FHIR Mapping: extension[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.2.0
SITUATIONAL RULE: Required when TRN01 = 2 and TRN04 was valued on the inquiry or when TRN01 = 1 and the UMO needs to identify a specific component, such as a specific division or group, of the company identified in the previous data element (TRN03). If not required by this implementation guide, do not send.
INDUSTRY NAME: Trace Assigning Entity Additional Identifier

AAA - SERVICE REQUEST VALIDATION

X12 Name:
Request Validation
X12 Purpose:
To specify the validity of the request and indicate follow-up action authorized
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
9
Situational Rule:
Required when the inquiry is not valid at this level to indicate the data condition that prohibits processing of the inquiry, or when the UMO has no authorizations on file that match the inquiry criteria specified at the Service level of the inquiry. If not required by this implementation guide, do not send.
TR3 Notes:
Use this AAA segment to identify the reasons why the inquiry could not be processed based on the data at this level of the inquiry.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim Inquiry Response profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
AAA✱N✱✱52✱C~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: AAA01 designates whether the request is valid or invalid. Code "Y" indicates that the code is valid; code "N" indicates that the code is invalid.
FHIR Mapping: ClaimResponse.error[n].extension(errorElement)
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.2.0
INDUSTRY NAME: Valid Request Indicator
CODE
DEFINITION
N
No
Use to indicate that the inquiry is not valid due to missing or invalid application data at this level of the inquiry.
Y
Yes
Use to indicate that no authorizations on file match the inquiry criteria specified at this level of the inquiry.
Not Used
2
559
Agency Qualifier Code
O 1
ID
2
Required
3
901
Reject Reason Code
O 1
ID
2
Code assigned by issuer to identify reason for rejection
FHIR Mapping: ClaimResponse.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.0
CODE
DEFINITION
15
Required application data missing
Use when data are missing that are not covered by another Reject Reason Code. For example, use for missing place of service or missing service type codes.
33
Input Errors
Use for input errors in the patient event data not covered by the other reject reason codes listed. For example, use for invalid place of service or invalid service type code.
52
Service Dates Not Within Provider Plan Enrollment
57
Invalid/Missing Date(s) of Service
Use for invalid/missing service dates.
60
Date of Birth Follows Date(s) of Service
61
Date of Death Precedes Date(s) of Service
62
Date of Service Not Within Allowable Inquiry Period
AA
Authorization Number Not Found
AG
Invalid/Missing Procedure Code(s)
CI
Certification Information Does Not Match Patient
NC
No Certification Information Found
T5
Certification Information Missing
Use to indicate missing or invalid previous certification number information.
Required
4
889
Follow-up Action Code
O 1
ID
1
Code identifying follow-up actions allowed
FHIR Mapping: ClaimResponse.error[n].extension(errorFollowupAction)
The errorFollowupAction 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.2.0
CODE
DEFINITION
C
Please Correct and Resubmit
N
Resubmission Not Allowed

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 needed to identify the request category, service type, or service location for specific services and that information differs from the information returned in the Patent Event level (Loop 2000E) of this response. If not required by this implementation guide, do not send.
FHIR Mapping:
Not Used on PAS Claim Inquiry Response profile on FHIR ClaimResponse
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
CODE
DEFINITION
HS
Health Services Review
Use for review of services related to an episode of care.
SC
Specialty Care Review
Use for a referral to a specialty provider.
Situational
2
1322
Certification Type Code
O 1
ID
1
Code indicating the type of certification
SITUATIONAL RULE: Required when returning status information on authorization requests found and this information is retained by the UMO to indicate the certification type code on the original request. 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
Use to indicate a renewal of an existing authorization.
S
Revised
Use to indicate a revision to the specifics of an authorization for which services have not been rendered.
Situational
3
1365
Service Type Code
O 1
ID
1/2
Code identifying the classification of service
SITUATIONAL RULE: Required when the response returns status information on health care service reviews on file that specifiy a service type. If not required by this implementation guide, do not send.
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 the response returns status information on health care service reviews on file that specifiy a service location or facility type for this service detail. If not required by this implementation guide, do not send.
Required
4-1
1331
Facility Code Value
M 1
AN
1/2
Code identifying where services were, or may be, performed; the first and second positions of the Uniform Bill Type Code for Institutional Services or the Place of Service Codes for Professional or Dental Services.
INDUSTRY NAME: Facility Type Code
Use to indicate a facility code value from the code source referenced in UM04-2.
Required
4-2
1332
Facility Code Qualifier
O 1
ID
1/2
Code identifying the type of facility referenced
CODE
DEFINITION
A
Uniform Billing Claim Form Bill Type
CODE SOURCE: 236: Uniform Billing Claim Form Bill Type
B
Place of Service Codes for Professional or Dental Services
CODE SOURCE: 237: Place of Service Codes for Professional Claims
Not Used
4-3
1325
Claim Frequency Type Code
O 1
ID
1
Not Used
5
C024
Related Causes Information
O 1
Not Used
6
1338
Level of Service Code
O 1
ID
1/3
Not Used
7
1213
Current Health Condition Code
O 1
ID
1
Not Used
8
923
Prognosis Code
O 1
ID
1
Not Used
9
1363
Release of Information Code
O 1
ID
1
Not Used
10
1514
Delay Reason Code
O 1
ID
1/2

HCR - HEALTH CARE SERVICES REVIEW

X12 Name:
Health Care Services Review
X12 Purpose:
To specify the outcome of a health care services review
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the UMO has reviewed the original request at this level, and the UMO renders a decision at both the Patient Event level and at the Service level, to provide service review outcome information and an associated reference number. If not required by this implementation guide, do not send.
TR3 Notes:
  1. If the UMO was unable to locate authorizations due to missing or invalid application data at this level of the inquiry, the UMO must return a 278 response containing a AAA segment at this level.
  2. If the HCR segment is sent in this 2000F Service level loop, it will override an HCR segment sent in the Patient Event loop (2000E) for this service only.
FHIR Mapping:
ClaimResponse.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 populated as follows:
item[n].adjudication[0].extension[n].extension[] -> see HCR attributes below
item[n].adjudication[0].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.2.0
TR3 Example:
HCR✱A1✱20050713~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
306
Action Code
M 1
ID
1/2
Code indicating type of action
FHIR Mapping: «reviewAction».extension(reviewActionCode)
The reviewActionCode extension is a CodeableConcept and populated as follows:
extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-reviewActionCode'
extension[n].valueCodeableConcept.coding[0].system = 'https://codesystem.x12.org/005010/306'
extension[n].valueCodeableConcept.coding[0].code = value of HCR01
Implement with version: STU 1.2.0
Certification Action Code
CODE
DEFINITION
51
Complete
Use this code to identify authorizations with a status of complete. For the UMO, the authorization is complete at the time the claim is received and recorded.
71
Term Expired
Use this code to identify authorizations with a status of expired. For the UMO, this is based on the effective period for which the original certification was authorized.
A1
Certified in total
A3
Not Certified
A4
Pended
A6
Modified
C
Cancelled
CT
Contact Payer
NA
No Action Required
Use this code to identify health care service reviews on file for which an authorization decision was not necessary.
Situational
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: HCR02 is the number assigned by the information source to this review outcome.
FHIR Mapping: «reviewAction».extension(number)
The number extension is a string and is populated as follows:
extension[n].url = 'number'
extension[n].valueString = value of HCR02
Implement with version: STU 1.2.0
SITUATIONAL RULE: Required when the UMO system has assigned a review identification number to the health care service review reported in this Service loop. If not required by this implementation guide, do not send.
INDUSTRY NAME: Review Identification Number
Situational
3
1271
Industry Code
O 5
AN
1/30
Code indicating a code from a specific industry code list
SEMANTIC: HCR03 is the code assigned by the information source to identify the reason for the health care service review outcome indicated in HCR01.See Code Source 886
FHIR Mapping: «reviewAction».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.2.0
SITUATIONAL RULE: Required when HCR01 = A3 or A4. If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver.
INDUSTRY NAME: Review Decision Reason Code
This data element is a repeating data element and can be repeated the maximum number allowed by the standard in this implementation guide.
Situational
4
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: HCR04 is the second surgical opinion indicator. A "Y" value indicates a second surgical opinion is required; an "N" value indicates a second surgical opinion is not required for this request.
FHIR Mapping: «reviewAction».extension(secondSurgicalOpinionFlag)
The number extension is a boolean and is populated as follows:
extension[n].url = 'secondSurgicalOpinionFlag'
extension[n].valueString = true if HCR04 = 'Y', false if HCR04 = 'N'
Implement with version: STU 1.2.0
SITUATIONAL RULE: Required when certification pertains to a surgical procedure and the contract under which the patient is covered has provisions regarding a second surgical opinion. If not required by this implementation guide, do not send.
INDUSTRY NAME: Second Surgical Opinion Indicator
CODE
DEFINITION
N
No
Y
Yes

REF*BB - PREVIOUS REVIEW AUTHORIZATION NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when valued on the inquiry and the UMO does not have certification information on file that matches this previously assigned authorization number or when the authorization number submitted on the inquiry has been superseded. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
TR3 Notes:
If the requester valued this segment on the inquiry and the UMO has certification information on file that matches the previous certification number, the UMO must return that certification identification in HCR02 in the HCR Health Care Services Review segment of the inquiry response.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim Inquiry Response 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: This data element is not defined in the PAS Claim Inquiry Response profile.
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: ClaimResponse.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.2.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 valued on the inquiry and the UMO does not have certification information on file that matches this previously assigned administrative reference number. If not required by this implementation, may be provided at the sender's discretion but cannot be required by the receiver.
TR3 Notes:
If the requester valued this segment on the inquiry and the UMO has health care service review outcome information on file that matches the previous review administrative reference number, the UMO must return that outcome information in the HCR Health Care Service Review segment of the inquiry response. If the event was authorized, the UMO system must return the authorization number in HCR02.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim Inquiry Response profile, see the FHIR Mapping instructions for each data element below.
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
FHIR Mapping: This data element is not defined in the PAS Claim Inquiry Response profile.
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: ClaimResponse.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.2.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 the UMO authorized the service for a specific date or date range. 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 Response profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
DTP✱472✱D8✱20050723~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
FHIR Mapping: This data element is not defined in the PAS Claim Inquiry Response profile.
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: See note on DTP03
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: ClaimResponse.item[n].extension(itemAuthorizedDate)
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.2.0
INDUSTRY NAME: Proposed or Actual Service Date

DTP*102 - CERTIFICATION ISSUE DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the UMO assigned a certification issue date to this authorization. If not required by this implementation guide, do not send.
TR3 Notes:
This is not the effective date of the authorization. This is the date when the UMO issued the authorization.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim Inquiry Response profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
DTP✱102✱D8✱20050701~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
FHIR Mapping: This data element is not defined in the PAS Claim Inquiry Response profile.
Implement with version: STU 1.0.0
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
102
Issue
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
FHIR Mapping: This data element is not defined in the PAS Claim Inquiry Response profile.
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: ClaimResponse.item[n].extension(itemPreAuthIssueDate)
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.2.0
INDUSTRY NAME: Certification Issue Date

DTP*036 - CERTIFICATION EXPIRATION DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the authorization has an expiration date to indicate the date on which the authorization expired or will expire. 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 Response profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
DTP✱036✱D8✱20050731~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
FHIR Mapping: This data element is not defined in the PAS Claim Inquiry Response profile.
Implement with version: STU 1.0.0
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
036
Expiration
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
FHIR Mapping: This data element is not defined in the PAS Claim Inquiry Response profile.
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: ClaimResponse.item[n].extension(itemPreAuthPeriod)
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.2.0
INDUSTRY NAME: Certification Expiration Date

DTP*007 - CERTIFICATION EFFECTIVE DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the authorization is limited by effective dates to indicate the date or date range when the certification is effective. 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 Response profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
DTP✱007✱RD8✱20050701-20050731~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
FHIR Mapping: This data element is not defined in the PAS Claim Inquiry Response profile.
Implement with version: STU 1.0.0
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
007
Effective
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
FHIR Mapping: See note on DTP03
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: ClaimResponse.item[n].extension(itemPreAuthPeriod)
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.2.0
INDUSTRY NAME: Certification Effective Date

SV1 - PROFESSIONAL SERVICE

X12 Name:
Professional Service
X12 Purpose:
To specify the service line item detail for a health care professional
X12 Syntax:
P0304
If either SV103 or SV104 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the UMO has authorized a specific professional service. If not required by this implementation guide, do not send.
FHIR Mapping:
ClaimResponse.item[n].extension(itemAuthorizedDetail)
The components of the SV1 segment are used to create the itemAuthorizedDetail extension in an item (created for the 2000F loop as noted above). The itemAuthorizedDetail 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 itemAuthorizedDetail 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.2.0
TR3 Example:
SV1✱HC:99211:25✱12✱UN✱1✱✱✱✱✱✱✱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: Convert 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 is an Alphabetic Character (A-Z) HC = 'http://www.cms.gov/Medicare/Coding/HCPCSReleaseCodeSets'
If the 1st position of the code is a Numeric (0-9) HC = 'http://www.ama-assn.org/go/cpt'
N4 = 'http://hl7.org/fhir/sid/ndc'
Implement with version: STU 1.2.0
INDUSTRY NAME: Product or Service ID Qualifier
CODE
DEFINITION
HC
Health Care Financing Administration Common Procedural Coding System (HCPCS) Codes
Because the AMA's CPT codes are also level 1 HCPCS codes, they are reported under HC.
CODE SOURCE: 130: Healthcare Common Procedure Coding System
IV
Home Infusion EDI Coalition (HIEC) Product/Service Code
This code set is not allowed for use under HIPAA at the time of this writing. Use only in non-HIPAA implementations.
CODE SOURCE: 513: Home Infusion EDI Coalition (HIEC) Product/Service Code List
N4
National Drug Code in 5-4-2 Format
CODE SOURCE: 240: National Drug Code by Format
WK
Advanced Billing Concepts (ABC) Codes
At the time of this writing, this code set has been approved by the Secretary of HHS as a pilot project allowed under the HIPAA law. The qualifier can only be used in transactions covered under HIPAA by parties registered in the pilot project and their trading partners,
OR
If a new rule names the ABC codes as an allowable code set under HIPAA,
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: «authorizedItemDetail».extension(productOrServiceCode)
The productOrServiceCode extension is comprised of multiple attributes from the SV1 as follows:
extension[n].url = 'productOrServiceCode'
extension[n].valueCodeableConcept.coding[0].system = SV101-01
extension[n].valueCodeableConcept.coding[0].code = value of SV101-02
extension[n].valueCodeableConcept.text = SV101-07
Implement with version: STU 1.2.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: «authorizedItemDetail».extension(modifier)
The modifier extension is comprised as follows:
extension[n].url = 'modifier'
extension[n].valueCodeableConcept.coding[0].system = SV101-01
extension[n].valueCodeableConcept.coding[0].code = value of SV101-03
Implement with version: STU 1.2.0
SITUATIONAL RULE: Required when the UMO has authorized a procedure with modifiers. If not required by this implementation guide, do not send.
Situational
1-4
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
FHIR Mapping: «authorizedItemDetail».extension(modifier)
The modifier extension is comprised as follows:
extension[n].url = 'modifier'
extension[n].valueCodeableConcept.coding[0].system = SV101-01
extension[n].valueCodeableConcept.coding[0].code = value of SV101-04
Implement with version: STU 1.2.0
SITUATIONAL RULE: Required when the UMO has authorized a procedure with modifiers. If not required by this implementation guide, do not send.
Situational
1-5
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
FHIR Mapping: «authorizedItemDetail».extension(modifier)
The modifier extension is comprised as follows:
extension[n].url = 'modifier'
extension[n].valueCodeableConcept.coding[0].system = SV101-01
extension[n].valueCodeableConcept.coding[0].code = value of SV101-05
Implement with version: STU 1.2.0
SITUATIONAL RULE: Required when the UMO has authorized a procedure with modifiers. If not required by this implementation guide, do not send.
Situational
1-6
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
FHIR Mapping: «authorizedItemDetail».extension(modifier)
The modifier extension is comprised as follows:
extension[n].url = 'modifier'
extension[n].valueCodeableConcept.coding[0].system = SV101-01
extension[n].valueCodeableConcept.coding[0].code = value of SV101-06
Implement with version: STU 1.2.0
SITUATIONAL RULE: Required when the UMO has authorized a procedure with modifiers. If not required by this implementation guide, do not send.
Situational
1-7
352
Description
O 1
AN
1/80
A free-form description to clarify the related data elements and their content
FHIR Mapping: «authorizedItemDetail».extension(productOrServiceCode)
See SV101-02 for using this attribute in the productOrServiceCode
Implement with version: STU 1.2.0
SITUATIONAL RULE: Required only when the UMO needs to provide further clarification on the review of this service. 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
FHIR Mapping: «authorizedItemDetail».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 = SV101-01
extension[n].valueCodeableConcept.coding[0].code = value of SV101-08
Implement with version: STU 1.2.0
SITUATIONAL RULE: Required when the UMO has authorized a range of procedures. If not required by this implementation guide, do not send.
INDUSTRY NAME: Product or Service ID
Use SV101-2 to represent the beginning value in 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: SV102 is the submitted service line item amount.
FHIR Mapping: «authorizedItemDetail».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.2.0
SITUATIONAL RULE: Required when the UMO has approved the health care service with monetary limitations. 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: «authorizedItemDetail».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.2.0
SEGMENT SYNTAX: P0304
SITUATIONAL RULE: Required when service units were not provided in the HSD segment and a specific number of service units was authorized 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: See SV103 above
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 service units was authorized 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
Not Used
7
C004
Composite Diagnosis Code Pointer
O 1
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: «authorizedItemDetail».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.2.0
SITUATIONAL RULE: Required when the review decision was 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
Not Used
20
1337
Level of Care Code
O 1
ID
1
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 the UMO has authorized a specific institutional service. If not required by this implementation guide, do not send.
TR3 Notes:
Use this segment to identify a specific revenue code.
FHIR Mapping:
ClaimResponse.item[n].extension(itemAuthorizedDetail)
The components of the SV2 segment are used to create the itemAuthorizedDetail extension in an item (created for the 2000F loop as noted above). The itemAuthorizedDetail 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 itemAuthorizedDetail 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.2.0
TR3 Example:
  1. SV2✱300✱HC:80019✱73✱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: «authorizedItemDetail».extension(revenue)
The revenue extension is of type 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.2.0
SEGMENT SYNTAX: R0102
SITUATIONAL RULE: Required when the UMO authorized 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 the UMO has authorized 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: Convert 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 is an Alphabetic Character (A-Z) HC = 'http://www.cms.gov/Medicare/Coding/HCPCSReleaseCodeSets'
If the 1st position of the code is a Numeric (0-9) HC = 'http://www.ama-assn.org/go/cpt'
N4 = 'http://hl7.org/fhir/sid/ndc'
Implement with version: STU 1.2.0
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
Use for inpatient services only.
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
At the time of this writing, this code set has been approved by the Secretary of HHS as a pilot project allowed under the HIPAA law. The qualifier can only be used in transactions covered under HIPAA by parties registered in the pilot project and their trading partners,
OR
If a new rule names the ABC codes as an allowable code set under HIPAA,
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: «authorizedItemDetail».extension(productOrServiceCode)
The productOrServiceCode extension is comprised of multiple attributes from the SV2 as follows:
extension[n].url = 'productOrServiceCode'
extension[n].valueCodeableConcept.coding[0].system = value from SV202-01
extension[n].valueCodeableConcept.coding[0].code = value of SV202-02
extension[n].valueCodeableConcept.text = value of SV202-07
Implement with version: STU 1.2.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: «authorizedItemDetail».extension(modifier)
The modifier extension is comprised as follows:
extension[n].url = 'modifier'
extension[n].valueCodeableConcept.coding[0].system = value from SV202-01
extension[n].valueCodeableConcept.coding[0].code = value of SV202-03
Implement with version: STU 1.2.0
SITUATIONAL RULE: Required when the UMO has authorized a procedure with modifiers. If not required by this implementation guide, do not send.
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: Awaiting implementation of change request for mapping
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the UMO has authorized a procedure with modifiers. If not required by this implementation guide, do not send.
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: Awaiting implementation of change request for mapping
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the UMO has authorized a procedure with modifiers. If not required by this implementation guide, do not send.
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: Awaiting implementation of change request for mapping
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the UMO has authorized a procedure with modifiers. If not required by this implementation guide, do not send.
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: «authorizedItemDetail».extension(productOrServiceCode)
See SV202-02 for using this attribute in the productOrServiceCode
Implement with version: STU 1.2.0
SITUATIONAL RULE: Required when the UMO needs to provide further clarification on the review of this service. If not required by this implementation guide, do not send.
INDUSTRY NAME: Procedure Code Description
Situational
2-8
234
Product/Service ID
O 1
AN
1/48
Identifying number for a product or service
FHIR Mapping: «authorizedItemDetail».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 = value from SV202-01
extension[n].valueCodeableConcept.coding[0].code = value of SV202-08
Implement with version: STU 1.2.0
SITUATIONAL RULE: Required when the UMO has authorized a range of procedures. If not required by this implementation guide, do not send.
INDUSTRY NAME: Product or Service ID
Use SV202-2 to represent the beginning value in the procedure range and this data element to represent the ending value in a range of codes.
Situational
3
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: SV203 is the submitted service line item amount.
FHIR Mapping: «authorizedItemDetail».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.2.0
SITUATIONAL RULE: Required when the UMO has approved the health care service with monetary limitations. 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: «authorizedItemDetail».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.2.0
SEGMENT SYNTAX: P0405
SITUATIONAL RULE: Required when service units were not provided in the HSD segment and a specific number of service units was authorized for this procedure. If not required by this implementation guide, do not send.
CODE
DEFINITION
DA
Days
F2
International Unit
International Unit is used to indicate dosage amount. Dosage amount is only used for drug claims when the dosage of the drug is variable within a single NDC number (e.g., blood factors).
UN
Unit
Situational
5
380
Quantity
O 1
R
1/15
Numeric value of quantity
FHIR Mapping: See SV204 above
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 service units was authorized 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: «authorizedItemDetail».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.2.0
SITUATIONAL RULE: Required when SV201 is used and the UMO has approved the health care service with monetary limitations on the accommodation rate. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Line Rate
Not Used
7
782
Monetary Amount
O 1
R
1/18
Not Used
8
1073
Yes/No Condition or Response Code
O 1
ID
1
Not Used
9
1345
Nursing Home Residential Status Code
O 1
ID
1
Not Used
10
1337
Level of Care Code
O 1
ID
1

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 the UMO has authorized 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 Inquiry Response 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
CODE SOURCE: 135: American Dental Association
Required
1-2
234
Product/Service ID
M 1
AN
1/48
Identifying number for a product or service
INDUSTRY NAME: Procedure Code
Situational
1-3
1339
Procedure Modifier
O 1
AN
2
This identifies special circumstances related to the performance of the service, as defined by trading partners
SITUATIONAL RULE: Required when the UMO has authorized a procedure with modifiers. If not required by this implementation guide, do not send.
A modifier must be from code source 135 (American Dental Association) found in the `Code on Dental Procedures and Nomenclature', 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 the UMO has authorized a procedure with modifiers. If not required by this implementation guide, do not send.
A modifier must be from code source 135 (American Dental Association) found in the `Code on Dental Procedures and Nomenclature', 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 the UMO has authorized a procedure with modifiers. If not required by this implementation guide, do not send.
A modifier must be from code source 135 (American Dental Association) found in the `Code on Dental Procedures and Nomenclature', 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 the UMO has authorized a procedure with modifiers. If not required by this implementation guide, do not send.
A modifier must be from code source 135 (American Dental Association) found in the `Code on Dental Procedures and Nomenclature', 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 UMO needs to provide further clarification on the review of this service. 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 UMO has authorized a range of procedures. If not required by this implementation guide, do not send.
INDUSTRY NAME: Product or Service ID
Use SV301-2 to represent the beginning value in the procedure range and this data element to represent the ending value in a range of codes.
Situational
2
782
Monetary Amount
O 1
R
1/18
Monetary amount
SEMANTIC: SV302 is the submitted service line item amount.
SITUATIONAL RULE: Required when the UMO has approved the health care service with monetary limitations. 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 the UMO has authorized treatment of an area of the oral cavity. If not required by this implementation guide, do not send.
  1. Do not use this element to indicate authorization of individual teeth. Use the Tooth Information (TOO) segment in this loop for authorizations related to one or more individual teeth.
  2. The oral cavity area codes are contained in the ISO TC 106 Designation System for Teeth and Areas of the Oral Cavity.
Required
4-1
1361
Oral Cavity Designation Code
M 1
ID
1/3
Code Identifying the area of the oral cavity in which service is rendered
CODE SOURCE 135: American Dental Association
Situational
4-2
1361
Oral Cavity Designation Code
O 1
ID
1/3
Code Identifying the area of the oral cavity in which service is rendered
SITUATIONAL RULE: Required when the UMO has authorized a procedure for a second area of the oral cavity. If not required by this implementation guide, do not send.
The code values in SV304-1 apply to all occurrences of the oral cavity designation code.
CODE SOURCE 135: American Dental Association
Situational
4-3
1361
Oral Cavity Designation Code
O 1
ID
1/3
Code Identifying the area of the oral cavity in which service is rendered
SITUATIONAL RULE: Required when the UMO has authorized a procedure for a third area of the oral cavity. If not required by this implementation guide, do not send.
The code values in SV304-1 apply to all occurrences of the oral cavity designation code.
CODE SOURCE 135: American Dental Association
Situational
4-4
1361
Oral Cavity Designation Code
O 1
ID
1/3
Code Identifying the area of the oral cavity in which service is rendered
SITUATIONAL RULE: Required when the UMO has authorized a procedure for a fourth area of the oral cavity. If not required by this implementation guide, do not send.
The code values in SV304-1 apply to all occurrences of the oral cavity designation code.
CODE SOURCE 135: American Dental Association
Situational
4-5
1361
Oral Cavity Designation Code
O 1
ID
1/3
Code Identifying the area of the oral cavity in which service is rendered
SITUATIONAL RULE: Required when the UMO has authorized a procedure for a fifth area of the oral cavity. If not required by this implementation guide, do not send.
The code values in SV304-1 apply to all occurrences of the oral cavity designation code.
CODE SOURCE 135: American Dental Association
Situational
5
1358
Prosthesis, Crown or Inlay Code
O 1
ID
1
Code specifying the placement status for the dental work
SITUATIONAL RULE: Required when the UMO has authorized dental prosthesis, crown, or inlay. If not required by this implementation code, 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.
Not Used
7
352
Description
O 1
AN
1/80
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 the UMO has authorized the procedure for a specific tooth number and/or tooth surface related to this procedure line. 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 Inquiry Response 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
See Appendix A for 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 the procedure code requires tooth surface codes. 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 reporting a second tooth surface. If not required by this implementation guide, do not send.
Additional tooth surface codes can be carried in TOO03-2 through TOO03-5. The code values are the same as in 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 reporting a third tooth surface. If not required by this implementation guide, do not send.
CODE
DEFINITION
B
Buccal
D
Distal
F
Facial
I
Incisal
L
Lingual
M
Mesial
O
Occlusal
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 reporting a fourth tooth surface. If not required by this implementation guide, do not send.
CODE
DEFINITION
B
Buccal
D
Distal
F
Facial
I
Incisal
L
Lingual
M
Mesial
O
Occlusal
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 reporting a fifth tooth surface. If not required by this implementation guide, do not send.
CODE
DEFINITION
B
Buccal
D
Distal
F
Facial
I
Incisal
L
Lingual
M
Mesial
O
Occlusal

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 the UMO authorized services with 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 or when identifying the number of medical services reservations remaining. 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:
«authorizedItemDetail».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 = «ServiceRequest id in Bundle»
Set the ServiceRequest.subject to the value of ClaimResponse.patient
Note: Although 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.2.0
TR3 Example:
HSD✱VS✱1✱DA✱1✱7✱10~ (This indicates "1 visit every (per) 1 day (daily)for 10 days".)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: ServiceRequest.quantityQuantity.unit
Implement with version: STU 1.2.0
SEGMENT SYNTAX: P0102
SITUATIONAL RULE: Required when the pattern of delivery has a quanity of services authorized. 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: ServiceRequest.quantityQuantity.value
Implement with version: STU 1.0.0
SEGMENT SYNTAX: P0102
SITUATIONAL RULE: Required when the pattern of delivery has a quanity of services authorized. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Unit Count
Service Quantity
Situational
3
355
Unit or Basis for Measurement Code
O 1
ID
2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
FHIR Mapping: ServiceRequest.occurrenceTiming.repeat.periodUnit
Translate the HSD03 value as follows:
'DA' -> 'd'
'WK' -> 'wk'
'MO' -> 'mo'
Implement with version: STU 1.0.0
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
FHIR Mapping: ServiceRequest.occurrenceTiming.repeat.period
Implement with version: STU 1.0.0
SITUATIONAL RULE: Required when the UMO authorized services which must be rendered within a specific time frame. 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: ServiceRequest.occurrenceTiming.repeat.boundsDuration.unit
Implement with version: STU 1.0.0
SEGMENT SYNTAX: C0605
SITUATIONAL RULE: Required when the UMO authorized services that can continue for a specific time period. If not required by this implementation guide, do not send.
CODE
DEFINITION
6
Hour
7
Day
21
Years
26
Episode
27
Visit
29
Remaining
34
Month
35
Week
Situational
6
616
Number of Periods
O 1
N
1/3
Total number of periods
FHIR Mapping: ServiceRequest.occurrenceTiming.repeat.boundsDuration.value
Implement with version: STU 1.0.0
SEGMENT SYNTAX: C0605
SITUATIONAL RULE: Required when the UMO authorized a service to continue for a specific time period. 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: ServiceRequest.occurrenceTiming.extension(timingCalendarPattern)
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.2.0
SITUATIONAL RULE: Required when the UMO authorized a specific calendar delivery pattern for the service. 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: ServiceRequest.occurrenceTiming.extension(timingDeliveryPattern)
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.2.0
SITUATIONAL RULE: Required when the UMO authorized a specific time delivery pattern for the service. 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)

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 it is necessary to send additional information about the Service which could not otherwise be codified within the 2000F Loop. 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 Response 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: ClaimResponse.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.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 the UMO authorized a specific provider or specialty entity for this service. If not required by this implementation guide, do not send.
TR3 Notes:
Use this segment to convey the name and identification number of the service provider (person, group, or facility) or to identify the specialty entity.
FHIR Mapping:
ClaimResponse.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 = «Practitioner or Organization id in Bundle»
Implement with version: STU 1.2.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: extension[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.2.0
CODE
DEFINITION
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 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.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.family | Organization.name
Implement with version: STU 1.0.0
SEGMENT SYNTAX: C1203
SITUATIONAL RULE: Required when the UMO authorized a specific person, facility, group practice, clinic, or specialty entity for this service. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Provider Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
FHIR Mapping: Practitioner.name.given[0] | not used on Organization
Implement with version: STU 1.2.0
SITUATIONAL RULE: Required when NM103 is valued and NM102 = 1. 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.given[1] | not used on Organization
Implement with version: STU 1.2.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.prefix[0] | not used on Organization
Implement with version: STU 1.2.0
SITUATIONAL RULE: Required when the UMO uses military title or rank to further identify the individual provider. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Provider Name Prefix
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
FHIR Mapping: Practitioner.name.suffix[0] | not used on Organization
Implement with version: STU 1.2.0
SITUATIONAL RULE: Required when the UMO uses the name suffix to further identify the individual. 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 | Organization.identifier[0].type
Populate the CodeableConcept components of the type 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.0
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when the UMO authorized a specific provider or specialty entity for this service by provider ID. 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 UMO;
OR
Required for providers before the mandated HIPAA NPI implementation date when the provider has an NPI and the UMO 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 the UMO authorized a specific provider or specialty entity for this service by provider ID. 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:
9
Situational Rule:
Required prior to the mandated NPI implementation date when the Service Provider is a Health Care Provider and an NPI is reported in NM109 of this loop and an additional identification number is required by the UMO to identify the Health Care Provider.
OR
Required when the Service Provider is not a Health Care Provider and an NPI is reported in NM109 of this loop and an additional identification number is required by the UMO to identify the provider.
OR
Required prior to the mandated NPI implementation date when an identifier other than an NPI is reported in NM109 of this loop and an additional identification number is required by 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 Response profile, see the FHIR Mapping instructions for each data element below.
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
FHIR Mapping: Practitioner.identifier[1].type | Organization.identifier[1].type
Populate the CodeableConcept components of the type as follows:
type.coding[0].system = 'http://terminology.hl7.org/CodeSystem/v2-0203'
type.coding[0].code = value of REF01 translated as follows:
'0B' -> 'SL'
'1G' -> 'UPIN'
'1J' -> 'FI'
'EI' -> 'EN'
'G5' -> 'G5'
'N5' -> 'N5'
'N7' -> 'N7'
'SY' -> 'SB'
'ZH' -> 'ZH'
Implement with version: STU 1.2.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.
G5
Provider Site Number
N5
Provider Plan Network Identification Number
N7
Facility Network Identification Number
SY
Social Security Number
The social security number must not be used for Medicare. Not used if NM108 = 34.
ZH
Carrier Assigned Reference Number
Use for the provider ID as assigned by the UMO identified in Loop 2000A.
Required
2
127
Reference Identification
O 1
AN
1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
FHIR Mapping: Practitioner.identifier[1].value | Organization.identifier[1].value
Implement with version: STU 1.2.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(identifierJurisdiction).coding[0].code | Organization.identifier[1].extension(identifierJurisdiction).coding[0].code
Implement with version: STU 1.2.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 UMO uses the address to further identify the service provider or when the UMO authorizes a specific location for a service provider that has multiple locations. 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 Response 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[0] | Organization.address[0].line[0]
Implement with version: STU 1.0.0
INDUSTRY NAME: Service Provider Address Line
Use this element for the first line of the service provider's address.
Situational
2
166
Address Information
O 1
AN
1/55
Address information
FHIR Mapping: Practitioner.address[0].line[1] | 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: 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 UMO uses the address to further identify the service provider or when the UMO authorizes a specific location for a service provider that has multiple locations. 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 Response 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 communication number for the provider. If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver.
TR3 Notes:
When the communication number represents a telephone number in the United States and other countries using the North American Dialing Plan (for voice, data, fax, etc.), the communication number should always include the area code and phone number using the format AAABBBCCCC. Where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number (e.g. (534) 224-2525 would be represented as 5342242525). The extension, when applicable, should be included in the communication number immedidately after the telephone number.
FHIR Mapping:
The data elements in this segment are defined in the PAS Claim Inquiry Response 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✱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: This data element is not defined in the PAS Claim Inquiry Response profile.
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: Not used on Practitioner | Organization.contact[0].name.text
Implement with version: STU 1.2.0
SITUATIONAL RULE: Required when the UMO wishes to indicate a particular contact for this service provider and the name of the individual to contact is not already defined or is different than the name within the prior name supplied in the NM1 segment of this loop. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Provider Contact Name
Required
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
Translate the PER03 value as follows:
EM -> email
FX -> fax
TE -> phone
UR -> url
Implement with version: STU 1.2.0
SEGMENT SYNTAX: P0304
CODE
DEFINITION
EM
Electronic Mail
FX
Facsimile
TE
Telephone
UR
Uniform Resource Locator (URL)
Required
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].value
Implement with version: STU 1.2.0
SEGMENT SYNTAX: P0304
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
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.2.0
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
CODE
DEFINITION
EM
Electronic Mail
EX
Telephone Extension
When used, the value following this code is the extension for the preceding communications contact number.
FX
Facsimile
TE
Telephone
UR
Uniform Resource Locator (URL)
Situational
6
364
Communication Number
O 1
AN
1/256
Complete communications number including country or area code when applicable
FHIR Mapping: Practitioner.telecom[1].value | Organization.contact[0].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. «value-of-PER06»' to telecom[0].value
See ITU-T E.123 for format of telephone values
Implement with version: STU 1.2.0
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Provider Contact Communication Number
Situational
7
365
Communication Number Qualifier
O 1
ID
2
Code identifying the type of communication number
FHIR Mapping: Practitioner.telecom[n].system | Organization.contact[0].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.2.0
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
CODE
DEFINITION
EM
Electronic Mail
EX
Telephone Extension
When used, the value following this code is the extension for the preceding communications contact number.
TE
Telephone
UR
Uniform Resource Locator (URL)
Situational
8
364
Communication Number
O 1
AN
1/256
Complete communications number including country or area code when applicable
FHIR Mapping: Practitioner.telecom[n].value | Organization.contact[0].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. «value-of-PER06»' to telecom[1].value
See ITU-T E.123 for format of telephone values
Implement with version: STU 1.2.0
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when a telephone extension or multiple communication types are available. If not required by this implementation guide, do not send.
INDUSTRY NAME: Service Provider Contact Communication Number
Not Used
9
443
Contact Inquiry Reference
O 1
AN
1/20

AAA - SERVICE PROVIDER REQUEST VALIDATION

X12 Name:
Request Validation
X12 Purpose:
To specify the validity of the request and indicate follow-up action authorized
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
9
Situational Rule:
Required when the inquiry is not valid at this level to indicate the data condition that prohibits processing of the inquiry, or when the UMO has no authorizations on file that match the inquiry criteria specified at the this level of the inquiry. 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 Response profile, see the FHIR Mapping instructions for each data element below.
Implement with version: STU 1.0.0
TR3 Example:
AAA✱N✱✱43✱C~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: AAA01 designates whether the request is valid or invalid. Code "Y" indicates that the code is valid; code "N" indicates that the code is invalid.
FHIR Mapping: ClaimResponse.error[n].extension(errorElement)
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.2.0
INDUSTRY NAME: Valid Request Indicator
CODE
DEFINITION
N
No
Use to indicate that the inquiry is not valid due to missing or invalid application data at this level of the inquiry.
Y
Yes
Use to indicate that no authorizations on file match the inquiry criteria specified at this level of the inquiry.
Not Used
2
559
Agency Qualifier Code
O 1
ID
2
Required
3
901
Reject Reason Code
O 1
ID
2
Code assigned by issuer to identify reason for rejection
FHIR Mapping: ClaimResponse.error[n].code
Populate the CodeableConcept components of the type 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.0
CODE
DEFINITION
15
Required application data missing
Use when data is missing that is not covered by another reject reason code. Use to indicate when there is not enough information to identify the service provider.
33
Input Errors
Use for input errors not covered by another reject reason code.
35
Out of Network
41
Authorization/Access Restrictions
43
Invalid/Missing Provider Identification
44
Invalid/Missing Provider Name
45
Invalid/Missing Provider Specialty
46
Invalid/Missing Provider Phone Number
47
Invalid/Missing Provider State
49
Provider is Not Primary Care Physician
51
Provider Not on File
52
Service Dates Not Within Provider Plan Enrollment
79
Invalid Participant Identification
97
Invalid or Missing Provider Address
IP
Inappropriate Provider Role
Required
4
889
Follow-up Action Code
O 1
ID
1
Code identifying follow-up actions allowed
FHIR Mapping: ClaimResponse.error[n].extension(errorFollowupAction)
The errorFollowupAction 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.2.0
CODE
DEFINITION
C
Please Correct and Resubmit
N
Resubmission Not Allowed

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 used by the UMO to identify the provider specialty. 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 Response profile, see the FHIR Mapping instructions for each data element below.
Not used for Organization
Implement with version: STU 1.2.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: This data element is not defined in the PAS Claim Inquiry Response profile.
Implement with version: STU 1.1.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: This data element is not defined in the PAS Claim Inquiry Response profile.
Implement with version: STU 1.1.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: Practitioner.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.2.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

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 Inquiry Response profile.
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 - Inquiry and Response (005010X215)

FEBRUARY 2024

Copyright © 2008-2024, X12 Incorporated, Format © 2008-2024 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 Inquiry and Response Implementation Guide describes the use of the X12 Health Care Services Review Information (278) transaction set for the following business usages:

  • Make inquiries to utilization management organizations for information on previously processed health care services
  • Send response(s) to inquiry(ies) on previously processed health care services

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 inquire on authorizations or certifications or who respond to such inquiries 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 inquiries and responses. The intention of the developers of the 278 is represented in this guide.

This implementation guide is designed to assist providers who inquire about certification decisions (specialty care, treatment, admission) and the Utilization Management Organizations (UMO) who respond to those inquiries using the 278 format. In the context of this implementation guide, an inquiry refers to a transaction that asks for information on previously processed requests for authorization or certification.


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

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

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

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

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


1.3.2 Other Usage Limitations

Real Time Delivery of the 278
This implementation guide requires the use of a separate 278 inquiry transaction (ST to SE) for each real time patient event inquiry or global inquiry as defined in 1.4.1.

If the UMO system cannot process the 278 inquiry transaction upon receipt, the UMO system must return a 278 inquiry response transaction to indicate the reason for rejecting the transaction.

Batch Delivery of the 278
In batch mode, the 278 inquiry transaction can include one or more patient event or global inquiries from the requester to the UMO. This implementation guide requires that the batch 278 inquiry transaction include no more than 99 patient event inquiries or 5 global inquiries per 278 inquiry transaction (ST to SE).


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

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

Figure 1.1. Health Care Services Review - Inquiry and Response

Health Care Services Review - Inquiry and Response

The following are examples of business events supported by this implementation. These events are all examples of inquiries to obtain complete referral or certification information for 278 service review requests previously processed.

Specialty Care Referral Inquiry
A specialist has not received a referral for a patient who has arrived for an appointment. The specialist sends a 278 inquiry to the UMO to verify that an approved referral exists for this patient. The UMO uses the 278 to transmit an inquiry response, listing one or more previous referral review decisions, back to the requesting provider. The health care provider can also use this inquiry when a patient is scheduled to arrive and the referral authorization information is not available.

Admission Certification Inquiry
A patient arrives or is scheduled to arrive for a hospital admission, and the pre-admission certification information previously requested from the UMO by the primary care provider (PCP) is not available. The provider uses the 278 inquiry to verify that the patient's primary care provider received certification for the admission. The UMO uses the 278 inquiry response to transmit any available admission certification information to the requesting provider.

Health Care Service Certification Inquiries
A patient is scheduled to receive a series of services or supplies; for example physical therapy and equipment for home exercises. The physical therapist has no certification information available and uses the 278 inquiry to verify that the services previously requested from the UMO by the PCP or specialist are authorized. The UMO returns the appropriate certification information in the 278 inquiry response.

All Patient Certifications Inquiry
The 278 inquiry enables the requester to determine the range of review activity associated with a specific patient to be included on the response. Some examples follow.

  • A provider inquires on all certifications (within a date range) for one patient from a utilization management organization. This implementation would typically be used when a PCP wants to see all review activity (within a date range) with a UMO for one of his patients.
  • A provider (such as a hospital, clinic, group practice, or physician) can inquire on all certifications from a UMO where the current requesting provider was the original requesting provider for a specific patient. If the inquiry does not specify a date range, the UMO might limit the number of certifications that qualify for inclusion in the response. For example, the UMO might limit the response to the five most recent certifications.
  • A provider inquires on all review activities (referrals and certifications) from a UMO where the current requesting provider is the patient event provider or service provider for a specific patient. Based on the review entity's rules, the provider may have authority to view only some of that activity.

NOTE:
Implementers of the 278 Inquiry and Response must establish response content criteria based on the identity of the requesting entity. For example, UMOs might limit the response to a specialist to those services that pertain to the specialist's treatment of the patient only and not return any additional authorization information associated with the patient event.

Multiple Patients Certification Inquiry
The 278 inquiry provides limited support for inquiring on multiple certifications for multiple patients. In this type of inquiry, the requester uses a single transaction to inquire on the status of authorizations for more than one patient. Three scenarios illustrating the use of the multiple patients inquiry follow.

  • A number of patients are scheduled for appointments with a specialist on a specific day. The specialist's office needs to determine if these patients have authorizations from the UMO for the specialist visit. The specialist's office submits a batch inquiry transaction, listing each of the patients scheduled. The inquiry must include the appropriate member ID information for each patient and the inquiring provider must be identified as the service provider (referred-toprovider) on the inquiry. Additional information, such as the service(s) to be performed, may help to limit the number of patient event authorizations returned per patient on the response.
  • A provider has submitted service review requests for several patients for which he has not received final responses. The provider inquires on the status of these requests. The provider submits a batch inquiry transaction listing each patient for which he has not received a final services review response. The inquiry must include the appropriate member ID information for each patient and the inquiring provider must be identified as the referring provider on the inquiry. Additional information, such as the date of the original request, may help to limit the number of patient event authorizations returned per patient on the response.
  • A primary care provider (PCP) has several patients for whom he tracks all authorizations initiated by himself or by specialists. The PCP inquires to determine if the UMO has authorized any service reviews for these patients. The provider submits a batch inquiry transaction listing each of the patients and can specify a certification effective date or issue date for each, if applicable. The inquiry must include the appropriate member ID information for each patient. Additional information, such as the patient diagnosis or service(s) to be performed, may help to limit the number of patient event authorizations returned per patient on the response.

Global Inquiry
The 278 inquiry also enables the requester to inquire on the status of authorizations that meet specific patient event or service criteria without identifying a specific patient. Inquiries of this type are denoted in the transaction with a BHT02 value of 51 (Historical Inquiry). A scenario illustrating the use of a global inquiry follows.

  • A provider has submitted service review requests for several patients for which he has not received final responses. The inquiry does not specify the name or member information for each patient. Instead, the provider inquires on the status of all the requests submitted on a specific date. The inquiry transaction identifies the inquiring provider as the referring provider and specifies the date when these initial service review requests were initiated.
    NOTE:
    For the UMO to respond to this type of inquiry, the UMO must provide other methods of access to authorizations on file in addition to access by member ID. Support at this level is at the discretion of the UMO. The UMO must authenticate that the provider initiating the inquiry has a relationship with this patient that authorizes the requester to receive this information.

1.4.2 Business Events Supported in Other 278 Guides

The 278 transaction set accommodates additional health care services review business events that are covered in separate 278 implementation guides. A brief description of these business events follows.


1.4.2.1 Notification

Trading partners can use the 278 transaction set to share unsolicited information with providers, payers, delegated UMO entities and/or other providers. This information may include 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 provider(s), service provider(s), or other Health Care entities requiring the information for specific purposes.

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

As illustrated in Figure 1.2, unsolicited information is sent from the information source to both the UMO and Service Provider. For example, in a situation where the primary care provider may 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, without the expectation of a response.

Figure 1.2 - Health Care Services Review - Notification

Health Care Services Review - Notification


1.4.2.2 Request and Response

Health Care Services Review - Request and Response includes the following business events.

  • admission certification review request and associated response
  • referral review request and associated response
  • health care services certification review request and associated response
  • extend certification review request and associated response
  • certification appeal review request and associated response
  • reservation of medical services request and associated response
  • cancellations of service reservations request and associated response

As illustrated in Figure 1.3, the exchange of information is between the primary parties, the provider and the UMO.

Figure 1.3 - Health Care Services Review - Request for Review and Response

Health Care Services Review - Request for Review and Response


1.5 Business Terminology

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

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

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.

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

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

Patient event provider
Patient event provider is the referred-to provider, specialist, specialty entity, group, or facility where the patient event will be performed.

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

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

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

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

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

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


1.6 Transaction Acknowledgments

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


1.6.1 997 Functional Acknowledgment

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

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

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

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


1.6.2 999 Implementation Acknowledgment

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

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


1.10.2 Implementation Migration Strategy

During the transition period (for example, the period from May 23, 2005 until the NPI compliance dates), it will be necessary to accommodate both the NPI and proprietary identifiers to identify health care providers in the same standard health care services review transaction. This will allow health care providers to demonstrate to their trading partners their NPIs in relation to their proprietary identifier(s). Health plans may attempt a match routine using the National 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.

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

Interested parties can exchange the 278 transaction in a bi-directional request/response mode of operation. In this implementation, a participant inquires on the status of authorizations and a review entity responds to that request. This section provides general information on the structure of the transaction set as represented in this implementation guide.

NOTE:
See Appendix B, Nomenclature, for a review of 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. Refer to Section 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. The value assigned to BHT02 in the header provides additional information about the business purpose of the transaction. A BHT02 value of 28 (Query) indicates an inquiry for authorizations for the patient( s) identified and a BHT02 value of 51 (Historical Inquiry) identifies a global inquiry for all authorizations on file that match the search criteria specified where that search criteria does not identify any specific patients.

A BHT02 value of 49 (Original — No Response Necessary) indicates a response to a patient inquiry and a value of 52 (Response to Historical Inquiry) indicates a response to a global inquiry.

This implementation uses the BHT06 to further qualify the business purpose of the transaction. BHT06, used in conjunction with BHT02, enables the trading partners to specify the amount of detail to exchange in global inquiries. A BHT06 value of RD (Returns Detail) on the inquiry indicates that the requester (or requesting system) can handle a response containing the full detail for the available records on the UMO system. A BHT06 value of ZW (Sort and Segregate Detail) indicates that the requester (or requesting system) prefers summary detail for the available records on the UMO system. The requester can use this, in combination with a global inquiry (BHT02 = 51), to indicate a preference for summary responses. This implementation guide does not require that UMO systems support the ability to return both summary and detail responses.

On the response, BHT06 provides information on the status of the response to the inquiry. A value of RD (Returns Detail) advises that the response contains detail information and a value of ZW advises that the response contains only summary information on the authorizations available in the UMO system. Depending on the detail provided on the inquiry, the UMO system may have a large number of records on file that match the query criteria. Some UMO systems have limitations on the number of authorizations returned per inquiry. The UMO system can use a response BHT06 value of RS (Response – Additional Responses Available) to indicate that more records qualified than the UMO system returned on the response.

Refer to Section 1.12.5 Summary Responses and Detail Responses for guidelines on the content of these responses.

The Detail level, Table 2, contains all the data relating to the transaction, including transaction participants, the patient, all providers, and services detail information. Table 2 uses a hierarchical data structure. For the types of business transactions that this implementation guide addresses, the following HL levels apply to both the inquiry and the response.

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

One Patient Per Transaction
The 278 supports multiple types of service review inquiries. The number of referrals and certifications that qualify for inclusion in the response will vary based on the criteria specified on the inquiry and the review entity's rules for relinquishing patient information to the requesting provider. An inquiry respecting a single patient can result in a response that contains multiple patient event loops, one for each patient event authorized. Each of these loops may contain one to many service loops depending on the complexity of services authorized. Due to the multiplicity of uses of the 278, this guide requires a separate transaction for each patient inquiry submitted in real-time mode.

Refer to "Multiple Patients Certification Inquiry" in Section 1.4.1 for scenarios that support multiple patients on the inquiry.

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 or information source) 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. The 278 supports multiple types of service review requests. Due to the multiplicity of uses of the 278, this guide requires that inquiries submitted in real-time mode use separate transaction sets for different patients and events. This is 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.

NOTE:
The inclusion of detailed service review information on the inquiry limits the authorizations that qualify for inclusion on the response.


1.11.2 Sample Table 2 Configurations

The following are sample Table 2 configurations.

The following example represents an inquiry for authorizations for a specific patient event, 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 an inquiry 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 an inquiry from a PCP to a UMO on all certifications for a patient who is the Subscriber.

UMO (Loop 2000A)

Requester (Loop 2000B) - PCP

Subscriber (Loop 2000C) - Patient

Patient Event (Loop 2000E) (Certification Search Criteria)

The following example represents a response (from a UMO to a PCP) to an inquiry on all authorizations (certifications) for a patient who is the Subscriber. The UMO system contains two certifications that match the query criteria.

UMO (Loop 2000A)

Requester (Loop 2000B) - PCP

Subscriber (Loop 2000C) - Patient

Patient Event (Loop 2000E)

Service (Loop 2000F) - Authorization 1

Patient Event (Loop 2000E)

Service (Loop 2000F) - Authorization 2

In the preceding example, the second patient event level is for a different episode of care and associated authorization.

NOTE:
The providers, including the original referring or ordering provider, 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.

Inquiry
For an inquiry transaction, matrix 1, Intended Segment Use for an Inquiry Transaction, identifies the intended segment use by hierarchical level.

Matrix 1. Intended Segment Use for an Inquiry 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 YESYESYESYES
0300AAA
0400UM YESYES
0500HCR YESYES
0600REF YESYES
0700DTP YESYES
0800HI YES
0810SV1 YES
0820SV2 YES
0830SV3 YES
0840TOO YES
0900HSD
1000CRC
1100CL1
1200CR1
1300CR2
1400CR5
1500CR6
1520CR7
1530CR8
1550PWK
1600MSG
1700NM1YESYESYESYESYESYES
1800REF YESYESYESYESYES
1900N2
2000N3 YES YESYES
2100N4 YES YESYES
2200PER YES
2300AAA
2400PRV YES YESYES
2500DMG YESYES
2600INS
2700DTP

Response
Matrix 2, Intended Segment Use for a Response Transaction, identifies the intended segment use by hierarchical level for an inquiry response transaction.

Matrix 2. Intended Segment Use for an Inquiry 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 YESYESYESYES
0300AAAYES YESYES
0400UM YESYES
0500HCR YESYES
0600REF YESYES
0700DTP YESYES
0800HI YES
0810SV1 YES
0820SV2 YES
0830SV3 YES
0840TOO YES
0900HSD YESYES
1000CRC
1100CL1 YES
1200CR1 YES
1300CR2 YES
1400CR5 YES
1500CR6 YES
1520CR7
1530CR8
1550PWK
1600MSG YESYES
1700NM1YESYESYESYESYESYES
1800REF YESYESYESYESYES
1900N2
2000N3 YESYESYESYES
2100N4 YESYESYESYES
2200PERYES YESYES
2300AAAYESYESYESYESYESYES
2400PRV YES YESYES
2500DMG YESYES
2600INS
2700DTP

1.11.4 Matching the Inquiry 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 inquiry. 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 response transactions that may not contain all of the HL Loops. BHT03 is required on both the inquiry and the response. When the 278 inquiry and response are used in real time mode, the receiver of the 278 inquiry (whether it is a clearinghouse or UMO) must return the inquiry BHT03 value in the 278 response BHT03.

In batch processing the responding system might not address each patient inquiry in the same batch response. Therefore, this implementation guide does not require the receiver of the request transaction to return the inquiry BHT03 value on the batch response. The responder can assign its own identifier to the transaction in BHT03.

TRN Segment
The TRN is supplied solely for the convenience of the organization that originated it. It enables the originator to assign a unique ID to each unique service review inquiry and identifies the organization that generated the inquiry. Both the requester (provider) and the clearinghouse can add a TRN segment to the inquiry. Each trace number provided in a TRN segment on the inquiry must be returned by the UMO in the TRN segment at the corresponding level of the response.

Loop 2000C (Subscriber level) and Loop 2000D (Dependent level) contain a TRN segment. This segment identifies the request at the patient level (Loop 2000C if the patient is the subscriber or the dependent with a unique member ID, or Loop 2000D if the dependent does not have a unique member ID). Loop 2000E (Patent Event level) and Loop 2000F (Service level) also contain a TRN segment. Use this TRN segment in lieu of the patient level TRN only when inquiring on certifications for more than one patient event (multiple patient event loops) or service (multiple service loops) for the same patient, or when submitting a global inquiry.

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

  • uniquely identify this service review inquiry or each query contained in the inquiry within the provider's environment
  • match the associated response to the inquiry
  • 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.

Clearinghouse TRN
If the transaction is routed through a clearinghouse, the clearinghouse can provide its own trace number in a separate TRN segment in Loop 2000C (Subscriber), Loop 2000D (Dependent), Loop 2000E (Patient Event), or Loop 2000F (Service) on the request to use for transaction tracking and matching purposes.

If the 278 inquiry 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 must 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.

UMO TRN
If the TRN segment is used on the inquiry, 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 in the same loop on the response. The UMO cannot use this trace number to identify the certification to the requester.


1.11.5 Inquiry Responses

The UMO must respond to each 278 transaction set received. If the UMO can process the 278 inquiry, the UMO must return a 278 response that contains either the authorization(s) found or the reason why no authorizations were found.

Patient Confidentiality
Inquiry responses may include authorizations that contain information concerning the patient's current condition and treatment. Implementers of the 278 inquiry and response must ensure that only authorized participants have access to this data. The UMO/responding entity should establish response content criteria based on the identity of the requesting entity. For example, UMOs might use the requesting provider's role in the care of the patient as criteria for determining what authorization information to return on the response. If the provider initiating the inquiry is the member's PCP, the UMO rules may permit the PCP to view all authorizations for that patient, regardless of what provider initiated the original service review request. These criteria must prevent the UMO's system from disseminating confidential patient information to providers not directly involved in the care of the patient.

Rejected Transactions
Missing or incorrect application data on the 278 inquiry can cause the UMO to reject the transaction. For these requests, the UMO must return a 278 inquiry 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 inquiry request for processing.


1.12 Data Use By Business Use

The segments referenced in Matrix 1 and Matrix 2 carry the data content of the health care services review. This section provides examples of the segments and data element values used in the hierarchical levels. The use of 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 authorization inquiries make it difficult to identify a single set of data elements that are required for all types of inquiries. 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 Section 2 of this guide for detailed information on valuing specific data elements within the segments.


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

The Loop 2000A and Loop 2000B hierarchical levels convey information about the primary participants in a health care service review transaction, the information source (UMO) and the information receiver (requester). Figure 1.4, UMO and Requester Levels, presents Loop 2000A and Loop 2000B.

Figure 1.4 - UMO and Requester Levels

UMO and Requester Levels

Hierarchy Usage Chart for Transaction Participants
Various utilization management entities may appear in either Loop 2000A or Loop 2000B depending on the transaction usage. Matrix 3, HL Information Sources and Receivers, has been included to better clarify the various entities involved in a health care services review inquiry. 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.

Matrix 3. HL Information Sources and Receivers

Transaction Use

HL

UMO

HL

Requester

Physical

Transmitter

Physical

Receiver

Specialist Inquiry on a Specialty Care Referral HMO SCP SCP HMO
Response to a Specialty Care Referral Inquiry HMO SCP HMO SCP
Hospital Inquiry on Admission Certification HMO HOSP HOSP HMO
Response to Admission Certification Inquiry HMO HOSP HMO HOSP
Specialist Inquiry on a Specialty Care Referral PCP SCP SCP PCP
Response to a Specialty Care Referral Inquiry PCP SCP PCP SCP

* UMO - Utilization Management Organization

* PCP - Primary Care Provider

* SCP - Specialty Care Provider

* HOSP - Hospital

* HMO - Health Maintenance Organization

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 inquiry and for whom the response decision is intended.

On the response, this loop is required if the UMO system processed any of the information contained in the corresponding Loop 2000B of the inquiry. The UMO system must return a response or error response containing this loop. If the UMO system was unable to process any data beyond Loop 2000A of the inquiry, then this Loop 2000B is not required.

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 valued when inquiring on certifications for a specific patient and not used on global inquiries. Loop 2000C is required on a response to a patient specific inquiry when that response does not report a reject reason in a AAA segment in Loop 2000A or Loop 2000B. It is also required on global inquiry responses that return information on authorizations that match the inquiry criteria. 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.

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

When the 278 inquiry and response transaction set is used in real time mode, it can contain only one patient request. When the 278 inquiry and response transaction set is used in batch mode, it can contain multiple patient requests. The required maximum is 99. Refer to Section 1.3.1 Batch and Real-time Usage for more information.

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

Figure 1.5 - Subscriber and Dependent Levels

Subscriber and Dependent Levels

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). When the subscriber is the patient or when 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:

Loop 2010C
Subscriber's Member ID

Loop 2010D
Patient's First Name
Patient's Last Name
Patient's 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*20021229~

Patient Account Number
The requester (provider) can supply the patient account number as a supplemental identifier for the patient on the inquiry. 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 inquiry response transaction.


1.12.3 Patient Event (Loop 2000E)

A 278 inquiry transaction must include criteria to indicate the type of service review authorization to search for in the UMO system. The Patient Event loop is required on global inquiries and either the Patient Event loop or the Service loop (Loop 2000F) is required on patient inquiries. The Loop 2000E hierarchical level identifies the patient event associated with this health care services review inquiry. It identifies the category of service on the original request and whether the patient event concerns a referral to a specialist, specialty treatment, or an admission to a facility.

Figure 1.6 - Patient Event Level

Patient Event Level

Patient Event Inquiry Search Criteria
The requester can narrow the search by including additional patient event level search criteria in the inquiry such as the following:

  • status of the service review decision
  • previous review authorization number
  • previous review administrative reference number
  • dates associated with the patient event or the certification period
  • diagnosis associated with the original health care services review request
  • providers or specialty entities associated with this patient event, including the original referring or ordering provider

If the requester needs to further qualify the inquiry to search for specific procedures to be performed, the requester must identify these procedures at the Service Level (Loop 2000F).

Patient Event Inquiry Response - Authorizations Found
The inquiry response indicates if any authorizations are on file that meet the specifications contained in the inquiry. If this is a response to a global inquiry and authorizations exist that match the patient event specified, the response identifies one to many patients (Loops 2000C/2000D), where each patient loop contains at least one subordinate Patient Event loop (2000E). If this is a response to a patient-specific patient event inquiry and authorizations exist, the response includes one to many Patient Event loops associated with that patient. Each Patient Event loop of the response identifies a different service review authorization and may have subordinate Service loops that identify the specific services associated with that patient event. The response indicates the level of approval and any additional information available respecting the details of the authorization.

Patient Event Inquiry Response - Data Error or No Authorizations Found
The AAA segment is used only on the response. If the UMO system was unable to process the inquiry due to missing or invalid application data at this level, the UMO must return a 278 inquiry response containing a AAA segment at this level.

The AAA segment serves two purposes. It identifies the primary error condition in the Patient Event level on the inquiry that prohibits processing of the original inquiry. Also, if no authorizations are on file that meet the criteria specified at the Patient Event level of the inquiry, the UMO system must return an AAA segment at this level of the response to indicate that no authorizations match the inquiry criteria specified.


1.12.3.1 Specialty Care Referral Inquiries

Health care service review requests originally submitted on a 278 request transaction must specify a request category. You can specify the same service review request category on the inquiry to limit the number of authorizations in the UMO system that qualify in the inquiry result.

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. A specialist (patient event or service provider) can use a specialty care referral inquiry to verify that a referral has been authorized for a specific patient. The original requesting provider can use the global inquiry to determine the status of all referral requests that the provider sent to the UMO previously. The requester can further qualify both patient specific and global inquiries with additional information on the specialist, specialty entity, or service type specified on the original request for referral.

The following example inquires on authorizations on file for a single office visit for a consultation at the provider's office.

Referral Inquiry

HL*4*3*EV*0~
UM*SC**3*11:B~

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

UM01 = SC (Specialty Care Review)
UM03 = 3 (Consultation)
UM04 = 11:B (Physician's Office)

Generally, referral inquires include additional patient event inquiry criteria such as identification information about the consulting physician or specialty and the proposed date of the event. If the inquiry concerns referrals for a specific patient, then the Patient Event loop follows a parent Patient loop (2000C/2000D).

Referral Inquiry Response
The following sections describe the segments, in addition to those included on the inquiry, that may appear at the Patient Event level in the referral inquiry response.

The following response identifies an approved specialty care referral.

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

Response Indicating Approval
The response includes the original service level details respecting the services requested. 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. 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 (Review Identification Number)

The UMO has authorized one visit (HSD*VS*1~).

Response Indicating Approval with Modification of Services
If the review entity approved the specialist visits specified on the original request but increased the number of visits to 4, the inquiry response would indicate this modification as follows:

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

The HCR value "A6" indicates a status of modified.

Response Indicating Denial of Services
Some UMO systems retain information on file about denials. Many do not. The following is an example of the information returned on the inquiry response if the review entity denied the original service review request.

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

The A3 value indicates "not certified." In this example, the UMO has also supplied a Decision Reason Code (0Y), "Service Inconsistent with Patient's Age". Depending on UMO policy, the UMO might also return an administrative reference number (REF segment where REF01 = NT) that the requester can use to reference the transaction at a later date.

Inquiry on 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, in a 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. The UMO authorizes treatment for 30 day intervals, one interval at a time. In the original request for a renewal, the requester references the previous certification identifier and assigns UM02 the value "R". An inquiry can contain criteria to inquire on the status of the request for renewal, as follows:

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

where UM02 = R (renewal) indicates that the requester wants to locate authorizations for renewal and REF01 = BB identifies AUT00001 as the previous review authorization number that was submitted on the request for renewal.


1.12.3.2 Health Services Review Inquiries

The term "health services review" identifies certifications for specific treatments or more extended care. Extended care refers to treatment for a condition requiring prolonged rehabilitation therapy. The requester can structure each inquiry to identify a certification related to a specific treatment, or extended care associated with a single patient event. If no specific dates are identified on the inquiry, multiple patient event certifications may be returned.

Health Service Review Inquiry
The UM segment identifies the type of health care services review inquiry. This limits the selection to only those certifications for the type of service specified. Use of this data element assumes that the original health care services review request specified the same service type. An example illustrating the use of UM03 to identify a service type follows.

UM*HS**6~

UM01 = HS (Health Services Review)
UM03 = 6 (Radiation Therapy)

Note that the original health care services review request might have specified a different service type or expressed the service as a specific procedure or set of procedures in the Service level segments of the original request. Use of this segment on the inquiry implies that only those certifications with an exact match on this value are returned by the UMO.

Health Service Review Inquiry Response
The uses of the Patient Event level on the health care services certification inquiry response are similar to those defined for the specialty care referral inquiry response with the exception of the following additional segments.

CR1, CR2, CR5, CR6 Segments
These segments provide more detailed information regarding ambulance, spinal manipulation, oxygen therapy, and home health care services. The inquiry response returns this information if it was submitted on the original health care services review request and is relevant to the certification information returned.

Inquiry Response for Spinal Manipulation Treatment
This is an example of a certification for spinal manipulation services (UM03 = 33) of the thoracic and lumbar section of the spine. It provides an example of the use of the CR2 segment. In this scenario, the UMO authorized 2 visits per week over a 3 month period. In addition, the certification specifies subluxation for Thoracic Eleven and Lumbar Five of the spine. In addition, the UMO might have authorized specific procedures in association with this treatment. The response returns procedure information at the Service level.

HL*4*3*EV*0~
UM*HS*I*33~
HCR*A1*00287654S~
HSD*VS*2*WK**34*3~
CR2***T11*L5~

The HSD Segment specifies the pattern of delivery for the authorized treatment. The spinal manipulation services 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 expresses the subluxation levels.
CR203 = T11 (Subluxation level code)
CR204 = L5 (Subluxation level code)


1.12.3.3 Admission Review Inquiries

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. Admission certification inquiries identify certifications for admission to a facility for treatment (pre-certification).

Admission Review Inquiry
The following example demonstrates an inquiry for authorizations for admission to a specific facility.

HL*4*3*EV*0~
UM*AR**2*21:B~
DTP*435*D8:20050820~
NM1*FA*2*ABC MEMORIAL HOSPITAL*****24*765432100~

The UM segment identifies the type of admission.
UM01 = AR (Admission Review)
UM03 = 2 (Surgical)
UM04 = 21:B (Hospital - Inpatient)

In this example, the additional elements clarify that the admission is for surgery that will take place in an inpatient setting. The NM1 segment identifies a specific facility as the provider of services for this patient event. The DTP identifies the date of admission.

NOTE:
Use the Service Level (Loop 2000F) to inquire on authorizations for specific surgical procedures associated with this admission.

Admission Review Inquiry Response
The uses of the Patient Event level on the admission certification inquiry response are similar to those defined for the specialty care referral inquiry response with the exception of the following additional segment.

CL1 Segment
The CL1 statement provides information on the type of institutional admission and the status of the patient. The inquiry response may provide this information if it was submitted in the original admission review request.


1.12.3.4 Search for All Certifications for a Patient

The requester can elect to omit the request category (UM segment) from the Patient Event level of the inquiry. A PCP could use this type of inquiry to access all review and certification activity for the patient identified at the Patient level (2000C/2000D), as qualified by any one of the Patient Event level dates (DTP segments). The responder can limit the number of certifications returned on the response. For example, the UMO system might restrict responses to include the most recent 10 certifications that meet the search criteria.

All Certifications for a Patient Inquiry
If the inquiry was limited to a specific health care service review request date range, the Patient Event level would include a DTP segment but no UM segment. For example:

HL*4*3*EV*0~
DTP*881*RD8*20050101-20050830~

All Certifications for a Patient Inquiry Response
The all certifications for a patient inquiry response uses are identical to those described for the other types of inquiries. However, multiple Patient Event and Service level combinations may be returned representing multiple certifications for multiple patient events respecting the one patient.


1.12.4 Services (Loop 2000F)

On the 278 inquiry, the requester can use the Service level (Loop 2000F) to inquire on authorizations associated with specific procedures identified by procedure code. The requester can also identify service dates and service providers associated with the delivery of those procedures. Even if the inquiry does not include Service level information, any inquiry response that returns information on authorizations found may return Service level information that provides the details on the services associated with the patient event authorized. Some UMOs assign authorization to each service and others authorize the entire patient event. If the UMO authorizes at the service level, then each Service loop on the response can contain an HCR segment to return a specific review outcome and authorization number for each service.

Figure 1.7 - Service Level

Figure 1.7 - Service Level

As illustrated in Matrix 1 and Matrix 2, many of the segments used in Loop 2000F are the same as those available in Loop 2000E. For a detailed explanation of their use, refer to Section 1.12.3 Patient Event.

Requesters can omit the Service level from the inquiry if they want to see all services associated with a patient event. On the inquiry response, the Service level can include all the pertinent information originally submitted as part of the original health care services review request.

Services Inquiry
The following demonstrates the Service level information for an inquiry for authorizations for a triple bypass venous graft. The inquiry has identified a specific patient in Loop 2000C and a patient event of admission review in Loop 2000E.

HL*5*4*SS*0~
SV2**HC:33510~

The SV2 segment specifies the CPT code for a triple bypass venous graft.

The UMO returns additional detail on the authorized service as follows:

HL*5*4*SS*0~

This HL is subordinate to HL*4, the parent HL (which contains Patient Event information). This HL code is SS, identifying the service. This HL has no subordinate levels, or children.

UM*HS**2~

This service review is for surgery.

HCR*A1*AUTH0002~

The UMO has approved the surgery in full and assigned it a separate certification number, AUTH0002.

DTP*472*D8*20050924~

The requested date for the surgery is September 24, 2005

SV2**HC:33510~

The surgeon will perform a triple bypass venous graft

NM1*72*1*Watson*Susan****

34*987654321~

Dr. Watson is the surgeon

PRV*PE*203BS0133X~

Dr. Watson's specialty is thoracic cardiovascular surgery.

On the 278 inquiry response, the Service level (Loop 2000F) conveys the outcome of the service review decisions previously made about the patient for the period or services specified on the inquiry or as supported by the UMO.


1.12.5 Summary Responses and Detail Responses

Section 1.10.1 Overall Data Architecture describes the BHT06 values used to indicate if the response provides summary level or detail information on the authorizations found in the UMO system. Different UMOs may retain and return different levels of detail data related to the authorizaton. Use the situational rules in Section 2 to determine the specific data fields that the UMO can return on a detail response.

Patient Event level summary responses should return enough information to enable the recipient to send a follow up inquiry for additional detail. Minimum information for an authorized patient event must identify the patient, patient event category (UM01), authorization status (HCR01) and certification number (HCR02), and a Patient Event level date if one has been assigned. This enables the requester to submit a follow-up inquiry using the patient identification information, request category, and previous review authorization number (REF) to request the details associated with the authorization.

Service level summary responses must return any summary information about the Patient Event in addition to the summary information associated with this service. Summary service authorization information must specify the procedure authorized and can include the authorization status (HCR01), certification number (HCR02), and service date. The requester can use the certification number returned at the Service level, or the certification number returned at the Patient Event level along with the procedure code, to send a follow-up inquiry to access details about the procedure authorized.


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 Inquiry / Response sequence between a Specialist and a Utilization Management Organization. The example demonstrates how a specialist can inquire on referrals on file with the UMO for a specific patient. The example shows the associated response. Joe Smith, a subscriber to Maryland Capital Insurance Company, has scheduled an appointment with Dr. Susan Watson, a cardiologist, for a consultation. Dr. Watson's staff initiates an inquiry to determine if a certification is on file for Joe's scheduled visit. The UMO responds with the appropriate authorization information.


3.1.1 Inquiry Request

The following example represents the inquiry from Dr. Susan Watson to Maryland Capital Insurance Company for an authorization on Joe Smith for consultation with Dr. Watson.

Table 1

ST*278*0001*005010X215~

Begin transaction set 278, control #0001, implementation convention reference 005010X215.

BHT*0007*28*B67890*20050809*1101*RD~

This transaction is a query on authorizations for a specific patient (BHT02 = 28) using hierarchical structure 0078 (information source, information receiver, subscriber, dependent, event, services). The originating system has assigned the Submitter Transaction Identifier "B67890" along with the transaction set creation date and time. The information receiver indicates a preference for a response with full detail for the available records on the UMO system based on the search criteria provided.

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~

Dr. Watson has directed the inquiry to Maryland Capital Insurance Company. The company's Electronic Transmitter Identification Number is 789312.

Loop 2000B hierarchical level identifies the inquiring entity.

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

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

Susan Watson is the inquiring entity. Her Social Security Number is 987654321.

PER*IC**TE*4029993456~

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

PRV*CO*PXC*203BS0126Y~

Susan Watson has indicated her current role in the care of the patient as consulting physician and her specialty as thoracic cardiovascular surgery.

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. there is no dependent in this example, there is no Loop 2000D.

Loop 2000E hierarchical level identifies the patient event. Loop 2000E repeats for each 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*20050809*9012345678~

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

UM*SC**3*11:B~

Dr. Watson is inquiring on authorizations for an office consult (3*11:B)

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

Dr. Watson has further limited the search to only those authorizations where the patient event provider is identified as Susan Watson. Her Social Security Number is 987654321.

SE*15*0001~

Number of segments, control number.


3.1.2 Response to the Inquiry

The following example represents the response from Maryland Capital Insurance to the inquiry made by Dr. Susan Watson. In this case Maryland Capital Insurance has found an authorization on file that indicates a referral to Dr. Watson for a consult for the patient, Joe Smith.

The response transaction provides the detail of the authorization to identify what Maryland Capital Insurance has approved and includes the certification number (AUTH0001) assigned to this authorization by Maryland Capital Insurance. The DTP segment specifies the time period during which the referral for this service/ consult is valid.

Table 1

ST*278*0001*005010X215~

Begin transaction set 278, control #0001, implementation convention reference 005010X215.

BHT*0007*49*B67890*20050809*1112*RD~

This transaction is a response using hierarchical structure 0083 (information source, information receiver, subscriber, dependent, event, services). A BHT02 value of "49" indicates that this is a response to a patient inquiry The UMO's system returns the Submitter Transaction Identifier "B67890". The BHT06 value of "RD" indicates that this a response containing authorization detail.

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~

This is a response from Maryland Capital Insurance Company. Their Electronic Transmitter Identification Number is 789312.

Loop 2000B hierarchical level identifies the entity that submitted the inquiry.

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

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

Susan Watson is the inquiring entity. Her 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. Loop 2000E repeats for each 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*20050809*9012345678~

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

TRN*2*20050809*9012345678~

The responder must return the trace number passed on the inquiry to enable the requester to link this response to the original inquiry.

UM*SC**3*11:B~

The UMO has authorized an office consult.

HCR*A1*AUTH0001~

Maryland Capital provides the certification number associated with this referral authorization. Susan Watson can use this number in any follow-up with the UMO related to this consultation.

DTP*AAH*RD8*20050901-20050930~

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

HSD*VS*1~

The UMO has authorized a single visit for Joe Smith with Dr. Watson.

NM1*1P*1*GARDENER*JAMES****34*8189991234~

Dr. James Gardner was the original referring provider.

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

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

SE*17*0001~

Number of segments, control number.


3.2 Business Scenario 2 - Admission Inquiry

During the consultation examination, Dr. Watson determined that Joe's diagnosis, acute myocardial infarction, required hospitalization and a surgical procedure, a triple bypass venous graft. Dr. Watson submitted a request for review seeking approval to perform the surgery. She requested that the operation and recovery occur at Montgomery Hospital. Maryland Capital approved the request.

Joe Smith calls Montgomery Hospital to schedule his pre-admission tests. The Montgomery Hospital pre-admission staff send an inquiry to Maryland Capital to determine if an admission has been authorized for Joe Smith.


3.2.1 Inquiry Request

The following example represents the inquiry from Montgomery Hospital to Maryland Capital Insurance Company for an authorization for admission to Montgomery Hospital for Joe Smith.

Table 1

ST*278*0001*005010X215~

Begin transaction set 278, control #0001, implementation convention reference 005010X215.

BHT*0007*28*MHA54321*20050908*0625*RD~

This transaction is a query on authorizations for a specific patient (BHT02 = 28) using hierarchical structure 0078 (information source, information receiver, subscriber, dependent, event, services). The originating system has assigned the Submitter Transaction Identifier "MHA54321" along with the transaction set creation date and time. The information receiver indicates a preference for a response with full detail for the available records on the UMO system based on the search criteria provided.

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~

Dr. Watson has directed the inquiry to Maryland Capital Insurance Company. The company's Electronic Transmitter Identification Number is 789312.

Loop 2000B hierarchical level identifies the inquiring entity.

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

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

The inquiring provider, the hospital, is identified as Montgomery Hospital. The Employer's Identification Number is 000012121.

Loop 2000C 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. Loop 2000E repeats for each patient event. This loop is optional.

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*MHA20050908*9MHA45678~

The requester assigned the trace number MHA20050908 to the Patient Event level of the inquiry. The requester has included the user-assigned identifier of MHA45678 to this trace number.

UM*AR~

Montgomery Hospital inquires on authorizations for admission for Joe Smith.

DTP*435*D8*20050917~

The hospital has further narrowed the inquiry criteria to include only authorizations for admission with an admit date (435) of September 17, 2005.

SE*13*0001~

Number of segments, control number.


3.2.2 Response to the Inquiry

The following example represents the response from the Maryland Capital Insurance Company to Montgomery Hospital's inquiry on the existence of an authorization for admission to Montgomery Hospital for Joe Smith. Maryland Capital Insurance Company responds with information on the authorization for admission and the surgery included in that authorization.

Table 1

ST*278*0001*005010X215~

Begin transaction set 278, control #0001, implementation convention reference 005010X215.

BHT*0007*49*MHA54321*20050908*0633*RD~

The transaction uses the hierarchal structure information source, information receiver, subscriber, dependent, event, services (0007) and is a response to a specific patient inquiry (49). The system that created the original inquiry assigned the reference identification value of "MHA54321" that is being returned in this transaction. The date and time for the creation of the transaction set is followed by the transaction type indicating a response with full detail (RD).

Loop 2000A hierarchical level identifies the information source for the response.

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 Information Source is an UMO (X3) non-person entity (2) by the name of Maryland Capital Insurance Company with an ETIN (46) identification value of 789312.

Loop 2000B hierarchical level identifies the information receiver for the response.

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

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

The information receiver is a Facility (FA) non-person entity (2) by the name of Montgomery Hospital with an Employer's Identification number of 000012121.

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. Loop 2000E repeats for each patient event. This loop is optional.

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*MHA20050908*9MHA45678~

The UMO returns the trace number assigned by the requester.

UM*AR**2*21:B~

The UMO system has found a matching authorization for surgery in a hospital inpatient setting.

HCR*A6*AUTH0002~

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

DTP*435*D8*20050917~

The hospital has further narrowed the inquiry criteria to include only authorizations for admission with an admit date (435) of September 17, 2005.

HI*BF:41090:D8:20090809~

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

HSD*DY*5~

Maryland Capital has approved a length of stay of five days.

NM1*FA*2*Montgomery Hospital*****24*000012121~

The authorized admitting facility is identified as Montgomery Hospital.

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 authorized for this hospital admission.

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**2~

The admission includes health services authorization for surgery.

DTP*472*D8*20050918~

The proposed surgery date is September 18, 2005.

SV2**HC:33510~

The surgical procedure authorized is a triple bypass venous graft.

NM1*SJ*1*Watson*Susan****34*987654321~

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

PRV*PE*203BS0133X~

Dr. Watson's specialty is thoracic cardiovascular surgery.

SE*25*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.

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.

896 International Classification of Diseases, 10th Revision, Procedure Coding System (ICD-10-PCS)

SIMPLE DATA ELEMENT/CODE REFERENCES

235/IP, 1270/BBQ, 1270/BBR

SOURCE

International Classification of Diseases, 10th Revision, Procedure Coding System (ICD-10-PCS)

AVAILABLE FROM

CMM, HAPG, Division of Acute Care
Centers for Medicare and Medicaid Services
7500 Security Boulevard
Baltimore, MD 21244

ABSTRACT

The International Classification of Diseases, 10th Revision, Procedure Coding System (ICD-10-PCS), describes the classification of inpatient procedures for statistical purposes and for the indexing of healthcare records by procedures.

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

SIMPLE DATA ELEMENT/CODE REFERENCES

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

SOURCE

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

AVAILABLE FROM

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

ABSTRACT

The International 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.

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 the X12N implementation 005010X215 of the Health Care Services Review - Inquiry and Response (278). It is based on version/ release/sub-release 005010 of the ASC X12 standards. This new guide has a new format, in accordance with version 5010 of the X12N Implementation Guide Handbook.

The previous X12N implementation guide of the Health Care Services Review - Inquiry and Response was 004010X059. It was based on version/release/sub-release 004010 of the ASC X12 standards.

As reflected in this new guide, the structure of both the detail in 278 standard transaction and this implementation have changed. The major structural changes, as reflected in X215, are as follows:

  • Subscriber and Dependent Levels - Loop 2000C and Loop 2000D
    The Subscriber and Dependent levels now provide information for Subscriber/Dependent identification, address and demographic information only. Any segments associated with patient condition information, such as a diagnosis, or an associated date are now reported at the Patient Event level.
  • Patient Event Level - Loop 2000E
    X215 can support multiple patient events for the same patient. Loop 2000E (formerly the Referring Provider loop) now represents the patient event. Loop 2010E (Patient Event Provider) identifies any providers associated with the patient event, including the referring provider and the performing provider. In addition to the patient condition segments formerly associated with the Subscriber and Dependent levels, Loop 2000E includes segments from the X059 Service level (Loop 2000G) that identify a category of service.
  • Service Level - Loop 2000F
    X215 combines Service Provider and Service level information from Loops 2000F and G of X059 into a single Service level, Loop 2000F. This new Service level uses the SV1 Professional Service, SV2 Institutional Service, and SV3 Dental Service segments to carry detailed information on services and procedures. Loop 2010F enables you to identify the provider(s) associated with specific service or procedure.

In addition, the X215 Beginning of Hierarchical Transaction (BHT) supports additional values to differentiate inquiries about specific patients from global inquiries. It also enables the requester to indicate a preference for a summary response or a detail response. It also enables the responder to indicate if the response contains summary or detail authorization information.

This appendix provides a summary of the changes between 004010X059 and 005010X215.


Appendix D.1 Change Descriptions

Front Matter

The ASC X12 005010X215 Health Care Services Review - Inquiry and Response (X215) implementation guide contains significant changes from the ASC X12 004010X059 (X059) implementation guide. Section 1 through Section 2.3 comprise the front matter and are new. They replace Section 1 to Section 3.2 of X059. These new sections provide detailed information on the 5010 structure and composition.

Please review these sections, along with the inquiry and response implementation summaries in Sections 2.3.1and 2.5.1, and X12 standard summaries in Sections 2.3.2 and 2.5.2 respectively, for an overview of the scope of these changes.

Segment Detail

The following two sections, Health Care Services Review Inquiry, and Health Care Services Review Inquiry Response, list the segment detail changes from Section 3 of ASC X12N 004010X094 to Sections 2.4 and 2.6 of ASC X12N 005010X215. The noted changes may report changes in the segments including changes to the data elements, notes, number of repeats, and usage requirements. This change summary does not itemize the following overall changes at the segment or data element level in this change summary.

  1. All segment and data element situational usage notes are revised in accordance with version 5010 of the X12N Implementation Guide Handbook.
  2. Segment examples are updated to reflect changes in usage at the data element level and to update any date values.
  3. Data element Implementation Names are updated, where applicable.
  4. Object descriptors (OD) have been assigned at every level of the X12N implementation.
  5. Segment Identifiers, the acronym that represents the segment name in the X12 standard, have been added to the titles.

Health Care Services Review Inquiry

Header - Changed

  1. ST - Transaction Set Header
    • ST03 - Implementation Convention Reference - added with usage Required
  2. BHT - Beginning of Hierarchical Transaction
    • BHT01 Hierarchical Structure Code - value changed to 0007
    • BHT02 Transaction Set Purpose Code - added code 51, Historical Inquiry
    • BHT06 Transaction Type Code- change usage to Situational, added codes
      RD, Returns Detail
      ZW, Sort and Segregate Detail

Loop 2000A - Changed

  1. NM1 - UTILIZATION MANAGEMENT ORGANIZATION (UMO) NAME
    • NM101 Entity Identifier Code - added codes
      1P Provider
      2B Third-Party Administrator
      36 Employer
      PR Payer

Loop 2000B - Changed

  1. NM1 - REQUESTER NAME
    • NM101 Entity Identifier Code - added codes
      2A Federal, State, County or City Facility
      2B Third-Party Administrator
      36 Employer
      PR Payer
      X3 Utilization Management Organization
      Deleted code TV Third Party Administrator (TPA)
  2. REF - REQUESTER SUPPLEMENTAL IDENTIFICATION
    • Loop repeat increased to 9
    • REF01 Reference Identification Qualifier - added code G5 Provider Site Number, deleted code CT Contract Number
  3. N4 - REQUESTER CITY/STATE/ZIP CODE
    • N401 City Name - usage changed to Required
  4. PER - REQUESTER CONTACT INFORMATION
    • PER03 Communication Number Qualifier - usage changed to Required, added code UR Uniform Resource Locator (URL)
    • PER04 Communication Number - usage changed to Required
    • PER05 Communication Number Qualifier - added code UR Uniform Resource Locator (URL)
    • PER07 Communication Number Qualifier - added code UR Uniform Resource Locator (URL)
  5. PRV - REQUESTER PROVIDER INFORMATION
    • PRV02 Reference Identification Qualifier - usage changed to Situational, added code PXC Health Care Provider Taxonomy Code, deleted code ZZ Mutually Defined
    • PRV03 Reference Identification - usage changed to Situational

Loop 2000C - Changed

  1. SUBSCRIBER DIAGNOSIS - deleted this segment
  2. NM1 - SUBSCRIBER NAME
    • NM108 Identification Code Qualifier - removed code ZZ Mutually Defined, added code II Standard Unique Health Identifier for each Individual in the United States
  3. REF - SUBSCRIBER SUPPLEMENTAL IDENTIFICATION
    • REF01 Reference Identification Qualifier - added codes 3L Branch Identifier, DP Department Number, deleted codes 1W Member Identification Number, A6 Employee Identification Number
  4. DMG - SUBSCRIBER DEMOGRAPHIC INFORMATION
    • DMG03 Gender Code - changed usage to Not Used

Loop 2000D - Changed

  1. DEPENDENT DIAGNOSIS - deleted this segment
  2. REF - DEPENDENT SUPPLEMENTAL IDENTIFICATION
    • REF01 Reference Identification Qualifier - deleted code A6 Employee Identification Number, added code 28 Employee Identification Number
  3. DMG - DEPENDENT DEMOGRAPHIC INFORMATION
    • DMG03 Gender Code - changed usage to Not Used
  4. DEPENDENT RELATIONSHIP - deleted this segment

Loop 2000E - Replaced

  1. REFERRING PROVIDER LEVEL - deleted this segment
  2. REFERRING PROVIDER NAME - deleted this segment
  3. REFERRING PROVIDER SUPPLEMENTAL IDENTIFICATION - deleted this segment
  4. REFERRING PROVIDER ADDRESS - deleted this segment
  5. REFERRING PROVIDER CITY/STATE/ZIPCODE - deleted this segment
  6. REFERRING PROVIDER INFORMATION - deleted this segment
  7. HL - PATIENT EVENT LEVEL - added this segment. Refer to Section 2.4 for details.
  8. TRN - PATIENT EVENT TRACKING NUMBER - added this segment. Refer to Section 2.4 for details.
  9. UM - HEALTH CARE SERVICES REVIEW INFORMATION - added this segment. Refer to Section 2.4 for details.
  10. HCR - HEALTH CARE SERVICES REVIEW - added this segment. Refer to Section 2.4 for details.
  11. REF - PREVIOUS REVIEW AUTHORIZATION NUMBER - added this segment. Refer to Section 2.4 for details.
  12. REF - PREVIOUS REVIEW ADMINISTRATIVE REFERENCE NUMBER - added this segment. Refer to Section 2.4 for details.
  13. DTP - ACCIDENT DATE - added this segment. Refer to Section 2.4 for details.
  14. DTP - EVENT DATE - added this segment. Refer to Section 2.4 for details.
  15. DTP - ADMISSION DATE - added this segment. Refer to Section 2.4 for details.
  16. DTP - DISCHARGE DATE - added this segment. Refer to Section 2.4 for details.
  17. DTP - CERTIFICATION ISSUE DATE - added this segment. Refer to Section 2.4 for details.
  18. DTP - CERTIFICATION EXPIRATION DATE - added this segment. Refer to Section 2.4 for details.
  19. DTP - CERTIFICATION EFFECTIVE DATE - added this segment. Refer to Section 2.4 for details.
  20. DTP - HEALTH CARE SERVICES REVIEW REQUEST DATE - added this segment. Refer to Section 2.4 for details.
  21. HI - PATIENT DIAGNOSIS - added this segment with support of only one diagnosis code per patient event inquiry.
  22. NM1 - PATIENT EVENT PROVIDER NAME - added this segment. Refer to Section 2.4 for details.
  23. REF - PATIENT EVENT PROVIDER SUPPLEMENTAL INFORMATION - added this segment. Refer to Section 2.4 for details.
  24. N3 - PATIENT EVENT PROVIDER ADDRESS - added this segment. Refer to Section 2.4 for details.
  25. N4 - PATIENT EVENT PROVIDER CITY/STATE/ZIP CODE - added this segment. Refer to Section 2.4 for details.
  26. PRV - PATIENT EVENT PROVIDER INFORMATION - added this segment. Refer to Section 2.4 for details.

Loop 2000F - Replaced

  1. SERVICE PROVIDER LEVEL - deleted this segment
  2. SERVICE PROVIDER NAME - deleted this segment
  3. SERVICE PROVIDER SUPPLEMENTAL IDENTIFICATION - deleted this segment
  4. SERVICE PROVIDER ADDRESS - deleted this segment
  5. SERVICE PROVIDER CITY/STATE/ZIPCODE - deleted this segment
  6. SERVICE PROVIDER INFORMATION - deleted this segment
  7. HL - SERVICE LEVEL - added this segment. Refer to Section 2.4 for details.
  8. TRN - SERVICE TRACE NUMBER - added this segment. Refer to Section 2.4 for details.
  9. UM - HEALTH CARE SERVICE REVIEW INFORMATION - added this segment. Refer to Section 2.4 for details.
  10. HCR - HEALTH CARE SERVICES REVIEW - added this segment. Refer to Section 2.4 for details.
  11. REF - PREVIOUS REVIEW AUTHORIZATION NUMBER - added this segment. Refer to Section 2.4 for details.
  12. REF - PREVIOUS REVIEW ADMINISTRATIVE REFERENCE NUMBER - added this segment. Refer to Section 2.4 for details.
  13. DTP - SERVICE DATE - added this segment. Refer to Section 2.4 for details.
  14. DTP - CERTIFICATION ISSUE DATE - added this segment. Refer to Section 2.4 for details.
  15. DTP - CERTIFICATION EXPIRATION DATE - added this segment. Refer to Section 2.4 for details.
  16. DTP - CERTIFICATION EFFECTIVE DATE - added this segment. Refer to Section 2.4 for details.
  17. SV1 - PROFESSIONAL SERVICE - added this segment. Refer to Section 2.4 for details.
  18. SV2 - INSTITUTIONAL SERVICE - added this segment. Refer to Section 2.4 for details.
  19. SV3 - DENTAL SERVICE - added this segment. Refer to Section 2.4 for details.
  20. TOO - TOOTH INFORMATION - added this segment. Refer to Section 2.4 for details.
  21. NM1 - SERVICE PROVIDER NAME - added this segment. Refer to Section 2.4 for details.
  22. REF - SERVICE PROVIDER SUPPLEMENTAL IDENTIFICATION - added this segment. Refer to Section 2.4 for details.
  23. N3 - SERVICE PROVIDER ADDRESS - added this segment. Refer to Section 2.4 for details.
  24. N4 - SERVICE PROVIDER CITY/STATE/ZIP CODE - added this segment. Refer to Section 2.4 for details.
  25. PRV - SERVICE PROVIDER INFORMATION - added this segment. Refer to Section 2.4 for details.

Loop 2000G - Deleted

  1. SERVICE LEVEL - deleted this segment
  2. SERVICE TRACE NUMBER - deleted this segment
  3. HEALTH CARE SERVICES REVIEW INFORMATION - deleted this segment
  4. HEALTH CARE SERVICES REVIEW - deleted this segment
  5. PREVIOUS CERTIFICATION IDENTIFICATION - deleted this segment
  6. SERVICE DATE - deleted this segment
  7. ADMISSION DATE - deleted this segment
  8. SURGERY DATE - deleted this segment
  9. CERTIFICATION ISSUE DATE - deleted this segment
  10. CERTIFICATION EXPIRATION DATE - deleted this segment
  11. CERTIFICATION EFFECTIVE DATE - deleted this segment
  12. HEALTH CARE SERVICES REVIEW REQUEST DATE - deleted this segment
  13. PROCEDURES - deleted this segment

Health Care Services Review Inquiry Response

Header - Changed

  1. ST - Transaction Set Header
    • ST03 - Implementation Convention Reference - added with usage Required
  2. BHT - Beginning of Hierarchical Transaction
    • BHT06 Transaction Type code - change usage to Required, added codes
      RS Response - Additional Response(s) Available
      ZW Sort and Segregate Detail

Loop 2000A - Changed

  1. NM1 - UTILIZATION MANAGEMENT ORGANIZATION (UMO) NAME
    • NM101 Entity Identifier Code - added codes
      1P Provider
      2B Third-Party Administrator
      36 Employer
      PR Payer
  2. PER - UTILIZATION MANAGEMENT ORGANIZATION (UMO) CONTACT INFORMATION
    • PER03 Communication Number Qualifier - usage changed to Required, added code UR Uniform Resource Locator (URL)
    • PER04 Communication Number - usage changed to Required
    • PER05 Communication Number Qualifier - added code UR Uniform Resource Locator (URL)
    • PER07 Communication Number Qualifier - added code UR Uniform Resource Locator (URL)
  3. AAA - UTILIZATION MANAGEMENT ORGANIZATION (UMO) REQUEST VALIDATION (2010A)
    • AAA03 Reject Reason Code - deleted code 41 Authorization/Access Restrictions, added code ZZ Mutually Defined to indicate that the UMO system does not support the response type specified in BHT06 of the inquiry or cannot process the inquiry in real-time.

Loop 2000B - Changed

  1. NM1 - REQUESTER NAME
    • NM101 Entity Identifier Code - added codes
      2A Federal, State, County or City Facility
      2B Third-Party Administrator
      36 Employer
      X3 Utilization Management Organization
      Deleted code TV Third Party Administrator (TPA)
  2. REF - REQUESTER SUPPLEMENTAL IDENTIFICATION
    • Loop repeat increased to 9
    • REF01 Reference Identification Qualifier - added code G5 Provider Site Number, deleted code CT Contract Number
  3. AAA - REQUESTER REQUEST VALIDATION
    • AAA03 Reject Reason Code - added codes
      15 Required application data missing
      IP Inappropriate Provider Role
      Deleted code 04 Authorization Quantity Exceeded
    • AAA04 - usage changed to Required
  4. PRV - REQUESTER PROVIDER INFORMATION
    • PRV02 Reference Identification Qualifier - usage changed to Situational, added code PXC Health Care Provider Taxonomy Code, deleted code ZZ Mutually Defined
    • PRV03 Reference Identification - usage changed to Situational

Loop 2000C - Changed

  1. SUBSCRIBER REQUEST VALIDATION (2000C) - deleted this segment
  2. ACCIDENT DATE - deleted this segment
  3. LAST MENSTRUAL PERIOD DATE - deleted this segment
  4. ESTIMATED DATE OF BIRTH - deleted this segment
  5. ONSET OF CURRENT SYMPTOMS OR ILLNESS DATE - deleted this segment
  6. SUBSCRIBER DIAGNOSIS - deleted this segment
  7. NM1 - SUBSCRIBER NAME
    • NM106 Name Prefix - changed usage to Situational
    • NM108 Identification Code Qualifier - deleted code ZZ Mutually Defined, added code II Standard Unique Health Identifier for each Individual in the United States
  8. REF - SUBSCRIBER SUPPLEMENTAL IDENTIFICATION
    • REF01 Reference Identification Qualifier - added codes 3L Branch Identifier, DP Department Number, deleted codes 1W Member Identification Number, A6 Employee Identification Number
  9. N3 - SUBSCRIBER MAILING ADDRESS - added this segment. Refer to Section 2.6 for details.
  10. N4 - SUBSCRIBER MAILING CITY/STATE/ZIP CODE - added this segment. Refer to Section 2.6 for details.
  11. AAA - SUBSCRIBER REQUEST VALIDATION (2010C)
    • AAA03 Reject Reason Code - changed usage to Required, deleted codes 04 Authorized Quantity Exceeded, 15 Required application data missing, 74 Invalid/Missing Subscriber/Insured Gender Code, 89 No Prior Approval, added code 95 Patient Not Eligible
    • AAA04 Follow-up Action Code - changed usage to Required, deleted code S Do Not Resubmit; Inquiry Initiated to a Third Party
  12. DMG - SUBSCRIBER DEMOGRAPHIC INFORMATION
    • DMG03 Gender Code - changed usage to Not Used

Loop 2000D - Changed

  1. DEPENDENT REQUEST VALIDATION (2000D) - deleted this segment
  2. ACCIDENT DATE - deleted this segment
  3. LAST MENSTRUAL PERIOD DATE - deleted this segment
  4. ESTIMATED DATE OF BIRTH - deleted this segment
  5. ONSET OF CURRENT SYMPTOMS OR ILLNESS DATE - deleted this segment
  6. DEPENDENT DIAGNOSIS - deleted this segment
  7. NM1 - DEPENDENT NAME
    • NM108 Identification Code Qualifier - removed code ZZ Mutually Defined, added code II Standard Unique Health Identifier for each Individual in the United States
  8. REF - DEPENDENT SUPPLEMENTAL IDENTIFICATION
    • REF01 Reference Identification Qualifier - deleted code A6 Employee Identification Number, added code 28 Employee Identification Number
  9. N3 - DEPENDENT MAILING ADDRESS - added this segment. Refer to Section 2.6 for details.
  10. N4 - DEPENDENT MAILING CITY/STATE/ZIP CODE - added this segment. Refer to Section 2.6 for details.
  11. AAA - DEPENDENT REQUEST VALIDATION (2010D)
    • AAA03 Reject Reason Code - changed usage to Required, deleted codes 04 Authorized Quantity Exceeded, 15 Required application data missing, 33 Input Errors, 66 Invalid/Missing Patient Gender Code, 89 No Prior Approval, added code 95 Patient Not Eligible
    • AAA04 Follow-up Action Code - changed usage to Required, deleted code S Do Not Resubmit; Inquiry Initiated to a Third Party
  12. DMG - DEPENDENT DEMOGRAPHIC INFORMATION
    • DMG03 Gender Code - changed usage to Not Used
  13. DEPENDENT RELATIONSHIP - deleted this segment

Loop 2000E - Replaced

  1. REFERRING PROVIDER LEVEL - deleted this segment
  2. REFERRING PROVIDER NAME - deleted this segment
  3. REFERRING PROVIDER SUPPLEMENTAL IDENTIFICATION - deleted this segment
  4. REFERRING PROVIDER ADDRESS - deleted this segment
  5. REFERRING PROVIDER CITY/STATE/ZIP CODE - deleted this segment
  6. REFERRING PROVIDER CONTACT INFORMATION - deleted this segment
  7. REFERRING PROVIDER REQUEST VALIDATION - deleted this segment
  8. REFERRING PROVIDER INFORMATION - deleted this segment
  9. HL - PATIENT EVENT LEVEL - added this segment. Refer to Section 2.6 for details.
  10. TRN - PATIENT EVENT TRACKING NUMBER - added this segment. Refer to Section 2.6 for details.
  11. AAA - PATIENT EVENT REQUEST VALIDATION (2000E) - added this segment. Refer to Section 2.6 for details.
  12. UM - HEALTH CARE SERVICES REVIEW INFORMATION - added this segment. Refer to Section 2.6 for details.
  13. HCR - HEALTH CARE SERVICES REVIEW - added this segment. Refer to Section 2.6 for details.
  14. REF - PREVIOUS REVIEW AUTHORIZATION NUMBER - added this segment. Refer to Section 2.6 for details.
  15. REF - PREVIOUS REVIEW ADMINISTRATIVE REFERENCE NUMBER - added this segment. Refer to Section 2.6 for details.
  16. DTP - EVENT DATE - added this segment. Refer to Section 2.6 for details.
  17. DTP - ADMISSION DATE - added this segment. Refer to Section 2.6 for details.
  18. DTP - DISCHARGE DATE - added this segment. Refer to Section 2.6 for details.
  19. DTP - CERTIFICATION ISSUE DATE - added this segment. Refer to Section 2.6 for details.
  20. DTP - CERTIFICATION EXPIRATION DATE - added this segment. Refer to Section 2.6 for details.
  21. DTP - CERTIFICATION EFFECTIVE DATE - added this segment. Refer to Section 2.6 for details.
  22. DTP - HEALTH CARE SERVICES REVIEW REQUEST DATE - added this segment. Refer to Section 2.6 for details.
  23. HI - PATIENT DIAGNOSIS - added this segment with support of only one diagnosis code per patient event inquiry.
  24. HSD - HEALTH CARE SERVICES DELIVERY - added this segment. Refer to Section 2.6 for details.
  25. CL1 - INSTITUTIONAL CLAIM CODE - added this segment. Refer to Section 2.6 for details.
  26. CR1 - AMBULANCE TRANSPORT INFORMATION - added this segment. Refer to Section 2.6 for details.
  27. CR2 - SPINAL MANIPULATION SERVICE INFORMATION - added this segment. Refer to Section 2.6 for details.
  28. CR5 - HOME OXYGEN THERAPY INFORMATION - added this segment. Refer to Section 2.6 for details.
  29. CR6 - HOME HEALTH CARE INFORMATION - added this segment. Refer to Section 2.6 for details.
  30. MSG - MESSAGE TEXT - added this segment. Refer to Section 2.6 for details.
  31. NM1 - PATIENT EVENT PROVIDER NAME - added this segment. Refer to Section 2.6 for details.
  32. REF - PATIENT EVENT PROVIDER SUPPLEMENTAL INFORMATION - added this segment. Refer to Section 2.6 for details.
  33. N3 - PATIENT EVENT PROVIDER ADDRESS - added this segment. Refer to Section 2.6 for details.
  34. N4 - PATIENT EVENT PROVIDER CITY/STATE/ZIP CODE - added this segment. Refer to Section 2.6 for details.
  35. PER - PATIENT EVENT PROVIDER CONTACT INFORMATION - added this segment. Refer to Section 2.6 for details.
  36. AAA - PATIENT EVENT PROVIDER REQUEST VALIDATION (2010EA) - added this segment. Refer to Section 2.6 for details.
  37. PRV - PATIENT EVENT PROVIDER INFORMATION - added this segment. Refer to Section 2.6 for details.
  38. NM1 - PATIENT EVENT TRANSPORT INFORMATION - added this segment. Refer to Section 2.6 for details.
  39. N3 - PATIENT EVENT TRANSPORT LOCATION ADDRESS - added this segment. Refer to Section 2.6 for details.
  40. N4 - PATIENT EVENT TRANSPORT LOCATION CITY/STATE/ZIP CODE - added this segment. Refer to Section 2.6 for details.

Loop 2000F - Replaced

  1. SERVICE PROVIDER LEVEL - deleted this segment
  2. MESSAGE TEXT - deleted this segment
  3. SERVICE PROVIDER NAME - deleted this segment
  4. SERVICE PROVIDER SUPPLEMENTAL IDENTIFICATION - deleted this segment
  5. SERVICE PROVIDER ADDRESS - deleted this segment
  6. SERVICE PROVIDER CITY/STATE/ZIP CODE - deleted this segment
  7. SERVICE PROVIDER CONTACT INFORMATION - deleted this segment
  8. SERVICE PROVIDER REQUEST VALIDATION - deleted this segment
  9. SERVICE PROVIDER INFORMATION - deleted this segment
  10. HL - SERVICE LEVEL - added this segment. Refer to Section 2.6 for details.
  11. TRN - SERVICE TRACE NUMBER - added this segment. Refer to Section 2.6 for details.
  12. AAA - SERVICE REQUEST VALIDATION (2000F) - added this segment. Refer to Section 2.6 for details.
  13. UM - HEALTH CARE SERVICE REVIEW INFORMATION - added this segment. Refer to Section 2.6 for details.
  14. HCR - HEALTH CARE SERVICES REVIEW - added this segment. Refer to Section 2.6 for details.
  15. REF - PREVIOUS REVIEW AUTHORIZATION NUMBER - added this segment. Refer to Section 2.6 for details.
  16. REF - PREVIOUS REVIEW ADMINISTRATIVE REFERENCE NUMBER - added this segment. Refer to Section 2.6 for details.
  17. DTP - SERVICE DATE - added this segment. Refer to Section 2.6 for details.
  18. DTP - CERTIFICATION ISSUE DATE - added this segment. Refer to Section 2.6 for details.
  19. DTP - CERTIFICATION EXPIRATION DATE - added this segment. Refer to Section 2.6 for details.
  20. DTP - CERTIFICATION EFFECTIVE DATE - added this segment. Refer to Section 2.6 for details.
  21. SV1 - PROFESSIONAL SERVICE - added this segment. Refer to Section 2.6 for details.
  22. SV2 - INSTITUTIONAL SERVICE - added this segment. Refer to Section 2.6 for details.
  23. SV3 - DENTAL SERVICE - added this segment. Refer to Section 2.6 for details.
  24. TOO - TOOTH INFORMATION - added this segment. Refer to Section 2.6 for details.
  25. HSD - HEALTH CARE SERVICES REVIEW DELIVERY - added this segment. Refer to Section 2.6 for details.
  26. MSG - MESSAGE TEXT - added this segment. Refer to Section 2.6 for details.
  27. NM1 - SERVICE PROVIDER NAME - added this segment. Refer to Section 2.6 for details.
  28. REF - SERVICE PROVIDER SUPPLEMENTAL IDENTIFICATION - added this segment. Refer to Section 2.6 for details.
  29. N3 - SERVICE PROVIDER ADDRESS - added this segment. Refer to Section 2.6 for details.
  30. N4 - SERVICE PROVIDER CITY/STATE/ZIP CODE - added this segment. Refer to Section 2.6 for details.
  31. PER - SERVICE PROVIDER CONTACT INFORMATION - added this segment. Refer to Section 2.6 for details.
  32. AAA - SERVICE PROVIDER REQUEST VALIDATION (2010F) - added this segment. Refer to Section 2.6 for details.
  33. PRV - SERVICE PROVIDER INFORMATION - added this segment. Refer to Section 2.6 for details.

Loop 2000G - Deleted

  1. SERVICE LEVEL - deleted this segment
  2. SERVICE TRACE NUMBER - deleted this segment
  3. SERVICE REQUEST VALIDATION (2000G) - deleted this segment
  4. HEALTH CARE SERVICES REVIEW INFORMATION - deleted this segment
  5. HEALTH CARE SERVICES REVIEW - deleted this segment
  6. PREVIOUS CERTIFICATION IDENTIFICATION - deleted this segment
  7. SERVICE DATE - deleted this segment
  8. ADMISSION DATE - deleted this segment
  9. DISCHARGE DATE - deleted this segment
  10. SURGERY DATE - deleted this segment
  11. CERTIFICATION ISSUE DATE - deleted this segment
  12. CERTIFICATION EXPIRATION DATE - deleted this segment
  13. CERTIFICATION EFFECTIVE DATE - deleted this segment
  14. HEALTH CARE SERVICES REVIEW REQUEST DATE - deleted this segment
  15. PROCEDURES - deleted this segment
  16. HEALTH CARE SERVICES DELIVERY - deleted this segment
  17. INSTITUTIONAL CLAIM CODE - deleted this segment
  18. AMBULANCE TRANSPORT INFORMATION - deleted this segment
  19. SPINAL MANIPULATION SERVICE INFORMATION - deleted this segment
  20. HOME OXYGEN THERAPY INFORMATION - deleted this segment
  21. HOME HEALTH CARE INFORMATION - deleted this segment
  22. MESSAGE TEXT - deleted this segment

EDI Transmission Examples

Section 4 EDI Transmission Examples for Different Business Uses from 004010X059 is completely replaced in 00510X215 with the new Section 3 EDI Transmission Examples for Different Business Uses. This new section contains new examples that illustrate the use of the new structure and composition of the segment detail.

Appendices

The Appendices have been reorganized and 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 - Inquiry
D | 2000E | DTP03 | - | 1251

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

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

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

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

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 - Inquiry
D | 2000E | DTP03 | - | 1251
D | 2000F | DTP03 | - | 1251
278 - Health Care Services 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 - Inquiry
D | 2000E | DTP03 | - | 1251
D | 2000F | DTP03 | - | 1251
278 - Health Care Services 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 - Inquiry
D | 2000E | DTP03 | - | 1251
D | 2000F | DTP03 | - | 1251
278 - Health Care Services Review - Response
D | 2000E | DTP03 | - | 1251
D | 2000F | DTP03 | - | 1251

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

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

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

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

Country Code
Code indicating the geographic location.
278 - Health Care Services Review - Inquiry
D | 2010B | N404 | - | 26
D | 2010EA | N404 | - | 26
D | 2010F | N404 | - | 26
278 - Health Care Services Review - Response
D | 2010C | N404 | - | 26
D | 2010D | N404 | - | 26
D | 2010EA | N404 | - | 26
D | 2010F | N404 | - | 26

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

Daily Oxygen Use Count
Number of times per day that the patient must use oxygen.
278 - Health Care Services Review - 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 - Inquiry
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 | 2000F | DTP02 | - | 1250
D | 2000F | DTP02 | - | 1250
D | 2000F | DTP02 | - | 1250
D | 2000F | DTP02 | - | 1250
278 - Health Care Services 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 | 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 - Inquiry
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
278 - Health Care Services 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 | 2000F | DTP01 | - | 374
D | 2000F | DTP01 | - | 374
D | 2000F | DTP01 | - | 374
D | 2000F | DTP01 | - | 374

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

Dependent Address Line
The street address of the patient.
278 - Health Care Services 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 - Inquiry
D | 2010D | DMG02 | - | 1251
278 - Health Care Services Review - Response
D | 2010D | DMG02 | - | 1251

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

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

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

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

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

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

Dependent State Code
The state postal code of the dependent.
278 - Health Care Services 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 - Inquiry
D | 2010D | REF02 | - | 127
278 - Health Care Services Review - Response
D | 2010D | REF02 | - | 127

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

Diagnosis Code
An ICD-9-CM Diagnosis Code identifying a diagnosed medical condition.
278 - Health Care Services Review - Inquiry
D | 2000E | HI01 | C022-02 | 1271
278 - Health Care Services Review - Response
D | 2000E | HI01 | C022-02 | 1271

Diagnosis Type Code
Code identifying the type of diagnosis.
278 - Health Care Services Review - Inquiry
D | 2000E | HI01 | C022-01 | 1270
278 - Health Care Services Review - Response
D | 2000E | HI01 | 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 - Response
D | 2000F | SV111 | - | 1073

Entity Identifier Code
Code identifying an organizational entity, a physical location, property or an individual.
278 - Health Care Services Review - Inquiry
D | 2010A | NM101 | - | 98
D | 2010B | NM101 | - | 98
D | 2010C | NM101 | - | 98
D | 2010D | NM101 | - | 98
D | 2010EA | NM101 | - | 98
D | 2010F | NM101 | - | 98
278 - Health Care Services 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 | 2010F | NM101 | - | 98

Entity Type Qualifier
Code qualifying the type of entity.
278 - Health Care Services Review - Inquiry
D | 2010A | NM102 | - | 1065
D | 2010B | NM102 | - | 1065
D | 2010C | NM102 | - | 1065
D | 2010D | NM102 | - | 1065
D | 2010EA | NM102 | - | 1065
D | 2010F | NM102 | - | 1065
278 - Health Care Services 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 | 2010F | NM102 | - | 1065

Facility Code Qualifier
Code identifying the type of facility referenced.
278 - Health Care Services Review - Inquiry
D | 2000E | UM04 | C023-02 | 1332
D | 2000F | UM04 | C023-02 | 1332
278 - Health Care Services 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 - Inquiry
D | 2000E | UM04 | C023-01 | 1331
D | 2000F | UM04 | C023-01 | 1331
278 - Health Care Services 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 - 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 | 2000F | AAA04 | - | 889
D | 2010F | AAA04 | - | 889

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

Health Care Services Review Request Date
Date when the health care service review was requested.
278 - Health Care Services Review - Inquiry
D | 2000E | DTP03 | - | 1251
278 - Health Care Services Review - Response
D | 2000E | DTP03 | - | 1251

Hierarchical Child Code
Code indicating if there are hierarchical child data segments subordinate to the level being described.
278 - Health Care Services Review - Inquiry
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 - 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 - Inquiry
D | 2000A | HL01 | - | 628
D | 2000B | HL01 | - | 628
D | 2000C | HL01 | - | 628
D | 2000D | HL01 | - | 628
D | 2000E | HL02 | - | 734
D | 2000F | HL02 | - | 734
278 - Health Care Services 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 - Inquiry
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 - 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 - Inquiry
D | 2000B | HL02 | - | 734
D | 2000C | HL02 | - | 734
D | 2000D | HL02 | - | 734
D | 2000E | HL01 | - | 628
D | 2000F | HL01 | - | 628
278 - Health Care Services 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 - Inquiry
H | | BHT01 | - | 1005
278 - Health Care Services 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 - 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 - 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 - Inquiry
D | 2010A | NM108 | - | 66
D | 2010B | NM108 | - | 66
D | 2010C | NM108 | - | 66
D | 2010EA | NM108 | - | 66
D | 2010F | NM108 | - | 66
278 - Health Care Services Review - Response
D | 2010A | NM108 | - | 66
D | 2010B | NM108 | - | 66
D | 2010C | NM108 | - | 66
D | 2010D | NM108 | - | 66
D | 2010EA | NM108 | - | 66
D | 2010F | NM108 | - | 66

Implementation Convention Reference
Reference assigned to identify Implementation Convention.
278 - Health Care Services Review - Inquiry
H | | ST03 | - | 1705
278 - Health Care Services Review - Response
H | | ST03 | - | 1705

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

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

Oral Cavity Designation Code
Code identifying an oral cavity involved in the service.
278 - Health Care Services Review - Inquiry
D | 2000F | SV304 | C006-01 | 1361
278 - Health Care Services 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

Oxygen Delivery System Code
Code to indicate if a particular form of delivery was prescribed.
278 - Health Care Services 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 - 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 - Response
D | 2000E | CR506 | - | 380

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

Patient Event Provider Address Line
Address line in the mailing address of the provider to whom the patient has been or will be referred for this patient event.
278 - Health Care Services Review - Inquiry
D | 2010EA | N301 | - | 166
D | 2010EA | N302 | - | 166
278 - Health Care Services 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 - Inquiry
D | 2010EA | N401 | - | 19
278 - Health Care Services 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 - 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 - 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 - Inquiry
D | 2010EA | NM104 | - | 1036
278 - Health Care Services 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 - Inquiry
D | 2010EA | NM109 | - | 67
278 - Health Care Services 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 - Inquiry
D | 2010EA | NM103 | - | 1035
278 - Health Care Services 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 - Inquiry
D | 2010EA | NM105 | - | 1037
278 - Health Care Services 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 - Inquiry
D | 2010EA | NM106 | - | 1038
278 - Health Care Services 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 - Inquiry
D | 2010EA | NM107 | - | 1039
278 - Health Care Services 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 - Inquiry
D | 2010EA | N403 | - | 116
278 - Health Care Services Review - Response
D | 2010EA | N403 | - | 116

Patient Event Provider State or Province Code
Code indicating the state or province in the mailing address of the provider to whom the patient has been or will be referred for the patient event.
278 - Health Care Services Review - Inquiry
D | 2010EA | N402 | - | 156
278 - Health Care Services 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 - Inquiry
D | 2010EA | REF02 | - | 127
278 - Health Care Services 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 - Inquiry
D | 2000E | TRN02 | - | 127
278 - Health Care Services 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 - Response
D | 2010EB | N301 | - | 166
D | 2010EB | 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 - Response
D | 2010EB | N401 | - | 19

Patient Event Transport Location Name
Name of location for which the patient is being transported.
278 - Health Care Services Review - Response
D | 2010EB | 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 - Response
D | 2010EB | 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 - Response
D | 2010EB | N402 | - | 156

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

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

Portable Oxygen System Flow Rate
Oxygen flow rate for a portable oxygen system in liters per minute.
278 - Health Care Services Review - 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 - Inquiry
D | 2000E | REF02 | - | 127
D | 2000F | REF02 | - | 127
278 - Health Care Services Review - Response
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 - Inquiry
D | 2000E | REF02 | - | 127
D | 2000F | REF02 | - | 127
278 - Health Care Services Review - Response
D | 2000E | REF02 | - | 127
D | 2000F | REF02 | - | 127

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

Procedure Code Description
Description clarifying the Product/Service Procedure Code and related data elements.
278 - Health Care Services Review - 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 - 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
Identifying number for a product or service.
278 - Health Care Services Review - Inquiry
D | 2000F | SV101 | C003-08 | 234
D | 2000F | SV202 | C003-08 | 234
D | 2000F | SV301 | C003-08 | 234
278 - Health Care Services Review - Response
D | 2000F | SV101 | C003-08 | 234
D | 2000F | SV202 | C003-08 | 234
D | 2000F | SV301 | C003-08 | 234

Product or Service ID Qualifier
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
278 - Health Care Services Review - Inquiry
D | 2000F | SV101 | C003-01 | 235
D | 2000F | SV202 | C003-01 | 235
D | 2000F | SV301 | C003-01 | 235
278 - Health Care Services 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 - 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 - Inquiry
D | 2000E | DTP03 | - | 1251
278 - Health Care Services 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 - Inquiry
D | 2000E | DTP03 | - | 1251
278 - Health Care Services Review - Response
D | 2000E | DTP03 | - | 1251

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

Proposed or Actual Service Date
Requested or actual date of service.
278 - Health Care Services Review - Inquiry
D | 2000F | DTP03 | - | 1251
278 - Health Care Services 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 - Inquiry
D | 2000F | SV305 | - | 1358
278 - Health Care Services Review - Response
D | 2000F | SV305 | - | 1358

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

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

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

Reference Identification Qualifier
Code qualifying the reference identification.
278 - Health Care Services Review - Inquiry
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 | 2010F | REF01 | - | 128
D | 2010F | PRV02 | - | 128
278 - Health Care Services 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 | 2010F | REF01 | - | 128
D | 2010F | PRV02 | - | 128

Reject Reason Code
Code assigned by issuer to identify reason for rejection.
278 - Health Care Services 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 | 2000F | AAA03 | - | 901
D | 2010F | AAA03 | - | 901

Request Category Code
Code indicating a type of request.
278 - Health Care Services Review - Inquiry
D | 2000E | UM01 | - | 1525
D | 2000F | UM01 | - | 1525
278 - Health Care Services 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 - Inquiry
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 - Inquiry
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 - Inquiry
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 - Inquiry
D | 2010B | PER02 | - | 93

Requester First Name
First name of the requester of a health care services review.
278 - Health Care Services Review - Inquiry
D | 2010B | NM104 | - | 1036
278 - Health Care Services 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 - Inquiry
D | 2010B | NM109 | - | 67
278 - Health Care Services 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 - Inquiry
D | 2010B | NM103 | - | 1035
278 - Health Care Services 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 - Inquiry
D | 2010B | NM105 | - | 1037
278 - Health Care Services 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 - Inquiry
D | 2010B | NM107 | - | 1039
278 - Health Care Services 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 - Inquiry
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 - Inquiry
D | 2010B | N402 | - | 156

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

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

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

Sample Selection Modulus
To specify the sampling frequency in terms of a modulus of the Unit of Measure, e.g., every fifth bag, every 1.5 minutes.
278 - Health Care Services Review - 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 - Response
D | 2000E | HCR04 | - | 1073
D | 2000F | HCR04 | - | 1073

Service Line Amount
Charges related to this service.
278 - Health Care Services 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 - Response
D | 2000F | SV206 | - | 1371

Service Line Revenue Code
UB92 Revenue Code pertaining to the service line.
278 - Health Care Services Review - Inquiry
D | 2000F | SV201 | - | 234
278 - Health Care Services 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 - Inquiry
D | 2010F | N301 | - | 166
D | 2010F | N302 | - | 166
278 - Health Care Services Review - Response
D | 2010F | N301 | - | 166
D | 2010F | N302 | - | 166

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Subluxation Level Code
Code identifying the specific level of subluxation.
278 - Health Care Services 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 - Inquiry
H | | BHT03 | - | 127
278 - Health Care Services 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 - 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 - Inquiry
D | 2010C | DMG02 | - | 1251
278 - Health Care Services 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 - 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 - Inquiry
D | 2010C | NM104 | - | 1036
278 - Health Care Services Review - Response
D | 2010C | NM104 | - | 1036

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

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

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

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

Subscriber 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 - Inquiry
D | 2000C | TRN02 | - | 127
278 - Health Care Services Review - Response
D | 2000C | TRN02 | - | 127

Time Period Qualifier
Code defining the type of time period.
278 - Health Care Services 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 - Inquiry
D | 2000F | TOO02 | - | 1271
278 - Health Care Services 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 - Inquiry
D | 2000F | TOO03 | C005-01 | 1369
278 - Health Care Services 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 - Inquiry
D | 2000C | TRN04 | - | 127
D | 2000D | TRN04 | - | 127
D | 2000E | TRN04 | - | 127
D | 2000F | TRN04 | - | 127
278 - Health Care Services Review - Response
D | 2000C | TRN04 | - | 127
D | 2000D | TRN04 | - | 127
D | 2000E | TRN04 | - | 127
D | 2000F | TRN04 | - | 127

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

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

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

Transaction Set Control Number
The unique identification number within a transaction set.
278 - Health Care Services Review - Inquiry
H | | ST02 | - | 329
D | | SE02 | - | 329
278 - Health Care Services 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 - Inquiry
H | | BHT04 | - | 373
278 - Health Care Services Review - Response
H | | BHT04 | - | 373

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

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

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

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

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

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

Treatment Series Number
Number this treatment is in the series of services.
278 - Health Care Services 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 - Inquiry
D | 2000F | SV103 | - | 355
D | 2000F | SV204 | - | 355
278 - Health Care Services 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 - 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 - 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 - Inquiry
D | 2010A | NM104 | - | 1036
278 - Health Care Services Review - Response
D | 2010A | NM104 | - | 1036

Utilization Management Organization (UMO) Identifier
Code uniquely identifying the Utilization Management Organization (UMO).
278 - Health Care Services Review - Inquiry
D | 2010A | NM109 | - | 67
278 - Health Care Services 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 - Inquiry
D | 2010A | NM103 | - | 1035
278 - Health Care Services 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 - Inquiry
D | 2010A | NM105 | - | 1037
278 - Health Care Services 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 - Inquiry
D | 2010A | NM107 | - | 1039
278 - Health Care Services 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 - Response
D | 2010B | AAA01 | - | 1073
D | 2010C | AAA01 | - | 1073
D | 2010D | AAA01 | - | 1073
D | 2000E | AAA01 | - | 1073
D | 2010EA | AAA01 | - | 1073
D | 2000F | AAA01 | - | 1073
D | 2010F | AAA01 | - | 1073

Yes No Condition or Response Code
Code indicating a Yes or No condition or response.
278 - Health Care Services Review - Response
D | 2000A | AAA01 | - | 1073
D | 2010A | AAA01 | - | 1073

Appendix F. FHIR Claim Inquiry to X12 278 Inquiry

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 Inquiry elements and the associated X12 278 Inquiry 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 Inquiry 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 populated during the transformation between the PAS Claim Inquiry profile and X12 278. Implement with version: STU 1.0.0R
ST03'005010X215' Implement with version: STU 1.0.0R
BHTThe data elements in this segment are defined in the PAS Claim Inquiry 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'28' Because FHIR requires a patient to be present in the inquiry resource, can only query against a single patient. 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 Inquiry profile because BHT02 will always be '28'. Implement with version: STU 1.0.0S
HL - 2000AThe data elements in this segment are not defined in the PAS Claim Inquiry 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 Inquiry profile. Implement with version: STU 1.0.0S
NM105This data element is not defined in the PAS Claim Inquiry profile. Implement with version: STU 1.0.0S
NM107This data element is not defined in the PAS Claim Inquiry 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 Inquiry 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 Inquiry profile. Implement with version: STU 1.0.0S
NM105This data element is not defined in the PAS Claim Inquiry profile. Implement with version: STU 1.0.0S
NM107This data element is not defined in the PAS Claim Inquiry profile. Implement with version: STU 1.0.0S
NM108'XX' Implement with version: STU 1.0.0R
NM109When Organization.identifier[n].system = 'http://hl7.org/fhir/sid/us-npi' move Organization.identifier[n].value to NM109 Implement with version: STU 1.2.0R
REF - 2010BThe data elements in this segment are not defined in the PAS Claim Inquiry profile. Implement with version: STU 1.0.0S
N3 - 2010BThe data elements in this segment are defined in the PAS Claim Inquiry profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.2.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 Inquiry 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
N407Organization.address[0].district Implement with version: STU 1.2.0S
PER - 2010BThe data elements in this segment are defined in the PAS Claim Inquiry 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.text Implement with version: STU 1.2.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.0R
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, remove the extension part of the phone number and place in PER06 and set PER05 to 'EX' Implement with version: STU 1.2.0R
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 extracted value for the extension from PER04 Otherwise refer to PER04 for rules on formatting Implement with version: STU 1.2.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 extracted value for the extension from PER06 Otherwise refer to PER04 for rules on formatting Implement with version: STU 1.2.0S
PRV - 2010BThe data elements in this segment are not defined in the PAS Claim Inquiry profile. Implement with version: STU 1.0.0S
HL - 2000CThe data elements in this segment are not defined in the PAS Claim Inquiry profile because the values are hardcoded or derived. Implement with version: STU 1.0.0S
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
TRN - 2000CThe data elements in this segment are not defined in the PAS Claim Inquiry profile. Implement with version: STU 1.1.0S
NM1 - 2010CClaim.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 Inquiry profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.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.2.0R
REF02Patient.identifier[1].value Implement with version: STU 1.0.0R
DMG - 2010CThe data elements in this segment are defined in the PAS Claim Inquiry 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
HL - 2000DThe data elements in this segment are not defined in the PAS Claim profile because the values are hardcoded or derived. 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.2.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
TRN - 2000DThe data elements in this segment are not defined in the PAS Claim Inquiry profile. Implement with version: STU 1.1.0S
NM1 - 2010DClaim.patient => Patient Locate the Patient Resource in the Bundle referenced in the Claim.patient attribute. Use the Patient Resource for all of the segments of the 2010D Loop 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.2.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 Inquiry profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
REF01Patient.identifier[0].type.coding[0].code Translated as follows: 'EI' -> '28' 'EJ' -> 'EJ' 'SB' -> 'SY' Implement with version: STU 1.2.0R
REF02Patient.identifier[0].value Implement with version: STU 1.0.0R
DMG - 2010DThe data elements in this segment are defined in the PAS Claim Inquiry 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
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.2.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'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 Inquiry 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.2.0S
UM - 2000EThe data elements in this segment are not defined in the PAS Claim Inquiry profile. Implement with version: STU 1.0.0S
HCR - 2000EThe data elements in this segment are not defined in the PAS Claim Inquiry profile. Implement with version: STU 1.0.0S
REF - 2000ENot Used on PAS Claim Inquiry profile on FHIR Claim Implement with version: STU 1.0.0S
REF - 2000ENot Used on PAS Claim Inquiry profile on FHIR Claim Implement with version: STU 1.0.0S
DTP - 2000EThe data elements in this segment are defined in the PAS Claim Inquiry 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 - 2000EAn 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.2.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 '«value of timingPeriod.start»-«value of timingPeriod.end»' Implement with version: STU 1.2.0R
DTP - 2000EAn Admission Date DTP segment is created when the Claim has a supportingInfo attribute for a 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' The date format in FHIR for this element is YYYY-MM-DD and will need to be converted. Implement with version: STU 1.2.0S
DTP01'435' Implement with version: STU 1.0.0R
DTP02'D8' or 'RD8' If the AdmissionDates has an attribute named 'timingDate' set DTP02 to 'D8' Otherwise set DTP02 to 'RD8' Implement with version: STU 1.2.0R
DTP03Claim.supportingInfo(AdmissionDates).timingDate | Claim.supportingInfo(AdmissionDates).timingPeriod If the supportingInfo[n] has the attribute timingDate set DTP03 to the value of timingDate Otherwise set DTP03 to '«value of timingPeriod.start»-«value of timingPeriod.end»' The date format in FHIR for this element is YYYY-MM-DD and will need to be converted. Implement with version: STU 1.2.0R
DTP - 2000EAn 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' The date format in FHIR for this element is CCYY-MM-DD and will need to be converted. Implement with version: STU 1.2.0S
DTP01'096' Implement with version: STU 1.0.0R
DTP02'D8' or 'RD8' If the DischargeDates has an attribute named 'timingDate' set DTP02 to 'D8' Otherwise set DTP02 to 'RD8' Implement with version: STU 1.2.0R
DTP03Claim.supportingInfo(DischargeDates).timingDate | Claim.supportingInfo(DischargeDates).timingPeriod If the supportingInfo[n] has the attribute timingDate set DTP03 to the value of timingDate Otherwise set DTP03 to '«value of timingPeriod.start»-«value of timingPeriod.end»' The date format in FHIR for this element is YYYY-MM-DD and will need to be converted. Implement with version: STU 1.2.0R
DTP - 2000EA DTP (Certification Issue Date) segment is created in the 2000E loop when Claim.item[0].productOrService.coding[0].code is No Value Implement with version: STU 1.2.0S
DTP01'102' Implement with version: STU 1.0.0R
DTP02'D8' or 'RD8' If the itemCertificationIssueDate has an attribute named 'valueDate' set DTP02 to 'D8' Otherwise set DTP02 to 'RD8' Implement with version: STU 1.2.0R
DTP03Claim.item[0].extension(itemCertificationIssueDate).valueDate | Claim.item[0].extension(itemCertificationIssueDate).valuePeriod If the Claim.item[0] has the attribute valueDate set DTP03 to the value of valueDate Otherwise set DTP03 to '«value of valuePeriod.start»-«value of valuePeriod.end»' The date format in FHIR for this element is YYYY-MM-DD and will need to be converted. Implement with version: STU 1.2.0R
DTP - 2000EA DTP (Certification Expiration Date) segment is created in the 2000E loop when Claim.item[0].productOrService.coding[0].code is No Value Implement with version: STU 1.2.0S
DTP01'36' Implement with version: STU 1.0.0R
DTP02'D8' or 'RD8' If the itemCertificationExpirationDate has an attribute named 'valueDate' set DTP02 to 'D8' Otherwise set DTP02 to 'RD8' Implement with version: STU 1.2.0R
DTP03Claim.item[0].extension(itemCertificationExpirationDate).valueDate | Claim.item[0].extension(itemCertificationExpirationDate).valuePeriod If the Claim.item[0] has the attribute valueDate set DTP03 to the value of valueDate Otherwise set DTP03 to '«value of valuePeriod.start»-«value of valuePeriod.end»' The date format in FHIR for this element is YYYY-MM-DD and will need to be converted. Implement with version: STU 1.2.0R
DTP - 2000EA DTP (Certification Effective Date) segment is created in the 2000E loop when Claim.item[0].productOrService.coding[0].code is No Value Implement with version: STU 1.2.0S
DTP01'007' Implement with version: STU 1.0.0R
DTP02'D8' or 'RD8' If the itemCertificationEffectiveDate has an attribute named 'valueDate' set DTP02 to 'D8' Otherwise set DTP02 to 'RD8' Implement with version: STU 1.2.0R
DTP03Claim.item[0].extension(itemCertificationEffectiveDate).valueDate | Claim.item[0].extension(itemCertificationEffectiveDate).valuePeriod If the Claim.item[0] has the attribute valueDate set DTP03 to the value of valueDate Otherwise set DTP03 to '«value of valuePeriod.start»-«value of valuePeriod.end»' The date format in FHIR for this element is YYYY-MM-DD and will need to be converted. Implement with version: STU 1.2.0R
DTP - 2000EThe data elements in this segment are not defined in the PAS Claim Inquiry profile. Implement with version: STU 1.0.0S
HI - 2000EThe data elements in this segment are defined in the PAS Claim Inquiry 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
NM1 - 2010EAThe data elements in this segment are defined in the PAS Claim Inquiry 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.2.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.2.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' 'UPIN' -> '1G' 'FI' -> '1J' 'EN' -> 'EI' 'G5' -> 'G5' 'N5' -> 'N5' 'N7' -> 'N7' 'SB' -> 'SY' 'ZH' -> 'ZH' Implement with version: STU 1.2.0R
REF02Practitioner.identifier[1].value | Organization.identifier[1].value Implement with version: STU 1.0.0R
REF03Practitioner.identifier[1].extension(identifierJurisdiction).coding[0].code | Organization.identifier[1].extension(identifierJurisdiction).valueCodeableConcept.coding[0].code Implement with version: STU 1.2.0S
N3 - 2010EAThe data elements in this segment are defined in the PAS Claim Inquiry 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.2.0R
N302Practitioner.address[0].line[1] | Organization.address[0].line[1] Implement with version: STU 1.2.0S
N4 - 2010EAThe data elements in this segment are defined in the PAS Claim Inquiry 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
PRV - 2010EAThe data elements in this segment are defined in the PAS Claim Inquiry 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
HL - 2000FClaim.item[n] Each occurrence of Claim.item will have a corresponding 2000F occurrence except when the item[0].productOrService.coding[0].code is No Value (there should be only a single Claim.item in this situation and no 2000F Loop will be created) Implement with version: STU 1.2.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.2.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-itemTraceNumber' Implement with version: STU 1.2.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.2.0R
TRN04Claim.item[n].extension(itemTraceNumber).valueIdentifier.extension(identifierSubDepartment).valueString The identifierSubDepartment extension has a url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-identifierSubDepartment' Implement with version: STU 1.2.0S
UM - 2000FThe data elements in this segment are defined in the PAS Claim Inquiry profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
UM01Claim.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.2.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-certificationType' Implement with version: STU 1.2.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[n].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.2.0R
HCR - 2000FThe data elements in this segment are defined in the PAS Claim Inquiry profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
HCR01Claim.item[n].extension(reviewActionCode).valueCodeableConcept.coding[0].code The reviewActionCode extension is identified as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-reviewActionCode' Implement with version: STU 1.2.0R
REF - 2000FThe data elements in this segment are defined in the PAS Claim Inquiry 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
REF - 2000FThe data elements in this segment are defined in the PAS Claim Inquiry 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 The administrationReferenceNumber extension has: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-administrationReferenceNumber' Implement with version: STU 1.2.0R
DTP - 2000FThe data elements in this segment are defined in the PAS Claim Inquiry 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 Claim.item[n] has the attribute servicedDate set DTP03 to the value of servicedDate Otherwise set DTP03 to '«value of servicedPeriod.start»-«value of servicedPeriod.end»' Implement with version: STU 1.2.0R
DTP - 2000FThe data elements in this segment are defined in the PAS Claim Inquiry profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
DTP01'102' Implement with version: STU 1.0.0R
DTP02'D8' or 'RD8' If the itemCertificationIssueDate has an attribute named 'valueDate' set DTP02 to 'D8' Otherwise set DTP02 to 'RD8' Implement with version: STU 1.2.0R
DTP03Claim.item[0].extension(itemCertificationIssueDate).valueDate | Claim.item[0].extension(itemCertificationIssueDate).valuePeriod If the Claim.item[0] has the attribute valueDate set DTP03 to the value of valueDate Otherwise set DTP03 to '«value of valuePeriod.start»-«value of valuePeriod.end»' The date format in FHIR for this element is YYYY-MM-DD and will need to be converted. Implement with version: STU 1.2.0R
DTP - 2000FThe data elements in this segment are defined in the PAS Claim Inquiry profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
DTP01'036' Implement with version: STU 1.0.0R
DTP02'D8' or 'RD8' If the itemCertificationExpirationDate extension has an attribute named 'valueDate' set DTP02 to 'D8' Otherwise set DTP02 to 'RD8' Implement with version: STU 1.2.0R
DTP03Claim.item[0].extension(itemCertificationExpirationDate).valueDate | Claim.item[0].extension(itemCertificationExpirationDate).valuePeriod If the Claim.item[0] has the attribute valueDate set DTP03 to the value of valueDate Otherwise set DTP03 to '«value of valuePeriod.start»-«value of valuePeriod.end»' The date format in FHIR for this element is YYYY-MM-DD and will need to be converted. Implement with version: STU 1.2.0R
DTP - 2000FThe data elements in this segment are defined in the PAS Claim Inquiry profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
DTP01'007' Implement with version: STU 1.0.0R
DTP02'D8' or 'RD8' If the itemCertificationEffectiveDate has an attribute named 'valueDate' set DTP02 to 'D8' Otherwise set DTP02 to 'RD8' Implement with version: STU 1.2.0R
DTP03Claim.item[0].extension(itemCertificationEffectiveDate).valueDate | Claim.item[0].extension(itemCertificationEffectiveDate).valuePeriod If the Claim.item[0] has the attribute valueDate set DTP03 to the value of valueDate Otherwise set DTP03 to '«value of valuePeriod.start»-«value of valuePeriod.end»' The date format in FHIR for this element is YYYY-MM-DD and will need to be converted. Implement with version: STU 1.2.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.2.0S
SV101-01The value of Claim.item[n].productOrService.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.2.0R
SV101-02Claim.item[n].productOrService.coding[0].code Implement with version: STU 1.2.0R
SV101-08Claim.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.2.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
SV2 - 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 = 'institutional' then populate the SV2 segment otherwise do not populate the elements. Implement with version: STU 1.2.0S
SV201Claim.item[n].revenue.coding[0].code Implement with version: STU 1.0.0S
SV202-01The value of Claim.item[n].productOrService.coding.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.2.0R
SV202-02Claim.item[n].productOrService.coding[0].code Implement with version: STU 1.2.0R
SV202-08Claim.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.2.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
SV3 - 2000FThe data elements in this segment are not defined in the PAS Claim Inquiry profile. Implement with version: STU 1.0.0S
TOO - 2000FThe data elements in this segment are not defined in the PAS Claim Inquiry profile. Implement with version: STU 1.0.0S
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 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.2.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' 'UPIN' -> '1G' 'FI' -> '1J' 'EN' -> 'EI' 'G5' -> 'G5' 'N5' -> 'N5' 'N7' -> 'N7' 'SB' -> 'SY' 'ZH' -> 'ZH' Implement with version: STU 1.2.0R
REF02Practitioner.identifier[1].value | Organization.identifier[1].value Implement with version: STU 1.0.0R
REF03Practitioner.identifier[1].extension(identifierJurisdiction).valueCodeableConcept.coding[0].code | Organization.identifier[1].extension(identifierJurisdiction).valueCodeableConcept.coding[0].code Implement with version: STU 1.2.0S
N3 - 2010FThe data elements in this segment are defined in the PAS Claim Inquiry 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.2.0R
N302Practitioner.address[0].line[1] | Organization.address[0].line[1] Implement with version: STU 1.2.0S
N4 - 2010FThe data elements in this segment are defined in the PAS Claim Inquiry 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
PRV - 2010FThe data elements in this segment are defined in the PAS Claim Inquiry 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 The qualifier code used in this qualifier element is mapped from the qualifier codes used in NM101. Implement with version: STU 1.2.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 Inquiry profile because the values are hardcoded or derived. Implement with version: STU 1.0.0R

Appendix G. X12 278 Inquiry Response to the FHIR Claim Inquiry 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 Inquiry Response segments and elements and associated FHIR Claim Inquiry 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 Inquiry Response profile. Implement with version: STU 1.0.0R
BHTThe data elements in this segment are defined in the PAS Claim Inquiry 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 Inquiry Response profile. Implement with version: STU 1.0.0R
BHT02This data element is not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0R
BHT03Bundle.identifier.value Implement with version: STU 1.2.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' 'RD' -> 'complete' 'RS' -> 'partial' 'ZW' -> '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 Inquiry Response profile. Implement with version: STU 1.0.0R
AAA - 2000AThe data elements in this segment are defined in the PAS Claim Inquiry Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
AAA01ClaimResponse.error[n].extension(errorElement) 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.2.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(errorFollowupAction) The errorFollowupAction 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.2.0R
NM1 - 2010AOrganization.type Populate the CodeableConcept components of the type as follows: type.coding[0].system = 'https://codesystem.x12.org/005010/98' type.coding[0].code = value of NM101 Implement with version: STU 1.2.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 = 'XX' Implement with version: STU 1.2.0R
NM102This data element is not defined in the PAS Claim Inquiry 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 Inquiry Response profile. Implement with version: STU 1.0.0S
NM105This data element is not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0S
NM107This data element is not defined in the PAS Claim Inquiry 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 = 'http://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.2.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 Inquiry 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 Inquiry 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.0R
PER04Organization.contact.telecom[0].value Implement with version: STU 1.0.0R
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. «value-of-PER06»' to telecom[0].value See ITU-T E.123 for format of telephone values Implement with version: STU 1.2.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. «value-of-PER06»' to telecom[1].value See ITU-T E.123 for format of telephone values Implement with version: STU 1.2.0S
AAA - 2010AThe data elements in this segment are defined in the PAS Claim Inquiry Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
AAA01ClaimResponse.error[n].extension(errorElement) 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 = '2010A' Implement with version: STU 1.2.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(errorFollowupAction) The errorFollowupAction 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.2.0S
HL - 2000BThe data elements in this segment are not defined in the PAS Claim Inquiry 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 CodeableConcept components of the type as follows: type.coding[0].system = 'https://codesystem.x12.org/005010/98' type.coding[0].code = value of NM101 Implement with version: STU 1.2.0R
NM102This data element is not defined in the PAS Claim Inquiry 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 Inquiry Response profile. Implement with version: STU 1.0.0S
NM105This data element is not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0S
NM107This data element is not defined in the PAS Claim Inquiry 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 Inquiry Response profile. Implement with version: STU 1.0.0S
AAA - 2010BThe data elements in this segment are defined in the PAS Claim Inquiry Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
AAA01ClaimResponse.error[n].extension(errorElement) 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 = '2010B' Implement with version: STU 1.2.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(errorFollowupAction) The errorFollowupAction 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.2.0R
PRV - 2010BThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0S
HL - 2000CThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0S
TRN - 2000CThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.1.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.0.0R
NM101This data element is not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0R
NM102This data element is not defined in the PAS Claim Inquiry Response profile. 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.2.0S
NM105Patient.name[0].given[1] Implement with version: STU 1.2.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 CodeableConcept components of the type as follows: type.coding[0].system = 'http://terminology.hl7.org/CodeSystem/v2-0203' type.coding[0].code = 'MB' Implement with version: STU 1.2.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 Inquiry 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' -> 'SS' Implement with version: STU 1.2.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 Inquiry Response 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.2.0R
N302Patient.address[0].line[1] Implement with version: STU 1.2.0S
N4 - 2010CThe data elements in this segment are defined in the PAS Claim Inquiry 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 Inquiry Response profile. Implement with version: STU 1.0.0S
AAA - 2010CThe data elements in this segment are defined in the PAS Claim Inquiry Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
AAA01ClaimResponse.error[n].extension(errorElement) 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 = '2010C' Implement with version: STU 1.2.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(errorFollowupAction) The errorFollowupAction 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.2.0R
DMG - 2010CThe data elements in this segment are defined in the PAS Claim Inquiry 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 Inquiry 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
HL - 2000DThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0S
TRN - 2000DThe data elements in this segment are not defined in the PAS Claim Inquiry 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.2.0R
NM101This data element is not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0R
NM102This data element is not defined in the PAS Claim Inquiry Response profile. 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.2.0S
NM105Patient.name[0].given[1] Implement with version: STU 1.2.0S
NM107Patient.name[0].suffix[0] Implement with version: STU 1.0.0S
NM108Patient.identifier[0].type Populate the CodeableConcept components of the type as follows: type.coding[0].system = 'http://terminology.hl7.org/CodeSystem/v2-0203' type.coding[0].code = 'MB' Implement with version: STU 1.2.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 Inquiry 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: '28' -> 'EI' '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 Inquiry Response 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.2.0R
N302Patient.address[0].line[1] Implement with version: STU 1.2.0S
N4 - 2010DThe data elements in this segment are defined in the PAS Claim Inquiry 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 Inquiry Response profile. Implement with version: STU 1.0.0S
AAA - 2010DThe data elements in this segment are defined in the PAS Claim Inquiry Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
AAA01ClaimResponse.error[n].extension(errorElement) 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.2.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(errorFollowupAction) The errorFollowupAction 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.2.0R
DMG - 2010DThe data elements in this segment are defined in the PAS Claim Inquiry 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 Inquiry 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
HL - 2000EThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0S
TRN - 2000EThe data elements in this segment are defined in the PAS Claim Inquiry 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 Inquiry Response profile. Implement with version: STU 1.0.0R
TRN02ClaimResponse.identifier[0].value Implement with version: STU 1.1.0R
TRN03ClaimResponse.identifier[0].system Implement with version: STU 1.1.0R
TRN04ClaimResponse.identifier[0].assigner.reference Implement with version: STU 1.2.0S
AAA - 2000EThe data elements in this segment are defined in the PAS Claim Inquiry Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
AAA01ClaimResponse.error[n].extension(errorElement) 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 = '2000E' Implement with version: STU 1.2.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(errorFollowupAction) The errorFollowupAction 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.2.0R
UM - 2000EThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0S
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 populated 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-reviewAction' adjudication[0].category.coding[0].system = 'http://terminology.hl7.org/CodeSystem/adjudication' adjudication[0].category.coding[0].value = 'submitted' Implement with version: STU 1.2.0S
HCR01«reviewAction».extension(reviewActionCode) The reviewActionCode extension is a CodeableConcept and populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-reviewActionCode' extension[n].valueCodeableConcept.coding[0].system = 'https://codesystem.x12.org/005010/306' extension[n].valueCodeableConcept.coding[0].code = value of HCR01 Implement with version: STU 1.2.0R
HCR02ClaimResponse.preAuthRef AND «reviewAction».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.2.0S
HCR03«reviewAction».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.2.0S
HCR04«reviewAction».extension(secondSurgicalOpinionFlag) The number extension is 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.2.0S
REF - 2000EThe data elements in this segment are defined in the PAS Claim Inquiry 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 Inquiry 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.2.0R
REF - 2000EThe data elements in this segment are defined in the PAS Claim Inquiry 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.2.0R
REF02ClaimResponse.item[n].extension(administrationReferenceNumber) Used for each iteration of 2000F where REF (Previous Administrative Reference 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.2.0R
DTP - 2000EThe data elements in this segment are defined in the PAS Claim Inquiry 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 Inquiry 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.2.0R
DTP - 2000EThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0S
DTP - 2000EThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0S
DTP - 2000EThe data elements in this segment are defined in the PAS Claim Inquiry 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 Inquiry Response profile. Implement with version: STU 1.0.0R
DTP02This data element is not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0R
DTP03ClaimResponse.item[n].extension(itemPreAuthIssueDate) 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.2.0R
DTP - 2000EThe data elements in this segment are defined in the PAS Claim Inquiry 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 Inquiry Response profile. Implement with version: STU 1.0.0R
DTP02This data element is not defined in the PAS Claim Inquiry 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.2.0R
DTP - 2000EThe data elements in this segment are defined in the PAS Claim Inquiry 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 Inquiry Response profile. Implement with version: STU 1.0.0R
DTP02This data element is not defined in the PAS Claim Inquiry 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.2.0R
DTP - 2000ENot Used on PAS Claim Inquiry Response profile on FHIR ClaimResponse Implement with version: STU 1.0.0S
HI - 2000EThe data elements in this segment are defined in the PAS Claim Inquiry Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.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.1.0R
HI01-02ClaimResponse.item[n].extension(communicatedDiagnosis) The communicatedDiagnosis extension is a CodeableConcept and is 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: the communicatedDiagnosis does not indicate if the returned diagnosis code is for admitting, patient reason for visit or any other modifier for the diagnosis code. Implement with version: STU 1.2.0R
HSD - 2000E«authorizedItemDetail».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 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 = «ServiceRequest id in Bundle» Set the ServiceRequest.subject to the value of ClaimResponse.patient Note: Although 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.2.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(timingCalendarPattern) 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.2.0S
HSD08ServiceRequest.occurrenceTiming.extension(timingDeliveryPattern) 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.2.0S
CL1 - 2000EThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.2.0S
CR1 - 2000EThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0S
CR2 - 2000EThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0S
CR5 - 2000EThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0S
CR6 - 2000EThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0S
MSG - 2000EThe data elements in this segment are defined in the PAS Claim Inquiry 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.2.0R
NM1 - 2010EAThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0S
REF - 2010EAThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0S
N3 - 2010EAThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0S
N4 - 2010EAThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0S
PER - 2010EAThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0S
AAA - 2010EAThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0S
PRV - 2010EAThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0S
NM1 - 2010EBThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0S
N3 - 2010EBThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0R
N4 - 2010EBThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0R
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 Inquiry Response profile. Implement with version: STU 1.0.0R
HL03This data element is not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0R
HL04This data element is not defined in the PAS Claim Inquiry 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 Inquiry 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.2.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.2.0S
AAA - 2000FThe data elements in this segment are defined in the PAS Claim Inquiry Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
AAA01ClaimResponse.error[n].extension(errorElement) 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.2.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(errorFollowupAction) The errorFollowupAction 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.2.0R
UM - 2000FNot Used on PAS Claim Inquiry Response profile on FHIR ClaimResponse 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 populated as follows: item[n].adjudication[0].extension[n].extension[] -> see HCR attributes below item[n].adjudication[0].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.2.0S
HCR01«reviewAction».extension(reviewActionCode) The reviewActionCode extension is a CodeableConcept and populated as follows: extension[n].url = 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-reviewActionCode' extension[n].valueCodeableConcept.coding[0].system = 'https://codesystem.x12.org/005010/306' extension[n].valueCodeableConcept.coding[0].code = value of HCR01 Implement with version: STU 1.2.0R
HCR02«reviewAction».extension(number) The number extension is a string and is populated as follows: extension[n].url = 'number' extension[n].valueString = value of HCR02 Implement with version: STU 1.2.0S
HCR03«reviewAction».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.2.0S
HCR04«reviewAction».extension(secondSurgicalOpinionFlag) The number extension is a boolean and is populated as follows: extension[n].url = 'secondSurgicalOpinionFlag' extension[n].valueString = true if HCR04 = 'Y', false if HCR04 = 'N' Implement with version: STU 1.2.0S
REF - 2000FThe data elements in this segment are defined in the PAS Claim Inquiry 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 Inquiry 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.2.0R
REF - 2000FThe data elements in this segment are defined in the PAS Claim Inquiry 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 Inquiry 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.2.0R
DTP - 2000FThe data elements in this segment are defined in the PAS Claim Inquiry 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 Inquiry Response profile. Implement with version: STU 1.0.0R
DTP02See note on DTP03 Implement with version: STU 1.0.0R
DTP03ClaimResponse.item[n].extension(itemAuthorizedDate) 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.2.0R
DTP - 2000FThe data elements in this segment are defined in the PAS Claim Inquiry 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 Inquiry Response profile. Implement with version: STU 1.0.0R
DTP02This data element is not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0R
DTP03ClaimResponse.item[n].extension(itemPreAuthIssueDate) 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.2.0R
DTP - 2000FThe data elements in this segment are defined in the PAS Claim Inquiry 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 Inquiry Response profile. Implement with version: STU 1.0.0R
DTP02This data element is not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0R
DTP03ClaimResponse.item[n].extension(itemPreAuthPeriod) 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.2.0R
DTP - 2000FThe data elements in this segment are defined in the PAS Claim Inquiry 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 Inquiry Response profile. Implement with version: STU 1.0.0R
DTP02See note on DTP03 Implement with version: STU 1.0.0R
DTP03ClaimResponse.item[n].extension(itemPreAuthPeriod) 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.2.0R
SV1 - 2000FClaimResponse.item[n].extension(itemAuthorizedDetail) The components of the SV1 segment are used to create the itemAuthorizedDetail extension in an item (created for the 2000F loop as noted above). The itemAuthorizedDetail 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 itemAuthorizedDetail 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.2.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 is an Alphabetic Character (A-Z) HC = 'http://www.cms.gov/Medicare/Coding/HCPCSReleaseCodeSets' If the 1st position of the code is a Numeric (0-9) HC = 'http://www.ama-assn.org/go/cpt' N4 = 'http://hl7.org/fhir/sid/ndc' Implement with version: STU 1.2.0R
SV101-02«authorizedItemDetail».extension(productOrServiceCode) The productOrServiceCode extension is comprised of multiple attributes from the SV1 as follows: extension[n].url = 'productOrServiceCode' extension[n].valueCodeableConcept.coding[0].system = SV101-01 extension[n].valueCodeableConcept.coding[0].code = value of SV101-02 extension[n].valueCodeableConcept.text = SV101-07 Implement with version: STU 1.2.0R
SV101-03«authorizedItemDetail».extension(modifier) The modifier extension is comprised as follows: extension[n].url = 'modifier' extension[n].valueCodeableConcept.coding[0].system = SV101-01 extension[n].valueCodeableConcept.coding[0].code = value of SV101-03 Implement with version: STU 1.2.0S
SV101-04«authorizedItemDetail».extension(modifier) The modifier extension is comprised as follows: extension[n].url = 'modifier' extension[n].valueCodeableConcept.coding[0].system = SV101-01 extension[n].valueCodeableConcept.coding[0].code = value of SV101-04 Implement with version: STU 1.2.0S
SV101-05«authorizedItemDetail».extension(modifier) The modifier extension is comprised as follows: extension[n].url = 'modifier' extension[n].valueCodeableConcept.coding[0].system = SV101-01 extension[n].valueCodeableConcept.coding[0].code = value of SV101-05 Implement with version: STU 1.2.0S
SV101-06«authorizedItemDetail».extension(modifier) The modifier extension is comprised as follows: extension[n].url = 'modifier' extension[n].valueCodeableConcept.coding[0].system = SV101-01 extension[n].valueCodeableConcept.coding[0].code = value of SV101-06 Implement with version: STU 1.2.0S
SV101-07«authorizedItemDetail».extension(productOrServiceCode) See SV101-02 for using this attribute in the productOrServiceCode Implement with version: STU 1.2.0S
SV101-08«authorizedItemDetail».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].syste m = SV101-01 extension[n].valueCodeableConcept.coding[0].code = value of SV101-08 Implement with version: STU 1.2.0S
SV102«authorizedItemDetail».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.2.0S
SV103«authorizedItemDetail».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.2.0S
SV104See SV103 above Implement with version: STU 1.0.0S
SV111«authorizedItemDetail».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.2.0S
SV2 - 2000FClaimResponse.item[n].extension(itemAuthorizedDetail) The components of the SV2 segment are used to create the itemAuthorizedDetail extension in an item (created for the 2000F loop as noted above). The itemAuthorizedDetail 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 itemAuthorizedDetail 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.2.0S
SV201«authorizedItemDetail».extension(revenue) The revenue extension is of type 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.2.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 is an Alphabetic Character (A-Z) HC = 'http://www.cms.gov/Medicare/Coding/HCPCSReleaseCodeSets' If the 1st position of the code is a Numeric (0-9) HC = 'http://www.ama-assn.org/go/cpt' N4 = 'http://hl7.org/fhir/sid/ndc' Implement with version: STU 1.2.0R
SV202-02«authorizedItemDetail».extension(productOrServiceCode) The productOrServiceCode extension is comprised of multiple attributes from the SV2 as follows: extension[n].url = 'productOrServiceCode' extension[n].valueCodeableConcept.coding[0].system = value from SV202-01 extension[n].valueCodeableConcept.coding[0].code = value of SV202-02 extension[n].valueCodeableConcept.text = value of SV202-07 Implement with version: STU 1.2.0R
SV202-03«authorizedItemDetail».extension(modifier) The modifier extension is comprised as follows: extension[n].url = 'modifier' extension[n].valueCodeableConcept.coding[0].system = value from SV202-01 extension[n].valueCodeableConcept.coding[0].code = value of SV202-03 Implement with version: STU 1.2.0S
SV202-04Awaiting implementation of change request for mapping Implement with version: STU 1.0.0S
SV202-05Awaiting implementation of change request for mapping Implement with version: STU 1.0.0S
SV202-06Awaiting implementation of change request for mapping Implement with version: STU 1.0.0S
SV202-07«authorizedItemDetail».extension(productOrServiceCode) See SV202-02 for using this attribute in the productOrServiceCode Implement with version: STU 1.2.0S
SV202-08«authorizedItemDetail».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 = value from SV202-01 extension[n].valueCodeableConcept.coding[0].code = value of SV202-08 Implement with version: STU 1.2.0S
SV203«authorizedItemDetail».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.2.0S
SV204«authorizedItemDetail».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.2.0S
SV205See SV204 above Implement with version: STU 1.0.0S
SV206«authorizedItemDetail».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.2.0S
SV3 - 2000FThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0S
TOO - 2000FThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0S
HSD - 2000F«authorizedItemDetail».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 = «ServiceRequest id in Bundle» Set the ServiceRequest.subject to the value of ClaimResponse.patient Note: Although 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.2.0S
HSD01ServiceRequest.quantityQuantity.unit Implement with version: STU 1.2.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(timingCalendarPattern) 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.2.0S
HSD08ServiceRequest.occurrenceTiming.extension(timingDeliveryPattern) 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.2.0S
MSG - 2000FThe data elements in this segment are defined in the PAS Claim Inquiry 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 - 2010FClaimResponse.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 = «Practitioner or Organization id in Bundle» Implement with version: STU 1.2.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.2.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 Organization Implement with version: STU 1.2.0S
NM105Practitioner.name.given[1] | not used on Organization Implement with version: STU 1.2.0S
NM106Practitioner.name.prefix[0] | not used on Organization Implement with version: STU 1.2.0S
NM107Practitioner.name.suffix[0] | not used on Organization Implement with version: STU 1.2.0S
NM108Practitioner.identifier[0].type | Organization.identifier[0].type Populate the CodeableConcept components of the type 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 - 2010FThe data elements in this segment are defined in the PAS Claim Inquiry 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[1].type Populate the CodeableConcept components of the type as follows: type.coding[0].system = 'http://terminology.hl7.org/CodeSystem/v2-0203' type.coding[0].code = value of REF01 translated as follows: '0B' -> 'SL' '1G' -> 'UPIN' '1J' -> 'FI' 'EI' -> 'EN' 'G5' -> 'G5' 'N5' -> 'N5' 'N7' -> 'N7' 'SY' -> 'SB' 'ZH' -> 'ZH' Implement with version: STU 1.2.0R
REF02Practitioner.identifier[1].value | Organization.identifier[1].value Implement with version: STU 1.2.0R
REF03Practitioner.identifier[1].extension(identifierJurisdiction).coding[0].code | Organization.identifier[1].extension(identifierJurisdiction).coding[0].code Implement with version: STU 1.2.0S
N3 - 2010FThe data elements in this segment are defined in the PAS Claim Inquiry 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 - 2010FThe data elements in this segment are defined in the PAS Claim Inquiry 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 - 2010FThe data elements in this segment are defined in the PAS Claim Inquiry 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 Inquiry Response profile. Implement with version: STU 1.0.0R
PER02Not used on Practitioner | Organization.contact[0].name.text Implement with version: STU 1.2.0S
PER03Practitioner.telecom[0].system | Organization.contact[0].telecom[0].system Translate the PER03 value as follows: EM -> email FX -> fax TE -> phone UR -> url Implement with version: STU 1.2.0R
PER04Practitioner.telecom[0].value | Organization.contact[0].telecom[0].value Implement with version: STU 1.2.0R
PER05Practitioner.telecom[1].system | Organization.contact[0].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.2.0S
PER06Practitioner.telecom[1].value | Organization.contact[0].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. «value-of-PER06»' to telecom[0].value See ITU-T E.123 for format of telephone values Implement with version: STU 1.2.0S
PER07Practitioner.telecom[n].system | Organization.contact[0].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.2.0S
PER08Practitioner.telecom[n].value | Organization.contact[0].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. «value-of-PER06»' to telecom[1].value See ITU-T E.123 for format of telephone values Implement with version: STU 1.2.0S
AAA - 2010FThe data elements in this segment are defined in the PAS Claim Inquiry Response profile, see the FHIR Mapping instructions for each data element below. Implement with version: STU 1.0.0S
AAA01ClaimResponse.error[n].extension(errorElement) 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.2.0R
AAA03ClaimResponse.error[n].code Populate the CodeableConcept components of the type 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(errorFollowupAction) The errorFollowupAction 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.2.0R
PRV - 2010FThe 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 Organization Implement with version: STU 1.2.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.2.0R
SEThe data elements in this segment are not defined in the PAS Claim Inquiry Response profile. Implement with version: STU 1.0.0R