Software prototyping A case report of refining user requirements for a health information exchange dashboard
Software prototyping A case report of refining user requirements for a health information exchange dashboard
复制标题
DOI：
10.4338/aci-2015-07-cr-0091
复制
发表时间：
2016-01-01
影响因子：
2.9
通讯作者：
Cummins, Mollie R.
中科院分区：
文献类型：
--
作者：
Nelson, Scott D.;Del Fiol, Guilherme;Cummins, Mollie R.
背景：中毒控制中心(PCCs)和急诊科(EDs)之间的健康信息交流(HIE)可以改善中毒患者的护理。然而，PCC信息系统的设计并不是为了促进HIE与EDS的结合，因此，我们正在开发专门的软件，以支持PCC正常工作流程中的HIE，采用以用户为中心的设计和快速原型制作。目的：描述HIE仪表板的设计和通过快速原型对用户需求的细化。方法：利用先前获取的用户需求，通过迭代细化设计纸面上的低保真设计草图。接下来，我们设计了一个交互式高保真原型，并与最终用户进行了基于场景的可用性测试。用户被要求在完成与案例场景相关的任务时进行大声思考。测试后，用户提供反馈，并使用系统可用性量表(SUS)对原型进行评估。结果：来自3个用户的调查结果提供了有用的反馈，并将其纳入设计。在实现了稳定的设计后，我们将原型本身作为实际软件开发的规范。原型设计的好处包括：1)主题专家大量参与设计；2)快速更改的灵活性；3)在设计阶段早期最大限度地减少软件开发工作量的能力；4)需求的快速最终确定；5)设计的早期可视化；6)与程序员交流设计的强大工具。挑战包括：1)开发原型和案例情景所需的时间和精力；2)没有对系统性能进行模拟；3)最终产品中没有所有拟议的功能；4)PCC信息系统中缺少必要的数据元素。
Background: Health 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.Objective: To describe the design of an HIE dashboard and the refinement of user requirements through rapid prototyping.Methods: Using 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).Results: Survey 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.