IP Library › Granted Patent US 12,646,617
Granted Patent B2
US 12,646,617 · App. 19/020,852 · Granted Jun 2, 2026

Alarm notification system

Inventors: Bilal Muhsin (San Clemente, CA); Emil Sultanov (Anaheim, CA); Stephen Quong (Huntington Beach, CA)
Assignee: Maismo Corporation
G16H40/67G16H10/60G16H50/30G16Z99/00G16H40/20
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,646,617
App. No.
19/020,852
Granted
Jun 2, 2026
Kind
B2
Abstract

An alarm notification system can enable a clinician to respond to an alarm notification received via a computing device, which may have more advanced functionality than a pager. The clinician's device can include a notification client which can respond to alarm notifications. The notification client can also provide one or more user interfaces that enable the clinician to view information about an alarm, such as information about a patient's status, physiological parameter values, trend data, audio/video of the patient, combinations of the same, or the like. Further, the notification client can provide functionality for a clinician to respond to an alarm, annotate an alarm, and/or indicate that the clinician can or cannot respond to the alarm, among other features. In addition, the clinician device can also (or instead) include an admit module that provides for automatic association of a patient to a device or location.

Claims (51)

1 . A method of managing alarm notifications at a patient monitoring computing device, the method comprising:

sending an alarm notification message to a user device associated with a user;

determining whether a first indication that the alarm notification message was received by the user device has been received from the user device; and

in response to receiving, from the user device, the first indication:

determining whether a second indication that the alarm notification message was viewed by the user at the user device has been received from the user device, wherein the second indication indicates that the user has viewed but not yet responded to the alarm notification message; and

in response to receiving, from the user device, the second indication:

determining whether a response responsive to an input that the user has declined handling an alarm has been received from the user device; and

in response to receiving, from the user device, the response responsive to the input, accelerating escalation of the alarm.

2 . The method of claim 1 further comprising:

in response to not receiving, from the user device, the first indication, accelerating escalation of the alarm.

3 . The method of claim 1 further comprising:

in response to not receiving, from the user device, the response responsive to the input:

determining whether the alarm has been cleared; and

in response to determining that the alarm has not been cleared, accelerating escalation of the alarm.

4 . The method of claim 1 further comprising:

determining whether or not an escalation condition is present based at least in part on at least one of: receipt or non-receipt of the first indication from the user device, receipt or non-receipt of the second indication from the user device, or receipt or non-receipt of the response from the user device; and

in response to determining that the escalation condition is present, automatically escalating the alarm by sending the alarm notification message to a second user device associated with a second user.

5 . The method of claim 1 , wherein the input comprises an indication that the user has marked the alarm notification message as unread.

6 . The method of claim 1 , wherein the input comprises an indication that the user is unable to respond to the alarm.

7 . The method of claim 1 , wherein the user device comprises a smartphone or other mobile device.

8 . The method of claim 1 further comprising:

sending the alarm notification message in response to receiving an alarm indication from a patient monitor.

9 . The method of claim 8 , wherein the patient monitor is configured to:

determine that physiological parameter values trigger an alarm; and

send, to the patient monitoring computing device, the alarm indication responsive to determining that the physiological parameter values trigger the alarm.

10 . A system comprising:

physical computer hardware configured to:

send an alarm notification message to a user device associated with a user;

determine whether a first indication that the alarm notification message was received by the user device has been received from the user device; and

in response to receiving, from the user device, the first indication:

determine whether a second indication that the alarm notification message was viewed by the user at the user device has been received from the user device, wherein the second indication indicates that the user has viewed but not yet responded to the alarm notification message; and

in response to receiving, from the user device, the second indication:

determine whether a response responsive to an input that the user has declined handling an alarm has been received from the user device; and

in response to receiving, from the user device, the response responsive to the input, accelerate escalation of the alarm.

11 . The system of claim 10 , wherein the physical computer hardware is further configured to:

in response to not receiving, from the user device, the first indication, accelerate escalation of the alarm.

12 . The system of claim 10 , wherein the physical computer hardware is further configured to:

in response to not receiving, from the user device, the response responsive to the input:

determine whether the alarm has been cleared; and

in response to determining that the alarm has not been cleared, accelerate escalation of the alarm.

13 . The system of claim 10 , wherein the physical computer hardware is further configured to:

determine whether or not an escalation condition is present based at least in part on at least one of: receipt or non-receipt of the first indication from the user device, receipt or non-receipt of the second indication from the user device, or receipt or non-receipt of the response from the user device; and

in response to determining that the escalation condition is present, automatically escalate the alarm by sending the alarm notification message to a second user device associated with a second user.

14 . The system of claim 10 , wherein the input comprises an indication that the user has marked the alarm notification message as unread.

15 . The system of claim 10 , wherein the input comprises an indication that the user is unable to respond to the alarm.

16 . The system of claim 10 , wherein the user device comprises a smartphone or other mobile device.

17 . The system of claim 10 , wherein the physical computer hardware is further configured to:

send the alarm notification message in response to receiving an alarm indication from a patient monitor.

18 . The system of claim 17 , wherein the patient monitor is configured to:

determine that physiological parameter values trigger an alarm; and

send, to a patient monitoring computing device of the system, the alarm indication responsive to determining that the physiological parameter values trigger the alarm.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 29, 2026
From: MUHSIN, BILAL; SULTANOV, EMIL; QUONG, STEPHEN
To: MASIMO CORPORATION
Reel/Frame 074514/0968 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 18, 2026
From: MUHSIN, BILAL; SULTANOV, EMIL; QUONG, STEPHEN
To: MASIMO CORPORATION
Reel/Frame 073826/0393 →
Continuity (7)
Continuation 18651438 · Apr 30, 2024
Continuation 18323001 · May 24, 2023
Continuation 17952793 · Sep 26, 2022
Continuation 17035382 · Sep 28, 2020
Continuation 14511972 · Oct 10, 2014
Provisional Application 61890076 · Oct 11, 2013
Related Publication 20250157645A1 · May 15, 2025
References Cited (91)
US 5752976A · Duffin et al. · 1998 [cited by applicant]
US 10169607B1 · Sheth · 2019 [cited by applicant]
US 10825568B2 · Muhsin et al. · 2020 [cited by applicant]
US 10832818B2 · Muhsin et al. · 2020 [cited by applicant]
US 11488711B2 · Muhsin et al. · 2022 [cited by applicant]
US 11699526B2 · Muhsin et al. · 2023 [cited by applicant]
US D1022729S · Forrest et al. · 2024 [cited by applicant]
US 11974833B2 · Forrest et al. · 2024 [cited by applicant]
US 11986067B2 · Al-Ali et al. · 2024 [cited by applicant]
US 11986289B2 · Dalvi et al. · 2024 [cited by applicant]
US 11986305B2 · Al-Ali et al. · 2024 [cited by applicant]
US D1031729S · Forrest et al. · 2024 [cited by applicant]
US 12004869B2 · Kiani et al. · 2024 [cited by applicant]
US 12009098B2 · Muhsin et al. · 2024 [cited by applicant]
US 12014328B2 · Wachman et al. · 2024 [cited by applicant]
US D1036293S · Al-Ali et al. · 2024 [cited by applicant]
US D1037462S · Al-Ali et al. · 2024 [cited by applicant]
US 12029844B2 · Pauley et al. · 2024 [cited by applicant]
US 12048534B2 · Vo et al. · 2024 [cited by applicant]
US 12064217B2 · Ahmed et al. · 2024 [cited by applicant]
US 12066426B1 · Lapotko et al. · 2024 [cited by applicant]
US D1041511S · Indorf et al. · 2024 [cited by applicant]
US D1042596S · DeJong et al. · 2024 [cited by applicant]
US D1042852S · Hwang · 2024 [cited by applicant]
US 12076159B2 · Belur Nagaraj et al. · 2024 [cited by applicant]
US 12082926B2 · Sharma et al. · 2024 [cited by applicant]
US D1044828S · Chandran et al. · 2024 [cited by applicant]
US D1048571S · Yu et al. · 2024 [cited by applicant]
US D1048908S · Al-Ali et al. · 2024 [cited by applicant]
US 12106752B2 · Campbell et al. · 2024 [cited by applicant]
US 12114974B2 · Al-Ali et al. · 2024 [cited by applicant]
US 12126683B2 · Koo et al. · 2024 [cited by applicant]
US 12127838B2 · Olsen et al. · 2024 [cited by applicant]
US 12128213B2 · Kiani et al. · 2024 [cited by applicant]
US 12131661B2 · Pauley et al. · 2024 [cited by applicant]
US D1050910S · Al-Ali et al. · 2024 [cited by applicant]
US 12178572B1 · Pauley et al. · 2024 [cited by applicant]
US 12178581B2 · Telfort et al. · 2024 [cited by applicant]
US 12178852B2 · Kiani et al. · 2024 [cited by applicant]
US D1057159S · DeJong et al. · 2025 [cited by applicant]
US D1057160S · DeJong et al. · 2025 [cited by applicant]
US 12198790B1 · Al-Ali · 2025 [cited by applicant]
US 12200421B2 · Campbell et al. · 2025 [cited by applicant]
US 12207901B1 · Lapotko et al. · 2025 [cited by applicant]
US D1060680S · Al-Ali et al. · 2025 [cited by applicant]
US D1061585S · Indorf · 2025 [cited by applicant]
US D1063893S · DeJong et al. · 2025 [cited by applicant]
US 12220207B2 · Telfort et al. · 2025 [cited by applicant]
US 12230396B2 · Muhsin et al. · 2025 [cited by applicant]
US 12235941B2 · Kiani et al. · 2025 [cited by applicant]
US 12236767B2 · Muhsin · 2025 [cited by applicant]
US D1066244S · Lim et al. · 2025 [cited by applicant]
US D1066672S · Al-Ali et al. · 2025 [cited by applicant]
US 20040172222A1 · Simpson · 2004 [cited by examiner]
US 20100088120A1 · Gonzalvo · 2010 [cited by applicant]
US 20110140896A1 · Menzel · 2011 [cited by applicant]
US 20110245707A1 · Castle et al. · 2011 [cited by applicant]
US 20130305164A1 · Karunamuni · 2013 [cited by examiner]
US 20160210430A1 · Saleh · 2016 [cited by applicant]
US 20160361026A1 · Sarkar et al. · 2016 [cited by applicant]
US 20170287300A1 · Herbst et al. · 2017 [cited by applicant]
US 20240180456A1 · Al-Ali · 2024 [cited by applicant]
US 20240188872A1 · Al-Ali et al. · 2024 [cited by applicant]
US 20240245855A1 · Vo et al. · 2024 [cited by applicant]
US 20240260894A1 · Olsen · 2024 [cited by applicant]
US 20240267698A1 · Telfort et al. · 2024 [cited by applicant]
US 20240277233A1 · Al-Ali · 2024 [cited by applicant]
US 20240277280A1 · Al-Ali · 2024 [cited by applicant]
US 20240298920A1 · Fernkvist et al. · 2024 [cited by applicant]
US 20240306985A1 · Vo et al. · 2024 [cited by applicant]
US 20240324953A1 · Telfort · 2024 [cited by applicant]
US 20240380246A1 · Moran · 2024 [cited by applicant]
US 20240380247A1 · Moran · 2024 [cited by applicant]
US 20240404549A1 · Campbell et al. · 2024 [cited by applicant]
US 20250000458A1 · Abdul-Hafiz et al. · 2025 [cited by applicant]
US 20250037836A1 · Kiani · 2025 [cited by applicant]
U.S. Pat. No. 9,749,232, Intelligent Medical Network Edge Router, Aug. 29, 2017. [cited by applicant]
U.S. Pat. No. 10,833,983, Intelligent Medical Escalation Process, Nov. 10, 2020. [cited by applicant]
U.S. Pat. No. 11,887,728, Intelligent Medical Escalation Process, Jan. 30, 2024. [cited by applicant]
U.S. Pat. No. 10,832,818, Alarm Notification System, Nov. 10, 2020. [cited by applicant]
U.S. Pat. No. 11,488,711, Alarm Notification System, Nov. 1, 2022. [cited by applicant]
U.S. Pat. No. 11,699,526, Alarm Notification System, Jul. 11, 2023. [cited by applicant]
U.S. Pat. No. 12,009,098, Alarm Notification System, Jun. 11, 2024. [cited by applicant]
U.S. Pat. No. 12,230,396, Alarm Notification System, Feb. 18, 2025. [cited by applicant]
U.S. Pat. No. 10,825,568, Alarm Notification System, Nov. 3, 2020. [cited by applicant]
U.S. Pat. No. 10,667,764, Mobile Patient Alarm Display, Jun. 2, 2020. [cited by applicant]
U.S. Pat. No. 11,109,818, Mobile Patient Alarm Display, Sep. 7, 2021. [cited by applicant]
U.S. Pat. No. 11,844,634, Mobile Patient Alarm Display, Dec. 19, 2023. [cited by applicant]
U.S. Pat. No. 12,193,849, Mobile Patient Alarm Display, Jan. 14, 2025. [cited by applicant]
U.S. Appl. No. 18/530,852, Intelligent Medical Escalation Process, filed Dec. 6, 2023. [cited by applicant]
U.S. Appl. No. 18/963,166, Mobile Patient Alarm Display, filed Nov. 27, 2024. [cited by applicant]