> ## 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.

# Tumor boards and case review

> How a multidisciplinary team can use a persistent Coresee Room to keep imaging, pathology, notes and decisions together from one case conference to the next.

A tumor board brings together oncology, radiology, pathology and surgery around a single patient. Each specialist arrives with something different to show: a scan, a slide, a report, a note from the last review. The meeting works when everyone can see the same material and remember what was decided last time.

## Where continuity breaks

The material for one case often sits in several places. Imaging lives in one system, and everything else lands wherever the meeting tool and the inbox put it. When a case comes back for review, someone has to gather it all again. A specialist who missed the last meeting has to ask around to find out what was decided.

The team ends up rebuilding the case every time the meeting starts.

## A Room for each board

A Coresee Room stays open between meetings, so a standing board can have a workspace of its own.

**1. Create the Room**

Set one up for the board or the service line, and add your institution's logo and colors.

**2. Add the case material**

Upload imaging, pathology images, reports and reference documents into folders, organized the way your team already thinks about its cases. Playback runs up to 4K at 60 fps, and PDFs and images keep their full resolution.

**3. Invite the specialists**

Add everyone who needs to take part, including guests from other institutions. Hosts can hold outside participants in a waiting room until they are admitted.

**4. Review the case together**

Put up to 16 items on screen at once, such as a current CT next to a prior one, or a pathology image beside its report. Mark up findings live with the whiteboard overlay, and leave frame-accurate annotations on video.

**5. Leave it ready for next time**

When the meeting ends, the files, recordings, annotations and chat history stay in the Room. When the case returns, the team opens the same Room and the history is already there.

## Joining a case late

Someone who joins the board for the first time, or who missed the last review, can open the Room and read the discussion, watch the recording and look at the same images. They don't need a briefing from a colleague to catch up.

## Access and security

Hosts and co-hosts have full control of the Room. Participants and guests have limited access. A Room can be limited to people the host named in advance, or to people who have signed in. Coresee encrypts media in transit and encrypts files, recordings and chat at rest with AES-256.

> [!NOTE]
>
> Coresee is a collaboration workspace, and your PACS and EMR remain the system of record. Decide with your compliance and privacy offices what patient information goes into a Room, and apply the same policies you use elsewhere. Clinical and regulatory requirements for diagnostic use stay with your organization.

## Beyond tumor boards

The same setup works for other recurring multidisciplinary reviews, from cardiac and transplant conferences to cross-department working groups. Each one gets a Room, and the context builds up over time instead of starting again.

## FAQ

> [accordion] Do we have to move our imaging into Coresee?
>
> Coresee is where the team reviews and discusses the case. Your imaging and record systems stay as they are, and you decide which files go into a Room.

> [accordion] Can specialists from other hospitals join?
>
> Yes. Hosts invite them as guests and can hold them in a waiting room until they are admitted.

> [accordion] Who should own the Room?
>
> Usually the board's coordinator or a physician lead. Decide who hosts, who can invite others and how long you keep a case Room.

> [accordion] Where should we start?
>
> Pick one recurring board and run it in a Room for a few meetings. Once the team is comfortable, other conferences can follow.


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