Learners need safe chances to practice difficult conversations, like delivering bad news, calming an angry family member or taking a full history, before having them with real patients. A patient simulator stands in for a real patient, whether a manikin, an actor, software or AI, so learners practice assessment, conversation and clinical judgment where mistakes cost nothing. The newest form of nursing simulation adds an on-demand simulated patient that holds the same history and behaves the same way for every learner, every time.

Standardized patient (SP) programs offer live practice, but SPs are contractors who work sporadic hours and often split time across several schools. An AI patient simulator adds practice volume without adding actors. A learner opens a browser link, talks with a simulated patient who answers in real time, and the case stays as faculty wrote it.

What is a patient simulator?

A patient simulator lets a learner rehearse the parts of care that carry risk (assessment, communication, clinical judgment) before doing them with a real person. Prelicensure nursing programs, medical schools, physician assistant programs, residencies and continuing medical education (CME) providers all use them. State nursing boards decide how much simulation counts as clinical time.

The tools behind that practice vary widely. The Society for Simulation in Healthcare (SSH) Healthcare Simulation Dictionary lists standardized patients, manikins, partial task trainers, avatars and computer-based and virtual reality formats as simulation tools. It also states that fidelity “is not constrained to a certain type of simulation modality, and higher levels of fidelity are not required for a simulation to be successful.”

One newer option, the AI patient, differs from an actor-played SP in who generates the patient’s words. The Association of Standardized Patient Educators (ASPE) defines an SP as “a person trained to portray a patient in realistic and repeatable ways.” In an AI patient, a large language model (LLM) generates each reply inside a case faculty write, so no actor needs booking, but a physical exam is not possible.

Types of patient simulators

Clinical simulation uses three patient simulator formats, namely physical manikins, virtual patients on a screen or in virtual reality (VR), and AI conversational patients. SSH classifies simulators as low, medium or high fidelity by how closely they resemble reality, and each format can sit anywhere on that scale.

Physical manikins

Manikins carry procedural and physiological practice (CPR, airway management, medication administration and a patient who deteriorates on cue), but cannot independently hold a conversation that reacts to the learner. A high-fidelity programmable manikin has an upfront base cost of $65,000–$85,000 for a critically ill patient, excluding the bed and monitors. Running one also takes a simulation technician to program it, operate it during scenarios and repair it afterward.

Screen-based and VR virtual patients

In screen-based virtual patient simulation, branching case scripts run on a computer, and VR versions place the learner inside an immersive encounter through a headset. A review of 51 trials with nearly 4,700 participants by the Digital Health Education Collaboration found virtual patients improved skills more than traditional teaching and knowledge about as well.

Branching scripts limit conversation practice, and a qualitative study concluded one virtual patient platform did not meet students’ needs for practicing challenging communication. VR adds hardware and comfort problems, since a systematic review in Virtual Reality reports that 60–95% of participants experience some cybersickness.

AI conversational patients

An AI conversational patient uses conversational AI in healthcare to answer whatever the learner says, out loud, in character. Faculty define a persona (history, symptoms, personality, what the patient will and will not reveal), and an LLM generates each reply inside those limits. The format turns the patient simulator from a decision tree into an open conversation.

Because the learner speaks freely, each encounter unfolds differently. A learner taking a history can ask an open question, press on a vague answer or change approach when the patient hesitates, and the patient answers in character each time. Every learner starts from the same case, so faculty can compare practice across a cohort.

Why face-to-face helps

Text and voice chat can support virtual patient encounters, and voice carries pacing and tone, but both drop the facial cues a learner reads face to face. Patients seem to value those cues, since in one telehealth study they said communication worked better over video than audio-only, citing facial cues. A JMIR scoping review of LLM-based virtual patients also names the absence of nonverbal cues as a limit on implementation.

Face-to-face AI patients add that missing channel. A Personified Application Layer (PAL) is a real-time application you talk to face to face, which sees, hears, remembers and responds. Tavus, a human computing company, builds PAL patients for encounters in which the PAL plays the patient and perceives the learner’s tone and expression as it talks.

AI patients vs standardized patients

AI patients, standardized patients and manikins solve different problems, so most programs need more than one.

  AI patient simulator Standardized patient High-fidelity manikin
Reported cost Request per-encounter pricing $38.08 per student in one pharmacy SP assessment No per-encounter figure, $65,000–$85,000 upfront plus maintenance and an operator
Scalability Confirm concurrent-session limits Capped by pool size; many SPs work for several programs One scenario per manikin and operator at a time
Scheduling Browser link, any hour Sporadic contractor hours, often weekday business hours Lab booking plus technician time
Consistency Same case each run; LLM output can drift Trained for repeatable portrayal over 2–12 hours per case; fatigue after long sessions Programmed physiology can be repeated
Realism Real-time face, voice and expression; no physical exam Physical exam possible; arguably higher in physical fidelity than a full-bodied patient simulator Physiology and procedures; scripted or operator-voiced talk
Assessment use Transcripts, recordings, completion criteria; AI scores need validation before grading OSCEs and high-stakes exams; SP completes learner checklists Procedural and team performance with debrief
Best for Repeated history taking and difficult conversations High-stakes assessment and physical exam Procedures, deterioration and crisis teams

Programs can only train as many learners as their clinical practice allows. The American Association of Colleges of Nursing (AACN) names insufficient clinical placement sites among the primary barriers to accepting every qualified student. Its enrollment survey counts 93,176 qualified applications turned away at US nursing schools in 2025.

AI patients add practice that does not depend on a placement site. They work best as a complement, absorbing routine repetition so SP hours go to high-stakes assessment. Learners can also repeat a face-to-face conversation with a patient who reacts to how they speak as many times as they need.

How AI patient simulation works

An AI patient simulator needs a case that defines the patient, a language model that replies in character, and an interface that makes the exchange feel like a conversation.

Tavus’s Conversational Video Interface (CVI) shows what this looks like in practice. One API call opens a real-time video room (WebRTC) with the PAL patient, and nothing is pre-rendered because the face, voice and words are produced live during the conversation.

Building the case

A good case works like an SP case sheet. It sets the patient’s history, emotional state and personality, what the patient should reveal or hold back, and what counts as a successful encounter. The patient also needs the program’s protocols and facts, so answers come from the case and not from the model’s general knowledge. Tavus lets faculty set these through five settings.

  • System prompt: Sets the history, emotional state and personality, such as an anxious 74-year-old with heart failure who distrusts water pills.
  • Objectives: Define what counts as success, such as confirming the patient can state when to call the clinic.
  • Guardrails: Set what the patient must not do, such as volunteering a diagnosis or giving clinical advice.
  • Knowledge Base: Holds the program’s protocols and case documents, so a question about home medications is answered from the uploaded medication list.
  • Memories: Keep a profile and timeline for each learner, so a follow-up visit can pick up where the first one ended.

Faculty without engineering support can build in PAL Maker, the no-code builder, and choose from 100+ Stock Faces or create one in AI Face Studio. Each case becomes a PAL that faculty can reuse with every cohort, so a program can build a library of simulated patient encounters over time.

How the patient responds

A convincing patient has to register how the learner speaks, take turns the way a person does and show reactions on its face. In Tavus’s closed loop, Sparrow-2 manages timing, Raven-2 interprets the learner’s signals, the LLM layer decides what the patient says next, and Phoenix-4.5 renders the response.

  • Raven-2: A multimodal perception system that fuses tone, prosody, expression, posture and gaze into one interpretation of the learner, such as a steady voice paired with a tense face. Its rolling perception keeps context no more than 300ms stale.
  • Sparrow-2: A turn-taking model that predicts who holds the conversational floor rather than waiting for silence, so a pause to check a chart passes without the patient jumping in. It ranks #1 on Sesame’s TurnBench in preliminary results on the public dev split.
  • Phoenix-4.5: A real-time human rendering model that renders the PAL’s face, head and upper body in under 130 milliseconds.

The LLM layer runs on Tavus’s latency-tuned models, or you can bring your own LLM through an OpenAI-compatible endpoint. Learners join from a browser link with no headset, which removes the hardware and cybersickness problems VR carries.

Skills, feedback and debrief

AI patients fit skills that are practiced through conversation and assessed through what the learner says and does. Typical uses include:

  • History taking across body systems
  • Clinical judgment in cases such as heart failure, stroke and childbirth
  • Medication administration and patient teaching
  • Breaking bad news, often with the SPIKES protocol
  • Informed consent conversations
  • De-escalating angry or upset family members
  • Encounters with language barriers

Feedback in simulation works best when the learner gets a record of the encounter and a structured conversation about it. The record shows what was said and when, so faculty can give formative feedback before any graded attempt. The debrief then turns that record into learning, and the International Nursing Association for Clinical Simulation and Learning (INACSL) requires a planned debrief for every simulation.

Programs commonly use a structured framework such as PEARLS or Debriefing with Good Judgment. Validated rubrics such as the Lasater Clinical Judgment Rubric, which rates 11 dimensions on four levels, are a common way to score performance.

Tavus shows how an AI patient can supply that record. After each session, faculty get a transcript with speaker roles and per-turn timing, recordings in the program’s own cloud storage, and perception analysis from Raven-2. Objectives show whether each completion criterion was met, so the debrief can start from the record.

Evidence and limitations

Early research on AI patients is encouraging but limited. In a JMIR Medical Education trial, learners who practiced with an AI patient improved their communication more than learners who studied reading modules. In an npj Digital Medicine trial, trainees scored higher on a history-taking assessment.

Most studies are small and short, and a 2026 systematic review found only 6 of 15 had a control group. A meta-analysis of 27 studies found virtual simulation worked about as well as mannequins or real persons, though results specific to nursing remain thin. The research also points to four weak spots:

  • Made-up details: AI patients can invent facts, and a review of 39 studies reported rates of 0.31% to 5%.
  • Drifting out of character: Over a long conversation, an AI patient can contradict itself or slip out of its role.
  • Too agreeable: Many AI patients cooperate more than real ones, which makes cases easier than real life, as an MDPI review notes.
  • Unreliable scores: In a physical therapy pilot, AI-generated scores clustered near the top, so check them against trained human raters before grading.

Faculty review of each case, a short test with a few learners and faculty-led grading handle most of these risks. In Tavus, the Knowledge Base ties answers to your documents, and Guardrails report off-case behavior.

Choosing a patient simulator

A patient simulator earns its place when it fits the curriculum, the assessment plan and the data rules a program already works under. Start with the two checks faculty can run themselves.

Check whether the tool covers your specialties, difficult conversations and languages, and whether faculty can edit history, emotional state and disclosure rules without engineering help. Ask for a sample case in your weakest clinical area. Then confirm what faculty receive after each session, including transcripts, recordings and completion criteria, and treat any AI-generated score as formative until it is checked against your raters.

Five more questions involve curriculum rules, other campus offices and compliance.

  • Curriculum and clinical hours: NCLEX case studies measure six clinical judgment steps, so map cases to them and to your own competencies. Your state board also decides how much simulation counts as clinical time, from Washington’s 1:1 ratio for screen-based simulation to New York’s one-third of clinical hours.
  • Your systems: Ask whether scores reach your learning management system (LMS) gradebook. Browser-based tools need only a webcam and microphone, while VR vendors such as UbiSim say headsets are typically bought separately.
  • Cost: Published Shadow Health and Laerdal vSim licenses for screen-based nursing simulation run about $119.99 to $149.95 per student. Ask AI patient vendors for per-learner or per-cohort pricing.
  • Student data: Learner recordings can count as education records under FERPA, so ask how the vendor handles student access and retention.
  • Compliance: If a case uses real patient material, ask counsel whether HIPAA applies. Tavus offers HIPAA compliance and a Business Associate Agreement on the Enterprise plan only, supports SOC 2 Type 2, and offers Zero Data Retention for applicable deployments.

Faculty can test cases and feedback in a single afternoon by running a sample case and reading the transcript. The systems, cost and data questions involve IT, purchasing and compliance offices, so start those conversations while the pilot runs.

Getting started in your program

Start with one case, run it with one cohort, and expand once faculty trust the transcripts. A first pilot can follow these steps:

  1. Pick one case: Choose a high-volume conversation, such as heart failure discharge teaching, and write two or three Objectives tied to clinical judgment steps.
  2. Prebrief: Share preparation materials and set ground rules, as INACSL’s prebriefing standard requires, and tell learners whether the session is formative or graded.
  3. Run sessions: Give each learner a link and a window, and allow repeat attempts.
  4. Debrief: Hold a faculty-led debrief with your chosen framework, using transcripts and perception notes as the shared record.
  5. Assess and revise: Score with your existing rubric, then fix any case facts or behaviors the transcripts show went wrong.

The pilot is working when the patient stays on the case, learners treat the session as real practice and the transcript gives faculty enough to grade fairly. If a case needs more than a few fixes after the first cohort, rewrite it before adding more cases.

A worked example

A second-year nursing student reviews discharge medications with the patient, speaks quickly, glances at the clock and asks, “Any questions before you go?” The perception model, Raven-2, registers the hurried pace and the look away, a mismatch between an open question and a closed manner. The case script says this patient withholds confusion when the nurse seems rushed, so she waits until the student finishes, her face tightening, and answers quietly, “No, I think I have got it.”

The Objective requiring a teach-back on daily weights stays incomplete, and faculty reviewing the transcript see that the student never asked. In debrief the student sees the moment, reruns the case, slows down and asks the patient to explain her routine. This time the patient admits she does not own a scale, and the Objective is met.

Next steps for your program

A nurse’s first rushed discharge, missed cue or clumsy consent conversation will happen somewhere. A patient simulator that responds to how the learner speaks lets the same mistake happen with a patient who offers a second attempt.

Faculty who would rather start on their own can follow the virtual nurse starter kit. See it for yourself. Book a demo.