Translating Advances in Medical Knowledge to Software Requirements : The Lead User Requirements Engineering Method - LURE
Bibliographic record
Abstract
Software-based clinical information systems like electronic medical records (EMR) and computerized decision support systems (CDS) have become instrumental for modern healthcare processes. However, the functionality offered by these systems needs to change in order to translate new knowledge discovered in healthcare research into clinical practice, particularly when considering large changes such as -omics and integration of continuous sensor data. A crucial prerequisite for successful knowledge translation is a sound understanding of end-user requirements. One challenge is the potentially large knowledge gap between healthcare practitioners and healthcare researchers. We propose that the Lead User method can be adapted to close this gap and report on an application of that method to elicit the requirements for introducing genomic-based decision support functions in primary care EMR software.
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.029 | 0.078 |
| Meta-epidemiology (narrow) | 0.002 | 0.002 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.005 | 0.002 |
| Science and technology studies | 0.001 | 0.004 |
| Scholarly communication | 0.005 | 0.007 |
| Open science | 0.003 | 0.007 |
| Research integrity | 0.003 | 0.004 |
| Insufficient payload (model declined to judge) | 0.006 | 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; 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".