The MFN transaction is defined as follows:
MFN Master File Notification Chapter
MSH Message Header 2
MFI Master File Identification 8
{MFE Master File Entry 8
[Z..] } One or more HL7 and/or (varies)
Z-segments carrying the data
for the entry identified in the MFE segment
MFK Master File Application Acknowledgment Chapter
MSH Message Header 2
MSA Acknowledgment 2
[ ERR ] Error 2
MFI Master File Identification 8
{ [MFA] } Master file ACK segment 8
The master file record identified by the MFE segment is contained in either Z-segments and/or HL7-defined segments immediately following the MFE segment, and is denoted by "Z..." in the MFN abstract message definition given above. This record may be either a flat record contained in a single segment, or a complex record needing more than a single segment to carry its data and (usually hierarchical) structure.
The master file record "[Z..]" identified by the MFE segment is optional (indicated by square brackets) in the single case where the master file is a simple one which contains only a key and the text value of that key. For this case only, both values may be carried in MFE-4-primary key value. segment.
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). |
Note: The MFK message is used for an application acknowledgment in either the original or enhanced acknowledgment modes. |
The MFA segment carries acknowledgment information for the corresponding MFE segment (identified by MFA-5-primary key value).