Patent Grant
11272839
The present disclosure relates to physiological sensors and wireless pairing devices. More specifically, the present disclosure relates to collection of physiological data using physiological sensors and transmitting the data to nearby computing systems using a wireless pairing device.
Conventional physiological measurement systems are limited by the patient cable connection between sensor and monitor. A patient must be located in the immediate vicinity of the monitor. Also, patient relocation requires either disconnection of monitoring equipment and a corresponding loss of measurements or an awkward simultaneous movement of patient equipment and cables. Various devices have been proposed or implemented to provide wireless communication links between sensors and monitors, freeing patients from the patient cable tether.
This disclosure describes, among other things, embodiments of systems, devices, and methods for collecting patient physiological data and transmitting the data to nearby computing systems via wireless transmission.
A sensor system is discloses that can include a disposable sensor usable to monitor a tissue of a patient and a reusable transmitter usable to wirelessly communicate with a patent monitor. The disposable sensor can include a sensor element and a battery to provide power for both the disposable sensor and the reusable transmitter. The sensor element can include one or more emitters and detectors. The reusable transmitter can include an antenna and one or more hardware processors.
A method of pairing a sensor with a computing device is disclosed. The method can include communicating pairing data between a transmitter and a computing device using a first communication protocol. The method can include receiving power from a battery included in a sensor package responsive to mating of the transmitter with the sensor package. The method can include connecting with the computing device based on the received airing data using a second communication protocol. The second communication protocol can be different than the first communication protocol. The method can further include transmitting sensor data to the computing device based on the second protocol connection.
A circuit for a disposable sensor for a system for pairing a noninvasive patient sensor with a computing device is disclosed. The circuit can include a body that can include one or more first electrical contacts. The circuit can include elongate members that include one or more second electrical contacts. The elongate members can extend from the body along a length of the body. The elongate members can be arcuate. The first electrical contacts and the second electrical contacts can be connected such that electrical signals can be transmitted between the first and the second electrical contacts. The first electrical contacts can be operatively connected to a sensor element and a battery of the disposable sensor.
A physiological sensor for a system for pairing a noninvasive patient sensor with a computing device is disclosed. The physiological sensor can include a sensor element. The physiological sensor can include a docking member. The docking member can include a docking surface and a retainer. The retainer can be hingedly coupled to the docking member. The physiological sensor can include a cable operatively coupled to the sensor element and the docking member. The cable can allow signals to be transmitted between the sensor element and the docking member. The retainer can engage a reusable transmitter to hold the reusable transmitter against the docking surface.
In some embodiments, a system for pairing a disposable noninvasive sensor assembly with a monitoring device using a reusable transmitter assembly is disclosed. The disposable noninvasive sensor assembly can collect physiological data of a patient. The system can include a disposable noninvasive sensor assembly and a reusable transmitter assembly. The disposable noninvasive sensor assembly can collect physiological data from a patient. The physiological data can be indicative of physiological condition of the patient. The disposable noninvasive sensor assembly can include a sensor element and a battery. The sensor element can be attached to the patient. The reusable transmitter assembly can receive the physiological data of the patient from the disposable noninvasive sensor assembly. The reusable transmitter assembly can include a processor and a wireless communication module can establish a wireless communication with a patient monitor.
The system of the preceding paragraph can include one or more of following features: The reusable transmitter assembly does not include a power source for providing power for the processor and the wireless communication module. The wireless communication module can include a first antenna. The wireless communication module can also include a second antenna. The reusable transmitter assembly can receive power from the battery of the disposable noninvasive sensor assembly. The reusable transmitter assembly can receive raw physiological data from the disposable noninvasive sensor assembly, and wherein the raw physiological data can be collected by the sensor element. The processor can process the raw physiological data transmitted to the reusable transmitter assembly and generate physiological parameters. The reusable transmitter assembly can transmit the physiological parameters to the patient monitor. The sensor element can include a detector and an emitter. The detector and the emitter can be optical based. The emitters can be light-emitting diodes (LEDs). The disposable noninvasive sensor assembly can be coupled to a patient. The reusable transmitter assembly can be removably coupled to the disposable noninvasive sensor assembly. The reusable transmitter assembly or the disposable noninvasive sensor assembly may be waterproof or shockproof. The wireless communication module can receive electronic data from or transmit electronic data to the patient monitor. The wireless communication module can use at least a first wireless communication protocol to associate the reusable transmitter assembly with the patient monitor, and wherein the wireless communication module can use at least a second wireless communication protocol to transmit data between the wireless communication module and the patient monitor. The first wireless communication protocol can be near-field communication (NFC). The second wireless communication protocol can be different from the first wireless communication protocol. The second wireless communication protocol can be Bluetooth®. The wireless communication between the reusable transmitter assembly and the patient monitor can be based at least on a pairing signal transmitted from the patient monitor to the reusable transmitter assembly and an identification information transmitted from the reusable transmitter assembly to the patient monitor. The patient monitor can transmit the pairing signal to the reusable transmitter assembly when the reusable transmitter assembly is brought within a predetermined distance from the patient monitor. The pairing signal and the identification information can be transmitted via the first wireless communication protocol. The identification information can be unique to the reusable transmitter assembly. The identification information can be an RFID tag associated with the reusable transmitter assembly. The identification information can be transmitted from the reusable transmitter assembly to the patient monitor in response of the transmission of the pairing signal from the patient monitor to the reusable transmitter assembly. The transmission of the identification information may occur automatically. The transmission of the identification information may not occur automatically. The disposable noninvasive sensor assembly can include a dock configured to mate with the reusable transmitter assembly. The dock can include arcuate supports and a flexible circuit comprising elongate members. The elongate members can be supported by the arcuate supports that push the elongate members of the flexible circuit against the reusable transmitter assembly when the reusable transmitter assembly is coupled to the dock of the disposable noninvasive sensor assembly. The flexible circuit can facilitate transmission electronic signals between the disposable noninvasive sensor assembly and the reusable transmitter assembly. The elongate members can include electrical contacts that come in contact with electrical contacts of the reusable transmitter assembly when the reusable transmitter assembly is coupled with the disposable noninvasive sensor assembly. The flexible circuit can be in contact with the battery such that the flexible circuit transmits power from the battery to the reusable transmitter assembly when the reusable transmitter assembly is coupled with the disposable noninvasive sensor assembly. The battery can generate power by reacting with oxygen in the air. The disposable noninvasive sensor assembly can include a housing storing the battery. The housing can include channels and openings, and wherein the channels can facilitate the air to enter into the housing via the openings. The openings may be formed on inner surfaces of the channels such that the openings are exposed to the air when the channels are covered. The channels can be defined on a top surface of the housing. The channels may extend to side edges of the housing. The disposable noninvasive sensor assembly can be removably attached to a patient. The disposable noninvasive sensor assembly can include elongate members that can wrap around a patient. The patient monitor can be a mobile device. The reusable transmitter assembly can be brought proximate to a specific location on the patient monitor to establish the wireless communication between the reusable transmitter assembly and the patient monitor. The patient monitor is a mobile device. The patient monitor can be a bedside patient monitor.
In some embodiments, a method of pairing a noninvasive sensor assembly with a patient monitor using a transmitter is disclosed. The noninvasive sensor assembly can collect physiological data from a patient and transmit the physiological data to the transmitter. The patient monitor can display parameters associated with the physiological data and indicative of physiological condition of the patient. The method can include: receiving, using a transmitter, a pairing signal from a patient monitor via a first wireless communication protocol; transmitting, using the transmitter, an identification information to the patient monitor via the first wireless communication protocol; establishing a wireless communication between the transmitter and the patient monitor based at least on the pairing signal and the identification information, the wireless communication based at least on a second wireless communication protocol; collecting raw physiological data of a patient using a sensor element of the noninvasive sensor assembly; processing, using a processor of the transmitter, the raw physiological data to generate physiological parameters; and transmitting the physiological parameters to the patient monitor via the wireless communication.
The method of preceding paragraph can include one or more of following features: The method can include generating power from the signal using the transmitter. The power can be used for transmission of the identification information. The first wireless communication protocol can be different from the second wireless communication protocol. The transmitter may not require a power source to receive the pairing signal. The transmitter may not include a power source. The method can include receiving power from a battery of the noninvasive sensor assembly. Collecting of the raw physiological data can include: generating an emitter signal using a processor of the noninvasive sensor assembly; transmitting the emitter signal to an emitter of the noninvasive sensor assembly; generating, using the emitter, an optical output based at least on the emitter signal; detecting the optical output using a detector; and converting the optical output to generate the raw physiological data. The transmitter can be reusable. The noninvasive sensor assembly can be disposable. The first wireless communication protocol can be near-field communication (NFC). The second communication protocol can be Bluetooth®. The identification information can be an RFID tag uniquely identifying the transmitter. The transmission of the identification information can occur automatically in response to receiving the pairing signal. Establishing the wireless communication between the transmitter and the patient monitor can include associating the transmitter with the patient monitor using at least in part the pairing signal and the identification information.
In some embodiments, a method of collecting patient physiological data using a noninvasive sensor system having a disposable sensor assembly and a reusable transmitter assembly is disclosed. The reusable transmitter assembly can wirelessly transmit the physiological data to a patient monitor. The method can include: establishing a first wireless communication between a reusable transmitter assembly and a patient monitor; transmitting, using the reusable transmitter, pairing parameters to the patient monitor via the first wireless communication; establishing a second wireless communication between the reusable transmitter and the patient monitor; coupling the reusable transmitter with a disposable sensor assembly; collecting raw physiological data using a sensor element of the disposable sensor assembly; and transmitting, using the reusable transmitter, physiological parameters to the patient monitor.
The method of the preceding paragraph can include one or more of following features: The first wireless communication can be different from the second wireless communication. The first wireless communication can be based on near-field communication (NFC) and the second wireless communication can be based on Bluetooth®. The reusable transmitter may not include a power source. Transmitting the pairing parameters can include: receiving a pairing signal from the patient monitor; and generating power from the pairing signal, the power used for transmitting the pairing parameters to the patient monitor. Transmitting the physiological parameters to the patient monitor can include receiving power from a battery of the disposable sensor assembly. The method can include processing the raw physiological data using a processor of the transmitter to generate physiological parameters. Collecting of the raw physiological data can include: generating an emitter signal; transmitting the emitter signal to an emitter of the disposable sensor assembly; generating, using the emitter, an optical output based at least on the emitter signal; detecting the optical output using a detector; and converting the optical output to generate the raw physiological data. The reusable transmitter can include an RFID tag uniquely identifying the reusable transmitter. The transmission of the pairing parameters can occur automatically after the reusable transmitter is brought within a predetermined distance of the patient monitor. Establishing the second wireless communication between the reusable transmitter and the patient monitor can include associating the reusable transmitter with the patient monitor using at least the pairing parameters. Establishing the first wireless communication between the reusable transmitter and the patient monitor can include bringing the reusable transmitter proximate to a specific location on the patient monitor. The patient monitor can be a mobile device. The patient monitor can be a bedside patient monitor.
In some embodiments, a method of collecting and displaying patient physiological data using a sensor system having a disposable sensor assembly and a reusable transmitter assembly is disclosed. The method can include: establishing a wireless communication between the reusable transmitter and the patient monitor; collecting raw physiological data using a sensor element of the disposable sensor assembly; transmitting, using the reusable transmitter, the raw physiological data to the patient monitor; processing the raw physiological data to determine physiological parameters using a processor of the patient monitor; and displaying, using a display of the patient monitor, the physiological parameters.
The method of the preceding paragraph can include one or more of following features: Establishing the wireless communication between the reusable transmitter assembly and the patient monitor can include: receiving, using the reusable transmitter assembly, pairing signal from the patient monitor; transmitting, using the reusable transmitter assembly, pairing parameters to the patient monitor; and associating the reusable transmitter assembly with the patient monitor using at least in part the pairing parameters. The pairing parameters can be transmitted using a first wireless protocol, and wherein the first wireless protocol can be near-field communication (NFC). The reusable transmitter assembly may not require a power source to receive the pairing signal. The reusable transmitter assembly can include a RFID tag that can include the pairing parameters. The transmission of the pairing parameters can occur automatically in response to the receipt of the pairing signal. The reusable transmitter assembly may not include a power source. The reusable transmitter assembly can receive power from a battery of the disposable sensor assembly. Collecting the raw physiological data can include: generating an emitter signal; transmitting the emitter signal to an emitter of the disposable sensor assembly; generating, using the emitter, an optical output based at least on the emitter signal; detecting the optical output using a detector; and converting the optical output to generate the raw physiological data. The wireless communication between the reusable transmitter assembly and the patient monitor can be based at least on Bluetooth®. Establishing the wireless communication between the transmitter and the patient monitor can include associating the reusable transmitter assembly with the patient monitor. Establishing the wireless communication between the reusable transmitter and the patient monitor can include bringing the reusable transmitter proximate to a specific location on the patient monitor.
In some embodiments, a flexible circuit for a disposable sensor assembly is disclosed. The disposable sensor assembly can collect physiological data of a patient and transmit the physiological data to a patient monitor via a transmitter assembly. The flexible circuit can include a body and elongate members. The body can include a first plurality of electrical contacts. The elongate members can include a second plurality of electrical contacts. The elongate members can extend from the body along a longitudinal axis of the body. The elongate members can be arcuate. The first plurality of electrical contacts can be operatively connected to a sensor element and a battery of the disposable sensor. The first electrical contacts and the second electrical contacts can be connected such that electrical signals can be transmitted between the first and the second electrical contacts.
The flexible circuit of the preceding paragraph can include one or more of following features: The elongate members can be flat. An interaction between tips of the elongate members and the disposable sensor can cause the elongate members to be arcuate. The second plurality of electrical contacts can be located at an apex of each of the elongate members when the elongate members are arcuate. The elongate members can be arcuate with a first degree of curvature when installed on the disposable sensor, and wherein the elongate members can be arcuate with a second degree of curvature when a reusable transmitter is mated with the disposable sensor. The second degree of curvature can be less than the first degree of curvature. The elongate members can have a first height when installed on the disposable sensor, and the elongate members can have a second height when a reusable transmitter is mated with the disposable sensor. The first height can be greater than the second height. The elongate members can be supported by a plurality of arcuate supports of the disposable sensor when installed on the disposable sensor.
In some embodiments, a pairing system for establishing a wireless communication between a transmitter assembly of a physiological sensor system and a patient monitor is disclosed. The patient monitor can display physiological parameters of a patient. The pairing system can include an adaptor, a housing, and a cable assembly. The adaptor can be coupled to a patient monitor. The housing can include a processor and a wireless communication interface. The processor can generate a pairing signal. The wireless communication interface can establish a wireless communication with a transmitter assembly and receive physiological parameters from the transmitter assembly. The physiological parameters can be based at least in part on physiological data collected by a disposable noninvasive physiological sensor removably coupled to the patient. The cable assembly can be coupled to the adaptor and the housing. The cable assembly can allow transmission of the physiological parameters the adaptor and the housing.
The pairing system of the preceding paragraph can include one or more of following features: The housing can be removably coupled to a body of the patient monitor. The processor can transmit the pairing signal to the transmitter assembly. The pairing signal can be used to establish the wireless communication between the wireless communication interface and the transmitter assembly. The pairing signal can be transmitted to the transmitter assembly when the transmitter assembly is proximate a specific location on the patient monitor. The housing can include an inset surface. The inset surface can indicate a location of the wireless communication interface. The wireless communication interface can establish a wireless communication with the transmitter assembly via a first wireless communication protocol. The first wireless communication protocol can be near-field communication (NFC). The wireless communication interface can wirelessly receive an identification information from the transmitter assembly. The identification information can be an RFID tag unique to the transmitter assembly. The wireless communication interface can wirelessly receive the identification information from the transmitter assembly in response to the transmission of the pairing signal. The processor of the housing can receive the identification information from the wireless communication interface and transmit the identification information to the patient monitor. The identification information can include pairing parameters unique to the transmitter assembly. The patient monitor can establish a wireless communication with the transmitter assembly based at least on the identification information of the transmitter assembly. The wireless communication between the patient monitor and the transmitter assembly can be based on Bluetooth®. The pairing system can receive power from the patient monitor via the adaptor and the cable assembly. The pairing signal can generate power for the transmitter assembly. The pairing signal can be transmitted to the transmitter assembly when the transmitter assembly is within a predetermined distance from the wireless communication interface or when the transmitter assembly contacts the housing. The wireless communication interface can receive physiological parameters from the transmitter assembly and transmit the physiological parameters to the patient monitor for display. The wireless communication interface can receive physiological parameters from the transmitter assembly using a wireless communication protocol different from one used for transmitting the pairing signal to the transmitter assembly. The adaptor can be plugged into a sensor input of the patient monitor. The pairing system can provide wireless communication capability for the patient monitor.
In some embodiments, an apparatus for storing a reusable wireless transmitter assembly is disclosed. The reusable wireless transmitter can receive patient physiological data from a disposable noninvasive sensor assembly and transmit the patient physiological data to a patient monitor via a wireless communication. The apparatus can include a base and a body. The base can be coupled to a housing of a patient monitor. The patient monitor can receive patient physiological parameters from a reusable wireless transmitter assembly. The body can include a support surface that can receive a corresponding mating surface of the reusable wireless transmitter assembly. The body can protrude out from the base in a direction orthogonal to the base. The body can include a magnet to retain the reusable wireless transmitter assembly. The support surface can be arcuate and perpendicular to the base.
The apparatus of the preceding paragraph can include one or more of following features: The base can include a magnet configured to retain the wireless transmitter. The magnet can be positioned about the support surface of the body. An outer surface of the body can be flush with an outer surface of the reusable wireless transmitter assembly when the reusable wireless transmitter assembly is coupled to the apparatus. A shape of the base can correspond to a shape of the reusable wireless transmitter assembly such that an outline of the base matches that of the reusable wireless transmitter assembly when the reusable wireless transmitter assembly is coupled to the apparatus.
In some embodiments, a method of coupling a wireless transmitter assembly with a noninvasive sensor assembly configured to collect physiological data from a patient is disclosed. The method can include: positioning a wireless transmitter assembly such that legs of the wireless transmitter assembly can be substantially aligned with and facing slots formed on a dock of a noninvasive sensor assembly, the slots can be dimensioned and shaped to receive the legs of the wireless transmitter assembly; pushing the wireless transmitter assembly towards the slots such that the legs can be positioned within the slots; and pressing down the wireless transmitter assembly to removably couple the wireless transmitter assembly with the dock of the noninvasive sensor assembly, thereby causing the wireless transmitter assembly to receive patient physiological data from the noninvasive sensor assembly and to transmit the patient physiological data to a proximate bedside patient monitor.
The method of the preceding paragraph can include one or more of following features: The sensor assembly can include a housing. The slots can be defined between the dock and the housing. The housing can include lips. Each of the lips can correspond to each of the slots of the dock. The legs of the wireless transmitter can be positioned under the lips of the housing. The dock can include a retainer that can hold the transmitter assembly within the dock. The retainer can be positioned opposite from the slots. Pressing down the transmitter assembly can cause the retainer to change from a first configuration to a second configuration, thereby allowing the transmitter assembly to be seated within the dock. The retainer can be substantially vertical with respect to the dock when in the first configuration, and the retainer can be bent in a direction away from the dock in the second configuration. The retainer can be in the first configuration when the transmitter assembly is coupled with the dock, and the retainer in the first configuration can hold the transmitter assembly within the dock.
In some embodiments, a system for collecting patient physiological parameters and transmitting the parameters to a mobile device is disclosed. The patient physiological parameters can be collected with a noninvasive sensor assembly. The parameters can be transmitted to the mobile device using a transmitter assembly. The system can include a noninvasive sensor assembly, a transmitter assembly, and a patient monitor. The noninvasive sensor assembly can include a sensor element and a battery in a first housing. The sensor element can collect physiological data from a patient. The transmitter assembly can include a processor and a wireless communication module in a second housing. The transmitter assembly can establish wireless communication with a patient monitor. The patient monitor can display physiological parameters and transmit the patient physiological parameters to a mobile device.
The system of the preceding paragraph can include one of more of following features: The sensor element can include an emitter and a detector. The emitter and the detector can be optical. The transmitter assembly may not include a power source for providing power for the processor and the wireless communication module. The transmitter assembly can be reusable. The noninvasive sensor assembly can be disposable. The transmitter assembly can receive power from the battery of the noninvasive sensor assembly. The reusable transmitter assembly can receive raw physiological data from the disposable sensor assembly. The raw physiological data may be collected by the sensor element. The noninvasive sensor assembly can be removably coupled to the patient. The noninvasive sensor assembly can be coupled to a wrist of the patient. The sensor element can be coupled to a fingertip of the patient. The first housing or the second housing can be waterproof or shockproof. The wireless communication module can use a first wireless communication protocol to associate the transmitter assembly with the patient monitor, and the wireless communication module can use a second wireless communication protocol to transmit data to the patient monitor. The processor of the transmitter assembly can receive the physiological data from the noninvasive sensor assembly and process the physiological data to generate the physiological parameters. The transmitter assembly can wirelessly transmit the physiological parameters to a mobile device. The patient monitor can wirelessly transmit the physiological parameters to a mobile device. The patient monitor can be Root® platform.
In some embodiments, a method transmitting physiological data from a noninvasive sensor assembly to a patient monitor using a wireless transmitter assembly is disclosed. The method can include: approximating a wireless transmitter assembly to a pairing device of a patient monitor to receive a pairing signal from the pairing device and transmit pairing parameters to the pairing device; and coupling the wireless transmitter assembly to a noninvasive sensor assembly to receive power from a battery of a noninvasive sensor assembly and receive physiological data from a sensor element of the noninvasive sensor assembly, wherein the wireless transmitter assembly can determine physiological parameters based at least in part on the physiological data and transmit the physiological parameters to the patient monitor.
The method of the preceding paragraph can include one or more of following features: The reception of the pairing signal and the transmission of the pairing parameters can be conducted via a first wireless communication protocol. The wireless transmitter assembly can transmit the physiological parameters to the patient monitor via a second wireless communication protocol. The first wireless communication protocol can be near-field communication (NFC). The second wireless communication protocol can Bluetooth®. The wireless transmitter assembly may not include a power source. The wireless transmitter can be reusable. The wireless transmitter assembly can be coupled to a dock of the noninvasive sensor assembly. The sensor element can include a detector and an emitter. The detector and the emitter can be optical. Coupling the wireless transmitter assembly automatically can cause the wireless transmitter assembly to determine physiological parameters and transmit the physiological parameters to the patient monitor.
In some embodiments, a flexible circuit for transmitting physiological data from a noninvasive sensor assembly to a transmitter assembly is disclosed. The transmission of the physiological data can occur when the transmitter assembly is coupled to the noninvasive sensor assembly. The flexible circuit can include a first plurality of electrical contacts, a second plurality of electrical contacts, a flexible body, and flexible elongate members. The first plurality of electrical contacts can receive physiological data from a sensor element of the noninvasive sensor assembly. The second plurality of electrical contacts can be in electronic communication with the first plurality of electrical contacts and can receive the physiological data from the first plurality of electrical contacts. The flexible elongate members can be coupled to the flexible body. Each of the elongate members can include a corresponding electrical contact of the second plurality of electrical contacts such that the second plurality of electrical contacts are in contact with the transmitter assembly when the transmitter assembly is coupled to the noninvasive sensor assembly.
The flexible circuit of the preceding paragraph can include one or more of following features: The flexible circuit can be coupled to the noninvasive sensor assembly. The flexible elongate members can be arcuate. Each of the flexible elongate members can have a first portion extending away and upwards with respect to a longitudinal axis of the body and a second portion extending away and downwards with respect to the longitudinal axis. The flexible elongate members can be supported on arcuate supports of the noninvasive sensor assembly. The arcuate supports can ensure contact between the flexible elongate members and the transmitter assembly when the transmitter assembly is coupled to the noninvasive sensor assembly. The sensor element of the noninvasive sensor assembly can include an emitter and a detector. The flexible elongate members of the flexible circuit can have a first configuration when the transmitter assembly is not coupled to the noninvasive sensor assembly and a second configuration when the transmitter assembly is coupled to the noninvasive sensor. The elongate members in the first configuration can be associated with a first degree of curvature and the elongate member in the second configuration can be associated with a second degree of curvature. The second degree of curvature can be less than the first degree of curvature. The flexible circuit can be coupled to a battery of the noninvasive sensor assembly such that the flexible circuit can receive power from a battery of the noninvasive sensor assembly and transmit the power to the transmitter assembly when the transmitter assembly is coupled to the dock.
In some embodiments, a wearable noninvasive sensor assembly for collecting physiological data from a patient is disclosed. The wearable noninvasive sensor assembly can include a dock, a transmitter assembly, and a sensor element. The dock can be coupled to a housing. The dock can include a retainer and an attachment mechanism. The transmitter assembly can be coupled to the dock. The sensor element can be coupled to the housing via a cable. The sensor element can collect physiological data from the patient. At least a portion of the cable can be positioned within the retainer.
The wearable noninvasive sensor assembly of the preceding paragraph can include one or more of following features: The attachment mechanism can include a plurality of straps that can wrap around the patient. The sensor element can include an emitter and a detector. The retainer can be coupled along a side of the dock and include a channel that can receive the cable. The retainer can limit the movement of the cable in at least a first direction while allowing movement in a second direction. The housing can house a battery that powers the sensor element. The battery can further power the transmitter assembly when the transmitter assembly is coupled to the dock. The wearable noninvasive sensor assembly can be coupled to the patient's wrist and the sensor element can be coupled to the patient's fingertip. The transmitter assembly can include a processor and a wireless communication module that can establish a wireless communication with a patient monitor. The wearable noninvasive sensor assembly can be waterproof or shockproof. The transmitter assembly can establish a wireless communication with a patient monitor, and the patient monitor can receive the physiological data from the transmitter assembly and display the physiological data on a display. The dock can include arcuate supports and a flexible circuit that can include elongate members supported by the arcuate supports. The arcuate supports can ensure contact between the elongate members of the flexible circuit and the transmitter assembly when the transmitter assembly is coupled to the dock. The dock can further comprises a flexible circuit. The flexible circuit can include elongate members. The elongate members can be flexible. The elongate members can be supported on arcuate supports of the dock, wherein the arcuate supports can ensure contact between the elongate members and the transmitter assembly when the transmitter assembly is coupled to the noninvasive sensor assembly. The elongate members can have a first configuration when the transmitter assembly is not coupled to the dock and a second configuration when the transmitter assembly is coupled to the dock. The elongate members in the first configuration can be associated with a first degree of curvature and the elongate member in the second configuration can be associated with a second degree of curvature. The second degree of curvature can be less than the first degree of curvature. The flexible circuit can be coupled to a battery of the noninvasive sensor assembly such that the flexible circuit receives power from a battery of the noninvasive sensor assembly and transmits the power to the transmitter assembly when the transmitter assembly is coupled to the dock.
In some embodiments, a system for collecting physiological data related to physiological conditions of a patient is disclosed. The physiological data can be collected using a disposable sensor assembly and a reusable transmitter assembly. A patient monitor can be used to display physiological parameters. The system can include a patient monitor, a disposable sensor assembly, and a reusable transmitter assembly. The patient monitor can include a display device. The disposable sensor assembly can include a battery, a sensor element, a housing, and a securement strap. The sensor element can collect physiological data from a patient. The disposable sensor assembly can include a flexible circuit having a plurality of electrical contacts. The securement strap can removably couple the disposable sensor assembly to the patient. The reusable transmitter assembly can include a processor and a wireless transmission module. The reusable transmitter assembly can receive the physiological data from the disposable sensor assembly. The processor can determine physiological parameters based at least in part on the physiological data. The wireless transmission module can establish a wireless communication with the patient monitor and transmit the physiological parameters of the patient to the patient monitor.
The system of the preceding paragraph can include one or more of following features: The patient monitor can include a communication module that can establish wireless communication with the reusable transmitter assembly. The sensor element can include an emitter and a detector. The battery can generate power by reacting with oxygen in the air. The sensor system can include channels and openings. The channels can be formed on a top surface of the housing and the openings can be formed on an inner surface of the channels. The channels and the openings can allow the air to enter into the housing and react with the battery. The reusable transmitter assembly may not include a power source for providing power for the processor and the wireless communication module. The reusable transmitter assembly can receive power from the battery of the disposable sensor assembly. The reusable transmitter assembly can be removably coupled to the dock of the disposable sensor assembly. The reusable transmitter assembly or the disposable sensor assembly can be waterproof or shockproof. The wireless communication module can use at least a first wireless communication protocol to associate the reusable transmitter assembly with the patient monitor. The wireless communication module can use at least a second wireless communication protocol to transmit data between the wireless communication module and the patient monitor. The first wireless communication protocol can be near-field communication (NFC). The second wireless communication protocol can be different from the first wireless communication protocol. The second wireless communication protocol can be Bluetooth®. The association between the reusable transmitter assembly and the patient monitors can be based at least on a pairing signal transmitted from the patient monitor to the reusable transmitter assembly and an identification information transmitted from the reusable transmitter assembly to the patient monitor. The patient monitor can transmit the pairing signal to the reusable transmitter assembly when the reusable transmitter assembly is brought within a predetermined distance from the patient monitor. The identification information can be transmitted from the reusable transmitter assembly to the patient monitor in response of the transmission of the pairing signal from the patient monitor to the reusable transmitter assembly. The transmission of the identification information can occur automatically. The transmission of the identification information may not occur automatically. The identification information can be an RFID unique to the reusable transmitter assembly. The patient monitor can retain the identification information of the reusable transmitter assembly and prevent other patient monitors from establishing wireless communication with the reusable transmitter assembly. The patient monitor can retain the identification information of the reusable transmitter assembly for a predetermined period of time when the wireless communication between the patient monitor and the reusable transmitter assembly is interrupted. The patient monitor can remove the identification information of the reusable transmitter assembly after the predetermined period of time. The patient monitor can reestablish the wireless communication with the reusable transmitter assembly using the identification information in response of the reusable transmitter being within a predetermined distance from the patient monitor. The flexible circuit can be configured to transmit the physiological data from the disposable sensor assembly to the reusable transmitter assembly. The dock can include arcuate supports and the flexible circuit comprises elongate members supported by the arcuate supports. The arcuate supports can push the elongate members of the flexible circuit against the reusable transmitter assembly when the reusable transmitter assembly is coupled to the dock of the disposable sensor assembly. The plurality of electrical contacts of the flexible circuit can come in contact with electrical contacts of the reusable transmitter assembly when the reusable transmitter assembly is coupled with the disposable sensor assembly. The flexible circuit can be in contact with the battery such that the flexible circuit can transmit power from the battery to the reusable transmitter assembly when the reusable transmitter assembly is coupled with the disposable sensor assembly. The patient monitor can be a bedside patient monitor. The patient monitor can be a mobile device. The patient monitor can monitor the strength of wireless signals via the wireless communication between the patient monitor and the reusable transmitter assembly. The patient monitor can generate a notification that the wireless signals is weak when the strength of the wireless signals is below a predetermined signal strength threshold. The patient monitor can monitor a charge level of the battery. The patient monitor can generate a notification that the charge level is low when the charge level of the battery is below a predetermined charge threshold.
For purposes of summarizing the disclosure, certain aspects, advantages, and novel features have been described herein. Of course, it is to be understood that not necessarily all such aspects, advantages, or features will be embodied in any particular embodiment.
Introduction
Wired solution for sensors may be cumbersome and difficult to manage when there are multiple sensors attached to a patient as shown in
Overview
However, the cables 130 can be cumbersome to the patient and prone to tangling. The cables 130 can develop kinks and be damaged over time. In addition, because the sensors 140A, 140B, 140C, 140D are connected to the computing system 106 via the cables 130, location of the computing system 106 can be restricted to the lengths of the cables 130 attached to the sensors 140A, 140B, 140C, 140D. The cables 130 can also restrict patient movements. Therefore, a wireless solution including wireless communication capacity between the sensors and the computing device may resolve some of the concerns of the wired configuration. The wireless configuration can eliminate the need of the cables 130 between the sensors and the computing device and thus provide greater patient mobility.
However, the wireless solutions may have their own limitations. For example, wireless patient monitoring sensors require internal power source (for example, battery), which can have limited capacity due to size of the sensors. In addition, since continuous data collection and wireless transmission can require significant power usage, operation of the sensors can be very limited. Moreover, it may be expensive to replace the entire device when the internal battery is depleted. Furthermore, having a rechargeable battery may not be suitable in a hospital environment where nurses might not have enough time to wait for the battery to recharge. Also, it may not be ideal for a patient to wait for the battery to recharge in time of need. Accordingly, it can be advantageous to provide a sensor system that is compatible with existing sensors and monitors and is capable of wireless communication as discussed herein.
The disposable module 220 can include a dock 222 coupled to a sensor 240 via a cable 230. The dock 222 can be removably connected to the reusable module 250. The reusable module 250 and the computing device 206 can together establish a wireless communication 204 and perform wireless transmission of data between. The reusable module 250 can transmit patient physiological parameters to the computing device 206, where the parameters are calculated from raw physiological data collected by the sensor 240. The transmitted patient data can be raw data collected by the sensor 240.
The reusable module 250 alone or in combination with the dock 222 can perform signal processing on the raw physiological data and transmit the processed physiological data to the computing device 206. The reusable module 250 can establish wireless communication 204 with the computing device 206 to allow data be transmitted between the reusable module 250 and the computing device 206. The reusable module 250 can establish wireless communication 204 with one or more computing devices 206. As shown in
The reusable module 250 can establish wireless communication 204 with portable mobile devices such as mobile phone, smartphone, tablets, and the like. The computing device 206 can be a hospital patient monitoring system, which includes various types of monitors capable of displaying patient health data. The computing device 206 can be a mobile monitoring system or a personal mobile device. The computing device 206 can be Root® Platform, a patient monitoring and connectivity platform available at Masimo Corporation, Irvine, Calif. A mobile physiological parameter monitoring system usable with the cable is described in U.S. Pat. No. 9,436,645, issued on Sep. 6, 2016, titled “MEDICAL MONITORING HUB,” the disclosure of which is hereby incorporated by reference in its entirety.
The cable 230 can be flexible or non-flexible. The cable 230 can be a thin film including electrical circuitries. The cable 230 can be surrounded by different types of electrical insulating material. The cable 230 can be substantially flat or round.
The sensor 240 can be an acoustic sensor, ECG sensor, EEG sensor, SpO2 sensor, or any other types of patient monitoring sensors. The sensor 240 can include one or more emitters and detectors. The emitters can be low-power, high-brightness LEDs (light-emitting diodes) to increase the life of the batteries 224. The sensor 240 can measure raw physiological data responsive to various types of patient physiological parameters including, but not limited to, temperature, blood pressure, blood oxygen saturation, hemoglobin level, electrocardiogram, and the like. The sensor measurements can be used by physicians to determine patient conditions and treatment for the patient. The sensor 240 can transmit the raw physiological data to the dock 222 via the cable 230. The sensor 240 and the dock 222 may form a unitary body such that the dock 222 receives the physiological data directly from the sensor 240 without the cable 230. The dock 222 can be integrated with one or more of the sensors 340.
The sensor 240 can output a raw sensor signal or a conditioned sensor signal. The sensor 240 can include a signal processor that can process the raw or conditioned sensor signal to derive and calculate physiological parameters associated with the raw or conditioned sensor signal.
The sensor 240 can perform mixed analog and digital pre-processing of an analog sensor signal to generate a digital output signal. As discussed above, the sensor 240 can include a signal processor that can perform digital post-processing of the front-end processor output. The input sensor signal and the output conditioned signal may be either analog or digital. The front-end processing may be purely analog or purely digital. The back-end processing may be purely analog or mixed analog or digital.
The sensor 240 can include an encoder, which translates a digital word or serial bit stream, for example, into a baseband signal. The baseband signal can include the symbol stream that drives the transmit signal modulation, and may be a single signal or multiple related signal components. The encoder can include data compression and redundancy.
The sensor 240 can include a signal processor, an encoder, and a controller. The sensor 240 can utilize emitters 242 and the detectors 244 to generate sensor signals, such as a plethysmograph signal. The signal processor then can use the sensor signal to derive a parameter signal that can include a real time measurement of oxygen saturation and pulse rate. The parameter signal may include other parameters, such as measurements of perfusion index and signal quality. The signal processor can be an MS-5 or MS-7 board available from Masimo Corporation, Irvine, Calif. The signal processing step can be performed by the processor 254 of the reusable module 250, as described above.
The dock 222 can be placed on various locations of a patient's body. For example, the dock 222 is placed on the patient's chest. The dock 222 can be placed on other locations on the patient including, but not limited to, torso, back, shoulder, arms, legs, neck, or head. Various means can be used to affix the dock 222 to the patient. For example, the dock 222 is affixed to the patient with an adhesive. In another example, the dock 222 is affixed to the patient with a fastener, such as tape, laid over at least a portion of the dock 222. The dock 222 can be mechanically attachable to at least one strap, which can wrap around the patient.
The reusable module 250 can receive physiological data from the sensor 240 via the dock 222. The reusable module 250 can wirelessly transmit the physiological data to the computing device 206. The reusable module 240 can couple with the dock 222 to establish an electronic communication between the reusable module 250 and the dock 222. The electrical communication between the dock 222 and the reusable module 250 can allow physiological data to be transmitted from the dock 222 to the pairing device 250. The coupling between the reusable module 250 and the dock 222 can be waterproof or shockproof. The disposable module 220 and the reusable module 250 may be shockproof or waterproof. The disposable module 220 and the reusable module 250 can be durable under various types of environments. For example, the reusable module 250 can be fully enclosed, allowing it to be washed, sanitized, and reused.
As shown in
The antenna 252 can be an RFID (radio-frequency identification) antenna. The antenna 252 can be a Bluetooth® antenna. The reusable module 250 can include one or more antennae 252. In some aspects, the reusable module 250 includes a first antenna and a second antenna, where first antenna is a receiving antenna and the second antenna is a transmitting antenna. The first antenna can be a transmitting antenna and the second antenna can be a receiving antenna. Both the first antenna and the second antenna can both receive data from or transmit data to the computing device 206. The first antenna can be a passive antenna while the second antenna can be an active antenna. The first antenna can be an active antenna while the second antenna can be a passive antenna. An active antenna can include a built-in amplifier that can amplify certain spectrum or frequency of signals. The first antenna can establish an RFID or NFC (near field communication) connection with the computing device 206 while the second antenna can establish a Bluetooth® connection with the computing device 206. In another aspect, both the first and the second antenna are capable of establishing RFID and/or Bluetooth® wireless connection. The process of establishing wireless communication 204 with the computing device 206 and wirelessly transmitting the patient physiological data to the computing device 206 will be further described below in detail.
The memory 256 can be computer hardware integrated circuits that store information for immediate use for a computer (for example, the processor 254). The memory 256 can store the patient physiological data received from the sensor 240. The memory 256 can be volatile memory. For example, the memory 256 is a dynamic random access memory (DRAM) or a static random access memory (SRAM). The memory 256 can be a non-volatile memory. For example, the memory 256 is a flash memory, ROM (read-only memory), PROM (programmable read-only memory), EPROM (erasable programmable read-only memory), and/or EEPROM (electrically erasable programmable read-only memory).
The memory 256 of the reusable module 250 can store patient physiological data received from the sensor 240. The memory 256 can store electronic instructions that, when accessed, prompts the processor 254 to receive patient physiological data from the memory 226 of the dock 222, store the data in the memory 256, retrieve the data from the memory 256, transmit the data to the antenna 252, and use the antenna 252 to wirelessly transmit the data to the computing device 206. One or more of the actions discussed above can be performed simultaneously. For example, the processor 254 of the reusable module 250 can receive patient physiological data from the memory 226 of the dock 222 and simultaneously store the data in the memory 256.
The memory 256 can store patient data and health-related events related to a patient when the sensor assembly 202 is no longer in range with or is otherwise unable to communicate with the computing system 206. The memory 256, as noted above, can have sufficient capacity to store patient health data and/or health-related events. The memory 256 can store patient physiological information regardless of whether the reusable module 250 is paired with the computing device 206. Some examples of the health-related events include arrhythmia, low blood pressure, blood oxygen level (SpO2), and the like. Such data and/or health-related events may be accessed via a mobile application on a mobile device (for example, a smartphone, tablet, and the like). Patient data and/or health-related events can be relayed to a device without a display. In such circumstances, the device can have a light source (for example, an LED) that can blink in different colors or patterns to tell the patients or medical personnel something has happened or the data needs to be reviewed. Different rules can be used to determine when or in what situations can patient physiological information be transmitted from the sensor assembly 202 to other external devices (for example, monitoring devices, mobile devices, and the like). In order to maximize the life of the memory 256, the memory 256 may only store health-related event data. For example, this data can be as simple as a time stamp when an event occurred or it can be a snapshot of data taken just before and just after an event. The memory can also store large sections of data. The memory 256 can store up to 96 hours or more of data.
In some aspects, the data stored in the memory 256 can be transmitted to an outside server. The memory 256 can transfer the entire patient physiological information to the outside server or transmit only certain portions of the information. For example, the memory 256 can transmit timestamp information and associated event information to the external server. In another example, the memory 256 can transmit a snapshot of patient physiological information.
The processor 254 can be a chip, an expansion card/board, or a stand-alone device that interfaces with peripheral devices. For example, the processor 254 is a single integrated circuit on a circuit board for the reusable module 250. The processor 254 can be a hardware device or a software program that manages or directs the flow of data.
The processor 254 can communicate with the antenna 252 and the memory 256 of the reusable module 250. For example, the processor 254 communicates with the antenna 252 and the memory 256 of the reusable module 250 to retrieve or receive patient physiological data and to transmit the data to external devices via the antenna 252. The processor 254 can be a Bluetooth® chipset. For example, the processor 254 is a SimpleLink™ Bluetooth® low energy wireless MCU (microcontroller unit) by Texas Instruments Incorporated.
The processor 254 of the reusable module 250 can be connected to the sensor 240 such that it receives patient physiological data from the sensor 240 when the reusable module 250 is mated with the dock 222. The processor 254 can retrieve the patient physiological data from the memory 226 of the dock 222 and transmit the data to the antenna 252. The processor 254 can be operatively connected to the antenna 252 such that the processor 254 can use the antenna 252 to wirelessly transmit the patient physiological parameters to the computing device 206. The patient physiological data transmitted from the reusable module 250 to the computing device 206 can be raw patient physiological data in analog format (for example, 1131001310113100) or patient physiological parameters in a digital format (for example, 60% SpO2).
The sensor 240 can transmit raw or analog patient physiological data to the processor 254 of the reusable module 250. The processor 254 can then perform signal processing on the raw data to calculate patient physiological parameters. It can be advantageous to have the processor 254 to perform signal processing on the raw patient physiological data instead of having the computing device 206 perform signal processing on the raw data. Raw data can comprise strings of binary bits, whereas processed data can comprise digital (not binary) data (for example, 36 degrees Celsius, 72 beats per minute, or 96% blood oxygen level). Therefore transmitting digital data can require less power consumption than transmitting raw data. Thus, by performing signal processing on the raw data using the processor 254 and transmitting the processed data (as opposed to raw data) to the computing device 206, life of the battery 224 can be extended.
The battery 224 of the dock 222 can provide power for the sensor 240. Additionally, the battery 224 can provide power for the reusable module 250. In some aspects, the reusable module 250 may not have an internal power source to transmit patient data to the computing device 206. When the reusable module 250 is mated with the dock 222, the processor 254 of the reusable module 250 can draw power from the battery 224. The processor 254 can use the power from the battery 224 to process patient physiological data from the sensor 240 and to wirelessly transmit the data to the computing device 206. The battery 224 may or may not be rechargeable. The battery 224 can have wireless charging capacity.
The dock 222 and the reusable module 250 can include one or more electrical contacts 228 and electrical contacts 258, respectively. The electrical contacts 228 and 258 can establish electronic communication between the dock 222 and the reusable module 250 when the reusable module 250 is mated with the dock 222. The electrical communication between the electrical contacts 228 and 258 can allow the reusable module 250 to receive power from the battery 224 of the disposable module 220. Additionally and/or alternatively, the electrical connection between the electrical contacts 228 and 258 can allow the reusable module 250 to receive patient physiological data from the memory 226 of the dock 222. The coupling of the reusable module 250 and the dock 222 will be further described below.
Sensor Assembly
The dock 222 can include a strap 308 that is coupled to a bottom portion of the dock 222. The strap 308 can loop around a patient (e.g., a wrist or an arm) to removably attach the dock 222 to the patient (see
The dock 222 can include a cable retainer 306 disposed on a side of the dock 222. The cable retainer 306 can be dimensioned and sized to retain the cable 230. The cable retainer 306 can be removably connected to the dock 222. At least a portion of the cable retainer 306 may be flexible to facilitate insertion of the cable 230 into the cable retainer 306. The cable retainer 306 can advantageously limit movement of the cable 230 to prevent possible tangling of cables of different sensor assemblies. The cable retainer 306 can include a channel to through which the cable 230 can extend. The channel of the cable retainer 306 can be dimensioned such that the cable 230 is snug within the channel, thereby limiting movement of the cable 230.
The retainer 304 of the dock 222 can include a protrusion 324 that can interact with a groove 322 of the reusable module 250. The interaction between the groove 322 and the protrusion 324 can maintaining coupling between the reusable module 250 and the dock 222. For example, when the reusable module 250 is inserted into the dock 222, the retainer 304 is pushed in a direction away from the housing 300 of the dock 222 in order to allow the reusable module 250 to mate with the dock 222. When the reusable module 250 is fully inserted into the dock 222, the retainer 304 can snap back to its original position to engage the groove 322 of the reusable module 250. The retainer 304 and the groove 322 can together prevent vertical displacement of the reusable module 250.
The retainer 304 can have a first position and a second position. When in the first position, the retainer 304 is substantially vertical with respect to the dock 222. When in the second position, the retainer 304 is pushed in a direction away from the housing 300 so that the retainer 304 forms an angle greater than 90 degrees with respect to the dock 222. Before the reusable module 250 is inserted into the dock 222, the retainer 304 can be in the first position. While the reusable module 250 is being pushed into the dock 220, the reusable module 250 interacts with the retainer 304 and causes the retainer 304 to be in the second position. When the reusable module 250 is fully engaged with the dock 222, the retainer 304 reverts to the first position so that the protrusion 324 engages the groove 322.
The dock 222 can also include a flex circuit 320 and a cover 318 to retain the flex circuit 320. The flex circuit 320 can include the electrical contacts 228 of the dock 222, where the flex circuit 320 serves as a connection between the cable 230 and the electrical contact 228. Therefore any information or data transmitted from the sensor 240 via the cable 230 to the dock 222 can be transmitted to the electrical contacts 228 via the flex circuit 320. Additional details of the flex circuit 320 will be provided below.
The housing 300 of the dock 222 can include one or more slots 328 that can interact with one or more legs 326 of the reusable module 250. The slots 328 can be dimensioned and shaped to allow the legs 326 of the reusable module 250 to slide into the slots 328. The legs 326 can slide into the slots 328 to assist in maintaining connection between the reusable module 250 and the dock 222. Once the legs 326 are inserted into the slots 328, the legs 326 can prevent vertical displacement of the reusable module 250.
It can be advantageous to have the battery 224 in a disposable portion such as the dock 222 or the sensor 240. Establishing wireless communication 204 and performing wireless transmission requires a significant amount of power. If the reusable module 250 has an internal power source, its functionalities (for example, establishing wireless communication 204 and performing wireless transmission) can be limited by the capacity of the internal power source. In such configuration, the reusable module 250 needs to be replaced once its internal power source is depleted. In a wireless patient monitoring context, it is desirable to keep the same pairing device for each patient because having to use multiple pairing devices for the same patient often can lead to confusion and can create a need to reestablish connections between pairing devices and display devices. When the reusable module 250 has an external power source such as battery 224 of the dock 222, it does not need to be replaced when the battery 224 is depleted.
The batteries 224 can be zinc-air batteries powered by oxidizing zinc with oxygen in the air. It can be advantageous to use zinc-air batteries because they have higher energy density and thus have greater capacity than other types of batteries for a given weight or volume. In addition, zinc-air batteries have a long shelf life if properly sealed to keep the air out. The housing 300 can include one or more openings 332 that allow air to enter and react with the batteries 224. The one or more openings 332 can be sealed prior to use to prevent the air from entering and reacting with the batteries 224, thereby reducing capacity of the batteries 224. Once ready to use, the seal placed on the one or more openings 332 may be removed to allow the batteries 224 to provide power for the reusable module 250. The housing 300 may include a gasket 330 to seal the batteries 224 from the air. The gasket 330 can further increase the capacity of the batteries 224.
Having a disposable element (for example, the disposable module 220) as a power source for the reusable module 250 can address the above issues by eliminating the need to replace the reusable module 250. In this configuration, only the dock 222 or the sensor 240 needs to be replaced when the battery 224 is depleted. Since the cost of replacing the dock 222 or the sensor 240 can be much less than the cost of replacing the reusable module 250, this configuration can be advantageous in reducing operation costs. The sensor 240 may include the battery 224 that provides power to the reusable module 250. Both the sensor 240 and the dock 222 can include the battery 224. The reusable module 250 can include a battery consumption priority setting such that the reusable module 250 receives power first from the sensor 240 then from the dock 222.
The dock 222 can include a battery circuit 314 in contact with the batteries 224. The battery circuit 314 can be in contact with the flexible circuit 320. When the reusable module 250 is mated with the dock 222, the electronic contacts 258 can be in contact with the electronic contacts 228 of the flexible circuit 320 to allow the reusable module 250 to receive power from the batteries 224 via the flexible circuit 320.
The dock 222 can include an opening 362 and one or more supports 360. The one or more supports 360 can be formed on a side of the opening 362 and extend over a substantial portion of the opening 362. The supports 360 can be arcuate. The supports 360 can extend over the length of the opening 362. The cover 318 for the flexible circuit 320 can be placed over the opening 362 to hold the flexible circuit 320 over the opening 362.
The dock 222 can include a slot dimensioned to retain the reusable module 250 during the use of the sensor assembly 202. The reusable module 250 can be disposed between the housing 300 and the retainer 304. The slot of the dock 222 can include one or more arcuate surfaces or one or more angular corners. The slot of the dock 222 may be substantially rectangular or circular in shape. The slot can have substantially the same size, shape, and/or dimensions as that of the reusable module 250.
The reusable module 250 can include one or more electrical contacts 258. The electrical contacts 258 can be located on a bottom surface of the reusable module 250. The electrical contacts 258 can be substantially rectangular or circular in shape. The electrical contacts 258 can establish contact with electrical contacts 228 of the dock 222 when the reusable module 250 is mated with the dock 222. The contact between the electrical contacts 228 and electrical contacts 258 can allow information or data be transmitted between the reusable module 250 and the dock 222 of the disposable module 220.
As disclosed herein, the batteries 224 can be zinc-air batteries powered by oxidizing zinc with oxygen in the air. The openings 332 formed on the housing 300 can allow the air to enter through and react with the battery 224. The battery 224 then provides power for the disposable module 220 and the reusable module 250. However, the openings 332 may sometimes be covered by blankets, clothes, and the like, which can prevent the air from entering through the openings 332 and react with the battery 224. Consequently, power supply for the disposable module 220 and the reusable module 250 can be interrupted if the openings 332 are covered.
As shown in
The number, dimensions, orientation, or positions of the channels 331 may be varied depending on the size of the housing 300 of the reusable module 250. The channels 331 can be oriented such that they together form a shape on the housing 300. The channels 331 may be oriented in a triangular shape (as shown in
The sensor assembly 202A can include a sensor 240A. The sensor 240A can be an O3 sensor that can be adhered to a forehead of a patient. The sensor assembly 202A can include a cable 230A that couples the sensor 240A and a dock 222A of the disposable module 220A. The cable 230A can be flat or round. As discussed above, the sensor 240A can include one or more batteries that can provide power for a reusable module 250A. The mating of the dock 222A and the reusable module 250A can facilitate electronic communication therebetween. The dock 222A can include a housing 300A that includes a retainer member 304A. Pressing down the retainer member 304A can allow the reusable module 250A to be coupled with or removed from the dock 222A.
The sensor assembly 202B can include a sensor 240B. The sensor 240B can be a RAM sensor adhered to a neck of a patient. The sensor 240B can be an ECG sensor that can be adhered to a chest or abdominal area of a patient. The dock 222B can include a housing 300B and a retainer member 304B. The housing 300B can include one or more extensions 500 that can extend from the body of the housing 300B towards the retainer member 304B. The reusable module 250B can include cutouts that correspond to the one or more extensions 500. When the reusable module 250B is coupled with the dock 222B, the extensions 500 can extend over the cutouts of the reusable module 250B, preventing the reusable module 250B from being dislodged from the dock 222B.
Flexible Circuit
As shown in
The number of the elongate members 600 can correspond to the number of electrical contacts 258 of the reusable module 250 (see
Each the elongate members 600 of the flex circuit 320 can include an arcuate portion with a first curvature. The arcuate portions of the elongate members 600 can be laid over the opening 362 of the dock 222. The one or more electrical contacts 228 of the flex circuit 320 can be disposed over a portion of the elongate members 600 of the flex circuit 320. For example, the one or more electrical contacts 228 are located at an apex of each of the elongate members 600 of the flex circuit 320. In another example, the entire upper surface of each of the elongate members 600 defines the electrical contacts 228. The elongate members 600 of the flex circuit 320 can be configured such that the apex of the arcuate portions of the elongate members 600 of the flex circuit 320 are located at a predetermined distance away from the opening 362 of the dock 222. The apex of the elongate members 600 of the flex circuit 320 can point away from the opening 362 of the dock 222 such that the arcuate portions of the elongate members 600 define a concave surface facing the opening of the dock 222. The apex of the elongate members 600 can be arcuate in shape or substantially flat.
It can be advantageous to have the elongate members 600 of the flex circuit 320 include a curved portion upward and away (for example, concave downward) from the opening 362 of the dock 222. Such configuration can allow the elongate members 600 to act as springs providing reactive upward forces when pressed downward by the reusable module 250. Such upward forces provided by the elongate members 600 can allow the electrical contacts 228, 258 of the dock 222 and the reusable module 250, respectively, to maintain adequate contact between them.
The elongate members 600 of the flex circuit 320 can have different curvatures. For example, a first elongate member of the flex circuit 320 has a first curvature while a second elongate member of the flex circuit 320 has a second curvature. The first curvature of the first elongate member and the second curvature of the second elongate member can be the same or different. The first curvature of the first elongate member is greater than, less than, or equal to the second curvature of the second elongate member.
The elongate members 600 of the flex circuit 320, in their resting positions, may not have any arcuate portions. The elongate members 600 of the flex circuit 320 can be substantially linear prior to being installed on the dock 222. The elongate members 600, can be linear or curved. The elongate members 600 of the flex circuit 320 can include more than one linear portions.
The elongate members 600 of the flex circuit 320 can be flexible or not flexible. The flex circuit 320 can be laid on the dock 222 such that the elongate members 600 are laid over one or more supports 360 of the dock 222. The elongate members 600 can extend distally away from the body 608 of the flex circuit 320. The flex circuit 320 can include more than one elongate members 600. The flex circuit 320 can include one or more elongate members 600 that are flexible. Some the elongate members 600 may be flexible while other elongate members 600 are not.
As discussed above, the dock 222 can include the opening 362 over which the elongate members 600 of the flex circuit 320 can extend over. The dock 222 can include one or more supports 360 dimensioned and shaped to support the elongate members 600 of the flex circuit 320. When the flex circuit 320 is installed on the dock 222, the supports 360 can provide a surface on which the elongate members 600 of the flex circuit 320 can be placed on.
The supports 360 of the dock 222 can be curved and define the curvature of the arcuate portions of the elongate members 600. The supports 360 can be arcuate. It can be advantageous to have the supports that correspond to each of the elongate members 600 of the flex circuit 320. For example, the dock 222 has six independent supports 360 associated with each of the six elongate members 600 of the flex circuit 320. Such configuration allows each of the corresponding elongate members 600 and the supports 360 of the dock 222 to move independently from other elongate members 600 and supports 360 as opposed to all of the elongate members 600 and the supports 360 moving that the same time. Such configuration can make inserting the reusable module 250 into the slot 940 of the dock 222 easier. Moreover, this can allow interoperability between the dock 222 and the reusable module 250 that have different height configurations for the electrical contacts 258.
It can be advantageous to have the supports 360 for the flex circuit 320 include a curved portion upward and away (e.g., concave downward) from a bottom portion of the dock 222. Such configuration can allow the supports to act as springs providing reactive upward force when pressed downward by the reusable module 250. Such upward forces can allow the electrical contacts 228, 258 of the dock 222 and the reusable module 250, respectively, to maintain adequate contact between them. The supports 360 can include a first upward portion that is concave upward, a second upward portion that is concave downward, and a third downward portion that is concave downward. The supports 360 may include a first upward portion that is concave upward and a second upward portion that is concave downward. The supports 360 can include one or more inflection point, defined as a point where the supports 360 changes from being concave to convex, or vice versa. The supports 360 can also include one or more linear portions.
The supports 360 may also provide sufficient force to push the reusable module 250 away the dock 222 when the retainer member 304 is pulled away from the reusable module 250. The support 360 may push the reusable module 250 away from the dock 222 when the retainer member 304 is in its second position, as discussed above. When the retainer 304 no longer engages the groove 322 of the reusable module 250, it may no longer provide force to counteract the force generated by the supports 360, allowing the supports 360 to push the reusable module 250 away from the dock 222.
The supports 360 can have a length that is greater than, less than, or equal to the length of the elongate members 600 of the flex circuit 320. The supports 360 have a width that is greater than, less than, or equal to the width of the elongate members 600. The supports 360 can have a thickness that is greater than, less than, or equal to the thickness of the elongate members 600 to allow the supports 360 to provide sufficient mechanical support and to withstand the downward force exerted on the elongate members 600 and the supports 360 by the reusable module 250. The interaction between the elongate members 600, supports 360, and the reusable module 250 will be further described below.
The supports 360 can be made out of the same or different material as the dock 222.
The body 608 of the flex circuit 320 can be laid under the housing 300 of the dock 222. The body 608 can be connected to the cable 230 connected to the dock 222 such that the flex circuit 320 allows the health monitoring data from sensor 240 to be transmitted to the electrical contacts 606 of the flex circuit 320.
The downward force F in a first direction can cause the supports 360 of the dock 222 to provide a reactive force in a second direction. The second direction of the reactive force can be an opposite direction then the first direction of the downward force F. Specifically, the reactive force by the supports 360 can be upward away from the dock 222. The supports 360 can act as a spring such that as the supports 360 moves further downward from its natural position (for example, as H1 changes to H2), the magnitude of the reactive force increases. The directions of F and the reactive force may be opposite from each other. The magnitude of the reactive force is less than the downward force F in order to allow the supports 360 to move downward and allow the reusable module 250 to be inserted into the slot 940 of the dock 222. The magnitude of the downward force F caused by the reusable module 250 may correlate to the following: the change in the relative height difference between the apex of the elongate members 600 and the body 608 (for example, from H1 to H2) and the change in the positions of the tips 602 (for example, from L1 to L2).
The elongate members 600 of the flex circuit 320 can have a first degree of curvature before the reusable module 250 is inserted into the dock 222. The elongate members 600 can have a second degree of curvature after the reusable module is inserted into the dock 222. The first degree of curvature of the elongate members 600 can be greater than, less than, or equal to the second degree of curvature. The first degree of curvature can correspond to a first position of the tips 602 (for example, L1). The second degree of curvature can correspond to a second position of the tips 602 (for example, L2). Moreover, the first degree of curvature can correspond to a first position of the apex (for example, H1) of the elongate members 600. The second degree of curvature can correspond to a second position of the apex (for example, H2) of the elongate members 600.
The reactive force provided by the supports 360 can maintain sufficient contact between the electrical contacts 310a of the dock 222 and the electrical contacts 310b of the reusable module 250 to allow electrical signals be transmitted between the contacts.
Attachment Mechanisms
With reference to
A distal end of the first strap 700 can be inserted into one of the openings 704 of the second strap 702. The fastener 706 of the first strap 700 may be inserted into one of the openings 704 of the second strap 702. The interaction between the fastener 706 and openings 704 can removably affix the dock 222 as shown in
Dongle and Pairing
Given the time demands placed on clinicians in busy hospitals and the number of patients and patient monitoring devices, manual interaction to establish connection between the computing device 206 (for example, a mobile patient monitoring display device) and the reusable module 250 can be burdensome. In some cases, the time required to manually interact with a patient monitor device in order to establish connection with a pairing device can even jeopardize a patient's well-being in particularly urgent circumstances. For at least the foregoing reasons, it would be advantageous for the computing device 206, such as bedside patient monitors, central monitoring stations, and other devices, to have the capability to detect the presence of the reusable module 250 nearby and establish a wireless communication 204 with the reusable module 250.
When the dongle 800 is connected to the computing device 206 via the connector 804, the computing device 206 can automatically detect the connector 804. The computing device 206 can determine a type of connector 804 and automatically change its settings. The settings may include, but not limited to, display settings for the display 208, display setting for the computing device 206 (for example, color of lights used to denote pair or communication status), communication protocol settings (for example, type of wireless communication utilized), communication signal settings (for example, varying communication signal type or strength based on different types of communications), and the like. Additionally, the settings for the dongle 800 can change to accommodate different types of computing devices 206 and their displays 208. Such setting can include display settings (for example, colors or messages denoting communication/pairing status), communication signal settings (for example, frequency of wireless signal used), communication protocol settings (for example, types of wireless communication used), and the like.
The computing device 206 can receive processed physiological parameter data and display on a display screen. This feature can be advantageous because it can reduce the amount of processing power required by the computing device 206. As discussed above, the reusable module 250 can perform signal processing on raw patient physiological data collected by the sensor 240 and calculate patient physiological parameters. Therefore, the data transmitted from the reusable module 250 to the computing device 206 via the body 802 includes patient physiological parameters that do not require further signal processing.
The reusable module 250 can transmit patient physiological parameters with low resolution and the dongle 800 can fill in the data using various methods. For example, the dongle 800 may use different types of averages to fill in the data transmitted from the reusable module 250. The reusable module 250 can send waveform data, for example, at a low resolution and the dongle 800 can increase the resolution of the waveform. This feature can further increase the life of the battery 224 of the disposable module 220.
The body 802 of the dongle 800 can include a transceiver or receiver, and a communication module for communicatively coupling the computing device 206 to other patient monitoring devices such as the reusable module 250. When the reusable module 250 is sufficiently proximate, the body 802 can communicate with the reusable module 250 so as to identify the reusable module 250. The body 802 can include a radio-frequency identification (RFID) reader and while the reusable module 250 can include an embedded RFID chip containing an identifying information unique to the reusable module 250. The RFID reader of the body 802 can identify the embedded RFID chip inside the reusable module 250 and establish a wireless communication 204 between the reusable module 250 and the body 802. The body 802 can include a transceiver that complies with one or more short-range wireless communications standards, such as Bluetooth®. Other types of wireless communication protocols may be utilized to establish communication and transfer data between the dongle 800 and the reusable module 250.
The body 802 can include a groove 808 dimensioned to receive a portion of the reusable module 250. The groove 808 can indicate a medical personnel where to place the reusable module 250 in order to associate (for example, pair) the reusable module 250 with the computing device 206.
The dongle 800 can include a holder 850 that can retain the reusable module 250 when not in use. The holder 850 can be separate from the dongle 800 as shown in
When the reusable module 250 is brought sufficiently close to the body 802 of the dongle 800, the body 802 can, for example, use RFID technology to receive from the reusable module 250 information that can identify the reusable module 250 to the computing device 206. The identifying information can be an ID tag of a token specific or unique to the reusable module 250. The identifying information can include Bluetooth® parameters of the reusable module 250. Other types of identification mechanisms can be used to allow the computing device 206 to identify and associate with the reusable module 250.
The identifying information of the reusable module 250 can be stored in the memory 256. The identifying information may be hardwired into the memory 256 or programmable. The identifying information can include pairing parameters (for example, a pairing device ID) that is unique to the reusable module 250. The identifying information may be unique to the patient to whom the reusable module is assigned. The identifying information of the reusable module 250 may also include other information such as, for example, the pairing device's information, information regarding the sensor 240 the reusable module 250 is operatively connected to, or a code or other indicator for initiating a predetermined action to be performed by the computing device 206. Additionally and/or alternatively, the identifying information of the reusable module 250 can be generated using physiological data collected by the sensors 240 of the sensor assembly 202.
The body 802 of the dongle 800 can include a RFID reader. The RFID reader can communicatively couple the computing device 206 to other patient monitoring devices such as the reusable module 250. When the reusable module 250 is proximate to the body 802, as shown in
The computing device 206 can use the identifying information to associate the reusable module 250 with the computing device 206. For example, the Bluetooth® parameters of the reusable module 250 can be used to associate the reusable module with the computing device 206. Once associated, the reusable module 250 can connect with the computing device 206 using the pairing parameters (for example, Bluetooth® parameters) included in the identifying information. The computing device 206 can identify the reusable module 250 and allow wireless communication 204 with the reusable module 250 using the Bluetooth® parameters it received from the reusable module 250. After establishing connection with the computing device 206, the reusable module 250 can communicate with the dongle 800 and the computing device 206 via Bluetooth® transmission. Other types or standards of wireless communication can be used, including, for example, ultrasound, Near Field Communication (NFC), and the like. If multiple reusable modules 250 are proximate to the computing device 206, a priority scheme or a user acknowledgment may be used to determine which reusable modules 250 are accommodated.
The reusable module 250 can use the NFC to provide instructions to program the dongle 800 to take certain actions in certain situations. The NFC communication circuitry of the reusable module 250 can have an associated memory that can have read/write capabilities. For example, the reusable module 250 can use NFC to indicate how long the dongle 206 must wait before deleting the pairing parameters (“giving up”). In another example, the reusable module 250 can use the NFC to indicate when the dongle 800 is disallowed from deleting the pairing parameters (“not giving up”). The NFC can be used to allow the dongle 800 to associate with one or more reusable modules 250 at the same time.
The dongle 800 can use the NFC to receive various types of information from the reusable module 250. The dongle 800 can receive information associated with NFC components of the reusable module 250 and determine sensor types, patient types, patient information, physician information, hospital information, authorized uses, authorized supplies, authorized manufacturers, emitter wavelengths, or indications of the usage or life of the reusable module 250, parameters the reusable module 250 is capable of measuring, and the like. For example, the dongle 800 can receive information via the NFC to determine that a particular reusable module 250 is designed to work with sensor assembly 202. The dongle 800 can also write back using NFC. For example, the dongle 800 can provide programming information through NFC to the reusable module 250. The dongle 800 can also write sensor usage information to the reusable module 250. For example, the reusable module 250 may only be allowed to be used a certain number of times before it must be discarded in order to maintain quality. This information can be written to the reusable module 250 through NFC communication.
Throughout the present disclosure, it is to be understood that the dongle 800 may be incorporated directly into the computing device 206. For example, the dongle 800 can be built into the circuitry of the computing device 206 such that the dongle 800 and the computing device 206 are in the same housing. In another example, the dongle 800 and the computing device 206 are in the same housing but the dongle 800 is not built into the circuitry of the computing device 206. The dongle 800 can be incorporated into the computing device 206 such that the dongle 800 is located near an outer housing or body of the computing device 206. Such a configuration can allow the reusable module 250 to readily establish wireless communication 204 with the dongle 800. The dongle 800 incorporated directly into the computing device 206 can prevent possible connection issues between the dongle 800 and the computing device 206.
Once the computing device 206 is associated with the reusable module 250, it can transmit a signal to the reusable module 250 indicating that the reusable module 250 is associated with the computing device 206. Different types of notifications can be generated when the reusable module 250 has successfully established wireless communication 204 with the computing device 206. The notifications can be generated by the computing device 206, the reusable module 250, or both.
The computing device 206 can provide an auditory notification or a visual notification on the display 208. For example, the computing device 206 can play a pattern of beeps or a predetermined melody for successful pairing. In another example, the computing device can play an auditory message such as “SpO2 sensor number 1234 has been successfully paired with patient monitoring device A123.” Visual notifications can include a blinking LED on the display 208. Another example of a visual notification can be in a form of text such as “Pairing successful” displayed on the display 208. The reusable module 250 has one or more LEDs to indicate status of wireless communication 204 with the computing device 206. For example, the reusable module 250 can include a red LED to indicate that no wireless communication 204 has been established between the reusable module 250 and the computing device 206. In another example, the reusable module 250 can include a blue LED to indicate that the reusable module 250 has established the wireless communication 204 with the computing device 206. A blinking green LED may be used to indicate that the computing device 206 is waiting for the reusable module 250 to establish the wireless communication 204 with the computing device 206. Different color LEDs and different schemes can be used to indicate different status of wireless communication 204 between the reusable module 250 and the computing device 206.
After receiving the pairing parameters from the reusable module 250, the computing device 206 can wait for a predetermined time period for the reusable module 250 to establish the wireless communication 204 (for example, Bluetooth® connection). If the wireless communication 204 is not established within the predetermined time period, the pairing parameters can expire, requiring the reusable module 250 to retransmit the pairing parameters to the computing device 206 again. The predetermined time period can be modified.
Once the computing device 206 receives the pairing parameters from the reusable module 250, the reusable module 250 can be mated with the dock 222, as shown in
The computing device 206 can receive the patient data including patient physiological parameters from the reusable module 250 and display the parameters on the display 208. The computing device 206 can receive the patient data via the body 802 of the dongle 800. In other words, the body 802 of the dongle 800 can receive patient physiological parameters from the reusable module 250 and in turn transmit the parameters to the computing device 206. As discussed above, Bluetooth® can be used to transmit the patient data between the reusable module 250 and the computing device 206 (or the body 802). For example, the reusable module 250 operatively connected to a SpO2 sensor can establish Bluetooth® communication with the computing device 206. The computing device 206 can receive the patient data including SpO2 parameters from the reusable module 250 and display the parameters on the display 208. In another example, the reusable module 250 operatively connected to a temperature sensor can establish Bluetooth® communication with the computing device 206. The computing device 206 can receive the patient data including temperature parameters from the reusable module 250 and display the parameters on the display 208. The computing device 206 can receive one or more parameters from the reusable modules 250 and display the one or more parameters on the display 208.
The reusable module 250 can include an ID tag that is active or passive RFID tag. An active RFID tag may be WiFi-enabled, for example. The ID tag can be a barcode (e.g., two-dimensional or three-dimensional) or a WiFi-enabled RFID tag. By communicating with the WiFi access points, the computing device 206 can triangulate its position relative to that WiFi access points. Likewise, the position of the reusable module 250 (and the sensor 240 if the reusable module 250 is operatively connected to the sensor 240) can be triangulated. Thus, the distributed WiFi access points can be used by, for example, the computing device 206 to determine the approximate position of the reusable module 250 (and/or the sensor 240) with respect to the computing device 206. The computing device 206 may also communicate directly with the reusable module 250 in order to, for example, enhance the position approximation determined using the distributed WiFi access points.
Positions of one or more reusable modules 250 can be used to determine relative or absolute positions of the one or more reusable modules 250. For example, consider reusable modules 250A, 250B, 250C, and 250D. When locations of the reusable modules 250A, 250B, and 250C are known, their positional information can be used to determine a position of the reusable module 250D.
The presence or proximity of the reusable module 250 to the computing device 206 may be determined by the reusable module 250 including an RFID tag. An “RFID tag” or simply “tag” can include any wireless communication device and/or communication standard (e.g., RFID, NFC, Bluetooth, ultrasound, infrared, and the like) that can remotely identify a proximate user to a monitor. Tags include, but are not limited to, devices in the form of badges, tags, clip-ons, bracelets or pens that house an RFID chip or other wireless communication components. Tags also encompass smart phones, PDAs, pocket PCs and other mobile computing devices having wireless communications capability. The RFID tag can include identifying information or pairing parameters for the reusable module 250.
The computing device 206 may respond to the departure of all proximate reusable modules 250 by automatically removing displays associated with the reusable modules 250. This feature can provide display patient physiological data only for sensors 240 associated with reusable modules 250 proximate to the computing device 206. The computing device 206 may respond in a similar manner by automatically silencing pulse “beeps” or other non-critical sounds when there are no proximate reusable modules 250 and associated sensors 240.
The computing device 206 can generate alarms when its wireless communication 204 with the reusable module 250 is disrupted or no longer exists. For example, the computing device 206 can create at least one of auditory and visual alarm when the reusable module 250 is no longer mated with the disposable sensor 220.
The computing device 206 can monitor signal strength of the wireless communication 204 between the computing device 206 and the reusable module 250. Under some circumstances, the reusable module 250 may move out of the range of the computing device 206 which may cause the wireless communication 204 to be disrupted. For example, a patient equipped with the reusable module 250 may visit an x-ray room for a routine visit and disrupt the wireless communication 204 between the reusable module 250 and the computing device 206. If the same reusable module 250 becomes available within the range within a period of time, the computing device 206 can automatically reestablish the wireless communication 204. For example, if the patent returns from the x-ray room within 30 minutes, the computing device 206 may be able to reestablish the wireless communication between the reusable module 250 and the computing device 206. Upon reestablishing communications, any information stored on the reusable module 250 for the time period where communication was disrupted can be downloaded to the computing device 206.
The computing device 206 can be configured to not lose (or delete) the pairing parameters received from the reusable dongle 250. This feature can prevent other reusable modules 250 from pairing with the computing device 206 even when the reusable module 250 is no longer wirelessly communicating with the computing device 206. For example, a first computing device 206 and a first reusable module 250 are in a first wireless communication 204. The first computing device 206 can be configured to not “give up” or “give up” the first reusable module 250 even after the first wireless communication 204 is terminated. When configured to “give up,” a second reusable module 250 can be paired with the first computing device 206. When configured to “not give up,” a second reusable module 250 cannot be paired with the first computing device 206.
This feature can also apply in situations in which the battery 224 of the disposable module 220 is about to be depleted or when the reusable module 250 is removed from the disposable module 220. Without power from the battery 224, the reusable module 250 cannot maintain the wireless communication 204 with the computing device 206. The computing device 206 can be configured to prevent or not prevent other computing device 206 from establishing wireless communication 204 with the reusable module 250. The reusable module 250 can also send a “dying” signal to the computing device 206 providing instructions on pairing or other instructions as the device is removed from the disposable module 220 or when the batteries are depleted. This dying instruction allows the pairing to be maintained.
Computing devices 206 (or dongle 800) can communicate to other computing devices 206 (or other dongles 800) to ensure that each computing device 206 (or dongle 800) is paired to a single reusable module 250 at any time. For example, when a first reusable module 250 is paired (or associated) with a first computing device 206, a second reusable module 250 may not be paired (or associated) with the first computing device 206. However, the first reusable module 250 may be able to pair with a second computing device 206. Pairing the first reusable module 250 with the second computing device 206 can cause the second computing device 206 to inform the first computing device 206 to release its pairing with the first reusable module 250.
The computing device 206 can identify the sensors 240 and the reusable modules 250 associated with the computing device 206. When one or more sensors 240 and reusable modules 250 are wirelessly associated to the computing device 206, it may be advantageous for the computing device 206 to distinguish and indicate different physiological parameters from different sensors 240 or reusable devices 250. For example, the computing device 206 can be associated with two different sensors 240 (and their respective reusable modules 250) for detecting peripheral capillary oxygen saturation (SpO2) and acoustic respiration rate (RRa). The computing device 206 can display information pertaining to the sensors 240 or the reusable modules 250 (for example, sensor name, sensor type, sensor location, sensor ID, reusable module ID, reusable module name) to distinguish patient parameters from different sensors and/or reusable modules.
The reusable module 250 of the sensor assembly 202 can establish wireless communication 204 with mobile devices such as smartphones, tablets, smartwatches, laptops, and the like. The mobile devices can include a mobile application that allows the mobile devices to establish wireless communication 204 with the reusable module 250 of the sensor assembly 202, receive patient physiological parameters from the reusable module 250, and display the patient physiological parameters. In addition to the patient physiological parameters, the mobile application can also display other patient information including, but not limited to, name, age, past medical history, current medications, address, gender, and the like.
The wireless communication 204 between the mobile devices and the reusable module 250 can be in a form of Bluetooth®. The wireless communication 204 between the mobile devices and the reusable module 250 can be established via the Internet. For example, the computing device 206 can be connected to the Internet or a secured network server. Once wireless communication 204 between the reusable module 250 and the computing device 206 is established, the mobile devices can access the Internet or the secure network server to receive and display the patient physiological parameters via the mobile application described above.
The mobile application can include various security measures to prevent third-parties from accessing patient information. The mobile application can be associated with certain mobile devices that has been identified by a healthcare provider. Identification and a passcode may be required for using the application to connect to the reusable module 250 (or the computing device 206), receive patient data (for example, patient data and/or patient physiological parameters), and display patient data. Each of the mobile applications can be associated with a unique access code or an identification code that may be required for receiving patient data from the Internet or the secured network server. The unique access code or the identification code can be associated with the mobile device or the mobile application. The unique access code can be a media access control (MAC) address associated with each of the mobile devices.
Mating of the Dock and Reusable Module
Methods of Pairing, Collecting Data, and Transmitting Data to Computing Device
At block 1102, a patient monitor (for example, the computing device 206) can generate and transmit a pairing signal. Generating the transmitting the pairing signal can be done automatically or manually. The pairing signal may be a radio signal. The pairing signal can be configured such that a nearby device, upon receiving the signal, is triggered to transmit an identification information in response. The nearby device may be the reusable module 250. The pairing signal can also contain sufficient power to enable nearby devices to transmit pairing parameters in response to the pairing signal.
Generating and transmitting the pairing signal can be done by different devices. The computing device 206 can generate the pairing signal while the dongle 800 attached to the computing device 206 via the connector 804 can transmit the pairing signal. The dongle 800 can generate and transmit the pairing signal for the computing device 206.
The reusable module 250 located within a predetermined distance from the computing device 206 can receive the pairing signal. This can be advantageous in hospital environments where many patients can be placed within a short distance from an electronic device such as the computing device 206. Such configuration can allow the electronic device (for example, the computing device 206) to receive patient health data only from a patient who is nearby and prevent the electronic device from receiving patient health data from other patients who may not be a patient-in-interest. Strength of the pairing signal can be varied to allow the signal to travel further or closer.
At block 1104, the reusable module 250 can receive power from the pairing signal generated by the computing device 206. The pairing signal can be a high-frequency alternating current which can be used to create a voltage potential. The pairing signal of the computing device 206 may be received when the reusable module 250 is within a predetermined distance. As discussed above, physical contact between the computing device 206 (or the dongle 800) and the reusable module 250 may be required for the reusable module 250 to receive the power from the pairing signal. The reusable module 250 can automatically receive power from the pairing signal. By receiving power from the pairing signal, the antenna 252 of the reusable module may not need to draw power from the battery 226 of the disposable device 220.
At block 1106, the reusable module 250 can use the power received from the pairing signal to transmit identification information to the computing device 206. The identification information can include pairing parameters of the reusable module 250. The identification information may be a tag serial number unique to the reusable module 250. The identification information can include, but not limited to, stock number, lot number, batch number, production date, or other specific information. The computing device 206 can use the identification information to uniquely identify the reusable module 206. The transmission of the identification information can occur automatically.
The reusable module 250 can include a feature that prevents automatic transmission of the identification information to the computing device 206. This feature can be advantageous to prevent inadvertent pairing of the reusable module 205 with the computing device 206. Medical personnel can deal with patients in need of many different types of sensors. In such circumstances, reusable modules 250 may inadvertently be brought proximal to the computing device 206 (or dongle 800). Thus it can be advantageous for the reusable module 250 to have the feature to prevent the reusable modules 250 from automatically pairing with the computing device 206 (or dongle 800) to prevent inadvertent pairing.
At block 1108, the computing device 206 can receive the identification information from the reusable module 250. The dongle 800 connected to the computing device 206 can receive the identification information and relay it to the computing device 206. At block 1110, the computing device 206 can associate with the reusable module 250, which allows the wireless communication 204 to be established between the reusable module 250 and the computing device 206.
The association between the computing device 206 and the reusable module 250 can occur automatically. On the other hand, the association can require a user input via the computing device 206. For example, upon receiving the pairing parameters from the reusable module 250, the computing device 206 can generate a notification prompting a user to allow or disallow the computing device 206 to associate with the reusable module 250. If allowed, the computing device 206 can associate with the reusable module 250 and the reusable module 250 can establish a wireless communication 204 with the computing device 206. If not allowed, the computing device 206 may not associate with the reusable module 250 and the reusable module 250 may not establish a wireless communication 204 with the computing device 206.
Establishing wireless communication 204 can require the reusable module 250 to have an external power source. The battery 224 provides sufficient power for the reusable module 250 to receive raw patient physiological data from the sensor 240 and perform signal processing on the raw data to calculate patient physiological parameters. Moreover, the reusable module 250 can use the power from the battery 224 to use the antenna 252 to wirelessly transmit the calculated parameters to the computing device 206. Without the battery 224 connected to the dock 222, the reusable module 250 cannot receive power via the electrical contacts 228, 258.
At block 1112, the reusable module 250 can mate with the dock 222 and receives power from the battery 224 via the battery circuit 314 and the electrical contacts 228, 258. At block 1114, the reusable module 250 can establish wireless communication 204 with the computing device 206. The wireless communication 204 can be established using the pairing parameters. The wireless communication 204 can be via Bluetooth®, as discussed above. The wireless communication 204 can be one-way or two-way communication between the reusable module 250 and the computing device 206. For example, the reusable module 250 can transmit calculated physiological parameters to the computing device 206. The computing device 206, in return, can transmit a confirmation signal back to the reusable module 250 to let the reusable module 250 know that the calculated parameters were received. The reusable module 250 can include one or more light sources (for example, LEDs) that can generate light when the reusable module 250 receives the confirmation signal from the computing device 206.
At block 1116, the sensor 240 can acquire raw patient physiological data and transmits the data to the dock 222 via the cable 230 and the flex circuit 320. The raw physiological data can be transferred to the reusable module 250 via the electrical contacts 228, 258. The sensor 240 can include, but not limited to, an acoustic sensor, ECG sensor, EEG sensor, respiratory acoustic sensor (RAS), SpO2 sensor, and the like. The sensor 240 can include one or more different types of sensors.
The sensor 240 can be placed on various areas of a patient. The location of the sensor 240 can depend on the type of sensor used for the sensor 240. For example, the sensor 240 can be an O3 sensor typically adhered to a patient's forehead to monitor cerebral oxygenation. In another example, the sensor 240 can be a respiratory acoustic sensor typically attached to a patient's neck near the trachea to detect vibrations associated with respiration.
At block 1118, the processor 254 of the reusable module 250 can receive the raw patient physiological data from the sensor 240 of the disposable module 220. The raw patient physiological data can be stored in the memory 256.
At block 1120, the processor 254 of the reusable module 250 can perform signal processing on the raw physiological data. Various types of signal processing used on the physiological data raw can include, but not limited to, analog signal processing, continuous-time signal processing, discrete-time signal processing, digital signal processing, or nonlinear signal processing. For example, continuous-time signal processing such as time domain, frequency domain, and complex frequency domain can be used. Some of the signal processing methods that can be used on the raw physiological data include, but not limited to, passive filters, active filters, additive mixers, integrators, delay lines, compandors, multiplicators, voltage-controlled filters, voltage-controlled oscillators, phase-locked loops, time domain, frequency domain, fast Fourier transform (FFT), finite impulse response (FIR) filter, infinite impulse response (IIR) filter, and adaptive filters. Such processing techniques can be used to improve signal transmission, storage efficiency, and subjective quality. In addition, such processing techniques can be used to emphasize or detect components of interest in the raw physiological data. Noise filtering can be used to filter out raw physiological data corrupted by noise due to patient movement, electromagnetic interference, or ambient light.
Signal processing can determine the absorbance's of the light due to pulsating arterial blood. For example, pulse oximeter generates a blood-volume plethysmograph waveform from which oxygen saturation of arterial blood, pulse rate, and perfusion index, among other physiological parameters, can be determined. In the context of pulse oximetry, the sensor 240 can use adaptive filter technology to separate an arterial signal, detected by a pulse oximeter sensor, from the non-arterial noise for example, venous blood movement during motion). During routine patient motions (shivering, waving, tapping, etc.), the resulting noise can be quite substantial and can easily overwhelm a conventional ratio based oximetry system. This can provide accurate blood oxygenation measurements even during patient motion, low perfusion, intense ambient light, and electrocautery interference.
At block 1122, the processor 254 of the reusable module 250 can determine patient physiological parameters by processing the raw physiological data. The processor 254 can then store the processed data and the calculated parameters in the memory 256 before transmitting them to the computing device 206.
The processed data can be indicative of an amount of attenuation of predetermined wavelengths (ranges of wavelengths) of light by body tissues, such as, for example, a digit, portions of the nose or year, a foot, or the like. For example, the predetermined wavelengths correspond to specific physiological parameter data desired including, but not limited, blood oxygen information such as oxygen content (SpOC®), oxygen saturation (SpO2), blood glucose, total hemoglobin (SbHb), methemoglobin (SpMet®), carboxyhemoglobin (SpCO), bulk tissue property measurements, water content, pH, blood pressure, respiration related information, cardiac information, perfusion index (PI), pleth variability indices (PVI®), or the like, which can be used by the mobile computing device to determine the condition of the user. The processed data can provide information regarding physiological parameters such as EEG, ECG, heart beats per minute, acoustic respiration rate (RRa), breaths per minute, end-tidal carbon dioxide (EtCO2), respiratory effort index, return of spontaneous circulation (ROSC), or the like, which can be used to determine the physiological condition of the user.
At block 1124, the processor 254 of the reusable module 250 can transmit the patient physiological parameters to the computing device 206 via the antenna 252 using the communication protocol and the pairing parameters. It can be advantageous to transmit the calculated physiological parameters (for example, 60% SpO2) as opposed to transmit the raw physiological data to the computing device 206. Compared to calculated physiological parameters, the raw physiological data can be larger in size and thus require larger bandwidth during transmission to the computing device 206. Calculated physiological parameters, on the other hand, can be much smaller in size and can require smaller bandwidth to transmit. Therefore, transmitting patient physiological parameters instead of raw physiological data can lead to decreased battery consumption and longer battery life for the disposable module 220.
The transmission of the physiological parameters can occur wirelessly via NFC. For example, the transmission of the physiological parameters occur wirelessly via Bluetooth. The transmission of the physiological parameters may occur via a cable.
At block 1126, the computing device 206 can receive the patient physiological parameters and displays them using the display 208. As discussed above, the computing device can include the display 208 that can display various patient physiological parameters including, but not limited to, body temperature, heart rate, blood oxygen level, blood pressure, and the like.
At block 1152, the reusable module 250 can establish a NFC (near field communication) with the computing device 206. As discussed above, establishing a NFC can require the reusable module 250 to be within a predetermined distance of the computing device 206. As noted above, the NFC can be established between the body 802 of the dongle 800 and the reusable module 250.
At block 1154, the reusable module 250 can transmit pairing parameters to the computing device 206. The transmission of the pairing parameters to the computing device 206 can occur when the reusable module 250 establishes the NFC with the computing device 206. At block 1156, the computing device 206 can receive the pairing parameters from the reusable module 250. The computing device 206 can use the dongle 800 to receive the pairing parameters. For example, the body 802 of the dongle 800 can wirelessly receive the pairing parameters and transmit the pairing parameters to the computing device 206 via the cable 806 and the connector 804.
At block 1158, the computing device 206 or the body 802 can associate with the reusable module 250 using the pairing parameters. Once associated, the computing device 206 or the body 802 may wait for the wireless communication 204 from the reusable module 250. As noted above, the wireless communication 204 can be made via Bluetooth®. At block 1164, the sensor 240 of the disposable module 220 can acquire physiological data and transmit the data to the reusable module 250. The physiological data acquired by the sensor 240 and transmitted to the reusable module 250 can be raw physiological data.
Blocks 1166 through 1174 may be optional. At block 1166, the reusable module can receive the patient physiological data from the disposable module 220. At block 1168, the reusable module 250 can perform signal processing on the patient physiological data. At block 1170, the reusable module 250 can determine patient physiological parameters using the processed physiological data. At block 1172, the reusable module 250 can transmit patient physiological parameters using the wireless communication 204 established between the reusable module 250 and the computing device 206. The body 802 of the dongle 800 may wirelessly receive the patient physiological parameters from the reusable module 250 and transmit the parameters to the computing device via the cable 806 and the connector 804. At block 1174, the computing device 206 receives the patient physiological parameters and displays the parameters on the display 208.
At block 1202, the processor 254 of the reusable module 250 receives raw patient physiological data from the sensor 240 of the disposable module 220 according to the blocks 1102-1120 of
At block 1204, the processor 254 of the reusable module 250 transmits the raw patient physiological data to the computing device 206. The process 254 can use the antenna 252 to transmit the raw data via the wireless communication 204 established between the reusable module 250 and the computing device 206. As mentioned above, the wireless communication 204 can be one-way or two-way between the reusable module 250 and the computing device 206.
At block 1206, the computing device 206 receives the raw patient physiological data. At block 1208, the computing device 206 performs signal processing on the raw patient physiological data. At block 1210, the computing device 206 determines patient physiological parameters using processed raw patient physiological data. At block 1212, the computing device 206 displays the determined physiological parameters on the display 208.
Mobile Application
As discussed above, the computing device 206 can be a mobile device 1300 such as a phone, tablet, watch and the like. The mobile device 1300 can include a mobile application that can establish wireless communication with the reusable module 250 via a wireless communication protocol, such as Bluetooth or the like.
As shown in
As shown in
Terminology
Many other variations than those described herein will be apparent from this disclosure. For example, depending on the embodiment, certain acts, events, or functions of any of the algorithms described herein 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, in certain embodiments, 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 various illustrative logical blocks, modules, and algorithm steps described in connection with the embodiments disclosed 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 embodiments disclosed 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. In another embodiment, a processor includes 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 embodiments disclosed 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 embodiments include, while other embodiments 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 embodiments or that one or more embodiments 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 embodiment. 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 embodiments, 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 embodiments 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 embodiments, other embodiments 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 embodiments, but is to be defined by reference to claims.
This application claims the benefit of U.S. Provisional Application No. 62/744,988, filed Oct. 12, 2018, entitled SYSTEM FOR TRANSMISSION OF SENSOR DATA USING DUAL COMMUNICATION PROTOCOL; the disclosure of which is hereby incorporated by reference in entirety.
| 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 | Polczynski | 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 | 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 et al. | 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 | May 2007 | B2 |
| 7215986 | Diab | May 2007 | B2 |
| 7221971 | Diab | May 2007 | B2 |
| 7225006 | Al-Ali et al. | May 2007 | B2 |
| 7225007 | Al-Ali | 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 | 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 | 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 | 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 |
| 7661976 | Ma | Feb 2010 | B2 |
| D614305 | Al-Ali et al. | Apr 2010 | S |
| 7697966 | Monfire 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 | Al-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 | Bellot 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 |
| 8591411 | Banet | 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 |
| 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 |
| 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 |
| 9149228 | Kinast | Oct 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 |
| 9318840 | Siev | Apr 2016 | B2 |
| 9323894 | Kiani | Apr 2016 | B2 |
| D755392 | Hwang et al. | May 2016 | S |
| 9326712 | Kiani | May 2016 | B1 |
| 9333316 | Kiani | May 2016 | B2 |
| 9339209 | Banet | 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 et al. | 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 | May 2018 | B2 |
| 9973534 | Mahaffey | 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 | Al-Ali et al. | Jan 2019 | B1 |
| 10188348 | Kiani et al. | Jan 2019 | B2 |
| RE47218 | Ali-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 |
| 10226215 | Cohrs | 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 | Triman 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 |
| 10374350 | Nakazono | 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 |
| 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 | 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 |
| 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 |
| 20020169439 | Flaherty | Nov 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 |
| 20030195401 | Tian et al. | Oct 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 |
| 20080221418 | Al-Ali et al. | Sep 2008 | A1 |
| 20080312518 | Jina et al. | Dec 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 |
| 20110004079 | Al-All et al. | Jan 2011 | A1 |
| 20110028806 | Merritt et al. | Feb 2011 | A1 |
| 20110028809 | Goodman | Feb 2011 | A1 |
| 20110040197 | Welch et al. | Feb 2011 | A1 |
| 20110082711 | Poeze et al. | Apr 2011 | A1 |
| 20110087081 | Kiani et al. | Apr 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 |
| 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 |
| 20140120564 | Workman et al. | May 2014 | A1 |
| 20140121482 | Merritt et al. | May 2014 | A1 |
| 20140127137 | Bellott et al. | May 2014 | A1 |
| 20140163344 | Al-Ali | 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 |
| 20140200420 | Al-Ali | Jul 2014 | A1 |
| 20140213864 | Abdul-Hafiz et al. | Jul 2014 | A1 |
| 20140275835 | Lamego et al. | Sep 2014 | A1 |
| 20140275871 | Lamego et al. | Sep 2014 | A1 |
| 20140275872 | Merritt 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 |
| 20150032029 | Al-Ali et al. | Jan 2015 | A1 |
| 20150038859 | Dalvi et al. | Feb 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 |
| 20150099950 | 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 |
| 20150165312 | Kiani | Jun 2015 | A1 |
| 20150196249 | Brown et al. | Jul 2015 | A1 |
| 20150216459 | 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 | 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 |
| 20160166182 | Al-Ali et al. | Jun 2016 | A1 |
| 20160166183 | Poeze et al. | Jun 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 |
| 20160321420 | Klee | Nov 2016 | A1 |
| 20160324488 | Olsen | Nov 2016 | A1 |
| 20160327984 | Al-Ali et al. | Nov 2016 | A1 |
| 20160331332 | Al-Ali | Nov 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 |
| 20170014083 | Diab et al. | Jan 2017 | A1 |
| 20170014084 | Al-Ali et al. | Jan 2017 | A1 |
| 20170024748 | Haider | Jan 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 et al. | Mar 2017 | A1 |
| 20170079594 | Telfort et al. | Mar 2017 | A1 |
| 20170086723 | Al-Ali et al. | Mar 2017 | A1 |
| 20170119252 | Kim | May 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 |
| 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 et al. | Nov 2017 | A1 |
| 20170332980 | Fifield | Nov 2017 | A1 |
| 20170340293 | Al-Ali et al. | Nov 2017 | A1 |
| 20170360310 | Kiani et al. | 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 |
| 20180216370 | Ishiguro 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 | 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 |
| 20190216370 | Schurman 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 |
| 20190320906 | Olsen | Oct 2019 | A1 |
| 20190320988 | Ahmed 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 |
| 20200085321 | Hatch | Mar 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 |
| 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 |
| Number | Date | Country |
|---|---|---|
| WO 2013184283 | Dec 2013 | WO |
| WO 2020077149 | Apr 2020 | WO |
| Entry |
|---|
| PCT Invitation to Pay Additional Search Fees issued in application No. PCT/US2019/055722 dated Jan. 30, 2020. |
| International Search Report and Written Opinion received in PCT Application No. PCT/US2019/055722, dated Mar. 23, 2020. |
| Number | Date | Country | |
|---|---|---|---|
| 20200138288 A1 | May 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62744988 | Oct 2018 | US |
