In typical medical care situations, monitors are connected to devices that receive physiological data from patients. Such devices may be passive monitoring devices or active delivery devices. Active delivery devices, for example, may provide stimulus (e.g., cardiopulmonary resuscitation (CPR) machines), drugs, and/or oxygen.
In such situations, the monitors of such devices provide critical patient information to the caregivers, such as health care providers or medical professionals (e.g., medical doctors, nurses, emergency medical technicians, etc.). In many cases, the monitors are connected to the devices as an integrated package. Oftentimes, the monitors are not readily visible to the caregivers, particularly if the caregivers are away from the patient and the devices.
Although caregivers are away from the monitors and devices, the need to be aware of a patient's condition(s) continues. In certain cases, a medical professional may not be able to view a monitor and be aware of the patient's condition(s). Examples of such situations, include instances when the caregiver has to walk away to check on another patient or attend to another task. In certain cases, a caregiver is physically unable to view a monitor. An example includes a medical evacuation situation in a helicopter when a technician and patient are physically situated such that the technician is unable to view the monitor of the device. Furthermore, in such medical evacuation situations, the environment may not be ideal (e.g., noisy, dimly lit, etc.) to properly view the monitor.
In certain situations, a monitor not only provides status of physiological data and of the connected device, but may also provide alerts as to critical levels of a patient. For example, a blood pressure device may alert the medical professional as to a critically low blood pressure level and/or irregular heartbeat. In the case of an oxygen sensing device, a monitor may alert the professional as to low levels of oxygen to the patient. Such alerts may be triggered by abnormalities/conditions experienced by the patient and/or problems/malfunctions of the device.
If a caregiver is away from a monitor, the patient's care may be compromised because the caregiver cannot properly view the condition of the patient or be aware of alerts provided by the device through the monitor.
The present description gives instances of medical technology that facilitates the remote monitoring of patients.
In one embodiment, a medical device facilitates monitoring of a patient. The medical system includes a main patient monitor collecting patient physiological parameter data, and also capable of transmitting the collected patient physiological parameter data. The main patient monitor alarms if the collected data is determined to reach a predetermined value. The device further includes a remote patient monitor, also referred to as a remote patient monitoring device, in the form of a wrist band, worn by a caregiver, configured to receive the collected patient physiological parameter data, display the collected patient physiological parameter data received from the main patient monitor, and receive a signal in response to an alarm(s) from the main patient monitor.
In one embodiment, the remote patient monitor can be a bracelet, a wrist or arm band, or other type of a small, compact, or wearable device. The remote patient monitor interfaces with the main patient monitor, a defibrillator, and/or other medical device or system. Alternatively, the remote patient monitor operates as a stand-alone, such as a puck or is incorporated into another device, such as a cell phone, a watch, bag valve mask, defibrillation electrodes, etc. The remote patient monitor allows a wearer of the device to monitor a patient through pre-set alarms, which can manifest as one or a combination of visual, tactile, auditory types of notifications, which may vary in intensity and duration depending on the preset parameters.
In some embodiments, the remote patient monitor includes a sensory feedback, such as haptic feedback, guiding a rescuer, dictating the rate via metronome, and/or notifying of elapsed time in Cardiopulmonary Resuscitation (CPR). The remote patient monitor further may include haptic feedback mechanism in bag valve mask (BVM). The remote patient monitor is, in one example, configured to differentiate haptic sensation to the wearer/rescuer to signify that a two-minute cycle has elapsed, and further to detect ventricular fibrillation (VF) or shockable rhythm, ST-elevation, ROSC (Return of Spontaneous Circulation), apnea, desaturation, etc. These and other features and advantages of this description will become more readily apparent from the following Detailed Description, which proceeds with reference to the drawings, in which:
As has been mentioned, the present description pertains to remote patient monitoring technology. Embodiments are now described in more detail.
Patient Monitoring System
The main patient monitor 108 may be configured to collect patient physiological parameter data, to transmit the collected patient physiological parameter data, and to alarm if the collected data is determined to reach a predetermined value. Other alarms may be provided, such as condition states of the main patient monitor 108 and/or devices connected to the patient of the main patient monitor 108. Examples of condition states include low power/battery of the patient monitor 108 and/or devices, transmission connectivity to the remote patient monitor 110 and other networks, etc.
The main patient monitor 108 may be connected to a remote patient monitor 110. The connection between the main patient monitor 108 and the remote patient monitor 110 may be a wired or wireless connection as represented by connection 112. In other words, the main patient monitor 108 and the remote patient monitor 110 may be wired or wirelessly coupled to one another.
In certain embodiments, the main patient monitor 108 and remote patient monitor 110 may be connected intermediately through a network, such as a cloud based network. In other words, the connection 112 may go through or be part of a network or networks, which may include cloud based network(s). In certain embodiments, cloud based network(s) may perform monitoring based on information received from the main patient monitor 108.
The remote patient monitor 110 may be configured as or be part of a cell phone, puck, or arm or wrist band 114, that may be worn or carried by a caregiver, for example on a caregiver's wrist 116. In another embodiment, the band 114 may be a in a form of a necklace, arm band, or waist band, or other wearable device. Other embodiments are possible. Caregivers may include laypeople such as family members, and/or trained medical professionals such as medical doctors, medical directors, nurses, emergency medical technicians (EMTs), and the like. Therefore, in some embodiments, the remote patient monitor 110 may be in the form of a band, such as a wrist band 114 and configured to be worn by a caregiver, to receive the collected patient physiological parameter data. The remote patient monitor 110 further may display the collected patient physiological parameter data received from the main patient monitor 108, and to receive a signal in response to an alarm from the main patient monitor 108.
In some embodiments, the band 114 may be adjustable and may include a buckle 118 and holes to attach the buckle 118 to adjust to accommodate for various sized wrists, waists, etc. A slider 122 may be used to secure to excess length of the band 114. In addition to being adjustable, the band 114 may also be waterproof and/or shock-resistant. In certain embodiments, the band 114 may be in the form of or attached to a necklace or lanyard around the caregiver's neck. In other embodiments the band 114 may be in the form of or attached to a belt around the caregiver's waist. Other embodiments may provide for the remote patient monitor 110 to be clipped onto the caregiver's clothing, such as on a lapel or chest pocket. Other embodiments may provide for the remote patient monitor 110 to be implemented as a wearable device.
The remote patient monitor 110 may include an alarm reset button 124 to reset any alarms received from the main patient monitor 108. In certain embodiments, the alarm(s) that is(are) received by the remote patient monitor 110 include one or more of vibrate (e.g., tactile/haptic alarm), light up, and/or an audible noise. In particular embodiments, the remote patient monitor 110 only vibrates as determined by the main patient monitor 108.
In certain embodiments, the remote patient monitor 110 receives haptic/sensory feedback for patient monitoring that may include a guide rate for chest compression, such as used in CPR. In such an implementation, a patient may have a physiologic monitoring sensor, which is not necessarily “wearable”, but merely attached to the patient. The patient sensor provides data to the remote patient monitor 110. The remote patient monitor 110 may include a haptic motor that conveys information to the caregiver in the form of “mimicked” sensory feedback from the patient. In yet certain other embodiments, monitoring data transmitted to the remote patient monitor 110 may be include information about ventilation (e.g. rate, tidal volume, airway pressure) being provided to the patient. The patient sensors may be incorporated as a wearable device (e.g., wrist band, head band, bracelet, etc.), standalone sensor, or incorporated into another device (e.g. bag valve mask).
In certain embodiments, the patient may be provided with disposable components such as a sticker with a wireless identifier (i.e., an RFID chip) to initiate or inform as to a haptic component/feedback. Different variations of such disposable components may make use of color coded stickers with RFID used to set various rates (e.g., 100/min for chest compression and 8/min for ventilation). Other colors may be used for various rate guidance purposes. Disposable component/sticker or RFIDs may be used to start or stop a patient/caregiver haptic motor when patient/caregiver is in proximity of the RFID. In certain implementation, a disposable component/sticker may be incorporated into a device, such as a defibrillator.
Other haptic signals may include use of different frequencies, duty cycles, sensations (vibration, taps, squeeze, etc.) to communicate different information. Physiological feedback could provide input signal to vibration intensity, rate, sensation, etc. The remote patient monitor 110 and particularly a wearable portion may incorporate a display, such that a haptic signal would alert the caregiver and the display would provide detailed information about the alert.
In certain embodiments, depending on the level of a caregiver's expertise, the alarm(s) that is(are) received by the remote patient monitor 110 may be activated based on specific preset threshold values. The alarms may include a general overall urgency alarm, and/or specific alarms. Variety of settings may be determined depending on the patient's condition, parameters, status and combined with the caregiver's rank, skills, expertise, and preferences. An alarm may be initiated at the remote patient monitor 110 to indicate an urgent need to respond to the patient, such as a cardiac arrest, an oxygen desaturation, etc. In such cases, a general urgency alarm may be activated, and/or specific alarms indicating specific medical conditions may be activated. Specific alarms may further be selected by a user/caregiver to differentiate between sounds, vibration patterns, and intensity depending on the patient identification, location, and other parameters. If several caregivers receive alarms pertaining to the same patient, and one of the alerted caregivers responds, other caregivers may be notified that the patient is being attended to. If the attending to the patient caregiver still needs additional help, the caregiver may be able to send another alarm to solicit further help. Alternatively, upon arrival at the patient's side or resolution as to the patient needs, one caregiver may terminate alarms sent to others and may further be able to follow up with a message as to the resolution of the issue.
Alarms may be sent by signals from the main patient monitor 108 to the remote patient monitor 110. After a period of time the signals may be degraded. Therefore, in certain embodiments a decoupling or a disconnection may occur between the main patient monitor 108 and the remote patient monitor 110 after a determined time period after a signal(s) is degraded. In certain instances, it may be desirable for a caregiver to reset the alarm(s) of the remote patient monitor 110. An alarm reset button 124 is provided by the remote patient monitor 110 to allow resetting of the alarm(s).
The patient monitor 110, or a wearable portion of the patient monitor 110, may include a start/stop haptic feedback metronome which may include different pre-selected metronome rates such as ventilation (e.g., 8/min), compression (e.g., 100/min), etc.
In certain embodiments, the remote patient monitor 110 may be coupled to more than one main patient monitors, including the main patient monitor 108 that is shown. In such embodiments, the remote patient monitor 110 is configured to receive various patient physiological parameter data and alarms from different medical devices and/or patients.
In certain embodiments, there may be more than one patient. Therefore, the remote patient monitor 110 may be coupled to more than one main patient monitors and/or one or more patients.
The patient monitoring system 100 may be part of different health care environments. In certain embodiments, the patient monitoring system 100 may be part of a hospital environment that includes nursing stations. A nursing station may include multiple patient monitors, such as main patient monitor 108.
Caregivers, such as medical doctors, nurses, etc., are able to simultaneously monitor patients from a central station at the nursing station. However, in certain situations the caregiver may be away from the central stations and the monitors, but would still need to be aware of the patients. In such cases, the remote patient monitor 110 may be configured to provide alarms to let the caregiver know the status of the patients and/or determine which patient(s) need to be attended to. In certain embodiments, the remote patient monitor 110 may provide a patient's name, room number (location) and/or other specific patient information. In certain embodiments, either through preset thresholds that are set at particular main patient monitor(s) 108, patients may be listed in order of need for medical attention or listed some other order, such as first request. In a further embodiment, the remote patient monitor is configured to monitor more than one patient simultaneously. If one caregiver is monitoring more than one patient, the remote patient monitor 110 can provide ranking of urgency between patients, depending on a patient's symptoms.
In certain embodiments, there may be multiple caregivers connected to the patient monitoring system 100. Provision may be made to allow a caregiver that is the first responder to the patient, to notify other caregivers that the first responding caregiver has reached the patient. Provision may also be provided to allow the first responding caregiver to request for additional help if needed. This may be performed through the remote patient monitor that is worn by the first responding caregiver.
In certain embodiments, the main patient monitor 108 may be configured with a cellular, global positioning system (GPS), or other tracking unit (not shown). The tracking unit may provide specific location of the patient (i.e., patient location 104). This may assist in identifying specific location of an ambulatory patient, to the remote patient monitor 110. The foregoing indications and responses described in conjunction with
In this embodiment, a main patient monitor 108-1 is shown to include a patient data collection module 200 which communicates with and receives patient physiological data from one or more medical devices and/or probes, such as medical probes and/or delivery devices 106 described above. In particular, the patient data collection module 200 gathers patient physiological parameter data, which may include one or more vital signs of a monitored patient (e.g., patient 102). As an example, the patient physiological parameter data may particularly include one or more of the following: blood pressure, heart rate, respiration rate, pulse rate, oxygen saturation, air flow, temperature, ECG parameters, and/or other parameters. Device data, such as low battery on one of the devices/probes interfacing/interacting with the patient or the band's inability to access information, or other parameters/data, can also be included. Other example data that may be sent can include 1) physiologic data, such as vital signs data, and/or alarm info on vital signs excursions out of normal/stable ranges; 2) monitoring device data, battery status, sensor status, etc. (i.e., information meriting the attention or intervention of a caregiver); and 3) Medical care/intervention data, i.e., information about the presence or quality of the care being applied to the patient by someone other than the person wearing the remote patient monitor, for example, alert the person managing a resuscitation (and e.g. wearing a haptic wristband) that the person managing the airway is ventilating too fast, or the person doing chest compressions has paused for too long.
The main patient monitor 108-1 may include a patient data evaluation module 202 which is configured with values for patient physiological parameter data. Such values may be preset by a caregiver to trigger an alarm. For example, if a particular value reaches or exceeds a particular level or levels, the alarm or alarms may be triggered. In this example, an alarm module 204 may be configured to provide such alert(s) in response to reaching a predetermined value(s) for the patient physiological parameter data. Alarms or alerts may initiate one or more actions such as vibration, light up, or a noise/audible sound. Such alarms or alerts may be communicated to the remote patient monitor 110.
The main patient monitor 108-1 may include a display module 206 to display the patient physiological parameter data and/or alarms. A transmitting module 208 provides signals (e.g., one or more alarm signals) to the remote patient monitor 110. The signals to the remote patient monitor 110 may include the one or more actions such as vibration, light up, or a noise/audible/haptic sound/response. In certain embodiments, the transmitting module 208 is a wireless module that may implement one or more various wireless technologies, including but not limited to Bluetooth®. one or more the various IEEE 802.11 standards, etc.
The main patient monitor 108-1 includes one or more processors 210 couple with the other components of the main patient monitor 108-1. Volatile and nonvolatile memory 212 is included in main patient monitor 108-1. Memory 212 may include computer-readable storage medium that includes instructions to perform the acts/methods described herein.
The remote patient monitor 110 is wired or wireless coupled to the main patient monitors 108 by respective links or connections 112. The remote patient monitor 110 includes a receiving module 214. In certain embodiments the receiving module 214 is a wireless receiving module, which may implement one or more various wireless technologies, including but not limited to Bluetooth®., one or more the various IEEE 802.11 standards, etc. The receiving module 214 receives one more alerts, which may be in the form of one more transmitted signals from the main patient monitors 108. The received signals from main patient monitors 108 may include the one or more actions such as vibration, light up, or a noise/audible sound.
The remote patient monitor 110 may include display module 216 may display the patient physiological parameter data and/or alarms (alerts). The display module 216 may light up with a particular alert or alerts. The remote patient monitor 110 may include a separate alert module 218. A function the alert module may perform is to vibrate when a particular alert or alerts is/are received from the main patient monitors 108. An alarm reset module 220, which may be reset by alarm reset button 124 described above, may be implemented by the remote patient monitor 110 to reset one or more alerts and alarms that are activated/displayed.
The remote patient monitor 110 includes one or more processors 222 coupled with the other components of the remote patient monitor 110. Volatile and nonvolatile memory 224 is included in remote patient monitor 110. Memory 224 may include computer-readable storage medium that includes instructions to perform the acts/methods described herein. In certain embodiments, and particular where the remote patient monitor 110 is a portable unit, a long lasting battery(ies) 226 may be part of the remote patient monitor 110.
The foregoing indications and responses described in conjunction with
Shown in
The functions of this description may be implemented by one or more devices that include logic circuitry. The device performs functions and/or methods as are described in this document. The logic circuitry may include a processor that may be programmable for a general purpose, or dedicated, such as microcontroller, a microprocessor, a Digital Signal Processor (DSP), etc. For example, the device may be a digital computer like device, such as a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Alternately, the device may be implemented by an Application Specific Integrated Circuit (ASIC), etc.
Moreover, methods are described below. The methods and algorithms presented herein are not necessarily inherently associated with any particular computer or other apparatus. Rather, various general-purpose machines may be used with programs in accordance with the teachings herein, or it may prove more convenient to construct more specialized apparatus to perform the required method steps. The required structure for a variety of these machines will become apparent from this description.
In all cases there should be borne in mind the distinction between methods in this description, and the method of operating a computing machine. This description relates both to methods in general, and also to steps for operating a computer and for processing electrical or other physical signals to generate other desired physical signals.
Programs are additionally included in this description, as are methods of operation of the programs. A program is generally defined as a group of steps leading to a desired result, due to their nature and their sequence. A program is usually advantageously implemented as a program for a computing machine, such as a general-purpose computer, a special purpose computer, a microprocessor, etc.
Storage media are additionally included in this description. Such media, individually or in combination with others, have stored thereon instructions of a program made according to the technology described herein. A storage medium according to the technology described herein is a computer-readable medium, such as a memory, and is read by the computing machine mentioned above.
Performing the steps or instructions of a program requires physical manipulations of physical quantities. Usually, though not necessarily, these quantities may be transferred, combined, compared, and otherwise manipulated or processed according to the instructions, and they may also be stored in a computer-readable medium. These quantities include, for example electrical, magnetic, and electromagnetic signals, and also states of matter that can be queried by such signals. It is convenient at times, principally for reasons of common usage, to refer to these quantities as bits, data bits, samples, values, symbols, characters, images, terms, numbers, or the like. It should be borne in mind, however, that all of these and similar terms are associated with the appropriate physical quantities, and that these terms are merely convenient labels applied to these physical quantities, individually or in groups.
This detailed description is presented largely in terms of flowcharts, display images, algorithms, and symbolic representations of operations of data bits within at least one computer readable medium, such as a memory. Indeed, such descriptions and representations are the type of convenient labels used by those skilled in programming and/or the data processing arts to effectively convey the substance of their work to others skilled in the art. A person skilled in the art of programming may use these descriptions to readily generate specific instructions for implementing a program according to the technology described herein.
Often, for the sake of convenience only, it is preferred to implement and describe a program as various interconnected distinct software modules or features, individually and collectively also known as software. This is not necessary, however, and there may be cases where modules are equivalently aggregated into a single program with unclear boundaries. In any event, the software modules or features of this description may be implemented by themselves, or in combination with others. Even though it is said that the program may be stored in a computer-readable medium, it should be clear to a person skilled in the art that it need not be a single memory, or even a single machine. Various portions, modules or features of it may reside in separate memories, or even separate machines. The separate machines may be connected directly, or through a network, such as a local access network (LAN), or a global network, such as the Internet.
It will be appreciated that some of these methods may include software steps that may be performed by different modules of an overall software architecture. For example, data forwarding in a router may be performed in a data plane, which consults a local routing table. Collection of performance data may also be performed in a data plane. The performance data may be processed in a control plane, which accordingly may update the local routing table, in addition to neighboring ones. A person skilled in the art will discern which step is best performed in which plane.
An economy is achieved in the present document in that flowcharts are used to describe both programs, and also methods. So, while flowcharts are described in terms of boxes, they can mean both method and programs.
For this description, the methods may be implemented by machine operations. In other words, embodiments of programs are made such that they perform methods in accordance to embodiments of the technology that are described in this document. These may be optionally performed in conjunction with one or more human operators performing some, but not all of them. As per the above, the users need not be collocated with each other, but each only with a machine that houses a portion of the program. Alternately, some of these machines may operate automatically, without users and/or independently from each other.
According to an operation 402, a main patient monitor obtains patient's physiological data.
According to an operation 404, the main patient monitor transmits the obtained patient physiological data to a remote patient monitor, which may be part of or integrated as a wrist band, and the evaluates obtained patient physiological data.
According to an operation 406, a decision is made whether a threshold value is reached. If the threshold value is not reached, following the “NO” branch of operation 406, operation 402 is performed.
According to an operation 408, if the threshold value is reached as determined by operation 406, then following the “YES” branch of operation 406, the main patient monitor triggers or performs an alarm or alarms.
According to an operation 410, the main patient monitor transmits the alarm or alarms to the remote patient monitor.
According to an operation 412, the remote patient monitor vibrates, alerting a caregiver.
According to an operation 412, an alarm reset button on the remote patient monitor may be activated by the caregiver to silence the alarm or alarms.
For flowchart 400, it will be recognized that a number of their operations can be augmented with what was described above.
An operation 502 obtains patient physiological data at a remote patient monitor. The remote patient monitor may be part of or integrated as a wrist band.
An operation 502 displays the patient physiological data at the remote patient monitor.
An operation 506 determines if the remote patient monitor is vibrating. If the remote patient monitor is not vibrating, then following the “NO” branch of operation 506, operation 502 is performed.
According to an operation 508, if the remote patient monitor is vibrating as determined by operation 506, then following the “YES” branch of operation 506, the alarm or alarms on the remote patient monitor may be reset.
For flowchart 500, it will be recognized that a number of their operations can be augmented with what was described above.
Notes and Additional/Alternative Implementation Details
In the above description of exemplary implementations, for purposes of explanation, specific numbers, materials configurations, and other details are set forth in order to better explain the present invention, as claimed. However, it will be apparent to one skilled in the art that the claimed invention may be practiced using different details than the exemplary ones described herein. In other instances, well-known features are omitted or simplified to clarify the description of the exemplary implementations.
The inventor intends the described exemplary implementations to be primarily examples. The inventor does not intend these exemplary implementations to limit the scope of the appended claims. Rather, the inventor has contemplated that the claimed invention might also be embodied and implemented in other ways, in conjunction with other present or future technologies.
Moreover, the word “exemplary” is used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as exemplary is not necessarily to be construed as preferred or advantageous over other aspects or designs. Rather, use of the word “exemplary” is intended to present concepts and techniques in a concrete fashion. The term “technology,” for instance, may refer to one or more devices, apparatuses, systems, methods, articles of manufacture, and/or computer-readable instructions as indicated by the context described herein.
As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless specified otherwise or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more,” unless specified otherwise or clear from context to be directed to a singular form.
Note that the order in which the processes are described is not intended to be construed as a limitation, and any number of the described process blocks can be combined in any order to implement the processes or an alternate process. Additionally, individual blocks may be deleted from the processes without departing from the spirit and scope of the subject matter described herein.
One or more embodiments described herein may be implemented fully or partially in software and/or firmware. This software and/or firmware may take the form of instructions contained in or on a non-transitory computer-readable storage medium. Those instructions may then be read and executed by one or more processors to enable performance of the operations described herein. The instructions may be in any suitable form, such as but not limited to source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. Such a computer-readable medium may include any tangible non-transitory medium for storing information in a form readable by one or more computers, such as but not limited to read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; a flash memory, etc.
The term “computer-readable media” includes computer-storage media. For example, computer-storage media may include, but are not limited to, magnetic storage devices (e.g., hard disk, floppy disk, and magnetic strips), optical disks (e.g., compact disk [CD] and digital versatile disk [DVD]), smart cards, flash memory devices (e.g., thumb drive, stick, key drive, and SD cards), and volatile and nonvolatile memory (e.g., RAM and ROM).
In the claims appended herein, the inventor invokes 35 U.S.C. § 112, paragraph 6 only when the words “means for” or “steps for” are used in the claim. If such words are not used in a claim, then the inventor does not intend for the claim to be construed to cover the corresponding structure, material, or acts described herein (and equivalents thereof) in accordance with 35 U.S.C. § 112, paragraph 6.
This patent application is a continuation of application Ser. No. 16/195,525 filed Nov. 19, 2018, which is a continuation of application Ser. No. 15/073,442 filed Mar. 17, 2016, now U.S. Pat. No. 10,136,815 Issued Nov. 27, 2018, which is a continuation of application Ser. No. 14/035,903 filed Sep. 24, 2013, now U.S. Pat. No. 9,314,159 Issued Apr. 19, 2016, which claims the benefit of provisional Application No. 61/704,710 filed Sep. 24, 2012. Each of the applications are incorporated in this patent application by this reference.
Number | Name | Date | Kind |
---|---|---|---|
2330356 | Belliveau | Sep 1943 | A |
2335524 | Lomax | Nov 1943 | A |
2736888 | McLain | Feb 1956 | A |
2896021 | Phillipps | Jul 1959 | A |
3098220 | de Graaf | Jul 1963 | A |
3439320 | Ward | Apr 1969 | A |
3478344 | Schwitzgebel et al. | Nov 1969 | A |
3553383 | Rochtus | Jan 1971 | A |
3599199 | Bunting | Aug 1971 | A |
3599200 | Bunting | Aug 1971 | A |
3696384 | Lester | Oct 1972 | A |
3739329 | Lester | Jun 1973 | A |
3767859 | Doering et al. | Oct 1973 | A |
3805265 | Lester | Apr 1974 | A |
3913153 | Adams et al. | Oct 1975 | A |
3973200 | Akerberg | Aug 1976 | A |
4067005 | Levy et al. | Jan 1978 | A |
4150284 | Trenkler et al. | Apr 1979 | A |
4151407 | McBride et al. | Apr 1979 | A |
4183015 | Drew et al. | Jan 1980 | A |
4216462 | McGrath et al. | Aug 1980 | A |
4225953 | Simon et al. | Sep 1980 | A |
4228426 | Roberts | Oct 1980 | A |
4237344 | Moore | Dec 1980 | A |
4264982 | Sakarya | Apr 1981 | A |
4275385 | White | Jun 1981 | A |
4279433 | Petaja | Jul 1981 | A |
4298863 | Natitus et al. | Nov 1981 | A |
4331953 | Blevins et al. | May 1982 | A |
4356475 | Neumann et al. | Oct 1982 | A |
4418334 | Burnett | Nov 1983 | A |
4455548 | Burnett | Jun 1984 | A |
4489387 | Lamb et al. | Dec 1984 | A |
4495495 | Ormanns et al. | Jan 1985 | A |
4495496 | Miller, III | Jan 1985 | A |
4539560 | Fleck et al. | Sep 1985 | A |
4577185 | Andersen | Mar 1986 | A |
4578671 | Flowers | Mar 1986 | A |
4593273 | Narcisse | Jun 1986 | A |
4598275 | Ross et al. | Jul 1986 | A |
4601064 | Shipley | Jul 1986 | A |
4649385 | Aires et al. | Mar 1987 | A |
4680790 | Packard et al. | Jul 1987 | A |
4709330 | Yokoi et al. | Nov 1987 | A |
4740788 | Konneker | Apr 1988 | A |
4752951 | Konneker | Jun 1988 | A |
4792798 | Wilowski | Dec 1988 | A |
4795905 | Zierhut | Jan 1989 | A |
4814751 | Hawkins et al. | Mar 1989 | A |
4833452 | Currier | May 1989 | A |
4833467 | Kobayashi et al. | May 1989 | A |
4837568 | Snaper | Jun 1989 | A |
4853692 | Wolk et al. | Aug 1989 | A |
4870700 | Ormanns et al. | Sep 1989 | A |
4899135 | Ghahariiran | Feb 1990 | A |
4907845 | Wood | Mar 1990 | A |
4947152 | Hodges | Aug 1990 | A |
4955000 | Nastrom | Sep 1990 | A |
4967195 | Shipley | Oct 1990 | A |
4990892 | Guest et al. | Feb 1991 | A |
4998095 | Shields | Mar 1991 | A |
4998938 | Ghajar et al. | Mar 1991 | A |
5006830 | Merritt | Apr 1991 | A |
5027314 | Linwood et al. | Jun 1991 | A |
5041086 | Koenig et al. | Aug 1991 | A |
5050612 | Matsumura | Sep 1991 | A |
5062151 | Shipley | Oct 1991 | A |
5065154 | Kaiser et al. | Nov 1991 | A |
5075523 | Ford | Dec 1991 | A |
5103108 | Crimmins | Jan 1992 | A |
5086290 | Murray et al. | Feb 1992 | A |
5124991 | Allen | Jun 1992 | A |
5137033 | Norton | Aug 1992 | A |
5140309 | Gusakov | Aug 1992 | A |
5153584 | Engira | Oct 1992 | A |
5235258 | Schuerch | Aug 1993 | A |
5266944 | Carroll et al. | Nov 1993 | A |
5276680 | Messenger | Jan 1994 | A |
5291399 | Chaco | Mar 1994 | A |
5319355 | Russek | Jun 1994 | A |
5319363 | Welch et al. | Jun 1994 | A |
5327592 | Stump | Jul 1994 | A |
5351439 | Takeda et al. | Oct 1994 | A |
5357254 | Kah, Jr. | Oct 1994 | A |
5375604 | Kelly et al. | Dec 1994 | A |
5396224 | Dukes et al. | Mar 1995 | A |
5396227 | Carroll et al. | Mar 1995 | A |
5400301 | Rackley | Mar 1995 | A |
5416695 | Stutman et al. | May 1995 | A |
5430900 | Kim | Jul 1995 | A |
5434755 | Corathers et al. | Jul 1995 | A |
5446678 | Saltzstein et al. | Aug 1995 | A |
5455560 | Owen | Oct 1995 | A |
5458123 | Unger | Oct 1995 | A |
5461390 | Hoshen | Oct 1995 | A |
5475367 | Prevost | Dec 1995 | A |
5511256 | Capaldi | Apr 1996 | A |
5534851 | Russek | Jul 1996 | A |
5537459 | Price et al. | Jul 1996 | A |
5548637 | Heller et al. | Aug 1996 | A |
5549119 | Solar | Aug 1996 | A |
5561412 | Novak et al. | Oct 1996 | A |
5564108 | Hunsaker et al. | Oct 1996 | A |
5568119 | Schipper et al. | Oct 1996 | A |
5576452 | Dever et al. | Nov 1996 | A |
5576952 | Stutman et al. | Nov 1996 | A |
5579001 | Dempsey et al. | Nov 1996 | A |
5588005 | Ali et al. | Dec 1996 | A |
5594786 | Chaco et al. | Jan 1997 | A |
5600214 | Fromson | Feb 1997 | A |
5621388 | Sherburne et al. | Apr 1997 | A |
5635907 | Bernard et al. | Jun 1997 | A |
5636245 | Ernst et al. | Jun 1997 | A |
5640953 | Bishop et al. | Jun 1997 | A |
5649833 | Pfeuffer et al. | Jul 1997 | A |
5650759 | Hittman et al. | Jul 1997 | A |
5650770 | Schlager et al. | Jul 1997 | A |
5664270 | Bell et al. | Sep 1997 | A |
5682139 | Pradeep et al. | Oct 1997 | A |
5682193 | Gundjian | Oct 1997 | A |
5686229 | Twist | Nov 1997 | A |
5686888 | Welles, II et al. | Nov 1997 | A |
5686902 | Reis et al. | Nov 1997 | A |
5687734 | Dempsey et al. | Nov 1997 | A |
5689229 | Chaco et al. | Nov 1997 | A |
5691980 | Welles, II et al. | Nov 1997 | A |
5699038 | Ulrich et al. | Dec 1997 | A |
5705980 | Shapiro | Jan 1998 | A |
5708421 | Boyd | Jan 1998 | A |
5713856 | Eggers et al. | Feb 1998 | A |
5714548 | Ma et al. | Feb 1998 | A |
5719761 | Gatti et al. | Feb 1998 | A |
5731757 | Layson, Jr. | Mar 1998 | A |
5742237 | Bledsoe | Apr 1998 | A |
5751246 | Hertel | May 1998 | A |
5752917 | Fuchs | May 1998 | A |
5760704 | Barton et al. | Jun 1998 | A |
5767791 | Stoop et al. | Jun 1998 | A |
5781442 | Engleson et al. | Jul 1998 | A |
5781921 | Nichols | Jul 1998 | A |
5787528 | Antinori | Aug 1998 | A |
5788646 | Fuchs et al. | Aug 1998 | A |
5793290 | Eagleson et al. | Aug 1998 | A |
5795300 | Bryars | Aug 1998 | A |
5808564 | Simms et al. | Sep 1998 | A |
5812056 | Law | Sep 1998 | A |
5822418 | Yacenda et al. | Oct 1998 | A |
5822544 | Chaco et al. | Oct 1998 | A |
5838233 | Hawes et al. | Nov 1998 | A |
5844488 | Musick | Dec 1998 | A |
5867821 | Ballantyne et al. | Feb 1999 | A |
5877675 | Rebstock et al. | Mar 1999 | A |
5901391 | Kato | May 1999 | A |
5912865 | Ortega | Jun 1999 | A |
5933488 | Marcus et al. | Aug 1999 | A |
5936539 | Fuchs | Aug 1999 | A |
5942986 | Shabot et al. | Aug 1999 | A |
5944659 | Flach et al. | Aug 1999 | A |
5956539 | Fitterman et al. | Sep 1999 | A |
5963137 | Waters, Sr. | Oct 1999 | A |
5974389 | Clark et al. | Oct 1999 | A |
5991728 | DeBusk et al. | Nov 1999 | A |
5995937 | DeBusk et al. | Nov 1999 | A |
6014633 | DeBusk et al. | Jan 2000 | A |
6037723 | Shafer et al. | Mar 2000 | A |
6057758 | Dempsey et al. | May 2000 | A |
6057782 | Koenig | May 2000 | A |
6067019 | Scott | May 2000 | A |
6076166 | Moshfeghi et al. | Jun 2000 | A |
6078261 | Davsko | Jun 2000 | A |
6085493 | DeBusk et al. | Jul 2000 | A |
6088362 | Turnbull et al. | Jul 2000 | A |
6093146 | Filangeri | Jul 2000 | A |
6097308 | Albert et al. | Aug 2000 | A |
6101644 | Gagneur et al. | Aug 2000 | A |
6111509 | Holmes | Aug 2000 | A |
6125350 | Dirbas | Sep 2000 | A |
6133837 | Riley | Oct 2000 | A |
6142592 | Grittke et al. | Nov 2000 | A |
6147592 | Ulrich et al. | Nov 2000 | A |
6149602 | Arcelus | Nov 2000 | A |
6183417 | Geheb et al. | Feb 2001 | B1 |
6208250 | Dixon et al. | Mar 2001 | B1 |
6241668 | Herzog | Jun 2001 | B1 |
6259355 | Chaco et al. | Jul 2001 | B1 |
6264614 | Albert et al. | Jul 2001 | B1 |
6272347 | Griffith et al. | Aug 2001 | B1 |
6279183 | Kummer et al. | Aug 2001 | B1 |
6287253 | Ortega et al. | Sep 2001 | B1 |
6302844 | Walker et al. | Oct 2001 | B1 |
6314556 | DeBusk et al. | Nov 2001 | B1 |
6320510 | Menkedick et al. | Nov 2001 | B2 |
6344794 | Ulrich et al. | Feb 2002 | B1 |
6348777 | Brown et al. | Feb 2002 | B1 |
6362725 | Ulrich et al. | Mar 2002 | B1 |
6364834 | Reuss et al. | Apr 2002 | B1 |
6398727 | Bui et al. | Jun 2002 | B1 |
6406426 | Reuss et al. | Jun 2002 | B1 |
6407335 | Franklin-Lees et al. | Jun 2002 | B1 |
6412980 | Lounsberry et al. | Jul 2002 | B1 |
6416471 | Kumar et al. | Jul 2002 | B1 |
6418394 | Puolakanaho et al. | Jul 2002 | B1 |
6421649 | Rattner | Jul 2002 | B1 |
6439469 | Gruber et al. | Aug 2002 | B1 |
6441742 | Lovely et al. | Aug 2002 | B1 |
6442290 | Ellis et al. | Aug 2002 | B1 |
6445299 | Rojas, Jr. | Sep 2002 | B1 |
6450956 | Rappaport et al. | Sep 2002 | B1 |
6462656 | Ulrich et al. | Oct 2002 | B2 |
6483264 | Shafer et al. | Nov 2002 | B1 |
6486792 | Moster et al. | Nov 2002 | B1 |
6493568 | Bell et al. | Dec 2002 | B1 |
6494831 | Koritzinsky | Dec 2002 | B1 |
6510344 | Halpern | Jan 2003 | B1 |
6516324 | Jones et al. | Feb 2003 | B1 |
6526310 | Carter et al. | Feb 2003 | B1 |
6529164 | Carter | Mar 2003 | B1 |
6533453 | Heidsieck et al. | Mar 2003 | B1 |
6535576 | Vafi et al. | Mar 2003 | B2 |
6539393 | Kabala | Mar 2003 | B1 |
6544173 | West et al. | Apr 2003 | B2 |
6544174 | West et al. | Apr 2003 | B2 |
6551243 | Bocionek et al. | Apr 2003 | B2 |
6553105 | Chea, Jr. et al. | Apr 2003 | B2 |
6553106 | Gould et al. | Apr 2003 | B1 |
6554174 | Aceves | Apr 2003 | B1 |
6556630 | Brinsfield et al. | Apr 2003 | B1 |
6560165 | Barker | May 2003 | B1 |
6560224 | Kung et al. | May 2003 | B1 |
6560274 | Leitgeb et al. | May 2003 | B1 |
6572556 | Stoycos et al. | Jun 2003 | B2 |
6575901 | Stoycos et al. | Jun 2003 | B2 |
6581204 | DeBusk et al. | Jun 2003 | B2 |
6584182 | Brodnick | Jun 2003 | B2 |
6584454 | Hummel, Jr. et al. | Jun 2003 | B1 |
6585645 | Hutchinson | Jul 2003 | B2 |
6589170 | Flach et al. | Jul 2003 | B1 |
6593528 | Franklin-Lees et al. | Jul 2003 | B2 |
6594146 | Frangesch et al. | Jul 2003 | B2 |
6594519 | Stoycos et al. | Jul 2003 | B2 |
6600421 | Freeman | Jul 2003 | B2 |
6603494 | Banks et al. | Aug 2003 | B1 |
6609115 | Mehring et al. | Aug 2003 | B1 |
6616606 | Petersen et al. | Sep 2003 | B1 |
6622088 | Hood | Sep 2003 | B2 |
6640246 | Gary, Jr. et al. | Oct 2003 | B1 |
6643238 | Nakajima | Nov 2003 | B2 |
6650346 | Jaeger et al. | Nov 2003 | B1 |
6659947 | Carter et al. | Dec 2003 | B1 |
6665358 | Odagiri | Dec 2003 | B1 |
6665385 | Rogers et al. | Dec 2003 | B2 |
6665820 | Frowein et al. | Dec 2003 | B1 |
6669630 | Joliat et al. | Dec 2003 | B1 |
6671547 | Lyster et al. | Dec 2003 | B2 |
6671563 | Engelson et al. | Dec 2003 | B1 |
6675041 | Dickinson | Jan 2004 | B2 |
6685633 | Albert et al. | Feb 2004 | B2 |
6689091 | Bui et al. | Feb 2004 | B2 |
6693514 | Perea, Jr. et al. | Feb 2004 | B2 |
6694367 | Miesbauer et al. | Feb 2004 | B1 |
6694509 | Stoval et al. | Feb 2004 | B1 |
6697765 | Kuth | Feb 2004 | B2 |
6707476 | Hochstedler | Mar 2004 | B1 |
6714913 | Brandt et al. | Mar 2004 | B2 |
6721818 | Nakamura | Apr 2004 | B1 |
6726634 | Freeman | Apr 2004 | B2 |
6727818 | Wildman et al. | Apr 2004 | B1 |
6731311 | Bufe et al. | May 2004 | B2 |
6731989 | Engleson et al. | May 2004 | B2 |
6736759 | Stubbs et al. | May 2004 | B1 |
6740033 | Olejniczak et al. | May 2004 | B1 |
6749566 | Russ | Jun 2004 | B2 |
6751630 | Franks et al. | Jun 2004 | B1 |
6754545 | Haeuser et al. | Jun 2004 | B2 |
6754833 | Black et al. | Jun 2004 | B1 |
6754883 | DeBusk et al. | Jun 2004 | B2 |
6759607 | Engler | Jul 2004 | B2 |
6759959 | Wildman | Jul 2004 | B2 |
6763541 | Mahoney et al. | Jul 2004 | B2 |
6771172 | Robinson et al. | Aug 2004 | B1 |
6773396 | Flach et al. | Aug 2004 | B2 |
6778225 | David | Aug 2004 | B2 |
6781517 | Moster et al. | Aug 2004 | B2 |
6784797 | Smith et al. | Aug 2004 | B2 |
6788206 | Edwards | Sep 2004 | B1 |
6791460 | Dixon et al. | Sep 2004 | B2 |
6792396 | Inda et al. | Sep 2004 | B2 |
6801227 | Bocionek et al. | Oct 2004 | B2 |
6807543 | Muthya | Oct 2004 | B2 |
6821249 | Casscells, III et al. | Nov 2004 | B2 |
6825763 | Ulrich et al. | Nov 2004 | B2 |
6826578 | Brackett et al. | Nov 2004 | B2 |
6828992 | Freeman et al. | Dec 2004 | B1 |
6829478 | Layton et al. | Dec 2004 | B1 |
6829796 | Salvatini et al. | Dec 2004 | B2 |
6830549 | Bui et al. | Dec 2004 | B2 |
6832199 | Kucek et al. | Dec 2004 | B1 |
6840117 | Hubbard, Jr. | Jan 2005 | B2 |
6847814 | Vogeleisen | Jan 2005 | B1 |
6864795 | Smith et al. | Mar 2005 | B2 |
6868256 | Dooley et al. | Mar 2005 | B2 |
6870484 | Brinsfield et al. | Mar 2005 | B1 |
6871211 | Labounty et al. | Mar 2005 | B2 |
6873884 | Brackett et al. | Mar 2005 | B2 |
6876303 | Reeder et al. | Apr 2005 | B2 |
6876985 | Kawanaka | Apr 2005 | B2 |
6885288 | Pincus | Apr 2005 | B2 |
6891909 | Hurley et al. | May 2005 | B2 |
6892083 | Shostak | May 2005 | B2 |
6904161 | Becker et al. | Jun 2005 | B1 |
6909995 | Shiraishi | Jun 2005 | B2 |
6912549 | Rotter et al. | Jun 2005 | B2 |
6915170 | Engleson et al. | Jul 2005 | B2 |
6925367 | Fontius | Aug 2005 | B2 |
6930878 | Brackett et al. | Aug 2005 | B2 |
6958706 | Chaco et al. | Oct 2005 | B2 |
6968375 | Brown | Nov 2005 | B1 |
6982639 | Brackett et al. | Jan 2006 | B2 |
6982930 | Hung | Jan 2006 | B1 |
6988989 | Weiner et al. | Jan 2006 | B2 |
6998986 | Smith | Feb 2006 | B2 |
7020921 | Wang | Apr 2006 | B2 |
7023821 | Wotherspoon et al. | Apr 2006 | B2 |
7038584 | Carter | May 2006 | B2 |
7053767 | Petite et al. | May 2006 | B2 |
7061396 | Conrad et al. | Jun 2006 | B1 |
7068143 | Doering et al. | Jun 2006 | B2 |
7071820 | Callaway | Jul 2006 | B2 |
7079036 | Cooper et al. | Jul 2006 | B2 |
7088235 | Carricut | Aug 2006 | B1 |
7092376 | Schuman | Aug 2006 | B2 |
7107642 | Wong et al. | Sep 2006 | B2 |
7138902 | Menard | Nov 2006 | B2 |
7151457 | Riley et al. | Dec 2006 | B2 |
7160133 | Karadimas et al. | Jan 2007 | B2 |
7242306 | Wildman et al. | Jul 2007 | B2 |
7248881 | Shostak | Jul 2007 | B2 |
7263669 | Denholm | Aug 2007 | B2 |
7271774 | Puuri | Sep 2007 | B2 |
7275220 | Brummel et al. | Sep 2007 | B2 |
7290299 | Votel | Nov 2007 | B2 |
7292135 | Bixler et al. | Nov 2007 | B2 |
7299512 | Cavalier et al. | Nov 2007 | B2 |
7301451 | Hastings | Nov 2007 | B2 |
7307522 | Dawson | Dec 2007 | B2 |
7310541 | Shostak | Dec 2007 | B2 |
7310549 | Angelini et al. | Dec 2007 | B1 |
7319386 | Collins, Jr. et al. | Jan 2008 | B2 |
7333002 | Bixler et al. | Feb 2008 | B2 |
7336187 | Hubbard, Jr. et al. | Feb 2008 | B2 |
7379770 | Szeto | May 2008 | B2 |
7547279 | Kim et al. | Jun 2009 | B2 |
7746218 | Collins, Jr. et al. | Jun 2010 | B2 |
7760082 | Wong et al. | Jul 2010 | B2 |
8086728 | Nasnas | Dec 2011 | B2 |
8100834 | Shuler | Jan 2012 | B2 |
8107920 | Ben Ayed | Jan 2012 | B2 |
8120471 | Collins, Jr. et al. | Feb 2012 | B2 |
8140143 | Picard et al. | Mar 2012 | B2 |
8323188 | Tran | Dec 2012 | B2 |
8536990 | Collins, Jr. et al. | Sep 2013 | B2 |
8598995 | Schuman et al. | Dec 2013 | B2 |
8866598 | Collins, Jr. et al. | Oct 2014 | B2 |
8941487 | Lee et al. | Jan 2015 | B2 |
9050031 | Collins, Jr. et al. | Jun 2015 | B2 |
9073671 | Martinez et al. | Jul 2015 | B2 |
9299242 | Schuman et al. | Mar 2016 | B2 |
9336672 | Collins, Jr. et al. | May 2016 | B2 |
9517034 | Collins, Jr. et al. | Dec 2016 | B2 |
9517035 | Schuman et al. | Dec 2016 | B2 |
9713434 | Barak | Jul 2017 | B2 |
9861321 | Collins, Jr. et al. | Jan 2018 | B2 |
9898915 | Douglas | Feb 2018 | B2 |
9955926 | Schuman et al. | May 2018 | B2 |
10080503 | Prstojevich et al. | Sep 2018 | B2 |
10264970 | Lowe, Jr. et al. | Apr 2019 | B2 |
10610111 | Tran | Apr 2020 | B1 |
20010014769 | Bufe et al. | Aug 2001 | A1 |
20010050610 | Gelston | Dec 2001 | A1 |
20010051765 | Walker et al. | Dec 2001 | A1 |
20020014951 | Kramer et al. | Feb 2002 | A1 |
20020032583 | Joao | Mar 2002 | A1 |
20020044043 | Chaco et al. | Apr 2002 | A1 |
20020044059 | Reeder et al. | Apr 2002 | A1 |
20020067273 | Jaques et al. | Jun 2002 | A1 |
20020070867 | Conway et al. | Jun 2002 | A1 |
20020080037 | Dixon et al. | Jun 2002 | A1 |
20020101349 | Rojas, Jr. | Aug 2002 | A1 |
20020103674 | Reeder et al. | Aug 2002 | A1 |
20020151810 | Wong et al. | Oct 2002 | A1 |
20020151990 | Ulrich et al. | Oct 2002 | A1 |
20020173991 | Avitall | Nov 2002 | A1 |
20020186136 | Schuman | Dec 2002 | A1 |
20020196141 | Boone et al. | Dec 2002 | A1 |
20030010345 | Koblasz et al. | Jan 2003 | A1 |
20030028449 | Heinen et al. | Feb 2003 | A1 |
20030030569 | Ulrich et al. | Feb 2003 | A1 |
20030052787 | Zerhusen et al. | Mar 2003 | A1 |
20030074222 | Rosow et al. | Apr 2003 | A1 |
20030146835 | Carter | Aug 2003 | A1 |
20030149598 | Santoso et al. | Aug 2003 | A1 |
20030176798 | Simon | Sep 2003 | A1 |
20030179099 | Perea, Jr. et al. | Sep 2003 | A1 |
20030197614 | Smith et al. | Oct 2003 | A1 |
20030206116 | Weiner et al. | Nov 2003 | A1 |
20030208110 | Mault et al. | Nov 2003 | A1 |
20030212575 | Saalsaa et al. | Nov 2003 | A1 |
20030230469 | Engler | Dec 2003 | A1 |
20040020856 | Wong et al. | Feb 2004 | A1 |
20040064890 | Kim et al. | Apr 2004 | A1 |
20040158922 | Eberler et al. | Aug 2004 | A1 |
20040183681 | Smith | Sep 2004 | A1 |
20040183684 | Callaway | Sep 2004 | A1 |
20040186358 | Chernow et al. | Sep 2004 | A1 |
20040193449 | Wildman et al. | Sep 2004 | A1 |
20040222897 | Schuhmann et al. | Nov 2004 | A1 |
20040243446 | Wyatt | Dec 2004 | A1 |
20040249670 | Noguchi et al. | Dec 2004 | A1 |
20040261184 | Flick | Dec 2004 | A1 |
20050035862 | Wildman et al. | Feb 2005 | A1 |
20050055242 | Bello et al. | Mar 2005 | A1 |
20050055779 | Damewood | Mar 2005 | A1 |
20050076441 | Dominati et al. | Apr 2005 | A1 |
20050110617 | Kile et al. | May 2005 | A1 |
20050155149 | Pedersen | Jul 2005 | A1 |
20050170863 | Shostak | Aug 2005 | A1 |
20050206505 | Arcaria | Sep 2005 | A1 |
20050242946 | Hubbard et al. | Nov 2005 | A1 |
20050256416 | Chen | Nov 2005 | A1 |
20060046579 | Karadimas et al. | Mar 2006 | A1 |
20060049936 | Collins et al. | Mar 2006 | A1 |
20060114854 | Wotherspoon et al. | Jun 2006 | A1 |
20060126560 | Wotherspoon et al. | Jun 2006 | A1 |
20060136265 | Summers et al. | Jun 2006 | A1 |
20060142665 | Garay et al. | Jun 2006 | A1 |
20060214786 | Bixler et al. | Sep 2006 | A1 |
20060220798 | Willis | Oct 2006 | A1 |
20060239195 | Camins et al. | Oct 2006 | A1 |
20060248221 | Hottel et al. | Nov 2006 | A1 |
20060267740 | Bixler et al. | Nov 2006 | A1 |
20070071114 | Sanderford et al. | Mar 2007 | A1 |
20070078324 | Wijisiriwardana | Apr 2007 | A1 |
20070156456 | McGillin et al. | Jul 2007 | A1 |
20070210917 | Collins, Jr. et al. | Sep 2007 | A1 |
20070229249 | McNeal et al. | Oct 2007 | A1 |
20070237487 | Lin | Oct 2007 | A1 |
20070239484 | Arond et al. | Oct 2007 | A1 |
20070257788 | Carlson et al. | Nov 2007 | A1 |
20070258395 | Jollota et al. | Nov 2007 | A1 |
20080004904 | Tran | Jan 2008 | A1 |
20080015900 | Denholm | Jan 2008 | A1 |
20080018436 | Traughber et al. | Jan 2008 | A1 |
20080027754 | Auker et al. | Jan 2008 | A1 |
20080205310 | Perkins et al. | Aug 2008 | A1 |
20090054751 | Babashan et al. | Feb 2009 | A1 |
20090063183 | McNeely et al. | Mar 2009 | A1 |
20090069642 | Gao et al. | Mar 2009 | A1 |
20090076350 | Bly et al. | Mar 2009 | A1 |
20090203971 | Sciarappa et al. | Aug 2009 | A1 |
20090212925 | Schuman, Sr. et al. | Aug 2009 | A1 |
20090212956 | Schuman et al. | Aug 2009 | A1 |
20090217080 | Ferguson et al. | Aug 2009 | A1 |
20090221888 | Wijesiriwardana | Sep 2009 | A1 |
20090243833 | Huang et al. | Oct 2009 | A1 |
20090322513 | Hwang et al. | Dec 2009 | A1 |
20100022902 | Lee et al. | Jan 2010 | A1 |
20100079276 | Collins, Jr. et al. | Apr 2010 | A1 |
20100081946 | Garudadri et al. | Apr 2010 | A1 |
20100087900 | Flint | Apr 2010 | A1 |
20100102973 | Grohman et al. | Apr 2010 | A1 |
20100179389 | Moroney, III et al. | Jul 2010 | A1 |
20100191074 | Chou | Jul 2010 | A1 |
20110066050 | Moon | Mar 2011 | A1 |
20110190570 | Zaimi | Aug 2011 | A1 |
20110224505 | Sadhu | Sep 2011 | A1 |
20110245633 | Goldberg et al. | Oct 2011 | A1 |
20110257544 | Kaasinen et al. | Oct 2011 | A1 |
20110263950 | Larson et al. | Oct 2011 | A1 |
20120010543 | Johnson et al. | Jan 2012 | A1 |
20120108917 | Libbus et al. | May 2012 | A1 |
20120112903 | Kaib et al. | May 2012 | A1 |
20120119890 | Collins, Jr. et al. | May 2012 | A1 |
20120130203 | Stergiou et al. | May 2012 | A1 |
20120165688 | Liu et al. | Jun 2012 | A1 |
20120203076 | Fatta et al. | Aug 2012 | A1 |
20120203078 | Sze et al. | Aug 2012 | A1 |
20120232366 | Kiani et al. | Sep 2012 | A1 |
20120245439 | Andre et al. | Sep 2012 | A1 |
20120286955 | Welch et al. | Nov 2012 | A1 |
20130045685 | Kiani | Feb 2013 | A1 |
20130172691 | Tran | Jul 2013 | A1 |
20130338460 | He et al. | Dec 2013 | A1 |
20140009271 | Collins, Jr. et al. | Jan 2014 | A1 |
20140257058 | Clarysse et al. | Sep 2014 | A1 |
20140364751 | Dugan et al. | Dec 2014 | A1 |
20140377729 | Yuen et al. | Dec 2014 | A1 |
20150022330 | Collins, Jr. et al. | Jan 2015 | A1 |
20150065893 | Ye | Mar 2015 | A1 |
20150164437 | McCombie | Jun 2015 | A1 |
20160166214 | Schuman et al. | Jun 2016 | A1 |
20160174909 | Collins, Jr. et al. | Jun 2016 | A1 |
20170035370 | Collins, Jr. et al. | Feb 2017 | A1 |
20180369065 | Siedenburg et al. | Dec 2018 | A1 |
Number | Date | Country |
---|---|---|
1623666 | Feb 2006 | EP |
1679648 | Jul 2006 | EP |
250769 | Apr 1926 | GB |
H0340176 | Feb 1991 | JP |
WO9523378 | Aug 1995 | WO |
WO9808203 | Feb 1998 | WO |
WO02091297 | Nov 2002 | WO |
WO2004036390 | Apr 2004 | WO |
Entry |
---|
COMLinx. TM. Enterpise Solutions, Nurse Communication Module, User's Guide. (373 pgs). |
“The COMposer. TM. System, Installation Manual”, by Hill-Rom Services Inc. (2003) (225 pgs). |
The COMposer. Communication System Service Manual (1995) (426 pgs). |
Partial European Search Report from EP 09 25 0420, dated Jun. 16, 2009. |
European Search Report from EP 09014863 dated Jan. 20, 2010. |
European Search Report for EP 09250419 dated Aug. 13, 2010 (12 pages). |
European Search Report from EP 10179917 dated Feb. 9, 2011, 16 pages. |
European Search Report from EP 10179932.8-2415, dated Jan. 24, 2011, 12 pages. |
European Search Report for European Appl. No. 12164812.5, dated Mar. 9, 2012 (8 pages). |
European Search Report for European Appl. No. 12164815.8 dated Mar. 9, 2012 (8pages). |
European Search Report for European Appl. No. 12164817.4 dated Mar. 9, 2012 (9 pages). |
(Online) XP002S30934 Hill-Rom Technical Brief, 222.hill-rom/Canada/PDF/144097.pdf. |
Office Action for U.S. Appl. No. 16/195,525, mailed on Feb. 24, 2021, Lyon, “Patient Monitoring Device With Remote Alert”, 14 Pages. |
Office Action for U.S. Appl. No. 16/195,525, mailed on Jun. 24, 2021, Lyon, “Patient Monitoring Device With Remote Alert”, 18 Pages. |
Office Action for U.S. Appl. No. 16/195,525, mailed on Oct. 16, 2019, Lyon, “Patient Monitoring Device With Remote Alert”, 17 pages. |
Office Action for U.S. Appl. No. 14/035,903, mailed on Oct. 22, 2015, Lyon, “Patient Monitoring Device With Remote Alert”, 18 pages. |
Office Action for U.S. Appl. No. 16/195,525, mailed on Oct. 25, 2021, Lyon, “Patient Monitoring Device With Remote Alert”, 16 Pages. |
Non Final Office Action dated Oct. 27, 2020 for U.S. Appl. No. 16/195,525, “Patient Monitoring Device With Remote Alert”, Lyon, 19 pages. |
Office Action for U.S. Appl. No. 16/195,525, mailed on Feb. 10, 2022, Lyon, “Patient Monitoring Device With Remote Alert”, 16 Pages. |
Office Action for U.S. Appl. No. 16/195,525, mailed on Apr. 15, 2020, Lyon, “Patient Monitoring Device With Remote Alert”, 20 pages. |
Office Action for U.S. Appl. No. 15/073,442, mailed on Apr. 6, 2017, Lyon, “Patient Monitoring Device With Remote Alert”, 31 pages. |
Office Action for U.S. Appl. No. 14/035,903, mailed on May 29, 2015, Lyon, “Patient Monitoring Device With Remote Alert”, 18 pages. |
Office Action for U.S. Appl. No. 16/195,525, mailed on Jun. 29, 2020, Lyon, “Patient Monitoring Device With Remote Alert”, 18 pages. |
Number | Date | Country | |
---|---|---|---|
20230014808 A1 | Jan 2023 | US |
Number | Date | Country | |
---|---|---|---|
61704710 | Sep 2012 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16195525 | Nov 2018 | US |
Child | 17934763 | US | |
Parent | 15073442 | Mar 2016 | US |
Child | 16195525 | US | |
Parent | 14035903 | Sep 2013 | US |
Child | 15073442 | US |