Testing New Translation Tool (SNOMED International)

SNOMED Groups Translation User Group
1

Please reply to this post if you would like access to the new Translation Tool testing environment.

Thank you so much for all your valuable feedback so far. This tooling development is a collaboration.

2 Likes
2

Thank you for letting us test the new tool. In Norway, we are very interested.

1 Like
3

Hi Kai, the Dutch NRC would be very much interested in testing the new translation tool.

1 Like
4

Hi, I would like to test the Translation Tool. I think I have worked with all translation tools on the market the last 14 years so looking forward to this!

2 Likes
5

Hi, I would also be interested in testing the translation tool.

1 Like
6

Hi, thanks for the presentation during the TUG. I would love to test it too :slight_smile:

1 Like
7

Thanks @kkewley. Belgium is interested.

1 Like
8

Hi Kai,
With @AnnDo, we are interested in testing this tool. Thank you

1 Like
9

Thanks everyone, I’ll get those test accounts set up.

6 Likes
10

Hi Kai,

Interested in testing the tool aswell, thanks

2 Likes
11

Hi Kai, The Danish NRC would also like to test the new translation tool. Thx in advance.

2 Likes
12

Hello @kkewley ,

Canada would also like to test the Translation tool.

Thanks,

2 Likes
13

Regarding FSN changes, where we have an extensive backlog, is it possible to upload the FSN-changes into a translation project?

14

@klindve I think the Managed Service already supports bulk import of new or changed FSNs via spreadsheet. I suggest you ask the Managed Service support team about this.

FSN support is on the roadmap for the Translation Tool but this has not been added yet.

1 Like
15

Update - I have created test extensions for everyone, I’m just chasing up the account/permissions setup.

16

Hi, actually it is not the FSN’s themselves but the preferred term associated with a FSN change which has a translation. We need to check and update these, especially if the AI tool should work properly. These SCTID would look mas if they were already translated but in fact, as the FSN has changed, the rug has so to say been pulled from under the feet of the preferred term and the domino effect is that the translation is not always correct anymore. The report we get only states the English preferred term, not our translation so we can check. Instead we need to do manual checks and updates when needed. This is a time-consuming process. I had some hopes that this tool could be used for this task.

17

Hi Katarina, An alternative way to check for those changes is through the Extension Impact Report, on the Reporting Platform. That will even warn you about impending changes, so you can fix them as soon as the changes are published.

This report has a tab called Translation detail, which contains the translated Preferred Term as well as the original and the new English FSN.

2 Likes
18

I did not check for a separate tab! Thanks

19

Hi @klindve, we’re currently tackling the same problem in Belgium. What I did was to put together a file with all active concepts whose FSN’s ‘effectiveTime’ value is higher (=more recent) than the ‘effectiveTime’ of the translated PT. The information is in the RF2 files of your release, namely in the files concept snapshot, language snapshot and description snapshot.
I used Python for this.

I did this twice, once for French and once for Dutch.

image
image1533×216 13.8 KB

3 Likes
20

Thank you!

That sounds like a really easy way to list (and check) all FSN-changes!

Are you enrolled in Managed Services as well? This should really be a standard report, easily accessible through the Reporting platform.