One workspace for the full behavioural health clinic day.

Screening before the visit, the note drafted after it, check-ins in between. One record, and a clinician approves every entry.

empaithy / patients / a-rDemo patient · synthetic data
Review levelModerate
Priority trend▼ Down from previous review
Screenings
PHQ-912 → 8
GAD-79 → 7
C-SSRSNo active ideation reported
Source: pre-visit screenStatus: clinician review required
Recent sessions6 total
Jul 12Sleep improving, social withdrawal noted. Plan updated.
Jun 28Medication review. Reports steadier mornings.
Jun 14First adaptive assessment completed pre-visit.
Next touchpoint
Bridge check-inin 2 days
A day in the life

A calmer clinic day.

The same workflow, from the first visit to the whole caseload.

Before the first visit
Origin collects adaptive intake and screening responses.
Before each session
Clinicians see recent changes, previous plans, and pending review items.
During or after the session
Trace drafts structured documentation for clinician approval.
Between visits
Bridge sends check-ins and brings responses back into the record.
Across the caseload
Lens and Signal help teams see trajectory and what needs review across the caseload.
Who it is for

For the clinicians and the teams around them.

Built around the people who carry the caseload.

  • Solo and group practices
    Reduce repeated intake, after-hours notes, and manual follow-ups.
  • Psychiatry and psychology clinics
    Standardise documentation, screening, review states, and longitudinal tracking.
  • Multi-location clinics
    Give teams one current patient record across providers and touchpoints.
  • Hospital and integrated care teams
    Coordinate intake, follow-up, outcomes, and review queues across departments.
empaithy / today
09:00A. R. · follow-upprepped
10:30New patient · intake readyOrigin
nowS. K. · pattern highlightedreview
14:00Team review · 3 patientsLens
Rollout

How it starts, at your size.

No rip-and-replace. It runs beside what you already have.

Small clinic

Two clinicians, one shared record from day one.

  1. 1
    ScopeWhich instruments you already use, who reviews what.
  2. 2
    ConfigureNote sections and routing set to how you document today.
  3. 3
    ConsentCapture is opt-in per patient, recorded before any session.
  4. 4
    TrainOne short session: draft, approved, and what it never decides.
  5. 5
    GoThe whole clinic, same week.
Hospital or group

One department first. The record follows the patient to every branch.

  1. 1
    ScopeOne department, its instruments, its reviewers.
  2. 2
    ConfigureTemplates per team; review items route to whoever is on duty.
  3. 3
    ConsentLanguage and record agreed with your governance lead.
  4. 4
    TrainPer clinician, focused on the review model.
  5. 5
    Pilot, then widenA small group on real clinic days before anyone else moves.
Questions we get

The things clinics ask first.

Does it work with sessions in Hindi or Arabic?

Yes, including code-switching mid-sentence. The note comes out in the language you read, with no translation step in between.

Do I have to record sessions?

No. Capture is opt-in per patient and everything else works without it. When used, the audio is transcribed and discarded, never stored.

Where is patient data stored?

Confirmed in writing per engagement, with the DPA or BAA. Encrypted in transit and at rest; patients are held as codes, not names.

Does the AI diagnose?

No. Diagnosis is always the clinician's. Empaithy drafts and highlights for review; nothing enters the record until a clinician approves it.

How do notes get into our existing system?

Approved notes export through the API or a scheduled export, with provenance and review state intact. Unapproved drafts never leave.

How long does onboarding take?

It depends on how much configuration your documentation needs. We scope that first and give you a real timeline, not a standard one.


See how Empaithy fits your clinic workflow.

Intake to review queue on a demo patient, or on your own workflow.