FHIR API $translate - include display (term) in response when possible

[JonZammit]

This is a feature request.

When using the $translate operation, when a match has been identified, and the match is a SNOMED CT concept(s), it would be useful if the response from Snowstorm included a display term in the match.concept out parameter.

Example response with display term "Anaesthetist" included:

{
    "resourceType": "Parameters",
    "parameter": [
        {
            "name": "result",
            "valueBoolean": true
        },
        {
            "name": "match",
            "part": [
                {
                    "name": "equivalence",
                    "valueCode": "equal"
                },
                {
                    "name": "concept",
                    "valueCoding": {
                        "system": "http://snomed.info/sct",
                        "code": "88189002",
                        "display": "Anaesthetist"
                    }
                },
                {
                    "name": "source",
                    "valueString": "http://snomed.info/sct/32506021000036107/version/20231130?fhir_cm=900000000000527005"
                }
            ]
        }
    ]
}

[kaicode]

Thanks for raising this @JonZammit. It's odd that this is not working because I believe it works for the SNOMED CT to ICD-10 translate operation when ICD-10 is loaded as a FHIR CodeSystem. I'll look into this.

[kaicode]

For the record - Jon noticed that this works as expected when the Accept-Language request header is set. We should update Snowstorm to default to "en" if there is no header present, just so something is returned for display.

[pgwilliams]

Thanks for that investigation @JonZammit @kaicode. I've raised INFRA-12129 internally to track this.