IHEXDS | IHEXDS-153 | | Testable |
0
|
0
| | RegistryError SHALL contain the attribute codeContext | 101 | Section 4.2.4.1 | 9/3/18 6:09:08 PM by Meenal T |
|
IHEXDS | IHEXDS-154 | | Testable |
0
|
0
| | RegistryError SHALL contain severity attribute | 101 | Section 4.2.4.1 | 9/3/18 6:09:09 PM by Meenal T |
|
IHEXDS | IHEXDS-154-2 | | Testable |
0
|
0
| | RegistryError/@severity shall be one of : oasis:names:tc:ebxml-regrep:ErrorSeverityType:Error / urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Warning
| 101 | Section 4.2.4.1 | 9/3/18 6:09:09 PM by Meenal T |
|
IHEXDS | IHEXDS-155 | | Testable |
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 | 103 | Table 4.2.4.1-2 | 9/3/18 6:09:09 PM by Meenal T |
|
IHEXDS | IHEXDS-156 | | Testable |
0
|
0
| | RegistryError/@errorCode in ITI-42 response shall be from : XDSDuplicateUniqueIdInRegistry, XDSExtraMetadataNotSaved, XDSNonIdenticalHash, XDSNonIdenticalSize , XDSPatientIdDoesNotMatch, XDSRegistryBusy, XDSRegistryDeprecatedDocumentError, XDSRegistryDuplicateUniqueIdInMessage, XDSRepositoryDuplicateUniqueIdInMessage, XDSRegistryError, XDSRegistryMetadataError, XDSRegistryOutOfResources, XDSUnknownPatientId | 103 | Table 4.2.4.1-2 | 9/3/18 6:09:09 PM by Meenal T |
|
IHEXDS | IHEXDS-157 | | Testable |
0
|
0
| | RegistryError/@errorCode in ITI-18 response shall be from : XDSMissingHomeCommunityId, XDSRegistryBusy, XDSRegistryError, XDSRegistryOutOfResources, XDSResultNotSinglePatient, XDSStoredQueryMissingParam, XDSStoredQueryParamNumber, XDSTooManyResults, XDSUnavailableCommunity, XDSUnknownCommunity, XDSUnknownStoredQuery | 103 | Table 4.2.4.1-2 | 9/3/18 6:09:09 PM by Meenal T |
|
IHEXDS | IHEXDS-158 | | Testable |
0
|
0
| | RegistryError/@errorCode in ITI-43 response shall be from : XDSDocumentUniqueIdError, XDSMissingHomeCommunityId, XDSRepositoryBusy, XDSRepositoryError, XDSRepositoryOutOfResources, XDSResultNotSinglePatient, XDSUnavailableCommunity, XDSUnknownCommunity, | 103 | Table 4.2.4.1-2 | 9/3/18 6:09:10 PM by Meenal T |
|
IHEXDS | IHEXDS-160 | | Testable |
0
|
0
| | The RegistryError elements shall be contained within an ebXML RegistryErrorList element in the ebXML RegistryResponse or ebXML AdhocQueryResponse | 106 | Section 4.2.4.2 | 9/3/18 6:09:10 PM by Meenal T |
|
IHEXDS | IHEXDS-161 | | Testable |
0
|
0
| | The status attribute of the RegistryResponse or AdhocQueryResponse shall be one of the following values:
urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Success
urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Failure
urn:ihe:iti:2007:ResponseStatusType:PartialSuccess | 106 | Section 4.2.4.2 | 9/3/18 6:09:10 PM by Meenal T |
|
IHEXDS | IHEXDS-162 | | Testable |
0
|
0
| | The highestSeverity attribute may be present in a RegistryErrorList. If present, it shall contain the severity of the most severe of the RegistryErrors in the RegistryErrorList | 106 | Section 4.2.4.2 | 9/3/18 6:09:10 PM by Meenal T |
|
IHEXDS | IHEXDS-163 | | Testable |
0
|
0
| | RegistryResponse status of ITI-41 SHALL be from : urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Success / urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Failure | 106 | Table 4.2.4.2-1 | 9/3/18 6:09:11 PM by Meenal T |
|
IHEXDS | IHEXDS-164 | | Testable |
0
|
0
| | RegistryResponse status of ITI-42 SHALL be from : urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Success / urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Failure | 106 | Table 4.2.4.2-2 | 9/3/18 6:09:11 PM by Meenal T |
|
IHEXDS | IHEXDS-165 | | Testable |
0
|
0
| | RegistryResponse status of ITI-18 SHALL be from : urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Success / urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Failure / urn:ihe:iti:2007:ResponseStatusType:PartialSuccess | 107 | Table 4.2.4.2-3 | 9/3/18 6:09:11 PM by Meenal T |
|
IHEXDS | IHEXDS-165-2 | | Testable |
0
|
0
| | RegistryResponse status of ITI-43 SHALL be from :urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Success / urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Failure / urn:ihe:iti:2007:ResponseStatusType:PartialSuccess | 107 | Table 4.2.4.2-4 | 9/3/18 6:09:11 PM by Meenal T |
|
IHEXDS | IHEXDS-166 | to be reviewed | Testable |
0
|
0
| | Duplicate registration of a document - A document and its metadata are submitted to the XDS Document Repository as part of a Provide and Register Document Set [ITI-41] transaction. This document already exists in one or more Document Repositories and is already represented in the Document Registry. It is submitted with a new (not previously used) entryUUID for the DocumentEntry and associated ancillary objects. The Document Registry shall accept such duplicate registration of the documents | 105 | Section 4.3.1.2.2 | 3/20/15 11:59:23 AM by Abderrazek Boufahja |
|
IHEXDS | IHEXDS-167 | to be reviewed | Testable |
0
|
0
| | Duplicate document id submitted to repository - A document with its associated metadata is submitted to an XDS Document Repository. A document with the same DocumentEntry.uniqueId is present in the repository but the DocumentEntry.hash is different. This is an error and the Submission Request shall be rejected by the Document Repository. | 105 | Section 4.3.1.2.2 | 3/20/15 11:59:23 AM by Abderrazek Boufahja |
|
IHEXDS | IHEXDS-168 | to be reviewed | Testable |
0
|
0
| | Duplicate document Id submitted to registry - Metadata representing a document (DocumentEntry) is part of a Registry Submission Request. A DocumentEntry object with the same uniqueId is present in the registry but the hash is different. This is an error and the Submission Request shall be rejected by the XDS Document Registry | 105 | Section 4.3.1.2.2 | 3/20/15 11:59:23 AM by Abderrazek Boufahja |
|
IHEXDS | IHEXDS-169 | to be reviewed | Testable |
0
|
0
| | Registries shall only accept and produce lowercase UUIDs as specified in section 4.2.3.1.4. | 106 | Section 4.3.1.2.2 | 3/20/15 11:59:23 AM by Abderrazek Boufahja |
|
IHEXDS | IHEXDS-170 | to be reviewed | Testable |
0
|
0
| | If any part of the Submission Request Processing fails, the entire transaction shall fail and no changes result | 106 | Section 4.3.1.2.3 | 3/20/15 11:59:23 AM by Abderrazek Boufahja |
|
IHEXDS | IHEXDS-171 | to be reviewed | Testable |
0
|
0
| | If an error occurs, storing documents in the repository then all documents stored as part of the Repository Submission Request shall be removed | 106 | Section 4.3.1.2.3 | 3/20/15 11:59:23 AM by Abderrazek Boufahja |
|