URS segment
Unsolicited Selection
The shape of one line
segmentURS|URS-1R/U Where Subject…|URS-2R/U When Data Start…|URS-3R/U When Data End…|URS-4R/U What User Qualifier|URS-5R/U Other Results…|URS-6R/U Which Date/Time Qualifier|URS-7R/U Which Date/Time Status…|URS-8R/U Date/Time Selection…|URS-9R/U Quantity/Timing…
required optional
URS-2 and its value arrives as URS-1, so the receiver stores R/U When Data Start Date/Time as R/U Where Subject Definition.This page carries the URS field table as published and nothing beyond it. The field notes, vendor behaviour, FHIR mapping and parsing guidance that thePID page has are still to be written for URS.
Every field
| SEQ | LEN | DT | OPT | RP/# | TBL# | ITEM# | Element name | Cardinality |
|---|---|---|---|---|---|---|---|---|
| URS-1 | 20 | ST | R | Y | 00052 | R/U Where Subject Definition | 1..* | |
| 26 | TS | O | 00053 | R/U When Data Start Date/Time | 0..1 | |||
| ||||||||
| 26 | TS | O | 00054 | R/U When Data End Date/Time | 0..1 | |||
| ||||||||
| URS-4 | 20 | ST | O | Y | 00055 | R/U What User Qualifier | 0..* | |
| URS-5 | 20 | ST | O | Y | 00056 | R/U Other Results Subject Definition | 0..* | |
| URS-6 | 12 | ID | O | Y | 0156 | 00057 | R/U Which Date/Time Qualifier | 0..* |
| URS-7 | 12 | ID | O | Y | 0157 | 00058 | R/U Which Date/Time Status Qualifier | 0..* |
| URS-8 | 12 | ID | O | Y | 0158 | 00059 | R/U Date/Time Selection Qualifier | 0..* |
| 60 | TQ | O | 00695 | R/U Quantity/Timing Qualifier | 0..1 | |||
| ||||||||
Related
No message structure in v2.5.1 carries URS, and no other segment is linked to it here. The standard defines the segment on its own.