Distributes master file update notifications. The MFI segment identifies the master file and MFE segments carry individual record updates. Master file consumers use this to synchronize reference data.
# Zato
from zato.hl7v2 import HL7Message
# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
'MFN^M18^MFN_M18|MSG001|P|2.9\r' \
'MFI|PRA^Practitioner master file|UPD|RE\r' \
'MFE|MAD|E001|20260701|PRA0001'
# .. parsed into a Python object ..
msg = HL7Message.parse(raw)
# .. whose fields we can now access.
mf_identifier = msg.mfi.master_file_identifier
mf_event = msg.mfi.file_level_event_code
record_action = msg.mfe.record_level_event_code
primary_key = msg.mfe.primary_key_value_mfeHow to construct, send, receive, and extract fields from real-world MFN^M18 messages.
Demonstrates receiving and extracting key fields from a master file notification - test / observation (payer) transaction
# Zato
from zato.hl7v2 import HL7Message
# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
'MFN^M18^MFN_M18|MSG001|P|2.9\r' \
'MFI|PRA^Practitioner master file|UPD|RE\r' \
'MFE|MAD|E001|20260701|PRA0001'
# .. parsed into a Python object ..
msg = HL7Message.parse(raw)
# .. whose fields we can now access.
mf_identifier = msg.mfi.master_file_identifier
mf_event = msg.mfi.file_level_event_code
record_action = msg.mfe.record_level_event_code
primary_key = msg.mfe.primary_key_value_mfeStep-by-step guides for working with HL7 v2 in Zato.
Use the HL7v2 message parser to extract the typed structure. The parsed message gives you direct access to every segment and field by name.
from zato.hl7v2 import HL7Message
raw = 'MSH|^~\&|SENDER|FACILITY|RECEIVER|DEST|20260401120000||MFN^M18^MFN_M18|MSG00001|P|2.9\rMFI|PRA^Practitioner master file^HL70175||UPD|||AL'
msg = HL7Message.parse(raw)
mf_identifier = msg.mfi.master_file_identifier
mf_event = msg.mfi.file_level_event_codeBeyond the mandatory MSH header, the required segments are: MFI, MFE, PM1, MCP. Optional segments provide additional detail when available.
Zato connects to any system that speaks HL7v2 over MLLP or FHIR over REST. This includes Epic, Cerner, Meditech, Allscripts, and other EHR platforms.
Yes, Zato has built-in MLLP support for sending and receiving HL7v2 messages. MLLP channels handle the framing protocol automatically.
Zato supports HL7 v2.9, which is backward compatible with earlier versions including v2.3, v2.5, and v2.7. Standard segments and datatypes are available as typed Python classes.
Yes. Zato handles both HL7v2 and FHIR natively, so you can parse v2 messages and build FHIR resources with IG-specific extensions in the same service. Typed Python classes are available for both protocols, including extensions from US Core, UK Core, Da Vinci, and other Implementation Guides.
Segments that make up the MFN^M18 message, in order. Groups are shown with their child segments.
| # | Segment | Usage | Repeats | Description | Group |
|---|---|---|---|---|---|
| 1 | MSH | Required | No | Message header | - |
| 2 | SFT | Optional | Yes | Software segment | - |
| 3 | UAC | Optional | No | User authentication credential | - |
| 4 | MFI | Required | No | Master file identification | - |
| 5 | MFE | Required | No | Master file entry | MF_PAYER |
| 6 | PM1 | Required | No | Payer master file | MF_PAYER |
| 7 | MCP | Required | No | Master file coverage policy | PAYER_MF_COVERAGE |
| 8 | DPS | Optional | Yes | Diagnosis and procedure | PAYER_MF_COVERAGE |
Get started with Zato and connect your systems in minutes.