<?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">v13i1e78736</article-id><article-id pub-id-type="doi">10.2196/78736</article-id><article-categories><subj-group subj-group-type="heading"><subject>Original Paper</subject></subj-group></article-categories><title-group><article-title>Evaluating a Shared Decision Support Tool for Pediatric Cardiopulmonary Arrest: Mixed Methods Usability Study</article-title></title-group><contrib-group><contrib contrib-type="author"><name name-style="western"><surname>Rajic</surname><given-names>Ana</given-names></name><degrees>MS</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Kayne Olanka</surname><given-names>Sharleen</given-names></name><degrees>MS</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Generelli</surname><given-names>Marco</given-names></name><degrees>MS</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Davidson</surname><given-names>Jennifer</given-names></name><degrees>RNCS</degrees><xref ref-type="aff" rid="aff3">3</xref><xref ref-type="aff" rid="aff4">4</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Lin</surname><given-names>Yiqun</given-names></name><degrees>MD, MHSc, PhD</degrees><xref ref-type="aff" rid="aff4">4</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Kang</surname><given-names>Ryan</given-names></name><degrees>MSc</degrees><xref ref-type="aff" rid="aff5">5</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Kim</surname><given-names>Kangsoo</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff5">5</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Rebours</surname><given-names>Pierre-Louis</given-names></name><xref ref-type="aff" rid="aff6">6</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Ibrahim</surname><given-names>Marc</given-names></name><xref ref-type="aff" rid="aff6">6</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Duncan</surname><given-names>Donovan</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff7">7</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Manzano</surname><given-names>Sergio</given-names></name><degrees>Prof Dr</degrees><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="aff" rid="aff8">8</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Cheng</surname><given-names>Adam</given-names></name><degrees>Prof Dr</degrees><xref ref-type="aff" rid="aff3">3</xref><xref ref-type="aff" rid="aff4">4</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>De Masi</surname><given-names>Alexandre</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff8">8</xref></contrib><contrib contrib-type="author" corresp="yes" equal-contrib="yes"><name name-style="western"><surname>Siebert</surname><given-names>Johan N</given-names></name><degrees>MD, PD</degrees><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="aff" rid="aff8">8</xref><xref ref-type="fn" rid="equal-contrib1">*</xref></contrib><contrib contrib-type="author" equal-contrib="yes"><name name-style="western"><surname>Ehrler</surname><given-names>Frederic</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff6">6</xref><xref ref-type="aff" rid="aff8">8</xref><xref ref-type="fn" rid="equal-contrib1">*</xref></contrib></contrib-group><aff id="aff1"><institution>Educational Technologies and Learning Sciences (TECFA), Faculty of Psychology and Educational Sciences, University of Geneva</institution><addr-line>Geneva</addr-line><country>Switzerland</country></aff><aff id="aff2"><institution>Department of Pediatric Emergency Medicine, Geneva Children's Hospital, Geneva University Hospitals</institution><addr-line>47 Avenue de la Roseraie</addr-line><addr-line>Geneva</addr-line><country>Switzerland</country></aff><aff id="aff3"><institution>Departments of Pediatrics and Emergency Medicine, Cumming School of Medicine, University of Calgary</institution><addr-line>Calgary</addr-line><addr-line>AB</addr-line><country>Canada</country></aff><aff id="aff4"><institution>KidSIM-ASPIRE Simulation Research Program, Alberta Children's Hospital, University of Calgary</institution><addr-line>Calgary</addr-line><addr-line>AB</addr-line><country>Canada</country></aff><aff id="aff5"><institution>Department of Electrical and Software Engineering, Schulich School of Engineering, University of Calgary</institution><addr-line>Calgary</addr-line><addr-line>AB</addr-line><country>Canada</country></aff><aff id="aff6"><institution>Division of Computer Sciences, Diagnostic Department, Geneva University Hospitals</institution><addr-line>Geneva</addr-line><country>Switzerland</country></aff><aff id="aff7"><institution>Pediatric Intensive Care Unit, Alberta Children's Hospital, University of Calgary</institution><addr-line>Calgary</addr-line><addr-line>AB</addr-line><country>Canada</country></aff><aff id="aff8"><institution>Faculty of Medicine, University of Geneva</institution><addr-line>Geneva</addr-line><country>Switzerland</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>Cahill</surname><given-names>Brian</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Or</surname><given-names>Calvin</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Noordergraaf</surname><given-names>Gerrit J</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Johan N Siebert, MD, PD, Department of Pediatric Emergency Medicine, Geneva Children's Hospital, Geneva University Hospitals, 47 Avenue de la Roseraie, Geneva, 1211, Switzerland, 41 0 22 372 40 72; <email>johan.siebert@hug.ch</email></corresp><fn fn-type="equal" id="equal-contrib1"><label>*</label><p>these authors contributed equally</p></fn></author-notes><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>28</day><month>4</month><year>2026</year></pub-date><volume>13</volume><elocation-id>e78736</elocation-id><history><date date-type="received"><day>08</day><month>06</month><year>2025</year></date><date date-type="rev-recd"><day>02</day><month>12</month><year>2025</year></date><date date-type="accepted"><day>14</day><month>12</month><year>2025</year></date></history><copyright-statement>&#x00A9; Ana Rajic, Sharleen Kayne Olanka, Marco Generelli, Jennifer Davidson, Yiqun Lin, Ryan Kang, Kangsoo Kim, Pierre-Louis Rebours, Marc Ibrahim, Donovan Duncan, Sergio Manzano, Adam Cheng, Alexandre De Masi, Johan N Siebert, Frederic Ehrler. Originally published in JMIR Human Factors (<ext-link ext-link-type="uri" xlink:href="https://humanfactors.jmir.org">https://humanfactors.jmir.org</ext-link>), 28.4.2026. </copyright-statement><copyright-year>2026</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/2026/1/e78736"/><abstract><sec><title>Background</title><p>Effective team communication is critical in pediatric cardiopulmonary arrest management, where delays or miscommunication can jeopardize survival. TeamScreen, a web-based interface displayed on a large screen, was developed to enhance cardiopulmonary resuscitation (CPR) by providing real-time visualization of clinical data and resuscitation steps aligned with the American Heart Association pediatric advanced life support algorithms.</p></sec><sec><title>Objective</title><p>This study evaluated the usability of the TeamScreen Figma prototype, evaluating how efficiently and accurately experienced emergency physicians and nurses retrieved critical information during a simulated pediatric in-hospital cardiac arrest scenario. Although no strict time constraints were imposed, participants were instructed to perform the tasks as spontaneously and as quickly as possible.</p></sec><sec sec-type="methods"><title>Methods</title><p>Usability testing involved 20 pediatric emergency physicians and nurses with varied CPR experience. Participants performed 21 information retrieval tasks within a simulated pediatric cardiac arrest scenario (shockable rhythm). The data collected included audio-video recordings via the think-aloud method and participant responses to the Post-Study System Usability Questionnaire (PSSUQ) version 3 and a posttest survey. Effectiveness, efficiency, and satisfaction were measured by task completion rates, time-on-task metrics, and PSSUQ scores, respectively. Think-aloud data were analyzed for usability issues using Nielsen Norman Group&#x2019;s rating scale and Bastien and Scapin&#x2019;s ergonomic criteria.</p></sec><sec sec-type="results"><title>Results</title><p>Five physicians and 15 nurses achieved a mean task success rate of 81.19% (SD 16.87%), with a mean completion time of 8.13 (SD 7.07) seconds, calculated across all 21 tasks and all participants. PSSUQ scores reflected high satisfaction (mean 2.40 [SD 1.24] of 7.00; the lower the better), notably for information clarity and system utility. Qualitative analyses identified 16 usability issues, of which 5 were deemed major, primarily involving information visibility, navigation, and density, highlighting areas for interface and workflow enhancement.</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>The usability evaluation confirmed TeamScreen&#x2019;s potential to improve real-time information access during pediatric CPR, with high task success and satisfaction scores supporting its role in aiding decision-making. Challenges with visibility, navigation, and information density require further refinement. These findings will guide improvements and inform the design of multicenter trials to assess TeamScreen&#x2019;s efficacy in simulation-based resuscitation settings.</p></sec></abstract><kwd-group><kwd>cardiopulmonary resuscitation</kwd><kwd>pediatric emergency medicine</kwd><kwd>decision support systems</kwd><kwd>clinical</kwd><kwd>digital health</kwd><kwd>user-computer interface</kwd><kwd>health information technology</kwd><kwd>medical informatics applications</kwd><kwd>usability testing</kwd><kwd>simulation training</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><sec id="s1-1"><title>Context and Problem Statement</title><p>In-hospital pediatric cardiac arrests (IHCA), although rare, require immediate, coordinated response from resuscitation teams under intense pressure to provide guideline-compliant clinical care [<xref ref-type="bibr" rid="ref1">1</xref>]. Standardized protocols, such as the American Heart Association pediatric advanced life support (PALS) guidelines, emphasize uniform responses [<xref ref-type="bibr" rid="ref2">2</xref>], yet adherence remains suboptimal, with frequent deviations from recommended timing of defibrillation and drug administration, errors in dosing, and omissions of key steps in both real and simulated pediatric cardiac arrest scenarios [<xref ref-type="bibr" rid="ref3">3</xref>-<xref ref-type="bibr" rid="ref6">6</xref>]. These deviations are strongly influenced by human factors such as high cognitive load, stress, impaired decision-making, communication breakdowns, and challenges in maintaining team situational awareness and a shared mental model during complex emergencies [<xref ref-type="bibr" rid="ref4">4</xref>]. These lapses compromise quality of care and survival rates [<xref ref-type="bibr" rid="ref7">7</xref>]. As a result, there is increasing interest in tools that support team cognition and real-time guideline adherence during pediatric cardiopulmonary resuscitation (CPR).</p><p>Digital cognitive aids and decision support systems have emerged as promising approaches to mitigate these problems. In adult and mixed emergency settings, cognitive aids and electronic decision support tools have been associated with fewer errors and better adherence to resuscitation algorithms in simulated IHCA [<xref ref-type="bibr" rid="ref8">8</xref>-<xref ref-type="bibr" rid="ref11">11</xref>]. In pediatrics, few are purpose-built for real-time use in resuscitation [<xref ref-type="bibr" rid="ref12">12</xref>]. Tablet-based apps were developed specifically to support pediatric cardiac arrest management and showed good usability in high-fidelity simulation with reduced deviations from guideline recommendations [<xref ref-type="bibr" rid="ref13">13</xref>-<xref ref-type="bibr" rid="ref15">15</xref>]. A recent systematic review of cognitive aids in resuscitation similarly concluded that cognitive aids tend to reduce deviations from guidelines and improve resuscitation performance in simulated settings across adult and pediatric populations [<xref ref-type="bibr" rid="ref16">16</xref>]. However, most existing systems are designed as single-user, handheld interfaces that primarily support the team leader, rather than functioning as shared, team-centered displays that make time-critical information visible to the entire resuscitation team in real time.</p><p>Only a few technological solutions have been conceived as large situation displays to enhance team communication and situational awareness during emergency resuscitations. Pilot work in emergency departments has suggested that dedicated situation displays can facilitate teamwork, communication, and perceived situational awareness among resuscitation teams [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref18">18</xref>]. More recently, an interactive, large-screen clinical decision display designed for team-wide viewing has been evaluated and shown to improve adherence to guideline time intervals in simulated advanced cardiac life support [<xref ref-type="bibr" rid="ref8">8</xref>]. Despite these advances, pediatric-specific evidence for team-centered digital decision support during IHCA remains limited, and there is a need for tools explicitly designed around the information needs and workflows of pediatric resuscitation teams.</p><p>To address these limitations, we developed Interconnected and Focused Mobile Applications on Patient Care Environment (InterFACE), a suite of interconnected digital tools (<xref ref-type="fig" rid="figure1">Figure 1</xref>) designed to enhance team coordination and PALS adherence during pediatric CPR [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref20">20</xref>]. Building on an earlier prototype [<xref ref-type="bibr" rid="ref15">15</xref>] that demonstrated improvements in defibrillation timing and adherence to resuscitation algorithms but also highlighted risks of cognitive overload, we refined the system into an updated concept. This system integrates role-specific, interconnected digital tools&#x2014;TeamScreen, Guiding Pad (a tablet app), and augmented reality (AR) headsets [<xref ref-type="bibr" rid="ref21">21</xref>]&#x2014;to standardize care, reduce variability, and enhance CPR quality [<xref ref-type="bibr" rid="ref22">22</xref>]. TeamScreen provides real-time resuscitation oversight, with shared access to drug and shock dose calculations and PALS workflows to support the entire team [<xref ref-type="bibr" rid="ref20">20</xref>]. Developed iteratively with multidisciplinary input from 2 pediatric emergency departments, it addresses prior shortcomings and aligns with calls for innovative resuscitation aids [<xref ref-type="bibr" rid="ref16">16</xref>].</p><p>The design and evaluation of InterFACE-AR followed human factors and usability engineering recommendations for high-risk medical technologies. Regulatory guidance from the US Food and Drug Administration on applying human factors and usability engineering to medical devices emphasizes structured processes, identifying critical tasks, conducting formative evaluations, and performing summative usability testing to minimize use-related risks [<xref ref-type="bibr" rid="ref23">23</xref>]. Usability research in health information technology further supports the use of task-based testing and think-aloud methods as core, user-centered approaches to uncover interaction problems in complex interfaces [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]. In this context, this study focuses specifically on evaluating the usability of the updated TeamScreen interface during a simulated pediatric IHCA scenario, as an essential step before broader assessments of its impact on team performance and clinical outcomes.</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>Components of Interconnected and Focused Mobile Applications on Patient Care Environment&#x2013;augmented reality (InterFACE-AR). The system integrates multiple digital tools to support pediatric resuscitation teams. The Guiding Pad (tablet), used by the charting nurse, captures patient data and completed tasks, distributing real-time information to role-specific interfaces. The TeamScreen (web-based app displayed on a large screen) provides a centralized overview of the resuscitation algorithm, patient data, and team tasks for the entire resuscitation team. Augmented reality (AR) headsets (HoloLens 2) deliver targeted, real-time guidance to the physician leader (for physician-led tasks) and the medication nurse (for medication preparation and administration).</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v13i1e78736_fig01.png"/></fig></sec><sec id="s1-2"><title>Objective</title><p>This study aimed to evaluate the usability of the TeamScreen app in supporting resuscitation teams during pediatric IHCA management. By assessing the prototype&#x2019;s strengths and limitations, we sought to identify potential usability challenges and propose targeted improvements. The insights gathered were intended to inform the refinement of TeamScreen ahead of its full-scale clinical deployment and to contribute to the broader development of digital tools aimed at enhancing team performance and adherence to resuscitation guidelines.</p></sec></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>Study Design</title><p>The usability of the TeamScreen app was assessed through a scenario-based information retrieval evaluation, combining both quantitative and qualitative methods. Multitask quantitative and qualitative usability metrics were used and are described in detail in subsequent sections. Usability was defined, according to ISO 9241&#x2010;210, as &#x201C;the extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency, and satisfaction in a specified context of use&#x201D; [<xref ref-type="bibr" rid="ref26">26</xref>]. The usability of a digital tool can be assessed by how effectively and completely users are able to perform key tasks aligned with its core functionalities. In contrast, poor usability often results in reduced task efficiency, incomplete goal achievement, or even abandonment of the technology [<xref ref-type="bibr" rid="ref27">27</xref>]. Effectiveness was measured by task completion rates. Efficiency was evaluated through time-on-task metrics. User satisfaction was assessed using the Post-Study System Usability Questionnaire (PSSUQ) version 3 [<xref ref-type="bibr" rid="ref28">28</xref>] and a custom posttest evaluation questionnaire. In addition, think-aloud discussions were recorded verbatim and analyzed to extract key user insights and perceptions throughout the sessions.</p></sec><sec id="s2-2"><title>TeamScreen App Overview: A Core Component of InterFACE-AR</title><p>TeamScreen is a web-based app designed to centralize and display, in real time, critical information related to the patient&#x2019;s condition and resuscitation progress to support adherence to PALS algorithms during CPR. Displayed on a 75-inch wall-mounted screen in the resuscitation room, it provides resuscitation teams with a clear, shared overview of clinical status and required actions, aligned with PALS algorithms. This dynamic interface offers a visual overview of key data such as patient information (eg, weight, pulse presence, cardiac rhythm, and ventilation status), intervention timelines, upcoming clinical tasks, and medication dosing details without requiring direct user interaction. Instead, it relies on input from the charting nurse via the Guiding Pad, a tablet app that dynamically records interventions tailored to the patient&#x2019;s status. TeamScreen is part of the broader InterFACE-AR suite [<xref ref-type="bibr" rid="ref22">22</xref>], named for its AR foundation, which also includes AR headsets (HoloLens 2, Microsoft Corp), worn by the team leader and medication nurse [<xref ref-type="bibr" rid="ref21">21</xref>]. These deliver role-specific guidance via mixed reality, an advanced form of AR that&#x2014;unlike standard overlays&#x2014;enables interactive 3D holograms anchored in the environment [<xref ref-type="bibr" rid="ref29">29</xref>], to support clinical decision-making and medication preparation. The usability testing approach mirrored this role distribution, reflecting real-world dynamics where the Guiding Pad feeds data to TeamScreen for team-wide visibility. These tools collectively aim to improve situational awareness, communication, and adherence to PALS guidelines during IHCA, ensuring more efficient and guideline-compliant interventions. The TeamScreen prototype used in this study replicated all core functionalities of the current InterFACE-AR TeamScreen module, including the algorithm flow, task lists, timers, and weight-based drug and shock displays, but it was operated as a stand-alone simulated interface that was not technically connected to the AR headsets or live clinical systems. The Guiding Pad and AR headset components will be described and evaluated in separate studies.</p></sec><sec id="s2-3"><title>Participants and Setting</title><sec id="s2-3-1"><title>Inclusion Criteria and Recruitment</title><p>The inclusion criteria comprised physicians and nurses working in the Pediatric Emergency Department of the Geneva University Hospitals in Switzerland; fluent in French at a C1 level; and with prior experience in pediatric resuscitation, gained through real clinical practice, simulation training, or both. Individuals involved in the development of the InterFACE project were excluded from the study to avoid bias.</p><p>Sample size was established at 20 participants. This number is consistent with established guidelines for usability testing in high-risk, domain-specific systems, where 15 to 20 participants are generally considered sufficient to identify the majority of critical usability issues. This recommendation is supported by prior work in the field, particularly in the context of summative evaluations of medical technologies [<xref ref-type="bibr" rid="ref30">30</xref>]. The evaluation framework focused on interactions between the user, the task, and the system, intentionally excluding the user&#x2019;s actual clinical environment from the assessment [<xref ref-type="bibr" rid="ref31">31</xref>]. Recruitment was carried out by 2 senior attending physicians in pediatric emergency medicine (SM and JNS).</p></sec><sec id="s2-3-2"><title>Ethical Considerations</title><p>The study received ethical approval from the Geneva Cantonal Research Ethics Committee (reference Req-2023&#x2010;00162). All participants received an information sheet detailing the study&#x2019;s objectives and provided written informed consent before participating. Participants could opt out at any time without providing a reason and without any consequences. Participants received no compensation for their participation. All data were anonymized to ensure confidentiality. Explicit consent was obtained from participants to use their image for publication.</p></sec><sec id="s2-3-3"><title>Test Setting</title><p>The usability evaluation was conducted in a conference room, equipped with a prototype of the TeamScreen system displayed on a 75-inch wall-mounted Samsung Neo QLED screen (model QE75QN90). This standardized setup was designed to simulate real clinical environment and enable technical data collection. Participants stood 2.7 meters from the screen, with a table placed in front of it to simulate a resuscitation bed (<xref ref-type="fig" rid="figure2">Figure 2</xref>). This conference room layout (screen position, distance, and table simulating the resuscitation bed) was chosen to approximate a pediatric emergency department resuscitation bay, with the TeamScreen acting as the central &#x201C;wall monitor&#x201D; around which the simulated scenario unfolded. Testing sessions were conducted by 3 examiners (ADM, SO, and AR), each responsible for different aspects of the evaluation. SO operated the Guiding Pad connected to the TeamScreen and acted as the charting nurse, simulating real-time input of clinical actions to drive the system forward in alignment with the usability tasks presented to participants. AR facilitated the sessions, administered instructions, and guided the participants through the PALS algorithm, questionnaires, and posttest survey. All verbal responses and think-aloud reflections were recorded using lapel microphones. Data collection tools included a demographic questionnaire, the PSSUQ version 3, and a custom posttest survey, all administered digitally via Microsoft Forms, with responses stored in real time.</p><fig position="float" id="figure2"><label>Figure 2.</label><caption><p>Usability test setting with TeamScreen. Two health care professionals interact with TeamScreen, displayed on a 75-inch wall-mounted screen, during the usability testing session. The participants stand at a standardized distance while engaging in scenario-based tasks to assess system usability. The interface provides real-time guidance on pediatric advanced life support resuscitation algorithms. The test environment simulates a clinical setting, with technical equipment used for data collection and analysis.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v13i1e78736_fig02.png"/></fig></sec></sec><sec id="s2-4"><title>Test Procedure</title><sec id="s2-4-1"><title>Procedure</title><p>Each session involved the same screen-based simulated pediatric resuscitation scenario, featuring a child aged 8 years (25 kg) who had sustained an electrification injury and subsequently developed a witnessed IHCA in an emergency department resuscitation bay. The initial rhythm was ventricular fibrillation/pulseless ventricular tachycardia, and the scenario was structured to follow the typical progression of a case of shockable IHCA requiring high-quality CPR, repeated rhythm checks, defibrillation, and drug administration. No manikin was used, and participants were not required to perform physical life-saving interventions; the focus was exclusively on interacting with the TeamScreen. Using TeamScreen as the shared &#x201C;wall display&#x201D; for the resuscitation, participants were required to complete a series of information retrieval tasks, covering key aspects of CPR resuscitation such as pulse assessment (no pulse), defibrillation, medication management (epinephrine, amiodarone, and succinylcholine as an intubation drug option), and cardiac rhythm identification (ventricular fibrillation/pulseless ventricular tachycardia). The scenario included several critical steps that had to be completed before return of spontaneous circulation (ROSC) could be achieved, such as recognizing the absence of a pulse, initiating chest compressions, performing defibrillation, and delivering the appropriate medications at the correct timing. The objective was to evaluate participants&#x2019; ability to locate and interpret critical information displayed on the TeamScreen interface without prior training. The usability testing followed a standardized protocol:</p><list list-type="order"><list-item><p>Participant onboarding: upon arrival, participants were provided with an information sheet, and they signed an informed consent form. The study&#x2019;s purpose and procedure were explained, after which the participants completed a demographic questionnaire assessing their experience and expertise in pediatric resuscitation.</p></list-item><list-item><p>Equipment setup: participants were fitted with Tobii Pro Glasses 3 (Tobii AB) for eye-tracking analysis, and lapel microphones were used to record verbal feedback throughout the session.</p></list-item><list-item><p>Familiarization: clinicians who had been involved in the conception or technical development of the InterFACE-AR system were excluded. The remaining participants had not previously used the TeamScreen prototype and were exposed to it only through a short, standardized briefing immediately before the usability session. They were briefly presented with a static TeamScreen prototype (<xref ref-type="fig" rid="figure3">Figure 3</xref>) via FIGMA (Figma Inc) and asked to describe their observations. This phase served to ease their interaction with the interface before engaging in task execution.</p></list-item><list-item><p>Scenario execution and task completion: participants proceeded with the simulated IHCA scenario, performing 21 sequential information retrieval tasks (<xref ref-type="table" rid="table1">Table 1</xref>) using the think-aloud method [<xref ref-type="bibr" rid="ref32">32</xref>]. Each task corresponded to a TeamScreen display, with additional information progressively introduced as the session advanced. These tasks were designed to assess comprehension and eye navigation on the interface. Participants were asked to verbalize their thought processes while retrieving information, guided by 1 examiner (AR), who intervened only if a participant struggled to reach a final answer. Task success, completion time, and time required for task presentation were recorded.</p></list-item><list-item><p>Posttest debriefing: upon completion, participants filled out the PSSUQ version 3; the responses were used to assess their satisfaction with TeamScreen. A semistructured interview was conducted to gather qualitative feedback regarding usability, strengths, and areas for improvement.</p></list-item><list-item><p>Closing and follow-up: participants were thanked for their time, informed about the next steps of the project, and invited to share any additional comments or suggestions.</p></list-item></list><fig position="float" id="figure3"><label>Figure 3.</label><caption><p>TeamScreen prototype display during a simulated pediatric in-hospital cardiac arrest, showing the cardiopulmonary resuscitation (CPR) algorithm (left) and the current and upcoming tasks (center), with timer boxes for CPR cycles and epinephrine administration displayed at the bottom. The right-hand panel displays completed tasks and the medication list with weight-based dosing. Succinylcholine is included as one of several selectable intubation drugs to test navigation and selection within the interface and should not be interpreted as a recommendation for its use during ongoing cardiac arrest.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v13i1e78736_fig03.png"/></fig></sec><sec id="s2-4-2"><title>Scenario and Tasks</title><p>The IHCA scenario was standardized and tailored to each participant&#x2019;s professional role. Pediatric emergency physicians were assigned the role of team leader, and nurses were assigned the role of medication nurse. The scenario was co-developed by 2 pediatric emergency physicians (SM and JNS) and designed in parallel with 21 information retrieval tasks (<xref ref-type="table" rid="table1">Table 1</xref>) predefined by 3 examiners (ADM, SO, and AR), ensuring alignment between task execution and the corresponding TeamScreen displays.</p><p>Within the broader InterFACE-AR concept, the complete system is intended to provide individualized, role-specific decision support to the team leader and medication nurse through optically see-through AR headsets and to display a dynamic road map for patient care on TeamScreen, both components being coordinated via the Guiding Pad tablet app. This human factors study focuses solely on the usability of the TeamScreen app across a series of information retrieval tasks (<xref ref-type="table" rid="table1">Table 1</xref>). In the full system, weight-based medication doses are automatically calculated from the patient&#x2019;s weight and displayed as final numeric values on the AR headset of the medication nurse. In this TeamScreen-only prototype, dose-related panels (eg, tasks 8 and 16) primarily served to test whether participants could correctly locate where this information could be accessed rather than to verify the arithmetic itself. Similarly, the medication menu including succinylcholine (step 19) among other intubation drugs was configured to assess navigation and selection within the interface rather than as a recommendation for succinylcholine use during IHCA. An updated TeamScreen view reflecting the current implementation is provided in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>.</p><p>Participants individually performed the 21 information retrieval tasks while progressing through a scripted walk-through simulated pediatric IHCA scenario, with clinical information and TeamScreen prototype screens presented in a structured, stepwise fashion. Each of the 20 participants completed the full scenario once, resulting in 20 standardized runs of the case.</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>List of information retrieval tasks.</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">No.</td><td align="left" valign="bottom">Task name</td><td align="left" valign="bottom">Information retrieval task</td><td align="left" valign="bottom">Expected answer</td></tr></thead><tbody><tr><td align="left" valign="top">1</td><td align="left" valign="top">Define weight I</td><td align="left" valign="top">Locate the weight entry area</td><td align="left" valign="top">Locate the weight entry area; no weight displayed<sup><xref ref-type="table-fn" rid="table1fn1">a</xref></sup></td></tr><tr><td align="left" valign="top">2</td><td align="left" valign="top">Pulse check</td><td align="left" valign="top">Does the patient have a pulse?</td><td align="left" valign="top">Not indicated; it is in progress</td></tr><tr><td align="left" valign="top">3</td><td align="left" valign="top">Resuscitation time</td><td align="left" valign="top">How long has the resuscitation been going on?</td><td align="left" valign="top">15 s</td></tr><tr><td align="left" valign="top">4</td><td align="left" valign="top">Define weight II</td><td align="left" valign="top">What is the patient&#x2019;s weight?</td><td align="left" valign="top">25 kg</td></tr><tr><td align="left" valign="top">5</td><td align="left" valign="top">CPR<sup><xref ref-type="table-fn" rid="table1fn2">b</xref></sup> status</td><td align="left" valign="top">What is the status of CPR?</td><td align="left" valign="top">CPR has started; CPR was done once; CPR was performed for 10 s</td></tr><tr><td align="left" valign="top">6</td><td align="left" valign="top">Cardiac rhythm</td><td align="left" valign="top">What is the cardiac rhythm?</td><td align="left" valign="top">VF<sup><xref ref-type="table-fn" rid="table1fn3">c</xref></sup>; VF/pVT<sup><xref ref-type="table-fn" rid="table1fn4">d</xref></sup></td></tr><tr><td align="left" valign="top">7</td><td align="left" valign="top">Shocks given</td><td align="left" valign="top">How many shocks were delivered?</td><td align="left" valign="top">1 (algorithm or completed tasks)</td></tr><tr><td align="left" valign="top">8</td><td align="left" valign="top">Medication status I</td><td align="left" valign="top">Can any medication be administered?</td><td align="left" valign="top">Yes (epinephrine)</td></tr><tr><td align="left" valign="top">9</td><td align="left" valign="top">CPR time</td><td align="left" valign="top">How much CPR time is left to do?</td><td align="left" valign="top">1 min</td></tr><tr><td align="left" valign="top">10</td><td align="left" valign="top">Secondary tasks</td><td align="left" valign="top">Which secondary task is proposed?</td><td align="left" valign="top">Prepare the second person for CPR</td></tr><tr><td align="left" valign="top">11</td><td align="left" valign="top">Next step</td><td align="left" valign="top">What is the next step?</td><td align="left" valign="top">Check the pulse; identify the cardiac rhythm; switch the CPR provider</td></tr><tr><td align="left" valign="top">12</td><td align="left" valign="top">A/B<sup><xref ref-type="table-fn" rid="table1fn5">e</xref></sup> problem assessment</td><td align="left" valign="top">Which tasks have been carried out to resolve the A/B problems?</td><td align="left" valign="top">ETT<sup><xref ref-type="table-fn" rid="table1fn6">f</xref></sup> intubation and repositioning</td></tr><tr><td align="left" valign="top">13</td><td align="left" valign="top">Intubation time</td><td align="left" valign="top">At what time did the intubation take place?</td><td align="left" valign="top">HH:MM<sup><xref ref-type="table-fn" rid="table1fn7">g</xref></sup></td></tr><tr><td align="left" valign="top">14</td><td align="left" valign="top">Tasks in progress</td><td align="left" valign="top">Which tasks need to be done now?</td><td align="left" valign="top">Resume CPR for 2 min; administer epinephrine 0.01 mg/kg (0.1 mL/kg)</td></tr><tr><td align="left" valign="top">15</td><td align="left" valign="top">Shock time</td><td align="left" valign="top">At what time was the shock delivered?</td><td align="left" valign="top">HH:MM</td></tr><tr><td align="left" valign="top">16</td><td align="left" valign="top">Medication status II</td><td align="left" valign="top">Which medication was administered?</td><td align="left" valign="top">Epinephrine</td></tr><tr><td align="left" valign="top">17</td><td align="left" valign="top">Epinephrine time</td><td align="left" valign="top">How long until epinephrine must be administered again?</td><td align="left" valign="top">3 min 25 s</td></tr><tr><td align="left" valign="top">18</td><td align="left" valign="top">&#x201C;Other tasks&#x201D; section status</td><td align="left" valign="top">A team member placed an intraosseous line. Where is this information displayed?</td><td align="left" valign="top">Under &#x201C;Completed Tasks&#x201D;/&#x201C;Other tasks&#x201D;</td></tr><tr><td align="left" valign="top">19</td><td align="left" valign="top">Medication status</td><td align="left" valign="top">Which medication is being prepared?</td><td align="left" valign="top">Succinylcholine</td></tr><tr><td align="left" valign="top">20</td><td align="left" valign="top">Reversible causes</td><td align="left" valign="top">In the &#x201C;Tasks in progress&#x201D; area, the message &#x201C;Treat the reversible causes&#x201D; appeared. Where can you find help to recall the list of reversible causes?</td><td align="left" valign="top">Below the algorithm</td></tr><tr><td align="left" valign="top">21</td><td align="left" valign="top">Patient status: general understanding</td><td align="left" valign="top">What is the patient&#x2019;s current condition?</td><td align="left" valign="top">No longer in cardiac arrest; moved to ROSC<sup><xref ref-type="table-fn" rid="table1fn8">h</xref></sup>; ABCDE<sup><xref ref-type="table-fn" rid="table1fn9">i</xref></sup> assessment</td></tr></tbody></table><table-wrap-foot><fn id="table1fn1"><p><sup>a</sup>Success was defined as correctly identifying the relevant interface element rather than as giving a numeric answer.</p></fn><fn id="table1fn2"><p><sup>b</sup>CPR: cardiopulmonary resuscitation.</p></fn><fn id="table1fn3"><p><sup>c</sup>VF: ventricular fibrillation.</p></fn><fn id="table1fn4"><p><sup>d</sup>pVT: pulseless ventricular tachycardia.</p></fn><fn id="table1fn5"><p><sup>e</sup>A/B: airway and breathing.</p></fn><fn id="table1fn6"><p><sup>f</sup>ETT: endotracheal tube.</p></fn><fn id="table1fn7"><p><sup>g</sup>HH:MM: hours and minutes.</p></fn><fn id="table1fn8"><p><sup>h</sup>ROSC: return of spontaneous circulation.</p></fn><fn id="table1fn9"><p><sup>i</sup>ABCDE: airway, breathing, circulation, disability, exposure.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s2-4-3"><title>Outcome Measures</title><sec id="s2-4-3-1"><title>Quantitative Data</title><sec id="s2-4-3-1-1"><title>Performance Metrics</title><p>Participant performance was evaluated using 2 key efficiency metrics:</p><list list-type="bullet"><list-item><p>Task success rate: tasks were classified as successful if the participant provided the expected answer (<xref ref-type="table" rid="table1">Table 1</xref>), either immediately or after a correction, as long as the final response was correct. Incorrect or incomplete responses were categorized as task failures.</p></list-item><list-item><p>Time on task: This metric measured the average time (in seconds) taken to complete each task, starting from the end of the examiner&#x2019;s instructions until the participant provided a final answer (<xref ref-type="table" rid="table1">Table 1</xref>). Since participants had no prior training with TeamScreen, response time was not used as a determinant of task success.</p></list-item></list></sec><sec id="s2-4-3-1-2"><title>User Satisfaction</title><p>User satisfaction was measured after completion of the tasks using the PSSUQ version 3 [<xref ref-type="bibr" rid="ref28">28</xref>], a 16-item instrument rated on a 7-point Likert scale (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>), rated from 1 (&#x201C;strongly agree&#x201D;) to 7 (&#x201C;strongly disagree&#x201D;), in addition to a &#x201C;not applicable&#x201D; (N/A) option. Items 7 and 8, related to error messages and error recovery, were not applicable in this study because the TeamScreen prototype did not implement system error messaging or recovery workflows. These items were therefore marked &#x201C;not applicable&#x201D; and omitted from score calculations, in accordance with published PSSUQ scoring guidance [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref33">33</xref>], with overall scores computed as the mean of the remaining answered items.</p><p>The PSSUQ yields an overall usability score and scores on 3 subscales&#x2014;system usefulness (items 1&#x2010;6), information quality (items 7&#x2010;12), and interface quality (items 13&#x2010;15)&#x2014;with lower scores indicating greater satisfaction in each category. Based on 21 studies including 210 participants, the benchmark means reported by Lewis [<xref ref-type="bibr" rid="ref34">34</xref>] provided the reference values for interpreting the PSSUQ scores: overall 2.82, system usefulness 2.80, information quality 3.02, and interface quality 2.49. This comparison with published benchmark values was purely descriptive. No inferential statistical testing was performed against these reference data. Better performance and satisfaction are reflected in lower PSSUQ scores (closer to 1).</p></sec></sec></sec></sec><sec id="s2-5"><title>Qualitative Data</title><sec id="s2-5-1"><title>Error Analysis</title><p>All usability challenges encountered during task completion were systematically recorded and categorized using ergonomic criteria for human-computer interface evaluation [<xref ref-type="bibr" rid="ref35">35</xref>]. Each usability issue was assigned a severity rating based on Nielsen Norman Group&#x2019;s rating scale [<xref ref-type="bibr" rid="ref36">36</xref>], assessing its impact on user performance and experience. Severity level 3 indicates a major usability problem that significantly hinders task execution, forcing users to find alternative solutions and requiring urgent corrective action. A severity level 2 represents a minor usability issue that may cause frustration but does not prevent task completion, warranting moderate priority for resolution. A severity level 1 is considered a cosmetic issue, affecting only aesthetics, with no impact on usability, requiring resolution only if time allows. Finally, a severity level of 0 is considered as not usability related. Findings from the severity assessment informed targeted design refinements for TeamScreen&#x2019;s next iteration. The identified issues were addressed in a recently conducted multicenter simulation study, for which a manuscript is currently in preparation.</p></sec><sec id="s2-5-2"><title>Think-Aloud Verbal Feedback</title><p>During testing, participants were encouraged to verbalize their thought processes while interacting with TeamScreen. These verbal reflections were analyzed to identify usability issues, inform content and design refinements, and improve system design for better real-world applicability.</p></sec><sec id="s2-5-3"><title>Posttest Survey Feedback</title><p>To complement quantitative findings, qualitative feedback was collected via a standardized set of posttest interview questions (<xref ref-type="table" rid="table2">Table 2</xref>), ensuring consistency in data collection.</p><p>Responses provided a holistic understanding of user experience. Findings were systematically analyzed to refine TeamScreen&#x2019;s interface and functionality, ensuring alignment with user expectations and clinical workflows.</p><table-wrap id="t2" position="float"><label>Table 2.</label><caption><p>Posttest survey.</p></caption><table id="table2" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Question</td><td align="left" valign="bottom">Type of question</td><td align="left" valign="bottom">Choice provided</td></tr></thead><tbody><tr><td align="left" valign="top">Display understanding</td><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>1. What is your overall impression of the display?</td><td align="left" valign="top">Open-ended question</td><td align="left" valign="top">&#x2014;<sup><xref ref-type="table-fn" rid="table2fn1">a</xref></sup></td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>2. What did you find easy to understand in this display?</td><td align="left" valign="top">Open-ended question</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>3. What did you find difficult to understand in this display?</td><td align="left" valign="top">Open-ended question</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>4. What do you think of the readability of the information (eg, font size, colors, etc)?</td><td align="left" valign="top">Open-ended question</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>5. If you had to rearrange the entire TeamScreen display, what ideas or suggestions for improvement would you propose?</td><td align="left" valign="top">Open-ended question</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top">Completed tasks</td><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>6. What difficulties did you encounter while using the display, and why?</td><td align="left" valign="top">Open-ended question</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>7. What aspects of the display helped you complete the tasks (information retrieval)?</td><td align="left" valign="top">Open-ended question</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>8. What aspects of the display hindered you from completing the tasks (information retrieval)?</td><td align="left" valign="top">Open-ended question</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top">Display preferences</td><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>9. What do you think of the distribution of information in the &#x201C;Algorithm&#x201D; section?</td><td align="left" valign="top">Open-ended question</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>10. What do you think of the distribution of information in the &#x201C;Current Task&#x201D; section?</td><td align="left" valign="top">Open-ended question</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>11. To what extent did you find the display of secondary tasks helpful regarding patient status?</td><td align="left" valign="top">Likert-scale question</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Very useful</p></list-item><list-item><p>Useful</p></list-item><list-item><p>Neutral</p></list-item><list-item><p>Somewhat useful</p></list-item><list-item><p>Not useful at all</p></list-item></list></td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>12. What do you think of the distribution of information in the &#x201C;Next Steps&#x201D; section?</td><td align="left" valign="top">Open-ended question</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>12a. How many &#x201C;next steps&#x201D; would you ideally want to see? One, two, three, or more?</td><td align="left" valign="top">Single-choice question</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>One step</p></list-item><list-item><p>Two steps</p></list-item><list-item><p>Three steps</p></list-item><list-item><p>Other: ______</p></list-item></list></td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>13. What do you think of the distribution of information in the &#x201C;Countdown&#x201D; section?</td><td align="left" valign="top">Open-ended question</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>14. What do you think of the distribution of information in the &#x201C;Completed Tasks&#x201D; section?</td><td align="left" valign="top">Open-ended question</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>15. What do you think of the distribution of information in the &#x201C;Medications&#x201D; section?</td><td align="left" valign="top">Open-ended question</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>15a. What do you think these three icons represent in the &#x201C;Medications&#x201D; section?</td><td align="left" valign="top">Closed-ended question</td><td align="left" valign="top">&#x2014;</td></tr></tbody></table><table-wrap-foot><fn id="table2fn1"><p><sup>a</sup>Not applicable.</p></fn></table-wrap-foot></table-wrap></sec></sec><sec id="s2-6"><title>Data Collection and Analysis</title><sec id="s2-6-1"><title>Data Collection and Confidentiality</title><p>To ensure data confidentiality, all collected materials, including recordings, online questionnaires, and consent documents, were coded. Recordings captured only participants&#x2019; screen view, eye movements, and voice, ensuring privacy. When verbatim quotes were used in qualitative data analysis or reporting, only the assigned identifier was displayed. Each usability testing session was video- and audio-recorded for retrospective analysis of TeamScreen&#x2019;s usability. Two researchers (SO and ADM) independently reviewed task success rates and completion times. All PSSUQ scores were collected immediately after each test session and transcribed into Microsoft Excel spreadsheets for analysis. Half of the video recordings were independently assessed by SO and ADM to validate task success rates and completion times. Quantitative data collected during task execution underwent statistical analysis, and results were anonymized for reporting (see the <italic>Results</italic> section). During data collection and analysis, only 3 researchers (AR, SO, and ADM) had access to the audio and video recordings.</p></sec><sec id="s2-6-2"><title>Data Analysis</title><p>Descriptive statistics were used to summarize continuous variables, including task success rates, time-on-task metrics, and PSSUQ scores. Frequency counts and percentages were used to analyze categorical variables, such as the types of usability errors. Additionally, a correlation analysis of task failure rates was performed to explore potential dependencies between tasks, indicating whether tasks shared common cognitive demands or interface elements. Quantitative data, including task durations and success rates, were analyzed using the <italic>pandas</italic> library in Python (version 3.12; Python Software Foundation) to identify trends and compute averages. Verbal feedback from the think-aloud sessions was audio-recorded, transcribed verbatim, and analyzed using a structured content analysis approach. Two researchers (AR and SO) independently reviewed the transcripts, segmented them into meaning units corresponding to distinct interface problems, and coded each unit using Bastien and Scapin&#x2019;s [<xref ref-type="bibr" rid="ref35">35</xref>] ergonomic criteria for human-computer interaction (guidance, workload, explicit Ccntrol, adaptability, error management, consistency, significance of codes, and compatibility). These criteria were chosen because they provide a well-established, task-oriented framework for classifying usability issues in interactive systems [<xref ref-type="bibr" rid="ref37">37</xref>] and have been widely used in the evaluation of medical and health information technology interfaces [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref38">38</xref>]. Coded segments were then compared between both researchers. Discrepancies were resolved through discussion, and similar issues were grouped into overarching usability problems, which were mapped to specific interface sections (header, algorithm, completed tasks, medications). For each distinct usability issue, we calculated its frequency (number of participants who mentioned it) and assigned a severity rating using Nielsen Norman Group&#x2019;s rating scale ranging from 0 to 4 (0=none, 4=catastrophic). Graphical representations were generated using <italic>matplotlib</italic>, an open-source Python library [<xref ref-type="bibr" rid="ref39">39</xref>].</p></sec></sec></sec><sec id="s3" sec-type="results"><title>Results</title><sec id="s3-1"><title>Participant Characteristics</title><p>The usability tests were conducted in mid-September 2024. A total of 20 health care professionals participated in the study, of which 14 (70%) were women. The sample included 15 nurses (75%) and 5 physicians (25%). Of the 20 participants, 10 (50%) had completed PALS certification, including 3 of 5 physicians (60%) and 7 of 15 nurses (46.67%). Notably, 8 of 15 nurses (53.33%) had no PALS certification. The participants had a median experience of 6.00 (IQR 2.00-11.75) years in pediatric emergency care. All had prior exposure to real pediatric resuscitations, with the number of cases ranging from 2 to 100 and 30 cases being the most frequently reported value. Similarly, all had experience with simulated resuscitations, with the reported number of cases ranging widely, most commonly around 20 simulations.</p><p>Participants&#x2019; self-reported familiarity with digital devices varied: of 20 participants, 10 (50%) described themselves as &#x201C;comfortable&#x201D; using tablets and smartphones, whereas 6 (30%) reported being &#x201C;very comfortable.&#x201D; The remaining participants were either &#x201C;neutral&#x201D; (3/20, 15%) or &#x201C;slightly uncomfortable&#x201D; (1/20, 5%) with digital tools.</p></sec><sec id="s3-2"><title>Usability Evaluation</title><sec id="s3-2-1"><title>Quantitative Evaluation</title><sec id="s3-2-1-1"><title>Task Success Rate</title><p>Task success rates varied significantly across the usability assessment (<italic>&#x03C7;</italic><sup>2</sup><sub>20</sub>=74.59, <italic>P</italic>&#x003C;.001; <xref ref-type="fig" rid="figure4">Figure 4</xref>), ranging from 50% to 100%, with an overall success rate of 81.19% (SD 16.87%). Highest success rates (100%) were achieved for tasks 7 (<italic>Shocks given</italic>), 13 (<italic>Intubation time</italic>), 15 (<italic>Shock time</italic>), 18 (<italic>&#x201C;Other tasks&#x201D; section status</italic>), and 20 (<italic>Reversible causes</italic>), indicating that they were consistently completed without errors. The lowest success rates were achieved for task 5 (<italic>CPR status</italic>; 50%), followed by tasks 8 and 9 (55% each), suggesting that these tasks were more cognitively demanding or required greater user adaptation.</p><fig position="float" id="figure4"><label>Figure 4.</label><caption><p>Mean (95% CI) success rate by information retrieval task. The color gradient indicates the task success rate, ranging from light yellow (lower success rates) to dark green (higher success rates). A/B, airway and breathing; CPR: cardiopulmonary resuscitation.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v13i1e78736_fig04.png"/></fig></sec><sec id="s3-2-1-2"><title>Time on Task</title><p>Task completion times varied significantly (Kruskal-Wallis H<sub>20</sub>=154.99, <italic>P</italic>&#x003C;.001; <xref ref-type="fig" rid="figure5">Figure 5</xref>), reflecting differences in task complexity. On average, participants spent 170.80 (SD 44.70) seconds completing all 21 tasks, corresponding to a mean completion time of 8.13 (SD 7.07) seconds per task across all participants. Task 21 (<italic>Patient status: general understanding</italic>) required the longest duration, with an average completion time of 18.45 (SD 12.19) seconds, whereas task 4 (<italic>Define weight II</italic>) was completed the fastest, averaging 2.35 (SD 1.90) seconds.</p><fig position="float" id="figure5"><label>Figure 5.</label><caption><p>Box plot illustrating the distribution of task completion times across all 21 tasks performed during the usability study. Each box represents the IQR, with the median completion time indicated by the horizontal line inside the box. Whiskers extend to 1.5 times the IQR, and outliers are displayed as individual circles. Task 21 (Patient status: general understanding) exhibited the longest mean duration, suggesting higher complexity or additional steps required for completion, while task 4 (Define weight II) had the shortest duration, indicating a simpler information retrieval process. A/B: airway and breathing; CPR: cardiopulmonary resuscitation.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v13i1e78736_fig05.png"/></fig></sec><sec id="s3-2-1-3"><title>Average Task Duration by Success Versus Failure</title><p>Analysis of task completion times based on success or failure revealed a notable trend (<xref ref-type="fig" rid="figure6">Figure 6</xref>). In most cases, failed attempts were associated with significantly longer durations, suggesting that unsuccessful users required multiple attempts or encountered execution challenges. For example, in task 1 (<italic>Define weight I</italic>), failed attempts averaged 12.50 (SD 0.71) seconds, whereas successful attempts took only 3.78 (SD 3.42) seconds (<italic>P</italic>=.048), highlighting the impact of task difficulty on completion time. However, in task 5 (<italic>CPR status</italic>), the completion times for successful attempts (mean 10.00, SD 8.25 seconds) and failed attempts (mean 8.30, SD 5.81 seconds) were nearly identical (<italic>P</italic>=.73), indicating that participants invested consistent effort regardless of outcome.</p><fig position="float" id="figure6"><label>Figure 6.</label><caption><p>Box plot comparing task completion times between successful (blue) and failed (red) attempts across all 21 tasks. Each box represents the IQR, with the median duration indicated by the horizontal line. Whiskers extend to 1.5 times the IQR, and outliers are shown as individual circles. Overall, failed attempts generally took longer to complete, indicating challenges in task execution or repeated attempts (eg, task 1 [<italic>Define weight I</italic>]: failures averaged 12.5 s vs 3.77 s for successful attempts). However, for task 5 (<italic>CPR status</italic>), success and failure durations were nearly identical, suggesting that participants required similar effort regardless of the outcome. A/B: airway and breathing; CPR: cardiopulmonary resuscitation.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v13i1e78736_fig06.png"/></fig></sec><sec id="s3-2-1-4"><title>Correlation of Failure Rates Among Tasks</title><p>A correlation analysis of failure rates across tasks revealed potential dependencies, indicating that certain tasks share underlying cognitive demands or interface elements (<xref ref-type="fig" rid="figure7">Figure 7</xref>). Tasks with similar failure rates suggest common user difficulties, likely due to overlapping knowledge requirements or proximity within the interface. Several tasks exhibited strong positive correlations, suggesting that errors in one task were predictive of errors in another. For example, tasks 1 (<italic>Define weight I</italic>) and 4 (<italic>Define weight II</italic>) were highly correlated with tasks 12 (<italic>A/B problem assessment</italic>) and 16 (<italic>Medication status II</italic>) (Pearson correlation of per-participant binary success: <italic>r</italic>=0.69, <italic>P</italic>&#x003C;.001), as all of these required users to track updated patient data, such as weight changes, completed airway and breathing interventions, and medication details. Likewise, task 4 (<italic>Define weight II</italic>) and task 16 (<italic>Medication status II</italic>) showed a strong correlation (<italic>r</italic>=0.69, <italic>P</italic>&#x003C;.001), likely reflecting the dependency between understanding the patient&#x2019;s weight and correctly administering weight-based medication. Task 10 (<italic>Secondary tasks</italic>) was significantly correlated with task 12 (<italic>A/B problem assessment</italic>; <italic>r</italic>=0.69, <italic>P</italic>&#x003C;.001), suggesting that both tasks relied on the ability to monitor procedure logs or timeline view. Finally, tasks 16 (<italic>Medication status II</italic>) and 17 (<italic>Epinephrine time</italic>) exhibited a strong correlation (<italic>r</italic>=0.51, <italic>P</italic>=.02), as both involved understanding epinephrine administration; participants who struggled with one were likely to struggle with the other, highlighting potential cognitive or interface-related dependencies. Overall, these suggest that shared interface elements or related data points contributed to error clustering, emphasizing the need for enhanced visual cues or streamlined navigation to support information retrieval across interdependent tasks.</p><fig position="float" id="figure7"><label>Figure 7.</label><caption><p>Heat map visualizing the correlation of failure rates across 21 usability tasks. Darker blue regions indicate strong positive correlations. Conversely, light red areas represent negative correlations, where failure in one task was less predictive of failure in another.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v13i1e78736_fig07.png"/></fig></sec></sec></sec><sec id="s3-3"><title>Qualitative Evaluation</title><sec id="s3-3-1"><title>Frequent Errors</title><p>Analysis of task failures showed that task 5 (<italic>CPR status</italic>) had the highest failure frequency, accounting for 12.50% (10/80) of failed attempts. This was closely followed by tasks 8 (<italic>Medication status I</italic>) and 9 (<italic>CPR time</italic>) (9/80 each, 11.25%). Task 6 (<italic>Cardiac rhythm</italic>) accounted for 10% (8/80) of failures, and tasks 2, 3, 17, and 19 each accounted for 7.50% (6/80) of failures. These trends indicate that certain tasks posed consistent challenges across participants, potentially due to interface complexity, cognitive load, or unclear task presentation. <xref ref-type="table" rid="table3">Table 3</xref> provides a detailed breakdown of failed task occurrences across the 21 tasks, considering 80 total opportunities across all tasks.</p><table-wrap id="t3" position="float"><label>Table 3.</label><caption><p>Task failure frequency (N<sup><xref ref-type="table-fn" rid="table3fn1">a</xref></sup>=80).</p></caption><table id="table3" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Task number</td><td align="left" valign="bottom">Content</td><td align="left" valign="bottom">Failure frequency, n<sup><xref ref-type="table-fn" rid="table3fn2">b</xref></sup> (%)</td></tr></thead><tbody><tr><td align="char" char="." valign="top">5</td><td align="left" valign="top">What is the status of CPR<sup><xref ref-type="table-fn" rid="table3fn3">c</xref></sup>?</td><td align="left" valign="top">10 (12.50)</td></tr><tr><td align="char" char="." valign="top">8</td><td align="left" valign="top">Can any medication be administered?</td><td align="left" valign="top">9 (11.25)</td></tr><tr><td align="char" char="." valign="top">9</td><td align="left" valign="top">How much CPR time is left to do?</td><td align="left" valign="top">9 (11.25)</td></tr><tr><td align="char" char="." valign="top">6</td><td align="left" valign="top">What is the cardiac rhythm?</td><td align="left" valign="top">8 (10)</td></tr><tr><td align="char" char="." valign="top">17</td><td align="left" valign="top">How long until epinephrine must be administered again?</td><td align="left" valign="top">6 (7.50)</td></tr><tr><td align="char" char="." valign="top">2</td><td align="left" valign="top">Does the patient have a pulse?</td><td align="left" valign="top">6 (7.50)</td></tr><tr><td align="char" char="." valign="top">19</td><td align="left" valign="top">Which medication is being prepared?</td><td align="left" valign="top">6 (7.50)</td></tr><tr><td align="char" char="." valign="top">3</td><td align="left" valign="top">How long has the resuscitation been going on?</td><td align="left" valign="top">6 (7.50)</td></tr><tr><td align="char" char="." valign="top">21</td><td align="left" valign="top">What is the patient&#x2019;s current condition?</td><td align="left" valign="top">5 (6.25)</td></tr><tr><td align="char" char="." valign="top">11</td><td align="left" valign="top">What is the next step?</td><td align="left" valign="top">4 (5)</td></tr><tr><td align="char" char="." valign="top">16</td><td align="left" valign="top">Which medication was administered?</td><td align="left" valign="top">3 (3.75)</td></tr><tr><td align="char" char="." valign="top">14</td><td align="left" valign="top">Which tasks need to be done now?</td><td align="left" valign="top">2 (2.50)</td></tr><tr><td align="char" char="." valign="top">1</td><td align="left" valign="top">What is the patient&#x2019;s weight?</td><td align="left" valign="top">2 (2.50)</td></tr><tr><td align="char" char="." valign="top">10</td><td align="left" valign="top">Which secondary task is proposed to you?</td><td align="left" valign="top">2 (2.50)</td></tr><tr><td align="char" char="." valign="top">12</td><td align="left" valign="top">Which tasks have been performed to address the A/B<sup><xref ref-type="table-fn" rid="table3fn4">d</xref></sup> problems?</td><td align="left" valign="top">1 (1.25)</td></tr><tr><td align="char" char="." valign="top">4</td><td align="left" valign="top">What is the patient&#x2019;s weight?</td><td align="left" valign="top">1 (1.25)</td></tr></tbody></table><table-wrap-foot><fn id="table3fn1"><p><sup>a</sup>N: total number of opportunities.</p></fn><fn id="table3fn2"><p><sup>b</sup>n: number of failed attempts.</p></fn><fn id="table3fn3"><p><sup>c</sup>CPR: cardiopulmonary resuscitation.</p></fn><fn id="table3fn4"><p><sup>d</sup>A/B: airway and breathing.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s3-3-2"><title>Encountered Usability Issues</title><p>A total of 16 usability issues were identified across different sections of the TeamScreen interface. These issues were analyzed using the heuristics of Bastien and Scapin [<xref ref-type="bibr" rid="ref35">35</xref>] and classified by severity levels according to the Nielsen Norman Group&#x2019;s rating scale [<xref ref-type="bibr" rid="ref36">36</xref>] (<xref ref-type="table" rid="table4">Table 4</xref>).</p><table-wrap id="t4" position="float"><label>Table 4.</label><caption><p>Classification of usability issues identified by participants (N=20).</p></caption><table id="table4" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Usability issues (description and section)</td><td align="left" valign="bottom">Frequency, n</td><td align="left" valign="bottom">Bastien and Scapin&#x2019;s heuristics</td><td align="left" valign="bottom">Problem severity<sup><xref ref-type="table-fn" rid="table4fn1">a</xref></sup></td></tr></thead><tbody><tr><td align="left" valign="top">General issues</td><td align="left" valign="top">&#x2003;</td><td align="left" valign="top"/><td align="left" valign="top">&#x2003;</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>Excessive information displayed</italic>: multiple panels (eg, algorithm, completed tasks, and medications) with many elements visible at once made it difficult to identify the most relevant information for the current resuscitation step (general screen layout).</td><td align="left" valign="top">10</td><td align="left" valign="top"><italic>Workload</italic>: brevity, information density</td><td align="left" valign="top">3</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>Confusing time notation of CPR<sup><xref ref-type="table-fn" rid="table4fn2">b</xref></sup> timer:</italic> the CPR timer label did not clearly indicate whether the value represents total arrest duration, current cycle length, or time since last intervention, leading to misinterpretation of the timer.</td><td align="left" valign="top">2</td><td align="left" valign="top"><italic>Significance of codes</italic></td><td align="left" valign="top">2</td></tr><tr><td align="left" valign="top">Header section</td><td align="left" valign="top">&#x2003;</td><td align="left" valign="top"/><td align="left" valign="top">&#x2003;</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>Location visibility of patient weight</italic>: patient weight was located in the upper banner but not visually highlighted; several participants reported difficulty locating it quickly when asked to verify the weight.</td><td align="left" valign="top">5</td><td align="left" valign="top"><italic>Guidance</italic>: legibility</td><td align="left" valign="top">2</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>Font size of patient weight</italic>: the font size of patient weight in the header was too small to be read comfortably from the standard viewing distance of 2.7 m.</td><td align="left" valign="top">3</td><td align="left" valign="top"><italic>Guidance</italic>: legibility</td><td align="left" valign="top">1</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>Lack of current time display</italic>: the current clock time was not displayed anywhere on TeamScreen, forcing users to rely on external clocks to track absolute time during the scenario.</td><td align="left" valign="top">1</td><td align="left" valign="top"><italic>Adaptability</italic></td><td align="left" valign="top">2</td></tr><tr><td align="left" valign="top">Algorithm section</td><td align="left" valign="top">&#x2003;</td><td align="left" valign="top"/><td align="left" valign="top">&#x2003;</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>Poor legend visibility</italic>: the legend explaining the algorithm and color codes was small, making it difficult for users to remember or quickly decode the meaning of icons or colors.</td><td align="left" valign="top">4</td><td align="left" valign="top"><italic>Guidance</italic>: legibility</td><td align="left" valign="top">2</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>Difficulty understanding transitions between algorithm branches</italic>: transitions between algorithm branches (for example, from shockable to nonshockable pathways or post-ROSC<sup><xref ref-type="table-fn" rid="table4fn3">c</xref></sup> care) caused uncertainty about which branch to follow next.</td><td align="left" valign="top">6</td><td align="left" valign="top"><italic>Guidance</italic>: prompting</td><td align="left" valign="top">3</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>Visibility of patient status</italic>: patient&#x2019;s current state (eg, &#x201C;cardiac arrest&#x201D;) was not clearly highlighted near the active algorithm branch, which reduced situational awareness.</td><td align="left" valign="top">3</td><td align="left" valign="top"><italic>Compatibility</italic></td><td align="left" valign="top">3</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>Font size of 6H5T<sup><xref ref-type="table-fn" rid="table4fn4">d</xref></sup> text</italic>: the text listing reversible causes (6H5T) was presented in a small font and dense format, which participants found hard to read and use during the scenario.</td><td align="left" valign="top">3</td><td align="left" valign="top"><italic>Guidance</italic>: legibility</td><td align="left" valign="top">1</td></tr><tr><td align="left" valign="top">Completed tasks section</td><td align="left" valign="top">&#x2003;</td><td align="left" valign="top"/><td align="left" valign="top">&#x2003;</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>Overloaded with information</italic>: the list of completed tasks showed all previous actions with detailed timestamps, resulting in a visually dense list that was difficult to scan for the most recent or most important actions.</td><td align="left" valign="top">5</td><td align="left" valign="top"><italic>Workload</italic>: brevity, information density</td><td align="left" valign="top">3</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>Poor organization of task display in sections C<sup><xref ref-type="table-fn" rid="table4fn5">e</xref></sup>, A/B<sup><xref ref-type="table-fn" rid="table4fn6">f</xref></sup></italic></td><td align="left" valign="top">3</td><td align="left" valign="top"><italic>Compatibility</italic></td><td align="left" valign="top">2</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>Insufficient separation between subsections</italic></td><td align="left" valign="top">3</td><td align="left" valign="top"><italic>Guidance</italic>: legibility</td><td align="left" valign="top">2</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>Counterintuitive time notation</italic></td><td align="left" valign="top">3</td><td align="left" valign="top"><italic>Significance of codes</italic></td><td align="left" valign="top">2</td></tr><tr><td align="left" valign="top">Medications section</td><td align="left" valign="top">&#x2003;</td><td align="left" valign="top"/><td align="left" valign="top">&#x2003;</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>Ambiguous icons</italic>: icons used to represent medication-related actions (ie, in preparation, ready to administer, and administered) were not self-explanatory without accompanying text labels, potentially leading to misinterpretation of their meaning.</td><td align="left" valign="top">15</td><td align="left" valign="top"><italic>Significance of codes</italic></td><td align="left" valign="top">3</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>Missing calculated total doses/volumes</italic>: the medications panel did not display the final calculated total dose or volume for each drug, requiring users to mentally calculate weight-based dosage, which increased cognitive load and potential for dosing error.</td><td align="left" valign="top">5</td><td align="left" valign="top"><italic>Compatibility</italic></td><td align="left" valign="top">2</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>Unclear listed medication doses</italic></td><td align="left" valign="top">3</td><td align="left" valign="top"><italic>Compatibility</italic></td><td align="left" valign="top">2</td></tr></tbody></table><table-wrap-foot><fn id="table4fn1"><p><sup>a</sup>Nielsen Norman severity score: 4=catastrophic, 3=major, 2= minor, 1=cosmetic, 0=none.</p></fn><fn id="table4fn2"><p><sup>b</sup>CPR: cardiopulmonary resuscitation.</p></fn><fn id="table4fn3"><p><sup>c</sup>ROSC: return of spontaneous circulation.</p></fn><fn id="table4fn4"><p><sup>d</sup>6H5T: hypovolemia, hypoxia, hydrogen ion (acidosis), hypokalemia/hyperkalemia, hypoglycemia, hypothermia, tension pneumothorax, tamponade, toxins, thrombosis (pulmonary), thrombosis (coronary).</p></fn><fn id="table4fn5"><p><sup>e</sup>C: circulation.</p></fn><fn id="table4fn6"><p><sup>f</sup>A/B: airway and breathing.</p></fn></table-wrap-foot></table-wrap><p>The primary usability issues were general challenges rather than being confined to specific interface sections. These included cognitive overload due to excessive information displayed information; difficulty understanding task requirements, increasing mental workload; and medication-related confusion, particularly in interpreting drug administration icons. The most frequently reported issue was the lack of clarity in medication icons, making it difficult for participants to distinguish between medications in preparation, ready for administration, or already administered. Other issues, although present, were encountered by fewer than one-third of participants.</p><p>Overall, the study identified key usability challenges related to information visibility, navigation, and comprehension. The most critical usability issues (severity 3&#x2010;4) included medication icon confusion (most frequently reported), excessive information density leading to cognitive overload.</p></sec><sec id="s3-3-3"><title>User Satisfaction</title><sec id="s3-3-3-1"><title>PSSUQ Scores</title><p>Participants provided positive feedback on screen readability, with a mean PSSUQ score of 2.40 (SD 1.24) indicating high usability. However, they suggested improvements in information hierarchy and task simplification due to perceived cognitive overload. Overall, PSSUQ scores were lower (better usability) than the PSSUQ version 3 benchmark (<xref ref-type="table" rid="table5">Table 5</xref>), confirming high system usefulness and interface quality.</p><p>Scores closer to 1 indicate higher usability. TeamScreen scores were descriptively lower than the published PSSUQ benchmark means, suggesting that participants found the system intuitive and effective, although information presentation still offers room for optimization.</p><table-wrap id="t5" position="float"><label>Table 5.</label><caption><p>Comparison of TeamScreen PSSUQ<sup><xref ref-type="table-fn" rid="table5fn1">a</xref></sup> scores versus the PSSUQ version 3 (V3) benchmark.</p></caption><table id="table5" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom"/><td align="left" valign="bottom">TeamScreen score, mean (SD)</td><td align="left" valign="bottom">PSSUQ V3 benchmark mean</td></tr></thead><tbody><tr><td align="left" valign="top">Overall score</td><td align="left" valign="top">2.40 (1.24)</td><td align="left" valign="top">2.82</td></tr><tr><td align="left" valign="top">System usefulness (SysUse)</td><td align="left" valign="top">2.44 (1.22)</td><td align="left" valign="top">2.80</td></tr><tr><td align="left" valign="top">Information quality (InfoQual)</td><td align="left" valign="top">2.41 (1.20)</td><td align="left" valign="top">3.02</td></tr><tr><td align="left" valign="top">Interface quality (IntQual)</td><td align="left" valign="top">2.20 (1.41)</td><td align="left" valign="top">2.49</td></tr></tbody></table><table-wrap-foot><fn id="table5fn1"><p><sup>a</sup>PSSUQ: Post-Study System Usability Questionnaire.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s3-3-3-2"><title>Participant Verbal Feedback</title><p>Think-aloud verbalizations during task execution, combined with responses from the posttask debriefing survey, provided valuable contextual information that enriched the interpretation of the PSSUQ scores and offered deeper insights into users&#x2019; experiences and expectations regarding the interface.</p><p>Overall, participants expressed mixed feelings about their experience with the TeamScreen interface. In terms of strengths, 8 of 20 (40%) participants highlighted the clarity and organization of the information, quality of the display, and good readability (in terms of font size and color). Several participants particularly appreciated the guidance provided through the algorithm section (12/20, 60%) and the associated color coding (8/20, 40%)&#x2014;green indicating &#x201C;finished&#x201D; and orange indicating &#x201C;in progress&#x201D;&#x2014;as well as the &#x201C;Completed Tasks&#x201D; section (9/20, 45%), which enhanced their situational awareness.</p><p>Regarding areas for improvement, 9 of 20 (45%) participants reported misunderstanding difficulties, particularly related to the middle section of the screen, not directly attributable to usability issues. Several users (10/20, 50%) reported that the amount of information presented was overwhelming, contributing to increased cognitive load. The &#x201C;Current Task&#x201D; area was also frequently overlooked, as 9 of 20 (45%) participants felt that the relevant information was already accessible within the algorithm panel on the left side of the screen, making it redundant. Furthermore, several users suggested making a clearer distinction between &#x201C;Current Task&#x201D; and &#x201C;Next Steps&#x201D; to better support cognitive processing under pressure. These insights emphasize the need for improvements in information hierarchy and cognitive load reduction in critical usage scenarios. Finally, participants indicated a need for greater clarity in the &#x201C;Medication section&#x201D; (5/20, 25%), specifically concerning the meaning of the 3 icons representing the medication status (in preparation, ready for administration, administered). However, it is important to acknowledge that many of these reported issues were, according to the participants, largely attributable to their lack of prior exposure to the app. Participants indicated that with appropriate training, the interface would become significantly more intuitive, enabling faster and more accurate information retrieval during real-time pediatric cardiac arrest scenarios, as well as more effective adherence to American Heart Association guidelines.</p></sec></sec></sec><sec id="s3-4"><title>Modifications Based on Usability Findings</title><p>Following the usability analysis, several targeted refinements were implemented, each addressing a specific usability issue summarized in <xref ref-type="table" rid="table4">Table 4</xref>. First, limited visibility and ambiguous interpretation of the CPR timer led us to relocate the main timer to the top of the screen and clarify its label to ensure continuous and unambiguous visibility throughout the resuscitation process. Second, difficulties in reading and using the reversible causes (6H5T; hypovolemia, hypoxia, hydrogen ion [acidosis], hypokalemia/hyperkalemia, hypoglycemia, hypothermia, tension pneumothorax, tamponade, toxins, thrombosis [pulmonary], thrombosis [coronary]) prompted an increase in font size and a permanent display to provide immediate access to correction measures. Third, issues related to information overload and poor readability of the list of completed tasks motivated a restyling of the task list, replacing square markers with bullet points, and secondary tasks were repositioned higher in the interface to make them more noticeable and actionable. Fourth, in response to concerns that timers were easy to overlook as they approached zero, countdown timers were enhanced to blink when nearing expiry, drawing the team&#x2019;s attention and reducing the risk of delayed interventions. Finally, frequent misinterpretation of medication icons and confusion around drug administration stages led to the introduction of 3 distinct, clearly labeled icons indicating whether a drug was in preparation, prepared, or already administered. Collectively, these modifications aimed to alleviate information overload, improve navigation, and highlight essential cues in high&#x2010;stress pediatric resuscitation scenarios.</p></sec></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><sec id="s4-1"><title>Key Findings</title><p>TeamScreen introduces a new generation of context-aware clinical displays aimed at reinforcing shared cognition and temporal coordination among resuscitation teams rather than replacing clinical judgment. This single-center, mixed methods study evaluating its usability during simulated IHCA management yielded several salient insights.</p><p>With an overall task success rate of 81%, most participants effectively located and interpreted essential clinical information under simulated urgency, despite challenges in early pediatric IHCA response [<xref ref-type="bibr" rid="ref40">40</xref>]. Tasks 7 (<italic>Shocks given</italic>), 13 (<italic>Intubation time</italic>), 15 (<italic>Shock time</italic>), 18 (<italic>&#x201C;Other tasks&#x201D; section status</italic>), and 20 (<italic>Reversible causes</italic>), covering shock delivery logs, intubation timestamps, and reversible&#x2010;causes guidance, achieved 100% success, suggesting that these interface elements were well designed and intuitive. Conversely, tasks 5 (<italic>CPR status</italic>), 8 (<italic>Medication status I</italic>), and 9 (<italic>CPR time</italic>) related to tracking ongoing CPR and upcoming interventions (eg, epinephrine administration) exhibited the highest failure rates. Participants who struggled with these tasks frequently cited uncertainty regarding the location of real-time information, highlighting a need for improved visual hierarchy in high-density interface areas, in line with cognitive load theory [<xref ref-type="bibr" rid="ref41">41</xref>].</p><p>Task completion times demonstrated substantial variability across the 21 tasks, reflecting heterogeneity in task complexity and cognitive processing demands. Task 21 (<italic>Patient status: general understanding</italic>) exhibited the longest mean completion time, indicating that tasks involving a broader synthesis of patient information were more time-consuming. Conversely, task 4 (<italic>Define weight II</italic>) was completed most rapidly, suggesting minimal cognitive load and straightforward retrieval. This efficiency may also be attributed to task 4 representing the second occurrence of a previous task, that is, task 1 (<italic>Define weight I</italic>), whereby participants were already familiar with the location of the relevant information on the display.</p><p>Correlation analysis showed errors clustering around related data points, such as medication timing and dosage, underscoring the importance of consistent navigation cues and harmonized data presentation across the algorithm view, timeline, and &#x201C;Completed Tasks&#x201D; sections. This aligns with evidence that protocol adherence significantly improves IHCA outcomes [<xref ref-type="bibr" rid="ref42">42</xref>], emphasizing TeamScreen&#x2019;s potential to enhance care quality through better design. The PSSUQ scores indicated high user satisfaction, with participants valuing TeamScreen&#x2019;s consolidation of vital parameters, current tasks, and next&#x2010;step recommendations into a central, readable display. These findings suggest that TeamScreen excels where clarity is prioritized (eg, timestamps and shock logs) but requires refinement in areas with visual clutter, icon ambiguity, or subtle task distinctions. Given varying roles in IHCA response where nurses often manage documentation and physicians lead decisions [<xref ref-type="bibr" rid="ref43">43</xref>], future studies should explore whether task success or perceived usability differs across these groups.</p></sec><sec id="s4-2"><title>Comparison With Literature</title><p>TeamScreen shares similarities with real-time dashboard systems aggregating patient vitals, medication records, and intervention timelines onto shared displays, as seen in prior work improving clinicians&#x2019; access to critical data and reducing cognitive load [<xref ref-type="bibr" rid="ref44">44</xref>]. However, unlike passive aggregators, TeamScreen integrates real-time visualization with interactive PALS-aligned algorithmic guidance, supporting both team situational awareness and decision-making during IHCA. This dual functionality addresses a gap in traditional dashboards, which often lack structured support for resuscitation guidelines. For instance, Siebert et al [<xref ref-type="bibr" rid="ref45">45</xref>] demonstrated that AR glasses improved defibrillation dosing adherence compared to PALS pocket cards, although without broader workflow integration. A recent systematic review by Cheng et al [<xref ref-type="bibr" rid="ref46">46</xref>] highlights the potential of AR and virtual reality to enhance resuscitation skills but notes inconsistent superiority over traditional methods, underscoring the need for integrated solutions such as TeamScreen. TeamScreen extends this concept by offering a centralized, algorithm-synchronized interface, positioning it within an emerging class of digital tools designed to optimize shared cognition and temporal alignment in high-acuity care.</p></sec><sec id="s4-3"><title>Essential TeamScreen Enhancements</title><p>The usability evaluation of TeamScreen has identified critical areas for future refinement, and the following enhancements will be implemented to optimize its support for resuscitation teams. The information hierarchy will be restructured to minimize visual overload, consolidating related elements such as medication timing and dosage into a distinct, clearly labeled panel, guided by cognitive load principles [<xref ref-type="bibr" rid="ref41">41</xref>]. This adjustment could streamline data retrieval and lessen cognitive strain during time-sensitive tasks. Dynamic visual cues, such as color shifts or blinking countdowns for medication intervals, could prompt timely actions, provided they adhere to ergonomic principles to avoid distraction in high&#x2010;stress settings. Functionally, adaptive role-based prompts tied to PALS algorithms could guide users step-by-step, improving coordination and adherence. Standardizing labels, icons, and visual styles (eg, font sizes, colors, and legends) would enhance consistency and reduce the likelihood of misinterpretation, particularly for the 6H5T mnemonic and streamlined task lists. Finally, given its intuitive design, brief, role&#x2010;specific onboarding is advised&#x2014;especially for users with varying digital fluency&#x2014;to ensure efficient navigation in multitasking, high-stakes scenarios such as CPR. Paired with these design refinements and enhancements, targeted training could maximize TeamScreen&#x2019;s potential to support resuscitation teams effectively.</p></sec><sec id="s4-4"><title>Study Limitations</title><p>This study has several limitations. Testing TeamScreen in a simulated environment without direct user interaction limits conclusions about real-world PALS algorithms adherence or patient outcomes. The heightened stress of a real-life IHCA situation might exacerbate usability challenges not fully captured in this study. Additionally, evaluating TeamScreen isolation (ie, without AR Headsets or Guiding Pad) potentially reduces ecological validity, as the full InterFACE-AR suite&#x2019;s interplay was not assessed. This may also not fully capture the usability of the complete system. However, the Guiding Pad and AR headset modules have been evaluated in separate component-level usability studies, and the integrated InterFACE-AR system has recently been tested in a multicenter randomized controlled trial in a high-fidelity simulated setting. Third, the passive display design, reliant on a charting nurse&#x2019;s input via the Guiding Pad, aligns with its intended use but restricted participants&#x2019; ability to explore the interface freely, potentially skewing engagement. Fourth, the study sample size and various clinical backgrounds of participants further limit generalizability. Fifth, our evaluation was supposedly conducted in a dedicated emergency department resuscitation bay using a fixed, wall-mounted TeamScreen display, which may limit generalizability to ward-based pediatric IHCA where mobile configurations of TeamScreen and the Guiding Pad would be required and should be evaluated in future work. Finally, while cognitive overload was frequently noted in feedback, this dimension remained unquantified owing to the absence of a validated instrument such as the NASA-Task Load Index (NASA-TLX) [<xref ref-type="bibr" rid="ref47">47</xref>]. This should be addressed in future studies.</p></sec><sec id="s4-5"><title>Future Directions</title><p>Several of the usability issues identified in this study point to general design principles that are relevant for other digital tools in acute care. Information that is crucial for safe care (such as timers, current patient status, and key tasks) should be clearly visible on a shared team display. The amount of information on screen needs to be limited and well structured to avoid overload, and icons or color codes must be immediately understandable, even under stress. These lessons can guide the design of other real-time decision support systems that aim to support teamwork rather than only individual users.</p><p>The next phase of our program consists of 2 multicenter, simulation randomized controlled trials in 2025. The first, conducted in the second quarter of 2025, has now been completed, and the second, initiated in the fourth quarter of 2025, is currently underway, integrating TeamScreen with AR Headsets and Guiding Pad to evaluate clinical decision&#x2010;making, teamwork, communication, and patient safety outcomes across diverse hospital settings. Structured, role-specific onboarding will mitigate the learning curve effects observed in this study, offering a clearer performance baseline under realistic pressures. Because adherence to advanced life support guidelines is associated with better IHCA outcomes [<xref ref-type="bibr" rid="ref42">42</xref>], metrics such as drug administration timing, error rates, and PALS adherence will provide deeper insights into how digital support influences care quality. Role differences (eg, nurses&#x2019; documentation vs physicians&#x2019; leadership [<xref ref-type="bibr" rid="ref43">43</xref>]) will also be examined to further adapt the interfaces. Cognitive workload will be quantified using tools such as the NASA-TLX [<xref ref-type="bibr" rid="ref47">47</xref>] to address qualitative feedback about overload and to test whether the system genuinely reduces cognitive burden.</p><p>Future iterations could incorporate artificial intelligence&#x2013;driven predictive analytics to anticipate tasks (eg, rhythm reassessment), further reducing manual tracking demands. Qualitative feedback and high usability scores suggest that TeamScreen may alleviate cognitive load, although formal workload assessments are needed. Future work also needs to address more practical questions that apply to many medical digital tools, including feasibility of deployment, interoperability with existing hospital systems, and implementation costs, for widespread adoption. Integration with electronic health records, automated monitoring data capture, and tailored role-specific interfaces represent key translational goals to support clinical use of InterFACE-AR and similar decision support systems.</p></sec><sec id="s4-6"><title>Conclusion</title><p>This study provides a structured usability evaluation of TeamScreen, a shared digital interface designed to assist pediatric resuscitation teams during IHCA, with its clinical impact still to be validated. Using a mixed methods approach, we identified its strengths and limitations in a simulated setting. Results revealed an 81% task success rate and high user satisfaction, confirming TeamScreen&#x2019;s ability to deliver accessible, interpretable clinical data under time pressure. However, issues with information hierarchy and task clarity, evidenced by correlated failures in navigation and updates, highlighted areas for refinement. The combined analyses of error categorization, verbal feedback, and questionnaire responses provided insights about the prototype&#x2019;s strengths and areas requiring refinement. This comprehensive evaluation not only identified critical usability challenges but also validated the potential of the TeamScreen prototype to optimize pediatric resuscitation workflows.</p></sec></sec></body><back><notes><sec><title>Funding</title><p>This study was funded by grant support provided by the Private Foundation of the Geneva University Hospitals.</p></sec><sec><title>Data Availability</title><p>The datasets generated during this study are available from the corresponding author on reasonable request and after ethical approval.</p></sec></notes><fn-group><fn fn-type="conflict"><p>JNS received research grant support from the Geneva University Hospitals (HUG) Private Foundation for work related to this project. SM received research grant support from the Geneva Hospitals Private Foundation for work related to this project.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">6H5T</term><def><p>hypovolemia, hypoxia, hydrogen ion (acidosis), hypokalemia/hyperkalemia, hypoglycemia, hypothermia, tension pneumothorax, tamponade, toxins, thrombosis (pulmonary), thrombosis (coronary)</p></def></def-item><def-item><term id="abb2">AR</term><def><p>augmented reality</p></def></def-item><def-item><term id="abb3">CPR</term><def><p>cardiopulmonary resuscitation</p></def></def-item><def-item><term id="abb4">IHCA</term><def><p>in-hospital cardiac arrest</p></def></def-item><def-item><term id="abb5">InterFACE</term><def><p>Interconnected and Focused Mobile Applications on Patient Care Environment</p></def></def-item><def-item><term id="abb6">PALS</term><def><p>pediatric advanced life support</p></def></def-item><def-item><term id="abb7">PSSUQ</term><def><p>Post-Study System Usability Questionnaire</p></def></def-item><def-item><term id="abb8">ROSC</term><def><p>return of spontaneous circulation</p></def></def-item><def-item><term id="abb9">TLX</term><def><p>Task Load Index</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Giri</surname><given-names>S</given-names> </name><name name-style="western"><surname>Gyeltshen</surname><given-names>D</given-names> </name><name name-style="western"><surname>Wangchuk</surname><given-names>N</given-names> </name><etal/></person-group><article-title>Improving role allocation for cardiopulmonary resuscitation (CPR) in the emergency department: a quality improvement project</article-title><source>BMJ Open Qual</source><year>2024</year><month>09</month><day>30</day><volume>13</volume><issue>3</issue><fpage>e002870</fpage><pub-id pub-id-type="doi">10.1136/bmjoq-2024-002870</pub-id><pub-id pub-id-type="medline">39349305</pub-id></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>Topjian</surname><given-names>AA</given-names> </name><name name-style="western"><surname>Raymond</surname><given-names>TT</given-names> </name><name name-style="western"><surname>Atkins</surname><given-names>D</given-names> </name><etal/></person-group><article-title>Part 4: pediatric basic and advanced life support: 2020 American Heart Association guidelines for cardiopulmonary resuscitation and emergency cardiovascular care</article-title><source>Circulation</source><year>2020</year><month>10</month><day>20</day><volume>142</volume><issue>16_suppl_2</issue><fpage>S469</fpage><lpage>S523</lpage><pub-id pub-id-type="doi">10.1161/CIR.0000000000000901</pub-id><pub-id pub-id-type="medline">33081526</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>Hunt</surname><given-names>EA</given-names> </name><name name-style="western"><surname>Vera</surname><given-names>K</given-names> </name><name name-style="western"><surname>Diener-West</surname><given-names>M</given-names> </name><etal/></person-group><article-title>Delays and errors in cardiopulmonary resuscitation and defibrillation by pediatric residents during simulated cardiopulmonary arrests</article-title><source>Resuscitation</source><year>2009</year><month>07</month><volume>80</volume><issue>7</issue><fpage>819</fpage><lpage>825</lpage><pub-id pub-id-type="doi">10.1016/j.resuscitation.2009.03.020</pub-id><pub-id pub-id-type="medline">19423210</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>Corazza</surname><given-names>F</given-names> </name><name name-style="western"><surname>Stritoni</surname><given-names>V</given-names> </name><name name-style="western"><surname>Martinolli</surname><given-names>F</given-names> </name><etal/></person-group><article-title>Adherence to guideline recommendations in the management of pediatric cardiac arrest: a multicentre observational simulation-based study</article-title><source>Eur J Emerg Med</source><year>2022</year><month>08</month><day>1</day><volume>29</volume><issue>4</issue><fpage>271</fpage><lpage>278</lpage><pub-id pub-id-type="doi">10.1097/MEJ.0000000000000923</pub-id><pub-id pub-id-type="medline">35404331</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>Auerbach</surname><given-names>M</given-names> </name><name name-style="western"><surname>Brown</surname><given-names>L</given-names> </name><name name-style="western"><surname>Whitfill</surname><given-names>T</given-names> </name><etal/></person-group><article-title>Adherence to pediatric cardiac arrest guidelines across a spectrum of fifty emergency departments: a prospective, in situ, simulation&#x2010;based study</article-title><source>Acad Emerg Med</source><year>2018</year><month>12</month><volume>25</volume><issue>12</issue><fpage>1396</fpage><lpage>1408</lpage><pub-id pub-id-type="doi">10.1111/acem.13564</pub-id><pub-id pub-id-type="medline">30194902</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>Siebert</surname><given-names>JN</given-names> </name><name name-style="western"><surname>Ehrler</surname><given-names>F</given-names> </name><name name-style="western"><surname>Combescure</surname><given-names>C</given-names> </name><etal/></person-group><article-title>A mobile device app to reduce time to drug delivery and medication errors during simulated pediatric cardiopulmonary resuscitation: a randomized controlled trial</article-title><source>J Med Internet Res</source><year>2017</year><month>02</month><day>1</day><volume>19</volume><issue>2</issue><fpage>e31</fpage><pub-id pub-id-type="doi">10.2196/jmir.7005</pub-id><pub-id pub-id-type="medline">28148473</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>Wolfe</surname><given-names>HA</given-names> </name><name name-style="western"><surname>Morgan</surname><given-names>RW</given-names> </name><name name-style="western"><surname>Zhang</surname><given-names>B</given-names> </name><etal/></person-group><article-title>Deviations from AHA guidelines during pediatric cardiopulmonary resuscitation are associated with decreased event survival</article-title><source>Resuscitation</source><year>2020</year><month>04</month><volume>149</volume><fpage>89</fpage><lpage>99</lpage><pub-id pub-id-type="doi">10.1016/j.resuscitation.2020.01.035</pub-id><pub-id pub-id-type="medline">32057946</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>Crabb</surname><given-names>DB</given-names> </name><name name-style="western"><surname>Hurwitz</surname><given-names>JE</given-names> </name><name name-style="western"><surname>Reed</surname><given-names>AC</given-names> </name><etal/></person-group><article-title>Innovation in resuscitation: a novel clinical decision display system for advanced cardiac life support</article-title><source>Am J Emerg Med</source><year>2021</year><month>05</month><volume>43</volume><fpage>217</fpage><lpage>223</lpage><pub-id pub-id-type="doi">10.1016/j.ajem.2020.03.007</pub-id><pub-id pub-id-type="medline">32291164</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>Field</surname><given-names>LC</given-names> </name><name name-style="western"><surname>McEvoy</surname><given-names>MD</given-names> </name><name name-style="western"><surname>Smalley</surname><given-names>JC</given-names> </name><etal/></person-group><article-title>Use of an electronic decision support tool improves management of simulated in-hospital cardiac arrest</article-title><source>Resuscitation</source><year>2014</year><month>01</month><volume>85</volume><issue>1</issue><fpage>138</fpage><lpage>142</lpage><pub-id pub-id-type="doi">10.1016/j.resuscitation.2013.09.013</pub-id><pub-id pub-id-type="medline">24056391</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>Greig</surname><given-names>PR</given-names> </name><name name-style="western"><surname>Zolger</surname><given-names>D</given-names> </name><name name-style="western"><surname>Onwochei</surname><given-names>DN</given-names> </name><name name-style="western"><surname>Thurley</surname><given-names>N</given-names> </name><name name-style="western"><surname>Higham</surname><given-names>H</given-names> </name><name name-style="western"><surname>Desai</surname><given-names>N</given-names> </name></person-group><article-title>Cognitive aids in the management of clinical emergencies: a systematic review</article-title><source>Anaesthesia</source><year>2023</year><month>03</month><volume>78</volume><issue>3</issue><fpage>343</fpage><lpage>355</lpage><pub-id pub-id-type="doi">10.1111/anae.15939</pub-id><pub-id pub-id-type="medline">36517981</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>Grundgeiger</surname><given-names>T</given-names> </name><name name-style="western"><surname>Hahn</surname><given-names>F</given-names> </name><name name-style="western"><surname>Wurmb</surname><given-names>T</given-names> </name><name name-style="western"><surname>Meybohm</surname><given-names>P</given-names> </name><name name-style="western"><surname>Happel</surname><given-names>O</given-names> </name></person-group><article-title>The use of a cognitive aid app supports guideline-conforming cardiopulmonary resuscitations: a randomized study in a high-fidelity simulation</article-title><source>Resusc Plus</source><year>2021</year><month>09</month><volume>7</volume><fpage>100152</fpage><pub-id pub-id-type="doi">10.1016/j.resplu.2021.100152</pub-id><pub-id pub-id-type="medline">34458879</pub-id></nlm-citation></ref><ref id="ref12"><label>12</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Corazza</surname><given-names>F</given-names> </name><name name-style="western"><surname>Fiorese</surname><given-names>E</given-names> </name><name name-style="western"><surname>Arpone</surname><given-names>M</given-names> </name><etal/></person-group><article-title>The impact of cognitive aids on resuscitation performance in in-hospital cardiac arrest scenarios: a systematic review and meta-analysis</article-title><source>Intern Emerg Med</source><year>2022</year><month>10</month><volume>17</volume><issue>7</issue><fpage>2143</fpage><lpage>2158</lpage><pub-id pub-id-type="doi">10.1007/s11739-022-03041-6</pub-id><pub-id pub-id-type="medline">36031672</pub-id></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>Corazza</surname><given-names>F</given-names> </name><name name-style="western"><surname>Arpone</surname><given-names>M</given-names> </name><name name-style="western"><surname>Tardini</surname><given-names>G</given-names> </name><etal/></person-group><article-title>Effectiveness of a novel tablet application in reducing guideline deviations during pediatric cardiac arrest: a randomized clinical trial</article-title><source>JAMA Netw Open</source><year>2023</year><month>08</month><day>1</day><volume>6</volume><issue>8</issue><fpage>e2327272</fpage><pub-id pub-id-type="doi">10.1001/jamanetworkopen.2023.27272</pub-id><pub-id pub-id-type="medline">37535352</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>Corazza</surname><given-names>F</given-names> </name><name name-style="western"><surname>Snijders</surname><given-names>D</given-names> </name><name name-style="western"><surname>Arpone</surname><given-names>M</given-names> </name><etal/></person-group><article-title>Development and usability of a novel interactive tablet app (PediAppRREST) to support the management of pediatric cardiac arrest: pilot high-fidelity simulation-based study</article-title><source>JMIR Mhealth Uhealth</source><year>2020</year><month>10</month><day>1</day><volume>8</volume><issue>10</issue><fpage>e19070</fpage><pub-id pub-id-type="doi">10.2196/19070</pub-id><pub-id pub-id-type="medline">32788142</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>Siebert</surname><given-names>JN</given-names> </name><name name-style="western"><surname>Lacroix</surname><given-names>L</given-names> </name><name name-style="western"><surname>Cantais</surname><given-names>A</given-names> </name><name name-style="western"><surname>Manzano</surname><given-names>S</given-names> </name><name name-style="western"><surname>Ehrler</surname><given-names>F</given-names> </name></person-group><article-title>The impact of a tablet app on adherence to American Heart Association guidelines during simulated pediatric cardiopulmonary resuscitation: randomized controlled trial</article-title><source>J Med Internet Res</source><year>2020</year><month>05</month><day>27</day><volume>22</volume><issue>5</issue><fpage>e17792</fpage><pub-id pub-id-type="doi">10.2196/17792</pub-id><pub-id pub-id-type="medline">32292179</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>Nabecker</surname><given-names>S</given-names> </name><name name-style="western"><surname>Nation</surname><given-names>K</given-names> </name><name name-style="western"><surname>Gilfoyle</surname><given-names>E</given-names> </name><etal/></person-group><article-title>Cognitive aids used in simulated resuscitation: a systematic review</article-title><source>Resusc Plus</source><year>2024</year><month>09</month><volume>19</volume><fpage>100675</fpage><pub-id pub-id-type="doi">10.1016/j.resplu.2024.100675</pub-id><pub-id pub-id-type="medline">38873274</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>Parush</surname><given-names>A</given-names> </name><name name-style="western"><surname>Mastoras</surname><given-names>G</given-names> </name><name name-style="western"><surname>Bhandari</surname><given-names>A</given-names> </name><etal/></person-group><article-title>Can teamwork and situational awareness (SA) in ED resuscitations be improved with a technological cognitive aid? Design and a pilot study of a team situation display</article-title><source>J Biomed Inform</source><year>2017</year><month>12</month><volume>76</volume><fpage>154</fpage><lpage>161</lpage><pub-id pub-id-type="doi">10.1016/j.jbi.2017.10.009</pub-id><pub-id pub-id-type="medline">29051106</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>Calder</surname><given-names>LA</given-names> </name><name name-style="western"><surname>Bhandari</surname><given-names>A</given-names> </name><name name-style="western"><surname>Mastoras</surname><given-names>G</given-names> </name><etal/></person-group><article-title>Healthcare providers&#x2019; perceptions of a situational awareness display for emergency department resuscitation: a simulation qualitative study</article-title><source>Int J Qual Health Care</source><year>2018</year><month>02</month><day>1</day><volume>30</volume><issue>1</issue><fpage>16</fpage><lpage>22</lpage><pub-id pub-id-type="doi">10.1093/intqhc/mzx159</pub-id><pub-id pub-id-type="medline">29194491</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>Ehrler</surname><given-names>F</given-names> </name><name name-style="western"><surname>Del Zotto</surname><given-names>M</given-names> </name><name name-style="western"><surname>Rouyer</surname><given-names>F</given-names> </name><name name-style="western"><surname>Weinhold</surname><given-names>T</given-names> </name><name name-style="western"><surname>Lovis</surname><given-names>C</given-names> </name><name name-style="western"><surname>Siebert</surname><given-names>J</given-names> </name></person-group><article-title>Design of InterFACE: a tool to improve collaborative work and decision making during rescucitation</article-title><source>Stud Health Technol Inform</source><year>2018</year><volume>255</volume><fpage>117</fpage><lpage>121</lpage><pub-id pub-id-type="medline">30306919</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>Ehrler</surname><given-names>F</given-names> </name><name name-style="western"><surname>Sahyoun</surname><given-names>C</given-names> </name><name name-style="western"><surname>Manzano</surname><given-names>S</given-names> </name><etal/></person-group><article-title>Impact of a shared decision-making mHealth tool on caregivers&#x2019; team situational awareness, communication effectiveness, and performance during pediatric cardiopulmonary resuscitation: study protocol of a cluster randomized controlled trial</article-title><source>Trials</source><year>2021</year><month>04</month><day>13</day><volume>22</volume><issue>1</issue><fpage>277</fpage><pub-id pub-id-type="doi">10.1186/s13063-021-05170-3</pub-id><pub-id pub-id-type="medline">33849611</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>Kang</surname><given-names>R</given-names> </name><name name-style="western"><surname>Cheng</surname><given-names>A</given-names> </name><name name-style="western"><surname>Lin</surname><given-names>Y</given-names> </name><etal/></person-group><article-title>Perceived usability, user experience, and technology acceptance of role-specific augmented reality decision support tools for cardiac arrest resuscitation: prospective observational pilot study</article-title><source>JMIR XR Spatial Comput</source><year>2026</year><volume>3</volume><fpage>e72013</fpage><pub-id pub-id-type="doi">10.2196/72013</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>Ehrler</surname><given-names>F</given-names> </name><name name-style="western"><surname>Rajic</surname><given-names>A</given-names> </name><name name-style="western"><surname>De Masi</surname><given-names>A</given-names> </name><etal/></person-group><article-title>Overview of a user-centered, mixed-methods process for designing Interconnected and Focused Mobile Applications on Patient Care Environment (InterFACE): augmented-reality decision support system for pediatric resuscitation</article-title><source>JMIR Hum Factors</source><year>2026</year><month>02</month><day>13</day><volume>13</volume><fpage>e78144</fpage><pub-id pub-id-type="doi">10.2196/78144</pub-id><pub-id pub-id-type="medline">41687005</pub-id></nlm-citation></ref><ref id="ref23"><label>23</label><nlm-citation citation-type="book"><person-group person-group-type="author"><collab>Food and Drug Administration</collab></person-group><source>Applying Human Factors and Usability Engineering to Medical Devices: Guidance for Industry and Food and Drug Administration Staff</source><year>2016</year><access-date>2026-04-10</access-date><publisher-name>Food and Drug Administration</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://www.fda.gov/media/80481/download">https://www.fda.gov/media/80481/download</ext-link></comment></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>Kushniruk</surname><given-names>AW</given-names> </name><name name-style="western"><surname>Patel</surname><given-names>VL</given-names> </name></person-group><article-title>Cognitive and usability engineering methods for the evaluation of clinical information systems</article-title><source>J Biomed Inform</source><year>2004</year><month>02</month><volume>37</volume><issue>1</issue><fpage>56</fpage><lpage>76</lpage><pub-id pub-id-type="doi">10.1016/j.jbi.2004.01.003</pub-id><pub-id pub-id-type="medline">15016386</pub-id></nlm-citation></ref><ref id="ref25"><label>25</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Or</surname><given-names>CK</given-names> </name><name name-style="western"><surname>Chan</surname><given-names>AHS</given-names> </name></person-group><article-title>Inspection methods for usability evaluation</article-title><source>User Experience Methods and Tools in Human-Computer Interaction</source><year>2024</year><publisher-name>CRC Press</publisher-name><fpage>170</fpage><lpage>192</lpage><pub-id pub-id-type="doi">10.1201/9781003495161-7</pub-id></nlm-citation></ref><ref id="ref26"><label>26</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Rochat</surname><given-names>J</given-names> </name><name name-style="western"><surname>Ehrler</surname><given-names>F</given-names> </name><name name-style="western"><surname>Siebert</surname><given-names>JN</given-names> </name><name name-style="western"><surname>Ricci</surname><given-names>A</given-names> </name><name name-style="western"><surname>Garretas Ruiz</surname><given-names>V</given-names> </name><name name-style="western"><surname>Lovis</surname><given-names>C</given-names> </name></person-group><article-title>Usability testing of a patient-centered mobile health app for supporting and guiding the pediatric emergency department patient journey: mixed methods study</article-title><source>JMIR Pediatr Parent</source><year>2022</year><month>03</month><day>15</day><volume>5</volume><issue>1</issue><fpage>e25540</fpage><pub-id pub-id-type="doi">10.2196/25540</pub-id><pub-id pub-id-type="medline">35289754</pub-id></nlm-citation></ref><ref id="ref27"><label>27</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Inal</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Wake</surname><given-names>JD</given-names> </name><name name-style="western"><surname>Guribye</surname><given-names>F</given-names> </name><name name-style="western"><surname>Nordgreen</surname><given-names>T</given-names> </name></person-group><article-title>Usability evaluations of mobile mental health technologies: systematic review</article-title><source>J Med Internet Res</source><year>2020</year><month>01</month><day>6</day><volume>22</volume><issue>1</issue><fpage>e15337</fpage><pub-id pub-id-type="doi">10.2196/15337</pub-id><pub-id pub-id-type="medline">31904579</pub-id></nlm-citation></ref><ref id="ref28"><label>28</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Sauro</surname><given-names>J</given-names> </name><name name-style="western"><surname>Lewis</surname><given-names>JR</given-names> </name></person-group><source>Quantifying the User Experience: Practical Statistics for User Research</source><year>2016</year><publisher-name>Morgan Kaufmann Publishers</publisher-name><pub-id pub-id-type="doi">10.1016/B978-0-12-802308-2.00002-3</pub-id><pub-id pub-id-type="other">0128025484</pub-id></nlm-citation></ref><ref id="ref29"><label>29</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Clarke</surname><given-names>K</given-names> </name><name name-style="western"><surname>Al-Mukhtar</surname><given-names>A</given-names> </name><name name-style="western"><surname>Alim</surname><given-names>L</given-names> </name><etal/></person-group><article-title>Using mixed reality simulation to improve junior medical trainees&#x2019; preparedness to manage high-acuity trauma</article-title><source>BMJ Open Qual</source><year>2024</year><month>04</month><day>8</day><volume>13</volume><issue>2</issue><fpage>e002575</fpage><pub-id pub-id-type="doi">10.1136/bmjoq-2023-002575</pub-id><pub-id pub-id-type="medline">38589055</pub-id></nlm-citation></ref><ref id="ref30"><label>30</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Wiklund</surname><given-names>ME</given-names> </name><name name-style="western"><surname>Kendler</surname><given-names>J</given-names> </name><name name-style="western"><surname>Strochlic</surname><given-names>AY</given-names> </name></person-group><source>Usability Testing of Medical Devices</source><year>2015</year><publisher-name>CRC Press</publisher-name><pub-id pub-id-type="doi">10.1201/b19082</pub-id><pub-id pub-id-type="other">1466595892</pub-id></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>Yen</surname><given-names>PY</given-names> </name><name name-style="western"><surname>Bakken</surname><given-names>S</given-names> </name></person-group><article-title>Review of health information technology usability study methodologies</article-title><source>J Am Med Inform Assoc</source><year>2012</year><volume>19</volume><issue>3</issue><fpage>413</fpage><lpage>422</lpage><pub-id pub-id-type="doi">10.1136/amiajnl-2010-000020</pub-id><pub-id pub-id-type="medline">21828224</pub-id></nlm-citation></ref><ref id="ref32"><label>32</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Richardson</surname><given-names>S</given-names> </name><name name-style="western"><surname>Mishuris</surname><given-names>R</given-names> </name><name name-style="western"><surname>O&#x2019;Connell</surname><given-names>A</given-names> </name><etal/></person-group><article-title>&#x201C;Think aloud&#x201D; and &#x201C;Near live&#x201D; usability testing of two complex clinical decision support tools</article-title><source>Int J Med Inform</source><year>2017</year><month>10</month><volume>106</volume><fpage>1</fpage><lpage>8</lpage><pub-id pub-id-type="doi">10.1016/j.ijmedinf.2017.06.003</pub-id><pub-id pub-id-type="medline">28870378</pub-id></nlm-citation></ref><ref id="ref33"><label>33</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>IBM computer usability satisfaction questionnaires: psychometric evaluation and instructions for use</article-title><source>Int J Hum Comput Interact</source><year>1995</year><month>01</month><volume>7</volume><issue>1</issue><fpage>57</fpage><lpage>78</lpage><pub-id pub-id-type="doi">10.1080/10447319509526110</pub-id></nlm-citation></ref><ref id="ref34"><label>34</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>Psychometric evaluation of the PSSUQ using data from five years of usability studies</article-title><source>Int J Hum Comput Interact</source><year>2002</year><month>09</month><volume>14</volume><issue>3-4</issue><fpage>463</fpage><lpage>488</lpage><pub-id pub-id-type="doi">10.1080/10447318.2002.9669130</pub-id></nlm-citation></ref><ref id="ref35"><label>35</label><nlm-citation citation-type="report"><person-group person-group-type="author"><name name-style="western"><surname>Bastien</surname><given-names>JMC</given-names> </name><name name-style="western"><surname>Scapin</surname><given-names>DL</given-names> </name></person-group><article-title>Ergonomic criteria for the evaluation of human-computer interfaces</article-title><source>INRIA</source><year>1993</year><access-date>2026-04-10</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://blocnotes.iergo.fr/wp-content/uploads/2011/04/criteres.pdf">https://blocnotes.iergo.fr/wp-content/uploads/2011/04/criteres.pdf</ext-link></comment></nlm-citation></ref><ref id="ref36"><label>36</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Nielsen</surname><given-names>J</given-names> </name></person-group><article-title>Usability inspection methods</article-title><source>Conference Companion on Human Factors in Computing Systems</source><access-date>2026-04-10</access-date><publisher-name>Association for Computing Machinery</publisher-name><fpage>413</fpage><lpage>414</lpage><comment><ext-link ext-link-type="uri" xlink:href="https://dl.acm.org/doi/pdf/10.1145/259963.260531">https://dl.acm.org/doi/pdf/10.1145/259963.260531</ext-link></comment></nlm-citation></ref><ref id="ref37"><label>37</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Scapin</surname><given-names>DL</given-names> </name><name name-style="western"><surname>Bastien</surname><given-names>JMC</given-names> </name></person-group><article-title>Ergonomic criteria for evaluating the ergonomic quality of interactive systems</article-title><source>Behav Inf Technol</source><year>1997</year><month>01</month><volume>16</volume><issue>4-5</issue><fpage>220</fpage><lpage>231</lpage><pub-id pub-id-type="doi">10.1080/014492997119806</pub-id></nlm-citation></ref><ref id="ref38"><label>38</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Barton</surname><given-names>HJ</given-names> </name><name name-style="western"><surname>Salwei</surname><given-names>ME</given-names> </name><name name-style="western"><surname>Rutkowski</surname><given-names>RA</given-names> </name><etal/></person-group><article-title>Evaluating the usability of an emergency department after visit summary: staged heuristic evaluation</article-title><source>JMIR Hum Factors</source><year>2023</year><month>03</month><day>9</day><volume>10</volume><fpage>e43729</fpage><pub-id pub-id-type="doi">10.2196/43729</pub-id><pub-id pub-id-type="medline">36892941</pub-id></nlm-citation></ref><ref id="ref39"><label>39</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Hunter</surname><given-names>JD</given-names> </name></person-group><article-title>Matplotlib: a 2D graphics Environment</article-title><source>Comput Sci Eng</source><year>2007</year><volume>9</volume><issue>3</issue><fpage>90</fpage><lpage>95</lpage><pub-id pub-id-type="doi">10.1109/MCSE.2007.55</pub-id></nlm-citation></ref><ref id="ref40"><label>40</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Hunt</surname><given-names>EA</given-names> </name><name name-style="western"><surname>Walker</surname><given-names>AR</given-names> </name><name name-style="western"><surname>Shaffner</surname><given-names>DH</given-names> </name><name name-style="western"><surname>Miller</surname><given-names>MR</given-names> </name><name name-style="western"><surname>Pronovost</surname><given-names>PJ</given-names> </name></person-group><article-title>Simulation of in-hospital pediatric medical emergencies and cardiopulmonary arrests: highlighting the importance of the first 5 minutes</article-title><source>Pediatrics</source><year>2008</year><month>01</month><volume>121</volume><issue>1</issue><fpage>e34</fpage><lpage>43</lpage><pub-id pub-id-type="doi">10.1542/peds.2007-0029</pub-id><pub-id pub-id-type="medline">18166542</pub-id></nlm-citation></ref><ref id="ref41"><label>41</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Sweller</surname><given-names>J</given-names> </name><name name-style="western"><surname>van Merri&#x00EB;nboer</surname><given-names>JJG</given-names> </name><name name-style="western"><surname>Paas</surname><given-names>F</given-names> </name></person-group><article-title>Cognitive architecture and instructional design: 20 years later</article-title><source>Educ Psychol Rev</source><year>2019</year><month>06</month><volume>31</volume><issue>2</issue><fpage>261</fpage><lpage>292</lpage><pub-id pub-id-type="doi">10.1007/s10648-019-09465-5</pub-id></nlm-citation></ref><ref id="ref42"><label>42</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>McEvoy</surname><given-names>MD</given-names> </name><name name-style="western"><surname>Field</surname><given-names>LC</given-names> </name><name name-style="western"><surname>Moore</surname><given-names>HE</given-names> </name><name name-style="western"><surname>Smalley</surname><given-names>JC</given-names> </name><name name-style="western"><surname>Nietert</surname><given-names>PJ</given-names> </name><name name-style="western"><surname>Scarbrough</surname><given-names>SH</given-names> </name></person-group><article-title>The effect of adherence to ACLS protocols on survival of event in the setting of in-hospital cardiac arrest</article-title><source>Resuscitation</source><year>2014</year><month>01</month><volume>85</volume><issue>1</issue><fpage>82</fpage><lpage>87</lpage><pub-id pub-id-type="doi">10.1016/j.resuscitation.2013.09.019</pub-id><pub-id pub-id-type="medline">24103233</pub-id></nlm-citation></ref><ref id="ref43"><label>43</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Guetterman</surname><given-names>TC</given-names> </name><name name-style="western"><surname>Kellenberg</surname><given-names>JE</given-names> </name><name name-style="western"><surname>Krein</surname><given-names>SL</given-names> </name><etal/></person-group><article-title>Nursing roles for in-hospital cardiac arrest response: higher versus lower performing hospitals</article-title><source>BMJ Qual Saf</source><year>2019</year><month>11</month><volume>28</volume><issue>11</issue><fpage>916</fpage><lpage>924</lpage><pub-id pub-id-type="doi">10.1136/bmjqs-2019-009487</pub-id><pub-id pub-id-type="medline">31420410</pub-id></nlm-citation></ref><ref id="ref44"><label>44</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Schatz</surname><given-names>A</given-names> </name><name name-style="western"><surname>Osterhoff</surname><given-names>G</given-names> </name><name name-style="western"><surname>Georgi</surname><given-names>C</given-names> </name><name name-style="western"><surname>Joeres</surname><given-names>F</given-names> </name><name name-style="western"><surname>Neumuth</surname><given-names>T</given-names> </name><name name-style="western"><surname>Rockstroh</surname><given-names>M</given-names> </name></person-group><article-title>Improving preparation in the emergency trauma room: the development and impact of real-time data transfer and dashboard visualization system</article-title><source>Int J Comput Assist Radiol Surg</source><year>2025</year><month>02</month><volume>20</volume><issue>2</issue><fpage>301</fpage><lpage>310</lpage><pub-id pub-id-type="doi">10.1007/s11548-024-03256-2</pub-id><pub-id pub-id-type="medline">39259482</pub-id></nlm-citation></ref><ref id="ref45"><label>45</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Siebert</surname><given-names>JN</given-names> </name><name name-style="western"><surname>Ehrler</surname><given-names>F</given-names> </name><name name-style="western"><surname>Gervaix</surname><given-names>A</given-names> </name><etal/></person-group><article-title>Adherence to AHA guidelines when adapted for augmented reality glasses for assisted pediatric cardiopulmonary resuscitation: a randomized controlled trial</article-title><source>J Med Internet Res</source><year>2017</year><month>05</month><day>29</day><volume>19</volume><issue>5</issue><fpage>e183</fpage><pub-id pub-id-type="doi">10.2196/jmir.7379</pub-id><pub-id pub-id-type="medline">28554878</pub-id></nlm-citation></ref><ref id="ref46"><label>46</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Cheng</surname><given-names>A</given-names> </name><name name-style="western"><surname>Fijacko</surname><given-names>N</given-names> </name><name name-style="western"><surname>Lockey</surname><given-names>A</given-names> </name><etal/></person-group><article-title>Use of augmented and virtual reality in resuscitation training: a systematic review</article-title><source>Resusc Plus</source><year>2024</year><month>06</month><volume>18</volume><issue>100643</issue><fpage>100643</fpage><pub-id pub-id-type="doi">10.1016/j.resplu.2024.100643</pub-id><pub-id pub-id-type="medline">38681058</pub-id></nlm-citation></ref><ref id="ref47"><label>47</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Hart</surname><given-names>SG</given-names> </name></person-group><article-title>NASA-task load index (NASA-TLX); 20 years later</article-title><source>Proceedings of the Human Factors and Ergonomics Society Annual Meeting</source><year>2006</year><publisher-name>Sage Publications</publisher-name><pub-id pub-id-type="doi">10.1177/154193120605000909</pub-id></nlm-citation></ref></ref-list><app-group><supplementary-material id="app1"><label>Multimedia Appendix 1</label><p>Updated TeamScreen prototype display during a simulated pediatric in-hospital cardiac arrest (Ventricular Fibrillation scenario), showing the cardiopulmonary resuscitation (CPR) algorithm and reversible causes (left); timers and task lists for current, secondary and next actions (center); and the &#x201C;Completed Tasks&#x201D; panel with a medications table that presents the final weight-based doses and administration times visible to the entire team.</p><media xlink:href="humanfactors_v13i1e78736_app1.png" xlink:title="PNG File, 532 KB"/></supplementary-material><supplementary-material id="app2"><label>Multimedia Appendix 2</label><p>Post-Study System Usability Questionnaire (PSSUQ) statements.</p><media xlink:href="humanfactors_v13i1e78736_app2.docx" xlink:title="DOCX File, 18 KB"/></supplementary-material></app-group></back></article>