<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JRAT</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Rehabil Assist Technol</journal-id>
      <journal-title>JMIR Rehabilitation and Assistive Technologies</journal-title>
      <issn pub-type="epub">2369-2529</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">v13i1e90442</article-id>
      <article-id pub-id-type="pmid">42995698</article-id>
      <article-id pub-id-type="doi">10.2196/90442</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>AI Scribe in Specialized Rehabilitation: Usability Study of Perceived Usability and Usefulness Among Physicians and Psychologists</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Munce</surname>
            <given-names>Sarah</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Wright</surname>
            <given-names>Donald</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Das</surname>
            <given-names>Sayandeep</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Engan</surname>
            <given-names>Harald Kåre</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution/>
            <institution>Department of Research and Development</institution>
            <institution>Unicare Rehabiliation</institution>
            <addr-line>Fyrstikkalléen 19</addr-line>
            <addr-line>Oslo, Oslo, 0661</addr-line>
            <country>Norway</country>
            <phone>47 99516082</phone>
            <email>harald.kare.engan@unicare.no</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-4393-460X</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Landstad</surname>
            <given-names>Ingeborg</given-names>
          </name>
          <degrees>M.Sc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0001-9014-0036</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Sand</surname>
            <given-names>Kari</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-8391-2990</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Evenshaug</surname>
            <given-names>Ståle</given-names>
          </name>
          <degrees>M.Sc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0003-9282-8226</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Henjum Halsnes</surname>
            <given-names>Einar</given-names>
          </name>
          <degrees>M.Sc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0009-6905-4342</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Department of Research and Development</institution>
        <institution>Unicare Rehabiliation</institution>
        <addr-line>Oslo, Oslo</addr-line>
        <country>Norway</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Department of Research and Development</institution>
        <institution>SINTEF Digital</institution>
        <addr-line>Trondheim, Trøndelag</addr-line>
        <country>Norway</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Harald Kåre Engan <email>harald.kare.engan@unicare.no</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2026</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>6</day>
        <month>11</month>
        <year>2026</year>
      </pub-date>
      <volume>13</volume>
      <elocation-id>e90442</elocation-id>
      <history>
        <date date-type="received">
          <day>28</day>
          <month>12</month>
          <year>2025</year>
        </date>
        <date date-type="rev-request">
          <day>15</day>
          <month>8</month>
          <year>2026</year>
        </date>
        <date date-type="rev-recd">
          <day>29</day>
          <month>9</month>
          <year>2026</year>
        </date>
        <date date-type="accepted">
          <day>5</day>
          <month>10</month>
          <year>2026</year>
        </date>
      </history>
      <copyright-statement>©Harald Kåre Engan, Ingeborg Landstad, Kari Sand, Ståle Evenshaug, Einar Henjum Halsnes. Originally published in JMIR Rehabilitation and Assistive Technology (https://rehab.jmir.org), 06.11.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 (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Rehabilitation and Assistive Technology, is properly cited. The complete bibliographic information, a link to the original publication on https://rehab.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://rehab.jmir.org/2026/1/e90442" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Clinical documentation in specialized, interdisciplinary rehabilitation is often time-consuming and complex and may contribute to clinician burnout and reduced time for patient interaction. AI-based scribes transcribe and summarize clinical notes and may reduce documentation burden; however, their usefulness and usability in specialized rehabilitation remain uninvestigated.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study aimed to assess the use of an ambient AI scribe tool among physicians and psychologists in specialized rehabilitation, focusing on perceived usefulness, usability, note quality, impact on patient interaction, perceptions of time spent on documentation, and documentation-related fatigue.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>Over approximately 4 weeks, physicians and psychologists at 9 specialized rehabilitation centers used an ambient AI scribe during clinical consultations. Usability and user experience were assessed using the System Usability Scale (SUS) and a modified technology acceptance model (TAM). Participants rated an AI-generated note using a modified 8-item Physician Documentation Quality Instrument (PDQI-8) questionnaire to evaluate documentation quality. Additional questions explored perceived impact on patient interaction, documentation-related fatigue, and general attitudes toward AI technology.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>Thirty-one clinicians (18 physicians and 13 psychologists) used the AI scribe over approximately one month and completed evaluation questionnaires. The mean SUS score was 78.3 (SD 10.4), with 86.7% of participants scoring above the usability threshold. Perceived usefulness (PU) and perceived ease of use (PEOU) were relatively high (mean PU score 5.65, SD 1.33; mean PEOU score 5.56, SD 1.17), and 87.1% expressed intention to use the AI scribe in future practice. Most participants (80.6%) agreed that using the AI scribe reduced time spent on documentation, while 66.6% reported a reduced perception of documentation-related fatigue. The quality of AI-generated notes was rated relatively high, with a mean modified PDQI-8 score of 4.3 (SD 0.3) out of 5. Comprehensibility received the highest rating (mean 4.6, SD 0.6), whereas thoroughness received the lowest rating (mean 3.9, SD 1.0) among the note quality variables. Overall, 71.0% of participants expressed some level of agreement that the AI scribe enhanced attentiveness during patient consultations, while a similar proportion (70.9%) agreed that it made active listening easier by reducing distractions associated with note-taking. A few participants reported that some notes were incomplete, lacked biopsychosocial details, and contained inaccuracies.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>This study demonstrated broad acceptance of an AI-based ambient scribe among physicians and psychologists working in specialized rehabilitation. The AI scribe was generally perceived as valuable, easy to use, and clinically relevant. Most participants reported a reduced perceived documentation burden and improved attentiveness during consultations. These findings suggest that clinicians perceived the AI scribe as supporting more focused patient interactions. Some concerns were noted regarding completeness and occasional inaccuracies, highlighting areas for refinement. Future research should explore long-term implementation in routine rehabilitation settings and its effects on workflow, documentation quality, and patient experience.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>eHealth</kwd>
        <kwd>artificial intelligence</kwd>
        <kwd>AI</kwd>
        <kwd>rehabilitation</kwd>
        <kwd>technology</kwd>
        <kwd>usability</kwd>
        <kwd>adoption</kwd>
        <kwd>implementation</kwd>
        <kwd>scribe</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Clinical documentation in electronic health records (EHRs) is essential for ensuring the accuracy and comprehensiveness of clinical information, promoting shared decision-making, and enhancing care coordination [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref3">3</xref>]. In specialized rehabilitation, health care professionals must thoroughly document the patient’s functional status, therapeutic interventions, and progress over time [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref5">5</xref>]. This requires that medical records accurately reflect the interdisciplinary approach to patient care, often incorporating contributions from various health care professionals. At the same time, fulfilling these documentation requirements often places a heavy burden on clinicians [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref7">7</xref>]. For instance, research indicates that many physicians spend several hours outside regular working hours completing EHRs, leading to career dissatisfaction, negative impacts on work-life balance, and disruption of clinician-patient relationships [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref9">9</xref>].</p>
      <p>Manual documentation has been associated with increased cognitive demands and distractions and may contribute to clinician burnout because of the excessive time spent on clinical documentation [<xref ref-type="bibr" rid="ref10">10</xref>]. This burden may adversely affect health care personnel by reducing productivity and contributing to frustration, emotional exhaustion, and potentially compromised patient care [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>]. Patients have expressed concerns that the increase in EHR-based administrative tasks leads physicians to spend more time at digital devices, making visits feel impersonal and routine [<xref ref-type="bibr" rid="ref13">13</xref>]. Recent qualitative research shows that electronic documentation in rehabilitation is perceived as burdensome, limiting time for patient interaction and affecting relational quality [<xref ref-type="bibr" rid="ref5">5</xref>].</p>
      <p>In recent years, advances in AI scribes have offered potential solutions to optimize documentation by reducing the time clinicians spend on manual note-taking, alleviating the administrative burden, and improving the quality and consistency of clinical records [<xref ref-type="bibr" rid="ref14">14</xref>]. AI scribes use advancements in natural language processing (NLP) and machine learning to record, transcribe, and summarize clinical encounters [<xref ref-type="bibr" rid="ref15">15</xref>]. Automated digital scribes can capture conversations between clinicians and patients and generate documentation for inclusion in the medical record. By automating the documentation process, AI scribes may potentially reduce the administrative burden on health care providers, allowing them to dedicate more time to direct patient care [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref16">16</xref>]. This could enhance the patient experience and improve clinical outcomes [<xref ref-type="bibr" rid="ref17">17</xref>]. Recent studies suggest that AI-enhanced medical scribe services can maintain high levels of accuracy and consistency in clinical documentation while minimizing errors associated with manual data entry [<xref ref-type="bibr" rid="ref17">17</xref>]. Furthermore, integrating AI into health care documentation has shown promise in reducing physician burnout by decreasing the time required for manual medical record documentation [<xref ref-type="bibr" rid="ref18">18</xref>]. Digital scribes may enable clinicians to engage more with patients, maintain eye contact during consultations, and avoid diverting attention from the patient to a computer for manual documentation, which may ultimately lead to more patient-centered care [<xref ref-type="bibr" rid="ref19">19</xref>].</p>
      <p>Although these developments are promising, evidence from peer-reviewed studies on the benefits of digital scribe technology in rehabilitation settings remains limited. AI scribes may help health care providers in specialized rehabilitation meet documentation requirements and allocate more time to direct patient interactions. In addition, AI scribes may help standardize clinical documentation and improve information flow across interdisciplinary teams, potentially improving care coordination. Despite the potential of AI in clinical documentation, concerns remain about the quality of AI-generated notes [<xref ref-type="bibr" rid="ref16">16</xref>]. Further research is therefore needed to examine this issue in a rehabilitation setting. To date, no studies have examined clinicians’ experiences with the latest version of AI scribe technology in specialized rehabilitation. Unicare Rehabilitation is among the first health care institutions to pilot an ambient AI scribe in this context.</p>
      <p>The overall aim of this study was to investigate physicians’ and psychologists’ experiences using ambient AI-scribing technology as a clinical documentation assistant in specialized rehabilitation. This aim was addressed through 2 specific objectives: first, to evaluate perceived usefulness (PU), perceived ease of use (PEOU), overall usability, perceived interaction support (PIS), the quality of generated clinical notes, and the impact on documentation-related fatigue; and second, to explore the relationship between AI scribe usability, measured using the System Usability Scale (SUS), and key acceptance factors in the modified technology acceptance model (TAM), providing preliminary insight into the relevance of usability in specialized rehabilitation.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Materials</title>
        <p>This exploratory evaluation assessed clinicians’ perceptions of the usability and usefulness of the AI scribe Noteless (Noteless AS) following 4 weeks of routine clinical use. The study was reported in accordance with relevant recommendations for observational studies [<xref ref-type="bibr" rid="ref20">20</xref>].</p>
      </sec>
      <sec>
        <title>Product Information and Workflow Overview</title>
        <p>The AI scribe evaluated in this study was Noteless, a web-based software application designed to transcribe and summarize medical conversations. The system operates through a series of structured steps to streamline clinical documentation. It uses a transformer-based speech-to-text model, refined to handle medical terminology, to enhance transcription accuracy. The AI scribe was accessible via a web-based app. At the beginning of patient consultations, the clinician initiated the recording session. The device’s voice-recording hardware (Nedis [Nedis BV], model MICCU100BK), in conjunction with the AI scribe app, captured the conversation between the clinician and the patient. Upon completion, the recording was transmitted to the cloud for processing by AI designed to interpret and analyze speech. The AI scribe analyzed the recording and generated a draft derived from the recorded dialogue. For summarization, it used a combination of large language models integrated with a customized prompt structure and supplementary rules [<xref ref-type="bibr" rid="ref21">21</xref>]. During the study period, the evaluated system was Noteless version 2.0. The system was used to transcribe and generate clinical documentation from consultations conducted in Norwegian.</p>
        <p>The platform used a model-agnostic, modular architecture that allowed different commercially available large language models to be used for specific documentation tasks. Noteless was designed as a clinical documentation support tool rather than a clinical decision-support system and was not intended to provide diagnostic, treatment, or other clinical recommendations. Generated notes were copied into the clinician’s EHR system, where they were reviewed, edited as needed, and approved by the clinician before finalization. Clinicians retained full responsibility for the final documentation.</p>
        <p>Audio recordings were processed in real time through Speechmatics (Speechmatics Inc) speech-recognition services hosted on Microsoft Azure infrastructure located in Ireland and Spain and were not retained after transcription. Audio data were deleted immediately once the corresponding text transcript had been generated. Resulting transcripts and AI-generated notes were temporarily stored within the Noteless platform for a maximum of 24 hours in a Microsoft Azure data center located in Norway (Norway East region) to support document generation and clinician review before being securely deleted. AI-based note generation was performed using services hosted on Microsoft Azure infrastructure in Sweden and Google Cloud Platform infrastructure in Belgium. Neither Noteless nor its subprocessors retained patient data following processing or used such data for model training or any other secondary purposes. Privacy and security safeguards included encryption in transit and at rest, access controls based on the principle of least privilege, audit logging, periodic access reviews, contractual data-processing agreements with subprocessors, and automated deletion procedures to ensure removal of transcripts and generated notes after the retention period.</p>
      </sec>
      <sec>
        <title>Setting</title>
        <p>This cohort study was conducted at Unicare’s specialized academic rehabilitation centers in Norway. Unicare Rehabilitation comprises 10 specialized centers offering both inpatient and outpatient services. Many rehabilitation programs in Norway are organized as outpatient programs at hospitals or rehabilitation centers near hospitals and as inpatient programs at rehabilitation centers primarily located in rural areas. The current study was conducted in inpatient rehabilitation centers. Unicare provides specialized interdisciplinary rehabilitation services, including professionals such as physical medicine physicians, psychologists, physiotherapists, nutritionists, and occupational therapists. The rehabilitation centers annually receive approximately 9000 patients across all major diagnostic groups. The study was conducted across all centers from January to February 2025.</p>
      </sec>
      <sec>
        <title>Recruitment and Participants</title>
        <p>Ambient scribe technology was offered to all physicians and psychologists for use during inpatient and outpatient medical appointments, with informed consent obtained from all participants. A convenience sample was used, comprising physicians and psychologists who were invited to use the ambient scribe technology and agreed to participate in the evaluation. Potential participants were recruited through a dual approach: informal recruitment emails to engage interested clinicians and proactive efforts by department leaders to disseminate information about the study across 9 distinct rehabilitation centers. This recruitment strategy successfully identified 31 clinicians, comprising 18 physicians and 13 psychologists, all of whom consented to participate in the pilot program. Patients verbally consented to the use of the ambient scribing tool during clinical encounters; however, the project team did not collect or review any patient information at any point during the study. Participants received no reimbursement for participating.</p>
      </sec>
      <sec>
        <title>Procedure</title>
        <p>Prior to the commencement of the 4-week pilot period, participants attended a 45-minute orientation session via video call, during which the project leader provided information about the study and basic instructions on using the ambient scribe tool. The training session primarily emphasized practical aspects of setting up and configuring the ambient AI scribe technology, including hardware and software components. While the session deliberately limited detailed guidance on usage to allow participants to explore the system’s ease of use independently, it nonetheless introduced key principles for practical and safe application of the technology in clinical practice.</p>
        <p>Participants were instructed to use their microphone to record the encounter and generate summarized documentation that was automatically uploaded to and stored on a secure cloud, accessible on their desktop computer through secure web interfaces for later incorporation and text editing into the EHR. During the initial briefing, participants were also told how to obtain patients’ permission to use the AI medical scribe for in-person or virtual encounters. Throughout the study, participants used ambient scribing for specialized rehabilitation, with continuous technological support from support staff.</p>
      </sec>
      <sec>
        <title>Patient Information Resources</title>
        <p>Informational brochures were developed and distributed to the rehabilitation centers where the ambient AI scribe was implemented. These brochures contained essential information, which participants could summarize verbally during the consent process. Additionally, laminated posters were offered for placement in visible areas within the clinics to inform patients that physicians and psychologists might use AI scribe technology during their consultations.</p>
      </sec>
      <sec>
        <title>Inclusion Criteria</title>
        <p>Licensed physicians and psychologists working at one of the participating rehabilitation centers are currently involved in patient care and are willing to use an AI scribe during medical appointments.</p>
      </sec>
      <sec>
        <title>Exclusion Criteria</title>
        <p>Individuals who had previously used any form of AI-based scribe were not eligible to participate.</p>
      </sec>
      <sec>
        <title>Outcomes</title>
        <sec>
          <title>PU and Usability</title>
          <p>The study used a dual-strategy approach, combining the TAM from Information Systems and the SUS from human-computer interaction [<xref ref-type="bibr" rid="ref22">22</xref>]. Integrating these 2 complementary approaches was intended to provide a comprehensive understanding of both usability and user experience factors, thereby enhancing the evaluation process. In addition, another purpose was to enable a comparison of the measurement tools themselves, offering insights into their respective contributions to assessing technology in this context.</p>
        </sec>
        <sec>
          <title>TAM Methodology</title>
          <p>TAM is one of the most widely used and researched models for predicting the adoption and use of information technology by individuals, with its validity in health research affirmed by numerous studies [<xref ref-type="bibr" rid="ref23">23</xref>]. This model highlights 2 key factors that influence user acceptance of technology: PU and PEOU. PU is defined as “the degree to which a person believes that using a particular system would improve his/her job performance” [<xref ref-type="bibr" rid="ref24">24</xref>], and PEOU is defined as “the degree to which a person believes that using a particular system would be free of effort” [<xref ref-type="bibr" rid="ref24">24</xref>].</p>
          <p>Initially, TAM items elicited likelihood ratings rather than agreement ratings because the model was designed to predict future product use rather than to rate the experience of actual use [<xref ref-type="bibr" rid="ref24">24</xref>]. Since the aim of this study was to evaluate PU and PEOU following actual product experience rather than to predict future use, the TAM was adapted to align with the usability metric for user experience (UMUX) format [<xref ref-type="bibr" rid="ref25">25</xref>]. This modification allowed respondents to express their level of agreement with items that reflect real user experience rather than anticipated usage. The TAM questionnaire used in this study consisted of 12 items: 6 to measure PU and 6 to measure PEOU. In addition, 2 dimensions considered determinants of PU according to the TAM methodology were included, as they are highly relevant to the evaluation of an AI scribe: (1) job relevance (JR), defined as “the degree to which an individual believes that the target system applies to his or her job,” and (2) quality output (QO), defined as “the degree to which an individual believes that the system performs his or her job tasks well.” Additionally, the construct intention to use (IU) was included, defined as “the degree to which an individual intends to use the system.” JR, QO, and IU were each measured with 2 items [<xref ref-type="bibr" rid="ref26">26</xref>]. TAM items were measured on a 7-point Likert scale, from “1=strongly disagree” to “7=strongly agree.” The TAM literature does not define any established cutoff values for interpreting mean scores.</p>
        </sec>
        <sec>
          <title>SUS</title>
          <p>The SUS is among the most used standardized questionnaires for assessing perceived usability [<xref ref-type="bibr" rid="ref27">27</xref>]. SUS is a 10-item questionnaire that includes an equal number of positive and negative statements. Each statement is rated on a scale from 1 (strongly disagree) to 5 (strongly agree), with higher scores indicating better usability. The SUS is a widely used and validated measure of system usability, and extensive normative research offers various methods for interpreting SUS scores, including the Curved Grading Scale (CGS) approach [<xref ref-type="bibr" rid="ref28">28</xref>]. To calculate the SUS score, one is subtracted from each odd-numbered item score, and 5 is subtracted from each even-numbered item score. Then, these adjusted scores are summed and multiplied by 2.5 to obtain the overall SUS score, which ranges from 0 (extremely poor usability) to 100 (excellent usability). Usability was classified into 7 descriptive categories based on the adjective rating scale proposed by Bangor et al [<xref ref-type="bibr" rid="ref3">3</xref>]. The corresponding SUS score ranges were “worst imaginable” (0-12.5), “awful” (12.6-20.3), “poor” (20.4-35.7), “OK” (35.8-50.9), “good” (51.0-71.4), “excellent” (71.5-85.5), and “best imaginable” [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref29">29</xref>].</p>
        </sec>
        <sec>
          <title>Perception of Documentation Fatigue</title>
          <p>Participants were given a question regarding their perception of reduced tiredness following use of the AI scribe: (1) “The use of the AI tool has reduced the experience of fatigue due to decreased documentation work.” Items in the questionnaire were measured on a 7-point Likert scale, from “1=strongly disagree” to “7=strongly agree” (<xref ref-type="table" rid="table1">Table 1</xref>).</p>
          <table-wrap position="float" id="table1">
            <label>Table 1</label>
            <caption>
              <p>Participant characteristics.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="250"/>
              <col width="250"/>
              <col width="250"/>
              <col width="250"/>
              <thead>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>All (n=31)</td>
                  <td>Physicians (n=18)</td>
                  <td>Psychologists (n=13)</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Age (years), mean (range)</td>
                  <td>47.5 (28-75)</td>
                  <td>55.4 (33-75)</td>
                  <td>37.9 (28-56)</td>
                </tr>
                <tr valign="top">
                  <td>Sex (male), n (%)</td>
                  <td>12 (39)</td>
                  <td>10 (56)</td>
                  <td>2 (15)</td>
                </tr>
                <tr valign="top">
                  <td>University education, n (%)</td>
                  <td>31 (100)</td>
                  <td>18 (100)</td>
                  <td>13 (100)</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
        </sec>
        <sec>
          <title>Perceived Benefits and Challenges of Using the AI Scribe</title>
          <p>Participants were asked to provide free-text responses to two open-ended questions: (1) Did you experience any benefits from using the AI tool in your work? If so, what were they? and (2) Were there any challenges or difficulties you encountered while using the AI tool in your work? If so, what were they?</p>
        </sec>
        <sec>
          <title>Perceived Impact on Clinician-Patient Interaction</title>
          <p>A structured questionnaire, primarily self-developed, with some questions informed by Duggan et al [<xref ref-type="bibr" rid="ref30">30</xref>], was used to gather data on various aspects of patient interactions. The questions addressed the following dimensions: perceived reduction in time spent on documentation, maintaining high-quality patient conversations, ability to give undivided attention to patients, focus on nonverbal cues, ease of active listening, overall interaction effectiveness, and understanding of patient needs and concerns. Items were measured on a 7-point Likert scale, from “1=strongly disagree” to “7=strongly agree” (<xref rid="figure1" ref-type="fig">Figure 1</xref>).</p>
          <fig id="figure1" position="float">
            <label>Figure 1</label>
            <caption>
              <p>Distribution of responses to 8 statements assessing the perceived usefulness of the AI scribe in relation to time consumption, patient interaction, and perceived documentation fatigue. Bars represent the percentage of respondents in each Likert category, with the percentages displayed within the segments.</p>
            </caption>
            <graphic xlink:href="rehab_v13i1e90442_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <p>A composite score, referred to as PIS, was created from 6 study-specific items developed for this exploratory study to capture different aspects of how the AI scribe was perceived to influence clinician-patient interaction. The composite score was used as an exploratory summary measure and to facilitate correlation analyses with factors from the TAM framework. This approach is widely used when multiple items reflect different facets of the same underlying concept [<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref32">32</xref>]. PIS was designed to capture participants’ overall experience of interaction quality when using the AI scribe and should be regarded as a study-specific exploratory measure rather than a validated scale. Higher scores indicate stronger perceived support for interaction. The PIS score was calculated as the mean of the 6 items. The 6 items are provided in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>.</p>
        </sec>
        <sec>
          <title>General Attitude Toward AI Technology</title>
          <p>Information regarding participants’ general attitude toward AI technology was collected using the AI Attitude Scale (AIAS) [<xref ref-type="bibr" rid="ref33">33</xref>]. The AIAS is a concise self-report instrument designed to evaluate public perceptions of AI technology. Items were measured on a 10-point Likert scale, from “1=not at all” to “10=completely agree.”</p>
        </sec>
        <sec>
          <title>Quality of Notes</title>
          <p>The primary outcome was clinician-rated note quality, assessed using a modified 8-item version of the 9-item Physician Documentation Quality Instrument (PDQI-9) that differed from the original validated instrument by removal of one item and modification of another item. The PDQI-9 has been validated as a reliable tool for evaluating the quality of progress notes and discharge summaries. This tool assesses note quality in 9 domains on a 9-item scale with responses on a 5-point Likert scale ranging from 1 (not at all) to 5 (extremely). The original items are: up-to-date, accurate, thorough, useful, organized, comprehensible, succinct, synthesized, and internally consistent. As in Tierney et al [<xref ref-type="bibr" rid="ref34">34</xref>], we excluded “up-to-date” because it was deemed not relevant. In addition, we changed the definition of the domain “synthesized” from “reflects the author’s understanding of the patient’s status and ability to develop a plan of care” to “The note reflects my understanding of the patient’s status as it was presented during the consultation.” This change was made because, in the context of this study, the author was the AI scribe itself. Thus, the total score for the modified 8-item Physician Documentation Quality Instrument (mPDQI-8) could range from 8 (worst possible note quality) to 40 (best possible quality). Participants were instructed to rate an AI-generated admission note as presented by the AI scribe. This rating was conducted during the final week of the study.</p>
        </sec>
      </sec>
      <sec>
        <title>Data Collection Method</title>
        <p>The study used a Microsoft Forms survey to assess PU, PEOU, JR, QO, IU, SUS, patient interaction, perceived documentation fatigue, evaluation questions, and AIAS after the 4-week test period. Participants were instructed to complete a paper version of the modified PDQI-8 to evaluate notes generated by the AI scribe after patient consultations and then return them to the project leader.</p>
      </sec>
      <sec>
        <title>Analysis</title>
        <p>Descriptive statistics were calculated for all variables, including sociodemographic characteristics and scores from the TAM, SUS, AIAS, and custom items related to patient interaction. Group comparisons by profession were conducted using independent-samples Student <italic>t</italic> tests or Mann-Whitney U tests. Pearson correlation coefficients were computed to assess associations between constructs. Following the approach described by Venkatesh and Bala [<xref ref-type="bibr" rid="ref35">35</xref>], mean item scores were calculated for each instrument. Construct-level scores were then derived by computing the mean of item means, which were used in subsequent statistical analyses. Given the exploratory nature of the study and the modest sample size, no adjustment for multiple testing was performed. Correlation analyses and subgroup comparisons were therefore interpreted as exploratory and hypothesis-generating. To evaluate the internal consistency and dimensionality of the PIS composite variable, reliability and factor analyses were performed. Internal consistency was assessed using Cronbach alpha, and item quality was examined through corrected item-total correlations and interitem correlations. An exploratory factor analysis (EFA) was conducted to assess the underlying structure of the PIS items, including evaluation of sampling adequacy (Kaiser-Meyer-Olkin [KMO]) and the Bartlett test of sphericity. The PIS score was calculated as the mean of the 6 individual items. Results were considered statistically significant at <italic>P</italic>&#60;.05. Data were analyzed using IBM SPSS Statistics.</p>
      </sec>
      <sec>
        <title>Qualitative Analysis of Free-Text Responses</title>
        <p>The free-text responses were analyzed by means of qualitative content analysis combining deductive and inductive approaches. The deductive component was based on the 2 open-ended evaluation questions regarding perceived advantages and disadvantages associated with the AI scribe. In the first stage of the analysis, the responses to these 2 questions were analyzed separately. Initially, one researcher (IL) gained an overall understanding of the topics addressed and sorted the responses into preliminary codes for each question. This coding structure was reviewed and discussed by 3 researchers (HKE, IL, and KS), who jointly refined the codes into a final codebook. The names of the codes were based on participants’ own wording.</p>
        <p>In the next step, the entire dataset was coded. Codes were compared in terms of similarities and differences in content and grouped into preliminary code groups. Through several rounds of discussion and revision among 4 researchers, the code groups were abstracted into categories and subtopics (<xref ref-type="table" rid="table2">Table 2</xref>). The categories represent broader areas of participants’ experiences, while the subtopics describe specific aspects within these areas. The coding process and the development of categories and subtopics were inductive.</p>
        <p>During the process of developing categories, the research team merged responses from the 2 open-ended questions into a single dataset since the analysis revealed that the participants described both advantages and disadvantages within the same category. For example, in the category of quality of clinical documentation, it was identified as an advantage that the AI scribe improved summaries and captured clinically relevant information and as a disadvantage that the tool occasionally drew incorrect conclusions or generated text that required manual revision. The predefined dimensions of advantages and disadvantages were retained by including a separate column in <xref ref-type="table" rid="table2">Table 2</xref> (inspired by Duggan et al [<xref ref-type="bibr" rid="ref30">30</xref>]). The organization of codes, the development of categories and subthemes, and the selection of illustrative quotations were discussed and refined by all 4 members of the research team. Any differences in interpretation were resolved through discussion until consensus was reached. The study did not include a member-checking procedure.</p>
        <p>The originally Norwegian free-text responses were translated into English at the final stage of the analysis. An AI tool was prompted to translate the responses into language resembling the style used by health care professionals. All translations were subsequently reviewed and, where necessary, revised by 3 researchers. The analysis team consisted of 4 researchers with experience in specialized rehabilitation, technology implementation, health services research, and qualitative and quantitative research methods.</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Key themes from qualitative comments.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="250"/>
            <col width="720"/>
            <thead>
              <tr valign="top">
                <td colspan="2">Category and subtopic</td>
                <td>Quotes (+ indicates advantages; – indicates disadvantages)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="3">
                  <bold>Workload related to documentation task</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Stress and fatigue</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>(+) “Less time spent on documentation – reduced fatigue” (K2)</p>
                    </list-item>
                    <list-item>
                      <p>(+) “Time-saving, reduces stress” (K19)</p>
                    </list-item>
                    <list-item>
                      <p>(+) “Easier to go back and write/complete notes later the same day. Noticeably less stress during the workday.” (K22)</p>
                    </list-item>
                    <list-item>
                      <p>(+) “Gives me more time to prepare between sessions” (K29)</p>
                    </list-item>
                    <list-item>
                      <p>(+) “Good summaries of the conversation drastically reduce the time and energy spent on documentation.” (K4)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Documentation burden</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>(+) “Because a note was already generated, it was much easier for me to finalize the note right after a session. The threshold for starting documentation was lower since the task felt smaller and already started, which meant I had less backlog.” (K3)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Time spent</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Initial draft/preliminary note<break/>  <break/>  </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>(+) “Repeats all findings during the examination and explains more to us along the way. Provides a good starting point for documentation if there isn’t time to finish writing between sessions.” (K20)</p>
                    </list-item>
                    <list-item>
                      <p>(+) “Captured the main essence of the conversation, which was transcribed and could be used with only minor edits.” (K11)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Quality of clinical documentation</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Summary</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>(+) “Good summary and structure in the notes” (K22)</p>
                    </list-item>
                    <list-item>
                      <p>(+) “More time, more complete notes, better note structure” (K25)</p>
                    </list-item>
                    <list-item>
                      <p>(+) “It summarized longer conversations just fine. Provided a quick starting point for the journal entry.” (K15)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Captures more information</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>(+) “It could sometimes pick up things that I didn’t manage to note during the consultation, which was valuable when transcribing the clinical examination.” (K9)</p>
                    </list-item>
                    <list-item>
                      <p>(+) “Reduced risk of missing something important the patient says during the conversation” (K5)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Generates suggestions for follow-up interventions</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>(+) “Good summaries of relevant topics in the consultation, along with useful suggestions for the assessment section of the note.” (K10)</p>
                    </list-item>
                    <list-item>
                      <p>(+) “Helpful that AI can assist in generating follow-up interventions after the summary and occasionally provide additional advice.” (K25)</p>
                    </list-item>
                    <list-item>
                      <p>(+) “It did a good job with simple assessments as suicide risk evaluation, and it was helpful for gathering background information/anamnesis.” (K32)</p>
                    </list-item>
                    <list-item>
                      <p>(+) “Suggestions for referrals are useful.” (K4)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Generates its own clinical evaluations</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>(–) “It sometimes picked up that the patient was using medications that hadn’t been mentioned at all during the session.” (K32)</p>
                    </list-item>
                    <list-item>
                      <p>(–) “It also added a bit too many interpretations, which means things can easily end up in the note that you don’t fully stand behind if you’re not careful when reviewing.” (K15)</p>
                    </list-item>
                    <list-item>
                      <p>(–) “I’ve also noticed that it occasionally provides incorrect information, which makes it hard to fully trust the tool. The program’s recommendations for next steps are often not very useful for my practice.” (K9)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Selects information</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>(+) “Being able to talk with the patient calmly and then get a transcript of the entire conversation, excluding small talk, is a big advantage.” (K17)</p>
                    </list-item>
                    <list-item>
                      <p>(–) “It filters out parts of the conversation about upbringing, conflicts, etc., which can be important to include.” (K18)</p>
                    </list-item>
                    <list-item>
                      <p>(–) “It doesn’t write exactly the way I want, and not everything I’d like to include makes it into the note.” (K11)</p>
                    </list-item>
                    <list-item>
                      <p>(–) “There’s a need for a template, especially to include biopsychosocial context in the note structure and in the summary/assessment section. I feel the wording lacks some holistic perspective.” (K19)</p>
                    </list-item>
                    <list-item>
                      <p>(–) “The software is very selective in? What it listens to, leaving out large parts of information that I find relevant, especially during longer conversations.” (K9)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Proofreading/editing</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>(–) “Overall, it took longer to edit the AI-generated note than to write my own notes, and my notes had higher quality and greater relevance to the patient’s course of treatment.” (K32)</p>
                    </list-item>
                    <list-item>
                      <p>(–) “Small errors can slip in and need to be caught during editing/proofreading.” (K23)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Quality of patient consultation</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Maintains focus on the patient</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>(+) “I could focus on history-taking and the clinical examination.” (K8)</p>
                    </list-item>
                    <list-item>
                      <p>(+) “I was more focused on the conversation with the patient and wrote a good summary at the end.” (K5)</p>
                    </list-item>
                    <list-item>
                      <p>(+) “Able to focus on the conversation without having to take too many notes along the way.” (K29)</p>
                    </list-item>
                    <list-item>
                      <p>(+) “Being able to talk with the patient calmly and then get a transcript of the entire conversation, excluding small talk, is a big advantage.” (K17)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Patient can access the note immediately after the consultation</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>(+) “Reading through the AI note together with the patient helps create a neutral summary of the session and invites the patient to correct or share an alternative perspective without feeling contradicted.” (K4)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Sensitive topics</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>(–) “I feel the recording limits the ability to talk about difficult topics.” (K12)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Role of the Vendor</title>
        <p>Noteless provided access to the AI scribe software free of charge during the study period and assisted with user registration in the system. The company provided general information about the technology but did not provide training to participants. Noteless had no role in the study design, data collection, data analysis, interpretation of results, manuscript preparation, or the decision to submit the manuscript for publication.</p>
      </sec>
      <sec>
        <title>Ethical Considerations</title>
        <p>The study was conducted in accordance with the Norwegian Research Ethics Act, the National Guidelines for Research Ethics, and the Declaration of Helsinki. Approval from a Regional Committee for Medical and Health Research Ethics (REK) was not required under Norwegian regulations. Unicare, as the data controller, was responsible for ensuring a lawful basis for processing personal data in accordance with the General Data Protection Regulation (GDPR). All participants provided informed consent prior to participation, and the processing of personal data was based on consent in accordance with Article 6(1)(a) and Article 9(2)(a) of the GDPR. Participation was voluntary, and participants were informed that participation or non-participation would have no consequences for their employment. All collected data were de-identified and stored securely, and only authorized members of the research team had access to the data. The authors declare no conflicts of interest.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Sample Characteristics</title>
        <p>A total of 33 physicians and psychologists attended the information meeting and were invited to participate in the study. One physician declined participation, and another did not complete the evaluation questionnaires. The study sample consisted of 31 participants: 18 physicians and 13 psychologists. All participants used the AI scribe for 4 weeks and completed the evaluation questionnaires. Among the physicians, 8 were women, and 10 were men, with a mean age of 55.4 years (SD 12.5). The psychologist group included 11 women and 2 men, with a mean age of 38.3 years (SD 9.0). Among physicians, the mean number of years since graduation was 16.0 (SD 13.8), while among psychologists it was 9.3 years (SD 7.0). <xref ref-type="table" rid="table1">Table 1</xref> presents the demographic information of the included participants.</p>
      </sec>
      <sec>
        <title>TAM Constructs, Usability, Attitudes to AI Technology, and Patient Interaction Support</title>
        <p>All 31 participants completed the questionnaires, although data were missing for 1 participant on the modified PDQI-8 and SUS. The most relevant and statistically meaningful correlations are reported below, along with other observed results. <xref ref-type="table" rid="table3">Table 3</xref> shows the correlations between TAM factors, SUS, AIAS, PIS, and categorical variables.</p>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Pearson correlations between TAM<sup>a</sup> factors, SUS<sup>b</sup>, AIAS<sup>c</sup>, PIS<sup>d</sup>, and categorical variables.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="100"/>
            <col width="100"/>
            <col width="100"/>
            <col width="100"/>
            <col width="100"/>
            <col width="100"/>
            <col width="100"/>
            <col width="100"/>
            <col width="100"/>
            <col width="100"/>
            <thead>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>PU<sup>e</sup></td>
                <td>PEOU<sup>f</sup></td>
                <td>SUS</td>
                <td>BI<sup>g</sup></td>
                <td>JR<sup>h</sup></td>
                <td>QO<sup>i</sup></td>
                <td>PIS</td>
                <td>AIAS</td>
                <td>Age</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>PU, <italic>r</italic> (<italic>P</italic> value)</td>
                <td>1</td>
                <td>0.612 (.001)</td>
                <td>0.433 (.017)</td>
                <td>0.585 (&#60;.001)</td>
                <td>0.731 (.001)</td>
                <td>0.843 (.001)</td>
                <td>0.778 (.001)</td>
                <td>0.541 (.002)</td>
                <td>0.168 (.37)</td>
              </tr>
              <tr valign="top">
                <td>PEOU, <italic>r</italic> (<italic>P</italic> value)</td>
                <td>0.612 (.001)</td>
                <td>1</td>
                <td>0.794 (.001)</td>
                <td>0.505 (.004)</td>
                <td>0.332 (.07)</td>
                <td>0.652 (&#60;.001)</td>
                <td>0.519 (.003)</td>
                <td>0.389 (.03)</td>
                <td>0.231 (.20)</td>
              </tr>
              <tr valign="top">
                <td>SUS, <italic>r</italic> (<italic>P</italic> value)</td>
                <td>0.433 (.017)</td>
                <td>0.794 (.001)</td>
                <td>1</td>
                <td>0.601 (.001)</td>
                <td>0.296 (.11)</td>
                <td>0.486 (.006)</td>
                <td>0.413 (.02)</td>
                <td>0.355 (.054)</td>
                <td>–0.023 (.90)</td>
              </tr>
              <tr valign="top">
                <td>BI, <italic>r</italic> (<italic>P</italic> value)</td>
                <td>0.585 (&#60;.001)</td>
                <td>0.505 (.004)</td>
                <td>0.601 (.001)</td>
                <td>1</td>
                <td>0.766 (.001)</td>
                <td>0.490 (.005)</td>
                <td>0.481 (.006)</td>
                <td>0.718 (.001)</td>
                <td>0.021 (.91)</td>
              </tr>
              <tr valign="top">
                <td>JR, <italic>r</italic> (<italic>P</italic> value)</td>
                <td>0.731 (.001)</td>
                <td>0.332 (.07)</td>
                <td>0.296 (.11)</td>
                <td>0.766 (.001)</td>
                <td>1</td>
                <td>0.552 (.001)</td>
                <td>0.560 (.001)</td>
                <td>0.651 (.001)</td>
                <td>0.091 (.63)</td>
              </tr>
              <tr valign="top">
                <td>QO, <italic>r</italic> (<italic>P</italic> value)</td>
                <td>0.843 (.001)</td>
                <td>0.652 (&#60;.001)</td>
                <td>0.486 (.006)</td>
                <td>0.490 (.005)</td>
                <td>0.552 (.001)</td>
                <td>1</td>
                <td>0.832 (.001)</td>
                <td>0.411 (.02)</td>
                <td>0.205 (.27)</td>
              </tr>
              <tr valign="top">
                <td>PIS, <italic>r</italic> (<italic>P</italic> value)</td>
                <td>0.778 (.001)</td>
                <td>0.519 (.003)</td>
                <td>0.413 (.02)</td>
                <td>0.481 (.006)</td>
                <td>0.560 (.001)</td>
                <td>0.832 (.001)</td>
                <td>1</td>
                <td>0.466 (.008)</td>
                <td>0.293 (.11)</td>
              </tr>
              <tr valign="top">
                <td>AIAS, <italic>r</italic> (<italic>P</italic> value)</td>
                <td>0.541 (.002)</td>
                <td>0.389 (.03)</td>
                <td>0.355 (.054)</td>
                <td>0.718 (.001)</td>
                <td>0.651 (.001)</td>
                <td>0.411 (.02)</td>
                <td>0.466 (.008)</td>
                <td>1</td>
                <td>–0.011 (.95)</td>
              </tr>
              <tr valign="top">
                <td>Age, <italic>r</italic> (<italic>P</italic> value)</td>
                <td>0.168 (.37)</td>
                <td>0.231 (.20)</td>
                <td>–0.023 (.90)</td>
                <td>0.021 (.91)</td>
                <td>0.091 (.63)</td>
                <td>0.205 (.27)</td>
                <td>0.293 (.11)</td>
                <td>–0.011 (.95)</td>
                <td>1</td>
              </tr>
              <tr valign="top">
                <td>Profession, <italic>r</italic> (<italic>P</italic> value)</td>
                <td>–0.046 (.81)</td>
                <td>0.019 (.92)</td>
                <td>0.068 (.72)</td>
                <td>–0.008 (.97)</td>
                <td>–0.112 (.55)</td>
                <td>–0.108 (.56)</td>
                <td>–0.233 (.21)</td>
                <td>0.041 (.82)</td>
                <td>0.631 (.001)</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table3fn1">
              <p><sup>a</sup>TAM: technology acceptance model.</p>
            </fn>
            <fn id="table3fn2">
              <p><sup>b</sup>SUS: System Usability Scale.</p>
            </fn>
            <fn id="table3fn3">
              <p><sup>c</sup>AIAS: AI attitude scale.</p>
            </fn>
            <fn id="table3fn4">
              <p><sup>d</sup>PIS: perceived interaction support.</p>
            </fn>
            <fn id="table3fn5">
              <p><sup>e</sup>PU: perceived usefulness.</p>
            </fn>
            <fn id="table3fn6">
              <p><sup>f</sup>PEOU: perceived ease of use.</p>
            </fn>
            <fn id="table3fn7">
              <p><sup>g</sup>BI: behavioral intention.</p>
            </fn>
            <fn id="table3fn8">
              <p><sup>h</sup>JR: job relevance.</p>
            </fn>
            <fn id="table3fn9">
              <p><sup>i</sup>QO: quality output.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <sec>
          <title>PU</title>
          <p>Twenty-two of 31 participants (71.0%) agreed or strongly agreed that the AI scribe was useful, choosing either “agree” or “strongly agree” on the Likert scale. The mean PU score across all participants was 5.65 (SD 1.33), with physicians scoring 5.71 (SD 1.15) and psychologists 5.59 (SD 1.56). There was no statistically significant difference between groups (<italic>P</italic>=.81; Cohen <italic>d</italic>=0.09; 95% CI –0.62 to 0.80). Participants most often strongly agreed with the item “I find the system useful in my job” (51.6%), followed by “Using the AI scribe in my job enables me to accomplish tasks more quickly” (45.2%; <xref ref-type="table" rid="table4">Table 4</xref>). PU was positively correlated with. No significant correlation was found between PU and age or profession (<xref ref-type="table" rid="table3">Table 3</xref>).</p>
          <table-wrap position="float" id="table4">
            <label>Table 4</label>
            <caption>
              <p>Descriptive statistics for perceived usefulness, perceived ease-of-use, job relevance, intention to use, and quality output<sup>a</sup>.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="30"/>
              <col width="240"/>
              <col width="0"/>
              <col width="130"/>
              <col width="0"/>
              <col width="80"/>
              <col width="0"/>
              <col width="90"/>
              <col width="0"/>
              <col width="80"/>
              <col width="0"/>
              <col width="0"/>
              <col width="90"/>
              <col width="0"/>
              <col width="80"/>
              <col width="0"/>
              <col width="90"/>
              <col width="0"/>
              <col width="0"/>
              <col width="90"/>
              <thead>
                <tr valign="top">
                  <td colspan="3">TAM<sup>b</sup> statements</td>
                  <td colspan="9">Rating</td>
                  <td colspan="7">Scale</td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr valign="top">
                  <td colspan="3">
                    <break/>
                  </td>
                  <td colspan="2">Strongly disagree</td>
                  <td colspan="2">Disagree</td>
                  <td colspan="2">Slightly disagree</td>
                  <td colspan="2">Neither</td>
                  <td colspan="3">Slightly agree</td>
                  <td colspan="2">Agree</td>
                  <td colspan="2">Strongly agree</td>
                  <td colspan="2">Mean (SD)</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td colspan="20">
                    <bold>PU<sup>c</sup> Items</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Using the AI scribe in my job enables me to accomplish tasks more quickly </td>
                  <td colspan="2">1 (3.2)</td>
                  <td colspan="2">0 (0.0)</td>
                  <td colspan="2">1 (3.2)</td>
                  <td colspan="2">2 (6.5)</td>
                  <td colspan="3">4 (12.9)</td>
                  <td colspan="2">9 (29.0)</td>
                  <td colspan="2">
                    <italic>14 (45.2)</italic>
                    <sup>d</sup>
                  </td>
                  <td colspan="3">5.94 (1.41)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Using the AI scribe improves my job performance </td>
                  <td colspan="2">1 (3.2)</td>
                  <td colspan="2">1 (3.2)</td>
                  <td colspan="2">0 (0.0)</td>
                  <td colspan="2">3 (9.7)</td>
                  <td colspan="3">
                    <italic>11 (35.5)</italic>
                  </td>
                  <td colspan="2">8 (25.8)</td>
                  <td colspan="2">7 (22.6)</td>
                  <td colspan="3">5.39 (1.41)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Using the AI scribe in my job increases my productivity </td>
                  <td colspan="2">1 (3.2)</td>
                  <td colspan="2">1 (3.2)</td>
                  <td colspan="2">2 (6.5)</td>
                  <td colspan="2">3 (9.7)</td>
                  <td colspan="3">5 (16.1)</td>
                  <td colspan="2">
                    <italic>12 (38.7)</italic>
                  </td>
                  <td colspan="2">7 (22.6)</td>
                  <td colspan="3">5.39 (1.54)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Using the system enhances my effectiveness on the job </td>
                  <td colspan="2">1 (3.2)</td>
                  <td colspan="2">1 (3.2)</td>
                  <td colspan="2">2 (6.5)</td>
                  <td colspan="2">2 (6.5)</td>
                  <td colspan="3">4 (12.9)</td>
                  <td colspan="2">
                    <italic>13 (41.9)</italic>
                  </td>
                  <td colspan="2">8 (25.8)</td>
                  <td colspan="3">5.52 (1.55)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Using the system makes it easier to do my job </td>
                  <td colspan="2">0 (0.0)</td>
                  <td colspan="2">1 (3.2)</td>
                  <td colspan="2">0 (0.0)</td>
                  <td colspan="2">5 (16.1)</td>
                  <td colspan="3">5 (16.1)</td>
                  <td colspan="2">
                    <italic>12 (38.7)</italic>
                  </td>
                  <td colspan="2">8 (25.8)</td>
                  <td colspan="3">5.65 (1.23)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>I find the system useful in my job</td>
                  <td colspan="2">0 (0.0)</td>
                  <td colspan="2">1 (3.2)</td>
                  <td colspan="2">0 (0.0)</td>
                  <td colspan="2">4 (12.9)</td>
                  <td colspan="3">4 (12.9)</td>
                  <td colspan="2">6 (19.4)</td>
                  <td colspan="2">
                    <italic>16 (51.6)</italic>
                  </td>
                  <td colspan="3">6.00 (1.32)</td>
                </tr>
                <tr valign="top">
                  <td colspan="20">
                    <bold>PEOU<sup>e</sup> Items</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Learning to operate the AI scribe was easy for me </td>
                  <td colspan="2">0 (0.0)</td>
                  <td colspan="2">1 (3.2)</td>
                  <td colspan="2">1 (3.2)</td>
                  <td colspan="2">2 (6.5)</td>
                  <td colspan="3">4 (12.9)</td>
                  <td colspan="2">6 (19.4)</td>
                  <td colspan="2">
                    <italic>17 (54.8)</italic>
                  </td>
                  <td colspan="3">6.06 (1.34)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>I found it easy to get the AI scribe to do what I want it to do </td>
                  <td colspan="2">1 (3.2)</td>
                  <td colspan="2">1 (3.2)</td>
                  <td colspan="2">4 (12.9)</td>
                  <td colspan="2">4 (12.9)</td>
                  <td colspan="3">
                    <italic>9 (29.0)</italic>
                  </td>
                  <td colspan="2">
                    <italic>9 (29.0)</italic>
                  </td>
                  <td colspan="2">3 (9.7)</td>
                  <td colspan="3">4.87 (1.48)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>My interaction with the AI scribe was clear and understandable </td>
                  <td colspan="2">0 (0.0)</td>
                  <td colspan="2">1 (3.2)</td>
                  <td colspan="2">2 (6.5)</td>
                  <td colspan="2">3 (9.7)</td>
                  <td colspan="3">4 (12.9)</td>
                  <td colspan="2">7 (22.6)</td>
                  <td colspan="2">
                    <italic>14 (45.2)</italic>
                  </td>
                  <td colspan="3">5.81 (1.45)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>I find the AI scribe to be flexible to interact with </td>
                  <td colspan="2">0 (0.0)</td>
                  <td colspan="2">0 (0.0)</td>
                  <td colspan="2">4 (12.9)</td>
                  <td colspan="2">5 (16.1)</td>
                  <td colspan="3">6 (19.4)</td>
                  <td colspan="2">
                    <italic>8 (25.8)</italic>
                  </td>
                  <td colspan="2">
                    <italic>8 (25.8)</italic>
                  </td>
                  <td colspan="3">5.35 (1.38)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>It was easy for me to become skillful at using the AI scribe </td>
                  <td colspan="2">1 (3.2)</td>
                  <td colspan="2">1 (3.2)</td>
                  <td colspan="2">1 (3.2)</td>
                  <td colspan="2">4 (12.9)</td>
                  <td colspan="3">
                    <italic>10 (32.3)</italic>
                  </td>
                  <td colspan="2">9 (29.0)</td>
                  <td colspan="2">5 (16.1)</td>
                  <td colspan="3">5.19 (1.42)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>I find the AI scribe easy to use </td>
                  <td colspan="2">0 (0.0)</td>
                  <td colspan="2">0 (0.0)</td>
                  <td colspan="2">2 (6.5)</td>
                  <td colspan="2">0 (0.0)</td>
                  <td colspan="3">5 (16.1)</td>
                  <td colspan="2">9 (29.0)</td>
                  <td colspan="2">
                    <italic>15 (48.4)</italic>
                  </td>
                  <td colspan="3">6.13 (1.12)</td>
                </tr>
                <tr valign="top">
                  <td colspan="20">
                    <bold>Behavioral intention/intention to use</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Assuming I have access to the AI scribe, I intend to use it</td>
                  <td colspan="2">0 (0.0)</td>
                  <td colspan="2">0 (0.0)</td>
                  <td colspan="2">3 (9.7)</td>
                  <td colspan="2">0 (0.0)</td>
                  <td colspan="3">1 (3.2)</td>
                  <td colspan="2">5 (16.1)</td>
                  <td colspan="2">
                    <italic>22 (71.0)</italic>
                  </td>
                  <td colspan="3">6.39 (1.23)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Given that I have access to the AI scribe, I predict that I would use it.</td>
                  <td colspan="2">0 (0.0)</td>
                  <td colspan="2">1 (3.2)</td>
                  <td colspan="2">1 (3.2)</td>
                  <td colspan="2">1 (3.2)</td>
                  <td colspan="3">1 (3.2)</td>
                  <td colspan="2">4 (12.9)</td>
                  <td colspan="2">
                    <italic>23 (74.2)</italic>
                  </td>
                  <td colspan="3">6.42 (1.26)</td>
                </tr>
                <tr valign="top">
                  <td colspan="20">
                    <bold>Job relevance</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>In my job, usage of the AI scribe is important</td>
                  <td colspan="2">1 (3.2)</td>
                  <td colspan="2">0 (0.0)</td>
                  <td colspan="2">2 (6.5)</td>
                  <td colspan="2">6 (19.4)</td>
                  <td colspan="3">9 (29.0)</td>
                  <td colspan="2">3 (9.7)</td>
                  <td colspan="2">
                    <italic>10 (32.3)</italic>
                  </td>
                  <td colspan="3">5.29 (1.53)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>In my job, usage of the AI scribe is relevant</td>
                  <td colspan="2">1 (3.2)</td>
                  <td colspan="2">0 (0.0)</td>
                  <td colspan="2">0 (0.0)</td>
                  <td colspan="2">1 (3.2)</td>
                  <td colspan="3">10 (32.3)</td>
                  <td colspan="2">5 (16.1)</td>
                  <td colspan="2">
                    <italic>14 (45.2)</italic>
                  </td>
                  <td colspan="3">5.90 (1.33)</td>
                </tr>
                <tr valign="top">
                  <td colspan="20">
                    <bold>Output quality</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>The quality of the output I get from the AI scribe is high</td>
                  <td colspan="2">0 (0.0)</td>
                  <td colspan="2">2 (6.5)</td>
                  <td colspan="2">3 (9.7)</td>
                  <td colspan="2">4 (12.9)</td>
                  <td colspan="3">8 (25.8)</td>
                  <td colspan="2">
                    <italic>8 (25.8)</italic>
                  </td>
                  <td colspan="2">6 (19.4)</td>
                  <td colspan="3">5.13 (1.48)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>I have no problem with the quality of the AI scribe`s output</td>
                  <td colspan="2">2 (6.7)</td>
                  <td colspan="2">2 (6.7)</td>
                  <td colspan="2">3 (10.0)</td>
                  <td colspan="2">5 (16.7)</td>
                  <td colspan="3">7 (23.3)</td>
                  <td colspan="2">
                    <italic>8 (26.7)</italic>
                  </td>
                  <td colspan="2">3 (10.0)</td>
                  <td colspan="3">4.63 (1.69)</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table4fn1">
                <p><sup>a</sup>Absolute number and percentage of participants in agreement with the statements.</p>
              </fn>
              <fn id="table4fn2">
                <p><sup>b</sup>TAM: technology acceptance model</p>
              </fn>
              <fn id="table4fn3">
                <p><sup>c</sup>PU: perceived usefulness.</p>
              </fn>
              <fn id="table4fn4">
                <p><sup>d</sup>Italic text indicates the category with the highest response proportion.</p>
              </fn>
              <fn id="table4fn5">
                <p><sup>e</sup>PEOU: perceived ease of use.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
        </sec>
        <sec>
          <title>PEOU</title>
          <p>Twenty-four of 31 participants (77.4%) expressed agreement with the ease of use of the AI scribe, selecting “agree” or “strongly agree” on the Likert scale. The mean PEOU score was 5.56 (SD 1.17) across all participants, with physicians scoring 5.54 (SD 1.16) and psychologists 5.58 (SD 1.22). There was no statistically significant difference between groups (<italic>P</italic>=.92; Cohen <italic>d</italic>=–0.04, 95% CI –0.74 to 0.67). Participants most often (strongly) agreed with the item “Learning to operate the AI scribe was easy for me” (54.8%), followed by “I find the AI scribe easy to use” (54.8%; <xref ref-type="table" rid="table4">Table 4</xref>). There was a significant and positive correlation between PEOU and SUS, QO, PIS, and AIAS. No significant correlation was found between PEOU and age or profession (<xref ref-type="table" rid="table3">Table 3</xref>).</p>
        </sec>
        <sec>
          <title>Behavioral Intention</title>
          <p>Twenty-seven of 31 participants (87.1%) agreed with the intention to use the AI scribe in the future, selecting either “agree” or “strongly agree” on the Likert scale. The mean BI score was 6.40 (SD 1.23) across all participants, with physicians scoring 6.41 (SD 0.96) and psychologists 6.39 (SD 1.55). There was no statistically significant difference between groups (<italic>P</italic>=.97; Cohen <italic>d</italic>=0.02, 95% CI –0.69 to 0.72). There was a significant positive correlation between BI and PEOU, SUS, and PU. No significant correlation was found between BI and age or profession (<xref ref-type="table" rid="table3">Table 3</xref>).</p>
        </sec>
        <sec>
          <title>JR</title>
          <p>Across all participants, the mean JR score was 5.63 (SD 1.35). Physicians had a mean score of 5.76 (SD 1.06), while psychologists had a mean score of 5.46 (SD 1.67). There was no statistically significant difference between groups (<italic>P</italic>=.55; Cohen <italic>d</italic>=0.22, 95% CI –0.49 to 0.93).</p>
          <p>No significant correlation was found between JR and age or profession (<xref ref-type="table" rid="table3">Table 3</xref>).</p>
        </sec>
        <sec>
          <title>QO</title>
          <p>The mean QO score was 4.89 (SD 1.48) across all participants, with physicians scoring 5.03 (SD 1.44) and psychologists 4.71 (SD 1.57). There was no statistically significant difference between groups (<italic>P</italic>=.57; Cohen <italic>d</italic>=0.21, 95% CI –0.50 to 0.92). No significant correlation was found between QO and age or profession (<xref ref-type="table" rid="table3">Table 3</xref>).</p>
        </sec>
        <sec>
          <title>System Usability</title>
          <p>In total, 26 of 30 participants (86.7%) considered the usability of the AI scribe to be acceptable (SUS score &#62;70). The mean SUS score was 78.3 (SD 10.4) across all participants, with physicians scoring 77.6 (SD 10.3) and psychologists 79.0 (SD 10.9). According to the adjective rating scale by Bangor et al [<xref ref-type="bibr" rid="ref3">3</xref>] and van der Nat et al [<xref ref-type="bibr" rid="ref29">29</xref>], this corresponds to the “Excellent” category, indicating a strong perceived usability of the AI scribe. There was no statistically significant difference between groups (<italic>P</italic>=.72; Cohen <italic>d</italic>=–0.13, 95% CI –0.85 to 0.59). Participants most often strongly agreed with the item “I think that I would like to use the AI scribe frequently” (80.6%, 25/31), followed by “I would imagine that most people would learn to use the AI scribe very quickly” (70.0%, 21/30). There was a significant positive correlation among SUS, QO, and PIS. No significant correlation was found between SUS and AIAS, age, or profession (<xref ref-type="table" rid="table3">Table 3</xref>).</p>
        </sec>
        <sec>
          <title>General Attitude Toward AI Technology</title>
          <p>Across all participants, the average AIAS score was 7.84 (SD 1.60). Physicians had a mean score of 7.78 (SD 1.49), while psychologists had a mean score of 7.91 (SD 1.78). There was no statistically significant difference between groups (<italic>P</italic>=.83; Cohen <italic>d</italic>=–0.08, 95% CI –0.79 to 0.63). There was a significant and positive correlation between AIAS and PU, PIS, BI, and JR. No significant correlation was found between AIAS and age or profession (<xref ref-type="table" rid="table3">Table 3</xref>).</p>
        </sec>
        <sec>
          <title>Perception of Documentation Time and Documentation Fatigue</title>
          <p>Most participants (80.6%, 25/31) expressed some agreement that the AI scribe could help them save time on documentation. About two-thirds of participants (66.6%, 20/30) expressed some level of agreement that the AI scribe had reduced fatigue due to a lighter documentation burden (<xref rid="figure1" ref-type="fig">Figure 1</xref>).</p>
        </sec>
        <sec>
          <title>PIS</title>
          <p>Most participants agreed that the AI scribe provided positive support for patient interaction (<xref rid="figure1" ref-type="fig">Figure 1</xref>). Across multiple items, responses clustered in the upper range of the Likert scale, indicating that the AI scribe facilitates attentiveness, active listening, and patient-centered interaction. Specifically, participants reported that the AI scribe helps them maintain focus on patients' verbal and nonverbal cues (67.7%, 21/31), reduces distractions from notetaking (70.9%, 22/31), and supports clearer, more engaged dialogue (64.5%, n0/31); <xref rid="figure1" ref-type="fig">Figure 1</xref>).</p>
        </sec>
        <sec>
          <title>Qualitative Comments</title>
          <p>In their open-ended feedback, participants described the AI tool as time-saving and reported that it reduced stress and fatigue in daily practice (<xref ref-type="table" rid="table2">Table 2</xref>). They highlighted that the generated summaries provided a starting point that could be finalized more quickly. Furthermore, participants reported that the AI scribe reduced the documentation backlog, allowed more time between consultations, and decreased the time and energy spent on notetaking.</p>
        </sec>
        <sec>
          <title>Psychometric Properties of the PIS Scale</title>
          <p>The items of PIS showed excellent internal consistency (Cronbach α=0.983), with corrected item-total correlations ranging from 0.872 to 0.976 and interitem correlations between 0.84 and 0.96. An EFA supported a unidimensional structure, with one factor explaining 92.5% of the total variance (KMO=0.924; Bartlett test <italic>P</italic>&#60;.001), indicating that the items measured a coherent construct. The internal consistency remained high when any single item was removed, indicating that all items contributed meaningfully to the composite score. There was a significant and positive correlation between PIS and PU, PEOU, SUS, and AIAS. No significant correlation was found between PIS and age or profession (<xref ref-type="table" rid="table3">Table 3</xref>).</p>
        </sec>
        <sec>
          <title>Quality of Notes</title>
          <p>The mean modified PDQI-8 score across all participants was 4.3 (SD 0.3). Physicians had a mean score of 4.3 (SD 0.6), and psychologists had a mean score of 4.3 (SD 0.6). There was no difference between the groups on the mean modified PDQI-8 score (<italic>P</italic>=.81). Overall ratings across documentation domains are summarized in <xref ref-type="table" rid="table4">Table 4</xref>. The thoroughness domain had the lowest mean score (3.9), followed by accuracy (4.1) and synthesis (4.1). The highest mean scores across all participants were observed for comprehensibility (4.6), internal consistency (4.5), and usefulness (4.4). Psychologists reported lower scores on the domain succinct than physicians (3.7 vs 4.7, <italic>P</italic>=.01; <xref ref-type="table" rid="table5">Table 5</xref>). One participant had a missing response for the modified PDQI-8 item “Internally consistent”; therefore, analyses for this item were based on 30 responses.</p>
          <table-wrap position="float" id="table5">
            <label>Table 5</label>
            <caption>
              <p>Ratings of documentation quality in the modified PDQI-8<sup>a</sup> by domain.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="160"/>
              <col width="170"/>
              <col width="210"/>
              <col width="230"/>
              <col width="70"/>
              <col width="160"/>
              <thead>
                <tr valign="top">
                  <td>Domain</td>
                  <td>All (n=30), mean (SD)</td>
                  <td>Physicians (n=18), mean (SD)</td>
                  <td>Psychologists (n=12), mean (SD)</td>
                  <td><italic>P</italic> value</td>
                  <td>Cohen <italic>d</italic> (95% CI)</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Accurate</td>
                  <td>4.1 (0.8)</td>
                  <td>4.1 (0.7)</td>
                  <td>4.0 (1.0)</td>
                  <td>.71</td>
                  <td>0.15 (–0.62 to 0.92)</td>
                </tr>
                <tr valign="top">
                  <td>Thorough</td>
                  <td>3.9 (1.0)</td>
                  <td>3.7 (1.3)</td>
                  <td>4.1 (0.5)</td>
                  <td>.31</td>
                  <td>–0.41 (–1.18 to 0.37)</td>
                </tr>
                <tr valign="top">
                  <td>Useful</td>
                  <td>4.4 (0.6)</td>
                  <td>4.4 (0.8)</td>
                  <td>4.5 (0.5)</td>
                  <td>.51</td>
                  <td>–0.26 (–1.03 to 0.51)<break/>  <break/>  </td>
                </tr>
                <tr valign="top">
                  <td>Organized</td>
                  <td>4.3 (0.7)</td>
                  <td>4.4 (0.7)</td>
                  <td>4.2 (0.8)</td>
                  <td>.38</td>
                  <td>0.35 (–0.43 to 1.12)</td>
                </tr>
                <tr valign="top">
                  <td>Comprehensible</td>
                  <td>4.6 (0.6)</td>
                  <td>4.7 (0.5)</td>
                  <td>4.5 (0.8)</td>
                  <td>.36</td>
                  <td>0.37 (–0.41 to 1.14)</td>
                </tr>
                <tr valign="top">
                  <td>Succinct</td>
                  <td>4.3 (1.0)</td>
                  <td>4.7 (0.5)</td>
                  <td>3.7 (1.3)</td>
                  <td>.01<sup>b</sup></td>
                  <td>1.08 (0.25 to 1.90)</td>
                </tr>
                <tr valign="top">
                  <td>Synthesized</td>
                  <td>4.1 (0.7)</td>
                  <td>4.2 (0.8)</td>
                  <td>4.0 (0.6)</td>
                  <td>.50</td>
                  <td>0.27 (–0.51 to 1.03)</td>
                </tr>
                <tr valign="top">
                  <td>Internally consistent<break/>  <break/>  </td>
                  <td>4.5 (0.6)</td>
                  <td>4.5 (0.7)</td>
                  <td>4.5 (0.7)</td>
                  <td>.96</td>
                  <td>0.02 (–0.76 to 0.80)</td>
                </tr>
                <tr valign="top">
                  <td>Mean total (SD)</td>
                  <td>4.3 (0.5)</td>
                  <td>4.3 (0.5)</td>
                  <td>4.2 (0.6)</td>
                  <td>.46</td>
                  <td>0.29 (–0.49 to 1.06)</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table5fn1">
                <p><sup>a</sup>PDQI-8: 8-item Physician Documentation Quality Instrument.</p>
              </fn>
              <fn id="table5fn2">
                <p><sup>b</sup>Significance at <italic>P</italic>&#60;.05.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
          <p>In the open-ended questions, clinicians were divided in their experiences regarding the quality of the generated summaries. Some reported that the summaries were well-structured and occasionally captured more than they themselves had noted during the consultation, such as “it captured things I did not manage to note during the consultation” and “reduced the risk of missing out something important during the conversation.” Some participants described the AI scribe as selective in what it included. While some clinicians appreciated that “small talk” was excluded, others considered it a drawback that important information was occasionally omitted. Some noted that the summaries lacked coherence and did not sufficiently capture biopsychosocial aspects, such as upbringing and conflicts, describing them as “lacking a holistic perspective.” Participants reported that the summaries contained enough inaccuracies to require editing and proofreading (<xref ref-type="table" rid="table2">Table 2</xref>).</p>
          <p>In open-ended feedback, clinicians reported that the AI scribe allowed them to draw more attention to the patient during consultations. They described being able to speak directly with the patient without taking handwritten notes or typing on a computer as an advantage. Another advantage mentioned was the ability to share the generated summary with the patient immediately after the consultation, enabling the patient to review and provide corrections or additional input. As a potential drawback, some clinicians noted that the recording could make some patients uncomfortable and “might limit the ability to talk about difficult topics” (<xref ref-type="table" rid="table2">Table 2</xref>).</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>To our knowledge, this is the first study to explore the PU and usability of an AI-based ambient scribe among physicians and psychologists working in specialized multidisciplinary rehabilitation. The results show that the AI scribe was perceived as both valuable and easy to use by most participants, with no significant differences between physicians and psychologists. Usability ratings were high, with over 86% of participants scoring above the accepted threshold on the SUS [<xref ref-type="bibr" rid="ref3">3</xref>], indicating a positive usability experience. Although the study did not include a comparison with conventional documentation workflows, the mean SUS score of 78.3 exceeded the widely accepted benchmark score of 68 for average usability. Recent evidence has also suggested that this benchmark is applicable to digital health applications, supporting its use for contextualizing the present findings [<xref ref-type="bibr" rid="ref36">36</xref>]. Comparisons across studies should nevertheless be interpreted cautiously because of differences in technologies, settings, and study populations. While overall perceptions were positive, some participants noted challenges, including occasional inaccuracies, selective omission of relevant information, and insufficient coverage of biopsychosocial aspects. In sum, these findings suggest that the AI scribe was generally well-received and perceived as useful for supporting clinical documentation in specialized rehabilitation settings.</p>
        <p>Most participants considered the AI scribe important and relevant to their clinical work. JR showed a strong positive correlation with PU (<italic>r</italic>=0.731), indicating that clinicians who viewed the AI scribe as applicable to their professional responsibilities also tended to perceive it as beneficial. About 87% of participants reported an intention to use (behavioral intention [BI]) the AI scribe in the future, provided they were given the opportunity. These findings indicate a generally high level of acceptance and willingness to adopt the AI scribe among participants. Moreover, intention to use the AI scribe was positively correlated with PU, PEOU, and SUS. The observed correlations indicate that PU and PEOU were associated with intention to use the AI scribe, consistent with the relationships proposed in the TAM model [<xref ref-type="bibr" rid="ref24">24</xref>]. It should be noted that, in contrast to previous studies, PU has shown a clearly more decisive influence than PEOU on AI adoption in health care [<xref ref-type="bibr" rid="ref37">37</xref>]. Our findings indicate a more balanced contribution of both constructs to BI (PU: <italic>r</italic>=0.585; PEOU: <italic>r</italic>=0.505). This may reflect the practical importance of ease of integration into clinical workflows, where time constraints, cognitive load, and the need for seamless documentation make usability a key consideration. However, it cannot be ruled out that the importance of PEOU might have diminished over time had clinicians gained more extensive experience with the AI scribe beyond the 4 weeks. This assumption is based on previous research suggesting that once the PU of a technology is firmly established, ease of use may become a less decisive factor in adoption decisions [<xref ref-type="bibr" rid="ref38">38</xref>,<xref ref-type="bibr" rid="ref39">39</xref>]. Nonetheless, in clinical practice, where time constraints, cognitive load, and the need for seamless documentation present ongoing challenges, continued attention to both PU and usability remains essential to support the long-term adoption of ambient AI scribe tools.</p>
        <p>In addition to these system-specific factors, participants' general attitudes toward AI were assessed using the AIAS [<xref ref-type="bibr" rid="ref33">33</xref>]. The mean score of 7.84 out of 10 indicates a broadly positive attitude toward AI. Although no significant differences were found between professions or age groups, AIAS scores correlated positively with PU, PIS, BI, and JR, suggesting that clinicians with more positive attitudes toward AI also tended to evaluate the AI scribe more favorably. It should be noted, however, that AIAS was administered after participants had used the AI scribe. While designed to measure general attitudes, responses may have been influenced by the specific experience, potentially affecting correlation coefficients. This type of response bias is a known concern in postintervention measurement of attitudes, particularly in technology acceptance research [<xref ref-type="bibr" rid="ref40">40</xref>]. Future studies should consider measuring general AI attitudes prior to exposure to better distinguish pre-existing dispositions from experience-based evaluations.</p>
        <p>Beyond general measures of technology acceptance and usability, a majority of participants reported that the AI scribe contributed positively to their clinical workflow. The results of this study suggest that ambient AI-scribing was perceived as contributing to greater efficiency, reduced documentation burden, and more attentive patient interactions during consultations. Specifically, 81% of participants responded with slight to strong agreement (Likert scale: 5–7) that the AI scribe reduced the time spent on documentation for the patient in question. In comparison, 66% reported reduced fatigue, addressing 2 commonly cited challenges in clinical contexts with high documentation demands [<xref ref-type="bibr" rid="ref41">41</xref>]. While the current study did not directly measure time spent on clinical notetaking, the high level of agreement suggests that many participants perceived a meaningful reduction in documentation burden. This perception aligns with previous research suggesting that AI scribe technology may reduce perceived documentation burden and documentation-related workload while supporting clinician-patient interaction. However, reported effects on objective measures such as documentation time, EHR use, and productivity have varied across studies and clinical settings [<xref ref-type="bibr" rid="ref42">42</xref>-<xref ref-type="bibr" rid="ref47">47</xref>]. In their free-text answers, participants perceived the main benefit of the AI scribe as its ability to produce a well-structured initial draft that served as a foundation for documentation. Participants described the AI scribe as helping streamline note creation, reduce typing effort, and decrease time spent on postconsultation tasks. Several participants also perceived benefits related to reduced backlog, stress, and fatigue. On the other hand, some participants mentioned the omission of relevant information, inaccuracies, and increased editing time as disadvantages.</p>
        <p>In addition to supporting documentation and workflow efficiency, participants also highlighted relational benefits of the AI scribe. Importantly, many perceived it as a support for patient interaction during consultations. Participants frequently reported that the AI scribe enhanced attentiveness, reduced distractions associated with notetaking, and facilitated more engaged patient interactions. These qualities are highly relevant in specialized rehabilitation, where therapeutic alliance and interaction are central to the quality of care. In fact, providing care in this context is both cognitively and relationally demanding [<xref ref-type="bibr" rid="ref48">48</xref>,<xref ref-type="bibr" rid="ref49">49</xref>], requiring clinicians to maintain focused attention to support complex decision-making, deliver individualized education, document clinical encounters, and foster a trusting relationship. Digital tools perceived as reducing cognitive load and administrative distractions, such as ambient AI scribes, may therefore be perceived as supportive of the therapeutic process.</p>
        <p>In free-text responses in our study, participants reported that the AI scribe reduced reliance on memory for notetaking, as the generated draft captured key elements of the dialogue and minimized computer interaction during consultations. Participants reported that this supported more face-to-face engagement and attentiveness to patient needs. The positive impressions reported by many participants in our study are not isolated. Similar experiences have been documented in other clinical environments, reinforcing the notion that ambient AI scribe technology may support both interaction and workflow. For instance, studies have shown that such tools are associated with more personal and effective clinician–patient interactions, reduced clerical workload, and improved attentiveness [<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref43">43</xref>]. In addition, a recently published study from Australia found that the AI scribe had a positive impact on factors considered important to the therapeutic alliance, such as listening, eye contact, and engagement, both among patients and allied health professionals [<xref ref-type="bibr" rid="ref50">50</xref>]. These observations align with the results of our study, in which many participants reported increased engagement and attention during consultations.</p>
        <p>In addition to the feedback provided in free-text fields by participants, this study introduced a composite variable, PIS, to quantitatively assess how use of the AI scribe influenced clinician-patient interaction and to explore its potential impact on technology acceptance constructs. Interestingly, PIS showed a strong correlation with PU (<italic>r</italic>=0.778), a moderate correlation with PEOU (<italic>r</italic>=0.519), and a weaker correlation with SUS (<italic>r</italic>=0.413). These results suggest that PIS was associated with clinicians’ perceptions of usefulness and usability. However, the observed correlations reflect associations between variables and do not permit conclusions about causality or the direction of these relationships. However, it should be noted that while the majority of participants in the present study reported supportive effects on patient interaction, some did not. This variability in PU may reflect contextual factors such as professional role, familiarity with digital tools, or integration into existing workflows. For example, some participants noted that the AI scribe did not align well with their documentation routines or clinical setting, which may have limited its perceived value. Thus, the results presented in this study offer a foundation for further research into how contextual factors may influence clinicians' acceptance of AI scribe technology in health care.</p>
        <p>The AI-generated clinical notes were generally perceived as clear, well-organized, and clinically useful, according to assessments using the modified PDQI-8 instrument. Domains such as comprehensibility, internal consistency, and usefulness received particularly positive ratings, while thoroughness and accuracy were rated somewhat lower, indicating potential for improvement. Overall quality ratings were similar between physicians and psychologists. The only significant professional difference was related to succinctness, with psychologists rating the generated notes lower than physicians. This may reflect differing documentation preferences, as psychologists may place greater emphasis on preserving psychosocial context and narrative detail that can be reduced in more concise summaries. However, these findings should be interpreted cautiously given the small sample size and exploratory nature of the analyses. The generally positive PDQI ratings observed in this study are consistent with a recent study evaluating AI-generated clinical documentation, in which ambient AI-generated notes achieved quality ratings broadly comparable to physician-authored notes when assessed using modified versions of the PDQI framework [<xref ref-type="bibr" rid="ref51">51</xref>]. However, methodological differences, including note types, evaluators, and scoring procedures, limit direct comparison with the present findings.</p>
        <p>Assessments of output quality, as conceptualized in the TAM model, indicated that most participants rated the AI scribe’s documentation as high quality. It should, however, be noted that a few participants in their free-text responses reported the clinical notes as incomplete and insufficiently addressing biopsychosocial dimensions, including social history, psychological factors, and family and work life. Furthermore, a few participants reported that the notes contained inaccuracies, which increased the time spent on proofreading and editing. One participant reported that the tool occasionally produced erroneous conclusions or misrepresented information from the consultation, including information about medication use. Although only a few participants raised these concerns, they highlight the need for a more comprehensive inclusion of biopsychosocial information to enhance clinical relevance and minimize the need for later editing. As the assessment of documentation quality was based on notes from initial patient consultations, future studies should examine how the AI scribe performs across a broader range of clinical contexts, where documentation needs and expectations may differ.</p>
        <p>Although our study, along with previous studies, has found that clinicians generally rate AI-generated clinical notes as good to excellent in quality [<xref ref-type="bibr" rid="ref52">52</xref>], several categories of errors warrant attention. Hallucinations, or fabricated content not present in the conversation, occurred more frequently in AI notes (31%) than in physician-authored notes (20%) [<xref ref-type="bibr" rid="ref51">51</xref>]. Omission errors were also common, often involving details such as the history of present illness or social factors [<xref ref-type="bibr" rid="ref52">52</xref>]. Some systems failed to differentiate and emphasize critical problems over less urgent ones, which may affect clinical prioritization [<xref ref-type="bibr" rid="ref45">45</xref>]. Structural issues included misclassification in key sections of the clinical note and generalization errors, in which specific information was oversimplified (eg, “Colles fracture” reduced to “fracture”) [<xref ref-type="bibr" rid="ref52">52</xref>]. Finally, contextual factors such as off-topic dialogue and multi-speaker interactions affected accuracy, with some systems struggling to distinguish between 3 or more voices [<xref ref-type="bibr" rid="ref52">52</xref>]. These findings underscore the need for ongoing refinement of AI scribe algorithms to minimize errors and ensure clinical reliability.</p>
      </sec>
      <sec>
        <title>Relationship Between System Usability Score and TAM Constructs</title>
        <p>To explore the role of usability in technology acceptance, the study examined how SUS scores related to TAM constructs, including BI. The observed correlation between SUS scores and BI (<italic>r</italic>=0.601) suggests that participants who perceived the AI scribe as more usable also tended to report a stronger intention to use it, complementing the TAM constructs of PEOU and PU. The stronger correlation between SUS and PEOU (<italic>r</italic>=0.794) than between SUS and PU (<italic>r</italic>=0.433) indicates that ease of use and usability may capture similar aspects of user experience. This is particularly relevant given that SUS is a standardized usability measure, whereas PEOU is a theoretical construct within TAM. This observation aligns with previous research suggesting that PEOU can reflect perceptions of usability in technology acceptance contexts [<xref ref-type="bibr" rid="ref53">53</xref>]. Thus, future research could use the TAM framework to investigate the usability aspects of AI scribes further.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>The interpretation of this study’s results must be tempered with an understanding of its limitations. The participants were from a similar rehabilitation organization, which may limit the generalizability of the findings. There was also a potential sampling bias among physicians and psychologists who volunteered to participate. To better understand the use of AI scribes in rehabilitation practices, future studies should consider clinicians who have concerns about incorporating an AI scribe in their practice. This explorative study also had a modest sample size and a relatively short intervention period, which together may limit the representativeness of the results. Unfortunately, due to technical errors, usage data, including the number of consultations and time spent on documentation, were not available. Consequently, individual exposure to the AI scribe could not be quantified, preventing analysis of actual usage patterns or potential differences in experiences according to frequency use. In addition, the study did not include baseline measurements or a control group, limiting the ability to determine whether the observed perceptions can be attributed specifically to AI scribe use.</p>
        <p>Furthermore, the study did not include objective measurements of documentation time, independent assessments of note accuracy, or patient-reported outcomes. As a result, conclusions are limited to clinicians’ self-reported perceptions and cannot establish effects on documentation efficiency, note quality, accuracy, or patient experience. Finally, participants may have been more motivated to engage with new technology than non-participants, and the introduction of a novel tool may have contributed to more favorable responses, resulting in potential selection and novelty bias.</p>
        <p>Moreover, self-reported data may introduce recall or reporting bias, limiting the accuracy of the findings. The modified PDQI-8 was administered following a single consultation, limiting the ability to assess the consistency and reliability of note-quality ratings over time. Although the rating of note quality was relatively consistent in this study, repeated assessments across multiple consultations could provide a more comprehensive understanding of the accuracy and quality of clinical notes in routine practice. It should be noted that the free-text answers may have been influenced by the preceding structured questionnaires (SUS, TAM, modified PDQI-8), as participants answered the open-ended questions after completing these scales. Consequently, the identified themes, such as time use, documentation burden, note quality, and patient interaction, reflect categories emphasized in the questionnaires, which may have shaped participants' focus and wording. In addition, questions related to the interaction aspect were phrased as positive statements, consistent with the TAM methodology. This may represent a limitation, as positive wording may lead to a tendency to agree, potentially reducing the ability to capture critical or negative perceptions. A limitation of this study is that participants were not invited to review or comment on the findings following the analysis.</p>
        <p>While the composite measure of PIS showed high internal consistency, the strong interitem correlations suggest it may capture a narrow aspect of interaction support. This may imply that the measure primarily captures a specific dimension of clinician-patient interaction, such as attentional presence or reduced distraction, rather than the broader complexity of clinical interaction. Thus, future research should refine item wording to better capture the multifaceted nature of interaction in clinical practice and use qualitative methods to obtain more in-depth data on the communicative aspects of AI scribes.</p>
      </sec>
      <sec>
        <title>Conclusion</title>
        <p>This study provides initial evidence of acceptance of an AI-based ambient scribe among physicians and psychologists in specialized rehabilitation, with generally positive perceptions of its usefulness, usability, and documentation quality, and future use intentions. Most participants reported a perceived reduction in documentation burden and experienced the AI scribe as supportive of attentiveness during consultations. However, the findings reflect clinicians’ subjective experiences and do not establish objective effects on documentation time, documentation accuracy, clinical outcomes, patient safety, or clinician well-being. Participants also reported omissions, occasional inaccuracies, and insufficient coverage of biopsychosocial aspects in generated notes, highlighting the continued need for clinician review and suggesting areas for further development. General attitudes toward AI were associated with key acceptance variables, indicating that broader views on AI may influence how such technologies are received in practice. Overall, the findings suggest that ambient AI-scribing is acceptable to many rehabilitation clinicians and is perceived as supportive of documentation processes and clinician-patient interactions. Future studies should investigate its implementation in routine care using objective measures of documentation time, note accuracy, workflow integration, quality of care, patient outcomes, and safety. Research should also explore long-term effects across diverse clinical contexts and professional roles and improve evaluation instruments to better capture the communicative and clinical impact of AI-assisted documentation.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Study-specific items included in the perceived interaction support (PIS) composite score.</p>
        <media xlink:href="rehab_v13i1e90442_app1.docx" xlink:title="DOCX File , 31 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">AIAS</term>
          <def>
            <p>AI Attitude Scale</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">BI</term>
          <def>
            <p>behavioral intention</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">CGS</term>
          <def>
            <p>Curved Grading Scale</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">EFA</term>
          <def>
            <p>exploratory factor analysis</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">GDPR</term>
          <def>
            <p>General Data Protection Regulation</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">IU</term>
          <def>
            <p>intention to use</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">JR</term>
          <def>
            <p>job relevance</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">KMO</term>
          <def>
            <p>Kaiser-Meyer-Olkin</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">mPDQI-8</term>
          <def>
            <p>modified 8-item Physician Documentation Quality Instrument</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb11">NLP</term>
          <def>
            <p>natural language processing</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb12">PDQI</term>
          <def>
            <p>Physician Documentation Quality Instrument</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb13">PDQI-8</term>
          <def>
            <p>8-item Physician Documentation Quality Instrument</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb14">PDQI-9</term>
          <def>
            <p>9-item Physician Documentation Quality Instrument</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb15">PEOU</term>
          <def>
            <p>perceived ease of use</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb16">PIS</term>
          <def>
            <p>perceived interaction support</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb17">PU</term>
          <def>
            <p>perceived usefulness</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb18">QO</term>
          <def>
            <p>quality output</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb19">SUS</term>
          <def>
            <p>System Usability Scale</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb20">TAM</term>
          <def>
            <p>technology acceptance model</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb21">UMUX</term>
          <def>
            <p>usability metric for user experience</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The authors extend special thanks to candidate psychologist Kjetil Fjell, Associate Professor Simone Grassini, and senior researcher Filip Drozd, who provided valuable advice during the initial planning of the study, and to the psychologists and physicians at Unicare Rehabilitation, who volunteered for the study.</p>
    </ack>
    <notes>
      <sec>
        <title>Funding</title>
        <p>No external funding was obtained.</p>
      </sec>
    </notes>
    <notes>
      <sec>
        <title>Data Availability</title>
        <p>The dataset generated and/or analyzed in this study are available from the corresponding author upon reasonable request.</p>
      </sec>
    </notes>
    <fn-group>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <notes>
      <sec>
        <title>Generative AI Use</title>
        <p>Microsoft Copilot was used to support language editing. All AI-assisted text was reviewed and revised by the authors, who take full responsibility for the final content.</p>
      </sec>
    </notes>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kuhn</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Basch</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Barr</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Yackel</surname>
              <given-names>T</given-names>
            </name>
            <collab>Medical Informatics Committee of the American College of Physicians</collab>
          </person-group>
          <article-title>Clinical documentation in the 21st century: executive summary of a policy position paper from the American College of Physicians</article-title>
          <source>Ann Intern Med</source>
          <year>2015</year>
          <month>02</month>
          <day>17</day>
          <volume>162</volume>
          <issue>4</issue>
          <fpage>301</fpage>
          <lpage>3</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.acpjournals.org/doi/10.7326/M14-2128?url_ver=Z39.88-2003&#38;rfr_id=ori:rid:crossref.org&#38;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.7326/M14-2128</pub-id>
          <pub-id pub-id-type="medline">25581028</pub-id>
          <pub-id pub-id-type="pii">2089368</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>Vos</surname>
              <given-names>JFJ</given-names>
            </name>
            <name name-style="western">
              <surname>Boonstra</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kooistra</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Seelen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>van Offenbeek</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>The influence of electronic health record use on collaboration among medical specialties</article-title>
          <source>BMC Health Serv Res</source>
          <year>2020</year>
          <month>07</month>
          <day>22</day>
          <volume>20</volume>
          <issue>1</issue>
          <fpage>676</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmchealthservres.biomedcentral.com/articles/10.1186/s12913-020-05542-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12913-020-05542-6</pub-id>
          <pub-id pub-id-type="medline">32698807</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12913-020-05542-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC7374868</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>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 Stud</source>
          <year>2009</year>
          <volume>4</volume>
          <issue>3</issue>
          <fpage>114</fpage>
          <lpage>123</lpage>
          <pub-id pub-id-type="doi">10.5555/2835587.2835589</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>Kjeken</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Bjor</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Westerlund</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Interdisciplinary documentation of the course of rehabilitation</article-title>
          <source>Tidsskr Nor Laegeforen</source>
          <year>2008</year>
          <volume>128</volume>
          <issue>4</issue>
          <fpage>468</fpage>
          <lpage>470</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://tidsskriftet.no/article/1657320"/>
          </comment>
          <pub-id pub-id-type="medline">18274584</pub-id>
          <pub-id pub-id-type="pii">1657320</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Schwartz-Dillard</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ng</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Villegas</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Murray-Weir</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Electronic documentation burden among outpatient rehabilitation therapists: a qualitative descriptive study and quality improvement initiative</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2024</year>
          <month>10</month>
          <day>01</day>
          <volume>31</volume>
          <issue>10</issue>
          <fpage>2347</fpage>
          <lpage>2355</lpage>
          <pub-id pub-id-type="doi">10.1093/jamia/ocae192</pub-id>
          <pub-id pub-id-type="medline">39042519</pub-id>
          <pub-id pub-id-type="pii">7718666</pub-id>
          <pub-id pub-id-type="pmcid">PMC11413440</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>Asan</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>D Smith</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Montague</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>More screen time, less face time - implications for EHR design</article-title>
          <source>J Eval Clin Pract</source>
          <year>2014</year>
          <month>12</month>
          <volume>20</volume>
          <issue>6</issue>
          <fpage>896</fpage>
          <lpage>901</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/24835678"/>
          </comment>
          <pub-id pub-id-type="doi">10.1111/jep.12182</pub-id>
          <pub-id pub-id-type="medline">24835678</pub-id>
          <pub-id pub-id-type="pmcid">PMC4237676</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sinsky</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Colligan</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Prgomet</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Reynolds</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Goeders</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Westbrook</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Tutty</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Blike</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Allocation of physician time in ambulatory practice: a time and motion study in 4 specialties</article-title>
          <source>Ann Intern Med</source>
          <year>2016</year>
          <month>12</month>
          <day>06</day>
          <volume>165</volume>
          <issue>11</issue>
          <fpage>753</fpage>
          <lpage>760</lpage>
          <pub-id pub-id-type="doi">10.7326/M16-0961</pub-id>
          <pub-id pub-id-type="medline">27595430</pub-id>
          <pub-id pub-id-type="pii">2546704</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tai-Seale</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Olson</surname>
              <given-names>CW</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Chan</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Morikawa</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Durbin</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Luft</surname>
              <given-names>HS</given-names>
            </name>
          </person-group>
          <article-title>Electronic health record logs indicate that physicians split time evenly between seeing patients and desktop medicine</article-title>
          <source>Health Aff (Millwood)</source>
          <year>2017</year>
          <month>04</month>
          <day>01</day>
          <volume>36</volume>
          <issue>4</issue>
          <fpage>655</fpage>
          <lpage>662</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/28373331"/>
          </comment>
          <pub-id pub-id-type="doi">10.1377/hlthaff.2016.0811</pub-id>
          <pub-id pub-id-type="medline">28373331</pub-id>
          <pub-id pub-id-type="pii">36/4/655</pub-id>
          <pub-id pub-id-type="pmcid">PMC5546411</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Holmgren</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Downing</surname>
              <given-names>NL</given-names>
            </name>
            <name name-style="western">
              <surname>Bates</surname>
              <given-names>DW</given-names>
            </name>
            <name name-style="western">
              <surname>Shanafelt</surname>
              <given-names>TD</given-names>
            </name>
            <name name-style="western">
              <surname>Milstein</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sharp</surname>
              <given-names>CD</given-names>
            </name>
            <name name-style="western">
              <surname>Cutler</surname>
              <given-names>DM</given-names>
            </name>
            <name name-style="western">
              <surname>Huckman</surname>
              <given-names>RS</given-names>
            </name>
            <name name-style="western">
              <surname>Schulman</surname>
              <given-names>KA</given-names>
            </name>
          </person-group>
          <article-title>Assessment of electronic health record use between US and non-US Health systems</article-title>
          <source>JAMA Intern Med</source>
          <year>2021</year>
          <month>02</month>
          <day>01</day>
          <volume>181</volume>
          <issue>2</issue>
          <fpage>251</fpage>
          <lpage>259</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33315048"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamainternmed.2020.7071</pub-id>
          <pub-id pub-id-type="medline">33315048</pub-id>
          <pub-id pub-id-type="pii">2774129</pub-id>
          <pub-id pub-id-type="pmcid">PMC7737152</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>Gesner</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Dykes</surname>
              <given-names>PC</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Gazarian</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Documentation burden in nursing and its role in clinician burnout syndrome</article-title>
          <source>Appl Clin Inform</source>
          <year>2022</year>
          <month>10</month>
          <volume>13</volume>
          <issue>5</issue>
          <fpage>983</fpage>
          <lpage>990</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.thieme-connect.com/DOI/DOI?10.1055/s-0042-1757157"/>
          </comment>
          <pub-id pub-id-type="doi">10.1055/s-0042-1757157</pub-id>
          <pub-id pub-id-type="medline">36261113</pub-id>
          <pub-id pub-id-type="pmcid">PMC9581587</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>Mazur</surname>
              <given-names>LM</given-names>
            </name>
            <name name-style="western">
              <surname>Adapa</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Meltzer-Brody</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Karwowski</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>Towards better understanding of workplace factors contributing to hospitalist burden and burnout prior to COVID-19 pandemic</article-title>
          <source>Appl Ergon</source>
          <year>2023</year>
          <month>01</month>
          <volume>106</volume>
          <fpage>103884</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/36030734"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.apergo.2022.103884</pub-id>
          <pub-id pub-id-type="medline">36030734</pub-id>
          <pub-id pub-id-type="pii">S0003-6870(22)00207-1</pub-id>
          <pub-id pub-id-type="pmcid">PMC9395300</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>Alobayli</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>O'Connor</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Holloway</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Cresswell</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Electronic health record stress and burnout among clinicians in hospital settings: a systematic review</article-title>
          <source>Digit Health</source>
          <year>2023</year>
          <volume>9</volume>
          <fpage>20552076231220241</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/10.1177/20552076231220241?url_ver=Z39.88-2003&#38;rfr_id=ori:rid:crossref.org&#38;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/20552076231220241</pub-id>
          <pub-id pub-id-type="medline">38130797</pub-id>
          <pub-id pub-id-type="pii">10.1177_20552076231220241</pub-id>
          <pub-id pub-id-type="pmcid">PMC10734365</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>Dugdale</surname>
              <given-names>DC</given-names>
            </name>
            <name name-style="western">
              <surname>Epstein</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Pantilat</surname>
              <given-names>SZ</given-names>
            </name>
          </person-group>
          <article-title>Time and the patient-physician relationship</article-title>
          <source>J Gen Intern Med</source>
          <year>1999</year>
          <month>01</month>
          <volume>14 Suppl 1</volume>
          <issue>Suppl 1</issue>
          <fpage>S34</fpage>
          <lpage>40</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/9933493"/>
          </comment>
          <pub-id pub-id-type="doi">10.1046/j.1525-1497.1999.00263.x</pub-id>
          <pub-id pub-id-type="medline">9933493</pub-id>
          <pub-id pub-id-type="pmcid">PMC1496869</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>van Buchem</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Boosman</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Bauer</surname>
              <given-names>MP</given-names>
            </name>
            <name name-style="western">
              <surname>Kant</surname>
              <given-names>IMJ</given-names>
            </name>
            <name name-style="western">
              <surname>Cammel</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Steyerberg</surname>
              <given-names>EW</given-names>
            </name>
          </person-group>
          <article-title>The digital scribe in clinical practice: a scoping review and research agenda</article-title>
          <source>NPJ Digit Med</source>
          <year>2021</year>
          <month>03</month>
          <day>26</day>
          <volume>4</volume>
          <issue>1</issue>
          <fpage>57</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-021-00432-5"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-021-00432-5</pub-id>
          <pub-id pub-id-type="medline">33772070</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41746-021-00432-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC7997964</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>Mess</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Mackey</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Yarowsky</surname>
              <given-names>DE</given-names>
            </name>
          </person-group>
          <article-title>Artificial intelligence scribe and large language model technology in healthcare documentation: advantages, limitations, and recommendations</article-title>
          <source>Plast Reconstr Surg Glob Open</source>
          <year>2025</year>
          <month>01</month>
          <volume>13</volume>
          <issue>1</issue>
          <fpage>e6450</fpage>
          <pub-id pub-id-type="doi">10.1097/GOX.0000000000006450</pub-id>
          <pub-id pub-id-type="medline">39823022</pub-id>
          <pub-id pub-id-type="pii">GOX-D-24-00947</pub-id>
          <pub-id pub-id-type="pmcid">PMC11737491</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>Bracken</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Reilly</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Feeley</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sheehan</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Merghani</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Feeley</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Artificial intelligence (AI) - powered documentation systems in healthcare: a systematic review</article-title>
          <source>J Med Syst</source>
          <year>2025</year>
          <month>02</month>
          <day>18</day>
          <volume>49</volume>
          <issue>1</issue>
          <fpage>28</fpage>
          <pub-id pub-id-type="doi">10.1007/s10916-025-02157-4</pub-id>
          <pub-id pub-id-type="medline">39966286</pub-id>
          <pub-id pub-id-type="pii">10.1007/s10916-025-02157-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC11835907</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>Lee</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Britto</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Diwan</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Evaluating the impact of artificial intelligence (AI) on clinical documentation efficiency and accuracy across clinical settings: a scoping review</article-title>
          <source>Cureus</source>
          <year>2024</year>
          <month>11</month>
          <volume>16</volume>
          <issue>11</issue>
          <fpage>e73994</fpage>
          <pub-id pub-id-type="doi">10.7759/cureus.73994</pub-id>
          <pub-id pub-id-type="medline">39703286</pub-id>
          <pub-id pub-id-type="pmcid">PMC11658896</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>Shah</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Devon-Sand</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ma</surname>
              <given-names>SP</given-names>
            </name>
            <name name-style="western">
              <surname>Jeong</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Crowell</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Liang</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Delahaie</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Hsia</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Shanafelt</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Pfeffer</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Sharp</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Garcia</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Ambient artificial intelligence scribes: physician burnout and perspectives on usability and documentation burden</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2025</year>
          <month>02</month>
          <day>01</day>
          <volume>32</volume>
          <issue>2</issue>
          <fpage>375</fpage>
          <lpage>380</lpage>
          <pub-id pub-id-type="doi">10.1093/jamia/ocae295</pub-id>
          <pub-id pub-id-type="medline">39657021</pub-id>
          <pub-id pub-id-type="pii">7917501</pub-id>
          <pub-id pub-id-type="pmcid">PMC11756571</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>Ghatnekar</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Faletsky</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Nambudiri</surname>
              <given-names>VE</given-names>
            </name>
          </person-group>
          <article-title>Digital scribe utility and barriers to implementation in clinical practice: a scoping review</article-title>
          <source>Health Technol (Berl)</source>
          <year>2021</year>
          <volume>11</volume>
          <issue>4</issue>
          <fpage>803</fpage>
          <lpage>809</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34094806"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s12553-021-00568-0</pub-id>
          <pub-id pub-id-type="medline">34094806</pub-id>
          <pub-id pub-id-type="pii">568</pub-id>
          <pub-id pub-id-type="pmcid">PMC8169416</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>von Elm</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Altman</surname>
              <given-names>DG</given-names>
            </name>
            <name name-style="western">
              <surname>Egger</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Pocock</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Gøtzsche</surname>
              <given-names>Peter C</given-names>
            </name>
            <name name-style="western">
              <surname>Vandenbroucke</surname>
              <given-names>JP</given-names>
            </name>
            <collab>STROBE Initiative</collab>
          </person-group>
          <article-title>The Strengthening the Reporting of Observational Studies in Epidemiology (STROBE) statement: guidelines for reporting observational studies</article-title>
          <source>Ann Intern Med</source>
          <year>2007</year>
          <month>10</month>
          <day>16</day>
          <volume>147</volume>
          <issue>8</issue>
          <fpage>573</fpage>
          <lpage>7</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.acpjournals.org/doi/10.7326/0003-4819-147-8-200710160-00010?url_ver=Z39.88-2003&#38;rfr_id=ori:rid:crossref.org&#38;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.7326/0003-4819-147-8-200710160-00010</pub-id>
          <pub-id pub-id-type="medline">17938396</pub-id>
          <pub-id pub-id-type="pii">147/8/573</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>Boscardin</surname>
              <given-names>CK</given-names>
            </name>
            <name name-style="western">
              <surname>Gin</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Golde</surname>
              <given-names>PB</given-names>
            </name>
            <name name-style="western">
              <surname>Hauer</surname>
              <given-names>KE</given-names>
            </name>
          </person-group>
          <article-title>ChatGPT and generative artificial intelligence for medical education: potential impact and opportunity</article-title>
          <source>Acad Med</source>
          <year>2024</year>
          <month>01</month>
          <day>01</day>
          <volume>99</volume>
          <issue>1</issue>
          <fpage>22</fpage>
          <lpage>27</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://academic.oup.com/academicmedicine/article-lookup/doi/10.1097/ACM.0000000000005439"/>
          </comment>
          <pub-id pub-id-type="doi">10.1097/ACM.0000000000005439</pub-id>
          <pub-id pub-id-type="medline">37651677</pub-id>
          <pub-id pub-id-type="pii">00001888-202401000-00011</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Persico</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Manca</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Pozzi</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Adapting the technology acceptance model to evaluate the innovative potential of e-learning systems</article-title>
          <source>Computers in Human Behavior</source>
          <year>2014</year>
          <month>01</month>
          <volume>30</volume>
          <fpage>614</fpage>
          <lpage>622</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.chb.2013.07.045"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.chb.2013.07.045</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hornbæk</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Hertzum</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Technology acceptance and user experience</article-title>
          <source>ACM Trans Comput-Hum Interact</source>
          <year>2017</year>
          <month>10</month>
          <day>06</day>
          <volume>24</volume>
          <issue>5</issue>
          <fpage>1</fpage>
          <lpage>30</lpage>
          <pub-id pub-id-type="doi">10.1145/3127358</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Davis</surname>
              <given-names>FD</given-names>
            </name>
          </person-group>
          <article-title>Perceived usefulness, perceived ease of use, and user acceptance of information technology</article-title>
          <source>MIS Q</source>
          <year>1989</year>
          <volume>13</volume>
          <issue>3</issue>
          <fpage>319</fpage>
          <lpage>340</lpage>
          <pub-id pub-id-type="doi">10.2307/249008</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nguyen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Fujioka</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wentlandt</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Onabajo</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Wong</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Bhatia</surname>
              <given-names>RS</given-names>
            </name>
            <name name-style="western">
              <surname>Bhattacharyya</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Stamenova</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Using the technology acceptance model to explore health provider and administrator perceptions of the usefulness and ease of using technology in palliative care</article-title>
          <source>BMC Palliat Care</source>
          <year>2020</year>
          <month>09</month>
          <day>07</day>
          <volume>19</volume>
          <issue>1</issue>
          <fpage>138</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcpalliatcare.biomedcentral.com/articles/10.1186/s12904-020-00644-8"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12904-020-00644-8</pub-id>
          <pub-id pub-id-type="medline">32895060</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12904-020-00644-8</pub-id>
          <pub-id pub-id-type="pmcid">PMC7476427</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>Venkatesh</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Davis</surname>
              <given-names>FD</given-names>
            </name>
          </person-group>
          <article-title>A theoretical extension of the technology acceptance model: four longitudinal field studies</article-title>
          <source>Management Science</source>
          <year>2000</year>
          <month>02</month>
          <volume>46</volume>
          <issue>2</issue>
          <fpage>186</fpage>
          <lpage>204</lpage>
          <pub-id pub-id-type="doi">10.1287/mnsc.46.2.186.11926</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>Lewis</surname>
              <given-names>JR</given-names>
            </name>
          </person-group>
          <article-title>The System Usability Scale: past, present, and future</article-title>
          <source>International Journal of Human–Computer Interaction</source>
          <year>2018</year>
          <month>03</month>
          <day>30</day>
          <volume>34</volume>
          <issue>7</issue>
          <fpage>577</fpage>
          <lpage>590</lpage>
          <pub-id pub-id-type="doi">10.1080/10447318.2018.1455307</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sauro</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lewis</surname>
              <given-names>JR</given-names>
            </name>
          </person-group>
          <source>Quantifying the User Experience: Practical Statistics for User Research</source>
          <year>2016</year>
          <publisher-loc>Burlington, Massachusetts</publisher-loc>
          <publisher-name>Morgan Kaufmann</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>van der Nat</surname>
              <given-names>DJ</given-names>
            </name>
            <name name-style="western">
              <surname>Huiskes</surname>
              <given-names>VJB</given-names>
            </name>
            <name name-style="western">
              <surname>Taks</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Pouls</surname>
              <given-names>BPH</given-names>
            </name>
            <name name-style="western">
              <surname>van den Bemt</surname>
              <given-names>BJF</given-names>
            </name>
            <name name-style="western">
              <surname>van Onzenoort</surname>
              <given-names>HAW</given-names>
            </name>
          </person-group>
          <article-title>Usability and perceived usefulness of patient-centered medication reconciliation using a personalized health record: a multicenter cross-sectional study</article-title>
          <source>BMC Health Serv Res</source>
          <year>2022</year>
          <month>06</month>
          <day>13</day>
          <volume>22</volume>
          <issue>1</issue>
          <fpage>776</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmchealthservres.biomedcentral.com/articles/10.1186/s12913-022-07967-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12913-022-07967-7</pub-id>
          <pub-id pub-id-type="medline">35698220</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12913-022-07967-7</pub-id>
          <pub-id pub-id-type="pmcid">PMC9195254</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Duggan</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Gervase</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Schoenbaum</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Hanson</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Howell</surname>
              <given-names>JT</given-names>
            </name>
            <name name-style="western">
              <surname>Sheinberg</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>KB</given-names>
            </name>
          </person-group>
          <article-title>Clinician experiences with ambient scribe technology to assist with documentation burden and efficiency</article-title>
          <source>JAMA Netw Open</source>
          <year>2025</year>
          <month>02</month>
          <day>03</day>
          <volume>8</volume>
          <issue>2</issue>
          <fpage>e2460637</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jamanetwork.com/journals/jamanetworkopen/fullarticle/10.1001/jamanetworkopen.2024.60637"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamanetworkopen.2024.60637</pub-id>
          <pub-id pub-id-type="medline">39969880</pub-id>
          <pub-id pub-id-type="pii">2830383</pub-id>
          <pub-id pub-id-type="pmcid">PMC11840636</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>Eo</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Park</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>YR</given-names>
            </name>
          </person-group>
          <article-title>Predictive and representative composite score</article-title>
          <source>Qual Quant</source>
          <year>2022</year>
          <month>02</month>
          <day>24</day>
          <volume>57</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>14</lpage>
          <pub-id pub-id-type="doi">10.1007/s11135-022-01345-5</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Joshi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kale</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Chandel</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Pal</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Likert scale: explored and explained</article-title>
          <source>Br J Appl Sci Technol</source>
          <year>2015</year>
          <volume>7</volume>
          <issue>4</issue>
          <fpage>396</fpage>
          <lpage>403</lpage>
          <pub-id pub-id-type="doi">10.9734/BJAST/2015/14975</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>Grassini</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Development and validation of the AI attitude scale (AIAS-4): a brief measure of general attitude toward artificial intelligence</article-title>
          <source>Front Psychol</source>
          <year>2023</year>
          <volume>14</volume>
          <fpage>1191628</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/37554139"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fpsyg.2023.1191628</pub-id>
          <pub-id pub-id-type="medline">37554139</pub-id>
          <pub-id pub-id-type="pmcid">PMC10406504</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>Tierney</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gayre</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Hoberman</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Mattern</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Ballesca</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kipnis</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Ambient artificial intelligence scribes to alleviate the burden of clinical documentation</article-title>
          <source>NEJM Catal Innov Care Deliv</source>
          <year>2024</year>
          <volume>5</volume>
          <issue>3</issue>
          <fpage>CAT.23.0404</fpage>
          <pub-id pub-id-type="doi">10.1056/CAT.23.0404</pub-id>
        </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>Venkatesh</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Bala</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Technology acceptance model 3 and a research agenda on interventions</article-title>
          <source>Decis Sci</source>
          <year>2008</year>
          <volume>39</volume>
          <issue>2</issue>
          <fpage>273</fpage>
          <lpage>315</lpage>
          <pub-id pub-id-type="doi">10.1111/j.1540-5915.2008.00192.x</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>Hyzy</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bond</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Mulvenna</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bai</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Dix</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Leigh</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hunt</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>System usability scale benchmarking for digital health apps: meta-analysis</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2022</year>
          <month>08</month>
          <day>18</day>
          <volume>10</volume>
          <issue>8</issue>
          <fpage>e37290</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2022/8/e37290/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/37290</pub-id>
          <pub-id pub-id-type="medline">35980732</pub-id>
          <pub-id pub-id-type="pii">v10i8e37290</pub-id>
          <pub-id pub-id-type="pmcid">PMC9437782</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chaibi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Brini</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Flah</surname>
              <given-names>IB</given-names>
            </name>
            <name name-style="western">
              <surname>Sobaih</surname>
              <given-names>AE</given-names>
            </name>
          </person-group>
          <article-title>Understanding AI acceptance in healthcare: a mixed-method study on trialability and doctor-patient relationships</article-title>
          <source>J Posthumanism</source>
          <year>2025</year>
          <volume>5</volume>
          <issue>1</issue>
          <fpage>89</fpage>
          <lpage>118</lpage>
          <pub-id pub-id-type="doi">10.63332/joph.v5i1.486</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gefen</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Karahanna</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Straub</surname>
              <given-names>DW</given-names>
            </name>
          </person-group>
          <article-title>Trust and TAM in online shopping: an integrated model</article-title>
          <source>MIS Q</source>
          <year>2003</year>
          <volume>27</volume>
          <issue>1</issue>
          <fpage>51</fpage>
          <lpage>90</lpage>
          <pub-id pub-id-type="doi">10.2307/30036519</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>Sobaih</surname>
              <given-names>AEE</given-names>
            </name>
            <name name-style="western">
              <surname>Elshaer</surname>
              <given-names>IA</given-names>
            </name>
            <name name-style="western">
              <surname>Hasanein</surname>
              <given-names>AM</given-names>
            </name>
          </person-group>
          <article-title>Examining students' acceptance and use of ChatGPT in Saudi Arabian higher education</article-title>
          <source>Eur J Investig Health Psychol Educ</source>
          <year>2024</year>
          <month>03</month>
          <day>17</day>
          <volume>14</volume>
          <issue>3</issue>
          <fpage>709</fpage>
          <lpage>721</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=ejihpe14030047"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/ejihpe14030047</pub-id>
          <pub-id pub-id-type="medline">38534908</pub-id>
          <pub-id pub-id-type="pii">ejihpe14030047</pub-id>
          <pub-id pub-id-type="pmcid">PMC10969089</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Podsakoff</surname>
              <given-names>PM</given-names>
            </name>
            <name name-style="western">
              <surname>MacKenzie</surname>
              <given-names>SB</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Podsakoff</surname>
              <given-names>NP</given-names>
            </name>
          </person-group>
          <article-title>Common method biases in behavioral research: a critical review of the literature and recommended remedies</article-title>
          <source>J Appl Psychol</source>
          <year>2003</year>
          <month>10</month>
          <volume>88</volume>
          <issue>5</issue>
          <fpage>879</fpage>
          <lpage>903</lpage>
          <pub-id pub-id-type="doi">10.1037/0021-9010.88.5.879</pub-id>
          <pub-id pub-id-type="medline">14516251</pub-id>
          <pub-id pub-id-type="pii">2003-08045-010</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>Budd</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Burnout related to electronic health record use in primary care</article-title>
          <source>J Prim Care Community Health</source>
          <year>2023</year>
          <volume>14</volume>
          <fpage>21501319231166921</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/10.1177/21501319231166921?url_ver=Z39.88-2003&#38;rfr_id=ori:rid:crossref.org&#38;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/21501319231166921</pub-id>
          <pub-id pub-id-type="medline">37073905</pub-id>
          <pub-id pub-id-type="pmcid">PMC10134123</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Albrecht</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Shanks</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Hudson</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Thompson</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Filardi</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Wright</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Ator</surname>
              <given-names>GA</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>TR</given-names>
            </name>
          </person-group>
          <article-title>Enhancing clinical documentation with ambient artificial intelligence: a quality improvement survey assessing clinician perspectives on work burden, burnout, and job satisfaction</article-title>
          <source>JAMIA Open</source>
          <year>2025</year>
          <month>02</month>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>ooaf013</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://academic.oup.com/jamiaopen/article-lookup/doi/10.1093/jamiaopen/ooaf013"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamiaopen/ooaf013</pub-id>
          <pub-id pub-id-type="medline">39991073</pub-id>
          <pub-id pub-id-type="pii">ooaf013</pub-id>
          <pub-id pub-id-type="pmcid">PMC11843214</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>Olson</surname>
              <given-names>KD</given-names>
            </name>
            <name name-style="western">
              <surname>Meeker</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Troup</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Barker</surname>
              <given-names>TD</given-names>
            </name>
            <name name-style="western">
              <surname>Nguyen</surname>
              <given-names>VH</given-names>
            </name>
            <name name-style="western">
              <surname>Manders</surname>
              <given-names>JB</given-names>
            </name>
            <name name-style="western">
              <surname>Stults</surname>
              <given-names>CD</given-names>
            </name>
            <name name-style="western">
              <surname>Jones</surname>
              <given-names>VG</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>SD</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Schwamm</surname>
              <given-names>LH</given-names>
            </name>
          </person-group>
          <article-title>Use of ambient AI scribes to reduce administrative burden and professional burnout</article-title>
          <source>JAMA Netw Open</source>
          <year>2025</year>
          <month>10</month>
          <day>01</day>
          <volume>8</volume>
          <issue>10</issue>
          <fpage>e2534976</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jamanetwork.com/journals/jamanetworkopen/fullarticle/10.1001/jamanetworkopen.2025.34976"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamanetworkopen.2025.34976</pub-id>
          <pub-id pub-id-type="medline">41037268</pub-id>
          <pub-id pub-id-type="pii">2839542</pub-id>
          <pub-id pub-id-type="pmcid">PMC12492056</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>Haberle</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Cleveland</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Snow</surname>
              <given-names>GL</given-names>
            </name>
            <name name-style="western">
              <surname>Barber</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Stookey</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Thornock</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Younger</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Mullahkhel</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Ize-Ludlow</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>The impact of nuance DAX ambient listening AI documentation: a cohort study</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2024</year>
          <month>04</month>
          <day>03</day>
          <volume>31</volume>
          <issue>4</issue>
          <fpage>975</fpage>
          <lpage>979</lpage>
          <pub-id pub-id-type="doi">10.1093/jamia/ocae022</pub-id>
          <pub-id pub-id-type="medline">38345343</pub-id>
          <pub-id pub-id-type="pii">7606586</pub-id>
          <pub-id pub-id-type="pmcid">PMC10990544</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>Alpert</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Saper</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Boose</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Ruff</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hopkins</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Gaskins</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Guo</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Schneider</surname>
              <given-names>JP</given-names>
            </name>
            <name name-style="western">
              <surname>Giffi Scibona</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gutierrez</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Rothberg</surname>
              <given-names>MB</given-names>
            </name>
          </person-group>
          <article-title>Evaluating an artificial intelligence scribe for clinical documentation</article-title>
          <source>Digit Health</source>
          <year>2025</year>
          <volume>11</volume>
          <fpage>20552076251395588</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/10.1177/20552076251395588?url_ver=Z39.88-2003&#38;rfr_id=ori:rid:crossref.org&#38;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/20552076251395588</pub-id>
          <pub-id pub-id-type="medline">41278378</pub-id>
          <pub-id pub-id-type="pii">10.1177_20552076251395588</pub-id>
          <pub-id pub-id-type="pmcid">PMC12638734</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>Sasseville</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Yousefi</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Ouellet</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Naye</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Stefan</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Carnovale</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Bergeron</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Ling</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Gheorghiu</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Hagens</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Gareau-Lajoie</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>LeBlanc</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>The impact of AI scribes on streamlining clinical documentation: a systematic review</article-title>
          <source>Healthcare (Basel)</source>
          <year>2025</year>
          <month>06</month>
          <day>16</day>
          <volume>13</volume>
          <issue>12</issue>
          <fpage>20552076251395588</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=healthcare13121447"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/healthcare13121447</pub-id>
          <pub-id pub-id-type="medline">40565474</pub-id>
          <pub-id pub-id-type="pii">healthcare13121447</pub-id>
          <pub-id pub-id-type="pmcid">PMC12193156</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>Husa</surname>
              <given-names>RA</given-names>
            </name>
            <name name-style="western">
              <surname>Haggerty</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Nute</surname>
              <given-names>AW</given-names>
            </name>
            <name name-style="western">
              <surname>Levine</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Love</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Martinez</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Parrish</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Ambient artificial intelligence use and clinician documentation burden, productivity, and efficiency</article-title>
          <source>JAMA Netw Open</source>
          <year>2026</year>
          <month>05</month>
          <day>01</day>
          <volume>9</volume>
          <issue>5</issue>
          <fpage>e2615762</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jamanetwork.com/journals/jamanetworkopen/fullarticle/10.1001/jamanetworkopen.2026.15762"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamanetworkopen.2026.15762</pub-id>
          <pub-id pub-id-type="medline">42213439</pub-id>
          <pub-id pub-id-type="pii">2849634</pub-id>
          <pub-id pub-id-type="pmcid">PMC13221680</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>Pinto</surname>
              <given-names>RZ</given-names>
            </name>
            <name name-style="western">
              <surname>Ferreira</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>Oliveira</surname>
              <given-names>VC</given-names>
            </name>
            <name name-style="western">
              <surname>Franco</surname>
              <given-names>MR</given-names>
            </name>
            <name name-style="western">
              <surname>Adams</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Maher</surname>
              <given-names>CG</given-names>
            </name>
            <name name-style="western">
              <surname>Ferreira</surname>
              <given-names>PH</given-names>
            </name>
          </person-group>
          <article-title>Patient-centred communication is associated with positive therapeutic alliance: a systematic review</article-title>
          <source>J Physiother</source>
          <year>2012</year>
          <month>06</month>
          <volume>58</volume>
          <issue>2</issue>
          <fpage>77</fpage>
          <lpage>87</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/S1836-9553(12)70087-5"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/s1836-9553(12)70087-5</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>Brondfield</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>O'Sullivan</surname>
              <given-names>PS</given-names>
            </name>
          </person-group>
          <article-title>The cognitive load of inpatient consults: a convergent parallel mixed methods study using the consult cognitive load instrument</article-title>
          <source>Acad Med</source>
          <year>2021</year>
          <month>11</month>
          <day>01</day>
          <volume>96</volume>
          <issue>11S</issue>
          <fpage>S119</fpage>
          <lpage>S125</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://academic.oup.com/academicmedicine/article-lookup/doi/10.1097/ACM.0000000000004265"/>
          </comment>
          <pub-id pub-id-type="doi">10.1097/ACM.0000000000004265</pub-id>
          <pub-id pub-id-type="medline">34348389</pub-id>
          <pub-id pub-id-type="pii">00001888-202111001-00021</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Evans</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Papinniemi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ploderer</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Nicholson</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Hindhaugh</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Vuvan</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Cowley</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Tariq</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Thomson</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Impact of using an AI scribe on clinical documentation and clinician-patient interactions in allied health private practice: perspectives of clinicians and patients</article-title>
          <source>Musculoskelet Sci Pract</source>
          <year>2025</year>
          <month>08</month>
          <volume>78</volume>
          <fpage>103333</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2468-7812(25)00081-5"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.msksp.2025.103333</pub-id>
          <pub-id pub-id-type="medline">40328004</pub-id>
          <pub-id pub-id-type="pii">S2468-7812(25)00081-5</pub-id>
        </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>Palm</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Manikantan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Mahal</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Belwadi</surname>
              <given-names>SS</given-names>
            </name>
            <name name-style="western">
              <surname>Pepin</surname>
              <given-names>ME</given-names>
            </name>
          </person-group>
          <article-title>Assessing the quality of AI-generated clinical notes: validated evaluation of a large language model ambient scribe</article-title>
          <source>Front Artif Intell</source>
          <year>2025</year>
          <volume>8</volume>
          <fpage>1691499</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.3389/frai.2025.1691499"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/frai.2025.1691499</pub-id>
          <pub-id pub-id-type="medline">41199808</pub-id>
          <pub-id pub-id-type="pmcid">PMC12586549</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>Ha</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Choon-Kon-Yune</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Murray</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Luan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Montague</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Bhattacharyya</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Agarwal</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Evaluating the usability, technical performance, and accuracy of artificial intelligence scribes for primary care: competitive analysis</article-title>
          <source>JMIR Hum Factors</source>
          <year>2025</year>
          <month>07</month>
          <day>23</day>
          <volume>12</volume>
          <fpage>e71434</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://humanfactors.jmir.org/2025//e71434/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/71434</pub-id>
          <pub-id pub-id-type="medline">40700466</pub-id>
          <pub-id pub-id-type="pii">v12i1e71434</pub-id>
          <pub-id pub-id-type="pmcid">PMC12309782</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>Lah</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Lewis</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Šumak</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Perceived usability and the modified technology acceptance model</article-title>
          <source>Int J Hum Comput Interact</source>
          <year>2020</year>
          <month>02</month>
          <day>17</day>
          <volume>36</volume>
          <issue>13</issue>
          <fpage>1216</fpage>
          <lpage>1230</lpage>
          <pub-id pub-id-type="doi">10.1080/10447318.2020.1727262</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
