Skrypt Health's AI receptionist, Ani, maintains many workstreams to deliver a seamless patient experience. Skrypt uses Browserbase to keep a fresh login to the clinic's EHR (electronic health record) system saved and ready. When Ani needs the EHR during a call, it opens a short Browserbase session that starts already logged in, and never handles a password.

At one family medicine practice in New York:

Lab results triaged in the last 30 days
8,500
Refill requests sent to the pharmacy
1,230
Speak with our team

About Skrypt Health

Skrypt Health builds AI agents that handles a clinic’s daily operations. Its agent, Ani, works as a HIPAA-compliant AI receptionist. Almost everything Ani does involves patient health information: answering calls, booking appointments, taking prescription refill requests, following up with patients, tracking everything in clinic’s records, etc.

The Problem

Skrypt's medical clients use a major cloud EHR. Ani has to check the schedule and book visits in it while the patient is on the phone. It also logs refill requests to the right patient chart, copies lab results into the clinic's review queue, and records follow-up outcomes.

The EHR vendor's API didn't cover those actions yet. Skrypt's request for access was still pending in the vendor's marketplace, and the practice couldn't wait. Skrypt didn't want to automate a staff member's personal login either, so it set up its own dedicated account in the EHR, which signs in through single sign-on.

However, a script running on one machine couldn't keep that account reliably logged in. Sessions expire every two hours, and MFA (multi-factor authentication) prompts show up at unpredictable times. A script that retries a failed password can lock the clinic out of its own EHR.

“We needed one login that stays warm and behaves exactly like a careful employee. Everything else in the stack should never have to open a browser.” — Hasan Ahmed, Founder & CEO, Skrypt Health

The Solution

Using Browserbase, Skrypt built a small service it calls the session keeper. Every 45 minutes, the keeper starts a Browserbase session, logs in to the EHR with Skrypt's account, and saves the login in a Browserbase context so the rest of Skrypt's platform can reuse it.

A context saves the browser's cookies and stored data from one run to the next. Each new session that loads it starts already logged in, so nothing else in Skrypt's platform has to sign in.

How Skrypt set it up:

  1. Log in well before expiry. The keeper logs in every 45 minutes, against a two-hour expiry. If one run fails, the login saved by the last run is still valid and there's time for the next run.
  2. Keep environments separate. Development and production each have their own EHR account and their own Browserbase context, so one can't overwrite the other's saved login.
  3. Only one process logs in. The tools Ani uses during a live call each open a short, fresh Browserbase session that loads the saved context. Skrypt's other jobs (logging refills, copying the schedule and lab results) reuse the saved login through ordinary web requests. None of them sees a password.
  4. Stop on errors instead of retrying. If the saved login isn't available, Ani hands the caller to the front desk. If a login fails, a person gets alerted. The system never retries a failed login, because the EHR counts failed attempts per user.

Skrypt also limits what each service can do with the saved login. The lab service, for example, can only search documents and download lab results for the configured office. An automated test checks that this limit doesn't change. Skrypt's EHR password is only ever entered in one place: the keeper's Browserbase session, which Skrypt can watch and inspect. It never passes through Ani, the phone call, or the Skrypt 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, Founder & CEO, Skrypt Health

The result

Because a fresh login is always saved and ready, Ani has been able to streamline all of its workflows. At one New York family medicine practice, Ani has handled 5,853 calls, including 533 after hours, and books about 70 appointments a week directly into the EHR. It has also captured 1,230 refill requests and sent them to the pharmacy desk.

Lab results use the same saved login. More than 13,400 have been copied from the EHR into the clinic's queue, 8,500 of them in the last 30 days. 9,300 have been triaged and 4,600 released to patients.

What's next

Skrypt plans to keep Browserbase in its stack as it brings on more clinics. When the EHR vendor's API becomes available, the same workflows can move to it.

If your agents need reliable, secure access to systems that don't have an API yet, talk to our team.

Start building with Browserbase

Run headless browsers for your agents and automations at scale. Get started for free in minutes.

Sign up for free