Cruise Ship Guest Illness and Injury Report Form

Use this template for guest illness, injury, or any onboard event that may require medical evaluation or reporting review. It is designed to capture the incident details, symptoms or injury mechanism, treatment provided, and whether the case may be reportable to VSP or port health authorities. If the event is minor but could change later, it is still worth documenting while the facts are fresh. This helps avoid gaps between the medical center, guest services, and operations.

A shipboard medical team member, guest services lead, or trained incident reporter should complete it as soon as practical after the event. The reporter role field should identify who observed the incident, who received the guest, or who entered the final record. If multiple people were involved, one person should own the submission and gather witness details rather than leaving the form partially filled out. Clear ownership improves follow-up and reduces duplicate records.

Complete a new report for each distinct guest illness or injury incident, even if the same guest is seen more than once for the same event. If the situation evolves, update the original record with follow-up notes instead of creating unrelated entries. This keeps the audit trail easier to review and prevents confusion about symptom onset, treatment timing, and reporting status. For recurring symptoms, note whether they appear linked to the same exposure or a separate event.

No. This template helps document the facts needed to decide whether reporting is required, but it does not replace the reporting process itself. The reportable_to_vsp and reportable_to_port_health fields support the decision, and the follow-up section should record what was submitted and when. If your shipboard procedures require escalation, use this form as the source record and complete the external reporting steps separately. Keep the language factual and avoid speculative conclusions.

Collect only what is needed for incident handling, medical care, and reporting review, in line with GDPR data minimization and the minimum-necessary principle. Avoid unnecessary PII, and do not add sensitive details that are not relevant to the incident. If a field is not needed for the specific case, leave it blank rather than forcing a response. This is especially important when documenting symptoms, exposure sources, or witness statements.

Common issues include vague symptom descriptions, missing onset times, and incomplete location details that make it hard to reconstruct the event. Another frequent mistake is marking every field required, which can slow reporting and encourage inaccurate entries. Teams also sometimes skip witness summaries or fail to note whether the guest was restricted from activity after treatment. The best records are specific, time-stamped, and limited to observable facts.

Yes. You can tailor incident types, treatment options, follow-up actions, and reporting fields to match your medical center workflow and shipboard escalation process. Conditional logic can hide injury-specific fields when the case is illness-only, and vice versa, so the form stays short and relevant. You can also add role-based routing for medical staff, guest services, or compliance review. Keep the core structure intact so incident records remain comparable across voyages.

It can be paired with incident logs, medical records, case management tools, and compliance workflows through integrations or exports. The submission notice and follow-up fields help create a clean handoff to the next team, whether that is medical, operations, or regulatory reporting. If your process uses an audit trail, this form should feed the same case ID or incident reference. That makes it easier to track actions without duplicating the guest story in multiple places.