CESSA Subcommittee for Technology, Systems Integration & Data Management (TSIDM)
March 18, 2024, 2:00 pm - 3:30 pm via Zoom
Meeting Minutes - Approved by Members 04/15/2024
Subcommittee members: Brent Reynolds, Cindy Barbera-Brelle, David Albert (Designee-Lee Ann Reinert), Richard Manthy, Jim Kaitschuk, Ashley Thoele (Designee - Robert Van Bebber)
- Welcome and Call to Order (Roll Call)
- Open Meetings Act
- Approval of the Minutes from previous meeting
- State updates
- Updates from and to other bodies
- Planning and updates on Subcommittee deliverables
- Next meeting dates
- Public comment
- Adjournment
The meeting was called to order by Brent Reynolds at 2:01 pm.
Pete Eckart reviewed procedures around the Open Meetings Act and meeting logistics.
Roll Call:
- Present by phone or video: Robert Van Bebber, Brett Reynolds, Lee Ann Reinert, Jim Kaitschuk, Richard Manthy
- Absent: Cindy Barbera-Brelle
Motion to approve meeting minutes from February 20, 2024 and March 4, 2024 from Lee Ann Reinert, seconded by Brent Reynolds. All present members approved the minutes except Robert Van Bebber and Richard Manthy who both abstained.
- Minutes from February 20, 2024 and March 4, 2024 approved by Brent Reynolds at 2:05 pm.
State updates: Lee Ann Reinert
- Legislative changes that were proposed were scheduled for first hearing last week and are moving through to the next hearing. No changes in terms of what's been proposed to date. Changes may occur as it moves through committee.
Updates to and from other bodies: Pete Eckart - No updates
Planning and updates on subcommittee deliverables: Pete Eckart
- We planned to be working on operational procedures between 911 and 988, and 988 and MCRT but we are subject to the work that happens in other places, so the conversation about communications between those entities is happing first in those other places. Because of that, we've moved forward to Task H.
- Today we will review Arizona and Virgina models, then review these specific elements:
- Call Intake
- Bed Registry
- Mobile Dispatch
- Referral and Appointment Scheduling
- Reporting and Analytics
Discussion on Arizona and Virginia models:
- Illinois will need a way to incorporate follow up for both mobile crisis response and 988.
- A phased approach is a key process recommendation
- Brent Reynolds: One solution for reporting data in North Carolina is the ability to gather the local data like call times and call transcripts that interfaces with the database no matter your processing equipment using artificial intelligence.
- 11 other states use situational awareness apps for their first responders, we could consider this for mobile crisis response teams. We can take a look at what Brent was introduced to see what's available.
- Charlie Petrof: Three checkboxes to add to the Arizona list for consideration.
- A system that would allow advanced care directives (in CESSA legislation)
- Different liability requirements. For example, ambulance company believes they have to take someone to hospital emergency room, but emergency room thinks they are not the correct receiving location.
- How will the people at 911 centers connect with dispatch? For third party calls, I would hope that service, the broad reach of the emergency responder community, can be maintained when there is need to locate the individual.
- Pete Eckart: To Charlie's second point, there are a variety of things that are covered to some extent in existing legislation. For example, there are some liability issues in the legislation regarding the PSAPs but they aren't covered the same way for mobile crisis response, so there is going to need to be some research.
Call center risk assessment:
- Virginia has automated their risk assessment process. It looks similar to Illinois' interim risk level matrix
- Their process helps them screen the caller to identify the right resource.
Mobile Dispatch:
- Lee Ann Reinert: some ability to have GPS enabled technology so can get whoever is closest to respond.
- Rick Manthy: When transferring information, the caller should know when they are being transferred and who they are being transferred to.
- Jessica Gimeno: Can we do a LOCUS (Levels of Care Utilization) approach so that the person on the crisis wouldn't have to repeat?
- Pete Eckart: That's a general suggestion and also software requirement that you're suggesting. For the software it could be two ways: if the system was able to accept that information you described, or if they are asked to provide that information wherever they enter the system and it travels with them.
- Lee Ann Reinert: A 911 communicator maybe won't have done a LOCUS nor would we expect them to. But it is important that the technology collects information about the person and it continues to be shared and built upon rather than having to start all over. I call it a medical record or electronic health records, to share information across responders in a HIPPA compliant way. This relates to what Charlie was saying about psychiatric advance directives.
- Brent Reynolds: We should know not just location, but also status of mobile crisis response teams. Are they checking in? When was the last update? Also triaging if needed.
Referral and Appointment Scheduling:
- Charlie Petrof: Is there a place where these systems allow them to go back and make secondary referrals like a mobile crisis response in an overdose situation needs an ambulance?
- Pete Eckart: I don't see that either, but I remember when I looked at the workflow, there was a feedback loop for the MCRT to connect back to 911, EMS or law enforcement. That's a common piece of these systems.
- Lee Ann Reinert: I think there is nothing on theses slides that we wouldn't want but as we make recommendations that would lead to procurement requirements, there are some things that are system is not ready for. We don't yet have a system of community providers that could provide a schedule of same day appointments to MCRT.
- This is a process piece. Some recommendations are dependent on the continued maturation of the system, and other recommendations are dependent on other pieces built first.
- Charlie Petrof: I'm thinking about locations where there would be a challenge to provide location information, like a train, like a public place, like a college.
- Brent Reynolds: In most cases where you are trying to locate a caller, depending on the technology and the provider, there may be a way to bread crumb that person's location. And there should be a space for notes that are more specific.
- Pete Eckart: The persistence and specificity of the location data are completely subject to how someone comes into the system. If someone comes in through 911, that data is more specific because the cell phone towers can triangulate location. If call comes in through 988, location data is less helpful and the communication about the location is much more importation. There is legislation about changing the location data available to 988. This is one of the many ways the heterogenous technology knitting these systems together.
- Jessica Gimeno: I learned in a CARE presentation that hunger was a big secondary concern. So the need for basic needs as a secondary concern to be included in notes.
- Lee Ann Reinert: We've been doing all of our planning with the assumption that if someone is at an airport, that's not somewhere that our MCRT would be going.
- Brent Reynolds: I would think that with the proper arrangements with public safety, they can get your teams into those areas.
- Lee Ann Reinert: Not right now because our MCRT don't have the same status as other emergency responders.
Reporting and Analytics:
- We'd want information differentiated by jurisdiction and the ability to get your information directly from the system without having someone else provide it to you.
- Jessica Gimeno: I like how this separated by involuntary and voluntary. I think the number of times that restraints were used, the number of times there were complaints, the number of times that the caller dropped the call could be added.
Next Meetings:
- Monday, April 1, 2024 2:00-3:30 pm
- Monday, April 15, 2024 2:00-3:30 pm
Public Comment: No comment
Adjournment:
- Meeting adjourned by Brent Reynolds at 3:21 pm.
