Current product status
The experiences shown on this site are proposed workflows and illustrative examples. ArioMed is not currently a clinical service, emergency service, diagnostic tool or treatment provider, and it should not be used to make patient-care decisions.
Intended boundaries
- Support administrative data extraction and care coordination.
- Preserve source evidence and uncertainty for human review.
- Do not diagnose, prescribe or independently adjust treatment.
- Do not replace a clinician, carer or established escalation pathway.
- Do not present routine digital messaging as emergency monitoring.
Safety by workflow
Proposed safeguards include role-based review, visible provenance, confirmation before export, clear ownership of follow-up, defined escalation rules, auditability, fallback procedures and a way for users to report errors or unsafe behaviour.
Before a bounded pilot
A pilot would require an agreed intended use, clinical owner, risk assessment, test evidence, approved users, training, monitoring, incident response, change control, privacy and security review, and explicit exit criteria. Regulatory classification would be assessed against the final intended purpose before supply or clinical use.
Urgent care
ArioMed must not be used for emergencies. Anyone who is seriously unwell or believes immediate help is needed should use the emergency pathways provided by their local health service.