Code Blue and critical teams: mobilizing and auditing the response

Published on November 7, 2026 · 6 min read

What a Code Blue demands of whoever activates it

A Code Blue is usually called for a cardiac arrest. Whoever activates it has to call the right team, with the roles the protocol asks for, and has to know who accepted and who is on the way. Afterward, the hospital wants to know what happened and how long it took.

Without a system, this depends on extensions, phone calls and the memory of whoever was on shift. TRR, the SigaME module for critical clinical responses, organizes this mobilization for Code Blue and for the hospital's other protocols.

What the hospital configures beforehand

TRR works with a configuration per code. Each code gets the time limit to form the team, the arrival time limit, the required and desired roles (physician, nurse, physical therapist, elevator operator) and the backup call. Codes and colors follow each hospital's protocol, and Code Yellow, Code Orange, sepsis and stroke are configured the same way.

From activation to closing

Activation can be done from the platform screen, from a call point at the bed or in the room, or by extension and an integrated nurse call system. At the call point, the professional uses the badge and holds the button for 5 seconds. From there:

1. The team forms. The system calls one professional per role, prioritizing the backup and the highest-priority team for the code.
2. The alert reaches the eCom. An +80 dB sound alarm, vibration and the code color, with the option to accept or decline.
3. Escalation runs on its own. If the professional declines or does not answer, the system calls the next one.
4. Arrival is recognized. By the eCom location. Without location, it is done by confirmation.
5. The event is closed. By the closing professional, by the console with a justification, or automatically.

What gets recorded

TRR produces reports with confirmation, arrival and response times, per event and per professional. A TV panel shows the active events, and the full trail is kept for 5 years.

Team managers follow the events, shifts and alerts of their teams. Operational alerts warn of an incomplete team on shift, an eCom out of the area, without coverage or with low battery, and a base without communication, that is, problems that can be fixed before a call.

Location with privacy

TRR uses the location only of the professionals who were called and only during the event. There is no free search and no history of where the team has been, which reduces exposure of personal data and supports compliance with the LGPD.

The eCom also has a panic button, which sends an immediate alert to the managers with the location, without opening an event.

What TRR does not promise

TRR mobilizes and records. It does not provide the care, does not define the clinical protocol and does not replace the team's judgment. The hospital decides what each code requires, and the system follows that configuration.

It also does not promise clinical results. What the hospital gains is safety in activation, standardized protocols, fewer communication failures and a complete record of events.

Flow and TRR do not mix. Flow organizes operations, such as taking a stable patient to the CT scan, and TRR coordinates critical clinical responses. One eCom serves one module at a time, and each module has its own teams and shifts.

Where to start

The conversation starts with the hospital's codes and protocols. A few questions help prepare the configuration:

1. Which codes does the hospital use, and with which colors? Each one gets its own configuration.
2. Which roles must be present in each code? Required and desired roles are defined separately.
3. Who is responsible for shifts and teams? Team managers follow the events and the alerts.