Dataset Information

User stories as lightweight requirements for agile clinical decision support development.

ABSTRACT: OBJECTIVE:We sought to demonstrate applicability of user stories, progressively elaborated by testable acceptance criteria, as lightweight requirements for agile development of clinical decision support (CDS). MATERIALS AND METHODS:User stories employed the template: As a [type of user], I want [some goal] so that [some reason]. From the "so that" section, CDS benefit measures were derived. Detailed acceptance criteria were elaborated through ensuing conversations. We estimated user story size with "story points," and depicted multiple user stories with a use case diagram or feature breakdown structure. Large user stories were split to fit into 2-week iterations. RESULTS:One example user story was: As a rheumatologist, I want to be advised if my patient with rheumatoid arthritis is not on a disease-modifying anti-rheumatic drug (DMARD), so that they receive optimal therapy and can experience symptom improvement. This yielded a process measure (DMARD use), and an outcome measure (Clinical Disease Activity Index). Following implementation, the DMARD nonuse rate decreased from 3.7% to 1.4%. Patients with a high Clinical Disease Activity Index improved from 13.7% to 7%. For a thromboembolism prevention CDS project, diagrams organized multiple user stories. DISCUSSION:User stories written in the clinician's voice aid CDS governance and lead naturally to measures of CDS effectiveness. Estimation of relative story size helps plan CDS delivery dates. User stories prove to be practical even on larger projects. CONCLUSIONS:User stories concisely communicate the who, what, and why of a CDS request, and serve as lightweight requirements for agile development to meet the demand for increasingly diverse CDS.

SUBMITTER: Kannan V

PROVIDER: S-EPMC6798563 | biostudies-literature | 2019 Nov

REPOSITORIES: biostudies-literature

ACCESS DATA

Publications

User stories as lightweight requirements for agile clinical decision support development.

Kannan Vaishnavi V Basit Mujeeb A MA Bajaj Puneet P Carrington Angela R AR Donahue Irma B IB Flahaven Emily L EL Medford Richard R Melaku Tsedey T Moran Brett A BA Saldana Luis E LE Willett Duwayne L DL Youngblood Josh E JE Toomay Seth M SM

Journal of the American Medical Informatics Association : JAMIA 20191101 11

<h4>Objective</h4>We sought to demonstrate applicability of user stories, progressively elaborated by testable acceptance criteria, as lightweight requirements for agile development of clinical decision support (CDS).<h4>Materials and methods</h4>User stories employed the template: As a [type of user], I want [some goal] so that [some reason]. From the "so that" section, CDS benefit measures were derived. Detailed acceptance criteria were elaborated through ensuing conversations. We estimated us ...[more]

PMID: 31512730

Similar Datasets

Project description:BackgroundMoving to electronic health records (EHRs) confers substantial benefits but risks unintended consequences. Modern EHRs consist of complex software code with extensive local configurability options, which can introduce defects. Defects in clinical decision support (CDS) tools are surprisingly common. Feasible approaches to prevent and detect defects in EHR configuration, including CDS tools, are needed. In complex software systems, use of test-driven development and automated regression testing promotes reliability. Test-driven development encourages modular, testable design and expanding regression test coverage. Automated regression test suites improve software quality, providing a "safety net" for future software modifications. Each automated acceptance test serves multiple purposes, as requirements (prior to build), acceptance testing (on completion of build), regression testing (once live), and "living" design documentation. Rapid-cycle development or "agile" methods are being successfully applied to CDS development. The agile practice of automated test-driven development is not widely adopted, perhaps because most EHR software code is vendor-developed. However, key CDS advisory configuration design decisions and rules stored in the EHR may prove amenable to automated testing as "executable requirements."ObjectiveWe aimed to establish feasibility of acceptance test-driven development of clinical decision support advisories in a commonly used EHR, using an open source automated acceptance testing framework (FitNesse).MethodsAcceptance tests were initially constructed as spreadsheet tables to facilitate clinical review. Each table specified one aspect of the CDS advisory's expected behavior. Table contents were then imported into a test suite in FitNesse, which queried the EHR database to automate testing. Tests and corresponding CDS configuration were migrated together from the development environment to production, with tests becoming part of the production regression test suite.ResultsWe used test-driven development to construct a new CDS tool advising Emergency Department nurses to perform a swallowing assessment prior to administering oral medication to a patient with suspected stroke. Test tables specified desired behavior for (1) applicable clinical settings, (2) triggering action, (3) rule logic, (4) user interface, and (5) system actions in response to user input. Automated test suite results for the "executable requirements" are shown prior to building the CDS alert, during build, and after successful build.ConclusionsAutomated acceptance test-driven development and continuous regression testing of CDS configuration in a commercial EHR proves feasible with open source software. Automated test-driven development offers one potential contribution to achieving high-reliability EHR configuration. Vetting acceptance tests with clinicians elicits their input on crucial configuration details early during initial CDS design and iteratively during rapid-cycle optimization.

Project description:BackgroundChildren are at increased risk from transfusion-related medical errors. Clinical decision support (CDS) can enhance pediatric providers' decision-making regarding transfusion practices including indications, volume, rate, and special processing instructions. Our objective was to use CDS in a pediatric health system to reduce:blood product-related safety events from ordering errors;special processing ordering errors for patients with T-cell dysfunction, sickle cell disease (SCD), or thalassemia;transfusions administered faster than 5 mL/kg/h.Materials and methodsIn this single-center before and after quality improvement study, we evaluated how user-centered design of pediatric blood product orders influenced pediatric transfusion practices and outcomes. Safety events were identified through active and passive surveillance. Other clinically relevant outcomes were identified through electronic health record queries.ResultsBlood product-related safety events from ordering errors did not change significantly from the baseline period (6 events, 0.4 per month, from 1/1/2018-3/27/2019) to the intervention period (1 event, 0.1 per month, from 3/28/2019-12/31/2019; rate ratio: 0.27 [0.01-2.25]). Packed red blood cell (PRBC) and platelet orders for patients with T-cell dysfunction that did not specify irradiation decreased significantly from 488/12,359 (3.9%) to 204/6,711 (3.0%, risk ratio: 0.77 [0.66-0.90]). PRBC orders for patients with SCD or thalassemia that did not specify phenotypically similar units fell from 386/2,876 (13.4%) to 57/1,755 (3.2%, risk ratio: 0.24 [0.18-0.32]). Transfusions administered faster than 5 mL/kg/h decreased from 4,112/14,641 (28.1%) to 2,125/9,263 (22.9%, risk ratio: 0.82 [0.78-0.85]).DiscussionUser-centered design of CDS for pediatric blood product orders significantly reduced special processing ordering errors and inappropriate transfusion rates. Larger studies are needed to evaluate the impact on safety events.

Project description:BackgroundCurrent guidelines recommend less aggressive target hemoglobin A1c (HbA1c) levels based on older age and lower life expectancy for older adults with diabetes. The effectiveness of electronic health record (EHR) clinical decision support (CDS) in promoting guideline adherence is undermined by alert fatigue and poor workflow integration. Integrating behavioral economics (BE) and CDS tools is a novel approach to improving adherence to guidelines while minimizing clinician burden.MethodsWe will apply a systematic, user-centered design approach to incorporate BE "nudges" into a CDS module and will perform user testing in two "vanguard" sites. To accomplish this, we will conduct (1) semi-structured interviews with key informants (n = 8), (2) a 2-h, design-thinking workshop to derive and refine initial module ideas, and (3) semi-structured group interviews at each site with clinic leaders and clinicians to elicit feedback on three proposed nudge module components (navigator section, inbasket refill protocol, medication preference list). Detailed field notes will be summarized by module idea and usability theme for rapid iteration. Frequency of firing and user action taken will be assessed in the first month of implementation via EHR reporting to confirm that module components and related reporting are working as expected as well as assess utilization. To assess the utilization and feasibility of the new tools and generate estimates of clinician compliance with the Choosing Wisely guideline for diabetes management in older adults, a 6-month, single-arm pilot study of the BE-EHR module will be conducted in six outpatient primary care clinics.DiscussionWe hypothesize that a low burden, user-centered approach to design will yield a BE-driven, CDS module with relatively high utilization by clinicians. The resulting module will establish a platform for exploring the ability of BE concepts embedded within the EHR to affect guideline adherence for other use cases.

Project description:BackgroundPharmacogenomic clinical decision support systems (CDSS) have the potential to help overcome some of the barriers for translating pharmacogenomic knowledge into clinical routine. Before developing a prototype it is crucial for developers to know which pharmacogenomic CDSS features and user-system interactions have yet been developed, implemented and tested in previous pharmacogenomic CDSS efforts and if they have been successfully applied. We address this issue by providing an overview of the designs of user-system interactions of recently developed pharmacogenomic CDSS.MethodsWe searched PubMed for pharmacogenomic CDSS published between January 1, 2012 and November 15, 2016. Thirty-two out of 118 identified articles were summarized and included in the final analysis. We then compared the designs of user-system interactions of the 20 pharmacogenomic CDSS we had identified.ResultsAlerts are the most widespread tools for physician-system interactions, but need to be implemented carefully to prevent alert fatigue and avoid liabilities. Pharmacogenomic test results and override reasons stored in the local EHR might help communicate pharmacogenomic information to other internal care providers. Integrating patients into user-system interactions through patient letters and online portals might be crucial for transferring pharmacogenomic data to external health care providers. Inbox messages inform physicians about new pharmacogenomic test results and enable them to request pharmacogenomic consultations. Search engines enable physicians to compare medical treatment options based on a patient's genotype.ConclusionsWithin the last 5 years, several pharmacogenomic CDSS have been developed. However, most of the included articles are solely describing prototypes of pharmacogenomic CDSS rather than evaluating them. To support the development of prototypes further evaluation efforts will be necessary. In the future, pharmacogenomic CDSS will likely include prediction models to identify patients who are suitable for preemptive genotyping.

Project description:PLAIN ENGLISH SUMMARY:For the elderly to get the care and services they need, they may need to make the difficult decision about staying in their home or moving to another home. Many other people may be involved in their care too (friends, family and healthcare providers), and can support them in making the decision. We asked informal caregivers of elderly people to help us develop a decision guide to support them and their loved ones in making this decision. This guide will be used by health providers in home care who are trained to help people make decisions. The guide is in French and English. To design and test this decision guide we involved elderly people, their caregivers and health administrators. We first asked them what they needed for making the decision, and then designed a first version of the guide. Then we asked them to look at it and give feedback, which was used to make the final version. We then used scientific criteria to check its content and the language used. The final decision guide was acceptable to the caregivers, their elderly loved ones, and the health administrators. The guide is currently being evaluated in a large research project with home care teams in the province of Quebec. ABSTRACT:Background As they grow older, many elderly people are faced with the difficult and preference-sensitive decision about staying in their home or moving to a residence better adapted to their evolving care needs. We aimed to develop an English and French decision aid (DA) for elderly people facing this decision, and to involve end-users in all phases of the development process. Methods A three-cycle design with involvement of end-users in Quebec. End-users were elderly people (n?=?4) caregivers of the elderly (n?=?5), health administrators involved in home-care service delivery or policy (n?=?6) and an interprofessional research team (n?=?19). Cycle 1: Decisional needs assessment and development of the first prototype based on existing tools and input from end-users; overview of reviews examining the impact of location of care on elderly people's health outcomes. Cycle 2: Usability testing with end-users, adaptation of prototype. Cycle 3: Refinement of the prototype with a linguist, graphic designer and end-users. The final prototype underwent readability testing and an International Patient Decision Aids (IPDAS) criteria compatibility assessment to verify minimal requirements for decision aids and was tested for usability by the elderly. ResultsCycle 1: We used the Ottawa Personal Decision Guide to design a first prototype. As the overview of reviews did not find definitive evidence regarding optimal locations of care for elderly people, we were not able to add evidence-based advantages and disadvantages to the guide. Cycle 2: Overall, the caregivers and health administrators who evaluated the prototype (n?=?10) were positive. In response to their suggestions, we deleted some elements (overview of pros, cons, and consequences of the options) that were necessary to qualify the tool as a DA and renamed it a "decision guide". Cycle 3: We developed French and English versions of the guide, readable at a primary school level. The elderly judged the guide as acceptable. Conclusion We developed a decision guide to support elderly people and their caregivers in decision making about location of care. This paper is one of few to report on a fully collaborative approach to decision guide development that involves end-users at every stage (caregivers and health administrators early on, the frail elderly in the final stages). The guide is currently being evaluated in a cluster randomized trial. Trial registration: NCT02244359.

Dataset Information

User stories as lightweight requirements for agile clinical decision support development.

Publications

User stories as lightweight requirements for agile clinical decision support development.

Similar Datasets

OmicsDI is part of the ELIXIR infrastructure

Tweets