06.05.2014 Views

Book of abstract 2008

Book of abstract 2008

Book of abstract 2008

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Clinical use <strong>of</strong> cleaved forms <strong>of</strong> the urokinase receptor<br />

Gunilla Høyer Hansen, Charlotte Almasi, Helle Pappot, Ib Jarle Christensen<br />

Finsen Laboratory, Copenhagen Biocenter, Ole Maaløes Vej 5, DK-2200 Copenhagen N, Denmark<br />

It is well established that the urokinase plasminogen activator, uPA and its cellular<br />

receptor uPAR are involved in cancer invasion and metastasis and the tumor tissue and<br />

circulating levels correlate with cancer patient survival. In addition to the cellular binding,<br />

uPA cleaves uPAR in the linker region between domains I and II and thereby inactivates<br />

uPAR´s binding potential. Cleavage <strong>of</strong> uPAR thus reflects the activity <strong>of</strong> uPA and possibly<br />

the aggressiveness <strong>of</strong> the tumor. uPA in physiological relevant concentrations cleaves<br />

glycolipid-anchored uPAR but not soluble uPAR (suPAR). To elucidate the mechanism<br />

<strong>of</strong> uPA-mediated uPAR cleavage and identify the different uPAR forms we have used<br />

PMA–stimulated U937 cells. On the cell surface as well as inside the cell, both intact<br />

uPAR(I-III) and cleaved uPAR(II-III) are present, whereas in the media only intact suPAR<br />

and uPAR(I) are detected. Treatment <strong>of</strong> the cells with Pi-PLC releases both uPAR(I-III)<br />

and uPAR(II-III) from the cell surface. Biotinylation <strong>of</strong> cell surface proteins showed that<br />

when uPAR cleavage was inhibited by incubation with a neutralizing anti-uPA antibody,<br />

uPAR(II-III) was not found on the cell surface. The intracellular pattern <strong>of</strong> uPAR(I-III)<br />

and uPAR(II-III) was not affected by inhibiting the cell surface cleavage. However, in<br />

the media from cells grown in the presence <strong>of</strong> the neutralizing anti-uPA antibody, both<br />

suPAR(I-III) and suPAR(II-III) were present. This indicates that uPAR(II-III) is shed<br />

from the cell surface when uPA-mediated cleavage <strong>of</strong> uPAR is blocked.<br />

In tumor tissue and body fluids both intact and cleaved forms <strong>of</strong> uPAR have been<br />

identified using Western blotting and immunoassays quantifying the individual uPAR<br />

forms. In tumor extracts from patients with non-small cell lung cancer uPAR(I) is<br />

a stronger prognostic marker then the total amount <strong>of</strong> all uPAR forms. Also in serum<br />

from patients with non-small cell lung cancer the level <strong>of</strong> uPAR(I) correlates with overall<br />

survival. The concentrations <strong>of</strong> uPAR(I) as well as suPAR(II-III) are significantly elevated<br />

in serum samples<br />

l13<br />

from patients with prostate cancer compared to the concentrations in<br />

serum from men with benign prostatic conditions. Furthermore, specific measurements<br />

<strong>of</strong> uPAR(I) were found to improve specificity <strong>of</strong> prostate cancer detection. Similarly high<br />

concentration <strong>of</strong> plasma uPAR(I) is an independent preoperative marker <strong>of</strong> poor prognosis<br />

in patients with ovarian cancer. The combination <strong>of</strong> plasma suPAR(I-III)+suPAR(II-III)<br />

and CA125 discriminates between malignant and benign ovarian tumors with an AUC<br />

<strong>of</strong> 0.94. We will verify our findings in a larger collection <strong>of</strong> plasma/serum samples from<br />

prostate, ovarian and non-small cell lung cancer patients and investigate the prognostic<br />

significance and possible diagnostic utility <strong>of</strong> cleaved uPAR variants in other forms <strong>of</strong><br />

cancer.<br />

28

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!