| ITI-92 | ITI-001 | to be reviewed | Testable |
3
|
4
| | Restricted Update Document Set [ITI-92] is used by the Update Initiator and Update Responder (See Section 3.92 Restricted Update Document Set) | 24 | Section 3.92 | 9/30/22 2:33:19 PM by vhofman |
|
| ITI-92 | ITI-002 | to be reviewed | Testable |
3
|
4
| | The Restricted Update Document Set Request message shall use SOAP 1.2 and Simple SOAP (See Section 3.92.4.1.2 Message Semantics) | 25 | Section 3.92.4.1.2 | 9/30/22 2:33:20 PM by vhofman |
|
| ITI-92 | ITI-003 | to be reviewed | Testable |
3
|
4
| | Implementers of this transaction shall comply with all requirements described in ITI TF-2x: Appendix V.3: Synchronous and Asynchronous Web Services (see Section 3.92.4.1.2 Message Semantics) | 25 | Section 3.92.4.1.2 | 9/30/22 2:33:30 PM by vhofman |
|
| ITI-92 | ITI-005 | to be reviewed | Testable |
2
|
3
| | The Update Responder shall use Metadata Annotations when processing the request for storage (see Section 3.92.4.1.2.2 Metadata Annotations) | 27 | Section 3.92.4.1.2.2 | 9/30/22 2:33:30 PM by vhofman |
|
| ITI-92 | ITI-006 | to be reviewed | Testable |
2
|
3
| | The default value for Association Propagation is "yes" (See Section 3.92.4.1.2.2.2 Association Propagation) | 28 | Section 3.92.4.1.2.2.2 | 9/30/22 2:33:30 PM by vhofman |
|
| ITI-92 | ITI-007 | to be reviewed | Testable |
2
|
3
| | The Update Responder shall return the status and any error codes incurred during the processing of the request in its response message (See Section 3.92.4.1.3 Expected Actions) | 29 | Section 3.92.4.1.3 | 9/30/22 2:33:30 PM by vhofman |
|
| ITI-92 | ITI-008 | to be reviewed | Testable |
2
|
3
| | If the value is not known, the Update Responder shall return the error code, XDSUnknownCommunity (See Section 3.92.4.1.3.1 Forward Update Option) | 29 | Section 3.92.4.1.3.1 | 9/30/22 2:33:30 PM by vhofman |
|
| ITI-92 | ITI-009 | to be reviewed | Testable |
2
|
3
| | If the value is omitted, the Update Responder shall return the error code, XDSMissingHomeCommunityId (See Section 3.92.4.1.3.1 Forward Update Option) | 29 | Section 3.92.4.1.3.1 | 9/30/22 2:33:30 PM by vhofman |
|
| ITI-92 | ITI-010 | to be reviewed | Testable |
2
|
3
| | The current version of the stored logical metadata object shall always have an availabilityStatus equal to urn:oasis:names:tc:ebxml-regrep:StatusType:Approved and prior versions shall have their availabilityStatus attribute set tourn:oasis:names:tc:ebxml-regrep:StatusType:Deprecated (see Section 3.92.4.1.3.4.1 Storage Requirements) | 30 | Section 3.92.4.1.3.4.1 | 9/30/22 2:33:30 PM by vhofman |
|
| ITI-92 | ITI-011 | to be reviewed | Testable |
2
|
3
| | Unless a more specific code is provided within the validation, the Update Responder shall return the error code, XDSMetadataUpdateError, for any error returned during processing (See Section 3.92.4.1.3.4 Request Validation) | 31 | Section 3.92.4.1.3.4 | 9/30/22 2:33:30 PM by vhofman |
|
| ITI-92 | ITI-012 | to be reviewed | Testable |
2
|
3
| | The system shall contain an existing DocumentEntry (Stable or On-Demand) metadata object instance with status of urn:oasis:names:tc:ebxml-regrep:StatusType:Approved (See Section 3.92.4.1.3.4 Request Validation) | 32 | Section 3.92.4.1.3.4 | 9/30/22 2:33:30 PM by vhofman |
|
| ITI-92 | ITI-013 | to be reviewed | Testable |
2
|
3
| | The SS-DE HasMember Association shall be present and have a Slot with name PreviousVersion (See Section 3.92.4.1.3.4 Request Validation) | 32 | Section 3.92.4.1.3.4 | 9/30/22 2:33:30 PM by vhofman |
|
| ITI-92 | ITI-014 | to be reviewed | Testable |
2
|
3
| | The submitted and existing DocumentEntry objects shall have the same values for both the logicalID ans uniqueID attribute (See Section 3.92.4.1.3.4 Request Validation) | 32 | Section 3.92.4.1.3.4 | 9/30/22 2:33:30 PM by vhofman |
|
| ITI-92 | ITI-015 | to be reviewed | Testable |
2
|
3
| | The submitted and existing DocumentEntry objects shall have the same values for the patientID attributes (see Section 3.92.4.1.3.4 Request Validation) | 32 | Section 3.92.4.1.3.4 | 9/30/22 2:33:30 PM by vhofman |
|
| ITI-92 | ITI-016 | to be reviewed | Testable |
2
|
3
| | All metadata objects must conform to the rules for content and format defined in ITI TF-3: 4.2 and 4.3. Stable Document Entry object metadata must confirm to the requirements defined in ITI TF-2b: 3.42 for the Register Document Set-b [ITI-42] transaction (see Section 3.92.4.1.3.4 Request Validation) | 32 | Section 3.92.4.1.3.4 | 9/30/22 2:33:30 PM by vhofman |
|
| ITI-92 | ITI-017 | to be reviewed | Testable |
2
|
3
| | On-Demand Document Entry objects must conform to the requirements defined in ITI TF-2b: 3.61 for the Register On-Demand Document Entry [ITI-61] transaction (see Section 3.92.4.1.3.4 Request Validation) | 32 | Section 3.92.4.1.3.4 | 9/30/22 2:33:30 PM by vhofman |
|
| ITI-92 | ITI-018 | to be reviewed | Testable |
2
|
3
| | The Restricted Update Document Set Response message shall use SOAP 1.2 and Simple SOAP (see Section 3.92.4.2.2 Message Semantics) | 33 | Section 3.92.4.2.2 | 9/30/22 2:33:30 PM by vhofman |
|
| ITI-92 | ITI-019 | to be reviewed | Testable |
2
|
3
| | Implementers of this transaction shall comply with all requirements described in ITI TF-2x: Appendix V.3: Synchronous and Asynchronous Web Services (see Section 3.92.4.2.2 Message Semantics) | 33 | Section 3.92.4.2.2 | 9/30/22 2:33:30 PM by vhofman |
|
| RMU | RMU-001 | to be reviewed | Testable |
3
|
4
| | Actors must implement ITI-92 transaction. | 10 | Table 48.1-1 | 9/30/22 2:33:53 PM by vhofman |
|
| RMU | RMU-002 | to be reviewed | Testable |
3
|
4
| | To claim compliance with this profile, an actor shall support all required transactions (labeled R) (Section 48.2 RMU Actors, Transactions, and Content Modules) | 10 | Section 48.1 | 9/30/22 2:33:53 PM by vhofman |
|