{"resourceId":"northeastern-ai-911-duplicate-triage-limits-20260810","versions":[{"version":"external-175ee34ab28e163d2caf1f73c25a1efee4d0f508f67b6efd582be6a899a41ad2","resource":{"id":"northeastern-ai-911-duplicate-triage-limits-20260810","title":"Northeastern analysis of New Orleans-style 911 AI: narrow duplicate-crash triage only; experts warn mission creep, missed distress cues, dialect risk","organization":"Northeastern University Global News","sector":"Higher education journalism / expert commentary on emergency communications","geography":"United States (New Orleans OPCD case; national implications)","publishedAt":"2026-08-10","publicationDate":"2026-08-10","eventDate":null,"sourceName":"Northeastern Global News","sourceLabel":"University news interview with EMS/dispatch expertise and EPIC privacy commentary","sourceUrl":"https://news.northeastern.edu/2026/08/10/ai-answering-911-calls/","evidenceClass":"independent-reporting","outcomeClass":"cautionary","topics":["operating-model","governance-procurement","accessibility-workforce","data-security"],"finding":"Reporting clarifies that Orleans Parish Communication District’s AI is used only for a narrow category of 911 calls near an already-reported vehicle crash when dispatchers are busy—not general bot-answered 911 as some headlines claimed. Northeastern professor Stephen Wood (former MedFlight paramedic) argues AI can augment surge duplicate handling but warns the biggest failure mode is mistaking separate nearby incidents for one, missing coded distress (e.g., domestic violence ‘pizza’ calls), suicidal ideation cues, and regional dialect clinical shorthand. EPIC’s Mayu Tobin-Miyaji urges limits against mission creep to full 911 handling or broadened surveillance and unnecessary data collection. Wood concludes complex dispatching tasks are not ready for AI replacement.","sledRelevance":"Pass-2 scrutiny for PSAP AI programs launching non-emergency or duplicate-triage tools (including today’s CSPD Axon launch and NTIA’s measured early adopters): stresses narrow scope, human routing for medical/distress, and anti-mission-creep governance.","evidence":"Opened Northeastern article. Combines OPCD scope clarification with expert interviews—not a new quantitative trial. Some radius figures appear as 200-meter (OPCD statement) and 20 meters (Wood paraphrase)—treat operational geofence details as reported with possible inconsistency and verify locally.","architectureImplications":"If implementing duplicate-incident AI, hard-constrain geofence/category, keep busy-human precondition, and default all medical/distress/other categories to humans. Log near-miss separate-incident cases.","governanceImplications":"Ban silent expansion from duplicate-MVA triage to general 911 answering; require public scope statements, data-minimization, and periodic expert review of failure modes.","securityPrivacyImplications":"EPIC guidance: limit collection to necessity; avoid surveillance broadening via 911 AI. Protect call content used for training.","caveats":"August 2026 article used for why-now controls against current PSAP AI wave. Expert judgment and secondary reporting—not a controlled evaluation of Carbyne/OPCD outcomes. Radius figure inconsistency noted.","streamIds":["emergency-services"],"roles":{"sales":"Use Northeastern’s clarification to set honest scope with buyers: AI for narrow duplicate-crash surge when humans are busy—not headlines that bots answer 911. Discovery must probe separate-nearby-incident risk, coded distress handling, dialect clinical shorthand, and data-minimization limits urged by EPIC. Bounded engagement: a failure-mode and scope-lock workshop before expanding any 911-path AI. Unsupported claims include emotional-intelligence parity with dispatchers, safe full-call replacement, or zero risk of merging distinct incidents into one response plan.","engineering":"Fit geofenced duplicate-call classifiers that activate only under documented busy-human preconditions, with mandatory human paths for medical, distress, and non-matching categories. Integrate CAD live-incident correlation, telephony busy-state signals, keyword bypass lists, and full audit logging. Prerequisites include reliable caller/incident geolocation and medical-director-approved distress rules. Constraints: separate-incident confusion, coded domestic-violence language, and dialectal slang. Proof of value is red-team dual-crash scenarios, distress-code routing tests, and a dialect phrase battery—not vendor demo scripts alone.","delivery":"Deliver policy and technology together: publish the exact allowlisted categories, configure bypass rules, train staff on reclaiming AI-handled calls, and schedule quarterly red-team drills. Dependencies include CAD and AI vendors, privacy counsel, and the EMS medical director. Ownership: PSAP director owns scope; medical director owns clinical bypass. Skills adoption requires a clear mental model of when AI is in-path. Acceptance criteria include a documented allowlist, passing dual-incident and distress tests, and no production scope change without formal review—blocking silent mission creep."},"roleDetails":{"sales":{"customerProblem":"Agencies under staffing pressure face hype that AI can answer 911, while experts say only narrow surge triage is plausible.","stakeholders":["PSAP directors","Fire/EMS medical directors","Privacy counsel","City council oversight"],"discoveryQuestions":["What exact call categories can AI touch?","How are separate nearby incidents detected?","How are coded distress calls forced to humans?","What data is retained for training?"],"valueHypothesis":"Narrow, busy-only duplicate triage can reduce surge load if failure modes are tested and scope is locked.","potentialEngagement":"Scoped failure-mode and policy workshop before any 911-path AI expansion.","unsupportedClaims":["AI ready to replace call takers","No risk of merging distinct incidents","Dialect/distress handling solved"]},"engineering":{"fit":"Constrained duplicate-incident voice triage with geofence and category filters; all else to human queue.","architectureIntegration":"CAD correlation of active incidents + telephony busy state leads to AI path; comprehensive bypass rules for medical/distress keywords.","prerequisites":["Reliable geolocation","Live incident database","Keyword/distress bypass lists","Audit logging"],"constraints":["Separate-incident confusion","Coded language","Dialectal clinical slang","Headline-driven scope creep"],"security":"Minimize training data; prevent surveillance expansion; secure call audio used in models.","proofOfValue":["Red-team dual-crash scenarios","Distress-code routing tests","Dialect phrase battery"]},"delivery":{"work":"Write public scope, configure bypass rules, train staff on AI edge cases, schedule periodic red-teams.","dependencies":["CAD vendor","AI vendor","Privacy counsel","Medical director"],"ownership":"PSAP director owns scope; medical director owns clinical bypass rules.","skillsAdoption":"Dispatchers need clear mental model of when AI is in-path and how to reclaim calls.","governanceCheckpoints":["Public scope published","Privacy review","Quarterly failure-mode drill"],"acceptanceCriteria":["Documented category allowlist","Passing dual-incident and distress tests","No production scope change without review"],"risks":["Media misframing driving bad procurement","Silent expansion to general 911","Missed domestic-violence coded calls"]}},"retrievedAt":"2026-09-22T22:16:45-05:00","enrichedAt":"2026-09-22T22:17:50-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Dialect and coded-language limits disproportionately risk underserved callers if AI scope expands; workforce still required for nuanced empathy and investigation of incomplete callers.","procurementImplications":"Contracts should hard-limit categories, ban silent scope expansion, and require failure-mode testing evidence.","operatingModelImplications":"Keep AI as surge duplicate assistant under dispatcher busyness constraints; preserve human compassion/empathy as core operating model.","sourceVerification":{"openedUrl":"https://news.northeastern.edu/2026/08/10/ai-answering-911-calls/","referenceExcerpt":"Government agencies should ensure that it doesn't lead to mission creep, such as deploying an AI system to handle 911 calls entirely","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}