The Demo site for our new HL7 Version 2+ (plus) Standard
visit the hl7 website

Draft Website - For Review Purposes Only

MFE - Master File Entry Segment

The Technical Steward for the MFE segment is Infrastructure and Messaging.

HL7 Attribute Table - MFE - Master File Entry Segment
Seq# Data Element Name DataType Usage Vocabulary Cardinality Item # Length C.LEN Flags
MFE
1 Record-Level Event Code ID R
0180(R) Record-level Event Code(Required)
[1..1] 00664 [3..3]
2 MFN Control ID ST C
[0..1] 00665 20 #
3 Effective Date/Time DTM O
[0..1] 00662
4 Primary Key Value - MFE Varies R
0608
[1..*] 00667
5 Primary Key Value Type ID R
0355(R) Primary Key Value Type(Required)
[1..*] 01319 [2..3]
6 Entered Date/Time DTM O
[0..1] 00661
7 Entered By XCN O
[0..1] 00224

MFE-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 in Chapter 2C, Code Tables, for valid values.

Note: If the MFI-3 - File-level event code is "REP" (replace file), then each MFE segment must have an MFE-1 - Record-level event code of "MAD" (add record to master file).


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


MFE-3: Effective Date/Time (DTM) 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).

MFE-4: Primary Key Value - MFE (Varies) 00667

Definition: This field 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 data type of field is defined by the value of MFE-5 - Value Type, and may take on the format of any of the HL7 data types defined in HL7 Table 0355 - Primary Key Value Type in Chapter 2C, Code Tables. The PL data type is used only on Location master transactions. Refer to Table 0608 - Primary Key Value - MFE in Chapter 2C for valid values.

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. If this field repeats, the field MFE-5 - Value Type must also repeat (with the same number of repetitions), and the data type of each repetition of MFE-4 - Primary Key Value - MFE is specified by the corresponding repetition of MFE-5 - Value Type.

MFE-5: Primary Key Value Type (ID) 01319

Definition: This field contains the HL7 data type of MFE-4 - Primary Key Value - MFE. The valid values for the data type of a primary key are listed in HL7 Table 0355 - Primary Key Value Type in Chapter 2C, Code Tables.

MFE-6: Entered Date/Time (DTM) 00661

Definition: This field contains the date and time of the last change of the record.

MFE-7: Entered By (XCN) 00224

Definition: This field contains the identity of the person who actually keyed the master file entry into the application. It provides an audit trail in case the request is entered incorrectly and the ancillary department needs to clarify the request.