05/07/2026
Decoding the Nervous System: My Process with P-DTR
In my practice, I treat the body like a complex biological computer. To get the best results using Proprioceptive Deep Tendon Reflex (P-DTR), I follow a specific “debugging” protocol to ensure I’m working with the nervous system rather than against it.
1. Checking the Connection
Before starting, I must ensure the patient is “testable.” This means verifying that their muscles respond accurately to specific stimuli. If there is too much “noise” in the nervous system, I’m effectively “locked out” of the network—much like hitting a firewall. In these cases, I have to back up, identify the source of the disruption (often a specific area where pain receptors are misfiring), and reset those sensors using P-DTR protocols before I can proceed.
2. Accessing the “Source Code”
Once the firewall is down, I have the patient initiate a specific movement—perhaps a simple neck rotation or a complex motion like a running stride. I think of this as hitting “Ctrl + Alt + Del” on a keyboard; it highlights the dysfunctional pattern within the nervous system.
By engaging this movement, I can “get into the system” to find the offending muscle or joint. This puts the patient into what I call Diagnostic Mode. Much like a programmer booting a PC into MS-DOS to rewrite code, this state allows me to access deeper neurological layers.
3. The Diagnostic State
Interestingly, the patient doesn’t feel any different while in this mode. However, their neurology shifts: all isolated muscle tests will temporarily show “weak” until the dysfunctional pattern is resolved or I manually exit the diagnostic state.
4. The System Reset
By following the strict rules of P-DTR, I can effectively reprogram the software of the body. I identify overfiring or underfiring muscles and “reset” them, bringing balance back to the joints and fluid harmony to the patient’s movement patterns.