HL7 URD Results/update Definition
HL7 field reference URD fields from HL7 v2.5.1 Show fields
These are the generated fields for the version selected at the top of the page. The document stays the same, but the reference panel follows that version.
Fields
| Field | Name | Required | Repeatable | Type | Table |
|---|---|---|---|---|---|
| URD.1 | R/U Date/Time | No | No | TS | |
| URD.2 | Report Priority | No | No | ID | 0109 |
| URD.3 | R/U Who Subject Definition | Yes | Yes | XCN | |
| URD.4 | R/U What Subject Definition | No | Yes | CE | 0048 |
| URD.5 | R/U What Department Code | No | Yes | CE | |
| URD.6 | R/U Display/Print Locations | No | Yes | ST | |
| URD.7 | R/U Results Level | No | No | ID | 0108 |
URD defines an unsolicited results/update request or subscription.
The standard describes URD this way: The URD segment is used in sending unsolicited updates about orders and results. Its purpose is similar to that of the QRD segment, but from the results/unsolicited update point of view. Some of the fields have parallels in the QRD segment. This segment is not carried forward to the recommended queries for v 2.4.
Query segments define what the sender is asking for, how the receiver should format the answer, and how a multi-message response is continued or limited.
A query is an interface contract. The tag, parameters, row definitions, sort/filter rules, and continuation pointers must match exactly or the receiver may return technically valid data that is not what the requester expected.
The v2.5.1 structures show URD in UDM_Q05 - Unsolicited display update message. That tells you where it can appear, but the implementation guide still decides which optional fields are meaningful.
For practical interface work, read the generated field panel for datatype, required, repeatable, and table details, then use the notes below to decide what the field should mean in the receiving workflow.
URD-1 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
URD-2 qualifies the query workflow rather than identifying it. This is the sort of field receivers often use for branching, filtering, or display grouping.
Use the agreed value set, starting from HL7 table 0109. A local code without an agreed coding system is a small ambiguity that becomes a mapping problem later.
URD-3 carries R/U Who Subject Definition for this query workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
This field can repeat. Use repetitions for separate real-world values, not as a workaround for putting several unrelated ideas in one field.
URD-4 carries R/U What Subject Definition for this query workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
The generated panel links this to HL7 table 0048; many real interfaces narrow that list further, so follow the receiver's implementation guide.
URD-5 identifies the R/U What Department Code for this query workflow. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
If there are several identifiers, use repetitions deliberately and make each repeat self-explanatory rather than relying on position alone.
URD-6 places the query workflow in an organization, facility, department, room, bed, or location group. Keep physical location, owning department, and receiving facility separate when the datatype allows it.
This field can repeat. Use repetitions for separate real-world values, not as a workaround for putting several unrelated ideas in one field.
URD-7 qualifies the query workflow rather than identifying it. This is the sort of field receivers often use for branching, filtering, or display grouping.
Use the agreed value set, starting from HL7 table 0108. A local code without an agreed coding system is a small ambiguity that becomes a mapping problem later.