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

Draft Website - For Review Purposes Only

MFI - Master File Identification Segment

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

The fields in the MFI segment are defined in HL7 Attribute Table - MFI.

HL7 Attribute Table - MFI - Master File Identification Segment
Seq# Data Element Name DataType Usage Vocabulary Cardinality Item # Length C.LEN Flags
MFI
1 Master File Identifier CWE R
0175(R) Master File Identifier Code(Required)
[1..1] 00658
2 Master File Application Identifier HD O
0361 Application
[0..*] 00659
3 File-Level Event Code ID R
0178(R) File Level Event Code(Required)
[1..1] 00660 [3..3]
4 Entered Date/Time DTM O
[0..1] 00661
5 Effective Date/Time DTM O
[0..1] 00662
6 Response Level Code ID R
0179(R) Response Level(Required)
[1..1] 00663 [2..2]

MFI-1: Master File Identifier (CWE) 00658

Definition: This field is a CWE data type that identifies a standard HL7 master file. This table may be extended by local agreement during implementation to cover site-specific master files (z-master files). HL7 recommends use of the HL7 assigned table number as the master file identifier code if one is not specified in Table 0175. For example, a master file of Marital Status codes would be identified by HL70002 as the MFI-1 - Master file identifier. Refer to HL7 Table 0175 – Master File Identifier Code in Chapter 2C, Code Tables, for valid values.

MFI-2: Master File Application Identifier (HD) 00659

Definition: This field contains an optional code of up to 180 characters which (if applicable) uniquely identifies the application responsible for maintaining this file at a particular site. A group of intercommunicating applications may use more than a single instance of a master file of certain type (e.g., charge master or physician master). The particular instance of the file is identified by this field. Refer to User-defined table 0361 - Applications.

MFI-3: File-Level Event Code (ID) 00660

Definition: This field defines the file-level event code. Refer to HL7 Table 0178 – File Level Event Code in Chapter 2C, Code Tables, for valid values.

Note: The replace option allows the sending system to replace a file without sending delete record-level events for each record in that file. UPD means that the events are defined according to the record-level event code contained in each MFE segment in that message.

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


MFI-4: Entered Date/Time (DTM) 00661

Definition: This field contains the date/time for the file-level event on originating system.

MFI-5: Effective Date/Time (DTM) 00662

Definition: This optional field contains the effective date/time, which can be included for file-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 action date/time should default to the current date/time (when the message is received).

MFI-6: Response Level Code (ID) 00663

Definition: These codes specify the application response level defined for a given Master File Message at the MFE segment level as defined in HL7 Table 0179 – Response Level in Chapter 2C, Code Tables. Required for MFN-Master File Notification message. Specifies additional detail (beyond MSH-15 - Accept Acknowledgment Type and MSH-16 - Application Acknowledgment Type) for application-level acknowledgment paradigms for Master Files transactions. MSH-15 - Accept Acknowledgment Type and MSH-16 - Application Acknowledgment Type operate as defined in Chapter 2.