ArticleAMIA Joint Summits on Translational Science proceedings. AMIA Joint Summits on Translational Science2014
Using software to elicit user needs for clinical research visit scheduling.
Article in AMIA Joint Summits on Translational Science proceedings. AMIA Joint Summits on Translational Science, 2014. The graph could read no effect estimate from its abstract, so it casts no vote on the map. Not yet cited in PubMed.
What it found
Each row is one number read from the abstract, on the scale the paper reported it, with its interval. Left of the dashed line favours the treatment, right favours the comparator. Under each row is the sentence it came from. New to these charts? A ten-minute tutorial.
The abstract states no effect estimate the extractor could read, or names no intervention and outcome on the map, so this paper lights no cell and moves no belief. It is still indexed, cited and linked below.
The trial behind it
Trials whose registry record cites this paper, or whose number appears in the abstract. A trial that started after this paper was published is citing it as background, not reporting it.
Neither the registry nor the abstract names a trial number. If this is a trial report, that itself is worth knowing.
Who cites it
0 citing papers in PubMed.
No citing paper in PubMed yet.
Corrections and comments
PubMed lists nothing against this paper. Absence here is not a guarantee, only a check that was made.
Authors and funding
9 authors.
Funding
Abstract
User needs understanding is critical for developing useful and usable clinical research decision support. Existing methods largely depend on self-reporting and often fail to elicit implicit or fine-grained user needs. We hypothesized that functional software would address this problem by presenting to users existing technology while simultaneously encouraging users to optimize workflow. Using clinical research visit scheduling as an example, we used a piece of software under development that was called IMPACT to reveal user needs iteratively. The identified user needs explained why most clinical research coordinators still rely on paper to schedule clinical research visits. The common user needs themes such as information completeness for software to be useful may generalize to other clinical decision support. This paper contributes valuable firsthand knowledge about user needs for decision support for clinical research visit scheduling among clinical research coordinators and a generalizable methodology for collecting and analyzing software usage data to inform user needs elicitation.
Identifiers
25954586PMC4419758What OpenQuestion holds
Registered trials
Read under generation 80e0d062 · epoch 390. Bibliography from PubMed, PubMed Central and OpenAlex; grants from NIH RePORTER; trial links from ClinicalTrials.gov; estimates, votes and beliefs from the OpenQuestion graph.