Humanitarian Surgical Missions: Guidelines for Successful Anesthesia Support

Brian M. Fitzgerald, Christopher J. Nagy, Eric F. Goosman, Matthew C. Gummerson, John E. Wilson

Research output: Contribution to journalArticlepeer-review

1 Scopus citations

Abstract

Many anesthesiologists and CRNAs are provided little training in preparing for a humanitarian surgical mission. Furthermore, there is very little published literature that outlines how to plan and prepare for anesthesia support of a humanitarian surgical mission. This article attempts to serve as an in-depth planning guide for anesthesia support of humanitarian surgical missions. Recommendations are provided on planning requirements that most anesthesiologists and CRNAs do not have to consider on routinely, such as key questions to be answered before agreeing to support a mission, ordering and shipping supplies and medications, travel and lodging arrangements, and coordinating translators in a host nation. Detailed considerations are included for all the phases of mission planning: advanced, mission-specific, final, mission-execution, and postmission follow-up planning, as well as a timeline in which to complete each phase. With the proper planning and execution, the anesthetic support of humanitarian surgical missions is a very manageable task that can result in an extremely satisfying sense of accomplishment and a rewarding experience. The authors suggest this article should be used as a reference document by any anesthesia professional tasked with planning and supporting a humanitarian surgical mission.

Original languageEnglish (US)
Pages (from-to)56-62
Number of pages7
JournalJournal of special operations medicine : a peer reviewed journal for SOF medical professionals
Volume17
Issue number4
StatePublished - Dec 1 2017
Externally publishedYes

ASJC Scopus subject areas

  • General Medicine

Fingerprint

Dive into the research topics of 'Humanitarian Surgical Missions: Guidelines for Successful Anesthesia Support'. Together they form a unique fingerprint.

Cite this