Update readme.md
Browse files
readme.md
CHANGED
@@ -4,7 +4,7 @@ Below are the instructions to create a valid configuration file.
|
|
4 |
|
5 |
## Configuration File Structure
|
6 |
|
7 |
-
The configuration file should be in YAML format (.config file) and follow the structure outlined below
|
8 |
|
9 |
```yaml
|
10 |
disease_label: <disease_label> mandatory only if the prediction task is Phenotype
|
@@ -20,7 +20,7 @@ proc: <proc>
|
|
20 |
meds: <meds>
|
21 |
disease_filter: <disease_filter>
|
22 |
icu_no_icu: <icu_no_icu>
|
23 |
-
|
24 |
select_diag: <select_diag>
|
25 |
select_med: <select_med>
|
26 |
select_proc: <select_proc>
|
@@ -31,6 +31,33 @@ outlier: <outlier>
|
|
31 |
left_outlier: <left_outlier>
|
32 |
```
|
33 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
34 |
Replace the `<variable>` placeholders with the corresponding values specific to your use case. Detailed explanations of each variable and their valid values are provided in the next section.
|
35 |
|
36 |
## Variable Definitions and Valid Values
|
@@ -60,11 +87,15 @@ Replace the `<variable>` placeholders with the corresponding values specific to
|
|
60 |
- CAD
|
61 |
- No Disease Filter
|
62 |
- `icu_no_icu` (string): Specifies the dataset type. Valid values: ICU.
|
63 |
-
- `
|
64 |
- Convert ICD-9 to ICD-10 and group ICD-10 codes
|
65 |
- Keep both ICD-9 and ICD-10 codes
|
66 |
- Convert ICD-9 to ICD-10 codes
|
67 |
-
- `
|
|
|
|
|
|
|
|
|
68 |
- `outlier_removal` (string): Specifies the outlier removal method. Valid values:
|
69 |
- No outlier detection
|
70 |
- Impute Outlier (default:98)
|
@@ -74,7 +105,7 @@ Replace the `<variable>` placeholders with the corresponding values specific to
|
|
74 |
|
75 |
## Example Configuration File
|
76 |
|
77 |
-
Here's an example of a valid configuration file
|
78 |
|
79 |
```yaml
|
80 |
disease_label: CAD
|
@@ -100,6 +131,31 @@ outlier_removal: Impute Outlier (default:98)
|
|
100 |
outlier: 98
|
101 |
left_outlier: 0
|
102 |
```
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
103 |
|
104 |
Feel free to modify the values to fit your specific requirements.
|
105 |
|
|
|
4 |
|
5 |
## Configuration File Structure
|
6 |
|
7 |
+
The configuration file should be in YAML format (.config file) and follow the structure outlined below for **ICU Data**:
|
8 |
|
9 |
```yaml
|
10 |
disease_label: <disease_label> mandatory only if the prediction task is Phenotype
|
|
|
20 |
meds: <meds>
|
21 |
disease_filter: <disease_filter>
|
22 |
icu_no_icu: <icu_no_icu>
|
23 |
+
groupingDiag: <groupingDiag>
|
24 |
select_diag: <select_diag>
|
25 |
select_med: <select_med>
|
26 |
select_proc: <select_proc>
|
|
|
31 |
left_outlier: <left_outlier>
|
32 |
```
|
33 |
|
34 |
+
The configuration file should be in YAML format (.config file) and follow the structure outlined below for **Non-ICU Data**:
|
35 |
+
|
36 |
+
```yaml
|
37 |
+
disease_label: <disease_label> mandatory only if the prediction task is Phenotype
|
38 |
+
timePrediction: <timePrediction>
|
39 |
+
timeWindow: <timeWindow>
|
40 |
+
timebucket: <timebucket>
|
41 |
+
radimp: <radimp>
|
42 |
+
predW: <predW>
|
43 |
+
diagnosis: <diagnosis>
|
44 |
+
lab: <lab>
|
45 |
+
proc: <proc>
|
46 |
+
meds: <meds>
|
47 |
+
disease_filter: <disease_filter>
|
48 |
+
icu_no_icu: <icu_no_icu>
|
49 |
+
groupingDiag: <groupingDiag>
|
50 |
+
groupingProc: <groupingProc>
|
51 |
+
groupingMed: <groupingMed>
|
52 |
+
select_diag: <select_diag>
|
53 |
+
select_med: <select_med>
|
54 |
+
select_proc: <select_proc>
|
55 |
+
select_lab: <select_lab>
|
56 |
+
outlier_removal: <outlier_removal>
|
57 |
+
outlier: <outlier>
|
58 |
+
left_outlier: <left_outlier>
|
59 |
+
```
|
60 |
+
|
61 |
Replace the `<variable>` placeholders with the corresponding values specific to your use case. Detailed explanations of each variable and their valid values are provided in the next section.
|
62 |
|
63 |
## Variable Definitions and Valid Values
|
|
|
87 |
- CAD
|
88 |
- No Disease Filter
|
89 |
- `icu_no_icu` (string): Specifies the dataset type. Valid values: ICU.
|
90 |
+
- `groupingDiag` (string): Specifies the grouping ICD option for diagnosis. Valid values:
|
91 |
- Convert ICD-9 to ICD-10 and group ICD-10 codes
|
92 |
- Keep both ICD-9 and ICD-10 codes
|
93 |
- Convert ICD-9 to ICD-10 codes
|
94 |
+
- `groupingMed`: Specifies if grouping Medication codes should be done to use Non propietary names : Valid values : Yes, No
|
95 |
+
- `groupingProc` : Specifies the ICD codes version to perform grouping for procedures : Valid values :
|
96 |
+
- ICD-9 and ICD-10
|
97 |
+
- ICD-10
|
98 |
+
- `select_diag`, `select_med`, `select_proc`, `select_out`, `select_chart`,`select_lab` (boolean): Specifies whether to do features selection as describe in https://github.com/healthylaife/MIMIC-IV-Data-Pipeline benchmark. Valid values: True or False.
|
99 |
- `outlier_removal` (string): Specifies the outlier removal method. Valid values:
|
100 |
- No outlier detection
|
101 |
- Impute Outlier (default:98)
|
|
|
105 |
|
106 |
## Example Configuration File
|
107 |
|
108 |
+
Here's an example of a valid configuration file for **ICU Data**:
|
109 |
|
110 |
```yaml
|
111 |
disease_label: CAD
|
|
|
131 |
outlier: 98
|
132 |
left_outlier: 0
|
133 |
```
|
134 |
+
Here's an example of a valid configuration file for **Non-ICU Data**:
|
135 |
+
|
136 |
+
```yaml
|
137 |
+
timePrediction: 0
|
138 |
+
timeWindow: First 48 hours
|
139 |
+
timebucket: 2
|
140 |
+
radimp: forward fill and mean
|
141 |
+
predW: 2
|
142 |
+
diagnosis: True
|
143 |
+
lab: True
|
144 |
+
proc: False
|
145 |
+
meds: False
|
146 |
+
disease_filter: CKD
|
147 |
+
icu_no_icu: ICU
|
148 |
+
groupingDiag: Convert ICD-9 to ICD-10 and group ICD-10 codes
|
149 |
+
select_diag: False
|
150 |
+
select_med: False
|
151 |
+
select_proc: False
|
152 |
+
select_lab: False
|
153 |
+
outlier_removal: Impute Outlier (default:98)
|
154 |
+
outlier: 98
|
155 |
+
left_outlier: 0
|
156 |
+
groupingMed: Yes
|
157 |
+
groupingProc: ICD-10
|
158 |
+
```
|
159 |
|
160 |
Feel free to modify the values to fit your specific requirements.
|
161 |
|