HL7 MFQ_M01 Master Files Query

The older QRD/QRF query for master-file records.
HL7 message structure MFQ_M01 groups and segments from HL7 v2.5.1 Hide structure

These are the generated groups and segments for the version selected at the top of the page. The article explains the workflow, and this panel follows the chosen HL7 version.

Message Structure

SegmentNameRequiredRepeatable
MSH
 Message Header Yes No
SFT
 Software Segment No Yes
QRD
 Original-Style Query Definition Yes No
QRF
 Original style query filter No No
DSC
 Continuation Pointer No No

MFQ_M01 is the older original-mode query for master-file data. A system sends MFQ when it needs a current slice of a catalog or reference file, and the receiver can answer with MFR_M01.

Modern HL7 material withdraws the MFQ/MFR master-file query pattern in later versions and points implementers toward newer query mechanisms. Still, MFQ exists in local v2.5.1 data and shows up in legacy catalog integrations.

A small MFQ M01 example

MSH|^~\&|LIS|CITYHOSP|CATALOG|CITYHOSP|20260718121000||MFQ^M01^MFQ_M01|MFQ010001|P|2.5.1 QRD|20260718121000|R|I|MFQ010001|||10^RD|LABTEST^Laboratory test master^HL70175|MFN|CATALOG QRF|CATALOG|20260701000000|20260718235959|CBC^Complete blood count^L DSC|PAGE1|I

What workflow it represents

The requester needs the current definition of a master-file record or a small set of records. The receiver owns or serves that reference data. Common examples include looking up a test definition, location code, provider entry, or site-defined catalog record.

Because this is an old query style, both sides need a very explicit agreement for QRD and QRF. The fields can carry query ID, desired quantity, subject filter, date range, and target system, but their exact interpretation is profile-driven.

How to read the structure

MSH identifies the query. QRD is the original-style query definition. QRF narrows the request. DSC is used when continuation is needed.

There is no MFI in MFQ_M01. The master-file target is expressed through the query fields and the local profile. That makes the implementation guide important; otherwise the receiver has to guess what catalog the requester wants.

Implementation traps

The main trap is treating QRD/QRF like a general search box. They are structured fields with local meaning, and the response will only be predictable if both sides agree on each parameter.

Also document continuation. If the receiver sends DSC and the requester ignores it, the requester may cache a partial catalog and then behave as if the missing records do not exist.

Reference notes

HL7 v2+ master-file material describes MFQ/MFR as the older master-file query pattern and notes that it is withdrawn in later versions. Local v2.5.1 data still includes MFQ_M01 for legacy support.