<?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 Med Inform</journal-id><journal-id journal-id-type="publisher-id">medinform</journal-id><journal-id journal-id-type="index">7</journal-id><journal-title>JMIR Medical Informatics</journal-title><abbrev-journal-title>JMIR Med Inform</abbrev-journal-title><issn pub-type="epub">2291-9694</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">v14i1e84900</article-id><article-id pub-id-type="doi">10.2196/84900</article-id><article-categories><subj-group subj-group-type="heading"><subject>Original Paper</subject></subj-group></article-categories><title-group><article-title>Candidate Passive Sensor Suite Technologies for Tactical Combat Casualty Care Environments: Comparative Assessment Study</article-title></title-group><contrib-group><contrib contrib-type="author"><name name-style="western"><surname>Stoor-Burning</surname><given-names>Ericka</given-names></name><degrees>MS, DHS-C, PA-C, CHSE</degrees><xref ref-type="aff" rid="aff1"/></contrib><contrib contrib-type="author"><name name-style="western"><surname>Gaudaen</surname><given-names>James</given-names></name><degrees>MA</degrees><xref ref-type="aff" rid="aff1"/></contrib><contrib contrib-type="author"><name name-style="western"><surname>Pavliscsak</surname><given-names>Holly</given-names></name><degrees>BS, MHSA</degrees><xref ref-type="aff" rid="aff1"/></contrib><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>Little</surname><given-names>Jeanette</given-names></name><degrees>BS, MS</degrees><xref ref-type="aff" rid="aff1"/></contrib></contrib-group><aff id="aff1"><institution>United States Army Institute for Surgical Research</institution><addr-line>Building 1054, Patchel Street</addr-line><addr-line>Fort Detrick</addr-line><addr-line>MD</addr-line><country>United States</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Benis</surname><given-names>Arriel</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Al-Muqarm</surname><given-names>Abbas</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Keeney-Bonthrone</surname><given-names>Toby P</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Jeanette Little, BS, MS, United States Army Institute for Surgical Research, Building 1054, Patchel Street, Fort Detrick, MD, 21702, United States, 1 706-993-6862; <email>jeanette.r.little.civ@health.mil</email></corresp></author-notes><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>24</day><month>6</month><year>2026</year></pub-date><volume>14</volume><elocation-id>e84900</elocation-id><history><date date-type="received"><day>26</day><month>09</month><year>2025</year></date><date date-type="rev-recd"><day>27</day><month>04</month><year>2026</year></date><date date-type="accepted"><day>17</day><month>05</month><year>2026</year></date></history><copyright-statement>&#x00A9; Ericka Stoor-Burning, James Gaudaen, Holly Pavliscsak, Jeanette Little. Originally published in JMIR Medical Informatics (<ext-link ext-link-type="uri" xlink:href="https://medinform.jmir.org">https://medinform.jmir.org</ext-link>), 24.6.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 Medical Informatics, is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://medinform.jmir.org/">https://medinform.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://medinform.jmir.org/2026/1/e84900"/><abstract><sec><title>Background</title><p>The United States Army Institute for Surgical Research conducted an analysis of 3 prototype sensor suites; all candidates were designed to passively document care delivery in tactical combat casualty care environments.</p></sec><sec><title>Objective</title><p>This study aims to ensure sensor suites remain resilient and adaptive in complex battlefield environments. This research effort conducts a systematic comparative assessment of prototype solutions.</p></sec><sec sec-type="methods"><title>Methods</title><p>The assessment methodology prioritized functionality, usability, and performance. The assessment consisted of three phases: (1) tabletop evaluations, (2) simulated use testing, and (3) a sensor suite rodeo simulation event. The second and third phases included human participants leveraging the technology prototypes in hyperrealistic tactical combat casualty care simulation environments. Additionally, the third phase allowed the researchers to assess the performance of each prototype in a range of operational environmental lighting conditions.</p></sec><sec sec-type="results"><title>Results</title><p>During the tabletop evaluation phase, all 3 prototype sensor suite solutions demonstrated acceptable results (&#x2265;1) in the technical specification assessment. The 2-part heuristic analysis revealed variability, where the least complex configurations received the highest assessment scores. To capture and record raw data, scores ranged from 44.6 to 87 on a 100-point scale. To offload and export the raw data, scores ranged from 22.9 to 87.5 on a 100-point scale. During simulated user testing, all 3 sensor suites achieved passing quantitative scores (&#x2265;60); the system usability scores (SUS) ranged from 60 to 85 on a 100-point scale. More complex technology configurations received higher usability scores. From a qualitative perspective, vital sign monitor latency display issues led to reliability concerns. All 3 prototypes successfully generated raw data; the individual outputs ranged from 0.06 to 0.13 GB/minute. During the sensor suite rodeo simulation event, all 3 sensor suites achieved passing quantitative scores (&#x2265;60); the SUS ranged from 66.7 to 86.7 on a 100-point scale; the most complex technology prototype configuration scored higher. Qualitative findings identified data transfer issues with large file sizes and pairing issues with vital sign monitors. All 3 prototypes successfully generated raw data; the individual outputs varied (ranging from 0.012 to 0.24 GB/min) based on the environmental lighting conditions (full sun, indoor lighting, and low light). However, from a data quality perspective, only 1 camera component produced viable video data in all 3 environments.</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>The comparative assessment revealed opportunities to combine the strengths of both approaches in a next-generation implementation. This preliminary assessment was constrained by several factors: (1) effective tracking of consumable medical supplies, (2) advancement of artificial intelligence algorithms to process the raw data, and (3) ability to manage multiple casualties or patients. Follow-on evaluations are needed to address these limitations. This systematic, 3-part methodology evaluates early-stage sensor suite prototypes and provides a reproducible framework for advancing battlefield medical technologies.</p></sec><sec sec-type="registered-report"><title>International Registered Report Identifier (IRRID)</title><p>RR2-10.2196/67673</p></sec></abstract><kwd-group><kwd>autonomous medical documentation</kwd><kwd>comparative technology performance assessment</kwd><kwd>military medical documentation</kwd><kwd>multi-phase assessment methodology</kwd><kwd>passive medical documentation</kwd><kwd>tactical combat casualty care</kwd><kwd>prototype sensor suites</kwd><kwd>simulation-based assessment</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><p>The Military Health System faces a persistent challenge: while medical documentation is mandated at all echelons [<xref ref-type="bibr" rid="ref1">1</xref>], providers in high-intensity combat situations must prioritize lifesaving measures over record-keeping, often leading to significant data gaps. Manual, paper-based documentation is not only burdensome but also prone to result-interpretation errors due to varying environmental factors.</p><p>To address this challenge, the United States Army Institute of Surgical Research (USAISR), formerly known as the Telemedicine and Advanced Technology Research Center, commenced an effort to prototype systems specifically designed to passively document care delivery within the tactical combat casualty care (TCCC) environment. The sensor suite systems used individual commercial-off-the-shelf components integrated with an edge computing device and/or end user device as shown in <xref ref-type="table" rid="table1">Table 1</xref>. The 3 specific systems were selected by the government after their respective proposed approaches were determined to have merit.</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>Sensor suite prototype configurations.</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom"/><td align="left" valign="bottom">Medical Wearable Audio Video Entry</td><td align="left" valign="bottom">Autonomous Communication Medical Ecosystem</td><td align="left" valign="bottom">Point of Treatment Aggregator</td></tr></thead><tbody><tr><td align="left" valign="top">Audio or video component</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>PatrolEyes visible or near infrared camera</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>GoPro Hero 13 Black action camera</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>MOHOC M2 <sc>c</sc>amera</p></list-item><list-item><p>Sennheiser Lapel microphone</p></list-item></list></td></tr><tr><td align="left" valign="top">Patient vital sign monitor<break/>component</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Vivalink electrocardiogram patch</p></list-item><list-item><p>Vivalink pulse oximeter</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Masimo MightySat pulse oximeter</p></list-item></list></td><td align="left" valign="top">&#x2014;<sup><xref ref-type="table-fn" rid="table1fn1">a</xref></sup></td></tr><tr><td align="left" valign="top">Provider activity tracking component</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Electromyography armband</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Movella DOTs</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Movella DOTs</p></list-item></list></td></tr><tr><td align="left" valign="top">Consumable medical supply use tracking component</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Near field communication tags</p></list-item></list></td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top">Edge computing device</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>NVIDIA Jetson Orin Nano</p></list-item></list></td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top">End user device</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Samsung Galaxy S23 FE smartphone</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Samsung Galaxy S21 smartphone</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Dell Latitude 7230 Rugged Extreme tablet</p></list-item></list></td></tr></tbody></table><table-wrap-foot><fn id="table1fn1"><p><sup>a</sup>Not applicable.</p></fn></table-wrap-foot></table-wrap><p>Between September 2023 and July 2025, the USAISR conducted a formal analysis of the 3 early-stage prototype sensor suites: the Medical Wearable Audio Video Entry (M-WAVE), the Autonomous Communication Medical Ecosystem (ACME), and the Point of Treatment Aggregator (PoTAg). The results from this initial comparative assessment highlighted opportunities to integrate the unique strengths of each approach, paving the way for a next-generation solution. By identifying complementary features and capabilities among the various prototypes, the assessment established a foundation for designing systems that are resilient and adaptive to complex battlefield environments.</p><p>The systematic, 3-part methodology used to evaluate these early-stage sensor suite prototypes provides a robust and reproducible framework for guiding the future development of advanced medical technologies for the battlefield. This approach not only ensures objective comparison and evaluation of devices or systems but also facilitates iterative improvement based on empirical data. Ultimately, such a structured process accelerates the innovation cycle, enhances decision-making for future investments, and supports the creation of integrated solutions that can better address the dynamic and unpredictable needs of battlefield medicine.</p><p>The premise behind this prototyping effort is that smart devices, defined as context-aware electronic devices capable of autonomous computation and data exchange [<xref ref-type="bibr" rid="ref2">2</xref>], offer a unique solution to this TCCC medical documentation capability gap. By integrating these technologies into sensor suites, they serve as a force multiplier for the TCCC level provider, which includes the following:</p><list list-type="order"><list-item><p>Reduced cognitive load: By automating the capture of patient statuses and caregiver actions, the sensor suite system alleviates the medic&#x2019;s cognitive burden, allowing them to remain fully &#x201C;hands-on&#x201D; with the patient without the distraction of manual documentation [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>].</p></list-item><list-item><p>Data integrity for handoffs: The sensor suite system facilitates the accurate generation of a digital TCCC care, ensuring that life-critical information (including medication dosages and tourniquet times) is seamlessly transferred to the next echelon of care without requiring the medic to pause treatment for manual logging [<xref ref-type="bibr" rid="ref5">5</xref>].</p></list-item><list-item><p>Mass casualty and patient management: Mature sensor suite technologies will enable continuous, simultaneous, and passive monitoring of multiple vital signs across multiple patients through a centralized interface, significantly enhancing a care provider&#x2019;s situational awareness in complex environments [<xref ref-type="bibr" rid="ref6">6</xref>].</p></list-item><list-item><p>Enhanced operational readiness: Near real-time monitoring of physiological parameters and environmental exposures (eg, noise, radiation, chemical agents) ensures that the health and safety of military members are maintained throughout the mission [<xref ref-type="bibr" rid="ref7">7</xref>-<xref ref-type="bibr" rid="ref9">9</xref>].</p></list-item></list><p>In the long term, the resulting sensor suite datasets will empower the development of artificial intelligence (AI) and clinical decision support systems to further aid care delivery in austere environments.</p><p>This comparative assessment evaluates the performance, usability, and refinement needs of these initial prototypes based on four main hypotheses:</p><list list-type="order"><list-item><p>Synchronized passive sensor modalities can establish large, reliable TCCC encounter datasets.</p></list-item><list-item><p>Passively collected data can effectively train future patient documentation algorithms.</p></list-item><list-item><p>Mature algorithms can reliably automate real-time data inputs for digital TCCC cards.</p></list-item><list-item><p>Passive, autonomous collection will eliminate the need for manual care provider input at the point of care (POC), improving both efficiency and accuracy.</p></list-item></list></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>Overview</title><p>There were three phases to the assessment: (1) tabletop evaluations, (2) simulated use testing, and (3) a sensor suite rodeo simulation event as shown in <xref ref-type="fig" rid="figure1">Figure 1</xref>. The assessment methodology prioritized 3 factors: functionality, usability, and performance. For each prototype, both the entirety of the sensor suite configuration and the individual components were included in the assessment process.</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>Sensor suite assessment phases.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="medinform_v14i1e84900_fig01.png"/></fig></sec><sec id="s2-2"><title>Study Design or Recruitment</title><p>All nonpersonally identifiable information data collected for this assessment were conducted under an exempt research protocol (protocol ID# M-11061). A more expansive, human subject research protocol assessment methodology (protocol ID# M-11057) for the sensor suite prototype assessments has been previously described in the Journal of Medical Internet Research [<xref ref-type="bibr" rid="ref10">10</xref>].</p></sec><sec id="s2-3"><title>Analysis</title><p>The sensor suite analysis had 3 discrete phases (<xref ref-type="fig" rid="figure1">Figure 1</xref>). The first phase was a benchtop assessment of each component of the individual sensor suites, and the second and third phases required the use of hyper-realistic TCCC simulation scenarios with human subject participants engaging with the sensor suite technologies.</p></sec><sec id="s2-4"><title>Phase 1: Tabletop Evaluations</title><p>The initial phase of the assessment process took place in a controlled laboratory environment and was conducted by independent evaluators systematically reviewing each component of the 3 sensor suite configurations (<xref ref-type="fig" rid="figure2">Figure 2</xref>). There were two parts to this tabletop evaluation: (1) a technical specification assessment and (2) a 2-part heuristic analysis.</p><fig position="float" id="figure2"><label>Figure 2.</label><caption><p>Tabletop evaluations.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="medinform_v14i1e84900_fig02.png"/></fig><sec id="s2-4-1"><title>Phase 1A: Technical Specification Assessment</title><p>Evaluators considered the overarching sensor suite&#x2019;s technical specifications and documentation associated with the individual components (<xref ref-type="other" rid="box1">Textbox 1</xref>). The validity of the technical specifications and documentation was assessed for each defined top-level attribute (<xref ref-type="table" rid="table2">Table 2</xref>).</p><boxed-text id="box1"><title> Sensor suite specifications.</title><p><bold>Technology</bold></p><list list-type="bullet"><list-item><p>Suite includes at least 2 commercial off-the-shelf sensors and a physical data hub</p></list-item><list-item><p>Commercial off-the-shelf sensors include audio, video, physiological monitors, wearables, and radio frequency identification technologies</p></list-item><list-item><p>Sensor components are established technologies, not prototypes</p></list-item></list><list list-type="bullet"><list-item><p>The suite is reliable, effective, and easy to use</p></list-item><list-item><p>Suite is size, weight, and power efficient, runs for at least 2 hours</p></list-item><list-item><p>Suite enables passive monitoring of patients, caregivers, and/or resources</p></list-item><list-item><p>Suite is suitable for collecting combat casualty care data</p></list-item><list-item><p>Suite is fit for austere, tactical environments</p></list-item></list><p><bold>Data outputs</bold></p><list list-type="bullet"><list-item><p>Meets industry standards, is not proprietary</p></list-item><list-item><p>Data outputs include raw sensor data</p></list-item><list-item><p>Data separate patient and caregiver data</p></list-item><list-item><p>All data are downloadable, organized, time-stamped, and include descriptive tags</p></list-item><list-item><p>Data processing is efficient and effective</p></list-item></list><p><bold>Technical documentation</bold></p><list list-type="bullet"><list-item><p>Lists targeted tactical combat casualty care fields</p></list-item><list-item><p>Details data standards used</p></list-item><list-item><p>Estimates data output or bandwidth</p></list-item><list-item><p>Estimates power or battery needs</p></list-item><list-item><p>Describes software</p></list-item><list-item><p>Provides user manuals</p></list-item><list-item><p>Includes both a training and project plan</p></list-item></list></boxed-text><table-wrap id="t2" position="float"><label>Table 2.</label><caption><p>Technical specification attributes.</p></caption><table id="table2" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Attribute</td><td align="left" valign="bottom">Sub attribute</td></tr></thead><tbody><tr><td align="left" valign="top">Systemwide factors</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Automatic data aggregation</p></list-item><list-item><p>Data aggregation system</p></list-item><list-item><p>Synchronized data format</p></list-item><list-item><p>Time synchronization</p></list-item><list-item><p>Data processing steps</p></list-item><list-item><p>Key metadata or tags</p></list-item><list-item><p>Approximate cost</p></list-item></list></td></tr><tr><td align="left" valign="top">Form factor</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Size (width, length, height)</p></list-item><list-item><p>Weight</p></list-item></list></td></tr><tr><td align="left" valign="top">Device power requirements</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Power modality</p></list-item><list-item><p>Approximate battery life</p></list-item></list></td></tr><tr><td align="left" valign="top">Interface</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Attaches to (eg, caregiver or patient)</p></list-item><list-item><p>Attachment method</p></list-item><list-item><p>User interface modality</p></list-item><list-item><p>Passive or active collection</p></list-item><list-item><p>Required actions (if active)</p></list-item></list></td></tr><tr><td align="left" valign="top">Data capture and storage</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Data type</p></list-item><list-item><p>Data format</p></list-item><list-item><p>Data streams</p></list-item><list-item><p>Data intended use case</p></list-item><list-item><p>Key metadata</p></list-item><list-item><p>Software required to access data</p></list-item><list-item><p>Real-time data availability</p></list-item><list-item><p>Time recording modality</p></list-item><list-item><p>Sample or frame rate</p></list-item></list></td></tr><tr><td align="left" valign="top">Device flexibility</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Key settings</p></list-item></list></td></tr><tr><td align="left" valign="top">Data transfer</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Wireless transfer capabilities</p></list-item><list-item><p>Connection type</p></list-item></list></td></tr></tbody></table></table-wrap><p>Each component of the sensor suite was independently evaluated by 2 separate raters using a 3-point scale (0=lowest, 2=highest). The scores were then consolidated; if the raters provided different scores for the same component, the lower score was recorded as the official score for that component. Next, the scores for all the individual components were averaged.</p></sec><sec id="s2-4-2"><title>Phase 1B: Heuristic Analysis</title><p>A heuristic evaluation is a systematic inspection methodology to quantify the usability of the sensor suite prototype interface design. During this phase of the analysis, 2 subject matter expert evaluators examined the interface and determined compliance with recognized usability principles, specifically the Nielsen Norman Group 10 Usability Heuristics model [<xref ref-type="bibr" rid="ref7">7</xref>], as outlined in <xref ref-type="table" rid="table3">Table 3</xref>.</p><table-wrap id="t3" position="float"><label>Table 3.</label><caption><p>Nielsen Norman Group&#x2019;s 10 heuristics.</p></caption><table id="table3" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Heuristic</td><td align="left" valign="bottom">Example</td></tr><tr><td align="left" valign="bottom">Visibility of system status</td><td align="left" valign="bottom">Keeps users informed with timely feedback.</td></tr></thead><tbody><tr><td align="left" valign="top">Match between system and real world</td><td align="left" valign="top">Leverages end user language and real-world conventions; avoids jargon and presents information logically.</td></tr><tr><td align="left" valign="top">User control and freedom</td><td align="left" valign="top">Provides clear exits so users can easily undo mistakes.</td></tr><tr><td align="left" valign="top">Consistency and standards</td><td align="left" valign="top">Ensures consistency by following platform and industry conventions.</td></tr><tr><td align="left" valign="top">Error prevention</td><td align="left" valign="top">Prevents problems before they occur; eliminates error-prone conditions or confirms risky actions.</td></tr><tr><td align="left" valign="top">Recognition rather than recall</td><td align="left" valign="top">Reduces memory load by making key elements and information visible or easily accessible.</td></tr><tr><td align="left" valign="top">Flexibility and efficiency of use</td><td align="left" valign="top">Provides shortcuts for experienced users and allows customization of frequent actions.</td></tr><tr><td align="left" valign="top">Esthetic and minimalist design</td><td align="left" valign="top">Removes irrelevant or rarely needed information from the interface.</td></tr><tr><td align="left" valign="top">Help users recognize, diagnose, and record from error</td><td align="left" valign="top">Writes error messages in plain language, clearly stating the problem and solution.</td></tr><tr><td align="left" valign="top">Help and documentation</td><td align="left" valign="top">Aims for a self-explanatory system but provides helpful documentation if needed.</td></tr></tbody></table></table-wrap><p>There were 2 discrete parts to the heuristic assessment. Task 1 focused on the ability of the sensor suite components to capture and record data in a usable fashion (eg, openly accessible, and not using proprietary data formats). Task 2 focused on the ability to offload and leverage the data that were generated by the sensor suite components. To conduct the task 1 heuristic assessment, all the sensor suite components were powered up, connectivity was established in accordance with the performer&#x2019;s documentation, and data collection or recording was commenced. Once this process was completed, the data offloaded from the sensor suites were exported to a secure, cloud-based research data repository (eg, the task 2 heuristic assessment). In instances where the data were not generated by the individual sensor component in task 1, the task 2 heuristic assessment did not occur.</p><p>For each individual sensor suite component, it was assessed across 10 discrete heuristic factors, described in <xref ref-type="table" rid="table3">Table 3</xref>, with a maximum score of 2 per factor resulting in a maximum of 20 total points. Evaluator scores were averaged to determine a final score. Each sensor suite configuration score was then calculated using the sum of the individual components.</p><p>The resulting summary score was then divided by the total possible points a sensor suite could receive, which was based on the total number of component devices multiplied by 20 (eg, number of components &#x00D7; 20). After this division, the resulting number was multiplied by 100 to standardize the 100-point scale, as follows:</p><disp-formula id="E2"><mml:math id="eqn1"><mml:mstyle displaystyle="true" scriptlevel="0"><mml:mrow><mml:mstyle displaystyle="true" scriptlevel="0"><mml:mtext>Sensor suite configuration score</mml:mtext><mml:mo>=</mml:mo><mml:mrow><mml:mo>(</mml:mo><mml:mfrac><mml:mi>s</mml:mi><mml:mrow><mml:mi>n</mml:mi><mml:mo>&#x00D7;</mml:mo><mml:mn>20</mml:mn></mml:mrow></mml:mfrac><mml:mo>)</mml:mo></mml:mrow><mml:mo>&#x00D7;</mml:mo><mml:mn>100</mml:mn></mml:mstyle></mml:mrow></mml:mstyle></mml:math></disp-formula><p>where <italic>s</italic> is the sum of all individual suite component heuristic scores and <italic>n</italic> is the total number of individual sensor suite component devices.</p><p>This scoring process was used for both the task 1 and task 2 heuristic assessments. For the purposes of this assessment, a total score of 60 or higher was considered a passing score, a standard used with other validated usability instruments. In addition to providing numerical scores, each evaluator added comments to their ratings. These qualitative comments were combined into a thematic analysis for each of the heuristics to add more information about the quantitative ratings.</p></sec></sec><sec id="s2-5"><title>Phase 2: Simulated Use Testing</title><p>Simulated use cases involving end user testing, and data quality assessments were conducted as a second phase of the sensor suite evaluation [<xref ref-type="bibr" rid="ref11">11</xref>] (<xref ref-type="fig" rid="figure3">Figure 3</xref>). The simulated use cases were carried out in a controlled field setting, where the prototypes were deployed under carefully managed conditions and known reference points for comparison (<xref ref-type="other" rid="box2">Textbox 2</xref>).</p><fig position="float" id="figure3"><label>Figure 3.</label><caption><p>Simulated use testing.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="medinform_v14i1e84900_fig03.png"/></fig><boxed-text id="box2"><title> Simulated use testing live actor scenarios.</title><p><bold>Clinical presentations</bold></p><list list-type="bullet"><list-item><p>Open tibia or fibula fracture</p></list-item><list-item><p>Minor head laceration</p></list-item><list-item><p>Second degree burn to upper extremity</p></list-item></list><p><bold>Expected treatments</bold></p><list list-type="bullet"><list-item><p>Splinting of leg</p></list-item><list-item><p>Management of minor laceration</p></list-item><list-item><p>Burn management</p></list-item><list-item><p>Initiating intravenous</p></list-item><list-item><p>Administering medications</p></list-item><list-item><p>Hypothermia prevention</p></list-item></list></boxed-text><p>During the simulated use testing phase of the assessment, each sensor suite prototype was used within a high-fidelity simulation where the care provider or medic participant was a TCCC provider (eg, tier 1, 2, and/or 3). The care provider or medic participant performed casualty care on live actors. The simulation team used testing scenarios that were run twice to ensure that a complete dataset was collected during the assessment. Once each simulation was complete, the participant was given two surveys to fill out: a quantitative instrument and a qualitative tool.</p><sec id="s2-5-1"><title>Phase 2A: Quantitative Assessment</title><p>The objective, quantitative instrument selected for this assessment was the System Usability Scale (SUS) [<xref ref-type="bibr" rid="ref12">12</xref>] questionnaire. The SUS instrument is a validated, standardized survey that has been used across all types of systems and technologies to evaluate usability. Once the final SUS scores are calculated, they are stratified against published norms based on the technology types. In general, a total SUS score of 60 or higher is considered passing from a usability perspective, and this widely accepted criterion was used for the sensor suite evaluation.</p></sec><sec id="s2-5-2"><title>Phase 2B: Qualitative Assessment</title><p>The qualitative assessment consisted of specific short answer questions that more specifically targeted the sensor suites that are being assessed in a subjective manner. This assessment was limited in scope to the sensor suite components that were worn by the care provider or medic (eg, audio or video and activity tracking sensor components) during the simulated use case assessment.</p></sec><sec id="s2-5-3"><title>Phase 2C: Data Quality Assessment</title><p>The data quality assessment was conducted by 2 evaluators after the sensor suite data were extracted from simulated use testing events. The primary focus of this assessment was to ascertain the usefulness of the data outputs for algorithms to achieve passive, autonomous documentation based on the defined data output specifications (<xref ref-type="other" rid="box1">Textbox 1</xref>). While the preponderance of this assessment was qualitative and presented in a narrative format, the overall data output quality from each sensor suite configuration was also quantitatively rated. This rating used a 3-point scale, where a &#x201C;2&#x201D; indicated that the data quality satisfied the requirements, a &#x201C;1&#x201D; meant the data quality required additional clarification to determine minimal viability, and a &#x201C;0&#x201D; signified that the data quality did not meet the minimum viability required.</p><p>The scoring process was designed to minimize the risk of overestimating performance or outcomes. By employing stringent criteria and favoring lower or more cautious scores when uncertainty existed, the process ensured that only clear evidence of achievement or competency was rewarded with higher marks. Ambiguous, incomplete, or borderline cases were typically scored on the lower end of the scale, reducing the likelihood of inflating results. Additionally, the use of standardized rubrics and, where applicable, multiple reviewers further contributed to the conservative nature by encouraging consistency and discouraging leniency. This approach ultimately provided a more reliable and defensible assessment, emphasizing accuracy and restraint over optimism or assumption.</p></sec></sec><sec id="s2-6"><title>Phase 3: Sensor Suite Rodeo Simulation Event</title><p>To directly compare each sensor suite configuration, the team conducted a &#x201C;sensor suite rodeo&#x201D; simulation event in March 2025 (<xref ref-type="fig" rid="figure4">Figure 4</xref>). The rodeo event was conducted using 3 different environmental venues (outdoor or full sun, indoor or full lighting, and low-light conditions). The assessment team collected data within each setting, which had 9 discrete clinical TCCC skills [<xref ref-type="bibr" rid="ref13">13</xref>] using both live actions and manikins (<xref ref-type="table" rid="table4">Table 4</xref>). End user feedback was collected after each simulation through the same quantitative and qualitative survey instruments used in the simulated use assessment (eg, phase 2).</p><fig position="float" id="figure4"><label>Figure 4.</label><caption><p>Sensor suite rodeo simulation event.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="medinform_v14i1e84900_fig04.png"/></fig><table-wrap id="t4" position="float"><label>Table 4.</label><caption><p>Sensor suite rodeo simulation event summary.</p></caption><table id="table4" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Lighting conditions</td><td align="left" valign="bottom">Clinical TCCC<sup><xref ref-type="table-fn" rid="table4fn1">a</xref></sup> skills performed</td><td align="left" valign="bottom">Casualty type</td></tr></thead><tbody><tr><td align="left" valign="top">Outdoor or full sun</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Chest needle decompression</p></list-item><list-item><p>Apply pressure dressing to open extremity fracture</p></list-item><list-item><p>Apply chest seal</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Manikin</p></list-item><list-item><p>Live actor with moulage</p></list-item><list-item><p>Live actor with moulage</p></list-item></list></td></tr><tr><td align="left" valign="top">Indoor full lighting</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Nasopharyngeal airway placement</p></list-item><list-item><p>Start intravenous line</p></list-item><list-item><p>Medication administration</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Manikin</p></list-item><list-item><p>Live actor (no moulage)</p></list-item><list-item><p>Live actor with moulage</p></list-item></list></td></tr><tr><td align="left" valign="top">Low-light conditions</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Cricothyrotomy</p></list-item><list-item><p>Tourniquet placement</p></list-item><list-item><p>Pelvic binder placement</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Manikin</p></list-item><list-item><p>Live actor with moulage</p></list-item><list-item><p>Live actor without moulage</p></list-item></list></td></tr></tbody></table><table-wrap-foot><fn id="table4fn1"><p><sup>a</sup>TCCC: tactical combat casualty care.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s2-7"><title>Ethical Considerations</title><sec id="s2-7-1"><title>Institutional Review Board or Ethics Board Approval</title><p>This protocol was reviewed and approved by the United States Army Medical Research and Development Command Institutional Review Board Office, which included human participants&#x2019; ethics review. The approved protocol (#M-11057) was classified as minimal risk to human participants and undergoes annual continuing reviews by the Institutional Review Board Office to ensure the safety and ethical considerations of research on all human participants in our research.</p></sec><sec id="s2-7-2"><title>Informed Consent</title><p>Prior to conducting simulation scenarios, individual participants were provided with a consent form. This form explained the activities, potential risks, and data collection that the principal investigator would like to conduct. If the participant agrees to participate, they are asked to sign the consent form, either in hard copy or electronically.</p></sec><sec id="s2-7-3"><title>Privacy and Confidentiality</title><p>All simulation participants (eg, care providers and simulated patients) are assigned a participant ID to be associated with collected demographics, video, and physiological signal recordings. All data are stored in Department of War (DoW)&#x2013;compliant and Health Insurance Portability and Accountability Act&#x2013;compliant safety and security compliant e-storage facilities. All hard copy documents, including completed consent forms, are stored in locked filing cabinets at the USAISR. Following data collection sessions, all recordings are checked to ensure that any nonconsented individual&#x2019;s identifiable information was not recorded. If any inadvertent recordings were made, the principal investigator or a study team member deleted these segments of recordings. All recordings are stored securely in DoW-approved, USAISR-maintained server or repository, including a network attached storage at Fort Detrick, Maryland. Additionally, photo release waivers for image use in nonresearch activities also accompany the consent forms at the start of participation but are entirely optional for participation in the study.</p></sec><sec id="s2-7-4"><title>Compensation Details</title><p>Military volunteers who meet the eligibility requirements and consent to participate in the study had the opportunity to participate in volunteer hours as a participation incentive. After completion of their participation in the study, the participant may request a letter of participation from the research team. The eligibility for volunteer hours toward service recognition will be determined by the units or offices who grant the volunteer hours. The research team will provide the letter of participation in an electronic format to the participant&#x2019;s email address. This process will be mirrored at all data collection locations. There are no monetary incentives or compensation for this research effort for volunteers.</p></sec></sec></sec><sec id="s3" sec-type="results"><title>Results</title><p>During the first phase of the assessment (eg, the tabletop evaluations), all 3 prototype sensor suite solutions demonstrated acceptable results (scores <underline>&#x003E;</underline>1) during the technical specification assessment. The ACME and PoTAg sensor suites received the maximum possible scores for specific technical specifications. The ACME configuration stood out for its intuitive form factor, and the PoTAg prototype received distinction for its power requirements, data capture and storage, and device flexibility, as noted in <xref ref-type="table" rid="table5">Table 5</xref>.</p><table-wrap id="t5" position="float"><label>Table 5.</label><caption><p>Results of sensor suite system wide technical specifications assessment<sup><xref ref-type="table-fn" rid="table5fn1">a</xref></sup>.</p></caption><table id="table5" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Technical specification</td><td align="left" valign="bottom">M-WAVE<sup><xref ref-type="table-fn" rid="table5fn2">b</xref></sup></td><td align="left" valign="bottom">ACME<sup><xref ref-type="table-fn" rid="table5fn3">c</xref></sup></td><td align="left" valign="bottom">PoTAg<sup><xref ref-type="table-fn" rid="table5fn4">d</xref></sup></td></tr></thead><tbody><tr><td align="left" valign="top"/><td align="left" valign="top">Average score</td><td align="left" valign="top">Average score</td><td align="left" valign="top">Average score</td></tr><tr><td align="left" valign="top">Form factor</td><td align="left" valign="top">1.7</td><td align="left" valign="top">2.0</td><td align="left" valign="top">1.8</td></tr><tr><td align="left" valign="top">Power requirements</td><td align="left" valign="top">1.7</td><td align="left" valign="top">1.8</td><td align="left" valign="top">2</td></tr><tr><td align="left" valign="top">Interface</td><td align="left" valign="top">1.50</td><td align="left" valign="top">1.6</td><td align="left" valign="top">1.3</td></tr><tr><td align="left" valign="top">Data capture and storage</td><td align="left" valign="top">1.8</td><td align="left" valign="top">1.6</td><td align="left" valign="top">2</td></tr><tr><td align="left" valign="top">Device flexibility</td><td align="left" valign="top">1.8</td><td align="left" valign="top">1.8</td><td align="left" valign="top">2</td></tr><tr><td align="left" valign="top">Data transfer</td><td align="left" valign="top">1.8</td><td align="left" valign="top">1.8</td><td align="left" valign="top">1.8</td></tr></tbody></table><table-wrap-foot><fn id="table5fn1"><p><sup>a</sup>The evaluation used a 3-point scale (0=lowest and 2=highest) for scoring each attribute where a score of &#x003E;1 is considered acceptable or passing. Two research team evaluators conducted this tabletop assessment separately; their individual scores were averaged.</p></fn><fn id="table5fn2"><p><sup>b</sup>M-WAVE: Medical Wearable Audio Video Entry.</p></fn><fn id="table5fn3"><p><sup>c</sup>ACME: Autonomous Communication Medical Ecosystem.</p></fn><fn id="table5fn4"><p><sup>d</sup>PoTAg: Point of Treatment Aggregator.</p></fn></table-wrap-foot></table-wrap><p>The results of the 2-part, tabletop-based heuristics analysis revealed variability, where the least complex configuration (ACME) received the highest assessment scores from the research team (<xref ref-type="table" rid="table6">Table 6</xref>). To capture and record raw data, the quantitative assessment results ranged from 44.6 (M-WAVE) to 87 (ACME) on a 100-point scale. To offload and export the raw data, the scoring ranged from 22.9 (M-WAVE) to 87.5 (ACME) on a 100-point scale.</p><table-wrap id="t6" position="float"><label>Table 6.</label><caption><p>Results of heuristic analysis<sup><xref ref-type="table-fn" rid="table6fn1">a</xref></sup>.</p></caption><table id="table6" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Heuristic analysis criteria</td><td align="left" valign="bottom">M-WAVE<sup><xref ref-type="table-fn" rid="table6fn2">b</xref></sup></td><td align="left" valign="bottom">ACME<sup><xref ref-type="table-fn" rid="table6fn3">c</xref></sup></td><td align="left" valign="bottom">PoTAg<sup><xref ref-type="table-fn" rid="table6fn4">d</xref></sup></td></tr></thead><tbody><tr><td align="left" valign="top">Task 1: Capture or record data score</td><td align="left" valign="top">44.9</td><td align="left" valign="top">87</td><td align="left" valign="top">67.5</td></tr><tr><td align="left" valign="top">Task 2: Offload or export data score</td><td align="left" valign="top">22.9</td><td align="left" valign="top">87.5</td><td align="left" valign="top">75</td></tr></tbody></table><table-wrap-foot><fn id="table6fn1"><p><sup>a</sup>Due to the varied number of sensor suite components, scores were adjusted to a 100-point scale (0=lowest and 100=highest). Two research team evaluators conducted this tabletop assessment separately; their individual scores were averaged.</p></fn><fn id="table6fn2"><p><sup>b</sup>M-WAVE: Medical Wearable Audio Video Entry.</p></fn><fn id="table6fn3"><p><sup>c</sup>ACME: Autonomous Communication Medical Ecosystem.</p></fn><fn id="table6fn4"><p><sup>d</sup>PoTAg: Point of Treatment Aggregator.</p></fn></table-wrap-foot></table-wrap><p>During the second phase of the assessment (eg, simulated use testing), the quantitative assessment portion resulted in SUS scores for each sensor suite prototype. The M-WAVE configuration total score was 85, the ACME SUS score was 60, and the PoTAg total score was 80. While all 3 suites received passing scores (&#x003E;60), it is noteworthy that the M-WAVE prototype, which had the lowest phase 1 assessment scores, received the highest usability scores from the TCCC provider end users.</p><p>During simulated user testing, all 3 sensor suites achieved passing quantitative scores (&#x003E;60); the system usability scores (SUS) ranged from 60 to 85 on a 100-point scale. The more complex technology configurations (M-WAVE and PoTAg) received higher usability scores from the TCCC provider end users.</p><p>The qualitative assessment inputs from the simulated use testing were organized thematically by sensor suite prototype, as shown in <xref ref-type="other" rid="box3">Textbox 3</xref>. M-WAVE vital sign monitor latency display issues led to reliability concerns. Additionally, the NFC tags associated with the ACME prototype required active engagement by the TCCC provider, which did not align with the overarching passive data collection objective.</p><boxed-text id="box3"><title> Simulated use testing: qualitative thematic analysis. Thematic qualitative input was provided by 2 tactical combat casualty care (TCCC) providers.</title><p><bold>Medical Wearable Audio Video Entry</bold></p><list list-type="bullet"><list-item><p>Participants found that the use of the Medical Wearable Audio Video Entry sensor suite did not encumber the care delivery process.</p></list-item><list-item><p>One participant noted the bulkiness of the MindRove electromyography armband component, specifically that it would make it hard to roll up their operational camouflage pattern sleeves when required.</p></list-item><list-item><p>With respect to the Vivalink Pulse Oximeter, it was noted that there was a delay in displaying the patient vital signs and pairing with the rest of the sensor suite system.</p></list-item></list><p><bold>Autonomous Communication Medical Ecosystem</bold></p><list list-type="bullet"><list-item><p>Participants found the use of the Autonomous Communication Medical Ecosystem sensor suite was easy to use.</p></list-item><list-item><p>Participants specifically noted that the near-field communication tags interfered with the care delivery workflow and were cumbersome to use.</p></list-item><list-item><p>One participant stated they failed to scan the near-field communication tags in more than one instance during the simulation events.</p></list-item></list><p><bold>Point of Treatment Aggregator</bold></p><list list-type="bullet"><list-item><p>The MOHOC M2 camera and Sennheiser Lapel microphone were unobtrusive, and the hard-wired connections from these components did not get in the way of the care provider or medic actions.</p></list-item><list-item><p>Participants found that the sensor suite did not interfere with care delivery progress.</p></list-item></list></boxed-text><p>The data quality assessment portion revealed that all 3 prototypes successfully generated raw data outputs in file formats that were compliant with the sensor suite specifications (<xref ref-type="other" rid="box1">Textbox 1</xref>). However, the raw data generated by the 3 sensor suite configurations varied significantly in terms of gigabytes/minute (<xref ref-type="table" rid="table7">Table 7</xref>). The M-WAVE configuration generated 0.06 GB/minute of raw data outputs, the PoTAg prototype generated 0.1 GB/minute, and the ACME sensor suite generated 0.13 GB/minute. In disconnected, denied, intermittent, and limited operational environments, where synchronous cloud-based connectivity is not an option, the ability to locally process the raw sensor data efficiently is a priority, so maximum data efficiencies are desired (eg, lower amounts of data per minute). The M-WAVE sensor suite prototype demonstrated the most promise, but all 3 prototypes will require additional refinement to streamline the raw data outputs to rates that are more suitable for processing by local edge compute devices in TCCC environments in the future.</p><table-wrap id="t7" position="float"><label>Table 7.</label><caption><p>Simulated use testing: data file sizes.</p></caption><table id="table7" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Sensor suite</td><td align="left" valign="bottom">GB/min</td></tr></thead><tbody><tr><td align="left" valign="bottom">M-WAVE<sup><xref ref-type="table-fn" rid="table7fn1">a</xref></sup></td><td align="char" char="." valign="bottom">0.06</td></tr><tr><td align="left" valign="bottom">ACME<sup><xref ref-type="table-fn" rid="table7fn2">b</xref></sup></td><td align="char" char="." valign="bottom">0.13</td></tr><tr><td align="left" valign="bottom">PoTAg<sup><xref ref-type="table-fn" rid="table7fn3">c</xref></sup></td><td align="char" char="." valign="bottom">0.10</td></tr></tbody></table><table-wrap-foot><fn id="table7fn1"><p><sup>a</sup>M-WAVE: medical wearable audio video entry.</p></fn><fn id="table7fn2"><p><sup>b</sup>ACME: autonomous communication medical ecosystem.</p></fn><fn id="table7fn3"><p><sup>c</sup>PoTAg: point of treatment aggregator.</p></fn></table-wrap-foot></table-wrap><p>Additionally, the evaluation team noted specific quality constraints about the data generated by all 3 initial prototypes (<xref ref-type="other" rid="box4">Textbox 4</xref>). The M-WAVE camera had the most flexibility in terms of lighting conditions, but the mounting on the TCCC provider had to be refined to a helmet-mounted position from the chest to ensure appropriate field of view. The Movella Dot IMU sensors leveraged by both the ACME and PoTAg prototypes generated concerns about data file sizes and reliability. Finally, the cabling associated with the PoTAg microphone was prone to disconnection, making data outputs unreliable.</p><boxed-text id="box4"><title> Simulated use testing&#x2014;data quality assessment: qualitative thematic analysis. Thematic qualitative input was provided by 2 members of the research team.</title><p><bold>Medical Wearable Audio Video Entry</bold></p><list list-type="bullet"><list-item><p>The PatrolEyes visible or near-infrared camera automatically transitions between the modes based on lighting conditions (visible vs near-infrared).</p></list-item><list-item><p>When the camera was affixed to the chest (as intended by the performer), it provided a narrow field of view that did not align with the care provider or medic&#x2019;s line of sight, which impacts the quality of the video data generated, which in turn could impact future algorithm detection performance.</p></list-item></list><p><bold>Autonomous Communication Medical Ecosystem</bold></p><list list-type="bullet"><list-item><p>The right and left Movella Dot inertial measurement unit (IMU) sensor data are not collected simultaneously into a single data output file as expected; instead, the system generates 2 separate data (.csv format) files. As a result, it is possible to have a slight data differential (milliseconds) between the right and left IMU data files during data collection. The origins of this potential data discrepancy would need to be further explored in future assessments to fully appreciate the impact.</p></list-item></list><p><bold>Point of Treatment Aggregator</bold></p><list list-type="bullet"><list-item><p>During the tactical combat casualty care simulations, one of the Movella Dot sensor components consistently disconnected, and as a result, no IMU activity data for that sensor were generated during that data collection event.</p></list-item><list-item><p>In one collection event, the hard-wired audio connection from the microphone to the end user device disconnected, resulting in a loss of data.</p></list-item></list></boxed-text><p>The third phase of the assessment (eg, sensor suite rodeo simulation assessment) resulted in quantitative, qualitative, and data quality assessments. The sensor suite rodeo was the first opportunity to assess the performance of each prototype sensor suite in a range of operational environmental conditions, rather than a fixed laboratory environment.</p><p>The quantitative assessment portion resulted in separate SUS calculated scores for each sensor suite prototype, with all receiving passing scores (<underline>&#x003E;</underline>60). M-WAVE had a total SUS score of 86.67. ACME&#x2019;s SUS score was 66.67, and the PoTAg received a score of 76.67.</p><p>The SUS scores ranged from 66.7 to 86.7 on a 100-point scale. The M-WAVE sensor suite prototype received the highest usability scores from the TCCC provider end users, mirroring the results from the phase 2 simulated use testing.</p><p>The qualitative assessment inputs of the sensor suite rodeo simulated use testing were organized thematically by sensor suite prototype and further stratified based on simulation participant (TCCC provider) and researcher inputs as shown in (<xref ref-type="other" rid="box5">Textboxes 5</xref> and <xref ref-type="other" rid="box6">6</xref>), respectively. From the simulation participant perspective, the M-WAVE prototype was noted to have latency issues with its vital sign monitor component, and the electromyography armband required acclimation by the simulation end users.</p><boxed-text id="box5"><title> Sensor suite rodeo simulation qualitative assessment: simulation participant thematic analysis. Thematic qualitative input was provided by 3 simulation participant evaluators or tactical combat casualty care (TCCC) providers.</title><p><bold>Medical Wearable Audio Video Entry</bold></p><list list-type="bullet"><list-item><p>Medical Wearable Audio Video Entry sensor suite was easy to use and did not hinder care</p></list-item><list-item><p>Vivalink SpO2 data latency on reduced confidence in accuracy</p></list-item></list><list list-type="bullet"><list-item><p>MindRove electromyography armband and NVIDIA edge computing device felt bulky at first but were not distracting during use</p></list-item></list><p><bold>Autonomous Communication Medical Ecosystem</bold></p><list list-type="bullet"><list-item><p>Autonomous Communication Medical Ecosystem sensor suite was easy to use and did not hinder care</p></list-item></list><list list-type="bullet"><list-item><p>GoPro and Masimo interfaces were familiar to users</p></list-item></list><p><bold>Point of Treatment Aggregator</bold></p><list list-type="bullet"><list-item><p>Point of Treatment Aggregator sensor suite was easy to use and did not hinder care</p></list-item><list-item><p>Audio or video components and wired connections did not interfere with care</p></list-item></list></boxed-text><boxed-text id="box6"><title> Sensor suite rodeo simulation qualitative assessment: researcher thematic analysis. Thematic qualitative input was provided by 4 research team members.</title><p><bold>Medical Wearable Audio Video Entry</bold></p><list list-type="bullet"><list-item><p>Medical Wearable Audio Video Entry (M-WAVE) setup is cumbersome and requires components to sync in a specific order</p></list-item><list-item><p>The M-WAVE app has limited functions, lacks troubleshooting options, and does not clearly show setup status</p></list-item><list-item><p>Large video files do not auto-transfer, and M-WAVE does not notify users of failed transfers</p></list-item><list-item><p>M-WAVE file naming makes offloading multiple events tedious and risks data errors</p></list-item><list-item><p>Offloading less than 5 GB of data from the edge computing device requires third-party software</p></list-item></list><p><bold>Autonomous Communication Medical Ecosystem</bold></p><list list-type="bullet"><list-item><p>Autonomous Communication Medical Ecosystem app was simple and showed clear component statuses</p></list-item><list-item><p>Movella Dot inertial measurement unit setup with end user device was streamlined</p></list-item></list><list list-type="bullet"><list-item><p>Pairing Masimo sensor required toggling Bluetooth, or vital sign monitor data were lost</p></list-item></list><p><bold>Point of Treatment Aggregator</bold></p><list list-type="bullet"><list-item><p>No setup issues with the Point of Treatment Aggregator were noted by the research team</p></list-item><list-item><p>Sennheiser microphone mini-jack connection to the tablet was unreliable due to its proprietary plug</p></list-item></list></boxed-text><p>The researchers conducting assessments of the prototypes noted concerns with the complexity and reliability of the raw data transfers with the M-WAVE prototype, pairing issues with the ACME components, and the vulnerability of hardwired connections on the PoTAg configurations (<xref ref-type="other" rid="box6">Textbox 6</xref>).</p><p>With respect to the data quality assessment, all 3 sensor suite prototypes were able to generate raw data outputs successfully during the sensor suite rodeo simulation event. The sensor suite data outputs varied (ranging from 0.012 to 0.24 GB/min) based on the environmental lighting conditions (full sun, indoor lighting, and low light), as shown in <xref ref-type="fig" rid="figure5">Figure 5</xref>. The M-WAVE prototype generated data at consistent rates regardless of lighting conditions. The PoTAg configuration provided the lowest (most desirable) raw data outputs, even with variability in different lighting conditions. However, from a data quality perspective, only 1 camera component, the visible or near infrared (NIR) camera leveraged by the M-WAVE configuration produced viable video data in all 3 environments.</p><fig position="float" id="figure5"><label>Figure 5.</label><caption><p>Sensor suite rodeo simulation: data file sizes (GB/min). ACME: Autonomous Communication Medical Ecosystem; M-WAVE: Medical Wearable Audio Video Entry; PoTAg: Point of Treatment Aggregator.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="medinform_v14i1e84900_fig05.png"/></fig><p>The evaluation team noted specific data quality constraints, which are highlighted in <xref ref-type="other" rid="box7">Textbox 7</xref>. The camera components leveraged by the ACME and PoTAg prototypes were not optimized for all lighting conditions, whereas the NIR or visible camera leveraged by the M-WAVE solution was ideally suited for all conditions that were assessed in this phase.</p><boxed-text id="box7"><title> Sensor suite rodeo: data quality assessment: qualitative thematic analysis. Thematic qualitative input was provided by 2 research team members.</title><p><bold>Medical Wearable Audio Video Entry</bold></p><list list-type="bullet"><list-item><p>Helmet mounting improved video field of view and made camera adjustment easier. A preview feature before recording is recommended</p></list-item><list-item><p>Medical Wearable Audio Video Entry video was consistently clear in all lighting conditions</p></list-item></list><p><bold>Autonomous Communication Medical Ecosystem</bold></p><list list-type="bullet"><list-item><p>GoPro Hero 13 had poor video quality in low light due to reduced visibility</p></list-item></list><p><bold>Point of Treatment Aggregator</bold></p><list list-type="bullet"><list-item><p>MOHOC M2 video was washed out in bright sunlight outdoors</p></list-item><list-item><p>Sennheiser microphones&#x2019; wired connection caused unreliable and incomplete audio data</p></list-item></list></boxed-text><p>Each of the 3 sensor suite systems assessed during these 3 phased evaluation processes had unique solutions with varying levels of complexity and performance, which directly impacted the results (<xref ref-type="table" rid="table8">Table 8</xref>). None of the sensor suites were fully optimized at this early stage of prototype development, and the systematic assessment of each configuration identified opportunities for improvement in future phases.</p><table-wrap id="t8" position="float"><label>Table 8.</label><caption><p>Summary of sensor suite prototype strengths and weaknesses.</p></caption><table id="table8" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom"/><td align="left" valign="bottom">M-WAVE<sup><xref ref-type="table-fn" rid="table8fn1">a</xref></sup></td><td align="left" valign="bottom">ACME<sup><xref ref-type="table-fn" rid="table8fn2">b</xref></sup></td><td align="left" valign="bottom">PoTAg<sup><xref ref-type="table-fn" rid="table8fn3">c</xref></sup></td></tr></thead><tbody><tr><td align="left" valign="top">Strengths</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>PatrolEyes visible or NIR camera auto-switched modes</p></list-item><list-item><p>MindRove electromyography<sup><xref ref-type="table-fn" rid="table8fn4">d</xref></sup> armband outperformed other IMUs<sup><xref ref-type="table-fn" rid="table8fn6">f</xref></sup></p></list-item><list-item><p>ECD<sup><xref ref-type="table-fn" rid="table8fn7">g</xref></sup> and EUD<sup><xref ref-type="table-fn" rid="table8fn8">h</xref></sup> worked well with files less than 1 GB</p></list-item><list-item><p>Sensor suite data were consistent in all conditions</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Simple setup</p></list-item><list-item><p>VSM<sup><xref ref-type="table-fn" rid="table8fn5">e</xref></sup> component was optimized</p></list-item><list-item><p>Only prototype tracking resource use</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Reliable prototype</p></list-item><list-item><p>Data were efficient but varied slightly by environment</p></list-item></list></td></tr><tr><td align="left" valign="top">Weaknesses</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>No resource usage component</p></list-item><list-item><p>Vivalink ECG<sup><xref ref-type="table-fn" rid="table8fn9">i</xref></sup> Patch and Pulse Oximeter were hard to configure and had latency issues</p></list-item><list-item><p>ECD and EUD could not manage files less than 1 GB</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>NFC<sup><xref ref-type="table-fn" rid="table8fn10">j</xref></sup> resource tracking was poorly received by users and was not passive</p></list-item><list-item><p>Camera struggled in low light conditions</p></list-item><list-item><p>Raw data generation was inefficient and inconsistent across environments</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Limited scope; lacked both VSM and resource usage component</p></list-item><list-item><p>The camera did not perform optimally in bright sunlight, impacting data quality</p></list-item><list-item><p>The directional nature of the Sennheiser Lapel microphone limited audio capture</p></list-item><list-item><p>Specific components required hard-wired connections to the EUD, making it vulnerable to disruptions during use</p></list-item></list></td></tr></tbody></table><table-wrap-foot><fn id="table8fn1"><p><sup>a</sup>M-WAVE: Medical Wearable Audio Video Entry.</p></fn><fn id="table8fn2"><p><sup>b</sup>ACME: Autonomous Communication Medical Ecosystem.</p></fn><fn id="table8fn3"><p><sup>c</sup>PoTAg: Point of Treatment Aggregator.</p></fn><fn id="table8fn4"><p><sup>d</sup>EMG: electromyography.</p></fn><fn id="table8fn5"><p><sup>e</sup>VSM: vital sign monitor.</p></fn><fn id="table8fn6"><p><sup>f</sup>IMU: inertial measurement unit.</p></fn><fn id="table8fn7"><p><sup>g</sup>ECD: edge computing device.</p></fn><fn id="table8fn8"><p><sup>h</sup>EUD: end user device.</p></fn><fn id="table8fn9"><p><sup>i</sup>ECG: electrocardiogram.</p></fn><fn id="table8fn10"><p><sup>j</sup>NFC: near field communication.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><sec id="s4-1"><title>Principal Findings</title><p>This 3-part methodology (<xref ref-type="fig" rid="figure1">Figure 1</xref>) demonstrated the value of employing a systematic methodology for technology assessments, including, but not limited to, future advanced development of sensor suite prototypes. This discovery-based research approach, including tabletop exercises and systematic technological evaluations, serves as a critical precursor to more formal, controlled studies; it narrows down the vast field of possibilities to a manageable number of promising avenues for further investigation.</p><p>While the resulting data from this initial assessment do not yield large enough sample sizes to be assessed for statistical significance, the mixed methods approach is repeatable from both a quantitative and qualitative perspective and can be implemented at a larger scale for more mature technology prototypes.</p><p>There are several limitations to the findings of this initial, early-stage prototype assessment. These constraints are expected at this early stage of the prototype development process, as the continuum of technology refinements is intended to be a multiphase, Agile development process [<xref ref-type="bibr" rid="ref14">14</xref>].</p><p>The first limitation was the lack of a prototype solution that was effective in providing passive tracking of the use of consumable medical supplies at the POC. This is an unmet need based on the results of this initial assessment. Future solutions may be dependent upon computer vision algorithms, where tactical cameras can detect consumable medical supplies (eg, tourniquets, blood products) using AI resources, but this assumption will need to be tested and proven in the future phases.</p><p>A second confounder is that the data quality assessments performed during this initial assessment were constrained to raw data outputs from the individual components. The initial raw data outputs will require efficiencies to be of future value. Furthermore, providing a complete data assessment requires a systematic evaluation of the edge computing component&#x2019;s ability to process AI algorithms in disconnected, denied, intermittent, and limited environments and generate orchestrated and consolidated data outputs. This could not be addressed in this evaluation because the AI algorithms were under development. Future, final data outputs will also need to be assessed for their potential to be exported to patient record systems (eg, Battlefield Assisted Trauma Distributed Observation Kit, Operational Medicine Information Systems&#x2013;Army) and Command and Control systems (eg, MAVIN smart system et al.) in an interoperable fashion to achieve the overarching, autonomous documentation objectives.</p><p>Additionally, the results of this assessment are limited with respect to the sensor suite prototypes&#x2019; abilities to manage multiple patients or casualties at the POC in mass casualty environments.</p><p>Finally, mature sensor suite systems will need to be hardened for the operational environment (eg, ruggedized) and will consider the constraints of cyber and electronic warfare risks. Cyber and electronic warfare protections ensure that future sensor suite technologies for use in TCCC environments do not place service members on the battlefield at risk by generating electronic signatures that can be detected by adversaries. Follow-on development and cyber-specific assessments will be required to address these issues.</p></sec><sec id="s4-2"><title>Conclusions</title><p>The systematic, 3-part methodology leveraged to evaluate the initial, early-stage sensor suite prototypes is a reproducible process to determine the direction of advanced battlefield medical technology capabilities. The outcomes of this initial comparative assessment revealed opportunities to blend the strengths of each sensor suite prototype approach into a next-generation implementation.</p><p>Based on the quantitative results of the tabletop assessment, the form factor of the ACME prototype and the size, weight, and power and data management approaches leveraged by the PoTAg solution should be modeled in future research. The quantitative data from the phase 2 and 3 assessments demonstrate that the M-WAVE configuration was favored by the end users with respect to overall system usability. The raw data output measurements revealed that the M-WAVE provided the most consistent data in all environments, but the PoTAg provided the greatest data efficiencies. All thematic, quantitative data will be leveraged to drive the next generation of sensor suite prototypes.</p><p>Further refinement of the prototype sensor suites will adopt a best-of-breed collaborative approach, leveraging the superior components identified in this assessment from both a quantitative and qualitative perspective into a next-generation unified system. There are several notable commercial-off-the-shelf components recommended to be advanced as best-of-breed candidates: the PatrolEyes visible or NIR camera, the Masimo Pulse Oximeter, and the MindRove EMG armband.</p><p>This systematic evaluation process is a critical step in determining the shape and direction of future medical capabilities on the battlefield. Technologies inserted into military medicine must improve battlefield health care, making it more effective without compromising the quality of care. To that end, the Institute of Surgical Research is committed to providing fair and unbiased assessments of prototype capabilities, which align with key Defense Health Agency and DoW tenets.</p></sec></sec></body><back><ack><p>This sensor suite evaluation was a collaborative, United States Army Institute of Surgical Research&#x2013;wide effort led by members of the Medical Robotics and Autonomous Systems, Science and Technology Innovation Management and Synchronization, and Medical Modeling, Simulation, Information, and Visualization functional teams.</p><p>The following individuals are acknowledged for their direct and indirect support to this effort: Dr Omar Badawi, Ms LeNiqua Ballou, Mr Joe Barrick, SSG Lam Bui, Dr Jonathan Chambers, Mr Valmik Desai, Ms Alix Donnelly, MAJ Clarence Ducummon, Dr Dion Edwards, Ms Stephanie Edwards, Mr Evan Feuer, Mr Nate Fisher, Dr Stephanie Fonda, Ms Bethzaida Gonzalez-Lanham, Ms Ollie Gray, Mr Todd Hall, Ms Tina Hamrick, Ms Airi JungRhee, Mr Daniel Kalala, Ms Courtney Kentrus, Dr Ben Knisley, Ms Buffy Krall, Mr Zach Lattimore, Dr Jaeyeon Lee, Mr Carl Manemeit, Mr Larry Markins, LTC Rachel Morgans, Ms Moriah Newman, COL Jeremy Pamplin, Ms Yema Pizzuto, Ms Tiffany Quach, Mr Matt Quinn, Mr Ethan Quist, CPT Tamara Richardson, Mr Tyler Ring, Ms Triana Rivera-Nichols, Mr Jeff Robbins, Ms Kerri Root, COL Sharon Rosser, Taylor Somers, Mr Mark Spears, Mr Jesse Steffens, SPC Dustin Turner, Ms Ann Trout, Mr Nick Williams, and Mr Chevas Yeoman.</p><p>The authors did not use generative artificial intelligence tools to develop this manuscript. However, during the preparation of this work, the authors used the Grammarly tool to improve language and readability. After using this tool, the authors reviewed and edited the content as needed and take full responsibility for the content of the publication.</p></ack><notes><sec><title>Funding</title><p>The funding for this project (#CO230044) was provided under the Enabling Medical System Technologies Program Area, Combat Casualty Care Portfolio, Defense Health Agency, and Research and Engineering. The Enabling Medical System Technologies Combat Casualty Care portfolio was previously referred to as the Joint Program Office 6 Combat Casualty Care Research Program. The funder did not influence the design of the study or strategies related to its collection, analysis, or interpretation of data.</p></sec><sec><title>Disclaimer</title><p>The views expressed are those of the authors and do not reflect the official policy of the Department of the Army, the Department of War, the Defense Health Agency, or the United States Federal Government.</p></sec><sec><title>Data Availability</title><p>The data obtained in this evaluation effort contain personally identifiable information. According to our approved protocols, to protect the confidentiality of our participants, the Headquarters, Medical Research and Development Command institutional review board (IRB) requires any institution to execute proper agreements between Headquarters, Medical Research and Development Command IRB and their respective local IRB.</p></sec></notes><fn-group><fn fn-type="con"><p>JL, HP, and JG drafted the original manuscript. ESB and JG designed this research. JL, HP, and JG edited the manuscript. All authors read and approved the final manuscript.</p></fn><fn fn-type="conflict"><p>None declared.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">ACME</term><def><p>Autonomous Communication Medical Ecosystem</p></def></def-item><def-item><term id="abb2">AI</term><def><p>artificial intelligence</p></def></def-item><def-item><term id="abb3">DoW</term><def><p>Department of War</p></def></def-item><def-item><term id="abb4">M-WAVE</term><def><p>Medical Wearable Audio Video Entry</p></def></def-item><def-item><term id="abb5">NIR</term><def><p>near infrared</p></def></def-item><def-item><term id="abb6">POC</term><def><p>point of care</p></def></def-item><def-item><term id="abb7">PoTAg</term><def><p>Point of Treatment Aggregator</p></def></def-item><def-item><term id="abb8">SUS</term><def><p>system usability score</p></def></def-item><def-item><term id="abb9">TCCC</term><def><p>Tactical Combat Casualty Care</p></def></def-item><def-item><term id="abb10">USAISR</term><def><p>United States Army Institute for Surgical Research</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="report"><article-title>Tactical Combat Casualty Care (TCCC) guidelines</article-title><year>2024</year><access-date>2026-06-02</access-date><publisher-name>Joint Trauma System (JTS), Committee on Tactical Combat Casualty Care (CoTCCC)</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://learning-media.allogy.com/api/v1/pdf/f4cf1d4e-3191-443a-befc-415838fb04f2/contents">https://learning-media.allogy.com/api/v1/pdf/f4cf1d4e-3191-443a-befc-415838fb04f2/contents</ext-link></comment></nlm-citation></ref><ref id="ref2"><label>2</label><nlm-citation citation-type="report"><person-group person-group-type="author"><name name-style="western"><surname>Veigl</surname><given-names>A</given-names> </name><name name-style="western"><surname>Wardall</surname><given-names>A</given-names> </name><name name-style="western"><surname>Butkus</surname><given-names>C</given-names> </name></person-group><article-title>Smart device evaluation for deployed operations</article-title><year>2021</year><access-date>2026-06-02</access-date><publisher-name>Air Force Research Laboratory, United States Air Force</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://apps.dtic.mil/sti/trecms/pdf/AD1152865.pdf">https://apps.dtic.mil/sti/trecms/pdf/AD1152865.pdf</ext-link></comment></nlm-citation></ref><ref id="ref3"><label>3</label><nlm-citation citation-type="web"><article-title>Reducing the cognitive burden on the modern soldier: leveraging slingshot and GENSS technologies</article-title><source>Asian Military Review</source><access-date>2026-02-04</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.asianmilitaryreview.com/2024/12/reducing-the-cognitive-burden-on-the-modern-soldier-leveraging-slingshot-and-genss-technologies/">https://www.asianmilitaryreview.com/2024/12/reducing-the-cognitive-burden-on-the-modern-soldier-leveraging-slingshot-and-genss-technologies/</ext-link></comment></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>Kodithuwakku Arachchige</surname><given-names>SNK</given-names> </name><name name-style="western"><surname>Burch V</surname><given-names>RF</given-names> </name><name name-style="western"><surname>Chander</surname><given-names>H</given-names> </name><name name-style="western"><surname>Turner</surname><given-names>AJ</given-names> </name><name name-style="western"><surname>Knight</surname><given-names>AC</given-names> </name></person-group><article-title>The use of wearable devices in cognitive fatigue: current trends and future intentions</article-title><source>Theor Issues Ergon Sci</source><year>2022</year><month>05</month><day>4</day><volume>23</volume><issue>3</issue><fpage>374</fpage><lpage>386</lpage><pub-id pub-id-type="doi">10.1080/1463922X.2021.1965670</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>Gaudaen</surname><given-names>JC</given-names> </name><name name-style="western"><surname>Papadopoulos</surname><given-names>A</given-names> </name><name name-style="western"><surname>Dockery</surname><given-names>T</given-names> </name><name name-style="western"><surname>Manemeit</surname><given-names>C</given-names> </name></person-group><article-title>Usability enhancements to a prototype clinical decision support system for combat medics</article-title><source>Mil Med</source><year>2023</year><month>11</month><day>8</day><volume>188</volume><issue>Suppl 6</issue><fpage>614</fpage><lpage>620</lpage><pub-id pub-id-type="doi">10.1093/milmed/usad279</pub-id><pub-id pub-id-type="medline">37948290</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>Lutz</surname><given-names>J</given-names> </name><name name-style="western"><surname>Memmert</surname><given-names>D</given-names> </name><name name-style="western"><surname>Raabe</surname><given-names>D</given-names> </name><name name-style="western"><surname>Dornberger</surname><given-names>R</given-names> </name><name name-style="western"><surname>Donath</surname><given-names>L</given-names> </name></person-group><article-title>Wearables for integrative performance and tactic analyses: opportunities, challenges, and future directions</article-title><source>Int J Environ Res Public Health</source><year>2019</year><month>12</month><day>19</day><volume>17</volume><issue>1</issue><fpage>59</fpage><pub-id pub-id-type="doi">10.3390/ijerph17010059</pub-id><pub-id pub-id-type="medline">31861754</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>Alshamari</surname><given-names>MA</given-names> </name><name name-style="western"><surname>Althobaiti</surname><given-names>MM</given-names> </name></person-group><article-title>Usability evaluation of wearable smartwatches using customized heuristics and system usability scale score</article-title><source>Future Internet</source><year>2024</year><volume>16</volume><issue>6</issue><fpage>204</fpage><pub-id pub-id-type="doi">10.3390/fi16060204</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>Mejia</surname><given-names>C</given-names> </name><name name-style="western"><surname>Ciarlante</surname><given-names>K</given-names> </name><name name-style="western"><surname>Chheda</surname><given-names>K</given-names> </name></person-group><article-title>A wearable technology solution and research agenda for housekeeper safety and health</article-title><source>Int J Contemp Hosp Manag</source><year>2021</year><month>10</month><day>20</day><volume>33</volume><issue>10</issue><fpage>3223</fpage><lpage>3255</lpage><pub-id pub-id-type="doi">10.1108/IJCHM-01-2021-0102</pub-id></nlm-citation></ref><ref id="ref9"><label>9</label><nlm-citation citation-type="book"><source>Human Factors for Informatics Usability</source><year>1991</year><access-date>2026-02-04</access-date><publisher-name>Cambridge University Press</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://books.google.com.mt/books?id=KSHrPgLlMJIC&#x0026;printsec=copyright&#x0026;source=gbs_pub_info_r#v=onepage&#x0026;q&#x0026;f=false">https://books.google.com.mt/books?id=KSHrPgLlMJIC&#x0026;printsec=copyright&#x0026;source=gbs_pub_info_r#v=onepage&#x0026;q&#x0026;f=false</ext-link></comment></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>Little</surname><given-names>JR</given-names> </name><name name-style="western"><surname>Rivera-Nichols</surname><given-names>T</given-names> </name><name name-style="western"><surname>Pavliscsak</surname><given-names>HH</given-names> </name><etal/></person-group><article-title>Demonstrating tactical combat casualty care in simulated environments to enable passive, autonomous documentation: protocol for a prospective simulation-based study</article-title><source>JMIR Res Protoc</source><year>2025</year><month>03</month><day>17</day><volume>14</volume><fpage>e67673</fpage><pub-id pub-id-type="doi">10.2196/67673</pub-id><pub-id pub-id-type="medline">40096684</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>Schmidt</surname><given-names>PM</given-names> </name><name name-style="western"><surname>Ortman</surname><given-names>H</given-names> </name><name name-style="western"><surname>Gaudaen</surname><given-names>JC</given-names> </name><etal/></person-group><article-title>Developing a comparative effective methodology for technology usability during a simulated casualty event</article-title><source>Mil Med</source><year>2023</year><month>11</month><day>8</day><volume>188</volume><issue>Suppl 6</issue><fpage>642</fpage><lpage>650</lpage><pub-id pub-id-type="doi">10.1093/milmed/usad289</pub-id><pub-id pub-id-type="medline">37948220</pub-id></nlm-citation></ref><ref id="ref12"><label>12</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Brooke</surname><given-names>J</given-names> </name></person-group><article-title>SUS: a &#x201C;quick and dirty&#x201D; usability scale</article-title><source>Usability Evaluation in Industry</source><year>1996</year><publisher-name>CRC Press</publisher-name><fpage>189</fpage><lpage>194</lpage><pub-id pub-id-type="other">9781040070918</pub-id></nlm-citation></ref><ref id="ref13"><label>13</label><nlm-citation citation-type="report"><article-title>Tactical Combat Casualty Care (TCCC) Handbook: version 5 &#x2013; lessons and best practices</article-title><year>2017</year><access-date>2026-06-02</access-date><publisher-name>Committee on Tactical Combat Casualty Care (CoTCCC), U.S. Department of Defense (Joint Trauma System)</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://api.army.mil/e2/c/downloads/2023/01/19/31e03488/17-13-tactical-casualty-combat-care-handbook-v5-may-17-distro-a.pdfUse?">https://api.army.mil/e2/c/downloads/2023/01/19/31e03488/17-13-tactical-casualty-combat-care-handbook-v5-may-17-distro-a.pdfUse?</ext-link></comment></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>Saxon</surname><given-names>L</given-names> </name><name name-style="western"><surname>DiPaula</surname><given-names>B</given-names> </name><name name-style="western"><surname>Fox</surname><given-names>GR</given-names> </name><etal/></person-group><article-title>Continuous measurement of reconnaissance marines in training with custom smartphone app and watch: observational cohort study</article-title><source>JMIR mHealth uHealth</source><year>2020</year><month>06</month><day>15</day><volume>8</volume><issue>6</issue><fpage>e14116</fpage><pub-id pub-id-type="doi">10.2196/14116</pub-id><pub-id pub-id-type="medline">32348252</pub-id></nlm-citation></ref></ref-list></back></article>