Search Criteria : 13 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
RDRD-001to be reviewedTestable 0 0 When the On-Demand Documents option is implemented by a Responding Gateway it shall also implement the Persistence of Retrieved Documents option and shall ensure that any Stable Documents created through support of the Persistence of Retrieved Documents option be a replacement for a prior version of that document.8Section 2.49/13/17 1:29:56 PM by aberge
RDRD-002to be reviewedTestable 0 0 Responding NHIN Gateways shall support asynchronous retrieve requests as described in the XCA Profile.10Section 3.19/13/17 1:29:56 PM by aberge
RDRD-003to be reviewedTestable 1 0 Each NHIO shall use the homeCommunityId of the form urn:oid:n.n.n.n (using a globally unique OID assigned to the NHIO) when responding to a Cross Gateway Query.11Section 3.1.15/17/17 3:16:02 PM by aberge
RDRD-004to be reviewedTestable 0 0 NHIOs that generate On-Demand documents by aggregating data from multiple sources must ensure that the generated document remains available until a subsequent request for that On-Demand document causes generation of a more recent version of the same content11Section 3.1.29/13/17 1:29:56 PM by aberge
RDRD-005to be reviewedTestable 0 0 Within an XDS Affinity Domain, if the Cross Gateway Retrieve requests multiple documents with different repository unique IDs, the Responding Gateway shall contact multiple Document Repositories and consolidate the responses.11Section 3.2.39/13/17 1:29:56 PM by aberge
RDRD-006to be reviewedTestable 1 0 The Cross Gateway Retrieve Request shall carry a required repositoryUniqueId that identifies the repository from which the document is to be retrieved. This value corresponds to XDSDocumentEntry.repositoryUniqueId.12Section 3.35/17/17 3:15:05 PM by aberge
RDRD-007to be reviewedTestable 1 0 The Cross Gateway Retrieve Request shall carry a required documentUniqueId that identifies the document within the repository. This value corresponds to the XDSDocumentEntry.uniqueId.12Section 3.35/17/17 3:15:12 PM by aberge
RDRD-008to be reviewedTestable 1 0 The Cross Gateway Retrieve Request shall carry the homeCommunityId element that identifies the community holding the document. The homeCommunityId element must be specified in the Cross Gateway Retrieve request .12Section 3.35/17/17 3:15:18 PM by aberge
RDRD-009to be reviewedTestable 0 0 The Cross Gateway Retrieve Request shall carry the repositoryUniqueId associated to each document requested, it can be different therefore allowing a single request to identify multiple repositories.12Section 3.35/17/17 3:16:18 PM by aberge
RDRD-010to be reviewedTestable 1 0 For each of the returned documents, the Cross Gateway Retrieve Response Message shall carry a homeCommunityId. This value shall be the same as the homeCommunityId value in the Cross Gateway Retrieve Request Message12Section 3.35/17/17 3:16:23 PM by aberge
RDRD-011to be reviewedTestable 1 0 For each of the returned documents, the Cross Gateway Retrieve Response Message shall carry a required repositoryUniqueId that identifies the repository from which the document is to be retrieved.12Section 3.35/17/17 3:16:28 PM by aberge
RDRD-012to be reviewedTestable 1 0 For each of the returned documents the Cross Gateway Retrieve Response Message the documentUniqueId value shall be the same as the documentUniqueId in the original Cross Gateway Retrieve Request Message. This value corresponds to the XDSDocumentEntry.uniqueId.12Section 3.35/17/17 3:16:33 PM by aberge
RDRD-013to be reviewedTestable 2 0 Both the Initiating Gateway and Responding Gateway shall audit the Cross Gateway Retrieve as described in section 3.39.4.1.4.13Section 59/13/17 1:29:56 PM by aberge