Exam day used to end in a stack of paper. The wall is already filling in.
Stand up the stations and the circuits. Print a QR for each examiner. They score from the link, including people with no Medtrics account. The control room watches completion as it happens.
Bring one exam day to the discovery session. We load the stations and walk the builder, the tokens, and the wall, and the exam day stays yours either way.
Pick your seat
Practicum Completion Wall
Updated automatically from station assignment and response status.
Station matrix
| Student | 1 | 2 | 3 | 4 | 5 | 6 |
|---|---|---|---|---|---|---|
| Learner A | Done | Done | Now | Open | Open | Open |
| Learner B | Done | Now | Open | Open | Open | Open |
| Learner C | Done | Done | Done | Late | Open | Open |
| Learner D | Now | Open | Open | Open | Open | Open |
| Learner E | Done | Done | Flag | Open | Open | Open |
| Learner F | Open | Open | Open | Open | Open | Open |
Detail
Station 3
- Examiner
- Examiner 1
- Room
- Room A
- Status
- In progress
Open response
Live station completion. Demonstration data.
Medical schools · Veterinary · Nursing · Allied health
Clinical skills is the stations, not the clipboards.
The stations are known. The work is the day around them: who sits where, who scores, which sheet is live, and whether the last circuit is actually done. We built practicum around four beliefs.
The rotation should exist before anyone prints a clipboard.
Cases, circuits, rooms, examiners, and learner seats are a blueprint. Generate the day. Then print. The grid that gets approved is the grid that runs.
Examiners should never create an account to score a station.
A printed QR opens the station rubric for the assigned learner. Standardized patients score from the kiosk link only. They submit and the next encounter is waiting.
The control room should watch a wall, not collect paper.
Completion by learner and station refreshes on its own. Done, now, late, open. Open a cell for the examiner, the room, and the response.
Nobody should run exam day alone.
Your Medtrics team loads the cases and the first day with you, prints the first token sheets, and sits the first live wall.
One cycle, from the blueprint to the scores
Build the day. Print the station links. Examiners score. The wall fills in. After the last circuit, question scores are already on Analytics.
Coordinators run the day. Examiners score from a QR. The skills office owns the cases and the pass line. Same cycle.
Build
Stations, circuits, people
The blueprint becomes the day.
A QR on the door
No account for examiners or SPs.
Score
Submit and next
The kiosk already knows the learner.
Wall
The control room watches
Scores are already there.
Coordinators build the day, print tokens, and watch the wall.
Examiners score from a QR, including people with no account.
The skills office sits. Cases in a library. Scores on Analytics after the last circuit.
Exam day looks different from each seat.
The same practicum day reads differently depending on where you sit. Pick your seat.
For clinical-skills coordinators
I can build the stations. I cannot see whether station 4 is actually done.
Name the day, set the stations, generate the grid.
Exam name, date, rubric, stations, circuits, rooms, examiners, learner seats. Save a draft. Create the day. Publish when staff-facing surfaces should go live. After publish, swap examiners and move learners without rebuilding.
New Practicum Day
Create the day from a blueprint, then fix exceptions before generation.
Day blueprint
Set the structure once, build the grid, then edit exceptions.
Exam name
Year 2 Clinical Skills Day
Academic period
AY 2026-2027
Part of OSCE (optional)
Leave empty for a single day
Date
Mar 12, 2026
Start time
08:00
Site
Skills center
Control room
Control room A
Published rubric
Station rubric
Slot minutes
8
Stations
8
Watch completion while the circuits are still running.
The live wall is a station matrix. Filter by completed, in progress, now, overdue, or flagged. Open a cell for the examiner, the room, and the response. It polls on its own.
Practicum Completion Wall
Updated automatically from station assignment and response status.
Station matrix
| Student | 1 | 2 | 3 | 4 | 5 | 6 |
|---|---|---|---|---|---|---|
| Learner A | Done | Done | Now | Open | Open | Open |
| Learner B | Done | Now | Open | Open | Open | Open |
| Learner C | Done | Done | Done | Late | Open | Open |
| Learner D | Now | Open | Open | Open | Open | Open |
| Learner E | Done | Done | Flag | Open | Open | Open |
| Learner F | Open | Open | Open | Open | Open | Open |
Detail
Station 3
- Examiner
- Examiner 1
- Room
- Room A
- Status
- In progress
Open response
What your Medtrics team does here: your Impact Engineer loads cases and the first day from how you actually run the exam. Your Academic Strategist walks publish, tokens, and the wall so exam morning is not the first time you see it.
For examiners and standardized patients
I have a station, a learner, and gloves on. If it takes a password, it waits until after.
A sheet on the door. The QR is the login.
Control room prints station token sheets. Each QR is single-use and expires after the exam window. Download prints the live codes again. Reprint issues new codes and voids the old sheet.
Print SP token sheets
Download QR sheets for station staff. Download prints the same live codes again. Reprint sheet issues new codes and voids posted sheets.
Station
Circuit
12 printable links · 1 file(s)
Station 1
Circuit Alpha
Learner: Learner A
Prefix A · new link
Station 2
Circuit Beta
Learner: Learner A
Prefix A · new link
Unused links open the station rubric for the assigned learner.
Submitted links advance the station queue and cannot be reused.
Links scanned after the exam window show the control-room message.
Reprinting revokes old links and writes an audit entry.
Single-use station link · expires after the exam window
Open the link, score, submit, next encounter.
The header already has the station, the case, the learner, and the round. Tap the rubric. Device draft saves if the network drops. Submit and the next encounter is waiting. No Medtrics account.
Introduces self and states purpose of the encounter
12345Elicits chief complaint accurately and without interruption
12345Explores onset, duration, and severity of symptoms
12345Uses open-ended questions before closed-ended questions
12345
What your Medtrics team does here: your Impact Leader prints the first sheets with your control room and stands a station so examiners see the kiosk before the cohort arrives.
For clinical-skills directors and the office that owns the exam
We own the cases. We should not rebuild the scores in Excel after the last circuit.
Cases live in a library, already tied to a published rubric.
Reusable station cases: name, code, published evaluation form, active or inactive. Pick them when you build the day. The form that scores the station is the form on the case.
Case Library
Reusable station cases linked to published evaluation forms.
| Case | Code | Evaluation form | Status | Actions |
|---|---|---|---|---|
| Chest pain | CS-01 | Station rubric A | Active | EditRemove |
| Abdominal exam | CS-02 | Station rubric B | Active | EditRemove |
| Informed consent | CS-03 | Station rubric C | Active | EditRemove |
| Hand hygiene | CS-04 | Station rubric D | Inactive | EditRemove |
Question scores, by station, after the day.
Analytics reviews Yes and No counts for completed encounters at each station. Save a pass line when you are ready. Pass/fail appears after that. Export the view you are looking at.
Analytics
Review question scores for each OSCE.
Station 1
Search learners...| Introduces self | Open questions | Closes encounter | Washes hands | |
|---|---|---|---|---|
| Learner A | Yes | Yes | Yes | No |
| Learner B | Yes | No | Yes | Yes |
| Learner C | Yes | Yes | No | Yes |
| Learner D | No | Yes | Yes | Yes |
Yes and No counts for all completed encounters at this station, not just this page.
| Question | Yes | No |
|---|---|---|
| Introduces self | 3 | 1 |
| Open questions | 3 | 1 |
| Closes encounter | 3 | 1 |
| Washes hands | 3 | 1 |
What your Medtrics team does here: your Academic Strategist sits the first analytics pass with you so the pass line means what the skills office actually uses.
You will not stand up exam day alone.
Software vendors hand you a form builder and a login. We hand you three people who know your program by name, and they stand exam day with you.
Vicky DaiImpact Leader
Meg RodgersImpact Leader
Santhosh Cherian, MDAcademic Strategist
Weekly during onboarding. Monthly after go-live. Quarterly with your directors. Once a year, on your campus.
- 1
Discovery. Your Impact Leader maps how the exam actually runs: stations, circuits, who prints, who scores, where the control room sits. The picture of how exam day runs stays yours.
- 2
Cases. Your Impact Engineer loads station cases and published rubrics from your files, in the order the day depends on, and cleans what needs cleaning with you.
- 3
First day. You build one day together. Generate. Publish. Print tokens. Watch the wall. The first live exam happens with us in the room.
- 4
Scores. After the last circuit, Analytics is the board. Your Academic Strategist walks the pass line with the skills office.
- 5
Cadence. Weekly during onboarding. Monthly after go-live. Quarterly with your directors. Once a year, on your campus.
New Practicum Day
Create the day from a blueprint, then fix exceptions before generation.
Day blueprint
Set the structure once, build the grid, then edit exceptions.
Exam name
Year 2 Clinical Skills Day
Academic period
AY 2026-2027
Part of OSCE (optional)
Leave empty for a single day
Date
Mar 12, 2026
Start time
08:00
Site
Skills center
Control room
Control room A
Published rubric
Station rubric
Slot minutes
8
Stations
8
The same exam day, in your program's words.
Stations, examiners, a live wall. The nouns change: OSCE or skills exam, student or trainee, SP or support, skills center or teaching hospital.
A form builder stores the rubric. This runs the day.
Legacy platforms let you build a checklist and export a spreadsheet after. You still print paper, still chase missing stations, still rebuild scores on Sunday. Medtrics generates the day from a blueprint, lets examiners score from a QR, and keeps a live wall while the circuits run.
A QR, not another login.
Examiners and standardized patients open a single-use station link. Logged-in staff still have the control room. The scoring delay at the doorway is a login problem. This is the login we removed.
The wall is the day, not a recap.
Completion by learner and station while the exam is still running. Nobody waits for the last clipboard to know who is late.
A team that runs the first exam with you, and stays.
An OSCE vendor hands you a rubric builder. We map how your exam actually moves, load the cases, and stay on a first-name basis after go-live.
From clipboards to a wall you can watch
Programs have scored a fully digital OSCE from printed station links, without training every examiner. After the last circuit, scores were on one board instead of in a stack of paper.
Before
Stations on paper. Scores in Excel. Sunday after the exam is a grading marathon.
After
Examiners score from a QR. The control room watches the wall. Question scores are already on Analytics.
Questions programs ask
See one exam day, built, printed, and on the wall.
Bring one OSCE to the discovery session. We load the stations and walk the builder, the tokens, and the wall, and the exam day stays yours either way.
Reviewed against shipped Practicum (day builder, token sheets, examiner kiosk, live wall, case library, analytics) on September 2, 2026. Accreditor names are used descriptively; nothing here implies endorsement.