System for transmitting sensor data using dual communication protocols

Abstract

A system for collecting physiological data from a patient is disclosed. The system includes a reusable module and a disposable module. The disposable module collects and transmits the physiological data to the reusable module, which then transmits the physiological data to a patient monitoring system. The reusable module accesses operational data from the disposable module to validate the disposable sensor assembly. In some cases, the operational data includes sensor life data that can be used to determine the life of the disposable module. The disposable sensor assembly may store the physiological data for a predetermined length of time when wireless communication is not established for the reusable module.

Description

[Technical Field]

[0001] Related Applications This application is a continuation-in-part of U.S. patent application Ser. No. 16 / 599,017, filed October 10, 2019, and entitled "SYSTEM FOR TRANSMISSION OF SENSOR DATA USING DUAL COMMUNICATION PROTOCOL," which claims the benefit of U.S. provisional application Ser. No. 62 / 744,988, filed October 12, 2018, and entitled "SYSTEM FOR TRANSMISSION OF SENSOR DATA USING DUAL COMMUNICATION PROTOCOL." This application claims the benefit of U.S. Provisional Application No. 63 / 023,711, entitled "SYSTEM FOR TRANSMISSION OF SENSOR DATA USING DUAL COMMUNICATION PROTOCOL," filed May 12, 2020, and U.S. Provisional Application No. 63 / 062,939, entitled "SYSTEM FOR TRANSMISSION OF SENSOR DATA USING DUAL COMMUNICATION PROTOCOL," filed August 7, 2020. The entire disclosure of each of the above-identified applications is incorporated herein by reference.

[0002] The present disclosure relates to physiological sensors and wireless pairing devices. More particularly, the present disclosure relates to collecting physiological data using physiological sensors and transmitting the data to nearby computing systems using wireless pairing devices. [Background technology]

[0003] Conventional physiological measurement systems are limited by the patient cable connection between the sensor and monitor. The patient must be positioned in close proximity to the monitor. Furthermore, repositioning the patient requires either disconnecting the monitoring equipment, resulting in a loss of measurements, or awkwardly moving the patient equipment and cable simultaneously. Various devices have been proposed or implemented to create a wireless communication link between the sensor and monitor, freeing the patient from the patient cable. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] U.S. Patent Application No. 9,436,645 [Patent Document 2] U.S. Patent Application No. 11 / 580,214 (now U.S. Patent No. 7,880,626) Summary of the Invention [Means for solving the problem]

[0005] Among other things, this disclosure describes embodiments of systems, devices, and methods for collecting patient physiological data and transmitting that data via wireless transmission to a nearby computing system.

[0006] According to one aspect of the present disclosure, a system for collecting physiological data from a patient is disclosed. The system can include a disposable module and a reusable module. The disposable module can include a sensor element capable of collecting physiological data from the patient, a memory, and a battery. The reusable module can include a processor, a memory, and a wireless communication module capable of establishing wireless communication with a patient monitoring system. The memory of the reusable module can store the physiological data before the wireless communication module establishes wireless communication. The processor of the reusable module can receive the physiological data from the sensor element of the disposable module when the reusable module is coupled to the disposable module.

[0007] The system may include one or more of the following features: The disposable module may include an attachment mechanism and a dock coupled to the housing. The housing may house a memory and a battery. The sensor element may be housed within the housing. The sensor element may be coupled to the housing via a cable assembly. The processor of the reusable module may transmit a sensor signal to the sensor element of the disposable module. The sensor signal may cause the sensor element to collect physiological data from the patient. The wireless communication module may establish wireless communication with the patient monitoring system when the wireless communication module is located within a predetermined distance from the patient monitoring system. The wireless communication module may transmit identification information to the patient monitoring system when the wireless communication module is located within the predetermined distance from the patient monitoring system. The patient monitoring system may create an association with the wireless communication module upon receiving the identification information from the wireless communication module. The identification information may include an identifier that uniquely identifies the disposable module. The patient monitoring system may establish wireless communication with the reusable module using the identifier. The disposable module may include an attachment mechanism, and the attachment mechanism may couple the disposable module to the patient. The attachment mechanism may be a medical band. The attachment mechanism may include a radio frequency identifier. The battery of the disposable module can provide power for the reusable module when the disposable module is coupled to the reusable module. The memory of the reusable module can store physiological data for approximately 6 hours to approximately 30 days. The memory of the reusable module can store physiological data for a length of time before establishing or detecting wireless communication. The length of time can be specified by a user or can be user-configurable. In some cases, the user may not specify the length of time to store physiological data in the memory of the reusable module.The memory of the reusable module can store the physiological data for, for example, a default length of time before the wireless communication module of the reusable module establishes wireless communication. The default length of time can be stored in the memory of the reusable module. The physiological data can be collected and stored in the memory of the disposable module when an abnormality is detected. The abnormality can include at least one of a low blood pressure reading, a high blood pressure reading, a low respiratory rate reading, a high respiratory rate reading, a low blood oxygen saturation reading, an arrhythmia, a consistently low or low blood oxygen saturation reading, a low heart rate, or a high heart rate. The processor of the reusable module can transmit the physiological data to local or remote storage when wireless communication between the wireless communication module and the online server is established. Transmission of the stored physiological data can be automatic or manual. The physiological data collected by the sensor element can have high fidelity. The physiological data collected by the sensor element can have low fidelity. The fidelity of the physiological data stored in the memory can be variable. The fidelity of the stored physiological data can be varied based at least in part on a length of time designated for storing the physiological data in the memory of the reusable module. The fidelity of the stored physiological data can be varied based at least in part on a type of physiological data or a type of health-related event. The fidelity of the physiological data collected by the sensor element can be variable. The fidelity of the physiological data collected by the sensor element can be varied based at least in part on a length of time designated for storing the physiological data in the memory of the reusable module. The fidelity of the stored physiological data collected by the sensor element can be varied based at least in part on a type of physiological data or a type of health-related event. The physiological data stored in the memory of the reusable module may be downloaded when the battery of the disposable module is depleted.The memory can store physiological data collected by the sensor element from the time the reusable module is attached to the disposable module until the reusable portion is detached from the disposable module or the battery of the disposable module fails.

[0008] According to another aspect of the present disclosure, a method for collecting physiological data from a patient using a reusable module that can be coupled to a disposable module including a non-invasive sensor element is disclosed. The method can include detecting coupling of the reusable module and the disposable module. The method can further include collecting physiological data from the disposable module, where the physiological data is collected via the sensor element of the disposable module and the physiological data is stored in a memory of the reusable module. The method can further include establishing wireless communication with a remote computing device. The method can further include transmitting the physiological data to the remote computing device via wireless communication.

[0009] The method may include one or more of the following features: The physiological data may be stored in the memory of the reusable module for a length of time before establishing wireless communication, and the length of time may range from about 6 hours to about 30 days. The length of time may be configurable via a setting provided by a healthcare provider. The memory may store a default length of time, and when the length of time is not specified, the physiological data may be stored in the memory of the disposable module for the default length of time before wireless communication is established between the reusable module and the remote computing device. The physiological data may include health-related events related to the patient. The physiological data may be collected and stored when an abnormality is detected. The abnormality may include at least one of a low blood pressure reading, a high blood pressure reading, a low respiratory rate reading, a high respiratory rate reading, a low blood oxygen saturation reading, an arrhythmia, a consistently low or low blood oxygen saturation reading, a low heart rate, or a high heart rate. The physiological data may be transmitted to the remote computing device when wireless communication is established. The fidelity of the physiological data can vary based at least in part on a length of time designated for storing the physiological data in the memory of the reusable module. The fidelity of the physiological data can vary based at least in part on a type of physiological data or a type of health-related event. The physiological data stored in the memory of the reusable module may be downloaded when the battery of the disposable module is depleted.

[0010] According to another aspect of the present disclosure, a system for collecting physiological data from a patient is disclosed. The system can include a reusable module and a disposable module. The reusable module can include a processor, a first memory, and a wireless communication module configured to establish wireless communication with a patient monitoring system. The disposable module can include a sensor element capable of collecting physiological data from the patient, a memory, and a battery. The memory can store operational data associated with the sensor element. The disposable module can be validated based at least in part on the operational data. The first memory can store physiological data collected by the sensor element of the disposable module.

[0011] The system may include one or more of the following features: the operational data may include sensor type information associated with the disposable module. The sensor type information may indicate one or more types of sensors associated with the disposable module. The reusable module assembly may be associated with a sensor type, and the disposable module may be verified based at least in part on a comparison of the sensor type associated with the reusable module assembly with the sensor type information associated with the disposable module. A sensor lifetime may be determined based at least in part on the operational data and the sensor lifetime data, and the sensor lifetime may represent an expected operating time of the disposable module. The sensor lifetime data may include sensor usage information and one or more functions, and the sensor lifetime data may be stored in a memory of the disposable module. The sensor lifetime may be automatically updated when a patient condition changes or an operating condition for the disposable module changes. The physiological data may be stored in the first memory for a length of time. The length of time may range from approximately 6 hours to approximately 30 days. The length of time may be configurable via a setting provided by a healthcare provider. The first memory can store a default length of time, and when a length of time is not specified, the first memory can store physiological data for the default length of time before the wireless communication module establishes wireless communication. The physiological data can include health-related events related to the patient. The physiological data can be stored when an abnormality is detected. The abnormality can include at least one of a low blood pressure reading, a high blood pressure reading, a low respiratory rate reading, a high respiratory rate reading, a low blood oxygen saturation reading, an arrhythmia, a consistently low or low blood oxygen saturation reading, a low heart rate, or a high heart rate.The processor of the reusable module can transmit the stored physiological data to local or remote storage via the wireless communication module when wireless communication between the wireless communication module and the online server is established. Transmission of the stored physiological data can be automatic or manual. The physiological data collected by the sensor element can have high fidelity. The physiological data collected by the sensor element can have low fidelity. The fidelity of the physiological data stored in the memory can be indeterminate. The fidelity of the stored physiological data can vary based at least in part on a predetermined length of time. The fidelity of the stored physiological data can vary at least in part on a type of physiological data or a type of health-related event. The fidelity of the physiological data collected by the sensor element can be indeterminate. The fidelity of the stored physiological data collected by the sensor element can vary based at least in part on a predetermined length of time. The fidelity of the stored physiological data collected by the sensor element can vary based at least in part on a type of physiological data or a type of health-related event. The memory can store physiological data collected by the sensor element from the time the reusable module is attached to the disposable module until the reusable portion is detached from the disposable module or the battery of the disposable module fails.

[0012] According to another aspect of the present disclosure, a method for validating a disposable module is disclosed. The method can include detecting coupling between a disposable module and a reusable module. The method can further include accessing operational data associated with the disposable module. The method can further include analyzing the operational data. The method can further include validating the disposable module based at least in part on the analysis of the operational data.

[0013] The method may include one or more of the following features: detecting coupling between the disposable module and the reusable module may include determining that the reusable module is receiving power from the disposable sensor module; the disposable module may include a memory capable of storing operational data; analyzing the operational data may include identifying sensor type information from the operational data, comparing the sensor type information to a sensor type associated with the reusable module, and determining that the disposable module is compatible with the reusable transmitter module based at least in part on comparing the sensor type information to the sensor type associated with the reusable module.

[0014] For purposes of summarizing the disclosure, certain aspects, advantages, and novel features have been described herein. Of course, it should be understood that not necessarily all such aspects, advantages, or features may be embodied in any particular embodiment. [Brief explanation of the drawings]

[0015] [Figure 1] FIG. 1 illustrates an embodiment of a sensor system including a sensor attached to a patient that transmits patient physiological data via a cable to a computing device. [Figure 2A] FIG. 1 illustrates another embodiment of a sensor system including a sensor assembly that collects and wirelessly transmits patient physiological data to a computing device. [Figure 2B] FIG. 2 is a schematic diagram of an embodiment of a sensor assembly and a computing device showing further details of the sensor assembly. [Figure 2C] FIG. 1 is a wiring diagram of one embodiment of a sensor assembly. [Figure 3A]FIG. 1 is a perspective view of one embodiment of a sensor assembly for collecting and wirelessly transmitting patient physiological data to a computing device. [Figure 3B] FIG. 3B is an exploded top perspective view of the sensor assembly of FIG. 3A. [Figure 3C] FIG. 3B is an exploded bottom perspective view of the sensor assembly of FIG. 3A. [Figure 3D] FIG. 3B is a top view of one embodiment of the sensor assembly of FIG. 3A. [Figure 4] FIG. 10 is a perspective view of another embodiment of a sensor assembly for collecting and wirelessly transmitting patient physiological data to a computing device. [Figure 5] FIG. 10 is a perspective view of another embodiment of a sensor assembly for collecting and wirelessly transmitting patient physiological data to a computing device. [Figure 6A] FIG. 10 is a diagram of a flex circuit of the disposable module of the sensor assembly. [Figure 6B] FIG. 10 is a diagram of a flex circuit of the disposable module of the sensor assembly. [Figure 6C] FIG. 6B is a side view of the flex circuit of FIG. 6A showing a modification of the flex circuit configuration. [Figure 6D] FIG. 6B is a side view of the flex circuit of FIG. 6A showing a modification of the flex circuit configuration. [Figure 7A] FIG. 1 is a perspective view of an embodiment of a sensor assembly coupled to an embodiment of an attachment mechanism. [Figure 7B] FIG. 1 is a perspective view of an embodiment of a sensor assembly coupled to an embodiment of an attachment mechanism. [Figure 7C] FIG. 1 is a perspective view of an embodiment of a sensor assembly coupled to an embodiment of an attachment mechanism. [Figure 7D] FIG. 1 is a perspective view of an embodiment of a sensor assembly coupled to an embodiment of an attachment mechanism. [Figure 7E] FIG. 1 is a perspective view of an embodiment of a sensor assembly coupled to an embodiment of an attachment mechanism. [Figure 7F] FIG. 1 is a perspective view of an embodiment of a sensor assembly coupled to an embodiment of an attachment mechanism. [Figure 7G] FIG. 1 is a perspective view of an embodiment of a sensor assembly coupled to an embodiment of an attachment mechanism. [Figure 7H] FIG. 1 is a perspective view of an embodiment of a sensor assembly coupled to an embodiment of an attachment mechanism. [Figure 7I] FIG. 1 is a perspective view of an embodiment of a sensor assembly coupled to an embodiment of an attachment mechanism. [Figure 7J] FIG. 1 is a perspective view of an embodiment of a sensor assembly coupled to an embodiment of an attachment mechanism. [Figure 7K] FIG. 1 is a perspective view of an embodiment of a sensor assembly coupled to an embodiment of an attachment mechanism. [Figure 8A] FIG. 1 is a diagram of a dongle operably coupled to a computing device. [Figure 8B] FIG. 1 is a diagram of a dongle operably coupled to a computing device. [Figure 8C] FIG. 1 is a diagram of a dongle operably coupled to a computing device. [Figure 9A] FIG. 10 illustrates a reusable module and a computing device coupled to a dongle, showing further details of how the reusable module and computing device are paired. [Figure 9B] FIG. 10 illustrates a reusable module and a computing device coupled to a dongle, showing further details of how the reusable module and computing device are paired. [Figure 9C] FIG. 10 illustrates a reusable module and a computing device coupled to a dongle, showing further details of how the reusable module and computing device are paired. [Figure 10A]3B is a perspective view of the reusable and disposable modules of FIG. 3A attached to a patient's wrist, showing further details for how the reusable and disposable modules mate. [Figure 10B] 3B is a perspective view of the reusable and disposable modules of FIG. 3A attached to a patient's wrist, showing further details for how the reusable and disposable modules mate. [Figure 10C] 3B is a perspective view of the reusable and disposable modules of FIG. 3A attached to a patient's wrist, showing further details for how the reusable and disposable modules mate. [Figure 10D] 3B is a perspective view of the reusable and disposable modules of FIG. 3A attached to a patient's wrist, showing further details for how the reusable and disposable modules mate. [Figure 11A] FIG. 1 illustrates a method for establishing wireless communication and acquiring and displaying patient physiological parameters using a reusable module, a disposable module, and a computing device. [Figure 11B] FIG. 10 illustrates another method of establishing wireless communication and acquiring and displaying patient physiological parameters using a reusable module, a disposable module, and a computing device. [Figure 12] FIG. 10 illustrates another embodiment of a method for acquiring and displaying patient physiological parameters using a reusable module, a disposable module, and a computing device. [Figure 13A] FIG. 1 illustrates a mobile application for establishing wireless communication with a reusable module. [Figure 13B] FIG. 13B is a diagram of the mobile application of FIG. 13A displaying patient parameters in a display format. [Figure 13C] FIG. 13B is a diagram of the mobile application of FIG. 13A displaying patient parameters in a display format. [Figure 13D] FIG. 13B is a diagram of the mobile application of FIG. 13A displaying patient parameters in a display format. [Figure 13E] FIG. 13B is a diagram of the mobile application of FIG. 13A displaying patient parameters in a display format. [Figure 14A] FIG. 10 is a block diagram of one embodiment of a memory of a disposable module. [Figure 14B] FIG. 10 illustrates a method for identifying a disposable module based at least in part on operational data stored in a memory of the disposable module. [Figure 15A] 1 illustrates an embodiment of a backup power device for a sensor assembly. [Figure 15B] 1 illustrates an embodiment of a backup power device for a sensor assembly. [Figure 16A] FIG. 1 is a block diagram of an exemplary sensor assembly and an exemplary patient monitoring device in wireless communication. [Figure 16B] FIG. 1 is a schematic diagram illustrating wireless communication between a sensor assembly, a patient monitoring device, and a network. [Figure 16C] FIG. 1 illustrates an exemplary method for transmitting physiological data using a sensor assembly. [Figure 16D] FIG. 1 illustrates an exemplary method for identifying a patient monitoring device and transmitting patient physiological data to the identified patient monitoring device. [Figure 16E] FIG. 1 illustrates an exemplary method for identifying a patient monitoring device and transmitting patient physiological data to the identified patient monitoring device. [Figure 17] FIG. 1 is a schematic diagram illustrating an exemplary environment for transmitting patient physiological data from a reusable module to a user's computing device. DETAILED DESCRIPTION OF THE INVENTION

[0016] Introduction Wiring solutions for sensors can be cumbersome and difficult to manage when multiple sensors are attached to a patient, as shown in Figure 1. For example, sensor cables can become tangled and damaged with repeated use. Additionally, because sensors are tethered to the patient health monitor, the patient must be positioned in close proximity to the health monitor, which can limit patient movement. If a longer cable is required, both the sensor and the cable must be repositioned. Similarly, when sensors are tethered to the monitor, patient mobility becomes very difficult, requiring the patient to stay close to the monitor or detach the sensor, resulting in a loss of measurements.

[0017] Overview 1 illustrates an example of a sensor system 100 including a computing device 106 coupled to sensors 140A, 140B, 140C, and 140D via a cable 130, where the sensors are attached to a patient 110. The computing system 106 may include a display 108 capable of displaying various physiological parameters. The sensors 140A, 140B, 140C, and 140D may collect various types of physiological data from the patient 110 and transmit it to the computing system 106 via the cable 130. Some examples of the sensors 140A, 140B, 140C, and 140D include, but are not limited to, a rainbow acoustic monitoring sensor (RAM), an O3 Regional Oximetry sensor, an SpO2 sensor, a blood pressure sensor, an ECG sensor, etc.

[0018] However, the cables 130 can be cumbersome for the patient and prone to tangling. The cables 130 can become kinked and damaged over time. Furthermore, because the sensors 140A, 140B, 140C, and 140D are connected to the computing system 106 via the cables 130, the location of the computing system 106 may be limited by the length of the cables 130 attached to the sensors 140A, 140B, 140C, and 140D. The cables 130 may also restrict patient movement. Therefore, a wireless solution that includes wireless communication capabilities between the sensors and the computing device may eliminate some of the problems with wiring configurations. A wireless configuration may eliminate the need for the cables 130 between the sensors and the computing device, thus increasing patient mobility.

[0019] However, wireless solutions may have their own limitations. For example, wireless patient monitoring sensors require an internal power source (e.g., a battery), which may have limited capacity due to the size of the sensor. Furthermore, continuous data collection and wireless transmission may require significant power usage, which may severely limit the operation of the sensor. Furthermore, replacing the entire device when the internal battery is depleted may be costly. Furthermore, having a rechargeable battery may not be appropriate in a hospital environment, where nurses may not have enough time to wait for the battery to recharge. Also, waiting for the patient to recharge the battery when needed may not be ideal. Therefore, it may be advantageous to provide a sensor system that is compatible with existing sensors and is capable of monitoring and performing wireless communication as described herein.

[0020] 2A illustrates a sensor system 100 that includes a computing device 206 that wirelessly receives patient physiological data for a patient 110 from sensor assemblies 202A, 202B, 202C, and 202D. The sensor assemblies 202A, 202B, 202C, and 202D can establish communication with the computing device 206 to enable wireless transmission of data between the sensor assemblies 202A, 202B, 202C, and 202D and the computing device 206. The computing device 206 can include a display 208 that can display patient parameters determined from the patient physiological data received from the sensor assemblies 202A, 202B, 202C, and 202D.

[0021] 2B shows a schematic diagram of a sensor assembly 202 wirelessly connected to a computing device. The sensor assembly 202 can include a disposable module 220 and a reusable module 250. The reusable module 250 can be a pairing device capable of establishing a wireless connection with the computing device 206. In some implementations, the reusable module 250 is a transmitter device and can send and receive data to and from nearby computing devices, such as the computing device 206.

[0022] The disposable module 220 may include a dock 222 coupled to the sensor 240 via a cable 230. The dock 222 may be removably connected to the reusable module 250. The reusable module 250 and the computing device 206 may establish wireless communication 204 with each other and perform wireless transmission of data therebetween. The reusable module 250 may transmit patient physiological parameters to the computing device 206, where such parameters are calculated from raw physiological data collected by the sensor 240. The transmitted patient data may be raw data collected by the sensor 240.

[0023] The reusable module 250, alone or in combination with the dock 222, can perform signal processing on the raw physiological data and transmit the processed physiological data to the computing device 206. The reusable module 250 establishes wireless communication 204 with the computing device 206, allowing data to be transmitted between the reusable module 250 and the computing device 206. The reusable module 250 can establish wireless communication 204 with one or more computing devices 206. As shown in FIG. 2A , the computing device 206 can establish wireless communication 204 with sensor assemblies 202A, 202B, 202C, and 202D. The computing device 206 can establish wireless communication 204 with fewer than four or more than four sensor assemblies 202.

[0024] The reusable module 250 can establish wireless communication 204 with a portable mobile device, such as a cell phone, smartphone, or tablet. The computing device 206 can be a hospital patient monitoring system, which includes various types of monitors capable of displaying patient health data. The computing device 206 can be a mobile monitoring system or a personal mobile device. The computing device 206 can be the Root® Platform, a patient monitoring and connectivity platform available from Masimo Corporation of Irvine, California. A cable-enabled mobile physiological parameter monitoring system is described in U.S. Patent No. 9,436,645, issued September 6, 2016, and entitled "MEDICAL MONITORING HUB," the disclosure of which is incorporated herein by reference in its entirety.

[0025] The cable 230 may or may not be flexible. The cable 230 may be a thin film containing electrical circuitry. The cable 230 may be surrounded by various types of electrically insulating materials. The cable 230 may be substantially flat or round.

[0026] The sensor 240 may be an acoustic sensor, an ECG sensor, an EEG sensor, an SpO2 sensor, or any other type of patient monitoring sensor. The sensor 240 may include one or more emitters and detectors. The emitters may be low-power, high-brightness LEDs (light-emitting diodes) to extend the life of the battery 224. The sensor 240 may measure raw physiological data according to various types of patient physiological parameters, including, but not limited to, body temperature, blood pressure, blood oxygen saturation, hemoglobin levels, electrocardiograms, etc. The sensor measurements may be used by a physician to determine the patient's condition and treatment. The sensor 240 may transmit the raw physiological data to the dock 222 via the cable 230. The sensor 240 and the dock 222 may form a single unit such that the dock 222 receives the physiological data directly from the sensor 240 without the cable 230. The dock 222 may be integrated with one or more of the sensors 340.

[0027] The sensor 240 can output a raw sensor signal or a conditioned sensor signal. The sensor 240 can include a signal processor that can process the raw sensor signal or the conditioned sensor signal to derive and calculate a physiological parameter associated with the raw sensor signal or the conditioned sensor signal.

[0028] The sensor 240 can perform mixed analog-digital pre-processing of the analog sensor signal to generate a digital output signal. As explained above, the sensor 240 can include a signal processor that can perform digital post-processing of the front-end processor output. The input sensor signal and the output conditioned signal can be analog or digital. The front-end processing can be purely analog or purely digital. The back-end processing can be purely analog or mixed analog and digital.

[0029] The sensor 240 can include an encoder, which converts, for example, a digital word or serial bit stream into a baseband signal. The baseband signal can include a symbol stream that drives the transmit signal modulation and can be a single signal component or multiple related signal components. The encoder can include data compression and redundancy.

[0030] The sensor 240 may include a signal processor, an encoder, and a controller. The sensor 240 may utilize an emitter 242 and a detector 244 to generate a sensor signal, such as a plethysmographic signal. The signal processor may then use the sensor signal to derive a parameter signal, which may include real-time measurements of oxygen saturation and pulse rate. The parameter signal may also include other parameters, such as a perfusion index and a signal quality measurement. The signal processor may be an MS-5 or MS-7 board, commercially available from Masimo Corporation of Irvine, California. The signal processor steps may be performed by the processor 254 of the reusable module 250, as described above.

[0031] The dock 222 can be positioned on various parts of the patient's body. For example, the dock 222 can be positioned on the patient's chest. The dock 222 can be positioned on other parts of the patient, including, but not limited to, the torso, back, shoulders, arms, legs, neck, or head. The dock 222 can be secured to the patient using various means. For example, the dock 222 can be secured to the patient using an adhesive. In another example, the dock 222 can be secured to the patient using a fastener, such as tape, that is disposed over at least a portion of the dock 222. The dock 222 can be mechanically attached to at least one strap, which can be wrapped around the patient.

[0032] The reusable module 250 can receive physiological data from the sensor 240 via the dock 222. The reusable module 250 can transmit the physiological data wirelessly to the computing device 206. The reusable module 250 can be coupled to the dock 222 to establish electronic communication between the reusable module 250 and the dock 222. The electrical communication between the dock 222 and the reusable module 250 can enable transmission of the physiological data from the dock 222 to the paired device 250. The coupling between the reusable module 250 and the dock 222 can be waterproof or shock-resistant. The disposable module 220 and the reusable module 250 may be shock-resistant or waterproof. The disposable module 220 and the reusable module 250 can be durable in various types of environments. For example, the reusable module 250 can be completely sealed, allowing the reusable module 250 to be washed, cleaned, and reused.

[0033] 2B, the dock 222 may include a memory 226 and a battery 224. The reusable module 250 may include an antenna 252, a processor 254, and a memory 256. The antenna 252, the processor 254, and the memory 256 may be operatively connected to each other to enable electronic communication or transmission between the antenna 252, the processor 254, and the memory 256.

[0034] The antenna 252 may be an RFID (Radio Frequency Identification) antenna. The antenna 252 may be a Bluetooth® antenna. The reusable module 250 may include one or more antennas 252. In some aspects, the reusable module 250 includes a first antenna and a second antenna, where the first antenna is a receive antenna and the second antenna is a transmit antenna. The first antenna may be a transmit antenna and the second antenna may be a receive antenna. Both the first antenna and the second antenna may be capable of both receiving data from and transmitting data to the computing device 206. The first antenna may be a passive antenna, while the second antenna may be an active antenna. The first antenna may be an active antenna, while the second antenna may be a passive antenna. The active antenna may include a built-in amplifier that may amplify a certain spectrum or frequency of a signal. The first antenna may establish an RFID or NFC (near field communication) connection with the computing device 206, while the second antenna may establish a Bluetooth® connection with the computing device 206. In another aspect, both the first and second antennas may establish RFID and / or Bluetooth® wireless connections. The process of establishing wireless communication 204 with the computing device 206 and transmitting patient physiological data wirelessly to the computing device 206 is described in further detail below.

[0035] The memory 256 may be a computer hardware integrated circuit that stores information for immediate use by a computer (e.g., the processor 254). The memory 256 may store patient physiological data received from the sensor 240. The memory 256 may be a volatile memory. For example, the memory 256 is a dynamic random access memory (DRAM) or a static random access memory (SRAM). The memory 256 may be a non-volatile memory. For example, the memory 256 is a flash memory, a ROM (read-only memory), a PROM (programmable read-only memory), an EPROM (erasable programmable read-only memory), and / or an EEPROM (electrically erasable programmable read-only memory).

[0036] The memory 256 of the reusable module 250 can store patient physiological data received from the sensor 240. The memory 256 can store electronic instructions that, when accessed, prompt the processor 254 to receive patient physiological data from the memory 226 of the dock 222, store the data in the memory 256, retrieve the data from the memory 256, transmit the data to the antenna 252, and transmit the data wirelessly to the computing device 206 using the antenna 252. One or more of the above-described actions can be performed simultaneously. For example, the processor 254 of the reusable module 250 can receive patient physiological data from the memory 226 of the dock 222 and simultaneously store the data in the memory 256. In some implementations, the reusable module 250 receives patient physiological data directly from the sensor 240 without the memory 226 storing the patient physiological data. The memory 226 can store other types of data, such as operational data and sensor lifetime data, as described herein.

[0037] The memory 256 can store patient physiological data and / or health-related events related to the patient when the sensor assembly 202 is no longer located within range of the computing system 206 or, in some cases, cannot communicate with the computing system 206. The memory 256 can have sufficient capacity to store patient health data and / or health-related events, as noted above. In some cases, the memory 256 can store patient physiological data regardless of whether the reusable module 250 is paired with the computing device 206. Some examples of health-related events can include arrhythmia, low blood pressure, blood oxygen level (SpO2), etc. Such data and / or health-related events may be accessed via a mobile application on a mobile device (e.g., a smartphone, a tablet, etc.). The data collected and stored in the memory 256 may be downloaded and / or transferred to local or remote storage. For example, the data can be transferred to a cloud server or a computer system at a doctor's office. The transfer of data can occur automatically when wireless communication is established between the sensor assembly 202 and, for example, an online server or the computing system 206, or manually.

[0038] Patient data and / or health-related events may be relayed to devices that do not have a display. In such situations, the device may have a light source (e.g., an LED) that can flash different colors or patterns to communicate, for example, that patient or medical personal data has been transferred, that an error has occurred, that data needs to be reviewed, or that something else has happened. Various rules may be used to determine when or under what circumstances patient physiological information can be transmitted from the sensor assembly 202 to other external devices (e.g., monitoring devices, mobile devices, etc.).

[0039] In some implementations, the memory 256 may store patient data and / or health-related events related to the patient only when the sensor assembly 202 is no longer within range of the computing system 206 or, in some cases, is unable to communicate with the computing system 206. In some implementations, the patient data and / or health-related events may be stored when an abnormality is detected. The abnormality may include, but is not limited to, a low blood pressure reading, a high blood pressure reading, a low respiratory rate reading, a high respiratory rate reading, a low blood oxygen saturation reading, an irregular heartbeat, a consistently low or low blood oxygen saturation reading, a low heart rate, a high heart rate, etc. In some implementations, a combination of abnormalities or an abnormal combination of patient status and / or health parameters may cause the sensor assembly 202 to store patient data and / or health-related events. For example, the sensor assembly 202 may store patient data and / or health-related events when a high blood pressure reading and a low heart rate are detected. In another example, the sensor assembly 202 may store patient data and / or health-related events when the patient is less mobile and a high heart rate or high blood pressure is detected. In yet another example, the sensor assembly 202 may store patient data and / or health-related events when the patient is both less mobile and has low blood oxygen levels. Any suitable combination of abnormalities or abnormal conditions may be used to trigger the sensor assembly 202 to store patient data and / or health-related events.

[0040] In some implementations, the memory 256 may store only selected health-related events. Such a configuration may advantageously maximize or extend the life of the battery 224 and / or the memory 256. For example, this data may be as simple as a timestamp of when the event or trigger occurred, or it may be snapshots of data taken immediately before and after the event or trigger. Events may include physiologically significant events such as an abnormal heart rate or a drop in oxygen saturation. A trigger indicates the start of an event and may cause a window of data to be stored in memory. For example, the system may continuously retain the window of data for a period of time, e.g., five minutes. When a trigger is detected, data within a window beginning a few minutes before the event and continuing a few minutes after the event may be stored in memory and held until the data is downloaded to another device. Of course, various times before and after the trigger may be stored, e.g., ranging from 1 second to 24 hours.

[0041] In some implementations, the memory 256 can store a large amount of data, e.g., days or weeks' worth of data, before establishing wireless communication with the computing system 206, for example. In some implementations, the memory 256 can store up to 96 hours or more of data before establishing wireless communication with the computing system 206, for example. In some implementations, the memory 256 can store up to 30 days' worth of data. The length of time that the sensor assembly 202 can collect and store patient data and / or health-related events before establishing wireless communication with the computing system 206, for example, can be between about 1 hour and about 30 days, between about 3 hours and about 28 days, between about 6 hours and about 21 days, between about 12 hours and about 14 days, between about 24 hours and 7 days, or an indefinite range between about 1 hour, about 3 hours, about 6 hours, about 12 hours, about 24 hours, about 72 hours, about 7 days, about 14 days, about 21 days, about 28 days, about 30 days, or any range between any two of the above values. In this configuration, the device can be worn by the patient at home for the monitoring period, and then downloaded over a wired or wireless connection by a physician at the physician's office. Data can also be stored for periods when no network connection is detected, and then downloaded immediately after a wired or wireless network connection is detected.

[0042] In some implementations, a user may specify the length of time for memory 256 to store patient physiological data before establishing or detecting wireless communication. This may be advantageous in non-critical situations where real-time patient monitoring and management may not be required. For example, a healthcare provider may request that a patient return to a doctor's office in one week and provide sensor assembly 202 configured to store patient physiological data for the next seven days in memory 256. Thus, when the patient returns to the doctor's office one week later, the healthcare provider can access the data collected and stored in memory 256 via reusable module 250. In some implementations, sensor assembly 202 may be brought to the doctor's office or shipped (via mail) to the doctor's office. Additionally or alternatively, the data stored in memory may be automatically or manually uploaded and stored on a server (e.g., a cloud server) accessible to a healthcare provider (e.g., a doctor). In some implementations, the data stored in memory 256 may be uploaded, for example, via a web interface or a mobile application interface accessible via a user computing device (e.g., a mobile phone, a laptop computer, a desktop computer, a smartphone, a smart device, etc.) as described herein. The sensor assembly 202 may establish wireless communication with the user computing device (e.g., via Bluetooth) and upload the data stored in memory 256 to a server accessible to a healthcare provider via network communication available to the user computing device (e.g., Wi-Fi, 4G, 4G LTE, 5G, 5G LTE, ZigBee, etc.).

[0043] In some implementations, a user may specify how often data is collected and stored in memory 256. For example, a healthcare provider may provide sensor assembly 202 configured to collect and store patient physiological data in memory 256 every second, every 10 seconds, every minute, every 5 minutes, every 10 minutes, every hour, every day, etc. This may be advantageous to prevent sensor assembly 202 from collecting and storing excessive amounts of data, particularly in situations where periodic measurements of, for example, blood oxygen level, blood pressure, heart rate, etc., are sufficient. Additionally, adjusting the frequency at which data is collected and stored in memory 256 may extend the life of battery 224 and memory 256.

[0044] In some implementations, a user may configure the sensor assembly 202 to specify a particular time period for collecting patient physiological data. For example, a healthcare provider may want to collect or measure blood glucose levels between 7:00 AM and 10:00 AM every day. In another example, a healthcare provider may want to collect or measure blood oxygen levels once in the morning between 8:00 AM and 10:00 AM and once in the evening between 6:00 PM and 8:00 PM. Additionally, a user may configure the sensor assembly 202 to specify a data collection and storage frequency for a particular time period. The particular time period may be a particular day of the week, date, etc. For example, a healthcare provider may configure the sensor assembly 202 to measure heart rate every hour between 6:00 AM and 10:00 AM, every two hours between 10:00 AM and 6:00 PM, and every three hours between 6:00 PM and 6:00 AM. Thus, the sensor assembly 202 may be customized to collect patient physiological data depending on the patient's condition and the physiological data being monitored. This may allow a healthcare provider to more easily identify general trends, for example, without having to search for data at specific intervals for a particular time period.

[0045] In some implementations, memory 256 may store a default length of time for collecting and storing patient data and / or health-related events, for example, before establishing wireless communication with computing system 206. As described herein, a healthcare provider may provide a setting that specifies a length of time for sensor assembly 202 to collect and store patient data and / or health-related events. However, when such a setting is not provided, sensor assembly 202 may access the default length of time from memory 256 and proceed with collecting and storing patient data and / or health-related events. The default length of time may be configurable. The default length of time may vary between about 1 hour and about 30 days. In some implementations, the default length of time may be longer than 30 days.

[0046] The battery 224 has a limited charge capacity and may deplete over time. Because the battery 224 provides power for the reusable module 250, a depleted battery 224 may prevent the reusable module 250 from storing patient physiological data in the memory 256 and / or transmitting data wirelessly, for example, to the computing device 206 and / or a remote server. In some implementations, a backup power device 1500A may be used to provide power for the reusable module 250. An example of a backup power device 1500A is shown in FIG. 15A.

[0047] The backup power device 1500A may be coupled to the reusable module 250. When coupled to the reusable module 250, the backup power device 1500A described herein can provide power for the reusable module 250. The reusable module 250 can then use power from the backup power device 1500A to access patient physiological data stored in the memory 256 and wirelessly transmit the data to, for example, the computing device 206. The backup power device 1500A may be useful when a replacement disposable device is not readily available. The backup power device 1500A may include one or more electrical contacts that can contact the electrical contacts 258 of the reusable module 250, allowing power to be transferred from the backup power source 1500A to the reusable module 250. In some implementations, the backup power device 1500A can include a holder 1502 that can hold the reusable module 250 in place. In some cases, the holder 1502 can magnetically hold the reusable module 250 in place. In some cases, the backup power device 1500A may be wall mounted.

[0048] In some implementations, the backup power device 1500A has an internal power supply device and can use power from the internal power supply device to provide power for the reusable module 250. Alternatively, as described herein, the backup power device 1500A can be wall-mounted and receive power from an external power source, such as a building's power line. Power from the external power source can be used to provide power for the reusable module 250.

[0049] Additionally or alternatively, the backup power device 1500A may wirelessly supply power for the reusable module 250. Thus, the backup power device 1500A may be a device with wireless charging capability. In some implementations, the backup power device 1500B may be magnetically coupled to the sensor assembly 202, as shown in FIG. 15B . In some implementations, the backup power device 1500B may be magnetically coupled to the reusable module 250 or the disposable module 220, as shown in FIG. 15B . The backup power device 1500 may be capable of magnetically attaching to the reusable module 250 while the reusable module 250 is coupled to the disposable module 220. As described herein, the backup power device 1500 may wirelessly supply power to the reusable module 250, which can then supply the power provided by the backup power device 1500 to the disposable module 220. Thus, the backup power device 1500 may be used to provide power to the sensor assembly 202, enabling the sensor assembly 202 to collect and wirelessly transmit patient physiological data. Alternatively, as described herein, the backup power device 1500 may be attached to the disposable module 220, e.g., the housing 300, to provide power for the battery 224. Thus, the backup power device 1500 may directly provide power for the disposable module 220, which can transfer power to the reusable module 250, e.g., to process the patient physiological data and / or transmit data wirelessly, e.g., to the computing device 206.

[0050] The patient data and / or health-related events stored in memory 256 may vary in fidelity (i.e., the extent to which the patient data collected by sensor assembly 202 accurately reflects actual patient data). In some implementations, the fidelity of the patient data (e.g., heart rate) may vary based at least in part on the length of time that sensor assembly 202 is configured to collect and store the patient data and / or health-related events. For example, the longer the length of time that sensor assembly 202 is configured to collect and store the patient data and / or health-related events, the lower the fidelity of the patient data and / or health-related events may be, and the shorter the length of time that sensor assembly 202 is configured to collect and store the patient data and / or health-related events, the higher the fidelity of the patient data and / or health-related events may be. Such variations in fidelity may be caused by the limited storage capacity of memory 256.

[0051] In some implementations, fidelity may vary among various patient data or health-related events. In some situations, some patient data (e.g., blood oxygen level) may be more important than other patient data (e.g., body temperature). For example, for a patient with malaria, it may be more important to closely monitor blood oxygen level than other patient data, such as heart rate or core temperature. Thus, a healthcare provider may configure fidelity settings for the sensor assembly 202 that specify different levels of fidelity for collecting patient data and / or health-related events. In some embodiments, the data stored in the memory 256 may be transmitted to an external server. The memory 256 may transfer the entire patient physiological information to the external server or transmit only some portions of the information. For example, the memory 256 may transmit timestamp information and associated event information to the external server. In another example, the memory 256 may transmit a snapshot of the patient physiological information.

[0052] Processor 254 can be a chip that interfaces with peripheral devices, an expansion card / board, or a standalone device. For example, processor 254 is a single integrated circuit on a substrate for reusable module 250. Processor 254 can be a hardware device or a software program that manages or directs the flow of data.

[0053] The processor 254 may be in communication with the antenna 252 and memory 256 of the reusable module 250. For example, the processor 254 communicates with the antenna 252 and memory 256 of the reusable module 250 to retrieve or receive patient physiological data and transmit the data to an external device via the antenna 252. The processor 254 may be a Bluetooth® chipset. For example, the processor 254 is a SimpleLink™ Bluetooth® low energy wireless MCU (microcontroller unit) by Texas Instruments Incorporated.

[0054] The processor 254 of the reusable module 250 can be connected to the sensor 240 to receive patient physiological data from the sensor 240 when the reusable module 250 is mated with the dock 222. The processor 254 can retrieve the patient physiological data from the memory 226 of the dock 222 and transmit the data to the antenna 252. The processor 254 can be operatively connected to the antenna 252 to wirelessly transmit the patient physiological parameters to the computing device 206 using the antenna 252. The patient physiological data transmitted from the reusable module 250 to the computing device 206 can be raw patient physiological data in an analog format (e.g., 1131001310113100) or patient physiological parameters in a digital format (e.g., 60% SpO2).

[0055] The sensor 240 can transmit raw or analog patient physiological data to the processor of the reusable module 250. The processor can then perform signal processing on the raw data to calculate patient physiological parameters. It may be advantageous to have the processor 254 perform signal processing on the raw patient physiological data instead of having the computing device 206 perform signal processing on the raw data. The raw data may include a string of binary bits, and the processed data may include digital (non-binary) data (e.g., 36°C, a heart rate of 72 beats per minute, or a blood oxygen level of 96%). Therefore, transmitting digital data may require less power consumption than transmitting raw data. Therefore, using the processor 254 to perform signal processing on the raw data and transmitting the processed data (as opposed to the raw data) to the computing device 206 may extend the life of the battery 224.

[0056] The battery 224 of the dock 222 can provide power for the sensors 240. Additionally, the battery 224 can provide power for the reusable module 250. In some embodiments, the reusable module 250 may not have an internal power source for transmitting patient data to the computing device 206. When the reusable module 250 is mated with the dock 222, the processor 254 of the reusable module 250 can draw power from the battery 224. The processor 254 can process patient physiological data from the sensors 240 using power from the battery 224 and transmit the data wirelessly to the computing device 206. The battery 224 may or may not be rechargeable. The battery 224 can have wireless charging capability.

[0057] 2C shows a wiring diagram for the sensor system 202. The sensor 240 can include one or more detectors 244 and one or more emitters 242. The detectors 244 and emitters 242 can be optical. The emitters 242 can be LEDs. The detectors 244 can detect light generated by the emitters 242. The emitters 242 and detectors 244 are used to collect various types of patient physiological data, such as blood oxygen levels, heart rate, and respiratory rate. As described below, the sensor 240 can include one of several sensor elements, including, but not limited to, piezoelectric elements for acoustic sensors, electrodes for EEG sensors, electrodes for ECG sensors, etc.

[0058] The dock 222 and the reusable module 250 may include one or more electrical contacts 228 and 258, respectively. The electrical contacts 228 and 258 may establish electronic communication between the dock 222 and the reusable module 250 when the reusable module 250 is mated with the dock 222. Electrical communication between the electrical contacts 228 and 258 may allow the reusable module 250 to receive power from the battery 224 of the disposable module 220. Additionally and / or alternatively, the electrical connection between the electrical contacts 228 and 258 may enable the reusable module 250 to receive patient physiological data from the memory 226 of the dock 222. In some implementations, the reusable module 250 receives patient physiological data from the sensor 240 such that the memory 226 does not store the patient physiological data. The coupling of the reusable module 250 and the dock 222 is described further below.

[0059] Sensor Assembly 3A shows a front perspective view of an example sensor assembly 202 including a reusable module 250 and a disposable module 220. As described above, the reusable module 250 can be a pairing device capable of establishing a wireless connection with the computing device 206. The disposable module 220 can include a dock 222 and a cable 130 that couples the dock 222 to the sensor 240 (not shown).

[0060] The dock 222 may include a strap 308 coupled to the bottom of the dock 222. The strap 308 may be wrapped around a patient (e.g., wrist or arm) to removably attach the dock 222 to the patient (see FIG. 7H). The dock 222 may also include a strap loop 302 having a slot through which the strap 308 extends. The strap 308 may extend through the strap loop 302 and be wrapped around the patient to removably attach the dock 222 to the patient. The strap 308 may include a fastener 310 disposed near the distal end of the strap 308, which may interact with the strap 308 to secure the distal end of the strap 308. The fastener 310 may be located at the distal end of the strap 308 as shown in FIG. 3A. The fastener 310 may be located at other locations on the strap 308. The dock may also include a retainer 304 that holds the reusable module 250 within the dock 222 and maintains an electrical connection between the reusable module 250 and the dock 222. Additionally, the dock 222 may include a housing 300 that may house a battery 224 and a memory 226.

[0061] The dock 222 may include a cable retainer 306 disposed on a side of the dock 222. The cable retainer 306 may be dimensioned and sized to hold the cable 230. The cable retainer 306 may be removably connected to the dock 222. At least a portion of the cable retainer 306 may be flexible to facilitate insertion of the cable 230 into the cable retainer 306. The cable retainer 306 may advantageously limit movement of the cable 230 to prevent possible tangling of the cables of the various sensor assemblies. The cable retainer 306 may include a groove through which the cable 230 may extend. The groove of the cable retainer 306 may be dimensioned such that the cable 230 fits snugly within the groove, thereby limiting movement of the cable 230.

[0062] Figure 3B shows an exploded top perspective view of the sensor assembly 202 of Figure 3A. Figure 3C shows an exploded bottom perspective view of the sensor assembly 202 of Figure 3A. The dock 222 of the disposable module 220 can include a support plate 316 disposed below the dock 222. The support plate 316 can be integrated with the strap 308. The strap 308 can be modular to the support plate 316 and / or the dock 222. The dock 222 need not include the support plate 316 such that the strap 308 is directly coupled to the dock 222.

[0063] The retainer 304 of the dock 222 includes a protrusion 324 that can interact with a groove 322 of the reusable module 250. The interaction of the groove 322 and the protrusion 324 can maintain the coupling between the reusable module 250 and the dock 222. For example, when the reusable module 250 is inserted into the dock 222, the retainer 304 is pushed away from the housing 300 of the dock 222, allowing the reusable module 250 to mate with the dock 222. When the reusable module 250 is fully inserted into the dock 222, the retainer 304 can return to its original position and engage with the groove 322 of the reusable module 250. Together, the retainer 304 and the groove 322 can prevent the reusable module 250 from displacing vertically.

[0064] The retainer 304 can have a first position and a second position. In the first position, the retainer 304 is substantially perpendicular to the dock 222. In the second position, the retainer 304 is pushed away from the housing 300 so as to form an angle greater than 90° with respect to the dock 222. The retainer 304 can be positioned in the first position before the reusable module 250 is inserted into the dock 222. While the reusable module 250 is being pushed into the dock 222, the reusable module 250 interacts with the retainer 304, positioning the retainer 304 in the second position. When the reusable module 250 is fully engaged with the dock 222, the retainer 304 returns to the first position, thereby engaging the protrusion 324 with the groove 322.

[0065] The dock 222 may also include a flex circuit 320 and a cover 318 for holding the flex circuit 320. The flex circuit 320 may include the electrical contacts 228 of the dock 222, with the flex circuit 320 serving as a connection between the cable 230 and the electrical contacts 228. Thus, any information or data transmitted from the sensor 240 to the dock 222 via the cable 230 may be transmitted to the electrical contacts 228 via the flex circuit 320. Further details of the flex circuit 320 are described below.

[0066] The housing 300 of the dock 222 may include one or more slots 328 that can interact with one or more legs 326 of the reusable module 250. The slots 328 may be sized and shaped to allow the legs 326 of the reusable module 250 to slide into the slots 328. The legs 326 may slide into the slots 328 to help maintain the connection between the reusable module 250 and the dock 222. After the legs 326 are inserted into the slots 328, the legs 326 may prevent vertical displacement of the reusable module 250.

[0067] It may be advantageous to have the battery 224 within a disposable portion, such as the dock 222 or the sensor 240. Establishing wireless communication 204 and performing wireless transmissions requires a significant amount of power. If the reusable module 250 has an internal power source, the functionality of the reusable module 250 (e.g., establishing wireless communication 204 and performing wireless transmissions) may be limited by the capacity of the internal power source. In such a configuration, the reusable module 250 must be replaced when its internal power source is depleted. In the context of wireless patient monitoring, it is desirable to maintain the same paired device for each patient, as using multiple paired devices for the same patient can often lead to confusion and the need to reestablish the connection between the paired device and the display device. When the reusable module 250 has an external power source, such as the battery 224 in the dock 222, it is not necessary to replace the reusable module 250 when the battery 224 is depleted.

[0068] The battery 224 may be a zinc-air battery, which is powered by the oxidation of zinc by atmospheric oxygen. Using a zinc-air battery may be advantageous because zinc-air batteries have a higher energy density and therefore a larger capacity for a given weight or volume than other types of batteries. Furthermore, zinc-air batteries have a longer lifespan when properly sealed to exclude air. The housing 300 may include one or more openings 332 that allow air to enter and react with the battery 224. The opening or openings may be sealed prior to use to prevent air from entering the battery 224 and reacting with it, thereby reducing its capacity. Once ready for use, the seal placed over the opening or openings 332 is removed to allow the battery 224 to provide power for the reusable module 250. The housing 300 may include a gasket 330 to seal the battery 330 from air. The gasket 330 may further increase the capacity of the battery 224.

[0069] Having a disposable element (e.g., disposable module 220) as the power source for the reusable module 250 can address the above problem by eliminating the need to replace the reusable module 250. In this configuration, only the dock 222 or the sensor 240 needs to be replaced when the battery 224 is depleted. This configuration can be advantageous in reducing operational costs because the cost of replacing the dock 222 or the sensor 240 is much lower than the cost of replacing the reusable module 250. The sensor 240 may include a battery 224 that provides power to the reusable module 250. Both the sensor 240 and the dock 222 can include a battery 224. The reusable module 250 can include a battery consumption priority setting to receive power from the sensor 240 first, followed by power from the dock 222.

[0070] The dock 222 may include a battery circuit 314 in contact with the battery 224. The battery circuit 314 may be in contact with the flex circuit 320. When the reusable module 250 is mated with the dock 222, the electrical contacts 258 may be in contact with the electrical contacts 228 of the flex circuit 320, allowing the reusable module 250 to receive power from the battery 224 via the flex circuit 320.

[0071] The dock 222 may include an opening 362 and one or more supports 360. The one or more supports 360 may be formed on sides of the opening 362 and may extend over a substantial portion of the opening 362. The supports 360 may be arcuate. The supports 360 may extend the entire length of the opening 362. A cover 318 for the flex circuit 320 may be positioned over the opening 362 to hold the flex circuit 320 over the opening 362.

[0072] The dock 222 may include a slot dimensioned to hold the reusable module 250 when the sensor assembly 202 is in use. The reusable module 250 may be disposed between the housing 300 and the retainer 304. The slot in the dock 222 may include one or more arcuate surfaces or one or more squared corners. The slot in the dock 222 may be substantially rectangular or circular in formation. The slot may have substantially the same size, shape, and / or dimensions as the reusable module 250.

[0073] The reusable module 250 may include one or more electrical contacts 258. The electrical contacts 258 may be located on a bottom surface of the reusable module 250. The electrical contacts 258 may be substantially rectangular or circular in shape. The electrical contacts 258 may establish contact with electrical contacts 228 of the dock 222 when the reusable module 250 is mated with the dock 222. The contact between the electrical contacts 228 and the electrical contacts 258 may allow information or data to be transmitted between the reusable module 250 and the dock 222 of the disposable module 220.

[0074] As disclosed herein, the battery 224 may be a zinc-air battery that is powered by the oxidation of zinc by atmospheric oxygen. An opening 332 formed on the housing 300 allows air to enter the battery 224 and react with it. The battery 224 then provides power for the disposable module 220 and the reusable module 250. However, the opening 332 may optionally be covered with a blanket, cloth, or the like, to prevent air from entering through the opening 332 and reacting with the battery 224. Thus, when the opening 332 is covered, the power source for the disposable module 220 and the reusable module 250 may be shut off.

[0075] As shown in FIG. 3D , the housing 300 can include one or more recesses 331, such as grooves, that can facilitate air ingress through openings 332. The recesses 331 can be formed on the top surface of the housing 300 to form openings that allow air flow. The openings 332 can be formed on the inner surface of the recesses 331. The inner surface of the recesses 331 is spaced at least a predetermined distance from the top surface of the housing 300, so that the openings 332 remain uncovered and exposed to the atmosphere even when the housing is covered. The housing can have a single groove or multiple recesses, such as indentations or notches of any shape or size.

[0076] The number, size, orientation, or location of the grooves 331 may vary depending on the size of the housing 300 of the reusable module 250. The grooves 331 may be oriented so that they collectively form a shape on the housing 300. The grooves 331 may be oriented to be triangular (as shown in FIG. 3D ), rectangular, pentagonal, hexagonal, etc. The cross-sectional shape of the grooves 331 may be circular, triangular, rectangular, etc. In some examples, the grooves 331 may extend to one or more edges of the housing 300, such that even when the top surface of the housing 300 is covered, the grooves 331 that extend to the edges of the housing 300 can leave the openings 332 exposed to the atmosphere.

[0077] 4 illustrates an example of a sensor assembly 202, generally identified by the reference numeral 202A. Portions, components, and features of the sensor assembly 202A are identified using the same reference numerals as the corresponding portions, components, and features of the sensor assembly 202, except that the reference numeral for the sensor assembly 202A has the letter "A" appended to it. The illustrated example includes a disposable module 220A and a reusable module 250A coupled together.

[0078] The sensor assembly 202A can include a sensor 240A. The sensor 240A can be an O3 sensor that can be attached to the patient's forehead. The sensor assembly 202A can include a cable 230A that couples the sensor 240A to a dock 222A of the disposable module 220A. The cable 230A can be flat or rounded. As described above, the sensor 240A can include one or more batteries that can provide power for the reusable module 250A. Mating the dock 222A and the reusable module 250A can facilitate electronic communication between the dock 222A and the reusable module 250A. The dock 222A can include a housing 300A that includes a retainer member 304A. Depressing the retainer member 304A can allow the reusable module 250A to be coupled to or detached from the dock 222A.

[0079] 5 illustrates an example of a sensor assembly 202, generally identified by the reference numeral 202B. Portions, components, and features of the sensor assembly 202B are identified using the same reference numerals as the corresponding portions, components, and features of the sensor assembly 202, except that the reference numeral for the sensor assembly 202B has the letter "B" appended to it. The illustrated example includes a disposable module 220B and a reusable module 250B coupled together.

[0080] The sensor assembly 202B may include a sensor 240B. The sensor 240B may be a RAM sensor attached to the patient's neck. The sensor 240B may be an ECG sensor that may be attached to the patient's chest or abdominal region. The dock 222B may include a housing 300B and a retainer member 304B. The housing 300B may include one or more extenders 500 that may extend from a main body of the housing 300B toward the retainer member 304B. The reusable module 250B may include cutouts that correspond to the one or more extenders 500. When the reusable module 250B is coupled to the dock 222B, the extenders 500 may extend over the cutouts of the reusable module 250B to prevent the reusable module 250B from being removed from the dock 222B.

[0081] Flexible Circuit FIG. 6A shows a perspective view of the flex circuit 320. The flex circuit 320 can include one or more elongate members 600, each of which can include a tip 602 and a body 608. The electrical contacts 228 can be disposed on the one or more elongate members 600. The elongate members 600 can extend distally from the body 608. The tip 602 can be located at the distal end of the elongate member 600 of the flex circuit 320. The elongate members 600 can be flat or arcuate, as shown in FIG. 6A. The elongate members 600 can be arcuate due to interaction of the support 360 and the cover 318 with the elongate member 600. The elongate members 600 can include one or more substantially flat portions and / or one or more arcuate portions. Each of the one or more tips 602 can correspond to each of the one or more elongate members 600 of the flex circuit 320. Some of the elongate members 600 may not have electrical contacts 228. The flex circuit 320 may include the same or different numbers of elongate members 600 and tips 602. The flex circuit 320 may include one or more openings 604 that couple the flex circuit 320 to the dock 222.

[0082] 6C and 6D, the tip 602 of the elongated member 600 can be positioned below the cover 318 while the elongated member 600 is supported by the support 360. The tip 602 can be wedged below the cover 318, allowing the elongated member 600 to maintain an arcuate shape above the support 360.

[0083] 6B shows a bottom view of the flex circuit 320. The flex circuit 320 may include one or more electrical contacts 606 that may connect to the cable 230 and the battery circuit 314 (see FIGS. 3A and 3C). Thus, power from the battery 224 may be transmitted via the electrical contacts 606 of the flex circuit 320 to the electrical contacts 228 of the dock 222. Additionally, the electrical contacts 606 may establish a connection between the electrical contacts 228 and the sensor 240 via the cable 230.

[0084] The number of elongate members 600 can correspond to the number of electrical contacts 258 of reusable module 250 (see FIG. 3C ). For example, reusable module 250 has six electrical contacts 258, and flex circuit 320 has six fingers, each including an electrical contact 228. The number of electrical contacts 258 of reusable module 250 can be different from the number of elongate members 600 of flex circuit 320. For example, flex circuit 320 can include six elongate members 600, each with a corresponding electrical contact 310 a, while reusable module 250 has only four electrical contacts 258. The number of electrical contacts 258 of reusable module 250 can be different from or the same as the number of electrical contacts 228 disposed on elongate members 600 of flex circuit 320.

[0085] Each of the elongated members 600 of the flex circuit 320 can include an arcuate portion having a first curvature. The arcuate portion of the elongated member 600 can be positioned above the opening 362 of the dock 222. One or more electrical contacts 228 of the flex circuit 320 can be disposed above a portion of the elongated member 600 of the flex circuit 320. For example, one or more electrical contacts 228 are located at an apex of each of the elongated members 600 of the flex circuit 320. In another example, the entire top surface of each of the elongated members 600 defines the electrical contacts 228. The elongated members 600 of the flex circuit 320 can be configured such that an apex of the arcuate portion of the elongated member 600 of the flex circuit 320 is located a predetermined distance from the opening 362 of the dock 222. The apex of the elongate member 600 of the flex circuit 320 can face away from the opening 362 of the dock 222 such that the arcuate portion of the elongate member 600 defines a concave surface facing the opening of the dock 222. The apex of the elongate member 600 can be arcuate in shape or can be substantially flat.

[0086] It may be advantageous to have the elongated member 600 of the flex circuit 320 include a curved portion that points upward (e.g., concave downward) away from the opening 362 of the dock 222. Such a configuration may allow the elongated member 600 to act as a spring that exerts a resilient upward force when pushed downward by the reusable module 250. Such an upward force exerted by the elongated member 600 may allow the electrical contacts 228, 258 of the dock 222 and the reusable module 250, respectively, to maintain proper contact therebetween.

[0087] The elongate members 600 of the flex circuit 320 can have different curvatures. For example, a first elongate member of the flex circuit 320 has a first curvature, while a second elongate member of the flex circuit 320 has a second curvature. The first curvature of the first elongate member and the second curvature of the second elongate member can be the same or different. The first curvature of the first elongate member can be greater than, less than, or equal to the second curvature of the second elongate member.

[0088] The elongated member 600 of the flex circuit 320 may not have any arcuate portions in its rest position. The elongated member 600 of the flex circuit 320 may be substantially straight before being installed on the dock 222. The elongated member 600 may be straight or curved. The elongated member 600 of the flex circuit 320 may include two or more straight portions.

[0089] The elongated members 600 of the flex circuit 320 can be flexible or inflexible. The flex circuit 320 can be positioned on the dock 222 such that the elongated members 600 are positioned above one or more supports 360 of the dock 222. The elongated members 600 can extend distally away from a body 608 of the flex circuit 320. The flex circuit 320 can include two or more elongated members 600. The flex circuit 320 can include one or more flexible elongated members 600. Some of the elongated members 600 can be flexible, while other elongated members 600 can be inflexible.

[0090] As described above, the dock 222 can include an opening 362 over which the elongated member 600 of the flex circuit 320 can extend. The dock 222 can include one or more supports 360 sized and shaped to support the elongated member 600 of the flex circuit 320. When the flex circuit 320 is installed on the dock 222, the supports 360 can form a surface against which the elongated member 600 of the flex circuit 320 can be positioned.

[0091] The supports 360 of the dock 222 can be curved and can define the curvature of the arcuate portion of the elongate member 600. The supports 360 can be arcuate. It may be advantageous to have a support corresponding to each of the elongate members 600 of the flex circuit 320. For example, the dock 222 has six independent supports 360 associated with each of the six elongate members 600 of the flex circuit 320. Such a configuration allows each corresponding elongate member 600 and support 360 of the dock 222 to move independently of the other elongate members 600 and supports 300, rather than all of the elongate members 600 and supports 360 moving simultaneously. Such a configuration makes it easier to insert the reusable module 250 into the slot 940 of the dock 222. Furthermore, this can enable interoperability of docks 222 and reusable modules 250 having various height configurations for the electrical contacts 258.

[0092] It may be advantageous for the support 360 for the flex circuit 320 to include a curved portion (e.g., a downwardly concave portion) that curves upwardly away from the bottom of the dock 222. Such a configuration can allow the support to act as a spring that applies a resilient upward force when pushed downwardly by the reusable module 250. Such an upward force can allow the respective electrical contacts 228, 258 of the dock 222 and the reusable module 250 to maintain proper contact therebetween. The support 360 can include a first upwardly concave portion, a second upwardly concave portion, and a third downwardly concave portion. The support 360 may also include a first upwardly concave portion and a second upwardly concave portion. The support 360 can include one or more inflection points, defined as points where the support 360 changes from concave to convex or from convex to concave. The support 360 can also include one or more straight portions.

[0093] Support 360 may also apply sufficient force to push reusable module 250 away from dock 222 when retainer member 304 is pulled away from reusable module 250. Support 360 may also push reusable module 250 away from dock 222 when retainer member 304 is in its second position. When retainer 304 is no longer engaged with groove 322 of reusable module 250, as described above, it may no longer apply a force counteracting the force generated by support 360 that enables support 360 to push reusable module 250 away from dock 222.

[0094] Support 360 can have a length that is greater than, less than, or equal to the length of elongate member 600 of flex circuit 320. Support 360 can have a width that is greater than, less than, or equal to the width of elongate member 600. Support 360 can have a thickness that is greater than, less than, or equal to the thickness of elongate member 600 to provide sufficient mechanical support and enable it to withstand downward forces applied to elongate member 600 and support 360 by reusable module 250. The interactions between elongate member 600, support 360, and reusable module 250 are further described below.

[0095] The support 360 can be made of the same material as the dock 222 or can be made of a different material.

[0096] The body 608 of the flex circuit 320 can be positioned below the housing 300 of the dock 222. The body 608 can be connected to the cable 230 connected to the dock 222, thereby enabling the flex circuit 320 to transmit health monitoring data from the sensor 240 to the electrical contacts 606 of the flex circuit 320.

[0097] 6C and 6D illustrate a change in the configuration of the flex circuit 320. Inserting the reusable module 250 into the slot 940 of the dock 222 can reposition the tip 602 of the flex circuit 320 by engaging the reusable module 250 with the dock 222. FIGS. 6C and 6D illustrate the relative position of the tip 602 before and after the reusable module 250 is mated with the dock 222. The relative position of the tip 602 before the reusable module 250 is inserted into the dock 222 is indicated by L1. When the reusable module 250 is inserted into the slot 940 of the dock 222, the reusable module 250 can apply a downward force (denoted as F) to the arcuate portion of the elongate member 600 and the support 360. This downward force F can move the arcuate portion and the support 360 downward. This downward movement of elongate member 600 and support 360 can cause tip 602 to move distally along an axis defined by elongate member 600 of flex circuit 320. Specifically, such downward movement can change the relative position of tip 602 from L1 to L2, where L2 is greater than L1.

[0098] 6C and 6D illustrate another modification to the configuration of the flex circuit 320. When the reusable module 250 is inserted into the dock 222, the engagement between the reusable module 250 and the dock 222 can change the position of the tip 602 of the flex circuit 320. The relative height difference between the apex of the arcuate portion of the elongate member 600 and the body 608 before the reusable module 250 is inserted is indicated by H1. When the reusable module 250 is inserted into the dock 222, the reusable module 250 can apply a downward force (indicated as F) to the arcuate portion of the elongate member 600 and the support 360. This downward force F can move the arcuate portion and the support 360 downward. Such downward movement can change the relative height difference between the apex of the arcuate portion of the elongate member 600 and the body 608 from H1 to H2, where H2 is less than H1. The relative difference in height between the apex of the arcuate portion of the elongate member 600 and the body 608 can be changed while the relative position of the tip 602 is not changed from L1 to L2, or vice versa.

[0099] The downward force F in a first direction can cause the support 360 of the dock 222 to apply a counter force in a second direction. The second direction of the counter force can be opposite to the first direction of the downward force F. Specifically, the counter force from the support 360 can be directed upward away from the dock 222. The support 360 can act as a spring, whereby the magnitude of the counter force increases as the support 360 moves further downward from its natural position (e.g., from H1 to H2). The direction of F and the counter force can be opposite to each other. The magnitude of the counter force is smaller than the downward force F, thereby allowing the support 360 to move downward and insert the reusable module 250 into the slot 940 of the dock 222. The magnitude of the downward force F generated by the reusable module 250 may correlate with a change in the relative height difference between the apex of the elongated member 600 and the body 608 (e.g., a change from H1 to H2) and a change in the position of the tip 602 (e.g., a change from L1 to L2).

[0100] The elongated member 600 of the flex circuit 320 can have a first degree of curvature before the reusable module 250 is inserted into the dock 222. The elongated member 600 can have a second degree of curvature after the reusable module is inserted into the dock 222. The first degree of curvature of the elongated member 600 can be greater than, less than, or equal to the second degree of curvature. The first degree of curvature can correspond to a first position (e.g., L1) of the tip 602. The second degree of curvature can correspond to a second position (e.g., L2) of the tip 602. Furthermore, the first degree of curvature can correspond to a first position (e.g., H1) of the apex of the elongated member 600. The second degree of curvature can correspond to a second position (e.g., H2) of the apex of the elongated member 600.

[0101] The reaction force exerted by the support 360 can maintain sufficient contact between the electrical contacts 310a of the dock 222 and the electrical contacts 310b of the reusable module 250 to allow electrical signals to be transmitted between the contacts.

[0102] Mounting mechanism 7A-7I show various examples of attachment mechanisms for the disposable module 220 of the sensor assembly 202. FIG.

[0103] 7A-7C , the dock 222 can be coupled to a first strap 700 and a second strap 702. The first strap 700 and the second strap 702 can be mechanically coupled to the dock 222. The straps 700, 702 can be removably coupled to the dock 222. Alternatively, the straps 700, 702 can be integral with the dock 222. The second strap 702 can include one or more openings 704. The first strap 700 can include a fastener 706 configured to secure the second strap 702 to the first strap 700. The opening 704 can be dimensioned to receive the fastener 706. The first strap 700 can be inserted through one of the openings 704 to removably attach the dock 222 to the patient. The straps 700, 702 can have various thicknesses, lengths, and flexibilities. The straps 700, 702 may be stretchable. The first strap 700 may include one or more openings 704, while the second strap 702 includes a fastener 706.

[0104] A distal end of the first strap 700 can be inserted into one of the openings 704 of the second strap 702. A fastener 706 of the first strap 700 can be inserted into one of the openings 704 of the second strap 702. Interaction of the fastener 706 with the opening 704 can removably secure the dock 222 as shown in FIGS. 7B and 7C .

[0105] In some implementations, the sensor assembly 202 can be coupled to a medical band 750, as shown in FIGS. 7J and 7K. The band 750 may include any of the straps disclosed herein or any suitable strap or band for attaching the sensor assembly 202 to a patient. The sensor assembly 202 may not include a strap (e.g., strap 308 shown in FIG. 3B), and the dock 222 of the disposable module 220 may be coupled to the band 750. In some implementations, the dock 222 may include two strap loops (e.g., strap loop 302), and the band 750 may be routed through the strap loops to couple the sensor assembly 202 to the band 750. The band securing mechanism can be non-removable once attached to the patient, requiring the band to be cut for removal. The band can include a tamper detection mechanism and an alarm to indicate if the band has been improperly removed or tampered with. The band may include patient identification information 752, a barcode 754, and medication information 756. The patient identification information 752 may include the patient's name, contact information, physician information, etc. The barcode 754 may represent the patient identification information 752 and may serve as an identifier that can be used to associate the patient with one or more devices (e.g., patient monitoring devices). The barcode 754 may, in some examples, be a QR code. The medication information 756 may identify, for example, the patient's allergy information, medications given to the patient, dosage information, etc. In some implementations, the band 750 may include an RFID (radio frequency identification) tag that can allow the patient and / or family members to pass through a security checkpoint. In some cases, the sensor assembly 202 may include one or more physiological sensors attached to the wrist and measuring parameters at the wrist. In some cases, the band 750 may include a location device that can identify the patient's exact or approximate location.

[0106] By coupling the sensor assembly 202 to, for example, a medical band 750, the number of items worn by the patient can be reduced. For example, if the patient is still wearing a medical wearable device (e.g., a wearable fitness tracker, a smart health watch, a wearable ECG monitor, a wearable blood pressure monitor, etc.), the sensor assembly 202 may be coupled (e.g., attached via adhesive or coupled via a strap loop) to the medical wearable device. Additionally or alternatively, the sensor assembly 202 may be coupled to a non-medical device, such as a conventional watch or jewelry that may be worn on the wrist or other part of the patient's body (e.g., ankle, neck, arm, leg, etc.).

[0107] In some implementations, at least one of the patient identification information 752, the barcode 754, or the medication information 756 may be separately printed and attached, for example, to the strap 308 shown in FIG. 3B of the sensor assembly 202. This configuration may eliminate the need, for example, to remove the strap 308 from the dock 222 of the sensor assembly 202 and attach the band 750 to the dock 220 (e.g., wrap the band 750 around the strap loop 302 of the dock 222).

[0108] In some implementations, the appearance of the band 750 may include one or more light sources (e.g., light-emitting diodes) that can be activated (e.g., switched on and off) to reflect, for example, changes in the patient's condition. In some cases, different colors can be used to indicate different conditions for each patient. For example, green may represent good and / or excellent patient conditions, while yellow and red may represent suboptimal and critical conditions, respectively. The band 750 may include a processor and wireless communications module that receives physiological data from the sensor assembly 202 of a patient wearing the band 750 and causes the light source to change its appearance based at least in part on the physiological data. In some implementations, the processor of the band 750 may receive patient status data (e.g., very good, good, suboptimal, poor, critical, etc.) from the sensor assembly 202 (rather than receiving raw or processed patient physiological data) and change the display of the light source based on the patient status data. This may be advantageous when the patient and / or healthcare provider (or family member) do not have access to the patient's physiological data. By monitoring the appearance (eg, color) of the band 750, the patient, healthcare provider, and family can easily recognize and monitor the patient's condition.

[0109] In some cases, the identifier can be used as a security tag, causing an alarm system to trigger an alert if the identifier passes through a geofence location. For example, a hospital or healthcare provider facility may have RF scanners located at various locations. Such RF scanners may be installed at the main entrance of the healthcare provider facility or at several checkpoints, such as an emergency room, intensive care unit, maternity ward, or neonatal care unit. The RF scanners may detect the identifier of a medical band attached to the sensor assembly 202 and trigger an alarm. Such use of the identifier as a security tag can prevent unauthorized and / or accidental movement of patients, removal or movement of a medical band with the sensor assembly 202, leaving the hospital without returning the sensor device, etc.

[0110] FIG. 7D shows the dock 222 of the disposable module 220 coupled to yet another example of an attachment mechanism. The dock 222 can be coupled to an extension 708 that extends away from the disposable module 220. For example, as shown in FIG. 7D, the disposable module 220 can be placed on the hand, with the extension 708 extending toward the patient's wrist. The extender 708 can include a strap 700A that can be wrapped around the wrist to secure the disposable module 220 and extension 708 to the wrist. The strap 700A can include a fastener 706A that can attach the strap 700A to a top surface of the extension 708. The fastener 706A can be disposed at a distal or proximal end of the strap 700A. The fastener 706A can be attached to a top or bottom surface of the strap 700A. The fastener 706A can incorporate one of the following mechanisms, including a hook-and-loop system, Velcro, a button, a snap, a magnet, etc.

[0111] FIG. 7E illustrates another example of an attachment mechanism for the disposable module 220. As shown, the dock 222 can be coupled to a strap 700B. A first proximal end of the strap 700B can be attached to the dock 222, while a second distal end of the strap 700B can extend away from the dock 222. The distal end of the strap 700B can include a fastener 706B. The strap 700B can secure the dock 222 to a patient's wrist by wrapping the second distal end around the wrist. The distal end of the strap 700B can be secured by wrapping it above or below the proximal end of the strap 700B. After wrapping the distal end of the strap 700B around the first proximal end of the strap 700B, the fastener 706B can be used to secure the distal end of the strap 700B. The fastener 706B may incorporate one of the following mechanisms, including, but not limited to, a hook and loop system, Velcro, buttons, snaps, and / or magnets.

[0112] FIG. 7F illustrates yet another example of an attachment mechanism for the sensor assembly 202. The sensor assembly 202 can be coupled to an extender 708A that includes a hook 710. The extender 708A can extend away from the dock 222 of the sensor assembly 202, with the hook 710 coupled to a distal end of the extender 708A. The hook 710 can be wrapped around a strap 700C such that the extender 708A and the dock 222 are held substantially in place relative to the patient's wrist. The strap 700C can be modular. The strap 700C can be removably connected to or secured to the hook 710 of the extender 708A. The strap 700C can be a flexible band that can be securely wrapped around the patient's wrist, as shown in FIG. 7F.

[0113] FIG. 7G illustrates yet another example of an attachment mechanism for the sensor assembly 202. The dock 222 may include a strap 308 extending from a first side of the dock 222 and dimensioned to be wrapped around a patient's wrist in a first direction, and a strap loop 302 extending from a second side of the dock 222. The strap 308 may include a fastener 310 disposed near its distal end. The strap 308 may be wrapped around a patient's wrist and threaded through the strap loop 302 of the dock 222. After threading the strap 308 through the strap loop 302 of the dock 222, the strap 308 may be wrapped around the strap loop 302 and wrapped around the wrist in a second direction. The first direction in which the strap 308 is wrapped around the wrist may be clockwise or counterclockwise. The second direction in which the strap 308 is wrapped around the wrist may be clockwise or counterclockwise. FIG. 7H illustrates the sensor assembly 202 of FIG. 3A secured to a patient's wrist.

[0114] FIG. 7I shows yet another example of an attachment mechanism for the sensor assembly 202. The dock 222 and sensor 240 can be coupled to a glove 712. When the glove 712 is placed on a patient's hand, the sensor 240 of the sensor assembly 202 can be placed on one of the fingertips. The dock 222 can be attached to the top of the glove 712 as shown in FIG. 7I. The sensor 240 of the sensor assembly 202 can be assembled inside or outside a finger of the glove 712. The sensor 240 can be integrated with the finger of the glove 712. The cable 230 of the sensor assembly 202 can be integrated with the glove 712.

[0115] Dongle and Pairing Given the time demands on clinicians and the number of patients and patient monitoring devices in a busy hospital, manual interaction to establish a connection between a computing device 206 (e.g., a mobile patient monitoring display device) and a reusable module 250 can be tedious. In some cases, the time required to manually interact with a patient monitoring device to establish a connection with a pairing device can, in some cases, jeopardize the patient's health, especially in emergency situations. For at least the above reasons, it is advantageous for computing devices 206, such as bedside patient monitors, central monitoring stations, and other devices, to have the ability to detect the presence of a reusable module 250 in their vicinity and establish wireless communication with the reusable module 250.

[0116] 8A-8C show various views of a dongle 800 connected to a computing device 206. The dongle 800 may include a body 802 and a connector 804 coupled to the body 802 via a cable 806. The connector 804 may be connected to the computing device 206 to enable transmission between the dongle 800 and the computing device 206. The cable 806 may include one or more conductive wires that may transmit data and / or power between the body 802 and the connector 804. The body 802 of the dongle 800 may be removably attached to the computing device 206. The body 802 may receive power from the computing device 206 via the connector 804 and the cable 806.

[0117] When the dongle 800 is connected to the computing device 206 via the connector 804, the computing device 206 can automatically detect the connector 804. The computing device 206 can determine the type of connector 804 and automatically change its settings. The settings may include, but are not limited to, display settings for the display 208, display settings for the computing device 206 (e.g., color of light used to indicate pairing or communication status), communication protocol settings (e.g., type of wireless communication utilized), communication signal settings (e.g., variable communication signal type or strength based on different types of communication), etc. Furthermore, the settings for the dongle 800 can be changed to accommodate different types of computing devices 206 and their display 208. Such settings can include display settings (e.g., color or message indicating communication / pairing status), communication signal settings (e.g., frequency of wireless signal used), communication protocol settings (e.g., type of wireless communication utilized), etc.

[0118] The computing device 206 can receive the processed physiological parameter data and display it on a display screen. This capability can be advantageous because it can reduce the amount of processing power required by the computing device 206. As described above, the reusable module 250 can perform signal processing on the raw patient physiological data collected by the sensors 240 to calculate the patient physiological parameters. Thus, the data transmitted from the reusable module 250 to the computing device 206 via the body 802 includes patient physiological parameters that do not require further data processing.

[0119] The reusable module 250 can transmit the patient physiological parameters at a lower resolution, and the dongle 800 can fill in the data using various methods. For example, the dongle 800 can use various types of averaging to fill in the data transmitted from the reusable module 250. The reusable module 250 can, for example, send waveform data at a lower resolution, and the dongle 800 can provide a higher resolution waveform. This feature can also extend the life of the battery 224 of the disposable module 220.

[0120] The body 802 of the dongle 800 may include a transceiver or receiver and a communication module for communicatively coupling the computing device 206 to other patient monitoring devices, such as the reusable module 250. When the reusable module 250 is in sufficient proximity, the body 802 may communicate with and identify the reusable module 250. The body 802 may include a radio frequency identification (RFID) reader, while the reusable module 250 may include an embedded RFID chip that contains identification information unique to the reusable module 250. The RFID reader of the body 802 may identify the embedded RFID chip within the reusable module 250 and establish wireless communication 204 between the reusable module 250 and the body 802. The body 802 may include a transceiver that complies with one or more short-range wireless communication standards, such as Bluetooth®. Other types of wireless communication protocols may be utilized to establish communication and transfer data between the dongle 800 and the reusable module 250.

[0121] The body 802 may include a groove 808 dimensioned to receive a portion of the reusable module 250. The groove 808 may indicate to medical personnel where to place the reusable module 250 in order to associate (e.g., pair) the reusable module 250 with the computing device 206.

[0122] The dongle 800 may include a holder 850 that can hold the reusable module 250 when not in use. The holder 850 may be detachable from the dongle 800 as shown in FIG. 8B . The holder 850 may include a surface sized and shaped to engage a surface of the reusable module 250 to assist in holding the reusable module 250. The holder 850 may hold the reusable module 250 using a magnet. The holder 850 may be attached onto the computing device 206 via a variety of mechanisms, including, but not limited to, adhesive, Velcro, magnets, etc.

[0123] 9A-9C illustrate the process of pairing a reusable module 250 with a computing device 206 using a dongle 800. Wireless communication between the reusable module 250 and the computing device 206 can be initiated by mating the connector 804 of the dongle 800 with the computing device 206 and placing the reusable module 250 within a distance from the body 802 of the dongle 800. The reusable module 250 may or may not require physical contact with the body 802 to transfer its identification information to the dongle 800.

[0124] When the reusable module 250 is brought sufficiently close to the body 802 of the dongle 800, the body 802 may receive information from the reusable module 250 that may identify the reusable module 250 to the computing device 206, for example, using RFID technology. The identification information may be a token ID tag that is specific or unique to the reusable module 250. The identification information may include Bluetooth parameters of the reusable module 250. Other types of identification mechanisms may be used to enable the computing device 206 to identify and associate with the reusable module 250.

[0125] The identification information of the reusable module 250 can be stored in the memory 256. The identification information may be hardwired to the memory 256 or may be programmable. The identification information may include pairing parameters (e.g., a paired device ID) unique to the reusable module 250. The identification information may also be unique to the patient to whom the reusable module is assigned. The identification information of the reusable module 250 may include, for example, information about the paired device, information about the sensor 240 to which the reusable module 250 is operatively connected, or other information such as a code or other indicator for initiating a predetermined action to be performed by the computing device 206. Additionally and / or alternatively, the identification information of the reusable module 250 can be generated using physiological data collected by the sensor 240 of the sensor assembly 202.

[0126] The body 802 of the dongle 800 may include an RFID reader. The RFID reader may communicatively couple the computing device 206 to other patient monitoring devices, such as the reusable module 250. As shown in FIG. 9B , when the reusable module 250 is in proximity to the body 802, the RFID reader of the body 802 may receive identification information from the reusable module 250. After the body 802 receives the identification information, it may transmit the identification information to the computing device 206 via the cable 806 and the connector 804.

[0127] The computing device 206 can associate the reusable module 250 with the computing device 206 using the identification information. For example, the Bluetooth® parameters of the reusable module 250 can be used to associate the reusable module with the computing device 206. Once associated, the reusable module 250 can connect to the computing device 206 using pairing parameters (e.g., Bluetooth® parameters) included in the identification information. The computing device 206 can identify the reusable module 250 and enable wireless communication 204 with the reusable module 250 using the Bluetooth® parameters that the computing device 206 received from the reusable module 250. After establishing a connection with the computing device 206, the reusable module 250 can communicate with the dongle 800 and the computing device 206 via Bluetooth® transmissions. Other types or standards of wireless communication can be used, including, for example, ultrasound, near field communication (NFC), etc. If multiple reusable modules 250 are in proximity to the computing device 206, a priority scheme or user confirmation may be used to determine which reusable module 250 is accommodated.

[0128] The reusable module 250 can use NFC to provide instructions that program the dongle 800 to take specific actions in specific situations. The NFC communication circuitry of the reusable module 250 can have associated memory that can have read / write capabilities. For example, the reusable module 250 can use NFC to indicate how long the dongle 800 should wait before removing the pairing parameters (“give up”). In another example, the reusable module 250 can use NFC to indicate when the dongle 800 is refused to remove the pairing parameters (“don't give up”). NFC can be used to allow the dongle 800 to associate with one or multiple reusable modules 250 simultaneously.

[0129] The dongle 800 can receive various types of information from the reusable module 250 using NFC. The dongle 800 can receive information related to the NFC components of the reusable module 250 to determine the sensor type, patient type, patient information, physician information, hospital information, authorized uses, authorized supplies, authorized manufacturers, emitter wavelength, or instructions for use or lifespan of the reusable module 250, parameters the reusable module 250 can measure, and the like. For example, the dongle 800 can receive information via NFC to determine that a particular reusable module 250 is designed to work with the sensor assembly 202. The dongle 800 can also write back using NFC. For example, the dongle 800 can provide programming information to the reusable module 250 via NFC. The dongle 800 can also write sensor usage information to the reusable module 250. For example, the reusable module 250 may only be usable a certain number of times before it must be discarded to maintain quality. This information can be written to the reusable module 250 via NFC communication.

[0130] It should be understood throughout this disclosure that the dongle 800 may be incorporated directly into the computing device 206. For example, the dongle 800 may be incorporated into the circuitry of the computing device 206 such that the dongle 800 and the computing device 206 are located within the same housing. In another example, the dongle 800 and the computing device 206 are located within the same housing, but the dongle 800 is not incorporated into the circuitry of the computing device 206. The dongle 800 may be incorporated into the computing device 206 such that the dongle 800 is located near the outer housing or body of the computing device 206. Such a configuration may enable the reusable module 250 to easily establish wireless communication 204 with the dongle 800. Integrating the dongle 800 directly into the computing device 206 may prevent connection issues that may arise between the dongle 800 and the computing device 206.

[0131] After the computing device 206 is associated with the reusable module 250, the computing device 206 may send a signal to the reusable module 250 indicating that the reusable module 250 has associated with the computing device 206. Various types of notifications may be generated when the reusable module 250 successfully establishes wireless communication 204 with the computing device 206. The notifications may be generated by the computing device 206, by the reusable module 250, or by both.

[0132] The computing device 206 may provide an audible notification or a visual notification on the display 208. For example, the computing device 206 may output a certain pattern of beeps or a predetermined melody that the pairing was successful. In another example, the computing device may output an audible message such as, "SpO2 sensor number 1234 has successfully paired with patient monitoring device A 123." The visual notification may include a flashing LED on the display 208. Another example of a visual notification may be displaying some form of text on the display 208, such as "Pairing successful." The reusable module 250 has one or more LEDs that indicate the status of the wireless communication 204 with the computing device 206. For example, the reusable module 250 may include a red LED that indicates that wireless communication 204 has not been established between the reusable module 250 and the computing device 206. In another example, the reusable module 250 may include a blue LED that indicates that the reusable module 250 has established wireless communication 204 with the computing device 206. A blinking green LED may be used to indicate that computing device 206 is waiting for reusable module 250 to establish wireless communication 204 with computing device 206. Different color LEDs and different schemes may be used to indicate different statuses of wireless communication 204 between reusable module 250 and computing device 206.

[0133] After receiving the pairing parameters from the reusable module 250, the computing device 206 may wait a predetermined period of time for the reusable module 250 to establish wireless communication 204 (e.g., a Bluetooth connection). If wireless communication 204 is not established within the predetermined period of time, the pairing parameters may expire and the reusable module 250 may again need to resend the pairing parameters to the computing device 206. The predetermined period of time may be modified.

[0134] After the computing device 206 receives the pairing parameters from the reusable module 250, the reusable module 250 can be mated with the dock 222, as shown in FIG. 9C. After mating with the dock 222, the reusable module 250 can draw power from the battery 224 to establish wireless communication 204 with the computing device 206. The reusable module 250 can perform signal processing on the raw data using the power drawn from the battery 224 to calculate the physiological parameters. After the physiological parameters are determined, the reusable module 250 can transmit the physiological parameters to the computing device 206 via wireless communication 204 using power from the battery.

[0135] The computing device 206 can receive patient data, including patient physiological parameters, from the reusable module 250 and display the parameters on the display 208. The computing device 206 can receive the patient data via the body 802 of the dongle 800. In other words, the body 802 of the dongle 800 can receive the patient physiological parameters from the reusable module 250 and then transmit the parameters to the computing device 206. As described above, Bluetooth® can be used to transmit patient data between the reusable module 250 and the computing device 206 (or the body 802). For example, the reusable module 250 operably connected to an SpO2 sensor can establish Bluetooth® communication with the computing device 206. The computing device 206 can receive patient data, including SpO2 parameters, from the reusable module 250 and display the parameters on the display 208. In another example, the reusable module 250 operably connected to a temperature sensor can establish Bluetooth® communication with the computing device 206. The computing device 206 can receive patient data, including temperature parameters, from the reusable module 250 and display the parameters on the display 208. The computing device 206 can receive one or more parameters from the reusable module 250 and display the one or more parameters on the display 208.

[0136] The reusable module 250 can include an ID tag, which can be an active or passive RFID tag. An active RFID tag may be WiFi-enabled, for example. The ID tag can also be a barcode (e.g., two-dimensional or three-dimensional) or a WiFi-enabled RFID tag. By communicating with a WiFi access point, the computing device 206 can triangulate the location of the computing device 206 relative to the WiFi access point. Similarly, the location of the reusable module 250 (and the location of the reusable module 250 and the sensor 240, if the reusable module 250 is operably connected to the sensor 240) can be triangulated. Thus, using distributed WiFi access points, for example, the computing device 206 can determine the approximate location of the reusable module 250 (and / or the sensor 240) relative to the computing device 206. The computing device 206 may also communicate directly with the reusable module 250 to improve the location approximation determined, for example, using distributed WiFi access points.

[0137] The positions of one or more reusable modules 250 can be used to determine the relative or absolute position of one or more reusable modules 250. For example, consider modules 250A, 250B, 250C, and 250D. If the positions of reusable modules 250A, 250B, and 250C are known, then that position information can be used to determine the position of reusable module 250D.

[0138] The presence and proximity of the reusable module 250 to the computing device 206 can be determined by the reusable module 250 including an RFID tag. An "RFID tag" or simply "tag" can include a wireless communication device and / or communication standard (e.g., RFID, NFC, Bluetooth, ultrasonic, infrared, etc.) that can remotely identify a user in proximity to the monitor. Tags include, but are not limited to, badge, tag, clip-on, bracelet, or pen-shaped devices that contain an RFID chip or other wireless communication component. Tags also include smartphones, PDAs, pocket PCs, and other mobile computing devices with wireless communication capabilities. The RFID tag can include identification information or pairing parameters for the reusable module 250.

[0139] The computing device 206 can respond to the departure of all nearby reusable modules 250 by automatically detaching the displays associated with the reusable modules 250. This feature can provide and display patient physiological data for only the sensors 240 associated with the reusable modules 250 that are nearby the computing device 206. The computing device 206 may also respond by automatically muting a pulsed "beep" or other inconsequential sound upon the disappearance of nearby reusable modules 250 and associated sensors 240.

[0140] The computing device 206 may generate an alarm when the wireless communication 204 of the computing device 206 with the reusable module 250 is interrupted or no longer exists. For example, the computing device 206 may generate an audible and / or visual alarm when the reusable module 250 is no longer mated with the disposable module 220.

[0141] The computing device 206 may monitor the signal strength of the wireless communication 204 between the computing device 206 and the reusable module 250. In some situations, the reusable module 250 may move out of range of the computing device 206, thereby interrupting the wireless communication 204. For example, a patient equipped with the reusable module 250 may enter a habitually visited X-ray room, interrupting the wireless communication 204 between the reusable module 250 and the computing device 206. If the same reusable module 250 is available within range within a period of time, the computing device 206 may automatically re-establish the wireless communication 204. For example, if the patient returns from the X-ray room within 30 minutes, the computing device 206 may be able to re-establish the wireless communication between the reusable module 250 and the computing device 206. Upon re-establishing the communication, any information stored on the reusable module 250 during the period that communication was interrupted may be downloaded to the computing device 206.

[0142] The computing device 206 can be configured not to lose (or delete) the pairing parameters received from the reusable dongle 250. This feature can prevent other reusable modules 250 from pairing with the computing device 206 even when the reusable module 250 is no longer in wireless communication with the computing device 206. For example, a first computing device 206 and a first reusable module 250 have a first wireless communication 204. The first computing device 206 can be configured not to “give up” or to “give up” the first reusable module even after the first wireless communication 204 ends. When the second reusable module 250 is configured to “give up,” it can pair with the first computing device 206. When the second reusable module 250 is configured not to “give up,” it cannot pair with the first computing device 206.

[0143] This feature can also be applied in situations where the battery 224 of the disposable module 220 is about to run out or when the reusable module 250 is detached from the disposable module 220. When power from the battery 224 is depleted, the usable module 250 will be unable to maintain wireless communication 204 with the computing device 206. The computing device 206 can be configured to prevent or not prevent other computing devices 206 from establishing wireless communication 204 with the reusable module 250. The reusable module 250 can also send a “battery low” signal to the computing device 206 providing pairing or other instructions when the device is detached from the disposable module 220 or when the battery is depleted. This battery low instruction allows the pairing to be maintained.

[0144] A computing device 206 (or dongle 800) can communicate with other computing devices 206 (or other dongles 800) such that each computing device 206 (or dongle 800) is paired with a single reusable module 250 at any given time. For example, once a first reusable module 250 is paired (or associated) with the first computing device 206, a second reusable module 250 may no longer be paired (associated) with the first computing device 206. However, the first reusable module 250 may be able to pair with the second computing device 206. Once the first reusable module 250 is paired with the second computing device 206, the second computing device 206 can notify the first computing device 206 to unpair with the first reusable module 250.

[0145] The computing device 206 can identify sensors 240 and reusable modules 250 associated with the computing device 206. When one or more sensors 240 and reusable modules 250 are wirelessly associated with the computing device 206, it may be advantageous for the computing device 206 to distinguish between different physiological parameters from different sensors 240 or reusable modules 250. For example, the computing device 206 can be associated with two different sensors 240 (and their respective reusable modules 250) to detect peripheral capillary oxygen saturation (SpO2) and breath sounds (RRa). The computing device 206 can display information about the sensor 240 or reusable module 250 (e.g., sensor name, sensor type, sensor location, sensor ID, reusable module ID, reusable module name) to distinguish between patient parameters from different sensors and / or reusable modules.

[0146] The reusable module 250 of the sensor assembly 202 can establish wireless communication 204 with a mobile device, such as a smartphone, tablet, smartwatch, laptop, etc. The mobile device can include a mobile application that enables the mobile device to establish wireless communication 204 with the reusable module 250 of the sensor assembly 202, receive patient physiological parameters from the reusable module 250, and display the patient physiological parameters. The mobile application can display not only the patient physiological parameters but also other patient information, including, but not limited to, name, age, past medical history, current medications, address, gender, etc.

[0147] The wireless communication 204 between the mobile device and the reusable module 250 can take the form of Bluetooth®. The wireless communication 204 between the mobile device and the reusable module 250 can be established over the Internet. For example, the computing device 206 can be connected to the Internet or a secured network server. After the wireless communication 204 is established between the reusable module 250 and the computing device 206, the mobile device can access the Internet or secured network server to receive and display the patient physiological parameters via the mobile application described above.

[0148] The mobile application may include various security measures to prevent third parties from accessing patient information. The mobile application may be associated with several mobile devices identified by the healthcare provider. An identification and passcode may be required to use the application to connect to the reusable module 250 (or computing device 206), receive patient data (e.g., patient data and / or patient physiological parameters), and display patient data. Each mobile application may be associated with a unique access code or identification code, which may be required to receive patient data from the Internet or a secured network server. The unique access code or identification code may be associated with a mobile device or a mobile application. The unique access code may be a media access control (MAC) address associated with each of the mobile devices.

[0149] Mating the dock with the reusable module 10A-10D illustrate the process of mating the reusable module 250 and the dock 222 of the disposable module 220. The dock 222 of the disposable module 220 can be attached to the patient's wrist as shown in FIG. 10A. The dock 222 can include a housing 300 that includes slots 328 (see FIG. 3B) that correspond to the legs 326 of the reusable module 250.

[0150] 10B shows the reusable module 250 being inserted into the dock 222. The legs 326 can face the slots 328 of the dock 222 when the reusable module 250 is inserted. When the legs 326 are substantially positioned within the slots 328 of the dock 222, the body of the reusable module 250 can be positioned at an angle relative to the dock 222. One end of the reusable module 250 can be placed on the retainer 304 while at least a portion of the legs 326 is positioned in the slots 328 of the dock 222.

[0151] FIG. 10C shows the reusable module 250 being pushed down toward the dock 222. As shown in FIG. 10C, the legs 326 can be partially inserted into the slots 328. The reusable module 250 can be pushed down, which moves the retainer 304 away from the housing 300, thereby allowing the reusable module 250 to be fully inserted into the dock 222 and mated therewith, as shown in FIG. 10D. Once the reusable module 250 is fully inserted, the retainer 304 can move back toward the housing 300 and engage with the grooves 322 (FIG. 3B) on the reusable module 250. When the reusable module 250 and the dock 222 are mated, the legs 326 can engage with the slots 328 on the housing 300. Engagement of the grooves 322 with the protrusions 324 (FIG. 3B) on the retainer 304 can hold the reusable module 250 in place while mated with the dock 222. Engagement of slots 328 and legs 326 may hold reusable module 250 in place.

[0152] How to pair, collect, and transmit data to a computing device FIG. 11A illustrates a method 1100 of establishing wireless communication between a reusable module 250 and a computing device 206, determining a patient physiological parameter using a sensor assembly 202, and displaying the physiological parameter using the computing device 206.

[0153] In block 1102, the patient monitor (e.g., the computing device 206) may generate and transmit a pairing signal. Generating and transmitting the pairing signal may be automatic or manual. The pairing signal may be a wireless signal. The pairing signal may be configured to be triggered when a nearby device receives the signal and transmits its identification information in response. The nearby device may be a reusable module 250. The pairing signal may also include sufficient power to enable the nearby device to transmit pairing parameters in response to the pairing signal.

[0154] Generating and transmitting the pairing signal can be performed by various devices. The computing device 206 can generate the pairing signal, while the dongle 800 attached to the computing device 206 via the connector 804 can transmit the pairing signal. The dongle 800 can generate and transmit the pairing signal for the computing device 206.

[0155] The reusable module 250 can receive a pairing signal when located a predetermined distance from the computing device 206. This can be advantageous in a hospital environment where many patients may be located a short distance from an electronic device such as the computing device 206. Such a configuration can allow an electronic device (e.g., the computing device 206) to receive patient health data only from nearby patients and prevent the electronic device from receiving patient health data from other patients who may not be patients of interest. The strength of the pairing signal can be varied to allow the signal to travel farther or closer.

[0156] In block 1104, the reusable module 250 may receive power from a pairing signal generated by the computing device 206. The pairing signal may be a high-frequency alternating current that can be used to generate a voltage potential. The pairing signal of the computing device 206 may be received when the reusable module 250 is located within a predetermined distance. As explained above, physical contact between the computing device 206 (or dongle 800) and the reusable module 250 may be required for the reusable module 250 to receive power from the pairing signal. The reusable module 250 may automatically receive power from the pairing signal. By receiving power from the pairing signal, the reusable module's antenna 252 may not be required to draw power from the battery 224 of the disposable device 220.

[0157] At block 1106, the reusable module 250 may transmit identification information to the computing device 206 using the power received from the pairing signal. The identification information may include pairing parameters for the reusable module 250. The identification information may be a tag serial number unique to the reusable module 250. The identification information may include, but is not limited to, a stock number, a lot number, a batch number, a manufacturing date, or other specific information. The computing device 206 may use the identification information to uniquely identify the reusable module 250. The transmission of the identification information may be automatic.

[0158] The reusable module 250 may include a feature that prevents the automatic transmission of identifying information to the computing device 206. This feature may be advantageous in preventing the reusable module 250 from inadvertently pairing with the computing device 206. Medical personnel may treat patients who require many different types of sensors. In such situations, they may inadvertently bring the reusable module 250 into close proximity with the computing device 206 (or dongle 800). Therefore, it may be advantageous for the reusable module 250 to have a feature that prevents it from automatically pairing with the computing device 206 (or dongle 800) and prevents inadvertent pairing.

[0159] At block 1108, the computing device 206 may receive the identification information from the reusable module 250. When the dongle 800 is connected to the computing device 206, it may receive and relay the identification information to the computing device 206. At block 1110, the computing device 206 may associate with the reusable module 250, thereby enabling wireless communication 204 to be established between the reusable module 250 and the computing device 206.

[0160] Association between computing device 206 and reusable module 250 can occur automatically. Alternatively, association may require user input via computing device 206. For example, upon receiving pairing parameters from reusable module 250, computing device 206 may generate a notification prompting the user to allow or disallow computing device 206 to associate with reusable module 250. If allowed, computing device 206 may associate with reusable module 250, and reusable module 250 may establish wireless communication 204 with computing device 206. If disallowed, computing device 206 may not associate with reusable module 250, and reusable module 250 may not establish wireless communication 204 with computing device 206.

[0161] Establishing wireless communication 204 may require reusable module 250 to have an external power source. Battery 224 provides sufficient power for reusable module 250 to receive raw patient physiological data from sensors 240 and perform signal processing on the raw data to calculate patient physiological parameters. Additionally, reusable module 250 can use power from battery 224 to wirelessly transmit the calculated parameters to computing device 206 using antenna 252. If battery 224 is not connected to dock 222, reusable module 250 cannot receive power via electrical contacts 228, 258.

[0162] At block 1112, the reusable module 250 may mate with the dock 222 and receive power from the battery 224 via the battery circuit 314 and electrical contacts 228, 258. At block 1114, the reusable module 250 may establish wireless communication 204 with the computing device 206. The wireless communication 204 may be established using pairing parameters. The wireless communication 204 may occur via Bluetooth®, as described above. The wireless communication 204 may be one-way or two-way communication between the reusable module 250 and the computing device 206. For example, the reusable module 250 may transmit the calculated physiological parameters to the computing device 206. The computing device 206 may, in response, send a confirmation signal back to the reusable module 250, informing the reusable module 250 that the calculated parameters were received. The reusable module 250 may include one or more light sources (e.g., LEDs) that may emit light upon receiving a confirmation signal from the computing device 206.

[0163] In block 1116, the sensors 240 can acquire raw patient physiological data and transmit the data to the dock 222 via the cable 230 and flex circuit 320. The raw physiological data can be transferred to the reusable module 250 via the electrical contacts 228, 258. The sensors 240 can include, but are not limited to, acoustic sensors, ECG sensors, EEG sensors, respiratory sound sensors (RAS), SpO2 sensors, etc. The sensors 240 can include one or more different types of sensors.

[0164] The sensor 240 can be placed on various locations on the patient. The location of the sensor 240 can depend on the type of sensor used for the sensor 240. For example, the sensor 240 can be an O sensor that is typically attached to the patient's forehead to monitor cerebral oxygenation. In another example, the sensor 240 can be a breath sound sensor that is typically attached to the patient's neck near the trachea to detect vibrations associated with breathing.

[0165] At block 1118, the processor 254 of the reusable module 250 may receive raw patient physiological data from the sensor 240 of the disposable module 220. The raw patient physiological data may be stored in the memory 256.

[0166] In block 1120, the processor 254 of the reusable module 250 can perform signal processing on the raw physiological data. Various types of signal processing used on the raw physiological data can include, but are not limited to, analog signal processing, continuous-time signal processing, discrete-time signal processing, digital signal processing, or nonlinear signal processing. For example, continuous-time signal processing such as time domain, frequency domain, and complex frequency domain can be used. Some signal processing methods that can be used on the raw physiological data include, but are not limited to, passive filters, active filters, additive mixers, integrators, delay lines, companders, multipliers, voltage-controlled filters, voltage-controlled oscillators, phase-locked loops, time domain, frequency domain, fast Fourier transform (FFT), finite impulse response (FIR) filters, infinite impulse response (IIR) filters, and adaptive filters. Such processing techniques can be used to improve signal transmission, storage efficiency, and subjective quality. Furthermore, such processing techniques can be used to enhance or detect components of interest in the raw physiological data. Noise filtering can be used to filter out raw physiological data corrupted by noise caused by patient movement, electromagnetic interference, or ambient light.

[0167] Signal processing can determine the absorbance of light due to pulsating arterial blood. For example, a pulse oximeter generates a blood volume plethysmographic waveform from which arterial oxygen saturation, pulse rate, and perfusion index, among other physiological parameters, can be determined. In the context of pulse oximetry, sensor 240 can use adaptive filtering techniques to separate the arterial signal detected by the pulse oximeter sensor from non-arterial noise (e.g., venous blood movement during patient movement). During habitual patient movement (such as shaking, shaking, or tapping), the resulting noise can be significant and easily overwhelmed by conventional ratio-based oximetry systems. This allows for accurate blood oxygenation measurements even during patient movement, low perfusion, strong ambient light, and electrocautery interference.

[0168] At block 1122, the processor 254 of the reusable module 250 may determine patient physiological parameters by processing the raw physiological data. The processor 254 may then store the processed data and calculated parameters in memory 256 before transmitting them to the computing device 206.

[0169] The processed data may indicate, for example, the attenuation of a predetermined wavelength (range of wavelengths) of light by body tissue, such as a finger, a portion of the nose or ear, or a foot. For example, the predetermined wavelengths may correspond to desired specific physiological parameter data, including, but not limited to, oxygen content (SpOC®), oxygen saturation (SpOC2), blood glucose, total hemoglobin (SbHb), methemoglobin (SpMet®), carboxyhemoglobin (SpCO), bulk tissue property measurements, water content, pH, blood pressure, respiratory-related information, cardiac information, perfusion index (PI), electroencephalography (PVI®), etc., which may be used by the mobile computing device to determine the user's condition. The processed data may provide information regarding physiological parameters, such as EEG, ECG, heart rate (HRa), respiratory sounds (RRa), respiratory rate (breaths) per minute, partial pressure of exhaled carbon dioxide (EtCO2), respiratory effort index, return of spontaneous circulation (ROSC), etc., which may be used to determine the user's physiological condition.

[0170] At block 1124, the processor 254 of the reusable module 250 can transmit the patient physiological parameters to the computing device 206 via the antenna 252 using the communication protocol and pairing parameters. It may be advantageous to transmit the calculated physiological parameters (e.g., 60% SpO2) rather than transmitting the raw physiological data to the computing device 206. Compared to the calculated physiological parameters, the raw physiological data is larger in size and therefore requires a larger bandwidth when transmitted to the computing device 206. On the other hand, the calculated physiological parameters can be much smaller in size and require a smaller bandwidth for transmission. Therefore, transmitting the patient physiological parameters instead of the raw physiological data can reduce battery consumption and extend battery life for the disposable module 220.

[0171] The physiological parameters may be transmitted wirelessly via NFC. For example, the physiological parameters may be transmitted wirelessly via Bluetooth. The physiological parameters may also be transmitted via a cable.

[0172] At block 1126, the computing device 206 may receive the patient physiological parameters and display the parameters using the display 208. As described above, the computing device may include a display 208 capable of displaying various patient physiological parameters, including, but not limited to, body temperature, heart rate, blood oxygen level, blood pressure, etc.

[0173] FIG. 11B illustrates another method 1150 of establishing wireless communication between a reusable module 250 and a computing device 206, determining a patient physiological parameter using a sensor assembly 202, and displaying the physiological parameter using the computing device 206.

[0174] At block 1152, the reusable module 250 may establish NFC (near field communication) with the computing device 206. As explained above, all that is required to establish NFC may be that the reusable module 250 be located within a predetermined distance from the computing device 206. As noted above, NFC may be established between the body 802 of the dongle 800 and the reusable module 250.

[0175] At block 1154, the reusable module 250 may transmit the pairing parameters to the computing device 206. The transmission of the pairing parameters to the computing device 206 may occur when the reusable module 250 establishes NFC with the computing device 206. At block 1156, the computing device 206 may receive the pairing parameters from the reusable module 250. The computing device 206 may receive the pairing parameters using the dongle 800. For example, the body 802 of the dongle 800 may receive the pairing parameters wirelessly and transmit the pairing parameters to the computing device 206 via the cable 806 and the connector 804.

[0176] At block 1158, the computing device 206 or main body 802 may associate with the reusable module 250 using pairing parameters. After being associated, the computing device 206 or main body 802 may wait for wireless communication 204 from the reusable module 250. As noted above, the wireless communication 204 may be via Bluetooth. At block 1164, the sensor 240 of the disposable module 220 may acquire physiological data and transmit the data to the reusable module 250. The physiological data acquired by the sensor 240 and transmitted to the reusable module 250 may be raw physiological data.

[0177] Blocks 1166 to 1174 may be optional. In block 1166, the reusable module may receive patient physiological data from the disposable module 220. In block 1168, the reusable module 250 may perform signal processing on the patient physiological data. In block 1170, the reusable module 250 may determine patient physiological parameters using the processed physiological data. In block 1172, the reusable module 250 may transmit the patient physiological parameters using wireless communication 204 established between the reusable module 250 and the computing device 206. The main body 802 of the dongle 800 may wirelessly receive the patient physiological parameters from the reusable module 250 and transmit the parameters to the computing device via the cable 806 and connector 804. In block 1174, the computing device 206 receives the patient physiological parameters and displays the parameters on the display 208.

[0178] FIG. 12 illustrates another method 1200 of determining a patient physiological parameter using the sensor assembly 202 and displaying the physiological parameter using the computing device 206.

[0179] In block 1202, the processor 254 of the reusable module 250 receives raw patient physiological data from the sensor 240 of the disposable module 220 according to blocks 1102-1120 of FIG.

[0180] At block 1204, the processor 254 of the reusable module 250 transmits the raw patient physiological data to the computing device 206. The processor 254 may use the antenna 252 to transmit the raw data via wireless communication 204 established between the reusable module 250 and the computing device 206. As described above, the wireless communication 204 may be a one-way or two-way communication between the reusable module 250 and the computing device 206.

[0181] In block 1206, the computing device 206 receives raw patient physiological data. In block 1208, the computing device 206 performs signal processing on the raw patient physiological data. In block 1210, the computing device 206 determines patient physiological parameters using the processed raw patient physiological data. In block 1212, the computing device 206 displays the determined physiological parameters on the display 208.

[0182] Mobile Applications As described above, the computing device 206 can be a mobile device 1300 such as a phone, tablet, watch, etc. The mobile device 1300 can include a mobile application capable of establishing wireless communication with the reusable module 250 via a wireless communication protocol such as Bluetooth.

[0183] 13A illustrates a mobile application executing on a mobile device 1300 (e.g., a mobile phone) to establish wireless communication with a reusable module 250. The mobile application can pair with nearby reusable modules 250. In one example, a user can press a pair button 1302 to cause the mobile application to search for nearby reusable modules 250. The mobile application can create a screen 1304 to display nearby reusable modules 250. The screen 1304 can present the reusable module 250 with a unique MAC address or any other pairing information. The mobile application may automatically search for nearby reusable modules 250 without user intervention or input.

[0184] 13B-13E show various examples of the mobile application displaying patient parameters. Triggering the home button 1308 can cause the mobile application to display real-time patient parameters in numeric and graphical representations, as shown in FIG. 13A. The mobile application can display numeric parameters 1310 (e.g., the patient's SpO2, PR BPM, and PI measurements) in real-time or with a predetermined delay. The mobile application may also display a graphical representation 1314 of the patient parameters showing the real-time trend of the parameters. For example, a user can trigger the SpO2 portion of the display to cause the mobile application to display the real-time trend of the SpO2 parameter.

[0185] 13C, triggering the history button 1312 can cause the mobile application to display a graphical display 1314 showing the historical trend of the patient health parameter. The graphical display 1314 can have an x-axis showing timestamps and a y-axis showing the parameter value. The mobile application may also display real-time values ​​of the patient health parameter above or below the graphical display 1314. The real-time values ​​can be integrated into the graphical display 1314.

[0186] As shown in FIGS. 13D and 13E, the mobile application can display at least one of the numerical parameters 1310 and the graphical representation 1314 in a landscape view.

[0187] Method for identifying and / or verifying a disposable module - Patent Application 20070122997 As described herein, the disposable module 220 may include a sensor assembly 240 that may include various types of sensors. Therefore, it may be advantageous for the reusable module 250 to be able to identify the disposable module 220. This may be advantageous, for example, to check or verify that the sensor assembly 240 of the disposable module 220 has the desired or correct type of sensors appropriate for a certain situation, environment, etc. Additionally, the reusable module 250 may also obtain identification and / or operating parameters such that the reusable module 250 uses the correct algorithm or calibration curve for the attached disposable sensor.

[0188] The memory of the disposable module 220, for example, the memory 226 shown in FIG. 2B , can be configured to store operational data 1400 as shown in FIG. 14A . The operational data 1400 may or may not be unique to the disposable module 220. The operational data indicates the types of sensors associated with a given disposable module 220 at any given time. For example, the operational data 1400 may be automatically updated when a new sensor 240 is provided to the disposable module 220. Thus, the operational data 1400 can accurately reflect what sensors 240 are associated with a given disposable module 220 and provide such information to a healthcare provider. This can be useful in situations where different types of sensors may look the same or when a healthcare provider does not have enough time to check or ensure that all sensors are properly identified.

[0189] In some cases, a reusable module, such as reusable module 250 shown in FIG. 2B , may be programmed to be associated with a particular type of sensor or a particular type of patient health data. For example, the reusable module may be programmed to be associated with patient health data, such as, for example, pulse oximetry-related data, including, but not limited to, blood oxygen saturation (SpO2). Thus, when connected to a disposable module, the reusable module may access and analyze operational data from the disposable module to verify that a sensor assembly associated with or of the disposable module is compatible with, for example, the reusable module or is capable of collecting patient health data related to, for example, blood oxygen saturation.

[0190] The memory of the disposable module 220 may include sensor life data 1402. The sensor life data 1402 may be used, for example, to monitor the lifespan of the disposable module 220. The sensor life data 1402 may include one or more sensor usage information 1404 and one or more functions that can be used to determine the sensor lifespan. The sensor lifespan may represent the expected operating time of the disposable module 220. Some examples of the sensor usage information 1404 may include, but are not limited to, the age of the sensor, the actual hours of operation of the sensor, the current supplied to the sensor, the temperature of the sensor, the number of times the sensor has been depressed, the number of times the sensor has been calibrated, the number of times power has been supplied to the sensor, etc. Various examples of systems and methods for determining sensor life using sensor life data, e.g., sensor usage information and functions, are disclosed in U.S. patent application Ser. No. 11 / 580,214, filed Oct. 12, 2006, and entitled "SYSTEM AND METHOD FOR MONITORING THE LIFE OF A PHYSIOLOGICAL SENSOR," now U.S. Pat. No. 7,880,626, issued Feb. 1, 2011, which is incorporated herein by reference in its entirety. In some configurations, the sensor life is the life of the battery contained on the sensor. When the battery dies, the sensor records a dead battery event in sensor memory.

[0191] In some embodiments, the sensor lifetime may be automatically updated when the patient's condition changes or when the operating condition of the disposable module 220 changes. For example, changes in the patient's condition, e.g., a sudden increase in blood pressure and a decrease in blood oxygen levels, may be identified based at least in part on the physiological data collected by the disposable module 220. As described herein, detecting such changes in the patient's condition may trigger the disposable module 220 to collect physiological data, e.g., more frequently or with higher fidelity, thereby increasing power consumption by the disposable module 220. In another example, the temperature of the disposable module 220 (and its sensor element) may increase, and the sensor lifetime may be automatically updated when an increase in the temperature of the disposable module 220 is detected. By automatically calculating and updating the sensor lifetime under such exemplary conditions described herein, a healthcare provider may have access to a more accurate estimate of the sensor lifetime. This may be advantageous, for example, in situations where a patient may be experiencing an emergency situation and the disposable sensor needs to collect more data points, e.g., with higher fidelity. By automatically updating the sensor life, a healthcare provider may accurately monitor the expected operating time of the disposable module 220 and determine if additional disposable modules 220 may be needed.

[0192] In some implementations, the sensor life may be automatically updated at a predetermined time interval. The predetermined time interval for updating the sensor life may be in a range between about 1 minute and about 1 hour, between about 2 minutes and about 30 minutes, between about 5 minutes and about 20 minutes, between about 10 minutes and about 15 minutes, or in a range of about 1 minute, about 2 minutes, about 5 minutes, about 10 minutes, about 15 minutes, about 20 minutes, about 30 minutes, about 1 hour, or any two of the above values.

[0193] 14B illustrates an example method 1450 for identifying or verifying a disposable module. At block 1452, coupling of the disposable module and the reusable module is detected. A processor of the reusable module, e.g., processor 254 of reusable module 250, may detect coupling of the reusable module and the disposable module by detecting an electronic input or signal transmitted between the reusable module and the disposable module. The electronic input or signal may be patient health data and / or current flowing from a battery, e.g., battery 224 of disposable module 220, to the reusable module, etc. In some cases, computing system 206 may detect coupling of the reusable module and the disposable module by detecting, for example, patient health data and / or parameters transmitted from reusable module 250.

[0194] At block 1454, operational data is accessed from the disposable module 220. As described herein, the operational data may be stored in a memory, for example, the memory 226 of the disposable module 220. In some examples, a processor, for example, the processor 254 of the reusable module, may access the operational data from the disposable module 220. As described herein, the operational data may include operational data and sensor life data.

[0195] The operational data is analyzed at block 1456. The processor 254 of the reusable module 250 may perform the analysis. In some cases, the reusable module 250 may relay the operational data to the computing system 206, which may perform the analysis of the operational data.

[0196] At block 1458, the disposable module 220 is identified based at least in part on the operational data and the analysis of the operational data. Identifying the disposable module 220 may include determining a sensor type associated with the disposable module 220, determining whether the sensor type associated with the disposable module corresponds to the configuration of the reusable module, determining the lifespan of the sensor associated with the disposable module, etc.

[0197] Communication with other sensor devices In some implementations, the sensor assembly 202 can communicate with other monitoring devices, such as a patient monitoring device 1600. FIG. 16A shows a block diagram of the sensor assembly 202 in wireless communication with a patient monitoring device 1600. The patient monitoring device 1600 can include a communications module 1602, a storage device 1604, and a sensor assembly 1606. The patient monitoring device 1600 can be an activity tracker, a bedside monitor, a handheld monitor, and a wearable device. For example, the patient monitoring device 1600 can be an electrocardiogram (ECG), a thermometer, Radical (a patient monitoring device commercially available from Masimo Corporation of Irvine, California), Rad (a patient monitoring device commercially available from Masimo Corporation of Irvine, California), Root (a patient monitoring and connectivity platform commercially available from Masimo Corporation of Irvine, California), etc. The patient monitoring device 1600 may collect, analyze, or display data regarding various types of physiological parameters, including electrocardiogram, pulse rate, respiratory rate, temperature, blood oxygen saturation (SpO2), perfusion index (PI), electroencephalography (PVi®), total hemoglobin (SbHb®), oxygen content (SpOC™), methemoglobin (SpMet®), carboxyhemoglobin (SpCO®), breath sounds (RRa®), electroencephalogram (EEG), enhanced Patient State Index (PSi), frequency spectral density array (DSA), and the like.

[0198] The communication module 1602 can establish wired or wireless communication with various devices, networks, etc. The sensor assembly 1606 can collect data related to or relating to, for example, a physiological condition of a patient. The sensor assembly 1606 may be in direct contact with the patient. The storage device 1604 may store the data collected by the sensor assembly 1606.

[0199] The sensor assembly 1606 may include one or more sensors capable of collecting one or more types of physiological data described herein. For example, the patient monitoring device 1600 may be a Holter monitor, and the sensor assembly 1606 may include one or more leads that may be attached, for example, to the patient's torso region. In one example, the sensor assembly 1606 includes three leads. In another example, the sensor assembly 1606 includes twelve leads.

[0200] In some implementations, the sensor assembly 202 can communicate with the patient monitoring device 1600. The sensor assembly 202 may communicate directly with the patient monitoring device 1600 by establishing direct communication with the patient monitoring device 1600. Alternatively and / or in some cases, the sensor assembly 202 may communicate indirectly with the patient monitoring device 1600, for example, via a network 1620 (see FIG. 16B ) or a server.

[0201] As described herein, the sensor assembly 202 may store collected patient physiological data in the memory 256 of the reusable module 250 when it is unable to transmit the data, e.g., via wireless communication, to, e.g., the computing system 206. When the sensor assembly 202 determines that it is unable to transmit the collected data, e.g., to the computing system (e.g., due to wireless communication between the sensor assembly 202 and the computing device 206 being interrupted), it may alternatively transmit the collected patient physiological data to the patient monitoring device 1600 via wireless communication 1608. The patient monitoring device 1600 may receive the patient physiological data via the communication module 1602 and store the data. The data may be stored in the storage device 1604.

[0202] The patient monitoring device 1600 may transmit the patient physiological data back to the sensor assembly 202 when communication between the sensor assembly 202 and the computing system 206 is restored. In some implementations, the sensor assembly 202 generates and transmits a notification to the patient monitoring device 1600 indicating that communication between the sensor assembly 202 and the computing system 206 has been restored. Upon receiving the notification from the sensor assembly 202, the patient monitoring device 1600 can transmit the stored patient physiological data (i.e., the patient physiological data that the sensor assembly 202 transmitted to the patient monitoring device 1600 when it determined that it was unable to transmit collected data, for example, to the computing system 206) to the sensor assembly 202 via wireless communication 1608. Upon receiving the patient physiological data from the patient monitoring device 1600, the sensor assembly 202 can transmit the data to the computing device 206. Thus, the sensor assembly 202 can use the patient monitoring device 1600 as a backup data storage device.

[0203] In some implementations, the sensor assembly 202 can communicate with one or more patient monitoring devices 1600. FIG. 16B shows a block diagram illustrating the sensor assembly 202 in wireless communication with the patient monitoring devices 1600a, 1600b, 1600c and the network 1620. The sensor assembly 202 may establish wireless communication with one or more of the patient monitoring devices 1600a, 1600b, 1600c at any time. In some implementations, the sensor assembly 202 may not, by default, establish wireless communication when it is able to communicate with, for example, the computing system 206, in order to preserve power stored in the battery 224 of the disposable module 220. Thus, the sensor assembly 202 may establish wireless communication with one or more of the patient monitoring devices 1600a, 1600b, 1600c when it determines that wireless communication with the sensor assembly 202 is no longer available and therefore, for example, cannot transmit patient physiological data to the computing device 206.

[0204] In some implementations, the sensor assembly 202 may be capable of communicating with the network 1620 via wireless communication 1610. As noted herein, the network 1620 may be in communication with the computing system 206. Thus, even if the sensor assembly 202 is unable to establish direct communication with the computing system 206, the sensor assembly 202 may be capable of communicating with the computing system 206 indirectly via the network 1620.

[0205] In some implementations, the patient monitoring device 1600 may communicate with the network 1620 via wireless communication 1612. For example, upon receiving patient physiological data from the sensor assembly 202, the patient monitoring devices 1600a, 1600b, 1600c may transmit the data to the network 1620 via wireless communication 1612. The network 1620 may be a server in communication with the computing device 206. Upon receiving patient physiological data from the patient monitoring devices 1600a, 1600b, 1600c, the network 1620 may, for example, transmit the data to the computing device 206 to analyze the data, determine physiological parameters based on the data, and generate an indication of the physiological parameters, for example, on a display. In some implementations, the transmission of patient physiological data between the sensor assembly 202, the patient monitoring devices 1600a, 1600b, 1600c, and the network 1620 may occur with or without a delay. For example, patient monitoring devices 1600a, 1600b, 1600c may transmit patient physiological data to network 1620 immediately after receiving the patient physiological data from sensor assembly 202. Alternatively, patient monitoring devices 1600a, 1600b, 1600c may transmit patient physiological data to network 1620 after a predetermined period of time has elapsed.

[0206] In some implementations, the sensor assembly 202 generates a packet including the patient physiological data and instructions for the patient monitoring devices 1600a, 1600b, 1600c. The instructions cause the patient monitoring devices 1600a, 1600b, 1600c to transmit the patient physiological data after receiving it, for example, to the computing device 206 or the network 1620. In another example, the instructions cause the patient monitoring devices 1600a, 1600b, 1600c to store the patient physiological data until the patient monitoring devices 1600a, 1600b, 1600c are connected, for example, to the computing device 206 or the network 1620. In yet another example, the instructions cause the patient monitoring devices 1600a, 1600b, 1600c to store the patient physiological data.

[0207] In some implementations, transmission of patient physiological data between the sensor assembly 202 and the patient monitoring devices 1600a, 1600b, 1600c and the network 1620 may occur when a predetermined condition is met. For example, the sensor assembly 202 (or the reusable module 250 of the sensor assembly 202) may transmit collected patient physiological data to one or more of the patient monitoring devices 1600a, 1600b, 1600c when wireless communication cannot be established with, for example, the computing device 206 or the network 1620 for a predetermined period of time. The predetermined period of time (e.g., a timer) may be 10 seconds, 30 seconds, 1 minute, 2 minutes, 5 minutes, 10 minutes, or any duration sufficient to prevent or reduce data loss or unnecessary power consumption due to failed attempts to establish wireless communication.

[0208] In another example, the sensor assembly 202 (or the reusable module 250 of the sensor assembly 202) may transmit collected patient physiological data to one or more of the patient monitoring devices 1600a, 1600b, 1600c after a predetermined number of failed attempts to establish wireless communication, for example, with the computing device 206 or the network 1620. The predetermined number of failed attempts may be 1 minute, 2 minutes, 5 minutes, 10 minutes, 20 minutes, or any number sufficient to prevent or reduce data loss or unnecessary power consumption due to failed attempts to establish wireless communication.

[0209] The predetermined conditions may be modifiable and may be modified by a user (e.g., a patient) or a healthcare provider (e.g., a doctor). Alternatively, input or request from a user (e.g., a healthcare provider such as a nurse or doctor) may cause or enable transmission of patient physiological data between sensor assembly 202 and patient monitoring devices 1600a, 1600b, 1600c and network 1620. For example, a nurse may determine that sensor assembly 202 is no longer in communication with computing system 206 and provide user input to sensor assembly 202 to enable sensor assembly 202 to transmit patient physiological data to patient monitoring devices 1600a, 1600b, 1600c.

[0210] In some implementations, a priority scheme may be used between the sensor assembly 202 and the patient monitoring devices 1600a, 1600b, 1600c. For example, the sensor assembly 202 may generate and send to the patient monitoring devices 1600a, 1600b, 1600c a request for connectivity information related to the wireless communication 1612 between the patient monitoring devices 1600a, 1600b, 1600c and the network 1620. Upon receiving the request for the connectivity information, the patient monitoring devices 1600a, 1600b, 1600c may responsively send the connectivity information back to the sensor assembly 202. The connectivity information may be related, for example, to the strength of the connection between the patient monitoring devices 1600a, 1600b, 1600c and the network 1620.

[0211] Based on the received connectivity information, the sensor assembly 202 can identify a patient monitoring device (e.g., patient monitoring device 1600c) to transmit the patient physiological data to. The sensor assembly 202 can transmit the patient physiological data to the identified patient monitoring device, which can relay the data to the network 1620 as described herein.

[0212] In another example, the priority scheme may be related to battery status and / or storage device status. For example, the sensor assembly 202 may generate and transmit a request to the patient monitoring devices 1600a, 1600b, 1600c for battery status and / or storage device status information associated with the patient monitoring devices 1600a, 1600b, 1600c. Upon receiving the request for the battery status and / or storage device status information, the patient monitoring devices 1600a, 1600b, 1600c may transmit the battery status and / or storage device status information back to the sensor assembly 202 in response. The battery status information may relate to (1) the battery charge level, (2) the power usage of the patient monitoring devices 1600a, 1600b, 1600c, and (3) the expected power usage due to data transmission between the sensor assembly 202 and the patient monitoring devices 1600a, 1600b, 1600c. The storage device status may relate to (1) the amount of data storage available, (2) the amount of expected data from the sensor assembly 1606, and (3) the amount of expected data from the sensor assembly 202.

[0213] The sensor assembly 202 can identify a patient monitoring device (e.g., patient monitoring device 1600c) to transmit the patient physiological data to based on the received battery status and / or storage device status information. The sensor assembly 202 can transmit the patient physiological data to the identified patient monitoring device, and the identified patient monitoring device can store the patient physiological data.

[0214] The use of patient monitoring devices 1600a, 1600b, 1600c may allow for increased flexibility in handling, storing, and transmitting patient physiological data to computing device 206. For example, patient monitoring devices 1600a, 1600b, 1600c may have a longer battery life and / or a larger data storage capacity than sensor assembly 202. Sending patient physiological data to patient monitoring devices may allow patient monitoring devices 1600a, 1600b, 1600c to retrieve a greater amount of data, for example, for storage until wireless communication between sensor assembly 202 and computing system 206 is restored. Additionally, the use of patient monitoring devices 1600a, 1600b, 1600c may provide increased flexibility for data transmission, as the patient monitoring devices 1600a, 1600b, 1600c provide additional paths for transmission of data (e.g., patient physiological data) between the sensor assembly 202 and the computing device 206 via wireless communication 1608 between the sensor assembly 202 and the patient monitoring devices 1600a, 1600b, 1600c and wireless communication 1612 between the patient monitoring devices 1600a, 1600b, 1600c and the network 1620.

[0215] 16C shows an example method 1630 for transmitting patient physiological data by the sensor assembly 202. The method 1630 may be performed by the sensor assembly 202 (or the processor 254 of the reusable module 250) or any device in communication with the sensor assembly 202. At block 1632, the sensor assembly 202 attempts to establish a first wireless communication. The first wireless communication may be a communication between the sensor assembly 202 and, for example, the computing device 206 or the network 1620.

[0216] At block 1634, the sensor assembly 202 determines whether a first wireless communication has been established, e.g., between the sensor assembly 202 and the computing system 206 or the network 1620. If the sensor assembly 202 determines that the first wireless communication has been established, then at block 1636, the sensor assembly 202 transmits the patient physiological data to the computing system 206 or the network 1620, e.g., via the first wireless communication. If the sensor assembly 202 determines that the first wireless communication has not been established, then the sensor assembly 202 determines whether a predetermined condition has been met. As described herein, the predetermined condition includes, but is not limited to, whether the sensor assembly 202 has failed a predetermined number of attempts to establish the first wireless communication, e.g., with the computing system 206 or the network 1620, or whether a predetermined amount of time has elapsed since the sensor assembly 202 failed to establish the first wireless communication, e.g., with the computing system 206 or the network 1620.

[0217] If the sensor assembly 202 determines that the predetermined condition is not met, it attempts to establish wireless communication in block 1632. Alternatively, if the sensor assembly 202 determines that the predetermined condition is met, it attempts to establish a second wireless communication, for example, with the patient monitoring device 1600a, 1600b, 1600c, in block 1640. In block 1642, the sensor assembly 202 determines whether the second wireless communication is established. If the second communication is established, the sensor assembly 202 transmits the patient physiological data to the patient monitoring device 1600a, 1600b, 1600c, for example, via the second wireless communication. However, if the second wireless communication is not established, the sensor assembly 202 attempts to establish the first wireless communication in block 1632. In some cases, when the sensor assembly 202 determines that the second wireless communication is not established, it may store the patient physiological data in the memory 256 instead of attempting to establish the first wireless communication.

[0218] 16D shows an example method 1650 for transmitting patient physiological data to patient monitoring devices. In block 1652, the sensor assembly 202 sends a request for network connectivity information to one or more patient monitoring devices (e.g., patient monitoring devices 1600a, 1600b, 1600c). The one or more patient monitoring devices may be proximate to the sensor assembly 202. The one or more patient monitoring devices may or may not be coupled to the patient.

[0219] At block 1654, the sensor assembly 202 receives requested network connectivity information from one or more patient monitoring devices. As described herein, the network connectivity information may relate, for example, to the network connection strength between one or more patient monitoring devices and, for example, the network 1620. At block 1656, the sensor assembly 202 identifies a first patient monitoring device based on the network connectivity information. For example, to achieve uninterrupted, reliable, and high-speed wireless transmission of patient physiological data, the sensor assembly 202 may identify the patient monitoring device having the strongest and most reliable network connection with, for example, the network 1620 or the computing device 206.

[0220] At block 1658, sensor assembly 202 (or processor 254 of reusable module 250) may establish wireless communication with the first patient monitoring device (i.e., the patient monitoring device identified at block 1656). At block 1660, sensor assembly 202 may transmit patient physiological data to the first patient monitoring device. The first patient monitoring device may then transmit the data to network 1620, as described herein.

[0221] 16E shows an example method 1670 for transmitting patient physiological data to patient monitoring devices. In block 1672, sensor assembly 202 transmits a request for operational data to one or more patient monitoring devices (e.g., patient monitoring devices 1600a, 1600b, 1600c). The one or more patient monitoring devices may or may not be in close proximity to sensor assembly 202. The one or more patient monitoring devices may or may not be coupled to the patient.

[0222] At block 1674, the sensor assembly 202 receives requested operational data information from one or more patient monitoring devices. As described herein, the operational data may relate to (1) battery charge level, (2) power consumption level, and (3) expected power usage due to data transmission. At block 1676, the sensor assembly 202 identifies a first patient monitoring device based on the battery status information. For example, to maximize the amount of patient physiological data stored, the sensor assembly 202 identifies the patient monitoring device having the highest battery charge, the lowest power usage, and / or the lowest expected power usage due to data transmission.

[0223] At block 1678, the sensor assembly 202 (or the processor 254 of the reusable module 250) may establish wireless communication with the first patient monitoring device (i.e., the patient monitoring device identified at block 1676). At block 1680, the sensor assembly 202 may transmit the patient physiological data to the first patient monitoring device. The first patient monitoring device 1600 may then transmit the data to the network 1620 as described herein.

[0224] Sending data to healthcare providers In some implementations, the communication module 252 of the reusable module 250 of the sensor assembly 202 is optional, and the reusable module 250 may not include the communication module 252. Thus, the reusable module 250 may not establish wireless communications with nearby devices, routers, access points, etc., and may not transmit patient physiological data to, for example, the computing system 206 or the network 1620. In the absence of the communication module 252, the reusable module 250 may receive physiological data from the sensors 240 of the disposable module 220 and store the data, for example, in the memory 256. Such a configuration may include a much larger memory, allowing the communication module 252 to store high-fidelity data for several days, e.g., 3-7 days, of continuous monitoring. This configuration advantageously allows the reusable module 250 to operate for longer periods by reducing power consumption by storing the patient physiological data in the memory 256 instead of wirelessly transmitting the patient physiological data to, for example, the computing system 206 via the communication module 252.

[0225] In some implementations, the reusable module 250 includes a communications module 252 that can be disabled. For example, a healthcare provider or the patient themselves may be able to disable the functionality of the communications module 252 to prevent wireless transmission of patient physiological data from the sensor assembly 202 to, for example, the computing system 206 or the network 1620. As described herein, such wireless transmission of patient physiological data may be transmitted via wireless communications protocols including, but not limited to, Wi-Fi, ZigBee, Lo-Fi, Bluetooth, Zwave, MiWI, near field communication (NFC), etc. In some implementations, the functionality of the communications module 252 can be remotely enabled or disabled.

[0226] In some cases, reusable module 250 (or processor 254 of reusable module 250) may generate and provide a notification when it determines that the storage capacity of memory 256 meets a predetermined condition. For example, the predetermined condition may be a percentage of available storage in memory 256 (e.g., 10% or less of available storage). In another example, the predetermined condition may be an estimated duration for which sensor assembly 202 can collect and store data in memory 256 (e.g., one day's worth or less of patient physiological data).

[0227] The notification may be provided to the patient using the sensor assembly 202 (e.g., in the patient's home) or to a healthcare provider with access to the sensor assembly 202. The sensor assembly 202 (e.g., the reusable module 250 or the disposable module 220) may have an LED or display that can display a notification regarding the storage capacity of the memory 256. Additionally or alternatively, the sensor assembly 202 (or the processor 254 of the reusable module 250) may send a notification, for example, to a computing device of the healthcare provider, e.g., via the network 1620 or the computing device 206. The notification may include a message indicating to the patient or healthcare provider that the memory 256, for example, is almost full. The notification advantageously allows a patient using the sensor assembly 202, for example, to send the reusable module 250 with the patient physiological data stored thereon to a healthcare provider and / or request another reusable module 250, or to allow a healthcare provider to identify a patient having a reusable module 250 that needs to be replaced. After identifying a patient who has a reusable module 250 that needs to be replaced, the healthcare provider can contact the patient and instruct them to either visit a healthcare facility, e.g., a hospital, to submit the reusable module 250 and receive a new reusable module 250, or to have the reusable module 250 that needs to be replaced sent to the healthcare facility, e.g., via mail.

[0228] 17 illustrates an exemplary environment 1700 between a reusable module 250 and a user computing device 1750. In the example shown in FIG. 17, the reusable module 250 can be connected to the user computing device 1750 via a terminal 1710 and a cable 1720. The user computing device 1750 can include a desktop computer, a tablet, a laptop computer, a mobile communication device, etc.

[0229] The cable 1720 can enable transmission of data between the terminal 1710 and the user computing device 1750. In some implementations, the cable 1720 is optional and the terminal 1710 can communicate with the user computing device 1750 wirelessly.

[0230] The terminal 1710 can receive and establish communication with the reusable module 250. In some implementations, the terminal 1710 can detect communication with the reusable module 250 and initiate a transfer of patient physiological data (i.e., patient physiological data stored in the memory 256 of the reusable module 250) from the reusable module 250 to the terminal 1710. Alternatively, the reusable module 250 (or the processor 254 of the reusable module 250) can detect communication with the terminal 1710 and initiate a transfer of patient physiological data (i.e., patient physiological data stored in the memory 256 of the reusable module 250) from the reusable module 250 to the terminal 1710.

[0231] In some implementations, user input may cause or enable data transfer between the reusable module 250 and the terminal 1710. For example, the terminal 1710 detects connection with the reusable module 250 and sends a notification to the user computing device 1750. The notification includes a request for data transfer between the reusable module 250 and the terminal 1710 (and / or the user computing device 1750) and prompts user input to allow or deny the data transfer. If the user provides user input allowing the data transfer, the data transfer between the reusable module 250 and the terminal 1710 can occur. If the user provides user input denying the data transfer, the data transfer between the reusable module 250 and the terminal 1710 may not occur. After receiving the patient physiological data from the reusable module 250, the terminal 1710 can relay the data to the user computing device 1750.

[0232] 17, a user computing device 1750 can be connected to the network 1620. The user computing device 1750 can transmit data received from the reusable module 250 to the network 1620 so that it can be further analyzed, processed, or stored.

[0233] The user computing device 1750 may be located remotely from the patient using the sensor assembly 202. As described herein, the patient may be located remotely from a healthcare facility, e.g., a hospital, for remote patient monitoring. Such remote monitoring of the patient may be advantageous in reducing or eliminating the possibility of transmission of diseases, such as COVID-19, between the patient and the healthcare provider. In some implementations, the user computing device may be the patient's desktop computer, tablet, laptop computer, or mobile communication device, e.g., a smartphone. Thus, the terminal 1710 may be located in proximity to the patient, e.g., a desktop computer. The terminal 1710 may facilitate the transfer of patient physiological data between the sensor assembly 202 and the patient's desktop computer, which may then transmit the data to the network 1620, as described herein. Such a configuration may advantageously prevent delays caused, for example, by the patient sending their sensor system 202 to their healthcare provider or by the patient visiting their healthcare provider to submit the sensor system 202. Additionally, this may enable data transmission to the patient's home, thereby preventing potentially contaminated reusable modules 250 from being sent to or entering a healthcare facility (e.g., a hospital), further reducing the potential for transmission of diseases such as COVID-19.

[0234] term Numerous variations in embodiments beyond those described herein will be apparent from this disclosure. For example, depending on the embodiment, certain acts, events, or functions of any of the algorithms described herein may be performed in a different order, or may be added, intermixed, or excluded entirely (e.g., not all acts or events described may be required to implement an algorithm). Furthermore, in some embodiments, acts or events may occur simultaneously rather than sequentially, for example, through multithreading, interrupt processing, or multiple processors or processor cores, or other parallel architectures. Furthermore, various tasks or processes may be performed by different machines and / or computing systems that may work together.

[0235] The various illustrative logic blocks, modules, and algorithm steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, the above description generally describes various illustrative components, blocks, modules, and steps 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.

[0236] The various illustrative logic blocks and modules described in connection with the embodiments disclosed herein may be implemented or performed by machines such as general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any various combinations of the above elements designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, 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 embodiment, 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. The computing environment can include any type of computer system, including, but not limited to, computer systems based on microprocessors, mainframe computers, digital signal processors, portable computing devices, device controllers, or computational engines within appliances.

[0237] The steps of a method, process, or algorithm described in connection with the embodiments 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. In alternative embodiments, 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.

[0238] Conditional language used herein, particularly "can," "may," "may," "for example," and the like, is generally intended to convey that some embodiments include certain features, elements, and / or conditions, and that other embodiments do not include those features, elements, and / or conditions, unless otherwise specified or understood within the context of use. Thus, such conditional language is generally not intended to imply that features, elements, and / or conditions are required for one or more embodiments, or that one or more embodiments necessarily include logic for determining whether those features, elements, and / or conditions are included or should be implemented in any particular embodiment, with or without authorial input or direction. Terms such as "comprise," "include," "have," and the like are synonymous and used in an open-ended, inclusive manner and do not exclude additional elements, features, acts, operations, etc. Furthermore, the term "or" is used in its inclusive sense (rather than exclusive), whereby, when used to connect a list of elements, "or" refers to one, some, or all of the elements in the list. Furthermore, as used herein, the term "each" has its ordinary meaning, but can also refer to any subset of the set of elements to which the term "each" applies.

[0239] While the foregoing detailed description has shown, described, and pointed out novel features applicable to various embodiments, it will be understood that various omissions, substitutions, and changes in the form and details of the illustrated systems, devices, or methods may be made without departing from the spirit of the disclosure. As will be recognized, some embodiments described herein may be embodied in forms that do not provide all of the features and benefits described herein, since some features may be used or practiced separately from other features.

[0240] The term "and / or" as used herein has its broadest and least limiting meaning, i.e., the present disclosure includes A only, B only, both A and B, or either A or B, but does not necessarily require both A and B, nor does it necessarily require one A or one B. As used herein, the phrase "at least one of" A, B, "and" C should be interpreted to mean the logical A or B or C, using a non-exclusive logical OR.

[0241] The apparatus and methods described herein may be implemented by one or more computer programs executed by one or more processors. The computer programs include processor-executable instructions stored on a non-transitory tangible computer-readable medium. The computer programs may also include stored data. Non-limiting examples of non-transitory tangible computer-readable media are non-volatile memory, magnetic storage, and optical storage.

[0242] While the above disclosure has been described in terms of certain preferred embodiments, other embodiments will be apparent to those skilled in the art from the disclosure herein. Additionally, other combinations, omissions, substitutions, and modifications will be apparent to those skilled in the art in light of the disclosure herein. Accordingly, the present invention is not limited by the description of the preferred embodiments, but should be defined by reference to the claims. [Explanation of symbols]

[0243] 100 Sensor System 106, 206 Computing devices, computing systems 110 patients 130, 230, 230A cables 140A, 140B, 140C, 140D, 240, 240A, 240B, 340 Sensors 202 Sensor system, sensor assembly 202A, 202B, 202C, 202D Sensor Assemblies 204 Wireless Communication, First Wireless Communication 208 Display 220 Disposable Module, Disposable Device 220A Disposable Module 222, 222A, 222B Docks 224 Battery 226 memory 228 Electrical Contacts 242 Emitter 244 detector 250 Reusable Modules, Reusable Dongles 250A, 250B, 250C, 250D Reusable Modules 252 Antenna 254 processors 256 memory 258 Electrical Contacts 300, 300A, 300B housing 302 strap loop 304, 304A, 304B retainer 306 Cable Retainer 308 Strap 310 Fastener 310a, 310b electrical contacts 314 Battery Circuit 316 Support Plate 318 Cover 320 flex circuit 322 Groove 324 Protrusion 326 Legs 328 slot 330 Gasket 331 hollow 332 Opening 360 support 362 Opening 500 extension 600 Long and thin members 602 Tip 604 Opening 606 Electrical Contacts 608 Main Unit 700 First Strap 700A, 700B, 700C Straps 702 Second Strap 704 Opening 706, 706A, 706B fasteners 708, 708A Extension, Extender 710 Hook 712 gloves 750 Medical Band 752 Patient Identification Information 754 Barcode 756 Drug Information 800 dongle 802 Main Unit 804 Connector 806 Cable 808 Groove 850 holder 940 slot 1300 mobile devices 1302 Pair Buttons 1304 screens 1308 Home button 1310 Numerical Parameters 1312 History button 1314 Graph display 1400 Operational Data 1402 Sensor Life Data 1404 Sensor Usage Information 1408 Functions 1500, 1500B Backup Power Device 1500A Backup Power Device, Backup Power Supply 1502 Holder 1600, 1600a, 1600b, 1600c Patient Monitoring Devices 1602 communication module 1604 Storage Devices 1606 Sensor Assembly 1608 Wireless Communications 1610 Wireless Communications 1612 Wireless Communications 1620 Network 1700 Environment 1710 terminal 1720 Cable 1750 computing devices H1, H2 height L1, L2 relative position

Claims

1. 1. A system for collecting physiological data from a patient, comprising: A disposable module, a sensor element configured to collect physiological data from the patient; a second memory configured to store operational data associated with the sensor element; Battery and a disposable module comprising: A reusable module comprising: a processor; a first memory; a wireless communication module configured to establish wireless communication with the patient monitoring system; a reusable module comprising: Equipped with the first memory of the reusable module is configured to store the physiological data; the processor of the reusable module is configured to receive the physiological data from the sensor element of the disposable module when the reusable module is coupled to the disposable module; the reusable module does not include a battery, and the battery of the disposable module is configured to provide power to the reusable module when the disposable module is coupled to the reusable module; a lifespan of a disposable module is determined by a processor of the reusable module based at least in part on the operational data and the lifespan of the battery of the disposable module, the lifespan of the disposable module representing an expected operating time of the disposable module; the life span of the disposable module is automatically updated by the processor of the reusable module when a patient condition changes or an operating condition for the disposable module changes; detecting a change in the patient condition, which causes an increase in power consumption by the disposable module, triggering collection of physiological data at a higher accuracy than before the detection; A system configured as follows.

2. The system of claim 1 , wherein the disposable module comprises a dock, the dock coupled to an attachment mechanism and a housing, the housing containing the second memory and the battery.

3. The system of claim 2 , wherein the sensor element is contained within the housing.

4. The system of claim 2 , wherein the sensor element is coupled to the housing via a cable assembly.

5. 5. The system of claim 1, wherein the processor of the reusable module transmits a sensor signal to the sensor element of the disposable module, the sensor signal causing the sensor element to collect the physiological data from the patient.

6. 6. The system of claim 1, wherein the wireless communication module is configured to establish the wireless communication with the patient monitoring system when located within a predetermined distance from the patient monitoring system.

7. 7. The system of claim 6, wherein the wireless communication module is configured to transmit identification information to the patient monitoring system when located at the predetermined distance from the patient monitoring system.

8. 8. The system of claim 7, wherein the patient monitoring system creates an association with the wireless communication module upon receiving the identification information from the wireless communication module.

9. 8. The system of claim 7, wherein the identification information includes an identifier that uniquely identifies the disposable module, and wherein the patient monitoring system uses the identifier to establish the wireless communication with the reusable module.

10. 10. The system of claim 1, wherein the disposable module comprises an attachment mechanism configured to couple the disposable module to the patient.

11. The system of claim 10 , wherein the attachment mechanism is a medical band.

12. The system of claim 10 , wherein the attachment mechanism includes a radio frequency identifier.

13. 13. The system of claim 1, wherein the first memory of the reusable module is capable of storing the physiological data for about 6 hours to about 30 days.

14. 14. The system of claim 1, wherein the first memory of the reusable module stores the physiological data for a length of time before establishing or detecting the wireless communication, the length of time being specified by a user.

15. 15. The system of claim 14, wherein the first memory of the reusable module stores a default length of time, and wherein the first memory of the reusable module is configured to store the physiological data for the default length of time before the wireless communication module establishes the wireless communication when the length of time is not specified.

16. The system of claim 1 , wherein the physiological data includes health-related events related to the patient.

17. 17. The system of claim 1, wherein the physiological data is collected and stored in the second memory of the disposable module when an abnormality is detected.

18. 18. The system of claim 17, wherein the abnormality comprises at least one of a low blood pressure reading, a high blood pressure reading, a low respiratory rate reading, a high respiratory rate reading, a low blood oxygen saturation reading, an irregular heartbeat, a consistently low or low blood oxygen saturation reading, a low heart rate, or a high heart rate.

19. 19. The system of claim 1, wherein the processor of the reusable module is configured to transmit the physiological data to local or remote storage when wireless communication between the wireless communication module and an online server is established.

20. 20. The system of claim 19, wherein the transmitting of the stored physiological data occurs automatically or manually.

21. 21. The system of claim 1, wherein the fidelity of the physiological data stored in the first memory is variable.

22. 22. The system of claim 21, wherein the fidelity of the stored physiological data varies based at least in part on a length of time designated for storing the physiological data in the first memory of the reusable module.

23. 22. The system of claim 21, wherein the fidelity of the stored physiological data varies based at least in part on a type of physiological data or a type of health-related event.

24. 24. The system of claim 1, wherein the fidelity of the physiological data collected by the sensor elements is variable.

25. 25. The system of claim 24, wherein the fidelity of the physiological data collected by the sensor element varies based at least in part on a length of time designated for storing the physiological data in the first memory of the reusable module.

26. 25. The system of claim 24, wherein the fidelity of the stored physiological data collected by the sensor elements varies based at least in part on a type of physiological data or a type of health-related event.

27. 27. The system of claim 1, wherein the physiological data stored in the first memory of the reusable module is downloaded when the battery of the disposable module is depleted.

28. 28. The system of claim 1, wherein the first memory of the reusable module stores the physiological data collected by the sensor element from the time the reusable module is attached to the disposable module until the time the reusable part is detached from the disposable module or the battery of the disposable module fails.

29. 1. A system for collecting physiological data from a patient, comprising: A reusable module comprising: a processor; a first memory; a wireless communication module configured to establish wireless communication with the patient monitoring system; a reusable module comprising: A disposable module, a sensor element configured to collect physiological data from the patient; a second memory configured to store operational data associated with the sensor element; and Battery and a disposable module comprising: Equipped with the disposable module is validated by the processor of the reusable module based at least in part on the operational data; the first memory is configured to store the physiological data collected by the sensor element of the disposable module; the processor of the reusable module is configured to receive the physiological data from the sensor element of the disposable module when the reusable module is coupled to the disposable module; the reusable module does not include a battery, and the battery of the disposable module is configured to provide power to the reusable module when the disposable module is coupled to the reusable module; a lifespan of a disposable module is determined by a processor of the reusable module based at least in part on the operational data and the lifespan of the battery of the disposable module, the lifespan of the disposable module representing an expected operating time of the disposable module; the life span of the disposable module is automatically updated by the processor of the reusable module when a patient condition changes or an operating condition for the disposable module changes; detecting a change in the patient condition, which causes an increase in power consumption by the disposable module, triggering collection of physiological data at a higher accuracy than before the detection; A system configured as follows.

30. 30. The system of claim 29, wherein the operational data includes sensor type information associated with the disposable module.

31. 31. The system of claim 30, wherein the sensor type information indicates one or more types of sensors associated with the disposable module.

32. 32. The system of claim 30, wherein a reusable module is associated with a sensor type, and the disposable module is validated by the processor of the reusable module based at least in part on a comparison of the sensor type associated with the reusable module with sensor type information associated with the disposable module.

33. 33. The system of any one of claims 29 to 32, wherein the lifespan of the disposable module includes sensor usage information and one or more functions, and the lifespan of the disposable module is stored in the second memory of the disposable module.

34. 34. The system of any one of claims 29 to 33, wherein the physiological data is stored in the first memory for a length of time.

35. 35. The system of claim 34, wherein the length of time ranges from about 6 hours to about 30 days.

36. 36. The system of any one of claims 34 to 35, wherein the length of time is configurable via settings provided by a healthcare provider.

37. 36. The system of claim 34, wherein the first memory stores a default length of time, and wherein the first memory is configured to store the physiological data for the default length of time before the wireless communication module establishes the wireless communication when the length of time is not specified.

38. 38. The system of any one of claims 29 to 37, wherein the physiological data includes health-related events related to the patient.

39. 39. The system of any one of claims 29 to 38, wherein the physiological data is stored when an abnormality is detected.

40. 40. The system of claim 39, wherein the abnormality comprises at least one of a low blood pressure reading, a high blood pressure reading, a low respiratory rate reading, a high respiratory rate reading, a low blood oxygen saturation reading, an arrhythmia, a consistently low or low blood oxygen saturation reading, a low heart rate, or a high heart rate.

41. 41. The system of any one of claims 29 to 40, wherein the processor of the reusable module is configured to transmit the stored physiological data to local or remote storage via the wireless communication module when wireless communication between the wireless communication module and an online server is established.

42. 42. The system of claim 41, wherein the transmitting of the stored physiological data occurs automatically or manually.

43. 43. The system of any one of claims 29 to 42, wherein the fidelity of the physiological data stored in the first memory is variable.

44. 44. The system of claim 43, wherein the fidelity of the stored physiological data varies based at least in part on a length of time designated for storing the physiological data in the first memory.

45. 44. The system of claim 43, wherein the fidelity of the stored physiological data varies based at least in part on a type of physiological data or a type of health-related event.

46. 46. ​​The system of any one of claims 29 to 45, wherein the fidelity of the physiological data collected by the sensor elements is variable.

47. 47. The system of claim 46, wherein the fidelity of the physiological data collected by the sensor element varies based at least in part on a length of time designated for storing the physiological data in the first memory.

48. 47. The system of claim 46, wherein the fidelity of the stored physiological data collected by the sensor elements varies based at least in part on a type of physiological data or a type of health-related event.

49. 49. The system of any one of claims 29 to 48, wherein the first memory stores the physiological data collected by the sensor element from the time the reusable module is attached to the disposable module until the reusable part is detached from the disposable module or the battery of the disposable module fails.

Images