The MFN Site defined master file notification transaction is used where the master file is not a simple one (as defined for MFN^M13) and is not a transaction type currently defined by HL7, but rather requires one or more HL7 and/or 'Z' segments to carry the master file information.
The Site defined master file notification is defined as follows:
| MSH-15 | MSH-16 | Immediate ACK | Application Ack |
|---|---|---|---|
| Blank | Blank | - | MFK^M14^MFK_M01 |
| NE | NE | - | - |
| AL, SU, ER | NE | ACK^M14^ACK | - |
| NE | AL, SU, ER | - | MFK^M14^MFK_M01 |
| AL, SU, ER | AL, SU, ER | ACK^M14^ACK | MFK^M14^MFK_M01 |
| MSH-15 | MSH-16 | Immediate ACK | Application Ack |
|---|---|---|---|
| Blank | Blank | ACK^M15^ACK | - |
| Blank | Blank | - | - |
| Blank | Blank | - | - |
| Blank | Blank | ACK^M04^ACK | - |
| Blank | Blank | - | - |
| Blank | Blank | ACK^M06^ACK | - |
| Blank | Blank | - | - |
| Blank | Blank | ACK^M07^ACK | - |
| Blank | Blank | - | - |
| Blank | Blank | ACK^M05^ACK | - |
| Blank | Blank | - | - |
| Blank | Blank | ACK^M16^ACK | - |
| Blank | Blank | - | - |
| Blank | Blank | ACK^M17^ACK | - |
| Blank | Blank | - | - |
| Blank | Blank | - | - |
| Blank | Blank | - | - |
| NE | NE | - | - |
| NE | NE | - | - |
| NE | NE | - | - |
| NE | NE | - | - |
| NE | NE | - | - |
| NE | NE | - | - |
| NE | NE | - | - |
| NE | NE | - | - |
| NE | NE | - | - |
| NE | NE | - | - |
| NE | NE | - | - |
| NE | NE | - | - |
| NE | NE | - | - |
| NE | NE | - | - |
| NE | NE | - | - |
| NE | NE | - | - |
| NE | NE | - | - |
| AL, SU, ER | NE | ACK^M13^ACK | - |
| AL, SU, ER | NE | ACK^M19^ACK | - |
| AL, SU, ER | NE | ACK^M14^ACK | - |
| AL, SU, ER | NE | ACK^M17^ACK | - |
| AL, SU, ER | NE | ACK^M02^ACK | - |
| AL, SU, ER | NE | ACK^M16^ACK | - |
| AL, SU, ER | NE | ACK^M08^ACK | - |
| AL, SU, ER | NE | ACK^M18^ACK | - |
| AL, SU, ER | NE | ACK^M09^ACK | - |
| AL, SU, ER | NE | ACK^M07^ACK | - |
| AL, SU, ER | NE | ACK^M10^ACK | - |
| AL, SU, ER | NE | ACK^M06^ACK | - |
| AL, SU, ER | NE | ACK^M11^ACK | - |
| AL, SU, ER | NE | ACK^M04^ACK | - |
| AL, SU, ER | NE | ACK^M12^ACK | - |
| AL, SU, ER | NE | ACK^M05^ACK | - |
| AL, SU, ER | NE | ACK^M15^ACK | - |
| NE | AL, SU, ER | - | - |
| AL, SU, ER | AL, SU, ER | ACK^M19^ACK | - |
The master file record identified by the MFE segment is contained in Z-segments immediately following the MFE segment, and is denoted by "..." 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 definition of this transaction and the associated abstract message structure code (as defined in MSH-9 - Message Type, denoted by MFN_Znn above) are subject to site negotiation. Refer to Chapter 2, section 2.17, "Local Extension" for additional information on 'Z' abstract message structure code definition.
The MFA segment carries acknowledgment information for the corresponding MFE segment (identified by MFA-5 - Primary Key Value - MFA). Fields MFE-4 - Primary Key Value - MFE and MFA-5 - Primary Key Value - MFA provide the link between the corresponding segments.
The Demo site for our new HL7 Version 2+ (plus) Standard
MFN^M14^MFN_Znn
