What the ASPE standards ask of a standardized patient program
ASPE's 2017 Standards of Best Practice cover five domains for a standardized patient program and set no numeric limits. A page of limits your program can own.
ClinicalSim Team
ClinicalSim
The ASPE Standards of Best Practice are easy to agree with and hard to audit against, because they're written as principles. Read closely, what they hand a standardized patient program is a list of decisions with the numbers left blank. A program that never fills them in follows the standards in spirit and can't show that it follows them in practice.
What are the ASPE Standards of Best Practice?
The ASPE Standards of Best Practice are the Association of Standardized Patient Educators' consensus guidance for programs that train standardized patients (SPs), the people who portray patients for teaching and assessment. Published in Advances in Simulation in 2017 after a three and a half year consensus process that began with a modified Delphi round in December 2013, they cover five domains: safe work environment, case development, SP training, program management, and professional development (Lewis et al., 2017). The standards rest on five values (safety, quality, professionalism, accountability, and collaboration) and are meant to be used alongside the INACSL simulation standards.
A commentary in the same journal by Nestel, Roche, and Battista describes them as "essential and sometimes aspirational practices" and as a "living document" expected to change (Advances in Simulation, 2017). The standards' own authors agree: they offer "both practical and at times, aspirational guidance," and not every practice applies to every situation.
Why the standards carry no numbers
The first safe work practice in the standards reads: "Ensure safe working conditions in the design of the activity (e.g., number of rotations, number of breaks, physical, cognitive, and psychological challenges in the role portrayal)." That sentence names the variables a program controls, and it stops there. Nowhere in the five domains does ASPE say how many encounters an SP can run in a session, how long a break should last, or how many minutes de-roling takes.
That's a defensible choice for an international document. A short history station and a long goals of care conversation don't belong under the same cap, and a program running high-stakes exams has different obligations from one running formative practice. But it moves the work to the program. Every limit the standards imply has to be set locally, by someone who knows the cases, and written somewhere an SP, a faculty member, or a new coordinator can find it.
The authors are blunt about what's at stake: "Failure to follow the ASPE SOBP could compromise the safety of participants and the effectiveness of a simulation session."
Safe work environment: the limits to set before anyone is booked
The safe work environment domain has three principles (safe work practices, confidentiality, and respect), and most of its practices turn into a decision a program can write down in a sentence. The standards ask programs to:
- Design activities around the number of rotations, the number of breaks, and the physical, cognitive, and psychological load of the role.
- "Structure time and create a process for de-roling and/or debriefing."
- "Allow SPs to opt out of any given activity if they feel it is not appropriate for them to participate."
- Give SPs a way to report adverse effects from an activity, and monitor and respond when it happens.
- Set clear expectations with the faculty or department requesting the encounter about what an SP will and won't do.
- Make sure SPs understand their compensation before they accept work, and respect the boundaries they set for themselves.
The standards ask for time for debriefing after the encounter. Preparation and briefing before a scenario is what the INACSL standards call prebriefing.
Read as an operations checklist, each item is a question with a local answer. What is our maximum number of encounters per SP per session for an emotionally heavy case, and is it lower than for a routine history? How many minutes of de-roling do we schedule after a breaking bad news case, and who runs it? Where does an SP report that a role went badly for them, and who reads it, and how soon?
A program that can answer those questions from a written policy is doing what the domain asks. A program where the answers live in one coordinator's head is relying on that person never leaving.
Case development and training: where the educator hours go
The case development and SP training domains carry most of the practices that need educator time, and a capacity plan that counts only SP hours leaves them out. Cases should align with measurable learning objectives, get a dry run or pilot before they count, and include training protocols for whoever rates the encounter, SP or faculty. ClinicalSim's OSCE case design guide covers that build in more detail.
Training is where the standards come closest to a measurable requirement. Programs are asked to ensure consistency and accuracy of portrayal within each SP and across SPs playing the same role, to "Ensure that SPs are able to complete assessment instruments in the time allotted," and, in high-stakes assessment, to verify inter-rater reliability and check each rater's consistency over time. None of that comes with a threshold attached, so a program has to choose one: what agreement it accepts between two SPs scoring the same recorded encounter, and how often it re-checks.
Those hours land on the SP educator, not the actor. Simulation educators doing that work can look at the Certified Healthcare Simulation Educator exam from the Society for Simulation in Healthcare. A 2026 review of peer simulated patient programs lists "the need for ongoing SP-educator capacity to recruit, train, and quality-assure SP performance" among the practical barriers to expanding SP use (Pollak and Feinstein, Postgraduate Medical Journal, 2026). That's also why capacity runs out before the room schedule does, which ClinicalSim covered in why standardized patient programs run out of capacity.
Program management: records and quality are the auditable parts
The program management domain has six principles: purpose, expertise, policies and procedures, records management, team management, and quality management. Two of them produce artifacts an accreditor, a general counsel, or a new director can ask to see.
Records management asks programs to document methods for "securely storing, archiving, and destroying confidential data," and the standards name SP records, learner data, video, and consent forms among them. For a program recording every encounter, that's a retention schedule with a deletion date on it, and somebody who owns the deletion.
Quality management asks programs to gather data and feedback from SPs, learners, faculty, and other users on a regular schedule, analyze it, "Implement changes for continuous improvement," and tell the people who gave feedback what changed. That last step is what tells an SP that the report they filed was read.
Team management adds two items with legal weight. Programs should consult legal, financial, and human resources experts on SP employment status and compensation, and should recruit and keep a pool of SPs that reflects the diversity of the patients they portray.
A one-page version a program can write this term
The standards don't need to be rewritten to be usable. They need a page of local numbers next to them. A workable version has one line per decision, each with a number or a named owner and a review date:
- Session limits. Maximum encounters per SP per session, set separately for routine and emotionally demanding cases.
- Breaks and de-roling. Minutes scheduled after each kind of case, and who leads the debrief.
- Opt-out and adverse effects. How an SP declines a role or reports a bad experience, and who responds.
- Rater agreement. The agreement level the program accepts on high-stakes cases, and how often it re-checks.
- Records. Retention period for video and learner data, and the date and owner for deletion.
- Quality loop. Which feedback is collected each term, and where the program reports back what it changed.
None of these numbers come from ASPE, so none of them can be borrowed from a vendor or a neighboring school without checking them against the program's own cases. That's the point of writing them down.
A revision is on the way
ASPE's Standards of Practice Committee lists publishing "a revision of the 2017 ASPE SOBP and a companion paper" among its 2026 goals. In a 2026 commentary, ASPE's elected leaders write that the 2017 document "is undergoing its first major revision, with an anticipated publication date of 2026" (Wallace et al., Advances in Simulation, 2026). The same commentary marks new standards for physical exam teaching associates, "what is now the third SOBP publication" after the 2017 standards and the 2021 standards for gynecological and male urogenital teaching associates (Hopkins et al., 2021). A program that writes its local limits against the five 2017 domains now should plan to re-read them against the revision when it publishes, rather than wait for it.
Where AI patients fit
ClinicalSim is a voice-based AI patient simulation platform for practicing and measuring clinical communication in medical education, and learners can use it for more practice between scheduled SP encounters. AI patients don't do what a trained SP does: respond as a person in the room, give feedback from having been on the receiving end of the conversation, and carry a summative OSCE station. The ASPE standards exist because that work is done by people, and the safety domain in particular is about protecting them. ClinicalSim's comparison of AI clinical simulation and standardized patients sets out where each is stronger: extend your SP program, don't replace it.
References
- Lewis KL, Bohnert CA, Gammon WL, Holzer H, Lyman L, Smith C, Thompson TM, Wallace A, Gliva-McConvey G. The Association of Standardized Patient Educators (ASPE) Standards of Best Practice (SOBP). Advances in Simulation. 2017. doi:10.1186/s41077-017-0043-4
- Nestel D, Roche J, Battista A. Creating a quality improvement culture in standardized/simulated patient methodology: the role of professional societies. Advances in Simulation. 2017. doi:10.1186/s41077-017-0051-4
- Wallace AM, Krebsbach C, Radway J, Clark L. Contextualizing the ASPE Standards of Best Practice: reflecting on the past, present, and future of SP methodology. Advances in Simulation. 2026. doi:10.1186/s41077-026-00480-5
- Hopkins H, Weaks C, Webster T, Elcin M. The Association of Standardized Patient Educators (ASPE) gynecological teaching associate (GTA) and male urogenital teaching associate (MUTA) Standards of Best Practice. Advances in Simulation. 2021. doi:10.1186/s41077-021-00162-4
- Standards of Practice Committee. Association of SP Educators. 2026.
- Pollak U, Feinstein Y. Training medical students as peer simulated patients in undergraduate medical education: a narrative review and implementation framework. Postgraduate Medical Journal. 2026. doi:10.1093/postmj/qgag100