Read on, or see single tweet summary here👇0/44
On 6th Jan 2017 a tweet about an #eHealth #AI #Chatbot in #NHS trials caught his attention, so he thought he'd take a look. 1/44
Evidence here 👇
As evidenced by👇 2/44
Watch video evidence here 👇3/44
Evidenced here 👇4/44
@babylonhealth also provided a link to an unpublished report outlining how the #Chatbot had been tested > arxiv.org/abs/1606.02041…
DM from Babylon 👇 5/44
Initial submission to CQC & follow-up email 👇6/44
The #CQC indicated that they would involve the #MHRA, & may also play a role in reviewing the App if it was being used to access the Babylon GP services. 7/44
Evidenced here 👇 8/44
This was discussed in a BMJ article > bmj.com/content/358/bm… & on @BBCRadio4.
Listen here (1st 12mins) 👇9/44
bbc.co.uk/programmes/b08…
Consequently he re-contacted the CQC & also made @ptsafetyNHS aware of the #PatientSafety concerns.
Email correspondence👇10/44
Including, time critical Reg Flag presentations such as 'referred cardiac pain'! 😲
NHS111 App triage 👇11/44
Babylonhealth response to BMJ👇12/44
bmj.com/content/358/bm…
Evidenced here 👇14/44
Learn about Class I & II #MedicalDevice regs here👇15/44
Evidenced here 👇 16/44
Evidenced here 👇 17/44
Evidence of confusion 👇18/44
Dr Murphy had to put it to the test...
See questions regarding the #AskBabylon #Chatbot here 👇 22/44
This was a 'suspected cancer' presentation with weight loss and fatigue, that the #AskBabylon #Chatbot diagnosed as depression!
Another #AI diagnostic fail...
Evidenced here 👇 26/44
This was a barn door #PE #DVT presentation that you would expect a medical student to get right...
Sadly the #AskBabylon #AI #Chatbot failed, again 😕
Evidenced here 👇 27/44
By this point it was clear the #AskBabylon #Chatbot wasn't very good, so I tried it with a really easy #NoseBleed.
The result, was amusing...
The now infamous #Nosebleed triage👇 28/44
In reality; this was a flawed, unvalidated, non-CE Marked #MedicalDevice!
Evidenced here 👇 29/44
@ASA_UK were informed of the misleading claim & raised it with @babylonhealth. By May 18, the claim was removed from the Babylon website.
Evidenced here👇31/44
For example, they didn't like a recent @CareQualityComm report & tried to block its publication.
However, their website comments that they 'passed with flying colours'
Evidenced here👇32/44
It's therefore worth considering; how did they meet the #PatientSafety requirements of @NHSDigital?
Possibly because of this?👇33/44
IMO;
- The regulations allowed them to
- They thought no one would check
- Corporate culture & conflicts
#ClinicalGovernance👇34/44
> Nope.
Currently class I devices (most #eHealth Apps) are not assessed or approved by @MHRAdevices.
Companies self certify; without external scrutiny
The Regs don't work👇35/44
You may have noticed, Dr Murphy has become a (reluctant) #eHealth Regs nerd 🤓
New Regs👇36/44
pharmatimes.com/magazine/2018/…
Given my experience with the Babylon #AI #Chatbots, I questioned that description.
The FT 👇37/44
There was still no outcome 😕
April 18 CQC email response👇 38/44
Yet again, the response from @babylonhealth was dismissive...
See 7 tweet thread👇39/44
1. @DrMurphy11 was a bogus doctor with probity issues 🙄
2. The allegations of compliants/concerns were false.
3. The #Chatbot had undergone rigorous testing.
🤨👇41/44
IMO; the Babylon #AI #Chatbot provides a good example of how NOT to do #HealthTech.
- Fundamental flaws
- Misplaced confidence in system
- No validation
- Confusing T&Cs
- Misleading marketing
- Dismissive of criticism
👇43/44
& PLEASE, drop the hype...
Usual T&Cs apply 👇 44/44