HL7 MFR_M01 Master Files Query Response
MFR_M01 returns master-file records after an MFQ_M01 query. It echoes the query, identifies the master file, then repeats returned entries using MFE plus the segment that contains the actual record data.
Like MFQ, this is a legacy pattern. It is still useful to document because older catalog and reference-data interfaces often live for a long time, quietly feeding systems that everyone relies on.
A small MFR M01 example
What workflow it represents
The receiver is answering a catalog or reference-data query. The requester may use the returned record to populate a local cache, validate a code, or display current catalog metadata.
Because the response can be partial, the consumer should read query status, returned records, and continuation together. A successful response with continuation is not the same thing as a complete catalog.
How to read the structure
MSH and MSA frame the response. QAK reports query status when present. QRD and QRF echo the old-style query.
MFI identifies the master file being returned. Each response group starts with MFE and then carries one actual master-file record segment, such as OM1 for a test/observation definition. DSC handles continuation.
Implementation traps
Do not ignore QAK or DSC. A response can be accepted, partial, empty, or continued, and each state should drive a different cache/update decision.
Also keep the primary key from MFE with the returned record. If the receiver changes the display text but the primary key is the stable identifier, mapping by display text will eventually hurt.
Reference notes
HL7 v2+ master-file material describes MFQ/MFR as withdrawn in later versions, but local v2.5.1 data still defines MFR_M01 with MSA, optional QAK, QRD/QRF, MFI, returned MFE groups, and DSC continuation.