Status and security facts
This page states plainly what AEVRUS is and is not today. Where another page on this site says more than this page, rely on this page.
AEVRUS is in development. It has been demonstrated only on synthetic test data: generated patient records, and the test patients that health-record vendors provide for development. It does not accept real patient records. Please do not upload, send or connect real medical records.
Compliance
AEVRUS has no SOC 2 report, and no SOC 2 audit is under way. AEVRUS does not offer Business Associate Agreements. AEVRUS has not been assessed for HIPAA compliance by any third party and does not claim to be HIPAA compliant.
Who can read stored data
AEVRUS holds keys that can decrypt the data it stores. Through the AEVRUS portal, a clinician reads a patient’s record only with the patient’s grant, and the patient can withdraw that grant.
Encryption
Documents uploaded to the AEVRUS vault are encrypted with AES-256-GCM, each under its own key. Other records, including those retrieved from health-record test environments, are stored in the AEVRUS database without per-record encryption. Connections to the site use TLS. Post-quantum encryption is not implemented. Sign-in to the AEVRUS portal is by email and password.
Access logs
Clinician reads made through the AEVRUS portal are recorded in an access log the patient can view. Each entry is written before the data is shown. Reads that the AEVRUS AI assistant makes under a patient’s grant are entered the same way and marked as AI. A refused request is not entered in this log, and a patient’s own reads are not entered in it. The access log has no cryptographic protection: an administrator with direct database access could alter it, and access made directly to the database does not appear in it.
Downloads of documents uploaded to the vault, including the patient’s own, and refused attempts to download them are recorded in a separate vault log. Database triggers make that log append-only. That is not cryptographic protection, and an administrator could remove the triggers.
Neither log is offered as evidence for court.
Connections to health-record systems
AEVRUS has read-only test registrations with several health-record vendors. It writes nothing back to any health-record system.
Not offered today
No pilot program is open. Nothing on this site is an offer of tokens, staking, rewards or yields. Emergency (break-glass) access is designed and not built; emergency settings shown in demonstrations have no effect.
Demonstrations
The demonstration cockpit uses synthetic patients generated with Synthea.