Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Incident Reporting topic
No spam. Unsubscribe anytime.
Legislation pushes expanded incident reporting and nine new ESI fields; USB to accept additional fields and keep Qualtrix temporary intake
Summary
USB told LEAs to prepare for two developments: Senate Bill 51 requires reporting credible-threat details and threat-assessment results, and emergency-safety-intervention (ESI) reporting will expand to nine fields (six in current specs, three added after LEA feedback). USB will accept select-all ESI purpose/outcome fields and clarified minutes aggregation.
USB staff briefed LEAs on pending incident- and ESI-related reporting changes driven by recent legislation. Two parallel items are highlighted: (1) Senate Bill 51 requires collection and reporting of credible-threat indicators and related threat-assessment outputs; and (2) emergency safety intervention reporting is expanding.
On ESI, staff said six fields originally added to the UTREX spec will be joined by three additional fields that LEAs asked for to reduce reporting burden. The three new fields will report counts (for example, the number of physical restraints or seclusions) plus whether any event exceeded 30 minutes, allowing LEAs to report totals across multiple ESIs instead of creating separate incident records for each application. USB also changed ESI purpose and outcome fields to select-all-that-apply to match LEA practice in Qualtrics.
For incident codes, USB deprecated the separate 'sexual assault' code and instructed LEAs to use the federal sexual-harassment coding, and it expanded infraction code options to reduce 'other' and 'disruption' percentages in the annual law-enforcement action report.
USB said LEAs may provide ESI details in their SIS once the fields are implemented; until then, Qualtrics will continue as a temporary intake mechanism. Staff emphasized that they do not intend to require duplicate reporting once SIS fields roll into UTREX and vendors enable automated feeds.
Source and provenance: the incident and ESI conversation is recorded (topic begins SEG 2680 and the ESI field discussion occurs SEG 3000–3185).
