pyAKI - An Open Source Solution to Automated KDIGO classification

This data is the result of the experiment used in the validation experiment of pyAKI (https://github.com/aidh-ms/pyAKI). PyAKI is an open source software used for determining Acute Kidney Injury (AKI) stages accroding to the Kidney Injury Improving Global Outcomes (KDIGO) criteria. The data is extracted from the MIMIC Demo dataset and was then labelled by physicians and our software alike and used for comparison between both labels. The MIMIC demo dataset is a subset of the full MIMIC dataset which can be shared under the Open Data Commons Open Database License. The full MIMIC dataset is not open for publication and requires special training and identification to be worked with.

For further details on the methodology we kindly refer to our publication which can be found in the GitHub repository, mentioned above. The columns contain the following data:
- stay_id: int, unique identificator for each patient
- charttime: datetime, arbitrary date that identifies each point in time during the ICU stay in an hourly frequence
- urineoutput: float, the hourly urine output in ml
- human_urineoutput_stage: int, the AKI stage according to urine output, determined by a physician
- machine_urineoutput_stage: int, the AKI stage according to urine output, determined by pyAKI
- urineoutput_stage_vote: int, in case of discrepancy or incorrectness of both labels, the decision which AKI stage according to urine output was correct, or an alternative determined by experts
- urineoutput_stage_comment: string, free text comment explaining the reasoning behind a stage correction
- creat: float, the creatinine values in mg/dl
- human_abs_creat_stage: int, the AKI stage according to absolute creatinine criterion, determined by a physician
- machine_abs_creat_stage: int, the AKI stage according to absolute creatinine criterion, determined by pyAKI
- abs_creat_stage_vote: int, in case of discrepancy or incorrectness of both labels, the decision which AKI stage according to absolute creatinine criterion was correct, or an alternative determined by experts
- abs_creat_stage_comment: string, free text comment explaining the reasoning behind a stage correction
- human_rel_creat_stage: int, the AKI stage according to relative creatinine criterion, determined by a physician
- machine_rel_creat_stage: int, the AKI stage according to relative creatinine criterion, determined by pyAKI
- rel_creat_stage_vote: int, in case of discrepancy or incorrectness of both labels, the decision which AKI stage according to relative creatinine criterion was correct, or an alternative determined by experts
- rel_creat_stage_comment: string, free text comment explaining the reasoning behind a stage correction
- weight: float, the weight of each patient
- rrt_status: bool, the status of renal replacementtherapy (RRT), 0 or NaN indicating no RRT ist present, 1 indicating RRT is present
- human_rrt_stage: int, AKI stage according to dialysis criterion, determined by physicians
- machine_rrt_stage: int, AKI stage according to dialysis criterion, determined by pyAKI
- rrt_stage_vote: int, in case of discrepancy or incorrectness of both labels, the decision which AKI stage according to dialysis criterion was correct, or an alternative determined by experts
- rrt_stage_comment: string, free text comment explaining the reasoning behind a stage correction
- human_stage: the overall AKI stage, determined by physicians
- machine_stage: the overall AKI stage, determined by physicians
- stage_vote: int, in case of discrepancy or incorrectness of both labels, the decision which AKI overall stage was correct, or an alternative determined by experts
- stage_comment: string, free text comment explaining the reasoning behind a stage correction