Built in clinic,
not in a boardroom.

02 A letter from the founder

Why I built the Psychiatry OS

I am a psychiatrist, and for years I documented my work in EHRs that were generalist tools with a psychiatry skin. The signal in my specialty is longitudinal — a PHQ-9 dropping over twelve weeks, a clozapine level against a scale, an anticholinergic load climbing with each added medication — and a generalist chart never sees it. It stores prose, and the trajectory disappears into it.

So I built ClearMind the only way I know how to build clinical software: in clinic. Every workflow exists because I needed it that week, and every automation earned its place by running my own notes, claims, and refills before it touched anyone else's. Nothing here shipped from a roadmap. It shipped from Tuesday's schedule.

The thesis is simple: the visit ends and the work is already done. The note signs, the claim files, the follow-up books, the summary reaches the patient. Doctors should be attestors, not typists — you review and sign what the system has prepared, instead of spending the evening reconstructing the afternoon.

I also think documentation is heading somewhere specific. Over the next twenty years, the note becomes a rendering — one view over a structured clinical record that holds measurement, medication, and risk as coded data from the first visit. ClearMind captures the record that way today, so the trajectory is there when you and the patient need it.

Don't take my word for any of this. Watch ClearMind on your own workflows — a 30-minute walkthrough, no commitment — and see whether the visit really can end with the work already done.

— Surender Punia, MD