From the Emergency Services edition of September 30, 2026
GovTech/cleveland.com: Lake County, Ohio approves Eventide AI to review 100% of EMD calls
Lake County Central Communications / Lake County Board of Commissioners (reported by cleveland.com via GovTech) · County 911 / emergency medical dispatch QA · United States (Lake County, Ohio)
- Publisher
- GovTech (Tribune/cleveland.com)
- Original publication
- 2026-09-30
- Source retrieved
- 2026-10-01
- Event date
- 2026-09-29
What happened
September 30, 2026 GovTech republish of a cleveland.com report states Lake County’s 911 dispatch center will use AI to review every emergency medical dispatch (EMD) call after commissioners on Tuesday (September 29) approved a five-year, approximately $190,000 agreement with Eventide Communications to upgrade the existing call-recording system. Capt. Daniel Bachnicki, 911 coordinator, said Ohio now requires PSAPs to review at least 2% of EMD calls (~272 for Lake County). The AI system is to review 100% of EMD calls and report whether dispatchers asked required questions, obtained needed information, and followed medical dispatch procedures. Central Communications handles about 90,000 911 calls annually. Supervisors remain responsible for final evaluations, coaching, and corrective action. First-year cost $45,340; then $36,369/year for four years.
Why it matters
Same-day SLTT PSAP procurement signal extending the 100% EMD/911 QA automation pattern with Ohio regulatory 2% baseline and HITL coaching retained. Why now: published 2026-09-30; not in emergency-services archive; first Eventide Critical Insights–style county buy surfaced since last published run 2026-09-28.
Evidence and measured results
Opened GovTech HTML via curl (final URL with www). Date September 30, 2026; ~$190k/5 years; 2%/272 EMD; 100% AI review quote; 90,000 annual 911 calls; HITL supervisor role; year-1 $45,340 and $36,369 thereafter from page.
Limitations and uncertainty
Procurement/announcement reporting—not post-deployment measured QA agreement or patient-outcome data; Eventide product claims not independently audited here.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-30; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- PSAPs cannot manually meet meaningful EMD QA coverage under state sample floors without more supervisor time.
- Stakeholders
- 911 coordinators
- ECC supervisors
- County commissioners
- Telecommunicators/labor
- Discovery questions
- What % of EMD calls are QA'd today?
- Is Eventide already the recorder?
- How will AI scores enter evals?
- What Ohio/local SOP checklist applies?
- Value hypothesis
- AI EMD QA may expand coverage toward 100% if humans still finalize coaching—not if scores become unreviewed punishment.
- Potential engagement
- 90-day Eventide AI QA pilot with agreement and coaching-latency KPIs against the 2% baseline.
- Unsupported claims
- Guaranteed $190k ROI
- Improved patient outcomes proven
- AI replaces QA supervisors
Pre-sales engineering
Role takeaway
- Fit
- Recording-based AI EMD protocol scoring and reporting with human final evaluation.
- Architecture and integration
- Eventide recorder → AI EMD score/report → supervisor queue → coaching/eval systems.
- Prerequisites
- Recording access
- Digitized EMD checklist
- Flag thresholds
- Access logging
- Constraints
- Announcement-only metrics
- Vendor score opacity
- Medical-call PHI/PII
- Security
- Limit vendor access to EMD audio; set retention, subprocessors, and CJIS/HIPAA controls in the DPA.
- Proof of value
- Auto–manual agreement
- Manual QA hours vs 2% baseline
- Time-to-coaching after flags
Delivery
Role takeaway
- Work
- Configure EMD scorecards, train supervisors on AI reports, and stand up dispute/coaching SOPs.
- Dependencies
- 911 coordinator
- Recording/IT
- HR evaluation policy
- Ownership
- Supervisors own final evaluations; 911 coordinator owns program policy.
- Skills and adoption
- Train coaches to treat AI reports as prompts for listening, not automatic verdicts.
- Governance checkpoints
- Monthly agreement audit
- Labor consultation
- Eval-policy check
- Acceptance criteria
- Human finalization of flagged calls
- Documented dispute path
- Local KPI dashboard
- Risks
- Eval misuse
- Flag-queue overload
- Opaque vendor model changes
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Treat as recording-sidecar AI QA on EMD audio with supervisor evaluation queues—not live triage or CAD automation.
Governance
Who approves, reviews and stays accountable for outcomes?
Map AI reports to Ohio’s 2% EMD QA mandate, define how scores enter coaching vs discipline, and set pilot KPIs before workforce evaluation use.
Security and privacy
What data, permissions and controls need testing?
Full-EMD AI review expands vendor access to medical-dispatch audio; require CJIS/HIPAA-aligned DPA, retention limits, and access logging for the Eventide upgrade.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Shifts supervisor time from tiny mandatory samples toward trend spotting and coaching across all EMD calls while keeping humans as final evaluators.
Procurement
What should contracts, pricing and exit terms secure?
Budget ~$45k year one plus four renewals; evaluate against existing Eventide recorder lock-in and require local SOP scorecard alignment proofs.
Operating model
Which teams own the service once it runs?
Keep QA/coaching ownership with supervisors; use AI reports to prioritize which of 100% scored EMD calls get human deep review.
Publication history
- 2026-09-30Emergency Services · Issue 245 resources
Stable resource ID: govtech-lake-county-ohio-eventide-emd-ai-qa-20260930