Migrating wireless observations with minimal data loss

Abstract

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

Description

[Technical Field]

[0001] Any and all applications for which a claim of foreign or domestic priority is disclosed in an Application Data Sheet filed herewith are incorporated herein by reference under 37 CFR 1.57. This application claims the benefit of priority to U.S. Provisional Application No. 63 / 370,637, filed August 5, 2022. The disclosure of each of the above-referenced applications is incorporated herein in its entirety for all purposes.

[0002] The present disclosure relates to physiological function monitoring devices, systems, and methods. [Background technology]

[0003] Hospitals, nursing homes, and other patient care facilities typically utilize numerous sensors, devices, and / or monitors to collect or analyze patients' physiological parameters. A variety of conventional sensor systems exist 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 personnel, use the physiological parameters obtained from patient monitors to diagnose illnesses and prescribe treatments. Clinicians also use the physiological parameters to monitor patients in various clinical conditions and to determine whether to increase the level of medical care provided to the patient. Summary of the Invention [Problem to be solved by the invention]

[0004] Some conventional sensor systems require time-consuming and complicated procedures to change the observation of physiological data between display devices. For example, a user may be required to unplug a sensor from a first display device and reinsert the sensor into a second display device. As another example, a user may be required to power off a sensor and then power it on and wirelessly connect it to a different display device. As another example, a user may be required to manually change the pairing status 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. In at least the above examples, changing the observation of physiological data from a first display device to a second display device in conventional sensor systems can be time-consuming, overly complicated and frustrating for users, can lead to user error, and can result in loss of physiological data, such as while the sensor is not connected (e.g., wirelessly and / or wired) to any display device. [Means for solving the problem]

[0005] Various implementations 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 properties described herein. Without limiting the scope of the appended claims, the following description will set forth some prominent features.

[0006] The details of one or more implementations of the subject matter described herein are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, drawings, and claims. It should be noted that the relative dimensions of the following drawings may not be drawn to scale.

[0007] Disclosed herein is a monitoring hub configured to monitor the health status of a subject having 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 a plurality of computer-executable instructions to cause the monitoring hub, in response to a request to establish wireless monitoring of the subject's physiology at the monitoring hub, to access wireless configuration data managing wireless communication with the subject's wearable device, the wireless configuration data comprising 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 one or more hardware processors may be configured to execute a plurality of computer-executable instructions to cause the monitoring hub, in response to the request to establish wireless monitoring of the subject's physiology at the monitoring hub based at least on the wireless configuration data, to establish wireless communication between the monitoring hub and the wearable device to wirelessly receive real-time physiological data from the wearable device using one or more wireless communication protocols. The one or more hardware processors may be configured to execute a plurality of computer-executable instructions to cause the observation hub to receive historical physiological data from a remote server in response to a request to establish wireless observation of the subject's physiology at the observation hub, wherein the historical physiological data comprises physiological data collected by the wearable device prior to establishing wireless communication between the observation hub and the wearable device, and the historical physiological data comprises physiological data communicated from the wearable device to another observation hub prior to establishing wireless communication between the observation hub and the wearable device.The one or more hardware processors may be configured to execute a plurality of computer-executable instructions to cause the observation hub, in response to a request to establish wireless observation of the subject's physiology at the observation hub, to generate user interface data for rendering a user interface including the real-time physiology data in combination with the historical physiology data to reduce observation gaps between the historical physiology data and the real-time physiology data.

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

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

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

[0011] The one or more hardware computer processors may be further configured to execute the plurality of computer-executable instructions to cause the observation hub to receive identification data via the observation 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 a wireless observation with the observation hub. The one or more hardware computer processors may be further configured to execute the plurality of computer-executable instructions to cause the observation hub to determine, based at least on the identification data, that the user is authorized to establish the wireless observation.

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

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

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

[0015] The one or more hardware computer processors may be further configured to execute a plurality of computer-executable instructions to cause the observation hub to render a user interface via a display of the observation hub.

[0016] The one or more hardware computer processors may further be configured to execute a plurality of computer-executable instructions to cause the observation hub to receive past user interface data from a remote server, the past user interface data corresponding to past physiological data, and the past user interface data having been previously generated by another observation hub.

[0017] Disclosed herein is a method for continuously monitoring a patient with a wireless wearable device while changing from a first observation hub to a second observation hub. The method may include, in response to a request to establish wireless monitoring at an observation hub of the subject's physiology, accessing wireless configuration data managing wireless communication with the subject's wearable device, the wireless configuration data comprising at least one or more device addresses associated with the wearable device, the wireless configuration data being received at the observation hub from a remote server. The method may further include establishing wireless communication between the observation hub and the wearable device using one or more wireless communication protocols to cause the observation hub to wirelessly receive real-time physiological data from the wearable device based at least on the wireless configuration data. The method may further include receiving historical physiological data from the remote server, the historical physiological data comprising physiological data collected by the wearable device prior to establishing wireless communication between the observation hub and the wearable device, and the historical physiological data comprising physiological data communicated from the wearable device to another observation hub prior to establishing wireless communication between the observation hub and the wearable device. The method may further comprise generating user interface data for rendering a user interface including the real-time physiological data in combination with the historical physiological data to reduce an observation gap between the historical physiological data and the real-time physiological data.

[0018] In some implementations, establishing the wireless communication between the observation hub and the wearable device comprises establishing a Bluetooth connection between the observation hub and the wearable device without performing a Bluetooth pairing process.

[0019] The method may further comprise establishing said wireless communication between the observation hub and the wearable device in response to a user input, the user input comprising a contactless user input.

[0020] The method may further include receiving identification data via the observation hub using one or more of near field communication (NFC) or radio frequency identification (RFID), the identification data associated with a user requesting to establish a wireless observation with the observation hub. The method may further include determining that the user is authorized to establish the wireless observation based at least on the identification data.

[0021] In some embodiments, accessing the wireless configuration data comprises retrieving the wireless configuration data from a memory.

[0022] The method may further comprise rendering the user interface via a display of the observation hub.

[0023] The method may further comprise receiving historical user interface data from the remote server, the historical user interface data corresponding to historical physiological data, the historical user interface data having been previously generated by another observation hub.

[0024] Disclosed herein is a non-transitory computer-readable medium containing computer-executable instructions that, when executed by a computing system, cause the computing system to perform operations. The operations may include accessing wireless configuration data managing wireless communication with the subject's wearable device in response to a request to establish wireless monitoring at an monitoring hub of the subject's physiology, the wireless configuration data comprising 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 further include establishing wireless communication between the monitoring hub and the wearable device using one or more wireless communication protocols to cause the monitoring hub to wirelessly receive real-time physiological data from the wearable device based at least on the wireless configuration data. The operations may further include receiving historical physiological data from the remote server, the historical physiological data comprising physiological data collected by the wearable device prior to establishing wireless communication between the monitoring hub and the wearable device, the historical physiological data comprising 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 operations may further comprise generating user interface data for rendering a user interface including the real-time physiological data in combination with the historical physiological data to reduce an observation gap between the historical physiological data and the real-time physiological data.

[0025] In some embodiments, the computer-executable instructions, when executed by a computing system, further cause the computing system to perform operations comprising rendering a user interface via a display of the observation hub.

[0026] In some embodiments, the computer-executable instructions, when executed by the computing system, further cause the computing system to perform an operation comprising receiving historical user interface data from a remote server, the historical user interface data corresponding to historical physiological data, and the historical user interface data having been previously generated by another observation hub.

[0027] Disclosed herein is a computing system configured to facilitate continuous monitoring of a patient with a wireless wearable device while changing from a first observation hub to a second observation hub. The computing system may include an in-room display device configured to electronically monitor the patient, the in-room display device including display indicia responsive to patient physiological data derived from the patient's wearable device, and the wearable device including a wireless wearable device, the wireless wearable device including wireless configuration data governing wireless transmission of the physiological data from the wearable device. The computing system may further include one or more hardware computer processors configured to execute computer-executable instructions to cause the computing system to receive, via the in-room display device, a request to transfer wireless observation of the patient from the in-room display device to a mobile observation hub, the request including identification data associated with a user requesting to transfer the wireless observation. The one or more hardware computer processors may further be configured to execute computer-executable instructions to cause the computing system to determine whether the user has authorization to transfer the wireless observation based at least on the identification data. The one or more hardware computer processors may be further configured to execute computer-executable instructions to cause the computing system to access the wireless configuration data associated with the patient's wireless wearable device in response to determining that the user has authorization to transfer wireless observation, the wireless configuration data being received from the in-room display device. The one or more hardware computer processors may be further configured to execute computer-executable instructions to cause the computing system to wirelessly transmit the wireless configuration data associated with the patient's wireless wearable device to a mobile observation hub to cause the mobile observation hub to establish wireless communication between the mobile observation hub and the wearable device.

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

[0029] The one or more hardware computer processors may be configured to execute computer-executable instructions to cause the computing system to further receive the identification data via one or more of near field communication (NFC) or radio frequency identification (RFID).

[0030] The one or more hardware computer processors may be further configured to execute computer-executable instructions to cause the computing system to receive the request to transfer a wireless observation comprising the identification data via a non-contact user input via an in-room display device.

[0031] In some implementations, the identification data comprises a serial number.

[0032] In some implementations, the identification data comprises a biological marker.

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

[0034] The one or more hardware computer processors may be further configured to execute computer-executable instructions to cause the computing system to, in response to determining that the user has authority to transition the wireless observation, wirelessly transmit historical physiological data to the mobile observation hub, the historical physiological data having been previously collected by the wearable device and communicated from the wearable device to the in-room display device.

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

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

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

[0038] Disclosed herein is a method for continuously monitoring a patient while changing from a first observation hub to a second observation hub with a wireless wearable device configured to move with the patient when the patient changes location. The method may include electronically monitoring the patient using an in-room display device, the in-room display device including display indicia responsive to patient physiological data derived from the patient's wearable device, the wearable device including a wireless wearable device, the wireless wearable device including wireless configuration data governing wireless transmission of the physiological data from the wearable device. The method may further include receiving, via the in-room display device, a request to transfer wireless observation of the patient from the in-room display device to a mobile observation hub, the request including identification data associated with a user requesting to transfer the wireless observation. The method may further include determining whether the user has authorization to transfer the wireless observation based at least on the identification data. The method may further include accessing the wireless configuration data associated with the patient's wireless wearable device in response to determining that the user has authorization to transfer the wireless observation, the wireless configuration data being received from the in-room display device. The method may further comprise, in response to determining that the user has authorization to migrate the wireless observation, wirelessly transmitting the wireless configuration data associated with the patient's wireless wearable device to the mobile observation hub to cause the mobile observation hub to establish wireless communication between the mobile observation hub and the wearable device.

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

[0040] The method may further comprise receiving the identification data via one or more of near field communication (NFC) or radio frequency identification (RFID).

[0041] The method may further comprise receiving the request to transfer the wireless view comprising the identification data via a contactless user input via an in-room display device.

[0042] In some implementations, the identification data comprises one or more of a serial number or a biological marker.

[0043] In some implementations, monitoring the patient with the wearable device comprises monitoring the patient with a wristwatch.

[0044] In some implementations, monitoring the patient using the wearable device comprises monitoring the patient using a wearable hub in communication with one or more of an ECG sensor, an SpO2 sensor, and a blood pressure sensor.

[0045] Disclosed herein is a non-transitory computer-readable medium including computer-executable instructions that, when executed by a computing system, cause the computing system to perform operations, including: electrically monitoring a patient using an in-room display device, the in-room display device including display indicia responsive to physiological data of the patient derived from a wearable device of the patient, the wearable device comprising a wireless wearable device, the wireless wearable device including wireless configuration data governing wireless transmission of the physiological data from the wearable device; and receiving, via the in-room display device, a request to transition wireless monitoring of the patient from the in-room display device to a mobile monitoring hub. The method includes: the request comprising identification data associated with a user requesting to transfer the wireless observation; determining whether the user has authority to transfer the wireless observation based at least on the identification data; in response to determining that the user has authority to transfer the wireless observation, accessing the wireless configuration data associated with the patient's wireless wearable device, the wireless configuration data being received from an in-room display device; and wirelessly transmitting the wireless configuration data associated with the patient's wireless wearable device to a mobile observation hub to cause the mobile observation hub to establish wireless communication between the mobile observation hub and the wearable device.

[0046] In some implementations, the computer-executable instructions, when executed by a computing system, further cause the computing system to perform an operation comprising receiving, via the mobile observation hub, second identification data and determining an approval status of a request to migrate the wireless observation based at least on comparing the identification data to the second identification data.

[0047] Disclosed herein is a method for continuously monitoring a patient while transferring from a first observation hub to a second observation hub with a wireless wearable device configured to move with the patient when the patient changes location. The method may include electronically monitoring the patient using an in-room display device. The in-room display device may include display indicators responsive to patient physiological data derived from the patient's wearable device. The wearable device may include a wireless wearable device. The wireless wearable device may include wireless configuration data governing wireless transmission of the physiological data from the wearable device. The method may further include receiving a request to transfer wireless monitoring of the patient from the in-room display device to a mobile observation hub. The method may further include electronically prompting a caregiver to place the mobile observation hub in a transfer mode. The method may further include accessing the wireless configuration data associated with the patient's wireless wearable device in response to an indication that the mobile observation hub is in the transfer mode, the wireless configuration data being received from the in-room display device. The method may further comprise, in response to an indication that the mobile observation hub is in the transition mode, wirelessly transmitting said wireless configuration data associated with the patient's wireless wearable device to the mobile observation hub to cause the mobile observation hub to establish wireless communication between the mobile observation hub and the wearable device. The method may further comprise, in response to an indication that the mobile observation hub is in the transition mode, wirelessly transmitting historical physiological data to the mobile observation hub, the historical physiological data having been previously collected by the wearable device and communicated from the wearable device to an in-room display device.

[0048] The method may further comprise receiving, via the in-room display device, identification data associated with a user requesting to transfer the wireless viewing, and determining whether the user is authorized to transfer the wireless viewing based at least on the identification data.

[0049] The method may further comprise receiving, via the in-room display device, identification data associated with a user requesting to transfer the wireless viewing, and determining an approval status of the request to transfer the wireless viewing based at least on comparing the identification data with second identification data received via the mobile viewing hub.

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

[0051] The method may further comprise terminating the wireless communication connection between the in-room display device and the wearable device in response to an indication that the mobile viewing hub is in the transition mode.

[0052] The method may further comprise receiving the wireless configuration data from an in-room display device.

[0053] The method may further comprise receiving the historical physiological data from an in-room display device.

[0054] In some implementations, monitoring the patient with a wearable device comprises monitoring the patient with a wristwatch.

[0055] In some implementations, monitoring the patient using the wearable device comprises monitoring the patient using a wearable hub in communication with one or more of an ECG sensor, an SpO2 sensor, and a blood pressure sensor.

[0056] The method may further comprise wirelessly transmitting user interface data to the mobile observation hub, the user interface data corresponding to past physiological data, the user interface data having been previously generated by the in-room display device.

[0057] Disclosed herein is a method for continuously monitoring a patient with a wireless wearable device while transferring from a first observation hub to a second observation hub. The method may include establishing wireless communication between the observation hub and the subject's wearable device according to a wireless communication protocol. The observation hub may include display indicators responsive to physiological data of the subject derived from the wearable device. The wireless communication may comprise a wireless communication connection. The method may further 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 further include receiving, at the observation hub, physiological data of the subject via wireless communication between the observation hub and the wearable device, the physiological data derived from the wearable device. The method may further include communicating the physiological data to a remote server. The method may further comprise communicating at least a portion of the wireless configuration data associated with the wearable device to a remote server, wherein the at least a portion of the wireless configuration data comprises at least one or more device addresses associated with the wearable device, the one or more device addresses configured to facilitate wireless communication with the wearable device.

[0058] The method may further comprise communicating the physiology data or the wireless configuration data to a remote server in response to a request to transfer physiology observation from an observation hub to another observation hub.

[0059] In some implementations, establishing the wireless communication between the observation hub and the wearable device comprises establishing a Bluetooth connection between the observation hub and the wearable device.

[0060] The method may further comprise communicating user interface data to a remote server, the user interface data corresponding to the physiology data, the user interface data being generated by the observation hub.

[0061] Disclosed herein is a method for monitoring the position of a patient wearing a wearable device. The method may include detecting, at an observation hub, a wireless configuration signal from the patient's wearable device. The wireless configuration signal may comprise at least a portion of a paging process of a Bluetooth communication protocol. The method may further include determining whether the wearable device is within a threshold proximity of the observation hub based at least on a signal strength associated with the wireless configuration signal. The method may further include establishing wireless communication between the wearable device and the observation hub according to the Bluetooth communication protocol in response to determining that the wearable device is within the threshold proximity of the observation hub, the wireless communication comprising a Bluetooth connection. The method may further include determining the subject's position based at least on determining the position of the observation hub in the environment in response to establishing the wireless communication.

[0062] Disclosed herein is a method for continuously monitoring a patient with a wireless wearable device while transitioning from a first observation hub to a second observation hub. The method may include accessing wireless configuration data governing wireless communication with one or more sensors coupled to the subject, the wireless configuration data comprising at least one or more device addresses associated with the one or more sensors. The method may include receiving user input for establishing wireless communication between the observation hub and the one or more sensors, the user input comprising a contactless user input. The method may include, in response to the user input, establishing wireless communication between the observation hub and the one or more sensors based at least on the wireless configuration data to cause the observation hub to wirelessly receive real-time physiological data from the one or more sensors.

[0063] The method may comprise determining a proximity of one or more sensors to an observation hub based at least on determining a signal strength associated with the one or more sensors. The method may further comprise establishing said wireless communication between the observation hub and the one or more sensors based at least on determining that the one or more sensors are within a threshold proximity from the observation hub.

[0064] In some implementations, receiving the contactless user input comprises receiving, via the observation hub, wireless signals associated with one or more of near field communication (NFC) or radio frequency identification (RFID).

[0065] Disclosed herein is a method for continuously monitoring a patient with a wireless wearable device while transitioning from a first observation hub to a second observation hub. The method may comprise accessing wireless configuration data governing wireless communication with a plurality of sensors coupled to the subject, the wireless configuration data comprising at least one or more devices associated with the plurality of sensors. The method may further comprise receiving a user input for establishing wireless communication between the observation hub and the plurality of sensors, the user input comprising a single user input. The method may further comprise, in response to the single user input, establishing wireless communication between the observation hub and the plurality of sensors based at least on the wireless configuration data to cause the observation hub to wirelessly receive real-time physiological data from the plurality of sensors.

[0066] In some implementations, receiving the user input comprises receiving contactless user input via a viewing hub.

[0067] Disclosed herein is a monitoring hub for monitoring a physiological state of a subject, the monitoring hub comprising a communications component, a computer-readable storage medium having program instructions embodied therein, and one or more processors, wherein the communications component may be configured to wirelessly communicate with one or more sensors to communicate physiological data and communication data therewith, and to wirelessly communicate with a physiological monitoring system to communicate physiological data and communication data therewith. The one or more processors may be configured to execute program instructions to cause the observation hub to receive a request to perform a transition operation; receive identification data; verify authority of the request based at least in part on the identification data; establish communication with another observation hub via a communication component, whereby the communication component is configured to communicate wirelessly with the other observation hub to communicate physiological data or communication data with the other observation hub; determine an authorization status of the request to perform the transition operation based at least in part on the identification data; and, in response to determining that the request to perform the transition operation is authorized, cause the communication component to communicate the physiological data or communication data to the other observation hub and terminate the wireless communication connection between the communication component and the one or more sensors.

[0068] In some implementations, the one or more processors are further configured to execute the program instructions to cause the observation hub to receive the identification data via the communication component. In some implementations, the one or more processors are further configured to execute the program instructions to cause the observation hub to receive the identification data using near field communication (NFC) of the communication component. In some implementations, the one or more processors are further configured to execute the program instructions to cause the observation hub to receive the identification data via user input or a display of the observation hub. In some implementations, the identification data includes user identification information. In some implementations, the one or more processors are further configured to execute the program instructions to cause the observation hub to receive second identification data via the communication component. In some implementations, the one or more processors are further configured to execute the program instructions to cause the observation hub to compare the identification data with second identification data to determine whether the identification data matches the second identification data. In some implementations, the one or more processors are further configured to execute the program instructions to cause the observation hub to determine an authorization status of the request based at least in part on comparing the identification data with the second identification data. In some implementations, the one or more processors are further configured to execute the program instructions to cause the observing hub to determine that a request to perform a transition operation is approved if the identification data matches the second identification data. In some implementations, the one or more processors are further configured to execute the program instructions to cause the observing hub to determine that a request to perform a transition operation is approved if a user identification information of the identification data matches a user identification information of the second identification data. In some implementations, the one or more processors are further configured to execute the program instructions to cause the observing hub to communicate the identification data to another observing hub via the communication component.In some embodiments, the one or more processors are further configured to execute the program instructions to cause the monitoring hub to communicate the identification data to the physiological monitoring system via the communication component. In some embodiments, the one or more processors are further configured to execute the program instructions to cause the monitoring hub to receive an approval status of the request from another monitoring hub via the communication component. In some embodiments, the one or more processors are further configured to execute the program instructions to cause the monitoring hub to communicate an approval status of the request from the physiological monitoring system via the communication component. In some embodiments, the one or more processors are further configured to execute the program instructions to cause the monitoring hub to, in response to determining that the request to perform the transition operation is approved, cause the communication component to communicate physiological data or communication data to the physiological monitoring system. In some embodiments, the physiological data includes one or more of 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 implementations, the one or more processors are further configured to execute the program instructions to cause the observation hub to receive communication data from another observation hub via the communication component. In some implementations, the one or more processors are further configured to execute the program instructions to cause the observation hub to communicate the communication data received from another observation hub to the one or more sensors via the communication component. In some implementations, the communication data received from another observation hub includes a device address of the other observation hub. In some implementations, the one or more processors are further configured to execute the program instructions to cause the observation hub to receive, via the communication component, a confirmation that the migration operation has been completed.In some embodiments, the one or more processors are further configured to execute the program instructions to cause the monitoring hub to receive confirmation from another monitoring hub or the physiological monitoring system. In some embodiments, the confirmation includes an indication that the other monitoring hub has established a wireless communication connection with the 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 the 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 observation hub using one or more wireless communication protocols, including Wi-Fi, Bluetooth, near field communication (NFC), radio frequency identification (RFID), cellular, 1G, 2G, 3G, 4G, 5G, or Zigbee. In some embodiments, the one or more processors are further configured to execute program instructions to receive a request to perform a transition operation via a user input at the observation hub. In some embodiments, verifying the authority of the request includes verifying the authority of a user associated with the request. In some embodiments, the one or more processors are further configured to execute program instructions to cause the communication component to communicate a transition signal to the physiology monitoring system to initiate the transition operation. In some embodiments, the one or more processors are further configured to execute program instructions to cause the communication component to communicate physiology data or communication data to the physiology monitoring system to initiate the transition operation.In some implementations, the physiological data includes historical physiological data. In some implementations, the communication data includes one or more device addresses of the one or more sensors.

[0069]

[0009] Disclosed herein is a monitoring hub for monitoring a physiological state of a subject, the monitoring hub comprising: a communications component; a computer-readable storage medium having program instructions embodied therein; and one or more processors. In some implementations, the communications component is configured to wirelessly communicate with one or more sensors to communicate physiological data and communication data with the one or more sensors, and to wirelessly communicate with a physiology monitoring system to communicate physiological data and communication data with the physiology monitoring system. In some implementations, the one or more processors are configured to execute program instructions to cause the observation hub to receive a request to perform a transition operation; receive identification data; establish communication with another observation hub via a communication component, whereby the communication component is configured to communicate wirelessly with the other observation hub to communicate physiological data or communication data with the other observation hub; determine an approval status of the request to perform the transition operation based at least in part on the identification data; and, in response to determining that the request to perform the transition operation is approved, receive physiological data or communication data from the other observation hub via the communication component; and establish a wireless communication connection between the communication component and one or more sensors.

[0070] In some implementations, the one or more processors are further configured to execute the program instructions to cause the observation hub to receive the identification data via the communication component. In some implementations, the one or more processors are further configured to execute the program instructions to cause the observation hub to receive the identification data using near field communication (NFC) of the communication component. In some implementations, the one or more processors are further configured to execute the program instructions to cause the observation hub to receive the identification data via user input or a display of the observation hub. In some implementations, the identification data includes user identification information. In some implementations, the one or more processors are further configured to execute the program instructions to cause the observation hub to receive second identification data via the communication component. In some implementations, the one or more processors are further configured to execute the program instructions to cause the observation hub to compare the identification data with second identification data to determine whether the identification data matches the second identification data. In some implementations, the one or more processors are further configured to execute the program instructions to cause the observation hub to determine an authorization status of the request based at least in part on comparing the identification data with the second identification data. In some implementations, the one or more processors are further configured to execute the program instructions to cause the observing hub to determine that a request to perform a transition operation is approved if the identification data matches the second identification data. In some implementations, the one or more processors are further configured to execute the program instructions to cause the observing hub to determine that a request to perform a transition operation is approved if a user identification information of the identification data matches a user identification information of the second identification data. In some implementations, the one or more processors are further configured to execute the program instructions to cause the observing hub to communicate the identification data to another observing hub via the communication component.In some embodiments, the one or more processors are further configured to execute the program instructions to cause the monitoring hub to communicate the identification data to the physiological monitoring system via the communication component. In some embodiments, the one or more processors are further configured to execute the program instructions to cause the monitoring hub to receive an approval status of the request from another monitoring hub via the communication component. In some embodiments, the one or more processors are further configured to execute the program instructions to cause the monitoring hub to communicate an approval status of the request from the physiological monitoring system via the communication component. In some embodiments, the one or more processors are further configured to execute the program instructions to cause the monitoring hub to receive physiological data or communication data from the physiological monitoring system via the communication component in response to determining that the request to perform the transition operation is approved. In some embodiments, the physiological data includes one or more of 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 implementations, the one or more processors are further configured to execute the program instructions to cause the monitoring hub to communicate, via the communication component, a confirmation that the transition operation has been completed. In some implementations, the one or more processors are further configured to execute the program instructions to cause the monitoring hub to communicate the confirmation to another monitoring hub or to the physiology monitoring system. In some implementations, the confirmation includes an indication that the monitoring hub has established a wireless communication connection with the one or more sensors. In some implementations, the communication component includes a transceiver.In some implementations, the communication component is further configured to communicate with the 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 implementations, the communication component is further configured to communicate with the physiology 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 implementations, the communication component is further configured to communicate with another observation 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 implementations, the one or more processors are further configured to execute program instructions to cause the observation hub to receive a request to perform a transition operation via a user input at the observation hub. In some implementations, the one or more processors are further configured to execute the program instructions to cause the communication component to communicate the physiological data or communication data to the physiological monitoring system. In some implementations, the one or more processors are further configured to execute the program instructions to cause the monitoring hub to receive physiological data from the one or more sensors via the communication component. In some implementations, the one or more processors are further configured to execute the program instructions to display the received physiological data and historical physiological data from the one or more sensors via a display of the monitoring hub.

[0071] Disclosed herein is a physiology monitoring system for monitoring a physiological state of a subject, the physiology monitoring system comprising a computer-readable storage medium having program instructions embodied thereon and one or more processors, wherein the one or more processors may be configured to execute the program instructions to cause the physiology monitoring system to receive a request to perform a transition operation from one or more monitoring hubs, determine an approval status of the request to perform the transition operation, and, in response to determining that the request to perform the transition operation is approved, receive monitoring hub communication data from the one or more monitoring hubs, access sensor communication data, establish a wireless communication connection between a first monitoring hub and one or more sensors of the one or more monitoring hubs, and terminate a wireless communication connection between a second monitoring hub and the one or more sensors of the one or more monitoring hubs.

[0072] In some embodiments, the one or more processors are further configured to execute the program instructions to cause the physiology monitoring system to determine an approval status based at least in part on one or more signals received from the one or more monitoring hubs. In some embodiments, the one or more processors are further configured to execute the program instructions to cause the physiology monitoring system to receive first and second identification data from the one or more monitoring hubs. In some embodiments, the first and second identification data include user identification information. In some embodiments, the one or more processors are further configured to execute the program instructions to cause the physiology monitoring system to compare 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 the program instructions to cause the physiology monitoring system to determine an 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 the program instructions to cause the physiology monitoring system to determine that the request to perform a transition operation is approved if the first identification data matches the second identification data. In some implementations, the one or more processors are further configured to execute the program instructions to cause the physiology monitoring system to determine that the request to perform the transition operation is approved if the user identification information of the first identification data matches the user identification information of the second identification data. In some implementations, the monitoring hub communication data includes a device address of the first monitoring hub. In some implementations, the sensor communication data includes one or more device addresses of the one or more sensors. In some implementations, the one or more processors are further configured to execute the program instructions to cause the physiology monitoring system to communicate the monitoring hub communication data to the one or more sensors.In some implementations, the one or more processors are further configured to execute the program instructions to cause the physiology monitoring system to communicate the sensor communication data to the first monitoring hub. In some implementations, the one or more processors are further configured to execute the program instructions to cause the physiology monitoring system to access historical physiology data. In some implementations, the one or more processors are further configured to execute the program instructions to cause the physiology monitoring system to communicate the historical physiology data to the first monitoring hub.

[0073] Disclosed herein is a method for transitioning 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, wherein the second medical monitoring device is different from the first medical monitoring device, the method comprising: receiving a request to transition the wireless connection; receiving, using the first medical monitoring device, first identification data; receiving, using the second medical monitoring device, second identification data; comparing the second identification data with the first identification data; and initiating the transition of the wireless connection based on the comparison to enable wireless communication between the one or more physiological sensors and the second medical monitoring device.

[0074] In some implementations, receiving the request to transition the wireless connection comprises receiving a user input at a first medical monitoring device. In some implementations, comparing second identification data with the first identification data is performed by one or more of the first medical monitoring device, the second medical monitoring device, the third medical monitoring device, or a server. In some implementations, initiating the transition comprises receiving, with the second medical monitoring device, communication data associated with each of one or more physiological sensors. In some implementations, initiating the transition comprises transmitting, to the second medical monitoring device, communication data associated with each of one or more physiological sensors. In some implementations, transmitting the communication data is performed by a server in communication with the first and second medical monitoring devices. In some implementations, transmitting the communication data is performed by the first medical monitoring device. In some implementations, initiating the transition comprises receiving, with one or more physiological sensors, communication data associated with the second medical monitoring device. In some implementations, initiating the transition comprises transmitting communication data associated with a second medical monitoring device to each of one or more physiological function sensors. In some implementations, transmitting the communication data is performed by the first medical monitoring device. In some implementations, comparing the second identification data with the first identification data comprises determining whether the second identification data is associated with the first identification data, and the method comprises initiating the transition of the wireless connection in response to determining that the second identification data is associated with the first identification data. In some implementations, comparing the second identification data with the first identification data comprises determining whether the second identification data matches the first identification data, and the method comprises initiating the transition of the wireless connection in response to determining that the second identification data matches the first identification data.In some implementations, the first identification data is associated with a user. In some implementations, the first identification data is associated with a healthcare provider. In some implementations, the user is not required to terminate the wireless connection between the wireless sensor and the first medical monitoring device. In some implementations, the first medical monitoring device is not directly connected to the second medical monitoring device using a wired or wireless connection. In some implementations, the method further 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 implementations, Bluetooth multipoint is not enabled. In some implementations, the wireless sensor is configured to wirelessly connect to a single medical monitoring device at a time.

[0075] Disclosed herein is a method for transitioning a wireless connection between a first medical monitoring device and one or more physiological function sensors to a wireless connection between a second medical monitoring device and the one or more physiological function sensors, wherein the second medical monitoring device is different from the first medical monitoring device, the method comprising: receiving first information regarding the transition of the wireless connection; receiving second information regarding the transition of the wireless connection; and initiating the transition of the wireless connection to enable wireless communication between the one or more physiological function sensors and the second medical monitoring device based at least on the received first and second information, wherein the step of initiating the transition does not require a user to terminate the wireless connection between the first medical monitoring device and the one or more physiological function sensors.

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

[0077] Disclosed herein is a mounting assembly for mounting an electronic device to a support surface, the mounting assembly comprising a first mount configured to be secured to a portion of the electronic device and a second mount configured to be secured to the support surface, the first mount may be configured to be removably secured to the second mount, thereby mounting the electronic device to the support surface.

[0078] In some implementations, the electronic device is an observation hub, such as any of the observation hubs disclosed herein, and any of the features and / or functionality are described with respect to any of the observation hubs disclosed herein. In some implementations, the support surface is a wall. In some implementations, the support surface is in contact with a support arm secured to the wall. In some implementations, the first mount is configured to be secured to the second mount without using screws and / or without using nails. In some implementations, the first mount is configured to be secured to the second mount by inserting a portion of the first mount into a portion of the second mount. In some implementations, the first mount is configured to be secured to the second mount by moving the first mount in a first direction relative to the second mount, and the first mount is configured to be removed from the second mount by moving the first mount in a second direction relative to the second mount opposite the first direction. In some implementations, the second mount includes one or more fingers configured to engage with portions of the first mount. In some implementations, the second mount comprises a base and the one or more fingers. The one or more fingers extend outward from the base such that a gap exists between a portion of each of the one or more fingers and a surface of the base, the gap being configured to receive the portion of the first mount. In some implementations, the one or more fingers are configured to vertically support the portion of the first mount. In some implementations, the one or more fingers form a tapered pocket that vertically supports the portion of the first mount. In some implementations, the portion of the first mount vertically supported by the one or more fingers is part of a base of the first mount, the base having a width that tapers along at least a portion of the height of the base. In some implementations, one of the first mount or the second mount comprises a lever configured to be moved from a first position to a second position, and when the lever is in the first position, separation of the first mount from the second mount is prevented.In some implementations, the second mount includes a lever configured to be moved from a first position to a second position, wherein when the lever is in the first position, a portion of the lever engages with a portion of the first mount, thereby providing a physical interference that prevents the first mount from being separated from the second mount, and when the lever is in the second position, the physical interference is removed. In some implementations, the lever includes a protrusion, and the first mount includes an opening, wherein when the lever is in the first position, the protrusion of the lever engages with a portion of the first mount near the opening of the first mount, thereby providing the physical interference. In some implementations, when the lever is in the first position, the second protrusion of the lever is at least partially located within the opening of the first mount. In some implementations, when the lever is in the second position, the protrusion of the lever is located outside the opening of the first mount.

[0079] Disclosed herein is a holder for receiving an electronic device, the holder comprising: a base configured to receive at least a portion of the electronic device; a first arm extending outward from the base, the first arm being oriented non-parallel to the base such that when the first arm is positioned on a support surface, the base is oriented non-parallel to the support surface; and a second arm extending outward from the base and spaced apart from the first arm, the second arm comprising a hook configured to secure a portion of an object.

[0080] In some implementations, the object is a hospital bed, and the portion comprises a wall or rail of the hospital bed. In some implementations, the first arm has a first end connected to the first portion of the base and a second portion connected to the second portion of the base, thereby forming a loop of the holder. In some implementations, the second arm has 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 holder. In some implementations, the holder further comprises 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 implementations, the first arm is connected to the first end of the base, and the second arm is connected to a second end of the base opposite the first end of the base. In some implementations, the holder is configured such that when the second arm is wrapped around and / or above 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 implementations, the holder is configured such that when the second arm is wrapped around and / or above 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 implementations, the support structure is generally perpendicular to the ground surface. In some implementations, the holder is configured such that when the second arm is wrapped around and / or above the top of the support structure, the first arm contacts the support structure and operably positions the base so that the base is generally perpendicular to the ground surface. In some implementations, the holder is configured such that when the second arm is wrapped around and / or on top of the support structure, the first arm contacts the support structure and operably positions the base within 30 degrees of perpendicular to the ground surface.In some implementations, the holder is configured such that when the second arm is wrapped around and / or above the top of the support structure, the first arm contacts the support structure and operably positions the base to be within 20 degrees of perpendicular to the ground surface. In some implementations, the holder is configured such that when the second arm is wrapped around and / or above the top of the support structure, the first arm contacts the support structure and operably positions the base to be within 10 degrees of perpendicular to the ground surface.

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

[0082] Additional implementations of the present disclosure are described below with reference to the accompanying claims, which may serve as an additional summary of the present disclosure.

[0083] In various implementations, systems and / or computer systems are disclosed that include a computer-readable storage medium having program instructions embodied thereon and one or more processors configured to execute the program instructions to cause the system and / or computer system to perform operations that comprise one or more aspects of the implementations described above and / or below (including one or more aspects of the appended claims).

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

[0085] In various implementations, a computer program product is disclosed that comprises a computer-readable storage medium having program instructions embodied therein, the program instructions being executable by one or more processors to cause the one or more processors to perform operations comprising one or more aspects of the implementations described above and / or below (including one or more aspects of the appended claims).

[0086] Various implementations are described below with reference to the accompanying drawings. These implementations are shown and described by way of example only and are not intended to limit the scope of the present disclosure. In the drawings, like elements may have like reference numerals. [Brief explanation of the drawings]

[0087] [Figure 1A] FIG. 1 is a schematic block diagram illustrating an exemplary implementation of a physiological monitoring system (PMS). [Figure 1B] FIG. 1 is a schematic block diagram illustrating an exemplary implementation of a physiological monitoring system (PMS). [Figure 1C] FIG. 1 illustrates an exemplary implementation of a physiological monitoring system. [Figure 1D] FIG. 1 is a schematic block diagram illustrating an exemplary physiological monitoring system (PMS) implementation. [Figure 2] FIG. 1 is a block diagram illustrating an exemplary implementation of a physiological monitoring system (PMS) observation hub. [Figure 3A] FIG. 1 is a perspective view of an exemplary viewing hub. [Figure 3B] FIG. 1 is a perspective view of an exemplary viewing hub. [Figure 4] FIG. 1 illustrates an exemplary process for transferring physiology observations from one observation hub to another. [Figure 5A] 10 is a flowchart illustrating an exemplary process associated with migrating physiology observations from a source observation hub to a destination observation hub. [Figure 5B]10 is a flowchart illustrating an exemplary process associated with migrating physiology observations from a source observation hub to a destination observation hub. [Figure 5C] 10 is a flowchart illustrating an exemplary process associated with migrating physiology observations from a source observation hub to a destination observation hub. [Figure 5D] 10 is a flowchart illustrating an exemplary process associated with migrating physiology observations from a source observation hub to a destination observation hub. [Figure 5E] 1 is a flowchart illustrating an exemplary process for observing the position of a subject. [Figure 6] FIG. 1 illustrates an exemplary implementation of a viewing hub. [Figure 7A] FIG. 1 is a front perspective view of a viewing hub according to aspects of the present disclosure. [Figure 7B] FIG. 7B is a top perspective view of the rear of the viewing hub of FIG. 7A according to an embodiment of the present disclosure. [Figure 7C] FIG. 7B is a top perspective view of the rear of the viewing hub of FIG. 7A according to an embodiment of the present disclosure. [Figure 7D] FIG. 7B is a bottom perspective view of the rear of the viewing hub of FIG. 7A according to an embodiment of the present disclosure. [Figure 7E] FIG. 7B is a bottom perspective view of the rear of the viewing hub of FIG. 7A according to an embodiment of the present disclosure. [Figure 7F] FIG. 7B is a front view of the viewing hub of FIG. 7A according to an embodiment of the present disclosure. [Figure 7G] FIG. 7B is a rear view of the viewing hub of FIG. 7A according to an embodiment of the present disclosure. [Figure 7H] FIG. 7B is a top view of the viewing hub of FIG. 7A according to an embodiment of the present disclosure. [Figure 7I] FIG. 7B is a bottom view of the viewing hub of FIG. 7A according to an embodiment of the present disclosure. [Figure 7J] FIG. 7B is a left side view of the viewing hub of FIG. 7A according to an embodiment of the present disclosure. [Figure 7K] FIG. 7B is a right side view of the viewing hub of FIG. 7A according to an embodiment of the present disclosure. [Figure 8A] FIG. 7B is a view of the viewing hub and holder of FIG. 7A according to an embodiment of the present disclosure. [Figure 8B] FIG. 7B is a view of the viewing hub and holder of FIG. 7A according to an embodiment of the present disclosure. [Figure 8C] 7A and 8A-8B separated from each other according to an embodiment of the present disclosure. [Figure 8D] FIG. 8C is a top, front perspective view of the holder of FIGS. 8A-8B according to an embodiment of the present disclosure. [Figure 8E] FIG. 8C is a top, front perspective view of the holder of FIGS. 8A-8B according to an embodiment of the present disclosure. [Figure 8F] FIG. 8C is a rear perspective view of the holder of FIGS. 8A-8B according to an embodiment of the present disclosure. [Figure 8G] FIG. 8C is a rear perspective view of the holder of FIGS. 8A-8B according to an embodiment of the present disclosure. [Figure 8H] FIG. 8C is a rear perspective view of the holder of FIGS. 8A-8B according to an embodiment of the present disclosure. [Figure 8I] FIG. 8C is a rear perspective view of the holder of FIGS. 8A-8B according to an embodiment of the present disclosure. [Figure 8J] 8A-8B according to an embodiment of the present disclosure. FIG. [Figure 8K] 8A-8B according to an embodiment of the present disclosure. FIG. [Figure 8L] FIG. 8C is a left side view of the holder of FIGS. 8A-8B according to an embodiment of the present disclosure. [Figure 8M] FIG. 8C is a right side view of the holder of FIGS. 8A-8B according to an embodiment of the present disclosure. [Figure 8N] 8A-8B according to an embodiment of the present disclosure. FIG. [Figure 8O] 8A-8B according to an embodiment of the present disclosure. FIG. [Figure 9A] 7B illustrates the viewing hub and mounting assembly of FIG. 7A according to an embodiment of the present disclosure. [Figure 9B] 7B illustrates the viewing hub and mounting assembly of FIG. 7A according to an embodiment of the present disclosure. [Figure 9C] 9A-9B according to an embodiment of the present disclosure. [Figure 9D]9A-9B according to an embodiment of the present disclosure. [Figure 9E] FIG. 9C is a rear perspective view of the mount of the mounting assembly of FIGS. 9A-9B connected to the viewing hub of FIG. 7A according to an embodiment of the present disclosure. [Figure 9F] 7B according to an embodiment of the present disclosure. FIG. 9A is a rear view of the mount of the mounting assembly of FIGS. 9A-9B connected to the viewing hub of FIG. 7A. [Figure 9G] 9A-9B show how the viewing hub and mounting assembly can be attached, according to an embodiment of the present disclosure. [Figure 9H] 9A-9B show how the viewing hub and mounting assembly can be attached, according to an embodiment of the present disclosure. [Figure 9I] 9A-9B show how the viewing hub and mounting assembly can be attached, according to an embodiment of the present disclosure. [Figure 9J] 9A-9B attached together according to an embodiment of the present disclosure. [Figure 9K] 9A-9B in an installed configuration without showing the viewing hub, according to an embodiment of the present disclosure. [Figure 9L] 9A-9B in an installed configuration without showing the viewing hub, according to an embodiment of the present disclosure. [Figure 9M] 9A-9B in an installed configuration without showing the viewing hub, according to an embodiment of the present disclosure. [Figure 10A] 7B illustrates another implementation of the viewing hub and mounting assembly of FIG. 7A according to an embodiment of the present disclosure. [Figure 10B] 7B illustrates another implementation of the viewing hub and mounting assembly of FIG. 7A according to an embodiment of the present disclosure. [Figure 10C] 10A-10B according to an embodiment of the present disclosure. [Figure 10D] 10A-10B according to an embodiment of the present disclosure. [Figure 10E] FIG. 10C is a rear perspective view of the mount of the mounting assembly of FIGS. 10A-10B connected to the viewing hub of FIG. 7A according to an embodiment of the present disclosure. [Figure 10F] 10A-10B connected to the viewing hub of FIG. 7A according to an embodiment of the present disclosure. FIG. [Figure 10G] 10A-10B show how the viewing hub and mounting assembly can be attached, according to an embodiment of the present disclosure. [Figure 10H] 10A-10B attached together according to an embodiment of the present disclosure. [Figure 10I] 10A-10B in an installed configuration without showing the viewing hub, according to an embodiment of the present disclosure. [Figure 10J] 10A-10B in an installed configuration without showing the viewing hub, according to an embodiment of the present disclosure. [Figure 10K] 10A-10B in an installed configuration without showing the viewing hub, according to an embodiment of the present disclosure. [Figure 11A] FIG. 10 is a front view of another implementation of a viewing hub according to aspects of the present disclosure. [Figure 11B] FIG. 10 is a rear view of another implementation of a viewing hub according to aspects of the present disclosure. [Figure 11C] FIG. 10 is a side view of another implementation of a viewing hub according to aspects of the present disclosure. [Figure 12A] FIG. 1 is a front perspective view of a viewing hub according to aspects of the present disclosure. [Figure 12B] FIG. 1 is a side perspective view of a viewing hub according to aspects of the present disclosure. [Figure 12C] FIG. 12B is a top perspective view of the rear of the viewing hub of FIG. 12A according to an embodiment of the present disclosure. [Figure 12D] FIG. 12B is a top perspective view of the rear of the viewing hub of FIG. 12A according to an embodiment of the present disclosure. [Figure 12E] FIG. 12B is a bottom perspective view of the rear of the viewing hub of FIG. 12A according to an embodiment of the present disclosure. [Figure 12F] FIG. 12B is a bottom perspective view of the rear of the viewing hub of FIG. 12A according to an embodiment of the present disclosure. [Figure 12G] FIG. 12B is a front view of the viewing hub of FIG. 12A according to an embodiment of the present disclosure. [Figure 12H] FIG. 12B is a rear view of the viewing hub of FIG. 12A according to an embodiment of the present disclosure. [Figure 12I] FIG. 12B is a top view of the viewing hub of FIG. 12A according to an embodiment of the present disclosure. [Figure 12J] FIG. 12B is a bottom view of the viewing hub of FIG. 12A according to an embodiment of the present disclosure. [Figure 12K] FIG. 12B is a left side view of the viewing hub of FIG. 12A according to an embodiment of the present disclosure. [Figure 12L] FIG. 12B is a right side view of the viewing hub of FIG. 12A according to an embodiment of the present disclosure. [Figure 12M] FIG. 12B is a rear perspective exploded view of the viewing hub of FIG. 12A according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0088] Although several implementations, embodiments, and examples are disclosed below, the subject matter of the present invention extends beyond the specifically disclosed implementations to other alternative implementations and / or applications, as well as modifications and equivalents thereof. Therefore, the scope of the claims appended hereto is not limited by any of the specific implementations described below. For example, in any method or process disclosed herein, the acts or operations of the method or process may be performed in any suitable order and are not necessarily limited to any particular disclosed order. Various operations may be described as multiple sequential, separate operations in a manner that may be useful for understanding some implementations. However, the order of description should not be construed as implying that these operations are order-dependent. In addition, the structures, systems, and / or devices described herein may be embodied as integrated or separate components. For purposes of comparing various implementations, several aspects and advantages of these implementations are described. Not all such aspects or advantages are necessarily achieved by any particular implementation. Thus, for example, various implementations may be performed in a manner that achieves or optimizes one advantage or group of advantages as taught herein without necessarily achieving other aspects or advantages that may also be taught or suggested herein.

[0089] overview A physiological monitoring system (PMS) can monitor a patient or subject, including the subject's physiological data. One or more physiological sensors may be coupled to the subject and can acquire the subject's physiological data. The one or more sensors can communicate the physiological data to an observation hub, which can display an indication of the physiological data. A user may desire to monitor the subject using another observation hub, such as to receive and display the physiological data obtained from the sensors. The user can request the PMS to transfer physiological observations from an initial observation hub to another observation hub. Described herein are systems, devices, processes, etc. for transferring PMS physiological observations from one observation hub to another observation hub, which can provide numerous benefits, including improved physiological observations, improved healthcare services, etc.

[0090] Advantageously, the systems, devices, and processes described herein can facilitate faster, easier, and more efficient transfer of physiological observations from one observation hub to another. For example, a user may be able to transfer physiological observations from one observation hub to another without having to unplug, plug, and / or replug cables, wires, and the like of the observation hub and / or physiological sensors. As another example, a user may be able to transfer physiological observations from one observation hub to another without having to turn off and / or on devices connected to the observation hub, such as physiological sensors. As another example, a user may be able to transfer physiological observations from one observation hub to another observation hub without having to perform a time-consuming wireless pairing process. As another example, the PMS provides an intuitive and easy-to-use system for transferring physiological observations, which can reduce the time healthcare providers must spend supervising a subject's physiological observations and improve the quality of healthcare services provided to the subject.

[0091] Advantageously, the systems, devices, and processes described herein can reduce and / or eliminate data loss during the transition of physiological observations from one observation hub to another. For example, a PMS may be configured to continuously monitor a subject's physiology while transitioning physiological observations from one observation hub to another. The PMS may be configured to retain (e.g., store) physiological data obtained from a sensor before, during, and / or after transitioning physiological observations between observation hubs. The PMS may be configured to exchange physiological data between observation hubs to allow a user to view historical physiological data in combination with current or real-time physiological data. For example, an observation hub of a PMS may be configured to display real-time physiological data received from a sensor in addition to historical physiological data received from the sensor by another observation hub before transitioning the physiological observations, as if the observation hub had been observing the subject all along and had received all subject data directly from the sensor.

[0092] Advantageously, the systems, devices, and processes described herein for transferring physiological observations of a PMS can improve patient mobility. For example, the PMS can facilitate easy, fast, and efficient transfer of physiological observations from one observation hub (which may be in a fixed location, such as a patient room in a hospital) to another observation hub (such as a portable observation hub) while continuing to observe the patient, which may allow the patient to move to a different location, such as a different room in a hospital. Moreover, while the patient moves through an environment, such as a hospital, the PMS can facilitate automatic wireless communication between sensors coupled to the patient and an observation hub located near the patient. For example, a sensor coupled to a patient may automatically establish a wireless connection, such as a Bluetooth connection, with the nearest observation hub while the patient moves around in an environment with multiple observation hubs.

[0093] Advantageously, the systems, devices, and processes described herein can improve patient location tracking. For example, a PMS may monitor a patient's location, such as within a hospital, by identifying which observation hubs are wirelessly connected to sensors attached to the patient. As the patient moves through the environment, the sensors coupled to the patient may wirelessly connect to and / or communicate with various observation hubs, such as those in proximity to the sensors. Thus, the PMS can track the patient's location, which can improve the quality of care provided to the patient by always quickly and efficiently knowing the patient's location, such as whether the patient is in a particular part of the hospital where the patient is supposed to be or is assigned or scheduled to be, such as an operating room.

[0094] Advantageously, the systems, devices, and processes described herein for migrating physiological observations of a PMS can facilitate removing, adding, replacing, and / or exchanging an observation hub within a PMS, such as when an observation hub has low battery and should be replaced by another observation hub to continue observing the subject, which can improve the performance of the PMS as well as medical services, for example.

[0095] Advantageously, the systems, devices, and processes described herein for transferring physiological observations in a PMS can control quality control of medical services. For example, the PMS can be configured to verify the authority associated with a user requesting to transfer physiological observations from one observation hub to another. For example, the PMS can be configured to reject a request to transfer physiological observations from a healthcare provider who does not have the authority to move the observed subject and / or who is not assigned to provide medical care to the subject.

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

[0097] To facilitate understanding of the systems and methods discussed herein, several terms are explained below. These terms, as well as other terms used herein, should be interpreted as including the explanations provided, the ordinary and customary meaning of the terms, and / or any other suggested meaning of the respective terms, such interpretation being consistent with the context of the terms. Thus, the following explanations do not limit the meaning of these terms, but merely provide exemplary explanations.

[0098] In some implementations, the sensor may comprise a wearable device. The sensor may comprise a wireless wearable device. The wearable device may include one or more sensors. The wearable device may comprise a wearable hub in communication with one or more sensors. The sensor may comprise an ear device, such as earbuds, earpieces, headphones, or earphones. The sensor may comprise a wrist-worn device, such as a smartwatch. The sensor may comprise a physiological sensor. The sensor may collect physiological data from a subject, such as ECG data, EEG data, blood oxygen data, heart rate data, pulse data, respiration data, blood pressure data, movement data, posture data, and temperature data. The sensor may be coupled to the subject. The sensor may be attached to the subject. The sensor may be worn by the subject. The sensor may be attached by the subject. The sensor may be secured to the subject by an adhesive. The sensor may be secured to the subject by one or more straps. The sensors may be worn and / or attached to a finger, wrist, arm, forearm, head, forehead, ear, chest, back, torso, abdomen, leg, ankle, foot, toe, or other body part of the subject. Multiple sensors may be disposed within the same housing or device. Sensors may be disposed within separate housings or devices.

[0099] In some implementations, the observation hub may comprise an electronic device configured to facilitate monitoring of the patient's physiology. The observation hub may display indicators corresponding to the patient's physiology data. The observation hub may be mobile. The observation hub may be portable. The observation hub may comprise a handheld device. The observation hub may be carried by a user. The observation hub may be wall-mounted. The observation hub may comprise an in-room display. The observation hub may be stationary. The observation hub may be in a fixed location. The observation hub may comprise a tablet, monitor, PC, phone, wearable device such as a smart watch, etc. The observation hub may communicate with one or more remote computing devices via one or more wireless communication protocols. The observation hub may communicate with a remote server. The observation hub may communicate with one or more sensors. The observation hub may also be referred to herein as a hub, electronic device, display device, observation device, etc.

[0100] In some implementations, a source observation hub may refer to an observation hub that is in wireless communication with one or more sensors before transferring physiological observations to another observation hub. The source observation hub may comprise any of the example observation hubs shown and / or described herein, including the structural and / or operational features of any of the example observation hubs shown and / or described herein. The source observation hub may also be referred to herein as a first observation hub, initial observation hub, etc.

[0101] In some implementations, a destination observation hub may refer to an observation hub that is in wireless communication with one or more sensors after transferring physiological observations from another observation hub. The destination observation hub may comprise any of the example observation hubs shown and / or described herein, including the structural and / or operational features of any of the example observation hubs shown and / or described herein. A destination observation hub may also be referred to herein as a second observation hub, a subsequent observation hub, another observation hub, etc.

[0102] The destination observation hub may comprise a different type of observation hub than the source observation hub. For example, one of the destination observation hub or the source observation hub may comprise a mobile observation hub, while the other of the destination observation hub or the source observation hub comprises an observation hub in a fixed location, such as a wall-mounted observation hub or an indoor observation hub. The destination observation hub may comprise the same type of observation hub as the source observation hub. For example, both the destination observation hub and the source observation hub may comprise mobile observation hubs.

[0103] In some implementations, "migrating physiological observations" may refer to migrating the observation, display, and / or collection of physiological data from a source observation hub to a destination observation hub. Migrating physiological observations may include migrating a wireless connection between a sensor and the source observation hub to a wireless connection between the sensor and the destination observation hub. Migrating physiological observations may include updating or modifying wireless connections of the physiological sensors and / or updating or modifying wireless connections of the observation hubs. Migrating physiological observations may include terminating wireless communication between the source observation hub and the sensors. Migrating physiological observations may include establishing wireless communication between the destination observation hub and the sensors. In some implementations, migrating physiological observations may include migrating less than all of the wireless connections to the sensors from the source observation hub to the destination observation hub. In some implementations, migrating physiological observations may include migrating all of the wireless connections to the sensors from the source observation hub to the destination observation hub.

[0104] In some implementations, the transition request may include a request to transition the physiological observations from a source observation hub to a destination observation hub. The transition request may be received via user input at the observation hub. For example, a user may press one or more observation hub buttons to initiate the transition request. In some implementations, the transition request may comprise a contactless or minimal-contact user input, such as a wireless communication signal, facial recognition, eye recognition, fingerprint recognition, gesture recognition, voice recognition, etc. The transition request may be received at a location and / or computing device remote from the observation hub. The transition request may initiate transitioning the physiological observations.

[0105] In some implementations, the identification data may include data generated and / or received via the observation hub when transferring physiological observations. The identification data may include data associated with the user and may be used to identify the user. The identification data may comprise a user ID. The identification data may include tags, markers, serial numbers, barcodes, QR codes, facial recognition, fingerprint recognition, voice recognition, eye recognition, gesture recognition, etc. The identification data may be specific to a user. The identification data may be specific to a group of users (and may be the same for individuals within a group). The identification data may be used to identify a group to which the user belongs. The identification data may comprise or indicate authority associated with the user, such as authority or privilege to transfer physiological observations. The identification data may include a reason for requesting the transfer (e.g., provided by the requesting user). A computing device, such as an observation hub, can 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 observation hub to be detected by the observation hub. A computing device, such as an observation hub, can receive identification data via manual user input at the observation hub. For example, a user may enter identification data at the observation hub via a keyboard, user interface, touch screen, etc. A computing device, such as an observation hub, can receive identification data via one or more biological markers. For example, a user may scan their finger, eye, face, or voice as their identification data to be identified at the observation hub. The identification data can be linked or paired with a migration request.

[0106] In some implementations, the transition request status may indicate the status of the request to transition the physiological observations. The transition request status may include an approved state or an unapproved state. In some implementations, the transition request may be approved if the identification data from the first observation hub matches the identification data from the second observation hub. The transition request may be approved if the requesting user has proper authority to perform the transition. In some implementations, the transition request may not be approved if the identification data from the first observation hub does not match the identification data from the second observation hub. The transition request may not be approved if the requesting user does not have proper authority to perform the transition.

[0107] In some implementations, the wireless communication configuration data may comprise data used to establish wireless communications between one or more computing devices. For example, an observation hub and a sensor may implement the wireless communication configuration data to communicate with each other via one or more wireless communication protocols. The wireless communication configuration data may include device addresses of one or more computing devices, such as the observation hub and / or the sensor. The wireless communication configuration data may include access codes, such as one or more of Inquiry Access Codes (IAC), Device Access Codes (DAC), and Channel Access Codes (CAC). The access codes may include and / or be derived from device addresses. The wireless communication configuration data may include a link key. The wireless communication configuration data may include clock data, such as frequencies at which the computing devices communicate (e.g., to 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.

[0108] In some implementations, the device address may facilitate wireless communication between computing devices. The device address may be associated with a computing device. The device address may be unique to a computing device. The device address may comprise an IP address. The device address may comprise a MAC address. The device address may comprise a serial ID associated with the computing device. The device address may comprise a Bluetooth Address (BD_ADDR). The device address may comprise a LAP value. The device address, or a derivative thereof, may form at least a portion of an access code.

[0109] In some implementations, a link key may facilitate wireless communication between computing devices. The link key may authenticate one or more computing devices to one another. The link key may encrypt data exchanged wirelessly between one or more computing devices. The link key may comprise a Long-Term Key (LTK).

[0110] In some implementations, the physiological data may include data generated by one or more sensors. The physiological data may correspond to a subject. The physiological data may include raw data, partially processed data, and / or fully processed data. The physiological data may include physiological parameters. The physiological data may include, by way of non-limiting example, data regarding heart rate, respiratory rate, blood pressure, blood oxygen saturation, hemoglobin content, ECG, EEG, body temperature, subject posture, subject position, and subject movement. The physiological data may include historical physiological data. The historical physiological data may include historical data generated by sensors over a time frame prior to the current time. The 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. The physiological data may include real-time physiological data. Real-time physiological data may include physiological data that is transmitted and / or received at substantially the same time as the physiological data is generated by the sensor, such that, for example, any time difference may be imperceptible to human senses.

[0111] Exemplary System 1A is a schematic block diagram illustrating an example implementation of a physiological monitoring system (PMS) 150. PMS 150 may include an observation hub 100A, an observation 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 observation hubs (e.g., hubs 100A, 100B). In some implementations, PMS 150 may include more than two observation hubs. In some implementations, PMS 150 may include only one observation hub.

[0112] The observation hub 100A can communicate with one or more sensors 102. In some implementations, the observation hub 100A may communicate with one or more sensors 102 via a wireless communication protocol, such as WiFi, Bluetooth, near field communication (NFC), radio frequency identification (RFID), cellular, 1G, 2G, 3G, 4G, 5G, and / or Zigbee. In some implementations, the sensor 102 may be a “slave” in a master-slave communication relationship, such as a Bluetooth communication protocol, with the observation hub 100A. In some implementations, the sensor 102 may communicate with only one device (e.g., a “master” device), such as the observation hub, at a time. The observation hub 100A may communicate data to and / or receive data from one or more sensors 102. For example, the observation hub 100A may receive physiological data from one or more sensors 102. As another example, observation 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 observation hubs 100A, 100B) to one or more sensors 102. In the example implementation shown in FIG. 1A, observation hub 100B does not establish direct wireless communication with one or more sensors 102.

[0113] Observation hubs 100A, 100B can communicate with server 106 via network 104. Network 104 may include any one or more communications networks, such as the Internet. 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. Accordingly, the various components of PMS 150 can communicate with each other directly or indirectly via any suitable communications link and / or network, such as network 104 (e.g., one or more communications links, one or more computer networks, one or more wired or wireless connections, the Internet, any combination of the above, etc.). Similarly, the various components of PMS 150 (e.g., as described below) may, in various implementations, communicate with each other directly or indirectly via any suitable communications link (e.g., one or more communications links, one or more computer networks, one or more wired or wireless connections, the Internet, any combination of the above, etc.). The observation 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 observation hub 100), physiological data, identification data (user ID), migration requests, request approval status, etc. The observation 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 implementations, the observation hub 100 may communicate with the server 106 via a different wireless communication protocol than the one via which it communicates with one or more sensors 102.For example, the observation hub 100 may communicate with the server 106 via a first wireless communication protocol, such as WiFi, and may communicate with one or more sensors 102 via a second wireless communication protocol, such as Bluetooth.

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

[0115] In some implementations, observation hub 100A may be portable or mobile. For example, observation hub 100A may be sized, shaped, and / or include a housing or casing that facilitates carrying observation hub 100A, such as by hand. In some implementations, observation hub 100A may be stationary or fixed in position. For example, observation hub 100A may be mounted to a wall. In some implementations, observation hub 100B may include similar structural and / or operational features as observation hub 100A. Observation hub 100A may be referred to herein as the source observation hub. Observation hub 100B may be referred to herein as the destination observation hub.

[0116] The one or more sensors 102 may include various types of sensors configured to collect physiological data of the subject. The one or more sensors 102 may be attached to or coupled to different parts of the subject, such as, but not limited to, the arms, legs, torso, chest, head, neck, fingers, forehead, etc. The one or more sensors 102 may collect physiological data of the patient, including, but not limited to, heart rate, respiratory rate, blood pressure, blood oxygen saturation, hemoglobin level, ECG, EEG, body temperature, subject posture, subject position, subject movement, etc. The one or more sensors 102 may transmit physiological data in real time to the observation hub 100A, the observation hub 100B, and / or the server 106 while collecting the data. In some implementations, the one or more sensors 102 may include a processor capable of fully or partially processing data acquired by the sensors 102.

[0117] The server 106 may comprise one or more computing devices including one or more hardware processors. The server 106 may comprise program instructions configured, when executed by the hardware processor, to cause the server 106 to perform one or more operations. The server 106 may include and / or have access to (e.g., be in communication with) a database or storage component or storage system, which may include any computer-readable storage medium and / or device (or 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), memory circuitry (e.g., solid-state drive, random access memory (RAM), etc.), etc. In some implementations, the server 106 may include and / or be in communication with a hosted storage environment, including a collection of physical data storage devices (commonly referred to as "cloud" storage) that are remotely accessible and can be rapidly provisioned as needed. Data stored on and / or accessible by the server 106 may include physiological data, including historical physiological data previously obtained by one or more sensors 102, and / or communication data, including, for example, link keys and / or device addresses associated with observation hubs, sensors, etc.

[0118] In some implementations, the network 104 may comprise and / or be in communication with an electronic medical record (EMR). In some implementations, the server 106 may comprise and / or be in communication with an EMR. In some implementations, one or more of the observation hubs 100A, 100B may be in communication with an EMR. The EMR may comprise a proprietary EMR. The EMR may comprise an EMR associated with a hospital. The EMR may store data including medical records.

[0119] FIG. 1B is a schematic block diagram illustrating an additional exemplary implementation of a physiological monitoring system (PMS) 150. The exemplary implementation illustrated in FIG. 1B may result from a request to migrate a physiological observation from observation hub 100A to observation hub 100B. Migrating a physiological observation from one observation hub to another is described in more detail herein, for example, with respect to at least FIG. 4 and / or FIG. 5A-5E. For example, as shown in the exemplary implementation of FIG. 1A, sensor 102 may be in communication with observation hub 100A or may not be in communication with observation hub 100B. PMS 150 can migrate the physiological observation from observation hub 100A to observation hub 100B (e.g., in response to a user request). As shown in FIG. 1B, after PMS 150 migrates the physiological observation from observation hub 100A to observation hub 100B, sensor 102 may be in communication with observation hub 100B or may not be in communication with observation hub 100A. The observation 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 protocol) established with the sensor 102 as a result of the transition.

[0120] The observation hubs 100A, 100B can receive user input 108. The user input 108 may include identification data and / or a migration request. The user input 108 may be manual user input, such as via a display on the observation hubs 100A, 100B or one or more buttons on the observation hubs 100A, 100B. For example, a user may press a button on the observation hubs 100A, 100B to request a migration. The user input 108 may include electronic input, such as an electronic signal generated in response to a wireless communication protocol. For example, a user may bring a communication device (e.g., a user ID badge) near the observation hubs 100A, 100B to generate an electrical signal (e.g., via NFC and / or RFID) at the observation hubs 100A, 100B.

[0121] In some implementations, observation hub 100A can optionally communicate with observation hub 100B. In some implementations, observation hub 100A may communicate with observation hub 100B via a wireless communication protocol, such as WiFi, Bluetooth, near field communication (NFC), radio frequency identification (RFID), cellular, 1G, 2G, 3G, 4G, 5G, and / or Zigbee. Observation hub 100A may communicate data to and / or receive data from observation hub 100B, including communication data (e.g., device addresses of sensors 102), physiological data, identification data (e.g., user ID), migration requests, request approval status, etc. In some implementations, observation hub 100A may communicate with observation hub 100B only while PMS 150 is migrating physiological observations from observation hub 100A to observation hub 100B. For example, in some implementations, observation hub 100A may communicate with observation hub 100B only until the transition is complete, until observation hub 100B establishes communication with sensor 102, etc. In some implementations, observation hub 100A may communicate with observation hub 100B to facilitate the transition (e.g., may send communication data to facilitate establishing communication between observation hub 100B and sensor 102). In some implementations, observation hub 100A may not communicate with observation hub 100B.

[0122] FIG. 1C illustrates an exemplary implementation of a physiological monitoring system (PMS) including observation hubs 110A, 110B, and one or more sensors 122. The PMS, or portions thereof, shown and discussed in FIG. 1C may include similar structural and / or operational features as PMS 150, or portions thereof, shown and / or discussed in FIGS. 1A-1B. For example, observation hub 110A may include similar structural and / or operational features as observation hub 100A discussed in FIGS. 1A-1B. As another example, observation hub 110B may include similar structural and / or operational features as observation hub 100B discussed in FIGS. 1A-1B. As another example, one or more sensors 122 may include similar structural and / or operational features as sensor 102 discussed in FIGS. 1A-1B.

[0123] As shown in this exemplary implementation, observation hub 110A is observing physiological data of subject 111, and observation hub 110B is not observing physiological data of subject 111.

[0124] The one or more sensors 122 may be configured to acquire physiological data of the subject 111. The observation hub 110A is in electrical communication with the one or more sensors 122. In some implementations, the electrical communication between the observation hub 110A and the one or more sensors 122 may include a wireless communication protocol such as Bluetooth. The observation hub 110A receives the 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 observation hub 110A displays an indication of and / or information about the physiological data on a display of the observation hub 110A.

[0125] Observation hub 110B is not in electrical communication with sensors 122. Observation hub 110B does not receive or display physiological data from sensors 122. A user, such as a healthcare provider (e.g., doctor, nurse, etc.), may desire to migrate physiological observations from observation hub 110A to observation hub 110B. As described in more detail herein, a user can migrate physiological observations from observation hub 110A to observation hub 110B such that observation hub 110B receives and displays physiological data from one or more sensors 122 and observation hub 110A1 stops receiving and / or displaying physiological data from the one or more sensors 122. Following the migration of the physiological observations, observation hub 110B may display indicators of the physiological data that were previously displayed in observation hub 110A. Observation hub 110B may display a user interface that is similar or identical in whole or in part to the user interface previously displayed by observation hub 110A.

[0126] 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, earpiece, etc. The one or more sensors 122 may include an ECG device 113, which may include and / or be coupled to one or more ECG electrodes 112. The one or more sensors 122 may include a body 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 comprise a wristwatch. The wearable device 113 may include one or more sensors. The one or more sensors 122 may include an optical sensor 140, which may comprise a fingerprint 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. Wearable hub 130 may be coupled to one or more of the sensors shown and / or described herein. Wearable hub 130 may be in communication with one or more of the sensors shown and / or described herein. Wearable hub 130 may receive data from one or more of the sensors shown and / or described herein. In some implementations, wearable hub 130 may be in communication with observation hub 110A and / or observation hub 110B. In some implementations, wearable hub 130 may collect sensor data from one or more sensors and communicate the sensor data to observation hub 110A and / or observation hub 110B. In some implementations, one or more of the sensors shown and / or described herein may be in direct communication with observation hub 110A and / or observation hub 110B.For example, wearable device 113, ear device 123, optical sensor 140, ECG device 113, acoustic sensor 116, body temperature sensor 114, motion sensor 115, blood pressure monitor 121 may communicate directly with observation hub 110A and / or observation hub 110B, such as via wireless communication. In some implementations, the one or more sensors may include one or more of an infusion pump, a brain observation device, a depth of consciousness device, or a pacemaker.

[0127] Observation hub 110A is shown as being in a fixed position (e.g., mounted to a wall). Observation hub 110A may be removably mounted to a wall. Observation hub 110B is shown as being placed on a surface near subject 111 and may be portable or mobile (e.g., not fixed to a specific location). Observation hub 110B is housed within holder 132. Holder 132 is configured to support the observation hub in an upright position. In some implementations, observation hub 110B may be fixed to a specific location or may be removably fixed. For example, observation hub 110B may be coupled to a structure such as a bed by holder 132. In some implementations, observation hub 110A may be portable or mobile. In some implementations, observation hub 110A may be housed within a holder similar to or identical to holder 132.

[0128] 1D is a schematic block diagram illustrating an implementation of an exemplary physiology monitoring system (PMS) 160. PMS 160 may include similar features to other PMSs discussed herein, such as PMS 150 shown and / or discussed with respect to FIGS. 1A-1B. The operations, processes, and functions of PMS 160 may be performed by one or more computing devices (e.g., hardware processors of a computing device), such as any of the computing devices discussed herein, such as, for example, monitoring hubs, sensors, and / or servers.

[0129] PMS 160 may receive one or more inputs. PMS 160 may receive a migration request 162. PMS 160 may receive migration request 162 via one or more observation hubs described in more detail elsewhere herein, such as, for example, those shown and / or discussed with respect to FIG. 4. PMS 160 may receive identification data 164. PMS may receive identification data 164 via one or more observation hubs described in more detail elsewhere herein, such as, for example, those shown and / or discussed with respect to FIG. 4.

[0130] The PMS 160 can receive and / or access physiological data 166. The PMS 160 can receive physiological data 166 from one or more physiological sensors. In some implementations, an observation hub of the PMS 160 can receive physiological data 166 in real time and / or directly from one or more sensors. In some implementations, a server of the PMS 160 can receive physiological data 166 in real time and / or directly from one or more sensors. In some implementations, the observation hub of the PMS 160 can transmit physiological data 166 to a server of the PMS 160 after receiving it from the sensors.

[0131] PMS 160 can receive and / or access communication data 168. The communication data may include data to facilitate establishing communications between computing devices. The communication data may include, for example, a device address of a computing device, such as a device address of an observation hub and / or a physiological sensor. PMS 160 can access computing device communication data 168 from a computing device. The PMS can transmit communication data 168 between computing devices of PMS 160, such as between observation hubs, sensors, and / or servers.

[0132] PMS 160 may process one or more inputs (e.g., inputs 162, 164, 166, 168) to generate an output. PMS may process inputs as described in more detail elsewhere herein, such as those shown and / or discussed with respect to FIGS. 5A-5E . PMS 160 may output a physiology observation transition operation 169 in response to receiving and / or processing one or more inputs. Physiology observation transition operation 169 may include transitioning a physiology observation from one observation hub of PMS 160 to another observation hub of PMS 160. Physiology observation transition operation 169 may be described in more detail elsewhere herein, such as those shown and / or discussed with respect to FIGS. 5A-5E .

[0133] Exemplary Implementation 2 is a block diagram illustrating an example implementation of observation hub 200. Observation hub 200 may include similar structural and / or operational features as any of the other example observation hubs shown and / or discussed herein, such as observation hubs 100A, 100B discussed in FIG.

[0134] As shown, observation hub 200 may include a hardware processor 201, a storage component 205, a communication component 207, and a battery 203. Hardware processor 201 may be configured to, among other things, process data, execute program instructions to perform one or more functions, and / or control the operation of observation hub 200. For example, hardware processor 201 may process physiological data obtained from physiological sensors and execute instructions to perform functions related to the storage and / or transmission of such physiological data. As another example, hardware processor 201 may process data related to transition requests, identification data, and / or transition approval status.

[0135] The storage component 205 may include one or more memory devices for storing 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 can store data including processed and / or unprocessed physiological data obtained from physiological sensors. The storage component 205 can store data including communication data, such as link keys and / or device addresses associated with sensors and / or observation hubs.

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

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

[0138] The observation hub 200 may include a display 209. The display 209 may comprise an LED display. The display 209 may comprise a touch screen, such as a capacitive touch screen. The display 209 may receive user input. The display 209 may render one or more user interfaces. The display 209 may display an indication of physiological data.

[0139] The observing hub 200 may include one or more speakers 211. The speaker 211 may emit audio signals. The speaker 211 may emit warning sounds. The speaker 211 may emit voice audio signals. The speaker 211 may include multiple speakers spaced apart from one another at various locations on the observing hub 200. The speaker 211 may emit stereo sound. The speaker 211 may emit sound using one or more audio channels. The speaker 211 may emit sound in multiple directions. The speaker 211 may emit mono sound. The speaker 211 may emit sounds occurring during voice and / or video calls.

[0140] The observation hub 200 may include one or more microphones 213. The microphone 213 may detect audio signals and generate signals in response to the detected audio signals. The microphone 213 may detect environmental noise levels. The microphone 213 may detect noise levels in the environment around the observation hub 200. The microphone 213 may detect noise levels in the environment adjacent to and / or surrounding the subject. The observation hub 200 may adjust one or more actions based at least on the ambient noise level detected by the microphone 213. The observation hub 200 may perform one or more actions to increase patient comfort 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 an audio call and / or a video call.

[0141] The observation hub 200 can conduct voice calls. The observation hub 200 can be connected to one or more cellular devices. The observation hub 200 can conduct voice calls using cellular phone technology, such as via the communications component 207. The observation hub 200 can conduct video calls. A patient being observed by the observation hub 200 can speak with another person at a remote location, such as a caregiver, via the observation hub 200, and the observation hub 200 can implement one or more wireless communication protocols, such as cellular phone technology, to connect to one or more remote computing devices over a network and can detect the patient's voice using a microphone 213.

[0142] The observation 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 with one or more LEDs. The indicator 214 may emit one or more visual signals. The visual signals may correspond to a physiological state of the patient being observed by the observation hub 200. The indicator 214 may emit a visual signal including multiple colors. The indicator 214 may emit a visual signal according to a color-coded scheme, where different colors may correspond to different physiological states of the patient being observed by the observation hub 200.

[0143] FIG. 3A is a perspective view of an exemplary observation hub 300. The observation hub 300 may include similar structural and / or operational features as any of the other exemplary observation hubs shown and / or described herein. In this exemplary implementation, the observation hub 300 is secured within a holder 332. The observation hub 300 may be removably secured within the holder 332, for example, via a friction fit. In this exemplary implementation, the observation hub 300 may include a display 302. The display 302 may include an LED display. The display 302 may include a touchscreen configured to receive user input in response to touching the display 302. The display 302 may display indicators of physiological data, including physiological trends, graphs, images, tables, parameters, values, percentages, animations, visualizations, and the like. The display 302 may display indicators of physiological data from multiple sensors, including different types of sensors measuring different types of physiological data. The observation hub may generate (and / or receive) user interface data for rendering display indicators based at least on physiological data generated from one or more sensors or other devices.

[0144] The observation 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 a subject being observed by the observation hub 300. For example, the status indicator 304 may illuminate in response to any change in the subject's physiological data, such as a physiological parameter of the subject, exceeding a threshold. The status indicator 304 may illuminate in different colors in different operations or modes. The status indicator 304 may illuminate (e.g., red) in an alert mode. The status indicator 304 may not illuminate when the observation hub 300 is not in an alert mode.

[0145] The observation hub 300 may include a communication interface 306. The communication interface 306 may include electronics configured to implement 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's phone, a user's mobile device, or a user's smartwatch, to identify and / or verify a user, such as by receiving unique user identification information from the user device.

[0146] The observation hub 300 may include a transition request button 308. The transition request button 308 may include a capacitance sensor configured to generate one or more signals in response to a user's touch. The transition request button 308 may include one or more physical or mechanical actuators configured to generate one or more signals in response to a physical actuation of the button 308, such as a press of the button 308. A user may press the transition request button 308 to initiate a transition of a physiological observation to or from the observation hub 300. In some implementations, the transition request button 308 may be incorporated into the display 302 (e.g., as part of a touchscreen display).

[0147] 3B is a perspective view of an exemplary observation hub 310. The observation hub 310 may include similar structural and / or operational features as any of the other exemplary observation hubs shown and / or described herein. The observation 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 observation hub 310 may vary the brightness of the display 312 based on the ambient light detected by the light sensor 319. The microphone 321 may be configured to detect sound. In some implementations, the observation hub 310 may receive user input, such as a transition request, as a voice command via the microphone 321. In some implementations, the observation hub 310 may perform voice recognition on sounds detected by the microphone 321. The indicator 323 may include one or more LEDs. The indicator 323 may include the status and / or operational status of the observation hub 310, such as the power level, the status of the wireless connection, etc. A user may operate buttons 525 to control the operation of the viewing hub 310 .

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

[0149] In some implementations, the observation hub 310 may include an alert toggle button 339. A user may press the alert toggle button 339 to silence an audible alert. A user may press the alert toggle button 339 to change the status of an alert. The alert toggle button 339 may comprise a capacitance sensor. The alert toggle button 339 may comprise one or more mechanical actuators.

[0150] FIG. 4 illustrates an exemplary process for migrating physiological observations from one observation hub (e.g., a source hub) to another observation hub (e.g., a destination hub) within a physiological observation system (PMS). Advantageously, as described herein, the PMS can facilitate faster, easier, and more efficient migration of physiological observations from one observation hub to another. For example, the PMS provides an intuitive and easy-to-use system (e.g., an observation hub user interface) for migrating physiological observations, which can reduce the amount of time a healthcare provider must spend supervising a subject's physiological observations and improve the quality of healthcare services provided to the subject. The process illustrated in FIG. 4 is provided as an example and is not intended to limit the present disclosure. In some implementations, some parts (e.g., steps) may be added, removed, and / or reordered.

[0151] In step 4001, the observing hub 400A (e.g., a source observing hub) observes physiological data of a subject. For example, the observing hub 400A may be in communication with one or more physiological sensors and receives physiological data therefrom. The observing hub 400A displays an indication of the physiological data on the display 402A. To initiate the transfer of observations from the observing hub 400A, the user can press the transfer request button 408A.

[0152] In step 4002, the display 402A may cease displaying physiological data, indicating that the observation hub 400A has entered a "transition mode" of operation. The display 402A may include instructions to the user for entering identification data (e.g., "Tap your badge to this device to authenticate"). The display 402A may include instructions and a graphical depiction 405A of actions to be taken by the user.

[0153] In step 4002, a user enters identification data into the observation hub 400A. In this example, as shown, the user moves a 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 from the user ID device 407A, including the user's identification information. For example, the identification data may include a unique user ID (e.g., a serial number, a data sequence, etc.) associated with the user. In this example, the user ID device 407A may include a card or badge. In some implementations, the user ID device 407A may include a phone, a mobile device, a tablet, a smartwatch, etc. In some implementations, the user may manually enter the identification data, including the identification information, at the observation hub 400A (e.g., via the display 402A). In some implementations, the identification data may include one or more biomarkers of the user (e.g., facial recognition, fingerprint recognition, eye recognition, voice recognition), and the observation hub 400A may include one or more devices configured to receive and identify the biomarkers.

[0154] In some implementations, in response to receiving the identification data at observation hub 400A, the PMS may determine whether the user has authorization to perform the transition, for example, as shown and / or discussed with respect to FIG. 5A. Receiving the identification data at step 4002 may cause observation hub 400A to terminate a wireless communication connection, such as a Bluetooth connection, with one or more sensors. In some implementations, receiving the identification data at step 402 may cause observation hub 400B to establish a wireless communication connection, such as a Bluetooth connection, with one or more sensors.

[0155] In step 4003, display 402A may show the identity of the user requesting the transition (e.g., "You are logged in as Dr. John Doe"). Display 402A may show instructions to the user for requesting transition to a second observation hub and providing identity at the second observation hub (e.g., "Select 'Transition Mode' on the destination device and authenticate with your badge"). Display 402A may include a graphical depiction 405A of the instructions and actions to be taken by the user.

[0156] In step 4004, observing hub 400B (e.g., the destination observing hub) may not be observing physiological data for the subject. For example, observing hub 400B may not be in communication with and receiving physiological data from one or more physiological sensors. Observing hub 400B may not be displaying physiological data on display 402B. To initiate the transfer of observation to observing hub 400B, the user may press transfer request button 408B, for example, in response to instructions provided on display 402A in step 4003.

[0157] At step 4005, display 402B indicates that observation hub 400B has entered "transition mode" operation. Display 402B may include instructions to the user for entering identification data (e.g., "Tap your badge to this device to authenticate"). Display 402B may include instructions and a graphical depiction 405B of the action to be taken by the user.

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

[0159] In some implementations, in response to receiving the identification data at the observation hub 400B, the PMS may determine whether the user has authorization to perform the transition, for example, as shown and / or discussed with respect to FIG. 5A. Receiving the identification data at step 4005 may cause the observation hub 400A to terminate a wireless communication connection, such as a Bluetooth connection, with one or more sensors. Receiving the identification data at step 4005 may cause the observation hub 400B to establish a wireless communication connection, such as a Bluetooth connection, with one or more sensors. Receiving the identification data at step 4005 may cause the observation hub 400B to initiate a paging process to establish a Bluetooth connection with one or more sensors.

[0160] After receiving the identification data at observing hub 400B, 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 observing hub 400A with the identification data received at observing hub 400B. Determining that the transfer request is approved may include comparing the user ID of the identification data received at observing hub 400A with the user ID of the identification data received at observing hub 400B. In some implementations, the PMS may determine that the transfer request is approved if the identification data received at observing hub 400A matches the identification data received at observing hub 400B. In some implementations, the PMS may determine that the transfer request is approved if the identification data received at observing hub 400A corresponds to the identification data received at observing hub 400B. Identification data may correspond, even if it does not match or match identically, if the identification data corresponds to two users in the same group, two users assigned to the same job, two users assigned to the same patient, two users with the same schedule, etc. For example, if two users work together to care for a patient, one user may enter their identification data at the source observation hub and the other user may enter their identification data at the destination observation hub, and the PMS may determine that the two identification data correspond (although they may not match exactly). Additional details regarding determining approval of a migration request are shown and / or discussed with respect to FIG. 5A.

[0161] In response to receiving the identification data and determining that the request to migrate is approved, the PMS may establish wireless communications, such as a Bluetooth connection, between the observation hub 400B and one or more of the physiological sensors that were previously in communication with the observation hub 400B. Establishing wireless communications may include initiating a paging process of the Bluetooth protocol. Establishing wireless communications may not include a pairing process of the Bluetooth protocol. Additional details regarding establishing communications between the observation hub 400B and the physiological sensors are shown and / or discussed with respect to FIGS. 5A-5E .

[0162] In some implementations, the PMS may establish communication between observation hubs 400A and 400B. Establishing communication between observation hubs 400A and 400B can facilitate communication of information therebetween, including, for example, communication data (e.g., device addresses of physiological sensors), physiological data (e.g., historical physiological data), etc.

[0163] In step 4006, observation hub 400A may stop displaying the indication of the physiological data and / or other data via display 402A. Observation hub 400B may begin displaying the indication of the physiological data and / or other data via display 402B. In some implementations, observation hub 400B may begin displaying the data after observation hub 400A has stopped displaying the data. In some implementations, observation hub 400B may begin displaying the data before observation hub 400A has stopped displaying the data. In some implementations, observation hub 400B may begin displaying the data at the same time that observation hub 400A has stopped displaying the data.

[0164] In step 4006, the observation hub 400B can display the physiological data via the display 402B. The physiological data displayed on the display 402B can include real-time physiological data received from a sensor in communication with the observation hub 400B. The physiological data displayed on the display 402B can include historical physiological data collected by the sensor prior to establishing communication between the sensor and the observation hub 400B. For example, the observation hub 400B can receive, from the observation hub 400A and / or a PMS server, historical physiological data collected by the sensor and / or received at the observation hub 400A prior to the observation hub 400B establishing communication with the sensor. The historical physiological data does not have to be received at the observation hub 400A directly from the sensor. Advantageously, by displaying historical physiological data in combination with real-time physiological data (e.g., received from a sensor), the observing hub 400B may display the physiological data as if the observing hub 400B were observing the physiological data (e.g., receiving data obtained from a sensor) at a time prior to when the observing hub 400B began observing the physiological data. Advantageously, because the destination observing hub (e.g., observing hub 400B) can display the data prior to the transition, transferring an observation from one hub to another may not result in data loss or unviewable data. Advantageously, a user may be able to view physiological data after transferring an observation from one observing hub to another with little or no disruption, interruption, data loss, or the like. Advantageously, the PMS may be configured to continuously monitor the subject's physiology while transferring physiological observations from one observing hub to another.

[0165] In some implementations, the PMS may transition physiological observations as shown and / or described with respect to FIG. 4 without receiving physical user input, such as a button press, in steps 4001 and / or 4004. For example, a user may not have to press a button, such as button 408A, on observation hub 400A to request a transition. As another example, a user may not have to press a button on observation hub 400B, such as button 408A, to place observation hub 400B in a transition mode. In some implementations, a user may request to transition physiological observations by entering identification data via NFC / RFID or the like, as described step 4002. In some implementations, a user may place observation hub 400B in a transition mode by entering identification data via NFC / RFID or the like, as described step 4005. Thus, the devices and systems described herein may provide a method for transitioning physiological observations by implementing contactless user input. For example, a user may transition physiological observations without physically contacting the observation hub, such as by pressing a button. Other examples include transitioning physiological observations without requiring a user to unplug or replug a device, turn the device on or off, or change the operating mode of a device, such as to place the device in pairing mode, discovery mode, or connection mode. Reducing physical contact may be more hygienic, improve the speed and efficiency of transitioning physiological observations, and reduce the complexity of transitioning physiological observations, such as by reducing the number of steps required to transition physiological observations. Contactless input may comprise near-field communication (NFC) and / or radio frequency identification (RFID). Contactless input may comprise facial recognition, eye recognition, fingerprint recognition, gesture recognition, voice recognition, etc. Contactless input may comprise minimal-contact input. Moreover, the devices and systems described herein may provide methods for user-managed transitioning of physiological observations. For example, a user may manage when to transition physiological observations, such as by providing user input to the system, which may include contactless user input.Controlling the transition of physiological observations with user input may reduce erroneous or undesired transitions that may occur, for example, due to the proximity of devices to one another. In some implementations, the system may automatically transition physiological observations without requiring user input, such as by implementing a proximity-based wireless communication connection.

[0166] In some implementations, the PMS may transfer physiological observations between the observation hub and multiple sensors as shown and / or described with respect to FIG. 4. The PMS may transfer wireless communication connections for multiple sensors at once. The PMS may transfer wireless communication connections for multiple sensors in response to a single user input. The PMS may transfer wireless communication connections for multiple sensors in response to a single request to transfer physiological observations. Advantageously, transferring physiological observations for multiple sensors at once may improve the speed and efficiency of transferring physiological observations, such as by not having to repeatedly perform similar transfer procedures for each sensor.

[0167] Exemplary Methods FIG. 5A is a flowchart illustrating an example process 500A for migrating physiological observations from a source observation hub to a destination observation hub. One or more hardware processors can perform process 500A, or portions thereof. Process 500A, or portions thereof, may be implemented on one or more computing devices described herein, such as a source observation hub, a destination observation hub, or a server. Process 500A, or portions thereof, may be performed by one or more hardware processors of a single computing device. Process 500A, or portions thereof, may be performed by one or more hardware processors of multiple computing devices, such as computing devices that are remote from each other and / or in wireless communication with each other. In some implementations, one or more hardware processors associated with a server, such as server 106 shown and / or described herein, may perform process 500A, or portions thereof. Process 500A is provided as an example and is not intended to limit the present disclosure. In some implementations, the one or more hardware processors performing process 500A may omit portions of process 500A, add additional operations, and / or rearrange the order in which the operations of process 500A are performed.

[0168] At block 501, one or more hardware processors may receive a request to migrate physiological observations from one observing hub (e.g., a source observing hub) to another observing hub (e.g., a destination observing hub). In some implementations, the source observing hub and / or the destination observing hub may receive the request to migrate, for example, as shown and / or described with respect to FIG. 4 . The one or more hardware processors may receive the request via user input at the observing hub. The user input may comprise pressing a button on the observing hub. In some implementations, process 500 may not include block 501. For example, the computing device may receive identification data as discussed in block 503 without receiving a request to migrate at block 501. In some implementations, the request to migrate physiological observations may comprise a request to establish an initial physiological observation at one observing hub without terminating the physiological observation at another observing hub, such as when the physiological observation is being established for the first time or when no physiological observations have been made recently prior to the request.

[0169] At block 503, one or more hardware processors may receive identification data. The identification data may be associated with a user requesting the migration. The one or more hardware processors may receive the identification data via an observing hub, such as a source observing hub and / or a destination observing hub. The identification data may be associated with the observing hub at which the hardware processor received it. In some implementations, the source observing hub may receive the identification data, for example, as shown and / or described with respect to FIG. 4. In some implementations, receiving the identification data may serve as receiving a request to migrate physiological observations as described in block 501. For example, process 500A may not perform block 501 or may perform block 501 as part of block 503.

[0170] At decision block 505, the one or more hardware processors may determine whether the user requesting to transfer the physiological observations has the appropriate authority to perform the transfer. In some implementations, the one or more hardware processors may determine whether the requesting user has authority based at least in part on the identification data received at block 503.

[0171] In some implementations, the one or more hardware processors may determine whether the requesting user has appropriate authority based on one or more of the user's identity, the user's job title, the user's role, the user's assigned duties, etc., which may be determined by the identification data. For example, a doctor (e.g., identified by a user ID included in the identification data) may have authority to perform the transition, while a nurse may not. As another example, one type of doctor (e.g., a cardiologist) may have authority to perform the transition, while another type of doctor (e.g., a surgeon) may not. As another example, a healthcare provider assigned to the patient may have authority to perform the transition, while a healthcare provider not assigned to the patient may not.

[0172] In some implementations, the one or more hardware processors may determine whether the requesting user has appropriate authority based on the time of the request. For example, the user may not have authority to transfer physiological observations between observation hubs while the subject being observed is undergoing surgery, sleeping, during a scheduled meal, etc. In some implementations, the one or more hardware processors may determine whether the requesting user has appropriate authority based on a user-provided reason that may be entered by the user in the observation hub (e.g., as part of the identification data). In some implementations, the one or more hardware processors may determine whether the requesting user has appropriate authority based on the location of the subject being observed and / or the location of the observation hub. For example, the user may not have authority to transfer physiological observations from an observation hub deployed in a particular hospital room to a mobile observation hub if the subject is scheduled to remain in that room. As another example, the user may not have authority to transfer physiological observations from a mobile observation hub to an observation hub deployed in a particular hospital room if the subject is scheduled to be away from that room (e.g., an operating room) (e.g., the subject is not scheduled for surgery).

[0173] Advantageously, verifying the permissions associated with a user can improve the quality of medical care by ensuring that the PMS transfers physiological observations only under appropriate conditions to ensure that the subject receives appropriate medical care (e.g., the subject is not moved to a different room in a hospital when it is not appropriate).

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

[0175] In 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 migration. The one or more hardware processors may receive the other identification data via an observing hub, such as a source observing hub and / or a destination observing hub. The other identification data may be associated with the observing hub at which the hardware processor received the other identification data. In some implementations, the destination hub may receive the other identification data, for example, as shown and / or described with respect to FIG. 4.

[0176] At decision block 509, one or more hardware processors may determine whether the identification information corresponds to other identification data. The one or more hardware processors may compare the identification data. For example, the one or more hardware processors may compare the identification data received by the source observing hub with the identification data received by the destination observing hub. In some implementations, comparing the identification data may include determining whether the identification data received at the source observing hub corresponds to the identification data received at the destination observing hub. In some implementations, comparing the identification data may include determining whether the identification data received at the source observing hub matches the identification data received at the destination observing hub. In some implementations, comparing the identification data may include comparing user identification information included in the identification data.

[0177] In some implementations, the one or more hardware processors may determine that the identification data correspond if the identification data (or portions thereof) in each of the respective identification data match each other, e.g., if they are identical or substantially similar. This may indicate, for example, that the user requesting the migration at the source observing hub is the same user as the user requesting the migration at the destination observing hub. In some implementations, the one or more hardware processors may determine that the identification data do not correspond if the identification data (or portions thereof) in each of the respective identification data do not match each other. This may indicate that the user requesting the migration at the source observing hub is not the same user as the user requesting the migration at the destination observing hub.

[0178] In some implementations, the one or more hardware processors may determine that the identification data corresponds when the respective identification information is associated with one another. This may indicate that the user requesting the transition at the source observation hub is associated with the user requesting the transition at the destination observation hub. For example, if the user requesting the transition at the source observation hub and the user requesting the transition at the destination observation hub work together (e.g., simultaneously providing medical services to a patient being observed by the PMS), the user requesting the transition at the source observation hub may be associated with the user requesting the transition at the destination observation hub. In some implementations, the one or more hardware processors may determine that the identification information of a first user is associated with the identification information of a second user if the first user and the second user are in the same group, e.g., are medical providers in the same or similar group and / or location (e.g., floor or treatment room).

[0179] Advantageously, comparing the identification data (e.g., that they correspond) can improve the accuracy of transferring physiological observations from one observing hub to the appropriate observing hub. For example, determining that the identification data correspond to each other can ensure that the PMS transfers the physiological observations to the correct observing hub rather than an incorrect observing hub that may have identification data that does not correspond to the identification data received at the source observing hub. Advantageously, verifying that the identification data correspond can facilitate accurate transfer of physiological observations between desired observing hubs in a PMS that includes multiple observing hubs and / or includes multiple requests to transfer physiological observations between various observing hubs occurring simultaneously or near simultaneously. For example, by verifying that the identification data of the source observation hub and the destination observation hub correspond, the PMS can accurately migrate physiological observations between appropriate pairs of observation hubs (e.g., between the source observation hub and the destination observation hub) at the same time or at similar times, such as between observation hub pair A, between observation hub pair B, and between observation hub pair C, without inaccurately migrating physiological observations between different pairs of hubs (e.g., from hub pair A to hub pair B).

[0180] 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.

[0181] At decision block 511, the one or more hardware processors may optionally determine whether the destination observation hub is within a threshold proximity of the sensor. The one or more hardware processors may determine the proximity of the observation hub to the sensor based at least on wireless signal strength between the observation hub and the sensor. In response to determining that the destination observation 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 destination observation hub is not within the threshold proximity of the sensor, the one or more hardware processors may return to block 501.

[0182] At block 513, the one or more hardware processors may begin migrating the physiological observations to the destination observation hub. Migrating the physiological observations may include establishing wireless communication between one or more sensors and the destination observation hub. Migrating the physiological observations may include terminating wireless communication between one or more sensors and the source observation hub. In some implementations, terminating communication with the source observation hub may precede establishing communication with the destination observation hub. In some implementations, terminating communication may occur automatically as a result of establishing communication. Migrating the physiological observations may include migrating physiological observations associated with all of the sensors in communication with the source observation hub to the destination observation hub. Migrating the physiological observations may include migrating physiological observations associated with less than all of the sensors in communication with the source observation hub to the destination observation hub.

[0183] Advantageously, process 500A can provide a system for migrating physiological observations from one observation hub to another (e.g., establishing and / or terminating communication between an observation hub and a sensor) without requiring the unplugging, plugging, and / or replugging of cables, wiring, etc. of the observation hub and / or physiological sensors.

[0184] FIG. 5B is a flowchart illustrating an example process 500B related to migrating physiological observations from a source observation hub to a destination observation hub. One or more hardware processors can perform process 500B, or portions thereof. Process 500B, or portions thereof, can be implemented on one or more computing devices described herein, such as a source observation hub, a destination observation hub, or a server. Process 500B, or portions thereof, can be performed by one or more hardware processors of a single computing device. Process 500B, or portions thereof, can be performed by one or more hardware processors of multiple computing devices, such as computing devices that are remote from each other and / or in wireless communication with each other. In some implementations, one or more hardware processors associated with a server, such as server 106 shown and / or described herein, can perform process 500B, or portions thereof. Process 500B is provided by way of example and is not intended to limit the present disclosure. In some implementations, the one or more hardware processors performing process 500B may omit portions of process 500B, add additional operations, and / or rearrange the order in which the operations of process 500B are performed.

[0185] At block 521, one or more hardware processors may receive wireless configuration data from the source observation 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 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.

[0186] At block 523, one or more hardware processors may receive physiological data from the source observing hub. The physiological data may include physiological data from one or more sensors received at the source observing hub. The physiological data may include historical physiological data previously received at the observing 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 implementations, the physiological data includes real-time physiological data. The real-time physiological data may include data generated by one or more sensors and transmitted from the source observing hub at a time substantially similar to that transmitted from the source observing hub to the one or more hardware processors. In some implementations, the one or more hardware processors may receive the physiological data as a continuous stream of data from the source observing hub while the source observing hub receives data from the one or more sensors. In some implementations, the one or more hardware processors may receive the physiological data in response to an event, such as in response to a request to migrate physiological observations. In some implementations, the one or more hardware processors may receive the physiological data as packets of data. For example, one or more hardware processors may receive a transmission from a source observation hub of physiological data, which may include physiological data from one or more sensors for a time period.

[0187] In some implementations, one or more hardware processors may receive data associated with the physiological data. The data associated with the physiological data may include user interface data for rendering a user interface comprising a display indicia of the physiological data. The data associated with the physiological data may include a signal corresponding to an alert or alarm generated in response to the physiological data. The data associated with the physiological data may include a condition associated with the subject corresponding to the physiological data.

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

[0189] At block 527, one or more hardware processors may receive a request to establish physiological observations at a destination observation hub. The request to establish physiological observations at a destination observation hub may be included as part of a request to migrate physiological observations from a source observation hub to a destination observation hub. The request to establish physiological observations may indicate one or more sensors with which the destination observation hub should establish wireless communication. The one or more hardware processors may receive the request via one or more observation hubs, such as those shown and / or described herein with respect to FIG. 4 and / or FIG. 5 . In some implementations, the one or more hardware processors may perform block 527 before performing block 521 and / or block 523. For example, the one or more hardware processors may perform block 521 and / or block 523 in response to receiving a request at block 527.

[0190] At block 529, the one or more hardware processors may transmit wireless configuration data to the destination observation hub. The one or more hardware processors may access the wireless configuration data to be transmitted from memory. The wireless configuration data may be associated with one or more sensors with which the destination observation hub is to establish wireless communication. 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 implementations, the wireless configuration data may be associated with the destination observation hub. For example, the wireless configuration data may include one or more link keys associated with the destination observation hub. The one or more hardware processors may transmit the wireless configuration data via one or more wireless communication protocols. The one or more hardware processors may transmit the wireless configuration data via WiFi. Transmitting the wireless configuration data to the destination observation hub may cause the destination observation hub to establish wireless communication with one or more sensors associated with the wireless configuration data.

[0191] In block 531, the one or more hardware processors may transmit physiological data to the destination observing hub. The physiological data may include physiological data previously generated by one or more sensors and / or previously received at the source observing hub. The physiological data may include data that is historical physiological data at the time of transmission in block 529. For example, the physiological data may include data generated by one or more sensors and communicated to the source observing hub before receiving a request to establish the physiological observation at the destination observing hub and / or before establishing the physiological observation at the destination observing hub. Transmitting the physiological data to the destination observing hub may cause the destination observing hub to render a user interface including display indicators corresponding to the physiological data. The one or more hardware processors may transmit the physiological data as a single transmission and / or at a time. The one or more hardware processors may transmit the physiological data as packets of data. The one or more hardware processors may transmit physiological data corresponding to a time period during which the physiological data was generated by one or more sensors, and may transmit the physiological data corresponding to the time period as a single transmission, as a data packet, and / or substantially simultaneously.

[0192] In some implementations, the one or more hardware processors can transmit data related to the physiological data. The data related to the physiological data can include user interface data for rendering a user interface comprising a display indicator of the physiological data. The data related to the physiological data can include signals corresponding to alerts or alarms generated in response to the physiological data. The data related to the physiological data can include conditions related to the subject corresponding to the physiological data. By way of example, the one or more hardware processors can transmit signals related to alerts, alarms, conditions, etc. that may have been generated at the source observing hub based on the physiological data to the destination observing hub. Thus, the destination observing hub can continue with the same alerts, alarms, conditions, etc. that occurred at the source observing hub, thereby maintaining continuity of physiological observation.

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

[0194] FIG. 5C is a flowchart illustrating an example process 500C related to migrating physiological observations from a source observation hub to a destination observation hub. One or more hardware processors can 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 observation hub, a destination observation hub, or a server. 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 multiple computing devices, such as computing devices that are remote from each other and / or in wireless communication with each other. In some implementations, one or more hardware processors associated with a destination observation 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 implementations, the one or more hardware processors performing process 500C may omit portions of process 500C, add additional operations, and / or rearrange the order in which the operations of process 500C are performed.

[0195] At block 543, one or more hardware processors may receive a request to establish physiological observations at a destination observation hub. The request to establish physiological observations at a destination observation hub may be included as part of a request to migrate physiological observations from a source observation hub to a destination observation hub. The request to establish physiological observations may indicate one or more sensors with which the destination observation hub should establish wireless communication. The one or more hardware processors may receive the request via one or more observation hubs, such as those shown and / or described with respect to FIG. 4 and / or FIG. 5A . In some implementations, the one or more hardware processors may additionally verify the authority of the requesting user, such as based at least on identification data.

[0196] At block 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 observation hub via an intermediate device. For example, the one or more hardware processors may receive the wireless configuration data from a server after the server receives the wireless configuration data from the source observation hub. The one or more hardware processors may access the wireless configuration data from memory. For example, the one or more hardware processors may access the wireless configuration data from memory stored in the destination observation hub. The wireless configuration data stored in memory may have been previously received from a remote computing device. In some implementations, the one or more hardware processors may receive the wireless configuration data from the source observation hub via wired or wireless communication. In some implementations, the one or more hardware processors may not receive the wireless configuration data directly from the source observation hub. In some implementations, the one or more hardware processors may receive the wireless configuration data from one or more sensors. In some implementations, one or more hardware processors may generate at least a portion of the wireless configuration data. For example, the one or more hardware processors may generate and / or receive at least a portion of the wireless configuration data from one or more sensors during a pairing process with the one or more sensors. In some implementations, the one or more hardware processors may not generate and / or receive the wireless configuration data during the pairing process.

[0197] At block 547, the one or more hardware processors may establish wireless communication between the destination observation hub and 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 comprise establishing a Bluetooth connection (e.g., following 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 communicating at least a portion of the wireless configuration data to the one or more sensors. The one or more hardware processors may establish wireless communication without initiating a pairing process and / or an interrogation process. In some implementations, the destination observation hub may be considered connected to the one or more sensors, such as by having access to wireless configuration data. In some implementations, the destination observation hub may not have previously established wireless communication with the one or more sensors. Establishing communication may include establishing communication between the destination observing hub and all of the sensors that were previously in communication with the source observing hub. Establishing communication may include establishing communication between the destination observing hub and fewer than all of the sensors that were previously in communication with the source observing hub.

[0198] Advantageously, accessing the wireless configuration data in block 545, such as receiving the wireless configuration data from a remote computing device such as a server, may facilitate establishing wireless communications, such as by eliminating the need to perform a pairing process (which may include an interrogation process), which may take up to 10 seconds to complete and involve significant data processing and communication between remote devices. Accordingly, accessing the wireless configuration data in block 545 may lower the processing requirements for establishing wireless communications in block 547, which may improve efficiency, reduce the time needed to establish wireless communications, and reduce the processing power needed to establish the wireless configuration data in block 545, which may improve energy conservation and extend battery life. Furthermore, reducing the time needed to establish wireless communications may reduce data loss. For example, data collected by a physiological sensor may be lost while waiting to establish wireless communications between the sensor and the monitoring hub (e.g., during the 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 while transitioning physiological monitoring between monitoring hubs. For example, the observation hub may continuously observe the subject, with gaps in data occurring between transitions of 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. Moreover, eliminating the need to perform a pairing process (e.g., by accessing wireless configuration data in block 545) may eliminate the need to place the sensor in discovery mode or avoid the inability to establish wireless communication if the sensor is not in discovery mode. Advantageously, a user may be able to establish communication between the sensor and destination hub without having to turn the sensor, destination hub, and / or source hub off and / or on.Advantageously, a user may be able to establish communication between the sensor and the destination hub without having to change the connection state or mode of the sensor, destination hub, and / or source hub.

[0199] The one or more hardware processors may automatically establish wireless communication in block 547, for example, without requiring user input. For example, the one or more hardware processors may establish wireless communication based on proximity of one or more sensors with the destination observation hub. The one or more hardware processors may establish wireless communication in block 547 in response to user input. For example, a user may provide input to confirm that the one or more hardware processors should establish wireless communication. In some implementations, a user may provide contactless user input to initiate establishment of wireless communication. Contactless user input may comprise near field communication (NFC) and / or radio frequency identification (RFID). Contactless user input may comprise facial recognition, eye recognition, fingerprint recognition, gesture recognition, voice recognition, etc. Contactless user input may comprise minimal-contact user input, such as an input that may not require contact but may still result in contact that may be minimal, may be small, may be unintended, or may be insignificant. Reducing physical contact may be more hygienic, improve the speed and efficiency of transitioning physiological observations, and reduce the complexity of transitioning physiological observations by reducing the number of steps required to transition physiological observations, etc. In some implementations, one or more hardware processors may establish wireless communication in block 547 based on the proximity of the destination observation hub to the one or more sensors in combination with user input.

[0200] One or more hardware processors can establish wireless communication between the destination observation hub and the multiple sensors in block 547. The one or more hardware processors can establish wireless communication with multiple sensors at a time. The one or more hardware processors can establish wireless communication with multiple sensors in response to a single user input. The one or more hardware processors can establish wireless communication with multiple sensors in response to a single request to transfer physiological observations.

[0201] In block 549, the one or more hardware processors may receive real-time physiological data from the one or more sensors. The one or more hardware processors may receive the real-time physiological data via the wireless communication established in block 547. The real-time physiological data may include data generated by the one or more sensors and transmitted to the one or more hardware processors in real time. For example, the one or more hardware processors may receive the physiological data substantially simultaneously as the one or more sensors generate the physiological data. As another example, the one or more hardware processors may receive the physiological data with a minimal time delay after the one or more sensors generate the physiological data, which may be imperceptible to a human. The one or more hardware processors may continuously receive the real-time physiological data. For example, the real-time physiological data may include a continuous stream of data. The one or more hardware processors may periodically receive the real-time physiological data. For example, the real-time physiological data may include data periodically generated by the one or more sensors.

[0202] In block 551, one or more hardware processors may receive historical physiological data from a remote computing device, such as 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, such as 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 establishing wireless communication between the destination observation hub and the one or more sensors in block 547. The historical physiological data may include data communicated from one or more sensors to the source observation hub, such as before establishing wireless communication between the destination observation hub and the one or more sensors in block 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 packet of data. The one or more hardware processors may receive the historical physiological data at a single instant in time. The one or more hardware processors may receive the historical physiological data over a time frame that is shorter than the corresponding time frame that the historical physiological data was generated by the one or more sensors. By way of example, the one or more hardware processors may receive a packet of data comprising the historical physiological data as a single transmission and / or at a single instant in time.

[0203] In some implementations, one or more hardware processors can receive data related to the physiological data. The data related to the physiological data can include user interface data for rendering a user interface comprising a display indicator of the physiological data. The data related to the physiological data can include signals corresponding to alerts or alarms generated in response to the physiological data. The data related to the physiological data can include a condition related to the subject corresponding to the physiological data. By way of example, the one or more hardware processors can receive signals related to alerts, alarms, conditions, etc. that may have been generated at the source observing hub based on the physiological data. Thus, the destination observing hub can continue with the same alerts, alarms, conditions, etc. that occurred at the source observing hub, thereby preserving continuity of physiological observation. Moreover, because the destination observing hub may not have to reprocess past physiological data at least to determine whether to initiate an alert or alarm or to determine a condition, it may be able to initiate an alert or alarm or indicate a condition more quickly, which may reduce processing time and energy requirements and improve computational efficiency and medical observation of the physiology. In one illustrative example, the source observing hub may have generated an alert corresponding to an urgent patient condition based at least on analyzing the physiological data received from the sensor. Pursuant to migrating the physiological observations to the destination observing hub, the destination observing hub may receive a signal corresponding to the alert, such as from a server. The destination observing hub may immediately initiate the alert without having to process the (historical) physiological data received from the source observing hub, such as via a server. Thus, the patient's physiological observations may continue with reduced gaps or discontinuities.

[0204] In some implementations, the one or more hardware processors may analyze the historical physiological data received in block 551 to determine one or more physiological states or trends in the physiological data. The one or more hardware processors may analyze the historical physiological data received in block 551 to generate one or more warnings, alerts, etc. corresponding to the physiological data. Advantageously, because the one or more hardware processors have access to historical physiological data, such as that received in block 551, the one or more hardware processors may be able to more accurately analyze the physiological data by having access to more physiological data, including at least historical and real-time physiological data.

[0205] In block 553, one or more hardware processors can generate user interface data to render a display including an indication of the physiological data, which may include real-time physiological data and / or historical physiological data. The one or more hardware processors can render the display via a destination observation hub. The one or more hardware processors can transmit the user interface data to a remote computing device, such as a smartwatch, smartphone, tablet, PC, wearable device, observation device, etc., that can render the display. Advantageously, the one or more hardware processors can access both 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 the one or more sensors), which may improve physiological observation by reducing data loss, providing a more comprehensive view of the subject's physiological data, etc. The one or more hardware processors can generate user interface data to render a display that combines the real-time physiological data with historical physiological data while minimizing or eliminating interruptions or discontinuities appearing in the display of the physiological data. The one or more hardware processors can generate user interface data to render the display as if the physiological data had been received from the sensor at a time prior to establishing wireless communication in block 547.

[0206] In some implementations, at block 553, one or more hardware processors may not generate user interface data corresponding to the past physiological data. For example, at block 551, one or more hardware processors may receive user interface data corresponding to the past physiological data. The user interface data received at block 551 may have been generated by a source observing hub, which may be of a similar or the same type as the destination observing hub. Thus, the user interface data generated by the source observing hub and received at the destination observing hub may be compatible with the destination observing hub, so the destination observing hub may not need to regenerate user interface data for rendering a display corresponding to the past physiological data. Advantageously, eliminating the need to generate redundant user interface data may lower processing requirements, improve processing speed and efficiency, and reduce the time required to render a display including an indication of the physiological data, which may improve physiological observation and the medical care provided to the subject. In some implementations, the source observing hub and the destination observing hub may be of different types and / or may have dissimilar displays, so the user interface data generated at the source observing hub may not be compatible with the destination observing hub. In such implementations, the destination observation hub may generate user interface data corresponding to the historical physiology data, as described in block 553 .

[0207] FIG. 5D is a flowchart illustrating an example process 500D related to migrating physiological observations from a source observation hub to a destination observation hub. One or more hardware processors can 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 observation hub, a destination observation hub, or a server. 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 multiple computing devices, such as computing devices that are remote from each other and / or in wireless communication with each other. In some implementations, one or more hardware processors associated with a source observation 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 implementations, one or more hardware processors performing process 500D may omit portions of process 500D, add additional operations, and / or rearrange the order in which the operations of process 500D are performed.

[0208] In block 561, one or more hardware processors may establish wireless communication between an observation hub, such as a source observation hub, and one or more sensors. The wireless communication may include one or more wireless communication protocols, including Bluetooth.

[0209] At block 563, the one or more hardware processors may transmit wireless configuration data associated with the one or more sensors to the remote computing device. The one or more hardware processors may transmit the 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 at block 561. The wireless configuration data may include device addresses associated with the one or more sensors. The wireless configuration data may include link keys associated with the one or more sensors. The one or more hardware processors may transmit the wireless configuration data via one or more wireless communication protocols, such as WiFi. In some implementations, the one or more hardware processors may communicate the wireless configuration data to the one or more sensors. For example, the one or more hardware processors may wirelessly transmit wireless configuration data associated with a destination observation hub to the one or more sensors. In some implementations, the one or more hardware processors may transmit the wireless configuration data in response to a request to migrate physiological observations. In some implementations, the one or more hardware processors may transmit the wireless configuration data automatically, such as upon generating and / or receiving wireless configuration data from the one or more sensors.

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

[0211] At block 567, the one or more hardware processors may transmit the physiological data to a remote computing device. The one or more hardware processors may transmit the physiological data to a server, such as server 106 shown and / or described herein. The one or more hardware processors may transmit the physiological data via one or more wireless communication protocols, such as WiFi. In some implementations, the one or more hardware processors may transmit the physiological data in response to an event, such as a request to transition a physiological observation. In some implementations, the one or more hardware processors may transmit the physiological data automatically, such as upon receiving physiological data from one or more sensors. The one or more hardware processors may transmit the physiological data continuously. The one or more hardware processors may transmit the physiological data periodically. The one or more hardware processors may transmit the physiological data from one or more sensors for a time frame as a single transmission.

[0212] In some implementations, the one or more hardware processors can transmit data associated with the physiological data. The data associated with the physiological data may include user interface data for rendering user interface data comprising a display indicator of the physiological data. The data associated with the physiological data may include a signal corresponding to an alert or alarm generated in response to the physiological data. The data associated with the physiological data may include a condition associated with the subject corresponding to the physiological data.

[0213] FIG. 5E is a flowchart illustrating an example process 500E related to observing a subject's position. One or more hardware processors can 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 observing hub, a destination observing hub, a server, etc. 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 multiple computing devices, such as computing devices that are remote from each other and / or in wireless communication with each other. In some implementations, one or more hardware processors associated with an observing 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 implementations, one or more hardware processors performing process 500E may omit portions of process 500E, add additional operations, and / or rearrange the order in which the operations of process 500E are performed.

[0214] Process 500E can facilitate monitoring the location of a subject. One or more sensors may be coupled to the subject. For example, the subject may wear one or more sensors included as one or more wearable devices. Thus, the location of the one or more sensors may indicate the location of the subject. Devices and systems can monitor the location of a subject by determining the location of the one or more sensors. An environment, such as a hospital, may include one or more observation hubs distributed at various locations throughout the environment. While a subject moves around the environment wearing one or more sensors, one or more observation hubs in the environment can detect the presence of the sensors using one or more wireless communication protocols, such as Bluetooth. The observation hubs may determine the proximity of the one or more sensors to the observation hubs based on, for example, the signal strength of the wireless signal. In some implementations, an observation hub in the environment may establish wireless communication with one or more sensors worn by the subject. The observation hubs may establish wireless communication based on the proximity of the one or more sensors to the observation hubs. For example, an observation hub closest to the one or more sensors may establish wireless communication with the one or more sensors rather than an observation hub farther from the one or more sensors. Thus, while a subject wearing one or more sensors moves about an environment, one or more observation hubs in the environment may automatically terminate and establish wireless communication with the one or more sensors based on their proximity to the one or more sensors. Thus, systems and devices may observe the subject's location based at least on the proximity of one or more sensors worn by the subject to the observation hub and / or whether the one or more sensors are in wireless communication with the observation hub.

[0215] At block 570, 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 memory. For example, the one or more hardware processors may access the wireless configuration data from memory stored in an observation hub. The wireless configuration data stored in memory may have been previously received from a remote computing device. In some implementations, the one or more hardware processors may receive the wireless configuration data from another observation hub via wired or wireless communication. In some implementations, the one or more hardware processors may receive the wireless configuration data from one or more sensors. In some implementations, the one or more hardware processors may generate at least a portion of the wireless configuration data. For example, the one or more hardware processors may generate and / or receive at least a portion of the wireless configuration data from one or more sensors during a pairing process with the one or more sensors. In some implementations, the one or more hardware processors may not generate and / or receive the wireless configuration data during the pairing process.

[0216] At block 571, one or more hardware processors may transmit a signal to initiate wireless communication between the observation hub and the 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 block 570. For example, the signal may comprise a device address code that may be based on a device address in 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 implementations, the signal may correspond to a pairing process of the Bluetooth protocol. For example, the signal may comprise an inquiry access code that corresponds to an inquiry process. In some implementations, the signal may not correspond to a pairing process.

[0217] 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 implementations, the response signal may correspond to a pairing process of the Bluetooth protocol, such as an inquiry process. In some implementations, the response signal may not correspond to a pairing process.

[0218] Advantageously, the one or more hardware processors may discover the presence of one or more sensors in proximity to the one or more sensors based at least on transmitting and receiving signals in accordance with blocks 571 and 573.

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

[0220] At decision block 575, the one or more hardware processors may determine whether one or more sensors are within a threshold proximity from the observation hub. The one or more hardware processors may determine the proximity of the one or more sensors to the observation hub based at least on signal strengths associated with the one or more sensors, such as the signal strength of the response signals received in block 573. A stronger signal strength may correspond to closer proximity. A weaker signal strength may correspond to 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.

[0221] In 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 comprise 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 based at least on transmitting a signal in block 571 and receiving a response signal in block 573.

[0222] In block 579, the one or more hardware processors may determine a location of the subject based at least on determining the location of the observation hub. The one or more hardware processors may access location data associated with the observation hub. The one or more hardware processors may access the location data by retrieving the location data from memory. The one or more hardware processors may access the location data by receiving the location data from one or more sensors, such as a sensor configured to generate location data, such as a GPS. In some implementations, the location data may be set by a user and stored in memory associated with the observation hub. The location data may indicate a location of the observation hub. The location data may indicate a location of the observation hub relative to the environment. As an example, the location data may indicate that the observation hub is located in a particular area of a building, such as a hospital, such as a particular floor or room. The location data may also indicate the location of one or more sensors (and the subject wearing the sensors), since the one or more sensors may be in proximity to the observation hub as determined in block 575.

[0223] In some implementations, one or more hardware processors executing on the observation hub may determine the subject's location. For example, the one or more hardware processors may access the observation hub's location data and / or determine the subject's location and transmit the location to a remote computing device. The one or more hardware processors may transmit the location data to a server, such as server 106 shown and / or described herein. The one or more hardware processors may transmit the location data via one or more wireless communication protocols, such as WiFi.

[0224] In some implementations, one or more hardware processors executing on a computing device remote from the observation hub, such as a server, may determine the subject's location. For example, the one or more hardware processors may receive an indication that one or more sensors are in proximity to the observation hub and / or may receive an indication that the observation hub has established wireless communication with the one or more sensors. In response, the one or more hardware processors may retrieve the observation hub's location data from memory and / or determine the subject's location based at least on determining the observation hub's location, such as by receiving the observation hub's location data from the observation hub and / or from one or more sensors configured to generate the location data.

[0225] Advantageously, in some implementations, the one or more hardware processors cannot determine a location unless they have established wireless communication (Bluetooth connection) between the observation hub and one or more sensors. Determining a location in response to establishing wireless communication may improve the observation of a location by ensuring that valid location data is used. For example, one or more sensors may establish wireless communication with a nearest observation hub of multiple observation hubs in the environment. Thus, the location of the observation hub (which may also be closest to the one or more sensors) that has established wireless communication with the one or more sensors may be used to determine the location of the one or more sensors and the subject. Thus, determining a location in response to establishing wireless communication may improve the accuracy of observing the subject's location.

[0226] Disclosed herein are various methods relating to transferring wireless connectivity and / or physiological data (e.g., previously collected data) from a first observation hub to a second observation hub (and possibly additionally to a third observation hub). Any of such disclosed methods and / or features described with respect to any of the observation hubs described herein may be applicable to other types of observation devices, such as an observation device configured to be secured to a user and receive physiological data from one or more physiological sensors that acquire physiological data for the user. For example, any of the disclosed methods may be utilized to transfer wireless connectivity and / or physiological data (e.g., previously collected data) from a first observation device secured to a portion of the user's body and configured to receive physiological data from the physiological sensors to a second, similar observation device. Such an observation device may be worn by the user (e.g., on the wrist, arm, or another portion of the user's body), configured to receive physiological data wirelessly (and / or via a wired connection) from the physiological sensors, and may further be configured to communicate wirelessly (and / or via a wired connection) with other devices.

[0227] Exemplary Observation Hub 6 illustrates an exemplary observation hub 600. Observation hub 600 may include similar structural and / or operational features as any of the other observation hubs discussed herein. In some implementations, observation hub 600 may operate in a manner similar to any of the source observation hubs disclosed herein. In some implementations, observation hub 600 may operate in a manner similar to any of the destination observation hubs disclosed herein.

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

[0229] FIG. 6 shows an observation hub 600 housed within a holder 602. The observation hub 600 may be removably housed within the holder 602. For example, the observation hub 600 may be removably mechanically mated (e.g., via a friction fit) with the holder 602. Advantageously, the holder 602 may improve the portability and / or mobility of the observation hub 600. For example, a user may more easily carry and transport the observation hub 600 when housed within the holder 602. The holder 602 may also help protect the observation hub 600 or portions thereof. As another example, as shown in FIG. 6 , the holder 602 may secure the observation hub 600 to a bed 604 to facilitate moving the observation hub 600 and the bed 604 together. For example, a user may be able to move the bed 604 and the observation hub 600 together by pushing the bed 604 without having to hold the observation hub 600 at the same time. Advantageously, the portability of the observation hub facilitates continuous physiological monitoring and / or subject mobility. For example, the observation hub 600 may continuously monitor the physiological data of a subject lying in bed 604 while the subject is transported to a new location, such as a different room in a hospital. The observation hub 600 may maintain wireless communication with the subject's sensors and a server on the bed 604 via a network when the observation hub 600 and bed 604 are moved, without the need to unplug and / or replug any connections to the observation hub 600. Each of the observation hubs 600, 700, and / or 1100, described further below, may include similar or identical operational and / or structural features. The holder 602 may include similar or identical operational and / or structural features to the holder 800, discussed further below.

[0230] 7A-7K show various views of observation hub 700. Observation hub 700 may be similar or identical in some or many respects to any of the observation hubs discussed elsewhere herein. For example, observation hub 700 may include any of the features described with respect to any of the other observation hubs described herein, and / or observation hub 700 may be configured to operate in any manner as described with respect to any of the other observation hubs described elsewhere herein. Furthermore, observation hub 700 may be an implementation of any of the observation hubs described herein.

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

[0232] In some implementations, the observation hub 700 is configured to receive power from an external power source via a power cable that can be connected to a connector port of the observation hub 700, such as, for example, connector port 705 shown in at least FIGS. 7D-7E . In some implementations, the observation hub 700 includes an internal power source (e.g., a battery) that is stored in a portion of the observation hub 700 (e.g., the housing of the observation hub 700). In some implementations, the observation hub 700 includes an internal power source and also includes a connector port (e.g., connector port 705). Such implementations can advantageously allow the observation hub 700 to draw power necessary for operation from the internal power source even when not connected to an external power source (e.g., via a cable connected to connector port 705), allow the observation hub 700 to draw power from an external power source (e.g., only from an external power source) when connected via a cable, and / or allow the internal power source of the observation hub 700 to be charged by an external power source. In some implementations in which the observation hub 700 includes an internal power supply, the observation hub 700 may be configured to allow such internal power supply to be charged via inductive charging. The observation hub 700 may be configured to operate on AC power and / or DC power. In some implementations, the observation hub 700 includes an AC power connector port and a DC power connector port separate from the AC power connector port. In some implementations in which the observation hub 700 includes an internal power supply, such internal power supply may have an operating time of 2 hours, 3 hours, 4 hours, or more. In some implementations, the observation hub 700 includes one or more speakers for issuing sounds, such as alerts, communications from a caregiver (e.g., inquiries about the user / patient's status, or otherwise communicating with the user / patient), among others. The observation hub 700 may include a USB port (e.g., USB port 709 as shown in FIGS. 7D-7E) configured to connect to a USB cable and / or an Ethernet port configured to connect to an Ethernet cable (e.g., Ethernet port 707 as shown in FIGS. 7D-7E).

[0233] As shown, for example, in FIG. 7F , the viewing hub 700 may have a height (measured perpendicular to the page) of approximately 10 inches. In some implementations, the viewing hub 700 may have a height greater than 10 inches, such as 12 inches, 14 inches, or more. In some implementations, the viewing hub 700 may have a height less than 10 inches, such as less than 9 inches, less than 8 inches, or less than 6 inches. The viewing hub 700 may have a width of approximately 8 inches (measured horizontally to the page). In some implementations, the viewing hub 700 may have a width greater than 8 inches, such as 9 inches, 10 inches, or more. In some implementations, the viewing hub 700 may 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 may have a height of approximately 9 inches. In some implementations, the display 701 may have a height greater than 9 inches, such as 10 inches, 11 inches, or more. In some implementations, display 701 may have a height of less than 9 inches, such as less than 8 inches, less than 7 inches, or less than 6 inches. Display 701 may have a width of approximately 6 inches. In some implementations, display 701 may have a width of more than 6 inches, such as 7 inches, 8 inches, or more. In some implementations, display 701 may have a width of less than 6 inches, such as less than 5 inches, less than 4 inches, or less than 3 inches.

[0234] 11A-11C show front, back, and side views (respectively) of another implementation of an observation hub 1100. The observation hub 1100 can be any implementation of the other observation hubs discussed elsewhere herein. In some implementations, the observation hub 1100 is configured to be received and / or supported by a holder 800. As shown in FIG. 11B, the observation hub 1100 can include an opening 1101 that can receive a portion (e.g., a top) of a fastener to allow the hub 1100 to be mounted to a surface or object (e.g., a wall). While FIGS. 11A-11C show a cable connected to the observation hub 1100, the observation hub 1100 can be configured to receive power from an internal power source that can be charged (e.g., via inductive charging) without the need to connect to a cable. Moreover, the observation hub 1100 can be configured to receive data via wireless transmission without the need to connect to a cable.

[0235] 12A-12M show various views of observation hub 1200. Observation hub 1200 may be similar or identical in some or many respects to any of the observation hubs discussed elsewhere herein. For example, observation hub 1200 may include any of the features described with respect to any of the other observation hubs described herein, and / or observation hub 1200 may be configured to operate in any manner as described elsewhere herein with respect to any of the other observation hubs described herein. Furthermore, observation hub 1200 may be an implementation of any of the observation hubs described herein.

[0236] The observation hub 1200 may include a display 1201, for example, on a front portion of the observation hub 1200 (see FIG. 12A ). The display 1201 may include any of the features and / or functionality of any of the other displays shown or described elsewhere herein. In some implementations, the observation hub 1200 includes a status indicator 1203, which may include similar structural and / or operational features as any or all of the status indicators described elsewhere herein.

[0237] In some implementations, the observation hub 1200 can receive power from an external power source via a power cable that can be connected to a connector port of the observation hub 1200, such as, for example, connector port 1205 shown in at least Figures 12E, 12F, and 12J. The observation hub 1200 can be configured to operate on AC power and / or DC power. In some implementations, the observation hub 1200 includes an AC power connector port and a DC power connector port that is separate from the AC power connector port.

[0238] The observation hub 1200 may include a USB port (such as USB port 1209 as shown in at least FIGS. 12E, 12F, and 12J) configured to connect to a USB cable, and / or may include an Ethernet port (such as Ethernet port 1207 as shown in at least FIGS. 12E, 12F, and 12J) configured to connect to an Ethernet cable.

[0239] The observation hub 1200 may include an auxiliary port 1206 .

[0240] In some implementations, the observation hub 1200 includes one or more speakers for emitting sounds, such as, among other things, alerts, communications from caregivers (e.g., inquiries about the user / patient's status, or otherwise communicating with the user / patient).

[0241] The observation hub 1200 may include one or more sensor ports 1211. The observation hub may include more than three sensor ports 1211. The observation hub may include six sensor ports 1211. The observation hub 1200 may include one, two, three, four, five, six, seven, eight, nine, or more than nine sensor ports 1211. The sensor ports 1211 may be configured to connect to one or more sensors via a wired connection. The observation hub 1200 can receive physiological data from one or more sensors via the sensor ports 1211. The sensor ports 1211 can receive ECG data, heart rate data, blood oxygen data, blood pressure data, EEG data, temperature data, respiration data, etc. Each sensor port 1211 may receive a different type of physiological data than the other sensor ports 1211. For example, a first sensor port 1211 may receive ECG data, while another sensor port 1211 may receive SpO2 data. Sensor ports may simultaneously receive multiple different types of physiological data. 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 with a blood pressure sensor, and the same sensor port 1211 may receive ECG data via a wired connection with an ECG sensor after unplugging and plugging in each sensor in the sensor port 1211.

[0242] For example, as shown in at least FIGS. 12G-12L, observation hub 1200 may include status indicator 1203. Status indicator 1203 may comprise one or more LEDs. Status indicator 1203 may emit light of one or more colors. Observation hub 1200 may include curved portion 1213. Status indicator 1203 may be disposed on curved portion 1213. Curved portion 1213 may protrude from a portion of the housing of observation hub 1200. Curved portion 1213 may not be flush with display 1201. Status indicator 1203 may be disposed on curved portion 1213 so as to be on a different plane from display 1201. Status indicator 1203 may be disposed on an edge of curved portion 1213. Curved portion 1213 may comprise an edge of observation hub 1200. Status indicator 1203 may be disposed on an edge of observation hub 1200. The status indicators 1203 may be viewable from multiple angles, which may improve observation of the patient's physiology because a caregiver may be able to view the status indicators 1203 from multiple positions around the observation hub 1200. The status indicators 1203 may be viewable from the front or back of the observation hub 1200 (e.g., as shown in FIGS. 12G-12H). The status indicators 1203 may be viewable from the top or bottom of the observation hub 1200 (e.g., as shown in FIGS. 121-12J). The status indicators 1203 may be viewable from the left or right side of the observation hub 1200 (e.g., as shown in FIGS. 12K-12L).

[0243] 12M, for example, the observation hub 1200 may include an internal power source (e.g., a battery) housed in a portion of the observation hub 1200 (e.g., the housing of the observation hub 1200). The observation hub 1200 may include a battery housing 1217 that encloses a battery within the observation hub 1200. In some implementations, the observation hub 1200 includes an internal power source and also includes a connector port (such as connector port 1205). Such implementations can advantageously allow the observation hub 1200 to draw power necessary for operation from the internal power source despite not being connected to an external power source (e.g., via a cable connected to connector port 1205), allow the observation hub 1200 to draw power from an external power source (e.g., only from an external power source) when connected via a cable, and / or allow the internal power source of the observation hub 1200 to be charged by an external power source. In some implementations in which the observation hub 1200 includes an internal power source, the observation hub 1200 may be configured to allow such internal power source to be charged via inductive charging. In some implementations in which the observation hub 1200 includes an internal power supply, such internal power supply may have a run time of 2 hours, 3 hours, 4 hours or more.

[0244] For example, as shown in at least FIG. 12M , the observation hub 1200 may include a heat sink 1215. The heat sink 1215 may be formed of a metal and / or alloy. The heat sink 1215 may dissipate heat from an interior region of the observation hub 1200 to an exterior region of the observation hub 1200. The heat sink 1215 may be disposed adjacent to the internal power source. The heat sink 1215 may be disposed adjacent to the battery housing 1217. A portion of the heat sink 1215 may be exposed to the exterior region of the observation hub 1200. A portion of the heat sink 1215 may be unexposed and / or disposed in the interior region of the observation hub 1200. The heat sink 1200 may dissipate thermal energy from the battery in the battery housing 1217 to an exterior region of the observation hub 1200. Advantageously, the heat sink 1215 may provide passive cooling for the observation hub 1200. Advantageously, the heat sink 1215 may alleviate the need to implement an active cooling system, such as a fan, which can be noisy and further consume energy. In some implementations, the heat sink 1215 may contact the battery housing 1217. The heat sink 1215 may be removably coupled to the observation hub 1200. In some implementations, the heat sink 1215 may only surround or cover the battery housing 1217 within the interior region of the observation hub 1200. In some implementations, the heat sink 1215 may form a portion of the housing of the observation hub 1200. In some implementations, the heat sink 1215 may cover or surround the interior region of the observation hub 1200.

[0245] The heat sink 1215 may include one or more through-holes 1219. The heat sink 1215 may include fewer than five through-holes 1219, fewer than four through-holes 1219, fewer than three through-holes 1219, or fewer than two through-holes 1219. The heat sink 1215 may include four through-holes 1219. The through-holes 1219 may accept one or more screws, nails, fasteners, or the like. The heat sink 1215 may be secured to the observation hub 1200 by the through-holes 1219. In some implementations, a user may remove the heat sink 1215 from the observation hub 1200 by simply unscrewing the screws from the through-holes 1219. In some implementations, a user may couple the heat sink 1215 to the observation hub 1200 by simply screwing the screws into the through-holes 1219. Advantageously, a user may easily remove and replace the heat sink 1215 from the observation hub 1200. Advantageously, a user can easily access the battery housing 1217 by simply removing the heat sink 1215. A user may wish to periodically replace the internal power supply enclosed by the battery housing 1217. As described herein, a user can easily replace the internal power supply by simply removing and replacing the heat sink 1215.

[0246] For example, as shown in at least FIG. 12G , the viewing hub 1200 may include a glass portion 1221. The glass portion 1221 may be disposed 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. The metal may affect the operation of wireless components. For example, the metal may cause an antenna to detune. Thus, placing a component configured for wireless communication near metal may adversely affect the operation of the wireless communication component. In some implementations, the viewing hub 1200 may include components configured for wireless communication, such as an antenna, transceiver, radio, pairing device, etc., which may be disposed in an interior region of the viewing hub 1200 adjacent to the glass portion 1221. Thus, wireless transmissions from one or more wireless communication components may occur through the glass portion 1221, which may improve the quality of the wireless transmissions. Furthermore, placing the wireless communication component adjacent to the glass portion 1221 may increase the distance between the wireless communication component and metal, such as the metal of the curved portion 1213 and / or the metal of other portions of the frame or housing of the viewing hub 1200.

[0247] For example, as shown in FIG. 12G , the viewing hub 1200 may have a height of approximately 21 inches (measured perpendicular to the page). In some implementations, the viewing hub 1200 may have a height greater than 21 inches, such as 23 inches, 26 inches, or more. In some implementations, the viewing hub 1200 may have a height less than 21 inches, such as less than 18 inches, less than 15 inches, or less than 12 inches. The viewing hub 1200 may have a width of approximately 15 inches (measured horizontally to the page). In some implementations, the viewing hub 1200 may have a width greater than 15 inches, such as 17 inches, 19 inches, or more. In some implementations, the viewing hub 1200 may 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 may have a height of approximately 19 inches. In some implementations, the display 1201 may have a height of more than 19 inches, such as 20 inches, 21 inches, or more. In some implementations, the display 1201 may 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 may have a width of approximately 11 inches. In some implementations, the display 1201 may have a width of more than 11 inches, such as 12 inches, 13 inches, or more. In some implementations, the display 1201 may have a width of less than 11 inches, such as less than 10 inches, less than 9 inches, or less than 8 inches.

[0248] holder 8A-8B show the observation hub 700A attached to a holder 800. The holder 800 can advantageously receive and surround a portion of the observation hub 700 and can serve to protect the observation hub 700. The holder 800 can also advantageously allow the observation hub 700 to be more easily carried (e.g., by a caregiver in a medical environment) and / or placed on a surface (e.g., a table, bed, chair, desk) so that the display of the observation hub 700 is viewable. Additionally, in some implementations, the holder 800 can be configured to be secured to a portion of a hospital bed (and / or other object), as discussed further below.

[0249] 8C shows the viewing hub 700 and holder 800 separated from one another. The holder 800 may be sized to receive any of the exemplary viewing hubs shown and / or described herein.

[0250] 8D-8O, holder 800 may include a base 802. Base 802 may be configured to receive and removably secure viewing hub 700, for example, in a manner such that a display of hub 700 is visible when hub 700 is received and secured by base 802 (see, for example, FIG. 8A ). Holder 800 may include one or more arms 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 hospital bed or chair, such as a post, handrail, among other objects, and / or to rest on a surface to operably position holder 800 (and viewing hub 700 when disposed in holder 800) such that, for example, a front of holder 800 is positioned away from the surface (which may allow a display of hub 700 to be visible when secured in holder 800). 8D-8O , the holder 800 may include an arm 804 (sometimes referred to as a “stand”) extending outward from a base 802. The arm 804 may extend crosswise (non-parallel) to the base 802, which may allow the holder 800 to be placed in a position on a surface (e.g., a table or desk). The arm 804 may be oriented non-parallel to the base 802 such that, when placed on a support surface (a table, desk, etc., among others), the base 802 faces in a direction that is not parallel (and / or not perpendicular) to such support surface. This may advantageously make the hub 700 more reachable and / or the display of the hub 700 more viewable when the holder 800 is placed on the support surface.

[0251] 8D-8O, the holder 800 may include an arm 806. The arm 806 may be configured to be removably secured to a portion of a hospital bed or chair. For example, the arm 806 may be configured to "hook" onto a portion of a hospital bed, as shown with respect to the hub 600, holder 602, and bed 604 in FIG. 6. The arm 806 may include a first portion extending outward from the base 802 and a second portion connected to and intersecting the first portion. In some implementations, the arms 804, 806 are integral with the base 802. The arms 804, 806 may form a single, integrated unit with the base 802. The arms 804, 806 may be fixed relative to the base 802. The arms 804, 806 may be non-adjustable. The arms 804, 806 may be configured not to be adjustable relative to the base 802. Arms 804, 806 may be fixed. In some alternative implementations, one or both of arms 804, 806 may be pivotally connected to base 802, which may allow the orientation of arm 804 and / or arm 806 to be changed relative to base 802 between multiple positions. When arm 806 is pivotally connected to base 802, the tilt of holder 800 relative to the surface supporting arm 806 can be changed, which may adjust the tilt of viewing hub 700 when attached to holder 800 (and, for example, the display of hub 700). Arms 804, 806 may facilitate orienting holder 800 in multiple orientations. For example, holder 800 may be placed on a surface by being placed on arm 804, or by being placed on arm 806, or by being placed on both arms 804 and 806, such as in a horizontal position.

[0252] In some implementations, 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 the loop of holder 800, as seen at least in FIGS. 8F-8I . In some implementations, arm 806 includes 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 the loop of holder 800. In some such implementations, holder 800 includes a rod 807 extending between portions of arm 806 that divides the loop formed by arm 806. A user carrying holder 800 (and hub 700 when received by holder 800) can grasp such rod 807. In some implementations, arm 806 includes a hook that allows arm 806 to at least partially wrap around and / or be placed on an object and / or surface. For example, arm 806 may include a first portion connected to base 802 and a second portion connected to and intersecting (but not parallel to) such first portion. Such a configuration may advantageously allow arm 806 to be secured to a variety of support structures, such as a wall piece at the edge of a hospital bed as shown in FIG. 6, or a post, handrail, or other support structure.

[0253] In some implementations, the holder 800 is configured such that when the arm 806 is wrapped around and / or placed on top of a support structure (e.g., a wall at the edge of a hospital bed as shown in FIG. 6 ), the arm 806 contacts the support structure (e.g., a side of the support structure) and operably positions the base 802 away from the support structure.

[0254] In some implementations, holder 800 is configured so that when arm 806 is wrapped around and / or placed on top of a support structure (e.g., a wall at the edge of a hospital bed as shown in FIG. 6), arm 806 contacts the support structure and operatively positions base 802 such that base 802 is oriented substantially parallel to a plane extending along the support structure (e.g., a plane extending along the side of the support structure). Such a "support structure" may be generally perpendicular to the ground surface (e.g., a hospital room or residential floor). In some implementations, the holder 800 is configured so that when the arm 806 is wrapped around and / or placed on top of a support structure (e.g., a wall at the edge of a hospital bed as shown in FIG. 6), the arm 806 contacts the support structure and operably positions the base 802 so that it is approximately perpendicular to the ground, within 30 degrees of perpendicular to the ground, within 20 degrees of perpendicular to the ground, or within 10 degrees of perpendicular to the ground.

[0255] The holder 800 may be made of a variety of materials, such as hard plastic, among other materials. In some implementations, the holder 800 includes an overmold of softer material disposed over a harder base material of the holder 800. In some implementations, portions of the holder 800 may include a material that aids in gripping (such as silicone and / or rubber), as indicated by the shaded portions appearing in FIGS. 8A-8O (which contrast with other non-shaded portions of the holder 800). In some implementations, the holder 800 includes one or more protrusions 805 extending outward from the surface of the base 802 that can help a user grip the holder 800 (e.g., with the user's fingers), as shown in at least FIGS. 8F-8I and 8K.

[0256] Installation Assembly Any of the observation hubs discussed herein can be mounted in a variety of ways to various objects and / or surfaces. Figures 9A-9M show a mounting assembly 900 (or a portion thereof) that can enable the observation hub 700 (or any of the other observation hubs shown and / or described herein) to be secured to a surface (such as a wall) or another object (such as a support arm that is itself mounted to a surface (such as a wall)). Figures 10A-10K show another implementation of a mounting assembly 1000 (or a portion thereof) that can enable the observation hub 700 (or any of the other observation hubs shown and / or described herein) to be secured to a surface (such as a wall) or another object (such as a support arm that is itself mounted to a surface (such as a wall)). The mounting assemblies 900, 1000 can include a first portion configured to be secured to a portion of the observation hub 700 (e.g., the back of the hub 700) and a second portion configured to be secured to a surface or object (such as a wall). Such a first portion may be secured to the observation hub 700 via one or more fasteners (such as screws, nails, or magnets), and such a second portion may be secured to a surface or object (e.g., a wall) via one or more fasteners (such as screws, nails, or magnets). Advantageously, such first and second portions of the mounting assembly 900 may be secured (e.g., removably secured) to one another without the need for one or more fasteners (such as screws or nails), which may enable rapid attachment and / or removal. Such rapid attachment and / or removal of the first and second portions of the mounting assembly 900 may then advantageously enable rapid attachment and / or removal of the observation hub 700 from an object or surface (e.g., a wall). Such a first portion may be a mount 910 (as for the mounting assembly 900 shown in FIGS. 9A-9M) or a mount 1010 (as for the mounting assembly 1000 shown in FIGS. 10A-10K). Such a second portion may be mount 920 (for mounting assembly 900 shown in FIGS. 9A-9M) or mount 1020 (for mounting assembly 1000 shown in FIGS. 10A-10K).Each of the mounts 910, 920, 1010, 1020 may also be referred to as a “mounting portion.” The mounting assemblies 900 and 1000 are then discussed below.

[0257] 9C-9D show rear and front perspective views (respectively) of mounts 910, 920 separated from one another. 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 outward from the base 912. When the mount 910 includes multiple arms 914 as shown in the figures, such multiple arms 914 may be separated and spaced apart from one another. In some implementations, 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 implementations, as shown in the figures, 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 intersecting such first portion 914a. This can allow the base 912 to be spaced from the plane of the hub 700 by a gap that is sized and / or shaped to allow a finger 924 of the mount 920 to engage a portion of the base 912 and fit between the base 912 and the hub 700 when the mount 910, 920, and hub 700 are attached together such that the second portion 914b is substantially parallel to the base 912 (e.g., a plane defined along the base 912). The mount 910 can include one or more through holes configured to receive fasteners (e.g., screws) to allow the mount 910 to be secured to the hub 700 (e.g., via the threaded hole 711 of the hub 700). Such through holes can be through holes 911 located in the arms 914. As shown in the figure, 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.

[0258] 9C-9D , mount 920 may include a base 922 (which may also be referred to as a “body” or “body portion”). Mount 920 may further include one or more through holes 921 configured to accommodate fasteners (e.g., screws) to enable mount 920 to be secured to a surface (e.g., a wall) and / or another object (such as a support arm mounted to a wall). In some implementations, the portion of base 922 surrounding hole 921 is recessed with respect to a first side of base 922 and / or protrudes from a second, opposing side of base 922. Such a recessed portion can allow the tops of fasteners to be hidden (“countersunk”), while a protruding portion can provide more space with respect to the mounting surface (e.g., a wall), which can provide more space for a user to reach lever 926 of mount 920 (to enable decoupling of mounts 910, 920 from one another).

[0259] The mount 920 may include structure to 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 a portion of the body 912. The fingers 924 may extend from the base 922, e.g., from a nearby opening 923. In some implementations, the fingers 924 may be formed by cutting material from the base 922 to form the opening 923 and the fingers 924. For example, the fingers 924 may include a first portion connected to and intersecting the base 923, and a second portion intersecting such first portion, such that the second portion of the fingers 924 is substantially parallel to the base 922 (e.g., a plane defined along the base 922). Such second portion of the fingers 924 may be spaced from the base 922 by a gap sized to receive a portion of the base 912 of the mount 910.

[0260] Mount 920 may further include a lever 926. Lever 926 may be formed from and / or connected to base 922 (e.g., via cutting a portion of base 922 to form opening 925). A first end (which may be referred to as the “connected end”) of lever 926 may be connected to base 922, and a second end of lever 926 may be “free.” Such a “free” end of lever 926 may be manipulated (e.g., moved) by a user, which may enable removal of mount 910 from mount 920, as described further below. Lever 926 may include a protrusion 928 configured to engage with opening 916 in mount 910 and / or a portion of base 912 near said opening 916. Lever 926 may be movable from a first position in which lever 926 engages a portion of mount 910 and a second position in which such engagement is removed. In some implementations, when the lever 926 is in such a first position, the protrusion 928 of the lever 926 engages with a portion of the base 912 near the opening 916 and / or is disposed at least partially within and / or through the opening 916. When the protrusion 928 is disposed at least partially within and / or through the opening 916 and / or contacts a structure surrounding the opening 916, the opening 916 and / or such surrounding structure can provide a physical interference that impedes (e.g., prevents) the mount 910 from separating 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, removing such physical interference and thereby allowing the mount 910 to be separated from the mount 920. In some implementations, when lever 926 is biased, mount 910 is inserted perpendicularly into mount 920 (e.g., base 912 is inserted between fingers 924) and protrusion 928 contacts the face of base 912 and snaps into engagement with aperture 916. As shown in at least FIGS. 9C-9D , in some implementations, the “free” end of lever 926 (which may also be referred to as the “actuation end”) is bent, e.g., away from the face or plane of the rest of lever 926 and / or base 922.Such implementations may advantageously provide more space for a user to reach lever 926 when mounts 910, 920 are attached to each other and / or to a surface (e.g., a wall). In some implementations, protrusion 928 has a semicircular shape. In some implementations, opening 927 has a semicircular shape. In some implementations, opening 916 has a semicircular shape. In some implementations, a portion of base 912 within opening 916 (e.g., disposed along a straight side of semicircular-shaped opening 916) is raised.

[0261] Continuing with reference to FIGS. 9C-9D , the base 912 of the mount 910 can have a width that tapers at least partially along its height. For example, the width of the base 912 may taper to a smaller width at or near the center of the mount 910 and / or the bottom end of the mount 910 (assuming the orientation of FIGS. 9C-9D ) and be larger at or near the top of the mount 910. As also shown in FIGS. 9C-9D , the fingers 924 of the mount 920 may be angled, for example, relative to the vertical. The fingers 924 can form a pocket that can receive a portion of the mount 910 (e.g., the base 912). In some implementations, the fingers 924 form a tapered pocket configured to receive a portion of the mount 910 (e.g., the base 912). Such a configuration can advantageously allow mount 910 (which may be secured to hub 700) to be secured vertically to mount 912 by moving base 912 down into and / or between fingers 924 so that mounts 910, 920 can be connected as shown in Figures 9K-9M. Note that Figures 9K-9M show mounts 910, 920 connected to one another without showing hub 700 to more clearly show how mounts 910, 920 may be positioned when secured to one another. In one exemplary method, mount 910 is secured to hub 700, for example, via a screw inserted through hole 911 in arm 914 (see FIGS. 9E-9F ) and into threaded hole 711 in hub 700, and mount 920 is secured to a wall or other object via a screw inserted through hole 921, with hub 700 and mount 910 secured to mount 920, for example, by vertically positioning base 912 within fingers 924 of mount 920. In some implementations, a portion of lever 926 can engage with a portion of mount 910 when mounts 910, 920 are connected to one another. For example, protrusion 928 can be disposed within opening 916 in mount 910 and / or can engage with structure surrounding opening 916.Such engagement of the lever 926 with a portion of the mount 910 can hinder (e.g., prevent) the mounts 910, 920 from being decoupled from one another. When decoupling 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 face or plane of the base 922), which can remove the protrusion 928 from the opening 916, thereby allowing the mount 910 to be decoupled from the mount 920. In some implementations, 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 was moved to insert the mount 910 into the mount 920. For example, in some implementations, the mount 910 is connected to the mount 920 by inserting the mount 910 downward into the mount 920, and the mount 910 is decoupled from the mount 920 by moving the mount 910 upward relative to the mount 920.

[0262] 10A-10D show another implementation of a mounting assembly 1000. The mounting assembly 1000 can include mounts 1010 and 1020. FIGS. 10C-10D show rear and front perspective views (respectively) of the mounts 1010, 1020 separated from one another. The mount 1010 can include a base 1012 (which can also be referred to as a "body" or "body portion") and one or more arms 1014 extending from and connecting to the base 1012. In some implementations, the mount 1010 includes two arms, each of which is separated from a portion of the base 1012 by an opening (see FIGS. 10C-10D). In some implementations, as shown in the figures, a portion 1019 of the arm 1014 is curved such that the arm 1014 is spaced from the base 1012 (e.g., the plane along which the arm 1014 extends is spaced from the plane along which the base 1012 extends). Such implementations can allow the base 1012 to be spaced from the face of the hub 700 by a gap that is sized and / or shaped to allow a finger 1024 of the mount 1020 to engage a portion of the base 1012 and fit between the base 1012 and the hub 700 when the mounts 1010, 1020, and hub 700 are attached together.

[0263] The mount 1010 may include one or more through holes configured to accommodate 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). As shown, such a through hole may be a through hole 1011 located in the arm 1014. As shown in the figure, the mount 1010 may include an opening 1016 that can interact with a protrusion 1028 of the mount 1020, as described in more detail below.

[0264] Continuing with reference to FIGS. 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 further include one or more through holes 1021 configured to accommodate fasteners (e.g., screws) to enable the mount 1010 to be secured to a surface (e.g., a wall) and / or another object (such as a support arm mounted to a wall). In some implementations, a portion of the base 1022 surrounding the holes 1021 is recessed with respect to a first surface of the base 1022 and / or protrudes from a second, opposing surface of the base 1022. Such a recessed portion can allow the tops of the fasteners to be hidden (“countersunk”), while a protruding portion can provide more space with respect to the mounting surface (e.g., a wall), which can provide more space for a user to reach the lever 1026 of the mount 1020 (to enable the mounts 1010, 1020 to be detached from one another).

[0265] The mount 1020 may include structure to 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, for example, at an opening 1025. In some implementations, the fingers 1024 may be formed by cutting material from the base 1022 to form the opening 1025 and the fingers 1024. For example, the fingers 1024 may include a first portion connected to and intersecting the base 1022 and a second portion intersecting such first portion, such that the second portion of the fingers 1024 is substantially parallel to the base 1022 (e.g., a plane defined along the base 1022). Such second portion of the finger 1024 may be spaced from the base 1022 by a gap sized to receive a portion of the base 1012 of the mount 1010 .

[0266] The mount 1020 may further include a lever 1026. The lever 1026 may be formed from and / or connected to the base 1022 (e.g., via cutting a portion of the base 1022 to form an opening 1025). A first end (which may be referred to as the “connected end”) of the lever 1026 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 enable removal of the mount 1010 from the mount 1020, as described further 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 near said opening 1016. The lever 1026 may be movable 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 implementations, when the lever 1026 is in such first position, a protrusion 1028 of the lever 1026 engages a portion of the base 1012 near the opening 1016 and / or is disposed at least partially within and / or through the opening 1016. When the protrusion 1028 is disposed at least partially within and / or through the opening 1016 and / or contacts structure surrounding the opening 1016, the opening 1016 and / or such surrounding structure may provide a physical interference that impedes (e.g., prevents) the mount 1010 from separating 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, removing such physical interference and thereby allowing the mount 1010 to be decoupled from the mount 1020. In some implementations, when the lever 1026 is biased, the mount 1010 is inserted vertically into the mount 1020 (e.g., the base 1012 is inserted between the fingers 1024) and the protrusion 1028 contacts the face of the base 1012 and snaps into engagement with the opening 1016.10C-10D , in some implementations, the “free” end of the lever 1026 (which may also be referred to as the “actuation end”) is curved, e.g., away from the face or plane of the lever 1026 and / or the remainder of the base 1022. Such implementations may advantageously provide more space for a user to reach the lever 1026 when the mounts 1010, 1020 are attached to each other and / or to a surface (e.g., a wall). In some implementations, the protrusion 1028 has a semicircular shape. In some implementations, the opening 1027 has a semicircular shape. In some implementations, the opening 1016 has a semicircular shape. In some implementations, a portion of the base 1012 within the opening 1016 (e.g., disposed along a straight side of the semicircular-shaped opening 1016) is elevated.

[0267] Continuing with reference to FIGS. 10C-10D , the base 1012 of the mount 1010 may have a width that tapers at least partially along its height. For example, the width of the base 1012 may taper to a smaller width at or near the center and / or bottom of the base 1012 (assuming the orientation of FIGS. 10C-10D ) and be larger at or near the top of the base 1012. As also shown in FIGS. 10C-10D , the fingers 1024 of the mount 1020 may be angled, for example, relative to the vertical. The fingers 1024 may form a pocket that can receive a portion of the mount 1010 (e.g., the base 1012). In some implementations, the fingers 1024 form a tapered pocket configured to receive a portion of the mount 1010 (e.g., the base 1012). Such a configuration can advantageously allow mount 1010 (which may be secured to hub 700) to be secured vertically to mount 1002 by moving base 1012 down into and / or between fingers 1024, so that mounts 1010, 1020 can be connected as shown in Figures 10G-10K. Note that Figures 10I-10K show mounts 1010, 1020 connected to one another without showing hub 700 to more clearly show how mounts 1010, 1020 may be positioned when secured to one another.

[0268] In one exemplary method, mount 1010 is secured to hub 700, for example, via a screw inserted through hole 1011 in arm 1014 (see FIGS. 10E-10F ) and into threaded hole 711 in hub 700, and mount 1020 is secured to a wall or other object via a screw inserted through hole 1021, with hub 700 and mount 1010 secured to mount 1020, for example, by vertically positioning base 1012 within fingers 1024 of mount 1020. In some implementations, a portion of lever 1026 can engage with a portion of mount 1010 when mounts 1010, 1020 are connected to one another. For example, protrusion 1028 can be disposed within opening 1016 in mount 1010 and / or can engage with structure surrounding opening 1016. Such engagement of the lever 1026 with a portion of the mount 1010 can hinder (e.g., prevent) the mounts 1010, 1020 from being decoupled from one another. When decoupling is desired, the lever 1026 can be actuated (e.g., by moving the free end of the lever 1026 in a direction generally perpendicular to the face or plane of the base 1022), which can remove the protrusion 1028 from the opening 1016, thereby allowing the mount 1010 to be decoupled from the mount 1020. In some implementations, the mount 1010 is removed from the mount 1020 by moving the mount 1010 in a direction opposite to the direction the mount 1010 was moved to insert the mount 1010 into the mount 1020. For example, in some implementations, mount 1010 is connected to mount 1020 by inserting mount 1010 downward into mount 1020, and mount 1010 is disconnected from mount 1020 by moving mount 1010 upward relative to mount 1020.

[0269] While some implementations 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 can connect to and support mounts 910, 1010 (respectively), which 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 mounts 910, 1010 to be removed (e.g., by a vertical movement upward or by being moved otherwise in the direction opposite to the direction in which the mount was inserted / connected) without having to take additional steps (e.g., "unlocking" the lever). Additionally, while the fingers 924, 1024 of the mounts 920, 1020 have been described as angled and the bases 912, 1012 of the mounts 910, 1010 have been described as having a tapered width (for at least a portion of their height), alternative implementations are possible that also 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.

[0270] In some variations, the mount 910 is integral with the viewing hub 700 (e.g., integrally formed into the housing of the hub 700). In some variations, the mount 1010 is integral with the viewing hub 700 (e.g., integrally formed into the housing of the hub 700).

[0271] Additional Implementations As used herein, "real time" or "substantially real time" may refer to events (e.g., receiving, processing, transmitting, displaying, etc.) occurring simultaneously or substantially simultaneously (disregarding any small delays, such as delays imperceptible to a human and / or insignificant delays, such as delays resulting from electrical conduction or transmission). As a non-limiting example, "real time" may refer to events occurring within a time frame of each other on the order of milliseconds, seconds, tens of seconds, or minutes. For example, "real time" may refer to events occurring 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 implementations, "real time" may refer to an event occurring simultaneously with or during another event.

[0272] As used herein, "system," "apparatus," "apparatus," and "device" generally encompass both hardware (e.g., mechanical and electronic) components and, in some implementations, associated software (e.g., specialized computer programs for graphics control) components.

[0273] It should be understood that not all objectives or advantages may necessarily be achieved in accordance with any particular implementation described herein. Thus, for example, those skilled in the art will recognize that some implementations may be configured to operate in a manner that achieves or optimizes one advantage or group of advantages as taught herein without necessarily achieving other objectives or advantages as may be taught or suggested herein.

[0274] Each of the processes, methods, and algorithms described in the preceding sections may be embodied in code modules executed by one or more computer systems or computer processors, including computer hardware, and thereby fully or partially automated. The code modules may 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 systems and modules may also be transmitted as generated data signals (e.g., as part of a carrier wave or other analog or digital propagated signal) over various computer-readable transmission media, including wireless-based media and wired / cable-based media, and may take various forms (e.g., as part of a single or multiplexed analog signal, or as multiple discrete digital packets or frames). The processes and algorithms may be implemented partially or entirely in application-specific circuitry. The results of the disclosed processes and process steps may be stored, persistently or otherwise, in any type of non-transitory computer storage, such as, for example, volatile or non-volatile storage.

[0275] Many variations beyond those described herein will be apparent from this disclosure. For example, depending on the implementation, some acts, events, or functions of any of the algorithms described herein may be performed in a different order, added together, combined, or omitted (e.g., not all described acts or events are required to practice the algorithm). Moreover, in some implementations, acts or events may be performed simultaneously rather than sequentially, for example, through multithreading, interrupt processing, or multiple processors or processor cores or other parallel architectures. In addition, different tasks or processes may be performed by different machines and / or computing systems that can function together.

[0276] The various illustrative logical blocks, modules, and algorithmic elements described in connection with the implementations disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, the various illustrative components, blocks, modules, and elements are described herein generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the particular application and design constraints imposed on the overall system. The described functionality may be implemented in various ways for each particular application, and such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0277] The various features and processes described herein may be used independently of one another or may be combined in various ways. All possible combinations and subcombinations are intended to be within the scope of the present disclosure. Additionally, in some implementations, some method or process blocks may be omitted. The methods and processes described herein are not limited to any particular order, and the blocks or states involved therein may be performed in other orders as appropriate. For example, the described blocks or states may be performed in an order other than that specifically disclosed, or multiple blocks or states may be combined into a single block or state. The example blocks or states may be performed serially, in parallel, or in some other manner. Blocks or states may be added to or removed from the disclosed example implementations. The example systems and components described herein may be configured differently from that described. For example, elements may be added to, removed from, or rearranged compared to the disclosed example implementations.

[0278] The various illustrative logic blocks and modules described in connection with the implementations disclosed herein may be implemented or embodied 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 alternatively, the processor may be a controller, microcontroller, or state machine, combinations thereof, or the like. A processor may include electrical circuitry configured to process computer-executable instructions. In another implementation, a processor includes an FPGA or other programmable device that performs logical operations without processing computer-executable instructions. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. While described herein primarily with reference to digital technology, a processor may also include primarily analog components. For example, some or all of the signal processing algorithms described herein may be implemented in analog circuitry or mixed analog and digital circuitry. 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 computational engine within a consumer electronics device, to name a few.

[0279] Elements of a method, process, or algorithm described in connection with the implementations disclosed herein may be embodied directly in hardware, in a software module stored in one or more memory devices and executed by one or more processors, or in a combination of the two. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of non-transitory computer-readable storage medium, media, or physical computer storage known in the art. An exemplary storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. Alternatively, the storage medium may be integral to 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. Alternatively, the processor and the storage medium may reside as discrete components in a user terminal.

[0280] In particular, conditional language such as "can," "could," "might," or "may," unless specifically stated otherwise or understood otherwise in the context in which it is used, is intended to generally convey that some implementations include certain features, elements, and / or steps but not others. Thus, such conditional language does not imply that the features, elements, and / or steps are in any way required for one or more implementations, or that one or more implementations necessarily include logic for determining, with or without user input or prompting, whether these features, elements, and / or steps are included in or should be performed in any particular implementation.

[0281] Disjunctive language, such as the phrase "at least one of X, Y, or Z," unless specifically stated otherwise or understood otherwise in the context in which it is used, generally indicates that an item, term, etc. can be either X, Y, or Z, or any combination thereof (e.g., X, Y, and / or Z). Thus, such disjunctive language does not imply that some implementations require that at least one of X, at least one of Y, or at least one of Z, each be present.

[0282] Degree language used herein, such as the terms "approximately," "about," "generally," and "substantially," refers to a value, amount, or characteristic that is close to the stated value, amount, or characteristic that still performs a desired function or achieves a desired result. For example, the terms "approximately," "about," "generally," and "substantially" can refer to an amount that is within 10%, within 5%, within 1%, within 0.1%, and within 0.01% of the stated amount. As another example, in some implementations, the terms "generally parallel" and "substantially parallel" refer to a value, amount, or characteristic that deviates by 10 degrees, 5 degrees, 3 degrees, or 1 degree or less from strictly parallel. As another example, in some implementations, the terms "generally perpendicular" and "substantially perpendicular" refer to a value, amount, or characteristic that deviates by 10 degrees, 5 degrees, 3 degrees, or 1 degree or less from strictly perpendicular.

[0283] Any process description, element, or block in the flowcharts described herein and / or shown in the accompanying drawings should be understood as representing, in some cases, a module, segment, or portion of code that comprises one or more executable instructions for implementing a particular logical function or step in the process. As will be appreciated by those skilled in the art, alternative implementations are within the scope of the implementations described herein, such that elements or functions may be omitted, performed substantially simultaneously, or in a different order than that shown or discussed, including in reverse order, depending on the functionality involved.

[0284] Unless expressly stated otherwise, articles such as "a" or "an" should generally be construed as including one or more described items. Thus, phrases such as "a device configured to" are intended to include one or more described devices. Such one or more described devices may also be collectively configured to perform the described descriptions. For example, "a processor configured to perform descriptions A, B, and C" may include a first processor configured to perform description A working in conjunction with a second processor configured to perform descriptions B and C.

[0285] All of the methods and processes described herein may be embodied in and partially or fully automated through software code modules executed by one or more general-purpose computers. For example, the methods described herein may be implemented by a computing system and / or any other suitable computing device. The methods may be executed on a computing device in response to the execution of software instructions or other executable code read from a tangible computer-readable medium. A tangible computer-readable medium is a data storage device that can store data readable 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 tape, flash drives, and optical data storage devices.

[0286] It should be emphasized that many variations and modifications may be made to the implementations described herein, and that these elements should be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure. The section headings used herein are provided for ease of reading only and do not limit the scope of the implementations disclosed in a particular section to the features or elements disclosed in that section. The above description details several implementations. However, no matter how detailed the above appears in text, it will be understood that the systems and methods can be practiced in many ways. Also noted herein, the use of a particular term when describing some features or aspects of the systems and methods should not be construed as implying that the term has been redefined herein to be constrained to include any specific characteristics of the features or aspects of the systems and methods associated with that term.

[0287] 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, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof. [Explanation of symbols]

[0288] 100 Observation Hub 102 Sensor 1 104 Network 106 Server 108 User Input 110 Observation Hub 111 subjects 112 ECG electrode 113 ECG devices 113 Wearable Devices 114 Body Temperature Sensor 115 Motion Sensor 116 Acoustic Sensor 121 Blood Pressure Monitor 122 sensors 123 Ear Device 130 Wearable Hub 132 Holder 140 Optical Sensor 150 PMS 160 PMS 162 Migration Request 164 Identification Data 166 Physiological Function Data 168 Communication Data 200 Observation Hub 201 Hardware Processor 203 Batteries 205 Memory Components 207 Communication Components 209 Display 211 Speaker 213 Microphone 214 Indicator 300 Observation Hub 302 Display 304 Status Indicator 306 Communication Interface 308 Migration Request Button 310 Observation Hub 312 Display 314 Status Indicator 315 Fall Detection Banner 317 Warning Icon 319 Optical Sensor 321 Microphone 323 indicator 325 Button 332 Holder 339 Warning Toggle Button 400 Observation Hub 402 Display 406 Communication Interface 407 User ID Device 408 Migration Request Button 600 Observation Hub 602 Holder 604 beds 700 Observation Hub 701 Display 703 Status Indicator 705 connector port 707 Ethernet port 709 USB port 711 Threaded Hole 800 holder 802 base 804 Arm 805 Protrusion 806 Arm 807 bar 900 Installation Assembly 910 Mount 911 Through Hole 912 base 914 Arm 916 Aperture 920 Mount 921 Through Hole 922 Base 923 Aperture 924 Finger 925 Aperture 926 Lever 927 Aperture 928 protrusion 1000 Installation assembly 1010 Mount 1011 through hole 1012 base 1014 Arm 1016 Aperture 1020 Mount 1021 through hole 1022 base 1024 Finger 1025 Aperture 1026 Lever 1027 Aperture 1028 protrusion 1100 Observation Hub 1101 Aperture 1200 Observation Hub 1201 Display 1203 Status Indicator 1205 connector port 1206 Auxiliary Port 1207 Ethernet port 1209 USB port 1211 Sensor Port 1213 Curved part 1215 heat sink 1217 Battery Housing 1219 Through Hole 1221 Glass part

Claims

1. 1. An observation hub configured to observe a health condition of a subject having a wireless wearable device, comprising: the observation hub; in response to a request to establish wireless monitoring of a subject's physiology at the monitoring hub; accessing wireless configuration data governing wireless communications with the subject's wearable device, the wireless configuration data comprising at least one or more device addresses associated with the wearable device, the wireless configuration data being received at the observation hub from a remote server; establishing wireless communication between the monitoring hub and the wearable device to cause the monitoring hub to wirelessly receive real-time physiological data from the wearable device using one or more wireless communication protocols based on at least the wireless configuration data; receiving historical physiological data from the remote server, the historical physiological data comprising physiological data collected by the wearable device prior to establishing the wireless communication between the observation hub and the wearable device, and the historical physiological data comprising physiological data communicated from the wearable device to another observation hub prior to establishing the wireless communication between the observation hub and the wearable device; generating user interface data for rendering a user interface including the real-time physiological data in combination with the historical physiological data to reduce an observation gap between the historical physiological data and the real-time physiological data; an observation hub comprising one or more hardware computer processors configured to execute a plurality of computer-executable instructions to:

2. 2. The observation hub of claim 1, wherein the one or more hardware computer processors are further configured to execute the plurality of computer-executable instructions to cause the observation hub to establish the wireless communication between the observation hub and the wearable device by establishing a Bluetooth connection between the observation hub and the wearable device.

3. The observation hub of claim 1 or 2, wherein the one or more hardware computer processors are further configured to execute the plurality of computer-executable instructions to cause the observation hub to establish the wireless communication between the observation hub and the wearable device by establishing the wireless communication without performing a Bluetooth pairing process.

4. 4. The observation hub of claim 1, wherein the one or more hardware computer processors are further configured to execute the plurality of computer-executable instructions to cause the observation hub to establish the wireless communication between the observation hub and the wearable device in response to user input, the user input comprising a contactless user input.

5. The one or more hardware computer processors may further configure the observation hub to: receiving identification data via the observation 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 observation with the observation hub; determining that the user is authorized to establish the wireless surveillance based at least on the identification data; 5. The observation hub of claim 1, configured to execute the plurality of computer-executable instructions to:

6. 6. The observation hub of claim 1, wherein the one or more hardware computer processors are further configured to execute the plurality of computer-executable instructions to cause the observation hub to establish the wireless communication between the observation hub and the wearable device based at least on the proximity of the wearable device to the observation hub.

7. 7. The observation hub of claim 1, wherein the one or more hardware computer processors are further configured to execute the plurality of computer-executable instructions to cause the observation hub to access the wireless configuration data by wirelessly receiving the wireless configuration data from the remote server.

8. 8. The observation hub of claim 1, wherein the one or more hardware computer processors are further configured to execute the plurality of computer-executable instructions to cause the observation hub to access the wireless configuration data based at least on retrieving the wireless configuration data from a memory.

9. 9. The observation hub of claim 1, wherein the one or more hardware computer processors are further configured to execute the plurality of computer-executable instructions to cause the observation hub to render the user interface via a display of the observation hub.

10. 10. The observation hub of claim 1, wherein the one or more hardware computer processors are further configured to execute the plurality of computer-executable instructions to cause the observation hub to receive past user interface data from the remote server, the past user interface data corresponding to the past physiological function data, and the past user interface data having been previously generated by another observation hub.

11. 1. A method for continuously monitoring a patient having a wireless wearable device while changing from a first observation hub to a second observation hub, comprising: In response to a request to establish wireless observation at an observation hub of a subject's physiology, accessing wireless configuration data governing wireless communication with a subject's wearable device, the wireless configuration data comprising at least one or more device addresses associated with the wearable device, the wireless configuration data being received at the observation hub from a remote server; establishing wireless communication between the monitoring hub and the wearable device to cause the monitoring hub to wirelessly receive real-time physiological data from the wearable device using one or more wireless communication protocols based on at least the wireless configuration data; receiving historical physiological data from a remote server, the historical physiological data comprising physiological data collected by the wearable device prior to establishing the wireless communication between the monitoring hub and the wearable device, and the historical physiological data comprising physiological data communicated from the wearable device to another monitoring hub prior to establishing the wireless communication between the monitoring hub and the wearable device; generating user interface data for rendering a user interface including the real-time physiological data in combination with the historical physiological data to reduce an observation gap between the historical physiological data and the real-time physiological data; A method comprising:

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

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

14. receiving identification data via the observation 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 a wireless observation with the observation hub; and determining, based at least on the identification data, that the user is authorized to establish the wireless observation.

15. 15. The method of claim 11, wherein accessing the wireless configuration data comprises retrieving the wireless configuration data from a memory.

16. 16. The method of any one of claims 11 to 15, further comprising the step of rendering the user interface via a display of the observation hub.

17. 17. The method of any one of claims 11 to 16, further comprising receiving 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 having been previously generated by the other observation hub.

Images