Existing telemedicine tools only supported one-to-one calls, so physicians had no way to bring in an interpreter or a specialist when a patient needed one. We built a browser-based platform and companion provider app that support multi-party video from day one, with session state that survives a browser reload.
Talk to UsA patient-centric digital health company connecting patients to specialized care across multiple regions, plus the independent providers who serve them.
Web-based HIPAA-compliant telehealth platform built from the ground up, plus a companion native mobile app for providers.
Java (Spring Boot), AngularJS, MySQL, AWS, OpenTok (Vonage).
Delivered
The platform shipped with multi-party video built in from day one, so physicians can bring an interpreter or a specialist into a visit rather than working around a one-to-one call. Persistent video sessions survive a browser reload without dropping the call or losing queue position, a problem most telehealth builds get wrong. Independent physicians gained a way to reach patients beyond local referrals, and the build shipped on the client's timeline after scope was validated through a Design Sprint.
The client needed a platform that could serve three different user types at once and hold a video session together through the kind of interruption that ends most telehealth calls.
Existing telemedicine platforms only supported one-to-one calls, so physicians had no way to bring an interpreter or a specialist into a visit when a patient needed one.
Independent private practice physicians had no way to expand their patient base beyond the referrals they were already getting locally.
The platform had to serve healthcare organizations, independent providers, and patients at once, each with different needs built into the same product.
The core technical problem was keeping a persistent video session alive across a browser reload without dropping the call or losing the patient's place in the queue.
Built on Java and Spring Boot with AngularJS on the front end, hosted on AWS, with OpenTok (Vonage) powering the multi-party video infrastructure.
The platform lets physicians add an interpreter or a family member to a visit mid-call, rather than being locked into a one-to-one consultation. Session state is built to hold together through the kind of interruption that usually ends a telehealth call.
Patients join through the browser with no download or setup. The platform serves three distinct user types at once, healthcare organizations, independent providers, and patients, each with different needs built into the same product.
Chat, files, and session notes are all built around not retaining PHI longer than the visit itself, on infrastructure built to be HIPAA-compliant throughout.
A native mobile app pairs with the browser-based patient platform so providers can manage visits on the go. Scope for both was mapped in a Design Sprint with the client's team before development started.
Talk to us about what session management and HIPAA-compliant architecture looks like for your platform.
Partner with us to design, build, and scale digital solutions that drive better outcomes.
Global Tech Teams LLC, 525 Washington Blvd, Industrious at Newport Tower, Jersey City, NJ 07310, United States.
Let’s discuss your goals, workflows, and next steps in a focused consultation call.