ArticleApplied clinical informatics2016
Software Prototyping: A Case Report of Refining User Requirements for a Health Information Exchange Dashboard.
Article in Applied clinical informatics, 2016. The graph could read no effect estimate from its abstract, so it casts no vote on the map. Cited by 16 papers.
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
16 citing papers in PubMed.
- MyLungHealth, a Patient-Facing Education Tool for Lung Cancer Screening: Qualitative User-Centered Design Study.JMIR formative research · 2026Article
- End Users' Perceived Engagement with Clinical Dashboards: A Rapid Review.Studies in health technology and informatics · 2024Review
- Development of a risk-tailored approach and dashboard for efficient management and monitoring of investigator-initiated trials.BMC medical research methodology · 2023Review
- Clinical research staff perceptions on a natural language processing-driven tool for eligibility prescreening: An iterative usability assessment.International journal of medical informatics · 2023Article
- Leveraging A Clinical Dashboard and Process Mappings to Improve Treatment Access and Outcomes for Women Veterans with Urinary Incontinence.AMIA ... Annual Symposium proceedings. AMIA Symposium · 2023Article
- User Experience Design for Adoption of Asthma Clinical Decision Support Tools.Applied clinical informatics · 2022Article
- Setting Requirements for a Dashboard to Inform Portuguese Decision-Makers About Environment Health in an Urban Setting.Frontiers in public health · 2022Article
- A Shared Decision-making Tool for Drug Interactions Between Warfarin and Nonsteroidal Anti-inflammatory Drugs: Design and Usability Study.JMIR human factors · 2021Article
- Optimizing Clinical Monitoring Tools to Enhance Patient Review by Pharmacists.Applied clinical informatics · 2021Article
- Provider Preferences for Patient-Generated Health Data Displays in Pediatric Asthma: A Participatory Design Approach.Applied clinical informatics · 2021Article
- Enabling health information exchange at a US Poison Control Center.Journal of the American Medical Informatics Association : JAMIA · 2020Article
- Converting and expanding a mobile support intervention: Focus group and field-testing findings from individuals in active tuberculosis treatment.International journal of medical informatics · 2020Article
- Converting and expanding mobile support tools for tuberculosis treatment support: Design recommendations from domain and design experts.Journal of biomedical informatics: X · 2020Article
- Ontology-Based Interactive Visualization of Patient-Generated Research Questions.Applied clinical informatics · 2019Article
- Health Information Exchange in Emergency Medical Services.Applied clinical informatics · 2018Review
- Simple Workflow Changes Enable Effective Patient Identity Matching in Poison Control.Applied clinical informatics · 2018Article
Corrections and comments
PubMed lists nothing against this paper. Absence here is not a guarantee, only a check that was made.
Authors and funding
5 authors.
Funding
Abstract
backgroundHealth information exchange (HIE) between Poison Control Centers (PCCs) and Emergency Departments (EDs) could improve care of poisoned patients. However, PCC information systems are not designed to facilitate HIE with EDs; therefore, we are developing specialized software to support HIE within the normal workflow of the PCC using user-centered design and rapid prototyping.
objectiveTo describe the design of an HIE dashboard and the refinement of user requirements through rapid prototyping.
methodsUsing previously elicited user requirements, we designed low-fidelity sketches of designs on paper with iterative refinement. Next, we designed an interactive high-fidelity prototype and conducted scenario-based usability tests with end users. Users were asked to think aloud while accomplishing tasks related to a case vignette. After testing, the users provided feedback and evaluated the prototype using the System Usability Scale (SUS).
resultsSurvey results from three users provided useful feedback that was then incorporated into the design. After achieving a stable design, we used the prototype itself as the specification for development of the actual software. Benefits of prototyping included having 1) subject-matter experts heavily involved with the design; 2) flexibility to make rapid changes, 3) the ability to minimize software development efforts early in the design stage; 4) rapid finalization of requirements; 5) early visualization of designs; 6) and a powerful vehicle for communication of the design to the programmers. Challenges included 1) time and effort to develop the prototypes and case scenarios; 2) no simulation of system performance; 3) not having all proposed functionality available in the final product; and 4) missing needed data elements in the PCC information system.
Indexed as
Identifiers
What 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.