Testing New Translation Tool (SNOMED International)

@ovage @mvandenberg @klindve @mlegall @sklopfenstein @chaas @fgeier @plammertyn @mharkonen @lbilliet @AnnDo @abyun @lbie @jboutin

You all now have test account access to the new Translation Tool, as shown in the business meetings two weeks ago :rocket:

I have created temporary SNOMED extensions for you to play in. Please access the user test environment here: https://uat-simplex.ihtsdotools.org/
If you do not know the password for your test account use the “Forgot Password?” button.

A reminder that the current automatic translation feature is designed for new translations but it should still give you a chance to get the feel of what it can do.

Yesterday I recorded a reminder demonstration video here: https://youtu.be/AQAX3e-Izuc
There is also a document with steps here. The document also has a translation advice template in the appendix.

Feel free to post your feedback or questions in this thread, or email if you prefer kke@snomed.org. We will also set up a call to talk through your feedback in the next few of weeks.

Thank you for volunteering to collaborate in this translation tooling development. We couldn’t do it without you!

The Implementation Support Team

4 Likes

Hi Kai,

Thank you for the test accounts. I really like the AI translation feature. It will save us a considerable amount of time on our translation and quality control tasks.

The translation interface is interesting, but I did notice a few usability issues during testing.

I logged my feedback and questions here:

Translation_tool_feedback_FR.pdf (304.4 KB)

@mlegall wonderful! Thank you for the detailed feedback.
I will go through each item carefully and consider next steps.

I would like to test the new translation tool.

No problem. I will get a test account set up for you. It will take a few days to get the permissions sorted.

1 Like

Great feedback Maël. Thank you for the effort!

Hello,

I don’t know if it was scheduled or something like that, but, with @AnnDo we were not able, today, to access previously created sets. They were available to test and to work on during previous days, but not today.
Is this something that was planned ? Can we do something about it ?

Below, some screenshots to illustrate were we encountered errors.

From the error messages, it seems that the previously created sets were not erased, but maybe just permission to access it that maybe “broken” or kind of ?
I assume that, since one error message tells us, when we try to create a new set, with the same label as a previously created, that there is a conflict with an existing set that already has this name .

Trying to create new set => failed

Translation dashboard reporting => history lacking ?

But, we must say, regarding our previous tests, the tool seems to be very helpful to accelerate translation works : thank you for this initiative !

Thank you for the functional feedback, that’s good news!

Thank you also for letting me know the test Translation Tool had stopped responding. It is available again now, we will diagnose the issue to try to prevent further outages. Your translation sets are now accessible again.