Isolation
Each facility's data is isolated at the database level: every query runs under row-level security bound to that facility, so one facility cannot read or write another's records.
Access
- Sign-in goes through a central identity provider. Workspace owners and platform administrators must use multi-factor authentication, and a facility can require it of all its users.
- Roles and permissions decide what each user can see and change. Platform staff can enter a workspace only with the facility's consent, and every such session is recorded.
Protection of data
- All traffic to ITQAN is encrypted in transit (HTTPS).
- Secrets the platform stores, such as integration credentials, are encrypted.
- Uploaded files are checked against their declared type before they are stored.
- The web applications send a strict Content-Security-Policy.
Accountability
Changes to records are written to an audit trail, and security events (refused sign-ins, refused actions) are logged.
Reporting a vulnerability
Please report a suspected vulnerability to asmaa.atef@itqan.health. Do not test against other facilities' data.