Episode ownership
Create a care-at-home episode with patient reference, named owner, pathway context and planned review date.
New care-coordination range
Local product demonstratorMeridian Home
Coordinate home-care episodes, patient check-ins and consented observations with a clear staff-review workflow.
Care at home, with an accountable team.
Home brings a care-at-home episode into a shared operational view: who owns it, when it should be reviewed, what instructions have been agreed and which updates need staff attention. The patient-app page provides a way to view the local plan and submit a check-in, while the care team keeps responsibility for interpretation and action.
What the AI does. What people decide.
The actual assistance
The current observation review uses locally configured boundaries and explicit status rules to create advisory flags. A model does not diagnose a patient, decide that missing data is normal or automatically escalate a person. Guardian review supports visibility; authorised staff assess context, acknowledge or resolve an item and choose any escalation route.
Human ownership
Synthetic care-at-home demonstrator. Check-ins are not continuously monitored and are not an emergency contact route. Wearable observations must not be assumed to be clinical measurements.
Features in the current workspace.
Agreed plan and hours
Record patient instructions and the agreed service-hours context so the contact route is explicit.
Consent-aware observations
Read profile observations only when consent for the provider and data category is active.
Locally defined boundaries
Allow authorised teams to configure observation limits and inspect resulting advisory flags.
Review queue
Bring observation flags and patient updates into a staff-owned Guardian review queue.
Explicit staff actions
Acknowledge, resolve or choose an escalation-route action; the system does not silently escalate a patient.
Patient-app check-ins
Let a local patient view the plan and record a check-in, including a request for contact or difficulty completing it.
Missing-data visibility
Keep absent or stale observations visible instead of treating the lack of a reading as reassurance.
Episode lifecycle
Track active, completed and staff-escalated records and maintain review context.
Transitions connection
Episode review dates and outstanding check-ins can contribute coordination tasks to the shared queue.
From first input to a reviewed next step.
- 01
Agree the episode
Set ownership, plan, service hours and review date.
- 02
Confirm source consent
Check the permitted provider and observation category.
- 03
Receive updates
Read available observations and patient-entered check-ins.
- 04
Review advisory flags
Staff interpret context and choose the next action.
- 05
Record follow-up
Maintain review state and coordinate outstanding work.
How the product works.
| Area | Mechanism and scope |
|---|---|
| Consent gate | The source checks patient-profile consent before using provider/category observations. |
| Advisory comparisons | Configured limits and local workflow state generate review flags; these are not validated diagnostic thresholds. |
| Local persistence | Episode, check-in and review actions are retained in the configured demonstrator store. |
| External boundary | No wearable-cloud connector or continuous on-call monitoring service is established by this local build. |
Product evidence and source notes
Content checked against the v25.2.0 source and visible local workspace on 30 October 2026. This is a product description and interface inspection, not an end-to-end deployment or clinical validation.
routes/home_care.py; static/home-care.js; RELEASE_NOTES_v24.7.0.md
Review assurance scopeQuestions about Home.
Does Home monitor a patient around the clock?
No continuous monitored service is provided by the local demonstrator. Service hours and response arrangements must be agreed separately.
What happens if an observation is missing?
The absence needs investigation in context. A missing or stale reading is not treated as a normal result.