A simulation AV system captures a clinical scenario from several angles, lets an operator run it from a control room, records every feed in sync, and plays it back for debrief. Cameras, microphones, the patient monitor, and manikin data all land on one timeline. This page explains how each part works, how the room gets built, what the gear and software options are, and what drives cost — so you can plan a lab before you talk to a vendor.
Here is how I take a simulation room from a floor plan to a working capture system. No black boxes — this is the real process.
1. Read the drawing first. I start with the architectural plans and the program's scenario list, not a product catalog. The plan shows sightlines, ceiling heights, and where the one-way glass sits. The scenarios tell me what has to be captured and reviewed.
2. Place cameras for coverage. Each bay needs the bed, the care team, and the vitals monitor in frame at once. I mark fixed positions on the ceiling plan and check every angle against casework and lights so nothing blocks the shot.
3. Budget the audio. Ceiling mics over each bed, a feed from the patient monitor, and intercom to control. I count channels early, because audio is where most sim recordings fall apart.
4. Lay out the control room. One operator should run cameras, recording, scenario audio, and lighting from a single seat behind the glass. I design the rack, the operator screen, and the sightlines so they never have to get up mid-scenario.
5. Make it record in sync. Every camera, every mic, and the monitor feed land on one timeline, so debrief is not a guessing game. I specify the capture platform and the network that carries it.
6. Draw it so the trades can build it. Camera locations, conduit, power, rack elevations, and a cable schedule — the documentation the electrician and the capture vendor actually need.
That is the whole method. The knowledge is free. If you want it designed and documented for your building, that is what we do.
A simulation AV system is a handful of subsystems that have to work together: cameras, microphones, a control room, recording, debrief, and integration with the manikin and patient monitor. Here is what each one does and what to weigh when you plan it.
A single-bed room usually runs three to five cameras, so the patient, the whole team, and the clinical detail are all in frame at once — you cannot re-stage in debrief what the camera missed. One or two wide cameras in opposite corners cover team movement; a ceiling camera over the bed captures hands-on technique; and a pan-tilt-zoom camera lets the operator push in on a syringe label or a wound without moving anyone. Fixed cameras are reliable and cheap to run; PTZ adds reach but needs an operator. Resolution is typically 1080p, with 4K only where you need to crop in, and low-light performance matters for night and trauma scenarios. Every angle is checked on the reflected ceiling plan so booms, lights, and curtains never block a shot.
Most failed sim recordings fail on audio, not video. A room full of monitors, ventilators, and overlapping voices is a hard acoustic problem. Ceiling microphones over the bed capture the team without anyone wearing a mic; boundary mics fill the corners; and wireless lavaliers go on facilitators, standardized patients, and roaming proctors whose voice has to stay clear as they move. The patient monitor and the manikin speaker are taken as direct feeds rather than picked up acoustically. Each channel is recorded separately so it can be balanced later, and acoustic treatment — soft ceilings, door seals, quiet HVAC — does as much for intelligibility as the microphones.
One operator runs the session from a control position, usually behind one-way glass, driving cameras, audio, recording, scenario cues, and lighting from a single workstation. The glass size and placement set the sightlines and the camera angles, so they are decided early, on the drawings, not as a finish detail. A well-designed control room keeps the operator on the scenario instead of hunting through menus, and in a multi-room center it is laid out so a small team can run the whole floor.
A capture platform records every camera, every microphone, and the patient-monitor feed onto one timeline, so debrief is never a guess about which clip matches which moment. The operator tags events as they happen — a missed step, a key decision, a complication — which builds an index into the recording before the scenario is even over. The platform is the software layer that turns raw AV into a searchable teaching asset.
Debrief is where the learning happens, and the AV exists to serve it. Faculty replay any camera angle, scrub to a tagged moment, and pause on a decision point, with the patient monitor shown beside the room video so students see what they saw and what they missed. Side-by-side review compares two attempts or two teams, and clip export builds a teaching library. A debrief room needs a large display, clean audio, and a control simple enough that faculty run it without a technician.
Patient-monitor displays and manikin data — from platforms such as SimMan and similar simulators — are recorded alongside the video, so the debrief shows what the students actually saw and how the patient responded, not just a camera view of the room. Capturing the monitor as a clean feed keeps the vital signs readable, and recording the manikin state lets faculty line up clinical changes with the team actions.
Clear, lag-free audio links the control room, the simulation room, and the debrief space. Faculty feed cues to the operator, speak to students as the patient or a proctor, and answer questions from control without breaking the scenario. Good intercom is what lets a facilitator run a believable encounter from behind the glass.
Lighting does real work in a sim room: bright, even task light for a procedure, dimmed scenes for a nighttime scenario, and a fast reset between runs, all on the same control system as the cameras so the operator sets the scene without walking in. Outside each room, occupied-and-available signage and room-scheduling integration keep live sessions from being interrupted, with a do-not-disturb state that turns on automatically during a scenario.
AV is one trade among many in a simulation build, and it touches the others. Planning it from the first drawing prevents change orders later.
The window between the sim room and the control room sets the operator sightlines and the camera angles. Its size and placement are an early architectural decision, not a finish detail.
Cameras, microphones, lighting, and speakers all hang from the ceiling and have to clear casework, booms, and medical-gas runs. They are coordinated on the reflected ceiling plan during design.
Camera and microphone runs, control wiring, and rack power are roughed in before the walls close. A missed conduit means cutting drywall later, so the AV rough-in is scheduled with the electrician.
Quiet rooms record clean audio. Duct design, door seals, and wall construction all show up in the recording, so acoustics are treated as part of the AV scope rather than an afterthought.
Camera locations, rack elevations, and a cable schedule go to the electrician and the capture vendor, so the room is built once instead of reworked in the field.
A simulation center is a small video-production and data operation, and the network is its backbone.
Each HD stream is a few megabits per second, so a center running several rooms at once needs a network designed for that load — usually a segmented VLAN kept separate from hospital or campus IT. IP cameras and microphones are often powered over Ethernet, which simplifies wiring but loads the switches, so cable type and length are specified during design. Video and audio over IP commonly use protocols such as NDI for video and Dante for audio. Recordings are large, so the center decides how long sessions are kept, who can reach them, and when they are purged, then sizes storage to the room count, recording hours, and retention policy.
The platform organizes everything the AV captures, and the major options differ in how they handle recording, live event tagging, debrief annotation, assessment and scoring, scheduling, and storage. The right approach is to design the AV to work with the platform a program already owns or plans to buy, rather than letting one vendor hardware lock in the choice. A manufacturer-agnostic design keeps that decision open and lets the capture software and the AV be selected on their own merits.
Simulation centers work under professional standards, and reliable AV supports them. Bodies such as the Society for Simulation in Healthcare (SSH) accredit centers, and the Healthcare Simulation Standards of Best Practice from INACSL describe how simulation should be run. Dependable capture, synchronized recording, and good debrief are part of the assessment and record-keeping these expect, which is why the AV is treated as core infrastructure rather than an accessory.
Recordings can include students, faculty, and standardized patients, so centers set policies for consent, access, retention, and deletion. Where real patient information could appear, HIPAA-style handling applies; at a university, student records can fall under FERPA. The AV design supports these rules by controlling who can view and export sessions, how long recordings persist, and where they are stored, and by keeping the recording network separate from general IT so sessions are not exposed.
Two sim labs can differ widely in cost. The drivers are predictable, and knowing them helps you budget before you ever get a quote.
The biggest factors are the number of rooms and stations, the cameras and microphones per room, whether it is new construction or a retrofit (open ceilings and fresh conduit are cheaper to work in than a finished room), the capture platform and its licensing, the control room and shared network and storage, and the documentation. Many centers phase the work — building the network and a few rooms first, then expanding — with the infrastructure designed for the final size so growth is plug-in, not rework.
The recurring ones are under-budgeting audio, forgetting storage and a retention plan, skipping the control-room sightlines, treating AV as a finish item instead of a rough-in trade, and choosing a capture platform before the rooms are designed around it. Each is far cheaper to avoid on paper than to fix after the room is built.
Planning a lab, or pricing one for a client? The method shown throughout this page — read the drawings, scope the capture, document it for the trades — is the work we do for simulation programs and integrators nationwide. Independent and manufacturer-agnostic, led by a Crestron Master Programmer. Talk through a project →
The rooms where scenarios run. We place cameras, microphones, and patient-monitor capture so the full encounter records cleanly from several angles.
The operator position, usually behind one-way glass. We design clean sightlines, an ergonomic control layout, and recording monitors so one person can run the whole session.
Where faculty review footage with students. We route any camera angle and the vitals feed into the debrief room for side-by-side review and discussion.
Smaller spaces for procedural practice. We scale capture and recording to fit a single station or rows of trainers without over-building the room.
Multi-station exam setups where each station needs its own camera, audio, and recording. We design the capture and routing so every station records on its own and reviews together.
Spaces for larger cohorts to watch a live scenario or review a recorded debrief. We feed clean audio and video from the simulation rooms to the gallery displays.
Exam-style rooms for encounters with standardized patients. We design discreet capture and intercom so the encounter feels natural while it is fully recorded.
Whole centers with many rooms feeding shared control and storage. We design the recording network, routing, and operator workflow so a small team can run the building.
Every project ships with construction documents: camera placement, conduit and power, control-room wiring, equipment racks, and cable schedules your trades and capture vendor can build from.
