| ITI38 | ITI38-002 | reviewed | Testable |
0
|
1
| | For stored queries that rely on concepts that a community may not support, namely associations, folders and submission sets, a Responding Gateway is allowed to respond with zero entries | 125 | Section 3.38.1 | 8/2/19 4:27:33 PM by mtoudic |
|
| ITI38 | ITI38-004 | reviewed | Testable |
1
|
2
| | homeCommunityId is structured as an OID limited to 64 characters and specified in URI syntax | 127 | Section 3.38.4.1.2.1 | 9/17/19 11:53:44 AM by aeschlimann |
|
| ITI38 | ITI38-008 | reviewed | Testable |
2
|
1
| | If the patient identifier is unknown by the Responding Gateway’s community, the Responding Gateway shall return either a successful response with no elements or an error with errorCode XDSUnknownPatientId, depending on local policy. | 128 | Section 3.38.4.1.2.2 | 9/17/19 11:54:29 AM by aeschlimann |
|
| ITI38 | ITI38-009 | reviewed | Testable |
1
|
1
| | FindDocuments Stored Query is required for Responding Gateway | 128 | Section 3.38.4.1.2.3 | 9/17/19 11:54:18 AM by aeschlimann |
|
| ITI38 | ITI38-010 | reviewed | Testable |
1
|
1
| | GetDocuments Stored Query is required for Responding Gateway | 128 | Section 3.38.4.1.2.3 | 9/17/19 11:54:20 AM by aeschlimann |
|
| ITI38 | ITI38-011 | reviewed | Testable |
1
|
1
| | The Responding Gateway Actor shall Return an XDSUnknownCommunity error code if the value of homeCommunityId is specified and is not known by the Responding Gateway | 129 | Section 3.38.4.1.3 | 9/17/19 11:54:32 AM by aeschlimann |
|
| ITI38 | ITI38-012 | reviewed | Testable |
1
|
1
| | The Responding Gateway Actor shall verify the homeCommunityId is specified on relevant queries and return an XDSMissingHomeCommunityId error code if missing | 129 | Section 3.38.4.1.3 | 9/17/19 11:54:41 AM by aeschlimann |
|
| ITI38 | ITI38-013 | reviewed | Testable |
1
|
1
| | The Responding Gateway Actor shall pass all parameters into the Registry Stored Query [ITI-18] transaction, when routing to a local XDS Document Registry | 129 | Section 3.38.4.1.3 | 9/17/19 11:54:52 AM by aeschlimann |
|
| ITI38 | ITI38-014 | reviewed | Testable |
1
|
1
| | In the response generated by the Respnding Gateway, If returntype=”LeafClass”, the ExtrinsicObject and RegistryPackage elements shall contain the home attribute | 129 | Section 3.38.4.1.3 | 9/17/19 11:54:59 AM by aeschlimann |
|
| ITI38 | ITI38-015 | reviewed | Testable |
1
|
1
| | In the response generated by the Respnding Gateway, If returnType=”ObjectRef”, the ObjectRef element shall contain the home attribute | 129 | Section 3.38.4.1.3 | 9/17/19 11:55:04 AM by aeschlimann |
|
| ITI38 | ITI38-016 | reviewed | Testable |
1
|
1
| | The Responding Gateway SHALL ensure that every RegistryError element returned in the response shall have the location attribute set to the homeCommunityId of the Responding Gateway | 129 | Section 3.38.4.1.3 | 9/17/19 11:55:21 AM by aeschlimann |
|
| ITI38 | ITI38-017 | reviewed | Testable |
0
|
2
| | The Initiating Gateway Actor shall On receiving the response from the Responding Gateway, verify the homeCommunityId is present where appropriate | 129 | Section 3.38.4.1.3 | 8/2/19 4:28:02 PM by mtoudic |
|
| ITI38 | ITI38-019 | reviewed | Testable |
0
|
1
| | All XDSMissingHomeCommunityId errors generated by the Initiating Gateway to the document consumer of the internal actor SHALL include, in the context of the message, identification of the Responding Gateway that returned the invalid response and the element or elements that were in error. | 129 | Section 3.38.4.1.3 | 5/2/19 5:32:51 PM by NicolasBailliet |
|
| ITI38 | ITI38-020 | reviewed | Testable |
0
|
1
| | If both successes and failures are received from Responding Gateways, the Initiating Gateway shall return both RegistryObjectList and RegistryErrorList in one response and specify PartialSuccess status. | 129 | Section 3.38.4.1.3 | 5/2/19 5:32:51 PM by NicolasBailliet |
|
| ITI38 | ITI38-027 | reviewed | Testable |
1
|
3
| | The Responding Gateway Shall audit the Cross Gateway Query as if it were a Document Registry except that for EventTypeCode the Responding Gateway shall specify EV(“ITI-38”, “IHE Transactions”, “Cross Gateway Query”) | 130 | Section 3.38.4.1.4 | 9/17/19 11:53:10 AM by aeschlimann |
|
| ITI38 | ITI38-028 | reviewed | Testable |
1
|
2
| | The Responding Gateway interacting with a local Document Registry SHALL audit as if it were a Document Consumer | 130 | Section 3.38.4.1.4 | 9/17/19 11:53:13 AM by aeschlimann |
|
| ITI39 | ITI39-001 | reviewed | Testable |
2
|
2
| | The ‘homeCommunityId’ parameter is required | 134 | Section 3.39.1 | 9/17/19 11:57:43 AM by aeschlimann |
|
| ITI39 | ITI39-002 | reviewed | Testable |
0
|
1
| | Responding Gateways shall support the Asynchronous Web Services Exchange Option on the Cross Gateway Retrieve. | 134 | Section 3.39.1 | 5/3/19 8:39:49 AM by NicolasBailliet |
|
| ITI39 | ITI39-003 | reviewed | Testable |
2
|
2
| | The Cross Gateway Retrieve uses the same syntax and standards as the Retrieve Document Set transaction specified in XDS | 135 | Section 3.39.4.1 | 9/17/19 11:57:46 AM by aeschlimann |
|
| ITI39 | ITI39-004 | reviewed | Testable |
2
|
2
| | The message semantics for Cross Gateway Retrieve are the same as Retrieve Document Set | 138 | Section 3.39.4.1.2 | 9/17/19 11:57:50 AM by aeschlimann |
|