Source: http://www.google.com/patents/US7630773?dq=7751826
Timestamp: 2015-03-06 04:17:05
Document Index: 722046665

Matched Legal Cases: ['art 105', 'art 105', 'art 105', 'art 105', 'art 105', 'art 105', 'art 105', 'art 105', 'art 105', 'art 105', 'art 105', 'art 105']

Patent US7630773 - Adaptive software configuration for a medical device - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsThis document describes, among other things, a method of operating a medical device comprising updating a regulatory approval status stored in at least one of the medical device or a second device operable to communicate with the medical device, and enabling or disabling the at least one function in...http://www.google.com/patents/US7630773?utm_source=gb-gplus-sharePatent US7630773 - Adaptive software configuration for a medical deviceAdvanced Patent SearchPublication numberUS7630773 B2Publication typeGrantApplication numberUS 11/560,658Publication dateDec 8, 2009Filing dateNov 16, 2006Priority dateOct 5, 2004Fee statusPaidAlso published asEP1807153A1, US7167755, US8639346, US20060074463, US20070100397, US20100049279, WO2006041827A1Publication number11560658, 560658, US 7630773 B2, US 7630773B2, US-B2-7630773, US7630773 B2, US7630773B2InventorsMichael Seeberger, Scott Vanderlinde, James Kalgren, Par Lindh, Kristine M. Larsen-Kelly, Mitchell Lanz, Jeffrey M. Thompson, John A. DyjachOriginal AssigneeCardiac Pacemakers, Inc.Export CitationBiBTeX, EndNote, RefManPatent Citations (99), Non-Patent Citations (6), Referenced by (1), Classifications (8), Legal Events (2) External Links: USPTO, USPTO Assignment, EspacenetAdaptive software configuration for a medical device
US 7630773 B2Abstract
This document describes, among other things, a method of operating a medical device comprising updating a regulatory approval status stored in at least one of the medical device or a second device operable to communicate with the medical device, and enabling or disabling the at least one function in the medical device based on the regulatory approval status. The regulatory approval status corresponds to at least one function performable by the medical device.
a controller circuit coupled to the memory circuit and communication circuit, the memory circuit storing instruction code executable by the controller circuit to perform at least one function and to enable or disable the at least one function; and
a controller circuit coupled to the memory circuit and the communication circuit, the controller circuit executing instructions to communicate with the IMD; and
wherein at least one of the memory circuits of the IMD and the second device stores a geographical location identifier, and wherein at least one of the controller circuits of the IMD and the second device is configured to automatically compare the geographic location identifier to a geographic jurisdiction of a regulatory approval of the at least one function.
2. The system of claim 1, wherein at least one of the memory circuits of the IMD and the second device stores a geographic location identifier to identify where the IMD was implanted, and wherein the status identifier enables or disables the function in accordance with a regulatory approval status of the at least one function, the approval status associated with the geographic location where the IMD was implanted.
3. The system of claim 1, wherein at least one of the memory circuits of the IMD and the second device stores a geographic location identifier stored in the memory circuit to identify where the IMD is deemed to be located, and wherein the status identifier enables or disables the function in accordance with a regulatory approval status of the at least one function, the approval status associated with the geographic location where the IMD is deemed to be located.
4. The system of claim 1, in which the status identifier includes a first value used to disable a function to indicate that the function is not approved, and a second value used to enable a function to indicate that the function is approved.
5. The system of claim 4, in which the status identifier includes a third value indicating that the function is approved for a clinical study purpose, and wherein the third value is used to enable the corresponding function.
6. The system of claim 1, in which the status identifier includes a value to indicate that the function has an approved status during a patient emergency, and wherein the value enables the corresponding function.
7. The system of claim 6, wherein at least one of the memory circuits of the IMD and the second device stores a geographic location identifier, and wherein the status identifier enables or disables the function during an emergency in accordance with a regulatory approval status of the function during an emergency, wherein the regulatory approval status is associated with the geographic location.
8. The system of claim 1, wherein at least one of the IMD and the second device further includes a timing circuit coupled to its controller circuit, wherein the controller circuit is operable to enable or disable a function during a timed duration associated with a regulatory approval status.
9. The system of claim 1, wherein at least one of the IMD and the second device further includes a clock circuit coupled to the controller circuit, wherein the controller circuit is operable to enable or disable a function in relation to a time and/or date associated with a regulatory approval status.
10. The system of claim 1, wherein the IMD further includes at least one cardiac signal sensing circuit operable to detect cardiac signals, and wherein the at least one function includes a diagnostic test.
11. The system of claim 1, wherein the IMD further includes a therapy circuit coupled to the controller circuit, and wherein the at least one function includes a therapy delivered to a patient.
12. The system of claim 1, wherein the at least one function includes a frequency of operation used in communication between the IMD and the second device.
13. The system of claim 1, wherein at least the memory circuit of the IMD stores the status identifier, wherein the second device is operable to communicate at least one approved function to the IMD, and wherein the IMD controller circuit is operable to compare at least one performable function to the approved function and update at least one status identifier in accordance with an outcome of a comparison.
14. The system of claim 1, wherein at least the memory circuit of the second device stores the status identifier, and wherein the second device is operable to communicate at least one identifier associated with the regulatory approval status to the IMD.
15. The system of claim 1, wherein the memory circuit of the second device stores the status identifier, and wherein the second device is operable to enable or disable the at least one function in accordance with the regulatory approval status.
16. The system of claim 1, wherein the memory circuit of the IMD stores the status identifier, and wherein the IMD is operable to communicate an enabled or disabled status of the at least one function to the second device.
17. The system of claim 1, wherein the second device is another IMD.
18. The system of claim 1, wherein the second device is an external device further including a user interface.
19. The system of claim 1, wherein the second device is operable to communicate over a network.
20. The system of claim 19, wherein the network includes a wireless communication network.
21. The system of claim 20, wherein the network includes the internet.
This application is a Division of U.S. application Ser. No. 10/958,628, filed on Oct. 5, 2004, now U.S. Pat. No. 7,167,755, which is incorporated herein by reference.
The field generally relates to medical devices and, in particular, but not by way of limitation, to systems and methods for managing functions performed by medical devices.
Patient care often includes use of advanced medical devices. These devices typically automatically perform a host of functions including therapeutic functions, for example, to deliver therapy to a patient or patients, or to perform diagnostic functions such as automatically running tests on patients. These functions are also sometimes referred to as features of the medical devices. Examples of medical devices include, blood glucose meters, insulin pumps, urinalysis devices, fetal heart monitoring devices, blood test meters, sleep apnea or hypopnea detection devices, and sleep apnea therapy devices like continuous positive airway pressure (CPAP) devices, blood pressure cuffs and weight scales. Implantable medical devices (IMDs) are devices designed to be implanted into a patient. Some examples of IMDs include cardiac rhythm management (CRM) devices such as implantable pacemakers and implantable cardioverter defibrillators (ICDs). The devices are used to treat patients using electrical therapy and to aid a physician or caregiver in patient diagnosis through internal monitoring of a patient's condition. IMDs may also include electrical leads that are either separate from, or connected to, a CRM device. Electrical leads connected to CRM devices are typically located in or near a heart to provide electrical therapy to the heart. The electrical leads are also in communication with sense amplifiers of the CRM devices to monitor intrinsic electrical heart activity of a patient. Other examples of IMDs include implantable insulin pumps or devices implanted to administer drugs to a patient. Additionally, some medical devices are able to communicate with other devices by wireless communication signals.
Often, the full functionality of the medical devices is not available or useful to a patient or caregiver. The functions actually needed or used may be a subset of the available functions, such as to match the device to specific patient needs. If the medical device is implantable, a device parameter, device configuration, or patient parameter may change. This, in turn, may require changing the functions available in the medical device.
Additionally, when new functions are developed, the functions may need to be approved by one or more governmental, quasi-governmental, or other regulatory bodies, such as the Food and Drug Administration (FDA) of the United States Government. Gaining regulatory approval is often a long process. For example, it may involve lengthy clinical trials. If an IMD is marketed worldwide, an IMD manufacturer needs to gain approval for the new functions from several regulatory bodies in different geographical areas of the world.
The present inventors have recognized a need for improved management of functions of medical devices. This document discusses, among other things, systems and methods provided for managing functions of medical devices. A method example includes a method of configuring a medical device. The method comprises updating a regulatory approval status stored in at least one of the medical device or a second device operable to communicate with the medical device, and enabling or disabling the at least one function in the medical device based on the regulatory approval status. The regulatory approval status corresponds to at least one function performable by the medical device.
A system example comprises an implantable medical device (IMD) and a second device. The IMD includes a communication circuit, a memory circuit and a controller circuit coupled to the at least one memory circuit and communication circuit. The memory circuit of the IMD stores instruction code executable by the controller circuit to perform at least one function and to enable or disable the at least one function. The second device includes a communication circuit, a memory circuit and a controller circuit coupled to the at least one memory circuit and the communication circuit. The controller circuit of the second device executes instructions to communicate with the IMD. At least one of the memory circuits of the IMD and the second device stores a status identifier corresponding to a regulatory approval status of the at least one function. The status identifier is used to enable or disable the at least one function.
FIG. 1 is an illustration of an embodiment of a system that uses an implantable medical device.
FIG. 2 is an illustration of an implantable medical device.
FIG. 3 is a block diagram of portions of an embodiment of a system that manages medical device functions.
FIG. 4 is a block diagram of portions of an embodiment of a system that manages medical device functions.
FIG. 5 is a block diagram of one example of a method of configuring a medical device.
FIG. 6 is a block diagram of a method of activating or deactivating a function of a medical device.
In the following detailed description, reference is made to the accompanying drawings which form a part hereof, and specific embodiments in which the invention may be practiced are shown by way of illustration. It is to be understood that other embodiments may be used and structural or logical changes may be made without departing from the scope of the present invention. In this document, the term �or� is used to refer to a nonexclusive or, unless otherwise indicated.
The present application discusses, among other things, systems and methods for managing functions performed by medical devices. Medical devices are often complex and are typically capable of providing many different functions. A patient may not require all of the functionality of a particular device. However, the functionality required from the device may change, such as when information related to the patient or the device is obtained. This information includes information related to a patient, such as a condition of the patient or change in condition of the patient. A change in the patient condition may result in a need for a different device having different functionality. If the device is an implantable device, the need for a different device typically results in another implant procedure, which typically involves both increased cost and risk.
This information related to the patient or the device may also include information related to changes in device-measured parameters. Such parameters may be measured after prompting by a user or done automatically by the device. Typically, the information is communicated to a user by the medical device itself or by a second device used to communicate with the medical device. The information is typically given to a user through a user interface. The user may then change the functionality of the device using the user interface. There may be adverse delays in enabling or disabling the proper functions in a medical device. The �user� of a device refers to anyone who interacts with the device and includes without limitation a patient, a caregiver and a manufacturer of the device.
The information related to the patient or device may further include information related to regulatory approval of the medical device. When new devices or device functions are developed, they typically need to gain approval from one or more regulatory bodies such as the FDA. If the medical device is to be marketed worldwide, the new functions typically need to be approved by several regulatory bodies. These regulatory bodies often have jurisdictions over different geographic areas. The result is that an approval status for a medical device (or, of certain functions of a medical device) may vary with geographic area. These geographic jurisdictional areas may include multiple countries such as the European Union (EU). Also, one country may base its regulatory approval on a regulatory approval of a body from another geographic jurisdiction, such as when regulatory approval in a non-EU country follows the approval of the EU. Additionally, a regulatory body may give limited approval before full approval, such as approval for a research study or approval for clinical trials. Also, a regulatory body may allow use of a device, a function of a device, or both, for emergency use before the device or function receives full approval. Typically, device manufacturers deal with this problem by providing several models of a medical device with each model having a different set of unalterable functional capabilities, or by holding up distribution until the devices have gained approval. These approaches generate additional overhead costs from the operation of multiple manufacturing lines, management of additional inventory and marketing of a multiple device product line.
In one example, these problems are avoided by providing complete functionality in all model versions of a medical device and providing an updated set of active functions based on the new information related to the patient and/or device. This is accomplished by providing the ability for a medical device to dynamically configure a set of one or more active functions from a set of one or more performable functions when the device receives the information. These medical devices include a controller circuit such as a microprocessor or microcontroller. The controller circuit executes instruction code to perform the various functions. According to some embodiments, all functionality resides in the device and a section or sections of corresponding instruction code are enabled to allow the medical device to provide the particular function. Conversely, these areas of instruction code are disabled to inhibit the function. For example, the enabling and disabling can be realized by branching to or around the pertinent areas of instruction code. In some embodiments, the enabling and disabling includes applying or removing power to circuitry that provides the functions, such as therapy circuitry for example. In some embodiments, the medical device is given an identifier after the update to reflect the new functionality, such as a new model number or dash or revision number appended to or otherwise associated with the model number.
In other embodiments, new instruction code is loaded into the device to provide a new function or set of functions. In some of these embodiments, this instruction code can be loaded into volatile memory from a second device, such as when a need for the updated code is recognized by the medical device or the second device. In another embodiment, the medical device contains writeable non-volatile memory such as flash-memory, and the instruction code is loaded into the flash-memory. In this embodiment, the medical device includes a basic kernel of instruction code to load and begin executing the downloaded instruction code. In other embodiments, the controller circuit checks the downloaded code for errors before loading the updated code into flash memory. In one such embodiment, the updated instruction code is first loaded into volatile memory and checked for errors. In another embodiment, the instruction code is checked for errors as it is received from the second device. The medical device may also include a write circuit that provides the voltages necessary to write non-volatile memory.
The medical device receiving the updated instruction code can be either an external device (such as an external cardioverter defibrillator, for example) or an implantable medical device (IMD) (such as an implantable cardioverter defibrillator, for example). The second device sending the instruction code can be an external device such as a computer, an IMD programmer, or a repeater, or the second device can be an external medical device or another IMD. The term �repeater� refers to a device that rebroadcasts information it receives. For example, a repeater may receive information by wired or wireless telephone or a wired or wireless connection to a communications network, such as the internet, and may rebroadcast the information using wireless communications, or vice versa. In this way, a repeater placed in proximity to a patient can communicate with an IMD thereby providing a user with a method to remotely communicate with an IMD.
FIG. 1 illustrates an embodiment of a system 100 that uses an implantable medical device (IMD) 110. The system 100 shown is one embodiment of portions of a system used to treat a cardiac arrhythmia. A pulse generator (PG) or similar electronics unit or other IMD 110 is coupled by an intravascular or other cardiac lead 108, or additional leads, to a heart 105 of a patient 102. Examples of IMD 110 include, without limitation, a pacer, a defibrillator, a cardiac resynchronization therapy (CRT) device, or a combination of such devices. System 100 also includes an IMD programmer or other external device 170 that typically provides wireless communication signals 160 to communicate with the IMD 110, such as inductive signals or radio frequency (RF) signals. In some embodiments, the IMD 110 is able to communicate wirelessly with another IMD 110.
Cardiac lead 108 includes a proximal end that is coupled to IMD 110 and a distal end that includes an electrode or electrodes. The distal end is coupled to, or placed in proximity to, one or more portions of a heart 105. The electrodes are for delivering atrial or ventricular cardioversion/defibrillation or pacing or resynchronization therapy to the heart 105. IMD 110 includes components that are enclosed in a hermetically-sealed canister or �can.� Additional electrodes may be located on the can, or on an insulating header, or on other portions of IMD 110, such as for providing unipolar pacing or defibrillation energy, for example, in conjunction with the electrodes disposed on or around heart 105. The lead 108 or leads and electrodes are also typically used for sensing intrinsic electrical activity of a heart 105 or for sensing impedance associated with a heart or thorax.
FIG. 2 illustrates an IMD 110 coupled by one or more leads 108A-B to heart 105. Heart 105 includes a right atrium 200A, a left atrium 200B, a right ventricle 205A, a left ventricle 205B, and a coronary sinus 220 extending from right atrium 200A. In this embodiment, atrial lead 108A includes electrodes (electrical contacts, such as ring electrode 225 and tip electrode 230) disposed in, around, or near an atrium 200A of heart 105 for sensing signals and/or delivering pacing therapy to the atrium 200A. Lead 108A optionally also includes additional electrodes, such as for delivering atrial and/or ventricular cardioversion/defibrillation and/or pacing or resynchronization therapy to heart 105.
Ventricular lead 108B includes one or more electrodes, such as tip electrode 235 and ring electrode 240, for delivering sensing signals and/or delivering pacing therapy. Lead 108B optionally also includes additional electrodes, such as for delivering atrial and/or ventricular cardioversion/defibrillation and/or pacing therapy to heart 105. IMD 110 includes components that are enclosed in a hermetically-sealed canister or �can� 250. Additional electrodes may be located on the can 250, or on an insulating header 255, or on other portions of IMD 110, for providing unipolar pacing and/or defibrillation energy in conjunction with the electrodes disposed on or around heart 105. Other forms of electrodes include meshes and patches which may be applied to portions of heart 105 or which may be implanted in other areas of the body to help �steer� electrical currents produced by IMD 110. In one embodiment, one of atrial lead 108A or ventricular lead 108B is omitted, i.e., a �single chamber� device is provided, rather than the dual chamber device illustrated in FIG. 2. In another embodiment, additional leads are provided for coupling the IMD 110 to other heart chambers and/or other locations in the same heart chamber as one or more of leads 108A-B. The present methods and systems will work in a variety of configurations and with a variety of electrical contacts or �electrodes.� The methods and systems also work in medical devices, implantable or external, that do not include leads or electrodes.
FIG. 3 is a block diagram 300 of portions of an embodiment of a system 302 that manages medical device functions. The system 302 includes an IMD 305 and a second device 350. The IMD 305 includes at least one memory circuit 310, which is either separate from or integral to a controller circuit 315 coupled to the at least one memory circuit 310. The memory circuit 315 stores instruction code 320 executable by the controller circuit 315 to perform at least one function. The IMD 305 also includes a communication circuit 325 for communication with the second device 350. The second device 350 includes at least one memory circuit 355, which is either separate from or integral to a controller circuit 360 coupled to the at least one memory circuit 355, and a communication circuit 365. A controller circuit 315, 360 operates using hardware, firmware, software or any combination of hardware, firmware and software.
The IMD 305 is dynamically configured after information is received that is related to regulatory approval of a device function. The term function includes, among other things, any diagnostic test or measurement performed by a medical device (in this embodiment, an IMD 305), any sensing function, any therapy delivered or performed by a medical device, or a medical device communicating using an approved operating frequency. In the example of FIG. 3, the IMD 305 includes at least one cardiac signal sensing circuit 330 to detect cardiac signals, and the at least one function includes a diagnostic test. In another embodiment, the IMD 305 further includes a therapy circuit 335 coupled to the controller circuit 315, and the at least one function includes a therapy delivered to a patient.
At least one of the memory circuits 310, 355 of the IMD 305 and the second device 350 stores at least one status identifier 340, 370 corresponding to a regulatory approval status of the at least one function. The status identifier 340, 370 is used to enable or disable the at least one function. According to some embodiments of the system 302, at least the memory circuit 310 of the IMD 305 stores the status identifier 340. In some examples, the second device 350 is operable to communicate at least one approved function to the IMD 305, and wherein the IMD controller circuit 315 is operable to compare at least one performable function to the approved function and update at least one status identifier 340 in accordance with an outcome of a comparison. In an example, the second device 350 may communicate a set of one or more functions to the IMD 305 that the IMD 305 is to perform. The IMD controller circuit 315 compares a set of active functions to the set obtained from the second device 350 and updates the corresponding IMD status identifier or identifiers 340 to match the set of active functions obtained from the second device. In another example, the second device sends one approved function at a time. The IMD 305 updates the corresponding IMD status identifiers 340 as the approved functions are communicated. In this example, any non-communicated functions are deemed to be disabled.
In other embodiments, at least the memory circuit 355 of the second device 350 stores the status identifier 370. The second device 350 communicates the status identifier 370 values for storage into the IMD memory circuit 310 to enable or disable functions. According to yet other embodiments, the memory circuit 355 of the second device 350 stores the status identifier 370, and the second device 350 enables or disables the at least one function in the IMD 305 in accordance with the regulatory approval status. In another embodiment, the memory circuit 310 of the IMD 305 stores the status identifier 340, and the IMD 305 is operable to communicate an enabled or disabled status of the at least one function to the second device 350.
To enable or disable the function, in certain examples, the IMD controller circuit 315 reads a first value in the status identifier 340 that indicates that the corresponding function is not approved by the applicable regulatory authority. Upon reading the first value, the corresponding function is disabled and the controller circuit 315 does not perform that function. For example, reading the value may cause the controller circuit 315 to branch around the executable instruction code corresponding to that function. When the controller circuit 315 reads a second value in the status identifier 340 to indicate that the corresponding function is approved by the applicable regulatory, that function is enabled and the controller circuit 315 performs that function.
In other examples, the second device controller circuit 360 reads a first value or a second value in the status identifier 370 that indicates that the corresponding function is not approved or approved by the applicable regulatory authority. Upon reading the first or second value, the second device 350 communicates a disable or enable to the IMD 305 and the corresponding function is disabled or enabled by the IMD 305. In further embodiments, a model number or a dash number of the IMD 305 is changed, such as to reflect the corresponding updated functionality.
In other embodiments, the system 302 further includes a geographic location identifier stored in at least one of the memory circuits 310, 355 to identify the IMD 305 with a location. In one example, the location specifies where the device is deemed to be located (i.e. where the medical device is used or the patient resides). The location may alternatively specify where the device 305 was implanted. In one example, the value of a status identifier 340, 370 enables or disables the corresponding function or functions in accordance with a regulatory approval status for the geographic location specified by the corresponding stored geographic location identifier. In one example, the memory circuit 310, 355 includes a table or set of tables. The table includes locations where the function is approved. In another example, a set of tables includes geographic locations organized into tables by jurisdiction. Regulatory approval in a jurisdiction is reflected by an entire table of locations becoming approved. If the geographic identifier is found in a table of approved locations, and the status identifier value is set to enable a function, then the controller circuit enables that function. If the geographic identifier is not found in a table of approved locations, and the status identifier value is set to enable the function, then the controller circuit does not enable that function. As discussed previously, which controller circuit 315, 360 enables or disables the function depends on where the status identifier 340, 370 is stored.
In certain examples, at least one of the IMD 305 and the second device 350 further includes a clock circuit coupled to the controller circuit 315, 360. The controller circuit 315, 360 is operable to enable or disable a function in relation to a time or date associated with a regulatory approval status. In one example, the controller circuit 315, 360 updates a status identifier with a new value at least partially in response to a time or date read from the clock circuit. In another example, the controller circuit 315, 360 performs a logic function (such as an �and� function) of the status identifier with the clock circuit value to enable or disable the function. In this way, a medical device can be programmed, in anticipation of an approval date, to start using a function after the anticipated approval date.
In another example, controller circuit 315, 360 uses a timing or clock circuit to provide a slot of time when the function is enabled or disabled. In the embodiment, the controller circuit 315, 360 enables or disables a function on a start date or time and disables or enables the function after a timed duration. For example, the controller circuit 315, 360 may update the status identifier with a new value during a timed duration, returning the status identifier to its previous value after the timed duration expires. In this way, a device may temporarily enable a medical device, such as for use in a clinical study. In another embodiment, to use a medical device in a clinical study, the device is deemed a clinical study device (such as by using a particular model number or dash number, for example). In one such example, the status identifier 340, 370 includes a third value to indicate that the function is approved for a clinical study purpose, and the third value enables the corresponding function in the clinical study device.
In another example, the status identifier 340, 370 includes a value to indicate that the function has an approved status during a patient emergency, and that value enables the corresponding function. In yet another embodiment, the timing or clock circuit provides a time slot where a function is enabled or disabled during an emergency. In a further embodiment, the emergency approved status is combined with the geographical location identifier information to provide the emergency function-enabled status in those geographic locations where such emergency use has obtained regulatory approval.
In some examples, the at least one function includes an operating frequency for communication between the IMD 305 and the second device 350. In one such example, the second device 350 communicates that a communication frequency (or frequencies) between the IMD 305 and the second device 350 has approval (for example, in a particular geographic location) from the appropriate regulatory body (such as the Federal Communications Commission (FCC), for example, in the United States). The IMD 305 then begins communicating using the approved frequency or frequencies.
In some examples, the second device 350 is another IMD. In one such illustrative example, the first IMD 305 administers a drug and the second device 350 is a cardiac rhythm management device providing electrical therapy.
In other examples, the second device 350 is an external device. In the examples, the memory circuit 355 stores information about one or more functions performable by the IMD 305. Such information is stored along with one or more corresponding current status identifiers 370, geographical identifiers, or both. The current status identifiers 370 indicate a most currently known regulatory approval status of the corresponding function. In some examples, the memory circuit 355 also includes at least one table including �device type� identifiers corresponding to any one or combinations of the performable functions. The term device type identifiers refers to any information that identifies the functionality of a device and includes model numbers, dash numbers, and the like. A particular device type identifier is communicated to a target device such as IMD 305 to reflect the new functionality of the device.
In one example, the second device 350 also includes a user interface for users to interact with the second external device 350. In some examples, the memory circuit 355 of the external device stores regulatory approval information. This includes regulatory approval by geographic location, or regulatory approval by jurisdiction. This information is used to update status identifiers in the IMD 305, for example, in accordance with the geographic location or jurisdiction or to enable and disable functions according to the information. According to some examples, the information can be entered into the second device 350 using the user interface. In some examples, the second device 350 receives the information from a third device. In another example, the second device 350 receives the information from the IMD 305.
In some examples, the second device 350 communicates over a network. In one such example, the second device 350 is an IMD programmer. In another example, the second device 350 is a repeater that communicates with the IMD 305 and a third device which is remote from the external device. In one example, such communication is carried out over a communication network. The communication network may be a wireless network such as a cell phone network, a telephone land line network, a cable television network, or a wired or wireless connection with a computer network, such as the internet. Examples of the third device include a user's computer or computer network, a server, a hospital computer network, a device manufacturer's �Advanced Patient Management� system, or the like.
FIG. 4 shows a block diagram 400 of portions of a system 405 that manages medical device functions. In this example, both the medical device and a second device are external devices. The system 400 includes a first external medical device 410 to perform diagnostic, therapeutic, or other functions. Examples of the first medical device 410 include, among other things, a blood glucose meter, an insulin pump, a urinalysis device, a fetal heart monitoring device, a blood test meter, a sleep apnea or hypopnea detection device, a sleep apnea therapy device, a blood pressure cuff, or a weight scale. The first external medical device 410 includes at least one memory circuit 415 and a controller circuit 420 coupled thereto. The memory circuit 415 stores instruction code 430 executable by the controller circuit 420 to perform at least one function. The memory circuit 415 also stores a corresponding status identifier 425 that enables or disables a corresponding function according to a regulatory approval status of that function. The first external device 410 also includes a communication circuit 435 coupled to the controller circuit 420.
The system 405 also includes a second external device 450 that communicates a regulatory approval status to the first device 410. The second device 450 includes a communication circuit 455 to communicate with the first device 410 and a memory circuit 460. The memory circuit 460 stores information 465 about one or more functions performable by the first device 410 along with one or more corresponding current status identifiers 470 of the most current regulatory approval status of a corresponding function. The second device 450 also includes a controller circuit 475 coupled to the communication circuit 455 and the memory circuit 460. The controller circuit 475 executes instructions to communicate the most current regulatory approval status to the first device 410 via the communication circuit 455. The devices 410 and 450 communicate via wireless or wired signals 490.
In some examples, the signals 490 are wireless communication signals, such as telemetry or radio frequency (RF) signals. In some examples, the at least one function includes communicating using a frequency of operation that is within a frequency spectrum approved by a regulatory body that regulates communication frequencies. In an illustrative example, the function includes communicating using frequencies within the Industrial Scientific and Medical band (ISM) or within the Short Range Devices (SRD) frequencies. In other examples, the signals 490 are communicated through a computer port such as a serial or parallel port. In further examples, the first and second devices 410 and 450 include web or other network interface circuits and the signals are communicated using the internet or other computer network.
In some examples, the controller circuits 420 or 475 execute instructions to retrieve and store information between the memory circuits 415 or 460 and the communication circuits 435 or 455. In other examples, the controller circuits 420 and 475 execute instructions to provide a starting address and block size information to the communication circuits 435 or 455, and the communication circuits 435 or 455 retrieve or store information from or to the memory circuits 415 or 460.
The system 405 operates similarly to the system discussed previously where the medical device is implantable. For example, the first medical device 410 performs similar functions of the IMD. In some examples, the first medical device 410 further includes a geographic location identifier stored in the memory circuit 415 to identify where the first device 410 is deemed to be located. A particular function's corresponding status identifier enables or disables that function in accordance with a geographic jurisdiction of a regulatory approval agency. In some examples of the first device 410, to enable or disable the function, the controller circuit 420 reads a first value in the status identifier 425 to indicate that the corresponding function is not approved. Upon reading the first value, that function is disabled and the controller circuit 420 does not perform that function. When the controller circuit 420 reads a second value in the status identifier 425 to indicate that the corresponding function is approved, that function is enabled and the controller circuit 420 performs that function. In another example, a third value of the status identifier 425 is used to designate that the function is approved for a clinical study purpose and the third value enables that function.
In some examples, the second device 450 communicates at least one approved function to the first device 410, and the controller circuit 420 of the first device 410 compares a set of performable functions to the approved function and updates any corresponding status identifiers 425 to enable or disable functions based on the comparison. In other examples, the second device 450 communicates one more status identifiers 425 or geographic identifiers associated with the regulatory approval status to the first device 410 for storage. In other examples, only the memory circuit 460 of the second device 450 stores the identifier or identifiers 470, and the second device 450 enables or disables the at least one function in the first device 410 in accordance with the regulatory approval status. In other examples, the memory circuit 415 of the first device 410 stores the at least one status identifier 425, and the first device 410 is operable to communicate an enabled or disabled status of the at least one function to the second device 450.
In some examples, at least one of the first and second devices communicates over a network with a third device or devices using either communication circuits 435 and 455 or additional or other communication circuits. In some examples, the network includes a wireless communication network. In further examples, the network includes the internet, or another wired computer network. In one example, the second device is a repeater in communication with a third device over the internet either through hard wire or a wireless local area network (LAN). In another example, the first medical device 410 communicates wirelessly with another medical device such as an IMD.
FIG. 5 is a block diagram of one example of a method 500 of configuring a medical device. At 510, a regulatory approval status of at least one function performable by the medical device is updated. The status is stored in either the medical device, a second device operable to communicate with the medical device, or both devices. The medical device may be an external medical device or an implantable medical device (IMD). In one embodiment, the IMD is a cardiac rhythm management device. The second device may be an external device, an external medical device, or an IMD. At 520, the function is enabled or disabled in the medical device based on the regulatory approval status. The at least one function includes, among other things, one or more diagnostic functions, one or more sensing functions, one or more therapeutic functions, or communicating using approved communication frequencies.
In some examples, the method 500 further includes comparing a geographic jurisdiction of a regulatory approval body to a geographic location of the medical device, and updating the regulatory approval status of the function using the comparison. In some examples, the geographic location of the medical device includes a location where the medical device is deemed to be located. In one example, such location is deemed to be the home address of the patient or the location of a hospital or clinic frequented by the patient. In certain examples in which the medical device is an IMD, the geographic location is deemed to be a location where the medical device was implanted into the patient. In yet other examples, the location is an actual location of the medical device, such as determined by a global positioning system (GPS) or by communication with a particular node in a wireless or wired communication network that has a known geographic location.
In some examples, enabling or disabling the at least one function of the medical device includes setting a corresponding status identifier to a first value indicating that the function is not approved. This value is used to disable the device from performing that function. Enabling and disabling also includes setting the status identifier to a second value indicating that the function is approved. This value is used to enable the device to perform that function. The term �used to enable or disable� encompasses enabling and disabling in conjunction with other enables or disables to provide further logical functions of the device. For example, a status identifier may enable a function because it has regulatory approval and yet the function may remain disabled for another reason, such as because the function is not needed by the user. The values are used by either the medical device or the second device to enable or disable the function.
According to some examples, updating a regulatory approval status includes updating a regulatory approval status stored in the second device and communicating at least one identifier associated with the regulatory approval status to the medical device. The communicating may be accomplished using wireless communication signals or the communicating may be over wired connections. In the examples, enabling or disabling the at least one function in accordance with the regulatory approval status includes enabling or disabling the function using the medical device. In one example, a controller circuit of the medical device reads the value stored in its memory and branches around the executable instruction code corresponding to that function. When the controller circuit reads a second value in the status identifier to indicate that a corresponding function is approved by the applicable regulatory, that function is enabled and the controller circuit performs that function.
In another example, the enabling or disabling is done using the second device. The second device reads the identifier value stored in its memory and communicates with the medical device to enable or disable a function, or functions, performable by the medical device. In another example, the second device communicates at least one approved function to the medical device. The medical device compares at least one performable function to the approved function. The comparison may be done by using comparison circuitry, by executing instructions in a controller circuit in the medical device to perform a comparison, or both. Based on the comparison, the medical device then updates a regulatory approval status stored in the medical device.
In other examples, the regulatory approval is limited to using the device in a research study, or a clinical study. In some such limited approval cases, the enabling or disabling of the function in the medical device includes enabling the function when the medical device is deemed a clinical-use device. In some examples, such limited approval is accomplished by using a third value for a status identifier that enables the function when the medical device is identified as a clinical device, such as by communicating a clinical-use model or dash number to the device. In other examples, the function is enabled in relation to a date of the study, such as enabling using a date and/or time. The enabling can be done using the medical device or the second device. In other examples, the function is allotted a particular time window such that it is enabled only during the period of the clinical study. In one example, a function-enabled time window can be established using a timing or clock circuit in the medical device. The medical device updates a status identifier from one value to another during the time slot and returns the status identifier to the original value after the time slot. In another example, the timing or clock circuit is in the second device and the second device updates the status identifiers to enable or disable one or more functions.
In some examples, the regulatory approval is limited to use of the function only during a patient emergency (such as while the function awaits full regulatory approval). In these examples, the enabling and disabling of status identifiers includes enabling the function during a patient emergency. Either the first device or the second device may detect the emergency. In some of these examples, enabling the function during a patient emergency includes enabling the function for a timed duration and then disabling after the timed duration. As an illustrative example, suppose that the medical device is an implantable cardioverter defibrillator (ICD) and the function includes a particular defibrillation therapy. A regulatory body may allow use of the therapy only during predetermined patient emergencies.
In some examples, the method 500 further includes validating the at least one function having updated approval status. In some examples, the validating includes error-checking information that is associated with the function and stored in the medical device. The information includes parameters used to perform a function stored in the medical device. For example, the parameter may be a value corresponding to an output voltage. The information checked can also include instruction code executed to perform the function.
In some examples, the validating includes verifying that functions do not contain conflicting parameters. As an illustrative example, suppose that the medical device is a cardiac rhythm management device. In this illustrative example, a status identifier update may enable a function that requires electrical leads that are not present in the system. In some examples, the validating includes validating using the medical device, the second device or a combination of the first and second devices. If the function cannot be validated because of parameter or other conflicts, in one example, the second device is not allowed to interact with the medical device. This is useful, for example, where there is substantial interaction between parameters of multiple functions and it is not desirable to allow a user to have access to some but not all parameters.
In some examples, the method 500 further includes providing notification of an update of a set of active functions of the medical device. The notification is useful to a caregiver to be alerted to changes in capabilities of the medical devices. It is also useful to a manufacturer of devices to track the functionality of the devices. In some examples, providing notification includes providing notification of an update to a third device. For example, the third device may be a computer or server on a network such as the internet, a hospital local area network (LAN), an APM, or the like. The notification can be sent by wireless or other electronic communication methods. In some examples, the update is communicated to a database. The database includes stored updates of the set of functions of devices which may be in the field or in inventory. In some examples, the notification includes notice that a device with a certain serial number has an updated different type identifier based on an updated set of functions active in the device. Examples of such identifiers include model numbers or dash or revision numbers appended to or otherwise associated with a model number. Since either the first or second device can be an IMD or an external device, providing the notification can be carried out using an IMD or an external device.
According to some embodiments, the notification of the update is delayed. In some examples of the embodiments, a notification is sent by electronic mail (e-mail) and the notification is provided when the e-mail is opened. In other examples, the notification is delayed until the medical device is interrogated by either a user or another device. In other examples, the notification is provided through a user interface display on any of the mentioned devices, and notification is delayed until the next time a user interacts with the user interface
Some of the embodiments discussed previously involve status identifiers stored in two devices. This raises an issue of how to handle the different circumstances that can arise when the identifiers agree, disagree, or when one, the other, or both of the identifiers are missing. FIG. 6 is a block diagram of a method 600 of activating or deactivating a function of a first medical device. At 610, regulatory approval information is stored in a second device that communicates with the first device. In one example, the regulatory approval information includes regulatory approval by geographic location. Approval by geographic location includes approval by country or region and corresponds to geographic jurisdictions of regulating bodies. At 620, geographic location information associated with the first device is stored in the first device and geographic location information associated with the second device is stored in the second device. The first medical device can be either an external medical device or an IMD. The second device can be an external device, an external medical device, or an IMD. In one example, the geographic location information associated with the first device includes a location where the device is deemed to be located. If the first device is an IMD, the geographic location information includes a location where the device is implanted, in one example.
At 630, one or more approval status identifiers are used to enable or disable at least one function of the first device. A first status identifier is stored in the first device to represent a first regulatory approval status of the function, and a second status identifier is stored in the second device to represent a second regulatory approval status of the function. In some examples, values are assigned to the status identifiers, such as a first value to indicate an approved status and a second value to indicate an unapproved status. Further examples include assigning a third value to indicate a limited approval, such as to one or more clinical trials.
At 640, the first and second status identifiers are updated according to at least one rule. In one example, the at least one rule is applied to the stored geographic information, the stored approval information, or the status identifiers. In some examples, updating the status identifiers in the first and second devices according to at least one rule includes deeming the function approved. In further examples, deeming the function approved includes indicating the availability of the function using the second device. For example, if the second device is an external device with a user interface, in one example, a display on the external device is used to indicate to the user that the function is available. In other examples, deeming the function approved includes deeming the function approved for clinical use.
In some examples, updating the first and second status identifiers according to the at least one rule includes deeming the function unapproved. In the example where the second device is an external device with a user interface, a display on the external device is used to indicate to the user that the function is unavailable, such as by either not displaying the option or �ghosting� the option on the display. In further examples, deeming the function unapproved includes preventing access to the first device using the second device, such as by not allowing the communications or by limiting the communications. In yet another example, deeming the function unapproved includes triggering an alarm or notification using the second device.
In some examples, updating the first and second status identifiers according to a rule or a set of rules includes updating to affect the most restrictive use of a function or functions subject to approval. For example, if applying a rule or set of rules to the information and identifiers results in one device allowing the function and a second device not allowing the function, use of the function is not allowed. In some examples, updating the first and second status identifiers according to a rule or a set of rules includes updating to affect the least restrictive use of a function or functions subject to approval. For example, if applying a rule or set of rules to the information and identifiers results in one device allowing the function and a second device not allowing the function, use of the function is allowed.
Table 1 below illustrates one example of a set of rules applied to stored geographical information, stored approval information, or status identifiers. The result of applying the rules is to allow or not allow use of one or more functions in a medical device. In the example shown, the first device is an IMD and the second device is an external device (PRM) to program the IMD. The PRM has a user interface including a display. The devices communicate using wireless signals. The embodiment is also applicable to two external devices or two IMDs. This example implements a set of rules that is more restrictive.
IMD/PRM
Function not available.
IMD model available with
geography window.
Function available OR not
available depending on geography.
If available, then IMD model
available with clinical window.
If function available, then IMD
model available with geography
Out of sync - raise alarm.
Function not available (or
available if IMD is deemed a
clinical device).
Special geography window
IMD model not available until
geography is entered.
IMD model not available.
The first column of the table is merely the line number of the rules. The second column of the Table relates to the geographic location information. Both the IMD and PRM contain geographic information. The geographic location information can be the same for the two devices, different for the two devices, or the information may be missing from one or the other device. The third and fourth columns contain the status identifiers for the IMD and the PRM respectively. The status identifier can be approved, not approved, approved for clinical study, or missing. The fifth column contains the outcome of applying the rules to the geographic information and the status identifiers. The IMD model number identifies the type of IMD. Changes in a set of active functions in the device are tracked by modifying the model number with a dash number.
Line 1 of the Table shows an example of the simple case of the IMD and PRM containing the same geographic location information and the status identifiers of both devices agree that the function is not allowed in the geographic location. The PRM is allowed to interact with the IMD but not use the function. Line 2 of the Table shows an example of the case where the geographical information is different, but the function is not allowed in either location. The PRM is allowed to interact with the device and the user interface includes a window notifying the user of the geographic difference.
Lines 3 and 4 of the Table show a case where the IMD is a clinical device but the PRM is not part of the clinical study. The function may be allowed if the geographic location of the devices approves use of the function outside of a clinical study setting. In this case, a clinical window is provided on the PRM user interface. If it is not approved, the function is not available. Because the geographic information of the devices differs, a geographic window is provided on the PRM user interface to notify the user of the geographic difference.
Lines 5 and 6 of the Table show examples of rules where the status identifiers conflict or are out of sync. Because the rules are more restrictive, in this example, the function is not allowed in line 5. In line 6 the function is allowed or not allowed depending on the geographical location. Lines 7 through 12 are examples of rules based on the PRM having a clinical status identifier for the function. Lines 13 through 18 are examples of rules where the PRM has an approved status of the function. Lines 13 and 15 show examples of rules where an alarm or other notification is raised because the status identifiers do not match.
Lines 19 through 22 are examples of rules applied when some information is missing. In lines 19 and 20, a status identifier is missing. In such cases, use of the function is not allowed, in one example. Another way to handle the case of missing identifiers is to not allow the PRM to interact with the IMD. This approach is useful if the function has substantial interaction with other functions and the missing information is important to know how to proceed. In line 21, the geographic location information for the PRM is missing. Interaction with the IMD is not allowed until information is entered in the PRM. A special window is displayed for the user to enter geographical information. In line 22, the geographic location information for the IMD is missing. In this case the PRM is not allowed to interact with the IMD. This case may arise when the IMD model is an old configuration or the PRM is not compatible with the IMD.
The Table is intended to show an example of a set of rules applied to stored geographical information, the stored approval information, and the status identifiers. Other examples can be utilized to implement other logical results. For example, other examples implement a set of least restrictive rules. Additionally, a more restrictive implementation may prevent more than just use of a function or set of functions. For example, most restrictive rules may prevent any interaction with the IMD in some circumstances. This is useful where there is substantial interaction between parameters of multiple functions and it is not desirable to allow a user to change some but not all parameters. Other examples of rules do not allow use of the function or functions if the geographic information does not match.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS4236524Nov 6, 1978Dec 2, 1980Medtronic, Inc.Program testing apparatusUS4273133Nov 6, 1978Jun 16, 1981Medtronic, Inc.Programmable digital cardiac pacemaker with means to override effects of reed switch closureUS4407288Mar 16, 1981Oct 4, 1983Mieczyslaw MirowskiImplantable heart stimulator and stimulation methodUS4809697Oct 14, 1987Mar 7, 1989Siemens-Pacesetter, Inc.Interactive programming and diagnostic system for use with implantable pacemakerUS4940052Jan 25, 1989Jul 10, 1990Siemens-Pacesetter, Inc.Microprocessor controlled rate-responsive pacemaker having automatic rate response threshold adjustmentUS5076272Jun 15, 1990Dec 31, 1991Telectronics Pacing Systems, Inc.Autocontrollable pacemaker with alarmUS5080096Jul 6, 1990Jan 14, 1992Medtronic, Inc.Method and apparatus for accessing a nonvolatile memoryUS5113869Aug 21, 1990May 19, 1992Telectronics Pacing Systems, Inc.Implantable ambulatory electrocardiogram monitorUS5127404Sep 25, 1991Jul 7, 1992Medtronic, Inc.Telemetry format for implanted medical deviceUS5217010May 28, 1991Jun 8, 1993The Johns Hopkins UniversityEcg amplifier and cardiac pacemaker for use during magnetic resonance imagingUS5312446Aug 26, 1992May 17, 1994Medtronic, Inc.Compressed storage of data in cardiac pacemakersUS5342408Jan 7, 1993Aug 30, 1994Incontrol, Inc.Telemetry system for an implantable cardiac deviceUS5360437Nov 8, 1993Nov 1, 1994Medtronic, Inc.Implantable medical device with flexible hardware platformUS5387229Jan 21, 1993Feb 7, 1995Pacesetter, Inc.Multi-sensor cardiac pacemaker with sensor event recording capabilityUS5456691Nov 12, 1993Oct 10, 1995Pacesetter, Inc.Programming system having multiple program modulesUS5456692Sep 3, 1993Oct 10, 1995Pacesetter, Inc.System and method for noninvasively altering the function of an implanted pacemakerUS5565005Feb 17, 1993Oct 15, 1996Amei Technologies Inc.Implantable growth tissue stimulator and method operationUS5607458Jul 13, 1995Mar 4, 1997Pacesetter, Inc.Safety optimization in microprocessor controlled implantable devicesUS5626623Apr 30, 1996May 6, 1997Medtronic, Inc.Method and apparatus for optimizing pacemaker AV delayUS5653735Jun 28, 1995Aug 5, 1997Pacesetter, Inc.Implantable cardiac stimulation device having an improved backup mode of operation and method thereofUS5653737Apr 8, 1996Aug 5, 1997Pacesetter, Inc.Programmable pacemaker for noninvasive EP testing for atrial tachycardias with ventricular supportUS5693076Jan 16, 1996Dec 2, 1997Medtronic, Inc.Compressed patient narrative storage in and full text reconstruction from implantable medical devicesUS5722998Jun 7, 1995Mar 3, 1998Intermedics, Inc.Apparatus and method for the control of an implantable medical deviceUS5725559May 16, 1996Mar 10, 1998Intermedics Inc.Programmably upgradable implantable medical deviceUS5735887Dec 10, 1996Apr 7, 1998Exonix CorporationClosed-loop, RF-coupled implanted medical deviceUS5785660Mar 28, 1996Jul 28, 1998Pacesetter, Inc.Methods and apparatus for storing intracardiac electrogramsUS5792201Nov 15, 1996Aug 11, 1998Pacesetter, Inc.Implantable cardiac stimulating deviceUS5792204Jun 13, 1996Aug 11, 1998Pacesetter, Inc.Methods and apparatus for controlling an implantable device programmer using voice commandsUS5800473Feb 7, 1997Sep 1, 1998Ela Medical S.A.Systems, methods, and apparatus for automatic updating of a programmer for an active implantable medical deviceUS5836989Dec 26, 1996Nov 17, 1998Medtronic, Inc.Method and apparatus for controlling an implanted medical device in a time-dependent mannerUS5843138Jul 9, 1997Dec 1, 1998Vitatron Medical, B.V.Pacemaker system with enhanced programmable modification capacityUS5891182May 22, 1997Apr 6, 1999Regeneration TechBio-active frequency generator and methodUS5899931Jun 4, 1997May 4, 1999Ela Medical S.A.Synchronous telemetry transmission between a programmer and an autonomous deviceUS5902325Jul 30, 1998May 11, 1999Medtronic, Inc.Method and apparatus for detecting cardiac captureUS5941906Oct 15, 1997Aug 24, 1999Medtronic, Inc.Implantable, modular tissue stimulatorUS6073049Oct 29, 1997Jun 6, 2000Sulzer Intermedics, Inc.Programmably upgradable implantable cardiac pacemakerUS6088618Jul 7, 1998Jul 11, 2000Vitatron Medical, B.V.Pacemaker system and method for providing manual display concurrent with pacemaker software modificationUS6157859Mar 9, 1998Dec 5, 2000Sulzer Intermedics, Inc.Upgradable implantable medical device with post-shock pacing and redraw functionsUS6200265Apr 16, 1999Mar 13, 2001Medtronic, Inc.Peripheral memory patch and access method for use with an implantable medical deviceUS6243608Jun 12, 1998Jun 5, 2001Intermedics Inc.Implantable device with optical telemetryUS6308099Nov 13, 1998Oct 23, 2001Intermedics Inc.Implantable device and programmer system which permits multiple programmersUS6321117Aug 20, 1999Nov 20, 2001Cardiac Pacemakers, Inc.Change log for implantable medical deviceUS6363282Oct 29, 1999Mar 26, 2002Medtronic, Inc.Apparatus and method to automatic remote software updates of medical device systemsUS6427088Jan 22, 2001Jul 30, 2002Medtronic Minimed, Inc.Ambulatory medical apparatus and method using telemetry system with predefined reception listening periodsUS6512954Oct 16, 2001Jan 28, 2003Intermedics, Inc.Implantable device and programmer system which permits multiple programmersUS6535766Aug 26, 2000Mar 18, 2003Medtronic, Inc.Implanted medical device telemetry using integrated microelectromechanical filteringUS6562001Jan 22, 2001May 13, 2003Medtronic Minimed, Inc.Microprocessor controlled ambulatory medical apparatus with hand held communication deviceUS6564105Jan 22, 2001May 13, 2003Medtronic Minimed, Inc.Method and apparatus for communicating between an ambulatory medical device and a control device via telemetry using randomized dataUS6571128Jan 22, 2001May 27, 2003Medtronic Minimed, Inc.Microprocessor controlled ambulatory medical apparatus with hand held communication deviceUS6577899Jan 22, 2001Jun 10, 2003Medtronic Minimed, Inc.Microprocessor controlled ambulatory medical apparatus with hand held communication deviceUS6584356Jan 5, 2001Jun 24, 2003Medtronic, Inc.Downloadable software support in a pacemakerUS6585644Jan 22, 2001Jul 1, 2003Medtronic Minimed, Inc.Ambulatory medical apparatus and method using a telemetry system with predefined reception listening periodsUS6618618Dec 15, 2000Sep 9, 2003Cardiac Pacemakers, Inc.Cardiac rhythm management system providing control of pacing features with a reduced number of variablesUS6622045Mar 29, 2001Sep 16, 2003Pacesetter, Inc.System and method for remote programming of implantable cardiac stimulation devicesUS6625488Mar 13, 2001Sep 23, 2003Pacesetter, Inc.Implantable cardiac stimulation device having a programmable reconfigurable sequencerUS6635014Jan 22, 2001Oct 21, 2003Timothy J. StarkweatherAmbulatory medical apparatus and method having telemetry modifiable control softwareUS6648821Jan 22, 2001Nov 18, 2003Medtronic Minimed, Inc.Microprocessor controlled ambulatory medical apparatus with hand held communication deviceUS6659948Jan 22, 2001Dec 9, 2003Medtronic Minimed, Inc.Ambulatory medical apparatus and method using a telemetry system with predefined reception listening periodsUS6665565Dec 6, 2000Dec 16, 2003Medtronic, Inc.Method and a system for conducting failure mode recovery in an implanted medical deviceUS6668196Jan 22, 2001Dec 23, 2003Medical Research Group, Inc.Ambulatory medical apparatus with hand held communication deviceUS6681003Jul 16, 2002Jan 20, 2004Lifecor, Inc.Data collection and system management for patient-worn medical devicesUS6687546Jan 22, 2001Feb 3, 2004Medtronic Minimed, Inc.Ambulatory medical apparatus and method using a robust communication protocolUS6694191Jan 22, 2001Feb 17, 2004Medtronic Minimed, Inc.Ambulatory medical apparatus and method having telemetry modifiable control softwareUS6733446Jan 22, 2001May 11, 2004Medtronic Minimed, Inc.Ambulatory medical apparatus and method using a telemetry system with predefined reception listening periodsUS6738670Jun 19, 2000May 18, 2004Medtronic, Inc.Implantable medical device telemetry processorUS6738671Oct 26, 2001May 18, 2004Medtronic, Inc.Externally worn transceiver for use with an implantable medical deviceUS6740075Jan 22, 2001May 25, 2004Medtronic Minimed, Inc.Ambulatory medical apparatus with hand held communication deviceUS6758810Jan 22, 2001Jul 6, 2004Medtronic Minimed, Inc.Ambulatory medical apparatus and method using a robust communication protocolUS6792311Jan 24, 2003Sep 14, 2004Intermedics Inc.Implantable device and programmer system which permits multiple programmersUS6804558Jan 18, 2001Oct 12, 2004Medtronic, Inc.System and method of communicating between an implantable medical device and a remote computer system or health care providerUS6847843Jun 6, 2001Jan 25, 2005Pacesetter, Inc.Method and apparatus for electrophysiological testing in an implantable deviceUS6868288Nov 9, 2001Mar 15, 2005Medtronic, Inc.Implanted medical device telemetry using integrated thin film bulk acoustic resonator filteringUS6882883Aug 31, 2001Apr 19, 2005Medtronic, Inc.Implantable medical device (IMD) system configurable to subject a patient to a stress test and to detect myocardial ischemia within the patientUS7149773Jan 18, 2001Dec 12, 2006Medtronic, Inc.System and method of automated invoicing for communications between an implantable medical device and a remote computer system or health care providerUS7167755Oct 5, 2004Jan 23, 2007Cardiac Pacemakers, Inc.Adaptive software configuration for a medical deviceUS7181505Jan 18, 2001Feb 20, 2007Medtronic, Inc.System and method for remote programming of an implantable medical deviceUS20020032470Oct 26, 1999Mar 14, 2002Kurt R. LinbergApparatus and method for remote troubleshooting, maintenance and upgrade of implantable device systemsUS20020077668Dec 15, 2000Jun 20, 2002James KalgrenCardiac rhythm management system providing control of pacing features with a reduced number of variablesUS20020082665Jan 18, 2001Jun 27, 2002Medtronic, Inc.System and method of communicating between an implantable medical device and a remote computer system or health care providerUS20020143372Mar 29, 2001Oct 3, 2002Snell Jeffery D.System and method for remote programming of implantable cardiac stimulation devicesUS20020177878Mar 13, 2001Nov 28, 2002Poore John W.Implantable cardiac stimulation device having a programmable reconfigurable sequencerUS20030028219Jul 20, 2001Feb 6, 2003Powers Daniel J.Modular medical device, base unit and module thereof, and automated external defibrillator (AED), methods for assembling and using the AEDUS20030088292Nov 4, 2001May 8, 2003Anderson Thomas N.Method and system for programming an implantable cardiac deviceUS20030114897Dec 19, 2001Jun 19, 2003Von Arx Jeffrey A.Implantable medical device with two or more telemetry systemsUS20030139778Jan 22, 2002Jul 24, 2003Fischell Robert E.Rapid response system for the detection and treatment of cardiac eventsUS20030170901Nov 25, 2002Sep 11, 20033M Innovative Properties CompanyElectronic system for tracking and monitoring articles to be sterilized and associated methodUS20030204147Apr 30, 2002Oct 30, 2003Condie Catherine R.Method and apparatus for injection of external data within an implantable medical deviceUS20030220673May 24, 2002Nov 27, 2003Snell Jeffrey D.Multi-device telemetry architectureUS20040064165Sep 30, 2002Apr 1, 2004Thompson David L.Implantable medical device with hardware-based patchUS20040068199Sep 12, 2003Apr 8, 2004The Trustees Of The University Of PennsylvaniaUnified probabilistic framework for predicting and detecting seizure onsets in the brain and multitherapeutic deviceUS20040138724Oct 29, 2003Jul 15, 2004Sieracki Jeffrey M.Failsafe programming of implantable medical devicesUS20040143304Jan 21, 2003Jul 22, 2004Hall Jeffrey A.Recordable macros for pacemaker follow-upUS20040143305Aug 29, 2003Jul 22, 2004Cardiac Pacemakers, Inc.Cardiac rhythm management system providing control of pacing features with a reduced number of variablesUS20040210255Apr 15, 2003Oct 21, 2004Medtronic, Inc.Activation of fibrillation and tachycardia functionsUS20040267233Jun 30, 2003Dec 30, 2004Codman Neuro Sciences SarlSystem and method for controlling an implantable medical device subject to magnetic field or radio frequency exposureUS20050049656Aug 29, 2003Mar 3, 2005Medtronic, Inc.Fail-safe programming for implantable medical deviceUS20050107839Nov 13, 2003May 19, 2005Sanders Richard S.Implantable cardiac monitor upgradeable to pacemaker or cardiac resynchronization deviceUS20060074463Oct 5, 2004Apr 6, 2006Michael SeebergerAdaptive software configuration for a medical deviceWO1991010471A1Jan 15, 1991Jul 23, 1991Medtronic IncImproved telemetry formatNon-Patent CitationsReference1"European Application Serial No. 05800875.6, Official Communication mailed Jan. 29, 2009", 2 pgs.2"European Application Serial No. 05800875.6, Response filed Jun. 3, 2009 to Official Communication mailed Jan. 29, 2009", 20 pgs.3"International Search Report and Written Opinion for Application PCT/US2005/035651, date mailed Feb. 20, 2006", 14 Pages.4"U.S. Appl. No. 10/958,628, Notice of Allowance mailed Sep. 12, 2006", 10 pgs.5"U.S. Appl. No. 10/958,628, Response filed Jun. 29, 2006 to Restriction Requirement mailed May 31, 2006", 8 pgs.6"U.S. Appl. No. 10/958,628, Restriction Requirement mailed May 31, 2006", 6 pgs.Referenced byCiting PatentFiling datePublication dateApplicantTitleUS8639346Oct 26, 2009Jan 28, 2014Cardiac Pacemakers, Inc.Adaptive software configuration for a medical deviceClassifications U.S. Classification607/59International ClassificationA61N1/08Cooperative ClassificationA61N1/37252, G06F19/3406, G06F19/3412European ClassificationG06F19/34A1, G06F19/34A, A61N1/372D8Legal EventsDateCodeEventDescriptionMar 8, 2013FPAYFee paymentYear of fee payment: 4Dec 21, 2010CCCertificate of correctionRotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services