Skip to content
Rinovis AI logoRinovis AI
Case Study: CareLattice AI

Healthcare Voice Agent for Patient Access

A controlled voice automation platform for appointment scheduling, administrative support, and intelligent patient routing.

Product
CareLattice AI
Industry
Healthcare Operations
Platform
Voice AI & Console
Project Type
Solution Blueprint
Data Env
Synthetic Patient Data
Primary Use Case
Patient Access Ops
Development Services
Voice AI, RAG, FastAPI
CareLattice AI Voice Access Console Screenshot

About the Project

CareLattice AI is a healthcare voice platform designed to help clinics manage routine patient-access calls through a controlled conversational workflow.

The platform focuses on appointment booking, rescheduling, cancellations, clinic information, and administrative routing. It is intentionally restricted from providing diagnoses, treatment recommendations, medication advice, or autonomous clinical decisions.

Instead of allowing a language model to make unrestricted decisions, CareLattice separates conversation from operational actions. The voice agent understands the caller’s request, while authenticated backend tools handle appointment searches and scheduling changes.

Requests involving symptoms, urgent concerns, medical decisions, or unsupported situations are transferred to clinic staff with a structured summary of the conversation and actions already attempted.

The Problem & Objectives

Healthcare front-desk teams regularly handle repetitive calls about appointment availability, cancellations, clinic locations, preparation instructions, and department routing.

These requests are individually simple but collectively time-consuming. Traditional telephone menus also create friction because patients must navigate fixed options that may not match how they naturally explain their needs.

Introducing a conversational AI agent creates a different set of challenges. The system must understand natural speech while preventing inaccurate scheduling actions, unsupported medical answers, lost patient context, and unsafe automation. The objective was therefore to design a system that could handle routine administrative requests without removing human oversight from clinical or exceptional situations.

Identified Challenges

  • [1]

    Natural Conversations with Controlled Actions

    Understanding diverse, natural patient vocabulary while forcing all system changes to obey clinic safety rules.

  • [2]

    Real-Time Appointment Availability

    Retrieving dynamic booking slots live from scheduling databases without race conditions during active phone calls.

  • [3]

    Administrative & Clinical Boundaries

    Automating appointments but immediately catching and transferring questions about symptoms, medications, or urgency.

  • [4]

    Patient Verification Gates

    Securing patient records by completing identity verification steps before revealing dates or updating bookings.

  • [5]

    Reliable Human Escalation Handouts

    Passing callers to staff with transcripts, risk ratings, and actions already attempted so the patient never repeats themselves.

  • [6]

    Operational Visibility

    Displaying complete logs of completed calls, successful bookings, escalations, and model retrieval quality.

How the Solution Was Designed

CareLattice uses a layered architecture that separates voice communication, language understanding, knowledge retrieval, and transactional actions.

The voice layer manages live audio streaming and conversational turn-taking. An orchestration service identifies the patient’s intent and selects an approved workflow.

Administrative questions are answered through retrieval-augmented generation using approved clinic information. The agent cannot answer from general model knowledge when responding to clinic-specific questions.

Appointment searches, bookings, cancellations, and rescheduling actions are completed through authenticated backend tools. Before changing an appointment, the agent repeats the provider, location, date, and time and requests explicit confirmation.

Clinical questions, urgent language, repeated misunderstandings, and failed integrations activate the human escalation workflow.

System Deliverables

Key Features Built into CareLattice

Operational blocks designed to guarantee secure patient routing, grounded information lookup, and context transfer.

Two-way Voice Interaction

Patients speak naturally to request help, bypassing rigid telephone menu dial pads completely.

Appointment Management Tools

Searches availability, queues new bookings, reschedules appointments, and handles cancellations via secure APIs.

Approved Knowledge RAG

Grounds administrative answers in approved clinic files. The model cannot reply using default web knowledge.

Caller Identity Verification

Implements secure verification checks before modifying bookings or sharing personal schedule information.

Explicit Confirmation Gates

Repeats provider, date, time, and location to request voice confirmation before executing write changes.

Safety-Based Escalations

Detects clinical terms, symptoms, or emergencies and automatically initiates a high-priority handoff.

Context-Preserving Handoffs

Transfers the audio call alongside caller status, conversation summary, and attempted actions to the staff console.

Structured Call Summarization

Saves a detailed call log showing the outcome, booked appointments, and immediate follow-ups required.

Operations Console

Displays live audio streams, current wait times, model answer accuracy, and historical call analytics.

How It Works

Conversation & Safety Flow

What happens between a patient speaking and a call resolving, step by step.

1

Caller speaks naturally

The patient describes what they need in their own words, no menu navigation.

2

Intent & identity check

The agent identifies the request type and verifies the caller before touching any record.

3

Approved-info RAG or appointment tool

Administrative questions are answered from approved clinic documents; scheduling changes go through authenticated booking tools.

4

Confirmation repeat-back

Before any write action, the agent repeats provider, location, date, and time and waits for explicit confirmation.

5

Clinical / urgent escalation gate

Symptoms, urgent language, or repeated misunderstandings trigger an immediate handoff.

6

Staff handoff with context

Clinic staff receive the caller with a transcript and summary of what was already attempted.

System Stack

Technology Infrastructure

The libraries, servers, and database tools powering the CareLattice AI pipeline.

Voice & Conversation

Twilio Voice APIWebSocket Audio StreamingStreaming Speech-to-Text (STT)Low-Latency Text-to-Speech (TTS)Claude / OpenAI Models

Backend Engineering

PythonFastAPIPydanticAsynchronous OrchestrationREST / WebSocket APIs

Knowledge Retrieval (RAG)

Approved Clinic Document IngestionEmbedding ModelsPostgreSQL with pgvectorSource-Level Citation Engine

Data & Infrastructure

PostgreSQLRedis CacheDocker ContainersAWS ECS / EC2Structured Application Logs

Simulation & Handoffs

FHIR-Compatible Scheduling SimulatorPatient-Access Mock DatabaseSMS/Email Notification EnginesCall-Transfer Queue
Solutions Engineering

Need a secure AI solution built for your operations?

Discuss your workflow constraints, system integrations, and safety boundaries with our engineering team.