Tracking the progress of a patient as they move from the responsibility of the emergency medical services (EMS) personnel to the doctors in the hospital is critical to improving the patient's care. Currently, most health care providers rely on pen-and-paper forms which may be later entered into a computer system to generate statistics for procedure review. While there may be medical information systems in use throughout the healthcare community, none are focused specifically on transforming patient care by decreasing the amount of time that it takes to get the patient from the care of the (EMS) personnel, or from the Hospital Emergency Department (for walk-in patients) to percutaneous interventions associated with, but not limited to, Trauma, Stroke or a Myocardial Infarction.
A specific example in which patient care has been significantly transformed is for patients experiencing a ST segment Elevation Myocardial Infarction (STEMI), more commonly known as a heart attack. This is a condition in which a plaque formation within the coronary artery has completely blocked the flow of blood to the downstream heart muscle, causing significant heart muscle damage, a loss of heart function, and often patient death. Recognizing that prompt percutaneous intervention for patients in a STEMI situation can significantly reduce the mortality and morbidity rate, the American College of Cardiology/American Heart Association (ACC/AHA) has recently reduced the recommended time to treatment guideline from 120 to 90 minutes. A multi-disciplinary strategy consisting of the adoption of a “code” alert used to mobilize and coordinate all treatment caregivers, improved regional paramedic education and a database to track the progress of a patient as they move through the emergency medical system, has shown to transform a patient's care. In an effort to reduce the elapsed time from when the patient enters the hospital Emergency Department to the time of reperfusion of the coronary artery, a time interval otherwise known as the door-to-balloon (D2B) time, a STEMI patient tracking software was developed. The STEMI data tracker software has had a significant impact on identifying and expediting the various treatment disciplines such as in-the-field or hospital electrocardiograms (EKGs), total Emergency Room time, activation of the code STEMI alert, and catherization laboratory staff arrival. After implementation of this STEMI data tracker software and a multi-disciplinary strategy at one local hospital, 96% of presented STEMI patients now meet the 90 minute treatment deadline. The STEMI Data Tracker software allows the user to enter key time parameters associated with a patient's care, from initial contact to the time of having their occluded coronary artery opened to reestablish the blood flow. These time points are used to calculate the time intervals during the patient's treatment travel. Using the software system, the time intervals may be presented both graphically as well as numerically. The cases can be analyzed in whole or in parts to allow the opportunity to see which portion of the patient's treatment travel needs to be improved in order to meet the ACC/AHA guidelines. With this system, the elapsed time from when the Emergency medical services first make contact with the patient to the time of reperfusion of the coronary artery, otherwise known as the E2B time, has also been improved such that 73% of the presented STEMI E2B times have met the 90 minute treatment deadline.
The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate various example systems, methods, and so on that illustrates various example embodiments of aspects of the invention. It will be appreciated that the illustrated element boundaries (e.g., boxes, groups of boxes, or other shapes) in the figures represent one example of the boundaries. One of ordinary skill in the art will appreciate that one element may be designed as multiple elements or that multiple elements may be designed as one element. An element shown as an internal component of another element may be implemented as an external component and vice versa. Furthermore, elements may not be drawn to scale.
The system user enters key time parameters associated with a patient's care, from their initial contact, either with the emergency medical service (EMS) or hospital emergency department if the patient walks in, to the time of having the appropriate procedure performed. These time points are used to calculate the time intervals during the patient's treatment travel. Such a system may be hosted on a dedicated computer system, or distributed over a network including the internet.
When the system is implemented as a computer program, a log on screen may appear. A case sensitive password can be used to allow access to the input form to prevent unauthorized entry into the database. The password may include text, biometric, authentication card and other known methods to restrict access to computerized systems. Individual log-ins may also be tracked along with records created or modified during a logged in session. In one example, a password or log-in may be time stamped and only work for a period of time set by an administrator. An option to set the password or login for an indefinite time period may also be available. In one embodiment, the password is stored in a separate “.dat” file different from the database file. A user may be allowed a limited number of unsuccessful log-in attempts before the program will cease to function.
An exemplary screen or form view, 100, in the system when the data entry tab, 108, is chosen, is shown in
Section, 130, permits viewing or entry of patient information. The first text box, 132, is the medical record number (MR#) or patient identifier for alpha-numeric entries. Text box, 134, is the date field and represents the date in which the emergency event occurred. When data for a new patient is being added, a message box will pop up allowing the user the option to set all dates on the screen to the entered date. If “yes” is selected, all of the date fields will be given the same entered date. If “no” is selected, then the program will just move to the next field. The fields for the patient arrival information represent the date, 136, and time, 138, that the patient arrived at the hospital. Arrival status, such as “squad” or “walk-in” are indicated at the editable, dropdown menu, 140, and represents the mode is which the patient was brought to the hospital. The choices for the box, 140, are up to the user. If the user types in an option that is not present when using the dropdown arrow, the typed in option will be saved and available for selection the next time the menu is selected. The small patient selector box, 142, allows the user to select one or more patients that is of specific interest. When more than one patient is selected, a subgroup is formed containing the selected patients. An individual patient can be cleared from the subgroup by un-checking the patient selector box, 142, or the entire group can be cleared by clicking the clear selected patients button, 126.
Another section is for the emergency medical service (EMS) information, 150. The date. 152, and time, 154, fields represent the date and time the EMS arrived at the scene of the patient. The EMS field information is represented by an editable dropdown menu, 156, which indicates which squad brought the patient to the emergency room (ED). Like menu 140, user entry may be free-field typed or selected from a prepopulated list where typed options are saved and added to the list for the next record. The field EKG box, 158, allows the user to indicate either “yes” or “no,” using the dropdown arrows, as to whether or not the patient had an EKG performed in the field prior to arrival at the hospital. Box 158 may be modified to track other medical procedures.
Section 160 on the screen is where the hospital emergency department information is entered. Boxes 162 and 164, are the date and time, respectively, for when the patient was seen by the ED doctor. Boxes 166 and 168, indicate the time and date, respectively, that the EKG was called for, and boxes 170 and 172, represent the time and date, respectively, that the EKG was completed. Calling a “code” can mean, for example, that the patient is in a STEMI situation and the medical personnel are dispatched to the catheterization laboratory (cath lab) to prepare for arrival of the patient. The catheterization laboratory is where the patient is treated and the blocked artery is cleared, for example via, balloon angioplasty. If the event happens off hours on a holiday or week-end, the response time may be increased. Section 180, specifically written for STEMI situations, represents the data for the catheterization laboratory. Boxes 182 and 184 represent the date and time, respectively that the catheterization laboratory personnel arrived. The off hours box, 186, has a drop down option that allows the user to indicate “yes” or “no” for whether or not the incident happened during off hours. Boxes, 188 and 190, are the date and time, respectively, that the patient arrived in the catheterization laboratory. Boxes, 192 and 194, indicate the date and time, respectively, that flow through the blocked artery was restored. Finally, box 196 has a drop down function that allows the user to identify personnel, such as the cardiologist that performed the balloon angioplasty.
In addition to the fields already described, potential menu options, such as commands and lookup tables, are shown along the top menu bar, 198.
An alternate view is shown in
With reference now to
Once the dates are set, a make graphs button, 230 (
Referring back to
With reference now to
Referring now to
In one embodiment, the various data collected may be manually entered by administrative personnel, for example during the intake process, or automated. For example, information may be automatically “ported” from electronic medical record entries, internal calendar/clock applications, proximity or wireless identification devices uniquely associated with treatment providers, treatment rooms, or the patient, and other automated systems.
Continuing with reference to
After a period of time, the method may execute a statistical analysis algorithm to analyze treatment times for similar treatments over a plurality of treatment providers, 622; or for a set of medical assessment procedures, 624, for example all of a selected assessment procedure organization-wide over a particular time period; or for a set of medical treatments 626, for example all of a selected treatment during a time period.
Referring to
Referring to
Referring to
Referring to
While the systems, methods, and so on have been illustrated by describing examples, and while the examples have been described in considerable detail, it is not the intention of the applicants to restrict or in any way limit the scope of the appended claims to such detail. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the systems, methods, and so on provided herein. Additional advantages and modifications will readily appear to those skilled in the art. Therefore, the invention, in its broader aspects, is not limited to the specific details, the representative apparatus, and illustrative examples shown and described. Accordingly, departures may be made from such details without departing from the spirit or scope of the applicants' general inventive concept. Thus, this application is intended to embrace alterations, modifications, and variations that fall within the scope of the appended claims. Furthermore, the preceding description is not meant to limit the scope of the invention. Rather, the scope of the invention is to be determined by the appended claims and their equivalents.
As used herein, “connection” or “connected” means both directly, that is, without other intervening elements or components, and indirectly, that is, with another component or components arranged between the items identified or described as being connected. To the extent that the term “includes” or “including” is employed in the detailed description or the claims, it is intended to be inclusive in a manner similar to the term “comprising” as that term is interpreted when employed as a transitional word in a claim. Furthermore, to the extent that the term “or” is employed in the claims (e.g., A or B) it is intended to mean “A or B or both”. When the applicants intend to indicate “only A or B but not both” then the term “only A or B but not both” will be employed. Similarly, when the applicants intend to indicate “one and only one” of A, B, or C, the applicants will employ the phrase “one and only one”. Thus, use of the term “or” herein is the inclusive, and not the exclusive use. See, Bryan A. Garner, A Dictionary of Modern Legal Usage 624 (2d. Ed. 1995).
This application claims the benefit of U.S. Provisional Application No. 61/414,656 filed Nov. 17, 2010.
Number | Date | Country | |
---|---|---|---|
61414656 | Nov 2010 | US |