Systems & Innovation

The care is only as good as the system around it

Good clinicians work inside referral pathways that fail people, documentation tools that fight them, and reporting that tells them little. I spend my working days on that layer.

The same question, from farther away

What produces psychological change that lasts is not only a clinical question. It is also an operational one. People cannot use treatment they cannot find. Clinicians cannot think well inside tools that fight them. Outcomes cannot be understood if the only thing the system records is whether a score moved.

I currently work in behavioral health operations and systems design at Peak Forensic Psych Services / Peak Memory Clinic, across multiple sites. At a high level that means clinical operations, workflow design, treatment-delivery infrastructure, documentation processes, reporting, and the internal tools that surround care. I am not describing proprietary systems here. The interesting part is the shape of the problems.

The professional strength I keep returning to is fairly simple: sit with an ambiguous, inefficient, or poorly named operational problem long enough to see the system underneath it, then design something practical. Software fluency helps. It is not the point.

Three problems
I keep coming back to

01

Finding a clinician who actually fits

It is still unnecessarily difficult for someone to identify a clinician who is genuinely suited to their particular needs: not merely available, nearby, or well marketed, but a real therapeutic fit. Matching remains one of the least solved problems in mental health care, and people pay for that failure with months of the wrong work.

02

Infrastructure that does not fight the work

Many EHRs, documentation tools, and practice-management systems are expensive, fragmented, and built around billing rather than thinking. Clinicians experience the note as part of clinical work. Most software treats it as an administrative leftover. I am interested in making these systems cleaner, more useful, and less intrusive.

03

Responsible AI around care, not inside the relationship

There are places where machine assistance might usefully support assessment, documentation, decision support, treatment selection, or outcome measurement, if it stays narrow, auditable, and subordinate to human clinical judgment. The posture is not that AI will replace therapists. The interest is reducing unnecessary friction around care.

Layered paper and stone edges joined by a thin brass line

How the days are actually spent

Operations as clinical infrastructure

These are the kinds of problems the work tends to involve. They are not a list of services, and they are not a tour of any one organization’s internals.

Clinical operations
The workflows and coordination that determine whether treatment can actually be delivered.
Treatment-delivery infrastructure
The systems that carry a person from referral through care, across sites and programs.
Documentation and EHR friction
Notes, records, and tools that either support clinical thinking or consume it.
Process improvement
Finding bottlenecks, naming them accurately, and changing the work rather than adding another dashboard.
Reporting that clinicians can use
Information that tells someone something about the work, instead of only satisfying a report.
Where automation belongs
Reducing repetition around care without pretending a model can sit in the chair.

Currently

Peak Forensic Psych Services / Peak Memory Clinic. Clinical operations, workflow and systems design across multiple sites.

  • Clinical operations and multi-site program operations
  • Workflow design and process improvement
  • Documentation workflows and internal tools
  • Operational reporting and healthcare technology, used carefully

If this is the layer you work on too

Get in touch