Evidence map›Paper›PMID 27081404›Full record

ArticleApplied clinical informatics2016

Software Prototyping: A Case Report of Refining User Requirements for a Health Information Exchange Dashboard.

Scott D Nelson, Guilherme Del Fiol, Haley Hanseler, Barbara Insley Crouch, Mollie R Cummins

Abstract read
In one paragraph

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.

0numbers the graph read from it
0cells of the map it votes in
16citing papers in PubMed
–field-weighted citation impact
1 · What the graph read from it

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.

2 · The registry

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.

3 · Its place in the literature

Who cites it

16 citing papers in PubMed.

  1. Article
  2. End Users' Perceived Engagement with Clinical Dashboards: A Rapid Review.Studies in health technology and informatics · 2024
    Review
  3. Review
  4. Article
  5. Article
  6. Article
  7. Article
  8. Article
  9. Article
  10. Article
  11. Enabling health information exchange at a US Poison Control Center.Journal of the American Medical Informatics Association : JAMIA · 2020
    Article
  12. Article
  13. Article
  14. Article
  15. Review
  16. Article
4 · The record

Corrections and comments

PubMed lists nothing against this paper. Absence here is not a guarantee, only a check that was made.

5 · Who and what money

Authors and funding

5 authors.

Scott D NelsonVanderbilt University Medical Center , Nashville, TN, USA.
Guilherme Del FiolUniversity of Utah , Salt Lake City, UT, USA.
Haley HanselerUniversity of Utah , Salt Lake City, UT, USA.
Barbara Insley CrouchUniversity of Utah , Salt Lake City, UT, USA.
Mollie R CumminsUniversity of Utah , Salt Lake City, UT, USA.

Funding

Electronic Exchange of Poisoning InformationR01HS021472 · AHRQ · UNIVERSITY OF UTAH · PI CUMMINS, MOLLIE R. · 2013 to 2017
$1.2M
AHRQ HHS R01 HS021472AHRQ HHS R01 HS021472-01A1
6 · The paper itself

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

Health Information ExchangeSoftwareEmergency Service, HospitalFeedbackHumansPoison Control CentersTime Factorshuman engineering/methodsmedical informatics/methodsSoftware designuser-computer interface

Identifiers

PMID27081404
PMCPMC4817332

What OpenQuestion holds

Textmetadata
Read underepoch 390

Registered trials

None linked

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.