Lynn Boergerhoff
Abstract
Trauma is a leading cause of death and disability in the United States. Planning a State-wide trauma care system begins with understanding the relationship between serious injuries and available trauma care resources. These multidisciplinary healthcare resources include injury prevention programs, emergency medical services, acute care hospitals, rehabilitation, and data for performance improvement and research. We describe how Hennepin County Medical Center, a Level I Trauma Center in Minneapolis, Minnesota, uses ArcView GIS to create an atlas of Minnesota's trauma care resources, to help develop an injury surveillance system, and to explore the spatial availability and use of trauma care resources.
Introduction
Trauma, or injury, is the leading cause of death for Americans under age 40 and the third leading cause of death overall after cardiovascular disease and cancer. The burden of injury often surpasses acute clinical care to involve a lifetime of recovery and rehabilitation, especially in head and spinal cord injuries. Generally, injury is damage to the body caused by exchanges with environmental energy that are beyond the bodys resilience, resulting in fractures of bones, tearing of skin, muscle, and organs, and the often life-threatening bleeding that follows. Mechanical energy, released in motor vehicle crashes, falls, and being struck by objects (including bullets) accounts for most fatal and severe trauma. Thermal, chemical, and electrical energy sources also cause injury. Injury epidemiology attempts to study the distribution and characteristics of injuries among a population in space and time, intending to identify causes and risk factors to effectively reduce injury incidence and severity.
Persons with severe injuries require access to a comprehensive trauma care system in which a continuum of multidisciplinary resources provide appropriate, capable, and coordinated medical care within the "Golden Hour" immediately after injury occurs. At the core of this continuum are two essential components: 1) prehospital emergency medical services (EMS) including 911 emergency telephone access and rescue squads and ambulance services whose firefighters, Emergency Medical Technicians, and paramedics respond to the injury scene to expedite treatment and ambulance transport; and, 2) acute care hospitals (particularly trauma centers) where emergency physicians stabilize and surgeons repair damaged body structures and where multidisciplinary teams in critical care units manage complex, multi-organ system injuries. Other trauma care system components, described by the American College of Surgeons (ACS) and others, include enabling legislation, lead agency oversight, injury prevention programs, rehabilitation services, and information systems with data for system evaluation and performance improvement, injury surveillance, and research.
Trauma occurs in spatial distributions shaped largely by where, when, and how people live, work, travel, and recreate. Geography, demographics, economics, politics, and a variety of other influences shape the distribution of the components of a trauma care system and may significantly effect a severely injured person's access to its services. This paper presents the use of ArcView GIS (Esri, Inc., Redlands, California) to integrate and visualize data on multidisciplinary trauma care resources and on fatal and severe motor vehicle crashes and to explore their interrelationships using common GIS spatial analysis methods.
Methods
Obtaining Spatial Data Files
To map the distribution of various trauma care resources and motor vehicle crashes, three types of spatial data were needed: named point locations of Minnesota cities; center-lines for state roadways; and named areas for Minnesota state, counties, cities, and townships. The roadway and area spatial data files were obtained from the Minnesota Department of Planning's CD titled Basemap 99 (1999). The city points were obtained from the Department's Land Management Information Center (1999). These files were readily available at no cost and provided in .dbf format.
Obtaining Attribute Data on Trauma Care Resources
Attribute data describing important characteristics of the trauma care resources were obtained from several administrative databases in Minnesota (Table 1). Each data file included a location identifier field, for example a city or township name, to enable geocoding against the Basemap 99 spatial data files. These files were readily available at no cost and provided in .dbf or convertible format.
Table 1. Description, sources, and data elements of selected trauma system components and other project-related data.
Trauma System Component |
Resource |
Description |
Data Source And (Year) |
Data Elements |
Prehospital Emergency Care |
911 Public Safety Answering Point (PSAPs) |
911 PSAP and area from which 911 telephone calls are received |
Minnesota Department of Administration (2000) |
|
Prehospital Emergency Care |
Fire Department Rescue Squad |
Minnesota rescue squads are usually fire department-based and respond to trauma and medical emergencies, usually arriving before the ambulance with special crash rescue equipment. |
Minnesota Arrowhead EMS Region, one of Minnesota's 8 multi-county EMS Regions (1999) |
|
Prehospital Emergency Care |
Ground and Air Emergency Ambulance Service |
Basic Life Support (BLS) ambulance personnel provide general emergency medical care and ground transport. Advance Life Support (ALS) ambulance service paramedics provide more advanced emergency medical care and ground transport. Helicopter air ambulance personnel, usually critical care nurses and paramedics, provide the most advanced prehospital care and the most rapid transport by helicopter. |
Emergency Medical Services Regulatory Board, Minnesota Department of Health (1999) |
|
Acute Care Facility |
Licensed Acute Care Hospital |
All Minnesota hospitals offer some level of emergency care. Four hospitals have developed the most advanced trauma care capabilities and have been verified by the American College of Surgeons as Level I, a region-wide resource hospital serving a population-dense area and able to manage the most severe trauma. Two hospitals are Level II, providing advanced trauma care and referral to Level I as needed for complex injuries. |
Facility and Provider Compliance, Minnesota Department of Health (2000), American College of Surgeons (2000) |
|
Acute Care Facilities |
Practitioner Trained in Trauma Care |
Physician, nurse, or other medical personnel trained in trauma care in the Comprehensive Advanced Life Support (CALS) course |
Minnesota Academy of Family Practice (2000) |
|
Rehabilitation Services |
Injury Rehabilitation Program |
Rehabilitation program providing therapeutic services to persons recovering from severe injury |
Minnesota Head Injury Association (1999) |
|
Injury Prevention Program |
Child Passenger Protection Program |
Child Passenger Safety Training class trains persons to inspect and install child passenger safety seats in motor vehicles. Persons drive their vehicles with car seats to "Car Seat Clinics" for inspection. |
Office of Traffic Safety, Minnesota Department of Public Safety (2000) |
|
Information Systems |
Hospital Trauma Registry Database |
Some Minnesota acute care hospitals maintain a Trauma Registry, an injury database, with patient, injury type and severity, treatment, and outcome data
|
Minnesota Trauma Registry Alliance (2000) |
|
Trauma Care Related |
Healthcare Professional Shortage Area (HPSA) or Medically Underserved Area (MUA) |
Some Minnesota cities and townships are designated HPSA or MUA by the Minnesota Department of Health as lacking certain healthcare resources. |
Office of Rural Health and Primary Care, Minnesota Department of Health (1999) |
|
Trauma Care Related |
Population Estimate |
Estimated total population of Minnesota cities and townships |
Office of the State Demographer, Minnesota Department of Planning (1998) |
|
Obtaining Data on Fatal and Serious Motor Vehicle Crashes
When a motor vehicle crash is reported to a law enforcement agency in Minnesota, the responding officer completes a standardized motor vehicle accident report form. The report is submitted to the Minnesota Department of Public Safety (DPS) where the data is abstracted and entered into a database organized into three files, each containing an accident number as a common field to enable linking of the files. The crash file contains data about the crash event, including the date, time, type of crash, and roadway location. The vehicle file holds data on each vehicle involved in the crash. The person file contains data on each person involved in the crash, including their age, vehicle entrapment or ejection, injury severity, and transport to a hospital. The files contain other trauma-related data not obtained for this project. Together, these files form a hierarchical relationship of a person in a vehicle involved in a crash event. Tables 2 and 3 describe the data obtained for this project from the DPS crash and person files respectively.
Table 2. Data in the Motor Vehicle Crash File
Data Element |
Description |
Data Format |
Example |
Accident ID Number |
Unique 9-digit number identifying the crash event (yydddnnnn format) |
9 character text string |
Crash # 991230456 (Read as: crash #0456 occurred on the 123rd day of 1999) |
Route Identification |
Unique 10-digit number identifying the roadway route system |
10 character text string |
Crash # 991230456 occurred on route 0600000014 |
Beginning Point |
Distance measurement of crash scene location along the roadway system from a reference point |
Number |
Crash # 991230456 occurred on route 0600000014 at location 147.235 |
Crash Severity |
Most severe injury caused by this crash event. Crashes are coded as "K" for killed, "A" for severe injury, "B" for minor injury, and "C" for possible injury.
|
1 character text |
Crash # 991230456 was coded "K" (a fatal crash because at least 1 person died) |
Table 3. Data in the Motor Vehicle Person File.
Data Element |
Description |
Data Format |
Example |
Accident ID Number |
Unique 9-digit number identifying the crash event |
9-character text string |
Crash # 991230456 |
Vehicle Number |
Numbers 1, 2, 3, etc. assigned to each vehicle involved in the crash |
1-digit text |
Crash # 991230456 involved two vehicles: # 1 and # 2. |
Person Number |
Numbers 1, 2, 3, etc. assigned to each person occupant in each vehicle involved in the crash |
1-digit text |
In crash # 991230456, vehicle # 1 had two occupants (persons # 1 and # 2); vehicle # 2 held only one occupant (person # 1). |
Person Injury Severity |
"K" or "A" code assigned to each person in each vehicle |
1-digit text |
In crash # 991230456 vehicle # 1, person # 1 was coded "A" and person # 2 was coded "K." |
Person Ejected |
2-digit codes assigned to each person in each vehicle. Code "01" if person was trapped in the vehicle and required extrication; code "03" if person was ejected from the vehicle during the crash |
2-digit text |
In crash # 991230456 vehicle # 1, person # 2 was coded "03" (ejected from the vehicle). In vehicle # 2, person # 1 was coded "01" as trapped in the wreckage and requiring extrication. |
Person Transported to Hospital |
"Y" for yes and "N" for no assigned to each person involved in the crash to identify whether the person was transported to a hospital |
1-digit text |
In crash # 991230456, all persons were coded "Y" (transported to a hospital). |
Person Age |
Age in years of each person involved in the crash |
2-digit text |
In crash # 991230456, vehicle #1, person # 1 was 17 years old and person # 2 was 18 years old; in vehicle # 2, person # 1 was 42 years old. |
Only crashes with injuries coded as "K" or "A" for September and October 1999 were obtained for this project. The crash and person data files were received in .dbf format and imported into Microsoft Access (Microsoft Corporation, Redmond, Washington) where the two files were joined on the common field, Accident Number. The crash location indicators (Route Identification and Beginning Point) were retained in each record to enable geocoding of crashes against the roadway files in Basemap 99.
Questions of Interest
Three ACS recommended guidelines were used to identify persons in fatal and severe crashes who may need care in a Level I or II trauma center. Ambulance personnel may use these guidelines together with assessment of anatomic injury and physiologic status to triage the person to determine transport to the most appropriate receiving hospital. Queries were developed in Microsoft Access to select persons meeting one or more of these characteristics:
In addition, queries were developed to identify several characteristics of fatal and severe crashes and the persons involved that were of interest from trauma system perspective:
Four steps were necessary to visualize the spatial distribution and characteristics of trauma care resources and motor vehicle crashes using ArcView GIS. First, the trauma care resources data files were prepared in .dbf format and queried in a relational database to identify crashes with characteristics of interest. Next, the trauma care resources data, the selected crash data, and the appropriate spatial data were added as themes to a view. Third, the data tables of both resources and crash attribute themes were geocoded on the common location identifier field in the spatial themes as either a city or roadway crash location point, or as a city or township area. Finally, the resulting maps were modified with the Legend Editor and Color Palette for best visualization of the characteristics of interest and prepared as a layout for printing.
Results
Visualizing and Exploring the Relationship of Trauma Care Resources and Motor Vehicle Crashes
Of 594 "K" and "A" crashes obtained from the Department of Public Safety, 161 (29%) could be readily geocoded against the Basemap '99 roadway files and were used as the sample of crashes in this project. These crashes occurred exclusively on interstate and Minnesota trunk highways. The remainder of the crashes occurred on other roadways including state-aid highways, county roads, township roads, city streets, and other locations. These crashes would have required manual geocoding and were excluded from this demonstration project.
Themes from the trauma resources and motor vehicle crashes were combined using the spatial analysis capabilities regarding proximity and containment to explore the relationships among the sample of fatal and severe motor crashes and trauma care resources. A series of maps were created of the trauma care resources and motor vehicle crashes to address each of the questions of interest regarding the relationship of crashes to trauma care resources. Two questions and their spatial analysis methods are presented here as examples. Both are questions of spatial relationship called containment, in which features (e.g. points) are inside other features, typically areas. The first question asks which crashes occurred inside or outside the paramedic ambulance service areas. To answer this question, the Select by Theme option was used to select crashes (from the Crash theme) that are within the paramedic service area (from the Ambulance Area theme). A second operation selected those crashes outside the ALS ambulance service area. A map showing the distribution of Minnesota's licensed ambulance services and motor vehicle crashes appears in Figure 1. The second question asks which crashes occurred within the 15 and 30 miles of a Level I or Level II trauma center. To answer this question, two concentric buffers 15 miles apart were created around the hospitals with ACS Level I and Level II trauma center verification using the Create Buffers option. These buffered areas were then used to select crashes within the specified distance of a Trauma Center. A map showing the buffered Trauma Centers and the fatal and severe motor vehicle crashes appears in Figure 2.
Using GIS to Enhance Public Health Injury Surveillance
GIS may be used to monitor the incidence and characteristics of motor vehicle crashes (and other types of injury events) over time to enhance public health injury surveillance systems. Public health injury surveillance is the ongoing and systematic collection and analysis of data describing the incidence and characteristics of injuries in a described geographic area and time period. GIS is well suited to managing and integrating the data needed to describe the who, what, when, where, and how of injuries needed for injury surveillance. These injury data may then be integrated with data describing demographic, housing, socioeconomic, and other community and environmental characteristics to help identify persons, times, and places that may be at risk of certain types of injury and useful in planning, delivering, and evaluating injury prevention programs. For example, GIS could easily locate crashes causing injury to unrestrained children to help target child passenger protection programs. GIS may then be used to display this information in maps to better inform professional and public audiences with shared interest in injury prevention.
Summary
ArcView GIS is a powerful tool to integrate and manage data from multidisciplinary trauma care resources and from motor vehicle crashes. In addition, GISs spatial analysis capability enables the exploration of the relationships between crashes and trauma care resources to better inform discussions of the current and desired characteristics of a comprehensive trauma care system. Finally, GIS is a useful enhancement of public health injury surveillance systems.
Lynn Boergerhoff
Trauma Services
Hennepin County Medical Center
701 Park Ave
Minneapolis, MN 55455