System and method for distributing meaningful clinical alerts

• US 9,356,888 B2
• Filed: 12/21/2011
• Issued: 05/31/2016
• Est. Priority Date: 01/05/2011
• Status: Active Grant

• Current Assignee: Koninklijke Philips Electronics N.V. (Koninklijke Philips N.V.)
• Original Assignee: Koninklijke Philips N.V.
• Inventors: Gross, Brian David, Lagor, Charles, Weiss, David Warren, Pattillo, Monroe Wyatt, Porterfield, Robert Duane, Gosse, Redvers Curtis
• Primary Examiner(s): Sall, El Hadji
• Application Number:
  US13/977,019
• Publication Number:
  US 20130275539A1
• Time in Patent Office: 1,623 Days
• Field of Search: 709/206, 709/226, 709/239, 709/200
• US Class Current: 1/1
• CPC Class Codes: G16H 40/20 for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
• CPC Class Codes: H04L 12/1895 for short real-time information, e.g. alarms, notifications, alerts, updates
• CPC Class Codes: H04L 51/00 User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
• CPC Class Codes: H04L 51/214 using selective forwarding
• CPC Class Codes: H04L 51/216 Handling conversation history, e.g. grouping of messages in sessions or threads
• CPC Class Codes: H04L 51/234 for tracking messages

Abstract

A messaging system (100) for routing clinical messages includes an event handler and a standardized protocol (105). The event handler (106) receives one or more inbound messages from one or more event sources (102). The event sources (102) include one or more worklist items. The event handler (106) further stores the worklist items in an event database (198) and generates and communicates outbound messages for one or more worklist items in the event database (198) that need to be acted upon, as determined by one or more rules. The standardized protocol (105) is used to represent the inbound messages and the outbound messages.

Claims

1. A messaging system for routing clinical messages, said messaging system comprising:

an event handler comprising;

a memory with executable instructions stored thereon; and

a processor configured to access said memory to execute said instructions and to;

receive one or more inbound messages, including one or more worklist items, from one or more event sources;

store the worklist items in an event database; and

,

generate and communicate outbound messages for one or more worklist items in the event database that need to be acted upon, as determined by one or more rules; and

a standardized protocol to represent the inbound messages and the outbound messages;

wherein the event handler verifies and/or modifies the worklist items of the inbound messages using one or more rules, wherein the rules are based on one or more of hospital policies, target settings, properties of the inbound messages, on-call status, worklists, and workflows.

2. The messaging system according to claim 1, wherein the event handler determines the worklist items that need to be acted upon using one or more rules, wherein the rules include one or more rules based on worklists implicit in the event database and/or workflows.

3. The messaging system according to claim 1, wherein the event handler updates and/or deletes worklist items in the event database for which outbound messages were generated and communicated.

4. The messaging system according to claim 1, wherein the inbound messages include properties specifying when corresponding outbound messages are to be sent.

5. The messaging system according to claim 1, wherein the event handler is configured to:

receive a worklist item for a location, device, or patient from the inbound messages, wherein the location, device, or patient includes an escalation sequence of escalation levels, each escalation level including a target;

determine whether the worklist item is to be escalated using the rules;

in response to determining the worklist item is to be escalated, identify a next escalation level of the location, device, or patient, the next escalation level including only target(s) not already servicing higher and/or equal priority worklist items; and

,

generate and communicate an outbound message for the worklist item to the identified target.

6. The messaging system according to claim 5, wherein the next escalation level is identified by stepping through escalation levels of the escalation sequence until an escalation level including a target not already servicing higher and/or equal priority worklist items is found.

7. A method of routing clinical messages, said method performed by one or more processors preprogrammed to perform said method, said method comprising:

receiving one or more inbound messages in a standardized protocol from one or more event sources, said inbound messages including one or more worklist items;

storing the worklist items in an event database;

generating and communicating outbound messages in the standardized protocol for one or more worklist items in the event database that need to be acted upon, as determined by one or more rules;

receiving a worklist item for a location, device, or patient from the inbound messages, wherein the location, device, or patient includes an escalation sequence of escalation levels, each escalation level including a target;

determining whether the worklist item is to be escalated using the rules;

in response to determining the worklist item is to be escalated, identifying a next escalation level of the location, device, or patient, the next escalation level including only target(s) not already servicing higher and/or equal priority worklist items; and

generating and communicating an outbound message for the worklist item to the identified target.

8. The method according to claim 7, further including:

verifying and/or modifying the worklist items of the inbound messages using one or more rules, wherein the rules are based on one or more of hospital policies, target settings, properties of the inbound messages, on-call status, worklists, and workflows.

9. The method according to claim 7, wherein the generation of the outbound messages use one or more rules based on one or more of hospital policies, target settings, properties of the inbound messages, on-call status, worklists, and workflows.

10. The method according to claim 7, wherein the identifying includes:

stepping through escalation levels of the escalation sequence until an escalation level including a target not already servicing higher and/or equal priority worklist items is found.

11. A computer readable medium carrying software which controls one or more processors to perform the method according to claim 8.

12. A method of self-describing and communicating event information to an event handler, comprising one or more processors, said method performed by one or more processors preprogrammed to perform the method, said method comprising:

receiving event information including a notice of an event and/or a user response to the notice of an event;

generating a message using a standardized protocol, wherein the message includes the event information and one or more worklist items, represented using one or more standardized message properties, wherein the worklist items specify to whom the message is directed and how the message should be routed by the event handler; and

,

communicating the message to an event handler;

wherein the event handler verifies and/or modifies the worklist items of the inbound messages using one or more rules, wherein the rules are based on one or more of hospital policies, target settings, properties of the inbound messages, on-call status, worklists, and workflows.

13. The method according to claim 12, wherein each of the worklist items specify one or more targets for all or a subset of the event information.

14. The method according to claim 12, wherein the message includes business logic for how all or a subset of the event information should be routed.

15. The method according to claim 12, further including:

receiving second event information including a user response to the notice of the event;

generating a second message using the standardized protocol, the second message including the second event information and specifying to whom the second message is directed and how the second message should be routed by the event handler; and

,

communicating the second message to the event handler.