Private AI · Therapy practices

Use AI on session notes without sending them into the public cloud.

A managed, on-prem AI system for therapy groups, counseling centers, and mental-health practices. Session-note drafts with strict review, intake summaries, and admin follow-up — on hardware your practice controls. Designed around HIPAA, state mental-health rules, and the privacy expectations your clients walk in with.

For 5–50 clinician practices. Apple-silicon hardware. Managed by Wilcoe.

Why session notes are different.

Therapy notes carry a higher privacy bar than typical PHI. Many states give psychotherapy notes extra protection. Cloud chatbots aren't a fit for any of that. Three frictions our therapy clients walk in with.

🧠

"Psychotherapy notes have extra rules."

Under HIPAA, psychotherapy notes get heightened protection — separate authorization in many cases, narrower disclosure, often kept apart from the rest of the chart. Public-cloud AI workflows don't recognize that distinction.

🏢

"Our state has its own rules."

Many states layer additional protections on mental-health records. A national consumer chatbot can't track state boundaries. A managed appliance can be configured per office and per state if your group spans multiple jurisdictions.

💙

"Clients ask where their notes go."

Trust matters here more than in most other regulated work. "On hardware in our locked closet" is a legitimately better answer than "we use a third-party vendor that signed a BAA." Both can be defensible; one earns more trust.

What we tend to start with.

Documentation reduction with strict review. Clinical judgment, treatment planning, and assessment stay with the clinician.

01

Session-note drafts (with strict review).

Recorded sessions or clinician audio dictation → structured note drafts. Mandatory clinician review and edit before anything lands in the chart. The system never auto-finalizes a note.

02

Intake summaries.

Intake forms and prior records → a structured summary delivered to the clinician before first contact. Saves the front-loaded admin minutes that get in the way of the actual session.

03

Treatment plan templating.

Auto-populate standard sections of a treatment plan from intake and recent session notes — for clinician edit and signoff. The system generates structure; the clinician owns the substance.

04

Admin follow-up & recall.

Recall lists, post-session follow-up, billing-coordination drafts, and patient-instruction language. Front-desk acceleration with mandatory signoff before patient communication.

Built around HIPAA & state mental-health rules.

Defaults matter more here than anywhere else. Sensitive notes are local-by-default, with cloud disabled for note-touching workflows unless your policy explicitly allows it for narrow tasks.

Strict cloud-off defaults for notes.

Session notes, treatment plans, assessment results, and crisis-related documentation are configured to never leave the appliance. There's no "oops" path.

Per-office and per-state partitioning.

Multi-office groups get partitioned indexes, partitioned access, and per-state policy overlays. Your Massachusetts office and your Connecticut office can carry different retention rules.

Audit logs scoped to clinician + client.

The Security Rule expects access logs. Therapy practices need them tighter — scoped to the clinician treating the client, with breach-response workflow ready for state-specific notification timelines.

Clinician-in-the-loop, always.

The system never finalizes a note, treatment plan, or client communication on its own. Every output is a draft with a mandatory review gate before it counts.

Wilcoe Private AI is designed around your HIPAA + state obligations. Final compliance signoff is practice-specific and remains with your privacy officer or compliance counsel. Read the full HIPAA & BAAs explainer →

Deployment shape.

A representative starting point. Right-sized in the Readiness Sprint and quoted firm-specifically.

ElementTherapy group, multi-office (20–50 clinicians)
Hardware2× Mac Studio M4 Max or 1× M3 Ultra + local backup. Central rack. Site VPN or private links between offices. Per-office partitions.
ModelsLocal models for all note workflows. Cloud disabled for notes by default. Allowed only on explicitly approved non-note tasks (e.g., generic admin drafting) under written policy.
Knowledge layerLocal vector DB. Per-clinician + per-client partitioning. Per-office policy overlays. Conservative sync rules between offices.
ControlsHIPAA + state-specific controls. Access by role, site, and clinician. Breach-response playbook scoped to state notification rules. Encrypted backup. Minimum-necessary access.
Cloud fallbackDisabled for notes by default. Allowed only with explicit written policy and signed BAA for narrow non-note tasks.

90 days from sprint to live.

One workflow live in a single office, with clinician signoff and a state-specific breach-response plan ready.

Days 1–14

Risk + workflow + privacy review.

Inventory note flows. Map the first workflow. Coordinate with privacy officer + state-specific compliance counsel.

Days 15–30

Hardware + policy pack.

Right-sized appliance. Written policies covering note retention, access, and state-specific breach response.

Days 31–50

Install + identity + logs.

Network segmentation, MFA, role + site + clinician-scoped access, encrypted backup, audit logging.

Days 51–70

Connectors + first workflow.

Per-office indexing. The first vertical copilot, with strict clinician-review gates.

Days 71–90

Training + go-live.

Clinician + admin training. Audit log review. Decide what to add next.

Common questions from clinical directors.

Will the system ever store an unreviewed note?

No. Drafts are explicitly marked as drafts and aren't part of the chart until a clinician edits, finalizes, and signs. The audit log captures the review and signoff for each note.

What about psychotherapy notes specifically?

Psychotherapy notes get extra protection under HIPAA — separate authorization, narrower disclosure rules, often kept apart from the rest of the chart. The appliance respects those boundaries: separate partition, separate access controls, separate retention.

What if we operate in multiple states?

Per-office partitioning supports per-state policy overlays. Massachusetts retention rules, Connecticut breach-notification timelines, and California-specific mental-health protections can all be configured per office.

Can it touch crisis or suicidality content?

By default, yes — for documentation and follow-up. We do NOT use the system for any kind of clinical decision-support around crisis. The clinician's response stays the clinician's response; the system documents it.

What about billing and coding?

Code-suggestion can run on the appliance with mandatory clinician review before submission. We don't auto-bill anything. The clinician owns coding decisions.

How fast can we start?

The Readiness Sprint scopes the pilot in two weeks. Most practices launch live inside 90 days from sprint kickoff.

What does it cost?

Sized in the Readiness Sprint. Pilots vary several-fold across practice shapes, especially across multi-office groups. How we think about cost →

Use AI on session notes. Without giving them away.

Book a 30-minute Readiness Call. We'll walk through your highest-leverage workflow, the privacy frame for your practice and state, and what a 90-day pilot would look like.

Book a Readiness Call →

or

Take the readiness check →