HL7 EDR_R07 Enhanced Display Response

A legacy query response that returns display lines instead of structured rows.
HL7 message structure EDR_R07 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
MSA
 Message Acknowledgment Yes No
ERR
 Error No No
QAK
 Query Acknowledgment Yes No
DSP
 Display Data Yes Yes
DSC
 Continuation Pointer No No

EDR_R07 is an enhanced display response. It answers a query with formatted display data in repeating DSP segments, plus query status and optional continuation handling.

This is mostly a compatibility message now. It is useful when an old receiver expects screen-ready text, but it is a poor fit when the next system needs reusable clinical data.

A small EDR R07 example

MSH|^~\&|RESULTS|CITYHOSP|PORTAL|CITYHOSP|20260718151500||EDR^R07^EDR_R07|EDRR070001|P|2.5.1 MSA|AA|EQQQ040001 QAK|QDISPLAY001|OK|Q04^Display query^HL7nnn|2 DSP|1||Patient has two recent notes for review. DSP|2||Follow-up appointment requested for 20260722.

What systems do with it

The requester sends a legacy display-style query and the responder returns text lines that a user interface can show with minimal interpretation. QAK gives query status and count context. DSC can appear when the receiver has more data to request later.

Receivers often print, show, or archive the display lines exactly as sent. That is the benefit and the drawback: the message is easy to show but hard to transform safely.

How to read the structure

MSH identifies EDR^R07^EDR_R07. MSA acknowledges the original query. Optional ERR reports problems. Required QAK carries query status. Repeating DSP segments carry the display payload.

If DSC is present, the requester should treat the response as incremental and use the continuation rules from the receiver's query profile.

Implementation traps

The biggest trap is treating DSP text as structured clinical content. Line numbers and display formatting are not stable identifiers. If the receiver needs observations, orders, diagnoses, or charges, use a structured response message instead.

Also avoid reflowing the text unless the interface contract allows it. Some old systems depend on line breaks and column positions.

Reference notes

HL7 v2.3.1 Chapter 2 lists EDR as the enhanced display response alongside related display, tabular, and event replay response messages. See the HL7 v2.3.1 control/query chapter.