Patent Grant
8812841
The present invention relates generally to systems, devices, and methods for transporting medical information over a network.
Implantable pulse generators (IPGs) are medical devices commonly used to treat irregular heartbeats, known as arrhythmias. Cardiac pacemakers, for example, are designed to manage bradycardia, an abnormally slow or irregular heartbeat. Left untreated, bradycardia can cause symptoms such as fatigue, dizziness, and fainting. Cardiac resynchronizers are a particular class of pacemaker that provide cardiac resynchronization therapy, such a bi-ventricular pacing, for patients suffering from heart failure. Implantable cardioverter defibrillators (ICDs), by way of further example, are designed to treat tachycardia, heart rhythms that are abnormally fast and life threatening. Some forms of tachycardia can result in sudden cardiac death, if left untreated.
Implantable pulse generators are increasingly being equipped with an on-board, volatile memory in which telemetered signals can be stored for later retrieval and analysis. The telemetered signals provide various types of patient device information, such as atrial electrical activity, ventricular electrical activity, time of day, activity level, cardiac output, and any interventions made on a per heartbeat or binned average basis. In addition, a growing class of cardiac medical devices, including implantable heart failure monitors, implantable event monitors, cardiovascular monitors, and therapy devices, are being used to provide similar stored device information. Telemetered signals are also stored in a broader class of monitors and therapeutic devices for other areas of medicine, including metabolism, endocrinology, hematology, neurology, muscular, gastrointestinal, genital-urology, ocular, auditory, and the like.
Information stored in an implantable medical device is typically retrieved using a proprietary interrogator or programmer, often during a clinic visit or following a device event. The volume of data retrieved from a single device interrogation procedure can be large and proper interpretation and analysis can require significant physician time and detailed subspecialty knowledge, particularly by cardiologists and cardiac electrophysiologists. Present approaches to data interpretation and understanding, and practical limitations on time and physician availability, make such analyses impracticable.
Conventional systems for collecting and analyzing pacemaker and ICD telemetered signals in a clinical or office setting can be used to retrieve data, such as patient electrocardiogram and any measured physiological signals, collected by the IPG for recordation, display and printing. The retrieved data may be displayed in chronological order and analyzed by a physician. Conventional systems often lack remote communications facilities and must be operated with the patient present. These systems present a limited analysis of the collected data based on a single device.
The present invention is generally directed to systems, devices, methods, and software that provide for transportation of medical information over a network. In particular, the present invention is directed to systems, devices, methods, and software that provide for secured communications between a multiplicity of portable patient communicators and a central authority over an unsecured network. Embodiments of the invention are directed to hubs, switches, routers, medical device programmers, and other communication devices that can be implemented to facilitate secured transport of patient implantable medical device data between a multiplicity of portable patient communicators and a central authority over an unsecured network.
In accordance with embodiments of the present invention, a communications device is configured to facilitate secured communications between a multiplicity of PPCs and a CA. Each of the PPCs is configured to effect connectivity with a PIMD in accordance with medical firmware or software program instructions implemented by the processor of the PPC. The communications device includes a housing, a logical network port provided at the housing and adapted to facilitate communications between the device and the unsecured network, and a multiplicity of logical local ports provided at the housing and adapted to implement a plurality of disparate communication protocols for effecting connectivity between the device and the plurality of PPCs.
A processor of the device is coupled to the logical network port and the logical local ports. A memory is coupled to the processor and configured to store life critical network software. The LCN software comprises program instructions which, when executed by the processor, cause the processor to determine whether or not entities requesting a network connection via the device are PPCs, authenticate only PPCs to the CA, facilitate communication between the PPCs and the CA via the logical local ports, the logical network port, and the unsecured network upon successful PPC authentication, and transfer PPC data to the CA. At least some of the PPC data comprises PIMD data.
Methods, according to embodiments of the present invention, provide for secured communications between a multiplicity of PPCs and a CA using a communications device via an unsecured network. Method embodiments involve detecting, using a multiplicity of disparate communication protocols implemented by the communications device, presence of each of a plurality of entities requesting a network connection and determining whether or not each of the entities is a PPC. Method embodiments involve establishing, only for the entities determined to be PPCs, a connection to the CA via the unsecured network using the disparate communication protocols implemented by the communications device, authenticating only the PPCs to the CA via the communications device and the unsecured network, and facilitating communication of PPC data between the PPCs and the CA via the communications device and the unsecured network upon successful PPC authentication. The PPC data comprises at least some PIMD data acquired from PIMDs by their respective PPCs.
According to various embodiments of the present invention, a computer-readable medium has instructions stored thereon which are executable by a data processing arrangement disposed in a communications device and capable of being coupled to an unsecured network. Program instructions stored on the computer-readable medium facilitate processor implementation of detecting, using a multiplicity of disparate communication protocols implemented by the communications device, presence of each of a plurality of entities requesting a network connection, determining whether or not each of the entities is a PPC, establishing, only for the entities determined to be PPCs, a connection to the CA via the unsecured network using the disparate communication protocols implementable by the communications device, authenticating only the PPCs to the CA via the communications device and the unsecured network, and facilitating communication of PPC data between the PPCs and the CA via the communications device and the unsecured network upon successful PPC authentication. The PPC data comprises at least some PIMD data acquired from PIMDs by their respective PPCs.
The above summary of the present invention is not intended to describe each embodiment or every implementation of the present invention. Advantages and attainments, together with a more complete understanding of the invention, will become apparent and appreciated by referring to the following detailed description and claims taken in conjunction with the accompanying drawings.
While the invention is amenable to various modifications and alternative forms, specifics thereof have been shown by way of example in the drawings and will be described in detail below. It is to be understood, however, that the intention is not to limit the invention to the particular embodiments described. On the contrary, the invention is intended to cover all modifications, equivalents, and alternatives falling within the scope of the invention as defined by the appended claims.
In the following description of the illustrated embodiments, references are made to the accompanying drawings forming a part hereof, and in which are shown by way of illustration, various embodiments by which the invention may be practiced. It is to be understood that other embodiments may be utilized, and structural and functional changes may be made without departing from the scope of the present invention.
Systems, devices or methods according to the present invention may include one or more of the features, structures, methods, or combinations thereof described herein. For example, a device or system may be implemented to include one or more of the advantageous features and/or processes described below. It is intended that such a device or system need not include all of the features described herein, but may be implemented to include selected features that provide for useful structures, systems, and/or functionality.
A life critical network as described herein is preferably configured as a robust network supported by existing mobile and data networks, and exhibiting heightened communication attributes such as guaranteed delivery, high quality of service (QoS), and tight security. A life critical network implemented in accordance with this disclosure provides for the acquisition of physiologic and contextual data acquired for any number of patients that are each carrying a portable communications device, referred to herein as a portable patient communicator.
Acquisition of physiologic data by a central authority of the life critical network for individual patients may advantageously occur on an unscheduled basis, such as in response to predefined events (e.g., tachycardia events) or in response to patient initiated interrogations. In this regard, a life critical network may acquire patient data for any number of patients that carry a PPC on an event-driven basis, in contrast to a time-scheduled basis.
Patient physiologic data may be acquired by the CA while the patient is ambulatory, such as during daily routines at the home or office, or when traveling locally, nationally or worldwide. Physiologic data for patients may be acquired by a wide variety of sensors, including external and internal sensors. For example, a patient implantable medical device (PIMD), such as a pacemaker or ICD, may acquire physiologic data and transmit such data to the PPC.
Data acquired by the PPC may be transmitted to a CA of the life critical network in real-time, such as by use of a real-time data streaming protocol. Store-and-forward data transfer protocols may also be employed, such as for less critical data or when a real-time data transfer connection is not available. Incremental data transfers may also be performed to reduce the volume of data transferred from the PPC to the CA. A life critical network of the present invention provides connectivity between a patient's PPC and CA that can be dynamically adjusted to meet the needs of the patient, physician, emergency services, and system/technical personnel.
Real-time transfer of patient physiologic data may be triggered by real-time clinical events detected by a sensor or implantable medical device provided with the patient. Data transfers may also be triggered in accordance with query/response protocols. Clinical alerts for high risk patients may be communicated through the life critical network in real-time. Physiologic monitoring for remote triage may be implemented in real-time through the life critical network.
Examples of patient data that may be transferred from the PPC to the CA include electrograms (EGMs), clinical event data, episode counters, alerts, device or sensor settings, battery status, lead measurements, and patient activity level, among other types of data. Data transferred from the PPC to the CA may be integrated at a web site supported by the CA and displayed at a remote location (e.g., physician's office).
Although technically feasible, large scale implementation of an LCN that facilitates network connectivity between a CA and a vast number of PPCs may be hampered by economic considerations, such as costs associated with system/device deployment and communications, as well as uncertainty in governmental reimbursement for such investments. For example, there is increasing pressure to reduce the expense of PPCs and long-term communication costs, particularly the relatively high cost of cellular connectivity.
There is an increasing desire to increase LCN connectivity options afforded PPCs. Certain environments lend themselves to supporting the goals of reduced PPC cost while increasing LCN connectivity. Also, connectivity of a programmer to an LCN has been desired for some time. LCN connectivity can provide an authorized programmer with the ability to obtain software updates and upload initial patient data via an LCN/CA connection, among other capabilities.
Embodiments of the present invention are directed to a communication hub that provides an interface to an LCN for a multiplicity of PPCs that communicate with the hub via a multiplicity of communication protocols. According to various embodiments, an LCN hub of the present invention is a physical device that provides LCN access to PPCs. It is to be understood that the term “hub” as used herein is intended to cover a range of communication devices, including repeaters, switches, and routers, among others. In many embodiment descriptions, the term hub is used interchangeably with such other communications devices.
In this regard, an LCN hub of the present invention is distinguishable from an ordinary network hub, switch or router in that the LCN hub provides LCN access only to PPCs, programmers, or other approved/authorized LCN devices. An LCN hub of the present invention preferably provides varied forms of PPC connectivity to an LCN, such as through both diversified WAN and diversified local LAN ports. An LCN hub of the present invention advantageously permits use of existing network resources in order to effectively extend the LCN to remote and typically ambulatory patients provided with a PPC.
Embodiments of the present invention are directed to a medical device programmer implemented to communicate with a CA via an LCN. Embodiments of an LCN programmer may, in general, be similar to conventional programmers. Unlike a conventional programmer that operates either as a stand-alone system or connects with a private secured network/sever, an LCN programmer of the present invention is itself an entity that connects to the LCN via unsecured networks (e.g., the Internet) and can further be implemented to act as an LCN hub. An LCN programmer can act as a data collection facility for PPCs.
For example, an LCN programmer may be stationed in a hospital ER or in the waiting room of a clinic, and can triage implantable medical device patients as they enter the door of the facility. For example, an LCN programmer stationed at an ER entrance can detect presence of the patient's PPC, automatically interrogate the PPC, authenticate and connect the PPC with the LCN, and upload data acquired from the PPC/implanted medical device to a CA via the LCN.
A secured LCN provider preferably prevents entities other than approved entities from gaining access to the LCN. In the context of an Internet-based implementation, a secured provider will not provide an LCN IP address to any entity other than for example, a PPC, LCN hub, an LCN programmer, or a generic hub or switch that is provided with and executes authorized LCN operating and security software, thereby operating as a secured LCN hub or switch.
For example, an LCN hub or programmer, when equipped with 802.11, Bluetooth, or USB via a local logical port, can use any number of authentication protocols to allow PPC access to the LCN. One such protocol is 802.1X or Extensible Authentication Protocol (EAP). The specific EAP authentication method is one of many possible methods, and includes pre-shared keys and a Remote Authentication Dial In User Service (RADIUS) network protocol. Authentication is provided through contact with the CA, located on the LCN.
An LCN hub of the present invention allows medical device manufacturers, clinics, and physicians to leverage existing network infrastructures in order to provide LCN access to a vast number of PPCs associated with a vast number of patients. Advantages afforded embodiments of the present invention include reductions in patient/medical device data transmission costs. This is especially pertinent in high-density environments such as nursing homes. Reductions in the cost of PPC manufacturing and deployment are also realizable, due to use of less expensive technologies such as Bluetooth. Enhanced features are provided by embodiments that employ LCN programmers for connecting with a CA, and provides additional benefits for hospitals, clinics, and patients.
Embodiments of the present invention are directed to a modular PPC. A modular PPC typically includes sufficient hardware and software to be able to interrogate an implantable medical device (e.g., IPG or other CRM device). Preferably, a modular PCC of the present invention is implemented to incorporate communications circuitry to communicate with the implantable medical device, but excludes a built-in communications facility that, by itself, can communicate with external devices, systems and networks. In other words, communications between the modular PPC and an external device, system or network can be effected only by physically connecting a communications-enabled module or communications cable/connector to a communications interface socket of the PPC. A modular PPC according to embodiments of the invention is purposefully implemented with a reduced capability for effecting communications that rely on built-in protocols. This reduced communications capability provides advantages of reduced PPC build costs and future-proofing the PPC from communication protocols that can become outmoded or obsolete.
These and other advantages of a modular PPC of the present invention are realized by employment of a “universal” communications port. Preferably, a universal communications port of the modular PPC, such as a USB or FireWire™ port, provides a hardware mechanism to access external devices and systems, including an LCN and CA. The universal nature of the modular PPC's communications port allows the PPC to communicate using a wide variety of wireless and wired protocols, such as Bluetooth, 802.11, WiMax, Cellular, Ethernet, FireWire™, and POTS, among others. The universal communications port of a modular PPC may also receive a communications interface connector of a wide variety of devices, such as memory devices (e.g., a memory stick or thumb drive) and sensors, for example, which can expand the functionality of a PPC.
In some embodiments, a modular PPC may be configured as a “universal” host (e.g., USB host). In other embodiments, a modular PPC may be configured as a “universal” host and a “universal” device (e.g., USB device). For purposes of simplicity, and not of limitation, the term USB (Universal Serial Bus) is used herein to denote a port, interface, socket, device, peripheral, host and the like that is “universal” in terms of connectivity. A typical universal communications port of a modular PPC is configured as a serial bus that facilitates connectivity between the PPC and a wide variety of modules, devices, peripherals, systems, and networks.
A universal communications port of a modular PPC is typically a single standardized interface socket that facilitates plug-and-play capabilities by enabling hot swapping, thereby allowing devices to be connected and disconnected to the PPC without rebooting the PPC processor or turning off the PPC. A universal communications port of a modular PPC typically provides power to low-power consumption devices that are connected to the port, thus eliminating the need for the connecting device to includes its own power supply. A universal communications port of a modular PPC advantageously allows many different devices to be connected to the PPC without requiring manufacturer-specific device drivers to be installed.
As previously discussed, a modular PPC according to various embodiments can operate as both a USB device and USB host. According to some embodiments, a USB-OTG (On-the-Go) protocol may be employed by a modular PPC to provide USB device and host functionality. A USB-OTG protocol (USB 2.0 Specification, promulgated by the USB Implementer Forum) is a standard USB that uses a master/slave architecture. In this context, a USB device (e.g., a PPC) can act as both a protocol master and a protocol slave.
Embodiments of a modular PPC can be implemented as a USB host to manage LCN connectivity options, such as Bluetooth, 802.11, WiMax, Cellular, Ethernet, FireWire™, and POTS, for example. A wide variety of detectable modules equipped with a universal port (e.g., USB interface) can be selectably attached to the universal communications port of the PPC. Examples of such detachable modules include memory sticks, thumb drives, physiologic sensors (temperature, blood pressure, blood gas saturation, heart rate, body fat, weight scale), and other external add-on modules. Alternatively, or in addition, the functionality of certain detachable modules may be implemented internally within the PPC, through selective component PCB population and provision of necessary components on the PPC or external element (e.g., electrodes or IR sensor on the PPC housing).
A PPC according to embodiments of the present invention preferably implements LCN software that enables communications between a patient implantable medical device and a central authority via an unsecured network, such as the Internet. In some embodiments, the PPC effects secured communications with a CA by way of a generic (general purpose) network access device. In other embodiments, the PPC effects secured communications with a CA by way of a special purpose network access device, such as an LCN hub or an LCN programmer (or other authorized communications device/system—generic or non-generic—that implements LCN software).
The PPC preferably implements LCN software that provides secured communications with a PIMD and with the central authority. For example, programming instructions of the LCN software executed by a processor of the PPC facilitates connection of the PPC to an unsecured network, authentication of the PPC to the central authority, and transfer of data between the PPC and the central authority. In this regard, the LCN software allows PPCs to communicate to a secure central authority via a life critical network supported by an unsecured network (e.g., the Internet).
According to other embodiments, a PPC may be configured with software that recognizes a special dongle, such as a USB dongle. A dongle generally refers to a small piece of hardware that detachably connects to a computer via a universal interface (e.g., a USB port). Dongles are often implemented to appear as two-interface security tokens with transient data flow that does not collide with the dongle function and a pull communication that reads security data from the dongle. An important function of a dongle is to authenticate a piece of software. Without the dongle, this software will not execute or only does so in a restricted mode.
A USB dongle, according to embodiments of the invention, stores a unique code in a secure area of the dongle that uniquely identifies the dongle as a “PPC key device.” The USB dongle is preferably universal in configuration and protocol, and enables PPC special modes. There may be different versions of the dongle that allow a tier of special features on the PPC as security allows. A USB “programming” dongle may be implemented that enables any number of programming capabilities, such as temporarily deactivating an implanted medical device.
A modular PPC of the present invention provides a number advantages, including providing a medical device manufacturer the ability to customize PPCs based on patient need. A modular PPC of the present allows a medical device manufacture the ability to customize PPCs based on device cost requirements (e.g., bradycardia patients—lower cost vs. tachycardia patients—higher cost). A modular PPC of the present provides a medical device manufacture the ability to rapidly adopt new network/server connectivity options as future technologies become available/prevalent.
Embodiments of the invention are directed to systems that are configured to incorporate combinations of PPCs (e.g., modular and non-modular), LCN hubs, and LCN programmers. Some embodiments may include, for example, PPCs and LCN hubs, while others may incorporate PPCs and LCN programmers. Some systems may incorporate LCN hubs and LCN programmers. Other system deployments may incorporate PPCs, LCN hubs, and LCN programmers. These and other combinations of PPCs, LCN hubs, and LCN programmers may be incorporated in systems that include a central authority (e.g., advanced patient management system) and/or LCN infrastructure. It is understood that PPCs, LCN hubs, and LCN programmers are intended to include generic forms of these devices that are modified or upgraded to include appropriate PPC and/or LCN operating system and security software as described herein.
A PPC implemented in accordance with the present invention facilitates acquisition of implantable medical device data and/or patient sensor by a remote system for ambulatory patients. A PPC of the present invention is preferably configured (via internal components or preferably by components of a module connected to a universal port of the PPC) to communicate over existing mobile and/or ground-based data networks, and to effect local wired or wireless communication with one or more internal and/or external physiologic sensors, ambient and/or contextual sensors, implantable medical devices, and/or other external systems or devices.
A PPC of the present invention may be implemented to provide a wide spectrum of capabilities and functionality. For example, the PPC may be configured to provide only a limited number of features, such as in the case of a PPC having a reduced feature set (low-cost configurations). By way of further example, a PPC may be implemented to provide a variety of features and capabilities that enable a wide range of functionality (higher cost configurations).
According to some embodiments, a PPC may provide limited functionality to achieve low cost and future-proofing objectives. For example, a PPC provided with a universal communications port need not be equipped with an internal cellular or other relatively expensive communications device to communicate with an external device, system, or network. Rather, a communications module may be connected to the PPC's universal communications port to effect wired or wireless connectivity with an external device, system, or network.
According to other embodiments, a PPC may be dynamically configurable via interaction with a central authority or an LCN programmer. Dynamically altering the configuration of a PPC serves to enhance cooperative operation between the PPC, implantable medical device/sensor, and the central authority, an embodiment of which is referred to herein as an advanced patient management system or server. Illustrative examples of an APM server system include a remote patient monitoring system and a patient monitoring system that need not be remote relative to the patient's location. Dynamically altering the configuration of a PPC may also serve to conserve power of the implantable medical device or sensor(s) that are communicatively coupled to the PPC.
The life critical network 200 essentially provides a private or secured network that is configured to operate on top of existing unsecured mobile and fixed facility networks. The LCN 200 utilizes a secured architecture providing for authentication and management of those components that are allowed access to the network 200. Such components or nodes include, for example, PPCs 14 (modular and non-modular), LCN hubs 19, LCN programmers 23, patient sensors 17A-17B, clinician mobile devices 25, clinician workstations 27, patient advocate mobile devices 21, among others.
The LCN 200 preferably follows cryptographic best practices with regard to confidentiality, integrity, and availability. Given the computational—versus-power requirements, the LCN system 200 can minimize the number of asymmetric cryptographic operations in favor of a symmetric algorithm based on various factors, including a known shared-secret generated or installed at time of manufacture, and a dynamically shifting key based on a seed fed to a pseudo random number generator (e.g., such as model, serial number, and network time).
The LCN system 200 preferably leverages the physical network as a virtualized transport, essentially treating any underlying protocol as potentially unsecured, and thus not relying on any native security mechanisms inherent in any given protocol with regard to the encryption and integrity of its data. The LCN system 200 preferably supports both stateful and stateless connections in order to facilitate asynchronous communication where network bandwidth does not support real-time communication.
The LCN 200, as shown in the embodiment of
The various entities requesting access to the LCN 200 are granted different access rights based on their classification. For example, a low-urgency sensor device 17A-17B or PPC 14 may not be given access to high-speed connectivity if it is classified in a lower urgency or priority tier. A patient implantable medical device programming system 23 may be granted priority access to a higher speed connectivity capability due to its more demanding need for timely interconnection to the infrastructure. This classification and prioritization is preferably dynamically managed via the CA 16. Additional details regarding the LCN implementations shown in
A PPC 800 configured to have a reduced set of features advantageously reduces the complexity and cost of the device, and enhances acceptance of the device by less sophisticated users. A PPC 800 having a reduced set of features also provides for lower power consumption, such as by minimizing or eliminating high power consuming components, such as a color display or other user interface components. The PPC 800 may also be implemented to incorporate a variety of features and capabilities that provide for a wide range of functionality, an example of which is shown in
The button 801 may provide basic functionality, such as initiating patient-interrogated transmissions and PIMD pairing/re-pairing procedures. The button 801 may also be actuated by the patient for indicating a distress condition of the patient, to which an emergency service may respond (e.g., 911 alert/call). The reduced feature set PPC 800 may exclude a keypad or other more sophisticated user input device. In some configurations, the button 801 may be a multi-functional button (e.g., contact sensitive switch, multi-state switch or rocker switch).
Button activation for controlling PPC functions may include one or more of a quick click, a double click, and a long hold. A button clicking scheme may be developed to perform a variety of operations, including initiating a PIMD 802 interrogation when the patient feels poorly, initiating a connection to the LCN and central authority (e.g., APM server or system), and initiating delivery of a message to pre-determined parties (e.g., physician, neighbors, friends, children, relatives, emergency response service) to alert the recipient that the patient is in distress or need of attention.
A more sophisticated PPC 800 is shown in
The PPC 800 shown in
In general terms, the hub 201 is configured to effect secured communications between a multiplicity of PPCs 800 and the CA 850. The PPCs 800 are adapted to effect connectivity with the CA 850 via an unsecured network 830 (e.g., the Internet) using a multiplicity of disparate communication protocols. The hub 201 includes a housing 209 which houses/supports a number of components. Provided at the housing 209 is a universal communications port 857 which includes a socket configured to receive a properly configured connector or detachable module 859 (depicted as a dashed block for purposes of illustration).
The universal communications port 857 preferably includes a mechanical retention arrangement to provide secured detachable engagement with a properly configured connector or detachable module 859. The universal communications port 857 typically includes contacts that electrically couple to corresponding electrical contacts of the connector or detachable module 859. The universal communications port 857 may alternatively or additionally incorporate an optical communications interface. In addition to signal connectivity provided between the PPC 800 and a detachable module, the universal communications port 857 may also provide power for the detachable module, such as in conformance with a USB port specification.
A logical network port 204 is provided at the housing 209 and adapted to effect communications between the hub 201 and the CA 850 via the unsecured network 830. A multiplicity of logical local ports 210 are provided at the housing 209 and adapted to implement the various disparate communication protocols for effecting connectivity between the hub 201 and the multiplicity of PPCs 800. Memory 203 is provided at the housing and coupled to a processor 205.
The memory 203 is configured to store life critical network software 202 comprising program instructions which, when executed by the processor 250, cause the processor 250 to determine that entities requesting a network connection via the hub 201 are PPCs 800. The processor 250, when executing LCN software 202, authenticates requesting PPCs 800 to the CA 850, and enables communication between the PPCs 800 and CA 850 via the logical local ports 210 and the logical network port 204 upon successful authentication.
The logical local ports 210 facilitate communication between the PPCs 800 and the hub 201 using a variety of different protocols. Preferably, the logical local ports 210 facilitate short-range wireless connectivity between the PPCs 800 and the hub 201, although wired connectivity may be provided. By way of non-limiting example, and as shown in
The LCN software 202 resides in memory 203 and comprises program instructions that are executed by processor 250 to perform various tasks, including PPC recognition, establishing network connections, authenticating PPCs 800 to the CA 850, and facilitating data transport between the PPCs 800 and the CA 850 via the logical local ports 210 and logical network port 204, among other tasks. For example, the LCN software 202, when executed by processor 250, provides a connection mapping and authentication to the CA only for entities that are determined by the processor 250 to be PPCs. LCN software 202 executed by the processor 250 preferably effects interrogation of PPCs 800 coming into proximity with the hub 201 and automatic authentication of the PPCs 800 with the CA 850. Execution of the LCN software 202 by the processor 205 preferably effects transfer of PIMD/PCC data to the CA 850 as part of PPC interrogation.
If the detected entity is a PPC, the hub establishes 410 a network connection to the central authority via the logical network port of the hub. The hub facilitates 412 authentication of the PPC for use on the LCN, and access 414 to the central authority by the PPC. Authorized operations may then be performed 416 as between the PPC and central authority, such as interrogations, data transfers, and software updates.
A hub 201 implemented in accordance with
The memory 203 of the hub 201 shown in
In this case, the hub establishes 542 a network connection to the central authority via the logical network port of the hub using the LCN software executed by the hub's processor. The hub facilitates authentication 544 of the PPC, access 546 to the central authority by the PPC, and performance 548 of various operations as between the central authority and the authenticated PPC.
If the hub determines that the detected entity is not a PPC or other LCN authorized entity, the hub manages 520 connectivity of the non-LCN authorized entity using the general network/Internet access and security software executed by the hub's processor. In this case, the hub establishes 522 a network/Internet connection to a target resource via the logical network port of the hub using the general software executed by the hub's processor. The hub facilitates authentication and/or authorization 524 of the entity, connection and/or access 526 to the target resource by the entity, and performance 528 of various operations as between the target resource and the entity.
Embodiments according to
The router/switch 302 shown in
In the representative embodiment shown in
Turning now to
The programmer 350 shown in
For each PPC (or LCN authorized entity) that comes 602 into proximity with the programmer, the programmer detects 604 presence of the PPC using one of a multiplicity of logical local ports supporting disparate communication protocols. The programmer interrogates 606 the PPC and receives data from the PPC. Preferably, the programmer transmits a request to the PPC that the PPC perform an interrogation of the PIMD. The PPC's processor executes medical firmware program instructions to securely interrogate the PIMD and acquire PIMD data from a patient's implantable medical device, preferably in compliance with the Health Insurance Portability and Accountability Act (HIPPA) and other laws and regulations that can require special procedures for handling of medical data (e.g., requirements of an FDA Class III medical device).
The PPC data typically includes data acquired from a patient's implantable medical device and, in some embodiments, other implantable or external sensors/devices by the PPC. This data is preferably encrypted or otherwise secured by the PPC (or the PIMD) so that the programmer is initially unable to decipher most or all of the data received from the PPC. The interrogation of the PPC/PIMD generally occurs in real-time with the programmer communicatively coupled to the LCN/CA. The interrogation may also be conducted and PPC/PIMD data collected 608 by the programmer in cases where the programmer is not connected to the LCN/CA or such connection is intermittent or of poor quality.
When connected to the LCN/CA, the programmer transmits 610 the secured PPC data to the CA via the LCN. The CA decrypts and processes 612 the received PCC data. The CA encrypts or otherwise secures the processed PPC data and then transmits 612 this data back to the programmer. The programmer may then access 614 the CA-processed PPC data, such as for presentation on the programmer's display and/or printing via the programmer's printer. The CA-processed PPC data received from the CA by the programmer may include patient and/or PIMD data that may be accessed by the programmer. Various operations impacting the programmer, PPC, and/or the PIMD may be implemented via communications between the CA and the PPC, such as software updates.
For each PPC (or LCN authorized entity) that comes 640 into proximity with the programmer, the programmer detects 642 presence of the PPC using one of a multiplicity of logical local ports supporting disparate communication protocols. The programmer initiates PPC/PIMD interrogation, which preferably involves the programmer transmitting a signal to the PPC requesting the PCC to interrogate its PIMD. Data acquired and/or produced by the PPC is preferably encrypted or otherwise secured 650 by the PPC so that the programmer is initially unable to decipher most or all of this data. According to one approach, the PPC encrypts the PPC data using the CA's public key. This ensures that only the CA can decrypt the PPC data. Interrogation of the PPC/PIMD generally occurs in real-time with the programmer communicatively coupled to the LCN/CA. The interrogation may also be conducted and PPC/PIMD data collected 648 by the programmer in cases where the programmer is not connected to the LCN/CA or such connection is intermittent or of poor quality.
In cases where the programmer has a legitimate need for the PPC data (e.g., when PIMD data is needed by an ER physician), the programmer generates 646 a unique session ID code and transmits the session ID code to the PPC. The session ID code is amended 650 to the PPC data prior to encryption. Generation and use of a session ID code is considered optional, since it is contemplated that, in many instances, the programmer will be used to communicate PPC data to the CA without need for local displaying or printing of the PPC data.
The programmer, if not already connected, establishes 652 connectivity with, and authenticates to, the CA via an LCN connection. The programmer transmits 654 the secured PPC data to the CA via the LCN. In cases where a session ID code is generated, this code is incorporated in the secured PPC data that is transmitted from the programmer to the CA. In some embodiments, the PPC, rather than the programmer, connects and authenticates with the CA via the LCN, and transmits the PPC data (and any programmer data) to the CA. In some configurations, the programmer and the PPC are capable of facilitating transmission of PPC data between the PPC and the CA, thereby providing redundancy in PPC-to-CA connectivity options. In other configurations, only the PPC (and not the programmer) is capable of facilitating transmission of PPC data between the PPC and the CA, which may be the case in reduced cost programmer implementations.
The CA decrypts 656 the secured PPC data, preferably by use of the CA's private key, and performs processes 656 to ensure that the PPC data is associated with an authorized PPC and that the received PPC data includes a session ID code, if any. The CA associates the received PPC data with a patient record, and appends the received PPC data to the patient's data record file.
In cases where the programmer has a legitimate need for PPC data, the programmer (directly or indirectly via the PPC), if not already connected, establishes 658 a connection with, and authenticates to, the CA. The programmer provides the session ID code to the CA. The CA returns the PPC data (and possibly patient or other data) to the programmer in an unencrypted format. The unencrypted PPC data received from the CA may be accessed 660 at the programmer, such as for presentation on the programmer's display or printer for review by a clinician or physician. If other data is included with the unencrypted PPC data, such as trended PIMD data and other patient information, the data may also be accessed 662 at the programmer, such as for displaying or printing. Various operations impacting the programmer, PPC, and/or the PIMD may be implemented via communications between the CA and the programmer/PPC, such as software updates.
Embodiments of the invention implemented in accordance with
The PPC 800 shown in
The module 940, for example, is tailored for conducting cardiac monitoring for Patient #1. In this representative illustration, Patient #1 has a fairly benign form of cardiac arrhythmia (e.g., PVCs, PACs), which requires minimal monitoring by the patient's physician (via the LCN/CA). As such, module 940 includes an Ethernet communications facility and a memory stick. The memory stick provides extra memory for storing PIMD data acquired by the PPC 800, and the Ethernet communications facility allows for LCN/CA connectivity, which may be relatively infrequent for Patient #1.
The module 942 is tailored for Patient #2, who has a bradycardia condition. Patient #2 may require more frequent monitoring by the physician. As such, module 942 is equipped with two different communications facilitates which, in this example, include a wireless facility (802.11) and a wired communications facility (Ethernet). Patient #3, by way of further example, has a more serious Ischemia condition, which requires an increased number of connectivity options for connecting with the LCN/CA. In this representative example, the module 946 for Patient #3 includes a cellular and short-range wireless (802.11) communications facility. Patient #4 has a relatively serious ventricular tachycardia condition, which requires an increased number of connectivity options for connecting with the LCN/CA. As such, the module 948 for Patient #4 includes three different communications facilities, including cellular, short-range wireless (802.11), and Bluetooth communications facilities.
Patient #5 has a progressive heart failure condition which is treated using a CRT device. Module 950 is tailored to provide enhanced features for this patient. In this illustrative example, Patient #5 is relatively immobile, living in a nursing facility that provides WiFi Internet access. The module 950 for Patient #5 need only include a single short-range wireless communications capability (802.11). However, Patient #5 requires frequent monitoring of blood pressure, heart rate, and other sensor information (e.g., weight scale data, respiration data, blood gas saturation data, etc.). The module 950 includes a Bluetooth communications facility to effect connectivity between the PPC 800 and various sensors, such as sensors 952 and 954. Data acquired by the PPC 800 for each of the patient scenarios shown in
In the illustrative embodiment shown in
According to embodiments consistent with
The memory of the dongle preferably stores a unique code that uniquely identifies the dongle as an authorized PPC device. The memory of the dongle also stores program instructions which, when executed by the computer, enable predetermined modes of the PPC, such as programming modes, interrogation modes, diagnostics modes, software/firmware update modes (e.g., for updates, upgrades, patches), and other modes affecting the functionality and/or operation of the PPC. The dongle software may enable “programmer-like” capabilities on the computer, such as PIMD data review, displaying, printing, or outputting to another device, system, or network. The dongle software may enable a computer (e.g., laptop, PDA, tablet PC) to operate as an LCN hub or an LCN programmer as described hereinabove.
According to various embodiments, including those described hereinabove, components of a life critical network may incorporate various methodologies for providing secure and reliable communication, including features described in one or more of the following references: U.S. Patent Publication Nos. 20070118188 and 20070083246, and U.S. Pat. Nos. 7,218,969; 7,203,545; 8,041,032; 8,027,727; 8,160,704; 7,801,620; 7,805,199; 7,218,969; and 7,751,901, all of which are incorporated herein by reference. Data originating at the PPC may be stored and/or analyzed at the central authority, which may include an APM server system, and which may be further coupled to one or more client stations to perform input and output functions. Methods, structures, and/or techniques described herein, may incorporate various APM server system related methodologies, including features described in one or more of the following references: U.S. Pat. Nos. 6,221,011; 6,270,457; 6,277,072; 6,280,380; 6,312,378; 6,336,903; 6,358,203; 6,368,284; 6,398,728; and 6,440,066, which are hereby incorporated herein by reference. Data acquired from a PIMD by a PPC and stored in an APM server may be transferred to, and incorporated within, an electronic medical records system, such as that disclosed in commonly owned U.S. Patent Publication No. 20070226013, which is incorporated herein by reference.
Using the description provided herein, embodiments of the invention may be implemented as a machine, process, or article of manufacture by using standard programming and/or engineering techniques to produce programming software, firmware, hardware or any combination thereof. Any resulting program(s), having computer-readable program code, may be embodied on one or more computer-usable media such as resident memory devices, smart cards or other removable memory devices, or transmitting devices, thereby making a computer program product or article of manufacture according to the invention. As such, the terms “article of manufacture,” “computer program product,” “computer-readable media” and other similar terms as used herein are intended to encompass a computer program that exists permanently or temporarily on any computer-usable medium or in any transmitting medium which transmits such a program.
As indicated above, memory/storage devices include, but are not limited to, disks, optical disks, removable memory devices such as smart cards, SIMs, WIMs, semiconductor memories such as RAM, ROM, PROMS, etc. Transmitting mediums include, but are not limited to, transmissions via wireless/radio wave communication networks, the Internet, intranets, telephone/modem-based network communication, hard-wired/cabled communication network, satellite communication, and other stationary or mobile network systems/communication links.
By way of example, and in accordance with various embodiments, a computer-readable medium of the present invention includes instructions stored thereon which are executable by a data processing arrangement disposed in a modular PPC. The program instructions stored on the medium causes the data processing arrangement to establish signal connectivity between a universal communications port of the PPC and at least one detachable module of a multiplicity of disparate detachable modules when mechanically connected to the universal communications port. At least some of the detachable modules are configured to provide the PPC with an external communications facility and have disparate communication protocols. The PPC is preferably devoid of a facility to effect external communications other than by way of a radio and the universal communications port of the PPC. The program instructions stored on the medium causes the data processing arrangement to execute life critical network (LCN) software stored on the medium to cause the PPC in cooperation with the at least one detachable module to transmit a request to a network access facility for a connection to an unsecured network, facilitate authentication of the PPC to a central authority (CA), and facilitate secured communication between the PPC and CA upon successful PPC authentication
From the description provided herein, those skilled in the art are readily able to combine software created as described with appropriate general purpose or special purpose computer hardware to create a system and/or device and/or subcomponents embodying aspects of the invention, and to create a system and/or device and/or subcomponents for carrying out the methods of the invention.
Various modifications and additions can be made to the preferred embodiments discussed hereinabove without departing from the scope of the present invention. Accordingly, the scope of the present invention should not be limited by the particular embodiments described above, but should be defined only by the claims set forth below and equivalents thereof.
This application claims the benefit of Provisional Patent Application Ser. No. 61/157,455, filed on Mar. 4, 2009, to which priority is claimed pursuant to 35 U.S.C. §119(e) and which is hereby incorporated herein by reference, and is related to Provisional Patent Application Ser. Nos. 60/967,060, 60/967,061, 60/967,062, and 60/967,063 respectively filed on Aug. 31, 2007; 61/128,583, filed on May 22, 2008; and 61/157,451, filed on Mar. 4, 2009; and to Non-Provisional U.S. patent application Ser. No. 12/151,869, issued Jul. 12, 2011 as U.S. Pat. No. 7,978,062, U.S. patent application Ser. No. 12/151,780, issued Aug. 20, 2013 as U.S. Pat. No. 8,515,547, U.S. patent application Ser. No. 12/151,910, issued Mar. 12, 2013 as U.S. Pat. No. 8,395,498, U.S. patent application Ser. No. 12/151,796, filed on May 9, 2008; and 12/228,915 filed on Aug. 18, 2008; and all of which are hereby incorporated herein by reference in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4211235 | Keller et al. | Jul 1980 | A |
| 5012411 | Policastro et al. | Apr 1991 | A |
| 5033286 | Guardiani | Jul 1991 | A |
| 5047930 | Martens et al. | Sep 1991 | A |
| 5113869 | Nappholz et al. | May 1992 | A |
| 5293642 | Lo | Mar 1994 | A |
| 5336245 | Adams et al. | Aug 1994 | A |
| 5339824 | Engira | Aug 1994 | A |
| 5383915 | Adams | Jan 1995 | A |
| 5400246 | Wilson et al. | Mar 1995 | A |
| 5438983 | Falcone | Aug 1995 | A |
| 5462051 | Oka et al. | Oct 1995 | A |
| 5464012 | Falcone | Nov 1995 | A |
| 5465082 | Chaco | Nov 1995 | A |
| 5522396 | Langer et al. | Jun 1996 | A |
| 5579775 | Dempsey et al. | Dec 1996 | A |
| 5620472 | Rahbari | Apr 1997 | A |
| 5634468 | Platt et al. | Jun 1997 | A |
| 5674249 | de Coriolis et al. | Oct 1997 | A |
| 5720770 | Nappholz | Feb 1998 | A |
| 5720771 | Snell | Feb 1998 | A |
| 5749907 | Mann | May 1998 | A |
| 5752976 | Duffin et al. | May 1998 | A |
| 5759199 | Snell | Jun 1998 | A |
| 5827180 | Goodman | Oct 1998 | A |
| 5867821 | Ballantyne et al. | Feb 1999 | A |
| 5873040 | Dunn et al. | Feb 1999 | A |
| 5880867 | Mahany | Mar 1999 | A |
| 5891178 | Mann et al. | Apr 1999 | A |
| 5899855 | Brown | May 1999 | A |
| 5904708 | Goedeke | May 1999 | A |
| 5959529 | Kail et al. | Sep 1999 | A |
| 6050940 | Braun et al. | Apr 2000 | A |
| 6083248 | Thompson | Jul 2000 | A |
| 6088594 | Kingdon et al. | Jul 2000 | A |
| 6093146 | Filangeri | Jul 2000 | A |
| 6095985 | Raymond et al. | Aug 2000 | A |
| 6161095 | Brown | Dec 2000 | A |
| 6221011 | Bardy | Apr 2001 | B1 |
| 6225901 | Kail, IV | May 2001 | B1 |
| 6270457 | Bardy | Aug 2001 | B1 |
| 6277072 | Bardy | Aug 2001 | B1 |
| 6280380 | Bardy | Aug 2001 | B1 |
| 6282441 | Raymond et al. | Aug 2001 | B1 |
| 6287252 | Lugo | Sep 2001 | B1 |
| 6292687 | Lowell et al. | Sep 2001 | B1 |
| 6312378 | Bardy | Nov 2001 | B1 |
| 6325756 | Webb et al. | Dec 2001 | B1 |
| 6330426 | Brown et al. | Dec 2001 | B2 |
| 6336903 | Bardy | Jan 2002 | B1 |
| 6353761 | Conley et al. | Mar 2002 | B1 |
| 6358203 | Bardy | Mar 2002 | B2 |
| 6363282 | Nichols et al. | Mar 2002 | B1 |
| 6368284 | Bardy | Apr 2002 | B1 |
| 6377843 | Naydenov et al. | Apr 2002 | B1 |
| 6396416 | Kuusela et al. | May 2002 | B1 |
| 6398727 | Bui et al. | Jun 2002 | B1 |
| 6398728 | Bardy | Jun 2002 | B1 |
| 6402691 | Peddicord et al. | Jun 2002 | B1 |
| 6405083 | Rockwell et al. | Jun 2002 | B1 |
| 6406426 | Reuss et al. | Jun 2002 | B1 |
| 6411840 | Bardy | Jun 2002 | B1 |
| 6413213 | Essenpreis et al. | Jul 2002 | B1 |
| 6418346 | Nelson et al. | Jul 2002 | B1 |
| 6428475 | Shen | Aug 2002 | B1 |
| 6434429 | Kraus et al. | Aug 2002 | B1 |
| 6440066 | Bardy | Aug 2002 | B1 |
| 6442432 | Lee | Aug 2002 | B2 |
| 6450953 | Place et al. | Sep 2002 | B1 |
| 6453200 | Koslar | Sep 2002 | B1 |
| 6456256 | Amundson et al. | Sep 2002 | B1 |
| 6466819 | Weiss | Oct 2002 | B1 |
| 6470215 | Kraus et al. | Oct 2002 | B1 |
| 6477363 | Ayoub et al. | Nov 2002 | B1 |
| 6477424 | Thompson et al. | Nov 2002 | B1 |
| 6480745 | Nelson et al. | Nov 2002 | B2 |
| 6485418 | Yasushi et al. | Nov 2002 | B2 |
| 6497655 | Linberg et al. | Dec 2002 | B1 |
| 6512944 | Kovtan et al. | Jan 2003 | B1 |
| 6544171 | Beetz et al. | Apr 2003 | B2 |
| 6544173 | West et al. | Apr 2003 | B2 |
| 6553262 | Lang et al. | Apr 2003 | B1 |
| 6556871 | Schmitt et al. | Apr 2003 | B2 |
| 6558320 | Causey, III et al. | May 2003 | B1 |
| 6564104 | Nelson et al. | May 2003 | B2 |
| 6564108 | Makar et al. | May 2003 | B1 |
| 6569095 | Eggers | May 2003 | B2 |
| 6574509 | Kraus et al. | Jun 2003 | B1 |
| 6574510 | Von Arx et al. | Jun 2003 | B2 |
| 6574742 | Jamroga et al. | Jun 2003 | B1 |
| 6577899 | Lebel et al. | Jun 2003 | B2 |
| 6584356 | Wassmund et al. | Jun 2003 | B2 |
| 6591242 | Karp et al. | Jul 2003 | B1 |
| 6599250 | Webb et al. | Jul 2003 | B2 |
| 6602191 | Quy | Aug 2003 | B2 |
| 6609023 | Fischell et al. | Aug 2003 | B1 |
| 6609115 | Mehring | Aug 2003 | B1 |
| 6611206 | Eshelman et al. | Aug 2003 | B2 |
| 6614406 | Amundson et al. | Sep 2003 | B2 |
| 6622043 | Kraus et al. | Sep 2003 | B1 |
| 6622044 | Bange et al. | Sep 2003 | B2 |
| 6622050 | Thompson | Sep 2003 | B2 |
| 6650939 | Taepke, II et al. | Nov 2003 | B2 |
| 6664893 | Eveland et al. | Dec 2003 | B1 |
| 6665385 | Rogers et al. | Dec 2003 | B2 |
| 6665565 | Stomberg et al. | Dec 2003 | B1 |
| 6675045 | Mass et al. | Jan 2004 | B2 |
| 6694177 | Eggers et al. | Feb 2004 | B2 |
| 6701183 | Baker et al. | Mar 2004 | B2 |
| 6708065 | Von Arx et al. | Mar 2004 | B2 |
| 6712762 | Lichter et al. | Mar 2004 | B1 |
| 6720887 | Zunti | Apr 2004 | B1 |
| D490525 | Stein et al. | May 2004 | S |
| 6731311 | Bufe et al. | May 2004 | B2 |
| 6735479 | Fabian et al. | May 2004 | B2 |
| 6735551 | Voegeli et al. | May 2004 | B2 |
| 6749566 | Russ | Jun 2004 | B2 |
| 6758812 | Lang | Jul 2004 | B2 |
| 6763269 | Cox | Jul 2004 | B2 |
| 6766201 | Von Arx et al. | Jul 2004 | B2 |
| 6773396 | Flach et al. | Aug 2004 | B2 |
| 6783492 | Dominguez et al. | Aug 2004 | B2 |
| 6785573 | Kovtun et al. | Aug 2004 | B2 |
| 6792321 | Sepe, Jr. | Sep 2004 | B2 |
| 6801137 | Eggers | Oct 2004 | B2 |
| 6801802 | Sitzman et al. | Oct 2004 | B2 |
| 6804557 | Kroll | Oct 2004 | B1 |
| 6804558 | Haller et al. | Oct 2004 | B2 |
| 6804559 | Kraus et al. | Oct 2004 | B1 |
| 6809701 | Amundson et al. | Oct 2004 | B2 |
| 6820057 | Loch et al. | Nov 2004 | B1 |
| 6840904 | Goldberg | Jan 2005 | B2 |
| 6850252 | Hoffberg | Feb 2005 | B1 |
| 6878112 | Linberg et al. | Apr 2005 | B2 |
| 6885288 | Pincus | Apr 2005 | B2 |
| 6889086 | Mass et al. | May 2005 | B2 |
| 6893395 | Kraus et al. | May 2005 | B1 |
| 6903657 | Kwoen | Jun 2005 | B2 |
| 6915265 | Johnson | Jul 2005 | B1 |
| 6936007 | Quy | Aug 2005 | B2 |
| 6940403 | Kail, IV | Sep 2005 | B2 |
| 6941168 | Girouard | Sep 2005 | B2 |
| 6954673 | Von Arx et al. | Oct 2005 | B2 |
| 6957102 | Silver et al. | Oct 2005 | B2 |
| 6957107 | Rogers et al. | Oct 2005 | B2 |
| 6958705 | Lebel | Oct 2005 | B2 |
| 6961621 | Krishnan et al. | Nov 2005 | B2 |
| 6963907 | McBride et al. | Nov 2005 | B1 |
| 6970737 | Brodnick et al. | Nov 2005 | B1 |
| 6976958 | Quy | Dec 2005 | B2 |
| 6978169 | Guerra | Dec 2005 | B1 |
| 6978182 | Mazar et al. | Dec 2005 | B2 |
| 6980112 | Nee | Dec 2005 | B2 |
| 6985771 | Fischell et al. | Jan 2006 | B2 |
| 6988989 | Weiner et al. | Jan 2006 | B2 |
| 6993393 | Von Arx et al. | Jan 2006 | B2 |
| 7002468 | Eveland et al. | Feb 2006 | B2 |
| 7009511 | Mazar et al. | Mar 2006 | B2 |
| 7016739 | Bange et al. | Mar 2006 | B2 |
| 7043305 | KenKnight et al. | May 2006 | B2 |
| 7058453 | Nelson et al. | Jun 2006 | B2 |
| 7060030 | Von Arx et al. | Jun 2006 | B2 |
| 7065409 | Mazar | Jun 2006 | B2 |
| 7066883 | Schmidt et al. | Jun 2006 | B2 |
| 7070562 | Bardy et al. | Jul 2006 | B2 |
| 7072718 | Von Arx et al. | Jul 2006 | B2 |
| 7079035 | Bock et al. | Jul 2006 | B2 |
| 7096067 | Linberg | Aug 2006 | B2 |
| 7096068 | Mass et al. | Aug 2006 | B2 |
| 7099715 | Korzinov et al. | Aug 2006 | B2 |
| 7104955 | Bardy et al. | Sep 2006 | B2 |
| 7117031 | Lohman et al. | Oct 2006 | B2 |
| 7120488 | Nova et al. | Oct 2006 | B2 |
| 7123950 | Mannheimer | Oct 2006 | B2 |
| 7130396 | Rogers et al. | Oct 2006 | B2 |
| 7134996 | Bardy et al. | Nov 2006 | B2 |
| 7149570 | Ellscheid et al. | Dec 2006 | B2 |
| 7149773 | Haller et al. | Dec 2006 | B2 |
| 7151435 | Brackett et al. | Dec 2006 | B2 |
| 7155290 | Von Arx et al. | Dec 2006 | B2 |
| 7156808 | Quy | Jan 2007 | B2 |
| 7156809 | Quy | Jan 2007 | B2 |
| 7181017 | Nagel | Feb 2007 | B1 |
| 7181505 | Haller et al. | Feb 2007 | B2 |
| 7194300 | Korzinov | Mar 2007 | B2 |
| 7203545 | Schmitt et al. | Apr 2007 | B2 |
| 7204378 | Schaeff | Apr 2007 | B2 |
| 7209790 | Thompson et al. | Apr 2007 | B2 |
| 7212849 | Zhang et al. | May 2007 | B2 |
| 7212850 | Prystowsky | May 2007 | B2 |
| 7218969 | Vallapureddy et al. | May 2007 | B2 |
| 7240833 | Zarembo | Jul 2007 | B2 |
| 7257447 | Cates et al. | Aug 2007 | B2 |
| 7270633 | Goscha | Sep 2007 | B1 |
| 7273454 | Raymond et al. | Sep 2007 | B2 |
| 7283864 | Thomas et al. | Oct 2007 | B2 |
| 7286872 | Kramer et al. | Oct 2007 | B2 |
| 7289761 | Mazar | Oct 2007 | B2 |
| 7292139 | Mazar et al. | Nov 2007 | B2 |
| 7313441 | Mass et al. | Dec 2007 | B2 |
| 7316648 | Kelly et al. | Jan 2008 | B2 |
| 7319903 | Bange et al. | Jan 2008 | B2 |
| 7324850 | Persen et al. | Jan 2008 | B2 |
| 7353063 | Simms, Jr. | Apr 2008 | B2 |
| 7359753 | Bange et al. | Apr 2008 | B2 |
| 7363080 | Stubbs et al. | Apr 2008 | B2 |
| 7373200 | Stubbs et al. | May 2008 | B2 |
| 7378955 | Mazar et al. | May 2008 | B2 |
| 7383087 | Hoyme et al. | Jun 2008 | B2 |
| 7383088 | Spinelli et al. | Jun 2008 | B2 |
| 7389146 | Hanson et al. | Jun 2008 | B2 |
| 7392086 | Sathaye | Jun 2008 | B2 |
| 7392092 | Li et al. | Jun 2008 | B2 |
| 7395117 | Mazar et al. | Jul 2008 | B2 |
| 7536557 | Murakami et al. | May 2009 | B2 |
| 7751801 | Torvinen | Jul 2010 | B2 |
| 7752059 | Sweeney | Jul 2010 | B2 |
| 7830381 | Lundstrom et al. | Nov 2010 | B2 |
| 7978062 | LaLonde et al. | Jul 2011 | B2 |
| 8373556 | Lalonde et al. | Feb 2013 | B2 |
| 20010051787 | Haller et al. | Dec 2001 | A1 |
| 20020010679 | Felsher | Jan 2002 | A1 |
| 20020052539 | Haller | May 2002 | A1 |
| 20020055917 | Muraca | May 2002 | A1 |
| 20020082480 | Riff | Jun 2002 | A1 |
| 20030025602 | Medema et al. | Feb 2003 | A1 |
| 20030088290 | Spinelli et al. | May 2003 | A1 |
| 20030227414 | Saliga | Dec 2003 | A1 |
| 20040006265 | Alhussiny | Jan 2004 | A1 |
| 20040048601 | Lee et al. | Mar 2004 | A1 |
| 20040117308 | Bouknight | Jun 2004 | A1 |
| 20040122488 | Mazar et al. | Jun 2004 | A1 |
| 20040128161 | Mazar et al. | Jul 2004 | A1 |
| 20040170154 | Carter et al. | Sep 2004 | A1 |
| 20040176811 | Von Arx et al. | Sep 2004 | A1 |
| 20040230246 | Stein et al. | Nov 2004 | A1 |
| 20040230247 | Stein et al. | Nov 2004 | A1 |
| 20040233930 | Colby, Jr. | Nov 2004 | A1 |
| 20040260189 | Eggers et al. | Dec 2004 | A1 |
| 20050021370 | Riff | Jan 2005 | A1 |
| 20050027329 | Holmquist et al. | Feb 2005 | A1 |
| 20050032511 | Malone et al. | Feb 2005 | A1 |
| 20050071199 | Riff | Mar 2005 | A1 |
| 20050091338 | De la Huerga | Apr 2005 | A1 |
| 20050113900 | Shiroff et al. | May 2005 | A1 |
| 20050114711 | Hesselink | May 2005 | A1 |
| 20050120082 | Hesselink | Jun 2005 | A1 |
| 20050124866 | Elaz et al. | Jun 2005 | A1 |
| 20050125258 | Yellin | Jun 2005 | A1 |
| 20050131479 | Axelrod et al. | Jun 2005 | A1 |
| 20050144186 | Hesselink | Jun 2005 | A1 |
| 20050144195 | Hesselink | Jun 2005 | A1 |
| 20050144200 | Hesselink | Jun 2005 | A1 |
| 20050149481 | Hesselink | Jul 2005 | A1 |
| 20050159105 | Mass et al. | Jul 2005 | A1 |
| 20050160147 | Denny et al. | Jul 2005 | A1 |
| 20050192649 | Shehadeh et al. | Sep 2005 | A1 |
| 20050192836 | Rossinni et al. | Sep 2005 | A1 |
| 20050192837 | Fears et al. | Sep 2005 | A1 |
| 20050192838 | Jones et al. | Sep 2005 | A1 |
| 20050206518 | Welch et al. | Sep 2005 | A1 |
| 20050241026 | Esler et al. | Oct 2005 | A1 |
| 20050245995 | Diebold | Nov 2005 | A1 |
| 20050251227 | Khoo et al. | Nov 2005 | A1 |
| 20050282494 | Kossi | Dec 2005 | A1 |
| 20050288808 | Lopez et al. | Dec 2005 | A1 |
| 20060020314 | Bodner | Jan 2006 | A1 |
| 20060020960 | Relan | Jan 2006 | A1 |
| 20060030810 | Mandrusov et al. | Feb 2006 | A1 |
| 20060047318 | Pastore et al. | Mar 2006 | A1 |
| 20060052084 | Diebold et al. | Mar 2006 | A1 |
| 20060064133 | Von Arx et al. | Mar 2006 | A1 |
| 20060064142 | Chavan et al. | Mar 2006 | A1 |
| 20060064143 | Von Arx et al. | Mar 2006 | A1 |
| 20060074465 | Webb | Apr 2006 | A1 |
| 20060089856 | Kadhiresan et al. | Apr 2006 | A1 |
| 20060106433 | Mazar et al. | May 2006 | A1 |
| 20060111759 | Hoyme et al. | May 2006 | A1 |
| 20060116744 | Von Arx et al. | Jun 2006 | A1 |
| 20060122667 | Chavan et al. | Jun 2006 | A1 |
| 20060133362 | Stein et al. | Jun 2006 | A1 |
| 20060136717 | Buer et al. | Jun 2006 | A1 |
| 20060139229 | Theobold et al. | Jun 2006 | A1 |
| 20060142820 | Von Arx et al. | Jun 2006 | A1 |
| 20060142821 | Bange et al. | Jun 2006 | A1 |
| 20060154642 | Scannell, Jr. | Jul 2006 | A1 |
| 20060159074 | Diebold et al. | Jul 2006 | A1 |
| 20060161213 | Patel | Jul 2006 | A1 |
| 20060161223 | Vallapureddy et al. | Jul 2006 | A1 |
| 20060173985 | Moore | Aug 2006 | A1 |
| 20060194615 | Vallapureddy et al. | Aug 2006 | A1 |
| 20060195162 | Von Arx et al. | Aug 2006 | A1 |
| 20060195163 | KenKnight et al. | Aug 2006 | A1 |
| 20060200007 | Brockway et al. | Sep 2006 | A1 |
| 20060206246 | Walker | Sep 2006 | A1 |
| 20060218054 | Postelnik et al. | Sep 2006 | A1 |
| 20060220839 | Fifolt et al. | Oct 2006 | A1 |
| 20060241712 | Cates et al. | Oct 2006 | A1 |
| 20060253158 | Stubbs et al. | Nov 2006 | A1 |
| 20060253163 | Stubbs et al. | Nov 2006 | A1 |
| 20060253300 | Somberg et al. | Nov 2006 | A1 |
| 20060253301 | Simms et al. | Nov 2006 | A1 |
| 20060253894 | Bookman | Nov 2006 | A1 |
| 20060265740 | Clark | Nov 2006 | A1 |
| 20070018810 | Smythe et al. | Jan 2007 | A1 |
| 20070027723 | Bardy | Feb 2007 | A1 |
| 20070036771 | Wagner et al. | Feb 2007 | A1 |
| 20070049983 | Freeberg | Mar 2007 | A1 |
| 20070049992 | Freeberg | Mar 2007 | A1 |
| 20070053516 | Katoozi et al. | Mar 2007 | A1 |
| 20070061266 | Moore | Mar 2007 | A1 |
| 20070078491 | Siejko et al. | Apr 2007 | A1 |
| 20070083246 | Mazar et al. | Apr 2007 | A1 |
| 20070100384 | Fischell et al. | May 2007 | A1 |
| 20070100396 | Freeberg | May 2007 | A1 |
| 20070100397 | Seeberger et al. | May 2007 | A1 |
| 20070106129 | Srivathsa et al. | May 2007 | A1 |
| 20070106536 | Moore | May 2007 | A1 |
| 20070106537 | Moore | May 2007 | A1 |
| 20070106750 | Moore | May 2007 | A1 |
| 20070106751 | Moore | May 2007 | A1 |
| 20070106752 | Moore | May 2007 | A1 |
| 20070106753 | Moore | May 2007 | A1 |
| 20070106754 | Moore | May 2007 | A1 |
| 20070116036 | Moore | May 2007 | A1 |
| 20070116037 | Moore | May 2007 | A1 |
| 20070118188 | Von Arx et al. | May 2007 | A1 |
| 20070123943 | Patangay et al. | May 2007 | A1 |
| 20070123946 | Masoud | May 2007 | A1 |
| 20070129642 | Korzinov | Jun 2007 | A1 |
| 20070130657 | Rogers et al. | Jun 2007 | A1 |
| 20070135855 | Foshee et al. | Jun 2007 | A1 |
| 20070135865 | Schmitt et al. | Jun 2007 | A1 |
| 20070136098 | Smythe et al. | Jun 2007 | A1 |
| 20070138253 | Libin | Jun 2007 | A1 |
| 20070142727 | Zhang et al. | Jun 2007 | A1 |
| 20070150010 | Stubbs et al. | Jun 2007 | A1 |
| 20070150028 | Parkinson et al. | Jun 2007 | A1 |
| 20070156054 | Korzinov et al. | Jul 2007 | A1 |
| 20070157298 | Dingwall | Jul 2007 | A1 |
| 20070168222 | Hoyme et al. | Jul 2007 | A1 |
| 20070168461 | Moore | Jul 2007 | A1 |
| 20070175827 | Wariar | Aug 2007 | A1 |
| 20070179349 | Hoyme et al. | Aug 2007 | A1 |
| 20070180047 | Dong et al. | Aug 2007 | A1 |
| 20070185547 | Hoyme et al. | Aug 2007 | A1 |
| 20070185550 | Vallapureddy et al. | Aug 2007 | A1 |
| 20070191723 | Prystowsky et al. | Aug 2007 | A1 |
| 20070192140 | Gropper | Aug 2007 | A1 |
| 20070195163 | Chestak et al. | Aug 2007 | A1 |
| 20070203754 | Harrington | Aug 2007 | A1 |
| 20070206615 | Plamondon et al. | Sep 2007 | A1 |
| 20070210923 | Butler | Sep 2007 | A1 |
| 20070226013 | Elletson et al. | Sep 2007 | A1 |
| 20070251835 | Mehta et al. | Nov 2007 | A1 |
| 20070260293 | Carpenter et al. | Nov 2007 | A1 |
| 20070263873 | Qi et al. | Nov 2007 | A1 |
| 20070265533 | Tran | Nov 2007 | A1 |
| 20070273504 | Tran | Nov 2007 | A1 |
| 20070276270 | Tran | Nov 2007 | A1 |
| 20070282634 | Johnson et al. | Dec 2007 | A1 |
| 20070288067 | Eveland | Dec 2007 | A1 |
| 20070288069 | Goscha et al. | Dec 2007 | A1 |
| 20070293776 | Korzinov et al. | Dec 2007 | A1 |
| 20070299317 | Hoyme et al. | Dec 2007 | A1 |
| 20080001735 | Tran | Jan 2008 | A1 |
| 20080004904 | Tran | Jan 2008 | A1 |
| 20080015655 | Bange et al. | Jan 2008 | A1 |
| 20080015656 | Bange et al. | Jan 2008 | A1 |
| 20080021521 | Shah et al. | Jan 2008 | A1 |
| 20080021523 | Cates et al. | Jan 2008 | A1 |
| 20080021524 | Goscha et al. | Jan 2008 | A1 |
| 20080021730 | Holla | Jan 2008 | A1 |
| 20080021741 | Holla | Jan 2008 | A1 |
| 20080021834 | Holla | Jan 2008 | A1 |
| 20080024294 | Mazar | Jan 2008 | A1 |
| 20080027499 | Srivathsa et al. | Jan 2008 | A1 |
| 20080040151 | Moore | Feb 2008 | A1 |
| 20080055070 | Bange et al. | Mar 2008 | A1 |
| 20080058651 | Shen et al. | Mar 2008 | A1 |
| 20080058881 | Wagner et al. | Mar 2008 | A1 |
| 20080061961 | John | Mar 2008 | A1 |
| 20080071183 | Thomas et al. | Mar 2008 | A1 |
| 20080071314 | John | Mar 2008 | A1 |
| 20080086185 | Amurthur et al. | Apr 2008 | A1 |
| 20080103542 | Hoyme et al. | May 2008 | A1 |
| 20080109051 | Splinter et al. | May 2008 | A1 |
| 20080114412 | Bange et al. | May 2008 | A1 |
| 20080140163 | Keacher | Jun 2008 | A1 |
| 20080154099 | Aspel | Jun 2008 | A1 |
| 20080157928 | Butler | Jul 2008 | A1 |
| 20080164975 | Butler | Jul 2008 | A1 |
| 20080164977 | Butler | Jul 2008 | A1 |
| 20080177194 | Zhang et al. | Jul 2008 | A1 |
| 20080180249 | Butler | Jul 2008 | A1 |
| 20080186137 | Butler | Aug 2008 | A1 |
| 20080186138 | Butler | Aug 2008 | A1 |
| 20080186139 | Butler | Aug 2008 | A1 |
| 20080186180 | Butler | Aug 2008 | A1 |
| 20080209513 | Graves et al. | Aug 2008 | A1 |
| 20080211630 | Butler | Sep 2008 | A1 |
| 20080222711 | Michaelis | Sep 2008 | A1 |
| 20080252459 | Butler | Oct 2008 | A1 |
| 20080294019 | Tran | Nov 2008 | A1 |
| 20080306872 | Felsher | Dec 2008 | A1 |
| 20090019552 | McLaughlin | Jan 2009 | A1 |
| 20090024178 | Hennig | Jan 2009 | A1 |
| 20090024416 | McLaughlin | Jan 2009 | A1 |
| 20090058635 | LaLonde et al. | Mar 2009 | A1 |
| 20090058636 | Gaskill et al. | Mar 2009 | A1 |
| 20090062887 | Mass et al. | Mar 2009 | A1 |
| 20090063187 | Johnson et al. | Mar 2009 | A1 |
| 20090063193 | Barton et al. | Mar 2009 | A1 |
| 20090099866 | Newman | Apr 2009 | A1 |
| 20090146822 | Soliman | Jun 2009 | A1 |
| 20090158274 | Roberts | Jun 2009 | A1 |
| 20090222898 | Veidung | Sep 2009 | A1 |
| 20090231125 | Baldus et al. | Sep 2009 | A1 |
| 20090240526 | Vesto et al. | Sep 2009 | A1 |
| 20090320029 | Kottomtharayil | Dec 2009 | A1 |
| 20100144316 | Piercy et al. | Jun 2010 | A1 |
| 20100225468 | Sievert et al. | Sep 2010 | A1 |
| 20100228977 | Sievert et al. | Sep 2010 | A1 |
| 20110202371 | Darguesse et al. | Aug 2011 | A1 |
| 20120068847 | Pirzada | Mar 2012 | A1 |
| 20130076535 | Sievert et al. | Mar 2013 | A1 |
| 20130133011 | Chhaochharia et al. | May 2013 | A1 |
| 20130147622 | LaLonde et al. | Jun 2013 | A1 |
| 20130154851 | Gaskill et al. | Jun 2013 | A1 |
| 20130262311 | Buhrmann et al. | Oct 2013 | A1 |
| 20130310896 | Mass | Nov 2013 | A1 |
| 20140111353 | Sievert et al. | Apr 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 1681803 | Jul 2006 | EP |
| 08329374 | Dec 1996 | JP |
| 2003047599 | Feb 2003 | JP |
| 2005080175 | Mar 2005 | JP |
| 2007200276 | Aug 2007 | JP |
| WO 9736443 | Oct 1997 | WO |
| WO03077994 | Sep 2003 | WO |
| WO 03100647 | Dec 2003 | WO |
| WO 2004109992 | Dec 2004 | WO |
| WO2006010166 | Jan 2006 | WO |
| WO2009032134 | Mar 2009 | WO |
| Entry |
|---|
| Biotronic Technical Manual for Philos DR-T, DDDR Dual Chamber Pulse Generator with Home Monitor, 2004, 32 pages. |
| Medtronic Analyzer Reference Guide for Medtronic Carelink Analyzer, Model 2290 Analyzer for Medtronic and Vitatron Devices, 2008, 106 pages. |
| Medtronic Programmer Reference Guide for Medtronic Carelink Programmer, Model 2090 Programmer for Medtronic and Vitatron Devices, 2008, 112 pages. |
| International Search Report and Written Opinion dated Apr. 9, 2009 from International Application No. PCT/US2008/010162, 24 pages. |
| International Preliminary Report on Patentability dated Mar. 1, 2010 from International Application No. PCT/US2008/010162, 13 pages. |
| U.S. Appl. No. 12/694,826, filed Jan. 27, 2010, Sievert et al. |
| Invitation to Pay Additional Fees dated Jul. 12, 2010 from PCT Application No. PCT/US2010/026076, 6 pages. |
| Savci et al., “MICS Transceivers: Regulatory Standards and Applications”, IEEE Proceedings, Apr. 8, 2005. pp. 179-182. |
| Valdastri et al., “An implantable ZigBee ready telemetric platform for in vivo monitoring of physiological parameters,” Sensors and Actuators A, vol. 142, 2008, pp. 369-378. |
| Office Action dated Oct. 5, 2010 from U.S. Appl. No. 12/151,869, 6 pages. |
| Office Action Response submitted Oct. 7, 2010 to office action dated Oct. 5, 2010 from U.S. Appl. No. 12/151,869, 9 pages. |
| International Search Report and Written Opinion from International Application No. PCT/US2010/026076 dated Oct. 11, 2010, 17 pages. |
| Office Action Response dated Sep. 4, 2012 for U.S. Appl. No. 12/151,910, 13 pages. |
| Notice of Allowance dated Sep. 10, 2012 for U.S. Appl. No. 13/181,176, 7 pages. |
| Margolis et al., Latitude Active Monitoring alerts physician of silent AF episode, Latitude Patient Management Case Study, Boston Scientific Corporation, 2006, 2 pages. |
| JP Office Action with translation dated Mar. 28, 2012 from JP Application No. 2010-522944, 4 pages. |
| File History for U.S. Appl. No. 12/151,869. |
| File History for U.S. Appl. No. 12/228,915. |
| File History for European Application No. 08795636.3 as retrieved from the European Patent Office Electronic Filing System on Jun. 15, 2012, 92 pages. |
| File History for U.S. Appl. No. 12/151,910. |
| File History for U.S. Appl. No. 12/151,780. |
| File History for U.S. Appl. No. 12/151,796. |
| File History for U.S. Appl. No. 13/181,176. |
| File History for U.S. Appl. No. 12/694,826. |
| Klemm, Fabius et al., “Alleviating effects of mobility on TCP performance in ad hoc networks using signal strength based link management”, Lecture notes in Computer Science, vol. 2775, 2003, pp. 611-624. |
| “File History for co-owned, U.S. Appl. No. 13/758,489”, Entitled “Medical Data Transport Over Wireless Life Critical Network,”, filed Feb. 4, 2013 (325 pages). |
| “File History for co-owned, U.S. Appl. No. 12/151,796”, Entitled “Dashboard Diagnostics for Wireless Patient Communicator,”, filed May 9, 2008 (604 pages). |
| “File History for co-owned, co-pending U.S. Appl. No. 13/684,893”, Entitled “Modular Patient Communicator for Use in Life Critical Network,”, filed Nov. 26, 2012 (237 pages). |
| “JP Office Action Translation”, for Japanese Application No. 2011553082, mailed Dec. 18, 2012 (14 pages). |
| “File History for U.S. Appl. No. 14/071,893”, 276 pages. |
| “Partial File History for U.S. Appl. No. 12/228,915”, 182 pages. |
| Final Office Action, for U.S. Appl. No. 12/228,915, mailed May 28, 2014 (40 pages). |
| “Final Office Action”, for U.S. Appl. No. 14/071,893, mailed Mar. 13, 2014 (9 pages). |
| “Notice of Allowance”, for U.S. Appl. No. 13/955,746, mailed Apr. 22, 2014 (49 pages). |
| Number | Date | Country | |
|---|---|---|---|
| 20100228977 A1 | Sep 2010 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61157455 | Mar 2009 | US |
