Previous Page TOC Index Next Page

6.4.1 FT1 - financial transaction segment

The FT1 segment contains the detail data necessary to post charges, payments, adjustments, etc. to patient accounting records.

Figure 6-1. FT1 attributes

SEQ

LEN

DT

OPT

RP/#

TBL#

ITEM#

ELEMENT NAME

1

4

SI

O



00355

Set ID -FT1

2

12

ST

O



00356

Transaction ID

3

10

ST

O



00357

Transaction Batch ID

4

26

TS

R



00358

Transaction Date

5

26

TS

O



00359

Transaction Posting Date

6

8

IS

R


0017

00360

Transaction Type

7

80

CE

R


0132

00361

Transaction Code

8

40

ST

B



00362

Transaction Description

9

40

ST

B



00363

Transaction Description - Alt

10

6

NM

O



00364

Transaction Quantity

11

12

CP

O



00365

Transaction Amount - Extended

12

12

CP

O



00366

Transaction Amount - Unit

13

60

CE

O


0049

00367

Department Code

14

8

IS

O


0072

00368

Insurance Plan ID

15

12

CP

O



00369

Insurance Amount

16

80

PL

O



00133

Assigned Patient Location

17

1

IS

O


0024

00370

Fee Schedule

18

2

IS

O


0018

00148

Patient Type

19

60

CE

O

Y

0051

00371

Diagnosis Code

20

120

XCN

O


0084

00372

Performed By Code

21

120

XCN

O



00373

Ordered By Code

22

12

CP

O



00374

Unit Cost

23

22

EI

O



00217

Filler Order Number

24

120

XCN

O



00765

Entered By Code

25

80

CE

O


0088

00393

Procedure Code

6.4.1.0 FT1 field definitions

6.4.1.1 Set ID - FT1 (SI) 00355

Definition: This field contains the number that identifies this transaction. For the first occurrence of the segment the sequence number shall be 1, for the second occurrence it shall be 2, etc.

6.4.1.2 Transaction ID (ST) 00356

Definition: This field contains a number assigned by the sending system for control purposes. The number can be returned by the receiving system to identify errors.

6.4.1.3 Transaction batch ID (ST) 00357

Definition: This field uniquely identifies the batch in which this transaction belongs.

6.4.1.4 Transaction date (TS) 00358

Definition: This field contains the date of the transaction. For example, this field would be used to identify the date a procedure, item, or test was conducted or used. It may be defaulted to today’s date.

6.4.1.5 Transaction posting date (TS) 00359

Definition: This field contains the date of the transaction that was sent to the financial system for posting.

6.4.1.6 Transaction type (IS) 00360

Definition: This field contains the code that identifies the type of transaction. Refer to user-defined table 0017 - Transaction type for suggested values.

User-defined Table 0017 - Transaction type

Values

Description

CG

Charge

CD

Credit

PY

Payment

AJ

Adjustment

6.4.1.7 Transaction code (CE) 00361

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>

Definition: This field contains the code assigned by the institution for the purpose of uniquely identifying the transaction. For example, this field would be used to uniquely identify a procedure, supply item, or test for charging purposes. Refer to user-defined table 0132 - Transaction code for suggested values. See Chapter 7 for a discussion of the universal service ID.

6.4.1.8 Transaction description (ST) 00362

Definition: This field has been retained for backward compatibility only. As of Version 2.3, FT1-7-transaction code contains a component for the transaction description. When used for backward compatibility, FT1-8-transaction description contains a description of the transaction associated with the code entered in FT1-7-transaction code

6.4.1.9 Transaction description - alt (ST) 00363

Definition: This field has been retained for backward compatibility only. As of Version 2.3, FT1-7-transaction code contains a component for the alternate transaction description. When used for backward compatibility, FT1-9-transaction description--alt contains an alternate description of the transaction associated with the code entered in FT1-7-transaction code.

6.4.1.10 Transaction quantity (NM) 00364

Definition: This field contains the quantity of items associated with this transaction.

6.4.1.11 Transaction amount - extended (CP) 00365

Components: <price (MO)> ^ <price type (ID)> ^ <from value (NM)> ^ <to value (NM)> ^ <range units (CE)> ^ <range type (ID)>

Definition: This field contains the amount of a transaction. It may be left blank if the transaction is automatically priced. Total price for multiple items.

6.4.1.12 Transaction amount - unit (CP) 00366

Components: <price (MO)> ^ <price type (ID)> ^ <from value (NM)> ^ <to value (NM)> ^ <range units (CE)> ^ <range type (ID)>

Definition: This field contains the unit price of a transaction. Price of a single item.

6.4.1.13 Department code (CE) 00367

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>

Definition: This field contains the department code that controls the transaction code described above. Refer to user-defined table 0049 - Department code for suggested values.

6.4.1.14 Insurance plan ID (IS) 00368

Definition: This field contains the identifier of the primary insurance plan with which this transaction should be associated. Refer to user-defined table 0072 - Insurance plan ID for suggested values.

6.4.1.15 Insurance amount (CP) 00369

Components: <price (MO)> ^ <price type (ID)> ^ <from value (NM)> ^ <to value (NM)> ^ <range units (CE)> ^ <range type (ID)>

Definition: This field contains the amount to be posted to the insurance plan referenced above.

6.4.1.16 Assigned patient location (PL) 00133

Components: <point of care (IS)> ^ <room (IS)> ^ <bed (IS)> ^ <facility (HD)> ^ <location status (IS)> ^ <person location type (IS)> ^ <building (IS)> ^ <floor (IS)> ^ <location description (ST)>

Definition: This field contains the current patient location. This can be the location of the patient when charge item was ordered or when the charged service was rendered. For the current assigned patient location, use PV1-3-assigned patient location.

6.4.1.17 Fee schedule (IS) 00370

Definition: This field contains the code used to select the appropriate fee schedule to be used for this transaction posting. Refer to user-defined table 0024 - Fee schedule for suggested values.

6.4.1.18 Patient type (IS) 00148

Definition: This field contains the type code assigned to the patient for this episode of care (visit or stay). Refer to user-defined table 0018 - Patient type for suggested values. This is for use when the patient type for billing purposes is different than the visit patient type in PV1-18-patient type.

6.4.1.19 Diagnosis code (CE) 00371

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>

Definition: This field contains the primary diagnosis code for billing purposes. ICD9-CM is assumed for all diagnosis codes. This is the most current diagnosis code that has been assigned to the patient. ICD10 can also be used. Refer to user-defined table 0051 - Diagnosis code for suggested values.

6.4.1.20 Performed by code (XCN) 00372

Components: <ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code(ID)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>

Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)

Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)

Definition: This field contains the composite number/name of the person/group that performed the test/procedure/transaction, etc. This is the service provider. Refer to user-defined table 0084 - Performed by for suggested values. Multiple names and identifiers for the same practitioner may be sent in this field, not multiple practitioners. The legal name is assumed to be in the first repetition. When the legal name is not sent, a repeat delimiter must be sent first for the first repetition. The components of this field are described in Chapter 2.

6.4.1.21 Ordered by code (XCN) 00373

Components: <ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code(ID)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>

Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)

Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)

Definition: This field contains the composite number/name of the person/group that ordered the test/ procedure/ transaction, etc. Multiple names and identifiers for the same practitioner may be sent in this field, not multiple practitioners. The legal name is assumed to be in the first repetition. When the legal name is not sent, a repeat delimiter must be sent first for the first repetition. The components for this field are described in Chapter 2.

6.4.1.22 Unit cost (CP) 00374

Components: <price (MO)> ^ <price type (ID)> ^ <from value (NM)> ^ <to value (NM)> ^ <range units (CE)> ^ <range type (ID)>

Definition: This field contains the unit cost of transaction. The cost of a single item.

6.4.1.23 Filler order number (EI) 00217

Components: <entity identifier (ST)> ^ <namespace ID (IS)> ^ <universal ID (ST)> ^ <universal ID type (ID)>

Definition: This field is used when the billing system is requesting observational reporting justification for a charge. This is the number used by a filler to uniquely identify a result. See Chapter 4 for a complete description.

6.4.1.24 Entered by code (XCN) 00765

Components: <ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code(ID)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>

Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)

Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)

Definition: This field identifies the composite number/name of the person who entered the insurance information.

6.4.1.25 Procedure code (CE) 00393

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>

Definition: This field contains a unique identifier assigned to the procedure, if any, associated with the charge. Refer to user-defined table 0088 - Procedure code for suggested values. This field is a CE data type for compatibility with clinical and ancillary systems.

Previous Page TOC Index Next Page