CESSA Technology, Systems Integration & Data Management Subcommittee Meeting - Approved Minutes 2/06/2023

CESSA Subcommittee for Technology, Systems Integration & Data Management (TSIDM) - February 6, 2023, 2:30 - 4:00 pm

Meeting Minutes - Approved by Members 02/21/2023

Subcommittee members: Brent Reynolds, Cindy Barbera-Brelle, David Albert (Designee-Lee Ann Reinert), Richard Manthy, Alice Cary, Jim Kaitschuk

Expert Consultant Group (ECG) members: Peter Eckart, Chris Baldwin

  1. Welcome and Call to Order
  2. Meeting Logistics/OMA
  3. Roll Call and Approval of Minutes from TSIDM meeting on November 28, 2022
  4. Discussion regarding data needs and collection
  5. State Updates
  6. Wrap Up
  7. Public Comment
  8. Adjournment

Welcome and Call to Order

  • Meeting called to order at 2:36 pm by Brent Reynolds, Chair

Meeting Logistics/OMA

  • Eckart confirmed that the meeting minutes are being taken and that the meeting is being recorded.
  • Reynolds confirmed that OMA training is still requested for all members.

Roll Call and Approval of Minutes from TSIDM meeting on December 19, 2022

  • Member Attendees Present: Brent Reynolds Y, Lee Ann Reinert Y (David Albert designee), Richard Manthy, Jr. Y, Jim Kaitschuk, Cindy Barbera-Brelle Y
  • With five members present, a quorum is established.
  • Expert Consulting Group Attendees Present: Peter Eckart, Chris Baldwin
  • Barbera-Brelle motioned to accept the minutes, Manthy seconded.
  • Reynolds, yes and yes
  • Kaitschuk, yes and yes
  • Reinert, yes and abstain
  • Manthy, yes and yes
  • Barbera-Brelle, yes and yes
  • Motion to approve the 12/19 meeting minutes passes.

State updates, Lee Ann Reinert

  • No additional updates beyond what was recently reported at SAC meeting earlier today
  • Eckart provides updates on the six-month plan

Eckart presents on behalf of Reynolds regarding planned Subcommittee discussions

Reynolds: Need to specify performance and metrics being collected or need to be

  • Manthy: from the 911 centers, can't count calls transferred to 988 or EMS, but they can count at the 988 provider
  • PSAPs probably can't count level 1 through 4, but what is the most basic level of data that we can collect?
  • How many from 988 to 911
  • Most CAD and EMD vendors will not be able to report by the 4 tiers
  • But we can say, to the vendors, ask for something, perhaps like BH calls
  • Reynolds: Before what the response determinants, need to know where are their programs around the state that can be referred to
  • For example, if there is a level 3 but there isn't a Level 3 responder available, then knowing the kind of response necessary won't help
  • Manthy: so we need the benchmarks
  • Dallas: 911 will not be dispatching MCRT, "nature code" but a "referred code" so we can say which ones we've referred to, but 988 can speak to that
  • 911 can speak to dispatching

How are we going to collect this data, what is the collection point? Is there a collecting source identified by the state?

  • Barbera-Brelle: after we determine what data we need to collect, then we can go to the vendors and give them some standards so that the EMD providers
  • Craig Kowalski, AWS is working with one of our municipalities to download CAD data, AWS and Ripple (sp?) are working together for social betterment, no cost

What data is PATH able to collect?

  • We know what we can get from EMS and 911 centers (EMD protocols that we can pull or ask to format)
  • How many calls directly from 988, how many transferred to 988 from 911, what percentage are being answered at each of the six regional sites. Boundaries are different for 911, 988, regions.
  • How is it tracked at the 988s
  • 988s and the 590s.

Chris Baldwin, PATH

  • we don't dispatch, but we refer
  • Some of the info regarding what is routed and rerouted happens at Vibrant and we don't have access to them.
  • We are one of six centers and don't have access to the other five now.

Reinert

  • the reason 988s don't' dispatch now, as interim guidance, but that is not the final response
  • Because of how 988 routes calls, we don't necessarily know
  • We would not want to directly prohibit a direct relationship between 911s and MCRT, but there are lots of things that would have to be worked out to make the possible, most important of them is that 988 and 911 are not the same thing.
  • Dallas: offers an example where the MCRT team would be way to long relative to the nature of the crisis. 911 can't transfer to 988.
  • Baldwin: why not 911 transfer to 988?
  • Dallas: we can't transfer a third-party caller to 988, we wouldn't do it. We could transfer a first-person caller.

Reynolds: we need a way to track the ability of the current system to respond without a police/ems presence when the MCRT response is inadequate

Mary Smith:

  • We developed a survey with DMH to ask for mcrt response time currently
  • Number of teams, location, on call or in office, amount of time between dispatch to face-to-face contact, time of day, 24/7 coverage or less.
  • We've got 50 of 66.
  • We're covering July 1 to September 1.
  • Another survey coming from the Crisis Hub to be executed by the RACs
  • Reynolds: will this data be available to show each region? Yes, but that is a secondary purpose based on

Motion for meeting schedule through July 1, 2023 to be approved.

Moved by Barbera-Brelle, seconded by Reynolds

Passed unanimously.

Public Comment

  • Changed to allow for public discussion as well
  • Comment or ask for a question
  • Susan Schaefer asked Craig Kowalski which jurisdiction he represents
    • Southern suburban cook county
    • Econ 911
    • Hazel Crest police dept
    • Project participants include Motorola, AWS,

Adjourn

Barbera-Brelle moved to adjourn, and Reinert seconded

Passed unanimously.

Chair Reynolds declared the meeting adjourned at 3:41 pm.