Integrating Health and Disability Data Into Academic Information Systems: Workflow Optimization Study
Bibliographic record
Abstract
Background: Integrating health information into university information systems holds significant potential for enhancing student support and well-being. Despite the growing body of research highlighting issues faced by university students, including stress, depression, and disability, little has been done in the informatics field to incorporate health technologies at the institutional level. Objective: This study aims to investigate the current state of health information integration within university systems and provide design recommendations to address existing gaps and opportunities. Methods: We used a user-centered approach to conduct interviews and focus group sessions with stakeholders to gather comprehensive insights and requirements for the system. The methodology involved data collection, analysis, and the development of a suggested workflow. Results: The findings of this study revealed the shortcomings in the current process of handling health and disability data within university information systems. In our results, we discuss some requirements identified for integrating health-related information into student information systems, such as privacy and confidentiality, timely communication, task automation, and disability resources. We propose a workflow that separates the process into 2 distinct components: a health and disability system and measures of quality of life and wellness. The proposed workflow highlights the vital role of academic advisors in facilitating support and enhancing coordination among stakeholders. Conclusions: To streamline the workflow, it is vital to have effective coordination among stakeholders and redesign the university information system. However, implementing the new system will require significant capital and resources. We strongly emphasize the importance of increased standardization and regulation to support the information system requirements for health and disability. Through the adoption of standardized practices and regulations, we can ensure the smooth and effective implementation of the required support system.
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.018 | 0.037 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.003 | 0.004 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.004 | 0.003 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.002 | 0.000 |
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; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
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".