Skip to content

mCLEIMS station design: six teams rotating through six 25-minute sequential simulation stations

Design · All designs
Evidence · no claims cited

Description

The 2-day mCLEIMS course organized 108 students into six teams of six per session, rotating through six specialty stations (pediatrics, traumatology, internal medicine, geriatrics, obstetrics/gynecology, emergency medicine). "Each station lasted 25 min: 2 min of facilitator briefing, 18 min of team task performance, 1 min of team-leader summary, and 4 min of reflection and feedback." Stations were linked as a patient journey rather than isolated exercises.

Design Implications

Context

Requirements

  • Preparatory information and learning objectives provided in a pre-brief at the start of each session

Constraints

  • Condensed 2-day format adapted because of local curricular requirements, scheduling constraints, and limited resources

Target Learners

  • second-year clinical clerkship medical students

Learning Goals

  • clinical skills
  • interprofessional collaboration
  • communication
  • patient safety

Claims

Examples

-

Key Sources

  • Liu Hsin-Liang, Lu Peih-Ying, Hsu Anna Shan-Chun, Lin Yen-Ko, Chan Kwong D., Lee Chien-Hsing, Chang Po-Chih. (2026). Implementing team-based sequential simulation for medical students in clinical clerkship: preliminary findings and learning efficiency evaluation. BMC Medical Education. https://doi.org/10.1186/s12909-026-09412-3
Page metadata
Field Value
type design
id mcleims-station-rotation-design
title mCLEIMS station design: six teams rotating through six 25-minute sequential simulation stations
description The 2-day mCLEIMS course organized 108 students into six teams of six per session, rotating through six specialty stations (pediatrics, traumatology, internal medicine, geriatrics, obstetrics/gynecology, emergency med...
status review
generated by process:settle-candidates on 2026-11-04
trust unverified — no one has confirmed this page's content
sources 1 — liu-hsin-liang-2026

Frontmatter is the page's machine-readable record — see the Schema & Guide.