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 0 0 A document repository is responsible for storing documents in a transparent, secure, reliable and persistent manner and responding to document retrieval requests86Section 101/29/19 2:23:47 PM by aboufahj
XDS.bXDSb-10to be reviewedTestable 0 1 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.89Table 10.1-1b9/3/18 6:11:02 PM by aboufahj
XDS.bXDSb-11to be reviewedTestable 0 1 Document 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.89Table 10.1-1b9/3/18 6:11:02 PM by aboufahj
XDS.bXDSb-12to be reviewedTestable 0 1 Document 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] transaction89Table 10.1-1b9/3/18 6:11:02 PM by aboufahj
XDS.bXDSb-13to be reviewedTestable 0 1 Document 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] transaction89Table 10.1-1b9/3/18 6:11:02 PM by aboufahj
XDS.bXDSb-14to be reviewedTestable 0 1 Integrated Document Source/Repository actor which claims support of the Cross-Enterprise Document Sharing-b (XDS.b) integration profile shall perform the Register Document Set-b [ITI-42] transaction.89Table 10.1-1b9/3/18 6:11:03 PM by aboufahj
XDS.bXDSb-15to be reviewedTestable 0 1 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.89Table 10.1-1b9/3/18 6:11:03 PM by aboufahj
XDS.bXDSb-16to be reviewedTestable 0 1 Patient 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. 89Table 10.1-1b9/3/18 6:11:03 PM by aboufahj
XDS.bXDSb-17to be reviewedTestable 0 1 Patient 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.89Table 10.1-1b9/3/18 6:11:03 PM by aboufahj
XDS.bXDSb-18to be reviewedTestable 0 1 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.89Table 10.1-1b9/3/18 6:11:03 PM by aboufahj
XDS.bXDSb-19to be reviewedTestable 0 1 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.89Table 10.1-1b9/3/18 6:11:04 PM by aboufahj
XDS.bXDSb-2to be reviewedTestable 0 1 A document registry is responsible for storing information about those documents86Section 109/3/18 6:11:04 PM by aboufahj
XDS.bXDSb-20to be reviewedTestable 0 1 If 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 Authority89Table 10.1-1b9/3/18 6:11:04 PM by aboufahj
XDS.bXDSb-21to be reviewedTestable 0 1 Document Registry and Patient Identify Source shall implement at least one of Patient Identity Feed or Patient Identity Feed HL7v389Table 10.1-1b9/3/18 6:11:04 PM by aboufahj
XDS.bXDSb-21-bisto be reviewedTestable 0 1 extra components entered in that string of Patient ID in the transaction ITI-8 or ITI-44 shall cause those transactions to fail92Section 10.1.2.69/3/18 6:11:04 PM by aboufahj
XDS.bXDSb-23to be reviewedTestable 0 1 XDS.b implementations shall support either Patient Identity Feed (ITI TF-2a: 3.8) or Patient Identity Feed HL7v3 (ITI TF-2b: 3.44) or both92Section 10.1.2.69/3/18 6:11:05 PM by aboufahj
XDS.bXDSb-24to be reviewedTestable 0 1 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 vocabulary94Section 10.29/3/18 6:11:05 PM by aboufahj
XDS.bXDSb-25to be reviewedTestable 0 1 In case of failure to process a Submission Request, the Submission Set and any XDS Documents and Folders shall not be registered.106Section 10.4.39/3/18 6:11:05 PM by aboufahj
XDS.bXDSb-27to be reviewedTestable 0 1 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 Registry113Section 10.4.99/3/18 6:11:05 PM by aboufahj
XDS.bXDSb-28to be reviewedTestable 0 1 Each XDS Document contained in a XDS Document Registry will be assigned one of the following Availability Status codes : Approved, Deprecated114Section 10.4.10.19/3/18 6:11:05 PM by aboufahj