<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "journalpublishing.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="2.0" xml:lang="en" article-type="research-article"><front><journal-meta><journal-id journal-id-type="nlm-ta">JMIR Hum Factors</journal-id><journal-id journal-id-type="publisher-id">humanfactors</journal-id><journal-id journal-id-type="index">6</journal-id><journal-title>JMIR Human Factors</journal-title><abbrev-journal-title>JMIR Hum Factors</abbrev-journal-title><issn pub-type="epub">2292-9495</issn><publisher><publisher-name>JMIR Publications</publisher-name><publisher-loc>Toronto, Canada</publisher-loc></publisher></journal-meta><article-meta><article-id pub-id-type="publisher-id">v12i1e60268</article-id><article-id pub-id-type="doi">10.2196/60268</article-id><article-categories><subj-group subj-group-type="heading"><subject>Original Paper</subject></subj-group></article-categories><title-group><article-title>Leveraging Dual Usability Methods to Evaluate Clinical Decision Support Among Patients With Traumatic Brain Injury: Mixed Methods Study</article-title></title-group><contrib-group><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>Rizvi</surname><given-names>Rubina F</given-names></name><degrees>MD, PhD</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Faisal</surname><given-names>Sameen</given-names></name><degrees>BS</degrees><xref ref-type="aff" rid="aff4">4</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Sussman</surname><given-names>Mark</given-names></name><degrees>MPAS</degrees><xref ref-type="aff" rid="aff5">5</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Mendlick</surname><given-names>Patricia</given-names></name><degrees>CMA</degrees><xref ref-type="aff" rid="aff6">6</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Brown</surname><given-names>Sam</given-names></name><degrees>BA</degrees><xref ref-type="aff" rid="aff6">6</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Lindemann</surname><given-names>Elizabeth</given-names></name><degrees>MHA</degrees><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="aff" rid="aff6">6</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Switzer</surname><given-names>Sean</given-names></name><degrees>DO</degrees><xref ref-type="aff" rid="aff6">6</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Melton</surname><given-names>Genevieve B</given-names></name><degrees>MD, PhD</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="aff" rid="aff3">3</xref><xref ref-type="aff" rid="aff6">6</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Tignanelli</surname><given-names>Christopher J</given-names></name><degrees>MD, MS</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff2">2</xref></contrib></contrib-group><aff id="aff1"><institution>Department of Surgery, University of Minnesota</institution><addr-line>420 Delaware Street South East, Mayo Mail Code 195</addr-line><addr-line>Minneapolis</addr-line><addr-line>MN</addr-line><country>United States</country></aff><aff id="aff2"><institution>Center For Learning Health System Sciences, University of Minnesota</institution><addr-line>Minneapolis</addr-line><addr-line>MN</addr-line><country>United States</country></aff><aff id="aff3"><institution>Institute for Health Informatics, University of Minnesota</institution><addr-line>Minneapolis</addr-line><addr-line>MN</addr-line><country>United States</country></aff><aff id="aff4"><institution>College of Biological Sciences, University of Minnesota</institution><addr-line>Minneapolis</addr-line><addr-line>MN</addr-line><country>United States</country></aff><aff id="aff5"><institution>Stanson Premier Inc</institution><addr-line>Charlotte</addr-line><addr-line>NC</addr-line><country>United States</country></aff><aff id="aff6"><institution>Fairview Health Services</institution><addr-line>Minneapolis</addr-line><addr-line>MN</addr-line><country>United States</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Kushniruk</surname><given-names>Andre</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Witteman</surname><given-names>Holly</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Quintana</surname><given-names>Yuri</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to  Rubina F Rizvi, MD, PhD, Department of Surgery, University of Minnesota, 420 Delaware Street South East, Mayo Mail Code 195, Minneapolis, MN, 55455, United States, 1 612-626-1999; <email>rizvi007@umn.edu</email></corresp></author-notes><pub-date pub-type="collection"><year>2025</year></pub-date><pub-date pub-type="epub"><day>30</day><month>7</month><year>2025</year></pub-date><volume>12</volume><elocation-id>e60268</elocation-id><history><date date-type="received"><day>06</day><month>05</month><year>2024</year></date><date date-type="rev-recd"><day>23</day><month>04</month><year>2025</year></date><date date-type="accepted"><day>12</day><month>05</month><year>2025</year></date></history><copyright-statement>&#x00A9; Rubina F Rizvi, Sameen Faisal, Mark Sussman, Patricia Mendlick, Sam Brown, Elizabeth Lindemann, Sean Switzer, Genevieve B Melton, Christopher J Tignanelli. Originally published in JMIR Human Factors (<ext-link ext-link-type="uri" xlink:href="https://humanfactors.jmir.org">https://humanfactors.jmir.org</ext-link>), 30.7.2025. </copyright-statement><copyright-year>2025</copyright-year><license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/"><p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (<ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link>), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Human Factors, is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://humanfactors.jmir.org">https://humanfactors.jmir.org</ext-link>, as well as this copyright and license information must be included.</p></license><self-uri xlink:type="simple" xlink:href="https://humanfactors.jmir.org/2025/1/e60268"/><abstract><sec><title>Background</title><p>Patients with traumatic brain injury are at an increased risk of developing venous thromboembolism. Clinical decision support systems (CDSSs) may improve the use of venous thromboembolism prophylaxis protocols, yet suffer from poor compliance among end users due to a lack of user-centered design.</p></sec><sec><title>Objective</title><p>The objective of this work was to improve the content, design, and workflow integration of a traumatic brain injury&#x2013;CDSS based on feedback from experts and end users.</p></sec><sec sec-type="methods"><title>Methods</title><p>The CDSS was evaluated leveraging a dual usability approach. A set of usability experts (n=3) and trauma providers (n=5) performed heuristic evaluations and usability testing by end users. Data was collected through a triangulation of methods and analyzed using qualitative (thematic) and quantitative (descriptive) analyses.</p></sec><sec sec-type="results"><title>Results</title><p>Among the 145 total issues identified across both methods, 66 issues were found to be unique. Of the 66, a total of 17 issues were found by heuristic evaluations, 43 by usability testing by end users, and 6 were found across both methods. Thematic analysis was conducted on the 66 unique issues, which were further assigned to themes and subsequent subthemes. We identified 13 unique themes. The 3 most prevalent themes of 66 issues were lack of supporting evidence (n=17, 26%), operational barriers arising from the test environment (n=11, 17%), formatting inconsistencies, and lack of following standards (n=8, 12%). The system&#x2019;s usability scale survey score was 77.5 (SD 16, 95% CI 57.6-97.4), interpreted as an acceptable or good usability range. The mean response score for Single Ease Questions for all tasks was 5.9 (SD 0.53).</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>Combining expert and end user&#x2013;driven usability evaluation methods identified a more comprehensive list of issues. This can facilitate the optimization of the traumatic brain injury&#x2013;CDSS, resulting in improved usability and care management.</p></sec></abstract><kwd-group><kwd>traumatic brain injury</kwd><kwd>venous thromboembolism</kwd><kwd>clinical decision support system (CDSS)</kwd><kwd>heuristic evaluations</kwd><kwd>end user&#x2013;based usability testing</kwd><kwd>decision support system</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><p>Traumatic brain injury is one of the leading causes of mortality and disability worldwide. In the United States alone, over 69,000 traumatic brain injury&#x2013;related deaths occurred in 2021 [<xref ref-type="bibr" rid="ref1">1</xref>]. Patients with traumatic brain injury are at an increased risk of developing complications secondary to venous thromboembolism [<xref ref-type="bibr" rid="ref2">2</xref>]. Fifty-four percent of patients with a traumatic brain injury will develop a venous thromboembolism in the absence of appropriate anticoagulation intervention [<xref ref-type="bibr" rid="ref3">3</xref>]. Despite the significance of timely venous thromboembolism prophylaxis administration, there has been a reluctance to implement anticoagulation in such patients, thus resulting in delays in timely intervention [<xref ref-type="bibr" rid="ref4">4</xref>-<xref ref-type="bibr" rid="ref7">7</xref>].</p><p>Optimal use of venous thromboembolism prophylaxis protocols manages the risk of thromboembolism with the competing risk of progression of intracranial bleeding in patients following trauma [<xref ref-type="bibr" rid="ref7">7</xref>]. However, there is variability in venous thromboembolism prophylaxis protocols across trauma centers [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. In an attempt to optimize thromboembolism prophylaxis for the patient, institutional implementation of anticoagulation protocols has been shown to improve clinical outcomes [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. To improve prophylactic anticoagulation of patients with traumatic brain injury without adversely affecting outcomes, integrating a clinical decision support system (CDSS) has emerged as an indispensable solution to supplement providers with evidence-based venous thromboembolism prevention guidelines [<xref ref-type="bibr" rid="ref9">9</xref>]. Existing literature cites improved patient outcomes when evidence-based practices are followed, along with improved compliance with these practices through the use of CDSSs [<xref ref-type="bibr" rid="ref10">10</xref>-<xref ref-type="bibr" rid="ref12">12</xref>].</p><p>CDSSs, whether stand-alone or integrated with an electronic health records system, are considered a monumental step forward in health care delivery as they serve as reliable and readily available aids to decision makers. CDSSs serve as a platform for clinicians by comparing individual patient data and integrating evidence-based recommendations into their daily workflow [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>]. When adhered to, these tools serve as an effective means of changing clinician behavior [<xref ref-type="bibr" rid="ref15">15</xref>-<xref ref-type="bibr" rid="ref17">17</xref>]. The use of CDSSs varies by purpose and context. However, the resultant benefits of CDSSs are found to consistently positively impact various elements of health care delivery for both patients and clinicians. For providers, it facilitates overall disease management by aiding complex decision-making that is mandated for accurate diagnosis, effective treatment, and efficient monitoring [<xref ref-type="bibr" rid="ref18">18</xref>]. For patients, the use of CDSSs leads to fewer errors, improved patient safety, improved care quality, and enhanced health outcomes [<xref ref-type="bibr" rid="ref19">19</xref>].</p><p>Despite these benefits, there are some risks and resistance to using CDSS [<xref ref-type="bibr" rid="ref19">19</xref>]. This includes but is not limited to cost-related challenges, alert fatigue, physicians&#x2019; autonomy and trust, liability issues, workflow disruptions, and usability challenges. The negative consequences of a tool to be developed and implemented could be mitigated if iterative evaluations are carried out earlier rather than in the later phase of the system development life cycle [<xref ref-type="bibr" rid="ref20">20</xref>]. Often, due to the additional resources required (both time and money), iterative evaluations are not prioritized before deployment in clinical practice. However, predeployment usability evaluation could potentially save time and money by preventing the need for critical changes after system implementation [<xref ref-type="bibr" rid="ref21">21</xref>]. This study highlights the criticality of early testing and engaging end users during the system development life cycle. Identifying and addressing users&#x2019; concerns around tool optimization and workflow integration should be considered an integral component when building, implementing, and maintaining a CDSS.</p><p>Lack of user-centered design, interoperability, and implementation barriers hinder the widespread adoption of a CDSS [<xref ref-type="bibr" rid="ref22">22</xref>-<xref ref-type="bibr" rid="ref24">24</xref>]. There is a need for robust usability studies to address existing barriers and optimize the functionality of the CDSS according to users&#x2019; needs. The objective of this study was to evaluate and optimize the usability of a traumatic brain injury CDSS integrated into a US Midwest American College of Surgeons&#x2013;verified trauma center. Usability issues in a traumatic brain injury-venous thromboembolism-CDSS were identified by leveraging a dual usability evaluation approach. We hypothesized that combining expert and end user&#x2013;driven methods of usability evaluation would help identify a wide range of unique issues specific to each method, along with common findings shared between the 2 methods.</p></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>Overview of Traumatic Brain Injury&#x2013;Venous Thromboembolism Prevention Guidelines</title><p>The traumatic brain injury&#x2013;CDSS delivers a patient-centered outcomes research guideline for venous thromboembolism prevention in patients with traumatic brain injury [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref25">25</xref>], which was centered around the modified Berne-Norwood criteria [<xref ref-type="bibr" rid="ref8">8</xref>]. Patients are categorized as being at low, moderate, or high risk for spontaneous progression of hemorrhage, with prophylactic treatment regimens tailored for each group, respectively. The traumatic brain injury&#x2013;CDSS is a modification of an original, natively developed COVID-19 CDSS logic model, which is currently translated to interoperable standards [<xref ref-type="bibr" rid="ref16">16</xref>] (<xref ref-type="fig" rid="figure1">Figure 1</xref>). We chose this model for two major reasons: (1) we have previous experience implementing the traumatic brain injury venous thromboembolism prevention guideline with success [<xref ref-type="bibr" rid="ref2">2</xref>], and (2) many of the data elements and artifacts (~80%) overlap with minimal additional mappings and technology build. The final CPG-FHIR (clinical practice guidelines on Fast Healthcare Interoperability Resources) COVID-19 CDSS included 108 data elements. The traumatic brain injury clinical practice guideline added 21 data elements specifically related to traumatic brain injury (eg, intracranial pressure monitoring, neurosurgical consultation, craniotomy, head computed tomography imaging, subdural hematoma, contusion, and Glasgow Coma Scale).</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>Clinical decision support system logic model for venous thromboembolism prevention among patients with traumatic brain injury. *S06: 2024 <italic>ICD-10-CM</italic> Diagnosis Code S06. CT: computed tomography; D/C: discontinue anticoagulation order; <italic>ICD-10-CM</italic>: <italic>International Statistical Classification of Diseases, Tenth Revision, Clinical Modification</italic>; ICP: intracranial pressure; IVC: inferior vena cava; S/P: status post; TBI: traumatic brain injury.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v12i1e60268_fig01.png"/></fig><p>Given the logic model, patients will enter the system by admission under predetermined diagnoses, generally falling under the traumatic brain injury category. Our target population is adult patients admitted with an acute traumatic brain injury, as defined by <italic>ICD-10-CM</italic> (<italic>International Statistical Classification of Diseases, Tenth Revision, Clinical Modification</italic>): S06.1-S06.9 or S06.A. Patients who died within 24 hours of hospital admission and patients documented as &#x201C;comfort cares&#x201D; during the first 72 hours of hospitalization will be excluded. Additionally, patients with a pre-existing venous thromboembolism or inferior vena cava filter at the time of admission and patients with a mechanical heart valve or ventricular assist device will be excluded from the final analysis.</p><p>The CDSS is provided in the subsequent 72 hours (dependent on risk stratification) and administered in the form of seven alerts (<xref ref-type="other" rid="box1">Textbox 1</xref>). <xref ref-type="other" rid="box1">Textbox 1</xref> provides descriptions of the seven alerts deployed at various points in time, stratified by level of risk.</p><boxed-text id="box1"><title> Description of seven alerts in traumatic brain injury&#x2013;clinical decision support system (CDSS).</title><list list-type="bullet"><list-item><p><bold>Initial assessment:</bold> provides initial risk stratification.</p></list-item><list-item><p><bold>Follow-up computed tomography (CT) scan alert:</bold> Guide proper timing of a follow-up CT head scan based on stratification</p></list-item></list><list list-type="bullet"><list-item><p><bold>Daily assessments:</bold> Track patient course and modify stratification in the event of critical conditions; that is, progression of bleed, placement of intracranial pressure (ICP) monitor, decompressive craniotomy, etc.</p></list-item><list-item><p><bold>Anticoagulation alert:</bold> Guides the health care provider to prescribe the correct dose of anticoagulation medication at the appropriate time, and not too soon.</p></list-item><list-item><p><bold>Discontinue anticoagulation order alert:</bold> Any attempt to prescribe anticoagulation before the appropriate clinical decision support system calculated time triggers an alert to discontinue the medication.</p></list-item><list-item><p><bold>Laboratory order alert:</bold> Prompts order of appropriate laboratories to monitor side effects of the anticoagulation medications, that is, Anti-Xa, platelets, etc.</p></list-item><list-item><p><bold>Laboratory level alerts:</bold> Additional prompts to monitor laboratory levels for appropriateness.</p></list-item></list></boxed-text></sec><sec id="s2-2"><title>Study Settings</title><p>Our foundational usability evaluation-related research work was conducted by a team of researchers from the University of Minnesota (UMN) and associated health systems, such as the M (Minnesota) Health Fairview and affiliated hospitals, which consisted of 9 state-verified trauma centers, including the flagship UMN as an American College of Surgeons&#x2013;verified level 2 trauma center. The usability evaluation methodology is reported in <xref ref-type="fig" rid="figure2">Figure 2</xref>.</p><fig position="float" id="figure2"><label>Figure 2.</label><caption><p>A process diagram of the methodology. MHFV: M (Minnesota) Health Fairview; TEST: test environment.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v12i1e60268_fig02.png"/></fig></sec><sec id="s2-3"><title>Data Collection</title><sec id="s2-3-1"><title>Expert-Based Usability Evaluations</title><p>Heuristic evaluations leveraging Nielsen 10 Usability Heuristics for User Interface Design were used iteratively during the whole development cycle, where issues identified were addressed sequentially [<xref ref-type="bibr" rid="ref26">26</xref>]. The initial round of heuristic evaluations was conducted on screenshots of the user interface that researchers independently evaluated.</p><p>Three experts with varied backgrounds, that is, a physician informatics or usability expert (RFR); a hospitalist with content and CDSS-related expertise (SS); and an undergraduate in neuroscience (SF) conducted the evaluation independently. We then had a debriefing session to walk through findings from individual users, removing any duplicates. Once we had a final, consolidated, clean list of unique issues, each evaluator did the severity ranking of each issue. A 0 to 4 rating scale was used to rate the severity of usability problems (0=I do not agree that this is a usability problem at all; 1=cosmetic problem only: need not be fixed unless extra time is available on project; 2=minor usability problem: fixing this should be given low priority; 3=major usability problem: important to fix, so should be given high priority; 4=usability catastrophe: imperative to fix this before product can be released) [<xref ref-type="bibr" rid="ref27">27</xref>]. While assigning the severity score to usability problems, 3 factors were considered: the frequency with which the problem occurs, the impact of the problem, and the persistence of the problem. The team reconvened in a severity scoring session where a scoring consensus was reached for each problem after mutual deliberations.</p></sec><sec id="s2-3-2"><title>End Users&#x2019; Based Usability Testing</title><p>End users&#x2019; based usability testing was conducted with actual end users, that is, trauma providers from M Health Fairview and affiliated hospital systems. Purposive sampling was used for recruitment purposes by sharing information about the traumatic brain injury&#x2013;CDSS usability study through emails, discussions during meetings, word of mouth, etc. Scenario&#x2013;based usability testing was done with individual end users along with our usability team comprised of up to 5 team members, including a moderator (n=1), facilitators&#x2013;information technology (IT) experts both from the MHVF and the vendors who helped with building (n=2&#x2010;3); and a note taker (n=1). Each session was conducted on Zoom (Zoom Inc.) and lasted up to 90 minutes.</p><p>In the scenario-based guided usability testing, we asked users to perform certain tasks on 3 unique test patients corresponding to 3 risk groups: low, medium, and high. Two to four scenarios were associated with each test patient for a total of 9 scenarios, which required each user to perform a few predefined, sequential tasks. Participants were asked to think out loud as they interacted with the traumatic brain injury&#x2013;CDSS in the Epic testing environment (Epic Inc). Once each scenario and relevant task were completed, participants were asked a few questions to elaborate on their experience and complete a single ease survey questionnaire (REDCap [Research Electronic Data Capture] Consortium; Vanderbilt University). At the end of the session, participants completed a System Usability Scale survey (SUS) [<xref ref-type="bibr" rid="ref28">28</xref>] and Single Ease Question (SEQ) [<xref ref-type="bibr" rid="ref29">29</xref>] and were asked to share their overall experience with the tool.</p></sec></sec><sec id="s2-4"><title>Building Test Patients and Testing in Epic Test Environment</title><p>Our team of experts was comprised of builders or IT specialists (SB, PM, and MS) and clinicians (SS, RFR, and CJT), who helped with building the 3 master test patients stratified by risk level (<xref ref-type="other" rid="box2">Textbox 2</xref>). Scenarios were generated by a team of clinicians having diverse sets of experiences (ie, CJT, a trauma surgeon, and project principal investigator, SS, a hospitalist, and RFR, a physician informaticist with user acceptance testing experiences) and builders or IT specialists (SB, PM, and MS) after in-depth discussions. The goal was to have scenarios that are commonly encountered and require trauma providers to perform certain high-priority tasks. Copies of the master patients were created to be used by each study participant..</p><boxed-text id="box2"><title> Patient risk stratification modified the Berne-Norwood criteria.</title><p><bold>Test patient # 1: low risk</bold></p><list list-type="bullet"><list-item><p>Subdural hematoma 2 mm.</p></list-item><list-item><p>No moderate or high-risk criteria.</p></list-item></list><p>Recommendation: initiate pharmacologic prophylaxis if repeat head computed tomography (CT) was stable at 24 hours.</p><p><bold>Test patient # 2: moderate risk</bold></p><list list-type="bullet"><list-item><p>Subdural or epidural hematoma &#x003E;8 mm.</p></list-item><list-item><p>Contusion or intraventricular hemorrhage &#x003E;2 cm.</p></list-item><list-item><p>Multiple contusions per lobe.</p></list-item><list-item><p>Subarachnoid hemorrhage with abnormal CT.</p></list-item><list-item><p>Evidence of progression at 24 hours.</p><p>Recommendation: initiate pharmacologic prophylaxis if the head CT was stable at 72 hours.</p></list-item></list><p><bold>Test patient # 3: high risk</bold></p><list list-type="bullet"><list-item><p>Placement of an intracranial pressure monitor, craniotomy, or both.</p></list-item><list-item><p>Evidence of progression at 72 hours.</p></list-item></list><p>Recommendation: consider placement of an inferior vena cava filter.</p></boxed-text><p>The purpose of the testing was to receive user feedback effectively and efficiently, ensuring that the testing context matches as much as possible with the user interactions in the real world. Leveraging the Epic test environment to create a simulated environment came with a few constraints described under limitations.</p></sec><sec id="s2-5"><title>Data Analysis</title><sec id="s2-5-1"><title>Overview</title><p>The respective data was analyzed both qualitatively and quantitatively as described.</p></sec><sec id="s2-5-2"><title>Qualitative-Thematic Analysis</title><p>We compiled all the issues identified by each method into 1 consolidated list. This included data collected through heuristic evaluations and usability testing by end users. First, a subset of the issue was coded independently by 2 individuals (RFR and SF) at a more granular level, and a codebook was generated after mutual agreement between both coders and applied to the full list of issues. Each analyst coded the rest of the transcripts for various usability problems, using the codebook generated earlier. We cataloged the lowest-level codes into higher-level subthemes and themes to gain a more holistic understanding of traumatic brain injury&#x2013;CDSS.</p></sec><sec id="s2-5-3"><title>Quantitative Analysis</title><p>The primary focus was on data collected from the SEQ survey and SUS. SEQ is an effective and efficient tool comprised of a single question asked immediately after task completion. SUS is the most widely used and accepted standardized tool to measure subjective usability. We performed descriptive analysis, reporting means and SDs.</p></sec></sec><sec id="s2-6"><title>Ethical Considerations</title><p>This component of the project is not a clinical trial. This study protocol (STUDY00017107) was submitted to the UMN Institutional Review Board and given the determination of &#x201C;exempt&#x201D; as secondary research for which consent is not required. The mixed methods investigation was determined as a &#x201C;not human research&#x201D; as a quality improvement activity. Signed and written informed consent was obtained to screen and audio record the session, with the speech-to-text transcription feature turned on. Each recording was saved on a secured and encrypted UMN device. Each participant later received a US $50 gift card for their participation.</p></sec></sec><sec id="s3" sec-type="results"><title>Results</title><sec id="s3-1"><title>End Users&#x2019; Characteristics</title><p>Five trauma providers participated in the individual usability testing session. The detailed characteristics are described in <xref ref-type="table" rid="table1">Table 1</xref>.</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>Demographics of participants.</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Characteristics</td><td align="left" valign="bottom">Trauma providers (n=5), n (%)</td></tr></thead><tbody><tr><td align="left" valign="top">Sex</td><td align="left" valign="top">&#x2003;</td></tr><tr><td align="left" valign="top">&#x2003;Male</td><td align="left" valign="top">2 (40)</td></tr><tr><td align="left" valign="top">&#x2003;Female</td><td align="left" valign="top">3 (60)</td></tr><tr><td align="left" valign="top">Role</td><td align="left" valign="top">&#x2003;</td></tr><tr><td align="left" valign="top">&#x2003;MD<sup><xref ref-type="table-fn" rid="table1fn1">a</xref></sup></td><td align="left" valign="top">4 (80)</td></tr><tr><td align="left" valign="top">&#x2003;APP<sup><xref ref-type="table-fn" rid="table1fn2">b</xref></sup></td><td align="left" valign="top">1 (20)</td></tr><tr><td align="left" valign="top">Specialty</td><td align="left" valign="top">&#x2003;</td></tr><tr><td align="left" valign="top">&#x2003;Trauma surgery</td><td align="left" valign="top">3 (60)</td></tr><tr><td align="left" valign="top">&#x2003;Neurosurgery</td><td align="left" valign="top">1 (20)</td></tr><tr><td align="left" valign="top">&#x2003;Neurocritical care</td><td align="left" valign="top">1 (20)</td></tr><tr><td align="left" valign="top">Comfort with technology</td><td align="left" valign="top">&#x2003;</td></tr><tr><td align="left" valign="top">&#x2003;Expert</td><td align="left" valign="top">4 (80)</td></tr><tr><td align="left" valign="top">&#x2003;Intermediate</td><td align="left" valign="top">1 (20)</td></tr></tbody></table><table-wrap-foot><fn id="table1fn1"><p><sup>a</sup>MD: medical doctor.</p></fn><fn id="table1fn2"><p><sup>b</sup>APP: advanced practice provider.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s3-2"><title>Usability-Related Findings From the 2 Methods</title><p>We identified a set of both common and unique issues using 2 methods: heuristic evaluation with experts (domain experts, ie, physicians, usability experts, or both) and usability testing with end users (the actual users).</p></sec><sec id="s3-3"><title>Findings From Heuristics Evaluation</title><p>Thirty-seven heuristic violations (23 unique and 14 duplicates) were identified by 3 experts. The results showed that 30% of possible heuristics were responsible for ~74% of all violations, the Pareto principle (<xref ref-type="fig" rid="figure3">Figure 3</xref>). Three heuristics that represented the most violations were (1) consistency and standards (n=8, 35%), (2) help and documentation (n=5, 22%), and (3) recognition rather than recall (n=4, 17%). Of 23 unique, we found cosmetic (n=6) and minor (n=17) issues only.</p><fig position="float" id="figure3"><label>Figure 3.</label><caption><p>The Pareto chart of heuristics principles violation and the severity ranking.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v12i1e60268_fig03.png"/></fig></sec><sec id="s3-4"><title>Findings From Usability Testing</title><p>We identified 108 issues (49 unique and 59 duplicates). Of 49 issues, we found cosmetic (n=6), minor (n=20), major (n=10), and catastrophic (n=2) issues. The remaining 11 were considered operational and not ranked. The mean responses to SEQ for all tasks were 5.9 (SD 0.53), ranked from 1 (very difficult) to 7 (very easy). The mean SUS score was 77.5 (SD 16) interpreted as an acceptable or good usability range (<xref ref-type="fig" rid="figure4">Figure 4</xref>). The 95% CI for the mean SUS score is 77.5 (95% CI 57.6&#x2010;97.4).</p><fig position="float" id="figure4"><label>Figure 4.</label><caption><p>The mean Systems Usability Scale score is interpreted as being within acceptable or good usability range  (adapted from Lewis and Sauro [<xref ref-type="bibr" rid="ref30">30</xref>], with permission from Jim Lewis). CDSS: clinical decision support system; NPS: net promoter score; SUS: Systems Usability Scale survey</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v12i1e60268_fig04.png"/></fig><p>Between the 2 methods, we identified a total of 145 issues, 66 of which were unique: 17 from heuristic evaluations, 43 from end users, and 6 common issues shared between both methods. Thematic analysis was performed on all unique issues, eliminating those arising from the constraints of thfsuye Epic test environment (66&#x2010;11=55).</p></sec><sec id="s3-5"><title>Ranking of Usability Issues</title><p>We ranked 55 unique usability issues on a severity scale from 0&#x2010;4, where 20% (n=11) were marked as cosmetic; 58% (n=32) were identified as minor; 18% (n=10) as major, and 4% (n=2) as catastrophic issues. We identified both cosmetic and minor issues through heuristic evaluations and usability testing with end users. However, severe and catastrophic issues were solely identified during the usability sessions with end users.</p></sec><sec id="s3-6"><title>Thematic Analysis</title><p>Thematic analysis was conducted on 66 unique issues identified through heuristic evaluations and usability testing. Eleven issues arising from Epic test environment constraints were eliminated. We identified 13 unique themes, including lack of supporting evidence, operational barriers arising from the test environment, formatting inconsistencies and lack of following standards, suboptimal data retrieval and display, lack of user control, lacking language clarity, order set-related suboptimal usability, language inconsistencies, best practice alert lacking patient-specific details, clinicians missing critical information or action, unfamiliarity with the full clinical context, infinite ordering loop leading to error, and having redundant options. The 3 most identified themes were lack of supporting evidence (n=17, 26%), operational barriers arising from the test environment (n=11, 17%), formatting inconsistencies, and lack of following standards (n=8, 12 %; <xref ref-type="table" rid="table2">Table 2</xref>).</p><table-wrap id="t2" position="float"><label>Table 2.</label><caption><p>Thematic analysis distribution.</p></caption><table id="table2" frame="hsides" rules="groups"><thead><tr><td align="left" valign="top">Theme</td><td align="left" valign="top">Unique issues (n=66)</td></tr></thead><tbody><tr><td align="left" valign="top">Lack of supporting evidence</td><td align="left" valign="top">17</td></tr><tr><td align="left" valign="top">Operational barriers arising from the test environment</td><td align="left" valign="top">11</td></tr><tr><td align="left" valign="top">Formatting inconsistencies and lack of following standards</td><td align="left" valign="top">8</td></tr><tr><td align="left" valign="top">Suboptimal data retrieval and display</td><td align="left" valign="top">6</td></tr><tr><td align="left" valign="top">Lack of user control</td><td align="left" valign="top">5</td></tr><tr><td align="left" valign="top">Lacking language clarity</td><td align="left" valign="top">4</td></tr><tr><td align="left" valign="top">Order-set related suboptimal usability</td><td align="left" valign="top">4</td></tr><tr><td align="left" valign="top">Language inconsistencies</td><td align="left" valign="top">3</td></tr><tr><td align="left" valign="top">Best Practice Advisory lacking patient-specific details</td><td align="left" valign="top">2</td></tr><tr><td align="left" valign="top">Clinicians missing critical information, action, or both</td><td align="left" valign="top">2</td></tr><tr><td align="left" valign="top">Unfamiliarity with the full clinical context</td><td align="left" valign="top">2</td></tr><tr><td align="left" valign="top">Infinite ordering loop leading to error</td><td align="left" valign="top">1</td></tr><tr><td align="left" valign="top">Redundant options</td><td align="left" valign="top">1</td></tr></tbody></table></table-wrap><p>Lack of supporting evidence refers to the end users&#x2019; request to integrate and access evidence-based citations throughout the CDSS. Of the 17 usability issues about evidence-based medicine, 14 were identified by end users and 3 were identified by experts. Examples include users disagreeing with threshold values and requesting evidence-based medicine citations, and users requesting the ability of the CDSS tool to be explained.</p><p>Formatting consistency and a lack of following standards refer to the system&#x2019;s ability to present information clearly and concisely, with a consistent interface to ensure easy readability for the user. Of the 8 usability issues about formatting consistency and standards, 2 were identified by end users, and 6 were identified by experts. Examples include inconsistent and difficult-to-read text usage, style, color, and sizes.</p><p>Suboptimal data retrieval and display refer to the system&#x2019;s ability to present information in a manner that reduces user cognitive burden by increasing smooth and efficient navigation by auto-populating data (such as laboratory results). Of the 6 usability issues about easy retrieval and optimal display, all were identified by end users. Examples include users requesting that laboratory or imaging values and administration time be incorporated into the CDSS.</p><p>Lack of user control refers to the flexible design of the system to ensure smooth interaction with the user. Of the 5 usability issues about user control, 2 were identified by end users and 3 were identified by experts. Examples include users requesting the ability to navigate away from the tool and forgiveness when using the CDSS.</p><p>Lacking language clarity refers to specifying verbiage to omit any confusion the user may have. Of the 4 usability issues about language clarity, 3 were identified by end users and 1 was identified by experts. Examples include specifying verbiage used throughout the tool and using specific phrases (ie, the use of &#x201C;active bleed&#x201D; vs &#x201C;new bleed&#x201D; may imply 2 different ideas).</p><p>Order set-related suboptimal usability refers to any suboptimal interactions the user may encounter when interacting with the order set. Of the 4 usability issues related to order set-related suboptimal usability, all were identified by end users. Examples include users requesting the tool display prompts regarding its functionality on a case-by-case basis and easy access to the admission order set.</p><p>Language inconsistencies refer to the consistent use of verbiage throughout the system. Of the 3 usability issues about language consistency, they were all identified by experts. Examples include discrepancies between verbiage used in the storyboard or title and the consistent use of terms implying the same definition (ie, either &#x201C;snooze&#x201D; or &#x201C;lockout time&#x201D; should be used, not both).</p><p>Best Practice Advisory (BPA) lacking patient-specific details refers to information that the system does not include, which users would prefer to be included. Of the 2 usability issues about BPA lacking patient-specific details, both were identified by end users. Examples include adding patient risk stratification to the BPA (ie, changing the tool to be more diagnostic) and including crucial patient-specific laboratory values.</p><p>Clinicians missing critical information refers to ensuring a system design that ensures easy readability for the clinician. Of the 2 usability issues about eliminating the chance of clinicians missing critical information, 1 was identified by end users and 1 was identified by experts. Examples include bolding information and making information more accessible to improve readability.</p><p>Unfamiliarity with the context refers to additional guidance presented to the clinician on the system. Of the 2 usability issues about unfamiliarity with context, both were identified by end users. Examples include ensuring proper education and introduction of the tool to clinicians to ensure it does not interrupt their workflow.</p><p>A redundant option refers to options already included as part of the system. Of the 1 usability issue about redundant options, it was identified by end users. Examples include omitting the &#x201C;already ordered complete&#x201D; button.</p><p>An infinite ordering loop leading to error refers to an infinite loop that occurs when using the system, during the beginning of its launch. It has since been resolved as of May 16, 2023. The 1 usability issue about the infinite ordering loop was identified by end users. Examples include users noting their warranted frustration with the ordering process.</p><p>Clinicians most often identified issues relating to the readily apparent integration of evidence-based medicine into the CDSS, recognizing a need for the use of citations and principles. Clinicians frequently noted how the CDSS might disrupt their workflow. For practical feasibility, request the integration of critical laboratory or imaging values and consistency in formatting throughout the tool to reduce user cognitive burden and ensure an efficient workflow. A compilation of unique usability issues categorized by theme is included in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>.</p></sec><sec id="s3-7"><title>Examples of Usability Modifications</title><p><xref ref-type="fig" rid="figure5">Figures 5</xref> and <xref ref-type="fig" rid="figure6">6</xref> present a few examples of modifications made based on insights from heuristic evaluations and usability testing by end users. The full list of identified usability issues is provided as a supplementary table.</p><fig position="float" id="figure5"><label>Figure 5.</label><caption><p>Examples of modifications.  TBI: traumatic brain injury. Copyright 2024 Epic Systems Corporation. Used with permission.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v12i1e60268_fig05.png"/></fig><fig position="float" id="figure6"><label>Figure 6.</label><caption><p>Examples of modifications. Images included with approval from Epic. CrCl: creatinine clearance; IP: inpatient; IVC: inferior vena cava; SL: service line; SCr: serum creatinine; T/PEDS: ADULT/PEDS; TBI: traumatic brain injury; VTE: venous thromboembolism. Copyright 2024 Epic Systems Corporation. Copyright 2024 Epic Systems Corporation. Used with permission.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v12i1e60268_fig06.png"/></fig></sec></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><sec id="s4-1"><title>Summary and Interpretation of Findings</title><p>Using a dual usability evaluation approach, namely expert-driven heuristic evaluation and end user&#x2013;driven usability testing, we identified a variety of both similar and unique issues across the traumatic brain injury venous thromboembolism CDSS. Of the 66 unique issues identified, the percentage attributed to each method was as follows: usability testing (43 issues, 65%), heuristic evaluations (17 issues, 26%), and both methods together (6 issues, 9%). Although the mean severity scores of the identified problems did not differ significantly between the 2 methods, issues that were ranked as severe and catastrophic were exclusively found through usability testing by the end users. The most common issues identified across both methods were related to a lack of supporting evidence, operational barriers, and formatting consistency or lack of following standards. Heuristic evaluations primarily identified issues related to formatting consistency or lack of following standards, user control, suboptimal language clarity, and consistency. In contrast, usability testing revealed a broader range of issues, where lack of supporting evidence, operational barriers, and suboptimal data retrieval and display were found to be the most common.</p><p>Using a combination of these 2 methods can identify a wider range of usability issues. This aligns with prior evidence suggesting that combining 2 methods of usability evaluation can facilitate the development of an optimal CDSS [<xref ref-type="bibr" rid="ref24">24</xref>]. We found that the majority of issues identified by usability testing were only discovered by end users, as compared to the experts. Although the experts identified fewer issues, they pinpointed more granular issues related to the layout, formatting, and consistency. In contrast, end users were more concerned with larger, more consequential issues, such as the lack of supporting evidence to increase their trust and confidence and fragmented workflow (primarily sending form test environment-related constraints). The findings from this study validate many of the claims made in previous comparisons of heuristic evaluations and usability testing [<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref32">32</xref>] such as heuristic evaluations being more cost-effective in terms of time and resources, and the ability of each method to identify distinct sets of usability issues with very small convergence rates (9% in our study). Heuristic evaluation findings were limited to identifying issues, whereas end users engaged in usability testing provided both strengths and weaknesses. For example, end users appreciated the clarity of the premier questionnaire (which covered the critical issue for risk profiling), as well as the straightforward alert verbiage. They also appreciated that the creatinine clearance value was apparent in the laboratory order results, eliminating the need to navigate to find it.</p></sec><sec id="s4-2"><title>Limitations</title><p>There are some limitations to this study. First, the usability evaluation was conducted at a single institution (M Health Fairview) using a single electronic health system (Epic). We had 5 clinicians participate in the end user testing. Several usability evaluation resources suggest that testing with 5 individuals is often considered appropriate for identifying usability issues, especially in qualitative analysis [<xref ref-type="bibr" rid="ref26">26</xref>]. However, a larger sample size would have strengthened the generalizability of the findings for quantitative analysis. Additionally, we did not examine whether participants&#x2019; amount of experience in their respective fields or their overall familiarity with digital technology influenced their insights.</p><p>Usability testing being conducted in the Epic test environment introduced some constraints that users had to adjust to, such as manually shortened refresh time frames to decrease testing time, which resulted in some unusual system behaviors. To simulate the passage of time, users had to right-click anywhere and hit &#x201C;refresh&#x201D; after responding to alerts. For the testing session, test results and imaging reports were simplified and appeared shorter in length. Consequently, the insights gathered during the simulation may not completely represent the realities and challenges faced by clinicians working in high-pressure environments, caring for their patients who are critically ill. Finally, the IT team faced challenges due to system constraints, as the systems were hardwired with limited ability for upgrades. We were, however, able to incorporate several build-related upgrades through close collaborations. We are still in the process of upgrading the tool based on the observations made during our evaluations and the feedback collected from end users since the tool went live.</p></sec><sec id="s4-3"><title>Implications for Future Directions</title><p>Concerning further CDSS implementation in different hospital settings, we plan to scale and assess the effectiveness of the CDSS for venous thromboembolism prophylaxis guidelines in patients with traumatic brain injury. This will consist of a stepped wedge hybrid effectiveness implementation trial to scale the CDSS across 9 sites within 4 trauma systems.</p></sec><sec id="s4-4"><title>Conclusions</title><p>By using dual usability evaluation methods, leveraging both expert and end user input during the early phases of system development in an iterative manner, we were able to identify a diverse range of usability issues. These issues varied in severity and were relevant to each evaluator based on their respective experience and role. Through conducting this study and our continued efforts to gather feedback from end users, we have been able to optimize the design and functionality of the traumatic brain injury&#x2013;CDSS to align more effectively with clinicians&#x2019; needs and workflow. This comprehensive approach has provided us with valuable insights in refining CDSS, ultimately improving its usability and effectiveness in clinical practice.</p></sec></sec></body><back><ack><p>We acknowledge M (Minnesota) Health Fairview information technology and data sciences, Vincent Peta, PhD, and the staff at Stanson (Stanson Premier Inc) for their support in these efforts. We are grateful to clinicians at the Minneapolis location who facilitated our running the pilot and enabling dissemination of the decision support solution. This research was supported by the Agency for Healthcare Research and Quality (AHRQ; R18HS028583, CJT and GBM-M [principal investigators], and the AHRQ and Patient-Centered Outcomes Research Institute [PCORI; grant P30HS029744], Minnesota-Learning Health System scholar program [MN-LHS], and the National Institutes of Health&#x2019;s [NIH] National Center for Advancing Translational Sciences [UM1TR004405, K12TR004373, T32HL007741]). Additional support for MN-LHS is provided by the University of Minnesota Office of Academic Clinical Affairs, Clinical Translational Science Institute, and Center for Learning Health System Sciences. The content is solely the responsibility of the authors and does not necessarily represent the official views of AHRQ, PCORI, NIH, or MN-LHS.</p></ack><fn-group><fn fn-type="conflict"><p>None declared.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">BPA</term><def><p>Best Practice Advisory</p></def></def-item><def-item><term id="abb2">CDSS</term><def><p>clinical decision support system</p></def></def-item><def-item><term id="abb3">CPG-FHIR</term><def><p>clinical practice guidelines on Fast Healthcare Interoperability Resources</p></def></def-item><def-item><term id="abb4"><italic>ICD-10-CM</italic></term><def><p><italic>International Statistical Classification of Diseases, Tenth Revision, Clinical Modification</italic></p></def></def-item><def-item><term id="abb5">IT</term><def><p>information technology</p></def></def-item><def-item><term id="abb6">SEQ</term><def><p>Single Ease Question</p></def></def-item><def-item><term id="abb7">SUS</term><def><p>Systems Usability Scale</p></def></def-item><def-item><term id="abb8">UMN</term><def><p>University of Minnesota</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="web"><article-title>Get the facts about TBI | concussion | traumatic brain injury</article-title><source>CDC Injury Center</source><year>2023</year><access-date>2025-06-21</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.cdc.gov/traumatic-brain-injury/data-research/facts-stats/?CDC_AAref_Val=https://www.cdc.gov/traumaticbraininjury/get_the_facts.html">https://www.cdc.gov/traumatic-brain-injury/data-research/facts-stats/?CDC_AAref_Val=https://www.cdc.gov/traumaticbraininjury/get_the_facts.html</ext-link></comment></nlm-citation></ref><ref id="ref2"><label>2</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Tignanelli</surname><given-names>CJ</given-names> </name><name name-style="western"><surname>Gipson</surname><given-names>J</given-names> </name><name name-style="western"><surname>Nguyen</surname><given-names>A</given-names> </name><etal/></person-group><article-title>Implementation of a prophylactic anticoagulation guideline for patients with traumatic brain injury</article-title><source>Jt Comm J Qual Patient Saf</source><year>2020</year><month>04</month><volume>46</volume><issue>4</issue><fpage>185</fpage><lpage>191</lpage><pub-id pub-id-type="doi">10.1016/j.jcjq.2019.11.007</pub-id><pub-id pub-id-type="medline">31899154</pub-id></nlm-citation></ref><ref id="ref3"><label>3</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Geerts</surname><given-names>WH</given-names> </name><name name-style="western"><surname>Code</surname><given-names>KI</given-names> </name><name name-style="western"><surname>Jay</surname><given-names>RM</given-names> </name><name name-style="western"><surname>Chen</surname><given-names>E</given-names> </name><name name-style="western"><surname>Szalai</surname><given-names>JP</given-names> </name></person-group><article-title>A prospective study of venous thromboembolism after major trauma</article-title><source>N Engl J Med</source><year>1994</year><month>12</month><day>15</day><volume>331</volume><issue>24</issue><fpage>1601</fpage><lpage>1606</lpage><pub-id pub-id-type="doi">10.1056/NEJM199412153312401</pub-id><pub-id pub-id-type="medline">7969340</pub-id></nlm-citation></ref><ref id="ref4"><label>4</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Norwood</surname><given-names>SH</given-names> </name><name name-style="western"><surname>McAuley</surname><given-names>CE</given-names> </name><name name-style="western"><surname>Berne</surname><given-names>JD</given-names> </name><etal/></person-group><article-title>Prospective evaluation of the safety of enoxaparin prophylaxis for venous thromboembolism in patients with intracranial hemorrhagic injuries</article-title><source>Arch Surg</source><year>2002</year><month>06</month><volume>137</volume><issue>6</issue><fpage>696</fpage><lpage>701</lpage><pub-id pub-id-type="doi">10.1001/archsurg.137.6.696</pub-id><pub-id pub-id-type="medline">12049541</pub-id></nlm-citation></ref><ref id="ref5"><label>5</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Wong</surname><given-names>H</given-names> </name><name name-style="western"><surname>Lovett</surname><given-names>N</given-names> </name><name name-style="western"><surname>Curry</surname><given-names>N</given-names> </name><name name-style="western"><surname>Shah</surname><given-names>K</given-names> </name><name name-style="western"><surname>Stanworth</surname><given-names>SJ</given-names> </name></person-group><article-title>Antithrombotics in trauma: management strategies in the older patients</article-title><source>J Blood Med</source><year>2017</year><volume>8</volume><fpage>165</fpage><lpage>174</lpage><pub-id pub-id-type="doi">10.2147/JBM.S125209</pub-id><pub-id pub-id-type="medline">29042825</pub-id></nlm-citation></ref><ref id="ref6"><label>6</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Phelan</surname><given-names>HA</given-names> </name></person-group><article-title>Pharmacologic venous thromboembolism prophylaxis after traumatic brain injury: a critical literature review</article-title><source>J Neurotrauma</source><year>2012</year><month>07</month><day>1</day><volume>29</volume><issue>10</issue><fpage>1821</fpage><lpage>1828</lpage><pub-id pub-id-type="doi">10.1089/neu.2012.2459</pub-id><pub-id pub-id-type="medline">22651698</pub-id></nlm-citation></ref><ref id="ref7"><label>7</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Yorkgitis</surname><given-names>BK</given-names> </name><name name-style="western"><surname>Berndtson</surname><given-names>AE</given-names> </name><name name-style="western"><surname>Cross</surname><given-names>A</given-names> </name><etal/></person-group><article-title>American Association for the Surgery of Trauma/American College of Surgeons-Committee on Trauma Clinical Protocol for inpatient venous thromboembolism prophylaxis after trauma</article-title><source>J Trauma Acute Care Surg</source><year>2022</year><month>03</month><day>1</day><volume>92</volume><issue>3</issue><fpage>597</fpage><lpage>604</lpage><pub-id pub-id-type="doi">10.1097/TA.0000000000003475</pub-id><pub-id pub-id-type="medline">34797813</pub-id></nlm-citation></ref><ref id="ref8"><label>8</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Pastorek</surname><given-names>RA</given-names> </name><name name-style="western"><surname>Cripps</surname><given-names>MW</given-names> </name><name name-style="western"><surname>Bernstein</surname><given-names>IH</given-names> </name><etal/></person-group><article-title>The Parkland Protocol&#x2019;s modified Berne-Norwood criteria predict two tiers of risk for traumatic brain injury progression</article-title><source>J Neurotrauma</source><year>2014</year><month>10</month><day>15</day><volume>31</volume><issue>20</issue><fpage>1737</fpage><lpage>1743</lpage><pub-id pub-id-type="doi">10.1089/neu.2014.3366</pub-id><pub-id pub-id-type="medline">24945196</pub-id></nlm-citation></ref><ref id="ref9"><label>9</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Haut</surname><given-names>ER</given-names> </name><name name-style="western"><surname>Lau</surname><given-names>BD</given-names> </name><name name-style="western"><surname>Kraenzlin</surname><given-names>FS</given-names> </name><etal/></person-group><article-title>Improved prophylaxis and decreased rates of preventable harm with the use of a mandatory computerized clinical decision support tool for prophylaxis for venous thromboembolism in trauma</article-title><source>Arch Surg</source><year>2012</year><month>10</month><volume>147</volume><issue>10</issue><fpage>901</fpage><lpage>907</lpage><pub-id pub-id-type="doi">10.1001/archsurg.2012.2024</pub-id><pub-id pub-id-type="medline">23070407</pub-id></nlm-citation></ref><ref id="ref10"><label>10</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Macheel</surname><given-names>C</given-names> </name><name name-style="western"><surname>Reicks</surname><given-names>P</given-names> </name><name name-style="western"><surname>Sybrant</surname><given-names>C</given-names> </name><etal/></person-group><article-title>Clinical decision support intervention for rib fracture treatment</article-title><source>J Am Coll Surg</source><year>2020</year><month>08</month><volume>231</volume><issue>2</issue><fpage>249</fpage><lpage>256</lpage><pub-id pub-id-type="doi">10.1016/j.jamcollsurg.2020.04.023</pub-id><pub-id pub-id-type="medline">32360959</pub-id></nlm-citation></ref><ref id="ref11"><label>11</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Moja</surname><given-names>L</given-names> </name><name name-style="western"><surname>Friz</surname><given-names>HP</given-names> </name><name name-style="western"><surname>Capobussi</surname><given-names>M</given-names> </name><etal/></person-group><article-title>Effectiveness of a hospital-based computerized decision support system on clinician recommendations and patient outcomes: a randomized clinical trial</article-title><source>JAMA Netw Open</source><year>2019</year><month>12</month><day>2</day><volume>2</volume><issue>12</issue><fpage>e1917094</fpage><pub-id pub-id-type="doi">10.1001/jamanetworkopen.2019.17094</pub-id><pub-id pub-id-type="medline">31825499</pub-id></nlm-citation></ref><ref id="ref12"><label>12</label><nlm-citation citation-type="web"><article-title>Clinical decision support</article-title><source>Agency for Healthcare Research and Quality</source><year>2022</year><access-date>2025-06-21</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.ahrq.gov/cpi/about/otherwebsites/clinical-decision-support/index.html">https://www.ahrq.gov/cpi/about/otherwebsites/clinical-decision-support/index.html</ext-link></comment></nlm-citation></ref><ref id="ref13"><label>13</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Loftus</surname><given-names>TJ</given-names> </name><name name-style="western"><surname>Altieri</surname><given-names>MS</given-names> </name><name name-style="western"><surname>Balch</surname><given-names>JA</given-names> </name><etal/></person-group><article-title>Artificial intelligence-enabled decision support in surgery: state-of-the-art and future directions</article-title><source>Ann Surg</source><year>2023</year><month>07</month><day>1</day><volume>278</volume><issue>1</issue><fpage>51</fpage><lpage>58</lpage><pub-id pub-id-type="doi">10.1097/SLA.0000000000005853</pub-id><pub-id pub-id-type="medline">36942574</pub-id></nlm-citation></ref><ref id="ref14"><label>14</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Nguyen</surname><given-names>AS</given-names> </name><name name-style="western"><surname>Yang</surname><given-names>S</given-names> </name><name name-style="western"><surname>Thielen</surname><given-names>BV</given-names> </name><etal/></person-group><article-title>Clinical decision support intervention and time to imaging in older patients with traumatic brain injury</article-title><source>J Am Coll Surg</source><year>2020</year><month>09</month><volume>231</volume><issue>3</issue><fpage>361</fpage><lpage>367</lpage><pub-id pub-id-type="doi">10.1016/j.jamcollsurg.2020.05.023</pub-id><pub-id pub-id-type="medline">32561447</pub-id></nlm-citation></ref><ref id="ref15"><label>15</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Durieux</surname><given-names>P</given-names> </name><name name-style="western"><surname>Nizard</surname><given-names>R</given-names> </name><name name-style="western"><surname>Ravaud</surname><given-names>P</given-names> </name><name name-style="western"><surname>Mounier</surname><given-names>N</given-names> </name><name name-style="western"><surname>Lepage</surname><given-names>E</given-names> </name></person-group><article-title>A clinical decision support system for prevention of venous thromboembolism: effect on physician behavior</article-title><source>JAMA</source><year>2000</year><month>06</month><day>7</day><volume>283</volume><issue>21</issue><fpage>2816</fpage><lpage>2821</lpage><pub-id pub-id-type="doi">10.1001/jama.283.21.2816</pub-id><pub-id pub-id-type="medline">10838650</pub-id></nlm-citation></ref><ref id="ref16"><label>16</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Shah</surname><given-names>S</given-names> </name><name name-style="western"><surname>Switzer</surname><given-names>S</given-names> </name><name name-style="western"><surname>Shippee</surname><given-names>ND</given-names> </name><etal/></person-group><article-title>Implementation of an anticoagulation practice guideline for COVID-19 via a clinical decision support system in a large academic health system and its evaluation: observational study</article-title><source>JMIR Med Inform</source><year>2021</year><month>11</month><day>18</day><volume>9</volume><issue>11</issue><fpage>e30743</fpage><pub-id pub-id-type="doi">10.2196/30743</pub-id><pub-id pub-id-type="medline">34550900</pub-id></nlm-citation></ref><ref id="ref17"><label>17</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Kawamoto</surname><given-names>K</given-names> </name><name name-style="western"><surname>Lobach</surname><given-names>DF</given-names> </name></person-group><article-title>Clinical decision support provided within physician order entry systems: a systematic review of features effective for changing clinician behavior</article-title><source>AMIA Annu Symp Proc</source><year>2003</year><volume>2003</volume><fpage>361</fpage><lpage>365</lpage><pub-id pub-id-type="medline">14728195</pub-id></nlm-citation></ref><ref id="ref18"><label>18</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Grechuta</surname><given-names>K</given-names> </name><name name-style="western"><surname>Shokouh</surname><given-names>P</given-names> </name><name name-style="western"><surname>Alhussein</surname><given-names>A</given-names> </name><etal/></person-group><article-title>Benefits of clinical decision support systems for the management of noncommunicable chronic diseases: targeted literature review</article-title><source>Interact J Med Res</source><year>2024</year><month>11</month><day>27</day><volume>13</volume><issue>1</issue><fpage>e58036</fpage><pub-id pub-id-type="doi">10.2196/58036</pub-id><pub-id pub-id-type="medline">39602213</pub-id></nlm-citation></ref><ref id="ref19"><label>19</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Sutton</surname><given-names>RT</given-names> </name><name name-style="western"><surname>Pincock</surname><given-names>D</given-names> </name><name name-style="western"><surname>Baumgart</surname><given-names>DC</given-names> </name><name name-style="western"><surname>Sadowski</surname><given-names>DC</given-names> </name><name name-style="western"><surname>Fedorak</surname><given-names>RN</given-names> </name><name name-style="western"><surname>Kroeker</surname><given-names>KI</given-names> </name></person-group><article-title>An overview of clinical decision support systems: benefits, risks, and strategies for success</article-title><source>NPJ Digit Med</source><year>2020</year><volume>3</volume><issue>1</issue><fpage>17</fpage><pub-id pub-id-type="doi">10.1038/s41746-020-0221-y</pub-id><pub-id pub-id-type="medline">32047862</pub-id></nlm-citation></ref><ref id="ref20"><label>20</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Cho</surname><given-names>H</given-names> </name><name name-style="western"><surname>Keenan</surname><given-names>G</given-names> </name><name name-style="western"><surname>Madandola</surname><given-names>OO</given-names> </name><etal/></person-group><article-title>Assessing the usability of a clinical decision support system: heuristic evaluation</article-title><source>JMIR Hum Factors</source><year>2022</year><month>05</month><day>10</day><volume>9</volume><issue>2</issue><fpage>e31758</fpage><pub-id pub-id-type="doi">10.2196/31758</pub-id><pub-id pub-id-type="medline">35536613</pub-id></nlm-citation></ref><ref id="ref21"><label>21</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Corrao</surname><given-names>NJ</given-names> </name><name name-style="western"><surname>Robinson</surname><given-names>AG</given-names> </name><name name-style="western"><surname>Swiernik</surname><given-names>MA</given-names> </name><name name-style="western"><surname>Naeim</surname><given-names>A</given-names> </name></person-group><article-title>Importance of testing for usability when selecting and implementing an electronic health or medical record system</article-title><source>J Oncol Pract</source><year>2010</year><month>05</month><volume>6</volume><issue>3</issue><fpage>120</fpage><lpage>124</lpage><pub-id pub-id-type="doi">10.1200/JOP.200017</pub-id><pub-id pub-id-type="medline">20808553</pub-id></nlm-citation></ref><ref id="ref22"><label>22</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Liberati</surname><given-names>EG</given-names> </name><name name-style="western"><surname>Ruggiero</surname><given-names>F</given-names> </name><name name-style="western"><surname>Galuppo</surname><given-names>L</given-names> </name><etal/></person-group><article-title>What hinders the uptake of computerized decision support systems in hospitals? A qualitative study and framework for implementation</article-title><source>Implement Sci</source><year>2017</year><month>09</month><day>15</day><volume>12</volume><issue>1</issue><fpage>113</fpage><pub-id pub-id-type="doi">10.1186/s13012-017-0644-2</pub-id><pub-id pub-id-type="medline">28915822</pub-id></nlm-citation></ref><ref id="ref23"><label>23</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Khairat</surname><given-names>S</given-names> </name><name name-style="western"><surname>Marc</surname><given-names>D</given-names> </name><name name-style="western"><surname>Crosby</surname><given-names>W</given-names> </name><name name-style="western"><surname>Al Sanousi</surname><given-names>A</given-names> </name></person-group><article-title>Reasons for physicians not adopting clinical decision support systems: critical analysis</article-title><source>JMIR Med Inform</source><year>2018</year><month>04</month><day>18</day><volume>6</volume><issue>2</issue><fpage>e24</fpage><pub-id pub-id-type="doi">10.2196/medinform.8912</pub-id><pub-id pub-id-type="medline">29669706</pub-id></nlm-citation></ref><ref id="ref24"><label>24</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Jones</surname><given-names>EK</given-names> </name><name name-style="western"><surname>Banks</surname><given-names>A</given-names> </name><name name-style="western"><surname>Melton</surname><given-names>GB</given-names> </name><name name-style="western"><surname>Porta</surname><given-names>CM</given-names> </name><name name-style="western"><surname>Tignanelli</surname><given-names>CJ</given-names> </name></person-group><article-title>Barriers to and facilitators for acceptance of comprehensive clinical decision support system-driven care maps for patients with thoracic trauma: interview study among health care providers and nurses</article-title><source>JMIR Hum Factors</source><year>2022</year><month>03</month><day>16</day><volume>9</volume><issue>1</issue><fpage>e29019</fpage><pub-id pub-id-type="doi">10.2196/29019</pub-id><pub-id pub-id-type="medline">35293873</pub-id></nlm-citation></ref><ref id="ref25"><label>25</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Rappold</surname><given-names>JF</given-names> </name><name name-style="western"><surname>Sheppard</surname><given-names>FR</given-names> </name><name name-style="western"><surname>Carmichael Ii</surname><given-names>SP</given-names> </name><etal/></person-group><article-title>Venous thromboembolism prophylaxis in the trauma intensive care unit: an American Association for the Surgery of Trauma Critical Care Committee Clinical Consensus Document</article-title><source>Trauma Surg Acute Care Open</source><year>2021</year><volume>6</volume><issue>1</issue><fpage>e000643</fpage><pub-id pub-id-type="doi">10.1136/tsaco-2020-000643</pub-id><pub-id pub-id-type="medline">33718615</pub-id></nlm-citation></ref><ref id="ref26"><label>26</label><nlm-citation citation-type="web"><article-title>10 usability heuristics for user interface design</article-title><source>Nielsen Norman Group</source><year>2023</year><access-date>2025-06-21</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.nngroup.com/articles/ten-usability-heuristics">https://www.nngroup.com/articles/ten-usability-heuristics</ext-link></comment></nlm-citation></ref><ref id="ref27"><label>27</label><nlm-citation citation-type="web"><article-title>Severity ratings for usability problems: article by Jakob Nielsen</article-title><source>Nielsen Norman Group</source><year>2023</year><access-date>2025-06-21</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.nngroup.com/articles/how-to-rate-the-severity-of-usability-problems">https://www.nngroup.com/articles/how-to-rate-the-severity-of-usability-problems</ext-link></comment></nlm-citation></ref><ref id="ref28"><label>28</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Lewis</surname><given-names>JR</given-names> </name></person-group><article-title>The System Usability Scale: past, present, and future</article-title><source>Int J Hum-Comput Interact</source><year>2018</year><month>07</month><day>3</day><volume>34</volume><issue>7</issue><fpage>577</fpage><lpage>590</lpage><pub-id pub-id-type="doi">10.1080/10447318.2018.1455307</pub-id></nlm-citation></ref><ref id="ref29"><label>29</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Sauro</surname><given-names>J</given-names> </name></person-group><article-title>10 things to know about the Single Ease Question (SEQ)</article-title><source>Measuring U</source><year>2012</year><access-date>2025-06-21</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://measuringu.com/seq10/">https://measuringu.com/seq10/</ext-link></comment></nlm-citation></ref><ref id="ref30"><label>30</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Lewis</surname><given-names>J</given-names> </name><name name-style="western"><surname>Sauro</surname><given-names>J</given-names> </name></person-group><article-title>How to estimate SUS using the UX-lite</article-title><source>Measuring U</source><year>2021</year><access-date>2025-07-30</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://measuringu.com/how-to-estimate-sus-with-ux-lite/">https://measuringu.com/how-to-estimate-sus-with-ux-lite/</ext-link></comment></nlm-citation></ref><ref id="ref31"><label>31</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Bailey</surname><given-names>RW</given-names> </name><name name-style="western"><surname>Allan</surname><given-names>RW</given-names> </name><name name-style="western"><surname>Raiello</surname><given-names>P</given-names> </name></person-group><article-title>Usability testing vs. heuristic evaluation: a head-to-head comparison</article-title><source>Proc Hum Factors Soc Ann Meet</source><year>1992</year><month>10</month><volume>36</volume><issue>4</issue><fpage>409</fpage><lpage>413</lpage><pub-id pub-id-type="doi">10.1177/154193129203600431</pub-id></nlm-citation></ref><ref id="ref32"><label>32</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Desurvire</surname><given-names>HW</given-names> </name></person-group><article-title>Faster, cheaper!! Are usability inspection methods as effective as empirical testing?</article-title><source>Usability Inspection Methods</source><year>1994</year><publisher-name>John Wiley &#x0026; Sons, Inc</publisher-name><fpage>173</fpage><lpage>202</lpage></nlm-citation></ref></ref-list><app-group><supplementary-material id="app1"><label>Multimedia Appendix 1</label><p>Usability issues by theme.</p><media xlink:href="humanfactors_v12i1e60268_app1.docx" xlink:title="DOCX File, 26 KB"/></supplementary-material></app-group></back></article>