X-rays, reports and forms.
Upload an X-ray, a lab report or a signed consent form. It is encrypted before it is stored, filed against the patient and the encounter, and kept out of reach of anyone who should not have it.
- AES-256-GCM
- Per-patient files
- Hot to archive
- Per-plan quotas
- Legal hold
What happens to a file
X-rays, reports and signed forms belong with the patient, not in a folder.
Encrypted before storage
A patient file is encrypted with AES-256-GCM before it is written, and what lands in storage is a unique nonce plus ciphertext with no readable content. The key lives in the deployment's configuration, not in the bucket beside the file.
Not every asset is clinical
Clinical uploads are encrypted. Non-clinical assets such as a clinic's branding are stored as they are, because a logo is not a medical record and encrypting it would only make it slower to serve.
Filed, not dumped
A file is attached to the patient it belongs to and, when it came from one, to that encounter, so it appears on the timeline rather than in a folder nobody opens.
Known file types
X-rays, lab reports, prescriptions, documents and attachments are distinguished, which is what makes the record navigable.
Legal hold
A file can be marked as held, which is what stops it being cleared when a clinic tidies up its storage.
Uploads go through the API
The browser uploads through the API rather than straight to the bucket, so a file is never public even for a moment.
Storage that cools off
A file stays on hot storage for 30 days, moves to warm for the rest of the first year, and then to archive. A scheduled scan does the moving and never deletes anything.
A limit you can see
The plan's storage allowance is checked before an upload rather than after, and the clinic can see how much of it is in use.
What it does not do
- Handing a file to the patient directly