Ship Doctor Interview Questions
& Operational Answers

I would confirm cardiac arrest, initiate CPR, and send for the AED and medical team. Once the defibrillator arrives I follow the ALS algorithm — rhythm check, shock if shockable, adrenaline every 3-5 minutes for non-shockable rhythms. I would establish IV access, secure the airway with an iGel or intubation if trained, and continue cycles. If ROSC is achieved, I initiate post-resuscitation care with monitoring in the medical centre. I would arrange telemed consultation and consider whether the patient needs evacuation.

Simultaneously with ALS, I am running a parallel operational track. Within the first 5 minutes I direct my nurse to pull the oxygen audit — how many D-cylinders are charged, what is our burn rate at 15L/min through a non-rebreather, and how many hours of supply that gives us. That number determines my escalation timeline.

I have a crew member control the scene — move passengers, clear a path to the medical centre, and confirm stretcher access through the nearest elevator. While CPR continues, I send an SBAR-M to the bridge:

If ROSC is not achieved after 30 minutes, I am not just thinking about termination — I am considering who makes the pronouncement documentation, which flag-state death-at-sea protocol applies, and whether I need to brief the Captain on passenger relations and next-of-kin notification procedures before the next port.

The clinical algorithm is the floor. The operational context — oxygen endurance, medevac window, bridge communication, and documentation under maritime law — is what the interviewer wants to hear.

I use SBAR to communicate with the bridge. I give the Situation, Background, Assessment, and Recommendation in a concise format. The Captain needs to know the severity of the case, whether the patient needs evacuation, and if there are any changes needed to the ship's itinerary.

The Captain is not a clinician. Telling them "the patient has a STEMI" is meaningless. What the Captain needs is a decision framework expressed in operational terms. I use SBAR-M, and the critical addition is the M — Maritime Context.

The Captain needs three things from me: what is at risk (life, limb, or stability), what I can sustain (how long my resources last against the clinical trajectory), and what I recommend (continue, divert, or evacuate — and the time window for each).

Notice there is no diagnosis in that communication. There is risk level, resource endurance, a recommendation, and a reassessment timeline. That is bridge command translation — the language that converts clinical findings into navigational decisions. Interviewers who hear this know you understand the command hierarchy.

I would monitor the patient's SpO2 and titrate oxygen to maintain saturations above 94%. I would check the available oxygen supply and calculate how long it will last at the current flow rate. If supply is limited, I would consider reducing the flow rate if the patient tolerates it and request evacuation if the oxygen may run out before we reach port.

This is a resource endurance problem, not a titration question. At 15L/min, a standard D-cylinder (340L) lasts approximately 22 minutes. An E-cylinder (680L) lasts about 45 minutes. The first thing I calculate is my total oxygen reserve in hours at current burn rate, then compare that to time-to-port.

If my oxygen endurance is less than time-to-port plus a 2-hour safety margin, I have a capability gap. I declare this to the bridge immediately using capability gap language:

Meanwhile, I implement a staged conservation protocol: Can I wean to 10L/min via Venturi and maintain SpO2 above 90%? Can I use CPAP to reduce FiO2 requirement? Is there an onboard oxygen concentrator as a backup for periods of stability? I document each titration step, the SpO2 response, and the revised burn rate.

The operational answer is not "titrate to sats." The operational answer is: know the number, know the deficit, communicate the gap, and implement a conservation strategy while the bridge solves the logistics. That parallel thinking — clinical care plus resource management plus bridge communication — is what distinguishes the maritime clinician.

I would request a medevac when the patient needs definitive care that I cannot provide onboard — for example, surgical intervention, advanced imaging, or ICU-level care. I would consider the clinical urgency, distance from shore, and whether the patient is stable enough to survive the transit time to port.

Medevac is not a clinical decision alone — it is a multi-variable operational calculation. I consider:

Clinical urgency: Is the patient's trajectory such that the condition will become irreversible within the transit-to-port window? A STEMI with ongoing chest pain has a different urgency from a stable fracture.

Resource endurance: Can my onboard supplies (oxygen, medications, monitoring capability) sustain the patient for the full transit? If not, when does the resource run out relative to arrival?

Helicopter operational factors: Range (typically 150-200 nautical miles offshore), weather and sea state (hoisting is not possible above Sea State 5-6), daylight requirements in some regions, and the fact that helicopter transfer itself carries risk — the patient must be stable enough to survive the winch.

Receiving facility capability: There is no point in a medevac to a coastal clinic without PCI capability if the patient needs a cath lab. I confirm the destination through TMAS or the P&I club.

The distinction is framing medevac as a resource-gap calculation with a clear recommendation, not simply "the patient needs a hospital."

I would suspect a gastrointestinal outbreak, likely norovirus. I would isolate affected crew members, collect stool samples, notify the ship's sanitation officer, increase hand hygiene measures, and report to the relevant public health authority. I would treat symptomatically with antiemetics and rehydration.

This is not just a clinical management question — it is a public health trigger with operational and regulatory consequences. My response has four parallel tracks:

1. Clinical: Symptomatic treatment, IV rehydration for severe cases, stool samples for virology. But I am also tracking the attack rate — 15 crew in 24 hours tells me the doubling time and whether this is point-source or propagated. If the curve is accelerating, I am escalating before it hits passengers.

2. Containment: Immediate crew isolation protocol. I work with the hotel director and HR to identify which departments are affected. If galley crew are involved, I am recommending a precautionary galley deep-clean and temporary staff redeployment. I notify the environmental health officer.

3. Regulatory: Under US CDC VSP rules, if the vessel is bound for a US port and the GI illness rate exceeds 2% of passengers or crew, I must report. I am calculating that threshold now. I also check flag-state and next-port-of-call notification requirements. Some ports require 24-hour advance notification of outbreaks.

4. Bridge communication:

The interviewer wants to hear that you understand outbreaks are not just about treating patients — they are about attack rate surveillance, regulatory thresholds, operational containment, and proactive bridge communication before the situation escalates to a port health intervention.

I would perform a rapid neurological assessment, check blood glucose, and treat this as a presumed stroke. I would contact TMAS for telemedicine consultation, monitor closely, and arrange evacuation to a facility with CT and thrombolysis capability. I would not give thrombolytics without imaging to exclude haemorrhagic stroke.

This question tests whether you understand time-critical decision-making under diagnostic uncertainty. The clinical clock is ticking — the thrombolysis window is 4.5 hours from onset — but I have no CT scanner to differentiate ischaemic from haemorrhagic stroke.

Immediate actions: ABCDE, glucose check (to exclude hypoglycaemia mimicking stroke), NIHSS or FAST score, ECG (AF as embolic source), BP measurement. I do NOT give aspirin yet — I cannot exclude haemorrhage.

The operational calculation: Symptom onset was 90 minutes ago. The thrombolysis window closes in approximately 3 hours. My question to the bridge is not "can we get to a hospital?" but specifically:

I contact TMAS immediately — not just for clinical advice, but to have them pre-alert the receiving facility so the CT scanner and stroke team are ready the moment the patient arrives. I am also documenting the exact time of symptom onset, the NIHSS score, and every intervention with timestamps — this documentation will be critical for the receiving team's decision to thrombolyse.

The distinction is understanding that in maritime stroke management, you are not treating the stroke — you are buying time and eliminating delays in the transfer chain so that someone with a CT scanner can treat it.

I document the patient's history, examination, diagnosis, treatment, and outcome in the ship's medical records. I ensure documentation is clear, contemporaneous, and complete. I also complete any required company incident reports and notify relevant parties such as TMAS or the patient's travel insurance.

Maritime documentation serves three masters simultaneously: clinical care, legal protection, and operational record-keeping. The difference from hospital documentation is that your notes may be reviewed by maritime lawyers, flag-state authorities, port health officials, P&I clubs, and coroners — not just by other clinicians.

Clinical documentation: Standard medical notes — history, examination, investigations, management, outcome. But I also document what was not available — "CT imaging not available onboard; clinical decision made without imaging based on examination findings and TMAS consultation." This protects you when the standard-of-care question arises.

Operational documentation: I record every bridge communication with timestamps. "1430 UTC — SBAR-M delivered to bridge. Recommendation: diversion to port X. Captain acknowledged." I document resource status: "Oxygen supply at time of event: 6 x D-cylinders. Consumption rate: 15L/min. Estimated endurance: 7.5 hours." This creates an objective record of the operational constraints under which decisions were made.

Regulatory documentation: Death certificates at sea follow flag-state requirements, not your home country's format. Infectious disease notifications have specific maritime reporting obligations. I know which forms are required by the company, the flag state, and the next port of call.

The principle is: document not just what you did, but why you did it, what you did not have, and who you told. If this case is reviewed 18 months later by a maritime lawyer, your notes should make the decision chain self-evident.

I would clean and irrigate the wound, assess tendon function, apply a sterile dressing, splint the hand in a position of function, start prophylactic antibiotics, update tetanus if needed, and arrange for the crew member to see a hand surgeon at the next port. I would document the injury and complete an incident report.

This is a capability gap scenario with a 72-hour endurance requirement. The tendon injury needs surgical repair, but I am 3 days from anyone who can do it. My job is to preserve the tendon for definitive repair and prevent complications over that transit window.

Immediate management: Thorough irrigation (at least 500ml saline under pressure), neurovascular assessment distal to the injury, assessment of which tendon is involved and whether there is partial or complete division. I photograph the wound before dressing for the receiving surgeon. I do NOT attempt primary tendon repair — that is a specialist procedure, and a failed onboard repair is worse than a delayed clean repair.

72-hour endurance plan: I close the skin loosely (or leave open with wet dressings if contaminated), splint in a position that takes tension off the affected tendon (wrist in slight flexion for flexor tendons), start co-amoxiclav, and schedule daily wound reviews. I create a specific monitoring plan: check for signs of compartment syndrome, infection, and neurovascular compromise every 8 hours.

Operational considerations: This is a work-related injury. I complete an incident report, document the mechanism (galley knife — was the crew member fatigued? Was it during routine work?), and notify the safety officer. Under MLC 2006, this crew member is entitled to medical care and may need repatriation for surgical follow-up. I brief the Captain on the likely need for crew sign-off at the next port.

I also contact TMAS or a hand surgery telemedicine service to confirm my splinting position and antibiotic choice, and to have the receiving hospital expect the patient with a tendon injury requiring delayed primary repair.

I would explain that the patient is seriously unwell and that there is a risk of deterioration. I would avoid giving a definitive yes or no and instead focus on what actions are needed — whether we need to divert, evacuate, or continue monitoring.

This question tests whether you can translate prognostic uncertainty into an actionable decision framework for a non-medical decision-maker. The Captain is not asking for a medical prognosis — they are asking whether they need to change the ship's course. Your answer must serve that purpose.

I would never answer "yes" or "no" to this question. Instead, I reframe it operationally:

This does three things: it acknowledges the gravity without making a prognostic commitment you cannot back up, it converts the question into a resource-and-time problem the Captain can act on, and it gives a clear recommendation with a decision deadline.

The trap in this question is getting drawn into clinical explanation. The Captain does not need to understand the pathophysiology. They need to know: what do I need to do, how soon, and what happens if I don't?

I would confirm the diagnosis clinically, start IV antibiotics (cefuroxime and metronidazole or similar), keep the patient nil by mouth, provide analgesia, and monitor for signs of perforation. I would contact TMAS and arrange evacuation as soon as possible. If the patient develops peritonitis I would manage conservatively with antibiotics and IV fluids until surgical care is available.

The Southern Ocean, 4 days from port. No helicopter range. No passing vessels. This is the purest form of the maritime medicine problem — you must sustain the patient beyond the point where, on land, they would already be in theatre.

Clinical management: IV access x2, IV antibiotics (I would use piperacillin-tazobactam if available for broad-spectrum cover), IV fluids, NGT if vomiting, urinary catheter for fluid balance monitoring, analgesia with morphine (and I document that analgesia does NOT mask peritoneal signs when given appropriately — this is a common misconception). Serial abdominal examinations every 4 hours with documented findings.

Endurance planning: I audit my antibiotic supply — do I have 4 days of IV piperacillin-tazobactam, or do I need to switch to an oral step-down earlier? I check my IV fluid stock. I check my morphine stock against projected requirements. I create a 4-day resource consumption forecast and identify which resource will run out first.

Deterioration planning: If the appendix perforates, my management shifts to abscess containment, not cure. I plan for potential sepsis management with my available vasopressors (if any), and I identify my ceiling of care. If the patient develops generalised peritonitis with septic shock, I must have an honest conversation with TMAS about what is realistically achievable onboard versus the clinical trajectory.

The interviewer wants to hear endurance planning, resource auditing, deterioration contingencies, and honest capability-gap communication — not just the antibiotic choice. This is the 72-hour maritime ICU doctrine in action.

I would ensure the patient has capacity to make this decision, explain the risks of refusing evacuation clearly, and document their informed refusal. I would ask them to sign a refusal-of-treatment form, continue monitoring them onboard, and inform the Captain of the situation.

This question sits at the intersection of clinical ethics, maritime law, and operational risk management. The answer involves multiple stakeholders and parallel obligations.

Capacity assessment: First, I formally assess capacity. Can the patient understand the information, retain it, weigh it, and communicate a decision? I document this assessment explicitly. If they lack capacity (due to illness, medication, or altered mental state), the framework changes entirely — I act in their best interest under duty-of-care principles.

If they have capacity: I explain the risks clearly and specifically — not "you might get worse" but "without the surgery you need, there is a significant risk of [specific consequence] within [timeframe]." I document the exact words I used and the patient's response. I have a witness present — ideally a senior officer. The patient signs a refusal form, and I document that they were "informed of the risk of death/serious harm and declined evacuation with capacity confirmed."

Operational layer: I inform the Captain, because a patient who refuses evacuation and subsequently deteriorates creates an ongoing operational liability. The Captain needs to know that there is a high-risk patient onboard who may require emergency intervention later. I also inform the P&I club through the company's reporting chain, because this is a potential future claim.

Continuing care: Refusal of evacuation does not mean refusal of all treatment. I negotiate a monitoring plan the patient will accept, set up clear escalation triggers, and document a contingency plan for if they deteriorate and lose capacity — at which point, the refusal may no longer apply.

The distinction is showing that you understand refusal at sea is not just a consent form — it is a chain of documented communication involving the patient, the Captain, the P&I club, and potentially the flag-state authority, all with medicolegal implications that extend well beyond the voyage.

A capability gap is when the patient's clinical needs exceed what I can provide onboard. For example, if they need a CT scan or surgery and I do not have those facilities. When I identify a capability gap, I would inform the Captain and arrange for the patient to be transferred to a facility that can provide the necessary care.

A capability gap is not a binary state — it is a dynamic, time-dependent relationship between three variables: the patient's clinical trajectory, the ship's available resources, and the time required to access definitive care.

The critical concept is that a capability gap can be current or predicted. A current capability gap means the patient needs something I do not have right now. A predicted capability gap means that, based on the clinical trajectory and my resource consumption rate, I will run out of a critical resource before the patient reaches definitive care. The predicted gap is the one that matters most, because it gives the bridge time to act.

In practice, I use capability gap language in every bridge communication where a resource deficit exists or is anticipated:

The power of this language is that it converts a vague clinical concern into a quantifiable, time-bound operational problem that the bridge can act on. It also creates a documented record that you identified and communicated the risk proactively — which is critical for medicolegal protection.

The Osolika Doctrine formalises this into a structured framework: Deterioration Loop, ORS levels, and the Capability Gap Speech. Understanding this language signals to an interviewer that you think like a maritime clinician, not a hospital doctor temporarily at sea.