Biochemical staging of XXXX .

@entity5 @entity1 @entity2533 @entity263
PSA continues to be one of the most effective and widely used @entity5 screening tools available. Its popularity in @entity263 screening, however, has eroded its usefulness in the staging of this disease. As more @entity1 are screened every year on a routine basis with DRE and PSA, the average PSA at diagnosis has drifted down to well below 10 ng/mL in many centers, including ours. This trend is likely to accelerate, as a PSA cut off for prompting biopsy of the prostate of 2.5 ng/mL gains more widespread acceptance. The recent realization that, at these levels, serum PSA is more reflective of the presence of BPH than of the extent of @entity5 and, therefore, does not provide additional staging information, has renewed the search for new biochemical markers that are capable of predicting @entity263 stage and prognosis. Because of the heterogeneity of this disease, it is unlikely that a single biochemical marker that is capable of accurately staging @entity263 @entity1 will be found. For this reason, nomograms that are capable of integrating various parameters to predict stage and prognosis will remain indispensable. As new biochemical markers that provide independent predictive information about stage or prognosis are identified, they can be incorporated into currently available nomograms. Of the biochemical markers discussed in this article, IL-6sR and @entity2533 are the most promising. By incorporating them into a preoperative nomogram designed to predict PSA recurrence, we found that they improved the ability to predict biochemical recurrence by a statistically and clinically significant margin. The @entity5 and predict response to therapy has improved dramatically over the last 3 decades. Nevertheless, there is still a need for new biochemical markers that will improve the ability to predict an individual @entity1 's stage and response to therapy. Incorporating these new markers into nomograms will enhance the ability to provide optimal care for each @entity263 @entity1 .
