How to Automate Osmind

Interventional psychiatry administers the treatment it prescribes

Interventional psychiatry is the corner of mental health where the practice gives the treatment as well as writing it. Osmind is the health record built for exactly that: clinics running ketamine infusions, dosing Spravato on site and putting patients through a course of TMS alongside ordinary psychiatric care. The line splits the same way: Osmind One is the record, Osmind 360 the billing technology and service, the Osmind Care Network credentialing.

A talking-therapy practice sells an hour and books a room for an hour. These practices sell a supervised dose. A Spravato patient is dosed on site and then observed in a recliner for two hours. A ketamine course is a series of infusions across weeks, and a TMS course runs most weekdays for a month and more, finished only when the whole course is.

So the schedule here is not a diary of appointments. It is a set of chairs, staff and part-finished courses, every one of them with a payer somewhere behind it.

Nobody is dosed until a payer has said yes

Each course was approved before it started, and approval is never a single event. Esketamine and TMS both sit behind prior authorisation, which carries a start date, a number of sessions and an expiry nobody is tracking except whoever last opened the payer's portal.

That queue is where a practice manager's week goes. Log in to each payer in turn, work down the pending requests, note what came back approved and for how many sessions, find the one denied on a technicality four days ago. A rejected claim keeps its reason code on the payer's site, not in the chart.

The rest collects around it. A patient dosing today needs a monitoring chair, staff cover and two hours of somebody's attention. A prepaid infusion package has a balance that exists only because a person is keeping count. A patient who missed a Tuesday in week three of TMS has quietly moved the end of their own course, and nobody notices for a fortnight.

Osmind

Prior auths that do not run out mid-course Open Spravato and TMS approvals read on the payer's own portal, with sessions remaining and the next decision date attached.

Packages that cannot be overdrawn Prepaid infusion and TMS balances set against sessions actually delivered, so a chair is never used against a package already spent.

Denials worked in deadline order Rejected esketamine and TMS claims collected with their reason codes, sorted by which appeal window closes first.

Osmind already scores the scale and scrubs the claim

A practice should exhaust what it already has, and there is a lot of it.

Charting is templated, with more than sixty customisable psychiatry note templates and a drag-and-drop intake builder for pre-visit forms. Measurement-based care is the piece most practices notice first: over fifty patient rating scales, PHQ-9 and GAD-7 among them, sent, scored and graphed automatically, so a trend exists without anyone adding up a paper form. There is SPRAVATO REMS compliance automation, TMS documentation templates, e-prescribing with PDMP access, two-way Google Calendar sync with automated reminders, and a patient app for secure messaging.

On the money, Osmind 360 pairs billing technology with a service: benefit verification, prior authorisation worked by specialists organised by payer, claims submission with psychiatry-first scrubbing, and denials management. Osmind describes AI-powered benefit verification, prior auth and denial detection for practices that want it.

All of it shares one condition. It runs on the record Osmind holds, or through people Osmind employs. The payer's own portal, the REMS programme's site, the specialty pharmacy that ships the vial and the referring prescriber's system are none of those. Each is a login and a person.

A treatment course that counts itself

Every number that would stop a course is already on a screen somewhere, posted by the payer that decided it.

Every open Spravato and TMS authorisation checked on the payer that issued it, sessions remaining counted, the ones nearing a decision date named, so a course does not halt in week four because a number ran out. Denied esketamine claims collected off each payer's site with the reason code and appeal window attached, soonest closing first.

Self-pay infusion packages set against sessions delivered and payments taken, so a seventh infusion on a six-session package is caught before the chair is used, not in next month's reconciliation. TMS courses counted against their expected pace, so a patient four sessions behind is a phone call this week, not a surprise in month two. Today's dosing list checked against the diary for a booked two-hour monitoring window, before anybody draws a vial.

The line does not move in psychiatry. Reading, counting and comparing can run unattended overnight. Anything that writes into a chart, files a claim or reaches a patient is prepared and left for a clinician or a coder to approve. What gets handed over is the looking, never the deciding.

The authorisation queue never gets shorter on its own

It gets worked every morning regardless, before the first patient arrives.

WebRun is an agent that drives a real Chrome browser, signed in the way your own staff sign in. It opens the payer's portal, the REMS site or the pharmacy's queue, reads what is on the screen, and brings back a list against your own patients with the dates attached.

It runs on your schedule inside your own private environment, sessions are not shared between tools, and a workflow can be locked to an explicit list of domains. You can watch a run and stop it. Anything irreversible drafts and waits.

Each workflow below carries the list of sites it visits, and the hour.