Devices and methods for improving remote programming of implanted neurostimulation systems
Through remote communication devices and software, the problem of remote programming of implantable neural stimulation systems is solved, system adjustments are achieved without medical treatment, and treatment efficiency and convenience are improved. It is especially suitable for patients in remote areas and elderly groups.
Patent Information
- Application Number
- CN202380018917.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-05-04
- Filing Date
- 2023-05-03
- Publication Date
- 2024-11-12
Smart Images

Figure CN118946381A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to and the benefit of U.S. Provisional Patent Application No. 63 / 338,403, which is incorporated herein by reference.
[0003] This application is usually related to:
[0004] U.S. Nonprovisional Application No. 17 / 513,790, filed on October 28, 2021, entitled “Devices and Methods for Remote Programming of Implanted Neurostimulation Systems”;
[0005] U.S. Nonprovisional Application No. 16 / 871,738, filed May 11, 2020, entitled “Attachment Devices and Associated Methods of Use With a Nerve Stimulation Charging Device”;
[0006] U.S. Non-Provisional Patent Application No. 14 / 827,067, filed on August 14, 2015, entitled “Systems and Methods for Neurostimulation Electrode Configurations Based on Neural Localization” (now U.S. Patent No. 9,855,423);
[0007] U.S. Nonprovisional Application No. 14 / 992,777, filed on January 11, 2016, entitled “Patient Remote and Associated Methods of Use With a Nerve Stimulation System” (now U.S. Patent No. 9,895,546); and
[0008] U.S. Nonprovisional Application No. 14 / 993,009, filed on January 11, 2016, entitled “Improved Antenna and Methods of Use For an Implantable Nerve Stimulator” (now U.S. Patent No. 9,700,731);
[0009] Each of these applications is assigned to the same assignee and is hereby incorporated by reference in its entirety. Technical Field
[0010] The present application relates to remote programming of neural stimulation therapy systems and associated devices, methods, and system settings. Background Art
[0011] Treatment with implantable neurostimulation systems has become increasingly common in recent years. While such systems have shown promise in treating a variety of conditions, treatment outcomes can vary widely from patient to patient. Many factors may contribute to very different patient outcomes; and, it may be difficult to determine the feasibility of treatment prior to implantation. Current stimulation electrode placement / implantation techniques and known treatment setting techniques have significant disadvantages. The neural tissue structure of different patients may be very different, and the location and branches of nerves that perform specific functions and / or weaken specific organs are difficult to accurately predict or identify. The electrical properties of the tissue structure surrounding the target neural structure may also be very different between different patients, and the neural response to stimulation may be significantly different, and the electrical stimulation pulse pattern, pulse width, frequency, and / or amplitude may effectively affect the physical function of one patient, but produce significant discomfort or pain for another patient, or have limited effect. Even in patients where an implanted neurostimulation system provides effective treatment, frequent adjustments and changes to the stimulation regimen are often required before an appropriate treatment regimen is determined, which often requires repeated visits to the doctor and significant discomfort to the patient before achieving efficacy. While recently developed systems have improved lead placement and stimulation efficiency to increase consistency of treatment, many patients still require occasional adjustments or changes to their treatment regimen. This reprogramming often requires an in-person, sometimes repeated visit. Given that implantable neurostimulation systems utilize dedicated local communications (e.g., MedRadio) to communicate with accessory components within the system and that patients lack the expertise or permission to adjust or modify treatment, this creates a significant barrier to programming implantable systems without requiring an in-person visit from a clinician or system technician. Current treatment systems are simply not designed to be remotely controlled or programmed. These challenges pose a significant barrier to maintaining long-term, effective treatment for patients living in remote areas or for those in the elderly or vulnerable patient populations.
[0012] It would therefore be desirable to provide improved systems, devices, and methods by which a clinician or technologist could remotely adjust or reprogram an implanted neurostimulation system without requiring an in-person visit. Such an approach would further help facilitate interaction between the patient and clinician to provide the benefits of an in-person visit while still allowing the system to be remotely programmed. Summary of the invention
[0013] The present application generally relates to remote programming of a neurostimulation therapy system and associated devices and methods. The present application is particularly applicable to a sacral neurostimulation therapy system configured to treat bladder and bowel-related dysfunctions. However, as will be appreciated by one of ordinary skill in the art, various exemplary embodiments disclosed herein may also be used to treat pain or other indications, such as movement or affective disorders, or various other implanted medical devices.
[0014] The disclosed embodiments relate to methods, user devices, intermediate communication devices, and dedicated application software that facilitate remote programming of implants via remote devices. As described above, there is an increasing need for remote programming of implanted medical devices, which allows medical personnel to remotely connect with patients via a phone or tablet device and reprogram or troubleshoot the medical devices implanted in their bodies. By using a dedicated intermediate communication device and a dedicated software application that utilizes various types of communications (e.g., Bluetooth (BT), MedRadio (MR), cellular / WiFi, or any combination thereof), users can use existing devices and their personal computing devices to establish a real-time communication session for programming their implanted devices, or remotely troubleshoot their devices in a manner that is convenient and secure for all parties. In some exemplary embodiments, users can utilize customized devices and / or accessory devices to simplify system setup and / or provide additional functionality beyond the capabilities of existing devices or personal devices. In addition, the present application discloses various options and system settings that can accommodate a range of available IPG designs (rechargeable and non-rechargeable) with various communication capabilities. In some exemplary embodiments, the remote programming setup system is designed to be backward compatible with existing devices / systems (IPGs that do not support BT). In other embodiments, the system settings are designed to be forward compatible with the next generation of remote programming functions (e.g., an IPG or patient remote control with both MR and BT functions). In another aspect, the system settings may include a patient database portal through which treatment information can be periodically updated and remote programming of remote devices can be notified, or self-programming of patient devices can be notified. The patient portal can be web-based and hosted on a secure server and can be accessed by a patient device or a remote programming device. In another aspect, the remote programming system settings described herein can be integrated into a telehealth platform (e.g., Teledoc, VSee, Doxy.me, OhMD, Whereby, Mend, Updox, NextGen Healthcare EHR, etc.). In general, telemedicine platforms cover technical infrastructure, services, and support, allowing remote private, secure, HIPAA-compliant, and high-quality virtual medical consultations and treatments. Such telemedicine systems may include telephone, video conferencing, or text-based communications, which are typically communicated through a telecommunications system, typically using a patient's personal device. Therefore, the remote programming functions described herein can be incorporated into these telehealth platforms to facilitate remote programming using the existing functions of these platforms.
[0015] A typical implanted medical device communicates with its peripheral devices (e.g., clinician programmers, patient remote controls, etc.) over specific frequencies dedicated to medical device use, such as the Medical Device Radiocommunication Service (MedRadio) band (e.g., 401-406 MHz, 413-419 MHz, 426-432 MHz, 438-444 MHz, and 451-457 MHz ranges). In addition, a Medical Body Area Network (MBAN) is a low-power network of sensors worn on the body that is controlled by a hub device located on or near the body, which operates in the 2360-2400 MHz band. Standard smartphones or tablet devices are not suitable for communicating with or programming implanted medical devices. By using a dedicated intermediary device or an update to an existing accessory device, a real-time communication session can be remotely established between the implanted medical device, the patient device, and the remote device to allow programming.
[0016] The intermediate device can communicate with the implanted medical device via the MedRadio band on one end and with the patient's phone or tablet device (iOS or Android device) via Bluetooth or low-power Bluetooth on the other end. In some exemplary embodiments, the system utilizes existing accessories such as patient remote controls or chargers as intermediate devices. In some exemplary embodiments, a dedicated intermediate device can be configured to be plugged into a user's device (e.g., a smartphone, tablet device, laptop) via its charging port or other port (e.g., USB-C, USB, etc.). The intermediate device can then be powered and recognized by the user's phone or tablet device. A dedicated application ("App") can be developed and pre-downloaded to the user's device. The user can be a patient, a clinician, or a patient advocate. The App can be used to change the program settings of the implanted device or perform troubleshooting by commanding the implanted device to run diagnostics on its own and report to the user's device. In other embodiments, the dedicated device can be a separate device that communicates with the patient's device (e.g., a smartphone or tablet device) via radio communication (e.g., Bluetooth or near-field communication ("NFC")) and communicates with the implanted device via MedRadio. In this embodiment, the intermediate device contains a power source and is self-powered. As described above, specific apps can be developed and pre-downloaded to the user's device to allow for changes to the program settings of the implanted device or to troubleshoot the implanted device.
[0017] A method for remotely programming an implanted neurostimulation system is disclosed herein. The method may include the following steps: receiving a patient's request for programming an implantable pulse generator of a neurostimulation system implanted in a patient's body by a remote device; establishing a communication session between the implantable pulse generator of the neurostimulation system and a remote device associated with a remote support entity through one or more intermediate local devices; receiving program information and patient information by the remote device; determining or receiving a program update about one or more parameters of updating a current program or a new program to be applied by the implanted neurostimulation system by the remote device; and programming the implantable pulse generator by the remote device through the one or more intermediate devices using the program update. In some exemplary embodiments, the program information includes the current treatment program applied by the implanted neurostimulation system. In some exemplary embodiments, the patient information includes patient identification information, objective information, and / or subjective information about the treatment. The objective information may include, but is not limited to, any of the following information: number of urinations, amount of urination per time, number of pads, visual analog scale (VAS) pain score, quality of life (QoL) score, sleep time, and current stimulation treatment parameters. The subjective information may include, but is not limited to, any of the following information: patient feelings, mood changes, and sleep quality.
[0018] In some exemplary embodiments, the one or more intermediate local devices include any of the following: a charger device, a patient remote control, a patient's personal computing device, a dedicated communication device. In some exemplary embodiments, the one or more intermediate devices include a first intermediate device and a second intermediate device, the first intermediate device communicating with the implantable pulse generator and the second intermediate device, and the second intermediate device communicating with the first intermediate device and a remote device of the remote support entity. In some exemplary embodiments, the first intermediate device is any of the following: a charger, a patient remote control, a dedicated communication device, and a plug-in accessory that plugs into the patient's personal computing device. The first intermediate device communicates with the implantable pulse generator via a first communication scheme (e.g., MedRadio). The second intermediate device communicates with the first intermediate device via a second communication scheme (e.g., Bluetooth), and can communicate with the remote device via another communication scheme (e.g., via Wifi, cellular, wired connection, or any combination thereof).
[0019] In some exemplary embodiments, the second intermediate device includes a dedicated patient App that is specially configured to facilitate programming. The patient App can be configured to access or store program information and transmit it to a remote device for programming. In some exemplary embodiments, the patient App can be configured to access program information from a data center associated with a first-party developer of an implantable pulse generator. In some exemplary embodiments, the patient App can be configured to access program information from an implantable pulse generator via a first intermediate device. In some exemplary embodiments, the patient App is further configured to receive patient input about the current treatment program and / or patient information via a user interface. The patient App may also include a bladder and / or urination diary that stores subjective information about the efficacy of the current treatment program, and the remote entity can access the subjective information during programming. The subjective information can be periodically collected and / or recorded within the patient App for at least a few days. In some exemplary embodiments, the patient App can be configured to conduct a real-time communication session (e.g., a real-time video call) between a patient and a remote device of a remote support entity. The communication between the remote device and one or more local intermediate devices can utilize any of the following: a cloud-based server, a local server of the remote entity, a hosted server hosted by a third party. In some exemplary embodiments, the remote entity is associated with a first-party developer of an implantable pulse generator and / or a dedicated patient app on one or more local intermediate devices. In some exemplary embodiments, the remote entity is a third party that serves as a technical advisor, treating physician, clinician, or healthcare provider. In some exemplary embodiments, the patient app can be configured to be installed on a user's personal portable computing device and cannot be accessed by an Internet browser.
[0020] In another aspect, the remote device may include a dedicated remote programming App operating thereon. The remote programming App may be configured to serve an Internet browser and be accessed by the remote device. The remote device may be any one of a smartphone, a tablet device, a laptop computer, and a desktop computing device. In some exemplary embodiments, the remote programming App may be configured to be installed and accessed on a portable computing device associated with a treating clinician or an associated healthcare provider. In some exemplary embodiments, the remote programming App may be configured to establish communication with the patient through a backend associated with a first-party developer of an implantable pulse generator. The communication session may include accessing patient information and / or program information from a data center associated with a first-party developer of an implantable pulse generator accessed through the backend. In some exemplary embodiments, the backend is a cloud-based, first-party local server or a hosted server. In some exemplary embodiments, initial communication is established in response to a remote entity or an associated entity receiving a request for programming initiated by a patient using a second intermediate device. In some exemplary embodiments, establishing communication includes exchanging identification information about the implantable pulse generator, the patient, and the remote entity between the second intermediate device and the remote device to ensure secure authentication communication during the session. In some exemplary embodiments, the remote device has administrative control of the implantable pulse generator during at least a portion of the communication session over the patient. In some exemplary embodiments, the method includes: accessing, using the remote device, a plurality of recommended neurostimulation programs including a current therapy program; and selecting, using the remote device, another of the plurality of recommended neurostimulation programs to apply as a new updated program. The plurality of recommended neurostimulation programs may be stored on any implantable pulse generator, or stored in a separate data center and accessed by the remote device using the patient information.
[0021] Disclosed herein is a method for remotely programming an implanted neurostimulation system using a patient device. The method may include the following steps: establishing a communication session with a remote device associated with a remote support entity using the patient device; sending patient information and / or program information about a current treatment program applied by an implanted pulse generator of the implanted neurostimulation system to the remote device using the patient device; receiving a program update from the remote device about an update of one or more parameters of the current program or a new program using the patient device; and outputting the program update to the implanted neurostimulation system using the patient device, thereby programming the implanted pulse generator from the remote device via the patient device using the program update of one or more parameters of the current program or the new program.
[0022] Various methods for remotely programming an implanted neurostimulation system using a remote device are disclosed herein. The method may include the following steps: establishing a communication session between an implanted pulse generator of a neurostimulation system implanted in a patient and a remote device associated with a remote support entity through one or more intermediate local devices for programming and / or reprogramming the implanted pulse generator by the remote entity; receiving program information using the remote device, wherein the program information includes a current treatment program on the implanted neurostimulation system; receiving patient information about the current treatment program using the remote device via the one or more local intermediate devices, wherein the patient information includes patient identification information and / or subjective information about the treatment; determining or receiving a program update about one or more parameters for updating the current program or a new program for the implanted neurostimulation system based on a current based on the treatment program information and the patient information using the remote device; and programming the implanted pulse generator using the program update using the remote device through the one or more intermediate devices.
[0023] A system for remote programming of an implanted neurostimulation system is also disclosed. The system may include an implantable pulse generator, a first intermediate device, a second intermediate device, and a remote device of a remote support entity. The implantable pulse generator of the neurostimulation system is implanted in the patient's body and includes one or more antennas for wirelessly communicating with one or more external devices via a first communication. The first intermediate device may be configured to communicate with the implantable pulse generator and one or more additional devices via local communication. The second intermediate device associated with the patient may be configured to communicate with the first intermediate device via local communication and communicate with one or more other devices via remote communication. The second intermediate device includes a user interface for receiving patient input from the patient. The remote device associated with the remote support entity may be configured to communicate with the second intermediate device via remote communication, wherein the remote device includes a user interface for receiving input from the remote support entity. In some exemplary embodiments, the system may be configured to establish a communication session between the implantable pulse generator of the neurostimulation system and the remote device via a first intermediate local device and a second intermediate local device, wherein the remote device receives program information and / or patient information via the communication session for programming and / or reprogramming the implantable pulse generator by the remote entity.
[0024] Disclosed herein is an embodiment of a patient device configured to facilitate remote programming of an implanted neurostimulation system. The patient device may include a portable housing, a communication module, a user interface, and a processor module disposed in the housing. The communication module has one or more antennas having a remote communication antenna for communicating with one or more remote devices via a network and a local communication antenna for local communication with one or more intermediate devices and / or an implantable pulse generator. The processor module includes a processor and a memory, on which computer executable instructions configured to be programmed by a remote device through a patient device are stored. In some exemplary embodiments, the patient device may be a portable computing device, such as a laptop or smartphone, or a dedicated device, and may include a dedicated patient App to facilitate programming according to any aspect described herein.
[0025] Other areas of applicability of the present disclosure will become apparent from the detailed description provided below.It should be understood that while indicating various embodiments, the detailed description and specific examples are only for illustrative purposes and are not intended to limit the scope of protection of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0026] Figure 1 A neurostimulation system is schematically shown that includes a clinician programmer and a patient remote control for positioning and / or programming both a trial neurostimulation system and a permanently implanted neurostimulation system.
[0027] Figure 2A-2C Diagram showing neural structures along the spine, lower back, and sacral regions that may be stimulated by the systems and devices disclosed herein.
[0028] Figure 3 An example of a fully implanted neurostimulation system is shown.
[0029] Figure 4 An example of a neurostimulation system with implantable stimulation leads, an implantable pulse generator, and an external charging device is shown.
[0030] Figure 5A-5B A detailed view of an implantable pulse generator and related components used in a neurostimulation system is shown.
[0031] Figure 6A-6B Signal characteristics of a neural stimulation procedure are shown.
[0032] Figure 7 A schematic diagram of the clinician programmer configuration is shown.
[0033] Figure 8and Fig. 9 The workflow for using a clinician programmer in programming an implanted neurostimulation system according to some disclosed embodiments is schematically illustrated.
[0034] Fig.10 An example method of determining electrode configuration recommendations during programming and providing the electrode configuration recommendations to a physician is shown.
[0035] Fig.11 Example electrode configuration recommendations are shown for display on a clinician programmer during programming and / or reprogramming of a neurostimulation system.
[0036] Figures 12A-12B Electrode configuration recommendations for an example case study based on electrode thresholds are shown.
[0037] Figures 13A-13K A graphical user interface display of a clinician programmer is shown during the programming process.
[0038] Fig.14 A remote programming system according to some exemplary embodiments is schematically illustrated.
[0039] Figures 15A-15B A communication setup between a patient device and an implanted medical device for remote programming according to some exemplary embodiments is schematically illustrated.
[0040] Fig.16 A communication setup between a patient device and a remote support entity is schematically illustrated according to some example embodiments.
[0041] Fig.17 Workflow options for remote programming settings are schematically illustrated according to some exemplary embodiments.
[0042] Figure 18-20 An exemplary method of remotely programming an implanted medical device using a communication setup is shown in accordance with some exemplary embodiments.
[0043] 21 illustrates an exemplary system setup for remotely programming an implanted medical device using a communication setup, according to some exemplary embodiments.
[0044] Figure 22-26 Various options are shown for an exemplary system setup for remotely programming an implanted medical device using a communication setup in accordance with some exemplary embodiments.
[0045] Figure 27-28 An exemplary method of remotely programming an implanted medical device using various optional system settings is shown in accordance with some exemplary embodiments. DETAILED DESCRIPTION
[0046] The disclosed embodiments relate to remote programming of implanted neural stimulation therapy systems and associated devices, and associated devices that facilitate remote programming. Specific embodiments relate to sacral neural stimulation therapy systems that are configured to treat bladder dysfunction, including overactive bladder ("OAB"), and bowel dysfunction, and alleviate symptoms associated therewith. For ease of description, embodiments for OAB may be described, however, it should be understood that the disclosed embodiments may also be used for any of a variety of neural regulation purposes, such as treatment of intestinal disorders (e.g., fecal incontinence, stool frequency, stool urgency, and / or stool retention), pain, or other indications (e.g., motor or affective disorders), as understood by one of ordinary skill in the art.
[0047] I. Indications for neurostimulation
[0048] Neurostimulation (or neuroregulation, which may be used interchangeably below) treatment systems (e.g., any treatment system described herein) can be used to treat a variety of diseases and related symptoms, such as acute pain disorders, movement disorders, affective disorders, and bladder-related dysfunction and bowel dysfunction. Examples of pain disorders that can be treated by neurostimulation include failed back surgery syndrome, reflex sympathetic dystrophy or complex regional pain syndrome, dystonia, arachnoiditis, and peripheral neuropathy. Movement disorders include muscle paralysis, tremor, dystonia, and Parkinson's disease. Affective disorders include depression, obsessive-compulsive disorder, cluster headaches, Tourette syndrome, and certain types of chronic pain. Bladder-related dysfunction includes, but is not limited to, OAB, impulsive incontinence, frequent urination, urgency, and urinary retention. OAB may include urgency incontinence and frequent urination, either alone or in combination. Urgency incontinence refers to involuntary urinary incontinence associated with a sudden and strong desire to urinate (sense of urgency). Frequent urination refers to frequent, often uncontrollable urges to urinate (urgency), which usually result in a small amount of urination (frequency). Urinary retention refers to the inability to empty the bladder. Neurostimulation therapy can be configured to address a specific condition by neurostimulating targeted neural tissue associated with sensory and / or motor control associated with the specific condition or associated symptoms. Intestinal disorders can include any of a variety of inflammatory, motility, and incontinence disorders.
[0049] In one aspect, the methods and systems described herein are particularly useful for treating urinary and fecal dysfunction. Historically, these diseases have been underrecognized and significantly underserved by the medical community. OAB is one of the most common urinary dysfunctions. It is a complex disease characterized by the presence of bothersome urinary symptoms, including urgency, frequency, nocturia, and urge incontinence. It is estimated that approximately 40 million Americans suffer from OAB. In the adult population, approximately 16% of men and women suffer from symptoms of OAB.
[0050] OAB symptoms can have a significant negative impact on patients’ psychosocial functioning and quality of life. Patients with OAB often limit activities and / or develop coping strategies. In addition, OAB imposes a significant economic burden on individuals, families, and healthcare organizations. The prevalence of comorbidities in patients with OAB is also significantly higher than in the general population. Comorbidities may include falls and fractures, urinary tract infections, skin infections, vulvovaginitis, cardiovascular, and central nervous system diseases. Chronic constipation, fecal incontinence, and overlapping chronic constipation are more common in patients with OAB.
[0051] II. Sacral Nerve Modulation
[0052] SNM is an established treatment that provides a safe, effective, reversible and durable treatment option for the treatment of urge incontinence, urinary frequency and urgency, and non-obstructive urinary retention. SNM treatment involves the use of mild electrical pulses to stimulate the sacral nerves located in the lower back. The electrodes are placed next to the sacral nerves by inserting the electrode leads into the corresponding sacral foramina, typically at the S3 level. The electrodes are inserted subcutaneously and subsequently connected to an implantable pulse generator (IPG). The safety and efficacy of SNM for the treatment of OAB is supported by multiple studies and is well documented, including a five-year tolerability profile in patients with urge incontinence and urinary frequency and urgency. SNM is also approved for chronic fecal incontinence in patients who have failed treatment or are not suitable for more conservative treatments.
[0053] A. Implantation of the Sacral Neuromodulation System
[0054] Currently, there is a trial phase for SNM qualification, which, if successful, leads to permanent implantation. The trial phase is a test stimulation period that allows the patient to assess whether the treatment is working. Typically, there are two techniques used to perform test stimulation. The first is an office-based procedure called a percutaneous nerve evaluation (PNE), and the other is a staged trial.
[0055] In PNE, a bore needle is usually first used to determine the best stimulation location, usually at the S3 level, and to assess the integrity of the sacral nerves. Motor and sensory responses are used to verify proper placement of the needle. A temporary stimulation lead (monopolar electrode) is then placed near the sacral nerve under local anesthesia. This procedure can be performed in an office setting without fluoroscopy. The temporary lead is then connected to an external pulse generator (EPG) taped to the patient's skin during the trial phase. The level of stimulation can be adjusted to provide the best comfort level for the specific patient. The patient will monitor his or her urination for 3 to 7 days to see if there is any symptom improvement. The advantage of PNE is that it is an incision-free procedure that can be performed in the doctor's office using local anesthesia. If a patient fails this pilot test, the doctor may still recommend a staged trial as described below. If the PNE trial is positive, the temporary trial lead is removed and a permanent quadripolar stimulation lead and IPG are implanted under general anesthesia.
[0056] A phased trial involves implanting a permanent quadripolar stimulation lead in the patient from the outset. It also requires the use of a bore needle to identify the nerve and the optimal stimulation location. The lead is implanted near the S3 sacral nerve and connected to the EPG via a lead extension. The procedure is performed in the operating room under fluoroscopic guidance and is done under local or general anesthesia. The EPG is adjusted to provide the patient with optimal comfort, and the patient monitors his or her urination for up to two weeks. If the patient achieves meaningful symptom improvement, he or she is considered a suitable candidate for permanent implantation of an IPG under general anesthesia, usually in the upper buttocks area, such as Figure 3 shown.
[0057] In terms of measuring the outcome of SNM treatment of urinary dysfunction, urinary dysfunction indicators (e.g., urge incontinence, frequent urinary urgency, and non-obstructive urinary retention) can be assessed through unique primary urination diary variables. These same variables are used to measure treatment outcomes. SNM treatment is considered successful if there is at least a 50% improvement in any of the primary urination diary variables compared to baseline. For patients with urgency urinary incontinence, these urination diary variables can include: number of leaks per day, number of severe leaks per day, and number of pads used per day. For patients with frequent urinary urgency, the primary urination diary variables can include: number of urinations per day, urine volume per urination, and urgency before each urination. For patients with retention, the primary urination diary variables can include: catheter capacity per catheterization and number of catheterizations per day. For patients with fecal incontinence, the outcome indicators recorded in the urination diary include: number of leaks per week, number of days with leakage per week, and urgency before each leak.
[0058] The disclosed embodiments relate to remote programming of a neurostimulation system adapted to deliver neurostimulation to target neural tissue in a manner that results in partial or complete activation of target neural fibers, causing enhancement or inhibition of neural activity, the target neural tissue may be the same as or different from the stimulation target, which controls organs and structures related to bladder and bowel function.
[0059] B. Neurostimulation Lead Placement and Programming
[0060] Neurostimulation relies on the continuous delivery of therapeutic stimulation from a pulse generator to a specific nerve or targeted area via one or more neurostimulation electrodes. The neurostimulation electrodes are disposed on the distal end of an implantable lead that can be advanced through a tunnel formed in the patient's tissue. Implantable neurostimulation systems provide patients with a great deal of freedom and flexibility, but it may be easier to adjust the neurostimulation electrodes of these systems before they are surgically implanted. Physicians want to confirm that the patient has the desired motor and / or sensory response before implanting an IPG. For at least some treatments (including treatment of at least some forms of urinary and / or bowel dysfunction), demonstrating an appropriate motor response may be very beneficial for accurate and objective lead placement, while a sensory response may not be required or available (e.g., the patient is under general anesthesia).
[0061] Placing and calibrating neural stimulation electrodes and implantable leads sufficiently close to specific nerves is beneficial to the therapeutic effect. Therefore, various aspects and embodiments of the present disclosure are directed to assisting and improving the accuracy and precision of neural stimulation electrode placement. In addition, various aspects and embodiments of the present disclosure are directed to assisting and refining protocols for setting therapeutic treatment signal parameters for stimulation programs implemented by implanted neural stimulation electrodes.
[0062] In an exemplary embodiment, stimulation can be tested by utilizing neuromuscular responses, for example, by observing responses or by using electromyography ("EMG") (also known as surface electromyography), to determine whether implantable leads and neurostimulation electrodes are in the desired or correct position. EMG is a technique that uses an EMG system or module to evaluate and record the electrical activity generated by muscles, which produces a recording called an electromyogram. EMG detects the electrical potential generated by muscle cells when they are electrically activated or neurally activated. These signals can be analyzed to detect activation levels or recruitment sequences. EMG can be performed through the patient's skin surface, within the muscle, or by electrodes placed near the target muscle in the patient's body, or using a combination of external and internal structures. When a muscle or nerve is stimulated by an electrode, EMG can be used to determine whether the relevant muscle is activated in response to the stimulation (i.e., whether the muscle is fully contracted, partially contracted, or not contracted). Therefore, the degree of activation of the muscle can indicate whether the implantable lead or neurostimulation electrode is in the desired or correct position of the patient. In addition, the degree of activation of the muscle can indicate whether the neurostimulation electrode provides stimulation of sufficient intensity, amplitude, frequency, or duration to affect the treatment regimen for the patient. Thus, the use of EMG provides an objective and quantitative means by which to standardize the placement of implanted leads and neurostimulation electrodes, thereby reducing subjective assessments of patient sensory responses. Although the use of EMG responses is discussed in some of the exemplary programming methods described below, it should be understood that the remote programming concepts described herein can be applied to any type of programming method, including programming methods that do not utilize EMG.
[0063] C. System Embodiment
[0064] Figure 1An exemplary neurostimulation system setup is schematically shown, which includes a setup for a trial neurostimulation system 200 and a setup for a permanently implanted neurostimulation system 100. The EPG 80 and IPG 50 are each compatible and wirelessly communicate with a clinician programmer (CP) 60 and a patient remote control 70, which are used to position and / or program the trial neurostimulation system 200 and / or the permanently implanted system 100 after a successful trial. As described above, the system utilizes the cable set and EMG sensor patches in the trial system setup 100 to facilitate lead placement and neurostimulation programming. The CP may include dedicated software, dedicated hardware, and / or both to assist in lead placement, programming, reprogramming, stimulation control, and / or parameter setting. In addition, each of the IPG and EPG allows the patient to have at least some control over the stimulation (e.g., start a preset program, increase or decrease stimulation), and / or monitor battery status with a patient remote control. This approach also allows for an almost seamless transition between a trial system and a permanent system. The clinician may use the CP during initial programming of the EPG and IPG, or may use the CP remotely during subsequent remote programming of the IPG in a communication session with remote support 90. The system may include one or more intermediate devices to facilitate the communication session between the remote support and the IPG and the patient. The one or more intermediate devices may include a patient device 80, and may further utilize an accessory device, such as a charger 50, a patient remote control 70, or a reprogramming communicator 75, to allow communication between the patient device 80 and the IPG.
[0065] During initial programming, when the leads are implanted in the patient, the physician uses the CP 60 to adjust the settings of the EPG and / or IPG. The CP can be a tablet device that the clinician uses to program the IPG or control the EPG during a trial. The CP can also include the ability to record stimulation-induced electromyograms to facilitate lead placement and programming. A patient remote control 70 can allow the patient to turn stimulation on or off, or change the stimulation from the IPG at the time of implantation, or change the stimulation from the EPG during the trial phase. The CP 60 has a control unit that can include a microprocessor and dedicated computer code instructions for implementing the methods and systems used by the physician when deploying the treatment system and setting treatment parameters. The CP typically includes a graphical user interface for easy programming by clinician input. The CP can include a module with hardware and computer code that performs EMG analysis, wherein the module can be a component of the control unit microprocessor, a pre-processing unit coupled or connected in series to the stimulation and / or sensory cables, and the like.
[0066] In other aspects, whenever the lead is connected to the EPG, IPG or CP, the CP 60 allows the clinician to read the impedance of each electrode contact to ensure a reliable connection and that the lead is intact. This can be used during positioning the lead and when programming the lead to ensure that the electrode is working properly. The CP 60 is also capable of saving and displaying previous (e.g., up to the last four) programs used by the patient to help facilitate reprogramming. Alternatively, the most recent program can be stored on the IPG, the patient's device, or in the patient's archive and stored in a data center accessible to the patient's device and / or CP. In some exemplary embodiments, the CP 60 also includes a USB port and a charging port for saving reports to a USB drive. The CP can be configured to operate in combination with the EPG when the lead is placed in the patient's body, and in combination with the IPG during programming. During a test simulation, the CP can be electronically coupled to the EPG via a dedicated cable set or via wireless communication, allowing the CP to configure, modify or otherwise program the electrodes on the lead connected to the EPG. The CP may also include a physical or virtual on / off button to turn the CP on and off and / or turn stimulation on and off
[0067] Figure 2A-2C Diagram showing various neural structures of a patient that may be amenable to neurostimulation therapy. Figure 2A Different parts of the spinal cord and the corresponding nerves in each part are shown. The spinal cord is a bundle of elongated nerves and supporting cells extending from the brainstem along the cervical spinal cord, through the thoracic spinal cord, and reaching the space between the first lumbar vertebra and the second lumbar vertebra in the lumbar spinal cord. After leaving the spinal cord, the nerve fibers split into multiple branches, which control various muscles and organs, and transmit impulses of sensation and control between the brain and the organs and muscles. Since some nerves may include branches that control certain organs (e.g., bladder), as well as branches that control certain muscles of the legs and feet, stimulating nerves at or near the nerve roots near the spinal cord can stimulate the nerve branches that control the target organs, which can also cause muscle reactions associated with stimulating another nerve branch. Therefore, by visually, by using EMG as described herein or both to monitor certain muscle reactions, doctors can determine whether the target nerve is stimulated. Although a certain level of stimulation may cause a robust muscle reaction visible to the naked eye, a lower level (e.g., subthreshold) of stimulation can still provide activation of the nerves associated with the target organ without causing a corresponding muscle reaction or a reaction that is only visible with EMG. In some exemplary embodiments, this low level of stimulation also does not cause any paresthesia. This is advantageous because it allows the disease to be treated through neural stimulation without otherwise causing discomfort, pain or undesirable muscle reactions in the patient.
[0068] Figure 2BNerves associated with the lower back in the lower lumbar cord region are shown, with the nerve bundles exiting the spinal cord and passing through the sacral foramen of the sacrum. In some exemplary embodiments, a neurostimulation lead is advanced through the sacral foramen until the neurostimulation electrode is positioned at the anterior sacral nerve root, and an anchoring portion of the lead proximal to the stimulation electrode is typically disposed dorsal to the sacral foramen through which the lead passes, thereby anchoring the lead in place. Figure 2C A detailed view of the lumbosacral trunk and sacral plexus is shown, particularly the SI-SS nerves of the lower sacrum. The S3 sacral nerve is particularly important for the treatment of bladder-related dysfunction, particularly OAB.
[0069] Figure 3 An example of a fully implanted neurostimulation system 100 suitable for sacral nerve stimulation is schematically shown. The neurostimulation system 200 includes an IPG implanted in the lower back region and connected to a neurostimulation lead extending through the S3 foramen for stimulating the S3 sacral nerve. The lead is anchored by a toothed anchoring portion 30 that maintains the position of a set of neurostimulation electrodes 40 along a targeted nerve, in this example, the anterior sacral nerve root S3 that debilitates the bladder, in order to provide treatment for a variety of bladder-related dysfunctions. Although this embodiment is suitable for sacral nerve stimulation, it should be understood that similar systems can be used to treat patients suffering from, for example, chronic, severe, refractory neuropathic pain originating from peripheral nerves or various urinary dysfunctions or other indications. The implantable neurostimulation system can be used to stimulate a targeted peripheral nerve or the posterior epidural space of the spine.
[0070] The characteristics of the electrical pulses may be controlled via a controller of the implanted pulse generator. In some exemplary embodiments, these characteristics may include, for example, the frequency, amplitude, pattern, duration, or other aspects of the electrical pulses. These characteristics may include, for example, voltage, current, etc. Such control of the electrical pulses may include: creating one or more electrical pulse programs, plans, or patterns, and in some exemplary embodiments, this may include selecting one or more pre-existing electrical pulse programs, plans, or patterns. Figure 3 In the depicted embodiment, the implantable neurostimulation system 220 includes a controller in an IPG having one or more pulse programs, schedules, or patterns that can be pre-programmed or created as described above. In some exemplary embodiments, these same features associated with the IPG can be used in an EPG of a partially implanted trial system used prior to implantation of a permanent neurostimulation system 200.
[0071] Figure 4An example neurostimulation system 300 is shown that is fully implantable and suitable for sacral nerve stimulation therapy. The implantable system 300 includes an IPG 10 that is coupled to a neurostimulation lead 20 that includes a set of neurostimulation electrodes 40 at the distal end of the lead. The lead includes a lead anchoring portion 30 that has a series of tines extending radially outward to anchor the lead and maintain the position of the neurostimulation lead 20 after implantation. The lead 20 may also include one or more radiopaque markers 25 to assist in locating the lead using visualization techniques such as fluoroscopy. In some exemplary embodiments, the IPG provides monopolar or bipolar electrical pulses delivered to the targeted nerve through one or more neurostimulation electrodes. In sacral nerve stimulation, the lead is typically implanted through the S3 foramen, as described herein.
[0072] like Figure 1 As shown in the schematic diagram of the neurostimulation system in , the system may also include a patient remote control 70 and a CP60, each of which is configured to communicate wirelessly with an implanted IPG, or to communicate wirelessly with an EPG during a trial. The CP60 can be a tablet device used by a clinician to program the IPG and EPG. The device also has the ability to record stimulation-evoked electromyograms (EMGs) to facilitate lead placement, programming, and / or reprogramming. The patient remote control can be a battery-operated portable device that communicates with the EPG and IPG using radio frequency (RF) signals and allows the patient to adjust the stimulation level, check the status of the IPG battery level, and / or turn stimulation on or off.
[0073] In one aspect, the IPG is wirelessly charged by inductive coupling using a charging device 50 (CD), which is a portable device powered by a rechargeable battery to allow the patient to move while charging. The CD is used to transcutaneously charge the IPG by RF induction. The CD can be attached to the patient's skin using an adhesive, or can be fixed in place using a strap 53 or by an adhesive patch 52, such as Figure 1 The CD can be charged by plugging it directly into a socket or by placing it in a charging cradle or station 51 connected to an AC wall socket or other power source.
[0074] In one aspect, the CD is equipped with one or more communication antennas that allow communication with the IPG. In this embodiment, the communication unit is via shortwave radio waves, typically MedRadio. Typically, the communication unit (e.g., MedRadio) has been used to communicate with the IPG during a charging session, however, the communication unit can also be used to facilitate reprogramming of the remote support entity, since the CD is also equipped with another communication unit, through which the CD can communicate with one or more additional external devices. In some exemplary embodiments, such additional communication can include communication with a patient device (e.g., via Bluetooth). This configuration allows the CD to communicate with both the IPG and the patient device, so that communication can be established between remote support and the IPG for programming using the charger, as described in further detail below.
[0075] Figure 5A-5B A detailed view of an IPG and its internal components is shown. In some exemplary embodiments, the pulse generator can generate one or more non-ablative electrical pulses that are delivered to a nerve to control pain or cause some other desired effect, such as inhibiting, preventing, or disrupting neural activity for treating OAB or bladder-related dysfunction. In some applications, pulses having pulse amplitudes in a range between 0mA to 1000mA, 0mA to 100mA, 0mA to 50mA, 0mA to 25mA, 0mA to 12.5mA, and / or any other or intermediate amplitude ranges can be used. One or more of the pulse generators may include a processor and / or a memory that are suitable for providing instructions to and receiving information from other components of the implantable neural stimulation system. The processor may include a microprocessor, such as from Advanced Micro Devices (Advanced Micro Devices, Inc) commercially available microprocessors, etc. The IPG may include energy storage features (eg, one or more capacitors, one or more batteries), and typically includes a wireless charging unit.
[0076] One or more properties of the electrical pulses can be controlled via a controller of the IPG or EPG. In some exemplary embodiments, these properties may include, for example, the frequency, amplitude, pattern, duration, or other aspects of timing and amplitude of the electrical pulses. These properties may further include, for example, voltage, current, and the like. Such control of the electrical pulses may include: creating one or more electrical pulse programs, plans, or patterns, and in some exemplary embodiments, this may include: selecting one or more pre-existing electrical pulse programs, plans, or patterns. In one aspect, the IPG 100 includes a controller having one or more pulse programs, plans, or patterns that can be created and / or pre-programmed. In some exemplary embodiments, the IPG may be programmed to change stimulation parameters, including pulse amplitudes in the range of 0 mA to 10 mA, pulse widths in the range of 50 μs to 500 μs, pulse frequencies in the range of 5 Hz to 250 Hz, stimulation modes (e.g., continuous or cyclic), and electrode configurations (e.g., anode, cathode, or off) to achieve optimal patient-specific treatment outcomes. In particular, this allows the optimal settings to be determined for each patient, even if each parameter may vary from person to person.
[0077] like Figure 5A-5B As shown in , the IPG may include a head 11 at one end and a ceramic portion 14 at an opposite end. The head 11 houses a feedthrough assembly 12 and a connector stack 13, while the ceramic housing portion 14 houses an antenna assembly 16 to facilitate wireless communication with a clinician program, a patient remote control, and / or a charging coil, thereby facilitating wireless charging using a CD. The remainder of the IPG is covered with a titanium housing portion 17, which encapsulates a printed circuit board, memory, and controller assembly to facilitate execution of the electrical pulse program described above. The head of the IPG includes a four-pin feedthrough assembly 12, which is coupled to a connector stack 13, and the proximal end of the lead is coupled in the connector stack 13. These four pins correspond to the four electrodes of the neurostimulation lead. In some exemplary embodiments, The connector block is electrically connected to four platinum-iridium alloy feedthrough pins, which are brazed to an alumina ceramic insulating plate along with a titanium alloy flange. This feedthrough assembly is laser seam welded to the titanium-ceramic brazed housing to form a complete sealed housing for the electronics.
[0078] In some embodiments, Figure 5AAs shown in , a ceramic and titanium brazed housing is used for one end of the IPG, where the ferrite coil and PCB antenna assembly are located. A reliable airtight seal is provided via a ceramic to metal brazing technique. The zirconia ceramic may include 3Y-TZP (3 mol% yttrium stabilized tetragonal zirconia polycrystalline) ceramic, which has high bending strength and impact resistance and has been commercially used in many implantable medical technologies. In one aspect, when the communication antenna is housed within the sealed ceramic housing, the use of ceramic material provides an effective, RF-transparent window for wireless communication with an external patient remote control and clinician programmer. The ceramic window further facilitates miniaturization of the implant while maintaining an effective RF-transparent window for long-term, reliable wireless communication between the IPG and an external controller (e.g., a patient remote control and a CP). In another aspect, the ferrite core is part of the charging coil assembly 15, as shown in FIG. Figure 5B , which is located inside the ceramic housing 14. The ferrite core concentrates the magnetic field flux through the ceramic housing opposite the metal housing portion 17. This configuration maximizes the coupling efficiency, thereby reducing the required magnetic field and, in turn, reducing device heating during charging.
[0079] In one aspect, the IPG can be programmed with various stimulation modes, which can be determined by the CP or selected by the physician using the CP during initial programming or remote programming. In some exemplary embodiments, the IPG / EPG can be configured with two stimulation modes: a continuous mode and a cyclic mode. Compared to the continuous mode, the cyclic mode saves energy, thereby extending the battery charging interval and the life of the device. The cyclic mode may also help reduce the risk of neuroadaptation in some patients. Neuroadaptation is the change in the responsiveness of the nervous system to constant stimulation over time. Therefore, the cyclic mode may also mitigate neuroadaptation, thereby providing long-term therapeutic benefits. Fig. 6A An example of stimulation in a cyclic mode is shown, where the duty cycle is the stimulation on time versus the stimulation on time plus the stimulation off time. In some exemplary embodiments, the IPG / EPG may be configured with a ramp feature, e.g. Figure 6B In these embodiments, the stimulation signal ramps up and / or down between stimulation on and stimulation off levels. This feature helps reduce the sudden "jolt" or "shock" feeling that some patients may experience when initially turning on stimulation or during the cycle-on phase of a cycle mode. This feature is particularly beneficial for patients who require relatively high stimulation settings and / or for patients who are sensitive to electrical stimulation.
[0080] In order to activate the axon of a nerve fiber, an electric field needs to be applied outside the axon to generate a voltage gradient across its membrane. This can be achieved by pumping electric charge between the electrodes of a stimulator. The action potential that transmits information through the nervous system is generated when the outside of the nerve is depolarized to a certain threshold, which is determined by the amount of current delivered. In order to generate continuous action potentials in the axon, this extracellular gradient threshold needs to be reached with the delivery of each stimulation pulse. In order to activate the axon of a nerve fiber, an electric field needs to be applied outside the axon to generate a voltage gradient across its membrane. This can be achieved by pumping electric charge between the electrodes of a stimulator. The action potential that transmits information through the nervous system is generated when the outside of the nerve is depolarized to a certain threshold, which is determined by the amount of current delivered. In order to generate continuous action potentials in the axon, this extracellular gradient threshold needs to be reached with the delivery of each stimulation pulse.
[0081] In traditional systems, a constant voltage power supply is able to maintain the output voltage of the electrode, thereby delivering sufficient current to activate the axon upon initial implantation. However, in the first few weeks after implantation, tissue encapsulation occurs around the electrode, which causes the impedance (tissue resistance) to increase. According to Ohm's law (I = V / R, where I is the current, V is the voltage, and R is the tissue impedance of the electrode pair), the current delivered by the constant voltage stimulator will therefore decrease, producing a smaller gradient around the nerve. When the impedance reaches a certain value, the extracellular depolarization will drop below the threshold, so no more action potentials may be generated in the axon. Patients often need to adjust the voltage of their system to readjust the current and restore the effectiveness of the treatment.
[0082] In contrast, certain exemplary embodiments use a constant current power supply. In one aspect, the system uses feedback to adjust the voltage so that the current is maintained regardless of what happens to the impedance (until the compliance limit of the device is reached), thereby keeping the gradient field around the nerve constant over time. Using a constant current stimulator, the same current initially selected is maintained regardless of impedance changes to maintain the therapeutic effect.
[0083] Figure 7 Schematically shows a block diagram of the configuration of CP 60 and associated interfaces and internal components. As described above, CP 60 is generally a tablet computer with software running on a standard operating system. CP 60 includes a communication module, a stimulation module and an EMG sensing module. The communication module communicates with IPG and / or EPG in the medical implant communication service band for programming IPG and / or EPG. Although this configuration reflects a portable user interface display device (e.g., a tablet computer), it should be understood that the CP can be incorporated into various other types of computing devices, such as a laptop computer, a desktop computer, or a stand-alone terminal for a medical facility.
[0084] D. Workflow for programming and reprogramming using CP
[0085] Figure 8-9 A schematic diagram of the workflow used in lead placement and programming of a neurostimulation system using CP with EMG assistance is shown. Figure 8 A detailed overview of the use of a CP with a graphical user interface for lead placement and subsequent programming, which may include initial programming and reprogramming, is schematically shown. Fig. 9 A schematic diagram of a CP graphical user interface screen representation of a workflow including various settings and connections associated with each step is shown.
[0086] III. Neural Stimulation Programming
[0087] After lead placement and nerve localization, the neurostimulation system is programmed. Typically, programming utilizes stimulation thresholds and / or characteristics of the electrodes, which may be performed specifically for programming, or may be performed during lead placement and subsequently used during programming. Previously determined stimulation thresholds or electrode characteristics may be stored on any device of the system shown, or may be stored on a data center of a first-party developer of the system and accessed by remote support or the patient device during programming or reprogramming. While some of the programming examples herein describe the use of EMG measurements to inform electrode characterization, it should be understood that these EMG measurements may be stored and subsequently used during the reprogramming process, or various other methods that do not use EMG may be used, as known in the art.
[0088] In some exemplary embodiments, the system stores the last four programs on the memory of the IPG / EPG. This is particularly advantageous for reprogramming because it allows a physician using a completely different CP to access the most recent program used in neurostimulation, who otherwise may not have access to the programming information. In another aspect, the programming data may be accessible online or on a cloud server and associated with a unique identifier for a given IPG / EPG, so that a different CP can easily access and download program information as needed for reprogramming.
[0089] A. Electrode Characteristics
[0090] In one aspect, during lead placement, CP 60 can characterize the suitability of each electrode in nerve stimulation using previously recorded thresholds. In some exemplary embodiments, CP 60 can be configured to program IPG / EPG using only EMG records from one muscle, which are from the anal canal or from the big toe reaction. This programming can also utilize visual observation of the reaction and the maximum reaction amplitude recorded. In one aspect, CP 60 performs programming without the need for anal canal reaction observation or EMG waveform measurement of anal canal reaction. In some exemplary embodiments, CP 60 performs programming using only EMG records from the big toe reaction, such as shown in Figure 15C, where the graphical user interface of CP displays patient information 63, which can include information about the patient's subjective response to stimulation or treatment. In an alternative embodiment, CP 60 can be used to program EPG / IPG using only EMG from the anal canal reaction.
[0091] In one aspect, the EMG recordings may be obtained during lead placement, or more typically, during programming, so that the patient can provide subjective sensory response data while performing a big toe response with a given electrode during testing. Programming may further include: visual observation of the big toe response and / or maximum response amplitude obtained during programming. Allowing the IPG / EPG to be programmed without the need for anal canal responses is advantageous because the patient is not under general anesthesia when programming is performed, and anal canal responses may be uncomfortable and painful for the patient. This also allows the CP to receive subjective sensory data from the patient during programming regarding any discomfort, paresthesia, or pain associated with stimulation of a particular electrode configuration.
[0092] In one aspect, the EMG recording can be a recording obtained during lead placement, or more typically, during programming, so that the patient can provide subjective sensory response data while performing a big toe reaction with a given electrode during testing. Programming can further include: visual observation of the big toe reaction and / or maximum reaction amplitude obtained during programming. It is advantageous to allow programming of the IPG / EPG without the need for anal canal reactions because the patient is not under general anesthesia when performing programming, and anal canal reactions may be uncomfortable and painful for the patient. This also allows the CP to receive subjective sensory data from the patient during programming regarding any discomfort, paresthesia, or pain associated with stimulation of a particular electrode configuration.
[0093] B. Electrode Configuration Recommendations
[0094] In one aspect, the system configuration determines multiple electrode configuration recommendations based on threshold data using electrode characterization and / or based in part on patient responses to previously obtained electrode stimulation (e.g., via EMG or visual observation), and provides the recommendations to the clinician. Fig.10 An example method for determining and providing electrode configuration recommendations implemented with CP is shown. In such a method, the system first checks the impedance of each electrode using pre-set stimulation parameters, and can lock any electrode with unacceptable impedance (<50 or >3,000 ohms) to be designated as an anode or cathode. The system then identifies threshold data associated with each electrode based on data previously recorded during lead placement or by generating new threshold data. The system grades the electrodes based on thresholds (e.g., "good," "ok," and "bad") and sorts the electrodes in each layer. Any electrode that causes an unpleasant sensation is excluded from use as a cathode. The system then determines multiple electrode configuration recommendations based on predetermined rules, preferably at least four different configurations, and then presents them to the clinician using CP.
[0095] In one aspect, the electrode configuration is determined based on the threshold data according to the following rules: (1) each contact in the "good" layer is assigned a single cathode configuration, prioritized from the farthest pair to the closest pair; (2) each contact in the "good" layer is assigned a single cathode configuration, prioritized from the lowest threshold to the highest threshold; (3) each pair of adjacent electrodes in the "good" layer is assigned a dual cathode configuration, prioritized by the lowest combined threshold; (4) each contact in the "normal" layer is assigned a single cathode configuration, prioritized from the lowest to the highest threshold; and (5) each pair of adjacent electrodes in the "good" and "normal" layers is assigned a dual cathode configuration, prioritized by the lowest combined threshold. Anode assignments for cathode configurations are as follows: for a monopolar configuration, the IPG housing or "can" is assigned as the anode; for a bipolar configuration, the electrode farthest from the cathode with acceptable impedance is designated as the anode.
[0096] After identifying the electrode configuration recommendation, the system typically presents the electrode configuration recommendation to the physician on the user interface of the CP, such as Fig.11 As shown in , the doctor can select any electrode configuration to test on the user interface, modify the recommended electrode configuration as needed, or create a new electrode configuration. In one aspect, the system presents electrode configuration recommendations within a selectable menu and may include one or more default values or attributes for a given electrode recommendation.
[0097] In one aspect, in an ideal setup where each electrode has a “good” impedance, the system simply recommends that each contact act as a single cathode. While having four “good” electrodes is desirable, having at least three “good” electrodes for initial programming is acceptable. The algorithm described above recommends the best electrode selection for a given situation. While each physician may have their own way of selecting electrodes for programming, providing a set of electrode configuration recommendations that are easy for the physician to review and select helps standardize the process, shorten the duration of the procedure, and improve patient outcomes, especially for inexperienced implanters or poorly trained personnel.
[0098] In one aspect, the above algorithm assumes that the electrode threshold is a single input parameter. In some exemplary embodiments, the system allows the physician to choose through the CP what parameter (sensory or motor response or combination) to use to determine the threshold for each electrode. The physician can also choose whether to rely on previously obtained EMG feedback to determine the threshold. In another aspect, qualitative sensory feedback will be considered in electrode selection, for example, if the patient reports unpleasant sensations for any particular electrode, the electrode is excluded from use as a cathode. In another aspect, for all contacts in the "good" layer, the algorithm prioritizes single cathodes over dual cathodes. In some exemplary embodiments, electrodes are stratified according to the following hierarchy: "Good" = "l-3mA"; "Normal" = "0.5-lmA" and "3-4mA"; "Bad" = "<0.5mA" and ">4mA."
[0099] Figures 12A-12B The description is shown according to the above Fig. 12A In each case 1 and Fig. 12B The algorithm described in Case 2 is used to select the four recommended electrodes for bipolar and monopolar therapy in this case study.
[0100] C. Program selection, modification and testing
[0101] When programming a neurostimulation system, the EMG signal can be used to assess the quality of the programming by allowing the user to see whether the stimulation elicits a motor response. In some exemplary embodiments, the user can manually observe the EMG response and enter the observation into the CP and try to set the stimulation amplitude at a level that elicits the desired motor response.
[0102] Figures 13A-13K The graphical user interface of the CP is shown during initial programming and testing, but it should be understood that various aspects are also applicable to reprogramming. Fig.13A Describes how the CP 60 reconnects to the patient device and verifies the device information. The physician can view the Fig. 13B The device information display 66 is shown to confirm this. Fig. 13Bis an IPG data display showing a summary of thresholds and contact status. Threshold data for Lead Placement is recorded and can be viewed in summary form on this page. The symbol to the right of each contact represents the impedance associated with that contact: Green ("Good"): 50-3,000 Ohms, Red ("Bad"): <50 or >3,000 Ohms. In some exemplary embodiments, yellow may indicate "Marginal," while in other embodiments there will be no yellow option. The colored circle around each contact represents a qualitative assessment of that contact from the perspective of lead placement. This is a summary of the information in the Threshold Details tab. As shown Fig. 13B , electrodes #0 and #1 are shown in green, electrode #2 is shown in orange, and electrode #3 is shown in red. In one aspect, CP 60 can program the IPG / EPG without utilizing EMG waveforms and / or visual responses and patient sensory data obtained by CP 60 during lead placement. Programming can also utilize additional patient information obtained from the patient during programming (e.g., subjective input regarding sensory perception).
[0103] Fig. 13C Programming of the IPG is shown and testing of a first electrode configuration recommendation is shown on display 67 which shows four electrode configuration recommendations determined according to the algorithm discussed above. The electrode configuration recommendations are based on the input of threshold details determined during lead placement characterization. It should be understood that electrode thresholds may also be determined during programming. The colored circle around each contact represents a qualitative assessment of that contact from lead placement. This is a summary of the information in the Threshold Details tab. For retrospective data analysis, the presence of motor responses and the quality of sensory responses are manually recorded. Amplitude adjustments may be made in either automatically adjusted increments or fixed increments, as previously discussed.
[0104] exist Fig. 13C In the first electrode configuration recommendation in , the lead is operated in bipolar mode between electrodes 0 and 3, with electrode #0 acting as the cathode and electrode #3 acting as the anode. The same process is repeated for each of the four electrode recommendations, such as Fig.13D , where a dual cathode configuration is being tested.
[0105] In one aspect, the graphical user interface allows the user to adjust various parameters associated with each recommended electrode configuration being tested. Fig.13EAs shown in FIG. 6 , the graphical user interface of the CP 60 includes an additional parameter display 68 in which the physician selects and adjusts various parameters (e.g., frequency, pulse width, cycle, and pattern) associated with each electrode configuration according to the needs of the particular treatment and / or patient. After the adjustment, the patient and procedure information can be updated and recorded in the CP 60. In another aspect, the physician can use the CP to reassign the electrode polarity associated with a given electrode configuration recommendation, such as Figure 13G , where a cursor can be used to change the electrode polarity on the electrode status display 64. In yet another aspect, the user can switch between bipolar mode and monopolar mode by selecting a mode button in the additional parameter display 68. When the monopolar mode is selected, the CP 60 will display a plurality of monopolar electrode configuration recommendations, such as Fig.13H When the physician is satisfied with the electrode configuration settings, the physician can select the patient device menu (eg Fig.13J ), confirm treatment settings (such as viewing Figure 13K The current therapy display 69 is shown, and the therapy is saved to the patient device, continuing with saving the settings in the CP 60, after which the IPG / EPG is fully programmed and the CP 60 can be detached.
[0106] In one aspect, after the IPG / EPG is programmed according to the methods described above, the patient evaluates the selected program over a predetermined period of time. Typically, the patient is able to make limited adjustments to the program, such as increasing or decreasing the amplitude or turning off treatment. If after the evaluation period, the patient does not experience relief from the treatment state, or if other problems arise, the patient returns to the physician and the IPG / EPG is reprogrammed with the CP in a process similar to the programming methods described above to select an alternative electrode configuration from the recommended configurations, or to develop a new treatment program that provides effective treatment.
[0107] V. Remote Programming
[0108] In one aspect, the methods and apparatus described in detail throughout facilitate remote programming of the IPG. As described herein, "reprogramming" refers only to programming operations that occur after initial programming, and may include: determining an entirely new program or troubleshooting a current treatment program by remotely modifying one or more treatment parameters. Reprogramming may utilize some information previously obtained during lead placement or initial programming, or the programming process may be repeated or an alternative programming process may be utilized. In some exemplary embodiments, the programming process may utilize algorithms or rules to determine an appropriate treatment program based on known parameters. In other embodiments, the programming process may include a clinician applying or adjusting parameters based on their preferences. It should be understood that any aspect of the programming process described herein may also be applied to remote reprogramming.
[0109] A. Patient Interface / Session Initiation
[0110] In one scenario, after a patient is implanted with neural stimulation leads and an implantable pulse generator, the patient may experience unsatisfactory treatment due to lack of efficacy or discomfort with stimulation and reprogramming. Various aspects of the process that may enable or inform reprogramming are described in detail below.
[0111] In some exemplary embodiments, the patient completes a bladder or bowel diary included on a "Patient App" installed on a patient device (e.g., a smartphone) to "confirm" or enable the remote programming function. A comprehensive symptom diary (bladder and / or bowel diary) allows the patient to record their symptoms prior to the initial assessment of device suitability, prior to a request, and for a period of time after a reprogramming session. In some exemplary embodiments, a programming technician can access this information remotely to assess programming needs. Alternatively, the diary function can be performed on a variety of other devices such as a tablet device, laptop, or desktop computer.
[0112] In some exemplary embodiments, the patient places the charger on the IPG to charge and communicate with the patient app on the patient device. In some exemplary embodiments, the charger to IPG communication is MedRadio and the charger to patient app communication is Bluetooth. In other embodiments, the system utilizes a patient remote control that communicates with the IPG via MedRadio and connects to the patient app on the patient device via Bluetooth.
[0113] In some exemplary embodiments, a patient app on a patient device (e.g., a smartphone) communicates with a remote programming service via Wifi. Typically, the patient app can be configured to utilize both Bluetooth (e.g., to a charger) and Wifi functionality. In some exemplary embodiments, to avoid the need for standard voice calls, voice over internet protocol (VoIP) technology can be incorporated into the patient app, for example by using Skype integration. In other embodiments, the system can utilize a dedicated, dedicated intermediate communication device that communicates with the IPG via MedRadio and connects to the patient device via Bluetooth. In other embodiments, the system can utilize a dedicated patient device that communicates with the IPG via MedRadio and connects to the remote programming service via Wifi.
[0114] B. Remote programming function
[0115] In another aspect, the patient app of the patient device can be configured to communicate with a remote programming "backend" via Wifi. In some exemplary embodiments, the communication includes a data connection between the patient and the programming technician plus a voice or video chat connection. The backend components can be deployed in a variety of ways, including any of the following: cloud-based, local servers, or hosted servers. The communication can include any of the following: program information (e.g., current treatment, electrode characteristics, stimulation thresholds) and patient information (e.g., account, profile information, symptom information diary from the patient).
[0116] In another aspect, the reprogramming procedure can use a doctor app or a remote programming app (these terms can be used interchangeably throughout the text), which can be a mobile / web application that serves a browser. This approach provides the greatest flexibility and scalability. This approach further provides versatility between several options for supporting team structures, such as any one of a virtual call center with technicians from the equipment provider, a team of technicians in a call center, and a virtual call center team of contracted clinicians (e.g., super users, professional nurses, or doctors). In some exemplary embodiments, the application can be configured to provide direct contact from the patient to a doctor / clinician of their own choice, which may be preferred for clinicians who wish to maintain control of the entire process. In some exemplary embodiments, the patient app cannot be accessed through a browser and must be installed on the patient's portable device (e.g., a smartphone, a tablet device).
[0117] In another aspect, the Remote Programming App synchronizes to other databases as needed. These additional databases may include a Patient Care Manager (PCM), which allows support technicians to view relevant patient treatment history. In some exemplary embodiments, the patient's recent treatment history can be extracted from the IPG via the charger or patient remote control and shared via the Patient App connection to the Remote Programming App. Thus, the Patient App and the Remote Programming App create an application framework through which the patient and remote support can interact and access information through any subject device. In one aspect, the framework allows remote support authorizations and permissions for an implanted pulse generator to exceed the patient's authorizations and permissions to enable remote support to control and / or adjust the implanted pulse generator for programming.
[0118] C. Remote Programming Process (Patient / Technology Interaction)
[0119] The system application is configured so that a technician receives a communication (e.g., a "call") from a patient who wishes to adjust a device setting remotely, typically initiated via the Patient App. In some exemplary embodiments, remote support can then access the patient's history stored in the patient database (e.g., the patient care manager) and can discuss the patient's needs with them in real time via a voice or video call made by the application framework. In some exemplary embodiments, the technician sends the new settings to the patient's IPG via the patient's own mobile device during the call session. In some exemplary embodiments, any setting except amplitude can be adjusted remotely. In some exemplary embodiments, the patient must increase the amplitude on their patient remote control, which minimizes the risk of unexpected irritation / discomfort.
[0120] In another aspect, the patient explicitly allows setting changes to be communicated to the stimulator via the Patient App user interface, or allows remote support to change the IPG in real time. In some exemplary embodiments, the patient uses their Patient Remote Control to increase the amplitude and describes any resulting changes in sensation or discomfort to the technician, who adjusts the settings in response. In some exemplary embodiments, the Patient Remote Control has access to the full amplitude range (just as when programming with the CP), and if the charger is used as a communication bridge from the IPG to the smartphone, communicates with the IPG while the charger is also connected. In some exemplary embodiments, after completing the programming activity, the technician or patient can disconnect the programming connection via the Patient App or the Remote Programming App.
[0121] D. Clinician Interface
[0122] In another aspect, the system utilizes a remote device, which can be a CP as well as a standard computing device (e.g., a smartphone, a tablet device, a laptop, a desktop). The standard computing device can be configured to facilitate remote programming by using a remote programming App. In some exemplary embodiments, the remote programming App can be a web application accessed using a standard browser. In some exemplary embodiments, doctors can access reports of remote programming activities to view logs / reports of their patients' remote programming sessions. In some exemplary embodiments, the patient App can only be installed on the patient's personal computing device and cannot be accessed through a browser.
[0123] E. Remote Programming System Example
[0124] By reference Figure 14-20 The above-described aspects of the remote reprogramming process may be further appreciated.
[0125] Fig.14A remote programming system 400 according to some exemplary embodiments is schematically illustrated. The remote programming system includes an IPG 401 that communicates with a remote support 430 through local intermediary devices 410, 420, which may include any of a patient remote control 411, a charger 412, a laptop computer 422, a smartphone 421, or a dedicated reprogramming device 423. Typically, the communication path requires the IPG to communicate with a first intermediary device 410, which communicates with a patient device 420, which in turn communicates with the remote support 430. In this embodiment, the first intermediary device may be a charger 411 or a patient remote control 412, and the patient device 420 may be a smartphone 421, a laptop computer 422, or a dedicated programmer device 423. Preferably, the communication system includes the IPG 401, the charger 411, the smartphone 421, and the remote support 430, which is advantageous because the charger is easy to charge, and the use of a smartphone provides greater versatility and mobility, and does not require additional dedicated equipment. It should be understood that the remote programming process may utilize any combination of the depicted devices and communication paths.
[0126] In one aspect, local communication between local devices can utilize shortwave radio communication, such as MedRadio or Bluetooth. In this embodiment, communication between IPG 401 and remote support 430 can be achieved through multiple alternative communication paths and different types of communication (as shown by dashed and solid lines). IPG 401 communicates via MedRadio, usually to meet regulatory requirements, making patient remote control 412 and charger 411 very suitable for use as intermediate devices because each device has been equipped to communicate with IPG via MedRadio. Each of the patient remote control and charger can also be configured to communicate via Bluetooth so that both can be used to facilitate interaction with the patient through patient device 420. In this method, the patient's personal computing device can be configured to be remotely programmed using a patient App, which is a dedicated executable application stored on the memory of the patient device. The patient App establishes a framework through which patients can enter subjective information about their treatment and interact with the remote support entity to facilitate reprogramming and securely send program information for remote programming purposes. In some exemplary embodiments, the system can utilize a dedicated device 422 developed specifically for reprogramming. Such a device may be configured to communicate with a first intermediate device via Bluetooth (as described above) or via MedRadio. In some exemplary embodiments, the dedicated device may be configured to communicate directly with the IPG via MedRadio, such that only a single intermediate local device is required. Remote support 430 communicates with the patient device via a network (e.g., via Wifi, cellular, a wired connection, or any combination thereof). Remote support 430 may be cloud-based or may utilize a first party server or a hosted server.
[0127] In some exemplary embodiments, the first intermediate device may be an existing charger or patient remote control, in which the software is updated to allow functionality as the first intermediate device. For example, the software is updated to enable the charger or patient remote control to act as an interpreter between the implanted medical device and another external device (e.g., a second intermediate device) that uses a different communication scheme. Specifically, the first intermediate device transmits any commands or requests received from the second intermediate device in one communication scheme (e.g., Bluetooth), converts these commands or requests into another communication scheme (e.g., MedRadio), and sends the converted commands or requests to the implantable device. In this way, the second intermediate device requests information from the implanted medical device, and the request is transmitted to the implanted medical device by the first intermediate device in an appropriate communication scheme. In response to receiving the request, the implanted medical device then outputs a communication of the requested information, which is received by the first intermediate device and transmitted to the second intermediate device according to an appropriate communication scheme. In this way, the first intermediate device merely relays any commands and requests received between the implanted medical device and the second intermediate device. In some exemplary embodiments, the first intermediate device does not substantially modify the content of the requests or commands, nor does it respond to the content of the requests or commands, or even respond to the device from which it receives the commands or requests.
[0128] In some exemplary embodiments, the implanted medical device stores any information related to the treatment (e.g., current programming parameters, alternative programs, electrode information, patient information, etc.). During the programming process, to the extent that the remote entity requests the information, the information is obtained from the memory of the implanted medical device. In some exemplary embodiments, although the information is usually stored on the implanted medical device and requested from the implanted medical device during reprogramming, some of the information can be obtained from a second intermediate device (e.g., a smartphone, a laptop) or a remote server that communicates with the remote support entity. In some exemplary embodiments, a request for information is received by a first intermediate device. In response to the request, the first intermediate device transmits the request on the implanted medical device in an appropriate communication scheme. In response to receiving the request, the implanted medical device accesses the requested stored information and then outputs the information to the second intermediate device via the first intermediate device, as described above. Therefore, in the described embodiments, the software configuration of the first intermediate device limits the role of the first intermediate device to transmit the request from one device to another device according to an appropriate communication scheme. In some exemplary embodiments, any command, request, or information transmitted between devices can be temporarily stored on the first intermediate device, limited to the extent required to relay the command, request, or information between devices. In some exemplary embodiments of the remote programming process, the implanted medical device is the single source of information regarding the current treatment program and parameters, which is advantageous because it avoids any potentially conflicting information regarding the current treatment being applied.
[0129] Figures 15A-15B Schematically illustrates a communication setup between a patient device and an implanted medical device for remote programming according to some exemplary embodiments, the communication setup utilizing a dedicated device as a first intermediate device. Fig.15A , the first intermediate device is a plug-in accessory 1510 that is plugged into the patient device 1520 such that it communicates directly with and is powered by the patient device 1520. The plug-in accessory 1510 includes a communication device that communicates wirelessly with the implanted medical device 1501, typically via MedRadio. This approach allows a smartphone that is not equipped with a MedRadio communication unit to be used as a patient device 1520 to communicate with the implanted medical device without the need for a charger or patient remote control. In some exemplary embodiments, the plug-in accessory 1510 may further include a memory having software thereon, which may include any additional features, such as authentication functionality to ensure secure communications with the IPG and / or remote support, or software related to the patient App and / or reprogramming process. Fig. 15BIn the embodiment, the first intermediate device can be configured as a separate dedicated communication device 1511 that communicates wirelessly and locally with the IPG and the patient device 1520. In this embodiment, the communicator communicates with the IPG via MedRadio and communicates with the patient device 1520 via Bluetooth or NFC. Similar to the plug-in accessory 1510 described above, the communication device 1511 may further include a memory with software related to the reprogramming process, which may include authentication functions or a patient app. In this embodiment, the intermediate device 1511 has its own power supply. The above method may be advantageous because the devices 1510, 1511 can be configured with additional functions and capabilities that may exceed the capabilities of the current charger or patient remote device described above.
[0130] Fig.16 Schematically illustrates a communication system setup 1600 between a patient device and a remote support entity according to some exemplary embodiments. In this embodiment, the patient device 1620 communicates remotely with a remote device / remote entity 1640 via Wifi, through a remote server 1630. In some exemplary embodiments, the communication can be through a cellular or wired connection, or any combination of Wifi, cellular and wired connections. In this embodiment, the remote server 1630 can be any of the following: a first-party server 1632, a cloud server 1631, or a hosted server 1633 of a developer of a neurostimulation system. The remote device / remote support entity 1640 can be a remote support team 1641, a call center 1642, or a consultant clinician 1643 of a first-party developer, which can include a contracted clinician or a treating physician. The remote entity utilizes a remote device to receive input from a physician regarding reprogramming and interact with the patient. The remote device can be any computing device, including a smartphone, a tablet device, a laptop, a clinician programmer, or a desktop computer. In this embodiment, the remote device may include a doctor app or a remote programming app framework that facilitates communication through the patient app of the local patient device 1620. In some exemplary embodiments, the doctor app can be configured to be provided to an Internet browser and accessed by the remote device. This allows greater versatility in the setup of the remote entity, so that the remote device can be any of a smartphone, a tablet device, a laptop computer, and a desktop computing device. Although the device application of the remote support entity is sometimes referred to as a "doctor app", it should be understood that the remote support does not need to be a doctor and can include clinicians, medical professionals, and technical experts or consultants with expertise in programming or programming troubleshooting. It should be understood that the remote programming process can utilize any combination of the described support entities and / or servers or communication paths.
[0131] Fig.17 A workflow 1700 is schematically illustrated, depicting various communication paths and options for a remote programming setup according to some exemplary embodiments. The setup indicates additional details regarding the functionality and steps of communications between devices and entities of the remote programming setup described herein. The schematic also illustrates which devices and functionality are associated with a first party developer of a neurostimulation system versus a third party developer (e.g., a smartphone / computer manufacturer, a consultant, a physician). It should be understood that the schematic represents a specific embodiment and that various alternatives or modifications are within the scope of the inventive concepts described herein. Additionally, Fig.17 Any of the various aspects and communications shown in can be used in various other embodiments, including in any alternative arrangements described herein.
[0132] Figure 18-20 An exemplary method of remotely programming an implanted medical device using a communication setup is shown in accordance with some exemplary embodiments.
[0133] Fig.18 A method of facilitating remote programming of an implanted neurostimulation system using one or more intermediate devices is depicted according to some exemplary embodiments. This method may include receiving, using a remote device, a request from a patient to remotely reprogram and / or reprogram an implanted pulse generator of a neurostimulation system implanted in a patient. Upon receiving the request, the system establishes a communication session between the implanted pulse generator of the neurostimulation system and a remote device associated with a remote support entity through one or more intermediate local devices for programming and / or reprogramming the implanted pulse generator by the remote entity. Program information is received using the remote device through the communication session, via the one or more local intermediate devices. The program information may include a current treatment program on the implanted neurostimulation system. In addition, the remote device receives patient information about the current treatment program via the one or more local intermediate devices associated with the patient. The remote device then receives a program update input by the remote support based on a current based on the treatment program information and the patient information, which updates one or more parameters of a current program or a new program for the implanted neurostimulation system. The system then programs the implanted pulse generator from the remote device through the one or more intermediate devices through a program update of one or more parameters of the current program or the new program.
[0134] Fig.19A method for remote programming using a patient device is depicted according to some exemplary embodiments. Such a method may include the following steps: establishing, using the patient device, a communication session between an implantable pulse generator of a neurostimulation system implanted in a patient and a remote device associated with a remote support entity through the patient device for programming and / or reprogramming the implantable pulse generator by the remote entity; sending, using the patient device, patient information to the remote device, wherein the patient information is associated with program information regarding a current treatment program applied by the implantable pulse generator of the implanted neurostimulation system. The patient device then receives a program update regarding an update of one or more parameters of the current program or a new program from the remote support device, and outputs the program update to the implanted neurostimulation system, thereby programming the implantable pulse generator from the remote device via the patient device using the program update of one or more parameters of the current program or the new program. In some exemplary embodiments, the patient device communicates with the implantable pulse generator through one or more intermediate devices, the one or more intermediate devices comprising any one of a patient remote control, a charger, a plug-in accessory, or a dedicated communication device.
[0135] Fig. 20 A method for remote programming using a remote device is depicted according to some exemplary embodiments. This method may include the following steps: establishing a communication session between an implantable pulse generator of a neurostimulation system implanted in a patient and a remote device associated with a remote support entity through one or more intermediate local devices for programming and / or reprogramming the implantable pulse generator by the remote entity; receiving program information from the intermediate local device via the one or more local intermediate devices using the remote device, wherein the program information includes a current treatment program on the implanted neurostimulation system; and receiving patient information about the current treatment program on the implanted neurostimulation system from the intermediate local device using the remote device via the one or more local intermediate devices. The remote device then determines an update to one or more parameters of a current program or a new program of the implanted neurostimulation system based on a current based on the treatment program information and the patient information, or receives through an update input. The remote device then programs the implantable pulse generator using the program update of one or more parameters of the current program or the new program using the remote device through one or more intermediate devices including the patient device.
[0136] FIG. 21 illustrates an exemplary setup that facilitates remote programming according to some exemplary embodiments. Setup 500 includes a conventional IPG 501 that communicates with a first intermediate device (a patient remote control 510), which in turn communicates with a second intermediate device (a patient device 520, such as a laptop or smartphone), which in turn communicates remotely with a remote programming device 530 (e.g., a computing device of a manufacturer / company representative or clinician). In this embodiment, the patient remote control 510 is specifically configured with a communication unit (e.g., Bluetooth) suitable for wireless communication with the patient device 520. This patient remote control is in contrast to a conventional patient remote control, which is only capable of communicating with an IPG (e.g., via MedRadio). In some exemplary embodiments, remote communication between the patient device 520 and the programming device 530 is conducted via a cellular network. In some exemplary embodiments, the patient device 520 includes a dedicated software application (e.g., IPG communication software) thereon to facilitate local communication with the IPG and remote communication with the programming device 530. The programming device 530 may include a corresponding application (e.g., IPG communication software) for a company representative or clinician to communicate with the IPG through the first intermediate device and the second intermediate device to facilitate remote programming by the representative or clinician through the user interface of the remote device. In some exemplary embodiments, the application software on the programming device 530 can be configured to allow adjustment of existing programs stored on the IPG, replacement of existing programs with alternative programs or newly determined programs, and downloading of IPG information (e.g., current or past programs, activities, etc.). In other embodiments, remote programming can be achieved through a web-based portal accessed by each of the patient device 520 and the remote device 530.
[0137] Figure 22-26 Various alternative setup options are shown to facilitate remote programming according to some exemplary embodiments. These settings can utilize existing communication capabilities of various devices, or include dedicated devices or software applications. In one aspect, these settings can utilize a patient database portal that utilizes communication with a secure server, particularly a web-based patient database portal (e.g., via Wi-Fi and / or cellular), and is designed to facilitate remote programming. The database portal can maintain various types of data related to patient treatment, such as 1) patient procedure history, 2) device event log, and 3) patient bladder diary. In some exemplary embodiments, these settings can be configured to allow patients to perform self-programming by utilizing information exchanged through the patient database portal (e.g., by receiving updated or modified programs from the portal based on information previously obtained from the patient).
[0138] Fig. 22A system setup 600 is shown that utilizes a dedicated patient remote control 610 to allow remote programming via the patient remote control, which allows for the use of different types of IPGs. For example, previous embodiments that rely on a charging device to communicate with the IPG are not suitable for use with an IPG having a non-rechargeable battery because a charging device is not used. The setup can utilize the functionality of existing patient programmers to communicate with the IPG, thereby being backward compatible. The setup further utilizes the functionality of existing smartphone / tablet devices with Bluetooth and Wifi communications because the patient remote control communicates with the patient device 620 via Bluetooth. The setup can further utilize a hosted patient bladder / urination diary application maintained by the patient using the patient device 620. Optionally, the setup can be provided only to those patients who need reprogramming. Advantageously, the impact of remote programming on the usable life of the patient remote control is negligible (e.g., 10 20-minute sessions use approximately 20% or less of the patient remote control battery energy).
[0139] In the system setting 600, the first intermediate device is a dedicated patient remote control 610 that is capable of a first type of communication (e.g., MedRadio) with an IPG 601 having a rechargeable battery or an IPG 602 having a non-rechargeable battery. The patient remote control 610 is specifically configured with a second type of communication (e.g., Bluetooth) for communicating with a second intermediate device (e.g., the patient's laptop, tablet device, smartphone) of a patient device 620, which in turn wirelessly communicates with a programming device 630 and / or a remote database portal 640 connected to a database 650 that contains various types of data related to the patient's treatment, such as 1) patient procedure history, 2) device event log, and 3) patient bladder diary. The communication between the patient device 620 and the remote programming device 630 can be a third type of communication (e.g., cellular, 4G, 5G, Wifi, or any combination thereof), and can further include a phone call, video call, or text type exchange between the clinician and the patient. Optionally, the patient device 620 can further communicate with a patient database portal 640, which can be accessed through a dedicated application on a smartphone, or alternatively, through a standard web browser on the patient device. The patient device 620 can exchange information (e.g., upload and download) from the patient database portal 640 as needed for reprogramming. In another aspect, the remote programming device 630 can directly exchange information with the patient database portal to notify remote programming. The remote programming device 630 can be a standard computing device (e.g., a commercial tablet device or a smartphone) with dedicated application software, or it can be a dedicated device. Similarly, the patient device 620 can be a standard computing device (e.g., a commercial tablet device or a smartphone) with dedicated application software, or it can be a dedicated device.
[0140] Fig.23A setup 700 is shown in which any of the IPGs 701, 702 can communicate locally with a patient device 720 via a first type of communication (e.g., Bluetooth). Similar to the previous setup, the patient device 720 can communicate remotely with a remote programming device 730 and / or a patient database portal 740 via a second type of communication (e.g., cellular, 4G, 5G, WiFi, or any combination thereof), wherein the patient database portal is connected to a database 750 containing various types of data related to the patient's treatment, such as 1) patient procedure history, 2) device event log, and 3) patient bladder diary. The setup can utilize dedicated application software on the patient device 720 and the remote programming device 730 to facilitate remote programming, and can utilize any of a phone call, video call, or text exchange. The setup can utilize existing smartphone / tablet device communication capabilities of Bluetooth and Wifi, and can include enabling Bluetooth functionality on the current patient remote device. In some exemplary embodiments, the patient device 720 hosts a bladder diary application and updates the patient database portal 740 with treatment information. In some exemplary embodiments, the setup is not backward compatible with conventional IPGs that do not have Bluetooth functionality. In some exemplary embodiments, the patient remote control 710 may communicate with the IPG via a first type of communication (eg, Bluetooth).
[0141] Fig.24 A setup 800 is shown having substantially the same or similar features and compatibility as those in setup 700, and includes an IPG 801, 802 that communicates locally with a patient device 820 via a first type of communication (e.g., Bluetooth). In this embodiment, since the IPG communicates directly with the patient device 820, the functionality of the patient remote control can be incorporated into the patient device 820, for example, through a dedicated software application (e.g., a patient remote control App), which can be configured to adjust stimulation or select between multiple stimulation programs. The application can be separate from a remote programming application (e.g., an IPG communication software) that allows communication between a remote programming device 830 and the IPG via the patient device 820. The setup can similarly include the features of Option 2A related to utilizing a phone / video call / texting, as well as a patient database portal 840 connected to a database 850, wherein the database 850 contains various types of data related to patient treatment, such as 1) patient procedure history, 2) device event log, and 3) patient bladder diary.
[0142] Fig.25A setup 900 is shown with a custom patient device 920 that is a combined patient remote device and intermediate device for remote programming. In some exemplary embodiments, the patient device 920 can be configured to communicate with the IPG 901, 902 via a first type of communication (e.g., MedRadio), and to communicate with a remote programming device 930 and / or a patient database portal 940 via a second type of communication (e.g., cellular, WiFi), wherein the database portal 940 is connected to a database 950 that contains various types of data related to the patient's treatment, such as 1) patient program history, 2) device event log, and 3) patient bladder diary. In some exemplary embodiments, the custom patient device 920 can be configured to communicate locally via MedRadio, and remotely via WiFi, cellular, or any combination thereof. In this embodiment, since the IPG can communicate directly with the patient device 920, the functionality of an existing patient remote control can be incorporated into the patient device 920, for example, via a dedicated application, for adjusting stimulation or selecting between multiple stimulation programs. Thus, this approach is backward compatible with existing IPGs that communicate with a dedicated patient remote control via a first type of communication (e.g., MedRadio). However, this arrangement does not require that the customized patient device 920 be configured to communicate via a first type of communication and a second type of communication in order to serve as an intermediary device for remote programming. Advantageously, since the need for a separate patient remote control has been eliminated, this approach can present fewer operating system maintenance issues and require fewer updates. In terms of patient devices that are reprogrammed using telephone / video / text communications, patient database portals, and act as an intermediary device for remote programming using a remote programming device 930, the arrangement otherwise includes features that are substantially the same or similar to the previous arrangement. In some exemplary embodiments, the arrangement allows the IPG to be self-programmed using a patient device 920 that uses a patient portal 940.
[0143] Fig.26 A setup 1000 is shown having a personal patient device 1020 (e.g., a standard smartphone / tablet device personal to the patient) with one or more dedicated software applications thereon, such that the device functions as a combined patient remote control and intermediary device for remote programming. In this example, the patient device 1020 is a personal device of the patient that is coupled to a communication adapter 1060 accessory (e.g., a plug-in or wireless accessory, see Figures 15A-15B) to facilitate communication via a first type of communication (e.g., MedRadio that is not native to the device), thereby allowing communication with the IPG 1001, 1002. The local communication of the patient device 1020 in the second type of communication (e.g., cellular, WiFi) can be used to communicate with the remote programming device 1030 and / or the patient database portal 1040, wherein the database portal 1040 is connected to a database 1050 that contains various types of data related to the patient's treatment, such as 1) patient procedure history, 2) device event log, and 3) patient bladder diary. In this embodiment, because the IPG can communicate directly with the patient device 1020, the functionality of the patient remote control can be incorporated into the patient device 1020, for example, through a dedicated application, for adjusting stimulation or selecting between multiple stimulation programs. Therefore, the method is backward compatible with existing systems that utilize an IPG, which communicates with a dedicated patient remote control via a first type of communication (e.g., MedRadio). This arrangement is advantageous because it further eliminates the need for custom-built dedicated intermediary devices and allows both patient remote functionality and remote programming to be accomplished using the patient's own personal device (e.g., a smartphone / tablet device). The arrangement otherwise includes substantially the same or similar features as in the previous arrangement in terms of the ability for phone / video / text communication for reprogramming, a patient database portal, and a patient device that functions as an intermediary device for remote programming by a remote programming device 1030 or as a self-programming device utilizing a patient portal 1040. In some exemplary embodiments, the arrangement allows self-programming of the IPG utilizing a patient device 1020 utilizing a patient portal 1040.
[0144] Figure 22-26Various aspects / features associated with each of the above options are described. These aspects emphasize how each of the proposed settings can be integrated with existing systems and devices to take advantage of existing functionality, as well as the implications and advantages associated with modified, customized or new devices. For example, the option of utilizing an existing IPG can be implemented in a current patient who has already implanted an existing (not BT-supported) IPG, while other setting options can be implemented in an updated neurostimulation system to be implanted in a new patient. It should be understood that these features are exemplary and that changes can be implemented for each option in the options or other options not shown. For example, a setting utilizing direct communication between a patient device and an IPG can additionally include a patient remote control in a redundant manner to provide the patient with additional options and greater flexibility per user preference. It is noted that the various features are performed by a device provider "provider" (e.g., Axonics), but it is understood that the term can alternatively refer to any customer service, clinical care team representative. It should be understood that each of the listed features can be utilized in different setting options in any suitable compatible manner.
[0145] Fig. 27 An exemplary programming method is described, comprising the steps of establishing a remote programming communication session between an IPG of a neurostimulation system implanted in a patient and a remote device associated with a remote support entity through one or more intermediary devices local to the patient, and receiving program information with the remote device via the one or more local intermediary devices, the program information including a current treatment program. Next, the method may include the steps of establishing communication between the remote device and a web-based patient database portal previously updated with treatment information received from the one or more intermediary devices, and receiving treatment information from the patient database portal with the remote device; and determining or receiving an updated program update with the remote device based on the program information and the treatment information regarding one or more parameters of a current program or a new program to be applied by the implanted neurostimulation system. Finally, the method entails programming the IPG with the remote device through the one or more intermediary devices using the updated or new program.
[0146] Fig.28Another exemplary method for remote programming using one or more intermediate devices is depicted. The method may include the steps of: establishing a remote programming communication session between an IPG of a neurostimulation system implanted in a patient and a remote device associated with a remote support entity through one or more intermediate local devices; and receiving current program information from the IPG using the remote device. Optionally, the method may include: establishing communication between a patient database portal previously updated with treatment information via the one or more local intermediate devices, and receiving the treatment information using the remote device. In some exemplary embodiments, the one or more local intermediate devices include any of the following: (i) a patient remote control with MedRadio (MR) and Bluetooth (BT) communications, and a patient smartphone / tablet device with Bluetooth and cellular and / or Wifi communications; (ii) a patient smartphone or tablet device with BT communications for use with a BT-enabled IPG (and optionally a BT-enabled patient remote control); (iii) a customized patient device configured with MR communications for the IPG and BT for communicating with a remote device / patient portal; and (iv) a standard smartphone / tablet device with a dedicated application providing patient remote control and remote programming capabilities, a built-in communication unit (WiFi / cellular), and an adapter accessory for providing MR for communication with the IPG. The method then requires determining or receiving, using the remote device, an updated program update of one or more parameters of a current program or a new program to be applied by the implanted neurostimulation system based on the program information and the treatment information; and programming the IPG using the remote device with the updated or new program through the one or more intermediate devices.
[0147] In the above description, various embodiments are described, but those of ordinary skill in the art will recognize that the present invention is not limited thereto. Various disclosed features, embodiments and aspects may be used individually or in combination. In addition, without departing from the broader spirit and scope of protection of this specification, the described embodiments may be used for any number of environments and applications beyond those described herein. Therefore, the description and the accompanying drawings should be regarded as illustrative, not restrictive. It should be recognized that the terms "including", "comprising" and "having" as used herein are specifically understood as open technical terms. Any reference to a publication, patent or patent application is incorporated herein by reference in its entirety for all purposes.
Claims
1. A method for remotely programming an implanted neural stimulation system, the method comprising: include: establishing, through one or more intermediate local devices of the patient, a communication session between an implantable pulse generator of a neural stimulation system implanted in the patient and a remote programming device associated with a remote support entity, the implantable pulse generator being configured to provide electrical stimulation pulses to the patient; receiving, with the remote device, program information via the one or more local intermediate devices, wherein the program information includes a current therapy program associated with the electrical stimulation pulses applied to the patient by the implanted neural stimulation system, wherein the one or more local intermediate devices include a patient device having a user interface thereon; receiving, using the remote device, treatment information from a web-based portal, wherein the treatment information was previously received remotely by the web-based portal from the one or more local intermediary devices; and Determining or receiving a program update regarding an update to one or more parameters of the electrical stimulation pulses associated with the current treatment program using the remote device, wherein the update is applied to the neurostimulation system based on the program information and treatment information, thereby changing the one or more parameters of the electrical stimulation pulses associated with the current treatment program provided to the patient.
2. The method according to claim 1, in, The treatment information is stored on a patient database and includes any of: a patient procedure history, a device event log of the implantable pulse generator, and a patient bladder diary.
3. The method according to claim 1, in, The treatment information is received by the web-based portal from the patient device and periodically updated remotely using the patient device.
4. The method according to claim 1, in, The one or more intermediate devices include a first intermediate device and a second intermediate device, wherein the first intermediate device includes a patient remote control that communicates with the implantable pulse generator for the patient to adjust the stimulation level, and the second intermediate device is the patient device, wherein the patient device includes a tablet device or a smartphone of the patient configured to communicate with the patient remote control and each of the remote devices of the remote support entity.
5. The method according to claim 4, in, The patient remote control is configured to communicate with the implantable pulse generator via a first type of communication and to communicate with the second intermediate device via a second type of communication.
6. The method according to claim 5, in, The first type of communication is MedRadio, and the second type of communication is Bluetooth.
7. The method according to claim 4, in, The second intermediate device is configured to communicate with the remote device and the web-based portal via remote-type communications.
8. The method according to claim 7, in, The long-range type of communication is any one of cellular and WiFi or any combination thereof.
9. The method according to claim 8, in, The remote device is farther away from the pulse generator than the first intermediate device and the second intermediate device.
10. The method according to claim 1, in, The patient device is configured to communicate locally with the implantable pulse generator and remotely with the remote device of the remote support entity and / or the patient portal database.
11. The method according to claim 10, in, The implantable pulse generator is Bluetooth enabled, and the patient device is a smartphone or tablet device that communicates locally with the implantable pulse generator via Bluetooth.
12. The method according to claim 10, further comprising: include: One or more parameters of the current therapy are adjusted using a patient remote control configured to communicate with the implantable pulse generator via Bluetooth.
13. The method according to claim 11, in, The smartphone or tablet device includes a dedicated software application thereon which, in addition to operating as the intermediate device for remote programming, provides the patient device with functionality to operate as a patient remote control to adjust therapeutic stimulation.
14. The method according to claim 1, in, The patient device is a customized device that communicates locally and directly with the implantable pulse generator via a first type of communication and remotely with the remote device and / or web-based portal via a second type of communication.
15. The method according to claim 14, in, The first type of communication is MedRadio, and the second type of communication is cellular, Wifi, or a combination thereof.
16. The method according to claim 1, in, The patient device is communicatively coupled to an adapter accessory that provides a first type of communication for communicating with the implantable pulse generator, wherein the patient device has built-in communications for a second type of communication.
17. The method according to claim 16, in, The first type of communication is MedRadio and the second type of communication is cellular, Wifi, or a combination thereof.
18. The method according to claim 16, in, The patient device comprises the patient's standard smartphone or watch with dedicated software stored thereon, which operates both as a patient remote control for adjusting stimulation and as the intermediate device for remote programming.
19. The method according to claim 18, in, The adapter accessory is electrically connected to the patient device or wirelessly connected to the patient device via Bluetooth.
20. The method according to claim 1, further comprising: include: The patient device is self-programmed by utilizing the patient device to determine or receive from the web-based portal a program update regarding an update to one or more parameters of the current program to be applied by the implanted neurostimulation system based on the program information and treatment information received by the web-based portal.
21. A remote programming system for remotely programming an implanted neural stimulation system using a remote support entity, the system include: an implantable pulse generator of the neural stimulation system implanted in a patient, the implantable pulse generator having one or more antennas for wireless communication with one or more external devices; wherein the one or more external devices include one or more intermediate devices configured to communicate with the implantable pulse generator via local communication and further communicate via remote communication; a remote programming device associated with the remote support entity, the remote device configured to communicate with the one or more intermediate devices via the remote communication, wherein the remote device includes a user interface for receiving input from the remote support entity; and A patient database portal, the patient database portal being a web-based portal having thereon treatment information updated by the one or more intermediary devices, wherein the patient database portal is accessible by the remote programmer device and the one or more intermediary devices.
22. The system according to claim 21, in, The one or more intermediate devices include any of the following: a patient remote control, a patient device, and an adapter accessory.
23. The system according to claim 21, in, The one or more intermediate devices include a patient remote control configured to communicate locally via both MedRadio and Bluetooth, and a patient device that communicates locally via Bluetooth and remotely via cellular and / or WiFi.
24. The system according to claim 21, in, The implantable pulse generator is Bluetooth enabled, and the one or more intermediate devices include a patient device that communicates locally and directly with the implantable pulse generator via Bluetooth and remotely with the remote programming device via cellular, Wifi, or a combination thereof.
25. The system according to claim 24, in, The patient device is a standard smartphone or tablet device having a dedicated software application operable thereon to facilitate remote programming.
26. The system according to claim 25, further comprising: include: A patient remote control for adjusting stimulation therapy, the patient remote control communicating with the implantable pulse generator via Bluetooth.
27. The system according to claim 25, in, The dedicated software is also configured to cause the patient device to communicate with the implantable pulse generator via Bluetooth and operate as a patient remote control for adjusting stimulation therapy.
28. The system according to claim 21, in, The one or more intermediate devices include a customized patient device configured to communicate with the implantable pulse generator via Bluetooth and with the remote programming device via cellular, WiFi, or a combination thereof.
29. The system according to claim 21, in, The one or more intermediate devices include a patient device having a dedicated software application operable thereon to facilitate remote programming and an adapter accessory communicatively coupled to the patient device to facilitate local communication with the implantable pulse generator.
30. The system according to claim 29, in, The patient device comprises a standard smartphone or tablet device with built-in communications for cellular and / or WiFi, the patient device communicates with the remote programming device via cellular and / or WiFi, and wherein the accessory device is configured to communicate with the implantable pulse generator via MedRadio.
31. The system according to claim 29, in, The accessory is a plug-in device that connects to the patient device either electrically or wirelessly via Bluetooth.
32. The system according to claim 21, in, The one or more intermediate devices include a patient device having a user interface thereon and a dedicated software application configured for self-programming the implantable pulse generator using the patient device by determining or receiving program updates regarding one or more parameters of the current program to be applied by the implanted neural stimulation system based on updates received from the patient database portal, wherein the updates are based on the program information and treatment information received by the patient database portal.
33. A remote programming system for remotely programming an implanted neural stimulation system using a remote support entity, the system include: an implantable pulse generator of the neural stimulation system implanted in a patient, wherein the implantable pulse generator is configured to apply a therapeutic program associated with electrical stimulation pulses provided to the patient, and wherein the implantable pulse generator has one or more antennas for wireless communication with one or more external devices; wherein the one or more external devices include one or more intermediate devices configured to communicate with the implantable pulse generator via local communication, and wherein the one or more intermediate devices are configured to further communicate via remote communication; a remote programming device associated with the remote support entity, the remote device configured to communicate with the one or more intermediate devices via the remote communication, wherein the remote device includes a user interface for receiving input from the remote support entity; and Wherein, the remote programming device is configured to update the treatment program by modifying one or more parameters of the electrical stimulation pulses via the one or more intermediate devices.
34. The system according to claim 33, in, The one or more intermediate devices include any of the following: a patient remote control, a patient device, and an adapter accessory.
35. The system according to claim 33, in, The one or more intermediate devices include a patient remote control configured to communicate locally via both MedRadio and Bluetooth, and a patient device that communicates locally via Bluetooth and remotely via cellular and / or WiFi.
36. The system according to claim 33, in, The implantable pulse generator is Bluetooth enabled, and the one or more intermediate devices include a patient device that communicates locally and directly with the implantable pulse generator via Bluetooth and remotely with the remote programming device via cellular, Wifi, or a combination thereof.
37. The system according to claim 33, further comprising: include: A patient remote control for adjusting stimulation therapy, the patient remote control communicating with the implantable pulse generator via Bluetooth.
38. The system according to claim 33, in, The one or more intermediate devices include a customized patient device configured to communicate with the implantable pulse generator via Bluetooth and with the remote programming device via cellular, WiFi, or a combination thereof.
39. The system according to claim 33, in, The one or more intermediate devices include a patient device having a dedicated software application operable thereon to facilitate remote programming and an adapter accessory communicatively coupled to the patient device to facilitate local communication with the implantable pulse generator.
