net.ihe.gazelle.assets.SearchCriteria : 83 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
ITI57ITI57-001reviewedTestable 1 1 An Update Document Set Request message is an ebRS SubmitObjectsRequest containing ebRIM formatted metadata19Section 3.57.4.1.28/28/19 11:51:09 AM by ycadoret
ITI57ITI57-002reviewedTestable 1 1 ITI TF-3: Table 4.3.1-3 details the requirements on metadata attributes for each actor submitting metadata19Section 3.57.4.1.28/28/19 11:53:20 AM by ycadoret
ITI57ITI57-003reviewedTestable 1 1 The receiving actor shall be able to manage the following attributes on DocumentEntry, Folder, and Association objects: logicalID version availabilityStatus, which require special handling dictated by metadata update20Section 3.57.4.1.39/17/19 11:30:06 AM by aeschlimann
ITI57ITI57-004reviewedTestable 1 1 The receiving actor SHALL be capable of storing multiple versions of DocumentEntry and Folder metadata objects20Section 3.57.4.1.38/28/19 5:31:50 PM by ycadoret
ITI57ITI57-005reviewedTestable 1 1 A Document Registry then it shall make stored versions of DocumentEntry and Folder metadata objects available through the Registry Stored Query [ITI-18] transaction20Section 3.57.4.1.39/17/19 11:29:59 AM by aeschlimann
ITI57ITI57-006reviewedTestable 1 1 An Update Document Set [ITI-57] request SHALL include a SubmissionSet object20Section 3.57.4.1.3.18/28/19 11:53:32 AM by ycadoret
ITI57ITI57-007reviewedTestable 1 1 An Update Document Set request [ITI-57] shall not include initial versions of DocumentEntry or Folder objects. In a request, initial versions are recognized by having entryUUID = logicalID or logicalID missing20Section 3.57.4.1.3.18/28/19 11:53:40 AM by ycadoret
ITI57ITI57-008reviewedTestable 1 1 An updated version of a DocumentEntry object, when included in an Update Document Set request [ITI-57], SHALL be a complete DocumentEntry object. Individual attributes cannot be submitted alone 21Section 3.57.4.1.3.18/28/19 11:53:59 AM by ycadoret
ITI57ITI57-009reviewedTestable 1 1 An updated version of a Folder object, when included in an Update Document Set request [ITI-57], shall be a complete Folder object. Individual attributes cannot be submitted alone21Section 3.57.4.1.3.18/28/19 11:54:07 AM by ycadoret
ITI57ITI57-010reviewedTestable 1 1 All metadata objects in an Update Document Set Request [ITI-57] message shall have an entryUUID (id) attribute21Section 3.57.4.1.3.18/28/19 11:54:12 AM by ycadoret
ITI57ITI57-011reviewedTestable 1 1 Metadata objects entryUUID (id) attribute MAY be coded as a UUID or symbolic nam21Section 3.57.4.1.3.18/28/19 11:54:28 AM by ycadoret
ITI57ITI57-012reviewedTestable 1 1 Metadata objects entryUUID (id) attribute SHALL be used by the receiving actor when reporting errors21Section 3.57.4.1.3.18/28/19 5:29:07 PM by ycadoret
ITI57ITI57-013reviewedTestable 1 1 The submission of metadata objects: DocumentEntries, Folders, Associations; in the support of metadata versioning follows the same rules as defined for the Register Document Set-b [ITI-42] transaction or Provide and Register Document Set-b [ITI-41] transaction. These rules are defined in ITI TF-3: 4.2 and 4.321Section 3.57.4.1.3.18/28/19 5:32:19 PM by ycadoret
ITI57ITI57-014reviewedTestable 1 1 A single Update Document Set transaction MAY contain both an Update DocumentEntry Metadata operation and an Update DocumentEntry Status operation targeting the same logical DocumentEntry.21Section 3.57.4.1.3.18/28/19 11:55:15 AM by ycadoret
ITI57ITI57-015reviewedTestable 1 1 When a single Update Document Set transaction contains both an Update DocumentEntry Metadata operation and an Update DocumentEntry Status operation targeting the same logical DocumentEntry, the Document Registry or Document Recipient SHALL create the new DocumentEntry version and then apply the new availablityStatus value to this new version. The previous version, the one present before the processing of this transaction began, SHALL not be modified21Section 3.57.4.1.3.18/28/19 5:28:48 PM by ycadoret
ITI57ITI57-016reviewedTestable 1 1 A single Update Document Set transaction MAY contain both an Update Folder Metadata operation and an Update Folder Status operation targeting the same logical Folder21Section 3.57.4.1.3.18/28/19 11:55:33 AM by ycadoret
ITI57ITI57-017reviewedTestable 1 1 When a single Update Document Set transaction contains both an Update Folder Metadata operation and an Update Folder Status operation targeting the same logical Folder, the Document Registry or Document Recipient SHALL create the new Folder version and apply the new availablityStatus value to this new version21Section 3.57.4.1.3.18/28/19 5:25:46 PM by ycadoret
ITI57ITI57-018reviewedTestable 1 1 A single Update Document Set transaction SHALL not contain multiple Update (DocumentEntry or Folder) Metadata operations targeting the same logical object21Section 3.57.4.1.3.18/28/19 11:56:03 AM by ycadoret
ITI57ITI57-019reviewedTestable 1 1 A single Update Document Set transaction SHALL not contain multiple Update (DocumentEntry or Folder or Association) Status operations targeting the same logical object21Section 3.57.4.1.3.18/28/19 11:56:13 AM by ycadoret
ITI57ITI57-020reviewedTestable 1 1 At any point in time there SHALL be at most one version of a logical DocumentEntry object with status Approved in the registry/recipient. If this version exists it shall always be the most recent version21Section 3.57.4.1.3.19/17/19 11:29:47 AM by aeschlimann