net.ihe.gazelle.assets.SearchCriteria : 25 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
ITI41ITI41-1to be reviewedTestable 0 1 A Provide and Register Document Set-b transaction shall carry within metadata, one XDSDocumentEntry object per document155Section 3.41.19/3/18 6:09:47 PM by meenal
ITI41ITI41-10to be reviewedTestable 0 1 In the case where the Document Source submits a replacement of documents, if the Document Recipient is not able to process the replacement semantics in the submission it shall return a PartialReplaceContentNotProcessed warning which includes a textual description identifying that the replacement semantics were not processed. In this case the Document Recipient is expected to have processed the rest of the submission successfully158Section 3.41.4.1.39/3/18 6:09:47 PM by meenal
ITI41ITI41-11to be reviewedTestable 0 1 A Document Repository shall forward the metadata to the Document Registry using the Register Document Set-b transaction [ITI-42]158Section 3.41.4.1.39/3/18 6:09:48 PM by meenal
ITI41ITI41-12to be reviewedTestable 0 1 Each document within the message shall be stored into the Document Repository as an octet stream with an associated MIME type. 158Section 3.41.4.1.39/3/18 6:09:48 PM by meenal
ITI41ITI41-13to be reviewedTestable 0 1 The Document Repository shall modify the received document metadata before initiating the Register Document Set-b transaction to the Document Registry by adding/replacing: The repositoryUniqueId for this Document Repository to allow for the Document Consumer to correctly identify the proper Document Repository for each document (XDSDocumentEntry.repositoryUniqueId). A hash value (XDSDocumentEntry.hash) A size (XDSDocumentEntry.size).158Section 3.41.4.1.39/3/18 6:09:48 PM by meenal
ITI41ITI41-15to be reviewedTestable 0 1 The Document Repository shall ensure that when any Retrieve Document Set transaction is received requesting a specific document(s), it shall be provided to the Document Consumer unchanged from the octet stream that was submitted (full fidelity repository) and shall match the size and hash attributes of the XDSDocumentEntry object158Section 3.41.4.1.39/3/18 6:09:48 PM by meenal
ITI41ITI41-16to be reviewedTestable 0 1 If the Document Repository or Document Recipient detects a failure it shall return an error message to the Document Source or Metadata-Limited Document Source thus terminating this transaction. 158Section 3.41.4.1.39/3/18 6:09:48 PM by meenal
ITI41ITI41-17to be reviewedTestable 0 1 The Document Repository or Document Recipient shall send a Provide and Register Document Set-b Response when the processing of a Provide and Register Document Set-b Request is complete161Section 3.41.4.29/3/18 6:09:48 PM by meenal
ITI41ITI41-18to be reviewedTestable 0 1 The document(s) received by the Document Recipient shall be available for further processing according to the capabilities of the system162Section 3.41.4.2.39/3/18 6:09:49 PM by meenal
ITI41ITI41-19to be reviewedTestable 0 1 The metadata added to the registry shall be available for discovery via Registry Stored Query transactions162Section 3.41.4.2.39/3/18 6:09:49 PM by meenal
ITI41ITI41-2to be reviewedTestable 0 1 A Provide and Register Document Set-b transaction shall carry XDS Submission Set definition along with the linkage to new documents and references to existing documents155Section 3.41.19/3/18 6:09:49 PM by meenal
ITI41ITI41-20to be reviewedTestable 0 1 An implementation of the Document Source or Metadata-Limited Document Source Actor shall be capable of Submit one or more documents161Section 3.41.6.13/20/15 11:59:23 AM by aboufahj
ITI41ITI41-22to be reviewedTestable 0 1 A Document Repository or Document Recipient shall be capable of accepting submissions containing multiple documents162Section 3.41.6.23/20/15 11:59:23 AM by aboufahj
ITI41ITI41-23to be reviewedTestable 0 1 A Document Repository shall validate the following metadata element received as part of a Provide and Register transaction: XDSDocumentEntry.uniqueId, XDSSubmissionSet.sourceId, XDSDocumentEntry.hash, XDSDocumentEntry.size 162Section 3.41.6.23/20/15 11:59:23 AM by aboufahj
ITI41ITI41-24to be reviewedTestable 0 1 A submission shall be rejected if not unique within the repository and the hashes of the two documents do not match. If the hashes of the documents match, the Document Repository shall accept the duplicate document162Section 3.41.6.23/20/15 11:59:23 AM by aboufahj
ITI41ITI41-25to be reviewedTestable 0 1 a submission shall be rejected if the hash is included in the submission and its value does not match the hash for the received document (ignoring case), as calculated by the Document Repository or Document Recipient; an XDSRepositoryMetadataError shall be returned on mismatch162Section 3.41.6.23/20/15 11:59:23 AM by aboufahj
ITI41ITI41-26to be reviewedTestable 0 1 a submission shall be rejected if the size is included in the submission and its value does not match the size of the received document, as computed by the Document Repository or Document Recipient; an XDSRepositoryMetadataError shall be returned on mismatch162Section 3.41.6.23/20/15 11:59:23 AM by aboufahj
ITI41ITI41-27to be reviewedTestable 0 1 The Provide and Register Document Set-b Transaction is either a PHI-Import event or a PHI-Export event, depending on actor, as defined in ITI TF-2a: Table 3.20.6-1, with the following exceptions162Section 3.41.7.13/20/15 11:59:23 AM by aboufahj
ITI41ITI41-3to be reviewedTestable 0 1 The Document Repository shall, upon receipt of a Provide and Register Document Set-b [ITI-41] transaction send a corresponding Register Document Set-b [ITI-42] transaction to the Document Registry Actor156Section 3.41.4.19/3/18 6:09:51 PM by meenal
ITI41ITI41-4to be reviewedTestable 0 1 The Document Repository Actor shall create and insert the XDSDocumentEntry.repositoryUniqueId, XDSDocumentEntry.size, and XDSDocumentEntry.hash attributes for each document received from the Provide and Register Document Set-b [ITI-41] transaction into the resulting Register Document Set-b [ITI-42] transaction metadata156Section 3.41.4.19/3/18 6:09:51 PM by meenal