Security is not a feature.
It's the architecture.
LUKE encrypts sensitive fields at rest with AES-256-GCM, chains audit entries in a tamper-evident audit trail, and scopes each clinic's data to that clinic.
Field-level AES-256.
Not just TLS in transit.
LUKE encrypts patient identity, intake answers, clinical notes, messages, vitals, prescription dosing and lab results at the field level with AES-256-GCM.
SHA-256 hash columns enable lookups without decryption. Your application can search for a patient by hashed identifier without ever exposing the plaintext value in a query.
Clinical and administrative actions are recorded in a hash-chained audit trail.
LUKE writes audit entries to a hash-chained audit log. Each entry carries the SHA-256 hash of the entry before it, and the database rejects any insert that breaks the chain. Alteration becomes detectable. Clinic admins can verify the audit chain's integrity on demand from the compliance page.
Each clinic's data is kept separate.
Each clinic's data is scoped to that clinic.
Defense in depth. Every layer.
Reporting deadlines, flagged.
Breaches affecting 500 or more patients are flagged with the 60-day HHS reporting deadline.
Built HIPAA-first.
Built HIPAA-first: field-level encryption, staff MFA, a hash-chained audit log, AWS under a Business Associate Addendum.
- Compliance APIs: audit-chain verification, PHI access reports, patient data export and deletion, and breach notification
- GDPR-style data rights: data export and deletion on request. Deletion removes clinical and message records and anonymizes the patient record. Audit and consent records are retained as required
- Automated security tests: security, encryption and concurrency test suites run on every change before it merges
Hosted on AWS, under a BAA.
LUKE's clinical platform runs on AWS under AWS's Business Associate Addendum.