Patent Application
20140088988
The present invention relates to computer based medical information systems, and more particularly to systems and methods for creating, managing and utilizing collaborative electronic clinical pathways for patient care.
Clinical Pathways, also known as integrated care pathways, clinical algorithms, multi-disciplinary pathways of care, pathways of care, care maps, and collaborative care pathways are one of the main tools used to manage the quality in healthcare concerning the standardization of care processes. Conventionally, Clinical Pathways reduce the variability in clinical practice and improve outcomes; pathways promote organized and efficient patient care based on the evidence-based practice; and optimize outcomes in the acute care and homecare settings. Clinical Pathways are structured, multi-disciplinary plans of care designed to support the implementation of clinical guidelines and protocols. They are designed to support clinical management, clinical and non-clinical resource management, clinical audit and also financial management. They provide detailed guidance for each stage in the management of a patient, treatments, interventions with a specific condition over a given time period, and include progress and outcomes details.
Conventional Clinical Pathways aim to improve, in particular, the continuity and co-ordination of care across different disciplines and sectors and may be viewed as algorithms because they offer a flow chart format of the decisions to be made and the care to be provided for a given patient or patient group for a given condition in a step-wise sequence.
Clinical Pathways have four main components: a timeline, the categories of care or activities and their interventions, intermediate and long term outcome criteria, and the variance record (to allow deviations to be documented and analyzed). Conventional Clinical Pathways support the introduction of evidence-based medicine and use of clinical guidelines, clinical effectiveness, risk management and clinical audit, improves multidisciplinary communication, teamwork and care planning, provide explicit and well-defined standards for care, the introduction of evidence-based medicine and use of clinical guidelines, clinical effectiveness, risk management and clinical audit, continuity and co-ordination of care across different clinical disciplines and sectors, reduce variations in patient care, improve and even reduce patient documentation, disseminate accepted standards of care; provide a baseline for future initiatives; help reduce risk; and help reduce costs by shortening hospital stays.
Conventional Clinical Pathways may not be readily accessible, appear to discourage personalized care; are typically not prescriptive; may not respond well to unexpected changes in a patient's condition; are best suited for standard conditions rather than unusual or unpredictable ones; may not be tied to clinical outcomes; may take time to be accepted in the workplace; and need to ensure variance and outcomes are properly recorded, audited and acted upon. There is a need for a web-based graphical user interface (GUI) platform for medical professionals to collaborate in building decision making pathways or algorithms, which interacts with Electronic Medical Records (EMR) systems, supports the association of information used to support each decision or step and support for dynamically updating standard clinical pathways to support unusual or unpredictable conditions.
The invention provides a web based, collaborative clinical pathway platform (“Platform”) for creating, building and maintaining dynamic or flexible clinical pathways or algorithms.
Embodiments of the present invention may include systems and methods for finding and building clinical pathways and associating pertinent evidence and content collaboratively, including the creation of underlying relational data records, in a graphical interface.
Additional features, advantages, and embodiments of the invention are set forth or apparent from consideration of the following detailed description, drawings and claims. Moreover, it is to be understood that both the foregoing summary of the invention and the following detailed description are exemplary and intended to provide further explanation without limiting the scope of the invention as claimed.
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate preferred embodiments of the invention and together with the detailed description serve to explain the principles of the invention. In the drawings:
In the following detailed description of the illustrative embodiments, reference is made to the accompanying drawings that form a part hereof. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, and it is understood that other embodiments may be utilized and that logical or structural changes may be made to the invention without departing from the spirit or scope of this disclosure. To avoid detail not necessary to enable those skilled in the art to practice the embodiments described herein, the description may omit certain information known to those skilled in the art. The following detailed description is, therefore, not to be taken in a limiting sense.
As used herein, a database may be a relational database, flat file database, relational database management system, object database management system, operational database, data warehouse, hyper media database, post-relational database, hybrid database models, RDF database, key value database, XML database, XML store, text file, flat file or other type of database.
As used herein, a workflow broadly refers to a path and/or order of steps in which the Collaborative Clinical Pathway platform may perform a task or a step. The order or number of steps may vary in different embodiments.
As used herein, a computer shall include without limitation desktop computers, notebook computers, netbook computers, personal digital assistants (PDAs), mobile phones, servers, handheld computers, cellular phones, and similar devices, including without limitation web enabled devices.
In some embodiments, the Collaborative Clinical Pathway platform may be implemented via one or more computers and a web browser 100. Each computer may be well known to those skilled in the art and may include a display, a central processor, a system memory, and a system bus that couples various system components including the system memory to the central processor unit. The system bus may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. The structure of system memory may be well known to those skilled in the art and may include a basic input/output system (BIOS) stored in a read only memory (ROM) and one or more program modules such as operating systems, application programs and program data stored in random access memory (RAM). The computers may also include a variety of interface units and drives for reading and writing data and a database for storing data. The computers may run an Operating System (OS). The OS may include a shell, for providing transparent user access to resources such as application programs. The OS may include a kernel, which provides essential services required by other parts of OS and application programs. The services provided by the kernel include memory management, process and task management, disk management, and I/O device management. The OS may be the Linux Operating system, Microsoft Operating system or other operating systems.
Each computer may be able to communicate with another computer via a network using a network interface, which is coupled to the system bus. The network may be an external network such as the Internet, or an internal network such as an Ethernet or a Virtual Private Network (VPN). The network may also include one or more of a wireless network, a wired network, the Internet, a PSTN, a private network, or any other communication network. The computers that implement the Platform may be implemented on a variety of hardware platforms or implemented in a variety of software environments.
Applications running on or accessing these computers may include a browser 100, a rules engine, a workflow application or other application required by the Platform. A browser 100 may include program modules and instructions for enabling a World Wide Web (WWW) client to send and receive network messages to the Internet. The browser 100 may use well known protocols, such as Hypertext Transfer Protocol (HTTP) messaging to enable communication with another computer.
Embodiments of the present invention provide an improved Platform for clinicians and others to collaborate in the building of decision-making algorithms or creation, use or management of collaborative clinical pathways. In some alternatives, the Platform may provide users with the ability to use “Drag and Drop” techniques as illustrated in
The Platform may include components for the creation and consumption of graphical pathways with underlying databases. The creation and discovery of pathways may occur in a centralized or decentralized, web-based platform and database. Pathways may be developed through a graphical, drag-and-drop interface, allowing the user to see a visual representation of the underlying relational data records. For example, a user may add one or more graphical nodes to a clinical pathway by dragging and dropping a new graphical node from a toolbox within the Platform into a designated target area. In some alternatives, the user may be able to create a relational data record between nodes by dragging and dropping a new node into the target area of an existing node. The relational data record created by this action may establish a parent to child relationship between nodes, the existing node may be the parent node and the new node may be the child node. In some alternatives, a user may be able to edit textual content of a node through the Platform's GUI. The edited textual content may be stored as an object in the Platform's database. In some alternatives, the textual content for a node may be retrieved using live search technology to query a database of clinical terms and their variants, while the user is typing the textual context. In some alternatives, the textual content may include a selected variant and one or more clinical diagnosis codes. In some alternatives, the Platform may recommend appropriate textual content and/or clinical term variants to a user based on similarities in the intra node relational data in a database. For example, the Platform may compare similar nodes from one or more pathways to assist the user with recommending similar relationships for the current node that a user may edit. In some alternatives, the user may locate pertinent evidence to support the textual content. This pertinent evidence may be stored as a relational record to the textual content.
In some alternatives, the underlying relational databases may contain records associating specific nodes within pathways, establishing parent to child relationships. These intra pathway relationships may be used to process semantic search queries by users to deliver targeted and relevant search results. For example, the Platform may be able to deliver user specific pathways which contain the node to node relationship “headache+fever”. Pathway nodes may have associated content such as images, videos, external links, cited evidence, published journal articles, related guidelines from subspecialty societies or governments, user comments, institutional protocols, coding terminology (e.g., ICD-11, SNOMED, CPT), and links to additional pathways which reside in the Platform's database.
The Platform may allow for users to search for specific pathways using semantic keywords and strings and be presented with relevant and accurate search results. In some alternatives, the search results may be ranked and organized via a method of user feedback. For each observed user interaction with a given pathway search result page, the Platform may promote the position of a result the user may have interacted with during subsequent searches by other users. Over time, this implicit feedback loop may provide more accuracy in the search results. In some alternatives, the search results may be ranked and organized based on data collected from previous Platform queries, both by a specific user or by other users of the Platform. In some alternatives, the search results may be ranked and organized based on data derived from the association of the user with networks available on the Platform. In some alternatives, the search results may be ranked and organized based on data derived from the user's subscriptions to pathways in the system. In some alternatives, the search results may be organized by the previous pathways which the user has navigated in the Platform. In some alternatives, the search results may be ranked in part by data collected from usage data by all Platform users, such as the number of times that a pathway may have been accessed by the Platform users; time the Platform users may have spent browsing a particular pathway; the number of Platform users that may be subscribed to a pathway; and the number of times the Platform users may have copied or personalized a pathway. In some alternatives, the search results may be ranked in part by explicit positive or negative user ratings. In some alternatives, the search results may be ranked by a sentiment analysis of user submitted comments. In some alternatives, the search results may be ranked in part by the number of time a pathway has been referenced by other pathways. In some alternatives, the search results may be ranked in part by the internal rankings of pathway contributors. The pathway contributors may be ranked by metrics, such as the number of pathways published on the Platform; the number of subscribers to those pathways; and the number of times a given contributor's pathway has been copied within the Platform. In some alternatives, the search results may be ranked in part by the number of nodes contained in a pathway. Pathways with a higher number of nodes, with a log based growth rate, in some cases may be ranked higher. In some alternatives, the search results may be ranked in part by an analysis of similarities between individual users. Similar users may be grouped based on explicit and implicit signals. Search results may be served on an individual basis according to the broader group's desires. In some alternatives, the search results may be ranked in part by historical user usage data from historical versions of pathways. As a pathway has changed over time, usage data may vary and may therefore provide insight as to how relevant a particular pathway may be at certain points in time (e.g., a pathway that may have been extremely popular or one that may have become extremely popular may be more or less relevant at present).
The Platform may be engineered to deliver search results that collect and leverage data from a number of sources, both implicit and explicit, to deliver hyper accurate and relevant pathways. For example, a user may submit the following query to the platform “child+headache+fever” and the Platform may return results that contain one or all of the terms in the query. In some alternatives, a user or third-party application or database may submit data or algorithms as a search query to the Platform. The Platform could be used to ask the user or a third party application to input additional relevant information as they actually see a patient based on existing pathways in the Platform. For example, a physician may enter “suspected pulmonary embolism” into a query field available on the Platform. Using data from a clinical pathway in the Platform as illustrated in
The Platform may allow for users to see the variance between similar pathways in a visual manner as well as the ability for users to see the evolution of a particular pathway's development over time in a visual manner. For example, individual nodes inside of pathways may have different background colors, which may be representative of node types (e.g., procedure, diagnostic test, diagnosis etc.) or different shapes (e.g., square, circle, triangle) to visualize node types (e.g., procedure, diagnostic test, diagnosis etc.). Node colors and shapes may be selected by the user or determined based on analysis of the node's content by the Platform. The Platform may determine the colors and shapes of individual nodes based on the underlying data associated with each particular node. This underlying data may be derived from ICD-11, SNOMED, and CPT codes. In some alternatives, the colors and shapes of the nodes may be used to visualize how a node in specific pathway compares with the nodes in a similar pathway. In some alternatives, the colors and shapes of the nodes may be used visualize the individual contributions by specific users to a collaboratively developed pathway (i.e., a pathway that has been edited by numerous users). In some alternatives, the colors and shapes of the nodes may be used to visualize how the nodes within a pathway have changed over time. Varying colors and shapes may show nodes that have been recently added or modified and other colors may show nodes that may not have change for a certain amount of time. For example, the user may be able to layer multiple pathways on top of each other, where similarities are distinguished in one series of shapes and/or colors and differences are displayed in other shapes and/or colors. One pathway may suggest a CT Angiography at a certain point in the pathway and another may suggest a D-Dimer Test. These differences in data may be visualized using colors and/or shapes. Two or more pathways may be compared by merging the pathways and using colors to highlight differences (e.g., yellow & blue) and similarities (e.g., green) between the various steps within pathways. This comparison may be used to rapidly demonstrate where two or more pathways diverge such that a clinician may identify areas where there is general consensus versus disagreement in the approach to a clinical problem.
In some alternatives, the various steps of a clinical pathway or nodes of a clinical pathway may be associated with one or more medical terminology or translated into one or more data formats for the exchange of data with other electronic clinical systems. The Platform may allow for the direct, node to node navigation through pathways.
In some embodiments of the invention, the Platform may provide users with the ability to create a community of one or more custom networks. Custom networks may include entities, such as a hospital system, a subspecialty society, clinical department, university, medical school, research entity or clinical practice group. In some alternatives, the custom networks may have their own security, permissions, users, administrators and private clinical pathways. In some alternatives, the custom networks may have publicly available pathways. In some alternatives, the custom networks may be shared by one or more entities. These networks may serve as pathway working groups, in which multiple pathways may be edited and shared with other network members. These networks may be able to be designated as private (only open to users who have been specifically invited by network administrators) or public (open to all users, system-wide). In some alternatives, the users may be able to designate privacy settings for pathways. These privacy settings may be used to control access to the pathway by other users. For example, a pathway may be published to specific networks and/or working groups and/or to specific users. If a particular user has not been granted access to a specific pathway, they may not be able to view the underlying data, relationships, and content contained in the pathway. This user may be able to request access to the restricted pathway. If the request is granted by a pathway contributor, then the user may be able to access the restricted pathway.
In some alternatives, as illustrated in
In some alternatives, the Platform may store and organize data regarding the evolution of pathways, which reside in the Platform's database. The Platform may store data items on a node by node basis, storing historical textual content, and associated items (e.g., videos, images, documents, cited evidence etc.). In some alternatives, the Platform may store usage data per pathway or per pathway version. This means that each version of a given pathway may have a specific record of how much user interaction may have occurred within each version.
In some alternatives, the user may be able to copy steps from one pathway to another pathway in the Platform. For example, when a user changes a step, adds/deletes content, etc. to a node, the same step, content, etc. may be added/deleted to the companion node(s) in the “mirror image” or “cloned” branch.
Multiple users may have privileges to edit, modify, update, and distribute certain pathways which reside in the database. In this manner, the Platform may drive collaboration by delivering updates and changes to pathways to the associated users through pathway updates. For example, a specific user may desire to work on a single pathway with multiple colleagues. To achieve this, the user may simply invite the desired colleagues using a tool provided by the Platform. The user may enter the desired colleagues' email addresses and a uniquely identifiable link would be sent to them. When the colleague clicks the link, he or she may be able to access the content by signing up for a Platform user account or log in with an existing user account. After accepting the invitation, the colleague may have access to the Platform to modify the pathway. All changes in the particular pathway may be seen by other approved contributors.
Integrating a Pathway with EMR
In some embodiments of the invention, the Platform may interface with an Electronic Medical Record (EMR) system using any conventional means. In some alternatives, the interface may be used to automate the input of data from the EMR to the Platform. In some alternatives, a user may submit query based on data from an EMR related to a patient encounter, such as demographics, past medical history, medications, lab results or other data to the Platform, which may provide results that may suggest one or more appropriate clinical pathways which are appropriate for management, ideally personalized based on a provider's institution, specialty, prior usage, known patient preferences, etc. In some embodiments of the invention, outcome data on pathway use may be obtained through the interface with the one or more EMR systems. For example, if the user would like to know if the “Dartmouth Hip Pain Pathway” has been used 400 times during the last 6 months at 12 institutions. An interaction with the EMR may provide the following outcome data, 75% of patients were managed non-operatively with an additional 25% of patients undergoing hip replacement surgery with an average cost of $26K per patient. In some alternatives, the user may be able to populate a patient's electronic medical record by clicking through a graphical pathway during the course of care.
In some embodiments of the invention, the user-generated pathways created with the Platform may be used to build a computerized decision-support system. For example, as illustrated in
Although the foregoing description is directed to the preferred embodiments of the invention, it is noted that other variations and modifications will be apparent to those skilled in the art, and may be made without departing from the spirit or scope of the invention. Moreover, features described in connection with one embodiment of the invention may be used in conjunction with other embodiments, even if not explicitly stated above.
This application claims benefit to U.S. Provisional Patent Application No. 61/697,127, filed Sep. 5, 2012, the contents of which are incorporated by reference herein in their entirety.
| Number | Date | Country | |
|---|---|---|---|
| 61697127 | Sep 2012 | US |
