Why ShriMD Is Async-First, Not a Scheduling Calendar With Extra Steps

Every EHR vendor we compared ourselves against during evaluation — Canvas Medical, Healthie, Charm, Jane, Cerbo, Osmind — treats a scheduled, synchronous video visit as the default clinical encounter, with async messaging as a bolt-on convenience feature. We built ShriMD the other way around.

For a cash-pay, condition-specific practice (weight management, hormone therapy, and similar recurring-care models), the overwhelming majority of encounters don't need two people staring at a camera at the same scheduled time. A provider reviewing a structured intake, a photo, and lab context can make a clinically sound decision asynchronously, in the time it actually takes — not the fifteen-minute slot a calendar forces on both sides.

So in ShriMD's queue-and-claim model, a request lands in an async queue the moment it's submitted. Any credentialed, licensed provider on the network can claim it and act — no scheduling handshake required. Scheduling exists (booking, timezone handling), but it's a secondary surface for the specific subset of care that genuinely requires a live visit, not the platform's home screen.

This ordering isn't a missing feature — it's a deliberate default, because most EHR-vendor evaluation documents assume synchronous care is the baseline and async is the exception. For the practices ShriMD is built for, it's the reverse.