Care continues in the life around the visit.
A planned Android companion that helps patients understand the plan and lets authorised caregivers support it.
Explore the story
Medrella roadmap. This experience is being planned; scope and readiness will be demonstrated before implementation.
What this workflow connects.
The scope below guides discovery and demonstration. This capability is on the Medrella roadmap.
- 01
Patient-facing appointments and approved records
- 02
Planned Android access and care-team follow-up
- 03
Authorised caregiver tasks and revocation
- 04
Education matched to the approved care plan
- 05
Human support for people who need assistance
The patient is part of the care team
A consultation creates a plan, but much of the work happens later at home. Patients need to remember instructions, arrange the next visit and understand which information to share back.
A digital experience should make those steps clearer without assuming that everyone is comfortable using an app. Medrella's planned Android companion connects appointments, shared records, education and check-ins around the clinician-approved plan. For older adults and others who need help, authorised caregivers should be able to participate. The objective is a more continuous relationship, with practical support rather than a stream of generic notifications.
Organise the experience around today's next step
A patient should not need to understand hospital software categories to find out what to do next. The home view should prioritise the current plan, upcoming appointments and relevant messages.
Records should be understandable in context, with clear dates and sources. A reminder needs a useful action and a route to ask for help. Where a task is optional or a booking is not yet confirmed, the wording should make that distinction visible. The experience should work for people who return infrequently as well as those managing an ongoing care relationship.
Include caregivers through explicit permission
Caregiver participation is not the same as sharing a password.
The patient may want someone to help arrange appointments without giving unrestricted access to clinical history. The planned model should support clear delegated permissions, identity verification and revocation. Changes in the care relationship need to be reflected in access. Staff should know who is communicating and on whose behalf. These requirements must be designed with real patient and caregiver scenarios, including people who need assisted onboarding. The platform should support participation without assuming that family membership automatically establishes consent or authority.
Make education specific and reviewable
Useful patient education connects to the approved care plan and the person's ability to understand and act on it. Language, reading level and preferred format matter.
Planned AI can help prepare explanations and coaching content, but it should not independently change treatment or present unreviewed advice as the doctor's instruction. Patients need to know the limits of the service and how to reach the appropriate team. Check-ins should have a defined recipient and response expectation. Collecting information without a plan for review creates work and uncertainty rather than a dependable care relationship.
Evaluate comprehension and participation
A patient-experience pilot should include people with different levels of digital confidence and caregivers supporting older adults. Ask participants to find the next appointment, understand a shared plan and change a permission.
Test notification preferences, accessible text sizes and the route back to human support. Measure whether people understand the next step, not only whether they opened a message. The Android application and caregiver delegation remain planned capabilities. Website images and interface concepts illustrate the direction; they are not evidence of a released patient app or an already operational monitoring service.
Connected thinking.
What would more time
for care make possible?
Let's explore it together