Rapid Response · Every responder, in view

When a hospital team is called, who has acknowledged?

Portuguese- and English-language software that connects a request for help in a hospital with the people on duty. Each person confirms for themselves, and the person who asked can see exactly who has.

Begin

Working software · Remote integration tested

Someone on a ward asks for the rapid response team. The alert goes out. Then the questions start: did it arrive, and who is coming?

When one person’s reply stands in for the whole team, nobody can tell who else is on the way. Rapid Response asks each assigned person to confirm, keeps reminding only those who haven’t, and shows the requester one card per person.

Try a sample request

One request. Two responders. Every answer visible.

Send it, then confirm as Responder A and as Responder B. Watch what the requester sees at each step.

Sample data · nothing is sent

The requester’s screen

Demo ward · Room 03

Ready to send

Reason: sample reason, from the hospital’s own list

Start the example to send this sample request to the two responders on duty.

The responders’ alerts

Responder AEnglish

Rapid response requestDemo ward · Room 03 · Sample reason

“I’m responding” confirms you received this request and are responding.

Responder BEnglish

Rapid response requestDemo ward · Room 03 · Sample reason

“I’m responding” confirms you received this request and are responding.

Reminders continue for anyone who hasn’t confirmed.

See the example as steps
  1. A request is sent from Demo ward · Room 03. 0 of 2 acknowledged.
  2. Responder A taps “I’m responding”. 1 of 2 acknowledged; Responder B is still awaiting confirmation, and reminders continue for B.
  3. Responder B taps “I’m responding”. 2 of 2 acknowledged: both responders have acknowledged.
  1. A request is sent from Demo ward · Room 03. 0 of 2 acknowledged.
  2. Responder A taps “I’m responding”. 1 of 2 acknowledged; Responder B is still awaiting confirmation, and reminders continue for B.
  3. Responder B taps “I’m responding”. 2 of 2 acknowledged: both responders have acknowledged.

Acknowledging confirms the request arrived and the person is responding. Arriving, giving care and closing the request are separate events.

Three people, one handoff

Who does what, and who sees what.

The requester

Asks, then sees each answer.

  • Scans the room’s QR code, or types the building, room or place
  • Picks a reason from the hospital’s own list
  • Needs no account and no phone number
  • Sees one card per assigned person: waiting, or confirmed
  • If nobody is on duty, the page says the team is unavailable

A responder

Confirms for themselves.

  • Starts and ends duty on the web, or with a short WhatsApp message such as ON DUTY or DE TURNO
  • Gets each alert in their own saved language
  • Taps “I’m responding” (in Portuguese, “Vou responder”) to confirm
  • Reminders continue only for teammates who haven’t confirmed
  • An optional WhatsApp call, only with the responder’s own permission

Hospital IT

Decides who, where and how.

  • Gives and removes each person’s access
  • Sets how many people can be on duty at once
  • Creates the rooms and prints their QR codes
  • Reviews a restricted history of events
  • Responder AOn dutyEN
  • Responder BOn dutyPT
  • Responder COff dutyPT

Where it stands

Built, deployed, and tested end to end.

Working software · Remote integration tested

The software is running and has been tested end to end from outside a hospital, in both languages. Before any hospital uses it, that hospital confirms its own room names, its location rules, its emergency fallback and the wording of its messages. Rapid Response adds to a hospital’s emergency procedures; it doesn’t replace them.