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

Assertion

Applies to

Applied to
Not applied to

Coverage

Covered by
Not covered by
Id scheme
Assertion id
Status
Testable?
#Coverage
#Applies to
Comment
Predicate
Page
Tags
Last changed
Actions
ITI48ITI48-004to be reviewedTestable 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.273Section 3.48.4.1.37/9/19 11:18:49 AM by aeschlimann
ITI48ITI48-005to be reviewedTestable 1 2 If no version is specified in the Request, then the most recent version shall be returned.273Section 3.48.4.1.37/9/19 11:18:49 AM by aeschlimann
ITI48ITI48-009to be reviewedTestable 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. 273Section 3.48.4.2.27/9/19 11:18:50 AM by aeschlimann
ITI48ITI48-010to be reviewedTestable 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. 274Section 3.48.2.27/9/19 11:18:50 AM by aeschlimann
ITI48ITI48-011to be reviewedTestable 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.274Section 3.48.4.2.27/9/19 11:18:50 AM by aeschlimann
ITI48ITI48-012to be reviewedTestable 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.274Section 3.48.4.2.27/9/19 11:18:50 AM by aeschlimann
ITI48ITI48-013to be reviewedTestable 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.274Section 3.48.4.2.27/9/19 11:18:50 AM by aeschlimann
ITI48ITI48-014to be reviewedTestable 1 2 A Value Set Repository shall return the Expanded Value Set indicated in the request.274Section 3.48.4.2.37/9/19 11:18:50 AM by aeschlimann
ITI48ITI48-015to be reviewedTestable 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.274Section 3.48.4.2.37/9/19 11:18:50 AM by aeschlimann
ITI48ITI48-016to be reviewedTestable 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 permitted274Section 3.48.4.2.37/9/19 11:18:50 AM by aeschlimann
ITI48ITI48-017to be reviewedTestable 1 2 The ConceptList shall have the same code values for the Value Set in question.274Section 3.48.4.2.37/9/19 11:18:50 AM by aeschlimann
ITI48ITI48-018to be reviewedTestable 1 2 The displayName may have a different value appropriate to the locale.274Section 3.48.4.2.37/9/19 11:18:50 AM by aeschlimann
ITI48ITI48-019to be reviewedTestable 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.274Section 3.48.4.2.37/9/19 11:18:50 AM by aeschlimann
ITI48ITI48-027to be reviewedTestable 0 3 Value Set Repositories shall include within the response message payload for the SOAP Binding Option the <ihe:RetrieveValueSetResponse/> element which contains an optional /ihe:RetrieveValueSetResponse@cacheExpirationHint attribute, indicating that the Value Set Consumer should obtain a new copy before this date and time.276Section 3.48.5.17/9/19 11:18:51 AM by aeschlimann
ITI48ITI48-028to be reviewedTestable 0 3 Value Set Repositories shall include within the response message payload for the SOAP Binding Option the <ihe:RetrieveValueSetResponse/> element which contains a required /ihe:RetrieveValueSetResponse/ihe:ValueSet element.276Figure 3.48.5.17/9/19 11:18:51 AM by aeschlimann
ITI48ITI48-029to be reviewedTestable 0 3 The only occurrence of more than one ConceptList element in a response message shall be for the purpose of returning multiple language representations of the same value set.276Section 3.48.5.17/9/19 11:18:51 AM by aeschlimann
ITI48ITI48-032to be reviewedTestable 0 2 Value Set Repositories shall format the response to the HTTP GET operation as an HTTP response message as defined in IETF RFC2616.277Section 3.48.5.2.27/9/19 11:18:51 AM by aeschlimann
ITI48ITI48-033to be reviewedTestable 0 2 The Content-Type field of the HTTP header shall be text/xml (see Section 14.4 of IETF RFC2616). 277Section 3.48.5.2.27/9/19 11:18:51 AM by aeschlimann
ITI48ITI48-034to be reviewedTestable 0 2 The content of the HTTP response message shall be an XML encoded Expanded Value Set that complies with the SVS schema. 277Section 3.48.5.2.27/9/19 11:18:51 AM by aeschlimann
ITI48ITI48-035to be reviewedTestable 0 2 The XML format shall be identical to the body of the SOAP response described in the SOAP binding.277Section 3.48.5.2.27/9/19 11:18:51 AM by aeschlimann