Dutasteride for Post Finasteride Syndrome
There is no direct, dutasteride-specific evidence that dutasteride causes Post-Finasteride Syndrome; the link rests entirely on extrapolation from finasteride as a shared 5-alpha-reductase inhibitor, so any causal claim remains unverified and disputed.
Why this grade7-layer evidence engine
This grade is Unverified because no dutasteride-specific RCT, cohort, or prospective study of persistent post-treatment symptoms exists. The largest data point, a 2019 meta-analysis (PMID 30206635, n=4495), found only a non-significant trend toward sexual adverse effects with dutasteride (RR 1.37, 95% CI 0.81-2.32) and measured events during treatment, not after stopping. A 2016 systematic review (PMID 27672412) reported similar treatment-era rates but did not establish a distinct post-dutasteride syndrome.
The remaining literature is mechanistic or anecdotal. A 2025 review (PMID 38886596) treats PFS as a theoretical 5-alpha-reductase class effect without dutasteride-specific data, the only human report invoking dutasteride is a single confounded case of combined finasteride plus dutasteride use (PMID 27298504, n=1), and a 2018 editorial (PMID 30549493) warns that odds ratios near 1.5 overstate absolute risk at low baseline rates.
Regulators and clinics are split, which drives the 'disputed' status. The FDA approves dutasteride (Avodart) for benign prostatic hyperplasia only, and the EMA's 2025 review found no direct causal link to suicidal ideation while applying precautionary class-effect labeling; WHO pharmacovigilance shows a far smaller dutasteride signal than finasteride. The Post-Finasteride Syndrome Foundation names dutasteride as a cause, but mainstream urology and academic clinics do not recognize PFS as a distinct entity.
Scoring transparency
All scores computed by a 7-layer evidence engine — fully auditable▸View the full decision path (audit trail)
- compute_raw_score — 加權公式: L2×0.30 + L3×0.25 + L5×0.25 + L11×0.10 + L1×0.10 = 0.515
- tier_from_score — 依分數區間映射至 tier letter
- apply_hec_rules — 無高階證據可裁決
- tier_strict_requirement_check — | C→U 因 scope.conflation_risk=true 且 L11 獨評較低 (B7-2 tier cap)
- detect_disputes — 偵測到 1 個 hard + 0 個 soft dispute
- decide_status — 依 tier + dispute 結果決定 status