THe original Ocean/openEHR Archetype Editor did have the capacity to internationalise some of these RM attributes but this was very much part of the VB programming language, so could not be easily used in other applications. Part of the problem is that a full translation of all RM attributes is an enormous exercise, and generally they will never appear in the UI.
So one question is which attributes are worth translating and if/how we can do this in a vendor-tech-neutral manner?
One option is to take a lead from the Reference Model tab in CKM (for any archetype) this just lists the key ‘clinically relevant’ RM attributes available for a particular archetype class and is powered by a simple definition file - perhaps that could be the start point? I even wonder if we could create one or more dummy archetypes to carry this information, as that would then give use the capacity to handle translation efforts in the same way as we do archetypes themselves.