Language/translations

Home Forums LOINC FHIR Terminology Server Language/translations

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #24156
    Denise Fernandez
    Participant

    Hi! I was just testing your fhir terminology server with some code system queries.

    I was wondering if there’s any way (as there is in https://search.loinc.org) to set the language, so I can get translated values in valueCoding.display for all properties.

    For example:
    * https://search.loinc.org/searchLOINC/search.zul?query=1975-2 (if I “Set Language” to Spanish/Argentina, then I get translated values in the search results)
    * GET https://fhir.loinc.org/CodeSystem/$lookup?system=http://loinc.org&code=1975-2
    (I’m using the same user for basic auth for rest api, and for log in at search.loinc.org)

    I tried:
    – Adding displayLanguage=es-AR as a query param (as per https://www.hl7.org/fhir/operation-codesystem-lookup.html)
    – Adding a header to the request Accept-Language=es-AR (as per https://hl7.org/fhir/2018May/languages.html##http)

    Thanks!

    Denise.

     

    #429482
    Simone Heckmann
    Participant

    Any news about this? Being able to expand ValueSets with display values in other languages is a very important requirement for the usage of LOINC in FHIR implementations in Germany as well.

    We’d love to know if this feature is somewhere on the roadmap!

    #429483
    Tim Briscoe
    Keymaster

    This is something we will be exploring as we realize its importance for the community. We do not have a timetable for a potential release. It would probably be March 2020 at the earliest.

    #435660
    Alejandro Bologna
    Participant

    Hi

    Are there any updates on multi-language support for the fhir-loinc api?

    Thanks!

    #435914
    Marc de Graauw
    Participant

    It’s a feature the Netherlands would really appreciate as well – to the point that using the LOINC FHIR API does not make much sense for us without it. And the API looks great, I’d love to incorporate it.

    #448538
    Marcelo Cabello
    Participant

    Is there any updates? It’s interesting for me also. I tried to define local designations in supplements, but poor outcomes.

    Thanks

    Marc

    #448546
    Tim Briscoe
    Keymaster

    Hello Marc,

    This is still very much on our to-do list. As with many things, COVID destroyed our earlier timeline estimate. We are very much concentrated now on our upcoming LOINC release in December. I can only provide a very rough estimate of May 2021 for this language feature.

    We will be adding the ability to retrieve specific LOINC version CodeSystem and ValueSet resources with our December release. (Initially, we will only make available the previous two releases.) We will be certain to share more information on this new feature at that time.

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.