Browse Prior Art Database

MANAGING MULTIPLE ACTIVE IMPLANTED MEDICAL DEVICES IN A SINGLE SESSION

IP.com Disclosure Number: IPCOM000202481D
Publication Date: 2010-Dec-17
Document File: 3 page(s) / 697K

Publishing Venue

The IP.com Prior Art Database

Abstract

Multiple active implanted medical devices can be managed to provide a common user interface for programming and data access during a single communication session.

This text was extracted from a Microsoft Word document.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 52% of the total text.

Managing Multiple Active Implanted Medical Devices in a Single Session

Patients may be diagnosed with multiple conditions, diagnosed or treated using multiple active implantable medical devices (AIMDs).  An AIMD can be configured to perform one or more therapeutic functions.  Examples of an AIMD can include cardiac rhythm management devices, cochlear implants, neural stimulation devices, or insulin or other drug pumps.  When implanted, the function of the AIMD is customized by a clinician for the therapeutic needs of the patient.  Managing the multiple AIMDs involves using a separate programmer or application software for each AIMD. 

A unified interface for managing multiple AIMDs allows a clinician access to view data from each AIMD in a single application.  A unified interface for multiple AIMDs can be designed to (1) manage user access, (2) initiate a session with each AIMD, (3) manage multiple telemetry streams, and (4) display data collected from each device.

Managing User Access

User access protection can allow for protection of sensitive data, both for programming an AIMD and displaying the data.  A clinician can program each AIMD during a single session.  Accessibility can be limited using password protection.  A password can be used to limit programming permissions and to control access to AIMD parameters, and can be stored in a programmer, the AIMD or both.  Programming access can be managed by the programmer. 

In an example, the patient’s AIMDs can include an implantable cardioverter-defibrillator (ICD), an apnic stimulator, and a vagus nerve stimulation device.  The clinician can be assigned a password allowing full access to all of these AIMDs, such as for programming and data management, or the clinician can be assigned a password limiting programming and data management access to a single AIMD.  The clinician can be assigned a password that can limit programming access to only a specific AIMD, but which can provide access to limited data sets from multiple AIMDs.  In an example, a password assigned to a clinician allows reading of data of all AIMDs, but limits programming access to one or more AIMDs, a subset of parameters of a specified one or more AIMDs, or both.  For example, programming access to one or more particular parameters, such as safety-critical parameters can be limited to only a specified clinician. 

Session Initiation

In an example, a single programmer can initiate a communication session with each AIMD individually.  In an example, the programmer can initiate a communication session with a single AIMD, which then can initiate communication to one or more AIMDs.  As seen in FIG. 1A, the AIMD may initiate communication with each device automatically, or, in FIG. 1B, prompt a user to initiate a communication session with one or more AIMDs. 

Managing multiple telemetry streams

In an example, the programmer can manage the telemetry streams from the one or more AIMDs to ensure data integrity and...