Everything in the build, written down.

Demographics, contact details, pronouns, allergies, medications, conditions, insurance and the clinician responsible. Every patient has a stable ID that the rest of the app refers to, so a name change never orphans a chart.

The patient view carries a full timeline: visits, results, procedures, medications, files, messages, payments, case updates and referrals, in one column, newest first.

Symptoms, vitals, the note and the recommendation, written while you are still in the room. The note attaches to that visit and stays editable afterwards.

Roles decide who reaches which parts of the workspace — a front-desk login does not get the clinical surfaces on its dashboard. Note-level gating inside an open chart is on the roadmap, not shipped.

Work notes, school notes, activity restrictions and return-to-work notes, generated from the visit using wording the app supplies rather than a document you maintain yourself. They save to the patient record and come out in an export. Printing on clinic letterhead is not wired up yet — that is the Forms module today.

Current medications on the record, visible from the chart and the visit, and included when you export or share a record.

Results recorded against the patient timeline. Protected results sit behind an identity check — verified once and held for fifteen minutes, so working through a stack of results does not mean re-authenticating for every one.

A specialty procedure reference you search by name, category or code, with the CPT, HCPCS, ICD-10-CM, modifier and revenue codes for common procedures shown alongside each one — so coding happens where the work is, not in a separate program afterwards. Anything uncommon is flagged for you to verify rather than guessed at.

A case is a thread that outlives a single visit — a specialist coordination, an investigation, a treatment plan. Each has a lead, assigned clinicians, a status and a priority.

Twelve sections per case: overview, patient issues, symptoms, diagnostics, medications, tests, images and files, referrals, care plan, patient notes, team discussion and timeline. Hide the ones your specialty does not use.

Outbound referrals tracked to a person rather than a folder. An open referral that goes quiet comes back as a follow-up instead of being forgotten.

Day, week and list views in one calendar, with a provider board for seeing the whole team at once. Book from the schedule, from the patient’s chart, or by clicking a day on the dashboard — it is the same appointment.

Meetings are scheduled the same way appointments are, with their own attendees and notes, so team time and patient time live in one calendar.

One press from the schedule. Check-in opens with the patient’s standing concern pre-filled, along with their provider, insurance and how they prefer to be contacted, and starts the visit rather than leaving it as a separate step somebody forgets.

Owner, due date and priority, one line each. Critical work looks different from routine work, and completed work stays crossed off until you sweep it.

Assigning a task notifies the person it lands on. Re-saving a task without changing the owner does not notify again, so editing a due date never spams somebody.

Set a rule once and the app does the chasing: appointment reminders on the lead days you choose, case and referral follow-ups, recurring tasks, inventory reorder points, equipment maintenance schedules and staff workload notifications.

Rules propose; people approve. Anything that costs money or leaves the building waits for a person.

Direct messages between staff, whole-team announcements, and whole-team chat, in one thread list with unread counts on the sidebar. Reply where the conversation is, rather than in a separate program.

Schedule items can be shared into a message, so “can you take my 2pm” carries the actual appointment rather than a description of it.

Patient names stay out of notification payloads — the notification says there is something to read, and Messages resolves who it is about once you are authorised to see it.

Attach a file to a message and it travels with the thread, previewable in place. Export a record or a packet of results as a PDF from the patient’s chart, or hand it to your mail app as a draft with the recipient, subject and body already written — you attach the file in that last step rather than us.

Outbound patient email goes through an explicit approval step every time. Nothing addressed to a patient leaves the building because a rule fired.

One place for what needs you: new messages, assigned tasks, results to review, schedule reminders and case updates. Read and unread are tracked per person, so your list is yours.

Today at a glance — who is coming, what is outstanding, what needs attention. Every card reads live from the workspace; none of them show placeholder content.

Choose which cards appear and drag them into the order you want. Cards a role may not see are not offered — a front-desk login is not shown the clinical ones. The layout is set for the workspace rather than per person.

One search across patients, staff, cases, tasks, files, referrals and pages. Results respect your role, so search never reveals something a screen would not.

PDFs, images, scans, documents, spreadsheets, lab results, X-rays, DICOM studies, NIfTI volumes and 3D models, filed against the right patient and searchable by type, patient or folder.

In-app preview for PDFs, images and text, so opening a result does not mean opening another program.

Press Scan and the app drives the scanner on your desk through your own driver. On a phone the camera does the same job. The result lands on the right patient, typed and searchable.

Sensitive results stay obscured until you verify — either with a one-time code sent to your account, or with Windows Hello or the device’s biometric check. There is no shared unlock code, and if verification fails the result stays covered rather than falling open.

Verifying with the device covers the next fifteen minutes and then expires on its own, so working through a stack of results is not fifteen prompts. Verifying with an emailed code currently holds for the rest of the session instead — on a shared workstation, sign out rather than walk away. An administrator can also switch re-verification off for the whole clinic in Settings.

Every unlock is written to the audit trail with who, what and when.

Build a form from your own fields, grouped into your own categories. Intake, consent, history, screening, discharge — whatever your specialty actually hands people.

Live preview as you build, so you see the printed page rather than a field list. Export to PDF, print it, or email it from the form itself, all on your clinic letterhead.

Templates for your specialty are loaded at setup, so you start by editing something rather than facing an empty screen. Upload an existing form and keep it alongside the ones you build.

Text or email a patient a link before they come in and they fill the form in on their own phone, one question at a time, at their kitchen table rather than on a clipboard in your waiting room. The answers arrive on their record. Nothing is scanned afterwards and nobody at the desk retypes a stranger’s handwriting.

The link opens only once the patient enters their date of birth, and that is deliberately not in the message — so a text read over a shoulder on a train, or forwarded to the wrong person, is not enough to open anything. The message itself names your clinic and nothing else: not the patient, not the form, not why they are coming. The link works once, and the moment the form is submitted it is spent.

LogBlues will not text a patient who has not agreed to be texted, or email one who has not agreed to be emailed. That consent is recorded on the record, with the date, and the send is refused without it rather than left to whoever is at the desk to remember.

Patients who would rather not, or who do not have a smartphone, are handed the same form on paper on your own letterhead. Nobody is turned away for not owning a phone.

Your logo, clinic details and footer applied to the forms you print or export. Set once in Settings, under Clinic profile.

Raise an invoice with as many line items as the visit needs, each with its own CPT or HCPCS code, quantity and price. Save it as a draft or issue it straight away — a draft does not count against the patient until you issue it. Every invoice carries a due date and turns overdue on its own.

Record payments against it by card, cash, cheque, bank transfer or insurance, in full or in parts, with a reference you can reconcile. The patient balance, the day’s revenue and the outstanding total are all computed from those documents rather than stored separately, so they cannot drift apart. Payments land on the patient’s timeline as they happen.

Cancel an invoice and it is voided rather than deleted: it stays on file and stops counting. A clinic’s books should not lose documents.

Not yet: emailing a payment request with a secure link needs the clinic mail connection, and claims submission through a clearinghouse is not built. Coding, invoicing, payments and balances all work today.

Stock levels with reorder points per item and location. When something drops past the point you set, the app raises it rather than waiting for someone to notice an empty shelf.

Assets with service schedules and maintenance history, so a due inspection surfaces before it lapses.

Purchase orders with an approval trail. Requesting and approving are separate permissions on purpose — a staff member can raise a request without being able to commit the practice’s money.

Supplier records with contacts and terms, linked to the purchase orders that use them.

Facility safety checks tracked with their own schedule and status, alongside the equipment they cover.

Policies and procedures in one place, side by side. A policy is the rule your clinic works to; a procedure is the steps somebody follows to carry it out. Keeping them together is the difference between having a policy and following one.

Both are searchable and carry a review cadence, so staff can be pointed at the exact procedure rather than at a binder.

Business reports covering appointments, patients, tasks and billing — filtered by date range, patient or search — computed from live records and exportable to CSV and Excel. Inventory and procurement are not reportable here yet.

Blues runs IBM Granite on the computer in front of you through a local runtime. No API key, no account, no request leaving the building, and no per-message cost. It works with the internet unplugged.

Search records, list overdue follow-ups, read the operations position, prepare a check-in, draft a task, draft an appointment, draft an internal message, generate a form and draft meeting notes. Two more are scaffolded and not switched on yet: sending an approved message outside the practice, and retrieving a document on your behalf.

Blues cannot write to the workspace on its own. Every action is rebuilt by the app from your confirmation, so the model produces text and nothing else.

It is handed your permissions, not more. It does not diagnose or prescribe. And the audit trail records that a tool ran without storing what you typed.

A register you can set, because the assistant you want at 7am between patients is not the one you want writing to a specialist.

No. The model weights are fixed and never change. There is no training, no fine-tuning and no embedding of your records into a model — not on our servers, and not on yours.

When you ask Blues something, it reads the records on your machine at that moment, answers, and forgets. Ask the same question tomorrow and it reads them again. That is the whole mechanism.

For a lookup — a patient, an overdue follow-up, the stock position — Blues is handed the relevant records at the moment you ask, from the workspace on your own computer, filtered to what your role may see. The knowledge is in your database, not in the model. Open-ended questions are answered without any clinic data attached.

This is why a new clinic gets useful answers on day one without a training period, and why deleting a patient actually removes them from what Blues can tell you.

It stays on the device, capped, and you can clear it from the assistant itself. Nothing is uploaded, because there is nowhere for it to be uploaded to.

The audit trail records that a tool ran and when. It deliberately does not store your prompt text or the reply, so the audit log never becomes a second copy of the conversation.

Everything else keeps working. Blues is a way into the workspace, not a dependency of it. No feature stops functioning because the assistant is not running.

Ten roles from Owner to Read-only, each mapped to a specific set of rights across patients, clinical notes, results, scheduling, tasks, billing, staff, security, integrations, backups, inventory, procurement, reports, cases, forms and automations.

Ten roles across sixteen permission domains decide which screens, dashboard cards and actions a person reaches, and an administrator can subtract further per person. Enforcement is in the app today; the same rules are designed to be re-checked by the backend, which is not the piece that ships first.

Invite, edit, archive, restore or remove staff. Each person gets their own role, their own sidebar and their own notifications.

The security architecture behind LogBlues: device checks, AES-256-GCM encryption of the whole local record store with the key in OS secure storage, role-based access across the workspace, re-authentication before results flagged sensitive, and a security log. It is a framework we built, not a certification anyone issued us.

Covered properly on the security page rather than repeated everywhere.

Exports, backups, protected-result verifications and security-policy changes are written to a security log you can read in the Security Center. It is a session log today — it is not yet persisted across restarts, and it does not yet cover sign-in, record access, deletes or permission changes. A durable, append-only trail covering all of those is the next piece of work on it.

Encrypted local export and import, with the export protected by AES-256-GCM and a key derived through 210,000 rounds of PBKDF2. Patients, appointments and tasks archive and restore rather than delete, so an accident is undone rather than mourned.

Not yet: cloud backup is not connected, and restoring an encrypted backup over live records is preview-only. Both are named as Premium features on the pricing page and neither ships today.

Text size, contrast, reduced motion and keyboard support, with the settings in one place rather than scattered through the app.

Six steps — sign in, your practice, the type of care you give, which modules you want, how your dashboard should look, and a review — and the workspace assembles itself: modules suggested from your specialty, forms for it already loaded.

Fifteen modules you switch on or off: schedule, patients, clinical notes, medications, tests and results, procedures, files, tasks, billing, team, cases, inventory, tools, security and reports. A dental office and a rehab clinic should not get the same screens.

Twenty-one themes. Seven come with every plan — including the Founders Edition — and the other fourteen are part of the Premium collection. Light and dark throughout, with clinical text kept readable on every one.

Practice launches in the United States and Mexico, each with its own date and time format, units, phone and postal shapes, and currency — a Mexican invoice reads in pesos, and a Mexico City number takes a two-digit area code while the rest of the country takes three. Spanish matters on both sides of the border: a great many American clinics have a bilingual front desk.

Two languages are live, English and Spanish, and a language is only offered once the interface behind it is actually translated. The rest are listed in the app as in development rather than half-finished. Choose which of the live ones your practice offers its staff.

Ten calculators built in: BMI and BMR, ideal body weight, water intake, pregnancy due date, paediatric OTC dosing, PREVENT heart risk, PHQ-9, GAD-7, STOP-Bang and CAGE. Calculations happen locally; the official sources are linked where they exist.

Windows and Android, from the same workspace. The app is responsive from a phone in the exam room to a desktop at the front desk.

Answer a few questions and the app gives you one thing to do — small enough that you will actually do it. Hold it for a few days and the next one opens. Thirty-seven steps across six levels, ordered easiest to hardest.

Tap any step to see the trial behind it, the size of the effect and the caveats. Where the evidence is weak, it says so. A hundred and thirty documents.

Gemma 3 1B running on the device itself. After one optional download it never talks to anything again — it works in aeroplane mode. It tells you when it does not know, and it refuses questions it should not answer.

No streak guilt: miss a day and nothing breaks. No social features, no sharing, no leaderboards. One reminder a day at most, off by default, naming today’s step and nothing else.

It is not a medical device and does not diagnose, treat or prevent any condition.