Patent Grant
9877171
©2016 Priority Dispatch Corp. A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever. 37 C.F.R. § 1.71(d).
The present disclosure relates to computer systems and methods for providing emergency protocol interrogation, instruction, and dispatch. More specifically, the disclosure is directed to systems and methods for sending picture and/or video messages to and/or receiving picture and/or video messages from a person needing assistance while guiding a dispatcher during interrogation and instruction of the person needing assistance.
Non-limiting and non-exhaustive embodiments of the disclosure are described, including various embodiments of the disclosure with reference to the figures, in which:
Emergency dispatchers may serve a critical role as the first and/or only persons to interface with a person needing assistance (e.g., a person contacting or calling an emergency dispatch center). In their role of receiving emergency communication, emergency dispatchers are in a unique position and may potentially contribute to more positive outcomes by providing a person needing assistance with critical lifesaving instructions and by conducting a precise interrogation to gather specific information that will assist police officers in determining the appropriate response. Unfortunately, emergency dispatchers are often 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 communications (e.g., emergency calls, emergency messages, etc.) that are received and in processing the communications 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 communication to the next.
In some situations, a graphical multimedia message may be the only, safest, and/or most convenient way to communicate effectively with a person needing assistance. Oftentimes, a person needing assistance will make a call to an emergency response dispatcher on a mobile device, i.e., a cellular telephone, smartphone, or other similar portable electronic device. For example, a person needing assistance may have been in a car accident, come across someone who has overdosed on drugs, witnessed a person going into cardiac arrest, or been stung by a bee while on a hike. The person needing assistance may also be ignorant to the incident at hand and not have the knowledge necessary to administer first aid or other types of treatment to himself or herself or any other individual in need. A graphical multimedia message may be able to provide information that cannot be conveyed in a phone call and/or SMS message, such as a picture of a possible remedy with accompanying instructions and/or a video of how to administer a potential treatment. The person needing assistance may also be hearing-impaired and/or may not be able to talk due to a hostile assailant in the area, extreme background noise, a lack of oxygen (e.g., asthma or choking), or the like. Unfortunately, existing emergency dispatch centers may be poorly equipped to receive and/or send graphical multimedia messages. Additionally, even if a dispatch center is able to receive and/or send graphical multimedia messages, the messaging capability may not be integrated with automated emergency dispatch systems.
In many emergency situations, speed is of the essence. Delays of seconds or minutes may lead to a poorer outcome for a person needing assistance. Having to copy and/or transcribe every question and/or response between an automated emergency dispatch system and an SMS/MMS messaging system may result in such delays. An automated emergency dispatch system could save time and/or effect better outcomes by being able to send questions and/or receive responses automatically and/or with little operator effort.
Upon receiving answers to various inquiries, the automated emergency dispatch system may be configured to send graphical multimedia messages itself or may be communicatively coupled with a messaging system that can be instructed by the automated emergency dispatch system to send messages. To save time, the automated emergency dispatch system may transmit a graphical multimedia message in response to no more than zero, one, two, three, or four actions by the dispatcher. For example, once the dispatcher has ascertained what sort of help the person needing assistance requires, the dispatcher may be able to select a graphical multimedia message to transmit to the person needing assistance. Alternatively, or in addition, the actions may be single key strokes. The graphical multimedia message may be received on a portable electronic device, and in the case of video messages, may be playable on the portable electronic device for on-scene instruction to the person needing assistance.
The automated emergency dispatch system may log all graphical multimedia messages as well as SMS text messages sent and received by the system. For example, the automated emergency dispatch system may store a time stamp for each message and/or the contents (e.g., text, photo, video, etc.) of each message to a persistent storage device. The automated emergency dispatch system may ensure that messages are properly routed to and from people needing assistance. In some embodiments, the automated emergency dispatch system may be coupled to a computer network. The automated emergency dispatch system may then translate a telephone number for the person needing assistance to a computer network address and/or may determine the computer network address from a message (e.g., from the header of a message) received from the person needing assistance. The automated emergency dispatch system may automatically register its own computer network address with one or more telephone service providers so graphical multimedia messages to people needing assistance are sent from the appropriate emergency dispatch center to the appropriate portable electronic device.
Following inquiries to and upon receiving answers from the person needing assistance, the automated emergency dispatch system may also be configured to provide an image and/or video depicting a potential treatment for a particular incident. This may be done via a graphical multimedia message. The dispatcher may be prompted by the automated emergency dispatch system to transmit the image and/or video in a graphical multimedia message format such as MMS, simple mail transfer protocol (SMTP) or other format to the person needing assistance. Alternatively or in addition, the automated emergency dispatch system may automatically send the image and/or video in a graphical multimedia message format such as MMS or other format. The graphical multimedia message may then be received by the person needing assistance on his or her portable electronic device so as to provide instructions and/or information on potential treatments to a particular incident. Such instructions may include but are not limited to: a picture of a specific medication needed for treating drug overdose, an image of a bee sting remedy and how to apply it, or a picture and accompanying labels of an external defibrillator with usage instructions. The instructions may alternatively be in playable video format for the person needing assistance to, for example: view an instructional video on how to treat a bee sting, observe how a particular medication is prepared and administered, or receive instruction on how to operate an external defibrillator. Graphical instructions of this kind are beneficial in helping the person needing assistance understand what do to in a certain situation through clear, concise direction in times of distress when verbal communication may be less effective. Additionally, graphical multimedia messages may aid in preventing further harm to any injured persons involved in a particular incident as a result of misguided efforts by the person needing assistance had the he or she not received and/or understood any instructions in a timely 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/2, 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.
The responses of the person needing assistance 118 are processed according to predetermined logic of the logic tree of the emergency dispatch protocol 108. The predetermined logic may enable the emergency dispatch system 100 to provide to the dispatcher 104 information concerning the correct emergency dispatch response (e.g., by trained law enforcement officers or agencies and/or other emergency responders). The predetermined logic may also enable the emergency dispatch system 100 to provide to the dispatcher 104 appropriate post-dispatch instructions for relay to the person needing assistance 118 before professional help arrives at the scene. The predetermined logic may also enable the emergency dispatch system 100 to aid the dispatcher 104 in determining an appropriate priority of the emergency communication, including but not limited to a priority of the emergency communication relative to other emergency communications and a level of emergency response to provide for the reported incident or situation.
Although an emergency dispatch system 100 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 U.S. Pat. Nos. 5,857,966; 5,989,187; 6,004,266; 6,010,451; 6,053,864; 6,076,065; 6,078,894; 6,106,459; 6,607,481; 7,106,835; 7,428,301; 7,436,937; 7,645,234; 8,066,638; 8,103,523; 8,294,570; 8,335,298; and 8,355,483, which are hereby incorporated herein by reference.
The computer 106 operates a determinant value calculator 110 to calculate a determinant value from the responses of the person needing assistance 118 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-1 for generally very serious emergencies to Ω-2 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, Ω-2 is the least serious while E-1 is the most serious communication. Depending on the determinant level, the appropriate emergency response is dispatched as indicated by the response protocol. For example, an Alpha A communication will typically be responded to by a next available law enforcement unit using the safest arrival method reasonably possible. A Delta D communication will typically be responded to by any or all available law enforcement units proceeding under the most urgent method possible. Echo E communications typically involve likely immediate life-threatening situations and will be responded to in the most urgent manner available. Bravo B and Charlie C communications are intermediate emergencies that are typically responded to in business-like, orderly manner according to specific department protocol. An Omega Ω communication 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 communication with a determinant value of D-1 is generally more critical and requires a more urgent response than a communication with a determinant value of D-2. However, in some instances, the numeric determinant levels within a determinant value may serve only to identify the type, rather than criticality, of the communication. Also, if more than one determinant value can be assigned to a particular communication, the more critical or higher determinant value is assigned. That is, the communication is assigned a criticality determinant value based on the fact or aspect that would lead to the most urgent response. For example, if the communication concerns a burglary that occurred over 30 minutes before, but where the suspect remains on the scene or nearby and the person needing assistance 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-1 (due to the imminent danger) rather than D-2 (suspect on scene or nearby) or B-1 (incident occurred over 30 minutes before).
Many communications for law enforcement are not true emergencies, so it is important to prioritize the communications in several ways. First, communications 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.W.A.T. 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 106 presents the determinant value to generate an appropriate emergency dispatch response and/or establish the priority of the emergency communication. 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 112, which is a tool that the dispatcher 104 may use to track and allocate emergency response resources for processing emergency communications. The CAD system 112 may manage dispatcher tools for processing emergency communications, including but not limited to the emergency dispatch protocol 108, responder 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 112 may operate in whole or in part on a separate computer in communication with the computer 106. In another embodiment, the CAD system 112 operates on the computer 106. The primary information used by the CAD system 112 is location information of the incident and units, unit availability, and the type of incident. The CAD system 112 may use third party solutions, such as E-911, vehicle location transponders, and mobile data terminals (MDTs) for automating the location and availability tasks. The CAD system 112 may also use the emergency dispatch protocol 108 to facilitate structured communication for incident interrogation, as previously described.
Although many emergency communications 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 dispatch protocol 108 may provide the dispatcher 104 with instructions for the person needing assistance 118 that are appropriate to the type of communication, whether the communication 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 106 may include a reporting component 114 to statistically measure the performance of individual staff and overall performance of the dispatch center 102. To record information received during a communication, the dispatcher 104 may be required to open a new case. Once the communication is complete, the dispatcher 104 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 114 may determine statistics from the case summaries and/or do so while the cases are open. The statistics may include compliance rates, call/communication processing statistics, and peer measurements.
The computer 106 may further comprise an input device 128, such as a keyboard, mouse, touch screen, laser pointer, or other input device, and also an output device 130, such as a display monitor. The input device 128 receives input from a user (generally a dispatcher) and provides the input to the emergency dispatch system 100. The input may be provided to the computer 106, the emergency dispatch protocol 108, diagnostic tools 120, and/or the CAD system 112. The output device 130 receives output from the emergency dispatch system 100 and displays or otherwise provides the output to the user. In another embodiment, the input device 128 and output device 130 are provided by the CAD system 112.
The dispatch center 102 includes a communication device 116 (e.g., telephone equipment) to answer emergency communications. The communication device 116 may be configured to send and/or receive communications using one or more different methods and may include a telephone coupled to a public switch telephone network (PSTN) (e.g., a landline telephone); a telephone coupled to a computer network (e.g., a VoIP telephone); a telephone configured to communicate via radio waves (e.g., a mobile phone); a system, which may or may not include a telephone, configured to send and/or receive SMS and/or graphical multimedia messages such as MMS messages via a PSTN, a computer network, and/or radio waves; and/or the like. The communication device 116 may include multiple communication systems, such as a landline telephone and a system configured to send and receive graphical multimedia messages and SMS messages via a network. As can be appreciated, the particular methods of communication used may change as technology evolves. Some and/or all of the communication device may be implemented on the computer 106 (e.g., when communicating via a computer network). Alternatively, the communication device 116 may be coupled to the computer 106.
The communication device 116 may be configured to determine a computer network address (e.g., an internet protocol address, email address, etc.) corresponding to a telephone number of the person needing assistance 118. For example, the communication device 116 may determine a telephone service provider based on the telephone number and may construct the computer network address based on the phone service provider and the telephone number. Alternatively, or in addition, the communication device 116 may determine the computer network address based on a source address specified in a communication from the person needing assistance 118. The communication device 116 may register a computer network address of the communication device 116 so graphical multimedia and/or SMS text messages are properly routed by the telephone service providers. For example, the communication device 116 may inform the telephone service providers and/or a third party of one or more telephone numbers, telephone number ranges, telephone exchanges, and/or geographic areas that are serviced by the dispatch center 102 and the computer network address that should be used to contact the dispatch center 102.
A message interface component 122 may be a component of an automated emergency dispatch system. The message interface component 122 may enable the emergency dispatch protocol 108, determinant value calculator 110, reporting component 114, diagnostic tools 120, and/or dispatch protocols 124 to interact with the communication device 116. In some embodiments, the message interface component 122 may also be or instead be a component of the communication device 116 and/or may itself be able to send communications to and/or receive communications from the person needing assistance 118. The message interface component 122 may also be able to send graphical multimedia messages that include images and/or playable videos containing information relating to the emergency to further help the person needing assistance 118. For example, the person needing assistance 118 may be able to receive a playable video on his or her portable electronic device that contains instructions on how to operate an external defibrillator. The message interface component 122 may send the graphical multimedia messages automatically or in response to input by the dispatcher 104.
A communication received at the dispatch center 102 from the person needing assistance 118 may initiate creation of an emergency communication incident. The dispatcher 104 identifies the communication as requiring an emergency dispatch, and the emergency dispatch protocol 108 is accessed. The emergency dispatch protocol 108, including the dispatch protocols 124, may provide questions and/or instructions that are expertly drafted to assist the novice person needing assistance 118 in reporting aspects of the incident, and/or assessing a situation of the victim 117. The emergency dispatch protocol 108 may also provide expertly drafted instructions to assist the victim 117 prior to the arrival of trained law enforcement and/or emergency responders. The instructions may be vocally relayed and/or sent as one or more graphical multimedia messages by the dispatcher 104 to the person needing assistance 118 over the communication device 116.
Some protocol inquiries or questions may be readily answerable by the person needing assistance 118, whereas others may be more difficult to answer. Certain diagnostic inquiries may be difficult for the untrained person needing assistance to determine or may be difficult to answer under the stress of an emergency situation. Accordingly, in addition to instructions, the emergency dispatch system 100 may provide one or more computer-implemented diagnostic tools 120. The diagnostic tools 120 may greatly improve information collection and intervention for emergency response situations and aid in saving lives.
A diagnostic tool 120 may aid the dispatcher 104 and/or the person needing assistance 118 (via instructions from the dispatcher 104) in assessing a situation of the victim 117. A diagnostic tool 120 may also be an interventional tool, providing instructions that direct the person needing assistance 118 to intervene, or take action, to aid the victim 117, 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 120, as referred to herein, may provide diagnostic instructions, interventional instructions, or both diagnostic and interventional instructions. Whether a diagnostic tool 120 provides merely diagnostic instructions, merely interventional instructions, or both diagnostic and interventional instructions, the diagnostic tool 120 provides consistent and reliable instruction, information gathering, and/or timing for a particular emergency situation.
The diagnostic tools 120 are computer-implemented software modules that enable the dispatcher 104 to provide consistent, expert advice to assist the person needing assistance 118 with regard to a particular aspect of an emergency situation, such as determining a vital sign. One benefit of the diagnostic tools 120 is the computer-aided timing of techniques to determine the vital signs. In highly stressful conditions, the diagnostic tools 120 provide a necessary resource to reading critical signs. The diagnostic tools 120 may be stored in the memory of the computer 106 and initiated and executed as required. The diagnostic tools 120 may be embodied as computer-executable software applications and associated data.
The emergency dispatch protocol 108, including the dispatch protocols 124, also may call on one or more diagnostic tools 120 to assist with an inquiry and may route to the appropriate diagnostic tool 120 when needed. When directed according to the protocol, the emergency dispatch protocol 108 may automatically, i.e., without dispatcher intervention, initiate the appropriate diagnostic tool 120. This may occur when the emergency dispatch protocol 108 arrives at a diagnosis or assessment step in the logic tree. The emergency dispatch system 100 may also allow the dispatcher 104 the option to call upon a diagnostic tool 120 as desired. Icons may be displayed in a tool bar or other convenient location on a user interface to allow the dispatcher 104 to initiate the corresponding diagnostic tool 120.
If the dispatcher receives and enters information that an incident is especially critical (e.g., an active assailant, a person needing assistance in imminent danger, a sinking vehicle, a vehicle in rising flood water, or a vehicle with a stuck accelerator that cannot stop), for whatever reason, an emergency response is dispatched 204 immediately, before continuing with any further interrogation or instructions. The dispatched 204 emergency response may be a maximum emergency response, including properly trained law enforcement officers. The criticality of the incident is verified 206 and pre-arrival instructions are given 208. 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 person needing assistance) 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 person needing assistance. The pre-arrival instructions may aid to ensure safety and improve the effectiveness of the dispatched 204 emergency response.
If the dispatcher receives information from the person needing assistance 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 124, the emergency dispatch protocol 108 may shunt to additional inquiries 210 designed to guide the dispatcher to gather information from the person needing assistance to enable the dispatcher to ascertain the chief complaint. If the chief complaint is determined, the emergency dispatch protocol 108 may shunt to the appropriate dispatch protocol 124 for dealing with that chief complaint.
The dispatch protocol 124 may guide the dispatcher through a secondary interrogation focusing on the chief complaint. The dispatch protocol 124 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 124 may be termed “Key Questions” for the particular situation or condition of the chief complaint. The preprogrammed inquiries presented may depend on responses from the person needing assistance. Verifying 206 the criticality of the incident and giving 208 pre-arrival instructions may include traversing the logic tree of the dispatch protocol 124. Dispatch protocols 124, in general, are discussed in greater detail below with reference to
During the dispatch protocol 124, the dispatcher 104 and/or the emergency dispatch protocol 108 will gather information about the circumstances of the incident or emergency situation, discovered through interrogation, and may dispatch 214 an appropriate emergency dispatch response. The dispatch protocol 124 facilitates uniform and consistent gathering of information relating to the emergency and dispatching 214 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-1 for generally very serious emergencies to Ω-2 for generally less serious emergencies. In another embodiment, the determinant values may range from, for example, E-1 for generally very serious emergencies to A-2 for generally less serious emergencies. In still another embodiment, the determinant values may range differently, such as for example from A-1 for generally very serious emergencies to E-5 for generally less serious emergencies.
After the appropriate emergency dispatch response has been dispatched 214 (e.g., law enforcement officers), the dispatcher may remain in communication with the person needing assistance to provide 216 post-dispatch instructions regarding what to do, and what not to do, prior to the arrival of law enforcement officers. The post-dispatch instructions help to stabilize the situation and 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. Post-dispatch instructions may also or alternatively include a graphical multimedia message transmitted to a portable electronic device belonging to the person needing assistance, viewable by the person needing assistance to provide him or her with additional, more detailed instructions for specific tasks, remedies, treatments, equipment operation, etc.
The dispatcher may input the responses of the person needing assistance to the inquiries 302 into response fields 304 provided by the user interface 300. The response fields 304 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 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 304 may correspond to information indicative of one or more responses to the inquiries 302 from the person needing assistance. In some embodiments, the inquiries 302 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 304.
The responses from the person needing assistance are relayed from the person needing assistance to the dispatcher, for example, over the telephone or via an SMS/MMS message. Information from the responses of the person needing assistance may be input into the system by the dispatcher and may be used by the emergency dispatch protocol to determine subsequent inquiries 302 and instructions to present to the dispatcher. The response information may indicate the person needing assistance's observations of the incident and/or current situation. The emergency dispatch system may use the response information to generate an emergency dispatch response by properly trained law enforcement officers. The information gathered from the responses of the person needing assistance 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 dispatch protocols and user interfaces to interact with the same can be found in the earlier referenced U.S. patents.
The inquiries 302 of the user interface 300 may include a chief complaint inquiry and corresponding responses 306. For example, the chief complaint of the person needing assistance may be drug overdose/poisoning (ingestion). In other embodiments, the chief complaint may be a bee sting, cardiac arrest, stroke, heart attack, gunshot wound, etc., either of the person needing assistance or of some other victim. The responses 306 to the chief complaint inquiry may include relevant preprogrammed responses to be selected by the dispatcher according to the responses given by the person needing assistance. Upon inputting a response 306 to a chief complaint, the user interface 300 may advance to a further screen depicted in
The user interface 300 may further comprise tabs 310 to aid in organizing and/or compartmentalizing various aspects of processing a communication. The tabs 310 may include a tab 310a for presenting a case entry protocol portion of an emergency dispatch protocol (e.g., “Entry” tab). Other tabs may include a tab for presenting a dispatch protocol portion of the emergency 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 communication and/or processing of the communication (e.g., “Summary” tab). The KQ tab is discussed below with reference to
For example, as shown in
The user interface 300 as depicted in
The user interface 300 presents one or more tabs 310, including the 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 and the path along a logic tree of the emergency dispatch protocol 108 (
The user interface 300 may present navigation buttons 472a, 472b to enable the dispatcher to indicate to the user interface 300 to navigate back or forward, respectively, in the emergency dispatch protocol. The dispatcher can select the forward navigation button 472b to indicate to the user interface 300 that the dispatcher is ready to proceed in the protocol. The dispatcher can select the back navigation button 472a to go back in the protocol. Accordingly, when the dispatcher selects the forward navigation button 472b, the protocol advances and the user interface 300 may present a next instruction and/or a preprogrammed inquiry.
The list of determinants 576 may be used by the dispatcher to determine a determinant value (e.g., O-1, C-3, etc.) to assign to a given situation, as discussed in
Post-dispatch instructions 602 as displayed in
Additional information (not shown) may be displayed upon selection of tab 610b by the dispatcher. Such additional information may provide the dispatcher with background knowledge and/or context related to the circumstances reported by the person needing assistance. For example, in the case of a drug overdose, the additional information under tab 610b may display definitions of relevant terminology and/or vernacular used in the appropriate determinant value in the case. Such definitions may include, “OVERDOSE: Intentional intake of potentially harmful substance” or “POISONING (Ingestion): Accidental intake of a potentially harmful substance.” The additional information may additionally or alternatively include background information to the dispatcher, relevant for further diagnosis of the situation, such as “CHANGING COLOR: Changing colors of clinical significance include: Ashen, Blue, Cyanotic, Gray, Mottled, Purple.” This additional information may be used by the dispatcher to ascertain other helpful details relating to a given situation in a post-dispatch setting where the gathering of helpful information may still be important, but not be as time-sensitive as it is before dispatching emergency responders.
Also depicted in
Within DLS tab 310d, instruction prompt 802 may describe what the graphical multimedia message 804 shown in the user interface 300 is provided to do, while a descriptor 806 is also displayed which may describe the specific type, brand, or function of the treatment and/or medication shown. The graphical multimedia message 804 may be transmittable via MMS, SMTP, or any other viable protocol via cellular telephone networks, data networks (e.g., 4G, 4G LTE, 3G, Edge, etc.), Bluetooth, Wi-Fi, or any other wired and/or wireless communications network suitable for transmitting data from the emergency dispatch system to a portable electronic device. Transmitting the graphical multimedia message 804 to the person needing assistance provides an added measure of clarity and effectiveness to the directions given by the dispatcher. A picture is worth a thousand words, after all. Some situations may result in the person needing assistance losing focus easily, not hearing the dispatcher clearly over the phone, or being too panicked to fully understand the direction he or she is given by the dispatcher. Sending a graphical multimedia message 804 to the person needing assistance so he or she can view it on his or her smartphone or other portable electronic device may help minimize the issues of standard verbal communication, thereby enabling the person needing assistance to comprehend the given instructions more easily through visual representation. The dispatcher may communicate more effectively with the person needing assistance and so provide the necessary help in an efficient manner by simply providing him or her with a picture and/or video that explains what to do in a certain situation. This may be done alone or in conjunction with additional verbal instructions over the phone or in addition to written instructions given via text message (in SMS/MMS format, email format, instant message format, or other suitable messaging format). And this may be done before, after, and/or during dispatch of emergency responders.
In some embodiments, the graphical multimedia message 804 may depict a type of medication with various labels and prompts to aid the person needing assistance in understanding how to recognize and administer the medication. For example, as shown in
In alternative embodiments, the graphical multimedia message 804 may relate to chief complaints other than a drug overdose. For example, if the chief complaint of the person needing assistance is a bee sting, graphical multimedia message 804 may be transmitted by the dispatcher via the emergency dispatch system to display a bee sting medication or an emergency allergy medication (e.g., EpiPen auto-injector) in case the victim is allergic. In still other embodiments, the graphical multimedia message 804 may relate to treating a victim of cardiac arrest. In such cases, an external defibrillator is often required to stop arrhythmia and allow the heart to reestablish an effective rhythm. Accordingly, the graphical multimedia message 804 may display an external defibrillator and may provide additional instruction on its application and use. In some embodiments, the graphical multimedia message 804 may help the person needing assistance prevent further harm to the victim, himself or herself, or others until the emergency responders arrive on scene. In other embodiments, the graphical multimedia message 804 may provide the person needing assistance with the information necessary to resolve the situation on his or her own. In still other embodiments, the graphical multimedia message 804 may provide little more than a distraction to occupy the person needing assistance until professional help arrives. Additional or alternative embodiments are described further in
Additionally, the graphical multimedia message 804 may be received by the person needing assistance on his or her portable electronic device in a viewable format (e.g., .jpg, .png, .gif, .tiff, .bmp, etc.), and receipt of the graphical multimedia message 804 may be confirmed to the emergency dispatch system. In some embodiments, the emergency dispatch system may require a confirmation of receipt of the graphical multimedia message 804 by the person needing assistance. Should the person needing assistance be unable to view the graphical multimedia message 804, the message may be resent in a different format and/or resolution (e.g., 320×240 pixels, 1920×1080 pixels, etc.) until the message is viewable and confirmation of receipt is obtained. The confirmation of receipt may be sent automatically or may be sent manually by the person needing assistance to the dispatcher through verbal communication (i.e., the person needing assistance tells the dispatcher that the message was received and viewable/playable), SMS/MMS message, or other means. Sometimes, the portable electronic device of the person needing assistance may not be compatible with one or more of the possible message formats available for transmitting and receiving the graphical multimedia message 804. In such situations, no confirmation of receipt may be sent to and/or received by the emergency dispatch system. The emergency dispatch system may have an internal timer that may prompt the dispatcher to resend the graphical multimedia message 804 in an alternate format should no confirmation be received in a given time frame. In other embodiments, the graphical multimedia message 804 may be resent automatically by the emergency dispatch system when the timer expires. In still other embodiments, the dispatcher may ask the person needing assistance if the graphical multimedia message 804 was received and viewable/playable on the portable electronic device of the person needing assistance. Upon receiving confirmation from the person needing assistance, the dispatcher may manually confirm receipt of the graphical multimedia 804 message by the person needing assistance.
A video such as a bee sting treatment video may provide instruction in even greater detail than an image or a series of images and may help the person needing assistance most effectively. If a picture is worth a thousand words, then a video is worth even more. For example, if a victim is allergic to bee stings, the person needing assistance may not be familiar with severe allergic reactions and how to properly address the situation to help the victim. Likewise, the dispatcher may be similarly ignorant and otherwise unable to provide assistance over the phone. Through the pre-scripted interrogation provided by the emergency dispatch system, the dispatcher may be able to provide the appropriate guidance by sending a video to the person needing assistance which depicts proper application of, for example, an EpiPen auto-injector. In other embodiments, video instructions of drug overdose medication, external defibrillators, and various other medications and treatments are contemplated.
The transmittable video may be recorded and preprogrammed into the emergency dispatch system and may be transmitted to the person needing assistance either manually or automatically. In other embodiments, the video may be a live feed from a camera of the dispatcher or a camera of emergency response personnel who can provide assistance to the person needing assistance. In the same or alternate embodiments, the video may be in any playable format suitable for a portable electronic device, such as: .m4a, .mp4, .mpg, .wmv, .m4v, etc. In some embodiments, the video may be sent at a lower resolution (e.g., 320×240 pixels) for faster transmission while in other embodiments the video may be sent at a higher resolution (e.g., 1920×1080 pixels) for clarity and precision of instruction.
The dispatch protocol 124 may present 1104 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. The preprogrammed inquiries may be considered a part of a pre-scripted interrogation that is based on a logic tree of the dispatch protocol 124. The preprogrammed inquiries that are presented as part of a pre-scripted interrogation may depend on dispatcher-entered input. 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.
Data is received 1106 from the dispatcher, as relayed from the person needing assistance, following the preprogrammed inquiries asked to the person needing assistance by the dispatcher. The data received 1106 may correspond to responses from the person needing assistance to the preprogrammed inquiries. The data may be used to determine subsequent questions, or to determine instructions to provide to the dispatcher. The data may be received substantially in real-time, as the dispatcher inputs the data. Alternatively, or in addition, the input may be received from the emergency dispatch system 100 because information sought by the dispatch protocol 124 may have previously been obtained from the dispatcher via the case entry protocol and/or another portion of the dispatch protocol 124. Alternatively, or in addition, the input may be received from a diagnostic tool 120. The dispatcher-entered input relates to the emergency communication and/or the reported incident. The dispatcher-entered input may affect the path along which the logic tree is traversed.
The received 1106 data is also used by the protocol to determine 1108 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 124 may provide 1110 appropriate instructions to be relayed to the person needing assistance by the dispatcher. The instructions may comprise post-dispatch instructions for the person needing assistance to help stabilize or otherwise ameliorate a situation and to expedite the work of law enforcement officers at the scene. A database may be accessed to produce appropriate instructions. Records of the communications may be stored 1112 for historical reports, for review and analysis of dispatcher performance, and for continued quality assurance control. A record of a communication may include, but is not limited to, inquiries, responses, and determinant values.
As can be appreciated, some or all of the information gathered by the pre-scripted interrogation 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 dispatch system may be deployed.
While specific embodiments and applications of the disclosure have been illustrated and described, it is to be understood that the disclosure is not limited to the precise configuration and components disclosed herein. Various modifications, changes, and variations apparent to those of skill in the art may be made in the arrangement, operation, and details of the methods and systems of the disclosure without departing from the spirit and scope of the disclosure.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3799147 | Adolph et al. | Mar 1974 | A |
| 4130881 | Haessler et al. | Dec 1978 | A |
| 4164320 | Irazoqui et al. | Aug 1979 | A |
| 4237344 | Moore | Dec 1980 | A |
| 4290114 | Sinay | Sep 1981 | A |
| 4338493 | Stenhuis et al. | Jul 1982 | A |
| 4360345 | Hon | Nov 1982 | A |
| 4455548 | Burnett | Jun 1984 | A |
| 4489387 | Lamb et al. | Dec 1984 | A |
| 4731725 | Suto et al. | Mar 1988 | A |
| 4839822 | Dormond et al. | Jun 1989 | A |
| 4858121 | Barber et al. | Aug 1989 | A |
| 4865549 | Sonsteby | Sep 1989 | A |
| 4922514 | Bergeron et al. | May 1990 | A |
| 4926495 | Comroe et al. | May 1990 | A |
| 4945476 | Bodick et al. | Jul 1990 | A |
| 4967754 | Rossi | Nov 1990 | A |
| 5063522 | Winters | Nov 1991 | A |
| 5065315 | Garcia | Nov 1991 | A |
| 5072383 | Brimm et al. | Dec 1991 | A |
| 5077666 | Brimm et al. | Dec 1991 | A |
| 5086391 | Chambers | Feb 1992 | A |
| 5109399 | Thompson | Apr 1992 | A |
| 5122959 | Nathanson et al. | Jun 1992 | A |
| 5193855 | Shamos | Mar 1993 | A |
| 5228449 | Christ et al. | Jul 1993 | A |
| 5253164 | Holloway et al. | Oct 1993 | A |
| 5255187 | Sorensen | Oct 1993 | A |
| 5291399 | Chaco | Mar 1994 | A |
| 5323444 | Ertz et al. | Jun 1994 | A |
| 5339351 | Hoskinson et al. | Aug 1994 | A |
| 5348008 | Bornn et al. | Sep 1994 | A |
| 5379337 | Castillo et al. | Jan 1995 | A |
| 5404292 | Hendrickson | Apr 1995 | A |
| 5410471 | Alyfuku et al. | Apr 1995 | A |
| 5423061 | Fumarolo et al. | Jun 1995 | A |
| 5438996 | Kemper et al. | Aug 1995 | A |
| 5441047 | David et al. | Aug 1995 | A |
| 5462051 | Oka et al. | Oct 1995 | A |
| 5471382 | Tallman et al. | Nov 1995 | A |
| 5502726 | Fischer | Mar 1996 | A |
| 5513993 | Lindley et al. | May 1996 | A |
| 5516702 | Senyei et al. | May 1996 | A |
| 5521812 | Feder et al. | May 1996 | A |
| 5536084 | Curtis et al. | Jul 1996 | A |
| 5544649 | David et al. | Aug 1996 | A |
| 5554031 | Moir et al. | Sep 1996 | A |
| 5590269 | Kruse et al. | Dec 1996 | A |
| 5593426 | Morgan | Jan 1997 | A |
| 5594638 | Iliff | Jan 1997 | A |
| 5594786 | Chaco et al. | Jan 1997 | A |
| 5596994 | Bro | Jan 1997 | A |
| 5630125 | Zellweger | May 1997 | A |
| 5636873 | Sonsteby | Jun 1997 | A |
| 5650995 | Kent | Jul 1997 | A |
| 5660176 | Iliff | Aug 1997 | A |
| 5675372 | Aguayo, Jr. et al. | Oct 1997 | A |
| 5682419 | Grube et al. | Oct 1997 | A |
| 5684860 | Milani et al. | Nov 1997 | A |
| 5689229 | Chaco et al. | Nov 1997 | A |
| 5719918 | Serbetciouglu et al. | Feb 1998 | A |
| 5722418 | Bro | Mar 1998 | A |
| 5724983 | Selker et al. | Mar 1998 | A |
| 5734706 | Windsor et al. | Mar 1998 | A |
| 5745532 | Campana, Jr. | Apr 1998 | A |
| 5748907 | Crane | May 1998 | A |
| 5754960 | Downs et al. | May 1998 | A |
| 5759044 | Redmond | Jun 1998 | A |
| 5761278 | Pickett et al. | Jun 1998 | A |
| 5761493 | Blakeley et al. | Jun 1998 | A |
| 5764923 | Tallman et al. | Jun 1998 | A |
| 5787429 | Nikolin, Jr. | Jul 1998 | A |
| 5805670 | Pons et al. | Sep 1998 | A |
| 5809493 | Ahamed et al. | Sep 1998 | A |
| 5822544 | Chaco et al. | Oct 1998 | A |
| 5823948 | Ross, Jr. et al. | Oct 1998 | A |
| 5826077 | Blakeley et al. | Oct 1998 | A |
| 5832187 | Pedersen et al. | Nov 1998 | A |
| 5842173 | Strum et al. | Nov 1998 | A |
| 5844817 | Lobley et al. | Dec 1998 | A |
| 5850611 | Krebs | Dec 1998 | A |
| 5857966 | Clawson | Jan 1999 | A |
| 5901214 | Shaffer et al. | May 1999 | A |
| 5902234 | Webb | May 1999 | A |
| 5910987 | Ginter et al. | Jun 1999 | A |
| 5912818 | McGrady et al. | Jun 1999 | A |
| 5915019 | Ginter et al. | Jun 1999 | A |
| 5926526 | Rapaport et al. | Jul 1999 | A |
| 5933780 | Connor et al. | Aug 1999 | A |
| 5961446 | Beller et al. | Oct 1999 | A |
| 5962891 | Arai | Oct 1999 | A |
| 5964700 | Tallman et al. | Oct 1999 | A |
| 5986543 | Johnson | Nov 1999 | A |
| 5989187 | Clawson | Nov 1999 | A |
| 5991730 | Lubin et al. | Nov 1999 | A |
| 5991751 | Rivette et al. | Nov 1999 | A |
| 6004266 | Clawson | Dec 1999 | A |
| 6010451 | Clawson | Jan 2000 | A |
| 6022315 | Iliff | Feb 2000 | A |
| 6035187 | Franza | Mar 2000 | A |
| 6040770 | Britton | Mar 2000 | A |
| 6052574 | Smith, Jr. | Apr 2000 | A |
| 6053864 | Clawson | Apr 2000 | A |
| 6058179 | Shaffer et al. | May 2000 | A |
| 6074345 | van Oostrom et al. | Jun 2000 | A |
| 6076065 | Clawson | Jun 2000 | A |
| 6078894 | Clawson et al. | Jun 2000 | A |
| 6084510 | Lemelson et al. | Jul 2000 | A |
| 6106459 | Clawson | Aug 2000 | A |
| 6112083 | Sweet et al. | Aug 2000 | A |
| 6115646 | Fiszman et al. | Sep 2000 | A |
| 6117073 | Jones et al. | Sep 2000 | A |
| 6118866 | Shtivelman | Sep 2000 | A |
| 6127975 | Maloney | Oct 2000 | A |
| 6134105 | Lueker | Oct 2000 | A |
| 6292542 | Bilder | Sep 2001 | B1 |
| 6370234 | Kroll | Apr 2002 | B1 |
| 6535121 | Matheny | Mar 2003 | B2 |
| 6594634 | Hampton et al. | Jul 2003 | B1 |
| 6607481 | Clawson | Aug 2003 | B1 |
| 6610012 | Mault | Aug 2003 | B2 |
| 6696956 | Uchida et al. | Feb 2004 | B1 |
| 6710711 | Berry | Mar 2004 | B2 |
| 6879819 | Brooks | Apr 2005 | B2 |
| 6901397 | Moldenhauer et al. | May 2005 | B1 |
| 6931112 | McFarland et al. | Aug 2005 | B1 |
| 6968375 | Brown | Nov 2005 | B1 |
| 7106835 | Saalsaa | Sep 2006 | B2 |
| 7194395 | Genovese | Mar 2007 | B2 |
| 7289944 | Genovese | Oct 2007 | B1 |
| 7428301 | Clawson | Sep 2008 | B1 |
| 7436937 | Clawson | Oct 2008 | B2 |
| 7438301 | Schilling et al. | Oct 2008 | B2 |
| 7645234 | Clawson | Jan 2010 | B2 |
| 7703020 | Bhattaru | Apr 2010 | B2 |
| 7783586 | Friedlander et al. | Aug 2010 | B2 |
| 7978826 | Salafia et al. | Jul 2011 | B2 |
| 8066638 | Clawson | Nov 2011 | B2 |
| 8081951 | Blum | Dec 2011 | B1 |
| 8103523 | Clawson | Jan 2012 | B2 |
| 8294570 | Clawson | Oct 2012 | B2 |
| 8335298 | Clawson | Dec 2012 | B2 |
| 8346942 | Ezerzer et al. | Jan 2013 | B2 |
| 8355483 | Clawson | Jan 2013 | B2 |
| 8396191 | Clawson | Mar 2013 | B2 |
| 8417533 | Clawson | Apr 2013 | B2 |
| 8462914 | Ragno et al. | Jun 2013 | B2 |
| 8488748 | Clawson | Jul 2013 | B2 |
| 8494868 | Saalsaa | Jul 2013 | B2 |
| 8538374 | Haimo et al. | Sep 2013 | B1 |
| 8670526 | Clawson | Mar 2014 | B2 |
| 8712020 | Clawson | Apr 2014 | B2 |
| 8873719 | Clawson | Oct 2014 | B2 |
| 8971501 | Clawson et al. | Mar 2015 | B2 |
| 9319859 | Clawson | Apr 2016 | B2 |
| 20020004729 | Zak et al. | Jan 2002 | A1 |
| 20020106059 | Kroll et al. | Aug 2002 | A1 |
| 20030028536 | Singh et al. | Feb 2003 | A1 |
| 20030050538 | Naghavi et al. | Mar 2003 | A1 |
| 20030187615 | Epler | Oct 2003 | A1 |
| 20030195394 | Saalsaa | Oct 2003 | A1 |
| 20030211856 | Zilliacus | Nov 2003 | A1 |
| 20030212575 | Saalsaa et al. | Nov 2003 | A1 |
| 20050015115 | Sullivan et al. | Jan 2005 | A1 |
| 20050065813 | Mishelevich et al. | Mar 2005 | A1 |
| 20060059423 | Lehmann et al. | Mar 2006 | A1 |
| 20060122520 | Banet et al. | Jun 2006 | A1 |
| 20060152372 | Stout | Jul 2006 | A1 |
| 20060167346 | Sarel | Jul 2006 | A1 |
| 20060173500 | Walker et al. | Aug 2006 | A1 |
| 20060178908 | Rappaport | Aug 2006 | A1 |
| 20060212315 | Wiggins | Sep 2006 | A1 |
| 20060225213 | Tomcany | Oct 2006 | A1 |
| 20070055559 | Clawson | Mar 2007 | A1 |
| 20070112275 | Cooke et al. | May 2007 | A1 |
| 20070116189 | Clawson | May 2007 | A1 |
| 20070189480 | Salafia et al. | Aug 2007 | A1 |
| 20070201664 | Salafia et al. | Aug 2007 | A1 |
| 20080208801 | Friedlander et al. | Aug 2008 | A1 |
| 20080310600 | Clawson | Dec 2008 | A1 |
| 20090037374 | Delia et al. | Feb 2009 | A1 |
| 20090168975 | Clawson | Jul 2009 | A1 |
| 20090191529 | Mozingo et al. | Jul 2009 | A1 |
| 20090233631 | Butler, Sr. et al. | Sep 2009 | A1 |
| 20090276489 | Ragno et al. | Nov 2009 | A1 |
| 20100004710 | Kellum | Jan 2010 | A1 |
| 20100121156 | Yoo | May 2010 | A1 |
| 20100152800 | Walker et al. | Jun 2010 | A1 |
| 20100198755 | Soll et al. | Aug 2010 | A1 |
| 20100257250 | Salafia et al. | Oct 2010 | A1 |
| 20110050417 | Piccioni | Mar 2011 | A1 |
| 20110064204 | Clawson | Mar 2011 | A1 |
| 20110066002 | Clawson | Mar 2011 | A1 |
| 20110099031 | Nair | Apr 2011 | A1 |
| 20110205052 | Clawson | Aug 2011 | A1 |
| 20110215930 | Lee | Sep 2011 | A1 |
| 20120034897 | Kreitzer et al. | Feb 2012 | A1 |
| 20120066345 | Rayan | Mar 2012 | A1 |
| 20120171989 | Matsuo et al. | Jul 2012 | A1 |
| 20120183128 | Clawson | Jul 2012 | A1 |
| 20120207286 | Clawson | Aug 2012 | A1 |
| 20120210271 | Clawson | Aug 2012 | A1 |
| 20130100268 | Mihailidis et al. | Apr 2013 | A1 |
| 20140031885 | Elghazzawi | Jan 2014 | A1 |
| 20140211927 | Clawson | Jul 2014 | A1 |
| 20140243749 | Edwards | Aug 2014 | A1 |
| 20150289121 | Lesage | Oct 2015 | A1 |
| 20160088455 | Bozik et al. | Mar 2016 | A1 |
| 20160148490 | Barnes | May 2016 | A1 |
| Number | Date | Country |
|---|---|---|
| 1674685 | Sep 2005 | CN |
| 101169840 | Apr 2008 | CN |
| 201117055 | Sep 2008 | CN |
| 102714524 | Oct 2012 | CN |
| 2476092 | Mar 2011 | EP |
| 2471960 | Jan 2011 | GB |
| 2478171 | Aug 2011 | GB |
| 2482741 | Feb 2012 | GB |
| 2489875 | Oct 2012 | GB |
| 2002-049693 | Feb 2002 | JP |
| 2003-109162 | Apr 2003 | JP |
| 2003-187003 | Jul 2003 | JP |
| 2003-256963 | Dec 2003 | JP |
| 2010-033201 | Dec 2010 | JP |
| 10-2005-0085778 | Aug 2005 | KR |
| 10-2006-0084866 | Jul 2006 | KR |
| 2007-0043337 | Apr 2007 | KR |
| 10-2008-0004125 | Jan 2008 | KR |
| 10-2009-0014837 | Feb 2009 | KR |
| WO2004030259 | Apr 2004 | WO |
| WO 2005039406 | May 2005 | WO |
| WO2006015229 | Feb 2006 | WO |
| WO 2008014398 | Jan 2008 | WO |
| WO2008156876 | Dec 2008 | WO |
| WO2011031383 | Mar 2011 | WO |
| WO2012108898 | Aug 2012 | WO |
| Entry |
|---|
| Office Action Summary from USPTO for U.S. Appl. No. 10/140,635 dated Jul. 16, 2004, 11 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 10/140,635 dated Apr. 19, 2005, 11 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 10/140,635 dated Jan. 17, 2006, 13 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 10/140,635 dated Sep. 20, 2006, 15 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 10/140,635 dated Jun. 21, 2007, 15 pgs. |
| International Search Report for PCT/US2008/054987 filed on Feb. 26, 2008, and dated Oct. 8, 2008, 2 pgs. |
| Written Opinion of the International Searching Authority for PCT/US2008/054987 filed on Feb. 26, 2008, and dated Oct. 8, 2008, 9 pgs. |
| Notification of Transmittal of the International Search Report (2 pgs.) for PCT/US2009/040909, International Search Report, (2 pgs.), and Written Opinion (8 pgs.) mailed from International Searching Authority dated Jun. 10, 2009. |
| International Search Report and Written Opinion for PCT/US09/48577, International filed Jun. 25, 2009, mailed from ISA dated Aug. 7, 2009, 9 pgs. |
| International Search Report and Written Opinion dated Jan. 19, 2011 in PCT Application No. PCT/US2010/043308, filed Jul. 27, 2010. |
| International Search Report and Written Opinion dated Jan. 19, 2011 in PCT Application No. PCT/US2010/043311, filed Jul. 27, 2010. |
| Office Action Summary from USPTO for U.S. Appl. No. 12/396,201 dated Mar. 8, 2011, 23 pgs. |
| International Search Report and Written Opinion PCT/US2010/050402, filed on Sep. 27, 2010, and mailed from ISA dated Apr. 27, 2011, 9 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 12/268,963 dated Jul. 29, 2011, 18 pgs. |
| International Preliminary Report of Patentability for PCT/US2009/048577 filed on Jun. 25, 2009 dated Oct. 27, 2011, 7 pgs. |
| International Search Report and Written Opinion for PCT/US2011/042543 filed on Jun. 30, 2011, mailed from ISA dated Feb. 9, 2012, 11 pgs. |
| International Search Report and Written Opinion for PCT/US2011/042582 filed on Jun. 30, 2011, mailed from ISA dated Feb. 9, 2012, 8 pgs. |
| International Preliminary Report of Patentability for PCT/US2010/043308 filed on Jul. 27, 2010 dated Mar. 22, 2012, 6 pgs. |
| International Preliminary Report of Patentability for PCT/US2010/043311 filed on Jul. 27, 2010 dated Mar. 29, 2012, 6 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 12/558,045 dated Mar. 22, 2012, 9 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 12/558,808 dated Apr. 23, 2012, 9 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 12/422,561 dated Jul. 3, 2012, 21 pgs. |
| International Search Report and Written Opinion for PCT/US2012/021867 filed on Jan. 19, 2012, and mailed from ISA dated Aug. 30, 2012, 8 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 13/354,116 dated Jan. 22, 2013, 9 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 12/422,561 dated Feb. 1, 2013, 26 pgs. |
| Notice of Allowance from USPTO for U.S. Appl. No. 13/026,055 dated Jan. 24, 2013. |
| Notice of Allowance from USPTO for U.S. Appl. No. 10/255,901 dated Feb. 20, 2013. |
| Nordberg, Marie, “Dispatch Disasters,” Emergency Medicine, Aug. 1995. |
| Notice of Allowance from USPTO for U.S. Appl. No. 13/354,116 dated Jun. 7, 2013. |
| Liferidge, Aisha T., et al., “Ability of Laypersons to Use the Cincinnati Prehospital Stroke Scale”, Prehospital Emergency Care, Elsevier, vol. 8, No. 4, Oct. 1, 2004, pp. 384-387. |
| Office Action Summary from USPTO for U.S. Appl. No. 13/026,043 dated Oct. 10, 2013. |
| International Preliminary Report of Patentability for PCT/US2011/042543 filed on Jun. 30, 2011 dated Aug. 22, 2013, 7 pgs. |
| International Preliminary Report of Patentability for PCT/US2011/042582 filed on Jun. 30, 2011 dated Aug. 22, 2013, 5 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 13/605,501 dated Nov. 18, 2013. |
| International Search Report and Written Opinion for PCT/US2013/055537 filed on Aug. 19, 2013 and mailed from ISA dated Nov. 22, 2013. |
| Notice of Allowance from USPTO for U.S. Appl. No. 13/026,043 dated Jan. 13, 2014. |
| Nor, A. Mohd, et al., “Agreement Between Ambulance Paramedic—and Physician-Recorded Neurological Signs With Face Arm Speech Test (FAST) in Acute Stroke Patients”, http://stroke.ahajournals.org/content/35/6/1355, Apr. 29, 2004, visited Nov. 17, 2013, 3 pgs. |
| Clark University “Active Shooter Emergency Plan” Revised Jan. 11, 2013. |
| Notice of Allowance from USPTO for U.S. Appl. No. 13/605,501 dated Mar. 6, 2014. |
| International Search Report and Written Opinion for PCT/US2014/011405 filed on Jan. 14, 2014 and mailed from ISA dated Apr. 25, 2014. |
| International Search Report and Written Opinion for PCT/US2014/014029 filed on Jan. 31, 2014 and mailed from ISA dated May 16, 2014. |
| Office Action Summary from USPTO for U.S. Appl. No. 13/755,793 dated Jul. 21, 2014. |
| International Preliminary Report of Patentability for PCT/US2013/055537 filed on Aug. 19, 2013 dated Mar. 19, 2015. |
| Notice of Allowance from USPTO for U.S. Appl. No. 12/422,561 dated Dec. 9, 2014. |
| Notice of Allowance from USPTO for U.S. Appl. No. 13/755,793 dated Sep. 22, 2014. |
| Non-Final Office Action for U.S. Appl. No. 14/169,302 filed Jan. 31, 2014, and mailed from the USPTO dated Sep. 25, 2015, 46 pgs. |
| Notice of Allowance and Fee(s) Due for U.S. Appl. No. 14/169,302 filed Jan. 31, 2014, and mailed from the USPTO dated Mar. 4, 2016, 13 pgs. |
| Non-Final Office Action for U.S. Appl. No. 14/723,947 filed May 28, 2016, and mailed from the USPTO dated Mar. 31, 2016, 33 pgs. |
| Non-Final Office Action for U.S. Appl. No. 15/083,810 filed Mar. 29, 2016, and mailed from the USPTO dated Jul. 15, 2016, 28 pgs. |
| Notice of Allowance and Fee(s) Due for U.S. Appl. No. 15/083,810 filed Mar. 29, 2016, and mailed from the USPTO dated Sep. 23, 2016, 14 pgs. |
| Notice of Allowance and Fee(s) Due for U.S. Appl. No. 14/723,947 filed May 28, 2015, and mailed from the USPTO dated Oct. 24, 2016, 29 pgs. |
| Peck, “Got a Minute?You Could Diagnose a Stroke,” WebMD Health News, http://www.webmd.com/stroke/news/20030213/got-minute-you-could-diagnosie-stroke, Feb. 13, 2003, 3 pgs. |
| Radosevich, Lynda, “Network holds sway on life, death,” Computerworld, v27 n21, May 24, 1993, 2 pgs. |
| Harris, Roger, “Updated 911 Phone System Top Concern of Residents,” Business First-Louisville, v9 n19 s1, Dec. 1992, 3 pgs. |
| “Geac Completes Software Install,” Wireless Week, Nov. 18, 1996, 3 pgs. |
| “Dictaphone introduces Windows-based Computer-Aided Dispatch (CAD) system,” Business Wire, Apr. 23, 1996, 2 pgs. (in commercial use in 1995). |
| Holroyd, Brian, et al., “Medical Control; Quality Assurance in Prehospital Care,” JAMA, the Journal of American Medical Association, v256, n8, Aug. 1986, p. 1027-1031. |
| CBS web page News Story entitled “911 Operator: ‘It's got to be Hell’”, Mar. 31, 2006 (excerpts from 911 operators' actions during the attacks on Sep. 11, 2001), 3 pgs. |
| Best, Wendy, “999 United Emergency services share life-saving Role to boost response,” Western Daily Press, WDP Severnside ed., May 27, 1999, 2 pgs. |
| Poellmitz, William C., “Wireless technology keeps public safety a step ahead,” Nation's Cities Weekly, v21 n17, Apr. 27, 1998, 3 pgs. |
| Crowley, Mark, “Learning from CAD System Implementation,” Communications, v29 n8, Aug. 1992, 5 pgs. |
| Anonymous, “Suburban Chicago towns centralize 911 services,” Communications News, v31 n10, Oct. 1994, 2 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 10/255,901 dated Dec. 31, 2003, 8 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 10/255,901 dated Oct. 13, 2004, 8 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 10/255,901 dated Jun. 29, 2005, 7 pgs. |
| Advisory Action Before the Filing of an Appeal Brief from USPTO for U.S. Appl. No. 10/255,901 dated Feb. 14, 2006, 3 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 10/255,901 dated Jun. 7, 2006, 8 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 10/255,901 dated Feb. 27, 2007, 8 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 10/255,901 dated Sep. 6, 2007, 9 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 10/255,905 dated May 19, 2004, 7 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 10/255,905 dated May 26, 2005, 5 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 10/255,905 dated Feb. 9, 2006, 8 pgs. |
| Advisory Action Before the Filing of an Appeal Brief from USPTO for U.S. Appl. No. 10/255,905 dated Aug. 11, 2006, 3 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 10/255,905 dated Jan. 30, 2007, 7 pgs. |
| Notice of Non-Compliant Amendment (37 CFR 1.121) from USPTO for U.S. Appl. No. 10/255,905 dated Jul. 9, 2007, 4 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 10/255,905 dated Oct. 5, 2007, 7 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 09/685,697 dated Jul. 18, 2003, 8 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 09/685,697 dated Feb. 3, 2004, 5 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 09/685,697 dated Jan. 4, 2005, 5 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 09/685,697 dated Oct. 4, 2005, 7 pgs. |
| Advisory Action Before the Filing of an Appeal Brief from USPTO for U.S. Appl. No. 09/685,697 dated Mar. 13, 2006, 4 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 09/685,697 dated Jun. 26, 2006, 8 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 09/685,697 dated Apr. 10, 2007, 9 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 09/685,697 dated Oct. 9, 2007, 11 pgs. |
| Office Action Summary from USPTO for U.S. Appl. No. 10/140,635 dated Oct. 3, 2003, 9 pgs. |
| International Search Report and Written Opinion for International Application No. PCT/US2017/021519 filed Mar. 9, 2017, and mailed from the International Search Authority dated May 22, 2017, 17 pgs. (23517/3601 PCT). |
| Number | Date | Country | |
|---|---|---|---|
| 20170295477 A1 | Oct 2017 | US |
