You have a patient. Tremor-dominant Parkinson's, late 60s, bilateral STN implant, three years post-surgery. Standard settings are holding, but tremor control is suboptimal. You've adjusted frequency across the 60–185 Hz range. You've walked pulse width from 60 to 120 microseconds. You've titrated amplitude carefully. You've seen maybe eight patients with this exact profile in your career.
Somewhere in Germany, a movement disorder center has seen twenty-two.
In Tokyo, a team developed a parameter sequence last year — a specific combination of contact configuration, stimulation cycling, and LFP-triggered adjustment — that works precisely for this profile. Their outcomes data is real. It's structured. It's sitting in a Medtronic Percept PC dashboard.
None of it reaches you. Not one byte.
This is the DBS programming intelligence problem, and it is entirely architectural.
The Scale of the Isolation
Approximately 160,000 to 200,000 patients worldwide have received deep brain stimulation implants. Roughly 10,000 new DBS implantations occur in the United States each year. More than 300 specialized DBS programming centers operate globally — each one accumulating empirical knowledge about stimulation parameter optimization for the patients they happen to see.
DBS programming is inherently iterative. After implant, each patient requires individualized optimization across a multidimensional parameter space: stimulation frequency (typically 60–185 Hz), pulse width (60–120 μs), amplitude (1–5 V), contact configuration, and increasingly, adaptive stimulation thresholds triggered by local field potential biomarkers. The combinatorial search space is large. Ramirez-Zamora et al. (2017) documented the complexity of this empirical process and called explicitly for systematic approaches to knowledge sharing across centers — a call that remains substantially unanswered nearly a decade later.
The synthesis opportunity is concrete. 300 centers × 299 ÷ 2 = 44,850 unique center-to-center knowledge paths.
Currently active: zero.
The Data Already Exists
This is what makes the problem almost unbearable once you see it clearly.
Modern sensing-enabled DBS platforms — Medtronic's Percept PC, Abbott's Infinity aDBS system — capture local field potentials in real time. These devices generate structured outcome data at the hardware level. LFP power spectra. Beta-band suppression in response to parameter changes. Stimulation-linked symptom biomarkers. The data architecture that would be required to enable intelligent knowledge routing already exists, implanted in the patient's skull.
It sits in proprietary device dashboards. It does not route.
Benabid and colleagues' original 1993 demonstration of STN stimulation for Parkinson's opened a surgical frontier that has expanded dramatically. Anderson et al. documented UPDRS-III motor score improvements of 40–60% with optimized STN-DBS. The clinical evidence base for DBS efficacy is substantial. What has not scaled is the knowledge infrastructure that would allow the hard-won parameter expertise of one center to benefit the patients of another.
The patient at your center with suboptimal tremor control is not suffering from a lack of technology. She is suffering from a lack of routing.
Why Federated Learning Cannot Solve This
The federated learning proposal is intuitive: keep data local, share model gradients, aggregate intelligence without centralizing patient records. For large, homogeneous datasets, it works.
DBS programming breaks federated learning's core assumption.
A center that performs 40 DBS programming sessions per year — not uncommon for a busy movement disorder practice — sees those sessions distributed across heterogeneous patient profiles: STN vs. GPi targets, tremor-dominant vs. akinetic-rigid phenotypes, early vs. advanced disease, varying surgical outcomes, different device platforms. When you isolate the relevant subtype — bilateral STN, tremor-dominant, late 60s, three or more years post-implant, showing plateau — a center might accumulate meaningful data on that profile across three to five years. That is not enough local data to compute gradients that meaningfully update a shared model. The N per relevant subtype is structurally too small.
Federated learning requires statistical mass at the node. DBS programming expertise is granular, longitudinal, and profile-specific. The architecture does not fit.
The QIS Protocol Architecture
QIS protocol — Quadratic Intelligence Swarm — takes a different approach. It does not require large local datasets. It does not require a central database. It does not require patient data to leave any institution.
The unit of exchange is the outcome packet.
Each DBS programming session generates an outcome packet of approximately 512 bytes. That packet contains:
- Patient profile: age range (not exact DOB), disease duration bracket, symptom subtype classification, genetic markers if available (e.g., LRRK2, GBA status)
- Anatomical target: STN vs. GPi, laterality, approximate lead position relative to target
- Parameters trialed: frequency, pulse width, amplitude, contact configuration, adaptive threshold settings if applicable
- Outcome metrics: UPDRS-III tremor subscores, patient diary data (tremor diary, dyskinesia log), LFP biomarker response to parameter changes
What the packet does NOT contain: patient name, date of birth, exact geographic location, medical record number, full clinical history.
Raw patient data — the information that constitutes protected health information under HIPAA — never leaves the institution. Only the distilled outcome packet routes. This is structurally compatible with privacy regulation, not by exception or legal workaround, but by architecture. There is nothing to protect in transit because there is nothing identifying in transit.
The packet is posted to a semantic address determined by a similarity function — a definition of "this patient profile" — specified by a movement disorder expert. Every center running QIS protocol with similar patient definitions pulls relevant packets. Local synthesis runs on the clinical workstation. The programming neurologist sees aggregated parameter outcomes across all centers whose patients matched their query profile.
What the Routing Looks Like
CENTER: Phoenix, AZ
Profile query: bilateral STN | tremor-dominant | age 65-72 | duration 8-12yr | LFP beta >25 μV²/Hz
Relevant packets received:
├── Freiburg, DE [22 matches] — contact 1+3-, 130Hz, 80μs, 2.8V → UPDRS-III -34%
├── Tokyo, JP [17 matches] — cycling 40Hz/off, LFP-triggered → tremor diary -61%
├── Toronto, CA [11 matches] — GPe co-stim trial → discontinued (dyskinesia)
├── London, UK [9 matches] — pulse width 90μs outperformed 60μs in this subtype
└── Melbourne, AU [7 matches] — amplitude ceiling at 3.1V for beta suppression
Local synthesis: parameter space prioritized by weighted outcomes
Programming session: informed rather than empirical from first adjustment
The routing substrate can be implemented through various transport mechanisms — distributed hash table-based routing is one option, but the protocol is transport-agnostic. What matters is the semantic addressing layer and the packet structure. The architecture is the breakthrough. Not the hash function. Not the storage format. Not the compression algorithm. The complete loop: structured packet → semantic address → distributed routing → local synthesis → better patient outcome → next packet contributes to the same network.
This loop is what Christopher Thomas Trevethan discovered. QIS protocol, covered by 39 provisional patents, is not a single clever component. It is the architecture of the loop itself.
The Three Elections
Three dynamics govern how a QIS-enabled DBS network matures. They are worth understanding as structural forces — not as engineered mechanisms, but as natural consequences of the architecture.
The Hiring Election. A movement disorder specialist decides what "similar enough" means for their patient population. They define the similarity function: which variables matter (symptom subtype, disease duration, LFP characteristics), which do not (precise surgical date, insurance status, ethnicity variables irrelevant to parameter prediction). This is expert judgment, not algorithmic default. The quality of what a center receives is determined by the quality of how they define similarity. The domain expert controls their own query.
The Math Election. No one votes on which parameter approaches are good. Outcomes vote. A parameter sequence that produces consistent UPDRS-III improvement across 17 centers' similar patients accumulates weight through repetition. A sequence that appears in the literature but fails in practice generates outcome packets that contradict the hypothesis. The aggregate of real-world programming sessions is the intelligence. There is no reputation layer added on top — the math is the reputation.
The Darwinism Election. Centers that define similarity well receive relevant packets and improve faster. Their programming sessions become more informed, their outcomes improve, their packets become more valuable to the network, they attract more relevant data. Centers that define similarity poorly — too broad, too narrow, miscategorized — receive irrelevant packets, see no synthesis benefit, and fall behind peers who invested in good similarity definitions. The network selects for quality of thought about patient profiles. No committee enforces this. It is structural.
44,850 Paths, Currently Zero
The problem with DBS programming intelligence is not a shortage of data. It is a shortage of routing.
The Percept PC is capturing LFP biomarkers in patients right now. Programming neurologists are developing hard-won intuitions about parameter sequences for specific patient subtypes right now. Somewhere, a team has cracked the profile that is frustrating you today.
None of it routes. 44,850 center-to-center synthesis paths exist in principle. Zero are active.
QIS protocol — Quadratic Intelligence Swarm, discovered by Christopher Thomas Trevethan, covered under 39 provisional patents — activates all of them simultaneously. Not by building a central database. Not by requiring patient data transfer. Not by waiting for federated learning to accumulate sufficient N. By posting 512-byte outcome packets to semantic addresses, pulling relevant packets from peers, and running synthesis locally.
The network gets smarter with every programming session at every center. The patient with suboptimal tremor control at your center is one routing layer away from the parameter sequence that works for her profile.
The architecture exists. The loop is complete. The paths are ready to open.
Top comments (0)