# US 2023/0068111 A1 · Medical Monitoring System

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2023/0068111 A1
- Document ID: US20230068111A1
- Status: Published application
- Kind: A1
- Application number: 17/411,006
- Filed: 2021-08-24
- Published: 2023-03-02
- Earliest claimed: 2021-08-24
- Assignees: BioLink Systems, LLC
- Applicants: BioLink Systems, LLC
- Inventors: Roger King; Ken Heyl; Tim King; Alex Matsukevich; Tim Gardner
- Web page: https://patentgrep.com/patent/US20230068111A1

## CPC

- A61B 5/747: {in case of emergency, i.e. alerting emergency services}
- A61B 5/0022: {Monitoring a patient using a global network, e.g. telephone networks, internet}
- A61B 5/0205: Simultaneously evaluating both cardiovascular conditions and different types of body conditions, e.g. heart and respiratory condition
- A61B 5/1113: {Local tracking of patients, e.g. in a hospital or private home}
- A61B 5/6823: {Trunk, e.g., chest, back, abdomen, hip}
- A61B 5/6824: {Arm or wrist}
- A61B 5/7264: {Classification of physiological signals or data, e.g. using neural networks, statistical classifiers, expert systems or fuzzy systems}
- A61B 5/746: {Alarms related to a physiological condition, e.g. details of setting alarm thresholds or avoiding false alarms}
- A61B 5/7475: {User input or interface means, e.g. keyboard, pointing device, joystick}
- G16H 10/60: for patient-specific data, e.g. for electronic patient records
- G16H 40/20: for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
- G16H 40/67: for remote operation
- A61B 2505/07: Home care
- G16H 50/20: for computer-aided diagnosis, e.g. based on medical expert systems
- A61B: DIAGNOSIS; SURGERY; IDENTIFICATION (usefulness limited to only animals A61D)
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA

## Abstract

A medical monitoring system for use in residential facilities, nursing homes, or home environments is disclosed. The system utilizes a variety of modules and wearable medical devices that convey vital patient information to a series of smart hubs which are connected to the cloud. In the event a change in medical status of a patient occurs, the health care workers receive an Alert notifying them of which specific patient needs attention. The system is monitored using a specialized dashboard.

## Claims

### Claim at position 1

1-8. (canceled)

### Claim 9 (depends on 27)

The method of claim 27, further comprising:
encrypting all communications either to or from the one or more smart hubs, such that hacking or invading or ransom-izing a smart hub yields only encrypted data that would still need to be unencrypted to be usable;
an IOT hub component within a cloud system looking up a normal encryption key and decrypting encrypted data sent by a smart hub; and
storing that decrypted data within an event hub for long-term storage and blob storage.

### Claim at position 3

10-11. (canceled)

### Claim 12 (depends on 9)

The method of claim 9, further comprising:
all of the one or more smart hubs directly communicating with the cloud system.

### Claim 13 (depends on 9)

The method of claim 9, further comprising:
exactly one of the one or more smart hubs directly communicating with the cloud system and acting as a boss smart hub;
all other smart hubs all acting as relays that pass data to the boss smart hub.

### Claim at position 6

14-26. (canceled)

### Claim 27

A method of configuring a medical monitoring system, comprising:
positioning one or more wearable devices onto one or more patients, each patient wearing at least one of the one or more wearable devices;
the one or more wearable devices wirelessly communicating medical data to one or more smart hubs;
configuring one or more mobile clients to receive medical alerts regarding a particular patient and to respond to those alerts;
equipping each of one or more health care workers with one of the one or more mobile clients thereby facilitating the one or more health care workers having the ability to respond to the medical alerts;
the one or more wearables arriving to a facility in an un-registered state;
as part of a facility registration process, setting a first of the one or more wearables into a special pairing mode;
once the special pairing mode happens, an app running on the mobile client setting up a secure connection, where the app will receive a passcode generated by the first of the one or more wearables, as well as generate its own special encryption key;
comparing the special encryption key and the passcode;
if they match, that establishes that secure communication between the first of the one or more wearables and the app on the mobile client;
if they don't match, something went wrong in the registration process and the app will post an error-GUI;
the system facilitating both a special pairing mode and a normal pairing mode between one of the one or more module/wearables and one or more of the one or more smart hubs;
the special pairing mode occurring during a registration process wherein each time one of the one or more wearables is registered, generating a new special encryption key;
the normal pairing mode occurring during normal everyday use of the one or more wearables and one or more smart hubs;
during normal pairing mode, the app on the mobile client inquiring to the cloud system for the cloud system to generate the normal encryption key;
while generating the normal encryption key, the cloud system assigning that key to the ID of that module\wearable.

### Claim 28 (depends on 27)

The method of claim 27, further comprising:
the app generating the special encryption key; and
the cloud system generating the normal encryption key.

### Claim 29 (depends on 28)

The method of claim 28, further comprising:
the system achieving registration of a wearable whether the wearable is on or off a patient's body.

### Claim 30 (depends on 28)

The method of claim 28, further comprising:
configuring exactly one special encryption key for exactly one of the one or more wearables at a time;
facilitating any of the one or more module\wearables to be re-usable and re-registrable;
each time a one of the one or more wearables gets re-registered, discarding the old special encryption key and the cloud system creating a new special encryption key.

### Claim 31 (depends on 28)

The method of claim 28, further comprising:
the app running on the mobile client acting as a status indicator and problem notifier for one of the one or more wearables;

### Claim 32 (depends on 31)

The method of claim 31, further comprising:
a health care worker possessing one of the one or more mobile clients and using that mobile client for assigning a specific wearable to be worn by a specific patient;
the health care worker holding the mobile client physically close to a specific wearable thereby avoiding any accidental match with a separate and non-intended wearable;
assessing and making a determination about a distance between the mobile client and the module/wearable;
when the distance is deemed sufficient, triggering a near field communication mechanism within the specific module\wearable;
when the distance is deemed sufficient, intentionally avoiding triggering a near field communication mechanism within any other module\wearable other than the specific module\wearable;
performing an encryption key exchange between the mobile client and the specific module\wearable;
the mobile client obtaining an ID of the module\wearable; and
the health care worker reading the app within the mobile client to ensure an “assignment completed” message appears.

### Claim 33 (depends on 32)

The method of claim 32, further comprising:
the encryption key that is part of the encryption key exchange comprising the normal encryption key referred to earlier.

### Claim 34 (depends on 32)

The method of claim 32, further comprising:
the system requiring that a successful registration occur prior to any attempt at assignment beginning.

### Claim 35 (depends on 34)

The method of claim 34, further comprising:
the smart hub conveying only encrypted data, where the special encryption key and normal encryption key are inaccessible from the smart hub; and
insulating the smart hub from either storing or conveying any non-encrypted or patient-sensitive medical data.

### Claim 36 (depends on 35)

The method of claim 35, further comprising:
in the event of a data hack of any of the one or more smart hubs, preventing the data hack from yielding any data about any patient.

### Claim 37 (depends on 34)

The method of claim 34, further comprising:
arranging that the one or more smart hubs be incapable of decrypting any data passed therethrough;
the one or more smart hubs forwarding all data through an Internet connection to the cloud system and then to an IOT hub;
the IOT hub and cloud system looking up the normal encryption key;
decrypting the data therein; and
putting that raw data into the event hub, at which point the raw data will be stored for long-term use within the blob storage.

### Claim 38

The method of claim X, further comprising:
configuring an alerts questionnaire so that at log in, workers first landing at a list of all currently active alerts;
the alerts questionnaire sorting the alerts by escalation levels comprising priority escalated, escalated, and other; and
facilitating that additional escalation levels can be added within the alerts questionnaire.

### Claim 39 (depends on 38)

The method of claim 38, further comprising:
facilitating sorting of alerts by patient;
within the patient alerts, sorting the alerts by escalation level, thereby facilitating workers paying attention appropriately; and
arranging that an alert changing escalation level may result in a different worker-role responding to that alert.

### Claim 40 (depends on 38)

The method of claim 38, further comprising:
arranging that alerts are only closed and reacted to by workers through the alert questionnaire on the mobile client and that closing of an alert never occurs through the system dashboard.

### Claim 41 (depends on 38)

The method of claim 38, further comprising:
configuring the alert questionnaire to manage alerts that have been triggered more than once in a chain context such that a chain alert does not reflect some new issue, but is merely repeating that an earlier issue has not yet been addressed; and
a GUI showing how often a chain alert has been repeated.

### Claim 42 (depends on 37)

The method of claim 37, further comprising:
acknowledging that the person data-entry or data-cleanup results in the person authorizing a discharge may differ from the person documenting a discharge;
acknowledging these are two different tasks with two different levels of information-accuracy; and
arranging that other workers can modify data after the fact, but the alert system will know where and when the data was modified, thus preserving data-integrity in a style similar to blockchain.
