CH-XDS | CH-XDS-001 | to be reviewed | Testable |
0
|
0
| Agreed to do not cover this assertion | In Stored Queries (transaction ITI-18), the parameter $MetadataLevel, whenever provided, shall equal to 1 (one) (See Section 1.2.1 MetadataLevel). | 6 | Section 1.2 | 7/2/21 10:26:08 AM by aeschlimann |
|
CH-XDS | CH-XDS-002 | to be reviewed | Testable |
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) | 6 | Section 1.2 | 7/2/21 10:26:09 AM by aeschlimann |
|
CH-XDS | CH-XDS-003 | to be reviewed | Testable |
0
|
0
| Agreed to do not cover this assertion | Document 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) | 6 | Section 1.2 | 7/2/21 10:26:09 AM by aeschlimann |
|
CH-XDS | CH-XDS-004 | to be reviewed | Testable |
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) | 7 | Section 1.2.2.1 | 3/15/24 2:33:35 PM by aeschlimann |
|
CH-XDS | CH-XDS-005 | to be reviewed | Testable |
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) | 7 | Section 1.2.3 | 3/15/24 2:33:35 PM by aeschlimann |
|
CH-XDS | CH-XDS-006 | to be reviewed | Testable |
0
|
0
| Agreed to do not cover this assertion | The 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) | 6 | Section 1.2 | 7/2/21 10:26:09 AM by aeschlimann |
|
CH-XDS | CH-XDS-007 | to be reviewed | Testable |
2
|
0
| | The metadata DocumentEntry.Title is required in XDS DS and XDS DR (see Table 2: Metadata Optionality) | 6 | Section 1.2 | 7/2/21 10:26:09 AM by aeschlimann |
|
CH-XDS | CH-XDS-008 | to be reviewed | Testable |
0
|
0
| Agreed to do not cover this assertion | The metadata DocumentEntry.DeletionStatus is optional in XDS DS and XDS DR (see Table 2: Metadata Optionality) | 6 | Section 1.2 | 7/2/21 10:26:09 AM by aeschlimann |
|
CH-XDS | CH-XDS-009 | to be reviewed | Testable |
2
|
0
| | The metadata SubmissionSet.Author is required in XDS DS and XDS DR (see Table 2: Metadata Optionality) | 6 | Section 1.2 | 7/2/21 10:26:09 AM by aeschlimann |
|
CH-XDS | CH-XDS-010 | reviewed | Testable |
0
|
0
| | The AuthorRole attribute shall be user ONLY IF the Author attribute is set (0..1 for the Author attribute). | 8 | Section 1.2.4.3 | 3/15/24 2:33:35 PM by vhofman |
|
CH-XDS | CH-XDS-011 | reviewed | Testable |
0
|
0
| | The extra metadata attribute DocumentEntry.originalProviderRole SHALL be used. | 8 | Section 1.2.4.4 | 3/15/24 2:33:35 PM by vhofman |
|
CH-XDS | CH-XDS-012 | to be reviewed | Not testable |
0
|
0
| | The extra metadata attribute DocumentEntry.originalProviderRole SHALL be set by the Document Source actor to the role value of the current user. | 8 | Section 1.2.4.4 | 3/15/24 2:33:35 PM by vhofman |
|
CH-XDS | CH-XDS-013 | to be reviewed | Testable |
0
|
0
| | For the extra metadata attribute Document Entry.originalProviderRole, the Predefined URN datatype SHALL be used (ITI TF Vol 3, Section 4.2.3.1.7) with name urn:e-health-suisse:2020:originalProviderRole. Values SHALL be taken from the value set DocumentEntry.originalProviderRole (OID: 2.16.756.5.30.1.127.3.10.1.42) and formatted as Coded String data type defined in ITI TF 3, Table 4.2.3.1.7-2, i.e. as Code^^^&CodeSystemID&ISO | 8 | Section 1.2.4.4 | 3/15/24 2:33:35 PM by vhofman |
|
CH-XDS | CH-XDS-014 | reviewed | Testable |
0
|
0
| | The extra metadata attribute Document Entry.originalProviderRole SHALL NOT be updated by Update Initiator or Document Administrator actors. | 8 | Section 1.2.4.4 | 3/15/24 2:33:35 PM by vhofman |
|
ITI18 | ITI18-1 | reviewed | Testable |
1
|
1
| | The ebXML Registry stored query facility (Invoke Stored Query transaction) accepts the following parameters for returnType : 'LeafClass' or 'ObjectRef' | 93 | Section 3.18.4.1.2.3 | 7/23/19 11:36:04 AM by aeschlimann |
|
ITI18 | ITI18-10 | reviewed | Testable |
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 implements | 98 | Section 3.18.4.1.2.3.7 | 7/23/19 11:42:54 AM by aeschlimann |
|
ITI18 | ITI18-11 | reviewed | Testable |
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 results | 111 | Section 3.18.4.1.2.3.9.1 | 5/3/19 4:44:31 PM by wbars |
|
ITI18 | ITI18-12 | reviewed | Testable |
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 | 111 | Section 3.18.4.1.2.3.9.1 | 5/3/19 4:44:33 PM by wbars |
|
ITI18 | ITI18-13 | reviewed | Testable |
1
|
1
| | An error shall be returned when an unsupported stored query ID is received | 112 | Section 3.18.4.1.2.4 | 8/26/19 4:36:00 PM by aeschlimann |
|
ITI18 | ITI18-14 | reviewed | Testable |
0
|
1
| | If this parameter $XDSDocumentEntryType is specified, and the Document Registry does not support it, the Document Registry shall ignore | 113 | Section 3.18.4.1.2.5 | 5/3/19 4:44:39 PM by wbars |
|