Case studies

Two ways medscrub goes to work.

Clinicians running it as their daily workspace, and software companies building on the proxy underneath.

For cliniciansDesktop app
Monarch Health

Monarch Health

Internal medicine · Sandpoint, Idaho · eClinicalWorks

The medscrub desktop app as a daily workspace: four assistants the practice wrote itself, nightly chart prep, and open plans — plans left unresolved, flagged before the patient is in the room.

~2 hrs

saved / clinic day

150

charts / night

3

open plans / patient

OPEN PLANS · 3 OF 5 PLANS UNRESOLVED

Type 2 diabetes — suboptimal control

PLAN Recheck A1c in 3 months · 04/02/2026

07/10/2026 A1c 8.2% — above goal, no follow-up scheduled

Read the case study →

For developersAPI · any LLM or gateway
eSpiral

eSpiral

Clinical intelligence platform · SMART on FHIR · Hospital residencies

Safe LLM interactions for hundreds of residents and their supervisors — every call routed through medscrub's API, which works with any LLM or gateway.

100s

residents covered

18

Safe Harbor identifiers

0

PHI in the cloud

What the AI model sees

"name": "[NAME_1]"
"mrn": "[MRN_1]"
"cc": "knee pain, bilateral"

Read the case study →

See each capability in a real deployment.

More stories in progress.

If you're using medscrub in production, we'd love to tell yours. Share your story

Solo practice

MIPS coding optimization and revenue recovery

Health system

Population health screening at scale

Payer integration

Prior authorization automation