<?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">v13i1e87589</article-id><article-id pub-id-type="doi">10.2196/87589</article-id><article-categories><subj-group subj-group-type="heading"><subject>Original Paper</subject></subj-group></article-categories><title-group><article-title>Multicenter Usability Evaluation and Co-Development of a Digital Decision-Support Tool for Labor Triage: Mixed Methods Study</article-title></title-group><contrib-group><contrib contrib-type="author"><name name-style="western"><surname>Tome</surname><given-names>Mariana</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Laurent</surname><given-names>Xavier</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Georgiev</surname><given-names>Kristiyan</given-names></name><degrees>BSc</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Tolladay</surname><given-names>John</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Collins</surname><given-names>Sarah</given-names></name><degrees>BSc (Hons)</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Hedgecott</surname><given-names>Deborah</given-names></name><degrees>BSc (Hons)</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Bozhilova</surname><given-names>Lyuba V</given-names></name><degrees>MMath, DPhil</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Hirst</surname><given-names>Jane E</given-names></name><degrees>MBChB PhD</degrees><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Impey</surname><given-names>Lawrence</given-names></name><degrees>MBBS, FRCOG, PhD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>Georgieva</surname><given-names>Antoniya</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib></contrib-group><aff id="aff1"><institution>Nuffield Department of Women's &#x0026; Reproductive Health, Oxford Labour Monitoring, University of Oxford</institution><addr-line>Nuffield Department of Women's &#x0026; Reproductive Health, University of Oxford</addr-line><addr-line>Oxford</addr-line><addr-line>England</addr-line><country>United Kingdom</country></aff><aff id="aff2"><institution>Artificial Intelligence (AI) Competency Centre, University of Oxford</institution><addr-line>Oxford</addr-line><addr-line>England</addr-line><country>United Kingdom</country></aff><aff id="aff3"><institution>The George Institute for Global Health, School of Public Health, Imperial College London</institution><addr-line>London</addr-line><addr-line>England</addr-line><country>United Kingdom</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>Morlotti</surname><given-names>Chiara</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Antoniya Georgieva, PhD, Nuffield Department of Women's &#x0026; Reproductive Health, Oxford Labour Monitoring, University of Oxford, Nuffield Department of Women's &#x0026; Reproductive Health, University of Oxford, Oxford, England, OX3 9DU, United Kingdom, 1 01865 221004; <email>antoniya.georgieva@wrh.ox.ac.uk</email></corresp></author-notes><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>23</day><month>7</month><year>2026</year></pub-date><volume>13</volume><elocation-id>e87589</elocation-id><history><date date-type="received"><day>12</day><month>11</month><year>2025</year></date><date date-type="rev-recd"><day>25</day><month>05</month><year>2026</year></date><date date-type="accepted"><day>23</day><month>06</month><year>2026</year></date></history><copyright-statement>&#x00A9; Mariana Tome, Xavier Laurent, Kristiyan Georgiev, John Tolladay, Sarah Collins, Deborah Hedgecott, Lyuba V Bozhilova, Jane E Hirst, Lawrence Impey, Antoniya Georgieva. Originally published in JMIR Human Factors (<ext-link ext-link-type="uri" xlink:href="https://humanfactors.jmir.org">https://humanfactors.jmir.org</ext-link>), 23.7.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/e87589"/><abstract><sec><title>Background</title><p>Digital decision-support tools for labor care remain limited, with few technologies successfully addressing the complex, time-sensitive decisions required during labor triage. Fit4Labour is a clinician-facing, data-driven research tool, currently under development, that combines computerized cardiotocography interpretation with maternal and fetal risk factors to generate individualized risk scores at labor onset. Its primary aim is to support clinicians in identifying fetuses who may require closer monitoring or expedited delivery, while simultaneously providing reassurance in low-risk cases. By promoting consistent communication and timely escalation of care, the Fit4Labour tool seeks to strengthen clinical decision-making. Understanding and addressing usability and implementation barriers will be critical to its adoption in clinical practice.</p></sec><sec><title>Objective</title><p>This study aims to evaluate whether a digitally co-developed labor decision-support tool (Fit4Labour) maintains usability and implementation readiness across NHS hospitals with differing clinical contexts.</p></sec><sec sec-type="methods"><title>Methods</title><p>We conducted a convergent parallel mixed methods study in 3 United Kingdom hospitals (December 2022 to May 2025). Phase 1 involved iterative co-development with midwives and doctors at Oxford University Hospitals NHS Foundation Trust; Phase 2 validated the locked version at Birmingham Women&#x2019;s and Children&#x2019;s NHS Foundation Trust and Buckinghamshire Healthcare NHS Trust. Participants completed scenario-based usability sessions evaluated with the System Usability Scale (SUS) and Single Ease Question (SEQ), and task completion time, followed by focus groups and interviews analyzed thematically.</p></sec><sec sec-type="results"><title>Results</title><p>Twenty-six health care professionals participated: 12 in co-development (7 midwives, 5 doctors) and 14 in validation (8 midwives, 6 doctors) phases. During co-development at Oxford, the tool met the &#x201C;excellent&#x201D; usability threshold (mean SUS 82.1, SD 12.3), indicating readiness for the validation phase. The locked version (v4.0) independently met the &#x201C;excellent&#x201D; threshold at both validation sites (combined mean SUS 85.8, SD 10.2; Birmingham 80.7, SD 10.8; Buckinghamshire 90.8, SD 7.2). Task completion times were comparable across validation sites (Birmingham 10.3, SD 1.6 min; Buckinghamshire 9.2, SD 1.9 min), while SEQ scores were consistently high across all scenarios (mean 6.1/7, SD 0.8). Thematic analysis identified 12 themes within 3 domains: clinical integration and workflow, technology adoption and implementation, and patient safety and decision-making. Participants described the Fit4Labour tool as a supportive tool, &#x201C;like a co-pilot,&#x201D; improving confidence in decisions with the potential to aid triage assessment. Perceived limitations included an incomplete risk factor profile and the need for minor technical adjustments or integration with existing hospital systems.</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>Through systematic co-development, the Fit4Labour tool met the established usability benchmark at 2 independent NHS hospitals with markedly different clinical contexts. Clinicians viewed the tool as a supportive aid providing a shared language for risk communication and enhanced decision-making while preserving clinical autonomy. Whether these usability findings translate to improved clinical outcomes in real-world practice requires prospective evaluation.</p></sec></abstract><kwd-group><kwd>cardiotocography</kwd><kwd>fetal monitoring</kwd><kwd>usability testing</kwd><kwd>clinical decision support systems</kwd><kwd>labor management</kwd><kwd>health care technology</kwd><kwd>co-development methodology</kwd><kwd>maternity care</kwd><kwd>digital health</kwd><kwd>labor triage</kwd><kwd>user-centered design</kwd><kwd>implementation</kwd><kwd>data-based tools in health care</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><sec id="s1-1"><title>Overview</title><p>Health care systems worldwide are undergoing rapid digital transformation, with clinical decision-support tools increasingly recognized as valuable tools for improving patient safety and care quality [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref5">5</xref>]. This transformation is particularly important in maternity care, where time-sensitive decisions during labor have profound consequences for both maternal and neonatal outcomes [<xref ref-type="bibr" rid="ref6">6</xref>-<xref ref-type="bibr" rid="ref8">8</xref>]. Yet, successful implementation depends not only on algorithmic accuracy, but also on user-centered design: tools must present information clearly, fit seamlessly into workflows, and support rather than disrupt decision-making [<xref ref-type="bibr" rid="ref9">9</xref>-<xref ref-type="bibr" rid="ref13">13</xref>].</p></sec><sec id="s1-2"><title>Implementation Challenge in Health Care Technology</title><p>Traditional development models in health care technologies often involve limited user engagement until late validation stages, resulting in tools that perform well in controlled settings (&#x201C;work as imagined&#x201D;) but fail in the reality of busy clinical environments (&#x201C;work as done&#x201D;) [<xref ref-type="bibr" rid="ref14">14</xref>-<xref ref-type="bibr" rid="ref16">16</xref>]. Insufficient investment of time and resources in co-design and usability testing remains a major barrier to adoption. Systematic reviews consistently demonstrate that poor usability is linked to low uptake, which in turn can pose patient safety risks [<xref ref-type="bibr" rid="ref17">17</xref>-<xref ref-type="bibr" rid="ref19">19</xref>].</p><p>Maternity care poses additional unique challenges as clinicians often manage multiple patients simultaneously with diverse risk profiles, while maintaining high safety standards [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>]. Front-line clinical staff (eg, midwives and junior doctors) in the United Kingdom (UK) National Health System (NHS) are often key decision-makers in triage, and hold unique insights into workflow barriers; however, their perspectives are frequently underrepresented during the design of new technologies [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref23">23</xref>].</p></sec><sec id="s1-3"><title>Challenges in Labor Care</title><p>Fetal monitoring can be performed using intermittent auscultation or cardiotocography. Cardiotocography, a graphical record of fetal heart rate and uterine contractions over time, remains the standard tool for monitoring during labor [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]. However, cardiotocography interpretation demands specialist expertise, and yet, the same trace can be classified differently, which may lead to suboptimal decisions [<xref ref-type="bibr" rid="ref25">25</xref>-<xref ref-type="bibr" rid="ref27">27</xref>].</p><p>Labor triage involves the rapid assessment of maternal and fetal well-being at the onset of labor to determine appropriate monitoring, the appropriate place for birth, and whether urgent intervention (such as expedited delivery) may be required [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref28">28</xref>]. These early decisions shape the entire labor care pathway. Published investigations repeatedly identified that failures during intrapartum monitoring are associated with delays in both decision-making and escalation of care [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref30">30</xref>]. At the same time, modern maternity care increasingly emphasizes shared decision-making, requiring clinicians to communicate individualized risk information effectively to support women&#x2019;s autonomy [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref31">31</xref>].</p></sec><sec id="s1-4"><title>The Fit4Labour Tool Innovation</title><p>The Fit4Labour tool (University of Oxford) was designed as a clinician-facing digital system to address these challenges by combining maternal and fetal risk factors (eg, maternal age, diabetes, and meconium-stained liquor) with computerized cardiotocography analysis to generate individualized risk scores indicating the likelihood of fetal compromise during labor (<xref ref-type="fig" rid="figure1">Figure 1</xref>). Unlike earlier computerized cardiotocography systems that rely mainly on human pattern recognition, the Fit4Labour tool applies a prognostic modeling approach that integrates multiple clinical risk factors with cardiotocography data to produce standardized, evidence-based predictions of adverse outcomes at delivery [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref33">33</xref>]. Developed by the Oxford Labor Monitoring Group through multidisciplinary, user-centered co-design involving clinicians, engineers, and patient representatives, the tool draws on a dataset of over 147,000 cardiotocographs linked to birth outcomes and prioritizes intuitive use and clear risk communication to support clinicians&#x2019; intrapartum decision-making [<xref ref-type="bibr" rid="ref34">34</xref>].</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>The Fit4Labour tool clinical workflow pathway from initial risk assessment to generation of the risk report. The diagram illustrates how the tool integrates into existing maternity workflows, combining maternal and fetal risk factors with computerized analysis of the cardiotocography trace to support triage, escalation, and communication of risk. CTG: cardiotocography.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v13i1e87589_fig01.png"/></fig><p>This multicenter convergent parallel mixed methods study aimed to evaluate whether the Fit4Labour tool, developed through intensive co-development at a single NHS hospital, maintained usability and implementation readiness across 2 NHS hospitals with differing clinical contexts.</p></sec></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>Study Design and Conceptual Framework</title><p>We conducted a multicenter convergent parallel mixed methods study over a two-and-a-half-year period (December 2022-May 2025) to assess the usability and implementation readiness of the Fit4Labour decision-support tool. Quantitative usability metrics were combined with qualitative user experience data, analyzed in parallel and then systematically integrated. This approach allowed us to explore both the measurable performance and clinicians&#x2019; lived experience, providing a comprehensive understanding of usability and potential implementation barriers.</p><p>The study was guided by human factors engineering principles and we used 3 theoretical approaches (<xref ref-type="fig" rid="figure2">Figure 2</xref>). First, user-centered design entails involving midwives and doctors throughout development [<xref ref-type="bibr" rid="ref9">9</xref>]. We designed the tool based on user feedback, with the aim of aligning its features to clinicians&#x2019; cognitive workflows and practical needs. Second, Distributed Cognition recognized that clinical decision-making is shared across people, tools such as checklists or cardiotocography traces, rather than occurring solely in individual minds [<xref ref-type="bibr" rid="ref35">35</xref>]. The Fit4Labour tool was designed to provide both midwives and doctors with the same risk information, creating a shared risk score that supports team coordination and collective decision-making. Third, Sociotechnical Systems emphasized that technology operates within complex systems of people, processes, and environments [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref36">36</xref>]. This framework guided our assessment of whether participating hospitals had the necessary infrastructure, culture, and organizational support to implement the Fit4Labour tool effectively.</p><p>The study was conducted in 2 phases. Phase 1 was an iterative co-development process at Oxford University Hospitals NHS Foundation Trust (OUH) (referred to as Oxford throughout the paper), where the tool was refined through multiple cycles of usability testing and direct user feedback. Phase 2 involved multisite validation at Birmingham Women&#x2019;s and Children&#x2019;s NHS Foundation Trust (referred to as Birmingham throughout the paper) and Buckinghamshire Healthcare NHS Trust (referred to as Buckinghamshire), where the locked prototype version of the tool was evaluated to assess its usability and transferability across different organizational contexts.</p><fig position="float" id="figure2"><label>Figure 2.</label><caption><p>Conceptual framework and study design showing the Fit4Labour tool version iterations. SEIPS: Systems Engineering Initiative for Patient Safety. SEQ: Single Ease Question; SUS: System Usability Scale.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v13i1e87589_fig02.png"/></fig></sec><sec id="s2-2"><title>Study Sites</title><p>Hospitals were intentionally selected to capture diverse maternity services and populations within the UK National Health Service. OUH (Oxford) is a large university teaching hospital with a well-established research infrastructure and strong links to the University of Oxford, serving both urban and rural populations. BWC (Birmingham) is a specialist teaching hospital providing high-volume maternity services to an ethnically diverse population, while BHT (Buckinghamshire) is a medium-sized district general hospital broadly representative of typical NHS maternity care, reflecting the realities of routine clinical practice. Together, these sites enabled evaluation across varied demographics, clinical practices, and infrastructure levels, thereby enhancing the generalizability within the NHS hospitals and ethnically diverse populations.</p></sec><sec id="s2-3"><title>The Fit4Labour Tool</title><p>The clinician-facing Fit4Labour tool is a web-based application that runs on tablet devices or computers and can communicate with electronic maternity record systems. It integrates maternal and fetal risk factors with computerized cardiotocography analysis to produce color-coded risk categories (green=low, amber=moderate, red=high) accompanied by a numerical score indicating the risk of severe fetal compromise. Severe compromise is defined as a composite of intrapartum stillbirth, neonatal death (&#x003C;28 days), neonatal encephalopathy (including hypoxic-ischemic encephalopathy), or neonatal seizures.</p><p>The tool displayed time-related changes in risk that updated in real time as the cardiotocography recording progressed, alongside detailed computerized analyses of individual cardiotocography parameters including baseline heart rate variability, accelerations, and decelerations. Reports were generated at 20- and 60-minute intervals and included integrated note-taking and record-storage features to support clinical documentation, handover continuity, and audit processes.</p></sec><sec id="s2-4"><title>Study Objectives</title><p>The primary objective was to evaluate usability and acceptability of the Fit4Labour tool across 3 NHS sites using quantitative metrics (System Usability Scale, Single Ease Question, task completion times) and qualitative assessment of clinician perceptions. Secondary objectives were to explore organizational factors influencing transferability, examine how midwives and doctors perceived and interacted with the tool, assess its perceived potential to enhance patient care, and identify organizational and technical barriers that may impact adoption.</p></sec><sec id="s2-5"><title>Participants and Recruitment</title><p>Participants comprised qualified midwives and doctors currently working in the selected maternity services, with direct patient care responsibilities in labor triage or delivery settings, and the need for and experience in cardiotocography interpretation as part of their clinical role. Department managers distributed information sheets to recruit participants. Three factors determined sample size: Nielsen&#x2019;s guidance for interface evaluation (5&#x2010;8 participants per group typically uncover 80%&#x2010;85% of usability issues in interface evaluation studies, a pattern following the diminishing returns where each additional participant identifies fewer new problems), thematic saturation requirements for qualitative analysis, and practical constraints of multisite recruitment [<xref ref-type="bibr" rid="ref37">37</xref>]. Using a relatively small number of samples, our convergent mixed methods design prioritized depth of insight over statistical power, consistent with exploratory implementation research [<xref ref-type="bibr" rid="ref38">38</xref>,<xref ref-type="bibr" rid="ref39">39</xref>]. All participants received a small honorarium (Amazon voucher) for their time.</p></sec><sec id="s2-6"><title>Procedures</title><p>Between December 2022 and January 2024, the co-development phase took place in Oxford with participants testing successive prototypes in structured usability sessions. Feedback was sought on the user interface, layout, workflow, data entry, and risk visualization. Development followed a user-centered, multidisciplinary approach with iterative refinement over 4 versions at Oxford. Each version incorporated feedback from midwives and doctors, addressing user interface design, navigation, and risk visualization. Detailed version histories are provided in Table S3 in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>. All design modifications were systematically logged, including user feedback prompting the change, implementation details, and impact assessment on overall functionality. Once usability goals, defined by high ease-of-use ratings, absence of major usability issues, and thematic saturation in qualitative feedback were achieved, the version was locked for validation testing. The locked version represented a stable version with no further interface or algorithmic modifications permitted during the validation phase. From November 2024 to May 2025, the locked version underwent prospective validation at Birmingham and Buckinghamshire. Participants followed the same protocol used at Oxford.</p></sec><sec id="s2-7"><title>Usability Testing Sessions</title><p>Sessions lasted between 60 and 120 minutes and were co-facilitated by a clinical researcher (MT) and an experimental psychologist (XL) with extensive experience in usability testing. All sessions were conducted in dedicated rooms to minimize interruptions and ensure a consistent testing environment.</p><p>Testing was done in 2 separate stages (Figure S1 in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). In the task-based evaluation, participants first viewed a standardized 5-minute introduction video explaining the tool&#x2019;s purpose. The video did not include instructions on how to use the tool, as we sought to evaluate the user&#x2019;s intuitive navigation (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> video). The users were then given the tool and were asked to enter data for 4 progressive clinical scenarios, simulating common clinic triage tasks. This included baseline clinical risk factor entry, report generation, note-taking, risk factor updates, and advanced report features (Table S1 in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). Each scenario lasted up to 5 minutes, with facilitators observing silently and recording task completion times, errors, and usability barriers. If a task could not be completed within the allocated time, participants were instructed to move on to the next task.</p><p>After completing each scenario, participants were asked to rate the task&#x2019;s difficulty using the Single Ease Question (SEQ), a 7-point Likert scale (1=very difficult, 7=very easy). At the end of all tasks, they subsequently completed the System Usability Scale (SUS), a 10-item questionnaire generating an overall usability score from 0 to 100 (Figure S2 and S3 in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>).</p><p>The second stage was the qualitative exploration, which involved profession-specific focus groups or, where necessary, individual interviews. Discussions followed a structured topic guide exploring ease of use, clinical relevance, workflow integration, training needs, communication implications, and impact on clinical autonomy. All sessions were audio-recorded and transcribed verbatim.</p></sec><sec id="s2-8"><title>Outcomes</title><p>Quantitative outcomes included SUS scores: values below 68 indicating below-average usability, between 68 and 80 indicating good usability, and above 80 indicating excellent usability [<xref ref-type="bibr" rid="ref40">40</xref>,<xref ref-type="bibr" rid="ref41">41</xref>]. SEQ ratings were used to assess ease of use following each clinical scenario. Lastly, task performance parameters were evaluated through completion times, error rates, and variability across participants. Qualitative outcomes captured themes relating to clinical integration, technology adoption, patient safety, and decision-making, drawing on data from focus groups and interviews.</p></sec><sec id="s2-9"><title>Analysis</title><sec id="s2-9-1"><title>Quantitative Analysis</title><p>Descriptive statistics were reported as mean (SD) or median (IQR) according to the data distribution that was assessed by the Shapiro-Wilk test. No inferential statistical testing was performed. This was a deliberate choice as the primary aim of this study was to establish readiness and understand patterns of usability performance within each phase, rather than test population-level hypotheses. Moreover, phase 1 and phase involved different participants, tool versions, and clinical sites, precluding between-phase comparison being attributed to a single factor. The sample size was deemed sufficient for thematic saturation in the qualitative data. Data analysis and graphical representation were performed using the R software (version 4.5.3; R Core Team).</p></sec><sec id="s2-9-2"><title>Qualitative Analysis</title><p>Transcripts were analyzed inductively using Braun and Clarke&#x2019;s 6-phase framework [<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref43">43</xref>]. Three researchers (MT, XL, and DH) independently coded the transcripts, with consensus meetings to refine the coding framework and resolve any discrepancies. Themes were iteratively developed and mapped to usability and implementation domains. Saturation was defined as the absence of new themes across 2 consecutive coding rounds. NVivo software (Lumivero) was used for coding and data management.</p></sec><sec id="s2-9-3"><title>Mixed Methods Integration</title><p>Quantitative and qualitative findings were integrated using a convergent parallel design [<xref ref-type="bibr" rid="ref38">38</xref>]. Independent analyses were brought together in joint displays, with patterns categorized as convergence (alignment of findings), complementarity (mutual enrichment), or dissonance (contradictory insights). This approach enables a richer understanding of usability and implementation than either method alone.</p></sec></sec><sec id="s2-10"><title>Ethical Considerations</title><p>This usability study was conducted independently of, but in parallel with, the Fit4Labour technology evaluation and proof-of-concept study (ethics reference: 22/SC/0097). As this study involved health care professionals evaluating a prototype tool in a simulated setting, and did not involve patients, patient data, or clinical decision-making, formal research ethics committee review was determined not to be required. This was confirmed and agreed with the principal investigator at each of the 3 participating sites prior to recruitment.The study was registered with, and formally endorsed by, the research governance team at each of the three participating sites prior to recruitment, and this determination was further confirmed and agreed with the principal investigator at each site. All participants provided informed consent, recorded at the start of each audio-recorded session, after receiving detailed information regarding the study objectives and procedures, including their right to withdraw at any time without giving a reason. No identifiable patient data were collected or used in this study, and audio recordings and transcripts were stored securely with access restricted to the research team. Participants received a small honorarium (an Amazon voucher) in recognition of their time. Funding for the usability testing was provided by a National Institute for Health and Care Research (NIHR) Invention for Innovation (i4i) Product Development Award (NIHR202117); the funder had no role in study design, data collection, analysis, or interpretation.</p></sec></sec><sec id="s3" sec-type="results"><title>Results</title><sec id="s3-1"><title>Participant Characteristics</title><p>Twenty-six health care professionals were recruited across 3 NHS sites: 15 midwives (58%) and 11 doctors (42%). Twelve participants (7 midwives and 5 doctors) contributed to Phase 1 co-development at Oxford, and 14 participants (8 midwives and 6 doctors) to Phase 2 validation at Birmingham and Buckinghamshire. Most participants (22/26, 85%) were women. Participants represented a wide range of seniority, from junior staff to consultant midwives and obstetricians, broadly reflecting the professional mix of UK maternity care (Table S2 in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). Although 25 participants completed the scenario-based usability testing, 26 took part in the interviews.</p></sec><sec id="s3-2"><title>The Fit4Labour Tool Developments</title><p>The co-development phase at Oxford involved 3 iterative sessions, with each systematically incorporating users&#x2019; feedback and testing progressively refined versions of the Fit4Labour tool (<xref ref-type="fig" rid="figure2">Figure 2</xref>). The first session with midwives (n=4) evaluated version 1.0, followed by a second midwives&#x2019; session (n=3) a few months later testing version 2.0, and finally, version 3.0 was tested by doctors (n=5). This led to the final locked version 4.0, which was then tested in the 2 validation sites (Birmingham and Buckinghamshire). Detailed systematic documentation of design modifications is provided in Table S3 in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> and examples of user interface improvements in Figure S5 in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>.</p></sec><sec id="s3-3"><title>Quantitative Findings</title><sec id="s3-3-1"><title>System Usability Scale (SUS)</title><p>During the co-development at Oxford, the initial version (1.0) had a mean SUS of 77.5 (SD 15.1; rated as &#x201C;good&#x201D;), and by version 3.0 this had reached 83.5 (SD 9.1; rated as &#x201C;excellent&#x201D;). The co-development phase using the locked version (v4.0) had an overall mean SUS of 82.1 (SD 12.3) (<xref ref-type="table" rid="table1">Table 1</xref>, <xref ref-type="fig" rid="figure3">Figure 3</xref>), which indicated that the threshold for the locked version had been met (SUS&#x003E;80).</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>System Usability Scale scores by study phase and site. Learnability scores derived from System Usability Scale items 4 and 10.</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Phase, site, and professional group</td><td align="left" valign="bottom">Participants, n</td><td align="left" valign="bottom">Version tested</td><td align="left" valign="bottom">SUS<sup><xref ref-type="table-fn" rid="table1fn1">b</xref></sup> score, mean (SD)</td><td align="left" valign="bottom">Range</td><td align="left" valign="bottom">Learnability, mean (SD)</td><td align="left" valign="bottom">Ratings<sup><xref ref-type="table-fn" rid="table1fn2">c</xref></sup></td></tr></thead><tbody><tr><td align="left" valign="top" colspan="7">Co-development</td></tr><tr><td align="left" valign="top" colspan="7"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Oxford</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>1st Midwives session</td><td align="left" valign="top">4</td><td align="left" valign="top">v1.0</td><td align="left" valign="top">77.5 (15.1)</td><td align="left" valign="top">62.5&#x2010;95</td><td align="left" valign="top">81.2 (16.1)</td><td align="left" valign="top">Good</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>2nd Midwives session</td><td align="left" valign="top">3</td><td align="left" valign="top">v2.0</td><td align="left" valign="top">85.8 (13.7)</td><td align="left" valign="top">70&#x2010;95</td><td align="left" valign="top">79.2 (19.1)</td><td align="left" valign="top">Excellent</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>Doctors</td><td align="left" valign="top">5</td><td align="left" valign="top">v3.0</td><td align="left" valign="top">83.5 (9.1)</td><td align="left" valign="top">72.5&#x2010;97.5</td><td align="left" valign="top">87.5 (12.5)</td><td align="left" valign="top">Excellent</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>Co-development total</td><td align="left" valign="top">12</td><td align="left" valign="top">v1.0&#x2010;3.0</td><td align="left" valign="top">82.1 (12.3)</td><td align="left" valign="top">62.5&#x2010;97.5</td><td align="left" valign="top">83.3 (14.4)</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top" colspan="7">Validation</td></tr><tr><td align="left" valign="top" colspan="7"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Birmingham</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>Midwives</td><td align="left" valign="top">4</td><td align="left" valign="top" rowspan="3">v4.0</td><td align="left" valign="top">76.3 (11.4)</td><td align="left" valign="top">65&#x2010;90</td><td align="left" valign="top">62.5 (22.8)</td><td align="left" valign="top">Good</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>Doctors</td><td align="left" valign="top">3</td><td align="left" valign="top">86.7 (6.6)</td><td align="left" valign="top">77.5&#x2010;92.5</td><td align="left" valign="top">75 (33.1)</td><td align="left" valign="top">Excellent</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>Site Subtotal</td><td align="left" valign="top"><bold>7</bold></td><td align="left" valign="top">80.7 (10.8)</td><td align="left" valign="top">65&#x2010;92.5</td><td align="left" valign="top">67.9 (25.9)</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top" colspan="7"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Buckinghamshire</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>Midwives</td><td align="left" valign="top">3</td><td align="left" valign="top" rowspan="3">v4.0</td><td align="left" valign="top">94.2 (5.1)</td><td align="left" valign="top">87.5&#x2010;100</td><td align="left" valign="top">95.8 (7.2)</td><td align="left" valign="top">Excellent</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>Doctors</td><td align="left" valign="top">3</td><td align="left" valign="top">87.5 (8.2)</td><td align="left" valign="top">77.5&#x2010;97.5</td><td align="left" valign="top">95.8 (7.2)</td><td align="left" valign="top">Excellent</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>Site subtotal</td><td align="left" valign="top">6</td><td align="left" valign="top">90.8 (7.2)</td><td align="left" valign="top">77.5&#x2010;100</td><td align="left" valign="top">95.8 (6.5)</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">Validation total</td><td align="left" valign="top">13</td><td align="left" valign="top">v4.0</td><td align="left" valign="top">85.8 (10.2)</td><td align="left" valign="top">65&#x2010;100</td><td align="left" valign="top">80.8 (23.7)</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">Overall study (all participants<sup><xref ref-type="table-fn" rid="table1fn3">d</xref></sup>)</td><td align="left" valign="top">25</td><td align="left" valign="top">v1.0&#x2010;4.0</td><td align="left" valign="top">83.8 (11.3)</td><td align="left" valign="top">62.5&#x2010;100</td><td align="left" valign="top">82 (19.5)</td><td align="left" valign="top">Excellent</td></tr></tbody></table><table-wrap-foot><fn id="table1fn1"><p><sup>b</sup>SUS: System Usability Scale.</p></fn><fn id="table1fn2"><p><sup>c</sup>Interpretation thresholds: &#x003C;68=below average, 68&#x2013;80=good, &#x003E;80=excellent.</p></fn><fn id="table1fn3"><p><sup>d</sup>One Birmingham midwife observed scenarios only and participated solely in focus groups, resulting in n=26 total participants but n=25 for SUS assessments.</p></fn></table-wrap-foot></table-wrap><fig position="float" id="figure3"><label>Figure 3.</label><caption><p>SUS scores by study phase and site. During co-development, scores reflect iterative refinement across successive versions. During validation, the locked version (v4.0) independently met the &#x201C;excellent&#x201D; threshold at both sites. SUS: System Usability Scale.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v13i1e87589_fig03.png"/></fig><p>The final locked version 4.0 independently met the &#x201C;excellent&#x201D; usability threshold during validation testing at 2 distinct sites, with a combined mean SUS score of 85.8 (SD 10.2), but with some intersite variability (Birmingham 80.7, SD 10.8 vs Buckinghamshire 90.8, SD 7.2). The SD of 10.2 within this phase reflects a relatively narrow spread of individual scores, suggesting a more predictable and uniform user experience across participants and sites.</p><p>Learnability scores (SUS items 4 and 10) showed an overall mean of 82 (SD 19.5). Co-development mean scores were 83.3 (SD 14.4) (Oxford) and validation mean scores were 80.8 (SD 23.7). Buckinghamshire showed a mean of 95.8 (SD 6.5), while Birmingham showed greater variability at a mean of 67.9 (SD 25.9). Professional group differences were modest (doctors: mean 87.5, SD 12.5; midwives: mean 80.4, SD 15.9 at Oxford; <xref ref-type="table" rid="table1">Table 1</xref>).</p></sec><sec id="s3-3-2"><title>Single Ease Question (SEQ)</title><p>Task difficulty ratings demonstrated that participants perceived most scenarios as being &#x201C;very easy&#x201D; across all versions (mean SEQ 5.8&#x2010;6.3 for Scenarios 1&#x2010;3) (<xref ref-type="table" rid="table2">Table 2</xref>, <xref ref-type="fig" rid="figure4">Figure 4</xref>). Scenario 4, covering advanced functions, showed more variable ratings during co-development (v1.0 mean SEQ 5, SD 1.4; v2.0 mean SEQ 4.7, SD 1.2; and v3.0 mean SEQ 5.6, SD 0.7). In the validation phase, the locked version received SEQ ratings of mean 5.9 (SD 0.9) (Birmingham) and mean 6.3 (SD 0.8) (Buckinghamshire) for Scenario 4, indicating that advanced functions were perceived as easy to use. Overall, both validation sites demonstrated comparable ratings across all scenarios (Birmingham SEQ 6.2 vs Buckinghamshire SEQ 6.3), suggesting that version 4.0 had consistent perceived ease of use across scenarios.</p><table-wrap id="t2" position="float"><label>Table 2.</label><caption><p>Single ease question scores by study phase and scenario. Single Easy Question Scale: 1=Very Difficult, 7=Very Easy.</p></caption><table id="table2" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom" rowspan="2">Phase, site, and group</td><td align="left" valign="bottom" rowspan="2">Participants, n</td><td align="left" valign="bottom" rowspan="2">Fit4Labour version tested</td><td align="left" valign="bottom" colspan="5">Mean SEQ<sup><xref ref-type="table-fn" rid="table2fn1">a</xref></sup> (SD)</td></tr><tr><td align="left" valign="bottom">Scenario 1</td><td align="left" valign="bottom">Scenario 2</td><td align="left" valign="bottom">Scenario 3</td><td align="left" valign="bottom">Scenario 4</td><td align="left" valign="bottom">Total</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="8">Co-development</td></tr><tr><td align="left" valign="top" colspan="8"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Oxford</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>1st Midwives</td><td align="left" valign="top">4</td><td align="left" valign="top">v1.0</td><td align="left" valign="top">6 (0.8)</td><td align="left" valign="top">6.5 (0.6)</td><td align="left" valign="top">6.3 (0.5)</td><td align="left" valign="top">5.0 (1.4)</td><td align="left" valign="top">5.9</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>2nd Midwives</td><td align="left" valign="top">3</td><td align="left" valign="top">v2.0</td><td align="left" valign="top">6 (0)</td><td align="left" valign="top">6.3 (0.6)</td><td align="left" valign="top">6 (1)</td><td align="left" valign="top">4.7 (1.2)</td><td align="left" valign="top">5.8</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>Doctors</td><td align="left" valign="top">5</td><td align="left" valign="top">v3.0</td><td align="left" valign="top">6.4 (0.5)</td><td align="left" valign="top">5.8 (0.8)</td><td align="left" valign="top">5.6 (0.9)</td><td align="left" valign="top">5.6 (0.7)</td><td align="left" valign="top">5.9</td></tr><tr><td align="left" valign="top" colspan="8">Validation</td></tr><tr><td align="left" valign="top" colspan="8"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Birmingham</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>Combined</td><td align="left" valign="top">7</td><td align="left" valign="top">v4.0</td><td align="left" valign="top">6.4 (0.7)</td><td align="left" valign="top">6.0 (0.9)</td><td align="left" valign="top">6.5 (0.5)</td><td align="left" valign="top">5.9 (0.9)</td><td align="left" valign="top">6.2</td></tr><tr><td align="left" valign="top" colspan="8"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Buckinghamshire</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>Combined</td><td align="left" valign="top">6</td><td align="left" valign="top">v4.0</td><td align="left" valign="top">6.5 (0.5)</td><td align="left" valign="top">6.2 (0.8)</td><td align="left" valign="top">6.3 (0.8)</td><td align="left" valign="top">6.3 (0.8)</td><td align="left" valign="top">6.3</td></tr><tr><td align="left" valign="top">Overall<sup><xref ref-type="table-fn" rid="table2fn2">b</xref></sup></td><td align="left" valign="top">25</td><td align="left" valign="top">v4.0</td><td align="left" valign="top">6.3 (0.6)</td><td align="left" valign="top">6.1 (0.8)</td><td align="left" valign="top">6.1 (0.7)</td><td align="left" valign="top">5.7 (1)</td><td align="left" valign="top">6.1</td></tr></tbody></table><table-wrap-foot><fn id="table2fn1"><p><sup>a</sup>SEQ: Single Ease Question.</p></fn><fn id="table2fn2"><p><sup>b</sup>One Birmingham midwife observed scenarios only and participated solely in focus groups, resulting in n=26 total participants but n=25 for SEQ assessments.</p></fn></table-wrap-foot></table-wrap><fig position="float" id="figure4"><label>Figure 4.</label><caption><p>Heat map single ease question scores by study phase and scenario. Color-coded visualization of ease-of-use ratings (1=very difficult; 7=very easy) across scenarios<italic>.</italic> SEQ: Single Ease Question.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v13i1e87589_fig04.png"/></fig></sec><sec id="s3-3-3"><title>Task Efficiency and Errors</title><p>Cumulative task completion times in the co-development phase in Oxford ranged from 7 to 18 minutes, with a mean of 11.8 (SD 2.5) reflecting expected variation during refinements across successive prototype versions and iterative designs (Table S4 in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>).</p><p>During the validation phase, the locked version 4.0 was completed in a mean of 9.8 (SD 1.8) minutes overall (<xref ref-type="fig" rid="figure5">Figure 5</xref>). Despite testing in different clinical environments and with different digital infrastructure, both validation sites had comparable completion times (Birmingham 10.3, SD 1.6 min and Buckinghamshire 9.2, SD 1.9 min), suggesting consistent and transferable usability of the locked version across sites.</p><fig position="float" id="figure5"><label>Figure 5.</label><caption><p>Task completion times (minutes) for all 4 simulated clinical scenarios completed sequentially during usability testing across study phases and sites. Each bar represents the total time taken to complete the entire set of 4 scenarios, not the time required to use the Fit4Labour tool in real clinical practice for 1 patient.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v13i1e87589_fig05.png"/></fig></sec><sec id="s3-3-4"><title>Professional Group Comparisons</title><p>Usability was comparable between midwives and doctors. Doctors reported slightly higher SUS scores (mean 87.1, SD 8.2 vs mean 83, SD 13.8) and faster completion times (9.3 versus 10.1 min), but differences were modest. Midwives had higher variability in both. SEQ ratings were also very similar, indicating intuitive usability across professional groups.</p></sec></sec><sec id="s3-4"><title>Qualitative Findings</title><p>Thematic analysis identified 12 themes grouped within 3 domains: clinical integration and workflow, technology adoption and implementation, and patient safety and decision-making (<xref ref-type="table" rid="table3">Table 3</xref>). All thematic summaries and supporting quotes are presented in the Supplementary Analysis 1&#x2010;3 and Figure S4 in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>.</p><table-wrap id="t3" position="float"><label>Table 3.</label><caption><p>Thematic framework showing the 3 domains and 12 themes identified through qualitative analysis across study sites. Summary of the 12 themes organized under 3 domains: clinical integration and workflow, technology adoption and implementation, and patient safety and decision-making.</p></caption><table id="table3" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Domain and theme number</td><td align="left" valign="bottom">Theme name</td><td align="left" valign="bottom">Description</td></tr></thead><tbody><tr><td align="left" valign="top">Clinical integration and workflow</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</td><td align="left" valign="top">Risk factors and clinical comprehensiveness</td><td align="left" valign="top">Need for more risk factor options (eg, IUGR<sup><xref ref-type="table-fn" rid="table3fn1">a</xref></sup>, reduced fetal movements) and complex combinations to improve accuracy and avoid underestimating risk.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>2</td><td align="left" valign="top">Timeline and workflow integration</td><td align="left" valign="top">Report timing options (20 versus 60 min) and workflow challenges including room availability, resources, and staffing constraints.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>3</td><td align="left" valign="top">Screening and triage effectiveness</td><td align="left" valign="top">Value in objective screening and triage with color-coded risk stratification (green, red, amber) for prioritizing care.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>4</td><td align="left" valign="top">Escalation support for midwives</td><td align="left" valign="top">Enhanced midwife-doctor communication, confidence building for junior staff, and structured escalation protocols.</td></tr><tr><td align="left" valign="top">Technology adoption and implementation</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>5</td><td align="left" valign="top">Training and digital confidence</td><td align="left" valign="top">Digital skills vary; success linked to training champions, mandatory sessions, and understanding tool rationale.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>6</td><td align="left" valign="top">Ease of use</td><td align="left" valign="top">Intuitive design, straightforward interface, easy demographic input, and successful co-development outcomes.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>7</td><td align="left" valign="top">Technology infrastructure barriers</td><td align="left" valign="top">Internet connectivity, Wi-Fi issues, device charging, CTG<sup><xref ref-type="table-fn" rid="table3fn2">b</xref></sup> compatibility, and hardware availability.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>8</td><td align="left" valign="top">Digital overload and change management</td><td align="left" valign="top">Too many tools and software can overwhelm; resistance to change needs addressing through buy-in engagement strategies.</td></tr><tr><td align="left" valign="top">Patient safety and decision-making</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</td><td align="left" valign="top">Decision-making safety net</td><td align="left" valign="top">&#x201C;Co-pilot&#x201D; for clinical support, especially valuable in gray areas of CTG interpretation and safety net for junior staff.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>10</td><td align="left" valign="top">Risk communication and intervention requests</td><td align="left" valign="top">Support for informed patient counseling with individualized risk information and transparent communication strategies.<break/>Concerns about sharing risk information could increase patient requests for interventions.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>11</td><td align="left" valign="top">Clinical autonomy and professional responsibility</td><td align="left" valign="top">Tool should support and not replace clinical judgment; concerns around medico-legal risk and deskilling.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>12</td><td align="left" valign="top">System-wide implementation and organizational adoption</td><td align="left" valign="top">Requires strong implementation planning, organizational readiness, and consistent departmental adoption and unified protocols.</td></tr></tbody></table><table-wrap-foot><fn id="table3fn1"><p><sup>a</sup>IUGR: intrauterine growth restriction.</p></fn><fn id="table3fn2"><p><sup>b</sup>CTG: cardiotocography.</p></fn></table-wrap-foot></table-wrap><sec id="s3-4-1"><title>Clinical Integration and Workflow Domain</title><p>Across all sites, participants described the Fit4Labour tool as a valuable screening and triage aid, with color-coded risk stratification enabling rapid and intuitive prioritization. One Oxford doctor explained that the colors &#x201C;acts as a powerful shortcut&#x2026; one of the fastest and easiest ways to express risk.&#x201D;</p><p>The tool was also seen as an effective escalation support mechanism, particularly for junior midwives who valued having objective evidence when calling senior staff: &#x201C;You feel more confident having documentation that says you need to seek urgent medical advice&#x201D; (Midwife, Oxford). Similarly, a Buckinghamshire midwife highlighted that the outputs facilitated communication by noting that <italic>&#x201C;</italic>the Fit4Labour tool is one language&#x2026;It helps put into words when you are not happy with a trace.&#x201D;</p><p>However, limitations were also noted, including an incomplete risk factor profile, such as the absence of reduced fetal movements, small-for-gestational-age, previous stillbirth, and antepartum hemorrhage. Clinicians felt that these omissions could undermine accuracy and provide false reassurance, with one Oxford doctor commenting that &#x201C;missing risk factors gives an impression of being very accurate and specific but may not be if you don&#x2019;t input certain combinations.&#x201D; Views on workflow integration varied, with some suggesting that 60-minute reports were impractical in fast-turnaround triage but potentially feasible in induction bays or antenatal wards.</p></sec><sec id="s3-4-2"><title>Technology Adoption and Implementation Domain</title><p>Ease of use was widely recognized by all participants and was commonly described as being &#x201C;very intuitive and straightforward.&#x201D; A midwife at Oxford noted its accessibility even when fatigued, explaining that &#x201C;it works for tired brains.&#x201D; Some participants with visual impairments or neurodivergent profiles, including those who were color-blind or dyslexic, commented positively on accessibility, with one noting, &#x201C;I can read it really clearly, I&#x2019;m dyslexic.&#x201D;</p><p>Nonetheless, a common theme was that structured training was essential given variation in digital literacy. A Birmingham doctor observed that &#x201C;people that struggle with technology will still struggle because their confidence with IT is low <italic>&#x2026;</italic> it&#x2019;s not that this is difficult to use.&#x201D; Suggested strategies included champion-led training and mandatory education programs. &#x201C;People are always anxious with new technology, it needs mandatory training to use it properly, more reassurance to not miss things before using it&#x201D; (Oxford Midwife).</p><p>Perceived implementation challenges extended to both infrastructure and organizational culture. Participants raised concerns about digital overload and imposed software changes in the NHS together with the need for senior buy-in, with one participant in Birmingham noting that &#x201C;nobody likes change&#x2026; you&#x2019;ll need a lot of buy-in from senior people... it&#x2019;ll snowball, just like iPhones when they came in..&#x201D; Another common topic was infrastructure constraints, such as poor Wi-Fi, delays in IT support, missing chargers, and limited hardware, which was cited in Birmingham (&#x201C;Wi-Fi doesn&#x2019;t work, and you can&#x2019;t see the CTGs<italic>&#x201D;</italic>). In contrast, Buckinghamshire participants reported implementation would likely be easier as the hospital was already paperless.</p></sec><sec id="s3-4-3"><title>Patient Safety and Decision-Making Domain</title><p>A prominent theme was the &#x201C;co-pilot in a plane&#x201D; analogy, first raised at Oxford, framing the tool as a supportive safety net rather than a replacement for clinical judgment, with a Birmingham doctor emphasizing that <italic>&#x201C;</italic>the physician still has the ultimate decision-making.&#x201D; The Fit4Labour tool was seen as particularly reassuring for junior staff and when presented with complex or ambiguous cases.</p><p>Participants valued the Fit4Labour tool to facilitate risk communication with patients, providing a &#x201C;common language&#x201D; for explaining probabilities and counseling women requesting care outside guidelines: &#x201C;We are not informing patients of their real risks because we don&#x2019;t know, but this is what Fit4Labour can bring&#x201D; (Doctor, Oxford). Some clinicians cautioned that transparent risk data might increase cesarian requests &#x201C;for the price of honest communication of risk,&#x201D; while others felt it would reduce paternalism and enhance women&#x2019;s autonomy. Buckinghamshire participants emphasized its role in countering misinformation, particularly the perception that cesarian birth is inherently safer: &#x201C;Patients think c-section is the safer option, often misled by social media; the tool can help address this and decrease requests.&#x201D;</p><p>Concerns regarding over-reliance and deskilling were also raised, with one participant warning that &#x201C;it can deskill people&#x2026; you will take shortcuts after a while.<italic>&#x201D; Moreover,</italic> participants highlighted the need for clear protocols to ensure the tool complements rather than replaces expertise. Perspectives evolved across sites, shifting from early skepticism about being &#x201C;told what to do by a machine&#x201D; to recognition of the tool as &#x201C;an important piece of the jigsaw.<italic>&#x201D;</italic> Birmingham participants stressed balanced integration, underscoring that &#x201C;your clinical judgment is always going to be important&#x2014;see the patient beyond the technology.&#x201D; They also noted potential to rebuild trust in maternity care, with one participant observing that &#x201C;maternity is in the public eye because of serious incidents and poor care. Social media doesn&#x2019;t help. Trust is broken. Fit4Labour can decrease this.&#x201D;</p></sec></sec><sec id="s3-5"><title>Mixed Methods Integration: Joint Display Analysis</title><p>Integration of quantitative and qualitative findings revealed strong convergence, with both complementary and contrasting insights (<xref ref-type="table" rid="table4">Table 4</xref>).</p><p>Convergence (direct alignment) was evident as high SUS and SEQ scores aligned with qualitative reports of intuitive design and ease of use, while completion times paralleled clinicians&#x2019; descriptions of smoother workflows, which may translate to more efficient practice.</p><p>Complementarity (mutual enhancement) also emerged, with quantitative improvements in task completion times complementing qualitative concerns about resource constraints and highlighting both usability and systemic challenges. Quantitative differences between midwives and doctors were minor, but differences became evident for qualitative themes around escalation support and risk communication.</p><p>Dissonance (contrasting perspectives) appeared in 2 key areas: while learnability scores were high, participants still requested structured training, indicating that initial perceived ease of use of the Fit4Labour tool does not eliminate the need for formal instruction regarding its clinical application. Similarly, strong usability ratings contrasted with concerns about incomplete or &#x201C;missing&#x201D; risk factor coverage&#x2014;highlighting that usability alone does not guarantee clinical comprehensiveness and further understanding of the limitations of the tool is needed.</p><table-wrap id="t4" position="float"><label>Table 4.</label><caption><p>Mixed methods integration summary: convergence, complementarity, and dissonance across findings. Joint display illustrating alignment between quantitative and qualitative results, highlighting usability, workflow efficiency, and training needs.</p></caption><table id="table4" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Integration pattern and key findings</td><td align="left" valign="bottom">Evidence</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="2">Convergence</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Excellent usability</td><td align="left" valign="top">Validation phase SUS<sup><xref ref-type="table-fn" rid="table4fn1">a</xref></sup> scores (mean 85.8, SD10.2) independently met the "excellent" threshold and aligns with qualitative feedback stating both &#x201C;very intuitive&#x201D; and &#x201C;easy to use.&#x201D;</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Co-development progression</td><td align="left" valign="top">SUS scores across co-development versions reflect iterative refinement reaching the excellent threshold by v3.0, consistent with participants&#x2019; growing familiarity with the tool&#x2019;s &#x2019;co-pilot&#x2019; function.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Advanced feature complexity</td><td align="left" valign="top">More complex scenarios (eg, 4) had lowest scores (mean 5.7, SD 1.0), which aligns with concerns regarding the need for &#x201C;structured and mandatory training.&#x201D;</td></tr><tr><td align="left" valign="top" colspan="2">Complementarity</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Workflow integration</td><td align="left" valign="top">Within the validation phase, task completion times of 9.8 minutes were broadly feasible.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Performance predictability</td><td align="left" valign="top">Narrow SD (1.8 min) within the validation phase supported workflow consistency needs for &#x2019;rapid turnover in triage.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Professional group needs</td><td align="left" valign="top">Quantitative differences between midwives and doctors complemented qualitative emphasis on escalation support.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Infrastructure feasibility</td><td align="left" valign="top">Fast completion times (9.8 min) supported feasibility despite &#x201C;Wi-Fi,&#x201D; &#x201C;charging,&#x201D; and &#x201C;compatibility&#x201D; concerns.</td></tr><tr><td align="left" valign="top" colspan="2">Dissonance</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Learning versus training</td><td align="left" valign="top">High learnability scores (89.6%) contrasted with participants' expressed need for extensive training, reflecting the complexity of using the tool in clinical practice</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Performance versus comprehensiveness</td><td align="left" valign="top">Excellent usability scores contrasted with concerns regarding &#x201C;limited risk factors profile.&#x201D;</td></tr></tbody></table><table-wrap-foot><fn id="table4fn1"><p><sup>a</sup>SUS: System Usability Scale.</p></fn></table-wrap-foot></table-wrap></sec></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><sec id="s4-1"><title>Main Findings</title><p>This multicenter mixed methods study demonstrated that the Fit4Labour tool developed through intensive co-design at a single NHS hospital independently met the &#x201C;excellent&#x201D; usability threshold (SUS &#x003E;80) in simulated testing conditions at both validation sites, with consistent task completion times across 2 hospitals with different organizational contexts and digital maturity. Birmingham midwives reported lower usability scores (mean 76.3, SD 11.4), though still within the &#x2019;good&#x2019; range. This likely reflects the more critical evaluation standards based on their extensive clinical experience with existing triage systems, which strengthens the robustness of our validation findings.</p><p>Qualitative data reinforced these findings: participants described the Fit4Labour as a helpful triage and escalation tool, particularly for junior staff and as a shared &#x201C;one language&#x201D; for risk communication across professional boundaries. The spontaneous &#x201C;co-pilot&#x201D; analogy indicated that clinicians viewed the tool as supportive rather than substitutive, preserving autonomy while easing cognitive load. This preference for augmentation over automation mirrors findings from emergency triage settings, where professionals and patients alike favor hybrid digital-human approaches over fully automated solutions [<xref ref-type="bibr" rid="ref44">44</xref>]. Although midwives and doctors have distinct roles, both groups reported that the interface met their needs, suggesting that a single design can accommodate diverse professional requirements in simulated testing conditions.</p><p>Clinicians also identified areas for improvement, including incomplete risk factor profile coverage, infrastructure barriers that may complicate seamless integration, and the need for structured training to support consistent use.</p></sec><sec id="s4-2"><title>Comparison With Prior Work</title><p>Earlier evaluations of computerized cardiotocography systems in randomized controlled trials have shown limited benefit, with no clear improvements in neonatal outcomes or reductions in unnecessary interventions [<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref46">46</xref>]. Systematic reviews suggest that for decision-support tools to make a real difference, they must be interpretable, reproducible, and trusted by clinicians, rather than simply replicating the same inconsistencies seen in human interpretation [<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref47">47</xref>,<xref ref-type="bibr" rid="ref48">48</xref>]. Fernandes et al [<xref ref-type="bibr" rid="ref49">49</xref>]<italic>,</italic> in a systematic review of intelligent clinical decision support systems for emergency triage, found that many such systems lack a formal implementation phase and that validated systems consistently improved clinician decision-making; this study directly addresses this gap by combining algorithmic development with structured multicenter usability evaluation.</p><p>The Fit4Labour tool represents a promising evolution in this field. Unlike earlier systems based purely on human cardiotocography pattern recognition, it is a prognostic model trained on data from a large, multicenter clinical database, allowing it to produce standardized, evidence-based risk scores [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref33">33</xref>]. By providing clear, data-driven outputs, clinicians perceived the tool as having the potential to reduce variation in cardiotocography interpretation and to support less experienced staff, while complementing rather than replacing senior clinical judgment, perceptions that align with the tool&#x2019;s design intent but require prospective clinical evaluation to confirm.</p><p>These advantages are particularly relevant in the current maternity safety landscape. The UK Healthcare Safety Investigation Branch recently highlighted how unpredictable workloads and a constant need to juggle tasks in labor wards can compromise situational awareness and delay recognition of fetal compromise [<xref ref-type="bibr" rid="ref50">50</xref>]. Participants in this study felt that the Fit4Labour tool could help maintain an overview of the full clinical picture, reduce cognitive load, and minimize the risk of overlooking important patient information. By alerting users when data is missing or incomplete, the tool also aligns with human-factors principles of error-tolerant design [<xref ref-type="bibr" rid="ref51">51</xref>].</p><p>Similarly, national inquiries such as Ockenden and MBRRACE have underscored the role of poor communication and delayed escalation in adverse outcomes [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref30">30</xref>]. These findings resonate with observations from our study, where participants described using vague, non-specific expressions over the phone (eg, &#x201C;I&#x2019;m not happy with this trace&#x201D;) when escalating concerns about cardiotocography traces. Clinicians suggested that a numeric risk score could help reduce subjectivity in intrapartum communication, though this needs to be confirmed in adequately powered prospective studies.</p><p>Previous evaluations of computerized cardiotocography systems have reported variable user acceptance due to unclear risk calculations and scoring methods [<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref53">53</xref>]. In contrast, participants found the Fit4Labour tool intuitive and transparent, which likely contributed to its positive usability scores. They also expressed interest in greater clarity regarding how individual maternal and fetal factors influence the overall risk score, including the relative weight of each contributing variable. Showing how these factors, together with cardiotocography interpretation and population data, feed into the score could help clinicians better understand and trust the tool&#x2019;s output, rather than viewing it as a &#x201C;black box.&#x201D;</p><p>Finally, participants valued the unified interface that supported both midwives and doctors. Our findings indicate that a shared, role-sensitive interface can accommodate diverse professional needs while promoting interprofessional communication. This aligns with human-factors literature advocating shared mental models to bridge doctor&#x2013;midwife silos, reduce fears of hierarchical barriers when escalating, and ensure complete, consistent communication in high-risk settings [<xref ref-type="bibr" rid="ref54">54</xref>,<xref ref-type="bibr" rid="ref55">55</xref>]. The slightly lower scores observed among senior midwives at Birmingham are consistent with evidence from emergency department settings, where senior physicians have been shown to report greater frustration with health IT systems than residents, attributed to higher expectations shaped by prior workflows. [<xref ref-type="bibr" rid="ref56">56</xref>]</p></sec><sec id="s4-3"><title>Human Factors Innovation: Cognitive Support and Communication</title><p>Intrapartum care involves complex decisions under uncertainty, where cognitive load, fatigue, and time pressure can compromise situational awareness. Participants described the Fit4Labour tool as &#x201C;working for tired brains,&#x201D; highlighting its perceived value under conditions of fatigue, multitasking, and workload pressures, particularly relevant in maternity care. The design also appeared to support progressive disclosure: junior staff could rely on simple, color-coded outputs for rapid decision-making, while senior clinicians valued the ability to review detailed cardiotocography metrics and contributing risk factors. This layering helped ensure that transparency and autonomy were maintained without overloading users. In addition, when information was incomplete or omitted, the tool prompted users to add missing data, helping to reduce errors.</p></sec><sec id="s4-4"><title>Clinical Integration and Implementation Considerations</title><p>In our analysis of over 147,000 births, the Fit4Labour algorithm identified about 1 in 3 babies who later showed signs of severe compromise, using only the first 20 minutes of cardiotocography at the start of labor [<xref ref-type="bibr" rid="ref34">34</xref>]. Many of these babies were not recognized until 8&#x2010;10 hours later, when emergency intervention was needed, suggesting that harm experienced during the birth process might be curtailed or even prevented. Although these results come from retrospective cohort analysis rather than real-time use, participants suggested that making risk visible, readily available, and quantifiable could support earlier and more consistent decision-making, especially when early cardiotocography changes are subtle. With maternity-related litigation in the UK now exceeding &#x00A3;37 billion (more than the annual cost of running maternity services), there is an urgent need for preventive, evidence-based innovations that reduce avoidable harm and help rebuild trust in care [<xref ref-type="bibr" rid="ref57">57</xref>, <xref ref-type="bibr" rid="ref58">58</xref>].</p><p>Participants across all sites emphasized that structured clinician education remains essential for effective and consistent implementation. Training should go beyond button-clicking or navigation (interface use), focusing on supporting decisions and helping clinicians interpret risk, and communicating effectively with women. This approach ensures that the Fit4Labour <italic>tool</italic> outputs are translated into safe, evidence-based care rather than reducing decision-making to a &#x201C;tick-box&#x201D; exercise.</p><p>Interestingly, over nearly 2 and a half years of sessions, a noticeable shift in participants&#x2019; views emerged, reflecting the broader uptake of digital technologies and AI in health care, with early anxieties about &#x201C;being told what to do by a machine&#x201D; evolving into recognition of a novel digital tool as a potentially &#x201C;important piece of the puzzle&#x201D; that enhances, rather than constrains, professional autonomy. This gradual shift also highlights increasing confidence in technology and the potential of digital tools to support decision-making and improve escalation pathways [<xref ref-type="bibr" rid="ref59">59</xref>]. This trajectory is consistent with Longoni et al.&#x2019;s framework, in which resistance to medical artificial intelligence is primarily driven by &#x201C;uniqueness neglect,&#x201D; the concern that algorithms cannot account for individual patient characteristics. Fit4Labour tool&#x2019;s transparent, interpretable outputs and preservation of clinical autonomy directly address this concern. [<xref ref-type="bibr" rid="ref60">60</xref>]</p><p>Organizational readiness is likely to play a pivotal role in adoption. Digitally mature sites, such as Buckinghamshire, noted that the Fit4Labour tool could be easily integrated into existing workflows, while others cited unreliable Wi-Fi, limited computer access, poor and delayed IT support, and competing software as major barriers. These findings echo &#x2018;Consolidated Framework for Implementation Research (CFIR) v2.0,&#x2019; emphasizing that infrastructure, culture, and implementation support, through training, local champions, and change management, are as important as usability for successful adoption [<xref ref-type="bibr" rid="ref61">61</xref>].</p><p>Equity considerations also featured prominently in group discussions. Clinicians acknowledged the steps taken during co-development to promote inclusiveness in the user interface. These included design choices tested for accessibility among color-blind and dyslexic users, adaptations for staff wearing gloves when using touch tablets, such as larger buttons, and adjustments to font and button sizes to accommodate differences in visual acuity and hand size. However, participants also highlighted areas for further improvement. The current version is available only in English, which may create barriers for clinicians when explaining risk to non&#x2013;English-speaking patients. Participants noted that using an interpreter or relying on a family member for translation, particularly over the phone, can make it more difficult to use the tool effectively in real time. Cultural factors may also influence how risk is communicated and perceived, underscoring the need for continued research and iterative refinement. Finally, participants noted that ethnic minority groups were not specifically represented and are likely underrepresented in the dataset used to refine the Fit4Labour algorithm, which could limit its generalizability. Ensuring inclusive design and representative data will be essential to prevent the reinforcement of existing inequities in maternity care [<xref ref-type="bibr" rid="ref62">62</xref>].</p></sec><sec id="s4-5"><title>Practical Implication for Digital Health Tools Development</title><p>Digital health projects often allocate significant resources to local customization (often between 15%&#x2010;20% of implementation budgets) [<xref ref-type="bibr" rid="ref63">63</xref>-<xref ref-type="bibr" rid="ref65">65</xref>]. In this study, the Fit4Labour tool maintained high usability across 3 hospitals with different organizational contexts and IT infrastructures when tested in the same version. This observation raises a practical question of whether intensive co-development at the outset might reduce the need for postdeployment customization. However, establishing this would require prospective studies comparing implementation costs and outcomes for tools developed with versus without intensive participatory design.</p></sec><sec id="s4-6"><title>Future Research</title><p>Our team will conduct a regulated clinical evaluation of the Fit4Labour tool across multiple NHS sites to assess real-world safety, usability, and workflow integration, in line with Medicines and Healthcare products Regulatory Agency requirements for medical device approval [<xref ref-type="bibr" rid="ref66">66</xref>]. This study will focus on outcomes such as escalation timeliness, reliability of communication, handover quality, and patient safety indicators.</p><p>We will also examine factors influencing sustained use and implementation, including the impact of structured training, local clinical champions, and integration into existing hospital systems. In parallel, our team will build on early health economic modeling to assess whether the usability patterns observed in this study translate into measurable cost savings and better clinical outcomes.</p><p>Beyond our own work, external validation in non-NHS health care systems is an important next step to determine whether the tool&#x2019;s core design principles transfer to other diverse health care contexts.</p><p>Finally, we will continue to engage directly with women, families, and PPI panels to explore how different ways of presenting risk information affect perception, autonomy, and trust. Embedding patient perspectives throughout these evaluations will help ensure that digital tools strengthen shared decision-making and enhance both safety and the experience of care.</p></sec><sec id="s4-7"><title>Strengths and Limitations</title><p>This study has several strengths. The multicenter design, spanning 3 NHS hospitals with different organizational contexts and levels of digital maturity, provided a robust test of both usability and scalability across diverse settings. The mixed methods approach enabled convergence of quantitative usability metrics with qualitative insights into workflow, communication, and professional practice. Importantly, the locked-version (v4.0) validation offered a more rigorous test of scalability across diverse settings than is usually attempted in health care technology evaluations.</p><p>Our study also has important limitations. Usability testing was conducted in structured environments rather than during real-time clinical care, which may have increased observed task efficiency. However, as all sites used the same testing protocol, the relative comparisons between validation sites remain valid, even if absolute values might differ in clinical practice. Recruitment through departmental managers could have favored digitally confident clinicians, although efforts were made to capture a range of roles and experience. The involvement of members of the development team in evaluation may also have introduced bias, but this was mitigated by standardized protocols and independent analysis. The relatively small sample size (n=26) is consistent with Nielsen&#x2019;s guidance for usability studies and similar mixed methods implementation studies. No inferential statistical testing was performed, which is consistent with the exploratory descriptive aims of this work. Moreover, phase 1 and phase 2 differed simultaneously in tool version, participants, and clinical site, making between-phase inferential comparison inappropriate. Finally, the study was confined to NHS hospitals in the United Kingdom, which limits direct generalizability to health care systems with different funding models, workforce structures, technological infrastructures, or cultural norms. However, the 3 sites were selected to capture meaningful variation in organizational context and digital maturity, and the human-factors frameworks and usability instruments applied are internationally validated. The core challenges addressed, variable cardiotocography interpretation, escalation delays, and risk communication, are not unique to the NHS and have been documented in maternity systems internationally. Future evaluation in non-NHS settings will be essential to establish broader applicability.</p></sec><sec id="s4-8"><title>Conclusions</title><p>This study demonstrates that systematic co-development, grounded in human-factors principles, can produce clinician-facing decision-support tools that independently meet established usability benchmarks across NHS hospitals with different organizational contexts and digital maturity. The locked version (v4.0) showed high usability at both validation sites (SUS mean 80.7, SD 10.8 Birmingham vs SUS mean 90.8, SD 7.2 Buckinghamshire). Clinicians described the Fit4Labour tool as a supportive, like a &#x201C;co-pilot&#x201D; rather than a replacement for clinical judgment, and that it provided a shared language for risk communication with potential to strengthen confidence in escalation decisions. Other factors, such as organizational readiness, structured training, and adequate infrastructure support, will be important enablers of adoption. Whether usability in simulated settings translates to improved clinical outcomes in real-world practice, and whether these findings generalize beyond NHS settings, requires prospective evaluation.</p></sec></sec></body><back><ack><p>We thank the Patient and Public Involvement panel from the Oxford Labor Monitoring Group for their advisory role throughout this study. We are grateful to all participating health care professionals, including midwives and doctors across the 3 participating hospitals within the National Health Service (NHS) in England, who provided invaluable feedback during system testing. Special thanks to the clinical managers, research midwives, and fetal monitoring midwives who facilitated this multisite study through their organizational support and coordination of testing sessions. We also acknowledge Dr. Sandra Morales Rios, researcher at the University of Oxford, for contribution to qualitative data coding and interrater reliability assessment.</p></ack><notes><sec><title>Funding</title><p>This study was supported by a National Institute for Health and Care Research (NIHR) Invention for Innovation (i4i) Product Development Award (NIHR202117). The views expressed are those of the authors and not necessarily those of the NIHR or the Department of Health and Social Care.</p></sec></notes><fn-group><fn fn-type="con"><p>MT and XL designed and conducted the usability testing sessions and focus groups, extracted quantitative data, and performed qualitative coding analysis. MT conducted the statistical analysis of usability metrics and completion time data. DH contributed to qualitative data coding and provided interrater reliability validation. KG and JT served as the tool developers and software engineers, implementing iterative design modifications based on user feedback and providing technical support throughout the co-development process to enhance the Fit4Labour system. AG conceived the original Fit4Labour tool concept and provided overall oversight and strategic guidance for the project. All authors made substantial contributions to manuscript preparation, critically reviewed the content, and provided final approval for publication.</p></fn><fn fn-type="conflict"><p>All authors are or have been members of the Oxford Labor Monitoring Group at the University of Oxford, which conducts research on intrapartum fetal monitoring and decision-support tools. This study involved usability testing and evaluation of the Fit4Labour tool, which may be commercialized in the future through a planned company called Safer Birth. No commercial entity provided funding for this research, and the potential for commercialization did not influence the study design, data analysis, or interpretation. All results are reported transparently, regardless of their implications for future commercialization. JH is supported by a UKRI Future Leaders Fellowship (MR/Y033833/1).</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">BHT</term><def><p>Buckinghamshire Healthcare NHS Trust</p></def></def-item><def-item><term id="abb2">BWC</term><def><p>Birmingham Women&#x2019;s and Children&#x2019;s NHS Foundation Trust</p></def></def-item><def-item><term id="abb3">NHS</term><def><p>National Health Service</p></def></def-item><def-item><term id="abb4">NIHR</term><def><p>National Institute for Health and Care Research</p></def></def-item><def-item><term id="abb5">OUH</term><def><p>Oxford University Hospitals NHS Foundation Trust</p></def></def-item><def-item><term id="abb6">PPI</term><def><p>patient and public involvement</p></def></def-item><def-item><term id="abb7">SEIPS</term><def><p>Systems Engineering Initiative for Patient Safety</p></def></def-item><def-item><term id="abb8">SEQ</term><def><p>Single Ease Question</p></def></def-item><def-item><term id="abb9">SUS</term><def><p>System Usability Scale</p></def></def-item><def-item><term id="abb10">UK</term><def><p>United Kingdom</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>Shortliffe</surname><given-names>EH</given-names> </name><name name-style="western"><surname>Sep&#x00FA;lveda</surname><given-names>MJ</given-names> </name></person-group><article-title>Clinical decision support in the era of artificial intelligence</article-title><source>JAMA</source><year>2018</year><month>12</month><day>4</day><volume>320</volume><issue>21</issue><fpage>2199</fpage><lpage>2200</lpage><pub-id pub-id-type="doi">10.1001/jama.2018.17163</pub-id><pub-id pub-id-type="medline">30398550</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>Topol</surname><given-names>EJ</given-names> </name></person-group><article-title>High-performance medicine: the convergence of human and artificial intelligence</article-title><source>Nat Med</source><year>2019</year><month>01</month><volume>25</volume><issue>1</issue><fpage>44</fpage><lpage>56</lpage><pub-id pub-id-type="doi">10.1038/s41591-018-0300-7</pub-id><pub-id pub-id-type="medline">30617339</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>Rajkomar</surname><given-names>A</given-names> </name><name name-style="western"><surname>Dean</surname><given-names>J</given-names> </name><name name-style="western"><surname>Kohane</surname><given-names>I</given-names> </name></person-group><article-title>Machine learning in medicine</article-title><source>N Engl J Med</source><year>2019</year><month>04</month><day>4</day><volume>380</volume><issue>14</issue><fpage>1347</fpage><lpage>1358</lpage><pub-id pub-id-type="doi">10.1056/NEJMra1814259</pub-id><pub-id pub-id-type="medline">30943338</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>Lehne</surname><given-names>M</given-names> </name><name name-style="western"><surname>Sass</surname><given-names>J</given-names> </name><name name-style="western"><surname>Essenwanger</surname><given-names>A</given-names> </name><name name-style="western"><surname>Schepers</surname><given-names>J</given-names> </name><name name-style="western"><surname>Thun</surname><given-names>S</given-names> </name></person-group><article-title>Why digital medicine depends on interoperability</article-title><source>NPJ Digit Med</source><year>2019</year><volume>2</volume><issue>1</issue><fpage>79</fpage><pub-id pub-id-type="doi">10.1038/s41746-019-0158-1</pub-id><pub-id pub-id-type="medline">31453374</pub-id></nlm-citation></ref><ref id="ref5"><label>5</label><nlm-citation citation-type="book"><source>Global Strategy on Digital Health 2020-2025</source><year>2021</year><publisher-name>World Health Organization</publisher-name><pub-id pub-id-type="other">978-92-4-002092-4</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>Ayres&#x2010;de&#x2010;Campos</surname><given-names>D</given-names> </name><name name-style="western"><surname>Spong</surname><given-names>CY</given-names> </name><name name-style="western"><surname>Chandraharan</surname><given-names>E</given-names> </name><collab>FIGO Intrapartum Fetal Monitoring Expert Consensus Panel</collab></person-group><article-title>FIGO consensus guidelines on intrapartum fetal monitoring: cardiotocography</article-title><source>Intl J Gynecology &#x0026; Obste</source><year>2015</year><month>10</month><volume>131</volume><issue>1</issue><fpage>13</fpage><lpage>24</lpage><pub-id pub-id-type="doi">10.1016/j.ijgo.2015.06.020</pub-id></nlm-citation></ref><ref id="ref7"><label>7</label><nlm-citation citation-type="book"><source>WHO Recommendations: Intrapartum Care for a Positive Childbirth Experience</source><year>2018</year><publisher-name>World Health Organization</publisher-name><pub-id pub-id-type="other">978-92-4-155021-5</pub-id></nlm-citation></ref><ref id="ref8"><label>8</label><nlm-citation citation-type="web"><article-title>Fetal monitoring in labour [NG229]</article-title><source>National Institute for Health and Care Excellence (NICE)</source><year>2022</year><access-date>2026-07-11</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.nice.org.uk/guidance/ng229">https://www.nice.org.uk/guidance/ng229</ext-link></comment></nlm-citation></ref><ref id="ref9"><label>9</label><nlm-citation citation-type="book"><person-group person-group-type="editor"><name name-style="western"><surname>Norman</surname><given-names>DA</given-names> </name></person-group><source>User Centered System Design: New Perspectives on Human-Computer Interaction</source><year>1986</year><publisher-name>CRC Press</publisher-name><pub-id pub-id-type="doi">10.1201/9780367807320</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>Bates</surname><given-names>DW</given-names> </name><name name-style="western"><surname>Kuperman</surname><given-names>GJ</given-names> </name><name name-style="western"><surname>Wang</surname><given-names>S</given-names> </name><etal/></person-group><article-title>Ten commandments for effective clinical decision support: making the practice of evidence-based medicine a reality</article-title><source>J Am Med Inform Assoc</source><year>2003</year><volume>10</volume><issue>6</issue><fpage>523</fpage><lpage>530</lpage><pub-id pub-id-type="doi">10.1197/jamia.M1370</pub-id><pub-id pub-id-type="medline">12925543</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>Kawamoto</surname><given-names>K</given-names> </name><name name-style="western"><surname>Houlihan</surname><given-names>CA</given-names> </name><name name-style="western"><surname>Balas</surname><given-names>EA</given-names> </name><name name-style="western"><surname>Lobach</surname><given-names>DF</given-names> </name></person-group><article-title>Improving clinical practice using clinical decision support systems: a systematic review of trials to identify features critical to success</article-title><source>BMJ</source><year>2005</year><month>04</month><day>2</day><volume>330</volume><issue>7494</issue><fpage>765</fpage><pub-id pub-id-type="doi">10.1136/bmj.38398.500764.8F</pub-id><pub-id pub-id-type="medline">15767266</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>Carayon</surname><given-names>P</given-names> </name><name name-style="western"><surname>Schoofs Hundt</surname><given-names>A</given-names> </name><name name-style="western"><surname>Karsh</surname><given-names>BT</given-names> </name><etal/></person-group><article-title>Work system design for patient safety: the SEIPS model</article-title><source>Qual Saf Health Care</source><year>2006</year><month>12</month><volume>15 Suppl 1</volume><issue>Suppl 1</issue><fpage>i50</fpage><lpage>8</lpage><pub-id pub-id-type="doi">10.1136/qshc.2005.015842</pub-id><pub-id pub-id-type="medline">17142610</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>Blandford</surname><given-names>A</given-names> </name><name name-style="western"><surname>Furniss</surname><given-names>D</given-names> </name><name name-style="western"><surname>Vincent</surname><given-names>C</given-names> </name></person-group><article-title>Patient safety and interactive medical devices: realigning work as imagined and work as done</article-title><source>Clin Risk</source><year>2014</year><month>09</month><volume>20</volume><issue>5</issue><fpage>107</fpage><lpage>110</lpage><pub-id pub-id-type="doi">10.1177/1356262214556550</pub-id><pub-id pub-id-type="medline">25866466</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>Johnson</surname><given-names>CM</given-names> </name><name name-style="western"><surname>Johnson</surname><given-names>TR</given-names> </name><name name-style="western"><surname>Zhang</surname><given-names>J</given-names> </name></person-group><article-title>A user-centered framework for redesigning health care interfaces</article-title><source>J Biomed Inform</source><year>2005</year><month>02</month><volume>38</volume><issue>1</issue><fpage>75</fpage><lpage>87</lpage><pub-id pub-id-type="doi">10.1016/j.jbi.2004.11.005</pub-id><pub-id pub-id-type="medline">15694887</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>Cresswell</surname><given-names>KM</given-names> </name><name name-style="western"><surname>Bates</surname><given-names>DW</given-names> </name><name name-style="western"><surname>Sheikh</surname><given-names>A</given-names> </name></person-group><article-title>Ten key considerations for the successful implementation and adoption of large-scale health information technology</article-title><source>J Am Med Inform Assoc</source><year>2013</year><month>06</month><volume>20</volume><issue>e1</issue><fpage>e9</fpage><lpage>e13</lpage><pub-id pub-id-type="doi">10.1136/amiajnl-2013-001684</pub-id><pub-id pub-id-type="medline">23599226</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>van Gemert-Pijnen</surname><given-names>JL</given-names> </name></person-group><article-title>Implementation of health technology: directions for research and practice</article-title><source>Front Digit Health</source><year>2022</year><volume>4</volume><fpage>1030194</fpage><pub-id pub-id-type="doi">10.3389/fdgth.2022.1030194</pub-id><pub-id pub-id-type="medline">36440459</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>Sittig</surname><given-names>DF</given-names> </name><name name-style="western"><surname>Singh</surname><given-names>H</given-names> </name></person-group><article-title>Defining health information technology-related errors: new developments since to err is human</article-title><source>Arch Intern Med</source><year>2011</year><month>07</month><day>25</day><volume>171</volume><issue>14</issue><fpage>1281</fpage><lpage>1284</lpage><pub-id pub-id-type="doi">10.1001/archinternmed.2011.327</pub-id><pub-id pub-id-type="medline">21788544</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>Yusof</surname><given-names>MM</given-names> </name><name name-style="western"><surname>Takeda</surname><given-names>T</given-names> </name><name name-style="western"><surname>Shimai</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Mihara</surname><given-names>N</given-names> </name><name name-style="western"><surname>Matsumura</surname><given-names>Y</given-names> </name></person-group><article-title>Evaluating health information systems-related errors using the human, organization, process, technology-fit (HOPT-fit) framework</article-title><source>Health Informatics J</source><year>2024</year><volume>30</volume><issue>2</issue><fpage>14604582241252763</fpage><pub-id pub-id-type="doi">10.1177/14604582241252763</pub-id><pub-id pub-id-type="medline">38805345</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>Cahill</surname><given-names>M</given-names> </name><name name-style="western"><surname>Cleary</surname><given-names>BJ</given-names> </name><name name-style="western"><surname>Cullinan</surname><given-names>S</given-names> </name></person-group><article-title>The influence of electronic health record design on usability and medication safety: systematic review</article-title><source>BMC Health Serv Res</source><year>2025</year><month>01</month><day>6</day><volume>25</volume><issue>1</issue><fpage>31</fpage><pub-id pub-id-type="doi">10.1186/s12913-024-12060-2</pub-id><pub-id pub-id-type="medline">39762805</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>Creswell</surname><given-names>L</given-names> </name><name name-style="western"><surname>Lindow</surname><given-names>BJ</given-names> </name><name name-style="western"><surname>Lindow</surname><given-names>SW</given-names> </name><etal/></person-group><article-title>A retrospective observational study of labour ward work Intensity: the challenge of maternity staffing</article-title><source>Eur J Obstetrics &#x0026;amp; Gynecol Reprod Biol</source><year>2023</year><month>07</month><volume>286</volume><fpage>90</fpage><lpage>94</lpage><pub-id pub-id-type="doi">10.1016/j.ejogrb.2023.05.021</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>Turner</surname><given-names>L</given-names> </name><name name-style="western"><surname>Ball</surname><given-names>J</given-names> </name><name name-style="western"><surname>Meredith</surname><given-names>P</given-names> </name><name name-style="western"><surname>Kitson-Reynolds</surname><given-names>E</given-names> </name><name name-style="western"><surname>Griffiths</surname><given-names>P</given-names> </name></person-group><article-title>The association between midwifery staffing and reported harmful incidents: a cross-sectional analysis of routinely collected data</article-title><source>BMC Health Serv Res</source><volume>24</volume><issue>1</issue><pub-id pub-id-type="doi">10.1186/s12913-024-10812-8</pub-id></nlm-citation></ref><ref id="ref22"><label>22</label><nlm-citation citation-type="report"><article-title>Maternity triage (Good Practice Paper No. 17)</article-title><year>2023</year><access-date>2026-07-11</access-date><publisher-name>RCOG</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://www.rcog.org.uk/guidance/browse-all-guidance/good-practice-papers/maternity-triage-good-practice-paper-no-17/">https://www.rcog.org.uk/guidance/browse-all-guidance/good-practice-papers/maternity-triage-good-practice-paper-no-17/</ext-link></comment></nlm-citation></ref><ref id="ref23"><label>23</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Park</surname><given-names>S</given-names> </name><name name-style="western"><surname>Marquard</surname><given-names>J</given-names> </name></person-group><article-title>Nurse-centered co-design of an electronic health record nursing summary</article-title><source>Human Factors in Healthcare</source><year>2024</year><month>06</month><volume>5</volume><fpage>100065</fpage><pub-id pub-id-type="doi">10.1016/j.hfh.2024.100065</pub-id></nlm-citation></ref><ref id="ref24"><label>24</label><nlm-citation citation-type="web"><article-title>Intrapartum care [NG235]</article-title><source>National Institute for Health and Care Excellence (NICE)</source><year>2023</year><access-date>2026-07-11</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.nice.org.uk/guidance/ng235">https://www.nice.org.uk/guidance/ng235</ext-link></comment></nlm-citation></ref><ref id="ref25"><label>25</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Lovers</surname><given-names>A</given-names> </name><name name-style="western"><surname>Daumer</surname><given-names>M</given-names> </name><name name-style="western"><surname>Frasch</surname><given-names>MG</given-names> </name><etal/></person-group><article-title>Advancements in fetal heart rate monitoring: a report on opportunities and strategic initiatives for better intrapartum care</article-title><source>BJOG</source><year>2025</year><month>06</month><volume>132</volume><issue>7</issue><fpage>853</fpage><lpage>866</lpage><pub-id pub-id-type="doi">10.1111/1471-0528.18097</pub-id><pub-id pub-id-type="medline">39971749</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>Rei</surname><given-names>M</given-names> </name><name name-style="western"><surname>Tavares</surname><given-names>S</given-names> </name><name name-style="western"><surname>Pinto</surname><given-names>P</given-names> </name><etal/></person-group><article-title>Interobserver agreement in CTG interpretation using the 2015 FIGO guidelines for intrapartum fetal monitoring</article-title><source>Eur J Obst Gynecol Reprod Biol</source><year>2016</year><month>10</month><volume>205</volume><fpage>27</fpage><lpage>31</lpage><pub-id pub-id-type="doi">10.1016/j.ejogrb.2016.08.017</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>Neri</surname><given-names>S</given-names> </name><name name-style="western"><surname>Ramirez Zegarra</surname><given-names>R</given-names> </name><name name-style="western"><surname>Dininno</surname><given-names>M</given-names> </name><name name-style="western"><surname>Di Pasquo</surname><given-names>E</given-names> </name><name name-style="western"><surname>Tagliaferri</surname><given-names>S</given-names> </name><name name-style="western"><surname>Ghi</surname><given-names>T</given-names> </name></person-group><article-title>Interobserver agreement of intrapartum cardiotocography interpretation by midwives using current FIGO and physiology-based guidelines</article-title><source>J Mater Fetal Neonatal Med</source><year>2024</year><month>01</month><day>2</day><volume>37</volume><issue>1</issue><pub-id pub-id-type="doi">10.1080/14767058.2024.2425758</pub-id></nlm-citation></ref><ref id="ref28"><label>28</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Friedman</surname><given-names>AM</given-names> </name><name name-style="western"><surname>Campbell</surname><given-names>ML</given-names> </name><name name-style="western"><surname>Kline</surname><given-names>CR</given-names> </name><name name-style="western"><surname>Wiesner</surname><given-names>S</given-names> </name><name name-style="western"><surname>D&#x2019;Alton</surname><given-names>ME</given-names> </name><name name-style="western"><surname>Shields</surname><given-names>LE</given-names> </name></person-group><article-title>Implementing obstetric early warning systems</article-title><source>AJP Rep</source><year>2018</year><month>04</month><volume>8</volume><issue>2</issue><fpage>e79</fpage><lpage>e84</lpage><pub-id pub-id-type="doi">10.1055/s-0038-1641569</pub-id><pub-id pub-id-type="medline">29686937</pub-id></nlm-citation></ref><ref id="ref29"><label>29</label><nlm-citation citation-type="report"><person-group person-group-type="author"><name name-style="western"><surname>Ockenden</surname><given-names>D</given-names> </name></person-group><article-title>Findings, conclusions and essential actions from the independent review of maternity services at the shrewsbury and telford hospital NHS trust</article-title><year>2022</year><access-date>2026-07-11</access-date><publisher-name>Department of Health and Social Care</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://www.gov.uk/government/publications/final-report-of-the-ockenden-review/ockenden-review-summary-of-findings-conclusions-and-essential-actions">https://www.gov.uk/government/publications/final-report-of-the-ockenden-review/ockenden-review-summary-of-findings-conclusions-and-essential-actions</ext-link></comment></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>Knight</surname><given-names>M</given-names> </name><name name-style="western"><surname>Bunch</surname><given-names>K</given-names> </name><name name-style="western"><surname>Tuffnell</surname><given-names>D</given-names> </name><etal/></person-group><source>Saving Lives, Improving Mothers&#x2019; Care-Lessons Learned to Inform Maternity Care from the UK and Ireland Confidential Enquiries into Maternal Deaths and Morbidity 2017-19</source><year>2021</year><publisher-name>MBRRACE-UK</publisher-name><pub-id pub-id-type="other">978-1-8383678-9-3</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>Charles</surname><given-names>C</given-names> </name><name name-style="western"><surname>Gafni</surname><given-names>A</given-names> </name><name name-style="western"><surname>Whelan</surname><given-names>T</given-names> </name></person-group><article-title>Shared decision-making in the medical encounter: what does it mean? (or it takes at least two to tango)</article-title><source>Soc Sci Med</source><year>1997</year><month>03</month><volume>44</volume><issue>5</issue><fpage>681</fpage><lpage>692</lpage><pub-id pub-id-type="doi">10.1016/s0277-9536(96)00221-3</pub-id><pub-id pub-id-type="medline">9032835</pub-id></nlm-citation></ref><ref id="ref32"><label>32</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><collab>INFANT Collaborative Group</collab></person-group><article-title>Computerised interpretation of fetal heart rate during labour (INFANT): a randomised controlled trial</article-title><source>Lancet</source><year>2017</year><month>04</month><day>29</day><volume>389</volume><issue>10080</issue><fpage>1719</fpage><lpage>1729</lpage><pub-id pub-id-type="doi">10.1016/S0140-6736(17)30568-8</pub-id><pub-id pub-id-type="medline">28341515</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>Ayres-de-Campos</surname><given-names>D</given-names> </name><name name-style="western"><surname>Sousa</surname><given-names>P</given-names> </name><name name-style="western"><surname>Costa</surname><given-names>A</given-names> </name><name name-style="western"><surname>Bernardes</surname><given-names>J</given-names> </name></person-group><article-title>Omniview-SisPorto 3.5 - a central fetal monitoring station with online alerts based on computerized cardiotocogram+ST event analysis</article-title><source>J Perinat Med</source><year>2008</year><volume>36</volume><issue>3</issue><fpage>260</fpage><lpage>264</lpage><pub-id pub-id-type="doi">10.1515/JPM.2008.030</pub-id><pub-id pub-id-type="medline">18576938</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>Bozhilova</surname><given-names>LV</given-names> </name><name name-style="western"><surname>Ugwumadu</surname><given-names>A</given-names> </name><name name-style="western"><surname>Chong</surname><given-names>HP</given-names> </name><etal/></person-group><article-title>A prognostic model for use at labour onset to estimate the risk of severe fetal compromise at birth: development and validation with over 145,000 electronic health records</article-title><source>Lancet Digital Health (forthcoming)</source><year>2026</year></nlm-citation></ref><ref id="ref35"><label>35</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Hollan</surname><given-names>J</given-names> </name><name name-style="western"><surname>Hutchins</surname><given-names>E</given-names> </name><name name-style="western"><surname>Kirsh</surname><given-names>D</given-names> </name></person-group><article-title>Distributed cognition: toward a new foundation for human-computer interaction research</article-title><source>ACM Transactions on Computer-Human</source><year>2000</year><volume>Interaction7</volume><fpage>174</fpage><lpage>196</lpage><pub-id pub-id-type="doi">10.1145/353485.353487</pub-id></nlm-citation></ref><ref id="ref36"><label>36</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Holden</surname><given-names>RJ</given-names> </name><name name-style="western"><surname>Carayon</surname><given-names>P</given-names> </name><name name-style="western"><surname>Gurses</surname><given-names>AP</given-names> </name><etal/></person-group><article-title>SEIPS 2.0: a human factors framework for studying and improving the work of healthcare professionals and patients</article-title><source>Ergonomics</source><year>2013</year><volume>56</volume><issue>11</issue><fpage>1669</fpage><lpage>1686</lpage><pub-id pub-id-type="doi">10.1080/00140139.2013.838643</pub-id><pub-id pub-id-type="medline">24088063</pub-id></nlm-citation></ref><ref id="ref37"><label>37</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><source>Usability Engineering</source><year>1994</year><publisher-name>Morgan Kaufmann</publisher-name><pub-id pub-id-type="other">978-0-08-052029-2</pub-id></nlm-citation></ref><ref id="ref38"><label>38</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Creswell</surname><given-names>JW</given-names> </name><name name-style="western"><surname>Plano Clark</surname><given-names>VL</given-names> </name></person-group><source>Designing and Conducting Mixed Methods Research</source><year>2017</year><publisher-name>Sage Publications</publisher-name><pub-id pub-id-type="other">978-1-4833-4437-9</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>Palinkas</surname><given-names>LA</given-names> </name><name name-style="western"><surname>Horwitz</surname><given-names>SM</given-names> </name><name name-style="western"><surname>Green</surname><given-names>CA</given-names> </name><name name-style="western"><surname>Wisdom</surname><given-names>JP</given-names> </name><name name-style="western"><surname>Duan</surname><given-names>N</given-names> </name><name name-style="western"><surname>Hoagwood</surname><given-names>K</given-names> </name></person-group><article-title>Purposeful sampling for qualitative data collection and analysis in mixed method implementation research</article-title><source>Adm Policy Ment Health</source><year>2015</year><month>09</month><volume>42</volume><issue>5</issue><fpage>533</fpage><lpage>544</lpage><pub-id pub-id-type="doi">10.1007/s10488-013-0528-y</pub-id><pub-id pub-id-type="medline">24193818</pub-id></nlm-citation></ref><ref id="ref40"><label>40</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 quick and dirty 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="doi">10.1201/9781498710411-35</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>Bangor</surname><given-names>A</given-names> </name><name name-style="western"><surname>Kortum</surname><given-names>P</given-names> </name><name name-style="western"><surname>Miller</surname><given-names>J</given-names> </name></person-group><article-title>Determining what individual SUS scores mean: adding an adjective rating scale</article-title><source>J Usability</source><year>2009</year><access-date>2026-07-11</access-date><fpage>114</fpage><lpage>123</lpage><comment><ext-link ext-link-type="uri" xlink:href="https://dl.acm.org/doi/10.5555/2835587.2835589">https://dl.acm.org/doi/10.5555/2835587.2835589</ext-link></comment></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>Braun</surname><given-names>V</given-names> </name><name name-style="western"><surname>Clarke</surname><given-names>V</given-names> </name></person-group><article-title>Using thematic analysis in psychology</article-title><source>Qual Res Psychol</source><year>2006</year><month>01</month><volume>3</volume><issue>2</issue><fpage>77</fpage><lpage>101</lpage><pub-id pub-id-type="doi">10.1191/1478088706qp063oa</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>Braun</surname><given-names>V</given-names> </name><name name-style="western"><surname>Clarke</surname><given-names>V</given-names> </name></person-group><article-title>Reflecting on reflexive thematic analysis</article-title><source>Qual Res Sport Exer Health</source><year>2019</year><month>08</month><day>8</day><volume>11</volume><issue>4</issue><fpage>589</fpage><lpage>597</lpage><pub-id pub-id-type="doi">10.1080/2159676X.2019.1628806</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>Morlotti</surname><given-names>C</given-names> </name><name name-style="western"><surname>Cattaneo</surname><given-names>M</given-names> </name><name name-style="western"><surname>Paleari</surname><given-names>S</given-names> </name><name name-style="western"><surname>Manelli</surname><given-names>F</given-names> </name><name name-style="western"><surname>Locati</surname><given-names>F</given-names> </name></person-group><article-title>The digitalization of emergency department triage: the perspectives of health professionals and patients</article-title><source>BMC Health Serv Res</source><year>1406</year><volume>24</volume><issue>1</issue><pub-id pub-id-type="doi">10.1186/s12913-024-11862-8</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>Ben M&#x2019;Barek</surname><given-names>I</given-names> </name><name name-style="western"><surname>Jauvion</surname><given-names>G</given-names> </name><name name-style="western"><surname>Ceccaldi</surname><given-names>PF</given-names> </name></person-group><article-title>Computerized cardiotocography analysis during labor &#x2013; a state&#x2010;of&#x2010;the&#x2010;art review</article-title><source>Acta Obstet Gynecol Scand</source><year>2023</year><month>02</month><volume>102</volume><issue>2</issue><fpage>130</fpage><lpage>137</lpage><pub-id pub-id-type="doi">10.1111/aogs.14498</pub-id><pub-id pub-id-type="medline">36541016</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>Tsipoura</surname><given-names>A</given-names> </name><name name-style="western"><surname>Giaxi</surname><given-names>P</given-names> </name><name name-style="western"><surname>Sarantaki</surname><given-names>A</given-names> </name><name name-style="western"><surname>Gourounti</surname><given-names>K</given-names> </name></person-group><article-title>Conventional cardiotocography versus computerized CTG analysis and perinatal outcomes: a systematic review</article-title><source>Maedica (Bucur)</source><year>2023</year><month>09</month><volume>18</volume><issue>3</issue><fpage>483</fpage><lpage>489</lpage><pub-id pub-id-type="doi">10.26574/maedica.2023.18.3.483</pub-id><pub-id pub-id-type="medline">38023753</pub-id></nlm-citation></ref><ref id="ref47"><label>47</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>O&#x2019;Sullivan</surname><given-names>ME</given-names> </name><name name-style="western"><surname>Considine</surname><given-names>EC</given-names> </name><name name-style="western"><surname>O&#x2019;Riordan</surname><given-names>M</given-names> </name><name name-style="western"><surname>Marnane</surname><given-names>WP</given-names> </name><name name-style="western"><surname>Rennie</surname><given-names>JM</given-names> </name><name name-style="western"><surname>Boylan</surname><given-names>GB</given-names> </name></person-group><article-title>Challenges of developing robust AI for intrapartum fetal heart rate monitoring</article-title><source>Front Artif Intell</source><year>2021</year><volume>4</volume><fpage>765210</fpage><pub-id pub-id-type="doi">10.3389/frai.2021.765210</pub-id><pub-id pub-id-type="medline">34765970</pub-id></nlm-citation></ref><ref id="ref48"><label>48</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Balayla</surname><given-names>J</given-names> </name><name name-style="western"><surname>Shrem</surname><given-names>G</given-names> </name></person-group><article-title>Use of artificial intelligence (AI) in the interpretation of intrapartum fetal heart rate (FHR) tracings: a systematic review and meta-analysis</article-title><source>Arch Gynecol Obstet</source><year>2019</year><month>07</month><volume>300</volume><issue>1</issue><fpage>7</fpage><lpage>14</lpage><pub-id pub-id-type="doi">10.1007/s00404-019-05151-7</pub-id><pub-id pub-id-type="medline">31053949</pub-id></nlm-citation></ref><ref id="ref49"><label>49</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Fernandes</surname><given-names>M</given-names> </name><name name-style="western"><surname>Vieira</surname><given-names>SM</given-names> </name><name name-style="western"><surname>Leite</surname><given-names>F</given-names> </name><name name-style="western"><surname>Palos</surname><given-names>C</given-names> </name><name name-style="western"><surname>Finkelstein</surname><given-names>S</given-names> </name><name name-style="western"><surname>Sousa</surname><given-names>JMC</given-names> </name></person-group><article-title>Clinical decision support systems for triage in the emergency department using intelligent systems: a review</article-title><source>Artif Intell Med</source><year>2020</year><month>01</month><volume>102</volume><fpage>101762</fpage><pub-id pub-id-type="doi">10.1016/j.artmed.2019.101762</pub-id><pub-id pub-id-type="medline">31980099</pub-id></nlm-citation></ref><ref id="ref50"><label>50</label><nlm-citation citation-type="report"><article-title>Investigation report: delays to intrapartum intervention once fetal compromise is suspected</article-title><year>2022</year><access-date>2026-07-11</access-date><publisher-name>Healthcare Safety Investigation Branch</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://www.hssib.org.uk/patient-safety-investigations/delays-to-intrapartum-intervention-once-fetal-compromise-is-suspected/investigation-report/">https://www.hssib.org.uk/patient-safety-investigations/delays-to-intrapartum-intervention-once-fetal-compromise-is-suspected/investigation-report/</ext-link></comment></nlm-citation></ref><ref id="ref51"><label>51</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Carayon</surname><given-names>P</given-names> </name><name name-style="western"><surname>Xie</surname><given-names>A</given-names> </name><name name-style="western"><surname>Kianfar</surname><given-names>S</given-names> </name></person-group><article-title>Human factors and ergonomics as a patient safety practice</article-title><source>BMJ Qual Saf</source><year>2014</year><month>03</month><volume>23</volume><issue>3</issue><fpage>196</fpage><lpage>205</lpage><pub-id pub-id-type="doi">10.1136/bmjqs-2013-001812</pub-id><pub-id pub-id-type="medline">23813211</pub-id></nlm-citation></ref><ref id="ref52"><label>52</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Dlugatch</surname><given-names>R</given-names> </name><name name-style="western"><surname>Georgieva</surname><given-names>A</given-names> </name><name name-style="western"><surname>Kerasidou</surname><given-names>A</given-names> </name></person-group><article-title>AI-driven decision support systems and epistemic reliance: a qualitative study on obstetricians&#x2019; and midwives&#x2019; perspectives on integrating AI-driven CTG into clinical decision making</article-title><source>BMC Med Ethics</source><year>2024</year><volume>25</volume><issue>1</issue><pub-id pub-id-type="doi">10.1186/s12910-023-00990-1</pub-id></nlm-citation></ref><ref id="ref53"><label>53</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Aeberhard</surname><given-names>JL</given-names> </name><name name-style="western"><surname>Radan</surname><given-names>AP</given-names> </name><name name-style="western"><surname>Delgado-Gonzalo</surname><given-names>R</given-names> </name><etal/></person-group><article-title>Artificial intelligence and machine learning in cardiotocography: a scoping review</article-title><source>European Journal of Obstetrics &#x0026; Gynecology and Reproductive Biology</source><year>2023</year><month>02</month><volume>281</volume><fpage>54</fpage><lpage>62</lpage><pub-id pub-id-type="doi">10.1016/j.ejogrb.2022.12.008</pub-id></nlm-citation></ref><ref id="ref54"><label>54</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>McComb</surname><given-names>S</given-names> </name><name name-style="western"><surname>Simpson</surname><given-names>V</given-names> </name></person-group><article-title>The concept of shared mental models in healthcare collaboration</article-title><source>J Adv Nurs</source><year>2014</year><month>07</month><volume>70</volume><issue>7</issue><fpage>1479</fpage><lpage>1488</lpage><pub-id pub-id-type="doi">10.1111/jan.12307</pub-id><pub-id pub-id-type="medline">24237202</pub-id></nlm-citation></ref><ref id="ref55"><label>55</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Wu</surname><given-names>AW</given-names> </name></person-group><article-title>Reaching common ground: the role of shared mental models in patient safety</article-title><source>Journal of Patient Safety and Risk Management</source><year>2018</year><month>10</month><volume>23</volume><issue>5</issue><fpage>183</fpage><lpage>184</lpage><pub-id pub-id-type="doi">10.1177/2516043518805326</pub-id></nlm-citation></ref><ref id="ref56"><label>56</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Khairat</surname><given-names>S</given-names> </name><name name-style="western"><surname>Burke</surname><given-names>G</given-names> </name><name name-style="western"><surname>Archambault</surname><given-names>H</given-names> </name><name name-style="western"><surname>Schwartz</surname><given-names>T</given-names> </name><name name-style="western"><surname>Larson</surname><given-names>J</given-names> </name><name name-style="western"><surname>Ratwani</surname><given-names>RM</given-names> </name></person-group><article-title>Perceived burden of EHRs on physicians at different stages of their career</article-title><source>Appl Clin Inform</source><year>2018</year><month>04</month><volume>9</volume><issue>2</issue><fpage>336</fpage><lpage>347</lpage><pub-id pub-id-type="doi">10.1055/s-0038-1648222</pub-id><pub-id pub-id-type="medline">29768634</pub-id></nlm-citation></ref><ref id="ref57"><label>57</label><nlm-citation citation-type="report"><article-title>NHS resolution annual report and accounts 2024 to 2025</article-title><year>2025</year><access-date>2026-07-11</access-date><publisher-name>NHS Resolution</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://www.gov.uk/government/publications/nhs-resolution-annual-report-and-accounts-2024-to-2025">https://www.gov.uk/government/publications/nhs-resolution-annual-report-and-accounts-2024-to-2025</ext-link></comment></nlm-citation></ref><ref id="ref58"><label>58</label><nlm-citation citation-type="web"><article-title>NHS facing &#x2018;absolutely shocking&#x2019; &#x00A3;27bn bill for maternity failings in England</article-title><source>The Guardian</source><year>2025</year><month>07</month><day>20</day><access-date>2026-07-11</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.theguardian.com/society/2025/jul/20/nhs-facing-absolutely-shocking-27bn-bill-for-maternity-failings-in-england">https://www.theguardian.com/society/2025/jul/20/nhs-facing-absolutely-shocking-27bn-bill-for-maternity-failings-in-england</ext-link></comment></nlm-citation></ref><ref id="ref59"><label>59</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Huo</surname><given-names>W</given-names> </name><name name-style="western"><surname>Yuan</surname><given-names>X</given-names> </name><name name-style="western"><surname>Li</surname><given-names>X</given-names> </name><name name-style="western"><surname>Luo</surname><given-names>W</given-names> </name><name name-style="western"><surname>Xie</surname><given-names>J</given-names> </name><name name-style="western"><surname>Shi</surname><given-names>B</given-names> </name></person-group><article-title>Increasing acceptance of medical AI: the role of medical staff participation in AI development</article-title><source>Int J Med Inform</source><year>2023</year><month>07</month><volume>175</volume><fpage>105073</fpage><pub-id pub-id-type="doi">10.1016/j.ijmedinf.2023.105073</pub-id><pub-id pub-id-type="medline">37119693</pub-id></nlm-citation></ref><ref id="ref60"><label>60</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Longoni</surname><given-names>C</given-names> </name><name name-style="western"><surname>Bonezzi</surname><given-names>A</given-names> </name><name name-style="western"><surname>Morewedge</surname><given-names>CK</given-names> </name></person-group><article-title>Resistance to medical artificial intelligence</article-title><source>J Consum Res</source><year>2019</year><month>12</month><day>1</day><volume>46</volume><issue>4</issue><fpage>629</fpage><lpage>650</lpage><pub-id pub-id-type="doi">10.1093/jcr/ucz013</pub-id></nlm-citation></ref><ref id="ref61"><label>61</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Damschroder</surname><given-names>LJ</given-names> </name><name name-style="western"><surname>Reardon</surname><given-names>CM</given-names> </name><name name-style="western"><surname>Widerquist</surname><given-names>MAO</given-names> </name><name name-style="western"><surname>Lowery</surname><given-names>J</given-names> </name></person-group><article-title>The updated consolidated framework for implementation research based on user feedback</article-title><source>Implementation Sci</source><year>2022</year><volume>17</volume><issue>1</issue><pub-id pub-id-type="doi">10.1186/s13012-022-01245-0</pub-id></nlm-citation></ref><ref id="ref62"><label>62</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Green</surname><given-names>TL</given-names> </name><name name-style="western"><surname>Zapata</surname><given-names>JY</given-names> </name><name name-style="western"><surname>Brown</surname><given-names>HW</given-names> </name><name name-style="western"><surname>Hagiwara</surname><given-names>N</given-names> </name></person-group><article-title>Rethinking bias to achieve maternal health equity: changing organizations, not just individuals</article-title><source>Obstet Gynecol</source><year>2021</year><month>05</month><day>1</day><volume>137</volume><issue>5</issue><fpage>935</fpage><lpage>940</lpage><pub-id pub-id-type="doi">10.1097/AOG.0000000000004363</pub-id><pub-id pub-id-type="medline">33831936</pub-id></nlm-citation></ref><ref id="ref63"><label>63</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Donovan</surname><given-names>T</given-names> </name><name name-style="western"><surname>Abell</surname><given-names>B</given-names> </name><name name-style="western"><surname>Fernando</surname><given-names>M</given-names> </name><name name-style="western"><surname>McPhail</surname><given-names>SM</given-names> </name><name name-style="western"><surname>Carter</surname><given-names>HE</given-names> </name></person-group><article-title>Implementation costs of hospital-based computerised decision support systems: a systematic review</article-title><source>Implementation Sci</source><year>2023</year><volume>18</volume><issue>1</issue><pub-id pub-id-type="doi">10.1186/s13012-023-01261-8</pub-id></nlm-citation></ref><ref id="ref64"><label>64</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Khan</surname><given-names>ZA</given-names> </name><name name-style="western"><surname>Kidholm</surname><given-names>K</given-names> </name><name name-style="western"><surname>Pedersen</surname><given-names>SA</given-names> </name><etal/></person-group><article-title>Developing a program costs checklist of digital health interventions: a scoping review and empirical case study</article-title><source>Pharmacoeconomics</source><year>2024</year><month>06</month><volume>42</volume><issue>6</issue><fpage>663</fpage><lpage>678</lpage><pub-id pub-id-type="doi">10.1007/s40273-024-01366-y</pub-id><pub-id pub-id-type="medline">38530596</pub-id></nlm-citation></ref><ref id="ref65"><label>65</label><nlm-citation citation-type="web"><article-title>What&#x2019;s the real cost of EHR implementation for healthcare providers in 2026?</article-title><source>Sprypt</source><year>2024</year><access-date>2026-07-11</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.sprypt.com/blog/guide-to-the-cost-of-ehr-implementation-for-healthcare-providers">https://www.sprypt.com/blog/guide-to-the-cost-of-ehr-implementation-for-healthcare-providers</ext-link></comment></nlm-citation></ref><ref id="ref66"><label>66</label><nlm-citation citation-type="web"><article-title>Clinical investigations of medical devices &#x2013; guidance for manufacturers</article-title><source>UK Government</source><year>2025</year><access-date>2026-07-11</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.gov.uk/guidance/notify-mhra-about-a-clinical-investigation-for-a-medical-device">https://www.gov.uk/guidance/notify-mhra-about-a-clinical-investigation-for-a-medical-device</ext-link></comment></nlm-citation></ref></ref-list><app-group><supplementary-material id="app1"><label>Multimedia Appendix 1</label><p>Video demonstration of the Fit4Labour tool showing clinical workflow and user interface.</p><media xlink:href="humanfactors_v13i1e87589_app1.docx" xlink:title="DOCX File, 1071 KB"/></supplementary-material></app-group></back></article>