Three surfaces. One continuous thread of care.
Each interface is shaped around its user: simple conversation for the person, traceable coordination for the workflow and operational visibility for the care team.
Speak naturally. See what happens next.
A familiar mobile experience for reporting a change, checking the approved care plan, asking a question and seeing updates from the team—without exposing clinical complexity.
- Today and care-plan steps
- Voice-first questions and check-ins
- Visible status and human follow-up
“I took my morning medication, but I've been more breathless walking around the house.”
Source, structured context and ownership stay visible.
Turn a conversation into a reviewable workflow.
The iPad view makes provenance, structured facts, workflow status and ownership explicit. The agent can progress approved steps, but stops where clinical authority begins.
- Recording, transcript and source context
- Structured facts and care-plan context
- Workflow history and accountable owner
See the queue, the context and the accountable next action.
The desktop workspace extends beyond a single case into review queues, patients, governed workflows, reporting and audit history.
Increased breathlessness during usual activity
What the person can do
- Call and speak naturally without learning a new app.
- Ask questions grounded in approved information and their care plan.
- Report symptoms, medication adherence and changes since the last visit.
- Progress an approved workflow such as requesting medication renewal.
- Reach a caregiver, nurse or clinical team when human help is needed.
What the care team can see
A longitudinal, structured view of conversations, reported symptoms, medication events, questions, workflow status and escalations. Audio, transcript and derived fields are intended to remain traceable so the team can understand what was said and what the agent did.
Assistant versus agent
An assistant answers a question. An agent can also move a service-approved workflow forward—within explicit limits and with a named human owner.
Answers when asked.
- Provides information grounded in the approved care plan.
- Responds to questions in natural language.
- Takes no independent clinical action.
Coordinates within guardrails.
- Notices a change that matches an agreed workflow.
- Collects context and progresses approved administrative steps.
- Executes, stops or escalates within clearly defined limits.
Structured data is an outcome
Patient-reported information and clinical documents can contribute to a reviewed longitudinal record and registry workflow. Registry assistance is a capability of the platform—not the whole product.
Designed to work with the care environment
Integration is a discovery question, not a pre-made assumption. A bounded pilot would identify the safest useful connection for the participating service—from structured import and export to standards or systems already in use.
These are potential integration paths, not claims of current compatibility. Technical, privacy and clinical governance requirements would be agreed with each organisation before a pilot.