HL7 URS Unsolicited Selection
HL7 field reference URS 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 |
|---|---|---|---|---|---|
| URS.1 | R/U Where Subject Definition | Yes | Yes | ST | |
| URS.2 | R/U When Data Start Date/Time | No | No | TS | |
| URS.3 | R/U When Data End Date/Time | No | No | TS | |
| URS.4 | R/U What User Qualifier | No | Yes | ST | |
| URS.5 | R/U Other Results Subject Definition | No | Yes | ST | |
| URS.6 | R/U Which Date/Time Qualifier | No | Yes | ID | 0156 |
| URS.7 | R/U Which Date/Time Status Qualifier | No | Yes | ID | 0157 |
| URS.8 | R/U Date/Time Selection Qualifier | No | Yes | ID | 0158 |
| URS.9 | R/U Quantity/Timing Qualifier | No | No | TQ |
URS adds selection criteria for unsolicited update workflows.
The standard describes URS this way: The URS segment is identical with the QRF segment, except that if the name of any field contains Query (of QRY), this word has been changed to Results (see URS-5-R/U other results subject definition). 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 URS 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.
URS-1 carries R/U Where 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.
URS-2 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.
For effective and end dates, make the boundary rule explicit. Receivers need to know whether the value is inclusive, exclusive, planned, actual, or merely informational.
URS-3 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.
For effective and end dates, make the boundary rule explicit. Receivers need to know whether the value is inclusive, exclusive, planned, actual, or merely informational.
URS-4 carries R/U What User Qualifier 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.
URS-5 carries R/U Other Results 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.
URS-6 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.
The generated panel links this to HL7 table 0156; many real interfaces narrow that list further, so follow the receiver's implementation guide.
URS-7 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.
The generated panel links this to HL7 table 0157; many real interfaces narrow that list further, so follow the receiver's implementation guide.
URS-8 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.
The generated panel links this to HL7 table 0158; many real interfaces narrow that list further, so follow the receiver's implementation guide.
URS-9 carries a measured, counted, priced, or dosed value. A number without the expected unit, currency, or companion qualifier is much easier to misread than an empty field.