Validation of multiplex steroid hormone measurements in prostate cancer using plasma for multimodality biomarker studies release_oo4csefv4jgmvh3hjjl3piwql4

by Gido Snaterse, Lisanne F. van Dessel, Angela E Taylor, Jenny A Visser, Wiebke Arlt, Martijn P. Lolkema, Johannes Hofland

Released as a post by Cold Spring Harbor Laboratory.

2020  

Abstract

Background Steroid hormones are essential signaling molecules in prostate cancer (PC). However, many studies focusing on liquid biomarkers fail to take hormonal status of these patients into account. Because steroid measurements are sensitive to bias caused by matrix effects, thus assessing potential matrix effects is an important step in combining ctDNA analysis with hormone status. Methods We investigated the accuracy of multi-steroid hormone profiling in mechanically-separated plasma tubes (MSP) and in CellSave Preservative plasma tubes (CS), that are typically used to obtain ctDNA. We performed multiplex steroid profiling in samples obtained from ten healthy controls and ten castration-resistant prostate cancer patients Results Steroid measurements were comparable between the MSP and serum tubes. A small but consistent decrease of 11 - 18% compared to serum was observed in CS tubes, which was considered to be within the acceptable margin. The minimally residual testosterone levels of castrate patients could be sensitively quantified in both CS and MSP samples. Conclusions We validated the use of MSP and CS tubes for multi-steroid profiling by LC-MS/MS. The optimised use of these samples used in clinical trials will allow us to gain further insight into the steroid metabolism in PC patients.
In application/xml+jats format

Archived Files and Locations

application/pdf   3.0 MB
file_mgluuc7hqngnfnmnj5c3j5ogwq
www.medrxiv.org (repository)
web.archive.org (webarchive)
Read Archived PDF
Preserved and Accessible
Type  post
Stage   unknown
Date   2020-08-06
Work Entity
access all versions, variants, and formats of this works (eg, pre-prints)
Catalog Record
Revision: 80003b9e-12b2-4be6-a8d2-a16fc2913c86
API URL: JSON