All case studies
Behavioral health · 12-provider clinical practice · Pacific Northwest US placeholder

Riverbend Behavioral Health

Riverbend was running their telehealth practice across SimplePractice (scheduling), Doxy.me (video), and a third-party e-prescribing tool. Three separate brand experiences, three separate logins, two HIPAA BAAs to manage, and a patient experience that consistently surfaced "where do I click again" as a top theme in their post-visit feedback. As they grew through 10 providers, the operational tax of stitching the three tools became more expensive than buying their way out of the problem.

+18 points

New-patient NPS

71% to 89%

Average new-patient signup completion

From 3 to 1

Vendor / BAA count

28 days

Time to live (License path)

The setup

Riverbend is a 12-provider behavioral-health practice in the Pacific Northwest, specializing in adult outpatient therapy with a small medication-management arm. They run a telehealth-first model — most patient visits are video, on the patient’s device, in the patient’s home.

Their stack at the time of the engagement: SimplePractice for scheduling and notes, Doxy.me for the actual video visit, and a partner e-prescribing tool for medication-management visits. Three separate brand experiences for the patient. Two BAAs to keep current. Three monthly vendor invoices. And a growing pile of patient-feedback responses that all said some version of “the technology was confusing.”

What they wanted

Riverbend wanted to consolidate. The clinical staff did not want to re-learn an EHR — they wanted an evolution of what they already had, not a rebuild. The leadership team wanted the data and the vendor relationships under their own control, given the regulatory environment they operated in. And the practice was at the size where licensing software they’d run themselves had become more economical than per-provider monthly fees on three different tools.

A self-operated, HIPAA-aware telehealth-and-EHR-lite platform under their own brand was the right shape — provided the deployment timeline didn’t disrupt patient care for more than a couple of weeks.

What we shipped

License-model deployment of two paired AppLiaison products — Telehale (telehealth visits, scheduling, e-prescribing pathway) and Patientlink (patient portal, charting, problem-list / medication-list / allergy-list, audit log) — under Riverbend’s brand and on AWS infrastructure they own. BAA in place before kickoff. Chart migration ran from the SimplePractice export through HL7-shaped intermediate format, validated session-by-session before cutover.

Provider onboarding ran ahead of patient cutover by a week — every provider had run a real video visit in the new tool against a colleague before the first real patient hit the system. E-prescribing turned on after DoseSpot’s separate provider verification finished (six days, outside the Telehale install timeline).

The outcome

Six months post-cutover Riverbend reported new-patient NPS up 18 points. New-patient signup completion rose from 71% to 89% — the win was a single-brand flow (“book → fill intake → join visit”) instead of three. The clinical-staff time on charting dropped about a quarter versus the prior tool, mostly because intake-form data auto-populated the SOAP note instead of being re-typed.

The win the leadership team mentioned most often, though, wasn’t a metric. It was a single phrase from a long-time patient: “I like the new portal — feels like Riverbend.” Six months later, the practice’s growth came from word-of-mouth referrals, not from paid acquisition. The tooling stopped being a friction point and started being part of the brand.

This case study is a placeholder. Outcome figures are illustrative; we’ll replace it with a verified version once the live customer signs off on attribution.

Apps in this deployment