Telehealth SDK:
Embed Video Visits in Your Health App
A telehealth SDK lets developers embed secure video visits, virtual waiting rooms and call handling directly inside an existing health app, instead of sending patients to a separate product. We deliver telehealth SDK modules for iOS, Android, React Native, Flutter and web, built on HIPAA-eligible video infrastructure and integrated with your authentication, scheduling and records. The module is built for your product, documented for your engineers and owned by you. This page is written for developers and technical evaluators. Request technical documentation to evaluate it properly.
Request Technical DocumentationComponents
What the Telehealth SDK Provides
The telehealth video SDK packages the hardest parts of virtual visits, the same parts our telemedicine app development services rely on, into components your team can drop into existing screens. It handles media, reconnection, device permissions, call notifications and session security, while your app keeps control of users, scheduling and clinical workflow. Because we deliver it as a service, the SDK is tailored to your stack and requirements rather than forcing a generic product. These are the core building blocks it provides. For secure chat alongside video, see our telehealth messaging SDK; for a complete virtual care product, see telehealth app development.
Video Session Component
A prebuilt, themeable video view with mute, camera switch, screen sharing and multi-party support. Your app passes a session token, and the component manages media, layout and reconnection automatically. Layouts adapt to screen size.
Waiting Room and Admission
Patients join a waiting room, run a device and network check, and wait for admission. Providers see who is waiting and admit participants, preventing uninvited access to any visit. Wait times are visible to staff.
Call Notifications
Incoming visit alerts use CallKit and VoIP push on iOS and high-priority notifications with full-screen intents on Android, so calls ring reliably even when the app is in the background.
Session Events and Webhooks
Your backend receives events such as participant joined, left or disconnected, call duration and quality metrics, supporting documentation, billing and operational monitoring without polling. Events are signed so your backend can verify their source.
Platform Support
Feature and Platform Support Table
Technical evaluators need to know exactly what works where. The table lists core capabilities and their support across platforms. Support depends on the underlying HIPAA-eligible video provider selected for your project, so we confirm the final matrix during technical discovery. Where a capability depends on platform restrictions, such as background behaviour on iOS, notes explain the limits honestly rather than promising identical behaviour everywhere. Every limitation is documented clearly upfront.
| Capability | iOS | Android | React Native | Flutter | Web |
|---|---|---|---|---|---|
| One-to-one video | ✅ | ✅ | ✅ | ✅ | ✅ |
| Multi-party (interpreter, family) | ✅ | ✅ | ✅ | ✅ | ✅ |
| Screen sharing | ✅ | ✅ | ✅ | Provider-dependent | ✅ |
| Waiting room and admission | ✅ | ✅ | ✅ | ✅ | ✅ |
| Background call notifications | ✅ CallKit + VoIP push | ✅ Full-screen intent | ✅ Native bridge | ✅ Platform channel | Browser notifications |
| Picture-in-picture | ✅ | ✅ | Native module | Platform channel | Browser-dependent |
| Network quality events | ✅ | ✅ | ✅ | ✅ | ✅ |
| Recording (optional, consent-gated) | Server-side | Server-side | Server-side | Server-side | Server-side |
Native iOS and Android
Native modules provide the deepest control over audio routing, picture-in-picture and background behaviour, and are recommended when video is central to your product experience. Native modules also deliver the best battery and performance.
Cross-Platform Wrappers
React Native and Flutter health app wrappers expose the same API surface, built on native modules. Our React Native health app development team maintains these bridges. Both wrappers are tested on real devices.
Web Support
Web components run in modern browsers using WebRTC, suitable for clinician portals and patients joining from desktops without installing an app or creating new accounts. Browser compatibility is tested thoroughly.
Provider-Dependent Features
Some features, such as screen sharing in Flutter, depend on the chosen video provider's SDK maturity. We confirm support during discovery and fill gaps with native code where practical. Limitations are documented clearly.
Integration
Integration and Authentication Model
The telehealth API SDK is designed so your backend stays in control of who joins which visit. Your server creates sessions and issues short-lived tokens, and the mobile or web client uses those tokens to join. Patient credentials and clinical data never pass through the SDK unnecessarily. The illustrative snippet below shows the shape of a typical integration; the final API is documented for your specific project and stack. Security remains under your control.
// 1. Your backend creates a visit session and returns a short-lived token
const { sessionId, token } = await api.post('/visits/123/session');
// 2. The app joins the visit with the token
const visit = await TelehealthSDK.join({ sessionId, token, role: 'patient' });
// 3. React to session events
visit.on('participantJoined', (p) => showProvider(p));
visit.on('networkQuality', (q) => updateIndicator(q));
visit.on('ended', (summary) => navigateToSummary(summary));Server-Issued Tokens
Your backend authenticates users, checks visit permissions and requests short-lived session tokens. Tokens expire quickly and are scoped to one visit and one role, limiting misuse. Tokens are never stored long term.
Role-Based Permissions
Roles such as provider, patient, interpreter and observer control who can admit participants, share screens or end visits, reflecting your clinical workflow and safety rules. Permissions are enforced on the server, not the client.
Event-Driven Integration
Client events and server webhooks report joins, disconnections, durations and quality metrics, letting your app update documentation, billing and dashboards automatically after every visit. Webhooks retry automatically when your endpoint is unavailable.
Minimal Data Exposure
The SDK handles media and session data, not clinical records. Visit metadata uses identifiers rather than names, keeping protected health information inside your own secured systems. This design keeps audit scope small.
Compliance & Pricing
Compliance Posture and Pricing Model
Developers and procurement teams both need clarity on compliance and cost. The SDK runs on HIPAA-eligible video infrastructure from providers willing to sign a BAA, with encryption, access control and audit events built in. Pricing reflects our service-based model: you pay for building and maintaining the SDK, plus video usage charged by the underlying provider. You own the integration code, with no proprietary licence restricting how you use it. Costs stay predictable.
HIPAA-Ready Infrastructure
Media is encrypted, sessions are access-controlled and events are logged. Our HIPAA-compliant app development approach documents each safeguard as evidence. Evidence is shared with your compliance team, ready for audits and customer security reviews.
BAA Chain
We use video providers that sign BAAs and confirm the full chain, including our own BAA with you, before any real patient visits run through the system. Each agreement is recorded.
Pricing Model
Costs combine a project fee for building and integrating the SDK, optional maintenance, and video minutes billed by the provider at its usage rates, giving transparent, predictable unit economics. Costs scale with real usage.
Ownership and Portability
Integration code and wrappers are yours. If you later switch video providers, the abstraction layer limits changes to the SDK internals rather than every screen in your app. Your investment stays protected.
FAQ
Frequently Asked Questions About the Telehealth SDK
These answers cover what developers and technical evaluators ask most about our telehealth SDK, including platforms, authentication, compliance, pricing and customisation. They reflect our service-based delivery model, where the SDK is built and maintained for your product. For complete API documentation, a platform support matrix for your stack or a technical call with our engineers, contact our team, and we will share materials tailored to your evaluation. Materials are tailored to your stack.
What is a telehealth SDK?
A telehealth SDK is a software development kit that lets developers add video visits, waiting rooms and call handling to their own health app. It provides prebuilt components and APIs for media, sessions and notifications, so teams avoid building real-time video infrastructure from scratch.
Which platforms does the telehealth SDK support?
The SDK supports native iOS and Android, React Native, Flutter and modern web browsers. Some advanced features, such as picture-in-picture or screen sharing on certain platforms, depend on the selected video provider and are confirmed during technical discovery for your project.
Is the telehealth video SDK HIPAA compliant?
The SDK is built on HIPAA-eligible infrastructure from providers that sign BAAs, with encryption, access control and audit events. HIPAA compliance also depends on how your organisation configures and operates the whole system, which we document and support throughout implementation.
How is the telehealth SDK priced?
Pricing combines a project fee for building and integrating the SDK, optional maintenance and video usage billed by the underlying provider. This avoids per-seat licensing and keeps costs tied to actual visit volume, with full code ownership for your organisation.
Can we customise the video interface?
Yes. Components are themeable, and teams can build fully custom layouts using lower-level APIs. Branding, controls, layouts and accessibility settings can match your app's design system, while the SDK continues to handle media, reconnection and session security underneath. Accessibility is tested too.
Get Started
Book your strategy session
Free architecture review. Expert HIPAA compliance advice. No hard sell — just an honest conversation about your project.