US 7,791,467 B2Grant
Repeater providing data exchange with a medical device for remote patient care and method thereof
Issue Date:2010-09-07
•24 Claims
•8 Drawing Sheets
Abstract
A repeater providing data exchange with a medical device for remote patient care and method thereof are provided. A plurality of interfaces include a medical device interface interconnected with a medical device, a wireless interface coupled to a wireless medium, and a wired interface coupled to a wired medium. An interface selector includes a test module operable over the wireless interface and the wired interface to evaluate conditions on each respective medium that could affect data exchange over each of the interfaces. The interface selector further includes a selection module specifying data exchange to occur using one of the wireless interface and the wired interface based on the evaluated conditions. An interrogator module exchanges data with the medical device over the medical device interface. A data transfer module exchanges the data with an external device over the specified interface.
Metadata
Assignee
- Cardiac Pacemakers, Inc.
Inventors
- Scott T. Mazar
- Yatheendhar D. Manicka
Application Information
Application Number:US 11/872,841
Filing Date:2007-10-16
Priority Date:2002-12-17
Art Unit:2612
Classifications
IPC:
G08B1/00
Patent Drawings (8 sheets)
Description
Cross-Reference to Related Applications
[0001] This patent application is a continuation of U.S. patent application Ser. No. 11/327,879, filed Jan. 9, 2006, now U.S. Pat. No. 7,292,139, which is the continuation of U.S. patent application Ser. No. 10/321,885 filed 12/17/2002, now U.S. Pat. No. 7,009,511, issued Mar. 7, 2006, the priority of filing dates of which are claimed, and the disclosures of which are incorporated by reference.
Field
[0002] The present relay device relates generally to advanced patient management systems, and more specifically to providing information between a medical device and a repository of the advanced patient management system through a repeater device.
Background
[0003] In an effort to limit the number of follow-ups necessary to monitor the device and the data that it acquires, an advanced patient management system may provide a communication infrastructure. This infrastructure allows the implantable medical device to communicate over long distances at virtually any time with a backend system that monitors the implantable device and the patient. Furthermore, this backend system allows monitoring of the patient on a more frequent basis than ordinary follow-up visits can practically allow. The back end system communicates with the implantable device through a repeater that the patient keeps in close proximity. The conventional repeater device interrogates the medical device through some form of wireless communication such as inductive coupling. The repeater device retrieves data from the medical device and transmits the data through another communication medium, such as a standard telephone line, to the remote location.
[0004] Some conventional repeater devices form a direct line of communication between the medical device and the remote location and thereby act as a conduit for the data. Generally, the patient operates these conventional repeater devices and must initiate the communication of the data at appropriate times. Other conventional repeater devices may retrieve the data from the medical device at an appropriate time and maintain it until another appropriate time when it is sent to the remote location. However, the patient must also initiate the communication between these conventional repeater devices and the remote location, or the repeater device uses a preset timer to initiate communication without regard for additional considerations.
[0005] Requiring the patient to initiate communication with the remote location is overly burdensome, especially in situations where the repeater device collects data at one time and then at some later time sends the data to the remote location. Furthermore, requiring the patient to initiate communications with the remote location makes the advanced patient management system vulnerable to human error. Relying solely on a preset timer to initiate communications with the remote location is also problematic. For example, the telephone line relied upon by the repeater device may be in use or is otherwise unavailable at the preset time, or an emergency situation may be occurring that requires immediate attention rather than communication after a preset delay period.
Summary
[0006] The problems discussed above and others are addressed by various embodiments. These embodiments allow the repeater device to automatically communicate with the remote location to transfer the patient data. The repeater device automatically communicates with the remote location by initiating communication after considering additional factors such as the accessibility or condition of the communications medium being used to pass the data and/or whether the condition of the patient requires immediate attention.
[0007] One embodiment provides an auto-configurable repeater for remote patient care and method thereof. A storage maintains data exchanged with a patient medical device. A processor includes a plurality of interfaces to an external device, including a wireless interface and a wired interface. A selection module automatically specifies one of the wireless interface and the wired interface based on conditions in respect of an associated communication medium that could affect data exchange. A transfer module accesses the data in the storage and exchanges the data with an external device over the specified interface.
[0008] A further embodiment provides a repeater providing data exchange with a medical device for remote patient care and method thereof. A plurality of interfaces include a medical device interface interconnected with a medical device, a wireless interface coupled to a wireless medium, and a wired interface coupled to a wired medium. An interface selector includes a test module operable over the wireless interface and the wired interface to evaluate conditions on each respective medium that could affect data exchange over each of the interfaces. The interface selector further includes a selection module specifying data exchange to occur using one of the wireless interface and the wired interface based on the evaluated conditions. An interrogator module exchanges data with the medical device over the medical device interface. A data transfer module exchanges the data with an external device over the specified interface.
[0009] These and various other features as well as advantages will be apparent from a reading of the following detailed description and a review of the associated drawings.
Brief Description of the Drawings
[0010] In the drawings, which are not necessarily drawn to scale, like numerals describe substantially similar components throughout the several views. Like numerals having different letter suffixes represent different instances of substantially similar components. The drawings illustrate generally, by way of example, but not by way of limitation, various embodiments discussed in the present document.
[0011] FIG. 1 illustrates an example advanced patient management system;
[0012] FIG. 2 illustrates an example computer system for use with the advanced patient management system;
[0013] FIG. 3 illustrates an example interrogator/transceiver unit for use with the advanced patient management system; and
[0014] FIG. 4 illustrates an example communication system for use with the advanced patient management system;
[0015] FIG. 5 illustrates communication between an implantable medical device, an external repeater device, and a repository;
[0016] FIG. 6 illustrates exemplary external repeater device of FIG. 5 in more detail;
[0017] FIG. 7 illustrates components of the exemplary repeater device;
[0018] FIG. 8 illustrates an exemplary operational flow of communication between the implantable medical device, the external repeater device, and the repository where the degree of urgency of the data is determined and considered in relation to data transfer to the repository;
[0019] FIG. 9 illustrates an exemplary operational flow of communication between the implantable medical device, the external repeater device, and the repository where the condition of the communication medium is considered in relation to data transfer to the repository;
[0020] FIG. 10 illustrates an exemplary operational flow of communication between the implantable medical device, the external repeater device, and the repository where both the degree of urgency of the data and the condition of the communication medium are considered in relation to data transfer to the repository.
Detailed Description
[0021] Prior to discussing the devices and communication protocols of the embodiments, an example of an advanced patient management system is discussed to provide an example of an environmental context for the embodiments. However, it is to be understood that the advanced patient management system described herein in conjunction with the embodiments is only one example of an environmental context and that the embodiments are applicable to other environmental contexts that may or may not include an advanced patient management system. The devices and communication protocols of the embodiments are described below with reference to FIGS. 5-10 and section V. Repeater Communications.
[0022] An advanced patient management system is configured to collect patient-specific information, store and collate the information, and generate actionable recommendations to enable the predictive management of patients. The advanced patient management system is also configured to leverage a remote communications infrastructure to provide automatic device follow-ups to collect data, coordinate therapy, and to determine if remote devices are functioning properly. The term “patient” is used herein to mean any individual from whom information is collected. The term “caregiver” is used herein to mean any provider of services, such as health care providers including, but not limited to, nurses, doctors, and other health care provider staff.
[0023] FIG. 1 illustrates an example advanced patient management system 100. Advanced patient management system 100 generally includes the following components: one or more devices 102, 104, and 106, one or more interrogator/transceiver units 108, a communication system 110, one or more remote peripheral devices 109, and a host 112.
[0024] Each component of the advanced patient management system 100 can communicate using the communication system 110. Some components may also communicate directly with one another. For example, devices 102 and 104 may be configured to communicate directly with one another. The various components of the example advanced patient management system 100 illustrated herein are described below.
Devices
[0025] Devices 102, 104, and 106 can be implantable devices or external devices that may provide one or more of the following functions with respect to a patient: (1) sensing, (2) data analysis, and (3) therapy. For example, in one embodiment, devices 102, 104, and 106 are either implanted or external devices used to measure a variety of physiological, subjective, and environmental conditions of a patient using electrical, mechanical, and/or chemical means. The devices 102, 104, and 106 can be configured to automatically gather data or can require manual intervention by the patient. The devices 102, 104, and 106 can be configured to store data related to the physiological and/or subjective measurements and/or transmit the data to the communication system 110 using a variety of methods, described in detail below. Although three devices 102, 104, and 106 are illustrated in the example embodiment shown, more or fewer devices may be used for a given patient.
[0026] The devices 102, 104, and 106 can be configured to analyze the measured data and act upon the analyzed data. For example, the devices 102, 104, and 106 are configured to modify therapy or provide alarm indications based on the analysis of the data.
[0027] In one embodiment, devices 102, 104, and 106 also provide therapy. Therapy can be provided automatically or in response to an external communication. Devices 102, 104, and 106 are programmable in that the characteristics of their sensing, therapy (e.g., duration and interval), or communication can be altered by communication between the devices 102, 104, and 106 and other components of the advanced patient management system 100. Devices 102, 104, and 106 can also perform self-checks or be interrogated by the communication system 110 to verify that the devices are functioning properly. Examples of different embodiments of the devices 102, 104, and 106 are provided below.
[0028] Devices implanted within the body have the ability to sense and communicate as well as to provide therapy. Implantable devices can provide direct measurement of characteristics of the body, including, without limitation, electrical cardiac activity (e.g., a pacemaker, cardiac resynchronization management device, defibrillator, etc.), physical motion, temperature, heart rate, activity, blood pressure, breathing patterns, ejection fractions, blood viscosity, blood chemistry, blood glucose levels, and other patient-specific clinical physiological parameters, while minimizing the need for patient compliance.
[0029] A heart rhythm sensor, typically found in a pacemaker or defibrillator, is one example of an implantable device. In the heart, an electrical wave activates the heart muscle just prior to contraction. As is known in the art, electrical circuits and lead-wires transduce the heart's activation event and reject other, non-essential electrical events. By measuring the time interval between activation events, the heart rhythm can be determined. A transthoracic impedance sensor is another example of a sensor in an implantable device. During the respiratory cycle, large volumes of air pass into and out of the body. The electrical resistance of the thorax changes markedly as a result of large differences in conductivity of air and body tissues. The thoracic resistance can be measured during respiration and converted into a measurable electrical signal (i.e., impedance) so that breathing rate and profile can be approximated. Implantable devices can also sense chemical conditions, such as glucose levels, blood oxygen levels, etc. Further, the advanced patient management system 100 may utilize other implantable devices as well that provide physiological measurements of the patient, such as drug pumps, neurological devices (e.g., stimulators), oxygen sensors, etc.
[0030] Derived measurements can also be determined from the implantable device sensors. For example, a sleep sensor can rely on measurements taken by an implanted accelerometer that measures body activity levels. The sleep sensor can estimate sleeping patterns based on the measured activity levels. Other derived measurements include, but are not limited to, a functional capacity indicator, autonomic tone indicator, sleep quality indicator, cough indicator, anxiety indicator, and cardiovascular wellness indicator for calculating a quality of life indicator quantifying a patient's overall health and well-being.
[0031] Devices 102, 104, and 106 can also be external devices, or devices that are not implanted in the human body, that are used to measure physiological data. Such devices include a multitude of devices to measure data relating to the human body, such as temperature (e.g., a thermometer), blood pressure (e.g., a sphygmomanometer), blood characteristics (e.g., glucose levels), body weight, physical strength, mental acuity, diet, heart characteristics, and relative geographic position (e.g., a Global Positioning System (GPS)).
[0032] Devices 102, 104, and 106 can also be environmental sensors. The devices can be placed in a variety of geographic locations (in close proximity to patient or distributed throughout a population) and record non-patient specific characteristics such as, but not limited to, temperature, air quality, humidity, carbon monoxide level, oxygen level, barometric pressure, light intensity, and sound.
[0033] One or more of the devices 102, 104, and 106 (for example, device 106) may be external devices that measure subjective or perceptive data from the patient. Subjective data is information related to a patient's feelings, perceptions, and/or opinions, as opposed to objective physiological data. For example, the “subjective” devices can measure patient responses to inquiries such as “How do you feel?” and “How is your pain?” The device can prompt the patient and record subjective data from the patient using visual and/or audible cues. For example, the patient can press coded response buttons or type an appropriate response on a keypad. Alternatively, subjective data may be collected by allowing the patient to speak into a microphone and using speech recognition software to process the subjective data.
[0034] In one example embodiment, the subjective device presents the patient with a relatively small number of responses to each question posed to the patient. For example, the responses available to the patient may include three faces representing feelings of happiness, nominalness, and sadness. Averaged over time, a trend of a patient's well being will emerge with a finer resolution than the quanta of the three responses.
[0035] The subjective data can be collected from the patient at set times, or, alternatively, collected whenever the patient feels like providing subjective data. The subjective data can also be collected substantially contemporaneously with physiological data to provide greater insight into overall patient wellness. The subjective device 106 can be any device that accepts input from a patient or other concerned individual and/or provides information in a format that is recognizable to the patient. Device 106 typically includes a keypad, mouse, display, handheld device, interactive TV, cellular telephone or other radio frequency (“RF”) communications device, cordless phone, corded phone, speaker, microphone, email message, or physical stimulus.
[0036] In one example embodiment, the subjective device 106 includes or is part of a computer system 200, as illustrated in FIG. 2 . The example computer system 200 includes a central processor unit 212 and a system memory 214. The computer system 200 further includes one or more drives 223 for reading data from and writing data to, as well as an input device 244, such as a keyboard or mouse, and a monitor 252 or other type of display device. A number of program modules may be stored on the drive 223, including an operating system 236, one or more application programs 238, other program modules 240, and program data 242. The computer system 200 can operate in a networked environment using logical connections to one or more remote computers or computer systems 256. Computer system 200 can also include hand-held computers such as a PDA computer.
[0037] The advanced patient management system 100 may also include one or more remote peripheral devices 109. The remote peripheral device 109 may include, for example and without limitation, cellular telephones, pagers, PDA devices, facsimiles, remote computers, printers, video and/or audio devices, etc. The remote peripheral device 109 can communicate using wired or wireless technologies and may be used by the patient or caregiver to communicate with the communication system 110 and/or the host 112. For example, the remote peripheral device 109 can be used by the caregiver to receive alerts from the host 112 based on data collected from the patient and to send instructions from the caregiver to either the patient or other clinical staff. In another example, the remote peripheral device 109 is used by the patient to receive periodic or real time updates and alerts regarding the patient's health and well-being.
Interrogator/Transceiver Unit
[0038] Referring now to FIG. 3 , the example advanced patient management system 100 includes one or more interrogator/transceiver units (“ITUs”), such as ITU 108. The ITU 108 includes an interrogator module 152 for sending and receiving data from a device, such as devices 102, 104, and 106, a memory module 154 for storing data, and a transceiver module 156 for sending and receiving data to and from other components of the APM system 100. The transceiver module may also operate as an interrogator of the devices 102, 104 and 106. The ITU 108 also includes a power module 158 that provides power.
[0039] The ITU 108 may perform one or more of the following functions: (1) data storage; (2) data analysis; (3) data forwarding; (4) patient interaction; (5) patient feedback; and (6) data communications. For example, the ITU 108 may facilitate communications between the devices 102, 104, and 106 and the communication system 110. The ITU 108 can, periodically or in real-time, interrogate and download into memory clinically relevant patient data from the devices 102, 104, and/or 106. This data includes, in the cardiac sensor context, for example, P and R-wave measurements, pacing, shocking events, lead impedances, pacing thresholds, battery voltage, capacitor charge times, ATR episodes with electrograms, tachycardia episodes with electrograms, histogram information, and any other clinical information necessary to ensure patient health and proper device function. The data is sent to the ITU 108 by the devices 102, 104, and 106 in real-time or periodically uploaded from buffers in the devices.
[0040] The ITU 108 may also allow patient interaction. For example, the ITU 108 may include a patient interface and allow the patient to input subjective data. In addition, the ITU 108 may provide feedback to the patient based on the data that has been analyzed or based on information communicated by the communication system 110.
[0041] In another embodiment, the ITU 108 includes a telemetry link from the devices to a network that forms the basis of a wireless LAN in the patient's home. The ITU 108 systematically uploads information from the devices 102, 104, and/or 106 while the patient is sleeping, for example. The uploaded data is transmitted through the communication system 110 or directly to the host 112. In addition, in one embodiment the ITU 108 functions in a hybrid form, utilizing wireless communication when available and defaulting to a local wireless portal or a wired connection when the wireless communication becomes unavailable.
[0042] Some devices, such as legacy implanted cardiac rhythm management (“CRM”) devices, communicate via an internal telemetry transceiver that communicates with an external programmer. The communication range of such devices is typically 1 to 4 inches. ITU 108 may include a special short-range interrogator that communicates with a legacy device.
[0043] When the interrogator 152 uses radio frequency to communicate with the devices 102, 104, 106, the ITU 108 may be in the form of a small device that is placed in an inconspicuous place within the patient's residence. Alternatively, the ITU 108 may be implemented as part of a commonly-used appliance in the patient's residence. For example, the ITU may be integrated with an alarm clock that is positioned near the patient's bed. In another embodiment, the ITU may be implemented as part of the patient's personal computer system. Other embodiments are also possible.
[0044] In another embodiment, the ITU 108 may comprise a hand-held device such as a PDA, cellular telephone, or other similar device that is in wireless communication with the devices 102, 104, and 106. The hand-held device may upload the data to the communication system 110 wirelessly. Alternatively, the hand-held device may periodically be placed in a cradle or other similar device that is configured to transmit the data to the communication system 110.
[0045] In one embodiment, the ITU 108 can perform analysis on the data and provide immediate feedback, as well as perform a variety of self-diagnostic tests to verify that it is functioning properly and that communication with the communication system 110 has not be compromised. For example, the ITU 108 can perform a diagnostic loop-back test at a time set by the host 112, which involves sending a request through the communication system 110 to the host 112. The host 112 can then reply with a response back through the communication system 110 to the ITU 108. If a specific duration elapses before the ITU 108 receives the response or the ITU 108 receives an unexpected response, or if the host 112 does not receive the diagnostic test communication, the ITU 108 can provide indications that the system is not functioning properly and the host 112 can alert an operator that there may be compromised communications with that specific ITU 108. For example, if wireless communications between the ITU 108 and the communication system 110 have been interrupted, and the ITU 108 performs a self-diagnostic test that fails, the ITU 108 may alert the patient so that corrective action may be taken. The alert can take the form of a sound or a visual and/or audible annunciator to alert the patient that communication has been interrupted. In another embodiment, the ITU 108 can automatically fail-back to a wired system to communicate with the communication system 110 and perform the same communications compromise checks.
[0046] In other embodiments of the advanced patient management system 100, the ITU 108 function can be integrated into devices 102, 104, and 106, so that the devices can communicate directly with the communication system 110 and/or host 112. The devices 102, 104 and 106 can incorporate multi-mode wireless telecommunications such as cellular, BLUETOOTH, or IEEE 802.11B to communicate with the communication system 110 directly or through a local wireless to a wired portal in the patients' home. For example, device 102 may include a miniature cellular phone capable of wirelessly uploading clinical data from the device on a periodic basis. This is particularly advantageous for devices that are mobile (e.g., an implanted device in a patient that is traveling).
[0047] To conserve the energy of the devices 102, 104, and 106, particularly when the devices (e.g., device 102) are configured to communicate directly with the communication system 110 without using an ITU 108, in one example embodiment the devices are configured to communicate during a given duty cycle. For example, the device 102 can be configured to communicate with the communication system 110 at given intervals, such as once a week. The device 102 can record data for the time period (e.g., a week) and transmit the data to the communication system 110 during the portion of the cycle that transmission is active and then conserve energy for the rest of the cycle. In another example, the device 102 conserves energy and only communicates with the communication system 110 when an “interesting” event, such as a heart arrhythmia, has occurred. In this manner, device 102 can communicate directly with the communication system 110 and/or host 112 without requiring an ITU 108, while conserving the energy of the device by communicating only during a given duty cycle.
[0048] The interrogation rate of the ITU 108 can be varied depending on disease state and other relevant factors. In addition, the devices 102, 104, and 106 can be configured to “wake up” frequently (e.g., once every couple minutes) to provide the ITU 108 an access window for the ITU 108 to provide commands to the devices 102, 104, and 106, as well as upload data from the devices.
[0049] If multiple devices, such as devices 102, 104, and 106, are provided for a given patient, each device may include its own means for communicating with the ITU 108 or communication system 110. Alternatively, a single telemetry system may be implemented as part of one of the devices, or separate from the devices, and each device 102, 104, and 106 can use this single telemetry system to communication with the ITU 108 or the communication system 110.
[0050] In yet another embodiment, the devices 102, 104, and 106 include wires or leads extending from devices 102, 104, and 106 to an area external of the patient to provide a direct physical connection. The external leads can be connected, for example, to the ITU 108 or a similar device to provide communications between the devices 102, 104, and 106 and the other components of the advanced patient management system 100.
[0051] The advanced patient management system 100 can also involve a hybrid use of the ITU 108. For example, the devices 102, 104, and 106 can intelligently communicate via short-range telemetry with the ITU when the patient is located within the patient's home and communicate directly with the communication system 110 or host 112 when the patient is traveling. This may be advantageous, for example, to conserve battery power when the devices are located near an ITU.
Communication System
[0052] Communication system 110 provides for communications between and among the various components of the advanced patient management system 100, such as the devices 102, 104, and 106, host 112, and remote peripheral device 109. FIG. 4 illustrates one embodiment for the communication system 110. The communication system 110 includes a plurality of computer systems 304, 306, 308, and 310, as well as device 102, host 112, and remote peripheral device 109, connected to one another by the communications network 300. The communications network 300 may be, for example, a local area network (LAN), wide area network (WAN), or the Internet. Communications among the various components, as described more fully below, may be implemented using wired or wireless technologies.
[0053] In the example embodiment illustrated, the host 112 includes server computers 318 and 322 that communicate with computers 304, 306, 308, and 310 using a variety of communications protocols, described more fully below. The server computers 318 and 322 store information in databases 316 and 320. This information may also be stored in a distributed manner across one or more additional servers.
[0054] A variety of communication methods and protocols may be used to facilitate communication between devices 102, 104, and 106, ITU 108, communication system 110, host 112, and remote peripheral device 109. For example, wired and wireless communications methods may be used. Wired communication methods may include, for example and without limitation, traditional copper-line communications such as DSL, broadband technologies such as ISDN and cable modems, and fiber optics, while wireless communications may include cellular, satellite, radio frequency (RF), Infrared, etc.
[0055] For any given communication method, a multitude of standard and/or proprietary communication protocols may be used. For example and without limitation, protocols such as radio frequency pulse coding, spread spectrum, direct sequence, time-hopping, frequency hopping, SMTP, FTP, and TCP/IP may be used. Other proprietary methods and protocols may also be used. Further, a combination of two or more of the communication methods and protocols may also be used.
[0056] The various communications between the components of the advanced patient management system 100 may be made secure using several different techniques. For example, encryption and/or tunneling techniques may be used to protect data transmissions. Alternatively, a priority data exchange format and interface that are kept confidential may also be used. Authentication can be implemented using, for example, digital signatures based on a known key structure (e.g., PGP or RSA). Other physical security and authentication measures may also be used, such as security cards and biometric security apparatuses (e.g., retina scans, iris scans, fingerprint scans, veinprint scans, voice, facial geometry recognition, etc.). Conventional security methods such as firewalls may be used to protect information residing on one or more of the storage media of the advanced patient management system 100. Encryption, authentication and verification techniques may also be used to detect and correct data transmission errors.
[0057] Communications among the various components of the advanced patient management system 100 may be enhanced using compression techniques to allow large amounts of data to be transmitted efficiently. For example, the devices 102, 104, and 106 or the ITU 108 may compress the recorded information prior to transmitting the information to the ITU 108 or directly to the communication system 110.
[0058] The communication methods and protocols described above can facilitate periodic and/or real-time delivery of data.
Host
[0059] The example host 112 includes a database module 114, an analysis module 116, and a delivery module 118 (see FIG. 1 ). Host 112 preferably includes enough processing power to analyze and process large amounts of data collected from each patient, as well as to process statistics and perform analysis for large populations. For example, the host 112 may include a mainframe computer or multi-processor workstation. The host 112 may also include one or more personal computer systems containing sufficient computing power and memory. The host 112 may include storage medium (e.g., hard disks, optical data storage devices, etc.) sufficient to store the massive amount of high-resolution data that is collected from the patients and analyzed.
[0060] The host 112 may also include identification and contact information (e.g., IP addresses, telephone numbers, or a product serial number) for the various devices communicating with it, such as ITU 108 and peripheral device 109. For example, each ITU 108 is assigned a hard-coded or static identifier (e.g., IP address, telephone number, etc.), which allows the host 112 to identify which patient's information the host 112 is receiving at a given instant. Alternatively, each device 102, 104, and 106 may be assigned a unique identification number, or a unique patient identification number may be transmitted with each transmission of patient data.
[0061] When a device is first activated, several methods may be used to associate data received by the advanced patient management system 100 with a given patient. For example, each device may include a unique identification number and a registration form that is filled out by the patient, caregiver, or field representative. The registration form can be used to collect the necessary information to associate collected data with the patient. Alternatively, the user can logon to a web site to allow for the registration information to be collected. In another embodiment, a barcode is included on each device that is scanned prior to or in conjunction deployment of the device to provide the information necessary to associate the recorded data with the given patient.
[0062] Referring again to FIG. 1 , the example database module 114 includes a patient database 400, a population database 402, a medical database 404, and a general database 406, all of which are described further below.
[0063] The patient database 400 includes patient specific data, including data acquired by the devices 102, 104, and 106. The patient database 400 also includes a patient's medical records. The patient database 400 can include historical information regarding the devices 102, 104, and 106. For example, if device 102 is an implantable cardioverter defibrillator (ICD), the patient database 400 records the following device information: P and R measurements, pacing frequency, pacing thresholds, shocking events, recharge time, lead impedance, battery voltage/remaining life, ATR episode and EGMs, histogram information, and other device-specific information. The information stored in the database 400 can be recorded at various times depending on the patient requirements or device requirements. For example, the database 400 is updated at periodic intervals that coincide with the patient downloading data from the device. Alternatively, data in the database 400 can be updated in real time. Typically, the sampling frequency depends on the health condition being monitored and the co-morbidities.
[0064] The population database 402 includes non-patient specific data, such as data relating to other patients and population trends. The population database 402 also records epidemic-class device statistics and patient statistics. The population database 402 also includes data relating to staffing by health care providers, environmental data, pharmaceuticals, etc.
[0065] The example medical database 404 includes clinical data relating to the treatment of diseases. For example, the medical database 404 includes historical trend data for multiple patients in the form of a record of progression of their disease(s) along with markers of key events.
[0066] The general database 406 includes non-medical data of interest to the patient. This can include information relating to news, finances, shopping, technology, entertainment, and/or sports. The general database 406 can be customized to provide general information of specific interest to the patient. For example, stock information can be presented along with the latest health information as detected from the devices 102, 104, and 106.
[0067] In another embodiment, information is also provided from an external source, such as external database 600. For example, the external database 600 includes external medical records maintained by a third party, such as drug prescription records maintained by a pharmacy, providing information regarding the type of drugs that have been prescribed for a patient.
[0068] The example analysis module 116 includes a patient analysis module 500, device analysis module 502, population analysis module 504, and learning module 506.
[0069] Patient analysis module 500 may utilize information collected by the advanced patient management system 100, as well as information for other relevant sources, to analyze data related to a patient and provide timely and predictive assessments of the patient's well-being. In performing this analysis, the patient device module 500 may utilize data collected from a variety of sources, include patient specific physiological and subjective data collected by the advanced patient management system 100, medical and historical records (e.g., lab test results, histories of illnesses, etc., drugs currently and previously administered, etc.), as well as information related to population trends provided from sources external to the advanced patient management system 100.
[0070] For example, in one embodiment, the patient analysis module 500 makes a predictive diagnosis of an oncoming event based on information stored in the database module 114. For example, the data continuously gathered from a device of a given patient at a heightened risk for a chronic disease event (such as de-compensations in heart failure) is analyzed. Based on this analysis, therapy, typically device-based or pharmaceutical, is then be applied to the patient either through the device or through clinician intervention.
[0071] In another example embodiment, the patient analysis module 500 provides a diagnosis of patient health status and predicted trend based on present and recent historical data collected from a device as interpreted by a system of expert knowledge derived from working practices within clinics. For example, the patient analysis module 500 performs probabilistic calculations using currently-collected information combined with regularly-collected historical information to predict patient health degradation.
[0072] In another example embodiment, the patient analysis module 500 may conduct pre-evaluation of the incoming data stream combined with patient historical information and information from patients with similar disease states. The pre-evaluation system is based on data derived from working clinical practices and the records of outcomes. The derived data is processed in a neural network, fuzzy logic system, or equivalent system to reflect the clinical practice. Further, the patient analysis module 500 may also provide means for periodic processing of present and historical data to yield a multidimensional health state indication along with disease trend prediction, next phase of disease progression co-morbidities, and inferences about what other possible diseases may be involved. The patient analysis module 500 may also integrate data collected from internal and external devices with subjective data to optimize management of overall patient health.
[0073] Device analysis module 502 analyzes data from the devices 102, 104, and 106 and ITU 108 to predict and determine device issues or failures. For example, if an implanted device 102 fails to communicate at an expected time, device analysis module 502 determines the source of the failure and takes action to restore the performance of the device 102. The device analysis module 502 may also perform additional deterministic and probabilistic calculations. For example, the device analysis module 502 gathers data related to charge levels within a given device, such as an ICD, and provides analysis and alerting functions based on this information if, for example, the charge level reaches a point at which replacement of the device and/or battery is necessary. Similarly, early degradation or imminent failure of implanted devices can be identified and proactively addressed, or at-risk devices can be closely monitored.
[0074] Population analysis module 504 uses the data collected in the database module 114 to manage the health of a population. For example, a clinic managing cardiac patients can access the advanced patient management system 100 and thereby obtain device-supplied advance information to predict and optimize resource allocation both as to immediate care and as a predictive metric for future need of practicing specialists. As another example, the spread of disease in remote populations can be localized and quarantined rapidly before further spread.
[0075] In one embodiment, population analysis module 504 trends the patient population therapy and management as recorded by the devices and directs health care resources to best satisfy the needs of the population. The resources can include people, facilities, supplies, and/or pharmaceuticals. In other embodiments, the population analysis module detects epidemics and other events that affect large population groups. The population analysis module 504 can issue alerts that can initiate a population quarantine, redirect resources to balance size of staffing with number of presenting population, and predict future need of qualified specialists.
[0076] The population analysis module 504 may utilize a variety of characteristics to identify like-situated patients, such as, for example, sex, age, genetic makeup, etc. The population analysis module 504 may develop large amounts of data related to a given population based on the information collected by the advanced patient management system 100. In addition, the population analysis module 504 may integrate information from a variety of other sources. For example, the population analysis module 504 may utilize data from public domain databases (e.g., the National Institute of Health), public and governmental and health agency databases, private insurance companies, medical societies (e.g., the American Heart Association), and genomic records (e.g., DNA sequences).
[0077] In one embodiment, the host 112 may be used as a “data clearinghouse,” to gather and integrate data collected from the devices 102, 104, and 106, as well as data from sources outside the advanced patient management system 100. The integrated data can be shared with other interested entities, subject to privacy restrictions, thereby increasing the quality and integration of data available.
[0078] Learning module 506 analyzes the data provided from the various information sources, including the data collected by the advanced patient system 100 and external information sources. For example, the learning module 506 analyzes historical symptoms, diagnoses, and outcomes along with time development of the diseases and co-morbidities. The learning module 506 can be implemented via a neural network (or equivalent) system.
[0079] The learning module 506 can be partially trained (i.e., the learning module 506 may be implemented with a given set of preset values and then learn as the advanced patient management system functions) or untrained (i.e., the learning module 506 is initiated with no preset values and must learn from scratch as the advanced patient management system functions). In other alternative embodiments, the learning module 506 may continue to learn and adjust as the advanced patient management system functions (i.e., in real time), or the learning module 506 may remain at a given level of learning and only advanced to a higher level of understanding when manually allowed to do so.
[0080] In a neural network embodiment, new clinical information is presented to create new neural network coefficients that are distributed as a neural network knowledge upgrade. The learning module 506 can include a module for verifying the neural network conclusions for clinical accuracy and significance. The learning module can analyze a database of test cases, appropriate outcomes and relative occurrence of misidentification of the proper outcomes. In some embodiments, the learning module 506 can update the analysis module 116 when the analysis algorithms exceed a threshold level of acceptable misidentifications.
[0081] The example learning module 506 uses various algorithms and mathematical modeling such as, for example, trend and statistical analysis, data mining, pattern recognition, cluster analysis, neural networks and fuzzy logic. Learning module 506 may perform deterministic and probabilistic calculations. Deterministic calculations include algorithms for which a clear correlation is known between the data analyzed and a given outcome. For example, there may be a clear correlation between the energy left in a battery of an implantable device and the amount of time left before the battery must be replaced.
[0082] A probabilistic calculation involves the correlation between data and a given outcome that is less than 100 percent certain. Probabilistic determinations require an analysis of several possible outcomes and an assignment of probabilities for those outcomes (e.g., an increase in weight of a patient may, at a 25% probability, signal an impending de-compensation event and/or indicate that other tests are needed). The learning module 506 performs probabilistic calculations and selects a given response based on less than a 100% probability. Further, as the learning module 506 “learns” for previous determinations (e.g., through a neural network configuration), the learning module 506 becomes more proficient at assigning probabilities for a given data pattern, thereby being able to more confidently select a given response. As the amount of data that has been analyzed by the learning module 506 grows, the learning module 506 becomes more and more accurate at assigning probabilities based on data patterns. A bifurcated analysis may be performed for diseases exhibiting similar symptoms. As progressive quantities of data are collected and the understanding of a given disease state advances, disease analysis is refined where a former singular classification may split into two or more sub-classes.
[0083] In addition, patient-specific clinical information can be stored and tracked for hundreds of thousands of individual patients, enabling a first-level electronic clinical analysis of the patient's clinical status and an intelligent estimate of the patient's short-term clinical prognosis. The learning module 506 is capable of tracking and forecasting a patient's clinical status with increasing levels of sophistication by measuring a number of interacting co-morbidities, all of which may serve individually or collectively to degrade the patient's health. This enables learning module 506, as well as caregivers, to formulate a predictive medical response to oncoming acute events in the treatment of patients with chronic diseases such as heart failure, diabetes, pain, cancer, and asthma/COPD, as well as possibly head-off acute catastrophic conditions such as MI and stroke.
[0084] Delivery module 118 coordinates the delivery of feedback based on the analysis performed by the host 112. In response to the analysis module 116, delivery module 118 can manage the devices 102, 104, and 106, perform diagnostic data recovery, program the devices, and otherwise deliver information as needed. In some embodiments, the delivery module 118 can manage a web interface that can be accessed by patients or caregivers. The information gathered by an implanted device can be periodically transmitted to a web site that is securely accessible to the caregiver and/or patient in a timely manner. In other embodiments, a patient accesses detailed health information with diagnostic recommendations based upon analysis algorithms derived from leading health care institutions.
[0085] For example, the caregiver and/or patient can access the data and analysis performed on the data by accessing one or more general content providers. In one example, the patient's health information is accessed through a general portal such as My Yahoo provided by Yahoo! Inc. of Sunnyvale, Calif. A patient can access his or her My Yahoo homepage and receive information regarding current health and trends derived from the information gathered from the devices 102, 104, and 106, as well as other health information gathered from other sources. The patient may also access other information in addition to health information on the My Yahoo website, such as weather and stock market information. Other electronic delivery methods such as email, facsimile, etc. can also be used for alert distribution.
[0086] In an alternative embodiment, the data collected and integrated by the advanced patient system 100, as well as any analysis performed by the system 100, is delivered by delivery module 118 to a caregivers hospital computer system for access by the caregiver. A standard or custom interface facilitates communication between the advanced patient management system 100 and a legacy hospital system used by the caregiver so that the caregiver can access all relevant information using a system familiar to the caregiver.
[0087] The advanced patient management system 100 can also be configured so that various components of the system (e.g., ITU 108, communication system 110, and/or host 112) provide reporting to various individuals (e.g., patient and/or caregiver). For example, different levels of reporting can be provided by (1) the ITU 108 and (2) the host 112. The ITU 108 may be configured to conduct rudimentary analysis of data gathered from devices 102, 104, and 106, and provide reporting should an acute situation be identified. For example, if the ITU 108 detects that a significant heart arrhythmia is imminent or currently taking place, the ITU 108 provides reporting to the patient in the form of an audible or visual alarm.
[0088] The host 112 can provide a more sophisticated reporting system. For example, the host 112 can provide exception-based reporting and alerts that categorize different reporting events based on importance. Some reporting events do not require caregiver intervention and therefore can be reported automatically. In other escalating situations, caregiver and/or emergency response personnel need to become involved. For example, based on the data collected by the advanced patient management system 100, the delivery module 118 can communicate directly with the devices 102, 104, and 106, contact a pharmacy to order a specific medication for the patient, and/or contact 911 emergency response. In an alternative embodiment, the delivery module 118 and/or the patient may also establish a voice communication link between the patient and a caregiver, if warranted.
[0089] In addition to forms of reporting including visual and/or audible information, the advanced patient management system 100 can also communicate with and reconfigure one or more of the devices 102, 104, and 106. For example, if device 102 is part of a cardiac rhythm management system, the host 112 can communicate with the device 102 and reconfigure the therapy provided by the cardiac rhythm management system based on the data collected from one or more of the devices 102, 104, and 106. In another embodiment, the delivery module 118 can provide to the ITU 108 recorded data, an ideal range for the data, a conclusion based on the recorded data, and a recommended course of action. This information can be displayed on the ITU 108 for the patient to review or made available on the peripheral device 109 for the patient and/or clinician to review.
[0090] One or more headings have been provided above to assist in describing the various embodiments disclosed herein. The use of headings, and the resulting division of the description by the headings, should not be construed as limiting in any way. The subject matter described under one heading can be combined with subject matter described under one or more of the other headings without limitation and as desired.
Repeater Communications
[0091] FIG. 5 shows a patient 602 that has a medical device 604 coupled thereto. In this example, the medical device 604 is an implantable medical device such as a pacemaker. The medical device 604 communicates bi-directionally with a repeater device 610, such as an ITU 108 described above, by sending signals 606 to the repeater 610 and receiving signals 608 sent by the repeater 610. Signals 606, 608 can be achieved through inductive coupling, RF electromagnetic signaling, acoustic signaling, or other signaling methods known in the art. Furthermore, the signaling may occur wirelessly or through a wired connection, depending upon whether the device 604 is implanted or external to the patient's body 602.
[0092] Typically, an implanted medical device 604 will communicate using on-board telemetry as is known in the art. The onboard telemetry of the implanted medical device 604 performs a handshake with an external device such as the repeater device 610 to establish communications. The repeater device 610 interrogates the medical device 604 to retrieve data that the medical device 604 has been storing in on-board memory. For example, an implantable medical device 604 may store the number of times a particular cardiac episode has occurred since the last time the repeater device 610 downloaded the data.
[0093] The repeater device 610 captures the data and stores it in on-board memory, as discussed in greater detail below. Subsequently, the repeater device 610 transmits the data through a communication medium 612 to a data repository 614, such as an advanced patient management system maintaining a database of patient information as discussed above. The communication medium 612 and associated form of communication between the repeater device 610 and the repository 614 can take on various forms known in the art as discussed above in relation to the communication system 110 of FIGS. 1 and 4 .
[0094] For example, a public switched telephone network (PSTN) may be used whereby the repeater device 610 accesses the telephone line of the patient's home and places a call to a repository telephone number to establish the connection entirely through the PSTN. As one alternative, the repeater device 610 may utilize a dial-up connection or an always-on connection to an Internet Service Provider (ISP) where the repository 614 is accessible through the Internet. Additionally, as discussed above, the repeater device 610 may incorporate wireless communication abilities enabling the repeater device 610 to transmit data wirelessly to the PSTN or wireless Internet through a cellular base station.
[0095] As mentioned above, the communication between the repeater device 610 and the medical device 604 may be bi-directional so that the repeater device 610 can also send data to the medical device 604. Furthermore, the communication between the repeater device 610 and the repository 614 may be bi-directional. This enables the repeater device 610 to forward data from the medical device 604 to the repository 614 and also forward data from the repository 614 to the medical device 604.
[0096] For instance, the repeater device 610 may forward data from the medical device 604 to the repository 614. After analysis of the data at the repository 614, it may be determined that reprogramming of the medical device 604 is necessary to compensate for a change in the patient's condition. The new programming may then be transferred from the repository 614 through the repeater device 610 to the medical device 604 where it can be implemented.
[0097] FIG. 6 is a view of an exemplary repeater device 610. The repeater device 610 may include audio and/or visual annunciation abilities to communicate progress and or alerts to the patient 602. For example, a liquid crystal display (LCD) 704 may be included to provide a visual cue to the patient about progress of upload from the medical device 604 and the progress of download to the repository 614. Furthermore, LCD 704 may be used to provide instructions for use of the medical device 604 and/or repeater device 610 as well as alerts. Similarly, an audio speaker 702 may provide audible cues including progress reports and warnings to the patient 602. Various other types of annunciation may be employed as well, including light emitting diodes (LEDs), etc.
[0098] In some embodiments, the repeater device 610 may include intelligence for analyzing the data being retrieved from the medical device 604. For example, the repeater device 610 may include programming that analyzes the data for episodes of cardiac activity that are precursors to a serious cardiac event. In this case, the repeater device 610 may annunciate to the patient 602 that a visit to a physician is necessary and immediately notify the repository 614 of the emergency situation. Likewise, the data from the medical device 604 may indicate that the medical device 604 itself has a problem, such as a broken cardiac lead. The repeater device 610 may be programmed to recognize this condition from the retrieved data and annunciate to the patient 602 that a visit to the physician is necessary.
[0099] FIG. 7 is a view of the major components of the exemplary repeater device 610 of FIG. 5 . This repeater device 610 contains telemetry 802 that enables communication with a medical device 604, such as an implantable medical device (IMD). As discussed above, such telemetry 802 may employ inductive coupling techniques to wirelessly transmit data to and from the repeater device 610. RF communications are a wireless alternative to inductive coupling and provide better range between the medical device 604 and the repeater device 610. Wired connections from the medical device 604 to telemetry 802 are another alternative for medical devices 604 worn externally.
[0100] The telemetry 802 demodulates or otherwise recovers data from the signal from the medical device 604 and provides the data to the processor 808. Alternatively, the telemetry 802 provides the received signal to the processor 808 which then demodulates or otherwise recovers the data from the signal. The processor 808 stores the data in memory 812, such as random access memory (RAM) where it can later be accessed. In certain embodiments, the processor 808 may perform data analysis to determine the urgency of the data.
[0101] Data analysis by the repeater 610 may include analyzing raw data recorded by the medical device 604 to detect physiological conditions and specific episodes. Data analysis may also include interpreting data generated by the medical device 604 that signals such conditions and episodes, such as where the medical device 604 analyzes raw data to determine the conditions and episodes prior to sending the data to the repeater 610. Data analysis of raw data to determine physiological condition and specific episodes is well known in the art, but examples include detecting cardiac arrhythmias, conduction disorders, pulse rate, episodes of tachycardia or bradycardia, and other physiological conditions.
[0102] The processor 808 provides the data from memory 812 to an external communications device 806, such as a telephone line interface (modem), a wireless digital or analog RF transceiver, and/or an always-on Internet connection (i.e., cable or DSL modem). The external communications device 806 interfaces with the communication medium 612 to transfer the data to the repository 614. Data transfer may occur through techniques well known in the art, including standard modulation techniques, circuit switched connections, and/or packet switched connections as is appropriate. The external communications device 806 is also configurable to receive data from the repository 614 through the communication medium 612.
[0103] The processor 808 controls annunciation devices including the display circuit 804 and audio circuit 810 to provide information to the user 602. The display circuit 804 controls the LCD display 704 to provide visual information such as instructions for use, problems with the repeater 610 or medical device 604, or emergency alerts. Likewise, the audio circuit 810 controls the speaker 702 to provide audible information.
[0104] Logical operations of the processor 808 and its interaction with the various components shown in FIG. 7 are shown for several different embodiments in FIGS. 9-11 . These logical operations of the various embodiments are implemented (1) as a sequence of computer implemented acts or program modules and/or (2) as interconnected machine logic circuits or circuit modules. The implementation is a matter of choice dependent on the performance requirements of the repeater 610. Accordingly, the logical operations making up embodiments described herein are referred to variously as operations, structural devices, acts, or modules. It will be recognized by one skilled in the art that these operations, structural devices, acts and modules may be implemented in software, in firmware, in special purpose digital logic, and any combination thereof without deviating from the spirit and scope as recited within the claims attached hereto.
[0105] FIG. 8 shows exemplary logical operations where the repeater 610 considers the urgency of the data when coordinating the transfer of data to the repository 614. The operations begin with the processor 808 initiating communication with the medical device 604 through the telemetry 802 at communication operation 902. At data operation 904, the processor 808 retrieves the data through the telemetry 802 and stores the data in memory 812. At analysis operation 906, the processor 808 reviews the data to determine the degree of urgency. As discussed above, the processor 808 may review the data to determine whether the medical device 604 has found a specific condition or episode, or the processor 808 may employ its own analysis logic on the raw data recorded by the medical device 604 to find a specific condition or episode. In addition to or as an alternative to determining the degree of urgency based on analysis of the data, the processor may detect the degree of urgency by receiving input provided by a user. For example, the patient may press a button of the repeater that provides a signal to the processor 808 that the patient knows the data should be treated as urgent such as if a particular episode is occurring that the patient is aware of.
[0106] At query operation 908, the processor 808 detects from the analysis or otherwise whether the degree of urgency of the data indicates an emergency situation, such as where the data analysis shows that the user 602 needs immediate medical attention due to an imminent cardiac arrest or if the patient has indicated that the data is urgent. When the degree of urgency indicates an emergency situation, the repeater 610 proceeds to immediately initiate communication at communication operation 910. A notice of the emergency situation is transferred to the repository 614 at notice operation 912 to trigger an alarm so that repository personnel may take emergency action including dispatching paramedics to the user's location.
[0107] The repeater 610 also warns the user 602 of the emergency through visual and/or audible warnings at notice operation 914. The data stored in memory 812, including at least the data signaling the emergency situation, may then be transferred to the repository 614 at transfer operation 916. The repository personnel may then review the data to further assess the situation and assist paramedics.
[0108] If query operation 908 detects that there is no emergency, then query operation 918 tests whether the analyzed data indicates a problem. A problem may be detected from the data where the medical device 604 reports a malfunction, such as a broken cardiac lead, or reports other information that indicates the patient 602 should seek medical attention by some future point in time, although not immediately. If such a problem is detected, then the repeater 610 provides audible and/or visual notice of the problem to the user 602 at notice operation 920.
[0109] Once notice of the problem has been given to the user 602, or if query operation 918 detects no problem, then operational flow transitions to query operation 922 which detects whether it is an appropriate time to transfer data to the repository 614. For example, the repeater 610 may be configured so that transfers occur over a telephone line during low-activity periods such as 3 a.m. Other factors may be considered as well in addition to or as an alternative to the time of day. If query operation 922 detects that the proper time has arrived, then the processor 808 initiates communication with the repository 614 at communication operation 926. Data is then transferred to the repository 614 at transfer operation 928. If the proper time for transfer has not arrived, then the processor 808 waits out a delay 924, and then query operation 922 again detects whether the proper time has arrived.
[0110] FIG. 9 shows the logical operations where the repeater 610 considers the condition of the communication medium when coordinating transfer of data to the repository 614. The logical operations begin at communication operation 1002 where the repeater 610 initiates communication with the medical device 604. The repeater 610 retrieves the data from the medical device 604 and stores it in memory 812 at data operation 1004.
[0111] After the data has been obtained from the medical device 604, the repeater 610 checks the condition of the external communication medium 614 through interface 806 at test operation 1006. In this example, checking the condition of the communication medium 614 involves determining whether the telephone line is already in use. Other communication medium conditions may be determined as well. For example, if a wireless connection is being used to communicate with the repository 614, the strength of the wireless signal may be referenced to determine whether the signal is strong enough to communicate. As another example, if the Internet is being used to transfer data to the repository 614, the available bandwidth through the Internet connection may be determined to decide whether the data should be transferred.
[0112] The processor 808 may be configured so that test operation 1006 occurs as soon as the data has been retrieved or occurs at a later point in time, such as at a low-activity part of the day. After test operation 1006 has been performed, query operation 1008 detects whether the condition of the communication medium 614 is satisfactory. In this example, query operation 1008 detects whether the telephone line is in use. If so, the processor 808 stalls data transfer for a delay period 1010, and operational flow returns to test operation 1006 to again check the condition of the communication medium.
[0113] Once query operation 1008 detects that the telephone line is not in use, then communication operation 1012 initiates communication through the interface 806 with the repository 614. Once communication has been established, then data is transferred between the repeater device 610 and the repository 614 at transfer operation 1014.
[0114] FIG. 10 shows an example of logical operations of the repeater device 610 where both the urgency of the data and the condition of the communication medium are considered when coordinating data transfer to the repository 614. The operations begin with the processor 808 initiating communication with the medical device 604 through the telemetry 802 at communication operation 112. At data operation 1104, the processor 808 retrieves the data through the telemetry 802 and stores the data in memory 812. At analysis operation 1106, the processor 808 reviews the data to determine the degree of urgency.
[0115] At query operation 1108, the processor 808 detects from the analysis whether the degree of urgency of the data indicates an emergency situation, such as where the data analysis shows that the user 602 needs immediate medical attention due to an imminent cardiac arrest. When the degree of urgency indicates an emergency situation, the repeater 610 proceeds to immediately detect whether the telephone line is in use at query operation 1110. If so, then the telephone line interface 806 short circuits the telephone line to disconnect the current telephone call that is occupying the telephone line.
[0116] Once the telephone line has been freed or once query operation 1110 detects that the telephone line is not in use, the processor 808 initiates communication at communication operation 1114. A notice of the emergency situation is transferred to the repository 614 at notice operation 1116 to trigger an alarm so that repository personnel may take emergency action including dispatching paramedics to the user's location.
[0117] The repeater 610 also warns the user 602 of the emergency through visual and/or audible warnings at notice operation 1118. The data stored in memory 812, including at least the data signaling the emergency situation, may then be transferred to the repository 614 at transfer operation 1120. The repository personnel may then review the data to further assess the situation and assist paramedics.
[0118] If query operation 1108 detects that there is no emergency, then query operation 1122 tests whether the analyzed data indicates a problem. As discussed above, a problem may be detected from the data where the medical device 604 reports a malfunction, such as a broken cardiac lead, or reports other information that indicates the patient 602 should seek medical attention by some future point in time, although not immediately. If such a problem is detected, then the repeater 610 provides audible and/or visual notice of the problem to the user 602 at notice operation 1124.
[0119] Once notice of the problem has been given to the user 602, or if query operation 1122 detects no problem, then operational flow transitions to query operation 1126 which detects whether it is an appropriate time to transfer data to the repository 614, such as during a low-activity period. If query operation 1126 detects that the proper time for transfer has not arrived, then the processor 808 waits out a delay 1128, and then query operation 1126 again detects whether the proper time has arrived.
[0120] If query operation 1126 detects that the proper time has arrived, then query operation 1130 detects whether the telephone line is in use. If so, then the processor 808 stalls for a delay period 1132 and then again checks the telephone line at query operation 1130. If the telephone line is not in use, then the processor 808 initiates communication with the repository 614 at communication operation 1134. Data is then transferred to the repository 614 at transfer operation 1136.
[0121] The various embodiments described above are provided by way of illustration only and should not be construed to limit. Those skilled in the art will readily recognize various modifications and changes that may be made without following the example embodiments and applications illustrated and described herein, and without departing from the true spirit and scope, which is set forth in the following claims.
Claims
What is claimed is:
1. An auto-configurable repeater for remote patient care, comprising:
a store maintaining data exchanged with a patient medical device; and
a processor, comprising:
a plurality of interfaces to an external device, comprising a wireless interface and a wired interface;
a selection module automatically specifying one of the wireless interface and the wired interface based on conditions in respect of an associated communication medium that could affect data exchange; and
a transfer module to access the data in the store and to exchange the data with an external device over the specified interface.
2. An auto-configurable repeater according to Claim 1, further comprising:
a default interface comprising one of the wired interface and the wireless interface, which is specified prior to the exchange with the external device.
3. An auto-configurable repeater according to claim 2, wherein the default interface comprises the one of the wireless interface and the wired interface having a fastest data exchange rate.
4. An auto-configurable repeater according to claim 1, further comprising:
a further interface to the patient medical device; and
an interrogator module to exchange the data with the patient medical device over the further interface.
5. A method for providing auto-configurable data exchange for remote patient care, comprising:
maintaining data exchanged with a patient medical device;
providing a plurality of interfaces to an external device, comprising a wireless interface and a wired interface;
automatically specifying one of the wireless interface and the wired interface based on conditions in respect of an associated communication medium that could affect data exchange; and
exchanging the data with an external device over the specified interface.
6. A method according to claim 5, further comprising:
a default interface comprising one of the wired interface and the wireless interface, which is specified prior to the exchange with the external device.
7. A method according to claim 6, wherein the default interface comprises the one of the wireless interface and the wired interface having a fastest data exchange rate.
8. A method according to claim 5, further comprising:
a further interface to the patient medical device; and
an interrogator module to exchange the data with the patient medical device over the further interface.
9. A repeater providing data exchange with a medical device for remote patient care, comprising:
a plurality of interfaces, comprising:
a medical device interface interconnected with a medical device;
a wireless interface coupled to a wireless medium; and
a wired interface coupled to a wired medium;
an interface selector, comprising:
a test module operable over the wireless interface and the wired interface to evaluate conditions on each respective medium that could affect data exchange over each of the interfaces; and
a selection module specifying data exchange to occur using one of the wireless interface and the wired interface based on the evaluated conditions;
an interrogator module to exchange data with the medical device over the medical device interface; and
a data transfer module to exchange the data with an external device over the specified interface.
10. A repeater according to claim 9, further comprising:
a default interface comprising one of the wired interface and the wireless interface as specified prior to the exchange with the external device, wherein the other of the wired interface and the wireless interface is selected upon failure of the default interface to satisfy the evaluated conditions.
11. A repeater according to claim 9, further comprising modules for one or more of data store, data analysis, data forwarding, patient interaction, patient feedback, and data communications.
12. A repeater according to claim 9, wherein the data is exchanged with the medical device either periodically or on demand.
13. A repeater according to claim 9, further comprising at least one of:
an analysis module to perform analysis on the data and provide immediate feedback; and
a diagnostic module to perform self-diagnostic tests to verify proper functioning and that communication has not been compromised.
14. A repeater according to claim 9, wherein the conditions are selected from the group comprising availability of the communication medium, signal strength, and data transfer speed, and data transfer bandwidth.
15. A repeater according to claim 9, wherein the data is selected from the group comprising P-wave measurements, R-wave measurements, pacing, shocking events, lead impedances, pacing thresholds, battery voltage, capacitor charge times, ATR episodes with electrograms, tachycardia episodes with electrograms, and histogram information.
16. A repeater according to claim 9, wherein the wireless medium is selected from the group comprising cellular, satellite, radio frequency, and infrared media, and the wired medium is selected from the group comprising telephonic, DSL, broadband, and fiber optic media.
17. A method for providing data exchange with a medical device for remote patient care, comprising:
interconnecting a medical device interface to a medical device;
providing each of a wireless interface coupled to a wireless medium and a wired interface coupled to a wired medium;
evaluating conditions that could affect data exchange over each of the wireless interface and the wired interface;
specifying data exchange to occur using one of the wireless interface and the wired interface based on the evaluated conditions;
exchanging data with the medical device over the medical device interface; and
exchanging the data with an external device over the specified interface.
18. A method according to claim 17, further comprising:
specifying a default interface comprising one of the wired interface and the wireless interface as specified prior to the exchange with the external device; and
selecting the other of the wired interface and the wireless interface upon failure of the default interface to satisfy the evaluated conditions.
19. A method according to claim 17, further comprising:
providing one or more of data store, data analysis, data forwarding, patient interaction, patient feedback, and data communications.
20. A method according to claim 17, further comprising:
exchanging the data with the medical device either periodically or on demand.
21. A method according to claim 17, further comprising at least one of:
performing analysis on the data and provide immediate feedback; and
performing self-diagnostic tests to verify proper functioning and that communication has not been compromised.
22. A method according to claim 17, wherein the conditions are selected from the group comprising availability of the communication medium, signal strength, and data transfer speed, and data transfer bandwidth.
23. A method according to claim 17, wherein the data is selected from the group comprising P-wave measurements, R-wave measurements, pacing, shocking events, lead impedances, pacing thresholds, battery voltage, capacitor charge times, ATR episodes with electrograms, tachycardia episodes with electrograms, and histogram information.
24. A method according to claim 17, wherein the wireless medium is selected from the group comprising cellular, satellite, radio frequency, and infrared media, and the wired medium is selected from the group comprising telephonic, DSL, broadband, and fiber optic media.
Patent Citations (216)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4142533(A) | 1979-03-01 | Brownlee et al. | Applicant |
| US4531527(A) | 1985-07-01 | Reinhold, Jr. et al. | Applicant |
| US4658831(A) | 1987-04-01 | Reinhard et al. | Applicant |
| US4681111(A) | 1987-07-01 | Silvian | Applicant |
| US4686999(A) | 1987-08-01 | Snyder et al. | Applicant |
| US4705043(A) | 1987-11-01 | Imran | Applicant |
| US4757816(A) | 1988-07-01 | Ryan et al. | Applicant |
| US4793353(A) | 1988-12-01 | Borkan | Applicant |
| US4809697(A) | 1989-03-01 | Causey et al. | Applicant |
| US4852570(A) | 1989-08-01 | Levine | Applicant |
| US4932408(A) | 1990-06-01 | Schaldach | Applicant |
| US4947407(A) | 1990-08-01 | Silvian | Applicant |
| US4952928(A) | 1990-08-01 | Carroll | Applicant |
| US4958645(A) | 1990-09-01 | Cadell et al. | Applicant |
| US4969464(A) | 1990-11-01 | Callaghan et al. | Applicant |
| US4974607(A) | 1990-12-01 | Miwa | Applicant |
| US4987897(A) | 1991-01-01 | Funke | Applicant |
| US5040536(A) | 1991-08-01 | Riff | Applicant |
| US5058581(A) | 1991-10-01 | Silvian | Applicant |
| US5081987(A) | 1992-01-01 | Nigam | Applicant |
| US5113859(A) | 1992-05-01 | Funke | Applicant |
| US5113869(A) | 1992-05-01 | Nappholz et al. | Applicant |
| US5117825(A) | 1992-06-01 | Grevious | Applicant |
| US5133346(A) | 1992-07-01 | Kulkarni | Applicant |
| US5137022(A) | 1992-08-01 | Henry | Applicant |
| US5199428(A) | 1993-04-01 | Obel et al. | Applicant |
| US5241961(A) | 1993-09-01 | Henry | Applicant |
| US5292343(A) | 1994-03-01 | Blanchette et al. | Applicant |
| US5331549(A) | 1994-07-01 | Crawford, Jr. | Applicant |
| US5331966(A) | 1994-07-01 | Bennett et al. | Applicant |
| US5336245(A) | 1994-08-01 | Adams et al. | Applicant |
| US5350411(A) | 1994-09-01 | Ryan et al. | Applicant |
| US5355889(A) | 1994-10-01 | Nevo et al. | Applicant |
| US5357427(A) | 1994-10-01 | Langen et al. | Applicant |
| US5383915(A) | 1995-01-01 | Adams | Applicant |
| US5390238(A) | 1995-02-01 | Kirk et al. | Applicant |
| US5413594(A) | 1995-05-01 | Williams | Applicant |
| US5415181(A) | 1995-05-01 | Hogrefe et al. | Applicant |
| US5416695(A) | 1995-05-01 | Stutman et al. | Applicant |
| US5421343(A) | 1995-06-01 | Feng | Applicant |
| US5437278(A) | 1995-08-01 | Wilk | Applicant |
| US5438983(A) | 1995-08-01 | Falcone | Applicant |
| US5458122(A) | 1995-10-01 | Hethuin | Applicant |
| US5464012(A) | 1995-11-01 | Falcone | Applicant |
| US5476485(A) | 1995-12-01 | Weinberg et al. | Applicant |
| US5481262(A) | 1996-01-01 | Urbas et al. | Applicant |
| US5509927(A) | 1996-04-01 | Epstein et al. | Applicant |
| US5522865(A) | 1996-06-01 | Schulman et al. | Applicant |
| US5544661(A) | 1996-08-01 | Davis et al. | Applicant |
| US5549654(A) | 1996-08-01 | Powell | Applicant |
| US5553609(A) | 1996-09-01 | Chen et al. | Applicant |
| US5576952(A) | 1996-11-01 | Stutman | Applicant |
| US5584868(A) | 1996-12-01 | Salo et al. | Applicant |
| US5591215(A) | 1997-01-01 | Greenhut et al. | Applicant |
| US5603331(A) | 1997-02-01 | Heemels et al. | Applicant |
| US5626630(A) | 1997-05-01 | Markowitz et al. | Applicant |
| US5629678(A) | 1997-05-01 | Gargano et al. | Applicant |
| US5630836(A) | 1997-05-01 | Prem et al. | Applicant |
| US5660183(A) | 1997-08-01 | Chiang et al. | Applicant |
| US5674249(A) | 1997-10-01 | De Coriolis et al. | Applicant |
| US5683432(A) | 1997-11-01 | Goedeke et al. | Applicant |
| US5687734(A) | 1997-11-01 | Dempsey et al. | Applicant |
| US5697959(A) | 1997-12-01 | Poore | Applicant |
| US5704366(A) | 1998-01-01 | Tracklind et al. | Applicant |
| US5711297(A) | 1998-01-01 | Iliff | Applicant |
| US5713350(A) | 1998-02-01 | Yokota et al. | Applicant |
| US5713937(A) | 1998-02-01 | Nappholz et al. | Applicant |
| US5720770(A) | 1998-02-01 | Nappholz et al. | Applicant |
| US5720771(A) | 1998-02-01 | Snell | Applicant |
| US5724580(A) | 1998-03-01 | Levi et al. | Applicant |
| US5724983(A) | 1998-03-01 | Selker et al. | Applicant |
| US5738102(A) | 1998-04-01 | Lemelson | Applicant |
| US5741315(A) | 1998-04-01 | Lee et al. | Applicant |
| US5743267(A) | 1998-04-01 | Nicolic et al. | Applicant |
| US5749907(A) | 1998-05-01 | Mann | Applicant |
| US5749908(A) | 1998-05-01 | Snell | Applicant |
| US5752976(A) | 1998-05-01 | Duffin et al. | Applicant |
| US5752977(A) | 1998-05-01 | Grevious et al. | Applicant |
| US5766232(A) | 1998-06-01 | Grevious et al. | Applicant |
| US5769074(A) | 1998-06-01 | Barnhill et al. | Applicant |
| US5769876(A) | 1998-06-01 | Silvian | Applicant |
| US5772586(A) | 1998-06-01 | Heinonen et al. | Applicant |
| US5772604(A) | 1998-06-01 | Langberg et al. | Applicant |
| US5774501(A) | 1998-06-01 | Halpern et al. | Applicant |
| US5778882(A) | 1998-07-01 | Raymond et al. | Applicant |
| US5785650(A) | 1998-07-01 | Akasaka et al. | Applicant |
| US5791342(A) | 1998-08-01 | Woodard | Applicant |
| US5792062(A) | 1998-08-01 | Poon et al. | Applicant |
| US5792207(A) | 1998-08-01 | Dietrich | Applicant |
| US5814089(A) | 1998-09-01 | Stokes et al. | Applicant |
| US5819251(A) | 1998-10-01 | Kremer et al. | Applicant |
| US5836983(A) | 1998-11-01 | Weijand et al. | Applicant |
| US5843133(A) | 1998-12-01 | Routh et al. | Applicant |
| US5843139(A) | 1998-12-01 | Goedeke et al. | Applicant |
| US5855593(A) | 1999-01-01 | Olson et al. | Applicant |
| US5860918(A) | 1999-01-01 | Schradi et al. | Applicant |
| US5861014(A) | 1999-01-01 | Familoni | Applicant |
| US5861018(A) | 1999-01-01 | Feierbach | Applicant |
| US5876353(A) | 1999-03-01 | Riff | Applicant |
| US5879375(A) | 1999-03-01 | Larson, Jr. et al. | Applicant |
| US5891178(A) | 1999-04-01 | Mann et al. | Applicant |
| US5897493(A) | 1999-04-01 | Brown | Applicant |
| US5899928(A) | 1999-05-01 | Sholder et al. | Applicant |
| US5899931(A) | 1999-05-01 | Deschamp et al. | Applicant |
| US5911132(A) | 1999-06-01 | Sloane | Applicant |
| US5917414(A) | 1999-06-01 | Oppelt et al. | Applicant |
| US5919214(A) | 1999-07-01 | Ciciarelli et al. | Applicant |
| US5931857(A) | 1999-08-01 | Prieve | Applicant |
| US5935078(A) | 1999-08-01 | Feierbach | Applicant |
| US5944659(A) | 1999-08-01 | Flach et al. | Applicant |
| US5954640(A) | 1999-09-01 | Szabo | Applicant |
| US5957861(A) | 1999-09-01 | Combs et al. | Applicant |
| US5974124(A) | 1999-10-01 | Schlueter, Jr. et al. | Applicant |
| US5987352(A) | 1999-11-01 | Klein et al. | Applicant |
| US5999857(A) | 1999-12-01 | Weijand et al. | Applicant |
| US6024699(A) | 2000-02-01 | Surwit et al. | Applicant |
| US6047203(A) | 2000-04-01 | Sackner et al. | Applicant |
| US6050940(A) | 2000-04-01 | Braun | Applicant |
| US6067466(A) | 2000-05-01 | Selker | Applicant |
| US6073046(A) | 2000-06-01 | Patel | Applicant |
| US6080106(A) | 2000-06-01 | Lloyd et al. | Applicant |
| US6083248(A) | 2000-07-01 | Thompson | Applicant |
| US6093146(A) | 2000-07-01 | Filangeri | Applicant |
| US6095985(A) | 2000-08-01 | Raymond et al. | Applicant |
| US6102856(A) | 2000-08-01 | Groff et al. | Applicant |
| US6122351(A) | 2000-09-01 | Schlueter, Jr. et al. | Applicant |
| US6139494(A) | 2000-10-01 | Cairnes | Applicant |
| US6141584(A) | 2000-10-01 | Rockwell et al. | Applicant |
| US6155267(A) | 2000-12-01 | Nelson | Applicant |
| US6168563(B1) | 2001-01-01 | Brown | Applicant |
| US6170488(B1) | 2001-01-01 | Spillman, Jr. et al. | Applicant |
| US6171237(B1) | 2001-01-01 | Avitall et al. | Applicant |
| US6171256(B1) | 2001-01-01 | Joo et al. | Applicant |
| US6185452(B1) | 2001-02-01 | Schulman et al. | Applicant |
| US6200264(B1) | 2001-03-01 | Satherley et al. | Applicant |
| US6203495(B1) | 2001-03-01 | Bardy | Applicant |
| US6206835(B1) | 2001-03-01 | Spillman, Jr. et al. | Applicant |
| US6208894(B1) | 2001-03-01 | Schulman et al. | Applicant |
| US6213942(B1) | 2001-04-01 | Flach et al. | Applicant |
| US6216038(B1) | 2001-04-01 | Hartlaub et al. | Applicant |
| US6221011(B1) | 2001-04-01 | Bardy | Applicant |
| US6223078(B1) | 2001-04-01 | Marcovecchio | Applicant |
| US6223083(B1) | 2001-04-01 | Rosar | Applicant |
| US6225901(B1) | 2001-05-01 | Kail, IV | Applicant |
| US6236889(B1) | 2001-05-01 | Soykan et al. | Applicant |
| US6246992(B1) | 2001-06-01 | Brown | Applicant |
| US6249705(B1) | 2001-06-01 | Snell | Applicant |
| US6250309(B1) | 2001-06-01 | Krichen et al. | Applicant |
| US6261230(B1) | 2001-07-01 | Bardy | Applicant |
| US6263245(B1) | 2001-07-01 | Snell | Applicant |
| US6263246(B1) | 2001-07-01 | Goedeke et al. | Applicant |
| US6263247(B1) | 2001-07-01 | Mueller et al. | Applicant |
| US6270457(B1) | 2001-08-01 | Bardy | Applicant |
| US6287252(B1) | 2001-09-01 | Lugo | Applicant |
| US6289238(B1) | 2001-09-01 | Besson et al. | Applicant |
| US6290646(B1) | 2001-09-01 | Cosentino et al. | Applicant |
| US6292698(B1) | 2001-09-01 | Duffin et al. | Applicant |
| US6302844(B1) | 2001-10-01 | Walker | Applicant |
| US6304788(B1) | 2001-10-01 | Eady et al. | Applicant |
| US6319200(B1) | 2001-11-01 | Lai et al. | Applicant |
| US6329929(B1) | 2001-12-01 | Weijand et al. | Applicant |
| US6336900(B1) | 2002-01-01 | Alleckson | Applicant |
| US6345203(B1) | 2002-02-01 | Mueller et al. | Applicant |
| US6349234(B2) | 2002-02-01 | Pauly et al. | Applicant |
| US6363282(B1) | 2002-03-01 | Nichols et al. | Applicant |
| US6416471(B1) | 2002-07-01 | Kumar et al. | Applicant |
| US6418346(B1) | 2002-07-01 | Nelson et al. | Applicant |
| US6442432(B2) | 2002-08-01 | Lee | Applicant |
| US6442433(B1) | 2002-08-01 | Linberg | Applicant |
| US6454705(B1) | 2002-09-01 | Cosentino | Applicant |
| US6477242(B1) | 2002-11-01 | Freeny, Jr. | Applicant |
| US6477424(B1) | 2002-11-01 | Thompson et al. | Applicant |
| US6480745(B2) | 2002-11-01 | Nelson et al. | Applicant |
| US6485418(B2) | 2002-11-01 | Yasushi et al. | Applicant |
| US6497657(B2) | 2002-12-01 | Nunome | Applicant |
| US6544171(B2) | 2003-04-01 | Beetz et al. | Applicant |
| US6544173(B2) | 2003-04-01 | West et al. | Applicant |
| US6544174(B2) | 2003-04-01 | West et al. | Applicant |
| US6564104(B2) | 2003-05-01 | Nelson et al. | Applicant |
| US6569094(B2) | 2003-05-01 | Suzuki et al. | Applicant |
| US6577901(B2) | 2003-06-01 | Thompson | Applicant |
| US6599250(B2) | 2003-07-01 | Webb et al. | Applicant |
| US6602191(B2) | 2003-08-01 | Quy | Applicant |
| US6622050(B2) | 2003-09-01 | Thompson | Applicant |
| US6687547(B2) | 2004-02-01 | Goedeke et al. | Applicant |
| US6754538(B2) | 2004-06-01 | Linberg | Applicant |
| US6780156(B2) | 2004-08-01 | Haueter et al. | Applicant |
| US6804558(B2) | 2004-10-01 | Haller et al. | Applicant |
| US6824512(B2) | 2004-11-01 | Warkentin et al. | Applicant |
| US6827670(B1) | 2004-12-01 | Stark et al. | Applicant |
| US6893396(B2) | 2005-05-01 | Schulze et al. | Applicant |
| US6974413(B2) | 2005-12-01 | Bardy | Applicant |
| US7009511(B2) | 2006-03-01 | Mazar et al. | Examiner |
| US7027872(B2) | 2006-04-01 | Thompson | Applicant |
| US7058453(B2) | 2006-06-01 | Nelson et al. | Applicant |
| US7096067(B2) | 2006-08-01 | Linberg | Applicant |
| US7149773(B2) | 2006-12-01 | Haller et al. | Applicant |
| US7181505(B2) | 2007-02-01 | Haller et al. | Applicant |
| US7261690(B2) | 2007-08-01 | Teller et al. | Applicant |
| US7292139(B2) | 2007-11-01 | Mazar et al. | Examiner |
| US2001/0044588(A1) | 2001-11-01 | Mault | Applicant |
| US2002/0013538(A1) | 2002-01-01 | Teller | Applicant |
| US2002/0052539(A1) | 2002-05-01 | Haller et al. | Applicant |
| EP342859 | 1989-11-01 | Applicant | |
| EP513457 | 1992-11-01 | Applicant | |
| EP531889(A2) | 1993-03-01 | Applicant | |
| EP554955 | 1993-08-01 | Applicant | |
| EP711531(A1) | 1996-05-01 | Applicant | |
| JP2000-041957 | 2000-02-01 | Applicant | |
| JP2000-271097 | 2000-10-01 | Applicant | |
| JP2002-224053 | 2002-08-01 | Applicant | |
| JP2002-245167 | 2002-08-01 | Applicant | |
| JP2002-355305 | 2002-12-01 | Applicant | |
| WO97/39792 | 1997-10-01 | Applicant | |
| WO98/07142 | 1998-02-01 | Applicant | |
| WO99/46718 | 1999-09-01 | Applicant |
Non-Patent Literature (7)
- Moody GB, “Integration of Real-Time and Off-Line Clinical Data in the MIMIC Database,” Computers in Cardiology 1997 vol. 24, pp. 585-588, Cambridge, MA USA.Applicant
- Long WJ, et al., “Differential Diagnosis Generation From A Causal Network With Probabilities,” Computers in Cardiology, 1988, Proceedings, pp. 185-188, Washington DC, USA.Applicant
- W. Diffie, “The First Ten Years of Public-Key Cryptography,” Proceedings of the IEEE, vol. 76, No. 5, pp. 560-577 (May 1988).Applicant
- Supplementary European Search Report from EP Application No. 03813807, corresponding to U.S. Appl. No. 11/872,841, mailed Jun. 22, 2009, pp. 1-5.Applicant
- PCT International Search Report and Written Opinion from International Application No. PCT/US2003/40693, corresponding to U.S. Appl. No. 10/321,885, mailed Jul. 7, 2008, pp. 1-6.Applicant
- Official Action dated Oct. 7, 2009 (including English translation), in Japanese Patent Application No. 2004-562331 (English translation (3 pages) and the Japanese Official Action (2 pages)), where Japanese Patent Application No. 2004-562331 corresponds to U.S. Appl. No. 10/321,885 which is the parent to present U.S. Appl. No. 11/872,841.Applicant
- Official Communication from the European Patent Office for EP Patent Application No. 03813807.9, dated Oct. 27, 2009, which corresponds to U.S. Appl. No. 10/321,885, which is the parent application to the present U.S. Appl. No. 11/872,841 (7 pages).Applicant