An OSCE station bank is a library of reviewed stations, each with its blueprint cell, version history, run record, and metrics. A bank allows a school to reuse good stations across sittings, as the evidence supports when security holds. The bank owner controls exposure, decides when a station returns, and retires a station whose metrics or content have drifted.
Why a bank, not a folder
Writing a station to the template, reviewing it, and piloting it takes weeks of clinician time. A station used once and lost is that investment thrown away. A bank is what makes the blueprint's rotation plan possible: the cell that the exam does not sample this year is filled next year by an existing station.
The AMEE guide on OSCE organization ends its station-development flow at the bank, after peer review, piloting, and psychometric analysis. The bank is where the results of that work are kept, not a place to store drafts. The written-exam equivalent is described in how to structure a question bank. An OSCE bank has the same logic with heavier objects: a station carries a script, a scheme, an equipment list, and a patient role, not a stem and five options.
What record does each station carry?
Field | Why the bank needs it |
|---|---|
Blueprint cell: competency, system, level | So the bank can be searched by the cell the next exam needs |
Station type and duration | So a station fits the circuit it is pulled into |
Version number, date, author, reviewer | So the exam office knows which version ran and who approved it |
Change log between versions | So a change in facility can be traced to a change in the station |
Run record: sitting, cohort size, examiners | So exposure can be counted, and the metrics have context |
Metrics per run: facility, discrimination, checklist-global agreement | So the bank owner can see drift, and the quality section's thresholds apply |
Status: draft, piloted, active, rested, retired | So nobody pulls a retired station by mistake |
Equipment and role requirements | So the site team can plan before the station is chosen |
Version control is the field most often missing. A station edited in a shared document has no versions; it has a current text and a memory of what it used to say. When a station's facility drops from 0.7 to 0.4 between sittings, the first question is what changed. A change log answers it. A memory does not.
When can a station be reused?
More often than most schools assume, if the bank is secure. A Canadian study followed six stations reused one year apart in a ten-station OSCE for international medical graduates, with 191 candidates the first year and 236 the second. The stations' measurement properties were equivalent across the two years, and the generalizability coefficient exceeded 0.70 both times. The authors concluded that, with careful security measures, high-stakes OSCEs may reuse stations with stable properties over several years.
Three conditions attach to that finding. The station must be unchanged, or its changes logged. The security must hold, which is the delivery section's job: quarantine between cohorts, no phones, mark sheets and instructions counted back. And the metrics must be read after each run. Stable properties are a finding, not an assumption. A station that was stable for two runs and drifted on the third has drifted, whatever the paper says.
How is exposure controlled?
Exposure is the number of candidates who have seen a station, and the time since they saw it. The bank owner sets three rules.
- A rest period between runs. A station used in this year's final does not appear in next year's final. It may appear in a different year group or a different program.
- A cap on lifetime exposure. After a set number of runs or candidates, the station is rested and rewritten from the case: same cell, new patient, new details.
- An immediate rest after a breach. If a station's content is known to have leaked, it is rested, and the run's metrics are read for the signature of a leak: a facility jump with lower discrimination.
The numbers depend on the school. A single-cohort program with 80 candidates a year can rest stations for two years and never run short. A large school with several sittings a year needs a bigger bank or faster rewriting. The budget page treats station writing as a recurring cost for that reason.
When is a station retired?
A station retires for one of four reasons, and the record says which.
- Content drift. The guideline changed, the drug was withdrawn, the presentation is no longer taught. The station is wrong, not merely old.
- Metric drift. Facility, discrimination, or the checklist-global agreement has fallen outside the bank's thresholds for two runs, and review found no fixable cause.
- Exposure. The lifetime cap is reached.
- Role loss. The simulated patients who could play it are no longer available, and the role cannot be trained into new ones.
A retired station stays in the bank as a record. Its metrics still describe the cohorts it ran on, and its case may be the seed of the rewrite. Deleting a station deletes the evidence that supported the results it produced.
Who owns the bank?
One person. The governance page puts the bank owner on the roles table. The owner keeps the record, applies the exposure rules, calls the retirements, and reports the bank's state to the assessment committee once a cycle: stations per cell, stations active, stations rested, cells with no station at all. That last number is the writing commission for the year.
The owner is not the reviewer. Review is the workshop's job. The owner is the librarian who ensures that what the workshop approved runs, and that what ran gets analyzed.
Limits
The evidence of reuse comes from one program with strong security and a stable examiner pool. A school with weak quarantine, candidates who sit together in the afternoon, and a student body that shares cases online should expect stations to leak faster than the study suggests. The bank rules are a control, not a guarantee. The metrics after each run are the check.
Frequently asked questions
Can OSCE stations be reused?
Yes, when security holds. A study that reused six stations one year apart, with different candidates, examiners, and simulated patients, found equivalent measurement properties and reliability above 0.70 in both years. The conditions are an unchanged or logged station, quarantine that works, and metrics read after every run.
How often should an OSCE station be rewritten?
When its record says so: content drift, metric drift over two runs, a lifetime exposure cap, or loss of the simulated patients who can play it. Set a rest period between runs of the same station in the same exam, and a cap on lifetime exposure. The numbers depend on the cohort size and the number of sittings per year.
What should an OSCE station bank record?
The blueprint includes the cell type and duration, version number and change log, author and reviewer, the run record with cohort size and examiners, the metrics per run, the status, and the equipment and role requirements. The version history is the field most banks lack, and the one an appeal or a metric drop needs first.
What is station exposure?
The number of candidates who have seen a station and how recently. Exposure rises with each run and with any leak. The bank controls it with a rest period between runs, a lifetime cap, and an immediate rest after a suspected breach. A facility jump with falling discrimination is the signature of a leaked station.
Should retired OSCE stations be deleted?
No. A retired station is marked retired and kept. Its metrics describe cohorts whose results still stand, and its case is often the seed of the rewrite. Deleting it deletes the evidence behind past pass decisions. The status field, not deletion, is what stops it being pulled again.