Documentation
Security and data
We describe the mechanisms as they exist in the application today, including where they stop. Hosting configuration, providers and operating responsibilities are set for each pilot.
Data separation and access
- Each institution's data lives in a separate database.
- Access is granted by roles and permissions (patients, admissions, investigations, on-call, pharmacy, CAS reporting and others).
- Staff with limited ward access see only their own ward and any additional permitted wards.
- The ED waiting-area display shows data anonymised (code, initials, age).
Access log and signed documents
- The patient-data access log is written on viewing and editing the Patient 360 record and on export of lab and imaging reports; it does not yet cover every clinical screen.
- The qualified electronic signature is applied outside the application with the physician's token; the signed document is uploaded and checked in the application. Cloud signing is not active.
- The patient portal has separate authentication, and each patient sees only their own documents.
AI assistance and data
- The clinical assistant proposes and does not execute: the physician confirms every appointment, request or prescription.
- The text of a command to the assistant is processed by an external language-model provider, without the patient identifier.
- Voice dictation is transcribed by a service hosted in our own infrastructure; the recording is not sent to third parties.
- In imaging, the study is sent to the AI provider configured for the institution, and the result remains a draft until the radiologist validates it.