HL7 v2.5.1 Specificationsv2.5.1

↑↓ to moveEnter to openTry PID-5, ADT, 0004

MFK: Master files application acknowledgment

This page lists the structures and trigger events MFK defines, taken from the standard. The written commentary that theADT page carries has not been written for MFK.

Recognising MFK messages

MFK announces itself in MSH-9 like this:

MSH-9MFK^M01^MFK_M01
  1. MSH-9.1MFKmessage code: what kind of message this is
  2. MSH-9.2M01trigger event: what happened in the real world: master file notification
  3. MSH-9.3MFK_M01message structure: which segments to expect, and in what order

How to use these specifications explains MSH-9 in full, with a worked example.

Message structures

MFK takes 1 structure.

MFK_M01: Master File Notification

15 different trigger events send this structure:

The segments below are the same for all 15. HL7 varies the meaning, not the shape: there is no separate MFK_M02 layout. What changes is MSH-9, which tells the receiver which of the 15 happened and therefore what to do with the message.

You must always send: MSH, MSA, MFI. Everything else is optional, or required only inside a group you chose to send.

SegmentNameOPTCardinality
MSHR1..1
SFTO0..*
MSAR1..1
ERRO0..*
MFIR1..1
MFAO0..*

Trigger events

The trigger event is the real-world thing that made the message get sent. MFK defines 15.

EventNameStructure
M01Master File NotificationMFK_M01
M02Staff/Practitioner Master File MessageMFK_M01
M03Master File Notification - Test/ObservationMFK_M01
M04Charge Description Master File MessageMFK_M01
M05Patient Location Master File MessageMFK_M01
M06M06MFK_M01
M07M07MFK_M01
M08Master File Notification - Test/Observation (Numeric)MFK_M01
M09M09MFK_M01
M10Master File Notification - Test/Observation BatteriesMFK_M01
M11Master File Notification - Test/Calculated ObservationsMFK_M01
M12M12MFK_M01
M13Master File Notification - GeneralMFK_M01
M14Master File Notification - Site DefinedMFK_M01
M15Inventory Item Master File MessageMFK_M01