Return to NHTSA homepage

Banner with logos of contributing organizations: FHWA, FMCSA, NHTSA, GHSA, and NCSA

Back   Table of Contents   Forward

MMUCC
MODEL MINIMUM UNIFORM CRASH CRITERIA GUIDELINE
Improving Crash Data for Safer Highways

APPENDIX E

Checklist for a State Highway Safety Information System

MMUCC supports implementing MMUCC within a state highway safety information system that is comprehensive, relies on standardized data, stores and distributes timely, complete and accurate data, and provides access to users at all levels. The following checklist lists the characteristics of a model state highway safety information system and provides a model for evaluating your state’s highway safety information system.

Types of Data

Does your state computerize statewide the following types of data? Yes No Partial
Traffic Records:    

Driver Licensing

      

Vehicle Registration

      

Enforcement (Citation/conviction)

      

DUI/DWI Offenders

      

Roadway Inventory (volume, ADT, type)

      
Injury Records:      

EMS Responses/transports

      

Emergency Department Visits

      

Hospital Discharges

      

Deaths

     
Other Data (observational studies, surveys, etc.)      

 

Scope of Data Resources

Does your state highway safety information system: Yes No Partial
Include comprehensive information about all components of the event: crash, persons involved, vehicle, roadway?      
Include GPS for location and a GIS based decision support system?      
Include data for all types of roads (local, county, state)?      
Support a data driven management approach for reporting, problem ID, monitoring, evaluation?      

 

Standardized Data Elements

Are the data elements in your state highway safety information system based on nationally accepted and published guidelines as well asstandards for reporting thresholds and definitions? Yes No Partial
Crash Data:      

MMUCC

      

Other applications using ANSI D16.1/ANSI D20

      
Injury Data:      

EMS (NHTSA sponsored)

      

Emergency Department (DEEDS or UB92)

      

Hospital (UB92)

      

 

Functional Capabilities

Does your state highway safety information system perform these functions? Yes No Partial
Link pre-crash, crash and post crash data to medical and financial outcome (CODES Project).      
Link environmental information (roadway, licensing, vehicle registration, citation) to crash data.      
Collect all records statewide per reporting thresholds and complete routine quality control checks.      
Describe individual crashes or crashes in the aggregate.      
Generate information in a timely manner for meaningful decision-making.      
Facilitate direct access to the data on-line, via the Web and/or on CD-ROM.      
Can distribute data in routine reports, by special request or via query systems.      
Archive historical data in a “warehouse” or “network,” so they can be easily accessed to evaluate trends over time.      
Store data in a central repository or on a decentralized network.      

 

Administrative Characteristics

Is your state highway safety information system: Yes No Partial
Supported by a Traffic Records Coordinating Committee (TRCC) that meets regularly?      
Carrying out routine traffic records assessments (within past three years)?      
Involved in ongoing strategic planning efforts involving the TRCC to improve the state highway safety information system?      
Sufficiently funded by the stakeholders to ensure long term survival?      

Banner with logos of contributing organizations: FHWA, FMCSA, NHTSA, GHSA, and NCSA

Back   Table of Contents   Forward