TRN

Patient Event Tracking Number

Pos: 020	Max: 2
Detail - Optional
Loop: 2000D	Elements: 4

Ref

Id

Element Name

Req

Type

Min/Max

Usage

TRN01

481

Trace Type Code
Description: Code identifying which transaction is being referenced

M

ID

1/2

Required

Code

Name

1

Current Transaction Trace Numbers

TRN02

127

Reference Identification
Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Industry: Patient Event Tracking Number

M

AN

1/30

Required

TRN03

509

Originating Company Identifier
Description: A unique identifier designating the company initiating the funds transfer instructions. The first character is one-digit ANSI identification code designation (ICD) followed by the nine-digit identification number which may be an IRS employer identification number (EIN), data universal numbering system (DUNS), or a user assigned number; the ICD for an EIN is 1, DUNS is 3, user assigned number is 9
Industry: 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.

O

AN

10/10

Required

TRN04

127

Reference Identification
Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Industry: Trace Assigning Entity Additional Identifier
Use this information if necessary to further identify a specific component, such as a specific division or group, of the company identified in the previous data element (TRN03).

O

AN

1/30

Situational

1.

TRN02 provides unique identification for the transaction.

2.

TRN03 identifies an organization.

3.

TRN04 identifies a further subdivision within the organization.

Notes:

1. This TRN segment is required if the dependent is the patient and the requester needs to assign a unique trace number to the patient event request. This enables the requester to
• uniquely identify this patient event request
• trace the request
• match the response to the request
• reference this request in any associated attachments containing additional patient information related to this patient event request.
2. If the transaction is routed through a clearinghouse, the clearinghouse may add their own TRN segment. If the transaction passes through multiple clearinghouses, and the second clearinghouse needs to assign their own TRN segment, they must replace the TRN from the first clearinghouse and retain it to be returned in the 278 response. If the second clearinghouse does not need to assign a TRN segment, they should pass all received TRN segments.
3. Each trace number provided in the TRN segment at this level on the request must be returned by the UMO in the TRN segment at the corresponding level of the response.

Example:

TRN*1*2001042801*9012345678*CARDIOLOGY~