HL7^® Reference Guide

QBP_Q15 is a query-by-parameter message for a display response. It uses the newer QBP pattern, with QPD and RCP, but the response is RDY_K15 and carries display lines rather than a structured segment pattern or table.

That makes QBP_Q15 a useful bridge when a system has a query profile but the natural answer is a human-readable screen, summary, or list. It is more governed than old QRD/QRF queries, but the response still needs display-line discipline.

A small QBP Q15 example

What workflow it represents

The requester sends a named query and a query tag in QPD. The receiver uses the profile to interpret the remaining QPD parameters and returns display data in RDY_K15. A portal might use this to show a medication summary, appointment instructions, or a short eligibility explanation without needing every value as a separate HL7 field.

This still needs a profile. The query name tells both systems what the QPD parameters mean, what the response may contain, and what display lines are safe to show or parse.

How to read the structure

MSH identifies QBP^Q15^QBP_Q15. QPD carries the query name, tag, and profile-defined parameters. RCP controls immediacy, quantity limits, and related response handling. DSC is used only when continuing a prior response.

The absence of RDF is the clue that this is not a tabular request. If the sender expects rows and columns, QBP_Q13 is the cleaner fit.

Implementation traps

Do not call this "unstructured" and then rely on undocumented display text. If the requester needs to extract values from the response, freeze the line format or pick a more structured query pattern.

Also be explicit about privacy. Display responses often carry a concise human-readable summary, which can make them easy to log accidentally in places that were designed for technical acknowledgments.

Reference notes

The HL7 v2+ refactored QBP_Q15 page describes the query as a QBP display-response pattern with MSH, QPD, RCP, and DSC, and pairs it with RDY_K15.