-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathsummary.qmd
More file actions
51 lines (27 loc) · 1.41 KB
/
summary.qmd
File metadata and controls
51 lines (27 loc) · 1.41 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
# Working log {.unnumbered}
Here is the Future work for TSA and Randy's thesis
## 20231101
1. Including other features and outcomes for matching
2. Using both pain for informative outcome for outcome inference
2\*. pain and dash two outcomes
3. ✅ 365 days cut off this is the last step of data cleaning
4. ✅ Insurance company, and the worker report worse
5. ✅ Cleaning multiple surgeries
- filter out the patient with only one
- filter out the two situations
- gap between the two surgeries are short or with few outcomes
- two adjacent surgeries without outcomes in between
- the second surgery without any further outcomes after
## 20231106
6. ✅ Cleaning the pain dataset
7. ✅ Table or histogram for the outcome number, timemax, and pain
## 20231109
8. How to use the tsa data.
- filter the patients with the first outcome in a week after surgery
- use imputation inla-rw or inla-bspline as the baseline
- ask Stef whether brokenstick or multiple-imputation is powerful enough to provide
- test on the patients with first outcome in a week (pick out the patients)
9. ✅ The pain and outcome at the same time ??? - most with both outcomes, very few no at the same time
10. only keep the first surgery for every one
11. the baseline will be `what ever the first outcome value is` and
include the time gap between surgery and the first outcome