MFR: Master files response
This page lists the structures and trigger events MFR defines, taken from the standard. The written commentary that theADT page carries has not been written for MFR.
Recognising MFR messages
MFR announces itself in MSH-9 like this:
MFR^M04^MFR_M04- MSH-9.1
MFRmessage code: what kind of message this is - MSH-9.2
M04trigger event: what happened in the real world: charge description master file message - MSH-9.3
MFR_M04message 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
MFR takes 5 structures. The first 4 are shown in full; the rest are listed below.
MFR_M01: Master File Notification
No trigger event in the standard names this structure.
You must always send: MSH, MSA, QRD, MFI, MFE, anyHL7Segment. Everything else is optional, or required only inside a group you chose to send.
| Segment | Name | OPT | Cardinality |
|---|---|---|---|
| MSH | R | 1..1 | |
| SFT | O | 0..* | |
| MSA | R | 1..1 | |
| ERR | O | 0..* | |
| QAK | O | 0..1 | |
| QRD | R | 1..1 | |
| QRF | O | 0..1 | |
| MFI | R | 1..1 | |
| MF_QUERY | a group of 2 segments, repeated together | R | 1..* |
| MFE | R | 1..1 | |
| anyHL7Segment | R | 1..1 | |
| DSC | O | 0..1 |
R inside a group means required of that group. Send the group and you must include that segment; leave the group out and it never appears. This structure has 1 such group: MF_QUERY.
MFR_M04: Charge Description Master File Message
Sent when one thing happens: M04: Charge Description Master File Message.
You must always send: MSH, MSA, QRD, MFI, MFE, CDM. Everything else is optional, or required only inside a group you chose to send.
| Segment | Name | OPT | Cardinality |
|---|---|---|---|
| MSH | R | 1..1 | |
| SFT | O | 0..* | |
| MSA | R | 1..1 | |
| ERR | O | 0..* | |
| QAK | O | 0..1 | |
| QRD | R | 1..1 | |
| QRF | O | 0..1 | |
| MFI | R | 1..1 | |
| MF_QUERY | a group of 3 segments, repeated together | R | 1..* |
| MFE | R | 1..1 | |
| CDM | R | 1..1 | |
| PRC | O | 0..* | |
| DSC | O | 0..1 |
MFR_M05: Patient Location Master File Message
Sent when one thing happens: M05: Patient Location Master File Message.
You must always send: MSH, MSA, QRD, MFI, MFE, LOC, LDP. Everything else is optional, or required only inside a group you chose to send.
| Segment | Name | OPT | Cardinality |
|---|---|---|---|
| MSH | R | 1..1 | |
| SFT | O | 0..* | |
| MSA | R | 1..1 | |
| ERR | O | 0..* | |
| QAK | O | 0..1 | |
| QRD | R | 1..1 | |
| QRF | O | 0..1 | |
| MFI | R | 1..1 | |
| MF_QUERY | a group of 7 segments, repeated together | R | 1..* |
| MFE | R | 1..1 | |
| LOC | R | 1..1 | |
| LCH | O | 0..* | |
| LRL | O | 0..* | |
| LDP | R | 1..* | |
| LCH | O | 0..* | |
| LCC | O | 0..* | |
| DSC | O | 0..1 |
MFR_M06
Sent when one thing happens: M06: M06.
You must always send: MSH, MSA, QRD, MFI, MFE, CM0. Everything else is optional, or required only inside a group you chose to send.
| Segment | Name | OPT | Cardinality |
|---|---|---|---|
| MSH | R | 1..1 | |
| SFT | O | 0..* | |
| MSA | R | 1..1 | |
| ERR | O | 0..* | |
| QAK | O | 0..1 | |
| QRD | R | 1..1 | |
| QRF | O | 0..1 | |
| MFI | R | 1..1 | |
| MF_QUERY | a group of 4 segments, repeated together | R | 1..* |
| MFE | R | 1..1 | |
| CM0 | R | 1..1 | |
| CM1 | O | 0..* | |
| CM2 | O | 0..* | |
| DSC | O | 0..1 |
Other MFR structures
| Structure | Name | Events |
|---|---|---|
| MFR_M07 | M07 |
Trigger events
The trigger event is the real-world thing that made the message get sent. MFR defines 5.
| Event | Name | Structure |
|---|---|---|
| M01 | Master File Notification | |
| M04 | Charge Description Master File Message | MFR_M04 |
| M05 | Patient Location Master File Message | MFR_M05 |
| M06 | M06 | MFR_M06 |
| M07 | M07 | MFR_M07 |