Patient-worn wireless physiological sensor with pairing functionality

Description

FIELD OF THE DISCLOSURE

The present disclosure relates to the field of pairing of wireless communication devices. More specifically, the disclosure describes among other things a portable wireless device that communicates with a second device capable of wireless communication with paired electronic devices.

BACKGROUND

In clinical settings, such as hospitals, nursing homes, convalescent homes, skilled nursing facilities, post-surgical recovery centers, and the like, patients are frequently monitored using one more different types of physiological sensors. Various types of sensors include a magnetometer that detects patient movement or orientation to track and prevent patient ulcers, a temperature sensor, an acoustic respiration sensor, an electrocardiogram (ECG) sensor, an electroencephalography (EEG) sensor, one or more pulse oximetry sensors, a moisture sensor, a blood pressure sensor, and an impedance sensor, among other sensors.

Wires leading to and from traditional physiological sensors inhibit patient movement and make it difficult to provide care to a patient. Often sensors are accidentally removed by patient movement. At other times, sensors must be moved or replaced when a patient is moved to a different location or when certain types of care are provided to the patient. Wireless sensors provide a solution to the patient movement and access. However, in busy hospital environments with non-technical staff operating these wireless devices, it can be difficult to correctly configure wireless sensors for communication with the correct monitors.

Similarly, other wireless devices including consumer devices such as, but not limited to, speakers, phones, headphones, watches, keyboards, mice, and so forth, capable of being paired have similar issues. These devices are often used by non-technically oriented users that encounter cumbersome pairing requirements.

SUMMARY

For purposes of summarizing the disclosure, certain aspects, advantages and novel features have been described herein. It is to be understood that not necessarily all such advantages can be achieved in accordance with any particular embodiment disclosed herein. Thus, the embodiments disclosed herein can be embodied or carried out in a manner that achieves or optimizes one advantage or group of advantages as taught or suggested herein without necessarily achieving others.

In certain embodiments, a system for electronically pairing a wireless sensor with a patient monitoring device can include a patient monitoring device, a wireless sensor, and at least one hardware processor. The patient monitoring device can include a first display. The wireless sensor can include a button configured to activate a pairing mode that enables the wireless sensor to electronically pair with the patient monitoring device. The wireless sensor can further comprise an optical detector configured to detect light based signals. The hardware processor can further generate a visual signal from the first display. In some embodiments, the hardware processor can detect the visual signal with the optical detector of the wireless sensor. The hardware processor can associate the wireless sensor with the patient monitoring device based on the detected visual signal, thereby pairing the wireless sensor with the patient monitoring device. The hardware processor can further transmit a confirmation signal from the wireless sensor to indicate that association is complete. The hardware processor can configure the wireless sensor to enter into a patient parameter sensing mode of operation after the association of the wireless sensor with the patient monitoring device.

The system of the preceding paragraph can have any sub-combination of the following features: where the first display is of a first size and the wireless sensor is of a second size, where the second size of the wireless sensor is smaller than the first size of the first display; where the size of the wireless sensor corresponds to a shape of a base of the wireless sensor; where the wireless sensor does not require a separate antenna or any additional components for the pairing with the patient monitoring device; where the wireless sensor does not use a wireless communication protocol for the pairing with the patient monitoring device; where the wireless sensor does not use a wireless communication protocol including a Bluetooth protocol, wifi protocol, or a zigbee protocol; where the one or more hardware processors are configured to detect a shape of the wireless sensor when the wireless sensor is placed directly on the first display and in response to the detected shape, associate the wireless sensor with the patient monitoring device; and where the one or more hardware processors are configured to generate a pattern on the first display and associate the wireless sensor with the patient monitoring device based on a successful placement of the wireless sensor on the first display in relation to the generated pattern.

Additionally, in certain embodiments, a system for electronically pairing a wireless sensor with a patient monitoring device can include a patient monitoring device. The system can include a wireless sensor. The wireless sensor can include a button configured to activate a pairing mode that enables the wireless sensor to electronically pair with the patient monitoring device. The system can include one or more hardware processors. The hardware processor can further generate a signal from the patient monitoring device. The hardware processor can also detect the signal with a detector of the wireless sensor. In some embodiments, the hardware processor can associate the wireless sensor with the patient monitoring device based on the detected signal, thereby pairing the wireless sensor with the patient monitoring device. The hardware processor can also transmit a confirmation signal from the wireless sensor to indicate that association is complete. Moreover, the hardware processor can configure the wireless sensor to enter into a patient parameter sensing mode of operation after the association of the wireless sensor with the patient monitoring device.

The system of the preceding paragraph can have any sub-combination of the following features: where the wireless sensor does not require a separate antenna or any additional components for the pairing with the patient monitoring device; where the wireless sensor does not use a wireless communication protocol for the pairing with the patient monitoring device; where the detector comprises a piezoelectric element; where the signal comprises an acoustic signal and where the wireless sensor is configured to detect the acoustic signal with the piezoelectric element; and where the detector comprises an optical detector and where the signal comprises a visual signal and the wireless sensor is configured to detect the visual signal with the optical detector.

In certain embodiments, a method for electronically pairing a wireless sensor with a patient monitoring device can include generating a signal from the patient monitoring device. The method can also include detecting the signal with a detector of the wireless sensor. In some embodiments, the method can include associating the wireless sensor with the patient monitoring device based on the detected signal, thereby pairing the wireless sensor with the patient monitoring device. Furthermore, the method can include transmitting a confirmation signal from the wireless sensor to indicate that association is complete. The method can also include configuring the wireless sensor to enter into a patient parameter sensing mode of operation after the association of the wireless sensor with the patient monitoring device.

The method of the preceding paragraph can have any sub-combination of the following features: where the wireless sensor does not require a separate antenna or any additional components for the pairing with the patient monitoring device; where the wireless sensor does not use a wireless communication protocol for the pairing with the patient monitoring device; where the detector comprises a piezoelectric element; where the detector comprises an optical detector; further generating a pattern on a first display of the patient monitoring device, where the association is further based on a successful placement of the wireless sensor on the first display in relation to the generated pattern.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a schematic assembled perspective view of a wireless sensor.

FIG. 1B is a schematic exploded perspective view of a wireless sensor.

FIG. 2A is a schematic perspective view of a wireless sensor.

FIG. 2B is a schematic perspective view of a wireless sensor and a mobile device for pairing.

FIGS. 3A-3B are perspective views of a wireless sensor and a patient monitor pairing.

FIG. 4 is a flow diagram describing a process to pair a wireless sensor with a patient monitor.

FIG. 5 is a flow diagram describing a process to pair a wireless sensor with a patient monitor.

FIG. 6 is a flow diagram describing a process to pair a first wireless device with a second wireless device.

FIG. 7 is a flow diagram describing a process to pair a first wireless device with a second wireless device.

FIG. 8 is a schematic perspective view of the disclosed wireless sensor and a mobile device for pairing.

FIG. 9 is a schematic perspective view of the disclosed wireless sensor and a car console for pairing.

DETAILED DESCRIPTION

FIG. 1A is a schematic assembled perspective view of wireless sensor 102. The wireless sensor 102 may also be referred to herein as “a wireless physiological sensor 102,” “a patient-worn sensor 102,” “a movement sensor 102,” and “a wearable wireless sensor 102.” The wireless sensor 102 includes one or more sensors configured to measure the patient's position, orientation, and motion. Also illustrated in FIG. 1A is a button or switch 124 located on a top portion of the housing 150. The button or switch 124 can be used to change modes of the wireless sensor 102. For example, pressing and holding the button or switch 124 can cause the wireless sensor 102 to switch into a pairing mode of operation. The pairing mode is used to associate the wireless sensor 102 with a mobile device 210 as shown in FIGS. 2A-B or a bedside patient monitor 310 as shown in FIGS. 3A-B. Wireless sensor 102 may include one or more detecting elements such as: a magnetometer which may also be referred to as a compass, a temperature sensor, an acoustic respiration sensor, an electrocardiogram (ECG) sensor, an electroencephalography (EEG) sensor, one or more pulse oximetry sensors, a moisture sensor, a blood pressure sensor, and an impedance sensor.

The magnetometer may be a three-dimensional magnetometer that provides information indicative of magnetic fields, including the Earth's magnetic field. A skilled artisan will understand that the accelerometer, gyroscope, and magnetometer can be integrated into a single hardware component such as an inertial measurement unit. The wireless sensor 102 may be configured to calculate the three-dimensional position and orientation of an object derived from inputs from three sensors attached to the object: an accelerometer configured to measure linear acceleration along three axes; a gyroscope configured to measure angular velocity around three axes; and a magnetometer configured to measure the strength of a magnetic field (such as the Earth's magnetic field) along three axes. The three sensors may attach to the wireless sensor 102 which is affixed to the patient. The sensors may be sampled at a rate between approximately 10 Hz and approximately 100 Hz. One skilled in the art will appreciate that the sensors can be sampled at different rates without deviating from the scope of the present disclosure. The sampled data from the three sensors, which provide nine sensor inputs, are processed to describe the patient's position and orientation in three-dimensional space. The patient's position and orientation are described in terms of Euler angles as a set of rotations around a set of X-Y-Z axes of the patient.

An acoustic respiration sensor can be used to sense acoustic and/or vibrational motion from the patient's body (e.g., the patient's chest) that are indicative of various physiologic parameters and/or conditions, including without limitation, heart rate, respiration rate, snoring, coughing, choking, wheezing, and respiratory obstruction (e.g., apneic events). The ECG sensor can be used to measure the patient's cardiac activity. The ECG sensor may include two electrodes and a single lead. The pulse oximetry sensor(s) can be used to monitor the patient's pulse oximetry, a widely accepted noninvasive procedure for measuring the oxygen saturation level of arterial blood, an indicator of a person's oxygen supply. A typical pulse oximetry system utilizes an optical sensor clipped onto a portion of the patient's body (such as, for example, a fingertip, an ear lobe, a nostril, and the like) to measure the relative volume of oxygenated hemoglobin in pulsatile arterial blood flowing within the portion of the body being sensed. Oxygen saturation (SpO2), pulse rate, a plethysmograph waveform, perfusion index (PI), pleth variability index (PVI), methemoglobin (MetHb), carboxyhemoglobin (CoHb), total hemoglobin (tHb), glucose, and/or otherwise can be measured and monitored using the pulse oximetry sensor(s). The moisture sensor can be used to determine a moisture content of the patient's skin which is a relevant clinical factor in assessing the patient's risk of forming a pressure ulcer. The impedance sensor can be used to track fluid levels of the patient. For example, the impedance sensor can monitor and detect edema, heart failure progression, and sepsis in the patient.

FIG. 1B is a schematic exploded perspective view of wireless sensor 102 including a bottom base 110, a removable battery isolator 120, a mounting frame 130, a circuit board 140, a housing 150, and a top base 160. The bottom base 110 is a substrate having a top surface on which various components of the wireless sensor 102 are positioned, and a bottom surface that is used to affix the wireless sensor 102 to the patient's body. The bottom base 110 and top base 160 can be made of medical-grade foam material such as white polyethylene, polyurethane, or reticulated polyurethane foams, to name a few. As illustrated in FIG. 1A, the bottom base 110 and the top base 160 are each in a substantially oval shape, with a thickness of approximately 1 mm. The top base 160 includes a cut-out 162 through which the housing 150 fits during assembly. A skilled artisan will understand that there are numerous sizes and shapes suitable for the top and bottom bases 110 and 160 that can be employed without departing from the scope of the present disclosure. The bottom surface of the bottom base 110 is coated with a high tack, medical-grade adhesive, which when applied to the patient's skin, is suitable for long-term monitoring, such as, for example two days or longer. Portions of the top surface of the bottom base 110 are also coated with a medical-grade adhesive, as the bottom base 110 and the top base 160 are adhered together during assembly of the wireless sensor 102. The bottom base 110 may have apertures 112 and 114. These apertures 112 and 114 may permit transmission of thermal energy, electrical energy, light, sound, or any other input to the wireless sensor 102.

The removable battery isolator 120 is a flexible strip made of an electrically insulating material that serves to block electrical communication between the battery 144 and an electrical contact (not shown) on the circuit board 140. The battery isolator 120 is used to preserve battery power until the wireless sensor 102 is ready for use. The battery isolator 120 blocks electrical connection between the battery 144 and the circuit board 140 until the battery isolator 120 is removed from the wireless sensor 102. The battery isolator 120 can be made of any material that possesses adequate flexibility to be slidably removed from its initial position and adequate dielectric properties so as to electrically isolate the battery 144 from the circuit board 140. For example, the battery isolator 120 can be made of plastic, polymer film, paper, foam, combinations of such materials, or the like. The battery isolator 120 includes a pull tab 122 that extends through a slot 152 of the housing 150 when the wireless sensor 102 is assembled. The pull tab 122 can be textured to provide a frictional surface to aid in gripping and sliding the pull tab 122 out of its original assembled position. Once the battery isolator 120 is removed the battery 144 makes an electrical connection with the electrical contact to energize the electronic components of the wireless sensor 102.

The mounting frame 130 is a structural support element that helps secure the battery 144 to the circuit board 140. The mounting frame 130 has wings 132 that, when assembled are slid between battery holder 142 and the battery 144. Additionally, the mounting frame 130 serves to provide rigid structure between the circuit board 140 and the bottom base 110. The rigid structure, which may include an acoustic respiratory sensor, may transmit vibrational motion (vibrations) emanating from the patient (such as, for example, vibrational motions related to respiration, heartbeat, snoring, coughing, choking, wheezing, respiratory obstruction, and the like) to the accelerometer 149 positioned on the circuit board 140. The mounting frame 130 may have an aperture 134 that extends through the mounting frame 130. The aperture 134 may be aligned with the aperture 114 in the bottom base 110 as described above. The aperture 134 may permit transmission of thermal energy, electrical energy, light, sound, or any other input to the wireless sensor 102. The aperture 134 may be filled with a thermally conductive material.

A battery holder 142 is attached to two sides of the top portion circuit board 140 and extends (forming a support structure) under the bottom side of the circuit board 140 to hold the battery 144 in position relative to the circuit board 140. An electrical connection between the anode of the battery 144 and the circuit board 140 is made by way of the battery holder which is in electrical contact with the anode of the battery 144 and the circuit board 140. The cathode of the battery 144 is positioned to touch a battery contact (not shown) on the bottom side of the circuit board 140.

The housing 150 is a structural component that serves to contain and protect the components of the wireless sensor 102. The housing 150 can be made of any material that is capable of adequately protecting the electronic components of the wireless sensor 102 such as thermoplastics and thermosetting polymers. The housing 150 includes a slot 152 through which the battery isolator 120 is inserted during assembly. The housing 150 also includes a rim 154 that extends around the outer surface of the housing 150. The rim 154 is used to secure the housing 150 in position relative to the bottom base 110 and the top base 160 when the wireless sensor 102 is assembled.

Assembly of the wireless sensor 102 is as follows: the circuit board 140 and battery holder 142 holding the battery 144 are placed into the housing 150. The wings 132 of the mounting frame 130 are inserted in between the battery 144 and the battery holder 142, so as to align the mounting frame 130 with the circuit board 140. The battery isolator 120 is positioned between the electrical contact and the battery 144. The pull tab 122 of the battery isolator 120 is then fed through the slot 152 in the housing 150. The top base 160 is then positioned over the housing 150. The rim 154 of the housing 150 adheres to the bottom surface of the top base 160, which is coated with high tack, medical-grade adhesive. The resulting partial assembly is positioned centrally onto the top surface of the bottom base 110, aligning the edges of the base top 160 with the edges of the base bottom 110. The bottom surface of the bottom base 110 is then coated with a high tack, medical-grade adhesive, and a release liner (not shown) is placed on the bottom surface of the bottom base 110 to protect the adhesive until it is time for use.

FIG. 2A is a perspective illustration of the patient monitoring system in a clinical setting. The patient monitoring system includes a wireless sensor 102 worn by a patient in proximity to mobile device 210. The mobile device 210 includes screen 220 that may be configured to transmit and receive a visual, optical, and/or light-based pairing signal. The pairing signal may contain a pattern containing a shape, color, or a combination of patterns. The pairing signal may involve displaying instructions on a screen 220 for a user to follow. The instructions may include the user placing a wireless sensor 102 of a particular shape and size in a certain position relative to the screen 220. The instructions may be displayed using an object 214 on the screen 220 to represent the silhouette of the wireless sensor 102. To follow the instructions, the user may hold the wireless sensor 102 and position the wireless sensor 102 according to the instructions. The user may place the wireless sensor 102 to resemble the relative position of the object 214 displayed on the screen 220 of the mobile device 210.

For example, the wireless sensor 102 and the mobile device 210 may include a detector that detects visual, optical, or light-based signals and another detector for detecting audio sound or a series of audio sounds. A detector may be configured to detect both visual and audio signals. The pairing signal may include a sequence of visual signals that is synchronized with a sequence of audio signals.

Additionally, the screen 220 may be configured to display motion instructions for a care provider to perform in order to generate motion signals representing a pairing signal. Mobile device 210 may also generate audio-based pairing signals using a speaker (not shown). The sounds may be tuned to a frequency within or outside of the range of human hearing and may comprise various rings or tones. Additionally, the mobile device 210 may have a port for connecting peripheral devices that may generate various signals such as current or voltage based signals. The pairing signal may take the form of an electrical signal.

FIG. 2B is a perspective illustration of the patient monitoring system in a clinical setting. The patient monitoring system includes a wireless sensor 202 worn by a patient in proximity to mobile device 210. The mobile device 210 includes screen 220 that may be configured to transmit a visual, optical, and/or light-based pairing signal. The pairing signal may contain a pattern containing a shape, color, or a combination of patterns. The pairing signal may involve displaying instructions on a screen 220 for a user to follow. The instructions may include the user placing a wireless sensor 202 of a particular shape and size in a certain position relative to the screen 220. The shape and size of the wireless sensor 202 may differ from the shape and size of the wireless sensor 102. The instructions may be displayed using an object 216 on the screen 220 to represent the silhouette of the wireless sensor 202. To follow the instructions, the user may hold the wireless sensor 202 and position the wireless sensor 202 according to the instructions. The user may place the wireless sensor 202 to resemble the relative position of the object 216 displayed on the screen 220 of the mobile device 210.

The pairing signal may contain a series of visual, optical, and/or light based signals. The series of signals may utilize variations in color, shade, shape, or visual patterns. The pairing signal may contain a series of flashes, wherein the flashes may vary in intensity or duration. Mobile device 210 may also generate audio-based pairing signals using a speaker (not shown). The sounds may be tuned to a frequency within or outside of the range of human hearing and may comprise various rings or tones. The pairing signal may comprise a combination of visual and audio signals. For example, the wireless sensor 102 and the mobile device 210 may include a detector that detects visual, optical, or light-based signals and another detector for detecting audio sound or a series of audio sounds. A detector may be configured to detect both visual and audio signals. The pairing signal may include a sequence of visual signals that is synchronized with a sequence of audio signals.

Additionally, the screen 220 may be configured to display motion instructions for a care provider to perform in order to generate motion signals representing a pairing signal. Additionally, the mobile device 210 may have a port for connecting peripheral devices that may generate various signals such as current or voltage based signals. The pair signal may take the form of an electrical signal.

Wireless sensor 202 may include a probe for taking non-invasive optical measurements. The probe may have an emitter for transmitting an optical signal and a detector for detecting the optical signal transmitted by the emitter. The probe may have a flexible circuit assembly with circuit paths to connect the emitter and the detector. The detector may be further configured to detect the pairing signal emitted by mobile device 210.

The wireless sensor 202 may also include a button or switch 204. The button or switch 204 can be used to change modes of the wireless sensor 202. For example, pressing and holding the button or switch 204 can cause the wireless sensor 202 to switch into a pairing mode of operation. The pairing mode is used to associate the wireless sensor 102 with a mobile device 210 or a bedside patient monitor 310.

FIG. 3A is a perspective illustration of the patient monitoring system in a clinical setting. The patient monitoring system includes a wireless sensor 102 worn by a patient in proximity to a bedside patient monitor 310 located at the side of a patient's bed. The bedside patient monitor 310 may include screen 312 that may be configured to transmit a visual, optical, and/or light-based pairing signal. The pairing signal may contain a pattern containing a shape, color, or a combination of patterns. The pairing signal may involve displaying instructions on a screen 312 for a user to follow.

The instructions may include the user placing a wireless sensor 102 of a particular shape and size in a certain position relative to the screen 312. The instructions may be displayed using an object 214 on the screen 312 to represent the silhouette of the wireless sensor 102. To follow the instructions, the user may hold the wireless sensor 102 and position the wireless sensor 102 according to the instructions. The user may place the wireless sensor 102 to resemble the relative position of the object 214 displayed on the screen 312 of the bedside patient monitor 310.

The pairing signal may contain a series of visual, optical, and/or light based signals. The series of signals may utilize variations in color, shade, shape, or visual patterns. Additionally, the pairing signal may contain a series of flashes, wherein the flashes may vary in intensity or duration. Additionally, the screen 312 may be configured to display motion instructions for a care provider to perform in order to generate motion signals representing a pairing signal. Bedside patient monitor 310 may also generate audio-based pairing signals using a speaker (not shown). The sounds may be tuned to a frequency within or outside of the range of human hearing and may comprise various rings or tones. Additionally, the bedside patient monitor 310 may have a port 316 for connecting peripheral devices that may generate various signals such as current or voltage based signals. The pairing signal may take the form of an electrical signal.

The patient monitor 310 may have a button or switch 317 can be used to activate the patient monitor 310 and place it in the pairing mode of operation. Similarly the buttons or switches 318, 319 can also be used to activate the patient monitor 310 and place it in the pairing mode of operation. This process is discussed more below. When the button/switch 317 is depressed and/or continuously held down, the patient monitor 310 may enter into the pairing mode of operation.

FIG. 3B is a perspective illustration of the patient monitoring system in a clinical setting. The patient monitoring system includes a wireless sensor 202 worn by a patient in proximity to a bedside patient monitor 310 located at the side of a patient's bed. The bedside patient monitor 310 may include screen 312 that may be configured to transmit a visual, optical, and/or light-based pairing signal. The pairing signal may contain a pattern containing a shape, color, or a combination of patterns. The pairing signal may involve displaying instructions on a screen 312 for a user to follow.

Similar to FIG. 3A, the instructions may include the user placing a wireless sensor 202 of a particular shape and size in a certain position relative to the screen 312. The instructions may be displayed using an object 216 on the screen 312 to represent the silhouette of the wireless sensor 202. To follow the instructions, the user may hold the wireless sensor 202 and position the wireless sensor 202 according to the instructions. The user may place the wireless sensor 202 to resemble the relative position of the object 216 displayed on the screen 312 of the bedside patient monitor 310.

Although described with respect to a bedside patient monitor 310, it is to be understood that mobile device 210 may also perform some or all of the functionality described in relation to bedside patient monitor 310. For example, wireless sensor 102 may pair with either the mobile device 210 or bedside patient monitor 310. Additionally, one skilled in the art will appreciate that numerous types of patient-specific information may be collected and analyzed by either the mobile device 210 or bedside patient monitor 310. Therefore, it is to be understood that patient monitoring system may be implemented with a mobile device 210 or a bedside patient monitor 310.

In some scenarios, it may be desirable to pair, or associate, the wireless sensor 102 with the bedside patient monitor 310 or mobile device 210 to avoid interference from other wireless devices and/or to associate patient-specific information (stored, for example, on the patient monitor 310) with the sensor data that is being collected and transmitted by the wireless sensor 102. Illustratively, such patient-specific information can include, by way of non-limiting example, the patient's name, age, gender, weight, identification number (e.g., social security number, insurance number, hospital identification number, or the like), admission date, length of stay, physician's name and contact information, diagnoses, type of treatment, perfusion rate, hydration, nutrition, pressure ulcer formation risk assessments, patient turn protocol instructions, treatment plans, lab results, health score assessments, and the like. One skilled in the art will appreciate that numerous types of patient-specific information can be associated with the described patient-worn sensor without departing from the scope of the present disclosure. Additionally, pairing the wireless sensor 102 with the mobile device 210 or bedside patient monitor 310 can be performed to provide data security and to protect patient confidentiality. Some wireless systems require the care provider to program the wireless sensor 102 to communicate with the correct mobile device 210 or bedside patient monitor 310. Other wireless systems require a separate token or encryption key and several steps to pair the wireless device 102 with the correct bedside patient monitors 310. Some systems require the token to be connected to the mobile device 210 or the bedside patient monitor 310, then connected to the wireless device 102, and then reconnected to the mobile device 210 or bedside patient monitor 310. In certain scenarios, it may be desirable to share wireless communication information between a wireless sensor 102 and a mobile device 210 or bedside patient monitor 310 without a separate token or encryption key. For security purposes, it may be desirable to use security tokens to ensure that the correct patient monitor 310 receives the correct wirelessly transmitted data. Security tokens prevent the mobile device 210 or bedside patient monitor 310 from accessing the transmitted data unless the wireless sensor 102 and mobile device 210 or patient monitor 310 share the same password. The password may be a word, passphrase, or an array of randomly chosen bytes.

FIG. 4 illustrates a method of associating a wireless sensor 102 with a mobile device 210 or a bedside patient monitor 310, which may be referred to as “pairing.” At block 402A, the wireless sensor 102 may be placed near the mobile device 210 or the bedside patient monitor 310 in preparation for receiving a pairing signal. A visual, optical, and/or light-based detector 146 of the wireless sensor 102 may be physically oriented and configured to receive a pairing signal in the form of a visual, optical, and/or light-based pairing signal. The pairing signal may contain a pattern containing a shape, color, or a combination of patterns. The pairing signal may contain a series of visual, optical, and/or light based signals. The series of signals may utilize variations in color, shade, shape, or visual patterns, Additionally, the pairing signal may contain a series of flashes, wherein the flashes may vary in intensity or duration. The signal may be unique to the wireless sensor 102 and the mobile device 210 or the bedside patient monitor 310. By using a pairing signal that uniquely identifies the wireless sensor 102 and the mobile device 210 or the bedside patient monitor 310, a secure connection may be established between the two paired devices.

Various types of sensors can be used with the pairing process of the present disclosure. For example, a pulse oximeter sensor can be paired by facing its light detector toward a bedside patient monitor screen 312 or mobile device screen 220 to receive a visual, optical, and/or light based signal. In another example, an ulcer sensor can be paired by receiving a pairing signal in the form of detected motion. Similarly, other types of wireless sensors can be paired using the included detectors. For example, an acoustic sensor can be paired based on audio signals emitted from the patient monitor 310. EEG and ECG wireless sensors can be paired using small electrical impulses from a special conductor included as part of the patient monitor 310. Other sensors can be paired in a similar fashion depending on the specific detectors included on the wireless sensors.

Returning to block 402A, the wireless sensor 102 may be placed in proximity to the mobile device 210 or the bedside patient monitor 310 such that the visual, optical, and/or light-based detector 146 may receive the visual, optical, and/or light-based pairing signal The visual, optical, and/or light-based pairing signal may have a pairing signal transmission range of up to approximately three inches. The visual, optical, and/or light-based pairing signal may have a pairing signal transmission range of up to approximately six inches. The visual, optical, and/or light-based pairing signal may have a pairing signal transmission range of up to approximately one foot (i.e., twelve inches) or farther. A skilled artisan will recognize that other ranges can be used for the pairing signal transmission range.

At block 404A the wireless sensor 102 is set to operate in a pairing mode. A user may begin by initiating the pairing mode of operation for the wireless sensor 102. This may include powering on the wireless sensor 102, switching the wireless sensor 102 to a special pairing state, and/or the like. For example, the wireless sensor 102 may include a battery isolator 120 which, when removed, activates the wireless sensor 102. Upon activation, the default mode of operation is the pairing mode. The wireless sensor 102 may have a button or switch 124 that can be used to activate the wireless sensor 102 and place it in the pairing mode of operation. For example, a depressible button or switch 124 can be located on the top portion of the housing 150. When the button or switch 124 is depressed and continuously held down, the wireless sensor 102 enters into the pairing mode of operation and remains in the pairing mode of operation for as long as the button or switch 124 is depressed. The wireless sensor 102 enters into the pairing mode by activating the visual, optical, and/or light-based sensor 146. Once activated, the optical sensor 146 may be configured to receive the visual, optical, and/or light-based pairing signal. Similarly, the wireless sensor 202 may have a button or switch 204 that can be used to activate the wireless sensor 202 and place it in the pairing mode of operation.

At block 404B, the mobile device 210 or bedside patient monitor 310 is set to operate in pairing mode. A user may begin by initiating the pairing mode of operation for the mobile device 210 or the bedside patient monitor 310. This may include powering on the mobile device 210 or the bedside patient monitor 310, switching the mobile device 210 or the bedside patient monitor 310 to a special pairing state, and/or the like. The bedside patient monitor 310 may have a button or switch 317 that can be used to activate the patient monitor 310 and place it in the pairing mode of operation. When the button or switch 317 is depressed and/or continuously held down, the patient monitor 310 enters into the pairing mode of operation. Similarly, the mobile device 210 may have a button or switch that can be used to activate the mobile device 210 and place it in the pairing mode of operation. When the button or switch is depressed and/or continuously held down, the mobile device 210 enters into the pairing mode of operation.

As reflected at block 406, the mobile device 210 or the bedside patient monitor 310 transmits a pairing signal to pair, or associate, with wireless sensor 102. The patient monitor screen 312 or mobile device screen 220 may be configured to emit a pairing signal. The mobile device screen 220 or patient monitor screen 312 may be configured to emit a visual, optical, and/or light-based pairing signal. The pairing signal transmission is received by orienting the visual, optical, and/or light-based detector 146 of the wireless sensor 102 toward the mobile device screen 220 or the patient monitor screen 312. The limited range of the visual, optical, and/or light-based pairing signal helps to prevent unintended or incidental association of the wireless sensor 102 with a mobile device 210 or bedside patient monitor 310 that might be nearby but which is not intended to be paired with the wireless sensor 102. Such circumstances can occur in hospitals, healthcare facilities, nursing homes, and the like where wireless sensors 102 mobile devices 210, and bedside patient monitors 310 are located in close physical proximity to one another.

At block 408, the wireless sensor 102 detects the pairing signal from bedside patient monitor 310 or mobile device 210. Upon detection of the pairing signal, at block 410, the wireless sensor 102 associates with the bedside patient monitor 310 thereby configuring the wireless sensor 102 and mobile device 210 or the patient monitor 310 to communicate with each other. Once the pairing is completed, the wireless sensor 102 transmits a confirmation signal confirming that the patient-worn sensor 102 is associated with the mobile device 210 or the bedside patient monitor 310, thereby indicating that the pairing process has been successfully completed, as reflected in block 412. At block 414, the mobile device 210 or the bedside patient monitor 310 receives the confirmation signal. And at block 416A, the wireless sensor 102 exits the pairing mode of operation and enters into a patient parameter sensing mode of operation. Similarly, at block 416B, the mobile device 210 or the bedside patient monitor 310 enters a patient parameter sensing mode of operation.

FIG. 5 illustrates a method of associating a wireless sensor 102 with a mobile device 210 or the bedside patient monitor 310, which may be referred to as “pairing.” At block 502A, the wireless sensor 102 may be placed near the mobile device 210 or the bedside patient monitor 310 in preparation for receiving a pairing signal. For sensors that utilize an audio sensor, such as respirator sensor, the pairing signal may be an audio sound or a series of audio sounds. A sound or audio-based detector 147 of the wireless sensor 102 may be configured to receive a pairing signal in the form of a sound or audio-based pairing signal. The sounds may be tuned to a frequency within or outside of the range of human hearing and may comprise various rings, chimes, or tones. The series of audio sounds may utilize variations in volume or tone to transmit pairing information. The signal may be unique to the wireless sensor 102 and the mobile device 210 or the patient monitor 310. By using a pairing signal that uniquely identifies the wireless sensor 102 and the mobile device 210 or the patient monitor 310, a secure connection may be established between the two paired devices.

Various types of sensors can be used with the pairing process of the present disclosure. For example, a pulse oximeter sensor can be paired by facing its light detector toward a patient monitor display 312 or mobile device display 220 to receive a visual, optical, and/or light based signal. In another example, an ulcer sensor can be paired by receiving a pairing signal in the form of detected motion. Similarly, other types of wireless sensors can be paired using the included detectors. For example, an acoustic sensor can be paired based on audio signals emitted from the mobile device 210 or the bedside patient monitor 310. EEG and ECG wireless sensors can be paired using small electrical impulses from a special conductor included as part of the patient monitor 310. Other sensors can be paired in a similar fashion depending on the specific detectors included on the wireless sensors.

Returning to block 502A, the wireless sensor 102 may be placed in proximity to the mobile device 210 or the bedside patient monitor 310 such that the sound or audio detector 147 may receive the sound or audio-based pairing signal. The sound or audio-based pairing signal has a pairing signal transmission range of up to approximately three inches. The sound or audio-based pairing signal may have a pairing signal transmission range of up to approximately six inches. The sound or audio-based pairing signal may have a pairing signal transmission range of up to approximately one foot (i.e., twelve inches) or farther. A skilled artisan will recognize that other ranges can be used for the pairing signal transmission range.

At block 504A the wireless sensor 102 is set to operate in a pairing mode. A user may begin by initiating the pairing mode of operation for the wireless sensor 102. This may include powering on the wireless sensor 102, switching the wireless sensor 102 to a special pairing state, and/or the like. For example, the wireless sensor 102 may include a battery isolator 120 which, when removed, activates the wireless sensor 102. Upon activation, the default mode of operation is the pairing mode. The wireless sensor 102 may have a button or switch 124 that can be used to activate the wireless sensor 102 and place it in the pairing mode of operation. For example, a depressible button or switch 124 can be located on the top portion of the housing 150. When the button or switch 124 is depressed and continuously held down, the wireless sensor 102 enters into the pairing mode of operation and remains in the pairing mode of operation for as long as the button or switch 124 is depressed. The wireless sensor 102 enters into the pairing mode by activating the sound or audio-based sensor 147. Once activated, the sound or audio-based sensor 147 may be configured to receive the audio or sound-based pairing signal.

At block 504B, the mobile device 210 or the bedside patient monitor 310 is set to operate in pairing mode. A user may begin by initiating the pairing mode of operation for the mobile device 210 or the bedside patient monitor 310. This may include powering on the device, switching the device to a special pairing state, and/or the Ike. The bedside patient monitor 310 may have a button or switch 317 that can be used to activate the bedside patient monitor 310 and place it in the pairing mode of operation. When the button or switch 317 is depressed and/or continuously held down, the patient monitor 310 enters into the pairing mode of operation.

As reflected at block 506, the mobile device 210 or the bedside patient monitor 310 transmits a pairing signal to pair, or associate, with wireless sensor 102. The mobile device 210 or the bedside patient monitor 310 is configured to emit a pairing signal. The speaker of the mobile device 210 or the bedside patient monitor 310 may be configured to emit an audio signal or a series of audio sounds as the pairing signal. The pairing signal transmission is received by orienting the audio or sound-based detector 147 of the wireless sensor 102 toward the bedside patient monitor 310 or mobile device 210. The limited range of the audio or sound-based pairing signal helps to prevent unintended or incidental association of the wireless sensor 102 with a mobile device or bedside patient monitor 310 that might be nearby but which is not intended to be paired with the wireless sensor 102. Such circumstances can occur in hospitals, healthcare facilities, nursing homes, and the like where wireless sensors 102 and the mobile device 210 or the bedside patient monitor 310 are located in close physical proximity to one another.

At block 508, the wireless sensor 102 detects the pairing signal from the mobile device 210 or the patient monitor 310. Upon detection of the pairing signal, the wireless sensor 102, at block 510, associates with the mobile device 210 or the bedside patient monitor 310 thereby configuring the wireless sensor 102 and patient monitor 310 to communicate with each other. Once the pairing is completed, the wireless sensor 102 transmits a confirmation signal confirming that the patient-worn sensor 102 is associated with the mobile device 210 or the bedside patient monitor 310, thereby indicating that the pairing process has been successfully completed, as reflected in block 512. At block 514, the mobile device 210 or the bedside patient monitor 310 receives the confirmation signal. And at block 516A, the wireless sensor 102 exits the pairing mode of operation and enters into a patient parameter sensing mode of operation. Similarly, at block 516B, the mobile device 210 or the bedside patient monitor 310 enters a patient parameter sensing mode of operation. In the patient parameter sensing mode of operation, the patient-worn sensor 102 transmits a patient parameter sensing signal having a patient parameter sensing signal transmission range. The wireless sensor 102 increases the power of the patient parameter sensing signal transmission range to a standard operating range, such as for example, approximately three meters. The patient parameter sensing signal transmission range may be approximately ten feet. Alternatively, the patient parameter sensing signal transmission range may be approximately thirty feet. The pairing signal transmission range may be between approximately three and twelve inches, while the patient parameter sensing signal transmission range may be approximately ten feet. There may be at least an order of magnitude difference between the pairing signal transmission range and the patient parameter sensing signal transmission range. Thus, the pairing signal transmission range is substantially less than the patient parameter sensing transmission range. Once the wireless sensor 102 enters into the patient parameter sensing mode of operation, the wireless sensor 102 is then in condition to be placed on the patient to perform sensing and monitoring functions.

The patient monitor 310 may access the patient's health records and clinician input via a data network. Illustratively, the patients' positional history data, analyzed in view of the patient's health records, may reveal or suggest a treatment protocol that will likely yield favorable clinical outcomes for the particular patient. Accordingly, the mobile device 210 or the bedside patient monitor 310 analyzes the accessed information in conjunction with the received information from the wireless sensor 102 to determine a recommended treatment protocol for the patient.

In another aspect of the present disclosure, the mobile device 210 or the bedside patient monitor 310 can determine a score that describes the patient's wellness/sickness state, which may also be referred to as a “Halo Index.” Illustratively, the patient monitor 310 accesses and analyzes the patient's health records, clinician input, positional history data provided by the wireless sensor, surface structure pressure data, and other physiological parameter data collected and provided by the wireless sensor (such as, by way of non-limiting example, the patient's temperature, respiration rate, heart rate, ECG signal, and the like) to assess the patient's overall health condition.

An extender/repeater may be used to communicate with the wireless sensor 102 instead of the mobile device 210 or the bedside patient monitor 310. Pairing with the extender/repeater may be performed in the same manner described above with respect to FIG. 4 or FIG. 5.

In another aspect of the present disclosure, the pairing procedures may be applicable to user products including phones, tablets, headphones, watches, speakers, computer mice, computer keyboards, wearable devices, audio headsets, virtual reality headsets, augmented reality headsets, vehicle consoles, infotainment systems, and any other wireless communication devices known to those of skill in the art.

The wireless communication device may be a mobile phone. The mobile phone may allow voice calls to establish a data connection using a cellular network or Wi-Fi network. The mobile phone may also include features in the operating system or mobile applications that offer various functionalities for the user. The wireless communication device may be configured to collect various data such as the GPS location of the mobile phone. The mobile applications may be configured to receive collected data from wireless devices that are paired with the mobile phone.

The wireless communication device may be a wireless headphone that emits audio signals from an audio source. The audio signal may be transmitted through a wireless data connection established using the disclosed pairing procedures. The wireless communication device may be a watch, headset, or other wear device. The device may provide functionality such as detecting the location, movement, physical activity, or physiological condition of the user. The detected data may be transmitted to another wireless device for display, storage, analysis, or other uses, The transmission of the detected data may be facilitated by a wireless data connection established using the disclosed pairing procedures. A wireless data connection may be established to facilitate the use of wireless communication device such as a wireless keyboard or wireless computer mouse. The wireless communication device may be connected to another wireless communication device such as a desktop computer or mobile device such as a laptop or tablet. The transmission of data associated with the functionality of the wireless communication device may be facilitated by a wireless data connection established using the disclosed pairing procedures.

The wireless communication device may be a vehicle console or infotainment system. The vehicle console or infotainment system may include a screen for displaying the operation of the vehicle. The screen may be a touch screen that functions as a control interface for the vehicle. The console or infotainment system may receive data such as an audio signal, video signal, GPS location, driving directions, or fare calculations from a paired wireless communication device, A skilled artisan would recognize that other data may be exchanged between the vehicle console or infotainment system and a paired wireless communication device. The transmission of data associated with the functionality of the wireless communication device and vehicle console or infotainment system may be facilitated by a wireless data connection established using the disclosed pairing procedures.

FIG. 6 illustrates a method of associating a first wireless device with a second wireless device, which may be referred to as “pairing.” The first wireless device may be a wireless sensor 102 or 202 as described above. The second wireless device may be a mobile device 210 or bedside patient monitor 310 as described above. At block 602A, the first wireless device may be placed near the second wireless device in preparation for receiving a pairing signal. A visual, optical, and/or light-based detector 146 of the first wireless communication device may be physically oriented and configured to receive a pairing signal in the form of a visual, optical, and/or light-based pairing signal. The pairing signal may contain a pattern containing a shape, color, or a combination of patterns. The pairing signal may contain a series of visual, optical, and/or light based signals. The series of signals may utilize variations in color, shade, shape, or visual patterns. The pairing signal may contain a series of flashes, wherein the flashes may vary in intensity or duration. The signal may be unique to the first wireless device and/or the second wireless device. By using a pairing signal that uniquely identifies the first wireless device and/or the second wireless device, a secure connection may be established between the two paired devices.

Various types of sensors can be used with the pairing process of the present disclosure. For example, a pulse oximeter sensor can be paired by facing its light detector toward the display or screen of second wireless communication device to receive a visual, optical, and/or light based signal. In another example, an ulcer sensor can be paired by receiving a pairing signal in the form of detected motion. Similarly, other types of wireless sensors can be paired using the already included detectors that are used for physiological detection or other detection of the surrounding environment during normal use. For example, an acoustic sensor can be paired based on audio signals emitted from the second wireless communications device. EEG and ECG wireless sensors can be paired using small electrical impulses from a special conductor included as part of the second wireless communications device. Other sensors can be paired in a similar fashion depending on the specific detectors included on the first wireless communication device.

Returning to block 602A, the first wireless device may be placed in proximity to the second wireless device such that the visual, optical, and/or light-based detector 146 may receive the visual, optical, and/or light-based pairing signal. The visual, optical, and/or light-based pairing signal has a pairing signal transmission range of up to approximately three inches. The visual, optical, and/or light-based pairing signal has a pairing signal transmission range of up to approximately six inches. The visual, optical, and/or light-based pairing signal has a pairing signal transmission range of up to approximately one foot (i.e., twelve inches) or farther. A skilled artisan will recognize that other ranges can be used for the pairing signal transmission range.

At block 604A the first wireless device is set to operate in a pairing mode. A user may begin by initiating the pairing mode of operation for the first wireless device. This may include powering on the First wireless device, switching the first wireless device to a special pairing state, and/or the like. For example, the first wireless device may include a battery isolator 120 which, when removed, activates the first wireless device. Upon activation, the default mode of operation is the pairing mode. The first wireless device may have a button/switch 124 that can be used to activate the first wireless device and place it in the pairing mode of operation. For example, a depressible button/switch 124 can be located on the top portion of the housing 150. When the button/switch 124 is depressed and continuously held down, the first wireless device enters into the pairing mode of operation and remains in the pairing mode of operation for as long as the button/switch 124 is depressed. The first wireless device may enter into the pairing mode by activating the sound or audio-based sensor 147. Once activated, the sound or audio-based sensor 147 may be configured to receive the audio or sound-based pairing signal.

At block 604B, the second wireless device is set to operate in pairing mode. A user may begin by initiating the pairing mode of operation for the second wireless device. This may include powering on the device, switching the device to a special pairing state, and/or the like. The second wireless device may have a button or switch that can be used to activate the second wireless device and place it in the pairing mode of operation, When the button or switch is depressed or continuously held down, the second wireless device enters into the pairing mode of operation.

As reflected at block 606, the second wireless device transmits a pairing signal to pair, or associate, with first wireless device. The second wireless communications device may be configured to emit a pairing signal. The display or screen of the second wireless communication device may be configured to emit a visual, optical, and/or light-based pairing signal. The pairing signal transmission is received by orienting the visual, optical, and/or light-based detector 146 of the first wireless communication device toward the display or screen. The limited range of the visual, optical, and/or light-based pairing signal helps to prevent unintended or incidental association of the first wireless communication device with a second wireless communication device that might be nearby but which is not intended to be paired with the first wireless communication device. Such circumstances can occur in residential buildings, office buildings, commercial facilities, airports, public transportation facilities, hospitals, healthcare facilities, nursing homes, and the like where the first wireless communications device and second communications device are located in close physical proximity to one another.

At block 608, the first wireless device detects the pairing signal from second wireless device. Upon detection of the pairing signal, the first wireless device, at block 610, associates with the second wireless device thereby configuring the first wireless device and second wireless device to communicate with each other. Once the pairing is completed, the first wireless device transmits a confirmation signal confirming that the first wireless communication device is associated with the second wireless device, thereby indicating that the pairing process has been successfully completed, as reflected in block 612. At block 614, the second wireless device receives the confirmation signal. And at block 616A, the first wireless device exits the pairing mode of operation and enters into a patient parameter sensing mode of operation. Similarly, at block 616B, the second wireless device enters a patient parameter sensing mode of operation.

FIG. 7 illustrates another method of associating a first wireless device with a second wireless device, which may be referred to as “pairing.” The first wireless device may be a wireless sensor 102 or 202 as described above. The second wireless device may be a mobile device 210 or a beside patient monitor 310 as described above.

At block 702A, the first wireless device may be placed near the second wireless device in preparation for receiving a pairing signal. For sensors that utilize an audio sensor, such as respirator sensor, the pairing signal may be an audio sound or a series of audio sounds. A sound or audio-based detector 147 of the first wireless device may be configured to receive a pairing signal in the form of a sound or audio-based pairing signal. The sounds may be tuned to a frequency within or outside of the range of human hearing and may comprise various rings, chimes, or tones. The series of audio sounds may utilize variations in volume or tone to transmit pairing information. The signal may be unique to the first wireless device and/or the second wireless device. By using a pairing signal that uniquely identifies the first wireless device and/or the second wireless device, a secure connection may be established between the two paired devices.

Various types of sensors can be used with the pairing process of the present disclosure. For example, a pulse oximeter sensor can be paired by facing its light detector toward the display or screen of a second wireless communication device to receive a visual, optical, and/or light based signal. In another example, an ulcer sensor can be paired by receiving a pairing signal in the form of detected motion. Similarly, other types of wireless sensors can be paired using the included detectors. For example, an acoustic sensor can be paired based on audio signals emitted from the second wireless communications device. EEG and ECG wireless sensors can be paired using small electrical impulses from a special conductor included as part of the second wireless communications device. Other sensors can be paired in a similar fashion depending on the specific detectors included on the first wireless communication device.

Returning to block 702A, the first wireless device may be placed in proximity to the second wireless communications device such that the sound or audio detector may receive the sound or audio-based pairing signal. The sound or audio-based pairing signal may have a pairing signal transmission range of up to approximately three inches. The sound or audio-based pairing signal has a pairing signal transmission range of up to approximately six inches. The sound or audio-based pairing signal may have a pairing signal transmission range of up to approximately one foot (i.e., twelve inches) or farther. A skilled artisan will recognize that other ranges can be used for the pairing signal transmission range.

At block 704A the first wireless device is set to operate in a pairing mode. A user may begin by initiating the pairing mode of operation for the first wireless device. This may include powering on the first wireless device, switching the first wireless device to a special pairing state, and/or the like. For example, the first wireless device may include a battery isolator 120 which, when removed, activates the first wireless device. Upon activation, the default mode of operation is the pairing mode. The first wireless device may have a button/switch 124 that can be used to activate the first wireless device and place it in the pairing mode of operation. For example, a depressible button/switch 124 can be located on the top portion of the housing 150. When the button/switch 124 is depressed and continuously held down, the first wireless device enters into the pairing mode of operation and remains in the pairing mode of operation for as long as the button or switch 124 is depressed. The wireless sensor can be placed in pairing mode by being shaken, bounced, or by shining a bright light at the detector. The first wireless device enters into the pairing mode by activating the sound or audio-based sensor 147. Once activated, the sound or audio-based sensor 147 may be configured to receive the audio or sound-based pairing signal.

At block 704B, the second wireless device is set to operate in pairing mode. A user may begin by initiating the pairing mode of operation for the second wireless device. This may include powering on the device, switching the device to a special pairing state, and/or the like. The second wireless device may have a button/switch that can be used to activate the second wireless device and place it in the pairing mode of operation. When the button/switch is depressed and/or continuously held down, the second wireless device enters into the pairing mode of operation.

As reflected at block 706, the second wireless device transmits a pairing signal to pair, or associate, with first wireless device. The second wireless communications device may be configured to emit a pairing signal. The speaker of the second wireless communications device may be configured to emit an audio signal or a series of audio sounds as the pairing signal. The pairing signal transmission is received by orienting the audio or sound-based detector 147 of the first wireless device toward the second wireless communications device. The limited range of the audio or sound-based pairing signal helps to prevent unintended or incidental association of the first wireless device with a second wireless device that might be nearby but which is not intended to be paired with the first wireless device. Such circumstances can occur in residential buildings, office buildings, commercial facilities, airports, public transportation facilities, hospitals, healthcare facilities, nursing homes, and the like where the first wireless communications device and second communications device are located in close physical proximity to one another.

At block 708, the first wireless device detects the pairing signal from second wireless device. Upon detection of the pairing signal, the first wireless device, at block 710, associates with the second wireless device thereby configuring the first wireless device and second wireless device to communicate with each other. Once the pairing is completed, the first wireless device transmits a confirmation signal confirming that the first wireless communication device is associated with the second wireless device, thereby indicating that the pairing process has been successfully completed, as reflected in block 712. At block 714, the second wireless device receives the confirmation signal. And at block 716A, the first wireless device exits the pairing mode of operation and enters into a patient parameter sensing mode of operation. Similarly, at block 716B the second wireless device enters a patient parameter sensing mode of operation.

FIG. 8 illustrates a method of associating a wireless sensor 102 with a wireless communication device 810, which may be referred to as “pairing.” A wireless sensor 102 may include a motion sensor. The wireless communication device 810 may include a device screen 820. Here, the pairing signal may involve displaying instructions on device screen 820 for a user to follow. The instructions may indicate steps that a user must follow in order to complete the pairing process. In one example, the instructions may be a sequence of motions that the user must perform on the wireless sensor 802. The instructions may be displayed using objects 830, 831, 832 on device screen 820 representing the silhouette of the wireless sensor 102. The objects 830, 831, 832 are displayed on the device screen 820 in sequence, one at a time, along with an arrow representing the direction the wireless sensor 102 should move. To follow the instructions, the user may hold the wireless sensor 102 and move the position of the wireless sensor 102 according to the instructions. For example, to complete STEP 1 of the pairing instruction, the user will move the wireless sensor 102 in an upward motion relative to the device screen 820. The change in position of first wireless communication device 820 will resemble the relative change in position from object 830 to object 831 on the device screen 820. To complete STEP 2 of the pairing instruction, the user will move the wireless sensor 102 in a leftward motion relative to the device screen 820. The change in position of the wireless communication device 820 will resemble the relative change in position from object 831 to object 832 on the device screen 820. The motion detector of the wireless communication device 810 detects each step of the motion. The detected motion is then used as the pairing signal to associate the wireless sensor 102 with wireless communication device 810. One skilled in the art will appreciate that other types and sequences of motion may be used as the pairing signal.

FIG. 9 illustrates a method of associating a first wireless communication device with a second wireless communication device. The first wireless communication device may be a bluetooth headset 902. The wireless communication device may be a vehicle console or infotainment system 910. The vehicle console or infotainment system 910 may include a screen 912 for displaying information related to the operation of the vehicle and control interface. The console or infotainment system 910 may receive data such as an audio signal, video signal, GPS location, driving directions, or fare calculations from a paired wireless communication device from a first wireless communication device 902. A skilled artisan would recognize that other data may be exchanged between the vehicle console or infotainment system and a paired wireless communication device.

The transmission of data associated with the functionality of the wireless communication device 902 and vehicle console or infotainment system 910 may be facilitated by a wireless data connection established using a pairing procedure. The pairing procedure may include using a pairing signal to associate the first wireless communication device 902 with vehicle console or infotainment system 910. The pairing signal may contain a pattern containing a shape, color, or a combination of patterns. The pairing signal may contain a series of visual, optical, and/or light based signals. The series of signals may utilize variations in color, shade, shape, or visual patterns. The pairing signal may contain a series of flashes, wherein the flashes may vary in intensity or duration. The wireless communication device 902 may have a light 906 that emits various visual or light based signals. Similarly, the wireless communication device 902 may include a speaker 908 that may generate audio-based pairing signals. The sounds may be tuned to a frequency within or outside of the range of human hearing and may comprise various rings or tones. The pairing signal may comprise a combination of visual signals emitted from wireless communication device light 906 and audio signals emitted from wireless communication device speaker 908. The pairing signal may include a sequence of visual signals emitted from console screen 912 that is synchronized with a sequence of audio signals emitted from console speaker. Additionally, the wireless communication device 902 may have a speaker 904 configured to be placed in the user's ear. The speaker 904 or the speaker 908 may transmit a confirmatory signal that the device has been successfully paired.

The pairing process may be similar to the methods described above. The screen 912 of the vehicle console or infotainment system 910. The pairing signal may involve displaying instructions on the screen 912 for a user to follow. The instructions may include placing a wireless communication device 902 of a particular shape and size in a certain position relative to the screen 912. The user may follow the instructions and hold the wireless communication device 902 in a certain position relative to the screen 912 to pair the wireless communication device 902 to the vehicle console or infotainment system 910.

Additionally, the console screen 912 may be configured to display motion instructions for a user to perform in order to generate motion signals representing a pairing signal. Additionally, the console or infotainment system 910 may have a port for connecting peripheral devices that may generate various signals such as current or voltage based signals. The pair signal may take the form of an electrical signal.

The vehicle console or infotainment system 910 can have a switch or button 916 which, when depressed, places the wireless communication device 902 in a pairing mode of operation, causing the wireless communication device 902 to wait for a pairing signal. Similarly, the vehicle console or infotainment system 910 can have a switch or button 918 on the steering wheel which, when depressed, places the wireless communication device 902 in a pairing mode of operation, causing the wireless communication device 902 to wait for a pairing signal.

Many other variations than those described herein will be apparent from this disclosure. For example, certain acts, events, or functions of any of the algorithms described herein can be performed in a different sequence, can be added, merged, or left out altogether (e.g., not all described acts or events are necessary for the practice of the algorithms). Moreover, acts or events can be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially. In addition, different tasks or processes can be performed by different machines and/or computing systems that can function together.

The first wireless communication device and second wireless communication device may be paired without additional components. The first wireless communication may be a wireless sensor. The wireless sensor may be a variety of sensors as described herein, such as a magnetometer which may also be referred to as a compass, a temperature sensor, an acoustic respiration sensor, an electrocardiogram (ECG) sensor, an electroencephalography (EEG) sensor, one or more pulse oximetry sensors, a moisture sensor, a blood pressure sensor, and an impedance sensor. The second wireless communication device may be a mobile device 210 or a bedside patient monitor 310. Similarly, a variety of wireless sensors described herein may be paired to a wireless communication device such as a mobile device or a patient monitoring system. Further, the wireless communication device may also other devices such as phones, tablets, headphones, watches, speakers, computer mice, computer keyboards, wearable devices, audio headsets, virtual reality headsets, augmented reality headsets, vehicle consoles, infotainment systems, and any other wireless communication devices known to those of skill in the art.

The methods and systems described herein can be implemented without any additional hardware components. There is no installation of additional components required. This can provide ease of use and implementation such that users can use devices they are familiar with without additional components. For example, as described above, the shape of the device may be used as a pairing signal. In another example, the vibration of an acoustic sensor may be used as a pairing signal. The properties of the sensors or wireless communication devices can be utilized in the pairing process by the system and methods described herein.

The methods and systems for pairing described herein can also be implemented without the use of wireless communication protocols. For example, the pairing methods and systems can be implemented without the use of protocols such as a Bluetooth protocol, a wifi protocol, or a zigbee protocol.

The various illustrative logical blocks, modules, and algorithm steps described in connection with the disclosure herein can be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. The described functionality can be implemented in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosure.

The various illustrative logical blocks and modules described in connection with the disclosure herein can be implemented or performed by a machine, such as a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor can be a microprocessor, but in the alternative, the processor can be a controller, microcontroller, or state machine, combinations of the same, or the like. A processor can include electrical circuitry configured to process computer-executable instructions. A processor may include an FPGA or other programmable device that performs logic operations without processing computer-executable instructions. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. A computing environment can include any type of computer system, including, but not limited to, a computer system based on a microprocessor, a mainframe computer, a digital signal processor, a portable computing device, a device controller, or a computational engine within an appliance, to name a few.

The steps of a method, process, or algorithm described in connection with the disclosure herein can 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. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, 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 example storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The storage medium can be volatile or nonvolatile. The processor and the storage medium can reside in an ASIC.

Conditional language used herein, such as, among others, “can,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain examples include, while other examples do not include, certain features, elements and/or states. Thus, such conditional language is not generally intended to imply that features, elements and/or states are in any way required for one or more examples or that one or more examples necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and/or states are included or are to be performed in any particular example. The terms “comprising,” “including,” “having,” and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations, and so forth. Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list. Further, the term “each,” as used herein, in addition to having its ordinary meaning, can mean any subset of a set of elements to which the term “each” is applied.

While the above detailed description has shown, described, and pointed out novel features as applied to various examples, it will be understood that various omissions, substitutions, and changes in the form and details of the systems, devices or methods illustrated can be made without departing from the spirit of the disclosure. As will be recognized, certain examples described herein can be embodied within a form that does not provide all of the features and benefits set forth herein, as some features can be used or practiced separately from others.

The term “and/or” herein has its broadest, least limiting meaning which is the disclosure includes A alone, B alone, both A and B together, or A or B alternatively, but does not require both A and B or require one of A or one of B. As used herein, the phrase “at least one of” A, B, “and” C should be construed to mean a logical A or B or C, using a non-exclusive logical or.

The apparatuses 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 that are stored on a non-transitory tangible computer readable medium. The computer programs may also include stored data. Non-limiting examples of the non-transitory tangible computer readable medium are nonvolatile memory, magnetic storage, and optical storage.

Although the foregoing disclosure has been described in terms of certain preferred examples, other examples will be apparent to those of ordinary skill in the art from the disclosure herein. Additionally, other combinations, omissions, substitutions and modifications will be apparent to the skilled artisan in view of the disclosure herein. Accordingly, the present invention is not intended to be limited by the description of the preferred examples, but is to be defined by reference to claims.

Claims

1. A system for electronically pairing a wireless physiological sensor with a patient monitoring device, the system comprising: a patient monitoring device comprising a first display;a wireless physiological sensor, the wireless physiological sensor further comprising a motion detector configured to detect position and orientation of the wireless physiological sensor; andone or more hardware processors configured to: generate a motion instruction on the first display;detect a pairing signal of the physiological sensor based at least in part on a movement of the wireless physiological sensor corresponding to the motion instruction;associate the wireless physiological sensor with the patient monitoring device based on the pairing signal, thereby pairing the wireless physiological sensor with the patient monitoring device;transmit a confirmation signal from the wireless physiological sensor to indicate that association is complete; andconfigure the wireless physiological sensor to enter into a patient parameter sensing mode of operation after the association of the wireless physiological sensor with the patient monitoring device.
2. The system of claim 1, wherein the motion detector comprises an inertial measurement unit.
3. The system of claim 2, wherein the inertial measurement unit comprises an accelerometer, gyroscope, or magnetometer.
4. The system of claim 1, wherein the wireless physiological sensor comprises a button or switch configured to activate the pairing mode.
5. The system of claim 1, wherein the motion instruction comprises an instruction to shake or bounce the wireless physiological sensor.
6. The system of claim 1, wherein the motion instruction comprises an instruction to move the wireless physiological sensor from one location on the first display to a second location on the first display.
7. The system of claim 1, wherein the motion instruction comprises the movement of a pairing object on the display.
8. The system of claim 1, wherein the one or more hardware processors are configured to receive a confirmation signal from the physiological sensor of a successful association.
9. The system of claim 1, wherein the wireless physiological sensor does not require a separate antenna or any additional components for the pairing with the patient monitoring device.
10. The system of claim 1, wherein the wireless physiological sensor uses a wireless communication protocol for the pairing with the patient monitoring device.
11. The system of claim 1, wherein the wireless physiological sensor does not use a wireless communication protocol for the pairing with the patient monitoring device.
12. The system of claim 11, wherein the wireless communication protocol comprises at least one of: a Bluetooth protocol, wifi protocol, or a zigbee protocol.
13. A method for electronically pairing a wireless physiological sensor with a monitoring device, the method comprising: receiving an indication for a wireless physiological sensor to enter a pairing mode;detecting a pairing signal from a physiological monitoring device with a motion detector of a wireless physiological sensor, wherein the motion detector is configured to detect a position or an orientation of a patient;associating the wireless physiological sensor with the patient monitoring device based on the detected pairing signal;configuring the wireless physiological sensor to enter into a patient parameter sensing mode after the wireless physiological sensor is associated with the patient monitoring device.
14. The method of claim 13, wherein the motion detector comprises an inertial measurement unit.
15. The method of claim 14, wherein the inertial measurement unit comprises an accelerometer, a gyroscope, or a magnetometer.
16. The method of claim 13, wherein the pairing signal comprises a sequence of motion data corresponding to a motion instruction on a display of the patient monitoring device.
17. The method of claim 13, wherein the indication comprises a user interaction with a button or switch on the wireless physiological sensor configured to activate the pairing mode.
18. The method of claim 13, wherein the indication comprises a motion of the sensor.
19. The method of claim 13, comprising generating the pairing signal at least in part based on a movement of the wireless physiological sensor.
20. The method of claim 19, wherein the movement of the wireless sensor is a bounce or a shake.
21. The method of claim 19, the movement of the wireless physiological sensor comprises moving from one location on a display of the physiological monitoring device to another location on the display of the physiological monitoring device.
22. The method of claim 13, wherein the wireless physiological sensor does not require a separate antenna or any additional components for the pairing with the patient monitoring device.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 16/899,386, titled “PATIENT-WORN WIRELESS PHYSIOLOGICAL SENSOR WITH PAIRING FUNCTIONALITY”, which is itself a continuation of U.S. patent application Ser. No. 15/874,652, filed Jan. 18, 2018, titled “PATIENT-WORN WIRELESS PHYSIOLOGICAL SENSOR WITH PAIRING FUNCTIONALITY”, which claims priority benefit under 35 U.S.C. § 119(e) from U.S. Provisional Patent Application Ser. No. 62/505,762, filed May 12, 2017, titled “PATIENT-WORN WIRELESS PHYSIOLOGICAL SENSOR WITH PAIRING FUNCTIONALITY”, and also claims priority benefit under 35 U.S.C. § 119(e) from U.S. Provisional Patent Application Ser. No. 62/447,836, filed Jan. 18, 2017, titled “PATIENT-WORN WIRELESS PHYSIOLOGICAL SENSOR WITH PAIRING FUNCTIONALITY”, the disclosure of which is hereby incorporated by reference in its entirety.

US Referenced Citations (1193)

Number	Name	Date	Kind
4960128	Gordon et al.	Oct 1990	A
4964408	Hink et al.	Oct 1990	A
5041187	Hink et al.	Aug 1991	A
5069213	Hink et al.	Dec 1991	A
5163438	Gordon et al.	Nov 1992	A
5319355	Russek	Jun 1994	A
5337744	Branigan	Aug 1994	A
5341805	Stavridi et al.	Aug 1994	A
D353195	Savage et al.	Dec 1994	S
D353196	Savage et al.	Dec 1994	S
5377676	Vari et al.	Jan 1995	A
D359546	Savage et al.	Jun 1995	S
5431170	Mathews	Jul 1995	A
5436499	Namavar et al.	Jul 1995	A
D361840	Savage et al.	Aug 1995	S
D362063	Savage et al.	Sep 1995	S
5452717	Branigan et al.	Sep 1995	A
D363120	Savage et al.	Oct 1995	S
5456252	Vari et al.	Oct 1995	A
5479934	Imran	Jan 1996	A
5482036	Diab et al.	Jan 1996	A
5490505	Diab et al.	Feb 1996	A
5494043	O'Sullivan et al.	Feb 1996	A
5533511	Kaspari et al.	Jul 1996	A
5534851	Russek	Jul 1996	A
5561275	Savage et al.	Oct 1996	A
5562002	Lalin	Oct 1996	A
5590649	Caro et al.	Jan 1997	A
5602924	Durand et al.	Feb 1997	A
5632272	Diab et al.	May 1997	A
5638816	Kiani-Azarbayjany et al.	Jun 1997	A
5638818	Diab et al.	Jun 1997	A
5645440	Tobler et al.	Jul 1997	A
5671914	Kalkhoran et al.	Sep 1997	A
5685299	Diab et al.	Nov 1997	A
5726440	Kalkhoran et al.	Mar 1998	A
D393830	Tobler et al.	Apr 1998	S
5743262	Lepper, Jr. et al.	Apr 1998	A
5747806	Khalil et al.	May 1998	A
5750994	Schlager	May 1998	A
5758644	Diab et al.	Jun 1998	A
5760910	Lepper, Jr. et al.	Jun 1998	A
5769785	Diab et al.	Jun 1998	A
5782757	Diab et al.	Jul 1998	A
5785659	Caro et al.	Jul 1998	A
5791347	Flaherty et al.	Aug 1998	A
5810734	Caro et al.	Sep 1998	A
5823950	Diab et al.	Oct 1998	A
5830131	Caro et al.	Nov 1998	A
5833618	Caro et al.	Nov 1998	A
5860919	Kiani-Azarbayjany et al.	Jan 1999	A
5890929	Mills et al.	Apr 1999	A
5904654	Wohltmann et al.	May 1999	A
5919134	Diab	Jul 1999	A
5934925	Tobler et al.	Aug 1999	A
5940182	Lepper, Jr. et al.	Aug 1999	A
5987343	Kinast	Nov 1999	A
5995855	Kiani et al.	Nov 1999	A
5997343	Mills et al.	Dec 1999	A
6002952	Diab et al.	Dec 1999	A
6010937	Karam et al.	Jan 2000	A
6011986	Diab et al.	Jan 2000	A
6027452	Flaherty et al.	Feb 2000	A
6036642	Diab et al.	Mar 2000	A
6040578	Malin et al.	Mar 2000	A
6045509	Caro et al.	Apr 2000	A
6066204	Haven	May 2000	A
6067462	Diab et al.	May 2000	A
6081735	Diab et al.	Jun 2000	A
6088607	Diab et al.	Jul 2000	A
6110522	Lepper, Jr. et al.	Aug 2000	A
6115673	Malin et al.	Sep 2000	A
6124597	Shehada et al.	Sep 2000	A
6128521	Marro et al.	Oct 2000	A
6129675	Jay	Oct 2000	A
6144868	Parker	Nov 2000	A
6151516	Kiani-Azarbayjany et al.	Nov 2000	A
6152754	Gerhardt et al.	Nov 2000	A
6157850	Diab et al.	Dec 2000	A
6165005	Mills et al.	Dec 2000	A
6184521	Coffin, IV et al.	Feb 2001	B1
6206830	Diab et al.	Mar 2001	B1
6229856	Diab et al.	May 2001	B1
6232609	Snyder et al.	May 2001	B1
6236872	Diab et al.	May 2001	B1
6241683	Macklem et al.	Jun 2001	B1
6253097	Aronow et al.	Jun 2001	B1
6255708	Sudharsanan et al.	Jul 2001	B1
6256523	Diab et al.	Jul 2001	B1
6263222	Diab et al.	Jul 2001	B1
6278522	Lepper, Jr. et al.	Aug 2001	B1
6280213	Tobler et al.	Aug 2001	B1
6280381	Malin et al.	Aug 2001	B1
6285896	Tobler et al.	Sep 2001	B1
6301493	Marro et al.	Oct 2001	B1
6308089	von der Ruhr et al.	Oct 2001	B1
6317627	Ennen et al.	Nov 2001	B1
6321100	Parker	Nov 2001	B1
6325761	Jay	Dec 2001	B1
6334065	Al-Ali et al.	Dec 2001	B1
6343224	Parker	Jan 2002	B1
6349228	Kiani et al.	Feb 2002	B1
6360114	Diab et al.	Mar 2002	B1
6368283	Xu et al.	Apr 2002	B1
6371921	Caro et al.	Apr 2002	B1
6377829	Al-Ali	Apr 2002	B1
6388240	Schulz et al.	May 2002	B2
6397091	Diab et al.	May 2002	B2
6411373	Garside et al.	Jun 2002	B1
6415167	Blank et al.	Jul 2002	B1
6430437	Marro	Aug 2002	B1
6430525	Weber et al.	Aug 2002	B1
6463311	Diab	Oct 2002	B1
6470199	Kopotic et al.	Oct 2002	B1
6487429	Hockersmith et al.	Nov 2002	B2
6501975	Diab et al.	Dec 2002	B2
6505059	Kollias et al.	Jan 2003	B1
6515273	Al-Ali	Feb 2003	B2
6519487	Parker	Feb 2003	B1
6525386	Mills et al.	Feb 2003	B1
6526300	Kiani et al.	Feb 2003	B1
6534012	Hazen et al.	Mar 2003	B1
6541756	Schulz et al.	Apr 2003	B2
6542764	Al-Ali et al.	Apr 2003	B1
6580086	Schulz et al.	Jun 2003	B1
6584336	Ali et al.	Jun 2003	B1
6587196	Stippick et al.	Jul 2003	B1
6587199	Luu	Jul 2003	B1
6595316	Cybulski et al.	Jul 2003	B2
6597932	Tian et al.	Jul 2003	B2
6597933	Kiani et al.	Jul 2003	B2
6606511	Ali et al.	Aug 2003	B1
6632181	Flaherty et al.	Oct 2003	B2
6635559	Greenwald et al.	Oct 2003	B2
6639668	Trepagnier	Oct 2003	B1
6640116	Diab	Oct 2003	B2
6640117	Makarewicz et al.	Oct 2003	B2
6643530	Diab et al.	Nov 2003	B2
6650917	Diab et al.	Nov 2003	B2
6654624	Diab et al.	Nov 2003	B2
6658276	Kiani et al.	Dec 2003	B2
6661161	Lanzo et al.	Dec 2003	B1
6671531	Al-Ali	Dec 2003	B2
6678543	Diab et al.	Jan 2004	B2
6684090	Ali et al.	Jan 2004	B2
6684091	Parker	Jan 2004	B2
6697656	Al-Ali	Feb 2004	B1
6697657	Shehada et al.	Feb 2004	B1
6697658	Al-Ali	Feb 2004	B2
RE38476	Diab et al.	Mar 2004	E
6699194	Diab et al.	Mar 2004	B1
6714804	Al-Ali et al.	Mar 2004	B2
RE38492	Diab et al.	Apr 2004	E
6721582	Trepagnier et al.	Apr 2004	B2
6721585	Parker	Apr 2004	B1
6725075	Al-Ali	Apr 2004	B2
6728560	Kollias et al.	Apr 2004	B2
6735459	Parker	May 2004	B2
6738652	Mattu et al.	May 2004	B2
6745060	Diab et al.	Jun 2004	B2
6760607	Al-Ali	Jul 2004	B2
6770028	Ali et al.	Aug 2004	B1
6771994	Kiani et al.	Aug 2004	B2
6788965	Ruchti et al.	Sep 2004	B2
6792300	Diab et al.	Sep 2004	B1
6813511	Diab et al.	Nov 2004	B2
6816241	Grubisic	Nov 2004	B2
6816741	Diab	Nov 2004	B2
6822564	Al-Ali	Nov 2004	B2
6826419	Diab et al.	Nov 2004	B2
6830711	Mills et al.	Dec 2004	B2
6850787	Weber et al.	Feb 2005	B2
6850788	Al-Ali	Feb 2005	B2
6852083	Caro et al.	Feb 2005	B2
6861639	Al-Ali	Mar 2005	B2
6876931	Lorenz et al.	Apr 2005	B2
6898452	Al-Ali et al.	May 2005	B2
6920345	Al-Ali et al.	Jul 2005	B2
6931268	Kiani-Azarbayjany et al.	Aug 2005	B1
6934570	Kiani et al.	Aug 2005	B2
6939305	Flaherty et al.	Sep 2005	B2
6943348	Coffin, IV	Sep 2005	B1
6950687	Al-Ali	Sep 2005	B2
6956649	Acosta et al.	Oct 2005	B2
6961598	Diab	Nov 2005	B2
6970792	Diab	Nov 2005	B1
6979812	Al-Ali	Dec 2005	B2
6985764	Mason et al.	Jan 2006	B2
6990364	Ruchti et al.	Jan 2006	B2
6993371	Kiani et al.	Jan 2006	B2
6996427	Ali et al.	Feb 2006	B2
6998247	Monfre et al.	Feb 2006	B2
6999904	Weber et al.	Feb 2006	B2
7003338	Weber et al.	Feb 2006	B2
7003339	Diab et al.	Feb 2006	B2
7015451	Dalke et al.	Mar 2006	B2
7024233	Ali et al.	Apr 2006	B2
7027849	Al-Ali	Apr 2006	B2
7030749	Al-Ali	Apr 2006	B2
7039449	Al-Ali	May 2006	B2
7041060	Flaherty et al.	May 2006	B2
7044918	Diab	May 2006	B2
7048687	Reuss et al.	May 2006	B1
7067893	Mills et al.	Jun 2006	B2
D526719	Richie, Jr. et al.	Aug 2006	S
7096052	Mason et al.	Aug 2006	B2
7096054	Abdul-Hafiz et al.	Aug 2006	B2
D529616	Deros et al.	Oct 2006	S
7132641	Schulz et al.	Nov 2006	B2
7133710	Acosta et al.	Nov 2006	B2
7142901	Kiani et al.	Nov 2006	B2
7149561	Diab	Dec 2006	B2
7186966	Al-Ali	Mar 2007	B2
7190261	Al-Ali	Mar 2007	B2
7215984	Diab et al.	May 2007	B2
7215986	Diab et al.	May 2007	B2
7221971	Diab et al.	May 2007	B2
7225006	Al-Ali et al.	May 2007	B2
7225007	Al-Ali et al.	May 2007	B2
RE39672	Shehada et al.	Jun 2007	E
7239905	Kiani-Azarbayjany et al.	Jul 2007	B2
7245953	Parker	Jul 2007	B1
7254429	Schurman et al.	Aug 2007	B2
7254431	Al-Ali et al.	Aug 2007	B2
7254433	Diab et al.	Aug 2007	B2
7254434	Schulz et al.	Aug 2007	B2
7272425	Al-Ali	Sep 2007	B2
7274955	Kiani et al.	Sep 2007	B2
D554263	Al-Ali et al.	Oct 2007	S
7280858	Al-Ali et al.	Oct 2007	B2
7289835	Mansfield et al.	Oct 2007	B2
7292883	De Felice et al.	Nov 2007	B2
7295866	Al-Ali	Nov 2007	B2
7328053	Diab et al.	Feb 2008	B1
7332784	Mills et al.	Feb 2008	B2
7340287	Mason et al.	Mar 2008	B2
7341559	Schulz et al.	Mar 2008	B2
7343186	Lamego et al.	Mar 2008	B2
D566282	Al-Ali et al.	Apr 2008	S
7355512	Al-Ali	Apr 2008	B1
7356365	Schurman	Apr 2008	B2
7371981	Abdul-Hafiz	May 2008	B2
7373193	Al-Ali et al.	May 2008	B2
7373194	Weber et al.	May 2008	B2
7376453	Diab et al.	May 2008	B1
7377794	Al-Ali et al.	May 2008	B2
7377899	Weber et al.	May 2008	B2
7383070	Diab et al.	Jun 2008	B2
7395158	Monfre et al.	Jul 2008	B2
7415297	Al-Ali et al.	Aug 2008	B2
7428432	Ali et al.	Sep 2008	B2
7438683	Al-Ali et al.	Oct 2008	B2
7440787	Diab	Oct 2008	B2
7454240	Diab et al.	Nov 2008	B2
7467002	Weber et al.	Dec 2008	B2
7469157	Diab et al.	Dec 2008	B2
7471969	Diab et al.	Dec 2008	B2
7471971	Diab et al.	Dec 2008	B2
7483729	Al-Ali et al.	Jan 2009	B2
7483730	Diab et al.	Jan 2009	B2
7489958	Diab et al.	Feb 2009	B2
7496391	Diab et al.	Feb 2009	B2
7496393	Diab et al.	Feb 2009	B2
D587657	Al-Ali et al.	Mar 2009	S
7499741	Diab et al.	Mar 2009	B2
7499835	Weber et al.	Mar 2009	B2
7500950	Al-Ali et al.	Mar 2009	B2
7509154	Diab et al.	Mar 2009	B2
7509494	Al-Ali	Mar 2009	B2
7510849	Schurman et al.	Mar 2009	B2
7514725	Wojtczuk et al.	Apr 2009	B2
7519406	Blank et al.	Apr 2009	B2
7526328	Diab et al.	Apr 2009	B2
D592507	Wachman et al.	May 2009	S
7530942	Diab	May 2009	B1
7530949	Al Ali et al.	May 2009	B2
7530955	Diab et al.	May 2009	B2
7563110	Al-Ali et al.	Jul 2009	B2
7593230	Abul-Haj et al.	Sep 2009	B2
7596398	Al-Ali et al.	Sep 2009	B2
7606608	Blank et al.	Oct 2009	B2
7618375	Flaherty et al.	Nov 2009	B2
7620674	Ruchti et al.	Nov 2009	B2
D606659	Kiani et al.	Dec 2009	S
7629039	Eckerbom et al.	Dec 2009	B2
7640140	Ruchti et al.	Dec 2009	B2
7647083	Al-Ali et al.	Jan 2010	B2
D609193	Al-Ali et al.	Feb 2010	S
D614305	Al-Ali et al.	Apr 2010	S
7697966	Monfre et al.	Apr 2010	B2
7698105	Ruchti et al.	Apr 2010	B2
RE41317	Parker	May 2010	E
RE41333	Blank et al.	May 2010	E
7729733	Al-Ali et al.	Jun 2010	B2
7734320	Al-Ali	Jun 2010	B2
7761127	Al-Ali et al.	Jul 2010	B2
7761128	Al-Ali et al.	Jul 2010	B2
7764982	Dalke et al.	Jul 2010	B2
D621516	Kiani et al.	Aug 2010	S
7791155	Diab	Sep 2010	B2
7801581	Diab	Sep 2010	B2
7822452	Schurman et al.	Oct 2010	B2
RE41912	Parker	Nov 2010	E
7844313	Kiani et al.	Nov 2010	B2
7844314	Al-Ali	Nov 2010	B2
7844315	Al-Ali	Nov 2010	B2
7865222	Weber et al.	Jan 2011	B2
7873497	Weber et al.	Jan 2011	B2
7880606	Al-Ali	Feb 2011	B2
7880626	Al-Ali et al.	Feb 2011	B2
7891355	Al-Ali et al.	Feb 2011	B2
7894868	Al-Ali et al.	Feb 2011	B2
7899507	Al-Ali et al.	Mar 2011	B2
7899518	Trepagnier et al.	Mar 2011	B2
7904132	Weber et al.	Mar 2011	B2
7909772	Popov et al.	Mar 2011	B2
7910875	Al-Ali	Mar 2011	B2
7919713	Al-Ali et al.	Apr 2011	B2
7937128	Al-Ali	May 2011	B2
7937129	Mason et al.	May 2011	B2
7937130	Diab et al.	May 2011	B2
7941199	Kiani	May 2011	B2
7951086	Flaherty et al.	May 2011	B2
7957780	Lamego et al.	Jun 2011	B2
7962188	Kiani et al.	Jun 2011	B2
7962190	Diab et al.	Jun 2011	B1
7976472	Kiani	Jul 2011	B2
7988637	Diab	Aug 2011	B2
7990382	Kiani	Aug 2011	B2
7991446	Ali et al.	Aug 2011	B2
8000761	Al-Ali	Aug 2011	B2
8008088	Bellott et al.	Aug 2011	B2
RE42753	Kiani-Azarbayjany et al.	Sep 2011	E
8019400	Diab et al.	Sep 2011	B2
8028701	Al-Ali et al.	Oct 2011	B2
8029765	Bellott et al.	Oct 2011	B2
8036727	Schurman et al.	Oct 2011	B2
8036728	Diab et al.	Oct 2011	B2
8046040	Ali et al.	Oct 2011	B2
8046041	Diab et al.	Oct 2011	B2
8046042	Diab et al.	Oct 2011	B2
8048040	Kiani	Nov 2011	B2
8050728	Al-Ali et al.	Nov 2011	B2
RE43169	Parker	Feb 2012	E
8118620	Al-Ali et al.	Feb 2012	B2
8126528	Diab et al.	Feb 2012	B2
8128572	Diab et al.	Mar 2012	B2
8130105	Al-Ali et al.	Mar 2012	B2
8145287	Diab et al.	Mar 2012	B2
8150487	Diab et al.	Apr 2012	B2
8175672	Parker	May 2012	B2
8180420	Diab et al.	May 2012	B2
8182443	Kiani	May 2012	B1
8185180	Diab et al.	May 2012	B2
8190223	Al-Ali et al.	May 2012	B2
8190227	Diab et al.	May 2012	B2
8203438	Kiani et al.	Jun 2012	B2
8203704	Merritt et al.	Jun 2012	B2
8204566	Schurman et al.	Jun 2012	B2
8219172	Schurman et al.	Jul 2012	B2
8224411	Al-Ali et al.	Jul 2012	B2
8228181	Al-Ali	Jul 2012	B2
8229532	Davis	Jul 2012	B2
8229533	Diab et al.	Jul 2012	B2
8233955	Al-Ali et al.	Jul 2012	B2
8244325	Al-Ali et al.	Aug 2012	B2
8255026	Al-Ali	Aug 2012	B1
8255027	Al-Ali et al.	Aug 2012	B2
8255028	Al-Ali et al.	Aug 2012	B2
8260577	Weber et al.	Sep 2012	B2
8265723	McHale et al.	Sep 2012	B1
8274360	Sampath et al.	Sep 2012	B2
8280473	Al-Ali	Oct 2012	B2
8301217	Al-Ali et al.	Oct 2012	B2
8306596	Schurman et al.	Nov 2012	B2
8310336	Muhsin et al.	Nov 2012	B2
8315683	Al-Ali et al.	Nov 2012	B2
RE43860	Parker	Dec 2012	E
8337403	Al-Ali et al.	Dec 2012	B2
8346330	Lamego	Jan 2013	B2
8353842	Al-Ali et al.	Jan 2013	B2
8355766	MacNeish, III et al.	Jan 2013	B2
8359080	Diab et al.	Jan 2013	B2
8364223	Al-Ali et al.	Jan 2013	B2
8364226	Diab et al.	Jan 2013	B2
8374665	Lamego	Feb 2013	B2
8385995	Al-Ali et al.	Feb 2013	B2
8385996	Smith et al.	Feb 2013	B2
8388353	Kiani et al.	Mar 2013	B2
8399822	Al-Ali	Mar 2013	B2
8401602	Kiani	Mar 2013	B2
8405608	Al-Ali et al.	Mar 2013	B2
8414499	Al-Ali et al.	Apr 2013	B2
8418524	Al-Ali	Apr 2013	B2
8423106	Lamego et al.	Apr 2013	B2
8428967	Olsen et al.	Apr 2013	B2
8430817	Al-Ali et al.	Apr 2013	B1
8437825	Dalvi et al.	May 2013	B2
8455290	Siskavich	Jun 2013	B2
8457703	Al-Ali	Jun 2013	B2
8457707	Kiani	Jun 2013	B2
8463349	Diab et al.	Jun 2013	B2
8466286	Bellott et al.	Jun 2013	B2
8471713	Poeze et al.	Jun 2013	B2
8473020	Kiani et al.	Jun 2013	B2
8483787	Al-Ali et al.	Jul 2013	B2
8489364	Weber et al.	Jul 2013	B2
8498684	Weber et al.	Jul 2013	B2
8504128	Blank et al.	Aug 2013	B2
8509867	Workman et al.	Aug 2013	B2
8515509	Bruinsma et al.	Aug 2013	B2
8523781	Al-Ali	Sep 2013	B2
8529301	Al-Ali et al.	Sep 2013	B2
8532727	Ali et al.	Sep 2013	B2
8532728	Diab et al.	Sep 2013	B2
D692145	Al-Ali et al.	Oct 2013	S
8547209	Kiani et al.	Oct 2013	B2
8548548	Al-Ali	Oct 2013	B2
8548549	Schurman et al.	Oct 2013	B2
8548550	Al-Ali et al.	Oct 2013	B2
8560032	Al-Ali et al.	Oct 2013	B2
8560034	Diab et al.	Oct 2013	B1
8570167	Al-Ali	Oct 2013	B2
8570503	Vo et al.	Oct 2013	B2
8571617	Reichgott et al.	Oct 2013	B2
8571618	Lamego et al.	Oct 2013	B1
8571619	Al-Ali et al.	Oct 2013	B2
8577431	Lamego et al.	Nov 2013	B2
8581732	Al-Ali et al.	Nov 2013	B2
8584345	Al-Ali et al.	Nov 2013	B2
8588880	Abdul-Hafiz et al.	Nov 2013	B2
8600467	Al-Ali et al.	Dec 2013	B2
8606342	Diab	Dec 2013	B2
8626255	Al-Ali et al.	Jan 2014	B2
8630691	Lamego et al.	Jan 2014	B2
8634889	Al-Ali et al.	Jan 2014	B2
8641631	Sierra et al.	Feb 2014	B2
8652060	Al-Ali	Feb 2014	B2
8663107	Kiani	Mar 2014	B2
8666468	Al-Ali	Mar 2014	B1
8667967	Al-Ali et al.	Mar 2014	B2
8670811	O'Reilly	Mar 2014	B2
8670814	Diab et al.	Mar 2014	B2
8676286	Weber et al.	Mar 2014	B2
8682407	Al-Ali	Mar 2014	B2
RE44823	Parker	Apr 2014	E
RE44875	Kiani et al.	Apr 2014	E
8688183	Bruinsma et al.	Apr 2014	B2
8690799	Telfort et al.	Apr 2014	B2
8700112	Kiani	Apr 2014	B2
8702627	Telfort et al.	Apr 2014	B2
8706179	Parker	Apr 2014	B2
8712494	MacNeish, III et al.	Apr 2014	B1
8715206	Telfort et al.	May 2014	B2
8718735	Lamego et al.	May 2014	B2
8718737	Diab et al.	May 2014	B2
8718738	Blank et al.	May 2014	B2
8720249	Al-Ali	May 2014	B2
8721541	Al-Ali et al.	May 2014	B2
8721542	Al-Ali et al.	May 2014	B2
8723677	Kiani	May 2014	B1
8740792	Kiani et al.	Jun 2014	B1
8754776	Poeze et al.	Jun 2014	B2
8755535	Telfort et al.	Jun 2014	B2
8755856	Diab et al.	Jun 2014	B2
8755872	Marinow	Jun 2014	B1
8761850	Lamego	Jun 2014	B2
8764671	Kiani	Jul 2014	B2
8768423	Shakespeare et al.	Jul 2014	B2
8771204	Telfort et al.	Jul 2014	B2
8777634	Kiani et al.	Jul 2014	B2
8781543	Diab et al.	Jul 2014	B2
8781544	Al-Ali et al.	Jul 2014	B2
8781549	Al-Ali et al.	Jul 2014	B2
8788003	Schurman et al.	Jul 2014	B2
8790268	Al-Ali	Jul 2014	B2
8801613	Al-Ali et al.	Aug 2014	B2
8821397	Al-Ali et al.	Sep 2014	B2
8821415	Al-Ali et al.	Sep 2014	B2
8830449	Lamego et al.	Sep 2014	B1
8831700	Schurman et al.	Sep 2014	B2
8840549	Al-Ali et al.	Sep 2014	B2
8847740	Kiani et al.	Sep 2014	B2
8849365	Smith et al.	Sep 2014	B2
8852094	Al-Ali et al.	Oct 2014	B2
8852994	Wojtczuk et al.	Oct 2014	B2
8868147	Stippick et al.	Oct 2014	B2
8868150	Al-Ali et al.	Oct 2014	B2
8870792	Al-Ali et al.	Oct 2014	B2
8886271	Kiani et al.	Nov 2014	B2
8888539	Al-Ali et al.	Nov 2014	B2
8888708	Diab et al.	Nov 2014	B2
8892180	Weber et al.	Nov 2014	B2
8897847	Al-Ali	Nov 2014	B2
8909310	Lamego et al.	Dec 2014	B2
8911377	Al-Ali	Dec 2014	B2
8912909	Al-Ali et al.	Dec 2014	B2
8920317	Al-Ali et al.	Dec 2014	B2
8921699	Al-Ali et al.	Dec 2014	B2
8922382	Al-Ali et al.	Dec 2014	B2
8929964	Al-Ali et al.	Jan 2015	B2
8942777	Diab et al.	Jan 2015	B2
8948834	Diab et al.	Feb 2015	B2
8948835	Diab	Feb 2015	B2
8965471	Lamego	Feb 2015	B2
8983564	Al-Ali	Mar 2015	B2
8989831	Al-Ali et al.	Mar 2015	B2
8996085	Kiani et al.	Mar 2015	B2
8998809	Kiani	Apr 2015	B2
9026053	Molettiere et al.	May 2015	B2
9028429	Telfort et al.	May 2015	B2
9037207	Al-Ali et al.	May 2015	B2
9060721	Reichgott et al.	Jun 2015	B2
9066666	Kiani	Jun 2015	B2
9066680	Al-Ali et al.	Jun 2015	B1
9072474	Al-Ali et al.	Jul 2015	B2
9078560	Schurman et al.	Jul 2015	B2
9084569	Weber et al.	Jul 2015	B2
9095316	Welch et al.	Aug 2015	B2
9106038	Telfort et al.	Aug 2015	B2
9106307	Molettiere et al.	Aug 2015	B2
9107625	Telfort et al.	Aug 2015	B2
9107626	Al-Ali et al.	Aug 2015	B2
9113831	Al-Ali	Aug 2015	B2
9113832	Al-Ali	Aug 2015	B2
9119595	Lamego	Sep 2015	B2
9131881	Diab et al.	Sep 2015	B2
9131882	Al-Ali et al.	Sep 2015	B2
9131883	Al-Ali	Sep 2015	B2
9131917	Telfort et al.	Sep 2015	B2
9138180	Coverston et al.	Sep 2015	B1
9138182	Al-Ali et al.	Sep 2015	B2
9138192	Weber et al.	Sep 2015	B2
9142117	Muhsin et al.	Sep 2015	B2
9153112	Kiani et al.	Oct 2015	B1
9153121	Kiani et al.	Oct 2015	B2
9161696	Al-Ali et al.	Oct 2015	B2
9161713	Al-Ali et al.	Oct 2015	B2
9167995	Lamego et al.	Oct 2015	B2
9176141	Al-Ali et al.	Nov 2015	B2
9186102	Bruinsma et al.	Nov 2015	B2
9192312	Al-Ali	Nov 2015	B2
9192329	Al-Ali	Nov 2015	B2
9192351	Telfort et al.	Nov 2015	B1
9195385	Al-Ali et al.	Nov 2015	B2
9211072	Kiani	Dec 2015	B2
9211095	Al-Ali	Dec 2015	B1
9218454	Kiani et al.	Dec 2015	B2
9226696	Kiani	Jan 2016	B2
9241662	Al-Ali et al.	Jan 2016	B2
9245668	Vo et al.	Jan 2016	B1
9259185	Abdul-Hafiz et al.	Feb 2016	B2
9267572	Barker et al.	Feb 2016	B2
9277880	Poeze et al.	Mar 2016	B2
9289167	Diab et al.	Mar 2016	B2
9295421	Kiani et al.	Mar 2016	B2
9307928	Al-Ali et al.	Apr 2016	B1
9323894	Kiani	Apr 2016	B2
D755392	Hwang et al.	May 2016	S
9326712	Kiani	May 2016	B1
9333316	Kiani	May 2016	B2
9339220	Lamego et al.	May 2016	B2
9341565	Lamego et al.	May 2016	B2
9351673	Diab et al.	May 2016	B2
9351675	Al-Ali et al.	May 2016	B2
9364181	Kiani et al.	Jun 2016	B2
9368671	Wojtczuk et al.	Jun 2016	B2
9370325	Al-Ali et al.	Jun 2016	B2
9370326	McHale et al.	Jun 2016	B2
9370335	Al-Ali et al.	Jun 2016	B2
9375185	Ali et al.	Jun 2016	B2
9386953	Al-Ali	Jul 2016	B2
9386961	Al-Ali et al.	Jul 2016	B2
9392945	Al-Ali et al.	Jul 2016	B2
9397448	Al-Ali et al.	Jul 2016	B2
9408542	Kinast et al.	Aug 2016	B1
9436645	Al-Ali et al.	Sep 2016	B2
9445759	Lamego et al.	Sep 2016	B1
9466919	Kiani et al.	Oct 2016	B2
9474474	Lamego et al.	Oct 2016	B2
9480422	Al-Ali	Nov 2016	B2
9480435	Olsen	Nov 2016	B2
9492110	Al-Ali et al.	Nov 2016	B2
9510779	Poeze et al.	Dec 2016	B2
9517024	Kiani et al.	Dec 2016	B2
9532722	Lamego et al.	Jan 2017	B2
9538949	Al-Ali et al.	Jan 2017	B2
9538980	Telfort et al.	Jan 2017	B2
9549696	Lamego et al.	Jan 2017	B2
9554737	Schurman et al.	Jan 2017	B2
9560996	Kiani	Feb 2017	B2
9560998	Al-Ali et al.	Feb 2017	B2
9566019	Al-Ali et al.	Feb 2017	B2
9579039	Jansen et al.	Feb 2017	B2
9591975	Dalvi et al.	Mar 2017	B2
9622692	Lamego et al.	Apr 2017	B2
9622693	Diab	Apr 2017	B2
D788312	Al-Ali et al.	May 2017	S
9636055	Al Ali et al.	May 2017	B2
9636056	Al-Ali	May 2017	B2
9649054	Lamego et al.	May 2017	B2
9662052	Al-Ali et al.	May 2017	B2
9668679	Schurman et al.	Jun 2017	B2
9668680	Bruinsma et al.	Jun 2017	B2
9668703	Al-Ali	Jun 2017	B2
9675286	Diab	Jun 2017	B2
9687160	Kiani	Jun 2017	B2
9693719	Al-Ali et al.	Jul 2017	B2
9693737	Al-Ali	Jul 2017	B2
9697928	Al-Ali et al.	Jul 2017	B2
9717425	Kiani et al.	Aug 2017	B2
9717458	Lamego et al.	Aug 2017	B2
9724016	Al-Ali et al.	Aug 2017	B1
9724024	Al-Ali	Aug 2017	B2
9724025	Kiani et al.	Aug 2017	B1
9730640	Diab et al.	Aug 2017	B2
9743887	Al-Ali et al.	Aug 2017	B2
9749232	Sampath et al.	Aug 2017	B2
9750442	Olsen	Sep 2017	B2
9750443	Smith et al.	Sep 2017	B2
9750461	Telfort	Sep 2017	B1
9775545	Al-Ali et al.	Oct 2017	B2
9775546	Diab et al.	Oct 2017	B2
9775570	Al-Ali	Oct 2017	B2
9778079	Al-Ali et al.	Oct 2017	B1
9782077	Lamego et al.	Oct 2017	B2
9782110	Kiani	Oct 2017	B2
9787568	Lamego et al.	Oct 2017	B2
9788735	Al-Ali	Oct 2017	B2
9788768	Al-Ali et al.	Oct 2017	B2
9795300	Al-Ali	Oct 2017	B2
9795310	Al-Ali	Oct 2017	B2
9795358	Telfort et al.	Oct 2017	B2
9795739	Al-Ali et al.	Oct 2017	B2
9801556	Kiani	Oct 2017	B2
9801588	Weber et al.	Oct 2017	B2
9808188	Perea et al.	Nov 2017	B1
9814418	Weber et al.	Nov 2017	B2
9820691	Kiani	Nov 2017	B2
9833152	Kiani et al.	Dec 2017	B2
9833180	Shakespeare et al.	Dec 2017	B2
9839379	Al-Ali et al.	Dec 2017	B2
9839381	Weber et al.	Dec 2017	B1
9847002	Kiani et al.	Dec 2017	B2
9847749	Kiani et al.	Dec 2017	B2
9848800	Lee et al.	Dec 2017	B1
9848806	Al-Ali	Dec 2017	B2
9848807	Lamego	Dec 2017	B2
9861298	Eckerbom et al.	Jan 2018	B2
9861304	Al-Ali et al.	Jan 2018	B2
9861305	Weber et al.	Jan 2018	B1
9867578	Al-Ali et al.	Jan 2018	B2
9872623	Al-Ali	Jan 2018	B2
9876320	Coverston et al.	Jan 2018	B2
9877650	Muhsin et al.	Jan 2018	B2
9877686	Al-Ali et al.	Jan 2018	B2
9891079	Dalvi	Feb 2018	B2
9895107	Al-Ali et al.	Feb 2018	B2
9913617	Al-Ali et al.	Mar 2018	B2
9924893	Schurman et al.	Mar 2018	B2
9924897	Abdul-Hafiz	Mar 2018	B1
9936917	Poeze et al.	Apr 2018	B2
9943269	Muhsin et al.	Apr 2018	B2
9949676	Al-Ali	Apr 2018	B2
9955937	Telfort	May 2018	B2
9965946	Al-Ali et al.	May 2018	B2
9980667	Kiani et al.	May 2018	B2
D820865	Muhsin et al.	Jun 2018	S
9986919	Lamego et al.	Jun 2018	B2
9986952	Dalvi et al.	Jun 2018	B2
9989560	Poeze et al.	Jun 2018	B2
9993207	Al-Ali et al.	Jun 2018	B2
10007758	Al-Ali et al.	Jun 2018	B2
D822215	Al-Ali et al.	Jul 2018	S
D822216	Barker et al.	Jul 2018	S
10010276	Al-Ali et al.	Jul 2018	B2
10032002	Kiani et al.	Jul 2018	B2
10039482	Al-Ali et al.	Aug 2018	B2
10052037	Kinast et al.	Aug 2018	B2
10058275	Al-Ali et al.	Aug 2018	B2
10064562	Al-Ali	Sep 2018	B2
10086138	Novak, Jr.	Oct 2018	B1
10092200	Al-Ali et al.	Oct 2018	B2
10092249	Kiani et al.	Oct 2018	B2
10098550	Al-Ali et al.	Oct 2018	B2
10098591	Al-Ali et al.	Oct 2018	B2
10098610	Al-Ali et al.	Oct 2018	B2
10111591	Dyell et al.	Oct 2018	B2
D833624	DeJong et al.	Nov 2018	S
10123726	Al-Ali et al.	Nov 2018	B2
10123729	Dyell et al.	Nov 2018	B2
10130289	Al-Ali et al.	Nov 2018	B2
10130291	Schurman et al.	Nov 2018	B2
D835282	Barker et al.	Dec 2018	S
D835283	Barker et al.	Dec 2018	S
D835284	Barker et al.	Dec 2018	S
D835285	Barker et al.	Dec 2018	S
10149616	Al-Ali et al.	Dec 2018	B2
10154815	Al-Ali et al.	Dec 2018	B2
10159412	Lamego et al.	Dec 2018	B2
10188296	Al-Ali et al.	Jan 2019	B2
10188331	Kiani et al.	Jan 2019	B1
10188348	Al-Ali et al.	Jan 2019	B2
RE47218	Al-Ali	Feb 2019	E
RE47244	Kiani et al.	Feb 2019	E
RE47249	Kiani et al.	Feb 2019	E
10194847	Al-Ali	Feb 2019	B2
10194848	Kiani et al.	Feb 2019	B1
10201298	Al-Ali et al.	Feb 2019	B2
10205272	Kiani et al.	Feb 2019	B2
10205291	Scruggs et al.	Feb 2019	B2
10213108	Al-Ali	Feb 2019	B2
10219706	Al-Ali	Mar 2019	B2
10219746	McHale et al.	Mar 2019	B2
10226187	Al-Ali et al.	Mar 2019	B2
10226576	Kiani	Mar 2019	B2
10231657	Al-Ali et al.	Mar 2019	B2
10231670	Blank et al.	Mar 2019	B2
10231676	Al-Ali et al.	Mar 2019	B2
RE47353	Kiani et al.	Apr 2019	E
10251585	Al-Ali et al.	Apr 2019	B2
10251586	Lamego	Apr 2019	B2
10255994	Sampath et al.	Apr 2019	B2
10258265	Poeze et al.	Apr 2019	B1
10258266	Poeze et al.	Apr 2019	B1
10271748	Al-Ali	Apr 2019	B2
10278626	Schurman et al.	May 2019	B2
10278648	Al-Ali et al.	May 2019	B2
10279247	Kiani	May 2019	B2
10292628	Poeze et al.	May 2019	B1
10292657	Abdul-Hafiz et al.	May 2019	B2
10292664	Al-Ali	May 2019	B2
10299708	Poeze et al.	May 2019	B1
10299709	Perea et al.	May 2019	B2
10299720	Brown et al.	May 2019	B2
10305775	Lamego et al.	May 2019	B2
10307111	Muhsin et al.	Jun 2019	B2
10325681	Sampath et al.	Jun 2019	B2
10327337	Schmidt et al.	Jun 2019	B2
10327713	Barker et al.	Jun 2019	B2
10332630	Al-Ali	Jun 2019	B2
10335033	Al-Ali	Jul 2019	B2
10335068	Poeze et al.	Jul 2019	B2
10335072	Al-Ali et al.	Jul 2019	B2
10342470	Al-Ali et al.	Jul 2019	B2
10342487	Al-Ali et al.	Jul 2019	B2
10342497	Al-Ali et al.	Jul 2019	B2
10349895	Telfort et al.	Jul 2019	B2
10349898	Al-Ali et al.	Jul 2019	B2
10354504	Kiani et al.	Jul 2019	B2
10357206	Weber et al.	Jul 2019	B2
10357209	Al-Ali	Jul 2019	B2
10366787	Sampath et al.	Jul 2019	B2
10368787	Reichgott et al.	Aug 2019	B2
10376190	Poeze et al.	Aug 2019	B1
10376191	Poeze et al.	Aug 2019	B1
10383520	Wojtczuk et al.	Aug 2019	B2
10383527	Al-Ali	Aug 2019	B2
10388120	Muhsin et al.	Aug 2019	B2
10398320	Kiani et al.	Sep 2019	B2
10405804	Al-Ali	Sep 2019	B2
10413666	Al-Ali et al.	Sep 2019	B2
10420493	Al-Ali et al.	Sep 2019	B2
D864120	Forrest et al.	Oct 2019	S
10433776	Al-Ali	Oct 2019	B2
10441181	Telfort et al.	Oct 2019	B1
10441196	Eckerbom et al.	Oct 2019	B2
10448844	Al-Ali et al.	Oct 2019	B2
10448871	Al-Ali et al.	Oct 2019	B2
10456038	Lamego et al.	Oct 2019	B2
10463340	Telfort et al.	Nov 2019	B2
10471159	Lapotko et al.	Nov 2019	B1
10505311	Al-Ali et al.	Dec 2019	B2
10524738	Olsen	Jan 2020	B2
10532174	Al-Ali	Jan 2020	B2
10537285	Shreim et al.	Jan 2020	B2
10542903	Al-Ali et al.	Jan 2020	B2
10555678	Dalvi et al.	Feb 2020	B2
10568553	O'Neil et al.	Feb 2020	B2
RE47882	Al-Ali	Mar 2020	E
10608817	Haider et al.	Mar 2020	B2
D880477	Forrest et al.	Apr 2020	S
10617302	Al-Ali et al.	Apr 2020	B2
10617335	Al-Ali et al.	Apr 2020	B2
10637181	Al-Ali et al.	Apr 2020	B2
D887548	Abdul-Hafiz et al.	Jun 2020	S
D887549	Abdul-Hafiz et al.	Jun 2020	S
10667764	Ahmed et al.	Jun 2020	B2
D890708	Forrest et al.	Jul 2020	S
10721785	Al-Ali	Jul 2020	B2
10736518	Al-Ali et al.	Aug 2020	B2
10750984	Pauley et al.	Aug 2020	B2
D897098	Al-Ali	Sep 2020	S
10779098	Iswanto et al.	Sep 2020	B2
10827961	Iyengar et al.	Nov 2020	B1
10828007	Telfort et al.	Nov 2020	B1
10832818	Muhsin et al.	Nov 2020	B2
10849554	Shreim et al.	Dec 2020	B2
10856750	Indorf et al.	Dec 2020	B2
D906970	Forrest et al.	Jan 2021	S
10918281	Al-Ali et al.	Feb 2021	B2
10932705	Muhsin et al.	Mar 2021	B2
10932729	Kiani et al.	Mar 2021	B2
10939878	Kiani et al.	Mar 2021	B2
D916135	Indorf et al.	Apr 2021	S
D917550	Indorf et al.	Apr 2021	S
D917564	Indorf et al.	Apr 2021	S
D917704	Al-Ali et al.	Apr 2021	S
10987066	Chandran et al.	Apr 2021	B2
10991135	Al-Ali et al.	Apr 2021	B2
D919094	Al-Ali et al.	May 2021	S
D919100	Al-Ali et al.	May 2021	S
11006867	Al-Ali	May 2021	B2
D921202	Al-Ali et al.	Jun 2021	S
11024064	Muhsin et al.	Jun 2021	B2
11026604	Chen et al.	Jun 2021	B2
D925597	Chandran et al.	Jul 2021	S
D927699	Al-Ali et al.	Aug 2021	S
11076777	Lee et al.	Aug 2021	B2
11114188	Poeze et al.	Sep 2021	B2
11147518	Al-Ali et al.	Oct 2021	B1
20010034477	Mansfield et al.	Oct 2001	A1
20010039483	Brand et al.	Nov 2001	A1
20020010401	Bushmakin et al.	Jan 2002	A1
20020058864	Mansfield et al.	May 2002	A1
20020133080	Apruzzese et al.	Sep 2002	A1
20030013975	Kiani	Jan 2003	A1
20030018243	Gerhardt et al.	Jan 2003	A1
20030144582	Cohen et al.	Jul 2003	A1
20030156288	Barnum et al.	Aug 2003	A1
20030212312	Coffin, IV et al.	Nov 2003	A1
20040106163	Workman, Jr. et al.	Jun 2004	A1
20050055276	Kiani et al.	Mar 2005	A1
20050234317	Kiani	Oct 2005	A1
20060073719	Kiani	Apr 2006	A1
20060161054	Reuss et al.	Jul 2006	A1
20060189871	Al-Ali et al.	Aug 2006	A1
20070073116	Kiani et al.	Mar 2007	A1
20070180140	Welch et al.	Aug 2007	A1
20070244377	Cozad et al.	Oct 2007	A1
20070282478	Al-Ali et al.	Dec 2007	A1
20080064965	Jay et al.	Mar 2008	A1
20080094228	Welch et al.	Apr 2008	A1
20080113618	De Leon et al.	May 2008	A1
20080221418	Al-Ali et al.	Sep 2008	A1
20090036759	Ault et al.	Feb 2009	A1
20090093687	Telfort et al.	Apr 2009	A1
20090095926	MacNeish, III	Apr 2009	A1
20090247984	Lamego et al.	Oct 2009	A1
20090275813	Davis	Nov 2009	A1
20090275844	Al-Ali	Nov 2009	A1
20100004518	Vo et al.	Jan 2010	A1
20100030040	Poeze et al.	Feb 2010	A1
20100099964	O'Reilly et al.	Apr 2010	A1
20100234718	Sampath et al.	Sep 2010	A1
20100270257	Wachman et al.	Oct 2010	A1
20110028806	Merritt et al.	Feb 2011	A1
20110028809	Goodman	Feb 2011	A1
20110040197	Welch et al.	Feb 2011	A1
20110072263	Bishop et al.	Mar 2011	A1
20110081860	Brown et al.	Apr 2011	A1
20110082711	Poeze et al.	Apr 2011	A1
20110087081	Kiani et al.	Apr 2011	A1
20110105854	Kiani et al.	May 2011	A1
20110118561	Tari et al.	May 2011	A1
20110125060	Telfort et al.	May 2011	A1
20110137297	Kiani et al.	Jun 2011	A1
20110172498	Olsen et al.	Jul 2011	A1
20110208015	Welch et al.	Aug 2011	A1
20110230733	Al-Ali	Sep 2011	A1
20120123231	O'Reilly	May 2012	A1
20120165629	Merritt et al.	Jun 2012	A1
20120209082	Al-Ali	Aug 2012	A1
20120209084	Olsen et al.	Aug 2012	A1
20120226117	Lamego et al.	Sep 2012	A1
20120283524	Kiani et al.	Nov 2012	A1
20120319816	Al-Ali	Dec 2012	A1
20130023775	Lamego et al.	Jan 2013	A1
20130041591	Lamego	Feb 2013	A1
20130060147	Welch et al.	Mar 2013	A1
20130096405	Garfio	Apr 2013	A1
20130096936	Sampath et al.	Apr 2013	A1
20130243021	Siskavich	Sep 2013	A1
20130253334	Al-Ali et al.	Sep 2013	A1
20130296672	O'Neil et al.	Nov 2013	A1
20130296713	Al-Ali et al.	Nov 2013	A1
20130324808	Al-Ali et al.	Dec 2013	A1
20130331660	Al-Ali et al.	Dec 2013	A1
20130345921	Al-Ali et al.	Dec 2013	A1
20140012100	Al-Ali et al.	Jan 2014	A1
20140051953	Lamego et al.	Feb 2014	A1
20140081175	Telfort	Mar 2014	A1
20140120564	Workman et al.	May 2014	A1
20140121482	Merritt et al.	May 2014	A1
20140127137	Bellott et al.	May 2014	A1
20140135588	Al-Ali et al.	May 2014	A1
20140163344	Al-Ali	Jun 2014	A1
20140163402	Lamego et al.	Jun 2014	A1
20140166076	Kiani et al.	Jun 2014	A1
20140171763	Diab	Jun 2014	A1
20140180038	Kiani	Jun 2014	A1
20140180154	Sierra et al.	Jun 2014	A1
20140180160	Brown et al.	Jun 2014	A1
20140187973	Brown et al.	Jul 2014	A1
20140213864	Abdul-Hafiz et al.	Jul 2014	A1
20140266790	Al-Ali et al.	Sep 2014	A1
20140275808	Poeze et al.	Sep 2014	A1
20140275835	Lamego et al.	Sep 2014	A1
20140275871	Lamego et al.	Sep 2014	A1
20140275872	Merritt et al.	Sep 2014	A1
20140276115	Dalvi et al.	Sep 2014	A1
20140288400	Diab et al.	Sep 2014	A1
20140316217	Purdon et al.	Oct 2014	A1
20140316218	Purdon et al.	Oct 2014	A1
20140316228	Blank et al.	Oct 2014	A1
20140323825	Al-Ali et al.	Oct 2014	A1
20140323897	Brown et al.	Oct 2014	A1
20140323898	Purdon et al.	Oct 2014	A1
20140330092	Al-Ali et al.	Nov 2014	A1
20140330098	Merritt et al.	Nov 2014	A1
20140357966	Al-Ali et al.	Dec 2014	A1
20150005600	Blank et al.	Jan 2015	A1
20150011907	Purdon et al.	Jan 2015	A1
20150012231	Poeze et al.	Jan 2015	A1
20150032029	Al-Ali et al.	Jan 2015	A1
20150038859	Dalvi et al.	Feb 2015	A1
20150045637	Dalvi	Feb 2015	A1
20150065046	Wilfred et al.	Mar 2015	A1
20150073241	Lamego	Mar 2015	A1
20150080754	Purdon et al.	Mar 2015	A1
20150087936	Al-Ali et al.	Mar 2015	A1
20150094546	Al-Ali	Apr 2015	A1
20150097701	Muhsin et al.	Apr 2015	A1
20150099943	Russell	Apr 2015	A1
20150099950	Al-Ali et al.	Apr 2015	A1
20150099955	Al-Ali et al.	Apr 2015	A1
20150101844	Al-Ali et al.	Apr 2015	A1
20150106121	Muhsin et al.	Apr 2015	A1
20150112151	Muhsin et al.	Apr 2015	A1
20150116076	Al-Ali et al.	Apr 2015	A1
20150126830	Schurman et al.	May 2015	A1
20150165312	Kiani	Jun 2015	A1
20150196249	Brown et al.	Jul 2015	A1
20150216459	Al-Ali et al.	Aug 2015	A1
20150230755	Al-Ali et al.	Aug 2015	A1
20150238722	Al-Ali	Aug 2015	A1
20150245773	Lamego et al.	Sep 2015	A1
20150245794	Al-Ali	Sep 2015	A1
20150257689	Al-Ali et al.	Sep 2015	A1
20150272514	Kiani et al.	Oct 2015	A1
20150351697	Weber et al.	Dec 2015	A1
20150359429	Al-Ali et al.	Dec 2015	A1
20150366507	Blank et al.	Dec 2015	A1
20160029932	Al-Ali	Feb 2016	A1
20160058347	Reichgott et al.	Mar 2016	A1
20160066824	Al-Ali et al.	Mar 2016	A1
20160081552	Wojtczuk et al.	Mar 2016	A1
20160095543	Telfort et al.	Apr 2016	A1
20160095548	Al-Ali et al.	Apr 2016	A1
20160103598	Al-Ali et al.	Apr 2016	A1
20160143548	Al-Ali	May 2016	A1
20160166182	Al-Ali et al.	Jun 2016	A1
20160166183	Poeze et al.	Jun 2016	A1
20160192869	Kiani et al.	Jul 2016	A1
20160196388	Lamego	Jul 2016	A1
20160197436	Barker et al.	Jul 2016	A1
20160213281	Eckerbom et al.	Jul 2016	A1
20160228043	O'Neil et al.	Aug 2016	A1
20160233632	Scruggs et al.	Aug 2016	A1
20160234944	Schmidt et al.	Aug 2016	A1
20160270735	Diab et al.	Sep 2016	A1
20160283665	Sampath et al.	Sep 2016	A1
20160287090	Al-Ali et al.	Oct 2016	A1
20160287786	Kiani	Oct 2016	A1
20160296169	McHale et al.	Oct 2016	A1
20160310052	Al-Ali et al.	Oct 2016	A1
20160314260	Kiani	Oct 2016	A1
20160324486	Al-Ali et al.	Nov 2016	A1
20160324488	Olsen	Nov 2016	A1
20160327984	Al-Ali et al.	Nov 2016	A1
20160328528	Al-Ali et al.	Nov 2016	A1
20160331332	Al-Ali	Nov 2016	A1
20160360561	Lee et al.	Dec 2016	A1
20160367173	Dalvi et al.	Dec 2016	A1
20170000394	Al-Ali et al.	Jan 2017	A1
20170007134	Al-Ali et al.	Jan 2017	A1
20170007198	Al-Ali et al.	Jan 2017	A1
20170010848	Hinckley et al.	Jan 2017	A1
20170014083	Diab et al.	Jan 2017	A1
20170014084	Al-Ali et al.	Jan 2017	A1
20170024748	Haider	Jan 2017	A1
20170027456	Kinast et al.	Feb 2017	A1
20170042488	Muhsin	Feb 2017	A1
20170055851	Al-Ali	Mar 2017	A1
20170055882	Al-Ali et al.	Mar 2017	A1
20170055887	Al-Ali	Mar 2017	A1
20170055896	Al-Ali	Mar 2017	A1
20170079594	Telfort et al.	Mar 2017	A1
20170086723	Al-Ali et al.	Mar 2017	A1
20170143281	Olsen	May 2017	A1
20170147774	Kiani	May 2017	A1
20170156620	Al-Ali et al.	Jun 2017	A1
20170173632	Al-Ali	Jun 2017	A1
20170187146	Kiani et al.	Jun 2017	A1
20170188919	Al-Ali et al.	Jul 2017	A1
20170196464	Jansen et al.	Jul 2017	A1
20170196470	Lamego et al.	Jul 2017	A1
20170202490	Al-Ali et al.	Jul 2017	A1
20170214780	Gofman et al.	Jul 2017	A1
20170224262	Al-Ali	Aug 2017	A1
20170228516	Sampath et al.	Aug 2017	A1
20170245790	Al-Ali et al.	Aug 2017	A1
20170251974	Shreim et al.	Sep 2017	A1
20170251975	Shreim et al.	Sep 2017	A1
20170258403	Abdul-Hafiz et al.	Sep 2017	A1
20170311851	Schurman et al.	Nov 2017	A1
20170311891	Kiani et al.	Nov 2017	A1
20170325728	Al-Ali et al.	Nov 2017	A1
20170332976	Al-Ali	Nov 2017	A1
20170340293	Al-Ali et al.	Nov 2017	A1
20170360310	Kiani	Dec 2017	A1
20170367632	Al-Ali et al.	Dec 2017	A1
20180008146	Al-Ali et al.	Jan 2018	A1
20180013562	Haider et al.	Jan 2018	A1
20180014752	Al-Ali et al.	Jan 2018	A1
20180028124	Al-Ali et al.	Feb 2018	A1
20180055385	Al-Ali	Mar 2018	A1
20180055390	Kiani et al.	Mar 2018	A1
20180055430	Diab et al.	Mar 2018	A1
20180064381	Shakespeare et al.	Mar 2018	A1
20180069776	Lamego et al.	Mar 2018	A1
20180070867	Smith et al.	Mar 2018	A1
20180082767	Al-Ali et al.	Mar 2018	A1
20180085068	Telfort	Mar 2018	A1
20180087937	Al-Ali et al.	Mar 2018	A1
20180103874	Lee et al.	Apr 2018	A1
20180103905	Kiani	Apr 2018	A1
20180110478	Al-Ali	Apr 2018	A1
20180116575	Perea et al.	May 2018	A1
20180125368	Lamego et al.	May 2018	A1
20180125430	Al-Ali et al.	May 2018	A1
20180125445	Telfort et al.	May 2018	A1
20180130325	Kiani et al.	May 2018	A1
20180132769	Weber et al.	May 2018	A1
20180132770	Lamego	May 2018	A1
20180146901	Al-Ali et al.	May 2018	A1
20180146902	Kiani et al.	May 2018	A1
20180153442	Eckerbom et al.	Jun 2018	A1
20180153446	Kiani	Jun 2018	A1
20180153447	Al-Ali et al.	Jun 2018	A1
20180153448	Weber et al.	Jun 2018	A1
20180161499	Al-Ali et al.	Jun 2018	A1
20180168491	Al-Ali et al.	Jun 2018	A1
20180174679	Sampath et al.	Jun 2018	A1
20180174680	Sampath et al.	Jun 2018	A1
20180182484	Sampath et al.	Jun 2018	A1
20180184917	Kiani	Jul 2018	A1
20180192924	Al-Ali	Jul 2018	A1
20180192953	Shreim et al.	Jul 2018	A1
20180192955	Al-Ali et al.	Jul 2018	A1
20180199871	Pauley et al.	Jul 2018	A1
20180206795	Al-Ali	Jul 2018	A1
20180206815	Telfort	Jul 2018	A1
20180213583	Al-Ali	Jul 2018	A1
20180214031	Kiani et al.	Aug 2018	A1
20180214090	Al-Ali et al.	Aug 2018	A1
20180218792	Muhsin et al.	Aug 2018	A1
20180225960	Al-Ali et al.	Aug 2018	A1
20180238718	Dalvi	Aug 2018	A1
20180242853	Al-Ali	Aug 2018	A1
20180242921	Muhsin et al.	Aug 2018	A1
20180242923	Al-Ali et al.	Aug 2018	A1
20180242924	Barker et al.	Aug 2018	A1
20180242926	Muhsin et al.	Aug 2018	A1
20180247353	Al-Ali et al.	Aug 2018	A1
20180247712	Muhsin et al.	Aug 2018	A1
20180249933	Schurman et al.	Sep 2018	A1
20180253947	Muhsin et al.	Sep 2018	A1
20180256087	Al-Ali et al.	Sep 2018	A1
20180256113	Weber et al.	Sep 2018	A1
20180285094	Housel et al.	Oct 2018	A1
20180289325	Poeze et al.	Oct 2018	A1
20180289337	Al-Ali et al.	Oct 2018	A1
20180296161	Shreim et al.	Oct 2018	A1
20180300919	Muhsin et al.	Oct 2018	A1
20180310822	Indorf et al.	Nov 2018	A1
20180310823	Al-Ali et al.	Nov 2018	A1
20180317826	Muhsin et al.	Nov 2018	A1
20180317841	Novak, Jr.	Nov 2018	A1
20180333055	Lamego et al.	Nov 2018	A1
20180333087	Al-Ali	Nov 2018	A1
20190000317	Muhsin et al.	Jan 2019	A1
20190000362	Kiani et al.	Jan 2019	A1
20190015023	Monfre	Jan 2019	A1
20190021638	Al-Ali et al.	Jan 2019	A1
20190029574	Schurman et al.	Jan 2019	A1
20190029578	Al-Ali et al.	Jan 2019	A1
20190038143	Al-Ali	Feb 2019	A1
20190058280	Al-Ali et al.	Feb 2019	A1
20190058281	Al-Ali et al.	Feb 2019	A1
20190069813	Al-Ali	Mar 2019	A1
20190069814	Al-Ali	Mar 2019	A1
20190076028	Al-Ali et al.	Mar 2019	A1
20190082979	Al-Ali et al.	Mar 2019	A1
20190090748	Al-Ali	Mar 2019	A1
20190090760	Kinast et al.	Mar 2019	A1
20190090764	Al-Ali	Mar 2019	A1
20190104973	Poeze et al.	Apr 2019	A1
20190110719	Poeze et al.	Apr 2019	A1
20190117070	Muhsin et al.	Apr 2019	A1
20190117139	Al-Ali et al.	Apr 2019	A1
20190117140	Al-Ali et al.	Apr 2019	A1
20190117141	Al-Ali	Apr 2019	A1
20190117930	Al-Ali	Apr 2019	A1
20190122763	Sampath et al.	Apr 2019	A1
20190133525	Al-Ali et al.	May 2019	A1
20190142283	Lamego et al.	May 2019	A1
20190142344	Telfort et al.	May 2019	A1
20190150800	Poeze et al.	May 2019	A1
20190150856	Kiani et al.	May 2019	A1
20190167161	Al-Ali et al.	Jun 2019	A1
20190175019	Al-Ali et al.	Jun 2019	A1
20190192076	McHale et al.	Jun 2019	A1
20190200941	Chandran et al.	Jul 2019	A1
20190201623	Kiani	Jul 2019	A1
20190209025	Al-Ali	Jul 2019	A1
20190214778	Scruggs et al.	Jul 2019	A1
20190216319	Poeze et al.	Jul 2019	A1
20190216379	Al-Ali et al.	Jul 2019	A1
20190221966	Kiani et al.	Jul 2019	A1
20190223804	Blank et al.	Jul 2019	A1
20190231199	Al-Ali et al.	Aug 2019	A1
20190231241	Al-Ali et al.	Aug 2019	A1
20190231270	Abdul-Hafiz et al.	Aug 2019	A1
20190239787	Pauley et al.	Aug 2019	A1
20190239824	Muhsin et al.	Aug 2019	A1
20190254578	Lamego	Aug 2019	A1
20190261857	Al-Ali	Aug 2019	A1
20190269370	Al-Ali et al.	Sep 2019	A1
20190274606	Kiani et al.	Sep 2019	A1
20190274627	Al-Ali et al.	Sep 2019	A1
20190274635	Al-Ali et al.	Sep 2019	A1
20190290136	Dalvi et al.	Sep 2019	A1
20190298270	Al-Ali et al.	Oct 2019	A1
20190304601	Sampath et al.	Oct 2019	A1
20190304605	Al-Ali	Oct 2019	A1
20190307377	Perea et al.	Oct 2019	A1
20190320906	Olsen	Oct 2019	A1
20190320959	Al-Ali	Oct 2019	A1
20190320988	Ahmed et al.	Oct 2019	A1
20190325722	Kiani et al.	Oct 2019	A1
20190374139	Kiani et al.	Dec 2019	A1
20190374173	Kiani et al.	Dec 2019	A1
20190374713	Kiani et al.	Dec 2019	A1
20200021930	Iswanto et al.	Jan 2020	A1
20200060869	Telfort et al.	Feb 2020	A1
20200111552	Ahmed	Apr 2020	A1
20200113435	Muhsin	Apr 2020	A1
20200113488	Al-Ali et al.	Apr 2020	A1
20200113496	Scruggs et al.	Apr 2020	A1
20200113497	Triman et al.	Apr 2020	A1
20200113520	Abdul-Hafiz et al.	Apr 2020	A1
20200138288	Al-Ali et al.	May 2020	A1
20200138368	Kiani et al.	May 2020	A1
20200163597	Dalvi et al.	May 2020	A1
20200196877	Vo et al.	Jun 2020	A1
20200253474	Muhsin et al.	Aug 2020	A1
20200253544	Belur Nagaraj et al.	Aug 2020	A1
20200275841	Telfort et al.	Sep 2020	A1
20200288983	Telfort et al.	Sep 2020	A1
20200321793	Al-Ali et al.	Oct 2020	A1
20200329983	Al-Ali et al.	Oct 2020	A1
20200329984	Al-Ali et al.	Oct 2020	A1
20200329993	Al-Ali et al.	Oct 2020	A1
20200330037	Al-Ali et al.	Oct 2020	A1
20210022628	Telfort et al.	Jan 2021	A1
20210104173	Pauley et al.	Apr 2021	A1
20210113121	Diab et al.	Apr 2021	A1
20210117525	Kiani et al.	Apr 2021	A1
20210118581	Kiani et al.	Apr 2021	A1
20210121582	Krishnamani et al.	Apr 2021	A1
20210161465	Barker et al.	Jun 2021	A1
20210236729	Kiani et al.	Aug 2021	A1
20210256267	Ranasinghe et al.	Aug 2021	A1
20210256835	Ranasinghe et al.	Aug 2021	A1
20210275101	Vo et al.	Sep 2021	A1
20210290060	Ahmed	Sep 2021	A1
20210290072	Forrest	Sep 2021	A1
20210290080	Ahmed	Sep 2021	A1
20210290120	Al-Ali	Sep 2021	A1
20210290177	Novak, Jr.	Sep 2021	A1
20210290184	Ahmed	Sep 2021	A1
20210296008	Novak, Jr.	Sep 2021	A1

Foreign Referenced Citations (1)

Number	Date	Country
WO 2017087168	May 2017	WO

Related Publications (1)

	Number	Date	Country
	20220264674 A1	Aug 2022	US

Provisional Applications (2)

	Number	Date	Country
	62505762	May 2017	US
	62447836	Jan 2017	US

Continuations (2)

	Number	Date	Country
Parent	16899386	Jun 2020	US
Child	17678830		US
Parent	15874652	Jan 2018	US
Child	16899386		US

Patient-worn wireless physiological sensor with pairing functionality

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

CPC

International Classifications

Abstract