The team sees the shape of the weeks. Never the words.
MendAI Platform is the clinical side of MendAI. It holds client records, aggregates the signals a client has agreed to share from their Aftercare diary, and gives the team that treated them a portal where the weeks between appointments are already assembled when the appointment starts.
A follow-up starts by reconstructing six weeks from memory.
In the room, under time pressure, with the clinician who knows the client best holding the least recent information about them. The gap is widest exactly where the hazard is.
The information already exists — the client is generating it daily. Nothing needs to be collected that is not already being written. The work is routing the consented part of it to the right clinician at the right time, and routing nothing else anywhere.
Relapse within three months of inpatient discharge
Median time to relapse; the hazard is steepest in month one
Relapse rate for clients with a co-occurring disorder
Effect of continuing care on outcomes at follow-up
Sources: 01 Andersson et al., 2018 · 02 Post-discharge survival analysis · 03 Andersson et al., co-occurring cohort · 04 Blodgett et al., 2014 meta-analysis
Four classes of signal. Everything else stays with the client.
The client agrees to this window one category at a time, when aftercare begins, and closes it at any point without losing their diary. They see exactly the view their clinician sees, including the rule behind any alert — a view its subject cannot inspect is not a consented view.
Anything computed from something on the right-hand list stays on the right-hand list. Abstraction is not anonymisation and paraphrase is not consent.
Engagement
How often the diary is written in, and whether that changed.
Self-reported trends
Mood, craving, stress and sleep, as the client reports them.
Goal progress
The goals the client committed to, and how they say those are going.
Assessments
Validated measures completed at agreed intervals.
Entry text
Clinicians do not read the diary.
Conversations
What the companion asked and the client answered is not surfaced.
Location or device data
MendAI does not track where a client is.
A programme may not make linkage a condition of admission, discharge, or continued participation. That is a term in the deployment agreement rather than a guideline, because consent obtained as a condition of care is not freely given — and because the Aftercare diary is complete unlinked, with nothing withheld to make linking attractive.
A record that assembles itself.
Each capability is described with the constraint that holds it, because on this product the limit is the capability.
Client records
Holds your programme's own record of a client — admission, discharge date, assigned clinician, consent state, linkage status. Programme-authored data only: diary content is not a record field and does not become one by being stored nearby.
Signal aggregation
Computes trends across the four consented signal classes and no others — engagement, self-reported mood, craving, stress and sleep, goal progress, and completed assessments.
Clinician portal
A per-client view and a caseload view for the team that treated the client. Access follows the treating relationship and the client's current consent state, and revocation takes effect in the portal itself — not in a support queue.
Health and data feeds
Outbound integration to your own systems — EHR, case management, reporting warehouse — and inbound from assessment instruments. A feed carries the same four classes and nothing beyond them.
Summaries
A narrative précis of a period, written for the treating clinician and computed only from the four consented classes. A summary derived from entry text would be a disclosure of entry text however abstracted, so none is produced.
Reports
Programme-level and cohort-level reporting, and per-client period reports. Cohort reporting is aggregate, with a small-n floor enforced in the query rather than left to a reviewer's judgement.
Alerts
An alert reports that a consented signal changed, or that something expected did not happen. It does not say what the change means — interpretation stays with the clinician.
Dashboards
Caseload overview, engagement state, assessments due. Ordered by clinical workflow — appointment due, assessment overdue, consent expiring — and never by inferred risk.
An alert says a signal changed. It does not say what that means.
Interpretation belongs to the clinician and the product does not pre-empt it. That is why the second list below is closed rather than a roadmap — a caseload sorted by danger is a risk engine with a different label on it.
- A consented signal crossing a threshold the client and clinician agreed in advance
- A non-event — the diary has gone quiet, an assessment is overdue, a goal has stalled
- A scheduled checkpoint arriving
- The client asking for contact
- Predicted relapse, relapse likelihood, or any forward-looking risk statement
- Risk scores, risk tiers, or ranking a caseload by danger
- Any alert derived from entry text or companion conversation
- Alerts the client cannot see the rule for
Not a monitoring system — the consent boundary is why. Not a risk engine: it does not predict relapse, score risk, or rank a caseload. Not an EHR; it sits beside your record of care and does not become it. And not a condition of treatment.
Three modes, one boundary.
Exporting to a system with weaker access control does not relax the boundary — it moves the liability and keeps the claim. The four classes travel the same way in every mode.
Managed
MendAI-operated, EU region, multi-tenant with per-programme isolation.
Dedicated
A single-tenant instance in a named EU region.
Customer-controlled
Deployed into infrastructure your programme controls, where procurement or national rules require it.
Client data stays in-region, and the region is named in the agreement rather than inferred. In a programme deployment your programme is controller and MendAI is processor for the linked record; the unlinked diary is a separate relationship with the client. Two lawful bases, one system, written down separately.
A DPA, a sub-processor register, a DPIA support pack and records of processing come with the deployment. This is Article 9 data, so explicit consent is the operative basis for the linked view — which is why linkage cannot be made a condition of care.
A small number of pilots are opening.
A pilot runs a cohort of discharged clients over roughly three months, with full clinician access and transparent reporting on what both sides see. Finding out where this does not work with five programmes is worth more than assuming it works with fifty.
Commercial terms follow from what your aftercare actually looks like — wholesale, revenue share, or bundled — so it is a conversation rather than a rate card.
If you are a client or a family member rather than a provider, the diary itself is on the MendAI Aftercare page.
Get in touch