Security boundaries before security claims.

The public demo is anonymous and separate from protected administrator access. The showcase should not receive real patient data, file uploads, live EHR connections, production OAuth credentials, or production clinical workflows.

Administrator access uses an authenticated, server-authorized flow. Organization verification, formal role matrices, periodic access certification, and workforce procedures remain pending operational validation.

Encryption standards, key management, backup recovery, production logging, vulnerability management, penetration testing, and secure-development controls are pending documented verification. No certification is claimed.

Research is designed around aggregate feasibility, organization isolation, explicit approval, pseudonymous outputs, purpose-bound access, expiry, revocation, and audit history. Pseudonymous data is not anonymous data.

Monitoring views and an incident history surface are present in the protected workspace. Severity definitions, notification duties, response ownership, evidence preservation, and post-incident review remain pending legal and operational approval.

Use the incident-reporting instructions. Do not send patient data, passwords, access tokens, or exploit details that could increase harm in an initial email.