Transferring wireless monitoring with reduced data loss

Abstract

A monitoring hub may monitor a health status of a subject wearing a wireless wearable device. A monitoring hub may access wireless configuration data received from a remote server. The monitoring may establish wireless communication with the wearable device based on the wireless configuration data to wirelessly receive real-time physiological data from the wearable device. A monitoring hub may receive historical physiological data from a remote server. The historical physiological data includes physiological data collected by the wearable device and / or physiological data communicated from the wearable device to another monitoring hub prior to establishing wireless communication between the monitoring hub and the wearable device. The monitoring hub may generate user interface data for presenting a user interface including real-time physiological data in conjunction with historical physiological data to reduce monitoring gaps between the historical physiological data and the real-time physiological data.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] Any and all applications for which foreign and domestic priority claims are identified in the Application Data Sheet filed with this application are hereby incorporated by reference in accordance with 37 CFR 1.57. This application claims the benefit of U.S. Provisional Application No. 63 / 370,637, filed on August 5, 2022. The disclosure of each of the foregoing applications is incorporated herein in its entirety for all purposes.

[0003] FIELD OF THE DISCLOSURE

[0004] The present disclosure relates to physiological monitoring devices, systems, and methods.

[0005] background

[0006] Hospitals, nursing homes and other patient care facilities typically utilize multiple sensors, devices and / or monitors to collect or analyze physiological parameters of patients. There are various conventional sensor systems that use physiological sensors to collect physiological data, process the data and display the data on a display device. Clinicians, including doctors, nurses and other medical staff, use physiological parameters obtained from patient monitors to diagnose diseases and prescribe treatments. Clinicians also use physiological parameters to monitor patients during various clinical situations to determine whether to improve the level of medical care given to patients.

[0007] Overview

[0008] Some conventional sensor systems require time-consuming and complex processes to change the monitoring of physiological data between display devices. For example, the user may need to unplug the sensor from the first display device and reinsert the sensor into the second display device. As another example, the user may need to turn off the power of the sensors and then turn on their power to connect wirelessly with different display devices. As another example, the user may need to manually change the pairing state of the sensor and / or display device to terminate the wireless connection with one display device and / or establish a wireless connection with another display device. At least for the aforementioned examples, changing the monitoring of physiological data from the first display device to the second display device in a conventional sensor system may take a lot of time, may be too complicated and frustrating for the user, may cause user errors, and may cause the loss of physiological data, such as during the time when the sensor is not connected (e.g., wirelessly and / or wired) to any display device.

[0009] Various embodiments of systems, methods, and devices within the scope of the appended claims each have several aspects, no single one of which is solely responsible for the desirable attributes described herein. Without limiting the scope of the appended claims, the following description describes some prominent features.

[0010] Details of one or more implementations of the subject matter described in this specification are shown in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, drawings, and claims. Note that the relative sizes of the following drawings may not be drawn to scale.

[0011] The present invention discloses a monitoring hub configured to monitor the health status of an object wearing a wireless wearable device. The monitoring hub may include one or more hardware computer processors. The one or more hardware processors may be configured to execute multiple computer executable instructions so that the monitoring hub responds to a request to establish wireless monitoring of the subject's physiology at the monitoring hub: accesses wireless configuration data for managing wireless communication with the wearable device on the subject, the wireless configuration data including at least one or more device addresses associated with the wearable device, and the wireless configuration data is received from a remote server at the monitoring hub. The one or more hardware processors may be configured to execute multiple computer executable instructions so that the monitoring hub responds to a request to establish wireless monitoring of the subject's physiology at the monitoring hub, and establishes wireless communication between the monitoring hub and the wearable device based at least on the wireless configuration data, so that the monitoring hub uses one or more wireless communication protocols to wirelessly receive real-time physiological data from the wearable device. One or more hardware processors may be configured to execute a plurality of computer executable instructions so that the monitoring hub receives historical physiological data from a remote server in response to a request to establish wireless monitoring of the subject's physiology at the monitoring hub, the historical physiological data including physiological data collected by the wearable device before wireless communication is established between the monitoring hub and the wearable device, and the historical physiological data including physiological data communicated from the wearable device to another monitoring hub before wireless communication is established between the monitoring hub and the wearable device. One or more hardware processors may be configured to execute a plurality of computer executable instructions so that the monitoring hub generates user interface data in response to a request to establish wireless monitoring of the subject's physiology at the monitoring hub for presenting a user interface including real-time physiological data combined with historical physiological data to reduce a monitoring gap between historical physiological data and real-time physiological data.

[0012] The one or more hardware computer processors may also be configured to execute a plurality of computer executable instructions to cause the monitoring hub to establish the wireless communication between the monitoring hub and the wearable device by establishing a Bluetooth connection between the monitoring hub and the wearable device.

[0013] The one or more hardware computer processors may also be configured to execute a plurality of computer-executable instructions to cause the monitoring hub to establish the wireless communication between the monitoring hub and the wearable device by establishing the wireless communication without performing a Bluetooth pairing process.

[0014] The one or more hardware computer processors may also be configured to execute a plurality of computer-executable instructions to cause the monitoring hub to establish the wireless communication between the monitoring hub and the wearable device in response to user input, the user input comprising contactless user input.

[0015] The one or more hardware computer processors may also be configured to execute a plurality of computer executable instructions so that the monitoring hub receives identification data via the monitoring hub using one or more of near field communication (NFC) or radio frequency identification (RFID), the identification data being associated with a user requesting to establish wireless monitoring with the monitoring hub. The one or more hardware computer processors may also be configured to execute a plurality of computer executable instructions so that the monitoring hub determines, based at least on the identification data, that the user has authority to establish wireless monitoring.

[0016] The one or more hardware computer processors may also be configured to execute a plurality of computer-executable instructions to cause the monitoring hub to establish the wireless communication between the monitoring hub and the wearable device based at least on a proximity of the wearable device to the monitoring hub.

[0017] The one or more hardware computer processors may also be configured to execute a plurality of computer-executable instructions to cause the monitoring hub to access the wireless configuration data by wirelessly receiving the wireless configuration data from a remote server.

[0018] The one or more hardware computer processors may also be configured to execute a plurality of computer-executable instructions to cause the monitoring hub to access the wireless configuration data based at least on retrieving the wireless configuration data from the memory.

[0019] The one or more hardware computer processors may also be configured to execute a plurality of computer-executable instructions to cause the monitoring hub to present a user interface via a display of the monitoring hub.

[0020] The one or more hardware computer processors may also be configured to execute a plurality of computer executable instructions to cause the monitoring hub to receive historical user interface data from a remote server, the historical user interface data corresponding to historical physiological data, the historical user interface data previously generated by another monitoring hub.

[0021] Disclosed herein is a method for continuously monitoring a patient wearing a wireless wearable device when changing from a first monitoring hub to a second monitoring hub. The method may include, in response to a request to establish wireless monitoring of the subject's physiology at the monitoring hub, accessing wireless configuration data for managing wireless communication with a wearable device on the subject, the wireless configuration data including at least one or more device addresses associated with the wearable device, the wireless configuration data being received at the monitoring hub from a remote server. The method may also include establishing wireless communication between the monitoring hub and the wearable device based at least on the wireless configuration data, so that the monitoring hub wirelessly receives real-time physiological data from the wearable device using one or more wireless communication protocols. The method may also include receiving historical physiological data from the remote server, the historical physiological data including physiological data collected by the wearable device before wireless communication is established between the monitoring hub and the wearable device, the historical physiological data including physiological data communicated from the wearable device to another monitoring hub before wireless communication is established between the monitoring hub and the wearable device. The method may also include generating user interface data for presenting a user interface including real-time physiological data combined with historical physiological data to reduce a monitoring gap between historical physiological data and real-time physiological data.

[0022] In some embodiments, establishing the wireless communication between the monitoring hub and the wearable device includes establishing a Bluetooth connection between the monitoring hub and the wearable device without performing a Bluetooth pairing process.

[0023] The method may further include establishing the wireless communication between the monitoring hub and the wearable device in response to a user input, the user input comprising a contactless user input.

[0024] The method may also include receiving identification data via the monitoring hub using one or more of near field communication (NFC) or radio frequency identification (RFID), the identification data being associated with a user requesting to establish wireless monitoring with the monitoring hub. The method may also include determining, based at least on the identification data, that the user has authority to establish wireless monitoring.

[0025] In some implementations, accessing the wireless configuration data includes retrieving the wireless configuration data from a memory.

[0026] The method may also include presenting a user interface via a display of the monitoring hub.

[0027] The method may also include receiving historical user interface data from a remote server, the historical user interface data corresponding to the historical physiological data, the historical user interface data previously generated by another monitoring hub.

[0028] Disclosed herein is a non-transitory computer-readable medium including computer-executable instructions, which when executed by a computing system causes the computing system to perform operations. The operations may include, in response to a request to establish wireless monitoring of the physiology of an object at a monitoring hub, accessing wireless configuration data for managing wireless communication with a wearable device on the subject, the wireless configuration data including at least one or more device addresses associated with the wearable device, the wireless configuration data being received at the monitoring hub from a remote server. The operations may also include establishing wireless communication between the monitoring hub and the wearable device based at least on the wireless configuration data, so that the monitoring hub wirelessly receives real-time physiological data from the wearable device using one or more wireless communication protocols. The operations may also include receiving historical physiological data from a remote server, the historical physiological data including physiological data collected by the wearable device before wireless communication is established between the monitoring hub and the wearable device, the historical physiological data including physiological data communicated from the wearable device to another monitoring hub before wireless communication is established between the monitoring hub and the wearable device. The operations may also include generating user interface data for presenting a user interface including real-time physiological data combined with historical physiological data to reduce a monitoring gap between historical physiological data and real-time physiological data.

[0029] In some implementations, the computer executable instructions, when executed by the computing system, further cause the computing system to perform operations including presenting a user interface via a display of the monitoring hub.

[0030] In some embodiments, the computer executable instructions, when executed by the computing system, also cause the computing system to perform operations including receiving historical user interface data from a remote server, the historical user interface data corresponding to historical physiological data, the historical user interface data previously generated by another monitoring hub.

[0031] A computing system is disclosed herein that is configured to facilitate continuous monitoring of a patient wearing a wireless wearable device when changing from a first monitoring hub to a second mobile monitoring hub. The computing system may include an indoor display device configured to electronically monitor the patient, the indoor display device including display indicia responsive to physiological data of the patient originating from a wearable device on the patient, wherein the wearable device includes a wireless wearable device, wherein the wireless wearable device includes wireless configuration data for managing wireless transmission of the physiological data from the wearable device. The computing system may also include one or more hardware computer processors configured to execute computer-executable instructions so that the computing system receives, via the indoor display device, a request to transfer wireless monitoring of the patient from the indoor display device to the mobile monitoring hub, the request including identification data associated with a user requesting to transfer the wireless monitoring. The one or more hardware computer processors may be configured to execute computer-executable instructions to further cause the computing system to determine whether the user has authority to transfer the wireless monitoring based at least on the identification data. One or more hardware computer processors can be configured to execute computer-executable instructions to further cause the computing system to access the wireless configuration data associated with the wireless wearable device on the patient in response to determining that the user has permission to transfer wireless monitoring, and the wireless configuration data is received from the indoor display device. One or more hardware computer processors can be configured to execute computer-executable instructions to further cause the computing system to wirelessly transmit the wireless configuration data associated with the wireless wearable device on the patient to the mobile monitoring hub, so that the mobile monitoring hub establishes wireless communication between the mobile monitoring hub and the wearable device.

[0032] The one or more hardware computer processors may be configured to execute computer-executable instructions to further cause the computing system to receive the second identification data via the mobile monitoring hub. The one or more hardware computer processors may be configured to execute computer-executable instructions to further cause the computing system to determine an approval status of the request to transfer wireless monitoring based at least on comparing the identification data to the second identification data.

[0033] One or more hardware computer processors may be configured to execute computer-executable instructions to further cause the computing system to receive the identification data via an indoor display device, via contactless user input, utilizing one or more of near field communication (NFC) or radio frequency identification (RFID).

[0034] The one or more hardware computer processors may be configured to execute computer-executable instructions to further cause the computing system to receive, via the indoor display device, via contactless user input, the request to transfer wireless monitoring including the identification data.

[0035] In some embodiments, the identification data includes a serial number.

[0036] In some embodiments, identification data includes biomarkers.

[0037] The one or more hardware computer processors may be configured to execute computer-executable instructions to further cause the computing system to determine the proximity of the wearable device to the mobile monitoring hub based at least on determining a signal strength associated with the wearable device. The one or more hardware computer processors may be configured to execute computer-executable instructions to further cause the computing system to establish the wireless communication between the mobile monitoring hub and the wearable device based at least on determining that the wearable device is within a threshold proximity of the mobile monitoring hub.

[0038] One or more hardware computer processors can be configured to execute computer-executable instructions to further cause the computing system to wirelessly transmit historical physiological data to the mobile monitoring hub in response to determining that the user has authority to transfer wireless monitoring, the historical physiological data previously collected by the wearable device and communicated from the wearable device to the indoor display device.

[0039] In some implementations, the wireless configuration data includes a device address associated with the wearable device and one or more link keys associated with establishing wireless communication with the wearable device.

[0040] The one or more hardware computer processors may be configured to execute computer-executable instructions to further cause the computing system to terminate the wireless communication connection between the indoor display device and the wearable device in response to an indication that the mobile monitoring hub is in a transfer mode.

[0041] The one or more hardware computer processors may be configured to execute computer-executable instructions to further cause the computing system to receive the wireless configuration data from the indoor display device.

[0042] Disclosed herein is a method for continuously monitoring a patient wearing a wireless wearable device while changing from a first monitoring hub to a second mobile monitoring hub, the second mobile monitoring hub being configured to move with the patient if the patient changes location. The method may include electronically monitoring the patient with an indoor display device, the indoor display device including a display indicia responsive to physiological data of the patient originating from a wearable device on the patient, wherein the wearable device includes a wireless wearable device, wherein the wireless wearable device includes wireless configuration data for managing wireless transmission of the physiological data from the wearable device. The method may also include receiving, via the indoor display device, a request to transfer wireless monitoring of the patient from the indoor display device to the mobile monitoring hub, the request including identification data associated with a user requesting to transfer the wireless monitoring. The method may also include determining, based at least on the identification data, whether the user has permission to transfer the wireless monitoring. The method may also include, in response to determining that the user has permission to transfer the wireless monitoring, accessing the wireless configuration data associated with the wireless wearable device on the patient, the wireless configuration data being received from the indoor display device. The method may also include, in response to determining that the user has permission to transfer wireless monitoring, wirelessly transmitting the wireless configuration data associated with the wireless wearable device on the patient to the mobile monitoring hub, so that the mobile monitoring hub establishes wireless communication between the mobile monitoring hub and the wearable device.

[0043] The method may further include receiving, via the mobile monitoring hub, second identification data.The method may further include determining an approval status of the request to transfer wireless monitoring based at least on comparing the identification data to the second identification data.

[0044] The method may further include receiving the identification data via the indoor display device via a contactless user input, using one or more of near field communication (NFC) or radio frequency identification (RFID).

[0045] The method may further include receiving, via a contactless user input via an indoor display device, the request to transfer wireless monitoring including the identification data.

[0046] In some embodiments, the identification data includes one or more of a sequence number or a biomarker.

[0047] In some embodiments, monitoring the patient with a wearable device comprises monitoring the patient with a watch.

[0048] In some embodiments, monitoring the patient with the wearable device includes monitoring the patient with a wearable hub in communication with one or more of an ECG sensor, a SpO2 sensor, and a blood pressure sensor.

[0049] The present invention discloses a non-transitory computer-readable medium including computer-executable instructions, which, when executed by a computing system, causes the computing system to perform operations including: electronically monitoring a patient with an indoor display device, the indoor display device including a display mark responsive to the patient's physiological data originating from a wearable device on the patient, wherein the wearable device includes a wireless wearable device, wherein the wireless wearable device includes wireless configuration data for managing the wireless transmission of the physiological data from the wearable device; receiving a request to transfer the patient's wireless monitoring from the indoor display device to a mobile monitoring hub via the indoor display device, the request including identification data associated with a user requesting to transfer the wireless monitoring; determining whether the user has permission to transfer the wireless monitoring based at least on the identification data; and in response to determining that the user has permission to transfer the wireless monitoring: accessing the wireless configuration data associated with the wireless wearable device on the patient, the wireless configuration data being received from the indoor display device; and wirelessly transmitting the wireless configuration data associated with the wireless wearable device on the patient to the mobile monitoring hub, so that the mobile monitoring hub establishes wireless communication between the mobile monitoring hub and the wearable device.

[0050] In some embodiments, the computer executable instructions, when executed by the computing system, further cause the computing system to perform operations including: receiving second identification data via the mobile monitoring hub; and determining an approval status of the request to transfer wireless monitoring based at least on comparing the identification data with the second identification data.

[0051] Disclosed herein is a method for continuously monitoring a patient wearing a wireless wearable device while changing from a first monitoring hub to a second mobile monitoring hub, the second mobile monitoring hub being configured to move with the patient if the patient changes location. The method may include electronically monitoring the patient with an indoor display device. The indoor display device may include display indicia responsive to physiological data of the patient originating from a wearable device on the patient. The wearable device may include a wireless wearable device. The wireless wearable device may include wireless configuration data for managing wireless transmission of the physiological data from the wearable device. The method may also include receiving a request to transfer wireless monitoring of the patient from the indoor display device to the mobile monitoring hub. The method may also include electronically instructing a caregiver to place the mobile monitoring hub in a transfer mode. The method may also include accessing the wireless configuration data associated with the wireless wearable device on the patient, the wireless configuration data being received from the indoor display device, in response to an indication that the mobile monitoring hub is in a transfer mode. The method may also include, in response to an indication that the mobile monitoring hub is in a transfer mode, wirelessly transmitting the wireless configuration data associated with the wireless wearable device on the patient to the mobile monitoring hub so that the mobile monitoring hub establishes wireless communication between the mobile monitoring hub and the wearable device. The method may also include, in response to an indication that the mobile monitoring hub is in a transfer mode, wirelessly transmitting historical physiological data to the mobile monitoring hub, the historical physiological data previously collected by the wearable device and communicated from the wearable device to an indoor display device.

[0052] The method may also include receiving, via the indoor display device, identification data associated with the user requesting transfer of the wireless monitoring. The method may also include determining whether the user has authority to transfer the wireless monitoring based at least on the identification data.

[0053] The method may also include receiving, via the indoor display device, identification data associated with the user requesting transfer of wireless monitoring.The method may also include determining an approval status of the request to transfer wireless monitoring based at least on comparing the identification data with second identification data received via the mobile monitoring hub.

[0054] In some implementations, the wireless configuration data includes a device address associated with the wearable device and one or more link keys associated with establishing wireless communication with the wearable device.

[0055] The method may also include terminating the wireless communication connection between the indoor display device and the wearable device in response to an indication that the mobile monitoring hub is in a transfer mode.

[0056] The method may further include receiving the wireless configuration data from an indoor display device.

[0057] The method may also include receiving the historical physiological data from an in-room display device.

[0058] In some embodiments, monitoring the patient with a wearable device comprises monitoring the patient with a watch.

[0059] In some embodiments, monitoring the patient with the wearable device includes monitoring the patient with a wearable hub in communication with one or more of an ECG sensor, a SpO2 sensor, and a blood pressure sensor.

[0060] The method may also include wirelessly transmitting user interface data to the mobile monitoring hub, the user interface data corresponding to the historical physiological data, the user interface data previously generated by the indoor display device.

[0061] Disclosed herein is a method for continuously monitoring a patient wearing a wireless wearable device while changing from a first monitoring hub to a second monitoring hub. The method may include establishing wireless communication between the monitoring hub and the wearable device on the subject according to a wireless communication protocol. The monitoring hub may include a display marker responsive to the subject's physiological data originating from the wearable device. The wireless communication may include a wireless communication connection. The method may also include receiving wireless configuration data associated with the wearable device according to the wireless communication protocol, the wireless configuration data managing wireless communication with the wearable device. The method may also include receiving physiological data of the subject at the monitoring hub via wireless communication between the monitoring hub and the wearable device, the physiological data originating from the wearable device. The method may also include communicating the physiological data to a remote server. The method may also include communicating at least a portion of the wireless configuration data associated with the wearable device to a remote server, at least a portion of the wireless configuration data including at least one or more device addresses associated with the wearable device, the one or more device addresses being configured to facilitate wireless communication with the wearable device.

[0062] The method may further include communicating the physiological data or the wireless configuration data to a remote server in response to a request to transfer physiological monitoring from the monitoring hub to another monitoring hub.

[0063] In some embodiments, establishing the wireless communication between the monitoring hub and the wearable device includes establishing a Bluetooth connection between the monitoring hub and the wearable device.

[0064] The method may also include communicating user interface data to a remote server, the user interface data corresponding to the physiological data, the user interface data being generated by the monitoring hub.

[0065] Disclosed herein is a method for monitoring the location of a patient wearing a wearable device. The method may include: detecting a wireless configuration signal from a wearable device on a patient at a monitoring hub. The wireless configuration signal may include at least a portion of a paging process of a Bluetooth communication protocol. The method may also include determining whether the wearable device is within a threshold proximity of the monitoring hub based at least on a signal strength associated with the wireless configuration signal. The method may also include, in response to determining that the wearable device is within a threshold proximity of the monitoring hub, establishing wireless communication between the wearable device and the monitoring hub according to the Bluetooth communication protocol, the wireless communication including a Bluetooth connection. The method may also include, in response to establishing the wireless communication, determining the location of an object based at least on determining the location of the monitoring hub in an environment.

[0066] Disclosed herein is a method for continuously monitoring a patient wearing a wireless wearable device while changing from a first monitoring hub to a second monitoring hub. The method may include accessing wireless configuration data that manages wireless communications with one or more sensors connected to the subject, the wireless configuration data including at least one or more device addresses associated with the one or more sensors. The method may include receiving user input to establish wireless communications between the monitoring hub and the one or more sensors, the user input including contactless user input. The method may include, in response to the user input, establishing wireless communications between the monitoring hub and the one or more sensors based at least on the wireless configuration data so that the monitoring hub wirelessly receives real-time physiological data from the one or more sensors.

[0067] The method may include determining a proximity of the one or more sensors to the monitoring hub based at least on determining a signal strength associated with the one or more sensors. The method may also include establishing the wireless communication between the monitoring hub and the one or more sensors based at least on determining that the one or more sensors are within a threshold proximity of the monitoring hub.

[0068] In some embodiments, receiving the contactless user input includes receiving, via the monitoring hub, a wireless signal associated with one or more of near field communication (NFC) or radio frequency identification (RFID).

[0069] Disclosed herein is a method for continuously monitoring a patient wearing a wireless wearable device while changing from a first monitoring hub to a second monitoring hub. The method may include accessing wireless configuration data that manages wireless communications with multiple sensors connected to the object, the wireless configuration data including at least one or more device addresses associated with the multiple sensors. The method may also include receiving user input to establish wireless communications between the monitoring hub and the multiple sensors, the user input including a single user input. The method may also include, in response to the single user input, establishing wireless communications between the monitoring hub and the multiple sensors based at least on the wireless configuration data so that the monitoring hub wirelessly receives real-time physiological data from the multiple sensors.

[0070] In some embodiments, receiving the user input includes receiving contactless user input via a monitoring hub.

[0071] The present invention discloses a monitoring hub for monitoring the physiological state of an object, the monitoring hub comprising: a communication component; a computer-readable storage medium having program instructions contained therein; and one or more processors. The communication component can be configured to: wirelessly communicate with one or more sensors to communicate physiological data and communication data with one or more sensors; and wirelessly communicate with a physiological monitoring system to communicate physiological data and communication data with the physiological monitoring system. One or more processors can be configured to execute program instructions so that the monitoring hub: receives a request to perform a transfer operation; receives identification data; verifies the authority of the request based at least in part on the identification data; establishes communication with another monitoring hub via the communication component, whereby the communication component is configured to wirelessly communicate with another monitoring hub to communicate physiological data or communication data with another monitoring hub; determines the approval status of the request to perform a transfer operation based at least in part on the identification data; in response to determining that the request to perform a transfer operation is approved, causes the communication component to communicate the physiological data or communication data to another monitoring hub; and terminates the wireless communication connection between the communication component and one or more sensors.

[0072] In some embodiments, the one or more processors are further configured to execute program instructions so that the monitoring hub receives identification data via the communication component. In some embodiments, the one or more processors are further configured to execute program instructions so that the monitoring hub receives identification data using near field communication (NFC) of the communication component. In some embodiments, the one or more processors are further configured to execute program instructions so that the monitoring hub receives identification data via a user input or display of the monitoring hub. In some embodiments, the identification data includes a user identification. In some embodiments, the one or more processors are further configured to execute program instructions so that the monitoring hub receives second identification data via the communication component. In some embodiments, the one or more processors are further configured to execute program instructions so that the monitoring hub compares the identification data with the second identification data to determine whether the identification data matches the second identification data. In some embodiments, the one or more processors are further configured to execute program instructions so that the monitoring hub determines the approval status of the request based at least in part on comparing the identification data with the second identification data. In some embodiments, the one or more processors are further configured to execute program instructions so that if the identification data matches the second identification data, the monitoring hub determines that the request to perform the transfer operation is approved. In some embodiments, one or more processors are further configured to execute program instructions so that if the user identifier of the identification data matches the user identifier of the second identification data, the monitoring hub determines that the request for the transfer operation is approved. In some embodiments, one or more processors are further configured to execute program instructions so that the monitoring hub communicates the identification data to another monitoring hub via a communication component. In some embodiments, one or more processors are further configured to execute program instructions so that the monitoring hub communicates the identification data to a physiological monitoring system via a communication component. In some embodiments, one or more processors are further configured to execute program instructions so that the monitoring hub receives the approval status of the request from another monitoring hub via a communication component. In some embodiments, one or more processors are further configured to execute program instructions so that the monitoring hub communicates the approval status of the request from the physiological monitoring system via a communication component. In some embodiments, one or more processors are further configured to execute program instructions so that the monitoring hub responds to determining that the request for the transfer operation is approved, so that the communication component communicates physiological data or communication data to the physiological monitoring system. In some embodiments, the physiological data includes one or more raw physiological data, processed physiological data, or physiological parameter values ​​obtained from one or more sensors. In some embodiments, the physiological data includes historical physiological data. In some embodiments, the communication data includes one or more device addresses of the one or more sensors.In some embodiments, one or more processors are further configured to execute program instructions so that the monitoring hub receives communication data from another monitoring hub via a communication component. In some embodiments, one or more processors are further configured to execute program instructions so that the monitoring hub communicates the communication data received from another monitoring hub to one or more sensors via a communication component. In some embodiments, the communication data received from another monitoring hub includes the device address of another monitoring hub. In some embodiments, one or more processors are further configured to execute program instructions so that the monitoring hub receives a confirmation of the completion of the transfer operation via a communication component. In some embodiments, one or more processors are further configured to execute program instructions so that the monitoring hub receives a confirmation from another monitoring hub or from a physiological monitoring system. In some embodiments, the confirmation includes an indication that another monitoring hub has established a wireless communication connection with one or more sensors. In some embodiments, the communication component includes a transceiver. In some embodiments, the communication component is further configured to communicate with one or more sensors using one or more wireless communication protocols including WiFi, Bluetooth, near field communication (NFC), radio frequency identification (RFID), cellular, 1G, 2G, 3G, 4G, 5G or Zigbee. In some embodiments, the communication component is further configured to communicate with the physiological monitoring system using one or more wireless communication protocols including WiFi, Bluetooth, near field communication (NFC), radio frequency identification (RFID), cellular, 1G, 2G, 3G, 4G, 5G or Zigbee. In some embodiments, the communication component is further configured to communicate with another monitoring hub using one or more wireless communication protocols including WiFi, Bluetooth, near field communication (NFC), radio frequency identification (RFID), cellular, 1G, 2G, 3G, 4G, 5G or Zigbee. In some embodiments, one or more processors are further configured to execute program instructions to receive a request for a transfer operation via a user input of the monitoring hub. In some embodiments, verifying the authority of the request includes verifying the authority of the user associated with the request. In some embodiments, one or more processors are further configured to execute program instructions so that the communication component communicates a transfer signal to the physiological monitoring system to initiate a transfer operation. In some embodiments, one or more processors are further configured to execute program instructions so that the communication component communicates physiological data or communication data to the physiological monitoring system to initiate a transfer operation. In some embodiments, the physiological data includes historical physiological data. In some embodiments, the communication data includes one or more device addresses of the one or more sensors.

[0073] Disclosed herein is a monitoring hub for monitoring the physiological state of an object, the monitoring hub comprising: a communication component; a computer-readable storage medium having program instructions contained therewith; and one or more processors. In some embodiments, the communication component is configured to: wirelessly communicate with one or more sensors to communicate physiological data and communication data with one or more sensors; and wirelessly communicate with a physiological monitoring system to communicate physiological data and communication data with the physiological monitoring system. In some embodiments, one or more processors are configured to execute program instructions so that the monitoring hub: receives a request to perform a transfer operation; receives identification data; establishes communication with another monitoring hub via the communication component, whereby the communication component is configured to wirelessly communicate with another monitoring hub to communicate physiological data or communication data with another monitoring hub; determines the approval status of the request to perform a transfer operation based at least in part on the identification data; in response to determining that the request to perform a transfer operation is approved, receives physiological data or communication data from another monitoring hub via the communication component; and establishes a wireless communication connection between the communication component and one or more sensors.

[0074] In some embodiments, the one or more processors are further configured to execute program instructions so that the monitoring hub receives identification data via the communication component. In some embodiments, the one or more processors are further configured to execute program instructions so that the monitoring hub receives identification data using near field communication (NFC) of the communication component. In some embodiments, the one or more processors are further configured to execute program instructions so that the monitoring hub receives identification data via a user input or display of the monitoring hub. In some embodiments, the identification data includes a user identification. In some embodiments, the one or more processors are further configured to execute program instructions so that the monitoring hub receives second identification data via the communication component. In some embodiments, the one or more processors are further configured to execute program instructions so that the monitoring hub compares the identification data with the second identification data to determine whether the identification data matches the second identification data. In some embodiments, the one or more processors are further configured to execute program instructions so that the monitoring hub determines the approval status of the request based at least in part on comparing the identification data with the second identification data. In some embodiments, the one or more processors are further configured to execute program instructions so that if the identification data matches the second identification data, the monitoring hub determines that the request to perform the transfer operation is approved. In some embodiments, one or more processors are further configured to execute program instructions so that if the user identification of the identification data matches the user identification of the second identification data, the monitoring hub determines that the request for the transfer operation is approved. In some embodiments, one or more processors are further configured to execute program instructions so that the monitoring hub communicates the identification data to another monitoring hub via a communication component. In some embodiments, one or more processors are further configured to execute program instructions so that the monitoring hub communicates the identification data to a physiological monitoring system via a communication component. In some embodiments, one or more processors are further configured to execute program instructions so that the monitoring hub receives the approval status of the request from another monitoring hub via a communication component. In some embodiments, one or more processors are further configured to execute program instructions so that the monitoring hub receives the approval status of the request from the physiological monitoring system via a communication component. In some embodiments, one or more processors are further configured to execute program instructions so that the monitoring hub receives physiological data or communication data from the physiological monitoring system via a communication component in response to determining that the request for the transfer operation is approved. In some embodiments, the physiological data includes one or more raw physiological data, processed physiological data, or physiological parameter values ​​obtained from one or more sensors. In some embodiments, the physiological data includes historical physiological data. In some embodiments, the communication data includes one or more device addresses of the one or more sensors.In some embodiments, one or more processors are further configured to execute program instructions so that the monitoring hub communicates the confirmation of the transfer operation via the communication component. In some embodiments, one or more processors are further configured to execute program instructions so that the monitoring hub will confirm the communication to another monitoring hub or a physiological monitoring system. In some embodiments, the confirmation includes an indication that the monitoring hub has established a wireless communication connection with one or more sensors. In some embodiments, the communication component includes a transceiver. In some embodiments, the communication component is further configured to communicate with one or more sensors using one or more wireless communication protocols including WiFi, Bluetooth, near field communication (NFC), radio frequency identification (RFID), cellular, 1G, 2G, 3G, 4G, 5G or Zigbee. In some embodiments, the communication component is further configured to communicate with the physiological monitoring system using one or more wireless communication protocols including WiFi, Bluetooth, near field communication (NFC), radio frequency identification (RFID), cellular, 1G, 2G, 3G, 4G, 5G or Zigbee. In some embodiments, the communication component is also configured to communicate with another monitoring hub using one or more wireless communication protocols including WiFi, Bluetooth, near field communication (NFC), radio frequency identification (RFID), cellular, 1G, 2G, 3G, 4G, 5G or Zigbee. In some embodiments, one or more processors are also configured to execute program instructions so that the monitoring hub receives a request for a transfer operation via a user input of the monitoring hub. In some embodiments, one or more processors are also configured to execute program instructions so that the communication component communicates physiological data or communication data to a physiological monitoring system. In some embodiments, one or more processors are also configured to execute program instructions so that the monitoring hub receives physiological data from one or more sensors via the communication component. In some embodiments, one or more processors are also configured to execute program instructions to display physiological data and historical physiological data received from one or more sensors via a display of the monitoring hub.

[0075] The present invention discloses a physiological monitoring system for monitoring the physiological state of an object, the physiological monitoring system comprising: a computer-readable storage medium having program instructions contained therein; and one or more processors. The one or more processors can be configured to execute the program instructions so that the physiological monitoring system: receives a request to perform a transfer operation from one or more monitoring hubs; determines the approval status of the request to perform the transfer operation; in response to determining that the request to perform the transfer operation is approved: receives monitoring hub communication data from one or more monitoring hubs; accesses sensor communication data: establishes a wireless communication connection between a first monitoring hub of the one or more monitoring hubs and one or more sensors; and terminates the wireless communication connection between a second monitoring hub of the one or more monitoring hubs and one or more sensors.

[0076] In some embodiments, the one or more processors are further configured to execute program instructions so that the physiological monitoring system determines the approval status based at least in part on one or more signals received from one or more monitoring hubs. In some embodiments, the one or more processors are further configured to execute program instructions so that the physiological monitoring system receives first and second identification data from one or more monitoring hubs. In some embodiments, the first and second identification data include user identification. In some embodiments, the one or more processors are further configured to execute program instructions so that the physiological monitoring system compares the first identification data with the second identification data to determine whether the first identification data matches the second identification data. In some embodiments, the one or more processors are further configured to execute program instructions so that the physiological monitoring system determines the approval status of the request based at least in part on comparing the first identification data with the second identification data. In some embodiments, the one or more processors are further configured to execute program instructions so that if the first identification data matches the second identification data, the physiological monitoring system determines that the request to perform the transfer operation is approved. In some embodiments, the one or more processors are further configured to execute program instructions so that if the user identification of the first identification data matches the user identification of the second identification data, the physiological monitoring system determines that the request to perform the transfer operation is approved. In some embodiments, the monitoring hub communication data includes a device address of the first monitoring hub. In some embodiments, the sensor communication data includes one or more device addresses of one or more sensors. In some embodiments, the one or more processors are also configured to execute program instructions so that the physiological monitoring system communicates the monitoring hub communication data to one or more sensors. In some embodiments, the one or more processors are also configured to execute program instructions so that the physiological monitoring system communicates the sensor communication data to the first monitoring hub. In some embodiments, the one or more processors are also configured to execute program instructions so that the physiological monitoring system accesses historical physiological data. In some embodiments, the one or more processors are also configured to execute program instructions so that the physiological monitoring system communicates historical physiological data to the first monitoring hub.

[0077] Disclosed herein is a method for transferring a wireless connection between a first medical monitoring device and one or more physiological sensors to a wireless connection between a second medical monitoring device and the one or more physiological sensors, the second medical monitoring device being different from the first medical monitoring device, wherein the method comprises: receiving a request to transfer the wireless connection; receiving first identification data with the first medical monitoring device; receiving second identification data with the second medical monitoring device; comparing the second identification data with the first identification data; and, based on the comparison, initiating the transfer of the wireless connection to achieve wireless communication between the one or more physiological sensors and the second medical monitoring device.

[0078] In some embodiments, receiving the request to transfer the wireless connection includes receiving a user input at the first medical monitoring device. In some embodiments, comparing the second identification data to the first identification data is performed by one or more of the following devices: the first medical monitoring device; the second medical monitoring device; the third medical monitoring device; or a server. In some embodiments, initiating the transfer includes receiving communication data associated with each of the one or more physiological sensors with the second medical monitoring device. In some embodiments, initiating the transfer includes transmitting the communication data associated with each of the one or more physiological sensors to the second medical monitoring device. In some embodiments, transmitting the communication data is performed by a server in communication with the first and second medical monitoring devices. In some embodiments, transmitting the communication data is performed by the first medical monitoring device. In some embodiments, initiating the transfer includes receiving communication data associated with the second medical monitoring device with one or more physiological sensors. In some embodiments, initiating the transfer includes transmitting the communication data associated with the second medical monitoring device to each of the one or more physiological sensors. In some embodiments, transmitting the communication data is performed by the first medical monitoring device. In some embodiments: comparing the second identification data to the first identification data includes determining whether the second identification data is associated with the first identification data; and the method includes initiating the transfer of the wireless connection in response to determining that the second identification data is associated with the first identification data. In some embodiments, comparing the second identification data to the first identification data includes determining whether the second identification data matches the first identification data; and the method includes initiating the transfer of the wireless connection in response to determining that the second identification data matches the first identification data. In some embodiments, the first identification data is associated with a user. In some embodiments, the first identification data is associated with a healthcare provider. In some embodiments, the user is not required to terminate the wireless connection between the wireless sensor and the first medical monitoring device. In some embodiments, the first medical monitoring device is directly connected to the second medical monitoring device without using a wired or wireless connection. In some embodiments, the method also includes automatically terminating the wireless connection between the wireless sensor and the first medical monitoring device in response to determining that the second identification data matches the first identification data. In some embodiments, Bluetooth multipoint is not enabled. In some embodiments, the wireless sensor is configured to wirelessly connect to a single medical monitoring device at a time.

[0079] Disclosed herein is a method for transferring a wireless connection between a first medical monitoring device and one or more physiological sensors to a wireless connection between a second medical monitoring device and the one or more physiological sensors, the second medical monitoring device being different from the first medical monitoring device, wherein the method comprises: receiving first information related to the transfer of the wireless connection; receiving second information related to the transfer of the wireless connection; and initiating the transfer of the wireless connection to enable wireless communication between the one or more physiological sensors and the second medical monitoring device based on at least the received first and second information, wherein initiating the transfer does not require a user to terminate the wireless connection between the first medical monitoring device and the one or more physiological sensors.

[0080] In some embodiments, the first information includes first identification data. In some embodiments, the first identification data is associated with a user. In some embodiments, the first identification data is associated with a healthcare provider. In some embodiments, the second information includes second identification data. In some embodiments, the second identification data is associated with a user. In some embodiments, the second identification data is associated with a healthcare provider. In some embodiments, initiating the transfer of the wireless connection includes determining that at least a portion of the first information matches at least a portion of the second information. In some embodiments, initiating the change does not require a user to change a pairing mode of the wireless sensor. In some embodiments, initiating the change does not require a user to turn off the wireless sensor.

[0081] The present invention discloses a mounting assembly for mounting an electronic device to a support surface, the mounting assembly comprising: a first mounting member configured to be fixed to a portion of the electronic device; and a second mounting member configured to be fixed to the support surface. The first mounting member can be configured to be removably fixed to the second mounting member, thereby mounting the electronic device to the support surface.

[0082] In some embodiments, the electronic device is a monitoring hub, such as any monitoring hub disclosed herein, having any of the features and / or functions described with respect to any monitoring hub disclosed herein. In some embodiments, the support surface is a wall. In some embodiments, the support surface is on a support arm fixed to the wall. In some embodiments, the first mount is configured to be fixed to the second mount without the use of screws and / or nails. In some embodiments, the first mount is configured to be fixed to the second mount by inserting a portion of the first mount into a portion of the second mount. In some embodiments, the first mount is configured to be fixed to the second mount by moving the first mount in a first direction relative to the second mount, and wherein the first mount is configured to be removed from the second mount by moving the first mount in a second direction opposite to the first direction relative to the second mount. In some embodiments, the second mount includes one or more fingers configured to engage a portion of the first mount. In some embodiments, the second mount includes a base and the one or more fingers; the one or more fingers extend outwardly from the base so that there is a gap between a portion of each of the one or more fingers and a surface of the base; and the gap is configured to receive the portion of the first mount. In some embodiments, the one or more fingers are configured to vertically support the portion of the first mount. In some embodiments, the one or more fingers form a funnel-shaped pocket that vertically supports the portion of the first mount. In some embodiments, the portion of the first mount vertically supported by the one or more fingers is a portion of the base of the first mount, and the width of the base gradually narrows along at least a portion of the height of the base. In some embodiments, one of the first or second mounts includes a lever configured to move from a first position to a second position; and when the lever is in the first position, the first mount is prevented from disengaging from the second mount. In some embodiments, the second mount includes a lever configured to move from a first position to a second position; when the lever is in the first position, a portion of the lever engages with a portion of the first mount, thereby causing a physical interference that prevents the first mount from being disengaged from the second mount; and when the lever is in the second position, the physical interference is removed. In some embodiments: the lever includes a protrusion, and the first mount includes an opening; when the lever is in the first position, the protrusion of the lever engages with a portion of the first mount proximate to the opening of the first mount, thereby causing the physical interference. In some embodiments, when the lever is in the first position, the protrusion of the lever is at least partially positioned within the opening of the first mount. In some embodiments, when the lever is in the second position, the protrusion of the lever is positioned outside the opening of the first mount.

[0083] Disclosed herein is a bracket for receiving an electronic device, the bracket comprising: a base configured to receive at least a portion of the electronic device; a first arm extending outwardly from the base, the first arm being oriented non-parallel relative to the base, so that when the first arm is positioned on a support surface, the base is oriented non-parallel relative to the support surface; and a second arm extending outwardly from the base and spaced apart from the first arm, the second arm comprising a hook configured to be fixed around a portion of an object.

[0084] In some embodiments, the object is a hospital bed, and the portion comprises a wall or railing of the hospital bed. In some embodiments, the first arm comprises a first end connected to the first portion of the base and a second end connected to the second portion of the base, thereby forming a loop of the support. In some embodiments, the second arm comprises a first end connected to the first portion of the base and a second end connected to the second portion of the base, thereby forming a loop of the support. In some embodiments, the support also includes a rod extending from the first portion of the first arm to the second portion of the first arm, the rod dividing the loop into a first loop portion and a second loop portion. In some embodiments, the first arm is connected to the first end of the base, and the second arm is connected to the second end of the base opposite to the first end of the base. In some embodiments, the support is configured so that when the second arm is wrapped around the top of the support structure and / or rests on the top of the support structure, the first arm contacts the support structure and operably positions the base away from the support structure. In some embodiments, the support is configured so that when the second arm is wrapped around the top of the support structure and / or rests on the top of the support structure, the first arm contacts the support structure and operably positions the base so that the base is oriented substantially parallel to a plane extending along the support structure. In some embodiments, the support structure is generally perpendicular to the ground surface. In some embodiments, the bracket is configured so that when the second arm is wrapped around the top of the support structure and / or rests on the top of the support structure, the first arm contacts the support structure and operably positions the base to be approximately perpendicular to the ground surface. In some embodiments, the bracket is configured so that when the second arm is wrapped around the top of the support structure and / or rests on the top of the support structure, the first arm contacts the support structure and operably positions the base within 30 degrees perpendicular to the ground surface. In some embodiments, the bracket is configured so that when the second arm is wrapped around the top of the support structure and / or rests on the top of the support structure, the first arm contacts the support structure and operably positions the base within 20 degrees perpendicular to the ground surface. In some embodiments, the bracket is configured so that when the second arm is wrapped around the top of the support structure and / or rests on the top of the support structure, the first arm contacts the support structure and operably positions the base within 10 degrees perpendicular to the ground surface.

[0085] Various combinations of the features, embodiments, implementations, and aspects described above and below are also disclosed and contemplated by the present disclosure.

[0086] Additional embodiments of the disclosure are described below with reference to the appended claims, which may serve as an additional summary of the disclosure.

[0087] In various embodiments, a system and / or computer system is disclosed, which includes a computer-readable storage medium and one or more processors, wherein the computer-readable storage medium has program instructions contained therewith, and the one or more processors are configured to execute the program instructions to cause the system and / or computer system to perform operations including one or more aspects of the above-mentioned and / or following embodiments (including one or more aspects of the appended claims).

[0088] In various embodiments, methods and / or computer-implemented methods are disclosed in which one or more aspects of the above and / or below described embodiments (including one or more aspects of the appended claims) are implemented and / or performed by one or more processors executing program instructions.

[0089] In various embodiments, a computer program product is disclosed that includes a computer-readable storage medium having program instructions contained therewith, the program instructions being executable by one or more processors to cause the one or more processors to perform operations including one or more aspects of the above-described and / or below-described embodiments (including one or more aspects of the appended claims). BRIEF DESCRIPTION OF THE DRAWINGS

[0091] Various embodiments will be described below with reference to the accompanying drawings. These embodiments are illustrated and described only by way of example and are not intended to limit the scope of the present disclosure. In the accompanying drawings, the same elements may have the same reference numerals.

[0092] Figure 1A-1B is a schematic block diagram illustrating an example implementation of a physiological monitoring system (PMS).

[0093] Figure 1C An example implementation of a physiological monitoring system (PMS) is shown.

[0094] Figure 1D is a schematic block diagram illustrating an embodiment of an example physiological monitoring system (PMS).

[0095] Figure 2 is a block diagram illustrating an example implementation of a monitoring hub of a physiological monitoring system (PMS).

[0096] Figure 3A-3B is a perspective view of an example monitoring hub.

[0097] Figure 4 An example process for transferring physiological monitoring from one monitoring hub to another is shown.

[0098] Figures 5A-5D is a flow chart illustrating an example process associated with transferring physiological monitoring from a source monitoring hub to a target monitoring hub.

[0099] Figure 5E is a flow chart illustrating an example process for monitoring the location of an object.

[0100] Figure 6 An example implementation of a monitoring hub is shown.

[0101] Fig. 7A Shown is a front perspective view of a monitoring hub according to aspects of the present disclosure.

[0102] Figure 7B-7C According to aspects of the present disclosure, Fig. 7A Rear and top perspective views of the monitoring hub.

[0103] Figure 7D-7E According to aspects of the present disclosure, Fig. 7A Rear and bottom perspective view of the monitoring hub.

[0104] Figure 7F-7K (respectively) show aspects according to the present disclosure Fig. 7A Front view, rear view, top view, bottom view, left view and right view of the monitoring hub.

[0105] Figures 8A-8B According to aspects of the present disclosure, Fig. 7A View of the monitoring hub and bracket.

[0106] Figure 8C shows the separation of aspects according to the present disclosure from each other Fig. 7A Monitoring center and Figures 8A-8B bracket.

[0107] Figures 8D-8E According to aspects of the present disclosure, Figures 8A-8B Front and top perspective views of the bracket.

[0108] Figure 8F-8I According to aspects of the present disclosure, Figures 8A-8B Rear perspective view of the bracket.

[0109] Figure 8J-8O (respectively) show aspects according to the present disclosure Figures 8A-8B Front view, back view, left side view, right side view, top view and bottom view of the bracket.

[0110] Figures 9A-9B According to aspects of the present disclosure, Fig. 7A Monitoring hub and installation components.

[0111] Figure 9C-9D According to aspects of the present disclosure, Figures 9A-9B Installation components.

[0112] Figures 9E-9F (respectively) show the connection to Fig. 7A The monitoring center Figures 9A-9B A rear perspective view and a rear view of the mounting member of the mounting assembly.

[0113] Figure 9G-9I A monitoring hub and a Figures 9A-9B How the mounting components can be connected.

[0114] Figure 9J A monitoring hub and a Figures 9A-9B The mounting components are connected together.

[0115] Figure 9K-9M FIG. 1 shows a configuration of a connection according to aspects of the present disclosure. Figures 9A-9B The installation components are shown without displaying the monitoring hub.

[0116] Figures 10A-10B According to aspects of the present disclosure, Fig. 7A Another embodiment of a monitoring hub and mounting assembly.

[0117] Figures 10C-10D According to aspects of the present disclosure, Figures 10A-10B Installation components.

[0118] Figures 10E-10F (respectively) show the connection to Fig. 7A The monitoring center Figures 10A-10B A rear perspective view and a rear view of the mounting member of the mounting assembly.

[0119] Figure 10G A monitoring hub and a Figures 10A-10B How the mounting components can be connected.

[0120] Fig. 10H A monitoring hub and a Figures 10A-10B The mounting components are connected together.

[0121] Figures 10I-10KFIG. 1 shows a configuration of a connection according to aspects of the present disclosure. Figures 10A-10B The installation components are displayed without the monitoring hub.

[0122] Figures 11A-11C Shown are front, rear and side views (respectively) of another embodiment of a monitoring hub according to aspects of the present disclosure.

[0123] Fig. 12A Shown is a front perspective view of a monitoring hub according to aspects of the present disclosure.

[0124] Fig. 12B Shown is a side perspective view of a monitoring hub according to aspects of the present disclosure.

[0125] Figures 12C-12D According to aspects of the present disclosure, Fig. 12A Rear and top perspective views of the monitoring hub.

[0126] Figures 12E-12F The present disclosure shows Fig. 12A Rear and bottom perspective view of the monitoring hub.

[0127] Figure 12G-12L (respectively) show aspects according to the present disclosure Fig. 12A Front view, rear view, top view, bottom view, left view and right view of the monitoring hub.

[0128] Figure 12M According to aspects of the present disclosure, Fig. 12A Rear perspective exploded view of the monitoring center.

[0129] Details

[0130] Although certain embodiments, implementations and examples are disclosed below, the subject matter of the present invention extends beyond the specifically disclosed embodiments to other optional embodiments and / or uses and modifications and equivalents thereof. Therefore, the scope of the appended claims is not limited to any specific embodiment described below. For example, in any method or process disclosed herein, the actions or operations of the method or process may be performed in any appropriate order and are not necessarily limited to any specific disclosed order. Various operations may be described as multiple discrete operations in sequence in a manner that may help understand certain embodiments; however, the order of description should not be interpreted as implying that these operations are sequence-dependent. In addition, the structures, systems and / or devices described herein may be embodied as integrated components or separate components. For the purpose of comparing various embodiments, certain aspects and advantages of these embodiments are described. Not all such aspects or advantages are necessarily achieved by any particular embodiment. Therefore, for example, various embodiments may be performed in a manner that achieves or optimizes an advantage or a set of advantages as taught herein without having to achieve other aspects or advantages that may also be taught or inspired herein.

[0131] Overview

[0132] A physiological monitoring system (PMS) can monitor a patient or object, including the physiological data of the object. One or more physiological sensors can be connected to the object and can obtain the physiological data of the object. One or more sensors can communicate the physiological data to a monitoring hub, which can display markers of the physiological data. A user may desire to use another monitoring hub to monitor the object in order to receive and display the physiological data obtained from the sensor. The user can request the PMS to transfer physiological monitoring from an initial monitoring hub to another monitoring hub. This article describes systems, devices, processes, etc. for transferring physiological monitoring of a PMS from one monitoring hub to another monitoring hub, and it can provide many benefits including improved physiological monitoring, improved health care services, etc.

[0133] Advantageously, the systems, devices, and processes described herein can facilitate faster, simpler, and more efficient transfer of physiological monitoring from one monitoring hub to another. For example, a user may be able to transfer physiological monitoring from one monitoring hub to another without having to unplug, plug in, and / or reinsert cables, lines, etc. of the monitoring hubs and / or physiological sensors. As another example, a user may be able to transfer physiological monitoring from one monitoring hub to another without having to turn off and / or turn on devices, such as physiological sensors, connected to the monitoring hubs. As another example, a user may be able to transfer physiological monitoring from one monitoring hub to another without having to implement a time-consuming wireless pairing process. As another example, the PMS provides an intuitive and easy-to-use system for transferring physiological monitoring, which can reduce the time that healthcare providers must spend on supervising the physiological monitoring of a subject and can improve the quality of healthcare services provided to the subject.

[0134] Advantageously, the systems, devices, and processes described herein can reduce and / or eliminate data loss while transferring physiological monitoring from one monitoring hub to another. For example, a PMS can be configured to continuously monitor the physiology of a subject while transferring physiological monitoring from one monitoring hub to another. The PMS can be configured to retain (e.g., store) physiological data obtained from sensors before, during, and / or after transferring physiological monitoring between monitoring hubs. The PMS can be configured to exchange physiological data between monitoring hubs to allow a user to view historical physiological data combined with current or real-time physiological data. For example, a monitoring hub of a PMS can be configured to display real-time physiological data received from a sensor in addition to historical physiological data, which historical physiological data was received from the sensor by another monitoring hub before transferring physiological monitoring, as if the monitoring hub had monitored the subject the entire time and had received all physiological data directly from the sensor.

[0135] Advantageously, the systems, devices, and processes described herein for transferring physiological monitoring of a PMS can improve patient mobility. For example, a PMS can facilitate simple, rapid, and efficient transfer of physiological monitoring from one monitoring hub (which can be located in a fixed location, such as a ward in a hospital) to another monitoring hub (e.g., a portable monitoring hub) while continuing to monitor the patient, which can allow the patient to be relocated to a different location, such as a different room in a hospital. In addition, as the patient moves within an environment, such as a hospital, the PMS can facilitate automatic wireless communication between sensors connected to the patient and monitoring hubs near the patient. For example, when a patient walks around in an environment with multiple monitoring hubs, sensors connected to the patient can automatically establish a wireless connection, such as a Bluetooth connection, with the nearest monitoring hub.

[0136] Advantageously, the systems, devices, and processes described herein can improve patient location tracking. For example, a PMS can monitor a patient's location (e.g., within a hospital) by identifying which monitoring hub is wirelessly connected to a sensor attached to the patient. As the patient moves within the environment, the sensors connected to the patient can wirelessly connect to and / or communicate with various monitoring hubs, such as monitoring hubs that are in close proximity to the sensors. Thus, the PMS can track the patient's location, which can improve the quality of healthcare provided to the patient by quickly and efficiently knowing the patient's location at all times, such as whether the patient is in a particular part of the hospital (e.g., an operating room) where they should or have been assigned or scheduled.

[0137] Advantageously, the systems, devices, and processes described herein for transferring physiological monitoring of a PMS can facilitate the removal, addition, replacement, and / or exchange of monitoring hubs within a PMS (such as, for example, when a monitoring hub is low on battery power and should be replaced by another monitoring hub) to continue monitoring a subject, which can, for example, improve PMS performance as well as healthcare services.

[0138] Advantageously, the systems, devices, and processes described herein for transferring physiological monitoring of a PMS can improve quality control of healthcare services. For example, a PMS can be configured to verify permissions associated with a user requesting to transfer physiological monitoring from one monitoring hub to another monitoring hub. For example, a PMS can be configured to deny a request to transfer physiological monitoring from a healthcare provider who does not have permission to relocate a monitored subject and / or a healthcare provider who is not assigned to provide healthcare to a subject.

[0139] Advantageously, the systems, devices, and processes described herein can improve the accuracy of transferring physiological monitoring from one monitoring hub to another monitoring hub. For example, the PMS can be configured to verify the requesting user ID at a first monitoring hub and a subsequent monitoring hub to ensure that the user IDs correspond (e.g., match), which can ensure that the PMS transfers the physiological monitoring to the correct monitoring hub (e.g., to a monitoring with a requesting user ID that matches the requesting user ID of the initial monitoring hub), which can advantageously improve the accuracy and precision of transfers in systems with multiple monitoring hubs and / or multiple transfer requests occurring simultaneously or nearly simultaneously.

[0140] To aid in understanding the systems and methods discussed herein, several terms are described below. These terms, as well as other terms used herein, should be interpreted to include the descriptions provided, the ordinary and customary meanings of the terms, and / or any other implicit meanings of the corresponding terms, where such interpretations are consistent with the context of the terms. Therefore, the descriptions below do not limit the meanings of these terms, but only provide example descriptions.

[0141] In some embodiments, sensor Wearable devices may be included. The sensor may include a wireless wearable device. The wearable device may include one or more sensors. The wearable device may include a wearable hub that communicates with one or more sensors. The sensor may include an ear device, such as an earbud headset, an earhook headset, a headset, an in-ear headset, etc. The sensor may include a wrist-worn device, such as a smart watch. The sensor may include a physiological sensor. The sensor may collect physiological data from the object, such as ECG data, EEG data, blood oxygenation data, heart rate data, pulse data, breathing data, blood pressure data, motion data, orientation data, temperature data, etc. The sensor may be connected to the object. The sensor may be attached to the object. The sensor may be worn by the object. The sensor may be worn by the object. The sensor may be fixed to the object by adhesion. The sensor may be fixed to the object by one or more straps. The sensor may be worn on and / or attached to the finger, wrist, arm, forearm, head, forehead, ear, chest, back, trunk, abdomen, leg, ankle, foot, toe or other body part of the object. Multiple sensors may be arranged in the same housing or device. The sensor may be provided in a separate housing or device.

[0142] In some embodiments, Monitoring Center An electronic device configured to facilitate physiological monitoring of a patient may be included. The monitoring hub may display markers corresponding to the patient's physiological data. The monitoring hub may be mobile. The monitoring hub may be portable. The monitoring hub may include a handheld device. The monitoring hub may be carried by a user. The monitoring hub may be mounted on a wall. The monitoring hub may include an indoor display. The monitoring hub may be fixed. The monitoring hub may be located in a fixed position. The monitoring hub may include a tablet, a monitor, a PC, a phone, a wearable device (e.g., a smart watch), etc. The monitoring hub may communicate with one or more remote computing devices via one or more wireless communication protocols. The monitoring hub may communicate with a remote server. The monitoring hub may communicate with one or more sensors. The monitoring hub may also be referred to herein as a hub, an electronic device, a display device, a monitoring device, etc.

[0143] In some embodiments, Source Monitoring Center Can refer to a monitoring hub that communicates wirelessly with one or more sensors before transferring physiological monitoring to another monitoring hub. A source monitoring hub can include any example monitoring hub shown and / or described herein, including the structural and / or operational features of any example monitoring hub shown and / or described herein. A source monitoring hub may also be referred to herein as a first monitoring hub, an initial monitoring hub, etc.

[0144] In some embodiments, Target Monitoring CenterMay refer to a monitoring hub that wirelessly communicates with one or more sensors after transferring physiological monitoring from another monitoring hub. The target monitoring hub may include any example monitoring hub shown and / or described herein, including the structure and / or operating characteristics of any example monitoring hub shown and / or described herein. The target monitoring hub may also be referred to herein as a second monitoring hub, a subsequent monitoring hub, another monitoring hub, etc.

[0145] The target monitoring hub may include a monitoring hub of a different type than the source monitoring hub. For example, one of the target monitoring hub or the source monitoring hub may include a mobile monitoring hub, while the other of the target monitoring hub or the source monitoring hub includes a fixed-position monitoring hub, such as a wall-mounted monitoring hub or an indoor monitoring hub. The target monitoring hub may include a monitoring hub of the same type as the source monitoring hub. For example, both the target monitoring hub and the source monitoring hub may include a mobile monitoring hub.

[0146] In some embodiments, “ Metastatic Physiological Monitoring " can refer to transferring the monitoring, display and / or collection of physiological data from a source monitoring hub to a target monitoring hub. Transferring physiological monitoring may include transferring the wireless connection between the sensor and the source monitoring hub to the sensor and the target monitoring hub. Transferring physiological monitoring may include updating or changing the wireless connection of the physiological sensor and / or updating or changing the wireless connection of the monitoring hub. Transferring physiological monitoring may include terminating the wireless communication between the source monitoring hub and the sensor. Transferring physiological monitoring may include establishing wireless communication between the target monitoring hub and the sensor. In some embodiments, transferring physiological monitoring may include transferring less than all wireless connections from the source monitoring hub to the target monitoring hub. In some embodiments, transferring physiological monitoring may include transferring all wireless connections from the source monitoring hub to the target monitoring hub.

[0147] In some embodiments, Transfer Request A request to transfer physiological monitoring from a source monitoring hub to a target monitoring hub may be included. The transfer request may be received via user input at the monitoring hub. For example, a user may press a button on one or more monitoring hubs to initiate a transfer request. In some embodiments, the transfer request may include contactless or minimal contact user input, such as a wireless communication signal, facial recognition, eye recognition, fingerprint recognition, gesture recognition, voice recognition, etc. The transfer request may be received at a location and / or computing device remote from the monitoring hub. The transfer request may initiate a transfer of physiological monitoring.

[0148] In some embodiments, Identification dataThe data generated and / or received via the monitoring hub when transferring physiological monitoring may be included. The identification data may include data associated with the user and can be used to identify the user. The identification data may include a user ID. The identification data may include a label, a marker, a serial number, a barcode, a QR code, facial recognition, fingerprint recognition, voice recognition, eye recognition, gesture recognition, etc. The identification data may be unique to the user. The identification data may be unique to a group of users (and may be the same for individuals within the group). The identification data may be used to identify the group to which the user belongs. The identification data may include or indicate permissions associated with the user, such as permission or authorization to transfer physiological monitoring. The identification data may include a reason for requesting a transfer (e.g., provided by the requesting user). A computing device (e.g., a monitoring hub) may receive the identification data via one or more wireless communication protocols such as near field communication (NFC) or radio frequency identification (RFID). For example, a user may place a badge configured for wireless communication near the monitoring hub so that it is detected by the monitoring hub. A computing device such as a monitoring hub may receive the identification data via manual user input at the monitoring hub. For example, a user may enter their identification data at the monitoring hub via a keyboard, user interface, touch screen, etc. A computing device such as a monitoring hub may receive identification data via one or more biomarkers. For example, a user may scan their fingers, eyes, face, or speak as their identification data to be authenticated at the monitoring hub. The identification data may be connected or paired with a transfer request.

[0149] In some embodiments, Transfer Request Status The status of a request to transfer physiological monitoring may be indicated. The transfer request status may include an approved or disapproved status. In some embodiments, the transfer request may be approved if the identification data from the first monitoring hub matches the identification data from the second monitoring hub. The transfer request may be approved if the requesting user has the appropriate authority to perform the transfer. In some embodiments, the transfer request may not be approved if the identification data from the first monitoring hub does not match the identification data from the second monitoring hub. The transfer request may not be approved if the requesting user does not have the appropriate authority to perform the transfer.

[0150] In some embodiments, Wireless communication configuration dataData for establishing wireless communication between one or more computing devices may be included. For example, a monitoring hub and a sensor may implement wireless communication configuration data to communicate with each other via one or more wireless communication protocols. The wireless communication configuration data may include, for example, the device address of one or more computing devices of the monitoring hub and / or sensor. The wireless communication configuration data may include access codes, such as one or more inquiry access codes (IACs), device access codes (DACs), and channel access codes (CACs). The access code may include and / or be derived from the device address. The wireless communication configuration data may include a link key. The wireless communication configuration data may include clock data, such as the frequency at which the computing device will communicate (e.g., transmit data). The wireless communication configuration data may also be referred to herein as wireless communication data or communication data or wireless configuration data or configuration data.

[0151] In some embodiments, Device Address Wireless communication between computing devices may be facilitated. A device address may be associated with a computing device. The device address may be unique to the computing device. The device address may include an IP address. The device address may include a MAC address. The device address may include a serial ID associated with the computing device. The device address may include a Bluetooth address (BD_ADDR). The device address may include a LAP value. The device address or a derivative thereof may form at least a portion of the access code.

[0152] In some embodiments, Link Key A link key may facilitate wireless communication between computing devices. A link key may enable one or more computing devices to authenticate each other. A link key may encrypt data wirelessly exchanged between one or more computing devices. A link key may include a long-term key (LTK).

[0153] In some embodiments, Physiological dataData generated by one or more sensors may be included. Physiological data may correspond to an object. Physiological data may include raw data, partially processed data, and / or fully processed data. Physiological data may include physiological parameters. As non-limiting examples, physiological data may include data related to heart rate, respiratory rate, blood pressure, blood oxygen saturation, hemoglobin content, ECG, EEG, body temperature, object orientation, object position, object movement. Physiological data may include historical physiological data. Historical physiological data may include physiological data generated by a sensor within a time frame before the current time. Historical physiological data may include data corresponding to a time frame of less than 24 hours, less than 12 hours, less than 1 hour, less than 30 minutes, less than 10 minutes, less than 5 minutes, less than 2 minutes, less than 1 minute, less than 30 seconds, less than 15 seconds, less than 10 seconds, less than 5 seconds, or less than 1 second. Physiological data may include real-time physiological data. Real-time physiological data may include physiological data transmitted and / or received at a time substantially similar to the time when the physiological data was generated by the sensor, for example, so that any time difference may be imperceptible to human senses.

[0154] Example System

[0155] Figure 1A 1 is a schematic block diagram illustrating an example implementation of a physiological monitoring system (PMS) 150. PMS 150 may include a monitoring hub 100A, a monitoring hub 100B, one or more sensors 102 (e.g., sensors 102A, 102B, 102C), a network 104, and one or more servers 106. In some implementations, PMS 150 may include only two monitoring hubs (e.g., hubs 100A, 100B). In some implementations, PMS 150 may include more than two monitoring hubs. In some implementations, PMS 150 may include only one monitoring hub.

[0156] The monitoring hub 100A can communicate with one or more sensors 102. In some embodiments, the monitoring hub 100A can communicate with one or more sensors 102 via a wireless communication protocol (e.g., WiFi, Bluetooth, near field communication (NFC), radio frequency identification (RFID), cellular, 1G, 2G, 3G, 4G, 5G and / or Zigbee). In some embodiments, the sensor 102 can be a "slave" in a master-slave communication relationship (e.g., Bluetooth communication protocol) with the monitoring hub 100A. In some embodiments, the sensor 102 can communicate with only one device (e.g., a "master" device), such as a monitoring hub, at a time. The monitoring hub 100A can communicate data to one or more sensors 102 and / or receive data from one or more sensors 102. For example, the monitoring hub 100A can receive physiological data from one or more sensors 102. As another example, the monitoring hub 100A may receive communication data (e.g., device addresses of one or more sensors 102) from one or more sensors 102 and / or communicate communication data (e.g., device addresses of the monitoring hubs 100A, 100B) to one or more sensors 102. Figure 1A In the example embodiment shown, the monitoring hub 100B has not yet established direct wireless communication with the one or more sensors 102 .

[0157] The monitoring hubs 100A, 100B may communicate with the server 106 via a network 104. The network 104 may include any one or more communication networks, such as the Internet. The network 104 may include any combination of networks, such as a personal area network (PAN), a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), etc. Thus, the various components of the PMS 150 may communicate directly or indirectly with each other via any appropriate communication connection and / or network (e.g., the network 104 (e.g., one or more communication connections, one or more computer networks, one or more wired or wireless connections, the Internet, any combination of the foregoing, etc.)). Similarly, in various embodiments, the various components of the PMS 150 (e.g., as described below) may communicate directly or indirectly with each other via any appropriate communication connection (e.g., one or more communication connections, one or more computer networks, one or more wired or wireless connections, the Internet, any combination of the foregoing, etc.). The monitoring hubs 100A, 100B may communicate data to and / or receive data from the server 106 via the network 104, including communication data (e.g., device addresses and / or link keys corresponding to the sensors 102 and / or the monitoring hub 100), physiological data, identification data (user ID), transfer requests, request approval status, etc. The monitoring hubs 100A, 100B may communicate with the server 106 via any combination of wireless communication protocols, including, for example, WiFi, Bluetooth, near field communication (NFC), radio frequency identification (RFID), cellular, 1G, 2G, 3G, 4G, 5G, and / or Zigbee. In some embodiments, the monitoring hub 100 may communicate with the server 106 via different wireless communication protocols that communicate with it and one or more sensors 102. For example, the monitoring hub 100 may communicate with the server 106 via a first wireless communication protocol (e.g., WiFi), and may communicate with one or more sensors 102 via a second wireless communication protocol (e.g., Bluetooth).

[0158] In some embodiments, the sensor 102 can optionally communicate with the server 106 via the network 104. For example, the sensor 102 can communicate physiological data to the server 106 and / or receive communication data (e.g., the device address of the monitoring hub) from the server 106. In some embodiments, the sensor 102 may not communicate directly with the server 106. In some embodiments, data can be transmitted from the sensor 102 to the server 106 via the monitoring hub 100, and vice versa.

[0159] In some embodiments, the monitoring hub 100A can be portable or mobile. For example, the monitoring hub 100A can be resized, shaped, and / or include a housing or casing to facilitate carrying the monitoring hub 100A, for example, by hand. In some embodiments, the monitoring hub 100A can be stationary or fixed in one position. For example, the monitoring hub 100A can be mounted to a wall. In some embodiments, the monitoring hub 100B can include similar structures and / or operating features to the monitoring hub 100A. The monitoring hub 100A can be referred to as a source monitoring hub. The monitoring hub 100B can be referred to as a target monitoring hub herein.

[0160] The one or more sensors 102 may include various types of sensors configured to collect physiological data of the object. The one or more sensors 102 may be attached or connected to different parts of the object, such as but not limited to arms, legs, torso, chest, head, neck, fingers, forehead, etc. The one or more sensors 102 may collect patient physiological data, including but not limited to data related to heart rate, respiratory rate, blood pressure, blood oxygen saturation, hemoglobin content, ECG, EEG, body temperature, object orientation, object position, object movement (as a non-limiting example), etc. When the one or more sensors 102 collect data, the one or more sensors 102 may transmit the physiological data to the monitoring hub 100A, the monitoring hub 100B and / or the server 106 in real time. In some embodiments, the one or more sensors 102 may include a processor that may process the data obtained by the sensor 102 in whole or in part.

[0161] The server 106 may include one or more computing devices including one or more hardware processors. The server 106 may include program instructions configured to cause the server 106 to perform one or more operations when executed by the hardware processor. The server 106 may include and / or may access (e.g., communicate with) a database or storage component or storage system, which may include any computer-readable storage medium and / or device (or a collection of data storage media and / or devices), including but not limited to one or more memory devices that store data, including but not limited to dynamic and / or static random access memory (RAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), optical disks (e.g., CD-ROM, DVD-ROM, etc.), magnetic disks (e.g., hard disk, floppy disk, etc.), memory circuits (e.g., solid-state drive, random access memory (RAM), etc.), etc. In some embodiments, the server 106 may include and / or communicate with a hosted storage environment, which includes a collection of physical data storage devices that may be remotely accessible and can be quickly provided as needed (commonly referred to as "cloud" storage). The data stored in and / or accessible by the server 106 may include physiological data and / or communication data, wherein the physiological data includes historical physiological data previously obtained by one or more sensors 102, and the communication data includes, for example, a link key and / or a device address associated with a monitoring hub, a sensor, etc.

[0162] In some embodiments, the network 104 may include and / or communicate with an electronic medical record (EMR). In some embodiments, the server 106 may include and / or communicate with an EMR. In some embodiments, one or more of the monitoring hubs 100A, 100B may communicate with an EMR. The EMR may include a proprietary EMR. The EMR may include an EMR associated with a hospital. The EMR may store data including medical records.

[0163] Figure 1B is a schematic block diagram illustrating additional example implementations of a physiological monitoring system (PMS) 150 . Figure 1B The example implementation shown in can be generated by a request to transfer physiological monitoring from monitoring hub 100A to monitoring hub 100B. Transferring physiological monitoring from one monitoring hub to another monitoring hub is described herein, for example, with reference to at least Figure 4 and / or Figures 5A-5E For example, Figure 1AAs shown in the example embodiment of , the sensor 102 may communicate with the monitoring hub 100A and may not communicate with the monitoring hub 100B. The PMS 150 may transfer physiological monitoring from the monitoring hub 100A to the monitoring hub 100B (e.g., in response to a user request). Figure 1B As shown, after the PMS 150 has transferred physiological monitoring from the monitoring hub 100A to the monitoring hub 100B, the sensor 102 may communicate with the monitoring hub 100B and may not communicate with the monitoring hub 100A. The monitoring hub 100B may receive and / or display physiological data received from the sensor 102 via a wireless communication connection (e.g., Bluetooth and / or other wireless communication protocols) established with the sensor 102 as a result of the transfer.

[0164] The monitoring hub 100A, 100B can receive user input 108. The user input 108 can include identification data and / or a transfer request. The user input 108 can be, for example, a manual user input via a display of the monitoring hub 100A, 100B or via one or more buttons of the monitoring hub 100A, 100B. For example, a user can press a button of the monitoring hub 100A, 100B to request a transfer. The user input 108 can include electronic input, such as an electronic signal generated in response to a wireless communication protocol. For example, a user can bring a communication device (e.g., a user ID badge) into the vicinity of the monitoring hub 100A, 100B to generate an electronic signal at the monitoring hub 100A, 100B (e.g., via NFC and / or RFID).

[0165] In some embodiments, the monitoring hub 100A may optionally communicate with the monitoring hub 100B. In some embodiments, the monitoring hub 100A may communicate with the monitoring hub 100B via a wireless communication protocol (e.g., WiFi, Bluetooth, near field communication (NFC), radio frequency identification (RFID), cellular, 1G, 2G, 3G, 4G, 5G, and / or Zigbee). The monitoring hub 100A may communicate data to and / or receive data from the monitoring hub 100B, including communication data (e.g., device address of the sensor 102), physiological data, identification data (e.g., user ID), transfer request, request approval status, etc. In some embodiments, the monitoring hub 100A may communicate with the monitoring hub 100B only when the PMS 150 transfers physiological monitoring from the monitoring hub 100A to the monitoring hub 100B. For example, in some embodiments, monitoring hub 100A may communicate with monitoring hub 100B only until the transfer is complete, monitoring hub 100B has established communication with sensor 102, etc. In some embodiments, monitoring hub 100A may communicate with monitoring hub 100B to facilitate the transfer (e.g., communication data may be transmitted to facilitate establishing communication between monitoring hub 100B and sensor 102). In some embodiments, monitoring hub 100A may not communicate with monitoring hub 100B.

[0166] Figure 1C An example implementation of a physiological monitoring system (PMS) is shown, which includes a monitoring hub 110A, a monitoring hub 110B, and one or more sensors 122. Figure 1C The PMS or portions thereof shown and discussed herein may include Figure 1A-1B The monitoring hub 110A may include structural and / or operational features similar to those of the PMS 150 or portions thereof shown and / or discussed in the accompanying drawings. Figure 1A-1B As another example, monitoring hub 110B may include a monitoring hub 110A having similar structural and / or operational features as discussed in Figure 1A-1B As another example, one or more sensors 122 may include a monitoring hub 100B having similar structure and / or operating features as discussed in Figure 1A-1B Similar structural and / or operating features to the sensor 102 discussed in .

[0167] As shown in this example embodiment, monitoring hub 110A is monitoring the physiological data of subject 111 , and monitoring hub 110B is not monitoring the physiological data of subject 111 .

[0168] The one or more sensors 122 may be configured to obtain physiological data of the subject 111. The monitoring hub 110A is in electrical communication with the one or more sensors 122. In some embodiments, the electrical communication between the monitoring hub 110A and the one or more sensors 122 may include a wireless communication protocol, such as Bluetooth. The monitoring hub 110A receives physiological data from the one or more sensors 122 (e.g., in real time as the data is generated by the one or more sensors 122). The monitoring hub 110A displays indicia of the physiological data and / or information related thereto on a display of the monitoring hub 110A.

[0169] The monitoring hub 110B is not in electrical communication with the sensors 122. The monitoring hub 110B does not receive or display physiological data from the sensors 122. A user, such as a healthcare provider (e.g., a doctor, nurse, etc.), may desire to transfer physiological monitoring from the monitoring hub 110A to the monitoring hub 110B. As described in more detail herein, the user may transfer physiological monitoring from the monitoring hub 110A to the monitoring hub 110B such that the monitoring hub 110B will receive and display physiological data from one or more sensors 122, and the monitoring hub 110A will stop receiving and / or displaying physiological data from one or more sensors 122. After transferring physiological monitoring, the monitoring hub 110B may display indicia of the physiological data previously displayed on the monitoring hub 110A. The monitoring hub 110B may display a user interface that is similar or identical in whole or in part to a user interface previously displayed by the monitoring hub 110A.

[0170] The one or more sensors 122 may include any number and / or type of sensors. The one or more sensors 122 may include an ear device 123, such as an earbud headset, an earhook headset, etc. The one or more sensors 122 may include an ECG device 113, which may include one or more ECG electrodes 112 and / or be connected to one or more ECG electrodes 112. The one or more sensors 122 may include a temperature sensor 114. The one or more sensors 122 may include a motion sensor 115, which may include one or more of a position sensor, a motion sensor, a gyroscope, an accelerometer, etc. The one or more sensors 122 may include an acoustic sensor 116. The one or more sensors 122 may include a wearable device 113, such as a smart device, which may include a watch. The wearable device 113 may include one or more sensors. The one or more sensors 122 may include an optical sensor 140, which may include a finger sensor. The one or more sensors 122 may include a blood pressure monitor 121. The one or more sensors 122 may include a wearable hub 130. The wearable hub 130 can be connected to one or more sensors shown and / or described herein. The wearable hub 130 can communicate with one or more sensors shown and / or described herein. The wearable hub 130 can receive data from one or more sensors shown and / or described herein. In some embodiments, the wearable hub 130 can communicate with the monitoring hub 110A and / or the monitoring hub 110B. In some embodiments, the wearable hub 130 can collect sensor data from one or more sensors and communicate the sensor data to the monitoring hub 110A and / or the monitoring hub 110B. In some embodiments, one or more sensors shown and / or described herein can communicate directly with the monitoring hub 110A and / or the monitoring hub 110B. For example, the wearable device 113, the ear device 123, the optical sensor 140, the ECG device 113, the acoustic sensor 116, the temperature sensor 114, the motion sensor 115, and the blood pressure monitor 121 can communicate directly with the monitoring hub 110A and / or the monitoring hub 110B, for example via wireless communication. In some embodiments, the one or more sensors may include one or more of an infusion pump, a brain monitoring device, a depth of consciousness device, or a pacemaker.

[0171] The monitoring hub 110A is shown in a fixed position (e.g., mounted to a wall). The monitoring hub 110A can be removably mounted to a wall. The monitoring hub 110B is shown resting on a surface adjacent to the object 111 and can be portable or mobile (e.g., not fixed to a specific location). The monitoring hub 110B is housed in a bracket 132. The bracket 132 is configured to support the monitoring hub in an upright position. In some embodiments, the monitoring hub 110B can be fixed or removably fixed to a specific location. For example, the monitoring hub 110B can be connected to a structure such as a bed via the bracket 132. In some embodiments, the monitoring hub 110A can be portable or mobile. In some embodiments, the monitoring hub 110A can be housed in a bracket similar to or identical to the bracket 132.

[0172] Figure 1D 1 is a schematic block diagram illustrating an embodiment of an example physiological monitoring system (PMS) 160. PMS 160 may include features similar to other PMS discussed herein, such as Figure 1A-1B PMS 150 shown and / or discussed. The operations, processes, functions of PMS 160 may be performed by one or more computing devices (e.g., hardware processors of computing devices), such as any computing device discussed herein, such as a monitoring hub, sensor, and / or server.

[0173] PMS 160 may receive one or more inputs. PMS 160 may receive transfer request 162. PMS 160 may receive a transfer request 162 as described in more detail elsewhere herein, e.g., with reference to Figure 4 One or more monitoring hubs shown and / or discussed receive the transfer request 162. The PMS 160 may receive the identification data 164. The PMS may communicate with the PMS via a communication channel as described in greater detail elsewhere herein, such as with reference to Figure 4 One or more monitoring hubs shown and / or discussed receive identification data 164 .

[0174] The PMS 160 can receive and / or access physiological data 166. The PMS 160 can receive the physiological data 166 from one or more physiological sensors. In some embodiments, a monitoring hub of the PMS 160 can receive the physiological data 166 in real time and / or directly from the one or more sensors. In some embodiments, a server of the PMS 160 can receive the physiological data 166 in real time and / or directly from the one or more sensors. In some embodiments, the monitoring hub of the PMS 160 can transmit the physiological data 166 to the server of the PMS 160 after it has been received from the sensors.

[0175] The PMS 160 may receive and / or access communication data 168. The communication data may include data that facilitates establishing communications between computing devices. The communication data may include a device address of a computing device, such as a device address of a monitoring hub and / or a physiological sensor. The PMS 168 may access the communication data 168 of a computing device from the computing device. The PMS may transmit communication data 168 between computing devices of the PMS 168, such as between a monitoring hub, a sensor, and / or a server.

[0176] PMS 160 can process one or more inputs (e.g., inputs 162, 164, 166, 168) to produce outputs. As described in more detail elsewhere herein, such as with respect to Figures 5A-5E As shown and / or discussed, the PMS 160 may process the inputs. The PMS 160 may output a transfer physiological monitoring operation 169 in response to receiving and / or processing one or more inputs. The transfer physiological monitoring operation 169 may include transferring physiological monitoring from one monitoring hub of the PMS 160 to another monitoring hub of the PMS 160. The transfer physiological monitoring operation 169 may be described in more detail elsewhere herein, for example with respect to Figures 5A-5E shown and / or discussed.

[0177] Example Implementations

[0178] Figure 2 2 is a block diagram illustrating an example implementation of a monitoring hub 200. The monitoring hub 200 may include any other example monitoring hubs shown and / or discussed herein, such as Figure 1A The monitoring hubs 100A, 100B discussed in the drawings have similar structural and / or operational features.

[0179] As shown, the monitoring hub 200 may include a hardware processor 201, a storage component 205, a communication component 207, and a battery 203. The hardware processor 201 may be configured, among other things, to process data, execute program instructions to perform one or more functions, and / or control the operation of the monitoring hub 200. For example, the hardware processor 201 may process physiological data obtained from a physiological sensor, and may execute instructions to perform functions related to storing and / or transmitting such physiological data. As another example, the hardware processor 201 may process data related to a transfer request, identification data, and / or a transfer approval status.

[0180] The storage component 205 may include one or more memory devices that store data, including but not limited to dynamic and / or static random access memory (RAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), etc. The storage component 205 may store data including processed and / or unprocessed physiological data obtained from physiological sensors. The storage component 205 may store data including communication data, such as link keys and / or device addresses associated with sensors and / or monitoring hubs.

[0181] The communication component 207 can facilitate communication (via wired and / or wireless connections) between the monitoring hub 200 (and / or its components) and separate computing devices (e.g., separate monitoring hubs, monitoring devices, sensors, systems, servers, etc.). For example, the communication component 207 can be configured to allow the monitoring hub 200 to communicate wirelessly with other devices and systems using any combination of various communication protocols and / or over one or more networks. The communication component 207 can be configured to implement various wireless communication protocols (e.g., Wi-Fi (802.11x), Any combination of cellular telephone, infrared, near field communication (NFC), radio frequency identification (RFID), satellite transmission, proprietary protocols, combinations thereof, etc.). The communication component 207 can allow data and / or instructions to be transmitted to and / or received from the monitoring hub 200 and a separate computing device. The communication component 207 can be configured to transmit and / or receive (e.g., wirelessly) processed and / or unprocessed physiological data using a separate computing device including a physiological sensor, other monitoring hubs, a remote server, etc. As another example, the communication component 207 can be configured to transmit and / or receive (e.g., wirelessly) communication data (e.g., link keys and / or device addresses associated with the monitoring hub and / or sensors) using a separate computing device including a physiological sensor, other monitoring hubs, a remote server, etc. The communication component 207 can be embodied in one or more components that can communicate with each other. The communication component 207 can include one or more wireless transceivers, one or more antennas, one or more radio devices, and / or a near field communication (NFC) component (e.g., a transponder). The communication component 207 can communicate or connect wirelessly to one or more remote computing devices via a network, such as by implementing one or more wireless communication protocols.

[0182] The monitoring hub 200 may include a battery 203. The battery 203 may provide power to the hardware components of the monitoring hub 200 described herein. The battery 203 may be, for example, a lithium battery. Additionally or alternatively, the monitoring hub 200 may be configured to obtain power from a power source external to the monitoring hub 200. For example, the monitoring hub 200 may include or may be configured to be connected to a cable, which itself may be connected to an external power source to provide power to the monitoring hub 200.

[0183] Monitoring hub 200 may include display 209. Display 209 may include an LED display. Display 209 may include a touch screen, such as a capacitive touch screen. Display 209 may receive user input. Display 209 may present one or more user interfaces. Display 209 may display markers of physiological data.

[0184] Monitoring hub 200 may include one or more speakers 211. Speaker 211 may emit audio signals. Speaker 211 may emit an alarm. Speaker 211 may emit voice audio signals. Speaker 211 may include multiple speakers placed apart from each other at different locations on monitoring hub 200. Speaker 211 may emit stereo audio. Speaker 211 may emit audio using one or more audio channels. Speaker 211 may emit audio in multiple directions. Speaker 211 may emit mono audio. Speaker 211 may emit audio originating during a voice call and / or video call.

[0185] The monitoring hub 200 may include one or more microphones 213. The microphone 213 may detect an audio signal and generate a signal in response to the detected audio signal. The microphone 213 may detect an ambient noise level. The microphone 213 may detect a noise level in an environment surrounding the monitoring hub 200. The microphone 213 may detect a noise level in an environment adjacent to and / or surrounding an object. The monitoring hub 200 may adjust one or more operations based at least on the ambient noise level detected by the microphone 213. The monitoring hub 200 may perform one or more operations to increase the comfort of the patient based at least on the ambient noise level detected by the microphone 213. The microphone 213 may detect the voice of a person speaking. The microphone 213 may detect the voice of a person during a voice call and / or during a video call.

[0186] The monitoring hub 200 can implement voice calls. The monitoring hub 200 can be connected to one or more cellular devices. The monitoring hub 200 can implement voice calls using a cellular phone, for example, via the communication component 207. The monitoring hub 200 can implement video calls. A patient monitored by the monitoring hub 200 can talk to another person (e.g., a caregiver) in a remote location via the monitoring hub 200, which can implement one or more wireless communication protocols (e.g., a mobile phone) to connect to one or more remote computing devices over a network and can use a microphone 213 to detect the patient's voice.

[0187] The monitoring hub 200 may include one or more indicators 214. The indicator 214 may include a visual indicator. The indicator 214 may include an LED indicator, wherein the LED indicator includes one or more LEDs. The indicator 214 may emit one or more visual signals. The visual signals may correspond to the physiological state of the patient monitored by the monitoring hub 200. The indicator 214 may emit visual signals including multiple colors. The indicator 214 may emit visual signals according to a color code scheme, wherein various colors may correspond to various physiological states of the patient monitored by the monitoring hub 200.

[0188] Figure 3A 300. The monitoring hub 300 may include similar structures and / or operating features to any other example monitoring hubs shown and / or described herein. In this example embodiment, the monitoring hub 300 is fixed in a bracket 332. The monitoring hub 300 may be removably fixed in the bracket 332 via, for example, a friction fit. In this example embodiment, the monitoring hub 300 may include a display 302. The display 302 may include an LED display. The display 302 may include a touch screen configured to receive user input in response to touching the display 302. The display 302 may display markers of physiological data, including physiological trends, graphs, graphs, charts, parameters, values, percentages, animations, visualizations, etc. The display 302 may display markers of physiological data from multiple sensors, including different types of sensors measuring different types of physiological data. The monitoring hub may generate (and / or receive) user interface data for presenting display markers based at least on physiological data originating from one or more sensors or other devices.

[0189] The monitoring hub 300 may include a status indicator 304. The status indicator 304 may include one or more LEDs. The status indicator 304 may indicate the status of the object monitored by the monitoring hub 300. For example, the status indicator 304 may illuminate in response to a certain change in the physiological data of the object (e.g., a physiological parameter of the object) exceeding a threshold. The status indicator 304 may illuminate different colors in different operations or modes. The status indicator 304 may illuminate (e.g., red) during an alarm mode. When the monitoring hub 300 is not in an alarm mode, the status indicator 304 may not illuminate.

[0190] The monitoring hub 300 may include a communication interface 306. The communication interface 306 may include an electronic device configured to execute a wireless communication protocol. The communication interface 306 may include an NFC and / or RFID transponder or reader. The communication interface 306 may include a barcode reader or scanner. The communication interface 306 may include a QR code reader or scanner. The communication interface 306 may include a fingerprint scanner. The communication interface 306 may include a camera configured to capture an image of a user's face for facial recognition. The communication interface 306 may use magnetic field induction to communicate with a separate device. The communication interface 306 may communicate with a user device such as a user ID badge, a user phone, a user mobile device, a user smart watch, etc., to identify and / or verify the user, for example, by receiving a unique user identification from the user device.

[0191] The monitoring hub 300 may include a transfer request button 308. The transfer request button 308 may include a capacitive sensor configured to generate one or more signals in response to a user's touch. The transfer request button 308 may include one or more physical or mechanical actuators configured to generate one or more signals in response to physical actuation of the button 308 (e.g., pressing of the button 308). The user may press the transfer request button 308 to initiate the transfer of physiological monitoring to or from the monitoring hub 300. In some embodiments, the transfer request button 308 may be integrated into the display 302 (e.g., as part of a touch screen display).

[0192] Figure 3B310. The monitoring hub 310 may include similar structures and / or operating features to any other example monitoring hubs shown and / or described herein. The monitoring hub 310 may include a light sensor 319, a microphone 321, one or more indicators 323, a display 312, and / or a button 325. The light sensor 319 may be configured to detect ambient light. The monitoring hub 310 may change the display brightness of the display 312 based on the ambient light detected by the light sensor 319. The microphone 312 may be configured to detect sound. In some embodiments, the monitoring hub 310 may receive user input via the microphone 321, such as a transfer request as a voice command. In some embodiments, the monitoring hub 310 may implement voice recognition for the sound detected by the microphone 321. The indicator 323 may include one or more LEDs. The indicator 323 may indicate the status and / or operating status of the monitoring hub 310, such as the power level, the status of the wireless connection, etc. The user may operate the button 325 to control the operation of the monitoring hub 310.

[0193] In this example implementation, the monitoring hub 310 is in an alert mode. During the alert mode, the status indicator 314 may be illuminated (e.g., red). During the alert mode, the display 312 of the monitoring hub 310 may display one or more badges, icons, slogans, symbols, indicators, etc. to indicate that the monitoring hub 310 is in an alert mode. During this example alert mode, the display 312 may include a "Fall Detected" slogan 315. During this example alert mode, the display 312 illuminates an alert icon 317.

[0194] In some embodiments, the monitoring hub 310 may include an alarm toggle button 339. A user may press the alarm toggle button 339 to silence the alarm. A user may press the alarm toggle button 339 to change the state of the alarm. The alarm toggle button 339 may include a capacitive sensor. The alarm toggle button 339 may include one or more mechanical actuators.

[0195] Figure 4 An example process for transferring physiological monitoring from one monitoring hub (e.g., a source hub) to another monitoring hub (e.g., a destination hub) within a physiological monitoring system (PMS) is shown. Advantageously, as described herein, a PMS can facilitate faster, simpler, and more efficient transfer of physiological monitoring from one monitoring hub to another monitoring hub. For example, a PMS provides an intuitive and easy-to-use system (e.g., a user interface of a monitoring hub) for transferring physiological monitoring, which can reduce the time that a healthcare provider must spend on supervising a subject's physiological monitoring, and this can improve the quality of healthcare services provided to the subject. Figure 4The processes shown are provided as examples and are not intended to limit the present disclosure. In some implementations, certain parts (eg, steps) may be added, removed, and / or rearranged.

[0196] At step 4001, a monitoring hub 400A (e.g., a source monitoring hub) monitors physiological data of a subject. For example, the monitoring hub 400A may communicate with one or more physiological sensors and receive physiological data therefrom. The monitoring hub 400A displays indicia of the physiological data on a display 402A. To initiate a transfer of monitoring from the monitoring hub 400A, a user may press a transfer request button 408A.

[0197] At step 4002, the display 402A may stop displaying physiological data and indicate that the monitoring hub 400A has entered a "transfer mode" of operation. The display 402A may include instructions for the user to enter identification data (e.g., "Please tap the badge to the device for authentication"). The display 402A may include a graphical depiction 405A associated with the instructions and the actions to be taken by the user.

[0198] In step 4002, the user enters identification data to the monitoring hub 400A. In this example, as shown, the user moves the user ID device 407A near the communication interface 406A. The communication interface 406A communicates with the user ID device 407A using a wireless communication protocol (e.g., NFC and / or RFID) to receive identification data including a user identification from the user ID device 407A. For example, the identification data may include a unique user ID associated with the user (e.g., a serial number, a data sequence, etc.). In this example, the user ID device 407A may include a card or a badge. In some embodiments, the user ID device 407A may include a phone, a mobile device, a tablet computer, a smart watch, etc. In some embodiments, the user may manually enter (e.g., via the display 402A) identification data including an identification in the monitoring hub 400A. In some embodiments, the identification data may include one or more biomarkers of the user (e.g., facial recognition, fingerprint recognition, eye recognition, voice recognition), and the monitoring hub 400A may include one or more devices configured to receive and identify biomarkers.

[0199] In some embodiments, in response to receiving the identification data at the monitoring hub 400A, the PMS may determine whether the user has permission to make the transfer, e.g., as described in relation to Figure 5AReceiving identification data at step 4002 may cause monitoring hub 400A to terminate a wireless communication connection, such as a Bluetooth connection, with one or more sensors. In some embodiments, receiving identification data at step 4002 may cause monitoring hub 400B to establish a wireless communication connection, such as a Bluetooth connection, with one or more sensors.

[0200] At step 4003, display 402A may indicate the identity of the user requesting the transfer (e.g., "You are logged in as Dr. John Doe."). Display 402A may indicate instructions to the user requesting the transfer to the second monitoring hub and providing identification data at the second monitoring hub (e.g., "On the target device: Please select 'Transfer Mode' and then enter with a badge."). Display 402A may include a graphical depiction 405A associated with the instructions and actions to be taken by the user.

[0201] At step 4004, monitoring hub 400B (e.g., a target monitoring hub) may not monitor the subject's physiological data. For example, monitoring hub 400B may not communicate with one or more physiological sensors and may not receive physiological data therefrom. Monitoring hub 400B may not display physiological data on display 402B. To initiate a transfer of monitoring to monitoring hub 400B, a user may, for example, press transfer request button 408B in response to instructions provided on display 402A at step 4003.

[0202] At step 4005, display 402B indicates that monitoring hub 400B has entered "transfer mode" operation. Display 402B may include instructions for the user to enter identification data (e.g., "Please tap the badge to the device for authentication"). Display 402B may include a graphical depiction 405B associated with the instructions and the actions to be taken by the user.

[0203] In step 4005, the user may input identification data to monitoring hub 400B. For example, the user moves user ID device 407B to the vicinity of communication interface 406B so that communication interface 406B communicates with ID device 407B using a wireless communication protocol (e.g., NFC and / or RFID) to receive identification data indicating the user's identification from user ID device 407B. In some embodiments, the user may input identification data using other devices or processes as described herein. In some embodiments, user ID device 407B may be the same as user ID device 407A.

[0204] In some embodiments, in response to receiving the identification data at the monitoring hub 400B, the PMS may determine whether the user has permission to make the transfer, e.g., as described in relation to Figure 5AAs shown and / or discussed above. Receiving identification data at step 4005 may cause monitoring hub 400A to terminate a wireless communication connection, such as a Bluetooth connection, with one or more sensors. Receiving identification data at step 4005 may cause monitoring hub 400B to establish a wireless communication connection, such as a Bluetooth connection, with one or more sensors. Receiving identification data at step 4005 may cause monitoring hub 400B to initiate a paging process to establish a Bluetooth connection with one or more sensors.

[0205] After the monitoring hub 400B receives the identification data, the PMS can determine whether the transfer request is approved. Determining that the transfer request is approved may include comparing the identification data received at the monitoring hub 400A with the identification data received at the monitoring hub 400B. Determining that the transfer request is approved may include comparing the user ID of the identification data received at the monitoring hub 400A with the user ID of the identification data received at the monitoring hub 400B. In some embodiments, if the identification data received at the monitoring hub 400A matches the identification data received at the monitoring hub 400B, the PMS can determine that the transfer request is approved. In some embodiments, if the identification data received at the monitoring hub 400A corresponds to the identification data received at the monitoring hub 400B, the PMS can determine that the transfer request is approved. The identification data may correspond without matching or being identical, such as if the identification data corresponds to two users in the same group, assigned to the same task, assigned to the same patient, on the same schedule, etc. For example, if two users are working together to care for a patient, and the PMS can determine that the two identification data correspond (although they may not exactly match), one user can enter their identification data at the source monitoring hub and the other user can enter their identification data at the target monitoring hub. Figure 5A shown and / or discussed.

[0206] In response to receiving the identification data and determining that the transfer request is approved, the PMS may establish wireless communication, such as a Bluetooth connection, between the monitoring hub 400B and one or more physiological sensors previously communicating with the monitoring hub 400A. Establishing wireless communication may include initiating a paging process of the Bluetooth protocol. Establishing wireless communication may not include a pairing process of the Bluetooth protocol. For additional details on establishing communication between the monitoring hub 400B and the physiological sensors, refer to Figures 5A-5E shown and / or discussed.

[0207] In some embodiments, the PMS can establish communication between the monitoring hub 400A and the monitoring hub 400B. Establishing communication between the monitoring hubs 400A and 400B can facilitate information communication therebetween, including, for example, communication data (e.g., device addresses of physiological sensors), physiological data (e.g., historical physiological data), and the like.

[0208] In step 4006, monitoring hub 400A may stop displaying markers of physiological data and / or other data via display 402A. Monitoring hub 400B may begin displaying markers of physiological data and / or other data via display 402B. In some embodiments, monitoring hub 400B may begin displaying data after monitoring hub 400A stops displaying data. In some embodiments, monitoring hub 400B may begin displaying data before monitoring hub 400A stops displaying data. In some embodiments, monitoring hub 400B may begin displaying data at the same time that monitoring hub 400A stops displaying data.

[0209] In step 4006, the monitoring hub 400B may display physiological data via the display 402B. The physiological data displayed on the display 402B may include real-time physiological data received from a sensor communicating with the monitoring hub 400B. The physiological data displayed on the display 402B may include historical physiological data collected by the sensor at a certain time before communication is established between the sensor and the monitoring hub 400B. For example, the monitoring hub 400B may receive historical physiological data from the monitoring hub 400A and / or from a server of the PMS, and the historical physiological data is collected by the sensor and / or received at the monitoring hub 400A before the monitoring hub 400B establishes communication with the sensor. The monitoring hub 400A may not directly receive historical physiological data from the sensor. Advantageously, by displaying historical physiological data combined with real-time physiological data (e.g., received from the sensor), the monitoring hub 400B can display physiological data as if the monitoring hub 400B had monitored physiological data (e.g., received data obtained from the sensor) at a certain time before the monitoring hub 400B began to monitor physiological data. Advantageously, transferring monitoring from one hub to another may not result in loss of data or inability to view data because the target monitoring hub (e.g., monitoring hub 400B) can display the data prior to the transfer. After transferring monitoring from one monitoring hub to another, the user can advantageously view physiological data with little or no discontinuities, interruptions, data loss, etc. Advantageously, the PMS can be configured to continuously monitor the subject's physiology while transferring physiological monitoring from one monitoring hub to another.

[0210] In some embodiments, at step 4001 and / or 4004, the PMS may be as described in reference Figure 4As shown and / or described, physiological monitoring is transferred without receiving physical user input, such as a button press. For example, a user may not press a button (e.g., button 408A) on monitoring hub 400A to request a transfer. As another example, a user may not press a button (e.g., button 408A) on monitoring hub 400B to place monitoring hub 400B in transfer mode. In some embodiments, a user may request to transfer physiological monitoring by entering identification data (e.g., via NFC / RFID), as described in step 4002. In some embodiments, a user may place monitoring hub 400B in transfer mode by entering identification data (e.g., via NFC / RFID), as described in step 4005. Therefore, the devices and systems described herein may provide methods for transferring physiological monitoring by implementing contactless user input. For example, a user may transfer physiological monitoring without physically contacting the monitoring hub, such as by pressing a button. Other examples include transferring physiological monitoring without requiring the user to unplug or reinsert the device, turn the device on or off, or change the operating mode of the device, such as placing the device in pairing mode, discovery mode, or connection mode. Reducing physical contact can improve hygiene, improve the speed and efficiency of transferring physiological monitoring, and reduce the complexity of transferring physiological monitoring, for example, by reducing the number of steps required for transferring physiological monitoring. Non-contact input can include near field communication (NFC) and / or radio frequency identification (RFID). Non-contact input can include facial recognition, eye recognition, fingerprint recognition, gesture recognition, voice recognition, etc. Non-contact input can include minimal contact input. In addition, the devices and systems described herein can provide methods for user-controlled transfer of physiological monitoring. For example, a user can control when to transfer physiological monitoring, for example, by providing user input to the system, and the user input can include non-contact user input. Controlling the transfer of physiological monitoring by user input can reduce erroneous or undesirable transfers, which may occur due to, for example, the devices being adjacent to each other. In some embodiments, the system can automatically transfer physiological monitoring without user input, for example, by implementing a wireless communication connection based on proximity.

[0211] In some embodiments, the PMS can be used between the monitoring hub and multiple sensors as shown in the reference Figure 4 The PMS may transfer the wireless communication connections of multiple sensors at a single time. The PMS may transfer the wireless communication connections of multiple sensors in response to a single user input. The PMS may transfer the wireless communication connections of multiple sensors in response to a single request to transfer the physiological monitoring. Advantageously, transferring the physiological monitoring of multiple sensors at a single time may improve the speed and efficiency of transferring the physiological monitoring, for example, by not having to repeat a similar transfer procedure for each sensor.

[0212] Example Method

[0213] Figure 5A is a flowchart showing an exemplary process 500A for transferring physiological monitoring from a source monitoring hub to a target monitoring hub. One or more hardware processors may perform process 500A or a portion thereof. Process 500A or a portion thereof may be implemented on one or more computing devices described herein, such as a source monitoring hub, a target monitoring hub, a server, etc. Process 500A or a portion thereof may be performed by one or more hardware processors of a single computing device. Process 500A or a portion thereof may be performed by multiple computing devices, such as one or more hardware processors of computing devices that are remote from each other and / or wirelessly communicate with each other. In some embodiments, one or more hardware processors associated with a server (e.g., server 106 shown and / or described herein) may perform process 500A or a portion thereof. Process 500A is provided as an example and is not intended to limit the present disclosure. In some embodiments, one or more hardware processors executing process 500A may omit portions of process 500A, may add additional operations, and / or may rearrange the order of operations for performing process 500A.

[0214] At block 501, one or more hardware processors may receive a request to transfer physiological monitoring from one monitoring hub (e.g., a source monitoring hub) to another monitoring hub (e.g., a target monitoring hub). In some embodiments, the source monitoring hub and / or the target monitoring hub may receive a transfer request, e.g., Figure 4 as shown and / or described. One or more hardware processors may receive the request via user input at a monitoring hub. The user input may include pressing a button on the monitoring hub. In some embodiments, process 500 may not include box 501. For example, the computing device may receive identification data as discussed in box 503 without receiving a transfer request at box 501. In some embodiments, the request to transfer physiological monitoring may include a request to establish initial physiological monitoring at a monitoring hub without terminating physiological monitoring at another monitoring hub, for example if the physiological monitoring is being established for the first time, or if physiological monitoring did not occur prior to the request.

[0215] At block 503, one or more hardware processors may receive identification data. The identification data may be associated with the user requesting the transfer. The one or more hardware processors may receive the identification data via a monitoring hub (e.g., a source monitoring hub and / or a target monitoring hub). The identification data may be associated with the monitoring hub that receives it. In some embodiments, the source monitoring hub may receive the identification data, e.g., Figure 4In some embodiments, receiving identification data may be used to receive a request for transfer physiological monitoring as described at block 501. For example, process 500A may not implement block 501 or may implement block 501 as part of block 503.

[0216] At decision block 505 , one or more hardware processors may determine whether the user requesting the transfer of physiological monitoring has appropriate permissions to make the transfer. In some implementations, one or more hardware processors may determine whether the requesting user has permissions based at least on the identification data received at block 503 .

[0217] In some embodiments, one or more hardware processors may determine whether the requesting user has appropriate authority based on one or more of an identification of the user, a title of the user, a role of the user, a task assigned to the user, etc. (which may be determined by the identification data). For example, a doctor (e.g., as identified by a user ID included in the identification data) may have authority to make a transfer, while a nurse may not. As another example, a certain type of doctor (e.g., a cardiologist) may have authority to make a transfer, while another type of doctor (e.g., a surgeon) may not. As another example, a healthcare provider assigned to a patient may have authority to make a transfer, while a healthcare provider not assigned to the patient may not.

[0218] In some embodiments, one or more hardware processors may determine whether the requesting user has the appropriate authority based on the time of the request. For example, when the monitored object is undergoing surgery or sleeping, or during a scheduled meal time, etc., the user may not have the authority to transfer physiological monitoring between monitoring centers. In some embodiments, one or more hardware processors may determine whether the requesting user has the appropriate authority based on a reason provided by the user that can be entered by the user in the monitoring center (e.g., as part of the identification data). In some embodiments, one or more hardware processors may determine whether the requesting user has the appropriate authority based on the location of the monitored object and / or the location of the monitoring center. For example, if the object is considered to be in a specific ward, the user may not have the authority to transfer physiological monitoring from a monitoring center located in a specific ward to a mobile monitoring center. As another example, if the object is considered not to be in a specific ward (e.g., the object is not scheduled for surgery), the user may not have the authority to transfer physiological monitoring from a mobile monitoring center to a monitoring center located in a specific ward (e.g., a surgical operating room).

[0219] Advantageously, verifying permissions associated with a user can improve the quality of healthcare, such as by ensuring that the PMS only transfers physiological monitoring in appropriate circumstances, which can ensure that the subject is receiving appropriate healthcare (e.g., the subject is not relocated to a different room in the hospital if it is not appropriate).

[0220] In response to determining that the requesting user has authority to make the transfer, the one or more hardware processors may proceed to block 507. In response to determining that the requesting user does not have authority to make the transfer, the one or more hardware processors may return to block 501.

[0221] At block 507, the one or more hardware processors may optionally receive other identification data. The other identification data may be associated with the user requesting the transfer. The one or more hardware processors may receive the other identification data via a monitoring hub (e.g., a source monitoring hub and / or a target monitoring hub). The other identification data may be associated with the monitoring hub that receives it. In some embodiments, the target monitoring hub may receive the other identification data, such as, for example, information about the user requesting the transfer. Figure 4 shown and / or described.

[0222] At decision box 509, one or more hardware processors may determine whether the identification corresponds to other identification data. One or more hardware processors may compare identification data. For example, one or more hardware processors may compare identification data received by the source monitoring hub with identification data received by the target monitoring hub. In some embodiments, comparing identification data may include determining whether identification data received at the source monitoring hub corresponds to identification data received at the target monitoring hub. In some embodiments, comparing identification data may include determining whether identification data received at the source monitoring hub matches identification data received at the target monitoring hub. In some embodiments, comparing identification data may include comparing user identifications included in the identification data.

[0223] In some embodiments, if the identification data (or portions thereof) in each corresponding identification data matches each other, for example if they are identical or substantially similar, then one or more hardware processors may determine that the identification data corresponds. For example, this may indicate that the user requesting the transfer at the source monitoring hub is the same user requesting the transfer at the target monitoring hub. In some embodiments, if the identification data (or portions thereof) in each corresponding identification data does not match each other, then one or more hardware processors may determine that the identification data does not correspond. This may indicate that the user requesting the transfer at the source monitoring hub is not the same user requesting the transfer at the target monitoring hub.

[0224] In some embodiments, if the corresponding identifications are associated with each other, one or more hardware processors can determine that the identification data corresponds. This can indicate that the user requesting the transfer at the source monitoring hub is associated with the user requesting the transfer at the target monitoring hub. For example, if the users work together (e.g., simultaneously providing healthcare services to patients monitored by a PMS), the user requesting the transfer at the source monitoring hub can be associated with the user requesting the transfer at the target monitoring hub. In some embodiments, if the first user and the second user are in the same group (e.g., healthcare providers in the same or similar group and / or location (e.g., floor or nursing unit)), the one or more hardware processors can determine that the identification of the first user is associated with the identification of the second user.

[0225] Advantageously, comparing identification data (e.g., to which they correspond) can improve the accuracy of transferring physiological monitoring from one monitoring hub to an appropriate monitoring hub. For example, determining that identification data correspond to each other can ensure that the PMS transfers physiological monitoring to the correct monitoring hub, rather than to an incorrect monitoring hub, which may have identification data that does not correspond to the identification data received at the source monitoring hub. Advantageously, verifying that identification data corresponds can facilitate accurate transfer of physiological monitoring between desired monitoring hubs in a PMS that includes many monitoring hubs and / or includes many requests to transfer physiological monitoring between various monitoring hubs that occur simultaneously or nearly simultaneously. For example, by verifying that identification data of source and target monitoring hubs correspond, the PMS can accurately transfer physiological monitoring between appropriate pairs of monitoring hubs (e.g., between source and target monitoring hubs), such as between monitoring hub pair A, between monitoring hub B, and between monitoring hub pair C, at the same or similar times, without incorrectly transferring physiological monitoring between different pairs of hubs (e.g., from a hub in pair A to a hub in pair B).

[0226] In some implementations, in response to determining that the identification data corresponds, the one or more hardware processors may proceed to block 511. In some implementations, in response to determining that the identification data does not correspond, the one or more hardware processors may return to block 501.

[0227] At decision block 511, the one or more hardware processors may optionally determine whether the target monitoring hub is within a threshold proximity of the sensor. The one or more hardware processors may determine the proximity of the monitoring hub to the sensor based at least on a wireless signal strength between the monitoring hub and the sensor. In response to determining that the target monitoring hub is within the threshold proximity of the sensor, the one or more hardware processors may proceed to block 513. In response to determining that the target monitoring hub is not within the threshold proximity of the sensor, the one or more hardware processors may return to block 501.

[0228] At box 513, one or more hardware processors may initiate a transfer of physiological monitoring to a target monitoring hub. Transferring physiological monitoring may include establishing wireless communication between one or more sensors and the target monitoring hub. Transferring physiological monitoring may include terminating wireless communication between one or more sensors and the source monitoring hub. In some embodiments, terminating communication with the source monitoring hub may be prior to establishing communication with the target monitoring hub. In some embodiments, terminating communication may occur automatically as a result of establishing communication. Transferring physiological monitoring may include transferring physiological monitoring associated with all sensors in communication with the source monitoring hub to the target monitoring hub. Transferring physiological monitoring may include transferring physiological monitoring associated with less than all sensors in communication with the source monitoring hub to the target monitoring hub.

[0229] Advantageously, process 500A can provide a system for transferring physiological monitoring from one monitoring hub to another (e.g., establishing and / or terminating communications between a monitoring hub and a sensor) without having to unplug, plug in, and / or reinsert cables, wires, etc., of the monitoring hub and / or physiological sensors.

[0230] Figure 5B Flowchart showing an example process 500B associated with transferring physiological monitoring from a source monitoring hub to a target monitoring hub. One or more hardware processors may perform process 500B or a portion thereof. Process 500B or a portion thereof may be implemented on one or more computing devices described herein, such as a source monitoring hub, a target monitoring hub, a server, etc. Process 500B or a portion thereof may be performed by one or more hardware processors of a single computing device. Process 500B or a portion thereof may be performed by a plurality of computing devices, such as one or more hardware processors of computing devices that are remote from each other and / or wirelessly communicate with each other. In some embodiments, one or more hardware processors associated with a server (e.g., server 106 shown and / or described herein) may perform process 500B or a portion thereof. Process 500B is provided as an example and is not intended to limit the present disclosure. In some embodiments, one or more hardware processors that perform process 500B may omit portions of process 500B, may add additional operations, and / or may rearrange the order of operations that perform process 500B.

[0231] At block 521, one or more hardware processors may receive wireless configuration data from a source monitoring hub. The one or more hardware processors may receive the wireless configuration data via a wireless transmission including one or more wireless communication protocols. The one or more hardware processors may receive the wireless configuration data via WiFi. The wireless configuration data may facilitate wireless communication with one or more sensors. The wireless configuration data may be associated with the one or more sensors. The wireless configuration data may include one or more device addresses. The wireless configuration data may include one or more link keys.

[0232] At block 523, one or more hardware processors may receive physiological data from a source monitoring hub. The physiological data may include physiological data received at the source monitoring and originating from one or more sensors. The physiological data may include historical physiological data previously received at the monitoring hub during a time frame. The physiological data may include historical physiological data previously generated by one or more sensors during a time frame. In some embodiments, the physiological data includes real-time physiological data. Real-time physiological data may include data generated by one or more sensors and transmitted to the source monitoring hub at a time substantially similar to the time transmitted from the source monitoring hub to the one or more hardware processors. In some embodiments, one or more hardware processors may receive physiological data from the source monitoring hub as a continuous stream of data when the source monitoring hub receives data from the one or more sensors. In some embodiments, one or more hardware processors may receive physiological data in response to an event, such as in response to a request to transfer physiological monitoring. In some embodiments, one or more hardware processors may receive physiological data as a data packet. For example, one or more hardware processors may receive a transmission of physiological data from a source monitoring hub, which may include physiological data originating from one or more sensors during a time frame.

[0233] In some embodiments, one or more hardware processors may receive data associated with physiological data. The data associated with physiological data may include user interface data for presenting a user interface including display indicia of physiological data. The data associated with physiological data may include a signal corresponding to an alarm or prompt generated in response to the physiological data. The data associated with physiological data may include a state associated with an object corresponding to the physiological data.

[0234] At block 525, the one or more hardware processors may store wireless configuration data and / or physiological data. The one or more hardware processors may store data in a memory. The one or more hardware processors may store wireless configuration data associated with the one or more sensors. The one or more hardware processors may store physiological data associated with the monitoring hub, associated with the one or more sensors, and / or such as associated with the subject.

[0235] At block 527, the one or more hardware processors may receive a request to establish physiological monitoring at the target monitoring hub. The request to establish physiological monitoring at the target monitoring hub may be included as part of a request to transfer physiological monitoring from the source monitoring hub to the target monitoring hub. The request to establish physiological monitoring may indicate one or more sensors with which the target monitoring hub is to establish wireless communication. The one or more hardware processors may receive the request via one or more monitoring hubs, such as those described herein, for example, with reference to Figure 4 and / or Figure 5A In some implementations, one or more hardware processors may perform block 527 prior to performing block 521 and / or block 523. For example, one or more hardware processors may perform block 521 and / or block 523 in response to receiving a request at block 527.

[0236] In box 529, one or more hardware processors may transmit wireless configuration data to the target monitoring hub. One or more hardware processors may access the wireless configuration data to be transmitted from the memory. The wireless configuration data may be associated with one or more sensors, and the target monitoring hub will establish wireless communication with the sensors. For example, the wireless configuration data may include one or more device addresses associated with the one or more sensors. The wireless configuration data may include one or more link keys associated with the one or more sensors. In some embodiments, the wireless configuration data may be associated with the target monitoring hub. For example, the wireless configuration data may include one or more link keys associated with the target monitoring hub. One or more hardware processors may transmit the wireless configuration data via one or more wireless communication protocols. One or more hardware processors may transmit the wireless configuration data via WiFi. Transmitting the wireless configuration data to the target monitoring hub can enable the target monitoring hub to establish wireless communication with one or more sensors associated with the wireless configuration data.

[0237] At box 531, one or more hardware processors may transmit physiological data to the target monitoring hub. The physiological data may include physiological data previously generated by one or more sensors and / or physiological data previously received at the source monitoring hub. The physiological data may include data that becomes historical physiological data when transmitted at box 529. For example, the physiological data may include data generated by one or more sensors and communicated to the source monitoring hub before receiving a request to establish physiological monitoring at the target monitoring hub and / or before the target monitoring hub establishes physiological monitoring. Transmitting physiological data to the target monitoring hub may cause the target monitoring hub to present a user interface including display tags corresponding to the physiological data. One or more hardware processors may transmit physiological data as a single transmission and / or at a single time. One or more hardware processors may transmit physiological data as a data packet. One or more hardware processors may transmit physiological data corresponding to a time frame within which the physiological data is generated by one or more sensors, and one or more hardware processors may transmit physiological data corresponding to the time frame as a single transmission, a data packet, and / or at substantially the same time.

[0238] In some embodiments, one or more hardware processors may transmit data associated with physiological data. The data associated with physiological data may include user interface data for presenting a user interface including display indicia of physiological data. The data associated with physiological data may include a signal corresponding to an alarm or prompt generated in response to the physiological data. The data associated with physiological data may include a state associated with an object corresponding to the physiological data. As an example, one or more hardware processors may transmit signals associated with alarms, prompts, states, etc. to a target monitoring hub, which may have been generated at a source monitoring hub based on the physiological data. Therefore, the target monitoring hub can continue the same alarms, prompts, states, etc. that occurred at the source monitoring hub, which can maintain the continuity of physiological monitoring.

[0239] The one or more hardware processors may transmit the physiological data via one or more wireless communication protocols. The one or more hardware processors may transmit the physiological data via WiFi.

[0240] Figure 5Cis a flowchart showing an example process 500C associated with transferring physiological monitoring from a source monitoring hub to a target monitoring hub. One or more hardware processors may perform process 500C or portions thereof. Process 500C or portions thereof may be implemented on one or more computing devices described herein, such as a source monitoring hub, a target monitoring hub, a server, etc. Process 500C or portions thereof may be performed by one or more hardware processors of a single computing device. Process 500C or portions thereof may be performed by one or more hardware processors of a plurality of computing devices, such as computing devices that are remote from each other and / or wirelessly communicate with each other. In some embodiments, one or more hardware processors associated with a target monitoring hub may perform process 500C or portions thereof. Process 500C is provided as an example and is not intended to limit the present disclosure. In some embodiments, one or more hardware processors performing process 500C may omit portions of process 500C, may add additional operations, and / or may rearrange the order of operations for performing process 500C.

[0241] At block 543, the one or more hardware processors may receive a request to establish physiological monitoring at a target monitoring hub. The request to establish physiological monitoring at a target monitoring hub may be included as part of a request to transfer physiological monitoring from a source monitoring hub to a target monitoring hub. The request to establish physiological monitoring may indicate one or more sensors with which the target monitoring hub is to establish wireless communication. The one or more hardware processors may receive the request via one or more monitoring hubs, such as those described herein, for example, with reference to Figure 4 and / or Figure 5A In some implementations, the one or more hardware processors can also verify the authority of the requesting user, for example based at least on the identification data.

[0242] At box 545, one or more hardware processors may access the wireless configuration data. The one or more hardware processors may access the wireless configuration data by receiving the wireless configuration data from a remote computing device, such as a server. The one or more hardware processors may receive the wireless configuration data indirectly from the source monitoring hub via an intermediate device. For example, the one or more hardware processors may receive the wireless configuration data from the server after the server has received the wireless configuration data from the source monitoring hub. The one or more hardware processors may access the wireless configuration data from the memory. For example, the one or more hardware processors may access the wireless configuration data from the memory stored on the target monitoring hub. The wireless configuration data stored in the memory may have been previously received from the remote computing device. In some embodiments, the one or more hardware processors may receive the wireless configuration data from the source monitoring hub via wired or wireless communication. In some embodiments, the one or more hardware processors may not receive the wireless configuration data directly from the source monitoring hub. In some embodiments, the one or more hardware processors may receive the wireless configuration data from one or more sensors. In some embodiments, the one or more hardware processors may generate at least a portion of the wireless configuration data. For example, during a pairing process with one or more sensors, the one or more hardware processors may generate and / or receive at least a portion of the wireless configuration data from the one or more sensors. In some implementations, one or more hardware processors may not generate and / or receive wireless configuration data during the pairing process.

[0243] At box 547, one or more hardware processors may establish wireless communication between the target monitoring hub and one or more sensors. The one or more hardware processors may establish wireless communication according to one or more wireless communication protocols. The one or more hardware processors may establish wireless communication according to a Bluetooth communication protocol. Establishing wireless communication may include establishing a Bluetooth connection (e.g., after a paging process). The one or more hardware processors may establish wireless communication based at least on wireless configuration data. The one or more hardware processors may establish wireless communication by initiating a paging process. The one or more hardware processors may establish wireless communication based at least on forwarding at least a portion of the wireless configuration data to one or more sensors. The one or more hardware processors may establish wireless communication without initiating a pairing process and / or an inquiry process. In some embodiments, the target monitoring hub may be considered to be bound to one or more sensors, for example, by accessing the wireless configuration data. In some embodiments, the target monitoring hub may have never previously established wireless communication with one or more sensors. Establishing communication may include establishing communication between the target monitoring hub and all sensors that previously communicated with the source monitoring hub. Establishing communication may include establishing communication between the target monitoring hub and less than all sensors that previously communicated with the source monitoring hub.

[0244] Advantageously, accessing the wireless configuration data at box 545 (e.g., receiving the wireless configuration data from a remote computing device such as a server) can facilitate establishing wireless communication, for example, by eliminating the need to perform a pairing process (which can include a query process), which can take up to 10 seconds to complete and can involve significant data processing and communication between remote devices. Thus, accessing the wireless configuration data at box 545 can reduce the processing requirements for establishing wireless communication at box 547, which can improve efficiency, reduce the time required to establish wireless communication, and reduce the processing power required to establish the wireless configuration data at box 545, which can improve energy conservation and extend battery life. In addition, reducing the time required to establish wireless communication can reduce data loss. For example, data collected by a physiological sensor may be lost while waiting for wireless communication to be established between the sensor and the monitoring hub (e.g., during a pairing process). Reducing data loss can improve physiological monitoring of the subject, which can improve the medical care provided to the subject. Reducing data loss can improve continuous physiological monitoring of the subject when transferring physiological monitoring between monitoring hubs. For example, the monitoring hub may continuously monitor the object, and the data gap generated during the transfer is less than 10 seconds, less than 5 seconds, less than 1 second, less than 0.5 seconds, less than 0.1 seconds, less than 0.05 seconds, less than 0.01 seconds, etc. In addition, eliminating the need to perform a pairing process (e.g., by accessing wireless configuration data at box 545) can avoid the need to place the sensor in discovery mode, or if the sensor is not in discovery mode, the inability to establish wireless communication can be avoided. Advantageously, a user may be able to establish communication between a sensor and a target hub without having to turn off and / or turn on the sensor, the target hub, and / or the source hub. Advantageously, a user may be able to establish communication between a sensor and a target hub without having to change the connection state or mode of the sensor, the target hub, and / or the source hub.

[0245] At box 547, one or more hardware processors may automatically establish wireless communication, for example, without requiring user input. For example, one or more hardware processors may establish wireless communication based on the proximity of one or more sensors to the target monitoring hub. At box 547, one or more hardware processors may establish wireless communication in response to user input. For example, a user may provide input to confirm that one or more hardware processors want to establish wireless communication. In some embodiments, a user may provide contactless user input to initiate the establishment of wireless communication. Contactless user input may include near field communication (NFC) and / or radio frequency identification (RFID). Contactless user input may include facial recognition, eye recognition, fingerprint recognition, gesture recognition, voice recognition, etc. Contactless user input may include minimal contact user input, such as input that may not require contact but may still result in minimal, insubstantial, unexpected or insignificant contact. Reducing physical contact can improve hygiene, increase the speed and efficiency of transfer physiological monitoring, and reduce the complexity of transfer physiological monitoring, for example, by reducing the number of steps required for transfer physiological monitoring. In some embodiments, at box 547, one or more hardware processors may establish wireless communication based on the proximity of the target monitoring hub to one or more sensors in combination with user input.

[0246] At block 547, the one or more hardware processors may establish wireless communication between the target monitoring hub and the plurality of sensors. The one or more hardware processors may establish wireless communication with the plurality of sensors at a single time. The one or more hardware processors may establish wireless communication with the plurality of sensors in response to a single user input. The one or more hardware processors may establish wireless communication with the plurality of sensors in response to a single request to transfer physiological monitoring.

[0247] At box 549, one or more hardware processors may receive real-time physiological data originating from one or more sensors. One or more hardware processors may receive real-time physiological data via wireless communication established at box 547. Real-time physiological data may include data generated by one or more sensors and transmitted to one or more hardware processors in real time. For example, one or more hardware processors may receive physiological data at substantially the same time as one or more sensors generate physiological data. As another example, after one or more sensors generate physiological data, one or more hardware processors may receive physiological data with minimal time delay, which may be imperceptible to humans. One or more hardware processors may receive real-time physiological data continuously. For example, real-time physiological data may include a continuous data stream. One or more hardware processors may receive real-time physiological data periodically. For example, real-time physiological data may include data periodically generated by one or more sensors.

[0248] At box 551, one or more hardware processors may receive historical physiological data from a remote computing device (e.g., a server, such as server 106 shown and / or described herein). The one or more hardware processors may receive the historical physiological data via one or more wireless communication protocols (e.g., WiFi). The historical physiological data may include physiological data previously generated by one or more sensors. The historical physiological data may include data generated by one or more sensors before wireless communication is established between the target monitoring hub and the one or more sensors at box 547. The historical physiological data may include data communicated from one or more sensors to the source monitoring hub, for example, before wireless communication is established between the target monitoring hub and the one or more sensors at box 547. The historical physiological data may include data corresponding to a time frame of less than 6 hours, less than 1 hour, less than 30 minutes, less than 10 minutes, less than 5 minutes, less than 1 minute, less than 30 seconds, less than 10 seconds, or less than 1 second. The one or more hardware processors may receive the historical physiological data as a single transmission or data packet. The one or more hardware processors may receive the historical physiological data at a single moment. The one or more hardware processors may receive the historical physiological data within a time frame shorter than the time frame corresponding to the one or more sensors generating the historical physiological data. As an example, one or more hardware processors may receive a data packet that includes historical physiological data as a single transmission and / or at a single moment in time.

[0249] In some embodiments, one or more hardware processors may receive data associated with physiological data. The data associated with physiological data may include user interface data for presenting a user interface including a display mark of physiological data. The data associated with physiological data may include a signal corresponding to an alarm or prompt generated in response to the physiological data. The data associated with physiological data may include a state associated with an object corresponding to the physiological data. As an example, one or more hardware processors may receive a signal related to an alarm, prompt, state, etc., which may have been generated at a source monitoring hub based on physiological data. Therefore, the target monitoring hub can continue the same alarm, prompt, state, etc. that occurred on the source monitoring hub, which can maintain the continuity of physiological monitoring. In addition, the target monitoring hub may be able to initiate an alarm or prompt or display a state more quickly, at least because the target monitoring hub may not have to reprocess historical physiological data to determine whether to initiate an alarm or prompt or determine a state that can reduce processing time and energy requirements, which can improve computing efficiency and improve healthcare monitoring. In an illustrative example, the source monitoring hub can generate an alarm corresponding to a critical patient condition based at least on analyzing physiological data received from a sensor. According to the transfer of physiological monitoring to the target monitoring hub, the target monitoring hub can receive (e.g., from a server) a signal corresponding to an alarm. The target monitoring hub can immediately initiate an alarm without having to process (historical) physiological data received from the source monitoring hub, for example, via a server. Therefore, physiological monitoring of the patient can continue with reduced gaps or discontinuities.

[0250] In some implementations, the one or more hardware processors can analyze the historical physiological data received at block 551 to determine one or more physiological states or trends in the physiological data. The one or more hardware processors can analyze the historical physiological data received at block 551 to generate one or more alarms, prompts, etc. corresponding to the physiological data. Advantageously, because the one or more hardware processors can access historical physiological data (e.g., received at block 551), the one or more hardware processors may be able to more accurately analyze the physiological data, at least because the one or more hardware processors can access more physiological data, including historical physiological data and real-time physiological data.

[0251] At box 553, one or more hardware processors may generate user interface data to present a display including a marker of physiological data, which may include real-time physiological data and / or historical physiological data. One or more hardware processors may present the display via the target monitoring hub. One or more hardware processors may transmit the user interface data to a remote computing device, such as a smart watch, a smart phone, a tablet, a PC, a wearable device, a monitoring device that can present the display. Advantageously, one or more hardware processors may access real-time physiological data as well as historical physiological data (which may have been generated by one or more sensors before establishing wireless communication with one or more sensors), which may improve physiological monitoring, for example, by reducing data loss and providing a more comprehensive view of the subject's physiological data. One or more hardware processors may generate user interface data to present a display that combines real-time physiological data with historical physiological data and has minimal or no interruptions or discontinuities in the display of physiological data. One or more hardware processors may generate user interface data to present the display as if one or more hardware processors had received physiological data from the sensor at some time before establishing wireless communication at box 547.

[0252] In some embodiments, at box 553, one or more hardware processors may not generate user interface data corresponding to historical physiological data. For example, at box 551, one or more hardware processors may receive user interface data corresponding to historical physiological data. The user interface data received at box 551 may have been generated by a source monitoring hub, which may be similar or of the same type as the target monitoring hub. Therefore, the user interface data generated by the source monitoring hub and received at the target monitoring hub may be compatible with the target monitoring hub, so that the target monitoring hub may not need to regenerate the user interface data for presenting a display corresponding to the historical physiological data. Advantageously, eliminating the need to generate redundant user interface data can reduce processing requirements, improve processing speed and efficiency, and reduce the time required to present a display including physiological data tags, which can improve physiological monitoring and medical care provided to the subject. In some embodiments, the source monitoring hub and the target monitoring hub may be of different types and / or include different displays, so that the user interface data generated at the source monitoring hub may be incompatible with the target monitoring hub. In such an embodiment, the target monitoring hub may generate user interface data corresponding to the historical physiological data, as described in box 553.

[0253] Figure 5Dis a flowchart showing an example process 500D associated with transferring physiological monitoring from a source monitoring hub to a target monitoring hub. One or more hardware processors may perform process 500D or portions thereof. Process 500D or portions thereof may be implemented on one or more computing devices described herein, such as a source monitoring hub, a target monitoring hub, a server, etc. Process 500D or portions thereof may be performed by one or more hardware processors of a single computing device. Process 500D or portions thereof may be performed by one or more hardware processors of a plurality of computing devices, such as computing devices that are remote from each other and / or wirelessly communicate with each other. In some embodiments, one or more hardware processors associated with a source monitoring hub may perform process 500D or portions thereof. Process 500D is provided as an example and is not intended to limit the present disclosure. In some embodiments, one or more hardware processors that perform process 500D may omit portions of process 500D, may add additional operations, and / or may rearrange the order of operations that perform process 500D.

[0254] At block 561, one or more hardware processors may establish wireless communication between a monitoring hub (eg, a source monitoring hub) and one or more sensors. The wireless communication may include one or more wireless communication protocols including Bluetooth.

[0255] In box 563, one or more hardware processors may transmit wireless configuration data associated with one or more sensors to a remote computing device. One or more hardware processors may transmit wireless configuration data to a server, such as server 106 shown and / or described herein. The wireless configuration data may include data used to establish wireless communication in box 561. The wireless configuration data may include a device address associated with one or more sensors. The wireless configuration data may include a link key associated with one or more sensors. One or more hardware processors may transmit wireless configuration data via one or more wireless communication protocols (e.g., WiFi). In some embodiments, one or more hardware processors may communicate wireless configuration data to one or more sensors. For example, one or more hardware processors may wirelessly transmit wireless configuration data associated with a target monitoring hub to one or more sensors. In some embodiments, one or more hardware processors may transmit wireless configuration data in response to a request to transfer physiological monitoring. In some embodiments, one or more hardware processors may automatically transmit wireless configuration data, for example, when wireless configuration data is generated and / or received from one or more sensors.

[0256] At block 565, the one or more hardware processors may receive physiological data originating from the one or more sensors. The one or more hardware processors may receive the physiological data via wireless communication, such as Bluetooth.

[0257] At box 567, one or more hardware processors may transmit the physiological data to a remote computing device. One or more hardware processors may transmit the physiological data to a server, such as server 106 shown and / or described herein. One or more hardware processors may transmit the physiological data via one or more wireless communication protocols (e.g., WiFi). In some embodiments, one or more hardware processors may transmit the physiological data in response to an event (e.g., a request to transfer physiological monitoring). In some embodiments, one or more hardware processors may automatically transmit the physiological data, for example, upon receiving the physiological data from one or more sensors. One or more hardware processors may transmit the physiological data continuously. One or more hardware processors may transmit the physiological data periodically. One or more hardware processors may transmit the physiological data originating from one or more sensors as a single transmission during a time frame.

[0258] In some embodiments, one or more hardware processors may transmit data associated with physiological data. The data associated with physiological data may include user interface data for presenting a user interface including display indicia of physiological data. The data associated with physiological data may include a signal corresponding to an alarm or prompt generated in response to the physiological data. The data associated with physiological data may include a state associated with an object corresponding to the physiological data.

[0259] Figure 5E is a flowchart illustrating an example process 500E associated with the location of a monitored object. One or more hardware processors may perform process 500E or portions thereof. Process 500E or portions thereof may be implemented on one or more computing devices described herein, such as a source monitoring hub, a target monitoring hub, a server, and the like. Process 500E or portions thereof may be performed by one or more hardware processors of a single computing device. Process 500E or portions thereof may be performed by one or more hardware processors of a plurality of computing devices, such as computing devices that are remote from each other and / or wirelessly communicate with each other. In some embodiments, one or more hardware processors associated with a monitoring hub may perform process 500E or portions thereof. Process 500E is provided as an example and is not intended to limit the present disclosure. In some embodiments, one or more hardware processors that perform process 500E may omit portions of process 500E, may add additional operations, and / or may rearrange the order of operations that perform process 500E.

[0260] Process 500E can help monitor the location of an object. One or more sensors can be connected to an object. For example, an object can wear one or more sensors included as one or more wearable devices. Therefore, the location of one or more sensors can indicate the location of the object. Devices and systems can monitor the location of an object by determining the location of one or more sensors. An environment (e.g., a hospital) can include one or more monitorings dispersed in different locations throughout the environment. When an object moves in the environment while wearing one or more sensors, one or more monitoring hubs in the environment can detect the presence of the sensor using one or more wireless communication protocols such as Bluetooth. The monitoring hub can determine the proximity of one or more sensors to the monitoring hub, for example, based on the signal strength of the wireless signal. In some embodiments, a monitoring hub in the environment can establish wireless communication with one or more sensors worn by the object. The monitoring hub can establish wireless communication based on the proximity of one or more sensors to the monitoring hub. For example, a monitoring hub closest to one or more sensors rather than a monitoring hub far from one or more sensors can establish wireless communication with one or more sensors. Therefore, when an object wearing one or more sensors moves in the environment, one or more monitoring hubs in the environment can automatically terminate and establish wireless communication with one or more sensors based on their proximity to the one or more sensors. Thus, systems and devices may monitor a subject's location based at least on the proximity of one or more sensors worn by the subject to a monitoring hub and / or whether the one or more sensors are in wireless communication with the monitoring hub.

[0261] At block 570, the one or more hardware processors may access the wireless configuration data. The one or more hardware processors may access the wireless configuration data by receiving the wireless configuration data from a remote computing device, such as a server. The one or more hardware processors may access the wireless configuration data from a memory. For example, the one or more hardware processors may access the wireless configuration data from a memory stored on the monitoring hub. The wireless configuration data stored in the memory may have been previously received from a remote computing device. In some embodiments, the one or more hardware processors may receive the wireless configuration data from another monitoring hub via wired or wireless communication. In some embodiments, the one or more hardware processors may receive the wireless configuration data from one or more sensors. In some embodiments, the one or more hardware processors may generate at least a portion of the wireless configuration data. For example, during a pairing process with one or more sensors, the one or more hardware processors may generate and / or receive at least a portion of the wireless configuration data from the one or more sensors. In some embodiments, the one or more hardware processors may not generate and / or receive the wireless configuration data during the pairing process.

[0262] At box 571, one or more hardware processors may transmit a signal to initiate wireless communication between the monitoring hub and one or more sensors. The one or more processors may transmit the signal according to a wireless communication protocol such as Bluetooth. The signal may be based at least on the wireless configuration data received at box 570. For example, the signal may include a device access code that may be based on a device address of the wireless configuration data. The device address may be associated with one or more of the one or more sensors. The signal may correspond to a paging process of the Bluetooth protocol. In some embodiments, the signal may correspond to a pairing process of the Bluetooth protocol. For example, the signal may include an inquiry access code corresponding to an inquiry process. In some embodiments, the signal may not correspond to a pairing process.

[0263] At block 573, one or more hardware processors may receive a response signal from one or more sensors. The one or more processors may receive the response signal according to a wireless communication protocol such as Bluetooth. The response signal may correspond to a paging process of the Bluetooth protocol. In some embodiments, the response signal may correspond to a pairing process of the Bluetooth protocol, such as an inquiry process. In some embodiments, the response signal may not correspond to a pairing process.

[0264] Advantageously, according to blocks 571 and 573, the one or more hardware processors may discover the presence of one or more sensors in the vicinity of the one or more sensors based at least on the transmitted and received signals.

[0265] Advantageously, accessing the wireless configuration data at block 570 (e.g., receiving the wireless configuration data from a remote computing device such as a server) can facilitate discovery of the presence and / or proximity of one or more sensors, such as by allowing one or more hardware processors to implement a paging process to discover the presence of one or more sensors. Thus, because the one or more hardware processors can access the wireless configuration data, the one or more hardware processors may not need to implement a pairing process to discover the presence of the one or more sensors. The pairing process may take longer than the paging process, may consume more energy, may require more hardware processing, and may require that the one or more sensors be discoverable in a discovery mode. Thus, by accessing the wireless configuration data, the one or more hardware processors may discover the presence and / or proximity of the one or more sensors in a shorter time using less energy and hardware processing, and may do so regardless of whether the one or more sensors are set to be discoverable in a discovery mode.

[0266] At decision block 575, one or more hardware processors may determine whether one or more sensors are within a threshold proximity of the monitoring hub. The one or more hardware processors may determine the proximity of the one or more sensors to the monitoring hub based at least on a signal strength associated with the one or more sensors (e.g., the signal strength of a response signal received at block 573). A stronger signal strength may correspond to a closer proximity. A weaker signal strength may correspond to a farther proximity. In response to determining that the one or more sensors are within the threshold proximity, the one or more hardware processors may proceed to block 577. In response to determining that the one or more sensors are not within the threshold proximity, the one or more hardware processors may return to block 570.

[0267] At block 577, the one or more hardware processors may optionally establish wireless communication with the one or more sensors. The one or more hardware processors may establish wireless communication according to one or more wireless communication protocols. The one or more hardware processors may establish wireless communication according to a Bluetooth communication protocol. Establishing wireless communication may include establishing a Bluetooth connection (e.g., after a paging process). The one or more hardware processors may establish wireless communication based at least on the wireless configuration data. The one or more hardware processors may establish wireless communication based at least on sending a signal at block 571 and receiving a response signal at block 573.

[0268] At box 579, one or more hardware processors may determine the location of the object based at least on determining the location of the monitoring hub. One or more hardware processors may access location data associated with the monitoring hub. One or more hardware processors may access the location data by retrieving the location data from a memory. One or more hardware processors may access the location data by receiving location data from one or more sensors (e.g., a sensor configured to generate location data, such as a GPS). In some embodiments, the location data may be set by a user and stored in a memory associated with the monitoring hub. The location data may indicate the location of the monitoring hub. The location data may indicate the location of the monitoring hub relative to the environment. As an example, the location data may indicate that the location of the monitoring hub is in a specific area of ​​a building (e.g., a hospital), such as on a specific floor or room. The location data may also indicate the location of one or more sensors (and objects wearing sensors) because one or more sensors may be near the monitoring hub, as determined in box 575.

[0269] In some embodiments, one or more hardware processors executing on the monitoring hub can determine the location of the object. For example, one or more hardware processors can access the location data of the monitoring hub and / or determine the location of the object and transmit the location to a remote computing device. One or more hardware processors can transmit the location data to a server, such as server 106 shown and / or described herein. One or more hardware processors can transmit the location data via one or more wireless communication protocols (e.g., WiFi).

[0270] In some embodiments, one or more hardware processors executing on a computing device (e.g., a server) remote from the monitoring hub can determine the location of the object. For example, the one or more hardware processors can receive an indication that one or more sensors are near the monitoring hub, and / or can receive an indication that the monitoring hub has established wireless communication with the one or more sensors. In response, the one or more hardware processors can determine the location of the object based at least on determining the location of the monitoring hub, such as by retrieving monitored location data from a memory and / or receiving location data of the monitoring hub from the monitoring hub and / or from one or more sensors configured to generate location data.

[0271] Advantageously, in some embodiments, one or more hardware processors may be unable to determine location unless one or more hardware processors have established wireless communication (e.g., a Bluetooth connection) between the monitoring hub and one or more sensors. Determining location in response to establishing wireless communication can improve location monitoring by ensuring that valid location data is used. For example, one or more sensors can establish wireless communication with the closest monitoring hub among multiple monitoring hubs within an environment. Therefore, the location of the monitoring hub that has established wireless communication with the one or more sensors (which may also be closest to the one or more sensors) can be used to determine the location of the one or more sensors and the object. Therefore, determining location in response to establishing wireless communication can improve the accuracy of the location of the monitored object.

[0272] Disclosed herein are various methods involving transferring wireless connections and / or physiological data (e.g., previously collected data) from a first monitoring hub to a second monitoring hub (and in some cases, additionally to a third monitoring hub). Any such disclosed methods and / or features described with respect to any monitoring hub described herein may be applied to other types of monitoring devices, such as monitoring devices that are configured to be safe for a user and receive physiological data from one or more physiological sensors that obtain the user's physiological data. For example, any disclosed method may be used to transfer a wireless connection and / or physiological data (e.g., previously collected data) from a first monitoring device that is configured to be fixed to a portion of a user's body and receive physiological data from a physiological sensor to a second similar monitoring device. Such a monitoring device may be worn by a user (e.g., on a wrist, an arm, or on another portion of the user's body) and may be configured to receive physiological data wirelessly (and / or via a wired connection) from a physiological sensor and may also be configured to communicate wirelessly (and / or via a wired connection) with other devices.

[0273] Example Monitoring Hub

[0274] Figure 6 An example monitoring hub 600 is shown. The monitoring hub 600 can include similar structural and / or operating features to any other monitoring hub discussed herein. In some embodiments, the monitoring hub 600 can operate in a manner similar to any source monitoring hub disclosed herein. In some embodiments, the monitoring hub 600 can operate in a manner similar to any target monitoring hub disclosed herein.

[0275] In some embodiments, the monitoring hub 600 is a portable device. The monitoring hub 600 can communicate with one or more computing devices (e.g., sensors, servers, other monitoring hubs, etc.) via a wireless connection (e.g., via one or more wireless communication protocols (e.g., any wireless communication protocol disclosed herein)). The monitoring hub 600 can include a battery to allow the components of the monitoring hub 600 to operate. The monitoring hub 600 can be configured for wired communication with other devices (e.g., sensors, servers, other monitoring hubs, etc.). The monitoring hub 600 can be configured to receive power via a wired connection to an external power source.

[0276] Figure 6The monitoring hub 600 is shown housed within a bracket 602. The monitoring hub 600 can be removably housed within the bracket 602. For example, the monitoring hub 600 can be removably mechanically engaged with the bracket 602 (e.g., via a friction fit). Advantageously, the bracket 602 can improve the portability and / or mobility of the monitoring hub 600. For example, when housed within the bracket 602, the user can more easily hold and carry the monitoring hub 600. The bracket 602 can also be used to protect the monitoring hub 600 or portions thereof. As another example, as Figure 6 As shown, the bracket 602 can fix the monitoring hub 600 to the bed 604 to facilitate repositioning the monitoring hub 600 and the bed 604 together. For example, a user may be able to move the bed 604 and the monitoring hub 600 together by pushing the bed 604 without having to hold the monitoring hub 600 at the same time. Advantageously, the portability of monitoring facilitates continuous physiological monitoring and / or object mobility. For example, the monitoring hub 600 can continuously monitor the physiological data of an object lying in the bed 604 while the object is transported to a new location (e.g., a different room in a hospital). When the monitoring hub 600 and the bed 604 are repositioned, the monitoring hub 600 can maintain wireless communication with sensors on the object in the bed 604 and wireless communication with the server via a network without unplugging and / or reinserting any connection with the monitoring hub 600. Each monitoring hub 600, 700, and / or 1100 described further below can include similar or identical operational and / or structural features. Bracket 602 may include similar or identical operational and / or structural features as bracket 800 discussed further below.

[0277] Figures 7A-7K Various views of the monitoring hub 700 are shown. The monitoring hub 700 can be similar or identical in some or many respects to any monitoring hub discussed elsewhere herein. For example, the monitoring hub 700 can include any of the features described with respect to any other monitoring hub described herein, and / or the monitoring hub 700 can be configured to operate in any manner as described elsewhere herein with respect to any other monitoring hub described herein. In addition, the monitoring hub 700 can be an embodiment of any monitoring hub described herein.

[0278] The monitoring hub 700 may include, for example, a display 701 on the front of the monitoring hub 700 (see Fig. 7A ). The display 701 may include any features and / or functionality of any other display shown or described elsewhere herein. In some embodiments, the monitoring hub 700 includes a status indicator 703, which may be similar or identical to any or all of the status indicators 304, 314 described elsewhere herein.

[0279] In some embodiments, the monitoring hub 700 is configured to connect to the monitoring hub 700, for example, via a connector port (e.g., at least Figure 7D-7E In some embodiments, the monitoring hub 700 includes an internal power source (e.g., a battery) contained within a portion of the monitoring hub 700 (e.g., a housing of the monitoring hub 700). In some embodiments, the monitoring hub 700 includes an internal power source and also includes a connector port (e.g., connector port 705). Such an embodiment can advantageously allow: the monitoring hub 700 draws power required for operation from the internal power source, despite not being connected to an external power source (e.g., via a cable connected to the connector port 705); the monitoring hub 700 draws power from (e.g., only from) an external power source when connected via a cable; and / or the internal power source of the monitoring hub 700 can be allowed to be charged by an external power source. In some embodiments where the monitoring hub 700 includes an internal power source, the monitoring hub 700 can be configured so that such an internal power source can be charged via inductive charging. The monitoring hub 700 can be configured to operate on an AC and / or DC power source. In some embodiments, the monitoring hub 700 includes an AC power connector port and a DC power connector port separate from the AC power connector port. In some embodiments where the monitoring hub 700 includes an internal power source, such internal power source can have a charge life equal to or greater than 2 hours, 3 hours, or 4 hours. In some embodiments, the monitoring hub 700 includes one or more speakers for emitting sounds, such as alarms, communications from a caregiver (e.g., to inquire about the user / patient's condition, or otherwise communicate with the user / patient), etc. The monitoring hub 700 can include a USB port configured to connect to a USB cable (e.g., such as Figure 7D-7E The USB port 709 shown in the figure) and / or may include an Ethernet port configured to connect to an Ethernet cable (e.g., Figure 7D-7E Ethernet port 707 shown in FIG.

[0280] For example Figure 7FAs shown in , the monitoring hub 700 can have a height of about 10 inches (measured vertically relative to the surface). In some embodiments, the monitoring hub 700 can have a height greater than 10 inches, such as 12 inches, 14 inches or greater. In some embodiments, the monitoring hub 700 can have a height less than 10 inches, such as less than 9 inches, less than 8 inches, or less than 6 inches. The monitoring hub 700 can have a width of about 8 inches (measured horizontally relative to the surface). In some embodiments, the monitoring hub 700 can have a width greater than 8 inches, such as 9 inches, 10 inches or greater. In some embodiments, the monitoring hub 700 can have a width less than 8 inches, such as less than 7 inches, less than 6 inches, or less than 5 inches. The display 701 can have a height of about 9 inches. In some embodiments, the display 701 can have a height greater than 9 inches, such as 10 inches, 11 inches or greater. In some embodiments, the display 701 can have a height less than 9 inches, such as less than 8 inches, less than 7 inches, or less than 6 inches. The display 701 can have a width of about 6 inches. In some embodiments, the display 701 can have a width greater than 6 inches, such as 7 inches, 8 inches, or greater. In some embodiments, the display 701 can have a width less than 6 inches, such as less than 5 inches, less than 4 inches, or less than 3 inches.

[0281] Figures 11A-11C A front view, a rear view, and a side view of another embodiment of a monitoring hub 1100 are shown (respectively). The monitoring hub 1100 can be any other embodiment of a monitoring hub discussed elsewhere herein. In some embodiments, the monitoring hub 1100 is configured to be received and / or supported by the bracket 800. Fig. 11B As shown, monitoring hub 1100 may include an opening 1101 that may receive a portion (eg, a head) of a fastener to allow hub 1100 to be mounted to a surface or object (eg, a wall). Figures 11A-11C A cable connected to the monitoring hub 1100 is shown, but the monitoring hub 1100 can be configured to receive power from an internal power source, for example, which can be charged without being connected to a cable (e.g., via inductive charging). In addition, the monitoring hub 1100 can be configured to receive data via wireless transmission without being connected to a cable.

[0282] Figures 12A-12MVarious views of monitoring hub 1200 are shown. Monitoring hub 1200 can be similar or identical in some or many respects to any monitoring hub discussed elsewhere herein. For example, monitoring hub 1200 can include any features described with respect to any other monitoring hub described herein, and / or monitoring hub 1200 can be configured to operate in any manner as described elsewhere herein with respect to any other monitoring hub described herein. In addition, monitoring hub 1200 can be an embodiment of any monitoring hub described herein.

[0283] The monitoring hub 1200 may include, for example, a display 1201 on the front of the monitoring hub 1200 (see Fig. 12A ). Display 1201 may include any features and / or functionality of any other display shown or described elsewhere herein. In some embodiments, monitoring hub 1200 includes status indicator 1203, which may include similar structural and / or operational features to any or all of the status indicators described elsewhere herein.

[0284] In some embodiments, the monitoring hub 1200 can be connected to the monitoring hub 1200, for example, via a connector port (e.g., at least Fig.12E , 12F , 12J) receives power from an external power source. Monitoring hub 1200 can be configured to operate on AC and / or DC power. In some embodiments, monitoring hub 1200 includes an AC power connector port and a DC power connector port separate from the AC power connector port.

[0285] Monitoring hub 1200 may include a USB port configured to connect to a USB cable (e.g., at least Fig.12E , 12F , USB port 1209 shown in 12J), and / or may include an Ethernet port configured to connect to an Ethernet cable (e.g., at least as shown in Fig.12E , 12F , Ethernet port 1207 shown in 12J).

[0286] The monitoring hub 1200 may include an auxiliary port 1206 .

[0287] In some embodiments, the monitoring hub 1200 includes one or more speakers for emitting sounds, such as alarms, communications from caregivers (e.g., inquiring about the status of a user / patient, or otherwise communicating with a user / patient), and the like.

[0288] The monitoring hub 1200 may include one or more sensor ports 1211. The monitoring hub may include more than three sensor ports 1211. The monitoring hub may include six sensor ports 1211. The monitoring hub 1200 may include one, two, three, four, five, six, seven, eight, nine or more than nine sensor ports 1211. The sensor port 1211 may be configured to be connected to one or more sensors via a wired connection. The monitoring hub 1200 may receive physiological data from one or more sensors via the sensor port 1211. The sensor port 1211 may receive ECG data, heart rate data, blood oxygenation data, blood pressure data, EEG data, body temperature data, respiratory data, etc. Each sensor port 1211 may receive different types of physiological data from other sensor ports 1211. For example, a first sensor port 1211 may receive ECG data, while another sensor port 1211 may receive SpO2 data. The sensor port may receive multiple different types of physiological data simultaneously. A single sensor port 1211 may be configured to receive one or more types of sensors. A single sensor port 1211 may be configured to receive one or more types of physiological data. For example, a sensor port 1211 may receive blood pressure data via a wired connection to a blood pressure sensor, and then, after unplugging and plugging the corresponding sensor into the sensor port 1211, the same sensor port 1211 may receive ECG data via a wired connection to an ECG sensor.

[0289] For example, at least Figure 12G-12L As shown in , the monitoring hub 1200 may include a status indicator 1203. The status indicator 1203 may include one or more LEDs. The status indicator 1203 may emit light having one or more colors. The monitoring hub 1200 may include a curved portion 1213. The status indicator 1203 may be located on the curved portion 1213. The curved portion 1213 may protrude from a portion of the housing of the monitoring hub 1200. The curved portion 1213 may not be coplanar with the display 1201. The status indicator 1203 may be located on the curved portion 1213 so that the status indicator 1203 is located in a different plane than the display 1201. The status indicator 1203 may be located at one end of the curved portion 1213. The curved portion 1213 may include an edge of the monitoring hub 1200. The status indicator 1203 may be located on an edge of the monitoring hub 1200. The status indicator 1203 may be visible from multiple angles, which may improve physiological monitoring of the patient because the caregiver may be able to see the status indicator 1203 from multiple locations around the monitoring hub 1200. The status indicator 1203 may be visible from the front or back of the monitoring hub 1200 (e.g., Figures 12G-12HThe status indicator 1203 may be visible from the top or bottom of the monitoring hub 1200 (e.g. Figures 12I-12J The status indicator 1203 may be visible from the left or right side of the monitoring hub 1200 (e.g. Figure 12K-12L shown).

[0290] For example, at least Figure 12M As shown in , the monitoring hub 1200 may include an internal power source (e.g., a battery) contained within a portion of the monitoring hub 1200 (e.g., a housing of the monitoring hub 1200). The monitoring hub 1200 may include a battery housing 1217 that encloses the battery within the monitoring hub 1200. In some embodiments, the monitoring hub 1200 includes an internal power source and also includes a connector port (e.g., connector port 1205). Such embodiments may advantageously allow: the monitoring hub 1200 to draw power required for operation from the internal power source despite not being connected to an external power source (e.g., via a cable connected to the connector port 1205); the monitoring hub 1200 to draw power from (e.g., only from) an external power source when connected via a cable; and / or may allow the internal power source of the monitoring hub 1200 to be charged by the external power source. In some embodiments where the monitoring hub 1200 includes an internal power source, the monitoring hub 1200 may be configured such that such an internal power source can be charged via inductive charging. In some embodiments where monitoring hub 1200 includes an internal power source, such internal power source may have a charge life equal to or greater than 2 hours, 3 hours, or 4 hours.

[0291] For example, at least Figure 12MAs shown in , the monitoring hub 1200 may include a heat sink 1215. The heat sink 1215 may be formed of a metal and / or a metal alloy. The heat sink 1215 may dissipate heat from an internal area of ​​the monitoring hub 1200 to an external area of ​​the monitoring hub 1200. The heat sink 1215 may be located near an internal power source. The heat sink 1215 may be located near a battery housing 1217. A portion of the heat sink 1215 may be exposed to an external area of ​​the monitoring hub 1200. A portion of the heat sink 1215 may not be exposed and / or may be disposed within an internal area of ​​the monitoring hub 1200. The heat sink 1200 may dissipate heat energy from a battery within the battery housing 1217 to an external area of ​​the monitoring hub 1200. Advantageously, the heat sink 1215 may provide passive cooling for the monitoring hub 1200. Advantageously, the heat sink 1215 may eliminate the need to implement an active cooling system (e.g., a fan), which may be noisy and consume more energy. In some embodiments, the heat sink 1215 can contact the battery housing 1217. The heat sink 1215 can be removably connected to the monitoring hub 1200. In some embodiments, only the heat sink 1215 can enclose or cover the battery housing 1217 within the interior area of ​​the monitoring hub 1200. In some embodiments, the heat sink 1215 can form a portion of the housing of the monitoring hub 1200. In some embodiments, the heat sink 1215 can cover or enclose the interior area of ​​the monitoring hub 1200.

[0292] The heat sink 1215 may include one or more through holes 1219. The heat sink 1215 may include less than five through holes 1219, less than four through holes 1219, less than three through holes 1219, or less than two through holes 1219. The heat sink 1215 may include four through holes 1219. The through holes 1219 may receive one or more screws, nails, fasteners, etc. The heat sink 1215 may be fixed to the monitoring hub 1200 through the through holes 1219. In some embodiments, the user may remove the heat sink 1215 from the monitoring hub 1200 simply by removing the screws from the through holes 1219. In some embodiments, the user may connect the heat sink 1215 to the monitoring hub 1200 simply by placing the screws into the through holes 1219. Advantageously, the user may easily remove and replace the heat sink 1215 from the monitoring hub 1200. Advantageously, the user may easily access the battery housing 1217 by simply removing the heat sink 1215. A user may desire to periodically replace the internal power source enclosed by battery housing 1217. A user may easily replace the internal power source simply by removing and replacing heat sink 1215, as described herein.

[0293] For example, at least Figure 12GAs shown in , the monitoring hub 1200 may include a glass portion 1221. The glass portion 1221 may be located between the curved portion 1213 and the display 1201. The curved portion 1213 may be formed of metal. The curved portion 1213 may be formed of aluminum. Metal may affect the operation of wireless components. For example, metal may detune the antenna. Therefore, placing components configured for wireless communication near metal may adversely affect the operation of the wireless communication components. In some embodiments, the monitoring hub 1200 may include components configured for wireless communication, such as antennas, transceivers, radio devices, pairing devices, etc., which may be placed in an internal area of ​​the adjacent glass portion 1221 of the monitoring hub 1200. Therefore, wireless transmission from one or more wireless communication components may occur through the glass portion 1221, which can improve the quality of wireless transmission. In addition, placing the wireless communication component adjacent to the glass portion 1221 can increase the distance between the wireless communication component and the metal (e.g., the metal of the curved portion 1213 and / or the metal in other parts of the frame or housing of the monitoring hub 1200).

[0294] For example Figure 12G As shown in , the monitoring hub 1200 can have a height of about 21 inches (measured vertically relative to the surface). In some embodiments, the monitoring hub 1200 can have a height greater than 21 inches, such as 23 inches, 26 inches, or greater. In some embodiments, the monitoring hub 1200 can have a height less than 21 inches, such as less than 18 inches, less than 15 inches, or less than 12 inches. The monitoring hub 1200 can have a width of about 15 inches (measured horizontally relative to the surface). In some embodiments, the monitoring hub 1200 can have a width greater than 15 inches, such as 17 inches, 19 inches, or greater. In some embodiments, the monitoring hub 1200 can have a width less than 15 inches, such as less than 13 inches, less than 11 inches, or less than 9 inches. The display 1201 can have a height of about 19 inches. In some embodiments, the display 1201 can have a height greater than 19 inches, such as 20 inches, 21 inches, or greater. In some embodiments, the display 1201 can have a height of less than 19 inches, such as less than 18 inches, less than 17 inches, or less than 16 inches. The display 1201 can have a width of about 11 inches. In some embodiments, the display 1201 can have a width greater than 11 inches, such as 12 inches, 13 inches, or greater. In some embodiments, the display 1201 can have a width less than 11 inches, such as less than 10 inches, less than 9 inches, or less than 8 inches.

[0295] Bracket

[0296] Figures 8A-8BThe monitoring hub 700 is shown attached to a bracket 800. The bracket 800 can advantageously receive and enclose portions of the monitoring hub 700, and can be used to protect the monitoring hub 700. The bracket 800 can also advantageously allow the monitoring hub 700 to be more easily carried (e.g., by a caregiver in a medical setting) and / or placed on a surface (e.g., a table, bed, chair, desk) so that the display of the monitoring hub 700 is visible. Additionally, in some embodiments, the bracket 800 can be configured to be secured to a portion of a patient's bed (and / or other object), as discussed further below.

[0297] Figure 8C The monitoring hub 700 and the bracket 800 are shown detached from each other. The bracket 800 is sized to receive any of the example monitoring hubs shown and / or described herein.

[0298] refer to Figure 8D-8O , the bracket 800 may include a base 802. The base 802 may be configured to receive and removably secure the monitoring hub 700, for example, in such a manner that when the hub 700 is received and secured by the base 802, the display of the hub 700 is visible (see, for example, Fig. 8A ). The support 800 may include one or more arms that are configured to interact with other objects and / or surfaces. For example, such one or more arms may be configured to: removably secure to a portion of a bed or chair, as well as other objects, such as poles, rails, etc.; and / or rest on a surface to operably position the support 800 (and the monitoring hub 700 when placed in the support 800), for example, so that the front of the support 800 is placed away from such a surface (which can allow the display of the hub 700 to be visible when secured in the support 800). For example, at least with reference to Figure 8D-8O , the stand 800 may include an arm 804 (which may be referred to as a "stand") extending outwardly from the base 802. The arm 804 may extend laterally (non-parallel) relative to the base 802, which may allow the stand 800 to rest on a surface (e.g., a table or desk) in one position. The arm 804 may be oriented non-parallel relative to the base 802, such that when the arm 804 is positioned on a support surface (e.g., a table, desk, etc.), the base 802 is oriented non-parallel (and / or non-perpendicular) relative to such a support surface. This may advantageously make the hub 700 more accessible and / or the display of the hub 700 more visible when the stand 800 is resting on the support surface.

[0299] Also like Figure 8D-8O As shown, the support 800 may include an arm 806. The arm 806 may be configured to be removably secured to a portion of a bed or chair. For example, the arm 806 may be configured to "hook" onto a portion of a bed, such as Figure 6 600, support 602 and bed 604. Arm 806 may include a first portion extending outwardly from base 802 and a second portion connected to such first portion and transverse to such first portion. In some embodiments, arms 804, 806 are integral with base 802. Arms 804, 806 may form a single integrated unit with base 802. Arms 804, 806 may be fixed relative to base 802. Arms 804, 806 may be non-adjustable. Arms 804, 806 may be configured not to adjust relative to base 802. Arms 804, 806 may be rigid. In some optional embodiments, one or both of arms 804, 806 may be pivotally connected to base 802, which may allow the orientation of arms 804 and / or arms 806 to change between multiple positions relative to base 802. With the arm 806 pivotally connected to the base 802, the inclination of the stand 800 relative to the surface supporting the arm 806 can be changed, which in turn can adjust the inclination of the monitoring hub 700 when attached to the stand 800 (and, for example, the display of the stand 700). The arms 804, 806 can help to orient the stand 800 in a variety of orientations. For example, the stand 800 can rest on a surface by resting on the arm 804, or by resting on the arm 806, or by resting on both the arms 804 and 806 (e.g., in a horizontal position).

[0300] In some embodiments, arm 804 has a first end connected to a first portion of base 802 and a second end connected to a second portion of base 802, thereby forming a loop of stent 800, such as at least Figure 8F-8I . In some embodiments, the arm 806 includes a first end connected to a first portion of the base 802 and a second end connected to a second portion of the base 802, thereby forming a loop of the bracket 800. In some such embodiments, the bracket 800 includes a rod 807 extending between portions of the arm 806, the rod 807 separating such a loop formed by the arm 806. Such a rod 807 can be grasped by a user carrying the bracket 800 (and the hub 700 when received by the bracket 800). In some embodiments, the arm 806 includes a hook that allows the arm 806 to be at least partially wrapped around and / or rest on an object and / or surface. For example, the arm 806 may include a first portion connected to the base 802 and a second portion connected to such first portion and transverse (non-parallel) relative to such first portion. Such a configuration can advantageously allow the arm 806 to be secured to various support structures, such as Figure 6 A wall assembly, or column, railing or other support structure is shown at the end of a hospital bed.

[0301] In some embodiments, the bracket 800 is configured so that when the arm 806 is wrapped around the top of the support structure (e.g., Figure 6 When the base 802 is positioned about a wall at the foot of the hospital bed as shown and / or resting on top of a support structure, the arm 806 contacts the support structure (e.g., a side surface of the support structure) and operably positions the base 802 away from the support structure.

[0302] In some embodiments, the bracket 800 is configured so that when the arm 806 is wrapped around the top of the support structure (e.g., Figure 6 When the support structure is wrapped around the wall at the end of the hospital bed (e.g., the wall at the end of the hospital bed shown) and / or resting on the top of the support structure, the arm 806 contacts the support structure and operably positions the base 802 so that the base 802 is oriented generally parallel with respect to a plane extending along the support structure (e.g., a plane extending along the side surface of the support structure). Such a "support structure" can generally be perpendicular to a ground surface (e.g., the floor of a patient room or home). In some embodiments, the bracket 800 is configured so that when the arm 806 is wrapped around the top of the support structure (e.g., as shown in FIG. 1 ), the bracket 800 can be placed on the top of the support structure (e.g., the wall at the end of the hospital bed shown). Figure 6 When positioned about a wall at the foot of the hospital bed shown and / or resting on top of a support structure, the arm 806 contacts the support structure and operably positions the base 802 to be approximately perpendicular to the floor surface, within 30 degrees of perpendicular to the floor surface, within 20 degrees of perpendicular to the floor surface, or within 10 degrees of perpendicular to the floor surface.

[0303] The bracket 800 can be made of a variety of materials, such as rigid plastics and other materials. In some embodiments, the bracket 800 includes an overmold of a soft material covering a more rigid base material of the bracket 800. In some embodiments, portions of the bracket 800 can include materials that facilitate gripping (e.g., silicon and / or rubber), such as Figures 8A-8O In some embodiments, the bracket 800 includes one or more bumps 805 extending outward from the surface of the base 802, which can help the user grasp the bracket 800 (e.g., with the user's fingers), at least as shown in the shaded portion appearing in the bracket 800 (which contrasts with other unshaded portions of the bracket 800). Figure 8F-8I and 8K as shown.

[0304] Installing Components

[0305] Any of the monitoring hubs discussed herein may be mounted to a variety of objects and / or surfaces in a variety of ways. Figures 9A-9M A mounting assembly 900 (or portion thereof) is shown that can allow the monitoring hub 700 (or any other monitoring hub shown and / or described herein) to be secured to a surface (e.g., a wall) or another object (e.g., a support arm that is itself mounted to a surface (e.g., a wall)). Figures 10A-10K Another embodiment of a mounting assembly 1000 (or a portion thereof) is shown, which can allow the monitoring hub 700 (or any other monitoring hub shown and / or described herein) to be fixed to a surface (e.g., a wall) or another object (e.g., a support arm that is itself mounted to a surface (e.g., a wall)). The mounting assembly 900, 1000 can include a first portion and a second portion, the first portion being configured to be fixed to a portion of the monitoring hub 700 (e.g., the rear portion of the hub 700) and the second portion being configured to be fixed to a surface or object (e.g., a wall). Such a first portion can be fixed to the monitoring hub 700 via one or more fasteners (e.g., screws, or nails, or magnets), and such a second portion can be fixed to a surface or object (e.g., a wall) via one or more fasteners (e.g., screws, or nails, or magnets). Advantageously, such first and second portions of the mounting assembly 900 can be fixed to each other (e.g., removably fixed) without the need for one or more fasteners (e.g., screws or nails), which can allow for quick attachment and / or removal. Such quick attachment and / or removal of the first and second portions of the mounting assembly 900 can in turn advantageously allow for quick attachment and / or removal of the monitoring hub 700 from an object or surface (e.g., a wall). Such a first portion can be a mounting member 910 (relative to Figures 9A-9M Mounting assembly 900 shown), or mounting member 1010 (relative to Figures 10A-10K Such a second portion may be a mounting member 920 (relative to Figures 9A-9M Mounting assembly 900 shown), or mounting member 1020 (relative to Figures 10A-10K Each of the mounting members 910, 920, 1010, 1020 may also be referred to as a "mounting portion." The mounting assemblies 900 and 1000 are discussed in turn below.

[0306] Figure 9C-9DA rear perspective view and a front perspective view of the mounts 910, 920 disengaged from each other are shown (respectively). The mount 910 may include a base 912 (which may also be referred to as a "body" or "body portion") and one or more arms 914 extending outwardly from the base 912. In the case where the mount 910 includes multiple arms 914, such multiple arms 914 may be separated and spaced apart from each other as shown. In some embodiments, the mount 910 includes two arms at a first end of the mount 910 and two additional arms at a second end of the mount 910. In some embodiments, as shown, the arms 914 may each have a first portion 914a connected to the base 912 and a second portion 914b connected to such first portion 914a and transverse to such first portion 924. This can allow the base 912 to be spaced apart from the surface of the hub 700 by a gap that is sized and / or shaped to allow the finger 924 of the mount 920 to engage with a portion of the base 912 and fit between the base 912 and the hub 700 when the mounts 910, 920 and the hub 700 are attached together, such that the second portion 914b is substantially parallel to the base 912 (e.g., along a plane defined by the base 912). The mount 910 can include one or more through holes configured to receive a fastener (e.g., a screw) to allow the mount 910 to be secured to the hub 700 (e.g., via a threaded hole 711 in the hub 700). Such a through hole can be a through hole 911 located in the arm 914. As shown, the mount 910 can include an opening 916 that can interact with a protrusion 928 of the mount 920, as described in more detail below.

[0307] Continue to refer Figure 9C-9D . The mount 920 may include a base 922 (which may also be referred to as a "body" or "body portion"). The mount 920 may also include one or more through holes 921 configured to receive a fastener (e.g., a screw) to allow the mount 920 to be secured to a surface (e.g., a surface of a wall) and / or another object (e.g., a support arm mounted on a wall). In some embodiments, a portion of the base 922 surrounding the hole 921 is recessed relative to a first surface of the base 922 and / or protrudes from an opposing second surface of the base 922. Such a recessed portion may allow the fastener head to be hidden ("countersunk"), and the protruding portion may provide more space between the mounting surface (e.g., a wall), which in turn may provide a user with more space to access a lever 926 of the mount 920 (to allow the mounts 910, 920 to disengage from each other).

[0308] The mount 920 may include structures that allow the mount 920 to be removably attached to the mount 910. For example, the mount 920 may include one or more fingers 924 that may be configured to engage with a portion of the body 912. The fingers 924 may extend from the base 922, for example, proximate the opening 923. In some embodiments, the fingers 924 may be formed by cutting material from the substrate 922 to form the opening 923 and the fingers 924. The fingers 924 may include a first portion and a second portion, the first portion being connected and transverse to the base 923, and the second portion being transverse to such first portion, for example, such that the second portion of the fingers 924 is substantially parallel to the base 922 (e.g., along a plane defined by the base 922). Such a second portion of the fingers 924 may be separated from the base 922 by a gap that is sized to receive a portion of the base 912 of the mount 910.

[0309] The mount 920 may also include a lever 926. The lever 926 may be formed outside of the base 922 (e.g., via cutting a portion of the base 922 to form the opening 925) and / or connected to the base 922. A first end of the lever 926 (which may be referred to as a "connection end") may be connected to the base 922, and a second end of the lever 926 may be "free". Such a "free" end of the lever 926 may be manipulated (e.g., moved) by a user, which may allow the mount 910 to be removed from the mount 920, as further described below. The lever 926 may include a protrusion 928 configured to engage with the opening 916 in the mount 910 and / or a portion of the base 912 proximate to the opening 916. The lever 926 may be movable from a first position in which the lever 926 engages a portion of the mount 910 and a second position in which such engagement is removed. In some embodiments, when the lever 926 is in such a first position, the protrusion 928 of the lever 926 engages a portion of the base 912 proximate the opening 916 and / or is at least partially positioned within and / or passes through the opening 916. When the protrusion 928 is at least partially positioned within and / or passes through the opening 916 and / or contacts a structure surrounding the opening 916, the opening 916 and / or such surrounding structure can present a physical interference that inhibits (e.g., prevents) the mount 910 from being disengaged from the mount 920. When the lever 926 is moved to such a second position, the protrusion 928 can be removed from the opening 916, and such physical interference can be removed, thereby allowing the mount 910 to be disengaged from the mount 920. In some embodiments, the lever 926 is biased so that when the mount 910 is vertically inserted into the mount 920 (e.g., the base 912 is inserted between the fingers 924), the protrusion 928 contacts a surface of the base 912 and snaps into engagement with the opening 916. If at least Figure 9C-9DAs shown, in some embodiments, the "free" end of the lever 926 (which may also be referred to as the "actuation end") is curved, for example, away from the surface or plane of the remainder of the lever 926 and / or the base 922. When the mounting members 910, 920 are attached to each other and / or to a surface (e.g., a wall), such an embodiment can advantageously provide a user with more space to access the lever 926. In some embodiments, the protrusion 928 includes a semicircular shape. In some embodiments, the opening 927 includes a semicircular shape. In some embodiments, the opening 916 includes a semicircular shape. In some embodiments, a portion of the base 912 within the opening 916 (e.g., arranged along the straight edge of the semicircular opening 916) is convex.

[0310] Continue to refer Figure 9C-9D , the width of the base 912 of the mounting member 910 can taper at least partially along its height. For example, the base 912 can have a larger width at or near the top of the mounting member 910, and the width tapers to a smaller width at or near the middle portion of the mounting member 910 and / or the bottom end of the mounting member 910 (given that Figure 9C-9D Orientation). Figure 9C-9D As shown, the fingers 924 of the mount 920 can be angled relative to, for example, a vertical line. The fingers 924 can form a pocket that can receive a portion of the mount 910 (e.g., the base 912). In some embodiments, the fingers 924 form a funnel-shaped pocket that is configured to receive a portion of the mount 910 (e.g., the base 912). Such a configuration can advantageously allow the mount 910 (which can be secured to the hub 700) to be vertically secured to the mount 912 by moving the base 912 downward within and / or between the fingers 924, so that the mounts 910, 920 can be connected, as shown. Figure 9K-9M It should be noted that Figure 9K-9M The mounting members 910, 920 are shown connected to each other, and the hub 700 is not shown to more clearly show how the mounting members 910, 920 can be positioned when fixed to each other. In one example method: the mounting member 910 is fixed to the hub 700, such as via a screw, which is inserted through the hole 911 in the arm 914 and into the threaded hole 711 in the hub 700 (see Figures 9E-9F); the mount 920 is secured to a wall or other object via screws inserted through the holes 921; and the hub 700 and the mount 910 are secured to the mount 920, for example, by positioning the base 912 vertically within the fingers 924 of the mount 920. In some embodiments, a portion of the lever 926 can engage with a portion of the mount 910 when the mounts 910, 920 are connected to each other. For example, the protrusion 928 can be positioned within the opening 916 of the mount 910 and / or can engage with a structure surrounding the opening 916. Such engagement of the lever 926 with a portion of the mount 910 can inhibit (e.g., prevent) the mounts 910, 920 from being separated from each other. When separation is desired, the lever 926 can be actuated (e.g., by moving the free end of the lever 926 in a direction generally perpendicular to the surface or plane of the base 922), which in turn can remove the protrusion 928 from the opening 916, thereby allowing the mount 910 to be separated from the mount 920. In some embodiments, the mount 910 is removed from the mount 920 by moving the mount 910 in a direction opposite to the direction in which the mount 910 is moved to insert the mount 910 into the mount 920. For example, in some embodiments, the mount 910 is connected to the mount 920 by inserting the mount 910 downward into the mount 920, and the mount 910 is separated from the mount 920 by moving the mount 910 upward relative to the mount 920.

[0311] Figures 10A-10D Another embodiment of a mounting assembly 1000 is shown. The mounting assembly 1000 may include mounting members 1010 and 1020. Figures 10C-10D A rear perspective view and a front perspective view are shown (respectively) of the mounts 1010, 1020 disengaged from one another. The mount 1010 may include a base 1012 (which may also be referred to as a "body" or "body portion") and one or more arms 1014 extending from and connected to the base 1012. In some embodiments, the mount 1010 includes two arms, each of which has a portion separated from a portion of the base 1012 by an opening (see Figures 10C-10D ). In some embodiments, as shown, portion 1019 of arm 1014 is curved such that arm 1014 is spaced apart from base 1012 (e.g., a plane along which arm 1014 extends is spaced apart from a plane along which base 1012 extends). Such embodiments can allow base 1012 to be spaced apart from a surface of hub 700 by a gap that is sized and / or shaped to allow finger 1024 of mount 1020 to engage a portion of base 1012 and fit between base 1012 and hub 700 when mounts 1010, 1020, and hub 700 are attached together.

[0312] The mount 1010 can include one or more through holes configured to receive fasteners (e.g., screws) to allow the mount 1010 to be secured to the hub 700 (e.g., via threaded holes 711 in the hub 700). Such through holes can be through holes 1011 located in the arm 1014, as shown. As shown, the mount 1010 can include an opening 1016 that can interact with a protrusion 1028 of the mount 1020, as described in more detail below.

[0313] Continue to refer Figures 10C-10D , the mount 1020 may include a base 1022 (which may also be referred to as a "body" or "body portion"). The mount 1020 may also include one or more through holes 1021 configured to receive a fastener (e.g., a screw) to allow the mount 1010 to be secured to a surface (e.g., a surface of a wall) and / or another object (e.g., a support arm mounted on a wall). In some embodiments, a portion of the base 1022 surrounding the hole 1021 is recessed relative to a first surface of the base 1022 and / or protrudes from an opposing second surface of the base 1022. Such a recessed portion may allow the fastener head to be hidden ("countersunk"), and the protruding portion may provide more space between the mounting surface (e.g., a wall), which in turn may provide more space for a user to access a lever 1026 of the mount 1020 (to allow the mounts 1010, 1020 to be disengaged from each other).

[0314] The mount 1020 may include structures that allow the mount 1010 to be removably attached to the mount 1020. For example, the mount 1020 may include one or more fingers 1024 that may be configured to engage with a portion of the body 1012. The fingers 1024 may extend from the base 1022, such as at the opening 1025. In some embodiments, the fingers 1024 may be formed by cutting material from the base 1022 to form the opening 1025 and the fingers 1024. The fingers 1024 may include a first portion that is connected to and transverse to the base 1022 and a second portion that is transverse to such first portion, such that the second portion of the fingers 1024 is substantially parallel to the base 1022 (e.g., along a plane defined by the base 1022). Such a second portion of the fingers 1024 may be separated from the base 1022 by a gap that is sized to receive a portion of the base 1012 of the mount 1010.

[0315] The mount 1020 may also include a lever 1026. The lever 1026 may be formed out of the base 1022 (e.g., via cutting a portion of the base 1022 to form the opening 1025) and / or connected to the base 1022. A first end of the lever 1026 (which may be referred to as a "connection end") may be connected to the base 1022, and a second end of the lever 1026 may be "free". Such a "free" end of the lever 1026 may be manipulated (e.g., moved) by a user, which may allow the mount 1010 to be removed from the mount 1020, as further described below. The lever 1026 may include a protrusion 1028 configured to engage with the opening 1016 in the mount 1010 and / or a portion of the base 1012 proximate to the opening 1016. The lever 1026 may be moved from a first position in which the lever 1026 engages a portion of the mount 1010 to a second position in which such engagement is removed. In some embodiments, when the lever 1026 is in such a first position, the protrusion 1028 of the lever 1026 engages a portion of the base 1012 proximate the opening 1016 and / or is at least partially positioned within and / or passes through the opening 1016. When the protrusion 1028 is at least partially positioned within and / or passes through the opening 1016 and / or contacts a structure surrounding the opening 1016, the opening 1016 and / or such surrounding structure can present a physical interference that inhibits (e.g., prevents) the mount 1010 from being disengaged from the mount 1020. When the lever 1026 is moved to such a second position, the protrusion 1028 can be removed from the opening 1016, and such physical interference can be removed, thereby allowing the mount 1010 to be disengaged from the mount 1020. In some embodiments, lever 1026 is biased so that when mount 1010 is vertically inserted into mount 1020 (e.g., base 1012 is inserted between fingers 1024), protrusion 1028 contacts a surface of base 1012 and snaps into engagement with opening 1016. Figures 10C-10D As shown, in some embodiments, the "free" end of the lever 1026 (which may also be referred to as the "actuation end") is curved, for example, away from the surface or plane of the remainder of the lever 1026 and / or the base 1022. When the mounting members 1010, 1020 are attached to each other and / or to a surface (e.g., a wall), such an embodiment can advantageously provide a user with more space to access the lever 1026. In some embodiments, the protrusion 1028 includes a semicircular shape. In some embodiments, the opening 1027 includes a semicircular shape. In some embodiments, the opening 1016 includes a semicircular shape. In some embodiments, a portion of the base 1012 within the opening 1016 (e.g., arranged along the straight edge of the semicircular opening 1016) is convex.

[0316] Continue to refer Figures 10C-10D , the width of the base 1012 of the mounting member 1010 can taper at least partially along its height. For example, the base 1012 can have a larger width at or near the top of the base 1012, and the width tapers to a smaller width at or near the middle portion of the base 1012 and / or at or near the bottom of the base 1012 (given that Figures 10C-10D Orientation). Figures 10C-10D As shown, the fingers 1024 of the mount 1020 can be angled, for example, relative to a vertical line. The fingers 1024 can form a pocket that can receive a portion of the mount 1010 (e.g., the base 1012). In some embodiments, the fingers 1024 form a funnel-shaped pocket that is configured to receive a portion of the mount 1010 (e.g., the base 1012). Such a configuration can advantageously allow the mount 1010 (which can be secured to the hub 700) to be vertically secured to the mount 1002 by moving the base 1012 downward within and / or between the fingers 1024, so that the mounts 1010, 1020 can be connected, as shown. Figure 10G-10K It should be noted that Figures 10I-10K The mounts 1010, 1020 are shown connected to one another, and the hub 700 is not shown, to more clearly illustrate how the mounts 1010, 1020 may be positioned when secured to one another.

[0317] In one example method, the mount 1010 is secured to the hub 700, for example, via a screw that is inserted through a hole 1011 in the arm 1014 and into a threaded hole 711 in the hub 700 (see Figures 10E-10F); the mount 1020 is secured to a wall or other object via screws that are inserted through holes 1021; and the hub 700 and the mount 1010 are secured to the mount 1020, for example, by vertically positioning the base 1012 within the fingers 1024 of the mount 1020. In some embodiments, a portion of the lever 1026 can engage a portion of the mount 1010 when the mounts 1010, 1020 are connected to each other. For example, the protrusion 1028 can be positioned within the opening 1016 of the mount 1010 and / or can engage with a structure surrounding the opening 1016. Such engagement of the lever 1026 with a portion of the mount 1010 can inhibit (e.g., prevent) the mounts 1010, 1020 from being separated from each other. When separation is desired, the rod 1026 can be actuated (e.g., by moving the free end of the rod 1026 in a direction generally perpendicular to the surface or plane of the base 1022), which in turn can remove the protrusion 1028 from the opening 1016, thereby allowing the mount 1010 to be separated from the mount 1020. In some embodiments, the mount 1010 is removed from the mount 1020 by moving the mount 1010 in a direction opposite to the direction in which the mount 1010 was moved to insert the mount 1010 into the mount 1020. For example, in some embodiments, the mount 1010 is connected to the mount 1020 by inserting the mount 1010 downwardly into the mount 1020, and the mount 1010 is separated from the mount 1020 by moving the mount 1010 upwardly relative to the mount 1020.

[0318] Although certain embodiments of mounts 920, 1020 are described above as including levers 926, 1026, in some variations, mounts 920, 1020 do not include levers 926, 1026. In such variations, mounts 920, 1020 may be connected to and support mounts 910, 1010 (respectively), which in turn may be connected to hub 700. In some such variations, mounts 910, 1010 may be supported (e.g., vertically) by mounts 920, 1020 (respectively), but may allow for removal of mounts 910, 1010 (e.g., by moving vertically upward or in a direction opposite to the direction in which the mounts were inserted / connected) without requiring additional steps (e.g., "unlocking" of a lever). Furthermore, while the fingers 924, 1024 of the mounts 920, 1020 are described as being angled, and the bases 912, 1012 of the mounts 910, 1010 are described as having a tapered width (at least for a portion of their height), alternative embodiments are possible that allow the bases 912, 1012 to be received and / or supported (e.g., vertically supported) by the fingers 924, 1024. For example, in some variations, the fingers 924, 1024 may form a pocket sized and / or shaped to receive and / or support the bases 912, 1012.

[0319] In some variations, mounting member 910 is integral with monitoring hub 700 (eg, integrally formed in a housing of hub 700). In some variations, mounting member 1010 is integral with monitoring hub 700 (eg, integrally formed in a housing of hub 700).

[0320] Additional Implementations

[0321] As used herein, "real-time" or "substantially real-time" may refer to events (e.g., reception, processing, transmission, display, etc.) that occur simultaneously or substantially simultaneously (e.g., ignoring any small delays, such as those that are imperceptible to humans and / or insignificant, such as delays caused by electrical conduction or transmission). As a non-limiting example, "real-time" may refer to events that occur within a time frame of each other, the time frame being on the order of milliseconds, seconds, tens of seconds, or minutes. For example, "real-time" may refer to events that occur within a time frame of less than 1 minute, less than 30 seconds, less than 10 seconds, less than 1 second, less than 0.05 seconds, less than 0.01 seconds, less than 0.005 seconds, less than 0.001 seconds, etc. In some embodiments, "real-time" may refer to an event that occurs simultaneously with or during another event.

[0322] As used herein, "systems," "apparatus," "device," and "device" generally include hardware (eg, mechanical and electronic) and, in some embodiments, associated software (eg, a dedicated computer program for graphic control) components.

[0323] It should be understood that not all objects or advantages may be achieved according to any particular embodiment described herein. Thus, for example, those skilled in the art will recognize that certain embodiments may be configured to operate in a manner that achieves or optimizes one advantage or a group of advantages as taught herein without necessarily achieving other objects or advantages as taught or suggested herein.

[0324] Each of the processes, methods, and algorithms described in the previous sections can be embodied in a code module executed by one or more computer systems or computer processors including computer hardware, and fully or partially automated by the code module. The code module can be stored on any type of non-transitory computer-readable medium or computer storage component, such as a hard drive, solid-state memory, optical disk, etc. The system and module can also be transmitted as a generated data signal (e.g., as part of a carrier or other analog or digital propagation signal) on various computer-readable transmission media, including wireless-based and wired / cable-based media, and can take various forms (e.g., as part of a single or multiplexed analog signal, or as multiple discrete digital packets or frames). The process and algorithm can be implemented in part or in whole in a dedicated circuit. The results of the disclosed process and process steps can be stored persistently or otherwise in any type of non-transitory computer storage device, such as, for example, a volatile or non-volatile storage device.

[0325] Many other variations beyond those described herein will be apparent from the present disclosure. For example, depending on the implementation, certain actions, events, or functions of any algorithm described herein may be performed in a different order, may be added, merged, or completely omitted (e.g., not all described actions or events are necessary for the practice of the algorithm). In addition, in some embodiments, actions or events may be performed simultaneously, for example, by multithreading, interrupt handling, or multiple processors or processor cores, or on other parallel architectures, rather than sequentially. In addition, different tasks or processes may be performed by different machines and / or computing systems that can work together.

[0326] Various illustrative logic blocks, modules and algorithm elements described in conjunction with the embodiments disclosed herein can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules and elements have been generally described herein according to their functions. Whether such functions are implemented as hardware or software depends on specific applications and the design constraints imposed on the entire system. The described functions can be implemented in different ways for each specific application, but such implementation decisions should not be interpreted as causing deviations from the scope of the present disclosure.

[0327] The various features and processes described herein can be used independently of each other, or can be combined in various ways. All possible combinations and sub-combinations are intended to fall within the scope of the present disclosure. In addition, certain method or process blocks can be omitted in some embodiments. The methods and processes described herein are also not limited to any particular order, and the blocks or states associated therewith can be performed in other appropriate orders. For example, the blocks or states described can be performed in a different order than that specifically disclosed, or multiple blocks or states can be combined in a single block or state. Example blocks or states can be performed in series, in parallel, or in some other way. Blocks or states can be added to or removed from the disclosed example implementations. The example systems and components described herein can be configured in a manner different from that described. For example, elements can be added, removed, or rearranged compared to the disclosed example implementations.

[0328] The various illustrative logic blocks and modules described in conjunction with the embodiments disclosed herein may be implemented or performed by a machine, such as a general purpose processor, a digital signal processor ("DSP"), an application specific integrated circuit ("ASIC"), a field programmable gate array ("FPGA") or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative embodiment, the processor may be a controller, a microcontroller, or a state machine, a combination thereof, or the like. The processor may include a circuit configured to process computer executable instructions. In another embodiment, the processor includes an FPGA or other programmable device that performs logical operations but does not process computer executable instructions. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration. Although primarily described herein with respect to digital technology, the processor may also primarily include analog components. For example, some or all of the signal processing algorithms described herein may be implemented in analog circuits or mixed analog and digital circuits. The computing environment may include any type of computer system, including but not limited to a microprocessor-based computer system, a mainframe computer, a digital signal processor, a portable computing device, a device controller or a computing engine within a device, etc.

[0329] The elements of the methods, processes or algorithms described in conjunction with the embodiments disclosed herein may be directly embodied in hardware, software modules stored in one or more memory devices and executed by one or more processors, or a combination of the two. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disks, removable disks, CD-ROMs, or any other form of non-temporary computer-readable storage media, media, or physical computer memory known in the art. An example storage medium may be connected to a processor so that the processor can read information from the storage medium and write information to the storage medium. In an optional solution, the storage medium may be integrated into the processor. The storage medium may be volatile or non-volatile. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In an optional solution, the processor and the storage medium may reside in a user terminal as discrete components.

[0330] Conditional language, such as "can," "could," "might," or "may," etc., unless otherwise specifically stated or understood otherwise in the context of use, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements, and / or steps. Thus, such conditional language is generally not intended to imply that features, elements, and / or steps are in any way required for one or more embodiments, or that one or more embodiments necessarily include logic for determining, with or without user input or prompting, whether such features, elements, and / or steps are included or will be performed in any particular embodiment.

[0331] Unless specifically stated otherwise, disjunctive language (e.g., the phrase "at least one of X, Y, or Z") is understood in context as generally used to present an item, term, etc. that can be X, Y, or Z, or any combination thereof (e.g., X, Y, and / or Z). Thus, such disjunctive language is generally not intended to, and should not, imply that certain embodiments require the presence of at least one X, at least one Y, or at least one Z, respectively.

[0332] The language of degree used herein, such as the terms "approximately", "about", "roughly", and "substantially" used herein, refers to a value, amount, or feature that is close to the stated value, amount, or feature, which still performs the desired function or achieves the desired result. For example, the terms "approximately", "about", "roughly", and "substantially" may refer to an amount that is less than 10%, less than 5%, less than 1%, less than 0.1%, and less than 0.01% of the stated amount. As another example, in some embodiments, the terms "roughly parallel" and "substantially parallel" refer to a value, amount, or feature that deviates from exact parallelism by less than or equal to 10 degrees, 5 degrees, 3 degrees, or 1 degree. As another example, in some embodiments, the terms "roughly perpendicular" and "substantially perpendicular" refer to a value, amount, or feature that deviates from exact perpendicularity by less than or equal to 10 degrees, 5 degrees, 3 degrees, or 1 degree.

[0333] Any process description, element or block in the flowcharts described herein and / or depicted in the accompanying drawings should be understood to represent a module, segment or portion of code that may include one or more executable instructions for implementing specific logical functions or steps in the process. Alternative implementations are included within the scope of the embodiments described herein, in which elements or functions may be deleted, performed in a sequence other than shown or discussed, including substantially simultaneously or in reverse order, depending on the functions involved, as will be understood by those skilled in the art.

[0334] Unless expressly stated otherwise, articles such as "a" or "an" should generally be interpreted as including one or more of the recited items. Thus, phrases such as "a device configured to..." are intended to include one or more of the recited devices. Such one or more recited devices may also be collectively configured to perform the recited statements. For example, "a processor configured to perform statements A, B, and C" may include a first processor configured to perform statement A working together with a second processor configured to perform statements B and C.

[0335] All methods and processes described herein can be implemented via software code modules executed by one or more general-purpose computers, and can be partially or completely automated. For example, the methods described herein can be performed by a computing system and / or any other suitable computing device. The method can be executed on a computing device in response to the execution of software instructions or other executable codes read from a tangible computer-readable medium. A tangible computer-readable medium is a data storage device that can store data that can be read by a computer system. Examples of computer-readable media include read-only memory, random access memory, other volatile or non-volatile memory devices, CD-ROMs, magnetic tapes, flash drives, and optical data storage devices.

[0336] It should be emphasized that many changes and modifications can be made to the embodiments described herein, and the elements of these embodiments should be understood to be other acceptable examples. All such modifications and changes are intended to be included in the scope of the present disclosure herein. The section titles used herein are provided only to enhance readability, and are not intended to limit the scope of the embodiments disclosed in a particular section to the features or elements disclosed in that section. The foregoing description describes certain embodiments in detail. However, it should be understood that no matter how the foregoing detailed description appears in the text, the system and method can be practiced in a variety of ways. As also described herein, it should be noted that when describing certain features or aspects of the system and method, the use of specific terms should not be considered to imply that the term is redefined herein to be limited to any specific features of the features or aspects of the system and method associated with the term.

[0337] Those skilled in the art will appreciate that information, messages, and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips referenced throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

Claims

1. A monitoring hub configured to monitor the health status of a subject wearing a wireless wearable device, the monitoring hub comprising: One or more hardware computer processors configured to execute a plurality of computer executable instructions to cause the monitoring hub to: In response to a request to establish wireless monitoring of the subject's physiology at the monitoring hub: accessing wireless configuration data for managing wireless communication with a wearable device on a subject, the wireless configuration data including at least one or more device addresses associated with the wearable device, the wireless configuration data being received at the monitoring hub from a remote server; establishing wireless communication between the monitoring hub and the wearable device based at least on the wireless configuration data, so that the monitoring hub wirelessly receives real-time physiological data from the wearable device using one or more wireless communication protocols; receiving historical physiological data from the remote server, the historical physiological data comprising physiological data collected by the wearable device before wireless communication is established between the monitoring hub and the wearable device, the historical physiological data comprising physiological data communicated from the wearable device to another monitoring hub before wireless communication is established between the monitoring hub and the wearable device; and User interface data is generated for presenting a user interface including the real-time physiological data combined with the historical physiological data to reduce a monitoring gap between the historical physiological data and the real-time physiological data.

2. The monitoring hub according to claim 1, wherein the one or more hardware computer processors are further configured to execute the plurality of computer executable instructions so that the monitoring hub establishes the wireless communication between the monitoring hub and the wearable device by establishing a Bluetooth connection between the monitoring hub and the wearable device.

3. A monitoring hub according to any of the preceding claims, wherein the one or more hardware computer processors are further configured to execute the plurality of computer executable instructions so that the monitoring hub establishes the wireless communication between the monitoring hub and the wearable device by establishing the wireless communication without implementing a Bluetooth pairing process.

4. A monitoring hub according to any of the preceding claims, wherein the one or more hardware computer processors are further configured to execute the plurality of computer executable instructions so that the monitoring hub establishes the wireless communication between the monitoring hub and the wearable device in response to user input, the user input comprising contactless user input.

5. The monitoring hub of any one of the preceding claims, wherein the one or more hardware computer processors are further configured to execute the plurality of computer executable instructions such that the monitoring hub: receiving identification data via the monitoring hub using one or more of near field communication (NFC) or radio frequency identification (RFID), the identification data being associated with a user requesting to establish wireless monitoring with the monitoring hub; and Based at least on the identification data, it is determined that the user has authority to establish the wireless monitoring.

6. A monitoring hub according to any of the preceding claims, wherein the one or more hardware computer processors are further configured to execute the plurality of computer executable instructions so that the monitoring hub establishes the wireless communication between the monitoring hub and the wearable device based at least on the proximity of the wearable device to the monitoring hub.

7. A monitoring hub according to any of the preceding claims, wherein the one or more hardware computer processors are further configured to execute the plurality of computer executable instructions so that the monitoring hub accesses the wireless configuration data by wirelessly receiving the wireless configuration data from the remote server.

8. A monitoring hub according to any of the preceding claims, wherein the one or more hardware computer processors are further configured to execute the plurality of computer executable instructions so that the monitoring hub accesses the wireless configuration data based at least on retrieving the wireless configuration data from a memory.

9. A monitoring hub according to any of the preceding claims, wherein the one or more hardware computer processors are further configured to execute the plurality of computer executable instructions so that the monitoring hub presents the user interface via a display of the monitoring hub.

10. A monitoring hub according to any of the preceding claims, wherein the one or more hardware computer processors are also configured to execute the multiple computer executable instructions so that the monitoring hub receives historical user interface data from the remote server, the historical user interface data corresponding to the historical physiological data, and the historical user interface data was previously generated by the other monitoring hub.

11. A method of continuously monitoring a patient wearing a wireless wearable device while changing from a first monitoring hub to a second monitoring hub, the method comprising: In response to a request to establish wireless monitoring of the subject's physiology at the monitoring hub: accessing wireless configuration data for managing wireless communication with a wearable device on a subject, the wireless configuration data including at least one or more device addresses associated with the wearable device, the wireless configuration data being received at the monitoring hub from a remote server; establishing wireless communication between the monitoring hub and the wearable device based at least on the wireless configuration data, so that the monitoring hub wirelessly receives real-time physiological data from the wearable device using one or more wireless communication protocols; receiving historical physiological data from a remote server, the historical physiological data comprising physiological data collected by the wearable device before wireless communication is established between the monitoring hub and the wearable device, the historical physiological data comprising physiological data communicated from the wearable device to another monitoring hub before wireless communication is established between the monitoring hub and the wearable device; as well as User interface data is generated for presenting a user interface including the real-time physiological data combined with the historical physiological data to reduce a monitoring gap between the historical physiological data and the real-time physiological data.

12. The method of claim 11, wherein establishing the wireless communication between the monitoring hub and the wearable device comprises establishing a Bluetooth connection between the monitoring hub and the wearable device without performing a Bluetooth pairing process.

13. The method of claim 11 or 12, further comprising establishing the wireless communication between the monitoring hub and the wearable device in response to a user input, the user input comprising a contactless user input.

14. The method according to any one of claims 11 to 13, further comprising: receiving identification data via the monitoring hub using one or more of near field communication (NFC) or radio frequency identification (RFID), the identification data being associated with a user requesting to establish wireless monitoring with the monitoring hub; as well as Based at least on the identification data, it is determined that the user has authority to establish the wireless monitoring.

15. The method of any of claims 11-14, wherein accessing the wireless configuration data comprises retrieving the wireless configuration data from a memory.

16. The method of any one of claims 11-15, further comprising presenting the user interface via a display of the monitoring hub.

17. The method according to any one of claims 11-16, further comprising receiving historical user interface data from the remote server, the historical user interface data corresponding to the historical physiological data, the historical user interface data being previously generated by the other monitoring hub.

Images