50+ clinics now run remote care with a nurse-assisted telehealth platform

We built Galen, a nurse-assisted telehealth platform. A clinic nurse operates the diagnostic tools on site, an examination camera, an otoscope, and a digital stethoscope, while a remote doctor runs the full visit by live video, guides the nurse with a shared body diagram, and signs the prescription at the end.

increase in patient engagement
30%
clinics onboarded in just 12 weeks
50+
reduction in in-person visits
60%
In this article

Short answer

RaftLabs built Galen, a nurse-assisted telehealth platform. A clinic nurse operates the examination camera, otoscope, and digital stethoscope while a remote doctor consults by live video, guides device placement with a shared body diagram, and signs the prescription digitally. The client reported 50+ clinics onboarded in the first 12 weeks and adoption across 150+ hospitals.

The ask

A US healthcare team came to us with a gap no video call could close. Their patients could talk to a doctor from home, but the doctor could not examine them. A routine checkup still meant a trip to the clinic, and for rural patients that trip could take half a day.

We built Galen, a nurse-assisted telehealth platform. A clinic nurse operates the diagnostic tools on site. A remote doctor runs the full visit by live video. The doctor guides the nurse with a shared body diagram, and signs the prescription at the end.

Fifty-plus clinics onboarded in the first 12 weeks. That includes clinics in rural areas, where patients used to travel for routine checkups.

A nurse-led examination streamed to a remote doctor who signs the prescription, hand-drawn illustration

At a glance

Client
US healthcare team (under NDA)
Timeline
14 weeks
Scope
Nurse-assisted telehealth web app: doctor, nurse, and patient views

What we had to solve

  • A video call cannot examine a patient

    A doctor on a video call can listen and advise, but cannot look in an ear, listen to a chest, or take a close look at a rash. Diagnoses waited on reports that arrived days later. Patients in rural areas still had to travel for routine checkups, even when the visit itself was simple.

  • A remote visit left no record to support payment

    Sessions were not recorded. There were no structured visit notes and no signed prescription at the end of a call. Without a clear record, the clinic could not show an insurer what happened in the visit, so payment for remote care stayed uncertain.

  • It had to work where connections are weakest

    The patients who need remote care most often live where the internet is worst. A visit that drops when the signal dips is not care, it is a failed appointment. And every record had to stay private: each person on the platform should see only the patients their job covers.

The call

The call was to turn the video call into a real clinical visit

A nurse on site operates the examination camera, the otoscope, and the digital stethoscope. The doctor directs the nurse with a shared body diagram. The doctor writes structured visit notes during the session. The doctor signs the prescription at the end of the visit. Every session is recorded as one file, so the clinic holds a complete record for payment.

We refused two things. We did not build a native mobile app. Patients join from a browser link, with no login and nothing to install. We did not build a link into the clinic's records system. We did not build an AI symptom checker. Doctors pay a subscription to practise on the platform. Booking checks that the subscription is active before a visit is confirmed.

How a visit runs

  1. Nurse operates diagnostic tools while a remote doctor directs the visit

    The nurse runs the tools; the doctor directs the visit

    The nurse switches on each tool from one screen: the main camera, the examination camera, the otoscope, and the stethoscope. The doctor sees every feed in one view and marks a body diagram to show the nurse exactly where to place each tool. No spoken guesswork, no delay. At the end of the visit, the doctor signs the prescription and the visit notes digitally, and the signed documents are ready to download. The full session is recorded as one file, so the clinic keeps a complete record of what was seen, heard, and decided.

  2. Patient joins a visit from a browser link on a weak connection

    Built for the weakest connection in the room

    Patients join from a browser link. There is no login and no app to install, which matters for older patients and for clinics where the staff are not technical. The video quality adjusts itself to the connection instead of dropping the call, and a brief dip does not end the visit. Reminders go out by message, email, and text. Booking checks the doctor's calendar and time zone, so no two visits clash. Each person sees only the records their role needs. A nurse sees their clinic's patients. A doctor sees their own appointments. A patient sees only their own visits.

What the platform produced

Client-reported outcomes from an NDA engagement. These are the client's own figures, not independently audited measurements.

ResultWhat changedPeriod or contextEvidence and limitation
Clinic onboarding50+ clinics operational in the first 12 weeksFully operational: booking visits, holding sessions, and preparing the paperwork for paymentClient report; onboarding built for clinical administrators, patients join from a browser link with no login
Hospitals using the platform150+ hospitalsAdoption across hospitals, as reported by the client at the time of this refreshClient report; the project record does not state a measurement period for this figure
In-person visitsDown 60% for conditions that do not require physical presenceRoutine checkups that previously required travel, including rural settingsClient-reported
Patient engagementUp 30% as routine care moved to structured virtual sessionsPatients with ongoing conditions who previously travelled for each checkupClient-reported

Where this applies

Where this applies

This story fits a healthcare team that wants remote visits to carry real exam data, not just a chat. It fits best where patients travel far for routine care, or where the internet is weak. It is the wrong fit if you need a mobile app, or a full link into your records system. Those were choices we made on purpose. If your team faces the same problem, our healthcare software work covers it. Our healthcare page has the full picture.

Frequently asked questions

Straight answers to what buyers ask before they scope. Still stuck? .

A standard video call gives the doctor what the patient can describe. A nurse-assisted visit adds a trained nurse on site. The nurse operates the examination camera, the otoscope, and the digital stethoscope while the doctor runs the session remotely. The doctor directs device placement with a shared body diagram. The doctor sees and hears the same exam data as in person. The prescription is signed digitally at the end. The result is a complete clinical visit, with structured notes and a recording, not a call that ends in advice alone.

The onboarding flow was built for clinical administrators, not technical staff. The admin portal sets up clinic accounts. Doctors and patients need no installation and work in the browser. Tools connect through standard USB and Bluetooth, with no setup during a visit. Patients join from a link with no login. The 12-week figure counts clinics that were fully running. They were booking visits, holding sessions, and preparing the paperwork for payment.

Yes. That was a design requirement from the start. The video quality adjusts itself to the connection instead of dropping the call. The platform shrinks the video and audio feeds to fit weak connections. A brief drop does not end the visit. The session picks up where it left off. More than 50 clinics in rural settings onboarded in the first 12 weeks without performance problems.

Work with us

Recognise this problem in your business?

Tell us what's broken. We'll diagnose it and show you exactly what to fix first, before you commit to anything.

  • Scope and cost agreed before work starts. No surprises. No obligation.
  • Working prototype within 3 weeks of kickoff.
  • Pay by milestone. You see progress before each invoice.
  • 60-day post-launch warranty. Bug fixes, UI tweaks, and deployment support. No retainer.
  • All conversations are NDA-protected.