7/15/03 Association of Transportation Safety Information Professionals 1 Traffic Safety Information...

7/15/03 Association of Transportation Safety Information Professionals

1

Traffic Safety Information System Guidelines:

Improved Tools for Better Results

Disclaimer:Disclaimer:These Guidelines are a “Work in Progress”. The These Guidelines are a “Work in Progress”. The

information provided in this slide show, and the associated information provided in this slide show, and the associated Traffic Records Forum presentation are intended to Traffic Records Forum presentation are intended to

provide an overview of proposed Guidelines as developed provide an overview of proposed Guidelines as developed by ATSIP, under contract to NHTSA. Until such time as by ATSIP, under contract to NHTSA. Until such time as

NHTSA publishes the formal, final version of these NHTSA publishes the formal, final version of these Guidelines, users of this information should acknowledge Guidelines, users of this information should acknowledge that it represents the suggestions from the Association of that it represents the suggestions from the Association of Transportation Safety Information Professionals, and in no Transportation Safety Information Professionals, and in no

way represents a standard, or rule from the National way represents a standard, or rule from the National Highway Traffic Safety Administration or US-DOT.Highway Traffic Safety Administration or US-DOT.


2

Traffic Safety Traffic Safety Information Information

System System Guidelines: Guidelines:

Improved Tools Improved Tools for Better for Better Results Results

2003 Traffic Records 2003 Traffic Records ForumForum

Session 17Session 17July 15, 2003July 15, 2003

Vehicle

Roadway

ExposureDriver

Motor

CarrierInjury Enforcement

Adjudication

CRASH

ANALYSIS


3

Traffic Safety Information System (TSIS) Guidelines

Vehicle

Roadway

ExposureDriver

Motor


Adjudication

CRASH

ANALYSIS


4

As drafted by the

Association of Transportation Safety Information

ProfessionalsPresented By

Richard D. Paddock, PETraffic Safety Analysis Systems & Services, Inc.

Traffic Safety Information System

(TSIS) Guidelines


5


ATSIP was contracted, through the National Safety Council, to develop a set of criteria for the various components of a state or local TSIS.

These Guidelines are currently being incorporated and edited to become part of the new State Safety Data Improvement Program.


6

Guidelines for the Guidelines Criteria should be suggestive, not Criteria should be suggestive, not

prescriptiveprescriptive

Criteria should provide “discussion Criteria should provide “discussion points” during the development of a points” during the development of a TSIS Strategic Plan.TSIS Strategic Plan.

Guidelines should be based upon Guidelines should be based upon MMUCC, D16, D20, and general “best MMUCC, D16, D20, and general “best practices” in traffic records systems.practices” in traffic records systems.


7

The Guidelines Team Representatives from NSC, NHTSA, Representatives from NSC, NHTSA,

FMCSA, BTS and FHWA.FMCSA, BTS and FHWA.

Mixture of State representatives Mixture of State representatives from each of the major system from each of the major system groups.groups.

Representatives from the “user” Representatives from the “user” community.community.


8

The Development Process Several 2-day working meetings at Several 2-day working meetings at

NSC.NSC.

Extensive electronic exchange of Extensive electronic exchange of documents and ideas.documents and ideas.

Compilation into a “workbook” and Compilation into a “workbook” and a PowerPoint Slide Show.a PowerPoint Slide Show.


9


A Traffic Safety Information System (TSIS) encompasses the hardware, software, personnel and procedures that capture, store, transmit, analyze and interpret highway safety data.


10


TSIS Purpose:TSIS Purpose:Provide timely, accurate, and complete information on highway safety issues.


11

TSIS Characteristics:TSIS Characteristics:

1. Data from variety of sources

2. Data may originally be collected for purposes other than safety

3. Overlaps other areas of data collection


12

TSIS Characteristics TSIS Characteristics (Con’t.):(Con’t.):

3. Collaborative effort spread across number of agencies

4. Data must be timely, accurate & complete


13

Basic TSIS Components

Motor Carrier

Roadway Driver License

Enforcement /Prosecution / Adjudication

CrashInjury Control

VehicleRegistration

Data Analysis

Exposure


14


Vehicle

Roadway

ExposureDriver

Motor


Adjudication

CRASH

ANALYSIS


15


TSIS Guideline 1 Crash DataTSIS Guideline 2 Driver License DataTSIS Guideline 3 Vehicle Regist. DataTSIS Guideline 4 Roadway DataTSIS Guideline 5 Injury Control DataTSIS Guideline 6 Enforce. /Adjud./Pros Data

TSIS Guideline 7 Motor Carrier DataTSIS Guideline 8 Exposure DataTSIS Guideline 9 Data Analysis Process


16

TSIS GUIDELINE 1 –TSIS GUIDELINE 1 –

CRASH DATACRASH DATA


17


CRASH DATACRASH DATA


18

Vehicle Registration

Roadway

Exposure

Driver License

Motor Carrier

Injury Control

CRASH

DATA ANALYSIS

Enforcement / Prosecution / Adjudication


19

Crash Data ComponentCrash Data Component

What is a Crash Data What is a Crash Data Component?Component?1. Contains detailed information about motor vehicle crashes

2. Is the primary information used in traffic safety programs


20


What is a Crash Data What is a Crash Data Component?Component?3. Describes the crash event, its location, and its environment; as well as the persons and vehicles involved in the crash

4. Is the cornerstone of highway safety and injury prevention programs in all levels of government, as well as the injury control community and the private sector


21


Who Uses Crash Data?Who Uses Crash Data?•Local, state, and Federal agencies •Engineering and enforcement•Hospital injury control programs•Special interest groups •Insurance companies •Court system•Media•Highway Safety Offices


22


Characteristics of a Crash Data Characteristics of a Crash Data Component:Component:

1. Incorporation of a quality assurance process to assure that data is complete and accurate from the time of collection and throughout the processing of the data.


23



2. A consistently applied threshold for reporting crashes to the state custodial agency.


24



3. Efficiently designed to utilize resources for data collection, management, and use and not to duplicate the expenditure of those resources across jurisdictions or agencies.


25



4. Well-trained data collectors, managers, and users.

5. Flexible enough to accommodate changing needs and requirements in data collection.


26



6. Consistent input from a wide range of stakeholders

7. Structured to minimize or eliminate duplicate data collection efforts.


27



8. Consistent with published standards for reporting crash data.

9. Designed with the capability to support surveillance & trend analysis.


28



10. Provide a reliable basis for measurement of deaths, injuries and property loss.

11. Provide reliable and consistent location of crashes.


29



12. Consider for strategic planning the stakeholder business decision process with respect to collection, storage and distribution issues.


30



13. Engender a common sense approach to litigation, privacy issues, and staffing costs.


31



14. Provide a user-friendly mechanism for access to state crash data by local law enforcement, EMS, traffic engineers and others.


32


Functions a Crash Data Functions a Crash Data Component Should Support:Component Should Support:

1. Crash involvement posted to driver history

2. Crash involvement posted to carrier history

3. Linkage to EMS and other medical data for injury control analysis


33



4. Identification of high incident locations

5. Identification of vehicle defect problems

6. Engineering studies – traffic signal warrants, etc.


34



7. Selective enforcement programs

8. Injury prevention programs

9. Legislation & public policy

10. Programs and countermeasures related to driver behavior and education


35


What a Crash Data Component What a Crash Data Component Should Contain:Should Contain:

1. Information describing the crash event and its characteristics; e.g., weather, surface condition, time


36



2. The specific location where the crash occurred and links to other supplemental data sources


37



3. The environment surrounding the crash, including pre-crash and post-crash characteristics


38



4. The persons involved in the crash, their injuries, their characteristics, and their license status


39



5. Vehicles involved in the crash and their characteristics

6. Violations cited that might indicate culpability in the crash


40



7. A consistent reporting threshold that is low enough to include property damage only crashes


41


Examples of Questions a Crash Examples of Questions a Crash Data Component Should Be Able to Data Component Should Be Able to Answer:Answer:

1. What are the characteristics (time, weather, driver age, types vehicles, etc.) of most frequent types of crashes, including specific locations?


42



2. What population groups (age, gender, etc.) are associated with various crash frequencies?


43



3. What types of vehicles are most likely to be involved in crashes?

4. What types of “causes” are identified most frequently?


44


Examples of Questions a Crash Examples of Questions a Crash Data Component Should Be Able toData Component Should Be Able to Answer:

5. In crashes involving large commercial vehicles, what percent of time is the commercial driver “at fault”?


45



6. At what locations are roadway issues identified as factors?


46



7. What types of violations are drivers involved in crashes being cited for?


47


DRIVER LICENSE DRIVER LICENSE DATADATA


48


Roadway

Exposure

Driver License

Motor Carrier

Injury Control

CRASH

DATA ANALYSIS



49

Driver License Data ComponentDriver License Data Component

What is a Driver License What is a Driver License Data Component?Data Component?That combination of procedures and data systems that track the status of a driver license and any actions taken against that license.


50

Attributes of a Driver License Data Attributes of a Driver License Data Component:Component:1. Traffic offense conviction histories

2. Administrative actions

3. Driver demographics and residency

4. Information accessible from the field

5. Crash involvement



51

Attributes of a Driver License Data Attributes of a Driver License Data Component:Component:6. Pending actions (citation file)

7. Driver license agreement – state of record

8. All actions – including dismissals/ reductions (citation file)

9. Driver improvement and training/test results



52

Attributes of a Driver License Data Attributes of a Driver License Data Component:Component:10. Link to crash data file

11. Link to citation data file

12. Link to court and prosecutor automation

13. Driving related medical conditions and verification of impairment

14. Bar coding



53

Who Uses a Driver License Who Uses a Driver License Data Component?Data Component?

•Driver education community

•Researchers •Court systems•Law Enforcement



54

Characteristics of a Driver Characteristics of a Driver License Data Component:License Data Component:1. A complete record of licensure status showing dates when the status changed

2. All restrictions on operating privileges such as medical limitations or “only to work” restrictions.

3. A complete log of traffic offenses and the resulting penalties.



55

Characteristics of a Driver Characteristics of a Driver License Data Component:License Data Component:4. Log of all related training

5. Accurate information on the basic demographics of the driver including date of birth, ethnicity, residence.

6. Name changes, gender, physical attributes



56

Characteristics of a Driver Characteristics of a Driver License Data Component:License Data Component:7. Digitized driver license document that will support field retrieval of basic demographic information (e.g. bar coding or magnetic stripe encoding).

8. Mechanism for flagging “problem drivers”



57

Characteristics of a Driver Characteristics of a Driver License Data Component:License Data Component: 9. Mechanisms for the sharing and exchange of data between DMV, courts, and law enforcement



58

Questions a Driver License Data Questions a Driver License Data Component Should Be Able to Component Should Be Able to Answer:Answer:

1. Does the driver involved in a motor vehicle crash have a current driver’s license?

2. Does law enforcement have timely access to driver history information?



59


3. Is the driver’s class of licensure consistent with the vehicle being operated?

4. Does the driver license file include medical restrictions?



60


5. Does law enforcement have timely access to previous crash, citation and court information about the driver?

6. Does law enforcement have timely access to demographic and residency information about the driver?



61


7. At the time of a crash, does law enforcement have access to driver’s training including improvement / rehab courses and skills development, such as CDL training?



62


8. Can the court and prosecutors interpret the information to perform their functions?



63


VEHICLE VEHICLE REGISTRATION REGISTRATION

DATADATA


64


Roadway

Exposure

Driver License

Motor Carrier

Injury Control

CRASH

DATA ANALYSIS



65

Vehicle Registration Data ComponentVehicle Registration Data Component

What is a Vehicle Registration What is a Vehicle Registration Data Component?Data Component?• Captures title and registration information on all vehicles licensed in a jurisdiction.


66


What is a Vehicle Registration What is a Vehicle Registration Data Component?Data Component?• Includes information such as owner identification, vehicle description and identification, insurance carrier, title brands, odometer readings, sanctions, and vehicle incidents.


67


Who Uses a Vehicle Who Uses a Vehicle Registration Data Component?Registration Data Component?• State agency that is assigned the responsibility for issuing vehicle licenses

• Local law enforcement, court administrators, highway safety researchers, and various safety programs


68


Who Uses a Vehicle Who Uses a Vehicle Registration Data Component?Registration Data Component?• Motor vehicle manufacturers for vehicle recall purposes

• Federal and state highway safety officials to investigate vehicle design and operational safety issues (including NHTSA and FMCSA).


69


Who Uses a Vehicle Who Uses a Vehicle Registration Data Component?Registration Data Component?

• National Motor Vehicle Title Information System (NMVTIS).


70


Characteristics of a Vehicle Characteristics of a Vehicle Registration Data Component:Registration Data Component:1. Flexibility to respond to changing demands for information and information exchange.

2. Sufficient breakdowns in types of vehicles and location coding to know the number and types of vehicles in the jurisdiction.


71


Characteristics of a Vehicle Characteristics of a Vehicle Registration Data Component:Registration Data Component:3. Ability to link the crash with the vehicle registration files to supplement analysis and problem identification.

4. Retention of periodic or random safety inspections, where available, to be used for safety analysis.


72


Characteristics of a Vehicle Characteristics of a Vehicle Registration Data Component:Registration Data Component:5. Provide the basis for identification of vehicle ownership for manufacturer’s recall and other programs.

6. Timely update of data to assist law enforcement in identification of stolen vehicles and other investigations.


73


Characteristics of a Vehicle Characteristics of a Vehicle Registration Data Component:Registration Data Component:7. Identification of vehicle sanction information for appropriate enforcement and adjudication actions.

8. Identification of the cost, value, and/or extent of prior damage to a vehicle.


74


Characteristics of a Vehicle Characteristics of a Vehicle Registration Data Component:Registration Data Component:9. Identification of potentially unsafe vehicles through vehicle branding.

10. Use of vehicle odometer history information as an exposure base and for safety analysis relating to vehicle use.


75


Characteristics of a Vehicle Characteristics of a Vehicle Registration Data Component:Registration Data Component:11. Tracking of vehicle location information and using vehicle geographic exposure data in a comparative analysis between jurisdictions.

12. Commercial vehicle registration controlled by motor carrier safety compliance and drivers’ violation history.


76


Functions a Vehicle Registration Functions a Vehicle Registration Data Component Should Support:Data Component Should Support:1. Identification of the vehicle owner information (ID, address, type, home county)

2. A link to motor carrier data base and commercial vehicle safety data

3. A link to driver license operator


77


Functions a Vehicle Registration Functions a Vehicle Registration Data Component Should Support:Data Component Should Support:

4. Vehicle description

5. Link to crash data

6. Insurance carrier

7. Brands on title (salvage flood, etc.)


78


Functions a Vehicle Registration Functions a Vehicle Registration Data Component Should Support:Data Component Should Support:

8. Cumulative dollar value of damage to vehicle

9. History (registration, plate, crashes, safety inspection)


79


Functions a Vehicle Registration Functions a Vehicle Registration Data Component Should Support:Data Component Should Support:10. Integration with National Motor Vehicle Title Information System (NMVTIS)

11. Bar coding of registration document for easier roadside owner identification and data collection


80


Functions a Vehicle Registration Functions a Vehicle Registration Data Component Should Support:Data Component Should Support:12. Odometer information – particularly with registration and inspection renewals

13. Inspection/renewal history

14. Vehicle/owner sanctions including Ignition Interlock device history


81


What a Vehicle Registration Data What a Vehicle Registration Data Component Should Contain:Component Should Contain:1. Vehicle owner / operator information

2. Vehicle identification number

3. Link to a vehicle’s involvement in a crash

4. Vehicle safety inspection history


82


What a Vehicle Registration Data What a Vehicle Registration Data Component Should Contain:Component Should Contain:

5. Manufacturer’s recall

6. Sanction history

7. Titling history

8. Odometer history


83


What a Vehicle Registration What a Vehicle Registration Data Component Should Data Component Should Contain:Contain:9. Geographic exposure data

10. Vehicle type

11. Vehicle damage statement / cumulative damage info


84


Examples of Questions a Vehicle Examples of Questions a Vehicle Registration Data Component Registration Data Component Should Be Able to Answer:Should Be Able to Answer:

• Is registration for a specific vehicle currently valid?

• Do vehicles registered to certain owners have unusual amounts of damage reported?


85



• For large trucks and buses, what is the identification of the carrier(s) which will utilize the vehicle?

• What percentage of total registered vehicles are certain vehicle types (e.g., large trucks)?


86



• What vehicles/owners are involved in a manufacturer’s safety recall?


87


ROADWAY ROADWAY DATADATA


88


Roadway

Exposure

Driver License

Motor Carrier

Injury Control

CRASH

DATA ANALYSIS



89

Roadway Data ComponentRoadway Data Component

What is a RoadwayWhat is a Roadway Data Component?Data Component?


90

IncludesIncludes ROADWAYROADWAY::• LocationLocation• IdentificationIdentification• ClassificationClassification• Attributes Attributes (Next slide)(Next slide)

• Usage Usage (Traffic volume & (Traffic volume & mix)mix)

LRS - LRS - GISGIS


““Safety Safety Events”Events”


91

Roadway ATTRIBUTES Include:Roadway ATTRIBUTES Include:• Type• Surface type• Structures• Classification• Number of lanes• Geometrics• Railroad grade crossings• Traffic control devices• Appurtenances• Access control



92

Linear Reference Systems (LRS) Linear Reference Systems (LRS) Typical Formats:Typical Formats:• Route, Log MileageRoute, Log Mileage• Link-NodeLink-Node• Street, AddressStreet, Address• Point-OffsetPoint-Offset



93

Geographic Information System Geographic Information System (GIS) (GIS) ExamplesExamples of “Feature Layers”: of “Feature Layers”:• Political subdivision boundariesPolitical subdivision boundaries

• Rivers and lakesRivers and lakes

• RoadwaysRoadways

• Maintenance regionsMaintenance regions

• Location of law enforcement call boxesLocation of law enforcement call boxes



94

TSIS should be able to link Geographic TSIS should be able to link Geographic Information System (GIS) data with other Information System (GIS) data with other Systems such as:Systems such as:

• Injury data• EMS runs• Violation/citation data• Crash data• Roadway attributes• Travel• Demographics• Locations of medical or response resources



95

““Safety Events” Safety Events” Examples Include:Examples Include:• CrashesCrashes

• EMS Run Start PointEMS Run Start Point

• EMS Run Delivery PointEMS Run Delivery Point



96

IncludesIncludes ROADWAYROADWAY::• LocationLocation• IdentificationIdentification• ClassificationClassification• Attributes Attributes (Next slide)(Next slide)

• Usage Usage (Traffic volume & (Traffic volume & mix)mix)

LRS - LRS - GISGIS


““Safety Safety Events”Events”


97


Who Uses a RoadwayWho Uses a Roadway Data Component?Data Component?• Engineering groups are the primary users of roadway information systems.

• Most other users of the TSIS require the ability to accurately locate safety events (crash, citation, EMS runs, etc).


98


Functions a RoadwayFunctions a RoadwayData Component Should Support:Data Component Should Support: 1. Engineering design

2. Roadway Maintenance

3. Highway safety analysis

4. Planning

5. Roadway operations & traffic management


99


Functions a RoadwayFunctions a RoadwayData Component Should Support:Data Component Should Support: 6. Ability to locate positions on the roadway through some location reference coding scheme or geographic coordinates

7. Location-based analysis for all TSIS users

8. Multiple roadway synonyms (aliases) – and a mechanism to map the aliases to a preferred name.


100


Functions a RoadwayFunctions a RoadwayData Component Should Support:Data Component Should Support:

9. Quality assurance mechanism that will detect incorrect locations and make the appropriate changes.

10. MUST be mechanisms or tools in place to translate between various LRS and GIS systems and different reference standards.


101


Functions a RoadwayFunctions a RoadwayData Component Should Support:Data Component Should Support:11. Must be a methodology and policy/procedure for continuous update, and address history.12. System should be accurate at lowest level needed for safety analyses.13. Standard base data should be accessible by all users.


102


Functions a RoadwayFunctions a RoadwayData Component Should Support:Data Component Should Support:14. System should support dynamic segmentation within the GIS platform.

15. Capability to locate all crashes in state, regardless of highway type, on a common or compatible LRS.


103


What the RoadwayWhat the RoadwayData Component Should Contain:Data Component Should Contain: 1. Accurate, current and historical

traffic characteristics 2. Comprehensive inventories of

roadway attributes 3. Links into a comprehensive

pavement management system


104


What the RoadwayWhat the RoadwayData Component Should Contain:Data Component Should Contain: 4. Defined functional classifications to

group similar types of roadways for analyses

5. Ability to construct a physical map using geographical information systems

6. Video logging to provide visual evaluation of the roadway characteristics


105


What the RoadwayWhat the RoadwayData Component Should Contain:Data Component Should Contain: 7. All roads , irrespective of maintenance

responsibility 8. Sufficient resolution to support Highway

Safety analysis planning, problem identification, design

9. Maintain historical traffic counts and roadway realignments

10. Location information for all crashes reported in the state


106


Examples of Questions the Roadway Examples of Questions the Roadway Data Component Should Be Able to Data Component Should Be Able to Answer:Answer:• Which locations are candidates for

in-depth engineering safety review?

• Are specific roadways’ attributes appropriate to the vehicle mix, volume and speeds experienced on those roadways?


107


Examples of Questions the Examples of Questions the Roadway Data Component Roadway Data Component Should Be Able to Answer:Should Be Able to Answer:• What are the crash characteristics

and morbidity associated with various types of roadways?

• Are different communities experiencing different crash characteristics and/or morbidity?


108


INJURY INJURY CONTROL DATACONTROL DATA


109


Roadway

Exposure

Driver License

Motor Carrier

Injury Control

CRASH

DATA ANALYSIS



110

Injury Control Data ComponentInjury Control Data Component

What is an Injury Control What is an Injury Control Data Component?Data Component?Injury Control data document the medical and financial outcomes for persons injured as the result of a motor vehicle traffic crash.


111


Sources of Injury Control Data:Sources of Injury Control Data:• Medical records including EMS run reports, emergency department records, hospital/rehabilitation inpatient discharge data, death certificates and outpatient records,• Non-medical records such as crash , insurance claims, other traffic records, and roadway inventories.


112


CRASH RELATED DATAENVIRONMENT DATAENVIRONMENT DATA

CRASHEVENT

CRASHEVENT

EmergencyDepartmentEmergencyDepartment

HospitalInpatientRehab

HospitalInpatientRehab

EMSEMS

Clinic/HMOPhysician Office

Clinic/HMOPhysician Office

CLAIMSCLAIMS

Death CertificateDeath Certificate


113


Who Uses Injury Control Who Uses Injury Control Data?Data?• Public and private entities responsible for highway safety to target resources that will have a direct impact on reducing deaths, injuries, injury severity and health care costs caused by motor vehicle crashes.


114


Characteristics of an Injury Characteristics of an Injury Control Data Component:Control Data Component:1. Should promote standardization and collaboration among data owners adhering to published standards such as:

•Model Minimum Uniform Crash Criteria (MMUCC)•Uniform Prehospital EMS Data Set•Data Elements for Emergency Data Systems (DEEDS)•Uniform Billing 1992 (UB92)


115


Characteristics of an Injury Characteristics of an Injury Control Data Component:Control Data Component:2. Should promote uniform content that includes sufficient direct and indirect identifiers for the person involved and the specific event to facilitate linkage.

3. Should promote use of the KABCO scale (K-killed, A-incapacitating injury, B-non-incapacitating injury, C-possible injury, 0-no injury) in crash data to document level of functioning at the scene and to facilitate linkage.


116


Characteristics of an Injury Characteristics of an Injury Control Data Component:Control Data Component:4. Should include death certificate and medical examiner data to track the location and cause of death.

5. Should link police crash data with EMS, ED, and hospital inpatient data.


117


Characteristics of an Injury Characteristics of an Injury Control Data Component:Control Data Component:6. Should also link roadway, citation/ conviction, driver licensing, vehicle registration, and other traffic records when available to ensure comprehensive information about the person, vehicle and event so that prevention efforts can be targeted to the appropriate population.


118


Characteristics of an Injury Characteristics of an Injury Control Data Component:Control Data Component:

7. Should include financial information to justify safety legislation in terms of reducing costs to society.

8. Should include a Global Positioning System (GPS) for locations and integrate GPS data with a Geographic Information System (GIS) for analysis.


119


Characteristics of an Injury Characteristics of an Injury Control Data Component:Control Data Component:9. Should include insurance claims data to obtain information about motor vehicle crash victims treated and discharged from outpatient settings (physician office/clinics/free-standing care facilities) which do not submit data for merging and analysis at the state level.


120


Characteristics of an Injury Characteristics of an Injury Control Data Component:Control Data Component:10. Should support a uniform reporting threshold and electronic data capture/exchange statewide so that data are collected for all people, both injured and non-injured, involved in motor vehicle crashes.

11. Should include statewide population based crash outcome data to ensure sufficient data for the surveillance of infrequent crash characteristics and analysis of their significance.


121


Characteristics of an Injury Characteristics of an Injury Control Data Component:Control Data Component:

12. Should apply the confidentiality standards of medical data to all linked data files.

13. Should distribute motor vehicle related health protected information according to the requirements of the HIPAA-Privacy Act and state legislation/ regulations governing patient confidentiality.


122


Characteristics of an Injury Characteristics of an Injury Control Data Component:Control Data Component:14. Should enable crash, pre-hospital EMS and other medical data to be available when needed at the time of treatment during each phase of the medical emergency to ensure continuity of patient care.

15. Should monitor responsiveness of the EMS/trauma system to motor vehicle crashes.


123


Characteristics of an Injury Characteristics of an Injury Control Data Component:Control Data Component:16. Should support a system’s approach to the evaluation of EMS and trauma system effectiveness for victims of motor vehicle crashes.

17. Should include an inventory of health care providers and facilities, preferably derived from licensing information, to ensure that appropriate resources that match patient need are available in a timely and effective manner.


124


Characteristics of an Injury Characteristics of an Injury Control Data Component:Control Data Component:18. Should promote collaboration between public safety and the public health communities to facilitate the collection and distribution of data for injury control related to motor vehicle crashes.

19. Should provide training for collectors and users of the data to assure the quality of the data collection and the proper use and interpretation of the data by end-users.


125


Characteristics of an Injury Characteristics of an Injury Control Data Component:Control Data Component:20. Should include data that are timely, complete, accurate and comprehensive to support data-driven highway safety decisions.


126


Examples of Questions an Injury Examples of Questions an Injury Control Data Component Should Control Data Component Should Be Able to Answer:Be Able to Answer:

• Are victims of motor vehicle crashes statewide receiving appropriate medical care in a timely manner?

• What characteristics of the person, vehicle and event are most associated with high severity and/or high health care costs?


127



• Where should resources be targeted in the state to have most impact on reducing deaths, injuries, injury severity and costs?


128



• What population groups (by age, gender, etc.) and types of crashes should be targeted to have the most impact on reducing deaths, injuries, injury severity and costs?


129



• Are injury control data available in a timely manner to support data driven critical highway safety decisions?


130


ENFORCEMENT / ENFORCEMENT / PROSECUTION/ PROSECUTION/

ADJUDICATION DATAADJUDICATION DATA


131


Roadway

Exposure

Driver License

Motor Carrier

Injury Control

CRASH

DATA ANALYSIS



132

Enforcement / Prosecution/ Enforcement / Prosecution/ Adjudication Data ComponentAdjudication Data Component

What is an Enforcement / What is an Enforcement / Prosecution /Adjudication Data Prosecution /Adjudication Data Component?Component?Identifies traffic arrest and conviction activity for drivers in the state, including information which tracks a citation from the time of its distribution to an enforcement jurisdiction, through its issuance to an offender, and its ultimate disposition by a court.


133

What is an Enforcement / What is an Enforcement / Prosecution/ Adjudication Data Prosecution/ Adjudication Data Component?Component?

Information obtained will identify the type of violation, location, date and time, the enforcement agency, court of jurisdiction, and final disposition.



134

Who Uses an Enforcement / Who Uses an Enforcement / Prosecution /Adjudication Data Prosecution /Adjudication Data Component?Component?• Law enforcement agencies – for enforcement program planning and monitoring

• Driver licensing and suspension authorities – for problem driver identification

• Courts – as part of driver history, monitoring, ideally as automated case entry



135

Who Uses an Enforcement / Who Uses an Enforcement / Prosecution /Adjudication Data Prosecution /Adjudication Data Component?Component?• Independent contractors with citation issuance authority – for planning and monitoring

• Motor carrier officials – for problem driver and problem carrier identification



136

Who Uses an Enforcement / Prosecution Who Uses an Enforcement / Prosecution /Adjudication Data Component?/Adjudication Data Component?

• Highway safety office – for problem identification, program planning, monitoring and evaluation

• Highway engineering offices, in conjunction with other TSIS data – for problem location analysis

• Lawmakers – for policy analysis

• Prosecutors – for planning and problem-driver identification



137

Characteristics of an Enforcement / Characteristics of an Enforcement / Prosecution /Adjudication Data Prosecution /Adjudication Data Component:Component:An Enforcement/ Prosecution /Adjudication Data Component should be able to:

(1) Provide history information to the officer in the field

• Is the driver’s conviction history available to the officer in the field?• Are pending cases available?• Is there a legal reference tool for use by officers?



138

Characteristics of an Enforcement / Characteristics of an Enforcement / Prosecution / Adjudication Data Component:Prosecution / Adjudication Data Component:

(2) Collect traffic citation data in the field, ideally electronically

• Is there a statewide uniform citation?• Are all contacts documented properly to ensure professionalism?• Does the system take advantage of bar-coding or magnetic strip technology?• Is there a consistent location system used to identify where citations are written?



139

Characteristics of an Enforcement / Characteristics of an Enforcement / Prosecution /Adjudication Data Prosecution /Adjudication Data Component:Component:

(3) Move citations to the court and state citation database, ideally electronically

• Are courts provided with timely and accurate driver history?• Are pending cases included in that history?



140

Characteristics of an Enforcement / Characteristics of an Enforcement / Prosecution /Adjudication Data Prosecution /Adjudication Data Component:Component:

(4) Pass adjudication data to enforcement agency, state citation database, and other states (for out-of-state drivers) electronically

• Is adjudication information captured for all citations?• Are these data posted to the driver history in a timely manner?• Do enforcement agencies have good data for planning and training?



141

Characteristics of an Enforcement / Characteristics of an Enforcement / Prosecution / Adjudication Data Prosecution / Adjudication Data Component:Component:

(5) Pass data to other systems, particularly driver licensing; link to and or access to crash and other data bases

• Are data available in a timely manner to other state, local or Federal data systems?• Are data coding standards used (e.g. ANSI D20)?



142

Characteristics of an Enforcement / Characteristics of an Enforcement / Prosecution /Adjudication Data Component:Prosecution /Adjudication Data Component:

(6) Provide citation/conviction data for analysis in a timely manner

• Are summary and detail data available for program and legislative support?

• Are data available for public information needs?

• Are data transferred in a timely manner?

• Are data available in a usable form for analysis?

• Can citation data be linked to crash, roadway, driver and vehicle files?



143

Characteristics of an Enforcement / Characteristics of an Enforcement / Prosecution / Adjudication Data Prosecution / Adjudication Data Component:Component:

(7) Capture all traffic citations issued, regardless of agency or whether issued under state law or municipal ordinance.

• Is there a tracking process for accountability by the officer, enforcement agency and court?• Is there a uniform citation?



144

Examples of Questions an Examples of Questions an Enforcement / Prosecution / Enforcement / Prosecution / Adjudication Data Component Should Adjudication Data Component Should Be Able to Answer:Be Able to Answer:

1. Who are the problem drivers in the state?

2. Are there locations that appear to be problematic based on citations?

3. Who are the problem motor carriers in the state?



145

Examples of Questions an Enforcement / Examples of Questions an Enforcement / Prosecution / Adjudication Data Prosecution / Adjudication Data Component Should Be Able to Answer:Component Should Be Able to Answer:

4. Are enforcement programs effective (in conjunction with crash data) ?

5. Nature of problems in enforcement, prosecution, or adjudication?

6. What is the relationship between enforcement locations and crash locations?



146

Examples of Questions an Enforcement / Examples of Questions an Enforcement / Prosecution / Adjudication Data Prosecution / Adjudication Data Component Should Be Able to Answer:Component Should Be Able to Answer:

7. How many speeding citations were written; where and when?

8. Are there different violation patterns among younger drivers that should be addressed through legislation (e.g. GDL)?



147

See TSIS Guidelines Document for a

Sample State Flow Chart

for Enforcement / Prosecution /Adjudication Data



148


MOTOR MOTOR CARRIER DATACARRIER DATA


149


Roadway

Exposure

Driver License

Motor Carrier

Injury Control

CRASH

DATA ANALYSIS



150

Motor Carrier Data ComponentMotor Carrier Data Component

What is a Motor Carrier Data What is a Motor Carrier Data Component?Component?• Basic identification data of motor carriers (truck and bus companies) authorized to conduct business in a State.• Usually includes record of payments of fees and taxes.• Varies from state to state. Usually includes only ‘for hire” carriers at state level.


151


Functions a Motor Carrier Data Functions a Motor Carrier Data Component Should Support:Component Should Support:• Motor carrier licensing, fees, and taxes• When linked to other components, provides law enforcement agencies the ability to identify motor carriers having safety problems, and to target inspection and audit programs


152


Who Uses a Motor Carrier Data Who Uses a Motor Carrier Data Component?Component?• Federal and State Motor Carrier Safety Assistance Program (MCSAP) managers and personnel• State & Local Agencies (Law enforcement, Vehicle registration, Taxation authorities)• Truck and Bus companies• Insurers• Shippers• Leasing Companies• The Public


153


Characteristics of a Motor Characteristics of a Motor Carrier Data Component:Carrier Data Component:1. Both private and for-hire motor carriers should be included if possible.

2. Identification must be keyed to a unique identifier, preferably a USDOT number.

3. Any other available identifiers should be included if permitted by law.


154


Characteristics of a Motor Characteristics of a Motor Carrier Data Component:Carrier Data Component:4. Addresses should be clearly defined as to whether they are primary places of business, mailing addresses only, terminals, etc.

5. The carrier’s entire “doing business as” (DBA) names should be included.

6. The data should be re-certified by the carrier annually, or every two years at a minimum.


155


Characteristics of a Motor Characteristics of a Motor Carrier Data Component:Carrier Data Component:7. If the data indicates whether a carrier is currently authorized to operate in the state and/or has valid insurance coverage, any suspension or revocation of privileges should be immediately posted.

8. Enforcement personnel as well as others should have immediate access to the data.


156


Characteristics of a Motor Characteristics of a Motor Carrier Data Component:Carrier Data Component:9. Should incorporate the architecture and operational concepts of CVISN.

10. Fields of data should be categorized by timeliness needed (real time, daily, weekly, etc.) to support enforcement and other users.


157


EXPOSURE EXPOSURE DATADATA


158


Roadway

Exposure

Driver License

Motor Carrier

Injury Control

CRASH

DATA ANALYSIS



159

Exposure Data ComponentExposure Data Component

What is an Exposure Data What is an Exposure Data Component?Component?• Denominators used as normalizing factors for highway safety analysis.

• Include measures of traffic volume, registered vehicles, licensed drivers, and population.


160


What is an Exposure Data What is an Exposure Data Component?Component?• Normalization allows valid comparisons across locations, types of vehicles or groups of people while accounting for differences in usage or population.

• May be subdivided by political subdivisions, other geographic areas, demographics, and vehicle and roadway characteristics.


161


Key Exposure Measures:Key Exposure Measures:

• Traffic volumeTraffic volume

• Registered vehiclesRegistered vehicles

• Licensed driversLicensed drivers

• PopulationPopulation


162


Exposure data allow for the computation of Exposure data allow for the computation of ratesrates,, which are usually a better measure than which are usually a better measure than simple counts. simple counts. For exampleFor example::

Crash rate = crashes per 100 Million vehicle Crash rate = crashes per 100 Million vehicle miles traveledmiles traveledInjury risk = injuries per 100,000 populationInjury risk = injuries per 100,000 populationCrash risk = crashes per 100,000 licensed Crash risk = crashes per 100,000 licensed driversdriversRollover risk = rollovers per 1,000 crashesRollover risk = rollovers per 1,000 crashes


163


Who Uses an Exposure Data Who Uses an Exposure Data Component?Component?• Highway agencies – to identify problem locations and compare crash experience across locations or over time

• Highway Safety Offices – to plan and evaluate programs


164


Who Uses an Exposure Data Who Uses an Exposure Data Component?Component?• Any organization that does problem identification, analysis or evaluation to compare experience over time or across locations


165


Characteristics of an Characteristics of an Exposure Data Component:Exposure Data Component:Traffic volume data

• Are traffic volume data available for road segments?

• Is traffic on all public roads included?

• Are historical volume data available for trend analysis and evaluation?


166


Characteristics of an Characteristics of an Exposure Data Component:Exposure Data Component:Population data

• Are data from the decennial census and annual estimates available?

• Are demographic data available at relevant levels of geography?

• Can incident data be aggregated to those levels of geography?


167


Characteristics of an Characteristics of an Exposure Data Component:Exposure Data Component:Driver License data

• Are counts of licensed drivers available by age, gender and geography?

• Are historical data available?


168


Characteristics of an Characteristics of an Exposure Data Component:Exposure Data Component:Vehicle Registration data

• Are counts of registered vehicles available by year, make, model and geography?

• Are historical data available?


169


Examples of Questions an Examples of Questions an Exposure Data Component Should Exposure Data Component Should Be Able to Answer:Be Able to Answer:• Who is most at risk for crashes or citations (age, gender, type of driver’s license held, etc.) ?• Is an intersection “A” with 100 crashes really more dangerous than intersection “B” with 20 crashes? (As measured in annual million vehicles entering the intersection)?


170


Examples of Questions an Examples of Questions an Exposure Data Component Should Exposure Data Component Should Be Able to Answer:Be Able to Answer:• Are heavy trucks more likely to be in crashes than passenger cars? (As measured in vehicle miles traveled by the particular vehicle type and in terms of the number of vehicles registered in the state of that type) ?• Do graduated driver licensing laws improve the safety of young novice drivers?


171


Examples of Questions an Examples of Questions an Exposure Data Component Should Exposure Data Component Should Be Able to Answer:Be Able to Answer:

• Is a particular model of SUV prone to rollover crashes?

• Do roundabouts improve safety?


172


DATA ANALYSIS DATA ANALYSIS PROCESSPROCESS


173


Roadway

Exposure

Driver License

Motor Carrier

Injury Control

CRASH

DATA ANALYSIS



174

Data Analysis ProcessData Analysis Process

What is a Data Analysis What is a Data Analysis Process Component?Process Component?• The procedures, documents, data sets and analytic tools used to characterize the traffic safety experience for a specific locale (a piece of roadway up to a state or even the nation), a specific population (as defined by demographics, residence, or behaviors), a type of vehicle and/or a set of circumstances.


175


Who Uses a Data Analysis Who Uses a Data Analysis Process Component?Process Component?• Usually limited to experienced, highly skilled personnel trained in the specific analytic procedures and software to be used. • Users of the results of the analysis include all highway safety professionals and interested parties from outside the highway safety professions (legislators, the press, students, community groups, etc.).


176


Functions the Data Analysis Functions the Data Analysis Process Component Should Process Component Should Support:Support:

1. Standardized reporting of safety information

2. Ad hoc reporting of safety information3. Quality control of all TSIS components’

data4. Problem identification5. Program (countermeasure) evaluation


177



6. Safety resource allocation7. Legislation and policy development and

effectiveness evaluation8. Public information program content

development9. TSIS component improvement


178



10. Valid comparison of crash experience among locales

11. Valid comparison of crash experience among sub-populations

12. Valid comparison of crash experience among vehicle types


179



13. Valid comparison of crash experience based on sets of circumstances

14. Optional user access to analysis results via Internet or CD


180


What a Data Analysis Process What a Data Analysis Process Component Should Contain:Component Should Contain:1. Crash data2. Data from any other TSIS component3. Linking variables to tie crashes to other TSIS source data4. Descriptive statistics derived from linked data sets5. Trend data describing changes over time


181


What a Data Analysis Process What a Data Analysis Process Component Should Contain:Component Should Contain:6. Comparative data for contrasting differences in locales, populations, vehicles or circumstances7. Results of statistical tests and significance levels8. Information on the limitations of data and/or analyses


182


Examples of Questions a Data Examples of Questions a Data Analysis Process Component Analysis Process Component Should Be Able To Answer:Should Be Able To Answer:1. What was the effect of passing the _______ law on traffic safety?2. Which communities/subpopulations have the highest risk for crash-related morbidity and mortality?3. What types of crashes are most likely for specific types of drivers or vehicles?


183


Examples of Questions a Data Examples of Questions a Data Analysis Process Component Analysis Process Component Should Be Able To Answer:Should Be Able To Answer:4. Which drivers are most at risk for crash involvement? Crash-related injuries or fatalities?5. Do seat belts save lives? Do air bags? How many?6. What is the profile of the average DUI driver? Of drivers without a valid license?


184


Examples of Questions a Data Examples of Questions a Data Analysis Process Component Analysis Process Component Should Be Able To Answer:Should Be Able To Answer:

7. What are the days and times when alcohol involved crashes are most likely to occur?

8. Per mile driven, what vehicle types are most likely to be involved in crashes?


185


Examples of Questions a Data Examples of Questions a Data Analysis Process Component Analysis Process Component Should Be Able To Answer:Should Be Able To Answer:

9. Is the rollover propensity of a specific vehicle model higher than for similar vehicles?

10. Does the survivability of crashes vary by the location type (urban, rural, etc.)?


186


• Guidelines were compiled to provide state and local safety information systems professionals with assistance as they review their current systems and plan changes to improve those systems.

• To be released probably late 2003 or early 2004…


187

Web Site

Association of Association of Transportation Safety Transportation Safety

Information ProfessionalsInformation Professionals

www.atsip.orgwww.atsip.org

7/15/03 Association of Transportation Safety Information Professionals 1 Traffic Safety Information...

Documents

Transcript of 7/15/03 Association of Transportation Safety Information Professionals 1 Traffic Safety Information...