Crash Data Guideline for Improved Traffic Safety
|
#1
|
|||
|
|||
|
Hello again fellow - MMUCC users
I know I promised a response to feedback that many of you provided on the data element P15 for Distracted Driving. I have not forgotten. We are gearing up for a major discussion of data elements contained on the PR-1 crash report form here in Connecticut. Beginning on April 21, each member of the PR-1 Review Working Group (38) will be given the opportunity to put his or her suggestions ‘on the table’ for others to review and discuss. The PR-1 was last updated in 1994 and many stakeholders from law enforcement to driver licensing to highway safety have begun questioning whether it still meets their needs. Today I must raise another issue that was discussed with the MMUCC Expert Panel during the update of the Third Edition of MMUCC. There was support for this idea and it was summarized in the MMUCC Third Edition (see below). Unfortunately, contrary to the last sentence, this effort has not made it out of the planning stages; that is, unless … which brings me to my new question for MMUCC users. Mini-MMUCC for PDOs Question - Has anyone adopted something similar - a reduced set of MMUCC data elements in their State - specifically for Property Damage Only (PDO) crashes? Thanks again – trust all is well and that many of you will be able to attend this year’s Forum in New Orleans! Dave Bozak MMUCC Guideline Third Edition (2008) Introduction p. vii Planning is underway to identify a reduced set of MMUCC elements that would be recommended specifically for Property Damage Only (PDO) crashes. Considering that approximately two-thirds of all crashes reported are PDO crashes, for law enforcement this could mean: a) less time spent reporting motor vehicle crashes, b) an increase in reporting of PDO crashes, which often go unreported, and c) improvement in the accuracy and completeness of information collected in the field. Results from this effort are expected to be completed in 2009. |
|
#2
|
|||
|
|||
|
We adopted use of a PDO form here in Nevada in 2006.
It's a subset of all elements included on our full crash report form (NV Form 5) so we didn't have to make significant database changes. For example, the original PDO design called for capturing occupant restraint use simply as 'Yes/No' instead of using the codified values used on the full crash report form. In the end, we stuck with the codifed values. For data elements that use codified values, we were able to incorporate the associated code lists on the PDO form itself so a separate code sheet wouldn't be necessary; the form is a single two-sided sheet. We also established criteria as to when a PDO form can be used: 1) No incapicitating, non-incapicating or claimed injuries (of course); 2) No commercial vehicles involved; 3) No non-motorists involved. |
|
#3
|
|||
|
|||
|
What percentage (or how many) of the data elements on your regular crash form are used on your PDO form?
I would be interested in knowing which data elements you exclude and which you simplify. Thanks |
![]() |
| Thread Tools | |
| Display Modes | |
|
|