Patent Application
20120310694
There are many causes of medical errors, inconsistent care, sub-optimal care and prolonged duration of care. For example, medical errors and inefficiencies may result from information overload, overcrowding/understaffing, lack of readily available specialists and the rapidly growing knowledge base in medicine. Evidence suggests that many medical errors and inefficiencies in healthcare can be avoided by standardizing clinical care through guidelines and protocols. Thus, clinical guidelines documenting a set of evidence-based recommendations for healthcare professionals on how to optimally diagnose, treat and manage patients have been developed by various medical professional organizations. Typically the recommendations by these organizations are not intended to be rigid rules, but rather are meant to be pieces of evidence to guide their users.
Efforts have been made to computerize clinical guidelines and protocols since electronic versions are preferable to paper versions given the advantages of exchanging information easily and reliably with a hospital information system. Languages that specify computer-interpretable guidelines (e.g., Asbru, EON, GLIF, New Guide, PRODIGY and PROforma) are interpreted by guideline execution engines (e.g. GLEE and Gaston) that interpret the computer-interpretable guideline languages. Conventional guideline execution engines, however, restrict clinical users to a prescribed order of events. In order to overcome this limitation, case handling or work flow management systems (e.g., FLOWER, ECHO, the Staffware Case Handler, the COSA Activity Manager) may be utilized.
Electronic guideline management systems, however, still have a number of limitations. The guidelines may be long, requiring a great deal of user navigation and making it difficult for a user to determine which tasks have been completed by other users. Additionally, the computerized guideline may not indicate which tasks should be completed together and whether a task should be completed within a certain amount of time.
A method for loading and displaying a guideline graph based on a first user input, receiving a second user input selecting a desired portion of the guideline graph and processing the second user input to load and display a sub-graph including the desired portion of the guideline graph.
A system having a user interface to enter a first and a second user input, a memory, a processor loading the guideline graph from the memory based on the first user input and a sub-graph based on the second user input, which selects a portion of the guideline graph that a user desires to view in the sub-graph and a display displaying the guideline graph and the sub-graph.
A computer-readable storage medium including a set of instructions executable by a processor. The set of instructions being operable to load and display a guideline graph based on a first user input, receive a second user input selecting a desired portion of the guideline graph and process the second user input to load and display a sub-graph including the desired portion of the guideline graph.
The exemplary embodiments may be further understood with reference to the following description and the appended drawings wherein like elements are referred to with the same reference numerals. The exemplary embodiments relate to a system and method for displaying a guideline graph of tasks associated with a particular disease. In particular, the exemplary embodiments provide a system and method for displaying sub-graphs of the disease guideline graph based on, for example, a portion of the guideline graph desired to be viewed by a user and/or a particular user type. The guideline graph and the sub-graph include nodes corresponding to tasks associated with the disease and may indicate, for example, a status of the tasks and/or a time requirement for a particular task. The sub-graphs may overlap such that a completion of a task by one user will reflect in a sub-graph for another user. It will be understood by those of skill in the art that although the exemplary embodiments describe guidelines for the management of acute stroke, the following systems and methods may be applied to guidelines for any disease. It will also be understood by those of skill in the art that the following systems and methods may be applicable outside of the medical domain to display a graphical representation of tasks based on any accepted guideline, workflow, or protocol.
As shown in
The user now selects a disease from any number of disease guideline graphs or sub-graphs stored in the memory 108 such as, for example, acute stroke, cardiac arrest, etc., in a step 230. The user may select the disease via direct election of a disease or by following a guideline graph or sub-graph for patient triage and/or differential diagnosis to help lead the user to the selection of the correct disease guideline graph or sub-graph. The disease guideline graphs and sub-graphs are a graphical representation of particular tasks associated with each disease. The tasks correspond to tasks recommended in industry-accepted guidelines, protocols and workflows. It will be understood by those of skill in the art, however, that the step 230 will only be required if the system 100 supports multiple diseases. It will also be understood by those of skill in the art that the user may also elect not to select a particular user type to view a guideline graph or sub-graph that is disease-specific only.
In a step 240, the guideline graph or sub-graph selected by the user, which is disease and/or user specific, is loaded and displayed on the display 106. The guideline graph or sub-graph is displayed, as shown in
In a step 250, the user updates a node (e.g., task) of the displayed guideline graph or sub-graph to, for example, indicate a status of the class, enter additional patient data and/or make a decision required by the task. It will be understood by those of skill in the art that the step 250 is repeated as desired by the user, until all available patient data has been entered. Visual indications may be used to indicate properties of a node such as, for example, a status of a task of a particular node and an active node. For example, a node may change color to indicate that the task has been completed. A change in color of only a portion of the node may indicate that the task has been partially completed. The active node (e.g., the node of the task currently being reviewed and/or updated) may be indicated via a bold border surrounding the node. Once the task of an active node has been completed, the following node(s) in the guideline graph or sub-graph automatically becomes the active node. It will be understood by those of skill in the art, however, that the user may also select a particular node to activate that node.
Since the system 100 may have various users whose responsibilities may overlap, guideline graphs and sub-graphs may overlap depending on selections made by various users. The various users may utilize the system 100 from different workstations on a network. To permit overlap and synchronization between guideline graphs and sub-graphs viewed on the same or different workstations, each node of the guideline graph or sub-graph includes two classes, a workflow step and a graph node. The workflow step corresponds to the task of the node such that the task is displayed in multiple guideline graphs and sub-graphs, sharing properties of the node. For example, updating a node (e.g., entering additional information, indicating a completion of the task) in one sub-graph will correspondingly change the status of the same node (i.e., task) in all other guideline graphs and sub-graphs as well. The workflow step of the node may also have an associated timer for tasks that require attention within a predetermined amount of time. For example, the guideline may require that a Head CT be conducted within 25 minutes of a patient's arrival. The timer tracks an elapsed time and/or an amount of time remaining until the predetermined amount of time expires. The graph node class is a graph-specific instantiation of the workflow step, representing graph-specific properties such as, node text, location, size, shape and color.
The displayed timer node shows both graphically and textually how much time has elapsed from the predetermined amount of time and/or the amount of time remaining until the task is due. For example, the graphical portion of the timer node may show a bar, moving in a given direction as time elapses. Separate colors may be used to show the time elapsed and the time remaining. The displayed timer nodes may also be edited. For example, the user selects the timer node to change a predetermined amount of time that a task must be completed in, change a visual and/or textual representation of the timer, etc. For guideline graphs in which a timer node is displayed, a visual and/or audible alert is generated, once the. predetermined amount of time has elapsed and the task has not been completed. In another embodiment, the visual and/or audible alert may be generated a predefined amount of time before and/or after the predetermined amount of time has expired. In addition, the alert may be generated at given intervals until a task is completed.
Visible alerts include a flashing timer node, a pop-up window showing the overdue node, etc. The timer node may flash in certain colors depending on the status of the task. For example, the timer node flashing red indicates that the task is overdue. In another embodiment, the timer node flashes green to indicate that the task needs to be repeated at given intervals. Audible alerts include beeps, rings, etc. It will be understood that any of a variety of audible and/or visible alerts may be generated by the processor 102 so long as the alerts sufficiently notify the user regarding the status of the task.
In some clinical situations, the guideline graph may be very large, requiring the user to scroll through a large portion of the guideline graph to view a desired portion of the guideline graph. In one exemplary embodiment, portions of the guideline graph that are viewable as sub-graphs are visually indicated. For example, some of the nodes of the guideline graph may be formed of a different shape, (e.g., hexagon), size, color or font type to indicate that a sub-graph is associated with that particular node of the guideline graph. It will be understood by those of skill in the art that the visual indications corresponding to the various properties of the node will be predetermined.
In the step 260, the user enters input regarding a user viewing preference via the user interface 104. The user elects to view a portion of the guideline graph, via a sub-graph, by selecting a particular node of the guideline graph, indicating the portion of the guideline graph that the user desires to view. Alternatively, the user may elect to view another sub-graph of the current guideline, or another guideline, or a sub-graph of another guideline. Thus, the user will select a, for example, hexagonally shaped node to view a sub-graph associated with the desired portion of the guideline graph, or another guideline graph, or a sub-graph of another guideline. Since user input may be entered for other reasons (e.g., to enter patient data for a particular task, or to indicate a completion of a task), a predetermined mode of input for selecting guideline graphs or sub-graphs may be stored. For example, the user may double-click on the hexagonally shaped node to view the associated sub-graph and single click on a node to open a form for entering data associated with the node. It will be understood by those of skill in the art, however, that the mode of input may be selected and determined for various types of user input, as desired. Based on the user input entered in step 260, the processor 102 loads and displays a guideline graph or sub-graph from the memory 108, in a step 270, which displays a portion of the nodes included in the guideline graph or sub-graph. The display 106 may also display the corresponding timer node for any nodes of the sub-graph that require attention within the predetermined amount of time. The displayed guideline graph or sub-graph may be either read-only, providing an overview of the tasks from that guideline graph and sub-graph, or writable, meaning that the user may update and/or edit the nodes of the sub-graph via, for example, entering additional info, changing the status of a node, etc. The guideline graph or sub-graph may be viewed in a separate window on the display 106 or may be viewed in an existing window, in a separate frame of the window.
In the step 280, the user enters additional input. The additional input may either elect a different system option or update one of the nodes of the guideline graph or sub-graph. For example, the user may elect to select a different guideline graph or sub-graph node to view a different guideline graph or sub-graph, select a different user-type, update a node to change a status of the task, enter additional patient information, make a decision, etc. Where the additional user input indicates a desire to view a different guideline graph or sub-graph, the method 200 may return to the step 240. It will be understood by those of skill in the art, however, that a variety of other user inputs and associated system responses are also possible. For example, the guideline graph and sub-graphs updated with patient information, user preferences and other user input may be stored in the memory 108 in a patient file and recalled, as desired by the user. Once the status of the currently displayed guideline graph/sub-graph has been stored in the memory 108 and the guideline graph or sub-graph has been closed, the method 200 may revert to the step 210 so that another new or existing guideline graph or sub-graph may be selected.
It will be apparent to those skilled in the art that various modifications may be made to the disclosed exemplary embodiments and methods and alternatives without departing from the spirit or the scope of the disclosure. Thus, it is intended that the present disclosure cover modifications and variations provided that they come within the scope of the appended claims and their equivalents.
It is also noted that the claims may include reference signs/numerals in accordance with PCT Rule 6.2(b). However, the present claims should not be considered to be limited to the exemplary embodiments corresponding to the reference signs/numerals.
| Filing Document | Filing Date | Country | Kind | 371c Date |
|---|---|---|---|---|
| PCT/IB2010/055241 | 11/17/2010 | WO | 00 | 5/22/2012 |
| Number | Date | Country | |
|---|---|---|---|
| 61285203 | Dec 2009 | US |
