> ## Documentation Index
> Fetch the complete documentation index at: https://help.coresee.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Simulation

> How a simulation program can use a persistent Room to observe from every angle, debrief with evidence, and keep selected sessions for the next cohort.

A simulation scenario might run twenty minutes. Most of the learning happens in the debrief afterward, and the debrief goes better when everyone has seen the same thing.

## The limits of the control room

Most centers observe from a control room. It works, but faculty see one angle at a time, observers have to be on site, and the notes are whatever someone had time to write. Once the scenario ends, the record ends with it unless someone captured it separately.

Even when it is captured, the pieces drift apart. The recording sits in one place, while the instructor's feedback and the training materials end up elsewhere. Learners end up hearing a summary of what happened, and revisiting a lesson means hunting for the parts.

## One Room per cohort

A Coresee Room stays available between sessions. For simulation, that means each cohort can have its own Room for the whole program.

> [card] Create & Brand the Room
>
> Add your institution's logo and colors so learners know they're in the right place.

> [card] Upload materials and files
>
> Put briefings, checklists and reference media into folders. They'll be waiting before the first session.

> [card] Bring in the cameras
>
> Cameras in the simulation suite and procedure room join as inbound feeds. Up to 16 live sources fit side by side in the multi-view grid.

> [card] Invite faculty and learners
>
> Give each person the role they need. Faculty can be co-hosts.

> [card] Record the session
>
> A host starts the recording, and every attendee sees a consent prompt before it begins.

> [card] Debrief on the recording
>
> Play the session back in the same Room. Faculty add time-stamped annotations right on the video, and learners can return to them later.

## What faculty and observers see

The multi-view grid puts the bedside, the monitor and the room overview on one screen. Faculty and observers watch the same moment together. Playback runs up to 4K at 60 fps.

## Procedural education

The same Room works for teaching beyond simulation. Instructors can share surgical demonstrations and procedure videos at high resolution and discuss them with trainees, giving feedback in the same place. A learner who wants to revisit a technique opens the Room and finds the video and the instructor's notes together.

## What stays after the session

The Room keeps the full recording, the annotations, the folders of files and the chat history. Selected sessions can stay there as teaching material, so a learner's first scenarios sit next to their later ones and progress is easy to see.

## Roles and access

Hosts and co-hosts have full control. A Room can have any number of co-hosts, so several faculty can run sessions, and participants and guests have limited access. Hosts can mute microphones, turn off cameras, manage visibility and remove attendees.

## FAQ

> [accordion] Do I need to replace my cameras or AV setup?
>
> Cameras join the Room as[Inbound Feeds](https://help.coresee.com/inbound-feeds.md)

> [accordion] Do learners have to agree to be recorded?
>
> Every attendee sees a consent prompt before a recording starts. Your institution's own rules on recording learners still apply, so settle them before the first session.

> [accordion] How long do recordings stay in the Room?
>
> They stay until you remove them. Decide in advance how long to keep recordings and who clears them out.

> [accordion] Can we use real patient information in a scenario?
>
> Most simulation uses manikins or standardized patients. If a scenario involves real patient information, follow your organization's policy and check with your compliance office first.

> [accordion] Where should we start?
>
> Choose one cohort and one recurring session type, such as a weekly scenario and its debrief. Add more once the team is comfortable.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.