I spent eight years on the other side of this question - as a classroom and clinical faculty, teaching dosage calculation, running med pass labs, and standing next to students at the bedside while they passed real medications to real patients. In that time, I watched a lot of students walk into clinical with a strong grade on their med math exam and absolutely no idea how to recover when a call bell went off mid-pass. The knowledge was there. The readiness wasn't.
That gap is the problem I kept running into when it came time to decide who was cleared to pass meds in clinical. A grade on a written test tells you what a student knows. It doesn't tell you what they'll do under time pressure, interruptions, and an unfamiliar eMAR. So, the question I learned to ask wasn't "did they pass the exam?" It was "what does readiness actually look like, and how do I observe it before a patient is involved?"
Medication competency has two layers: cognitive and procedural. Cognitive competency is what most testing captures: pharmacology, calculations, contraindications. Procedural competency is whether a student can execute the full workflow correctly and consistently - verifying the right patient, right drug, right dose, right route, and right time, in the right order, without skipping steps when something interrupts them.
I saw students who were strong in one layer and weak in the other far more often than I expected. That's exactly what paper-based testing misses, and it's why relying on it alone kept getting my students (and me) surprised in clinical.
After enough semesters of standing beside students during an actual med pass, I stopped trying to infer readiness from a test score and started watching for specific behaviors instead. These are the signals that told me more than any written exam ever did:
None of these five signals show up reliably on a paper exam. I only ever saw them when a student was performing the task.
Waiting until clinical to observe these behaviors is expensive in the worst way; a missed step or a bypassed alert becomes a real safety event instead of a teaching moment. Simulation let me move that observation earlier, into a setting where my students' mistakes were data instead of incidents.
The format of the assessment matters as much as the content here. A structured simulation that mirrors the actual eMAR and barcode workflow gave me a standardized way to watch for the five signals above across every student, instead of relying on my own subjective clinical impressions, which, if I'm honest, varied by how my day was going as much as anything else.
If your program's answer to "how do we know they're ready?" is still primarily a written test score, there's a real gap between what you're measuring and what you actually need to know before signing off on a student. In my experience, readiness assessment works best as a checkpoint built into the simulation curriculum - repeatable, observable, and consistent across cohorts - not a single high-stakes exam.
This is exactly the gap I now spend my time helping programs close at Sim2Grow. Platforms like the Sim2Grow Medication Administration Simulator are built for this: giving faculty a way to watch students perform the complete med pass workflow, flag the specific behaviors that predict clinical safety, and identify gaps while there's still time to close them.
Ready to see what a structured readiness assessment could look like for your program? Schedule a demo now.