The main workflow, step by step
A single remote consultation is shown below, from the patient's booking to the follow-up. Open any step to see its screen. The provider, the clinician and the patient are invented, and nothing here is medical advice.
Before your visit
VIS-73402Ready| Item | State |
|---|---|
| Identity check | Completed |
| Reason for visit | Described by patient |
| Consent to remote care | Given and recorded |
| Camera and microphone | Tested |
Off the pathA patient who reports symptoms on the provider's urgent list is shown emergency guidance instead of a booking.
Waiting room
VIS-73402Clinician running late- Position
- Next to be seen
- Clinician
- General practitioner
- While waiting
- Connection quality shown
- Updates
- Sent if the delay grows
Off the pathIf the patient's connection is too weak for video, an audio visit is offered before the consultation begins.
Consultation
VIS-73402In call| Panel | Shows |
|---|---|
| Video | Patient, with captions option |
| Intake | Reason and answers |
| History | From the records system |
| Notes | Structured visit note |
Off the pathWhen the call drops, both sides rejoin the same visit. After repeated failures the clinician can switch to a phone call.
Visit outcome
VIS-73402Completed- Summary
- Written for the patient
- Prescription
- Sent through the approved route
- Follow-up
- In-person review advised
- Record
- Filed in the records system
Off the pathA case that needs a physical examination is marked for in-person care and the patient is helped to book it.
Follow-up list
This weekTwo need action| Patient | Task | State |
|---|---|---|
| Patient one | In-person review | Not yet booked |
| Patient two | Check-in message | Sent, awaiting reply |
| Patient three | Results discussion | Booked |
Off the pathA patient who does not respond to a follow-up is escalated to a call, according to the provider's own protocol.
Who uses it, and what each role can do
Remote care is a regulated service, and the roles are defined as much by what each person must not see as by what they do.
| Role | Sees | Can do |
|---|---|---|
| Patient | Their visits, summaries, messages and documents | Book, complete intake, join visits and reply |
| Clinician | Their schedule and the records of patients they treat | Consult, document, prescribe through approved routes and refer |
| Care coordinator | Waiting rooms and follow-up tasks | Help patients connect, reschedule and chase follow-up |
| Practice manager | Schedules, visit volumes and service quality | Configure services, hours and clinician availability |
| Administrator | Users, roles and the audit record | Grant access and review who viewed which record |
When the work leaves the usual path
The difference between a demo and a service patients can rely on is the handling of failure. Each of these has a defined path.
| Situation | What the system does | Who decides |
|---|---|---|
| Urgent symptoms at intake | Shows emergency guidance and stops the booking | The provider's protocol |
| Connection too weak for video | Offers audio, then a phone call | Clinician |
| Call drops mid-visit | Lets both sides rejoin the same visit | No one, it is automatic |
| Patient does not attend | Records it and applies the provider's policy | Care coordinator |
| Needs a physical examination | Marks the visit for in-person care | Clinician |
| Patient outside the licensed area | Blocks the visit according to your rules | Practice manager |
What it connects to
A telemedicine product is a set of joined services. Which ones are permitted, and under what agreements, depends on your jurisdiction and is confirmed with your advisers.
| System | What moves | Direction |
|---|---|---|
| Video service | Encrypted audio and video sessions | Both ways |
| Health records system | Patient history in, visit notes and summaries out | Both ways |
| Prescribing service | Prescriptions through the route approved where you practise | Out of the app |
| Payments or insurance | Fees, co-payments or eligibility | Both ways |
| Messaging | Reminders and follow-up by channels patients accepted | Out of the app |
| Identity verification | Checks of patient identity where required | Into the app |
What a first release includes
Booking and intake
Visit types, clinician availability, reason for visit, questionnaires and recorded consent before the call.
Virtual waiting room
A device check, a place in the queue and updates, with a coordinator able to help a patient connect.
Video consultation
The call with the intake and history beside it, structured notes and a fallback to audio or phone.
Visit outcome
A summary for the patient, follow-up tasks and the record written back to your records system.
Patient apps
Apps for iOS and Android and a web version, with sign-in suited to sensitive data.
Audit and access control
Role-based access, an audit record of every view and change, and settings for data retention.
Often added after the first release
- Group visits and family members joining
- Remote monitoring devices
- Asynchronous visits by message and photo
- Interpreter on the call
- Clinician rota and on-call cover
What we need from you
- Your clinical model: which visits are offered remotely and by whom
- The legal and licensing rules for remote care where you practise, from your advisers
- The health records system you use and what it lets us connect
- Your protocols for urgent symptoms and for failed visits
- Clinicians and a coordinator who will test with realistic cases
Ownership and licensing terms are defined in the project agreement.
What to do next
Tell us which services you want to offer remotely and in which countries or states. We respond with the product outline, the questions for your compliance adviser and a proposal. Start a conversation or book a 30-minute call.
Common questions
Do you build the video technology yourselves?
No, and you would not want us to. We use an established video service designed for healthcare use and build the product around it: booking, intake, the waiting room, the clinician's workspace, records and follow-up. That is where your service differs from others. The video provider is chosen with you, including the data processing terms your jurisdiction requires.
Does the application meet health data regulations?
Compliance belongs to the service you operate, not to software alone, so we do not label a product as compliant. We build the technical measures regulations usually call for, including encryption, access control, audit records and data location choices, and we work to the requirements your legal and compliance advisers define for each market you enter.
Can it connect to our electronic health record?
Often, depending on the record system and what its vendor allows. Many expose interfaces based on healthcare data standards for patients, appointments and documents. We confirm what is available early, because it decides whether clinicians see history inside the consultation and whether notes are filed automatically or exported. Where no interface exists, we design the least painful manual step.
Should we start with a white-label platform instead?
It is a reasonable way to test demand. White-label telemedicine platforms get a basic service running quickly. Providers move to their own product when the visit flow has to match their clinical model, when they need integration the platform lacks, or when the per-visit fees outgrow the cost of building. We can help you judge when that point has arrived.