diff --git a/tx/languages.md b/tx/languages.md index 215308f5..a170f837 100644 --- a/tx/languages.md +++ b/tx/languages.md @@ -34,9 +34,9 @@ http://hl7.org/fhir/tools/StructureDefinion/valueset-expansion-param extension * Using the http Accept-Language header * ValueSet.language -All accept multiple languages with weights per the Accept-Language specification; which to use is a matter -of operational control on the client. These tests require that a server support all four. The sequence of -pre-eminance is as in the list given above. +The first three may contain multiple languages with weights per the Accept-Language specification; which to use is a matter +of operational control on the client. ValueSet Language is a single language code as described in BCP-47. These tests require +that a server support all four approaches. The sequence of pre-eminance is as in the list given above. Each of the tests below comes as a set of variants, depending on how the language is specified: * -param: using the displayLanguage parameter diff --git a/tx/requirements.md b/tx/requirements.md index fd9fd0dd..d6e1be49 100644 --- a/tx/requirements.md +++ b/tx/requirements.md @@ -57,16 +57,16 @@ If the server chooses to make them available elsewhere, it SHALL populate the ex * The server SHALL support system-version, check-system-version, and force-system-version * The server SHALL echo all parameters (including assumed values) in the expansion parameters * The server SHALL report with all versions of code systems used (in 'version') (this may be renamed) - * The server SHALL Support language correctly (both displayLanguage and accept-language header) - * The server SHALL support the excludeNested, includeDesignations, activeOnly, includeDefinition and property parameters + * The server SHALL Support language correctly (both displayLanguage parameter and Accept-Language header, as specified on [[languages.dd]]) + * The server SHALL support the excludeNested, includeDesignations, activeOnly, includeDefinition, property, designation parameters * For the validate-code operation: * The server SHALL support validating code+system(+version)(+display), Coding, and CodeableConcept * The server SHALL support the [mode/valueSetMode](https://jira.hl7.org/browse/FHIR-41229) parameter - * The server SHALL Support language correctly (both displayLanguage and accept-language header) + * The server SHALL Support language correctly (same locations/ruless for $expand) * The server SHALL support the [inferSystem](https://jira.hl7.org/browse/FHIR-41431) parameter - * The server SHALL return an issues parameter + * The server SHALL return an issues parameter when there are issues to return * The server SHALL return system, code and display for the code that it considered valid, along with the version if this is known * The server SHOULD return a x-caused-by-unknown-system parameter for each code system it did not support