Encrypted patient identifiers
Patient names, dates of birth and other identifiers are encrypted in the database with AES-256-GCM, on top of encrypted HTTPS connections.
Security
Patient trust,
built into the record.
A plain account of how Sigil protects patient information today, including what is not finished yet.
A tamper-proof audit log
Access to patient records is logged, and the database itself blocks any change to or deletion of an audit entry.
Two-factor sign-in
Staff accounts can require a time-based code from an authenticator app, and a code cannot be reused.
Role-based access
Front desk, clinical staff, prescribers, billing and administrators each see and do only what their role allows.
Each practice's data kept apart
Every query is scoped to the practice signed in, and each release is checked to confirm one practice can never read another's records.
Encrypted, off-site backups
The database is backed up every night, encrypted, and copied to a second server.
Common questions
Straight answers.
Will you sign a BAA?
Yes. A business associate agreement is signed before any real patient information goes into Sigil. Pilots start with synthetic patients.
Where is Sigil hosted?
On dedicated servers we own in a secure U.S. data center, not on shared consumer hosting.
Is Sigil a certified EHR?
Not yet. Sigil is not ONC-certified today. If your practice reports MIPS Promoting Interoperability, talk to us before starting a pilot.
Security review
Need more detail for your review?
We will walk your team through it on a call.