Search Criteria : 150 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-002to be reviewedTestable 1 0 Whenever a receiving actor (e.g. a Document Registry) discovers that this requirement ($MetadataLevel) is violated in an incoming request, it shall reject this request and return an error with the code XDSRegistryError (see section1.3) (See Section 1.2.1 MetadataLevel)6Section 1.27/2/21 10:26:09 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-007to be reviewedTestable 2 0 The metadata DocumentEntry.Title is required in XDS DS and XDS DR (see Table 2: Metadata Optionality) 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
CH-XDSCH-XDS-009to be reviewedTestable 2 0 The metadata SubmissionSet.Author is required in XDS DS and XDS DR (see Table 2: Metadata Optionality) 6Section 1.27/2/21 10:26:09 AM by aeschlimann
ITI18ITI18-1reviewedTestable 1 1 The ebXML Registry stored query facility (Invoke Stored Query transaction) accepts the following parameters for returnType : 'LeafClass' or 'ObjectRef'93Section 3.18.4.1.2.37/23/19 11:36:04 AM by aeschlimann
ITI18ITI18-10reviewedTestable 1 1 Document Consumer actors implementing this transaction (ITI-18) shall implement one or more of these queries as needed to support the use cases it implements98Section 3.18.4.1.2.3.77/23/19 11:42:54 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-13reviewedTestable 1 1 An error shall be returned when an unsupported stored query ID is received112Section 3.18.4.1.2.48/26/19 4:36:00 PM by aeschlimann
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-16reviewedTestable 2 1 The query request and response will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V114Section 3.18.4.1.2.77/23/19 11:42:59 AM by aeschlimann
ITI18ITI18-17reviewedTestable 1 1 The Document Registry Actor shall accept a Registry Stored Query Request formatted as a SIMPLE SOAP message and respond with a Registry Stored Query Response formatted as a SIMPLE SOAP message114Section 3.18.4.1.2.77/23/19 11:38:01 AM by aeschlimann
ITI18ITI18-18reviewedTestable 1 1 The Document Consumer Actor shall generate the Registry Stored Query Request formatted as a SIMPLE SOAP message and accept a Registry Stored Query Response formatted as a SIMPLE SOAP message114Section 3.18.4.1.2.77/23/19 11:43:04 AM by aeschlimann
ITI18ITI18-19reviewedTestable 1 1 The Document Registry Actor shall Accept a parameterized query in an AdhocQueryRequest message118Section 3.18.4.1.37/23/19 11:38:35 AM by aeschlimann