← Return to Prostox - learn about whether radiation will cause problems

Discussion
Comment receiving replies
Profile picture for K. J. HOLZ @kjholz

Just need to give people a heads-up. Because my husband has a weak stream and a 3+4 tumour in the right medial apex, we were worried that radiation could convert his existing weak stream into no-stream-at-all.

So we ordered both Prostox Ultra (SBRT) and Prostox Standard (CFRT) tests. Only 1%–2% of patients are found to be high risk of toxicity from both SBRT and CFRT/MHFRT. He scored "HIGH RISK" on both! Radiation was out!

Pic 1 👇 shows what our January 15, 2026 Prostox report looked like. It had just two risk categories. Either "LOW RISK" or "HIGH RISK".

I checked today and UCLA/Prostox has now changed their "Interpreting PROSTOX Results" report page to "LOW-AVERAGE RISK" or "HIGH RISK"!
https://miradx.com/prostox/interpreting-results/
From "LOW RISK" Jan 2026 to "LOW-AVERAGE RISK" now...

I wonder if page 2 of their current results report still includes:

"Limitations: Results do not predict a patient’s likelihood of clinical response, short-term side effects, or non-urinary side effects from SBRT or CFRT. A low-risk result does not rule out any possibility that the patient will experience toxicity, and a high-risk result does not guarantee that the patient will develop toxicity. Results should only be used as part of the
consideration of treatment choice."

Jump to this post


Replies to "Just need to give people a heads-up. Because my husband has a weak stream and a..."

@kjholz My Apr 13 1:07pm comment:

"I checked today and UCLA/Prostox has now changed their "Interpreting PROSTOX Results" report page to "LOW-AVERAGE RISK" or "HIGH RISK"!
https://miradx.com/prostox/interpreting-results/
From "LOW RISK" Jan 2026 to "LOW-AVERAGE RISK" now..."

IS WRONG! And I don't know how to delete it.

Only today (April 29th) did I realize that Prostox results were NOT changed from a gradation that included "AVERAGE" to the binary "High" vs "Low" risks.

I had not noticed the date being *2022* and not 2026. Anyway, I was careless and wrong!