You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be helpful if there was a way of seeing in the 'summary-tab' if any of the descriptions were preferred in a specific language refset.
One use-case would be for those who develop patient-friendly terms, another when a region or care-provider wants to visualise their preferred terms, which might not be the same as on the national level.
To get that information today you have to toggle to the 'details-tab' for each and every concept.
Would it be possible for example to add an icon next to the language-code? This would then only be visible for those searching a server with that specific language refset installed, but if needed (for instance if there are many language refsets on the server) maybe there could be an option to turn them on/off under the cogwheel? The cogwheel-selection only affects the 'details-tab' today.
Has anyone else been thinking or working in this direction?
The text was updated successfully, but these errors were encountered:
It would be helpful if there was a way of seeing in the 'summary-tab' if any of the descriptions were preferred in a specific language refset.
One use-case would be for those who develop patient-friendly terms, another when a region or care-provider wants to visualise their preferred terms, which might not be the same as on the national level.
To get that information today you have to toggle to the 'details-tab' for each and every concept.
Would it be possible for example to add an icon next to the language-code? This would then only be visible for those searching a server with that specific language refset installed, but if needed (for instance if there are many language refsets on the server) maybe there could be an option to turn them on/off under the cogwheel? The cogwheel-selection only affects the 'details-tab' today.
Has anyone else been thinking or working in this direction?
The text was updated successfully, but these errors were encountered: