# US 12,763,207 B2 · System event notification > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,763,207 B2 - Document ID: US12763207B2 - Status: Granted - Kind: B2 - Application number: 19/025,522 - Filed: 2025-01-16 - Published: 2025-05-15 - Granted: 2026-10-13 - Earliest claimed: 2013-06-12 - Assignees: CareFusion 303, Inc. - Applicants: CareFusion 303, Inc. - Inventors: Martin Orona; Aron Weiler - Web page: https://patentgrep.com/patent/US12763207B2 ## CPC - G16H 40/67: for remote operation - G06F 3/0482: Interaction with lists of selectable items, e.g. menus - G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications} - G06Q 30/02: Marketing; Price estimation or determination; Fundraising - G16H 15/00: ICT specially adapted for medical reports, e.g. generation or transmission thereof - G16H 40/20: for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms - G16H 40/63: for local operation - H04L 51/224: providing notification on incoming messages, e.g. pushed notifications of received messages - 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) - H04L 67/306: User profiles - H04L 67/55: Push-based network services - G06Q 50/22: Social work or social welfare, e.g. community support activities or counselling services - G16H 20/17: delivered via infusion or injection - H04L 9/40: Network security protocols - H04L 12/1859: {adapted to provide push services, e.g. data channels} - H04L 67/63: Routing a service request depending on the request content or context - G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## 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 ### Claim 1 A method for implementation by one or more data processors comprising: receiving, by at least one data processor via a network, data relating to a notification from an infusion pump connected to the network, the notification providing information relating to a status of the infusion pump, the infusion pump associated with providing an infusion; associating, by at least one data processor, the notification with a notification category, the notification category relating to a location of the infusion pump; identifying, by at least one data processor, at least one user from a database to distribute the at least one notification to, the at least one user having at least one subscription that matches the notification category of the notification; and providing, by at least one data processor, data comprising at least a portion of the notification to the at least one user until a function performed by the infusion pump is completed. ### Claim 2 (depends on 1) The method of claim 1, wherein the providing comprises at least one of loading at least the portion of the notification on a notifications page associated with the at least one user, sending an e-mail containing at least the portion of the notification to the at least one user; and sending a text message containing at least the portion of the notification to the at least one user. ### Claim 3 (depends on 2) The method of claim 2, further comprising: associating, by at least one data processor, the notification category for the at least one user with one of a high priority or a low priority, wherein the notifications page displays notifications associated with the high priority before notifications associated with the low priority. ### Claim 4 (depends on 1) The method of claim 1, wherein the at least one subscription is automatically assigned to the at least one user based on a role associated with the at least one user. ### Claim 5 (depends on 4) The method of claim 4, wherein the role associated with the at least one user is based on a position or a department associated with the at least one user. ### Claim 6 (depends on 1) The method of claim 1, wherein the status of the infusion pump indicates whether the infusion pump is connected to the network. ### Claim 7 (depends on 1) The method of claim 1, wherein the status of the infusion pump specifies whether action is required from the at least one user. ### Claim 8 (depends on 7) The method of claim 7, wherein the action required by the notification sent from the infusion pump indicates that the infusion pump needs to be refilled with medication. ### Claim 9 (depends on 7) The method of claim 7, wherein the action required by the notification indicates that a data set generated by an infusion data set editor application is awaiting review. ### Claim 10 (depends on 1) The method of claim 1, further comprising: automatically updating, by at least one data processor, at least one of the subscriptions of a user when a role associated the user changes. ### Claim 11 (depends on 1) The method of claim 1, further comprising: receiving, by at least one data processor, a removal request for at least one of the subscriptions from the at least one user; and deleting, by at least one data processor, the at least one subscription. ### Claim 12 (depends on 1) The method of claim 1, further comprising: modifying, by at least one data processor, the at least one notification before the providing, the modifying comprising adding information to the notification including at least when the notification was received. ### Claim 13 A non-transitory computer-readable medium containing instructions to configure a processor to perform operations comprising: receiving, by at least one data processor via a network, data relating to a notification from an infusion pump connected to the network, the notification providing information relating to a status of the infusion pump, the infusion pump associated with providing an infusion; associating, by at least one data processor, the notification with a notification category, the notification category relating to a location of the infusion pump; identifying, by at least one data processor, at least one user from a database to distribute the at least one notification to, the at least one user having at least one subscription that matches the notification category of the notification; and providing, by at least one data processor, data comprising at least a portion of the notification to the at least one user until a function performed by the infusion pump is completed. ### Claim 14 (depends on 13) The non-transitory computer-readable medium of claim 13, the operations further comprising: sending an e-mail containing at least the portion of the notification to the at least one user; and sending a text message containing at least the portion of the notification to the at least one user. ### Claim 15 (depends on 14) The non-transitory computer-readable medium of claim 14, the operations further comprising: associating, by at least one data processor, the notification category for the at least one user with one of a high priority or a low priority, wherein the notifications page displays notifications associated with the high priority before notifications associated with the low priority. ### Claim 16 (depends on 13) The non-transitory computer-readable medium of claim 13, wherein the at least one subscription is automatically assigned to the at least one user based on a role associated with the at least one user. ### Claim 17 (depends on 16) The non-transitory computer-readable medium of claim 16, wherein the role associated with the at least one user is based on a position or a department associated with the at least one user. ### Claim 18 (depends on 13) The non-transitory computer-readable medium of claim 13, wherein the status of the infusion pump indicates whether the infusion pump is connected to the network. ### Claim 19 (depends on 13) The non-transitory computer-readable medium of claim 13, wherein the status of the infusion pump specifies whether action is required from the at least one user. ### Claim 20 (depends on 13) The non-transitory computer-readable medium of claim 13, the operations further comprising: receiving, by at least one data processor, a removal request for at least one of the subscriptions from the at least one user; and deleting, by at least one data processor, the at least one subscription.