Standardized Patient Case
A standardized patient case is the written package that defines what an SP portrays in an encounter: the patient's history and presenting problem, their affect and manner, how they respond to specific learner behavior, and the checklist or rubric used to score what happened. The case is what makes an SP encounter repeatable, because two SPs working from the same case should produce the same encounter for two learners who behave the same way.
Source: Association of Standardized Patient Educators, Standards of Best Practice
Case development is one of the five domains in the ASPE Standards of Best Practice, which puts it alongside SP safety and program management rather than treating it as paperwork. A usable case starts from the learning objective and the learner's level, then works backward to a presentation that forces the behavior being assessed. A case written the other way round, starting from an interesting diagnosis, tends to produce an encounter that is enjoyable to run and impossible to score.
What separates a strong case from a thin one is usually the response rules and the scoring instrument. Response rules tell the SP what to do when the learner asks an open question, interrupts, or delivers news badly, and they are what keeps a portrayal standardized without making it mechanical. The scoring instrument has to be written at the same time as the case, because a rubric bolted on afterward almost always asks about behaviors the presentation gave the learner no opportunity to show.
A case also carries the practical detail that decides whether a session runs at all: the SP's opening line, the information they withhold unless asked, the physical findings and any moulage required, the time limit, and the feedback the SP gives in role. Programs that keep a case library with version dates can retire a case that has circulated among learners and rotate a variant in, which matters most where the encounter counts toward a grade.
What this looks like in a program
- Writing the checklist and the case in one pass catches the objectives that the scripted presentation gives a learner no chance to demonstrate.
- A case library with version dates and retirement notes is how a program keeps high-stakes encounters usable after a cohort has talked about them.
- The response rules, more than the history, are what two SPs have to align on if their encounters are going to score comparably.
Last updated August 2026