Beyond “implementation”: digital health innovation and service design
Bibliographic record
Abstract
Digital tools have shown great potential to enhance health services' capacity to achieve the goals of the triple aim (enhance patient experience, improve health outcomes, and control or reduce costs), but their actual impact remains variable. In this commentary, we suggest that shifting from a perspective focused on "implementing" new digital tools in health care settings toward one focused on "service design" will help teams execute more successful digital technology adoption projects. We present value proposition design (VPD) as a service design strategy requiring that stakeholders are brutally honest in determining the value of a new digital tool for their everyday work. Incorporating a perspective focused on how the value proposition of a technology is understood by each team member, and implications for their work routines, will help project teams to better understand how services can be reinvented during technology adoption initiatives. We present the simple heuristic [Tool+Team+Routine] as a reminder of the central considerations that make up a service design initiative, and present an illustrative case scenario of designing the use of a digital care coordination platform in an actual digital technology adoption project. We conclude by outlining two important challenges that need to be addressed to advance service design approaches to technology adoption in health care.
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.017 | 0.033 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.004 | 0.006 |
| Science and technology studies | 0.002 | 0.019 |
| Scholarly communication | 0.010 | 0.013 |
| Open science | 0.003 | 0.004 |
| Research integrity | 0.010 | 0.009 |
| Insufficient payload (model declined to judge) | 0.004 | 0.001 |
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".