Features
Everything a practice runs on.
The calendar, the chart, the notes and the money. Built as one thing, so the same session does not have to be entered twice.
Documentation
Session notes
Notes that sign and lock, psychotherapy notes kept out of the chart, and co-signature resolved against the date of service.
Read more →
Outcomes
Measures
PHQ-9, GAD-7 and your own scales — scored on a cadence, read against both the last session and the baseline.
Read more →
The week
Scheduling
Recurring series, conflict checking that holds, bookable hours, a waitlist and reminders a client controls.
Read more →
Money
Billing
Invoices, statements, superbills and Good Faith Estimates — with one figure for what a client owes, wherever it is read.
Read more →
Their side
Client portal
Appointments, documents, consent and secure messages — reached with a sign-in link rather than another password.
Read more →
Remote
Telehealth
Where the client actually was, which place of service the claim carries, and the licensure question underneath both.
Read more →
Claims
Insurance
Claim scrubbing, CMS-1500, and a real 837P for Washington L&I built against the department's own companion guide.
Read more →
The numbers
Reports
Twenty-four reports over real rows — narrowed to the caseload you can already see, and audited differently when they name people.
Read more →
Before they are a client
Somebody writing to ask for help is already telling you something private.
A practice puts an inquiry form on its own website and the submissions arrive here. What somebody writes in that box, describing why they want therapy, is the most sensitive text in this product, and they are not a client yet. The obvious thing to build is the one that emails it straight to the practice.
That is the entire email: a name, a link, and a sentence saying where the message is. Knowing one is waiting is enough to make somebody go and open the screen, and copying the message into an inbox nobody controls would undo every other protection around it.
On arrival
Encrypted from the first second
Not kept forever
Ninety days, then gone
Never the calendar
A request stays a request
The argument
One session, entered once.
A practice running a calendar, a notes tool and a billing product types the same fifty minutes into three of them, and reconciles them by hand when they disagree. Here it is one record that the rest of the product reads. Nothing below is a re-entry — it is the same appointment, seen from a different job.
-
1 Booked
The appointment is the record
A clinician, a client, a time and a service. Booking checks it against that clinician's other sessions rather than trusting whoever is looking at the screen.
-
2 Delivered
It starts owing the chart a note
A completed session with no signed note appears on the worklist by itself. Nobody has to remember which ones are outstanding. In a busy week that is the thing that slips.
-
3 Charged
The money is attached to the session
The charge belongs to that appointment — the fee, what the payer allowed, what was written off, and what is left. Not a figure retyped into a separate ledger.
-
4 Claimed or invoiced
The same charge goes out either way
Onto a claim for an insurer, or onto an invoice, a statement or a superbill for the client. One charge, so the two can never quietly disagree about what the session cost.
-
5 Read by the client
And they see what they owe, not the gross
The document reaches the client's own portal, showing their share rather than the whole balance while an insurer still has it. Same underlying record, narrowed to the person reading.
Also in here
The parts that do not need a page of their own.
Described in full where they belong rather than given a heading each. This is the shortest way to find out whether the thing you are looking for is here.
-
Inquiries from your website A form on your own site, encrypted on arrival, deleted after ninety days. Described above.
- Appointment requests A client asks for a time; the clock on answering starts when they ask.
- Calendar sync Your schedule in your own calendar, and control over how much of it travels.
- Announcements One thing said to every client, with no shared recipient list anywhere.
- Treatment plans Goals, measurable objectives, interventions, and progress rated session by session.
- Payroll Close a period and what each clinician was owed is written down once.
- Refunds Recorded as their own event, so "received" keeps meaning received.
- Product sales A workbook is sold, not charged — and cannot reach an insurance claim.
- Your own worklist Whatever you write down sits beside the work the records already imply.
- Corrections by the client They can say a detail is wrong, and both versions are kept.
- A read-only API FHIR R4, per-practice tokens, demographics and appointments only.
Start with the week you are already having.
Set up a practice, put a real week in the calendar, and see whether it fits before you move anything across.