ITI48 | ITI48-001 | to be reviewed | Testable |
1
|
2
| | The Retrieve Value Set Request shall carry a required id, representing the Value Set OID that identifies the Expanded Value Set within the Repository. | 273 | Section 3.48.4.1.2 | 7/9/19 11:18:49 AM by aeschlimann |
|
ITI48 | ITI48-002 | to be reviewed | Testable |
1
|
2
| | The Retrieve Value Set Request shall carry an optional version that identifies a specific version of the Expanded Value Set. If no version is specified, the Value Set Consumer is requesting the most recent version of the Value Set. | 273 | Section 3.48.4.1.2 | 7/9/19 11:18:49 AM by aeschlimann |
|
ITI48 | ITI48-003 | to be reviewed | Testable |
1
|
2
| | The Retrieve Value Set Request shall carry an optional lang parameter indicating the requested language locale for the displayName of the Value Set Concepts. | 273 | Section 3.48.4.1.2 | 7/9/19 11:18:49 AM by aeschlimann |
|
ITI48 | ITI48-004 | to be reviewed | Testable |
1
|
2
| | When receiving a Retrieve Value Set Request, a Value Set Repository shall generate a Retrieve Value Set Response containing the Expanded Value Set that corresponds to the request parameters or an error code if the Value Set could not be retrieved. | 273 | Section 3.48.4.1.3 | 7/9/19 11:18:49 AM by aeschlimann |
|
ITI48 | ITI48-005 | to be reviewed | Testable |
1
|
2
| | If no version is specified in the Request, then the most recent version shall be returned. | 273 | Section 3.48.4.1.3 | 7/9/19 11:18:49 AM by aeschlimann |
|
ITI48 | ITI48-006 | to be reviewed | Testable |
0
|
3
| The SOAP binding is covered, the HTTP binding isn't | The Value Set Repository shall support both the SOAP and HTTP bindings for this transaction. | 273 | Section 3.48.4.1.3 | 7/9/19 11:18:49 AM by aeschlimann |
|
ITI48 | ITI48-007 | to be reviewed | Testable |
0
|
2
| | If the Value Set Consumer sends the request using the SOAP binding, the Value Set Repository shall respond using the SOAP binding. | 273 | Section 3.48.4.1.3 | 7/9/19 11:18:49 AM by aeschlimann |
|
ITI48 | ITI48-008 | to be reviewed | Testable |
0
|
2
| | If the Value Set Consumer sends the request using the HTTP binding, the Value Set Repository shall respond using the HTTP binding | 273 | Section 3.48.4.1.3 | 7/9/19 11:18:49 AM by aeschlimann |
|
ITI48 | ITI48-009 | to be reviewed | Testable |
1
|
2
| | The Retrieve Value Set Response Message shall carry for the returned Expanded Value Set a required id, representing the Value Set OID that identifies the Value Set within the Value Set Repository. This OID shall be the same as the Value Set OID in the received Retrieve Value Set Request Message. | 273 | Section 3.48.4.2.2 | 7/9/19 11:18:50 AM by aeschlimann |
|
ITI48 | ITI48-010 | to be reviewed | Testable |
1
|
2
| | The Retrieve Value Set Response Message shall carry the following information for the returned Expanded Value Set a required displayName that can be used for display purposes. | 274 | Section 3.48.2.2 | 7/9/19 11:18:50 AM by aeschlimann |
|
ITI48 | ITI48-011 | to be reviewed | Testable |
1
|
2
| | The Retrieve Value Set Response Message shall carry the following information for the returned Expanded Value Set an optional version that shall be present if the Expanded Value Set has a version, that identifies the specific version of the Value Set returned. | 274 | Section 3.48.4.2.2 | 7/9/19 11:18:50 AM by aeschlimann |
|
ITI48 | ITI48-012 | to be reviewed | Testable |
1
|
2
| | The Retrieve Value Set Response Message shall carry the following information for the returned Expanded Value Set an optional cacheExpirationHint indicating that the Value Set Consumer is not expected to change before this date and time. If the request and the response use the HTTP binding, this information shall be also present in the HTTP Expire header of the response. For details, please see Section 14.21 of IETF RFC2616. | 274 | Section 3.48.4.2.2 | 7/9/19 11:18:50 AM by aeschlimann |
|
ITI48 | ITI48-013 | to be reviewed | Testable |
1
|
2
| | The Retrieve Value Set Response Message shall carry the following information for the returned Expanded Value Set one or more ConceptList, which provides the Concepts of the Expanded Value Set. If there are multiple translations of the Value Set, each translation is returned as a separate ConceptList, where only the displayName of each Concept, and the language locale represented by xml:lang are different. | 274 | Section 3.48.4.2.2 | 7/9/19 11:18:50 AM by aeschlimann |
|
ITI48 | ITI48-014 | to be reviewed | Testable |
1
|
2
| | A Value Set Repository shall return the Expanded Value Set indicated in the request. | 274 | Section 3.48.4.2.3 | 7/9/19 11:18:50 AM by aeschlimann |
|
ITI48 | ITI48-015 | to be reviewed | Testable |
1
|
2
| | If the Value Set Consumer requested a specific language locale, the Value Set Repository shall return only the requested translation of the Expanded Value Set. | 274 | Section 3.48.4.2.3 | 7/9/19 11:18:50 AM by aeschlimann |
|
ITI48 | ITI48-016 | to be reviewed | Testable |
1
|
2
| | If the Value Set Consumer did not request a specific language locale, the Value Set Repository shall return all known translations of the Expanded Value Set. This is the only case where more than one ConceptList XML element shall be permitted | 274 | Section 3.48.4.2.3 | 7/9/19 11:18:50 AM by aeschlimann |
|
ITI48 | ITI48-017 | to be reviewed | Testable |
1
|
2
| | The ConceptList shall have the same code values for the Value Set in question. | 274 | Section 3.48.4.2.3 | 7/9/19 11:18:50 AM by aeschlimann |
|
ITI48 | ITI48-018 | to be reviewed | Testable |
1
|
2
| | The displayName may have a different value appropriate to the locale. | 274 | Section 3.48.4.2.3 | 7/9/19 11:18:50 AM by aeschlimann |
|
ITI48 | ITI48-019 | to be reviewed | Testable |
1
|
2
| | The Value Set Repository shall return the Expanded Value Set or an error code in case the Value Set could not be expanded. | 274 | Section 3.48.4.2.3 | 7/9/19 11:18:50 AM by aeschlimann |
|
ITI48 | ITI48-020 | to be reviewed | Testable |
1
|
2
| | Value Set Consumers which support the SOAP Binding Option shall follow the rules for Web Services transactions outlined in ITI TF-2x: Appendix V. | 275 | Section 3.48.5.1 | 7/9/19 11:18:50 AM by aeschlimann |
|