Skrypt Journal of Clinic OperationsVol. 01 · 2026 · № 007

A patient is on the phone. The EHR has no API. The session expires every two hours. Here is how the booking still lands.

No API, a patient on the line, and a record system that logs itself out every two hours. Skrypt Health uses Browserbase to keep one warm EHR session that its AI receptionist reads mid-call, with the credentials fenced off from everything else. About 70 appointments a week booked straight into the EHR, 1,230 refill requests routed, 13,000+ lab results mirrored and triaged; zero browsers opened by the clinical readers.

Start reading
Partner case study · 6 min readPaper ID: SJCO.2026.007
~70 / weekAppointments written into the clinic's EHR during live calls
13,400+Lab results mirrored out of the EHR and triaged, 8,500 of them in the last 30 days
1,230Prescription refill requests routed to the pharmacy desk
0Browsers opened by the readers that use the session
"We needed one login that stays warm and behaves exactly like a careful employee. Everything else in the stack should never have to log in, and should never see a credential." — Hasan Ahmed, Founder & CEO, Skrypt Health

§ 01 About Skrypt Health

Skrypt Health builds the AI employees that run a clinic's day-to-day operations. Its receptionist, Ani, answers every call, books straight into the clinic's EHR, takes prescription refill requests and closes the loop on lab results, following up with patients. Dental, veterinary and medical clinics across North America run on it, and every one of those actions touches patient health information.

§ 02 The problem

The record system had no front door for software, and the caller couldn't wait.

Skrypt's medical clients run on a major cloud EHR. For Ani to be a real receptionist there, it has to read the schedule while the patient is still on the line, book the visit before they hang up, capture refill requests against the right chart, mirror lab results into the clinic's queue and write follow-up outcomes back. The vendor's API licence for those actions was still a marketplace request. The practice couldn't wait, and the clinic's own staff login was never something Skrypt would automate.

The alternative was a service account that behaves like a trusted staff member: logs in, passes the single sign-on check, keeps the session alive and never touches anything it isn't configured to touch. Doing that with a scripted browser on a laptop is fragile in exactly the ways healthcare can't afford. Sessions expire every two hours. MFA challenges appear at the wrong moment. A retry loop on a bad password can lock a clinic out of its own system. And a browser that holds a clinical login is a browser that holds credentials to protected health information, so it has to be the one place that ever does.

There was no room for the process to "run eventually." It had to work while a patient was asking for Tuesday at 10.

"Healthcare is high-risk and the phone is live. You don't get to tell a patient the robot is thinking. The schedule check has to be there, now, and it has to be right." — Hasan Ahmed

§ 03 The solution

One warm session, kept by Browserbase. Everything else builds on it.

Skrypt runs a session keeper on a timer. Every 45 minutes it opens a Browserbase session with Skrypt's own EHR account and its own persistent browser context, completes the login, and caches the resulting session for the rest of the platform. Because the browser profile persists between runs, the EHR remembers the device and the MFA challenge becomes rare instead of routine.

  • Log in like a person, on a schedule. The keeper signs in well inside the EHR's two-hour window, so one failed run still leaves a valid session and a second chance before anything notices.
  • One context per environment. Development and production each use their own account and their own Browserbase context. Two keepers never share a profile, so neither can overwrite the device trust that keeps MFA quiet.
  • Everything else stays headless. Mid-call availability checks, refill capture, the schedule mirror and the lab mirror read the cached session over plain HTTP. They never open a browser and never hold a credential. Bookings use the same sign-in and land directly in the EHR.
  • Fail closed, never retry blind. If the session is missing, the readers return nothing and Ani hands the caller to the front desk. A credential error surfaces to a person; it is never retried, because the EHR counts failed logins per user.

The security boundary is the whole design. Exactly one process ever holds the clinical login, and it runs in a managed, inspectable browser that Skrypt can see. The readers are fenced by request shape: the lab mirror may only submit the document search form and fetch lab-result documents for the configured office, and a test pins those imports so the boundary can't drift. Credentials never pass through Ani, never through the call, never through the portal.

"Browserbase gave us the one piece we didn't want to build: a browser that keeps its memory between runs and sits somewhere we can inspect. Everything we care about lives on top of that session." — Hasan Ahmed

§ 04 The result

With the session kept warm, Ani checks availability and books into the EHR during the call. At one family medicine practice in New York, that is about 70 appointments a week written directly into the EHR, out of 5,853 calls handled, with 1,230 refill requests captured and routed to the pharmacy desk and 533 calls taken after hours. Lab results run through the same session at a different scale: more than 13,400 lab results have been mirrored out of the EHR into the clinic's queue, 8,500 of them in the last 30 days; 9,300 have been triaged and 4,600 published to patients, and the follow-up loop that calls patients runs against the same login.

The change is measured in what stopped happening. No scheduled job has opened a browser since the keeper went live. Session expiry stopped being an incident. An MFA challenge is a logged event instead of a page nobody is watching. And the clinic kept its schedule, its record system and its own staff logins; Skrypt added one trusted account and the discipline around it.

§ 05 What it means for clinics

Deep integration without handing over your logins. A practice gives Skrypt a single named account with the permissions it needs, and keeps everything else. Ani reads and writes inside the clinic's record system under that account, under a signed Business Associate Agreement, with a session that is refreshed on a schedule and a boundary a reviewer can inspect. Bookings, refills and labs all run through it today. As the vendor's API opens up, the same workflows move to it; the clinic doesn't wait, and the patient on the phone doesn't either.

§ 06 Conclusion

In one word: "Steady."

"The best thing I can say about it is that I forgot it was there. The session is just there, every day, and Ani does the work." — Hasan Ahmed, Founder & CEO, Skrypt Health