Shipwizeshipwize
augmented-communicationcompliance

Medical Incident Communication on Cruise Ships: A Step-by-Step Protocol

Shipwize5 min read

The Medical Incident Challenge

A medical incident on a large cruise ship involves coordination between: the reporting crew member, the nearest qualified first responder, the ship's medical officer, the bridge (master and officer of the watch), passenger relations, and potentially shore-side medical consultation.

In a conventional setup, this coordination happens through a combination of PA announcements, radio calls, phone calls, and informal messages. Each channel is independent. There's no central record. The master may not have a complete picture of response status.

Augmented Communication handles this as a structured incident workflow.

The Initial Trigger

A medical incident can be triggered in several ways:

  • Crew member creates an incident from the communication app (takes 30 seconds)
  • Passenger calls crew services line (automatically creates an incident)
  • Crew medical officer activates from the medical centre console
On trigger, the platform immediately:
  • Creates a structured incident record with timestamp and location
  • Determines on-duty first responder based on current watch assignment and position
  • Sends targeted push notification to that crew member
  • Notifies medical officer
  • Notifies bridge watch officer
  • No PA announcement shouting to all 2,000 people. A precise, role-targeted notification to the people who need to act.

    The Push Notification Content

    The push notification received by the first responder includes:

    > [MEDICAL] Deck 12, Cabin 343 > Passenger health incident. You are the nearest crew member. > Respond → Delegate → Can't respond

    The notification contains enough context for the crew member to understand their role without opening the app. One tap to confirm response. The medical officer and bridge see the acknowledgement in real time.

    Escalation Handling

    If the first responder doesn't acknowledge within 60 seconds, the platform automatically escalates to the secondary responder. If neither responds within 120 seconds, the bridge watch officer is alerted to intervene.

    This automatic escalation eliminates a critical gap in conventional notification: the uncertainty of whether the notification reached and was seen by the right person.

    Multi-Party Coordination

    Once the initial response is confirmed, the platform opens a structured incident channel:

    • First responder (at scene)
    • Medical officer (may be remotely advising or en route)
    • Bridge watch officer (monitoring)
    • Master (if severity warrants)
    All communications in this channel are automatically logged to the incident record. When the medical officer requests a patient history update, the request and response are both captured. When the master decides to divert to a nearby port, the decision is logged with timestamp.

    Telemedicine Integration

    For medical situations requiring specialist input, the platform connects the medical officer with shore-side telemedicine services via WebRTC video call. The call can be initiated from within the incident channel.

    The telemedicine session — timing, participants — is automatically linked to the incident record.

    Resolution and Compliance Record

    When the medical officer marks the incident resolved, the platform generates a structured incident summary:

    • Incident ID and timestamp
    • Location
    • Initial reporter
    • First responder (with acknowledgement time)
    • Medical officer involvement
    • Communication record (all messages, all acknowledgements)
    • Resolution timestamp and outcome
    This summary is the compliance record. It can be exported for the ship's medical log, the flag state reporting system, or port authority inspection.

    Generating this record requires no manual data entry — it's automatically assembled from the communication log.

    Response Time Improvement

    The measurable improvement from structured Augmented Communication versus conventional alerting is primarily in response time. In conventional alerting:

    • Alert created (90 seconds — PA, radio call to bridge, bridge calls medical)
    • First responder notified (additional 60–120 seconds of phone calls)
    • Bridge confirms response status (follow-up call required)
    With Augmented Communication:
    • Alert created (30 seconds in the app)
    • First responder notified (under 5 seconds via push)
    • Bridge has acknowledgement status (real-time, no calls required)
    For cardiac events where survival rate decreases measurably with each minute of response delay, this improvement is clinically significant.

    See Shipwize in Action

    Experience offline-first maritime communication and Augmented Communication live.

    Request a Demo