| ITI18-MU | ITI18-MU-001 | reviewed | Testable |
0
|
0
| | The default value of $MetadataLevel is 1 (one). | 46 | Section 3.18.4.1.2.3.5.1.1 | 8/27/19 2:27:31 PM by aeschlimann |
|
| ITI18-MU | ITI18-MU-002 | reviewed | Testable |
0
|
0
| | If $MetadataLevel is 1 (one), the Document Registry shall not return the following metadata patterns in the Stored Query response: DocumentEntry and Folder objects that are not the latest version DocumentEntry objects that have documentAvailability of urn:ihe:iti:2010:DocumentAvailability:Offline Folder objects that have availabilityStatus of urn:oasis:names:tc:ebxml-regrep:StatusType:Deprecated Association objects that have availabilityStatus of urn:oasis:names:tc:ebxml-regrep:StatusType:Deprecated | 46 | Section 3.18.4.1.2.3.5.1.1 | 8/27/19 2:27:32 PM by aeschlimann |
|
| ITI18-MU | ITI18-MU-003 | reviewed | Testable |
0
|
0
| | Stored Query requests coded with $MetadataLevel value of 2 shall return without the above restrictions as is appropriate for the individual Stored Query and its other parameters. | 46 | Section 3.18.4.1.2.3.5.1.1 | 8/27/19 2:28:23 PM by aeschlimann |
|
| ITI18-MU | ITI18-MU-004 | reviewed | Testable |
0
|
0
| | The $MetadataLevel parameter shall be coded as a number. See Section 3.18.4.1.2.3.5 | 46 | Section 3.18.4.1.2.3.5.1.1 | 8/27/19 2:28:25 PM by aeschlimann |
|
| ITI18-MU | ITI18-MU-005 | reviewed | Testable |
0
|
0
| | Section 3.18.4.1.2.3.5.1.2 defines new Stored Query parameters added by Document Metadata Update | 47 | Section 3.18.4.1.2.3.5.1.2 | 8/27/19 2:28:26 PM by aeschlimann |
|
| ITI18-MU | ITI18-MU-006 | reviewed | Testable |
0
|
0
| | If the Document Registry supports the Document Metadata Update Option and this parameter includes the value urn:oasis:names:tc:ebxml-regrep:StatusType:Deprecated then the response may include multiple versions of a DocumentEntry object. See ITI TF-3: 4.1.5 for guidance on interpreting these results | 49 | Section 3.18.4.1.2.3.7.1 | 8/27/19 2:28:28 PM by aeschlimann |
|
| ITI18-MU | ITI18-MU-007 | reviewed | Testable |
0
|
0
| | FindDocuments Stored Query may include parameter $XDSDocumentEntryDocumentAvailability | 49 | Section 3.18.4.1.2.3.7.1 | 8/27/19 2:28:29 PM by aeschlimann |
|
| ITI18-MU | ITI18-MU-008 | reviewed | Testable |
0
|
0
| | FindDocuments Stored query may contain $MetadataLevel parameter | 49 | Section 3.18.4.1.2.3.7.1 | 8/27/19 2:28:31 PM by aeschlimann |
|
| ITI18-MU | ITI18-MU-009 | reviewed | Testable |
0
|
0
| | FindFolders Stored Query may contain $MetadataLevel parameter | 49 | Section 3.18.4.1.2.3.7.2 | 8/27/19 2:28:33 PM by aeschlimann |
|
| ITI18-MU | ITI18-MU-010 | reviewed | Testable |
0
|
0
| | In the case of a FindFolders Stored Query, If the Document Registry supports the Document Metadata Update Option and this parameter includes the value urn:oasis:names:tc:ebxml-regrep:StatusType:Deprecated then the response may include multiple versions of a Folder object. See ITI TF-3: 4.1.5 for guidance on interpreting these results. | 49 | Section 3.17.4.1.2.3.7.2 | 8/27/19 2:28:35 PM by aeschlimann |
|
| ITI18-MU | ITI18-MU-011 | reviewed | Testable |
0
|
0
| | In the case of a FindFolders Stored Query, the parameter setting of $MetadataLevel equals 1 shall not inhibit the return of non-Approved Folders. This is controlled only by $XDSFolderStatus. See Section 3.18.4.1.2.3.5.1 | 49 | Section 3.18.4.1.2.3.7.2 | 8/27/19 2:30:09 PM by aeschlimann |
|
| ITI18-MU | ITI18-MU-012 | reviewed | Testable |
0
|
0
| | In the case of a GetAll Stored Query, if the Document Registry supports the Document Metadata Update Option and $XDSDocumentEntryStatus or $XDSFolderStatus parameter includes the value urn:oasis:names:tc:ebxml-regrep:StatusType:Deprecated then the response may include multiple versions of a DocumentEntry/Folder object. See ITI TF-3: 4.1.5 for guidance on interpreting these results | 50 | Section 3.18.4.1.2.3.7.4 | 8/27/19 2:31:13 PM by aeschlimann |
|
| ITI18-MU | ITI18-MU-013 | reviewed | Testable |
0
|
0
| | GetAll Stored Query may contain parameter $XDSAssociationStatus | 50 | Section 3.18.4.1.2.3.7.5 | 8/27/19 2:31:20 PM by aeschlimann |
|
| ITI18-MU | ITI18-MU-014 | reviewed | Testable |
0
|
0
| | GetAll Stored Query may contain parameter $MetadataLevel | 50 | Section 3.18.4.1.2.3.7.4 | 8/27/19 2:31:21 PM by aeschlimann |
|
| ITI18-MU | ITI18-MU-015 | reviewed | Testable |
0
|
0
| | Retrieve a collection of XDSDocumentEntry objects. XDSDocumentEntry objects are selected either by their entryUUID,or uniqueID, or logicalID attribute | 50 | Section 3.18.4.1.2.3.7.5 | 8/27/19 2:31:23 PM by aeschlimann |
|
| ITI18-MU | ITI18-MU-016 | reviewed | Testable |
0
|
0
| | GetDocuments Stored Query may contain parameter $XDSDocumentEntryLogicalID | 51 | Section 3.18.4.1.2.3.7.5 | 8/27/19 2:31:24 PM by aeschlimann |
|
| ITI18-MU | ITI18-MU-017 | reviewed | Testable |
0
|
0
| | $XDSDocumentEntryEntryUUID or $XDSDocumentEntryUniqueId or $XDSDocumentEntryLogicalID shall be specified. This transaction shall return an error if more than one of theseparameters areis specified | 51 | Section 3.18.4.1.2.3.7.5 | 8/27/19 2:31:25 PM by aeschlimann |
|
| ITI18-MU | ITI18-MU-018 | reviewed | Testable |
0
|
0
| | The homeCommunityId value is specified as the home attribute on the AdhocQuery element of the query request, as in: <AdhocQuery id=... home=urn:oid:1.2.3 ... >. Document Consumer Actors shall specify the homeCommunityId value if they received a value for this attribute as part of the previous Registry Stored Query response entry, which contained the specified entryUUID, uniqueId or logicalID. See Section 3.18.4.1.2.3.8 for more details | 51 | Section 3.18.4.1.2.3.7.5 | 8/27/19 2:31:26 PM by aeschlimann |
|
| ITI18-MU | ITI18-MU-019 | reviewed | Testable |
0
|
0
| | Retrieving a DocumentEntry by its logicalID attribute returns the logical DocumentEntry, which includes all versions of that DocumentEntry object. See ITI TF-3: 4.1.5 for guidance on interpreting these results. If the Document Registry does not support the Document Metadata Update Option, $XDSDocumentEntryLogicalID parameter shall be ignored and thus cause an error because $XDSDocumentEntryEntryUUID and $XDSDocumentEntryUniqueId will be missing | 51 | Section 3.18.4.1.2.3.7.5 | 8/27/19 2:31:28 PM by aeschlimann |
|
| ITI18-MU | ITI18-MU-020 | reviewed | Testable |
0
|
0
| | Specifying $XDSDocumentEntryUniqueId parameter in a query to a Document Registry that supports the Document Metadata Update Option may return multiple DocumentEntry objects each representing a different version of the metadata. See ITI TF-3: 4.1.5 for guidance on interpreting these results. | 51 | Section 3.18.4.1.2.3.7.5 | 8/27/19 2:31:30 PM by aeschlimann |
|