Midvisit
Care programmes and workflows

One pathway. Consistent conversations.

Programmes connect patient groups, protocols, conversation workflows and voice-agent assignments.

Book a demo ↗
Configuration

Purpose → clinical logic → conversation → agent.

Programme

Defines target conditions, call frequency and links to protocols. Facility staff assign patients to programmes.

Care-team role: Agree the patient group and clinical purpose.

Protocol

Sets the questions, signals and clinical rules that guide the check-in.

Care-team role: Approve the clinical content; editing permissions depend on authorised roles.

Workflow

Structures conversation steps and connects the programme to a voice agent.

Care-team role: Review the patient-facing conversation and boundaries.

Agent

Provides the configured voice and workflow assignment. Mira is the patient-facing Midvisit agent brand.

Care-team role: Choose the appropriate configured language and workflow.

Supported pathways

A starting point for clinic-specific configuration.

Inside Midvisit

A closer look.

Care programme library
Care programme library · Illustrative data
From a programme to a patient

Configure the pathway, then assign it.

Define the purpose

Choose a supported patient group and the information the check-in should collect.

Care-team role: Agree clinical suitability and the purpose of follow-up.

Connect the configuration

Programmes link protocols, conversation workflows and agents. These define the structured check-in and its schedule.

Care-team role: Authorised configuration users maintain the pathway. clinician editing access can be granted; it is not provided by default.

Assign and review

Patient enrolment connects the selected programme to the patient record and subsequent call history.

Care-team role: Confirm consent, assignments and review responsibilities before activating the agreed workflow.

Configuration and evidence

Availability is not clinical validation.

The programme library includes post-op recovery, COPD, hypertension and diabetes programmes. Clinics can create their own. Explore post-procedure check-in and type 2 diabetes check-ins.

Full question banks, prompts, scoring formulas and detailed protocol logic remain private.

Programme library

Start with a programme. Configure your own.

The programme library includes post-op recovery, COPD, hypertension and diabetes programmes. Clinics can create their own programmes and approve the questions, call schedule and alert thresholds for their pathway.

Questions answered

Before you start.

Are full protocols public?

No. Question banks, prompts, scoring formulas and detailed protocol logic are kept private.

Are programmes clinically validated?

Product availability does not establish clinical validation. No validation or outcome claim is made without separate evidence.

Does Midvisit make clinical decisions?

Midvisit captures patient-reported information and prepares it for care-team review. Diagnosis, prescribing and treatment decisions remain with authorised professionals.

How do we start?

Start with one agreed pathway. Discuss the patient group, consent, configuration and review ownership in the demo. Pilot price, duration and implementation commitments are agreed separately.

Can a clinician configure a protocol?

Yes, when authorised configuration access is granted. clinicians are not given this access by default.

Can we inspect the pathway in a demo?

A demo can show how programme assignment, workflow configuration and call records connect, without publishing private protocol logic.

Start with one pathway

Make the next conversation a product demo.

Bring your patient group and follow-up task. Explore the workflow, responsibilities and fit with your care team.

Book a demo ↗