Clinical calculator summary
MDxHealth Genomic Prostate Score (GPS) Report Interpreter, formerly Oncotype DX GPS
Clinical calculator summary
MDxHealth Genomic Prostate Score (GPS) Report Interpreter, formerly Oncotype DX GPS
Enter the final Genomic Prostate Score (GPS) and choose the current MDxHealth report family printed on the prostate-biopsy report.
Evidence-based context for fast calculator use
- Purpose:
- Interprets a final externally generated MDxHealth GPS integer within the matching current low-risk or high-risk report family.
- Population:
- patients undergoing prostate cancer diagnostic, pathologic, recurrence, or molecular-risk assessment
- Factors:
- Exact report family, GPS copied exactly from final report
MDxHealth Genomic Prostate Score (GPS) Report Interpreter, formerly Oncotype DX GPS
Clinical Context & Background
External report lookup only: current report family + externally assigned NCCN context; high-risk family uses raw GPS 0-40 versus 41-100.Reference Data
| Verified report family | Externally assigned NCCN context | Neutral interpretation |
|---|---|---|
| Current low-risk family | Very Low / Low / Favorable Intermediate | Preserve exact GPS /100 as a continuous external report result; no score category. |
| Current high-risk family | Unfavorable Intermediate / High | 0-40 lower-likelihood report band; 41-100 higher-likelihood report band. |
| Legacy, unknown, or unverified | Any | No current report-family interpretation. |
| Very High or family/context mismatch | Unsupported or contradictory | Outside scope or mismatch; no band assigned. |
Clinical Workflow
Use, Interpret, And Continue The Patient Pathway
Expand for workflow guidance, limitations, examples, and related next steps.
Clinical Workflow
Use, Interpret, And Continue The Patient Pathway
Expand for workflow guidance, limitations, examples, and related next steps.
When To Use
- When a final current MDxHealth GPS report and its report family, provenance, biopsy setting, and externally assigned NCCN context are available.
How To Interpret
- Read the submitted score unchanged in the matching report family.
- Keep the low-risk continuous-score presentation separate from the high-risk 40/41 report-band lookup.
What To Do Next
- Confirm the displayed transcription and source family against the signed laboratory report.
Limitations
- No proprietary assay derivation, NCCN calculation, probability conversion, treatment-benefit estimate, risk upstaging, or management selection.
- Legacy and unidentified report formats require their own verified documentation and are not converted.
Validated Population
Software interpretation contract for current MDxHealth GPS prostate-biopsy report families in clinically localized newly diagnosed pretreatment prostate adenocarcinoma.
Calculation verification history
Verified
Calculation verification history
Verified: Production browser revalidation
- Three source-backed GPS cases passed through visible production controls across the low-risk continuous result and the high-risk report-family 40/41 boundary.
- No unexpected N/A, literal undefined value, stale control, unsupported risk gauge, or browser-console error was observed.
Case-level evidence is retained in validation/browser-revalidation/oncotype-gps-prostate-2026-08-03.json.
: Production browser validation
- Ten source-backed cases were exercised on the public production route through visible browser controls; 10/10 case records passed their expected-versus-observed assertions across 11 visible submissions.
- Overall browser status: failed-console. medium: Production emitted minified React error #418 during the route load.
- Case-level inputs, expected and observed results, reset/repeat behavior, failure reproductions, and console evidence are retained in the production-browser evidence record.
Case-level production evidence is retained in validation/browser-production/oncotype-gps-prostate.json.
: Input workflow simplified and revalidated
- Reduced the public form to result-, branch-, unit-, and applicability-changing inputs; removed or consolidated non-scoring, administrative, and duplicate questions.
- Preserved the verified calculation or report-interpretation logic, thresholds, model version, component logic, and supported result pathways behind strict deterministic adapters.
- Passed the calculator-specific regression audit, adapter-parity and malformed-input checks, the 144-calculator input-quality audit, and the 43-calculator entry-burden audit.
: Ownership and report identity corrected
- Preserved the permanent route while updating the visible identity to the current MDxHealth GPS report interpreter and retaining the former Oncotype DX GPS name only as transparent lineage.
- Locked the route to the current MDxHealth low-risk and high-risk report families reviewed on 2026-07-24.
: Input and applicability contract corrected
- Implemented the strict immutable exact eight-key contract for diagnosis, extent, timing, specimen, report family, report provenance, externally assigned NCCN context, and integer GPS.
- Removed favorable defaults, Number coercion, aliases, missing-value fallthrough, extra-key acceptance, inherited values, decimals, and nonfinite inputs.
: Report-family interpretation and language corrected
- Restored the low-risk continuous-score presentation and confined the 0-40 versus 41-100 likelihood bands to matching current high-risk reports.
- Removed fabricated 20/40 genomic-risk bins, score-to-probability claims, upstaging, active-surveillance support, immediate-treatment preference, and other management language.
: Full implementation validation completed
- Passed 2,304 deterministic assertions using a separately encoded literal oracle.
- Verified all 101 scores across supported current report/risk contexts, strict malformed inputs, scope and provenance gates, 40/41 equality, immutable inputs, generated assets, report/evidence mirrors, source/history, registry, and ledger.
Software implementation verification only; not clinical validation.
Verification confirms the calculator implementation against the cited model; it is not independent clinical validation, regulatory approval, or medical advice.
Related Tools
Frequently Asked Questions
When should MDxHealth Genomic Prostate Score (GPS) Report Interpreter, formerly Oncotype DX GPS be used?
Use it for patients undergoing prostate cancer diagnostic, pathologic, recurrence, or molecular-risk assessment when all required inputs and the intended clinical setting are confirmed.
Can MDxHealth Genomic Prostate Score (GPS) Report Interpreter, formerly Oncotype DX GPS determine treatment by itself?
No. Interpret the result with the cited evidence, complete clinical assessment, current guidelines, and patient-specific goals.
Evidence-based oncology decision support. Verify with clinical guidelines.