| CH-ADR | CH-ADR-032 | reviewed | Testable |
11
|
3
| FAIL_adr_request_sample_22_Resource_Element_Wrong_XDS_Input_Attributes.xml&FAIL_adr_request_sample_23_Resource_Element_Wrong_PPQ_Input_Attributes.xml&See also: Page 22 | The <AttributeValue> child element SHALL convey the resource identifier.- For ADR due to XDS [ITI-18], there SHALL BE three Resources to be identified, each representing a class of documents, i.e. urn:e-health-suisse:2015:epr-subset:<patient_id>:normal, urn:e-health-suisse:2015:epr-subset:<patient_id>:restricted, urn:e-health-suisse:2015:epr-subset:<patient_id>:secret- For ADR due to PPQ, an Authorization Decision MUST be requested for each object itself, not a class of objects. For CH:ADRdue to CH:ATC, there is exactly one Resource to be identified, representing the object class of patient audit trail records (see Section 3.1.6.5 Semantics) | 14 | Section 3.1.6.5 | 6/22/21 4:31:11 PM by aeschlimann |
|
| CH-ADR | CH-ADR-073 | reviewed | Testable |
4
|
3
| | The PEP authorizing ITI-18 transactions by implementing an Authorization Decision Consumer MUST, in addition to the result from the Authorization Decision Query, validate that the resource-id from the SAML Assertion identifies the same patient as the MPI-PID supplied in the Registry Stored Query transaction. If not true, the transaction MUST be denied (see Section 3.1.6.1 CH:ADRdue to XDS Registry Stored Query [ITI-18]) | 13 | Section 3.1.6.1 | 6/22/21 4:31:13 PM by aeschlimann |
|
| 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 |
|
| ITI18 | ITI18-15 | reviewed | Testable |
0
|
1
| | If $XDSDocumentEntryType parameter is specified, and the Document Registry does support it, the proper information is returned | 113 | Section 3.18.4.1.2.5 | 5/3/19 4:44:43 PM by wbars |
|
| ITI18 | ITI18-16 | reviewed | Testable |
2
|
1
| | The query request and response will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V | 114 | Section 3.18.4.1.2.7 | 7/23/19 11:42:59 AM by aeschlimann |
|
| ITI18 | ITI18-17 | reviewed | Testable |
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 message | 114 | Section 3.18.4.1.2.7 | 7/23/19 11:38:01 AM by aeschlimann |
|
| ITI18 | ITI18-18 | reviewed | Testable |
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 message | 114 | Section 3.18.4.1.2.7 | 7/23/19 11:43:04 AM by aeschlimann |
|
| ITI18 | ITI18-19 | reviewed | Testable |
1
|
1
| | The Document Registry Actor shall Accept a parameterized query in an AdhocQueryRequest message | 118 | Section 3.18.4.1.3 | 7/23/19 11:38:35 AM by aeschlimann |
|
| ITI18 | ITI18-2 | reviewed | Testable |
1
|
1
| | When returnType=ObjectRef, a list of object UUIDs (references) SHALL be returned | 93 | Section 3.18.4.1.2.3.1 | 7/23/19 11:38:42 AM by aeschlimann |
|
| ITI18 | ITI18-20 | reviewed | Testable |
0
|
1
| | The Document Registry Actor shall verify the required parameters are included in the request. Additionally, special rules documented in the above section Parameters for Required Queries shall be verified | 118 | Section 3.18.4.1.3 | 5/3/19 4:44:58 PM by wbars |
|
| ITI18 | ITI18-21 | reviewed | Testable |
1
|
1
| | The Document Registry Actor shall return an error for the following condition : Unknown query ID (error code XDSUnknownStoredQuery) | 118 | Section 3.18.4.1.3 | 9/17/19 2:02:13 PM by aeschlimann |
|
| ITI18 | ITI18-22 | reviewed | Testable |
1
|
1
| | The Document Registry Actor shall return an error for the following condition : Required parameter missing (error code XDSStoredQueryParamNumber) | 118 | Section 3.18.4.1.3 | 9/17/19 2:02:15 PM by aeschlimann |
|
| ITI18 | ITI18-23 | reviewed | Testable |
1
|
1
| | The Document Registry shall accept the homeCommunityId value if it is specified in a Registry Stored Query request | 118 | Section 3.18.4.1.3 | 7/23/19 11:39:36 AM by aeschlimann |
|
| ITI18 | ITI18-24 | reviewed | Testable |
1
|
1
| | If a patient identifier specified as a parameter to the query is unknown to the Document Registry it shall return a successful response with no elements. | 118 | Section 3.18.4.1.3 | 8/26/19 4:37:00 PM by aeschlimann |
|
| ITI18 | ITI18-25 | reviewed | Testable |
1
|
1
| | The Document Registry may specify the homeCommunityID attribute on any appropriate elements | 118 | Section 3.18.4.1.3 | 8/26/19 5:25:26 PM by aeschlimann |
|