One branded place for what your patients actually need: your care team, your clinic details, your explainers and the right contact at the right moment. A link or a QR code. No app, no patient login.
Not another platform. Four things that already exist, each going out of date on its own schedule.
Right the day it was printed. Reprinting is a budget line, so the wrong version stays in the rack.
Written for the organisation, not this service. Several clicks deep, awkward on a phone.
The same questions again at every appointment. Clinic time is the most expensive way to deliver information that never changes.
What they read at eleven at night, from whoever ranks highest, with nobody from your service in the room.
Written by your clinical team, carrying your branding, edited in the admin without a developer.
Patients often do not know whether to ring booking, imaging, the nursing team or a secretary. So they ring the wrong one, or nobody. Making the correct route obvious is the least glamorous thing on this page and usually the first thing a service notices.
Each contact says what it is for, so the choice happens before the call.
No bespoke development and nothing to integrate with. Setup is content work, done by the people who know the content.
Your clinics, clinicians and content. Branding applies per service automatically.
Its own URL, for the appointment letter, the clinic wall or the discharge summary. It opens on any device.
Your team edits directly, and you control who can publish.
The release is deliberately low-data and low-integration, so most of what makes an IG review slow does not apply.
No names, identifiers, records or results. It publishes what your service already gives out, so there is no record set to assess.
A link or a QR code. No account, no password, no credential to lose.
Content and uploaded files sit in a UK region (London), delivered from a content network, as any website is.
Service to patient, and it stops there. No reply channel, no message box, no upload.
PatientMemo runs no surveys and stores no responses. The app links out to your own form, on your own tooling.
No EPR connection and no integration to go live. One organisation cannot see another’s content, and a test suite tries to cross that boundary and must fail.
Read the full FAQ, or send the question your team is stuck on.
Every line describes the current release. Planned is not shipped, and planned is not on this page.
The same platform deploys as a research participant companion, through the same admin.
Run it for one service, with your own team, clinics and explainers in it rather than an example, and see what it changes.
Request demo