A useful comparison of deep brain stimulation programmer software begins by separating the workstation hardware from its programming application and planning module. The programmer is the interface clinicians use to set and adjust stimulation parameters for a compatible implanted pulse generator, but it may also incorporate optional image-guided planning tools that visualize estimated stimulation fields [2][1]. Procurement teams should therefore document three distinct questions for every candidate: which implantable systems the software can connect to, which stimulation parameters and contact configurations it can actually program, and what evidence supports any claimed reduction in session time. A direct answer is that no single programmer is inherently preferable across all sites; the appropriate choice depends on the existing implant fleet, the patient population and whether the clinic will license separate planning software for specific manufacturers.

Start with compatibility, because a programmer is useless outside its approved system

The Boston Scientific Vercise Neural Navigator 5 software is intended to set and adjust stimulation parameters for the Boston Scientific Stimulator, and the programming manual states that it is used to program the Vercise PC, Vercise Gevia and Vercise Genus DBS systems [2][7]. The setup reference table distinguishes multiple workflows: Vercise Genus implantable pulse generators and the external trial stimulator ETS 3 require placing the device into clinician programmer pairing mode, while Vercise Gevia, Vercise PC and ETS 2 require connecting a programming wand [2]. Importing the wrong pairing sequence into a cross-vendor evaluation can make a capable tool appear unusable, so procurement should request the exact generator models the clinic currently supports.

Medtronic's programming architecture is documented differently. An FDA summary describes a Model A610 Clinician Programmer Application, with adaptive deep brain stimulation added in software version 5.0 for the Percept system, and a separate Model A620 patient programmer application that can pause adaptive therapy [3]. A third-party planning product illustrates a narrower scope: Bullsai Confirm received 510(k) clearance to assist medical professionals in planning stimulation for patients receiving approved Abbott DBS devices only, with SureTune4 as the predicate for Medtronic devices [6]. Compatibility is therefore verified per device family, not per hospital or vendor relationship.

Compare programmable parameter ranges before comparing interface polish

Once compatibility is established, the comparison should move to numeric limits. Boston Scientific's programming manual lists a current-regulated, charge balanced, asymmetric biphasic rectangular waveform with amplitude from 0 mA to 20 mA, rate from 2 Hz to 255 Hz, pulse width from 20 μs to 450 μs, cycle timing from 1 second to 90 minutes, ramp from 1 second to 10 seconds, and up to 32 contact connections [2]. Each individual contact is limited to 12.7 mA, and the software accommodates up to 16 independent areas of stimulation across four programs with four areas per program [7]. These ceilings determine whether a patient with complex directional configurations can be managed within one session.

Boston Scientific also describes unique current path options, including semi-bipolar stimulation with the anode divided between the implantable pulse generator and the lead, and anodic stimulation [1]. The company attributes increased side effect threshold and improved efficacy to these capabilities, citing specific published studies, but states that results from different clinical investigations are not directly comparable [1]. For procurement, the practical question is whether the installed lead design can deliver those modes; a programmer cannot create anodic or semi-bipolar pathways that the implanted generator and lead do not support. The parameter table should be reviewed alongside the pulse generator purchase, not as an isolated software decision.

A minimum data request for each DBS programmer

Request the programming manual's parameter range table, the current instructions for use, the FDA clearance or approval summary that names the compatible implant systems, and the full citation for any time-reduction percentage the vendor presents. Confirm the exact generator model pairing steps for both rechargeable and non-rechargeable devices, because Boston Scientific's own setup table requires different procedures for Vercise Genus and ETS 3 versus Gevia, PC and ETS 2 [2]. Ask for the output format produced at the end of a session, such as a PDF report or PNG screenshot, and note whether the planning software can superimpose an anatomical atlas, since at least one cleared Abbott planning tool explicitly does not [6].

For image-guided claims, capture the study size, population, comparator and endpoint. Boston Scientific's 56 percent time reduction is associated with a 10-patient study, while the 84 percent clinical improvement figure is associated with 31 patients, so both numbers cannot be treated as one interchangeable dataset [5][4]. Finally, confirm which stimulation modes the implanted lead and generator can deliver, not merely which ones the software screen can display. A programmer demonstration that shows anodic stimulation is irrelevant if the site's lead does not support that current path.

Evaluate image-guided programming evidence with denominators and endpoints

Vendor materials for Boston Scientific state that image-guided programming in Parkinson's patients enables a 56 percent reduction in programming time compared with standard clinical-based programming, with an average programming time of 20 minutes [1][4]. The underlying reference is a 2021 study of 10 patients, and the Boston Scientific page also cites a 2024 publication reporting that 84 percent of 31 patients experienced lasting motor and quality of life improvements after reprogramming using image-guided programming [5][4]. Those denominators matter: a procurement committee comparing a 10-patient time study with a 31-patient outcome study is comparing different questions, even though both appear under the same therapy label.

The same Boston Scientific materials report that 88 percent of 18 patients selected the program generated by Illumina 3D programming compared with conventional programming, and that average stimulation field model overlap between initial programming and one-year follow-up was 92 percent in 18 patients [4]. These figures are attributable to named vendor communications and specific studies; they do not establish equivalent performance for another manufacturer's planning software. Procurement should request the full citation, sample size, endpoint definition and comparator method for any percentage presented during a demonstration, because marketing summaries routinely collapse distinct clinical investigations into a single efficiency claim.

A comparable planning tool for Abbott devices, Bullsai Confirm, received FDA clearance based on substantial equivalence to SureTune4, a Medtronic planning predicate [6]. The 510(k) summary states that Bullsai Confirm does not superimpose an anatomical atlas or manually segment structures of interest [6]. This is an explicit functional limitation relative to tools that advertise atlas-based or manual segmentation workflows. When a vendor omits a feature from its own submitted labeling, that omission is more reliable than a sales slide; procurement should compare the portions of each product's clearance summary that describe what the software does not do, not only what it does.

Treat interoperability claims as workflow claims, not buyer advantages

Boston Scientific describes the Vercise Genus DBS System as the first electronic medical record-connected DBS system, with communication from the clinician programmer to Epic, and positions streamlined note-taking alongside Illumina 3D [8]. For a procurement team, the relevant questions are which Epic modules the connection supports, what data elements transfer and whether the export is one-way or bidirectional. The vendor material does not establish that this integration reduces documentation time or improves billing accuracy; it establishes only that the vendor describes an EMR connection. A site that uses a non-Epic platform may receive no benefit from a feature that appears prominently in comparison tables.

Bullsai Confirm's 510(k) summary describes a more limited reporting scope: the software exports reports that summarize stimulation plans as PNG screenshots and shares results in an output PDF report visualized in a web-based interface [6]. That output format may be sufficient for a clinic that archives programming snapshots, but it is not a substitute for structured data exchange with an EMR. Procurement should map each candidate's output to the actual destination the clinic uses: if reports must be manually attached, transcription or scanning is still required. Interoperability should be scored as a discrete workflow with documented inputs, outputs and recipient systems, not as a general modernization theme.

A suggested evaluation workflow for your site

A procurement team can structure a defensible comparison without commissioning clinical trials. Begin with a fixed implant scenario: a subthalamic nucleus lead for Parkinson's disease, a specified generator model, and a recent postoperative imaging dataset. Ask each vendor to demonstrate the complete session from connection to report export using that same scenario. Record three measurements: time from software launch to first stimulation setting, number of manual steps to create a bipolar directional program if the lead supports it, and the exported file type and contents. This is a suggestion for an evaluation protocol, not a test that has been validated against patient outcomes.

Then separate the decision into a compatibility gate and an efficiency comparison. If a programmer cannot pair with the installed generator models, it fails the gate regardless of interface quality. If it passes, compare only the measurable elements: parameter ceilings from the programming manual, image-guided planning evidence with sample sizes, and the specific workflow steps each tool automates. The Boston Scientific manual's parameter table and the Bullsai Confirm clearance summary are examples of primary documents that answer these questions without relying on promotional language [2][6]. Documenting each product's own limitations is where a procurement file gains enough detail to survive an audit or a changed implant contract.