net.ihe.gazelle.assets.SearchCriteria : 30 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
XDS.bXDSb-1to be reviewedTestable 1 1 A document repository is responsible for storing documents in a transparent, secure, reliable and persistent manner and responding to document retrieval requests81Section 107/29/19 3:27:51 PM by NicolasBailliet
XDS.bXDSb-10reviewedTestable 1 2 Document Registry actor which claims support of the Cross-Enterprise Document Sharing-b (XDS.b) integration profile shall perform the Provide and Registry Stored Query [ITI-18] transaction.84Table 10.1-1b8/26/19 5:25:26 PM by aeschlimann
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
XDS.bXDSb-13to be reviewedTestable 0 2 out of scopeDocument Registry actor which claims support of the Cross-Enterprise Document Sharing-b (XDS.b) integration profile may perform the Register On-Demand Document Entry [ITI-61] transaction84Table 10.1-1b9/17/19 2:40:56 PM by aeschlimann
XDS.bXDSb-15to be reviewedTestable 2 3 Integrated Document Source/Repository actor which claims support of the Cross-Enterprise Document Sharing-b (XDS.b) integration profile shall perform the Retrieve Document Set [ITI-43] transaction.84Table 10.1-1b7/29/19 3:32:34 PM by NicolasBailliet
XDS.bXDSb-16to be reviewedTestable 0 2 out of scopePatient Identity Source 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:41:31 PM by aeschlimann
XDS.bXDSb-17to be reviewedTestable 0 2 out of scopePatient Identity Source actor which claims support of the Cross-Enterprise Document Sharing-b (XDS.b) integration profile may perform the Patient Identity Feed HL7v3 [ITI-44] transaction.84Table 10.1-1b9/17/19 2:41:36 PM by aeschlimann
XDS.bXDSb-18to be reviewedTestable 0 2 On-Demand Document Source actor which claims support of the Cross-Enterprise Document Sharing-b (XDS.b) integration profile shall perform the Register On-Demand Document Entry [ITI-61] transaction.84Table 10.1-1b8/26/19 5:25:26 PM by wbars
XDS.bXDSb-19to be reviewedTestable 0 2 On-Demand Document Source actor which claims support of the Cross-Enterprise Document Sharing-b (XDS.b) integration profile shall perform the Retrieve Document Set [ITI-43] transaction.84Table 10.1-1b8/26/19 5:25:26 PM by wbars
XDS.bXDSb-2reviewedTestable 1 2 A document registry is responsible for storing information about those documents82Section 108/26/19 5:25:26 PM by aeschlimann
XDS.bXDSb-20to be reviewedTestable 0 2 out of scopeIf Assigning Authority of Patient ID presents in the Patient Identity Feed or Patient Identity Feed HL7v3 transaction, the Patient Identity Source is required to use an OID to identify the Assigning Authority85Table 10.1-1b9/17/19 2:42:15 PM by aeschlimann
XDS.bXDSb-21reviewedTestable 0 3 out of scopeDocument Registry and Patient Identify Source shall implement at least one of Patient Identity Feed or Patient Identity Feed HL7v384Table 10.1-1b9/17/19 2:42:20 PM by aeschlimann
XDS.bXDSb-21-bisreviewedTestable 0 3 out of scopeextra components entered in that string of Patient ID in the transaction ITI-8 or ITI-44 shall cause those transactions to fail88Section 10.1.2.69/17/19 2:42:40 PM by aeschlimann
XDS.bXDSb-23reviewedTestable 0 1 out of scopeXDS.b implementations shall support either Patient Identity Feed (ITI TF-2a: 3.8) or Patient Identity Feed HL7v3 (ITI TF-2b: 3.44) or both88Section 10.1.2.69/17/19 2:42:45 PM by aeschlimann
XDS.bXDSb-24reviewedTestable 1 2 An XDS.b Document Registry has always been required to validate that documents that are registered do contain a confidentialityCode from an XDS Affinity Domain vocabulary89Section 10.28/26/19 5:25:26 PM by aeschlimann
XDS.bXDSb-25reviewedTestable 1 1 In case of failure to process a Submission Request, the Submission Set and any XDS Documents and Folders shall not be registered.102Section 10.4.39/17/19 2:43:48 PM by aeschlimann
XDS.bXDSb-27reviewedTestable 1 2 Submission Requests for Documents related to Patients with IDs not registered in the XDS Affinity Domain Patient Identifier Domain shall be rejected by the XDS Document Registry109Section 10.4.99/17/19 2:43:56 PM by aeschlimann
XDS.bXDSb-28reviewedTestable 1 1 Each XDS Document contained in a XDS Document Registry will be assigned one of the following Availability Status codes : Approved, Deprecated110Section 10.4.10.18/26/19 5:25:26 PM by aeschlimann
XDS.bXDSb-3reviewedTestable 1 2 Document Consumer actor which claims support of the Cross-Enterprise Document Sharing (XDS.b) integration profile shall perform the Registry Stored Query [ITI-18] transaction. 89Table 10.1-1b8/26/19 5:25:26 PM by aeschlimann