ADDITIONAL PARTICIPANTS
Use supported group calling in the telehealth video API to include an authorized participant. Your application manages consent, participant eligibility and access to information, while the appropriate Call plan connects the additional users.
CALL STATUS EVENTS
Connect telehealth video API call events to the next step in your application’s care workflow. Your system manages follow-up instructions, records and appointment status, with its own checks before treating a call as a completed visit.
MADE FOR YOUR USERS
Use a live conversation at a clearly defined point in your healthcare application.
Scheduled visits
A patient and provider start a conversation from the scheduled visit in your application. The healthcare service controls appointment eligibility, identity checks and access.
Follow-up conversations
A provider connects with a patient for an approved follow-up conversation. Your healthcare application manages the instructions, records and the need for further care.
Caregiver participation
A patient chooses to include a caregiver where the service permits it. Your application captures the necessary consent and authorizes the additional participant.
Interpreter participation
Your service invites an authorized interpreter to join the patient and provider. Interpreter availability, consent and access are managed by the healthcare application.
RELATED CUSTOMER STORY
GE HealthCare’s published Tencent RTC solution connects medical imaging operators with remote doctors through video and screen sharing, supported by messaging and whiteboarding.
Related healthcare case: specialist collaboration demonstrates remote clinical communication. This broader solution is separate from a patient-visit workflow or a specific Call SDK deployment.
CHOOSE WITH CONFIDENCE
Explore the Call capabilities and the application connections your experience needs.
| Your requirement | How it is delivered | What to plan for |
|---|---|---|
| Patient-provider conversations | One-to-one audio and video calling | Your healthcare application manages identity, appointment access and the care workflow. |
| Personal media controls | Camera, microphone and end-call controls | Test permissions, accessibility and failure recovery on the devices you intend to support. |
| Caregiver or interpreter participation | Supported group call invitations | Use the appropriate plan, consent flow and participant authorization; the current limit is nine. |
| Care records and follow-up | Application integration through call events | Clinical records, prescriptions, diagnosis, emergency response and visit completion remain with your service. |
| Healthcare requirements | Review of the exact services and configuration | Evaluate data handling, retention, regional requirements and contracts before production use; no universal compliance claim is made here. |
THREE STEPS TO YOUR FIRST CALL
Connect your users to the telehealth video API, then test outgoing calls, incoming invitations, and media controls.
BUDGET BEFORE YOU BUILD
Budget for your telehealth video API integration. Choose the calling features you need, then estimate the people and minutes using them.
CALL FREE TRIAL
Try Call with the feature trial and 100 MAU. Monthly free minutes and the feature trial have separate eligibility and deduction rules.
CALL STARTER PLAN
Group Call features, 50,000 package minutes and 1,000 MAU. Review Starter eligibility before purchase; the discount covers the first month.
YOUR APPLICATION
Discuss your platforms, expected usage and feature requirements. Get help with licensing, optional services and a plan for your launch.
This page describes adding live calling to an existing healthcare application. Patient identity, appointments, consent, clinical records, prescriptions, billing and care delivery remain with your service. The calling integration must fit the workflow and requirements of the organization using it.
Review the exact Tencent RTC services, configuration, data handling and available contractual terms with the appropriate teams before handling regulated healthcare information. Confirm any HIPAA-related requirements, BAA availability and encryption requirements for your intended deployment; video calling alone does not establish these commitments.
Supported group calling can connect an additional participant when your application authorizes them. The current Group Call plan supports up to nine people. Your healthcare workflow must manage consent, roles and information access; Call does not supply interpreter staffing or care permissions.
Test denied device permissions, unavailable participants, timeouts and network changes across your supported devices. Your healthcare application needs an appropriate recovery and follow-up process. A calling failure should not automatically mark an appointment complete or act as an emergency-care decision.
Do not assume recording is active. Cloud recording requires separate configuration and has additional usage charges. Before enabling it, define the applicable consent, data access, retention and storage requirements for the exact service configuration and healthcare workflow.
Your healthcare application verifies the appointment, participant identity and consent. Integrate the supported calling flow and separately review privacy, retention and contractual requirements.
Compliance depends on your complete application, contracts and handling of patient data. Review the actual service terms and your required safeguards; SDK integration alone does not establish compliance.
