This invention pertains to a system and method of correlating general patient health information and implant device data, and more particularly for correlating patient health information and cardiac rhythm management device data.
Implantable cardiac rhythm management devices (“CRM devices”) are well established therapeutic devices for treating patients who have experienced one or more documented episodes of hemodynamically significant ventricular tachycardia, ventricular fibrillation, bradycardia, or heart failure. Since their clinical inception more than two decades ago, CRM devices have evolved from basic to sophisticated electronic devices that provide physicians with a variety of clinically useful functions with which to treat patients.
Presently, even the most basic of CRM device typically has more than one tachycardia detection criterion, tiered therapy which combines bradycardia support pacing with various antitachycardia pacing modes, low-energy cardioversion, defibrillation, and data logging capabilities. The data logging capabilities within CRM devices have become increasingly important, since the amount of data required for the CRM device operation increases proportionally with the increase in CRM functions. Efficiently processing this large amount of data has become possible with the incorporation of microprocessors and memory within the CRM device.
Once a CRM device has been implanted, the physician interacts with the CRM device through a clinical programmer. The clinical programmer establishes a communication link with the implanted CRM device. The communication link allows instructions to be sent to the electronic circuitry of the CRM device and clinical data regarding the occurrence and treatment of a patient's cardiac arrhythmias and the CRM device's operation to be sent from the electronic circuitry of the CRM device to the clinical programmer. The typical programmer is a microprocessor-based unit that creates a communication link between the implanted CRM device and the programmer, and a graphics display screen that presents a patient's recorded cardiac data and CRM system information to the physician.
As the number of differing health data recorded by CRM device increases with each new generation of CRM device and the number of general patient health data increases, manufacturers and clinicians alike are becoming more sensitive to the role that time-efficient data interpretation plays in the physician's diagnosis of the patient. As CRM devices become increasingly complex, the interpretation of recorded arrhythmic episodes, operation of the CRM device, and the effect of changing a patient's therapy can be a challenging and time-consuming task.
Therefore, a need exists for improved CRM system and programmer technology that facilitates and correlates the identification of relevant information regarding the patient's clinical status. There is a need in the art for a system that correlates multiple data sets and displays same to the physician.
The present invention is generally directed to a system and method for presenting data from the CRM device simultaneously with patient health data and/or other patient data. The data so presented provides a physician with a visual display of more than one data set and thus the correlation between the data. Such a display may aid the physician in diagnosing and treating a patient.
Accordingly, one embodiment provides a cardiac rhythm management system including a cardiac rhythm management device and a programmer, the programmer being adapted to receive data from the cardiac rhythm management device. The programmer is adapted to correlate a first data set and a second data set for display to a physician. The first data set may be continuous, asynchronous or periodic data. The second data set may be asynchronous, continuous, or periodic data.
In another embodiment of the invention, the data is downloaded from the programmer into a data processor, which correlates the data. The correlated data is then output to a display device. One example of a data processor is a computer running appropriate software. One example of the display device is a computer monitor.
A further embodiment provides a display of the reoccurring first data against time and a second data imposed on the time axis to indicate a change in the patient's therapy. The second data may include changes to a patient's therapy including medication changes, medical device changes, or changes in operational parameters of a medical device.
Another embodiment provides a graphical display of data of the same type, which were recorded under different conditions, for example at different times or when the patient was under different treatment. The different circumstances are also displayed.
In another embodiment, the same type of data is heart rate variability data and the different circumstances may be the time at which the heart rate variability data was measured.
These and other embodiments, aspects, advantages, and features of the present invention will be set forth in part in the description which follows, and in part will become apparent to those skilled in the art by reference to the following description of the invention and referenced drawings or by practice of the invention. The aspects, advantages, and features of the invention are realized and attained by means of the instrumentalities, procedures, and combinations particularly pointed out in the appended claims.
In the following detailed description of the invention, reference is made to the accompanying drawings which form a part hereof, and in which is shown, by way of illustration, specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention. Other embodiments may be utilized and structural, logical, and electrical changes may be made without departing from the scope of the present invention.
The embodiments of the present invention illustrated herein are described as being included in a cardiac rhythm management device, e.g. an implantable cardiac defibrillator, pacemaker, or heart failure treatment device, which may include numerous pacing modes known in the art, and an external medical device programmer. The medical system and method of the present invention could also be implemented in an external cardioverter/monitor system as are known in the art. The medical system and method of the present invention could also be implemented in an implantable atrial cardioverter-defibrillator, which may include numerous pacing modes known in the art. Furthermore, although the present invention is described in conjunction with an implantable defibrillator having a microprocessor based architecture, it will be understood that the implantable cardiac defibrillator (or other implanted device) may be implemented in any logic based, custom integrated circuit architecture, if desired.
The intracardiac catheter 22 is implanted in a human body 24 with portions of the intracardiac catheter 22 inserted into a heart 26 or placed on the heart 26 to detect and analyze electric cardiac signals produced by the heart 26 and to provide electrical energy to the heart 26 under certain predetermined conditions to treat cardiac arrhythmias of the heart 26, including ventricular fibrillation, bradycardia and/or heart failure.
In one embodiment, the intracardiac catheter 22 is an endocardial lead adapted to be releasably attached to CRM device 20. The intracardiac catheter 22 has an elongate body with a proximal end 28 and a distal end 30 and is shown as having a pacing electrode 32 located at, or adjacent, the distal end 30 of intracardiac catheter 22. In one embodiment, the pacing electrode 32 is a tip electrode positioned at the distal end 30 of intracardiac catheter 22. Alternatively, pacing electrode 32 is an annular, or a semi-annular ring electrode positioned adjacent the distal end 30.
The intracardiac catheter 22 also includes one or more defibrillation electrodes. In one embodiment, the intracardiac catheter 22 has a first defibrillation electrode 34 and a second defibrillation electrode 36, where the first defibrillation electrode 34 and the second defibrillation electrode 36 are defibrillation coil electrodes. The first defibrillation electrode 34 is spaced apart and proximal to the pacing electrode 32, and the second defibrillation electrode 36 is spaced apart and proximal to the first defibrillation electrode 34 such that when the intracardiac catheter 22 is positioned within the heart 26, the pacing electrode 32 and first defibrillation electrode 34 reside within a right ventricle 38 of the heart 26, with pacing electrode 32 in an apex location within the right ventricle 38, and second defibrillation electrode 36 is positioned within the right atrium chamber 40 of heart 26 or a major vein leading to right atrium chamber 40 of heart 26. The description of catheter 22 is but one example of various leads, known to one of skill in the art, that will work with the present invention. As a further example CRM device 20 may be connected to a plurality of leads.
In one embodiment, electronic control circuitry 42 of CRM device 20 is encased and hermetically sealed in a housing 50 suitable for implanting in a human body. In one embodiment, titanium is used for the housing 50, however, other biocompatible housing materials as are known in the art may be used. A connector block 52 is additionally attached to the housing 50 of CRM device 20 to allow for the physical and the electrical attachment of the intracardiac catheter 22 and the electrodes to CRM device 20 and the encased electronic control circuitry 42 (
Electronic control circuitry 42 is a programmable microprocessor-based system, with a microprocessor 54 and a memory circuit 56, which contains parameters for various pacing and sensing modes (
Electronic control circuitry 42 further includes transmitter circuit 58 which is coupled to memory circuit 56 to allow the CRM device 20 to communicate with a programmer unit 60. In one embodiment, transmitter circuit 58 and programmer unit 60 use a wire loop antenna 62 and a radio frequency telemetric link to receive and transmit signals and data to and from the programmer unit 60 and the electronic control circuitry 42. In another embodiment, the transmitter circuit 58 includes inductive coils to bidirectionally transmit signals and data between programmer unit 60 and electronic control circuitry 42. In these manners, programming commands or instructions are transferred to the microprocessor 54 of CRM device 20 after implant, and stored cardiac data pertaining to patient health, including sensed arrhythmic episodes within the heart 26, and subsequent therapy, or therapies, applied to correct sensed arrhythmic events are transferred to programmer unit 60 from CRM device 20. It is within the scope of the present invention to transmit any data stored in CRM device 20 to programmer unit 60 so the data can be analyzed and used by a physician to diagnose and evaluate the efficacy of the therapy.
Pacing electrode 32 is coupled to a sense amplifier 64 through terminal 44 in the
First defibrillation electrode 34 and second defibrillation electrode 36 are coupled to a sense amplifier 70, whose output is connected to a cardiac morphology detector 72. These components serve to sense and amplify the QRS-waves of the cardiac cycle from the ventricular region of the heart 26, and apply signals indicative thereof to the microprocessor 54. In one embodiment, the cardiac morphology detector 72 includes an analog filter for filtering cardiac signal noise sensed by the electrodes. The cardiac signals are then band limited before arriving at an analog-to-digital filter. The cardiac signals are then A/D converted into a digital signal and subsequently received by microprocessor 54. In an alternative embodiment, the cardiac signals are filtered through an analog peak detector to extract the maximum and minimum cardiac signal values for each sensed cardiac interval.
Microprocessor 54 responds to the cardiac signals sensed within the heart 26 using the intracardiac catheter 22 by providing signals to cardioversion/defibrillation output circuitry 74 to provide either cardioversion or defibrillation electrical energy to the heart 26 depending upon nature of an arrhythmia sensed by CRM device 20. Power to CRM device 20 is supplied by an electrochemical battery 76 that is housed within CRM device 20.
While the illustrative embodiment show in
Referring now to
Medical device programmer 60 is designed to be positioned external of the human body 24 for communicating with an implantable medical device, such as CRM device 20 from
In one embodiment, the medical device programmer 60 comprises an outer housing 100 which is made of a thermal plastic or other suitable lightweight durable material. The graphics display screen 102 is disposed on the upper surface of housing 100. The graphics display screen 102 folds down into a closed position when medical device programmer 60 is not in use, thereby reducing the size of medical device programmer 60 and protecting the display surface of graphics display screen 102 during transportation and storage. In an additional embodiment, the external programmer additionally has a floppy disk drive and a hard drive disposed within the housing.
The medical device programmer 60 is shown with the graphics display screen 102 positioned in one of a plurality of possible open positions such that a display on the graphics display screen 102 is visible to a user situated in front of medical device programmer 60. In one embodiment, the graphics display screen 102 is of a CRT, LCD or electroluminescent type. The graphics display screen 102 is operatively coupled to the electronic circuitry disposed with the housing 100 and is adapted to provide a visual display of graphics and/or data under control of the programmer electronic circuitry, e.g. processor. It is within the scope of the present invention to provide programmer 60 with a video output connection to which a non-integral monitor can be connected.
Medical device programmer 60 further includes a user input device coupled to the electronic circuitry. In one embodiment, the user input device is the graphics display screen 102, which is provided with touch-sensitive capability, such that a user can interact with the programmer electronic circuitry by touching the display area on the graphics display screen 102 with a finger (not shown) or a stylus 104. In one embodiment, the touch-sensitive graphics display screen is primary input for the medical device programmer 60. The medical device programmer 60 further includes a programming head 106, which is place over a patient's body near the implant site of an implanted device, such as CRM device 20, in order to establish a communication link between CRM device 20 and programmer 60. The telemetry link between CRM device 20 and programmer 60 allows the electronic circuitry of programmer 60 to be coupled to the electronic control circuitry of the CRM device 20. The programming head 106 is coupled to the electronic circuitry of medical device programmer 60 and a receiver circuit for receiving signals from the transmitter circuit indicative of cardiac signals by a cable 108. In one embodiment, a communication system 70 is intermediate programmer 60 and CRM device 20, for example the telephone system or a computer network such as a LAN, WAN, or global computer network (e.g. internet). Consequently, the programmer 60 remotely monitors and receives data from the CRM device 20.
In one embodiment of the invention, the stylus 104 used to interact with the touch-sensitive graphics display screen 102 is coupled to the programmer electronic circuitry within the housing 100 by a cable 110. In another embodiment of the invention, only a touch sensitive screen 102 is provided which is activated by a user's finger touching the screen. Alternatively, medical device programmer 60 may be equipped with a conventional computer “mouse”-type pointing device, rather than a stylus or a touch sensitive screen which is actuatable by a user's finger. In the absence of either a stylus, touch-sensitive screen or a mouse, on-screen cursor control for enabling user interaction with medical device programmer 60 may be facilitated through cursor control keys 112 (arrow keys or the like) disposed on medical device programmer 60.
Medical device programmer 60 further includes a receiver circuit for receiving signals from the transmitter circuit indicative of cardiac signals. Through the communication link with CRM device 20, the medical device programmer 60 is capable of capturing and storing recorded data transmitted from CRM device 20 and displaying the data on its graphics display screen 102. Programmer 60 compiles data into numerous forms for display on graphics display screen 102, such forms include charts and graphs, for example those shown in
In one embodiment, programmer 60 downloads the data it receives from CRM device 20 to a computer system 80 (
While the above describes one embodiment of a medical system in which the present invention can be incorporated, it will be understood that the present invention can be incorporated into numerous CRM devices and programmers. Therefore, it will be understood by those of skill in the art that the present invention can be adapted for use with other types of CRM devices, examples of such devices are found in U.S. Pat. Nos. 6,112,117; 6,108,577; 6,091,990; 6,076,015; 6,067,471; 6,016,446; and 5,978,707, all assigned to the present assignee, and all herein incorporated in their entirety by reference. It will also be understood by those of skill in the art that the present invention can be adapted for use with other types of programmers.
The physician can now ascertain the effect the events 510 and 520 had on patient's health which is represented by the selected patient health data on the Y-axis. Events 510 and 520 can represent the same type of event, for example, changes in accelerometer response factor, lower rate limit, brady pacing parameters, etc. Events 510 and 520 can also represent two different type of events such the graph shows the effect on the patient health data of the first event 510 and the effect on the patient health data of the different, second event 520, such as a drug therapy change or a programmed parameter change in CRM device 20.
Specific examples of the graphs produced by the described embodiment of the system will now be described in conjunction with
In another embodiment, different representations of bar 60, for example different colors, hatching, etc., represent when the change in ventricular sensitivity occurred. In one embodiment, vertical hatching of bar 610 represents changing ventricular sensitivity (second data) after the number of shocks (first data) were recorded. In one embodiment, horizontal hatching of bar 610 represents changing ventricular sensitivity (second data) before the number of shocks (first data) were recorded. Accordingly, the physician can visualize the effect the change in ventricular sensitivity had on the number of shocks administered to the patient's heart. In the illustrated embodiment of
Therapy history as stored in memory 56 of CRM device 20 and downloaded to programmer 60 further includes patient activity data and which chambers of the patient's heart required pacing at specific times. Patient activity data is a measurement of the percent of a fixed time period, e.g. a day, at which a patient reaches an activity threshold, e.g. time patient has a heart rate above a predetermined threshold value such as beats per minute threshold value. The programmer, when instructed by a physician to do so, displays a graph of the patient's activity versus time (
In the illustrated
It will be recognized that it is within the scope of the present invention to select the data and/or parameters simultaneously displayed so that the display will be of most use to a physician when interpreting the displayed data. For example, the activity data display 1100 could be selected to display with the heart rate trend display 1010. Such a selection of data displays provides the physician with a tool which assists in quick and accurate interpretation of the data measured by CRM device 20 and parameters programmed into CRM device 20. Thus, the display of data and/or parameters according to the present invention includes simultaneously displaying measured data with other measured data and events, measured data with programmable parameters, and programmable parameters with other programmable parameters. Moreover, the measured data includes both synchronous data, periodic data, and asynchronous data. It will be appreciated that various combinations of data types and parameters can be simultaneously displayed.
While many of the embodiments described herein and shown in the drawings display data in a specific format, it will be understood that other formats are within the scope of the present invention. Such other formats include changing the display color, if a color display is available, or changing the grey-scale, if only a monochrome display is available, for first data before and after an event or in the presence of second data correlated to the first data. Other formats further include different cross-hatching and different line types. Nevertheless, each of the data formats provides the viewer with visual indication of a change in data or a change in the environment in which the data was recorded.
Although the invention has been described in conjunction with the foregoing specific embodiments, many alternatives, variations, and modifications will be apparent to those of ordinary skill in the art. Such alternatives, variations, and modifications are intended to fall within the scope of the following appended claims. For example, the CRM system controls a large number of programmable parameters of the CRM device and stores a large number of CRM device performance data sets and sensed patient health data. It will be understood that the above described embodiments are examples and numerous correlations of data, data and parameter, etc. are within the scope of the present invention.
This application is a continuation of U.S. patent application Ser. No. 13/411,063, filed on Mar. 2, 2012, now issued as U.S. Pat. No. 8,548,576, which is a continuation of U.S. patent application Ser. No. 12/941,377, filed on Nov. 8, 2010, now issued as U.S. Pat. No. 8,131,351, which is a continuation of U.S. patent application Ser. No. 11/379,912, filed on Apr. 24, 2006, now issued as U.S. Pat. No. 7,844,322, which is a continuation of U.S. patent application Ser. No. 10/687,433, filed on Oct. 16, 2003, now issued as U.S. Pat. No. 7,047,065, which is a continuation of U.S. patent application Ser. No. 09/738,869, filed on Dec. 15, 2000, now issued as U.S. Pat. No. 6,665,558, the specifications of which areincorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
4006737 | Cherry | Feb 1977 | A |
4090505 | Mortara | May 1978 | A |
4166470 | Neumann | Sep 1979 | A |
4172459 | Hepp | Oct 1979 | A |
4187854 | Hepp et al. | Feb 1980 | A |
4197850 | Schulman et al. | Apr 1980 | A |
4223678 | Langer et al. | Sep 1980 | A |
4232679 | Schulman | Nov 1980 | A |
4236524 | Powell et al. | Dec 1980 | A |
4316249 | Gallant et al. | Feb 1982 | A |
4336810 | Anderson et al. | Jun 1982 | A |
4364397 | Citron et al. | Dec 1982 | A |
4407288 | Langer et al. | Oct 1983 | A |
4509530 | Curtis et al. | Apr 1985 | A |
4527567 | Fischler et al. | Jul 1985 | A |
4529401 | Leslie et al. | Jul 1985 | A |
4531527 | Reinhold, Jr. et al. | Jul 1985 | A |
4549552 | Groch et al. | Oct 1985 | A |
4596255 | Snell et al. | Jun 1986 | A |
4601291 | Boute et al. | Jul 1986 | A |
4680708 | Ambos et al. | Jul 1987 | A |
4791936 | Snell et al. | Dec 1988 | A |
4800883 | Winstrom | Jan 1989 | A |
4802491 | Cohen et al. | Feb 1989 | A |
4809697 | Causey, III et al. | Mar 1989 | A |
4825869 | Sasmor et al. | May 1989 | A |
4850357 | Bach, Jr. | Jul 1989 | A |
4944298 | Sholder | Jul 1990 | A |
4947857 | Albert et al. | Aug 1990 | A |
4958632 | Duggan | Sep 1990 | A |
4964410 | Leahey et al. | Oct 1990 | A |
4974598 | John | Dec 1990 | A |
4979506 | Silvian | Dec 1990 | A |
4989610 | Patton et al. | Feb 1991 | A |
4998531 | Bocchi et al. | Mar 1991 | A |
5000189 | Throne et al. | Mar 1991 | A |
5012814 | Mills et al. | May 1991 | A |
5027824 | Dougherty et al. | Jul 1991 | A |
5046504 | Albert et al. | Sep 1991 | A |
5047930 | Martens et al. | Sep 1991 | A |
5050612 | Matsumura | Sep 1991 | A |
5052395 | Burton et al. | Oct 1991 | A |
5111816 | Pless et al. | May 1992 | A |
5113869 | Nappholz et al. | May 1992 | A |
5129392 | Bardy et al. | Jul 1992 | A |
5184614 | Collins et al. | Feb 1993 | A |
5193550 | Duffin | Mar 1993 | A |
5209228 | Cano et al. | May 1993 | A |
5213098 | Bennett et al. | May 1993 | A |
5215083 | Drane et al. | Jun 1993 | A |
5217021 | Steinhaus et al. | Jun 1993 | A |
5224475 | Berg et al. | Jul 1993 | A |
5273049 | Steinhaus et al. | Dec 1993 | A |
5279293 | Andersen et al. | Jan 1994 | A |
5292341 | Snell | Mar 1994 | A |
5299118 | Martens et al. | Mar 1994 | A |
5309919 | Snell et al. | May 1994 | A |
5311873 | Savard et al. | May 1994 | A |
5311874 | Baumann et al. | May 1994 | A |
5312441 | Mader et al. | May 1994 | A |
5315512 | Roth | May 1994 | A |
5341811 | Cano | Aug 1994 | A |
5342402 | Olson et al. | Aug 1994 | A |
5344430 | Berg et al. | Sep 1994 | A |
5357969 | Herleikson | Oct 1994 | A |
5391188 | Nelson et al. | Feb 1995 | A |
5402794 | Wahlstrand et al. | Apr 1995 | A |
5404877 | Nolan et al. | Apr 1995 | A |
5404880 | Throne | Apr 1995 | A |
5411530 | Akhtar | May 1995 | A |
5413594 | Williams | May 1995 | A |
5417714 | Levine et al. | May 1995 | A |
5421830 | Epstein et al. | Jun 1995 | A |
5423871 | Hoegnelid et al. | Jun 1995 | A |
5431692 | Hansen et al. | Jul 1995 | A |
5458623 | Lu et al. | Oct 1995 | A |
5464433 | White et al. | Nov 1995 | A |
5476485 | Weinberg et al. | Dec 1995 | A |
5487754 | Snell et al. | Jan 1996 | A |
5487755 | Snell et al. | Jan 1996 | A |
5496351 | Plicchi et al. | Mar 1996 | A |
5507786 | Morgan et al. | Apr 1996 | A |
5511553 | Segalowitz | Apr 1996 | A |
5513645 | Jacobson et al. | May 1996 | A |
5535753 | Petrucelli et al. | Jul 1996 | A |
5549646 | Katz et al. | Aug 1996 | A |
5549654 | Powell | Aug 1996 | A |
5555888 | Brewer et al. | Sep 1996 | A |
5578063 | Bocek et al. | Nov 1996 | A |
5584298 | Kabal | Dec 1996 | A |
5586556 | Spivey et al. | Dec 1996 | A |
5591214 | Lu | Jan 1997 | A |
5603331 | Heemels et al. | Feb 1997 | A |
5607460 | Kroll et al. | Mar 1997 | A |
5609612 | Plicchi et al. | Mar 1997 | A |
5609615 | Sanders et al. | Mar 1997 | A |
5613495 | Mills et al. | Mar 1997 | A |
5620474 | Koopman | Apr 1997 | A |
5626620 | Kieval et al. | May 1997 | A |
5626623 | Kieval et al. | May 1997 | A |
5628321 | Scheib et al. | May 1997 | A |
5628776 | Paul et al. | May 1997 | A |
5643255 | Organ | Jul 1997 | A |
5647369 | Petrucelli et al. | Jul 1997 | A |
5653737 | van Lake | Aug 1997 | A |
5674249 | De Coriolis et al. | Oct 1997 | A |
5683431 | Wang | Nov 1997 | A |
5687737 | Branham et al. | Nov 1997 | A |
5693075 | Plicchi et al. | Dec 1997 | A |
5697959 | Poore | Dec 1997 | A |
5709712 | Paul et al. | Jan 1998 | A |
5713366 | Armstrong et al. | Feb 1998 | A |
5716383 | Kieval et al. | Feb 1998 | A |
5716384 | Snell | Feb 1998 | A |
5722999 | Snell | Mar 1998 | A |
5724985 | Snell et al. | Mar 1998 | A |
5732708 | Nau et al. | Mar 1998 | A |
5743268 | Kabal | Apr 1998 | A |
5749900 | Schroeppel et al. | May 1998 | A |
5749906 | Kieval et al. | May 1998 | A |
5749907 | Mann | May 1998 | A |
5755742 | Schuelke et al. | May 1998 | A |
5759196 | Hess et al. | Jun 1998 | A |
5759199 | Snell et al. | Jun 1998 | A |
5772604 | Langberg et al. | Jun 1998 | A |
5782890 | Wahlstrand et al. | Jul 1998 | A |
5788640 | Peters | Aug 1998 | A |
5792203 | Schroeppel | Aug 1998 | A |
5792204 | Snell | Aug 1998 | A |
5792207 | Dietrich | Aug 1998 | A |
5814083 | Hess et al. | Sep 1998 | A |
5814088 | Paul et al. | Sep 1998 | A |
5817137 | Kaemmerer | Oct 1998 | A |
5833623 | Mann et al. | Nov 1998 | A |
5876353 | Riff | Mar 1999 | A |
5891043 | Ericksen et al. | Apr 1999 | A |
5891178 | Mann et al. | Apr 1999 | A |
5891179 | Er et al. | Apr 1999 | A |
5897577 | Cinbis et al. | Apr 1999 | A |
5924989 | Polz | Jul 1999 | A |
5925067 | Lu | Jul 1999 | A |
5948005 | Valikai et al. | Sep 1999 | A |
5951484 | Hoium et al. | Sep 1999 | A |
5954664 | Seegobin | Sep 1999 | A |
5957861 | Combs et al. | Sep 1999 | A |
5961467 | Shimazu et al. | Oct 1999 | A |
5974341 | Er et al. | Oct 1999 | A |
5978707 | Krig et al. | Nov 1999 | A |
6004276 | Wright et al. | Dec 1999 | A |
6007493 | Ericksen et al. | Dec 1999 | A |
6016442 | Hsu et al. | Jan 2000 | A |
6016446 | Belalcazar | Jan 2000 | A |
6016447 | Juran et al. | Jan 2000 | A |
6016448 | Busacker et al. | Jan 2000 | A |
6017307 | Raines | Jan 2000 | A |
6035233 | Schroeppel et al. | Mar 2000 | A |
6050950 | Mohler | Apr 2000 | A |
6067471 | Warren | May 2000 | A |
6076015 | Hartley et al. | Jun 2000 | A |
6091990 | Hsu et al. | Jul 2000 | A |
6095984 | Amano et al. | Aug 2000 | A |
6101415 | Er et al. | Aug 2000 | A |
6108577 | Benser | Aug 2000 | A |
6112117 | KenKnight et al. | Aug 2000 | A |
6122536 | Sun et al. | Sep 2000 | A |
6240317 | Villaseca et al. | May 2001 | B1 |
6243606 | Mann et al. | Jun 2001 | B1 |
6253102 | Hsu et al. | Jun 2001 | B1 |
6263244 | Mann et al. | Jul 2001 | B1 |
6264614 | Albert et al. | Jul 2001 | B1 |
6289244 | Conley et al. | Sep 2001 | B1 |
6289248 | Conley et al. | Sep 2001 | B1 |
6301503 | Hsu et al. | Oct 2001 | B1 |
6308095 | Hsu et al. | Oct 2001 | B1 |
6311089 | Mann et al. | Oct 2001 | B1 |
6312378 | Bardy | Nov 2001 | B1 |
6345200 | Mouchawar et al. | Feb 2002 | B1 |
6415175 | Conley et al. | Jul 2002 | B1 |
6418340 | Conley et al. | Jul 2002 | B1 |
6438407 | Ousdigian et al. | Aug 2002 | B1 |
6449504 | Conley et al. | Sep 2002 | B1 |
6459929 | Hopper et al. | Oct 2002 | B1 |
6459934 | Kadhiresan | Oct 2002 | B1 |
6477404 | Yonce et al. | Nov 2002 | B1 |
6535763 | Hiebert et al. | Mar 2003 | B1 |
6580948 | Haupert et al. | Jun 2003 | B2 |
6665558 | Kalgren et al. | Dec 2003 | B2 |
6718198 | Conley et al. | Apr 2004 | B2 |
6721594 | Conley et al. | Apr 2004 | B2 |
6843801 | Conley et al. | Jan 2005 | B2 |
6941167 | Stahmann et al. | Sep 2005 | B2 |
7047065 | Kalgren et al. | May 2006 | B2 |
7117037 | Hiebert et al. | Oct 2006 | B2 |
7406348 | Stahmann et al. | Jul 2008 | B2 |
7418295 | Conley et al. | Aug 2008 | B2 |
7844322 | Kalgren et al. | Nov 2010 | B2 |
7962203 | Conley et al. | Jun 2011 | B2 |
8032208 | Stahmann et al. | Oct 2011 | B2 |
8131351 | Kalgren et al. | Mar 2012 | B2 |
8463369 | Conley et al. | Jun 2013 | B2 |
8548576 | Kalgren et al. | Oct 2013 | B2 |
20020077859 | Stahmann et al. | Jun 2002 | A1 |
20020151809 | Conley et al. | Oct 2002 | A1 |
20030114891 | Hiebert et al. | Jun 2003 | A1 |
20040082976 | Kalgren et al. | Apr 2004 | A1 |
20050107840 | Conley et al. | May 2005 | A1 |
20050187588 | Stahmann et al. | Aug 2005 | A1 |
20060189877 | Kalgren et al. | Aug 2006 | A1 |
20080269827 | Stahmann et al. | Oct 2008 | A1 |
20090036942 | Conley et al. | Feb 2009 | A1 |
20110046692 | Kalgren et al. | Feb 2011 | A1 |
20110238127 | Conley et al. | Sep 2011 | A1 |
20120016250 | Stahmann et al. | Jan 2012 | A1 |
20120165883 | Kalgren et al. | Jun 2012 | A1 |
Number | Date | Country |
---|---|---|
0491649 | Jun 1992 | EP |
0558353 | Sep 1993 | EP |
0565084 | Oct 1993 | EP |
0711531 | May 1996 | EP |
0850661 | Jul 1998 | EP |
WO-9927992 | Jun 1999 | WO |
Entry |
---|
“U.S. Appl. No. 09/372,157, Non-Final Office Action mailed Apr. 25, 2001”, 9 pgs. |
“U.S. Appl. No. 09/372,157, Notice of Allowance mailed Feb. 12, 2002”, 5 pgs. |
“U.S. Appl. No. 09/372,157, Notice of Allowance mailed Sep. 7, 2001”, 6 pgs. |
“U.S. Appl. No. 09/372,157, Request for Continued Examination filed Dec. 7, 2001”, 8 pgs. |
“U.S. Appl. No. 09/372,157, Response filed Mar. 20, 2001 to Restriction Requirement mailed Feb. 20, 2001”, 1 pg. |
“U.S. Appl. No. 09/372,157, Response filed Jul. 25, 2001 to Non-Final Office Action mailed Apr. 25, 2001”, 13 pgs. |
“U.S. Appl. No. 09/372,157, Restriction Requirement mailed Feb. 20, 2001”, 4 pgs. |
“U.S. Appl. No. 09/378,030, Restriction Requirement mailed May 9, 2001”, 4 pgs. |
“U.S. Appl. No. 09/378,406, Non Final Office Action mailed Apr. 27, 2001”, 6 pgs. |
“U.S. Appl. No. 09/378,406, Non-Final Office Action mailed Apr. 27, 2001”, 5 pgs. |
“U.S. Appl. No. 09/378,406, Notice of Allowance mailed Feb. 12, 2002”, 6 pgs. |
“U.S. Appl. No. 09/378,406, Notice of Allowance mailed Aug. 23, 2001”, 6 pgs. |
“U.S. Appl. No. 09/378,406, Response filed Jul. 27, 2001 to Non-Final Office Action mailed Apr. 27, 2001”, 16 pgs. |
“U.S. Appl. No. 09/382,154, Non Final Office Action mailed Apr. 16, 2002”, 5 pgs. |
“U.S. Appl. No. 09/382,154, Non Final Office Action mailed Oct. 16, 2000”, 7 pgs. |
“U.S. Appl. No. 09/382,154, Notice of Allowance mailed Sep. 28, 2001”, 4 pgs. |
“U.S. Appl. No. 09/382,154, Notice of Allowance mailed Oct. 11, 2002”, 5 pgs. |
“U.S. Appl. No. 09/382,154, Response filed Feb. 15, 2001 to Non-Final Office Action mailed Oct. 16, 2000”, 4 pgs. |
“U.S. Appl. No. 09/382,154, Response filed Jul. 15, 2002 to Non-Final Office Action mailed Apr. 16, 2002”, 9 pgs. |
“U.S. Appl. No. 09/382,292, Amendment filed Dec. 12, 2001”, 5 pgs. |
“U.S. Appl. No. 09/382,292, Application filed Aug. 24, 1999”, 29 pgs. |
“U.S. Appl. No. 09/382,292, Notice of Allowance mailed Feb. 28, 2002”, 4 pgs. |
“U.S. Appl. No. 09/382,292, Notice of Allowance mailed Aug. 27, 2001”, 6 pgs. |
“U.S. Appl. No. 09/382,292, Preliminary Amendment filed Aug. 9, 2000”, 2 pgs. |
“U.S. Appl. No. 09/382,292, Response filed Jul. 12, 2001 to Restriction Requirement mailed Jul. 5, 2001”, 1 pg. |
“U.S. Appl. No. 09/382,292, Restriction Requirement mailed Jul. 5, 2001”, 4 pgs. |
“U.S. Appl. No. 09/572,410, Notice of Allowance mailed Jan. 25, 2001”, 4 pgs. |
“U.S. Appl. No. 09/572,410, Preliminary Amendment filed May 11, 2000”, 9 pgs. |
“U.S. Appl. No. 09/572,410, Response filed Oct. 3, 2000 to Restriction Requirement mailed Sep. 5, 2000”, 3 pgs. |
“U.S. Appl. No. 09/572,410, Restriction Requirement mailed Sep. 5, 2000”, 9 pgs. |
“U.S. Appl. No. 09/738,868, Final Office Action mailed Nov. 26, 2003”, 7 pgs. |
“U.S. Appl. No. 09/738,868, Non-Final Office Action mailed Apr. 15, 2004”, 7 pgs. |
“U.S. Appl. No. 09/738,868, Advisory Action mailed Feb. 13, 2004”, 2 pgs. |
“U.S. Appl. No. 09/738,868, Final Office Action mailed Oct. 5, 2004”, 6 pgs. |
“U.S. Appl. No. 09/738,868, Non-Final Office Action mailed Jul. 17, 2003”, 7 pgs. |
“U.S. Appl. No. 09/738,868, Notice of Allowance mailed Jan. 13, 2005”, 6 pgs. |
“U.S. Appl. No. 09/738,868, Request for Continued Examination filed Feb. 24, 2004”, 3 pgs. |
“U.S. Appl. No. 09/738,868, Response filed Jan. 23, 2004 to Final Office Action mailed Nov. 26, 2003”, 14 pgs. |
“U.S. Appl. No. 09/738,868, Response filed Jun. 9, 2004 to Non-Final Office Action Apr. 15, 2004”, 14 pgs. |
“U.S. Appl. No. 09/738,868, Response filed Oct. 15, 2003 to Non-Final Office Action mailed Jul. 17, 2003”, 15 pgs. |
“U.S. Appl. No. 09/738,868, Response filed Dec. 6, 2004 to Final Office Action mailed Oct. 5, 2004”, 17 pgs. |
“U.S. Appl. No. 09/905,054, Non Final Office Action mailed May 6, 2003”, 3 pgs. |
“U.S. Appl. No. 09/905,054, Notice of Allowance mailed Aug. 26, 2003”, 5 pgs. |
“U.S. Appl. No. 09/905,054, Preliminary Amendment filed Jul. 12, 2001”, 2 pgs. |
“U.S. Appl. No. 09/905,054, Response filed Aug. 19, 2003 to Non Final Office Action mailed May 6, 2003”, 8 pgs. |
“U.S. Appl. No. 09/905,054, Supplemental Preliminary Amendment filed Nov. 19, 2001”, 4 pgs. |
“U.S. Appl. No. 09/907,895, Non Final Office Action mailed May 6, 2003”, 4 pgs. |
“U.S. Appl. No. 09/907,895, Notice of Allowance mailed Aug. 26, 2003”, 5 pgs. |
“U.S. Appl. No. 09/907,895, Preliminary Amendment filed Nov. 27, 2001”, 4 pgs. |
“U.S. Appl. No. 09/907,895, Response filed Aug. 19, 2003 to Non Final Office Action mailed May 6, 2003”, 9 pgs. |
“U.S. Appl. No. 10/118,537, Non-Final Office Action mailed Apr. 6, 2004”, 4 pgs. |
“U.S. Appl. No. 10/118,537, Notice of Allowance mailed Sep. 10, 2004”, 5 pgs. |
“U.S. Appl. No. 10/118,537, Response filed Jul. 6, 2004 to Non Final Office Action mailed Apr. 6, 2004”, 10 pgs. |
“U.S. Appl. No. 10/687,433, Advisory Action mailed Dec. 28, 2004”, 3 pgs. |
“U.S. Appl. No. 10/687,433, Final Office Action mailed Aug. 2, 2005”, 6 pgs. |
“U.S. Appl. No. 10/687,433, Final Office Action mailed Nov. 18, 2004”, 5 pgs. |
“U.S. Appl. No. 10/687,433, Non Final Office Action mailed Mar. 1, 2005”, 5 pgs. |
“U.S. Appl. No. 10/687,433, Non-Final Office Action mailed Jun. 21, 2004”, 6 pgs. |
“U.S. Appl. No. 10/687,433, Notice of Allowance mailed Dec. 16, 2005”, 4 pgs. |
“U.S. Appl. No. 10/687,433, Response filed Jun. 1, 2005 to Non-Final Office Action mailed Mar. 1, 2005”, 14 pgs. |
“U.S. Appl. No. 10/687,433, Response filed Sep. 21, 2004 to Non-Final Office Action mailed Jun. 21, 2004”, 8 pgs. |
“U.S. Appl. No. 10/687,433, Response filed Dec. 2, 2005 to Final Office Action mailed Aug. 2, 2005”, 9 pgs. |
“U.S. Appl. No. 10/687,433, Response filed Dec. 10, 2004 to Final Office Action mailed Nov. 18, 2004”, 8 pgs. |
“U.S. Appl. No. 10/747,391, Advisory Action mailed Jun. 10, 2009”, 4 pgs. |
“U.S. Appl. No. 10/747,391, Advisory Action mailed Jul. 16, 2010”, 3 pgs. |
“U.S. Appl. No. 10/747,391, Final Office Action mailed Mar. 19, 2009”, 9 pgs. |
“U.S. Appl. No. 10/747,391, Final Office Action mailed Mar. 31, 2010”, 8 pgs. |
“U.S. Appl. No. 10/747,391, Final Office Action mailed Dec. 30, 2008”, 9 pgs. |
“U.S. Appl. No. 10/747,391, Non Final Office Action mailed Jun. 2, 2008”, 9 pgs. |
“U.S. Appl. No. 10/747,391, Non Final Office Action mailed Sep. 2, 2009”, 9 pgs. |
“U.S. Appl. No. 10/747,391, Non Final Office Action mailed Nov. 26, 2007”, 18 pgs. |
“U.S. Appl. No. 10/747,391, Notice of Allowance mailed Feb. 4, 2011”, 4 pgs. |
“U.S. Appl. No. 10/747,391, Response filed Feb. 12, 2007 to Restriction Requirement mailed Jan. 12, 2007”, 7 pgs. |
“U.S. Appl. No. 10/747,391, Response filed Feb. 24, 2009 to Final Office Action mailed Dec. 30, 2008”, 10 pgs. |
“U.S. Appl. No. 10/747,391, Response filed Feb. 25, 2008 to Non Final Office Action mailed Nov. 26, 2007”, 13 pgs. |
“U.S. Appl. No. 10/747,391, Response filed May 28, 2009 to Final Office Action mailed Mar. 19, 2009”, 11 pgs. |
“U.S. Appl. No. 10/747,391, Response filed Jun. 30, 2010 to Final Office Action mailed Mar. 31, 2010”, 9 pgs. |
“U.S. Appl. No. 10/747,391, Response filed Jul. 20, 2009 to Advisory Action mailed Jun. 10, 2009”, 11 pgs. |
“U.S. Appl. No. 10/747,391, Response filed Sep. 2, 2008 to Non Final Office Action mailed Jun. 2, 2008”, 10 pgs. |
“U.S. Appl. No. 10/747,391, Response filed Dec. 2, 2009 to Non Final Office Action mailed Sep. 2, 2009”, 12 pgs. |
“U.S. Appl. No. 10/747,391, Restriction Requirement mailed Jan. 12, 2007”, 6 pgs. |
“U.S. Appl. No. 11/021,141, Non-Final Office Action mailed Jul. 26, 2007”, 6 pgs. |
“U.S. Appl. No. 11/021,141, Notice of Allowance mailed Apr. 22, 2008”, 4 pgs. |
“U.S. Appl. No. 11/021,141, Response filed Oct. 26, 2007 to Office Action mailed Jul. 26, 2007”, 9 pgs. |
“U.S. Appl. No. 11/021,141, Supplemental Notice of Allowability mailed Jun. 25, 2008”, 3 pgs. |
“U.S. Appl. No. 11/115,618, Final Office Action mailed Jan. 8, 2008”, 8 pgs. |
“U.S. Appl. No. 11/115,618, Final Office Action mailed Aug. 24, 2007”, 11 pgs. |
“U.S. Appl. No. 11/115,618, Non-Final Office Action mailed Mar. 12, 2007”, 10 pgs. |
“U.S. Appl. No. 11/115,618, Notice of Allowance mailed Apr. 2, 2008”, 4 pgs. |
“U.S. Appl. No. 11/115,618, Response filed Oct. 22, 2007 to Final Office Action mailed Aug. 24, 2007”, 15 pgs. |
“U.S. Appl. No. 11/115,618, Response filed Mar. 4, 2008 to Final Office Action mailed Jan. 8, 2008”, 9 pgs. |
“U.S. Appl. No. 11/115,618, Response filed Jun. 12, 2007 to Non-Final Office Action mailed Mar. 12, 2007”, 13 pgs. |
“U.S. Appl. No. 11/379,912 Notice of Allowance mailed Jul. 26, 2010”, 4 pgs. |
“U.S. Appl. No. 11/379,912, Examiner Interview Summary mailed Sep. 22, 2009”, 2 pgs. |
“U.S. Appl. No. 11/379,912, Final Office Action mailed Sep. 10, 2008”, 9 pgs. |
“U.S. Appl. No. 11/379,912, Non-Final Office Action mailed Feb. 25, 2008”, 8 pgs. |
“U.S. Appl. No. 11/379,912, Non-Final Office Action mailed Mar. 25, 2009”, 8 pgs. |
“U.S. Appl. No. 11/379,912, Notice of Allowance mailed Dec. 21, 2009”, 4 pgs. |
“U.S. Appl. No. 11/379,912, Response filed Jan. 12, 2009 to Final Office Action mailed Sep. 10, 2008”, 9 pgs. |
“U.S. Appl. No. 11/379,912, Response filed May 14, 2008 to Non Final Office Action mailed Feb. 25, 2008”, 8 pgs. |
“U.S. Appl. No. 11/379,912, Response filed Sep. 23, 2009 to Non Final Office Action mailed Mar. 25, 2009”, 14 pgs. |
“U.S. Appl. No. 12/169,432, Non Final Office Action mailed Dec. 28, 2010”, 6 pgs. |
“U.S. Appl. No. 12/169,432, Notice of Allowance mailed Jun. 10, 2011”, 5 pgs. |
“U.S. Appl. No. 12/169,432, Response filed Mar. 28, 2011 to Non Final Office Action mailed Dec. 28, 2010”, 9 pgs. |
“U.S. Appl. No. 12/220,830, Final Office Action mailed Feb. 8, 2011”, 6 pgs. |
“U.S. Appl. No. 12/220,830, Non Final Office Action mailed Sep. 13, 2010”, 6 pgs. |
“U.S. Appl. No. 12/220,830, Response filed Dec. 8, 2010 to Non Final Office Action mailed Sep. 13, 2010”, 8 pgs. |
“U.S. Appl. No. 12/220,830, Response filed Aug. 8, 2011 to Final Office Action mailed Feb. 8, 2011”, 7 pgs. |
“U.S. Appl. No. 12/941,377, Non-Final Office Action mailed Feb. 9, 2011”, 6 pgs. |
“U.S. Appl. No. 12/941,377, Notice of Allowance mailed Oct. 21, 2011”, 5 pgs. |
“U.S. Appl. No. 12/941,377, Response filed Sep. 6, 2011 to Non-Final Office Action mailed May 9, 2011”, 8 pgs. |
“U.S. Appl. No. 13/158,955 , Response filed Jun. 5, 2012 to Non Final Office Action mailed Mar. 5, 2012”, 12 pgs. |
“U.S. Appl. No. 13/158,955, Examiner Interview Summary mailed Feb. 17, 2012”, 3 pgs. |
“U.S. Appl. No. 13/158,955, Final Office Action mailed Jun. 22, 2012”, 5 pgs. |
“U.S. Appl. No. 13/158,955, Non Final Office Action mailed Mar. 5, 2012”, 5 pgs. |
“U.S. Appl. No. 13/158,955, Non Final Office Action mailed Oct. 10, 2012”, 5 pgs. |
“U.S. Appl. No. 13/158,955, Non Final Office Action mailed Oct. 19, 2011”, 5 pgs. |
“U.S. Appl. No. 13/158,955, Notice of Allowance mailed Feb. 15, 2013”, 6 pgs. |
“U.S. Appl. No. 13/158,955, Response filed Jan. 8, 2013 to Non Final Office Action mailed Oct. 10, 2012”, 10 pgs. |
“U.S. Appl. No. 13/158,955, Response filed Sep. 21, 2012 to Final Office Action mailed Jun. 22, 2012”, 10 pgs. |
“U.S. Appl. No. 13/411,063, Final Office Action mailed Apr. 9, 2013”, 5 pgs. |
“U.S. Appl. No. 13/411,063, Non Final Office Action mailed Nov. 28, 2012”, 8 pgs. |
“U.S. Appl. No. 13/411,063, Notice of Allowance mailed Jun. 13, 2013”, 6 pgs. |
“U.S. Appl. No. 13/411,063, Response filed Mar. 26, 2013 to Non Final Office Action mailed Nov. 28, 2012”, 10 pgs. |
“U.S. Appl. No. 13/411,063, Response filed Jun. 4, 2013 to Final Office Action mailed Apr. 9, 2013”, 6 pgs. |
“International Application Serial No. PCT/US00/22644, International Preliminary Examination Report mailed Sep. 27, 2001”, 6 pgs. |
“International Application Serial No. PCT/US00/22644, International Search Report mailed Nov. 15, 2000”, 3 pgs. |
“International Application Serial No. PCT/US00/22644, Written Opinion mailed Jul. 25, 2001”, 5 pgs. |
“Vigor Model 2950 Physician's System Manual”, (1996), 87 pgs. |
Hiebert, J. F., et al., “Event Marker Alignment by Inclusion of Event Marker Transmission Latency in the Real-Time Data Stream”, Application Serial No., pp. 1-28. |
Tanenbaum, A. S., “Computer Networks”, Prentice-Hall, Inc., Englewood Cliffs, NJ, (1981), 125-128. |
“U.S. Appl. No. 13/247,473, Response filed Nov. 11, 2013 to Non Final Office Action mailed Aug. 15, 2013”, 9 pgs. |
“U.S. Appl. No. 13/247,473, Non Final Office Action mailed Aug. 15, 2013”, 7 pgs. |
“U.S. Appl. No. 13/247,473, Notice of Allowance mailed Dec. 26, 2013”, 6 pgs. |
Number | Date | Country | |
---|---|---|---|
20130324862 A1 | Dec 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13411063 | Mar 2012 | US |
Child | 13964893 | US | |
Parent | 12941377 | Nov 2010 | US |
Child | 13411063 | US | |
Parent | 11379912 | Apr 2006 | US |
Child | 12941377 | US | |
Parent | 10687433 | Oct 2003 | US |
Child | 11379912 | US | |
Parent | 09738869 | Dec 2000 | US |
Child | 10687433 | US |