Abstract: This application is generally related to identifying or otherwise programming one or more cycling parameters for operation of an implantable pulse generator to provide a neurostimulation therapy to a patient using a non-paresthesia stimulation pattern. In some embodiments, the cycling parameter is selected by measuring physiological signals during trial stimulation. In other embodiments, multiple cycling parameters are identified for use by the patient using a patient controller device.

Abstract: In one embodiment, a method for operating a system for management of implantable medical devices (IMDs), comprises: conducting communications sessions with a plurality of clinician programmer devices, wherein some of the communication sessions occur while the plurality of clinician programmer devices are engaged in respective programming sessions with IMDs; conducting communications sessions with a plurality of patient controller devices, wherein the communication sessions with the patient controller devices include communication of data pertaining to offline programming of IMDs; reconciling programming session data received from the plurality of clinician programmer devices with programming session data received from patient controller devices to identify instances of unauthorized IMD programming; and distributing revocation data to patient controller devices to be downloaded to corresponding IMDs, wherein the revocation data identifies cryptographic keys that are no longer trusted.

Abstract: This application is generally related to systems and methods for providing a medical therapy to a patient by tracking patient activity and adjusting medical therapy based on occurrence of different types of activities performed by the patient while automatically rescheduling stimulation programs based on detected patient activity.

Abstract: This application is generally related to systems and methods for providing a medical therapy to a patient by tracking patient activity and adjusting medical therapy based on occurrence of different types of activities performed by the patient including user indicated activities inputted from an icon driven user interface of an external patient controller device.

Abstract: This application is generally related to systems and methods for providing a medical therapy to a patient by tracking patient activity and adjusting medical therapy based on occurrence of different types of activities performed by the patient while automatically rescheduling stimulation programs based on detected patient activity.

Abstract: This application is generally related to systems and methods for providing a medical therapy to a patient by tracking patient activity and adjusting medical therapy based on occurrence of different types of activities performed by the patient including user indicated activities inputted from an icon driven user interface of an external patient controller device.

Abstract: This application is generally related to systems and methods for providing a medical therapy to a patient by tracking patient activity and adjusting medical therapy based on occurrence of different types of activities performed by the patient while automatically balancing stimulation program duration.

Abstract: This application is generally related to systems and methods for providing a medical therapy to a patient by tracking patient activity and adjusting medical therapy based on occurrence of different types of activities performed by the patient while automatically balancing stimulation program duration.

Abstract: This application is generally related to systems and methods for providing a medical therapy to a patient by tracking patient activity and adjusting medical therapy based on occurrence of different types of activities performed by the patient while automatically balancing stimulation program duration.

Abstract: This application is generally related to systems and methods for providing a medical therapy to a patient by tracking patient activity and adjusting medical therapy based on occurrence of different types of activities performed by the patient according to clinician defined stimulation program scheduling rules.

Abstract: This application is generally related to systems and methods for providing a medical therapy to a patient by tracking patient activity and adjusting medical therapy based on occurrence of different types of activities performed by the patient including user indicated activities inputted from an icon driven user interface of an external patient controller device.

Abstract: This application is generally related to systems and methods for providing a medical therapy to a patient by tracking patient activity and adjusting medical therapy based on occurrence of different types of activities performed by the patient while automatically rescheduling stimulation programs based on detected patient activity.

Abstract: In one embodiment, an implantable medical device (IMD) comprises: therapeutic circuitry for controlling delivery of a medical therapy to a patient; a processor for controlling the IMD according to executable code; wireless communication circuitry for conducting wireless communications; and memory for storing data and executable code, wherein the executable comprises code for causing the processor to (1) communicate with an external programming device to define therapeutic settings for operation of the IMD, (2) perform validation operations on one or more instances of therapeutic settings by determining whether a respective instance of therapeutic settings is accompanied by permanent validation data or temporary validation data, wherein the validation operations comprise analyzing temporary validation data against at least one key of a plurality of cryptographic keys stored by the IMD.

Abstract: In one embodiment, a method of programming an implantable medical device (IMD) to provide therapeutic operations for a patient, comprises: conducting a first communication session between the IMD with an external programming device when network connectivity for a remote server for medical device management is not available for the external programming device; receiving programming data by the IMD from the external programming device to provide therapeutic operations according to at least one instance of settings data during the first communication session, wherein the at least one instance of settings data is validated by a temporary key; conducting a second communication session between the IMD with an external device when network connectivity to the remote server for medical device management is available for the external device; and replacing validation data signed using the temporary key with the received validation data.

Abstract: In one embodiment, a method of programming an implantable medical device (IMD) to provide therapeutic operations for a patient, comprises: receiving first programming data by the IMD from the external programming device to provide therapeutic operations according to at least one instance of settings data during a first communication session; receiving second programming data by the IMD from the external programming device to define limitations of reprogramming during one or more subsequent offline programming sessions; conducting a second communication session between the IMD with an external programming device when network connectivity is not available; receiving third programming data by IMD from the external programming device to provide therapeutic operations according to at least one instance of settings data during the second communication session; and determining whether the third programming data is permitted according to limitations defined by the second programming data.

Abstract: In one embodiment, a method for operating a system for management of implantable medical devices (IMDs), comprises conducting communication sessions with a plurality of clinician programmer devices while the clinician programmer devices are engaged in respective programming sessions with IMDs; receiving and storing second programming data from a plurality of clinician programmer devices, wherein the second programming data was created during programming sessions with IMDs without network connectivity to the system for management of IMDs; reconciling programming of the plurality of IMDs that were programmed with the second programming data with data stored by the system for management of IMDs; and communicating second signed validation data to cause IMDs to conduct therapeutic operations according to programming data validated by respective instances of second validation data.

Abstract: In one embodiment, an implantable medical device (IMD) comprises: therapeutic circuitry for controlling delivery of a medical therapy to a patient; a processor for controlling the IMD according to executable code; wireless communication circuitry for conducting wireless communications; and memory for storing data and executable code, wherein the executable comprises code for causing the processor to (1) communicate with an external programming device to define therapeutic settings for operation of the IMD, (2) perform validation operations on one or more instances of therapeutic settings by determining whether a respective instance of therapeutic settings is accompanied by permanent validation data or temporary validation data, wherein the validation operations comprise analyzing temporary validation data against at least one key of a plurality of cryptographic keys stored by the IMD.

Abstract: In one embodiment, a method for operating a system for management of implantable medical devices (IMDs), comprises: conducting communication sessions with a plurality of clinician programmer devices while the clinician programmer devices are engaged in respective programming sessions with IMDs; receiving and storing second programming data from a plurality of clinician programmer devices, wherein the second programming data was created during programming sessions with IMDs without network connectivity to the system for management of IMDs; reconciling programming of the plurality of IMDs that were programmed with the second programming data with data stored by the system for management of IMDs; and communicating second signed validation data to cause IMDs to conduct therapeutic operations according to programming data validated by respective instances of second validation data.

Abstract: In one embodiment, a method for operating a system for management of implantable medical devices (IMDs), comprises: conducting communications sessions with a plurality of clinician programmer devices, wherein some of the communication sessions occur white the plurality of clinician programmer devices are engaged in respective programming sessions with IMDs; conducting communications sessions with a plurality of patient controller devices, wherein the communication sessions with the patient controller devices include communication of data pertaining to offline programming of IMDs; reconciling programming session data received from the plurality of clinician programmer devices with programming session data received from patient controller devices to identify instances of unauthorized IMD programming; and distributing revocation data to patient controller devices to be downloaded to corresponding IMDs, wherein the revocation data identifies cryptographic keys that are no longer trusted.

Abstract: In one embodiment, a method for operating a system for management of implantable medical devices (IMDs), comprises: conducting communications sessions with a plurality of clinician programmer devices, wherein some of the communication sessions occur while the plurality of clinician programmer devices are engaged in respective programming sessions with IMDs; conducting communications sessions with a plurality of patient controller devices, wherein the communication sessions with the patient controller devices include communication of data pertaining to offline programming of IMDs; reconciling programming session data received from the plurality of clinician programmer devices with programming session data received from patient controller devices to identify instances of unauthorized IMD programming; and distributing revocation data to patient controller devices to be downloaded to corresponding IMDs, wherein the revocation data identifies cryptographic keys that are no longer trusted.