Cruise Ship Port Health Authority Illness Notification Form

Submit it before arrival as soon as illness patterns are known and again if the situation changes materially before docking. The goal is to give the port health authority enough time to review the vessel's status and prepare any needed response. If your voyage is long or cases are evolving, use the form as a pre-arrival update rather than a one-time report.

It is usually completed by the ship's medical officer, designated reporting contact, or another officer responsible for public health reporting. The person submitting should have access to current case counts, symptom details, and the vessel's response actions. If multiple departments contribute data, one person should own the final review to avoid inconsistent entries.

Use it for any onboard illness pattern that may require port health review, especially when multiple passengers or crew share similar symptoms. The symptom categories and free-text description fields are meant to capture the pattern without forcing a diagnosis. If the situation is isolated and routine, only report what is necessary for the authority to assess risk.

No. This template is a notification and coordination form, not a clinical record or a full epidemiological investigation. It helps communicate the vessel's current status, but the port health authority may request additional documents, logs, or follow-up details. Keep the form focused on the minimum necessary information for operational reporting.

Collect only the fields needed for port health review, and avoid adding passenger names, room numbers, or other PII unless the authority explicitly requests them. The template already centers on counts, symptom categories, and response actions, which supports GDPR Article 5 data minimization and the minimum-necessary principle. If you add optional identifiers, make them clearly optional and explain why they are needed.

Common mistakes include leaving the symptom description too vague, forgetting to update onset dates, and marking every field required even when some details are not yet known. Another issue is failing to state what happens after submission, which can leave the reporting contact unsure whether follow-up is expected. The form should also avoid free-text where a date picker, numeric input, or multi-select would be more accurate.

Yes. You can add port-specific routing fields, internal incident reference numbers, or conditional logic for additional support requests. Keep the core structure intact so the report still contains vessel details, illness summary, care status, and response actions. If a port requires a different intake sequence, adapt the labels rather than changing the underlying reporting purpose.

It can be routed to email, a case management queue, or an internal audit trail after submission. Many operators connect it to a workflow that notifies the medical team, operations lead, and designated port contact. If you integrate it with other systems, preserve the submission timestamp and the final declaration so the report remains traceable.

Review the submission for completeness, confirm whether the port health authority needs follow-up, and update onboard records if the case count changes. If additional support is requested, assign ownership immediately so the vessel can respond before arrival. The template works best when submission triggers a clear internal next step, not just an inbox notification.