ClearScan
Security and data
What protects patient data in ClearScan, briefly and to the point. You can forward this page to your clinic’s IT department or lawyer.
A separate server for every clinic
No database or accounts are shared with other clinics. Every clinic has its own separate server; we choose where to host it (data centre and country) together with the clinic, based on its requirements.
Sign-in and accounts
Passwords are stored only as a strong hash (bcrypt). Two-factor sign-in with an authenticator app (TOTP) is mandatory for administrators and enabled by default for all roles. Sign-in attempts are limited to make password guessing harder.
Roles and permissions
Everyone works only with what their role needs: radiologist, head of department, technologist, manager, clinic administrator. The administrator configures role permissions in the access matrix.
Activity log
Views, downloads and changes to patient data are recorded in the activity log: who did what, and when. For views and downloads, logging is mandatory: if the event cannot be recorded, the data is not released.
Patient links
Patients need no account: they open images and the report via a link. The link contains a random key, and only its hash is stored in the database. The doctor sets the access code and expiry date, and can revoke the link in one click.
ClearScan gateway in the clinic
The gateway receives studies from the modalities over the local network and passes them to the portal on its own over HTTPS (the clinic servers we deploy run on HTTPS only), so no inbound ports need to be opened from the internet. Each gateway has its own access key, which can be revoked from the portal. While there is no connection, studies wait in the gateway’s queue.
Signed updates
Updates arrive signed: the server checks the signature before installing and refuses if it is missing or does not match. The database is backed up before every update, and a failed update is rolled back automatically.
Backups
Backups of the database and settings are encrypted. An off-server copy (S3-compatible storage) can be enabled from the admin panel: the archive is encrypted before upload, so the storage sees only encrypted data.
Contract and pilot
We start the pilot on test data, with no data from your patients. Before moving to real studies, we sign a contract and a data processing agreement (DPA) in line with GDPR.
Security questions
For documentation requests, questions from your IT department or vulnerability reports, write to the address below.