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

Draft Website - For Review Purposes Only

MFA - Master File Acknowledgment Segment

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

The MFA segment contains the following fields as defined in HL7 Attribute Table - MFA - Master File Acknowledgment

HL7 Attribute Table - MFA - Master File Acknowledgment Segment
Seq# DataElement Description Must Implement Flags Cardinality Length C.LEN Vocabulary DataType
MFA
1 00664 Record-Level Event Code SHALL [1..1] [3..3] ID
2

00665 MFN Control ID MAY
True:
False:
C=
[1..1]
[0..1]
20 ST
3 00668 Event Completion Date/Time [0..1] DTM
4 00669 MFN Record Level Error Return SHALL [1..1] CWE
5 01308 Primary Key Value - MFA SHALL [1..*] Varies
6 01320 Primary Key Value Type - MFA SHALL [1..*] [2..3] ID

MFA-1: Record-Level Event Code (ID) 00664

(Definition from MFE.1 in Ch. 8)

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


(Definition from MFA.1 in Ch. 8)

Definition: This field defines record-level event for the master file record identified by the MFI segment and the primary key 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 MFA segment must have an MFA-1 - Record-level event code of "MAD" (add record to master file).


MFA-2: MFN Control ID (ST) 00665

(Definition from MFE.2 in Ch. 8)

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.


(Definition from MFA.2 in Ch. 8)

Definition: This field contains a number or other identifier that uniquely identifies this change to this record from the point of view of the originating system. This field uniquely identifies the particular record (identified by the MFE segment) being acknowledged by this MFA segment. 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 MFI-6 - Response Level Code requires responses at the record level (any value other than NE).

MFA-3: Event Completion Date/Time (DTM) 00668

Definition: This field may be required or optional depending on the site specifications for the given master file, master file event, and receiving facility.

MFA-4: MFN Record Level Error Return (CWE) 00669

Definition: This field contains the status of the requested update. Site-defined table, specific to each master file being updated via this transaction.

Refer to User-defined Table 0181 - MFN Record-level Error Return in Chapter 2C, Code Tables, for suggested values. All such tables will have at least the following two return code values: "S" for successful and "U" for unsuccessful.

MFA-5: Primary Key Value - MFA (Varies) 01308

Definition: This field uniquely identifies the record of the master file (identified in the MFI segment) for which the update status is being acknowledged (as defined by the field MFN-4 - Record Level Error Return). The data type of this field is defined by the value of MFA-6 - Value Type - MFA, 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 0607 - Primary Key Value - MFA 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 MFA-6 - Primary Key Value Type - MFA must also repeat (with the same number of repetitions), and the data type of each repetition of MFA-5 - Primary Key Value - MFA is specified by the corresponding repetition of MFA-6 - Value Type - MFA.

MFA-6: Primary Key Value Type - MFA (ID) 01320

Definition: This field contains the HL7 data type of MFA-5 - Primary Key Value - MFA. The valid HL7 data types are listed in HL7 Table 0355 - Primary Key Value Type in Chapter 2C, Code Tables.