Privacy posture for staging evaluation.
This page describes the staging/development privacy posture only. It is not the final production privacy notice, data processing agreement, or NHS deployment assurance pack.
Staging and development status
Oryen Health must not be used for live patient care, production NHS workflows, or real clinical decision-making until the required production approvals are complete.
Before production use, controller/processor roles, lawful basis, Article 9 condition, subprocessors, retention rules, data residency, and signed customer agreements must be formally approved.
Data handled by the platform
Oryen Health is designed to handle organization records, user accounts, patients, devices, assignments, readings, alerts, reminders, reports, operational event records, API clients, and webhook activity.
Patient-identifiable information must be stored only in approved database and object-storage services with tenant-aware access controls.
Use of data
Product data is used to operate remote monitoring, device rental, alerting, reporting, and integration workflows for authorized healthcare organizations.
AI-assisted summaries, when enabled, must remain assistive and must not be used as autonomous diagnosis or treatment logic.
Before production launch
Production deployment requires a completed DPIA, RoPA, lawful basis, Article 9 condition, controller/processor mapping, data processing agreements, subprocessor register, retention schedule, data subject rights process, incident response procedures, backup evidence, and clinical safety sign-off where applicable.