Abstract

BackgroundDifficulties have been reported in patient distribution during mass-casualty incidents (MCIs). In this retrospective, descriptive study, the regional Patient Distribution Protocol (PDP) and the management of the patient distribution after the Turkish Airlines airplane crash on 25 February 2009 near Schiphol Airport in Amsterdam were analyzed.MethodsAnalysis of the of PDP involving the 126 surviving victims of the crash, by collecting data on Medical Treatment Capacity (MTC), number of patients received per hospital, triage classification, Injury Severity Scale (ISS) score, secondary transfers, distance from the crash site, and critical mortality rate.ResultsThe PDP holds two inconsistent definitions of MTC. The PDP was not followed. Four hospitals received 133–213% of their MTC, and five hospitals received one patient. There were 14 receiving hospitals (distance from crash: 5.8–53.5 km); thre hospitals within 20 km of the crash did not receive any patients. Major trauma centers received 89% of the “critical” casualties and 92% of the casualties with ISS score ≥ 16. They also received 10% of “minor” casualties and 29% of casualties with ISS score < 8. Only three patients were secondarily transferred, and no casualties died in, or on the way to, the hospital (critical mortality rate = 0%).ConclusionsPatient distribution was effective, as secondary transfers were low, and the critical mortality rate was zero. The regional PDP could not be followed during this MCI. Uneven casualty distribution was seen in the hospitals. The regional PDP is inconsistent, and should be updated in a new cooperation between Emergency Services, surrounding hospitals and vSchiphol Airport, a high risk area, for which area-specific PDPs must be designed.

Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.