FHIR Chat · Tooling for CodeSystem translations · terminology

Stream: terminology

Topic: Tooling for CodeSystem translations

view this post on Zulip Simone Heckmann (Jul 08 2019 at 13:40):

Does anyone know of tools that support the maintenance of CodeSystem supplements (i.e. import the original CodeSystem resource, add translations via a user friendly UI, save translations in a CodeSystem supplement)
Ideally the tool should also create language specific ValueSet expansions...
@Alexander Henket : Does Art-Decor support any of that?

view this post on Zulip Rob Hausam (Jul 08 2019 at 15:13):

I don't know of anything that can do all of that - but it sounds like it would be very useful.

view this post on Zulip Michael Lawley (Jul 08 2019 at 23:01):

Ontoserver R4 release due in a couple of months will have support for translations in CodeSystem supplements, so it will satisfy your ValueSet expansion requirement.

view this post on Zulip Adam Flinton (Jul 09 2019 at 08:40):

you could look at the snowstorm elastic search thing from snomed.... could be the basis for a solution.... & it's oss etc e.g.
https://github.com/IHTSDO/snowstorm/commit/d19a15dc7bd31f3e53d501c24ea5e6e532a904dc

  • FHIR:

    • Support for multiple languages
      • Accept-Language request header respected.
      • Valueset expand operation 'displayLanguage' and 'designations' parameters supported.
    • Add support for expand operation 'filter' parameter.
    • Add support for offset, count and total in ValueSet expand operation.
    • Add support for CodeSystem lookup properties.
    • Add support for all implicitly defined FHIR valuesets.
    • Add support for maps (ICD-10, CTV-3) including historical associations

  • FHIR:

    • Upgrade FHIR API from DSTU3 to R4.
    • Allow valueset expansion against other imported editions.
    • Allow FHIR requests to access MAIN (or equivalent) as well as versioned branches.
    • Automatically populate server capabilities version from maven pom.
    • Update documentation: paging and filtering, valueset defined via refset.

view this post on Zulip Alexander Henket (Jul 09 2019 at 11:20):

No sorry. I let it rest when a couple of months ago I was the seemingly only/first person to try them out and the publishing tooling wasn't ready to deal with them. After that I've been swamped/too busy with other stuff. We could revive that idea at some point though

view this post on Zulip Simone Heckmann (Jul 09 2019 at 12:47):

you could look at the snowstorm elastic search thing from snomed.... could be the basis for a solution.... & it's oss etc e.g.
https://github.com/IHTSDO/snowstorm/commit/d19a15dc7bd31f3e53d501c24ea5e6e532a904dc

Thanks, if only we were one of those countries with a SNOMED license :cry:

view this post on Zulip Adam Flinton (Jul 15 2019 at 08:35):

The code itself is OSS & you can re-use the holy trinity of snomed to model other code systems..... I did read v2 & 3 & ICD-10 in the snomed structure i.e. the concept, relationship, description model is applicable to more than just snomed itself.

Last updated: Apr 12 2022 at 19:14 UTC


An HL7 Website -