Standardized-patient OSCE station: conducting a full clinical encounter through a video visit
Before a single clinical question is asked, a competent telehealth encounter requires a technology check, identity verification, and a distinct informed-consent conversation about the nature and limits of care delivered by video. Skipping this stage is one of the most common failure points in telehealth OSCE stations — students who rush into history-taking without confirming the platform is secure, the patient is who they claim to be, and the patient understands what telehealth can and cannot do, lose points regardless of how well the rest of the encounter goes.
Telehealth OSCE stations increasingly award explicit rubric points for the first two minutes of the encounter — before any history is taken. This reflects a real clinical reality: a visit conducted on an unstable connection, with the patient's face poorly lit or off-frame, or without confirming who is actually on the call, is not merely inconvenient — it is a patient-safety and confidentiality problem.
A competent setup sequence typically includes: confirming the patient can see and hear the clinician clearly and vice versa; verifying the patient's full name, date of birth, and current physical location (critical for both identity verification and emergency dispatch); asking whether the patient is in a private space and who else, if anyone, is present in the room or on the call; checking camera framing and lighting so the face — and later, relevant body areas — will be visible; and having a documented backup contact method (phone number) in case the video connection drops.
Students are frequently assessed on whether they explicitly state the backup plan out loud ("If we lose the video, I will call you at the number on file") rather than assuming the patient already knows this.
In many telehealth OSCE rubrics, confirming patient location and a fallback phone number is weighted as heavily as any single history question — because without it, a deteriorating patient cannot be found in an emergency.
Standard clinical informed consent covers the proposed evaluation and treatment. Telehealth consent adds a parallel layer specific to the modality itself, and OSCE checklists typically look for the student to address:
• Nature of the service: that this is a real medical encounter, documented in the record, not an informal chat • Limitations: that physical examination is restricted to what can be seen or self-reported, and that some conditions cannot be safely diagnosed or ruled out by video alone • Privacy and technology: what platform is being used, whether it is encrypted and compliant with relevant health-privacy regulation (e.g., HIPAA in the US), and whether the session is recorded • Emergency protocol: what the patient should do if symptoms worsen or the connection fails, including local emergency numbers, since the clinician cannot physically intervene • Right to alternative care: that the patient may request an in-person visit at any time without penalty • Billing and licensure disclosure: that the clinician is identifying which jurisdiction they are licensed and practicing in for this visit
Stations frequently penalize students who obtain consent implicitly ("Is it okay if we do a video visit?") rather than walking through these distinct elements, even briefly.
Simulated stations often deliberately inject technical friction to see how the student adapts, since real telehealth is never friction-free:
• Asymmetric bandwidth: the student's video is smooth but the patient's upload is poor, causing frozen frames precisely when visual inspection matters most • Poor lighting or backlighting: the patient is silhouetted against a bright window, making facial expression and skin findings unreadable • Off-frame patient: the patient drifts out of camera view while talking, requiring a polite redirect • Audio-video desync: lip movement and sound fall out of sync, which can be misread as the patient being confused or hesitant • Platform unfamiliarity: an older or anxious patient struggles to unmute or reposition the camera, requiring plain-language, step-by-step verbal guidance rather than technical jargon
Handling these smoothly — without becoming visibly frustrated, and without simply pushing forward and hoping for the best — is itself an assessed communication skill.
"Webside manner" is the telehealth analogue of bedside manner: the deliberate set of behavioral adaptations that let a clinician build trust, convey empathy, and read a patient's emotional state across a two-dimensional, latency-prone video link. Because so many of the subtle cues clinicians rely on in person — shared physical space, full-body posture, subtle scent and temperature cues, the ability to sit close during a difficult moment — are unavailable on video, webside manner has to be more deliberate and more explicit than in-person bedside manner, not less.
On a screen, looking at the patient's face (as displayed) and looking at the camera lens are two different directions — and only looking at the lens reads to the patient as eye contact. Looking naturally at the patient's image on-screen, which is the intuitive behavior, actually appears to the patient as the clinician looking slightly down or away.
Trained webside manner teaches clinicians to consciously toggle: use the camera lens during moments meant to convey direct connection (delivering a diagnosis, acknowledging fear or distress, asking a sensitive question), and glance at the patient's on-screen image or the chart during information-gathering. Some clinicians place a small marker or sticky note near the camera as a physical reminder during training.
This is frequently a specific checklist item in telehealth OSCE stations: examiners note whether the student appears to be looking "through" the screen at key emotional moments rather than reading notes off to the side.
A simple, teachable fix — deliberately glancing at the camera lens rather than the screen during empathic statements — is one of the highest-yield, lowest-cost interventions shown to improve patient-perceived connection in telehealth communication training.
In-person, nonverbal communication is multi-channel: posture, proximity, subtle touch (a hand on the shoulder), and ambient cues all convey empathy simultaneously. Video collapses most of this into a small rectangle of face and shoulders, so webside manner substitutes deliberate, slightly amplified verbal and visible cues:
• Audible acknowledgements ("I hear you," "that sounds really difficult") delivered more frequently than in person, since a silent nod may not register clearly on a small or laggy video feed • Slower, more clearly punctuated speech, allowing for latency and avoiding talking over the patient — video calls have a natural lag that makes interruption more jarring than in person • Visible, slightly exaggerated head nods and facial expression, since fine micro-expressions are harder to read at typical webcam resolution • Explicit narration of actions ("I'm going to type a quick note now, I'm still listening") to prevent the patient from misreading screen-glancing as disengagement • Checking in on emotional state more explicitly than usual ("How are you feeling about all this, hearing it this way?") since the clinician cannot read subtle body language shifts
The goal is not to feel performative on the inside — it is to make sure the same warmth reads clearly on the outside through a narrower channel.
Delivering difficult news or responding to visible distress is measurably harder over video, and simulated stations frequently test this deliberately (e.g., a standardized patient reacting with anxiety mid-visit).
Adapted best practice includes:
• Pausing rather than filling silence — silence reads differently on a laggy connection, and clinicians should resist the urge to talk over a pause caused by network delay • Explicitly asking if the patient wants a moment, since the clinician cannot offer a tissue or step back physically • Confirming the patient is not alone if distress is severe, and having a plan (a friend/family member nearby, a follow-up call) since the clinician cannot stay physically present • Recognizing the limits of video: some difficult conversations (a new life-limiting diagnosis, for example) may be better delivered with an in-person or hybrid plan, and part of webside manner competency is judgment about when video itself is the wrong modality
Without hands, a stethoscope, or a reflex hammer, the clinician must extend their senses through the patient's own hands and camera. This stage tests the core telehealth-specific skill of directing a patient — often anxious, untrained, and holding a shaking phone — through a structured self-examination and camera-guided inspection, while still gathering a complete and reliable history.
Because physical examination is degraded, telehealth history-taking has to be proportionally more thorough and more precisely targeted. Experienced telehealth clinicians front-load questions that would otherwise be quickly answered by a hands-on exam:
• Explicit symptom mapping: asking the patient to point to and describe the exact location, quality, radiation, and timing of a symptom in more detail than a typical in-person history, since the clinician cannot palpate to confirm • Functional questions as exam substitutes: "Can you take a deep breath and tell me if it hurts?" or "Can you walk to your kitchen and back and tell me how that felt?" turn the patient's own body into the instrument • Serial self-report: asking the patient to track and report a measurement (temperature, pain score, a home blood-pressure reading) rather than relying on a single in-visit vital sign • Explicit closed-loop confirmation: repeating back what the patient described to reduce the risk of misinterpreting a description that substitutes for direct observation
This is a shift in cognitive weighting, not just extra questions: history becomes the primary diagnostic instrument, with visual exam as a supporting, imperfect adjunct.
When a visual or "hands-on" component is needed, the clinician must direct it entirely through spoken instruction, which is itself a skill:
• Framing and lighting first: "Can you move so the window light is on your face, not behind you?" before asking the patient to show anything • One instruction at a time: breaking a maneuver into small, sequential, plain-language steps ("Lift your shirt just on that side... now point the camera there... a little closer... hold still") rather than a single complex instruction • Guided self-palpation: for example, walking a patient through gently pressing on their own abdomen in each quadrant while watching their face for a wince, or guiding a caregiver to check a child's neck for stiffness — accepting that this reports subjective sensation and visible reaction, not the clinician's own tactile findings • Comparative framing: asking the patient to show the unaffected side first for comparison, since the clinician has no baseline exam to compare against • Explicit uncertainty statements: after a remote visual check, stating clearly what could and could not be assessed ("I can see the redness but I can't tell how warm or tender it is without touching it — can you press on it and tell me?")
OSCE stations commonly grade whether students narrate these limitations honestly rather than implying a remote look is equivalent to a hands-on exam.
A remote visual inspection is not a physical exam — it is a substitute with known, specific gaps (no palpation, no auscultation, no reliable measurement of temperature or turgor). Competent telehealth practice means stating that gap out loud, not papering over it.
Increasingly, telehealth visits are supplemented by patient-owned or clinic-distributed peripheral devices and by a second person physically present with the patient:
• Home devices: pulse oximeters, blood pressure cuffs, digital thermometers, and connected otoscopes/stethoscopes can transmit objective data, though device calibration and correct patient technique must be verified • Caregiver-assisted exam: a parent, partner, or home health aide physically present can perform simple guided maneuvers (checking capillary refill, palpating a joint) under verbal direction — effectively acting as the clinician's remote hands • Store-and-forward adjuncts: photos or short videos of a rash, wound, or gait submitted before or after the live visit can supplement real-time video, especially where bandwidth is limited
Each of these expands what remote data collection can achieve, but each also introduces a new source of measurement error that the clinician must explicitly account for when weighing the reliability of the finding.
The defining cognitive skill of telehealth practice is not making a diagnosis despite missing data — it is knowing, explicitly and in real time, which pieces of missing data actually change the differential enough to require escalation. This stage of the OSCE tests whether a student can reason transparently about uncertainty and recognize the specific red flags that mean the visit must convert to in-person, urgent, or emergency care.
A hallmark of strong telehealth performance — and a specific OSCE rubric item — is the student verbalizing their diagnostic reasoning in terms of what remote data can and cannot rule in or out, rather than presenting a confident diagnosis as if the exam were complete.
This typically sounds like: naming the leading differential; naming what in-person findings would normally help distinguish between the top two or three possibilities (e.g., "Normally I'd listen to your lungs and check your oxygen level directly, but from what you're describing and what I can see, here's my current thinking..."); and stating explicitly what would change the plan (e.g., "If your fever goes above X or you feel more short of breath, that changes things significantly").
Examiners are trained to distinguish between a student who reaches a reasonable working diagnosis while flagging its remote limitations, versus one who reaches the same diagnosis but implies unwarranted certainty — the latter is scored as a patient-safety concern even if the final diagnosis happens to be correct.
Telehealth triage frameworks generally organize red flags by system, but common cross-cutting categories tested in simulation include:
• Airway/breathing: any visible respiratory distress, inability to speak in full sentences, stridor, or reported oxygen saturation below a defined threshold — video cannot substitute for direct auscultation or pulse oximetry in a deteriorating patient • Circulatory/neurologic: chest pain with concerning features, sudden severe headache, new focal weakness or facial droop, altered mental status — these require in-person neurological and cardiovascular exam and often emergency transport • Abdominal: severe or rapidly worsening pain, guarding that cannot be reliably assessed by patient self-palpation, signs suggestive of an acute abdomen • Pediatric-specific: lethargy, poor feeding, dehydration signs in infants, since young children cannot reliably self-report and remote assessment of hydration status is especially unreliable • Mental health/safety: active suicidal or homicidal ideation with a plan, situations suggesting the patient is unsafe or not alone with someone trustworthy — these may require activating local emergency services rather than continuing the video visit • Exam-dependent findings that cannot be excluded remotely: for example, a suspected testicular torsion, an unstable fracture, or a wound needing debridement — conditions where the diagnosis genuinely depends on palpation, range-of-motion testing, or direct visualization no camera can substitute for
Recognizing these and converting the encounter — rather than pushing forward with reassurance because the visit is "almost done" — is one of the most heavily weighted competencies in telehealth OSCE design.
A well-designed telehealth station will often script an ambiguous or subtly worsening finding partway through the encounter specifically to test whether the student notices the shift and appropriately escalates, rather than completing the visit as originally planned.
The Association of American Medical Colleges (AAMC) has articulated telehealth-specific competencies intended to sit alongside — not replace — standard clinical competencies, spanning six broad domains: patient safety and appropriate use of telehealth; access and equity (recognizing when a patient lacks the technology, connectivity, language access, or health literacy for a safe visit); communication via telehealth (webside manner); data collection via telehealth (structured history and adapted exam); technology for telehealth (platform competence, troubleshooting, privacy); and legal/regulatory/ethical considerations (licensure, documentation, informed consent).
These domains map closely onto the five stages of this simulation: consent and access considerations appear in setup; communication competencies map to webside manner; data collection covers the guided history and exam; safety and appropriate use covers diagnostic reasoning and red-flag recognition; and legal/regulatory considerations map onto documentation and safety-netting. OSCE stations increasingly draw their rubric line items directly from this framework.
| Product | Indication | Trial Design | Key Result |
|---|---|---|---|
| Low acuity, video-appropriate | Medication refill review, rash follow-up, mild URI symptoms, chronic disease check-in | History and visual inspection typically sufficient; objective vitals via home device if available | High diagnostic confidence achievable by video alone |
| Moderate, video with contingency | New abdominal pain (mild), musculoskeletal injury, uncomplicated UTI symptoms | Guided self-exam plus explicit safety-netting; low threshold to escalate if symptoms evolve | Video-first with a clear, pre-stated escalation trigger |
| High acuity, requires escalation | Chest pain, focal neurologic deficit, significant respiratory distress, severe abdominal pain | Video used only to triage and arrange transport; exam-dependent diagnosis deferred to in-person/ED | Video role is rapid recognition and referral, not definitive diagnosis |
| Access/consent-limited | Patient without adequate bandwidth, privacy, language interpretation, or capacity to consent | Visit converted to phone-only, interpreter added, or rescheduled in-person | Recognizes technology and equity as a clinical safety variable, not a logistics footnote |
A telehealth encounter is not complete when the video call ends. The closing stage — clear verbal safety-netting, a documented asynchronous follow-up plan, compliant e-prescribing where applicable, and a note that meets both clinical and regulatory documentation standards — is where many otherwise-strong student performances lose points, because it happens after the "interesting" clinical part feels finished.
"Safety-netting" means giving the patient a specific, actionable plan for what to do if things do not go as expected — and telehealth raises the stakes because the clinician will not see the patient again unless the patient (or a caregiver) takes action. A strong closing typically includes:
• Specific, not vague, escalation triggers: "if your temperature goes above 38.5°C" rather than "if you feel worse" • A clear channel for each level of concern: routine questions go to the patient portal message, moderate concerns get a scheduled callback, severe symptoms go straight to emergency services — and the patient can repeat this back • A defined time horizon: telling the patient when to expect to feel improvement and by when they should re-contact if that has not happened • Confirmation of understanding (teach-back): asking the patient to restate the plan in their own words, which is especially important on video where the clinician cannot read confusion as easily as in person • Written reinforcement: a portal message or after-visit summary repeating the verbal plan in plain language, since a stressed or unwell patient may not retain everything said out loud
OSCE examiners frequently score whether the safety net was specific and confirmed, versus generic and merely stated.
Verbal safety-netting that is not also confirmed with teach-back and reinforced in writing is treated in many telehealth curricula as functionally incomplete — the absence of a durable, referenceable record is itself the safety gap.
Telehealth visits increasingly extend beyond the live video call into asynchronous channels:
• Patient portal messaging for follow-up questions, photo submission (e.g., a healing wound), or lab-result review without requiring a full repeat visit • Remote patient monitoring integration, where home device data (blood pressure, glucose, weight) continues to flow to the care team after the visit ends • E-prescribing, which requires the clinician to confirm the pharmacy location relative to the patient's actual location, check for any controlled-substance restrictions specific to telehealth (many jurisdictions impose extra requirements, such as an initial in-person visit, before certain controlled substances can be prescribed via telehealth), and verify the prescribing clinician is licensed in the state or jurisdiction where the patient is physically located at the time of the visit — not where the clinician is sitting
Stations increasingly include a documentation/e-prescribing sub-task specifically to test whether students remember the location-based licensure check before sending a prescription.
The clinical note from a telehealth visit generally needs to include everything a standard note requires, plus telehealth-specific elements that carry both clinical and medico-legal weight:
• Modality and platform: that the visit was conducted via synchronous video (vs. audio-only or store-and-forward), which platform was used, and confirmation it met applicable privacy/security standards • Patient location at time of service: required both for licensure compliance (the clinician must typically be licensed in the state/jurisdiction where the patient is located) and for billing • Consent documentation: that telehealth-specific informed consent was obtained, ideally with the specific elements covered noted • Exam limitations explicitly stated: which components of a normal exam were not performed and why (e.g., "abdominal exam limited to visual inspection; palpation not performed via video") • Safety-netting and follow-up plan, in enough detail that another clinician reading the chart later would know exactly what the patient was told to watch for
Regulatory complexity is substantial and varies by jurisdiction: licensure requirements (a clinician generally needs a license valid in the patient's location, with some cross-state compact exceptions), reimbursement/billing rules that differ for audio-only versus video visits, and evolving rules around controlled-substance prescribing via telehealth all interact. OSCE stations at advanced levels increasingly test awareness of these constraints, not just clinical skill.
Well-designed telehealth OSCE stations are built to assess the full arc modeled in this simulation, typically via a checklist plus a global rating scale, mirroring standard OSCE methodology but with telehealth-specific items layered in:
• Technical/setup checklist items (platform check, identity/location verification, backup contact) • Consent-specific items (the distinct telehealth consent elements, not just general consent) • Communication/webside-manner items, often scored by the standardized patient's own perception of empathy and connection, not just the examiner's observation • Data-gathering adequacy, including whether the student appropriately directed a self-exam and acknowledged its limits • Clinical reasoning transparency and red-flag recognition, including whether a scripted deterioration was caught and acted on • Closing competencies: safety-netting specificity, teach-back confirmation, and documentation/licensure awareness
A global score alone tends to under-weight the technology and consent components relative to their real-world importance, which is why most modern telehealth OSCE rubrics use a hybrid checklist-plus-global-rating design — the same hybrid approach reflected in the five graded stages of this simulation.