Decompression sickness rates for chamber personnel: case series from one facility

During 2004, a case series of decompression sickness (DCS) meeting the definition of epidemic DCS was observed in the Shaw AFB Physiological Training Program. There were 10 cases of chamber-induced altitude DCS observed. Internal and external investigations focused on time, place, person, and enviro...

Ausführliche Beschreibung

Gespeichert in:
Bibliographische Detailangaben
Veröffentlicht in:Aviation, space, and environmental medicine space, and environmental medicine, 2009-06, Vol.80 (6), p.570-573
Hauptverfasser: Brandt, Megan S, Morrison, Thomas O, Butler, William P
Format: Artikel
Sprache:eng
Schlagworte:
Online-Zugang:Volltext
Tags: Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
Beschreibung
Zusammenfassung:During 2004, a case series of decompression sickness (DCS) meeting the definition of epidemic DCS was observed in the Shaw AFB Physiological Training Program. There were 10 cases of chamber-induced altitude DCS observed. Internal and external investigations focused on time, place, person, and environment. No temporal trend was observed. Chamber, masks, regulators, crew positions, and oxygen sources revealed no defects. Among the cases, mean age was 27 yr. Peak altitude in four cases was 35,000 ft and in the other six cases was 25,000 ft. Six had joint pain, one skin symptoms, and three neurological findings. Four were treated with 100% ground-level oxygen and six with hyperbaric oxygen. Four were students and six were inside observers (IO). Four were women and six men. In the IO, where four of the six were women, no gender effect was seen. Examining the IO monthly exposure load (exposures per month) against DCS suggested a dose-response relationship. This relationship held true when 4 yr of Shaw AFB IO data was studied. Indeed, Poisson regression analysis demonstrated a statistically significant 2.1-fold rise in DCS risk with each monthly exposure. Consequently, the number of exposures per month may need to be considered when devising IO schedules.
ISSN:0095-6562
DOI:10.3357/ASEM.2438.2009