How to Run a Patient-Monitor Simulation Across iPads
Run a multi-iPad monitor simulation without losing the room
Updated July 13, 2026
To run a patient-monitor simulation across iPads, assign each device one role, pair and test the screens before learners enter, rehearse the cue plan, and keep a manual fallback ready. The four-part method below turns a fragile technology setup into a repeatable facilitation workflow.
Give every screen one job before pairing begins
Start with the room plan, not the connection button. A screen without a named owner becomes a shared distraction: facilitators reach for the wrong device, learners see an upcoming cue, or two people believe the other person is documenting. Write the role on the case plan and place each device where that role can be performed.
| Screen job | Primary user | Placement check |
|---|---|---|
| Facilitator control | Person directing simulated state and cues | Hidden from learners but visible to the facilitation team |
| Patient-monitor display | Learners observing the simulated monitor | Readable from the learners' working position |
| Optional action surface | Learner recording simulated assessments or interventions | Reachable without blocking the monitor display |
Failure mode this prevents: pairing devices first and deciding their jobs later. A successful connection does not tell the team who controls, who observes, or who records.
Pair early, then run the same preflight every time
A connected badge is only the first check. Prove the whole signal path while there is still time to fix it, then return every screen to the intended opening state. Use the same short sequence for rehearsals and live sessions so a skipped step is obvious.
- Connect the facilitator screen to the monitor display and any optional learner screen.
- Send one clearly visible test change and have a second team member confirm what appeared.
- Test the specific controls the case will use rather than tapping every available control.
- Return the display, event log, and facilitator notes to the planned starting point.
- Lock device orientation, power, notifications, and room placement according to your local setup.
The failure this catches is the false-ready room: devices appear connected, but the cue arrives on the wrong screen, the display is left in a test state, or a notification interrupts the opening minute.
Write a cue sheet that separates state changes from teaching cues
Do not place the entire scenario in one dense paragraph. For each planned moment, separate what changes on the simulated display, what the facilitator says or does, and what confirms that the moment has landed. This keeps a technical action from accidentally becoming an instructional hint.
| Run-sheet line | What to write | Why it is separate |
|---|---|---|
| Simulated state | The display or scenario state that changes | Keeps the technology action unambiguous |
| Facilitator cue | Only the information the case design intends to reveal | Prevents accidental coaching |
| Confirmation | The visible or verbal sign that the event was received | Stops the timeline from advancing on assumption |
| Recovery | The action to take if the cue or display change fails | Protects the objective when technology misbehaves |
Make the stop condition and fallback visible to the team
A simulation team should not invent pause language while learners wait. Agree on the stop condition and recovery path during rehearsal. The goal is not to hide every technical problem; it is to keep the problem from changing what learners are being asked to demonstrate.
- Name who may pause, resume, or end the scenario.
- Choose a plain phrase for a technology hold and use it consistently.
- Keep a paper or verbal backup for the cues tied to the learning objectives.
- Decide whether to resume from the saved state, restart a segment, or continue in discussion format.
- Record the interruption so it can be considered during evaluation and debriefing.
Where VitalSim Monitor fits
VitalSim Monitor is being prepared for launch around this multi-screen pattern. The current development build supports Controller and Monitor roles, with an optional Bedside role when it fits the simulation plan. Devices can pair on local Wi-Fi or remotely with a room code. Those tools organize the signal path; the educator still owns the objectives, cues, room plan, and fallback.
Frequently asked questions
How many iPads does a patient-monitor simulation need?
A multi-device setup needs at least one facilitator-controlled screen and one learner-facing monitor display. Add a separate learner action screen only when it serves a defined role in the scenario; an unused screen adds setup work without adding learning value.
What should a facilitator do if pairing drops during a simulation?
Use the pause language and fallback chosen before the session. State that there is a technology hold, preserve the current scenario state, and resume or move to the backup format without turning the outage into an unplanned learner test.
Should learners be able to see the instructor controller?
Usually the control screen should sit outside the learners' sightline so upcoming cues remain hidden. If seeing the control screen serves a stated objective, make that choice deliberately during design rather than by accident in the room.
Planning a monitor-based learning experience for your program?
Discuss an educator pilotVitalSim Monitor is in pre-launch development. Pilot conversations are for educators evaluating simulation workflows.