this is for holding javascript data
Jordan Wiebe edited Coding_Coding_the_process_by__.html
about 8 years ago
Commit id: abc4d0622c54ba842c78c6720bde80a7ec2be271
deletions | additions
diff --git a/Coding_Coding_the_process_by__.html b/Coding_Coding_the_process_by__.html
index f917599..545c480 100644
--- a/Coding_Coding_the_process_by__.html
+++ b/Coding_Coding_the_process_by__.html
...
that all of the coding process was reviewed once over. The papers were analyzed for nine specific
pieces of information: outcome, measurement device, method of
aggregation, primacy of outcome, whether the outcome was a harm or side effect
of an intervention, study design, study type, metric, & sample size. With regards to metric, when an outcome element was implicitly specified, we considered it specified. E.g., because quantifying survival is, by definition, measuring time to event, specific metric for survival analysis outcomes was
always coded as time to event. For survival, remission, and relapse, measurement device was coded as “N/A” because,
besides other than a calendar, there is no measurement device. For outcomes reported using scales (e.g., NCI-CTC), metric was coded as "value at a time point" unless otherwise specified within the body of the article. When coding sample size for studies including non-pediatric-ALL research, all study participants were counted, including adult
patients and pediatric patients with a cancer other than ALL.
Analysis:
After coding, outcomes were grouped into eight domains for analysis: 1) Survival; 2) Mortality; 3)
Remission; 4) Relapse; 5) Response to Treatment; 6) Adverse Event; 7) Cognitive
Event; 8) Other.