Dynamic presentation of actionable content items

Methods, systems, and computer-readable media are provided for determining and generating content items that provide patient information and content provided by, for example, a third-party content provider that is relevant to information associated with an open healthcare application. The content items are displayed in a separate display space from the healthcare application's user interface and dynamically change and update in response to changes in the information being displayed on the healthcare application's user interface. Additionally, the content items are actionable thereby enabling healthcare providers to address alerts, take actions, view supporting documentation, and the like.

BACKGROUND

A healthcare provider working within a patient healthcare application on a computing device typically desires access to additional content that helps the provider to better understand the information being presented by the application. For example, the provider may wish to access a differential diagnosis list associated with a set of patient symptoms. Traditional solutions to this problem require the provider to select, for example, the set of patient symptoms in the application. Selection of the symptoms may navigate the provider to another application where, for instance, a differential diagnosis list is presented. The provider must then close out of this application in order to return to the patient healthcare application. This navigation process disrupts the provider's train of thought and requires the provider to re-focus on the information presented by the healthcare application before proceeding.

Another problem associated with typical patient healthcare applications is the presentation of alerts or action items. Alerts, such as alerts regarding medication refills, or drug-drug interactions are often presented as pop-ups in the healthcare application and require the provider to take some type of action in order to dismiss the pop-up. The use of pop-ups to alert the provider to potential problems or action items also disrupts the provider's train of thought and requires the provider to re-focus his or her attention on the application once the pop-up is addressed and dismissed.

SUMMARY

In brief and at a high level, this disclosure describes, among other things, methods, systems, and computer-readable media for dynamically determining and presenting actionable content items that are contextually relevant to and augment information associated with an open healthcare application. The content items are presented in a non-disruptive manner such as, for example, in a sidebar that is displayed simultaneously with the application user interface. The content items dynamically flex and update in response to changes in the information currently being displayed by the healthcare application. Examples of content items may include alerts, patient-entered information, content provided by content providers, action items, and the like. Presenting dynamic and actionable content items in a sidebar to an existing application enables the provider to view and act on the content items at the provider's convenience. This stands in contrast to the traditional presentation of alerts as pop-ups or the necessity of having to open and close other applications to access needed information, both of which disrupt the provider's train of thought and can hamper patient care.

DETAILED DESCRIPTION

Embodiments of the present invention are directed to methods, systems, and computer-readable media for determining and presenting actionable content items that are contextually relevant to patient information associated with a healthcare application. The content items are generated by monitoring information associated with the healthcare application, including what information is currently being displayed by the healthcare application. Content related to the monitored information is retrieved from content providers. Additionally, information stored in association with the patient's electronic medical record (EMR) is accessed to identify patient information related to the monitored information and/or related to the content retrieved from the content providers. The patient information accessed from the EMR and the content retrieved from the content providers are presented in a non-disruptive manner as actionable content items.

The content items may include such things as alerts, patient-entered information, action items, content provided by content providers such as differential diagnosis lists, decision-support schemas, and various clinical tools, and the like. As mentioned, the content items are actionable. Interaction with a content item can initiate clinical orders or order sets, add information to the patient's EMR, address alerts, and the like. As well, interaction with a content item can affect changes to the information being presented by the healthcare application, and interaction with the information being presented by the healthcare application can affect changes to the content items. By way of example, a provider can import a content item, or portions of a content item, such as a patient-entered review-of-systems into a summary note in the healthcare application. In another example, a provider can highlight or tag information in the healthcare application and initiate the presentation of an actionable content item in the sidebar that is related to the tagged information. The actionable content item enables the provider to initiate an action related to the tagged information. The interaction between the content items and the information presented in the healthcare application helps the provider to provide improved care to his or her patients. In addition, the content items dynamically flex and update in response to new information being displayed by the healthcare application and/or in response to user actions.

An exemplary computing environment suitable for use in implementing embodiments of the present invention is described below.FIG. 1is an exemplary computing environment (e.g., medical-information computing-system environment) with which embodiments of the present invention may be implemented. The computing environment is illustrated and designated generally as reference numeral100. The computing environment100is merely an example of one suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the invention. Neither should the computing environment100be interpreted as having any dependency or requirement relating to any single component or combination of components illustrated therein.

The present invention might be operational with numerous other purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that might be suitable for use with the present invention include personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above-mentioned systems or devices, and the like.

The present invention might be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Exemplary program modules comprise routines, programs, objects, components, and data structures that perform particular tasks or implement particular abstract data types. The present invention might be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules might be located in association with local and/or remote computer storage media (e.g., memory storage devices).

With continued reference toFIG. 1, the computing environment100comprises a computing device in the form of a control server102. Exemplary components of the control server102comprise a processing unit, internal system memory, and a suitable system bus for coupling various system components, including data store104, with the control server102. The system bus might 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. Exemplary architectures comprise Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronic Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus, also known as Mezzanine bus.

The control server102might operate in a computer network106using logical connections to one or more remote computers108. Remote computers108might be located at a variety of locations in a medical or research environment, including clinical laboratories (e.g., molecular diagnostic laboratories), hospitals and other inpatient settings, veterinary environments, ambulatory settings, medical billing and financial offices, hospital administration settings, home healthcare environments, and clinicians' offices. Clinicians may comprise a treating physician or physicians; specialists such as surgeons, radiologists, cardiologists, and oncologists; emergency medical technicians; physicians' assistants; nurse practitioners; nurses; nurses' aides; pharmacists; dieticians; microbiologists; laboratory experts; laboratory technologists; genetic counselors; researchers; veterinarians; students; and the like. The remote computers108might also be physically located in nontraditional medical care environments so that the entire healthcare community might be capable of integration on the network. The remote computers108might be personal computers, servers, routers, network PCs, peer devices, other common network nodes, or the like and might comprise some or all of the elements described above in relation to the control server102. The devices can be personal digital assistants or other like devices.

Computer networks106comprise local area networks (LANs) and/or wide area networks (WANs). Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets, and the Internet. When utilized in a WAN networking environment, the control server102might comprise a modem or other means for establishing communications over the WAN, such as the Internet. In a networking environment, program modules or portions thereof might be stored in association with the control server102, the data store104, or any of the remote computers108. For example, various application programs may reside on the memory associated with any one or more of the remote computers108. It will be appreciated by those of ordinary skill in the art that the network connections shown are exemplary and other means of establishing a communications link between the computers (e.g., control server102and remote computers108) might be utilized.

In operation, an organization might enter commands and information into the control server102or convey the commands and information to the control server102via one or more of the remote computers108through input devices, such as a keyboard, a microphone (e.g., voice inputs), a touch screen, a pointing device (commonly referred to as a mouse), a trackball, or a touch pad. Other input devices comprise satellite dishes, scanners, or the like. Commands and information might also be sent directly from a remote healthcare device to the control server102. In addition to a monitor, the control server102and/or remote computers108might comprise other peripheral output devices, such as speakers and a printer.

Although many other internal components of the control server102and the remote computers108are not shown, such components and their interconnection are well known. Accordingly, additional details concerning the internal construction of the control server102and the remote computers108are not further disclosed herein.

Turning now toFIG. 2, an exemplary computing system environment200is depicted suitable for use in implementing embodiments of the present invention. The computing system environment200is merely an example of one suitable computing system environment and is not intended to suggest any limitation as to the scope of use or functionality of embodiments of the present invention. Neither should the computing system environment200be interpreted as having any dependency or requirement related to any single module/component or combination of modules/components illustrated therein.

The computing system environment200includes a content items service210, a data store212, a content provider214, and an end-user computing device216all in communication with each other view a network218. The network may include, without limitation, one or more local area networks (LANs) or wide area networks (WANs). Such networks are commonplace and, as such, will not be further described herein.

In some embodiments, one or more of the illustrated components/modules may be implemented as stand-alone applications. In other embodiments, one or more of the illustrated components/modules may be integrated directly into the operating system of the content items service210. The components/modules illustrated inFIG. 2are exemplary in nature and in number and should not be construed as limiting. Any number of components/modules may be employed to achieve the desired functionality within the scope of embodiments hereof. Further, components/modules may be located on any number of servers. By way of example only, the content items service210might reside on a server, a cluster of servers, or a computing device remote from one or more of the remaining components.

The computing system environment200is merely exemplary. While the content items service210is illustrated as a single unit, it will be appreciated that the content items service210is scalable. For example, the content items service210may in actuality include a plurality of computing devices in communication with one another. Moreover, the data store212, or portions thereof, may be included within, for instance, the content items service210as a computer-storage medium. The single unit depictions are meant for clarity, not to limit the scope of embodiments in any form.

The data store212is configured to store information for use by, for example, the content items service210and/or the end-user computing device216. The information stored in association with the data store212is configured to be searchable for one or more items of information stored in association therewith. The information stored in association with the data store212may comprise general information used by the content items service210and/or the end-user computing device216. For example, the data store212may store information concerning standards-of-care or quality initiatives promulgated by a particular healthcare facility or by standards-setting organizations. The standards-of-care or quality initiatives may be used by the content items service210to determine content items associated with, for example, particular findings or particular diagnoses. By way of illustrative example, a healthcare facility may have a standard-of-care requiring all patients diagnosed with diabetes be given diabetes patient education. Thus, a content item comprising diabetes education may be generated by the content items service210upon determining that a patient has been diagnosed with diabetes.

The data store212may also store information regarding licenses between healthcare facilities and content providers. The licenses delineate what type of content will be provided to a particular healthcare facility by the content providers. The data store212may also store information regarding providers associated with a particular healthcare facility and learned preferences associated with those providers. By way of illustrative example, learned preferences may include types of orders or actions routinely initiated by a provider, a history of the provider's interactions with content items, and the like. This information may be used to tailor the type and/or number of content items presented to the provider, the priority order in which the content items are presented, and/or the actions that are associated with the content items.

In one aspect, the data store212, or a different data store, may store EMRs of patients associated with a healthcare facility. EMRs may comprise electronic clinical documents such as images, clinical notes, orders, summaries, reports, analyses, or other types of electronic medical documentation relevant to a particular patient's condition and/or treatment. Electronic clinical documents contain various types of information relevant to the condition and/or treatment of a particular patient and can include information relating to, for example, patient identification information, images, alert history, culture results, patient-entered information, physical examinations, vital signs, past medical histories, surgical histories, family histories, histories of present illnesses, current and past medications, allergies, symptoms, past orders, completed orders, pending orders, tasks, lab results, other test results, patient encounters and/or visits, immunizations, physician comments, nurse comments, other caretaker comments, and a host of other relevant clinical information.

The content and volume of such information in the data store212are not intended to limit the scope of embodiments of the present invention in any way. Further, though illustrated as a single, independent component, the data store212may, in fact, be a plurality of storage devices, for instance, a database cluster, portions of which may reside on the content items service210, the end-user computing device216, and/or any combination thereof.

The content provider214is, in one aspect, an independent provider of healthcare-related content (e.g., a third-party content provider). Exemplary third-party content providers include, for example, ELSEVIER® CLINICALKEY™, CERNER®, ISABEL®, MEDCALC®, and UPTODATE®. Third-party content providers provide clinical decision support tools, educational information, differential diagnosis lists, clinical calculators, and the like. The content provider214may also include healthcare facilities. The healthcare facilities may publish their own content, such as standards-of-care or quality initiatives, for use by, for example, the content items service210. Although only one content provider is illustrated inFIG. 2, it is contemplated that the present invention may encompass multiple content providers.

As shown, the end-user computing device216includes a display screen217. The display screen217is configured to display information to the user of the end-user computing device216, for instance, information relevant to communications initiated by and/or received by the end-user computing device216, information associated with healthcare applications, content items generated by the content items service210, and/or the like. Embodiments are not intended to be limited to visual display but rather may also include audio presentation, combined audio/visual presentation, and the like. The end-user computing device216may be any type of display device suitable for presenting a graphical user interface. Such computing devices may include, without limitation, a computer, such as, for example, any of the remote computers108described above with reference toFIG. 1. Other types of display devices may include tablet PCs, PDAs, mobile phones, smart phones, as well as conventional display devices such as televisions. Interaction with the graphical user interface may be via a touch pad, a microphone, a pointing device, and/or gestures.

As shown inFIG. 2, the content items service210comprises a monitoring component220, an identifying component222, a determining component224, and a rendering component226. In some embodiments, one or more of the components220,222,224, and226may be implemented as stand-alone applications. In other embodiments, one or more of the components220,222,224, and226may be integrated directly into the operating system of a computing device such as the remote computer108ofFIG. 1. It will be understood that the components220,222,224, and226illustrated inFIG. 2are exemplary in nature and in number and should not be construed as limiting. Any number of components may be employed to achieve the desired functionality within the scope of embodiments hereof.

The monitoring component220is configured to monitor patient information associated with a healthcare application being executed on, for example, the end-user computing device216. The types of healthcare applications are numerous but representative examples may include documentation applications, workflow applications, ordering applications, summary pages, and the like. The content items service210is configured for use in association with any type of healthcare application. In one aspect, the patient information that is associated with the healthcare application may be customized based on the patient, the identity of the provider accessing the application and the role associated with that provider (e.g., physician versus nurse), the healthcare venue or healthcare facility associated with the patient's care (e.g., inpatient versus ambulatory), conditions associated with the patient (e.g., diabetes, hypertension, pregnancy, and the like), and by type of visit (e.g., new patient, follow-up, well-patient, admission, transfer, discharge, and the like). The monitoring component220is configured to take into account not only the patient, the provider, the provider role, the venue, patient conditions, and type of visit when monitoring information associated with the healthcare application, but also what information is currently being displayed by the healthcare application user interface and in what context the information is being presented. For example, the monitoring component220is configured to identify that a “Labs” section is currently being displayed by the application and what type of labs are being shown in this section.

The monitoring component220is further configured to monitor any updates to the information associated with the application. This may include updated information concerning the provider, the provider role, the venue, patient conditions, and type of visit. The updated information may also include changes to information currently being displayed by the healthcare application. For example, instead of healthcare application currently displaying the labs section, discharge information may currently be displayed by the application.

The monitoring component220is also configured to monitor information associated with the healthcare facility caring for the patient. For instance, the monitoring component220is configured to monitor antibiotic resistance patterns associated with the facility, medications carried by the facility's formulary, best practices implemented by the facility, and the like.

The monitoring component220is additionally configured to monitor provider interactions with the healthcare application and with content items in order to determine preferences associated with the provider. Exemplary provider interactions associated with the healthcare application may include frequently-placed orders or order sets, terminology or phrases frequently used in clinical notes, and frequently-taken actions. Exemplary provider interactions associated with content items may include dismissing certain content items, re-prioritizing content items in a certain order, types of actions selected by the provider with respect to certain content items, and the like. Provider preferences may be derived from the provider interactions and stored in association with the data store212.

The identifying component222is configured to identify and retrieve content from the content provider214that is related or contextually relevant to the information associated with the healthcare application. The content may be retrieved from the data store212, or directly from the content provider214. The identifying component222may employ, for instance, a universal application programming interface (API) to retrieve the content from the content provider214. The API may be modified and/or extended by various wrappers and translators (customized or standard) that are specific to the particular content provider. The content may include differential diagnosis lists, decision-support algorithms, healthcare facility-specific standards-of-care or quality initiatives, clinical tools such as clinical calculators, and the like.

The identifying component222is also configured to access the patient's EMR and identify patient information, including patient-entered information that is relevant to the information associated with the healthcare application and/or relevant to information retrieved from the content provider214. Examples of patient-entered information may include patient-entered questions, patient-entered responses to questions, patient-entered review-of-systems, patient-entered diet or exercise logs, patient-entered history, and the like.

The identifying component222is further configured to access the patient's EMR to identify any alerts and/or actions items related to the information associated with the healthcare application and/or the content retrieved from the content provider214. Exemplary alerts may comprise medication refill alerts, drug interaction alerts, allergy alerts, order alerts, and the like. The identifying component222is also configured to identify a level associated with the alert. For instance, some alerts may be informational and of low priority, while other alerts may be warning alerts or patient safety alerts having a higher priority.

The determining component224is configured to utilize at least the patient information identified by the identifying component222from the patient's EMR as well as the content identified and retrieved by the identifying component222from the content provider214to determine actionable content items that are contextually relevant to the information associated with the healthcare application. The actionable content items are subsequently rendered for display in a display space associated with the healthcare application user interface by the rendering component226.

Different content items may be determined by the determining component224based on the patient information from the patient's EMR as well as the content from the content provider214. For example, the determining component224may utilize patient-entered information to determine and generate a patient-entered review-of-systems content item, a patient-entered exercise or diet log content item, a patient-entered questions content item, a patient-entered response to question content item, and the like. Similarly, the determining component224may utilize patient information in the EMR to determine and generate alert content items and action content items. Content from content providers may be used by the determining component to determine and generate a differential diagnosis content item, a quality initiative content item, a decision-support content item, a clinical calculator content item, and the like. Each of the content items determined by the determining component224is related to or relevant to the information associated with the healthcare application including the information currently being displayed by the healthcare application.

The determining component224is further configured to determine actions associated with the content items where the type of action is dependent upon the type of content item and/or learned provider preferences. For example, actions associated with a medication refill content item may include “Refill” and “Dismiss.” Actions associated with a patient-entered review-of-systems content item may include “Import” and “Dismiss.” Selection of the “Import” option imports the patient-entered information, or a portion of the patient-entered information, into, for example, a document presented by the healthcare application such as a summary note. This will be explained in greater depth below. Actions associated with order content items may include “Add” or “Dismiss.” Additional actions associated with content items may include the ability to select information within the content item and be directed to supporting documentation associated with the selected information.

The determining component224is configured to prioritize content items based on, for example, relevance to information currently being displayed by the healthcare application, urgency status, and/or based on preferences associated with the provider utilizing the healthcare application. Content items that may no longer be relevant to information currently presented by the healthcare application may be presented lower in the content item list, may be partially collapsed, or may not be presented in the display space. With respect to provider preferences, if a provider consistently dismisses certain content items, these content items may be presented lower in the content item list as compared to other content items, be partially collapsed, or may not be presented in the display space.

The determining component224is additionally configured to dynamically update the content items in response to updated information associated with the healthcare application. As used throughout this disclosure, the term “dynamically” means occurring in near real time. As mentioned above, the updated information associated with the healthcare application may include changes to the provider, the provider role, the venue or healthcare facility, patient conditions, or type of visit. As well, the updated information may include changes to the information currently being displayed by the healthcare application. In response to the updated information, the determining component224may generate new content items, re-prioritize existing content items, or modify content associated with existing content items. Content items that are less relevant with respect to the updated information may be placed lower in the content item list, partially collapsed, or not be presented in the display space.

In one aspect, the rendering component226may render content items in a separate sidebar element to the left or to the right of the healthcare application user interface. In other embodiments, the content items may be presented in a separate display space positioned at the top or the bottom of the healthcare application user interface. Additionally, the content items may be presented as an overlay on existing content being presented by the application, or “in-line” to an item of information presented by the healthcare application. Any and all such variations, and any combination thereof, are contemplated as being within the scope of the invention.

Content items that are time sensitive, such as medication refills may be highlighted by the rendering component226in some manner to help draw the user's attention to the content items. Additionally, alert content items may be highlighted in different manners according to the level of the alert (e.g., informational versus warning versus patient safety). Highlighting may be accomplished by coloring the content item differently than other content items, using different font, placing the content item higher in the priority queue, making the content item appear to glow, associating an audible sound such as a beep or ping with the content item, and the like.

Turning now toFIGS. 3-8, these figures depict exemplary graphical user interfaces (GUIs) displaying exemplary content items related to information associated with a healthcare application. With respect toFIG. 3,FIG. 3depicts an exemplary GUI300that includes a healthcare application and its associated user interface314accessed by a provider312(Jan Carter M.D.) for a patient310(Charles Adams). Besides identifying the provider and provider role312and the patient310, the healthcare application314also includes information identifying the healthcare venue and the type of visit316(follow-up (ambulatory)), and conditions318associated with the patient310(hypertension, hyperlipidemia, and diabetes). As shown inFIG. 3, the healthcare application314is currently displaying information, such as lab results, for the condition of diabetes317.

The GUI300further includes a display space320. In one aspect, the display space320is presented simultaneously with the healthcare application314as a separate sidebar element. AlthoughFIG. 3depicts the display space320as a separate sidebar to the right of the healthcare application314, it is also contemplated that the display space320may be presented as a left sidebar or as a separate display space positioned at the top or the bottom of the healthcare application314. In another aspect, the display space320may be presented as an overlay to the healthcare application. With respect to this aspect, the entire display space320may be presented as an overlay on content associated with the healthcare application. Alternatively, individual content items may be presented as an overlay on content associated with the healthcare application. Further, when presented as an overlay, the display space320and/or the individual content items may be presented for a predetermined period of time before fading or disappearing. In one aspect, the display space320and/or content items may be minimized via a user action or automatically upon determining that the content item(s) is no longer relevant to information currently being presented by the healthcare application. In yet another aspect, the content items may be presented “in-line” within the healthcare application314. For example, a medication refill content item may be presented in-line with the listed medication in the healthcare application314. Any and all such variations, and any combination thereof, are contemplated as being within the scope of the invention.

The display space320includes a number of content items322,324, and326that are related to the information associated with the healthcare application314. The content item322is a differential diagnosis list provided by a third-party content provider. The differential diagnosis content item322is contextually relevant to the patient310, the lab results currently being shown by the healthcare application314, to the provider and provider role (physician)312, as well as to the diabetes condition317. The differential diagnosis content item322is displayed automatically and without human intervention which helps the provider312to maintain consistency in his or her workflow without having to navigate to a separate application to access the differential diagnosis information or be disrupted by a pop-up with the differential diagnosis information.

The content item324comprises a medication refill content item for the diabetes medication Metformin. The medication refill content item324is relevant to the patient310, the role associated with the provider312, and the diabetes condition317. For example, the medication refill content item324would not typically be displayed to a nurse since the nurse could not act on the refill order. The medication refill content item324includes a “Refill” action and a “Dismiss” action. If the provider312selects the “Refill” action, the order is automatically initiated and stored in the patient's EMR. If the provider selects the “Dismiss” action, the content item324is either dismissed from the display space320or moved lower in the priority queue.

The content item326comprises a content item for diabetes patient education. The diabetes patient education content item326is related to the patient310, the diabetes condition317, and the provider role. Diabetes patient education may be part of a healthcare facility's standard-of-care or quality initiative, and thus a diabetes education content item may be automatically generated by, for example, the content items service210ofFIG. 2upon identifying from the healthcare application314that the patient310suffers from diabetes. The diabetes patient education content item326includes the actions “Add” and “Dismiss.” By selecting the “Add” action, diabetes patient information will be added to a list of education items to be provided to the patient310. Additionally, by selecting the “Add” action, the provider312may also be able to initiate a specific order or order set related to diabetes. By selecting the “Dismiss” action, the provider312can dismiss the content item326as explained above with respect to the medication refill content item324.

FIG. 4depicts the GUI300at a point in time when the healthcare application314is displaying a new set of patient information to the provider312. Elements that are the same between the figures are indicated by like numerals. The display space320is presenting a new content item410. An indication of the differential diagnosis content item322is presented although the actual content item has been partially collapsed. The collapse may occur in response to a user action or it may occur automatically upon determining that the differential diagnosis content item322is no longer relevant to the information currently being presented by the healthcare application314. The remaining content items ofFIG. 3have either been moved down in the content item list where they can be accessed by scrolling down the display space320or they have been removed from the display space320.

The content item410comprises a patient-entered response to a question. In this case, the question requested that the patient310select the problem to be addressed by the current visit. The patient310selected the problem of high blood pressure. As seen, the content item410is related to the patient310, the provider and provider role312, the venue and type of visit316, and the information currently being displayed by the healthcare application314(e.g., medications for hypertension). Presentation of the content item410helps to ensure effective communication between the provider312and the patient310regarding the patient's care. For example, if the current visit was actually for the cholesterol problem and not for high blood pressure, presentation of the content item410in the display space320provides an opportunity for the provider312to educate the patient310about the purpose of the current visit.

FIG. 5depicts the healthcare application314displaying a discharge summary for the patient310. The display space320shown inFIG. 5includes a “Quality” tab319and a “Messages” tab321that enable the provider312to filter the content items presented in the display space320. Selection of the “Quality” tab319may restrict the content items to those related to quality of care, while selection of the “Messages” tab321may restrict the content items to patient-entered questions, nurse-entered questions, and the like. However, even though a tab may be selected, the filter associated with the tab may be overridden if it is determined that a particular content item is relevant to information being presented by the healthcare application314. Thus, a particular content item may be presented even though a filter has been set for that content item. Alternative wording for the tabs319and321is contemplated to be within the scope of the invention. The display space320may include or not include the tabs. For instance, tabs may be automatically displayed when there is greater than a predetermined number of content items. As well, additional tabs are contemplated as being within the scope of the invention. For example, additional tabs may include an “Alerts” tab, a “Patient-Entered Information” tab, and the like.

The information presented by the healthcare application314and the content items presented in the display space320are closely interrelated and interaction with one may cause changes to the other. For example, as shown inFIG. 5, the provider is able to tag information in the healthcare application314. Numeral510indicates information that has been tagged or highlighted by the user. The tagged information510is then presented as a content item514in the display space320. The content item514enables the provider312to initiate actions with respect to the tagged information510. In this example, the provider312has tagged information related to the patient's smoking history. The content item514comprises a set of orders related to smoking cessation. The orders may be based on past smoking cessation order sets submitted by the provider312and stored as provider preferences in a data store such as the data store212ofFIG. 2. The orders may also be based on standards-of-care or quality initiatives associated with the healthcare facility caring for the patient310. The actions associated with the content item514include an “Add All” action and a “Dismiss” action. The “Add All” action allows the provider312to initiate the complete order set with one click. Additional content items may also be generated based on the tagged information510. For instance, content items may be generated that enable the provider312to incorporate the tagged information510into a problem list, or to add smoking cessation education to the patient's education list.

Content items may also be presented upon determining that, for example, a document associated with the healthcare application314includes new information that has not yet been stored in discrete, structure fields in the patient's EMR. For example, the discharge summary includes item512where the provider312documented that the patient310has a sedentary lifestyle. Upon determining that this information is not part of the patient's EMR, a content item516is generated and displayed in the display space320. The content item516includes the action “Add” that enables the provider312to add “Lack of Physical Exercise” to the patient's problem list stored in association with the patient's EMR. Alternatively, the provider312can choose to dismiss the content item516.

Turning toFIG. 6, the healthcare application314is continuing to present the discharge summary. However, a new set of content items is being presented in the display space320. Content item610comprises a patient-entered content item by which the provider312can access the patient's diet and exercise log611. Ready access to this type information enables the provider312to prepare a complete discharge summary. Content item614comprises a patient-entered review-of-systems. In this case, only positive findings are shown. The provider312can interact with the content item614and select, for example, the patient's indication that he is having “Difficulty Swallowing”615. Actions associated with the content item614include “Import” and “Dismiss.” Upon the provider's selection of the “Import” action, the finding615is imported into, for example, the healthcare application314. This is shown inFIG. 7.FIG. 7depicts the healthcare application314displaying a Review-of-Systems screen. The finding615“Difficulty Swallowing” has been imported into the review-of-systems and re-labeled by its correct medical term “Dysphagia”710. The translation of the term “Difficulty Swallowing” to the term “Dysphagia” may be carried out by a third-party nomenclature service.

FIG. 8depicts the healthcare application314displaying, among other things, a charges workspace where the provider312can indicate the level of service associated with the patient visit as indicated by numeral810. The corresponding CPT code is shown at area812. The display space320presents content item814related to the charge summary. The content item814informs the provider312that there is not enough documentation to support the indicated level of service810. The content item814may be generated upon accessing the patient's EMR and determining that needed documentation is lacking. Actions associated with the content item814include “Change” and “Dismiss.” Selection of the “Change” action enables the provider312to change the level of service associated with the visit.

The display space320inFIG. 8also is presenting content item816. The content item816can be considered a “clean-up” content item in that it prompts the provider312to complete a one or more items prior to closing out of the healthcare application314. The content item816may be generated upon determining that, for example, a note has not yet been documented for the current patient visit. The content item816includes a “Create Note” action. Selection of this action directs the provider312to the appropriate section of the healthcare application314so that the provider312can prepare the note. Other clean-up content items may include alert reminder content items, charge documentation content items, electronic signature reminder content items, and the like.

Turning now toFIG. 9,FIG. 9depicts a flow diagram of an exemplary method of dynamically determining content items to be displayed in a display space that is presented in conjunction with a healthcare application. At a step910, information associated with the healthcare application is monitored by a monitoring component such as the monitoring component220ofFIG. 2. Examples of monitored information include patient name, user actions, patient conditions, provider name, provider role, venue or healthcare facility caring for the patient, type of visit, and what information is currently being displayed to the provider by the healthcare application. Monitoring may also include detecting any changes or updates to the information associated with the healthcare application such as, for example, a change in the information currently being displayed to the provider by the healthcare application, changes to patient conditions, provider role, type of visit, and the like.

At a step912, an identifying component, such as the identifying component222ofFIG. 2, identifies and retrieves content from content providers that is relevant to the monitored information. Content providers may include third-party content providers that are independent of the healthcare facility providing care to the patient. Content providers may also include the healthcare facility itself. Examples of content retrieved from the content providers include decision-support algorithms, condition-based practice models, quality initiatives, differential diagnosis lists, clinical tools such as clinical calculators, standards-of-care, and the like.

At a step914, the patient's EMR is accessed by the identifying component to identify patient information, including patient-entered information that is relevant to the monitored information associated with the healthcare application and/or relevant to the content retrieved from the content providers. Examples of patient information accessed from the EMR may include outstanding alerts, patient-entered questions, current diagnoses, predisposing conditions, responses to questions, exercise and/or diet logs, review-of-systems, and the like.

At a step916, a determining component such as the determining component224ofFIG. 2, utilizes the patient information identified from the patient's EMR and the content retrieved from the content providers to determine and generate content items and actions associated with the content items. Additional information may also be utilized when generating content items. For example, the determining component may access a data store such as the data store212ofFIG. 2to determine preferences associated with the provider. Provider preferences, in turn, may be used to customize the content of the content items to the particular provider, prioritize the content items in a particular order, highlight the content items in a particular way, customize the actions associated with the content items, and the like. At a step918, the determined content items are then rendered for display by, for example, a rendering component such as the rendering component226ofFIG. 2.

The generated content items are contextually relevant to the information associated with the healthcare application and are presented in a non-obtrusive manner such as in a sidebar or as an overlay to the healthcare application user interface. The content items may be actionable. For example, the provider is able to interact with the content items to address alerts, initiate orders, import information from the content items into the healthcare application, view supporting documentation, add information to the patient's EMR, navigate to different sections of the healthcare application, modify information in the healthcare application, and the like.

The content items dynamically update in response to, for example, changes in the information associated with the healthcare application such as changes to the information currently being displayed by the healthcare application as well as to changes in content provided by the content providers or to changes in the patient's medical information as stored in the patient's EMR. Content items may be updated by modifying content associated with existing content items, adding new content items, re-prioritizing content items, highlighting content items, removing content items that are no longer relevant to the healthcare application, and the like.

As seen, the present invention is directed to the presentation of dynamic, actionable content items that augment information associated with a healthcare application. The content items are presented in a non-distracting manner such as in a sidebar to the healthcare application user interface. The provider using the healthcare application can address the content items at his or her convenience without the necessity of having to stop the current workflow and navigate to different applications and/or address disruptive pop-ups.

The present invention has been described in relation to particular embodiments, which are intended in all respects to be illustrative rather than restrictive. Further, the present invention is not limited to these embodiments, but variations and modifications may be made without departing from the scope of the present invention.