DICOM PS3.4 2020c - Service Class Specifications

C.2.2.2.5 Range Matching (Current)
Prev | C.2.2.2 Attribute Matching | Next

##### C.2.2.2.5 Range Matching

###### C.2.2.2.5.1 Range Matching of Attributes of VR of DA

In the absence of extended negotiation, then:

1. A string of the form "<date1> - <date2>", where <date1> is less or equal to <date2>, shall match all occurrences of dates that fall between <date1> and <date2> inclusive

2. A string of the form "- <date1>" shall match all occurrences of dates prior to and including <date1>

3. A string of the form "<date1> -" shall match all occurrences of <date1> and subsequent dates

###### C.2.2.2.5.2 Range Matching of Attributes of VR of TM

All comparison specified in the following shall be based on a direct comparison of times within a day. "Prior" includes all times starting from midnight of the same day to the specified time. "Subsequent" includes all times starting with the specified time until any time prior to midnight of the following day. Range matching crossing midnight is not supported.

No offset from Universal Coordinated Time is permitted in the TM VR values. If Timezone Offset From UTC (0008,0201) is present in the query identifier, the specified time values and the definition of midnight are in the specified timezone.

In the absence of extended negotiation, then:

1. A string of the form "<time1> - <time2>", where <time1> is less or equal to <time2>, shall match all occurrences of times that fall between <time1> and <time2> inclusive

2. A string of the form "- <time1>" shall match all occurrences of times prior to and including <time1>

3. A string of the form "<time1> -" shall match all occurrences of <time1> and subsequent times

###### C.2.2.2.5.3 Range Matching of Attributes of VR of DT

1. A string of the form "<datetime1> - <datetime2>", where <datetime1> is less or equal to <datetime2>, shall match all moments in time that fall between <datetime1> and <datetime2> inclusive

2. A string of the form "- <datetime1>" shall match all moments in time prior to and including <datetime1>

3. A string of the form "<datetime1> -" shall match all moments in time subsequent to and including <datetime1>

4. The offset from Universal Coordinated Time, if present in the Value of the Attribute, shall be taken into account for the purposes of the match.

###### C.2.2.2.5.4 Range Matching General Rules

If extended negotiation of combined datetime matching is successful, then a pair of Attributes that are of VR DA and TM, both of which specify the same form of Range Matching, shall have the concatenated string values of each Range Matching component matched as if they were a single Attribute of VR DT.

### Note

For example, a Study Date of "20060705-20060707" and a Study Time of "1000-1800" will match the time period of July 5, 10am until July 7, 6pm, rather than the three time periods of 10am until 6pm on each of July 5, July 6 and July 7, as would be the case without extended negotiation.

Regardless of other extended negotiation, an application may use the value of Timezone Offset From UTC (0008,0201) to adjust values of Attributes of VR TM and DT from the local timezone to UTC for matching. See Section C.2.2.2.1.

### Note

If extended negotiation of combined datetime matching is successful, the timezone offset may effect a change in date if the local time and UTC are on different sides of midnight.

Range matching is not defined for types of Attributes other than dates and times.

Prev | Up | Next
C.2.2.2.4 Wild Card Matching | Home | C.2.2.2.6 Sequence Matching

DICOM PS3.4 2020c - Service Class Specifications