PATIENT ACCESS
Keep the patient journey moving.
Explore how scheduling, reminders and follow-up can stay connected across voice, messaging and hospital systems.
Patient access / CONNECTED JOURNEY
One appointment. Every next step.
ONE CASE CONTEXTVM-1024Permission / state / history
Normal path Exception to a personIllustrative · select a node to inspect
MayaPatient access agentSample conversation · VM-1024
CONVERSATION / STEP 1
HIS / EMRSample action
Capture appointment contextRequest retained for scheduling
No live calls or system writes
Clinical concerns go to authorized staff with context.
Explore healthcareFictional conversations and records · illustrative workflow · confirm supported systems and language coverage.
INSIDE THE EXECUTION
Inspect the workflow.
Start with administrative patient access. Clinical follow-up requires approved scripts, permitted record access and staff escalation.
Workflow explorer
Interactive illustration · sample data Voice conversation
Healthcare agentSample case VM-1024
I need to move my appointment to Friday.
I can help with the scheduling request. Morning or afternoon?
Fictional case · no real calls or data
ONE CONNECTED WORKFLOW 01 / 06
Request received
CONVERSATION & CHANNELS
SYSTEMS & PEOPLE
Appointment requestCapture the request and retain the appointment context.
Shared state Connected actions Human control
The complete journey
01
Appointment request
02
Check available slots
03
Confirm on WhatsApp
04
Update scheduling
05
Staff hand-off if needed
06
Review the outcome
Systems in this story
HIS / schedulingEMR / FHIRCalendarsStaff task queue
Integration categories describe the workflow. Confirm named systems, permitted actions and deployment compatibility with our team.
START WITH ONE WORKFLOW
Bring your SOP. Let’s map the first process.
Define the task, connect the systems and agree what a useful pilot should prove.