Maintenance Notice

Due to necessary scheduled maintenance, the JMIR Publications website will be unavailable from Wednesday, July 01, 2020 at 8:00 PM to 10:00 PM EST. We apologize in advance for any inconvenience this may cause you.

Who will be affected?

Accepted for/Published in: JMIR Formative Research

Date Submitted: Jul 26, 2024
Date Accepted: Aug 26, 2025

The final, peer-reviewed published version of this preprint can be found here:

Identification of Design Requirements for a Software Application for Use by Clinicians That Collects Acute Stroke Treatment Data During Clinical Workflow: Pilot Study

Forward A, Koca G, Sahli A, Kamal N

Identification of Design Requirements for a Software Application for Use by Clinicians That Collects Acute Stroke Treatment Data During Clinical Workflow: Pilot Study

JMIR Form Res 2025;9:e64800

DOI: 10.2196/64800

PMID: 41418281

PMCID: 12759296

Identification of Design Requirements for a Software Application for use by Clinicians that Collects Acute Stroke Treatment Data During Clinical Workflow: A Pilot Study

  • Adam Forward; 
  • Gizem Koca; 
  • Aymane Sahli; 
  • Noreen Kamal

ABSTRACT

Background:

Clinical registries are critical for monitoring processes of care in diseases and driving quality improvements. However, many smaller hospitals do not have the required resources to gather the necessary data to contribute to registries. This study aims to design and evaluate a data collection tool for acute stroke treatment. The evaluation will identify key design requirements that facilitates prospective data collection and adds value to clinicians.

Objective:

The objective of this study was to identify the design requirements for the collection of acute ischemic stroke data during clinical workflow.

Methods:

A prototype tool was developed for testing. Clinicians were recruited through convenience sampling to observe the prototype’s use in a simulated clinical field experiment, then follow-up interviews were conducted to gain feedback. Qualitative data analysis identified design requirements that were implemented to iterate the design and finalize the design requirements.

Results:

Three participants were recruited from two hospitals in the simulated field experiment. The simulated scenario times took between 10-12 minutes, with 1.2 to 3.7 minutes spent using the prototype. The simple and condensed layout, features such as calculators and timers, and the final pop-up summary received the most positive feedback. Issues identified included the small target sizes leading to higher error rates, the lack of coloring in important features reducing their visibility, and the grouping of mandatory and optional information layouts led to a disjointed flow. The key design requirements include prioritizing simple dynamic layouts, sufficient target sizes to prevent errors, useful features with clear visual cues, and prompt data feedback to facilitate seamless integration.

Conclusions:

A prospective data collection tool for clinicians to use during stroke treatment can add value for clinicians and, with further testing, can be integrated into workflow.


 Citation

Please cite as:

Forward A, Koca G, Sahli A, Kamal N

Identification of Design Requirements for a Software Application for Use by Clinicians That Collects Acute Stroke Treatment Data During Clinical Workflow: Pilot Study

JMIR Form Res 2025;9:e64800

DOI: 10.2196/64800

PMID: 41418281

PMCID: 12759296

Download PDF


Request queued. Please wait while the file is being generated. It may take some time.

© The authors. All rights reserved. This is a privileged document currently under peer-review/community review (or an accepted/rejected manuscript). Authors have provided JMIR Publications with an exclusive license to publish this preprint on it's website for review and ahead-of-print citation purposes only. While the final peer-reviewed paper may be licensed under a cc-by license on publication, at this stage authors and publisher expressively prohibit redistribution of this draft paper other than for review purposes.