Previous Page TOC Index Next Page

8.4.2 MFE - master file entry segment

Figure 8-2. MFE attributes

SEQ

LEN

DT

OPT

RP/#

TBL#

ITEM#

ELEMENT NAME

1

3

ID

R


0180

00664

Record-Level Event Code

2

20

ST

C



00665

MFN Control ID

3

26

TS

O



00662

Effective Date/Time

4

60

CE

R

Y


00667

Primary Key Value

8.4.2.0 MFE field definitions

8.4.2.1 Record-level event code (ID) 00664

Definition: This field defines the record-level event for the master file record identified by the MFI segment and the primary key field in this segment. Refer to HL7 table 0180 - Record level event code for valid values.

Table 0180 - Record-level event code

Value

Description

MAD

Add record to master file

MDL

Delete record from master file

MUP

Update record for master file

MDC

Deactivate: discontinue using record in master file, but do not delete from database

MAC

Reactivate deactivated record

Note: If the file-level event code is "REP" (replace file), then each MFA segment must have a record-level event code of "MAD" (add record to master file).

8.4.2.2 MFN control ID (ST) 00665

Definition: A number or other identifier that uniquely identifies this change to this record from the point of view of the originating system. When returned to the originating system via the MFA segment, this field allows the target system to precisely identify which change to this record is being acknowledged. It is only required if the MFI response level code requires responses at the record level (any value other than NE).

Note: Note that this segment does not contain a Set ID field. The MFE-2-MFN control ID implements a more general concept than the Set ID. It takes the place of the SET ID in the MFE segment.

8.4.2.3 Effective date/time (TS) 00662

Definition: An optional effective date/time can be included for the record-level action specified. It is the date/time the originating system expects that the event is to have been completed on the receiving system. If this field is not present, the effective date/time should default to the current date/time (when the message is received).

8.4.2.4 Primary key value (CE) 00667

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

Definition: Uniquely identifies the record of the master file (identified in the MFI segment) to be changed (as defined by the record-level event code). The first component of this CE data field carries an optional subcomponent, the application ID, that uniquely identifies the application responsible for creating the primary key value. The application ID subcomponent can be used to guarantee uniqueness of the primary key across multiple applications.

The repetition of the primary key permits the identification of an individual component of a complex record as the object of the record-level event code. This feature allows the Master Files protocol to be used for modifications of single components of complex records.

Previous Page TOC Index Next Page