A real-time telehealth application for guided movement assessments, exercise recording, pain and strength workflows, clinician collaboration, and tenant-configured session behavior.
MyMedicalHub Telemedicine is a web application created to make a real workflow clearer, faster, and easier to trust. It turns a focused product idea into something people can use, evaluate, and understand without needing to inspect the source code.
Why MyMedicalHub Telemedicine exists
Remote movement assessment requires more than a video call. Patients and providers must stay synchronized while exercises change, instructions play, recordings start and stop, pain or strength questions appear, network conditions vary, and either participant can leave unexpectedly.
The goal is not simply to add another tool. MyMedicalHub Telemedicine is designed to reduce the friction around that problem and give people a more dependable way to complete the work.
What it delivers
- Patients and providers can coordinate guided movement and exercise sessions through one real-time room experience.
- Exercise changes no longer reuse stale recordings or question state from a previous movement.
- Strength and other tenant-specific workflows can be introduced without forking the telehealth application.
- Departure, connection, and service failures resolve into clearer recovery or redirect paths instead of trapping the session.
The experience
A real-time telehealth workflow that coordinates guided exercise, movement recording, pain and strength questions, provider collaboration, and tenant-configured assessment behavior.
The project brings the important parts of the workflow into one coherent experience. Its interface and behavior are shaped around the people using it, while the implementation stays focused on predictable results and honest feedback.
What to know
Every product has boundaries. These are the most important considerations for MyMedicalHub Telemedicine:
- Camera, microphone, permissions, network quality, and WebRTC lifecycle events differ across browsers and patient devices.
- Exercise, recording, pain, strength, queue, and provider-presence state must not leak from one movement or session into the next.
- Tenant feature flags alter available assessment behavior without allowing unsupported controls to appear or execute.
- Disconnection, provider departure, stale media, and failed API responses require recoverable states that do not leave patients trapped on a loading screen.
These limitations are presented openly so visitors can understand where the project works well, what it depends on, and what may change in future versions.
Current status
Private employer-owned telehealth system used in ongoing product development. The current release demonstrates the core value of the project and the main end-to-end experience.
My role was frontend and real-time workflow engineering within the mymedicalhub team, covering webrtc sessions, media recording, exercise state, socket.io coordination, tenant features, and failure recovery. The related case study explains the decisions and delivery process in greater depth for visitors who want the engineering story behind the product.