how can i interpret cox multivariate analysis result
1
1
Entering edit mode
9 weeks ago
Sarah ▴ 30

Hello,

I performed a multivariate cox analysis using the following command for a single X gene(I am not very sure of my command ).

coxtest <- coxph(Surv(daysToDeath_cox, vitalStatus_cox) ~ DEG + ajcc_pathological_stage + gender + cigarette)


I got this result, someone can show me how I can interpret this, what can I say about the prognostic effect of this gene

Thank you !

statistics bladder analysis survival cancer • 380 views
ADD COMMENT
1
Entering edit mode
9 weeks ago
Jeremy ▴ 740

How was vitalStatus_cox coded? Assuming that death = 1 and censored = 0, this data shows that the risk associated with DEG is 0.93345 times the baseline risk (i.e. the risk of dying is slightly less), all other variables being the same. Along the same lines, ajcc_pathological_stageStage III increases risk 4.3023 times compared to baseline (Stage 0?), all other variables being the same. The risk associated with being male is 1.31453 times that of being female, all other variables being the same. That said, if you use a p-value cutoff of 0.05, none of these variables are statistically significant.

ADD COMMENT
1
Entering edit mode

Thank you, I have coded vital status like this :

nonComplt_cox <- is.na(daysToDeath_cox) vitalStatus_cox <- as.numeric(ifelse(nonComplt_cox, 0, 1))

Assuming that it is statistically significant and that DEG is the expression of gene x, can we say that this (gene x) has a prognostic effect in these cancer data during stage 2 etc.?

ADD REPLY
1
Entering edit mode

If it's statistically significant, then I think you can say that Gene X is prognostic for survival. If you want to know about a specific stage, then I think you would need to run the analysis on only patients that have that stage.

ADD REPLY
1
Entering edit mode

Thank you a lot !

ADD REPLY

Login before adding your answer.

Traffic: 1263 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6