Stream: shorthand
Topic: multi-language content
Jose Costa Teixeira (May 14 2020 at 06:18):
How would shorthand handle multi-language content? This can be in terminology resources but also in other resources (where we have the translation extension.
Jose Costa Teixeira (May 14 2020 at 06:18):
for those who have to write content in multiple languages, it would be nice if the shorthand language considers a short way of doing it
Jose Costa Teixeira (May 14 2020 at 06:47):
just throwing it out there:
CodeSystem: BeCSCareLocation
Id: be-cs-care-location
Title: "Care Location Codes"
Description: "Care Location Code System"
* #hospital "Hospital" {"fr":"hôpital", "nl":"ziekenhuis", "de":"krankenhaus"}
* #patient-home "Patient home" {"...
Mark Kramer (May 14 2020 at 21:10):
It's on our list!
Chris Moesel (May 14 2020 at 22:09):
Yes, we had initially thought that maybe internationalization would work via additional language-specific files that just contained rules for the translated strings. For example, i18n_la.fsh might contain:
Profile: Hospital
Description: "Lorem ipsum dolor sit amet"
* contact ^short = "Ut enim ad minim veniam"
The file would not contain complete FSH definitions, but only the bits that are strings... and these files could be generated from the FSH definitions with the strings set to the original language so you can pass them off to translators and they just replace the strings... It would provide a nice way to outboard translation without all the translators needing to work in the same file. I'm not sure if that would work so well for terminology (like in your example), but it was only in the early stages of thought anyway (and on the back-burner since then).
Jose Costa Teixeira (May 15 2020 at 06:57):
that is how it is usually done in software indeed, but in our case the people that write the 3 languages are the same that author the codesystem
Mark Kramer (May 15 2020 at 12:36):
@Jose Costa Teixeira what would the final product look like? Is it several IGs, each in a different language, with different markdown files as well as language-specific profiles, or would there be one integrated IG with several languages somehow combined into one?
Jose Costa Teixeira (May 15 2020 at 12:36):
this is just one code system
Jose Costa Teixeira (May 15 2020 at 12:37):
it's not about internationalization, it's just for reference data (in this case)
Jose Costa Teixeira (May 15 2020 at 12:38):
like this
Jose Costa Teixeira (May 15 2020 at 12:38):
https://ehealthplatformstandards.github.io/valueset-be-civilstate.html
Mark Kramer (May 15 2020 at 12:38):
In general the job of multi-language is bigger than that; so our solution should include many aspects of translation. So we don't want to look at it too narrowly.
Jose Costa Teixeira (May 15 2020 at 12:39):
true, and I am not constraining the scope. In fact, the reason I proposed the solution above is because of discussions for IG internationalization
Jose Costa Teixeira (May 15 2020 at 12:39):
as for how the output would look like - in the terminology, as per the link above
Mark Kramer (May 15 2020 at 12:39):
I like the multi-language display. It that from the HL7 IG publisher, or something you have done?
Jose Costa Teixeira (May 15 2020 at 12:40):
that is out of the box from the publisher, I think. @Etienne Cantineau ?
Jose Costa Teixeira (May 15 2020 at 12:42):
actually yes, i can confirm
Jose Costa Teixeira (May 15 2020 at 12:42):
http://build.fhir.org/ig/hl7-be/be-core/CodeSystem-be-civilstate.html
Jose Costa Teixeira (May 15 2020 at 12:42):
here is the same thing in my CI
Jose Costa Teixeira (May 15 2020 at 12:43):
The magic is in the publisher
Jose Costa Teixeira (May 15 2020 at 12:47):
so, the idea is to let people enter translations in a simple manner (in codesystems, but could be the same for other resource content. We have for example street names in different languages, cities, etc...).
I think using language resource files would require a lot of processing before the publisher could take those in.
Chris Moesel (May 15 2020 at 12:56):
Oh, I see. So, at its simplest, this specific request is really just about finding a shorthand syntax for the designation property in CodeSystem concept definitions. I hadn't realized that CodeSystem already had a very specific property for this. That seems fair. I can't remember for sure, but I think I even submitted a ballot comment that we should investigate ways to support other aspects of CodeSystem in the grammar. So this would fit in that.
I think our concern going forward will be how to have a consistent approach to multi-language support. But, we may need to get there in steps, so...
Jose Costa Teixeira (May 15 2020 at 13:00):
the proposal I made comes from here:
Jose Costa Teixeira (May 15 2020 at 13:02):
Michaela Ziegler (Oct 02 2020 at 07:14):
Is it meanwhile possible to integrate the translations (´designation´) in a code system with shorthand? If so, what is the syntax?
Chris Moesel (Oct 02 2020 at 12:41):
Michaela Ziegler said:
Is it meanwhile possible to integrate the translations (´designation´) in a code system with shorthand? If so, what is the syntax?
Thanks for bumping this topic. I'm afraid this didn't make it into the FHIR Shorthand 1.0.0 release, but seems like a good candidate for the next release (STU2). @Mark Kramer -- what do you think?
Jose Costa Teixeira (Oct 02 2020 at 12:43):
Did we have a syntax already?
Chris Moesel (Oct 02 2020 at 12:45):
No.
Mark Kramer (Oct 07 2020 at 13:56):
We've had multi-language support in our feature queue for a long time. We are dependent on having a stable approach in native FHIR, so FSH would have a clear target representation. As far as I know, that doesn't yet exist.
Grahame Grieve (Oct 12 2020 at 05:42):
no. it's on my todo list. You're right that you wouldn't want to take that on until we have clarity about how it's going to work
Last updated: Apr 12 2022 at 19:14 UTC
