Search Criteria : 54 assertions found for this search Review filtered assertions

Assertion

Applies to

Applied to
Not applied to

Coverage

Covered by
Not covered by
Id scheme
Assertion id
Status
Testable?
#Coverage
#Applies to
Comment
Predicate
Page
Tags
Last changed
Actions
CH-XDSCH-XDS-001to be reviewedTestable 0 0 Agreed to do not cover this assertionIn Stored Queries (transaction ITI-18), the parameter $MetadataLevel, whenever provided, shall equal to 1 (one) (See Section 1.2.1 MetadataLevel).6Section 1.27/2/21 10:26:08 AM by aeschlimann
CH-XDSCH-XDS-003to be reviewedTestable 0 0 Agreed to do not cover this assertionDocument Registries MUST reject metadata registration requests containing Folders and/or Associations whose source and/or target objects are Folders (See Section 1.2.2 Addtional requirements on the Registry actor) 6Section 1.27/2/21 10:26:09 AM by aeschlimann
CH-XDSCH-XDS-004to be reviewedTestable 0 0 The Registry must support the Reference ID Option (see ITI TF Vol 1: 10.2.6) thus to support the use case of imaging where an Imaging Source must store specific values to the DocumentEntry.referenceIdList attribute (see Section 1.2.2.1 Reference ID Option)6Section 1.2.2.17/2/21 10:26:09 AM by aeschlimann
CH-XDSCH-XDS-005to be reviewedTestable 0 0 Whenever the role of the accessing user is not DADM (Document Administrator), the Document Consumer MUST NOT displaymetadata of and references to objects of the following types: Submission Sets not containing any DocumentEntry or Association object the accessing person is permitted to retrieve, Folders, Associations whose source and/or target objects are any of the above objects (see Section 1.2.3 Additional requirements on the Document Consumer actor) 6Section 1.2.37/2/21 10:26:09 AM by aeschlimann
CH-XDSCH-XDS-006to be reviewedTestable 0 0 Agreed to do not cover this assertionThe extra metadata attribute (DeletionStatus) shall have the name of urn:e-health-suisse:2019:deletionStatus. The following values are defined (see table 1.3.4.1) (See section 1.2.4.1 DelectionStatus)6Section 1.27/2/21 10:26:09 AM by aeschlimann
CH-XDSCH-XDS-008to be reviewedTestable 0 0 Agreed to do not cover this assertionThe metadata DocumentEntry.DeletionStatus is optional in XDS DS and XDS DR (see Table 2: Metadata Optionality) 6Section 1.27/2/21 10:26:09 AM by aeschlimann
ITI18ITI18-11reviewedTestable 0 1 If the query includes a patient identifier parameter and that patient identity matches the subsumed patient identifier of a merge message then the query shall return no results111Section 3.18.4.1.2.3.9.15/3/19 4:44:31 PM by wbars
ITI18ITI18-12reviewedTestable 0 1 If the query includes a patient identifier and that patient identifier matches the surviving patient identifier of a previous merge message then the query shall return the composite of: Metadata registered against the surviving patient identifier Metadata registered against the subsumed patient identifier 111Section 3.18.4.1.2.3.9.15/3/19 4:44:33 PM by wbars
ITI18ITI18-14reviewedTestable 0 1 If this parameter $XDSDocumentEntryType is specified, and the Document Registry does not support it, the Document Registry shall ignore113Section 3.18.4.1.2.55/3/19 4:44:39 PM by wbars
ITI18ITI18-15reviewedTestable 0 1 If $XDSDocumentEntryType parameter is specified, and the Document Registry does support it, the proper information is returned113Section 3.18.4.1.2.55/3/19 4:44:43 PM by wbars
ITI18ITI18-27reviewedTestable 0 1 If a status of PartialSuccess is returned, the Actors involved shall record both a success and a failure audit event128Section 3.18.5.15/3/19 4:45:21 PM by wbars
ITI18ITI18-5reviewedTestable 0 1 All Date/time values are to be inclusive in ITI-1894Section 3.18.4.1.2.3.35/3/19 4:44:08 PM by wbars
ITI18ITI18-8reviewedTestable 0 1 If the Document Registry receives in a Registry Stored Query transaction a value for the $XDSDocumentEntryStatus parameter that it does not understand then the Document Registry shall ignore the value and process the Registry Stored Query transaction as if the not understood value were not specified. 97Section 3.18.4.1.2.3.65/3/19 4:44:11 PM by wbars
ITI41ITI41-7reviewedTestable 0 1 If the Document Recipient declares the Accepts Limited Metadata Option it shall not reflect an error because the limitedMetadata attribute is present157Section 3.41.4.1.3.18/26/19 5:25:26 PM by wbars
ITI41ITI41-8reviewedTestable 0 1 Out of ScopeThe Document Source may include Folders in metadata157Section 3.41.4.1.3.19/17/19 2:38:25 PM by aeschlimann
ITI41ITI41-9reviewedTestable 0 1 Out of ScopeIf the Document Recipient is not able to process the Folder specific content it shall return a PartialFolderContentNotProcessed warning which includes a textual description identifying that Folder Content was not processed. In this case the Document Recipient is expected to have processed the rest of the submission successfully.157Section 3.41.4.1.3.19/17/19 2:38:32 PM by aeschlimann
ITI42ITI42-4reviewedTestable 0 1 If the Document Registry Actor does not send the XDSExtraMetadataNotSaved warning in its response, it shall also store and later include in query responses all non-IHE-defined metadata attributes167Section 3.42.4.1.3.28/26/19 5:25:26 PM by wbars
ITI42ITI42-9reviewedTestable 0 1 The Document Repository Actor shall make (all) the new document(s) included in the XDS Submission Set available for retrieval via the Retrieve Document Set transaction before it initiates the Register Document Set-b Request message with the Registry Actor165Section 3.42.4.15/6/19 1:44:41 PM by wbars
XDS.bXDSb-11reviewedTestable 0 2 out of scopeDocument Registry actor which claims support of the Cross-Enterprise Document Sharing-b (XDS.b) integration profile may perform the Patient Identity Feed [ITI-8] transaction.84Table 10.1-1b9/17/19 2:40:35 PM by aeschlimann
XDS.bXDSb-12reviewedTestable 0 2 out of scopeDocument Registry actor which claims support of the Cross-Enterprise Document Sharing-b (XDS.b) integration profile may perform the Patient Identity Feed HL7v3 [ITI-44] transaction84Table 10.1-1b9/17/19 2:40:41 PM by aeschlimann