Until this week, ARAGS assumed everyone was a clinic. The assistant said “patients.” The onboarding asked about your practice. The dashboard counted appointments. For the organizations we built it for, that was right. For a law office, a bookkeeper, or for that matter our own company, it was a little absurd, and the absurdity told me something.
Healthcare is still where this company is going. It is the hardest version of the problem, the one with the most to protect, and the one the system was designed around. But the hoops a clinic has to jump through before it can trust a new system are enormous whatever the specialty, and while we clear them, other organizations with records worth protecting can use the same system today. A law office. A bookkeeper. A consultancy with client files. Each of them is a custodian of something.
What the system asks now
During onboarding, the assistant now asks what kind of organization you are, and it will not mark your setup complete until an answer is on record. Seven kinds, which collapse into three vocabularies: one for clinics, one for firms and businesses, and one for an individual working alone. A dental practice has patients and appointments. A bookkeeping firm has clients and engagements. The same tool that files a document or drafts a follow-up does the same work in either case; it just stops calling your clients patients.
The interesting part is not the vocabulary. It is the rule about how the kind gets written down.
It never guesses
A language model is very good at inferring. Tell it your firm is called Smile Dental and it will conclude, correctly, that you are a dental clinic. The temptation is to let it conclude and move on. We refused that, deliberately. The kind is declared, never inferred. If you name it yourself, the assistant writes it. If the assistant has only derived it — from a name, from a description — it says the proposed kind back to you in plain words and writes nothing until you confirm. A name is not evidence: a firm called Leask & Associates could be dental, legal or accounting.
That is a small rule with a long reach. The kind of organization you are determines what the system will say to the people who contact you. It is not the sort of fact a system should decide about you on a hunch, and the record of the conversation shows which it was: what you said, what the assistant proposed, what was written in answer to what.
One posture, not a division
The easy version of this feature would have been a lighter product for non-health organizations: fewer walls, because fewer rules apply. We did not build that, and the reason is that it would have meant maintaining two postures and explaining, forever, which one you were on. One posture is simpler to run, simpler to audit, and simpler to promise. A bookkeeper's client files get the same silo, the same screening and the same trail a clinic's records get. The firm does not have to care that the design came from healthcare. It just gets the benefit of it.
There is a doctrine behind that, and it is held by something mechanical rather than by good intentions: the kind is presentation only. A test in our own build scans the code and fails if the declared kind is ever read by anything that decides what is protected, where data lives, or who may see it.
Why do it now
We have no external clinics yet. That is exactly why. Changing how a system speaks is cheapest when it is speaking to nobody, and the precedent it sets — that the system adapts its words to the custodian and its protections to no one — is one I wanted in place before the first real tenant, of any kind, arrived. The first organization to run under the new rule was our own: we told the assistant that ARAGS Inc is a software company, and it stopped calling our records patients.
Healthcare remains the end of the road. The road just got wider.
Running a practice, a firm or an office with records worth protecting? Apply for Beta Access.