An interface between a computer aided dispatch system and an emergency medical dispatch protocol is provided. Able to operate in either a resident or a non-resident mode, this invention coordinates the transfer of control and information between the computer aided dispatch system and the emergency medical dispatch protocol to improve the efficiency of emergency medical response resources while maintaining the certainty of the use of an established medical response and instruction protocol.
|
1. A method for integrating a computer aided dispatch system and an emergency medical dispatch protocol, comprising:
(A) initiating a computer aided dispatch system;
(B) receiving an incident call;
(C) calling an expert emergency medical dispatch system, said expert emergency medical dispatch system interrogating for information; calculating a determinate value based on said information; and setting a dispatch process state for use by said computer aided dispatch system;
(D) returning control to saId computer aided dispatch system, said computer aided dispatch system testing for said desired dispatch process states, wherein said dispatch process states provide a control for the operation of said computer aided dispatch system; and
(E) returning control to said expert emergency medical dispatch system.
11. A system for integrating a computer aided dispatch system and an emergency medical dispatch protocol, comprising:
(A) a computer device; and
(B) a computer program operating on said computer device, wherein said computer program further comprises:
(1) an operating system, managing the operation of said computer device;
(2) a computer aided dispatch system operating in cooperation with said operating system to manage emergency response resources;
(3) an emergency medical response protocol system for guiding a dispatcher's response to a caller, wherein said emergency medical response protocol system further comprises a set of specified inquiries, a calculated determinate value based one or more responses to said set of specified inquiries, and a defined emergency medical response based on said determinate value; and
(4) an interface between said computer aided dispatch system and said emergency medical response protocol system, wherein said interface is a process for communicating information between said computer aided dispatch system and said emergency medical response protocol system, wherein said interface further comprises a miscellaneous file containing information unique to a workstation; a configuration file containing configuration variables; a communication file which is a bidirectional file for use in communicating data between said computer aided dispatch system and said emergency medical response protocol system, a set of state flags set by said emergency medical response protocol system and detected by said computer aided dispatch system to control operation of said computer aided dispatch system; and an export file.
2. A method for integrating a computer aided dispatch system and an emergency medical dispatch protocol, as recited in
3. A method for integrating a computer aided dispatch system and an emergency medical dispatch protocol, as recited in
4. A method for integrating a computer aided dispatch system and an emergency medical dispatch protocol, as recited in
5. A method for integrating a computer aided dispatch system and an emergency medical dispatch protocol, as recited in
6. A method for integrating a computer aided dispatch system and an emergency medical dispatch protocol, as recited in
7. A method for integrating a computer aided dispatch system and an emergency medical dispatch protocol, as recited in
8. A method for integrating a computer aided dispatch system and an emergency medical dispatch protocol, as recited in
9. A method for integrating a computer aided dispatch system and an emergency medical dispatch protocol, as recited in
10. A method for integrating a computer aided dispatch system and an emergency medical dispatch protocol, as recited in
12. A system for integrating a computer aided dispatch system and an emergency medical dispatch protocol, as recited in
(1) a processor, wherein said processor is capable of opelating both a computer aided dispatch system and an emergency medical response protocol system;
(2) a memory unit in electronic communication with said processor;
(3) a display device in electronic communication with said processor; and
(4) an input device in electronic communication with said processor.
13. A system for integrating a computer aided dispatch system and an emergency medical dispatch protocol, as recited in
14. A system for integrating a computer aided dispatch system and an emergency medical dispatch protocol, as recited in
(a) initiating a computer aided dispatch system;
(b) receiving an incident call;
(c) calling an expert emergency medical dispatch system, said expert emergency medical dispatch system setting one or more desired process states;
(d) returning to said computer aided dispatch system, said computer aided dispatch system testing for said one or more desired process states; and
(e) returning control to said expert emergency medical dispatch system.
|
|||||||||||||||||||||||||
1. Field of the Invention
This invention relates to methods and systems for integrating computer applications. More specifically, this invention relates to methods and systems for integrating a computer aided dispatch (CAD) system with a medical protocol interrogation process operating on a computer system.
2. Description of Related Art
A variety of computer software interface methods and systems have been proposed to provide an interface between two or more previously disconnected computer program methods. Generally, these prior systems and methods are not adapted to function with a computer aided dispatch system and a medical protocol interrogation process.
The reader is referred to the following U.S. patent documents for general background material. Each of these patents is hereby incorporated by reference in its entirety for the material contained therein.
U.S. Pat. No. 5,857,966 describes a method and system for receiving processing and responding to emergency medical calls for patients who have fainted or are unconscious.
U.S. Pat. No. 5,989,187 describes a method and system for providing emergency medical counseling to childbirth patients remotely.
U.S. Pat. No. 6,004,266 describes a method and system for receiving, processing and responding to emergency medical calls for patients with heart problems.
U.S. Pat. No. 6,010,451 describes a method and system for providing emergency medical counseling to choking patients remotely.
U.S. Pat. No. 6,053,864 describes a method and system for providing emergency medical counseling to arrest patients remotely.
It is desirable to provide a method and system for combining a computer aided dispatch system with an emergency medical dispatch protocol that provides an integrated dispatch system which enables a call taker to rapidly and safely navigate through the medical protocol, wherein key questions and answers are pre-determined in the logic of an expert system to calculate an appropriate determinate level and thereby the appropriate emergency medical response. The determinate level provides a categorization code of the type and level of the incident, the code is provided to a Computer Aided Dispatch system, which is a tool used by dispatchers to track and allocate emergency response resources, for processing.
Accordingly, it is an object of this invention to provide an interface between a computer aided dispatch system and an emergency medical dispatch protocol.
Another object of this invention is to provide an interface between a computer aided dispatch system and an emergency medical dispatch protocol, which enhances the cooperation between the two processes.
A further object of this invention is to provide an interface between a computer aided dispatch system and an emergency medical dispatch protocol, which operates in a multi-tasking environment.
A still further object of this invention is to provide an interface between a computer aided dispatch system and an emergency medical dispatch protocol, which enables a call-taker to rapidly, and consistently navigate through a medical protocol.
It is another object of this invention to provide an interface between a computer aided dispatch system and an emergency medical dispatch protocol in which key questions and answers are pre-determined in internal logic to generate an appropriate response determinate.
It is a further object of this invention to provide an interface between a computer aided dispatch system and an emergency medical dispatch protocol, which provides quality assurance procedures.
Another object of this invention is to provide an interface between a computer aided dispatch system and an emergency medical dispatch protocol that includes a reporting capability to measure the performance of individual staff and overall center performance.
A further object of this invention is to provide an interface between a computer aided dispatch system and an emergency medical dispatch protocol that provides a standardized coding system for use in the computer aided dispatch system.
A still further object of this invention is to provide an interface between a computer aided dispatch system and an emergency medical dispatch protocol that communicates the type and level of criticality of the incident from the protocol to the computer aided dispatch system.
A further object of this invention is to provide an interface between a computer aided dispatch system and an emergency medical dispatch protocol that, in combination with a computer aided dispatch system and the protocol, provides the means of tracking and allocating emergency medical resources.
Additional objects, advantages and other novel features of this invention will be set forth in part in the description that follows and in part will become apparent to those skilled in the art upon examination of the following or may be learned with the practice of the invention. The objects and advantages of this invention may be realized and attained by means of the instrumentalities and combinations particularly pointed out in the appended claims. Still other objects of the present invention will become readily apparent to those skilled in the art from the following description wherein there is shown and described the preferred embodiment of this invention, simply by way of illustration of one of the modes best suited to carry out this invention. As it will be realized, this invention is capable of other different embodiments, and its several details and specific steps are capable of modification in various aspects without departing from the concept of this invention. Accordingly, the objects, drawings and descriptions should be regarded as illustrative in nature and not as restrictive.
The accompanying drawings incorporated in and forming a part of the specification, illustrate a preferred embodiment of the present invention. Some, although not all, alternative embodiments are described in the following description. In the drawings:
Reference will now be made in detail to the present preferred embodiment of the invention, an example of which is illustrated in the accompanying drawings.
This invention is a method and system for combining and facilitating the operation of a computer-aided dispatch (CAD) system with an emergency medical dispatch system which enables an emergency call taker to rapidly, safely and consistently navigate through an emergency medical protocol.
CAD is a tool used by dispatchers to track and allocate resources. The primary information used in this task is location information of both the incident and units, unit availability and the type of incident. CAD systems typically use third party solutions, such as E-911, vehicle location transponders and MDT's for automating the location and availability tasks.
In its present preferred embodiment, this invention works with a software expert system, wherein key questions and answers are processed according to predetermined logic to both provide the correct emergency medical dispatch response and the appropriate doctor-approved post-dispatch instructions to the call taker before professional help arrives. The reader should note that for the purposes of this disclosure, the following terms shall be treated as synonyms, in the present preferred embodiment of the invention: expert system, software expert system, medical dispatch system or program, emergency medical dispatch expert system, ProQA and derivations thereof. The software expert system calculates a determinate value from the caller's responses and uses this determinate value to present the appropriate response for use by the dispatcher. Since many calls for medical service are not true medical emergencies, 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 more severe medical problems should receive the more advanced units. And finally, if lights-and-siren are not needed from a medical standpoint, they should not be used, thereby increasing the safety of all those on the road.
The present expert system provides a protocol, which includes a consistent carefully chosen set of questions, the responses to which are used to calculate a determinate value. The determinate value is used to classify the degree of emergency and to recommend the appropriate level of emergency medical response, both in terms of the type of equipment and the required speed of response. Since the questions asked and the recommendations that are made by the expert system deal directly with life and death decisions, the protocols used with this invention shall have passed through a rigorous medical review by a panel of doctors and EMS public safety experts who specialize in emergency medicine.
While many medical calls are not true emergencies, all situations can benefit from medical evaluation and instruction. Prior to the arrival of professional help on-scene, the expert system provides instructions that are appropriate to the type of call, from minor lacerations to someone who is not breathing.
The preferred expert system used with this invention has a built-in reporting capability to statistically measure the performance of individual staff and overall center performance. These statistics include compliance rates; call processing statistics and peer measurements. The expert system also determines the incident code, via a standardized coding system from an established protocol.
The expert system, in the preferred embodiment, can be run as a stand-alone application. However, because the information the expert system provides can be very effectively used as a tool within the CAD environment when properly integrated, this invention provides this integration.
The use of this invention begins with the creation of a medical call incident. A CAD call taker identifies the call as requiring access to the expert system, which is then called into operation to begin the Emergency Medical Dispatch (EMD) interrogation. Once the type and level of incident has been determined, the program returns to the CAD for processing of the information. In a horizontal dispatch center, the call taker then continues the expert system process while a radio dispatcher allocates the necessary equipment and performs the dispatch (and can obtain a summary of information from the expert system about the incident). In a vertical dispatch center, the call taker/dispatcher takes the required time to allocate and dispatch the emergency dispatch units, returning to the expert system for further instructions. The expert system has the capability to sense a change of dispatch, through the reconfiguration process (generally brought about by changing the answers to key questions during subsequent interrogation of the caller). Alerts and new incident codes are also communicated to CAD for any necessary processing. The preferred expert system is capable of handling multiple incidents, through the ability to place the call “on hold” and return a later time. Finally, once the call taker has completed the call, the expert system can be used to recall a closed incident if the caller accesses the center again.
In the present embodiment of the invention four files are used for configuration and communication purposes. These files are (1) a miscellaneous file, generally referred to as MISCFILE; (2) a configuration file, contained in the directory referenced by the files environment variable, generally referred to as AMPDSSYS; (3) a communications file, generally referred to as COMMFILE; and (4) an export file. Each of these four files is generally described as follows.
The miscellaneous file may be created using a file name of the CAD vendor's choice and set in an environment variable. This environment variable should contain the full path and file name of the miscellaneous file. Preferably, there should be separate miscellaneous files for each workstation on the system. Ideally, the miscellaneous files are located on the storage drive 101 of each workstation 100, rather than on a networked disk drive unit. In the present embodiment of the invention, the miscellaneous file contains information that is unique for each workstation in an installation. It contains the ID of the currently logged-on operator, a flag indicating if phone line ID numbers are used, the station number of the particular workstation 100 and a flag indicating if the expert medical dispatch software system is running in a resident mode or not.
The configuration file is a text file that contains several configuration parameters used by the expert medical dispatch software in a CAD environment. If any of the variables need to be set to non-default values, this file can be created or edited by a text editor in the sub-directory specified in the environment variables. Presently available variables for use in the configuration file include the following, each of which is identified with a brief description of its function. AllowReleaseToPend allows the user to release the call to pending and to return the program beck to CAD control. AllowOverride allows the operator to override to a higher response. AskGenderAgeOnUnk indicates that the user is always to obtain an age and gender. ExitOnDispatch sets the expert system to exit or pend on SEND events. AccessNoHiSublvls allows access to sub-levels other than those highlighted by the expert system recommendation. AllowMenuReconfig allows the Reconfigure Dispatch option. LogoffOnExit sets the system to always logoff the operator when the operator exits case entry. PollDelay is an integer value that represents the time in seconds that the expert system is to wait between polls of the communications file. PollCMode sets the communication file to close after every polling cycle or to leave the communication file open all of the time in a share mode or to close only when the status changes. PollFile provides the path and file name to poll the state of the current case instead of the communications file. CommFileMode can be set to (1) no CAD interface; (2) communication file is a disk file; (2) communication file is a named pipe; (3) communication file is a named message queue; (4) communication file is a DDE link; or (5) communication file is a TCP/IP socket. SignalCatch indicates whether when a signal is sent to case entry, a case in process will be aborted or if the signal will be ignored. AdjustCaseState indicates whether case states will be automatically adjusted to the correct value as necessary or whether an error will occur. ScreenDelay is an integer value that represents the timer value before the end of input is assumed on the entry of chief complaint numbers. ResponderScript indicates if the text from the responder script should be included in the COMMFILE. AllowProbDescPassed indicates whether CAD is to pass problem description text into the expert system. UpdatePassedCEfields allows the user to modify the location and callback fields in the expert system that have been passed from CAD, or keeps the user from modifying the location and callback fields in the expert system when they are passed from CAD. WriteCADonCEend causes the ProQA to update the COMMFILE with all available information when the user moves from Case Entry to Key Questions. AbortMode provides that when the operator aborts a case an abort DDE message is sent to CAD. AbortCADcode contains the returned string received by CAD in the CAD Incident Code field of the COMMFILE. AbortDispCode contains the returned string received by DAD in the Dispatch Level field of the COMMFILE. AllowAbortReason permits that the user can either type in free form text as a reason to abort a case or can only choose from the list of administrator defined abort reasons. AllowClose determines if the user can close the expert system through normal operating system conventions or must be shut down through CAD. AutoActivate permits the expert system to automatically change window states when the case state flag is set. AutoDeactivateDisp indicates whether the expert system will minimize itself on dispatch. AutoDeactivateClose indicates whether the expert system will minimize itself on case completion or will remain active on case completion. AutoNetLogin indicates if the network logon is used to automatically login to the expert system. Epoch specifies the current epoch for two-digit year entry. NotifyCADonStop indicates whether the COMMFILE should receive T state flag when the expert system is shutdown by the user. WriteCOMMFILEoninit indicates whether the COMMFILE will be rewritten when a case is initialized. WriteCOMMFILEonKQend if set causes the expert system to update the COMMFILE with all available information when the user moves from Key Questions to DLSs. FileAccessMode indicates whether database access is through a locally available file system or is via a TCP/IP to a database server. ServerName is a string value identifying the name of the database server. AutoPrintOnSend can be set to print selected case information when send or reconfigure occurs. AutoPrintOnClose can be set to print selected case information when the case is closed. AutoPrintSCaseInfo can be set print main case information. AutoPrintS4cmds can be sent to print the four commandments of the expert system. AutoPrintSDispInfo can be set to print dispatch information. AutoPrintSRespScr can be set to print the responder script. AutoPrintSTimeStamps can be set to print the time stamp information. AutoPrintSRunTimes can be set to print the running times. AutoPrintSKQs can be set to print the key questions of the expert system. AutoPrintSSeqs can be set to print the case sequences. AutoPrintSPrinter is set to the name of the printer to use when printing dispatch information on send. AutoPrintCCaseInfo can be set to print the main case information. AutoPrintC4cmds can be set to print the four commands of the expert system. AutoPrintCDispInfo can be set to print the dispatch information. AutoPrintCRespScr can be set to print the responder script. AutoPrintCTimeStamps can be set to print the time stamp information. AutoPrintCRunTimes can be set to print the running times. AutoPrintCKQs can be set to print the key questions. AutoPrintCSeqs can be set to print the case sequences. AutoPrintCPrinter is set to name the printer to use when printing dispatch information on closing a case. The communication file is the device by which CAD and the emergency dispatch expert system transfer information. Conceptually, the communication file is analogous to a shared memory segment in Unix with the first byte being a semaphore, controlling access to the rest of the memory/file. Preferably it should be a shared memory segment for speed and I-node use reasons, however, it can also be implemented as a file for portability with platforms that do not support inter-process communications. Since it is desirable to improve performance and to maintain multi-platform capability, the present implementation of this invention supports message queues and named pipes in Unix and DDE in Windows. The communication file may be created using a file name of the CAD vendor's choice and set in the environment variable COMMFILE. This variable would typically contain the full path and file name of the communication file. Preferably, the communication files are located on each workstation rather than a networked disk drive. The COMMFILE is presently treated as a sequential text file that contains alphanumeric and special punctuation or separator characters terminated by a new line character. Typically, the first line is a series of flags that indicate the presence or absence of subsequent lines and the status of the current case. The remaining lines contain data as indicated in the flags set in the first line. Presently the first line has thirty characters. The following table provides the present possible contents of each position and what that content means to the preferred emergency medical dispatch expert system. This is a bi-directional file, which is used to communicate between CAD and the expert system.
Position
Description
Content
Meaning
1**
State of the current case
I
Initialize
CAD
ex sys
P
Pend
ex sys
CAD
A
Abort
ex sys
CAD
D
Dispatch
ex sys
CAD
R
Reconfig.
ex sys
CAD
C
Complete
ex sys
CAD
O
Re-open
CAD
ex sys
E*
Error
ex sys
CAD
W*
Waiting
CAD
ex sys
U*
Unpend
CAD
ex sys
Q*
Quit
CAD
ex sys
S*
Case Sum.
CAD
ex sys
T*
Stopped
ex sys
CAD
B*
Bring-top
CAD
ex sys
M*
Case Entry finished
message
ex sys
CAD
K*
Key Question finished
message
ex sys
CAD
N*
New case # assigned
ex sys
CAD
2**
Operator number
Y
Operator no. specified
N
Operator no. not specif.
3**
Incident number
Y
Incident no. specified
N
Incident no. not specif.
4**
Location of incident
Y
Location of incident
spec.
N
Location of incident not
specified
5**
Call back phone number
Y
Call back phone number
specified
N
Call back phone number
not specified
6
Problem (description)
Y
Problem specified
N
Problem not specified
7
Number of patients
Y
Number of patients
specified
N
Number of patients
not specified
8
Age (numerical)
Y
Age specified
N
Age not specified
9
Units of the age
Y
Units of age specified
N
Units of age not specif.
10
Sex of the patient
Y
Sex specified
N
Sex not specified
11
Is the patient conscious?
Y
Consciousness specified
N
Consciousness not
specified
12
Is the patient breathing?
Y
breathing specified
N
breathing not specified
13
Chief complaint number
Y
Chief Complaint specif.
N
Chief Complaint not
specified
14
Dispatch level
Y
Dispatch level specified
N
Dispatch level not
specified
15
Reconfigured dispatch level
Y
Reconfigured dispatch
level specified
N
Reconfigured dispatch
level not specified
16**
Export file name
Y
Export file name specif.
N
Export file name not
specified
17**
Call phone line number
Y
Call phone line no.
specif.
N
Call phone line no. not
specified
18**
Override incident number
Y
Override incident number
specified
N
Override incident number
not specified
19**
Return Information
Y
Return information
specified
N
Return information not
specified
20**
Keystrokes to exit expert
system
Y
Keystrokes to exit expert
system specified
N
Keystrokes to exit expert
system not specified
21
Keystroke ending session
Y
Keystroke ending session
specified
N
Keystroke ending session
not specified
22
Dispatch Level Suffix
Y
Dispatch level suffix
specified
N
Dispatch level suffix not
specified
23
Medical Response Text
Y
Medical response text
specified
N
Medical response text not
specified
24
Abort Text
Y
Abort text specified
N
Abort text not specified
25
Reevaluation
Y
Reevaluation specified
Reevaluation not
specified
26
Exit Error Code
Y
Exit error code specified
N
Exit error code not
specified
27**
Post Send Dialog Message
Y
Post send dialog message
flag specified
N
Post send dialog message
flag not specified
28
CAD incident code
Y
CAD incident code
specified
N
CAD incident code
not specified
29**
Automatic Case Complete
Y
Automatic case complete
specified
N
Automatic case complete
not specified
30
Responder Script
Y
Responder script
specified
N
Responder script not
specified.
Below is an example of a communication file:
INYYYNNNNNNNNNNNNNNNNNNNNNNNN
0093000001
1025 East Harrington Place
712-675-0098
The beginning “I” above indicates that this incident is being initialized. This flag is used to avoid a partially processed incident being passed to the expert system. When a new incident is started, the expert system is informed so that it does not attempt to access non-existent historical information. In initializing the resident version of the expert system, this flag will presently be set to “W,” and all other flags will be set to “N.” The second position is an “N” which indicates that no operator ID will be passed to the expert system. This means that the expert system will use the operator ID. If the miscellaneous file has “logged-out” as the operator and no operator ID is passed to the expert system, through the COMMFILE, or the operator ID is invalid, an error will occur. Each valid operator ID passed in the COMMFILE will update the miscellaneous file automatically so that the miscellaneous file will contain the most recently used operator ID. Each new operator ID passed in the COMMFILE will be added to the operator database on the first reference. Positions three through five are “Y”′s. This indicates that an incident number, location and call back number will be expected in the communication file on the second, third and fourth lines. The rest of the top line contains “N”′s. This means that no other information will be passed in the communication file. Not all of the possible information needs to be exchanged each time. It is up to the CAD vendor to decide what information is important for them to share with the expert system. Only those items marked with “**” in the table above should be passed by CAD through the COMMFILE to the expert system. It is suggested that the location and call back number always be exchanged.
The limitations on the type of data stored in each fields (or lines) is described in the table below. In the present embodiment, all alpha characters are converted to upper case by the preferred expert system.
Line
Description
Length or possible content1
1.
State/Flags
30 characters
2.
Operator number
1 to 10 alphanumeric characters
specifying the
operator ID on file with expert system
3.
Incident number
1 to 10 alphanumeric characters
specifying the case
number.
4.
Location of incident
1 to 60 alphanumeric characters
5.
Call back phone
1 to 20 numeric and punctuation
number
characters
6.
Problem description
1–40 alphanumeric characters
7.
Number of patients
Numeric characters ranging 1 to 127
or the text “UNKNOWN”
8.
Age
Numeric characters ranging 1 to 127
or an “age range” description
9.
Units of the age
Description of the contents of the “Age”
field, i.e., years, months or range
10.
Sex of patient
Description of patient “” gender; i
i.e., MALE, FEMALE, UNKNOWN
11.
Is the patient
Description of patient's state of
conscious?
consciousness;
i.e., YES, NO, UNKNOWN
12.
Is the patient
Description of patient's state of
breathing?
breathing;
i.e., YES, NO, UNCERTAIN, UNKNOWN
13.
Chief complaint
Numeric characters ranging 1 to 32
number
14.
Dispatch level
Special format
15.
Reconfigure
Special format
dispatch level
16.
Export file name
1 to 80 legal file name characters
17.
Phone line number
1 to 4 alphanumeric characters
18.
Override incident
1 to 10 alphanumeric characters,
number
which will
change the current case number,
assigned.
19.
Return information
String of “Y”s and “N”s indicating
which fields
should be returned to the CAD
system in the
communication file.
20.
Keystrokes to exit
List of keystrokes used to
expert system
exit expert
system. These are in a two-
character format.
21.
Keystroke which
A two-character field
ended session
showing which
keystroke was used to exit the
expert system.
22.
Dispatch level suffix
Only applicable on chief complaint
numbers 4,
23 and 27.
23.
Medical response
The actual text of the response as it
text
appears on
the key question screen.
24.
Abort text
The actual text of the reason for
aborting
the case.
25.
Reevaluation
A “Y” or “N” indicating whether to
allow
reevaluation or not.
26.
Exit error code
The code number of the error, which
caused the
expert system to terminate.
27.
Post send dialog
“Y” or “N” indicating whether or not
message
a dialog
box should appear on the screen
after a send or
reconfigure, and prior to an
automatic jump to
Pre-Arrival Instructions.
28.
CAD incident code
Returns the CAD incident code for
the dispatch
determinant, if it exists in the user-
defined
responses.
29.
Automatic case
I set to “Y” the expert system
complete
performs a case
complete without any further action
by the
operator.
30.
Responder script
Returns human readable text
describing the sit
situation.
The communications file, in the present preferred embodiment, is handled differently depending on whether the invention is operating in the non-resident mode or the resident mode.
The resident mode has the same option to reopen as non-resident mode and works basically in the same manner. As with typical case processing, the difference between non-resident mode and resident mode is that in resident mode rather than calling the expert system after writing to the communication file, the CAD process goes into a polling mode to detect a change in the state flag.
The previous described preferred embodiments of the invention are to be considered in all respects only as illustrative and not as restrictive. Although the embodiments shown describe particular components in particular connection configurations, the invention is not limited thereto. The scope of this invention is indicated by the appended claims rather than by the foregoing description. All systems and devices, which come directly within the claims or within the meaning and range of equivalency of the claims, are to be embraced as being within the scope of protection of this invention.
| Patent | Priority | Assignee | Title |
| 10051047, | Oct 16 2015 | ATOS FRANCE | Load-balancing server for data transformation modules |
| 10105108, | Apr 06 2018 | Leeps Pro, Inc. | First responder dispatch system and methods of operation thereof |
| 10192277, | Jul 14 2015 | AXON ENTERPRISE, INC | Systems and methods for generating an audit trail for auditable devices |
| 10409621, | Oct 20 2014 | TASER International, Inc. | Systems and methods for distributed control |
| 10657614, | Dec 23 2015 | Locator diagnostic system for emergency dispatch | |
| 10699548, | Apr 19 2018 | Expedited dispatch protocol system and method | |
| 10848717, | Jul 14 2015 | AXON ENTERPRISE, INC | Systems and methods for generating an audit trail for auditable devices |
| 10901754, | Oct 20 2014 | Axon Enterprise, Inc. | Systems and methods for distributed control |
| 11025706, | Oct 16 2015 | ATOS FRANCE | Load-balancing server for data transformation modules |
| 11152107, | Sep 29 2016 | International Business Machines Corporation | System, method and computer program product for dispatching of medical emergencies and wait time control |
| 11544078, | Oct 20 2014 | Axon Enterprise, Inc. | Systems and methods for distributed control |
| 11547372, | Apr 06 2018 | Leeps Pro, Inc. | First responder dispatch system and methods of operation thereof |
| 11900130, | Oct 20 2014 | Axon Enterprise, Inc. | Systems and methods for distributed control |
| 11910471, | Apr 23 2021 | Priority Dispatch Corporation | System and method for emergency dispatch |
| 11937160, | Apr 23 2021 | Priority Dispatch Corporation | System and method for emergency dispatch |
| 7428301, | Oct 09 2000 | Method and system for the exit protocol of an emergency medical dispatch system | |
| 7436937, | Sep 26 2001 | Method and system for the police response dispatch protocol of an emergency dispatch system | |
| 7515693, | Aug 06 2004 | PowerPhone, Inc. | Call handler systems and methods |
| 7645234, | Jun 13 2007 | Diagnostic and intervention tools for emergency medical dispatch | |
| 8066638, | Jun 13 2007 | Diagnostic and intervention tools for emergency medical dispatch | |
| 8103523, | Jun 13 2007 | Diagnostic and intervention tools for emergency medical dispatch | |
| 8294570, | Feb 24 2010 | Burn diagnostic and intervention tool for emergency dispatch | |
| 8335298, | Sep 14 2009 | Pandemic diagnostic and intervention tool for emergency dispatch | |
| 8355483, | Sep 11 2009 | Stroke diagnostic and intervention tool for emergency dispatch | |
| 8396191, | Feb 11 2011 | Anti-social protocol for emergency dispatch | |
| 8417533, | Sep 25 2001 | Method and system for the fire response dispatch protocol of an emergency dispatch system | |
| 8488748, | Jan 19 2011 | Meningitis diagnostic and intervention tool for emergency dispatch | |
| 8494121, | Mar 08 2010 | System and method for gathering information at a crisis scene | |
| 8494868, | May 07 2002 | Priority Dispatch Corporation | Method and system for a seamless interface between an emergency medical dispatch system and a nurse triage system |
| 8582866, | Feb 10 2011 | Golden Edge Holding Corporation | Method and apparatus for disparity computation in stereo images |
| 8670526, | Feb 11 2011 | Hate crime diagnostic and intervention tool for emergency dispatch | |
| 8712020, | Sep 06 2012 | Pandemic protocol for emergency dispatch | |
| 8838061, | Dec 21 2011 | MOTOROLA SOLUTIONS, INC | Method and apparatus for providing multiparty participation and management for a text message session |
| 8873719, | Jan 31 2013 | Active assailant protocol for emergency dispatch | |
| 8971501, | Apr 13 2009 | Priority Dispatch Corporation | Methods and systems to identify code hierarchy bias in medical priority dispatch systems |
| 9319859, | Jan 31 2013 | System and method for text messaging for emergency response | |
| 9491605, | Jan 31 2013 | Text messaging for emergency response | |
| 9516166, | May 28 2015 | Chemical suicide protocol for emergency response | |
| 9877171, | Apr 08 2016 | Picture/video messaging protocol for emergency response |
| Patent | Priority | Assignee | Title |
| 4926495, | Dec 11 1986 | Motorola, Inc | Computer aided dispatch system |
| 5805670, | Mar 19 1996 | General Electric Capital Corporation | Private notification system for communicating 9-1-1 information |
| 5857966, | Mar 28 1997 | Method and system for the unconscious or fainting protocol of an emergency medical dispatch system | |
| 5989187, | Mar 29 1996 | Medical Priority Consultants, Inc. | Method and system for giving remote emergency medical counseling for childbirth patients |
| 6004266, | Mar 29 1996 | Method and system for the heart problem protocol of an emergency medical dispatch system | |
| 6010451, | Mar 29 1996 | Method and system for giving remote emergency medical counsel to choking patients | |
| 6053864, | Mar 29 1996 | Method and system for giving remote emergency medical counsel to arrest patients | |
| 6076065, | Mar 29 1996 | Method and system for the pregnancy condition protocol of an emergency medical dispatch system | |
| 6078894, | Mar 28 1997 | Method and system for evaluating the performance of emergency medical dispatchers | |
| 6106459, | Mar 29 1996 | Method and system for the entry protocol of an emergency medical dispatch system | |
| 20030028536, |
| Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
| Apr 12 2002 | SAALSAA, RICHARD | MEDICAL PRIORITY CONSULTANTS, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 012825 | /0541 | |
| Apr 16 2002 | Medical Priority Consultants, Inc. | (assignment on the face of the patent) | / |
| Date | Maintenance Fee Events |
| Jan 11 2010 | M2551: Payment of Maintenance Fee, 4th Yr, Small Entity. |
| Oct 30 2013 | M2552: Payment of Maintenance Fee, 8th Yr, Small Entity. |
| Jan 04 2018 | M2553: Payment of Maintenance Fee, 12th Yr, Small Entity. |
| Date | Maintenance Schedule |
| Sep 12 2009 | 4 years fee payment window open |
| Mar 12 2010 | 6 months grace period start (w surcharge) |
| Sep 12 2010 | patent expiry (for year 4) |
| Sep 12 2012 | 2 years to revive unintentionally abandoned end. (for year 4) |
| Sep 12 2013 | 8 years fee payment window open |
| Mar 12 2014 | 6 months grace period start (w surcharge) |
| Sep 12 2014 | patent expiry (for year 8) |
| Sep 12 2016 | 2 years to revive unintentionally abandoned end. (for year 8) |
| Sep 12 2017 | 12 years fee payment window open |
| Mar 12 2018 | 6 months grace period start (w surcharge) |
| Sep 12 2018 | patent expiry (for year 12) |
| Sep 12 2020 | 2 years to revive unintentionally abandoned end. (for year 12) |