Towards the Use of Standardized Terms in Clinical Case Studies for Process Mining in Healthcare
Bibliographic record
Abstract
Process mining can provide greater insight into medical treatment processes and organizational processes in healthcare. To enhance comparability between processes, the quality of the labelled-data is essential. A literature review of the clinical case studies by Rojas et al. in 2016 identified several common aspects for comparison, which include methodologies, algorithms or techniques, medical fields, and healthcare specialty. However, clinical aspects are not reported in a uniform way and do not follow a standard clinical coding scheme. Further, technical aspects such as details of the event log data are not always described. In this paper, we identified 38 clinically-relevant case studies of process mining in healthcare published from 2016 to 2018 that described the tools, algorithms and techniques utilized, and details on the event log data. We then correlated the clinical aspects of patient encounter environment, clinical specialty and medical diagnoses using the standard clinical coding schemes SNOMED CT and ICD-10. The potential outcomes of adopting a standard approach for describing event log data and classifying medical terminology using standard clinical coding schemes are further discussed. A checklist template for the reporting of case studies is provided in the Appendix A to the article.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.276 | 0.438 |
| Meta-epidemiology (narrow) | 0.002 | 0.002 |
| Meta-epidemiology (broad) | 0.003 | 0.006 |
| Bibliometrics | 0.027 | 0.029 |
| Science and technology studies | 0.003 | 0.010 |
| Scholarly communication | 0.023 | 0.022 |
| Open science | 0.007 | 0.015 |
| Research integrity | 0.004 | 0.012 |
| Insufficient payload (model declined to judge) | 0.005 | 0.003 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; the direct Gemma label and the distilled Codex classifier agree on what is shown here.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".