What AI actually returns in mental healthcare today
The question is no longer whether AI can do something for mental healthcare, but where the return shows up fastest. In our projects it is almost always the same place: the administrative shell around the treatment. Registration, intake, handover, correspondence and the assignment of e-health modules. Work that is necessary, but that requires no clinical judgement.
In the projects we run, client registrations were typically handled entirely by hand: staff phoned clients for missing information, retyped forms into the EHR and maintained waiting lists manually. After implementing AI-powered registration forms this process runs almost entirely automatically, and internal support tends to grow on its own: on average around fifteen percent of staff are already actively involved in shaping AI use right from the start, a group that quickly grows into a broader movement across the organisation.
Figures from live deployments
- ~15% of staff already actively involved in AI brainstorming from the start
- From 30 clicks to 1-3 clicks to register an email
- An expected 90% of incoming email registered into the EHR automatically
- A top five or top ten of matching e-health modules surfaced while the care plan is written
- Human review retained at every clinically meaningful step
Four applications that work in practice
1. Intelligent support during registration. Registration forms go out automatically with smart reminders, including a speech-to-text option for clients who struggle to write. Completed data flows into the EHR automatically and waiting lists update in real time across all divisions.
2. Automatic email registration. Registering a sent email often costs a clinician around 30 clicks, or roughly 5 minutes, with the risk of a missed registration. After implementation a pop-up appears automatically with the relevant fields pre-filled: registration is complete in 1 to 3 clicks, with an expected 90% running automatically. The staff member sees what is about to be recorded and confirms it; nothing is stored without that step.
3. The right e-health module from inside the EHR. E-health platforms offer hundreds of specialised modules and no clinician knows them all. An assistant combines client context from the EHR with the characteristics of the catalogue and surfaces a personalised top five or top ten at the moment the care plan is being written.
4. A digital assistant on top of any browser-based EHR. Through a browser extension, the assistant validates input, flags missing or inconsistent fields and automates repetitive actions. It works without your EHR vendor having to build anything.
What does not work
We see the same patterns fail repeatedly, and it is more useful to name them than to stay quiet about them.
- The standalone chatbot. An AI assistant that sits beside the EHR and requires clinicians to retype information into it returns no net time.
- The pilot without an owner. A proof of concept with no named process owner and no budget for maintenance almost always ends its life as a demo.
- AI on unstructured data with no cleanup. When the source data is messy, AI mostly accelerates the production of messy output.
- Full automation of clinical decisions. That is legally untenable and professionally undesirable. Automate the preparation, not the judgement.
GDPR, privacy and human review
Every mental healthcare organisation gets the same questions from its data protection officer, and rightly so. We therefore build on Microsoft technology in GDPR-compliant configurations, with data minimisation as the starting point: the assistant receives only the context the task requires.
The design principle matters just as much. At every step with clinical or legal weight, the AI prepares and a human decides. For automatic email registration that means a staff member sees what is about to be recorded before anything reaches the record. It costs a few seconds and removes the single biggest objection.
What an engagement looks like
An AI strategy engagement typically runs ten weeks and produces a roadmap that estimates, per opportunity, the expected return, the effort required and the risks involved. After that we build, usually starting with the application that has the shortest path to visible results.
We work to a proprietary framework inspired by MIT research, and we build with reusable components. That means the second mental healthcare organisation does not pay for the first one's learning curve.