A React Native app for video consultations, repeat prescriptions and results — with encryption throughout.
View live demo Opens a working demo with sample content in a new tab.
On location
Doctor MaskPhoto: Direct Media (CC0)
Doctors HospitalPhoto: Oles kanebckuu (CC0)
Doctor LookingPhoto: EVG Photos (CC0)
Doctor PatientPhoto: Direct Media (CC0)
Doctor PatientPhoto: Direct Media (CC0)
About the Project
This case study covers telehealth app development for a private healthcare group that wanted patients to see a clinician, request repeat prescriptions and read their results without phoning reception or opening a scattered trail of emails. The group’s clinicians were ready to consult remotely; what they lacked was a patient app they could trust with clinical data.
We built a React Native app for iPhone and Android that handles video consultations over WebRTC, repeat prescriptions routed to the patient’s nominated pharmacy, and results released with clinician commentary. Encryption runs through every layer, biometric sign-in protects the app on the device, and the app reads from the group’s clinical systems rather than keeping a second copy of the record.
About the Client
The client is a private healthcare group offering GP-style appointments and specialist care. Patients expect the convenience of booking and consulting from their phone, while the group has to meet strict clinical governance and data protection obligations.
Before the app, video calls ran on general-purpose tools, prescriptions were requested by phone, and results reached patients in emails that were easy to lose. The group wanted one secure place for all of it.
Project Goals
Start video consultations on time, with connection problems caught before the appointment.
Let patients request repeat prescriptions in the app, approved by a clinician and sent to their pharmacy.
Bring results, letters and care plans into one place patients can find again.
Keep clinical data inside the group’s governance framework.
Deliver one codebase for iPhone and Android.
Project Overview
The Challenge and Our Solution
The Challenge
Consultations ran on a general-purpose video tool with appointments booked by phone, so clinicians spent the first minutes of each call on technical problems and patients had no single place to find results, prescriptions or care plans. Handling clinical data in a consumer tool was also a governance problem the group could not defend.
Our Solution
We built a React Native app with WebRTC video designed for the consultation itself: a connection test before joining, a waiting room, in-call notes for the clinician and automatic fallback to audio when bandwidth drops. Records, results and care plans sit behind biometric sign-in with encryption at rest and in transit, and the clinical record of truth remains the group’s system — the app reads and writes through its API rather than storing a second copy.
Video Consultations That Start on Time
Most wasted minutes in remote care happen before the conversation starts: a camera that will not switch on, a microphone blocked by a permission, a connection too weak for video. The app runs a connection test ahead of the appointment and places the patient in a waiting room, so problems are fixed before the clinician joins rather than during the consultation.
During the call, WebRTC carries audio and video directly, clinicians can take in-call notes, and if the connection degrades the app falls back automatically to audio so the consultation can continue.
Pre-call connection testing and a waiting room
In-call notes for the clinician
Automatic audio fallback on weak connections
A Repeat Prescription App Connected to the Pharmacy
Repeat prescriptions used to mean a phone call during opening hours. Now patients request them in the app, a clinician reviews and approves each request, and the prescription is routed to the patient’s nominated pharmacy. Patients see the status at each step and receive a notification when it is ready to collect.
For the group, prescription requests arrive in a consistent format with the information clinicians need, which shortens review time and reduces follow-up calls.
Push notifications keep patients informed without them having to check: a reminder before a consultation, an update when a prescription is approved, and a message when new results or letters are available to read.
Results and Care Plans Patients Can Understand
Results are released into the app together with clinician commentary, so a patient reads what a number means for them rather than a bare value. Letters and care plans sit alongside, giving patients one place to follow the advice they were given instead of searching old emails.
Because the app reads this information from the group’s clinical system APIs, there is no duplicate clinical record to keep in sync or to secure separately.
Encrypted by Design, Tested Like a Clinical System
Security was designed in from the start. Biometric authentication protects access on the device, data is encrypted in transit and at rest, and sensitive information is stored in encrypted storage rather than ordinary app storage. Clinical data handling now sits inside the group’s governance framework instead of across general-purpose tools.
React Native and TypeScript give the group one codebase for both platforms, and end-to-end tests with Detox exercise the critical journeys, such as joining a consultation and requesting a prescription, before every release.
Our Process
How We Delivered It
1
Clinical Workflow Discovery
We worked with clinicians and reception teams to map consultations, prescriptions and results from both sides.
2
Security and Governance Design
Authentication, encryption and data flows agreed with the group’s governance leads before any screens were built.
3
Integration With Clinical Systems
APIs connected so the app reads results, letters and care plans without holding a duplicate record.
4
React Native Build
One TypeScript codebase for iPhone and Android, with WebRTC video, push notifications and biometric sign-in.
5
End-to-End Testing and Launch
Critical journeys automated with Detox, then released to patients in stages.
Key Features
What We Delivered
WebRTC consultations
Connection testing, waiting room, in-call notes and automatic audio fallback.
Repeat prescriptions
Request, clinician approval and routing to the patient’s nominated pharmacy.
Results & care plans
Results released with clinician commentary, plus care plans the patient can follow.
Encrypted by design
Biometric access, encryption in transit and at rest, and no duplicate clinical record.
Outcome
Results and Impact
Consultations start on time, with connection problems caught before the appointment.
Repeat prescriptions requested in-app and routed straight to the patient’s pharmacy.
Results, letters and care plans in one place instead of scattered emails.
Clinical data handling brought inside the group’s governance framework.
Client Feedback
What the Client Says
★★★★★
Consultations start on time because the app tests the connection first.
Clinical Services ManagerPrivate healthcare group
Services
Services Behind This Project
The React Native App, React, Mobile App expertise we used to build this mobile app development — and can bring to yours.
High-performance Android and iPhone apps built with Flutter, Dart, Kotlin and Swift — from idea and UI/UX design to Google Play and App Store launch.
Learn more
FAQ
Frequently Asked Questions
Is WebRTC suitable for medical video consultations?
Yes, when it is implemented carefully. WebRTC encrypts media by design and works on modern phones without plug-ins. Around it we add connection testing, a waiting room and an audio fallback, because a reliable consultation matters more than video quality alone.
Why build in React Native rather than two native apps?
React Native lets one team deliver iPhone and Android from a single TypeScript codebase, so features and fixes reach every patient at the same time. Where a native capability is needed, such as biometric sign-in or encrypted storage, we use the platform’s own APIs through native modules.
Does the app store patient records?
In this project, no. The app reads results, letters and care plans from the group’s clinical systems through APIs and shows them to the patient. Avoiding a second copy of the record reduces risk and keeps the clinical system as the single source of truth.
How are repeat prescriptions kept safe?
Every request is reviewed and approved by a clinician before it is routed to the patient’s nominated pharmacy. Patients see the status at each stage, and the request reaches clinicians in a consistent format, which supports safe and quick decisions.
What affects the cost of a telehealth app?
The main drivers are the number of integrations with clinical and pharmacy systems, the security and compliance requirements, and how many patient journeys are in the first release. Video, prescriptions and results together form a substantial build, so we usually agree a focused first phase.
Can you work with our existing clinical system?
Usually, yes. Most clinical platforms offer APIs or integration partners. During discovery we review what your system supports, agree what the app needs to read or write, and design around any limits before development begins.
Similar Work
Related Projects
Case studies built with the same technologies or for similar needs.
