Patent Description:
<CIT> describes systems and methods to guide an emergency dispatcher in responding to emergency calls involving a hate crime or other anti-social behavior. The systems and methods can include an emergency police dispatch protocol configured to facilitate uniform and consistent gathering of information about an incident being reported. The emergency police dispatch protocol includes one or more dispatch protocols configured for particular incidents or emergency situations, such as to aid the dispatcher in processing calls relating to anti-social behavior. The emergency police dispatch protocol presents a pre-scripted interrogation, including preprogrammed inquiries for a dispatcher to ask the caller. The pre-scripted interrogation of the dispatch protocol facilitates uniform and consistent gathering of information relating to hate crimes and other anti-social behavior. The information gathered can be stored and/or processed to determine a determinant value corresponding to an appropriate emergency dispatch response.

The invention is defined in the accompanying claims.

According to an aspect of the invention, there is provided a computer-implemented method according to claim <NUM>.

According to another aspect of the invention, there is provided a computer system according to claim <NUM>.

Non-limiting and non-exhaustive embodiments of the disclosure are described, including various embodiments of the disclosure with reference to the figures, in which:.

When a person intends to use or has used any type of weapon to inflict deadly physical force on others, the person may be referred to as an armed assailant. If an armed assailant continues or intends to continue inflicting deadly physical force while having unrestricted access to additional victims, the armed assailant may be referred to as an active assailant and/or an active shooter. An active assailant may be a shooter and/or may use any of a plurality of weapons, such as explosives, a knife, a blunt object, multiple weapons, or the like.

Active assailant events can quickly overwhelm the capabilities of emergency service agencies. Calls to emergency dispatchers can overload the number of phone lines available to an emergency dispatch center. Victims can outnumber available paramedic crews and emergency room beds. The size and scale of the event can easily exhaust available police resources. An event at a large public space or school can clog streets with anxious family members and/or parents. The clogged streets may make the response of additional units or the transport of the injured impossible. Accordingly, it can be important for emergency dispatchers to properly respond to calls reporting an active assailant event to minimize harm to callers and potential victims.

The goal of an active assailant may be to inflict as much death and misery as possible before police intervention. The active assailant may target large common areas where numerous potential victims may congregate, such as cafeterias. Historically, many active assailants have found most of their victims in the open or hiding in plain sight under desks or in corners. Active assailants may not spend much time trying to force entry into closed or locked rooms or offices, because attempting forced entry may slow them down, which is contrary to the goal of inflicting a high body count. Although the active assailant may have one or more specific targets, the active assailant may kill and/or injure anyone in their vicinity while locating a more specific target.

Traditionally, police responded to active assailants by surrounding and containing the scene before waiting for specialized units, such as SWAT teams, to arrive and take over. However, the active assailant may continue to inflict harm during the delay before the specialized units arrive. It may be more effective for police to respond by deploying patrol officers rapidly to the scene. The responders may attempt to locate the active assailant as quickly as possible and contain or neutralize the active assailant. The responders may deploy in teams of two to four officers. The responders may move quickly towards any evidence of the current location of the active assailant, such as the sound of gunfire. If no such evidence is present, they may move more slowly, clear rooms, and be attentive for any evidence and/or sounds indicative of the active assailant's location.

Active assailant incidents may be over in a matter of minutes. The short time frame may place police officers in a difficult position regarding officer and citizen safety and place emergency dispatchers in a critical role. Emergency dispatchers may be the first and/or only persons to interface with potential victims during an active assailant event. In their role of receiving emergency calls, emergency dispatchers are in a unique position and may potentially contribute to more positive outcomes by providing callers with critical lifesaving instructions and by conducting a precise caller interrogation to gather specific information that will assist police officers in determining the appropriate deployment tactics. Unfortunately, often emergency dispatchers are inexperienced and unskilled, largely due to a high turnover rate among emergency dispatchers.

An automated emergency dispatch system, potentially implemented on a computer, can aid even an unskilled and inexperienced dispatcher in prioritizing emergency calls that are received and in processing the calls to generate an appropriate emergency dispatch response. Regardless of the experience or skill level of the dispatcher, the automated emergency dispatch system can enable a consistent and predictable emergency dispatch response, despite the diverse aspects of emergency situations that may be reported from one call to the next.

Although existing automated emergency dispatch systems can enable receiving and processing of widely divergent aspects of emergency situations, these systems may not be well suited for processing particular types of unique situations. More particularly, an automated emergency dispatch system may not be well suited to respond to the short time frames of active assailant events, provide the information needed by first-responding patrol officers, and/or provide effective instructions to callers. An active assailant event may require special processing to enable the quick response time and to provide the particular caller advice necessary. Additional interrogation and instructions and/or alternative emergency dispatch procedures or protocols may facilitate more positive results from active assailant events.

Existing automated emergency dispatch systems are not equipped to assist or enable a dispatcher to process an emergency call involving an active assailant. A dispatcher unfamiliar with active assailant events and/or untrained in handling the same may not be able to compensate for the shortcomings of an automated emergency dispatch system. Inexperienced and/or unskilled dispatchers are generally unable to initiate or assist a proper police response, nor provide effective advice to callers. Even highly skilled and experienced dispatchers may have little skill or experience with handling incidents involving active assailants, simply because such incidents may be relatively rare compared to other types of incidents that are reported. Accordingly, the present disclosure provides a method and system for processing of emergency calls involving active assailant events in a rapid, consistent, and predictable manner.

The embodiments of the disclosure will be best understood by reference to the drawings, wherein like parts are designated by like numerals throughout. It will be readily understood that the components of the disclosed embodiments, as generally described and illustrated in the figures herein, could be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the systems and methods of the disclosure is not intended to limit the scope of the disclosure, as claimed, but is merely representative of possible embodiments of the disclosure. In addition, the steps of a method do not necessarily need to be executed in any specific order, or even sequentially, nor need the steps be executed only once, unless otherwise specified.

In some cases, well-known features, structures or operations are not shown or described in detail. Furthermore, the described features, structures, or operations may be combined in any suitable manner in one or more embodiments. It will also be readily understood that the components of the embodiments as generally described and illustrated in the figures herein could be arranged and designed in a wide variety of different configurations.

Several aspects of the embodiments described will be illustrated as software modules or components. As used herein, a software module or component may include any type of computer instruction or computer-executable code located within a memory device and/or computer-readable storage medium. A software module may, for instance, comprise one or more physical or logical blocks of computer instructions, which may be organized as a routine, program, object, component, data structure, etc. that performs one or more tasks or implements particular abstract data types.

In certain embodiments, a particular software module may comprise disparate instructions stored in different locations of a memory storage device, which together implement the described functionality of the module. Indeed, a module may comprise a single instruction or many instructions, and may be distributed over several different code segments, among different programs, and across several memory devices. Some embodiments may be practiced in a distributed computing environment where tasks are performed by a remote processing device linked through a communications network. In a distributed computing environment, software modules may be located in local and/or remote memory storage devices. In addition, data being tied or rendered together in a database record may be resident in the same memory device, or across several memory devices, and may be linked together in fields of a record in a database across a network.

Suitable software to assist in implementing the invention is readily provided by those of skill in the pertinent art(s) using the teachings presented here and programming languages and tools, such as Java, Pascal, C++, C, database languages, APIs, SDKs, assembly, firmware, microcode, and/or other languages and tools.

An emergency dispatch system as disclosed herein may be computer-implemented in whole or in part on a digital computer. The digital computer includes a processor performing the required computations. The computer further includes a memory in electronic communication with the processor to store a computer operating system. The computer operating systems may include, but are not limited to, MS-DOS, Windows, Linux, Unix, AIX, CLIX, QNX, OS/<NUM>, and Apple. Alternatively, it is expected that future embodiments will be adapted to execute on other future operating systems. The memory may also store application programs including a Computer Aided Dispatch (CAD) program, an automated emergency dispatch protocol, and a user interface program. The memory may also include data storage. The computer may further include an output device, such as a display unit, for viewing the displayed instructions and inquiries and a user input device for inputting response data.

<FIG> is an emergency police dispatch system <NUM>, according to one embodiment. At a dispatch center <NUM>, a dispatcher <NUM> may operate a computer <NUM> or other computing device. The computer <NUM> may include a memory <NUM> to store protocols, modules, tools, data, etc. The computer <NUM> may be configured to follow an emergency police dispatch protocol <NUM> to enable the dispatcher <NUM> to rapidly and consistently address an emergency incident involving a crime, or otherwise requesting law enforcement, as reported by a caller <NUM>. An emergency call requesting law enforcement may report an incident that may involve a victim <NUM>. As can be appreciated, in some circumstances and/or incidents, the caller <NUM> is the victim <NUM>. In other instances the caller may be a 2nd party (e.g., a person with the victim <NUM>), 3rd party (e.g., a person not in the immediate vicinity of the victim), 4th party (e.g., a reporting or referral agency), or the suspect (or perpetrator). The emergency police dispatch protocol <NUM> may include a logic tree, preprogrammed inquiries or questions, possible responses from a caller <NUM> to the inquiries, and instructions to the caller <NUM>. The responses may route to subsequent preprogrammed inquiries and/or instructions to the caller <NUM>. The emergency police dispatch protocol <NUM> may also include dispatch protocols <NUM> for guiding the dispatcher <NUM> in processing emergency calls involving specific situations and/or incidents. The dispatch protocols <NUM> may similarly include a logic tree, preprogrammed inquiries or questions, possible responses from a caller <NUM> to the preprogrammed inquiries, and instructions for the caller <NUM>. The dispatch protocols <NUM> may include an active assailant protocol <NUM> for rapid, consistent, and predictable processing of emergency calls involving active assailants.

The responses of the caller <NUM> are processed according to predetermined logic of the logic tree of the emergency police dispatch protocol <NUM>. The predetermined logic may enable the emergency police dispatch system <NUM> to provide to the dispatcher <NUM> information concerning the correct emergency police dispatch response (e.g., by trained law enforcement officers or agencies and/or other emergency responders). The predetermined logic may also enable the emergency police dispatch system <NUM> to provide to the dispatcher <NUM> appropriate post-dispatch instructions for relay to the caller <NUM> before professional help arrives at the scene. The predetermined logic may also enable the emergency police dispatch system <NUM> to aid the dispatcher in determining an appropriate priority of the emergency call, including but not limited to a priority of the emergency call relative to other emergency calls and a level of emergency response to provide for the reported incident or situation.

Although an emergency police dispatch system <NUM> is disclosed and described herein, a person of ordinary skill can appreciate that other emergency dispatch systems and protocols are contemplated, including but not limited to emergency medical dispatch systems and protocols and emergency fire dispatch systems and protocols. Exemplary embodiments of emergency dispatch systems and protocols are disclosed in <CIT>; <CIT>; <CIT>; <CIT>; <CIT>; <CIT>; <CIT>; <CIT>;<CIT>;<CIT>; <CIT>; <CIT>; <CIT>; <CIT>; <CIT>; <CIT>; <CIT>; and <CIT>.

The computer <NUM> operates a determinant value calculator <NUM> to calculate a determinant value from the responses of the caller <NUM> to protocol questions. The determinant value may be selected from a group of pre-established determinant values, such that the emergency responders are familiar with the determinant values and understand the meaning of each and what would be a corresponding emergency response. For example, the determinant values may range, for example, from E-<NUM> for generally very serious emergencies to Ω-<NUM> for generally less serious emergencies. The determinant value may provide a categorization code of the type and level of the incident.

In one embodiment of the present disclosure, the determinant value is a combination of a determinant level (Alpha A, Bravo B, Charlie C, Delta D, Echo E and Omega Ω) and a numeric value. Generally, Ω-<NUM> is the least serious while E-<NUM> is the most serious call. Depending on the determinant level, the appropriate emergency response is dispatched as indicated by the response protocol. For example, an Alpha-A call will typically be responded to by a next available law enforcement unit using the safest arrival method reasonably possible. A Delta-D call will typically be responded to by any or all available law enforcement units proceeding under the most urgent method possible. Echo-E calls typically involve likely immediate life-threatening situations and will be responded to in the most urgent manner available. Bravo-B and Charlie-C calls are intermediate calls that are typically responded to in business-like, orderly manner according to specific department protocol. An Omega-Ω call is generally not specifically responded to, but rather is referred to another person or agency. For the purposes of this disclosure, Echo-E is generally abbreviated as E; Delta-D is generally abbreviated as D; Charlie-C is generally abbreviated as C; Bravo-B is generally abbreviated as B; Alpha-A is generally abbreviated as A; and Omega-Ω is generally abbreviated as Ω. Generally, the lower determinant levels (e.g., numbers) within a determinant classification are more urgent than higher numbers. For example, an emergency dispatch call with a determinant value of D-<NUM> is generally more critical and requires a more urgent response than a call with a determinant value of D-<NUM>. However, in some instances, the numeric determinant levels within a determinant value may serve only to identify the type, rather than criticality of the call. Also, if more than one determinant value can be assigned to a particular call, the more critical or higher determinant value is assigned. That is, the call is assigned a criticality determinant value based on the fact or aspect that would lead to the most urgent response. For example, if the call concerns a burglary that occurred over <NUM> minutes before, but where the suspect remains on the scene or nearby and the caller indicates that he or she is still in danger and feels his or her life is in imminent danger, then the determinant value assigned would be E-<NUM> (due to the imminent danger) rather than D-<NUM> (suspect on scene or nearby) or B-<NUM> (incident occurred over <NUM> minutes before).

Many calls for law enforcement are not true emergencies, so it is important to prioritize the calls in several ways. First, calls that are true emergencies should be dispatched first. Second, if an agency has units with different capabilities, the emergencies involving more severe problems can be sent units that are more skilled and advanced (e.g., a S. team or bomb squad). And finally, if lights-and-siren are not needed, they should not be used, thereby increasing the safety of all those on the road and in the emergency response vehicles. The computer <NUM> presents the determinant value to generate an appropriate emergency dispatch response and/or establish the priority of the emergency call. The response may include dispatching professional law enforcement officers or other emergency responders to the scene of the emergency. The protocols used shall have passed through a rigorous review by a panel of experienced law enforcement agents and EMS public safety experts.

The determinant value may be provided to a Computer Aided Dispatch (CAD) system <NUM>, which is a tool that a dispatcher <NUM> may use to track and allocate emergency response resources for processing emergency calls. The CAD system <NUM> may manage dispatcher tools for processing emergency calls, including but not limited to the emergency police dispatch protocol <NUM>, communication resources (e.g., radio system, alpha pager), mapping tools (e.g., global positioning system (GPS) technology, geographic information systems (GIS)), and vehicle location systems (e.g., automatic vehicle location (AVL)). The CAD system <NUM> may operate in whole or in part on a separate computer in communication with the computer <NUM>. In another embodiment, the CAD system <NUM> operates on the computer <NUM>. The primary information used by the CAD system <NUM> is location information of the incident and units, unit availability, and the type of incident. The CAD system <NUM> may use third party solutions, such as E-<NUM>, vehicle location transponders, and mobile data terminals (MDT's) for automating the location and availability tasks. The CAD system may also use an emergency police dispatch protocol <NUM> to facilitate structured call taking for incident interrogation, as previously described.

Although many emergency calls are not true emergencies, all situations can benefit from expert evaluation and pertinent instruction. Prior to the arrival of professional help on-scene, the emergency police dispatch protocol <NUM> may provide the dispatcher <NUM> with instructions for the caller <NUM> that are appropriate to the type of call, whether the call relates to a complaint of vandalism or to a homicide. These instructions may help expedite the work of law enforcement officers and/or other emergency responders.

The computer <NUM> may include a reporting component <NUM> to statistically measure the performance of individual staff and overall performance of the dispatch center <NUM>. To record information received during a call, the dispatcher <NUM> may be required to open a new case. Once the call is complete, the dispatcher <NUM> may close the case, and a case summary may be saved. The case summary may be retrieved later for review and/or analysis. The reporting component <NUM> may determine statistics from the case summaries and/or while the cases are open. The statistics may include compliance rates, call processing statistics, and peer measurements.

The computer <NUM> may further comprise an input device <NUM>, such as a keyboard, mouse, touch screen, laser pointer, or other input device, and also an output device <NUM>, such as a display monitor. The input device <NUM> receives input from a user (generally a dispatcher) and provides the input to the emergency police dispatch system <NUM>. The input may be provided to the computer <NUM>, the emergency protocol <NUM>, the diagnostic tool <NUM>, and/or the CAD system <NUM>. An output device <NUM> receives output from the emergency police dispatch system <NUM> and displays or otherwise provides the output to the user. In another embodiment, the input device <NUM> and output device <NUM> are provided by the CAD system <NUM>.

The dispatch center <NUM> includes a communication device <NUM> (e.g., telephone equipment) to answer emergency calls. In some embodiments, the communication device <NUM> may be coupled to the computer <NUM> to enable the computer <NUM> to send and/or receive text messages and/or to identify dual-tone multi-frequency (DTMF) signals received at the communication device <NUM>. A call into the dispatch center <NUM> from a caller <NUM> may initiate creation of an emergency call incident. The dispatcher <NUM> identifies the call as requiring an emergency police dispatch, and the emergency police dispatch protocol <NUM> is accessed. The protocol <NUM>, including the dispatch protocols <NUM>, may provide questions and/or instructions that are expertly drafted to assist a novice caller <NUM> in reporting aspects of the incident, and/or assessing a situation of a victim <NUM>. The protocol <NUM> may also provide expertly drafted instructions to assist a victim <NUM> prior to the arrival of trained law enforcement and/or emergency responders. The instructions may be vocally relayed by the dispatcher <NUM> to the caller <NUM> over the communication device <NUM>.

Some protocol inquiries or questions may be readily answerable by the caller <NUM>, whereas others may be more difficult to answer. Certain diagnostic inquiries may be difficult for the untrained caller to determine or may be difficult to answer under the stress of an emergency situation. Accordingly, in addition to instructions, the emergency police dispatch system <NUM> may provide one or more computer-implemented diagnostic tools <NUM>. The diagnostic tools <NUM> may greatly improve information collection and intervention for emergency police response situations and aid in saving lives.

A diagnostic tool <NUM> may aid the dispatcher <NUM> and/or the caller <NUM> (via instructions from the dispatcher <NUM>) in assessing a situation of a victim <NUM>. A diagnostic tool <NUM> may also be an interventional tool, providing instructions that direct a caller <NUM> to intervene, or take action, to aid a victim <NUM>, or otherwise change the circumstances or conditions of an emergency situation. For sake of clarity, diagnostic tools and interventional tools are both referred to herein generally as diagnostic tools. Accordingly, a diagnostic tool <NUM>, as referred to herein, may provide diagnostic instructions, interventional instructions, or both diagnostic and interventional instructions. Whether a diagnostic tool <NUM> provides merely diagnostic instructions, merely interventional instructions, or both diagnostic and interventional instructions, the diagnostic tool provides consistent and reliable instruction, information gathering, and/or timing for a particular emergency situation.

The diagnostic tools <NUM> are computer implemented software modules that enable a dispatcher <NUM> to provide consistent, expert advice to assist a caller with regards to a particular aspect of an emergency situation, such as determining a vital sign. One benefit of the diagnostic tools <NUM> is the computer-aided timing of techniques to determine the vital signs. In highly stressful conditions, the diagnostic tools <NUM> provide a necessary resource to reading critical signs. The diagnostic tools <NUM> may be stored in the memory of the computer <NUM> and initiated and executed as required. The diagnostic tools <NUM> may be embodied as computer-executable software applications and associated data.

The emergency police dispatch protocol <NUM>, including the dispatch protocols <NUM>, also may call on one or more diagnostic tools <NUM> to assist with an inquiry and may route to the appropriate diagnostic tool <NUM> when needed. When directed according to the protocol, the emergency police dispatch protocol <NUM> may automatically, i.e., without dispatcher intervention, initiate the appropriate diagnostic tool <NUM>. This may occur when the emergency police dispatch protocol <NUM> arrives at a diagnosis or assessment step in the logic tree. The emergency police dispatch system <NUM> may also allow the dispatcher <NUM> the option to call upon a diagnostic tool <NUM> as desired. Icons may be displayed in a tool bar or other convenient location on a user interface to allow the dispatcher <NUM> to initiate a corresponding diagnostic tool <NUM>.

<FIG> is a high-level flow diagram of an emergency police dispatch protocol <NUM> of an emergency police dispatch system, according to one embodiment. The protocol <NUM> may begin with a case entry protocol <NUM> that guides the dispatcher in gathering initial information. One aim of the case entry protocol <NUM> is to obtain sufficient information from the caller to permit identification of a chief complaint. Also, the case entry protocol <NUM> may be considered a primary interrogation because all calls may be processed through the case entry protocol <NUM> to gather initial incident information. The information received through the case entry protocol <NUM> may include a location of the incident, a call-back number in the event the call is disconnected, the caller's name, and a description of the incident.

If the dispatcher receives and enters information that an incident is especially critical (e.g., an active assailant, a caller in imminent danger, a sinking vehicle, a vehicle in rising flood water, or a stuck accelerator and cannot stop vehicle), for whatever reason, an emergency response is dispatched <NUM> immediately, before continuing with any further interrogation or instructions. The dispatched <NUM> emergency response may be a maximum emergency response, including properly trained law enforcement officers. The criticality of the incident <NUM> is verified and pre-arrival instructions are given <NUM>. The pre-arrival instructions can be tailored to the specific incident and/or situation. Typically, a result of properly conveyed (by the dispatcher) and executed (by the caller) pre-arrival instructions may be a more calm, stable situation at the time the law enforcement emergency responders arrive, and/or reduced risk of injury or death for the caller. The pre-arrival instructions may aid to ensure safety and improve the effectiveness of the dispatched <NUM> emergency response.

If the dispatcher receives information from the caller to confirm the incident is not critical (e.g., not an imminent danger), but the dispatcher lacks sufficient information to proceed directly to a dispatch protocol <NUM>, the emergency police dispatch protocol <NUM> may shunt to additional inquiries <NUM> designed to guide the dispatcher to gather information from the caller to enable the dispatcher to ascertain the chief complaint. If the chief complaint is determined, the emergency police dispatch protocol <NUM> may shunt to the appropriate dispatch protocol <NUM> for dealing with that chief complaint.

The dispatch protocol <NUM> may guide the dispatcher through a secondary interrogation focusing on the chief complaint. The dispatch protocol <NUM> may present a pre-scripted interrogation to enable a more orderly and detailed understanding of the incident that can be communicated to law enforcement emergency responders. The pre-scripted interrogation may include preprogrammed inquiries focused on gathering information relating to the chief complaint. The preprogrammed inquiries provided by the dispatch protocol <NUM> may be termed "Key Questions" for the particular situation or condition of the chief complaint. The preprogrammed inquiries presented may depend on caller responses. Verifying <NUM> the criticality of the incident and giving <NUM> pre-arrival instructions may include traversing the logic tree of the dispatch protocol <NUM>. Dispatch protocols <NUM>, in general, are discussed in greater detail below with reference to <FIG>. The instant disclosure includes, inter alia, a dispatch protocol <NUM> configured to process an emergency call involving an active assailant, namely a dispatch protocol <NUM> including an active assailant protocol <NUM>. The active assailant protocol <NUM> will be discussed in greater detail below with reference to <FIG>, <FIG>, and <FIG>.

During the dispatch protocol <NUM>, the dispatcher and/or the emergency police dispatch protocol <NUM> will gather information about the circumstances of the incident or emergency situation, discovered through interrogation, and may dispatch <NUM> an appropriate emergency dispatch response. The dispatch protocol <NUM> facilitates uniform and consistent gathering of information relating to the emergency and dispatching of an appropriate emergency dispatch response. The appropriate emergency dispatch response may be determined through a system of assigning determinant values as the protocol progresses (i.e., traverses) through a logic tree. The determinant values, as described above, may range, for example, from E-<NUM> for generally very serious emergencies to Ω-<NUM> for generally less serious emergencies. In another embodiment, the determinant values may range from, for example, E-<NUM> for generally very serious emergencies to A-<NUM> for generally less serious emergencies. In still another embodiment, the determinant values may range differently, such as for example from A-<NUM> for generally very serious emergencies to E-<NUM> for generally less serious emergencies.

After the appropriate emergency dispatch response has been sent (e.g., law enforcement officers), the dispatcher may remain on the telephone with the caller to provide post-dispatch instructions <NUM> regarding what to do, and what not to do, prior to the arrival of law enforcement officers. The post-dispatch instructions <NUM> help to stabilize the situation, and to expedite the work of law enforcement officers at the scene. Post-dispatch instructions may include, for example, "do not disturb anything at the scene, including weapons, tools, or objects found nearby," "stay on the line and I'll tell you exactly what to do next," and the like.

<FIG> are a user interface <NUM> of an emergency police dispatch system, according to one embodiment. The emergency police dispatch system user interface <NUM> allows a dispatcher to interface with the emergency police dispatch protocol. The illustrated user interface <NUM> is shown traversing a case entry protocol <NUM> of the emergency police dispatch protocol <NUM> (described above with reference to <FIG>). The emergency police dispatch protocol may present inquiries <NUM> (or questions) via the emergency police dispatch system user interface <NUM>. The inquiries <NUM> are provided for the dispatcher to relay to the caller to gather information regarding the reported incident or emergency. The dispatcher and/or the emergency police dispatch system may gather the information in the form of caller responses to the inquiries <NUM>. The dispatcher may input the responses of the caller to the inquiries into response fields <NUM> provided by the user interface <NUM>. The response fields <NUM> may include, for example, any of a number of appropriate input field types, including but not limited to text fields, text boxes, menus, drop down menus, drop-down selection boxes, lists, buttons, check boxes, radio buttons and/or hybrid fields. For example, a text field for identifying the problem may allow for freeform input but also provide a list of suggestions (e.g., echo situations <NUM>) to the dispatcher that can be inserted into the text field by clicking and/or double clicking an entry in the list. The response fields <NUM> may correspond to information indicative of one or more responses of the caller to the inquiries <NUM>. In some embodiments, the inquiries <NUM> may change from an interrogative form to an assertional form after a response has been entered and/or when a cursor is not in the corresponding response field.

The caller responses are relayed from the caller to the dispatcher, typically over the telephone. Information from the caller responses may be input into the system by the dispatcher and may be used by the emergency police dispatch protocol to determine subsequent inquiries <NUM> and instructions to present to the dispatcher. The caller response information may indicate the caller's observations of the incident and/or current situation. The emergency police dispatch system may use the caller response information to generate an emergency police dispatch response by properly trained law enforcement officers. The information gathered from the caller responses may be used by the determinant value calculator to calculate a determinant value that can be communicated to the emergency responders. Additional details relating to emergency police dispatch protocols and user interfaces to interact with the same can be found in the earlier referenced U. In addition, similar concepts are discussed below in relation to a dispatch protocol, in particular an active assailant protocol, with reference to <FIG>, <FIG>, and <FIG>.

The user interface <NUM> may further comprise tabs <NUM> to aid in organizing and/or compartmentalizing various aspects of processing a call. The tabs <NUM> may include a tab 310a for presenting a case entry protocol portion of an emergency police dispatch protocol (e.g., "Entry" tab). Other tabs may include a tab 310b for presenting a dispatch protocol portion of the emergency police dispatch protocol (e.g., a "KQ" tab or Key Questions tab), a tab for presenting post-dispatch instructions and/or critical EMD information (e.g., a "PDI/CEI" tab), a tab for dispatching life support (e.g., a "DLS" tab), and a tab summarizing the call and/or processing of the call (e.g., "Summary" tab). The KQ tab, PDI/CEI tab, DLS tab, and Summary tab are discussed below with reference to <FIG>.

If the caller indicates that the problem is one of a predetermined set of echo situations <NUM>, the dispatcher may be able to select that problem from a list. In response, the case entry protocol <NUM> may automatically jump to the KQ tab 310b and may provide an input, such as a send determinant button <NUM>, allowing the dispatcher to set a determinant value of E-<NUM> and/or send the determinant value and/or case entry responses to the CAD system <NUM>. The determinant value may also include a prefix indicative of the type of incident, such as "<NUM>" for active assailant incidents. Police officers and/or other emergency personnel may be dispatched immediately in the most urgent manner available once the determinant value has been sent. Once the determinant value has been set, post-dispatch instructions may be provided, such as "I'm sending help to you now. Stay on the line, and I'll tell you exactly what to do next. " Next, the case entry protocol <NUM> may continue where it left off but allow the dispatcher to retrieve the previously provided dispatch instructions if need be using a post-dispatch instructions button <NUM>. The user interface <NUM> may include an indication <NUM> of the current determinant value once one has been set.

The user interface <NUM> may provide an input component <NUM> for the dispatcher to indicate when the portion of the emergency police dispatch protocol presented by the tab 310a has been completed. The input component <NUM> may be a navigation button, as illustrated in <FIG>, to enable a dispatcher to provide input that indicates to the user interface <NUM> that the dispatcher is ready to proceed to a next phase of the emergency police dispatch protocol. The dispatcher may also be able to double click on a chief complaint, use arrow keys, tabs, and/or the enter or return key to indicate a chief complaint, or the like to jump to the portion of the dispatch protocol <NUM> for that complaint.

<FIG> is a high-level flow diagram of a method <NUM> implemented by a dispatch protocol <NUM> (<FIG>) for an emergency dispatch system, according to one embodiment. The dispatch protocol <NUM> may include an active assailant protocol <NUM>, an example of which is described in greater detail below with reference to <FIG> and <FIG>. The dispatch protocol facilitates uniform and consistent gathering of information relating to the reported chief complaint. Generally, but not always, the dispatch protocol initializes from a prior protocol. The prior protocol may be a case entry protocol. In some instances the prior protocol may be a different dispatch protocol, from which a determination was made to shunt to a more appropriate dispatch protocol. The determination to shunt may be made automatically by the prior protocol or manually by the dispatcher. For a call involving an active assailant, the appropriate dispatch protocol may be an active assailant protocol, such as the active assailant protocol <NUM> described below with reference to <FIG> and <FIG>.

The dispatch protocol may present <NUM> preprogrammed inquiries according to a pre-scripted interrogation. The preprogrammed inquiries may also be referred to as "Key Questions," targeted to ascertain the criticality of the incident or situation and typically are based on the chief complaint. Data is received <NUM> from the dispatcher, as relayed from the caller, following the preprogrammed inquiries asked to the caller by the dispatcher. The data received <NUM> may correspond to caller responses to the preprogrammed inquiries. The data may be used to determine subsequent questions, or to determine instructions to provide to the dispatcher. The received data is also used by the protocol to determine <NUM> a determinant value and/or update an already determined determinant value. Intermediate determinant values may be produced as information is received and processed, and the final determinant value may be determined after all information is received and processed.

The dispatch protocol may provide <NUM> appropriate instructions to be relayed to the caller by the dispatcher. The instructions may comprise post-dispatch instructions for the caller to help stabilize or otherwise ameliorate a situation and to expedite the work of law enforcement officers at the scene. In one embodiment, the dispatch protocol may include an active assailant protocol. A database may be accessed to produce appropriate instructions. Records of the calls are stored <NUM> for historical reports, for review and analysis of dispatcher performance, and for continued quality assurance control. A record of a call may include, but is not limited to inquiries, responses, and determinant values.

<FIG> are a detailed flow diagram of a method <NUM> implemented by an active assailant protocol <NUM> (<FIG>) for an emergency dispatch system, according to one embodiment. The active assailant protocol <NUM> is initialized, typically, from a prior protocol. In particular, the active assailant protocol <NUM> may be launched from the case entry protocol. As can be appreciated, the active assailant protocol <NUM> may be accessed a variety of ways. In an embodiment, the active assailant protocol <NUM> may initialize once the emergency dispatch protocol has traversed all or a portion of a case entry protocol and shunts to the active assailant protocol <NUM> as the appropriate dispatch protocol for handling the chief complaint of the call. Also, an emergency police dispatch protocol may automatically shunt to the active assailant protocol <NUM> immediately upon receiving indication that an active assailant event is being reported.

The active assailant protocol <NUM> may present to the dispatcher a series of preprogrammed inquiries. The preprogrammed inquiries may be considered a part of a pre-scripted interrogation that is based on a logic tree of the active assailant protocol <NUM>. (The flow diagram of <FIG> may be considered to portray a logic tree, according to one embodiment). The preprogrammed inquiries that are presented as part of a pre-scripted interrogation may depend on dispatcher-entered input as will be described. A pre-scripted interrogation may be considered to be a set of preprogrammed inquiries presented according to traversal of a path along the logic tree.

During a pre-scripted interrogation, the active assailant protocol <NUM> may receive input from the dispatcher corresponding to instructions and preprogrammed inquiries, as was explained above with reference to <FIG>. The input may be received substantially in real-time, as the dispatcher provides the input. Alternatively, or in addition, the input may be received from the emergency police dispatch system <NUM> because information sought by the active assailant protocol <NUM> may have previously been obtained from the dispatcher via the case entry protocol and/or another portion of the dispatch protocol <NUM>. Alternatively, or in addition, the input may be received from a diagnostic tool <NUM>. While explicit steps of receiving information are not depicted in <FIG>, an ordinarily skilled artisan will recognize that input may be received at various points in the method <NUM> of the active assailant protocol <NUM>.

The dispatcher-entered input relates to the emergency call and/or the reported incident. The dispatcher-entered input may affect the path along which the logic tree is traversed. Various paths through one embodiment of a logic tree of an active assailant protocol <NUM> will now be described, including the corresponding preprogrammed inquiries and potential dispatcher-entered input that may be considered.

The active assailant protocol <NUM> may initially seek critical information necessary for responder safety before providing any additional post-dispatch and/or pre-arrival instructions. The information collected can heavily influence the tactics utilized by responders and law enforcement administration and can also benefit EMS and Fire agencies that may be assisting with the incident. The dispatcher may be presented <NUM> a preprogrammed inquiry, "Are you at that location now?," to relay to the caller. The dispatcher may input an affirmative or negative response and/or a freeform text response. A determination <NUM> may be made whether the caller is the victim, a 2nd party, a 3rd party, a 4th party, or a suspect. The active assailant protocol <NUM> may present a preprogrammed inquiry to the dispatcher (which may be relayed to the caller) inquiring what party the caller is and present options such as "2nd party," "3rd party," "4th party," or "Suspect" and/or the information may have been previously gathered as part of the case entry protocol or as part of an earlier dispatch protocol. The caller location and caller identity may allow the dispatcher to quickly triage a large volume of calls. In an embodiment, if the caller is not on scene and/or is a 3rd or 4th party, then the active assailant protocol <NUM> may automatically end and/or allow the dispatcher to close the case. In other embodiments, the dispatcher may be required to ask additional critical safety questions before the case can be closed.

The dispatcher may be presented <NUM> a preprogrammed inquiry, "What type of weapons are involved?" Possible responses presented to the dispatcher may include "Gun:," "Multiple:," Knife:," "Club:," "Explosive:," "Other:," and "Unknown:. " For any response, the active assailant protocol <NUM> may present <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> a preprogrammed inquiry and/or prompt to input the type(s) of weapons involved. The dispatcher may input the type of weapon into a freeform text box, and/or the dispatcher may receive suggestions of possible weapon types. If a gun or multiple weapons are involved, the dispatcher may be presented <NUM>, <NUM> with a preprogrammed inquiry, "How many shots have been fired?" The dispatcher may be able to input the response into a freeform text box, select a preprogrammed response of "Unknown," and/or, for multiple weapons, select a preprogrammed response of "Not Appropriate" or "Not Applicable. " If a response other than "Not Appropriate" is selected, the dispatcher may be presented <NUM>, <NUM> with a preprogrammed inquiry, "When was the last time you heard shots fired?" The dispatcher may be able to input the response into a freeform text box and/or select a preprogrammed response of "Unknown.

The information about the weapon(s) may allow responding officers to determine what risks they face, which may be very different for handguns versus high-powered rifles. Similarly, responding officers may use a different tactical response for an active assailant with a knife versus an active assailant with a handgun. The number of shots fired and/or when the last shots were fired may allow the dispatcher and/or responding officers to determine the level of activity of the assailant. Additionally, asking when shots were last fired may allow the dispatcher to determine which callers have the most up-to-date information because of their proximity to the assailant.

The active assailant protocol <NUM> may update <NUM> the determinant value based on the information about the weapon(s). For example, a suffix indicative of the type of weapon may be added to the determinant value, such as "G" for gun, "M" for multiple, "K" for knife, "C" for club, "E" for explosive, and "O" for other or unknown. In some embodiments, the determinant level may not be changed based on the length of time since shots were last heard. In other embodiments, the determinant level may be changed based on the answers to the preceding preprogrammed inquiries.

The dispatcher may be presented <NUM> with a preprogrammed inquiry, "How many suspects are involved?" The active assailant protocol <NUM> may present possible responses, such as "One," "More than one (enter number):," which may launch a freeform text box for inputting an exact number, and "Unknown. " The active assailant protocol <NUM> may present <NUM> a preprogrammed inquiry, "Where's the suspect now?" Possible response presented to the dispatcher may include "On scene:," "Still in area:," "Left/leaving area," "Circulating the area," and "Unknown. " If the response indicates the suspect is on scene or still in the area, the active assailant protocol <NUM> may present <NUM> a freeform text box allowing the dispatcher to include additional detail describing the suspect's location.

If the response indicates that the suspect left the area, is leaving the area, or is circulating the area, the dispatcher may be presented <NUM> a preprogrammed inquiry, "How did s/he leave?" The dispatcher may be presented a plurality of possible responses, such as "Vehicle," "Boat," "On foot," "Motorcycle," "Bicycle," "Other:," and "Unknown. " If "Vehicle" or "Boat" is selected, the active assailant protocol <NUM> may present <NUM> a preprogrammed inquiry, "Obtain the vehicle description. " and preprogrammed responses of "Info:," which may launch a diagnostic tool for obtaining a description of the vehicle, and "Unknown. " The diagnostic tool for obtaining the description of the vehicle may include a plurality of inquiries and response fields for additional descriptive details about the vehicle. If "Other" is selected in response to preprogrammed inquiry <NUM>, a freeform text box may be presented <NUM> allowing the dispatcher to include additional information. In the illustrated embodiment, no additional information about the suspect's method of departure is requested if the suspect is on foot, on a motorcycle, on a bicycle, or the method of departure is unknown. In other embodiments, a vehicle description and/or other information may be obtained for these methods of departure. For any of the methods of departure, the dispatcher may be presented <NUM> a preprogrammed inquiry, "What direction was s/he going?" The dispatcher may be able to select a preprogrammed response, such as "Info:," which may launch a freeform text box for answering, and "Unknown.

After information about the suspect's location has been obtained, the active assailant protocol <NUM> may present <NUM> a preprogrammed inquiry, "Obtain the suspect's description. " Possible response options may include "Info:," which may launch a diagnostic tool for obtaining a description of the suspect, and "Unknown. " The diagnostic tool for obtaining the description of the suspect may include a plurality of inquiries and response fields for additional descriptive details about the suspect. In some embodiments, the suspect's description may be obtained before the suspect's location, or the preprogrammed inquiries may be arranged in a different order.

The dispatcher may be presented <NUM> a preprogrammed inquiry, "Can you safely evacuate/leave the building/area?" The active assailant protocol <NUM> may present preprogrammed responses, such as "Yes," "No," and "Unknown. " The response may determine which set of pre-arrival instructions should be given to the caller. If the caller answers "Yes," the dispatcher may be presented <NUM> with evacuation instructions to provide to the caller. If the caller answers "No" or "Unknown," the dispatcher may be presented <NUM> with lockdown to provide to the caller. Evacuation and lockdown instructions are described in more detail below with reference to <FIG>. Because phone contact may be lost, it may be beneficial to give the pre-arrival instructions early to prepare the caller to escape, hide, and/or defend themselves. In some embodiments, the pre-arrival instructions may be provided before the aforementioned inquiries are asked, and/or the dispatcher may be able to skip to the pre-arrival instructions before completing all of the previous inquiries. The pre-arrival instructions may be configured to remove potential victims from the immediate area and/or plain sight. The dispatcher may be able to return to the key questions after the caller has completed the pre-arrival instructions and/or called back.

If the caller answers "No" or "Unknown" to preprogrammed inquiry <NUM>, the dispatcher may be presented <NUM> with a follow-up preprogrammed inquiry, "Where exactly are you?" Preprogrammed responses may include "Info:," which may launch a freeform text box for answering, and "Unknown. " The dispatcher may also be presented <NUM> with a follow-up preprogrammed inquiry, "What's the best way to get to you?" Possible response options may include "Info:," which may launch a freeform text box for answering, and "Unknown. " The dispatcher may be presented <NUM> with another follow-up preprogrammed inquiry, "How many people are with you?" Preprogrammed responses may include "Info:," which may launch a freeform text box for answering, "Unknown," and "None.

The dispatcher may be presented <NUM> with a preprogrammed inquiry, "How many people are in the building/area?" Possible response options may include "Info:," which may launch a freeform text box for answering, and "Unknown. " The active assailant protocol <NUM> may present <NUM> a preprogrammed inquiry, "Does the suspect appear to be wearing a bulletproof vest or body armor?" The dispatcher may be presented by preprogrammed responses, such as "Yes," "No," and "Unknown. " The presence of body armor on the suspect may limit the effectiveness of responders' weapons and may indicate that the assailant has a higher level of preparation and skill.

The dispatcher may be presented <NUM> with a preprogrammed inquiry, "Did you see the suspect carrying anything. Preprogrammed responses may include "Yes," "No," and "Unknown. " If the caller answers "Yes," the dispatcher may be presented <NUM> the preprogrammed inquiry, "Describe it to me. " with a possible response of "Info:," which may launch a freeform text box for answering. If the suspect is carrying a backpack, duffle bag, ammunition can, or the like, it may indicate the suspect has explosives, chemical or biological weapons, extra ammunition, or other weapons that will hinder a law enforcement response.

The active assailant protocol <NUM> may present <NUM> the dispatcher with a preprogrammed inquiry, "Did you hear the suspect saying anything?" Possible preprogrammed responses may include "Yes," "No," and "Unknown. " If the caller answers "Yes," the dispatcher may be presented <NUM> the preprogrammed inquiry, "What did s/he say?" The response may provide insight into the suspect's motives, level of preparation, and intended target(s). For example, the suspect might have shouted the name of a person who is a specific target, and police officers may focus their response based on the target's likely location. Religious, racial, or political statements may be made by a suspect affiliated with a racist or terrorist group, which may indicate a higher level of training and/or access to weapons and/or explosives not usually encountered by police responders.

The active assailant protocol <NUM> may determine <NUM> whether the caller previously indicated the suspect has left the area, was leaving the area, or was circulating the area and/or if vehicle information was previously provided. If the caller did not indicate the suspect had left, was leaving, or was circulating, the dispatcher may be presented <NUM> with a preprogrammed inquiry, "Did s/he arrive in a vehicle?" Possible preprogrammed responses may include "Yes-vehicle," "Yes-boat," "No," and "Unknown. " If the caller responds "Yes-vehicle" or "Yes-boat," the active assailant protocol may present <NUM> a preprogrammed inquiry, "Obtain the vehicle description. " and preprogrammed responses of "Info:," which may launch a diagnostic tool for obtaining a description of the vehicle, and "Unknown. " In addition, the active assailant protocol may present <NUM> a preprogrammed inquiry, "Where's the vehicle now?" Preprogrammed responses may include "Info:," which may launch a freeform text box for answering, and "Unknown.

The dispatcher may be presented <NUM> with a preprogrammed inquiry, "Has the suspect taken any hostages?" The dispatcher may be presented with preprogrammed responses, such as "Yes," "No," and "Unknown. " If the caller answers "Yes," the dispatcher may be presented <NUM> with a preprogrammed inquiry, "How many?" The active assailant protocol <NUM> may present possible responses, such as "One," "More than one (enter number):," which may launch a freeform text box for inputting an exact number, and "Unknown. " The dispatcher may also be presented with a preprogrammed inquiry <NUM> "Exactly where are they?" Preprogrammed responses may include "Info:," which may launch a freeform text box for answering, and "Unknown.

The active assailant protocol <NUM> may present <NUM> the dispatcher with a preprogrammed inquiry, "How many people are injured?" The active assailant protocol <NUM> may present possible responses, such as "One," "More than one (enter number):," which may launch a freeform text box for inputting an exact number, and "Unknown. " Before ending, the active assailant protocol <NUM> may present <NUM> a preprogrammed inquiry, "Is there anything else you can tell me?" Possible responses may include "Yes (info):," which may launch a freeform text box for recording additional details, and "No." The active assailant protocol <NUM> may end, provide post-dispatch instructions, and/or provide dispatch life support after all questions have been answered.

As can be appreciated, some or all of the information gathered by the pre-scripted interrogation of the active assailant protocol <NUM> may not be used, for example, in calculating a determinant value. Similarly, some or all the information may not be communicated to the emergency responder law enforcement officers. However, the information gathered may be used, or stored for later use, by law enforcement and/or emergency dispatch services, for example, to review the response and/or identify ways to improve the response.

As can also be appreciated, the spelling and/or sentence structure of the preprogrammed inquiries may vary according to the geographic location or region where the emergency police dispatch system and/or active assailant protocol <NUM> may be deployed.

<FIG> are a user interface <NUM> of an emergency police dispatch system at various points as the emergency police dispatch system presents a pre-scripted interrogation, traversing one path of a logic tree of the active assailant protocol <NUM>, according to one embodiment. As previously explained above, with reference to <FIG>, the emergency police dispatch system user interface <NUM> allows a dispatcher to interface with the emergency police dispatch protocol. In particular, in the illustrated embodiment, the user interface <NUM> is facilitating traversal of the active assailant protocol <NUM>.

The user interface <NUM> presents one or more tabs <NUM>, including a tab 310b (e.g., a key questions or "KQ" tab) that is configured to present preprogrammed inquiries (e.g., key questions) as part of a pre-scripted interrogation of a dispatch protocol. The particular questions presented may depend on the dispatch protocol, in this case the active assailant protocol <NUM>, and the path along a logic tree of the dispatch protocol that may be traversed based on caller responses to the preprogrammed inquiries, as explained above with reference to <FIG>. Typically, but not always, the user interface <NUM> will present a tab 310b (e.g. a Key Questions or "KQ" tab) upon completion of the case entry protocol on tab 310a (i.e., the "Entry" tab"). If sufficient information is available to identify a chief complaint, the emergency police dispatch protocol may shunt to an appropriate dispatch protocol. In this case, the emergency police dispatch protocol has shunted to the active assailant protocol <NUM>, presented tab 310b, initialized the active assailant protocol <NUM>, and traversed the active assailant protocol <NUM>.

<FIG> illustrates the user interface <NUM> presenting a preprogrammed inquiry <NUM> "Can you safely evacuate/leave the building/area?" for the dispatcher to relay to the caller. An input field <NUM> enables the dispatcher to quickly and easily enter input indicative of the caller's response to the preprogrammed inquiry <NUM>. In the illustrated embodiment, the input field <NUM> provided is a list box presenting a list of acceptable inputs. As will be appreciated, the input field <NUM> may be any of a number of appropriate input field types, including but not limited to text fields, text boxes, menus, drop down menus, drop-down selection boxes, lists, buttons, check boxes, and radio buttons. In <FIG>, the list of acceptable inputs may include "Yes," "No," and "Unknown. " In <FIG>, the input "Yes," is presently selected.

The user interface <NUM> may present navigation buttons 675a, 675b to enable the dispatcher to indicate to the user interface to navigate back or forward, respectively, in the emergency dispatch protocol. The dispatcher can select the forward navigation button 675b to indicate to the user interface <NUM> that the dispatcher is ready to proceed in the protocol. The dispatcher can select the back navigation button 675a to go back in the protocol. Accordingly, when the dispatcher selects the forward navigation button 675b, the protocol advances and the user interface <NUM> may present a next instruction and/or preprogrammed inquiry.

The user interface <NUM> may also present one or more diagnostic tool launch inputs 620a-c. As will be appreciated by a person of ordinary skill, other diagnostic tools may be included and/or the diagnostic tool launch inputs 620a-c may comprise a component other than a button, including familiar user interface components such as a drop down menu, a drop down selection box, a list, a check box, and a radio button. The diagnostic tool launch inputs 620a-c may enable the dispatcher to launch a particular diagnostic tool. Although the emergency police dispatch protocol may automatically initiate a diagnostic tool based on dispatcher-entered input indicative of one or more responses of the caller, the diagnostic tool launch inputs 620a-c provide a way for the dispatcher to manually (i.e., anytime, at the dispatcher's discretion) initiate a diagnostic tool. The diagnostic tool launch inputs 620a-c may include a vehicle description launch input 620a to receive descriptions of one or more vehicles, a boat (vessel) description launch input 620b to receive descriptions of one or more boats, and a person description launch input 620c to receive descriptions of one or more people. The illustrated diagnostic tool launch inputs 620a-c comprises buttons on the emergency police dispatch system user interface <NUM>. The buttons may include, for example, icons or symbols, such as a car, a boat, or a person, as shown, so that the functions of the buttons are easily identifiable.

The user interface <NUM> may also present an answers pane <NUM> to display input received in relation to previous instructions and/or preprogrammed inquiries. For example, the answers pane <NUM> of <FIG> displays the dispatcher-entered input provided for multiple previously presented preprogrammed inquiries and/or instructions presented by the active assailant protocol <NUM>; e.g., "<NUM>. The caller is on scene. The caller is a second party caller. The suspect's description is:. " The answers pane <NUM> enables a dispatcher to quickly review previous responses for accuracy and to thereby improve understanding of the situation and/or incident reported by the caller. If the dispatcher were to inadvertently select an incorrect input in the input field <NUM>, the dispatcher can readily recognize the error in the answers pane <NUM> and navigate back in the protocol by selecting the back navigation button 675a and then select a correct input. A description pane <NUM> may include descriptions of vehicles and/or people provided to one or more diagnostic tools. The dispatcher may be able to quickly review the descriptions for accuracy and/or to determine what descriptive information has already been provided by the caller. A dispatcher may use the diagnostic tool launch inputs 620a-c to easily launch the diagnostic tools and add, remove, and/or modify descriptions.

A plurality of tabs <NUM> may allow the dispatcher to switch between a "Question Answers" pane 670a and other panes. Other panes may provide additional information relating to processing a given emergency call, including an "Additional Information" pane 670b, which may provide axioms and rules for active assailant events and description essentials for answering questions, a "Determinant/Suffixes" pane 670c, which may include information about determinants and suffixes, and a "Determinant Codes" pane 670d, which may include information about determinant codes. The current determinant value <NUM> may be displayed to allow the dispatcher to determine the determinant value quickly, which may aid in determining if the determinant value should be changed.

<FIG> illustrates the user interface <NUM> presenting evacuation instructions. The evacuation instructions may be presented on an evacuation instructions pane 630a of a dispatching life support or "DLS" tab 310d. The evacuation instructions may be intended to help the caller evacuate the area as safely and as efficiently as possible. They may be designed to prevent potentially panicked callers from making the situation worse for themselves and/or responders. The evacuation instruction may include common sense advice that might not be apparent to a panicked caller without a clear reminder from a dispatcher, such as "Take an evacuation path that's away from the suspect. " Callers may also desire to remove as many victims from the location as possible including wounded people, but removing wounded people can slow the evacuation, put the caller and/or others at risk, an/or cause additional injury to the wounded people. Accordingly, the instructions may include, "Do not attempt to move wounded people. " Panicked callers may swarm responders and/or may appear to be a threat if they rush police officers. Swarming can endanger the callers and/or police officers by putting them in the line of fire and may hinder the ability of responders to appropriately assess and address possible threats. To prevent these problems, the instructions may include, "Do not rush towards officers, keep your hands visible at all times, and follow all of their commands. " The evacuation instructions may include a preprogrammed inquiry <NUM>, "Can you take the phone with you?" Buttons 605a, 605b containing possible responses may be selected by the dispatcher. If the caller can take the phone, the protocol may return to the "KQ" tab 310b. Otherwise, disconnect instructions may be provided and/or the case may be closed.

<FIG> illustrates the user interface <NUM> presenting lockdown instructions. The lockdown instructions may be provided on a lockdown instructions pane 630b. Lockdown may be the next best option for callers unable to evacuate to remove themselves from plain sight and secure themselves in an area that is more difficult for an assailant to target. A room with a locking door and/or a door that can be barricaded may remove potential victims from plain sight and keep the assailant(s) in the hallways and common areas where they can be easily located by responders. Accordingly, the lockdown instructions may include, "Gather those around you and go to the nearest room with a locking door. " To minimize the danger of being hit by bullets fired through the door, the lockdown instructions may also include, "Sit or lie on the floor next to the wall with the door. " It may also be important to prepare callers for the fact that they may need to fight for their life. A lockdown instruction, such as "If you are found and unable to get away, be aggressive and prepare to fight for your life by using any items you can as weapons," may suggest actions that callers can take if they are found and/or help put callers in an action mindset rather than a victim mindset. The lockdown instructions may include a button 607a to return to the "KQ" tab 310b and a button 607b to close the case, which may be used if the caller cannot take the phone and/or if heavy call volume requires the dispatcher to answer another call.

<FIG> illustrates the user interface <NUM> presenting the answer pane <NUM> once all questions have been answered. As before, the answer pane <NUM> may display previously entered input including, "<NUM>. The caller cannot evacuate the building/area. " Accordingly, the dispatcher selected the input "No" or "Unknown" in input field <NUM> (<FIG>) in response to preprogrammed inquiry <NUM> (<FIG>). The dispatcher can select the navigation button 675b to indicate to the user interface <NUM> that the dispatcher is ready to proceed. The dispatcher can select navigation button 675a to go back in the protocol and/or modify answers to previous questions. The user interface <NUM> may also present the description pane <NUM> with any and/or all descriptions provided by the caller. The dispatcher may be able to update the descriptions or add new descriptions by selecting one of the diagnostic tool launch inputs 620a-c.

Claim 1:
A computer-implemented method to guide a dispatcher (<NUM>) when communicating vocally with a caller (<NUM>) via a communication device (<NUM>) regarding an incident involving an active assailant and for dispatching an emergency dispatch response to the incident, the computer-implemented method comprising:
initiating an emergency police dispatch protocol and a new case to record information received from the caller;
presenting (<NUM>), on a dispatch center computer device (<NUM>, <NUM>), a pre-scripted interrogation comprising a plurality of preprogrammed inquiries for the dispatcher to ask the caller;
automatically, without dispatcher action, shunting from the emergency police dispatch protocol to an active assailant protocol immediately upon receiving indication of an active assailant in order to systematically obtain a description of the incident involving the active assailant, wherein the description of the incident comprises caller responses to the plurality of preprogrammed inquiries, and wherein the preprogrammed inquiries of the pre-scripted interrogation include:
asking what happened,
asking what type of weapons are involved (<NUM>),
asking if the caller is on scene (<NUM>) with the active assailant, and
asking whether the caller can safely evacuate/leave the building/area (<NUM>);
receiving (<NUM>), on the dispatch center computer device, dispatcher-entered input representative of caller responses to the preprogrammed inquiries of the pre-scripted interrogation;
determining (<NUM>) automatically on the dispatch center computer device a determinant value from one of a plurality of pre-established determinant values based on dispatcher-entered input representative of caller responses to one or more of the preprogrammed inquires including the caller response as to the type of weapon;
generating pre-arrival instructions for the caller based on the caller response as to safe evacuation; and
automatically ending the new case when a caller response indicates that the caller is not on scene with the active assailant.