Working Demo · Real State Data

Crosswalk

Map any state's crash data schema onto MMUCC6, validated against all 113 edit rules.

Every state runs its own crash-reporting system, built years apart, by different vendors, on different timelines — so the same real-world crash ends up recorded in incompatible ways from state to state. Crosswalk maps a state's own crash, vehicle, and person fields onto the federal MMUCC6 standard, then validates the result — without changing anything about how an officer files a report in the field.

State Mappings

Configured today for five states — Washington, D.C., Illinois, Iowa, Kansas, and Nebraska — each tracked across four mapping categories: crash fields, vehicle fields, person fields, and person-specific overrides. Nebraska's mapping is the most complete so far: 14 crash fields, 11 vehicle fields, 6 person fields, and 1 person override, all reviewable in the tool.

Validation, not blind trust

A mapping is only as good as what it's checked against. Crosswalk runs all 113 MMUCC6 edit rules against real mapped sample data — currently 65 real, de-identified Nebraska crash records — and surfaces every violation individually: which crash, which rule, and how severe.

Nothing passes through silently. Each violation goes through a human-decision step with four explicit options — allow it as-is, fix the source value, exclude the record, or delete the value — and that decision is saved rather than assumed.

Propose Crosswalk

Beyond reviewing existing mappings, the tool takes proposals for new ones. An AI-assist feature is built in to help draft a proposal, though it's disabled on this particular deployment — it degrades gracefully to an "unavailable" message rather than breaking anything.

Where it stands today

This is a working demo, not a finished product — described honestly here rather than oversold. It runs on real de-identified crash data from five states as proof of concept, and the review/validate workflow above is fully functional. What's not yet true: downstream systems don't yet consume the triage decisions made here — that's the next boundary to push past. If mapping your state's crash data onto MMUCC6 is a problem you have, get in touch.