System event notification

• US 10,476,921 B2
• Filed: 06/12/2013
• Issued: 11/12/2019
• Est. Priority Date: 06/12/2013
• Status: Active Grant

• Current Assignee: Carefusion 303 Incorporated (Becton, Dickinson & Co)
• Original Assignee: Carefusion 303 Incorporated (Becton, Dickinson & Co)
• Inventors: Orona, Martin, Weiler, Aron
• Primary Examiner(s): Zand, Davoud A
• Assistant Examiner(s): Sayoc, Kristoffer L S
• Application Number:
  US13/916,472
• Publication Number:
  US 20140372522A1
• Time in Patent Office: 2,344 Days
• Field of Search: 705 2, 709220, 4554563, 4554041
• CPC Class Codes: G06F 3/0482 Interaction with lists of selectable items, e.g. menus
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 50/22 Social work or social welfare, e.g. community support activities or counselling services
• CPC Class Codes: G16H 15/00 ICT specially adapted for medical reports, e.g. generation or transmission thereof
• CPC Class Codes: G16H 20/17 delivered via infusion or injection
• 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: G16H 40/63 for local operation
• CPC Class Codes: G16H 40/67 for remote operation
• CPC Class Codes: H04L 12/1859 adapted to provide push services, e.g. data channels
• CPC Class Codes: H04L 51/224 providing notification on incoming messages, e.g. pushed notifications of received messages
• CPC Class Codes: H04L 65/403 Arrangements for multi-party communication, e.g. for conferences data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

The subject matter disclosed herein provides methods for distributing notifications to a user. The method can include receiving data encapsulating notifications from a device connected to a network that provide information relating to the device'"'"'s status. The device can provide a health related treatment. The method can associate each notification with one or more notification categories relating to a function performed by the device or a location of the device. A table of users having one or more subscriptions to these notification categories can be accessed. The subscriptions can be automatically assigned to users based on the users'"'"' role. A user can be identified from the table to distribute the one or more notifications to. The user can have a subscription that matches a notification category of the received notifications, and data comprising the notifications can be distributed to the user. Related apparatus, systems, techniques, and articles are also described.

Claims

1. A method comprising:

receiving, by at least one processor via a network, data encapsulating a first notification from a medical device connected to the network, the first notification including a physiological measurement of a patient and a status of an infusion pump, the status of the infusion pump specifying that the infusion pump needs to be refilled with medication;

associating, by the at least one processor, the first notification with a first notification category, wherein the association is based on characteristics associated with the first notification, the first notification category relating to a medical function performed by the medical device and associated with a location of the medical device;

accessing, by the at least one processor, a table of one or more users including a first user, each of the one or more users having one or more subscriptions to one or more notification categories including the first notification category, the one or more subscriptions assigned to the one or more users based on a plurality of roles including a first role and a second role associated with the one or more users, and further based on locations of the one or more users;

detecting, by the at least one processor, a change in the first role associated with the first user, the first role associated with a first subscription, the first subscription excluding the first notification, the first subscription assigned to the first user based on the first role;

updating, by the at least one processor, the first subscription to a second subscription based on the first user being assigned the second role, the second subscription including the first notification including the physiological measurement of the patient;

identifying, by the at least one processor, the first user from the table of users to distribute the first notification, the first user having the second subscription that matches the first notification category;

distributing, by the at least one processor, data comprising the first notification including the physiological measurement of the patient to the first user, wherein the data comprising the first notification is populated on a notification page, the notification page customized by the first user based on designations assigned, by the first user, to a plurality of different notification categories including the first notification category, wherein the notification page for the first user comprises a plurality of notifications including the first notification associated with the first user;

verifying that the infusion pump has been refilled with fluid;

updating the status of the infusion pump; and

causing the infusion pump to pump fluid.

2. The method of claim 1, wherein the distributing comprises at least one of sending an e-mail containing the one or more notifications to the at least one user, and sending a text message containing the one or more notifications to the at least one user.

3. The method of claim 1, further comprising:

associating, by the at least one processor, the plurality of different notification categories for the at least one user with at least a high priority and a low priority, wherein the notifications page displays notifications in a notification category associated with a high priority before notifications in a notification category associated with a low priority.

4. The method of claim 1, wherein the role associated with the one or more users is based on a position or a department associated with the one or more users.

5. The method of claim 1, wherein the status of the medical device indicates whether the medical device is connected to the network.

6. The method of claim 1, wherein the status of the medical device specifies whether action is required from the at least one user.

7. The method of claim 1, further comprising:

deleting, by the at least one processor, at least one of the subscriptions assigned to the at least one user when the role associated with the at least one user changes.

8. The method of claim 1, further comprising:

receiving, by the at least one processor, a removal request for at least one of the subscriptions from the at least one user; and

deleting, by the at least one processor, the at least one subscription.

9. The method of claim 1, further comprising:

modifying, by the at least one processor, a notification in the one or more notifications before the distributing, the modifying comprising adding information to the notification indicating at least when the notification was received from the medical device.

17. The method of claim 1, wherein the one or more notification categories are further related to at least a location of the medical device.

18. The method of claim 1, wherein the medical function performed by the medical device includes a cardiopulmonary function.

19. The method of claim 1, wherein said associating the first notification with the first notification category is based at least in part on the medical functions performed by the medical device and the location of the medical device.

10. A non-transitory computer-readable medium containing instructions to cause at least one processor to perform operations comprising:

receiving, by at least one processor via a network, data encapsulating a first notification from a medical device connected to the network, the first notification including a physiological measurement of a patient and a status of an infusion pump, the status of the infusion pump specifying that the infusion pump needs to be refilled with medication;

associating, by the at least one processor, the first notification with a first notification category, wherein the association is based on characteristics associated with the first notification, the first notification category relating to a medical function performed by the medical device and associated with a location of the medical device;

accessing, by the at least one processor, a table of one or more users including a first user, each of the one or more users having one or more subscriptions to one or more notification categories including the first notification category, the one or more subscriptions assigned to the one or more users based on a plurality of roles including a first role and a second role associated with the one or more users, and further based on locations of the one or more users;

detecting, by the at least one processor, a change in the first role associated with the first user, the first role associated with a first subscription, the first subscription excluding the first notification, the first subscription assigned to the first user based on the first role;

updating, by the at least one processor, the first subscription to a second subscription based on the first user being assigned the second role, the second subscription including the first notification including the physiological measurement of the patient;

identifying, by the at least one processor, the first user from the table of users to distribute the first notification, the first user having the second subscription that matches the first notification category;

distributing, by the at least one processor, data comprising the first notification including the physiological measurement of the patient to the first user, wherein the data comprising the first notification is populated on a notification page, the notification page customized by the first user based on designations assigned, by the first user, to a plurality of different notification categories including the first notification category, wherein the notification page for the first user comprises a plurality of notifications including the first notification associated with the first user;

verifying that the infusion pump has been refilled with fluid;

updating the status of the infusion pump; and

causing the infusion pump to pump fluid.

11. The non-transitory computer-readable medium of claim 10, wherein the role associated with the one or more users is based on a position or a department associated with the one or more users.

12. The non-transitory computer-readable medium of claim 10, wherein the status of the medical device specifies whether action is required from the at least one user.

13. The non-transitory computer-readable medium of claim 10, the operations further comprising:

deleting, by the at least one processor, at least one of the subscriptions assigned to the at least one user when the role associated with the at least one user changes.

14. A system comprising:

a processor; and

a memory, wherein the processor and the memory perform operations comprising;

receiving, by at least one processor via a network, data encapsulating a first notification from a medical device connected to the network, the first notification including a physiological measurement of a patient and a status of an infusion pump, the status of the infusion pump specifying that the infusion pump needs to be refilled with medication;

associating, by the at least one processor, the first notification with a first notification category, wherein the association is based on characteristics associated with the first notification, the first notification category relating to a medical function performed by the medical device and associated with a location of the medical device;

accessing, by the at least one processor, a table of one or more users including a first user, each of the one or more users having one or more subscriptions to one or more notification categories including the first notification category, the one or more subscriptions assigned to the one or more users based on a plurality of roles including a first role and a second role associated with the one or more users, and further based on locations of the one or more users;

detecting, by the at least one processor, a change in the first role associated with the first user, the first role associated with a first subscription, the first subscription excluding the first notification, the first subscription assigned to the first user based on the first role;

updating, by the at least one processor, the first subscription to a second subscription based on the first user being assigned the second role, the second subscription including the first notification including the physiological measurement of the patient;

identifying, by the at least one processor, the first user from the table of users to distribute the first notification, the first user having the second subscription that matches the first notification category;

distributing, by the at least one processor, data comprising the first notification including the physiological measurement of the patient to the first user, wherein the data comprising the first notification is populated on a notification page, the notification page customized by the first user based on designations assigned, by the first user, to a plurality of different notification categories including the first notification category, wherein the notification page for the first user comprises a plurality of notifications including the first notification associated with the first user;

verifying that the infusion pump has been refilled with fluid;

updating the status of the infusion pump; and

causing the infusion pump to pump fluid.

15. The system of claim 14, wherein the status of the medical device specifies whether action is required from the at least one user.

16. The system of claim 14, the operations further comprising:

deleting, by the at least one processor, at least one of the subscriptions assigned to the at least one user when the role associated with the at least one user changes.