Centricity PACS Version 1.0 CONFORMANCE STATEMENT for ...

GEMS INFORMATION TECHNOLOGIESCENTRICITY PACS 1.0 CONFORMANCE STATEMENTREV 0, MAY 2002 IIS FP 10617In general, the Q/R AE will always return a limited number of responses to a Q/R SCU, if the submittedquery may potentially generate a large number of matches in the database. The maximum number ofreturned query responses is configurable.5.1.2.2.3 Matching Operations5.1.2.2.3.1 Date and Time Keys Matching OperationsThe Q/R AE supports a DICOM Query request using any matching operations in a date or timematching key specified in the DICOM PS 3.4-1999, as listed in the following table:SPEC.NONEEQGELERANGEKey Value DescriptionNo key or no key value was specified ; match all occurrences of value- ; match all occurrences of value and subsequent values- ; match all occurrences of prior to and including value- ; match all occurrences between value1 and value2 inclusive.TABLE 5-2: DATE AND TIME MATCHING OPERATIONSBecause Centricity PACS saves the date and time values in one single field in the database, anarbitrarily independent search for the date and time keys in a DICOM Query request cannot besupported. For a combination of the date and time matching keys, the Q/R AE will interpret theperformed date and time joint matching as indicated in Table 5-3.Date SpecificationSee Table 5-2Time SpecificationSee Table 5-2Operation PerformedNONE NONE, EQ, GE, LE, RANGE Search not qualified by date and time(ignored)EQ, GE, LE, RANGE NONE Search using date specificationEQ EQ, GE, LE, RANGE Search using specified date and timeGE, LE, RANGE EQ, GE, LE, RANGE Search using date specification onlyTABLE 5-3: DATE AND TIME JOINT MATCHING OPERATIONS PERFORMED BY THE SCP5.1.2.2.3.2 Other Keys Matching OperationsThe Q/R AE supports single value matching for all keys of a supported type “Matching”, see Section5.1.2.2.4.The Q/R AE supports wild card matching for all text valued keys of a supported type “Matching”, seeSection 5.1.2.2.4.The Q/R AE supports UID list matching for all UID keys of a supported type “Matching”, see Section5.1.2.2.4.5.1.2.2.4 Patient Root Information Model DefinitionThis section specifies the use of the DICOM Patient Root Query / Retrieve Information Model formatching keys and returned keys supported in a DICOM Query request.5–44