Search Criteria : 17 assertions found for this search Review filtered assertions


Applies to

Applied to
Not applied to


Covered by
Not covered by
Id scheme
Assertion id
#Applies to
Last changed
XDSMUXDSMU-001reviewedTestable 0 0 DocumentEntry.documentAvailability shall have a single value70Section 11:07:26 AM by aeschlimann
XDSMUXDSMU-002reviewedTestable 0 0 Document Registry May implement Update Document Set [ITI-57] transaction71Section 11:07:26 AM by aeschlimann
XDSMUXDSMU-003reviewedTestable 0 0 DocumentEntry.logicalID shall be a UUID71Section 11:07:26 AM by aeschlimann
XDSMUXDSMU-004reviewedTestable 0 0 DocumentEntry.logicalID shall never be submitted in symbolic form71Section 9/17/19 11:07:26 AM by aeschlimann
XDSMUXDSMU-005reviewedTestable 0 0 The value of the logicalID is coded in the lid XML attribute on the ExtrinsicObject representing the DocumentEntry71Section 11:07:26 AM by aeschlimann
XDSMUXDSMU-006reviewedTestable 0 0 Folder.logicalID value shall be an UUID73Section 11:07:26 AM by aeschlimann
XDSMUXDSMU-007reviewedTestable 0 0 Folder.logicalID value is coded in the lid XML attribute on the RegistryPackage representing the Folder73Section 11:07:26 AM by aeschlimann
XDSMUXDSMU-008reviewedTestable 0 0 The following form, with entryUUID (id) different from logicalID (lid), shall only be submitted in the Update Document Set transaction73Section 11:07:26 AM by aeschlimann
XDSMUXDSMU-009reviewedTestable 0 0 RegistryError/@errorCode in ITI-41 response shall be from : DocumentQueued, InvalidDocumentContent, PartialAppendContentNotProcessed, PartialFolderContentNotProcessed, PartialReplaceContentNotProcessed, PartialTransformNotProcessed, PartialTransformReplaceNotProcessed, XDSDuplicateUniqueIdInRegistry, XDSExtraMetadataNotSaved, XDSMissingDocument, XDSMissingDocumentMetadata, XDSPatientIdDoesNotMatch, XDSRegistryBusy, XDSRepositoryBusy, XDSRegistryDeprecatedDocumentError, XDSRegistryDuplicateUniqueIdInMessage, XDSRepositoryDuplicateUniqueIdInMessage, XDSRegistryError, XDSRepositoryError, XDSRegistryMetadataError, XDSRepositoryMetadataError, XDSRegistryNotAvailable, XDSRegistryOutOfResources, XDSRepositoryOutOfResources, XDSUnknownPatientId, XDSMetadataUpdateError, XDSPatientIDReconciliationError, XDSMetadataUpdateOperationError, XDSMetadataVersionError74Table 11:07:26 AM by aeschlimann
XDSMUXDSMU-012reviewedTestable 1 1 Document Registry May implement Update Document Set [ITI-57] transaction10Table 10.1-1b8/27/19 2:35:23 PM by aeschlimann
XDSMUXDSMU-018reviewedTestable 1 1 Document Administrator shall implement Update Document Set [ITI-57] transaction 10Table 10.1-1b8/27/19 2:35:24 PM by aeschlimann
XDSMUXDSMU-019reviewedTestable 0 1 Covered in XDS (XDS.b-10 assertion)Document Administrator may implement Registry Stored Query [ITI-18] transaction10Table 10.1-1b8/27/19 2:35:25 PM by aeschlimann
XDSMUXDSMU-020reviewedTestable 1 1 The Document Administrator shall be capable of generating at least one of the operations documented in ITI TF-2b: 2:35:27 PM by aeschlimann
XDSMUXDSMU-021reviewedTestable 0 1 Document Registry may support the Document Metadata Update option11Table 10.2-1b8/27/19 2:35:31 PM by aeschlimann
XDSMUXDSMU-022reviewedTestable 0 1 Document Consumer may support the Document Metadata Update option11Table 10.2-1b8/27/19 2:35:32 PM by aeschlimann
XDSMUXDSMU-023reviewedTestable 0 1 A Document Registry declares the Document Metadata Update Option when it is able to accept metadata updates via the Update Document Set [ITI-57] transaction (see ITI TF-2b: for details). All operations documented in ITI TF-2b: shall be supported. 12Section 10.2.108/27/19 2:35:33 PM by aeschlimann
XDSMUXDSMU-024reviewedTestable 0 1 A Document Registry declares the Document Metadata Update Option when it is able to Expose the metadata updates via the Registry Stored Query [ITI-18] transaction (See ITI TF-2a: for details)12Section 10.2.108/27/19 2:35:34 PM by aeschlimann