HAZARD: Remaining non-English language text interface elements will confuse users

[pacharanero]

Description

Albert Health is a Turkish company with a voice assistant platform built into a mobile and desktop app. The original Albert implementation used Turkish, and the UK version of Albert has been extensively localized to the UK and appropriate idiomatic British English. However, in pre-release, pre-pilot testing, there remain a few areas in which small amounts of Turkish UI elements can be seen.

Cause

If Turkish language elements remain in the UK version of Albert Health this creates an understanding barrier between the app and its users. There is naturally no expectation that UK users will understand any Turkish.

Effect

The end user could see Turkish elements and is unlikely to know what they mean. They may not know if this is a trivial piece of information or a very important piece of information.

Hazards

• The app could be imparting a very important piece of information, which is not realised by the user.
• The app could be imparting a very trivial piece of information, which the user could worry is important.

Harm

Clinically, the most significant harm that could occur is if an instruction relating to the enteral feeding or medication programme was not relayed accurately. This is a significant harm and must be mitigated.

---

Assignment: Assign this Hazard to its Owner. Default owner is the Clinical Safety Officer @pacharanero Labelling: Add labels according to Severity. Likelihood and Risk Level Project: Add to the Project 'Clinical Risk Management'

• Subsequent discussion can be used to mitigate the Hazard, reducing the likelihood (or less commonly reducing the severity) of the Harm.
• If Harm is reduced then you can change the labels to reflect this and reclassify the Risk Score.
• Issues can be linked to: Issues describing specific software changes, Pull Requests or Commits fixing Issues, external links, and much more supporting documentation. Aim for a comprehensive, well-evidenced, public and open discussion on risk and safety.

[github-actions[bot]]

Thank you for opening or editing a Hazard in the Hazard Log.

Next steps:

• Please use the Labels feature in the right sidebar area to stratify this Hazard in terms of Likelihood and Severity
• Assign the Issue to the Clinical Safety Officer for triage

[pacharanero]

This hazard has been triaged by the CSO @pacharanero

• I have assigned Likelihood: High as I have seen numerous instances of Turkish text in the application

• I have assigned Severity: Significant because in clinical reality the patient would almost certainly seek an alternative form of advice rapidly. It is difficult to imagine someone being unable to enterally feed themselves due to an issue with understanding the text in the Albert app, and NOT seeking advice from anyone, over such a timescale so as to harm their health permanently.

• Using the Risk Matrix below, this equates to a Risk Score 3: Undesirable, and requires mitigation.

[pacharanero]

Mitigation

Since this is a relatively simple problem to eradicate, the aim must be that NO Turkish text is at any time visible to a user in the UK. In discussion with @ensargunesdogdu (CTO) @Yigitcinar (PM) this is a technically feasible aim.

When fragments of remnant Turkish text show up in the UI I will create GitHub issues for them in this repo, and reference this Hazard. This will enable us to track the completion of the remaining localization work, and then the Hazard can be re-graded.