Classifications

• • G—PHYSICS
  • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
  • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
  • G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
  • G16H40/20—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
• • G—PHYSICS
  • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
  • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
  • G16H20/00—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
• • G—PHYSICS
  • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
  • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
  • G16H50/00—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics
  • G16H50/20—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics for computer-aided diagnosis, e.g. based on medical expert systems
• • G—PHYSICS
  • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
  • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
  • G16H50/00—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics
  • G16H50/50—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics for simulation or modelling of medical disorders
• • G—PHYSICS
  • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
  • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
  • G16H70/00—ICT specially adapted for the handling or processing of medical references
  • G16H70/20—ICT specially adapted for the handling or processing of medical references relating to practices or guidelines

Definitions

• the present embodiments relate generally to medical systems and more particularly, to a clinical workflow management and decision support system and method.
• various software products are commercially available, for example, hospital information systems, programs to manage workflows, statistical programs to analyze quality outcomes, and programs to develop decision support applications.
• No program is believed to exist that reconciles different applications into a single application, and in particular, one targeting a specific clinical problem.
• Studies have shown that physicians may agree poorly when interpreting the same set of clinical information.
• physicians are not always up-to-date on the most recent evidence-based disease management, in particular, if the management is only partially related to their main skills.
• nurses sometimes forget treatment steps or they may perform incorrect steps, for example, giving the wrong medication or drug to a patient.
• Figure 1 is a block diagram view of a clinical workflow management and decision support system according to an embodiment of the present disclosure
• Figure 2 is a screenshot view illustrating various regions of a graphical user interface of the clinical workflow management and decision support system and method according to an embodiment of the present disclosure
• Figure 3 is a screenshot view illustrating various regions of a graphical user interface of the clinical workflow management and decision support system and method according to another embodiment of the present disclosure.
• Figure 4 is a screenshot view illustrating various regions of a graphical user interface of the clinical workflow management and decision support system and method according to yet another embodiment of the present disclosure.
• the clinical workflow management and decision making system and method according to the embodiments of the present disclosure are designed to help clinicians adhere to a standard practice of medicine and to assist in the prevention of medical errors by providing suggestions to clinicians.
• a computer program stored on a computer readable media comprises a set of instructions for execution by a computer for reconciling clinical information from a hospital information system relevant to the management of a particular disease, such as stroke.
• stroke is used herein as an example for illustrative purposes only and that the embodiments of the present disclosure are not so limited.
• the program continuously analyzes the clinical data (i) to examine whether clinical actions adhere a predetermined protocol, (ii) to provide different healthcare professionals (e.g., physicians, nurses, CT technicians and so on) with an overview of the tasks that they have to perform, (iii) to assist healthcare professionals in making diagnostic and therapeutic decisions, and (iv) to provide healthcare professionals with reports of outcome parameters that measure the quality of their work (for example, number of stroke disabilities prevented in the past 6 months).
• healthcare professionals e.g., physicians, nurses, CT technicians and so on
• FIG. 1 is a block diagram view of a clinical workflow management and decision support system configured for use within a healthcare IT infrastructure (100) according to an embodiment of the present disclosure.
• the application (102) is interfaced with the healthcare IT infrastructure (100) and coupled to various other systems.
• the various other systems can comprise, for example, a workflow/guideline management system (104), a decision support module (106), and an electronic patient record system (108).
• the workflow/guideline management system (104) provides a computer-interpretable representation of the clinical guideline to be followed and maintains the current state of the clinical course of actions.
• the decision support module (106) is configured for calculating the probabilities for a set of differential diagnoses based on the current set of evidences, corresponding to patient data.
• the decision support module (106) is also configured for calculating suggestions for diagnostic and therapeutic steps to taken based on their diagnostic value and benefit/risk ratio, respectively.
• the electronic patient record system (108) is configured to provide access to clinical data for the patient under consideration.
• the illustration of Figure 1 is representative of one embodiment, it should be noted that the clinical workflow management and decision support system can also be independent of any existing hospital information system or electronic patient record.
• a method of clinical workflow management and decision making comprises receiving clinical information from a hospital information system (100), combining and reconciling the clinical information (for example, via application (102)) for use during the management of the particular clinical problem of the patient under consideration, and providing access to the combined and reconciled clinical information via a graphical user interface that comprises a plurality of interactive display regions.
• the clinical information can include a variety of information relevant to the management of a particular clinical problem of a patient under consideration.
• Receiving clinical information includes one or more of (i) receiving clinical information from one or more source internal to the hospital information system and (ii) receiving clinical information from one or more source external to the hospital information system.
• receiving from a source internal to the hospital information system 100 can include receiving clinical information from one or more of (a) a workflow/guideline management system (104), (b) a decision support module (106), (c) an electronic patient record system (108), and (d) a system user terminal (110) coupled to the hospital information system.
• the system user terminal (110) can include for example, a tablet PC or other suitable electronic device having a display (112) and an input (114).
• the system user terminal can comprise one or more of a computer, a personal digital assistant, a cellular telephone, a mobile communications device, or similar device, such as an electronic device wherein the display also serves as an input device.
• receiving from a source external to the hospital information system (100) can include, for example, receiving clinical information from a remote device (116), wherein the remote device can be configured for being suitably coupled to the hospital information system and for communicating clinical information to the hospital information system.
• a remote device (116) can comprise, for example, one or more of a computer, a personal digital assistant, a cellular telephone, a mobile communications device, or similar device.
• the combining and reconciling comprises repeatedly analyzing the clinical information for: (a) determining an overview of clinical actions as a function of the clinical information, (b) examining whether clinical actions adhere to a predetermined protocol, and (c) determining suggested next step information suitable for use in assisting with diagnostic and therapeutic decisions to be made by one or more healthcare providers in conjunction with treatment of the particular clinical problem.
• the clinical actions can comprise, for example, one or more of the following: (a) clinical actions performed, (b) clinical actions currently being performed, and (c) clinical actions yet to be performed.
• the one or more healthcare providers include at least one selected from the group consisting of a doctor, nurse, healthcare professional, and healthcare assistant.
• the predetermined protocol includes (i) one or more ideal clinical actions and (ii) timing for an occurrence of the one or more ideal clinical actions as a function of the clinical information and the particular clinical problem.
• the predetermined protocol comprises an evidence based protocol.
• repeatedly analyzing the clinical information can include continuously analyzing the clinical information throughout at least a critical portion of treatment of the particular clinical problem. Description of the GUI
• GUI graphical user interface
• the graphical user interface includes a plurality of interactive display regions, as will be discussed below.
• Figure 2 is a screenshot view (200) illustrating the various regions of the graphical user interface of the clinical workflow management and decision support system and method according to one embodiment of the present disclosure.
• Figure 2 illustrates the GUI of the combining and reconciling of clinical information application as applied in the management of stroke.
• the graphical user interface (200) is subdivided in various sections comprising: a high-level overview row (1) for displaying the most important patient data; a clinical findings window (2); a differential diagnosis window (3); a protocol and time map window (4); a suggested next step window (5); and an explanation window (26) as is shown in Figure 4.
• the graphical user interface (200) comprises a plurality of interactive display regions.
• the interactive display regions include a high- level patient data overview region (1), a clinical findings region (2), a differential diagnosis region (3), a protocol and time map region (4), and a suggested next step region (5).
• the top row (1) condenses the most important information about the patient under consideration at a glance: the name of the patient, his/her gender, birthday, and current location.
• the high-level patient data overview region (1) is configured for providing important information about the patient under consideration.
• the important information includes, for example, the patient's name, gender, information from which the patient's age can be discerned, and the patient's current physical location.
• the high-level patient data overview region is further configured for providing a graphical bar representation (6) of a time since onset of an event giving rise to the particular clinical problem of the patient under consideration. "Time since onset"- Bar
• the "Time since onset" bar (6) is of major importance for diseases that are characterized by a narrow time window between the onset of the symptoms and the start of the treatment. It provides a high-level overview of the time passed since symptom onset and of the progress within the protocol.
• the entire bar (7) represents the full time window (e.g. 3 hours in the case of stroke).
• a portion of the bar indicated by reference numeral (8) can be displayed as a colored fraction that represents the time already gone since symptom onset. As shown for illustration purposes only, the time since onset in this example is 1 : 10 hours.
• the combining and reconciling of clinical information application (102) maintains a model of a normative workflow in terms of the medical actions to be performed and the time needed for those steps. It also maintains a model of the actual course of actions.
• the application is, thus, able to compare the actual course of actions with the normative workflow and can determine whether or not there is a delay.
• a triangle (9) indicates the nominal position of the current step according to an ideal workflow. In this scenario, it is assumed that there is a delay, so the current step is placed before the actual time, thereby indicating that it ideally should have happened already 10 minutes before.
• there is an additional exclamation mark (10) and the color of the bar (8) can be changed, for example, to the color orange.
• the clinical findings window or region (2) is configured for providing a log of clinical findings, events, and actions pertinent to the particular clinical problem.
• the clinical findings, events, and actions are based upon the clinical information.
• each row of the log of clinical findings, events, and actions provides an indication of a date and time, a description, results, and an identification of a party that performed a corresponding one of the clinical findings, events, and actions.
• entries within the log of clinical findings, events, and actions can be internally tagged by definable categories. Tagging by definable categories enables filtering of the entries using a corresponding tab for a desired one of the categories.
• the definable categories can include one or more of history, physical, medical, laboratory, images, ECGs, orders, or other suitable categories according to the requirements of the particular clinical application.
• the top left window (2) in Figure 2 comprises the log of clinical findings, events, and actions that have taken place.
• the data displayed may be retrieved from a hospital information system or directly entered by the user into the application.
• Each row (12) indicates the date/time of the clinical action, a detailed description of the action and its results, and the user performing the action.
• the individual entries are internally tagged by definable categories (for example, History, Phys, Med, Lab, Images, ECGs, Orders, etc.), so it is possible to either view them all using the "View all" tab (13) or to filter them using the corresponding tabs (14) for the individual categories.
• the differential diagnosis window or region (3) is configured for providing a representation of probabilities for one or more differential diagnoses as a function of currently available clinical information.
• the differential diagnosis region lists possible diagnoses vertically, wherein each diagnosis is identified by its name and a bar having a length representative of a current probability of the corresponding diagnosis.
• a diagnosis may be structured hierarchically into a set of sub- diagnoses. In such an instance, the diagnosis with the set of sub-diagnoses can be graphically accounted for by one of expanding or collapsing a diagnosis in a tree -view like manner.
• the application (102) is coupled to the decision support module (106) that can calculate the probabilities for a set of differential diagnoses, given the currently available set of evidences (i.e., clinical findings).
• the decision support module (106) is based on a Bayesian network model that captures the causal relationships between evidences (i.e., results of clinical tests) and various stroke types, stroke mimics and a number of underlying pathologies.
• the differential diagnosis window (3) lists all possible diagnoses vertically. Each possible diagnosis is indicated by its name and a bar representing its current probability (16). A diagnosis may be structured hierarchically into a set of sub-diagnoses. This is graphically accounted for by the possibility to expand and collapse a diagnosis in a tree- view like manner (17).
• the application (102) queries the decision support module (106) in order to update the probabilities for the various differential diagnoses. This results in a change of the corresponding probability bars in the differential diagnosis window (3).
• the protocol and time map window or region (4) is configured for providing a graphical representation of a clinical workflow representative of the predetermined protocol, wherein the clinical workflow has been reconciled as a function of the overview of clinical actions.
• the protocol and time map region is further configured for providing a graphical representation of a clinical workflow time map.
• the clinical workflow time map includes, for example, a correlation between a progression of the clinical workflow with (a) a time that has elapsed from a symptom onset of the particular clinical problem and (b) a time that is remaining within a period of time for treatment of the particular clinical problem.
• the protocol and time map region highlights an adherence to time constraints of the clinical workflow by horizontally aligning one or more individual steps of the clinical workflow with a corresponding time on the time map.
• the time map is configured to begin with a time corresponding to the symptom onset.
• the protocol and time map region also provides visualization, in connection with the time map, of a deviation of a current step from its ideal timing in the clinical workflow.
• window (4) the information shown in window (4) is retrieved by the application (102) from the connected workflow or guideline management system (104).
• the window (4) displays the ideal clinical workflow and the actual steps that have been completed.
• the following graphical shapes connected by arcs are used to distinguish different types of steps:
• Parts of the map can be inflated into a single shape to save screen space. This is indicated by using a dashed line (e.g. in the step "EMS Delivery” that actually comprises several steps) (22).
• the protocol map further uses different colors for steps that have already been completed (e.g., blue), are currently active (e.g., yellow) and are not yet performed (e.g., white).
• one element is to correlate the progression within the clinical workflow with the time that has passed by or elapsed since symptom onset and the time that is left until the end of the treatment window, respectively.
• the individual steps are aligned horizontally with a time line (23) that starts with the symptom onset.
• the deviation of the current step from its timing in an ideal workflow is visualized in the timeline, similarly, as described above with respect to the "Time since onset" bar (6) of window (1).
• the time bars (6) and (23) are substantially the same or identical.
• the application (102) can also calculate the estimated time needed for the remaining steps to be done. To do this, it takes into account information about the typical duration of a step and the current availability of medical staff and resources. These durations may be specified in terms of time ranges, so it is possible to calculate a best case, worst case, and average case estimation. Depending on whether the remaining time until a certain target (e.g. the end of a time window for the thrombolysis therapy) is less than the time required for the remaining steps, the application (102) issues a warning, combined with the suggestion to put certain steps on a fast track (e.g. to prioritize the CT scan for this patient) or even to bypass certain steps. "Suggested next steps" window
• the suggested next step window or region (5) is configured for providing the suggested next step information having been determined to assist with diagnostic and therapeutic decisions to be made by one or more healthcare providers.
• the suggested next step information is based upon (or a function of) currently available clinical information.
• the suggested next step information can comprise (a) a suggested next action derived from a current state of execution of the clinical workflow and/or (b) a suggested next action resulting from a query to a decision support module in connection with a differential diagnosis of the differential diagnosis region.
• the query is configured for finding one or more suitable diagnostic steps to discriminate between multiple differential diagnoses.
• the suggested next step information can be presented in one or more rows.
• the one or more rows are characterized by a description of an action of a corresponding next step, identification of a party responsible for performing the action of the corresponding next step, and a check mark box. The occurrence of a check mark within the check mark box indicates that the corresponding next step has been completed.
• the suggested next step information can further include an optional button that, in response to being selected, executes a corresponding action of the suggested next step automatically.
• the suggested next step window (5) shows a list of steps suggested by the system. The suggestions are on the one hand derived from the current state of the guideline execution. On the other hand, the physician may query the decision support module 106 in the "Differential diagnosis" window (3) to find the best diagnostic steps to discriminate between multiple differential diagnoses. The result of such a query can also listed in the "Suggested next steps" window.
• Each step (24) in the suggested next steps window (5) is characterized by a short description, the actor responsible for performing the action, and a check mark, that indicates whether the step has been completed.
• a check mark that indicates whether the step has been completed.
• "Explanation" window
• the graphical user interface further comprises an explanation window or region (26) shown in Figure 4.
• the explanation region is configured for providing an explanation for a given suggested next step.
• the explanation can include, for example, a description of the reasoning behind the given suggested next step derived from an underlying decision support module.
• the explanation within the explanation region can be provided in response to activation via an explain button, wherein the explain button is provided with the corresponding suggested next step information within the suggested next step region.
• the explanation window (26) a detailed description of the reasoning behind a suggested step is displayed. This information is derived from the underlying decision support module (106).
• the explanation window (26) can be activated, for example, using the "Explain" button (27) in the "Suggested next step” window (5).
• the embodiments of the present disclosure will generally help in the management of acute diseases in a complex clinical setting. This in particular holds for diseases where adherence to normative guidelines is crucial and which are characterized by complex decision paths. Prime examples are the management of patients with trauma, myocardial infarction, or stroke.
• One application for the embodiments of the present disclosure includes the area of managing acute stroke patients.
• the embodiments of the present disclosure also include computer software or a computer program product.
• the computer program product includes a computer readable media having a set of instructions executable by a computer for carrying out the methods of clinical workflow management and decision making as described and discussed herein.
• the computer readable media can include any suitable computer readable media for a given clinical treatment system application.
• the computer readable media may also include a network communication media. Examples of network communication media include, for example, an intranet, the Internet, or an extranet.
• the healthcare IT infrastructure can comprise a computer, network, or other suitable computer based system.
• a clinical workflow management and decision making system comprises an input for receiving clinical information from a hospital information system, a processor (or suitable computer system) for combining and reconciling the clinical information for use during the management of the particular clinical problem of the patient under consideration, and a graphical user interface for providing access to the combined and reconciled clinical information, wherein the graphical user interface comprises a plurality of interactive display regions.
• the clinical information includes a variety of information relevant to management of a particular clinical problem of a patient under consideration.
• the combining and reconciling comprises repeatedly analyzing the clinical information for: (a) determining an overview of clinical actions as a function of the clinical information, (b) examining whether clinical actions adhere to a predetermined protocol.
• the predetermined protocol includes (i) one or more ideal clinical actions and (ii) timing for an occurrence of the one or more ideal clinical actions as a function of the clinical information and the particular clinical problem.
• the combining and reconciling further comprises (c) determining suggested next step information suitable for use in assisting with diagnostic and therapeutic decisions to be made by one or more healthcare providers in conjunction with treatment of the particular clinical problem.
• the graphical user interface comprises a plurality of interactive display regions that include at least (i) a protocol and time map region, (ii) a clinical findings region, (iii) a differential diagnosis region, (iv) a suggested next step region, and (v) a high-level patient data overview region.
• the graphical user interface may further comprise an explanation region.
• the protocol and time map region is configured for providing a graphical representation of a clinical workflow representative of the predetermined protocol, wherein the clinical workflow has been reconciled as a function of the overview of clinical actions.
• the protocol and time map region is further configured for providing a graphical representation of a clinical workflow time map.
• the time map includes a correlation between a progression of the clinical workflow with (a) a time that has elapsed from a symptom onset of the particular clinical problem and (b) a time that is remaining within a period of time for treatment of the particular clinical problem.
• the clinical findings region is configured for providing a log of clinical findings, events, and actions pertinent to the particular clinical problem, wherein the clinical findings, events, and actions are based upon the clinical information.
• the differential diagnosis region is configured for providing a representation of probabilities for one or more differential diagnoses as a function of currently available clinical information.
• the suggested next step region is configured for providing the suggested next step information having been determined to assist with diagnostic and therapeutic decisions to be made by one or more healthcare providers.
• the high-level patient data overview region is configured for providing important information about the patient under consideration, wherein the important information includes the patient's name, gender, information from which the patient's age can be discerned, and the patient's current physical location.
• the high-level patient data overview region is further configured for providing a graphical bar representation of a time since onset of an event giving rise to the particular clinical problem of the patient under consideration.
• One or more of the embodiments may be implemented by means of hardware comprising several distinct elements, and/or by means of a suitably programmed computer.
• a device claim enumerating several means several of these means may be embodied by one and the same item of hardware.
• the mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to an advantage.

Landscapes

• Health & Medical Sciences (AREA)
• Engineering & Computer Science (AREA)
• Medical Informatics (AREA)
• Public Health (AREA)
• Epidemiology (AREA)
• Primary Health Care (AREA)
• General Health & Medical Sciences (AREA)
• Biomedical Technology (AREA)
• Databases & Information Systems (AREA)
• Pathology (AREA)
• Data Mining & Analysis (AREA)
• Business, Economics & Management (AREA)
• General Business, Economics & Management (AREA)
• Bioethics (AREA)
• Medical Treatment And Welfare Office Work (AREA)
• Management, Administration, Business Operations System, And Electronic Commerce (AREA)
• Measuring And Recording Apparatus For Diagnosis (AREA)

Priority Applications (3)

Applications Claiming Priority (4)

Publications (2)

Family

ID=38006269

Family Applications (1)

Country Status (4)

Cited By (6)

Families Citing this family (50)

Family Cites Families (20)

• 2006
  • 2006-10-30 US US12/092,099 patent/US20080235057A1/en not_active Abandoned
  • 2006-10-30 EP EP06821261.2A patent/EP1946235B1/en not_active Not-in-force
  • 2006-10-30 JP JP2008537302A patent/JP5238507B2/ja active Active
  • 2006-10-30 WO PCT/IB2006/054020 patent/WO2007052213A2/en active Application Filing

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events