Security
Your charts stay on your machines, and we cannot read them.
HIPAA compliant from day one. We call it LMLSE.
Ten layers of protection around your patients’ records.
An exosystem rather than an ecosystem: it wraps the practice from the outside. Ten layers in the design, six of them working in the build you can download today, and each one built on the assumption that the one before it might fail.
The short version
Patient data does not move unless you move it.
LogBlues keeps records on the machines in your building. There is no copy of your patients on our servers, because nothing in normal use sends one.
That one decision closes off a lot of the ways clinical data goes astray. It does not close off all of them, which is what the layers below are for.
In plain words
A locked filing cabinet in your own office.
Think of LogBlues as a locked filing cabinet that lives in your own office, not in somebody else’s building. Everything inside it is scrambled, so even if someone walked off with the computer they would get gibberish without the key.
Each person on your team has their own key that only opens the drawers their job needs, so the front desk can book appointments without ever reading a clinical note. The most sensitive papers ask for a second key, a one-time code sent to that provider’s own email, before they open.
Every time a drawer is opened or something is copied out, the cabinet writes it down in a log you can read. And once a day a scrambled copy goes to a second cabinet in the cloud, so a broken computer means an afternoon of setup, not a lost practice.
Layer by layer
The six that are live. What each one is for.
-
1
The device
Before the app trusts the machine it’s running on, it checks it. Encryption enabled, screen lock present, no obvious tampering. A laptop that fails those checks is a laptop that shouldn’t be holding charts.
-
2
The record at rest
Credentials and keys live in the operating system’s own secure store, Windows DPAPI, never in a file we invented. The workspace database is encrypted at rest with AES-256-GCM under a key held in that store, and portable exports are separately encrypted with a passphrase you choose. Use Windows device encryption or BitLocker on every workstation that stores clinical attachments.
-
3
Who sees what
Twelve roles across twenty-eight permissions decide which screens, dashboard cards and actions a person reaches, and an administrator can subtract further for one individual. Blues is handed the same permissions you have, so it cannot answer past your role.
Where this stops today: the gate is at the workspace level rather than inside an open chart, so a role that can open a patient record can read the clinical notes in it. Per-note permissions and a second check in the backend are both in progress. -
4
The second door
Results flagged sensitive ask again. You get a one-time code generated from a cryptographically secure source and expiring in ten minutes; verifying that way unlocks for the rest of that session, so sign out rather than walk away from a shared workstation. Verifying with Windows Hello or a device credential instead holds for fifteen minutes and then lapses on its own. An administrator can turn re-verification off for the whole clinic in Settings, and every unlock either way is logged.
-
5
The trail
Exports, backups, protected-result verifications and security-policy changes are written to a security log alongside encrypted local export.
The assistant
Blues is inside the exosystem, not an exception to it.
The usual way to add AI to clinical software is to send the chart to somebody else’s API. We didn’t. Blues runs against a model on the clinic’s own machine, so what a provider types stays on that machine.
It’s also bound by the same permissions as the person using it: Blues cannot read or write anything you couldn’t yourself, and every write asks before it happens.
Blues uses an open-weights language model through a local runtime on the clinic computer. LogBlues may change the underlying model as local performance improves. No prompt or response is sent to a model vendor, and the local runtime does not charge by the message.
Your data
Your data is your data.
A hard drive failure, a stolen laptop, a fire — none of it should be the end of a practice. The fail-safes are built into the software, so getting your records back is something you do, not something you ask us for.
The records are already on your machines.
There is no retrieval request, because nothing of yours is held anywhere else.
A second admin you assign yourself.
Lose access to your email — and it happens — and your other administrator gets you back in.
Restore from inside the app.
Uninstalled it, replaced the computer, lost the drive: your backup comes back from your own account.
Yours after you leave.
Stop being a customer and we will still walk you through getting your records out.
Our support team will guide you through retrieving your own data, and we will not do it for you: we never take custody of a practice’s records, and we cannot restore a backup on your behalf. That is deliberate. It is the same design that means a breach of our servers cannot expose your charts — we are not holding them.
If you want somebody’s hands on it, we offer consulting, billed by the hour. What we would rather you did is assign a second administrator when you finish the launch checklist. It takes a minute, it costs nothing, and it is the single thing that stops a lost password from becoming a lost practice.
AI and your data
In plain language, before the legal version.
Nothing you type to Blues leaves your machine.
The model runs locally. There is no API call carrying a chart to a third party.
Your patient data is never used to train a model.
Not by us and not by anyone else, because it never reaches anywhere it could be trained on.
No transcripts are retained by us.
Conversations live on that device and are yours to keep or clear.
Blues is bound by your permissions
and asks before every write.
There is nothing to opt out of, which we think is a better answer than a well-designed opt-out.
If Blues ever gains a feature that sends anything off the machine, it will be opt-in, it will say so on this page, and it will be described here before it ships.
LogBlues technology
What is LMLSE?
LMLSE stands for LogBlues Multi-Layered Security Exosystem. It is our proprietary security and resilience framework, bringing together encryption, access controls, security activity records and recovery safeguards to help protect your clinic's data and saved work.
Your workspace data is encrypted automatically when it is saved. LMLSE is the framework behind these protections, with security designed into how LogBlues stores, accesses and recovers your information.
Read our Terms of Service for more about LMLSE.
Agreements and support
A BAA, and a person to email.
Business Associate Agreement: available on request, at no charge. Write to us and we will send it and talk it through. We would rather have that conversation early than have it become a surprise during your diligence.
Support is email today, answered by a person who works on the software, not a tier you upgrade into. As the practice base grows we will publish response times and hours here rather than leaving them implied.
Use the contact form — agreements, security questions and everything else
Being straight with you
HIPAA, without the hedging.
LogBlues is HIPAA compliant from day one — not a badge we bought, but the way it was built. Encryption at rest, access by role, re-authentication on protected screens, a security activity trail, and a Business Associate Agreement we sign free, on any plan.
Your own side of HIPAA is policies, training, and how the office actually runs. We hand you a checklist for it rather than leaving you to guess, and the agreement is ready the day you ask for it.
Contact form (general)
— agreements and BAA requests
Contact form (security)
— security questions and disclosure
Why any of this matters
You have patients to see.
The point of building this in from the start, rather than selling it as a tier, is that protecting your patients’ information should not become another thing you have to manage.
You are the one in the room doing the work that matters. We would like this part to be one less thing on your mind.
Four things it comes down to.
- Secure Access
- Encryption
- Permissions
- Audit & Recovery