IP Library Granted Patent US 12,651,209
Granted Patent B1
US 12,651,209 · App. 19/030,222 · Granted Jun 9, 2026

System for dynamic location-aware patient care process controls and dynamic location-aware tracking

Inventors: Jacob Mark (Boston, MA); Sajikumar Aravind (Burlington, MA); Michael Allen Kellstrand (Braintree, MA)
Assignee: Mobile Heartbeat, LLC
G06Q10/00G06F21/31G06F21/44G16H40/20G16H40/40G16H40/63G16H40/67G16Z99/00G06F2221/2111
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,651,209
App. No.
19/030,222
Granted
Jun 9, 2026
Kind
B1
Abstract

A system having a system backend having a backend processor configured to define a patient clinical team associated with a patient clinical process comprising of a series of patient clinical tasks effected within the healthcare facility, each patient clinical task with an associated patient clinical task location within the healthcare facility, a group of mobile devices communicably connected via a network to the system backend, each mobile device being associated with and configured for use by at least one care member of the patient clinical team, a low energy (LE) beacon array arranged in a predetermined relationship with and differentiating between different patient clinical task locations, and communicably connected to each of the mobile devices that is configured to resolve its proximity, from the beacon array, relative to the at least one patient clinical task location. The backend processor is configured to dynamically enhance the patient clinical team by dynamically changing in real-time a predetermined characteristic of the patient clinical team based on the resolved proximity of each mobile device associated with each care member of the patient clinical team.

Claims (34)

1 . A system for controlling a patient clinical process in a healthcare facility, the system comprising:

a system backend comprising:

a backend processor configured to define a patient care team associated with the patient clinical process for administering medical care to a patient within the healthcare facility, the patient clinical process comprising a series of patient clinical tasks effected within the healthcare facility and assigned to care members of the patient care team, each patient clinical task associated with a physically localized patient clinical task location within the healthcare facility, each physically localized patient clinical task location comprising a physical location within the healthcare facility at which a particular patient clinical task of the series of patient clinical tasks is to be performed with respect to administering the medical care to the patient;

a group of mobile devices communicably connected via a network to the system backend, each mobile device comprising a device processor and being fungible with another mobile device of the group of mobile devices, wherein logging into a mobile device comprises associating and configuring the mobile device of the group of mobile devices for use by a particular care member of the patient care team; and

a low energy (LE) beacon array comprising a plurality of LE beacons, each LE beacon being arranged in a predetermined physical locational relationship relative to other LE beacons of the plurality of LE beacons and differentiating between a plurality of physically localized patient clinical task locations based on the predetermined physical locational relationship, each LE beacon broadcasting a self-identifying signal, and each mobile device being configured to resolve its physical location within a single physically localized patient clinical task location of the plurality of physically localized patient clinical task locations by at least:

receiving one or more self-identifying signals from individual LE beacons of the plurality of LE beacons;

determining a proximity to each of the individual LE beacons from which the mobile device received the one or more self-identifying signals based at least in part on analyzing signal strength of the one or more self-identifying signals;

determining a particular LE beacon that is closest in proximity to the mobile device by comparing the determined proximities; and

resolving its physical location as being within the single physically localized patient clinical task location that is associated with the particular LE beacon;

wherein the backend processor is further configured to at least:

generate an alert or notification based on a first clinical task of a first clinical process;

dynamically route the alert or notification to at least a first subset of the group of mobile devices within the network;

receive resolved proximities of the group of mobile devices within the network that are communicating with the system backend;

determine whether there is a mobile device with a resolved proximity that is at the physical location associated to the first clinical task with the alert or notification that is still currently active;

in response to a mobile device having a resolved proximity at the physical location associated with the first clinical task, disable the alert or notification; and

in response to no mobile devices having resolved proximities at the physical location associated with the first clinical task, escalate the alert or notification to a higher level.

2 . The system of claim 1 , wherein escalating the alert or notification includes dynamically routing the alert or notification to at least a second subset of the group of mobile devices within the network, wherein the second subset is greater than the first subset.

3 . The system of claim 1 , wherein escalating the alert or notification includes escalating the alert or notification until there is a mobile device with a resolved proximity that is at the physical location associated to the first clinical task with the alert or notification that is still currently active.

4 . The system of claim 1 , wherein escalating the alert or notification includes escalating the alert or notification until there is the first clinical task is resolved.

5 . The system of claim 1 , wherein escalating the alert or notification includes expanding a number of the care members of the patient care team as part of a care team directory associated with the first clinical task.

6 . The system of claim 1 , wherein escalating the alert or notification includes escalating the alert or notification until a user responds to the alert or notification.

7 . The system of claim 1 , wherein the backend processor is further configured to resolve care members of the patient care team for each patient clinical task based on the resolved physical location of each mobile device associated with each care member of the patient care team.

8 . The system of claim 1 , wherein the backend processor resolves care members of the patient care team by dynamically updating a care team directory associated with each patient clinical task, the care team directory comprising one or more selectable elements, presented on each mobile device, each of the one or more selectable elements associated with each care member of the patient care team.

9 . The system of claim 8 , wherein the backend processor dynamically changes a state of at least one of the one or more selectable elements within the care team directory on each mobile device, the state of the at least one of the one or more selectable elements indicating availability of the associated care member of the patient care team, for each patient clinical task, based on the resolved physical location of each mobile device associated with each care member.

10 . The system of claim 1 , wherein the backend processor is further configured to filter access to at least one patient information associated with the patient clinical process based on the resolved physical location of each mobile device associated with each care member of the patient care team.

11 . The system of claim 1 , wherein the backend processor is further configured to filter access to at least one clinical information associated with the patient clinical process based on the resolved physical location of each mobile device associated with each care member of the patient care team.

12 . The system of claim 1 , wherein the backend processor is further configured to filter access to at least one laboratory information associated with the patient clinical process based on the resolved physical location of each mobile device associated with each care member of the patient care team.

13 . The system of claim 1 , wherein the backend processor is further configured to generate a patient care process-specific patient care team directory based on the resolved physical location of each mobile device associated with each care member of the patient care team.

14 . The system of claim 1 , wherein the backend processor is further configured to automatically change a login state of the mobile device of the group of mobile devices from a first login state to a second login state based at least in part on (i) a credential information of the particular care member of the patient care team and (ii) the resolved physical location of the mobile device, wherein the system backend receives the credential information.

15 . The system of claim 1 , wherein the backend processor is further configured to dynamically update and enhance a care team directory for each patient clinical task by dynamically changing a first predetermined characteristic of the patient care team based on the resolved physical location of each mobile device.

16 . The system of claim 15 , wherein the backend processor is further configured to dynamically update the patient clinical process by dynamically changing a second predetermined characteristic of the patient clinical process based on the resolved physical location of each mobile device.

17 . The system of claim 15 , wherein the backend processor is further configured to dynamically update and enhance the care team directory by dynamically changing a state of at least one selectable element of one or more selectable elements within a care team directory, the state of the at least one of the one or more selectable elements reflecting an availability of each care member, of the patient care team for each patient clinical task, based on the resolved physical location of each mobile device associated with each care member.

18 . The system of claim 13 , wherein the backend processor is further configured to dynamically route communication links between the care members and content links between the care members based on the resolved physical location of each mobile device associated with each care member of the patient care team.

19 . The system of claim 1 , wherein the backend processor is further configured to dynamically route asynchronous secure messaging based on the resolved physical location of each mobile device associated with each care member of the patient care team.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 6, 2025
From: MARK, JACOB; ARAVIND, SAJIKUMAR; KELLSTRAND, MICHAEL ALLEN
To: MOBILE HEARTBEAT, LLC
Reel/Frame 070430/0747 →
Continuity (6)
Continuation 17729335 · Apr 26, 2022
Continuation 16532310 · Aug 5, 2019
Division 14673478 · Mar 30, 2015
Provisional Application 62032172 · Aug 1, 2014
Provisional Application 62031089 · Jul 30, 2014
Provisional Application 61971887 · Mar 28, 2014
References Cited (67)
US 7603112B2 · Huomo et al. · 2009 [cited by applicant]
US 8041581B2 · Mitchel et al. · 2011 [cited by applicant]
US 8041583B2 · Albro et al. · 2011 [cited by applicant]
US 8060492B2 · Nair et al. · 2011 [cited by applicant]
US 8229358B2 · Caudevilla Laliena et al. · 2012 [cited by applicant]
US 8254902B2 · Bell et al. · 2012 [cited by applicant]
US 8326651B2 · McLaren et al. · 2012 [cited by applicant]
US 8355672B2 · Hinsey · 2013 [cited by applicant]
US 8359643B2 · Low et al. · 2013 [cited by applicant]
US 8428614B2 · Wolfe · 2013 [cited by applicant]
US 8516075B2 · Seetharam et al. · 2013 [cited by applicant]
US 8583560B1 · Burger · 2013 [cited by applicant]
US 8615413B2 · McKee et al. · 2013 [cited by applicant]
US 8656060B2 · Kyriazis et al. · 2014 [cited by applicant]
US 9058410B2 · McKee et al. · 2015 [cited by applicant]
US 9760682B2 · Mark · 2017 [cited by applicant]
US 9807195B2 · Mark · 2017 [cited by applicant]
US 9904777B2 · Mark · 2018 [cited by applicant]
US 10171935B1 · Reyes et al. · 2019 [cited by applicant]
US 10496790B2 · Mark et al. · 2019 [cited by applicant]
US 11328227B2 · Mark et al. · 2022 [cited by applicant]
US 20030137455A1 · McReynolds · 2003 [cited by applicant]
US 20040100377A1 · Brackett et al. · 2004 [cited by applicant]
US 20050136845A1 · Masuoka et al. · 2005 [cited by applicant]
US 20060290519A1 · Boate et al. · 2006 [cited by applicant]
US 20070184852A1 · Johnson et al. · 2007 [cited by applicant]
US 20090132586A1 · Napora et al. · 2009 [cited by applicant]
US 20090204434A1 · Breazeale, Jr. · 2009 [cited by applicant]
US 20090214009A1 · Schuman, Sr. · 2009 [cited by examiner]
US 20100305972A1 · McLaren et al. · 2010 [cited by applicant]
US 20110106565A1 · Compton et al. · 2011 [cited by applicant]
US 20120042039A1 · Mark · 2012 [cited by applicant]
US 20120095779A1 · Wengrovitz et al. · 2012 [cited by applicant]
US 20120290311A1 · Tara et al. · 2012 [cited by applicant]
US 20130074171A1 · Mark · 2013 [cited by applicant]
US 20130197928A1 · Vanderveen et al. · 2013 [cited by applicant]
US 20140074667A1 · Smith · 2014 [cited by applicant]
US 20140077956A1 · Sampath · 2014 [cited by examiner]
US 20140184408A1 · Herbst et al. · 2014 [cited by applicant]
US 20140330945A1 · Dabbiere et al. · 2014 [cited by applicant]
US 20140351175A1 · Venkat · 2014 [cited by examiner]
US 20150213213A1 · Havard et al. · 2015 [cited by applicant]
US 20150248230A1 · Mark · 2015 [cited by applicant]
US 20160012196A1 · Mark et al. · 2016 [cited by applicant]
US 20160029160A1 · Theurer et al. · 2016 [cited by applicant]
US 20170186301A1 · Vaddepally et al. · 2017 [cited by applicant]
CA 2550812A1 · 2006 [cited by applicant]
EP 3123438A1 · 2017 [cited by applicant]
WO 2015149073A1 · 2015 [cited by applicant]
Notice of Allowance mailed on Sep. 15, 2025 in related U.S. Appl. No. 17/729,335, 12 pages. [cited by applicant]
Advisory Action dated Dec. 31, 2018 in related U.S. Appl. No. 14/673,478, 2 pages. [cited by applicant]
Extended European Search Report dated Aug. 21, 2017 in related foreign application No. EP 15769644.4, 8 pgs. [cited by applicant]
Final Office Action dated Aug. 28, 2018 in related U.S. Appl. No. 14/673,478, 40 pages. [cited by applicant]
International Preliminary Report on Patentability dated Jun. 16, 2016 in International application No. PCT/US2015/023389, 27 pages. [cited by applicant]
International Search Report and Written Opinion, dated Aug. 28, 2015, in International application No. PCT/US2015/023389, 18 pages. [cited by applicant]
Boulos K., et al. “Real-time locating systems (RTLS) in healthcare: a condensed primer.” International journal of health geographics vol. 11, Issue 25, Jun. 28, 2012, doi:10.1186/1476-072X-11-25, 8 pages. [cited by applicant]
Non-Final Office Action dated Jan. 23, 2018 in related U.S. Appl. No. 14/673,478, 34 pages. [cited by applicant]
Notice of Allowance dated Apr. 9, 2019 in related U.S. Appl. No. 14/673,478, 10 pages. [cited by applicant]
Office Action dated Feb. 28, 2019 in related foreign European application No. EP 15769644.4, 8 pages. [cited by applicant]
Rauland, RTLS Nurse Call Integration Automating processes and improving care, 2013, rauland.com (Year: 2013), 4 pages. [cited by applicant]
Rauland, Responder® 5 Integration to Real-Time Staff Location Systems—Versus, Sep. 15, 2011, rauland.com (Year: 2011), 4 pages. [cited by applicant]
Non-Final Office Action dated Mar. 21, 2025, in related U.S. Appl. No. 17/729,335, 24 pages. [cited by applicant]
European Office Action dated Feb. 28, 2019, in related foreign application No. EP 15769644.4, 8 pages. [cited by applicant]
Extended European Search Report dated Jan. 30, 2023, in related European Patent Application No. 22187295, 11 pages. [cited by applicant]
Non-Final Office Action dated Jan. 25, 2019, in related U.S. Appl. No. 14/673,478, 36 pages. [cited by applicant]
Non-Final Office Action mailed Oct. 15, 2021, in related U.S. Appl. No. 16/532,310, 9 pages. [cited by applicant]
Notice of Allowance mailed Jan. 11, 2022, in related U.S. Appl. No. 16/532,310, 7 pages. [cited by applicant]